Configuration for a group-wide downlink channel using repetition

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may receive a configuration for a group-common physical downlink shared channel (PDSCH), where the group-common PDSCH is repeated by a repetition number. Accordingly, the UE may determine the repetition number and then monitor the group-common PDSCH based on the repetition number. In some implementations, the group-common PDSCH may include a semi-static repetition scheme, where the repetition number is indicated via a group aggregation factor. Additionally or alternatively, the group-common PDSCH may include a dynamic repetition scheme, where the repetition number is indicated via a group repetition number. Furthermore, techniques described herein may enable a configuration for a repeated group-common PDSCH to include a gap between each repetition of the group-common PDSCH, and may enable the UE to send acknowledgment feedback for the repetition of the group-common PDSCH.

Description

[Technical Field]

[0001] cross reference

[0001] This patent application claims the interests of U.S. Provisional Patent Application No. 63 / 090,036, filed on 9 October 2020, entitled "CONFIGURATION FOR GROUP-COMMON DOWNLINK CHANNELS WITH REPETITIONS," and U.S. Patent Application No. 17 / 472,452, filed on 10 September 2021, both of which have been assigned to the assignee of this application.

[0002]

[0002] The following relates to wireless communication including a configuration for a group-common downlink channel using repetition. [Background technology]

[0003]

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcast. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems such as Long-Term Evolution (LTE®) systems, LTE Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems, sometimes called New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiple access (DFT-S-OFDM).

[0004]

[0004] A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each supporting communication for multiple communication devices, which may sometimes be known as user equipment (UEs). In some cases, a base station may communicate with multiple UEs simultaneously. For example, a base station may use broadcast transmissions or multicast transmissions to carry the same message to multiple UEs. Rather than configuring a transmission specifically for each UE, a base station may configure a group common transmission for multiple UEs and present these configurations to multiple UEs so that multiple UEs can monitor and receive these group common transmissions. Efficient techniques are desired to support the successful reception and decoding of group common transmissions in multiple UEs. [Overview of the project]

[0005]

[0005] The techniques described relate to improved methods, systems, devices, and apparatus for supporting configurations for group-common downlink channels using repetitions. Generally, the techniques described provide a user equipment (UE) receiving a configuration for a group-common physical downlink shared channel (PDSCH), where the configuration includes an indication that the group-common PDSCH will be repeated a number of repetitions. 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. Thus, the UE can determine the number of repetitions and then monitor the group-common PDSCH based on the number of repetitions. In some implementations, the same or different configurations may represent a semi-static repetition scheme for a group-common PDSCH, where the number of repetitions is indicated by the group aggregation factor. Alternatively, the same or different configurations may represent a dynamic repetition scheme for a group-common PDSCH, where the number of repetitions is indicated by the group repetition number.

[0006]

[0006] Furthermore, the configuration for a group-common PDSCH may include instructions for a gap that occurs between each iteration of the group-common PDSCH. For example, the gap may include several slots (e.g., or transmission intervals of different lengths) between each iteration of the group-common PDSCH, where the UE does not expect to receive additional configurations scheduling additional group-common PDSCHs during the gap. This 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 gap). In some implementations, the UE may transmit acknowledgment feedback for the group-common PDSCH and the number of iterations for the group-common PDSCH. For example, the UE may use a Type 1 acknowledgment codebook or a Type 2 acknowledgment codebook to transmit acknowledgment feedback. In either type, the UE can determine the number of candidate occasions for receiving a group-common PDSCH and for determining acknowledgment feedback. The UE may determine the number of candidate occasions based on factors such as the group aggregation factor, the number of group repetitions, the gap between repetitions, the feedback timing indicator field value, and the slot offset, each of which of these factors is used depending on the type of acknowledgment codebook used or configured.

[0007]

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

[0008]

[0008] The device for wireless communication in the UE is described below. This device may include a processor, a memory communicating electronically with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to receive a repetitive configuration from a base station for a group-common downlink sharing channel, determine the number of repetitions for the group-common downlink sharing channel based on the repetitive configuration, which includes one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof, and monitor the group-common downlink sharing channel from the base station based on the determined number of repetitions.

[0009]

[0009] Another device for wireless communication in a UE is described. This device may include means for receiving a repetitive configuration for a group common downlink sharing channel from a base station, means for determining the number of repetitions for the group common downlink sharing channel based on the repetitive configuration, the group common downlink sharing channel including one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof, and means for monitoring the group common downlink sharing channel from the base station based on the determined number of repetitions.

[0010]

[0010] A non-transitory computer-readable medium for storing a code for wireless communication in the UE is described. The code may include instructions that can be executed by a processor to receive a repetitive configuration from a base station for a group-common downlink sharing channel, to determine the number of repetitions for the group-common downlink sharing channel based on the repetitive configuration, which includes one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof, and to monitor the group-common downlink sharing channel from the base station based on the determined number of repetitions.

[0011]

[0011] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, receiving a group common configuration for a downlink shared channel may include an operation, feature, means, or instruction for receiving a semi-static repetition configuration for a repetition configuration from a base station.

[0012]

[0012] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, receiving a semi-static repetitive configuration may include an operation, feature, means, or instruction for receiving a semi-static repetitive configuration from a base station via radio resource control signaling.

[0013]

[0013] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the semi-static repetitive configuration includes a group aggregation factor, where the number of repetitions may be determined based on the group aggregation factor and a group-common downlink shared channel.

[0014]

[0014] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, 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 1.

[0015]

[0015] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining a group aggregation factor for one or more semi-persistent group-common downlink sharing channels based on a group aggregation factor for one or more group-common downlink sharing channels, wherein the iterative configuration includes a group radio network temporary identifier associated with one or more semi-persistent group-common downlink sharing channels.

[0016]

[0016] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for determining a group aggregation factor for one or more group-common downlink shared channels having a group radio network temporary identifier based on the aggregation factor of unicast downlink shared channels configured in a UE.

[0017]

[0017] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, receiving a configuration for a downlink shared channel may include an operation, feature, means, or instruction for receiving a dynamic repetition configuration for a repetition configuration from a base station.

[0018]

[0018] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the dynamic repetition configuration includes a group repetition number parameter via a time-domain resource allocation indication, where the number of repetitions may be determined based on the group repetition number parameter.

[0019]

[0019] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for receiving from a base station a gap configuration, which includes instructions for gaps occurring between repetitions of a group common downlink shared channel.

[0020]

[0020] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, receiving a gap configuration may include an operation, feature, means, or instruction for receiving a gap configuration from a base station semi-statically via radio resource control signaling, dynamically via time-domain resource allocation instructions including a gap value for the gap, or a combination thereof.

[0021]

[0021] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the gap comprises several slots between each iteration of a group-common downlink shared channel, where the length of each slot may be based on the configuration of the bandwidth part used to carry the group-common downlink shared channel.

[0022]

[0022] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the gap may be configured independently for one or more downlink shared channels and one or more semi-persistent downlink shared channels.

[0023]

[0023] In some examples of the methods, apparatus, and non-temporary 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.

[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for causing a base station to transmit an acknowledgment feedback message for a group-common downlink shared channel based on monitoring, where the acknowledgment feedback message indicates successful or unsuccessful reception of the group-common downlink shared channel based on a repetition count.

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

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

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

[0028]

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

[0029]

[0029] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the repeating configuration includes a group radio network temporary identifier shared by a plurality of UEs, including at least one UE.

[0030]

[0030] A method for wireless communication at a base station will be described. This method may include determining a repetition count for a group common downlink sharing channel, transmitting a repetition configuration for the group common downlink sharing channel to one or more UEs, the group common downlink sharing channel including one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof, and transmitting the group common downlink sharing channel to one or more UEs based on the determined repetition count, the repetition configuration including instructions for the determined repetition count.

[0031]

[0031] The device for wireless communication at a base station will be described. The device may include a processor, a memory communicating electronically with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to determine the number of repetitions for a group common downlink shared channel, to transmit a repetition configuration for the group common downlink shared channel to one or more UEs, the group common downlink shared channel including one or more downlink shared channels, one or more semi-persistent downlink shared channels different from one or more downlink shared channels, or a combination thereof, and to transmit the group common downlink shared channel to one or more UEs, based on the determined number of repetitions, the repetition configuration including instructions for the determined number of repetitions.

[0032]

[0032] Another device for wireless communication at a base station will be described. This device may include means for determining the number of repetitions for a group common downlink sharing channel; means for transmitting a repetition configuration for a group common downlink sharing channel to one or more UEs, the group common downlink sharing channel including one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof; and means for transmitting the group common downlink sharing channel to one or more UEs based on the determined number of repetitions, the repetition configuration including instructions for the determined number of repetitions.

[0033]

[0033] A non-temporary computer-readable medium for storing code for wireless communication at a base station is described. The code may include instructions that can be executed by a processor to determine the number of repetitions for a group common downlink shared channel, the group common downlink shared channel includes one or more downlink shared channels, one or more semi-persistent downlink shared channels different from one or more downlink shared channels, or a combination thereof, and the repetition configuration includes instructions for the determined number of repetitions for the group common downlink shared channel to one or more UEs based on the determined number of repetitions.

[0034]

[0034] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, transmitting a group common configuration for a downlink shared channel may include an operation, feature, means, or instruction for transmitting a semi-static repetitive configuration for a repetitive configuration to one or more UEs.

[0035]

[0035] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, transmitting a semi-static repetitive configuration may include an operation, feature, means, or instruction for transmitting a semi-static repetitive configuration to one or more UEs via radio resource control signaling.

[0036]

[0036] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, a semi-static repetitive configuration includes a group aggregation factor, where the number of repetitions may be indicated based on the group aggregation factor and a group common downlink shared channel.

[0037]

[0037] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, transmitting a configuration for a downlink shared channel may include an operation, feature, means, or instruction for transmitting a dynamic repetitive configuration for a repetitive configuration to one or more UEs.

[0038]

[0038] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the dynamic repetition configuration includes a group repetition count parameter via a time-domain resource allocation instruction, where the repetition count may be indicated based on the group repetition count parameter.

[0039]

[0039] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for transmitting to one or more UEs a gap configuration including instructions for gaps occurring between repetitions of a group common downlink shared channel.

[0040]

[0040] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, transmitting a gap configuration may include an operation, feature, means, or instruction for transmitting a gap configuration to one or more UEs semi-statically via radio resource control signaling, dynamically via time-domain resource allocation instructions including the gap value of the gap, or a combination thereof.

[0041]

[0041] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the gap comprises several slots between each iteration of a group-common downlink shared channel, where the length of each slot may be based on the configuration of the bandwidth portion used to carry the group-common downlink shared channel.

[0042]

[0042] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the gap may be configured independently for one or more downlink shared channels and one or more semi-persistent downlink shared channels.

[0043]

[0043] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the number of repetitions, combined with the gap between repetitions, does not exceed the period configured for the semi-persistent downlink shared channel.

[0044]

[0044] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for receiving an acknowledgment feedback message for a group-common downlink sharing channel based on transmitting a group-common downlink sharing channel from one or more UEs, wherein the acknowledgment feedback message indicates a successful or unsuccessful reception of the group-common downlink sharing channel based on the number of repetitions.

[0045]

[0045] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for transmitting configurations for a Type 1 acknowledgment codebook for one or more UEs to transmit acknowledgment feedback messages, where the acknowledgment feedback messages may be received based on a Type 1 acknowledgment codebook.

[0046]

[0046] Some examples of methods, apparatus, and non-temporary computer-readable media described herein may further include operations, features, means, or instructions for transmitting configurations for a Type 2 acknowledgment codebook for one or more UEs to transmit acknowledgment feedback messages, where the acknowledgment feedback messages may be received based on a Type 2 acknowledgment codebook.

[0047]

[0047] In some examples of the methods, apparatus, and non-temporary computer-readable media described herein, the repetitive configuration includes a group radio network temporary identifier indicating that a group common downlink shared channel may be transmitted for one or more UEs. [Brief explanation of the drawing]

[0048] [Figure 1]

[0048] A diagram illustrating an example of a wireless communication system that supports a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. [Figure 2]

[0049] A diagram illustrating an example of a wireless communication system that supports a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 3A]

[0050] A diagram illustrating an example of a repetition scheme that supports a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 3B] A diagram illustrating an example of a repetition scheme that supports a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 4A]

[0051] A diagram illustrating an example of affirmative feedback supporting a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 4B] A diagram illustrating an example of affirmative feedback supporting a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 5]

[0052] A diagram illustrating an example of a process flow that supports the configuration of a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 6]

[0053] A block diagram of a device supporting a configuration for a group-common downlink channel using repetition, according to an aspect of this disclosure. [Figure 7] A block diagram of a device supporting a configuration for a group-common downlink channel using repetition, according to an aspect of this disclosure. [Figure 8]

[0054] A block diagram of a communications manager supporting a configuration for a group-common downlink channel using repetition, according to an aspect of this disclosure. [Figure 9]

[0055] A diagram of a system including a device that supports a configuration for a group-common downlink channel using repetition, according to an aspect of this disclosure. [Figure 10]

[0056] A block diagram of a device supporting a configuration for a group-common downlink channel using repetition, according to an aspect of this disclosure. [Figure 11] A block diagram of a device supporting a configuration for a group-common downlink channel using repetition, according to an aspect of this disclosure. [Figure 12]

[0057] A block diagram of a communications manager supporting a configuration for a group-common downlink channel using repetition, according to an aspect of this disclosure. [Figure 13]

[0058] A diagram of a system including a device that supports a configuration for a group-common downlink channel using repetition, according to an aspect of this disclosure. [Figure 14]

[0059] A flowchart illustrating a method for supporting a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 15]A flowchart illustrating a method for supporting a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 16] A flowchart illustrating a method for supporting a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 17] A flowchart illustrating a method for supporting a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 18] A flowchart illustrating a method for supporting a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Figure 19] A flowchart illustrating a method for supporting a configuration for a group-common downlink channel using repetition, according to aspects of this disclosure. [Modes for carrying out the invention]

[0049]

