Configuration for a Repeated Group Shared Downlink Channel

Abstract

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), where the group-shared PDSCH is repeated with a repetition number. Accordingly, the UE may determine this 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, where the repetition number is indicated via a group aggregation factor. Additionally or alternatively, the group-shared PDSCH may include a dynamic repetition scheme, where the repetition number is indicated via a group repetition number. Additionally, the techniques described herein may enable a configuration for a repeated group-shared PDSCH to include a gap between each repetition of the group-shared PDSCH and enable the UE to transmit an acknowledgement feedback for the repetitions of the group-shared PDSCH.

Description

[0001] Cross-reference

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

[0003] The following relates to wireless communication, including configurations for group-common downlink channels with repetitions. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, and so on. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems (such as Long-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems), and fifth-generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems may employ 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).

[0005] A wireless multi-access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication for multiple communication devices, which may also be 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. Instead of being specifically configured for each UE, a base station may be configured for group-common transmission to multiple UEs and indicate these configurations to the multiple UEs so that the multiple UEs can monitor and receive these group-common transmissions. Efficient techniques are desired to support successful reception and decoding of group-common transmissions at multiple UEs.

[0006] Overview

[0007] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting configurations for group common downlink channels with repetitions. Generally, the described techniques provide for a user equipment (UE) to receive a configuration for a group common physical downlink shared channel (PDSCH). The configuration includes an indication that the group common PDSCH is repeated by a repetition number. For example, the group common PDSCH may include a group common dynamic PDSCH, one or more group common semi-persistent scheduling (SPS) PDSCHs, or a combination thereof. Accordingly, the UE may determine the repetition number and then monitor the group common PDSCH based on the repetition number. In some implementations, the same configuration or a different configuration may indicate a semi-static repetition scheme for the group common PDSCH, where the repetition number is indicated via a group aggregation factor. Additionally or alternatively, the same configuration or a different configuration may indicate a dynamic repetition scheme for the group common 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 (e.g., or transmission intervals of different lengths) between each repetition of the group common PDSCH, where the UE does not expect to receive additional configurations scheduling additional group common PDSCHs during the gap. The gap may be signaled semi-statically (e.g., via radio resource control (RRC) signaling) or dynamically (e.g., via a time domain resource allocation (TDRA) entry that includes the time slot). In some implementations, the UE may transmit an acknowledgement feedback for the group common PDSCH and the repetition number for the group common PDSCH. For example, the UE may use a type 1 acknowledgement codebook or a type 2 acknowledgement codebook to transmit the acknowledgement feedback. For both types, the UE may determine several candidate occasions for receiving the group common PDSCH and for determining the acknowledgement feedback. The UE may determine the several candidate occasions based on a group aggregation factor, a group repetition number, a gap between repetitions, a feedback timing indicator field value, a time slot offset, etc., where each of these factors 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, based on the repetition configuration, a repetition number for the group common downlink shared channel, and monitoring, based on the determined repetition number, the group common downlink shared channel from the base station.

[0010] Describes an apparatus for wireless communication at a UE. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive, 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; determine, based on the repetition configuration, a number of repetitions for the group common downlink shared channel; and monitor, based on the determined number of repetitions, the group common downlink shared channel from the base station.

[0011] Describes another device for wireless communication at a UE. The device 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, based on the repetition configuration, a number of repetitions for the group common downlink shared channel; and means for monitoring, based on the determined number of repetitions, the group common downlink shared channel from the base station.

[0012] Describes a non-transitory computer-readable medium storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive, 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; determine, based on the repetition configuration, a number of repetitions for the group common downlink shared channel; and monitor, based on the determined number of repetitions, the group common downlink shared channel from the base station.

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

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

