Phase tracking reference signal transmission for physical uplink shared channel reliability enhancement

Abstract

The present application relates to devices and components including apparatus, systems, and methods for physical uplink shared channel transmissions with repetitions on different transmit beams and utilizing a phase tracking reference signal.

Description

Technical Field

[0001] The present application relates to the field of communications. Background Art

[0002] A Phase Tracking Reference Signal (PTRS) may be associated with the Physical Uplink Shared Channel (PUSCH) to compensate for the phase offset of each symbol. Summary of the Invention

[0003] Embodiments of the present disclosure provide methods, devices, and computer-readable media for phase tracking reference signal transmission with enhanced reliability of a physical uplink shared channel.

[0004] In a first aspect of the present disclosure, one or more computer-readable media are provided, having instructions that, when executed, cause a processing circuit to perform the following operations: process scheduling information to determine a schedule for physical uplink shared channel (PUSCH) transmissions having multiple repetitions, wherein the multiple repetitions include at least two repetition sets to be transmitted using at least two transmit beams, respectively; determine an indicated maximum number of phase tracking reference signal (PTRS) ports for all the multiple repetitions based on radio resource control (RRC) signaling; determine a certain number of PTRS ports based on the indicated maximum number of PTRS ports for transmitting PTRS associated with each of the at least two repetition sets; generate the PUSCH transmissions having the multiple repetitions transmitted using the at least two transmit beams; and generate the PTRS transmitted through the said number of PTRS ports.

[0005] In a second aspect of the present disclosure, a method for communication is provided, the method comprising: processing scheduling information to determine a schedule for physical uplink shared channel (PUSCH) transmissions having multiple repetitions, wherein the multiple repetitions include at least two repetition sets to be transmitted using at least two transmit beams, respectively; determining an indicated maximum number of phase tracking reference signal (PTRS) ports for all the multiple repetitions based on radio resource control (RRC) signaling; determining a certain number of PTRS ports for transmitting PTRS associated with each of the at least two repetition sets; generating the PUSCH transmissions having the multiple repetitions transmitted using the at least two transmit beams; and generating the PTRS transmitted through the number of PTRS ports.

[0006] In a third aspect of the present disclosure, a processing circuit is provided, which is used to: process scheduling information to determine a schedule for physical uplink shared channel (PUSCH) transmissions having multiple repetitions, wherein the multiple repetitions include at least two repetition sets to be transmitted using at least two transmit beams respectively; determine an indicated maximum number of phase tracking reference signal (PTRS) ports for all the multiple repetitions based on radio resource control (RRC) signaling; determine a certain number of PTRS ports for transmitting PTRS associated with each of the at least two repetition sets; generate the PUSCH transmissions having the multiple repetitions transmitted using the at least two transmit beams; and generate the PTRS transmitted through the said number of PTRS ports.

[0007] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the disclosure, nor is it intended to limit the scope of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0009] Figure 2 Shown is a time slot transmission according to some embodiments.

[0010] Figure 3 A signaling diagram according to some embodiments is shown.

[0011] Figure 4 Another signaling diagram according to some embodiments is shown.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0034] 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 a transmission reception point (AP) or other device. 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).

[0035] Base stations 108 may use APs 116 / 120 to geographically separate points at which 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.

[0036] Although network environment 100 illustrates 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 wireless access network connectivity for UE 104. For example, in some embodiments, base station 108 may be locally coupled to AP 116, while another base station may be locally coupled to AP 120. Base station 108 may communicate with the other base stations over ideal or non-ideal backhauls to facilitate communication with UE 104.

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

[0038] 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. Using beam management operations, based on reference signal measurements and channel reciprocity assumptions, the UE 104 and base station 108 can determine the desired uplink-downlink beam pairs.

[0039] In the downlink direction, the base station 108 may transmit synchronization signal blocks (SSBs) and channel state information-reference signals (CSI-RSs) measured by the UE 104 to determine the downlink beam pair required for transmitting / receiving physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH) transmissions. In some embodiments, the network element may assume uplink / downlink beam correspondence and use the required downlink beam pair as the uplink beam pair required for PUSCH 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 stages, such as initial acquisition of uplink and downlink beams and later refinement of the uplink and downlink beams.

[0040] The PUSCH may be used to transmit user data for the user plane and signaling radio bearer (SRB) messages for the control plane. The PUSCH may also be used to transmit various control information such as, for example, buffer status reports, cell radio network temporary identifiers (C-RNTIs), configured grant configurations, and power headroom reports.

[0041] The base station 108 may schedule a PUSCH transmission 124. The PUSCH transmission 124 may be scheduled using multiple repetitions that may be transmitted by one or more beams. Each repetition of the PUSCH transmission may carry the same transport block (TB) to increase the reliability of the PUSCH transmission. Each repetition may be transmitted on one or more transmission layers using multiple-input multiple-output (MIMO) technology.

[0042] As shown, PUSCH transmission 124 may include four repetitions, where repetitions #1 and #2 are scheduled for transmission to AP 116 using beam #1, and repetitions #3 and #4 are scheduled for transmission to AP 120 using beam #2. These repetitions may be divided into repetition sets, each of which includes repetitions with similar beam configurations. For example, repetitions #1 and #2 may be included in repetition set 1, while repetitions #3 and #4 may be included in repetition set 2.

[0043] In some embodiments, similar beam configurations may be determined based on repetitions in a repetition set sharing an SRS resource indicator (SRI) or a transmit precoder matrix indicator (TPMI). A repetition set may include one or more repetitions.

[0044] The base station 108 may schedule PUSCH transmissions using either a dynamic grant (DG) or a configured grant (CG). A PUSCH scheduled by a dynamic grant (DG-PUSCH) may be scheduled via DCI in a PDCCH that provides separate resource allocations for the DG-PUSCH. A PUSCH scheduled by a configured grant (CG-PUSCH) may be scheduled by a base station 108 that configures a dedicated set of resource blocks that may be used for the CG-PUSCH for the UE 104. Control signaling for the CG-PUSCH may include RRC signaling with or without layer 1 (e.g., PHY layer) signaling that serves as an activation trigger.

