Method and apparatus for PTRS transmission in simultaneous multi-panel transmission

Abstract

Aspects of the present disclosure relate to methods and apparatus for phase tracking reference signal (PTRS) transmission in simultaneous multi-panel transmission. The apparatus comprises a user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: receive an indication for an uplink transmission, the uplink transmission comprising at least one physical uplink shared channel (PUSCH) transmission associated with a different sounding reference signal (SRS) resource set at the same time; and determining a parameter of a PTRS transmission for each of the at least one PUSCH transmission.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly to methods and apparatus for Phase Tracking Reference Signal (PTRS) transmission in simultaneous multi-panel transmissions. Background Art

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which may support wireless communication with one or more user communication devices, which may be referred to as user equipment (UE) or other appropriate terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other appropriate radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0003] The following abbreviations and acronyms are defined herein, at least some of which are referred to in this specification:

[0004] 3rd Generation Partnership Project (3GPP), New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Orthogonal Frequency Division Multiplexing (OFDM), Downlink (DL), Uplink (UL), User Equipment (UE), Network Equipment (NE), Receiver or Receiver (RX or Rx), Transmitter or Transmitter (TX or Tx), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Bandwidth Part (BWP), Configuration Grant (CG), Device-to-Device (D2D), Downlink Control Information (DCI), Demodulation Reference Signal (DMRS or DM-RS), Frequency Division Multiple Access (FDMA), Internet of Things (IoT), Machine Type Communication (MTC), Non-Access Stratum (NAS), Protocol Data Unit (PDU), Phase Shift Keying (PSK), Quadrature Amplitude Modulation (QAM), Radio Access Network (RAN), Resource Element (RE), Radio Resource Control (RRC) C), Reference Signal (RS), Single Frequency Network (SFN), Sounding Reference Signal (SRS), Vehicle-to-Everything (V2X), Amplitude Modulation (AM), Access and Mobility Management Function (AMF), Code Division Multiple Access (CDMA), Core Network (CN), Evolved Packet Core (EPC), Frequency Range 1 (FR1), Frequency Range 2 (FR2), Low Noise Amplifier (LNA), SRS Resource Indicator (SRI), Transmission Configuration Indication (TCI), Time Division Multiple Access (TDMA), Technical Specification (TS), User Plane Function (UPF), Vehicle-to-Vehicle (V2V), 5G Core Network (5GC), Multiple Downlink Control Information (M-DCI), Single Downlink Control Information (S-DCI), Dynamic Grant (DG), Frequency Modulation (FM), Spatial Division Multiplexing (SDM), Synchronous Transmission across Multiple Panels (STxMP), Transmit Precoding Matrix Indicator (TPMI), Demodulation Reference Signal (DMRS or DM-RS), Phase Tracking Reference Signal (PTRS or PT-RS). Summary of the Invention

[0005] The word "a" or "an" preceding an element is not limiting and is understood to mean "at least one" of those elements or "one or more" of those elements. The terms "one," "at least one," "one or more," and "at least one of one or more" are interchangeable. As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of" or "one or two of") indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be understood as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be understood in the same manner as the phrase "based at least in part on." Furthermore, as used herein, including in the claims, a "set" can include one or more elements.

[0006] Some implementations of the methods and apparatus described herein may include a user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the UE to: receive an indication for an uplink transmission, the uplink transmission comprising at least one physical uplink shared channel (PUSCH) transmission to be sent simultaneously and associated with different sounding reference signal (SRS) resource sets; and determine parameters for a phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmission.

[0007] Some implementations of the methods and apparatus described herein may include a processor for wireless communications, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: receive an indication for an uplink transmission, the uplink transmission comprising at least one physical uplink shared channel (PUSCH) transmission associated with different sounding reference signal (SRS) resource sets to be sent simultaneously; and determine parameters for a phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmission.

[0008] Some implementations of the methods and apparatus described herein can include a method performed by a user equipment (UE), the method comprising: receiving an indication for an uplink transmission, the uplink transmission comprising at least one physical uplink shared channel (PUSCH) transmission associated with different sets of sounding reference signal (SRS) resources to be transmitted simultaneously; and determining parameters for phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmission.

[0009] In some implementations of the methods and apparatus described herein, the indication is that a higher layer parameter multipanelScheme is configured and set to “SDMscheme”; the uplink transmission is one PUSCH transmission, where different layers of the PUSCH transmission are associated with different sets of SRS resources; and the parameters include a PUSCH-to-PTRS power ratio per RE per PTRS port .

[0010] In some implementations of the methods and apparatus described herein, the power ratio for a PTRS port x is determined based on a number of PUSCH layers that are coherently precoded with a PUSCH layer associated with the PTRS port x in a same set of SRS resources as the PTRS port x , and a total number of scheduled PTRS ports Qp for the PUSCH transmission associated with different sets of SRS resources.

[0011] In some implementations of the methods and apparatus described herein, the power ratio is .

[0012] In some implementations of the methods and apparatus described herein, for ptrs-Power configured as ‘00’, if a number of PUSCH layers associated to a same set of SRS resources as a PTRS port is one, a power ratio for the PTRS port is .

[0013] In some implementations of the methods and apparatus described herein, for ptrs-Power configured as ‘00’, if a number of PUSCH layers associated to a same set of SRS resources as a PTRS port is two, for full-coherent codebook-based PUSCH, a power ratio for the PTRS port is .

[0014] In some implementations of the methods and apparatus described herein, for ptrs-Power configured as '00', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is two, then for partially coherent and non-coherent codebook-based PUSCH and for non-codebook-based PUSCH, the power ratio of the PTRS port is for .

[0015] In some implementations of the methods and apparatus described herein, for ptrs-Power configured as '01', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is one, the power ratio of the PTRS port is is 3 dB.

[0016] In some implementations of the methods and apparatus described herein, for ptrs-Power configured as '01', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is two, the power ratio of the PTRS port is is 6 dB.

[0017] In some implementations of the methods and apparatus described herein, the indication is that: a higher layer parameter enableSTx2PofmDCI is configured; the uplink transmission is multiple PUSCH transmissions associated with different SRS resource sets; and the parameter includes a maximum number of PTRS ports for each of the multiple PUSCH transmissions.

[0018] In some implementations of the methods and apparatus described herein, a first parameter is received for configuring a maximum number of PTRS ports for non-overlapping PUSCH transmissions associated with different SRS resource sets, wherein the value of the first parameter is one or two.

[0019] In some implementations of the methods and apparatus described herein, a second parameter is received for configuring a maximum number of PTRS ports for overlapping PUSCH transmissions associated with different SRS resource sets, wherein the value of the second parameter is one.

[0020] In some implementations of the methods and apparatus described herein, the actual number of PTRS ports is determined for each PUSCH transmission according to a first parameter or a second parameter based on whether PUSCH transmissions associated with different SRS resource sets overlap.

[0021] In some implementations of the methods and apparatus described herein, a third parameter for configuring a maximum number of PTRS ports is received, and a value of the third parameter is one or two.

[0022] In some implementations of the methods and apparatus described herein, if the maximum number of PTRS ports is two and PUSCH transmissions associated with different SRS resource sets overlap in the time domain, the actual number of PTRS ports per PUSCH transmission is determined to be one.

[0023] In some implementations of the methods and apparatus described herein, if the maximum number of PTRS ports is two, and PUSCH transmissions associated with different SRS resource sets overlap in the time domain, only PTRS port 0 of each PUSCH transmission is sent.

