Configuration for group-shared downlink channel with repetition

Abstract

The invention relates to a configuration for a group-shared downlink channel with repetition. Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a configuration for a group-shared physical downlink shared channel (PDSCH), wherein the group-shared PDSCH is repeated by a number of repetitions. Accordingly, the UE may determine the number of repetitions and then monitor the group-shared PDSCH based on the number of repetitions. In some implementations, the group-shared PDSCH may include a semi-static repetition scheme in which the number of repetitions is indicated via a group aggregation factor. Additionally or alternatively, the group-shared PDSCH may include a dynamic repetition scheme in which the number of repetitions is indicated via the number of group repetitions. Additionally, the techniques described herein may enable a configuration for a duplicated group-shared PDSCH to include a gap between each repetition in the group-shared PDSCH and enable a UE to transmit acknowledgement feedback for the repetition of the group-shared PDSCH.

Description

[0001] This patent application is a divisional application of Chinese patent application number 202180067723.1 and international application number PCT / US2021 / 050101, entitled "Configuration for group shared downlink channels with duplication", filed on September 13, 2021.

[0002] Cross-references

[0003] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 090,036, filed by LIU et al. on October 9, 2020, entitled “CONFIGURATION FOR GROUP-COMMON DOWNLINK CHANNELS WITH REPETITIONS,” and U.S. Patent Application No. 17 / 472,452, filed by LIU et al. on September 10, 2021, entitled “CONFIGURATION FOR GROUP-COMMON DOWNLINK CHANNELS WITH REPETITIONS,” each of which is assigned to the assignee of this application. Technical Field

[0004] The following relates to wireless communications, including configurations for a group-shared downlink channel with repetition. Background Art

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. 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, Advanced LTE (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 various technologies, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM).

[0006] A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication of multiple communication devices, which may be further referred to as user equipment (UE). In some cases, a base station may communicate with multiple UEs simultaneously. For example, a base station may use broadcast transmission or multicast transmission to convey the same message to multiple UEs. Rather than being specifically configured for transmission of each UE, a base station may be configured for group-shared transmissions of multiple UEs and indicate these configurations to the multiple UEs so that the multiple UEs can monitor and receive these group-shared transmissions. Efficient technology is desired to support successful reception and decoding of group-shared transmissions at multiple UEs. Summary of the Invention

[0007] The described technology relates to improved methods, systems, devices and apparatus for supporting configurations for group-shared downlink channels with repetitions. In general, the described technology provides a configuration for a user equipment (UE) to receive a group-shared physical downlink shared channel (PDSCH). The configuration includes an indication that the group-shared PDSCH is repeated with a repetition number. For example, the group-shared PDSCH may include a group-shared dynamic PDSCH, one or more group-shared semi-persistent scheduling (SPS) PDSCHs, or a combination thereof. Accordingly, the UE may determine the repetition number and then monitor the group-shared PDSCH based on the repetition number. In some implementations, the same configuration or different configurations may indicate a semi-static repetition scheme for the group-shared PDSCH, where the repetition number is indicated via a group aggregation factor. Additionally or alternatively, the same configuration or different configurations may indicate a dynamic repetition scheme for the group-shared PDSCH, where the repetition number is indicated via a group repetition number.

[0008] Additionally, the configuration for the group-common PDSCH may include an indication of a gap that occurs between each repetition of the group-common PDSCH. For example, the gap may include the number of time slots between each repetition of the group-common PDSCH (e.g., or transmission intervals of different lengths), where the UE does not expect to receive additional configurations that schedule additional group-common PDSCHs during the gap. The gap may be semi-statically signaled (e.g., via radio resource control (RRC) signaling) or dynamically signaled (e.g., via a time domain resource allocation (TDRA) entry having the time slot included). In some implementations, the UE may transmit acknowledgment feedback for the group-common PDSCH and the number of repetitions for the group-common PDSCH. For example, the UE may transmit acknowledgment feedback using a type 1 acknowledgment codebook or a type 2 acknowledgment codebook. For both types, the UE may determine several candidate opportunities for receiving the group-common PDSCH and for determining acknowledgment feedback. The UE may determine several candidate opportunities based on the grouping factor, group repetition number, gap between repetitions, feedback timing indicator field value, slot offset, etc., each of which depends on which type of acknowledgement codebook is used or configured.

[0009] A method for wireless communication at a UE is described. The method may include receiving, from a base station, a repetition configuration for a group common downlink shared channel, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof, determining a repetition number for the group common downlink shared channel based on the repetition configuration, and monitoring the group common downlink shared channel from the base station based on the determined repetition number.

[0010] An apparatus for wireless communication at a user equipment terminal (UE) is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive a repetition configuration for a group common downlink shared channel from a base station, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; determine a repetition number for the group common downlink shared channel based on the repetition configuration; and monitor the group common downlink shared channel from the base station based on the determined repetition number.

[0011] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving, from a base station, a repetition configuration for a group common downlink shared channel, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; means for determining a repetition number for the group common downlink shared channel based on the repetition configuration; and means for monitoring the group common downlink shared channel from the base station based on the determined repetition number.

[0012] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive a repetition configuration for a group common downlink shared channel from a base station, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; determine a repetition number for the group common downlink shared channel based on the repetition configuration; and monitor the group common downlink shared channel from the base station based on the determined repetition number.

[0013] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, receiving the group common configuration for the downlink shared channel may include operations, features, apparatus, or instructions for the following actions: receiving a semi-static repetition configuration for the repetition configuration from the base station.

[0014] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, receiving the semi-static repetition configuration may include operations, features, apparatuses, or instructions for the following actions: receiving the semi-static repetition configuration for the repetition configuration from the base station via radio resource control signaling.

[0015] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the semi-static repetition configuration includes a group clustering factor, wherein the repetition number can be determined based on the group clustering factor and the group common downlink shared channel.

[0016] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the group gathering factor for the one or more group-common downlink shared channels or the one or more semi-persistent group-common downlink shared channels may be predefined as one.

[0017] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining the group clustering factor for the one or more semi-persistent group common downlink shared channels based on the group clustering factor for the one or more group common downlink shared channels, wherein the repetitive configuration includes a group radio network temporary identifier associated with the one or more semi-persistent group common downlink shared channels.

[0018] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining, based on the clustering factor of the unicast downlink shared channel configured to the UE, the group clustering factor for the one or more group common downlink shared channels having a group radio network temporary identifier.

[0019] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, receiving the configuration for the downlink shared channel may include operations, features, apparatus, or instructions for the following actions: receiving a dynamic repetition configuration for the repetition configuration from the base station.

[0020] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the dynamic repetition configuration includes a group repetition number parameter indicated via a time domain resource allocation, wherein the repetition number can be determined based on the group repetition number parameter.

[0021] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for: receiving a gap configuration from the base station, the gap configuration including an indication of gaps occurring between repetitions of the group common downlink shared channel.

[0022] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, receiving the gap configuration may include operations, features, means, or instructions for receiving the gap configuration from the base station semi-statically via radio resource control signaling, dynamically via a time-domain resource allocation indication including a gap value for the gap, or a combination thereof.

[0023] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the gap comprises a number of time slots between each repetition of the group common downlink shared channel, where the length of each time slot may be based on a configuration of a portion of the bandwidth used to carry the group common downlink shared channel.

[0024] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the gap can be configured independently for the one or more downlink shared channels and the one or more semi-persistent downlink shared channels.

[0025] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the number of repetitions combined with the gap between repetitions does not exceed a periodicity configured for a semi-persistent downlink shared channel.

[0026] Some examples of the methods, apparatus (devices) and non-transitory computer-readable media described herein may further include operations, features, apparatuses or instructions for the following actions: transmitting an acknowledgment feedback message for the group common downlink shared channel to the base station based on the monitoring, wherein the acknowledgment feedback message indicates successful reception or unsuccessful reception of the group common downlink shared channel based on the number of repetitions.

[0027] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for the following actions: receiving, from the base station, a configuration of a type 1 acknowledgment codebook for transmitting the acknowledgment feedback message.

[0028] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining a plurality of opportunities for monitoring the group common downlink shared channel based on the number of repetitions and a gap value representing a gap between each repetition of the group common downlink shared channel, and transmitting a single acknowledgment feedback message for the plurality of opportunities to the base station based on the type 1 acknowledgment codebook.

[0029] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for the following actions: receiving, from the base station, a configuration of a type 2 acknowledgment codebook for transmitting the acknowledgment feedback message.

[0030] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for the following actions: determining multiple opportunities for monitoring the group common downlink shared channel based on a feedback timing indicator field value between the last repetition of the group common downlink shared channel and the acknowledgment feedback message, an offset value between the downlink control channel carrying the repetition configuration and the first repetition of the group common downlink shared channel, the number of repetitions, a gap value representing a gap between each repetition of the group common downlink shared channel, or a combination thereof, and transmitting the acknowledgment feedback message for the multiple opportunities to the base station based on the type 2 acknowledgment codebook.

[0031] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the recurring configuration includes a group radio network temporary identifier shared by a plurality of UEs including at least the UE.

[0032] A method for wireless communication at a base station is described. The method may include determining a repetition number for a group common downlink shared channel, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof, transmitting a repetition configuration for the group common downlink shared channel to one or more UEs, the repetition configuration including an indication of the determined repetition number, and transmitting the group common downlink shared channel to the one or more UEs based on the determined repetition number.

[0033] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: determine a repetition number for a group-common downlink shared channel, the group-common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; transmit a repetition configuration for the group-common downlink shared channel to one or more UEs, the repetition configuration including an indication of the determined repetition number; and transmit the group-common downlink shared channel to the one or more UEs based on the determined repetition number.

[0034] Another apparatus for wireless communication at a base station is described. The apparatus may include: means for determining a repetition number for a group-common downlink shared channel, the group-common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; means for transmitting a repetition configuration for the group-common downlink shared channel to one or more UEs, the repetition configuration comprising an indication of the determined repetition number; and means for transmitting the group-common downlink shared channel to the one or more UEs based on the determined repetition number.

[0035] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to: determine a repetition number for a group-common downlink shared channel, the group-common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; transmit a repetition configuration for the group-common downlink shared channel to one or more UEs, the repetition configuration including an indication of the determined repetition number; and transmit the group-common downlink shared channel to the one or more UEs based on the determined repetition number.

[0036] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, transmitting the group common configuration for the downlink shared channel may include operations, features, apparatus, or instructions for the following actions: transmitting a semi-static repetition configuration for the repetition configuration to the one or more UEs.

[0037] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, transmitting the semi-static repetition configuration may include operations, features, apparatuses, or instructions for transmitting the semi-static repetition configuration to the one or more UEs via radio resource control signaling.

[0038] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the semi-static repetition configuration includes a group clustering factor, wherein the repetition number can be indicated based on the group clustering factor and the group common downlink shared channel.

[0039] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, transmitting the configuration for the downlink shared channel may include operations, features, apparatus, or instructions for: transmitting a dynamic repetition configuration for the repetition configuration to the one or more UEs.

[0040] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the dynamic repetition configuration includes a group repetition number parameter indicated via a time domain resource allocation, wherein the repetition number can be indicated based on the group repetition number parameter.

[0041] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting a gap configuration to the one or more UEs, the gap configuration including an indication of gaps occurring between repetitions of the group common downlink shared channel.

[0042] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, transmitting the gap configuration may include operations, features, means, or instructions for transmitting the gap configuration to the one or more UEs semi-statically via radio resource control signaling, dynamically via a time domain resource allocation indication including a gap value for the gap, or a combination thereof.

[0043] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the gap comprises a number of time slots between each repetition of the group common downlink shared channel, where the length of each time slot may be based on a configuration of a portion of the bandwidth used to carry the group common downlink shared channel.

[0044] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the gap can be configured independently for the one or more downlink shared channels and the one or more semi-persistent downlink shared channels.

[0045] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the number of repetitions combined with the gap between repetitions does not exceed a periodicity configured for a semi-persistent downlink shared channel.

[0046] Some examples of the methods, apparatus (devices) and non-transitory computer-readable media described herein may further include operations, features, apparatuses or instructions for the following actions: receiving an acknowledgment feedback message for the group common downlink shared channel from the one or more UEs based on transmitting the group common downlink shared channel, wherein the acknowledgment feedback message indicates successful reception or unsuccessful reception of the group common downlink shared channel based on the number of repetitions.

[0047] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for the following actions: transmitting a configuration of a type 1 acknowledgment codebook for the one or more UEs to transmit the acknowledgment feedback message, wherein the acknowledgment feedback message can be received based on the type 1 acknowledgment codebook.