[0045] The UE 104 may utilize the PUSCH to transmit an uplink phase tracking reference signal (PTRS) to allow the base station 108 to estimate and compensate for both phase noise and frequency offset that may be generated based on the operation of the oscillators at the transmitter and receiver. This may be particularly prevalent in higher frequency bands where there may be greater phase noise, which may result in phase shifts for different symbols.

[0046] Figure 2 A time slot transmission 200 according to some embodiments is shown. Time slot transmission 200 may include DMRS 204, PUSCH transmission 208, and PTRS 212. PTRS 212 may be inserted into orthogonal frequency division multiplexing (OFDM) symbols that do not include DMRS 204. Phase noise may vary over time rather than frequency. Therefore, the density of PTRS 212 may be higher in the time domain than in the frequency domain.

[0047] Assuming that the same precoder is used to transmit DMRS 204 and PTRS 212, base station 108 can compensate for the phase noise effects and phase shift in DMRS 204 after receiving time slot transmission 200. Specifically, the receiver of base station 108 can compare the phase shift between PTRS 212 and DMRS 204 to calculate a phase offset that can be used to compensate for the phase shift of all subcarriers of DMRS 204.

[0048] In the current version of the 3GPP technical specifications, up to two PTRS ports may be supported. If the UE 104 includes multiple antenna panels, two PTRS ports may be desired, given that the local oscillator associated with each panel may be a separate source of phase noise and frequency offset. The UE 104 may signal its support for transmitting PTRS on one or two antenna ports via the onePortsPTRS information element (IE) and the twoPortsPTRS IE, respectively. The onePortsPTRS IE may indicate whether the UE supports single-port PTRS in Band 1 (410 MHz - 7125 MHz), as the UE 104 may be required to support single-port PTRS in Band 2 (24.25 GHz - 52.6 GHz).

[0049] Each PTRS port can be associated with a DMRS port, where the same digital precoder is applied to the PTRS and its associated DMRS. The two PTRS ports can be used for non-coherent / partially coherent precoders.

[0050] The association between the PTRS port and the DMRS port can be provided by control signaling that provides authorization information. For example, for DG-PUSCH, referring to one PTRS port in Table 1 and two PTRS ports in Table 2, the association between the PTRS and DMRS ports can be indicated by the DCI field PTRS-DMRS Association. Table 1 corresponds to Table 7.3.1.1.2-25 in 3GPP TS 38.212v16.3.0 (2020-09), and Table 2 corresponds to Table 7.3.1.1.2-26 of 3GPP TS 38.212.

[0051] value DMRS port 0 First DMRS scheduling port 1 Second DMRS scheduling port 2 3rd DMRS scheduling port 3 4th DMRS scheduling port

[0052] Table 1 - PTRS-DMRS association for UL PTRS port 0

[0053]

[0054] Table 2 - PTRS-DMRS association for UL PTRS ports 0 and 1

[0055] For example, if one PTRS port is enabled and a value of '0' is indicated in the DCI, then the one PTRS port (e.g., PTRS port 0) is associated with the first DMRS scheduling port based on Table 1. Therefore, the precoder for PTRS can be the same as the first transmission layer, which can also be referred to as layer 0.

[0056] If two PTRS ports are enabled and bit values ​​'01' are indicated in the DCI, then based on Table 2, PTRS port 0 is associated with the first transport layer (based on the most significant bit (MSB) value '0') and PTRS port 1 is associated with the second transport layer (based on the least significant bit (LSB) value '1').

[0057] The number of PTRS ports can be determined by RRC signaling and the indicated precoder (e.g., TPMI) for PUSCH transmission. When PTRS is associated with PUSCH, 2-port PTRS can be enabled when all of the following conditions are true: Condition 1—In RRC, the maximum number of uplink PTRS ports is configured as two; Condition 2—The codebook subset is configured as non-coherent or partially coherent; and Condition 3—PUSCH is transmitted through ports 1000 / 1002 and ports 1001 / 1003. For Condition 3, ports 1000 / 1002 can be associated with the first antenna panel, and ports 1001 / 1003 can be associated with the second antenna panel. Therefore, Condition 3 corresponds to dual-panel PUSCH transmission. Consider, for example, Table 3, which corresponds to an excerpt from Table 6.3.1.5-5 of 3GPP TS 38.211v16.3.0 (2020-09).

[0058]

[0059] Table 3 — Precoding matrix W for dual-layer transmission using four antenna ports with transform precoding disabled

[0060] In this example, when TPMI = 0, 2, 3, 5 for rank 2 and 4-port codebooks and the UE reports that it supports 2 PTRS ports, PUSCH can be scheduled with non-coherent or partially coherent precoders on ports 1000 / 1002 and ports 1001 / 1003, and thus conditions 2 and 3 can be met. Assuming condition 1 is also met, dual-port PTRS can be used.

[0061] If all three conditions are not met, a single-port PTRS may be transmitted when the PTRS is associated with the PUSCH.

[0062] As mentioned above Figure 1As discussed, the PUSCH transmission 124 may include repetitions transmitted using different precoders. This may complicate PTRS operation relative to known techniques. Therefore, embodiments of the present disclosure describe how to determine the number of PTRS ports for each PUSCH repetition; and also describe how to determine the PTRS to DMRS association for each PUSCH repetition. Specifically, various embodiments describe PTRS transmissions for PUSCH with repetitions from multiple beams / precoders. Some aspects include control signaling for a certain number of PTRS ports and PTRS to DMRS association indication. Other aspects include UE behavior to determine the number of PTRS ports and PTRS transmission characteristics.

[0063] Three options are provided for determining the number of PTRS ports for each PUSCH repetition. These options are not mutually exclusive. Aspects of some of these options can be used in conjunction with other options.

[0064] A first option may include using a single-port PTRS port for PUSCH scheduled with repetitions having multiple beams / precoders. For example, even if the three conditions for using dual-port PTRS are met (e.g., the maximum number of UL PTRS ports may be configured to be more than one; the codebook subset is configured as non-coherent / partially coherent, and dual-panel transmission is to be used), the UE 104 will still only apply one PTRS port. The UE 104 may transmit PTRS via one antenna port, and that PTRS may be used for all PUSCH repetitions. In various embodiments, a single PTRS port transmission may be transmitted on different antennas / panels in different repetition sets.

