Feedback signaling in carrier aggregation and external coding scenarios

Abstract

Methods, systems, and devices for wireless communication are described. A UE may receive externally coded downlink signaling via carrier aggregation, and may deactivate a retransmission protocol, and then select at least one of two different feedback modes. The first feedback mode may include a Radio Link Control (RLC) status reporting mode (e.g., which may be referred to as Mode 1 or RLC Mode 1). The second feedback mode is a hybrid automatic repeat request (HARQ) feedback mode (e.g., which may be referred to as mode 2 or HARQ mode 2). The network may configure the UE with parameters for operating in mode 1, mode 2, or both, or the UE may autonomously select a feedback mode. The UE may avoid sending additional feedback signaling, and retransmission may be deactivated, thereby improving power savings and using system resources more efficiently.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. patent application No. 18 / 157,769, filed on January 20, 2023, by ALLOUM et al., entitled “FEEDBACKSIGNALING IN CARRIER AGGREGATION AND OUTER CODING SCENARIOS,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications, including feedback signaling in carrier aggregation and external decoding scenarios. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and more. These systems can support 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-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-spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communication system may include one or more base stations, each of which supports wireless communication for communication devices, which may be referred to as user equipment (UE). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting feedback signaling in carrier aggregation and external coding scenarios. For example, the described techniques support deactivating a retransmission protocol when using external coding (e.g., in multicast use cases) and using an alternative feedback solution when retransmission has been deactivated. A user equipment (UE) receiving external coding downlink signaling via carrier aggregation can deactivate the retransmission protocol and then select at least one of two different feedback modes. The first feedback mode may include a radio link control (RLC) status reporting mode (e.g., which may be referred to as Mode 1 or RLC Mode 1). The second feedback mode is a hybrid automatic repeat request (HARQ) feedback mode (e.g., which may be referred to as Mode 2 or HARQ Mode 2). The two modes may also be used in combination. The network may configure the UE with parameters for operating in Mode 1, Mode 2, or both. In some examples, the network may indicate which mode the UE will use when the retransmission protocol is deactivated due to the use of external coding. In some examples, the UE may select a feedback mode based on satisfying one or more conditions, including when retransmission is deactivated. Regardless of the feedback mode used, feedback signaling may result in an update to the outer coding used (eg, may not result in retransmissions). The UE may avoid sending additional feedback signaling, and retransmissions may be disabled, thereby improving power conservation and more efficient use of system resources.

[0006] A method for wireless communication at a UE is described. The method may include: receiving one or more downlink messages from a network entity via carrier aggregation according to an outer coding transmission scheme; deactivating a retransmission protocol associated with the one or more downlink messages based on the outer coding transmission scheme being applied to the one or more downlink messages; selecting at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a hybrid automatic request report and a second set of resources based on the outer coding transmission scheme being applied to the one or more downlink messages; and transmitting a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0007] An apparatus for wireless communication at a user equipment terminal (UE) is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive one or more downlink messages from a network entity via carrier aggregation according to an external decoding transmission scheme; deactivate a retransmission protocol associated with the one or more downlink messages based on the external decoding transmission scheme being applied to the one or more downlink messages; select at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on the external decoding transmission scheme being applied to the one or more downlink messages; and transmit a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving one or more downlink messages from a network entity via carrier aggregation according to an external decoding transmission scheme; means for deactivating a retransmission protocol associated with the one or more downlink messages based on the external decoding transmission scheme being applied to the one or more downlink messages; means for selecting at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a hybrid automatic request report and a second set of resources based on the external decoding transmission scheme being applied to the one or more downlink messages; and means for transmitting a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a user equipment terminal (UE) is described. The code may include instructions executable by a processor to: receive one or more downlink messages from a network entity via carrier aggregation according to an outer coding transmission scheme; deactivate a retransmission protocol associated with the one or more downlink messages based on the outer coding transmission scheme being applied to the one or more downlink messages; select at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on the outer coding transmission scheme being applied to the one or more downlink messages; and transmit a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling from the network entity indicating one or more parameters for using the first feedback mode, the second feedback mode, or both, wherein the selection may be based on the one or more parameters.

[0011] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for selecting at least one of the first feedback mode or the second feedback mode based on satisfying one or more conditions, wherein the one or more conditions may be associated with a power state at the UE, a threshold latency corresponding to the one or more downlink messages, or a combination thereof.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the selection may include operations, features, components, or instructions for selecting a combination of the first feedback mode and the second feedback mode, wherein the first feedback mode corresponds to a first periodicity and the second feedback mode corresponds to a second periodicity, wherein the first periodicity may be greater than the second periodicity.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the feedback message may include operations, features, components, or instructions for: sending the first feedback message via the first set of resources according to the first periodicity; and sending the second feedback message via the second set of resources according to the second periodicity.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the feedback message may include operations, features, components, or instructions for: activating a first resource in the second set of resources according to the second periodicity; and sending a block error report, an indication of a lost message via a physical downlink control channel, or a combination thereof via the activated first resource in the second set of resources.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the first feedback message and the second feedback message may include operations, features, components, or instructions for alternating between sending via corresponding resources associated with the first set of resources according to the first periodicity and sending via corresponding resources associated with the second set of resources according to the second periodicity.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the feedback message may include operations, features, components, or instructions for sending an RLC status report via the first set of resources according to the first feedback mode based on detecting lost RLC packet data units, wherein a HARQ protocol associated with the second feedback mode may be disabled according to the selection.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for allowing one or more timers to expire or setting the one or more timers to zero based on selecting the first feedback mode, where the one or more timers may be associated with RLC status signaling.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for including in the RLC status report an indication of a number of segments associated with the outer decoding transmission scheme that may have been successfully received by the UE.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the feedback message may include operations, features, components, or instructions for sending a set of multiple feedback messages via the first set of resources of the primary component carrier of the first cell group and the second set of resources of the primary component carrier of the first cell group, the set of multiple feedback messages including the feedback message.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating the feedback message according to a HARQ codebook type, wherein sending the feedback message may be based on the generating.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: entering a sleep mode based on sending the feedback message; and deactivating the carrier aggregation, the outer coding transmission scheme, or both based on entering the sleep mode.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for avoiding sending one or more additional feedback messages via the first set of resources and the portion of the second set of resources associated with retransmitting the one or more downlink messages based on entering the sleep mode, deactivating the retransmission protocol, or both during at least a portion of the first set of resources and the second set of resources associated with retransmitting the one or more downlink messages.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an indication from the network entity that no additional downlink messages may be pending based on sending the feedback message, wherein entering the sleep mode may be based on receiving the indication.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, from the network entity, an indication of a threshold number of segments associated with the outer decoding transmission scheme, wherein entering the sleep mode may be based on the number of segments associated with the outer decoding transmission scheme that may have been successfully received by the UE satisfying the threshold number of segments.

[0025] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, from the network entity, an indication of a periodicity associated with the first feedback mode, the second feedback mode, or a combination thereof, wherein sending the feedback message may be based on the periodicity.

[0026] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling that triggers aperiodic feedback signaling via the first set of resources or the second set of resources, wherein sending the feedback message may be based on receiving the control signaling.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving control signaling indicating a carrier aggregation mode, an instruction to disable RLC retransmission, or a combination thereof.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the outer decoding transmission scheme includes a Packet Data Convergence Protocol (PDCP) distributed outer decoding scheme associated with a threshold link quality.

[0029] A method for wireless communication at a network entity is described. The method may include generating one or more downlink messages according to an outer coding transmission scheme; transmitting the one or more downlink messages to a UE via carrier aggregation according to the outer coding transmission scheme; selecting at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a hybrid automatic request report and a second set of resources based on generating the one or more downlink messages according to the outer coding transmission scheme; and receiving a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0030] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: generate one or more downlink messages according to an outer decoding transmission scheme; transmit the one or more downlink messages to a UE via carrier aggregation according to the outer decoding transmission scheme; select at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a hybrid automatic request report and a second set of resources based on generating the one or more downlink messages according to the outer decoding transmission scheme; and receive feedback messages corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0031] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for generating one or more downlink messages according to an outer decoding transmission scheme; means for transmitting the one or more downlink messages to a UE via carrier aggregation according to the outer decoding transmission scheme; means for selecting at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a hybrid automatic request report and a second set of resources based on generating the one or more downlink messages according to the outer decoding transmission scheme; and means for receiving a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0032] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to: generate one or more downlink messages according to an outer decoding transmission scheme; transmit the one or more downlink messages to a UE via carrier aggregation according to the outer decoding transmission scheme; select at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a hybrid automatic request report and a second set of resources based on generating the one or more downlink messages according to the outer decoding transmission scheme; and receive feedback messages corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling to the UE indicating one or more parameters for using the first feedback mode, the second feedback mode, or both, wherein the selection may be based on the one or more parameters.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for selecting at least one of the first feedback mode and the second feedback mode based on satisfying one or more conditions, wherein the one or more conditions may be associated with a power state at the UE, a threshold latency corresponding to the one or more downlink messages, or a combination thereof.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the selection may include operations, features, components, or instructions for selecting a combination of the first feedback mode and the second feedback mode, wherein the first feedback mode corresponds to a first periodicity and the second feedback mode corresponds to a second periodicity, wherein the first periodicity may be greater than the second periodicity.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the feedback message may include operations, features, components, or instructions for: receiving a first feedback message via the first set of resources according to the first periodicity; and receiving a second feedback message via the second set of resources according to the second periodicity.

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the first feedback message and the second feedback message may include operations, features, components, or instructions for alternating between receiving via corresponding resources associated with the first set of resources according to the first periodicity and receiving via corresponding resources associated with the second set of resources according to the second periodicity.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the feedback message may include operations, features, components, or instructions for sending an RLC status report indicating lost RLC packet data units via the first set of resources according to the first feedback mode, wherein a HARQ protocol associated with the second feedback mode may be disabled according to the selection.

[0039] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, in the RLC status report, an indication of a number of segments associated with the outer decoding transmission scheme that may have been successfully received by the UE.

[0040] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending an indication of a threshold number of segments associated with the outer decoding transmission scheme to the UE; and refraining from sending one or more additional segments associated with the outer decoding transmission scheme based on the number of segments associated with the outer decoding transmission scheme satisfying the threshold number of segments.

[0041] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the feedback message may include operations, features, components, or instructions for receiving a set of multiple feedback messages via the first set of resources of the primary component carrier of the first cell group and the second set of resources of the primary component carrier of the first cell group, the set of multiple feedback messages including the feedback message.

[0042] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the feedback message may include operations, features, components, or instructions for receiving the feedback message according to a HARQ codebook type.

[0043] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: avoiding sending one or more additional downlink messages based on receiving the feedback message; and avoiding monitoring one or more additional feedback messages during at least a portion of the first set of resources, the second set of resources, or both.

[0044] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for deactivating a retransmission protocol associated with the one or more downlink messages, wherein refraining from sending the one or more additional downlink messages may be based on the deactivation.

[0045] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication to the UE that the one or more additional downlink messages may not be pending, wherein avoiding sending the one or more additional downlink messages may be based on receiving the indication.

[0046] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending an indication to the UE of a periodicity associated with the first feedback mode, the second feedback mode, or a combination thereof, wherein receiving the feedback message may be based on the periodicity.

[0047] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling that triggers aperiodic feedback signaling via the first set of resources or the second set of resources, wherein receiving the feedback message may be based on receiving the control signaling.

[0048] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending control signaling indicating a carrier aggregation mode, an instruction to disable RLC retransmission, or a combination thereof.

[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the outer decoding transmission scheme includes a PDCP distributed outer decoding scheme associated with a threshold link quality. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 An example of a wireless communication system supporting carrier aggregation and feedback signaling in an outer coding scenario according to one or more aspects of the present disclosure is illustrated.

[0051] Figure 2 An example of a wireless communication system supporting carrier aggregation and feedback signaling in an outer coding scenario according to one or more aspects of the present disclosure is illustrated.

[0052] Figure 3 An example of a timeline for supporting feedback signaling in a carrier aggregation and outer coding scenario according to one or more aspects of the present disclosure is illustrated.

[0053] Figure 4 An example of a timeline for supporting feedback signaling in a carrier aggregation and outer coding scenario according to one or more aspects of the present disclosure is illustrated.

[0054] Figure 5 An example of a process flow for supporting feedback signaling in carrier aggregation and outer coding scenarios according to one or more aspects of the present disclosure is illustrated.

[0055] Figure 6 and Figure 7 A block diagram illustrating a device supporting carrier aggregation and feedback signaling in an outer coding scenario according to one or more aspects of the present disclosure is shown.

[0056] Figure 8 A block diagram illustrating a communication manager supporting carrier aggregation and feedback signaling in external coding scenarios according to one or more aspects of the present disclosure is illustrated.

[0057] Figure 9 A diagram illustrating a system including devices supporting carrier aggregation and feedback signaling in an outer coding scenario in accordance with one or more aspects of the present disclosure is illustrated.

[0058] Figure 10 and Figure 11 A block diagram illustrating a device supporting carrier aggregation and feedback signaling in an outer coding scenario according to one or more aspects of the present disclosure is shown.

[0059] Figure 12 A block diagram illustrating a communication manager supporting carrier aggregation and feedback signaling in external coding scenarios according to one or more aspects of the present disclosure is illustrated.

[0060] Figure 13 A diagram illustrating a system including devices supporting carrier aggregation and feedback signaling in an outer coding scenario in accordance with one or more aspects of the present disclosure is illustrated.

[0061] Figures 14 to 17 A flow chart illustrating a method for supporting feedback signaling in carrier aggregation and outer coding scenarios according to one or more aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0062] Some wireless communications, such as extended reality (XR) services, may rely on strict latency thresholds, high throughput, and specific reliability requirements. In such communications, wireless communication systems may support procedures to provide robust communication. One such action may include using Packet Data Convergence Protocol (PDCP) replication, which may include sending duplicate packets. Additional options for supporting robust communication may include outer decoding. In an outer decoding scenario, some redundancy in packet transmission is allowed, but a receiving device can successfully decode received transmissions even if fewer than all transmitted packets are received. Outer decoding can exploit link diversity and improve reliability, further enabling successful transmissions (e.g., video frame delivery) without relying on retransmission protocols. However, the user equipment (UE) may consume more power from repeated feedback signaling (e.g., despite the improved reliability of outer decoding). Feedback signaling may also unnecessarily utilize available system resources. Retransmission protocols may also increase system latency and reduce spectral efficiency.