[0048] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting a configuration of a type 2 acknowledgment codebook for transmitting the acknowledgment feedback message by the one or more UEs, wherein the acknowledgment feedback message may be received based on the type 2 acknowledgment codebook.

[0049] In some examples of the methods, apparatus (devices), and non-transitory computer-readable media described herein, the repetitive configuration includes a group radio network temporary identifier indicating that the group common downlink shared channel can be transmitted to the one or more UEs. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1

[0014] An example of a wireless communication system supporting configurations for group-common downlink channels with duplication is illustrated in accordance with aspects of the present disclosure.

[0051] Figure 2

[0014] An example of a wireless communication system supporting configurations for group-common downlink channels with duplication is illustrated in accordance with aspects of the present disclosure.

[0052] Figure 3A and 3B Examples of supporting a repetition scheme for configuration of a group common downlink channel with repetitions are illustrated in accordance with aspects of the present disclosure.

[0053] Figure 4A and 4B Examples of supporting acknowledgement feedback for a configuration with a repeated group common downlink channel are illustrated in accordance with aspects of the present disclosure.

[0054] Figure 5 An example of a process flow supporting configuration for a group common downlink channel with repetition is illustrated in accordance with aspects of the present disclosure.

[0055] Figure 6 and 7 A block diagram of a device supporting configuration for a group common downlink channel with duplication is shown in accordance with aspects of the present disclosure.

[0056] Figure 8A block diagram of a communications manager supporting configuration for a group common downlink channel with duplication is shown in accordance with aspects of the present disclosure.

[0057] Figure 9 A diagram of a system including devices supporting configuration for a group common downlink channel with duplication is shown in accordance with aspects of the present disclosure.

[0058] Figure 10 and 11 A block diagram of a device supporting configuration for a group common downlink channel with duplication is shown in accordance with aspects of the present disclosure.

[0059] Figure 12 A block diagram of a communications manager supporting configuration for a group common downlink channel with duplication is shown in accordance with aspects of the present disclosure.

[0060] Figure 13 A diagram of a system including devices supporting configuration for a group common downlink channel with duplication is shown in accordance with aspects of the present disclosure.

[0061] Figures 14 to 19 A flow chart illustrating a method of supporting configuration for a group common downlink channel with repetition in accordance with aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0062] User equipment (UE) and base stations may support semi-static and / or dynamic repetition of the physical downlink shared channel (PDSCH) in consecutive time slots. For example, the base station may configure the UE with a repetition configuration (e.g., including a pdsch-AggregationFactor (PDSCH aggregation factor) parameter, a RepNumR16 (number of repetitions R16) parameter, etc.) for the UE to apply to unicast dynamic PDSCH and unicast semi-persistent scheduling (SPS) PDSCH. Additionally, the UE in the wireless communication system may also support group-shared physical downlink control channels (PDCCH) and PDSCH (e.g., multicast data) and acknowledgement feedback for group-shared transmissions. However, the configuration for slot-level repetition of group-shared PDSCH has yet to be defined.

[0063] As described herein, a UE may be configured with one or more group-shared PDSCHs, such as a group-shared dynamic PDSCH, one or more group-shared SPS PDSCHs, or a combination thereof, wherein the group-shared PDSCH is further configured with repetition. The one or more group-shared dynamic PDSCHs may include a cyclic redundancy check (CRC) scrambled by different group radio network temporary identifiers (G-RNTIs), and the one or more group-shared SPS PDSCHs may include a CRC scrambled by different configured scheduled G-RNTIs (G-CS-RNTIs). The SPS PDSCH may be associated with the G-CS-RNTI. In a first option of repetition, the group-shared PDSCH may be independently configured with a group aggregation factor (e.g., pdsch-AggregationFactor_group) to indicate a semi-static repetition for the group-shared PDSCH. Alternatively, in a second option of repetition, the group-shared PDSCH may be configured with a group repetition parameter (e.g., RepNum_group) to indicate a dynamic number of repetitions for the group-shared PDSCH. In some cases, for a group-common PDSCH with the same G-RNTI, the same G-CS-RNTI, or a pair of associated G-RNTIs and G-CS-RNTIs configured to enable the same UE group to receive the same service, the UE may not be configured with both options, but may be independently configured with different options for a group-common PDSCH with different G-RNTIs or an SPS group-common PDSCH with different GCS-RNTIs. The UE may also be configured with a gap between each repetition of the group-common PDSCH.

[0064] Additionally, the UE may be configured to transmit acknowledgment feedback for a group-common PDSCH with configured repetitions. In some cases, the UE may transmit acknowledgment feedback using either a Type 1 acknowledgment codebook or a Type 2 acknowledgment codebook. For both types, the UE may determine several candidate opportunities for receiving the group-common PDSCH and for determining acknowledgment feedback. The UE may determine the candidate opportunities based on the group aggregation factor, the number of group repetitions, the gap between repetitions, the feedback timing indicator field value, the slot offset, and the like, each of which depends on which type of acknowledgment codebook is used or configured for use.

[0065] Aspects of the present disclosure are initially described in the context of wireless communication systems. Additionally, aspects of the present disclosure are illustrated using additional wireless communication systems, examples of repetition schemes, acknowledgment feedback configurations, and process flows. Aspects of the present disclosure are further illustrated and described using and with reference to apparatus diagrams, system diagrams, and flow charts related to configurations for a group-shared downlink channel with repetition.

[0066] Figure 1 An example of a wireless communication system 100 supporting a configuration for a group-shared downlink channel with duplication according to aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0067] Base stations 105 may be dispersed throughout a geographic area to form wireless communication system 100 and may be different forms of devices or devices with different capabilities. Base stations 105 and UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which UEs 115 and base stations 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographic area over which base stations 105 and UEs 115 may support signal communication according to one or more radio access technologies.

[0068] 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 stationary and mobile at different times. The UEs 115 may be different forms of devices or devices with different capabilities. Figure 1 1. The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network equipment (e.g., core network nodes, relays, integrated access and backhaul (IAB) nodes, or other network equipment), such as Figure 1 As shown in .

[0069] Each base station 105 can communicate with the core network 130, or with each other, or both. For example, the base stations 105 can interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 can communicate with each other directly (e.g., directly between the base stations 105), indirectly (e.g., via the core network 130), or both directly and indirectly over the backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, the backhaul links 120 can be or include one or more wireless links.

[0070] One or more of the base stations 105 described herein may include or may be referred to by one of ordinary skill in the art as a base transceiver station, a radio 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 Home Node B, a Home Evolved Node B, or other suitable terminology.

[0071] UE 115 may include or 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 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 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.

[0072] 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 base stations 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown in .

[0073] The UE 115 and the base station 105 may communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operation, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0074] In some examples (e.g., 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 Radio Frequency Channel Number (EARFCN)) and may be located according to a channel grid for discovery by a UE 115. A carrier may operate in a standalone mode in which initial acquisition and connection may be performed by a UE 115 via the carrier, or a carrier may operate in a non-standalone mode in which the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0075] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

[0076] A carrier may be associated with a particular bandwidth of radio frequency 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 several determined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) of a carrier of a particular radio access technology. Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth, or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0077] The signal waveform transmitted on the carrier 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 a system employing MCM techniques, a resource element may include one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are 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 code rate of the modulation scheme, or both). Thus, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 can be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further improve the data rate or data integrity of communications with UE 115.

[0078] One or more parameter designs for a carrier may be supported, where the parameter designs may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter designs. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for the UE 115 may be limited to the one or more active BWPs.

[0079] The time interval of the base station 105 or the UE 115 can be expressed as a multiple of a basic time unit, which can be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum 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).

[0080] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of codeword periods (e.g., depending on the length of the cyclic prefix added before each codeword period). In some wireless communication systems 100, the time slot may be further divided into a plurality of mini-time slots containing one or more codewords. Excluding the cyclic prefix, each codeword period may include one or more (e.g., Nf) sampling periods. The duration of the codeword period may depend on the subcarrier spacing or the operating frequency band.

[0081] 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 transmission 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)).

[0082] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier, 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)) for physical control channels may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of a carrier. 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. An aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded 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 .

[0083] Each base station 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 a base station 105 (e.g., on a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish between adjacent cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which the logical communication entity operates. The scope of such a cell may range from a smaller area (e.g., a structure, a subset of structures) to a larger area depending on various factors (such as the capabilities of the base station 105). For example, a cell may be or include a building, a subset of buildings, or an external space between or overlapping geographic coverage areas 110, among other examples.

[0084] 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. A small cell may be associated with a lower power base station 105 (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. 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 base station 105 may support one or more cells and may also support communications over one or more cells using one or more component carriers.

[0085] 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.

[0086] In some examples, base stations 105 can be mobile and, therefore, provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, but the different geographic coverage areas 110 can be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies can be supported by different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

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

[0088] 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 technology that allows devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that incorporate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents it to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wilderness survival monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0089] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but not simultaneous 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 communication, operating over a 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.

[0090] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. The UE 115 can be designed to support ultra-reliable, low-latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication or group communication and can be supported by one or more mission-critical services such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions can include prioritization of services, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency can be used interchangeably herein.

[0091] In some examples, UE 115 may also be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of base station 105 or otherwise unable to receive transmissions from base station 105. In some examples, groups of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, in which each UE 115 transmits to every other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

[0092] 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 may be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages 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)) that routes packets or interconnects to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP services 150 of one or more network operators. The IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0093] Some network devices (such as base stations 105) may include subcomponents, such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with each UE 115 through one or more other access network transport entities 145, which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., base station 105).

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

[0095] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices (such as base stations 105 and UEs 115) may employ carrier sensing for conflict detection and avoidance. In some examples, operations in the unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in coordination with component carriers operating in the licensed band. Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0096] The base station 105 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 base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can 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, the antennas or antenna arrays associated with the base station 105 may be located at different geographical locations. The base station 105 may have an antenna array having several rows and columns of antenna ports that the base station 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0097] The base station 105 or the UE 115 can use MIMO communication to exploit multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique may be referred to as spatial multiplexing. For example, a transmitting device may transmit multiple signals via different antennas or different antenna combinations. Similarly, a receiving device may receive multiple signals via different antennas or different antenna combinations. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits 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.

[0098] 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 device or a receiving device (e.g., base station 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 device and the receiving device. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with that device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0099] The base station 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the base station 105 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 base station 105 in different directions. For example, the base station 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. The transmissions in different beam directions may be used (e.g., by a transmitting device (such as the base station 105) or a receiving device (such as the UE 115)) to identify a beam direction for later transmission or reception by the base station 105.

[0100] Some signals, such as data signals associated with a particular recipient device, may be transmitted by base station 105 in a single beam direction, e.g., a direction associated with a recipient device, such as UE 115. In some examples, a beam direction associated with transmissions along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0101] In some examples, transmission by a device (e.g., by a base station 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from the base station 105 to the UE 115). The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. The base station 105 may transmit reference signals that may be precoded or unprecoded (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)). The 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 type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0102] A receiving device (e.g., UE 115) may attempt multiple receive configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105. For example, the receiving device may attempt multiple receive directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array (e.g., different directional listening weight sets), or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receive configurations or receive directions. In some examples, the receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving data signals). The single receive configuration may be aligned on 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).

[0103] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the bearer or packet data convergence protocol (PDCP) layer can be IP-based. The radio link control (RLC) layer can perform packet segmentation and reassembly to communicate on the logical channel. The media access control (MAC) layer can perform priority handling and multiplex the logical channel into the transport channel. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission of the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration and maintenance of the RRC connection of the radio bearer that supports user plane data between the UE 115 and the base station 105 or the core network 130. In the physical layer, the transport channel can be mapped to the physical channel.

[0104] UE 115 and base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid Automatic Repeat Request (HARQ) feedback is a technique for increasing the likelihood that data is correctly received on communication link 125. 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 may improve MAC layer throughput in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a particular time slot for data received in a previous symbol in that time slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or based on some other time interval.

[0105] A wireless device in the wireless communication system 100 may support semi-static PDSCH repetition in consecutive time slots. For example, a UE 115 may be configured with an aggregation factor (e.g., pdsch-AggregationFactor) in a configuration message for the PDSCH (e.g., pdsch-Config) to indicate semi-static repetition, wherein the UE applies the aggregation factor to unicast dynamic PDSCH, unicast SPS PDSCH, or both. Additionally, the wireless device may support semi-static or dynamic PDSCH repetition in consecutive time slots. For example, for URLLC, a UE 115 may be configured with more than one unicast SPS PDSCH. In some cases, the aggregation factor (e.g., pdsch-AggregationFactor) used for the SPS PDSCH in a configuration message (e.g., sps-Config) may be different from the aggregation factor of the unicast dynamic PDSCH in the corresponding configuration message (e.g., pdsch-Config) and may be different based on the BWP used for different PDSCHs.

