Physical uplink shared channel duplication with different configurations

Abstract

The present application relates to devices and components, including apparatus, systems, and methods for performing repeated physical uplink shared channel transmissions with different configurations on different beams.

Description

Background Art

[0001] The 3rd Generation Partnership Project (3GPP) introduced reliability enhancements for Physical Uplink Control Channel (PUCCH) and Physical Uplink Shared Channel (PUSCH) transmissions in Releases 15 and 16. These enhancements involve repeatedly transmitting the uplink channel payload. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Figure 1 A network environment is shown according to some embodiments.

[0003] Figure 2 Included is a signaling diagram illustrating scheduling of PUSCH transmissions with repetitions in multiple beams with downlink control information according to some embodiments.

[0004] Figure 3 Shown are comparative signaling metrics among multiple beams carrying repetitions of PUSCH according to some embodiments.

[0005] Figure 4 Included is a signaling diagram illustrating frequency hopping among multiple beams carrying repetitions of PUSCH according to some embodiments.

[0006] Figure 5 is a signaling diagram illustrating two levels of downlink control information according to some embodiments.

[0007] Figure 6 An operational flow / algorithm structure according to some embodiments is shown.

[0008] Figure 7 Another operational flow / algorithm structure according to some embodiments is shown.

[0009] Figure 8 Another operational flow / algorithm structure according to some embodiments is shown.

[0010] Figure 9 A beamforming component of a device according to some embodiments is shown.

[0011] Figure 10 User equipment according to some embodiments is shown.

[0012] Figure 11 A base station according to some embodiments is shown. DETAILED DESCRIPTION

[0013] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth for the purpose of illustration and not limitation, so as to provide a thorough understanding of the various aspects of the various embodiments. However, it will be apparent to those skilled in the art who benefit from this disclosure that the various aspects of the various embodiments can be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments due to unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0014] The following is a glossary of terms that may be used in this disclosure.

[0015] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or memory (shared, dedicated, or group) configured to provide the described functionality, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on a chip (SoC)), a digital signal processor (DSP), etc. In some embodiments, the circuit can execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" can also refer to a combination of one or more hardware elements and program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code can be referred to as a specific type of circuit.

[0016] As used herein, the term "processor circuitry" refers to, is part of, or includes circuitry that is capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuitry" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).

[0017] As used herein, the term "interface circuitry" refers to circuitry that enables, is part of, or includes information exchange between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and the like.

[0018] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can represent a remote user of network resources in a communication network. Furthermore, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0019] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0020] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and application, workload units, etc. "Hardware resources" may refer to computing, storage, or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage, or network resources provided by a virtualization infrastructure to applications, devices, systems, etc. The terms "network resources" or "communication resources" may refer to resources accessible to a computer device / system via a communication network. The term "system resource" may refer to any type of shared entity that provides a service and may include computing resources or network resources. System resources may be considered a set of coherent functions, network data objects, or services accessible through a server, where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0021] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices for transmitting and receiving information.

[0022] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0023] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0024] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0025] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0026] Figure 1 A network environment 100 is shown according to some embodiments. Network environment 100 may include a UE 104 and a base station 108. Base station 108 may provide one or more wireless serving cells, such as 3GPP New Radio (NR) cells, through which UE 104 may communicate with base station 108.

[0027] The UE 104 and the base station 108 can communicate over an air interface compatible with 3GPP technical specifications, such as those defining the fifth generation (5G) NR system standard. The base station 108 can be a next generation radio access network (NG-RAN) node coupled to a 5G core network. The NG-RAN node can be a gNB that provides NR user plane and control plane protocol termination to the UE 104, or an ng-eNB that provides Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocol termination to the UE 104.

[0028] Base station 108 may be coupled to one or more distributed antenna panels (APs) (e.g., AP 116 and AP 120). Distributed APs 116 / 120 may be implemented in transmit-receive points (TRPs) or other devices. Generally, base station 108 may perform most of the operations of the communication protocol stack, including scheduling, while APs 116 / 120 act as distributed antennas. In some embodiments, APs 116 / 120 may perform some low-level operations of the communication protocol stack (e.g., emulating physical (PHY) layer operations).

[0029] Base stations 108 may use APs 116 / 120 to geographically separate points where signals may be transmitted to or received from UEs 104. This may increase flexibility in communicating with UEs 104 using multiple-input, multiple-output, and beamforming enhancements. APs 116 / 120 may be used to transmit downlink transmissions to UEs 104 and receive uplink transmissions from UEs 104. In some embodiments, the distributed transmit / receive capabilities provided by APs 116 and 120 may be used for coordinated multi-point or carrier aggregation systems from one or more base stations.

[0030] Although network environment 100 shows one base station 108 communicating with UE 104 through AP 116 / 120, in various embodiments, network environment 100 may include multiple other network elements (e.g., base stations, TRPs, eNBs, etc.) to facilitate radio access network connectivity for UE 104.

[0031] The base station 108 can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and mapping transport channels onto physical channels. Logical channels can transfer data between the radio link control (RLC) layer and the medium access control (MAC) layer; transport channels can transfer data between the MAC and PHY layers; and physical channels can transfer information across the air interface.

[0032] One or more antenna panels on the AP 116 and UE 104 may include arrays of antenna elements that enable receive or transmit beamforming. Beamforming can improve uplink and downlink budgets by determining and using uplink and downlink beams that increase antenna gain and overall system performance. The UE 104 and base station 108 may use beam management operations to determine desired uplink-downlink beam pairs based on reference signal measurements and channel reciprocity assumptions.

[0033] In the downlink direction, the base station 108 may transmit synchronization signal blocks (SSBs) and channel state information-reference signals (CSI-RSs), which are measured by the UE 104 to determine the desired downlink beam pair for transmitting / receiving physical downlink control channel (PDCCH) transmissions and physical downlink shared channel (PDSCH) transmissions. In some embodiments, the network element may assume that the uplink / downlink beams correspond and use the desired downlink beam pair as the desired uplink beam pair for PUSCH transmissions and PUCCH transmissions. In some embodiments, the beam pair may be determined independently for the uplink direction based on the sounding reference signal (SRS) transmitted by the UE 104. In various embodiments, beam management may include different levels, such as initial acquisition of uplink and downlink beams and later refinement of the uplink and downlink beams.

[0034] The PUSCH can be used to transmit user data in the user plane and Signaling Radio Bearer (SRB) messages in the control plane. The PUSCH can also be used to transmit various control information such as, for example, buffer status reports, cell radio network temporary identifiers (C-RNTIs), configuration grants, and power headroom reports.