[0063] The techniques described herein provide rules for deactivating the retransmission protocol when using outer coding (e.g., in multicast use cases), as well as rules for using an alternative feedback solution when retransmission has been deactivated. The techniques described herein can improve power savings and spectral efficiency by generally reducing feedback signaling overhead. A UE receiving outer coding downlink signaling can implement the new power saving rules by deactivating the retransmission protocol and then selecting at least one of two different feedback modes. The first feedback mode may include a radio link control (RLC) reporting mode (e.g., which may be referred to as Mode 1 or RLC Mode 1). The second feedback mode is a hybrid automatic repeat request (HARQ) feedback mode (e.g., which may be referred to as Mode 2 or HARQ Mode 2). A combination of the two modes may also be used. The network may configure the UE with parameters for operating in Mode 1, Mode 2, or both. In some examples, the network may indicate which mode the UE will use when the retransmission protocol is deactivated due to the use of outer coding. In some examples, the UE may select a feedback mode based on satisfying one or more conditions, including when retransmission is deactivated. Regardless of the feedback mode used, feedback signaling may result in an update to the outer coding used (eg, may not result in a retransmission).

[0064] Various aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to wireless communication systems, timelines, and process flows. Aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow charts related to feedback signaling in carrier aggregation and external decoding scenarios.

[0065] Figure 1 An example of a wireless communication system 100 supporting carrier aggregation and feedback signaling in an external coding scenario according to one or more aspects of the present disclosure is illustrated. 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 LTE-Advanced (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.

[0066] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UEs 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entities 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UEs 115 and the network entities 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entities 105 and the UEs 115 may support signal communication based on one or more radio access technologies (RATs).

[0067] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile or both stationary and mobile at different times. The UEs 115 may be devices that take different forms or have different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 In some examples, a UE may be an example of a device.

[0068] As described herein, a node of wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be UE 115. As another example, the node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a 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 relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from the second node.

[0069] In some examples, network entities 105 can communicate with core network 130, with each other, or both. For example, network entities 105 can 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 can communicate with each other via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols), either directly (e.g., between network entities 105) or indirectly (e.g., via core network 130). In some examples, network entities 105 can communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol), or any combination thereof. Backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 can 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 may communicate with core network 130 via communication link 155 .

[0070] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a Home Node B, a Home evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., the base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) 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 the base station 140).

[0071] In some examples, the network entity 105 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed between 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, the network entity 105 can 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 (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit receive point (TRP). One or more components of the network entity 105 in the disaggregated RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the disaggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0072] The functional split between CU 160, DU 165, and RU 170 is flexible and can support different functions 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 functional split of the protocol stack can be employed between CU 160 and DU 165, such that CU 160 can support one or more layers of the protocol stack and DU 165 can 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)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as Layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., RLC layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between the CU 160 and the DU 165 or between the DU 165 and the RU 170 can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, DU 165, or RU 170). The CU 160 can be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU 160 can be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and the DU 165 can be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented according to interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 communicating via such communication links.

[0073] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources used for radio access may 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 nodes 104) may be partially controlled by one another. One or more IAB nodes 104 may be referred to as a donor entity or IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a 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 nodes 104) via supported access and backhaul links (e.g., backhaul communication link 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by the coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the 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 disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of the IAB node 104) may be configured to operate according to the techniques described herein.

[0074] For example, an access network (AN) or RAN may include communications 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, the IAB donor may refer to a RAN node with 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), where 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 the F1 interface according to a protocol that defines 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 an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with an alternative IAB donor) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0075] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capabilities, etc.). A DU 165 may act as a distributed scheduling node toward child nodes associated with the IAB node 104, and an IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. In other words, an IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay transmissions for UEs via one or more other IAB nodes 104). Additionally or alternatively, depending on the relay chain or configuration of the AN, an IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Thus, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104 , and a DU interface (eg, DU 165 ) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115 .

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

[0077] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support feedback signaling in carrier aggregation and external coding scenarios as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

[0078] UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances or vehicles, meters, etc.

[0079] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which 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 shown.

[0080] UE 115 and network entity 105 may 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" may refer to a collection of RF spectrum resources having a physical layer structure that defines the communication link 125. For example, a carrier used for communication link 125 may comprise a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) operating in accordance with 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 for coordinating carrier operation, user data, or other signaling. The wireless communication system 100 may support communications 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 may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between those devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of the network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of the RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0081] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates 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 raster used for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

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

[0083] A carrier may be associated with a particular bandwidth of RF spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4 megahertz (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., the network entity 105, the UE 115, or both) may have a hardware configuration that supports communication using a particular carrier bandwidth, or may be configurable to support communication using one of the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or a 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., a subband, a BWP) or all of the carrier bandwidth.

[0084] The signal waveform transmitted via a carrier wave may include multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In systems employing MCM techniques, a resource element may refer to the 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 coding 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-order modulation scheme may correspond to relatively high-speed communication. Wireless communication resources may refer to a combination of RF spectrum resources, time 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 communications with UE 115.

[0085] One or more parameter sets for a carrier may be supported, and the parameter set may include subcarrier spacing ( ) and cyclic prefix. A carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communications by UE 115 can be constrained to one or more active BWPs.

[0086] The time interval for the network entity 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, a sampling period. Seconds, for this can indicate the supported subcarrier spacing, and The supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0087] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a certain 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 certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended to the front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-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 may depend on the subcarrier spacing or the operating frequency band.

[0088] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a Transmit Time Interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0089] Physical channels may be multiplexed using carriers for communication according to various techniques. Physical control channels and physical data channels may be multiplexed for signaling via downlink carriers, for example, using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of a carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the number 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 sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0090] 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 between adjacent cells (e.g., a physical cell identifier (PCID), a 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) within which the logical communication entity operates. Depending on various factors, such as the capabilities of network entity 105, 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 a building, a subset of buildings, or an external space between or overlapping coverage areas 110.

[0091] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. Compared to a macro cell, a small cell may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140), and the small cell may operate using the same or different frequency bands as the macro cell (e.g., licensed, unlicensed). A small cell may provide unrestricted access to UEs 115 that have a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells and may also use one or more component carriers to support communications via the one or more cells.

[0092] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

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

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

[0095] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with each other or with a network entity 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 this information to a central server or application, which uses the information or presents it to a human interacting with the application. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other equipment. 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.

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

[0097] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). The UE 115 may be designed to support ultra-reliable or low-latency or critical functionality. 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 functionality may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

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

[0099] In some systems, 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-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. Vehicles may signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, 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 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.

[0100] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130, which may be an evolved packet core (EPC) or a 5G core (5GC), may include at least one control plane entity (e.g., a mobility management entity (MME), an 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), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management, for UEs 115 served by network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be delivered through the user plane entities, which may provide IP address allocation and other functions. The user plane entities may connect to one or more network operators' IP services 150. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0101] The wireless communication system 100 can operate using one or more frequency bands that can range from 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features (which can be referred to as clusters), but these waves can penetrate structures sufficiently for a macrocell to provide service to UEs 115 located indoors. Communication using UHF waves can be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) compared to communication using the smaller frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0102] The wireless communication system 100 may also operate using the super high frequency (SHF) region (also known as the centimeter band), which may be in the range of 3 GHz to 30 GHz, or the extremely high frequency (EHF) region of the spectrum (e.g., 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such technology may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by greater attenuation and a shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory agency.

[0103] The wireless communication system 100 can utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communication system 100 can employ license-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology using unlicensed bands, such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating using unlicensed RF spectrum bands, devices such as the network entity 105 and the UE 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations using the unlicensed bands can be based on a carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations using the unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0104] A 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) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations 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, antennas or antenna arrays associated with the network entity 105 may be located at different geographic locations. The network entity 105 may include an antenna array having a set of multiple rows and columns of antenna ports that the network entity 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panels may support RF beamforming for signals transmitted via the antenna ports.

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

[0106] Beamforming (which may also be referred to 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 steer 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 communicated via antenna elements of an antenna array so that some signals propagating along a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals communicated via the antenna elements can include the transmitting or receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements can be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other direction).

[0107] The network entity 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the 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 the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the network entity 105 along different directions. For example, the network entity 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as the network entity 105) or by a receiving device (such as the UE 115)) the beam direction for later transmission or reception by the network entity 105.

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

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

[0110] 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 receiving 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 received signals according to different antenna subarrays, receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array (e.g., different sets of directional listening weights), or processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array, any of which 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 receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive 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).

[0111] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly for communication via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer may provide for the establishment, configuration, and maintenance of RRC connections between the UE 115 and the network entity 105 or the core network 130 for radio bearers supporting user plane data. The PHY layer may map transport channels to physical channels.

[0112] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of successful data reception. HARQ feedback is a technique used to increase the likelihood of correct data reception via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a 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, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a particular slot for data received via previous symbols in that slot. In other examples, the device may provide HARQ feedback in a subsequent slot or based on some other time interval.

[0113] The described techniques support deactivating the retransmission protocol when using outer coding (e.g., in multicast use cases), as well as using an alternative feedback solution when retransmission has been deactivated. A UE 115 may receive outer coding downlink signaling via carrier aggregation, deactivate the retransmission protocol, and then select at least one of two different feedback modes. The first feedback mode may include an RLC status reporting mode (e.g., which may be referred to as Mode 1 or RLC Mode 1). The second feedback mode is a HARQ feedback mode (e.g., which may be referred to as Mode 2 or HARQ Mode 2). A combination of the two modes may also be used. The network may configure the UE with parameters for operating in Mode 1, Mode 2, or both. In some examples, the network may indicate which mode the UE 115 will use when the retransmission protocol is deactivated due to the use of outer coding. In some examples, the UE may select a feedback mode based on satisfying one or more conditions, including when retransmission is deactivated. Regardless of the feedback mode used, the feedback signaling may result in an update to the outer coding used (e.g., may not result in retransmissions). The UE 115 may avoid sending additional feedback signaling and retransmissions may be disabled, thereby improving power conservation and more efficient use of system resources.

[0114] Figure 2 An example of a wireless communication system 200 that supports carrier aggregation and feedback signaling in an external decoding scenario according to one or more aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100 or may be implemented by aspects of the wireless communication system. For example, the wireless communication system 200 may include a network entity 105-a and a UE 115-a, which may be reference entities. Figure 1 Examples of corresponding devices described.

[0115] The network entity 105-a may send downlink signaling 210 to the UE 115-a. In some examples, the downlink signaling may be configured via control signaling 205. The UE 115-a may send a feedback message 215 indicating successful (e.g., or unsuccessful) reception of the downlink signaling 210. In some examples, the downlink signaling 210 may be an example of low-latency signaling, such as hyper-reality (XR) traffic, which may rely on strict latency constraints, high throughput, and critical reliability, as well as low UE power consumption. In some examples, the network entity 105-a may perform outer decoding 220 on the downlink signaling 210, which may include, for example, PDCP duplication to exploit link diversity and improve wireless signaling reliability and reduce latency (e.g., compared to using only HARQ retransmissions and RLC layer retransmissions).

[0116] Upper layer outer decoding 220 can support successful video frame delivery without relying on such a retransmission protocol. Therefore, outer coding can be considered an alternative to the retransmission protocol while improving latency reduction and power saving techniques (e.g., in a unicast context). Outer decoding can enhance upper layer dynamic adaptation by exploiting link diversity and can improve resource and spectrum efficiency. PDCP duplication may be limited by repeated decoding and 100% redundancy. Outer decoding 220 can involve incremental redundancy and more efficient transmission (e.g., service or channel-specific adaptation). PDCP duplication can be a simple case of outer decoding 220. In some cases, outer decoding 220 can be referred to as PDCP duplication or PDCP split outer decoding.

[0117] In some examples (e.g., instead of relying on external decoding), wireless communication systems may support feedback signaling, retransmission protocols, etc. to improve signaling reliability. However, the external decoding process can improve signaling reliability even when parts of a transmission are not received by the receiving device. Consequently, the transmitting and receiving devices may unnecessarily consume power, utilize system resources, and increase system latency by implementing retransmission protocols, excessive feedback signaling, etc. (e.g., despite the improved reliability of external decoding).