[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 aggregation factor, where the repetition number can be determined based on the group aggregation 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 aggregation factor for the one or more group common downlink shared channels or the one or more semi-persistent group common downlink shared channels can 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, apparatuses, or instructions for the following actions: determining the group aggregation factor for the one or more semi-persistent group common downlink shared channels based on the group aggregation factor for the one or more group common downlink shared channels, where the repetition 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, apparatuses, or instructions for the following actions: determining the group aggregation factor for the one or more group common downlink shared channels with a group radio network temporary identifier based on the aggregation factor of the unicast downlink shared channel configured to the UE.

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

[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, where 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, apparatuses, or instructions for the following actions: receiving, from the base station, a gap configuration, the gap configuration including an indication of a gap that appears 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, apparatuses, or instructions for the following actions: 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, apparatuses (devices), and non-transitory computer-readable media described herein, the gap includes the 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 the configuration of the bandwidth part used to carry the group common downlink shared channel.

[0024] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the gap may be independently configured 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, apparatuses (devices), and non-transitory computer-readable media described herein, the number of repetitions combined with the gap between repetitions does not exceed the periodicity configured for the semi-persistent downlink shared channel.

[0026] 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: transmitting an acknowledgement feedback message for the group common downlink shared channel to the base station based on the monitoring, where the acknowledgement feedback message indicates successful 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, apparatuses, or instructions for the following actions: receiving a configuration of a type 1 acknowledgement codebook for transmitting the acknowledgement feedback message from the base station.

[0028] 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 occasions for monitoring the group common downlink shared channel based on the number of repetitions and a gap value representing the gap between each repetition of the group common downlink shared channel, and transmitting a single acknowledgement feedback message for the multiple occasions to the base station based on the type 1 acknowledgement codebook.

[0029] 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: 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 a plurality of 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 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, and transmitting, to the base station, the acknowledgment feedback message for the plurality of opportunities based on the type 2 acknowledgment codebook.

[0031] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the repetition 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 number of repetitions 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, to one or more UEs, a repetition configuration for the group common downlink shared channel, the repetition configuration including an indication of the determined number of repetitions; and transmitting, to the one or more UEs, the group common downlink shared channel based on the determined number of repetitions.

[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 may be executable by the processor to cause the apparatus to: determine a number of repetitions 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, to one or more UEs, a repetition configuration for the group common downlink shared channel, the repetition configuration including an indication of the determined number of repetitions; and transmit, to the one or more UEs, the group common downlink shared channel based on the determined number of repetitions.

[0034] Describes another device for wireless communication at a base station. The device may include: means for 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; means for transmitting to one or more UEs a repetition configuration for the group common downlink shared channel, the repetition configuration including 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] Describes a non-transitory computer-readable medium storing code for wireless communication at a base station. The code may include instructions executable by a processor to perform the following operations: 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 to one or more UEs a repetition configuration for the group common downlink shared channel, 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, apparatuses (devices), and non-transitory computer-readable media described herein, transmitting the group common configuration for the downlink shared channel may include operations, features, means, or instructions for the following actions: transmitting to the one or more UEs a semi-static repetition configuration for the repetition configuration.

[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, means, or instructions for the following actions: 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 aggregation factor, wherein the repetition number may be indicated based on the group aggregation factor and the group common downlink shared channel.

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

[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 time-domain resource allocation, where the repetition number may 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, apparatuses, or instructions for the following actions: transmitting a gap configuration to the one or more UEs, the gap configuration including an indication of a gap that occurs 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, apparatuses, or instructions for the following actions: transmitting the gap configuration to the one or more UEs semi-statically via radio resource control signaling, dynamically via time-domain resource allocation indicating a gap value for the gap, or a combination thereof.

[0043] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the gap includes the 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 the configuration of the bandwidth part used to carry the group common downlink shared channel.

[0044] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the gap may 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, apparatuses (devices), and non-transitory computer-readable media described herein, the combination of the repetition number and the gap between repetitions does not exceed the periodicity configured for the semi-persistent downlink shared channel.

[0046] 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: receiving an acknowledgement feedback message for the group common downlink shared channel from the one or more UEs based on transmitting the group common downlink shared channel, where the acknowledgement feedback message indicates successful or unsuccessful reception of the group common downlink shared channel based on the repetition number.

[0047] 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: 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 may 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, apparatuses, or instructions for the following actions: 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 may be received based on the type 2 acknowledgment codebook.

[0049] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the repetition configuration includes a group radio network temporary identifier that indicates that the group common downlink shared channel may be transmitted to the one or more UEs. Brief Description of the Drawings

[0051] Figure 1 Illustrates examples of a wireless communication system supporting a configuration of a group common downlink channel with repetition in accordance with aspects of the present disclosure.

[0052] Figure 2 Illustrates examples of a wireless communication system supporting a configuration of a group common downlink channel with repetition in accordance with aspects of the present disclosure.

[0053] Figure 3A And 3B Illustrates examples of a repetition scheme supporting a configuration of a group common downlink channel with repetition in accordance with aspects of the present disclosure.

[0054] Figure 4A And 4B Illustrates examples of acknowledgment feedback supporting a configuration of a group common downlink channel with repetition in accordance with aspects of the present disclosure.

[0055] Figure 5 Illustrates examples of a process flow supporting a configuration of a group common downlink channel with repetition in accordance with aspects of the present disclosure.

[0056] Figure 6 And 7 Shows a block diagram of a device supporting a configuration of a group common downlink channel with repetition in accordance with aspects of the present disclosure.

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

[0058] Figure 9 A diagram of a system including an apparatus supporting a configuration for a repeated group common downlink channel in accordance with aspects of the present disclosure is shown.

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

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

[0061] Figure 13 A diagram of a system including an apparatus supporting a configuration for a repeated group common downlink channel in accordance with aspects of the present disclosure is shown.

[0062] Figures 14 to 19 A flowchart depicting a method supporting a configuration for a repeated group common downlink channel in accordance with aspects of the present disclosure is shown.

[0063] Detailed Description

[0064] A user equipment (UE) and a base station may support semi-static and / or dynamic repetition of a 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 (repetition number R16) parameter, etc.) for the UE to apply to unicast dynamic PDSCH and unicast semi-persistent scheduling (SPS) PDSCH. Additionally, UEs in a wireless communication system may also support group common physical downlink control channel (PDCCH) and PDSCH (e.g., multicast data) as well as acknowledgement feedback for group common transmissions. However, time slot-level repetition configured for group common PDSCH remains to be defined.

[0065] As described herein, a UE may be configured with one or more group common PDSCHs, such as group common dynamic PDSCHs, one or more group common SPS PDSCHs, or combinations thereof, where the group common PDSCH is further configured with repetition. The one or more group common 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 common SPS PDSCHs may include a CRC scrambled by different configured scheduled G-RNTIs (G-CS-RNTIs). The SPS PDSCH may be associated with a G-CS-RNTI. In a first option of repetition, the group common PDSCH may be independently configured with a group aggregation factor (e.g., pdsch-AggregationFactor_group (pdsch-aggregation factor_group)) to indicate semi-static repetition for the group common PDSCH. Alternatively, in a second option of repetition, the group common PDSCH may be configured with a group repetition parameter (e.g., RepNum_group (repetition number_group)) to indicate the dynamic number of repetitions for the group common 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-RNTs configured to cause the same UE group to receive the same service, the UE may not be configured with both options, but for a group common PDSCH with different G-RNTs or an SPS group common PDSCH with different GCS-RNTs, different options may be configured independently. The UE may also be configured with a gap between each repetition of the group common PDSCH.

[0066] Additionally, the UE may be configured to transmit an acknowledgement feedback for a group common PDSCH with configured repetition. In some cases, the UE may use a type 1 acknowledgement codebook or a type 2 acknowledgement codebook to transmit the acknowledgement feedback. For both types, the UE may determine several candidate occasions for receiving the group common PDSCH and for determining the acknowledgement feedback. The UE may determine the several candidate occasions based on the group aggregation factor, the group repetition number, the gap between repetitions, the feedback timing indicator field value, the slot offset, etc., where each of these factors depends on which type of acknowledgement codebook is used or configured.

[0067] Aspects of the present disclosure are initially described in the context of a wireless communication system. Additionally, aspects of the present disclosure are illustrated by additional wireless communication systems, examples of repetition schemes, acknowledgement feedback configurations, and process flows. Aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flowcharts related to the configuration of a group common downlink channel with repetition.

[0068] Figure 1 An example of a wireless communication system 100 that supports configurations for a repeated group common downlink channel in accordance with aspects of the present disclosure is described. 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 LTE-Advanced (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.

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

[0070] 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 devices of different forms or with different capabilities. Some example UEs 115 are described in Figure 1 . The UEs 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, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as shown in Figure 1 .

[0071] Each base station 105 may communicate with the core network 130, or with each other, or both. For example, the base stations 105 may 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 may communicate with each other directly (e.g., directly between the base stations 105), or 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 may be or include one or more wireless links.

[0072] One or more of the base stations 105 described herein may include or may be referred to by those of ordinary skill in the art as a base transceiver station, radio base station, access point, radio transceiver, Node B, evolved Node B (eNB), next generation Node B or Gigabit Node B (any of which may be referred to as a gNB), home Node B, home evolved Node B, or other suitable terms.

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

[0074] The UE 115 described herein may be capable of communicating with various types of devices, such as other UE 115s that 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., as Figure 1 shown.

[0075] The UE 115 and the base station 105 may wirelessly communicate 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 (e.g., bandwidth part (BWP)) of a radio frequency spectrum band 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 communicating with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0076] 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 positioned according to a channel raster for discovery by UE 115. A carrier may operate in a stand-alone mode in which initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-stand-alone mode in which the connection is anchored using a different carrier (e.g., different carriers of the same or different radio access technologies).

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

[0078] A carrier may be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of several determined bandwidths of a carrier of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., the base station 105, UE 115, or both) may have a hardware configuration that supports communication on a specific carrier bandwidth, or may be configurable to support communication on one of the carrier bandwidths in a carrier bandwidth set. 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, BWP) or all of the carrier bandwidth.

[0079] The signal waveform transmitted on a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may include a symbol period (e.g., the duration of a modulated symbol) and a subcarrier, where the symbol period and the 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 the UE 115 and the higher the order of the modulation scheme, the higher the data rate of the 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 using multiple spatial layers can further increase the data rate or data integrity of the communication with the UE 115.

[0080] One or more parameter sets for a carrier may be supported, where a parameter set may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs having the same or different parameter sets. In some examples, the 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 the communication for the UE 115 may be limited to one or more active BWPs.

[0081] The time intervals of the base station 105 or the UE 115 may be expressed as multiples of a basic time unit, which may refer to, for example, a sampling period T s = 1 / (Δf max ·N f ) seconds, where Δf max may represent the maximum supported subcarrier spacing, and N f may represent the maximum supported discrete Fourier transform (DFT) size. The time intervals of the 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).

[0082] Each frame may include a plurality of consecutively numbered sub - frames or time slots, and each sub - frame or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into sub - frames, and each sub - frame 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 sub - carrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, a time slot may be further divided into multiple mini - slots each containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the sub - carrier spacing or the operating frequency band.

[0083] A sub - frame, time 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 TTI (sTTI)).

[0084] Physical channels may be multiplexed on a carrier according to various techniques. The physical control channel and the physical data channel may be multiplexed on a downlink carrier using, for example, one or more of time - division multiplexing (TDM) techniques, frequency - division multiplexing (FDM) techniques, or hybrid TDM - FDM techniques. A control region (e.g., a control resource set (CORESET)) for the physical control channel may be defined by the number of symbol periods and may extend across the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESET) may be configured for a set of UEs 115. For example, one or more of the UEs 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCE)) associated with the encoded information for a control information format with a given payload size. The search space set may include a common search space set configured to send control information to multiple UEs 115 and a UE - specific search space set for sending control information to a specific UE 115.

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

[0086] Macro cells generally cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unconstrained access by UEs 115 having a service subscription with the network provider supporting the macro cell. Small cells may be associated with lower-power base stations 105 (compared to macro cells), and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unconstrained access to UEs 115 having a service subscription with the network provider, or may provide constrained 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 communication on one or more cells using one or more component carriers.

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

[0088] In some examples, base station 105 can be movable and thus provide communication coverage for a mobile geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but 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 where different types of base stations 105 use the same or different radio access technologies to provide coverage for various geographic coverage areas 110.

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

