PHYSICAL DOWNLINK CONTROL CHANNEL TRANSMISSION FOR MULTICAST / BROADCAST SYSTEM SERVICES - Patent application

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may monitor a search space associated with a PDCCH corresponding to a multicast / broadcast (MBS) physical downlink shared channel (PDSCH) for at least one MBS PDCCH communication having a payload scrambled according to a PDCCH payload scrambling sequence based on a group RNTI (G-RNTI) or a radio network temporary identifier (RNTI) value equal to zero. The UE may receive the at least one MBS PDCCH communication. Numerous other aspects are described.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application claims priority to U.S. Provisional Patent Application No. 63 / 260,560, entitled "PHYSICAL DOWNLINK CONTROL CHANNEL TRANSMISSIONS FOR MULTICAST / BROADCAST SYSTEM SERVICES," filed on August 25, 2021, U.S. Provisional Patent Application No. 63 / 262,349, entitled "PHYSICAL DOWNLINK CONTROL CHANNEL TRANSMISSIONS FOR MULTICAST / BROADCAST SYSTEM SERVICES," filed on October 10, 2021, and U.S. Non-Provisional Patent Application No. 17 / 804,797, entitled "PHYSICAL DOWNLINK CONTROL CHANNEL TRANSMISSIONS FOR MULTICAST / BROADCAST SYSTEM SERVICES," filed on May 31, 2022, which are expressly incorporated by reference herein.

[0002] Aspects of the present disclosure relate generally to wireless communications and techniques and apparatus for physical downlink control channel transmission for multicast / broadcast system services. [Background technology]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may utilize multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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). LTE / LTE-Advanced is a set of improvements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP).

[0004] A wireless network may include one or more network nodes that support communication for a user equipment (UE) or multiple UEs. A UE may communicate with the network nodes via downlink and uplink communications. "Downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node.

[0005] The above multiple access technologies have been adopted in various communication standards to provide a common protocol that allows different UEs to communicate on a city, country, region, and / or global scale. New Radio (NR), sometimes referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink, and better integrating with other open standards that support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the Invention

[0006] Certain aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include monitoring a search space associated with a physical downlink control channel (MBS) PDCCH corresponding to a MBS physical downlink shared channel (PDSCH) for at least one MBS PDCCH communication having a payload scrambled according to a PDCCH payload scrambling sequence based on a radio network temporary identifier (RNTI) value equal to zero. The method may include receiving the at least one MBS PDCCH communication.

[0007] Certain aspects described herein relate to a method of wireless communication implemented by a UE. The method may include monitoring a search space associated with a PDCCH corresponding to an MBS PDSCH for at least one MBS PDCCH communication having a control channel element (CCE) index corresponding to a hash function based on a value of an RNTI equal to zero. The method may include receiving the at least one MBS PDCCH communication.

[0008] Certain aspects described herein relate to a method of wireless communication implemented by a UE. The method may include receiving an MBS configuration for configuring a plurality of G-RNTIs for a cell. The method may include monitoring, for at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the plurality of MBS PDSCH communications, at least one search space associated with a PDCCHPDCCH corresponding to the MBS PDSCH of the cell based on the MBS configuration.

[0009] Certain aspects described herein relate to a method of wireless communication implemented by a network node. The method may include transmitting an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of an RNTI equal to zero for a search space associated with a PDCCHPDCCH corresponding to an MBS PDSCH. The method may include transmitting at least one MBS PDCCH communication based at least in part on the configuration.

[0010] Certain aspects described herein relate to a method of wireless communication performed by a base station. The method may include transmitting an MBS configuration indicating a PDCCH hashing function based on a value of RNTI equal to zero for a search space associated with a PDCCH corresponding to an MBS PDSCH. The method may include transmitting at least one MBS PDCCH communication based at least in part on the configuration.

[0011] Certain aspects described herein relate to a method of wireless communication implemented by a network node. The method may include transmitting an MBS configuration to configure a plurality of G-RNTIs for a cell. The method may include transmitting at least one MBS PDCCH communication to schedule at least one MBS PDSCH communication of the plurality of MBS PDSCH communications based on the MBS configuration and using at least one search space associated with a PDCCH corresponding to an MBS PDSCH of the cell.

[0012] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to monitor a search space associated with a PDCCH corresponding to an MBS PDSCH for at least one MBS PDCCH communication having a payload scrambled according to a PDCCH payload scrambling sequence based on a value of an RNTI equal to zero. The one or more processors may be configured to receive the at least one MBS PDCCH communication.

[0013] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to monitor a search space associated with a PDCCH corresponding to an MBS PDSCH for at least one MBS PDCCH communication having a CCE index corresponding to a hash function based on a value of the RNTI equal to zero. The one or more processors may be configured to receive the at least one MBS PDCCH communication.

[0014] Certain aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive an MBS configuration that configures a plurality of G-RNTIs for a cell. The one or more processors may be configured to monitor, for at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the plurality of MBS PDSCH communications, at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell based on the MBS configuration.

[0015] Certain aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of G-RNTI or RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH. The one or more processors may be configured to transmit at least one MBS PDCCH communication based at least in part on the configuration.

[0016] Certain aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit an MBS configuration indicating a PDCCH hashing function based on a value of the RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH. The one or more processors may be configured to transmit at least one MBS PDCCH communication based at least in part on the configuration.

[0017] Certain aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit an MBS configuration that configures a plurality of G-RNTIs for a cell. The one or more processors may be configured to transmit at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the plurality of MBS PDSCH communications based on the MBS configuration and using at least one search space associated with a PDCCH corresponding to an MBS PDSCH of the cell.

[0018] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to monitor a search space associated with a PDCCH corresponding to an MBS PDSCH for at least one MBS PDCCH communication having a payload scrambled according to a PDCCH payload scrambling sequence based on a value of an RNTI equal to zero. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive the at least one MBS PDCCH communication.

[0019] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to monitor a search space associated with a PDCCH corresponding to an MBS PDSCH for at least one MBS PDCCH communication having a CCE index corresponding to a hash function based on a value of the RNTI equal to zero. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive the at least one MBS PDCCH communication.

[0020] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive an MBS configuration for configuring a plurality of G-RNTIs for a cell. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to monitor at least one search space associated with a PDCCH corresponding to an MBS PDSCH of the cell based on the MBS configuration for at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the plurality of MBS PDSCH communications.

[0021] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of RNTI equal to zero for a search space associated with a PDCCH corresponding to an MBS PDSCH. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit at least one MBS PDCCH communication based at least in part on the configuration.

[0022] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit an MBS configuration indicating a PDCCH hashing function based on a value of RNTI equal to zero for a search space associated with a PDCCH corresponding to an MBS PDSCH. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit at least one MBS PDCCH communication based at least in part on the configuration.

[0023] Certain aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit an MBS configuration that configures a plurality of G-RNTIs for a cell. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the plurality of MBS PDSCH communications based on the MBS configuration and using at least one search space associated with a PDCCH corresponding to an MBS PDSCH of the cell.

[0024] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for monitoring a search space associated with a PDCCH corresponding to an MBS PDSCH for at least one MBS PDCCH communication having a payload scrambled according to a PDCCH payload scrambling sequence based on a value of an RNTI equal to zero. The apparatus may include means for receiving the at least one MBS PDCCH communication.

[0025] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for monitoring a search space associated with a PDCCH corresponding to an MBS PDSCH for at least one MBS PDCCH communication having a CCE index corresponding to a hash function based on a value of an RNTI equal to zero. The apparatus may include means for receiving the at least one MBS PDCCH communication.

[0026] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an MBS configuration for configuring a plurality of G-RNTIs for a cell. The apparatus may include means for monitoring, for at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the plurality of MBS PDSCH communications, at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell based on the MBS configuration.

[0027] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of RNTI equal to zero for a search space associated with a PDCCH corresponding to an MBS PDSCH. The apparatus may include means for transmitting at least one MBS PDCCH communication based at least in part on the configuration.

[0028] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting an MBS configuration indicating a PDCCH hashing function based on a value of RNTI equal to zero for a search space associated with a PDCCH corresponding to an MBS PDSCH. The apparatus may include means for transmitting at least one MBS PDCCH communication based at least in part on the configuration.

[0029] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting an MBS configuration that configures a plurality of G-RNTIs for a cell. The apparatus may include means for transmitting at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the plurality of MBS PDSCH communications based on the MBS configuration and using at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell.

[0030] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated by the drawings and this specification.

[0031] The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure in order that the following Detailed Description may be better understood. Additional features and advantages are described hereinafter. The concept and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The nature of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for the purpose of illustration and description, and not as a definition of the limits of the claims.

[0032] Although aspects are described in this disclosure by illustrating some examples, those skilled in the art will understand that such aspects can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects can be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence-enabled devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital applications (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is contemplated that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and configurations. [Brief description of the drawings]

[0033] So that the above-listed features of the present disclosure may be understood in detail, a more detailed description, briefly summarized above, may be obtained by referring to the embodiments, some of which are shown in the accompanying drawings. However, it should be noted that the accompanying drawings show only some typical embodiments of the present disclosure, and therefore should not be considered as limiting its scope, since the present description may admit of other equally effective embodiments. The same reference numbers in different drawings may identify the same or similar elements. [Figure 1]FIG. 1 illustrates an example of a wireless network in accordance with the present disclosure. [Diagram 2] FIG. 1 illustrates an example of a base station communicating with user equipment (UE) in a wireless network in accordance with the present disclosure. [Diagram 3] FIG. 1 illustrates an example of a disaggregated base station architecture in accordance with the present disclosure. [Figure 4] FIG. 1 illustrates an example associated with a physical downlink control channel (PDCCH) transmission for a multicast / broadcast system (MBS) service in accordance with the present disclosure. [Diagram 5] 1 illustrates an example process associated with PDCCH transmission for an MBS service in accordance with the present disclosure. [Figure 6] 1 illustrates an example process associated with PDCCH transmission for an MBS service in accordance with the present disclosure. [Figure 7] 1 illustrates an example process associated with PDCCH transmission for an MBS service in accordance with the present disclosure. [Figure 8] 1 illustrates an example process associated with PDCCH transmission for an MBS service in accordance with the present disclosure. [Figure 9] 1 illustrates an example process associated with PDCCH transmission for an MBS service in accordance with the present disclosure. [Figure 10] 1 illustrates an example process associated with PDCCH transmission for an MBS service in accordance with the present disclosure. [Figure 11] FIG. 1 is a diagram of an example apparatus for wireless communication in accordance with the present disclosure. [Figure 12] FIG. 1 is a diagram of an example apparatus for wireless communication in accordance with the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0034] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Those skilled in the art should understand that the scope of the present disclosure encompasses any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects described herein. In addition, the scope of the present disclosure is intended to encompass such an apparatus or method that is practiced using other structures, functions, or structures and functions in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0035] Several aspects of a communication system are now presented with reference to various apparatus and techniques that are described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0036] Although aspects may be described herein using terminology commonly associated with 5G or New Radio (NR) radio access technologies (RATs), aspects of the disclosure may apply to other RATs, such as 3G RATs, 4G RATs, and / or post-5G (e.g., 6G) RATs.

[0037] FIG. 1 illustrates an example of a wireless network 100 in accordance with the present disclosure. The wireless network 100 may be or include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base stations 110 are entities that communicate with the UEs 120. The base stations 110 (sometimes referred to as BSs) may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, and / or transmit / receive points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​a base station 110 and / or a base station subsystem that serves that coverage area, depending on the context in which the term is used.

[0038] A base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 with an association with a femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or an indoor base station. 1, BS 110a may be a macro base station for a macro cell 102a, BS 110b may be a pico base station for a pico cell 102b, and BS 110c may be a femto base station for a femto cell 102c. A base station may support one or multiple (e.g., three) cells.

[0039] In some examples, the cells may not necessarily be stationary and the geographic area of ​​the cells may move according to the location of the base station 110 that is mobile (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected to each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0040] The wireless network 100 may include one or more relay stations. A relay station is an entity that may receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and send a transmission of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that may relay a transmission for another UE 120. In the example shown in FIG. 1, a BS 110d (e.g., a relay base station) may communicate with a BS 110a (e.g., a macro base station) and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A base station 110 that relays communication may be referred to as a relay station, a relay base station, a relay, etc.

[0041] In some aspects, the term "base station" or "network entity" may refer to an aggregated base station, a non-aggregated base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, the term "base station" or "network entity" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to one device configured to perform one or more functions, such as those described herein with respect to the network entity 110. In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, multiple different devices (which may be located at the same geographic location or different geographic locations) may each be configured to perform at least a portion of a function or replicate the implementation of at least a portion of a function, and the term "base station" or "network entity" may refer to any one or more of those different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions and not to another. In this manner, a single device may include two or more base stations.

[0042] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different susceptibility to interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5-40 watts), while the pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1-2 watts).

[0043] A network controller 130 may couple to or communicate with a set of base stations 110 and may provide coordination and control for these base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may communicate with each other directly or indirectly via wireless or wired backhaul communication links.

[0044] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be fixed or mobile. The UEs 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. The UEs 120 may be a mobile phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate over a wireless medium.

[0045] Some UEs 120 may be considered as machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and / or a location tag that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. The UEs 120 may be included within a housing that houses components of the UEs 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled to each other. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0046] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. The RAT may be referred to as a radio technology, an air interface, etc. The frequencies may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR networks or 5G RAT networks may be deployed.

[0047] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using the base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, vehicle-to-everything (V2X) protocols (which may include, e.g., vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, the UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0048] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, etc. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that FR1 is often referred to (interchangeably) as a "sub-6 GHz" band in various documents and articles, although a portion of FR1 is above 6 GHz. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as a "mmWave" band in documents and articles, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as a "mmWave" band by the International Telecommunications Union (ITU).

[0049] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and / or FR2 characteristics, and thus may in effect extend the features of FR1 and / or FR2 to the mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0050] With the above examples in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specified, it should be understood that terms such as "mmWave" as used herein may broadly refer to frequencies that may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, may include mid-band frequencies, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may change, and the techniques described herein are applicable to those changed frequency ranges.

[0051] In some aspects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, communications manager 140 may monitor a search space associated with a PDCCH corresponding to an MBS physical downlink shared channel (PDSCH) for at least one Multicast / Broadcast System (MBS) PDCCH communication having a payload scrambled in accordance with a PDCCH payload scrambling sequence based on a Group RNTI (G-RNTI) or a Radio Network Temporary Identifier (RNTI) value equal to zero, and may receive at least one MBS PDCCH communication. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0052] In some aspects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, communications manager 140 may monitor a search space associated with a PDCCH corresponding to an MBS PDSCH for at least one MBS PDCCH communication having a control channel element (CCE) index corresponding to a hash function based on a value of the G-RNTI or an RNTI equal to zero, and may receive the at least one MBS PDCCH communication. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0053] In some aspects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, communications manager 140 may receive an MBS configuration that configures a plurality of G-RNTIs for a cell, and monitor at least one search space associated with a PDCCH corresponding to an MBS PDSCH of the cell based on the MBS configuration for at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the plurality of MBS PDSCH communications. Additionally or alternatively, communications manager 140 may perform one or more other operations described herein.

[0054] In some aspects, the network node 110 may include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 may transmit an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of the G-RNTI or an RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH, and may transmit at least one MBS PDCCH communication based at least in part on the configuration. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0055] In some aspects, the network node 110 may include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 may transmit an MBS configuration indicating a PDCCH hashing function based on a value of the G-RNTI or an RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH, and may transmit at least one MBS PDCCH communication based at least in part on the configuration. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0056] In some aspects, the network node 110 may include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 may transmit an MBS configuration to configure a plurality of G-RNTIs for the cell, and transmit at least one MBS PDCCH communication to schedule at least one MBS PDSCH communication of the plurality of MBS PDSCH communications using at least one search space associated with a PDCCH corresponding to an MBS PDSCH of the cell based on the MBS configuration. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0057] As noted above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0058] 2 illustrates an example base station 200 in communication with a UE 120 in a wireless network 100 in accordance with the present disclosure. The base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas, where T≧1. The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas, where R≧1.

