Methods for facilitating 3Tx PUSCH transmission

Abstract

Various aspects of this disclosure relate to a UE for facilitating 3Tx PUSCH transmission, a processor for wireless communication, a network entity, a method, and a computer-readable medium. The UE receives from the network entity a configuration indicating PUSCH transmission based on a 3-port codebook. Based on this received configuration, the UE sends a 3-port SRS to the network entity. The UE receives a Data Encoding (DCI) from the network entity, which includes a TPMI field indicating the 3-port precoder and layer number used for PUSCH transmission. In this way, the related issues of supporting 3Tx PUSCH transmission are resolved.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically to user equipment (UE), network entities, processors, methods, and computer-readable media for facilitating 3Tx Physical Uplink Shared Channel (PUSCH) transmission. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the 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)). Additionally, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] In Rel-15, 1-port, 2-port, and 4-port PUSCH transmissions are supported. In Rel-18, 8-port PUSCH transmissions are supported. Current commercial mobile UEs are typically equipped with only 1 or 2 Tx antennas. To enhance uplink (UL) performance and anticipate advancements in hardware and design technologies, 3Tx antenna PUSCH transmissions are supported in Rel-19. Further research is needed on this aspect. Summary of the Invention

[0004] To support 3Tx PUSCH transmission, several issues need to be addressed. These include the design of the 3-port codebook and the transmit precoding matrix indicator (TPMI); and the design of the 3-port sounding reference signal (SRS) resources. Furthermore, the SRS used for antenna switching may also need to be enhanced. Embodiments of this disclosure address these issues related to supporting 3Tx PUSCH transmission.

[0005] This disclosure relates to a UE for facilitating 3Tx PUSCH transmission, a network entity, a processor for wireless communication, a method, and a computer-readable medium.

[0006] In a first aspect, a UE is provided. The UE includes a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive from a network entity a configuration indicating Physical Uplink Shared Channel (PUSCH) transmission based on a 3-port codebook; based on the reception of the configuration, transmit a 3-port probe reference signal (SRS) to the network entity; and receive downlink control information (DCI) from the network entity, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating the 3-port precoder and layer number used for PUSCH transmission.

[0007] In a second aspect, a network entity is provided, comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: transmit to a user equipment (UE) a configuration indicating physical uplink shared channel (PUSCH) transmission based on a 3-port codebook; receive a 3-port probe reference signal (SRS) from the UE; and transmit downlink control information (DCI) to the UE, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating the 3-port precoder and layer number used for PUSCH transmission.

[0008] In a third aspect, a processor for wireless communication is provided. The processor includes: at least one memory; and a controller coupled to the at least one memory and configured such that the controller: receives at a user equipment (UE) a configuration indicating physical uplink shared channel (PUSCH) transmission based on a 3-port codebook from a network entity; based on the reception of the configuration, transmits a 3-port probe reference signal (SRS) to the network entity; and receives downlink control information (DCI) from the network entity, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating the 3-port precoder and layer number for PUSCH transmission.

[0009] In a fourth aspect, a method performed by a user equipment (UE) is provided, the method comprising: receiving from a network entity a configuration indicating physical uplink shared channel (PUSCH) transmission based on a 3-port codebook; based on the reception of the configuration, sending a 3-port probe reference signal (SRS) to the network entity; and receiving downlink control information (DCI) from the network entity, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating a 3-port precoder and layer number for PUSCH transmission.

[0010] In a fifth aspect, a method performed by a network entity is provided, the method comprising: sending to a user equipment (UE) a configuration indicating physical uplink shared channel (PUSCH) transmission based on a 3-port codebook; receiving a 3-port probe reference signal (SRS) from the UE; and sending downlink control information (DCI) to the UE, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating the 3-port precoder and layer number used for PUSCH transmission.

[0011] In a sixth aspect, a computer-readable medium is provided having instructions stored thereon that, when executed by a processor of a device, cause the device to perform the method according to the fourth or fifth aspect of this disclosure.

[0012] In some implementations of the above method, UE, and network entity, the UE can ignore one of the first and second parameters by ignoring the second parameter based on the determination that the first altitude range and the second altitude range overlap.

[0013] In some implementations of the above methods, UEs, and network entities, a 3-port precoder is selected from a set of precoding matrices, where each precoding matrix has three rows and one or more columns corresponding to one or more layers.

[0014] In some implementations of the above methods, UEs, and network entities, for each precoding matrix, the precoding matrix includes only one non-zero element in each column.

[0015] In some implementations of the above methods, UEs, and network entities, when the maximum rank of the PUSCH transmission is greater than 1, the TPMI field includes three bits indicating the 3-port precoder and the number of layers used for the PUSCH transmission; or when the maximum rank of the PUSCH transmission is 1, the TPMI field includes two bits indicating the 3-port precoder and the number of layers used for the PUSCH transmission.

[0016] In some implementations of the above methods, UEs, and network entities, when two SRS resource sets used for codebooks are configured, the DCI also includes a second TPMI field, which indicates a second 3-port precoder and a second layer number for PUSCH transmission.

[0017] In some implementations of the above methods, UEs, and network entities, when a single-frequency network (SFN) scheme or a time-division multiplexing (TDM) scheme is configured for PUSCH transmission, if the maximum rank of the PUSCH transmission is greater than 1, the second TPMI field includes two bits indicating the second 3-port precoder and the number of layers that is the same as the number of layers indicated by the first TPMI field; or if the maximum rank of the PUSCH transmission is equal to 1, the second TPMI field includes two bits indicating the second 3-port precoder and the second number of layers for PUSCH transmission.

[0018] In some implementations of the above methods, UEs, and network entities, when the spatial division multiplexing (SDM) scheme is configured for PUSCH transmission, if the maximum rank of the PUSCH transmission is greater than 1, the second TPMI field includes three bits indicating the second 3-port precoder and the second layer number for the PUSCH transmission; or if the maximum rank of the PUSCH transmission is 1, the second TPMI field includes two bits indicating the second 3-port precoder and the second layer number for the PUSCH transmission.

[0019] In some implementations of the above methods, UEs, and network entities, the first parameter indicating the number of antenna ports for 3-port SRS resources is... It is configured as 3.

[0020] In some implementations of the above methods, UEs, and network entities, the second parameter is used when determining the cyclic shift (CS) of the 3-port SRS resource. The value is 3.

[0021] In some implementations of the above methods, UEs, and network entities, the transmission comb number... K TC When the second parameter is equal to 2 and the second parameter is equal to 3, the UE and the network entity can perform a round-down or round-up operation to obtain the CS of the 3-port SRS resource.

[0022] In some implementations of the above methods, UEs, and network entities, the transmission comb number K TC Equal to 2 and the first parameter The value 3 cannot be configured simultaneously.

[0023] In some implementations of the above methods, UEs, and network entities, the second parameter is used when determining the CS of the 3-port SRS resource. The value is 4.

[0024] In some implementations of the above methods, UEs, and network entities, the first parameter It is configured as 4, and the second parameter is used when determining the CS of the 3-port SRS resource. The value is 4.

[0025] In some implementations of the above method, UE, and network entities, of the four resulting CSs, the first three CSs are CSs for 3-port SRS resources.