[0090] Some UEs 115 (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices integrated with sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 can 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 geographical event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial billing.

[0091] Some UEs 115 may be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports one-way 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 the UE 115 include entering a deep sleep power-saving mode when not participating in active communication, operating on a limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type associated with a defined portion or extent (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of the carrier, or outside the carrier.

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

[0093] In some examples, the 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 the base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or may be unable to receive transmissions from the base station 105 for other reasons. In some examples, groups of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system where each UE 115 transmits to every other UE 115 in the group. In some examples, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving the base station 105.

[0094] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC can include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)), and at least one user plane entity that routes packets or interconnects to an external network (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity can manage non-access stratum (NAS) functions, such as the mobility, authentication, and bearer management of the UE 115 served by the base station 105 associated with the core network 130. User IP packets can be transmitted through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can be connected to the IP services 150 of one or more network operators. The IP services 150 can include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0095] Some network devices (such as the base station 105) can include sub-components, such as the access network entity 140, which can be an example of an access node controller (ANC). Each access network entity 140 can communicate with each UE 115 through one or more other access network transmission entities 145, which can be referred to as radio heads, intelligent radio heads, or transmit / receive points (TRPs). Each access network transmission entity 145 can include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or the base station 105 can be distributed across various network devices (e.g., radio heads and ANCs) or combined into a single network device (e.g., the base station 105).

[0096] 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, the 300 MHz to 3 GHz division is referred to as the ultra-high frequency (UHF) division or the decimeter band because the wavelengths are in the range of approximately 1 decimeter to 1 meter in length. 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 the UE 115 located indoors. Compared to transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, UHF wave transmissions can be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers).

[0097] The wireless communication system 100 can utilize both licensed and unlicensed radio frequency bands. For example, the wireless communication system 100 can adopt 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 band, devices (such as the base station 105 and the UE 115) can adopt carrier sensing for collision detection and avoidance. In some examples, the operation in the unlicensed band can be based on a carrier aggregation configuration (e.g., LAA) in coordination with a component carrier operating in a licensed band. The operation in the unlicensed spectrum can include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0098] The base station 105 or the UE 115 can be equipped with multiple antennas, which can be used to adopt techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the base station 105 or the UE 115 can be located within one or more antenna arrays or antenna panels that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays can 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 can be located at different geographical locations. The base station 105 can have an antenna array that has several rows and columns of antenna ports for beamforming that the base station 105 can use to support communication with the UE 115. Similarly, the UE 115 can have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel can support radio frequency beamforming for signals transmitted via the antenna ports.

[0099] The base station 105 or the UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques can be referred to as spatial multiplexing. For example, the transmitting device can transmit multiple signals via different antennas or different combinations of antennas. Similarly, the receiving device can receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0100] 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., transmit beam, receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via the antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. Adjustment of the signals communicated via the 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 adjustment 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).

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

[0102] Some signals (such as data signals associated with a particular receiving device) can be transmitted by the base station 105 in a single beam direction (e.g., the direction associated with the receiving device such as the UE 115). In some examples, the beam direction associated with transmission in a single beam direction can be determined based on signals transmitted in one or more beam directions. For example, the UE 115 can receive one or more signals transmitted by the base station 105 in different directions and can report to the base station 105 an indication of the signal that the UE 115 receives with the highest signal quality or other acceptable signal quality.

[0103] In some examples, transmissions made by a device (e.g., by base station 105 or 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 base station 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. Base station 105 may transmit reference signals that may or may not be precoded (e.g., cell-specific reference signal (CRS), channel state information reference signal (CSI-RS)). UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, 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 for transmitting signals multiple times in different directions (e.g., for identifying beam directions used by UE 115 for subsequent transmissions or receptions) or for transmitting signals in a single direction (e.g., for transmitting data to a receiving device).

[0104] 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 sets of receive beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different 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 a data signal). The single receive configuration may be aligned in 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).

[0105] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. On 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 for communication on logical channels. The Media Access Control (MAC) layer can perform priority handling and multiplex logical channels into transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. On the control plane, the Radio Resource Control (RRC) protocol layer can provide the establishment, configuration, and maintenance of the RRC connection that supports the radio bearers for user plane data between the UE 115 and the base station 105 or the core network 130. On the physical layer, the transport channels can be mapped to physical channels.

[0106] The UE 115 and the base station 105 can support retransmissions 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 the communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), Forward Error Correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve the throughput of the MAC layer in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support simultaneous slot HARQ feedback, where the device can provide HARQ feedback in a specific slot for data received in the previous symbols in that slot. In other cases, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.

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

[0108] For a multi-transmit receive 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 an 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 be expected 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 (repetition number-r16)), or if UE 115 is configured by a different repetition scheme (e.g., repetitionSchemeConfig-r16 (repetition scheme configuration-r16)) that is set to a specific multiplexing scheme (e.g., FDMSchemeA (FDM scheme A), FDMSchemeB (FDM scheme B), and TDMSchemeA (TDM scheme A)), then UE 115 may not be expected to be configured with a semi-static repetition indication (e.g., pdsch-AggregationFactor or PDSCH-AggregationFactor-r16 (PDSCH-aggregation factor-r16)).

[0109] Additionally, UE 115 in the wireless communication system 100 (e.g., in an RRC connected state with the base station 105 or with different wireless devices) may support a group common physical downlink control channel (PDCCH) with CRC scrambled by a common radio network temporary identifier (RNTI) to schedule a group common PDSCH, where the scrambling of the group common PDSCH is based on the same common RNTI. UE 115 may also support HARQ acknowledgement (HARQ-ACK) feedback for multicast transmission (e.g., group common messages). Additionally, UE 115 may support FDM between unicast PDSCH and group common PDSCH in a time slot based on UE capabilities. UE 115 may also support time slot level repetition for the group common PDSCH. However, the configuration of time slot level repetition for the group common PDSCH remains to be determined or decided.

[0110] The wireless communication system 100 may support efficient techniques for signaling configurations for a group-shared downlink channel (e.g., group-shared PDSCH), where the group-shared downlink channel has repetitions. For example, UE 115 may receive a configuration for the group-shared PDSCH, where the configuration includes an indication that the group-shared PDSCH is repeated by 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, 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, where the repetition number is indicated via a group aggregation factor. Additionally or alternatively, the group-shared PDSCH may include a dynamic repetition scheme, where the repetition number is indicated via a group repetition number. Additionally, the techniques described herein may enable the configuration of the group-shared PDSCH for repetition to include gaps between each repetition of the group-shared PDSCH and enable UE 115 to transmit an acknowledgement feedback (e.g., HARQ-ACK feedback) for the repetitions of the group-shared PDSCH.

[0111] Figure 2 An example of a wireless communication system 200 that supports configurations for a group-shared downlink channel with repetitions in accordance with 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, UE 115-a, UE 115-b, and UE 115-c, which may respectively represent examples of the corresponding base station 105 and UE 115 as described with reference to Figure 1 as described.

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

[0113] Additionally, the configuration for the group-shared dynamic downlink shared channel may include a CRC scrambled by a G-RNTI to indicate that the dynamic downlink shared channel is group-shared and is transmitted to multiple UEs 115. Similarly, the configuration for the group-shared SPS downlink shared channel may include a CRC scrambled by a G-CS-RNTI to indicate that the SPS downlink shared channel is group-shared and is transmitted to multiple UEs 115. The UEs 115 may be configured in different UE groups and receive different multicast services. Thus, the 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. The base station 105-a may transmit the group-shared downlink shared channel to the multiple UEs 115 via multicast transmission, broadcast transmission, or another technique that allows the base station 105-a to transmit the same message to the multiple UEs 115.

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

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

[0116] In some implementations, base station 105-a can transmit the repeated group common downlink shared channel 215 according to a semi-static repetition scheme. For example, base station 105-a can configure the repeated group common downlink shared channel 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 that of the unicast dynamic / SPS PDSCH) to indicate the repetition number of the repeated group common downlink shared channel 215. In some implementations, the group aggregation factor can be independently configured for different types from the repeated group common downlink shared channel 215. For example, a first group aggregation factor can be configured for the group common dynamic downlink shared channel, and a second group aggregation factor can be configured for the group common SPS downlink shared channel. Additionally or alternatively, the same group aggregation factor can be configured for both types of group common downlink shared channels.

