Broadcast and multicast capability reduction in RRC inactive states

Abstract

For example, an apparatus may be configured to receive a first indication of a CFR associated with at least one of an MCCH or an MTCH for a plurality of RedCap UEs in one of an inactive state or an idle state, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, the first capability being different from a second capability having a second maximum bandwidth greater than the first maximum bandwidth. The apparatus may also be configured to monitor a CFR for at least one of broadcast traffic or multicast traffic indicated in the first indication. The apparatus may be configured to output a first indication for transmission to the plurality of RedCap UEs, and output at least one of an MCCH communication or an MTCH communication for transmission to the plurality of RedCap UEs via a CFR for at least one of broadcast traffic or multicast traffic indicated in the first indication.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Non-Provisional Patent Application Serial No. 18 / 320,939, filed May 19, 2023, entitled “REDUCED CAPABILITY FOR BROADCAST AND MULTICAST INRRC INACTIVE STATE”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to multicast and broadcast services (MBS) for user equipment (UE) in a wireless network. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CWB) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR are based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a wireless device or a component of a wireless device, configured to receive a first indication of a common frequency resource (CFR) associated with at least one of a multicast control channel (MCCH) or multicast traffic channel (MTCH) for a plurality of capability-reduced (RedCap) UEs in an inactive or idle state, the plurality of capability-reduced (RedCap) UEs supporting a first capability having a first maximum bandwidth, the first capability being different from a second capability having a second maximum bandwidth greater than the first maximum bandwidth. The apparatus may also be configured to monitor the CFR for at least one of broadcast or multicast traffic indicated in the first indication.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a network node, network device, or a component of a network node or network device, configured to output a first indication of a CFR associated with at least one of the MCCH or MTCH of a plurality of RedCap UEs in an inactive or idle state for transmission to the plurality of RedCap UEs, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, the first capability being different from a second capability having a second maximum bandwidth greater than the first maximum bandwidth. The apparatus may also be configured to output at least one of the MCCH or MTCH communications via the CFR indicated in the first indication for at least one of broadcast or multicast services for transmission to the plurality of RedCap UEs.

[0009] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings illustrate some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0012] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0013] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0014] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0015] Figure 3 This is a diagram illustrating an example of a base station and a UE in an access network.

[0016] Figure 4A This is a diagram illustrating an example of an MBS area in an access network.

[0017] Figure 4B This is a diagram illustrating an example of MBS channel configuration in MBS.

[0018] Figure 5 The first and second diagrams respectively illustrate, according to some aspects of this disclosure, a first resource allocation for physical DL shared channel (PDSCH) communication and a second resource allocation for physical UL shared channel (PUSCH) communication associated with a first type of RedCap.

[0019] Figure 6 This includes a set of diagrams illustrating various options for configuring CFRs for broadcast or multicast (or MBS) of wireless devices in an RRC inactive state, according to some aspects of this disclosure.

[0020] Figure 7 This is an example of a call flow diagram illustrating a set of UE base stations associated with an MBS according to some aspects of this disclosure.

[0021] Figure 8 This is a flowchart of a wireless communication method.

[0022] Figure 9 This is a flowchart of a wireless communication method.

[0023] Figure 10 This is a flowchart of a wireless communication method.

[0024] Figure 11 This is a flowchart of a wireless communication method.

[0025] Figure 12 This is a diagram illustrating an example of a hardware implementation used in a device.

[0026] Figure 13 This is a diagram illustrating an example of a hardware implementation used for a network entity. Detailed Implementation

[0027] Wireless communication systems can support broadcast communications such as MBS. In some aspects of wireless communication, wireless devices (e.g., UEs) in an RRC inactive or idle state can be configured to conserve power in association with MBS. Some wireless devices (e.g., UEs) in a communication system can have reduced complexity and / or reduced power consumption based on supporting one or more reduced capabilities (e.g., they may be referred to as RedCap UEs). For example, a Type n RedCap device supporting a set of capabilities can be described in the following discussion as operating in one or more of a Type n RedCap mode, a Type n RedCap operation, or a Type n RedCap operation mode. In some aspects, a Type n RedCap operation mode can be associated with a Type n RedCap configuration or a set of Type n RedCap parameters that define and / or specify the capabilities supported in the Type n RedCap operation mode. UEs associated with or implementing a Type n RedCap operation mode can be collectively referred to as RedCap UEs below, or more specifically as Type n RedCap UEs.

[0028] In some respects, RedCap devices (or RedCap UEs) can support (or RedCap configurations can define and / or specify) the (maximum) baseband (BB) bandwidth (BW) and (maximum) RF BW for PDSCH and PUSCH. For example, a first-type RedCap UE can support a (maximum) BB BW of 5 MHz for PDSCH and PUSCH, while also supporting a (maximum) RF BW of 20 MHz. In some respects, the maximum BB BW and / or RF BW can be indicated based on resource blocks (RBs) or physical RBs (PRBs). For example, the maximum BB BW can be defined and / or specified as one of 23 to 27 RBs (e.g., 25 RBs) associated with a 15 kHz SCS or one of 11 to 13 RBs (e.g., 12 RBs) associated with a 30 kHz SCS (for a total BB BW of approximately 5 MHz). Additional types of RedCap UEs can support different maximum BB BWs and different RF BWs. Different types of RedCap UEs can also be associated with additional parameters to reduce the power associated with broadcast or multicast communication (or MBS) in RRC inactive states. These additional parameters can be different for different types of RedCap UEs.

[0029] Various aspects of this disclosure generally relate to MBS configuration for an enhanced RedCap device (eRedCap device or eRedCap UE) used in an RRC idle or inactive state and supporting a first capability with a first maximum bandwidth, which differs from a second capability with a second maximum bandwidth greater than the first maximum bandwidth. The MBS configuration for eRedCap can allow MBS reception associated with additional complexity reduction beyond that associated with other RedCap capabilities. Some aspects more specifically relate to configuring CFRs (and / or other parameters) associated with the MBS configuration for the eRedCap device. In some aspects, the base station can transmit, and the UE (e.g., eRedCap UE) can receive, an indication of a CFR (or additional parameter) associated with at least one of the MCCH or MTCH of a plurality of RedCap (or eRedCap) UEs supporting the first capability in an inactive or idle state. The base station can then transmit or communicate via the CFR indicated in the first indication for at least one of broadcast or multicast services, and the UE can monitor the transmission or communication.

[0030] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. MBS configuration for RedCap devices (or eRedCap devices) that support the first capability for RRC idle or inactive states can improve the complexity associated with multicast or broadcast communications when an eRedCap UE in one of the RRC idle or inactive states is conducting multicast or broadcast communications.

[0031] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0032] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0033] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0034] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0035] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0036] Communication systems, such as 5G NR systems, can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0037] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0038] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0039] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0040] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0041] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 for network control and signaling purposes, as needed.

[0042] DU 130 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0043] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 140 can be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration enables the implementation of the DU 130 and CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0044] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0045] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

[0046] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 125 and may be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or via the creation of RAN management policies (such as A1 policies).

[0047] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). These carriers may or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell) and the secondary component carrier can be referred to as the secondary cell (SCell).

[0048] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.) ™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0049] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP 150 may perform a free channel assessment (CCA) to determine whether a channel is available before communication.

[0050] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz–300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0051] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125GHz–24.25GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher bands falls within the EHF band.

[0052] In view of the above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0053] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0054] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0055] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0056] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0057] Wireless communication systems can support broadcast communication (such as MBS). See again Figure 1In some aspects, UE 104 may have an eRedCap MBS component 198, which may be configured to receive a first indication of a CFR associated with at least one of the MCCH or MTCH of a plurality of RedCap UEs in a connected, inactive, or idle state, the plurality of RedCap UEs supporting a first capability with a first maximum bandwidth, the first capability being different from a second capability with a second maximum bandwidth greater than the first maximum bandwidth. eRedCap MBS component 198 may also be configured to monitor the CFR indicated in the first indication for at least one of broadcast or multicast services. In some aspects, base station 102 may have an eRedCap MBS configuration component 199, which may be configured to output a first indication of a CFR associated with at least one of the MCCH or MTCH of a plurality of RedCap UEs in an inactive or idle state for transmission to the plurality of RedCap UEs, the plurality of RedCap UEs supporting a first capability with a first maximum bandwidth, the first capability being different from a second capability with a second maximum bandwidth greater than the first maximum bandwidth. The eRedCap MBS configuration component 199 can also be configured to be sent to multiple RedCap UEs via at least one of the CFR output MCCH communication or MTCH communication for at least one of the broadcast or multicast services indicated in the first indication. While the aspects described below describe an application associated with an MBS for a RedCap UE in an idle or inactive state (e.g., RRC inactive) in 5G NR, the concepts described herein can be applied to other similar fields (such as MBS for RedCap UEs in other states).

[0058] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 illustrates an example of the second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured using the slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0059] Figures 2A to 2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL can be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled by 1 / SCS.

[0060]

[0061] Table 1: Parameter Set, SCS, and CP

[0062] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. Subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0063] A resource grid can be used to represent the frame structure. Each time slot consists of a RB (also known as a PRB) extending for 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0064] like Figure 2A As illustrated, some REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0065] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP may be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0066] like Figure 2C As illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or second symbol of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0067] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0068] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0069] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream undergoes spatial pre-decoding to generate multiple spatial streams. Channel estimates from channel estimator 374 are used to determine the decoding and modulation scheme, as well as for spatial processing. Channel estimates can be derived based on reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to different antennas 320 via a separate transmitter 318Tx. Each transmitter 318Tx can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0070] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. Subsequently, the soft decision is decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0071] The controller / processor 359 may be associated with at least one memory 360 storing program code and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0072] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0073] The TX processor 368 can use the channel estimator 358 to obtain a reference signal transmitted from the base station 310 or a channel estimate derived from feedback, in order to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0074] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0075] The controller / processor 375 may be associated with at least one memory 376 storing program code and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets between transport and logical channels. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0076] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 The eRedCap MBS component 198 combines various aspects.

[0077] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform and Figure 1 The eRedCap MBS configuration component 199 combines various aspects.

[0078] Some wireless communication systems can support broadcast communication (such as MBS). Figure 4A Figure 410 illustrates an example of an MBS area in an access network. Base station 412 (or TRP) in cell 412' can form a first MBS area, and base station 414 in cell 414' can form a second MBS area. Base stations 412 and 414 can each be associated with other MBS areas. Cells in MBS areas can be designated as reserved cells. Reserved cells do not provide multicast / broadcast content, but can be time-synchronized with cells 412' and 414', and can have limited power regarding MBS resources to limit interference to the MBS area. Each base station in the MBS area synchronously transmits the same MBS control information and data. Each area can support broadcast, multicast, and unicast services. Unicast services are services designed for a specific user (e.g., voice calls to a specific UE). Multicast services are services that can be received by a group of users and can also be referred to as multicast (e.g., video subscription services). Broadcast services are services that can be received by any user within the coverage area (e.g., news broadcasts). See also Figure 4A The first MBS area can support first MBS broadcast services, such as providing specific news broadcasts to UE 425. The second MBS area can support second MBS broadcast services, such as providing different news broadcasts to UE 420.