[0026] In some implementations of the above methods, UEs, and network entities, the SRS sequence of the SRS resource is mapped to a physical resource having a coefficient indicating the number of antenna ports equal to 3.

[0027] In some implementations of the above method, UE, and network entity, the UE distributes linear transmission power equally across the three antenna ports used for SRS transmission.

[0028] In some implementations of the above methods, UEs, and network entities, the UE selects a precoder from an uplink codebook with an equal number of antenna ports (3).

[0029] In some implementations of the above method, UE, and network entity, the UE sends SRS resources for antenna switching, wherein, depending on the UE's capabilities, the antenna switching supports an SRS transmit port switch of one of 1T3R, 2T3R, 3T3R, 3T4R, 3T6R, and 3T8R.

[0030] In some implementations of the above methods, UEs, and network entities, for 2T3R, in a maximum of two SRS resource sets used for antenna switching, a total of two SRS resources are configured, one of which has two SRS ports and the other has a single SRS port.

[0031] In some implementations of the above method, UE, and network entities, for 2T3R, a total of two SRS resources are configured in at most two SRS resource sets used for antenna switching, wherein each SRS resource has two SRS ports.

[0032] In some implementations of the above method, UE, and network entities, for 3T4R, in a maximum of two SRS resource sets used for antenna switching, a total of two SRS resources are configured, one of which has three SRS ports and the other has a single SRS port.

[0033] In some implementations of the above method, UE, and network entities, for 3T4R, a total of two SRS resources are configured in at most two SRS resource sets used for antenna switching, wherein each SRS resource has three SRS ports.

[0034] In some implementations of the above method, UE, and network entities, for 3T8R, a total of three SRS resources are configured in a set of up to three SRS resources used for antenna switching, wherein one of the three SRS resources has two SRS ports, and the other two of the three SRS resources have three SRS ports.

[0035] In some implementations of the above methods, UEs, and network entities, for 3T8R, a total of three SRS resources are configured in a set of up to three SRS resources used for antenna switching, wherein each of the three SRS resources has three SRS ports.

[0036] In some implementations of the above method, UE, and network entity, the UE sends information to the network entity indicating the capability to support 3-port PUSCH transmission.

[0037] In some implementations of the above method, UE, and network entity, the UE sends capability information to the network entity indicating that the maximum number of SRS ports is 3. Attached Figure Description

[0038] Figure 1 Examples of wireless communication systems in which some embodiments of the present disclosure may be implemented are illustrated.

[0039] Figure 2 Examples of processing flows for facilitating 3Tx PUSCH transmission are illustrated according to some exemplary embodiments of the present disclosure.

[0040] Figure 3 Examples of devices suitable for implementing some embodiments of the present disclosure are illustrated.

[0041] Figure 4 Examples of processors suitable for implementing some embodiments of the present disclosure are illustrated.

[0042] Figure 5 The diagram illustrates a flowchart of a method performed by a user equipment according to various aspects of this disclosure.

[0043] Figure 6 The diagram illustrates a flowchart of a method performed by a network entity according to various aspects of this disclosure.

[0044] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0045] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0046] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the described embodiments(s) may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same(s) embodiments(s). Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that incorporating other embodiments (whether explicitly described or not) to affect such feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0047] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, processes, or apparatus are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a selection can be made from a number of functional alternatives used, and that such selection is not necessarily better, smaller, higher, or more preferred than other selections.

[0048] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein are also intended to include the plural forms. It should also be understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including”, when used herein, specify the presence of the stated features, elements, components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and its variations should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can mean “only A” or “only B” or “both A and B.” Other explicit or implicit definitions are included below.

[0049] Embodiments of this disclosure relate to the problem of 3-antenna-port PUSCH transmission. In the Rel-19 Multiple-Input Multiple-Output (MIMO) Work Item Description (WID), it is agreed to specify an incoherent UL codebook to facilitate transmission based on the 3-antenna-port codebook without enhancing UL full-power transmission or SRS resources. To support 3-antenna-port (i.e., 3Tx) PUSCH transmission, several issues need to be addressed. For example, the design of the 3-port codebook and TPMI indication; the design of the 3-port SRS resources. Furthermore, the SRS used for antenna switching may also need to be enhanced.

[0050] In view of the above, a solution to address the aforementioned problems is proposed. According to embodiments of this disclosure, a user equipment (UE) can receive a configuration indicating PUSCH transmission based on a 3-port codebook from a network entity (e.g., a base station, such as a gNB). Based on the reception of this configuration, the UE can send a 3-port probe reference signal (SRS) to the network entity and receive a transmitted precoding matrix indicator (TPMI) indicating the 3-port precoder and layer number used for PUSCH transmission.

[0051] The aspects of this disclosure are described in the context of wireless communication systems. Figure 1An example of a wireless communication system 100 in which some embodiments of the present disclosure may be implemented is illustrated. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A advanced network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. Additionally, the wireless communication system 100 may support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0052] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more network entities among the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceivers, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface. In a 3GPP non-terrestrial network (NTN), network entity 102 in satellite form may communicate directly with UE 104 using an NR / LTE Uu interface. The satellite may be a transparent satellite or a regenerated satellite. For an NTN with transparent satellites, a base station on Earth may communicate with the UE via the satellite. For an NTN with regenerated satellites, the base station may be onboard and communicate directly with the UE.

[0053] Network entity 102 may provide a geographic coverage area 112 for which network entity 102 supports services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more wireless access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0054] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Alternatively or additionally, 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, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100. In some other implementations, UE 104 may be a UAV UE and may communicate with one or more network entities 102 while in flight.

[0055] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1 The diagram shows that UE 104 can communicate with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay equipment, integrated access and backhaul (IAB) node, or another network device). Figure 1 As shown. Alternatively or concurrently, UE 104 may support communication with other network entities 102 or UE 104 that may be used as relays in wireless communication system 100.

[0056] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication 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, communication link 114 may be referred to as a sidelink. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0057] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). 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)).

[0058] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or Virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0059] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in the decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in the decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0060] The functional splitting among CU, DU, and RU can be flexible and can depend on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are executed at the CU, DU, or RU to support different functions. For example, protocol stack functional splitting can be adopted between the CU and DU, allowing the CU to support one or more layers of the protocol stack, and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0061] Alternatively or concurrently, functional splitting of the protocol stack can be employed between the DU and RU, such that the DU can support one or more layers of the protocol stack, and the RU can support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, functional splitting between the CU and DU, or between the DU and RU, can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by different items in the CU, DU, or RU).

[0062] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul or fronthaul communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by corresponding network entities 102 communicating via such communication links.

[0063] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include a server 117 for performing location management functions (LMF), control plane entities for managing access and mobility (e.g., mobility management entity (MME), access and mobility management functions (AMF)), and user plane entities for routing packets or interconnects 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 bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0064] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0065] In the wireless communication system 100, network entity 102 and UE 104 can use the 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 communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more sets of parameters.

[0066] 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., 15kHz) and a normal cyclic prefix. In some implementations, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a normal cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60kHz) 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., 120kHz) and a normal cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a normal cyclic prefix.

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

