Supporting multicast or broadcast operation with enhanced reduced capability user equipment

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive control information that schedules a multicast traffic channel transmission and indicates a bandwidth of the transmission. The UE may receive one or more instances of the transmission according to the control information, wherein a number of the one or more instances is based at least in part on a bandwidth of the transmission. Additionally or alternatively, the UE may receive control information that schedules multicast traffic channel transmissions and indicates whether the UE is to transmit acknowledgements in response to the transmissions. The UE may receive the transmission according to the control information, wherein the multicast traffic channel transmission is received on a bandwidth based at least in part on whether the UE is to transmit an acknowledgement in response to the multicast traffic channel transmission.

Description

Cross-reference to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 774,212, filed July 16, 2024, entitled “SUPPORTING MULTICAST OR BROADCAST OPERATIONS WITH ENHANCED REDUCED CAPACITY USER EQUIPMENT,” and U.S. Provisional Patent Application No. 63 / 515,509, filed July 25, 2023, entitled “SUPPORTING MULTICAST OR BROADCAST OPERATIONS WITH ENHANCED REDUCED CAPACITY USER EQUIPMENT,” each of which is assigned to the assignee of this application, and each of which is expressly incorporated herein by reference. Technical Field

[0002] The following relates to wireless communications, including the use of enhanced degraded capability user equipment to support multicast or broadcast operations. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems are capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0004] In some wireless communication systems, wireless devices can be degraded devices and can communicate within the wireless communication system. However, such methods can be improved. Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting multicast or broadcast operations using enhanced degraded capability user equipment. For example, the user equipment (UE) may receive control information scheduling multicast traffic channel transmissions and indicating the bandwidth of such transmissions. The UE may receive one or more instances of such transmissions based on the control information, wherein the number of such instances is at least partially based on the bandwidth of the transmission. Additionally or alternatively, the UE may receive control information scheduling multicast traffic channel transmissions and indicating whether the UE should send an acknowledgment in response to the transmission. The UE may receive the transmissions based on the control information, wherein the multicast traffic channel transmissions are received on a bandwidth at least partially based on whether the UE should send an acknowledgment in response to the multicast traffic channel transmission.

[0006] A method for wireless communication by a UE is described. The method may include: receiving control information that schedules broadcast transmission and indicates the bandwidth of the broadcast transmission; and receiving one or more instances of the broadcast transmission in multiple time slots according to the control information, wherein the number of the one or more instances is associated with the bandwidth of the broadcast transmission.

[0007] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the UE to: receive control information scheduling broadcast transmissions and indicating the bandwidth of the broadcast transmissions; and receive one or more instances of the broadcast transmissions in multiple time slots according to the control information, wherein the number of the one or more instances is associated with the bandwidth of the broadcast transmissions.

[0008] Another UE for wireless communication is described. The UE may include: components for receiving control information that schedules broadcast transmissions and indicates the bandwidth of the broadcast transmissions; and components for receiving one or more instances of broadcast transmissions in multiple time slots according to the control information, wherein the number of the one or more instances is associated with the bandwidth of the broadcast transmissions.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) to: receive control information scheduling a broadcast transmission and indicating the bandwidth of the broadcast transmission; and receive one or more instances of the broadcast transmission in multiple time slots according to the control information, wherein the number of such instances is associated with the bandwidth of the broadcast transmission.

[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, a broadcast transmission bandwidth greater than a bandwidth threshold may be associated with a number of one or more instances; and a broadcast transmission bandwidth less than a bandwidth threshold may be associated with a number of one or more instances being two or more.

[0011] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, the bandwidth threshold may be 5 MHz.

[0012] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, the bandwidth threshold may be based on 25 physical resource blocks and a subcarrier spacing of 15 kHz or 12 physical resource blocks and a subcarrier spacing of 30 kHz.

[0013] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the bandwidth of the broadcast transmission may indicate the number of one or more instances to be processed by the UE.

[0014] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the bandwidth of the broadcast transmission may be less than a bandwidth threshold, and based on the broadcast transmission bandwidth being less than a bandwidth threshold, one or more instances may include multiple instances. In such cases, the methods, UEs, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for processing multiple instances based on the broadcast transmission bandwidth being less than a bandwidth threshold.

[0015] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for determining the number of one or more instances of broadcast transmission based on a comparison of the bandwidth of the broadcast transmission with a set of multiple bandwidth thresholds, wherein each bandwidth threshold may be associated with a corresponding number of supported instances.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, determining the number of one or more instances of broadcast transmission may include operations, features, components, or instructions for: determining a first bandwidth threshold in a set of multiple bandwidth thresholds, which may be the maximum bandwidth threshold satisfied by the bandwidth of the broadcast transmission; and determining the number of one or more instances of broadcast transmission as a corresponding number of supported instances associated with the first bandwidth threshold.

[0017] In the methods described herein, in some examples of UEs and nontransitory computer-readable media, the set of multiple supported instance numbers can be negatively correlated with the set of multiple bandwidth thresholds.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, one of the multiple bandwidth thresholds in the set of bandwidth thresholds may be 5 MHz.

[0019] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, control information may be included in downlink control information signaling.

[0020] In the methods described herein, in some examples of UEs and nontransitory computer-readable media, multiple time slots can be consecutive or non-consecutive time slots.

[0021] A method for wireless communication by a UE is described. The method may include: receiving control information that schedules multicast service channel transmission and instructs the UE whether to send an acknowledgment in response to the multicast service channel transmission; and receiving the multicast service channel transmission according to the control information, wherein the multicast service channel transmission is received on a bandwidth based on whether the UE wants to send an acknowledgment in response to the multicast service channel transmission.

[0022] A UE for wireless communication is described. The UE may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the UE to: receive control information scheduling multicast service channel transmissions and instructing the UE whether to send an acknowledgment in response to the multicast service channel transmission; and receive the multicast service channel transmissions according to the control information, wherein the multicast service channel transmissions are received on a bandwidth based on whether the UE wants to send an acknowledgment in response to the multicast service channel transmission.

[0023] Another UE for wireless communication is described. The UE may include: components for receiving control information that schedules multicast service channel transmissions and instructs the UE whether to send an acknowledgment in response to the multicast service channel transmission; and components for receiving multicast service channel transmissions based on the control information, wherein the multicast service channel transmissions are received on a bandwidth based on whether the UE wants to send an acknowledgment in response to the multicast service channel transmission.

[0024] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) to: receive control information scheduling multicast service channel transmission and instructing a UE whether to send an acknowledgment in response to the multicast service channel transmission; and receive multicast service channel transmission according to the control information, wherein the multicast service channel transmission is received on a bandwidth based on whether the UE wants to send an acknowledgment in response to the multicast service channel transmission.

[0025] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for determining whether the bandwidth of a multicast service channel transmission is permitted to exceed a bandwidth threshold, based on control information instructing the UE to send an acknowledgment in response to multicast service channel transmission.

[0026] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, the bandwidth threshold may be 5 MHz.

[0027] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for determining that the bandwidth of a multicast service channel transmission may be allowed to exceed a bandwidth threshold based on control information indicating that the UE may send acknowledgments without responding to the transmission of the multicast service channel.

[0028] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, the bandwidth threshold may be 5 MHz.

[0029] The methods described herein, examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for determining that the bandwidth of the multicast channel transmission may exceed the bandwidth threshold, based on control information instructing the UE to transmit acknowledgments in response to multicast channel transmission and control information scheduling a second resource for the UE to transmit acknowledgments, which may be scheduled later than a first resource for feedback transmission when the bandwidth of the multicast channel transmission is less than the bandwidth threshold.

[0030] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, control information indicates whether the UE can send an acknowledgment in response to a multicast service channel transmission based on an identifier associated with the UE.

[0031] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the acknowledgment may be a hybrid automatic repeat request acknowledgment feedback.

[0032] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the UE can operate in connected mode.

[0033] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, control information may be included in downlink control information signaling, radio resource control signaling, or both. Attached Figure Description

[0034] Figure 1Examples of wireless communication systems that utilize enhanced reduced-capability user equipment to support multicast or broadcast operations, based on one or more examples disclosed herein, are shown.

[0035] Figure 2 Examples of wireless communication systems that utilize enhanced reduced-capability user equipment to support multicast or broadcast operations, based on one or more examples disclosed herein, are shown.