[0106] For a multiple transmit reception point (TRP) configuration (e.g., UE 115 includes multiple TRPs for communication with different devices, communication in different directions, etc.), UE 115 may be configured with a dynamic repetition indication (e.g., RepNumR16) included in one entry of a time domain resource allocation (TDRA) table for PDSCH. However, when UE 115 is configured with a dynamic repetition indication (e.g., RepNumR16), UE 115 may not expect to be configured with a semi-static repetition indication (e.g., pdsch-AggregationFactor). That is, if UE 115 is configured with a higher layer parameter for repetition of PDSCH (e.g., repetitionNumber-r16), or if UE 115 is configured with a different repetition scheme (e.g., repetitionSchemeConfig-r16) set to a specific multiplexing scheme (e.g., one of FDMschemeA, FDMschemeB, and TDMschemeA), UE 115 may not expect to be configured with a semi-static repetition indication (e.g., pdsch-AggregationFactor or PDSCH-AggregationFactor-r16).

[0107] Additionally, a UE 115 in the wireless communication system 100 (e.g., in RRC connectivity with the base station 105 or with a different wireless device) may support a group-shared physical downlink control channel (PDCCH) with a CRC scrambled by a common radio network temporary identifier (RNTI) to schedule a group-shared PDSCH, wherein the scrambling of the group-shared PDSCH is based on the same common RNTI. The UE 115 may also support HARQ acknowledgment (HARQ-ACK) feedback for multicast transmissions (e.g., group-shared messages). Additionally, the UE 115 may support FDM between unicast PDSCH and group-shared PDSCH in a slot based on UE capabilities. The UE 115 may also support slot-level repetition for the group-shared PDSCH. However, the configuration of slot-level repetition for the group-shared PDSCH has yet to be determined or determined.

[0108] The wireless communication system 100 may support efficient techniques for signaling configuration of a group-shared downlink channel (e.g., a group-shared PDSCH), wherein the group-shared downlink channel has repetitions. For example, a UE 115 may receive a configuration for a group-shared PDSCH, wherein the configuration includes an indication that the group-shared PDSCH is repeated with a repetition number. In some implementations, the group-shared PDSCH may include one or more group-shared dynamic PDSCHs, one or more group-shared SPS PDSCHs, or a combination thereof. Accordingly, the UE 115 may determine the repetition number and then monitor the group-shared PDSCH based on the repetition number. In some implementations, the group-shared PDSCH may include a semi-static repetition scheme, wherein the repetition number is indicated via a group aggregation factor. Additionally or alternatively, the group-shared PDSCH may include a dynamic repetition scheme, wherein the repetition number is indicated via a group repetition number. Additionally, the techniques described herein may enable configuration of a repeated group-common PDSCH to include gaps between each repetition in the group-common PDSCH and enable the UE 115 to transmit acknowledgement feedback (eg, HARQ-ACK feedback) for the repetitions of the group-common PDSCH.

[0109] Figure 2 An example of a wireless communication system 200 that supports configurations for group-shared downlink channels with duplication according to aspects of the present disclosure is illustrated. The wireless communication system 200 may implement aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a base station 105-a, a UE 115-a, a UE 115-b, and a UE 115-c, which may be represented as shown in FIG. Figure 1 Examples of corresponding base stations 105 and UEs 115 are described.

[0110] As described herein, base station 105-a may be configured with a group-common downlink shared channel (e.g., a group-common PDSCH) having repetitions. For example, base station 105-a may configure UE 115-a, UE 115-b, and UE 115-c to have one or more group-common dynamic downlink shared channels (e.g., a group-common dynamic PDSCH), one or more group-common SPS downlink shared channels (e.g., a group-common SPS PDSCH), or both. Accordingly, the one or more group-common downlink shared channels and the one or more group-common SPS downlink shared channels may each be repeated a number of times to increase the likelihood of successful reception and decoding at each UE 115. In some implementations, the one or more group-common downlink shared channels and the one or more group-common SPS downlink shared channels may have the same number of repetitions configured together, or may have different numbers of repetitions configured separately for each type of downlink shared channel.

[0111] Additionally, the configuration for a group-shared dynamic downlink shared channel may include a CRC scrambled by the G-RNTI to indicate that the dynamic downlink shared channel is group-shared and is transmitted to multiple UEs 115. Similarly, the configuration for a group-shared SPS downlink shared channel may include a CRC scrambled by the G-CS-RNTI to indicate that the SPS downlink shared channel is group-shared and is transmitted to multiple UEs 115. UEs 115 may be configured in different UE groups and receive different multicast services. Thus, UEs 115 may be configured to monitor one or more group-shared dynamic PDSCHs with CRCs scrambled by different G-RNTIs and one or more group-shared SPS PDSCHs with CRCs scrambled by different G-CS-RNTIs. Base station 105-a may transmit the group-shared downlink shared channel to multiple UEs 115 via multicast transmission, broadcast transmission, or another technique that allows base station 105-a to transmit the same message to multiple UEs 115.

[0112] In some implementations, the group-common dynamic downlink shared channel (e.g., one or more downlink shared channels) may include a downlink shared channel that is configured by the base station 105-a and transmitted on demand to the UE 115. For example, if the base station 105-a determines that downlink data is available for transmission to the UE 115 (e.g., multicast data), the base station 105-a may subsequently transmit a downlink control channel (e.g., a group-common downlink control channel, a group-common PDCCH, etc.) that schedules the dynamic downlink shared channel to communicate the downlink data to the UE 115. Additionally or alternatively, the group-common SPS downlink shared channel may include a downlink shared channel that is allocated on a semi-persistent basis and that may be used to communicate downlink data (e.g., multicast data) to the UE 115. For example, the base station 105-a may configure resources that occur periodically (e.g., every time slot, every other time slot, etc.), which the base station 105-a may use to transmit downlink data without having to configure resources for each transmission (e.g., a single configuration may indicate multiple instances that may be used for subsequent transmissions). In some implementations, the base station 105 - a may activate and deactivate the group-common SPS downlink shared channel on demand (eg, activated when a sufficient amount of downlink data is to be transmitted to the UE 115 ).

[0113] As shown, base station 105-a may communicate with UE 115-a on resources of carrier 205-a, with UE 115-b on resources of carrier 205-b, and with UE 115-c on resources of carrier 205-c. For example, base station 105-a may transmit a multicast message and data to each UE 115 on the corresponding carrier 205. Before transmitting the multicast message and data to the UE 115, base station 105-a may first transmit a configuration 210 to each UE 115 (e.g., in a PDCCH that schedules a PDSCH for the multicast message and data). In some implementations, configuration 210 may indicate a number of repeated group common downlink shared channels 215, including two or more repetitions of a group common downlink shared channel 220.

[0114] In some implementations, the base station 105-a may transmit repeated group-shared downlink shared channels 215 according to a semi-static repetition scheme. For example, the base station 105-a may configure repeated group-shared downlink shared channels 215 (e.g., dynamic PDSCH, SPS PDSCH, etc.) with a group aggregation factor (e.g., pdsch-AggregationFactor_group) via RRC signaling (e.g., a value different from the value for unicast dynamic / SPS PDSCH) to indicate the number of repetitions of the repeated group-shared downlink shared channels 215. In some implementations, the group aggregation factor may be configured independently for different types of repeated group-shared downlink shared channels 215. For example, a first group aggregation factor may be configured for a group-shared dynamic downlink shared channel, and a second group aggregation factor may be configured for a group-shared SPS downlink shared channel. Additionally or alternatively, the same group aggregation factor may be configured for both types of group-shared downlink shared channels.

[0115] The default value of the group aggregation factor for the group shared dynamic downlink shared channel may be defined to be similar to the value of the unicast dynamic downlink shared channel (in which case UEs monitoring the same group shared dynamic PDSCH are configured with the same unicast dynamic downlink shared channel), or may be predefined to be one (1) (e.g., one (1) instance of the group shared dynamic downlink shared channel is transmitted unless otherwise configured with a repetition number). Additionally or alternatively, the default value of the group aggregation factor for the group shared SPS downlink shared channel may be defined to be similar to the default value of the group shared dynamic downlink shared channel having the G-RNTI associated with the G-CS-RNTI (e.g., corresponding to the same service), or similar to the default value of the unicast dynamic downlink shared channel, or predefined to be one (1).

[0116] Additionally or alternatively, the base station 105-a may transmit a repeated group-shared downlink shared channel 215 according to a dynamic repetition scheme. For example, the base station 105-a may configure a repeated group-shared downlink shared channel 215 (e.g., a dynamic PDSCH, an SPS PDSCH, etc.) with a time domain allocation list (e.g., pdsch-TimeDomainAllocationList) containing a dynamic group repetition number (e.g., RepNum_group) to indicate the repetition number of the repeated group-shared downlink shared channel 215. In some implementations, the TDRA field in the downlink control information (DCI) format for scheduling the group-shared downlink shared channel 220 or for activating the group-shared downlink shared channel 220 (e.g., for the SPS downlink shared channel) may indicate an entry in the time domain allocation list for the repeated group-shared downlink shared channel 215. Similar to the semi-static repetition scheme, the base station 105-a may configure the dynamic group repetition number for different types of group-shared downlink shared channels independently or jointly.

[0117] Regarding the selection between the semi-static repetition scheme and the dynamic repetition scheme, the UE 115 may not be configured with both the semi-static repetition scheme and the dynamic repetition scheme for a group-common downlink shared channel 215 having the same G-RNTI, the same G-CS-RNTI, or a pair of associated G-RNTIs and G-CS-RNTIs configured to the same group of UEs to receive the same service. Additionally or alternatively, the base station 105-a may independently configure the semi-static repetition scheme and the dynamic repetition scheme for a group-common downlink shared channel 215 based on different G-RNTIs or G-CS-RNTIs.

[0118] In some implementations, gaps may occur between each repetition of the repeated group common downlink shared channel 215. Thus, the base station 105-a may configure the repetitions to occur with one or more time slots between each repetition, rather than having each repetition of the repeated group common downlink shared channel 215 occur in consecutive time slots. Figure 3B Describe in more detail.

[0119] Additionally, after monitoring and receiving the repeated group common downlink shared channel 215, the UE 115 may transmit an acknowledgment feedback 225 based on whether the group common downlink shared channel 220 is successfully received and decoded using the repeated group common downlink shared channel 215 (e.g., combining the repetitions). For example, the acknowledgment feedback 225 may include HARQ-ACK feedback, such as a positive acknowledgment (ACK) message indicating successful reception and decoding of the group common downlink shared channel 220 or a negative acknowledgment (NACK) message indicating unsuccessful reception or decoding of the group common downlink shared channel 220. A technique for determining the acknowledgment feedback 225 based on the repeated group common downlink shared channel 215 is described in detail in the accompanying drawings. Figure 4B Describe in more detail.

[0120] Figure 3A and 3B Illustrated are examples of repetition schemes 300 and 301 supporting configurations for a group shared downlink channel with repetitions, in accordance with aspects of the present disclosure. Repetition schemes 300 and 301 may implement aspects of wireless communication systems 100 and 200. For example, base station 105 may use repetition schemes 300 and 301 when transmitting a downlink shared channel to one or more UEs 115. Repetition scheme 300 may represent a unicast downlink shared channel transmitted by base station 105 to a single UE using repetitions of the unicast downlink shared channel. Repetition scheme 301 may represent a group shared downlink shared channel transmitted by base station 105 to multiple UEs 115 using repetitions of the group shared downlink shared channel.

[0121] As previously mentioned, the repetition scheme 300 may illustrate a unicast PDSCH 315 with repetitions in consecutive time slots. For example, the base station 105 may transmit a PDCCH 305 that schedules the repeated PDSCH 310 for the UE 115 to monitor and receive (e.g., via a configuration for the PDSCH). The PDCCH 305 may also indicate the number of repetitions that the unicast PDSCH 315 is transmitted (e.g., as described with reference to FIG. Figure 1As described, via pdsch-AggregationFactor or RepNumR16). For example, the PDCCH 305 may indicate four (4) repetitions of the unicast PDSCH 315 for the repeated PDSCH 310, such as a first unicast PDSCH 315-a (e.g., a first repetition), a second unicast PDSCH 315-b (e.g., a second repetition), a third unicast PDSCH 315-c (e.g., a third repetition), and a fourth unicast PDSCH 315-d (e.g., a fourth repetition). Additionally, in some cases, the PDCCH 305 may include an indication of a slot offset (K0) that represents the number of slots (e.g., or transmission time intervals of different lengths) between the end of the PDCCH 305 and the first unicast PDSCH 315-a.