[0065] A second option may include using the same number of PTRS ports for all PUSCH repetitions. For example, the initial number of PTRS ports for each repetition (or repetition set) may be determined based on a configuration set for the repetition or repetition set. The initial determination may be based on whether the configuration set (e.g., based on RRC signaling and an indicated precoder for the repetition (or repetition set)) satisfies the three conditions described above. For example, if in RRC, the maximum number of uplink PTRS ports for one repetition (or repetition set) is configured as 2; the codebook subset is configured as non-coherent or partially coherent; and the repetition (or repetition set) is to be transmitted over ports 1000 / 1002 and ports 1001 / 1003, the repetition (or repetition set) may be initially determined to have two PTRS ports. Otherwise, one PTRS port may be initially determined for the repetition (or repetition set).

[0066] In some embodiments, the repetitions (or repetition sets) transmitted via ports 1000 / 1002 and ports 1001 / 1003 may be transmitted via one beam defined at the UE layer, e.g., beamforming weights applied to two antenna panels to form one beam. Alternatively, the repetitions (or repetition sets) transmitted via ports 1000 / 1002 and ports 1001 / 1003 may be transmitted via two beams defined at the antenna panel layer.

[0067] Although initially determined, a number of PTRS ports may be selected to be used for all PUSCH repetitions. The selection of the number to be used for all PUSCH repetitions may be performed as described with reference to one of the subsequent sub-options.

[0068] Sub-option 2-1 may include determining the number of PTRS ports to be used based on the number of PTRS ports initially determined for a particular PUSCH repetition. The PUSCH repetition may be, for example, the first PUSCH repetition (or repetition set); however, in other embodiments, it may be another PUSCH repetition (or repetition set). Consider, for example, that it was initially determined that one PTRS port was to be used for repetition set 1 and two PTRS ports were to be used for repetition set 2. In sub-option 2-1, UE 104 may determine that one PTRS port is to be used for both repetition sets 1 and 2.

[0069] Sub-option 2-2 may include determining the number of PTRS ports to use for all PUSCH repetitions (or repetition sets) based on the minimum number of PTRS ports for all PUSCH repetitions (or repetition sets). Consider, for example, that it is initially determined that two PTRS ports are to be used for repetition set 1 and one PTRS port is to be used for repetition set 2. In sub-option 2-2, UE 104 may determine to use one PTRS port for both repetition sets 1 and 2.

[0070] Sub-option 2-3 may include determining the number of PTRS ports to use for all PUSCH repetitions (or repetition sets) based on the maximum number of PTRS ports for all PUSCH repetitions (or repetition sets). Consider, for example, an initial determination to use two PTRS ports for repetition set 1 and one PTRS port for repetition set 2. In sub-option 2-3, UE 104 may determine to use two PTRS ports for both repetition sets 1 and 2.

[0071] Sub-options 2-4 may include implementing a scheduling constraint where the base station 108 schedules the same number of PTRS ports for each PUSCH repetition. For example, the base station 108 may schedule PUSCH transmissions 124 as follows: initially, the same number of PTRS ports, e.g., one PTRS port or two PTRS ports, is determined for repetition sets 1 and 2. In this embodiment, if the repetition sets are scheduled in such a way that different numbers of PTRS ports are determined for different repetition sets, then the implementation may be considered erroneous.

[0072] In some embodiments, base station 108 may limit scheduling variations between repetition sets to ensure that the same number of PTRS ports is determined for different repetition sets. For example, if base station 108 schedules repetition set 1 in a manner that satisfies the three conditions for two PTRS ports, then the base station's scheduling for repetition set 2 must also satisfy the three conditions for two PTRS ports. It will be appreciated that some scheduling variations may still exist between the two repetition sets. For example, as long as the first of the second precoders is a non-coherent or partially coherent precoder (and therefore satisfies condition 2), the first repetition set may be scheduled using the first precoder and the second repetition set may be scheduled using the second precoder.

[0073] A third option for determining the number of PTRS ports to be used for each PUSCH repetition (or repetition set) may include determining the number of PTRS ports to be used for each PUSCH repetition (or repetition set) individually. For example, for each PUSCH repetition (or repetition set), it may be determined whether the RRC signaling and precoder meet three conditions. For example, it may be determined whether: in RRC, the maximum number of uplink PTRS ports is configured to be 2; the codebook subset is configured as non-coherent or partially coherent; and the PUSCH repetition (or repetition set) is to be transmitted over ports 1000 / 1002 and ports 1001 / 1003. If so, two PTRS ports may be applied to the PUSCH repetition (or repetition set). Otherwise, one PTRS port may be used for the repetition (or repetition set). It may be noted that the PUSCH repetition may indicate an actual or nominal PUSCH repetition.

[0074] Three options may be provided for determining PTRS to DMRS association for DG-PUSCH transmissions with repetitions. These options are not mutually exclusive. Aspects of some of these options may be used in conjunction with other options.

[0075] A first option may include determining PTRS to DMRS association for each PUSCH repetition (or repetition set, e.g., PUSCH repetitions with the same precoder / beam) based on an indicator provided by a single DCI. This may be performed according to at least two sub-options.

[0076] In sub-option 1-1, a single DCI field can be used to jointly configure the PTRS to DMRS association for each repetition (or repetition set). In some embodiments, the single DCI field can refer to a preconfigured table of values ​​corresponding to different repetitions (or repetition sets). Consider, for example, Table 4, which associates UL PTRS port 0 to the first DMRS scheduling port or the second DMRS scheduling port for the first and second PUSCH repetition sets. In this embodiment, a repetition set is defined as a repetition that shares a first SRI / TPMI and a repetition that shares a second SRI / TPMI.

[0077]

[0078] Table 4 - PTRS to DMRS association for UL PTRS port 0

