Codebook-based PUSCH transmission using eight antenna ports and up to eight transmission layers

Abstract

A user equipment (UE) configured for operation in a fifth-generation new radio (5G NR) network may be configured with a codebook type for codebook-based physical uplink shared channel (PUSCH) transmission using eight antenna ports and up to eight transmission layers. The codebook type may have a coherency indication that may indicate one of a fully coherent codebook type, a partially coherent codebook type, and a noncoherent codebook type. A downlink control information (DCI) format scheduling codebook-based PUSCH transmission using eight antenna ports may indicate a transmit precoding matrix indicator (TPMI) index and the number of transmission layers for the PUSCH transmission. The UE may generate a precoding matrix (W) based on the TPMI index and the codebook type and encode the PUSCH for codebook-based PUSCH transmission using eight antenna ports and the indicated number of transmission layers by applying the generated precoding matrix. The precoding matrix (W) uses a codebook based on the coherency indication. Restrictions on the codebook parameters may apply to a fully coherent precoder.

Description

[Technical Field]

[0001] Priority claims This application claims the benefit of priority to U.S. Provisional Patent Application No. 63 / 487,534, filed February 28, 2023 [Docket No. AF2201-Z], International Application No. PCT / CN2023 / 084994, filed March 30, 2023 [Docket No. AF2677-PCT-Z], and International Application No. PCT / CN2023 / 085464, filed March 31, 2023 [Docket No. AF2693-PCT-Z], all of which are incorporated herein by reference in their entireties.

[0002] Technical Field FIELD Embodiments relate to wireless communications. [Background technology]

[0003] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated, integrated communications platforms. The proliferation of different types of devices communicating with various network devices is driving the use of 3GPP® 5G NR systems. The proliferation of mobile devices (user equipment or UE) in modern society continues to drive demand for a wide variety of networked devices in many different environments. 5G NR radio systems are coming soon and are expected to deliver even faster speeds, greater connectivity, and ease of use, improving throughput, coverage, and robustness while reducing latency and operational and capital expenditures. 5G NR networks will continue to evolve based on 3GPP® LTE-Advanced, adding the potential for new radio access technologies (RATs) to enrich people's lives with seamless wireless connectivity solutions that deliver high speeds and rich content and services. As current cellular network frequencies become saturated, higher frequencies, such as millimeter wave (mmWave) frequencies, may be beneficial due to their higher bandwidth.

[0004] The current version of 5G NR is capable of codebook-based transmission using up to four antenna ports and up to four transmission layers. To improve throughput, future versions of 5G NR aim to use up to eight antenna ports and up to eight transmission layers for codebook-based transmission. One issue with codebook-based transmission using eight antenna ports with up to eight transmission layers is the complexity of the codebook. Designing an optimal codebook that covers all possible channel scenarios becomes very complex as the number of antennas and layers increases. The number of possible precoding matrices that need to be included in the codebook increases exponentially. Furthermore, to support more antennas and layers, the codebook size increases exponentially, which requires more bits for the UE to feedback the preferred precoding matrix indicator (PMI), which increases uplink overhead.

[0005] Therefore, there is a need for techniques to reduce the complexity of codebook-based transmission using coherent precoding for eight antenna ports with up to eight transmission layers. [Brief explanation of the drawings]

[0006] [Figure 1A] FIG. 1 illustrates a network architecture according to some embodiments.

[0007] [Figure 1B] FIG. 1 illustrates a non-roaming 5G system architecture according to some embodiments. [Figure 1C] FIG. 1 illustrates a non-roaming 5G system architecture according to some embodiments.

[0008] [Figure 2] FIG. 1 illustrates a functional block diagram of a wireless communication device according to some embodiments.

[0009] [Figure 3] FIG. 1 illustrates a multi-antenna port transmission with multiple transmission layers according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0010] The following description and drawings sufficiently describe particular embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, portions and features of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0011] Some embodiments are directed to a user equipment (UE) configured for operation in a fifth generation new radio (5G NR) network. The UE may decode a radio resource control (RRC) information element (IE) received from a gNode B (gNB) to configure the UE with a codebook type for codebook-based physical uplink shared channel (PUSCH) transmissions using eight antenna ports and up to eight transmission layers. In these embodiments, the codebook type may have a coherency indication that may indicate one of a fully coherent codebook type, a partially coherent codebook type, and a non-coherent codebook type. In these embodiments, the UE may decode a downlink control information (DCI) format that schedules codebook-based PUSCH transmissions for the eight antenna ports. In these embodiments, the DCI format may indicate a transmit precoding matrix indicator (TPMI) index and the number of transmission layers for the PUSCH transmission. The UE may generate a precoding matrix (W) based on the TPMI index and the codebook type, and may encode the PUSCH for codebook-based PUSCH transmission using eight antenna ports and an indicated number of transmission layers by applying the generated precoding matrix. In these embodiments, to generate the precoding matrix (W), the UE may use a codebook based on the coherency indication. In some of these embodiments, to generate the precoding matrix (W), the UE may use a first codebook when a fully coherent codebook type is indicated, a second codebook when a noncoherent codebook type is indicated, or a third or fourth codebook when a partially coherent codebook type is indicated. In some embodiments, restrictions on codebook parameters may apply to the fully coherent codebook type.In some embodiments, these and other embodiments are described in more detail below.

[0012] 1A illustrates a network architecture according to some embodiments. Network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and UE 102 are shown as smartphones (e.g., handheld, touchscreen, mobile computing devices capable of connecting to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, a drone, or any other computing device that includes a wired and / or wireless communication interface. UE 101 and UE 102 may be collectively referred to herein as UE 101, which may be used to perform one or more of the techniques disclosed herein.

[0013] Any of the wireless links described herein (eg, as used in network 140A or any other illustrated network) may operate according to any example wireless communication technology and / or standard.

[0014] LTE and LTE-Advanced are standards for high-speed data wireless communications for UEs, such as mobile phones. In LTE-Advanced and various wireless systems, carrier aggregation is a technique that allows multiple carrier signals operating at different frequencies to carry communications for a single UE, thus increasing the bandwidth available to a single device. In some embodiments, carrier aggregation may be used when one or more component carriers operate in unlicensed frequencies.

[0015] The embodiments described herein can be used in the context of any spectrum management scheme, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in the 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and beyond frequencies, and Spectrum Access System (SAS) in the 3.55-3.7 GHz and beyond frequencies).

[0016] The embodiments described herein can also be applied to different single carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, Filter Bank Based Multi-Carrier (FBMC), OFDMA, etc.), especially 3GPP NR (New Radio), by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0017] In some embodiments, either UE 101 or UE 102 may comprise an Internet of Things (IoT) UE or a cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications utilizing short-lived UE connections. In some embodiments, either UE 101 or UE 102 may comprise a narrowband (NB) IoT UE (e.g., enhanced NB-IoT (eNB-IoT) UE and further enhanced (FeNB-IoT) UE). IoT UEs may utilize technologies such as machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with an MTC server or device over a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communication, a sensor network, or an IoT network. M2M or MTC data exchanges may be machine-initiated data exchanges. An IoT network includes IoT UEs interconnected over short-lived connections, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). The IoT UE may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0018] In some embodiments, either UE 101 or UE 102 may comprise an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0019] UE 101 and UE 102 may be configured to connect, e.g., be communicatively coupled, to a radio access network (RAN) 110. RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. UE 101 and UE 102 utilize connections 103 and 104, respectively, which each include a physical communication interface or layer (described in further detail below), which in this example are shown as air interfaces for enabling communication coupling and may conform to cellular communication protocols such as Global System for Mobile Communications (GSM®) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, PTT over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP® Long Term Evolution (LTE) protocol, Fifth Generation (5G) protocol, New Radio (NR) protocol, etc.

[0020] In one aspect, the UE 101 and the UE 102 may also directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including, but not limited to, a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSPCH).

[0021] The UE 102 is shown configured to access an access point (AP) 106 via a connection 107. The connection 107 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, and accordingly, the AP 106 may include a Wireless Fidelity (WiFi) router. In this example, the AP 106 is shown connected to the Internet without connecting to a core network of a wireless system (described in more detail below).

[0022] The RAN 110 may include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next-generation NodeBs (gNBs), RAN nodes, etc., and may include earth stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). In some embodiments, the RAN nodes 111 and 112 may be transmit / receive points (TRPs). For example, when the RAN nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may function within the communication cell of the NodeB. The RAN 110 may include one or more RAN nodes for providing a macrocell, e.g., a macro RAN node, and one or more RAN nodes for providing a femtocell or picocell (e.g., a cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell), e.g., a low-power (LP) RAN node.

[0023] Either of RAN nodes 111 and 112 may terminate air interface protocols and may be the first point of contact for UE 101 and UE 102. In some embodiments, either of RAN nodes 111 and 112 may perform various logical functions for RAN 110, including, but not limited to, radio bearer management, radio network controller (RNC) functions such as uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In one example, either of RAN nodes 111 and / or 112 may be a Next Generation Node B (gNB), an Evolved Node B (eNB), or another type of RAN node.

[0024] The RAN 110 is shown communicatively coupled to a core network (CN) 120 via an S1 interface 113. In an embodiment, the CN 120 may be an evolved packet core (EPC) network, a next-generation packet core (NPC) network, or some other type of CN (e.g., as illustrated with reference to FIGS. 1B-1C ). In this aspect, the S1 interface 113 is split into two parts: an S1-U interface 114 that carries traffic data between the RAN nodes 111 and 112 and a serving gateway (S-GW) 122, and an S1-mobility management entity (MME) interface 115 that is a signaling interface between the RAN nodes 111 and 112 and the MME 121.

[0025] In this aspect, the CN 120 includes an MME 121, an S-GW 122, a Packet Data Network (PDN) Gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124. The MME 121 may be similar in function to the control plane of a legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 121 may manage mobility-at-access aspects such as gateway selection and tracking area list management. The HSS 124 may include a database for network users containing subscription-related information to support the processing of communication sessions by network entities. The CN 120 may include one or several HSSs 124s, depending on the number of mobile subscribers, device capabilities, network organization, etc. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc.

[0026] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful intercept, charging, and some policy enforcement.