[0059] At the base station 110, a transmit processor 220 may receive data destined for a UE 120 (or set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The base station 110 may process (e.g., encode and modulate) data for the UE 120 based at least in part on the MCS selected for the UE 120 and provide data symbols to the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or higher layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for a reference signal (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and a synchronization signal (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), denoted as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (denoted as MOD) of modem 232. Each modem 232 may process a respective output symbol stream (e.g., for OFDM) using a respective modulator component to obtain an output sample stream. Each modem 232 may further process (eg, convert to analog, amplify, filter, and / or upconvert) the output sample stream using a respective modulator component to obtain a downlink signal.Modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) denoted as antennas 234a through 234t.

[0060] At the UE 120, a set of antennas 252 (depicted as antennas 252a through 252r) may receive downlink signals from the base station 110 and / or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) depicted as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (depicted as DEMOD) of the modems 254. Each modem 254 may condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal using a respective demodulator component to obtain input samples. Each modem 254 may further process the input samples (e.g., for OFDM) using the demodulator component to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other examples. In some aspects, one or more components of the UE 120 may be included within the housing 284.

[0061] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base stations 110 via the communication unit 294.

[0062] One or more antennas (e.g., antennas 234a-t and / or antennas 252a-r) may include or be contained within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. The antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more of the components in FIG.

[0063] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna(s) 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to implement aspects of any of the methods described herein (eg, with reference to Figures 4-12).

[0064] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by an antenna 234, processed by a modem 232 (e.g., a demodulator component of the modem 232, denoted as DEMOD), detected by a MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 for scheduling one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modem(s) 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to implement aspects of any of the methods described herein (e.g., with reference to FIGS. 4-12).