[0024] In some implementations of the methods and apparatus described herein, it is undesirable that the indicated precoder or SRS resources result in more than one PTRS port in the event that different PUSCH transmissions associated with different SRS resource sets overlap.

[0025] Some implementations of the methods and apparatus described herein may include a base station for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory and configured to cause the base station to: send an indication for an uplink transmission, the uplink transmission comprising at least one physical uplink shared channel (PUSCH) transmission to be sent simultaneously and associated with different sounding reference signal (SRS) resource sets; and determine parameters for a received phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmission.

[0026] Some implementations of the methods and apparatus described herein may include a processor for wireless communications, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: send an indication for an uplink transmission, the uplink transmission comprising at least one physical uplink shared channel (PUSCH) transmission to be sent simultaneously and associated with different sounding reference signal (SRS) resource sets; and determine parameters of a received phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmission.

[0027] Some implementations of the methods and apparatus described herein may include a method of wireless communication performed by a base station, the method comprising: sending an indication for uplink transmissions comprising at least one physical uplink shared channel (PUSCH) transmission associated with different sounding reference signal (SRS) resource sets to be sent simultaneously; and determining parameters of a received phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmissions.

[0028] In some implementations of the methods and apparatus described herein, the indication is that: the higher layer parameter multipanelScheme is configured and set to "SDMscheme"; the uplink transmission is a PUSCH transmission, wherein different layers of the PUSCH transmission are associated with different SRS resource sets; and the parameter includes a PUSCH to PTRS power ratio per layer per RE for a PTRS port .

[0029] In some implementations of the methods and apparatus described herein, the power ratio of the PTRS port x is is the number of PUSCH layers that are precoded with respect to the PUSCH layers associated with PTRS port x in the same SRS resource set as PTRS port x. , and the total number Qp of scheduled PTRS ports for PUSCH transmission associated with different SRS resource sets.

[0030] In some implementations of the methods and apparatus described herein, the power ratio for .

[0031] In some implementations of the methods and apparatus described herein, for ptrs-Power configured as '00', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is one, the power ratio of the PTRS port is for .

[0032] In some implementations of the methods and apparatus described herein, for ptrs-Power configured as '00', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is two, then for fully coherent codebook-based PUSCH, the power ratio of the PTRS port is for .

[0033] In some implementations of the methods and apparatus described herein, for ptrs-Power configured as '00', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is two, then for partially coherent and non-coherent codebook-based PUSCH and for non-codebook-based PUSCH, the power ratio of the PTRS port is for .

[0034] In some implementations of the methods and apparatus described herein, for ptrs-Power configured as '01', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is one, the power ratio of the PTRS port is is 3 dB.

[0035] In some implementations of the methods and apparatus described herein, for ptrs-Power configured as '01', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is two, the power ratio of the PTRS port is is 6 dB.

[0036] In some implementations of the methods and apparatus described herein, the indication is that: a higher layer parameter enableSTx2PofmDCI is configured; the uplink transmission is multiple PUSCH transmissions associated with different SRS resource sets; and the parameter includes a maximum number of PTRS ports for each of the multiple PUSCH transmissions.

[0037] In some implementations of the methods and apparatus described herein, a first parameter is sent for configuring a maximum number of PTRS ports for non-overlapping PUSCH transmissions associated with different SRS resource sets, wherein the value of the first parameter is one or two.

[0038] In some implementations of the methods and apparatus described herein, a second parameter is sent for configuring a maximum number of PTRS ports for overlapping PUSCH transmissions associated with different SRS resource sets, wherein the value of the second parameter is one.

[0039] In some implementations of the methods and apparatus described herein, the actual number of PTRS ports is determined for each PUSCH transmission according to a first parameter or a second parameter based on whether PUSCH transmissions associated with different SRS resource sets overlap.

[0040] In some implementations of the methods and apparatus described herein, a third parameter for configuring a maximum number of PTRS ports is sent, and a value of the third parameter is one or two.

[0041] In some implementations of the methods and apparatus described herein, if the maximum number of PTRS ports is two and PUSCH transmissions associated with different SRS resource sets overlap in the time domain, the actual number of PTRS ports per PUSCH transmission is determined to be one.

[0042] In some implementations of the methods and apparatus described herein, if the maximum number of PTRS ports is two, and PUSCH transmissions associated with different SRS resource sets overlap in the time domain, only PTRS port 0 of each PUSCH transmission is received.

[0043] In some implementations of the methods and apparatus described herein, in the case where different PUSCH transmissions associated with different SRS resource sets overlap, the base station only indicates that the precoder or SRS resources result in one PTRS port. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 An example of a wireless communication system according to aspects of the present disclosure is shown.

[0045] Figure 2 An example of a user equipment (UE) 200 is shown in accordance with aspects of the present disclosure.

[0046] Figure 3 An example of a processor 300 according to aspects of the present disclosure is shown.

[0047] Figure 4 An example of a network equipment (NE) 400 according to aspects of the present disclosure is shown.

[0048] Figure 5 An example of power boosting of a PTRS port for PUSCH transmission using an SDM scheme when the maximum number of PTRS ports is configured to be one according to aspects of the present disclosure is shown.

[0049] Figure 6 An example of power boosting of PTRS ports for PUSCH transmission utilizing an SDM scheme when the maximum number of PTRS ports is configured as two according to aspects of the present disclosure is shown.

[0050] Figure 7 A flow chart of a method performed by a UE according to aspects of the present disclosure is shown.

[0051] Figure 8 A flow chart illustrating a method performed by a NE according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0052] Aspects of the disclosure are described in the context of a wireless communication system.

[0053] Figure 1An example of a wireless communication system 100 is shown in accordance with aspects of the present disclosure. The wireless communication system 100 can include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 can support various radio access technologies. In some implementations, the wireless communication system 100 can be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 can be a New Radio (NR) network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G-Ultra Wideband (5G-UWB) network. In other implementations, the wireless communication system 100 can be a combination of 4G networks and 5G networks, or other suitable radio access technologies, including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 can support a post-5G radio access technology, such as 6G. In addition, the wireless communication system 100 can support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0054] The one or more NEs 102 can be dispersed throughout the geographic area to form the wireless communication system 100. One or more of the NEs 102 described herein can be or include or can be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terminology. The NEs 102 and the UEs 104 can communicate via communication links, which can be wireless or wired connections. For example, the NEs 102 and the UEs 104 can perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0055] The NEs 102 can provide geographic coverage to geographic coverage areas for which the NEs 102 can provide service to one or more UEs 104 within the geographic coverage areas. For example, the NEs 102 and the UEs 104 can support wireless communication of signals related to service (e.g., voice, video, packet data, messaging, broadcast, etc.) in accordance with one or more radio access technologies. In some implementations, the NEs 102 can be mobile, such as satellites associated with non-terrestrial networks (NTNs). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, although different geographic coverage areas can be associated with different NEs 102.

[0056] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable terminology. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples.

[0057] A UE 104 may support wireless communication directly with another UE 104 via a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 via a PC5 interface.

[0058] An NE 102 may support communication with a CN 106, with another NE 102, or both. For example, an NE 102 may interface with another NE 102 or a CN 106 via one or more backhaul links (e.g., S1, N2, N3, or a network interface). In some implementations, the NEs 102 may communicate directly with one another. In other implementations, the NEs 102 may communicate with one another or indirectly (e.g., via the CN 106). In some implementations, one or more NEs 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0059] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core network (EPC) or a 5G core network (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)) and user plane entities that route packets or interconnect to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearer, signaling bearer, etc.) of one or more UEs 104 served by one or more NEs 102 associated with the CN 106.