[0027] The P-GW 123 may terminate the SGi interface toward the PDN. The P-GW 123 may route data packets between the core network 120 and external networks, such as networks including application servers 184 (alternatively referred to as application functions (AFs)), via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data to other external networks 131A, which may include the Internet, IP Multimedia Subsystem (IPS) networks, and other networks. In general, the application servers 184 may be elements that provide applications that use IP bearer resources in conjunction with the core network (e.g., a UMTS packet service (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown communicatively coupled to the application servers 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 101 and the UE 102 via the CN 120.

[0028] The P-GW 123 may also be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some embodiments, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with the UE's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0029] In some embodiments, communication network 140A may be an IoT network or a 5G network, including a 5G new radio network that uses communications in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is Narrowband IoT (NB-IoT).

[0030] The NG system architecture may include a RAN 110 and a 5G network core (5GC) 120. In these embodiments, the RAN 110 may include multiple nodes, such as a gNB and an NG-eNB. The core network 120 (e.g., a 5G core network or 5GC) may include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and UPF may be communicatively coupled to the gNB and the NG-eNB via an NG interface. More specifically, in some embodiments, the gNB and the NG-eNB may be connected to the AMF by an NG-C interface and to the UPF by an NG-U interface. The gNB and the NG-eNB may be coupled to each other via an Xn interface.

[0031] In some embodiments, the NG system architecture may use reference points between various nodes as provided by 3GPP® Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some embodiments, each of the gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, etc. In some embodiments, in a 5G architecture, the gNB may be a master node (MN) and the NG-eNB may be a secondary node (SN).

[0032] FIG. 1B illustrates a non-roaming 5G system architecture according to some embodiments. Referring to FIG. 1B, a 5G system architecture 140B is illustrated in a reference point representation. More specifically, a UE 102 can communicate with a RAN 110 and one or more other 5G Core (5GC) network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as an access and mobility management function (AMF) 132, a session management function (SMF) 136, a policy control function (PCF) 148, an application function (AF) 150, a user plane function (UPF) 134, a network slice selection function (NSSF) 142, an authentication server function (AUSF) 144, and a unified data management (UDM) / home subscriber server (HSS) 146. The UPF 134 can provide connectivity to a data network (DN) 152, which can include, for example, operator services, internet access, or third-party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The SMF 136 can be configured to set up and manage various sessions according to network policies. The UPF 134 can be deployed in one or more configurations according to the desired service type. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to a PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0033] In some embodiments, the 5G system architecture 140B includes multiple IP Multimedia Core Network subsystem entities, such as an IP Multimedia Subsystem (IMS) 168B and a Call Session Control Function (CSCF). More specifically, the IMS 168B includes a CSCF, which can operate as a Proxy CSCF (P-CSCF) 162B, a Serving CSCF (S-CSCF) 164B, an Emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an Interrogation CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first point of contact for the UE 102 within the IM Subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle session state within the network, and the E-CSCF can be configured to handle specific aspects of the emergency session, such as routing emergency requests to the correct emergency center or PSAP. The I-CSCF 166B may be configured to serve as the point of contact within an operator's network for all IMS connections directed to subscribers of that network operator or roaming subscribers currently located within that network operator's service area. In some embodiments, the I-CSCF 166B may be connected to another IP multimedia network 170E, for example an IMS operated by a different network operator.

[0034] In some embodiments, UDM / HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application server (AS). AS 160B can be coupled to IMS 168B via S-CSCF 164B or I-CSCF 166B.

[0035] The reference point representation indicates that there may be interactions between corresponding NF services. For example, Figure 1B shows the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM / HSS 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), and N10 (between the UDM / HSS 146 and the SMF 136, not shown). 1B , N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM / HSS 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in the case of a non-roaming scenario, or between the PCF 148, the visited network, and the AMF 132 in the case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between the AMF 132 and the NSSF 142, not shown). Other reference point representations not shown in FIG. 1B can also be used.

[0036] 1C illustrates a 5G system architecture 140C and a service-based representation. In addition to the network entities illustrated in FIG. 1B, the system architecture 140C may also include a Network Publishing Function (NEF) 154 and a Network Repository Function (NRF) 156. In some embodiments, the 5G system architecture is service-based, and interactions between network functions may be represented by corresponding point-to-point reference points N i or as service-based interfaces.

[0037] In some embodiments, a service-based representation may be used to represent network functions in the control plane that allow other authorized network functions to access those services, as shown in FIG. 1C. In this regard, the 5G system architecture 140C may include the following service-based interfaces: Namf 158H (service-based interface indicated by AMF 132), Nsmf 158I (service-based interface indicated by SMF 136), Nnef 158B (service-based interface indicated by NEF 154), Npcf 158D (service-based interface indicated by PCF 148), Nudm 158E (service-based interface indicated by UDM / HSS 146), Naf 158F (service-based interface indicated by AF 150), Nnrf 158C (service-based interface indicated by NRF 156), Nnssf 158A (service-based interface indicated by NSSF 142), Nausf 158G (service-based interface indicated by AUSF 144). Other service-based interfaces not shown in FIG. 1C (eg, Nudr, N5g-eir, and Nudsf) may also be used.

[0038] In some embodiments, any of the UEs or base stations described in connection with FIGS. 1A-1C may be configured to perform the functionality described herein.

[0039] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated, integrated communications platforms. 5G, or New Radio (NR), the next-generation wireless communications system, provides access to information and data sharing anytime, anywhere by a variety of users and applications. NR is expected to be a unified network / system that aims to meet very different and sometimes conflicting performance dimensions and services. These diverse multi-dimensional requirements are driven by different services and applications. In general, NR evolves based on 3GPP® LTE-Advanced, potentially adding new radio access technologies (RATs) to enrich people's lives with better, simpler, and more seamless wireless connectivity solutions. NR enables wireless connectivity for everything, delivering high speeds, rich content, and services.

[0040] Rel-15 NR systems are designed to operate in licensed spectrum. NR-Unlicensed (NR-U) is shorthand for NR-based access to unlicensed spectrum, a technology that enables NR systems to operate over unlicensed spectrum.

[0041] FIG. 2 illustrates a functional block diagram of a wireless communication device according to some embodiments. The wireless communication device 200 may be suitable for use as a UE or gNB configured for operation in a 5G NR or 6G network. Some embodiments are directed to a UE or gNB apparatus including processing circuitry and memory configured for operation in a 5G NR or 6G network. The wireless communication device 200 may include communications circuitry 202 and a transceiver 210 for transmitting and receiving signals to and from other communications devices using one or more antennas 201. The communications circuitry 202 may include circuitry capable of operating physical layer (PHY) communications and / or media access control (MAC) communications for controlling access to a wireless medium, and / or any other communications layer for transmitting and receiving signals. The wireless communication device 200 may also include processing circuitry 206 and memory 208 configured to perform operations described herein. In some embodiments, the communications circuitry 202 and the processing circuitry 206 may be configured to perform operations detailed in the figures, diagrams, and flows above.

[0042] According to some embodiments, the communications circuitry 202 may be configured to contend for the wireless medium and compose frames or packets for communication over the wireless medium. The communications circuitry 202 may be configured to transmit and receive signals. The communications circuitry 202 may also include circuitry for modulation / demodulation, upconversion / downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 206 of the wireless communication device 200 may include one or more processors. In other embodiments, two or more antennas 201 may be coupled to the communications circuitry 202 configured to transmit and receive signals. The memory 208 may store information for configuring the processing circuitry 206 to perform operations for composing and transmitting message frames, as well as information for performing various operations described herein. The memory 208 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 208 may include a computer-readable storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium, an optical storage medium, a flash memory device, and other storage devices and media.

[0043] In some embodiments, wireless communication device 200 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capabilities, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computing device, or another device that may receive and / or transmit information wirelessly.

[0044] In some embodiments, wireless communication device 200 may include one or more antennas 201. Antenna 201 may include one or more directional or omnidirectional antennas, including, for example, a dipole antenna, a monopole antenna, a patch antenna, a loop antenna, a microstrip antenna, or other types of antennas suitable for transmitting RF signals. In some embodiments, a single antenna with multiple apertures may be used instead of two or more antennas. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, antennas may be effectively separated due to spatial diversity and the different channel characteristics that may result between each of the antennas and the antenna of the transmitting device.

[0045] In some embodiments, wireless communication device 200 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, a speaker, and other mobile device elements. The display may be an LCD screen, including a touch screen.

[0046] Although wireless communication device 200 is illustrated as having several distinct functional elements, two or more of those functional elements may be combined and implemented by a combination of software-configured elements and / or other hardware elements, such as processing elements including digital signal processors (DSPs). For example, some elements may include one or more microprocessors, DSPs, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio frequency integrated circuits (RFICs), and various combinations of hardware and logic circuits to perform at least the functions described herein. In some embodiments, the functional elements of wireless communication device 200 may refer to one or more processes operating on one or more processing elements.

[0047] FIG. 3 illustrates a multi-antenna port transmission with multiple transmission layers according to some embodiments. The multi-antenna port transmission may be a codebook-based PUSCH transmission using eight antenna ports and up to eight transmission layers. In these embodiments, the UE may decode a radio resource control (RRC) information element (IE) received from a gNodeB (gNB) to configure the UE with a codebook type for codebook-based physical uplink shared channel (PUSCH) transmission using eight antenna ports and up to eight transmission layers. In these embodiments, the codebook type may include a coherency indication that may indicate one of a fully coherent codebook type, a partially coherent codebook type, and a non-coherent codebook type. In these embodiments, the UE may decode a downlink control information (DCI) format that schedules the codebook-based PUSCH transmission for the eight antenna ports. In these embodiments, the DCI format may indicate a transmit precoding matrix indicator (TPMI) index and the number of transmission layers for the PUSCH transmission. The UE may generate a precoding matrix (W) based on the TPMI index and codebook type and apply the generated precoding matrix to encode the PUSCH for codebook-based PUSCH transmission using eight antenna ports and an indicated number of transmission layers. In these embodiments, to generate the precoding matrix (W), the UE may use a codebook based on a coherency indication. In some of these embodiments, to generate the precoding matrix (W), the UE may use a first codebook when a fully coherent codebook type is indicated, a second codebook when a noncoherent codebook type is indicated, or a third or fourth codebook when a partially coherent codebook type is indicated. These embodiments, as well as other embodiments, are described in more detail below.

[0048] As shown in Figure 3, a UE 302 operating as a transmitter (TX) may encode a PUSCH for a codebook-based PUSCH transmission 306 using eight antenna ports 304 (m = 8) and an indicated number of transmission layers by applying the generated precoding matrix. The antenna ports 304 are logical entities distinguished by their reference signal sequences and do not necessarily correspond to physical antennas. One or more gNBs operating a receiver RX, illustrated by reference numeral 308, may decode the codebook-based PUSCH transmission 306 using multiple antennas or antenna ports, which may be at least as many as the number of transmission layers used by the UE for transmission of the codebook-based PUSCH transmission 306.

[0049] The 3rd Generation Partnership Project (3GPP®) New Radio (NR) Release 15 (Rel-15) / Release 16 (Rel-16) / Release 17 (Rel-17) specifications support up to four transmit (Tx) ports or transmitters for transmitting the Physical Uplink Shared Channel (PUSCH) for uplink transmission. For codebook-based PUSCH transmission, a transmit precoding matrix indicator (TPMI) field in a downlink control indication (DCI) may indicate the precoder used for the PUSCH transmission. A codebook subset may be configured for a user equipment (UE), including one or more of a fullyAndPartialAndNonCoherent codebook subset, a partialAndNonCoherent codebook subset, and / or a nonCoherent codebook subset.

[0050] However, the 3GPP® Release 18 (Rel-18) specification may support up to eight Tx ports / antennas supported for PUSCH transmission.

[0051] In Rel-18, the fully coherent precoder may be based on the Rel-15 downlink (DL) Type I codebook. The partially coherent / non-coherent precoder may be based on the Rel-15 4Tx / 2Tx precoding matrix. Therefore, in Rel-18, the TPMI indication may be extended to take into account or based on the codebook subset configuration. The embodiments herein relate to the TPMI indication for the 8Tx PUSCH taking into account the codebook subset configuration.

[0052] Extended TPMI indication for 8Tx PUSCH transmission

[0053] In one embodiment, for an 8-Tx UE, the fullyAndPartialAndNonCoherent codebook subset may include one or more of a fully coherent precoder, a partial coherent precoder, and / or a noncoherent precoder. The partialAndNonCoherent codebook subset may include one or more of a partial coherent precoder and a noncoherent precoder. The nonCoherent codebook subset may include a noncoherent precoder.