[0065] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component(s) of Figure 2 may implement one or more techniques associated with PDCCH transmission of the MBS service, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component(s) of Figure 2 may implement or direct the operation of, for example, process 500 of Figure 5, process 600 of Figure 6, process 700 of Figure 7, process 800 of Figure 8, process 900 of Figure 9, process 1000 of Figure 10, and / or other processes described herein. The memory 242 and the memory 282 may store data and program codes for the base station 110 and the UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly or after being compiled, converted, and / or interpreted), may cause the one or more processors, UE 120, and / or base station 110 to perform or direct operations of, for example, process 500 of FIG. 5, process 600 of FIG. 6, process 700 of FIG. 7, process 800 of FIG. 8, process 900 of FIG. 9, process 1000 of FIG. 10, and / or other processes as described herein. In some examples, executing the instructions may include executing the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0066] In some aspects, the UE includes means for monitoring a search space associated with a PDCCH corresponding to the MBS PDSCH for at least one MBS PDCCH communication having a payload scrambled in accordance with a PDCCH payload scrambling sequence based on a value of the G-RNTI or an RNTI equal to zero, and / or means for receiving at least one MBS PDCCH communication. Means for causing the UE to perform operations described herein may include, for example, one or more of communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0067] In some aspects, the UE includes means for monitoring a search space associated with a PDCCH corresponding to the MBS PDSCH for at least one MBS PDCCH communication having a CCE index corresponding to a hash function based on a value of the G-RNTI or an RNTI equal to zero, and / or means for receiving at least one MBS PDCCH communication. Means for causing the UE to perform operations described herein may include, for example, one or more of communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0068] In some aspects, the UE includes means for receiving an MBS configuration for configuring a plurality of G-RNTIs for the cell and / or means for monitoring at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell for at least one MBS PDCCH communication for scheduling at least one MBS PDSCH communication of the plurality of MBS PDSCH communications based on the MBS configuration. Means for causing the UE to perform operations described herein may include, for example, one or more of communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0069] In some aspects, the network node includes means for transmitting an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of the G-RNTI or an RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH, and / or means for transmitting at least one MBS PDCCH communication based at least in part on the configuration. Means for causing the network node to perform operations described herein may include, for example, one or more of the communications manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antennas 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0070] In some aspects, the network node includes means for transmitting an MBS configuration indicating a PDCCH hashing function based on a value of the G-RNTI or an RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH, and / or means for transmitting at least one MBS PDCCH communication based at least in part on the configuration. Means for causing the network node to perform operations described herein may include, for example, one or more of the communications manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antennas 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0071] In some aspects, the network node includes means for transmitting an MBS configuration that configures a plurality of G-RNTIs for the cell and / or means for transmitting at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the plurality of MBS PDSCH communications based on the MBS configuration and using at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell. Means for causing the network node to perform operations described herein may include, for example, one or more of the communications manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antennas 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0072] 2 are shown as separate components, the functionality described above with respect to the blocks may be implemented in a single hardware, software, or combination of components, or in various combinations of components. For example, functionality described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0073] As noted above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0074] The deployment of a communication system such as a 5G NR system can be configured in multiple ways with various components or parts. In a 5G NR system or network, a network node, a network entity, a mobility element of the network, a RAN node, a core network node, a network element, a base station, or a network equipment may be implemented in an aggregated or disaggregated architecture. For example, a base station (e.g., a Node B (NB), an evolved NB (eNB), a NR BS, a 5G NB, an Access Point (AP), a TRP, or a cell, among other examples), or one or more units (or one or more components) performing a base station function, may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0075] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A non-aggregated base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (e.g., a CU, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a RAN node, and one or more DUs may be collocated with the CU, or alternatively may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.

[0076] The operation or network design of the base station type may take into account the aggregation characteristics of the base station functions. For example, disaggregated base stations may be utilized in an IAB network, an open radio access network (O-RAN (e.g., a network configuration supported by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate scaling of the communication system by separating the base station functions into one or more units that can be deployed separately. A disaggregated base station may include functions implemented across two or more units in various physical locations as well as functions implemented virtually for at least one unit, which may allow flexibility in the network design. The various units of the disaggregated base station may be configured for wired or wireless communication with at least one other unit of the disaggregated base station.

[0077] 3 illustrates an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link or indirectly with the core network 320 via one or more disaggregated control units (e.g., a quasi-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, e.g., through an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served by multiple RUs 340 simultaneously.

[0078] Each of the units, including the CU 310, DU 330, RU 340, and the quasi-RT RIC 325, non-RT RIC 315, and SMO framework 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the respective unit's one or more communication interfaces, may be configured to communicate with one or more of the other units over a transmission medium. In some examples, each of the units may include a wired interface configured to receive or transmit signals to or from one or more of the other units over a wired transmission medium, and a wireless interface, which may include a receiver, transmitter, or transceiver (e.g., an RF transceiver), configured to receive, transmit, or transmit / receive signals to or from one or more of the other units over a wireless transmission medium.

[0079] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include a radio resource control (RRC) function, a packet data convergence protocol (PDCP) function, or a service data adaptation protocol (SDAP) function, among other examples. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functions (e.g., a central unit-user plane (CU-UP) function), control plane functions (e.g., a central unit-control plane (CU-CP) function), or a combination thereof. In some implementations, the CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP units may communicate bidirectionally with the CU-CP units over an interface, such as an E1 interface, if implemented in an O-RAN configuration. The CU 310 may be implemented to communicate with the DU 330, as necessary, for network control and signaling.

[0080] Each DU 330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more upper physical (PHY) layers, at least in part according to a functional division, such as that defined by 3GPP. In some aspects, the one or more upper PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, among other examples. In some aspects, the DU 330 may further host one or more lower PHY layers, such as implemented by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, among other examples. Each layer (which may also be referred to as a module) may be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with a control function hosted by the CU 310.

[0081] Each RU 340 may implement lower layer functions. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node hosting RF processing functions or lower PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, among other examples, based on a functional partition such as a lower layer functional partition (e.g., functional partition defined by 3GPP). In such an architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340(s) may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0082] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (e.g., an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (e.g., an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (e.g., instantiate virtualized network elements) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network elements may include, but are not limited to, the CU 310, the DU 330, the RU 340, the non-RT RIC 315, and the quasi-RT RIC 325. In some implementations, the SMO framework 305 may communicate with hardware aspects of a 4G RAN, such as the open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a separate O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0083] The non-RT RIC 315 may be configured to include logic 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 guidance of applications / features in the quasi-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the quasi-RT RIC 325 (e.g., via an A1 interface). The quasi-RT RIC 325 may be configured to include logic functions that enable near real-time control and optimization of RAN elements and resources through data collection and action via interfaces (e.g., via an E2 interface) that connect one or more CUs 310, one or more DUs 330, or both, and the O-eNB to the quasi-RT RIC 325.

[0084] In some implementations, the non-RT RIC 315 may receive parameters or external enrichment information from an external server to generate AI / ML models to be deployed to the quasi-RT RIC 325. Such information may be utilized by the quasi-RT RIC 325 or may be received from non-network data sources or from network functions in the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the quasi-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns regarding performance and use the AI / ML models to implement corrective actions through the SMO framework 305 (e.g., reconfiguration via the O1 interface) or through the creation of RAN management policies (e.g., A1 interface policies).

[0085] A network node may use a PDCCH transmission to schedule a PDSCH transmission for a UE. However, multiple UEs may interact with and / or be connected to a cell. To facilitate targeting a PDCCH transmission to a specific UE among multiple UEs in a cell, the network node may scramble the PDCCH payload before modulation according to a scrambling sequence recognizable by the UE. In this way, UEs to which the transmission is not directed can avoid decoding the scheduling transmission, and even if more than one UE can detect the scheduling transmission, the network node can schedule each UE independently.

[0086] In some cases, the UE may be configured to monitor for PDCCH transmissions having a payload scrambled according to a scrambling sequence that is based on a Cell RNTI (C-RNTI) or a value of RNTI equal to zero. In some cases, for example, the value of RNTI is equal to C-RNTI if the communication is directed to a UE-specific search space (USS) and if certain parameters are configured, and is equal to zero otherwise.

[0087] For example, the UE may:

[0088]

number

[0089]

number

[0090]

number

[0091] The above PDCCH payload scrambling is useful for directing a PDCCH transmission to one UE among multiple UEs. However, in an MBS system, because the C-RNTI is UE specific, attempts by a network node to use this scrambling scheme will not be successful in directing a PDCCH transmission to multiple UEs (e.g., for multicast and / or broadcast). As a result, the scrambling scheme may impede MBS communications, which may adversely affect network performance.

[0092] In some cases, in the case of a common search space (CSS), multiple UEs may monitor PDCCH candidates on the same set of CCEs. For example, for a search space set s associated with a core resource set (CORESET) p, the carrier indicator field value n CI For the active downlink bandwidth portion (BWP) of the serving cell corresponding to

[0093]

number

[0094]

number

[0095]

number

[0096]

number

[0097]

number

[0098]

number

[0099]

number

[0100]

number

[0101]

number

[0102]

number

[0103] In this way, a single downlink control information (DCI) transmission can be delivered to all UEs. In the case of a UE-specific search space, different UEs may have different C-RNTI values ​​and PDCCH candidates for different UEs may be mapped onto different sets of CCEs. However, in general, common DCI transmissions on UE-specific search spaces are not possible. Thus, in an MBS system, because the C-RNTI is UE-specific, attempts by a network node to use a hash function based on the C-RNTI will not be successful in directing a PDCCH transmission to multiple UEs (e.g., for multicast and / or broadcast). As a result, the hash function may impede MBS communications, which may adversely affect network performance.

[0104] In some cases, a cyclic redundancy check (CRC) may be used to provide error detection in the DCI transmission. To facilitate the CRC, the entire payload may be used to calculate the CRC parity bits according to a procedure that may be specified by the wireless standard. The CRC parity bits may be scrambled with the corresponding RNTI so that the UE can interpret the CRC parity bits to detect errors. The RNTI on which the CRC scrambling may be based may be any number of different RNTIs, including the C-RNTI, modulation coding scheme cell RNTI (MCS-C-RNTI), configured scheduling RNTI (CS-RNTI), system information RNTI (SI-RNTI), paging RNTI (P-RNTI), random access RNTI (RA-RNTI), and / or slot format indication RNTI (SFI-RNTI), among other examples. The G-RNTI may be used to scramble the CRC parity bits, but a single G-RNTI may not allow for multiple PDSCH transmissions for multiple MBS services. As a result, CRC scrambling using a single RNTI may impede MBS communications, thereby adversely affecting network performance.

[0105] In some cases, the search space associated with the PDCCH corresponding to the MBS PDSCH may include, for example, an MBS-specific type CSS (e.g., may be referred to as a Type-x CSS). The search space may be used for group-common PDCCH transmission for multicast in the RRC connected state. The monitoring priority of the search space associated with the PDCCH corresponding to the MBS PDSCH may be determined based on the search space set index of the Type-x CSS set and the USS set, regardless of which DCI format of the group-common PDCCH is configured in the Type-x CSS. The group-common PDCCH used in the MBS may be configured to support at least two DCI formats. For example, DCI format 1_0 may be used as a baseline for a first DCI format with a CRC scrambled with the G-RNTI. DCI format 1_1 or 1_2 may be used as a baseline for a second DCI format with a CRC scrambled with the G-RNTI. However, as mentioned above, USS-based payload scrambling schemes, hash functions, and / or CRC scrambling schemes may not be adaptable to MBS communications.

[0106] Some aspects may provide PDCCH payload scrambling for PDCCH transmissions that schedule MBS PDSCH communications. Some aspects may provide a hash function for PDCCH transmissions that schedule MBS PDSCH communications. Some aspects may provide CRC scrambling for PDCCH transmissions that schedule MBS PDSCH communications. The scrambling and hashing techniques described herein may be based on an RNTI that may have a value equal to zero or a value equal to a G-RNTI (or G-RNTIs). In this manner, the PDCCH payload scrambling, hash function, and CRC scrambling may be adapted to be used for PDCCH transmissions that schedule MBS PDSCH communications such that multiple UEs can receive the multicast and / or broadcast transmission. As a result, some aspects may facilitate multicast and / or broadcast transmissions, thereby positively impacting network performance.

[0107] 4 is a diagram illustrating an example 400 associated with PDCCH transmission for an MBS service according to the present disclosure. As shown in FIG. 4, a network node 402 and a UE 404 may communicate with each other. In an MBS implementation, the network node 402 may communicate with several UEs 404, although only one such UE 404 is shown in FIG. 4.

[0108] As indicated by reference numeral 406, the MBS configuration may be transmitted by the network node 402 and received by the UE 404. In some aspects, for example, the UE 404 may be provided with a common frequency resource (CFR) configuration. The CFR may include information indicating where in the frequency domain the MBS data may be scheduled. The CFR configuration may include other parameters used to facilitate MBS communication. For example, an RRC configuration for a CORESET and associated search space may be provided as part of the CFR configuration.

[0109] In some aspects, the MBS configuration (and / or one or more aspects thereof) may be, include, be included in, or be similar to a CFR configuration. In some aspects, the network node 402 may transmit, and the UE 404 may receive, a configuration of a PDCCH DMRS scrambling identifier for a control resource set associated with a search space. For example, the configuration may configure a pdcch-DMRS-ScramblingID parameter. In some aspects, the network node 402 may transmit, and the UE 404 may receive, a dedicated configuration indication to configure a search space associated with a PDCCH corresponding to the MBS PDSCH. The dedicated configuration indication may be transmitted using a dedicated RRC message and / or a dedicated RRC parameter. In some aspects, the network node 402 may transmit, and the UE 404 may receive, an MBS configuration to configure multiple G-RNTIs for a cell. In some aspects, at least one G-RNTI of the plurality of G-RNTIs may include a value of an RNTI associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a CCE index, or a CRC scrambling sequence. In some aspects, the G-RNTI may be configured using a G-RNTI list. In some aspects, the configuration may indicate a mapping between the G-RNTI and a respective multicast service. The multicast service may include a designated multicast service identifier (ID). In some aspects, the network node 402 may transmit, and the UE 404 may receive, a configuration indicating a configurable dedicated value of the RNTI. The configurable dedicated value of the RNTI may be associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a CCE index, or a CRC scrambling sequence.In some aspects, the network node 402 may transmit, and the UE 120 may receive, an RRC configuration indicating a mapping between at least one search space and at least one G-RNTI of the plurality of G-RNTIs. Any of the configurations described above may be included in the CFR configuration and / or the MBS configuration, among other examples.

[0110] As indicated by reference numeral 408, the network node 402 can generate the MBS PDCCH communication using a scrambling sequence, a hash function, and / or a CRC sequence, among other examples, as described herein. As indicated by reference numeral 410, the UE 404 can monitor a search space for at least one MBS PDCCH communication.

[0111] For example, in some aspects, the UE 404 may monitor a search space associated with a PDCCH corresponding to an MBS PDSCH for at least one MBS PDCCH communication having a payload scrambled according to a PDCCH payload scrambling sequence based on the value of the RNTI. The value of the RNTI may be equal to G-RNTI or zero. The value of the RNTI may be equal to zero and the UE 404 may receive a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space. In some aspects, the UE 404 does not receive a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space. For example, payload scrambling for a PDCCH scheduling an MBS PDSCH may be set to n. RNTI= 0. This may be true regardless of whether a pdcch-DMRS-ScramblingID parameter is provided in the controlResourceSet for the CORESET associated with the search space. In some aspects, the value of RNTI is equal to zero and PDCCH DMRS scrambling ID is not supported for the CORESET associated with the search space. For example, payload scrambling for a PDCCH that schedules an MBS PDSCH may be based on n RNTI =0, and pdcch-DMRS-ScramblingID may not be supported for the controlResourceSet for the CORESET associated with the search space.

[0112] In some aspects, the value of the RNTI may be equal to the G-RNTI and the UE 404 may receive a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space. The value of the RNTI may be equal to the G-RNTI and the UE 404 may not receive a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space. For example, payload scrambling for a PDCCH that schedules an MBS PDSCH may be configured to be n regardless of whether a pdcch-DMRS-ScramblingID is provided in the controlResourceSet for a CORESET associated with the search space. RNTI = May be based on G-RNTI.

[0113] In some aspects, the network node 402 may transmit, and the UE 404 may receive, a configuration of the PDCCH DMRS scrambling ID for a CORESET associated with the search space, and the value of the RNTI may be equal to G-RNTI based on the network node 402 transmitting and / or the UE 404 receiving the PDCCH DMRS scrambling ID configuration. In some aspects, the UE 404 may not receive a configuration of the PDCCH DMRS scrambling ID for a CORESET associated with the search space, and the value of the RNTI may be equal to zero based on the network node 402 not transmitting and / or the UE 404 not receiving the PDCCH DMRS scrambling ID configuration. For example, payload scrambling for a PDCCH scheduling an MBS PDSCH may be n if pdcch-DMRS-ScramblingID is provided in the controlResourceSet of the CORESET associated with the search space. RNTI = G-RNTI, otherwise n RNTI =0.

[0114] In some aspects, the network node 402 may transmit, and the UE 404 may receive, a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with a search space, and the network node 402 may transmit, and the UE 404 may receive, a dedicated configuration indication for configuring the search space. The value of the RNTI may be equal to the G-RNTI based on the network node 402 transmitting, and / or the UE 404 receiving, a configuration of a PDCCH DMRS scrambling ID and a dedicated configuration indication. In some aspects, the network node 402 may transmit, and the UE 404 may receive, a dedicated configuration indication by transmitting and receiving, respectively, a dedicated RRC message and / or RRC parameters. The value of the RNTI may be equal to zero based on a determination that the network node 402 has not transmitted, and / or the UE 404 has not received, a dedicated configuration indication for configuring a PDCCH DMRS scrambling ID for a CORESET associated with a search space, and a search space. For example, payload scrambling for a PDCCH that schedules an MBS PDSCH is performed if the pdcch-DMRS-ScramblingID is provided in the controlResourceSet of the CORESET associated with the search space, and if the search space is configured by a UE-specific RRC message (or is configured using a dedicated RRC parameter). RNTI = G-RNTI, otherwise n RNTI =0.

[0115] In some aspects, the network node 402 may transmit, and the UE 404 may receive, a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space, and the UE 404 may monitor the search space by monitoring the search space only in the RRC connected state. The value of the RNTI may be equal to the G-RNTI based on receiving the configuration of a PDCCH DMRS scrambling ID and monitoring the search space only in the RRC connected state. The value of the RNTI may be equal to zero based on a determination that the network node 402 has not transmitted and / or the UE 404 has not received a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space and a determination that the search space is not monitored only in the RRC connected state. For example, payload scrambling for a PDCCH that schedules an MBS PDSCH is provided in the controlResourceSet for the CORESET associated with the search space, and if the search space is a search space that is monitored only in the RRC_connected state, then RNTI = G-RNTI, otherwise nn RNTI =0.

[0116] In some aspects, the at least one MBS PDCCH communication may include a DCI transmission that schedules the MBS PDSCH. The value of the RNTI may be equal to zero based on a determination that the DCI format of the DCI transmission is DCI format 1_0, and the value of the RNTI may be equal to G-RNTI based on a determination that the DCI format of the DCI transmission is not DCI format 1_0 (e.g., when the DCI transmission format is DCI format 1_1 or 1_2). For example, payload scrambling for the PDCCH that schedules the MBS PDSCH may be set to n if the PDCCH that schedules the MBS PDSCH is DCI format 1_0. RNTI = 0, otherwise, n RNTI = May be based on G-RNTI.

[0117] In some aspects, the UE 404 may monitor a search space for at least one MBS PDCCH communication having a CCE index that corresponds to a hash function based on a value of the RNTI, the value of the RNTI being equal to the G-RNTI or zero. In some aspects, the value of the RNTI is equal to zero. For example, the hash function for the search space may be RNTI = 0. In some aspects, the value of the RNTI may be equal to the G-RNTI. For example, the hash function for the search space may be based on n RNTI = May be based on G-RNTI.

[0118] In some aspects, the network node 402 may transmit, and the UE 404 may receive, an indication of an RRC parameter that enables the RNTI to be equal to the G-RNTI, and the value of the RNTI may be equal to the G-RNTI based on the network node 402 transmitting and / or the UE 404 receiving the indication of the RRC parameter. The value of the RNTI may be equal to zero based on a determination that the network node 402 has not transmitted and / or the UE 404 has not received an indication of an RRC parameter that enables the RNTI to be equal to the G-RNTI. For example, if the UE has determined that n RNTI When configured with RRC parameters enabling = G-RNTI, the hash function for the search space is n RNTI = G-RNTI. RNTI If not configured with an RRC parameter enabling = G-RNTI, the hash function is RNTI =0.

[0119] In some aspects, the network node 402 may transmit and the UE 404 may receive a dedicated configuration indication to configure the search space, and the value of the RNTI may be equal to G-RNTI based on the network node 402 transmitting and / or the UE 404 receiving the dedicated configuration indication. In some aspects, the network node 402 may transmit and the UE 404 may receive the dedicated configuration indication by transmitting and receiving a dedicated RRC message and / or dedicated RRC parameters, respectively. The value of the RNTI may be equal to zero based on a determination that the network node 402 has not transmitted and / or the UE 404 has not received a dedicated configuration indication to configure the search space. For example, in some aspects, the hash function for the search space may be: n if the CSS is configured by a UE-dedicated RRC message (or configured with dedicated RRC parameters), RNTI = G-RNTI, otherwise nRNTI =0.

[0120] In some aspects, the UE 404 may monitor the search space by monitoring the search space only in the RRC connected state, and the value of the RNTI may be equal to the G-RNTI based on the UE 404 monitoring the search space only in the RRC connected state. In some aspects, the value of the RNTI may be equal to zero based on a determination that the search space is not monitored only in the RRC connected state. For example, the hash function for the search space may be equal to n if the search space is a search space that is monitored only in the RRC_connected state. RNTI = G-RNTI, otherwise n RNTI =0.

[0121] In some aspects, as described above with respect to the scrambling sequence, for the hash function, the at least one MBS PDCCH communication may include a DCI transmission scheduling an MBS physical downlink shared channel, and the value of the RNTI may be equal to zero based on a determination that the DCI format of the DCI transmission is DCI format 1_0. The value of the RNTI may be equal to the G-RNTI based on a determination that the DCI format of the DCI transmission is not DCI format 1_0.

[0122] In some aspects, for a downlink cell, the UE 404 may monitor a PDCCH for an MBS PDSCH with multiple G-RNTIs. The network node 402 may transmit, and the UE 404 may receive, an MBS configuration that configures multiple G-RNTIs for the cell, and the UE 404 may monitor at least one search space of the cell for at least one MBS PDCCH communication that schedules the at least one MBS PDSCH communication of the multiple MBS PDSCH communications based on the MBS configuration. Each MBS PDSCH communication of the multiple MBS PDSCH communications may be associated with a corresponding G-RNTI of the multiple G-RNTIs. For example, different G-RNTIs may be used for different multicast services. At least one G-RNTI of the multiple G-RNTIs may include a value of an RNTI associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a CCE index, or a CRC scrambling sequence.

[0123] In some aspects, different G-RNTIs may be used, for example, for scrambling, hash functions, and / or CRC scrambling of DCIs for MBS PDSCHs associated with different G-RNTIs. In some aspects, the value of the RNTI may be equal to at least one G-RNTI, and the at least one additional value of the RNTI may be equal to at least one additional G-RNTI of the multiple G-RNTIs. The value of the RNTI may be equal to the G-RNTI, and the at least one additional payload may be scrambled according to a PDCCH payload scrambling sequence based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI of the multiple G-RNTIs. In some aspects, the value of the RNTI may be equal to the G-RNTI, and the at least one additional CCE index may correspond to at least one additional hash function based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI of the multiple G-RNTIs.

[0124] In some aspects, one RNTI value may be used for scrambling, hash function, and / or CRC scrambling for DCI for MBS PDSCHs associated with different G-RNTIs. For example, in some aspects, at least one additional value of RNTI may be equal to the value of RNTI. At least one additional payload may be scrambled according to a PDCCH payload scrambling sequence based on the at least one additional value of RNTI, where the at least one additional value of RNTI is equal to the value of RNTI. At least one additional hash function may be based on the at least one additional value of RNTI, where the at least one additional value of RNTI is equal to the value of RNTI.

[0125] In some aspects, the value of the RNTI may be equal to a specified G-RNTI of a plurality of G-RNTIs. For example, the RNTI may be equal to the lowest value among the plurality of G-RNTIs and / or the highest value among the plurality of G-RNTIs, among other examples. In some aspects, the RNTI may be equal to a specified G-RNTI of a G-RNTI list. For example, the plurality of G-RNTIs may be configured using a G-RNTI list, and the value of the RNTI may be equal to the first listed G-RNTI of the G-RNTI list and / or the last listed G-RNTI of the G-RNTI list, among other examples. In some aspects, the G-RNTI may be mapped to a particular multicast service (e.g., a multicast service with the lowest multicast service ID and / or the highest multicast service ID, among other examples).

[0126] In some aspects, the RNTI may have a separately configurable value. In some aspects, values ​​may be separately configurable for, among other things, the hash function. In some aspects, the network node 402 may transmit, and the UE 404 may receive, a configuration indicating a configurable dedicated RNTI value. The configurable dedicated value of the RNTI may be associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a CCE index, or a CRC scrambling sequence. In some aspects, for example, a multicast UE may select n values ​​for scrambling, hash function, and / or CRC scrambling of DCI for MBS PDSCHs associated with different G-RNTIs. RNTI The multicast service may be configured with a value of RNTI. The multicast service may include a particular multicast service ID of a plurality of multicast service IDs. In some aspects, the value of the RNTI may include a configurable dedicated value.

[0127] In some aspects, when the at least one MBS PDCCH communication includes multiple MBS PDCCH communications, PDCCHs for MBS PDSCHs associated with different G-RNTIs may be monitored on the same search space set. In some aspects, for example, the mapping from G-RNTIs to search spaces may be one-to-one. In some aspects, PDCCHs for MBS PDSCHs associated with different G-RNTIs may be monitored on different search space sets. For example, the mapping from G-RNTIs to search spaces may be many-to-one. In some aspects, the mapping between the G-RNTIs and the search spaces associated with the PDCCHs corresponding to the MBS PDSCHs may be configured by RRC signaling. For example, the network node 402 may transmit, and the UE 404 may receive, an RRC configuration indicating a mapping between at least one search space and at least one G-RNTI of the multiple G-RNTIs.

[0128] At least one MBS PDCCH communication may be transmitted by the network node 402 and received by the UE 404, as indicated by reference numeral 412.

[0129] As noted above, Figure 4 is provided as an example. Other examples may differ from what is described with respect to Figure 4.

[0130] 5 illustrates an example process 500, performed by, for example, a UE, in accordance with the present disclosure. The example process 500 is an example in which a UE (e.g., the UE 404) performs operations associated with PDCCH transmission for an MBS service.

[0131] 5, in some aspects, process 500 may include monitoring a search space associated with a PDCCH corresponding to the MBS PDSCH for at least one MBS PDCCH communication having a payload scrambled according to a PDCCH payload scrambling sequence based on a value of G-RNTI or RNTI equal to zero (block 510). For example, the UE (e.g., using communications manager 140 and / or receiving component 1102 shown in FIG. 11) may monitor a search space for at least one MBS PDCCH communication having a payload scrambled according to a PDCCH payload scrambling sequence based on a value of G-RNTI or RNTI equal to zero, as described above.

[0132] 5, in some aspects, the process 500 may include receiving at least one MBS PDCCH communication (block 520). For example, the UE may receive the at least one MBS PDCCH communication (e.g., using the communications manager 140 and / or the receiving component 1102 shown in FIG. 11), as described above.

[0133] Process 500 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0134] In a first aspect, the value of the RNTI is equal to zero, and the method further includes receiving a configuration of a PDCCH DMRS scrambling ID for a CORSET associated with the search space.

[0135] In a second aspect, the value of RNTI is equal to zero and the UE does not receive a configuration of a PDCCH DMRS scrambling ID for the CORESET associated with the search space.

[0136] In a third aspect, the value of RNTI is equal to zero and the PDCCH DMRS scrambling ID is not supported for the control resource set associated with the search space.

[0137] In a fourth aspect, the value of the RNTI is equal to the G-RNTI, and the method further includes receiving a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space.

[0138] In a fifth aspect, the value of the RNTI is equal to the G-RNTI and the UE does not receive a configuration of a PDCCH DMRS scrambling ID for the CORESET associated with the search space.

[0139] In a sixth aspect, the process 500 includes receiving a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space, where a value of the RNTI is equal to the G-RNTI based on receiving the configuration of the PDCCH DMRS scrambling ID.

[0140] In a seventh aspect, the UE does not receive a PDCCH DMRS scrambling ID configuration for a CORESET associated with the search space, and the value of the RNTI is equal to zero based on the UE not receiving a PDCCH DMRS scrambling ID configuration.

[0141] In an eighth aspect, the process 500 includes receiving a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space and receiving a dedicated configuration indication to configure the search space, where a value of the RNTI is equal to the G-RNTI based on the configuration of the PDCCH DMRS scrambling ID and receiving the dedicated configuration indication.

[0142] In a ninth aspect, alone or in combination with the eighth aspect, receiving the dedicated configuration indication includes receiving a dedicated RRC message.

[0143] In a tenth aspect, alone or in combination with one or more of the eighth to ninth aspects, receiving the dedicated configuration indication includes receiving an RRC message indicating the dedicated parameters.

[0144] In an eleventh aspect, the value of the RNTI is equal to zero based on a determination that the UE has not received a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space and a dedicated configuration indication to configure the search space.

[0145] In a twelfth aspect, the process 500 includes receiving a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space, where monitoring the search space includes monitoring the search space only in an RRC connected state, and a value of the RNTI is equal to the G-RNTI based on receiving the configuration of the PDCCH DMRS scrambling ID and monitoring the search space only in the RRC connected state.

[0146] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the value of the RNTI is equal to zero based on a determination that the UE has not received a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space and a determination that the search space is not monitored only in a radio resource control connected state.

[0147] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the at least one MBS PDCCH communication includes a DCI transmission that schedules the MBS PDSCH.

[0148] In a fifteenth aspect, alone or in combination with the fourteenth aspect, the value of the RNTI is equal to zero based on a determination that the DCI format of the DCI transmission is DCI format 1_0.

[0149] The sixteenth aspect, alone or in combination with the fifteenth aspect, is that the value of the RNTI is equal to the G-RNTI based on a determination that the DCI format of the DCI transmission is not DCI format 1_0.

[0150] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, at least one MBS PDCCH communication schedules a plurality of MBS PDSCH communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI among a plurality of G-RNTIs including the G-RNTI.

[0151] In aspect 18, alone or in combination with aspect 17, the value of the RNTI is equal to the G-RNTI, and the at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to the at least one additional G-RNTI of the multiple G-RNTIs.

[0152] In aspect 19, alone or in combination with aspect 17, at least one additional payload is scrambled according to a PDCCH payload scrambling sequence based on at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to the value of the RNTI.

[0153] In a twentieth aspect, alone or in combination with the nineteenth aspect, the value of the RNTI is equal to a designated G-RNTI among the plurality of G-RNTIs.

[0154] In a 21st aspect, alone or in combination with one or more of the 19th to 20th aspects, multiple G-RNTIs are configured using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0155] In a twenty-second aspect, alone or in combination with one or more of the nineteenth to twenty-first aspects, the value of the RNTI is equal to the G-RNTI mapped to the multicast service.

[0156] In a twenty-third aspect, alone or in combination with the twenty-second aspect, the multicast service includes a specified multicast service ID of a plurality of multicast service IDs.

[0157] In a twenty-fourth aspect, alone or in combination with the nineteenth aspect, the value of the RNTI includes a configurable dedicated value.

[0158] In a twenty-fifth aspect, alone or in combination with one or more of the seventeenth to twenty-fourth aspects, the at least one MBS PDCCH communication includes a plurality of MBS PDCCH communications.

[0159] In a twenty-sixth aspect, alone or in combination with one or more of the nineteenth through twenty-fifth aspects, the process 500 includes monitoring at least one additional search space for at least one additional MBS PDCCH that schedules at least one additional MBS PDSCH communication associated with at least one additional G-RNTI of the plurality of G-RNTIs.

[0160] In a twenty-seventh aspect, alone or in combination with one or more of the first to twenty-sixth aspects, the process 500 includes receiving an RRC configuration indicating a mapping between a search space and a G-RNTI.

[0161] In a twenty-eighth aspect, alone or in combination with one or more of the first through third aspects, at least one MBS PDCCH communication includes a CRC scrambled using the G-RNTI.

[0162] In a 29th aspect, alone or in combination with the 28th aspect, at least one MBS PDCCH communication schedules a plurality of MBS PDSCH communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding Group RNTI (G-RNTI) among a plurality of G-RNTIs including the G-RNTI.

[0163] In a 30th aspect, alone or in combination with the 29th aspect, at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on at least one additional value of G-RNTI, and the at least one additional value of RNTI is equal to at least one additional G-RNTI of the multiple G-RNTIs.

[0164] In a 31st aspect, alone or in combination with one or more of the 29th or 30th aspects, at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on at least one additional value of the RNTI, and the at least one additional value of the G-RNTI is equal to the value of the G-RNTI.

[0165] In a thirty-second aspect, alone or in combination with one or more of the twenty-ninth to thirty-first aspects, the value of the G-RNTI is equal to a designated G-RNTI among the plurality of G-RNTIs.

[0166] In a 33rd aspect, alone or in combination with one or more of the 29th to 32nd aspects, multiple G-RNTIs are configured using a G-RNTI list, and the value of the G-RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0167] In a thirty-fourth aspect, alone or in combination with one or more of the twenty-ninth to thirty-third aspects, the value of the G-RNTI is equal to the G-RNTI mapped to the multicast service.

[0168] In a thirty-fifth aspect, alone or in combination with the thirty-fourth aspect, the multicast service includes a specified multicast service ID of a plurality of multicast service IDs.

[0169] 5 illustrates example blocks of process 500, in some aspects process 500 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 5. Additionally or alternatively, two or more of the blocks of process 500 may be performed in parallel.

[0170] 6 illustrates an example process 600, performed by, for example, a UE, in accordance with the present disclosure. The example process 600 is an example in which a UE (e.g., the UE 404) performs operations associated with PDCCH transmission for an MBS service.

[0171] 6, in some aspects, process 600 may include monitoring a search space associated with a PDCCH corresponding to the MBS PDSCH for at least one MBS PDCCH communication having a CCE index corresponding to a hash function based on a value of G-RNTI or RNTI equal to zero (block 610). For example, the UE (e.g., using communications manager 140 and / or receiving component 1102 shown in FIG. 11) may monitor a search space for at least one MBS PDCCH communication having a CCE index corresponding to a hash function based on a value of G-RNTI or RNTI equal to zero, as described above.

[0172] 6, in some aspects, the process 600 may include receiving at least one MBS PDCCH communication (block 620). For example, the UE may receive the at least one MBS PDCCH communication (e.g., using the communications manager 140 and / or the receiving component 1102 shown in FIG. 11), as described above.

[0173] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein. In a first aspect, the value of the RNTI is equal to zero.

[0174] In a second aspect, the value of the RNTI is equal to the G-RNTI.

[0175] In a third aspect, the process 600 includes receiving an indication of an RRC parameter that enables the RNTI to be equal to the G-RNTI, where the value of the RNTI is equal to the G-RNTI based on receiving the indication of the RRC parameter.

[0176] In a fourth aspect, the value of the RNTI is equal to zero based on a determination that the UE has not received an indication of a radio resource control parameter that enables the RNTI to be equal to the G-RNTI.

[0177] In a fifth aspect, the process 600 includes receiving a dedicated configuration indication to configure the search space, where the value of the RNTI is equal to the G-RNTI based on receiving the dedicated configuration indication.

[0178] In a sixth aspect, alone or in combination with the fifth aspect, receiving the dedicated configuration indication includes receiving a dedicated RRC message.

[0179] In a seventh aspect, alone or in combination with one or more of the fifth to sixth aspects, receiving the dedicated configuration indication includes receiving an RRC message indicating the dedicated parameters.

[0180] In an eighth aspect, the value of the RNTI is equal to zero based on a determination that the UE has not received a dedicated configuration indication to configure the search space.

[0181] In a ninth aspect, monitoring the search space includes monitoring the search space only in an RRC connected state, and the value of the RNTI is equal to the G-RNTI based on monitoring the search space only in the RRC connected state.

[0182] In a tenth aspect, the value of the RNTI is equal to zero based on a determination that the search space is not monitored only in the RRC connected state.

[0183] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the at least one MBS PDCCH communication includes a DCI transmission that schedules the MBS PDSCH.

[0184] In a twelfth aspect, alone or in combination with the eleventh aspect, the value of the RNTI is equal to zero based on a determination that the DCI format of the DCI transmission is DCI format 1_0.

[0185] In a thirteenth aspect, alone or in combination with the eleventh aspect, the value of the RNTI is equal to the G-RNTI based on a determination that the DCI format of the DCI transmission is not DCI format 1_0.

[0186] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, at least one MBS PDCCH communication schedules a plurality of MBS PDSCH communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI among a plurality of G-RNTIs including the G-RNTI.

[0187] In a fifteenth aspect, alone or in combination with the fourteenth aspect, the value of the RNTI is equal to a G-RNTI, the at least one additional CCE index corresponds to at least one additional hash function based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI among the multiple G-RNTIs.

[0188] In a sixteenth aspect, alone or in combination with the fourteenth aspect, at least one additional hash function is based on at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to the value of the RNTI.

[0189] In a seventeenth aspect, alone or in combination with the sixteenth aspect, the value of the RNTI is equal to a designated G-RNTI among the plurality of G-RNTIs.

[0190] In an 18th aspect, alone or in combination with one or more of the 16th to 17th aspects, multiple G-RNTIs are configured using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0191] In a nineteenth aspect, alone or in combination with one or more of the sixteenth to eighteenth aspects, the value of the RNTI is equal to the G-RNTI mapped to the multicast service.