[0117] The default value of the group aggregation factor for the group common dynamic downlink shared channel can be defined to be similar to the value of the unicast dynamic downlink shared channel (in which case, UEs monitoring the same group common dynamic PDSCH are configured with the same unicast dynamic downlink shared channel), or can be predefined as one (1) (e.g., one (1) instance of the group common 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 common SPS downlink shared channel can be defined to be similar to the default value of the group common dynamic downlink shared channel with a 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 be predefined as one (1).

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

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

[0120] In some implementations, gaps may appear between each repetition of the repeated group common downlink shared channel 215. Thus, 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. Techniques for configuring the gaps between times are described in Figure 3B more detail.

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

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

[0123] As previously mentioned, the repetition scheme 300 may illustrate a repeated unicast PDSCH 315 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 the configuration for the PDSCH). The PDCCH 305 may also indicate the number of repetitions that the unicast PDSCH 315 is transmitted (e.g., via pdsch-AggregationFactor or RepNumR16 as described in Figure 1 ). 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., the first repetition), a second unicast PDSCH 315-b (e.g., the second repetition), a third unicast PDSCH 315-c (e.g., the third repetition), and a fourth unicast PDSCH 315-d (e.g., the fourth repetition). Additionally, in some cases, the PDCCH 305 may include a time slot offset (K 0) indication, where the slot offset represents the number of slots (e.g., or transmission time intervals of different lengths) between the end of PDCCH 305 and the first unicast PDSCH 315-a.

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

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

[0126] 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 group-shared 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-shared SPS PDSCH (which may be associated with a different G-CS-RNTI) may have an independent configuration for periodicity, repetition, and gap. Accordingly, the repetition plus the gap 335 may be less than the periodicity configured for the associated group-shared SPS PDSCH. In some implementations, the UE 115 may not expect to receive an additional PDCCH to schedule another group-shared PDSCH with the same G-RNTI and the same HARQ process ID during the gap 335 (e.g., during the (one or more) gap slots).

[0127] Figure 4A and 4B Illustrates examples of acknowledgment feedback 400 and 401 supporting the configuration of group-shared downlink channels with repetition in accordance with aspects of the present disclosure. The acknowledgment feedback 400 and 401 may enable aspects of the wireless communication systems 100 and 200. For example, the UE 115 may use the acknowledgment feedback 400 or 401 to transmit an acknowledgment message to the base station indicating whether the downlink shared channel with repetition has been successfully received and decoded.

[0128] The acknowledgment feedback 400 may represent a unicast PDSCH repetition configuration, where the PDCCH 405 schedules a set of repeated PDSCHs 410, which includes a first unicast PDSCH 415-a (e.g., the first repetition), a second unicast PDSCH 415-b (e.g., the second repetition), a third unicast PDSCH 415-c (e.g., the third repetition), and a fourth unicast PDSCH 415-d (e.g., the fourth repetition). In some implementations, the PDCCH 405 may include an indication of a slot offset (K 0 ) that represents the number of slots (e.g., or transmission time intervals of different lengths) between the end of the PDCCH 405 and the first unicast PDSCH 415-a. Additionally, the PDCCH 405 may include a feedback indicator field value (e.g., a PDSCH-to-HARQ feedback timing indicator field value) K 1An indication that represents the number of time slots (e.g., or different length transmission time intervals) between the last-occurring PDSCH (e.g., the fourth unicast PDSCH 415-d) and the uplink channel (e.g., Physical Uplink Control Channel (PUCCH)) carrying the ACK / NACK 420 (e.g., the positive acknowledgment feedback message). The ACK / NACK 420 may include an indication of whether the UE 115 has successfully received and decoded the PDSCH 415 using the repeated PDSCH set 410.

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

[0130] Using a type 1 HARQ-ACK codebook, if the aggregation factor (e.g., pdsch-AggregationFactor) provides then the UE 115 may report for the time slots from The HARQ-ACK information for the PDSCH reception in time slot n, 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), report the HARQ-ACK information for the PDSCH reception from time slot n-RepNumR16+1 to time slot n, otherwise report the HARQ-ACK information for the PDSCH reception in time slot n.

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

[0132] Similarly, the ACK feedback 401 may include a PDCCH 425 transmitted by the base station 105, where the PDCCH 425 schedules a set of repeated PDSCHs 430. The set of repeated PDSCHs 430 may include repetitions of the PDSCH 435 (as referred to in Figure 2As described, for example, as indicated by the group aggregation factor pdsch - AggregationFactor_group or the group repetition number RepNum_group), such as the first PDSCH 435 - a (e.g., the first repetition), the second PDSCH 435 - b (e.g., the second repetition), the third PDSCH 435 - c (e.g., the third repetition), and the fourth PDSCH 435 - d (e.g., the fourth repetition). Additionally, the PDCCH 425 may also include the slot offset K 0 and the feedback timing indicator field value K 1 (e.g., the PDSCH to HARQ feedback timing indicator field value). However, the PDSCH 435 can be a group - shared PDSCH (e.g., group - shared downlink shared channel) transmitted to multiple UEs 115, rather than the unicast PDSCH as described with reference to Figure 4A which is described

[0133] Additionally, the ACK feedback 401 may include a gap 440 between each repetition of the PDSCH 435 (e.g., as described with reference to Figure 3B which is described). Based on the gap 440 and if the fourth PDSCH 435 - d appears in slot n, then the first PDSCH 435 - a may appear in the slot given by (n - 3(1 + gap)), the second PDSCH 435 - b may appear in the slot given by (n - 2(gap + 1)), and the third PDSCH 435 - c may appear in the slot given by (n - (gap + 1)). Subsequently, one of the multiple UEs 115 may transmit an ACK / NACK 445 to indicate whether the UE 115 has successfully received and decoded the PDSCH 435 using the repeated PDSCH set 430 (e.g., after K 1 ).

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

[0135]

[0136] That is It can represent the maximum value of the group aggregation factor (e.g., pdsch-AggregationFactor) and gap 440 in the configuration of group-shared dynamic PDSCH and group-shared SPS PDSCH with associated G-RNTI and G-CS-RNTI (e.g., corresponding to the same service) in the same BWP. For each gap occasion, UE 115 can be configured to send NACK, repeat ACK / NACK based on PDSCH reception, or send nothing.

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

[0138]

[0139] In some cases, for example, if the TDRA table for the group-shared PDSCH has a row containing the group repetition number (e.g., RepNum_group), then the PDSCH repetition configured via the group aggregation factor (e.g., pdsch-AggregationFactor_group) may not be applied.

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

[0141] Figure 5 Illustrates an example of a process flow 500 that supports configurations for group - shared downlink channels with repetition in accordance with aspects of the present disclosure. The process flow 500 may implement aspects of wireless communication systems 100 and 200. For example, the process flow 500 may include base station 105 - b and UE 115 - d, which may respectively represent examples of the corresponding base station 105 and UE 115 as described above with reference to Figures 1 - 4B as described.

[0142] In the following description of process flow 500, the operations between base station 105 - b and UE 115 - d may be transmitted in an order different from 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 different times. Some 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 performing several operations of process flow 500, any wireless device may perform the shown operations.

[0143] At 505, base station 105 - b may determine the number of repetitions for a group - shared 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.

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

[0145] In some implementations, UE 115-d may receive a semi-static repetition configuration for repetition configuration from base station 105-b. For example, the semi-static repetition configuration may include a group aggregation factor, where the number of repetitions is determined based on the group aggregation factor and the group common downlink shared channel. In some implementations, the group aggregation 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, UE 115-d may determine the group aggregation factor for one or more semi-persistent group common downlink shared channels based on the group aggregation factor for one or more group common downlink shared channels, where the one or more group common downlink shared channels include the group RNTI associated with the one or more semi-persistent group common downlink shared channels. In some implementations, UE 115-d may determine the group aggregation factor for one or more group common downlink shared channels with group RNTI based on the aggregation factor of the unicast downlink shared channel configured to UE 115-d.

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

[0147] At 515, UE 115-d may receive a gap configuration from base station 105-b, where the gap configuration includes an indication of the gap that appears 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 TDRA indication including a gap value for the gap, or a combination thereof. In some implementations, the gap may include the 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 independently configured for one or more downlink shared channels and one or more semi-persistent downlink shared channels. In some implementations, the combination of the number of repetitions and the gap between repetitions may not exceed the periodicity configured for the semi-persistent downlink shared channel.

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

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

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