[0118] The network entity 105-a may support outer decoding 220, which may occur at the PDCP layer at a CU (e.g., of the network entity 105-a). For example, for transmission 225, the network entity 105-a may segment the PDCP (e.g., including the PDCP SDU 230 and header) into K source packets of equal size (e.g., uncoded subpackets 240). The decoding rate may be configured based on a worst-case or rateless code. In some examples, if a single DU (e.g., DU 165-a) is involved, no splitting may occur at the PDCP layer. If multiple DUs 165 are present (e.g., DU 165-a and DU 165-b), outer decoding may replace PDCP duplication, and different sets of outer decoded packets 250 may be split across multiple DU legs (e.g., via different component carriers). For example, the uncoded subpacket 240 may be encoded into N decoded packets 245 at the network decoding sublayer of the network entity 105-a. Decoded packet 245 may be outer-decoded into outer-decoded packet 250 at the RLC layer of network entity 105-a, and outer-decoded packet 250 may be included in one or more MAC protocol data units (PDUs) TB 265. A CU (e.g., managing PDCP PDU 235 and the outer decoding sublayer at the PDCP layer) may communicate with DU 165 (e.g., via the F1-U interface). CU 160-a may provide segments (e.g., outer-decoded packet 250) to DU 165. For example, after calculating TB 255, DU 165-a and DU 165-b may receive the segments encapsulated in RLC SDU 230, which may have a size fixed by the MAC layer. After encapsulating the header, DU 165 may obtain an RLC PDU of a size set by the MAC layer. The MAC layer may reassemble the required number of RLC PDUs and encapsulate the headers to construct MAC PDU TB 255. The MAP PDU may be split across multiple CCs (e.g., in CA mode). For example, DU 165-a may send a first set of outer coded segments via a first branch (e.g., a first set of one or more CCs), and DU 165-b may send a second set of outer coded segments via a second branch (e.g., a second set of one or more CCs).

[0119] UE 115-a may receive downlink signaling 210 (e.g., via DU 165-a, DU 165-b, or both) and may perform the techniques described herein to provide feedback message 215, thereby saving power and reducing signaling overhead. For example, RLC and HARQ retransmission protocols may be disabled, but UE 115-a may use feedback mechanisms for the RLC or HARQ protocols to convey feedback signaling. In some examples, PDCP in-sequence delivery may also be disabled. UE 115-a may use RLC-AM mode for RLC status reporting that is activated by forcing one or more timers (e.g., a t_Reassembly timer set to 0) or by ignoring one or more timers (e.g., by ignoring t-Reassembly and t_Prohibit, which may be names of timers associated with feedback signaling).

[0120] The techniques described herein include feedback reduction protocols for outer decoding (e.g., PDCP split outer decoding, etc.). Such techniques can be implemented, for example, in carrier aggregation use cases and can save power. The techniques can also eliminate other retransmission protocols (e.g., HARQ or RLC protocols).

[0121] The techniques described herein may improve power savings and spectral efficiency through feedback reduction. For example, outer decoding may involve generating redundancy on the transmitter side. In the context of carrier aggregation, some feedback reduction techniques may focus on acknowledgement (ACK) signaling over the primary component carrier. However, if all ACK signaling associated with HARQ feedback signaling is sent, such signaling may overload the use of control channels (e.g., PUCCH resources) and may affect the power consumption of the device (e.g., UE). The techniques described herein may reduce feedback by disabling at least some HARQ or RLC retransmissions and by limiting the pacing of ACK signaling (e.g., by alternating and combining HARQ ACK feedback with RLC status feedback signaling, as described herein), thereby reducing power consumption and resource consumption.

[0122] The techniques described herein can also improve power savings and spectral efficiency while reducing latency by disabling retransmission protocols. For example, in unicast use cases (e.g., without carrier aggregation or PDCP duplication), HARQ and RLC mechanisms, as well as associated feedback signaling (e.g., ACK signaling), consume high power. Furthermore, retransmission protocols can reduce reliability or otherwise be unable to support low-latency use cases (e.g., XR use cases). Therefore, by disabling retransmission protocols, transmitting and receiving devices can avoid retransmissions (e.g., when part of a message is lost but the receiving device has received enough of the externally decoded transmission to render a retransmission unnecessary), thereby improving power savings, spectral efficiency, and latency. The techniques described herein are also compatible with various device types and generations. For example, both new and legacy devices can support the protocols described herein and are compatible with DU / CU splitting and other evolutions and use cases (e.g., messages available via the F1-U interface). The techniques described herein can support frameworks in which external decoding operates at the device's DU (e.g., between the PDCP and RLC layers, etc.). In some examples, the DU may interoperate with the CU, and this interoperability may support discarding or exchanging information between the CU and DU outside of the F10U interface header.

[0123] As described herein, a receiving device (e.g., a UE) may disable feedback mechanisms (e.g., HARQ feedback and retransmission schemes), RLC mechanisms (e.g., RLC retransmission schemes), or both. For example, whenever outer coding is enabled (e.g., if one or more conditions are met, or if the network indicates to the UE that network coding is currently being used or will be used for pending downlink communications), the UE may disable retransmission protocols (e.g., RLC and HARQ protocols). The UE may maintain feedback signaling (e.g., HARQ feedback signaling, RLC status feedback signaling, or both) in accordance with one or more power-saving rules (e.g., in accordance with one or more feedback modes (e.g., RLC reporting mode 1 or HARQ reporting mode 2)). If the UE selects feedback mode 1 (e.g., RLC reporting mode 1), the UE may send RLC status reports as feedback signaling (e.g., but not HARQ feedback signaling). If the UE selects feedback mode 2 (e.g., HARQ reporting mode 2), the UE may send feedback signaling via HARQ ACK / NACK feedback signaling. In some examples, mode 1 may be associated with a higher periodicity, while mode 2 may be used with a lower periodicity (e.g., to support mechanisms such as a HARQ block error report (BLER) control loop with a network entity, or detection of lost PDCCH signaling). For example, a UE may send feedback signaling via a configured RLC status report message at a high periodicity, and may occasionally (e.g., at a lower periodicity than the RLC status report signaling) send HARQ feedback messages to support BLER signaling or to indicate lost PDCCH signaling.

[0124] When operating according to Mode 1, the UE may send RLC status feedback upon detecting a lost RLC PDU (e.g., rather than relying on the HARQ protocol to send feedback). In such examples, the UE may adjust or override one or more timers (e.g., or other parameters) to ensure prompt transmission of the RLC report. For example, the UE may force a first timer associated with transmitting the RLC PDU (e.g., a timer defined by a parameter such as t_Reassembly) to zero, or may use a timer (e.g., associated with a parameter such as StatusProhibit) to adjust the RLC status load. Alternatively, in some examples, the UE may simply override two timers.

[0125] In some examples, the UE may send both ACK / NACK signaling and RLC status feedback signaling. Alternatively, the UE may use both ACK / NACK signaling and RLC status feedback signaling by sending feedback signaling via a primary cell or primary carrier component for each DU (e.g., for each cell group in a set of cell groups). Such signaling may be implemented by relying on standardized algorithms. RLC status feedback signaling may be activated more frequently than HARQ feedback signaling (e.g., RLC status feedback signaling may have a smaller periodicity and, therefore, may occur more frequently than HARQ feedback signaling).

[0126] A UE (e.g., or any receiving device) may send feedback signaling based on a HARQ codebook (e.g., a Type 1 codebook or a Type 2 codebook). In some examples, feedback signaling may be simplified. For example, if the time window, codebook size, or both allow for the complete elimination of HARQ Ack / NACK signaling, a UE operating in Mode 1 may send an RLC status report (e.g., instead of a NACK message). In such an example, the UE may send an RLC status report and avoid sending any HARQ feedback signaling (e.g., all feedback signaling is conveyed via RLC status report signaling). In some examples, when the UE operates in Mode 2, the UE may support a nominal feedback protocol for HARQ feedback signaling. The UE may employ either Mode 1 or Mode 2, may alternate between Mode 1 and Mode 2, or may operate in a combination of Mode 1 and Mode 2.

[0127] In some examples, the UE may stop sending any feedback signaling after successfully receiving a sufficient number of external decoding messages (e.g., when the UE has received a sufficient number of segments of the external decoding transmission such that additional signaling and retransmissions are not required). For example, the UE may refrain from sending any feedback signaling after the last PDSCH (e.g., monitored by a network entity) or after successful decoding (e.g., as detected by the network entity after processing feedback reported by the UE). Accordingly, the UE may enter sleep (e.g., enter idle mode or sleep mode) upon the last PDSCH or after successfully decoding the transmission or after sending a feedback message indicating successful reception or decoding of the transmission (e.g., in mode 1 or mode 2). In some examples, carrier aggregation functionality, external decoding mode, or both may be deactivated upon successful decoding or after the last PDSCH associated with the received transmission.

[0128] At the RLC layer of the transmitting device (e.g., at the network entity), the transmitting device may receive feedback signaling (e.g., on the primary component carrier) and may count the number of received RLC PDU packets (e.g., at the receiving device such as a UE, as indicated in the feedback signaling). For example, an initial transmission may include two legs (e.g., two parts or segments). The receiving device may send three RLC status reports (e.g., on the primary cell). Each transport block (TB) may include multiple RLC PDUs (e.g., N). Feedback from the receiving device (e.g., the UE) may indicate that multiple RLC PDUs have been successfully received (e.g., such that was successfully received).

[0129] Similarly, for a transmission with two legs and a receiving device sending one ACK and one NACK message on the primary cell, where each TB includes N RLC PDUs, the feedback from the receiving device may indicate to the transmitter that N RLC PDUs have been successfully received. If a plurality of received RLC PDU packets include a plurality of decoded segments, the number of decoded segments meeting (e.g., greater than or equal to) a threshold number of RLC PDU packets for decoding the source segments and reassembling the PDCP PDU (e.g., ), one or more actions may be triggered. For example, the network entity may deactivate carrier aggregation and outer coding (e.g., PDCP split outer coding), and may stop sending the remaining packets of the downlink sequence. In some examples, if there is no other ongoing traffic, mode 1, mode 2, or both may be deactivated. In some examples, if there is no other ongoing traffic, the network entity may request the UE to enter sleep mode (e.g., may send a message indicating that the UE is to enter sleep mode). Threshold (e.g., ) may depend on the outer coding design and may be determined based on other upper layer metrics (e.g., radio conditions, Quality of Service (QoS), Quality of Experience (QOE), etc.). For example, for some outer codings (e.g., for MDS coding), Can be equal to the decoding dimension.

[0130] In some examples, the techniques described herein may be combined or interact with one or more additional protocols. For example, based on an indication (e.g., a "go to sleep" field or indication in a downlink control information (DCI) message), a network entity and a UE may deactivate HARQ and RLC retransmissions, or the UE may enter sleep mode.

[0131] Feedback signaling according to Mode 1, Mode 2, or both can improve power consumption and reduce latency. For example, as described herein, a UE can operate according to a traffic reduction protocol with a HARQ-free protocol (e.g., an RLC status report conveying feedback information can be sent without using HARQ signaling). The UE and the network entity can disable HARQ and RLC retransmission protocols, and the decoding rate can be established based on a worst-case scenario. If decoding is detected as successful (e.g., by the base station based on processing feedback), the transmitting device can be triggered to stop downlink transmission, thereby reducing latency, and can be triggered to disable carrier aggregation functionality, outer decoding transmission, or both earlier than if such feedback had not been processed. If the transmission fails in delivery (e.g., as indicated by feedback), the network entity can introduce increased redundancy by triggering a rateless feature in the outer coding by the network entity.

[0132] If the UE supports the reduced feedback protocol in the uplink, it can use reduced feedback by alternating RLC status reports with HARQ feedback signaling in the feedback mechanism for carrier aggregation scenarios. RLC feedback can occur more frequently than HARQ feedback signaling. Reduced feedback can achieve more efficient utilization of PUCCH resources. Feedback can be aggregated across all component carriers of a cell group and transmitted on the primary cell of a cell group associated with a specific DU. Reduced feedback, resulting in reduced traffic, can enable the UE to enter sleep mode when decoding is detected as successful (e.g., by a network entity based on received feedback signaling).

[0133] In some examples, the UE may provide feedback signaling based on a periodicity, where RLC status feedback is used more frequently than HARQ feedback. ACK / NACK signaling may be used to implement other system mechanisms (e.g., in addition to actually sending feedback corresponding to received downlink data signaling), such as a HARQ BLER control loop with a network entity, or detection of control signaling (e.g., an indication of missed PDCCH signaling). In some examples, ACK / NACK feedback may be configured (e.g., by a network entity) as optional. RLC status feedback signaling may be sufficient for the transmitter to determine how many segments the receiving device (e.g., UE) has correctly received. In some examples, the optimal periodicity (e.g., for sending RLC and HARQ feedback by the UE) may be determined heuristically (e.g., through simulations), may be defined by one or more standards, may be selected or indicated by a network entity, or may be selected by the UE. Such periodicity may improve power and resource conservation. In some examples, the UE may send feedback signaling according to an aperiodic pattern (eg, triggered by control signaling such as DCI signaling, rather than according to a configured or selected periodicity).