[0068] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can 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, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 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 for 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 time slot may include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both regular and extended cyclic prefixes can depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and time slots.

[0069] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, along with other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, along with other devices or apparatuses, for short-range, high data rate capabilities.

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

[0071] Figure 2 The illustration shows an example of a processing flow for facilitating 3Tx PUSCH transmission according to some exemplary embodiments of the present disclosure. Processing flow 200 may involve a UE 201 and a network entity (e.g., a base station) 202. Processing flow 200 can be applied to reference... Figure 1 The wireless communication system 100, for example, UE 201 can be any of UE 104, and network entity 202 can be any of network entity 102. It should be understood that the processing flow 200 can be applied to other communication scenarios.

[0072] At 210, network entity 202 may send configuration 215 to UE 201 indicating PUSCH transmission based on a 3-port codebook. Correspondingly, at 220, UE 201 receives configuration 215. In this way, UE 201 is configured to perform PUSCH transmission to network entity 201 using a 3-port transmission (3Tx) based on a codebook precoding method. In some embodiments, when accessing a communication network, UE 201 may send capability information indicating support for 3-port PUSCH transmission to network entity 202. The network entity may send configuration 215 in response to the capability information.

[0073] At 230, UE 210 can send a 3-port probe reference signal (SRS) 235 to network entity 202. Correspondingly, at 240, network entity 202 can receive the 3-port SRS 235 from UE 201. Network entity 202 can measure the received 3-port SRS and determine the transmit precoding matrix indicator (TPMI) based on the measurement of the 3-port SRS. The TPMI can indicate the 3-port precoder and layer number used for PUSCH transmission.

[0074] At position 250, network entity 202 can send downlink control information (DCI) 255, which includes a TPMI field indicating the 3-port precoder and layer number used for PUSCH transmission. At position 250, network entity 202 can also send configuration authorization (i.e., CG) configuration 255, which includes a TPMI field indicating the 3-port precoder and layer number used for PUSCH transmission. PUSCH transmission can be dynamically scheduled by the DCI or periodically scheduled according to the RRC configuration. In some scenarios, such as in NR, the TPMI field may be referred to as precoding information and layer number field. Accordingly, at position 260, UE 201 can receive DCI 255 from network entity 202. In this way, UE 201 obtains the 3-port precoder for PUSCH transmission.

[0075] The implementation details of processing flow 200 will be described below.

[0076] Consider a codebook design for 3 Tx PUSCH transmission. The uplink (UL) codebook for UE 201 may include a set of precoding matrices, each with three rows corresponding to three antenna ports and one or more columns corresponding to one or more layers. For 3 Tx PUSCH transmission, the number of layers in the PUSCH transmission can be 1, 2, or 3.

[0077] In some embodiments, incoherent UL codebooks may be supported. In this case, each precoding matrix in the codebook may include only one non-zero element in each column. In other words, for each rank, there is only one non-zero element in each row of the codebook matrix. Examples of codebooks and 3-port precoders can be found in Tables 1 through 3 below. It should be understood that other codebooks and precoders are also applicable to 3Tx PUSCH transmissions. Table 1: Precoding matrix for single-layer transmission using three antenna ports W . Table 2: Precoding matrix for two-layer transmission using three antenna ports W . Table 3: Precoding matrix for three-layer transmission using three antenna ports W .

[0078] Consider the precoding information and layer number (i.e., the first TPMI) indication. It indicates the appropriate precoder for PUSCH transmission in the codebooks defined in Tables 1 to 3, and also indicates the actual number of layers for PUSCH transmission.

[0079] For PUSCH transmissions, if the maximum rank of the PUSCH transmission is greater than 1, Table 4 can be used to indicate the precoding information and the actual number of layers; if the maximum rank of the PUSCH transmission is 1, Table 5 can be used to indicate the precoding information and the actual number of layers. The maximum rank can be configured by the higher-level parameter maxRank. If a single-frequency network (SFN) scheme is configured for PUSCH transmissions, the maximum rank is max{maxRank, maxRankSfn}, while if a spatial division multiplexing (SDM) scheme is configured for PUSCH transmissions, the maximum rank is max{maxRank, maxRankSdm}. Table 4: Precoding information and layer number or second precoding information for 3 antenna ports. If the transform precoder is disabled, then maxRank = 2 or 3, or max{maxRank, maxRankSfn} = 2 or 3, or max{maxRank, maxRankSdm} = 2 or 3, or maxRankSdm = 2, and ul-FullPowerTransmission is not configured or configured to full power. Table 5: Precoding information and layer number or second precoding information for 3 antenna ports. If the transform precoder is enabled and ul-FullPowerTransmission is not configured or is configured to full power, or if the transform precoder is disabled, then maxRank=1, or max{maxRank, maxRankSfn}=1, or max{maxRank, maxRankSdm}=1, or maxRankSdm=1, or maxRankSfn=1, and ul-FullPowerTransmission is not configured or is configured to full power.

[0080] According to Table 4, for 3-antenna port PUSCH transmission, the TPMI field in DCI 255 or CG Configuration 255 can include 3 bits. txConfig = codebook ,but ul-FullPowerTransmission Not configured or configured as Full Power The transformation precoder is disabled, and depending on the value of the higher-level parameter, if multipanelScheme If not configured, then maxRank = 2 or 3 , or if multipanelScheme = sfnScheme Then max{ maxRank , maxRankSfn} = 2 or 3, or if multipanelScheme = sdmScheme ,as well as codebookSubsetThen max{ maxRank , maxRankSdm}=2.

[0081] According to Table 5, for 3-antenna port PUSCH transmission, the TPMI field in DCI 255 or CG Configuration 255 can include 2 bits, if txConfig = codebook ,but ul-FullPowerTransmission Not configured or configured as Full Power And depending on whether the transform precoder is enabled or disabled, if multipanelScheme If not configured, then maxRank = 1 , or if multipanelScheme = sfnScheme Then max{ maxRank , maxRankSfn}=1, or if multipanelScheme = sdmScheme ,as well as codebookSubset Then max{ maxRank , maxRankSdm}=1.

[0082] In some scenarios, such as for multi-TRP (Transmitter Receiver) transmissions, when two SRS resource sets used for codebooks are configured, the DCI 255 may also include a second TPMI field indicating a second 3-port precoder and a second layer number for PUSCH transmissions. In some embodiments, if an SFN or TDM scheme is configured for PUSCH transmissions, the actual layer number is the same as the layer number indicated by the first TPMI. In this case, Tables 6 and 5 below are used to indicate precoders with a maximum rank greater than 1 and a maximum rank of 1, respectively. Table 6: Second precoding information for 3 antenna ports, where maxRank = 2 or 3 if the transform precoder is disabled, or maxRankSfn = 2, and ul-FullPowerTransmission is not configured or configured to full power.

[0083] According to Table 6, the second TPMI field may include 2 bits, having the same layer number as indicated by the precoding information and layer number segment for 3-antenna port PUSCH transmission, if the SRS resource set indicator field is present. txConfig = codebook , ul-FullPowerTransmission Not configured or configured as Full Power The transformation precoder is disabled, and depending on the value of the higher-level parameter, if multipanelScheme If not configured, then maxRank = 2 or 3 , or if multipanelScheme = sfnScheme ,as well as codebookSubset ,but maxRankSfn =2.