[0192] In a twentieth aspect, alone or in combination with the nineteenth aspect, the multicast service includes a specified multicast service ID of a plurality of multicast service IDs.

[0193] In a twenty-first aspect, alone or in combination with the sixteenth aspect, the value of the RNTI comprises a configurable dedicated value.

[0194] In a twenty-second aspect, alone or in combination with one or more of the fourteenth to twenty-first aspects, the at least one MBS PDCCH communication includes a plurality of MBS PDCCH communications.

[0195] In a twenty-third aspect, alone or in combination with one or more of the fourteenth through twenty-second aspects, the process 600 includes monitoring at least one additional search space for at least one additional MBS PDCCH that schedules at least one additional MBS PDSCH communication associated with at least one additional G-RNTI of the plurality of G-RNTIs.

[0196] In a twenty-fourth aspect, alone or in combination with one or more of the first to twenty-third aspects, the process 600 includes receiving an RRC configuration indicating a mapping between a search space and a G-RNTI.

[0197] 6 illustrates example blocks of process 600, in some aspects process 600 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 6. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0198] 7 illustrates an example process 700, performed by, for example, a UE, in accordance with the present disclosure. The example process 700 is an example in which a UE (e.g., the UE 404) performs operations associated with PDCCH transmission for an MBS service.

[0199] 7, in some aspects, process 700 may include receiving an MBS configuration that configures multiple G-RNTIs for a cell (block 710). For example, the UE may receive (e.g., using the communications manager 140 and / or the receiving component 1102 shown in FIG. 11) an MBS configuration that configures multiple G-RNTIs for a cell, as described above.

[0200] 7, in some aspects, the process 700 may include monitoring, for the at least one MBS PDCCH communication that schedules the at least one MBS PDSCH communication of the plurality of MBS PDSCH communications, at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell based on the MBS configuration (block 720). For example, the UE (e.g., using the communications manager 140 and / or the receiving component 1102 shown in FIG. 11) may monitor, as described above, for the at least one MBS PDCCH communication that schedules the at least one MBS PDSCH communication of the plurality of MBS PDSCH communications, at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell based on the MBS configuration.

[0201] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0202] In a first aspect, each MBS PDSCH communication of the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI of the plurality of G-RNTIs.

[0203] In a second aspect, alone or in combination with the first aspect, at least one G-RNTI of the plurality of G-RNTIs includes a value of an RNTI associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a CCE index, or a CRC scrambling sequence.

[0204] In a third aspect, alone or in combination with the second aspect, the value of the RNTI is equal to at least one G-RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI of the plurality of G-RNTIs.

[0205] In a fourth aspect, alone or in combination with the second aspect, at least one additional value of the RNTI is equal to the value of the RNTI.

[0206] In a fifth aspect, alone or in combination with the fourth aspect, the value of the RNTI is equal to a designated G-RNTI among the plurality of G-RNTIs.

[0207] In a sixth aspect, alone or in combination with one or more of the fourth to fifth aspects, multiple G-RNTIs are configured using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0208] In a seventh aspect, either alone or in combination with one or more of the third to sixth aspects, at least one of the multiple G-RNTIs is mapped to a multicast service.

[0209] In an eighth aspect, alone or in combination with the seventh aspect, the multicast service includes a specified multicast service ID of a plurality of multicast service IDs.

[0210] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the process 700 includes receiving a configuration indicating a configurable dedicated value of the RNTI, the configurable dedicated value of the RNTI being associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a CCE index, or a CRC scrambling sequence.

[0211] In a tenth aspect, monitoring at least one search space includes monitoring one search space.

[0212] In an eleventh aspect, monitoring at least one search space includes monitoring a plurality of search spaces.

[0213] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the process 700 includes receiving an RRC configuration indicating a mapping between at least one search space and at least one G-RNTI of a plurality of G-RNTIs.

[0214] 7 illustrates example blocks of process 700, in some aspects process 700 may include additional blocks, fewer blocks, different blocks, or blocks in a different arrangement than the blocks illustrated in FIG 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0215] 8 illustrates an example process 800 implemented, for example, by a base station, in accordance with the present disclosure. The example process 800 is an example in which a base station (e.g., network node 402) implements operations associated with PDCCH transmission for an MBS service.

[0216] 8, in some aspects, process 800 may include transmitting an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of G-RNTI or RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH (block 810). For example, the base station may be configured to transmit (e.g., using communications manager 150 and / or transmitting component 1204 shown in FIG. 12) an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of G-RNTI or RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH, as described above.

[0217] 8, in some aspects, process 800 may include transmitting at least one MBS PDCCH communication based at least in part on the configuration (block 820). For example, the base station (e.g., using the communications manager 150 and / or the transmitting component 1204 shown in FIG. 12) may transmit at least one MBS PDCCH communication based at least in part on the configuration, as described above.

[0218] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0219] In a first aspect, the value of the RNTI is equal to zero, and the method further includes transmitting a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space.

[0220] In a second aspect, the value of RNTI is equal to zero and the base station does not transmit a configuration of the PDCCH DMRS scrambling ID for the CORESET associated with the search space.

[0221] In a third aspect, the value of RNTI is equal to zero and the PDCCH DMRS scrambling ID is not supported for the control resource set associated with the search space.

[0222] In a fourth aspect, the value of the RNTI is equal to the G-RNTI, and the method further includes transmitting a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space.

[0223] In a fifth aspect, the value of the RNTI is equal to the G-RNTI, and the base station does not transmit a configuration of the PDCCH DMRS scrambling ID for the CORESET associated with the search space.

[0224] In a sixth aspect, the process 800 includes transmitting a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space, where a value of the RNTI is equal to the G-RNTI based on transmitting the configuration of the PDCCH DMRS scrambling ID.

[0225] In a seventh aspect, the base station does not transmit a PDCCH DMRS scrambling ID configuration for the CORESET associated with the search space, and the value of the RNTI is equal to zero based on the base station not transmitting a PDCCH DMRS scrambling ID configuration.

[0226] In an eighth aspect, the process 800 includes transmitting a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space and transmitting a dedicated configuration indication to configure the search space, where a value of the RNTI is equal to the G-RNTI based on the configuration of the PDCCH DMRS scrambling ID and transmitting the dedicated configuration indication.

[0227] In a ninth aspect, alone or in combination with the eighth aspect, transmitting the dedicated configuration indication includes transmitting a dedicated RRC message.

[0228] In a tenth aspect, alone or in combination with one or more of the eighth to ninth aspects, transmitting the dedicated configuration indication includes transmitting an RRC message indicating the dedicated parameters.

[0229] In an eleventh aspect, the value of the RNTI is equal to zero based on a determination that the base station has not transmitted a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space and a dedicated configuration indication to configure the search space.

[0230] In a twelfth aspect, 800 includes transmitting to the UE a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space, and transmitting a monitoring configuration indicating that the UE should monitor the search space only in an RRC connected state, where a value of the RNTI is equal to the G-RNTI based on the configuration of the PDCCH DMRS scrambling ID and transmitting the monitoring configuration.

[0231] In a thirteenth aspect, the value of the RNTI is equal to zero based on a determination that the base station has not transmitted a PDCCH DMRS scrambling ID configuration for the CORESET associated with the search space and a determination that the search space is not monitored only in the RRC connected state.

[0232] In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the at least one MBS PDCCH communication includes a DCI transmission that schedules an MBS physical downlink shared channel.

[0233] In a fifteenth aspect, alone or in combination with the fourteenth aspect, the value of the RNTI is equal to zero based on a determination that the DCI format of the DCI transmission is DCI format 1_0.

[0234] In a sixteenth aspect, alone or in combination with the fourteenth aspect, the value of the RNTI is equal to the G-RNTI based on a determination that the DCI format of the DCI transmission is not DCI format 1_0.

[0235] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, at least one MBS PDCCH communication schedules a plurality of MBS PDSCH communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI among a plurality of G-RNTIs including the G-RNTI.