[0134] Figure 3An example of a timeline 300 for supporting feedback signaling in a carrier aggregation and external coding scenario according to one or more aspects of the present disclosure is illustrated. The timeline 300 may implement aspects of the wireless communication system 100 and the wireless communication system 200, or may be implemented by aspects of these wireless communication systems. For example, a transmitting device (e.g., a network entity) and a receiving device (e.g., a UE) (which may be a reference Figure 1 and Figure 2 Examples of corresponding devices described herein) can communicate with each other according to the communication timeline 300.

[0135] A sending device (eg, a network entity) may generate a source segment 305 having a number of source segments 305 (eg, source segments, where ) downlink transmission. This transmission may include a total of (For example, where ), including five source segments 305 and three parity segments 310. The network entity may perform outer decoding on the source segments 305 and may generate one or more RLC PDUs 315, one or more MAC PDU TBs 330, or a combination thereof. Each RLC PDU 315 may include a header 325 and two decoded segments (e.g., within one or more RLC SDUs 320). For example, a first RLC PDU 315-a may include two source decoded segments 305 (e.g., within one or more RLC SDUs 320-a), another RLC PDU 315-b may include two source decoded segments 305 (e.g., within one or more RLC SDUs 320-b), and so on. Another RLC PDU 315-c may include a parity segment 310 (e.g., within one or more RLC SDUs 320-c). Each MAC PDU 330 may include four coded segments (e.g., source segments 305, parity segments 310, or both) and one or more headers 325. For example, a first MAC PDU TB 330-a carried via a first CC (e.g., CC1) may include four source segments 305 (e.g., two source segments in a first MAC SDU 340-a and two source segments in a second MAC SDU 340-b), and a second MAC PDU TB 330-b carried via a second CC (e.g., CC2) may include four segments (e.g., one source segment 305 and three parity segments 310 carried via one or more MAC SDUs 340).

[0136] On the receiver side, a single ACK message may indicate that four decoded segments were received on one TB (e.g., may indicate that four decoded segments of MAC PDU TB 330-a were received). An RLC status report message may indicate that two decoded segments were not received on the indicated TB. Thus, the indication that two decoded segments of a given TB were not received indicates that two decoded segments were implicitly received. Thus, if the UE is operating in Mode 2, and if the UE sends feedback including an ACK message on one leg of the transmission and a NACK message associated with the other leg (e.g., the ACK message corresponds to MAC PDU TB 330-a and the NACK message corresponds to MAC PDU TB 330-b), the feedback signaling may indicate that the UE received four decoded segments but was unable to recover the source packet (e.g., because 5 decoded segments). If the UE sends feedback via RLC status reports (e.g., in Mode 1), the UE may send feedback in one RLC status report per leg. For example, the UE may indicate that it has received six decoded segments (e.g., may indicate that only two of the eight segments were not received, or may not indicate that any of RLC PDU 315-a, RLC PDU 315-b, and RLC PDU 315-c, each of which corresponds to two decoded segments, were not received). In such examples, the RLC status report message may indicate that the UE is able to recover the source packet (e.g., because the six received decoded segments meet the requirements). ).

[0137] The techniques described herein may be performed by any transmitting device and receiving device. For example, the transmitting device described herein may be a UE, and the receiving device may be a network entity. In some examples, such as reference Figure 5 Described in more detail, the UE may enter the sleep mode upon successfully receiving downlink signaling.

[0138] Figure 4 An example of a timeline 400 for feedback signaling in a scenario supporting carrier aggregation and external decoding according to one or more aspects of the present disclosure is illustrated. The timeline 400 may implement aspects of the wireless communication system 100 and the wireless communication system 200, or may be implemented by aspects of these wireless communication systems. For example, a transmitting device (e.g., a network entity) and a receiving device (e.g., a UE) (which may be a reference Figure 1 and Figure 2 Examples of corresponding devices described herein) can communicate with each other according to communication timeline 400.

[0139] Network entities and UEs may communicate according to a frame structure that may define uplink (U), downlink (D), and special (S) or flexible durations (e.g., time slots or symbols). For example, the frame structure may define a pattern of U, D, and S time slots, such as DDDSU (e.g., three downlink time slots, followed by a special time slot, followed by an uplink time slot). The frame structure may include a repeating pattern (e.g., DDDSU, DDDSU).

[0140] During the downlink time slot, the network entity may send a downlink transmission 405 (eg, as described with reference to Figure 2 and Figure 3 The network entity may send a downlink transmission 405-a via a first branch of transmission (branch 1) and a downlink transmission 405-b via a second branch of transmission (branch 2) (e.g., via CC1 and CC2, as described in reference to FIG. Figure 2 and Figure 3 ). During special time slots and uplink time slots, according to the frame structure, the UE may be configured to send feedback messages 410 (e.g., RLC status reports according to mode 1, HARQ feedback messages according to mode 2). Feedback message 410-a (e.g., sent via a special time slot) may indicate that the UE has received sufficient decoding segments to decode the downlink message via downlink transmission 405-a and downlink transmission 405-b. For example, the feedback information may confirm confirmed receipt of at least six downlink segments (e.g., frames, TBs, MAC PDUs, etc. in the case of one TB per user per downlink time slot). The UE may send feedback message 410-a via PUCCH branch 1 (e.g., via the primary cell or primary carrier for a given DU). Feedback on PUCCH branch 1 may indicate feedback information for downlink transmission 405 via both PDSCH branch 1 and PDSCH branch 2.

[0141] If feedback message 410-a indicates that the UE has received enough decoded segments to recover the source segments of the downlink message, the UE may enter a sleep mode (e.g., a light sleep mode, a deep sleep mode, etc.). In such an example (e.g., based on feedback message 410-a), the UE may enter sleep mode (e.g., prior to an uplink timeslot in which the UE may have otherwise sent additional feedback message 410-b). The UE may refrain from sending additional feedback message 410-b, feedback message 410-c, and feedback message 410-d (e.g., while in sleep mode after sending feedback message 410-a). The UE and the network entity may also deactivate a retransmission protocol. For example, the network entity may have configured the UE to receive a retransmission 415 of the downlink message in a subsequent downlink timeslot. However, based on receiving feedback message 410-a indicating that enough segments were successfully received to decode the source segments, the network entity may avoid sending retransmission 415-a (e.g., of downlink transmission 405-a) via PDSCH branch 1 and sending retransmission 415-b (e.g., of downlink transmission 405-b) via PDSCH branch 2. Avoiding sending additional (e.g., and unnecessary) feedback messages 410 and unnecessary retransmissions 415 may increase power conservation for the UE, improve system efficiency, reduce signaling overhead, improve throughput (e.g., where resources used for feedback messages 410 and retransmissions 415 may be reused for additional communications), reduce system latency, and improve user experience.

[0142] The techniques described herein may be performed by any transmitting device and receiving device. For example, the transmitting device described herein may be a UE, and the receiving device may be a network entity.

[0143] Figure 5 An example of a process flow 500 for supporting feedback signaling in a carrier aggregation and external coding scenario according to one or more aspects of the present disclosure is illustrated. The process flow 500 may implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, and the timelines 300 and 400. For example, a transmitting device (e.g., network entity 105-b) and a receiving device (e.g., UE 115-b) (which may be reference Figures 1 to 45. In some examples, although illustrated with reference to network entity 105-b and UE 115-b, any device may communicate according to process flow 500. For example, the transmitting device may be network entity 105 (e.g., other than UE 115-b), and the receiving device may be another network entity 105 or UE 115, or any other wireless device (e.g., a CU, DU, RU, IAB node, etc.). The techniques described herein may be triggered by the presence of low-latency traffic (e.g., which may be enabled or triggered by low-latency traffic such as Ultra Reliable Low Latency Communication (URLLC), XR traffic, etc.), carrier aggregation with an external decoding transmission scheme, or any combination thereof. External decoding with a coding rate designed for worst-case link scenarios or rateless decoding with a limited coding rate may be used (e.g., the decoding operation may be applied to segments of a PDCP PDU).

[0144] At 515, UE 115-b may receive one or more downlink messages (e.g., from network entity 105-b) via carrier aggregation according to an external decoding transmission scheme. The external decoding transmission scheme may be any external decoding scheme that distributes redundancy across different legs of a transmission (e.g., via different packets, different frequencies (e.g., different CCs), etc.). Distributed redundancy may include, for example, duplication. For example, the external decoding transmission scheme may be an example of a PDCP distributed external decoding scheme, such as a PDCP split external decoding scheme.

[0145] At 520, UE 115-b may deactivate a retransmission protocol associated with the one or more downlink messages based on the outer coding transmission scheme being applied to the one or more downlink messages.The network may deactivate RLC retransmissions when carrier aggregation, the outer coding transmission scheme, or both are activated.

[0146] At 525, UE 115-b may select at least one of a first feedback mode (e.g., Mode 1) associated with a first set of RLC reports and resources (e.g., for transmitting RLC status reports) and a second feedback mode (e.g., Mode 2) associated with a second set of HARQ reports and resources (e.g., for transmitting HARQ signaling). UE 115-b may select the first feedback mode or the second feedback mode as explicitly indicated by network entity 105-b (e.g., via control signaling indicating Mode 1 or Mode 2 at 505) or based on satisfying one or more conditions. The one or more conditions may include a power state at the UE, a threshold latency corresponding to the one or more downlink messages, or a combination thereof. These conditions may be configured by network entity 105-b (e.g., at 505) or may be defined in one or more standards. Mode 1 may be referred to as RLC reporting Mode 1. UE 115-b operating in Mode 1 may report RLC status feedback to replace NACK signaling for performing CA aggregation of feedback for all component carriers on the primary carrier. Mode 2 may be referred to as HARQ reporting mode 2. A UE 115-b operating in mode 2 may send HARQ feedback based on CA aggregation of all HARQ feedback for all carriers on the primary carrier. The periodicity of RLC reporting may be higher than in the HARQ reporting mode, and this periodicity may be set heuristically.

[0147] In some examples, UE 115-b may select a combination of a first feedback mode and a second feedback mode. The first feedback mode may correspond to a first periodicity, and the second feedback mode may correspond to a second periodicity. The first periodicity may be greater than the second periodicity. In some examples, UE 115-b may send feedback via RLC status reports more frequently (e.g., according to the first periodicity) than it sends HARQ signaling. In some examples, UE 115-b may send HARQ signaling more frequently (e.g., with a different periodicity) than it sends RLC status reports.

[0148] At 530, UE 115-b may send a feedback message corresponding to the one or more downlink messages (e.g., indicating a number of decoded segments received by UE 115-b) via a first set of resources (e.g., an RLC status report) or a second set of resources (e.g., a HARQ feedback message) in accordance with the selected feedback mode. In some examples, UE 115-b may send the feedback message via the first set of resources according to a first periodicity at 530. UE 115-b may also send a second feedback message via the second set of resources according to a second periodicity at 535. UE 115-b may count the number of received RLC PDUs based on a processing rule in accordance with the techniques described herein (e.g., and may indicate via the feedback message that a sufficient number of RLC PDUs satisfies a threshold and that UE 115-b has sufficient segments to decode the downlink message). As described herein, upon determining that a plurality of received RLC PDU packets include a plurality of decoded segments (the number of decoded segments being greater than a specified or threshold number), UE 115-b may take one or more actions. Such actions may include deactivating CA and outer decoding transmission schemes. If there is no additional, simultaneous, or pending traffic, UE 115-b may interrupt transmission of the remaining segments of the associated downlink sequence, deactivate all types of RLC and HARQ reporting, and enter sleep mode.

[0149] In some examples, UE 115-b may alternate between sending feedback signaling (e.g., a first feedback message at 530) via corresponding resources associated with a first set of resources according to a first periodicity and sending feedback signaling (e.g., a second feedback message at 535) via corresponding resources associated with a second set of resources according to a second periodicity. UE 115-b may alternate between periodic use of ACK / NACK HARQ signaling and NACK RLC status reporting in carrier aggregation and may aggregate feedback for all members sent on a primary CC (e.g., or any designated CC). The periodicity of the RLC status may be higher than the periodicity of the HARQ feedback. In some examples, the periodicity of the RLC status report may be lower than the periodicity of the HARQ feedback. In some examples, at 510, the UE may receive an indication of the periodicity.

[0150] In some examples, network entity 105-b may configure UE 115-b with one or more parameters for operating in Mode 1 or Mode 2. For example, at 505, UE 115-b may receive (e.g., from network entity 105-b) control signaling indicating one or more parameters to be used for a first feedback mode, a second feedback mode, or both. In such examples, UE 115-b may select a feedback mode 525 based on or in accordance with the indicated parameters. The parameters may include one or more rules for employing Mode 1 or Mode 2, one or more conditions under which UE 115-b will employ Mode 1 or Mode 2, a periodicity for sending feedback messages (e.g., at 530 and 535) according to Mode 1, Mode 2, or both, or any combination thereof.

[0151] In some examples, UE 115-b may activate a first resource in the second set of resources according to a second periodicity and may send a BLER message, an indication of a lost PUCCH channel, or a combination thereof via the activated first resource in the second set of resources. For example, UE 115-a may activate fast NACK RLC status feedback signaling, ignore one or more timers (e.g., t_Reassembly and t_StatusProhibit), or allow the timers to expire while following feedback signaling techniques in Mode 1 or Mode 2. In some examples, some HARQ feedback messages or resources may be periodically activated and may support a BLER control loop, detection of lost PUCCH, etc.

[0152] In some examples, sending the feedback message at 530 may include sending an RLC status report via a first set of resources according to a first feedback mode based on detecting the lost RLC PDU. UE 115-b may deactivate a HARQ protocol associated with the second feedback mode based on the selection at 525. UE 115-a may allow one or more timers to expire or may set one or more timers to zero based on selecting the first feedback mode, where the timers are associated with the RLC status report. UE 115-b may include in the RLC status report an indication of a number of segments associated with the outer decoding transmission scheme that have been successfully received by UE 115-b (e.g., or may indicate segments that were not received, thereby implicitly indicating segments that were successfully received).

[0153] In some examples, UE 115-b may send multiple feedback messages (e.g., at 530 and at 535) via a first set of resources via a primary CC of a first cell group and via a second set of resources of a primary CC of the first cell group. In some examples, the feedback messages may be generated according to a HARQ codebook (e.g., type 1 or type 2). The methods and techniques described herein may be applied to multiple cell groups via multiple DUs. The techniques described herein may be applied independently to each cell group.

[0154] In some examples, upon sending the feedback message at 530, UE 115-b may enter sleep mode based on sending the feedback message and may deactivate carrier aggregation, the outer decoding transmission scheme, or both based on having entered sleep mode. Network entity 105-b may similarly deactivate carrier aggregation mode and the outer decoding transmission scheme based on receiving the feedback message at 530 or upon sending the last of the downlink messages at 515. UE 115-b may refrain from sending one or more additional feedback messages (e.g., at 535) via at least a portion of the first set of resources and the second set of resources associated with retransmitting the one or more downlink messages based on entering sleep mode. In some cases, UE 115-b may receive an indication from the network entity that no additional downlink messages are pending based on having sent the feedback message at 530, and UE 115-a may enter sleep mode based on receiving the indication. In some cases, UE 115-b may receive an indication of a threshold number of segments (e.g., K) associated with the outer decoding transmission scheme from network entity 105-b and may enter sleep mode based on determining that the number of decoded segments in the downlink message meets the threshold number of segments indicated by network entity 105-b. In some examples, the threshold number of segments may be defined in one or more criteria.

[0155] The network entity 105-b may refrain from sending one or more retransmissions or one or more additional scheduled segments of the downlink message based on a determination that the UE 115-b has received a sufficient (e.g., a threshold) number of segments to decode the downlink message. In some cases, the network entity 105-b may determine that this is the case based on receiving the feedback message at 530 or based on sending the last PDSCH message at 515. In some cases, the network entity 105-b may, based on this determination, send an indication that the pending transmission will not be transmitted.

[0156] In some examples, network entity 105-b may send, and UE 115-b may receive, control signaling (e.g., at 505) that triggers aperiodic feedback signaling via the first set of resources, the second set of resources, or both. UE 115-b may periodically send feedback signaling based on the control signaling at 530. In some cases, a dynamic trigger may indicate a feedback mode, and UE 115-b may select a feedback mode based thereon at 525. In some examples, the dynamic trigger may indicate an instruction to enter sleep mode, and UE 115-b may do so after sending the feedback message based on the control signaling.

[0157] Figure 6 A block diagram 600 illustrates a device 605 that supports feedback signaling in carrier aggregation and external coding scenarios according to one or more aspects of the present disclosure. The device 605 may be an example of aspects of the UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0158] Receiver 610 may provide means 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 related to feedback signaling in carrier aggregation and external coding scenarios). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0159] Transmitter 615 may provide means 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 related to feedback signaling in carrier aggregation and external coding scenarios). 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.