[0079] Figure 4B Figure 430 is an example of an MBS channel configuration in an MBS. For example... Figure 4B As shown, each MBS region supports one or more Physical Multicast Channels (PMCHs) (e.g., 15 PMCHs). Each PMCH corresponds to one MCH. Each MCH can multiplex multiple (e.g., 29) multicast logical channels. Each MBS region can have one Multicast Control Channel (MCCH). Therefore, one MCH can multiplex one MCCH and multiple Multicast Traffic Channels (MTCHs), and the remaining MCHs can multiplex multiple MTCHs.

[0080] The UE can camp on the cell to discover the availability of MBS service access and the corresponding access stratum configuration. Initially, the UE can acquire an SIB, which includes information enabling the UE to acquire MBS area configuration messages on the MCCH. Subsequently, based on the MBS area configuration message, the UE can acquire the MCH scheduling information (MSI) media access control-control element (MAC-CE). The SIB may include the MBS area identifier for each MBS area supported by the cell and information for acquiring the MCCH. Each MBS area may have one MBS area configuration message. The MBS area configuration message may indicate the Temporary Mobile Group Identifier (TMGI) and optional session identifier for each MTCH identified by the logical channel identifier within the PMCH, as well as the time and / or frequency resources allocated for each PMCH of the MBS area. A specific TMGI identifier is available for a specific service within the MBS service.

[0081] In some aspects of wireless communication, a wireless device (e.g., a UE) in an RRC inactive state (or idle state) may be configured to conserve power in association with MBS. In some aspects, a wireless device (e.g., a UE) in an RRC inactive state may have reduced complexity and / or reduced power consumption, and may support one of several types of reduced capabilities (RedCap). A RedCap device of type n supporting a set of capabilities may be described in the following discussion as one or more of a RedCap mode of type n, RedCap operation of type n, or RedCap operation mode of type n. In some aspects, a RedCap operation mode of type n may be associated with a RedCap configuration of type n or a set of RedCap parameters defining and / or specifying the capabilities supported in the RedCap operation mode of type n. A UE associated with or implementing a RedCap operation mode of type n may be collectively referred to as a RedCap UE, or specifically as a RedCap UE of type n.

[0082] In some respects, RedCap devices can support (or RedCap configuration can define and / or specify) the (maximum) BB BW and (maximum) RF BW for PDSCH and PUSCH. For example, a first-type RedCap device can support a (maximum) BB BW of 5 MHz for PDSCH and PUSCH, while also supporting a (maximum) RF BW of 20 MHz. In some respects, the maximum BB BW and / or RF BW can be specified based on RB or PRB; for example, the maximum BB BW can be defined and / or specified as one of 23 to 27 RBs (e.g., 25 RBs) associated with a 15 kHz SCS or one of 11 to 13 RBs (e.g., 12 RBs) associated with a 30 kHz SCS (for a total BB BW of approximately 5 MHz). Additional types of RedCap can support different maximum BB BWs and different RF BWs. Different types of reduced capabilities or RedCap devices can also be associated with additional parameters to reduce the power associated with broadcast or multicast communications (or MBS) during RRC inactivity. These additional parameters can vary for different types of RedCap devices.

[0083] Figure 5 The document includes a first diagram 500 and a second diagram 550, respectively illustrating a first resource allocation for PDSCH communication and a second resource allocation for PUSCH communication associated with a reduced baseband bandwidth for a first type of RedCap UE, according to some aspects of this disclosure. The first diagram 500 illustrates that a first type of RedCap UE (e.g., a UE implementing the first type of RedCap) can receive control information (e.g., DCI) for scheduling unicast PDSCH via a 20MHz RF BW 520 within a larger system BW 510. In some aspects, the scheduled PDSCH can be scheduled via a set of PRBs 530 (or RBs) spanning less than 5MHz in a specific time slot (e.g., including no more than 1 to 13 RBs or 1 to 27 RBs associated with SCSs of 30kHz or 15kHz, respectively).

[0084] Figure 550 illustrates that, in some aspects, the first type of RedCap UE can receive configured permission or UL permission for PUSCH, where the BB BW 580 spans up to 5 MHz within the RF BW 570, and subsequently within the larger system BW 560. Permission for PUSCH can be sent by the network device via one or more of PUCCH, Random Access Response (RAR), or DCI (e.g., DCI scrambled by a Temporary Cell RNTI (Temporary C-RNTI or TC-RNTI) indicating a temporary (16-bit) identity that can be used by the MAC entity during random access using Msg3 PUSCH resource allocation), and received at the RedCap UE. In some aspects, the (up to) 5 MHz BB BW 580 for PUSCH can be allocated per time slot or per hop. When using an example of a first-type reduction capability with a maximum RF BW of 20MHz and a maximum BB BW of 5MHz (e.g., a first configuration associated with a first-type RedCap operation or mode), the maximum BW capability for one or more of the BB or RF may differ for the first-type reduction capability or for different types of reduction.

[0085] In some aspects associated with a cell supporting multiple types of RedCap UEs, the initial BWP can be configured to support communication with devices of different capabilities, such as RedCap UEs and non-RedCap UEs. The initial BWP (e.g., it may include an initial downlink BWP) can be used by the network to transmit information for multiple types of UEs, including different types of RedCap UEs. In some aspects, SIB1 or other system information (OSI) (e.g., via PDSCH) can carry information for RedCap UEs and non-RedCap UEs, as well as for multiple types of RedCap UEs with reduced (e.g., <5MHz) maximum bandwidth. In some aspects, scheduling of SIB1 and / or OSI (via PDSCH) greater than 5MHz can be allowed (e.g., for different types of RedCap UEs or non-RedCap UEs, frequency resources exceeding 5MHz can be spanned). In some aspects, even for transmission, paging messages or paging channels (e.g., via PDSCH) greater than 5MHz can be allowed to allow paging PDSCH scheduling greater than 5MHz. In some respects, it may be permissible to transmit RAR (e.g., Msg2) via multiple unicast PRBs (in the PDSCH), where the number of unicast PRBs exceeds the maximum number of unicast PRBs that a particular type of RedCap UE can support for processing per slot of the PDSCH. Therefore, when the scheduling of the RAR PDSCH is within the maximum number of unicast PRBs that a particular type of RedCap UE can process per slot of the PDSCH, a known time between RAR reception and Msg3 transmission (e.g., the time applied to non-RedCap UEs) (not less than N) can be applied. T,1 +N T,2 +0.5ms). However, when the scheduling of RAR PDSCH exceeds the maximum number of unicast PRBs supported per slot for a specific type of RedCap UE, if the TDRA indication for Msg3 in the UL grant in the RAR is not less than N, T,1 +N T,2 If the time interval is +0.5 + X ms, then a specific type of RedCap UE can receive the RAR and send the corresponding Msg3, where X can be determined based on relevant factors. If the UL in the RAR allows the time between RAR reception and Msg3 transmission to be less than N ms... T,1 +N T,2 With +0.5+Xms, in some aspects, UE behavior can be determined based on the specific implementation of the UE.

[0086] In some aspects, for UEs in RRC idle, RRC inactive, or RRC connected states, the broadcast common frequency resources (CFRs) for MCCH or MTCH can be configured, for example, by SIB20 or MCCH. Dynamically granted group common (GC)-PDCCH or GC-PDSCH for MCCH can be associated with MCCH-RNTI, while for MTCH, GC-PDCCH or GC-PDSCH can be associated with one or more G-RNTIs. In some aspects, the DCI format associated with GC-PDCCH (e.g., DCI format 4_0) can be configured in common search space parameters (e.g., Type0B-CSS). In some aspects, changes to the MCCH configuration can be indicated in the same DCI for MCCH. In some aspects, broadcast MTCH can be semi-statically or dynamically scheduled for slot-level repetition. In some aspects, MCCH and PBCH can be frequency-division multiplexed for broadcast UEs (e.g., UEs associated with broadcasts).

[0087] Figure 6 This includes a set of diagrams (e.g., diagrams 610, 620, and 630) illustrating multiple options for configuring CFRs for broadcast or multicast (or MBS) of a wireless device in an RRC inactive state, according to some aspects of this disclosure. In some aspects, the CFR for MBS (e.g., for MCCH and / or MTCH) can be defined (or configured) by common information elements (e.g., locationAndBandwidth) associated with broadcast or multicast communication. Figure 610 illustrates a first case where CFR 611 has the same BW as CORESET0 612, but not the same BW as the initial BW 613 (e.g., the initial downlink BWP configured by SIB1). Figure 620 illustrates a second case where CFR 621 has the same BW as the initial BW 623, which is greater than the BW of CORESET0 622. Figure 630 illustrates the third case, in which CFR 631 has a larger BW than both CORESET0 632 and initial BW 633 (e.g., initial downlink BWP).