[0079] For example, if the DCI field indicates a value of '1', the DMRS port for the first repetition set will be the second DMRS scheduling port (e.g., transmission layer 1), and the DMRS port for the second repetition set will be the first DMRS scheduling port (e.g., transmission layer 0). Therefore, PTRS port 0 will be associated with both the first DMRS scheduling port and the second DMRS scheduling port. Therefore, the PTRS transmitted from PTRS port 0 will use the same precoder as the DMRS transmitted with the first repetition set via transmission layer 0, and the DMRS transmitted with the second repetition set via transmission layer 1.

[0080] In some embodiments, the maximum number of layers used for each PUSCH repetition (or repetition set) may be limited to reduce overhead. For example, in some embodiments, up to two transmission layers may be allowed (e.g., two precoders / beams may be applied for all PUSCH repetitions). This may allow the use of a 2-bit PTRS to DMRS association field with reference to a PTRS-DMRS association table (such as Table 4) for a PTRS port indication.

[0081] In sub-options 1-2, multiple DCI fields may be used to configure PTRS-to-DMRS association for each repetition (or repetition set). For example, assuming that two repetition sets are to be transmitted, the first DCI field may indicate a first association value that references a PTRS-DMRS association table (such as Table 1) for the first repetition set; and the second DCI field may indicate a second association value that references a PTRS-DMRS association table for the second repetition set.

[0082] In a second option for determining PTRS to DMRS association for a DG-PUSCH with multiple precoders / beams, the PTRS-DMRS association may not be based on the DCI. For example, the association may not be indicated in the DCI, or if indicated, it may be ignored by the UE 104. This may be performed according to at least two sub-options.

[0083] In option 2-1, the PTRS-to-DMRS association may be based on a predefined value for PTRS-to-DMRS association. For example, a predefined association value may be assumed as a default PTRS-to-DMRS association to be applied. For example, the UE 104 may determine that the PTRS is always associated with the first DMRS port, e.g., with reference to any of Tables 1, 2, or 4, and that the PTRS-to-DMRS association value is 0.

[0084] In option 2-2, PTRS-to-DMRS association can be configured via higher-layer signaling (e.g., RRC or MAC CE). In this way, the association value can be updated based on the specific configuration scenario. However, the rate at which the association value is updated may be slower than the rate at which dynamic signaling via DCI is updated, as described above.

[0085] In options 2-3, PTRS to DMRS association can be based on a per-precoder port cycle, where the association is based on the number of DMRS ports and the number of repetitions within a repetition set. Specifically, according to some embodiments, the association can be determined by the number of associated DMRS ports (N) and the repetition index (k) between repetitions within a repetition set (e.g., repetitions that share the same precoder / beam). For example, the first repetition in a repetition set can have a k value of 0, the second repetition in a repetition set can have a value of 1, and so on. PTRS port 0 can then be associated with DMRS port k mod N.

[0086] Consider, for example, Figure 3 Signaling diagram 300. Similar to Figure 1 Signaling diagram 300 may include a PUSCH transmission 300 including a first repetition set 304 including PUSCH repetition #1 and PUSCH repetition #2. PUSCH transmission 300 may also include a second repetition set 308 including PUSCH repetition #3 and PUSCH repetition #4. First repetition set 304 may be transmitted via beam #1, and second repetition set 308 may be transmitted via beam #2.

[0087] Assuming that one PTRS port is enabled, the port cycling of option 2-3 may result in: on the first transmission layer, transmitting PUSCH repetition #1 (where PTRS port 0 is associated with DMRS port 0 (based on k=0 and N=2)); on the second transmission layer, transmitting PUSCH repetition #2 (where PTRS port 0 is associated with DMRS port 1 (based on k=1 and N=2)); on the first transmission layer, transmitting PUSCH repetition #3 (where PTRS port 0 is again associated with DMRS port 0 (based on k=0 and N=2)); and on the second transmission layer, transmitting PUSCH repetition #4 (where PTRS port 0 is associated with DMRS port 1 (based on k=1 and N=2)).

[0088] In a third option for determining PTRS to DMRS association for a DG-PUSCH whose repetitions have multiple precoders / beams, for the DG-PUSCH, the PTRS to DMRS association for PUSCH repetitions other than the first PUSCH repetition, or for PUSCH repetitions having a different precoder / beam than the first PUSCH repetition, may be indicated by a second-level DCI.

[0089] Figure 4 A signaling diagram 400 is shown with a second level indication of PTRS to DMRS association according to some embodiments. The signaling diagram includes a first level DCI 404 and a second level DCI 408. The first level DCI 404 may schedule a DG-PUSCH transmission 412. The DG-PUSCH transmission 412 may include a first repetition set 416 with PUSCH repetitions #1 and #2 and a second repetition set 420 with PUSCH repetitions #3 and #4.

[0090] The first-level DCI 404 may provide a dynamic grant for DG-PUSCH transmission 412. Additionally, the first-level DCI 404 may provide a PTRS to DMRS association for the first repetition set. In this embodiment, the association may indicate that PTRS port 0 is associated with DMRS port 0. Thus, the first repetition set 416 may be transmitted by the first transport layer. In some embodiments, the first-level DCI may also provide an indication of the second-level DCI 408 and may provide the location of the second-level DCI.

[0091] The second-level DCI 408 may provide an indication of the PTRS to DMRS association for repetition sets subsequent to the first repetition set. For example, the second-level DCI 408 may indicate that PTRS port 0 is associated with DMRS port 1 of the second repetition set 420. Therefore, the second repetition set 420 may be transmitted by the second transport layer.

[0092] In some embodiments, the first level DCI 404 may provide a dynamic grant for the DG-PUSCH 412, while the second level DCI 408 provides an indication of PTRS to DMRS association for all repetition sets.

[0093] In some embodiments, the bit width in the second-level DCI 408 can be adjusted based on the scheduling of the first-level DCI 404. The scheduling of the DG-PUSCH 412 can form a smaller subset of the values ​​of the PTRS-DMRS association table that are valid and need to be referenced. For example, if a port PTRS is used with only two transmission layers, only one bit may be needed to provide an indication of the PTRS to DMRS association. In some embodiments, the bit width of the PTRS-DMRS indication in the second-level DCI 408 can be determined by the number of PTRS ports M and the number of layers N. For example, the bit width can be log2(ceil(N / M))*M.