[0160] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of feedback signaling in carrier aggregation and external coding scenarios as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

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

[0162] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor (e.g., configured as or otherwise supporting means for performing the functions described herein), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0163] In some examples, communication manager 620 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 610, transmitter 615, or both. For example, communication manager 620 can receive information from receiver 610, transmit information to transmitter 615, or otherwise integrate with receiver 610, transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0164] According to examples disclosed herein, the communication manager 620 may support wireless communications at a UE. For example, the communication manager 620 may be configured to receive one or more downlink messages from a network entity via carrier aggregation according to an external coding transmission scheme. The communication manager 620 may be configured to deactivate a retransmission protocol associated with the one or more downlink messages based on the application of the external coding transmission scheme to the one or more downlink messages. The communication manager 620 may be configured to select at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on the application of the external coding transmission scheme to the one or more downlink messages. The communication manager 620 may be configured to transmit a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0165] By including or configuring the communication manager 620 according to examples as described herein, the device 605 (e.g., a processor controlling the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof or otherwise coupled thereto) can support techniques for feedback signaling in external decoding scenarios, thereby improving power conservation, increasing system efficiency, reducing signaling overhead, improving throughput, reducing system latency, and improving user experience.

[0166] Figure 7 A block diagram 700 illustrates a device 705 that supports feedback signaling in carrier aggregation and external coding scenarios according to one or more aspects of the present disclosure. The device 705 may be an example of aspects of the device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0167] Receiver 710 may provide means 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 related to feedback signaling in carrier aggregation and external coding scenarios). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0168] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the 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 related to feedback signaling in carrier aggregation and external coding scenarios). In some examples, the transmitter 715 may be co-located with the receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0169] Device 705 or its various components may be examples of means for performing various aspects of feedback signaling in carrier aggregation and external coding scenarios as described herein. For example, communications manager 720 may include downlink message component 725, deactivation component 730, feedback mode selection component 735, feedback message component 740, or any combination thereof. Communications manager 720 may be an example of aspects of communications manager 620 as described herein. In some examples, communications manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 710, transmitter 715, or both. For example, communications manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in conjunction with receiver 710, transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.

[0170] According to examples disclosed herein, a communication manager 720 can support wireless communications at a UE. A downlink message component 725 can be configured to, or otherwise support, receive one or more downlink messages from a network entity via carrier aggregation according to an external coding transmission scheme. A deactivation component 730 can be configured to, or otherwise support, deactivate a retransmission protocol associated with the one or more downlink messages based on the external coding transmission scheme being applied to the one or more downlink messages. A feedback mode selection component 735 can be configured to, or otherwise support, select at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on the external coding transmission scheme being applied to the one or more downlink messages. A feedback message component 740 can be configured to, or otherwise support, transmit a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0171] Figure 8Block diagram 800 illustrates a communication manager 820 supporting feedback signaling in carrier aggregation and external coding scenarios, according to one or more aspects of the present disclosure. Communication manager 820 may be an example of communication manager 620, communication manager 720, or aspects of both, as described herein. Communication manager 820 or its various components may be examples of means for performing various aspects of feedback signaling in carrier aggregation and external coding scenarios, as described herein. For example, communication manager 820 may include a downlink message component 825, a deactivation component 830, a feedback mode selection component 835, a feedback message component 840, a control signaling component 845, a sleep mode component 850, a periodicity component 855, a timer component 860, a threshold indication component 865, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0172] According to examples disclosed herein, a communication manager 820 can support wireless communications at a UE. A downlink message component 825 can be configured to, or otherwise support, receive one or more downlink messages from a network entity via carrier aggregation according to an external coding transmission scheme. A deactivation component 830 can be configured to, or otherwise support, deactivate a retransmission protocol associated with the one or more downlink messages based on the external coding transmission scheme being applied to the one or more downlink messages. A feedback mode selection component 835 can be configured to, or otherwise support, select at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on the external coding transmission scheme being applied to the one or more downlink messages. A feedback message component 840 can be configured to, or otherwise support, transmit a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0173] In some examples, the control signaling component 845 may be configured as or otherwise support means for receiving control signaling from the network entity indicating one or more parameters for using the first feedback mode, the second feedback mode, or both, wherein the selection is based on the one or more parameters.

[0174] In some examples, the feedback mode selection component 835 may be configured as or otherwise support a component for selecting at least one of the first feedback mode or the second feedback mode based on satisfying one or more conditions, wherein the one or more conditions are associated with a power state at the UE, a threshold latency corresponding to the one or more downlink messages, or a combination thereof.

[0175] In some examples, to support selection, the feedback mode selection component 835 may be configured as or otherwise support a component for selecting a combination of the first feedback mode and the second feedback mode, wherein the first feedback mode corresponds to a first periodicity and the second feedback mode corresponds to a second periodicity, wherein the first periodicity is greater than the second periodicity.

[0176] In some examples, to support sending the feedback message, feedback message component 840 can be configured as or otherwise support means for sending the first feedback message via the first set of resources according to the first periodicity. In some examples, to support sending the feedback message, feedback message component 840 can be configured as or otherwise support means for sending the second feedback message via the second set of resources according to the second periodicity.

[0177] In some examples, to support sending the feedback message, feedback message component 840 can be configured as or otherwise support means for activating a first resource in the second set of resources according to the second periodicity. In some examples, to support sending the feedback message, feedback message component 840 can be configured as or otherwise support means for sending a block error report, an indication of a lost message via a physical downlink control channel, or a combination thereof via the activated first resource in the second set of resources.

[0178] In some examples, to support sending the first feedback message and the second feedback message, the feedback message component 840 may be configured as or otherwise support a component for alternating between sending according to the first periodicity via the corresponding resources associated with the first set of resources and sending according to the second periodicity via the corresponding resources associated with the second set of resources.

[0179] In some examples, to support sending the feedback message, the feedback message component 840 may be configured as or otherwise support a component for sending an RLC status report via the first set of resources according to the first feedback mode based on detecting lost RLC packet data units, wherein the HARQ protocol associated with the second feedback mode is disabled according to the selection.

[0180] In some examples, the timer component 860 can be configured as or otherwise support a component for allowing one or more timers to expire or setting the one or more timers to zero based on selecting the first feedback mode, where the one or more timers are associated with RLC status signaling.

[0181] In some examples, feedback message component 840 can be configured as or otherwise support means for including in the RLC status report an indication of the number of segments associated with the outer decoding transmission scheme that have been successfully received by the UE.

[0182] In some examples, to support sending the feedback message, the feedback message component 840 may be configured as or otherwise support a component for sending a set of multiple feedback messages via the first set of resources of the primary component carrier of the first cell group and the second set of resources of the primary component carrier of the first cell group, the set of multiple feedback messages including the feedback message.

[0183] In some examples, feedback message component 840 can be configured as or otherwise support means for generating the feedback message according to the HARQ codebook type, wherein sending the feedback message is based on the generating.

[0184] In some examples, sleep mode component 850 can be configured as or otherwise support means for entering sleep mode based on sending the feedback message. In some examples, deactivation component 830 can be configured as or otherwise support means for deactivating the carrier aggregation, the outer coding transmission scheme, or both based on entering the sleep mode.

[0185] In some examples, the feedback message component 840 may be configured as or otherwise support a component for avoiding sending one or more additional feedback messages via the first set of resources and the portion of the second set of resources associated with retransmitting the one or more downlink messages based on entering the sleep mode, deactivating the retransmission protocol, or both during at least a portion of the first set of resources and the second set of resources associated with retransmitting the one or more downlink messages.

[0186] In some examples, feedback message component 840 can be configured as or otherwise support means for receiving an indication from the network entity that no additional downlink messages are pending based on sending the feedback message, wherein entering the sleep mode is based on receiving the indication.

[0187] In some examples, the threshold indication component 865 may be configured as or otherwise support a component for receiving an indication of a threshold number of segments associated with the external decoding transmission scheme from the network entity, wherein entering the sleep mode is based on the number of segments associated with the external decoding transmission scheme that have been successfully received by the UE satisfying the threshold number of segments.

[0188] In some examples, the periodicity component 855 may be configured as or otherwise support means for receiving, from the network entity, an indication of a periodicity associated with the first feedback mode, the second feedback mode, or a combination thereof, wherein sending the feedback message is based on the periodicity.

[0189] In some examples, the control signaling component 845 may be configured as or otherwise support a component for receiving control signaling that triggers aperiodic feedback signaling via the first set of resources or the second set of resources, wherein sending the feedback message is based on receiving the control signaling.

[0190] In some examples, control signaling component 845 can be configured as or otherwise support means for receiving control signaling indicating a carrier aggregation mode, an instruction to disable RLC retransmissions, or a combination thereof.

[0191] In some examples, the outer decoding transmission scheme includes a PDCP distributed outer decoding scheme associated with a threshold link quality.

[0192] Figure 9 A diagram illustrates a system 900 including a device 905 that supports carrier aggregation and feedback signaling in external coding scenarios, according to one or more aspects of the present disclosure. Device 905 may be an example of, or include components of, device 605, device 705, or UE 115, as described herein. Device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. Device 905 may include components for two-way voice and data communication, including components for sending and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, memory 930, code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 945).

[0193] I / O controller 910 can manage input and output signals for device 905. I / O controller 910 can also manage peripheral devices that are not integrated into device 905. In some cases, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 can utilize an operating system such as iOS. ® ANDROID ® , MS-DOS ® 、MS-WINDOWS ® , OS / 2 ® , UNIX ® 、LINUX ® or another known operating system. Additionally or alternatively, I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 910 may be implemented as part of a processor (such as processor 940). In some cases, a user may interact with device 905 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0194] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, wired, or wireless links as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The 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 the one or more antennas 925. The transceiver 915, or the transceiver 915 and one or more antennas 925, may be examples of the transmitter 615, the transmitter 715, the receiver 610, the receiver 710, or any combination thereof, or components thereof, as described herein.