[0084] According to Table 5, the second TPMI field may include 2 bits, having the same layer number as indicated by the precoding information and layer number segment for 3-antenna port PUSCH transmission, if the SRS resource set indicator field is present. txConfig = codebook , ul-FullPowerTransmission Not configured or configured as Full Power And depending on whether the transformation precoder is enabled or disabled, and the value of the higher-level parameters, if multipanelScheme If not configured, then maxRank = 1 , or if multipanelScheme = sfnScheme ,as well as codebookSubset ,but maxRankSfn = 1 .

[0085] If the SDM scheme is configured for PUSCH transmission, then Tables 4 and 5 can be used to indicate precoders for maximum rank greater than 1 and maximum rank of 1, respectively.

[0086] According to Table 4, the second TPMI field may include 3 bits for PUSCH transmission on the 3-antenna port. txConfig = codebook ,but ul-FullPowerTransmission Not configured or configured as Full Power The transformation precoder is disabled, and depending on the value of the higher-level parameter, if multipanelScheme = sdmScheme ,as well as codebookSubset ,but maxRankSdm = 2 .

[0087] According to Table 5, the second TPMI field may include 2 bits for PUSCH transmission on the 3-antenna port. txConfig = codebook ,but ul-FullPowerTransmission Not configured or configured as Full Power And depending on whether the transformation precoder is enabled or disabled, and the value of the higher-level parameters, if multipanelScheme = sdmScheme ,as well as codebookSubset ,but maxRankSdm = 1 .

[0088] Next, consider the generation of SRS sequences for 3-port SRS resources. The SRS sequence for each port of a multi-port SRS resource can be generated from ZC sequences with different cyclic shifts (CS). For 4-port and 8-port SRS resources, different halves of the total ports can occupy different combs (i.e., resource elements RE), and ports within a half of a port are orthogonal through different CS. According to standard TS38.211, the SRS sequence is generated as follows: For antenna port Circular shift Given as (1) in (2) in Included in higher-level parameters transmissionComb In the middle, and =0, 1, ... . It is the number of antenna ports. nrofSRS-Ports Table 7 shows the maximum number of cyclic shifts. , K TC It is the value of the comb. quantity and By giving the following - If higher level parameters nrofSRS-Ports-n8 equal ports8tdm - Otherwise Table 7: As K TC The maximum number of circular shifts of the function .

[0089] For formula (2), the CS of the 3-port SRS resource can be based on the second parameter. To determine, and The value is based on a first parameter indicating the number of antenna ports of the SRS resource. To determine. First parameter. This can be configured by the network, and the second parameter is used as an intermediate quantity when determining the CS of the SRS resource. An example for calculating the CS of a 3-port SRS resource is provided below.

[0090] In some embodiments, the CS of the 3-port SRS resource can be obtained through formula (2). To determine. In this embodiment, the number of antenna ports is nrofSRS-Ports (i.e., ) is configured as 3, and Used to determine the CS of the 3-port SRS resource, i.e. The SRS port is ,and Therefore, for K TCThe CS values ​​for the SRS resources on ports 2, 4, 8, and 3 are as follows: · ; , ; · ; , ; · ; , .