[0088] In some respects, the CFR for MBS broadcast (and / or multicast) may fully encompass CORESET0 (which may alternatively be referred to as CORESET#0) (e.g., spanning the bandwidth including the frequency resources for CORESET#0) and may have the same CP and SCS as CORESET0 and / or the initial BWP. In addition to the CFR BW size, the CFR for MCCH / MTCH (e.g., CFR 611, 621, or 631) may also include a first CFR for MCCH configured via SIB20 and a second CFR for MTCH configured via MCCH (e.g., via PDCCH-config and / or PDSCH-config for MTCH). In some respects, if the CFR for MTCH is not configured via MCCH, the PDCCH-config and / or PDSCH-config for MCCH configured via a different SIB may be reused for MTCH.

[0089] In some aspects, PDCCH configuration for MCCH and / or MTCH can be associated with a CORESET, search space, or DCI. PDCCH configuration for MCCH or MTCH can be included in an Information Element (IE) associated with a CORESET, search space, or DCI. For example, a CORESET can be associated with or include an IE that provides, specifies, or defines the PDCCH configuration for MCCH or MTCH in a first IE (e.g., PDCCH-Config-MCCH) or a second IE (e.g., PDCCH-Config-MTCH). In some aspects, a UE can be configured with up to two CORESETs for MCCH and / or MTCH. In some aspects, a CORESET for MCCH and / or MTCH can be CORESET0 configured via a first IE (e.g., commonControlResourceSet IE) for configuring a common CORESET. In some aspects, a UE can be configured with a CORESET having a larger BW than CORESET0 for MCCH and / or MTCH, for example, if commonControlResourceSet does not configure a CORESET. In some respects, if the CFR is the initial BWP and no other CORESET is configured, CORESET0 is used by default. In some respects, the initial scrambling sequence generators for GC-PDCCH and DMRS used for GC-PDCCH can be configured in or via CORESET.

[0090] In some aspects, the PDCCH used for MCCH and / or MTCH can be configured, for example, via PDCCH-ConfigCommon for MCCH and / or MTCH in association with a search space associated with MBS (e.g., SearchSpaceBroadcast IE). In some aspects, a first common search space (CSS) type can be configured for MCCH and MTCH. For the primary cell (Pcell), a second type (e.g., Type0B-PDCCH) CSS set can be configured for MCCH and MTCH, for example, via SIB (e.g., "SIBx") and / or MCCH. For the secondary cell (Scell) associated with a connected UE (e.g., a UE in RRC connection mode), a third type (e.g., Type3-PDCCH) CSS set can be configured for MCCH and MTCH, for example, via unicast RRC. In some aspects, the search space associated with MBS (e.g., SearchSpaceBroadcast IE) can also be associated with DCI (e.g., DCI may be included). In some aspects, DCI can indicate the PDCCH used for MCCH and / or MTCH. In some respects, the DCI indicating the PDCCH used for MCCH and / or MTCH can be transmitted via CSS and can be scrambled using an MBS-specific format and / or by an MBS-specific RNTI (e.g., G-RNTI, GC-RNTI, TG-RNTI, etc.). The MBS-specific format can be based on a known format (e.g., it can include the same type of information using the same bits) or it can be a newly defined DCI format or type.

[0091] Figure 7 This is a call flow diagram 700 illustrating a base station configuration associated with a group of UEs (User Equipment) and an MBS (Multi-User Base Station) according to some aspects of this disclosure. Base station 702 (e.g., as an example of a network device or network node that may include one or more components of a decomposed base station) can send, and the group of UEs 704 (e.g., as an example of a wireless device) can receive, a set of one or more messages 706, which includes configuration information for at least one of multicast or broadcast resources for the MBS. In some aspects, to send the set of one or more messages 706, base station 702 may include a first component that generates the set of one or more messages 706 and outputs the set of one or more messages 706 for transmission by a second component of the base station.

[0092] In some aspects, the group of UEs 704 may be in an inactive state or an idle state (e.g., RRC inactive state). In some aspects, the group of UEs 704 may be a group of first-type RedCap UEs (e.g., multiple UEs implementing the first type of RedCap) supporting a first capability with a first maximum bandwidth (e.g., 5MHz), which differs from a second capability with a second maximum bandwidth greater than the first maximum bandwidth (e.g., 100MHz or 20MHz). In some aspects, the configuration information may include a first indication of a first CFR associated with at least one of the MCCH or MTCH used for the group of first-type RedCap UEs. In some aspects, the first indication may be included in the SIB. In some aspects, the first CFR may be based on the first capability.

[0093] The second capability can be a non-RedCap (e.g., alternatively referred to as a full or standard capability), and a second CFR for MBS can be specified for a set of non-RedCap UEs (not shown). In some aspects, the second capability can be a second type of RedCap supporting the second capability. The set of one or more messages 706 can include indications of different CFRs for different types of RedCap UEs supporting the first capability. For example, different types of complexity reduction methods can be adopted in conjunction with the first capability (e.g., using a reduced total PRB for PDSCH or a reduced BB BW for PUSCH, as per the context). Figure 5 (as described).

[0094] In some respects, the first CFR can be associated with at least one of the MCCH or MTCH used for multiple types of RedCap UEs. In some respects, multiple types of RedCap UEs can be defined (or differentiated) based on at least one different value of a set of parameters associated with the type of RedCap (or the type of RedCap UE), while the same CFR can be shared based on supporting the same maximum bandwidth (e.g., supporting a first capability). For example, a first type of RedCap (e.g., an enhanced RedCap or eRedCap of the first type defined for Rel 18) can support the same maximum bandwidth as a second type of RedCap (e.g., an eRedCap of the second type defined for Rel 18 or a RedCap of the second type defined for Rel 17) to reduce complexity.

[0095] In some respects, the first CFR may differ from the second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs (e.g., a second group of RedCap UEs) that support a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth.

[0096] In some aspects, the group of one or more messages 706 may further include a first MCCH configuration for a first type of RedCap UE, which differs from a second MCCH configuration for a second type of RedCap UE. In some aspects, the first MCCH configuration specifies at least one of a first periodicity of the MCCH resource or a first offset associated with the MCCH, which differs from a second periodicity of the MCCH resource or an associated second offset specified by the second MCCH configuration. In some aspects, the group of one or more messages 706 may include a first MTCH configuration for a first type of RedCap UE, which differs from a second MTCH configuration for a second type of RedCap UE. In some aspects, the first MTCH configuration may include additional indications of at least one of a first rate matching (RM), a first finite buffer RM (LBRM), or a first set of reference signals (RS) configuration associated with the MTCH, which differs from a second RM, second LBRM, or second set of RS configuration associated with the second MTCH configuration.

[0097] In some aspects, the group of one or more messages 706 may include a first discontinuous reception (DRX) configuration associated with a first type of RedCap UE (e.g., associated with one or more DRX-Config elements), which differs from a second DRX configuration for a second type of RedCap UE. For example, the first DRX configuration may be associated with one or more of the following: a first cycle for a DRX cycle (e.g., a cycle including on / wake-up / active and off / sleep / inactive states), a first duration for an on or wake-up state (e.g., drx-onDuration), a first DRX inactivity time (e.g., drx-InactivityTimer), or other first parameter values ​​for other DRX parameters (e.g., drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-SlotOffset, etc.). In some aspects, the second DRX configuration may be associated with one or more of the following: a second cycle for a DRX loop, a second duration for an on or wake-up state, a second DRX inactivity period, or another second parameter value for other DRX parameters. In some aspects, the first DRX configuration and the second DRX configuration may include one of the same set of elements having one or more different associated values, or one of different sets of elements having associated values ​​for overlapping elements that may be the same or different.

[0098] In some aspects, the group of one or more messages 706 may include a configuration (e.g., mbs-NeighbourCellList IE) of a first neighboring cell list having ongoing multicast or broadcast communication sessions associated with a first type of RedCap UE, which is different from a second neighboring cell list having ongoing multicast or broadcast communication sessions associated with a second type of RedCap UE. In some aspects, the group of one or more messages 706 may include a second indication of a first ongoing multicast or broadcast communication session list associated with a first G-RNTI associated with an MTCH for a first type of RedCap UE, which is different from a second ongoing multicast or broadcast communication session list associated with a second G-RNTI associated with an MTCH for a second type of RedCap UE. In some aspects, the group of one or more messages 706 may include a third indication (e.g., mtch-NeighbourCell IE) of a first MTCH neighboring cell configuration for a first G-RNTI, which is different from a second MTCH neighboring cell configuration for a second G-RNTI.

[0099] Based on one or more messages 706 in this set of UEs 704, UEs in this set of UEs can monitor the MCCH (or PDCCH) at 708. In some aspects, monitoring the MCCH (or PDCCH) may include monitoring a configured first CFR. In some aspects, monitoring at 708 may be based on a first DRX configuration. In some aspects, monitoring at 708 may be limited to MTCH (or PDSCH) timings spanning no more than 5 MHz (e.g., limited to a 5 MHz span).

[0100] In some aspects, when the group of UEs 704 monitors the MCCH (or PDCCH), the base station 702 may transmit the MCCH (or PDCCH) 710, and the group of UEs 704 may receive the MCCH (or PDCCH). In some aspects, the MCCH (or PDCCH) 710 may involve one or more multicast or broadcast transmissions for a first type of RedCap UE or for a non-RedCap UE supporting a second maximum bandwidth or a second type of RedCap UE supporting either a second maximum bandwidth or a third maximum bandwidth (e.g., it may be associated with a G-RNTI or MCCH-RNTI associated with MTCH and / or PDSCH communication). For example, the MCCH (or PDCCH) 710 may schedule MTCH (or PDSCH) communication 712 via a set of frequency resources spanning a set of frequency resources less than the first maximum bandwidth (e.g., indicated in a first frequency domain resource allocation (FDRA)).

[0101] In some aspects, at 714, base station 702 can transmit, and the group of UEs 704 can receive (and decode) MTCH (or PDSCH) communications 712 for multiple RedCap UEs (e.g., first-type RedCap UEs) scheduled by MCCH (or PDCCH) 710. In some aspects, MTCH (or PDSCH) communications 712 for multiple RedCap UEs (e.g., first-type RedCap UEs) can be associated with a group of PRBs spanning less than 5 MHz (e.g., a group of consecutive or non-consecutive PRBs spanning less than 5 MHz). In some aspects, the group of PRBs (e.g., PRB 530 or BB BW 580) can be distributed within a larger RF BW (e.g., RF BW 520 or 570) supported by the group of UEs 704 (or by first-type RedCap UEs).

[0102] Additionally or alternatively, MCCH (or PDCCH) 710 may schedule MTCH (or PDSCH) communication 716 via a set of frequency resources spanning a set of frequency resources greater than a first maximum bandwidth (e.g., indicated in a second FDRA). Based on the scheduled MTCH (or PDSCH) communication 716 having frequency resources spanning more than the first maximum bandwidth, the set of UEs 704 may skip decoding of the MTCH (or PDSCH) communication 716 at 718.

[0103] Figure 8 This is a flowchart of a wireless communication method, 800. The method can be performed by a wireless device such as a UE (e.g., UEs 104, 420, 425; UEs in the group of UEs 704; device 1204). At 802, the UE can receive a first indication of a CFR associated with at least one of the MCCH or MTCH of a plurality of RedCap UEs in an inactive or idle state, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, which differs from a second capability having a second maximum bandwidth greater than the first maximum bandwidth. For example, 802 can be performed by… Figure 12The application processor 1206, cellular baseband processor 1224, transceiver 1222, antenna 1280, and / or eRedCap MBS component 198 are executed. In some aspects, the UE (and other UEs among a plurality of RedCap UEs) may be a first type of RedCap UE (e.g., a UE implementing the first type of RedCap) that supports a first capability having a first maximum bandwidth (e.g., 5 MHz), which is different from a second capability having a second maximum bandwidth (e.g., 100 MHz or 20 MHz) greater than the first maximum bandwidth. In some aspects, a first indication may be included in the SIB. In some aspects, a first CFR may be based on the first capability. A CFR may be a first CFR that is different from a second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs that support a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth.

[0104] The second capability can be non-RedCap (e.g., alternatively referred to as full or standard capability), and a second CFR for MBS can be specified for a set of non-RedCap UEs. In some aspects, the second capability can be a second type of RedCap supporting the second capability. The first indication can be included in a set of indications for different CFRs for different types of RedCap UEs supporting the first capability. For example, different types of complexity reduction methods can be adopted in conjunction with the first capability (e.g., using a reduced total PRB for PDSCH or a reduced BB BW for PUSCH, as per the previous section). Figure 5 (as described).

[0105] In some aspects, the first CFR can be associated with at least one of the MCCH or MTCH used for multiple types of RedCap UEs. In some aspects, the multiple types of RedCap UEs can be defined based on at least one different value from a set of parameters associated with the type of RedCap (or the type of RedCap UE), and the same CFR can be shared based on supporting the same maximum bandwidth (e.g., supporting a first capability). For example, a first-type RedCap device (e.g., a first-type enhanced RedCap or eRedCap device) can support the same maximum bandwidth as a second-type RedCap device (e.g., a second-type eRedCap device or a second-type RedCap device) to reduce complexity.

[0106] In some respects, the first CFR may differ from the second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs (e.g., a second group of RedCap UEs) that support a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth. See, for example, [link to relevant documentation]. Figure 7 The UE in the group of UEs 704 can receive one or more messages 706 that may include a first indication.

[0107] In some aspects, receiving a first indication of CFR at 802 may include receiving a first MCCH configuration (or associated therewith) for a first type of RedCap UE, which differs from a second MCCH configuration for a second type of RedCap UE. In some aspects, the first MCCH configuration may specify at least one of a first periodicity of the MCCH resource or a first offset associated with the MCCH, which may differ from a second periodicity of the MCCH resource specified by the second MCCH configuration or an associated second offset. See, for example, [link to documentation]. Figure 7 The UEs in this group of UEs 704 can receive one or more messages 706 that may include the first MCCH configuration.

[0108] In some aspects, receiving a first instruction to the CFR at 802 may include receiving a first MTCH configuration (or associated therewith) for a first type of RedCap UE, which differs from a second MTCH configuration for a second type of RedCap UE. The first MTCH configuration includes at least one of a first RM, a first LBRM, or a first set of RS configurations associated with the MTCH, which differs from a second RM, a second LBRM, or a second set of RS configurations associated with the second MTCH configuration. See, for example, [link to documentation]. Figure 7 The UEs in this group of UEs 704 can receive one or more messages 706 that may include the first MTCH configuration.

[0109] In some aspects, receiving a first instruction to the CFR at 802 may include receiving (or being associated with) a configuration of a first neighboring cell list having ongoing multicast or broadcast communication sessions associated with a first type of RedCap UE, which is different from a second neighboring cell list having ongoing multicast or broadcast communication sessions associated with a second type of RedCap UE. See also Figure 7 For example, a UE in the group of UEs 704 can receive one or more messages 706 that may include a first list of neighboring cells.

[0110] In some aspects, receiving a first indication of CFR at 802 may include receiving a second indication (or associated therewith) of a first ongoing multicast or broadcast communication session list associated with a first G-RNTI associated with an MTCH for a first type of RedCap UE, which is different from a second ongoing multicast or broadcast communication session list associated with a second G-RNTI associated with an MTCH for a second type of RedCap UE. In some aspects, PDSCH (or MTCH) communication scheduled by a PDCCH (or MCCH) associated with at least one of a G-RNTI or MCCH-RNTI may be associated with a set of PRBs spanning less than a first maximum bandwidth (e.g., 5 MHz), which is associated with an MTCH for a UE (or multiple RedCap UEs). See, for example, [link to relevant documentation]. Figure 7 The UE in the group of UEs 704 can receive one or more messages 706 that may include a second indication.

[0111] In some aspects, receiving a first indication of CFR at 802 may include receiving (or being associated with) a third indication of (or related to) a first MTCH neighbor cell configuration for a first G-RNTI, which differs from a second MTCH neighbor cell configuration for a second G-RNTI. See also Figure 7 For example, a UE in the group of UEs 704 can receive one or more messages 706 that may include a third indication.

[0112] In some aspects, receiving a first indication of CFR at 802 may include receiving (or being associated with) a first DRX configuration for a first type of RedCap UE, which differs from a second DRX configuration for a second type of RedCap UE. See also Figure 7 For example, a UE in the group of UEs 704 can receive one or more messages 706 that may include a first DRX configuration.

[0113] At point 816, the UE can monitor the CFR (Continuous Frequency Response) for at least one of broadcast or multicast services indicated in the first indication. In some aspects, monitoring the CFR at point 816 may include skipping decoding of the PDSCH based on the PDSCH having frequency resources spanning beyond a first maximum bandwidth. In some aspects, monitoring the CFR at point 816 may include monitoring PDSCH timings limited to a span of the first maximum bandwidth (e.g., 5 MHz) based on a first DRX configuration. For example, point 816 may be... Figure 12The application processor 1206, cellular baseband processor 1224, transceiver 1222, antenna 1280, and / or eRedCap MBS component 198 are executed. See also Figure 7 For example, a UE in this group of UEs 704 can monitor MCCH (or PDCCH) 710 at 708, can monitor (and can receive (and decode) MTCH (or PDSCH) communication 712 at 714, or can monitor MTCH (or PDSCH) communication 716 (and can skip decoding at 718). Figure 8

[0114] Figure 9 This is a flowchart of a wireless communication method, 900. The method can be performed by a wireless device such as a UE (e.g., UEs 104, 420, 425; UE in the group of UEs 704; device 1204). At 902, the UE can receive a first indication of a CFR associated with at least one of the MCCH or MTCH of a plurality of RedCap UEs in an inactive or idle state, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, which differs from a second capability having a second maximum bandwidth greater than the first maximum bandwidth. For example, 902 can be performed by… Figure 12 The application processor 1206, cellular baseband processor 1224, transceiver 1222, antenna 1280, and / or eRedCap MBS component 198 are executed. In some aspects, the UE (and other UEs among a plurality of RedCap UEs) may be a first type of RedCap UE (e.g., a UE implementing the first type of RedCap) that supports a first capability having a first maximum bandwidth (e.g., 5 MHz), which is different from a second capability having a second maximum bandwidth (e.g., 100 MHz or 20 MHz) greater than the first maximum bandwidth. In some aspects, a first indication may be included in the SIB. In some aspects, a first CFR may be based on the first capability. A CFR may be a first CFR that is different from a second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs that support a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth.

[0115] The second capability can be non-RedCap (e.g., alternatively referred to as full or standard capability), and a second CFR for MBS can be specified for a set of non-RedCap UEs. In some aspects, the second capability can be a second type of RedCap supporting the second capability. The first indication can be included in a set of indications for different CFRs for different types of RedCap UEs supporting the first capability. For example, different types of complexity reduction methods can be adopted in conjunction with the first capability (e.g., using a reduced total PRB for PDSCH or a reduced BB BW for PUSCH, as per the previous section). Figure 5 (as described).

[0116] In some aspects, the first CFR can be associated with at least one of the MCCH or MTCH used for multiple types of RedCap UEs. In some aspects, the multiple types of RedCap UEs can be defined based on at least one different value from a set of parameters associated with the type of RedCap (or the type of RedCap UE), and the same CFR can be shared based on supporting the same maximum bandwidth (e.g., supporting a first capability). For example, a first type of RedCap (e.g., a first type of enhanced RedCap or eRedCap device) can support the same maximum bandwidth as a second type of RedCap (e.g., a second type of eRedCap device or a second type of RedCap device) to reduce complexity.

[0117] In some respects, the first CFR may differ from the second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs (e.g., a second group of RedCap UEs) that support a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth. See, for example, [link to relevant documentation]. Figure 7 The UE in the group of UEs 704 can receive one or more messages 706 that may include a first indication.

[0118] In some aspects, receiving the first indication of CFR at 902 may include receiving (or associating with) a first MCCH configuration for a first type of RedCap UE at 904, which differs from a second MCCH configuration for a second type of RedCap UE. For example, 904 may be... Figure 12The application processor 1206, cellular baseband processor 1224, transceiver 1222, antenna 1280, and / or eRedCap MBS component 198 execute. In some aspects, the first MCCH configuration may specify at least one of a first periodicity of the MCCH resource or a first offset associated with the MCCH, which may differ from a second periodicity of the MCCH resource or an associated second offset specified by the second MCCH configuration. For example, see... Figure 7 The UEs in this group of UEs 704 can receive one or more messages 706 that may include the first MCCH configuration.

[0119] In some aspects, receiving the first instruction to the CFR at 902 may include receiving (or being associated with) a first MTCH configuration for a first type of RedCap UE at 906, which differs from a second MTCH configuration for a second type of RedCap UE. For example, 906 may be... Figure 12 The application processor 1206, cellular baseband processor 1224, transceiver 1222, antenna 1280, and / or eRedCap MBS component 198 execute. The first MTCH configuration includes at least one of a first RM, first LBRM, or first set of RS configurations associated with the MTCH, wherein the first RM, first LBRM, or first set of RS configurations differs from the second RM, second LBRM, or second set of RS configurations associated with the second MTCH configuration. See, for example. Figure 7 The UEs in this group of UEs 704 can receive one or more messages 706 that may include the first MTCH configuration.

[0120] In some aspects, receiving a first instruction to the CFR at 902 may include receiving (or being associated with) a configuration at 908 of a first neighboring cell list having ongoing multicast or broadcast communication sessions associated with a first type of RedCap UE, which is different from a second neighboring cell list having ongoing multicast or broadcast communication sessions associated with a second type of RedCap UE. For example, 908 may be... Figure 12 The application processor 1206, cellular baseband processor 1224, transceiver 1222, antenna 1280, and / or eRedCap MBS component 198 are executed. See also Figure 7 For example, a UE in the group of UEs 704 can receive one or more messages 706 that may include a first list of neighboring cells.

[0121] In some aspects, receiving a first indication of CFR at 902 may include receiving at 910 a second indication (or associated therewith) of a list of first ongoing multicast or broadcast communication sessions associated with a first G-RNTI associated with an MTCH for a first type of RedCap UE, which is different from a list of second ongoing multicast or broadcast communication sessions associated with a second G-RNTI associated with an MTCH for a second type of RedCap UE. For example, 910 may be by Figure 12 The application processor 1206, cellular baseband processor 1224, transceiver 1222, antenna 1280, and / or eRedCap MBS component 198 perform this. In some aspects, PDSCH (or MTCH) communication scheduled by a PDCCH (or MCCH) associated with at least one of G-RNTI or MCCH-RNTI can be associated with a set of PRBs spanning less than a first maximum bandwidth (e.g., 5 MHz), the G-RNTI or MCCH-RNTI being associated with an MTCH for the UE (or multiple RedCap UEs). See, for example, [link to relevant documentation]. Figure 7 The UE in the group of UEs 704 can receive one or more messages 706 that may include a second indication.

[0122] In some aspects, receiving a first indication of the CFR at 902 may include receiving (or being associated with) a third indication at 912 of a first MTCH neighbor cell configuration for a first G-RNTI, which differs from a second MTCH neighbor cell configuration for a second G-RNTI. For example, 912 may be... Figure 12 The application processor 1206, cellular baseband processor 1224, transceiver 1222, antenna 1280, and / or eRedCap MBS component 198 are executed. See also Figure 7 For example, a UE in the group of UEs 704 can receive one or more messages 706 that may include a third indication.

[0123] In some aspects, receiving the first indication of CFR at 902 may include receiving at 914 a first DRX configuration associated with (or related to) a first type of RedCap UE, which differs from a second DRX configuration for a second type of RedCap UE. For example, 914 may be... Figure 12 The application processor 1206, cellular baseband processor 1224, transceiver 1222, antenna 1280, and / or eRedCap MBS component 198 are executed. See also Figure 7For example, a UE in the group of UEs 704 can receive one or more messages 706 that may include a first DRX configuration.

[0124] At 916, the UE can monitor the CFR (Continuous Frequency Response) for at least one of broadcast or multicast services indicated in the first indication. In some aspects, monitoring the CFR at 916 may include skipping decoding of the PDSCH at 918 based on the PDSCH having frequency resources spanning beyond a first maximum bandwidth. In some aspects, monitoring the CFR at 916 may include monitoring PDSCH timings limited to a span of the first maximum bandwidth (e.g., 5 MHz) at 920 based on a first DRX configuration. For example, 916, 918, and 920 may be... Figure 12 The application processor 1206, cellular baseband processor 1224, transceiver 1222, antenna 1280, and / or eRedCap MBS component 198 are executed. See also Figure 7 For example, a UE in this group of UEs 704 can monitor MCCH (or PDCCH) 710 at 708, can monitor (and can receive (and decode) MTCH (or PDSCH) communication 712 at 714, or can monitor MTCH (or PDSCH) communication 716 (and can skip decoding at 718).

[0125] Figure 10 This is a flowchart 1000 of a wireless communication method. The method can be performed by a network node or network device such as a base station (e.g., base stations 102, 412, 414, 702; network entities 1202, 1302). At 1002, the base station can output (for transmission to one of a plurality of RedCap UEs in an inactive or idle state, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, which is different from a second capability having a second maximum bandwidth greater than the first maximum bandwidth) and / or can send to the plurality of RedCap UEs a first indication of a CFR associated with at least one of the MCCH or MTCH used for the plurality of RedCap UEs. For example, 1002 can be performed by Figure 13The CU processor 1312, DU processor 1332, RU processor 1342, transceiver 1346, antenna 1380, and / or eRedCap MBS configuration component 199 are executed. In some aspects, the plurality of RedCap UEs may be a first type of RedCap UE (e.g., a UE implementing the first type of RedCap) supporting a first capability having a first maximum bandwidth (e.g., 5 MHz), which is different from a second capability having a second maximum bandwidth (e.g., 100 MHz or 20 MHz) greater than the first maximum bandwidth. In some aspects, a first indication may be included in the SIB. In some aspects, a first CFR may be based on the first capability. A CFR may be a first CFR different from a second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs supporting a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth.

[0126] The second capability can be non-RedCap (e.g., full or standard capability), and a second CFR can be specified for a set of non-RedCap UEs for MBS. In some aspects, the second capability can be a second type of RedCap supporting the second capability. The first indication can be included in a set of indications for different CFRs for different types of RedCap UEs supporting the first capability. For example, the first capability can be combined to employ different types of complexity reduction methods (e.g., using a reduced total PRB for PDSCH or a reduced BB BW for PUSCH, as per the previous section). Figure 5 (as described).

[0127] In some respects, the first CFR can be associated with at least one of the MCCH or MTCH used for multiple types of RedCap UEs. In some respects, multiple types of RedCap UEs can be defined based on at least one different value from a set of parameters associated with the type of RedCap (or the type of RedCap UE), and the same CFR can be shared based on supporting the same maximum bandwidth (e.g., supporting a first capability). For example, a first type of RedCap (e.g., a first type of enhanced RedCap or eRedCap device) can support the same maximum bandwidth as a second type of RedCap (e.g., a second type of eRedCap or a second type of RedCap device defined for Rel 18) to reduce complexity.

[0128] In some respects, the first CFR may differ from the second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs (e.g., a second group of RedCap UEs) that support a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth. See, for example, [link to relevant documentation]. Figure 7 The base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include a first indication.

[0129] In some aspects, the first indication of CFR output at 1002 may include output (for transmission to multiple RedCap UEs) for a first type of RedCap UE (or associated with it), which differs from a second MCCH configuration for a second type of RedCap UE. In some aspects, the first MCCH configuration may specify at least one of a first periodicity of the MCCH resource or a first offset associated with the MCCH, which may differ from a second periodicity of the MCCH resource or an associated second offset specified by the second MCCH configuration. See, for example, [link to relevant documentation]. Figure 7 The base station 702 may output (for transmission to multiple RedCap UEs) and / or transmit one or more messages 706 that may include the first MCCH configuration.

[0130] In some aspects, the first indication of CFR output at 1002 may include output (for transmission to multiple RedCap UEs) for a first MTCH configuration (or associated therewith) for a first type of RedCap UE, which differs from a second MTCH configuration for a second type of RedCap UE. The first MTCH configuration includes at least one of a first RM, a first LBRM, or a first set of RS configurations associated with the MTCH, which differs from a second RM, a second LBRM, or a second set of RS configurations associated with the second MTCH configuration. See, for example, [link to relevant documentation]. Figure 7 The base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include the first MTCH configuration.

[0131] In some aspects, the first indication of CFR output at 1002 may include an output (for transmission to multiple RedCap UEs) configured (or associated with) a first neighboring cell list having ongoing multicast or broadcast communication sessions associated with a first type of RedCap UE, which is different from a second neighboring cell list having ongoing multicast or broadcast communication sessions associated with a second type of RedCap UE. See also Figure 7 For example, base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include a first list of neighboring cells.

[0132] In some aspects, the first indication of CFR output at 1002 may include an output (for transmission to multiple RedCap UEs) of a second indication (or associated therewith) of a first ongoing multicast or broadcast communication session list associated with a first G-RNTI associated with an MTCH for a first type of RedCap UE, which is different from a second ongoing multicast or broadcast communication session list associated with a second G-RNTI associated with an MTCH for a second type of RedCap UE. In some aspects, PDSCH (or MTCH) communication scheduled by a PDCCH (or MCCH) associated with at least one of a G-RNTI or MCCH-RNTI may be associated with a set of PRBs spanning less than a first maximum bandwidth (e.g., 5 MHz), which is associated with an MTCH for a base station (or multiple RedCap UEs). See, for example, [link to relevant documentation]. Figure 7 The base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include a second instruction.

[0133] In some respects, the first indication to CFR output at 1002 may include an output (for transmission to multiple RedCap UEs) of a third indication (or associated therewith) of the configuration of a first MTCH neighboring cell for a first G-RNTI, which differs from the configuration of a second MTCH neighboring cell for a second G-RNTI. See also Figure 7 For example, base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include a third instruction.

[0134] In some respects, the first indication of CFR output at 1002 may include output (for transmission to multiple RedCap UEs) to a first DRX configuration associated with a first type of RedCap UE, which differs from a second DRX configuration for a second type of RedCap UE. See also Figure 7 For example, base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include the first DRX configuration.

[0135] At 1016, the base station may output (for transmission to multiple RedCap UEs) via a CFR (Content Flow Chart) for at least one of broadcast or multicast services as indicated in the first indication, and / or may transmit at least one of MCCH or MTCH communications. In some aspects, outputting at least one of MCCH or MTCH communications at 1016 may include outputting (or transmitting) a PDSCH having a frequency resource spanning a first maximum bandwidth (e.g., associated with or transmitted via that frequency resource). In some aspects, outputting at least one of MCCH or MTCH communications at 1016 may include outputting (or transmitting) one or more PDSCH timings limited to a span of the first maximum bandwidth (e.g., 5 MHz). For example, 1016 may be... Figure 13 The CU processor 1312, DU processor 1332, RU processor 1342, transceiver 1346, antenna 1380, and / or eRedCap MBS configuration component 199 are executed. See also Figure 7 For example, base station 702 may output (for transmission to the group of UEs 704) and / or may transmit MCCH (or PDCCH) 710, MTCH (or PDSCH) communication 712 or MTCH (or PDSCH) communication 716.

[0136] Figure 11 This is a flowchart 1100 of a wireless communication method. The method can be performed by a network node or network device such as a base station (e.g., base stations 102, 412, 414, 702; network entities 1202, 1302). At 1102, the base station can output (for transmission to multiple RedCap UEs in an inactive or idle state, the multiple RedCap UEs supporting a first capability with a first maximum bandwidth, which is different from a second capability with a second maximum bandwidth greater than the first maximum bandwidth) and / or can send to the multiple RedCap UEs a first indication of a CFR associated with at least one of the MCCH or MTCH used for the multiple RedCap UEs. For example, 1102 can be performed by... Figure 13The CU processor 1312, DU processor 1332, RU processor 1342, transceiver 1346, antenna 1380, and / or eRedCap MBS configuration component 199 are executed. In some aspects, the plurality of RedCap UEs may be a first type of RedCap UE (e.g., a UE implementing the first type of RedCap) supporting a first capability having a first maximum bandwidth (e.g., 5 MHz), which is different from a second capability having a second maximum bandwidth (e.g., 100 MHz or 20 MHz) greater than the first maximum bandwidth. In some aspects, a first indication may be included in the SIB. In some aspects, a first CFR may be based on the first capability. A CFR may be a first CFR different from a second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs supporting a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth.

[0137] The second capability can be non-RedCap (e.g., full or standard capability), and a second CFR can be specified for a set of non-RedCap UEs for MBS. In some aspects, the second capability can be a second type of RedCap supporting the second capability. The first indication can be included in a set of indications for different CFRs for different types of RedCap UEs supporting the first capability. For example, the first capability can be combined to employ different types of complexity reduction methods (e.g., using a reduced total PRB for PDSCH or a reduced BB BW for PUSCH, as per the previous section). Figure 5 (as described).

[0138] In some respects, the first CFR can be associated with at least one of the MCCH or MTCH used for multiple types of RedCap UEs. In some respects, multiple types of RedCap UEs can be defined based on at least one different value from a set of parameters associated with the type of RedCap (or the type of RedCap UE), and the same CFR can be shared based on supporting the same maximum bandwidth (e.g., supporting a first capability). For example, a first type of RedCap (e.g., a first type of enhanced RedCap or eRedCap device) can support the same maximum bandwidth as a second type of RedCap (e.g., a second type of eRedCap or a second type of RedCap device defined for Rel 18) to reduce complexity.

[0139] In some respects, the first CFR may differ from the second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs (e.g., a second group of RedCap UEs) that support a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth. See, for example, [link to relevant documentation]. Figure 7 The base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include a first indication.

[0140] In some respects, the first indication of CFR output at 1102 may include an output at 1104 (for transmission to multiple RedCap UEs) of a first MCCH configuration (or associated therewith) for a first type of RedCap UE, which differs from a second MCCH configuration for a second type of RedCap UE. For example, 1104 may be... Figure 13 The CU processor 1312, DU processor 1332, RU processor 1342, transceiver 1346, antenna 1380, and / or eRedCap MBS configuration component 199 perform this. In some aspects, the first MCCH configuration may specify at least one of a first periodicity of the MCCH resource or a first offset associated with the MCCH, which may differ from a second periodicity of the MCCH resource or an associated second offset specified by the second MCCH configuration. For example, see... Figure 7 The base station 702 may output (for transmission to multiple RedCap UEs) and / or transmit one or more messages 706 that may include the first MCCH configuration.

[0141] In some respects, the first indication of CFR output at 1102 may include an output at 1106 (for transmission to multiple RedCap UEs) of a first MTCH configuration (or associated therewith) for a first type of RedCap UE, which differs from a second MTCH configuration for a second type of RedCap UE. For example, 1106 may be provided by Figure 13 The CU processor 1312, DU processor 1332, RU processor 1342, transceiver 1346, antenna 1380, and / or eRedCap MBS configuration component 199 are executed. The first MTCH configuration includes at least one of a first RM, first LBRM, or first set of RS configurations associated with the MTCH, wherein the first RM, first LBRM, or first set of RS configurations differs from the second RM, second LBRM, or second set of RS configurations associated with the second MTCH configuration. See, for example, [link to example]. Figure 7The base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include the first MTCH configuration.

[0142] In some aspects, the first indication to the CFR output at 1102 may include a configuration (or associated therewith) at 1108 (for transmission to multiple RedCap UEs) of a first neighboring cell list having ongoing multicast or broadcast communication sessions associated with a first type of RedCap UE, which is different from a second neighboring cell list having ongoing multicast or broadcast communication sessions associated with a second type of RedCap UE. For example, 1108 may be provided by Figure 13 The CU processor 1312, DU processor 1332, RU processor 1342, transceiver 1346, antenna 1380, and / or eRedCap MBS configuration component 199 are executed. See also Figure 7 For example, base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include a first list of neighboring cells.

[0143] In some aspects, the first indication to CFR output at 1102 may include a second indication (or associated therewith) output at 1110 (for transmission to multiple RedCap UEs) to a list of first ongoing multicast or broadcast communication sessions associated with a first G-RNTI associated with an MTCH for a first type of RedCap UE, which is different from the list of second ongoing multicast or broadcast communication sessions associated with a second G-RNTI associated with an MTCH for a second type of RedCap UE. For example, 1110 may be by Figure 13 The CU processor 1312, DU processor 1332, RU processor 1342, transceiver 1346, antenna 1380, and / or eRedCap MBS configuration component 199 perform this. In some aspects, PDSCH (or MTCH) communication scheduled by a PDCCH (or MCCH) associated with at least one of G-RNTI or MCCH-RNTI can be associated with a set of PRBs spanning less than a first maximum bandwidth (e.g., 5 MHz), the G-RNTI or MCCH-RNTI being associated with an MTCH for a base station (or multiple RedCap UEs). See, for example, [link to relevant documentation]. Figure 7 The base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include a second instruction.

[0144] In some aspects, the first indication to CFR output at 1102 may include a third indication (or associated therewith) output at 1112 (for transmission to multiple RedCap UEs) to the configuration of a first MTCH neighboring cell for a first G-RNTI, which differs from the configuration of a second MTCH neighboring cell for a second G-RNTI. For example, 1112 may be... Figure 13 The CU processor 1312, DU processor 1332, RU processor 1342, transceiver 1346, antenna 1380, and / or eRedCap MBS configuration component 199 are executed. See also Figure 7 For example, base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include a third instruction.

[0145] In some respects, the first indication of CFR output at 1102 may include the output at 1114 (for transmission to multiple RedCap UEs) of a first DRX configuration associated with a first type of RedCap UE, which differs from the second DRX configuration for a second type of RedCap UE. For example, 1114 may be... Figure 13 The CU processor 1312, DU processor 1332, RU processor 1342, transceiver 1346, antenna 1380, and / or eRedCap MBS configuration component 199 are executed. See also Figure 7 For example, base station 702 may output (for transmission to the group of UEs 704) and / or may transmit one or more messages 706 that may include the first DRX configuration.

[0146] At 1116, the base station may output (for transmission to multiple RedCap UEs) via a CFR (for broadcast or multicast services) indicated in the first indication and / or may transmit at least one of MCCH or MTCH communications. In some aspects, outputting at least one of MCCH or MTCH communications at 1116 may include outputting (or transmitting) a PDSCH at 1118 having a frequency resource spanning a first maximum bandwidth (e.g., associated with or transmitted via that frequency resource). In some aspects, outputting at least one of MCCH or MTCH communications at 1116 may include outputting (or transmitting) one or more PDSCH timings at 1120 with a span limited to the first maximum bandwidth (e.g., 5 MHz). For example, 1116, 1118, and 1120 may be... Figure 13The CU processor 1312, DU processor 1332, RU processor 1342, transceiver 1346, antenna 1380, and / or eRedCap MBS configuration component 199 are executed. See also Figure 7 For example, base station 702 may output (for transmission to the group of UEs 704) and / or may transmit MCCH (or PDCCH) 710, MTCH (or PDSCH) communication 712 or MTCH (or PDSCH) communication 716.

[0147] Figure 12Figure 1200 illustrates an example of a hardware implementation for device 1204. Device 1204 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1204 may include at least one cellular baseband processor 1224 (also referred to as a modem) coupled to one or more transceivers 1222 (e.g., cellular RF transceivers). Cellular baseband processor 1224 may include at least one on-chip memory 1224'. In some aspects, device 1204 may also include one or more Subscriber Identity Module (SIM) cards 1220 and at least one application processor 1206 coupled to a Secure Digital Card (SD) card 1208 and a screen 1210. Application processor 1206 may include on-chip memory 1206'. In some aspects, device 1204 may also include a Bluetooth module 1212, a WLAN module 1214, an SPS module 1216 (e.g., a GNSS module), one or more sensor modules 1218 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1226, a power supply 1230, and / or a camera 1232. Bluetooth module 1212, WLAN module 1214, and SPS module 1216 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). Bluetooth module 1212, WLAN module 1214, and SPS module 1216 may include their own dedicated antennas and / or communicate using one or more antennas 1280. Cellular baseband processor 1224 communicates with UE 104 and / or RU associated with network entity 1202 via transceiver 1222 through one or more antennas 1280. Cellular baseband processor 1224 and application processor 1206 may each include computer-readable media / memory 1224', 1206'. Additional memory module 1226 may also be considered as computer-readable media / memory. Each computer-readable media / memory 1224', 1206', 1226 may be non-transitory. Cellular baseband processor 1224 and application processor 1206 are each responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by cellular baseband processor 1224 / application processor 1206, the software causes cellular baseband processor 1224 / application processor 1206 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by cellular baseband processor 1224 / application processor 1206 during software execution.Cellular baseband processor 1224 / application processor 1206 may be a component of UE 350 and may include at least one of memory 360 and / or TX processor 368, RX processor 356 and controller / processor 359. In one configuration, device 1204 may be at least one processor chip (modem and / or application) and may only include cellular baseband processor 1224 and / or application processor 1206, while in another configuration, device 1204 may be the entire UE (e.g., see below). Figure 3 The UE 350 includes an additional module of the device 1204.

[0148] As discussed above, the eRedCap MBS component 198 can be configured to receive a first indication of a CFR associated with at least one of the MCCH or MTCH of a plurality of RedCap UEs in an inactive or idle state, the plurality of RedCap UEs supporting a first capability with a first maximum bandwidth, which differs from a second capability with a second maximum bandwidth greater than the first maximum bandwidth. The eRedCap MBS component 198 can also be configured to monitor the CFR indicated in the first indication for at least one of broadcast or multicast services. The eRedCap MBS component 198 can be within a cellular baseband processor 1224, an application processor 1206, or both. The eRedCap MBS component 198 can be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors can execute the stated process / algorithm individually or in combination. As shown in the figure, device 1204 may include various components configured for various functions. In one configuration, device 1204, and in particular cellular baseband processor 1224 and / or application processor 1206, may include components for receiving a first indication of a CFR associated with at least one of a plurality of RedCap UEs in an inactive or idle state, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, which differs from a second capability having a second maximum bandwidth greater than the first maximum bandwidth. Device 1204, and in particular cellular baseband processor 1224 and / or application processor 1206, may also include components for monitoring the CFR for at least one of broadcast or multicast services indicated in the first indication. Device 1204, and in particular cellular baseband processor 1224 and / or application processor 1206, may also include components for skipping decoding of PDSCH communications based on PDSCH communications having frequency resources spanning beyond the first maximum bandwidth. The device 1204, and in particular the cellular baseband processor 1224 and / or application processor 1206, may also include components for receiving a first MCCH configuration for a first type of RedCap UE, which is different from a second MCCH configuration for a second type of RedCap UE.The apparatus 1204, and in particular the cellular baseband processor 1224 and / or application processor 1206, may also include components for receiving a first MTCH configuration for a first type of RedCap UE, which differs from a second MTCH configuration for a second type of RedCap UE. The apparatus 1204, and in particular the cellular baseband processor 1224 and / or application processor 1206, may also include components for receiving a configuration having a first neighboring cell list having ongoing multicast or broadcast communication sessions associated with the first type of RedCap UE, which differs from a second neighboring cell list having ongoing multicast or broadcast communication sessions associated with the second type of RedCap UE. Apparatus 1204, and in particular cellular baseband processor 1224 and / or application processor 1206, may further include components for receiving a second indication of a first ongoing multicast or broadcast communication session list associated with a first G-RNTI associated with an MTCH for a first type of RedCap UE, the first ongoing multicast or broadcast communication session list being different from a second ongoing multicast or broadcast communication session list associated with a second G-RNTI associated with an MTCH for a second type of RedCap UE. Apparatus 1204, and in particular cellular baseband processor 1224 and / or application processor 1206, may further include components for receiving a third indication of a first MTCH neighboring cell configuration for a first G-RNTI, the first MTCH neighboring cell configuration being different from a second MTCH neighboring cell configuration for a second G-RNTI. Apparatus 1204, and in particular cellular baseband processor 1224 and / or application processor 1206, may further include components for receiving a first DRX configuration associated with a first type of RedCap UE, the first DRX configuration being different from a second DRX configuration for a second type of RedCap UE. Device 1204, and particularly cellular baseband processor 1224 and / or application processor 1206, may also include components for monitoring PDSCH timings across a 5MHz span based on a first DRX configuration. The component may be an eRedCap MBS component 198 of device 1204 configured to perform functions described therein. As described above, device 1204 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the component may be configured to perform functions described therein or in… Figure 8 or Figure 9 The TX processor 368, RX processor 356 and / or controller / processor 359 are functions of any of them.

[0149] Figure 13Figure 1300 illustrates an example of a hardware implementation for network entity 1302. Network entity 1302 may be a BS, a component of a BS, or implement BS functionality. Network entity 1302 may include at least one of CU 1310, DU 1330, or RU 1340. For example, depending on the layer functionality handled by component 199, network entity 1302 may include CU 1310; both CU 1310 and DU 1330; each of CU 1310, DU 1330, and RU 1340; DU 1330; both DU 1330 and RU 1340; or RU 1340. CU 1310 may include at least one CU processor 1312. CU processor 1312 may include on-chip memory 1312'. In some aspects, CU 1310 may also include an additional memory module 1314 and a communication interface 1318. CU1310 communicates with DU 1330 via a midhaul link, such as an F1 interface. DU 1330 may include at least one DU processor 1332. DU processor 1332 may include on-chip memory 1332'. In some aspects, DU 1330 may also include an additional memory module 1334 and a communication interface 1338. DU 1330 communicates with RU 1340 via a fronthaul link. RU 1340 may include at least one RU processor 1342. RU processor 1342 may include on-chip memory 1342'. In some aspects, RU 1340 may also include an additional memory module 1344, one or more transceivers 1346, one or more antennas 1380, and a communication interface 1348. RU 1340 communicates with UE 104. On-chip memories 1312', 1332', 1342' and additional memory modules 1314, 1334, 1344 may each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1312, 1332, and 1342 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor while executing the software.

[0150] As discussed above, the eRedCap MBS configuration component 199 can be configured to output a first indication of a CFR associated with at least one of the MCCH or MTCH of a plurality of RedCap UEs in an inactive or idle state for transmission to the plurality of RedCap UEs, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, which differs from a second capability having a second maximum bandwidth greater than the first maximum bandwidth. The eRedCap MBS configuration component 199 can also be configured to output at least one of the MCCH or MTCH communications via the CFR indicated in the first indication for at least one of broadcast or multicast services for transmission to the plurality of RedCap UEs. The eRedCap MBS configuration component 199 can be located within one or more processors of one or more of CU 1310, DU 1330, and RU 1340. The eRedCap MBS configuration component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of these operations. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1302 may include a variety of components configured for various functions. In one configuration, network entity 1302 may include a component for outputting a first indication of a CFR associated with at least one of the MCCH or MTCH of a plurality of RedCap UEs in an inactive or idle state for transmission to the plurality of RedCap UEs, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, the first capability being different from a second capability having a second maximum bandwidth greater than the first maximum bandwidth. In one configuration, network entity 1302 may include a component for outputting at least one of the MCCH or MTCH communications via a CFR indicated in the first indication for at least one of broadcast or multicast services for transmission to the plurality of RedCap UEs. In one configuration, network entity 1302 may include components for outputting a first MCCH configuration for a first type of RedCap UE to be transmitted to a plurality of RedCap UEs, the first MCCH configuration being different from a second MCCH configuration for a second type of RedCap UE. In another configuration, network entity 1302 may include components for outputting a first MTCH configuration for a first type of RedCap UE to be transmitted to a plurality of RedCap UEs, the first MTCH configuration being different from a second MTCH configuration for a second type of RedCap UE.In one configuration, network entity 1302 may include components for outputting a first neighboring cell list having ongoing multicast or broadcast communication sessions associated with a first type of RedCap UE for transmission to a plurality of RedCap UEs, the first neighboring cell list being different from a second neighboring cell list having ongoing multicast or broadcast communication sessions associated with a second type of RedCap UE. In one configuration, network entity 1302 may include components for outputting a second indication of a first ongoing multicast or broadcast communication session list associated with a first G-RNTI associated with an MTCH for a first type of RedCap UE for transmission to a plurality of RedCap UEs, the first ongoing multicast or broadcast communication session list being different from a second ongoing multicast or broadcast communication session list associated with a second G-RNTI associated with an MTCH for a second type of RedCap UE. In one configuration, network entity 1302 may include components for outputting a third indication of a first MTCH neighboring cell configuration for a first G-RNTI for transmission to a plurality of RedCap UEs, the first MTCH neighboring cell configuration being different from a second MTCH neighboring cell configuration for a second G-RNTI. In one configuration, network entity 1302 may include a component for outputting a first DRX configuration associated with a first type of RedCap UE for transmission to a plurality of RedCap UEs, the first DRX configuration being different from a second DRX configuration for a second type of RedCap UE. The component may be an eRedCap MBS configuration component 199 of network entity 1302 configured to perform the functions described therein. As described above, network entity 1302 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be configured to perform the functions described therein or as per the description of the component. Figure 10 and Figure 11 The functions described are TX processor 316, RX processor 370 and / or controller / processor 375.

[0151] Various aspects of this disclosure generally relate to the MBS configuration for an eRedCap used in an idle or inactive state and supporting a first capability having a first maximum bandwidth, which differs from a second capability having a second maximum bandwidth greater than the first maximum bandwidth. The MBS configuration for the eRedCap may allow an MBS associated with additional complexity reduction beyond that associated with a previous RedCap capability. Some aspects more specifically relate to configuring CFRs (and / or other parameters) associated with the MBS configuration for the eRedCap. In some aspects, the base station may transmit, and the UE (e.g., an eRedCap UE) may receive, an indication of a CFR (or additional parameters) associated with at least one of the MCCH or MTCH of a plurality of RedCap (or eRedCap) UEs supporting the first capability in an inactive or idle state. The base station may then transmit or communicate via the CFR indicated in the first indication for at least one of broadcast or multicast services, and the UE may monitor the transmission or communication.

[0152] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. MBS configuration for RedCap (or eRedCap) used in idle or inactive states and supporting first capabilities can improve the complexity associated with multicast or broadcast communications when an eRedCap UE in an idle or inactive state is performing multicast or broadcast communications.

[0153] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0154] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when…”, do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements, where the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to execute a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices through a set of devices. A device configured to “output” data (such as transmission, signal, or message) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data.A device configured to "acquire" data (such as, transmit, signal, or message) may, for example, receive the data using a transceiver, or may obtain the data from a device that receives the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc., cannot replace the word "component." Therefore, no claim element will be construed as a functional component unless the element is explicitly recited using the phrase "component for..."

[0155] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

[0156] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0157] Aspect 1 is a method of wireless communication at a wireless device, the method comprising: receiving a first indication of a CFR associated with at least one of an MCCH or MTCH for a plurality of RedCap UEs in an inactive or idle state, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, the first capability being different from a second capability having a second maximum bandwidth greater than the first maximum bandwidth; and monitoring the CFR indicated in the first indication for at least one of a broadcast service or a multicast service.