[0060] User equipment (UE) and base stations may support semi-static and / or dynamic repetition of physical downlink shared channels (PDSCH) in consecutive slots. For example, a base station may configure the UE in a repetitive configuration (including, for example, the pdsch-AggregationFactor parameter, RepNumR16 parameter, etc.) for the UE to apply to unicast dynamic PDSCH and unicast semi-persistent scheduling (SPS) PDSCH. Furthermore, UEs in a wireless communication system may also support acknowledgment feedback for group-common physical downlink control channels (PDCCH) and PDSCHs (e.g., multicast data) as well as group-common transmissions. However, configuring slot-level repetition for group-common PDSCHs does not yet need to be defined.

[0050]

[0061] As described herein, a UE may consist of one or more group-common PDSCHs, such as a group-common dynamic PDSCH, one or more group-common SPS PDSCHs, or a combination thereof, where the group-common PDSCHs are further configured with repetitions. One or more group-common dynamic PDSCHs may include cyclic redundancy checks (CRCs) scrambled by different group radio network temporary identifiers (G-RNTIs), and one or more group-common SPS PDSCHs may include CRCs scrambled by differently configured and scheduled G-RNTIs (G-CS-RNTIs). SPS PDSCHs may be associated with G-CS-RNTIs. In the first option for repetitions, a group-common PDSCH may be configured independently with a group aggregation factor (e.g., pdsch-AggregationFactor_group) to indicate a semi-static repetition for the group-common PDSCH. Alternatively, a second option for iterations is that a group-common PDSCH may be configured with a group iteration parameter (e.g., RepNum_group) to indicate a dynamic number of iterations for the group-common PDSCH. In some cases, a UE may not be configured with both options for a group-common PDSCH having the same G-RNTI, the same G-CS-RNTI, or related pairs of G-RNTI and G-CS-RNTI configured for the same group of UEs to receive the same service, but different options may be configured independently for a group-common PDSCH with different G-RNTIs or for an SPS group-common PDSCH with different GCS-RNTIs. A UE may also be configured with gaps between each iteration of a group-common PDSCH.

[0051]

[0062] Furthermore, the UE may be configured to send acknowledgment feedback for a group-common PDSCH using configured repetitions. In some cases, the UE may send acknowledgment feedback using a Type 1 or Type 2 acknowledgment codebook. In either type, the UE may determine the number of candidate opportunities to receive a group-common PDSCH and to determine acknowledgment feedback. The UE may determine the number of candidate opportunities based on the group aggregation factor, the number of group repetitions, the gap between repetitions, the feedback timing indicator field value, the slot offset, etc., where each of these factors is used depending on which type of acknowledgment codebook is used or configured.

[0052]

[0063] Aspects of this disclosure are initially described in the context of wireless communication systems. Further, aspects of this disclosure are illustrated by additional wireless communication systems, examples of repetition schemes, configurations of acknowledgment feedback, and process flows. Aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to configurations for group-common downlink channels using repetition.

[0053]

[0064] Figure 1 shows an example of a wireless communication system 100 that supports a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. 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 extended broadband communication, ultra-high reliability (e.g., mission-critical) communication, low-latency communication, communication using low-cost and low-complexity devices, or any combination thereof.

[0054]

[0065] Base stations 105 may be distributed across a geographical area to form a wireless communication system 100 and may be devices of different forms or with different capabilities. Base stations 105 and UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 in which the UEs 115 and the base station 105 can establish one or more communication links 125. The coverage area 110 may be an example of a geographical area in which base stations 105 and UEs 115 can support the communication of signals according to one or more radio access technologies.

[0055]

[0066] The UE115 may be distributed throughout the coverage area 110 of the wireless communication system 100, and each UE115 may be fixed, mobile, or both at different times. The UE115 may be devices of different forms or with different capabilities. Several exemplary UE115 are shown in Figure 1. The UE115 described herein may be capable of communicating with various types of devices, such as other UE115, 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.

[0056]

[0067] Base stations 105 may communicate with the core network 130, communicate with each other, or both. For example, base stations 105 may interface with the core network 130 through one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base stations 105 may communicate with each other over the backhaul links 120 (e.g., via X2, Xn, or other interfaces) either directly (e.g., directly between base stations 105) or indirectly (e.g., via the core network 130), or both. In some examples, the backhaul links 120 may be one or more wireless links, or include them.

[0057]

[0068] One or more of the base stations 105 described herein may include, or be referred to as, a base transceiver station, a radio base station, an access point, a radio transceiver, a node B, an e-node B (eNB), a next-generation node B or giganode B (any of which may be called a gNB), a home node B, a home e-node B, or other preferred terms.

[0058]

[0069] UE115 may include, or may be referred to as, a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other appropriate term, where “device” may also be referred to as a unit, station, terminal, or client, among other examples. UE115 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, UE115 may include, or may be referred to as, a wireless local loop (WLL) station, an Internet of Things (IoT) device, any Internet of Things (IoE) device, or a machine-type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters.

[0059]

[0070] The UE115 described herein may be capable of communicating with other UE115s that may sometimes function as relays, as well as various types of devices, including, among other examples, a macro eNB or gNB, a small cell eNB or gNB, or a base station 105 and network equipment including a relay base station.

[0060]

[0071] UE115 and base station 105 may communicate wirelessly with each other via one or more communication links 125 through 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 communication links 125. For example, a carrier used for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquired signaling (e.g., synchronization signals, system information), control signaling to coordinate carrier operation, user data, or other signaling. The wireless communication system 100 may support communication with UE115 using carrier aggregation or multi-carrier operation. UE115 may consist of multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation can be used with both frequency-division duplex (FDD) component carriers and time-division duplex (TDD) component carriers.

[0061]

[0072] In some examples (for instance, in carrier aggregation configurations), a carrier may also have acquisition or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Advanced Universal Mobile Communications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be arranged according to a channel raster for discovery by the UE115. A carrier may operate in a standalone mode where initial acquisition and connection are performed by the UE115 via the carrier, or it may operate in a non-standalone mode where connection is anchored using different carriers (e.g., of the same or different radio access technology).

[0062]

[0073] The communication link 125 shown in the wireless communication system 100 may include uplink transmissions from UE 115 to base station 105, or downlink transmissions from base station 105 to UE 115. The carrier may carry downlink communications or uplink communications (for example, in FDD mode), or may be configured to carry downlink communications and uplink communications (for example, in TDD mode).

[0063]

[0074] 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 carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of several predetermined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) for the carrier of a particular radio access technology. Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication over a specific carrier bandwidth, or may be configurable to support communication over one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication over carriers related to multiple carrier bandwidths. In some examples, each serviced UE 115 may be configured to operate over a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0064]

[0075] The signal waveform transmitted over a carrier can consist of multiple subcarriers (for example, using multicarrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM). In systems utilizing MCM techniques, a resource element may consist of one symbol period (e.g., duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements the UE115 receives, and the higher the order of the modulation scheme, the higher the data rate for the UE115 can be. Wireless communication resources can refer to a combination of radio frequency spectral resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity for communication with the UE115.

[0065]

[0076] One or more numerologies may be supported for a carrier, where the numerology may include a subcarrier interval (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, UE115 may consist of multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communication for UE115 may be limited to one or more active BWPs.

[0066]

[0077] The time interval for base station 105 or UE115 is, for example, T s = 1 / (Δf max ·N f It can represent a sampling period of ) seconds, and can be expressed in multiples of basic time units, where Δf max This can represent the maximum supported subcarrier interval, N f This may represent the maximum supported Discrete Fourier Transform (DFT) size. The time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0067]

[0078] Each frame may contain multiple sequentially numbered subframes or slots, each subframe or slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into several slots. Alternatively, each frame may contain a variable number of slots, the number of slots may depend on the subcarrier interval. Each slot may contain several symbol periods (e.g., depending on the length of the cyclic prefix prepared for each symbol period). In some wireless communication systems 100, a slot may be further divided into multiple minislots containing one or more symbols. Except for the cyclic prefix, each symbol period may contain one or more (e.g., N) symbols. f This may include the sampling period. The duration of the symbol period may depend on the subcarrier interval or frequency operating bandwidth.

[0068]

[0079] A subframe, slot, minislot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be called a transmit time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in the TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0069]

[0080] Physical channels can be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels can be multiplexed on a downlink carrier using, for example, one or more of the following techniques: time-division multiplexing (TDM), frequency-division multiplexing (FDM), or hybrid TDM-FDM. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by several symbolic periods and may extend across the carrier's system bandwidth or a subset of the system bandwidth. One or more control regions (e.g., a CORESET) may be configured for a set of UE115s. For example, one or more of the UE115s may monitor or search for control regions for control information according to one or more search space sets, each search space set may contain one or more control channel candidates in one or more aggregation levels configured in a cascaded manner. An aggregation level for a control channel candidate may refer to several control channel resources (e.g., control channel elements (CCEs)) related to encoded information for a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UE115s, and a UE-specific search space set for sending control information to a specific UE115.

[0070]

[0081] Each base station 105 may provide communication coverage through one or more cells, such as macrocells, small cells, hotspots, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with base station 105 (for example, on a carrier) and may be associated with an identifier for distinguishing neighboring cells (for example, a physical cell identifier (PCID), a virtual cell identifier (VCID), or something else). In some examples, a cell may also refer to a geographical coverage area 110 or a portion of a geographical coverage area 110 (for example, a sector) on which the logical communication entity operates. Such cells may span from smaller areas (for example, structures, subsets of structures) to larger areas, depending on various factors such as the capabilities of base station 105. For example, a cell may be, among other examples, a building, a subset of a building, or external space between or overlapping with geographical coverage areas 110, or include them.

[0071]

[0082] Macrocells generally cover relatively large geographical areas (e.g., a radius of several kilometers) and can enable unrestricted access by UE115s subscribed to the services of a network provider that supports macrocells. Small cells, compared to macrocells, may be associated with low-power base stations 105 and may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macrocells. Small cells may provide unrestricted access to UE115s subscribed to the services of a network provider, or they may provide restricted access to UE115s associated with small cells (e.g., UE115s in limited subscriber groups (CSGs), UE115s associated with users in their homes or offices). 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.

[0072]

[0083] In some cases, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)) that can provide access to different types of devices.

[0073]

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

[0074]

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

[0075]

[0086] Some UE115s, such as MTC devices or IoT devices, may be low-cost or low-complexity devices that can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that enables devices to communicate with each other or with base stations 105 without human intervention. In some examples, M2M communication or MTC may include communication from devices that incorporate sensors or meters to measure or capture information, utilize the information, or relay such information to a central server or application program that presents the information to a human who interacts with the application program. Some UE115s may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security detection, physical access control, and billing for transaction-based businesses.

[0076]

[0087] Some UE115s may be configured to employ power-saving operating modes such as half-duplex communication (e.g., modes that support one-way communication via transmit or receive rather than transmit and receive simultaneously). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for the UE115 include entering a power-saving deep sleep mode when not engaged in active communication, operating on a limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE115s may be configured for operation using narrowband protocol types associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within the carrier, within the carrier's protected band, or outside the carrier.

[0077]

[0088] The wireless communication system 100 may be configured to support ultra-reliable low-latency communication, 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 functions, low-latency functions, or critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private or group communications 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 service prioritization, 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.

[0078]

[0089] In some examples, a UE115 may also be able to communicate directly with other UE115s over a device-to-device (D2D) communication link 135 (for example, using peer-to-peer (P2P) or D2D protocols). One or more UE115s utilizing D2D communication may be within the geographical coverage area 110 of the base station 105. Other UE115s in such a group may be outside the geographical coverage area 110 of the base station 105, or otherwise unable to receive transmissions from the base station 105. In some examples, a group of UE115s communicating via D2D communication may utilize a one-to-many (1:M) system where each UE115 transmits to any other UE115 in the group. In some examples, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication occurs between UE115s without the involvement of the base station 105.

[0079]

[0090] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an advanced packet core (EPC) or 5G core (5GC) that includes 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 interconnections to the 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 may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management, for UE 115 serviced by base station 105 associated with the core network 130. User IP packets may be forwarded through user plane entities that may provide IP address allocation and other functions. A user plane entity may be connected to an IP service 150 for one or more network operators. The IP service 150 may include access to the Internet, (one or more) intranets, IP multimedia subsystems (IMS), or packet-switched streaming services.

[0080]

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

[0081]

[0092] The wireless communication system 100 may typically operate using one or more frequency bands in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band, as the wavelengths range from approximately 1 decimeter to 1 meter. While UHF waves may be blocked or redirected by buildings and environmental features, these waves can penetrate structures well enough to serve a UE 115 where a macrocell is located indoors. Transmitting UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmitting using lower frequencies and longer waves in the shortwave (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0082]

[0093] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ Licensed Auxiliary Access (LAA), Unlicensed LTE (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz Industrial Scientific and Medical (ISM) band. Devices such as base station 105 and UE 115 may employ carrier detection for collision detection and avoidance when operating in unlicensed radio frequency spectrum bands. In some examples, operation in unlicensed bands may be based on a carrier aggregation configuration with component carriers operating in licensed bands (e.g., LAA). Operation in unlicensed spectrums may include, among other examples, downlink transmission, uplink transmission, P2P transmission, or D2D transmission.

[0083]

[0094] Base station 105 or UE115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE115 may 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 may be collated in an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with base station 105 may be located in a variety of geographical locations. Base station 105 may have an antenna array with several rows and columns of antenna ports that base station 105 can use to support beamforming of communication with UE115. Similarly, UE115 may have one or more antenna arrays that can support various MIMO or beamforming operations. As an addition or alternative, an antenna panel may support radio frequency beamforming for signals transmitted through the antenna ports.

[0084]

[0095] A base station 105 or UE115 may use MIMO communication to leverage multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals through different spatial layers. Such techniques are sometimes called spatial multiplexing. Multiple signals may be transmitted by a transmitting device through different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device through different antennas or different combinations of antennas. Each of the multiple signals may be called a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0085]