[0035] The base station 108 may transmit downlink control information (DCI) in the PDCCH to the UE 104 to schedule the UE 104 to repeatedly transmit PUSCH transmissions over multiple beams. DCI corresponds to physical (PHY) layer signaling. 3GPP has defined multiple DCI formats to accommodate specific PDCCH payloads. For example, DCI format 0_0 may be used to schedule one PUSCH in a cell (with a relatively small payload to be used when coverage deteriorates and increased redundancy); DCI format 0_1 may be used to schedule one or more PUSCH transmissions in a cell or indicate configuration grant downlink feedback information; DCI format 0_2 may be used to schedule one PUSCH transmission in a cell; and DCI format 2_2 may provide transmit power control commands for PUCCH and PUSCH. Other DCI formats are also defined.

[0036] The base station 108 may transmit the PDCCH using resource elements belonging to a control resource set (CORESET).A search space configuration may refer to a specific CORESET to define a search space, eg, a specific set of resource blocks and symbols that the UE 104 attempts to decode the PDCCH.

[0037] A transport block (TB) may be a data packet transmitted via a PUSCH transmission. When PUSCH repetition is used, the same TB may be transmitted in each repetition. After UE 104 receives an uplink assignment, the UE must determine the transport block size. Similarly, when attempting to decode received data, base station 108 must also determine the same transport block size. To determine the TB size, a network element may determine the number of resource elements available for data transmission within the bandwidth of a single resource block. The number of resource elements available for data transmission may be based on the frequency allocation (e.g., the number of resource blocks) and the time allocation (e.g., the transmission duration) used for the uplink assignment. The TB size determination may be further based on the modulation order and coding rate to be used for the uplink transmission.

[0038] Figure 2 Specifically, signaling diagram 204 shows that PDCCH schedules PUSCH transmissions with repetition type A, while signaling diagram 208 shows that PDCCH schedules PUSCH transmissions with repetition type B.

[0039] In PUSCH repetition type A, each PUSCH repetition can be mapped to consecutive time slots. For example, the first PUSCH repetition can be mapped to the first time slot, the second PUSCH repetition can be mapped to the second time slot immediately following the first time slot, and so on. In PUSCH repetition type B, each PUSCH repetition can be mapped to consecutive symbols. The consecutive symbols can be in one or more time slots. Signaling diagram 208 shows consecutive symbols transmitted in the first time slot and the second time slot.