[0122] Similarly, the repetition scheme 301 may include a PDCCH 320 transmitted by the base station 105, wherein the PDCCH 320 schedules a repeated PDSCH set 325. The repeated PDSCH set 325 may include repetitions of the PDSCH 330 (as described with reference to FIG. Figure 2 As described, for example, as indicated by a group aggregation factor pdsch-AggregationFactor_group or a group repetition number RepNum_group), such as a first PDSCH 330-a (e.g., a first repetition), a second PDSCH 330-b (e.g., a second repetition), a third PDSCH 330-c (e.g., a third repetition), and a fourth PDSCH 330-d (e.g., a fourth repetition). Additionally, the PDCCH 320 may also include an indication of a slot offset K0. However, the PDSCH 330 may be a group common PDSCH (e.g., a group common downlink shared channel) transmitted to multiple UEs 115, rather than as described with reference to FIG. Figure 3A Unicast PDSCH described.

[0123] Additionally, the repetition scheme 301 may include a gap configuration for the group-common PDSCH repetitions. For example, a gap 335 may occur between each repetition in the group-common PDSCH 330. For slot-level repetitions, a gap 335 (e.g., a number of gap slots) having a gap value greater than or equal to zero (0) (e.g., gap 335 ≥ 0) may be configured between the group-common PDSCH repetitions. If the gap is equal to zero (0), the repetitions of the PDSCH 330 may be consecutive (e.g., no gaps occur between repetitions). The gap 335 may include (a plurality of) absolute slots designed according to the parameters of the BWP (e.g., including downlink / uplink slots) for the group-common PDSCH 330. Additionally, the gap 335 may be independent for the group-common dynamic PDSCH and each group-common SPS PDSCH.

[0124] In some implementations, the base station 105 may configure the value of the gap 335 semi-statically (e.g., via RRC signaling) or dynamically (e.g., by indicating a TDRA entry including a gap value). For a group-common SPS PDSCH, the total number of repetitions including the gap slots may not exceed the periodicity in each SPS PDSCH configuration. For example, each group-common SPS PDSCH (possibly associated with a different G-CS-RNTI) may have an independent configuration for periodicity, repetitions, and gaps. Accordingly, the repetitions plus the gap 335 may be less than the periodicity configured for the associated group-common SPS PDSCH. In some implementations, the UE 115 may not expect to receive an additional PDCCH to schedule another group-common PDSCH with the same G-RNTI and the same HARQ process ID during the gap 335 (e.g., during the gap slot(s)).

[0125] Figure 4A and 4B An example of acknowledgment feedback 400 and 401 supporting a configuration for a group shared downlink channel with duplication according to aspects of the present disclosure is illustrated. Acknowledgment feedback 400 and 401 can implement aspects of wireless communication systems 100 and 200. For example, UE 115 can use acknowledgment feedback 400 or 401 to transmit an acknowledgment message to a base station indicating whether the downlink shared channel with duplication was successfully received and decoded.

[0126] Acknowledgement feedback 400 may represent a unicast PDSCH repetition configuration, wherein PDCCH 405 schedules a repeated PDSCH set 410, which includes a first unicast PDSCH 415-a (e.g., a first repetition), a second unicast PDSCH 415-b (e.g., a second repetition), a third unicast PDSCH 415-c (e.g., a third repetition), and a fourth unicast PDSCH 415-d (e.g., a fourth repetition). In some implementations, PDCCH 405 may include an indication of a slot offset (K0) that indicates the number of slots (e.g., or transmission time intervals of different lengths) between the end of PDCCH 405 and the first unicast PDSCH 415-a. Additionally, the PDCCH 405 may include an indication of a feedback indicator field value (e.g., a PDSCH to HARQ feedback timing indicator field value) K1, which indicates the number of time slots (e.g., or different length transmission time intervals) between the last occurrence of the PDSCH (e.g., the fourth unicast PDSCH 415-d) and the uplink channel (e.g., a physical uplink control channel (PUCCH)) carrying the ACK / NACK 420 (e.g., acknowledging the feedback message). The ACK / NACK 420 may include an indication of whether the UE 115 successfully received and decoded the PDSCH 415 using the repeated PDSCH set 410.

[0127] When transmitting ACK / NACK 420 (e.g., for a PDSCH with repetitions), the UE 115 may use a HARQ-ACK codebook. For example, for a Type 1 HARQ-ACK codebook, the UE 115 may use M for the candidate PDSCH repetitions. A,c A single HARQ-ACK feedback is provided by a set of opportunities, where the timeline is counted at the end of the slot repetition. For the semi-static repetition scheme, M for candidate PDSCH reception A,c The set of opportunities may be determined based on the maximum value of the aggregation factor (e.g., pdsch-AggregationFactor) value (e.g., if provided in sps-Config and / or pdsch-Config). And the final PDSCH reception may be determined based on the indicated repetition number (e.g., RepNumR16). That is, if the UE 115 is provided with an aggregation factor (e.g., pdsch-AggregationFactor) in a configuration message (e.g., SPS-Config or PDSCH-Config) for the corresponding PDSCH and there is no time domain allocation list (e.g., pdsch-TimeDomainAllocationList) entry including the repetition number (e.g., RepNumR16) in the time domain allocation list (e.g., pdsch-TimeDomainResourceAllocation), then It can be the maximum value of the aggregation factor (e.g., pdsch-AggregationFactor) in the corresponding configuration message of PDSCH (e.g., in SPS-Config or PDSCH-Config); otherwise

[0128] Using Type 1 HARQ-ACK codebook, if the aggregation factor (e.g., pdsch-AggregationFactor) is provided Then UE 115 may report the The HARQ-ACK information for the PDSCH reception to time slot n is reported, or if the time domain resource assignment field of the DCI format scheduling the PDSCH reception indicates a time domain allocation list (e.g., pdsch-TimeDomainAllocationList) entry containing a repetition number (e.g., RepNumR16), the HARQ-ACK information for the PDSCH reception from time slot n-RepNumR16+1 to time slot n is reported, otherwise the HARQ-ACK information for the PDSCH reception in time slot n is reported.

[0129] Additionally or alternatively, to transmit ACK / NACK 420 using a type 2 HARQ-ACK codebook, the HARQ-ACK bits for a dynamic or SPS PDSCH with repetitions may correspond to PDCCH monitoring occasions based on a feedback timing indicator field value (K1) (e.g., a PDSCH to HARQ feedback timing indicator field value), a slot offset (K0), and a PDSCH repetition number (e.g., pdsch-AggregationFactor or RepNumR16) (when provided). That is, for a type 2 HARQ-ACK codebook in an uplink control channel (e.g., PUCCH), UE 115 may determine a monitoring opportunity for a PDCCH with a DCI format that schedules PDSCH reception or SPS PDSCH release on an active DL BWP of serving cell c, and for the monitoring opportunity, the UE transmits HARQ-ACK information in the same PUCCH in time slot n in response to the PDSCH reception or SPS PDSCH release based on K1 (e.g., PDSCH to HARQ feedback timing indicator field value) for PUCCH transmission with HARQ-ACK information in time slot n, and based on K0 (time slot offset) provided by the time domain resource assignment field in the DCI format that schedules PDSCH reception or SPS PDSCH release, and an aggregation factor or repetition number (e.g., pdsch-AggregationFactor or RepNumR16) (when provided).

[0130] Similarly, the acknowledgement feedback 401 may include a PDCCH 425 transmitted by the base station 105, wherein the PDCCH 425 schedules a repeated PDSCH set 430. The repeated PDSCH set 430 may include a repetition of the PDSCH 435 (as described with reference to FIG. Figure 2 As described, for example, as indicated by a group aggregation factor pdsch-AggregationFactor_group or a group repetition number RepNum_group), such as a first PDSCH 435-a (e.g., a first repetition), a second PDSCH 435-b (e.g., a second repetition), a third PDSCH 435-c (e.g., a third repetition), and a fourth PDSCH 435-d (e.g., a fourth repetition). Additionally, the PDCCH 425 may also include an indication of a slot offset K0 and a feedback timing indicator field value K1 (e.g., a PDSCH to HARQ feedback timing indicator field value). However, the PDSCH 435 may be a group common PDSCH (e.g., a group common downlink shared channel) transmitted to multiple UEs 115, rather than as described with reference to Figure 4A Unicast PDSCH described.

[0131] Additionally, the acknowledgment feedback 401 may include a gap 440 between each repetition of the PDSCH 435 (eg, as described with reference to FIG. 4 ). Figure 3B As described). Based on gap 440 and if the fourth PDSCH 435-d occurs in time slot n, the first PDSCH 435-a may occur in the time slot given by (n-3(1+gap)), the second PDSCH 435-b may occur in the time slot given by (n-2(gap+1)), and the third PDSCH 435-c may appear in the time slot given by (n-(gap+1)). Subsequently, one of the plurality of UEs 115 may transmit an ACK / NACK 445 to indicate whether the UE 115 successfully received and decoded the PDSCH 435 using the repeated PDSCH set 430 (e.g., after K1).

[0132] Additionally, the UE 115 may use a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook when transmitting ACK / NACK 445 for the group-common repeated PDSCH set 430 (e.g., multicast data). For example, if a type 1 HARQ-ACK codebook is configured for the group-common PDSCH 435 and if the group-common PDSCH 435 is configured with semi-static repetition (e.g., as described with reference to FIG. Figure 2 described), then the M for candidate PDSCH reception A,c The set of opportunities can be determined as the time slot to time slot n, where:

[0133]

[0134] Right now The maximum value of the group aggregation factor (e.g., pdsch-AggregationFactor) and the gap 440 in the configuration of the group-common dynamic PDSCH and the group-common SPS PDSCH with associated G-RNTI and G-CS-RNTI (e.g., corresponding to the same service) in the same BWP may be indicated. At each gap opportunity, the UE 115 may be configured to send a NACK, repeat an ACK / NACK based on PDSCH reception, or send nothing.

[0135] Additionally or alternatively, if a Type 1 HARQ-ACK codebook is configured for the group-common PDSCH 435 and if the group-common PDSCH 435 is configured with dynamic repetition (e.g., as described with reference to Figure 2 As described), UE 115 may determine that PDSCH reception is from time slot to time slot n, where:

[0136]

[0137] In some cases, For example, if the TDRA table for the group-common PDSCH has a row including the group repetition number (eg, RepNum_group), PDSCH repetition configured via the group aggregation factor (eg, pdsch-AggregationFactor_group) may not be applied.

[0138] Additionally or alternatively, if a type 2 HARQ-ACK codebook is configured for the group-common PDSCH 435, the PDCCH monitoring timing on the active downlink BWP of the serving cell may be determined by K1 (e.g., the PDSCH to HARQ Feedback Timing Indicator field value between the last repetition of the group-common PDSCH 435 and the PUCCH carrying the ACK / NACK 445), K0 (e.g., the slot offset between the PDCCH 425 and the first repetition of the group-common PDSCH 435), the number of repetitions for the group-common PDSCH (e.g., given by pdsch-AggregationFactor_group or RepNum_group), and the gap 440 (e.g., if configured). If the group-common PDSCH 435 is configured with a semi-static repetition scheme, the PDCCH monitoring timing may be based on K1, K0, and (pdsch-AggregationFactor_group + (pdsch-AggregationFactor_group-1) gap). Alternatively, if the group-common PDSCH 435 is configured with a dynamic repetition scheme, the PDCCH monitoring occasion may be based on K1, K0, and (RepNum_group+(RepNum_group-1) gap).

[0139] Figure 5 An example of a process flow 500 for supporting a configuration of a group shared downlink channel with duplication according to aspects of the present disclosure is illustrated. The process flow 500 may implement aspects of the wireless communication systems 100 and 200. For example, the process flow 500 may include a base station 105-b and a UE 115-d, which may be represented as described above with reference to Figure 1-4B Examples of corresponding base stations 105 and UEs 115 are described.

[0140] In the following description of process flow 500, the operations between base station 105-b and UE 115-d may be presented in a different order than the exemplary order shown, or the operations performed by base station 105-b and UE 115-d may be performed in a different order or at a different time. Certain operations may also be excluded from process flow 500, or other operations may be added to process flow 500. It will be understood that although base station 105-b and UE 115-d are shown as performing several operations of process flow 500, any wireless device may perform the operations shown.

[0141] At 505, the base station 105-b may determine a number of repetitions for a group-common downlink shared channel, which includes one or more downlink shared channels (e.g., one or more dynamic downlink shared channels, dynamic PDSCH, etc.), one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof.

[0142] UE 115-d may receive a repetitive configuration for a group common downlink shared channel from base station 105-b at 510. In some implementations, the repetitive configuration may include a group RNTI indicating that the group common downlink shared channel is transmitted to the set of UEs 115 including at least UE 115-d.