[0036] Figure 3A and Figure 3B Examples of multicast / broadcast (MBS) schemes that utilize enhanced reduced-capability user equipment to support multicast or broadcast operations are shown, based on one or more examples disclosed herein.

[0037] Figure 4 Examples of process flows for supporting multicast or broadcast operations using enhanced reduced-capability user equipment, based on one or more examples disclosed herein.

[0038] Figure 5 Examples of process flows for supporting multicast or broadcast operations using enhanced reduced-capability user equipment, based on one or more examples disclosed herein.

[0039] Figure 6 and Figure 7 A block diagram is shown of a device that utilizes enhanced reduced-capability user equipment to support multicast or broadcast operations, according to one or more examples disclosed herein.

[0040] Figure 8 A block diagram is shown of a communication manager that utilizes enhanced reduced-capability user equipment to support multicast or broadcast operations, according to one or more examples disclosed herein.

[0041] Figure 9 A diagram is shown of a system comprising a device that utilizes enhanced reduced-capability user equipment to support multicast or broadcast operations, according to one or more examples disclosed herein.

[0042] Figure 10 and Figure 11 A flowchart illustrating a method for supporting multicast or broadcast operations using enhanced reduced-capability user equipment, based on one or more examples disclosed herein. Detailed Implementation

[0043] In wireless communications, it may be desirable to use devices with reduced capabilities, which offer reduced power consumption (e.g., for long-term deployments or other situations where reduced power consumption is beneficial). Such devices may include Reduced Capability (RedCap) User Equipment (UE) or Enhanced Reduced Capability (eRedCap) UE, which may include various reduced capabilities, such as reduced bandwidth processing capabilities. However, some methods for wireless communications may not consider multicast / broadcast (MBS) scenarios for such UEs. For example, some methods may limit transmissions to a strict maximum bandwidth, may not allow repeated transmissions, or may not be suitable for feedback scenarios. Furthermore, current wireless communication standards may not consider the use of eRedCap UEs in the context of MBS communications. Therefore, improvements to RedCap and eRedCap wireless communications may be desired.

[0044] In some implementations, the allowed number of repetitions in MBS transmissions can be correlated with the MBS transmission bandwidth. For example, a network entity can indicate the MBS transmission bandwidth, and the UE can implicitly determine the number of MBS transmission repetitions that the network entity can send. For instance, if the MBS transmission bandwidth is relatively low, the UE can still receive or process repetitions despite reduced capabilities. In contrast, if the MBS transmission bandwidth is relatively high, the UE may be unable to receive or process repetitions, in which case the number of repetitions may be reduced (in some cases, reduced to a single transmission). In this way, the wireless communication system can improve the utilization of the UE's reduced capabilities, thereby providing improved communication quality and reliability.

[0045] Furthermore, in some implementations, the bandwidth for MBS transmission can be determined based on whether the UE provides acknowledgment feedback in response to the MBS transmission. For example, if the UE is signaled to provide acknowledgment feedback for the MBS transmission, the UE can implicitly determine that the MBS transmission will not exceed the bandwidth threshold, since receiving large-bandwidth communication and providing timely feedback may both be beyond the UE's capabilities. Similarly, if the UE is not signaled to provide acknowledgment feedback for the MBS transmission, the UE can implicitly determine that MBS transmission exceeding the bandwidth threshold is permitted. In this way, the wireless communication system can improve the utilization of the UE's reduced capabilities, thereby providing improved communication quality and reliability.

[0046] The aspects of this disclosure are first described in the context of a wireless communication system. Then, the aspects of this disclosure are described with reference to wireless communication systems, MBS schemes, and process flows. The aspects of this disclosure are further illustrated and described by means of and reference to apparatus diagrams, system diagrams, and flowcharts relating to multicast or broadcast operations utilizing enhanced degraded capability user equipment.

[0047] Figure 1An example of a wireless communication system 100 utilizing enhanced degraded capability user equipment to support multicast or broadcast operation, according to one or more examples disclosed herein, is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0048] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0049] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein is capable of supporting various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0050] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0051] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0052] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0053] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0054] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0055] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0056] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), wherein the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0057] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay for UE transmissions via one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0058] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0059] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support multicast or broadcast operations using enhanced degraded capability user equipment as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0060] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein “device” may also be referred to as a unit, station, terminal, or client, etc. UE 115 may also include or be referred to as personal electronic devices, such as cellular phones, personal digital assistants (PDAs), multimedia / entertainment devices (e.g., radios, MP3 players, or video devices), cameras, gaming devices, navigation / positioning devices (e.g., GNSS (Global Navigation Satellite System) devices based on, for example, GPS (Global Positioning System), BeiDou system, GLONASS or Galileo system, ground-based devices, etc.), tablet computers, laptop computers, netbooks, smartbooks, personal computers, smart devices, wearable devices (e.g., smartwatches, smart clothing, smart glasses, virtual reality goggles, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), drones, robots / robotic devices, vehicles, vehicle equipment, meters (e.g., parking timers, electricity meters, gas meters, water meters), monitors, air pumps, electrical appliances (e.g., kitchen appliances, washing machines, dryers), location tags, medical / healthcare devices, implants, sensors / actuators, displays, or any other suitable device configured to communicate via wireless or wired media. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which can be implemented in a variety of objects such as appliances or vehicles, meters, etc.

[0061] The UE 115 described herein is capable of communicating with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0062] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0063] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be made by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0064] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0065] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0066] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0067] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0068] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0069] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0070] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0071] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0072] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the extent of such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include buildings, subsets of buildings, or external space between or overlapping coverage areas 110, etc.

[0073] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0074] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0075] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0076] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0077] Some UEs 115 (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entities 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging. In one aspect, the techniques disclosed herein are applicable to MTC or IoT UEs. MTC or IoT UE can include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UE, NB-IoT (also known as CAT NB1) UE, and other types of UE. eMTC and NB-IoT can refer to future technologies that can evolve from or are based on these technologies. For example, eMTC can include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), and mMTC (massive MTC), while NB-IoT can include eNB-IoT (enhanced NB-IoT) and FeNB-IoT (further enhanced NB-IoT).

[0078] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, a reduced peak rate can be used to perform half-duplex communication. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0079] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0080] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0081] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0082] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0083] Wireless communication system 100 can operate using one or more frequency bands (ranging from 300 MHz to 300 GHz). Generally, the 300 MHz to 3 GHz band is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower HF or VHF portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0084] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the network entity 105 (e.g., base station 140, RU170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

[0085] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0086] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0087] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0088] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0089] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0090] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with the receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0091] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0092] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0093] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0094] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0095] In some implementations, UE 115 and network entity 105 may support one or more signaling-based or configuration-based mechanisms, according to which UE 115 and network entity 105 (e.g., RedCap UE or eRedCap UE) may support MBS communication. For example, UE 115 may receive from network entity 105 an indication of the bandwidth of an upcoming MTCH transmission (e.g., MBS transmission, broadcast traffic channel transmission). Based on this control signaling (and more specifically, the indicated bandwidth), the UE may determine whether UE 115 wants to receive multiple instances of MTCH transmission (e.g., repetition). For example, if the bandwidth of the MTCH transmission is large (e.g., exceeding a threshold), network entity 105 may transmit a single instance of MBS transmission, or if the bandwidth of the MTCH transmission is small (e.g., not exceeding a threshold), the network entity may transmit multiple instances of MTCH transmission. Additionally or alternatively, control signaling may instruct UE 115 whether to provide acknowledgment of the MTCH transmission. Based on this indication, UE 115 may determine the bandwidth of the MTCH transmission. For example, if UE 115 is to provide an acknowledgment, UE 115 can determine that the bandwidth for MTCH transmission will be small (e.g., below a threshold) to accommodate the acknowledgment. Similarly, if UE 115 does not provide an acknowledgment, UE 115 can determine that the bandwidth allowed for MTCH transmission is large (e.g., above a threshold) because UE 115 may not need to accommodate the acknowledgment.

[0096] Figure 2An example of a wireless communication system 200 utilizing enhanced degraded capability user equipment to support multicast or broadcast operations, according to one or more examples disclosed herein, is shown. The wireless communication system 200 may include network entity 105-a, which may be an example of one or more network entities discussed with respect to other figures. The wireless communication system 200 may include UE 115-a, which may be an example of a UE discussed with respect to other figures. The wireless communication system 200 may include UE 115-b, which may be an example of a UE discussed with respect to other figures.