[0040] In contrast to Releases 15 and 16, where all PUSCH repetitions are transmitted from a single beam, signaling diagrams 204 and 208 illustrate PUSCH being transmitted using two different beams (e.g., beam #1 and beam #2). In various embodiments, UE 104 may transmit PUSCH repeatedly using multiple different beams. In some embodiments, N beams may be scheduled for M repetitions, where M is greater than or equal to N. Repetitions from different beams may be transmitted to the same or different TRPs.

[0041] In various implementations, PUSCH repetitions transmitted on different beams can use different time / frequency resources configured by RRC or granted by a single downlink control information (DCI) or multiple DCIs to transmit the same PUSCH payload. The different beams used to transmit PUSCH repetitions can be defined by different SRS resource indicators (SRIs), transmit precoder matrix indicators (TPMIs), or power control parameters.

[0042] Transmitting PUSCH repetitions using different beams may result in different signaling metrics from one repetition set to another. Figure 3304 and 308. A comparative signaling metric is shown in accordance with some embodiments. For example, repetitively configuring different power control parameters for different beams can result in beam #1 and beam #2 having different path losses (as shown in graph 304) and per-resource element transmit powers (as shown in graph 308). This can also result in different power headrooms. Different transmit powers can also result in different maximum bandwidths, as shown in graph 312. Furthermore, the SINR for each beam can also be different. This can result in different modulation orders and coding rates for different beams.

[0043] In some implementations, it may be desirable to transmit PUSCH repetitions with different configurations to account for different power control parameters, path loss, and SINR that may be associated with different beams. Embodiments describe different configurations for repeated PUSCH transmissions. Various aspects include control signaling for: single DCI-based PUSCH repetitions; two-level DCI-based PUSCH repetitions; and multiple DCI-based PUSCH repetitions.

[0044] In some embodiments, the base station 108 may transmit a single DCI to schedule one PUSCH transmission (eg, one transport block) across multiple beams via multiple repetitions. According to some embodiments, PUSCH repetition based on a single DCI may be described as follows.

[0045] A single DCI may be DCI format 0_1, 0_2, or a new DCI format. A single DCI may provide an indication of some or all of the following information: frequency domain resource allocation (FDRA) for repetition of different beams; time domain resource allocation (TDRA) for repetition of different beams; or modulation and coding scheme (MCS) for repetition of different beams.

[0046] A single DCI may include one or more FDRA fields for allocating frequency domain resources (e.g., a group of resource blocks (RBs)) for PUSCH transmission. In some embodiments, a single DCI may include a frequency domain resource assignment field for specifying the group of allocated resource blocks. The FDRA information signaled in a single DCI may be based on the RRC configuration of UE 104. For example, base station 108 may configure the UE with resource allocation type 0 or type 1 (or allow dynamic switching between the two). For resource allocation type 0, the DCI may include a bitmap for allocating specific resource block groups (RBGs). An RBG may be a group of contiguous virtual resource blocks. For resource allocation type 1, the DCI may include a resource indication value for allocating a group of contiguous virtual resource blocks.

[0047] In some embodiments, the FDRAs for different beams may be indicated by separate fields in a single DCI. For example, a single DCI may include a first field for configuring beam #1 with a first FDRA configuration and a second field for configuring beam #2 with a second FDRA configuration. Alternatively, the FDRAs for different beams may be collectively indicated by a single field. For example, a single DCI may include one FDRA field for configuring beam #1 with a first FDRA configuration and beam #2 with a second FDRA configuration.

[0048] In some embodiments, a single DCI may include an indication of frequency hopping for PUSCH transmissions. For example, a single DCI may include a frequency hopping flag indicating whether frequency hopping is to be applied to the resource allocation. In some embodiments, the frequency hopping flag may be configured per beam or across all beams.

[0049] Figure 4 FIG. 4 shows a frequency hopping configuration for PUSCH repetitions for different beams according to some embodiments. Specifically, Figure 4 Frequency hopping configuration 404 and frequency hopping configuration 408 are shown.

[0050] Frequency hopping configuration 404 illustrates frequency hopping applied to repetitions within the same beam. For example, the first repetitions of beam #1 (repetition #1 and repetition #2) have a frequency hopping pattern that provides for the first repetition to be transmitted at different frequencies from one another; and the second repetitions of beam #2 (repetition #3 and repetition #4) have a frequency hopping pattern that provides for the second repetition to be transmitted at different frequencies from one another. Because the frequency hopping pattern is independent of the repetitions, some of the first repetitions may overlap in frequency with some of the second repetitions. For example, repetition #1 of beam #1 and repetition #3 of beam #2 completely overlap in frequency, as do repetition #2 of beam #1 and repetition #4 of beam #2.

[0051] In some embodiments, if the size of the allocated frequencies is different for repetitions in different beams, frequency hopping applied to repetitions within the same beam may be used, such as that shown above with respect to frequency hopping configuration 404 .

[0052] Frequency hopping configuration 408 shows the frequency hopping applied to the repetitions of different beams. For example, one frequency hopping pattern is applied to all first and second repetitions. Therefore, there is no complete frequency overlap with respect to any two repetitions in the plurality of repetitions.

[0053] In some embodiments, if the size of the allocated frequencies is the same for repetitions of different beams, frequency hopping applicable to repetitions of different beams may be used, such as that shown above with respect to frequency hopping configuration 408 .

[0054] In some embodiments, a single DCI may include one or more TDRA fields for allocating time domain resources for PUSCH transmission. In some embodiments, a single DCI may include a time domain resource assignment field for defining a pointer to a row in a lookup table configured by 3GPP technical specifications or RRC signaling. The lookup table may define the slot offset, PUSCH mapping type, starting symbol, and the number of allocated symbols. The PUSCH mapping type may be mapping type A or mapping type B and may determine the number of allowed combinations of PUSCH starting symbols and lengths for normal and extended cyclic prefixes.

[0055] In some embodiments, the TDRAs for different beams may be indicated in a single DCI by separate fields or collectively by a single field. For collective indication, additional starting symbol indices or symbol lengths for additional repetitions for different beams may be indicated by RRC. For example, the PUSCH TDRA information element (IE) may be updated as follows.

[0056]

[0057] The value of the TDRA field in a single DCI may be defined by the PUSCH TDRA IE. Additional starting symbols and length values for repetition type A; additional starting symbols for repetition type B and additional length values for repetition type B are added to allow flexibility in defining separate TDRAs for the first repetition (for the first beam) and the second repetition (for the second beam). In various implementations, more than one additional starting symbol / length value set may be added to allow signaling of PUSCH transmissions with repetitions across more than two beams.

[0058] To provide separate field indication, a single DCI may have multiple time-domain resource assignment fields corresponding to multiple beams carrying PUSCH repetitions, respectively.

[0059] In some embodiments, a single DCI may include one or more fields for indicating the MCS used for PUSCH transmission. In some embodiments, these fields may indicate a pointer to a row in the associated MCS lookup table. In some embodiments, for PUSCH with transform precoding and 64-quadrature amplitude modulation (QAM), the MCS lookup table may be similar to Table 1 shown below.

[0060]

[0061]

[0062] Table 1

[0063] In other embodiments, other tables may be used, including those defined for other QAMs (e.g., 256QAM) or for low spectral efficiency. In some embodiments, the tables and definitions may be similar to those described in 3GPP TS 38.214 v16.3.0 (2020-10-02).

[0064] In some embodiments, a single DCI may include MCS indications for N beams. In some embodiments, these indications may be based on a normal MCS or a reserved MCS. For example, referring to Table 1, a normal MCS indication may be a five-bit value corresponding to one of the MCS indices 0-27. A reserved MCS indication may be a two-bit value corresponding to one of the MCS indices 28-31.

[0065] In one option, a single DCI may include an indication for one normal MCS and an indication for N-1 reserved MCSs. The one normal MCS may correspond to the repetition of the first beam, while the N-1 reserved MCSs may correspond to the repetitions of the remaining N-1 beams, respectively.

[0066] As discussed above, the TB size can be based on the modulation order, coding rate, and uplink resource allocation (e.g., the number of resource elements available for transmission). In some embodiments, to facilitate decoding of PUSCH transmissions, it may be desirable to keep the TB size constant across all repetitions. Therefore, in a first option, the TB size for all repetitions can be based on a normal MCS and uplink resource allocation for the repetitions of the first beam. The modulation order for the repetitions transmitted by the remaining (N-1) beams can be selected based on the corresponding reserved MCS indication of the DCI.

[0067] In the second option, a normal MCS may be used. The TB size for each repetition may be selected based on the normal MCS and uplink resource allocation for the repetition of the first beam. The modulation order for the repetitions of other beams may also be based on the indicated normal MCS.

[0068] In a third option, N normal MCSs may be used. The TB size for all repetitions may be selected based on the normal MCS and uplink resource allocation for the repetition of the first beam. The modulation order for the repetitions transmitted by the remaining N-1 beams may be selected based on the corresponding N-1 normal MCS indications in the DCI.

[0069] PUSCH transmissions may be transmitted using an uplink phase tracking reference signal (PT-RS), which allows the base station 108 to estimate and subsequently compensate for both phase noise and frequency offset. The PT-RS time domain pattern depends on the MCS configured for the uplink transmission. For example, see Section 6.2.3.1 of TS 38.214 v16.3.0 (2020-09). In some embodiments, for the first and second options, the PT-RS time domain pattern may be determined by the normal MCS used for the repetition of the first beam.

[0070] Figure 5 5 is a signaling diagram 500 illustrating two-level DCI according to some embodiments. The base station 108 may transmit two-level DCI to schedule PUSCH transmissions with repetitions in multiple beams (e.g., N beams). Specifically, the base station 108 may transmit a first PDCCH with first-level DCI 504, which may be used to provide control signaling for the first beam repetitions (e.g., PUSCH repetition #1 and PUSCH repetition #2). The first-level DCI 504 may also indicate the presence of a second PDCCH with second-level DCI 508. In some embodiments, the first-level DCI 504 may also indicate the location of the second-level DCI 508.

[0071] The second-level DCI 508 may be used to provide control signaling for repetitions on a beam subsequent to the first beam repetition. As shown, the second-level DCI 508 may provide control signaling for the second beam repetition (e.g., PUSCH repetition #3 and PUSCH repetition #4). However, in other embodiments, the second-level DCI 508 may include control signaling for repetitions on additional beams.

[0072] In various implementations, the control signaling for the second beam repetition may include signaling for configuring FDRA, TDRA, or MCS for the second beam repetition.

[0073] A first option for signaling the FDRA for the second beam repetition may include an indication identifying frequency resources within the entire bandwidth. For example, the entire bandwidth may be defined based on the bandwidth portion 512 in which the second beam repetition is located. The FDRA indication of this option may provide the UE 104 with sufficient information to locate the second beam repetition within the bandwidth portion 512. This option may allow for the flexibility of scheduling the second repetition in a portion of the frequency bandwidth not covered by the frequency bandwidth of the first beam repetition.

[0074] A second option for signaling the FDRA for the second beam repetition may include an indication identifying a frequency resource within the allocated bandwidth for the first beam repetition. For example, the first beam repetition may be transmitted on a first plurality of subcarriers. In this option, the FDRA indication of the frequency allocation for the second beam repetition may indicate a subset of the first plurality of subcarriers to be used for the second beam repetition. In some embodiments, the FDRA for the second beam repetition may be provided as an offset from the FDRA for the first beam repetition. In this case, the FDRA for the second beam repetition may be considered a differential signaling implementation.

[0075] In the first option for signaling the TDRA for the second beam repetition, only a different length may be indicated. For example, the TDRA control signaling for the first beam repetition may include both the start symbol and the length value for the first beam repetition. The TDRA control signaling for the second beam repetition may then include only the length value. In some embodiments, the second beam repetition may be determined to begin immediately after the first beam repetition. Therefore, the start symbol value may not need to be transmitted by the second-level DCI 508.

[0076] In a second option for signaling the TDRA for the second beam repetition, both the starting symbol and the length value can be indicated. These embodiments can allow for some flexibility in when the second beam repetition begins. For example, the second beam repetition may not need to begin immediately after the first beam repetition. Furthermore, in some embodiments, separately signaling both the starting symbol and the length value in the second-level DCI 508 can increase reliability. For example, if the signaling of the TDRA for the first beam is improperly decoded, the signaling of the TDRA for the second beam repetition can provide sufficient information to independently receive the second beam repetition.

[0077] In a first option for signaling the MCS for the second beam repetition, the MCS may be indicated based on the reserved MCS. For example, as discussed above, a two-bit MCS may be provided to indicate one of the reserved MCSs (corresponding to MCS indices 28-31 of Table 1, according to some embodiments) to convey the modulation order to be used for the second beam repetition.

[0078] In a second option for signaling the MCS for the second beam repetition, the MCS may be indicated based on the normal MCS. For example, as also discussed above, a five-bit MCS may be provided to indicate one of the normal MCSs (corresponding to MCS indices 1-27 of Table 1, according to some embodiments) to convey the modulation order to be used for the second beam repetition.

[0079] Second-level DCI 508 may be carried by a separate search space (SS) / CORESET, just like first-level DCI 504. In this embodiment, UE 104 may perform separate blind decoding attempts to receive PDCCH #1 and PDCCH #2. In another option, the same SS / CORESET may carry first-level DCI 504 and second-level DCI 508. In this embodiment, UE 104 may perform a single blind decoding attempt to receive both PDCCHs. In another option, second-level DCI 508 may be carried by the resources indicated by first-level DCI 504. In this embodiment, first-level DCI 504 may schedule second-level DCI 508. Therefore, UE 104 may not need to perform a blind decoding attempt to receive second-level DCI 508.

[0080] In some embodiments, the base station 108 may use multiple DCIs to schedule PUSCH repetitions with multiple beams. For example, PUSCH transmissions with repetitions on N beams may be indicated by N DCIs.

[0081] The base station 108 may include an RRC parameter to enable multiple DCI operation. Providing this RRC parameter may inform the UE 104 that multiple DCIs correspond to multiple repetition sets for one PUSCH transmission on different beams, as opposed to multiple transmissions of an entire PUSCH transmission (e.g., an initial transmission and retransmissions based on a negative acknowledgement) or other PUSCH transmissions.

[0082] When multiple DCIs are enabled, N DCIs may be transmitted before the first PUSCH repetition scheduled by the first DCI.

[0083] In some embodiments, the N DCIs may include common information that allows the UE 104 to determine that the multiple DCIs correspond to multiple repetition sets on different beams, rather than retransmissions of a PUSCH transmission or transmissions of another PUSCH transmission. The common information may include, for example, an uplink (UL) / supplemental UL indicator; a bandwidth fraction indicator; a hybrid automatic repeat request (HARQ) process number; an uplink shared channel (UL-SCH) indicator; or a new data indicator.

[0084] Similar to the above implementation, the UE 104 may transmit the same TB across all repetitions scheduled by the N DCIs.The size of the TB may be determined based on one of the following options.

[0085] In a first option, the TB size can be determined by the first DCI, and only the reserved MCS can be indicated in other DCIs. For example, the first DCI can include a five-bit MCS indication based on which the TB size and uplink resource allocation can be determined. Subsequent DCIs can include a two-bit MCS indication that can be used to determine the repeated modulation order not indicated by the first DCI. The presence of the five-bit MCS can identify the first DCI as the first DCI.

[0086] Alternatively, a normal MCS may be indicated in other DCIs (indicated by a 5-bit MCS). The normal MCS in DCIs other than the first DCI may be used only to indicate the modulation order of the corresponding repetition set. To clarify which DCI is the first DCI (and therefore which DCI is the basis for determining the TB size), the base station 108 may provide an indicator. In some embodiments, the indicator may be in all DCIs (indicating whether the DCI is the first DCI), only in the first DCI (indicating that the first DCI is the first DCI), or only in DCIs that are not the first DCI (indicating that these DCIs are not the first DCI). In some embodiments, the indicator may be based on the DCI format used. For example, the first DCI may use the first DCI format, while other DCIs use the second DCI format. In some embodiments, the indicator may be configured by higher-layer signaling.

[0087] Because the UE 104 may rely on the first DCI to determine the TB size, according to some embodiments, if the UE fails to correctly decode the first DCI, the first DCI may not transmit additional PUSCH repetitions.

[0088] In a second option, the TB size may be explicitly indicated by the DCI. Thus, the DCI may provide a direct indication of the TB size, and there may be no need to calculate the TB size based on the MCS and uplink resource allocation at the UE 104. In this embodiment, each DCI may only need to use a two-bit MCS indication to indicate the reserved MCS.

[0089] Figure 6 An operational flow / algorithm structure 600 according to some embodiments is shown. The operational flow / algorithm structure 600 may be performed or implemented by a UE (such as, for example, UE 104 or UE 1000) or a component thereof (eg, baseband processor 1004A).

[0090] The operational flow / algorithm structure 600 may include processing DCI to determine scheduling of PUSCH transmissions at 604. The DCI may include a single DCI, two-stage DCI, or multiple DCI that may be used to schedule PUSCH transmissions with multiple repetitions on at least two transmit beams.

[0091] In some embodiments, the multiple repetition sets may correspond to a corresponding plurality of transmit beams. The repetition sets may be configured differently. In some embodiments, the different configurations may include different FDRA configurations, TDRA configurations, or MCS configurations. In some embodiments, the DCI received at 604 may indicate different configurations for different repetition sets, either alone or in combination with other control signaling (e.g., RRC configuration signaling).

[0092] Different FDRA configurations may include, for example, different frequency hopping patterns configured in different repetition sets, different frequency bandwidth allocations in different repetition sets, and the like.

[0093] Different TDRA configurations may include, for example, different starting symbols or length values for different repetition sets. In some embodiments, the DCI may include a common indication of different TDRA configurations by referencing the RRC configuration. In some embodiments, the RRC configuration may be based on a TDRA IE provided to the UE via RRC signaling. In other embodiments, the DCI may include multiple time domain resource assignment fields for indicating different starting symbols or length values for different repetition sets.

[0094] Different MCS configurations may include different modulation orders for different repetition sets. In some embodiments, the DCI may indicate the normal / reserved MCS for different repetition sets. The TB size for all repetitions may be determined based on the MCS and uplink resource allocation for the first repetition set, while the modulation order for other repetition sets may be based on the corresponding MCS value.

[0095] The operational flow / algorithm structure 600 may further include transmitting a PUSCH transmission with repetitions using multiple transmit beams, at 608. The UE may transmit a PUSCH transmission with repetition sets on corresponding transmit beams according to their different configurations.

[0096] Figure 7 An operational flow / algorithm structure 700 according to some embodiments may be included. The operational flow / algorithm structure 700 may be performed or implemented by a UE (such as, for example, UE 104 or UE 1000) or a component thereof (eg, baseband processor 1004A).

[0097] The operational flow / algorithm structure 700 may include, at 704, storing an RRC configuration. The RRC configuration may be based on RRC signaling received from a base station. The RRC signaling may include any of a variety of configuration IEs, including, for example, a PUSCH configuration IE. In some embodiments, the RRC signaling may include a PUSCH-TDRA IE to configure start and symbol length values that may be used for multiple repetition sets. In some embodiments, the RRC signaling may include parameters for enabling multi-DCI operation.

[0098] The operational flow / algorithm structure 700 may also include receiving DCI to schedule PUSCH transmissions with repetitions at 708. Similar to the discussion above with respect to 604, the DCI may include a single DCI, a two-stage DCI, or multiple DCIs. The DCI may schedule PUSCH transmissions with repetition sets corresponding to corresponding transmit beams.

[0099] The operational flow / algorithm structure 700 may also include transmitting a PUSCH transmission with repetitions based on the RRC configuration and the DCI, at 712. The PUSCH transmission with the repetition set may be transmitted on corresponding transmit beams with different configurations as described herein.

[0100] Figure 8 An operational flow / algorithm structure 800 according to some embodiments may be included. The operational flow / algorithm structure 800 may be performed or implemented by a base station such as, for example, base station 108 or gNB 1100, or a component thereof, such as baseband processor 1104A.

[0101] The operational flow / algorithm structure 800 may include, at 804, transmitting RRC signaling. The RRC signaling may include any of a variety of configuration IEs, including, for example, a PUSCH configuration IE. In some embodiments, the RRC signaling may include a PUSCH-TDRA IE to configure start and symbol length values that may be used for multiple repetition sets. In some embodiments, the RRC signaling may include parameters for enabling multi-DCI operation.

[0102] The operational flow / algorithm structure 800 may include, at 808, transmitting DCI to schedule PUSCH transmissions. Similar to the discussion above with respect to 604, the DCI may include a single DCI, a two-stage DCI, or multiple DCIs. The DCI may schedule PUSCH transmissions with repetition sets corresponding to corresponding transmit beams. Different repetition sets may be configured (via DCI / RRC) with different time / frequency / MCS configurations.

[0103] Operational flow / algorithm structure 800 may also include, at 812, receiving a PUSCH transmission. The base station may receive PUSCH transmissions having different repetition sets transmitted using different transmit beams. In some embodiments, some repetition sets may be directed to or received by a specific network element (e.g., a TRP), while other repetition sets may be directed to or received by a different network element. In these embodiments, the network element (e.g., a TRP) may provide the repetition sets to a centralized controller of the base station for further processing.

[0104] Figure 9900 according to some embodiments. Beamforming circuit 900 may include a first antenna panel (i.e., panel 1 1004) and a second antenna panel (i.e., panel 2 908). Each antenna panel may include multiple antenna elements. Other embodiments may include other numbers of antenna panels.

[0105] The digital beamforming (BF) component 928 may receive data from, for example, a baseband processor such as, for example, Figure 11 The baseband processor 1104A of the RF receiver receives an input baseband (BB) signal. The digital BF component 928 may rely on complex weights to precode the BB signal and provide a beamformed BB signal to the parallel radio frequency (RF) chains 920 / 924.

[0106] Each RF chain 920 / 924 may include a digital-to-analog converter that converts the BB signal into the analog domain, a mixer that mixes the baseband signal into an RF signal, and a power amplifier that amplifies the RF signal for transmission.

[0107] The RF signal may be provided to analog BF components 912 / 916, which may additionally apply beamforming by providing phase shifting in the analog domain.The RF signal may then be provided to antenna panels 904 / 908 for transmission.

[0108] In some embodiments, beamforming may be done solely in the digital domain or solely in the analog domain, instead of the hybrid beamforming shown here.

[0109] In various embodiments, control circuitry, which may reside in a baseband processor, may provide BF weights to analog / digital BF components to provide transmit beams at corresponding antenna panels. These BF weights may be determined by the control circuitry to provide directional deployment of serving cells as described herein. In some embodiments, the BF components and antenna panels may operate together to provide a dynamic phased array capable of steering a beam in a desired direction.

[0110] Figure 10 UE 1000 according to some embodiments is shown. UE 1000 may be similar to Figure 1 UE 104 and is essentially interchangeable therewith.

[0111] UE 1000 can be any mobile or non-mobile computing device, such as a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, an actuator, etc.), a video monitoring / surveillance device (e.g., a camera, a camcorder, etc.), a wearable device (e.g., a smart watch), or a loose IoT device.

[0112] UE 1000 may include a processor 1004, RF interface circuitry 1008, memory / storage 1012, a user interface 1016, sensors 1020, driver circuitry 1022, a power management integrated circuit (PMIC) 1024, antenna structures 1026, and a battery 1028. The components of UE 1000 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logical components, hardware, software, firmware, or combinations thereof. Figure 10 The block diagram is intended to show a high-level view of certain of the components of the UE 1000. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0113] Components of UE 1000 may be coupled to various other components via one or more interconnects 1032, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., that allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0114] The processor 1004 may include processor circuits such as a baseband processor circuit (BB) 1004A, a central processor unit circuit (CPU) 1004B, and a graphics processor unit circuit (GPU) 1004C. The processor 1004 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from the memory / storage device 1012) to cause the UE 1000 to perform operations as described herein.