[0060] The CN 106 can communicate with a packet data network via one or more backhaul links (e.g., via S1, N2, N3, or other network interfaces). The packet data network can include an application server. In some implementations, one or more UEs 104 can communicate with the application server. The UE 104 can establish a session (e.g., a protocol data unit (PDU) session, etc.) with the CN 106 via the NE 102. The CN 106 can use the established session (e.g., an established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server. A PDU session can be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0061] In the wireless communication system 100, the NE 102 and the UE 104 may use resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NE 102 and the UE 104 may support different resource structures. For example, the NE 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the NE 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the NE 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The NE 102 and the UE 104 may support various frame structures based on one or more parameter sets.

[0062] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first parameter set (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second parameter set (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third parameter set (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth parameter set (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0063] Time intervals for resources (e.g., communication resources) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, e.g., 10 milliseconds (ms). In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, e.g., 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0064] Additionally or alternatively, the time intervals of resources (e.g., communication resources) may be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, and μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and sixteen time slots per subframe, respectively. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for the normal and extended cyclic prefixes may depend on the parameter set. It should be understood that references to a first parameter set (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0065] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as the frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the NE 102 and the UE 104 can communicate wirelessly on one or more operating frequency bands. In some implementations, the NE 102 and the UE 104, as well as other devices or apparatuses, can use FR1 for cellular communication traffic (e.g., control information, data). In some implementations, the NE 102 and UE 104 and other devices or equipment may use FR2 for short-range, high data rate capabilities.

[0066] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the following parameter sets: a first parameter set (e.g., μ = 0) including a 15 kHz subcarrier spacing; a second parameter set (e.g., μ = 1) including a 30 kHz subcarrier spacing; and a third parameter set (e.g., μ = 2) including a 60 kHz subcarrier spacing. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with the following parameter sets: a third parameter set (e.g., μ = 2) including a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., μ = 3) including a 120 kHz subcarrier spacing.

[0067] Figure 2 An example of a UE 200 according to various aspects of the present disclosure is shown. The UE 200 may include a processor 202, a memory 204, a controller 206, and a transceiver 208. The processor 202, the memory 204, the controller 206, or the transceiver 208, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0068] The processor 202, memory 204, controller 206, or transceiver 208, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured to or otherwise support means for performing the functions described in the present disclosure.

[0069] The processor 202 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 202 may be configured to operate the memory 204. In some other implementations, the memory 204 may be integrated into the processor 202. The processor 202 may be configured to execute computer-readable instructions stored in the memory 204 to enable the UE 200 to perform various functions of the present disclosure.

[0070] Memory 204 can include volatile memory or non-volatile memory. Memory 204 can store computer-readable, computer-executable code including instructions that, when executed by processor 202, cause UE 200 to perform various functions described herein. This code can be stored in a non-transitory computer-readable medium such as memory 204 or another type of memory. Computer-readable media include both volatile and nonvolatile media, removable and nonremovable media, and computer storage media. Computer-readable media specifically include, but are not limited to, non-transitory computer-readable media, and communication media.

[0071] In some implementations, processor 202 and memory 204 coupled with processor 202 can be configured to cause UE 200 to perform one or more functions described herein (e.g., by processor 202 executing instructions stored in memory 204). For example, processor 202 can support wireless communication at a UE 200 in accordance with examples as disclosed herein. UE 200 can be configured to support means for receiving an indication for an uplink transmission including at least one physical uplink shared channel (PUSCH) transmission associated with different sets of sounding reference signal (SRS) resources to be transmitted simultaneously and determining parameters for phase tracking reference signal (PTRS) transmissions for each of the at least one PUSCH transmission.

[0072] Controller 206 can manage incoming and outgoing signals for UE 200. Controller 206 can also manage peripherals not integrated into UE 200. In some implementations, controller 206 can utilize an operating system, such as iOS®, ANDROID®, WINDOWS®, or other operating system. In some implementations, controller 206 can be implemented as part of processor 202.

[0073] In some implementations, UE 200 can include at least one transceiver 208. In some other implementations, UE 200 can have multiple transceivers 208. Transceiver 208 can represent a wireless transceiver. Transceiver 208 can include one or more receiver chains 210, one or more transmitter chains 212, or a combination thereof.

[0074] The receiver chain 210 may be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain 210 may include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 210 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 210 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 210 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0075] Transmitter chain 212 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 212 can include at least one modulator for modulating data onto a carrier signal, thereby preparing the signal for transmission over a wireless medium. The at least one modulator can be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 212 can also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level for transmission over a wireless medium. Transmitter chain 212 can also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0076] Figure 3 An example of a processor 300 according to aspects of the present disclosure is shown. The processor 300 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 300 may include a controller 302 configured to perform various operations according to the examples described herein. The processor 300 may optionally include at least one memory 304, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, the processor 300 may optionally include one or more arithmetic logic units (ALUs) 306. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0077] The processor 300 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., processor 300), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0078] The controller 302 may be configured to manage and coordinate various operations of the processor 300 (e.g., signaling, receiving, obtaining, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) so that the processor 300 supports various operations according to the examples described herein. For example, the controller 302 may operate as a control unit for the processor 300, generating control signals that manage the operation of various components of the processor 300. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0079] The controller 302 may be configured to retrieve (e.g., obtain, retrieve, receive) instructions from the memory 304 and determine which subsequent instruction(s) to execute, so that the processor 300 supports various operations according to the examples described herein. The controller 302 may be configured to track the memory addresses of instructions associated with the memory 304. The controller 302 may be configured to decode the instructions to determine the operations to be performed and the operands involved. For example, the controller 302 may be configured to interpret the instructions and determine control signals to be output to other components of the processor 300, so that the processor 300 supports various operations according to the examples described herein. Additionally or alternatively, the controller 302 may be configured to manage the flow of data within the processor 300. The controller 302 may be configured to control the transfer of data between registers, the arithmetic logic unit (ALU), and other functional units of the processor 300.

[0080] Memory 304 may include one or more caches (e.g., memory local to or included with processor 300, or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 304 may reside within or on a processor chipset (e.g., local to processor 300). In some other implementations, memory 304 may reside external to a processor chipset (e.g., remote from processor 300).

[0081] The memory 304 may store computer-readable, computer-executable code including instructions that, when executed by the processor 300, cause the processor 300 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. The controller 302 and / or the processor 300 may be configured to execute the computer-readable instructions stored in the memory 304 to cause the processor 300 to perform the various functions. For example, the processor 300 and / or the controller 302 may be coupled to or coupled to the memory 304, and the processor 300, the controller 302, and the memory 304 may be configured to perform the various functions described herein. In some examples, the processor 300 may include multiple processors, and the memory 304 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0082] One or more ALUs 306 can be configured to support various operations according to the examples described herein. In some implementations, one or more ALUs 306 can be located within or on a processor chipset (e.g., processor 300). In some other implementations, one or more ALUs 306 can be located external to the processor chipset (e.g., processor 300). One or more ALUs 306 can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 306 can receive input operands and an opcode, which determines the operation to be performed. One or more ALUs 306 can be configured with various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALUs 306 can support logic operations such as AND, OR, exclusive OR (XOR), not OR (NOR), and not AND (NAND), enabling one or more ALUs 306 to handle conditional operations, comparisons, and bitwise operations.