[0054] In another embodiment, in a DCI scheduling a PUSCH, the DCI may indicate whether a fully coherent precoder, a partially coherent precoder, and / or a non-coherent precoder is indicated in the TPMI field within the DCI, i.e., precoder coherence may be indicated via the DCI.

[0055] In one option, the precoder coherence indication can be via a new DCI field, which can be, for example, a 2-bit or 1-bit field, a binary coded or a bitmap, etc. Alternatively, one or more existing DCI fields can be reused, or some special code points of some DCI fields can be used for the precoder coherence indication.

[0056] In another option, the precoder coherence indication can be done via the media access control (MAC)-control element (CE) or can be configured by radio resource control (RRC) signaling.

[0057] In another embodiment, when a fullyAndPartialAndNonCoherent codebook subset is configured, the precoder coherence indication can indicate whether a fully coherent precoder, a partially coherent precoder, and / or a noncoherent precoder is indicated in a TPMI field in the DCI. In one example, the precoder coherence indication field can be two bits. In one option, one TPMI field can be configured in the DCI.

[0058] When the precoder coherence indication indicates a fully coherent precoder, the TPMI field can indicate an 8-port (e.g., 8 TX port) fully coherent precoder, which may be based on a DL Type I codebook. In another example, the parameters for generating the 8-port fully coherent precoder (i.e., i 1,1 , i 1,2 , i 1,3 and i2) may be indicated in the DCI.

[0059] When the precoder coherence indication indicates a partially coherent precoder, the TPMI field may indicate one of the following: One 8-port partially coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder A single 4Tx precoding matrix to construct an 8-port partially coherent precoder (e.g., a single 4Tx precoding matrix can be applied to a partially coherent UE with two antenna groups). A single 2Tx precoding matrix to construct an 8-port partially coherent precoder (e.g., a single 2Tx precoding matrix can be applied to a partially coherent UE with four antenna groups). ●Up to four 2-Tx precoding matrices can be specified to construct an 8-port partially coherent precoder (e.g., applicable to a partially coherent UE with four antenna groups).

[0060] When the precoder coherence indication indicates a non-coherent precoder, the TPMI field may indicate one or more of the following (note, however, that the following are intended as illustrative examples and that the TPMI field may additionally or alternatively indicate other information): One 8-port non-coherent precoder Two 4-Tx precoding matrices or one 4-Tx precoding matrix to construct an 8-port non-coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port non-coherent precoder Up to four 2-Tx precoding matrices to build an 8-port non-coherent precoder

[0061] The TPMI field size may be determined by the maximum bit width required for one or more of the fully coherent precoder, the partially coherent precoder, and / or the noncoherent precoder. For example, X bits are required for the fully coherent precoder, Y bits are required for the partially coherent precoder, and Z bits are required for the noncoherent precoder. Then the TPMI field length is max{X,Y,Z}.

[0062] In one option, the same or different coding schemes between the rank indicator and the precoder indicator can be applied to the different coherencies.

[0063] For example, in a fully coherent precoder, separate encoding of the rank indicator and the precoder indicator is applied. In a partially coherent and / or non-coherent precoder, joint encoding of the rank indicator and the precoder indicator is applied. The rank indication field should be present in the DCI and should be ignored when a partially coherent / non-coherent precoder is indicated.

[0064] In another example, joint coding of the rank indicator and the precoder indicator can be applied to all three coherence types, or separate coding of the rank indicator and the precoder indicator can be applied to all three coherence types.

[0065] In another embodiment, when a fullyAndPartialAndNonCoherent codebook subset is configured, the precoder coherence indication can indicate whether a fully coherent precoder is indicated in the TPMI field in the DCI, or whether a partially coherent precoder and a noncoherent precoder are indicated in the TPMI field in the DCI. In one example, the precoder coherence indication field can be 1 bit.

[0066] One option is to configure one TPMI field in the DCI.

[0067] When the precoder coherence indication indicates a fully coherent precoder, the TPMI field can indicate an 8-port fully coherent precoder, which is based on a DL Type I codebook. In another example, the parameters for generating an 8-port fully coherent precoder (i.e., i 1,1 , i 1,2 , i 1,3 and i2) one or some or all of which may be indicated in the DCI.

[0068] When the precoder coherence indication indicates a partially coherent and non-coherent precoder, the TPMI field can indicate one or more of the following: One 8-port partially coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder Only one 4-Tx precoding matrix to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with two antenna groups) Only one 2-Tx precoding matrix to construct an 8-port partially coherent precoder (applicable to a partially coherent UE with four antenna groups) Up to four 2-Tx precoding matrices are specified to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) One 8-port non-coherent precoder Two 4-Tx precoding matrices or one 4-Tx precoding matrix to construct an 8-port non-coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port non-coherent precoder Up to four 2-Tx precoding matrices to build an 8-port non-coherent precoder

[0069] The TPMI field size can be determined by the maximum bit width required for the fully coherent precoder, the partially coherent precoder, and the non-coherent precoder. For example, X bits are required for the fully coherent precoder, and Y bits are required for the partially coherent precoder and the non-coherent precoder. Then, the TPMI field length is max{X,Y}.

[0070] In one option, the same or different coding schemes between the rank indicator and the precoder indicator can be applied to the different coherencies.

[0071] For example, in the case of a fully coherent precoder, separate coding of the rank indicator and the precoder indicator is applied. In the case of a partially coherent precoder and a non-coherent precoder, joint coding of the rank indicator and the precoder indicator is applied. The rank indication field should be present in the DCI and should be ignored when a partially coherent / non-coherent precoder is indicated.

[0072] In another example, joint coding of the rank indicator and the precoder indicator can be applied to all three coherence types, or separate coding of the rank indicator and the precoder indicator can be applied to all three coherence types.

[0073] In another embodiment, when a fullyAndPartialAndNonCoherent codebook subset is configured, up to two or up to four TPMI fields can be included in the DCI. When the precoder coherence indication indicates a fully coherent precoder, one TPMI field is used. When the precoder coherence indication indicates a partially coherent and / or noncoherent precoder, up to two or up to four TPMI fields are used.

[0074] In another embodiment, when a partialAndNonCoherent codebook subset is configured, the precoder coherence indication can indicate whether a partially coherent or noncoherent precoder is indicated in a TPMI field in the DCI. In one example, the precoder coherence indication field can be 1 bit. In one option, one TPMI field can be configured in the DCI.

[0075] When the precoder coherence indication indicates a partially coherent precoder, the TPMI field may indicate one or more of the following (note, however, that the following are intended as illustrative examples and that the TPMI field may additionally or alternatively indicate other information): One 8-port partially coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder A single 4-Tx precoding matrix to construct an 8-port partially coherent precoder (e.g., applicable to a partially coherent UE with two antenna groups) A single 2-Tx precoding matrix to construct an 8-port partially coherent precoder (e.g., applicable to a partially coherent UE with four antenna groups) Up to four 2-Tx precoding matrices are specified to construct an 8-port partially coherent precoder (e.g., applicable to a partially coherent UE with four antenna groups).

[0076] When the precoder coherence indication indicates a non-coherent precoder, the TPMI field may indicate one of the following: one or more of the following (note, however, that the following are intended as illustrative examples and that the TPMI field may additionally or alternatively indicate other information): One 8-port non-coherent precoder Two 4-Tx precoding matrices or one 4-Tx precoding matrix to construct an 8-port non-coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port non-coherent precoder Up to four 2-Tx precoding matrices to build an 8-port non-coherent precoder

[0077] The TPMI field size can be determined by the maximum bit width required for the partially coherent and non-coherent precoders. For example, Y bits are required for the partially coherent precoder and Z bits are required for the non-coherent precoder. In this case, the TPMI field length can be max{Y,Z}. In the second option, up to two TPMI fields can be configured in the DCI.

[0078] When the precoder coherence indication indicates a partially coherent precoder, two TPMI fields can indicate one of the following (this can apply to partially coherent UEs with two antenna groups and four antenna groups): ●One TPMI field indicates one 4Tx precoding matrix and another TPMI field indicates one 4Tx precoding matrix for constructing an 8-port partially coherent precoder. Alternatively, only one TPMI field is used to indicate one 4Tx precoding matrix for constructing an 8-port partially coherent precoder and another TPMI field is unused. Unused TPMI fields may not be present in the DCI, or may be present in the DCI but ignored by the UE. One TPMI field indicates one 2-Tx precoding matrix, and another TPMI field indicates one 4-Tx precoding matrix to construct an 8-port partially coherent precoder. ●One TPMI field indicates up to two 2Tx precoding matrices. Up to four 2Tx precoding matrices are indicated to construct an 8-port partially coherent precoder (applicable to a partially coherent UE with four antenna groups).

[0079] When the precoder coherence indication indicates a non-coherent precoder, two TPMI fields can indicate one of the following: ●One TPMI field indicates one 4Tx precoding matrix and another TPMI field indicates one 4Tx precoding matrix for constructing an 8-port non-coherent precoder. Alternatively, only one TPMI field is used to indicate one 4Tx precoding matrix for constructing an 8-port non-coherent precoder and another TPMI field is unused. Unused TPMI fields may not be present in the DCI, or may be present in the DCI but ignored by the UE. One TPMI field indicates one 2-Tx precoding matrix, and another TPMI field indicates one 4-Tx precoding matrix to construct an 8-port non-coherent precoder. One TPMI field indicates up to two 2Tx precoding matrices, and another TPMI field indicates up to two 2Tx precoding matrices for constructing an 8-port non-coherent precoder.

[0080] The third option allows for up to four TPMI fields to be configured within the DCI.

[0081] When the precoder coherence indication indicates a partially coherent precoder, four TPMI fields can indicate the following (applicable to partially coherent UEs with four antenna groups): One TPMI field indicates one 2Tx precoding matrix. Up to four 2Tx precoding matrices are used to construct an 8-port partially coherent precoder.

[0082] When the precoder coherence indication indicates a non-coherent precoder, four TPMI fields can indicate the following: one TPMI field indicates one 2-Tx precoding matrix, and up to four 2-Tx precoding matrices are used to construct an 8-port non-coherent precoder.

[0083] Another option is to apply the same or different coding schemes between the rank indicator and the precoder indicator to the different coherencies.

[0084] In another embodiment, the partialAndNonCoherent codebook subset includes a partial coherent precoder and a noncoherent precoder. When the partialAndNonCoherent codebook subset is configured, the precoder coherence indication field may not be present in the DCI.

[0085] One option is to configure one TPMI field in the DCI to indicate one or more of the following: One 8-port partially coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder A single 4-transceiver precoding matrix for constructing an 8-port partially coherent precoder (applicable to partially coherent UEs with two antenna groups) A single 2-Tx precoding matrix to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) Up to four 2-Tx precoding matrices are specified to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) One 8-port non-coherent precoder Two 4-Tx precoding matrices or one 4-Tx precoding matrix to construct an 8-port non-coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to construct an 8-port partially non-coherent precoder Up to four 2-Tx precoding matrices to build an 8-port non-coherent precoder