[0115] In some embodiments, the baseband processor circuit 1004A can access the communication protocol stack 1036 in the memory / storage device 1012 to communicate over a 3GPP-compatible network. Generally speaking, the baseband processor circuit 1004A can access the communication protocol stack to perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some embodiments, PHY layer operations can additionally / alternatively be performed by components of the RF interface circuit 1008.

[0116] The baseband processor circuit 1004A may generate or process baseband signals or waveforms that carry information in a 3GPP-compliant network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM ("CP-OFDM") in the uplink or downlink, and discrete Fourier transform spread OFDM ("DFT-S-OFDM") in the uplink.

[0117] The memory / storage 1012 may include one or more non-transitory computer-readable media containing instructions (e.g., the communication protocol stack 1036) that are executable by one or more processors in the processor 1004 to cause the UE 1000 to perform the various operations described herein. The memory / storage 1012 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1000. In some embodiments, some of the memory / storage 1012 may be located on the processor 1004 itself (e.g., an L1 cache and an L2 cache), while other memory / storage 1012 may be external to the processor 1004 but accessible via a memory interface. The memory / storage 1012 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0118] The RF interface circuit 1008 may include transceiver circuitry and a radio frequency front-end module (RFEM), which allows the UE 1000 to communicate with other devices via a radio access network. The RF interface circuit 1008 may include various components arranged in a transmit path or a receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0119] In the receive path, the RFEM receives the radiated signal from the air interface via the antenna structure 1026 and further filters and amplifies the signal (using a low-noise amplifier). The signal can be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1004.