[0151] At 535, the UE 115-d may transmit an acknowledgement feedback message for the group common downlink shared channel to the base station 105-b based on the monitoring, where the acknowledgement feedback message indicates successful or unsuccessful reception of the group common downlink shared channel based on the number of repetitions. In some implementations, the UE 115-d may receive a configuration of a type 1 acknowledgement codebook for transmitting the acknowledgement feedback message from the base station 105-b. Accordingly, the UE 115-d may determine a set of timing 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 acknowledgement feedback message for the set of timing to the base station 105-b based on the type 1 acknowledgement codebook.

[0152] Additionally or alternatively, the UE 115-d may receive a configuration of a type 2 acknowledgement codebook for transmitting the acknowledgement feedback message from the base station 105-b. Accordingly, the UE 115-d may determine a set of timing for monitoring the group common downlink shared channel based on a feedback timing indicator field value (e.g., K 1 ) between the last repetition of the group common downlink shared channel and the acknowledgement feedback message, an offset value (e.g., K 0 ) between a 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. Subsequently, the UE 115-d may transmit an acknowledgement feedback message for multiple timing to the base station 105-b based on the type 2 acknowledgement codebook.

[0153] Figure 6 FIG. 600 shows a block diagram 600 of a device 605 supporting configuration of a group common downlink channel with repetitions, in accordance with aspects of the present disclosure. The device 605 may be an example of aspects of the UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0154] The receiver 610 may provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to a configuration for a repeated group-shared downlink channel). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or an array including multiple antennas.

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

[0156] 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 repeated group-shared downlink channel 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.

[0157] 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 communication management circuitry). 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 act as or otherwise support the means for performing the functions described in this disclosure. In some examples, the processor and memory coupled to the processor may be configured to perform one or more functions described herein (e.g., by the processor executing instructions stored in the memory).

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

[0159] In some examples, the communication manager 620 may be configured to use or otherwise cooperate with the receiver 610, transmitter 615, or both to perform various operations (e.g., receive, monitor, transmit). For example, the communication manager 620 may receive information from the receiver 610, send information to the transmitter 615, or integrate with the receiver 610, transmitter 615, or both to receive information, transmit information, or perform various other operations described herein.

[0160] According to examples disclosed herein, the communication manager 620 may support wireless communication at the UE. For example, the communication manager 620 may be configured or otherwise support means for receiving from a base station a repeated 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 communication manager 620 may be configured or otherwise support means for determining a number of repetitions for the group common downlink shared channel based on the repeated configuration. The communication manager 620 may be configured or otherwise support means for monitoring the group common downlink shared channel from the base station based on the determined number of repetitions.

[0161] By including or configuring a communication manager 620 according to examples as described herein, a device 605 (e.g., a processor controlling or otherwise coupled to the receiver 610, transmitter 615, communication manager 620, or combinations thereof) may support techniques for enhancing the reliability of group common messages. For example, repetition of the group common downlink shared channel may 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).

[0162] Figure 7FIG. 700 is a block diagram showing an apparatus 705 supporting configurations for a repeated group common downlink channel in accordance with aspects of the present disclosure. The apparatus 705 may be an example of aspects of an apparatus 605 or UE 115 as described herein. The apparatus 705 may include a receiver 710, a transmitter 715, and a communication manager 720. The apparatus 705 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

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

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

[0165] The apparatus 705 or its various components may be examples of means for performing various aspects of the configurations for a repeated group common downlink channel as described herein. For example, the communication 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. The communication manager 720 may be an example of aspects of the communication manager 620 as described herein. In some examples, the communication manager 720 or its various components may be configured to perform various operations (e.g., receive, monitor, transmit) using the receiver 710, the transmitter 715, or both, or otherwise in cooperation with the receiver 310, the transmitter 315, or both. For example, the communication manager 720 may receive information from the receiver 710, send information to the transmitter 715, or integrate with the receiver 710, the transmitter 715, or both to receive information, transmit information, or perform various other operations described herein.

[0166] According to the examples disclosed herein, the communication manager 720 may support wireless communication at a UE. The repetition configuration component 725 may be configured to or otherwise support an apparatus 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. The repetition determination component 730 may be configured to or otherwise support an apparatus for determining, based on the repetition configuration, a number of repetitions for the group common downlink shared channel. The group common downlink shared channel monitoring component 735 may be configured to or otherwise support an apparatus for monitoring, based on the determined number of repetitions, the group common downlink shared channel from the base station.

[0167] Figure 8 FIG. 820 is a block diagram illustrating a communication manager 820 supporting a configuration for a group common downlink channel with repetitions, 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 an apparatus for performing aspects of the methods described herein for a configuration for a group common downlink channel with repetitions. 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 acknowledgement feedback component 855, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0168] According to the examples disclosed herein, the communication manager 820 may support wireless communication at a UE. The repetition configuration component 825 may be configured to or otherwise support an apparatus 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. The repetition determination component 830 may be configured to or otherwise support an apparatus for determining, based on the repetition configuration, a number of repetitions for the group common downlink shared channel. The group common downlink shared channel monitoring component 835 may be configured to or otherwise support an apparatus for monitoring, based on the determined number of repetitions, the group common downlink shared channel from the base station.

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

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

[0171] In some examples, the semi-static repetition component 840 may be configured to or otherwise support a device for a semi-static repetition configuration that includes a clustering factor, where the repetition number is determined based on the clustering factor and a group common downlink shared channel.

[0172] In some examples, the semi-static repetition component 840 may be configured to or otherwise support a device for which the clustering 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.

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

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

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

[0176] In some examples, the dynamic repetition component 845 may be configured to or otherwise support a device for a dynamic repetition configuration that includes a group repetition number parameter indicated via time domain resource allocation, where the repetition number is determined based on the group repetition number parameter.

[0177] In some examples, the gap configuration component 850 may be configured to or otherwise support a device for receiving a gap configuration from a base station, the gap configuration including an indication of a gap that occurs between repetitions of a group common downlink shared channel.

[0178] In some examples, to support reception gap configuration, the gap configuration component 850 may be configured to or otherwise support an apparatus for receiving gap configuration 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.

[0179] In some examples, the gap configuration component 850 may be configured to or otherwise support an apparatus for a gap that includes the number of time slots between each repetition of a group common downlink shared channel, where the length of each time slot is based on the configuration of the bandwidth part used to carry the group common downlink shared channel.

[0180] In some examples, the gap configuration component 850 may be configured to or otherwise support an apparatus for a gap that is independently configured for one or more downlink shared channels and for one or more semi-persistent downlink shared channels.

[0181] In some examples, the gap configuration component 850 may be configured to or otherwise support an apparatus for which the combination of the number of repetitions and the gap between repetitions does not exceed the periodicity configured for a semi-persistent downlink shared channel.

[0182] In some examples, the acknowledgement feedback component 855 may be configured to or otherwise support an apparatus for transmitting an acknowledgement feedback message for a group common downlink shared channel to a base station based on monitoring, where the acknowledgement feedback message indicates successful reception or unsuccessful reception of the group common downlink shared channel based on the number of repetitions.

[0183] In some examples, the acknowledgement feedback component 855 may be configured to or otherwise support an apparatus for receiving a configuration of a type 1 acknowledgement codebook for transmitting an acknowledgement feedback message from a base station.

[0184] In some examples, the acknowledgement feedback component 855 may be configured to or otherwise support an apparatus 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 the gap between each repetition of the group common downlink shared channel. In some examples, the acknowledgement feedback component 855 may be configured to or otherwise support an apparatus for transmitting a single acknowledgement feedback message for the set of multiple opportunities to a base station based on the type 1 acknowledgement codebook.

[0185] In some examples, the acknowledgement feedback component 855 may be configured to or otherwise support an apparatus for receiving a configuration of a type 2 acknowledgement codebook for transmitting an acknowledgement feedback message from a base station.

[0186] In some examples, the acknowledgement 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 acknowledgement 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 acknowledgement feedback component 855 may be configured to or otherwise support means for transmitting an acknowledgement feedback message for the set of multiple opportunities to a base station based on a type 2 acknowledgement codebook.

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