[0158] Aspect 2 is the method according to aspect 1, wherein the CFR is a first CFR different from a second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs, and the one or more RedCap UEs support a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth.

[0159] Aspect 3 is the method according to any one of Aspects 1 and 2, wherein the different CFRs are indicated for different types of RedCap UEs that support the first capability.

[0160] Aspect 4 is the method according to any one of Aspects 1 to 3, wherein the CFR is also associated with at least one of the MCCH or the MTCH for a variety of RedCap UEs.

[0161] Aspect 5 is the method according to aspect 4, the method further comprising skipping the decoding of the PDSCH communication based on the PDSCH communication having frequency resources spanning beyond the first maximum bandwidth.

[0162] Aspect 6 is the method according to any one of aspects 1 to 5, wherein the first indication is included in the SIB.

[0163] Aspect 7 is a method according to any one of Aspects 1 to 6, the method further comprising receiving a first MCCH configuration for a first type of RedCap UE that is different from a second MCCH configuration for a second type of RedCap UE, wherein the first MCCH configuration specifies at least one of a first periodicity of MCCH resources or a first offset associated with the MCCH, the first periodicity or the first offset being different from a second periodicity of MCCH resources or an associated second offset specified by the second MCCH configuration.

[0164] Aspect 8 is the method according to any one of Aspects 1 to 7, the method further comprising receiving a first MTCH configuration for a first type of RedCap UE that is different from a second MTCH configuration for a second type of RedCap UE, wherein the first MTCH configuration includes at least one of a first RM, a first LBRM, or a first set of RS configurations associated with the MTCH, the first RM, first LBRM, or first set of RS configurations being different from the second RM, second LBRM, or second set of RS configurations associated with the second MTCH configuration.