[0120] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides an RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna 1026.

[0121] In various embodiments, the RF interface circuit 1008 may be configured to transmit / receive signals in a manner compatible with NR access technology.

[0122] Antenna 1026 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 1026 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple-input, multiple-output communications. Antenna 1026 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, and the like. Antenna 1026 may have one or more panels designed for a specific frequency band, including a band in FR1 or FR2.

[0123] User interface circuitry 1016 includes various input / output (I / O) devices designed to enable a user to interact with UE 1000. User interface 1016 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a trackpad, a touch screen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying or otherwise communicating information, such as sensor readings, actuator positions, or other similar information. Output device circuitry may include any number or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary state indicators (such as light emitting diodes "LEDs") and multi-character visual outputs), or more complex outputs, such as a display device or touch screen (e.g., a liquid crystal display "LCD," an LED display, a quantum dot display, a projector, etc.), where the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 1100.

[0124] Sensors 1020 may include devices, modules, or subsystems whose purpose is to detect events or changes in their environment and to send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a fluid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0125] The driver circuit 1022 may include software and hardware components for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1000. The driver circuit 1022 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1000. For example, the driver circuit 1022 may include a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings from the sensor circuit 1020 and controlling and allowing access to the sensor circuit 1020, a driver for obtaining actuator positions of electromechanical components or controlling and allowing access to electromechanical components, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0126] The PMIC 1024 may manage power provided to various components of the UE 1000. Specifically, with respect to the processor 1004, the PMIC 1024 may control power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0127] In some embodiments, the PMIC 1024 may control or otherwise be part of various power saving mechanisms of the UE 1000 , including DRX, as discussed herein.