[0086] In the second option, up to two TPMI fields can be configured in the DCI to indicate one of the following: ●One TPMI field indicates one 4Tx precoding matrix and another TPMI field indicates one 4Tx precoding matrix for constructing an 8-port partially coherent precoder. Alternatively, only one TPMI field is used to indicate one 4Tx precoding matrix for constructing an 8-port partially coherent precoder and another TPMI field is unused. Unused TPMI fields may not be present in the DCI, or may be present in the DCI but ignored by the UE (applicable to partially coherent UEs with two antenna groups and four antenna groups). ●One TPMI field indicates one 2Tx precoding matrix, and the other TPMI field indicates one 4Tx precoding matrix to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with two antenna groups and four antenna groups). ●One TPMI field indicates up to two 2Tx precoding matrices. Up to four 2Tx precoding matrices are indicated to construct an 8-port partially coherent precoder (which can be applied to a partially coherent UE with four antenna groups). ●One TPMI field indicates one 4Tx precoding matrix and another TPMI field indicates one 4Tx precoding matrix for constructing an 8-port non-coherent precoder. Alternatively, only one TPMI field is used to indicate one 4Tx precoding matrix for constructing an 8-port non-coherent precoder and another TPMI field is unused. Unused TPMI fields may not be present in the DCI, or may be present in the DCI but ignored by the UE. One TPMI field indicates one 2-Tx precoding matrix, and another TPMI field indicates one 4-Tx precoding matrix to construct an 8-port non-coherent precoder. One TPMI field indicates up to two 2Tx precoding matrices, and another TPMI field indicates up to two 2Tx precoding matrices for constructing an 8-port non-coherent precoder.

[0087] The third option allows up to four TPMI fields to be configured in the DCI to indicate one of the following: One TPMI field indicates one 2Tx precoding matrix. Up to four 2Tx precoding matrices are used to construct an 8-port partially coherent precoder (applicable to a partially coherent UE with four antenna groups). One TPMI field indicates one 2Tx precoding matrix. Up to four 2Tx precoding matrices are used to construct an 8-port non-coherent precoder.

[0088] In another embodiment, when a non-coherent codebook subset is configured, a non-coherent precoder is indicated in the TPMI field in the DCI. In one example, the precoder coherence indication field may not be present in the DCI.

[0089] In one option, one TPMI field may be configured in the DCI, which may indicate one of the following: One 8-port non-coherent precoder Two 4-Tx precoding matrices or one 4-Tx precoding matrix to construct an 8-port non-coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port non-coherent precoder Up to four 2-Tx precoding matrices to build an 8-port non-coherent precoder

[0090] The TPMI field size can be determined by the bit width required for the non-coherent precoder. For example, if Z bits are required for the non-coherent precoder, then the TPMI field length is Z.

[0091] In the second option, up to two TPMI fields can be configured in the DCI to indicate one of the following: ●One TPMI field indicates one 4Tx precoding matrix and another TPMI field indicates one 4Tx precoding matrix for constructing an 8-port non-coherent precoder. Alternatively, only one TPMI field is used to indicate one 4Tx precoding matrix for constructing an 8-port non-coherent precoder and another TPMI field is unused. Unused TPMI fields may not be present in the DCI, or may be present in the DCI but ignored by the UE. One TPMI field indicates one 2-Tx precoding matrix, and another TPMI field indicates one 4-Tx precoding matrix to construct an 8-port non-coherent precoder. One TPMI field indicates up to two 2Tx precoding matrices, and another TPMI field indicates up to two 2Tx precoding matrices to construct an 8-port non-coherent precoder.

[0092] In the third option, up to four TPMI fields can be configured in the DCI to indicate: one TPMI field indicates one 2-Tx precoding matrix, and up to four 2-Tx precoding matrices are used to construct an 8-port non-coherent precoder.

[0093] In another embodiment, the precoder coherence can be updated by the MAC-CE or configured by the RRC. When the precoder coherence of the fully coherent precoder is indicated by the MAC-CE or the RRC, one TPMI field can be configured in the DCI to indicate an 8-port fully coherent precoder. In another example, the parameters for generating the 8-port fully coherent precoder (i.e., i 1,1 , i 1,2 , i 1,3 and i2) are indicated in the DCI.

[0094] When precoder coherence for a partially coherent precoder is indicated by MAC-CE or RRC, one option may configure one TPMI field in the DCI to indicate one of the following (applicable for partially coherent UEs with two antenna groups and four antenna groups): One 8-port partially coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder A single 4-transceiver precoding matrix for constructing an 8-port partially coherent precoder (applicable to partially coherent UEs with two antenna groups) A single 2-Tx precoding matrix to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) Specify up to four 2-Tx precoding matrices to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups)

[0095] In another option, in the DCI, up to two TPMI fields may indicate one of the following (applicable for partially coherent UEs with two antenna groups and four antenna groups): ●One TPMI field indicates one 4Tx precoding matrix and another TPMI field indicates one 4Tx precoding matrix for constructing an 8-port partially coherent precoder. Alternatively, only one TPMI field is used to indicate one 4Tx precoding matrix for constructing an 8-port partially coherent precoder and another TPMI field is not used. Unused TPMI fields may be present in the DCI, or may be present in the DCI but ignored by the UE. One TPMI field indicates one 2-Tx precoding matrix, and another TPMI field indicates one 4-Tx precoding matrix to construct an 8-port partially coherent precoder. ●One TPMI field indicates up to two 2Tx precoding matrices. Up to four 2Tx precoding matrices are indicated to construct an 8-port partially coherent precoder (which can be applied to a partially coherent UE with four antenna groups).

[0096] Another option is to configure up to four TPMI fields in the DCI to indicate the following (applicable for partially coherent UEs with four antenna groups): one TPMI field indicates one 2Tx precoding matrix, and up to four 2Tx precoding matrices are used to construct an 8-port partially coherent precoder.

[0097] When precoder coherence for a non-coherent precoder is indicated by MAC-CE or RRC, in one option, one TPMI field in the DCI may indicate one or more of the following (note, however, that the following is intended as an illustrative example and that the TPMI field may additionally or alternatively indicate other information): One 8-port non-coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port non-coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port non-coherent precoder Up to four 2-Tx precoding matrices to build an 8-port non-coherent precoder

[0098] In another option, up to two TPMI fields in the DCI may indicate one or more of the following (note, however, that the following are intended as illustrative examples, and that the TPMI fields may additionally or alternatively indicate other information): ●One TPMI field indicates one 4Tx precoding matrix and another TPMI field indicates one 4Tx precoding matrix for constructing an 8-port non-coherent precoder. Alternatively, only one TPMI field is used to indicate one 4Tx precoding matrix for constructing an 8-port non-coherent precoder and another TPMI field is unused. Unused TPMI fields may not be present in the DCI, or may be present in the DCI but ignored by the UE. One TPMI field indicates one 2-Tx precoding matrix, and another TPMI field indicates one 4-Tx precoding matrix to construct an 8-port non-coherent precoder. One TPMI field indicates up to two 2Tx precoding matrices, and another TPMI field indicates up to two 2Tx precoding matrices for constructing an 8-port non-coherent precoder.

[0099] Another option is to configure up to four TPMI fields in the DCI to indicate: one TPMI field indicates one 2Tx precoding matrix, and up to four 2Tx precoding matrices are used to construct an 8-port non-coherent precoder.

[0100] In another embodiment, if the precoder coherence can be updated by MAC-CE or configured by RRC, the same or different coding schemes between the rank indicator and the precoder indicator can be applied for different coherences. For example, if a fully coherent precoder is configured, separate coding of the rank indicator and the precoder indicator is applied and a DCI field for the rank indication should be present in the DCI. If a partially coherent or non-coherent precoder is configured, joint coding of the rank indicator and the precoder indicator is applied and no rank indication field is present in the DCI.

[0101] In another example, joint coding of the rank indicator and the precoder indicator can be applied to all three coherence types, or separate coding of the rank indicator and the precoder indicator can be applied to all three coherence types.

[0102] In another embodiment, for a UE with 8 Tx, the fullyAndPartialAndNonCoherent codebook subset includes only fully coherent precoders, the partialAndNonCoherent codebook subset includes only partial coherent precoders (or the partialAndNonCoherent codebook subset includes partial coherent and noncoherent precoders), and the nonCoherent codebook subset includes noncoherent precoders.

[0103] When a fullyAndPartialAndNonCoherent codebook subset is configured, one TPMI field can be configured in the DCI to indicate an 8-port fully coherent precoder. In another example, the parameters for generating an 8-port fully coherent precoder (i.e., i 1,1 , i 1,2 , i 1,3 and i2) one or some or all of which may be indicated in the DCI.

[0104] When a partialAndNonCoherent codebook subset is configured, in one option, one TPMI field in the DCI may indicate one or more of the following (note, however, that the following is intended as an illustrative example, and that the TPMI field may additionally or alternatively indicate other information): One 8-port partially coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder A single 4-transceiver precoding matrix for constructing an 8-port partially coherent precoder (applicable to partially coherent UEs with two antenna groups) A single 2-Tx precoding matrix to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) Up to four 2-Tx precoding matrices are specified to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups)

[0105] In another option, in the DCI, up to two TPMI fields may indicate one of the following (applicable for partially coherent UEs with two antenna groups and four antenna groups): one or more of the following (note, however, that the following are intended as illustrative examples and that the TPMI fields may additionally or alternatively indicate other information): ●One TPMI field indicates one 4Tx precoding matrix and another TPMI field indicates one 4Tx precoding matrix for constructing an 8-port partially coherent precoder. Alternatively, only one TPMI field is used to indicate one 4Tx precoding matrix for constructing an 8-port partially coherent precoder and another TPMI field is unused. Unused TPMI fields may be present in the DCI, or may be present in the DCI but ignored by the UE. One TPMI field indicates one 2-Tx precoding matrix, and another TPMI field indicates one 4-Tx precoding matrix to construct an 8-port partially coherent precoder. ●One TPMI field indicates up to two 2Tx precoding matrices. Up to four 2Tx precoding matrices are indicated to construct an 8-port partially coherent precoder (applicable to a partially coherent UE with four antenna groups).

[0106] Another option is to configure up to four TPMI fields in the DCI to indicate the following (applicable for partially coherent UEs with four antenna groups): one TPMI field indicates one 2Tx precoding matrix, and up to four 2Tx precoding matrices are used to construct an 8-port partially coherent precoder.

[0107] When a non-coherent codebook subset is configured, in one option, one TPMI field in the DCI may indicate one or more of the following (note, however, that the following is intended as an illustrative example and that the TPMI field may additionally or alternatively indicate other information): One 8-port non-coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port non-coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port non-coherent precoder

[0108] In another option, up to two TPMI fields in the DCI may indicate one or more of the following (note, however, that the following are intended as illustrative examples, and that the TPMI fields may additionally or alternatively indicate other information): ●One TPMI field indicates one 4Tx precoding matrix and another TPMI field indicates one 4Tx precoding matrix for constructing an 8-port non-coherent precoder. Alternatively, only one TPMI field is used to indicate one 4Tx precoding matrix for constructing an 8-port non-coherent precoder and another TPMI field is unused. Unused TPMI fields may not be present in the DCI, or may be present in the DCI but ignored by the UE. One TPMI field indicates one 2-Tx precoding matrix, and another TPMI field indicates one 4-Tx precoding matrix to construct an 8-port non-coherent precoder. One TPMI field specifies up to two 2Tx precoding matrices, and another TPMI field specifies up to two 2Tx precoding matrices to construct an 8-port non-coherent precoder.

[0109] Another option is to configure up to four TPMI fields in the DCI to indicate: one TPMI field indicates one 2-Tx precoding matrix, and up to four 2-Tx precoding matrices are used to construct an 8-port non-coherent precoder.