[0165] Aspect 9 is the method according to any one of Aspects 1 to 8, the method further comprising receiving a configuration having a first neighboring cell list having a first group of one or more ongoing multicast or broadcast communication sessions associated with a first type of RedCap UE, the first neighboring cell list being different from a second neighboring cell list having a second group of one or more ongoing multicast or broadcast communication sessions associated with a second type of RedCap UE.

[0166] Aspect 10 is a method according to any one of aspects 1 to 9, the method further comprising receiving a second indication of a first ongoing multicast or broadcast communication session list associated with a first G-RNTI associated with the MTCH for a first type of RedCap UE, the first ongoing multicast or broadcast communication session list being different from a second ongoing multicast or broadcast communication session list associated with a second G-RNTI associated with the MTCH for a second type of RedCap UE.

[0167] Aspect 11 is the method according to aspect 10, wherein PDSCH communication scheduled by a PDCCH associated with at least one of G-RNTI or MCCH-RNTI is associated with a set of physical resource blocks spanning less than 5 MHz, the G-RNTI or MCCH-RNTI being associated with the MTCH for the plurality of RedCap UEs.

[0168] Aspect 12 is a method according to any one of Aspects 1 and 2, the method further comprising receiving a third indication of a first MTCH neighboring cell configuration for the first G-RNTI for transmission to the plurality of RedCap UEs, the first MTCH neighboring cell configuration being different from a second MTCH neighboring cell configuration for the second G-RNTI.