[0097] In some examples, UE 115-a may be located in a geographic coverage area 110-a that may be associated with network entity 105-a. Network entity 105-a and UE 115-a may communicate via one or more downlink communication links 205-a and one or more uplink communication links 205-b.

[0098] In wireless communications, some UEs may have reduced capabilities and may be referred to as RedCap UEs. UE 115-b is an example of such a RedCap UE. Some UEs may have "enhanced" reduced capabilities (e.g., further reduced capabilities) and may be referred to as eRedCap UEs. UE 115-a is an example of an eRedCap UE. For example, a RedCap UE is able to operate with reduced bandwidth (e.g., compared to a non-RedCap UE) for some communications (e.g., with network entity 105-a). In some approaches, an eRedCap UE (e.g., UE 115-a) may also have reduced baseband bandwidth capabilities for some communications (e.g., with network entity 105-a) compared to a RedCap UE. In some examples, the eRedCap UE (e.g., UE115-a) can operate with a PUSCH bandwidth that does not exceed a bandwidth threshold (e.g., 5 MHz) (e.g., an arrangement of 25 Physical Resource Blocks (PRBs) with a 15 kHz Subcarrier Spacing (SCS), 12 PRBs with a 30 kHz SCS, or another arrangement of PRBs, SCS, or both). In some examples, the eRedCap UE (e.g., UE 115-a) can operate with a unicast Physical Downlink Shared Channel (PDSCH) bandwidth that does not exceed a bandwidth threshold (e.g., 5 MHz) (e.g., 25 PRBs with a 15 kHz SCS, 12 PRBs with a 30 kHz SCS, or another arrangement of PRBs, SCS, or both). However, in some cases, some communications may exceed such bandwidth thresholds. For example, in some cases, broadcast PDSCH transmissions (e.g., one or more System Information Block (SIB) transmissions, paging transmissions, random access response transmissions, one or more other transmissions, or any combination thereof) may have bandwidth exceeding a bandwidth threshold (e.g., 5 MHz) (e.g., 25 PRBs with a 15 kHz SCS, 12 PRBs with a 30 kHz SCS, or other arrangements of PRBs, SCSs, or both). In some examples, other transmissions (such as SSB transmissions, TRS transmissions, CSI-RS transmissions, SRS transmissions, PDCCH transmissions, PUCCH transmissions, or channels, or any combination thereof) may have bandwidth exceeding a bandwidth threshold (e.g., 5 MHz).

[0099] In some examples of broadcast communication scenarios, multicast control channel (MCCH) or multicast traffic channel (MTCH) transmissions (e.g., MTCH transmission 225) may be received by UEs in idle, inactive, or connected states (e.g., UE 115-a, UE 115-b, or both). In some examples, a broadcast common frequency resource (CFR) (such as CFR 240) may be configured (e.g., transmitted via system information blocks such as SIB20) for MCCH transmission, MTCH transmission (e.g., MTCH transmission 225), or both. In some examples, control signaling (e.g., DCI, such as DCI format 4_0, which may be configured in the type 0 / 0B common search space (CSS)) may be used to schedule MCCH transmissions, MTCH transmissions (e.g., MTCH transmission 225), or both. In some examples, semi-static or dynamic slot-level (e.g., back-to-back) repetition (e.g., using multiple instances of a message or transmission) may be permitted for broadcast MTCH transmissions (e.g., MTCH transmission 225). In some examples, one or more parameters (e.g., pdsch-AggregationFactor) can be configured via control signaling (e.g., SIB20) (e.g., on a per G-RNTI basis) for semi-static repetition of broadcast MTCH transmissions (e.g., MTCH transmission 225). In some examples, one or more parameters (e.g., the repetitionNumber parameter in the Time Domain Resource Allocation (TDRA) table) can be configured for dynamic repetition of broadcast MTCH transmissions (e.g., MTCH transmission 225). In some examples, broadcast MCCH transmissions, MTCH transmissions (e.g., MTCH transmission 225), or both may not support feedback (e.g., HARQ-ACK feedback). However, in other examples, broadcast MCCH transmissions, MTCH transmissions (e.g., MTCH transmission 225), or both may support feedback (e.g., HARQ-ACK feedback).

[0100] In some examples of multicast communication scenarios, when a UE (e.g., UE 115-a, UE 115-b, or both) is in the RRC_CONNECTED state, the UE (e.g., UE 115-a, UE 115-b, or both) can receive multicast MTCH transmissions (e.g., MTCH transmission 225). In some examples, a multicast CFR (such as CFR 240) can be configured via unicast RRC signaling (e.g., via unicast RRC signaling or other control signaling) for multicast MTCH transmissions (e.g., MTCH transmission 225) on a per DL BWP basis. In some examples, the UE (e.g., UE 115-a, UE 115-b, or both) can receive control signaling (e.g., DCI signaling, such as DCI format 4_1 or 4_2 (e.g., in type 3)). (Configured in CSS), this control signaling can schedule one or more multicast MTCH transmissions (e.g., MTCH transmission 225). In some examples, semi-static or dynamic slot-level (e.g., back-to-back) repetition (e.g., transmission of multiple instances of a message) is allowed for multicast MTCH transmissions (e.g., MTCH transmission 225). In some examples, semi-static or dynamic enabling or disabling of feedback message reception (e.g., HARQ-ACK feedback) for multicast MTCH transmissions (e.g., MTCH transmission 225) is possible. In some examples where HARQ-ACK feedback is enabled for multicast, at least two feedback modes can be used to provide feedback (e.g., acknowledgment 245). The first feedback scheme may involve the transmission of both a positive acknowledgment (ACK) in response to successful reception and / or decoding of a message (e.g., MTCH transmission 225) and a negative acknowledgment (NACK) in response to unsuccessful reception and / or decoding of a message (e.g., MTCH transmission 225). The second scheme may be a NACK-only scheme, where the UE UE115-a does not send an ACK in response to successful message reception and / or decoding, but sends a NACK in response to unsuccessful message reception and / or decoding.

[0101] In some examples, modifications to the broadcast transmission scenario may be employed. For instance, a single CFR (e.g., CFR240) may be used for both RedCap UEs (e.g., UE 115-b) and eRedCap UEs (e.g., UE 115-a). Such CFRs may not exceed a bandwidth threshold (e.g., 20MHz) and may be configured via control signaling (e.g., system information broadcasts, such as SIB20 messages). Such CFRs may utilize resources that are at least partially different from those used by non-RedCap UEs.

[0102] In some examples, modifications to the multicast transmission scenario may be employed. For example, multicast MCCH transmission, multicast MTCH transmission, or both may be received by a UE (e.g., UE 115-a, UE 115-b, or both) in an inactive state (e.g., RRC_INACTIVE state). In some examples, a single CFR (e.g., CFR 240) may be configured for multicast transmission. Such a CFR may be configured via control signaling (such as system information block signaling). In some examples, control signaling (e.g., DCI signaling, such as DCI format 4_0) may be configured (e.g., in type 0 / 0B CSS) and used for multicast MCCH transmission to be received by a UE in an inactive state (e.g., RRC_INACTIVE). In some examples, control signaling (e.g., DCI signaling, such as DCI format 4_1) that can be configured (e.g., in type 3-CSS) may be used to schedule multicast MTCH transmission to be received by a UE in an inactive state (e.g., RRC_INACTIVE). In some examples, semi-static or dynamic slot-level (e.g., back-to-back) repetition for multicast MTCH transmissions may be permitted. In some examples, feedback transmission in response to multicast MTCH transmissions, multicast MCCH transmissions, or both may not be supported when the UE is in an inactive mode (e.g., RRC_INACTIVE).

[0103] In some examples, both RedCap UE (e.g., UE 115-b) and eRedCap UE (e.g., UE 115-a) may treat MBS transmissions such as MTCH transmission 225 (e.g., broadcast transmission, multicast transmission, or both) as transmissions that are permitted to use bandwidth above a bandwidth threshold (e.g., 5 MHz) (e.g., SIB transmission, paging transmission, or random access response message). In some examples, both RedCap UE (e.g., UE 115-b) and eRedCap UE (e.g., UE 115-a) may share CFR240 for conveying MCCH transmissions, MTCH transmissions (e.g., MTCH transmission 225), or both, as indicated by control signaling (e.g., system information block transmissions, such as SIB20). Because CFR 240 can be shared between RedCap UEs and eRedCap UEs, a device sending PDSCH transmissions (e.g., network entity 105-a) may not be able to distinguish between transmissions to RedCap UEs (e.g., UE 115-b) and transmissions to eRedCap UEs (e.g., UE 115-a). Additionally or alternatively, a device sending PDSCH transmissions (e.g., network entity 105-a) may not be able to distinguish between transmissions to RedCap UEs (e.g., UE 115-b) and transmissions to eRedCap UEs (e.g., UE 115-a) operating in an inactive mode (e.g., RRC_INACTIVE mode or state). In some examples, CFR 240 can be used for broadcast transmissions (e.g., broadcast traffic channel transmission, broadcast channel transmission), multicast transmissions (e.g., multicast traffic channel transmission, multicast channel transmission), or both. The operations described herein related to broadcast transmissions also apply to multicast transmissions, and vice versa.