[0094] For CG-PUSCH with repetitions from multiple beams / precoders, the base station 108 can configure different PTRS to DMRS associations for each repetition (or repetition set) through RRC signaling. Two options for configuring port associations using RRC signaling are provided below. These options are not mutually exclusive. Aspects of one of these options can be used with the other.

[0095] In the first option, an RRC parameter can be introduced to configure the PTRS to DMRS association for PUSCH repetitions. This can be indicated jointly through a single RRC parameter or a PTRS to DMRS association list. For example, if CG-PUSCH is scheduled using two transport layers and one PTRS port, the RRC parameter can indicate whether the PTRS port is associated with the first DMRS scheduling port or the second DMRS scheduling port for each of multiple CG-PUSCH repetition sets.

[0096] In the second option, an RRC parameter may be introduced to enable PTRS port cycling. Once enabled, the UE 104 may use the same protocol described above with reference to options 2-3 and Figure 4 A similar method as described above.

[0097] In some embodiments, the RRC parameters for configuring port association may be incorporated into the RRC signaling used to provide a configuration grant for the CG-PUSCH. Additionally / alternatively, the RRC parameters may be provided when the configuration grant is updated.

[0098] Figure 5An operational flow / algorithm structure 500 according to some embodiments is shown. The operational flow / algorithm structure 500 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).

[0099] The operational flow / algorithm structure 500 may include, at 504, processing scheduling information to determine a schedule with repeated PUSCH transmissions. In some embodiments, the scheduling information may be dynamic grant scheduling information transmitted via DCI. In other embodiments, the scheduling information may be configured as grant scheduling information transmitted via RRC and optionally DCI.

[0100] PUSCH transmission repetitions can be divided into multiple repetition sets, which are scheduled for transmission on corresponding multiple transmit beams. The scheduling of repetition sets on corresponding transmit beams can be based on a common SRI or TPMI configuration for each repetition within the repetition set. A repetition set can include one or more repetitions. Repetition sets can include different numbers of repetitions.

[0101] The operational flow / algorithm structure 500 may further include determining a PTRS port number for transmitting the PTRS associated with the repetition, at 508. The PTRS port number may be determined to be the same or different for all repetition sets.

[0102] In one embodiment, an initial number of PTRS ports may be determined for each repetition set. The initial number may be determined based on whether a configuration set for a specific repetition set satisfies the three conditions described above (e.g., the maximum number of uplink PTRS ports is configured to be two; the codebook subset is configured to be non-coherent or partially coherent; and the repetition set is transmitted via ports 1000 / 1002 and ports 1001 / 1003). In some embodiments, one of the initial numbers may be used for all repetition sets. The initial number may be the number associated with the first repetition set, the maximum number among the initial numbers, or the minimum number among the initial numbers. In other embodiments, the initial number may be used to transmit the corresponding repetition set.

[0103] The operational flow / algorithm structure 500 may further include transmitting a PUSCH transmission with repetitions, at 512. The PUSCH transmission may be transmitted using a transmit beam as configured by a dynamic grant or a configured grant.

[0104] The operational flow / algorithm structure 500 may further include, at 516 , transmitting the PTRS using the PTRS port number determined at 508 .

[0105] Figure 6An 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).

[0106] The operational flow / algorithm structure 600 may include, at 604, receiving one or more DCIs to schedule a PUSCH transmission and indicate an association value. The PUSCH transmission in this embodiment may be a DG-PUSCH with multiple repetition sets. Each repetition set may include one or more repetitions of a shared SRI / TPMI.

[0107] One or more DCI fields may include an indication of the affinity value in one or more fields. For example, in a first embodiment, a single DCI field may be used to jointly configure the affinity for each repetition set. In another embodiment, multiple DCI fields may be used to individually configure the affinity for the respective multiple repetition sets.

[0108] In some embodiments, the one or more DCIs may include a first-level DCI including scheduling information and a second-level DCI including relevance information. In some embodiments, the first-level DCI may include relevance information for a first repetition set, while the second-level DCI may include relevance information for a second repetition set. In other embodiments, the second-level DCI may include relevance information for all repetition sets.

[0109] The operational flow / algorithm structure 600 may also include determining PTRS to DMRS associations for each repetition set at 608. Specifically, one or more PTRS ports may be associated with one or more DMRS scheduling ports. These associations may be determined by using the association information to reference one or more PTRS-DMRS storage tables, such as, for example, Table 1, Table 2, or Table 4 as described herein.

[0110] The operational flow / algorithm structure 600 may also include, based on the association, transmitting a PTRS and transmitting a PUSCH transmission at 612. The PTRS may be transmitted using the same precoder used for the associated DMRS, which is transmitted using the corresponding repetition set.

[0111] 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 1000) or a component thereof (eg, baseband processor 1004A).

[0112] The operational flow / algorithm structure 700 may include receiving a DCI to schedule a PUSCH transmission at 704. In this embodiment, the PUSCH transmission may be a DG-PUSCH scheduled by a DCI similar to that described above.

[0113] The operational flow / algorithm structure 700 may also include, at 708, determining a PTRS to DMRS association for a repetition set based on configuration information. In this embodiment, the configuration information may be predefined or received from higher-layer signaling. As used herein, higher-layer signaling may refer to signaling above the physical layer. For example, higher-layer signaling may include RRC signaling or MAC control signaling (e.g., MAC CE).

[0114] If the DCI includes relevance information, it may be discarded or otherwise ignored by the UE.

[0115] In some embodiments, the configuration information may indicate that the PTRS to DMRS association is based on a predefined value. This predefined value may refer to a PTRS-DMRS table, such as the table described above with reference to Table 1, Table 2, or Table 3. The predetermined value may be a static value that is used as a default value when no other association information is configured, such as through higher layer signaling.

[0116] In some embodiments, the configuration information may indicate that the PTRS to DMRS association is to be cycled based on the PTRS port. For example, if a DG-PUSCH transmission is associated with N DMRS ports, where N is an integer, the PTRS to DMRS association may be determined for each repetition of a repetition set based on a repetition index (k) between one or more repetitions. For example, a PTRS port may be associated with DMRS port k mod N. In this embodiment, k = 0 for the first repetition of a particular repetition set and is incremented by one for subsequent repetitions of the repetition set. When determining the association for each repetition in a subsequent repetition set, the value k may be reset to 0.