[0091] However, for the number of transmission combs K TC =2, based on formula (2). It will not return an integer. To solve this problem, one approach is to... Perform a round-down or round-up operation. Alternatively, another method is that 3-port SRS resources and a comb count of 2 cannot be configured simultaneously. That is, when the number of antenna ports... nrofSRS-Ports ( When configured as 3, the UE does not expect comb values. K TC It is configured as 2.

[0092] When the first parameter is configured as 3, the UE can use the second parameter. The CS is calculated using formula (2). This means that the calculation of the CS for a 3-port SRS resource is similar to the calculation of the CS for a 4-port SRS resource as defined in TS 38.211. The only difference is the first parameter. nrofSRS-Ports It is configured as 3 because the number of SRS ports is 3 (i.e., In this embodiment, three CSs are determined, where the SRS port of the 3-port SRS resource is... ,and .

[0093] Alternative location, first parameter nrofSRS-Ports It can be configured to 4. In this embodiment, the UE can still use the second parameter. The CS is calculated using formula (2). The CS of a 3-port SRS resource is determined to be the same as that of a 4-port SRS resource, i.e., the number of antenna ports. nrofSRS-Ports It is configured to 4, and CS calculation is based on . With the previous first parameter nrofSRS-Ports The method of equaling 3 is different. In this embodiment, the first parameter... nrofSRS-PortsIt is configured as 4, and four CSs are determined. Since only three ports are used for SRS transmission, the first three CSs out of the total four CSs for 4-port SRS are used to generate sequences for 3-port SRS resources. That is, if configured for 3 Tx PUSCH transmission, and the first parameter... nrofSRS-Ports If configured as 4, then the SRS port for the 3-port SRS resource is... ,and In other words, the UE should only send the first three ports of the SRS resource, even if It is configured as 4.

[0094] This embodiment is consistent with formula (2) in TS 38.211, but several minor issues require corresponding updates. One of these issues concerns SRS transmission power. In TS 38.211, when the SRS sequence of an SRS resource is mapped to a physical resource, the sequence for each antenna port of the SRS resource is determined according to the following formula. It should be multiplied by the amplitude scaling factor. To comply with the transmission power specified in [TS 38.213]. (3) In this embodiment, the first parameter nrofSRS-Ports It is configured as 4, that is, And the actual number of SRS ports is 3. Therefore, if configured for 3 Tx PUSCH transmission, but nrofSRS-Ports If configured as 4, then the UE applies formula (3) In other words, the coefficients in formula (3) should indicate the actual number of antenna ports, i.e., three ports.

[0095] Similarly, in TS 38.213, the specification states that "for SRS, the UE shall equally allocate the serving cell on the antenna ports configured for SRS". c The activity of carrier wave 𝑓 UL BWP b On the transmission power linear value "If configured for 3 Tx PUSCH transmission, and although the configuration antenna ports for SRS are set to 4, the UE should distribute the linearity equally across the 3 antenna ports for SRS." .

[0096] Another issue concerns the determination of the precoder for PUSCH transmission. TS 38.214 specifies that "the transmission precoder is selected from the uplink codebook, which has parameters equal to the higher-layer parameters in the SRS-Config." nrofSRS- PortsThe number of antenna ports, as defined in Clause 6.3.1.5 of [4, TS 38.211]. The precoder for PUSCH transmission is based on the configured number of SRS ports. nrofSRS-Ports To determine this, if 3 Tx is configured for PUSCH transmission, the precoder should be selected from the uplink codebooks defined in Tables 1 to 3, which have an antenna port count equal to 3, rather than the configured SRS port count. nrofSRS-Ports .

[0097] To better understand, an example of CS calculation for a 3-port SRS resource is provided. It is assumed to be configured for 3 TxPUSCH transports, and the comb count is configured to 2. If... nrofSRS-Ports Configured to 3 and If the method equal to 4 is adopted, then identified as (4) in ,and i =0, 1, ... Therefore, the three CSs of a 3-port SRS are .

[0098] if nrofSRS-Ports Configured to 4 and If the method equal to 4 is adopted, then Similar to formula (4), the four CS are However, this is for 3TxPUSCH transmissions; only three CS are needed for 3-port SRS resources. Then, for simplicity, the first three CS values ​​are used, i.e. ,and i =0, 1, ... .

[0099] Now consider SRS for antenna switching. Multiple SRS resources for antenna switching are used to acquire DLCSI. Additional antenna switching configurations can be supported depending on the UE's capabilities by introducing three antenna ports for UL transmission. In some embodiments, the UE can transmit SRS resources for antenna switching, where, depending on the UE's capabilities, the SRS transmit port supported by antenna switching is switched to one of 1T3R, 2T3R, 3T3R, 3T4R, 3T6R, and 3T8R.

[0100] For 1T3R, a total of three SRS resources in up to three SRS resource sets are configured with the purpose of 'antennaSwitching'. Each SRS resource in a given set consists of one SRS port, and the SRS ports of the SRS resources in this set are associated with different UE antenna ports. In some embodiments, the three SRS resources are configured in one SRS resource set. In some embodiments, the three SRS resources are configured in two SRS resource sets, where one SRS resource set includes one SRS resource and the other SRS resource set includes two SRS resources. In some embodiments, the three SRS resources are configured in three SRS resource sets, where each SRS resource set includes one SRS resource. For 3T6R, a total of two SRS resources in up to two SRS resource sets are configured with the purpose of 'antennaSwitching'. Each SRS resource in a given set consists of three SRS ports, and the SRS port pairs of the SRS resources in this set are associated with different UE antenna port pairs. For 3T3R, an SRS resource in an SRS resource set is configured with the purpose set to 'antennaSwitching', each SRS resource set has one SRS resource, and the number of SRS ports for each resource is equal to 3.

[0101] For 2T3R, in order to detect the 3-port DL channel between the gNB and the UE, a total of two SRS resources can be configured in up to two SRS resource sets used for antenna switching.

[0102] In some embodiments, one SRS resource has two SRS ports, and another SRS resource has a single SRS port. Therefore, one port of the 3-port DL channel is probed by the single-port SRS resource, and the other two ports of the 3-port DL channel are probed by the two-port SRS resources.

[0103] Zero or one 'periodic' SRS resource set can be configured. If the UE does not indicate srs-AntennaSwitching2SP-1Periodic, zero or one 'semi-persistent' SRS resource set can be configured; or if the UE indicates srs-AntennaSwitching2SP-1Periodic, up to two 'semi-persistent' SRS resource sets and up to one 'periodic' SRS resource set can be configured. Two 'semi-persistent' SRS resource sets cannot be active simultaneously. Each 'periodic' or 'semi-persistent' SRS resource set has two SRS resources transmitted in different symbols, one SRS resource consisting of a single SRS port and the other SRS resource consisting of two SRS ports. The SRS ports of the SRS resources in a given set are associated with different UE antenna ports.

[0104] Zero, one, or two 'aperiodic' SRS resource sets can be configured. In the case of one SRS resource set, two SRS resources are included and transmitted in different symbols, one SRS resource consisting of a single SRS port and the other consisting of two SRS ports. The SRS ports of the two SRS resources are associated with different UE antenna ports. In the case of two SRS resource sets, a total of two SRS resources are transmitted in different symbols in two different time slots. One SRS resource set includes single-port SRS resources, and the other set includes two-port SRS resources. The SRS ports of the two SRS resources are associated with different UE antenna ports.

[0105] Alternatively, for 2T3R, each SRS resource can have two SRS ports. Therefore, a 3-port DL channel is probed by two 2-port SRS resources, and one port of the 3-port DL channel can be probed twice. For example, DL ports 0 and 1 are probed by the first SRS resource; and DL ports 1 and 2 are probed by the second SRS resource.

[0106] In this embodiment, similar to the case where one SRS resource has one port and the other has two ports, zero or one 'periodic' SRS resource set or up to two 'semi-persistent' SRS resource sets can be configured. Each 'periodic' or 'semi-persistent' SRS resource set has two SRS resources transmitted in different symbols, where each SRS resource consists of two SRS ports. The SRS port pairs of SRS resources in a given set are associated with different UE antenna port pairs.

[0107] Zero, one, or two 'aperiodic' SRS resource sets can be configured. In the case of a single SRS resource set, two SRS resources are included and transmitted in different symbols, with one SRS resource consisting of two SRS ports. In the case of two SRS resource sets, a total of two SRS resources are voluntarily transmitted in different symbols in two different time slots, with one SRS resource consisting of two SRS ports. The SRS port pairs of SRS resources in a given set are associated with different UE antenna port pairs.

[0108] For 3T4R, in order to probe the 4-port DL channel between the gNB and the UE, a total of two SRS resources can be configured in at most two SRS resource sets used for antenna switching. In some embodiments, one of the two SRS resources has three SRS ports, and the other SRS resource has a single SRS port.

[0109] In 2T3R, for example, zero or one 'periodic' SRS resource set or up to two 'semi-persistent' SRS resource sets can be configured. Each 'periodic' or 'semi-persistent' SRS resource set has two SRS resources transmitted in different symbols, one of which consists of a single SRS port and the other consists of three SRS ports. The SRS ports of the SRS resources in a given set are associated with different UE antenna ports.

[0110] Zero, one, or two 'aperiodic' SRS resource sets can be configured. In the case of one SRS resource set, two SRS resources are included and transmitted in different symbols; one SRS resource consists of a single SRS port, and the other consists of three SRS ports. In the case of two SRS resource sets, a total of two SRS resources are transmitted in different symbols in two different time slots. One SRS resource set includes a single-port SRS resource, and the other set includes a 3-port SRS resource. The SRS ports of the two SRS resources are associated with different UE antenna ports.

[0111] For 3T4R, alternatively, each SRS resource can have three SRS ports. Therefore, a 4-port DL channel is probed by two 3-port SRS resources, and two ports of the 4-port DL channel can be probed twice. For example, DL port 0, DL port 1, and port 2 are probed by the first SRS resource; and DL ports 1 through 3 are probed by the second SRS resource.

[0112] In 2T3R, for example, zero or one 'periodic' SRS resource set or up to two 'semi-persistent' SRS resource sets can be configured. Each 'periodic' or 'semi-persistent' SRS resource set has two SRS resources transmitted in different symbols, one of which consists of three SRS ports. The SRS port pairs of the resources in this set are associated with different UE antenna port pairs.

[0113] Zero, one, or two 'aperiodic' SRS resource sets can be configured. In the case of a single SRS resource set, two SRS resources are included and transmitted in different symbols, with one SRS resource consisting of three SRS ports. In the case of two SRS resource sets, a total of two SRS resources are transmitted in different symbols in two different time slots. An SRS resource set includes 3-port SRS resources. The SRS port pairs of the two SRS resources are associated with different UE antenna port pairs.

[0114] For 3T8R, in order to probe the 8-port DL channel between the gNB and the UE, a total of three SRS resources are configured in a set of up to three SRS resources used for antenna switching. In some embodiments, one of the three SRS resources may have two SRS ports, and the other two SRS resources may have three SRS ports.

[0115] In 2T3R, for example, zero or one 'periodic' SRS resource set or up to two 'semi-persistent' SRS resource sets can be configured. Each 'periodic' or 'semi-persistent' SRS resource set has three SRS resources transmitted in different symbols, one of which consists of two SRS ports, and the other two SRS resources consist of three SRS ports. The SRS port pairs of the SRS resources in a given set are associated with different UE antenna port pairs.

[0116] Zero, one, two, or three 'aperiodic' SRS resource sets can be configured. In the case of one SRS resource set, three SRS resources are included and transmitted in different symbols, one SRS resource consisting of two SRS ports and the other two SRS resources consisting of three SRS ports. In the case of two SRS resource sets, a total of three SRS resources are transmitted in different symbols in two different time slots. One SRS resource set includes one SRS resource, and another SRS resource set includes two SRS resources. One SRS resource has two SRS ports, and the other two SRS resources have three SRS ports. In the case of three SRS resource sets, a total of three SRS resources are transmitted in different symbols in three different time slots. One SRS resource set includes one SRS resource. One SRS resource has two SRS ports, and the other two SRS resources have three SRS ports. The SRS ports of the three SRS resources are associated with different UE antenna ports.

[0117] For 3T8R, alternatively, each of the three SRS resources can have three ports. Therefore, an 8-port DL channel is probed by three 3-port SRS resources, and one port of the 8-port DL channel can be probed twice. For example, DL ports 0, 1, and 2 are probed by the first SRS resource; DL ports 3 through 5 are probed by the second SRS resource; and DL ports 5 through 7 are probed by the third SRS resource.

[0118] In 2T3R, for example, zero or one 'periodic' SRS resource set or up to two 'semi-persistent' SRS resource sets can be configured. Each 'periodic' or 'semi-persistent' SRS resource set has three SRS resources transmitted in different symbols, one of which consists of three SRS ports. The SRS port pairs of the resources in this set are associated with different UE antenna port pairs.

[0119] Zero, one, two, or three 'aperiodic' SRS resource sets can be configured. In the case of one SRS resource set, three SRS resources are included and transmitted in different symbols, with one SRS resource consisting of three SRS ports. In the case of two SRS resource sets, a total of three SRS resources are transmitted in different symbols in two different time slots. One SRS resource set includes one SRS resource, and another SRS resource set includes two SRS resources. In the case of three SRS resource sets, a total of three SRS resources are transmitted in different symbols in three different time slots. One SRS resource set includes one SRS resource. The SRS port pairs of the three SRS resources are associated with different UE antenna port pairs.

[0120] UE 201 can send capability information to network entity 202 indicating that the maximum number of SRS ports is 3. For UEs equipped with multiple panels (MP-UE), 2-bit UE capabilities can be used, and each capability value corresponds to the maximum number of SRS ports on the panel, which can be 1, 2, 3, or 4. UE capabilities can be reported together with beamforming to indicate to network entity 202 whether corresponding scheduling information should be changed, such as precoder and layer number. In some embodiments, if UE 201 supports 3Tx PUSCH transmission, then capability value 3 should be introduced for UEs equipped with multiple panels. An example of UE capability enhancement for MP-UEs is shown below. -- R1 23-1-4 UE Capability Value Report srs-PortReport-r19 SEQUENCE { capVal1-r19 ENUMERATED {n1, n2,n3, n4} OPTIONAL, capVal2-r19 ENUMERATED {n1, n2,n3, n4} OPTIONAL, capVal3-r19 ENUMERATED {n1, n2,n3, n4} OPTIONAL, capVal4-r19 ENUMERATED {n1, n2,n3, n4} OPTIONAL }

[0121] Furthermore, the Phase Tracking Reference Signal (PT-RS) issue needs to be considered. In some scenarios, one or two PTRS ports can be configured for the UE. The actual number of (multiple) UL PT-RS ports can be determined based on the indicated / configured (multiple) TPMIs. If the maximum number of PTRS ports is configured to 1, all three PUSCH antenna ports share a single PTRS port; if the maximum number of PTRS ports is configured to 2, how to associate the PUSCH antenna ports with the PTRS ports needs to be determined.

[0122] In some embodiments, the association between the PUSCH antenna port and the PTRS port can be fixed. For example, PUSCH antenna ports 1000 and 1002 in the indicated TPMI(s) can share PTRS port 0, and PUSCH antenna port 1001 in the indicated TPDI(s) can share PTRS port 1. For example, if the indicated TPMI is If PUSCH antenna ports 1000 and 1001 share different PTRS ports, then the actual number of PTRS ports is 2; if the indicated TPMI is Therefore, PUSCH antenna ports 1000 and 1002 share the same PTRS port, so the actual number of PTRS ports is 1.

[0123] In some embodiments, the association between PUSCH antenna ports and PTRS ports is UE-specific. Since only two PTRS ports are supported, in a 3 Tx PUSCH transmission, two PUSCH antenna ports may share one PTRS port, and one PUSCH antenna port may share another PTRS port. Which two PUSCH antenna ports share the PTRS port is determined by the UE based on its hardware implementation, and the UE may report this to the gNB. The gNB can then instruct the appropriate precoder for the PUSCH transmission. For example, one UE may report that PUSCH antenna ports 1000 and 10001 share PTRS port 0, and PUSCH antenna port 1002 shares PTRS port 1; another UE may report that PUSCH antenna ports 1000 and 10002 share PTRS port 0, and PUSCH antenna port 1001 shares PTRS port 1.

[0124] In PTRS and DMRS associations, if the maximum number of PTRS ports is configured to 1, then two bits in Table 8 (reproduced from Table 7.3.1.1.2-25 in TS 38.212) are used to indicate which DMRS port a PTRS port is associated with. If the maximum number of PTRS ports is configured to 2, then one bit is sufficient to indicate the association in Table 9. Since in 3TxPUSCH transmissions, up to two PUSCH layers share a PTRS port, and one PUSCH layer shares another PTRS port, Table 9 can be used to indicate PTRS-DMRS associations if the number of PUSCH layers associated with a PTRS port is 2; and if the number of PUSCH layers associated with a PTRS port is 1, then a DMRS port is definitely associated with a PTRS port without needing to be indicated. Table 8: PTRS-DMRS Association for UL PTRS Port 0 Table 9: PTRS-DMRS Association for UL PTRS Port 0 or PTRS Port 1

[0125] Figure 3Examples of devices suitable for implementing some embodiments of this disclosure are illustrated. Device 300 may be an example of UE 104 or network entity 102 as described herein. Device 300 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 300 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 302, memory 304, transceiver 306, and optional I / O controller 308). These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0126] Processor 302, memory 304, transceiver 306, or various combinations thereof or various components thereof may be examples of components used to perform the various aspects of this disclosure described herein. For example, processor 302, memory 304, transceiver 306, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0127] In some implementations, processor 302, memory 304, transceiver 306, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 302 and memory 304 coupled to processor 302 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 304 by processor 302).