[0104] In some examples, even if UE 115-a is to provide acknowledgment 245 (e.g., acknowledgment indication 235 is included in control signaling 220, or acknowledgment indication 235 instructs UE 115-a to provide acknowledgment 245), the bandwidth of MTCH transmission 225 may exceed a bandwidth threshold. However, in some such cases, network entity 105-a may provide additional time for UE 115-a to provide acknowledgment 245 (e.g., because UE 115-a needs additional time to simultaneously receive, decode, or process MTCH transmission 225 and provide acknowledgment 245, given its characteristics as an eRedCap UE).

[0105] In some examples, UE 115-a (as an eRedCap UE) may include the ability to receive broadcast transmissions (such as MTCH transmission 225 (e.g., broadcast traffic channel transmission)) with a bandwidth greater than a bandwidth threshold (e.g., 5 MHz). However, in some cases, UE 115-a may not include the ability to receive such transmissions on back-to-back time slots. In some examples, duplication of MTCH transmission 225, MCCH transmission, or both may not be allowed for UE 115-a, other eRedCap UEs, or both. For example, the depicted optional instance of MTCH transmission 225 may not be transmitted. In some examples, such a scheme may also be implemented for RedCap UEs, non-RedCap UEs, or both. Additionally or alternatively, RedCap UEs, non-RedCap UEs, or both may receive duplicate or additional instances of MTCH transmission 225, even if the eRedCap UE may not receive duplicate or additional instances of MTCH transmission 225. Such a method may also apply if MTCH transmission 225 is a broadcast or multicast transmission. For example, for multicast MCCH transmission, multicast MTCH transmission 225, or both, duplication may be disallowed (e.g., disabled).

[0106] Alternatively or additionally, duplicate MCCH transmissions may be disallowed, but duplicate or additional instances of MTCH transmissions may be permitted based on the bandwidth indicated by MTCH transmission 225. For example, network entity 105-a may send control signaling 220 to UE 115-a, and control signaling 220 may include bandwidth indication 230, which may indicate the bandwidth of MTCH transmission 225. The bandwidth of MTCH transmission 225 indicated in bandwidth indication 230 may be the same bandwidth as that associated with CFR 240 for eRedCap UEs, or it may be a different bandwidth.

[0107] If MTCH transmission 225 is a broadcast or multicast transmission, this approach can also be applied. For example, repeated multicast MCCH transmissions may not be permitted for eRedCap UEs (e.g., UE 115-a) that are in an inactive mode or state (e.g., RRC_INACTIVE mode or state) or an active or connected mode or state (e.g., RRC_CONNECTED mode or state), but repeated or additional instances of multicast MTCH transmission 225 may be permitted for eRedCap UEs (e.g., UE 115-a) that are in an inactive mode or state (e.g., RRC_INACTIVE mode or state) or an active or connected mode or state (e.g., RRC_CONNECTED mode or state) based on the bandwidth indicated by MTCH transmission 225.

[0108] In some examples, the number of duplicates or instances of MTCH transmission 225 may be associated with (e.g., dependent on or based on) the bandwidth indicated in bandwidth indication 230, and may also be based on a sliding ratio between the bandwidth of MTCH transmission 225 and the number of duplicates or instances. That is, the bandwidth indicated in bandwidth indication 230 may be based on the number of duplicates or instances of MTCH transmission. In some examples, bandwidth and the number of duplicates or instances may be negatively correlated. For example, higher bandwidth may result in fewer duplicates or instances or no duplicates or instances, while lower bandwidth may result in a greater number of duplicates or instances. Such an approach may also apply if MTCH transmission 225 is a broadcast or multicast transmission (e.g., it may include situations where UE 115-a is in an inactive mode or state (e.g., RRC_INACTIVE mode or state) or an active or connected mode or state (e.g., RRC_CONNECTED mode or state)).

[0109] For example, if the bandwidth of MTCH transmission 225 is less than a first bandwidth threshold (e.g., 5MHz), network entity 105-a may transmit MTCH transmission 225 for a maximum number of repetitions or instances (e.g., 16 repetitions or instances) to eRedCap UEs (the same as RedCap UEs and non-RedCap UEs). Furthermore, if the bandwidth of the broadcast MTCH for eRedCap is greater than the first bandwidth threshold (e.g., 5MHz) and less than the second bandwidth threshold (e.g., 10MHz), network entity 105-a may transmit MTCH transmission 225 for eRedCap UEs with even fewer repetitions or instances (e.g., up to eight repetitions or instances). Moreover, if the bandwidth of MTCH transmission is greater than the second bandwidth threshold (e.g., 10MHz) and less than the third bandwidth threshold (e.g., 20MHz), network entity 105-a may transmit MTCH transmission 225 for eRedCap UEs with even fewer repetitions or instances (e.g., up to four repetitions or instances). Furthermore, if the bandwidth of MTCH transmission 225 is greater than a third bandwidth threshold (e.g., 20 MHz), network entity 105-a may not transmit any additional repetitions or instances of MTCH transmission 225 (e.g., repetition may be disallowed). This approach may also apply if MTCH transmission 225 is a broadcast or multicast transmission. In some examples where multiple repetitions or instances are transmitted, the repetitions or instances may be transmitted in back-to-back or consecutive time slots, or in non-back-to-back or non-consecutive time slots, or a combination thereof.

[0110] Such schemes can be applied equally to both multicast and broadcast transmissions. For example, the scheme discussed above, which utilizes multiple thresholds and MTCH to transmit different numbers of repetitions or instances of 225, can be applied equally to both broadcast and multicast transmissions, including multicast transmissions in which UE 115-a operates in an inactive mode or state (e.g., RRC_INACTIVE mode or state) or an active or connected mode or state (e.g., RRC_CONNECTED mode or state).

[0111] In some examples, UE 115-a (and optionally, UE 115-b) may operate in a connected mode or state (e.g., RRC_CONNECTED), and CFR 240 may be configured for use by UE 115-a (and optionally, UE 115-b) via control signaling (e.g., control signaling 220 or other control signaling). In some examples, network entity 105-a may allow or disallow bandwidth exceeding a bandwidth threshold (e.g., 5 MHz) for MTCH transmission 225 based on whether UE 115-a wishes to provide feedback or acknowledgment associated with MTCH transmission 225 (e.g., acknowledgment indication 235 is included in control signaling 220, or acknowledgment indication 235 instructs UE 115-a to provide acknowledgment 245, which may be ACK, NACK, or other feedback or acknowledgment). For example, if UE 115-a wishes to provide acknowledgment 245, network entity 105-a may not transmit MTCH transmission 225 on bandwidth exceeding the bandwidth threshold. Similarly, if no instruction is given to UE 115-a to provide acknowledgment 245 (e.g., acknowledgment instruction 235 is not included in control signaling 220 or acknowledgment instruction 235 indicates that UE 115-a will not provide acknowledgment 245), network entity 105-a may transmit MTCH transmission 225 on a bandwidth greater than the bandwidth threshold. UE 115-a may also determine the expected bandwidth for MTCH transmission 225. For example, if UE 115-a is to provide acknowledgment 245, UE 115-a may determine that MTCH transmission 225 is not permitted on a bandwidth greater than the bandwidth threshold. Similarly, if no instruction is given to UE 115-a to provide acknowledgment 245, UE 115-a may determine that MTCH transmission 225 is permitted on a bandwidth greater than the bandwidth threshold. In some examples, instructions instructing UE 115-a to provide or not provide acknowledgment 245 may be provided on one or more different bases. For example, enabling or disabling acknowledgment 245 can be provided on a per-identifier basis (e.g., group radio network temporary identifier (G_RNTI), group configured scheduling radio network temporary identifier (G-CS_RNTI), one or more other identifiers, or any combination thereof).