[0110] In another embodiment, for a UE with 8 Tx, the fullyAndPartialAndNonCoherent codebook subset includes only fully coherent precoders, the partialAndNonCoherent codebook subset includes only partial coherent precoders (or the partialAndNonCoherent codebook subset includes partial coherent and noncoherent precoders), and the nonCoherent codebook subset includes noncoherent precoders.

[0111] In this case, the same or different coding schemes between the rank indicator and the precoder indicator can be applied to the fullyAndPartialAndNonCoherent codebook subset, the partialAndNonCoherent codebook subset, and the nonCoherent codebook subset. For example, separate coding of the rank indicator and the precoder indicator is applied to the fullyAndPartialAndNonCoherent codebook subset. Joint coding of the rank indicator and the precoder indicator is applied to the partialAndNonCoherent codebook subset and the nonCoherent codebook subset. In this case, when the fullyAndPartialAndNonCoherent codebook subset is configured, a DCI field for rank indication should be present in the DCI. When the partialAndNonCoherent codebook subset or the nonCoherent codebook subset is configured, the rank indication field is not present in the DCI.

[0112] In another example, joint coding of the rank indicator and the precoder indicator can be applied to all three codebook subsets, or separate coding of the rank indicator and the precoder indicator can be applied to all three codebook subsets.

[0113] In another embodiment, for partially coherent and / or non-coherent precoder indication, separate or joint coding between the rank indicator and the precoder indicator may be applied in the DCI scheduling the PUSCH.

[0114] In a first option of this embodiment, separate coding of the rank indicator and the precoder indicator is applied.

[0115] In a first example of the first option, one DCI field, e.g., the TPMI field, is used for the rank indicator and the precoder indicator. Some bits of the DCI field can be used for the rank indication, and some other bits can be used for the precoder indication. For example, one DCI field, e.g., the TPMI field, can be divided into two parts. One part, e.g., the first part, is used for the rank indication, and the other part, e.g., the second part, is used for the precoder indication. The bit length of the first part for the rank indication can be fixed, or can be determined by a predetermined or configured rank limit based on the maximum number of layers.

[0116] Additionally, the second part of the DCI field may indicate one or more of the following: One 8-port partially coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder A single 4-transmitter precoding matrix for constructing an 8-port partially coherent precoder (applicable to partially coherent UEs with two antenna groups) A single 2-transmitter precoding matrix for constructing an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) Up to four 2-Tx precoding matrices are specified to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) One 8-port non-coherent precoder Two 4-Tx precoding matrices or one 4-Tx precoding matrix to construct an 8-port non-coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port non-coherent precoder Up to four 2-Tx precoding matrices to build an 8-port non-coherent precoder

[0117] In a second example of the first option, separate DCI fields are used for the rank indicator and the precoder indicator. For example, one DCI field, e.g., a TPMI field, is used for the precoder indicator, and another DCI field (which may be newly added) is used for the rank indicator. The DCI field for rank indication may have a fixed length, or the bit length of the rank indication field may be predetermined by the maximum number of layers or determined by a configured rank limit.

[0118] Furthermore, the DCI field for precoder indication, e.g., the TPMI field, can indicate one or more of the following: One 8-port partially coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder A single 4-transmitter precoding matrix for constructing an 8-port partially coherent precoder (applicable to partially coherent UEs with two antenna groups) A single 2-transmitter precoding matrix for constructing an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) Up to four 2-Tx precoding matrices are specified to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) One 8-port non-coherent precoder Two 4-Tx precoding matrices or one 4-Tx precoding matrix to construct an 8-port non-coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port non-coherent precoder Up to four 2-Tx precoding matrices to build an 8-port non-coherent precoder

[0119] In a third example of the first option, separate DCI fields are used for the rank indicator and the precoder indicator. For example, one DCI field or multiple DCI fields (e.g., one TPMI field or multiple TPMI fields) are used for the precoder indicator, and another DCI field (which may be newly added) is used for the rank indicator. The DCI field for rank indication may have a fixed length, or the bit length of the rank indication field may be predetermined by the maximum number of layers or determined by a configured rank limit.

[0120] Furthermore, up to two TPMI fields can be included in the DCI to indicate up to two 4Tx precoding matrices (one TPMI field indicates one 4Tx precoder, or each TPMI field indicates up to two 2Tx precoding matrices, or one TPMI field indicates a 2Tx precoder and another TPMI field indicates a 4Tx precoder), or up to four TPMI fields can be included to indicate up to four 2Tx precoding matrices (one TPMI field indicates one 2Tx precoder).

[0121] In a second option of this embodiment, joint coding of the rank indicator and the precoder indicator is applied.

[0122] In the first example of the second option, one TPMI field is included, which can indicate one of the following: One 8-port partially coherent precoder One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder A single 4-transmitter precoding matrix for constructing an 8-port partially coherent precoder (applicable to partially coherent UEs with two antenna groups) A single 2-transmitter precoding matrix for constructing an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) Up to four 2-Tx precoding matrices are specified to construct an 8-port partially coherent precoder (applicable to partially coherent UEs with four antenna groups) One 8-port non-coherent precoder Two 4-Tx precoding matrices or one 4-Tx precoding matrix to construct an 8-port non-coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port non-coherent precoder Up to four 2-Tx precoding matrices to build an 8-port non-coherent precoder

[0123] In a second example of the second option, one or more DCI fields (eg, one or more TPMI fields) are included in the DCI.

[0124] Furthermore, up to two TPMI fields can be included in the DCI to indicate up to two 4Tx precoding matrices (one TPMI field indicates one 4Tx precoder, or each TPMI field indicates up to two 2Tx precoding matrices, or one TPMI field indicates a 2Tx precoder and another TPMI field indicates a 4Tx precoder), and each field can be jointly coded between the 4Tx precoder and the rank. Alternatively, up to four TPMI fields can be included (one TPMI field indicates one 2Tx precoder) to indicate up to four 2Tx precoding matrices, and each field can be jointly coded between the 2Tx precoder and the rank. In this embodiment, as described in all the above embodiments of the present invention, partially coherent precoders and / or noncoherent precoders can be included in the codebook subset.

[0125] Note: The various embodiments and / or options described in this specification may be applied jointly or separately to the case of joint coding of the rank indicator and the precoder indicator in the DCI and to the case of separate coding of the rank indicator and the precoder indicator in the DCI.

[0126] The 3rd Generation Partnership Project (3GPP®) New Radio (NR) Release-15 / Release-16 / Release-17 (Rel-15 / Rel-16 / Rel-17) specifications for uplink transmissions can support up to four layers for the Physical Uplink Shared Channel (PUSCH). In the 3GPP® Release-18 (Rel-18) specifications, up to eight layers can be supported for PUSCH transmissions. Therefore, it may be desirable to enhance the associated uplink precoder to support up to eight layers with eight ports.

[0127] In Rel-18, the fully coherent precoder used for transmission may be based on the Rel-15 downlink (DL) Type I codebook. For the Rel-15 DL Type I codebook, this is based on the antenna structure and configuration as (N1,N2) and (O1,O2), where N1 and N2 are the number of antenna elements in the horizontal and vertical directions, respectively, and O1 and O2 are the oversampling factors in the horizontal and vertical directions, respectively. For the Type I codebook, the precoder is defined as a rank value and a parameter i 1,1 , i 1,2 , i 1,3 and i2. However, the amount of a fully coherent precoder based on a Type I codebook can be large. There may be low-overhead schemes to reduce the amount of precoder, e.g., some restrictions may be introduced on the Type I codebook parameters.

[0128] As mentioned above, legacy specifications may only support up to four layers and up to four ports for PUSCH transmission. Embodiments herein relate to restricting Type I codebook parameters to reduce the amount of fully coherent precoders.

[0129] Configuration and Instruction of an 8-Port Fully Coherent Precoder

[0130] In an embodiment, for an 8-port fully coherent precoder based on DL type I codebook, the parameters for generating the precoder, i.e., 1,1 , i 1,2 , i 1,3 A restriction can be introduced on i and i, such that only a subset of values ​​are allowed / used to generate a fully coherent precoder.

[0131] In one example, i 1,1 and i 1,2 For i, we can choose even values, e.g., {0,2...}. Alternatively, we can choose odd values, e.g., {1,3...}.1,1 and i 1,2 The same or different subsets can be selected for .

[0132] In one example, for i2, one value (e.g., {0}) or two values ​​(e.g., {0,2}) can be selected for rank 1. For ranks 2 through 8, one value (e.g., {0} or {1}) can be selected.

[0133] In one example, i 1,3 The value of can be fixed to 0.

[0134] In another embodiment, one or some or all of the parameters i 1,1 , i 1,2 , i 1,3 The restrictions on i and i2 may be configured or updated by higher level signaling such as Radio Resource Control (RRC) or Media Access Control - Control Element (MAC-CE), or may be indicated by Downlink Control Information (DCI). The restrictions indicate which values ​​are allowed. The restrictions can be a bitmap.

[0135] Another option is to specify one, some, or all of the parameters i 1,1 , i 1,2 , i 1,3 The limits for i1 and i2 may be predefined in the 3GPP® specifications related to the physical layer.

[0136] In one example, i 1,1 and i 1,2 The same restrictions may be applied to i 1,1 and i 1,2 Different restrictions may apply to

[0137] In another example, one bitmap may be configured / defined for each parameter, or one bitmap may be configured / defined for multiple parameters.

[0138] In another embodiment, one or some or all of the parameters i 1,1 , i 1,2 , i 1,3 The limits on i and i2 may be configured or predefined for each rank. The limits may be the same or different for different ranks.

[0139] Another option is to specify one, some, or all of the parameters i 1,1 , i 1,2 , i 1,3 The limits on i and i2 may be configured or predefined across ranks. The limits may be the same across ranks.

[0140] In another embodiment, the value of the oversampling factor of the 8-port fully coherent precoder, i.e., (01,02) = (1,1) or (2,1) or (2,2), may be configured / updated / indicated by RRC, configured / updated / indicated by MAC-CE, indicated by DCI, or predefined by the physical layer specification.

[0141] In another embodiment, a rank restriction may be introduced for an 8-port UE to disable some rank values ​​for transmission. The rank restriction may be configured by RRC or MAC-CE, and the rank restriction may be a bitmap.

[0142] In another option, a minimum number of layers and a maximum number of layers may be configured, and rank values ​​between the minimum number of layers and the maximum number of layers may be allowed.

[0143] In another embodiment, a linear indexing can be defined for the 8-port fully coherent precoder.

[0144] In one example, the linear index may be defined as follows:

[0145] FC-TPMI = index(i2) + size(i2) * index(i11,i12) + size(i2) * size(i11,i12) * index(ri), where index(i2) ranges from 0, 1, ..., size(i2)-1, and index(i11,i12) ranges from 0, 1, ..., size(i11,i12)-1. size(i2) is the number of unbounded i2 entries corresponding to the rank given by index(ri). size(i11,i12) is the number of unbounded i11 and i12 entries corresponding to the rank given by index(ri).

[0146] When separate coding of rank indicator and precoder indicator is applied, the linear index of rank-(ri) can be defined as follows:

[0147] FC-TPMI=index(i2)+size(i2)*index(i11,i12)

[0148] In another embodiment, an 8-port fully coherent precoder may be indicated in the DCI scheduling the PUSCH, or parameters for generating an 8-port fully coherent precoder may be indicated.

[0149] In one option, an 8-port fully coherent precoder may be indicated. This indication may be done via one TPMI field to indicate the index of the 8-port fully coherent precoder.