[0169] Aspect 13 is a method according to any one of aspects 1 to 12, the method further comprising receiving a first DRX configuration associated with a first type of RedCap UE, the first DRX configuration being different from a second DRX configuration for a second type of RedCap UE.

[0170] Aspect 14 is the method according to aspect 13, the method further comprising monitoring PDSCH timing with a span limited to 5 MHz based on the first DRX configuration.

[0171] Aspect 15 is a method of wireless communication at a network device, the method comprising: outputting a first indication of a CFR associated with at least one of an MCCH or MTCH for at least one of a plurality of RedCap UEs in an inactive or idle state for transmission to the plurality of RedCap UEs, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, the first capability being different from a second capability having a second maximum bandwidth greater than the first maximum bandwidth; and outputting at least one of an MCCH communication or MTCH communication for transmission to the plurality of RedCap UEs via the CFR indicated in the first indication for at least one of a broadcast service or a multicast service.

[0172] Aspect 16 is the method according to aspect 15, wherein the CFR is a first CFR different from a second CFR associated with at least one of the MCCH or MTCH for one or more RedCap UEs, the one or more RedCap UEs supporting a third capability having a third maximum bandwidth greater than the first maximum bandwidth and less than the second maximum bandwidth.

[0173] Aspect 17 is the method according to any one of aspects 15 and 16, wherein the different CFRs are indicated for different types of RedCap UEs supporting the first capability.