[0083] The processor 300 may support wireless communications according to examples as disclosed herein. The processor 300 may be configured or operable to support means for: receiving an indication for an uplink transmission, the uplink transmission comprising at least one physical uplink shared channel (PUSCH) transmission associated with different sounding reference signal (SRS) resource sets to be sent simultaneously; and determining parameters for a phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmission.

[0084] Figure 4 An example of an NE 400 according to various aspects of the present disclosure is shown. NE 400 may include a processor 402, a memory 404, a controller 406, and a transceiver 408. Processor 402, memory 404, controller 406, or transceiver 408, or various combinations thereof, or various components thereof, may be examples of apparatuses for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more interfaces.

[0085] The processor 402, memory 404, controller 406, or transceiver 408, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured to or otherwise support means for performing the functions described in the present disclosure.

[0086] Processor 402 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, processor 402 may be configured to operate memory 404. In some other implementations, memory 404 may be integrated into processor 402. Processor 402 may be configured to execute computer-readable instructions stored in memory 404 to enable NE 400 to perform various functions disclosed herein.

[0087] Memory 404 may include volatile memory or non-volatile memory. Memory 404 may store computer-readable, computer-executable code including instructions that, when executed by processor 402, cause NE 400 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 404 or another type of storage. Computer-readable media include non-transitory computer storage media and communication media, including any media that facilitates the transfer of computer programs from one location to another. Non-transitory storage media can be any available media that can be accessed by a general-purpose or special-purpose computer.

[0088] In some implementations, the processor 402 and the memory 404 coupled to the processor 402 may be configured to cause the NE 400 to perform one or more functions described herein (e.g., execution of instructions stored in the memory 404 by the processor 402). For example, the processor 402 may support wireless communications at the NE 400 according to the examples disclosed herein. The NE 400 may be configured to support means for: transmitting an indication for an uplink transmission, the uplink transmission including at least one physical uplink shared channel (PUSCH) transmission associated with different sounding reference signal (SRS) resource sets to be transmitted simultaneously; and determining parameters for a received phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmissions.

[0089] Controller 406 can manage input and output signals of NE 400. Controller 406 can also manage peripheral devices that are not integrated into NE 400. In some implementations, controller 406 can utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, controller 406 can be implemented as part of processor 402.

[0090] In some implementations, NE 400 may include at least one transceiver 408. In some other implementations, NE 400 may have multiple transceivers 408. Transceiver 408 may represent a wireless transceiver. Transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof.

[0091] Receiver chain 410 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, receiver chain 410 may include one or more antennas for receiving signals over the air or wireless medium. Receiver chain 410 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 410 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. Receiver chain 410 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0092] Transmitter chain 412 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 412 can include at least one modulator for modulating data onto a carrier signal, thereby preparing the signal for transmission over a wireless medium. The at least one modulator can be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 412 can also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level for transmission over a wireless medium. Transmitter chain 412 can also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0093] In Release 18, support is provided for single-DCI-based SDM PUSCH transmissions, where different layers of a PUSCH transmission are sent simultaneously by different panels, and for multiple-DCI-based PUSCH+PUSCH schemes, where different PUSCH transmissions are sent simultaneously by different panels. Phase noise estimation for different panels requires orthogonal Phase Tracking Reference Signals (PTRS).

[0094] In the present disclosure, PUSCH sent from different panels means that PUSCH is sent from different panels based on different SRS resource sets or different beams (e.g., spatial relationship or UL TCI state, or DLorJoint-TCIState specified in technical specification 38.331), or PUSCH is associated with different CORESETPoolIndex values.

[0095] It is proposed that for STxMP PUSCH transmission using the SDM scheme based on a single DCI, the PUSCH transmission corresponding to one panel (i.e., PUSCH corresponding to one SRS resource set) should be rate-matched around the PTRS port corresponding to another panel, as in Release 15. In this case, the power boost of the PTRS port may differ from the current specification for PUSCH transmission based on a single panel, because only the power of the muted REs of the same panel can be used for the power boost of the PTRS port. The issue of PTRS power boost in PUSCH transmission based on STxMP SDM needs to be addressed.

[0096] In addition, in STxMP PUSCH+PUSCH transmission based on multiple DCI, it has been agreed to limit the maximum number of PTRS ports for PUSCH transmission to one. The motivation for this limitation is to ensure that the maximum total number of PTRS ports is two even if two overlapping PUSCH transmissions are scheduled. If the scheduled PUSCH transmissions corresponding to different panels do not overlap in the time domain, the number of PTRS ports for PUSCH transmission corresponding to one panel can be at most two, as in the conventional scheme, to ensure performance when non-overlapping PUSCH transmissions are scheduled with high rank. Whether PUSCH transmissions from different panels overlap may depend dynamically on the scheduling DCI. Therefore, a solution is needed to ensure that in STxMP PUSCH+PUSCH transmission based on multiple DCI, the number of PTRS ports for PUSCH transmission is one.

[0097] In the current 3rd Generation Partnership Project (3GPP) Technical Specifications (TS), the following are provided.

[0098] 6.2.3.1 UE PT-RS transmission procedure when transform precoding is not enabled in TS 38.214

[0099] The maximum number of configured PT-RS ports is specified by the higher layer parameter maxNrofPorts in PTRS-UplinkConfig. It is not expected that a UE will be configured with a larger number of UL PT-RS ports than it has reported as needed.

[0100] If the UE has reported the capability to support fully coherent UL transmission, then if UL-PTRS is configured, the UE should expect the number of UL PT-RS ports to be configured as one.

[0101] For codebook-based or non-codebook-based UL transmissions, the association between the UL PT-RS ports and the DM-RS ports is indicated by the PTRS-DMRS Association field in DCI formats 0_1 and 0_2. For PUSCH corresponding to configured grant type 1 transmissions, the UE may assume that the association between the UL PT-RS ports and the DM-RS ports is defined by the value 0 in Table 7.3.1.1.2-25 or the value "00" in Table 7.3.1.1.1.2-26 described in clause 7.3.1 of [5, TS38.212].

[0102] For a PUSCH scheduled by DCI format 0_0 or by activating DCI format 0_0, the UL PT-RS port is associated with DM-RS port 0.

[0103] For non-codebook-based UL transmissions, the actual number of UL PT-RS ports to be transmitted is determined based on the SRI in DCI formats 0_1 and 0_2 or the higher-layer parameter sri-ResourceIndicator in rrc-ConfiguredUplinkGrant. If the UE is configured with the higher-layer parameter phaseTrackingRS in DMRS-UplinkConfig, the UE is configured with a PT-RS port index for each configured SRS resource via the higher-layer parameter ptrs-PortIndex configured by SRS-Config. If the PT-RS port index associated with different SRIs is the same, the corresponding UL DM-RS port is associated with that one UL PT-RS port.

[0104] For partially coherent and non-coherent codebook-based UL transmission, the actual number of UL PT-RS ports is determined based on the TPMI and / or number of layers indicated by the "Precoding information and number of layers" field in DCI format 0_1 ​​and DCI format 0_2 or configured by the higher-layer parameter precodingAndNumberOfLayers:

[0105] If the UE is configured with the higher layer parameter maxNrofPorts set to 'n2' in PTRS-UplinkConfig, the actual UL PT-RS ports and associated transport layers are derived from the indicated TPMI as follows:

[0106] - PUSCH antenna ports 1000 and 1002 in the indicated TPMI share PT-RS port 0, and PUSCH antenna ports 1001 and 1003 in the indicated TPMI share PT-RS port 1.