[0112] In some examples, UE 115-a (and optionally, UE 115-b) may operate in a connected mode or state (e.g., RRC_CONNECTED). In such scenarios, the operation involving multiple repetitions or instances of MTCH transmission 225 sent by network entity 105-a can be modified. For example, if UE 115-a is to provide acknowledgment 245 (which in turn may disallow transmission of MTCH transmission 225 on bandwidths greater than a bandwidth threshold (such as 5 MHz), then multiple repetitions or instances may be supported for transmission to UE 115-a (e.g., in a manner similar to the use of multiple repetitions or instances in a unicast scenario involving UE 115-a). However, if UE 115-a does not provide acknowledgment 245 (e.g., it may allow the transmission of MTCH transmission 225 on a bandwidth greater than a bandwidth threshold such as 5 MHz), then multiple repetitions or instances of MTCH transmission 225 may not be allowed, or the number of repetitions or instances of MTCH transmission 225 transmitted by network entity 105-a may depend on the bandwidth of MTCH transmission 225 (e.g., following one or more schemes as described herein for adjusting repetitions or instances based on bandwidth).

[0113] Figure 3A and Figure 3B Examples of MBS schemes 300 and 301 for supporting multicast or broadcast operations using enhanced reduced capability user equipment, as disclosed herein, are shown.

[0114] MBS scheme 300 can depict a communication scenario where the number of repetitions or instances of broadcast or multicast communication (e.g., MTCH transmission 225) depends on the bandwidth on which the repetitions or instances are to be transmitted. For example, if MTCH transmission 225 is to be transmitted on a first bandwidth 335 falling below a first threshold 320 (e.g., 5 MHz), a corresponding number of instances 315 (e.g., sixteen) can be transmitted. Similarly, if MTCH transmission 225 is to be transmitted on a second bandwidth 340 falling above the first threshold 320 (e.g., 5 MHz) and below a second threshold 325 (e.g., 10 MHz), a corresponding number of instances 315 (e.g., eight) can be transmitted. Similarly, if MTCH transmission 225 is to be transmitted on a third bandwidth 345 falling above the second threshold 325 (e.g., 10 MHz) and below a third threshold 330 (e.g., 15 MHz), a corresponding number of instances 315 (e.g., four) can be transmitted. Finally, if MTCH transmission 225 is to be transmitted on a fourth bandwidth 350 that falls above the third threshold 330 (e.g., 15 MHz), then a corresponding number of instances 315 (e.g., one) can be transmitted. As shown, there may be a negative correlation or relationship between bandwidths (e.g., first bandwidth 335, second bandwidth 340, third bandwidth 345, and fourth bandwidth 350) and the corresponding number of instances 315, because a larger bandwidth may be associated with a smaller number of instances 315, and a smaller bandwidth may be associated with a larger number of instances 315.

[0115] MBS scheme 301 can depict a communication scenario where the bandwidth for transmitting broadcast or multicast communication (e.g., MTCH transmission 225) depends on whether the UE (e.g., UE 115-a) is required to provide acknowledgment 355. For example, if the UE does not provide acknowledgment 355, broadcast or multicast communication can be transmitted on a sixth bandwidth 370 that may exceed a fourth threshold 360 (e.g., 5 MHz). In such a scenario, the UE may expect to allow the sixth bandwidth 370 to exceed the fourth threshold 360, although this is not required. However, if the UE is required to provide acknowledgment 355, broadcast or multicast transmission can be transmitted on a fifth bandwidth 365 that may not exceed the fourth threshold 360 (e.g., 5 MHz). In such a scenario, the UE may expect to disallow the fifth bandwidth 365 to exceed the fourth threshold 360.

[0116] In some cases, even if the UE is required to provide acknowledgment 355, the UE may determine that the bandwidth for broadcast or multicast transmission (e.g., sixth bandwidth 370) is permitted to exceed the fourth threshold 360. However, in such cases, the network entity may schedule additional time 375 for the UE to handle the larger bandwidth communication and provide acknowledgment 355 (e.g., if no additional time 375 is provided, this may be beyond the capabilities of the eRedCap UE). In cases involving such “anomalies” where the UE is required to provide acknowledgment 355 and the bandwidth (e.g., sixth bandwidth) is permitted to exceed the bandwidth threshold (e.g., fourth threshold 360), the network entity may (e.g., via control signaling or control information) signal to the UE that such a scenario may occur, that additional time 375 is available, or both.

[0117] Furthermore, in some cases, if the UE is to provide acknowledgment 355, the use of multiple duplicates or instances can be enabled or activated because the fifth bandwidth 365 may not be allowed to exceed the fourth threshold 360. In such cases, the RedCap UE is able to receive or process duplicates given a limited fifth bandwidth. In some cases, if the UE does not provide acknowledgment 355, thus including the possibility that bandwidth (e.g., the sixth bandwidth 370) exceeds the fourth threshold 360, the number of duplicates or instances may depend on the amount of bandwidth being used or be adjusted based on the amount of bandwidth being used (e.g., as per [reference to...]). Figure 3A (and as described elsewhere in this article).

[0118] Figure 4 An example of process flow 400 for supporting multicast or broadcast operations using enhanced degraded capability user equipment, according to one or more examples disclosed herein. Process flow 400 may implement various aspects of this disclosure as described herein. Elements described in process flow 400 (e.g., UE 115-c and network entity 105-b) may be examples of similarly named elements described herein.

[0119] In the following description of process flow 400, operations between various entities or elements may be performed in different orders or at different times. Some operations may also be excluded from process flow 400, or other operations may be added. Although various entities or elements are shown as performing operations of process flow 400, some aspects of some operations may also be performed by other entities or elements of process flow 400, or by entities or elements not depicted in the process flow, or any combination thereof.

[0120] At 420, UE 115-c can receive control information that schedules multicast service channel transmission and indicates the bandwidth of that multicast service channel. In some examples, the control information is included in downlink control information signaling.

[0121] At 425, UE 115-c may determine the number of one or more instances based on the bandwidth transmitted through the multicast service channel. In some examples, UE 115-c may determine the number of one or more instances transmitted through the multicast service channel based on a comparison of the bandwidth transmitted through the multicast service channel with multiple bandwidth thresholds, and each bandwidth threshold may be associated with a corresponding number of supported instances. In some examples, determining the number of one or more instances transmitted through the multicast service channel may include determining that a first bandwidth threshold among multiple bandwidth thresholds is the maximum bandwidth threshold satisfied by the bandwidth transmitted through the multicast service channel.

[0122] In some examples, determining the number of one or more instances transmitted by the multicast service channel may include determining the number of one or more instances transmitted by the multicast service channel as a corresponding number of supported instances associated with a first bandwidth threshold. In some examples, the number of supported instances may be negatively correlated with multiple bandwidth thresholds. In some examples, one of the multiple bandwidth thresholds may be 5 MHz.

[0123] At 430, UE 115-c can receive one or more instances transmitted by a multicast service channel in multiple time slots based on control information, and the number of such instances is based on the bandwidth of the multicast service channel transmission. In some examples, the bandwidth of the multicast service channel transmission is greater than a bandwidth threshold, and the number of one or more instances is one. In some examples, the bandwidth of the multicast service channel transmission may be less than the bandwidth threshold, and the number of one or more instances is two or more. In some examples, the bandwidth threshold may be 5 MHz. In some examples, the multicast service channel transmission may be multicast transmission or broadcast transmission. In some examples, the multiple time slots may be consecutive time slots or non-consecutive time slots.

[0124] Figure 5 An example of process flow 500 for supporting multicast or broadcast operations using enhanced degraded capability user equipment, according to one or more examples disclosed herein. Process flow 500 may implement various aspects of this disclosure as described herein. Elements described in process flow 500 (e.g., UE 115-d and network entity 105-c) may be examples of similarly named elements described herein.

[0125] In the following description of process flow 500, operations between various entities or elements may be performed in different orders or at different times. Some operations may also be excluded from process flow 500, or other operations may be added. Although various entities or elements are shown as performing operations of process flow 500, some aspects of some operations may also be performed by other entities or elements of process flow 500, or by entities or elements not depicted in the process flow, or any combination thereof.

[0126] At 520, UE 115-d can receive schedulable multicast traffic channel transmissions and can indicate whether the UE should send an acknowledgment in response to the multicast traffic channel transmission. In some examples, the control information may indicate whether the UE should send an acknowledgment in response to the multicast traffic channel transmission based on an identifier associated with the UE. In some examples, the control information may be included in downlink control information signaling, radio resource control signaling, or both. In some examples, UE 115-d can operate in connected mode.

[0127] At point 525, UE 115-d may determine that the bandwidth of the multicast service channel transmission is not allowed to exceed a bandwidth threshold based on control information instructing the UE to send an acknowledgment in response to the multicast service channel transmission. In some examples, the bandwidth threshold is 5 MHz. Alternatively or additionally, UE 115-d may determine that the bandwidth of the multicast service channel transmission is allowed to exceed the bandwidth threshold based on control information instructing the UE not to send an acknowledgment in response to the multicast service channel transmission. In some examples, the bandwidth threshold is 5 MHz. Alternatively or additionally, UE 115-d may determine that the bandwidth of the multicast service channel transmission is allowed to exceed the bandwidth threshold based on control information instructing the UE to send an acknowledgment in response to the multicast service channel transmission and control information scheduling a second resource for UE to send acknowledgments, which is later in time than a first resource scheduled for feedback transmission when the bandwidth of the multicast service channel transmission is less than the bandwidth threshold. In some examples, the bandwidth threshold is 5 MHz.

[0128] At 530, UE 115-d can receive multicast service channel transmissions based on control information. Multicast service channel transmissions can be received on bandwidth where the UE sends an acknowledgment based on whether it wishes to respond to the multicast service channel transmission.

[0129] At 535, UE 115-d can send an acknowledgment (e.g., a positive acknowledgment or a negative acknowledgment). In some examples, the acknowledgment is a hybrid automatic repeat request acknowledgment feedback.

[0130] Figure 6 A block diagram 600 illustrates a device 605 for supporting multicast or broadcast operations using enhanced degraded capability user equipment according to one or more examples disclosed herein. Device 605 may be an example of aspects of UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communications manager 620), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0131] Receiver 610 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels associated with support for multicast or broadcast operations using enhanced degraded capability user equipment). The information may be delivered to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0132] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels associated with support for multicast or broadcast operations using enhanced degraded capability user equipment). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0133] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of supporting multicast or broadcast operations using enhanced degraded capability user equipment as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may be capable of performing one or more of the functions described herein.