[0128] For example, according to the examples disclosed herein, processor 302 may support wireless communication at device 300. Device 300 may be an example of UE 104. In this case, processor 302 may be configured to operate to support: components for receiving from a network entity a configuration indicating physical uplink shared channel (PUSCH) transmission based on a 3-port codebook; components for transmitting a 3-port probe reference signal (SRS) to the network entity based on the reception of the configuration; and components for receiving downlink control information (DCI) from the network entity, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating the 3-port precoder and layer number for PUSCH transmission.

[0129] Device 300 may be an example of network entity 102, such as a network entity. In this case, processor 302 may be configured to support: components for sending to a user equipment (UE) a configuration indicating physical uplink shared channel (PUSCH) transmission based on a 3-port codebook; components for receiving a 3-port probe reference signal (SRS) from the UE; and components for sending downlink control information (DCI) to the UE, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating the 3-port precoder and layer number used for PUSCH transmission.

[0130] Processor 302 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 302 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 302. Processor 302 may be configured to execute computer-readable instructions stored in memory (e.g., memory 304) to cause device 300 to perform various functions of this disclosure.

[0131] Memory 304 may include random access memory (RAM) and read-only memory (ROM). Memory 304 may store computer-readable, computer-executable code, including instructions that, when executed by processor 302, cause device 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. In some implementations, the code may not be directly executed by processor 302, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 304 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0132] I / O controller 308 can manage input and output signals for device 300. I / O controller 308 can also manage peripheral devices not integrated into device 300. In some implementations, I / O controller 308 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 308 can utilize an operating system such as iOS®, Android®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 308 can be implemented as part of a processor, such as processor 302. In some implementations, a user can interact with device 300 via I / O controller 308 or via hardware components controlled by I / O controller 308.