[0107] -UL PT-RS port 0 is associated with UL layer 'x' of the layers transmitted with PUSCH antenna port 1000 and PUSCH antenna port 1002 in the indicated TPMI, and UL PT-RS port 1 is associated with UL layer 'y' of the layers transmitted with PUSCH antenna port 1001 and PUSCH antenna port 1003 in the indicated TPMI, where 'x' and / or 'y' are given by the DCI parameter 'PTRS-DMRS association' as shown in DCI format 0_1 ​​and DCI format 0_2 as described in clause 7.3.1 of [5, TS 38.212].

[0108] When the UE uses Q p ={1,2} PT-RS ports are scheduled, and the number of scheduled layers is hour,

[0109] - If the UE is configured with the higher layer parameter ptrs-Power, the PUSCH per RE per layer to PT-RS power ratio is given by where The PT-RS scaling factor according to the higher layer parameter ptrs-Power is shown in Table 6.2.3.1-3, [4, TS 38.211] clause 6.4.1.2.2.1 is given by and also on the “Precoding information and number of layers” field in the DCI.

[0110] - If not configured or in case of non-codebook-based PUSCH, the UE shall assume that ptrs-Power in PTRS-UplinkConfig is set to state “00” in Table 6.2.3.1-3.

[0111] Table 6.2.3.1-3: Factor related to the PUSCH per RE per layer to PT-RS power ratio

[0112]

[0113] The present disclosure provides a method to solve the PTRS issue in simultaneous multi-panel transmission, at least related to the PTRS power boosting in SDM PUSCH transmission, and to ensure that the maximum number of PTRS ports for PUSCH transmission in M-DCI based STxMP PUSCH+PUSCH transmission is one when PUSCH transmissions from different panels overlap.

[0114] PTRS power boost in SDM PUSCH transmission

[0115] In NR, different PTRS ports for PUSCH transmission occupy different REs in the frequency domain and are transmitted on different layers of PUSCH transmission. The power boosting of PTRS is specified in Release 15 to ensure the phase noise estimation performance. Until Release 17, the PTRS power boosting (i.e., the PUSCH per RE per layer to PT-RS power ratio ) is determined based on the number of PUSCH layers and the coherence type of the indicated precoder (i.e., full-coherent, partial-coherent, or non-coherent) and the number of PTRS ports scheduled to the UE. For non-codebook-based PUSCH transmission, the PTRS power boosting is the same as for non-coherent codebook PUSCH transmission.

[0116] ​For S-DCI based SDM PUSCH transmission, different PUSCH layers of the same PUSCH are transmitted by different panels. This means that different layers of the PUSCH transmission are transmitted based on SRS resources in different TCI states or different SRS resource sets. If two SRS resource sets for codebook-based or non-codebook-based PUSCH transmission are configured with the SRS resource set indicator in the scheduling DCI being '10' and the multi-panel scheme is configured as 'SDMscheme' (i.e., the higher layer parameter multipanelScheme is configured and set to 'SDMscheme'), it is identified as an SDM PUSCH transmission. For codebook-based STxMP SDM PUSCH, the scheduling DCI contains two TPMI fields, and each TPMI field indicates the precoding information and the number of layers transmitted through the SRS ports of the SRS resources indicated in each SRS resource set, respectively. For non-codebook-based STxMP SDM PUSCH, two SRI fields are included in the scheduling DCI, and each field indicates the SRS resources in each SRS resource set, so that the UE can determine the precoding matrix of the PUSCH layer associated with each SRS resource set.

[0117] Based on the agreed-upon rank combinations of STxMP SDM PUSCH, the number of PUSCH layers transmitted from different panels (or corresponding to different SRS resource sets) may differ, for example, in the layer combinations {1+2} and {2+1}, where the number of PUSCH layers from one panel is 1 and the number of PUSCH layers from another panel is 2. Furthermore, the power boost for PTRS ports corresponding to different panels may differ, assuming that power boosting can only be performed within REs of the same panel. Therefore, for S-DCI-based SDM PUSCH transmissions, the PTRS power boost for PTRS ports from one panel should be determined based on the number of PUSCH layers and precoder coherence type of the PUSCH transmissions from the same panel. In other words, when determining the power boost for PTRS ports of PUSCH transmissions based on the SRS resource set, the number of PUSCH layers and coherence type are based on the TPMI field or SRI field associated with the same SRS resource set.

[0118] For the STxMP PUSCH SDM scheme based on single DCI, layer combinations of {1+1, 1+2, 2+1 and 2+2} are supported. When the maximum number of PTRS ports (e.g., maxNrofPortsforSdm) is configured as 1, examples of PTRS power boost for layer combinations of {1+1 and 1+2} are as follows Figure 5 As shown in .

[0119] exist Figure 5In the example shown in , the maximum number of PTRS ports is one, and PTRS transmissions can be sent from panel 0 or panel 1 based on the associated DMRS port; and PUSCH transmissions from one panel are rate matched around the REs of a PTRS port from another panel.

[0120] For PUSCH transmission 500A in which the number of layers of PUSCH transmissions from each panel (i.e., panel 0 502 and panel 1 504) is one, PTRS port 0 of the PUSCH transmission is transmitted on RE 510 of panel 0 502, while RE 520 of panel 1 504 is muted. In this example, even with the presence of muted RE 520, the power of PTRS port 0 cannot be boosted because muted RE 520 and PTRS port 0 are transmitted by different panels, and there are no muted REs in the same panel (i.e., panel 0 502) for boosting PTRS port 0 transmissions.

[0121] For a PUSCH transmission 500B in which the number of layers of the PUSCH transmission from panel 0 502 is one and the number of layers of the PUSCH transmission from panel 1 504 is two (i.e., layers 504a and 504b), the PTRS port 0 of the PUSCH transmission is transmitted on RE 520 of layer 504a of panel 1 504, while RE 510 of panel 0 502 and RE 520a of layer 504b of panel 1 504 are both muted. In this example, when the two layers 504a and 504b are fully coherent, the power of the muted RE 520a in the same panel (i.e., panel 1 504) can be used for power boosting of PTRS port 0.

[0122] Therefore, in the case where the maximum number of PTRS ports is configured as one, when the PTRS port of PUSCH transmission is sent from a panel with a single PUSCH layer, the power boost of the PTRS port (i.e., ) is 0 dB. When the PTRS port of a PUSCH transmission is sent from a panel with two PUSCH layers, the power boost of the PTRS port depends on the coherence type of the indicated precoder. Specifically, for the case where the two layers of codebook-based PUSCH transmission are partially coherent or incoherent (i.e., the TPMI associated with the PTRS port to the same SRS resource set is partially coherent or incoherent) or for the case of non-codebook-based PUSCH transmission, the power of the muted REs on the other layer cannot be borrowed for PTRS transmission as in Release 17, i.e. For the case where the two layers of codebook-based PUSCH transmission are fully coherent (i.e., the TPMI associated with the PTRS port to the same SRS resource set is fully coherent), the power of the muted RE on the other layer can be borrowed for PTRS transmission, i.e. is 3 dB.

[0123] When the maximum number of PTRS ports (e.g., maxNrofPortsforSdm) is configured as 2, examples of PTRS power boost for layer combinations of {1+1 and 1+2} are as follows Figure 6 As shown in .