[0134] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, digital signal processor (DSP), central processing unit (CPU), graphics processing unit (GPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0135] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software). If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, GPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0136] In some examples, the communication manager 620 may be configured to use or otherwise cooperate with the receiver 610, the transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0137] Additionally or alternatively, the communication manager 620 may support wireless communication according to examples disclosed herein. For example, the communication manager 620 may be capable of, configured to, or operable to support components for receiving control information that schedules multicast traffic channel transmissions and indicates the bandwidth of the multicast traffic channel transmissions. The communication manager 620 may be capable of, configured to, or operable to support components for receiving one or more instances of multicast traffic channel transmissions in multiple time slots based on control information, wherein the number of such one or more instances is based on the bandwidth of the multicast traffic channel transmissions.

[0138] Additionally or alternatively, the communication manager 620 may support wireless communication according to examples disclosed herein. For example, the communication manager 620 may be capable of, configured to, or operable to support components for receiving control information for scheduling multicast service channel transmissions and instructing the UE whether to send an acknowledgment in response to the multicast service channel transmission. The communication manager 620 may be capable of, configured to, or operable to support components for receiving multicast service channel transmissions based on control information, wherein the multicast service channel transmissions are received on a bandwidth based on whether the UE wants to send an acknowledgment in response to the multicast service channel transmission.

[0139] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., at least one processor that controls or is otherwise coupled to receiver 610, transmitter 615, communication manager 620, or a combination thereof) can support techniques for reducing processing, lowering power consumption, utilizing communication resources more efficiently, or any combination thereof.

[0140] Figure 7 A block diagram 700 illustrates a device 705 for supporting multicast or broadcast operations using enhanced degraded capability user equipment according to one or more examples disclosed herein. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communications manager 720), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0141] Receiver 710 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels associated with support for multicast or broadcast operations using enhanced degraded capability user equipment). Information may be delivered to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0142] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels associated with support for multicast or broadcast operations using enhanced degraded capability user equipment). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0143] Device 705 or its various components may be examples of parts used to perform various aspects of supporting multicast or broadcast operations using enhanced degraded capability user equipment as described herein. For example, communication manager 720 may include control information component 725, MTCH receiving component 730, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use or otherwise cooperate with receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0144] The communication manager 720 may support wireless communication according to examples disclosed herein. The control information component 725 is capable of, configured to, or operable to support components for receiving control information that schedules multicast traffic channel transmission and indicates the bandwidth of the multicast traffic channel transmission. The MTCH receiving component 730 is capable of, configured to, or operable to support components for receiving one or more instances of multicast traffic channel transmission in multiple time slots according to control information, wherein the number of such instances is based on the bandwidth of the multicast traffic channel transmission.

[0145] Additionally or alternatively, the communication manager 720 may support wireless communication according to examples disclosed herein. The control information component 725 is capable of, configured to, or operable to support components for receiving control information for scheduling multicast service channel transmissions and instructing the UE whether to send an acknowledgment in response to the multicast service channel transmission. The MTCH receiving component 730 is capable of, configured to, or operable to support components for receiving multicast service channel transmissions based on control information, wherein the multicast service channel transmissions are received on a bandwidth based on whether the UE wants to send an acknowledgment in response to the multicast service channel transmission.

[0146] Figure 8 A block diagram 800 is shown of a communication manager 820 that supports multicast or broadcast operations using enhanced degraded capability user equipment according to one or more examples disclosed herein. The communication manager 820 may be an example of aspects of the communication manager 620, communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of parts for performing various aspects of supporting multicast or broadcast operations using enhanced degraded capability user equipment as described herein. For example, the communication manager 820 may include a control information component 825, an MTCH receiving component 830, an instance determination component 835, a bandwidth determination component 840, an acknowledgment component 845, an operation mode component 850, a bandwidth threshold component 855, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0147] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. The control information component 825 is capable of, configured to, or operable to support components for receiving control information that schedules multicast traffic channel transmissions and indicates the bandwidth of the multicast traffic channel transmissions. The MTCH receiving component 830 is capable of, configured to, or operable to support components for receiving one or more instances of multicast traffic channel transmissions in multiple time slots according to control information, wherein the number of such instances is based on the bandwidth of the multicast traffic channel transmissions.

[0148] In some examples, the instance determination component 835 is capable of, configured to, or able to operate to support a component used to determine the number of one or more instances based on the bandwidth transmitted on the multicast traffic channel.

[0149] In some examples, the instance determination component 835 is capable of, configured to, or operable to support a component that determines the number of one or more instances of multicast traffic channel transmission by comparing the bandwidth used for transmission based on the multicast traffic channel with a set of multiple bandwidth thresholds, wherein each bandwidth threshold is associated with a corresponding number of supported instances.

[0150] In some examples, to support determining the number of one or more instances transmitted by a multicast service channel, bandwidth determination component 840 is capable of, configured to, or operable to support components for determining that a first bandwidth threshold in a set of multiple bandwidth thresholds is the maximum bandwidth threshold satisfied by the bandwidth transmitted by the multicast service channel. In some examples, to support determining the number of one or more instances transmitted by a multicast service channel, instance determination component 835 is capable of, configured to, or operable to support components for determining the number of one or more instances transmitted by the multicast service channel as a supported number of instances associated with the first bandwidth threshold.

[0151] In some examples, the set of multiple supported instance counts is negatively correlated with the set of multiple bandwidth thresholds. In some examples, one of the bandwidth thresholds in the set of multiple bandwidth thresholds is 5 MHz. In some examples, the bandwidth transmitted by the multicast service channel is greater than the bandwidth threshold. In some examples, the number of one or more instances is one. In some examples, the bandwidth threshold is 5 MHz. In some examples, the bandwidth transmitted by the multicast service channel is less than the bandwidth threshold. In some examples, the number of one or more instances is two or more. In some examples, the bandwidth threshold is 5 MHz. In some examples, control information is included in the downlink control information signaling. In some examples, the multicast service channel transmission is either multicast or broadcast. In some examples, the multiple time slots are either consecutive or discontinuous time slots.