[0133] In some implementations, device 300 may include a single antenna 310. However, in other implementations, device 300 may have more than one antenna 310 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 306 may communicate bidirectionally via one or more antennas 310, wired, or wireless links, as described herein. For example, transceiver 306 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 306 may also include a modem for modulating packets, providing modulated packets to one or more antennas 310 for transmission, and demodulating packets received from one or more antennas 310. Transceiver 306 may include one or more transmit chains, one or more receive chains, or combinations thereof.

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

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

[0136] Figure 4 An example of a processor 400 suitable for implementing some embodiments of the present disclosure is illustrated. Processor 400 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 400 may include a controller 402 configured to perform various operations according to the examples described herein. Processor 400 may optionally include at least one memory 404. Additionally or alternatively, processor 400 may optionally include one or more arithmetic logic units (ALUs) 406. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0137] Processor 400 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to the processor chipset (e.g., processor 400) or included in the processor chipset) 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), etc.).

[0138] Controller 402 can be configured to manage and coordinate various operations of processor 400 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 400 to support various operations according to the examples described herein. For example, controller 402 can operate as a control unit of processor 400 to generate control signals that manage the operation of various components of processor 400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0139] Controller 402 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 404 and determine subsequent instructions(s) to be executed, enabling processor 400 to support various operations according to the examples described herein. Controller 402 may be configured to track the memory addresses of instructions associated with memory 404. Controller 402 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 402 may be configured to interpret instructions and determine control signals to be output to other components of processor 400, enabling processor 400 to support various operations according to the examples described herein. Additionally or alternatively, controller 402 may be configured to manage data flow within processor 400. Controller 402 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 400.

[0140] Memory 404 may include one or more caches (e.g., memory or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc., local to or included in processor 400). In some implementations, memory 404 may reside within or on the processor chipset (e.g., local to processor 400). In some other implementations, memory 404 may reside outside the processor chipset (e.g., remote from processor 400).

[0141] Memory 404 may store computer-readable, computer-executable code, including instructions that, when executed by processor 400, cause processor 400 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. Controller 402 and / or processor 400 may be configured to execute the computer-readable instructions stored in memory 404 to cause processor 400 to perform various functions. For example, processor 400 and / or controller 402 may be coupled to or coupled to memory 404, and processor 400, controller 402, and memory 404 may be configured to perform the various functions described herein. In some examples, processor 400 may include multiple processors, and memory 404 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.

[0142] One or more ALUs 406 can be configured to support various operations according to the examples described herein. In some implementations, one or more ALUs 406 may reside within or on a processor chipset (e.g., processor 400). In some other implementations, one or more ALUs 406 may reside outside the processor chipset (e.g., processor 400). One or more ALUs 406 can perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 406 can receive input operands and an opcode that determines the operation to be performed. One or more ALUs 406 are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALUs 406 can support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALUs 406 to handle conditional operations, comparisons, and bitwise operations.

[0143] Based on the examples disclosed herein, processor 400 can support wireless communication. Processor 400 can be implemented at UE 104. In this case, processor 400 can be configured to operate to support: components for receiving from a network entity a configuration indicating physical uplink shared channel (PUSCH) transmission based on a 3-port codebook; components for transmitting a 3-port probe reference signal (SRS) to the network entity based on the reception of the configuration; and components for receiving downlink control information (DCI) from the network entity, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating the 3-port precoder and layer number used for PUSCH transmission.

[0144] Processor 400 may be implemented at network entity 102 (e.g., base station). In this case, processor 400 may be configured to support: components for sending to user equipment (UE) a configuration indicating physical uplink shared channel (PUSCH) transmission based on a 3-port codebook; components for receiving a 3-port probe reference signal (SRS) from the UE; and components for sending downlink control information (DCI) to the UE, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating the 3-port precoder and layer number for PUSCH transmission.

[0145] Figure 5 A flowchart illustrating a method 500 performed by a UE according to various aspects of this disclosure is shown. The operation of method 500 may be implemented by the device or components thereof described herein. For example, the operation of method 500 may be performed by the UE 104 described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device may use dedicated hardware to perform aspects of the described functions.

[0146] At 510, the method may include: receiving from a network entity a configuration indicating Physical Uplink Shared Channel (PUSCH) transmission based on a 3-port codebook. The operation of 510 can be performed according to the examples described herein. In some implementations, aspects of the operation of 510 can be derived from references... Figure 1 The aforementioned UE 104 is executed.

[0147] At 520, the method may include: sending a 3-port probe reference signal (SRS) to the network entity based on the received configuration. The operation of 520 can be performed according to the examples described herein. In some implementations, aspects of the operation of 520 may be derived from a reference... Figure 1 The aforementioned UE 104 is executed.

[0148] At 530, the method may include: receiving downlink control information (DCI) from a network entity, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating the 3-port precoder and layer number used for PUSCH transmission. The operation of 530 can be performed according to the examples described herein. In some implementations, aspects of the operation of 530 may be derived from references... Figure 1 The aforementioned UE 104 is executed.

[0149] Figure 6 A flowchart illustrating a method 600 performed by a network entity according to various aspects of this disclosure is shown. Operation of method 600 may be implemented by the device or components thereof described herein. For example, operation of method 600 may be performed by network entity 102 described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device may use dedicated hardware to perform aspects of the described functions.

[0150] At 610, the method may include sending a configuration to the user equipment (UE) indicating physical uplink shared channel (PUSCH) transmission based on a 3-port codebook. The operation of 610 can be performed according to the examples described herein. In some implementations, aspects of the operation of 610 may be derived from references... Figure 1 The network entity 102 is executed.