[0096] Beamforming, sometimes called spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used in a transmitting or receiving device (e.g., base station 105, UE115) to shape or guide an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals communicated through the antenna elements of an antenna array such that several signals propagating in a particular orientation relative to the antenna array experience constructive interference and others experience destructive interference. Coordination of signals communicated through antenna elements may include the transmitting or receiving device applying amplitude offset, phase offset, or both to the signals carried through the antenna elements associated with the device. Coordination associated with each antenna element may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device, or to some other orientation).

[0086]

[0097] The base station 105 or UE 115 may use beam sweep techniques as part of its beamforming operation. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Several signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the base station 105 in different directions. For example, the base station 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmissions in various beam directions may be used to identify the beam direction for subsequent transmission or reception by the base station 105 (e.g., by a transmitting device such as the base station 105, or by a receiving device such as the UE 115).

[0087]

[0098] Some signals, such as data signals associated with a specific receiving device, may be transmitted by the base station 105 in a single beam direction (for example, a direction associated with a receiving device such as UE115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE115 may receive one or more signals transmitted by the base station 105 in various directions and report to the base station 105 an indication of the signals received by UE115 at the best or otherwise acceptable signal quality.

[0088]

[0099] In some examples, transmission by a device (e.g., by base station 105 or UE115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a composite beam for transmission (e.g., from base station 105 to UE115). UE115 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 (e.g., cell-specific reference signals (CRS), channel status information reference signals (CSI-RS)) that can be precoded or amplified. UE115 may provide feedback for beam selection, which may be precoding matrix indicators (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). While these techniques have been described in relation to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques for transmitting signals multiple times in different directions (for example, to identify beam directions for subsequent transmission or reception by UE 115) or for transmitting signals in a single direction (for example, to transmit data to a receiving device).

[0089]

[0100] A receiving device (e.g., UE115) may attempt multiple receiving configurations (e.g., directional listening) when receiving various signals from a base station 105, such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may attempt multiple receiving directions by receiving through different antenna subarrays, by processing the received signal according to different antenna subarrays, by receiving according to different sets of receive beamforming weights (e.g., different directional listening weight sets) applied to the received signal at multiple antenna elements of an antenna array, or by processing the received signal according to different sets of receive beamforming weights applied to the received signal at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, a receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receiving configuration can be aligned to a beam direction determined based on listening according to various receiving configuration directions (for example, a beam direction determined to have the highest signal strength, the highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0090]

[0101] The wireless communication system 100 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. The Radio Link Control (RLC) layer may perform packet segmentation and reassembly for communication over logical channels. The Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels to transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may establish, configure, and maintain RRC connections between the UE 115 and the base station 105 or core network 130, supporting radio bearers for user plane data. At the physical layer, transport channels may be mapped to physical channels.

[0091]

[0102] UE115 and base station 105 may support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Retransmission Request (ARQ) feedback is one technique to increase the likelihood of successful data reception over communication link 125. HARQ may include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Retransmission Request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise conditions). In some examples, devices may support same-slot HARQ feedback, where the device may provide HARQ feedback in a particular slot for data received in the previous symbol in that slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0092]

[0103] A wireless device in the wireless communication system 100 may support the repetition of semi-static PDSCHs in consecutive slots. For example, UE 115 may consist of an aggregation factor (e.g., pdsch-AggregationFactor) in a configuration message for a PDSCH (e.g., pdsch-Config) to indicate a semi-static repetition, where UE applies the aggregation factor to a unicast dynamic PDSCH, a unicast SPS PDSCH, or both. Furthermore, the wireless device may support the repetition of semi-static or dynamic PDSCHs in consecutive slots. For example, in the case of URLLC, UE 115 may consist of two or more unicast SPS PDSCHs. In some cases, the aggregation factor (e.g., pdsch-AggregationFactor) for an SPS PDSCH per configuration message (e.g., sps-Config) may differ from the aggregation factor of the unicast dynamic PDSCH in the corresponding configuration message (e.g., pdsch-Config) and may differ based on the BWP for different PDSCHs.

[0093]

[0104] In a multi-transmit / receive point (TRP) configuration (for example, if UE115 includes multiple TRPs for communication with different devices, communication in different directions, etc.), UE115 may be configured with a repetitive dynamic instruction (e.g., RepNumR16) included in one entry of the Time-Domain Resource Allocation (TDRA) table for PDSCH. However, when UE115 is configured with a repetitive dynamic instruction (e.g., RepNumR16), UE115 may not expect to be configured with a repetitive semi-static instruction (e.g., pdsch-AggregationFactor). In other words, if UE115 is configured with a higher-layer parameter for PDSCH repetition (e.g., repetitionNumber-16), or if UE115 is configured with a different repetition scheme (e.g., repetitionSchemeConfig-r16) set to a specific multiplexing scheme (e.g., one of FDMSchemeA, FDMSchemeB, and TDMSchemeA), then UE115 may not expect to be configured with a semi-static instruction for repetition (e.g., pdsch-AggregationFactor or pdsch-AggregationFactor-r16).

[0094]

[0105] Furthermore, a UE 115 in the wireless communication system 100 (for example, in an RRC connection state with a base station 105 or a different wireless device) may support a group-common PDSCH with a CRC scrambled by a common radio network temporary identifier (RNTI) to schedule a group-common physical downlink control channel (PDCCH), where the scrambling of the group-common PDSCH is based on the same common RNTI. The UE 115 may also support HARQ acknowledgment (HARQ-ACK) feedback for multicast transmissions (for example, group-common messages). In addition, the UE 115 may support FDM between unicast PDSCHs and group-common PDSCHs in a slot, depending on the capabilities of the UE. The UE 115 may also support slot-level repetition for group-common PDSCHs. However, the configuration for slot-level repetition for group-common PDSCHs does not yet need to be decided or determined.

[0095]

[0106] The wireless communication system 100 may support efficient techniques for signaling configurations for a group-common downlink channel (e.g., a group-common PDSCH) using repetitions for a group-common downlink channel. For example, UE 115 may receive a configuration for a group-common PDSCH, where the configuration includes an instruction that the group-common PDSCH will be repeated a number of times. In some implementations, the group-common PDSCH may include one or more group-common dynamic PDSCHs, one or more group-common SPS PDSCHs, or a combination thereof. Thus, UE 115 may determine this number of repetitions and then monitor the group-common PDSCH based on the number of repetitions. In some implementations, the group-common PDSCH may include a semi-static repetition scheme, where the number of repetitions is indicated via a group aggregation factor. As an addition or alternative, the group-common PDSCH may include a dynamic repetition scheme, where the number of repetitions is indicated via a group repetition count. Furthermore, the techniques described herein may allow configurations for repeated group-common PDSCHs to include gaps between each iteration of the group-common PDSCH, and may allow UE115 to transmit acknowledgment feedback (e.g., HARQ-ACK feedback) for the iterations of the group-common PDSCH.

[0096]

[0107] Figure 2 shows an example of a wireless communication system 200 that supports a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. The wireless communication system 200 may implement an aspect of the wireless communication system 100. For example, the wireless communication system 200 may include base stations 105-a, UE115-a, UE115-b, and UE115-c, which may represent examples of the corresponding base stations 105 and UE115, respectively, as described with reference to Figure 1.

[0097]

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

[0098]

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

[0099]

[0110] In some implementations, a group-common dynamic downlink sharing channel (e.g., one or more downlink sharing channels) may include a downlink sharing channel configured by base station 105-a and transmitted to UE 115 as needed. For example, if base station 105-a determines that downlink data is available for transmission to UE 115 (e.g., multicast data), base station 105-a may transmit a downlink control channel (e.g., a group-common downlink control channel, group-common PDCCH, etc.) that schedules a dynamic downlink sharing channel to carry the downlink data to UE 115. As an addition or alternative, a group-common SPS downlink sharing channel may include a semi-persistently allocated downlink sharing channel that can be used to carry downlink data (e.g., multicast data) to UE 115. For example, base station 105-a may configure resources that occur periodically (e.g., per slot, every other slot, etc.), where base station 105-a can use the resources to transmit downlink data without having to configure the resources for each transmission (e.g., a single configuration may represent multiple instances available for subsequent transmissions). In some implementations, base station 105-a may also activate or deactivate a group-common SPS downlink shared channel as needed (e.g., it may be activated when a sufficient amount of downlink data should be transmitted to UE115).

[0100]

[0111] As shown in the figure, base station 105-a may communicate with UE115-a on the resources of carrier 205-a, with UE115-b on the resources of carrier 205-b, and with UE115-c on the resources of carrier 205-c. For example, base station 105-a may send multicast messages and data to each UE115 on the corresponding carrier 205. Before sending multicast messages and data to the UE115, base station 105-a may first send configuration 210 to each UE115 (for example, in a PDCCH that schedules a PDSCH for multicast messages and data). In some implementations, configuration 210 may indicate a number of repeating group-common downlink shared channels 215, including two or more repetitions of the group-common downlink shared channel 220.

[0101]

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

[0102]

[0113] The default value for the group aggregation factor for group-common dynamic downlink sharing channels may be defined similarly to the default value for unicast dynamic downlink sharing channels (in which case the UEs monitoring the same group-common dynamic PDSCH are configured with the same unicast dynamic downlink sharing channel), or it may be predefined as 1 (for example, one instance of the group-common dynamic downlink sharing channel is sent unless configured with a repetition count). Additionally or alternatively, the default value for the group aggregation factor for group-common SPS downlink sharing channels may be defined similarly to the default value for group-common dynamic downlink sharing channels with G-RCTIs related to G-CS-RCTIs (for example, corresponding to the same service), or similarly to the default value for unicast dynamic downlink sharing channels, or it may be predefined as 1.

[0103]

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

[0104]

[0115] For the choice between a semi-static and a dynamic repetition scheme, UE115 may not be configured with both a semi-static and a dynamic repetition scheme for a repeating group-common downlink shared channel 215 having the same G-RNTI, the same G-CS-RNTI, or related pairs of G-RNTI and G-CS-RNTI configured in the same group of UEs to receive the same service. Additionally or alternatively, base station 105-a may independently configure a semi-static and a dynamic repetition scheme for a group-common downlink shared channel 215 based on different G-RNTI or G-CS-RNTI.

[0105]

[0116] In some implementations, gaps may occur between each iteration of the repeating group-common downlink shared channel 215. Therefore, instead of causing each iteration for the repeating group-common downlink shared channel 215 to occur in consecutive slots, the base station 105-a may be configured to cause the iterations in one or more slots in between each iteration. Techniques for creating gaps between slots will be described in more detail with reference to Figure 3B.

[0106]

[0117] Furthermore, after monitoring and receiving the repeated group-common downlink shared channel 215, the UE 115 may send acknowledgment feedback 225 based on whether it successfully receives and decodes the group-common downlink shared channel 220 or does not use the repeated group-common downlink shared channel 215 (for example, by combining repetitions). For example, the acknowledgment feedback 225 may include HARQ-ACK feedback such as an acknowledgment (ACK) message to indicate successful reception and decoding of the group-common downlink shared channel 220 or a negation (NACK) message to indicate failed reception or decoding of the group-common downlink shared channel 220. Techniques for determining the acknowledgment feedback 225 based on the repeated group-common downlink shared channel 215 will be described in more detail with reference to Figure 4B.

[0107]

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

[0108]

[0119] As described above, the repetition scheme 300 may represent a unicast PDSCH 315 using repetition in consecutive slots. For example, base station 105 may transmit a PDCCH 305 that schedules a repeating PDSCH 310 for UE 115 to monitor and receive (e.g., via the configuration for PDSCH). PDCCH 305 may also indicate the number of repetitions to which the unicast PDSCH 315 is transmitted (e.g., via the pdsch-AggregationFactor or RepNumR16 as described with reference to Figure 1). For example, PDCCH305 may indicate four repetitions of a unicast PDSCH315 for repeating PDSCH315, such as a first unicast PDSCH315-a (e.g., the first repetition), a second unicast PDSCH315-b (e.g., the second repetition), a third unicast PDSCH315-c (e.g., the third repetition), and a fourth unicast PDSCH315-d (e.g., the fourth repetition). Furthermore, in some cases, PDCCH305 may include an indication of a slot offset (K0) representing several slots (e.g., or transmission time intervals of different lengths) between the end of PDCCH305 and the first unicast PDSCH315-a.

[0109]

[0120] Similarly, the repetition scheme 301 may include a PDCCH320 transmitted by the base station 105, where the PDCCH320 schedules a set of repeating PDSCH325s. The set of repeating PDSCH325s may include repetitions of PDSCH330s (indicated, for example, via the group aggregation factor pdsch-AggregationFactor_group or group repetition number RepNum_group, as described with reference to Figure 2), such as a first PDSCH330-a (e.g., the first repetition), a second PDSCH330-b (e.g., the second repetition), a third PDSCH330-c (e.g., the third repetition), and a fourth PDSCH330-d (e.g., the fourth repetition). Furthermore, the PDCCH320 may also include an indication of a slot offset K0. However, rather than being a unicast PDSCH as described with reference to Figure 3A, PDSCH330 could be a group-common PDSCH (for example, a group-common downlink shared channel) transmitted to multiple UE115s.

[0110]

[0121] Furthermore, the repetition scheme 301 may include gap configurations for group-common PDSCH repetitions. For example, a gap 335 may occur between each repetition of the group-common PDSCH 330. In the case of slot-level repetitions, gaps 335 with gap values ​​of 0 or greater (e.g., gap 335 ≥ 0) (e.g., several gap slots) may be configured between group-common PDSCH repetitions. If the gap is equal to 0, the repetitions of the PDSCH 330 may be continuous (e.g., no slots occur between repetitions). The gap 335 may include absolute time slots in terms of the BWP numerology for the group-common PDSCH 330 (e.g., including downlink / uplink slots). Furthermore, gaps 335 may be independent for group-common dynamic PDSCHs and for each group-common SPS PDSCH.

[0111]

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

[0112]

[0123] Figures 4A and 4B show examples of acknowledgment feedback 400 and 401 supporting a configuration for a group-common downlink channel using repetition, according to aspects of the present disclosure. Acknowledgment feedback 400 and 401 may implement aspects of wireless communication systems 100 and 200. For example, UE 115 may use acknowledgment feedback 400 or 401 to send an acknowledgment message to a base station indicating whether the downlink shared channel using repetition has been successfully received and decoded.