[0152] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. In some examples, the control information component 825 is capable of, configured to, or operable to support components for receiving control information for scheduling multicast traffic channel transmissions and instructing the UE whether to send an acknowledgment in response to the multicast traffic channel transmission. In some examples, the MTCH receiving component 830 is capable of, configured to, or operable to support components for receiving multicast traffic channel transmissions based on control information, wherein the multicast traffic channel transmissions are received on a bandwidth based on whether the UE wants to send an acknowledgment in response to the multicast traffic channel transmission.

[0153] In some examples, the bandwidth determination component 840 is capable of, configured to, or able to operate to support components for determining that the bandwidth of a multicast channel transmission is not allowed to exceed a bandwidth threshold based on control information instructing the UE to send acknowledgments in response to multicast channel transmission. In some examples, the bandwidth threshold is 5 MHz.

[0154] In some examples, the bandwidth determination component 840 is capable of, configured to, or operable to support components for determining whether the bandwidth for multicast channel transmission is allowed to exceed a bandwidth threshold based on control information instructing the UE not to send acknowledgments in response to multicast channel transmission. In some examples, the bandwidth threshold is 5 MHz.

[0155] In some examples, the acknowledgment component 845 is capable, configured, or able to operate to support the following: determining that the bandwidth of the multicast service channel transmission is allowed to exceed the bandwidth threshold based on control information instructing the UE to send an acknowledgment in response to the multicast service channel transmission and control information scheduling a second resource for the UE to send an acknowledgment, which is later in time than a first resource scheduled for feedback transmission when the bandwidth of the multicast service channel transmission is less than the bandwidth threshold.

[0156] In some examples, the control information indicates whether the UE should send an acknowledgment in response to a multicast traffic channel transmission based on an identifier associated with the UE. In some examples, the acknowledgment is a hybrid automatic repeat request acknowledgment feedback. In some examples, the UE operates in connected mode. In some examples, the control information is included in downlink control information signaling, radio resource control signaling, or both.

[0157] Figure 9 A diagram is shown of a system 900 including device 905 supporting multicast or broadcast operations using enhanced degraded capability user equipment, according to one or more examples disclosed herein. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or may include components thereof. Device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 945).

[0158] I / O controller 910 manages the input and output signals of device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0159] In some cases, device 905 may include a single antenna 925. However, in other cases, device 905 may have more than one antenna 925, which can concurrently transmit or receive multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925 as described herein, or via a wired or wireless link. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0160] At least one memory 930 may include random access memory (RAM) and read-only memory (ROM). At least one memory 930 may store computer-readable, computer-executable code 935, including instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 930 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0161] At least one processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, GPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., functions or tasks that support multicast or broadcast operations using enhanced degraded capability user equipment). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, wherein at least one processor 940 and at least one memory 930 are configured to perform the various functions described herein. In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0162] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for receiving control information that schedules multicast traffic channel transmissions and indicates the bandwidth of the multicast traffic channel transmissions. The communication manager 920 may be capable of, configured to, or operable to support components for receiving one or more instances of multicast traffic channel transmissions in multiple time slots based on control information, wherein the number of such one or more instances is based on the bandwidth of the multicast traffic channel transmissions.

[0163] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for receiving control information for scheduling multicast service channel transmissions and instructing the UE whether to send an acknowledgment in response to the multicast service channel transmission. The communication manager 920 may be capable of, configured to, or operable to support components for receiving multicast service channel transmissions based on control information, wherein the multicast service channel transmissions are received on a bandwidth based on whether the UE wants to send an acknowledgment in response to the multicast service channel transmission.

[0164] By including or configuring a communication manager 920 according to an example as described herein, device 905 may support techniques for improving communication reliability, reducing latency, improving and reducing processing-related user experience, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, improving utilization of processing power, or any combination thereof.

[0165] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with transceiver 915, one or more antennas 925, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported by or performed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause device 905 to perform various aspects of supporting multicast or broadcast operations as described herein using enhanced degraded capability user equipment, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0166] Figure 10A flowchart illustrating a method 1000 for supporting multicast or broadcast operations using an enhanced degraded capability user equipment (UE) according to an example disclosed herein is shown. The operation of method 1000 can be implemented by a UE or its components as described herein. For example, the operation of method 1000 can be implemented by, as referenced herein... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0167] At 1005, the method may include receiving control information that schedules broadcast transmission and indicates the bandwidth of the broadcast transmission. The operation of block 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1005 may be provided by reference to [reference needed]. Figure 8 The control information component 825 described herein is used to perform this action.

[0168] At 1010, the method may include receiving one or more instances of broadcast transmission in multiple time slots according to control information, wherein the number of such instances is associated with the bandwidth of the broadcast transmission. The operation of block 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1010 may be provided by reference to [reference needed]. Figure 8 The MTCH receiving component 830 described herein is used to perform this action.

[0169] Figure 11 A flowchart illustrating a method 1100 for supporting multicast or broadcast operation using an enhanced degraded capability user equipment according to an example disclosed herein is shown. Operation of method 1100 may be implemented by a UE or its components as described herein. For example, operation of method 1100 may be implemented by, as referenced herein... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0170] At 1105, the method may include receiving control information for scheduling multicast service channel transmission and instructing the UE whether to send an acknowledgment in response to the multicast service channel transmission. The operation of block 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1105 may be provided by reference to [reference needed]. Figure 8 The control information component 825 described herein is used to perform this action.

[0171] At 1110, the method may include receiving a multicast service channel transmission based on control information, wherein the multicast service channel transmission is received on bandwidth on which an acknowledgment is sent based on whether the UE wishes to respond to the multicast service channel transmission. The operation of block 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1110 may be provided by reference to [reference needed]. Figure 8 The MTCH receiving component 830 described herein is used to perform this action.

[0172] The following provides an overview of the various aspects of this disclosure:

[0173] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving control information that schedules broadcast transmission and indicates the bandwidth of the broadcast transmission; and receiving one or more instances of the broadcast transmission in a plurality of time slots according to the control information, wherein the number of the one or more instances is at least partially based on the bandwidth of the broadcast transmission.

[0174] Aspect 2: According to the method of aspect 1, wherein the bandwidth of the broadcast transmission being greater than the bandwidth threshold is associated with the number of the one or more instances, and wherein the bandwidth of the broadcast transmission being less than the bandwidth threshold is associated with the number of the one or more instances being two or greater.

[0175] Aspect 3: According to the method of aspect 2, the bandwidth threshold is 5MHz.

[0176] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the bandwidth threshold is based at least in part on 25 physical resource blocks and a subcarrier spacing of 15 kHz or 12 physical resource blocks and a subcarrier spacing of 30 kHz.

[0177] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the bandwidth of the broadcast transmission indicates the number of the one or more instances to be processed by the UE.

[0178] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the bandwidth of the broadcast transmission is less than a bandwidth threshold, wherein the bandwidth of the broadcast transmission is less than the bandwidth threshold at least in part based on the broadcast service channel, wherein the one or more instances include a plurality of instances, and wherein the method further includes: processing the plurality of instances at least in part based on the bandwidth of the broadcast transmission being less than the bandwidth threshold.

[0179] Aspect 7: The method according to any one of Aspects 1 to 2, the method further comprising: determining the number of the one or more instances of the broadcast transmission based at least in part on a comparison of the bandwidth of the broadcast transmission with a plurality of bandwidth thresholds, wherein each bandwidth threshold is associated with a corresponding number of supported instances.

[0180] Aspect 8: According to the method of aspect 3, determining the number of the one or more instances of the broadcast transmission further includes: determining a first bandwidth threshold among the plurality of bandwidth thresholds as the maximum bandwidth threshold satisfied by the bandwidth of the broadcast transmission; and determining the number of the one or more instances of the broadcast transmission as the corresponding number of supported instances associated with the first bandwidth threshold.

[0181] Aspect 9: The method according to any one of Aspects 3 to 4, wherein the number of multiple supported instances is negatively correlated with the multiple bandwidth thresholds.

[0182] Aspect 10: The method according to any one of aspects 3 to 5, wherein one of the plurality of bandwidth thresholds is 5 MHz.

[0183] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the control information is included in downlink control information signaling.

[0184] Aspect 12: The method according to any one of aspects 1 to 11, wherein the plurality of time slots are continuous time slots or discontinuous time slots.