[0117] The operational flow / algorithm structure 700 may also include transmitting a PTRS and a PUSCH transmission at 712. As discussed above, the PTRS may be transmitted using the same precoder as its associated DMRS.

[0118] 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 (e.g., baseband processor 1104A).

[0119] The operational flow / algorithm structure 800 may include transmitting RRC signaling for CG-PUSCH at 804. The CG-PUSCH may be a type 1 configuration grant (fully configured by RRC signaling) or a type 2 configuration grant (configured by RRC signaling and subsequently triggered by DCI transmission).

[0120] In some embodiments, in addition to configuring the grant information, RRC signaling may also include association information to configure different PTRS to DMRS associations for each repetition set. In some embodiments, the association information may be included in one or more RRC parameters or association lists. In some embodiments, the association information may enable, trigger, or reconfigure PTRS port cycling for use by the receiving UE.

[0121] The operational flow / algorithm structure 800 may further include receiving a CG-PUSCH transmission and a PTRS at 808. The CG-PUSCH transmission and the PTRS may be transmitted by the UE based on the scheduling and association information provided by the RRC signaling at 804.

[0122] The operational flow / algorithm structure 800 may also include processing the CG-PUSCH based on the PTRS at 812. Specifically, the base station may determine a phase shift based on the PTRS and may use the determined phase shift to process the DMRS associated with the PTRS. In this manner, the base station may then demodulate the PUSCH repetitions based on the recovered DMRS.

[0123] Figure 9 Beamforming circuitry 900 is shown according to some embodiments. Beamforming circuitry 900 may include a first antenna panel, panel 1 904, and a second antenna panel, panel 2 908. Each antenna panel may include multiple antenna elements. Other embodiments may include other numbers of antenna panels.

[0124] The digital beam forming (BF) component 928 can receive data from, for example, a baseband processor such as, for example Figure 11 The baseband processor 1104A of the RF module 1104 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.

[0125] Each RF chain 920 / 924 may include a digital-to-analog converter to convert the BB signal into the analog domain; a mixer to mix the baseband signal into an RF signal; and a power amplifier to amplify the RF signal for transmission.

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

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

[0128] 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 dynamically phased array capable of steering a beam in a desired direction.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0152] 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 controller circuitry 1112 can include multiple controllers for providing connectivity to other networks using the same or different protocols.

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

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

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

[0156] Example

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

[0158] Embodiment 1 may include a method of operating a UE, the method comprising: processing scheduling information to determine a schedule for physical uplink shared channel (PUSCH) transmissions having multiple repetitions, wherein the multiple repetitions include at least two repetition sets to be transmitted using at least two transmit beams, respectively; determining a certain number of phase tracking reference signal (PTRS) ports for transmitting PTRS associated with each of the at least two repetition sets; transmitting the PUSCH transmissions having the multiple repetitions using at least two transmit beams; and transmitting the PTRS through the number of PTRS ports.

[0159] Embodiment 2 may include the method according to embodiment 1 or some other embodiments herein, further comprising: determining that multiple PTRS ports are configured; and determining that one PTRS port will be used to transmit the PTRS associated with each of the first repetition set and the second repetition set.

[0160] Embodiment 3 may include a method according to embodiment 1 or some other embodiment herein, wherein a first number of PTRS ports is initially determined for a first repetition set among at least two repetition sets, and a second number of PTRS ports is initially determined for a second repetition set among at least two repetition sets, and determining the number of PTRS ports includes: determining that the first number of PTRS ports will be used to transmit PTRS associated with multiple repetitions.

[0161] Embodiment 4 may include a method according to embodiment 3 or some other embodiment herein, wherein an initial number of PTRS ports is determined for each of at least two repetition sets, and the method further comprises: determining that the first number of PTRS ports will be used to transmit PTRS associated with multiple repetitions based on the first number being the minimum value of the initial number of PTRS ports; or determining that the first number of PTRS ports will be used to transmit PTRS associated with multiple repetitions based on the first number being the maximum value of the initial number of PTRS ports.

[0162] Embodiment 5 may include the method according to embodiment 1 or some other embodiment herein, further comprising: determining an indicated maximum number of PTRS ports from radio resource control (RRC) signaling for a first repetition set among at least two repetition sets; determining a codebook subset for the first repetition set; determining one or more antenna ports for transmitting the first repetition set; and determining a first number of PTRS ports for transmitting the PTRS associated with the first repetition set based on the indicated maximum number, the codebook subset, and the one or more antenna ports.

[0163] Embodiment 6 may include a method according to embodiment 5 or some other embodiment herein, further comprising: if the indicated maximum number is one, the codebook subset is not configured as non-coherent or partially coherent, or one or more antenna ports do not include port 1000 or 1002 and port 1001 or 1003, then determining that the first number of PTRS ports is one port.

[0164] Embodiment 7 may include a method according to embodiment 5 or some other embodiment herein, further comprising: if the indicated maximum number is two, the codebook subset is configured as non-coherent or partially coherent, and one or more antenna ports include port 1000 or 1002 and port 1001 or 1003, then determining that the first number of PTRS ports is two ports.

[0165] Embodiment 8 may include a method of operating a UE, the method comprising: storing a phase tracking reference signal (PTRS)-demodulation reference signal (DMRS) association table; receiving one or more downlink control information (DCI) to: schedule a physical uplink shared channel (PUSCH) transmission having a first repetition set and a second repetition set, the first repetition set including one or more repetitions of a shared first scheduling request indicator (SRI) or a transmitted precoding matrix indicator (TPMI), and the second repetition set including one or more repetitions of a shared second SRI / TPMI; and indicating one or more association values ​​in a single field or multiple fields; determining a PTRS to DMRS association for the first repetition set or the second repetition set based on the one or more association values ​​and the PTRS-DMRS association table; transmitting the PTRS based on the PTRS to DMRS association; and transmitting the first repetition set and the second repetition set.