[0113]

[0124] The acknowledgment feedback 400 may represent a unicast PDSCH repeat configuration, where PDCCH405 schedules a set of repeating PDSCH410s including a first unicast PDSCH415-a (e.g., the first repeat), a second unicast PDSCH415-b (e.g., the second repeat), a third unicast PDSCH415-c (e.g., the third repeat), and a fourth unicast PDSCH415-d (e.g., the fourth repeat). In some implementations, PDCCH405 may include a slot offset (K0) indication representing several slots (e.g., or transmission time intervals of different lengths) between the end of PDCCH405 and the first unicast PDSCH415-a. Furthermore, PDCCH405 may include an indication of a feedback indicator field value (e.g., PDSCH-to-HARQ_feedback timing indicator field value) K1 representing several slots (e.g., or transmission time intervals of different lengths) between the last occurring PDSCH (e.g., the fourth unicast PDSCH415-d) and the uplink channel (e.g., the physical uplink control channel (PUCCH)) carrying the ACK / NACK420 (e.g., the acknowledgment feedback message). The ACK / NACK420 may include an indication of whether UE115 successfully received and decoded the PDSCH415 using a set of repeated PDSCH410s.

[0114]

[0125] When sending an ACK / NACK420 (for example, for a PDSCH using repetition), the UE115 may use a HARQ-ACK codebook. For example, in the case of a Type 1 HARQ-ACK codebook, the UE115 will use the M of the candidate PDSCH repetition. A,c A single HARQ-ACK feedback can be given for the set of opportunities, where the timeline is counted at the end of the slot repetition. For a semi-static repetition scheme, M for receiving candidate PDSCH A,cThe set of opportunities may be determined based on the maximum value of the aggregation factor (e.g., pdsch-AggregationFactor) (if given, for example, during sps-Config and / or pdsch-Config). For dynamic iteration schemes,

[0115]

number

[0116] And the last PDSCH reception may be determined based on the indicated repetition number (e.g., RepNumR16). That is, if UE115 is given an aggregation factor (e.g., pdsch-AggregationFactor) in a 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) containing the repetition number (e.g., RepNumR16) in the time domain allocation list (e.g., PDSCH-TimeDomainResourceAllocation),

[0117]

number

[0118] This could be the maximum value of the aggregation factor (e.g., pdsch-AggregationFactor) in the corresponding configuration message for PDSCH (for example, in SPS-Config or PDSCH-Config), otherwise,

[0119]

number

[0120] That is the case.

[0121]

[0126] When using a Type 1 HARQ-ACK codebook, the UE115 is:

[0122]

number

[0123] If the slot is given by an aggregation factor (e.g., pdsch-AggregationFactor), then

[0124]

number

[0125] HARQ-ACK information for PDSCH reception may be reported between slot n and slot n, or between slot n-RepNumR16+1 and slot n if the time domain resource allocation field in the DCI format that schedules PDSCH reception indicates an entry in the time domain allocation list (e.g., pdsch-TimeDomainAllocationList) that includes the number of repetitions (e.g., RepNumR16), or otherwise in slot n.

[0126]

[0127] As an addition or alternative, when sending ACK / NACK420 using the Type 2 HARQ-ACK codebook, the HARQ-ACK bit for dynamic or SPS PDSCH with repetitions may correspond to a PDSCH monitoring opportunity based on the feedback timing indicator field value (K1) (e.g., PDSCH-to-HARQ_feedback timing indicator field value), the slot offset (K0), and the PDSCH repetition count (e.g., pdsch-AggregationFactor or RepNumR16) when given. In other words, for a type 2 HARQ-ACK codebook in an uplink control channel (e.g., PUCCH), UE115 may determine an opportunity to monitor for a PDCCH having a DCI format that schedules the reception of a PDSCH or the release of an SPS PDSCH on the active DL BWP of serving cell c, and the UE transmits the HARQ-ACK information in the same PUCCH in slot n based on K1 (e.g., the PDSCH-to-HARQ_feedback timing indicator field value) for a PUCCH transmission with HARQ-ACK information in slot n in response to the reception of a PDSCH or the release of an SPS PDSCH, and based on K0 (slot offset) given by the time-domain resource allocation field in the DCI format that schedules the reception of a PDSCH or the release of an SPS PDSCH, and, when given, by the aggregation factor or repetition count (e.g., pdsch-AggregationFactor or RepNumR16).

[0127]

[0128] Similarly, the acknowledgment feedback 401 may include a PDCCH425 transmitted by the base station 105, where the PDCCH425 schedules a set of repeated PDSCH430s. The set of repeated PDSCH430s may include repetitions of PDSCH435s such as a first PDSCH435-a (e.g., the first repetition), a second PDSCH435-b (e.g., the second repetition), a third PDSCH435-c (e.g., the third repetition), and a fourth PDSCH435-d (e.g., the fourth repetition) (indicated, for example, via the group aggregation factor pdsch-AggregationFactor_group or group repetition number RepNum_group, as described with reference to Figure 2). Furthermore, PDCCH425 may also include an instruction for slot offset K0 and a feedback timing indicator field value K1 (e.g., PDSCH-to-HARQ_feedback timing indicator field value). However, rather than being a unicast PDSCH as described with reference to Figure 4A, PDSCH435 may be a group-common PDSCH (e.g., a group-common downlink shared channel) sent to multiple UE115s.

[0128]

[0129] Furthermore, the acknowledgment feedback 401 may include a gap 440 between each repetition of the PDSCH435 (as illustrated, for example, with reference to Figure 3B). Based on the gap 440, if a fourth PDSCH435-d occurs in slot n, a first PDSCH435-a may occur in the slot given by (n-3(1+gap)), a second PDSCH435-b may occur in the slot given by (n-2(gap+1)), and a third PDSCH435-c may occur in the slot given by (n-(gap+1)). Subsequently, one of the multiple UE115s may send an ACK / NACK445 to indicate whether or not the UE115 has successfully received and decoded the PDSCH435 using a set of PDSCH430s that are repeated (for example, after K1).

[0129]

[0130] Further, UE115 may use a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook when transmitting ACK / NACK 445 for a group-common set of repeated PDSCHs 430 (e.g., multicast data). For example, if a type 1 HARQ-ACK codebook is configured for group-common PDSCH 435, and the group-common PDSCH 435 is configured with (e.g., as described while referring to FIG. 2) a semi-static repetition, the set of M A,c opportunities for receiving the candidate PDSCH is

[0130]

Number

[0131] used to determine from slot

[0132]

Number

[0133] to slot n. That is,

[0134]

Number

[0135] may represent the maximum value of the group aggregation factor (e.g., pdsch-AggregationFactor) and the gap 440 in the configuration of the group-common dynamic PDSCH and the group-common SPS PDSCH with related G-RNTI and G-CS-RNTI in the same BWP (e.g., corresponding to the same service). For each gap opportunity, UE115 may be configured to send a NACK, repeat ACK / NACK based on the reception of the PDSCH, or do nothing.

[0136]

[0131] In addition or alternative, if a Type 1 HARQ-ACK codebook is configured for a group-common PDSCH435, and the group-common PDSCH435 is configured for dynamic repetition (as described with reference to Figure 2, for example), then UE115 is:

[0137]

number

[0138] Using slots

[0139]

number

[0140] It can be determined that the range is from slot n. In some cases,

[0141]

number

[0142] For example, if a TDRA table for a group-common PDSCH has a row containing the group repetition count (e.g., RepNum_group), the repetition of the PDSCH configured via the group aggregation factor (e.g., pdsch-AggregationFactor_group) may not be applied.

[0143]

[0132] As an addition or alternative, if a Type 2HARQ-ACK codebook is configured for a group-common PDSCH435, the PDCCH monitoring opportunity on the serving cell's active downlink BWP may be determined by K1 (e.g., the PDSCH-to-HARQ_feedback timing indicator field value between the last iteration of the group-common PDSCH435 and the PUCCH carrying the ACK / NACK445), K0 (e.g., the slot offset between PDCCH425 and the first iteration of the group-common PDSCH435), the number of iterations for the group-common PDSCH (e.g., given by pdsch-AggregationFactor_group or RepNum_group), and (e.g., if configured) the gap 440. If the group-common PDSCH435 is configured in a semi-static repetitive manner, PDCCH monitoring opportunities may be based on K1, K0, and (pdsch-AggregationFactor_group+(pdsch-AggregationFactor_group-1)Gap). Alternatively, if the group-common PDSCH435 is configured in a dynamic repetitive manner, PDCCH monitoring opportunities may be based on K1, K0, and (RepNum_group+(RepNum_group-1)Gap).

[0144]

[0133] Figure 5 shows an example of a process flow 500 that supports a configuration for a group-common downlink channel using repetition, according to an aspect 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 stations 105-b and UE115-d, which may represent examples of corresponding base stations 105 and UE115, respectively, as described with reference to Figures 1 to 4B.

[0145]

[0134] 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 omitted from process flow 500, or other operations may be added to process flow 500. While it is shown that base station 105-b and UE 115-d perform some operations in process flow 500, it should be understood that any wireless device may perform the operations shown.

[0146]

[0135] In 505, base station 105-b determines the number of repetitions for a group common downlink sharing channel, which may include one or more downlink sharing channels (e.g., one or more dynamic downlink sharing channels, dynamic PDSCHs, etc.), one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof.

[0147]

[0136] In 510, UE115-d may receive a recurring configuration from base station 105-b for a group common downlink shared channel. In some implementations, the recurring configuration may include a group RNTI indicating that a group common downlink shared channel is transmitted for a set of UE115s including at least UE115-d.

[0148]

[0137] In some implementations, UE115-d may receive a semi-static repetitive configuration for a repetitive configuration from base station 105-b. For example, the semi-static repetitive 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 channels. 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 1. Additionally or alternatively, UE115-d may determine a 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 one or more group common downlink shared channels include a group RNTI associated with one or more semi-persistent group common downlink shared channels. In some implementations, the UE115-d may determine a group aggregation factor for one or more group-common downlink shared channels having a group RNTI based on the aggregation factor of the unicast downlink shared channels configured in the UE115-d.

[0149]

[0138] As an addition or alternative, UE115-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 count parameter via TDRA instruction, where the repetition count is determined based on the group repetition count parameter.

[0150]

[0139] In 515, UE115-d may receive a gap configuration from base station 105-b, which includes instructions for gaps that occur between repetitions of a group-common downlink shared channel. For example, UE115-d may receive the gap configuration from base station 105-b semistatically via RRC signaling, dynamically via TDRA instructions including gap values, or a combination thereof. In some implementations, the gap may consist of several slots between each repetition of the group-common downlink shared channel, where the length of each slot is based on the configuration of the BWP used to carry the group-common downlink shared channel. Furthermore, the gap may be configured independently for one or more downlink shared channels and one or more semi-persistent downlink shared channels. In some implementations, the number of repetitions combined with the gap between repetitions may not exceed the period configured for the semi-persistent downlink shared channel.

[0151]

[0140] In 520, UE115-d may determine the number of repetitions for a group-common downlink shared channel based on the repetition configuration.

[0152]

[0141] In 525, the UE115-d may monitor the group-common downlink shared channel from the base station based on the determined repetition count.

[0153]

[0142] In 530, base station 105-b may transmit a group common downlink shared channel to one or more UE115s, including UE115-b, based on a determined number of repetitions.

[0154]

[0143] In 535, UE115-d may send an acknowledgment feedback message to base station 105-b for a group common downlink shared channel based on monitoring, where the acknowledgment feedback message indicates a successful or failed reception of the group common downlink shared channel based on the repetition count. In some implementations, UE115-d may receive from base station 105-b a configuration for a type 1 acknowledgment codebook for sending an acknowledgment feedback message. Thus, UE115-d may determine a set of opportunities for monitoring the group common downlink shared channel based on the repetition count and a gap value representing the gap between each repetition of the group common downlink shared channel, and send a single acknowledgment feedback message to base station 105-b for the set of opportunities based on the type 1 acknowledgment codebook.

[0155]

[0144] As an addition or alternative, UE115-d may receive from base station 105-b a configuration for a Type 2 acknowledgment codebook for sending acknowledgment feedback messages. Thus, UE115-d may determine a set of opportunities for monitoring the group common downlink shared channel based on a feedback timing indicator field value between the last iteration of the group common downlink shared channel and an acknowledgment feedback message (e.g., K1), an offset value between the downlink control channel carrying the iteration configuration and the first iteration of the group common downlink shared channel (e.g., K0), the number of iterations, a gap value representing the gap between each iteration of the group common downlink shared channel, or a combination thereof. UE115-d may then send acknowledgment feedback messages for multiple opportunities to base station 105-b based on the Type 2 acknowledgment codebook.

[0156]

[0145] Figure 6 shows a block diagram 600 of device 605 supporting a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. Device 605 may be an example of an aspect of UE115 described herein. Device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. Device 605 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0157]

[0146] The receiver 610 may be provided with means for receiving information such as packets, user data, control information, or any combination thereof, related to various information channels (for example, control channels, data channels, and information channels related to the configuration for a group common downlink channel using repetition). The information may be passed to other components of device 605. The receiver 610 may use a single antenna or a set of multiple antennas.

[0158]

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

[0159]

[0148] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for implementing various aspects of the configuration for a group common downlink channel using the repetitions described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may support a method for implementing one or more of the functions described herein.

[0160]

[0149] In some examples, the communications manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may be implemented in hardware (for example, in communications management circuits). 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 gates or transistor logic, individual hardware components, or any combination thereof configured to perform or supporting the functions described herein. In some examples, a processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (for example, by the processor executing instructions stored in the memory).

[0161]

[0150] In addition or alternatively, in some examples, the communications manager 620, receiver 610, transmitter 615, or various combinations thereof or their components may be implemented in code executed by a processor (for example, as communications management software or firmware). When implemented in code executed by a processor, the functions of the communications manager 620, receiver 610, transmitter 615, or various combinations thereof or their components may be implemented by a general-purpose processor, DSP, central processing unit (CPU), ASIC, FPGA, or any combination of these or other programmable logic devices (for example, configured as a means for performing or supporting the functions described herein).