[0236] In an 18th aspect, alone or in combination with the 17th aspect, the value of the RNTI is equal to a G-RNTI, and the at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI of the multiple G-RNTIs.

[0237] In a nineteenth aspect, alone or in combination with the seventeenth aspect, at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to the value of the RNTI.

[0238] In a twentieth aspect, alone or in combination with the nineteenth aspect, the value of the RNTI is equal to a designated G-RNTI among the plurality of G-RNTIs.

[0239] In a 21st aspect, alone or in combination with one or more of the 19th to 20th aspects, multiple G-RNTIs are configured using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0240] In a twenty-second aspect, alone or in combination with one or more of the nineteenth to twenty-first aspects, the value of the RNTI is equal to the G-RNTI mapped to the multicast service.

[0241] In a twenty-third aspect, alone or in combination with the twenty-second aspect, the multicast service includes a specified multicast service ID of a plurality of multicast service IDs.

[0242] In a twenty-fourth aspect, alone or in combination with the nineteenth aspect, the value of the RNTI includes a configurable dedicated value.

[0243] In a twenty-fifth aspect, alone or in combination with one or more of the seventeenth to twenty-fourth aspects, the at least one MBS PDCCH communication includes a plurality of MBS PDCCH communications.

[0244] In a twenty-sixth aspect, alone or in combination with one or more of the seventeenth to twenty-fifth aspects, the process 800 includes transmitting a monitoring configuration indicating that the UE should monitor at least one additional search space for at least one additional MBS PDCCH scheduling at least one additional MBS PDSCH communication associated with the at least one additional G-RNTI of the plurality of G-RNTIs.

[0245] In a 27th aspect, alone or in combination with one or more of the 1st to 26th aspects, the process 800 includes transmitting an RRC configuration indicating a mapping between the search space and the G-RNTI.

[0246] In a twenty-eighth aspect, alone or in combination with one or more of the first through third aspects, at least one MBS PDCCH communication includes a CRC scrambled using the G-RNTI.

[0247] In a 29th aspect, alone or in combination with the 28th aspect, at least one MBS PDCCH communication schedules a plurality of MBS PDSCH communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding Group RNTI (G-RNTI) among a plurality of G-RNTIs including the G-RNTI.

[0248] In a 30th aspect, alone or in combination with the 29th aspect, at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on at least one additional value of G-RNTI, and the at least one additional value of G-RNTI is equal to at least one additional G-RNTI of the multiple G-RNTIs.

[0249] In a 31st aspect, alone or in combination with one or more of the 29th or 30th aspects, at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on at least one additional value of the RNTI, and the at least one additional value of the G-RNTI is equal to the value of the G-RNTI.

[0250] In a thirty-second aspect, alone or in combination with one or more of the twenty-ninth to thirty-first aspects, the value of the G-RNTI is equal to a designated G-RNTI among the plurality of G-RNTIs.

[0251] In a 33rd aspect, alone or in combination with one or more of the 29th to 32nd aspects, multiple G-RNTIs are configured using a G-RNTI list, and the value of the G-RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0252] In a thirty-fourth aspect, alone or in combination with one or more of the twenty-ninth to thirty-third aspects, the value of the G-RNTI is equal to the G-RNTI mapped to the multicast service.

[0253] In a thirty-fifth aspect, alone or in combination with the thirty-fourth aspect, the multicast service includes a specified multicast service ID of a plurality of multicast service IDs.

[0254] 8 illustrates example blocks of process 800, in some aspects process 800 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0255] 9 illustrates an example process 900 implemented, for example, by a base station, in accordance with the present disclosure. The example process 900 is an example in which a base station (e.g., network node 402) performs operations associated with PDCCH transmission for an MBS service.

[0256] 9, in some aspects, process 900 may include transmitting an MBS configuration indicating a PDCCH hash function based on a value of G-RNTI or RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH (block 910). For example, the base station may be configured to transmit (e.g., using communications manager 150 and / or transmitting component 1204 shown in FIG. 12) an MBS configuration indicating a PDCCH hash function based on a value of G-RNTI or RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH, as described above.

[0257] 9, in some aspects, the process 900 may include transmitting at least one MBS PDCCH communication based at least in part on the configuration (block 920). For example, the base station (e.g., using the communications manager 150 and / or the transmitting component 1204 shown in FIG. 12) may transmit the at least one MBS PDCCH communication based at least in part on the configuration, as described above.

[0258] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0259] In a first aspect, the value of the RNTI is equal to zero.

[0260] In a second aspect, the value of the RNTI is equal to the G-RNTI.

[0261] In a third aspect, the process 900 includes sending an indication of an RRC parameter that enables the RNTI to be equal to the G-RNTI, where the value of the RNTI is equal to the G-RNTI based on sending the indication of the RRC parameter.

[0262] In a fourth aspect, the value of the RNTI is equal to zero based on a determination that the base station has not transmitted an indication of an RRC parameter that enables the RNTI to be equal to the G-RNTI.

[0263] In a fifth aspect, the process 900 includes sending a dedicated configuration indication to configure the search space, where the value of the RNTI is equal to the G-RNTI based on sending the dedicated configuration indication.

[0264] In a sixth aspect, alone or in combination with the fifth aspect, transmitting the dedicated configuration indication includes transmitting a dedicated RRC message.

[0265] In a seventh aspect, alone or in combination with one or more of the fifth to sixth aspects, transmitting the dedicated configuration indication includes transmitting an RRC message indicating the dedicated parameters.

[0266] In an eighth aspect, the value of the RNTI is equal to zero based on a determination that the base station has not transmitted a dedicated configuration indication to configure the search space.

[0267] In a ninth aspect, a monitoring configuration indicating that the UE should monitor the search space only in an RRC connected state is transmitted, and the value of the RNTI is equal to the G-RNTI based on the monitoring configuration.

[0268] In a tenth aspect, the value of the RNTI is equal to zero based on a determination that the search space is not monitored only in the RRC connected state.

[0269] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the at least one MBS PDCCH communication includes a DCI transmission that schedules the MBS PDSCH.

[0270] In a twelfth aspect, alone or in combination with the eleventh aspect, the value of the RNTI is equal to zero based on a determination that the DCI format of the DCI transmission is DCI format 1_0.

[0271] In a thirteenth aspect, alone or in combination with the eleventh aspect, the value of the RNTI is equal to the G-RNTI based on a determination that the DCI format of the DCI transmission is not DCI format 1_0.

[0272] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, at least one MBS PDCCH communication schedules a plurality of MBS PDSCH communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI among a plurality of G-RNTIs including the G-RNTI.

[0273] In a fifteenth aspect, alone or in combination with the fourteenth aspect, the value of the RNTI is equal to a G-RNTI, the at least one additional CCE index corresponds to at least one additional hash function based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI among the multiple G-RNTIs.

[0274] In a sixteenth aspect, alone or in combination with the fourteenth aspect, at least one additional hash function is based on at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to the value of the RNTI.

[0275] In a seventeenth aspect, alone or in combination with the sixteenth aspect, the value of the RNTI is equal to a designated G-RNTI among the plurality of G-RNTIs.

[0276] In an 18th aspect, alone or in combination with one or more of the 16th to 17th aspects, multiple G-RNTIs are configured using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0277] In a nineteenth aspect, alone or in combination with one or more of the sixteenth to eighteenth aspects, the value of the RNTI is equal to the G-RNTI mapped to the multicast service.

[0278] In a twentieth aspect, alone or in combination with the nineteenth aspect, the multicast service includes a specified multicast service ID of a plurality of multicast service IDs.

[0279] In a twenty-first aspect, alone or in combination with the seventeenth aspect, the value of the RNTI comprises a configurable dedicated value.

[0280] In a twenty-second aspect, alone or in combination with one or more of the fifteenth to twenty-first aspects, the at least one MBS PDCCH communication includes a plurality of MBS PDCCH communications.

[0281] In a twenty-third aspect, alone or in combination with one or more of the fifteenth to twenty-second aspects, the process 900 includes transmitting a monitoring configuration indicating that the UE should monitor at least one additional search space for at least one additional MBS PDCCH scheduling at least one additional MBS PDSCH communication associated with the at least one additional G-RNTI of the plurality of G-RNTIs.

[0282] In a twenty-fourth aspect, alone or in combination with one or more of the first to twenty-third aspects, the process 900 includes transmitting an RRC configuration indicating a mapping between a search space and a G-RNTI.

[0283] 9 illustrates example blocks of process 900, in some aspects process 900 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 9. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0284] 10 illustrates an example process 1000 implemented, for example, by a base station, in accordance with the present disclosure. The example process 1000 is an example in which a base station (e.g., network node 402) implements operations associated with PDCCH transmission for an MBS service.

[0285] 10, in some aspects, process 1000 may include transmitting an MBS configuration that configures multiple G-RNTIs for the cell (block 1010). For example, the base station may transmit (e.g., using the communications manager 150 and / or the transmitting component 1204 shown in FIG. 12) an MBS configuration that configures multiple G-RNTIs for the cell, as described above.

[0286] 10, in some aspects, the process 1000 may include transmitting at least one MBS PDCCH communication that schedules the at least one MBS PDSCH communication of the plurality of MBS PDSCH communications based on the MBS configuration and using at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell (block 1020). For example, the base station (e.g., using the communications manager 150 and / or the transmitting component 1204 shown in FIG. 12) may transmit at least one MBS PDCCH communication that schedules the at least one MBS PDSCH communication of the plurality of MBS PDSCH communications based on the MBS configuration and using at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell, as described above.

[0287] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0288] In a first aspect, each MBS PDSCH communication of the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI of the plurality of G-RNTIs.

[0289] In a second aspect, alone or in combination with the first aspect, at least one G-RNTI of the plurality of G-RNTIs includes a value of an RNTI associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a CCE index, or a CRC scrambling sequence.

[0290] In a third aspect, the value of the RNTI is equal to at least one G-RNTI and the at least one additional value of the RNTI is equal to at least one additional G-RNTI of the plurality of G-RNTIs.

[0291] In a fourth aspect, the at least one additional value of the RNTI is equal to the value of the RNTI.

[0292] In a fifth aspect, alone or in combination with the fourth aspect, the value of the RNTI is equal to a designated G-RNTI among the plurality of G-RNTIs.

[0293] In a sixth aspect, alone or in combination with one or more of the fourth to fifth aspects, multiple G-RNTIs are configured using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0294] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, at least one of the multiple G-RNTIs is mapped to a multicast service.

[0295] In an eighth aspect, alone or in combination with the seventh aspect, the multicast service includes a specified multicast service ID of a plurality of multicast service IDs.

[0296] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the process 1000 includes transmitting a configuration indicating a configurable dedicated value of the RNTI, the configurable dedicated value of the RNTI being associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a CCE index, or a CRC scrambling sequence.

[0297] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the process 1000 includes transmitting a monitoring configuration indicating that the UE should monitor at least one search space, including monitoring one search space.

[0298] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the process 1000 includes transmitting a monitoring configuration indicating that the UE should monitor at least one search space, including monitoring multiple search spaces.

[0299] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the process 1000 includes transmitting an RRC configuration indicating a mapping between at least one search space and at least one G-RNTI of a plurality of G-RNTIs.

[0300] 10 illustrates example blocks of process 1000, in some aspects process 1000 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 10. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0301] 11 is a diagram of an example apparatus 1100 for wireless communication. The apparatus 1100 may be a UE, or a UE may include the apparatus 1100. In some aspects, the apparatus 1100 includes a receiving component 1102 and a transmitting component 1104, which may communicate with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using the receiving component 1102 and the transmitting component 1104. As further shown, the apparatus 1100 may include a communications manager 140.

[0302] In some aspects, the apparatus 1100 may be configured to perform one or more operations described herein with respect to FIG. 4. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as process 500 of FIG. 5, process 600 of FIG. 6, process 700 of FIG. 7, or a combination thereof. In some aspects, the apparatus 1100 and / or one or more components illustrated in FIG. 11 may include one or more components of a UE described in connection with FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 11 may be implemented in one or more components described in connection with FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0303] The receiving component 1102 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1106. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a UE as described in connection with FIG. 2.

[0304] The transmitting component 1104 may transmit a communication, such as a reference signal, control information, a data communication, or a combination thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate a communication and provide the generated communication to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and may transmit the processed signal to the device 1106. In some aspects, the transmitting component 1104 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of a UE as described in connection with FIG. 2. In some aspects, the transmitting component 1104 may be collocated with the receiving component 1102 in a transceiver.

[0305] The communications manager 140 and / or the receiving component 1102 may be configured to monitor a search space associated with a PDCCH corresponding to the MBS PDSCH for at least one MBS PDCCH communication having a payload scrambled according to a PDCCH payload scrambling sequence based on a value of the G-RNTI or an RNTI equal to zero. The receiving component 1102 may receive the at least one MBS PDCCH communication. In some aspects, the communications manager 140 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof of a UE as described in connection with FIG. 2. In some aspects, the communications manager 140 may include the receiving component 1102 and / or the transmitting component 1104.

[0306] The receiving component 1102 may receive a configuration of a PDCCH DMRS scrambling ID for a control resource set associated with the search space, where the value of the RNTI is equal to the G-RNTI based on receiving the configuration of the PDCCH DMRS scrambling ID. The receiving component 1102 may receive a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space.

[0307] The receiving component 1102 may receive a dedicated configuration indication to configure the search space, where the value of the RNTI is equal to the G-RNTI based on the configuration of the PDCCH DMRS scrambling ID and receiving the dedicated configuration indication.

[0308] The receiving component 1102 may receive a configuration of a PDCCH DMRS scrambling ID for a CORESET associated with the search space, where monitoring the search space includes monitoring the search space only in an RRC connected state, and where a value of the RNTI is equal to the G-RNTI based on receiving the configuration of the PDCCH DMRS scrambling ID and monitoring the search space only in the RRC connected state.

[0309] The communications manager 140 and / or the receiving component 1102 may monitor at least one additional search space for at least one additional MBS PDCCH that schedules at least one additional MBS PDSCH communication associated with at least one additional G-RNTI of the plurality of G-RNTIs.

[0310] The receiving component 1102 may receive an RRC configuration indicating a mapping between a search space and a G-RNTI.

[0311] The communications manager 140 and / or the receiving component 1102 may monitor a search space associated with a PDCCH corresponding to the MBS PDSCH for at least one MBS PDCCH communication having a CCE index corresponding to a hash function based on a value of the G-RNTI or an RNTI equal to zero. The receiving component 1102 may receive the at least one MBS PDCCH communication.

[0312] The receiving component 1102 may receive an indication of an RRC parameter that enables the RNTI to be equal to the G-RNTI, where the value of the RNTI is equal to the G-RNTI based on receiving the indication of the RRC parameter.

[0313] The receiving component 1102 may receive a dedicated configuration indication to configure the search space, where the value of the RNTI is equal to the G-RNTI based on receiving the dedicated configuration indication.

[0314] The communications manager 140 and / or the receiving component 1102 may monitor at least one additional search space for at least one additional MBS PDCCH that schedules at least one additional MBS PDSCH communication associated with at least one additional G-RNTI of the plurality of G-RNTIs.

[0315] The receiving component 1102 may receive an RRC configuration indicating a mapping between a search space and a G-RNTI.

[0316] The receiving component 1102 may receive an MBS configuration that configures the multiple G-RNTIs for the cell. The communications manager 140 and / or the receiving component 1102 may monitor at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell based on the MBS configuration for at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the multiple MBS PDSCH communications.

[0317] The receiving component 1102 may receive a configuration indicating a configurable dedicated value of the RNTI, where the configurable dedicated value of the RNTI is associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a CCE index, or a CRC scrambling sequence.

[0318] The receiving component 1102 may receive a radio resource control configuration indicating a mapping between at least one search space and at least one G-RNTI of a plurality of G-RNTIs.