[0124] exist Figure 6 In the example shown in , the maximum number of PTRS ports is configured as two, the actual number of PTRS ports for PUSCH transmission is two, and each PTRS port is associated with a DMRS port associated with a TPMI or SRI field.

[0125] For a PUSCH transmission 600A in which the number of layers of PUSCH transmissions from each panel (i.e., panel 0 602 and panel 1 604) is one, two PTRS ports (i.e., PTRS ports 0 and 1) transmit on RE 612 of panel 0 602 and RE 624 of panel 1 604, respectively, while their corresponding resources, i.e., RE 622 of panel 1 604 and RE 614 of panel 0 602, are muted. In this example, the power of the muted RE 614 can be used for power boosting of PTRS port 0 in the same panel (i.e., panel 0 602); and the power of the muted RE 622 can be used for power boosting of PTRS port 1 in the same panel (i.e., panel 1 604).

[0126] For PUSCH transmission 600B, the number of layers for PUSCH transmission from panel 0 602 is one, and the number of layers for PUSCH transmission from panel 1 604 is two (i.e., layers 604a and 604b). The two PTRS ports (i.e., PTRS ports 0 and 1) transmit on RE 614 of panel 0 602 and RE 622 of layer 604a of panel 1 604, respectively, while their corresponding resources, i.e., RE 624 and RE 624a of panel 1 604, and RE 612 of panel 0 602 and RE 622a of layer 604b of panel 1 604, are all muted. In this example, the power of the silent RE 612 can be used for power boosting of PTRS port 0 in the same panel (i.e., panel 0 602); and when the two layers 604a and 604b are fully coherent, the power of the silent RE 622a, RE 624 and RE 624a can be used for power boosting of PTRS port 1 in the same panel (i.e., panel 1 604).

[0127] PUSCH transmissions from one panel are rate matched around the REs of the PTRS ports from both panels. Even if a PTRS port of one panel cannot borrow power from the muted REs of another panel, it can still boost the power of the PTRS port by borrowing power from the muted REs of the same panel. Therefore, when the maximum number of PTRS ports is configured as 2, the power boost of the PTRS port (i.e., ) is 3 dB; when the PTRS port of a PUSCH transmission is sent from a panel with two PUSCH layers, the power boost of the PTRS port depends on the coherence type of the indicated precoder. Specifically, for the case when the two layers of the codebook-based PUSCH transmission are partially coherent or incoherent (i.e., the TPMI associated with the PTRS port to the same SRS resource set is partially coherent or incoherent) or for the case of non-codebook-based PUSCH transmission, is 3 dB, and for the case where both layers of the codebook-based PUSCH transmission are fully coherent (i.e., the TPMIs associated with the PTRS ports to the same SRS resource set are fully coherent), is 6 dB.

[0128] Therefore, the power boost of the PTRS port in SDM PUSCH transmission based on S-DCI can be summarized in Table 1, where Q p is the maximum number of configured PTRS ports or the total number of actual PTRS ports across different panels, and coherence type is the precoder that indicates the precoder used for PUSCH transmissions from the same panel as the PTRS ports.

[0129] Table 1: PUSCH to PT-RS power ratio per layer per RE for SDM PUSCH transmission Related factors

[0130]

[0131] That is, the power increase of PTRS port x in SDM PUSCH transmission is or ,in is the number of PUSCH layers that are co-precoded with the PUSCH layer associated with PTRS port x in the same SRS resource set as PTRS port x, and is the maximum number of configured PTRS ports or the total number of scheduled or actual PTRS ports for PUSCH transmission associated with different SRS resource sets.

[0132] The power boost for PTRS ports corresponding to different panels may be different. Therefore, the power boost should be determined for each PTRS port individually based on Table 1 or the above formula.

[0133] Based on the above, the UE may receive an indication from the gNB (i.e., multipanelScheme is set to "SDMscheme") indicating that the PUSCH transmission is an SDM PUSCH transmission based on S-DCI, where different layers of the PUSCH transmission are associated with different SRS resource sets; and the UE may determine the power boost of the PTRS port for the PUSCH transmission (i.e., the PUSCH to PTRS power ratio per layer per RE for one PTRS port). ).

[0134] Power ratio of PTRS port x The number of PUSCH layers pre-coded with the PUSCH layers associated with PTRS port x in the same SRS resource set as PTRS port x and the total number of scheduled PTRS ports for PUSCH transmissions associated with different SRS resource sets to confirm.

[0135] For ptrs-Power configured as '00' (ie, the first column of Table 1), if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is one, the power ratio of the PTRS port is for For ptrs-Power configured as '00', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is two, then for fully coherent codebook-based PUSCH, the power ratio of the PTRS port is for For ptrs-Power configured as '00', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is two, the power ratio of the PTRS port for partially coherent and non-coherent codebook-based PUSCH and for non-codebook-based PUSCH is for For ptrs-Power configured as '01', in some embodiments, if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is one, the power of the PTRS port is 3 dB; for ptrs-Power configured as '01', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is two, the power ratio of the PTRS port is For ptrs-Power configured as '01', in some other embodiments, if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is one, the power ratio of the PTRS port is for For ptrs-Power configured as '01', if the number of PUSCH layers associated with the PTRS port to the same SRS resource set is two, the power ratio of the PTRS port is for .

[0136] In one example (i.e., Example 1), assume that the multi-panel scheme is configured as 'SDMscheme' and maxNrofPortsforSDM is 2; and two SRS resource sets for codebook-based PUSCH transmission are configured and the number of SRS ports is 4. DCI format 0_1 ​​schedules 3-layer SDM PUSCH transmission, and the first TPMI field indicates the precoder for one layer of PUSCH transmission from panel 0 based on the SRS resources in the first SRS resource set. , and the second TPMI field indicates the precoders for the two layers of the PUSCH transmission from panel 1 based on the SRS resources in the second SRS resource set The actual number of PTRS ports is 2, and PTRS port 0 is associated with one layer from panel 0, and PTRS port 1 is associated with the first layer from panel 1, which is similar to Figure 6 For example, for PUSCH 600B in . Then, for PTRS port 0, the power can be boosted by 3 dB from the power of the muted RE corresponding to PTRS port 1 (i.e., RE 612); and for PTRS port 1, since the indicated precoder is partially coherent, the power of PTRS port 1 may only be boosted by 3 dB from the power of the muted RE corresponding to PTRS port 0 on the same layer (i.e., RE 624). If the second TPMI field indicates a fully coherent precoder, such as , the power of PTRS port 1 can be increased by 6dB compared to the power of the silent RE corresponding to PTRS port 0 on both layers.

[0137] PTRS port in PUSCH+PUSCH transmission based on M-DCI

[0138] In Release 17, PUSCHs scheduled by DCIs associated with different CORESETPoolIndex values should not overlap in time domain, and the number of PTRS ports for a PUSCH transmission can be at most two. In Release 17, the actual number of transmitted PTRS ports is determined based on TPMI and / or the number of layers and coherence type (for codebook-based PUSCH transmission) or based on the indicated SRS resource (for non-codebook-based PUSCH transmission). In Release 18, two PUSCH transmissions scheduled by DCIs or CG PUSCH associated with different CORESETPoolIndex values (which means PUSCH transmissions are transmitted based on different SRS resource sets) can fully or partially overlap in time domain, but in PUSCH+PUSCH transmission, for each PUSCH transmission, the maximum number of PTRS ports can only be one. If two SRS resource sets for codebook-based or non-codebook-based PUSCH transmission are configured and enableSTx2PofmDCI is configured (which means PUSCH transmissions from different panels can overlap in time domain in M-DCI scenario), and the PUSCH transmissions are associated with different values of CORESETPoolIndex, it is identified as M-DCI based PUSCH+PUSCH transmission. Whether the PUSCH transmissions from different panels and with different CORESETPoolIndex values overlap can dynamically depend on the scheduling DCI. Then, if the PUSCH transmissions from different panels overlap in time domain, it is needed to ensure the maximum number of PTRS ports for each PUSCH transmission is one. The following schemes are provided. In these schemes, the UE can receive an indication for multiple PUSCH transmissions associated with different SRS resource sets (i.e., enableSTx2PofmDCI is configured); and the UE can determine the maximum number of PTRS ports for each PUSCH transmission.