[0162]

[0151] In some examples, the communications manager 620 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both in order to receive information, transmit information, or perform various other operations described herein.

[0163]

[0152] The communication manager 620 may support wireless communication in the UE in accordance with the examples disclosed herein. For example, the communication manager 620 may be configured or support means for receiving a repetition configuration from a base station for a group common downlink sharing channel, the group common downlink sharing channel may include one or more downlink sharing channels, one or more semi-persistent downlink sharing channels distinct from one or more downlink sharing channels, or a combination thereof. The communication manager 620 may be configured or support means for determining the number of repetitions for the group common downlink sharing channel based on the repetition configuration. The communication manager 620 may be configured or support means for monitoring the group common downlink sharing channel from the base station based on the determined number of repetitions.

[0164]

[0153] By including or configuring the communications manager 620 according to the examples described herein, the device 605 (e.g., a processor controlling or coupled to a receiver 610, a transmitter 615, a communications manager 620, or a combination thereof) may support techniques for improving reliability for group common messages. For example, repetition for a group common downlink shared channel may increase the likelihood that the UE 115 will successfully receive and decode the group common downlink shared channel (e.g., by combining different repetitions of the group common downlink shared channel).

[0165]

[0154] Figure 7 shows a block diagram 700 of device 705 supporting a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. Device 705 may be an example of an aspect of device 605 or UE115 described herein. Device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. Device 705 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0166]

[0155] The receiver 710 may be provided with means for receiving information such as packets, user data, control information, or any combination thereof, related to various information channels (for example, control channels, data channels, and information channels related to the configuration for a group common downlink channel using repetition). The information may be passed to other components of device 705. The receiver 710 may use a single antenna or a set of multiple antennas.

[0167]

[0156] The transmitter 715 may provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets related to various information channels (e.g., control channels, data channels, information channels related to size-based neural network selection for autoencoder-based communication), user data, control information, or any combination thereof. In some examples, the transmitter 715 may be collated with the receiver 710 in the transceiver module. The transmitter 715 may use a single antenna or a set of multiple antennas.

[0168]

[0157] Device 705 or various components thereof may be examples of means for implementing various aspects of the configuration for a group-common downlink channel using repetition as described herein. For example, the communications manager 720 may include a repetition configuration component 725, a repetition decision component 730, a group-common downlink shared channel monitoring component 735, or any combination thereof. The communications manager 720 may be an example of an aspect of the communications manager 620 as described herein. In some examples, the communications manager 720 or various components thereof may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the receiver 710, the transmitter 715, or both. For example, the communications manager 720 may receive information from the receiver 710, send information to the transmitter 715, or be integrated with the receiver 710, the transmitter 715, or both in order to receive information, transmit information, or perform various other operations as described herein.

[0169]

[0158] The communication manager 720 may support wireless communication in the UE in accordance with the examples disclosed herein. The repetition configuration component 725 is configured or supports means for receiving a repetition configuration from a base station for a group common downlink shared channel, the group common downlink shared channel may include one or more downlink shared channels, one or more semi-persistent downlink shared channels different from one or more downlink shared channels, or a combination thereof. The repetition determination component 730 may be configured or support means for determining the number of repetitions for a group common downlink shared channel based on the repetition configuration. The group common downlink shared channel monitoring component 735 may be configured or support means for monitoring the group common downlink shared channel from a base station based on the determined number of repetitions.

[0170]

[0159] Figure 8 shows a block diagram 800 of a communications manager 820 supporting a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. Communications manager 820 may be an example of an aspect of communications manager 620, communications manager 720, or both, as described herein. Communications manager 820 or various components thereof may be an example of means for implementing various aspects of the configuration for a group-common downlink channel using repetition as described herein. For example, communications manager 820 may include a repetition configuration component 825, a repetition decision component 830, a group-common downlink shared channel monitoring component 835, a semi-static repetition component 840, a dynamic repetition component 845, a gap configuration component 850, an acknowledgment feedback component 855, or any combination thereof. Each of these components may communicate with one another directly or indirectly (for example, via one or more buses).

[0171]

[0160] The communication manager 820 may support wireless communication in the UE in accordance with the examples disclosed herein. The repetition configuration component 825 is configured or supports means for receiving a repetition configuration from a base station for a group common downlink shared channel, the group common downlink shared channel may include one or more downlink shared channels, one or more semi-persistent downlink shared channels different from one or more downlink shared channels, or a combination thereof. The repetition determination component 830 may be configured or support means for determining the number of repetitions for a group common downlink shared channel based on the repetition configuration. The group common downlink shared channel monitoring component 835 may be configured or support means for monitoring the group common downlink shared channel from a base station based on the determined number of repetitions.

[0172]

[0161] In some examples, in order to support receiving a group common configuration for a downlink shared channel, the semi-static repetitive configuration 840 may be configured or support the means for receiving a semi-static repetitive configuration for a repetitive configuration from the base station.

[0173]

[0162] In some examples, in order to support receiving semi-static repetitive configurations, the semi-static repetitive configuration 840 may be configured or support the means for receiving semi-static repetitive configurations from a base station via radio resource control signaling.

[0174]

[0163] In some examples, the semi-static repeating component 840 may be configured as a means for or supporting the semi-static repeating configuration which includes a group aggregation factor, where the number of repetitions is determined based on the group aggregation factor and a group common downlink shared channel.

[0175]

[0164] In some examples, the semi-static repeating component 840 may be configured as a means for a group aggregation factor for one or more group-common downlink sharing channels or one or more semi-persistent group-common downlink sharing channels to be predefined as 1.

[0176]

[0165] In some examples, the semi-static repeating configuration 840 may be configured or support means for determining a group aggregation factor for one or more semi-persistent group-common downlink sharing channels based on a group aggregation factor for one or more group-common downlink sharing channels, where the repeating configuration includes a group radio network temporary identifier associated with one or more semi-persistent group-common downlink sharing channels.

[0177]

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

[0178]

[0167] In some examples, in order to support receiving configurations for a downlink shared channel, the dynamic repetitive configuration 845 may be configured or support the means for receiving dynamic repetitive configurations for repetitive configurations from the base station.

[0179]

[0168] In some examples, the dynamic repetition component 845 may be configured or support the dynamic repetition configuration as a means for including a group repetition count parameter via a time-domain resource allocation instruction, where the repetition count is determined based on the group repetition count parameter.

[0180]

[0169] In some examples, the gap configuration component 850 may be configured or support means for receiving a gap configuration from a base station, which includes instructions for gaps occurring between repetitions of a group common downlink shared channel.

[0181]

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

[0182]

[0171] In some examples, the gap configuration component 850 may be configured or support the means for the gap to include several slots between each repetition of the group common downlink shared channel, where the length of each slot is based on the configuration of the bandwidth portion used to carry the group common downlink shared channel.

[0183]

[0172] In some examples, the gap configuration component 850 may be configured as a means for the gap to be configured independently for one or more downlink shared channels and one or more semi-persistent downlink shared channels, or to support such configuration.

[0184]

[0173] In some examples, the gap configuration component 850 may be configured or support a means to ensure that the number of repetitions combined with the gap between repetitions does not exceed the period configured for the semi-persistent downlink shared channel.

[0185]

[0174] In some examples, the acknowledgment feedback component 855 may be configured or support means for sending an acknowledgment feedback message to a base station for a group common downlink shared channel based on monitoring, where the acknowledgment feedback message indicates a successful or failed reception of the group common downlink shared channel based on the number of repetitions.

[0186]

[0175] In some examples, the acknowledgment feedback component 855 may be configured or support means for receiving from a base station a configuration for a Type 1 acknowledgment codebook for sending an acknowledgment feedback message.

[0187]

[0176] In some examples, the acknowledgment feedback component 855 may be configured as a means for determining a set of multiple opportunities for monitoring a 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 acknowledgment feedback component 855 may be configured as a means for sending a single acknowledgment feedback message for a set of multiple opportunities based on a Type 1 acknowledgment codebook to a base station, or may be configured as a means for doing so.

[0188]

[0177] In some examples, the acknowledgment feedback component 855 may be configured or support means for receiving from the base station a configuration for a Type 2 acknowledgment codebook for sending an acknowledgment feedback message.

[0189]

[0178] In some examples, the acknowledgment feedback component 855 may be configured or supportive of 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 the last iteration of the group common downlink shared channel and an acknowledgment feedback message, an offset value between the downlink control channel carrying the iteration configuration and the first iteration of the group common downlink shared channel, the number of iterations, a gap value representing the gap between each iteration of the group common downlink shared channel, or a combination thereof. In some examples, the acknowledgment feedback component 855 may be configured or supportive of means for sending an acknowledgment feedback message for a set of multiple opportunities based on a Type 2 acknowledgment codebook to a base station.

[0190]

[0179] In some examples, the repetitive configuration component 825 may be configured as a means for including a group radio network temporary identifier indicating that a group common downlink shared channel is transmitted for a set of multiple UEs, including at least one UE.

[0191]

[0180] Figure 9 shows a diagram of a system 900 including a device 905 that supports a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. Device 905 is an example of, or may include, a component of, device 605, device 705, or UE 115 as described herein. Device 905 can wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communications manager 920, an I / O controller 910, a transceiver 915, an antenna 925, a memory 930, a code 935, and a processor 940. These components communicate electronically via one or more buses (e.g., bus 945) or may be coupled (e.g., operably, communicatively, functionally, electronically, electrically).

[0192]

[0181] The I / O controller 910 may manage input and output signals for device 905. The I / O controller 910 may also manage peripherals not built into device 905. In some cases, the I / O controller 910 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 910 may utilize an operating system, such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some other cases, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of a processor, such as processor 940. In some cases, a user may interact with device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0193]

[0182] In some cases, device 905 may include a single antenna 925. However, in some other cases, device 905 may have two or more antennas 925 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired link, or a wireless link, as described herein. For example, transceiver 915 may represent a wireless transceiver and communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for modulating packets, feeding the modulated packets to one or more antennas 925 for transmission, and demodulating packets received from one or more antennas 925. Transceiver 915 or transceiver 915 and one or more antennas 925 may be examples of transmitters 615, transmitters 715, receivers 610, receivers 710, or any combination thereof or their components, as described herein.

[0194]

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

[0195]

[0184] The processor 940 may include intelligent hardware devices (for example, 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, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in memory (for example, memory 930) in order to cause device 905 to perform various functions (for example, functions or tasks that support configuration for a group common downlink channel using repetition). For example, device 905 or components of device 905 may include the processor 940 and memory 930 coupled to the processor 940, and the processor 940 and memory 930 are configured to perform various functions as described herein.

[0196]

[0185] The communication manager 920 may support wireless communication in the UE in accordance with the examples disclosed herein. For example, the communication manager 920 may be configured or support means for receiving a repetition configuration from a base station for a group common downlink sharing channel, the group common downlink sharing channel may include one or more downlink sharing channels, one or more semi-persistent downlink sharing channels distinct from one or more downlink sharing channels, or a combination thereof. The communication manager 920 may be configured or support means for determining the number of repetitions for the group common downlink sharing channel based on the repetition configuration. The communication manager 920 may be configured or support means for monitoring the group common downlink sharing channel from the base station based on the determined number of repetitions.

[0197]

[0186] By including or configuring a communications manager 920 according to the examples described herein, device 905 may support techniques for improved communications reliability and improved coordination between devices. For example, the repetition count for a group common downlink shared channel may increase the reliability that the processor of device 905 is able to fully receive the group common downlink shared channel. Furthermore, the repetition configuration from the base station may allow the processor to determine how to monitor and receive the group common downlink shared channel.

[0198]

[0187] In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the transceiver 915, one or more antennas 925, or any combination thereof. Although the communications manager 920 is shown as a separate component, in some examples, one or more functions described with respect to the communications manager 920 may be supported or performed by the processor 940, memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by the processor 940 to cause device 905 to perform various aspects of the configuration for a group common downlink channel using the repetitions described herein, or, in some cases, the processor 940 and memory 930 may be configured to perform or support such operations.

[0199]

[0188] Figure 10 shows a block diagram 1000 of a device 1005 that supports a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. Device 1005 may be an example of an aspect of a base station 105 described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. Device 1005 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0200]

[0189] The receiver 1010 may be provided with means for receiving information such as packets, user data, control information, or any combination thereof, related to various information channels (for example, control channels, data channels, and information channels related to the configuration for a group common downlink channel using repetition). The information may be passed to other components of the device 1005. The receiver 1010 may use a single antenna or a set of multiple antennas.

[0201]

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

[0202]

[0191] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may be examples of means for implementing various aspects of the configuration for a group common downlink channel using the repetitions described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or various components thereof may support a method for implementing one or more of the functions described herein.

[0203]

[0192] In some examples, the communications manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof or components thereof may be implemented in hardware (for example, in communications management circuits). Hardware may include processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gates or transistor logic, individual hardware components, or any combination thereof configured or supporting means for performing the functions described herein. In some examples, a processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (for example, by the processor executing instructions stored in the memory).

[0204]

[0193] In addition or alternatively, in some examples, the communications manager 1020, receiver 1010, transmitter 1015, or various combinations thereof or their components may be implemented in code executed by a processor (for example, as communications management software or firmware). When implemented in code executed by a processor, the functions of the communications manager 1020, receiver 1010, transmitter 1015, or various combinations thereof or their components may be implemented by a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination of these or other programmable logic devices (for example, configured as a means for performing or supporting the functions described herein).

[0205]

[0194] In some examples, the communications manager 1020 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated with the receiver 1010, the transmitter 1015, or both in order to receive information, transmit information, or perform various other operations as described herein.

[0206]