[0128] The battery 1028 can power the UE 1000, but in some examples, the UE 1000 can be installed in a fixed location and can have a power source coupled to the power grid. The battery 1028 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in vehicle-based applications, the battery 1028 can be a typical lead-acid automobile battery.

[0129] Figure 11 FIGURE 1 shows a gNB 1100 according to some embodiments. The gNB node 1100 may be similar to Figure 1 base station 108 and is essentially interchangeable therewith.

[0130] gNB 1100 may include a processor 1104, RF interface circuitry 1108, core network “CN” interface circuitry 1112, memory / storage device circuitry 1116, and antenna structures 1126.

[0131] Components of gNB 1100 may be coupled to various other components via one or more interconnects 1128.

[0132] The processor 1104, RF interface circuit 1108, memory / storage circuit 1116 (including communication protocol stack 1110), antenna structure 1126 and interconnect 1128 may be similar to those of reference Figure 10 Like-named elements are shown and described.

[0133] The CN interface circuitry 1112 can provide connectivity to a core network (e.g., a 5th Generation Core Network (5GC) using a 5GC-compatible network interface protocol (such as the Carrier Ethernet protocol) or some other suitable protocol). Network connectivity can be provided to and from the gNB 1100 via optical fiber or wireless backhaul. The CN interface circuitry 1112 can include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1112 can include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0134] In some embodiments, gNB 1100 may couple to a TRP such as TRP 112 or 116 using antenna structure 1126, CN interface circuitry, or other interface circuitry.

[0135] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0136] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples described below. For another example, circuitry associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0137] Example

[0138] In the following sections, additional exemplary embodiments are provided.

[0139] Embodiment 1 may include a method of operating a UE, the method comprising: processing one or more downlink control information (DCI) to determine a schedule for a physical uplink shared channel (PUSCH) transmission having multiple repetitions, wherein a first repetition having a first configuration in the multiple repetitions is to be transmitted using a first transmit beam, and a second repetition in the multiple repetitions is to be transmitted using a second transmit beam, wherein the first configuration and the second configuration include different time or frequency allocations or modulation orders; and transmitting the PUSCH transmission having the multiple repetitions using at least two transmit beams including the first transmit beam and the second transmit beam.

[0140] Embodiment 2 may include a method according to embodiment 1 or some other embodiment herein, wherein the one or more DCIs include a single DCI having separate fields indicating the first configuration and the second configuration individually or a single field indicating the first configuration and the second configuration collectively, wherein the first configuration and the second configuration are a first frequency domain resource allocation (FDRA) and a second FDRA, a first time domain resource allocation (TDRA) and a second TDRA, or a first modulation and coding scheme (MCS) and a second MCS.

[0141] Embodiment 3 may include the method according to embodiment 2 or some other embodiment herein, wherein the first configuration and the second configuration include a first FDRA and a second FDRA, the first FDRA and the second FDRA defining different frequency bandwidths or frequency hopping patterns for the first repetition and the second repetition.

[0142] Embodiment 4 may include a method according to embodiment 2 or some other embodiment herein, wherein the first configuration and the second configuration include a first TDRA and a second TDRA, wherein the first TDRA defines a first starting symbol and a length value corresponding to the first repetition, and the second TDRA defines a second starting symbol and a length value corresponding to the second repetition.

[0143] Embodiment 5 may include a method according to embodiment 2 or some other embodiment herein, wherein the first configuration and the second configuration include a first MCS and a second MCS, and the method further includes: determining a modulation and coding scheme for the first repetition based on the first MCS; determining a transport block size for the multiple repetitions based on the first MCS; and determining a modulation order for the second repetition based on the second MCS.

[0144] Embodiment 6 may include a method as in embodiment 5 or some other embodiment herein, wherein the first MCS comprises a five-bit indicator and the second MCS comprises a two-bit indicator.

[0145] Embodiment 7 may include a method as in embodiment 5 or some other embodiment herein, wherein the first MCS includes a first five-bit indicator and the second MCS includes a second five-bit indicator.

[0146] Embodiment 8 may include the method of embodiment 6 or 7, wherein the instructions, when executed, further cause the UE to: determine a phase tracking reference signal for the first repetition based on the first MCS.

[0147] Embodiment 9 may include a method according to embodiment 1 or some other embodiment herein, wherein the first configuration includes a first uplink resource allocation for the first repetition, and the second configuration includes a second uplink resource allocation for the second repetition, and the method further includes: determining a modulation and coding scheme (MCS); and determining a transport block size for the multiple repetitions based on the MCS and the first uplink resource allocation.