[0174] Aspect 18 is the method according to any one of aspects 15 to 17, wherein the CFR is also associated with at least one of the MCCH or the MTCH for various types of RedCap UE.

[0175] Aspect 19 is the method according to any one of aspects 15 to 18, wherein the first indication is included in the SIB.

[0176] Aspect 20 is a method according to any one of aspects 15 to 19, the method further comprising outputting a first MCCH configuration for a first type of RedCap UE, different from a second MCCH configuration for a second type of RedCap UE, for transmission to the plurality of RedCap UEs, wherein the first MCCH configuration specifies at least one of a first periodicity of MCCH resources or a first offset associated with the MCCH, the first periodicity or the first offset being different from a second periodicity of MCCH resources specified by the second MCCH configuration or an associated second offset.

[0177] Aspect 21 is a method according to any one of aspects 15 to 20, the method further comprising outputting a first MTCH configuration for a first type of RedCap UE, different from a second MTCH configuration for a second type of RedCap UE, for transmission to the plurality of RedCap UEs, wherein the first MTCH configuration includes at least one of a first RM, a first LBRM, or a first set of RS configurations associated with the MTCH, the first RM, first LBRM, or first set of RS configurations being different from the second RM, second LBRM, or second set of RS configurations associated with the second MTCH configuration.

[0178] Aspect 22 is a method according to any one of aspects 15 to 21, the method further comprising outputting a configuration for sending to the plurality of RedCap UEs having a first list of one or more ongoing multicast or broadcast communication sessions associated with a first type of RedCap UE, the first list of neighboring cells being different from a second list of neighboring cells having a second list of one or more ongoing multicast or broadcast communication sessions associated with a second type of RedCap UE.

[0179] Aspect 23 is a method according to any one of aspects 15 to 22, the method further comprising outputting a second indication of a first ongoing multicast or broadcast communication session list associated with a first G-RNTI associated with the MTCH for a first type of RedCap UE for transmission to the plurality of RedCap UEs, the first ongoing multicast or broadcast communication session list being different from a second ongoing multicast or broadcast communication session list associated with a second G-RNTI associated with the MTCH for a second type of RedCap UE.