[0150] Another option is to specify the parameters to generate an 8-port fully coherent precoder, i.e., one or some or all of the parameters i 1,1 , i 1,2 , i 1,3and i2 may be indicated. This indication may be done via one DCI field (e.g., one TPMI field, which may be divided into multiple parts, one part for each parameter) or via separate DCI fields (e.g., one field for each parameter). If only one value is used for a parameter (e.g., the only one value used is configured by higher layer signaling such as RRC / MAC-CE or is predefined), the bit length of the corresponding parameter is zero, i.e., not present in the DCI. For example, i 1,3 If the value of is set to 0, i 1,3 The bit length of is zero.

[0151] In one example, the parameter i 1,1 , i 1,2 , i 1,3 The bit length of i and i2 can vary depending on the value range of the parameter and the configured / predefined limits on the parameter. 1,1 , i 1,2 , i 1,3 The bit length of i1 and i2 is fixed, i.e., does not change due to the constraint.

[0152] Note: The various embodiments described above may be applied to the case of joint coding of the rank indicator and the precoder indicator in the DCI and / or to the case of separate coding of the rank indicator and the precoder indicator in the DCI.

[0153] In another embodiment, separate coding of the rank indicator and the precoder indicator in the DCI scheduling the PUSCH may be applied.

[0154] In a first option, one DCI field, e.g., the TPMI field, can be used for the rank indicator and the precoder indicator, where some bits of the DCI field can be used for the rank indication and some other bits can be used for the precoder indication.

[0155] In one example of the first option, one DCI field, e.g., the TPMI field, may be divided into two parts. One part, e.g., the first part, may be used for rank indication, and the other part, e.g., the second part, may be used for precoder indication. The bit length of the first part for rank indication may be fixed or may be determined by a predetermined or configured rank limit based on the maximum number of layers.

[0156] Additionally, the second part of the DCI field may indicate an 8-port fully coherent precoder, which may indicate an index of the 8-port fully coherent precoder.

[0157] Alternatively, the second part of the DCI field may indicate parameters for generating an 8-port fully coherent precoder, i.e., one or some or all of the parameters i 1,1 , i 1,2 , i 1,3 and i2 are indicated. 1,1 , i 1,2 , i 1,3 The bit length of i1 and i2 can vary depending on the value range of the parameter and the configured / predefined limits for the parameter. If only one value is used for a parameter (e.g., only one value used may be configured or predefined by RRC / MAC-CE), the bit length of the corresponding parameter is zero, i.e., not present in the DCI. In another example, parameter i 1,1 , i 1,2 , i 1,3 The bit length of i1 and i2 is fixed, i.e., does not change due to the constraint.

[0158] In the second option, separate DCI fields are used for the rank indicator and the precoder indicator, for example one DCI field, e.g. the TPMI field, is used for the precoder indicator and another DCI field (which may be newly added) is used for the rank indicator.

[0159] In one example of the second option, the DCI field for rank indication may be of fixed length, or the bit length of the rank indication field may be predetermined by the maximum number of layers or determined by a configured rank limit.

[0160] Furthermore, a DCI field for precoder indication, for example, a TPMI field, can indicate an 8-port fully coherent precoder, which can indicate the index of the 8-port fully coherent precoder.

[0161] Alternatively, the DCI field for precoder indication, e.g., the TPMI field, can indicate parameters for generating an 8-port fully coherent precoder, i.e., one, some, or all of the parameters i 1,1 , i 1,2 , i 1,3 and i2 are indicated. 1,1 , i 1,2 , i 1,3 The bit length of i1 and i2 can vary depending on the value range of the parameter and the configured / predefined limits for the parameter. If only one value is used for a parameter (e.g., only one value used may be configured or predefined by RRC / MAC-CE), the bit length of the corresponding parameter is zero, i.e., not present in the DCI. In another example, parameter i 1,1 , i 1,2 , i 1,3 The bit length of i1 and i2 is fixed, i.e., does not change due to the constraint.

[0162] In a third option, separate DCI fields may be used for the rank indicator and the precoder indicator. For example, one DCI field (e.g., a DCI field introduced in the 3GPP specification) may be used for the rank indicator. Additionally or alternatively, several DCI fields (e.g., newly introduced DCI fields) may be used to indicate parameters for generating an 8-port fully coherent precoder, i.e., one, several, or all of the parameters i 1,1 , i 1,2 , i 1,3 and i2 are indicated. In one example, each parameter may correspond to one field. Parameter i 1,1 , i 1,2 , i 1,3 The bit length of each field corresponding to i1 and i2 may vary depending on the value range of the parameter and the configured / predefined limits for the parameter. If only one value is used for a parameter (e.g., only one value can be configured or predefined by RRC / MAC-CE), the bit length of the corresponding parameter may be zero, i.e., not present in the DCI. In another example, the parameter i 1,1 , i 1,2 , i 1,3 The bit lengths of the fields corresponding to i1 and i2 are fixed, i.e., cannot be changed by restrictions.

[0163] In another embodiment, joint coding of the rank indicator and the precoder indicator may be applied in the DCI scheduling the PUSCH, and the index of the 8-port fully coherent precoder may be indicated, for example, via a TPMI field.

[0164] In these embodiments, the maximum rank of 8 refers to the number of MIMO transmission layers that can be supported. In some embodiments, the UE may decode a media access control (MAC) control element (MAC-CE) to determine restrictions on parameters used in generating one or more fully coherent precoders. In some embodiments, restrictions on parameters used in generating one or more fully coherent precoders may be determined from RRC signaling. [In some embodiments, coherence may be indicated by coherent (Ng=1), partially coherent (Ng=2, Ng=4), or non-coherent (Ng=8)]

[0165] A partially coherent precoder relies on partial knowledge of the channel coherence time when designing the precoder. A noncoherent precoder does not rely on any knowledge of the channel coherence time when designing the precoder.

[0166] Some embodiments are directed to a user equipment (UE) configured for operation in a fifth generation new radio (5G NR) network. The UE can decode a radio resource control (RRC) information element (IE) received from a gNodeB (gNB) to configure the UE with a codebook type for codebook-based physical uplink shared channel (PUSCH) transmissions using eight antenna ports and up to eight transmission layers. In these embodiments, the codebook type can have a coherency indication that can indicate one of a fully coherent codebook type, a partially coherent codebook type, and a non-coherent codebook type.

[0167] The UE may decode a downlink control information (DCI) format that schedules codebook-based PUSCH transmission for eight antenna ports. In these embodiments, the DCI format may indicate a transmit precoding matrix indicator (TPMI) index and the number of transmission layers for the PUSCH transmission. The UE may generate a precoding matrix (W) based on the TPMI index and the codebook type and encode the PUSCH for codebook-based PUSCH transmission using eight antenna ports and the indicated number of transmission layers by applying the generated precoding matrix.

[0168] In these embodiments, the UE may use a codebook based on the coherency indication to generate the precoding matrix (W). In some of these embodiments, the UE may use a first codebook (codebook 1; ng=1) when a fully coherent codebook type is indicated, a second codebook (codebook 4; ng=8) when a noncoherent codebook type is indicated, or a third or fourth codebook (codebook 2: ng=2 or codebook 3: ng=4) when a partially coherent codebook type is indicated to generate the precoding matrix (W).

[0169] In some embodiments, the number of transmission layers corresponds to a maximum of eight ranks. In these embodiments, the TPMI index and rank of the eight-port coherent precoder may be jointly indicated in a DCI format that schedules codebook-based PUSCH transmissions for eight antenna ports. In these embodiments, the codebook type indicates only one codebook type (i.e., either a fully coherent codebook type, a partially coherent codebook type, or a non-coherent codebook type).

[0170] In some embodiments, when the codebook type indicates a fully coherent codebook type, the processing circuitry may be configured to apply a restriction on parameters for use in generating the precoding matrix (W). In some embodiments, the restriction may limit the number of fully coherent precoders applied to the codebook-based PUSCH transmission. In some embodiments, the restriction on parameters used in generating the precoding matrix may be indicated in the DCI format.

[0171] In some embodiments, the RRC IE may include a PUSCH-Config IE to configure the UE with specific PUSCH parameters applicable to a particular bandwidth portion (BWP). In these embodiments, the codebook type may be indicated by the PUSCH-Config IE.

[0172] In some embodiments, restrictions on the parameters used in generating the precoding matrix may be based at least in part on rank.

[0173] In some embodiments, when the codebook type indicates one of a partially coherent codebook type and a non-coherent codebook type, the UE may generate a precoding matrix without restrictions on parameters.

[0174] In some embodiments, the UE may encode a UE capability information element that indicates, for transmission to the gNB, that the UE is capable of supporting codebook-based PUSCH transmission using eight antenna ports and up to eight transmission layers. In these embodiments, the UE capability information element may also indicate one of non-coherent, partially coherent, and fully coherent multiple-input multiple-output (MIMO) transmission depending on the number of transmission layers supported.

[0175] In some embodiments, the first codebook (codebook 1; ng=1) may be configured for one antenna port group (ng=1), the second codebook (codebook 4; ng=8) may be configured for eight antenna port groups (ng=8), the third codebook (codebook 2: ng=2) may be configured for two antenna port groups (ng=2), and the fourth codebook (codebook 3: ng=4) may be configured for four antenna port groups (ng=4).

[0176] In some embodiments, the UE may comprise processing circuitry that may include a baseband processor, hi some embodiments, the UE may comprise a memory configured to store a precoding matrix.

[0177] Some embodiments are directed to a computer-readable storage medium storing instructions for execution by processing circuitry of a user equipment (UE) configured for operation in a fifth generation new radio (5G NR) network.

[0178] Some embodiments are directed to a gNodeB (gNB) configured for operation in a fifth generation new radio (5G NR) network. In these embodiments, the gNB may encode a radio resource control (RRC) information element (IE) for transmission to a user equipment (UE) to configure the UE with a codebook type for codebook-based physical uplink shared channel (PUSCH) transmission using eight antenna ports and up to eight transmission layers. In these embodiments, the codebook type may indicate one of a fully coherent codebook type, a partially coherent codebook type, and a non-coherent codebook type. In these embodiments, the gNB may encode a downlink control information (DCI) format that schedules the codebook-based PUSCH transmission of the eight antenna ports for transmission to the UE. The DCI format may indicate a transmit precoding matrix indicator (TPMI) index and the number of transmission layers.

[0179] In these embodiments, the gNB may decode a PUSCH received from the UE, including a codebook-based PUSCH transmission using eight antenna ports and an indicated number of transmission layers. The codebook-based PUSCH transmission for the eight antenna ports may be based on application of a precoding matrix (W) generated by the UE based on the TPMI index and codebook type. In some embodiments, when a fully coherent codebook type is indicated, a first codebook (codebook 1; ng=1) may be used to generate the precoding matrix (W), when a non-coherent codebook type is indicated, a second codebook (codebook 4; ng=8) may be used to generate the precoding matrix (W), and when a partially coherent codebook type is indicated, a third or fourth codebook (codebook 2: ng=2 or codebook 3: ng=4) may be used to generate the precoding matrix (W).

[0180] Example

[0181] Example 1 may include a gNB, where the gNB may configure a UE for 8Tx PUSCH transmission.

[0182] Example 2 may include the method of Example 1 or any other example herein, where the codebook subsets may be configured by the gNB and include a fullyAndPartialAndNonCoherent codebook subset, a partialAndNonCoherent codebook subset, and a nonCoherent codebook subset.