[0148] Embodiment 10 may include a method according to embodiment 1 or some other embodiment herein, wherein the one or more DCIs include a first-level DCI and a second-level DCI, wherein the first-level DCI is to be provided for control signaling for the first repetition and the second-level DCI is to be provided for control signaling for the second repetition.

[0149] Embodiment 11 may include a method according to embodiment 1 or some other embodiment herein, wherein the one or more DCIs include at least two DCIs corresponding to the at least two transmit beams, respectively, and the method further includes: processing radio resource control parameters to enable operation using the at least two DCIs; and receiving the at least two DCIs before the first repetition of the multiple PUSCH repetitions.

[0150] Embodiment 12 may include a method of operating a UE, the method comprising: storing a radio resource control (RRC) configuration; receiving one or more downlink control information (DCI) to schedule a physical uplink shared channel (PUSCH) having multiple repetitions through two or more beams; and transmitting a first repetition having a first configuration in the multiple repetitions and a second repetition having a second configuration in the multiple repetitions based on the one or more DCIs and the RRC configuration, wherein the first configuration and the second configuration include different time or frequency allocations or modulation orders.

[0151] Embodiment 13 may include a method according to embodiment 12 or some other embodiment herein, wherein the one or more DCIs include a single DCI having separate fields indicating the first configuration and the second configuration individually or a single field indicating the first configuration and the second configuration collectively, wherein the first configuration and the second configuration are a first frequency domain resource allocation (FDRA) and a second FDRA, a first time domain resource allocation (TDRA) and a second TDRA, or a first modulation and coding scheme (MCS) and a second MCS.

[0152] Embodiment 14 may include the method of embodiment 13 or some other embodiment herein, wherein the first configuration and the second configuration include a first FDRA and a second FDRA, the first FDRA and the second FDRA defining different frequency bandwidths or frequency hopping patterns for the first repetition and the second repetition.

[0153] Embodiment 15 may include a method according to embodiment 13 or some other embodiment herein, wherein the first configuration and the second configuration include a first TDRA and a second TDRA, wherein the first TDRA defines a first starting symbol and a length value corresponding to the first repetition, and the second TDRA defines a second starting symbol and a length value corresponding to the second repetition.

[0154] Embodiment 16 may include a method according to embodiment 15 or some other embodiment herein, wherein the method further comprises: receiving RRC signaling with PUSCH time domain resource allocation information (TDRA) (IE) to provide the first starting symbol and length value and the second starting symbol and length value; and storing the RRC configuration based on the PUSCH TDRA IE.

[0155] Embodiment 17 may include a method according to embodiment 13 or some other embodiment herein, wherein the first configuration and the second configuration include a first MCS and a second MCS, wherein the method further comprises: determining a modulation and coding scheme for the first repetition based on the first MCS; determining a transport block size for the multiple repetitions based on the first MCS and uplink resource allocation for the first repetition; and determining a modulation order for the second repetition based on the second MCS.

[0156] Embodiment 17.1 may include a method as in Embodiment 17 or some other embodiment herein, wherein the first MCS includes a first five-bit indicator and the second MCS includes a second five-bit indicator or a two-bit indicator.

[0157] Embodiment 17.2 may include a method according to embodiment 17.1 or some other embodiment herein, further comprising: determining a phase tracking reference signal for the first repetition based on the first MCS.

[0158] Embodiment 18 includes a method of operating a base station, the method comprising: transmitting radio resource control (RRC) signaling to configure a user equipment with physical uplink shared channel (PUSCH) allocation information; transmitting one or more downlink control information (DCI) to schedule PUSCH transmissions having multiple repetitions on at least two beams based on the PUSCH allocation information, wherein a first repetition having a first configuration is to be scheduled for transmission on the first beam and a second repetition having a second configuration is to be scheduled for transmission on the second beam, wherein the first configuration and the second configuration include different time or frequency allocations or modulation orders; and receiving the PUSCH transmission from the user equipment.

[0159] Embodiment 19 may include a method according to embodiment 18 or some other embodiment herein, wherein the PUSCH allocation information includes a PUSCH time domain resource allocation information element, the PUSCH time domain resource allocation information element includes multiple start symbols and length values, the first configuration is to indicate a first start symbol and length value from the multiple start symbols and length values used for the first repetition, and the second configuration is to indicate a second start symbol and length value from the multiple start symbols and length values used for the second repetition.

[0160] Embodiment 20 may include a method according to embodiment 19 or some other embodiment herein, wherein the first configuration and the second configuration are a first frequency domain resource allocation (FDRA) and a second FDRA, a first time domain resource allocation (TDRA) and a first or modulation and coding scheme (MCS) and a second MCS.

[0161] Example 21 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Examples 1-20, or any other method or process described herein.

[0162] Embodiment 22 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any one of Embodiments 1 to 20 or any other method or process described herein.

[0163] Embodiment 23 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1-20, or any other method or process described herein.

[0164] Example 24 may include methods, techniques, or processes as described or related to any one of Examples 1 to 20, or portions or components thereof.

[0165] Embodiment 25 may include a device comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portion thereof, as described or related to any one of Embodiments 1 to 20.

[0166] Embodiment 26 may include a signal as described or associated with any one of Embodiments 1 to 20, or a portion or component thereof.

[0167] Embodiment 27 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or associated with any one of embodiments 1 to 20, or otherwise described in this disclosure.

[0168] Embodiment 28 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 20, or a portion or component thereof, or as otherwise described in this disclosure.

[0169] Embodiment 29 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU, or message as described or associated with any one of embodiments 1 to 20, or a portion or component thereof, or otherwise described in this disclosure.

[0170] Embodiment 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform the method, technique, or process described in or related to any one of Embodiments 1 to 20, or a portion thereof.

[0171] Embodiment 31 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of Embodiments 1 to 20, or a portion thereof.

[0172] Embodiment 32 may include signals in a wireless network as shown and described herein.

[0173] Embodiment 33 may include a method of communicating in a wireless network as shown and described herein.

[0174] Embodiment 34 may include a system for providing wireless communications as shown and described herein.

[0175] Embodiment 35 may include an apparatus for providing wireless communications as shown and described herein.

[0176] Unless expressly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the various embodiments.

[0177] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause user equipment (UE) to: processing one or more downlink control information (DCI) to determine a schedule for physical uplink shared channel (PUSCH) transmissions having a plurality of repetitions, wherein a first repetition of the plurality of repetitions having a first configuration is to be transmitted using a first transmit beam and a second repetition of the plurality of repetitions is to be transmitted using a second transmit beam, wherein the first configuration and the second configuration include different time or frequency allocations or modulation orders; determining a transport block size for each of the plurality of repetitions based on a 5-bit indication of a modulation and coding scheme (MCS) for a first repetition of the plurality of repetitions; as well as The PUSCH transmission with the plurality of repetitions is generated using the transport block size, a resource allocation for the first of the plurality of repetitions, and at least two transmit beams including the first transmit beam and the second transmit beam.