[0143] In some implementations, the UE 115-d may receive a semi-static repetition configuration for the repetition configuration from the base station 105-b. For example, the semi-static repetition configuration may include a group clustering factor, where the number of repetitions is determined based on the group clustering factor and a group common downlink shared channel. In some implementations, the group clustering factor for one or more group common downlink shared channels or one or more semi-persistent group common downlink shared channels may be predefined as one. Additionally or alternatively, the UE 115-d may determine a group clustering factor for one or more semi-persistent group common downlink shared channels based on the group clustering factor for one or more group common downlink shared channels, where the one or more group common downlink shared channels include a group RNTI associated with the one or more semi-persistent group common downlink shared channels. In some implementations, the UE 115-d may determine a group clustering factor for one or more group common downlink shared channels with a group RNTI based on a clustering factor for a unicast downlink shared channel configured to the UE 115-d.

[0144] Additionally or alternatively, UE 115-d may receive a dynamic repetition configuration for the repetition configuration from base station 105-b. In some implementations, the dynamic repetition configuration may include a group repetition number parameter indicated via TDRA, wherein the repetition number is determined based on the group repetition number parameter.

[0145] At 515, UE 115-d may receive a gap configuration from base station 105-b, the gap configuration including an indication of gaps that occur between repetitions of the group common downlink shared channel. For example, UE 115-d may receive the gap configuration from base station 105-b semi-statically via RRC signaling, dynamically via a TDRA indication including a gap value for the gap, or a combination thereof. In some implementations, the gap may include a number of time slots between each repetition of the group common downlink shared channel, where the length of each time slot is based on the configuration of the BWP used to carry the group common downlink shared channel. Additionally, the gap may be configured independently for one or more downlink shared channels and one or more semi-persistent downlink shared channels. In some implementations, the number of repetitions combined with the gap between repetitions may not exceed the periodicity configured for the semi-persistent downlink shared channel.

[0146] At 520 , UE 115 - d may determine a number of repetitions for the group common downlink shared channel based on the repetition configuration.

[0147] At 525 , UE 115 - d may monitor the group common downlink shared channel from the base station based on the determined number of repetitions.

[0148] At 530 , the base station 105 - b may transmit the group common downlink shared channel to one or more UEs 115 , including UE 115 - b , based on the determined number of repetitions.

[0149] At 535, UE 115-d may transmit an acknowledgment feedback message for the group common downlink shared channel based on the monitoring to base station 105-b, wherein the acknowledgment feedback message indicates successful or unsuccessful reception of the group common downlink shared channel based on the number of repetitions. In some implementations, UE 115-d may receive a configuration of a type 1 acknowledgment codebook from base station 105-b for transmitting the acknowledgment feedback message. Accordingly, UE 115-d may determine a set of opportunities for monitoring the group common downlink shared channel based on the number of repetitions and a gap value representing a gap between each repetition of the group common downlink shared channel, and may transmit a single acknowledgment feedback message for the set of opportunities to base station 105-b based on the type 1 acknowledgment codebook.

[0150] Additionally or alternatively, UE 115-d may receive a configuration of a type 2 acknowledgment codebook from base station 105-b for transmitting an acknowledgment feedback message. Accordingly, UE 115-d may determine a set of opportunities for monitoring the group common downlink shared channel based on a feedback timing indicator field value (e.g., K1) between the last repetition of the group common downlink shared channel and the acknowledgment feedback message, an offset value (e.g., K0) between a downlink control channel carrying the repetition configuration and the first repetition of the group common downlink shared channel, a number of repetitions, a gap value indicating a gap between each repetition of the group common downlink shared channel, or a combination thereof. Subsequently, UE 115-d may transmit acknowledgment feedback messages for multiple opportunities to base station 105-b based on the type 2 acknowledgment codebook.

[0151] Figure 6 A block diagram 600 is shown of a device 605 that supports configuration for a group common downlink channel with duplication according to aspects of the present disclosure. The device 605 can 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 be in communication with each other (e.g., via one or more buses).

[0152] Receiver 610 may provide a means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to configurations for group-shared downlink channels with repetition), user data, control information, or any combination thereof. The information may be communicated to other components of device 605. Receiver 610 may utilize a single antenna or a collection of multiple antennas.

[0153] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to size-based neural network selection for autoencoder-based communication), user data, control information, or any combination thereof. In some examples, the transmitter 615 may be co-located with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0154] 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 the configuration for a group common downlink channel with duplication as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or various components thereof, may support methods for performing one or more functions described herein.

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

[0156] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof, or components thereof, may be implemented by 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 thereof, or components thereof, may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured or otherwise supporting an apparatus for performing the functions described herein).

[0157] In some examples, the communication manager 620 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise coordinating with the receiver 610, the transmitter 615, or both. For example, the communication manager 620 can receive information from the receiver 610, send information to the transmitter 615, or be integrated in conjunction with the receiver 610, the transmitter 615, or both to receive information, transmit information, or perform various other operations described herein.

[0158] 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 or otherwise support means for receiving, from a base station, a repetition configuration for a group-common downlink shared channel, the group-common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof. The communication manager 620 may be configured to or otherwise support means for determining a repetition number for the group-common downlink shared channel based on the repetition configuration. The communication manager 620 may be configured to or otherwise support means for monitoring the group-common downlink shared channel from the base station based on the determined repetition number.

[0159] By including or configuring the communication manager 620 according to examples as described herein, the device 605 (e.g., a processor controlling or otherwise coupled to the receiver 610, the transmitter 615, the communication manager 620, or a combination thereof) can support techniques for enhancing the reliability of group common messages. For example, repetitions for a group common downlink shared channel can increase the likelihood that the UE 115 successfully receives and decodes the group common downlink shared channel (e.g., by combining different repetitions of the group common downlink shared channel).

[0160] Figure 7 A block diagram 700 of a device 705 supporting configuration for a group common downlink channel with duplication according to aspects of the present disclosure is shown. The device 705 can 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 be in communication with each other (e.g., via one or more buses).

[0161] Receiver 710 may provide a means for receiving information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to a configuration for a group common downlink channel with repetition), user data, control information, or any combination thereof. The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0162] The transmitter 715 may provide a means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to size-based neural network selection for autoencoder-based communication), user data, control information, or any combination thereof. 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.

[0163] Device 705 or its various components may be examples of means for performing various aspects of configuration for a group common downlink channel with repetition as described herein. For example, communications manager 720 may include a repetition configuration component 725, a repetition determination component 730, a group common downlink shared channel monitoring component 735, or any combination thereof. Communications manager 720 may be an example of various 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, monitor, transmit) using receiver 710, transmitter 715, or both, or otherwise in cooperation with receiver 310, transmitter 315, or both. For example, communications manager 720 may receive information from receiver 710, send information to transmitter 715, or be integrated with receiver 710, transmitter 715, or both to receive information, transmit information, or perform various other operations described herein.

[0164] According to examples disclosed herein, a communication manager 720 can support wireless communications at a UE. A repetition configuration component 725 can be configured to or otherwise support means for receiving a repetition configuration for a group common downlink shared channel from a base station, the group common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof. A repetition determination component 730 can be configured to or otherwise support means for determining a repetition number for the group common downlink shared channel based on the repetition configuration. A group common downlink shared channel monitoring component 735 can be configured to or otherwise support means for monitoring the group common downlink shared channel from the base station based on the determined repetition number.

[0165] Figure 8 A block diagram 820 of a communication manager 820 supporting configuration for a group common downlink channel with repetition is shown in accordance with aspects of the present disclosure. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both described herein. The communication manager 820 or its various components may be examples of means for performing aspects of configuration for a group common downlink channel with repetition as described herein. For example, the communication manager 820 may include a repetition configuration component 825, a repetition determination component 830, a group common downlink shared channel monitoring component 835, a semi-static repetition component 840, a dynamic repetition component 845, a gap configuration component 850, an acknowledgment feedback component 855, or any combination thereof. Each of these components may communicate directly or indirectly with one another (e.g., via one or more buses).

[0166] According to examples disclosed herein, a communication manager 820 can support wireless communications at a UE. A repetition configuration component 825 can be configured to or otherwise support means for receiving a repetition configuration for a group common downlink shared channel from a base station, the group common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof. A repetition determination component 830 can be configured to or otherwise support means for determining a repetition number for the group common downlink shared channel based on the repetition configuration. A group common downlink shared channel monitoring component 835 can be configured to or otherwise support means for monitoring the group common downlink shared channel from the base station based on the determined repetition number.

[0167] In some examples, to support receiving a group common configuration for a downlink shared channel, semi-static repetition component 840 may be configured as or otherwise support means for receiving a semi-static repetition configuration for repetition configuration from a base station.

[0168] In some examples, to support receiving a semi-static repetition configuration, semi-static repetition component 840 may be configured as or otherwise support means for receiving the semi-static repetition configuration from a base station via radio resource control signaling.

[0169] In some examples, the semi-static repetition component 840 can be configured as or otherwise support means for a semi-static repetition configuration including a group gathering factor, wherein the number of repetitions is determined based on the group gathering factor and a group common downlink shared channel.

[0170] In some examples, the semi-static repetition component 840 can be configured or otherwise support an arrangement in which the group gathering factor for one or more group-common downlink shared channels or one or more semi-persistent group-common downlink shared channels is predefined as one.

[0171] In some examples, the semi-static repetition component 840 may be configured to or otherwise support means for determining a group gathering factor for one or more semi-persistent group common downlink shared channels based on a group gathering factor for one or more group common downlink shared channels, wherein the repetition configuration includes a group radio network temporary identifier associated with the one or more semi-persistent group common downlink shared channels.

[0172] In some examples, the semi-static repetition component 840 may be configured as or otherwise support means for determining a group aggregation factor for one or more group shared downlink shared channels having a group radio network temporary identifier based on the aggregation factor of the unicast downlink shared channel configured to the UE.

[0173] In some examples, to support receiving a configuration for a downlink shared channel, the dynamic repetition component 845 may be configured as or otherwise support means for receiving a dynamic repetition configuration for the repetition configuration from a base station.

[0174] In some examples, the dynamic repetition component 845 may be configured as or otherwise support means for dynamic repetition configuration including a group repetition number parameter indicated via a time domain resource allocation, wherein the repetition number is determined based on the group repetition number parameter.

[0175] In some examples, gap configuration component 850 may be configured as or otherwise support means for receiving a gap configuration from a base station, the gap configuration including an indication of gaps occurring between repetitions of a group common downlink shared channel.

[0176] In some examples, to support receiving gap configurations, gap configuration component 850 may be configured as or otherwise support means for receiving gap configurations from a base station semi-statically via radio resource control signaling, dynamically via a time-domain resource allocation indication including a gap value for the gap, or a combination thereof.

[0177] In some examples, the gap configuration component 850 may be configured to or otherwise support means for gaps comprising a number of time slots between each repetition of a group common downlink shared channel, wherein the length of each time slot is based on a configuration of a portion of the bandwidth used to carry the group common downlink shared channel.

[0178] In some examples, gap configuration component 850 can be configured to or otherwise support means for gaps that are independently configured for one or more downlink shared channels and for one or more semi-persistent downlink shared channels.

[0179] In some examples, gap configuration component 850 can be configured to or otherwise support means for the number of repetitions combined with the gaps between repetitions to not exceed a periodicity configured for a semi-persistent downlink shared channel.

[0180] In some examples, the confirmation feedback component 855 may be configured as or otherwise support a device for transmitting a confirmation feedback message for a group common downlink shared channel to a base station based on monitoring, wherein the confirmation feedback message indicates successful or unsuccessful reception of the group common downlink shared channel based on a number of repetitions.

[0181] In some examples, the acknowledgment feedback component 855 may be configured as or otherwise support means for receiving configuration of a type 1 acknowledgment codebook for transmitting acknowledgment feedback messages from a base station.

[0182] In some examples, the acknowledgment feedback component 855 can be configured as or otherwise support means for determining a set of multiple opportunities for monitoring the group common downlink shared channel based on the number of repetitions and a gap value representing a gap between each repetition of the group common downlink shared channel. In some examples, the acknowledgment feedback component 855 can be configured as or otherwise support means for transmitting a single acknowledgment feedback message for the set of multiple opportunities to the base station based on a type 1 acknowledgment codebook.

[0183] In some examples, the acknowledgment feedback component 855 may be configured as or otherwise support means for receiving configuration of a type 2 acknowledgment codebook for transmitting acknowledgment feedback messages from a base station.