[0166] Embodiment 9 may include a method according to embodiment 8 or some other embodiment herein, wherein one or more DCIs include a single two-bit field to indicate one or more association values, and determining the PTRS to DMRS association includes: determining that the PTRS port is associated with a first DMRS scheduling port or a second DMRS scheduling port, wherein the DMRS port for the first repetition set is the first DMRS scheduling port or the second DMRS scheduling port, and the DMRS port for the second repetition set is the first DMRS scheduling port or the second DMRS scheduling port.

[0167] Embodiment 10 may include a method according to embodiment 8 or some other embodiment herein, wherein one or more DCIs include a first field for indicating a first association value among one or more association values ​​and a second field for indicating a second association value among one or more association values, and determining the PTRS to DMRS association includes: based on the first association value, determining a PTRS port associated with the DMRS port for the first repetition set; and based on the second association value, determining a PTRS port associated with the DMRS port for the second repetition set.

[0168] Embodiment 11 may include a method according to embodiment 10 or some other embodiment herein, wherein the PTRS port associated with the DMRS port for the first repetition set and the PTRS port associated with the DMRS port for the second repetition set are different PTRS ports.

[0169] Embodiment 12 may include a method according to embodiment 8 or some other embodiment herein, wherein the method further comprises: determining, based on the PTRS to DMRS association, that the first PTRS port is associated with the first DMRS port for the first repetition set; and transmitting the PTRS via the first PTRS port and transmitting the DMRS via the first DMRS port using a common precoder.

[0170] Embodiment 13 may include a method according to embodiment 8 or some other embodiment herein, wherein one or more association values ​​include a first association value and a second association value, one or more DCIs include a first-level DCI for scheduling PUSCH transmission and a second-level DCI for including the second association value, and the method further includes: determining the PTRS to DMRS association for the first repetition set based on the first association value and the PTRS-DMRS association table; and determining the PTRS to DMRS association for the second repetition set based on the second association value and the PTRS-DMRS association table.

[0171] Embodiment 14 may include a method according to embodiment 13 or some other embodiment herein, wherein the second level DCI comprises a bit width of log2(ceil(N / M)*M, where M is the number of PTRS ports and N is the number of transport layers.

[0172] Embodiment 15 may include a method as in embodiment 13 or some other embodiment herein, wherein the first relevance value is in a first level DCI or a second level DCI.

[0173] Embodiment 16 includes a method comprising: receiving downlink control information (DCI) to schedule a physical uplink shared channel (PUSCH) transmission having multiple repetition sets to be transmitted using at least two transmit beams; determining a PTRS to DMRS association for each of the multiple repetition sets based on configuration information predefined by or received from radio resource control (RRC) or medium access control (MAC) control signaling; transmitting a PTRS based on the PTRS to DMRS association; and transmitting a PUSCH transmission having multiple repetitions.

[0174] Embodiment 17 may include a method as in embodiment 16 or some other embodiment herein, wherein the configuration information comprises a medium access control (MAC) control element (CE).

[0175] Embodiment 18 may include a method according to embodiment 16 or some other embodiment herein, wherein the PUSCH transmission is associated with N DMRS ports, where N is an integer, and determining the PTRS to DMRS association includes: for each repetition of one or more repetitions of a first repetition set among a plurality of repetition sets, based on a repetition index (k) between the one or more repetitions, determining that the PTRS port is associated with the DMRS port k mod N, where k = 0 for the first repetition of the one or more repetitions and is incremented by one for subsequent repetitions in the one or more repetitions.

[0176] Embodiment 19 may include a method of operating a base station, the method comprising: transmitting radio resource control (RRC) signaling for a configuration authorization-physical uplink shared channel (PUSCH) transmission with multiple repetition sets to a user equipment, wherein the RRC signaling includes one or more parameters to configure corresponding multiple PTRS to DMRS associations for the multiple repetition sets; receiving a CG-PUSCH transmission; receiving a PTRS associated with the CG-PUSCH transmission; and processing the CG-PUSCH transmission based on receiving the PTRS.

[0177] Embodiment 20 may include a method according to embodiment 19 or some other embodiment herein, wherein the one or more parameters include a single RRC parameter to jointly indicate each repetition set having PTRS to DMRS association; or include multiple RRC parameters to indicate separately.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0194] 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, cause a processing circuit to: processing the scheduling information to determine a schedule for physical uplink shared channel (PUSCH) transmissions having a plurality of repetitions, wherein the plurality of repetitions includes at least two repetition sets to be transmitted using at least two transmit beams, respectively; determining, based on radio resource control (RRC) signaling, an indicated maximum number of phase tracking reference signal (PTRS) ports for all the plurality of repetitions; determining, based on the indicated maximum number of PTRS ports, a number of PTRS ports for transmitting PTRS associated with each of the at least two repetition sets; generating the PUSCH transmission having the plurality of repetitions transmitted using the at least two transmit beams; and The PTRS is generated for transmission through the number of PTRS ports.

2. The one or more computer-readable media of claim 1 , wherein to determine the number of PTRS ports, the instructions, when executed, further cause the processing circuit to: Verify that multiple PTRS ports are configured; and A PTRS port is determined to be used for transmitting the PTRS associated with each of the at least two repetition sets.

3. The one or more computer-readable media of claim 1 , wherein a first number of PTRS ports is initially determined for a first repetition set among the at least two repetition sets, and a second number of PTRS ports is initially determined for a second repetition set among the at least two repetition sets, and wherein to determine the number of PTRS ports, the instructions are further to cause the processing circuitry to: It is determined that the first number of PTRS ports are to be used for transmitting PTRS associated with the plurality of repetitions.

4. The one or more computer-readable media of claim 3 , wherein for each of the at least two repetition sets, an initial number of PTRS ports is determined, and the instructions, when executed, further cause the processing circuit to: determining that the first number of PTRS ports is to be used for transmitting PTRS associated with the plurality of repetitions based on the first number being a minimum of the initial number of PTRS ports; or Based on the first number being a maximum value of the initial number of PTRS ports, it is determined that the first number of PTRS ports is to be used for transmitting PTRS associated with the plurality of repetitions.