[0151] At 620, the method may include receiving a 3-port probe reference signal (SRS) from the UE. The operation of 620 can be performed according to the examples described herein. In some implementations, aspects of the operation of 620 may be derived from a reference... Figure 1 The network entity 102 is executed.

[0152] At 630, the method may include: sending downlink control information (DCI) to the UE, the DCI including a transmitted precoding matrix indicator (TPMI) field indicating the 3-port precoder and layer number used for PUSCH transmission. The operation of 630 can be performed according to the examples described herein. In some implementations, aspects of the operation of 630 may be derived from references... Figure 1 The network entity 102 is executed.

[0153] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0154] The various illustrated boxes and components disclosed herein can be implemented or performed using the following items designed to perform the functions described herein: general-purpose processors, DSPs, ASICs, CPUs, FPGAs or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0155] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of the foregoing. Features implementing the functions may also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0156] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0157] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the “or” used in a list of items (e.g., a list of items beginning with phrases 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 construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” could 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 interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0158] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: Receive configuration instructions from network entities for Physical Uplink Shared Channel (PUSCH) transmission based on a 3-port codebook; Based on the received configuration, a 3-port probe reference signal (SRS) is sent to the network entity. as well as Downlink control information (DCI) is received from the network entity, the DCI including a transmitted precoding matrix indicator (TPMI) field, the TPMI field indicating the 3-port precoder and layer number used for the PUSCH transmission.

2. The UE of claim 1, wherein the 3-port precoder is selected from a set of precoding matrices, and wherein each precoding matrix has three rows and one or more columns corresponding to one or more layers; and each precoding matrix includes only one non-zero element in each column.

3. The UE according to claim 1, wherein If the maximum rank of the PUSCH transmission is greater than 1, the TPMI field includes three bits indicating the 3-port precoder used for the PUSCH transmission and the layer number; or When the maximum rank of the PUSCH transmission is 1, the TPMI field includes two bits indicating the 3-port precoder used for the PUSCH transmission and the layer number.

4. The UE of claim 1, wherein when two SRS resource sets used as codebooks are configured, the DCI further includes a second TPMI field, the second TPMI field indicating a second 3-port precoder and a second layer number for the PUSCH transmission.

5. The UE of claim 4, wherein when a single-frequency network (SFN) scheme or a time-division multiplexing (TDM) scheme is configured for the PUSCH transmission, If the maximum rank of the PUSCH transmission is greater than 1, then the second TPMI field includes two bits indicating the second 3-port precoder and the same number of layers as indicated by the first TPMI field, or If the maximum rank of the PUSCH transmission is equal to 1, then the second TPMI field includes two bits indicating the second 3-port precoder and the second layer number used for the PUSCH transmission.

6. The UE of claim 4, wherein when a spatial division multiplexing (SDM) scheme is configured for the PUSCH transmission, If the maximum rank of the PUSCH transmission is greater than 1, then the second TPMI field includes three bits indicating the second 3-port precoder and the second layer number used for the PUSCH transmission; or If the maximum rank of the PUSCH transmission is 1, then the second TPMI field includes two bits indicating the second 3-port precoder and the second layer number used for the PUSCH transmission.

7. The UE of claim 1, wherein the first parameter indicating the number of antenna ports of SRS resources It is configured as 3, and the second parameter is used when determining the cyclic shift (CS) of the 3-port SRS resource. The value is 3.

8. The UE according to claim 7, wherein the processor is further configured to: In transmission comb number K TC If the value is equal to 2, perform a round-down or round-up operation to obtain the CS of the 3-port SRS resource.

9. The UE according to claim 7, wherein the number of transmission combs K TC Equal to 2 and the first parameter The value 3 cannot be configured simultaneously.

10. The UE of claim 1, wherein the first parameter indicating the number of antenna ports of SRS resources It is configured as 3, and the second parameter is used when determining the CS of the 3-port SRS resource. The value is 4.

11. The UE according to claim 1, wherein the first parameter The second parameter is configured as 4, and is used when determining the CS of the 3-port SRS resource. It is 4, and among them, Of the four CSs obtained, the first three CSs are the CSs of the 3-port SRS resource.

12. The UE of claim 11, wherein the SRS sequence of the SRS resource is mapped to physical resources having a coefficient indicating the number of antenna ports equal to 3, and the processor is further configured to: Linear transmission power is evenly distributed across the three antenna ports used for SRS transmission; and / or Select a precoder from the uplink codebook with 3 antenna ports.

13. The UE of claim 1, wherein the processor is further configured to transmit SRS resources for antenna switching, wherein, depending on the capabilities of the UE, the antenna switching supports an SRS transmit port switching of one of 1T3R, 2T3R, 3T3R, 3T4R, 3T6R, and 3T8R.

14. The UE according to claim 13, wherein, For 2T3R, in at most two SRS resource sets used for antenna switching, a total of two SRS resources are configured, of which One SRS resource has two SRS ports, and another SRS resource has a single SRS port; or alternatively... Each SRS resource has two SRS ports.

15. The UE according to claim 13, wherein, For 3T4R, in at most two SRS resource sets used for antenna switching, a total of two SRS resources are configured, of which One SRS resource has three SRS ports, and another SRS resource has a single SRS port; or alternatively... Each SRS resource has three SRS ports.

16. The UE according to claim 13, wherein, For 3T8R, in a maximum of three SRS resource sets used for antenna switching, a total of three SRS resources are configured, of which One of the three SRS resources has two SRS ports, and the other two SRS resources have three SRS ports; or alternatively... Each of the three SRS resources has three SRS ports.

17. The UE of claim 1, wherein the processor is configured to send capability information to the network entity indicating that the maximum number of SRS ports is 3.

18. A network entity, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: Send a configuration indicating the Physical Uplink Shared Channel (PUSCH) transmission based on the 3-port codebook to the User Equipment (UE); Receive a 3-port probe reference signal (SRS) from the UE. as well as Downlink control information (DCI) is sent to the UE, the DCI including a transmitted precoding matrix indicator (TPMI) field, the TPMI field indicating the 3-port precoder and layer number used for the PUSCH transmission.

19. A method performed by a user equipment (UE), the method comprising: Receive configuration instructions from network entities for Physical Uplink Shared Channel (PUSCH) transmission based on a 3-port codebook; Based on the received configuration, a 3-port probe reference signal (SRS) is sent to the network entity. as well as Downlink control information (DCI) is received from the network entity, the DCI including a transmitted precoding matrix indicator (TPMI) field, the TPMI field indicating the 3-port precoder and layer number used for the PUSCH transmission.

20. A method performed by a network entity, the method comprising: Send a configuration indicating the Physical Uplink Shared Channel (PUSCH) transmission based on the 3-port codebook to the User Equipment (UE); Receive a 3-port probe reference signal (SRS) from the UE. as well as Downlink control information (DCI) is sent to the UE, the DCI including a transmitted precoding matrix indicator (TPMI) field, the TPMI field indicating the 3-port precoder and layer number used for the PUSCH transmission.

Images