[0184] In some examples, the acknowledgment feedback component 855 may be configured to or otherwise support means for determining a set of multiple opportunities for monitoring the group common downlink shared channel based on a feedback timing indicator field value between a last repetition of the group common downlink shared channel and an acknowledgment feedback message, an offset value between a downlink control channel carrying a repetition configuration and a first repetition of the group common downlink shared channel, a number of repetitions, a gap value representing a gap between each repetition of the group common downlink shared channel, or a combination thereof. In some examples, the acknowledgment feedback component 855 may be configured to or otherwise support means for transmitting an acknowledgment feedback message for the set of multiple opportunities to the base station based on a type 2 acknowledgment codebook.

[0185] In some examples, the reconfiguration component 825 may be configured as or otherwise support means for reconfiguring a configuration including a group radio network temporary identifier indicating that a group common downlink shared channel is transmitted to a set of multiple UEs including at least the UE.

[0186] Figure 9A diagram of a system 900 including a device 905 supporting a configuration for a group-shared downlink channel with duplication, according to various aspects of the present disclosure, is shown. The device 905 may be an example of, or include a component of, a device 605, a device 705, or a UE 115 as described herein. The device 905 may wirelessly communicate with one or more base stations 105, UEs 115, or any combination thereof. The device 905 may include components for two-way voice and data communication, including components for transmitting and receiving communications, including a communication manager 920, an I / O controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0187] 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 or another known operating system. In some other cases, 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.

[0188] 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 transmitting or receiving multiple wireless transmissions concurrently. The transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired or wireless link, 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 to modulate packets and provide the modulated packets to one or more antennas 925 for transmission, and to demodulate packets received from 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, transmitter 715, receiver 610, receiver 710, or any combination thereof, or components thereof, as described herein.

[0189] 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 other types of memory. In some cases, the code 935 may not be directly executed by the processor 940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, the memory 930 may include, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0190] 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, a discrete gate or transistor logic component, a discrete hardware component, 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., memory 930) so that the device 905 performs various functions (e.g., supporting various functions or tasks for a configuration with a repeated group shared downlink channel). For example, the device 905 or a component of the device 905 may include a processor 940 and a memory 930 coupled to the processor 940, the processor 940 and the memory 930 being configured to perform the various functions described herein.

[0191] 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 or otherwise support means for receiving, from a base station, a repetition configuration for a group-common downlink shared channel, the group-common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof. The communication manager 920 may be configured to or otherwise support means for determining a repetition number for the group-common downlink shared channel based on the repetition configuration. The communication manager 920 may be configured to or otherwise support means for monitoring the group-common downlink shared channel from the base station based on the determined repetition number.

[0192] By including or configuring the communication manager 920 according to the examples described herein, the device 905 can support techniques for improved communication reliability and improved inter-device coordination. For example, the number of repetitions for a group-shared downlink shared channel can increase the reliability that the processor of the device 905 can fully receive the group-shared downlink shared channel. Additionally, the repetition configuration from the base station can enable the processor to determine how to monitor and receive the group-shared downlink shared channel.

[0193] In some examples, the communication manager 920 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating 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, memory 930, 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 the configuration for a group common downlink channel with duplication as described herein, or the processor 940 and memory 930 can be otherwise configured to perform or support such operations.

[0194] Figure 10 A block diagram 1000 is shown of a device 1005 that supports configuration for a group common downlink channel with duplication according to aspects of the present disclosure. The device 1005 can be an example of aspects of a base station 105 as described herein. The device 1005 can include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 can also include a processor. Each of these components can be in communication with each other (e.g., via one or more buses).

[0195] Receiver 1010 may provide a means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to configurations for group-shared downlink channels with repetition), user data, control information, or any combination thereof. The information may be passed to other components of device 1005. Receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0196] The transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to size-based neural network selection for autoencoder-based communication), user data, control information, or any combination thereof. In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0197] 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 the configuration for a group common downlink channel with duplication 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 functions described herein.

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

[0199] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may be implemented by 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 thereof, or components thereof, may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured or otherwise supporting an apparatus for performing the functions described herein).

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

[0201] According to examples disclosed herein, the communication manager 1020 can support wireless communications at a base station. For example, the communication manager 1020 can be configured to or otherwise support means for determining a repetition number for a group-common downlink shared channel, the group-common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels distinct from the one or more downlink shared channels, or a combination thereof. The communication manager 1020 can be configured to or otherwise support means for transmitting a repetition configuration for the group-common downlink shared channel to one or more user equipment (UEs), the repetition configuration comprising an indication of the determined repetition number. The communication manager 1020 can be configured to or otherwise support means for transmitting the group-common downlink shared channel to the one or more UEs based on the determined repetition number.

[0202] Figure 11 A block diagram 1100 is shown of a device 1105 that supports configuration for a group common downlink channel with duplication according to aspects of the present disclosure. The device 1105 can be an example of aspects of the device 1005 or base station 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 be in communication with each other (e.g., via one or more buses).

[0203] Receiver 1110 may provide a means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to configurations for group-shared downlink channels with repetition), user data, control information, or any combination thereof. The information may be communicated to other components of device 1105. Receiver 1110 may utilize a single antenna or a collection of multiple antennas.

[0204] The transmitter 1115 may provide a means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information such as packets associated with various information channels (e.g., a control channel, a data channel, an information channel related to size-based neural network selection for autoencoder-based communication), user data, control information, or any combination thereof. In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0205] Device 1105 or its various components may be examples of means for performing various aspects of configuring a group-shared downlink channel with repetitions as described herein. For example, communications manager 1120 may include a repetition number determining component 1125, a repetition configuration indicating component 1130, a group-shared downlink shared channel component 1135, or any combination thereof. Communications manager 1120 may be an example of various 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, monitor, transmit) using, or otherwise in cooperation with, receiver 1110, transmitter 1115, or both. For example, communications manager 1120 may receive information from receiver 1110, send information to transmitter 1115, or be integrated with receiver 1110, transmitter 1115, or both to receive information, transmit information, or perform various other operations described herein.

[0206] According to examples disclosed herein, a communication manager 1120 can support wireless communications at a base station. A repetition number determining component 1125 can be configured to or otherwise support means for determining a repetition number for a group-common downlink shared channel, the group-common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels distinct from the one or more downlink shared channels, or a combination thereof. A repetition configuration indicating component 1130 can be configured to or otherwise support means for transmitting a repetition configuration for the group-common downlink shared channel to one or more user equipment (UEs), the repetition configuration comprising an indication of the determined repetition number. A group-common downlink shared channel component 1135 can be configured to or otherwise support means for transmitting the group-common downlink shared channel to the one or more UEs based on the determined repetition number.

[0207] Figure 12A block diagram 1200 is shown of a communication manager 1220 that supports configuration of a group common downlink channel with repetitions, in accordance with aspects of the present disclosure. The communication manager 1220 can be an example of aspects of the communication manager 1020, the communication manager 1120, or both described herein. The communication manager 1220 or its various components can be examples of apparatuses for performing aspects of configuration of a group common downlink channel with repetitions, as described herein. For example, the communication manager 1220 can include a repetition number determination component 1225, a repetition configuration indication component 1230, a group common downlink shared channel component 1235, a semi-static repetition indication component 1240, a dynamic repetition indication component 1245, a gap configuration indication component 1250, an acknowledgment component 1255, or any combination thereof. Each of these components can communicate directly or indirectly with one another (e.g., via one or more buses).

[0208] According to examples disclosed herein, a communication manager 1220 can support wireless communications at a base station. A repetition number determining component 1225 can be configured to or otherwise support means for determining a repetition number for a group-common downlink shared channel, the group-common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels distinct from the one or more downlink shared channels, or a combination thereof. A repetition configuration indicating component 1230 can be configured to or otherwise support means for transmitting a repetition configuration for the group-common downlink shared channel to one or more user equipment (UEs), the repetition configuration comprising an indication of the determined repetition number. A group-common downlink shared channel component 1235 can be configured to or otherwise support means for transmitting the group-common downlink shared channel to the one or more UEs based on the determined repetition number.

[0209] In some examples, to support transmitting a group common configuration for a downlink shared channel, the semi-static repetition indication component 1240 may be configured as or otherwise support means for transmitting a semi-static repetition configuration for repetition configuration to one or more UEs.

[0210] In some examples, to support transmitting a semi-static repeat configuration, the semi-static repeat indication component 1240 may be configured as or otherwise support means for transmitting the semi-static repeat configuration to one or more UEs via radio resource control signaling.

[0211] In some examples, the semi-static repetition indication component 1240 may be configured as or otherwise support means for a semi-static repetition configuration including a group aggregation factor, wherein the number of repetitions is indicated based on the group aggregation factor and a group common downlink shared channel.

[0212] In some examples, to support transmitting a configuration for a downlink shared channel, the dynamic repetition indication component 1245 may be configured as or otherwise support means for transmitting a dynamic repetition configuration for the repetition configuration to one or more UEs.

[0213] In some examples, the dynamic repetition indication component 1245 may be configured as or otherwise support means for dynamic repetition configuration including a group repetition number parameter indicated via a time domain resource allocation, wherein the repetition number is indicated based on the group repetition number parameter.

[0214] In some examples, gap configuration indicating component 1250 may be configured as or otherwise support means for transmitting a gap configuration to one or more UEs, the gap configuration comprising an indication of gaps occurring between repetitions of a group common downlink shared channel.

[0215] In some examples, to support transmitting gap configuration, gap configuration indication component 1250 may be configured as or otherwise support means for transmitting the gap configuration to one or more UEs semi-statically via radio resource control signaling, dynamically via a time domain resource allocation indication including a gap value for the gap, or a combination thereof.

[0216] In some examples, the gap configuration indication component 1250 may be configured to or otherwise support means for gaps comprising a number of time slots between each repetition of a group common downlink shared channel, wherein the length of each time slot is based on a configuration of a portion of the bandwidth used to carry the group common downlink shared channel.

[0217] In some examples, gap configuration indicating component 1250 can be configured to or otherwise support means for gaps that are independently configured for one or more downlink shared channels and for one or more semi-persistent downlink shared channels.

[0218] In some examples, gap configuration indicating component 1250 can be configured or otherwise support means for the number of repetitions combined with the gaps between repetitions to not exceed a periodicity configured for a semi-persistent downlink shared channel.

[0219] In some examples, the confirmation component 1255 may be configured as or otherwise support a device for receiving an confirmation feedback message for the group common downlink shared channel from one or more UEs based on transmitting the group common downlink shared channel, wherein the confirmation feedback message indicates successful reception or unsuccessful reception of the group common downlink shared channel based on a repetition number.

[0220] In some examples, the confirmation component 1255 may be configured as or otherwise support a device for transmitting a configuration of a type 1 confirmation codebook for one or more UEs to transmit an confirmation feedback message, where the confirmation feedback message is received based on the type 1 confirmation codebook.

[0221] In some examples, the confirmation component 1255 may be configured as or otherwise support a device for transmitting a configuration of a type 2 confirmation codebook for one or more UEs to transmit an confirmation feedback message, where the confirmation feedback message is received based on the type 2 confirmation codebook.

[0222] In some examples, the reconfiguration indicating component 1230 may be configured as or otherwise support means for reconfiguring a reconfiguration including a group radio network temporary identifier indicating that a group common downlink shared channel is transmitted to one or more UEs.

[0223] Figure 13 A diagram of a system 1300 including a device 1305 supporting a configuration for a group-shared downlink channel with duplication, according to aspects of the present disclosure, is shown. Device 1305 may be an example of, or include components of, device 1005, device 1105, or base station 105 as described herein. Device 1305 may wirelessly communicate with one or more base stations 105, UEs 115, or any combination thereof. Device 1305 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communications manager 1320, a network communications manager 1310, a transceiver 1315, an antenna 1325, memory 1330, code 1335, a processor 1340, and an inter-station communications manager 1345. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1350).

[0224] The network communications manager 1310 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1310 may manage the delivery of data communications for client devices, such as one or more UEs 115.

[0225] In some cases, the device 1305 may include a single antenna 1325. However, in some other cases, the device 1305 may have more than one antenna 1325, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1315 may communicate bidirectionally via one or more antennas 1325, a wired or wireless link, as described herein. For example, the transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1315 may also include a modem to modulate packets and provide the modulated packets to one or more antennas 1325 for transmission, and to demodulate packets received from one or more antennas 1325. The transceiver 1315, or the transceiver 1315 and one or more antennas 1325, may be examples of the transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof, or components thereof, as described herein.

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

[0227] The processor 1340 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, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1340 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 1340. The processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause the device 1305 to perform various functions (e.g., supporting various functions or tasks for a configuration with a repeated group shared downlink channel). For example, the device 1305 or a component of the device 1305 may include a processor 1340 and a memory 1330 coupled to the processor 1340, the processor 1340 and the memory 1330 being configured to perform the various functions described herein.