[0183] Example 3 may include the method of example 2 or any other example herein, where, for an 8-Tx UE, the fullyAndPartialAndNonCoherent codebook subset includes a fully coherent precoder, a partial coherent precoder, and a noncoherent precoder, the partialAndNonCoherent codebook subset includes a partial coherent precoder and a noncoherent precoder, and the noncoherent codebook subset includes a noncoherent precoder.

[0184] Example 4 may include the method of example 1 or any other example herein, where in the DCI scheduling the PUSCH, the DCI may also indicate whether a fully coherent precoder, a partially coherent precoder, or a non-coherent precoder is indicated in a TPMI field within the DCI, i.e., may indicate precoder coherence via the DCI.

[0185] Example 5 may include the method of example 1 or any other example herein, where the precoder coherence indication may be via a new DCI field. Alternatively, some existing DCI fields may be reused, or some special code points of some DCI fields may be used for the precoder coherence indication.

[0186] Example 6 may include the method of Examples 1 to 4 or any other example herein, where the precoder coherence indication may be via MAC-CE or configured by RRC signaling.

[0187] Example 7 may include the method of Examples 1 to 6 or any other example herein, where, when the fullyAndPartialAndNonCoherent codebook subset is configured, the precoder coherence indication may indicate whether a fully coherent precoder, a partially coherent precoder, or a noncoherent precoder is indicated in a TPMI field in the DCI, and one TPMI field may be configured in the DCI.

[0188] Example 8 may include the method of Example 7 or any other example herein, wherein when the precoder coherence indication indicates a fully coherent precoder, the TPMI field may indicate an 8-port fully coherent precoder based on a DL Type I codebook.

[0189] Example 9 may include the method of example 7 or any other example herein, where when the precoder coherence indication indicates a partially coherent precoder, the TPMI field may indicate: One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder

[0190] Example 10 may include the method of example 7 or any other example herein, where when the precoder coherence indication indicates a non-coherent precoder, the TPMI field may indicate: One 8-port non-coherent precoder Two 4-Tx precoding matrices for constructing an 8-port noncoherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder

[0191] Example 11 may include the method of example 7 or any other example herein, where the TPMI field size may be determined by the maximum bit widths required for the fully coherent precoder, the partially coherent precoder, and the non-coherent precoder.

[0192] Example 12 may include the method of Examples 1 to 6 or some other example herein, where, when the partialAndNonCoherent codebook subset is configured, the precoder coherence indication may indicate whether a partial coherent precoder or a noncoherent precoder is indicated in a TPMI field in the DCI, and one TPMI field may be configured in the DCI.

[0193] Example 13 may include the method of Example 12 or any other example herein, where when the precoder coherence indication indicates a partially coherent precoder, the TPMI field may indicate: One 4-Tx precoding matrix or two 4-Tx precoding matrices to build an 8-port partially coherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder

[0194] Example 14 may include the method of example 12 or any other example herein, where when the precoder coherence indication indicates a non-coherent precoder, the TPMI field may indicate: One 8-port non-coherent precoder Two 4-Tx precoding matrices for constructing an 8-port noncoherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder

[0195] Example 15 may include the method of Examples 1 to 6 or some other example herein, where, when a nonCoherent codebook subset is configured, a nonCoherent precoder is indicated in a TPMI field in the DCI. Also, one TPMI field may be configured in the DCI.

[0196] Example 16 may include the method of example 15 or any other example herein, where the TPMI field may indicate: One 8-port non-coherent precoder Two 4-Tx precoding matrices for constructing an 8-port noncoherent precoder One 2Tx precoding matrix and one 4Tx precoding matrix to build an 8-port partially coherent precoder

[0197] Example 17 may include the method of example 15 or any other example herein, where the TPMI field size may be determined by a bit width required for the non-coherent precoder.

[0198] Example 18 includes a method performed by a user equipment (UE), one or more elements of a UE, and / or an electronic device that includes and / or implements a UE, the method comprising: - identifying, from a base station, an indication of a codebook subset associated with an uplink (UL) transmission using eight transmit ports; ● Transmitting UL transmissions over eight transmit ports based on the codebook subset; Includes:

[0199] Example 19 may include the method of example 18 and / or any other example herein, where the UL transmission is a UL Physical Uplink Shared Channel (PUSCH) transmission.

[0200] Example 20 may include the method of any of Examples 18-19 and / or any other example herein, wherein the codebook subset is a fullyAndPartialAndNonCoherent codebook subset including a fully coherent precoder, a partially coherent precoder, and a noncoherent precoder.

[0201] Example 21 may include the method of any of Examples 18-20 and / or some other examples herein, wherein the codebook subset is a partialAndNonCoherent codebook subset including a partial coherent precoder and a noncoherent precoder.

[0202] Example 22 may include the method of any of Examples 18-21 and / or some other examples herein, wherein the codebook subset is a nonCoherent codebook subset that includes a nonCoherent precoder.

[0203] Example 23 may include the method of any of Examples 18-22 and / or any other example herein, where the indication of the codebook subset is signaled in downlink control information (DCI).

[0204] Example 24 may include the method of any of Examples 18-22 and / or any other example herein, where the indication of the codebook subset is signaled in radio resource control (RRC) signaling.

[0205] Example 25 may include the method of any of Examples 18-22 and / or any other example herein, where the indication of the codebook subset is signaled in media access control (MAC)-control element (CE) signaling.

[0206] Example 26 includes a method performed by a base station, one or more elements of a base station, and / or an electronic device that includes and / or implements a base station, the method comprising: transmitting to a user equipment (UE) an indication of a codebook subset associated with an uplink (UL) transmission using eight transmit ports; - identifying, from the UE, UL transmissions via eight transmit ports based on the codebook subset; Includes:

[0207] Example 27 may include the method of Example 26 and / or any other example herein, where the UL transmission is a UL Physical Uplink Shared Channel (PUSCH) transmission.

[0208] Example 28 may include the method of any of Examples 26-27 and / or any other example herein, where the codebook subset is a fullyAndPartialAndNonCoherent codebook subset including a fully coherent precoder, a partially coherent precoder, and a noncoherent precoder.

[0209] Example 29 may include the method of any of Examples 26-28 and / or some other examples herein, where the codebook subset is a partialAndNonCoherent codebook subset that includes a partial coherent precoder and a noncoherent precoder.

[0210] Example 30 may include the method of any of Examples 26-29 and / or some other examples herein, wherein the codebook subset is a nonCoherent codebook subset that includes a nonCoherent precoder.

[0211] Example 31 may include the method of any of Examples 26-30 and / or some other examples herein, where the indication of the codebook subset is signaled in downlink control information (DCI).

[0212] Example 32 may include the method of any of Examples 26-30 and / or some other examples herein, where the indication of the codebook subset is signaled in radio resource control (RRC) signaling.

[0213] Example 33 may include the method of any of Examples 26-30 and / or any other example herein, where the indication of the codebook subset is signaled in media access control (MAC)-control element (CE) signaling.

[0214] Additional Examples

[0215] Example 1 may include a gNB, where the gNB may configure a fully coherent UE with 8-port PUSCH transmission.

[0216] Example 2 may include the method of example 1 or any other example herein, where the fully coherent precoder is based on a Rel-15 DL Type I codebook.

[0217] Example 3 may include the method of examples 1 and 2 or some other example herein, wherein the parameters for generating a fully coherent precoder, i.e., i 1,1 , i 1,2 , i 1,3 A restriction can be introduced on i and i2 such that only a subset of values ​​are allowed / used to generate a fully coherent precoder.

[0218] Example 4 may include the method of Example 3 or any other example herein, wherein one or some or all of the parameters i 1,1 , i 1,2 , i 1,3 and i2 can be configured by RRC, updated by MAC-CE, or indicated by DCI. The restriction indicates the allowed values. The restriction can be a bitmap.

[0219] Example 5 may include the method of Example 3 or any other example herein, wherein one or some or all of the parameters i 1,1 , i 1,2 , i 1,3 and limits on i2 can be predefined in the physical layer specification.

[0220] Example 6 may include the method of Example 3 or any other example herein, wherein one or some or all of the parameters i 1,1 , i 1,2 , i 1,3 Limits on i and i2 can be configured or predefined for each rank. The limits can be the same or different for different ranks.

[0221] Example 7 may include the method of Example 3 or any other example herein, wherein one, some, or all of the parameters i 1,1 , i 1,2 , i 1,3The limits on i and i2 can be configured or predefined across ranks. The limits can be the same across different ranks.

[0222] Example 8 may include the method of Examples 1 and 2 or any other example herein, where the value of the oversampling factor for the 8-port fully coherent precoder, i.e., (O1,O2)=(1,1) or (2,1) or (2,2), may be configured by RRC, updated by MAC-CE, indicated by DCI, or predefined in a physical layer specification.

[0223] Example 9 may include the method of Examples 1 and 2 or some other example herein, where linear indexing may be defined for an 8-port fully coherent precoder.

[0224] Example 10 may include the method of Examples 1 and 2 or any other example herein, where the DCI scheduling the PUSCH may indicate an 8-port fully coherent precoder or indicate parameters for generating the 8-port fully coherent precoder.

[0225] Example 11 may include the method of Example 10 or any other example herein, where an 8-port fully coherent precoder is indicated. The indication may be via one TPMI field to indicate an index of the 8-port fully coherent precoder.

[0226] Example 12 may include the method of Example 10 or any other example herein, wherein the parameters for generating an 8-port fully coherent precoder, i.e., i 1,1 , i 1,2 , i 1,3and i2 are indicated. The indication can be made via one DCI field (for example, one TPMI field, which can be divided into multiple parts, one part for each parameter), or via separate DCI fields (for example, one field for each parameter). If only one value is used for a particular parameter (the only one value used can be configured or predefined by RRC / MAC-CE), the bit length of the corresponding parameter is zero, i.e., not present in the DCI. For example, i 1,3 If the value of is set to 0, i 1,3 The bit length of is zero.

[0227] Example 13 may include the method of Example 12 or any other example herein, wherein the parameter i 1,1 , i 1,2 , i 1,3 The bit length of i and i2 can vary depending on the range of values ​​of the parameter and the configured / predefined limits for the parameter. 1,1 , i 1,2 , i 1,3 The bit length of i1 and i2 is fixed, i.e., does not change due to the constraint.

[0228] Example 14 may include the method of Examples 1 and 2 or any other example herein, where separate coding of the rank indicator and the precoder indicator in the DCI scheduling the PUSCH may be applied.

[0229] Example 15 may include the method of Example 14 or any other example herein, where one DCI field, e.g., a TPMI field, is used for the rank indicator and the precoder indicator, and a portion of the DCI field can be used for the rank indication and another portion can be used for the precoder indication.

[0230] Example 16 may include the method of Example 14 or some other example herein, where separate DCI fields are used for the rank indicator and the precoder indicator, e.g., one DCI field, e.g., a TPMI field, is used for the precoder indicator and another DCI field (which may be newly added) is used for the rank indicator.

[0231] Example 17 may include the method of Example 14 or any other example herein, where separate DCI fields are used for the rank indicator and the precoder indicator. For example, one DCI field (which may be newly added) is used for the rank indicator. Another DCI field (which may be newly added) is used to indicate parameters for generating an 8-port fully coherent precoder, i.e., one, some, or all of the parameters i 1,1 , i 1,2 , i 1,3 and i2 are indicated.