[0319] The number and arrangement of components shown in Figure 11 are provided as an example. In practice, there may be additional components, fewer components, different components, or a different arrangement of components compared to those shown in Figure 11. Furthermore, two or more of the components shown in Figure 11 may be implemented within a single component, or a single component shown in Figure 11 may be implemented as multiple distributed components. Additionally or alternatively, a set of components shown in Figure 11 may perform one or more functions that are described as being performed by another set of components shown in Figure 11.

[0320] 12 is a diagram of an example apparatus 1200 for wireless communication. The apparatus 1200 may be a base station, or a base station may include the apparatus 1200. In some aspects, the apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which may communicate with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using the receiving component 1202 and the transmitting component 1204. As further shown, the apparatus 1200 may include a communications manager 150.

[0321] In some aspects, the apparatus 1200 may be configured to perform one or more operations described herein in conjunction with FIG. 4. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as process 800 of FIG. 8, process 900 of FIG. 9, process 1000 of FIG. 10, or a combination thereof. In some aspects, the apparatus 1200 and / or one or more components illustrated in FIG. 12 may include one or more components of a base station described in conjunction with FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 12 may be implemented within one or more components described in conjunction with FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the functions or operations of the component.

[0322] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a base station as described in connection with FIG.

[0323] The transmitting component 1204 may transmit a communication, such as a reference signal, control information, a data communication, or a combination thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate a communication and provide the generated communication to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and may transmit the processed signal to the device 1206. In some aspects, the transmitting component 1204 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of a base station as described in connection with FIG. 2. In some aspects, the transmitting component 1204 may be collocated with the receiving component 1202 in a transceiver.

[0324] The communications manager 150 and / or the transmitting component 1204 may generate and transmit an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of the G-RNTI or an RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH. The transmitting component 1204 may transmit at least one MBS PDCCH communication based at least in part on the configuration. In some aspects, the communications manager 150 may include one or more antennas, a modem, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof of a base station as described in connection with FIG. 2. In some aspects, the communications manager 150 may include the receiving component 1202 and / or the transmitting component 1204.

[0325] The transmitting component 1204 may transmit a configuration of a PDCCH DMRS scrambling ID for the control resource set associated with the search space, where a value of the RNTI is equal to the G-RNTI based on transmitting the configuration of the PDCCH DMRS scrambling ID.

[0326] The transmitting component 1204 may transmit the configuration of the PDCCH DMRS scrambling ID for the CORESET associated with the search space.

[0327] The transmitting component 1204 may send a dedicated configuration indication to configure the search space, where the value of the RNTI is equal to the G-RNTI based on the configuration of the PDCCH DMRS scrambling ID and sending the dedicated configuration indication.

[0328] The transmitting component 1204 may transmit the configuration of the PDCCH DMRS scrambling ID for the CORESET associated with the search space to the UE.

[0329] The transmitting component 1204 may transmit a monitoring configuration indicating that the UE should monitor the search space only in the RRC connected state, where the value of the RNTI is equal to the G-RNTI based on the configuration of the PDCCH DMRS scrambling ID and transmitting the monitoring configuration.

[0330] The transmitting component 1204 may transmit a monitoring configuration indicating that the UE should monitor at least one additional search space for at least one additional MBS PDCCH scheduling at least one additional MBS PDSCH communication associated with the at least one additional G-RNTI of the plurality of G-RNTIs.

[0331] The transmitting component 1204 may transmit a radio resource control configuration indicating a mapping between the search space and the G-RNTI.

[0332] The transmitting component 1204 may transmit an MBS configuration indicating a PDCCH hashing function based on a value of the G-RNTI or an RNTI equal to zero for a search space associated with a PDCCH corresponding to the MBS PDSCH. The transmitting component 1204 may transmit at least one MBS PDCCH communication based at least in part on the configuration.

[0333] The transmitting component 1204 may transmit an indication of an RRC parameter that enables the RNTI to be equal to the G-RNTI, where the value of the RNTI is equal to the G-RNTI based on transmitting the indication of the RRC parameter.

[0334] The transmitting component 1204 may transmit a dedicated configuration indication to configure the search space, where the value of the RNTI is equal to the G-RNTI based on transmitting the dedicated configuration indication.

[0335] The transmitting component 1204 may transmit a monitoring configuration indicating that the UE should monitor at least one additional search space for at least one additional MBS PDCCH scheduling at least one additional MBS PDSCH communication associated with the at least one additional G-RNTI of the plurality of G-RNTIs.

[0336] The transmitting component 1204 may transmit a radio resource control configuration indicating a mapping between the search space and the G-RNTI.

[0337] The transmitting component 1204 may transmit an MBS configuration that configures the multiple G-RNTIs for the cell. The transmitting component 1204 may transmit at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the multiple MBS PDSCH communications based on the MBS configuration and using at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell.

[0338] The transmitting component 1204 may transmit a configuration indicating a configurable dedicated value of the RNTI, the configurable dedicated value of the RNTI being associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a CCE index, or a CRC scrambling sequence.

[0339] The transmitting component 1204 may transmit a monitoring configuration indicating that the UE should monitor at least one search space, including monitoring one search space.

[0340] The transmitting component 1204 may transmit a monitoring configuration indicating that the UE should monitor at least one search space, including monitoring multiple search spaces.

[0341] The transmitting component 1204 may transmit a radio resource control configuration indicating a mapping between the at least one search space and at least one G-RNTI of the plurality of G-RNTIs.

[0342] The number and arrangement of components shown in Figure 12 are provided as an example. In practice, there may be additional components, fewer components, different components, or a different arrangement of components compared to those shown in Figure 12. Furthermore, two or more of the components shown in Figure 12 may be implemented within a single component, or a single component shown in Figure 12 may be implemented as multiple distributed components. Additionally or alternatively, a set of components shown in Figure 12 may perform one or more functions that are described as being performed by another set of components shown in Figure 12.

[0343] The following provides a summary of several aspects of the disclosure. Aspect 1: A method of wireless communication implemented by a user equipment (UE), comprising: monitoring a search space associated with a PDCCH corresponding to a MBS physical downlink shared channel (PDSCH) for at least one Multicast / Broadcast System (MBS) PDCCH communication having a payload scrambled in accordance with a Physical Downlink Control Channel (PDCCH) payload scrambling sequence based on a Group RNTI (G-RNTI) or a Radio Network Temporary Identifier (RNTI) value equal to zero; and receiving the at least one MBS PDCCH communication.

[0344] Aspect 2: The method of aspect 1, wherein the value of the RNTI is equal to zero, the method further including receiving a PDCCH demodulation reference signal (DMRS) scrambling indicator configuration for a control resource set associated with the search space.

[0345] Aspect 3: The method of aspect 1, wherein the value of the RNTI is equal to zero and the UE does not receive a PDCCH demodulation reference signal (DMRS) scrambling indicator configuration for a control resource set associated with the search space.

[0346] Aspect 4: The method of aspect 1, wherein the value of the RNTI is equal to zero and a PDCCH demodulation reference signal (DMRS) scrambling identifier for the control resource set associated with the search space is not supported.

[0347] Aspect 5: The method of aspect 1, wherein the value of the RNTI is equal to the G-RNTI, and the method further includes receiving a PDCCH demodulation reference signal (DMRS) scrambling indicator configuration for a control resource set associated with the search space.

[0348] Aspect 6: The method of aspect 1, wherein the value of the RNTI is equal to the G-RNTI, and the UE does not receive a configuration of a PDCCH demodulation reference signal (DMRS) scrambling indicator for a control resource set associated with the search space.

[0349] Aspect 7: The method of aspect 1, further comprising receiving a configuration of a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) for a control resource set associated with the search space, wherein the value of the RNTI is equal to a G-RNTI based on receiving the configuration of the PDCCH DMRS scrambling ID.

[0350] Aspect 8: The method of aspect 1, wherein the UE does not receive a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) configuration for a control resource set associated with the search space, and the value of the RNTI is equal to zero based on the UE not receiving a PDCCH DMRS scrambling ID configuration.

[0351] Aspect 9: The method of aspect 1, further comprising receiving a configuration of a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) for a control resource set associated with the search space and receiving a dedicated configuration indication for configuring the search space, wherein a value of the RNTI is equal to a G-RNTI based on the configuration of the PDCCH DMRS scrambling ID and receiving the dedicated configuration indication.

[0352] Aspect 10: The method of aspect 9, wherein receiving a dedicated configuration indication includes receiving a dedicated radio resource control message.

[0353] Aspect 11: The method of any of aspects 9 or 10, wherein receiving the dedicated configuration indication includes receiving a radio resource control message indicating the dedicated parameters.

[0354] Aspect 12: The method of aspect 1, wherein the value of the RNTI is equal to zero based on a determination that the UE has not received a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) setting for a control resource set associated with the search space and a dedicated setting indication for setting the search space.

[0355] Aspect 13: The method of aspect 1, further comprising receiving a configuration of a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) for a control resource set associated with the search space, wherein monitoring the search space includes monitoring the search space only in a radio resource control (RRC) connected state, and a value of the RNTI is equal to the G-RNTI based on receiving the configuration of the PDCCH DMRS scrambling ID and monitoring the search space only in the RRC connected state.

[0356] Aspect 14: The method of aspect 1, wherein the value of the RNTI is equal to zero based on a determination that the UE has not received a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) configuration for a control resource set associated with the search space and a determination that the search space is not monitored only in a radio resource control connected state.

[0357] Example 15: The method of any of Examples 1-14, wherein the at least one MBS PDCCH communication includes a downlink control information (DCI) transmission that schedules an MBS physical downlink shared channel.

[0358] Aspect 16: The method of aspect 15, wherein the value of the RNTI is equal to zero based on a determination that the DCI format of the DCI transmission is DCI format 1_0.

[0359] Aspect 17: The method of aspect 15, wherein the value of the RNTI is equal to the G-RNTI based on a determination that the DCI format of the DCI transmission is not DCI format 1_0.

[0360] Aspect 18: The method of any of aspects 1 to 17, wherein at least one MBS PDCCH communication schedules a plurality of MBS physical downlink shared channel (PDSCH) communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI among a plurality of G-RNTIs including the G-RNTI.

[0361] Aspect 19: The method of aspect 18, wherein the value of the RNTI is equal to a G-RNTI, and the at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI among the plurality of G-RNTIs.

[0362] Aspect 20: The method of aspect 18, wherein the at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to the value of the RNTI.

[0363] Aspect 21: The method of aspect 20, wherein the value of the RNTI is equal to a designated G-RNTI among a plurality of G-RNTIs.

[0364] Aspect 22: The method of any of aspects 20 or 21, wherein the multiple G-RNTIs are configured using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0365] Aspect 23: The method according to any one of aspects 20 to 22, wherein the value of the RNTI is equal to a G-RNTI mapped to the multicast service.

[0366] Aspect 24: The method of aspect 23, wherein the multicast service includes a designated multicast service ID of a plurality of multicast service identifiers (IDs).

[0367] Aspect 25: The method of aspect 20, wherein the value of the RNTI includes a configurable dedicated value.

[0368] Example 26: The method of any of Examples 18 to 25, wherein the at least one MBS PDCCH communication includes a plurality of MBS PDCCH communications.

[0369] Example 27: The method of any of Examples 18 to 26, further comprising monitoring at least one additional search space for at least one additional MBS PDCCH that schedules at least one additional MBS PDSCH communication associated with at least one additional G-RNTI of the plurality of G-RNTIs.

[0370] Example 28: The method of any one of examples 1 to 27, further comprising receiving a radio resource control configuration indicating a mapping between a search space and a G-RNTI.

[0371] Aspect 29: A method of wireless communication implemented by a user equipment (UE), comprising: monitoring a search space associated with a PDCCH corresponding to an MBS physical downlink shared channel (PDSCH) for at least one Multicast / Broadcast System (MBS) physical downlink control channel (PDCCH) communication having a control channel element (CCE) index corresponding to a hash function based on a group RNTI (G-RNTI) or a radio network temporary identifier (RNTI) value equal to zero; and receiving the at least one MBS PDCCH communication.

[0372] Aspect 30: The method described in aspect 29, wherein the value of the RNTI is equal to zero.

[0373] Aspect 31: The method of aspect 29, wherein the value of the RNTI is equal to the G-RNTI.

[0374] Aspect 32: The method of aspect 29, further comprising receiving an indication of a radio resource control (RRC) parameter that enables the RNTI to be equal to the G-RNTI, wherein the value of the RNTI is equal to the G-RNTI based on receiving the indication of the RRC parameter.

[0375] Aspect 33: The method of aspect 29, wherein the value of the RNTI is equal to zero based on a determination that the UE has not received an indication of a radio resource control parameter that enables the RNTI to be equal to the G-RNTI.

[0376] Aspect 34: The method of aspect 29, further comprising receiving a dedicated configuration indication to configure the search space, wherein the value of the RNTI is equal to the G-RNTI based on receiving the dedicated configuration indication.

[0377] Aspect 35: The method of aspect 34, wherein receiving a dedicated configuration indication includes receiving a dedicated radio resource control message.

[0378] Aspect 36: The method of any of aspects 34 or 35, wherein receiving the dedicated configuration indication includes receiving a radio resource control message indicating the dedicated parameters.

[0379] Aspect 37: The method of aspect 29, wherein the value of the RNTI is equal to zero based on a determination that the UE has not received a dedicated configuration indication for configuring the search space.

[0380] Aspect 38: The method of aspect 29, wherein monitoring the search space includes monitoring the search space only in a radio resource control (RRC) connected state, and the value of the RNTI is equal to the G-RNTI based on monitoring the search space only in the RRC connected state.

[0381] Aspect 39: The method of aspect 29, wherein the value of the RNTI is equal to zero based on a determination that the search space is not monitored only in a radio resource control connected state.

[0382] Example 40: The method of any of examples 29-39, wherein the at least one MBS PDCCH communication includes a downlink control information (DCI) transmission that schedules an MBS physical downlink shared channel.

[0383] Aspect 41: The method of aspect 40, wherein the value of the RNTI is equal to zero based on a determination that the DCI format of the DCI transmission is DCI format 1_0.

[0384] Aspect 42: The method of aspect 40, wherein the value of the RNTI is equal to the G-RNTI based on a determination that the DCI format of the DCI transmission is not DCI format 1_0.

[0385] Aspect 43: The method of any of aspects 29 to 42, wherein at least one MBS PDCCH communication schedules a plurality of MBS physical downlink shared channel (PDSCH) communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI among a plurality of G-RNTIs including the G-RNTI.

[0386] Aspect 44: The method of aspect 43, wherein the value of the RNTI is equal to the G-RNTI, the at least one additional CCE index corresponds to at least one additional hash function based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI among the multiple G-RNTIs.

[0387] Aspect 45: The method of aspect 43, wherein the at least one additional hash function is based on at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to the value of the RNTI.

[0388] Aspect 46: The method described in aspect 45, wherein the value of the RNTI is equal to a designated G-RNTI among a plurality of G-RNTIs.

[0389] Aspect 47: A method as described in any of aspects 45 or 46, wherein multiple G-RNTIs are set using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0390] Example 48: The method according to any one of examples 45 to 47, wherein the value of the RNTI is equal to the G-RNTI mapped to the multicast service.

[0391] Aspect 49: The method of aspect 48, wherein the multicast service includes a designated multicast service ID of a plurality of multicast service identifiers (IDs).

[0392] Aspect 50: The method of aspect 45, wherein the value of the RNTI includes a configurable dedicated value.

[0393] Example 51: The method of any of examples 43 to 50, wherein the at least one MBS PDCCH communication includes a plurality of MBS PDCCH communications.

[0394] Example 52: The method of any of examples 43 to 51, further comprising monitoring at least one additional search space for at least one additional MBS PDCCH that schedules at least one additional MBS PDSCH communication associated with at least one additional G-RNTI of the plurality of G-RNTIs.

[0395] Example 53: The method of any of examples 29 to 52, further comprising receiving a radio resource control configuration indicating a mapping between a search space and a G-RNTI.