[0195] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform the various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium (such as system memory or another type of memory). In some cases, the code 935 may not be directly executable by the processor 940, but may (for example, when compiled and executed) cause the computer to perform the functions described herein. In some cases, the memory 930 may contain, for example, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0196] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the 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 the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting carrier aggregation and feedback signaling in external decoding scenarios). For example, the device 905 or a component of the device 905 may include the processor 940 and the memory 930 coupled to or coupled to the processor 940, and the processor 940 and the memory 930 are configured to perform the various functions described herein.

[0197] According to examples disclosed herein, the communication manager 920 may support wireless communications at a UE. For example, the communication manager 920 may be configured to receive one or more downlink messages from a network entity via carrier aggregation according to an external coding transmission scheme. The communication manager 920 may be configured to deactivate a retransmission protocol associated with the one or more downlink messages based on the application of the external coding transmission scheme to the one or more downlink messages. The communication manager 920 may be configured to select at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on the application of the external coding transmission scheme to the one or more downlink messages. The communication manager 920 may be configured to transmit a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0198] By including or configuring a communication manager 920 according to the examples described herein, the device 905 can support techniques for feedback signaling in external decoding scenarios, thereby improving power savings, increasing system efficiency, reducing signaling overhead, improving throughput, reducing system latency, and improving user experience.

[0199] In some examples, the communication manager 920 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise coordinating with the transceiver 915, one or more antennas 925, or any combination thereof. 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 can be supported or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 can include instructions executable by the processor 940 to cause the device 905 to perform various aspects of feedback signaling in carrier aggregation and external decoding scenarios as described herein, or the processor 940 and the memory 930 can be otherwise configured to perform or support such operations.

[0200] Figure 10A block diagram 1000 illustrates a device 1005 that supports feedback signaling in carrier aggregation and external coding scenarios according to one or more aspects of the present disclosure. The device 1005 may be an example of aspects of the network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0201] Receiver 1010 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, PDUs, service data units). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0202] Transmitter 1015 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, PDUs, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0203] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of feedback signaling in carrier aggregation and external coding scenarios as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0204] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor can be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0205] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor (e.g., a DSP, a CPU, an ASIC, an FPGA, a microcontroller), or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting means for performing the functions described herein).

[0206] In some examples, communication manager 1020 can be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 can receive information from receiver 1010, transmit information to transmitter 1015, or be integrated with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0207] According to examples disclosed herein, the communication manager 1020 may support wireless communications at a network entity. For example, the communication manager 1020 may be configured to function as, or otherwise support, means for generating one or more downlink messages according to an external decoding transmission scheme. The communication manager 1020 may be configured to function as, or otherwise support, means for transmitting the one or more downlink messages to a UE via carrier aggregation according to the external decoding transmission scheme. The communication manager 1020 may be configured to function as, or otherwise support, means for selecting, based on generating the one or more downlink messages according to the external decoding transmission scheme, at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources. The communication manager 1020 may be configured to function as, or otherwise support, means for receiving, via the first set of resources or the second set of resources, feedback messages corresponding to the one or more downlink messages according to the selected feedback mode.

[0208] By including or configuring the communication manager 1020 according to the examples as described herein, the device 1005 (e.g., a processor controlling the receiver 1010, the transmitter 1015, the communication manager 1020, or a combination thereof or otherwise coupled thereto) can support techniques for feedback signaling in external decoding scenarios, thereby improving power savings, increasing system efficiency, reducing signaling overhead, improving throughput, reducing system latency, and improving user experience.

[0209] Figure 11 A block diagram 1100 illustrates a device 1105 that supports feedback signaling in carrier aggregation and external coding scenarios according to one or more aspects of the present disclosure. The device 1105 may be an example of aspects of the device 1005 or network entity 105 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0210] Receiver 1110 may provide means for obtaining (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, PDUs, service data units). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0211] Transmitter 1115 may provide means for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, PDUs, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0212] Device 1105 or its various components may be examples of means for performing various aspects of feedback signaling in carrier aggregation and external coding scenarios as described herein. For example, communications manager 1120 may include a downlink message generation component 1125, a downlink message transmission component 1130, a feedback mode selection component 1135, a feedback message component 1140, or any combination thereof. Communications manager 1120 may be an example of aspects of communications manager 1020 as described herein. In some examples, communications manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise coordinating with receiver 1110, transmitter 1115, or both. For example, communications manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or otherwise integrate with receiver 1110, transmitter 1115, or both to obtain information, output information, or perform various other operations as described herein.

[0213] According to examples disclosed herein, a communication manager 1120 can support wireless communications at a network entity. A downlink message generation component 1125 can be configured to, or otherwise support, generate one or more downlink messages according to an external coding transmission scheme. A downlink message transmission component 1130 can be configured to, or otherwise support, transmit the one or more downlink messages to a UE via carrier aggregation according to the external coding transmission scheme. A feedback mode selection component 1135 can be configured to, or otherwise support, select at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on generating the one or more downlink messages according to the external coding transmission scheme. A feedback message component 1140 can be configured to, or otherwise support, receive feedback messages corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0214] Figure 12 A block diagram 1200 illustrates a communication manager 1220 that supports feedback signaling in carrier aggregation and external coding scenarios, in accordance with one or more aspects of the present disclosure. The communication manager 1220 may be an example of aspects of the communication manager 1020, the communication manager 1120, or both, as described herein. The communication manager 1220 or its various components may be examples of means for performing various aspects of feedback signaling in carrier aggregation and external coding scenarios, as described herein. For example, the communication manager 1220 may include a downlink message generating component 1225, a downlink message sending component 1230, a feedback mode selecting component 1235, a feedback message component 1240, a control signaling component 1245, a periodicity component 1250, a deactivation component 1255, a threshold indicating component 1260, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0215] According to examples disclosed herein, a communication manager 1220 can support wireless communications at a network entity. A downlink message generation component 1225 can be configured to, or otherwise support, generate one or more downlink messages according to an external coding transmission scheme. A downlink message transmission component 1230 can be configured to, or otherwise support, transmit the one or more downlink messages to a UE via carrier aggregation according to the external coding transmission scheme. A feedback mode selection component 1235 can be configured to, or otherwise support, select at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on generating the one or more downlink messages according to the external coding transmission scheme. A feedback message component 1240 can be configured to, or otherwise support, receive a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0216] In some examples, the control signaling component 1245 may be configured as or otherwise support a component for sending control signaling to the UE indicating one or more parameters for using the first feedback mode, the second feedback mode, or both, wherein the selection is based on the one or more parameters.

[0217] In some examples, the feedback mode selection component 1235 may be configured as or otherwise support a component for selecting at least one of the first feedback mode and the second feedback mode based on satisfying one or more conditions, wherein the one or more conditions are associated with a power state at the UE, a threshold delay corresponding to the one or more downlink messages, or a combination thereof.

[0218] In some examples, to support selection, the feedback mode selection component 1235 may be configured as or otherwise support a component for selecting a combination of the first feedback mode and the second feedback mode, wherein the first feedback mode corresponds to a first periodicity and the second feedback mode corresponds to a second periodicity, wherein the first periodicity is greater than the second periodicity.

[0219] In some examples, to support receiving the feedback message, feedback message component 1240 can be configured as or otherwise support means for receiving a first feedback message via the first set of resources according to the first periodicity. In some examples, to support receiving the feedback message, feedback message component 1240 can be configured as or otherwise support means for receiving a second feedback message via the second set of resources according to the second periodicity.

[0220] In some examples, to support receiving the first feedback message and the second feedback message, feedback message component 1240 may be configured as or otherwise support a component for alternating between receiving via the corresponding resources associated with the first set of resources according to the first periodicity and receiving via the corresponding resources associated with the second set of resources according to the second periodicity.

[0221] In some examples, to support receiving the feedback message, feedback message component 1240 may be configured as or otherwise support a component for receiving an RLC status report indicating lost RLC packet data units via the first set of resources according to the first feedback mode, wherein the HARQ protocol associated with the second feedback mode is disabled according to the selection.

[0222] In some examples, feedback message component 1240 can be configured as or otherwise support means for receiving, in the RLC status report, an indication of a number of segments associated with the outer decoding transmission scheme that have been successfully received by the UE.

[0223] In some examples, threshold indicating component 1260 can be configured as or otherwise support means for sending an indication of a threshold number of segments associated with the outer decoding transmission scheme to the UE. In some examples, threshold indicating component 1260 can be configured as or otherwise support means for refraining from sending one or more additional segments associated with the outer decoding transmission scheme based on the number of segments associated with the outer decoding transmission scheme meeting the threshold number of segments.

[0224] In some examples, to support receiving the feedback message, the feedback message component 1240 may be configured as or otherwise support a component for receiving a set of multiple feedback messages via the first set of resources of the primary component carrier of the first cell group and the second set of resources of the primary component carrier of the first cell group, the set of multiple feedback messages including the feedback message.

[0225] In some examples, to support receiving the feedback message, feedback message component 1240 can be configured as or otherwise support means for receiving the feedback message according to a HARQ codebook type.

[0226] In some examples, downlink message sending component 1230 can be configured as or otherwise support means for refraining from sending one or more additional downlink messages based on receiving the feedback message. In some examples, feedback message component 1240 can be configured as or otherwise support means for refraining from monitoring for one or more additional feedback messages during at least a portion of the first set of resources, the second set of resources, or both.

[0227] In some examples, deactivation component 1255 can be configured as or otherwise support means for deactivating a retransmission protocol associated with the one or more downlink messages, wherein refraining from sending the one or more additional downlink messages is based on the deactivation.

[0228] In some examples, downlink message sending component 1230 can be configured as or otherwise support means for sending an indication to the UE that the one or more additional downlink messages are not pending, wherein avoiding sending the one or more additional downlink messages is based on receiving the indication.

[0229] In some examples, the periodicity component 1250 may be configured as or otherwise support means for sending an indication to the UE of a periodicity associated with the first feedback mode, the second feedback mode, or a combination thereof, wherein receiving the feedback message is based on the periodicity.

[0230] In some examples, the control signaling component 1245 may be configured as or otherwise support a component for sending control signaling that triggers non-periodic feedback signaling via the first set of resources or the second set of resources, wherein receiving the feedback message is based on receiving the control signaling.

[0231] In some examples, control signaling component 1245 can be configured as or otherwise support means for sending control signaling indicating a carrier aggregation mode, an instruction to disable RLC retransmissions, or a combination thereof.

[0232] In some examples, the outer decoding transmission scheme includes a PDCP distributed outer decoding scheme associated with a threshold link quality.

[0233] Figure 13A diagram illustrates a system 1300 including a device 1305 supporting feedback signaling in carrier aggregation and external coding scenarios, according to one or more aspects of the present disclosure. Device 1305 may be an example of, or include components of, device 1005, device 1105, or network entity 105, as described herein. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, including via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components that support outgoing and incoming communications, such as a communications manager 1320, a transceiver 1310, an antenna 1315, memory 1325, code 1330, and a processor 1335. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1340).

[0234] The transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1305 may include one or more antennas 1315, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1310 may also include a modem to: modulate a signal; provide the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receive the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulate the signal. In some implementations, the transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or a combination thereof. In some implementations, the transceiver 1310 may include or be configured to be coupled to one or more processors or memory components operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1310, or the transceiver 1310 and one or more antennas 1315, or the transceiver 1310 and one or more antennas 1315 and one or more processors or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip assembly installed in the device 1305. In some examples, the transceiver is operable to support communications via one or more communication links (eg, communication link 125 , backhaul communication link 120 , midhaul communication link 162 , fronthaul communication link 168 ).

[0235] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1325 may contain, for example, a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0236] The processor 1335 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, the processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1335. The processor 1335 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1325) to cause the device 1305 to perform various functions (e.g., functions or tasks supporting carrier aggregation and feedback signaling in external decoding scenarios). For example, the device 1305 or a component of the device 1305 may include the processor 1335 and the memory 1325 coupled to the processor 1335, the processor 1335 and the memory 1325 being configured to perform the various functions described herein. Processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software (such as an operating system, virtual machine, or container instance)) that can host functionality (e.g., by executing code 1330) to perform the functions of device 1305. Processor 1335 may be any suitable processor or processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within memory 1325). In some implementations, processor 1335 may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes those inputs to produce a set of outputs (which may be passed to other systems or components of device 1305, for example). For example, a processing system of device 1305 may refer to a system that includes various other components or subcomponents of device 1305, such as processor 1335, transceiver 1310, communications manager 1320, or other components or combinations of components of device 1305. The processing system of device 1305 can interface with other components of device 1305 and can process information (such as input or signals) received from other components or output information to other components. For example, the chip or modem of device 1305 may include a processing system and one or more interfaces for outputting information or for obtaining information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or the same interface configured to output information and obtain information, among other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, so that device 1305 can transmit information output from the chip or modem.Additionally or alternatively, in some implementations, the one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1305 can obtain information or signal input and the information can be transmitted to the processing system. A person skilled in the art will readily recognize that the first interface can also obtain information or signal input, and the second interface can also output information or signal output.

[0237] In some examples, bus 1340 may support communications for protocol layers (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1340 may support communications associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within components of device 1305 or between different components of device 1305 that may be co-located or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or divided between the different components).