[0195] The communication manager 1020 may support wireless communication at a base station in accordance with the examples disclosed herein. For example, the communication manager 1020 may be configured or support means for determining the number of repetitions for a group common downlink sharing channel, the group common downlink sharing channel may include one or more downlink sharing channels, one or more semi-persistent downlink sharing channels distinct from one or more downlink sharing channels, or a combination thereof. The communication manager 1020 may be configured or support means for transmitting a repetition configuration for a group common downlink sharing channel to one or more user equipment (UEs), the repetition configuration including instructions for the determined number of repetitions. The communication manager 1020 may be configured or support means for transmitting a group common downlink sharing channel to one or more UEs based on the determined number of repetitions.

[0207]

[0196] Figure 11 shows a block diagram 1100 of device 1105 that supports a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. Device 1105 may be an example of an aspect of device 1005 or base station 105 described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communications manager 1120. Device 1105 may also include a processor. Each of these components may communicate with one another (for example, via one or more buses).

[0208]

[0197] The receiver 1110 may be provided with means for receiving information such as packets, user data, control information, or any combination thereof, related to various information channels (for example, control channels, data channels, and information channels related to the configuration for a group common downlink channel using repetition). The information may be passed to other components of the device 1105. The receiver 1110 may use a single antenna or a set of multiple antennas.

[0209]

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

[0210]

[0199] Device 1105 or various components thereof may be examples of means for implementing various embodiments of the configuration for a group-common downlink channel using repetitions as described herein. For example, the communication manager 1120 may include a repetition number determination component 1125, a repetition configuration instruction component 1130, a group-common downlink shared channel component 1135, or any combination thereof. The communication manager 1120 may be an example of an embodiment of the communication manager 1020 as described herein. In some examples, the communication manager 1120 or various components thereof may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communication manager 1120 may receive information from the receiver 1110, send information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both in order to receive information, transmit information, or perform various other operations as described herein.

[0211]

[0200] The communication manager 1120 may support wireless communication at a base station in accordance with the examples disclosed herein. The repetition count determination component 1125 is configured as a means for determining the repetition count for a group common downlink shared channel, the group common downlink shared channel may include one or more downlink shared channels, one or more semi-persistent downlink shared channels different from one or more downlink shared channels, or a combination thereof. The repetition configuration instruction component 1130 is configured as a means for transmitting a repetition configuration for a group common downlink shared channel to one or more user equipment (UEs), the repetition configuration including an instruction for the determined repetition count. The group common downlink shared channel component 1135 is configured as a means for transmitting a group common downlink shared channel to one or more UEs based on the determined repetition count, or may support it.

[0212]

[0201] Figure 12 shows a block diagram 1200 of a communications manager 1220 that supports a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. Communications manager 1220 may be an example of an aspect of communications manager 1020, communications manager 1120, or both, as described herein. Communications manager 1220 or various components thereof may be an example of means for implementing various aspects of the configuration for a group-common downlink channel using repetition as described herein. For example, communications manager 1220 may include a repetition number determination component 1225, a repetition configuration instruction component 1230, a group-common downlink shared channel component 1235, a semi-static repetition instruction component 1240, a dynamic repetition instruction component 1245, a gap configuration instruction component 1250, an acknowledgment component 1255, or any combination thereof. Each of these components may communicate with one another directly or indirectly (for example, via one or more buses).

[0213]

[0202] The communication manager 1220 may support wireless communication at a base station in accordance with the examples disclosed herein. The repetition count determination component 1225 is configured as a means for determining the repetition count for a group common downlink shared channel, the group common downlink shared channel may include one or more downlink shared channels, one or more semi-persistent downlink shared channels different from one or more downlink shared channels, or a combination thereof. The repetition configuration instruction component 1230 is configured as a means for transmitting a repetition configuration for a group common downlink shared channel to one or more user equipment (UEs), the repetition configuration including an instruction for the determined repetition count. The group common downlink shared channel component 1235 is configured as a means for transmitting a group common downlink shared channel to one or more UEs based on the determined repetition count, or may support it.

[0214]

[0203] In some examples, to support sending a group common configuration for a downlink shared channel, the semi-static repetitive instruction component 1240 may be configured or support the means for sending a semi-static repetitive configuration for a repetitive configuration to one or more UEs.

[0215]

[0204] In some examples, in order to support the transmission of a semi-static repetitive configuration, the semi-static repetitive instruction component 1240 may be configured to or support the transmission of a semi-static repetitive configuration to one or more UEs via radio resource control signaling.

[0216]

[0205] In some examples, the semi-static repetition instruction component 1240 may be configured as a means for or supporting a semi-static repetition configuration which includes a group aggregation factor, where the number of repetitions is indicated based on the group aggregation factor and a group common downlink shared channel.

[0217]

[0206] In some examples, to support sending configurations for a downlink shared channel, the dynamic repetition instruction component 1245 may be configured or support the sending of a dynamic repetition configuration for a repetition configuration to one or more UEs.

[0218]

[0207] In some examples, the dynamic repetition instruction component 1245 may be configured or support the dynamic repetition configuration as a means for including a group repetition count parameter via a time domain resource allocation instruction, where the repetition count is indicated based on the group repetition count parameter.

[0219]

[0208] In some examples, the gap configuration instruction component 1250 may be configured or support means for sending a gap configuration to one or more UEs, which includes instructions for gaps that occur between repetitions of a group-common downlink shared channel.

[0220]

[0209] In some examples, to support transmitting gap configurations, the gap configuration instruction component 1250 may be configured or support means for transmitting gap configurations to one or more UEs semi-statically via radio resource control signaling, dynamically via time-domain resource allocation instructions including gap values ​​for the gaps, or a combination thereof.

[0221]

[0210] In some examples, the gap configuration instruction component 1250 may be configured or support the means for the gap to include several slots between each repetition of the group common downlink shared channel, where the length of each slot is based on the configuration of the bandwidth portion used to carry the group common downlink shared channel.

[0222]

[0211] In some examples, the gap configuration instruction component 1250 may be configured as a means for the gap to be configured independently for one or more downlink shared channels and one or more semi-persistent downlink shared channels, or may support such configuration.

[0223]

[0212] In some examples, the gap configuration instruction component 1250 may be configured or support a means to ensure that the number of repetitions combined with the gap between repetitions does not exceed the period configured for the semi-persistent downlink shared channel.

[0224]

[0213] In some examples, the acknowledgment component 1255 may be configured or support means for receiving an acknowledgment feedback message for a group-common downlink shared channel based on one or more UEs transmitting the group-common downlink shared channel, where the acknowledgment feedback message indicates whether the group-common downlink shared channel was successfully or unsuccessfully received based on the number of repetitions.

[0225]

[0214] In some examples, the acknowledgment component 1255 may be configured or support a means for sending an acknowledgment feedback message, where the acknowledgment feedback message is received based on the type 1 acknowledgment codebook.

[0226]

[0215] In some examples, the acknowledgment component 1255 may be configured or support a means for transmitting a configuration for a Type 2 acknowledgment codebook for one or more UEs to send an acknowledgment feedback message, where the acknowledgment feedback message is received based on the Type 2 acknowledgment codebook.

[0227]

[0216] In some examples, the repetitive configuration instruction component 1230 may be configured as a means for including a group radio network temporary identifier indicating that a group common downlink shared channel is transmitted for one or more UEs, or support it.

[0228]

[0217] Figure 13 shows a diagram of a system 1300 including a device 1305 that supports a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. Device 1305 may be an example of, or include, a component of, device 1005, device 1105, or base station 105 as described herein. Device 1305 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 1305 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communications manager 1320, a network communications manager 1310, a transceiver 1315, an antenna 1325, a memory 1330, a code 1335, a processor 1340, and an inter-station communications manager 1345. These components may communicate electronically via one or more buses (e.g., bus 1350) or be coupled (e.g., operably, communicatively, functionally, electronically, electrically).

[0229]

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

[0230]

[0219] In some cases, device 1305 may include a single antenna 1325. However, in some other cases, device 1305 may have two or more antennas 1325 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 1315 may communicate bidirectionally via one or more antennas 1325, a wired link, or a wireless link, as described herein. For example, transceiver 1315 may represent a wireless transceiver and communicate bidirectionally with another wireless transceiver. Transceiver 1315 may also include a modem for modulating packets, feeding the modulated packets to one or more antennas 1325 for transmission, and demodulating packets received from one or more antennas 1325. Transceiver 1315 or transceiver 1315 and one or more antennas 1325 may be examples of transmitters 1015, transmitters 1115, receivers 1010, receivers 1110, or any combination thereof or their components, as described herein.

[0231]

[0220] Memory 1330 may include RAM and ROM. Memory 1330 may store computer-readable, computer-executable code 1335, which, when executed by processor 1340, causes device 1305 to perform various functions described herein. Code 1335 may be stored in a non-temporary 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 the computer to perform functions described herein (for example, when compiled and executed). In some cases, memory 1330 may include a BIOS that can control basic hardware or software operations, in particular, such as interactions with peripheral components or devices.

[0232]

[0221] The processor 1340 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, the processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1330) in order to cause device 1305 to perform various functions (e.g., functions or tasks that support configuration for a group common downlink channel using repetition). For example, device 1305 or components of device 1305 may include the processor 1340 and memory 1330 coupled to the processor 1340, and the processor 1340 and memory 1330 are configured to perform various functions as described herein.

[0233]

[0222] The inter-station communication manager 1345 may manage communication with other base stations 105 and may include a controller or scheduler for coordinating with other base stations 105 to control communication with the UE 115. For example, the inter-station communication manager 1345 may coordinate scheduling for 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 for communication between base stations 105.

[0234]

[0223] The communication manager 1320 may support wireless communication at a base station in accordance with the examples disclosed herein. For example, the communication manager 1320 may be configured or support means for determining the number of repetitions for a group common downlink shared channel, the group common downlink shared channel may include one or more downlink shared channels, one or more semi-persistent downlink shared channels distinct from one or more downlink shared channels, or a combination thereof. The communication manager 1320 may be configured or support means for transmitting a repetition configuration for a group common downlink shared channel to one or more user equipment (UEs), the repetition configuration including instructions for the determined number of repetitions. The communication manager 1320 may be configured or support means for transmitting a group common downlink shared channel to one or more UEs based on the determined number of repetitions.

[0235]

[0224] In some examples, the communications manager 1320 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with the transceiver 1315, one or more antennas 1325, or any combination thereof. Although the communications manager 1320 is shown as a separate component, in some examples, one or more functions described with respect to the communications manager 1320 may be supported or performed by the processor 1340, memory 1330, code 1335, or any combination thereof. For example, code 1335 may include instructions that can be executed by the processor 1340 to cause device 1305 to perform various aspects of the configuration for a group common downlink channel using the repetitions described herein, or, in some cases, the processor 1340 and memory 1330 may be configured to perform or support such operations.

[0236]

[0225] Figure 14 shows a flowchart illustrating method 1400 supporting a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. The operation of method 1400 may be implemented by a UE or its components described herein. For example, the operation of method 1400 may be implemented by UE 115, described with reference to Figures 1 to 9. In some examples, the UE may execute a set of instructions to control a functional element of the UE to perform the described function. In addition or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0237]

[0226] In 1405, the method may include receiving a recurring configuration from a base station for a group common downlink sharing channel, the group common downlink sharing channel may include one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof. Operation of 1405 may be carried out according to the examples disclosed herein. In some examples, the mode of operation of 1405 may be carried out by a recurring configuration component 825 described with reference to Figure 8.

[0238]

[0227] In 1410, the method may include determining the number of repetitions for a group common downlink shared channel based on the repetition configuration. Operation of 1410 may be carried out according to the examples disclosed herein. In some examples, the operation of 1410 may be carried out by a repetition determination component 830 described with reference to Figure 8.

[0239]

[0228] In 1415, the method may include monitoring a group-common downlink shared channel from a base station based on a determined repetition count. Operation of 1415 may be carried out according to the examples disclosed herein. In some examples, the operation of 1415 may be carried out by a group-common downlink shared channel monitoring component 835, which is described with reference to Figure 8.

[0240]

[0229] Figure 15 shows a flowchart illustrating method 1500 that supports a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. The operation of method 1500 may be implemented by a UE or its components described herein. For example, the operation of method 1500 may be implemented by UE 115, described with reference to Figures 1 to 9. In some examples, the UE may execute a set of instructions to control a functional element of the UE to perform the described function. In addition or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0241]

[0230] In 1505, the method may include receiving a recurring configuration from a base station for a group common downlink sharing channel, the group common downlink sharing channel may include one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof. Operation of 1505 may be carried out according to the examples disclosed herein. In some examples, the mode of operation of 1505 may be carried out by a recurring configuration component 825 described with reference to Figure 8.

[0242]

[0231] In 1510, the method may include receiving a semi-static repetitive configuration for repetitive configuration from a base station. Operation of 1510 may be carried out according to the examples disclosed herein. In some examples, the operation of 1510 may be carried out by a semi-static repetitive configuration 840 described with reference to Figure 8.

[0243]

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

[0244]

[0233] In 1520, the method may include monitoring a group-common downlink shared channel from a base station based on a determined repetition count. Operation of 1520 may be carried out according to the examples disclosed herein. In some examples, the operation of 1520 may be carried out by a group-common downlink shared channel monitoring component 835, which is described with reference to Figure 8.

[0245]

[0234] Figure 16 shows a flowchart illustrating method 1600 that supports a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. The operation of method 1600 may be implemented by a UE or its components described herein. For example, the operation of method 1600 may be implemented by UE 115, described with reference to Figures 1 to 9. In some examples, the UE may execute a set of instructions to control a functional element of the UE to perform the described function. In addition or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0246]

[0235] In 1605, the method may include receiving a recurring configuration from a base station for a group common downlink sharing channel, the group common downlink sharing channel may include one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof. Operation of 1605 may be carried out according to the examples disclosed herein. In some examples, the mode of operation of 1605 may be carried out by a recurring configuration component 825 described with reference to Figure 8.

[0247]

[0236] In 1610, the method may include receiving a dynamic repetitive configuration for repetitive configuration from a base station. Operation of 1610 may be carried out according to the examples disclosed herein. In some examples, the operation of 1610 may be carried out by a dynamic repetitive configuration 845 described with reference to Figure 8.

[0248]