[0188] Figure 9 A diagram of a system 900 including a device 905 that supports a configuration for a group common downlink channel with repetition in accordance with aspects of the present disclosure is shown. The device 905 may be an example of the device 605, the device 705, or the UE 115 as described herein or include components of the device 605, the device 705, or the UE 115. The device 905 may communicate wirelessly 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, which include 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).

[0189] The I / O controller 910 may manage input and output signals of the device 905. The I / O controller 910 may also manage peripheral devices not integrated into the device 905. In some instances, the I / O controller 910 may represent a physical connection or port to an external peripheral device. In some instances, the I / O controller 910 may utilize an operating system, such as or another known operating system. In some other cases, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 910 may be implemented as part of a processor (such as the processor 940). In some cases, a user may interact with the device 905 via the I / O controller 910 or via a hardware component controlled by the I / O controller 910.

[0190] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bidirectionally via one or more antennas 925, 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.

[0191] 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 executable 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 particularly include a basic input / output system (BIOS) that may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0192] Processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, 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 processor 940. Processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause device 905 to perform various functions (e.g., support functions or tasks for a configuration with a repeated group common downlink channel). For example, device 905 or components of device 905 may include processor 940 and memory 930 coupled to processor 940, and processor 940 and memory 930 are configured to perform the various functions described herein.

[0193] According to the examples disclosed herein, communication manager 920 may support wireless communication at a UE. For example, communication manager 920 may be configured to or otherwise support means for receiving, from a base station, a repeated 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. Communication manager 920 may be configured to or otherwise support means for determining, based on the repeated configuration, a number of repetitions for the group common downlink shared channel. Communication manager 920 may be configured to or otherwise support means for monitoring, based on the determined number of repetitions, the group common downlink shared channel from the base station.

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

[0195] In some examples, communication manager 920 may be configured to perform various operations (e.g., receive, monitor, transmit) using transceiver 915, one or more antennas 925, or any combination thereof, or otherwise in cooperation with transceiver 915, one or more antennas 925, or any combination thereof. Although communication manager 920 is illustrated as a separate component, in some examples, one or more of the functions described with reference to communication manager 920 may be supported or performed by processor 940, memory 930, code 935, or any combination thereof. For example, code 935 may include instructions executable by processor 940 to cause device 905 to perform various aspects of the configuration for a repeated group common downlink channel as described herein, or processor 940 and memory 930 may otherwise be configured to perform or support such operations.

[0196] Figure 10 Block diagram 1000 is shown that illustrates a device 1005 in accordance with aspects of the present disclosure that supports a configuration for a repeated group common downlink channel. Device 1005 may be an example of aspects of base station 105 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

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

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

[0199] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, can be examples of apparatuses for performing various aspects of the configuration for a repeated group common downlink channel as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof can support methods for performing one or more functions described herein.

[0200] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof can be implemented in hardware (e.g., in communication management circuitry). The hardware can 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 supporting an apparatus for performing the functions described in this disclosure. In some examples, a processor and memory coupled to the processor can be configured to perform one or more functions described herein (e.g., by the processor executing instructions stored in the memory).

[0201] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof can be implemented by code executed by a processor (e.g., as communication management software or firmware). If implemented by code executed by a processor, the functions of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof can 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 to or otherwise supporting an apparatus for performing the functions described in this disclosure).

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

[0203] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at a base station. For example, the communication manager 1020 may be configured to or otherwise support an apparatus for determining a number of repetitions 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 communication manager 1020 may be configured to or otherwise support an apparatus for transmitting a repetition configuration for a 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 communication manager 1020 may be configured to or otherwise support an apparatus for transmitting a group common downlink shared channel to one or more UEs based on the determined number of repetitions.

[0204] Figure 11 Block diagram 1100 illustrates a device 1105 that supports a configuration for a group common downlink channel with repetitions, in accordance with aspects of the present disclosure. The device 1105 may be an example of aspects of the device 1005 or the 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).

[0205] The receiver 1110 may provide an apparatus for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to a configuration for a group common downlink channel with repetitions). The information may be passed to other components of the device 1105. The receiver 1110 may utilize a single antenna or an array including multiple antennas.

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

[0207] Device 1105 or its various components may be examples of apparatus for performing various aspects of the configuration for a repeated group common downlink channel as described herein. For example, communication manager 1120 may include a repetition number determination component 1125, a repetition configuration indication component 1130, a group common downlink shared channel component 1135, or any combination thereof. Communication manager 1120 may be an example of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, monitor, transmit) using receiver 1110, transmitter 1115, or both, or otherwise in cooperation with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, send information to transmitter 1115, or integrate in combination with receiver 1110, transmitter 1115, or both to receive information, transmit information, or perform various other operations described herein.

[0208] According to examples disclosed herein, communication manager 1120 may support wireless communication at a base station. Repetition number determination component 1125 may be configured to or otherwise support apparatus for determining a repetition number for a group common downlink shared channel that includes 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. Repetition configuration indication component 1130 may be configured to or otherwise support apparatus for transmitting a repetition configuration for a group common downlink shared channel to one or more user equipments (UEs), the repetition configuration including an indication of the determined repetition number. Group common downlink shared channel component 1135 may be configured to or otherwise support apparatus for transmitting a group common downlink shared channel to one or more UEs based on the determined repetition number.

[0209] Figure 12FIG. 1200 is a block diagram illustrating a communication manager 1220 in accordance with aspects of the present disclosure that supports configurations for a repeated group common downlink channel. The communication manager 1220 may 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 may be an example of an apparatus for performing aspects of the configurations for a repeated group common downlink channel as described herein. For example, the communication manager 1220 may 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 acknowledgement component 1255, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0210] In accordance with examples disclosed herein, the communication manager 1220 may support wireless communication at a base station. The repetition number determination component 1225 may be configured to or otherwise support an apparatus for determining a repetition number for a group common downlink shared channel that includes 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 repetition configuration indication component 1230 may be configured to or otherwise support an apparatus for transmitting a repetition configuration for a group common downlink shared channel to one or more user equipments (UEs), the repetition configuration including an indication of the determined repetition number. The group common downlink shared channel component 1235 may be configured to or otherwise support an apparatus for transmitting a group common downlink shared channel to one or more UEs based on the determined repetition number.

[0211] 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 to or otherwise support an apparatus for transmitting a semi-static repetition configuration for a repetition configuration to one or more UEs.

[0212] In some examples, to support transmitting the semi-static repetition configuration, the semi-static repetition indication component 1240 may be configured to or otherwise support an apparatus for transmitting the semi-static repetition configuration to one or more UEs via radio resource control signaling.

[0213] In some examples, the semi-static repetition indication component 1240 may be configured to or otherwise support an apparatus for a semi-static repetition configuration that includes a group aggregation factor, wherein the repetition number is indicated based on the group aggregation factor and the group common downlink shared channel.

[0214] In some examples, to support the transmission of configurations for the downlink shared channel, the dynamic repetition indication component 1245 may be configured to or otherwise support an apparatus for transmitting a dynamic repetition configuration for repetition configuration to one or more UEs.

[0215] In some examples, the dynamic repetition indication component 1245 may be configured to or otherwise support an apparatus for a dynamic repetition configuration that includes 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.

[0216] In some examples, the gap configuration indication component 1250 may be configured to or otherwise support an apparatus for transmitting a gap configuration to one or more UEs, the gap configuration including an indication of a gap that occurs between repetitions of a group common downlink shared channel.

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

[0218] In some examples, the gap configuration indication component 1250 may be configured to or otherwise support an apparatus for a gap that includes the number of time slots between each repetition of a group common downlink shared channel, wherein the length of each time slot is based on the configuration of the bandwidth part used to carry the group common downlink shared channel.

[0219] In some examples, the gap configuration indication component 1250 may be configured to or otherwise support an apparatus for a gap that is independently configured for one or more downlink shared channels and for one or more semi-persistent downlink shared channels.

[0220] In some examples, the gap configuration indication component 1250 may be configured to or otherwise support an apparatus for which the combination of the repetition number and the gap between repetitions does not exceed the periodicity configured for the semi-persistent downlink shared channel.

[0221] In some examples, the acknowledgement component 1255 may be configured to or otherwise support an apparatus for receiving an acknowledgement feedback message for the group common downlink shared channel from one or more UEs based on the transmission of the group common downlink shared channel, wherein the acknowledgement feedback message indicates successful or unsuccessful reception of the group common downlink shared channel based on the repetition number.