[0396] Aspect 54: A method of wireless communication implemented by a user equipment (UE), comprising: receiving a multicast / broadcast system (MBS) configuration for a cell, the MBS configuration configuring a plurality of group radio network temporary identifiers (G-RNTIs); and monitoring, based on the MBS configuration, at least one search space associated with a PDCCH corresponding to the MBS PDSCH of the cell for at least one MBS physical downlink control channel (PDCCH) communication that schedules at least one MBS PDSCH communication of a plurality of MBS PDSCH communications.

[0397] Example 55: The method of example 54, wherein each MBS PDSCH communication of the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI of the plurality of G-RNTIs.

[0398] Aspect 56: A method as described in any of aspects 54 or 55, wherein at least one G-RNTI of the plurality of G-RNTIs includes a value of an RNTI associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a control channel element index, or a cyclic redundancy check scrambling sequence.

[0399] Aspect 57: The method of aspect 56, wherein the value of the RNTI is equal to at least one G-RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI of the plurality of G-RNTIs.

[0400] Aspect 58: The method of aspect 56, wherein at least one additional value of the RNTI is equal to the value of the RNTI.

[0401] Aspect 59: The method described in aspect 58, wherein the value of the RNTI is equal to a designated G-RNTI among a plurality of G-RNTIs.

[0402] Aspect 60: A method as described in any of aspects 58 or 59, wherein multiple G-RNTIs are set using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0403] Example 61: The method of any of examples 56 to 60, wherein at least one of the plurality of G-RNTIs is mapped to a multicast service.

[0404] Aspect 62: The method of aspect 61, wherein the multicast service includes a designated multicast service ID among a plurality of multicast service identifiers (IDs).

[0405] Aspect 63: A method as described in any of aspects 54 to 62, further comprising receiving a configuration indicating a configurable dedicated value of the RNTI, wherein the configurable dedicated value of the RNTI is associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a control channel element index, or a cyclic redundancy check scrambling sequence.

[0406] Aspect 64: The method of aspect 54, wherein monitoring at least one search space includes monitoring one search space.

[0407] Aspect 65: The method of aspect 54, wherein monitoring at least one search space includes monitoring a plurality of search spaces.

[0408] Example 66: The method of any of examples 54 to 65, further comprising receiving a radio resource control configuration indicating a mapping between at least one search space and at least one G-RNTI among a plurality of G-RNTIs.

[0409] Aspect 67: A method of wireless communication implemented by a base station, comprising: transmitting an MBS configuration indicating a physical downlink control channel (PDCCH) payload scrambling sequence based on a group RNTI (G-RNTI) or a radio network temporary identifier (RNTI) value equal to zero for a search space associated with a physical downlink control channel (PDCCH) corresponding to a multicast / broadcast system (MBS) physical downlink shared channel (PDSCH); and transmitting at least one MBS PDCCH communication based at least in part on the configuration.

[0410] Aspect 68: The method of aspect 67, wherein the value of the RNTI is equal to zero, the method further comprising transmitting a PDCCH demodulation reference signal (DMRS) scrambling identifier configuration for a control resource set associated with the search space.

[0411] Aspect 69: The method of aspect 67, wherein the value of the RNTI is equal to zero and the base station does not transmit a PDCCH demodulation reference signal (DMRS) scrambling identifier configuration for the control resource set associated with the search space.

[0412] Aspect 70: The method of aspect 67, wherein the value of the RNTI is equal to zero and a PDCCH demodulation reference signal (DMRS) scrambling identifier for the control resource set associated with the search space is not supported.

[0413] Aspect 71: The method of aspect 67, wherein the value of the RNTI is equal to the G-RNTI, and the method further includes transmitting a PDCCH demodulation reference signal (DMRS) scrambling identifier configuration for a control resource set associated with the search space.

[0414] Aspect 72: The method of aspect 67, wherein the value of the RNTI is equal to the G-RNTI, and the base station does not transmit a PDCCH demodulation reference signal (DMRS) scrambling identifier configuration for a control resource set associated with the search space.

[0415] Aspect 73: The method of aspect 67, further comprising transmitting a configuration of a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) for a control resource set associated with the search space, wherein a value of the RNTI is equal to a G-RNTI based on transmitting the configuration of the PDCCH DMRS scrambling ID.

[0416] Aspect 74: The method of aspect 67, wherein the base station does not transmit a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) configuration for a control resource set associated with the search space, and the value of the RNTI is equal to zero based on the base station not transmitting a PDCCH DMRS scrambling ID configuration.

[0417] Aspect 75: The method of aspect 67, further comprising: transmitting a configuration of a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) for a control resource set associated with the search space; and transmitting a dedicated configuration indication for configuring the search space, wherein a value of the RNTI is equal to the G-RNTI based on the configuration of the PDCCH DMRS scrambling ID and transmitting the dedicated configuration indication.

[0418] Aspect 76: The method of aspect 75, wherein transmitting a dedicated configuration indication includes transmitting a dedicated radio resource control message.

[0419] Aspect 77: The method of any of aspects 75 or 76, wherein transmitting the dedicated configuration indication includes transmitting a radio resource control message indicating the dedicated parameters.

[0420] Aspect 78: The method described in aspect 67, wherein the value of the RNTI is equal to zero based on a determination that the base station has not transmitted a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) configuration for a control resource set associated with the search space and a dedicated configuration indication for configuring the search space.

[0421] Aspect 79: The method of aspect 67, further comprising: transmitting to a user equipment (UE) a configuration of a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) for a control resource set associated with the search space; and transmitting a monitoring configuration indicating that the UE should monitor the search space only in a radio resource control (RRC) connected state, wherein a value of the RNTI is equal to the G-RNTI based on transmitting the configuration of the PDCCH DMRS scrambling ID and the monitoring configuration.

[0422] Aspect 80: The method described in aspect 67, wherein the value of the RNTI is equal to zero based on a determination that the base station has not transmitted a PDCCH demodulation reference signal (DMRS) scrambling identifier (ID) configuration for a control resource set associated with the search space and a determination that the search space is not monitored only in a radio resource control connected state.

[0423] Example 81: The method of any of examples 67-80, wherein the at least one MBS PDCCH communication includes a downlink control information (DCI) transmission that schedules an MBS physical downlink shared channel.

[0424] Aspect 82: The method of aspect 81, wherein the value of the RNTI is equal to zero based on a determination that the DCI format of the DCI transmission is DCI format 1_0.

[0425] Aspect 83: The method of aspect 81, wherein the value of the RNTI is equal to the G-RNTI based on a determination that the DCI format of the DCI transmission is not DCI format 1_0.

[0426] Aspect 84: The method of any of aspects 67 to 83, wherein at least one MBS PDCCH communication schedules a plurality of MBS physical downlink shared channel (PDSCH) communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI among a plurality of G-RNTIs including the G-RNTI.

[0427] Aspect 85: The method of aspect 84, wherein the value of the RNTI is equal to a G-RNTI, the at least one additional payload is scrambled according to a PDCCH payload scrambling sequence based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI among the multiple G-RNTIs.

[0428] Aspect 86: The method of aspect 84, wherein the at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to the value of the RNTI.

[0429] Aspect 87: The method described in aspect 86, wherein the value of the RNTI is equal to a designated G-RNTI among a plurality of G-RNTIs.

[0430] Aspect 88: A method as described in any of aspects 86 or 87, wherein multiple G-RNTIs are set using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0431] Example 89: The method according to any one of examples 86 to 88, wherein the value of the RNTI is equal to the G-RNTI mapped to the multicast service.

[0432] Aspect 90: The method of aspect 89, wherein the multicast service includes a designated multicast service ID of a plurality of multicast service identifiers (IDs).

[0433] Aspect 91: The method described in aspect 86, wherein the value of the RNTI includes a configurable dedicated value.

[0434] Example 92: The method of any of examples 84 to 91, wherein the at least one MBS PDCCH communication includes a plurality of MBS PDCCH communications.

[0435] Aspect 93: The method of any of aspects 84 to 92, further comprising: transmitting a monitoring configuration indicating that the user equipment (UE) should monitor at least one additional search space for at least one additional MBS PDCCH that schedules at least one additional MBS PDSCH communication associated with the at least one additional G-RNTI of the plurality of G-RNTIs.

[0436] Example 94: The method of any of examples 67 to 93, further comprising transmitting a radio resource control configuration indicating a mapping between the search space and the G-RNTI.

[0437] Aspect 95: A method of wireless communication implemented by a base station, comprising: transmitting an MBS configuration indicating a PDCCH hashing function based on a group RNTI (G-RNTI) or a radio network temporary identifier (RNTI) value equal to zero for a search space associated with a physical downlink control channel (PDCCH) corresponding to a multicast / broadcast system (MBS) physical downlink shared channel (PDSCH); and transmitting at least one MBS PDCCH communication based at least in part on the configuration.

[0438] Aspect 96: The method described in aspect 95, wherein the value of the RNTI is equal to zero.

[0439] Aspect 97: The method described in aspect 95, wherein the value of the RNTI is equal to the G-RNTI.

[0440] Aspect 98: The method of aspect 95, further comprising transmitting an indication of a radio resource control (RRC) parameter that enables the RNTI to be equal to the G-RNTI, wherein the value of the RNTI is equal to the G-RNTI based on transmitting the indication of the RRC parameter.

[0441] Aspect 99: The method of aspect 95, wherein the value of the RNTI is equal to zero based on a determination that the base station has not transmitted an indication of a radio resource control parameter that enables the RNTI to be equal to the G-RNTI.

[0442] Aspect 100: The method of aspect 95, further comprising: sending a dedicated configuration indication to configure the search space, wherein the value of the RNTI is equal to the G-RNTI based on sending the dedicated configuration indication.

[0443] Aspect 101: The method of aspect 100, wherein transmitting a dedicated configuration indication includes transmitting a dedicated radio resource control message.

[0444] Aspect 102: The method of any of aspects 100 or 101, wherein transmitting the dedicated configuration indication includes transmitting a radio resource control message indicating the dedicated parameters.

[0445] Aspect 103: The method of aspect 95, wherein the value of the RNTI is equal to zero based on a determination that the base station has not transmitted a dedicated configuration indication for configuring the search space.

[0446] Aspect 104: The method of aspect 95, wherein a user equipment (UE) transmits a monitoring configuration indicating that the search space should be monitored only in a radio resource control (RRC) connected state, and the value of the RNTI is equal to the G-RNTI based on the monitoring configuration.

[0447] Aspect 105: The method of aspect 95, wherein the value of the RNTI is equal to zero based on a determination that the search space is not monitored only in a radio resource control connected state.

[0448] Example 106: The method of any of examples 95 to 105, wherein the at least one MBS PDCCH communication includes a downlink control information (DCI) transmission that schedules an MBS physical downlink shared channel.

[0449] Aspect 107: The method of aspect 106, wherein the value of the RNTI is equal to zero based on a determination that the DCI format of the DCI transmission is DCI format 1_0.

[0450] Aspect 108: The method of aspect 106, wherein the value of the RNTI is equal to the G-RNTI based on a determination that the DCI format of the DCI transmission is not DCI format 1_0.

[0451] Aspect 109: The method of any of aspects 95 to 108, wherein at least one MBS PDCCH communication schedules a plurality of MBS physical downlink shared channel (PDSCH) communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI among a plurality of G-RNTIs including the G-RNTI.

[0452] Aspect 110: The method of aspect 109, wherein the value of the RNTI is equal to a G-RNTI, the at least one additional CCE index corresponds to at least one additional hash function based on the at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI among the multiple G-RNTIs.

[0453] Aspect 111: The method of aspect 109, wherein the at least one additional hash function is based on at least one additional value of the RNTI, and the at least one additional value of the RNTI is equal to the value of the RNTI.

[0454] Aspect 112: The method described in aspect 111, wherein the value of the RNTI is equal to a specified G-RNTI among a plurality of G-RNTIs.

[0455] Aspect 113: A method according to any of aspects 111 or 112, wherein multiple G-RNTIs are set using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0456] Example 114: The method according to any one of examples 111 to 113, wherein the value of the RNTI is equal to the G-RNTI mapped to the multicast service.

[0457] Aspect 115: The method of aspect 114, wherein the multicast service includes a designated multicast service ID of a plurality of multicast service identifiers (IDs).

[0458] Aspect 116: The method described in aspect 111, wherein the value of the RNTI includes a configurable dedicated value.

[0459] Example 117: The method of any of examples 109 to 116, wherein the at least one MBS PDCCH communication includes a plurality of MBS PDCCH communications.

[0460] Aspect 118: The method of any of aspects 109 to 117, further comprising: transmitting a monitoring configuration indicating that the user equipment (UE) should monitor at least one additional search space for at least one additional MBS PDCCH that schedules at least one additional MBS PDSCH communication associated with the at least one additional G-RNTI of the plurality of G-RNTIs.

[0461] Example 119: The method of any of examples 95 to 118, further comprising transmitting a radio resource control configuration indicating a mapping between the search space and the G-RNTI.

[0462] Aspect 120: A method of wireless communication implemented by a base station, comprising: transmitting a Multicast / Broadcast System (MBS) configuration that configures a plurality of Group Radio Network Temporary Identifiers (G-RNTIs) for a cell; and transmitting at least one MBS PDCCH communication that schedules at least one MBS PDSCH communication of the plurality of MBS PDSCH communications based on the MBS configuration and using at least one search space associated with a Physical Downlink Control Channel (PDCCH) corresponding to an MBS Physical Downlink Shared Channel (PDSCH) of the cell.

[0463] Example 121: The method of example 120, wherein each MBS PDSCH communication of the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI of the plurality of G-RNTIs.

[0464] Aspect 122: A method according to any of aspects 120 or 121, wherein at least one G-RNTI of the plurality of G-RNTIs includes a value of an RNTI associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a control channel element index, or a cyclic redundancy check scrambling sequence.

[0465] Aspect 123: The method of aspect 122, wherein the value of the RNTI is equal to at least one G-RNTI, and the at least one additional value of the RNTI is equal to at least one additional G-RNTI of the plurality of G-RNTIs.

[0466] Aspect 124: The method of aspect 122, wherein at least one additional value of the RNTI is equal to the value of the RNTI.

[0467] Aspect 125: The method described in aspect 124, wherein the value of the RNTI is equal to a specified G-RNTI among a plurality of G-RNTIs.

[0468] Aspect 126: A method according to any of aspects 124 or 125, wherein multiple G-RNTIs are set using a G-RNTI list, and the value of the RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0469] Example 127: The method according to any one of examples 122 to 126, wherein at least one of the plurality of G-RNTIs is mapped to a multicast service.

[0470] Aspect 128: The method of aspect 127, wherein the multicast service includes a designated multicast service ID of a plurality of multicast service identifiers (IDs).

[0471] Aspect 129: A method as described in any of aspects 120 to 128, further comprising transmitting a configuration indicating a configurable dedicated value of the RNTI, wherein the configurable dedicated value of the RNTI is associated with at least one of a PDCCH payload scrambling sequence, a hash function corresponding to a control channel element index, or a cyclic redundancy check scrambling sequence.

[0472] Aspect 130: A method according to any of aspects 120 to 129, further comprising: transmitting a monitoring configuration indicating that a user equipment (UE) should monitor at least one search space, including monitoring one search space.

[0473] Aspect 131: The method of any of aspects 120 to 130, further comprising: transmitting a monitoring configuration indicating that the user equipment (UE) should monitor at least one search space, including monitoring multiple search spaces.

[0474] Example 132: The method of any of examples 120 to 131, further comprising transmitting a radio resource control configuration indicating a mapping between at least one search space and at least one G-RNTI among a plurality of G-RNTIs.

[0475] Aspect 133: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method described in one or more of aspects 1 to 28.

[0476] Aspect 134: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the one or more processors are configured to perform a method described in one or more of aspects 1 to 28.

[0477] Aspect 135: An apparatus for wireless communication, comprising at least one means for performing the method according to one or more of aspects 1 to 28.

[0478] Aspect 136: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method described in one or more of aspects 1 to 28.

[0479] Aspect 137: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method described in one or more of aspects 1 to 28.

[0480] Aspect 138: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method described in one or more of aspects 29 to 53.

[0481] Aspect 139: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the one or more processors are configured to perform the methods described in one or more of aspects 29 to 53.