[0228] The inter-site communication manager 1345 can manage communications with other base stations 105 and can include a controller or scheduler for controlling communications with the UE 115 in cooperation with the other base stations 105. For example, the inter-site communication manager 1345 can coordinate the scheduling of transmissions to the UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, the inter-site communication manager 1345 can provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between the base stations 105.

[0229] According to examples disclosed herein, the communication manager 1320 may support wireless communications at a base station. For example, the communication manager 1320 may be configured to or otherwise support means for determining a repetition number for a group-shared downlink shared channel, the group-shared downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels distinct from the one or more downlink shared channels, or a combination thereof. The communication manager 1320 may be configured to or otherwise support means for transmitting a repetition configuration for the group-shared downlink shared channel to one or more user equipment (UEs), the repetition configuration comprising an indication of the determined repetition number. The communication manager 1320 may be configured to or otherwise support means for transmitting the group-shared downlink shared channel to the one or more UEs based on the determined repetition number.

[0230] In some examples, communication manager 1320 can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with transceiver 1315, one or more antennas 1325, or any combination thereof. Although communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to communication manager 1320 can be supported or performed by processor 1340, memory 1330, code 1335, or any combination thereof. For example, code 1335 can include instructions executable by processor 1340 to cause device 1305 to perform various aspects of a configuration for a group common downlink channel with duplication as described herein, or processor 1340 and memory 1330 can be otherwise configured to perform or support such operations.

[0231] Figure 14 A flow chart illustrating a method 1400 for supporting a configuration for a group shared downlink channel with duplication according to aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE or components thereof as described with reference to FIG. 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.

[0232] At 1405, the method may include receiving, from a base station, a repetitive configuration for a group common downlink shared channel, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof. The operations of 1405 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1405 may be performed as described with reference to Figure 8 The described repetitive configuration component 825 is executed.

[0233] At 1410, the method may include determining a number of repetitions for the group common downlink shared channel based on the repetition configuration. The operations of 1410 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1410 may be as described with reference to Figure 8 The described duplication determination component 830 is performed.

[0234] At 1415, the method may include monitoring the group common downlink shared channel from the base station based on the determined number of repetitions. The operations of 1415 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1415 may be as described with reference to Figure 8 The described group shares a downlink shared channel monitoring component 835 for execution.

[0235] Figure 15 A flow chart illustrating a method 1500 for supporting a configuration for a group shared downlink channel with duplication according to aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE or components thereof as described with reference to FIG. Figures 1 to 9 The 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.

[0236] At 1505, the method may include receiving, from a base station, a repetitive configuration for a group common downlink shared channel, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof. The operations of 1505 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1505 may be performed as described with reference to Figure 8The described repetitive configuration component 825 is executed.

[0237] At 1510, the method may include receiving a semi-static repetition configuration for the repetition configuration from the base station. The operations of 1510 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1510 may be performed as described with reference to Figure 8 The described semi-static repetitive component 840 is executed.

[0238] At 1515, the method may include determining a number of repetitions for the group common downlink shared channel based on the repetition configuration. The operations of 1515 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1515 may be as described with reference to Figure 8 The described duplication determination component 830 is performed.

[0239] At 1520, the method may include monitoring the group common downlink shared channel from the base station based on the determined number of repetitions. The operations of 1520 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1520 may be as described with reference to Figure 8 The described group shares a downlink shared channel monitoring component 835 for execution.

[0240] Figure 16 A flow chart illustrating a method 1600 for supporting a configuration for a group shared downlink channel with duplication according to aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE or components thereof as described with reference to FIG. Figures 1 to 9 The 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.

[0241] At 1605, the method may include receiving, from a base station, a repetitive configuration for a group common downlink shared channel, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof. 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 with reference to Figure 8 The described repetitive configuration component 825 is executed.

[0242] At 1610, the method may include receiving a dynamic repetition configuration for the repetition configuration from the base station. The operations of 1610 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Figure 8The described dynamic repeat component 845 is executed.

[0243] At 1615, the method may include determining a number of repetitions for the group common downlink shared channel based on the repetition configuration. The operations of 1615 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1615 may be as described with reference to Figure 8 The described duplication determination component 830 is performed.

[0244] At 1620, the method may include monitoring the group common downlink shared channel from the base station based on the determined number of repetitions. The operations of 1620 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1620 may be as described with reference to Figure 8 The described group shares a downlink shared channel monitoring component 835 for execution.

[0245] Figure 17 A flow chart illustrating a method 1700 for supporting a configuration for a group shared downlink channel with duplication according to aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE or components thereof as described with reference to FIG. Figures 1 to 9 The 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.

[0246] At 1705, the method may include receiving, from a base station, a repetitive configuration for a group common downlink shared channel, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof. The operations of 1705 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Figure 8 The described repetitive configuration component 825 is executed.

[0247] At 1710, the method may include receiving a gap configuration from the base station, the gap configuration including an indication of gaps occurring between repetitions of the group common downlink shared channel. 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 with reference to Figure 8 The described gap configuration component 850 is performed.

[0248] At 1715, the method may include determining a number of repetitions for the group common downlink shared channel based on the repetition configuration. The operations of 1715 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1715 may be as described with reference to Figure 8 The described duplication determination component 830 is performed.

[0249] At 1720, the method may include monitoring the group common downlink shared channel from the base station based on the determined number of repetitions. The operations of 1720 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1720 may be as described with reference to Figure 8 The described group shares a downlink shared channel monitoring component 835 for execution.

[0250] Figure 18 A flow chart illustrating a method 1800 for supporting a configuration for a group shared downlink channel with duplication according to aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a UE or components thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE or components thereof as described herein. Figures 1 to 9 The 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.

[0251] At 1805, the method may include receiving, from a base station, a repetitive configuration for a group common downlink shared channel, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof. The operations of 1805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described with reference to Figure 8 The described repetitive configuration component 825 is executed.

[0252] At 1810, the method may include determining a number of repetitions for the group common downlink shared channel based on the repetition configuration. The operations of 1810 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1810 may be as described with reference to Figure 8 The described duplication determination component 830 is performed.

[0253] At 1815, the method may include monitoring the group common downlink shared channel from the base station based on the determined number of repetitions. The operations of 1815 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1815 may be as described with reference to Figure 8The described group shares a downlink shared channel monitoring component 835 for execution.

[0254] At 1820, the method may include transmitting an acknowledgment feedback message for the group common downlink shared channel to the base station based on the monitoring, wherein the acknowledgment feedback message indicates successful reception or unsuccessful reception of the group common downlink shared channel based on the number of repetitions. The operations of 1820 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Figure 8 The described acknowledgement feedback component 855 is executed.

[0255] Figure 19 A flow chart illustrating a method 1900 for supporting a configuration for a group shared downlink channel with duplication according to aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a base station or components thereof as described herein. For example, the operations of the method 1900 may be implemented by a base station or components thereof as described herein. Figures 1 to 5 and Figures 10 to 13 The described functions may be performed by the base station 105. In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may use dedicated hardware to perform various aspects of the described functions.

[0256] At 1905, the method may include determining a repetition number for a group common downlink shared channel, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof. The operations of 1905 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described with reference to Figure 12 The described repetition number determination component 1225 is executed.

[0257] At 1910, the method may include transmitting a repetition configuration for the group common downlink shared channel to one or more user equipments (UEs), the repetition configuration including an indication of the determined number of repetitions. The operations of 1910 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described with reference to Figure 12 The described repetitive configuration directs component 1230 to perform.

[0258] At 1915, the method may include transmitting the group common downlink shared channel to the one or more UEs based on the determined number of repetitions. The operations of 1915 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1915 may be as described with reference to Figure 12 The described group shares a downlink shared channel component 1235 for execution.

[0259] 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 other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0260] The following provides an overview of various examples of the present invention:

[0261] Example 1: A method for wireless communication at a user equipment (UE), comprising: receiving a repetition configuration for a group common downlink shared channel from a base station, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; determining a number of repetitions for the group common downlink shared channel based at least in part on the repetition configuration; and monitoring the group common downlink shared channel from the base station based at least in part on the determined number of repetitions.

[0262] Example 2: The method of Example 1, wherein receiving the group common configuration for the downlink shared channel comprises: receiving a semi-static repetition configuration for the repetition configuration from the base station.

[0263] Example 3: The method of Example 2, wherein receiving the semi-static repetition configuration comprises: receiving the semi-static repetition configuration from the base station via radio resource control signaling.

[0264] Example 4: The method of any one of Examples 2-3, wherein the semi-static repetition configuration includes a group clustering factor, wherein the number of repetitions is determined based at least in part on the group clustering factor and the group common downlink shared channel.

[0265] Example 5: The method of Example 4, wherein the group gathering factor for the one or more group-common downlink shared channels or the one or more semi-persistent group-common downlink shared channels is predefined as one.

[0266] Example 6: The method of any one of Examples 4 to 5 further includes: determining the group clustering factor for the one or more semi-persistent group common downlink shared channels based at least in part on the group clustering factor for the one or more group common downlink shared channels, wherein the repetitive configuration includes a group radio network temporary identifier associated with the one or more semi-persistent group common downlink shared channels.

[0267] Example 7: The method of any one of Examples 4 to 6, further comprising: determining the group clustering factor for the one or more group common downlink shared channels with a group radio network temporary identifier based at least in part on a clustering factor of a unicast downlink shared channel configured to the UE.

[0268] Example 8: The method of Example 1, wherein receiving the configuration for the downlink shared channel comprises: receiving a dynamic repetition configuration for the repetition configuration from the base station.

[0269] Example 9: The method of Example 8, wherein the dynamic repetition configuration includes a group repetition number parameter indicated via a time domain resource allocation, wherein the repetition number is determined based at least in part on the group repetition number parameter.

[0270] Example 10: The method of any of Examples 1 to 9, further comprising: receiving a gap configuration from the base station, the gap configuration comprising an indication of gaps occurring between repetitions of the group common downlink shared channel.

[0271] Example 11: The method of Example 10, wherein receiving the gap configuration comprises receiving the gap configuration from the base station semi-statically via radio resource control signaling, dynamically via a time domain resource allocation indication including a gap value for the gap, or a combination thereof.

[0272] Example 12: A method as in any of Examples 10 to 11, wherein the gap comprises a number of time slots between each repetition of the group common downlink shared channel, wherein the length of each time slot is based at least in part on the configuration of the bandwidth portion used to carry the group common downlink shared channel.

[0273] Example 13: The method of any one of Examples 10 to 12, wherein the gap is configured independently for the one or more downlink shared channels and the one or more semi-persistent downlink shared channels.

[0274] Example 14: The method of any one of Examples 10 to 13, wherein the number of repetitions combined with the gaps between the repetitions does not exceed a periodicity configured for a semi-persistent downlink shared channel.

[0275] Example 15: The method of any one of Examples 1 to 14 further includes: transmitting an acknowledgment feedback message for the group common downlink shared channel to the base station based at least in part on the monitoring, wherein the acknowledgment feedback message indicates successful reception or unsuccessful reception of the group common downlink shared channel based at least in part on the number of repetitions.

[0276] Example 16: The method of Example 15 further comprises: receiving, from the base station, a configuration of a type 1 acknowledgment codebook for transmitting the acknowledgment feedback message.

[0277] Example 17: The method of Example 16 further includes: determining multiple opportunities for monitoring the group common downlink shared channel based at least in part on the number of repetitions and a gap value representing a gap between each repetition of the group common downlink shared channel; and transmitting a single acknowledgment feedback message for the multiple opportunities to the base station based at least in part on the type 1 acknowledgment codebook.

[0278] Example 18: The method of Example 15 further comprises: receiving, from the base station, a configuration of a type 2 acknowledgment codebook for transmitting the acknowledgment feedback message.

[0279] Example 19: The method of Example 18 further includes: determining multiple opportunities for monitoring the group common downlink shared channel based at least in part on a feedback timing indicator field value between the last repetition of the group common downlink shared channel and the acknowledgment feedback message, an offset value between the downlink control channel carrying the repetition configuration and the first repetition of the group common downlink shared channel, the number of repetitions, a gap value representing a gap between each repetition of the group common downlink shared channel, or a combination thereof; and transmitting the acknowledgment feedback message for the multiple opportunities to the base station based at least in part on the type 2 acknowledgment codebook.

[0280] Example 20: The method of any one of Examples 1 to 19, wherein the recurring configuration includes a group radio network temporary identifier shared by a plurality of UEs including at least the UE.

[0281] Example 21: A method for wireless communication at a base station, comprising: determining a repetition number for a group-common downlink shared channel, the group-common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; transmitting a repetition configuration for the group-common downlink shared channel to one or more user equipment (UE), the repetition configuration comprising an indication of the determined repetition number; and transmitting the group-common downlink shared channel to the one or more UEs based at least in part on the determined repetition number.