[0238] In some examples, communication manager 1320 can manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1320 can manage the delivery of data communications for client devices, such as one or more UEs 115. In some examples, communication manager 1320 can manage communications with other network entities 105 and can include a controller or scheduler for controlling communications with UEs 115 in coordination with other network entities 105. In some examples, communication manager 1320 can support an X2 interface within LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0239] According to examples disclosed herein, the communication manager 1320 may support wireless communications at a network entity. For example, the communication manager 1320 may be configured to function as, or otherwise support, means for generating one or more downlink messages according to an external decoding transmission scheme. The communication manager 1320 may be configured to function as, or otherwise support, means for transmitting the one or more downlink messages to a UE via carrier aggregation according to the external decoding transmission scheme. The communication manager 1320 may be configured to function as, or otherwise support, means for selecting, based on generating the one or more downlink messages according to the external decoding transmission scheme, at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources. The communication manager 1320 may be configured to function as, or otherwise support, means for receiving, via the first set of resources or the second set of resources, feedback messages corresponding to the one or more downlink messages according to the selected feedback mode.

[0240] By including or configuring a communication manager 1320 according to examples as described herein, the device 1305 can support techniques for feedback signaling in external decoding scenarios, thereby improving power savings, increasing system efficiency, reducing signaling overhead, improving throughput, reducing system latency, and improving user experience.

[0241] In some examples, the communication manager 1320 can be configured to perform various operations (e.g., receive, acquire, monitor, output, transmit) using or otherwise coordinating with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 can be supported or performed by the transceiver 1310, the processor 1335, the memory 1325, the code 1330, or any combination thereof. For example, the code 1330 can include instructions executable by the processor 1335 to cause the device 1305 to perform various aspects of feedback signaling in carrier aggregation and external decoding scenarios as described herein, or the processor 1335 and the memory 1325 can be otherwise configured to perform or support such operations.

[0242] Figure 14 A flow chart illustrating a method 1400 for supporting feedback signaling in a carrier aggregation and external decoding scenario according to one or more aspects of the present disclosure is provided. The operations of the method 1400 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or a component thereof as described herein. Figures 1 to 9The described functions may be performed by the UE 115. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0243] At 1405, the method may include receiving one or more downlink messages from a network entity via carrier aggregation according to an outer decoding transmission scheme. The operations of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figure 8 The described downlink message component 825 is executed.

[0244] At 1410, the method may include: deactivating a retransmission protocol associated with the one or more downlink messages based on the outer decoding transmission scheme being applied to the one or more downlink messages. The operations of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed as described in reference to Figure 8 The described deactivation component 830 is performed.

[0245] At 1415, the method may include selecting at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on the outer decoding transmission scheme being applied to the one or more downlink messages. The operations of 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed as described in reference to Figure 8 The described feedback mode selection component 835 is executed.

[0246] At 1420, the method may include sending a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode. The operations of 1420 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Figure 8 The feedback message component 840 described is executed.

[0247] Figure 15 A flow chart illustrating a method 1500 for supporting feedback signaling in a carrier aggregation and external decoding scenario according to one or more aspects of the present disclosure is provided. The operations of the method 1500 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or a component thereof as described herein. Figures 1 to 9The described functions may be performed by the UE 115. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0248] At 1505, the method may include receiving control signaling from a network entity indicating one or more parameters for using the first feedback mode, the second feedback mode, or both. The operations of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figure 8 The control signaling component 845 described is performed.

[0249] At 1510, the method may include receiving one or more downlink messages from a network entity via carrier aggregation according to an outer decoding transmission scheme. The operations of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described in reference to Figure 8 The described downlink message component 825 is executed.

[0250] At 1515, the method may include: deactivating a retransmission protocol associated with the one or more downlink messages based on the outer decoding transmission scheme being applied to the one or more downlink messages. The operations of 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1515 may be performed as described in reference to Figure 8 The described deactivation component 830 is performed.

[0251] At 1520, the method may include selecting at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on the outer decoding transmission scheme being applied to the one or more downlink messages, wherein the selection is based on the one or more parameters. The operations of 1520 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1520 may be performed as described with reference to Figure 8 The described feedback mode selection component 835 is executed.

[0252] At 1525, the method may include sending a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode. The operations of 1525 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1525 may be performed as described in reference to Figure 8 The feedback message component 840 described is executed.

[0253] Figure 16A flow chart illustrating a method 1600 for supporting feedback signaling in a carrier aggregation and external decoding scenario according to one or more aspects of the present disclosure is provided. The operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0254] At 1605, the method may include generating one or more downlink messages according to an outer decoding transmission scheme. The operations of 1605 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figure 12 The described downlink message generation component 1225 is performed.

[0255] At 1610, the method may include: transmitting the one or more downlink messages to the UE via carrier aggregation according to the outer decoding transmission scheme. The operations of 1610 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described in reference to Figure 12 The described downlink message sending component 1230 is performed.

[0256] At 1615, the method may include selecting at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on generating the one or more downlink messages according to the outer decoding transmission scheme. The operations of 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1615 may be performed as described with reference to Figure 12 The described feedback mode selection component 1235 is executed.

[0257] At 1620, the method may include receiving a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode. The operations of 1620 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Figure 12 The described feedback message component 1240 is executed.

[0258] Figure 17A flow chart illustrating a method 1700 for supporting feedback signaling in a carrier aggregation and external decoding scenario according to one or more aspects of the present disclosure is provided. The operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a network entity or a component thereof as described herein. Figures 1 to 5 as well as Figures 10 to 13 The network entity described herein performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0259] At 1705, the method may include: sending control signaling to the UE indicating one or more parameters for using the first feedback mode, the second feedback mode, or both. The operations of 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figure 12 The control signaling component 1245 described is performed.

[0260] At 1710, the method may include generating one or more downlink messages according to an outer decoding transmission scheme. The operations of 1710 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1710 may be performed as described in reference to Figure 12 The described downlink message generation component 1225 is performed.

[0261] At 1715, the method may include: transmitting the one or more downlink messages to the UE via carrier aggregation according to the outer decoding transmission scheme. The operations of 1715 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Figure 12 The described downlink message sending component 1230 is performed.

[0262] At 1720, the method may include selecting at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based on generating the one or more downlink messages according to the outer decoding transmission scheme, wherein the selection is based on the one or more parameters. The operations of 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1720 may be performed as described with reference to Figure 12 The described feedback mode selection component 1235 is executed.

[0263] At 1725, the method may include receiving a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode. The operations of 1725 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1725 may be performed as described in reference to Figure 12 The described feedback message component 1240 is executed.

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

[0265] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving one or more downlink messages from a network entity via carrier aggregation according to an external decoding transmission scheme; deactivating a retransmission protocol associated with the one or more downlink messages based at least in part on the external decoding transmission scheme being applied to the one or more downlink messages; selecting at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based at least in part on the external decoding transmission scheme being applied to the one or more downlink messages; and sending a feedback message corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0266] Aspect 2: According to the method of aspect 1, the method also includes: receiving control signaling from the network entity indicating one or more parameters for using the first feedback mode, the second feedback mode, or both, wherein the selection is at least partially based on the one or more parameters.

[0267] Aspect 3: According to the method described in any one of Aspects 1 to 2, the method further includes: selecting at least one of the first feedback mode or the second feedback mode based at least in part on satisfying one or more conditions, wherein the one or more conditions are associated with the power state at the UE, the threshold delay corresponding to the one or more downlink messages, or a combination thereof.

[0268] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the selection includes: selecting a combination of the first feedback mode and the second feedback mode, wherein the first feedback mode corresponds to a first periodicity and the second feedback mode corresponds to a second periodicity, wherein the first periodicity is greater than the second periodicity.

[0269] Aspect 5: The method according to aspect 4, wherein sending the feedback message comprises: sending a first feedback message via the first set of resources according to the first periodicity; and sending a second feedback message via the second set of resources according to the second periodicity.

[0270] Aspect 6: A method according to Aspect 5, wherein sending the feedback message includes: activating a first resource in the second set of resources according to the second periodicity; and sending a block error report, an indication of a lost message via a physical downlink control channel, or a combination thereof via the activated first resource in the second set of resources.

[0271] Aspect 7: A method according to any one of Aspects 5 to 6, wherein sending the first feedback message and the second feedback message includes: alternating between sending via the corresponding resources associated with the first set of resources according to the first periodicity and sending via the corresponding resources associated with the second set of resources according to the second periodicity.

[0272] Aspect 8: A method according to any one of Aspects 1 to 7, wherein sending the feedback message comprises: sending an RLC status report via the first set of resources according to the first feedback mode at least in part based on detecting lost RLC packet data units, wherein the HARQ protocol associated with the second feedback mode is disabled according to the selection.

[0273] Aspect 9: The method according to aspect 8 further includes: allowing one or more timers to time out or setting the one or more timers to zero based at least in part on selecting the first feedback mode, wherein the one or more timers are associated with RLC status signaling.

[0274] Aspect 10: The method according to any one of aspects 8 to 9, further comprising: including in the RLC status report an indication of the number of segments associated with the outer decoding transmission scheme that have been successfully received by the UE.

[0275] Aspect 11: A method according to any one of Aspects 1 to 10, wherein sending the feedback message includes: sending multiple feedback messages via the first set of resources of the main component carrier of the first cell group and the second set of resources of the main component carrier of the first cell group, the multiple feedback messages including the feedback message.

[0276] Aspect 12: The method according to any one of aspects 1 to 11, further comprising: generating the feedback message according to a HARQ codebook type, wherein sending the feedback message is based at least in part on the generating.

[0277] Aspect 13: According to the method described in any one of Aspects 1 to 12, the method also includes: entering a sleep mode based at least in part on sending the feedback message; and deactivating the carrier aggregation, the external decoding transmission scheme, or both based at least in part on entering the sleep mode.

[0278] Aspect 14: According to the method of Aspect 13, the method also includes: avoiding sending one or more additional feedback messages via the first set of resources and the second set of resources based at least in part on entering the sleep mode, deactivating the retransmission protocol, or both during at least a portion of the first set of resources and the second set of resources associated with retransmitting the one or more downlink messages.

[0279] Aspect 15: According to the method of any one of Aspects 13 to 14, the method also includes: receiving an indication from the network entity that no additional downlink messages are pending, at least in part based on sending the feedback message, wherein entering the sleep mode is at least in part based on receiving the indication.

[0280] Aspect 16: According to the method described in any one of Aspects 13 to 15, the method further includes: receiving an indication of a threshold number of segments associated with the external decoding transmission scheme from the network entity, wherein entering the sleep mode is at least partially based on the number of segments associated with the external decoding transmission scheme that have been successfully received by the UE meeting the threshold number of segments.

[0281] Aspect 17: The method according to any one of Aspects 1 to 16 further includes: receiving an indication of a periodicity associated with the first feedback mode, the second feedback mode, or a combination thereof from the network entity, wherein sending the feedback message is at least partially based on the periodicity.

[0282] Aspect 18: According to any one of the methods of Aspects 1 to 17, the method further includes: receiving control signaling that triggers non-periodic feedback signaling via the first set of resources or the second set of resources, wherein sending the feedback message is at least partially based on receiving the control signaling.

[0283] Aspect 19: The method according to any one of aspects 1 to 18, further comprising: receiving control signaling indicating: a carrier aggregation mode, an instruction for deactivating RLC retransmission, or a combination thereof.

[0284] Aspect 20: The method according to any one of aspects 1 to 19, wherein the outer decoding transmission scheme comprises a PDCP distributed outer decoding scheme associated with a threshold link quality.

[0285] Aspect 21: A method for wireless communication at a network entity, the method comprising: generating one or more downlink messages according to an external decoding transmission scheme; sending the one or more downlink messages to a UE via carrier aggregation according to the external decoding transmission scheme; selecting at least one of a first feedback mode associated with a first set of RLC reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based at least in part on generating the one or more downlink messages according to the external decoding transmission scheme; and receiving feedback messages corresponding to the one or more downlink messages via the first set of resources or the second set of resources according to the selected feedback mode.

[0286] Aspect 22: The method according to aspect 21 further includes: sending control signaling to the UE indicating one or more parameters for using the first feedback mode, the second feedback mode, or both, wherein the selection is at least partially based on the one or more parameters.

[0287] Aspect 23: According to any one of Aspects 21 to 22, the method further includes: selecting at least one of the first feedback mode and the second feedback mode based at least in part on satisfying one or more conditions, wherein the one or more conditions are associated with the power state at the UE, the threshold delay corresponding to the one or more downlink messages, or a combination thereof.

[0288] Aspect 24: A method according to any one of Aspects 21 to 23, wherein the selection includes: selecting a combination of the first feedback mode and the second feedback mode, wherein the first feedback mode corresponds to a first periodicity and the second feedback mode corresponds to a second periodicity, wherein the first periodicity is greater than the second periodicity.

[0289] Aspect 25: The method according to aspect 24, wherein receiving the feedback message comprises: receiving a first feedback message via the first set of resources according to the first periodicity; and receiving a second feedback message via the second set of resources according to the second periodicity.