[0185] Aspect 13: A method for wireless communication at a UE, the method comprising: receiving control information that schedules multicast service channel transmission and instructs the UE whether to transmit an acknowledgment in response to the multicast service channel transmission; and receiving the multicast service channel transmission according to the control information, wherein the multicast service channel transmission is received on a bandwidth at least in part based on whether the UE wants to transmit the acknowledgment in response to the multicast service channel transmission.

[0186] Aspect 14: The method according to aspect 13, the method further comprising: determining, at least in part, based on the control information instructing the UE to send the acknowledgment in response to the transmission of the multicast service channel, that the bandwidth of the multicast service channel transmission is not allowed to exceed a bandwidth threshold.

[0187] Aspect 15: The method according to aspect 14, wherein the bandwidth threshold is 5 MHz.

[0188] Aspect 16: The method according to any one of Aspects 13 to 15, the method further comprising: determining, at least in part, based on the control information instructing the UE not to send the acknowledgment in response to the transmission of the multicast service channel, that the bandwidth of the multicast service channel transmission is allowed to exceed a bandwidth threshold.

[0189] Aspect 17: The method according to aspect 16, wherein the bandwidth threshold is 5 MHz.

[0190] Aspect 18: The method according to any one of Aspects 13 to 17, the method further comprising: determining, at least in part, that the bandwidth of the multicast service channel transmission is permitted to exceed the bandwidth threshold, based on control information instructing the UE to transmit the acknowledgment in response to the transmission of the multicast service channel and control information scheduled for the UE to transmit the acknowledgment, which is later in time than a second resource scheduled for feedback transmission of a first resource when the bandwidth of the multicast service channel transmission is less than a bandwidth threshold.

[0191] Aspect 19: The method according to any one of Aspects 13 to 18, wherein the control information is at least partially based on an identifier associated with the UE to indicate whether the UE wants to send an acknowledgment in response to the transmission of the multicast service channel.

[0192] Aspect 20: The method according to any one of aspects 13 to 19, wherein the confirmation is a hybrid automatic repeating request confirmation feedback.

[0193] Aspect 21: The method according to any one of Aspects 13 to 20, wherein the UE operates in a connection mode.

[0194] Aspect 22: The method according to any one of Aspects 13 to 21, wherein the control information is included in downlink control information signaling, radio resource control signaling, or both.

[0195] Aspect 23: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the UE performs a method according to any one of aspects 1 to 12.

[0196] Aspect 24: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 12.

[0197] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 1 to 12.

[0198] Aspect 26: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the UE performs a method according to any one of aspects 13 to 22.

[0199] Aspect 27: A UE for wireless communication, the UE including at least one component for performing a method according to any one of aspects 13 to 22.

[0200] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform the method according to any one of aspects 13 to 22.

[0201] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0202] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0203] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0204] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, GPU, FPGA, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0205] The functionality described herein can be implemented using hardware, software executed by a processor, or any combination thereof. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether or not it is referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. When implemented using software executed by a processor, the functionality can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, hardware, hardwired, or any combination thereof. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.

[0206] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase-change memory, compact disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures and is accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0207] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on". As used herein, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items may be used alone, or any combination of two or more of the listed items may be used. For example, if a composition is described as containing components A, B and / or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B and C.

[0208] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0209] The terms "determine" or "identify" encompass a variety of actions, and therefore, "determine" or "identify" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), ascertainment, etc. Additionally, "determine" or "identify" can include receiving (such as receiving information or signaling, e.g., receiving information or signaling for determination, receiving information or signaling for identification), accessing (such as accessing data in memory or accessing information), etc. Furthermore, "determine" or "identify" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0210] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0211] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0212] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and capable of operating, alone or in combination, to execute the code to cause the UE to: receive control information scheduling a broadcast transmission and indicating a bandwidth of the broadcast transmission; and receive one or more instances of the broadcast transmission in a plurality of slots in accordance with the control information, wherein a number of the one or more instances is associated with the bandwidth of the broadcast transmission.

2. The UE of claim 1, wherein: the bandwidth of the broadcast transmission is greater than a bandwidth threshold is associated with the number of the one or more instances being one; and the bandwidth of the broadcast transmission is less than the bandwidth threshold is associated with the number of the one or more instances being two or greater.

3. The UE of claim 2, wherein: the bandwidth threshold is 5 MHz.

4. The UE of claim 2, wherein: the bandwidth threshold is based at least in part on 25 physical resource blocks and a subcarrier spacing of 15 kHz or 12 physical resource blocks and a subcarrier spacing of 30 kHz.

5. The UE of claim 1, wherein the bandwidth of the broadcast transmission indicates the number of the one or more instances to be processed by the UE.

6. The UE of claim 1, wherein the bandwidth of the broadcast transmission is less than a bandwidth threshold, wherein based at least in part on the bandwidth of the broadcast transmission being less than the bandwidth threshold, the one or more instances comprises a plurality of instances, and wherein the one or more processors are capable of operating, alone or in combination, to further execute the code to cause the UE to: process the plurality of instances based at least in part on the bandwidth of the broadcast transmission being less than the bandwidth threshold.

7. The UE of claim 1, wherein the one or more processors are capable of operating, alone or in combination, to further execute the code to cause the UE to: determine the number of the one or more instances of the broadcast transmission based at least in part on a comparison of the bandwidth of the broadcast transmission to a plurality of bandwidth thresholds, wherein each bandwidth threshold is associated with a respective number of supported instances.

8. The UE of claim 7, wherein, to determine the number of the one or more instances of the broadcast transmission, the one or more processors are capable of operating, alone or in combination, to further execute the code to cause the UE to: determine that a first bandwidth threshold of the plurality of bandwidth thresholds is a largest bandwidth threshold that is satisfied by the bandwidth of the broadcast transmission; and determine the number of the one or more instances of the broadcast transmission to be the respective number of supported instances associated with the first bandwidth threshold.

9. The UE of claim 7, wherein the number of supported instances is inversely related to the plurality of bandwidth thresholds.

10. The UE of claim 7, wherein: one of the plurality of bandwidth thresholds is 5 MHz.

11. A user equipment (UE), the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and capable of operating, alone or in combination, to execute the code to cause the UE to: receive control information scheduling a multicast traffic channel transmission and indicating whether the UE is to transmit an acknowledgement in response to the multicast traffic channel transmission; and receive the multicast traffic channel transmission in accordance with the control information, wherein the multicast traffic channel transmission is received over a bandwidth that is based at least in part on whether the UE is to transmit the acknowledgement in response to the multicast traffic channel transmission.

12. The UE of claim 11, wherein the one or more processors are further capable of operating, alone or in combination, to execute the code to cause the UE to: determine that the bandwidth of the multicast traffic channel transmission is not permitted to exceed a bandwidth threshold based at least in part on the control information indicating that the UE is to transmit the acknowledgement in response to the multicast traffic channel transmission.

13. The UE of claim 12, wherein: the bandwidth threshold is 5 MHz.

14. The UE of claim 11, wherein the one or more processors are further capable of operating, alone or in combination, to execute the code to cause the UE to: determine that the bandwidth of the multicast traffic channel transmission is permitted to exceed a bandwidth threshold based at least in part on the control information indicating that the UE is not to transmit the acknowledgement in response to the multicast traffic channel transmission.

15. The UE of claim 14, wherein: the bandwidth threshold is 5 MHz.

16. The UE of claim 11, wherein the one or more processors are further capable of operating, alone or in combination, to execute the code to cause the UE to: determine that the bandwidth of the multicast traffic channel transmission is permitted to exceed a bandwidth threshold based at least in part on the control information indicating that the UE is to transmit the acknowledgement in response to the multicast traffic channel transmission and the control information scheduling a second resource for the UE to transmit the acknowledgement that is later in time than a first resource scheduled for a feedback transmission when the bandwidth of the multicast traffic channel transmission is less than the bandwidth threshold.

17. The UE of claim 11, wherein the control information indicates whether the UE is to transmit the acknowledgement in response to the multicast traffic channel transmission based at least in part on an identifier associated with the UE.

18. The UE of claim 11, wherein: the acknowledgement is hybrid automatic repeat request acknowledgement feedback.

19. The UE of claim 11, wherein the UE is operating in a connected mode.

20. A method for wireless communication at a user equipment (UE), the method comprising: receiving control information scheduling a broadcast transmission and indicating a bandwidth of the broadcast transmission; and to receive one or more instances of the broadcast transmission in a plurality of time slots in accordance with the control information, wherein a number of the one or more instances is associated with the bandwidth of the broadcast transmission.

Images