[0237] In 1615, the method may include determining the number of repetitions for a group common downlink shared channel based on the repetition configuration. Operation of 1615 may be carried out according to the examples disclosed herein. In some examples, the operation of 1615 may be carried out by the repetition determination component 830 described with reference to Figure 8.

[0249]

[0238] In 1620, the method may include monitoring a group-common downlink shared channel from a base station based on a determined repetition count. Operation of 1620 may be carried out according to the examples disclosed herein. In some examples, the operation of 1620 may be carried out by a group-common downlink shared channel monitoring component 835, which is described with reference to Figure 8.

[0250]

[0239] Figure 17 shows a flowchart illustrating method 1700 supporting a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. The operation of method 1700 may be implemented by a UE or its components described herein. For example, the operation of method 1700 may be implemented by UE 115, described with reference to Figures 1 to 9. In some examples, the UE may execute a set of instructions to control a functional element of the UE to perform the described function. In addition or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0251]

[0240] In 1705, the method may include receiving a recurring configuration from a base station for a group common downlink sharing channel, the group common downlink sharing channel may include one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof. Operation of 1705 may be carried out according to the examples disclosed herein. In some examples, the mode of operation of 1705 may be carried out by a recurring configuration component 825 described with reference to Figure 8.

[0252]

[0241] In 1710, the method may include receiving a gap configuration from a base station, which includes instructions for gaps occurring between repetitions of a group-common downlink shared channel. Operation of 1710 may be carried out according to the examples disclosed herein. In some examples, the operation of 1710 may be carried out by a gap configuration component 850 described with reference to Figure 8.

[0253]

[0242] In 1715, the method may include determining the number of repetitions for a group-common downlink shared channel based on the repetition configuration. Operation of 1715 may be carried out according to the examples disclosed herein. In some examples, the operation of 1715 may be carried out by the repetition determination component 830 described with reference to Figure 8.

[0254]

[0243] In 1720, the method may include monitoring a group-common downlink shared channel from a base station based on a determined repetition count. Operation of 1720 may be carried out according to the examples disclosed herein. In some examples, the operation of 1720 may be carried out by a group-common downlink shared channel monitoring component 835, which is described with reference to Figure 8.

[0255]

[0244] Figure 18 shows a flowchart illustrating method 1800 supporting a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. The operation of method 1800 may be implemented by a UE or its components described herein. For example, the operation of method 1800 may be implemented by UE 115, described with reference to Figures 1 to 9. In some examples, the UE may execute a set of instructions to control a functional element of the UE to perform the described function. In addition or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0256]

[0245] In 1805, the method may include receiving a recurring configuration from a base station for a group common downlink sharing channel, the group common downlink sharing channel may include one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from one or more downlink sharing channels, or a combination thereof. Operation of 1805 may be carried out according to the examples disclosed herein. In some examples, the mode of operation of 1805 may be carried out by a recurring configuration component 825 described with reference to Figure 8.

[0257]

[0246] In 1810, the method may include determining the number of repetitions for a group common downlink shared channel based on the repetition configuration. Operation of 1810 may be carried out according to the examples disclosed herein. In some examples, the operation of 1810 may be carried out by a repetition determination component 830 described with reference to Figure 8.

[0258]

[0247] In 1815, the method may include monitoring a group-common downlink shared channel from a base station based on a determined repetition count. Operation of 1815 may be carried out according to the examples disclosed herein. In some examples, the operation of 1815 may be carried out by a group-common downlink shared channel monitoring component 835, which is described with reference to Figure 8.

[0259]

[0248] In 1820, the method may include sending an acknowledgment feedback message to a base station for a group-common downlink shared channel based on monitoring, wherein the acknowledgment feedback message indicates a successful or failed reception of the group-common downlink shared channel based on the repetition count. Operation of 1820 may be carried out according to the examples disclosed herein. In some examples, aspects of operation of 1820 may be carried out by an acknowledgment feedback component 855 described with reference to Figure 8.

[0260]

[0249] Figure 19 shows a flowchart illustrating method 1900 supporting a configuration for a group-common downlink channel using repetition, according to an aspect of the present disclosure. The operation of method 1900 may be implemented by a base station or its components as described herein. For example, the operation of method 1900 may be implemented by a base station 105 as described with reference to Figures 1 to 5 and Figures 10 to 13. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described. In addition or alternatively, the base station may perform aspects of the functions described using dedicated hardware.

[0261]

[0250] In 1905, the method may include determining the number of repetitions for a group-common downlink sharing channel, the group-common downlink sharing channel may include one or more downlink sharing channels, one or more semi-persistent downlink sharing channels distinct from one or more downlink sharing channels, or a combination thereof. Operation of 1905 may be carried out according to the examples disclosed herein. In some examples, the mode of operation of 1905 may be carried out by the repetition number determination component 1225 described with reference to Figure 12.

[0262]

[0251] In 1910, the method may include transmitting a repetitive configuration for a group common downlink shared channel to one or more user devices (UEs), the repetitive configuration including an instruction for a determined number of repetitions. Operation of 1910 may be carried out according to the examples disclosed herein. In some examples, the mode of operation of 1910 may be carried out by a repetitive configuration instruction component 1230 described with reference to Figure 12.

[0263]

[0252] In 1915, the method may include transmitting a group common downlink shared channel to one or more UEs based on a determined number of repetitions. The operation of 1915 may be implemented according to the examples disclosed herein. In some examples, aspects of the operation of 1915 may be implemented by the group common downlink shared channel component 1235 described while referring to FIG. 12.

[0264]

[0253] Note that the methods described herein represent possible implementations, and that operations and steps may be reordered or in some cases modified, and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0265]

[0254] The following provides an overview of examples of the present invention.

[0266]

[0255] Example 1: A method for wireless communication in 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 comprising one or more downlink shared channels, one or more semi-persistent downlink shared channels different from the one or more downlink shared channels, or a combination thereof, determining a number of repetitions for the group common downlink shared channel based at least in part on the received repetition configuration, and monitoring, based at least in part on the determined number of repetitions, the group common downlink shared channel from the base station.

[0267]

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

[0268]

[0257] Example 3: The method of Example 2, comprising receiving a semi-static repetitive configuration from a base station via radio resource control signaling.

[0269]

[0258] Example 4: A semi-static repeating configuration comprising a group aggregation factor, wherein the number of repetitions is determined at least in part on the group aggregation factor and a group common downlink shared channel, as described in any one of Examples 2 to 3.

[0270]

[0259] Example 5: The method in Example 4, wherein the group aggregation factor for one or more group-common downlink sharing channels or one or more semi-persistent group-common downlink sharing channels is predefined as 1.

[0271]

[0260] Example 6: The method according to any one of Examples 4 to 5, further comprising determining a group aggregation factor for one or more semi-persistent group common downlink sharing channels based at least in part on a group aggregation factor for one or more group common downlink sharing channels, wherein the iterative configuration comprises a group radio network temporary identifier associated with one or more semi-persistent group common downlink sharing channels.

[0272]

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

[0273]

[0262] Example 8: The method of Example 1, wherein receiving a configuration for a downlink shared channel is further comprising receiving a dynamic repetitive configuration for a repetitive configuration from a base station.

[0274]

[0263] Example 9: The method of Example 8, wherein a dynamic repetition configuration comprises a group repetition count parameter via a time-domain resource allocation instruction, wherein the repetition count is determined at least in part on the group repetition count parameter.

[0275]

[0264] Example 10: The method of any one of Examples 1 to 9, further comprising receiving a gap configuration from a base station, which has instructions for gaps that occur between repetitions of a group common downlink shared channel.

[0276]

[0265] Example 11: The method of Example 10, wherein receiving the gap configuration from a base station is semi-statically via radio resource control signaling, dynamically via time-domain resource allocation instructions having gap values ​​for the gap, or a combination thereof.

[0277]

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

[0278]

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

[0279]

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

[0280]

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

[0281]

[0270] Example 16: The method of Example 15, further comprising receiving a configuration for a Type 1 acknowledgment codebook for sending an acknowledgment feedback message from a base station.

[0282]

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

[0283]

[0272] Example 18: The method of Example 15, further comprising receiving a configuration for a Type 2 acknowledgment codebook for sending an acknowledgment feedback message from a base station.

[0284]

[0273] Example 19: Determining a plurality of opportunities for monitoring a group-common downlink shared channel based at least in part on a feedback timing indicator field value between the last repetition of the group-common downlink shared channel and 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 repetition number, a gap value representing a gap between repetitions of the group-common downlink shared channel, or a combination thereof; and further comprising transmitting, to a base station, an acknowledgement feedback message for the plurality of opportunities based at least in part on a type 2 acknowledgement codebook, the method according to Example 18.

[0285]

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

[0286]

[0275] Example 21: A method for wireless communication at a base station, comprising: determining a repetition number for a group-common downlink shared channel, wherein the group-common downlink shared channel comprises 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 user equipments (UEs), a repetition configuration for the group-common downlink shared channel, wherein the repetition configuration comprises an indication for the determined repetition number; and transmitting, to the one or more UEs, the group-common downlink shared channel based at least in part on the determined repetition number.

[0287]

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

[0288]

[0277] Example 23: The method of Example 22, comprising transmitting a semi-static repetitive configuration to one or more UEs via radio resource control signaling.

[0289]

[0278] Example 24: A semi-static repeating configuration comprising a group aggregation factor, wherein the number of repetitions is shown at least in part on the group aggregation factor and the group common downlink shared channel, as described in any one of Examples 22 to 23.

[0290]

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

[0291]

[0280] Example 26: A dynamic repetition configuration comprising a group repetition count parameter via a time-domain resource allocation instruction, wherein the repetition count is determined at least in part on the group repetition count parameter, as described in Example 25.

[0292]

[0281] Example 27: The method according to any one of Examples 21 to 26, further comprising sending a gap configuration to one or more UEs, which has instructions for gaps that occur between repetitions of a group-common downlink shared channel.

[0293]

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

[0294]

[0283] Example 29: The method according to any one of Examples 27 to 28, wherein the gap comprises several slots between each repetition of the group common downlink shared channel, where the length of each slot is at least in part based on the configuration of the bandwidth portion used to carry the group common downlink shared channel.

[0295]

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

[0296]

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

[0297]

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

[0298]

[0287] Example 33: The method of Example 32, further comprising sending a configuration for a Type 1 acknowledgment codebook for one or more UEs to send an acknowledgment feedback message, wherein the acknowledgment feedback message is received at least in part based on a Type 1 acknowledgment codebook.

[0299]

[0288] Example 34: The method according to any one of Examples 32 to 33, further comprising sending a configuration for a Type 2 Acknowledgment Codebook for one or more UEs to send an acknowledgment feedback message, wherein the acknowledgment feedback message is received at least in part based on a Type 2 Acknowledgment Codebook.

[0300]

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

[0301]

[0290] Example 36: A device for wireless communication in a user device (UE), comprising at least one means for carrying out any one of the methods of Examples 1 to 20.

[0302]

[0291] Example 37: A device for wireless communication in a user device (UE), comprising a processor and memory coupled to the processor, wherein the processor and memory are configured to implement any one of the methods of Examples 1 to 20.

[0303]

[0292] Example 39: A non-temporary computer-readable medium for storing code for wireless communication in a user device (UE), wherein the code comprises instructions that can be executed by a processor to carry out any one of the methods of Examples 1 to 20.

[0304]

[0293] Example 40: An apparatus for wireless communication at a base station, comprising at least one means for carrying out any one of the methods of Examples 21 to 35.

[0305]

[0294] Example 41: A device for wireless communication at a base station, comprising a processor and a memory coupled to the processor, wherein the processor and the memory are configured to implement any one of the methods of Examples 21 to 35.

[0306]

[0295] Example 43: A non-temporary computer-readable medium for storing a code for wireless communication at a base station, wherein the code comprises instructions that can be executed by a processor to carry out any one of the methods of Examples 21 to 35.

[0307]

[0296] Embodiments of LTE, LTE-A, LTE-A Pro, or NR systems may be described as examples, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used for the majority of the description, however the techniques described herein are applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described herein may be applied to various other wireless communication systems such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Flash OFDM, as well as other systems and wireless technologies not expressly mentioned herein.

[0308]

[0297] The information and signals described herein may be represented using any of the following different techniques and methods. For example, the 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, light fields or optical particles, or any combination thereof.

[0309]

[0298] Various exemplary blocks and components described in relation to the disclosure herein may be implemented or carried out using general-purpose processors, DSPs, ASICs, CPUs, FPGAs or other programmable logic devices, individual gate or transistor logic, individual hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration).

[0310]

[0299] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or a combination thereof. When 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 codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, depending on the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination thereof. The features that implement the functions may also be physically located in various locations, including the distribution of parts of the functions so that they are implemented in different physical locations.

[0311]

[0300] Computer-readable media include both non-temporary computer storage media and communication media, including any media that facilitates the transfer of computer programs from one place to another. Non-temporary storage media can be any available media that can be accessed by a general-purpose or dedicated computer. Non-temporary computer-readable media can include, but are not limited to, any other non-temporary media that can be used to carry or store desired program code means in the form of instructions or data structures, and can be accessed by a general-purpose or dedicated computer or a general-purpose or dedicated processor. Any connection is also appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable media. As used herein, disk and disc include CD, LaserDisc®, OpticalDisc, Digital Multipurpose Disc (DVD), FloppyDisc®, and Blu-ray®, where disk typically reproduces data magnetically and disc optically reproduces data by laser. Combinations of the above are also included in the scope of computer-readable media.

[0312]

[0301] In use herein, including in the claims, the “or” used in an enumeration of items (for example, an enumeration of items ending with a phrase such as “at least one of” or “one or more of”) indicates an inclusive enumeration such that, for example, the enumeration 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). Also, the phrase “based on” as used herein shall not be construed as a reference to a closed set of conditions. For example, an exemplary step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, the phrase “based on” as used herein shall be construed in the same way as the phrase “based at least partially on.”

[0313]

[0302] In the attached figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes them from similar components. When only the first reference label is used herein, its description is applicable to any similar component having the same first reference label, regardless of the second reference label or any other subsequent reference labels.