[0482] Aspect 140: An apparatus for wireless communication, comprising at least one means for performing the method according to one or more of aspects 29 to 53.

[0483] Aspect 141: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method described in one or more of aspects 29 to 53.

[0484] Aspect 142: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method described in one or more of aspects 29 to 53.

[0485] Aspect 143: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method described in one or more of aspects 54 to 66.

[0486] Aspect 144: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the one or more processors are configured to perform a method described in one or more of aspects 54 to 66.

[0487] Aspect 145: An apparatus for wireless communication, comprising at least one means for performing the method according to one or more of aspects 54 to 66.

[0488] Aspect 146: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method described in one or more of aspects 54 to 66.

[0489] Aspect 147: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method described in one or more of aspects 54 to 66.

[0490] Aspect 148: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method described in one or more of aspects 67 to 94.

[0491] Aspect 149: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the one or more processors are configured to perform a method described in one or more of aspects 67 to 94.

[0492] Aspect 150: An apparatus for wireless communication, comprising at least one means for performing the method according to one or more of aspects 67 to 94.

[0493] Aspect 151: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method described in one or more of aspects 67 to 94.

[0494] Aspect 152: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform the methods described in one or more of aspects 67 to 94.

[0495] Aspect 153: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method described in one or more of aspects 95 to 119.

[0496] Aspect 154: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the one or more processors are configured to perform a method described in one or more of aspects 95 to 119.

[0497] Aspect 155: An apparatus for wireless communication, comprising at least one means for performing the method described in one or more of aspects 95 to 119.

[0498] Aspect 156: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method described in one or more of aspects 95 to 119.

[0499] Aspect 157: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method described in one or more of aspects 95 to 119.

[0500] Aspect 158: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method described in one or more of aspects 120 to 132.

[0501] Aspect 159: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the one or more processors are configured to perform the methods described in one or more of aspects 120 to 132.

[0502] Aspect 160: An apparatus for wireless communication, comprising at least one means for performing the method according to one or more of aspects 120-132.

[0503] Aspect 161: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method described in one or more of aspects 120 to 132.

[0504] Aspect 162: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method described in one or more of aspects 120-132.

[0505] Aspect 163: A method of wireless communication implemented by a user equipment (UE), comprising: monitoring a search space associated with a physical downlink control channel (MBS) PDCCH communication corresponding to an MBS physical downlink shared channel (PDSCH) for at least one MBS PDCCH communication having a payload scrambled in accordance with a PDCCH payload scrambling sequence based on a radio network temporary identifier (RNTI) value equal to zero; and receiving the at least one MBS PDCCH communication.

[0506] Aspect 164: The method of aspect 163, further comprising receiving a PDCCH demodulation reference signal (DMRS) scrambling identifier configuration for a control resource set associated with the search space.

[0507] Aspect 165: The method of aspect 163, in which the UE does not receive a PDCCH demodulation reference signal (DMRS) scrambling identifier configuration for a control resource set associated with the search space.

[0508] Aspect 166: The method of aspect 163, wherein a PDCCH demodulation reference signal (DMRS) scrambling identifier for a control resource set associated with the search space is not supported.

[0509] Aspect 167: The method of aspect 163, wherein the at least one MBS PDCCH communication includes a cyclic redundancy check (CRC) scrambled using a group RNTI (G-RNTI).

[0510] Aspect 168: The method of aspect 167, wherein at least one MBS PDCCH communication schedules a plurality of MBS PDSCH communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding Group RNTI (G-RNTI) among a plurality of G-RNTIs including the G-RNTI.

[0511] Aspect 169: The method of aspect 168, wherein at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on at least one additional value of the G-RNTI, and the at least one additional value of the G-RNTI is equal to at least one additional G-RNTI among the plurality of G-RNTIs.

[0512] Aspect 170: The method according to aspect 168 or 169, wherein at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on at least one additional value of the G-RNTI, and the at least one additional value of the G-RNTI is equal to the value of the G-RNTI.

[0513] Example 171: The method according to any one of examples 168 to 170, wherein the value of the G-RNTI is equal to a specified G-RNTI among a plurality of G-RNTIs.

[0514] Aspect 172: A method according to any of aspects 168 to 171, wherein the multiple G-RNTIs are set using a G-RNTI list, and the value of the G-RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0515] Example 173: The method according to any one of examples 168 to 172, wherein the value of the G-RNTI is equal to the G-RNTI mapped to the multicast service.

[0516] Aspect 174: The method of aspect 173, wherein the multicast service includes a specified multicast service ID of a plurality of multicast service IDs.

[0517] Aspect 175: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method described in one or more of aspects 163 to 174.

[0518] Aspect 176: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the one or more processors are configured to perform the methods described in one or more of aspects 163 to 174.

[0519] Aspect 177: An apparatus for wireless communication, comprising at least one means for performing the method described in one or more of aspects 163 to 174.

[0520] Aspect 178: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method described in one or more of aspects 163 to 174.

[0521] Aspect 179: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform the methods described in one or more of aspects 163 to 174.

[0522] Aspect 180: A method of wireless communication implemented by a base station, the method including: transmitting an MBS configuration indicating a physical downlink control channel (PDCCH) payload scrambling sequence based on a radio network temporary identifier (RNTI) value equal to zero for a search space associated with a physical downlink control channel (PDCCH) corresponding to a multicast / broadcast system (MBS) physical downlink shared channel (PDSCH); and transmitting at least one MBS PDCCH communication based at least in part on the configuration.

[0523] Aspect 181: The method of aspect 180, further comprising transmitting a PDCCH demodulation reference signal (DMRS) scrambling identifier configuration for a control resource set associated with the search space.

[0524] Aspect 182: The method according to aspect 180, in which the base station does not transmit a PDCCH demodulation reference signal (DMRS) scrambling identifier configuration for a control resource set associated with the search space.

[0525] Aspect 183: The method of aspect 180, wherein a PDCCH demodulation reference signal (DMRS) scrambling identifier for a control resource set associated with the search space is not supported.

[0526] Aspect 184: The method of aspect 180, wherein the at least one MBS PDCCH communication includes a cyclic redundancy check (CRC) scrambled using a group RNTI (G-RNTI).

[0527] Aspect 185: The method of aspect 184, wherein at least one MBS PDCCH communication schedules a plurality of MBS PDSCH communications, and each MBS PDSCH communication among the plurality of MBS PDSCH communications is associated with a corresponding G-RNTI among a plurality of G-RNTIs including a group RNTI (G-RNTI).

[0528] Aspect 186: The method of aspect 185, wherein at least one additional payload is scrambled according to a PDCCH payload scrambling sequence that is based on at least one additional value of the G-RNTI, and the at least one additional value of the G-RNTI is equal to at least one additional G-RNTI among the plurality of G-RNTIs.

[0529] Aspect 187: The method according to aspect 185 or 186, wherein at least one additional payload is scrambled according to a PDCCH payload scrambling sequence based on at least one additional value of the G-RNTI, and the at least one additional value of the G-RNTI is equal to the value of the G-RNTI.

[0530] Example 188: The method according to any one of examples 185 to 187, wherein the value of the G-RNTI is equal to a designated G-RNTI among a plurality of G-RNTIs.

[0531] Aspect 189: The method of any of aspects 185 to 188, wherein the multiple G-RNTIs are set using a G-RNTI list, and the value of the G-RNTI is equal to the first listed G-RNTI in the G-RNTI list.

[0532] Example 190: The method according to any one of examples 185 to 189, wherein the value of the G-RNTI is equal to the G-RNTI mapped to the multicast service.

[0533] Aspect 191: The method of aspect 190, wherein the multicast service includes a specified multicast service ID of a plurality of multicast service IDs.

[0534] Aspect 192: An apparatus for wireless communication in a device, the apparatus including a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method described in one or more of aspects 180 to 191.

[0535] Aspect 193: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the one or more processors are configured to perform the methods described in one or more of aspects 180 to 191.

[0536] Aspect 194: An apparatus for wireless communication, comprising at least one means for performing the method described in one or more of aspects 180 to 191.

[0537] Aspect 195: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method described in one or more of aspects 180 to 191.

[0538] Aspect 196: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method described in one or more of aspects 180 to 191.

[0539] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the embodiments.

[0540] The term "component" as used herein shall be broadly construed as hardware and / or a combination of hardware and software. "Software" shall be broadly construed to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. A "processor" as used herein is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not intended to limit the aspects. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, as those skilled in the art will appreciate that software and hardware may be designed to implement the systems and / or methods based at least in part on the description herein.

[0541] As used herein, "meeting a threshold" can refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc., depending on the context.

[0542] Although particular combinations of features are recited in the claims and / or disclosed herein, those combinations do not limit the disclosure of the various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. The disclosure of the various aspects includes each dependent claim in combination with any other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to include a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other order of a, b, and c).

[0543] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Additionally, the articles "a" and "an" as used herein are intended to include one or more items and may be used interchangeably with "one or more." Additionally, the article "the" as used herein is intended to include one or more items referred to in relation to the article "the" and may be used interchangeably with "one or more." Additionally, the terms "set" and "group" as used herein are intended to include one or more items and may be used interchangeably with "one or more." When only one item is intended, the phrase "only one" or similar language is used. Additionally, terms such as "has," "have," and "having" as used herein are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "has" A may also have B). Additionally, the phrase "based on" is intended to mean "based at least in part on," unless otherwise specified. Also, as used herein, the term "or" is intended to be inclusive when used in a consecutive manner, and may be used interchangeably with "and / or" unless otherwise noted (e.g., when used in combination with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communications, comprising: Memory, one or more processors coupled to the memory; wherein the one or more processors: monitor a search space associated with a PDCCH corresponding to an MBS Physical Downlink Shared Channel (PDSCH) for at least one Multicast / Broadcast System (MBS) PDCCH communication having a payload scrambled in accordance with a Physical Downlink Control Channel (PDCCH) payload scrambling sequence based on the value of a Radio Network Temporary Identifier (RNTI) when the value of the RNTI is equal to zero, and for at least one MBS PDCCH communication having a Control Channel Element (CCE) index corresponding to a hash function based on the value of the RNTI when the value of the RNTI is equal to a Group RNTI (G-RNTI); and configured to receive the at least one MBS PDCCH communication. User Equipment (UE).

2. The UE of claim 1, wherein when the value of the RNTI is equal to the G-RNTI, the one or more processors are further configured to receive a setting of a PDCCH demodulation reference signal (DMRS) scrambling identifier for a control resource set associated with the search space.

3. The UE of claim 1, wherein if the value of the RNTI is equal to zero, the UE does not receive a PDCCH demodulation reference signal (DMRS) scrambling identifier setting for a control resource set associated with the search space.

4. The UE of claim 1, wherein if the value of the RNTI is equal to zero, then a PDCCH demodulation reference signal (DMRS) scrambling identifier is not supported for a control resource set associated with the search space.

5. The UE of claim 1 , wherein the at least one MBS PDCCH communication includes a cyclic redundancy check (CRC) scrambled using a group RNTI (G-RNTI).

6. 6. The UE of claim 5, wherein the at least one MBS PDCCH communication schedules a plurality of MBS PDSCH communications, each MBS PDSCH communication of the plurality of MBS PDSCH communications being associated with a corresponding Group RNTI (G-RNTI) of a plurality of G-RNTIs that comprise the G-RNTI.

7. The UE of claim 6, wherein the value of the G-RNTI is equal to a designated G-RNTI among the plurality of G-RNTIs.

8. The UE of claim 6, wherein the multiple G-RNTIs are configured using a G-RNTI list, and a value of the G-RNTI is equal to a first listed G-RNTI in the G-RNTI list.

9. The UE of claim 6, wherein the value of the G-RNTI is equal to a G-RNTI mapped to a multicast service.

10. The UE of claim 9 , wherein the multicast service includes a designated multicast service ID of a plurality of multicast service identifiers (IDs).

11. A network node for wireless communication, comprising: Memory, one or more processors coupled to the memory; wherein the one or more processors: For a search space associated with a physical downlink control channel (PDCCH) corresponding to a multicast / broadcast system (MBS) physical downlink shared channel (PDSCH), sending an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of a radio network temporary identifier (RNTI) if the value of the RNTI is equal to zero, and an MBS configuration indicating a hash function based on the value of the RNTI if the value of the RNTI is equal to a group RNTI (G-RNTI); and transmitting at least one MBS PDCCH communication based at least in part on the configuration. Network node.

12. A network node as described in claim 11, wherein if the value of the RNTI is equal to the G-RNTI, the one or more processors are further configured to transmit a PDCCH demodulation reference signal (DMRS) scrambling identifier setting for a control resource set associated with the search space.

13. The network node of claim 11, wherein if the value of the RNTI is equal to zero, the network node does not transmit a PDCCH demodulation reference signal (DMRS) scrambling identifier configuration for a control resource set associated with the search space.

14. The network node of claim 11, wherein if the value of the RNTI is equal to zero, then a PDCCH demodulation reference signal (DMRS) scrambling identifier is not supported for a control resource set associated with the search space.

15. The network node of claim 11, wherein the at least one MBS PDCCH communication includes a Cyclic Redundancy Check (CRC) scrambled using a Group RNTI (G-RNTI).

16. 16. The network node of claim 15, wherein the at least one MBS PDCCH communication schedules a plurality of MBS Physical Downlink Shared Channel (PDSCH) communications, each MBS PDSCH communication of the plurality of MBS PDSCH communications being associated with a corresponding G-RNTI of a plurality of G-RNTIs including the G-RNTI.

17. The network node of claim 16, wherein the plurality of G-RNTIs are configured using a G-RNTI list, and a value of the G-RNTI is equal to a first listed G-RNTI in the G-RNTI list.

18. The network node of claim 16, wherein the G-RNTI is mapped to a multicast service.

19. 20. The network node of claim 18, wherein the multicast service comprises a designated multicast service identifier (ID) of a plurality of multicast service IDs.

20. The network node of claim 11 , wherein the at least one MBS PDCCH communication comprises a plurality of MBS PDCCH communications.

21. 1. A method of wireless communication implemented by a user equipment (UE), comprising: monitoring a search space associated with a PDCCH corresponding to an MBS Physical Downlink Shared Channel (PDSCH) for at least one Multicast / Broadcast System (MBS) PDCCH communication having a payload scrambled in accordance with a Physical Downlink Control Channel (PDCCH) payload scrambling sequence based on a value of a Radio Network Temporary Identifier (RNTI) if the value of the RNTI is equal to zero, and for at least one MBS PDCCH communication having a Control Channel Element (CCE) index corresponding to a hash function based on the value of the RNTI if the value of the RNTI is equal to a Group RNTI (G-RNTI); receiving the at least one MBS PDCCH communication; The method includes:

22. 22. The method of claim 21, further comprising receiving a PDCCH demodulation reference signal (DMRS) scrambling indicator configuration for a control resource set associated with the search space if the value of the RNTI is equal to the G-RNTI.

23. 22. The method of claim 21, wherein the at least one MBS PDCCH communication includes a cyclic redundancy check (CRC) scrambled using a group RNTI (G-RNTI).

24. 1. A method of wireless communication implemented by a network node, comprising: transmitting an MBS configuration indicating a PDCCH payload scrambling sequence based on a value of a Radio Network Temporary Identifier (RNTI) when the value of the RNTI is equal to zero, and an MBS configuration indicating a hash function based on a value of a Group RNTI (G-RNTI) for a search space associated with a Physical Downlink Control Channel (PDCCH) corresponding to a Multicast / Broadcast System (MBS) Physical Downlink Shared Channel (PDSCH); transmitting at least one MBS PDCCH communication based at least in part on said configuration; The method includes:

25. 25. The method of claim 24, further comprising: transmitting a PDCCH demodulation reference signal (DMRS) scrambling indicator configuration for a control resource set associated with the search space if the value of the RNTI is equal to the G-RNTI.

26. 25. The method of claim 24, wherein the at least one MBS PDCCH communication includes a cyclic redundancy check (CRC) scrambled using a group RNTI (G-RNTI).

Images