[0222] In some examples, the acknowledgement component 1255 may be configured to or otherwise support an apparatus for transmitting a configuration for a type 1 acknowledgement codebook for one or more UEs to transmit acknowledgement feedback messages, wherein the acknowledgement feedback messages are received based on the type 1 acknowledgement codebook.

[0223] In some examples, the acknowledgement component 1255 may be configured to or otherwise support an apparatus for transmitting a configuration for a type 2 acknowledgement codebook for one or more UEs to transmit acknowledgement feedback messages, wherein the acknowledgement feedback messages are received based on the type 2 acknowledgement codebook.

[0224] In some examples, the repetition configuration indication component 1230 may be configured to or otherwise support an apparatus for a repetition configuration, the repetition configuration including a group radio network temporary identifier that indicates that a group common downlink shared channel is transmitted to one or more UEs.

[0225] Figure 13 A diagram of a system 1300 including an apparatus 1305 that supports a configuration for a group common downlink channel with repetition in accordance with aspects of the present disclosure is shown. The apparatus 1305 may be an example of the apparatus 1005, the apparatus 1105, or the base station 105 described herein or include components of these apparatuses. The apparatus 1305 may communicate wirelessly with one or more base stations 105, UEs 115, or any combination thereof. The apparatus 1305 may include components for two-way voice and data communication, which include components for transmitting and receiving communications, including a communication manager 1320, a network communication manager 1310, a transceiver 1315, an antenna 1325, a memory 1330, code 1335, a processor 1340, and an inter-station communication 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).

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

[0227] In some cases, device 1305 may include a single antenna 1325. However, in some other cases, device 1305 may have more than one antenna 1325, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1315 may communicate bidirectionally via one or more antennas 1325, wired or wireless links, as described herein. For example, transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. 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. Transceiver 1315 or transceiver 1315 and one or more antennas 1325 may be examples of transmitter 1015, transmitter 1115, receiver 1010, receiver 1110, or any combination thereof or components thereof, as described herein.

[0228] Memory 1330 may include RAM and ROM. Memory 1330 may store computer-readable, computer-executable code 1335 that includes 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 executable 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 specifically include BIOS, which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0229] Processor 1340 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, 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 processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., support functions or tasks for a configuration with a repeated group common downlink channel). For example, device 1305 or components of device 1305 may include processor 1340 and memory 1330 coupled to processor 1340, which are configured to perform the various functions described herein.

[0230] The inter-station communication manager 1345 may manage communication with other base stations 105 and may include a controller or scheduler for collaboratively controlling communication with the UE 115 with other base stations 105. For example, the inter-station communication manager 1345 may 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-station communication manager 1345 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between the base stations 105.

[0231] According to the examples disclosed herein, the communication manager 1320 may support wireless communication 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 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 communication manager 1320 may be configured to or otherwise support means for transmitting a repetition configuration for a group common downlink shared channel to one or more user equipments (UEs), the repetition configuration including an indication of the determined repetition number. The communication manager 1320 may be configured to or otherwise support means for transmitting a group common downlink shared channel to one or more UEs based on the determined repetition number.

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

[0233] Figure 14 A flowchart illustrating a method 1400 for supporting a configuration for a group common downlink channel with repetition in accordance with aspects of the present disclosure is shown. The operations of method 1400 may be implemented by a UE or its components as described herein. For example, the operations of method 1400 may be performed by a UE as referred to in Figures 1 to 9Performed by the UE 115 described. 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 aspects of the described functions.

[0234] At 1405, 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. The operation of 1405 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1405 may be performed by a repetition configuration component 825 as described with reference to Figure 8 Performed.

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

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

[0237] Figure 15 A flowchart illustrating a method 1500 supporting configuration of a group common downlink channel with repetitions in accordance with aspects of the present disclosure is shown. The operations of method 1500 may be implemented by a UE or its components as described herein. For example, the operations of method 1500 may be performed by a UE 115 as described with reference to Figures 1 to 9 Performed by the UE 115 described. 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 aspects of the described functions.

[0238] At 1505, 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. The operation of 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1505 may be performed by a repetition configuration component as described with reference to Figure 8Performed by the described repetitive configuration component 825.

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

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

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

[0242] Figure 16 A flowchart illustrating a method 1600 that supports configuration of a group common downlink channel with repetition in accordance with aspects of the present disclosure is shown. The operations of method 1600 may be implemented by a UE or its components as described herein. For example, the operations of method 1600 may be performed by a UE 115 as described with reference to Figures 1 to 9 the described UE 115. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0243] At 1605, 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. The operation of 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1605 may be performed by a repetition configuration component 825 as described with reference to Figure 8 the described repetition configuration component 825.

[0244] At 1610, the method may include receiving, from the base station, a dynamic repetition configuration for the repetition configuration. The operation of 1610 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1610 may be performed by a component as described with reference to Figure 8Execute using the described dynamic repeating component 845.

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

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

[0247] Figure 17 A flowchart illustrating a method 1700 supporting a configuration for a group common downlink channel with repetition in accordance with aspects of the present disclosure is shown. The operations of method 1700 may be implemented by a UE or its components as described herein. For example, the operations of method 1700 may be performed by a UE 115 as described with reference to Figures 1 to 9 Execute using the described UE 115. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0248] At 1705, the method may include receiving, from a base station, a repeating 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 at 1705 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1705 may be performed by a repeating configuration component 825 as described with reference to Figure 8 Execute using the described repeating configuration component 825.

[0249] At 1710, the method may include receiving, from the base station, a gap configuration, the gap configuration including an indication of a gap occurring between repetitions of the group common downlink shared channel. The operations at 1710 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1710 may be performed by a gap configuration component 850 as described with reference to Figure 8 Execute using the described gap configuration component 850.

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

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

[0252] Figure 18 FIG. shows a flowchart of a method 1800 for supporting a configuration for a group common downlink channel with repetition in accordance with aspects of the present disclosure. The operations of method 1800 may be implemented by a UE or its components as described herein. For example, the operations of method 1800 may be performed by a UE 115 as described with reference to Figures 1 to 9 as described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0253] In 1805, 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. The operations of 1805 may be performed according to the examples disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a repetition configuration component 825 as described with reference to Figure 8 as described.

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

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

[0256] At 1820, the method may include transmitting an acknowledgement feedback message for the group common downlink shared channel to the base station based on the monitoring, where the acknowledgement feedback message indicates a successful reception or an unsuccessful reception of the group common downlink shared channel based on the repetition number. The operation of 1820 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1820 may be performed by the acknowledgement feedback component 855 as described with reference to Figure 8 The described acknowledgement feedback component 855 to perform.

[0257] Figure 19 A flowchart illustrating a method 1900 supporting a configuration for a group common downlink channel with repetition in accordance with aspects of the present disclosure is shown. The operations of method 1900 may be implemented by a base station or its components as described herein. For example, the operations of method 1900 may be performed by the base station 105 as described with reference to Figures 1 to 5 And Figures 10 to 13 The described base station 105 to perform. In some examples, the base station may execute an instruction set to control functional elements of the base station to perform the described functions. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the described functions.

[0258] 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 operation of 1905 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1905 may be performed by the repetition number determination component 1225 as described with reference to Figure 12 The described repetition number determination component 1225 to perform.

[0259] 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 repetition number. The operation of 1910 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1910 may be performed by the repetition configuration indication component 1230 as described with reference to Figure 12 The described repetition configuration indication component 1230 to perform.

[0260] At 1915, the method may include transmitting the group common downlink shared channel to the one or more UEs based on the determined repetition number. The operation of 1915 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1915 may be performed by the group common downlink shared channel component 1235 as described with reference to Figure 12 The described group common downlink shared channel component 1235 to perform.

[0261] Note that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified and other implementations are possible. Additionally, aspects from two or more methods may be combined.

[0262] An overview of examples of the present invention is provided below:

[0263] Example 1: A method for wireless communication at a user equipment (UE), comprising: 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, at least in part based on the repetition configuration, a number of repetitions for the group common downlink shared channel; and monitoring, at least in part based on the determined number of repetitions, the group common downlink shared channel from the base station.

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

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

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

[0267] Example 5: The method of Example 4, wherein the group aggregation 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.