[0314]

[0303] The descriptions herein relating to the attached drawings describe exemplary configurations and do not necessarily represent all examples that may be implemented or that are within the scope of the claims. The term “example” as used herein means “to serve as an example, case, or illustration” and does not mean “preferred” or “advantageous over other examples.” Detailed descriptions include specific details to provide an understanding of the techniques described. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples described.

[0315]

[0304] The description herein is provided so that a person skilled in the art can create or use the disclosure. Various modifications of the disclosure will be obvious to a person skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Accordingly, the disclosure is not limited to the examples and designs described herein and should be given the broadest scope that conforms to the principles and novel features disclosed herein. The invention described in the original claims of this application is listed below. [C1] A method for wireless communication in user equipment (UE), Receiving a repetitive configuration from a base station for a group-common downlink sharing channel, and determining the number of repetitions for the group-common downlink sharing channel based at least in part on the repetitive configuration, wherein the group-common downlink sharing channel comprises one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from the one or more downlink sharing channels, or a combination thereof. Monitoring the group-common downlink shared channel from the base station based at least in part on the determined number of repetitions. A method that includes [a certain feature]. [C2] Receiving the repeating configuration for the group's common downlink sharing channel means that Receiving a semi-static repetitive configuration for the repetitive configuration from the base station via radio resource control signaling. A method of C1 comprising: [C3] The method according to C2, wherein the semi-static repetition configuration comprises a group aggregation factor for multicast transmission, wherein the number of repetitions is determined at least in part on the group aggregation factor and the group common downlink shared channel. [C4] The method according to C3, 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 1. [C5] Determining the group aggregation factor for one or more semi-persistent downlink sharing channels based at least in part on the group aggregation factor for one or more downlink sharing channels, wherein the iterative configuration comprises a group radio network temporary identifier associated with the one or more semi-persistent downlink sharing channels. A method using C3 that further includes the following features. [C6] Determining the group aggregation factor for one or more downlink shared channels having a group radio network temporary identifier, at least in part, based on the aggregation factor of the unicast downlink shared channels configured in the UE. A method using C3 that further includes the following features. [C7] Receiving the repeating configuration for the group's common downlink sharing channel means that Receiving a dynamic repetitive configuration for the repetitive configuration from the base station. A method of C1 comprising: [C8] The method according to C7, wherein the dynamic repetition configuration comprises a group repetition number parameter via a time-domain resource allocation instruction, wherein the repetition number is determined at least in part on the group repetition number parameter. [C9] Receiving the repeating configuration for the group's common downlink sharing channel means that Receiving a semi-static repetitive configuration for the repetitive configuration from the base station, wherein the UE applies either the semi-static repetitive configuration or the dynamic repetitive configuration. A method of C7 comprising the same. [C10] Receiving the repeating configuration for the group's common downlink sharing channel means that Receiving a semi-static repetitive configuration for the repetitive configuration from the base station, wherein the semi-static repetitive configuration and the dynamic repetitive configuration are independently configured with different group radio network temporary identifiers (G-RNTI) or configured and scheduled G-RNTIs (G-CS-RNTI). A method of C7 comprising the same. [C11] The base station receives a gap configuration that includes instructions for gaps that occur during the repetition of the group's common downlink sharing channel. A method of C1 that further includes the following: [C12] Receiving the aforementioned gap configuration means The gap configuration is received from the base station semi-statically via radio resource control signaling, dynamically via time-domain resource allocation instructions that include the gap value of the gap, or in a combination thereof. A method for C11 comprising the following: [C13] The method according to C11, wherein the gap comprises several slots between each repetition of the group common downlink shared channel, wherein the length of each slot is at least partially based on the configuration of the bandwidth portion used to carry the group common downlink shared channel. [C14] The method according to C11, wherein the gap is configured independently for the one or more downlink sharing channels and the one or more semi-persistent downlink sharing channels. [C15] The method according to C11, wherein the number of repetitions, combined with the gap between the repetitions, does not exceed the period configured for the semi-persistent downlink sharing channel. [C16] Send an acknowledgment feedback message to the base station for the group common downlink shared channel, at least in part on the monitoring, wherein the acknowledgment feedback message indicates a successful or failed reception of the group common downlink shared channel, at least in part on the number of repetitions. A method of C1 that further includes the following: [C17] Receiving a configuration for a Type 1 acknowledgment codebook for transmitting the acknowledgment feedback message from the base station. A method of C16 that further includes the following: [C18] Determining multiple 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, To transmit a single acknowledgment feedback message for the multiple occasions to the base station, at least in part, based on the Type 1 acknowledgment codebook. A method of C17 that further includes the following: [C19] Receiving a configuration for a Type 2 acknowledgment codebook for transmitting the acknowledgment feedback message from the base station. A method of C16 that further includes the following: [C20] Determining multiple opportunities for monitoring the group-common downlink sharing channel based at least partially on a feedback timing indicator field value between the last iteration of the group-common downlink sharing channel and the acknowledgment feedback message, an offset value between the downlink control channel carrying the iterative configuration and the first iteration of the group-common downlink sharing channel, the number of iterations, a gap value representing the gap between each iteration of the group-common downlink sharing channel, or a combination thereof, To transmit the acknowledgment feedback message for the multiple occasions to the base station, at least in part, based on the Type 2 acknowledgment codebook. A method using C19, which further includes the following features. [C21] The method according to C1, wherein the repeating configuration comprises a group radio network temporary identifier shared by at least the UE and a plurality of UEs. [C22] A device for wireless communication in user equipment (UE), Processor and The memory coupled to the aforementioned processor, Instructions stored in the aforementioned memory and The device is equipped with the command, Receiving a repetitive configuration from a base station for a group-common downlink sharing channel, and determining the number of repetitions for the group-common downlink sharing channel based at least in part on the repetitive configuration, wherein the group-common downlink sharing channel comprises one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from the one or more downlink sharing channels, or a combination thereof. Monitoring the group-common downlink shared channel from the base station based at least in part on the determined number of repetitions. To perform the above, the processor can perform the following: Device. [C23] The instruction for receiving the repetitive configuration for the group common downlink shared channel is: Receiving a semi-static repetitive configuration for the repetitive configuration from the base station via radio resource control signaling. The apparatus according to C22, which is executable by the processor to cause the apparatus to perform the above. [C24] The apparatus according to C23, wherein the semi-static repetition configuration comprises a group aggregation factor for multicast transmission, wherein the number of repetitions is determined at least in part on the group aggregation factor and the group common downlink shared channel. [C25] The instruction for receiving the repetitive configuration for the group common downlink shared channel is: Receiving a dynamic repetitive configuration for the repetitive configuration from the base station. The apparatus according to C22, which is executable by the processor to cause the apparatus to perform the above. [C26] The aforementioned dynamic repetition configuration includes a group repetition count parameter via a time-domain resource allocation instruction, The apparatus according to C25, wherein the number of repetitions is determined at least in part on the group repetitions parameter. [C27] The instruction for receiving the repetitive configuration for the group common downlink shared channel is: Receiving a semi-static repetitive configuration for the repetitive configuration from the base station, wherein the UE is configured to apply either the semi-static repetitive configuration or the dynamic repetitive configuration. The apparatus according to C22, which is executable by the processor to cause the apparatus to perform the above. [C28] The instruction for receiving the repetitive configuration for the group common downlink shared channel is: Receiving a semi-static repetitive configuration for the repetitive configuration from the base station, wherein the semi-static repetitive configuration and the dynamic repetitive configuration are independently configured with different group radio network temporary identifiers (G-RNTI) or configured and scheduled G-RNTIs (G-CS-RNTI). The apparatus according to C22, which is executable by the processor to cause the apparatus to perform the above. [C29] A device for wireless communication in user equipment (UE), Means for receiving a recurring configuration from a base station for a group-common downlink sharing channel, wherein the group-common downlink sharing channel comprises one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from the one or more downlink sharing channels, or a combination thereof. Means for determining the number of repetitions for the group common downlink shared channel based at least in part on the aforementioned repetition configuration, Means for monitoring the group-common downlink shared channel from the base station based at least in part on the determined number of repetitions, A device equipped with the following features. [C30] A non-temporary computer-readable medium for storing a code for wireless communication in a user device (UE), wherein the code is: Receiving a repetitive configuration from a base station for a group-common downlink sharing channel, and determining the number of repetitions for the group-common downlink sharing channel based at least in part on the repetitive configuration, wherein the group-common downlink sharing channel comprises one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from the one or more downlink sharing channels, or a combination thereof. Monitoring the group-common downlink shared channel from the base station based at least in part on the determined number of repetitions. A non-temporary computer-readable medium comprising instructions that can be executed by a processor to perform a certain action.

Claims

1. A method for wireless communication in user equipment (UE), The system receives a recurring configuration from a base station for a group-common downlink sharing channel, and the group-common downlink sharing channel comprises one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from the one or more downlink sharing channels, or a combination thereof. Based on the aforementioned repeating configuration, the number of repetitions for the group's common downlink shared channel is determined, Based on the determined number of repetitions, monitor the group-wide downlink shared channel from the base station, The base station transmits an acknowledgment feedback message for the group-common downlink shared channel based on the monitoring, wherein the acknowledgment feedback message indicates a successful or failed reception of the group-common downlink shared channel based on the number of repetitions. A method that includes [a certain feature].

2. Receiving the repeating configuration for the group's common downlink sharing channel means that Receiving a semi-static repetitive configuration for the repetitive configuration from the base station via radio resource control signaling. The method according to claim 1, comprising:

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

4. Determining the group aggregation factor for one or more semi-persistent downlink sharing channels based on the group aggregation factor for one or more downlink sharing channels, wherein the repeating configuration comprises a group radio network temporary identifier associated with the one or more semi-persistent downlink sharing channels, Determining the group aggregation factor for one or more downlink shared channels having a group radio network temporary identifier based on the aggregation factor of the unicast downlink shared channels configured in the UE. The method according to claim 3, further comprising:

5. Receiving the repeating configuration for the group's common downlink sharing channel means that Receiving a dynamic repetitive configuration for the repetitive configuration from the base station. The method according to claim 1, comprising:

6. The method according to claim 5, wherein the dynamic repetition configuration includes a group repetition number parameter via a time-domain resource allocation instruction, wherein the repetition number is determined based on the group repetition number parameter.

7. Receiving the repeating configuration for the group's common downlink sharing channel means that Receiving a semi-static repetitive configuration for the repetitive configuration from the base station, wherein the UE applies either the semi-static repetitive configuration or the dynamic repetitive configuration, Receiving a semi-static repetitive configuration for the repetitive configuration from the base station, wherein the semi-static repetitive configuration and the dynamic repetitive configuration are independently configured with different group radio network temporary identifiers (G-RNTI) or configured and scheduled G-RNTIs (G-CS-RNTI). The method according to claim 5, comprising:

8. The base station receives a gap configuration that includes instructions for gaps that occur during the repetition of the group's common downlink sharing channel. The method according to claim 1, further comprising:

9. Receiving the aforementioned gap configuration means The gap configuration is received from the base station semi-statically via radio resource control signaling, dynamically via time-domain resource allocation instructions that include the gap value of the gap, or in a combination thereof. The method according to claim 8, comprising:

10. The gap comprises several slots between each repetition of the group-common downlink shared channel, where the length of each slot is based on the configuration of the bandwidth portion used to carry the group-common downlink shared channel, or The gap is configured independently for the one or more downlink shared channels and the one or more semi-persistent downlink shared channels, or The method of claim 8, wherein the number of repetitions, combined with the gap between the repetitions, does not exceed the period configured for the semi-persistent downlink sharing channel.

11. Receiving a configuration for a Type 1 acknowledgment codebook for transmitting the acknowledgment feedback message from the base station, Determining 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, To transmit a single acknowledgment feedback message to the base station for the multiple occasions based on the Type 1 acknowledgment codebook. The method according to claim 1, further comprising:

12. Receiving a configuration for a Type 2 acknowledgment codebook for transmitting the acknowledgment feedback message from the base station, Determining multiple opportunities for monitoring the group-common downlink sharing channel based on the feedback timing indicator field value between the last iteration of the group-common downlink sharing channel and the acknowledgment feedback message, the offset value between the downlink control channel carrying the iterative configuration and the first iteration of the group-common downlink sharing channel, the number of iterations, the gap value representing the gap between each iteration of the group-common downlink sharing channel, or a combination thereof, To transmit the acknowledgment feedback messages for the multiple occasions to the base station based on the Type 2 acknowledgment codebook. The method according to claim 1, further comprising:

13. A device for wireless communication in user equipment (UE), Means for receiving a recurring configuration from a base station for a group-common downlink sharing channel, wherein the group-common downlink sharing channel comprises one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from the one or more downlink sharing channels, or a combination thereof. Means for determining the number of repetitions for the group's common downlink shared channel based on the aforementioned repetition configuration, Means for monitoring the group-common downlink shared channel from the base station based on the determined repetition count, The base station is provided with means for transmitting an acknowledgment feedback message for the group-common downlink sharing channel based on the monitoring, wherein the acknowledgment feedback message indicates a successful or failed reception of the group-common downlink sharing channel based on the number of repetitions. A device equipped with the following features.

14. A non-temporary computer-readable medium for storing a code for wireless communication in a user device (UE), wherein the code is: The system receives a recurring configuration from a base station for a group-common downlink sharing channel, and the group-common downlink sharing channel comprises one or more downlink sharing channels, one or more semi-persistent downlink sharing channels different from the one or more downlink sharing channels, or a combination thereof. Based on the aforementioned repeating configuration, the number of repetitions for the group's common downlink shared channel is determined, Based on the determined number of repetitions, monitor the group-wide downlink shared channel from the base station, The base station transmits an acknowledgment feedback message for the group-common downlink shared channel based on the monitoring, wherein the acknowledgment feedback message indicates a successful or failed reception of the group-common downlink shared channel based on the number of repetitions. A non-temporary computer-readable medium comprising instructions that can be executed by a processor to perform a certain action.

Images