5. The one or more computer-readable media of claim 1 , wherein the instructions, when executed, further cause the processing circuit to: determining a codebook subset for a first repetition set among the at least two repetition sets; determining one or more antenna ports for transmitting the first repetition set; as well as A first number of PTRS ports is determined based on the indicated maximum number, the codebook subset, and the one or more antenna ports to transmit the PTRS associated with the first repetition set.

6. One or more computer-readable media according to claim 5, wherein the instructions, when executed, further cause the processing circuit to: determine that the first number of PTRS ports is one port if the indicated maximum number is one, the codebook subset is not configured as non-coherent or partially coherent, or the one or more antenna ports do not include port 1000 or 1002 and port 1001 or 1003.

7. The one or more computer-readable media of claim 5, wherein the instructions, when executed, further cause the processing circuit to: determine that the first number of PTRS ports is two ports if the indicated maximum number is two, the codebook subset is configured as non-coherent or partially coherent, and the one or more antenna ports include port 1000 or 1002 and port 1001 or 1003.

8. A method for communication, the method comprising: processing the scheduling information to determine a schedule for physical uplink shared channel (PUSCH) transmissions having a plurality of repetitions, wherein the plurality of repetitions includes at least two repetition sets to be transmitted using at least two transmit beams, respectively; determining, based on radio resource control (RRC) signaling, an indicated maximum number of phase tracking reference signal (PTRS) ports for all the plurality of repetitions; determining a number of PTRS ports for transmitting the PTRS associated with each of the at least two repetition sets; generating the PUSCH transmission having the plurality of repetitions transmitted using the at least two transmit beams; and The PTRS is generated for transmission through the number of PTRS ports.

9. The method of claim 8, wherein determining the number of PTRS ports comprises: Make sure multiple PTRS ports are configured; as well as A PTRS port is determined to be used for transmitting the PTRS associated with each of the at least two repetition sets.

10. The method of claim 8, wherein a first number of PTRS ports is initially determined for a first repetition set among the at least two repetition sets, a second number of PTRS ports is initially determined for a second repetition set among the at least two repetition sets, and determining the number of PTRS ports comprises: It is determined that the first number of PTRS ports are to be used for transmitting PTRS associated with the plurality of repetitions.

11. The method of claim 10, wherein for each of the at least two repetition sets, an initial number of PTRS ports is determined, and the method further comprises: determining that the first number of PTRS ports is to be used for transmitting PTRS associated with the plurality of repetitions based on the first number being a minimum of the initial number of PTRS ports; or Based on the first number being a maximum value of the initial number of PTRS ports, it is determined that the first number of PTRS ports is to be used for transmitting PTRS associated with the plurality of repetitions.

12. The method according to claim 8, further comprising: determining a codebook subset for a first repetition set among the at least two repetition sets; determining one or more antenna ports for transmitting the first repetition set; as well as A first number of PTRS ports is determined based on the indicated maximum number, the codebook subset, and the one or more antenna ports to transmit the PTRS associated with the first repetition set.

13. The method according to claim 12, further comprising: If the indicated maximum number is one, the codebook subset is not configured as non-coherent or partially coherent, or the one or more antenna ports do not include port 1000 or 1002 and port 1001 or 1003, it is determined that the first number of PTRS ports is one port.

14. The method according to claim 12, further comprising: If the indicated maximum number is two, the codebook subset is configured as non-coherent or partially coherent, and the one or more antenna ports include port 1000 or 1002 and port 1001 or 1003, then the first number of PTRS ports is determined to be two ports.

15. A processing circuit, the processing circuit being configured to: processing the scheduling information to determine a schedule for physical uplink shared channel (PUSCH) transmissions having a plurality of repetitions, wherein the plurality of repetitions includes at least two repetition sets to be transmitted using at least two transmit beams, respectively; determining, based on radio resource control (RRC) signaling, an indicated maximum number of phase tracking reference signal (PTRS) ports for all the plurality of repetitions; determining a number of PTRS ports for transmitting the PTRS associated with each of the at least two repetition sets; generating the PUSCH transmission having the plurality of repetitions transmitted using the at least two transmit beams; and The PTRS is generated for transmission through the number of PTRS ports.

16. The processing circuit of claim 15, wherein to determine the number of PTRS ports, the processing circuit is configured to: Verify that multiple PTRS ports are configured; and A PTRS port is determined to be used for transmitting the PTRS associated with each of the at least two repetition sets.

17. The processing circuit of claim 15 , wherein a first number of PTRS ports is initially determined for a first repetition set among the at least two repetition sets, and a second number of PTRS ports is initially determined for a second repetition set among the at least two repetition sets, and to determine the number of PTRS ports, the processing circuit is configured to: It is determined that the first number of PTRS ports are to be used for transmitting PTRS associated with the plurality of repetitions.

18. The processing circuit of claim 17, wherein for each of the at least two repetition sets, an initial number of PTRS ports is determined, and the processing circuit is further configured to: determining that the first number of PTRS ports is to be used for transmitting PTRS associated with the plurality of repetitions based on the first number being a minimum of the initial number of PTRS ports; or Based on the first number being a maximum value of the initial number of PTRS ports, it is determined that the first number of PTRS ports is to be used for transmitting PTRS associated with the plurality of repetitions.

19. The processing circuit according to claim 15, wherein the processing circuit is further configured to: determining a codebook subset for a first repetition set among the at least two repetition sets; determining one or more antenna ports for transmitting the first repetition set; and A first number of PTRS ports is determined based on the indicated maximum number, the codebook subset, and the one or more antenna ports to transmit the PTRS associated with the first repetition set.

20. The processing circuit of claim 19, wherein the processing circuit is further configured to: determine that the first number of PTRS ports is one port if the indicated maximum number is one, the codebook subset is not configured as non-coherent or partially coherent, or the one or more antenna ports do not include port 1000 or 1002 and port 1001 or 1003.

21. The processing circuit of claim 19, wherein the processing circuit is further configured to: determine that the first number of PTRS ports is two ports if the indicated maximum number is two, the codebook subset is configured as non-coherent or partially coherent, and the one or more antenna ports include port 1000 or 1002 and port 1001 or 1003.

Images