[0139] In the first scheme, two RRC parameters are used to configure the maximum number of PTRS ports in M-DCI based PUSCH+PUSCH transmission.

[0140] In this solution, an additional RRC parameter, such as maxNrofPortsofSTx, can be configured for the UE. The legacy parameter maxNrofPorts (i.e., the first parameter) can be used to configure the maximum number of PTRS ports for PUSCH transmissions that do not overlap with other PUSCH transmissions from different panels with different CORESETPoolIndex values, and this parameter can have a value of n1 or n2, where n1 can be one and n2 can be two. The new parameter maxNrofPortsofSTx (i.e., the second parameter) is used to configure the maximum number of PTRS ports for PUSCH transmissions that overlap with at least one PUSCH transmission associated with a different CORESETPoolIndex value, and this parameter can have a value of n1. If the UE transmits a PUSCH from one panel and determines that there are no overlapping PUSCH transmissions from another panel, the UE determines the actual number of PTRS ports based on the legacy parameter. If the UE transmits two overlapping PUSCH transmissions from different panels with different CORESETPoolIndex values, the UE determines the number of PTRS ports for each PUSCH transmission based on the new parameter.

[0141] In the second solution, one RRC parameter is used to configure the maximum number of PTRS ports in M-DCI-based PUSCH+PUSCH transmission.

[0142] In this solution, a parameter (i.e., the third parameter), such as the legacy parameter maxNrofPorts, is used to configure the maximum number of PTRS ports used for each PUSCH transmission in M-DCI scenarios. Since the maximum number of PTRS ports can be at most two for non-overlapping PUSCH transmissions from different panels, the value of this parameter can be either n1 or n2. If the maximum number of PTRS ports is configured as n2, the following two methods are proposed to ensure that the maximum number of PTRS ports per PUSCH transmission is one when the UE transmits two overlapping PUSCHs from different panels.

[0143] As a first method of this solution, for STxMP PUSCH+PUSCH transmission, the UE always assumes that the actual number of PTRS ports for PUSCH transmission is 1.

[0144] In the current standard, the actual number of PTRS ports is determined based on the indicated precoder (for codebook-based PUSCH transmission) or the indicated SRS resources (for non-codebook-based PUSCH transmission). Specifically, for partially coherent and non-coherent codebook-based PUSCH transmission, the actual number of PTRS ports is determined based on the indicated TPMI and / or the number of layers, where PUSCH antenna ports 1000 and 1002 in the indicated TPMI share PTRS port 0, and PUSCH antenna ports 1001 and 1003 in the indicated TPMI share PTRS port 1; for non-codebook PUSCH, the actual number of PTRS ports is determined based on the indicated SRS resources, where each SRS resource is configured with a PTRS port index.

[0145] Therefore, in M-DCI-based PUSCH+PUSCH transmissions, if PUSCH transmissions from different panels with different CORESETPoolIndex values ​​do not overlap, the conventional procedure for determining the actual number of PTRS ports is applied; if PUSCH transmissions from different panels with different CORESETPoolIndex values ​​overlap, the UE always determines the actual number of PTRS ports for each PUSCH transmission as 1, regardless of the indicated precoder (for codebook-based PUSCH transmissions) or SRS resources (for non-codebook-based PUSCH transmissions), and the UE sends this one PTRS port (i.e., PTRS port 0) for each PUSCH transmission associated with the CORESETPoolIndex value.

[0146] In one example (i.e., Example 2), assume that enableSTx2PofmDCI is configured, which means that PUSCH transmissions from different panels can overlap in the time domain in an M-DCI scenario. Two SRS resource sets for codebook-based transmission are configured and the number of SRS ports is 4. PDCCH-Config contains two different values ​​of CORESETPoolIndex in ControlResourceSet in the active BWP, and the maximum number of configured PTRS ports is 2. DCI # 0 associated with CORESETPoolIndex 0 schedules PUSCH transmission # 0, and the TPMI field indicates the precoder for PUSCH transmission # 0 from panel 0 based on the SRS resources in the first SRS resource set. DCI #1 associated with CORESETPoolIndex 1 schedules PUSCH transmission #1, and the TPMI field indicates the precoder for PUSCH transmission #1 from panel 1 based on the SRS resources in the second SRS resource set. . Then, if PUSCH transmission #0 and PUSCH transmission #1 do not overlap, since PUSCH antenna ports 1000 and 1002 share the same PTRS port, the actual number of PTRS ports for PUSCH transmission #0 is 1, and since PUSCH antenna ports 1000 and 1001 are different PTRS ports, the actual number of PTRS ports for PUSCH transmission #0 is 2; and if PUSCH transmission #0 and PUSCH transmission #1 overlap in the time domain, the actual number of PTRS ports for each PUSCH transmission is 1.

[0147] In this method, the UE determines the actual number of PTRS ports for a PUSCH transmission based on whether the PUSCH transmission overlaps with another PUSCH transmission with a different CORESETPoolIndex value.

[0148] As a second method of the second scheme, in M-DCI-based STxMP PUSCH+PUSCH transmission, the UE always sends PTRS port 0 for each PUSCH transmission.

[0149] In this method, the UE determines the actual number of PTRS ports based on the conventional procedure as explained in the first method. If PUSCH transmissions from different panels with different CORESETPoolIndex values ​​overlap in the time domain and the actual number of PTRS ports for the PUSCH transmission is 2, the UE always transmits PTRS port 0 for that PUSCH transmission. For example, as in Example 2, if PUSCH transmission #0 and PUSCH transmission #1 overlap, the UE determines the actual number of PTRS ports for PUSCH transmission #0 and PUSCH transmission #1 to be 1 and 2, respectively, based on the conventional procedure, but the UE only transmits PTRS port 0 for PUSCH transmission #0 and PTRS port 0 for PUSCH transmission #1. In this method, the UE determines the actual number of PTRS ports based on the conventional procedure, but transmits PTRS port 0 only when PUSCH transmissions from different panels with different CORESETPoolIndex values ​​overlap in the time domain.

[0150] The third scheme ensures that the maximum number of PTRS ports per PUSCH transmission is 1, which involves gNB implementation. In this scheme, the gNB only indicates some precoders (for codebook-based PUSCH) or SRI combinations (for non-codebook-based PUSCH) that make the actual number of PTRS ports 1. That is, if two SRS resource sets for codebook-based or non-codebook-based PUSCH transmission are configured and the higher layer parameter enableSTx2PofmDCI is configured, and two different CORESETPoolIndex values ​​in ControlResourceSet are configured, then when different PUSCH transmissions from different panels overlap, the UE expects the indicated precoder or SRS resources for PUSCH transmission to produce one PTRS port. That is, in the case of overlap of different PUSCH transmissions associated with different SRS resource sets, the UE does not expect the indicated precoder or SRS resources to produce more than one PTRS port. For example, for a 2-layer codebook-based PUSCH transmission with a number of SRS ports of 2, the UE expects the precoder to be 、 For a 2-codebook PUSCH transmission with 4 SRS ports, the UE expects the precoder to be one of the following: 、 、 、 、 、 、 、 、 、 .