2. The one or more computer-readable media of claim 1 , wherein the instructions, when executed, further cause the UE to: The PUSCH transmission is transmitted by applying a frequency hopping pattern to the plurality of repetitions.

3. The one or more computer-readable media of claim 1 , wherein the instructions, when executed, further cause the UE to: A modulation order for the plurality of repetitions is determined based on the 5-bit indication of the MCS.

4. One or more computer-readable media according to any one of claims 1 to 3, wherein the one or more DCIs include a single DCI, the single DCI having separate fields indicating the first configuration and the second configuration individually or a single field indicating the first configuration and the second configuration collectively, wherein the first configuration and the second configuration are a first frequency domain resource allocation FDRA and a second FDRA, a first time domain resource allocation TDRA and a second TDRA, or a first modulation and coding scheme MCS and a second MCS.

5. The one or more computer-readable media of claim 4, wherein the first configuration and the second configuration include a first FDRA and a second FDRA, the first FDRA and the second FDRA defining different frequency bandwidths or frequency hopping patterns for the first repetition and the second repetition.

6. One or more computer-readable media according to claim 4, wherein the first configuration and the second configuration include a first TDRA and a second TDRA, wherein the first TDRA defines a first starting symbol and a length value corresponding to the first repetition, and the second TDRA defines a second starting symbol and a length value corresponding to the second repetition.

7. The one or more computer-readable media of claim 4, wherein the first configuration and the second configuration include a first MCS and a second MCS, wherein the instructions, when executed, further cause the UE to: determining a modulation and coding scheme for the first repetition based on the first MCS; determining a transport block size for the plurality of repetitions based on the first MCS; determining a modulation order for the second repetition based on the second MCS, The first MCS includes a five-bit indicator, and the second MCS includes a two-bit indicator or another five-bit indicator.

8. The one or more computer-readable media of claim 7, wherein the instructions, when executed, further cause the UE to: determine a phase tracking reference signal for the first repetition based on the first MCS.

9. One or more computer-readable media according to any one of claims 1 to 3 and 5 to 8, wherein the first configuration comprises a first uplink resource allocation for the first repetition, and the second configuration comprises a second uplink resource allocation for the second repetition, and the instructions, when executed, further cause the UE to: Determine the modulation and coding scheme MCS.

10. One or more computer-readable media according to any one of claims 1 to 3 and 5 to 8, wherein the one or more DCIs include a first-level DCI and a second-level DCI, wherein the first-level DCI is to be provided for control signaling of the first repetition and the second-level DCI is to be provided for control signaling of the second repetition.

11. One or more computer-readable media according to any one of claims 1 to 3 and 5 to 8, wherein the one or more DCIs include at least two DCIs corresponding to the at least two transmit beams, respectively, and the instructions, when executed, further cause the UE to: processing radio resource control parameters to enable operation using the at least two DCIs; and The at least two DCIs are received before a first repetition of the plurality of repetitions.

12. A user equipment comprising: a memory, the memory being configured to store a radio resource control (RRC) configuration; as well as a processing circuit, the processing circuit being coupled to the memory, the processing circuit being configured to: Processing one or more downlink control information (DCI) to schedule a physical uplink shared channel (PUSCH) with multiple repetitions through two or more beams; generating a first repetition of the plurality of repetitions having a first configuration and a second repetition of the plurality of repetitions having a second configuration based on the one or more DCIs and the RRC configuration, wherein the first configuration and the second configuration include different time or frequency allocations or modulation orders; determining a transport block size for each of the plurality of repetitions based on a 5-bit indication of a modulation and coding scheme (MCS) for a first repetition of the plurality of repetitions; as well as A first repetition in the plurality of repetitions having a first configuration and a second repetition in the plurality of repetitions having a second configuration are generated based on the one or more DCIs and the RRC configuration and the transport block size, wherein the first configuration and the second configuration include different time or frequency allocations or modulation orders.

13. A user equipment according to claim 12, wherein the one or more DCIs include a single DCI, the single DCI having separate fields indicating the first configuration and the second configuration separately or a single field indicating the first configuration and the second configuration jointly, wherein the first configuration and the second configuration are a first frequency domain resource allocation FDRA and a second FDRA, a first time domain resource allocation TDRA and a second TDRA, or a first modulation and coding scheme MCS and a second MCS.

14. The user equipment of claim 13, wherein the first configuration and the second configuration include a first FDRA and a second FDRA, the first FDRA and the second FDRA defining different frequency bandwidths or frequency hopping patterns for the first repetition and the second repetition.

15. The user equipment of claim 13, wherein the first configuration and the second configuration include a first TDRA and a second TDRA, wherein the first TDRA defines a first starting symbol and a length value corresponding to the first repetition, and the second TDRA defines a second starting symbol and a length value corresponding to the second repetition.

16. The user equipment of claim 15, wherein the processing circuit is further configured to: Receiving RRC signaling with PUSCH time domain resource allocation information TDRA IE to provide the first starting symbol and length value and the second starting symbol and length value; and The RRC configuration is stored based on the PUSCH TDRA IE.

17. The user equipment of claim 13, wherein the first configuration and the second configuration include a first MCS and a second MCS, wherein the processing circuit is further configured to: determining a modulation and coding scheme for the first repetition based on the first MCS; and A modulation order for the second repetition is determined based on the second MCS.

18. The user equipment of claim 17, wherein the processing circuit is further configured to: determine a phase tracking reference signal for the first repetition based on the first MCS.

19. A method of operating a base station, the method comprising: generating radio resource control (RRC) signaling to configure a user equipment with physical uplink shared channel (PUSCH) allocation information; generating one or more downlink control information (DCI) to schedule PUSCH transmission with a plurality of repetitions on at least two beams based on the PUSCH allocation information, wherein a first repetition with a first configuration is scheduled for transmission on the first beam and a second repetition with a second configuration is scheduled for transmission on the second beam, wherein the first configuration and the second configuration include different time or frequency allocations or modulation orders, and the one or more DCIs include a 5-bit indication of a modulation and coding scheme (MCS) for a first repetition of the plurality of repetitions; and The PUSCH transmission is received from the user equipment.

20. The method according to claim 19, wherein the PUSCH allocation information includes a PUSCH time domain resource allocation information element, the PUSCH time domain resource allocation information element includes multiple start symbols and length values, the first configuration is to indicate a first start symbol and length value from the multiple start symbols and length values used for the first repetition, and the second configuration is to indicate a second start symbol and length value from the multiple start symbols and length values used for the second repetition. 21 . The method of claim 20 , wherein the first configuration and the second configuration are first and second frequency domain resource allocations (FDRA and FDRA), first and second time domain resource allocations (TDRA and TDRA), or first and second modulation and coding schemes (MCS and MCS).

Images