[0180] Aspect 24 is the method according to any one of Aspect 23, the method further comprising outputting a third indication of a first MTCH neighboring cell configuration for the first G-RNTI for transmission to the plurality of RedCap UEs, the first MTCH neighboring cell configuration being different from a second MTCH neighboring cell configuration for the second G-RNTI.

[0181] Aspect 25 is a method according to any one of aspects 15 to 24, the method further comprising outputting a first DRX configuration associated with a first type of RedCap UE for transmission to the plurality of RedCap UEs, the first DRX configuration being different from a second DRX configuration for a second type of RedCap UE.

[0182] Aspect 26 is an apparatus for wireless communication at a device, the apparatus including at least one memory and at least one processor, the at least one processor being coupled to the at least one memory and being based at least in part on information stored in the memory, the at least one processor being configured individually or in any combination to implement any one of aspects 1 to 25.

[0183] Aspect 27 is the apparatus according to aspect 26, the apparatus further comprising at least one transceiver or at least one antenna coupled to the at least one processor.

[0184] Aspect 28 is an apparatus for wireless communication at a device, the apparatus including components for implementing any one of aspects 1 to 25.

[0185] Aspect 29 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement any one of aspects 1 to 25 individually or in any combination.

Claims

1. An apparatus for wireless communication at a wireless device, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and configured, based at least in part on information stored in the at least one memory, to: receive a first indication of a common frequency resource (CFR) associated with at least one of a multicast control channel (MCCH) or a multicast traffic channel (MTCH) for a plurality of reduced capability (RedCap) UEs in one of an inactive state or an idle state, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, the first capability being different from a second capability having a second maximum bandwidth that is greater than the first maximum bandwidth; and monitor the CFR indicated in the first indication for at least one of broadcast traffic or multicast traffic.

2. The apparatus of claim 1, wherein the CFR is a first CFR that is different from a second CFR associated with the at least one of the MCCH or the MTCH for one or more RedCap UEs, the one or more RedCap UEs supporting a third capability having a third maximum bandwidth that is greater than the first maximum bandwidth and less than the second maximum bandwidth.

3. The apparatus of claim 1, wherein different CFRs are associated with different types of RedCap UEs that support the first capability.

4. The apparatus of claim 1, wherein the CFR is further associated with the at least one of the MCCH or the MTCH for multiple types of RedCap UEs.

5. The apparatus of claim 4, wherein the at least one processor is further configured, individually or in any combination: to skip decoding a physical downlink shared channel (PDSCH) communication based on the PDSCH communication having frequency resources that span beyond the first maximum bandwidth.

6. The apparatus of claim 1, wherein the at least one processor is further configured, individually or in any combination, to receive the first indication in a system information block (SIB).

7. The apparatus of claim 1, wherein the at least one processor is further configured, individually or in any combination: to receive a first MCCH configuration for a first type of RedCap UE that is different from a second MCCH configuration for a second type of RedCap UE, wherein the first MCCH configuration specifies at least one of a first periodicity of MCCH resources or a first offset associated with the MCCH, the first periodicity or first offset being different from a second periodicity of MCCH resources or an associated second offset specified by the second MCCH configuration.

8. The apparatus of claim 1, wherein the at least one processor is further configured, individually or in any combination: ​ receive a first MTCH configuration for a first type of RedCap UE that is different from a second MTCH configuration for a second type of RedCap UE, wherein the first MTCH configuration comprises at least one of a first rate matching (RM), a first limited buffer RM (LBRM), or a first set of reference signal (RS) configuration associated with the MTCH that is different from a second RM, a second LBRM, or a second set of RS configuration associated with the second MTCH configuration.

9. The apparatus of claim 1, wherein the at least one processor is further configured to, individually or in any combination: receive a configuration of a first list of neighboring cells having a first set of one or more ongoing multicast or broadcast communication sessions associated with a first type of RedCap UE that is different from a second list of neighboring cells having a second set of one or more ongoing multicast or broadcast communication sessions associated with a second type of RedCap UE.

10. The apparatus of claim 1, wherein the at least one processor is further configured to, individually or in any combination: receive a second indication of a first list of ongoing multicast or broadcast communication sessions associated with a first group radio network temporary identifier (G-RNTI) associated with the MTCH for a first type of RedCap UE that is different from a second list of ongoing multicast or broadcast communication sessions associated with a second G-RNTI associated with the MTCH for a second type of RedCap UE.

11. The apparatus of claim 10, wherein a physical downlink shared channel (PDSCH) communication scheduled by a physical downlink control channel (PDCCH) associated with at least one of the G-RNTI or MCCH-RNTI associated with the MTCH for the plurality of RedCap UEs is associated with a set of physical resource blocks spanning less than 5 MHz.

12. The apparatus of claim 10, wherein the at least one processor is further configured to, individually or in any combination: receive a third indication of a first MTCH neighboring cell configuration for the first G-RNTI that is different from a second MTCH neighboring cell configuration for the second G-RNTI.

13. The apparatus of claim 1, wherein the at least one processor is further configured to, individually or in any combination: receive a first discontinuous reception (DRX) configuration associated with a first type of RedCap UE that is different from a second DRX configuration for a second type of RedCap UE.

14. The apparatus of claim 13, wherein the at least one processor, individually or in any combination, is further configured to: monitor a physical downlink shared channel (PDSCH) occasion limited to a span of 5 MHz based on the first DRX configuration.

15. An apparatus for wireless communication at a network device, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to, individually or in any combination, based on information stored in the at least one memory: output, for transmission to a plurality of reduced capability (RedCap) user equipments (UEs) in an inactive state or an idle state, a first indication of a common frequency resource (CFR) associated with at least one of a multicast control channel (MCCH) or a multicast traffic channel (MTCH) for the plurality of RedCap UEs, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, the first capability being different from a second capability having a second maximum bandwidth that is greater than the first maximum bandwidth; and output, for transmission to the plurality of RedCap UEs, at least one of an MCCH communication or an MTCH communication via the CFR indicated in the first indication for at least one of broadcast traffic or multicast traffic.

16. The apparatus of claim 15, wherein the CFR is a first CFR that is different from a second CFR associated with at least one of the MCCH or the MTCH for one or more RedCap UEs supporting a third capability having a third maximum bandwidth that is greater than the first maximum bandwidth and less than the second maximum bandwidth.

17. The apparatus of claim 15, wherein different CFRs are associated with different types of RedCap UEs supporting the first capability.

18. The apparatus of claim 15, wherein the CFR is further associated with at least one of the MCCH or the MTCH for multiple types of RedCap UEs.

19. The apparatus of claim 15, wherein the first indication is included in a system information block (SIB).

20. The apparatus of claim 15, wherein the at least one processor, individually or in any combination, is further configured to: output, for transmission to the plurality of RedCap UEs, a first MCCH configuration for a first type of RedCap UE that is different from a second MCCH configuration for a second type of RedCap UE, wherein the first MCCH configuration specifies at least one of a first periodicity of MCCH resources or a first offset associated with the MCCH that is different from a second periodicity of MCCH resources or an associated second offset specified by the second MCCH configuration. ​ 21. The apparatus of claim 15, wherein the at least one processor, individually or in any combination with other processors, is further configured to: output, for transmission to the plurality of RedCap UEs, a first MTCH configuration for a first type of RedCap UE that is different from a second MTCH configuration for a second type of RedCap UE, wherein the first MTCH configuration comprises at least one of a first rate matching (RM), a first limited buffer RM (LBRM), or a first set of reference signal (RS) configuration associated with the MTCH that is different from a second RM, a second LBRM, or a second set of RS configuration associated with the second MTCH configuration.

22. The apparatus of claim 15, wherein the at least one processor, individually or in any combination with other processors, is further configured to: output, for transmission to the RedCap UE, a configuration of a first list of neighboring cells having a first set of one or more ongoing multicast or broadcast communication sessions associated with a first type of RedCap UE that is different from a second list of neighboring cells having a second set of one or more ongoing multicast or broadcast communication sessions associated with a second type of RedCap UE.

23. The apparatus of claim 15, wherein the at least one processor, individually or in any combination with other processors, is further configured to: output, for transmission to the plurality of RedCap UEs, a second indication of a first list of ongoing multicast or broadcast communication sessions associated with a first group radio network temporary identifier (G-RNTI) associated with the MTCH for a first type of RedCap UE that is different from a second list of ongoing multicast or broadcast communication sessions associated with a second G-RNTI associated with the MTCH for a second type of RedCap UE.

24. The apparatus of claim 23, wherein the at least one processor, individually or in any combination with other processors, is further configured to: output, for transmission to the plurality of RedCap UEs, a third indication of a first MTCH neighboring cell configuration for the first G-RNTI that is different from a second MTCH neighboring cell configuration for the second G-RNTI.

25. The apparatus of claim 15, wherein the at least one processor, individually or in any combination with other processors, is further configured to: output, for transmission to the plurality of RedCap UEs, a first discontinuous reception (DRX) configuration associated with a first type of RedCap UE that is different from a second DRX configuration for a second type of RedCap UE.

26. A method for wireless communication at a wireless device (UE), comprising: receiving a first indication of a common frequency resource (CFR) associated with at least one of a multicast control channel (MCCH) or a multicast traffic channel (MTCH) for a plurality of reduced capability (RedCap) UEs in one of an inactive state or an idle state, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, the first capability being different from a second capability having a second maximum bandwidth that is greater than the first maximum bandwidth; and monitoring the CFR indicated in the first indication for at least one of broadcast traffic or multicast traffic.

27. The method of claim 26, wherein the CFR is a first CFR that is different from a second CFR associated with at least one of the MCCH or the MTCH for one or more RedCap UEs, the one or more RedCap UEs supporting a third capability having a third maximum bandwidth that is greater than the first maximum bandwidth and less than the second maximum bandwidth.

28. The method of claim 26, the method further comprising: receiving a first discontinuous reception (DRX) configuration associated with a first type of RedCap UE, the first discontinuous reception (DRX) configuration being different from a second DRX configuration for a second type of RedCap UE.

29. A method for wireless communication at a network device, the method comprising: outputting for transmission to a plurality of reduced capability (RedCap) user equipment (UEs) in one of an inactive state or an idle state, a first indication of a common frequency resource (CFR) associated with at least one of a multicast control channel (MCCH) or a multicast traffic channel (MTCH) for the plurality of RedCap UEs, the plurality of RedCap UEs supporting a first capability having a first maximum bandwidth, the first capability being different from a second capability having a second maximum bandwidth that is greater than the first maximum bandwidth; and outputting for transmission to the plurality of RedCap UEs, at least one of a MCCH communication or a MTCH communication via the CFR indicated in the first indication for at least one of broadcast traffic or multicast traffic.

30. The method of claim 29, wherein the CFR is a first CFR that is different from a second CFR associated with at least one of the MCCH or the MTCH for one or more RedCap UEs, the one or more RedCap UEs supporting a third capability having a third maximum bandwidth that is greater than the first maximum bandwidth and less than the second maximum bandwidth.

Images