[0282] Example 22: The method of Example 21, wherein transmitting the group common configuration for the downlink shared channel comprises: transmitting a semi-static repetition configuration for the repetition configuration to the one or more UEs.

[0283] Example 23: The method of Example 22, wherein transmitting the semi-static repetition configuration comprises transmitting the semi-static repetition configuration to the one or more UEs via radio resource control signaling.

[0284] Example 24: The method of any of Examples 22-23, wherein the semi-static repetition configuration includes a group clustering factor, wherein the number of repetitions is indicated based at least in part on the group clustering factor and the group common downlink shared channel.

[0285] Example 25: The method of Example 21, wherein transmitting the configuration for the downlink shared channel comprises transmitting a dynamic repetition configuration for the repetition configuration to the one or more UEs.

[0286] Example 26: The method of Example 25, wherein the dynamic repetition configuration comprises a group repetition number parameter indicated via a time domain resource allocation, wherein the repetition number is indicated based at least in part on the group repetition number parameter.

[0287] Example 27: The method of any one of Examples 21 to 26, further comprising: transmitting a gap configuration to the one or more UEs, the gap configuration comprising an indication of gaps occurring between repetitions of the group common downlink shared channel.

[0288] Example 28: The method of Example 27, wherein transmitting the gap configuration comprises: transmitting the gap configuration to the one or more UEs semi-statically via radio resource control signaling, dynamically via a time domain resource allocation indication including a gap value for the gap, or a combination thereof.

[0289] Example 29: A method as in any of Examples 27 to 28, wherein the gap comprises a number of time slots between each repetition of the group common downlink shared channel, wherein the length of each time slot is based at least in part on the configuration of the bandwidth portion used to carry the group common downlink shared channel.

[0290] Example 30: The method of any one of Examples 27 to 29, wherein the gap is configured independently for the one or more downlink shared channels and the one or more semi-persistent downlink shared channels.

[0291] Example 31: The method of any one of Examples 27 to 30, wherein the number of repetitions combined with the gaps between the repetitions does not exceed a periodicity configured for a semi-persistent downlink shared channel.

[0292] Example 32: The method of any one of Examples 21 to 31 further includes: receiving an acknowledgment feedback message for the group common downlink shared channel from the one or more UEs based at least in part on transmitting the group common downlink shared channel, wherein the acknowledgment feedback message indicates successful reception or unsuccessful reception of the group common downlink shared channel based at least in part on the number of repetitions.

[0293] Example 33: The method of Example 32 further comprises: transmitting a configuration of a type 1 acknowledgment codebook for the one or more UEs to transmit the acknowledgment feedback message, wherein the acknowledgment feedback message is received based at least in part on the type 1 acknowledgment codebook.

[0294] Example 34: The method of any one of Examples 32 to 33, further comprising: transmitting a configuration of a type 2 acknowledgment codebook for the one or more UEs to transmit the acknowledgment feedback message, wherein the acknowledgment feedback message is received based at least in part on the type 2 acknowledgment codebook.

[0295] Example 35: The method of any one of Examples 21 to 34, wherein the repetition configuration includes a group radio network temporary identifier indicating that the group common downlink shared channel is transmitted to the one or more UEs.

[0296] Example 36: An apparatus for wireless communication at a user equipment (UE), comprising at least one means for performing the method of any one of Examples 1 to 20.

[0297] Example 37: An apparatus for wireless communication at a user equipment (UE), comprising a processor and a memory coupled to the processor, the processor and memory configured to perform the method of any one of Examples 1 to 20.

[0298] Example 39: A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to perform the method of any one of Examples 1 to 20.

[0299] Example 40: An apparatus for wireless communication at a base station, comprising at least one means for performing the method of any of Examples 21 to 35.

[0300] Example 41: An apparatus for wireless communication at a base station, comprising a processor and a memory coupled to the processor, the processor and memory configured to perform the method of any one of Examples 21 to 35.

[0301] Example 43: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method of any of Examples 21 to 35.

[0302] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology 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.

[0303] 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 that may be referred to throughout this description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0304] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with 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. The 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).

[0305] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or code. Other examples and implementations fall 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, hardwiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0306] Computer-readable media include both non-transient computer storage media and communication media, which include any media that facilitates a computer program to be transferred from one place to another. Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer. As an example and not limitation, non-transient computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transient medium that can be used to carry or store the desired program code means of an instruction or data structure form and can be accessed by a general or special-purpose computer, or a general or special-purpose processor. Similarly, any connection is also properly referred to as a computer-readable medium. For example, if software is transmitted 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 in the definition of computer-readable media. Disk and disc, as used herein, include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0307] 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). Likewise, as used herein, the phrase "based on" should not be read as referencing a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be read in the same manner as the phrase "based at least in part on."

[0308] In the accompanying drawings, similar components or features may have the same reference number. In addition, components of the same type may be distinguished by following the reference number with a dash and a second reference number that distinguishes between the similar components. If only the first reference number is used in the specification, the description applies to any of the similar components having the same first reference number, regardless of the second reference number or other subsequent reference numbers.

[0309] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that can be implemented or fall within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not mean "better than" or "better than other examples." This 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 instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0310] 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 readily 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 is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving, from a base station, a repetitive configuration for a group common downlink shared channel, the group common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; determining a number of repetitions for the group common downlink shared channel based at least in part on the repetition configuration; as well as The group common downlink shared channel is received from the base station based at least in part on the determined number of repetitions.

2. The method of claim 1 , wherein receiving the repetitive configuration for the group-common downlink shared channel comprises: A semi-static repetition configuration for the repetition configuration is received from the base station via radio resource control signaling.

3. The method of claim 2, wherein the semi-static repetition configuration includes a group gathering factor for multicast transmission, wherein the number of repetitions is determined based at least in part on the group gathering factor and the group common downlink shared channel.

4. The method of claim 3, wherein the grouping factor for the one or more downlink shared channels or the one or more semi-persistent downlink shared channels is predefined as one.

5. The method of claim 3, further comprising: The grouping factor for the one or more semi-persistent downlink shared channels is determined based at least in part on the grouping factor for the one or more downlink shared channels, wherein the repetition configuration includes a group radio network temporary identifier associated with the one or more semi-persistent downlink shared channels.

6. The method of claim 3, further comprising: The group gathering factor for the one or more downlink shared channels having a group radio network temporary identifier is determined based at least in part on a gathering factor of a unicast downlink shared channel configured to the UE.

7. The method of claim 1 , wherein receiving the repetitive configuration for the group-common downlink shared channel comprises: A dynamic repetition configuration for the repetition configuration is received from the base station.

8. The method of claim 7, wherein the dynamic repetition configuration comprises a group repetition number parameter indicated via a time domain resource allocation, wherein the repetition number is determined based at least in part on the group repetition number parameter.

9. The method of claim 7, wherein receiving the repetitive configuration for the group-common downlink shared channel comprises: A semi-static repetition configuration for the repetition configuration is received from the base station, wherein the UE applies one of the semi-static repetition configuration or the dynamic repetition configuration.

10. The method of claim 7, wherein receiving the repetitive configuration for the group common downlink shared channel comprises: A semi-static repetition configuration for the repetition configuration is received from the base station, wherein the semi-static repetition configuration and the dynamic repetition configuration are independently configured with different group radio network temporary identifiers G-RNTIs or configured scheduled group radio network temporary identifiers G-CS-RNTIs.

11. The method of claim 1 , further comprising: A gap configuration is received from the base station, the gap configuration including an indication of gaps occurring between repetitions of the group common downlink shared channel.

12. The method of claim 11, wherein: Receiving the gap configuration includes: The gap configuration is received from the base station semi-statically via radio resource control signaling, dynamically via a time domain resource allocation indication including a gap value for the gap, or a combination thereof.

13. The method of claim 11, wherein the gap comprises a number of time slots between each repetition of the group common downlink shared channel, wherein a length of each time slot is based at least in part on a configuration of a portion of a bandwidth used to carry the group common downlink shared channel.

14. The method of claim 11, wherein the gaps are independently configured for the one or more downlink shared channels and the one or more semi-persistent downlink shared channels.

15. The method of claim 11, wherein the number of repetitions combined with the gap between the repetitions does not exceed a periodicity configured for a semi-persistent downlink shared channel.

16. The method of claim 1, further comprising: An acknowledgment feedback message for the group common downlink shared channel is transmitted to the base station based at least in part on the received group common downlink shared channel, wherein the acknowledgment feedback message indicates successful or unsuccessful reception of the group common downlink shared channel based at least in part on the number of repetitions.

17. The method of claim 16, further comprising: A configuration of a type 1 acknowledgment codebook for transmitting the acknowledgment feedback message is received from the base station.

18. The method of claim 17, further comprising: determining a plurality of opportunities for monitoring to receive the group common downlink shared channel based at least in part on the number of repetitions and a gap value representing a gap between each repetition of the group common downlink shared channel; as well as A single acknowledgment feedback message for the multiple opportunities is transmitted to the base station based at least in part on the type 1 acknowledgment codebook.

19. The method of claim 16, further comprising: A configuration of a type 2 acknowledgment codebook for transmitting the acknowledgment feedback message is received from the base station.

20. The method of claim 19, further comprising: determining a plurality of opportunities for monitoring to receive the group common downlink shared channel based at least in part on a feedback timing indicator field value between a last repetition of the group common downlink shared channel and the acknowledgment feedback message, an offset value between a downlink control channel carrying the repetition configuration and a first repetition of the group common downlink shared channel, the number of repetitions, a gap value representing a gap between each repetition of the group common downlink shared channel, or a combination thereof; as well as The acknowledgment feedback messages for the plurality of opportunities are transmitted to the base station based at least in part on the type 2 acknowledgment codebook.

21. The method of claim 1, wherein the recurring configuration comprises a group radio network temporary identifier shared by a plurality of UEs including at least the UE.

22. An apparatus for wireless communication at a user equipment (UE), comprising: one or more processors; a memory coupled to the one or more processors; as well as Instructions stored in the memory and executable by the one or more processors individually or in any combination to cause the apparatus to perform the following operations: receiving, from a base station, a repetitive configuration for a group common downlink shared channel, the group common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; determining a number of repetitions for the group common downlink shared channel based at least in part on the repetition configuration; as well as The group common downlink shared channel is received from the base station based at least in part on the determined number of repetitions.

23. The apparatus of claim 22, wherein the instructions for receiving the repetitive configuration for the group common downlink shared channel are executable by the one or more processors to cause the apparatus to: A semi-static repetition configuration for the repetition configuration is received from the base station via radio resource control signaling.

24. The apparatus of claim 23, wherein the semi-static repetition configuration comprises a group gathering factor for multicast transmission, wherein the number of repetitions is determined based at least in part on the group gathering factor and the group-common downlink shared channel.

25. The apparatus of claim 22, wherein the instructions for receiving the repetitive configuration for the group common downlink shared channel are executable by the one or more processors to cause the apparatus to: A dynamic repetition configuration for the repetition configuration is received from the base station.

26. The apparatus of claim 25, wherein the dynamic repetition configuration comprises a group repetition number parameter indicated via a time domain resource allocation, The number of repetitions is determined based at least in part on the group repetition number parameter.

27. The apparatus of claim 22, wherein the instructions for receiving the repetitive configuration for the group common downlink shared channel are executable by the one or more processors to cause the apparatus to: A semi-static repetition configuration for the repetition configuration is received from the base station, wherein the UE is configured to apply one of the semi-static repetition configuration or the dynamic repetition configuration.

28. The apparatus of claim 22, wherein the instructions for receiving the repetitive configuration for the group common downlink shared channel are executable by the one or more processors to cause the apparatus to: A semi-static repetition configuration for the repetition configuration is received from the base station, wherein the semi-static repetition configuration and the dynamic repetition configuration are independently configured with different group radio network temporary identifiers G-RNTI or configured scheduled group radio network temporary identifiers G-CS-RNTI.

29. An apparatus for wireless communication at a user equipment (UE), comprising: means for receiving, from a base station, a repetitive configuration for a group common downlink shared channel, the group common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; means for determining a number of repetitions for the group common downlink shared channel based at least in part on the repetition configuration; as well as Means for receiving the group common downlink shared channel from the base station based at least in part on the determined number of repetitions.

30. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by one or more processors, individually or in any combination, to: receiving, from a base station, a repetitive configuration for a group common downlink shared channel, the group common downlink shared channel comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof; determining a number of repetitions for the group common downlink shared channel based at least in part on the repetition configuration; and The group common downlink shared channel is received from the base station based at least in part on the determined number of repetitions.

Images