[0232] Example 18 may include the method of Examples 1 and 2 or some other example herein, where joint coding of a rank indicator and a precoder indicator can be applied in the DCI scheduling the PUSCH, and an index of the 8-port fully coherent precoder can be indicated, for example, via a TPMI field.

[0233] Example 19 includes a method performed by a user equipment (UE), one or more elements of the user equipment (UE), and / or one or more electronic devices that include and / or implement the UE, the method comprising: Identifying that a UE transmits a Physical Uplink Shared Channel (PUSCH) transmission on more than four transmit ports; generating a fully coherent precoder to be used for the PUSCH transmission based on constraints related to values ​​used to generate the fully coherent precoder; Transmitting PUSCH transmissions on more than four transmit ports based on a fully coherent precoder; and Includes:

[0234] Example 20 may include the method of example 19 and / or any other example herein, where the PUSCH transmission is transmitted on eight transmit ports.

[0235] Example 21 may include the method of any of Examples 19-20 and / or any other example herein, where the fully coherent precoder is further generated based on a 3rd Generation Partnership Project (3GPP) Release-15 (Rel-15) downlink (DL) Type-1 codebook.

[0236] Example 22 may include the method of any of Examples 19-21 and / or any other example herein, where the restriction relates to a subset of values ​​in a 3GPP Rel-15 DL Type 1 codebook that may be used to generate the fully coherent precoder.

[0237] Example 23 may include the method of any of Examples 19-22 and / or some other examples herein, where the method further includes identifying the restriction based on radio resource control (RRC) signaling.

[0238] Example 24 may include the method of any of Examples 19-22 and / or any other example herein, where the method further includes identifying the restriction based on a media access control-control element (MAC-CE) signal.

[0239] Example 25 may include the method of any of Examples 19-22 and / or any other example herein, where the method further includes identifying the restriction based on downlink control information (DCI).

[0240] Example 26 may include the method of any of Examples 19-22 and / or any other example herein, where the method further includes identifying the restriction based on the bitmap.

[0241] Example 27 may include the method of any of Examples 19-22 and / or any other example herein, where the constraint is pre-configured.

[0242] Example 28 includes a method performed by a base station, one or more elements of a base station, and / or an electronic device that includes and / or implements a base station, the method comprising: identifying a physical uplink shared channel (PUSCH) transmission transmitted from a user equipment (UE) on more than four transmit ports, the PUSCH transmission being transmitted based on a fully coherent precoder, the fully coherent precoder being based on a restriction associated with values ​​used to generate the fully coherent precoder; Processing PUSCH transmissions; and Includes:

[0243] Example 29 may include the method of example 28 and / or any other example herein, where the PUSCH transmission is sent on eight transmit ports.

[0244] Example 30 may include the method of any of Examples 28-29 and / or any other example herein, where the fully coherent precoder is further based on a 3rd Generation Partnership Project (3GPP) Release-15 (Rel-15) downlink (DL) Type-1 codebook.

[0245] Example 31 may include the method of any of Examples 28-30 and / or some other examples herein, where the restriction relates to a subset of values ​​in a 3GPP Rel-15 DL Type 1 codebook that may be used to generate the fully coherent precoder.

[0246] Example 32 may include the method of any of Examples 28-30 and / or some other examples herein, where the method further includes transmitting an indication of the restriction to the UE in radio resource control (RRC) signaling.

[0247] Example 33 may include the method of any of Examples 28-30 and / or some other examples herein, where the method further includes transmitting an indication of the restriction in a media access control-control element (MAC-CE) signal to the UE.

[0248] Example 34 may include the method of any of Examples 28-30 and / or some other examples herein, where the method further includes transmitting an indication of the restriction in downlink control information (DCI) to the UE.

[0249] Example 35 may include the method of any of Examples 28-30 and / or any other example herein, where the constraint is based on a bitmap.

[0250] Example 36 may include the method of any of Examples 28-30 and / or any other example herein, where the constraint is pre-configured.

[0251] The Abstract is provided to comply with 37 C.F.R. Section 1.72(b), requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

1. 1. An apparatus for user equipment (UE) configured for operation in a fifth generation new radio (5G NR) network, the apparatus comprising: a processing circuit; and a memory; the processing circuit: decoding a radio resource control (RRC) information element (IE) received from a gNodeB (gNB) to configure the UE with a codebook type for codebook-based physical uplink shared channel (PUSCH) transmission using eight antenna ports and up to eight transmission layers, where the codebook type indicates one of a fully coherent codebook type, a partially coherent codebook type, and a non-coherent codebook type; Decode a downlink control information (DCI) format that schedules the codebook-based PUSCH transmission using the eight antenna ports, where the DCI format indicates a transmit precoding matrix indicator (TPMI) index and a number of transmission layers; generating a precoding matrix based on the TPMI index and the codebook type; Encoding a PUSCH for the codebook-based PUSCH transmission using the eight antenna ports and the indicated number of transmission layers by applying the generated precoding matrix. It is configured as follows: To generate the precoding matrix, the processing circuitry When the fully coherent codebook type is indicated, a first codebook is used; using a second codebook when the non-coherent codebook type is indicated; When the partially coherent codebook type is indicated, use the third or fourth codebook. The apparatus is configured to:

2. The number of transmission layers corresponds to a maximum of 8 ranks; The TPMI index and rank for an 8-port coherent precoder are jointly indicated in the DCI format scheduling the codebook-based PUSCH transmission using 8 antenna ports.

10. The apparatus of claim 1.

3. When the codebook type indicates the fully coherent codebook type, the processing circuitry is configured to apply a restriction to parameters used in generating the precoding matrix, the restriction limiting the number of the fully coherent precoders applied to the codebook-based PUSCH transmission.

3. The apparatus of claim 2.

4. the restrictions on the parameters used in generating the precoding matrix are indicated in the DCI format.

4. The apparatus of claim 3.

5. The RRC IE includes a PUSCH-Config IE for configuring the UE with specific PUSCH parameters applicable to a specific bandwidth portion; The codebook type is indicated by the PUSCH-Config IE.

5. The apparatus of claim 4.

6. the restriction on the parameters used in generating the precoding matrix is ​​based at least in part on the rank.

6. The apparatus of claim 5.

7. When the codebook type indicates one of the partially coherent codebook type and the non-coherent codebook type, the processing circuitry is configured to generate the precoding matrix without the restriction on parameters.

7. The apparatus of claim 6.

8. The processing circuitry is configured to encode a UE capability information element indicating that the UE can support the codebook-based PUSCH transmission using eight antenna ports and up to eight transmission layers for transmission to the gNB, and the UE capability information element further indicates one of non-coherent, partially coherent, and fully coherent for multiple-input multiple-output (MIMO) transmission depending on the number of transmission layers supported.

4. The apparatus of claim 3.

9. the first codebook is configured for one antenna port group, the second codebook is configured for eight antenna port groups, the third codebook is configured for two antenna port groups, and the fourth codebook is configured for four antenna port groups; 4. The apparatus of claim 3.

10. the processing circuit includes a baseband processor, and the memory is configured to store the precoding matrix.

10. The apparatus of claim 1.

11. 1. A computer-readable storage medium storing instructions for execution by a processing circuit of a user equipment (UE) configured for operation in a fifth generation new radio (5G NR) network, the processing circuit comprising: decoding a radio resource control (RRC) information element (IE) received from a gNodeB (gNB) to configure the UE with a codebook type for codebook-based physical uplink shared channel (PUSCH) transmission using eight antenna ports and up to eight transmission layers, where the codebook type indicates one of a fully coherent codebook type, a partially coherent codebook type, and a non-coherent codebook type; Decode a downlink control information (DCI) format that schedules the codebook-based PUSCH transmission using the eight antenna ports, where the DCI format indicates a transmit precoding matrix indicator (TPMI) index and a number of transmission layers; generating a precoding matrix based on the TPMI index and the codebook type; Encoding a PUSCH for the codebook-based PUSCH transmission using the eight antenna ports and the indicated number of transmission layers by applying the generated precoding matrix. It is configured as follows: To generate the precoding matrix, the processing circuitry When the fully coherent codebook type is indicated, a first codebook is used; using a second codebook when the non-coherent codebook type is indicated; When the partially coherent codebook type is indicated, use the third or fourth codebook. A computer-readable storage medium configured to:

12. The number of transmission layers corresponds to a maximum of 8 ranks; The TPMI index and rank for an 8-port coherent precoder are jointly indicated in the DCI format scheduling the codebook-based PUSCH transmission using 8 antenna ports. The computer-readable storage medium of claim 11.

13. When the codebook type indicates the fully coherent codebook type, the processing circuitry is configured to apply a restriction to parameters used in generating the precoding matrix, the restriction limiting the number of the fully coherent precoders applied to the codebook-based PUSCH transmission.

13. The computer-readable storage medium of claim 12.

14. the restrictions on the parameters used in generating the precoding matrix are indicated in the DCI format.

14. The computer-readable storage medium of claim 13.

15. The RRC IE includes a PUSCH-Config IE for configuring the UE with specific PUSCH parameters applicable to a specific bandwidth portion; The codebook type is indicated by the PUSCH-Config IE.

15. The computer-readable storage medium of claim 14.

16. the restriction on the parameters used in generating the precoding matrix is ​​based at least in part on the rank.

16. The computer-readable storage medium of claim 15.

17. When the codebook type indicates one of the partially coherent codebook type and the non-coherent codebook type, the processing circuitry is configured to generate the precoding matrix without the restriction on parameters.

17. The computer-readable storage medium of claim 16.

18. The processing circuitry is configured to encode a UE capability information element indicating that the UE can support the codebook-based PUSCH transmission using eight antenna ports and up to eight transmission layers for transmission to the gNB, and the UE capability information element further indicates one of non-coherent, partially coherent, and fully coherent for multiple-input multiple-output (MIMO) transmission depending on the number of transmission layers supported.

14. The computer-readable storage medium of claim 13.

19. 1. An apparatus for a gNodeB (gNB) configured for operation in a fifth generation new radio (5G NR) network, the apparatus comprising: a processing circuit; and a memory; encoding a radio resource control (RRC) information element (IE) for transmission to a user equipment (UE) to configure the UE with a codebook type for codebook-based physical uplink shared channel (PUSCH) transmission using eight antenna ports and up to eight transmission layers, where the codebook type indicates one of a fully coherent codebook type, a partially coherent codebook type, and a non-coherent codebook type; Encode for transmission to the UE a downlink control information (DCI) format that schedules the codebook-based PUSCH transmission using the eight antenna ports, where the DCI format indicates a transmit precoding matrix indicator (TPMI) index and a number of transmission layers; Decode a PUSCH including the codebook-based PUSCH transmission using the eight antenna ports and the indicated number of transmission layers received from the UE, where the codebook-based PUSCH transmission using the eight antenna ports is based on application of a precoding matrix generated by the UE based on the TPMI index and the codebook type. It is configured as follows: When the fully coherent codebook type is indicated, a first codebook is used to generate the precoding matrix; When the non-coherent codebook type is indicated, a second codebook is used to generate the precoding matrix; When the partially coherent codebook type is indicated, a third or fourth codebook is used to generate the precoding matrix. Device.

20. The number of transmission layers corresponds to a maximum of 8 ranks; The TPMI index and rank for an 8-port coherent precoder are jointly indicated in the DCI format scheduling the codebook-based PUSCH transmission using 8 antenna ports.

20. The apparatus of claim 19.

Images