[0290] Aspect 26: A method according to any one of Aspects 24 to 25, wherein receiving the first feedback message and the second feedback message includes: alternating between receiving via corresponding resources associated with the first set of resources according to the first periodicity and receiving via corresponding resources associated with the second set of resources according to the second periodicity.

[0291] Aspect 27: A method according to any one of Aspects 21 to 26, wherein receiving the feedback message includes: receiving an RLC status report indicating lost RLC packet data units via the first set of resources according to the first feedback mode, wherein the HARQ protocol associated with the second feedback mode is disabled according to the selection.

[0292] Aspect 28: The method according to aspect 27, further comprising: receiving in the RLC status report an indication of a number of segments associated with the outer decoding transmission scheme that have been successfully received by the UE.

[0293] Aspect 29: The method according to Aspect 28 further includes: sending an indication of a threshold number of segments associated with the external decoding transmission scheme to the UE; and avoiding sending one or more additional segments associated with the external decoding transmission scheme based at least in part on the number of segments associated with the external decoding transmission scheme satisfying the threshold number of segments.

[0294] Aspect 30: A method according to any one of Aspects 21 to 29, wherein receiving the feedback message includes: receiving multiple feedback messages via the first set of resources of the main component carrier of the first cell group and the second set of resources of the main component carrier of the first cell group, the multiple feedback messages including the feedback message.

[0295] Aspect 31: The method according to any one of aspects 21 to 30, wherein receiving the feedback message comprises: receiving the feedback message according to a HARQ codebook type.

[0296] Aspect 32: According to any one of Aspects 21 to 31, the method further includes: avoiding sending one or more additional downlink messages based at least in part on receiving the feedback message; and avoiding monitoring one or more additional feedback messages during at least a portion of the first set of resources, the second set of resources, or both.

[0297] Aspect 33: The method according to aspect 32, further comprising: deactivating a retransmission protocol associated with the one or more downlink messages, wherein refraining from sending the one or more additional downlink messages is based at least in part on the deactivation.

[0298] Aspect 34: The method according to any one of Aspects 32 to 33, further comprising: sending an indication to the UE that the one or more additional downlink messages are not pending, wherein avoiding sending the one or more additional downlink messages is at least partially based on receiving the indication.

[0299] Aspect 35: The method according to any one of Aspects 21 to 34, further comprising: sending an indication of a periodicity associated with the first feedback mode, the second feedback mode, or a combination thereof to the UE, wherein receiving the feedback message is at least partially based on the periodicity.

[0300] Aspect 36: According to any one of aspects 21 to 35, the method further includes: sending control signaling to trigger non-periodic feedback signaling via the first set of resources or the second set of resources, wherein receiving the feedback message is at least partly based on receiving the control signaling.

[0301] Aspect 37: The method according to any one of aspects 21 to 36 further comprises: sending control signaling indicating the following: a carrier aggregation mode, an instruction for deactivating RLC retransmission, or a combination thereof.

[0302] Aspect 38: The method of any one of aspects 21 to 37, wherein the outer decoding transmission scheme comprises a PDCP distributed outer decoding scheme associated with a threshold link quality.

[0303] Aspect 39: An apparatus for wireless communication at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 20.

[0304] Aspect 40: An apparatus for wireless communication at a UE, the apparatus comprising: at least one component for performing the method according to any one of aspects 1 to 20.

[0305] Aspect 41: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 20.

[0306] Aspect 42: An apparatus for wireless communication at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 21 to 38.

[0307] Aspect 43: An apparatus for wireless communication at a network entity, the apparatus comprising: at least one component for performing the method according to any one of aspects 21 to 38.

[0308] Aspect 44: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 21 to 38.

[0309] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0310] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and the terminology of LTE, LTE-A, LTE-A Pro, or NR may be used throughout much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0311] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0312] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the 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, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0313] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or transmitted using one or more instructions or codes of 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 functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

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

[0315] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of 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). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can 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 "based at least in part on."

[0316] The term "determining" encompasses a variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, searching (such as by searching in a table, database, or other data structure), ascertaining, and the like. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), and the like. Furthermore, "determining" may include resolving, retrieving, selecting, choosing, establishing, and other such similar actions.

[0317] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description can apply to any of the similar components having the same first reference label, regardless of the second reference label or other subsequent reference labels.

[0318] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "having advantages over other examples." The detailed description includes specific details 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 concepts of the described examples.

[0319] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the UE to: receiving one or more downlink messages from a network entity via carrier aggregation according to an outer coding transmission scheme; deactivating a retransmission protocol associated with the one or more downlink messages based at least in part on applying the outer decoding transmission scheme to the one or more downlink messages; selecting at least one of a first feedback mode associated with a first set of radio link control reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based at least in part on applying the outer decoding transmission scheme to the one or more downlink messages; as well as A feedback message corresponding to the one or more downlink messages is sent via the first set of resources or the second set of resources according to the selected feedback mode.

2. The UE of claim 1 , wherein the instructions are further executable by the processor to cause the UE to: Control signaling is received from the network entity indicating one or more parameters for using the first feedback mode, the second feedback mode, or both, wherein selection of the at least one of the first feedback mode or the second feedback mode is based at least in part on the one or more parameters.

3. The UE of claim 1 , wherein the instructions are further executable by the processor to cause the UE to: At least one of the first feedback mode or the second feedback mode is selected based at least in part on satisfying one or more conditions, wherein the one or more conditions are associated with a power state at the UE, a threshold latency corresponding to the one or more downlink messages, or a combination thereof.

4. The UE of claim 1 , wherein the instructions for selecting are executable by the processor to cause the UE to: A combination of the first feedback mode and the second feedback mode is selected, wherein the first feedback mode corresponds to a first periodicity and the second feedback mode corresponds to a second periodicity, wherein the first periodicity is greater than the second periodicity.

5. The UE of claim 4 , wherein the instructions for sending the feedback message are executable by the processor to cause the UE to: sending a first feedback message via the first set of resources according to the first periodicity; and A second feedback message is sent via the second set of resources according to the second periodicity.

6. The UE of claim 5, wherein the instructions for sending the feedback message are executable by the processor to cause the UE to: activating a first resource in the second set of resources according to the second periodicity; and A block error report, an indication of a missed message via a physical downlink control channel, or a combination thereof is sent via the activated first resource in the second set of resources.

7. The UE of claim 5, wherein the instructions for sending the first feedback message and the second feedback message are executable by the processor to cause the UE to: Alternating between transmitting via respective resources associated with the first set of resources according to the first periodicity and transmitting via respective resources associated with the second set of resources according to the second periodicity.

8. The UE of claim 1 , wherein the instructions for sending the feedback message are executable by the processor to cause the UE to: and sending a radio link control status report via the first set of resources according to the first feedback mode based at least in part on detecting lost radio link control packet data units, wherein a hybrid automatic repeat request protocol associated with the second feedback mode is disabled according to selection of the at least one of the first feedback mode or the second feedback mode.

9. The UE of claim 8, wherein the instructions are further executable by the processor to cause the UE to: One or more timers are allowed to expire or are set to zero based at least in part on selection of the first feedback mode, wherein the one or more timers are associated with radio link control state signaling.

10. The UE of claim 8, wherein the instructions are further executable by the processor to cause the UE to: An indication of a number of segments associated with the outer decoding transmission scheme that have been successfully received by the UE is included in the radio link control status report.

11. The UE of claim 1 , wherein the instructions for sending the feedback message are executable by the processor to cause the UE to: A plurality of feedback messages are sent via the first set of resources of a primary component carrier of a first cell group and via the second set of resources of the primary component carrier of the first cell group, the plurality of feedback messages including the feedback message.

12. The UE of claim 1 , wherein the instructions are further executable by the processor to cause the UE to: The feedback message is generated according to a hybrid automatic repeat request codebook type, wherein sending the feedback message is based at least in part on generating the feedback message.

13. The UE of claim 1 , wherein the instructions are further executable by the processor to cause the UE to: entering a sleep mode based at least in part on sending the feedback message; and The carrier aggregation, the outer coding transmission scheme, or both are disabled based at least in part on entering the sleep mode.

14. The UE of claim 13, wherein the instructions are further executable by the processor to cause the UE to: Avoiding sending one or more additional feedback messages via the first set of resources and the portion of the second set of resources based at least in part on entering the sleep mode, deactivating the retransmission protocol, or both during at least a portion of the first set of resources and the second set of resources associated with retransmitting the one or more downlink messages.

15. The UE of claim 13, wherein the instructions are further executable by the processor to cause the UE to: An indication is received from the network entity that no additional downlink messages are pending based at least in part on sending the feedback message, wherein the sleep mode is entered based at least in part on receiving the indication.

16. The UE of claim 13, wherein the instructions are further executable by the processor to cause the UE to: An indication of a threshold number of segments associated with the outer decoding transmission scheme is received from the network entity, wherein the sleep mode is entered based at least in part on the number of segments associated with the outer decoding transmission scheme that have been successfully received by the UE satisfying the threshold number of segments.

17. The UE of claim 1 , wherein the instructions are further executable by the processor to cause the UE to: An indication of a periodicity associated with the first feedback mode, the second feedback mode, or a combination thereof is received from the network entity, wherein sending the feedback message is based at least in part on the periodicity.

18. The UE of claim 1 , wherein the instructions are further executable by the processor to cause the UE to: Control signaling is received that triggers aperiodic feedback signaling via the first set of resources or the second set of resources, wherein sending the feedback message is based at least in part on receiving the control signaling.

19. The UE of claim 1 , wherein the instructions are further executable by the processor to cause the UE to: Control signaling is received indicating a carrier aggregation mode, an instruction to disable radio link control retransmission, or a combination thereof.

20. The UE of claim 1, wherein the outer decoding transmission scheme comprises a Packet Data Convergence Protocol distributed outer decoding scheme associated with a threshold link quality.

21. A network entity, comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the network entity to: generating one or more downlink messages according to an outer decoding transmission scheme; transmitting the one or more downlink messages to a user equipment (UE) via carrier aggregation according to the outer coding transmission scheme; selecting at least one of a first feedback mode associated with a first set of radio link control reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based at least in part on generating the one or more downlink messages according to the outer decoding transmission scheme; as well as A feedback message corresponding to the one or more downlink messages is received via the first set of resources or the second set of resources according to the selected feedback mode.

22. The network entity of claim 21 , wherein the instructions are further executable by the processor to cause the network entity to: Control signaling is sent to the UE indicating one or more parameters for using the first feedback mode, the second feedback mode, or both, wherein selection of the at least one of the first feedback mode or the second feedback mode is based at least in part on the one or more parameters.

23. The network entity of claim 21 , wherein the instructions are further executable by the processor to cause the network entity to: The at least one of the first feedback mode and the second feedback mode is selected based at least in part on satisfying one or more conditions, wherein the one or more conditions are associated with a power state at the UE, a threshold latency corresponding to the one or more downlink messages, or a combination thereof.

24. The network entity of claim 21 , wherein the instructions for selecting are executable by the processor to cause the network entity to: A combination of the first feedback mode and the second feedback mode is selected, wherein the first feedback mode corresponds to a first periodicity and the second feedback mode corresponds to a second periodicity, wherein the first periodicity is greater than the second periodicity.

25. The network entity of claim 21 , wherein the instructions for receiving the feedback message are executable by the processor to cause the network entity to: A radio link control status report indicating lost radio link control packet data units is received via the first set of resources according to the first feedback mode, wherein a hybrid automatic repeat request protocol associated with the second feedback mode is disabled according to selection of the at least one of the first feedback mode or the second feedback mode.

26. The network entity of claim 21 , wherein the instructions for receiving the feedback message are executable by the processor to cause the network entity to: A plurality of feedback messages are received via the first set of resources of a primary component carrier of a first cell group and via the second set of resources of the primary component carrier of the first cell group, the plurality of feedback messages including the feedback message.

27. The network entity of claim 21 , wherein the instructions for receiving the feedback message are executable by the processor to cause the network entity to: The feedback message is received according to a hybrid automatic repeat request codebook type.

28. The network entity of claim 21 , wherein the instructions are further executable by the processor to cause the network entity to: refraining from sending one or more additional downlink messages based at least in part on receiving the feedback message; and Monitoring for one or more additional feedback messages is avoided during at least a portion of the first set of resources, the second set of resources, or both.

29. A method for wireless communication at a user equipment (UE), the method comprising: receiving one or more downlink messages from a network entity via carrier aggregation according to an outer coding transmission scheme; deactivating a retransmission protocol associated with the one or more downlink messages based at least in part on the outer decoding transmission scheme being applied to the one or more downlink messages; selecting at least one of a first feedback mode associated with a first set of radio link control reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based at least in part on the outer decoding transmission scheme being applied to the one or more downlink messages; as well as A feedback message corresponding to the one or more downlink messages is sent via the first set of resources or the second set of resources according to the selected feedback mode.

30. A method for wireless communication at a network entity, the method comprising: generating one or more downlink messages according to an outer decoding transmission scheme; transmitting the one or more downlink messages to a user equipment (UE) via carrier aggregation according to the outer coding transmission scheme; selecting at least one of a first feedback mode associated with a first set of radio link control reports and resources or a second feedback mode associated with a second set of hybrid automatic request reports and resources based at least in part on generating the one or more downlink messages according to the outer decoding transmission scheme; as well as A feedback message corresponding to the one or more downlink messages is received via the first set of resources or the second set of resources according to the selected feedback mode.

Images