[0268] Example 6: The method of any one of Examples 4 to 5, further comprising: determining, at least in part based on the group aggregation factor for the one or more group common downlink shared channels, a group aggregation factor for the one or more semi-persistent 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.

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

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

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

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

[0273] 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 including a gap value for the gap, or a combination thereof.

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

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

[0276] Example 14: The method of any one of Examples 10 to 13, wherein the combination of the repetition number and the gap between the repetitions does not exceed a periodicity configured for the semi-persistent downlink shared channel.

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

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

[0279] Example 17: The method as in Example 16 further includes: determining a plurality of occasions for monitoring the group common downlink shared channel at least in part based on the repetition number 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 occasions to the base station at least in part based on the type 1 acknowledgment codebook.

[0280] Example 18: The method as in Example 15 further includes: receiving from the base station a configuration of a type 2 acknowledgment codebook for transmitting the acknowledgment feedback message.

[0281] Example 19: The method as in Example 18 further includes: determining a plurality of occasions for monitoring the group common downlink shared channel at least in part based 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 repetition number, 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 plurality of occasions to the base station at least in part based on the type 2 acknowledgment codebook.

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

[0283] Example 21: A method for wireless communication at a base station includes: 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 user equipments (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 at least in part based on the determined repetition number.

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

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

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

[0287] Example 25: A method as in Example 21, wherein transmitting the configuration for the downlink shared channel includes: transmitting a dynamic repetition configuration for the repetition configuration to the one or more UEs.

[0288] Example 26: A method as in Example 25, wherein the dynamic repetition configuration includes a group repetition number parameter indicated via a time domain resource allocation, and wherein the number of repetitions is indicated at least in part based on the group repetition number parameter.

[0289] Example 27: A method as in any of Examples 21 to 26, further including: transmitting a gap configuration to the one or more UEs, the gap configuration including an indication of a gap that occurs between repetitions of the group common downlink shared channel.

[0290] Example 28: A method as in Example 27, wherein transmitting the gap configuration includes: transmitting the gap configuration to the one or more UEs semi-statically via radio resource control signaling, dynamically via a time domain resource allocation including a gap value for the gap, or a combination thereof.

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

[0292] Example 30: A method as in any 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.

[0293] Example 31: A method as in any of Examples 27 to 30, wherein the combination of the number of repetitions and the gap between the repetitions does not exceed the periodicity configured for the semi-persistent downlink shared channel.

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

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

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

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

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

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

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

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

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

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

[0304] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in much of the description, the techniques described herein may also be applied to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applied to a variety of 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.

[0305] The information and signals described herein may be represented using any of a variety of different arts 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 voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0306] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0307] 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, the functions may be stored on or transmitted via a computer readable medium as one or more instructions or code. Other examples and implementations fall within the scope of the 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, hardwired, or any combination thereof. The features implementing the functions may also be physically located in various positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0308] A computer-readable medium includes both a non-transitory computer storage medium and a communication medium including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Likewise, any connection is properly termed a computer-readable medium. For example, if software is transferred from a web site, 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 microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically with lasers. Combinations of the above media are also included within the scope of computer-readable media.

[0309] As used herein, including in the claims, the "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive listing such that, for example, a listing 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 construed as reciting a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0310] In the figures, like components or features may have the same reference numeral. Additionally, each of the same type of components may be distinguished by following the reference numeral with a dash and a second numeral that differentiates among the similar components. If only the first reference numeral is used in the specification, the description may apply to any one of the similar components having the same first reference numeral regardless of the second reference numeral, or any other subsequent reference numeral.

[0311] The description set forth herein with reference to the drawings describes example configurations and does not represent all examples that may be implemented or that 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 "superior to" or "better than" other examples. This detailed description includes specific details to provide an understanding of the described techniques. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0312] The description provided herein is to enable a person 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 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, at least in part, a number of repetitions for the group common downlink shared channel based on the repetition configuration; and monitoring, at least in part, the group common downlink shared channel from the base station based on the determined number of repetitions.

2. The method according to claim 1, wherein receiving the repetition configuration for the group common downlink shared channel comprises: receiving, via radio resource control signaling from the base station, a semi-static repetition configuration for the repetition configuration.

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

4. The method according to claim 3, wherein the group aggregation 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 according to claim 3, further comprising: determining, at least in part, the group aggregation factor for the one or more semi-persistent downlink shared channels based on the group aggregation 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 according to claim 3, further comprising: determining, at least in part, the group aggregation factor for the one or more downlink shared channels having a group radio network temporary identifier based on an aggregation factor of a unicast downlink shared channel configured to the UE.

7. The method according to claim 1, wherein receiving the repetition configuration for the group common downlink shared channel comprises: receiving, from the base station, a dynamic repetition configuration for the repetition configuration.

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

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

10. The method according to claim 7, wherein receiving the repetition configuration for the group common downlink shared channel comprises: Receive a semi-static repetition configuration for the repetition configuration 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 G-RNTIs (G-CS-RNTIs).

11. The method according to claim 1, further comprising: Receive a gap configuration from the base station, the gap configuration including an indication of a gap that occurs between repetitions of the group common downlink shared channel.

12. The method according to claim 11, 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.

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

14. The method according to claim 11, wherein the gap is independently configured for the one or more downlink shared channels and the one or more semi-persistent downlink shared channels.

15. The method according to claim 11, wherein the combination of the number of repetitions and the gap between the repetitions does not exceed the periodicity configured for the semi-persistent downlink shared channel.

16. The method according to claim 1, further comprising: Transmit an acknowledgement feedback message for the group common downlink shared channel to the base station at least partially based on the monitoring, wherein the acknowledgement feedback message indicates a successful reception or an unsuccessful reception of the group common downlink shared channel at least partially based on the number of repetitions.

17. The method according to claim 16, further comprising: Receive a configuration of a type 1 acknowledgement codebook for transmitting the acknowledgement feedback message from the base station.

18. The method according to claim 17, further comprising: Determine a plurality of opportunities for monitoring the group common downlink shared channel at least partially based on the number of repetitions and a gap value representing the gap between each repetition of the group common downlink shared channel; and Transmit a single acknowledgement feedback message for the plurality of opportunities to the base station at least partially based on the type 1 acknowledgement codebook.

19. The method according to claim 16, further comprising: Receive a configuration of a type 2 acknowledgement codebook for transmitting the acknowledgement feedback message from the base station.

20. The method according to claim 19, further comprising: Determine a plurality of occasions for monitoring the group common downlink shared channel at least in part based on a feedback timing indicator field value between a last repetition of the group common downlink shared channel and the acknowledgement 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; and Transmit the acknowledgement feedback message for the plurality of occasions to the base station at least in part based on the type 2 acknowledgement codebook.

21. The method according to claim 1, wherein the repetition configuration includes 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: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the following operations: Receive, 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; Determine, at least in part based on the repetition configuration, a number of repetitions for the group common downlink shared channel; and Monitor the group common downlink shared channel from the base station at least in part based on the determined number of repetitions.

23. The apparatus according to claim 22, wherein the instructions for receiving the repetition configuration for the group common downlink shared channel are executable by the processor to cause the apparatus to: Receive, from the base station via radio resource control signaling, a semi-static repetition configuration for the repetition configuration.

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

25. The apparatus according to claim 22, wherein the instructions for receiving the repetition configuration for the group common downlink shared channel are executable by the processor to cause the apparatus to: Receive, from the base station, a dynamic repetition configuration for the repetition configuration.

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

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

28. The apparatus according to claim 22, wherein the instruction for receiving the repetition configuration for the group common downlink shared channel can be executed by the processor to cause the apparatus to: Receive a semi-static repetition configuration for the repetition configuration 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 G-RNTIs (G-CS-RNTIs).

29. An apparatus for wireless communication at a user equipment (UE), comprising: 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, at least in part based on the repetition configuration, a number of repetitions for the group common downlink shared channel; and and means for monitoring, at least in part based on the determined number of repetitions, the group common downlink shared channel from the base station.

30. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code including instructions executable by a processor 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; Determining, at least in part based on the repetition configuration, a number of repetitions for the group common downlink shared channel; and Monitoring, at least in part based on the determined number of repetitions, the group common downlink shared channel from the base station.

Images