[0151] However, this solution may not be suitable for all situations. For example, if the UE reports non-coherent capability and the number of codebook SRS resources is two, no suitable precoder will exist. Furthermore, in Release 18, both CG PUSCH+CG PUSCH transmission (i.e., configured grant PUSCH and configured grant PUSCH can be transmitted simultaneously from different panels and overlap in the time domain) and CG PUSCH+DG PUSCH transmission (i.e., configured grant PUSCH and dynamically scheduled PUSCH can be transmitted simultaneously from different panels and overlap in the time domain) are supported. For Type 1 CG PUSCH, the precoder is configured by RRC, and if DG PUSCH overlaps with CG PUSCH, the precoder cannot be dynamically changed to ensure the number of PTRS ports is one. That is, if the precoder for Type 1 CG PUSCH has two PTRS ports, CG PUSCH cannot be transmitted simultaneously with other PUSCHs. In these cases, the first and second solutions are preferred to avoid reducing gNB flexibility.

[0152] Figure 7 A flow chart of a method according to various aspects of the present disclosure is shown. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the functional units of the UE to perform the described functions.

[0153] At 702, the method may include receiving an indication for an uplink transmission including at least one simultaneous PUSCH transmission associated with different SRS resource sets. The operations of 702 may be performed according to the examples described herein. In some implementations, aspects of the operations of 702 may be performed as described in reference to Figure 2 The described UE performs

[0154] At 704, the method may include determining parameters for PTRS transmission for each PUSCH transmission in at least one PUSCH transmission. The operations of 704 may be performed according to the examples described herein. In some implementations, aspects of the operations of 704 may be performed as described in reference to Figure 2 The described UE performs

[0155] It should be noted that the methods described herein describe one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0156] Figure 8A flow chart of a method according to various aspects of the present disclosure is shown. The operations of the method may be implemented by an NE as described herein. In some implementations, the NE may execute a set of instructions to control the functional units of the NE to perform the described functions.

[0157] At 802, the method may include sending an indication for an uplink transmission including at least one simultaneous PUSCH transmission associated with different SRS resource sets. The operations of 802 may be performed according to the examples described herein. In some implementations, aspects of the operations of 802 may be performed by the reference Figure 4 The NE described here performs the following.

[0158] At 804, the method may include determining parameters for PTRS transmission for each PUSCH transmission in at least one PUSCH transmission. The operations of 804 may be performed according to the examples described herein. In some implementations, aspects of the operations of 804 may be performed as described in reference to Figure 4 The NE described here performs the following.

[0159] It should be noted that the methods described herein describe one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0160] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the UE to: receiving an indication for uplink transmissions comprising at least one physical uplink shared channel (PUSCH) transmission associated with different sounding reference signal (SRS) resource sets to be sent simultaneously; and Parameters of a phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmission are determined.

2. The UE according to claim 1, wherein: The indication is that the higher layer parameter multipanelScheme is configured and set to "SDMscheme"; the uplink transmission is a PUSCH transmission, different layers of the PUSCH transmission are associated with different SRS resource sets; and the parameters include the PUSCH to PTRS power ratio per layer per RE of a PTRS port .

3. The UE according to claim 2, wherein: The power ratio of PTRS port x is based on the number of PUSCH layers pre-coded with the PUSCH layers associated with the PTRS port x in the same SRS resource set as the PTRS port x. , and the total number of scheduled PTRS ports for PUSCH transmissions associated with different SRS resource sets To be determined.

4. The UE according to claim 3, wherein: The power ratio for .

5. The UE according to claim 3, wherein: For ptrs-Power configured as '00', if the number of PUSCH layers associated with the same SRS resource set as a PTRS port is one, the power ratio of the PTRS port is for . The UE according to claim 3, wherein: For ptrs-Power configured as '00', if the number of PUSCH layers associated with the same SRS resource set as a TRS port is two, then for fully coherent codebook-based PUSCH, the power ratio of the PTRS port is for .

7. The UE according to claim 3, wherein: For ptrs-Power configured as '00', if the number of PUSCH layers associated with the same SRS resource set as a PTRS port is two, then for partially coherent and non-coherent codebook-based PUSCH and for non-codebook-based PUSCH, the power ratio of the PTRS port is for .

8. The UE according to claim 3, wherein: For ptrs-Power configured as '01', if the number of PUSCH layers associated with a PTRS port to an SRS resource set is one, the power ratio of the PTRS port is is 3 dB.

9. The UE according to claim 3, wherein: For ptrs-Power configured as '01', if the number of PUSCH layers associated with the same SRS resource set as a PTRS port is two, the power ratio of the PTRS port is 6dB.

10. The UE according to claim 1, wherein: The indication is that: a higher layer parameter enableSTx2PofmDCI is configured; the uplink transmission is a plurality of PUSCH transmissions associated with different SRS resource sets; and the parameter includes a maximum number of PTRS ports for each of the plurality of PUSCH transmissions.

11. The UE according to claim 10, wherein: A first parameter is received for configuring the maximum number of PTRS ports for non-overlapping PUSCH transmissions associated with different SRS resource sets, wherein a value of the first parameter is one or two.

12. The UE according to claim 11, wherein: A second parameter is received for configuring the maximum number of PTRS ports for overlapping PUSCH transmissions associated with different SRS resource sets, wherein a value of the second parameter is one.

13. The UE according to claim 12, wherein: Based on whether PUSCH transmissions associated with different SRS resource sets overlap, an actual number of PTRS ports is determined for each PUSCH transmission according to the first parameter or the second parameter.

14. The UE according to claim 10, wherein: A third parameter for configuring the maximum number of PTRS ports is received, and a value of the third parameter is one or two.

15. The UE according to claim 14, wherein: If the maximum number of PTRS ports is two, and PUSCH transmissions associated with different SRS resource sets overlap in the time domain, the actual number of PTRS ports per PUSCH transmission is determined to be one.

16. The UE according to claim 14, wherein: If the maximum number of PTRS ports is two, and PUSCH transmissions associated with different SRS resource sets overlap in the time domain, only PTRS port 0 of each PUSCH transmission is sent.

17. The UE according to claim 10, wherein: In case different PUSCH transmissions associated with different SRS resource sets overlap, it is not desirable for the indicated precoder or SRS resources to result in more than one PTRS port.

18. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: receiving an indication for uplink transmissions comprising at least one physical uplink shared channel (PUSCH) transmission associated with different sounding reference signal (SRS) resource sets to be sent simultaneously; and Parameters of a phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmission are determined.

19. A method performed by a user equipment (UE), the method comprising: receiving an indication for uplink transmissions comprising at least one physical uplink shared channel (PUSCH) transmission associated with different sounding reference signal (SRS) resource sets to be sent simultaneously; and Parameters of a phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmission are determined.

20. A base station for wireless communication, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the base station to: transmitting an indication for uplink transmissions including at least one physical uplink shared channel (PUSCH) transmission associated with different sounding reference signal (SRS) resource sets to be transmitted simultaneously; and Parameters of a received phase tracking reference signal (PTRS) transmission for each of the at least one PUSCH transmission are determined.

Images