WO2023177547A1 - Améliorations de transmission en liaison montante à huit ports - Google Patents

Améliorations de transmission en liaison montante à huit ports Download PDF

Info

Publication number
WO2023177547A1
WO2023177547A1 PCT/US2023/014610 US2023014610W WO2023177547A1 WO 2023177547 A1 WO2023177547 A1 WO 2023177547A1 US 2023014610 W US2023014610 W US 2023014610W WO 2023177547 A1 WO2023177547 A1 WO 2023177547A1
Authority
WO
WIPO (PCT)
Prior art keywords
ports
port
tpmi
phasing
codebook
Prior art date
Application number
PCT/US2023/014610
Other languages
English (en)
Inventor
Guotong Wang
Alexei Davydov
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Publication of WO2023177547A1 publication Critical patent/WO2023177547A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H04B7/0456—Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
    • H04B7/0478—Special codebook structures directed to feedback optimisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
    • H04B7/06956—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping using a selection of antenna panels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling

Definitions

  • Embodiments pertain to wireless communications. Some embodiments relate to uplink transmission with eight ports.
  • FIG.1A illustrates an architecture of a network, in accordance with some aspects.
  • FIG.1B illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • FIG. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.
  • FIG. 3 illustrates a partial coherent user equipment (UE) with four panels in accordance with some embodiments.
  • FIG. 4 illustrates a partial coherent UE with two panels in accordance with some embodiments.
  • FIG. 5 illustrates a partial coherent UE with a power amplifier (PA) of 17dBm in accordance with some embodiments.
  • PA power amplifier
  • FIG. 6 illustrates downlink control information (DCI) in accordance with some embodiments.
  • FIG. 7 illustrates Transmit Precoder Matrix Indicator (TPMI) operation in accordance with some embodiments.
  • TPMI Precoder Matrix Indicator
  • FIG. 8 illustrates another TPMI operation in accordance with some embodiments.
  • FIG. 9 illustrates another TPMI operation in accordance with some embodiments.
  • FIG. 10 illustrates a sounding reference signal (SRS) configuration for codebook-based transmission in accordance with some embodiments.
  • SRS sounding reference signal
  • FIG. 11 illustrates DCI-based switching between different ports for codebook-based transmission in accordance with some embodiments.
  • FIG. 12 illustrates a UE with port-dependent coherence in accordance with some embodiments.
  • FIG. 13 illustrates a UE with port-dependent coherence in accordance with some embodiments.
  • FIG. 14 illustrates a UE with port-dependent coherence in accordance with some embodiments.
  • FIG. 15 illustrates a UE with port-dependent coherence in accordance with some embodiments.
  • FIG. 16 illustrates a UE with port-dependent full power mode in accordance with some embodiments.
  • FIG. 1 A illustrates an architecture of a network in accordance with some aspects.
  • the network 140A includes 3GPP LTE/4G and NG network functions that may be extended to 6G and later generation functions.
  • a network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.
  • the network 140A is shown to include user equipment (UE) 101 and UE 102.
  • the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface.
  • the UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.
  • Any of the radio links described herein may operate according to any exemplary radio communication technology and/or standard.
  • Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies).
  • LSA Licensed Shared Access
  • SAS Spectrum Access System
  • OFDM Orthogonal Frequency Domain Multiplexing
  • SC-FDMA SC-FDMA
  • SC-OFDM filter bank-based multicarrier
  • OFDMA OFDMA
  • 3GPP NR 3GPP NR
  • any of the UEs 101 and 102 can comprise an Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections.
  • any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB-IoT
  • FeNB-IoT Further Enhanced
  • An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the loT UEs may execute background applications (e g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network.
  • any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
  • the UEs 101 and 102 may be configured to connect, e g., communicatively couple, with a radio access network (RAN) 110.
  • the 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.
  • the RAN 110 may contain one or more gNBs, one or more of which may be implemented by multiple units. Note that although gNBs may be referred to herein, the same aspects may apply to other generation NodeBs, such as 6 th generation NodeBs - and thus may be alternately referred to as next generation NodeB (xNB).
  • xNB next generation NodeB
  • Each of the gNBs may implement protocol entities in the 3GPP protocol stack, in which the layers are considered to be ordered, from lowest to highest, in the order Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Control (PDCP), and Radio Resource Control (RRC)/Service Data Adaptation Protocol (SDAP) (for the control plane/user plane).
  • the protocol layers in each gNB may be distributed in different units - a Central Unit (CU), at least one Distributed Unit (DU), and a Remote Radio Head (RRH).
  • the CU may provide functionalities such as the control the transfer of user data, and effect mobility control, radio access network sharing, positioning, and session management, except those functions allocated exclusively to the DU.
  • the higher protocol layers may be implemented in the CU, and the RLC and MAC layers may be implemented in the DU.
  • the PHY layer may be split, with the higher PHY layer also implemented in the DU, while the lower PHY layer is implemented in the RRH.
  • the CU, DU and RRH may be implemented by different manufacturers, but may nevertheless be connected by the appropriate interfaces therebetween.
  • the CU may be connected with multiple DUs.
  • the interfaces within the gNB include the El and front-haul (F) Fl interface.
  • the El interface may be between a CU control plane (gNB-CU- CP) and the CU user plane (gNB-CU-UP) and thus may support the exchange of signalling information between the control plane and the user plane through El AP service.
  • the El interface may separate Radio Network Layer and Transport Network Layer and enable exchange of UE associated information and non-UE associated information.
  • the El AP services may be non UE- associated services that are related to the entire El interface instance between the gNB-CU-CP and gNB-CU-UP using anon UE-associated signalling connection and UE-associated services that are related to a single UE and are associated with a UE-associated signalling connection that is maintained for the UE.
  • the Fl interface may be disposed between the CU and the DU.
  • the CU may control the operation of the DU over the Fl interface.
  • the F l interface may be split into the Fl -C interface for control plane signalling between the gNB-DU and the gNB-CU-CP, and the Fl-U interface for user plane signalling between the gNB-DU and the gNB-CU-UP, which support control plane and user plane separation.
  • the Fl interface may separate the Radio Network and Transport Network Layers and enable exchange of UE associated information and non-UE associated information.
  • an F2 interface may be between the lower and upper parts of the NR PHY layer.
  • the F2 interface may also be separated into F2-C and F2-U interfaces based on control plane and user plane functionalities.
  • the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE 3GPP Long Term Evolution
  • the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105.
  • the ProSe interface 105 may alternatively be referred to as a sidelink (SL) 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), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • PSFCH Physical Sidelink Feedback Channel
  • the UE 102 is shown to be configured to access an access point (AP) 106 via connection 107.
  • the connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 110 can include one or more access nodes that enable the connections 103 and 104.
  • These access nodes can be referred to as E2 nodes, base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the communication nodes 111 and 112 can be transmission-reception points (TRPs).
  • the RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.
  • RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • any of the nodes 111 and/or 112 can be a gNB, an eNB, or another type of RAN node.
  • the RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113.
  • the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C).
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 1 1 1 and 1 12 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signalling interface betw een the RAN nodes 111 and 112 and MMEs
  • the CN 120 comprises the MMEs 121, the S-GW
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the EISS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120.
  • the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility.
  • Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a PDN.
  • the P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • the P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks.
  • the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125.
  • the application server 184 can 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 UEs 101 and 102 via the CN 120.
  • VoIP Voice-over-Internet Protocol
  • the P-GW 123 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120.
  • PCRF Policy and Charging Rules Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • H-PCRF Home PCRF
  • V-PCRF Visited PCRF
  • the PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.
  • the communication network 140A can be an loT network or a 5G or 6G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
  • NB-IoT narrowband-IoT
  • Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an “anchor” in the licensed spectrum, called MulteFire.
  • Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems.
  • Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications.
  • An NG system architecture can include the RAN 110 and a core network (CN) 120.
  • the NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs.
  • the CN 120 e.g., a 5G core network (5GC)
  • the AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces.
  • the gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.
  • the NG system architecture can use reference points between various nodes.
  • each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
  • MN master node
  • SN secondary node
  • FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • FIG. IB illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture.
  • UE 102 can be in communication with RAN 110 as well as one or more other CN network entities.
  • the 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.
  • NFs network functions
  • AMF session management function
  • PCF policy control function
  • AF application function
  • UPF network slice selection function
  • AUSF authentication server function
  • UDM unified data management
  • HSS home subscriber server
  • the UPF 134 can provide a connection 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 AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies.
  • the SMF 136 can be configured to set up and manage various sessions according to network policy.
  • the SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs.
  • the SMF 136 may also select and control the UPF 134 for data transfer.
  • the SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other
  • the UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network.
  • the PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to 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).
  • the AF 150 may provide information on the packet flow to the PCF 148 responsible for policy control to support a desired QoS.
  • the PCF 148 may set mobility and session management policies for the UE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136.
  • the AUSF 144 may store data for UE authentication.
  • the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 1 8B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B.
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B.
  • the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP.
  • the I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area.
  • the I-CSCF 166B can be connected to another IP multimedia network 170B, e g. an IMS operated by a different network operator.
  • the UDM/HSS 146 can be coupled to an application server (AS) 160B, which can include a telephony application server (TAS) or another application server.
  • AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.
  • FIG. IB illustrates 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 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Ni l (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
  • FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation.
  • system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.
  • NEF network exposure function
  • NRF network repository function
  • 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces.
  • service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services.
  • 5G system architecture 140C can include the following servicebased interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), aNudm 158E (a servicebased interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF 144
  • NR-V2X architectures may support high-reliability low latency sidelink communications with a variety' of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size.
  • Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.
  • FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments, such as an evolved Node-B (eNB), a new generation Node-B (gNB) (or another RAN node), an access point (AP), a wireless station (STA), a mobile station (MS), or user equipment (UE), in accordance with some aspects and to perform one or more of the techniques disclosed herein.
  • the communication device 200 may operate as a standalone device or may be connected (e g., networked) to other communication devices.
  • the communication device may be any machine capable of executing instructions (sequential or otherw ise) that specify actions to be taken by that machine.
  • the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1A-1C.
  • communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules and components are tangible entities (e g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a machine readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e g., hardwired), or temporarily (e g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using software
  • the general-purpose hardware processor may be configured as respective different modules at different times.
  • Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • the communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208.
  • the main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory.
  • the communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse).
  • UI user interface
  • the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display.
  • the communication device 200 may additionally include a storage device (e g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor.
  • GPS global positioning system
  • the communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • USB universal serial bus
  • IR infrared
  • NFC near field communication
  • the storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200.
  • the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.
  • machine readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media.
  • machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory' (RAM); and CD-ROM and DVD-ROM disks.
  • non-volatile memory such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., electrically Erasable Programmable Read-Only Memory (EEPROM)
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.
  • the instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • WLAN wireless local area network
  • Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks.
  • LAN local area network
  • WAN wide area network
  • POTS Plain Old Telephone
  • Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5 th generation (5G) standards among others.
  • the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the transmission medium 226.
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory' (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry or “processor” as used herein thus refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • processor circuitry or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes.
  • any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High
  • 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel.
  • V2V Vehicle-to-Vehicle
  • V2X Vehicle-to-X
  • V2I Vehicle-to- Infrastructure
  • I2V Infrastructure-to-Vehicle
  • 3GPP cellular V2X DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)
  • DSRC Dedicated Short Range Communications
  • Intelligent-Transport-Systems and others typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)
  • the European ITS-G5 system i.e.
  • ITS-G5A i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety related applications in the frequency range 5,875 GHz to 5,905 GHz
  • ITS-G5B i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz
  • ITS-G5C i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz
  • DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802. 1 Ibd based systems, etc.
  • LSA Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies
  • Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300 220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology' family (1 Ib/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790
  • Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and
  • aspects described herein can also implement a hierarchical application of the scheme is possible, e.g., by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.
  • a hierarchical prioritization of usage for different types of users e.g., low/medium/high priority, etc.
  • a prioritized access to the spectrum e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc. users, etc.
  • 5G networks extend beyond the traditional mobile broadband services to provide various new services such as internet of things (loT), industrial control, autonomous driving, mission critical communications, etc. that may have ultra-low latency, ultra-high reliability, and high data capacity requirements due to safety and performance concerns.
  • Some of the features in this document are defined for the network side, such as APs, eNBs, NR or gNBs - note that this term is typically used in the context of 3 GPP 5G and 6G communication systems, etc.
  • a UE may take this role as well and act as an AP, eNB, or gNB; that is some or all features defined for network equipment may be implemented by a UE.
  • the precoders (TPMIs) for uplink physical uplink shared channel (PUSCH) transmissions are defined in TS 38.21 1 , depending on the rank value (number of layers), the number of antenna ports and waveform (cyclic prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) or discrete Fourier transform spread OFDM (DFT-s-OFDM)), as shown in the tables below:
  • TPMI Table 1 TPMIs for Rank-1 with two antenna ports
  • TPMI Table 2 TPMIs for Rank-2 with two antenna ports (CP-OFDM)
  • Table 6.3.1.5-2 Precoding matrix IF for single-layer transmission using four antenna ports with transform precoding enabled.
  • TPMI Table 3 TPMIs for Rank-1 with four antenna ports (DFT-s-OFDM)
  • Table 6.3.1.5-3 Precoding matrix IF for single-layer transmission using four antenna ports with transform precoding disabled.
  • TPMI Table 4 TPMIs for Rank-1 with four antenna ports (CP-OFDM)
  • SUBSTITUTE SHEET ( RULE 26) partial coherent TPMI and partial coherent codebook subset should be enhanced considering different UE antenna architectures.
  • Mode 0 all power amplifiers (PAs) of the UE can deliver full power (i.e., 23 dBm); the power scaling factor is fixed to be 1.
  • Mode 1 typically, none of the PAs can deliver full power.
  • the UE has 4 PAs, and each can deliver 17 dBm;
  • the non-antenna selection precoder is included in the non-coherent/partial coherent codebook subset, e.g., [1 1 1 1] to deliver full power;
  • the power scaling factor is the ratio of a number of antenna ports with non-zero PUSCH transmission power over the maximum number of sounding reference signals (SRS) ports supported by the UE.
  • SRS sounding reference signals
  • Mode 2 some PAs can deliver full power.
  • the UE has PA architecture of [23 23 20 20] dBm; the UE should report TPMI(s) to the gNB, which can enable full power transmission, for example, [1 0 0 0] and [0 1 0 0]; for the TPMIs supporting full power, the power scaling factor is fixed to 1.
  • the power scaling factor is the ratio of a number of antenna ports with non-zero PUSCH transmission power over a number of SRS ports of the SRS resource indicated by an SRS resource indicator (SRI).
  • SRI SRS resource indicator
  • FIG. 3 illustrates a partial coherent UE with four panels in accordance with some embodiments.
  • the UE has 2 panels
  • the four antenna ports from the same panel are co-phasing ports.
  • the partial coherent TPMI includes four co-phasmg ports.
  • FIG. 4 illustrates a partial coherent UE with two panels in accordance with some embodiments.
  • Table 2 An Example of Rank- 1 partial coherent precoding matrix containing four co-phasing ports for 8 antenna ports
  • a partial coherent UE reports capability, including whether the UE supports 2 co-phasing ports in a partial coherent TPMI, or the UE supports 4 co-phasing ports in a partial coherent TPMI (i.e., whether the UE supports 4 panels or supports 2 panels).
  • the partial codebook subsets include partial coherent TPMIs depending on the UE capability. If the UE supports 2 co-phasing ports in a partial coherent TPMI, then partial coherent TPMIs with two co-phasing ports can be configured to the UE in the partial coherent codebook subset. If the UE supports four co-phasing ports in partial coherent TPMI, then partial coherent TPMIs with four co-phasing ports can be configured to the UE in the partial coherent codebook subset.
  • partial coherent TPMIs with four co-phasing ports and partial coherent TPMIs with two co-phasing ports can be configured to the UE in the partial coherent codebook subset. If the UE supports two co-phasing ports in partial coherent TPMI, then partial coherent TPMIs with two co-phasing ports can be configured to the UE in the partial coherent codebook subset and partial coherent TP Mis with four co-phasing TPMIs are unable to be configured to the UE in the partial coherent codebook subset.
  • all the partial coherent TPMIs containing two co-phasing ports and all the partial coherent TPMIs containing four co-phasing ports can be configured to the UE in the full coherent codebook subset.
  • the UE reports whether the UE can support full power delivery for the partial coherent TPMIs with 2-port co-phasing or 4-port co-phasing. If the UE can support full power for partial coherent TPMIs, the power scaling factor for the corresponding partial coherent TPMIs is set to be 1. Alternatively, the UE reports the partial TPMIs that can deliver full power.
  • FIG. 5 illustrates a partial coherent UE with a PA of 17dBm in accordance with some embodiments.
  • the partial coherent UE has 8 PAs, and each PA can deliver 17dBm.
  • the UE can deliver a full power of 23 dBm, therefore the power scaling factor for partial coherent TPMI is set to 1.
  • the UE may report the supported power scaling factor (1 , 1/2, 1/4, etc.) for corresponding TPMIs.
  • the reported power scaling factor may be used for the corresponding TPMIs when performing power control.
  • the partial TPMIs may be further split into groups (for example, one group for TPMIs with two-port co-phasing, and one group from TPMIs with four-port co-phasing), and the UE reports the power scaling factor for different groups.
  • Table 6.3.1.5-5 Precoding matrix W for two-layer transmission using four antenna ports with transform precoding disabled.
  • TPMI Table 5 TPMIs for Rank-2 with four antenna ports (CP-OFDM)
  • Table 6.3.1.5-6 Precoding matrix IP for three-layer transmission using four antenna ports with transform precoding disabled.
  • TPMI Table 7 TPMIs for Rank-4 with four antenna ports (CP-OFDM)
  • the TPMIs may be categorized into full coherent TPMI, partial coherent TPMI, and non-coherent TPMI, depending on whether relative phase can be maintained among all (full coherent), or a subset (partial coherent), or none (non-coherent) of the antenna ports.
  • Table 3 shows the non-coherent, partial coherent and full coherent TPMIs for 2-ports and 4-ports.
  • TP MI may be indicated via the “Precoding information and number of layers” field, and the TP MI may be 4-port or 2-port.
  • two TPMIs may be indicated via two “Precoding information and number of layers” fields.
  • the UE may be configured with two SRS resource sets and two SRI fields are included in the DCI. The association between SRI/TPMI and the SRS resource set is further delivered by the field of SRS Resource Set Indication.
  • the DCI may be enhanced to indicate the UE with 8-port precoder.
  • Section A DCI enhancement for PUSCH transmission with 8 ports
  • one TPMI is indicated via the field of “Precoding information and number of layers”, wherein the TPMI is 8-port TPMI.
  • the field of “Precoding information and number of layers” should be extended to more bits to support 8-port TPMI.
  • the DCI scheduling PUSCH e.g., DCI format 0_l/0_2
  • two 4-ports TPMIs can be indicated (the 4-port TPMI are as shown in TPMI Tables 3-7).
  • Two fields of “Precoding information and number of layers” are included in the DCI, and each field indicates one 4-port TPMI.
  • port group may be introduced for uplink transmission.
  • the first port group corresponds to port #0 to port #3
  • the second port group corresponds to port #4 to port #7.
  • the first 4-port TPMI is applied for the first PUSCH port group (port #0 to port #3), and the second 4-port TPMI is applied for the second PUSCH port group (port #4 to port #7).
  • the 8-port precoding matrix with Rank may be generated according to Equation (1).
  • (size of 4 x XI) and (size of 4 x X2) are 4-port precoding matrix with Rank XI and X2, respectively.
  • the value for and are as shown in TPMI Tables 3-7. 14 and l/ 2 are matrix with size of 2 x 1.
  • the candidate values for V ⁇ and V 2 include the 2-port precoders with Rank-1 plus [0 0] T ), as shown as in Table 44.
  • Equation (1) if either V 1 or I/ 2 is all zeros then X Otherwise, X and X2 are non-zero positive integers, and
  • the DCI scheduling PUSCH (e g., DCI format 0 1/0 2)
  • two 4- port TPMIs and ( ) are indicated.
  • the value for 14 and U 2 may also be indicated by the DCI via new DCI field(s) or reuse/re- purpose some existing field(s).
  • the indication of V 4 and V 2 may be achieved by joint encoding with other field(s) (for example, the SRS Resource Set Indication field).
  • the UE may construct the 8-port precoding matrix according to Equation (1).
  • FIG. 6 illustrates DCI in accordance with some embodiments.
  • the 1 st indicated 4-port TPMI is 144, corresponding to i n Equation (1).
  • the 2 nd indicated 4- port TPMI is VI/ 2 , corresponding to in Equation (1).
  • a new field(s) or an existing DCI field(s) may be used to indicate 14 and V 2 .
  • the values of V 1 and V 2 are as shown in Table 4.
  • the DCI in FIG. 6 indicates and V 2 .
  • the value of V r and V 2 may be restricted.
  • the value combinations of V ⁇ and V 2 may be as shown in Table .
  • the new field of three bits may be added to the DCI or an existing field(s) may be re-used.
  • the first three values (the first three combinations of 14 and V 2 ) may be used.
  • the last value (the last combination of V ⁇ and V 2 ) may be used.
  • all the values (all the combinations of V r and V 2 ) may be used.
  • Table 5 List on values of V 1 and V 2 [00118] Furthermore, in order to reduce the overhead, the combinations of and V 2 may be further reduced. One example is show n in Table , where 4 combinations of V 1 and V 2 are listed. In such case, the new field of tw o bits may be added to the DCI or existing field(s) may be re-used.
  • the first two values when generating non-coherent TPMIs, the first two values (the first two combinations of V 1 and V 2 ) may be used.
  • the last value when generating full coherent TPMIs, the last value (the last combination of V ⁇ and V 2 ) may be used.
  • all the values all the combinations of 14 and V 2 ) may be used.
  • the UE is non-coherent, then only the first two values (the first two combinations of 14 and V 2 ) are used, and consequently the field length is 1 bit.
  • the UE may be configured with one SRS resource set (the SRS resource in the SRS resource set may support up to 8 ports) with usage of ‘codebook’ and one SRI field is indicated in the DCI.
  • the UE may be configured with two SRS resource sets (the SRS resource in the SRS resource set could support up to 4 ports) with usage of ‘codebook’ and two SRI fields are indicated in the DCI.
  • the association between SRI/SRS resource set and the PUSCH port group/TPMI field may be implicit or explicit.
  • the first SRI field/SRS resource set corresponds to the first PUSCH port group (port #0 to port #3)/the first TPMI
  • the second SRI field/SRS resource set corresponds to the second PUSCH port group (port #0 to port #3)/the second TPMI.
  • a new field may be added or the existing field (e.g., the field of SRS Resource Set Indication) may be re-used.
  • the field to indicate the value for V 1 and V 2 may be jointly encoded with the field of SRS Resource Set Indication.
  • the joint encoding the field of indicating V 1 and V 2 and the SRS Resource Set Indication field is as shown in Table .
  • the field to indicate 14 and V 2 is just one bit. For example, if the value of SRS Resource Set Indication is ‘00’, then value of 0 for the field indication V 1 and V 2 means and V 2 of ; and the value of 1 for the field indication V, and V 2 means and V 2 of and so on.
  • Table 8 Another joint encoding between the field indicating V 1 and V 2 and the field of SRS Resource Set Indication [00125] In this embodiment, whether both TMPI fields or only one TP MI field are used for 8-port precoder generation may be indicated by another field (which may be a new field, or the field indicating values for 14 and V 2 or some other existing field, e.g., the field of SRS Resource Set Indication).
  • whether both TPMI fields are present in the DCI may be configurable. For example, if the PUSCH transmission is with 4 ports or less than 4 ports, then the second TPMI field is not present. In another example, if the maximum number of ports for SRS resources configured with usage of codebook is 4 or less than 4, then the second TPMI field is not present in DCI.
  • this embodiment may also be applied to the case that multiple codewords (e.g., two codewords) are used for uplink transmission.
  • the 1 st codeword corresponds to the 1 st PUSCH port group (port #0 ⁇ port #3), and the 2 nd codeword corresponds to the 2 nd PUSCH port group (port #4 ⁇ port #7).
  • the 1 st TPMI is used for the 1 st codeword
  • the 2 nd TPMI is used for the 2 nd codeword.
  • W ⁇ and V 1 are used for the 1 st codeword
  • VF 2 and V 2 are used for the 2 nd codeword.
  • the concept of port group may be introduced for uplink transmission.
  • the first port group corresponds to port #0 to port #3, and the second port group corresponds to port #4 to port #7.
  • the 8-port precoding matrix (size of 8 X X) with Rank X may be generated by different methods.
  • the 8-port precoding matrix may be generated according to Equation (2).
  • (size of 2 x XI) is a 2-port precoder with Rank XI
  • (size of 4x X2) is a 4-port precoder with Rank X2.
  • TPMI Tables 1 and 2. is as shown in TPMI Tables 3-7.
  • 0 means Kronecker product operation.
  • Equation (2) where XI and X2 are non-zero positive integers, and XI ⁇ 2,X2 ⁇ 4.
  • FIG. 7 illustrates TPMI operation in accordance with some embodiments. In particular, FIG. 7 illustrates TPMI operation in accordance with Method A.
  • the 8-port precoding matrix may be generated according to Equation (3).
  • W 14Tx R ⁇ x ⁇ (size of 4 X XI) and (size of 4 X X2) are 4-port precoding matrix with Rank XI and X2, respectively.
  • W 2 ,4 TX ,R(X2) are as shown in TPMI Tables 3-7. and are 2-port precoder with Rank-1, as shown in TPMI Table 1.
  • Equation (3) where XI and X2 are non-zero positive integers, and XI ⁇
  • the 8-port precoder is generated according to Equation (3), then in the DCI scheduling PUSCH, two 4-port TPMIs and may be indicated. Two fields of “Precoding information and number of layers” is included in the DCI, and each field indicates one 4-port TPMI. In addition, two 2-port TPMIs with Rank-1 and may also be indicated. [00137] When two 4-port TPMIs are indicated in the DCI, the first 4-port TPMI is applied for the first PUSCH port group (port #0 to port #3), and the second 4-port TPMI is applied for the second PUSCH port group (port #4 to port #7).
  • FIG. 8 illustrates another TPMI operation in accordance with some embodiments. In particular, FIG. 8 illustrates TPMI operation in accordance with Method B.
  • a new field(s) may be added to indicate whether only one TPMI (either the 1 st TPMI or the 2 nd TPMI) is used or both TPMIs are used to generate the 8-port precoder.
  • the SRS Resource Set Indication field may be re-used if two SRS resource sets with usage of codebook are configured.
  • the 8-port precoding matrix (size of 8 X X) with Rank X may be generated as below. [00142] If only the 1 st TPMI field is used, then the 8-port precoding matrix may be generated by: [00143] where ® means Kronecker product operation.
  • the 8-port precoding may be generated by: [00145] where ⁇ 8> means Kronecker product operation.
  • the 8-port precoding matrix may be generated by:
  • [00148] and (size of 4 X X2) are 4-port precoding matrix with Rank XI and X2, respectively. and are as shown in TPMI Tables 3-7. and V are 2- port precoder with Rank-1, as shown in TPMI Table 1. The value combinations for and may be further restricted as shown in TPMI Tables 3-4 (14 and U 2 corresponds to V 1 2TX ,R( 1 ) and V respectively, and value of [0 0] r means it is not used).
  • Equation (4) X — XI.
  • X X2.
  • X XI + X2.
  • XI and X2 are non-zero positive integers, and XI ⁇ 4, X2 ⁇ 4.
  • the 8-port precoder generation with Equation (5) may be optional, i.e., the precoder is generated based on Equation (4) and Equation (6).
  • Equation (4) is used if the Rank value is X E ⁇ 1,2, 3,4 ⁇ .
  • Equation (6) is used if the Rank value is X E ⁇ 5, 6, 7, 8 ⁇ .
  • FIG. 9 illustrates another TPMI operation in accordance with some embodiments. In particular, FIG. 9 illustrates TPMI operation in accordance with Method C.
  • Table shows an example of the joint encoding between SRS Resource Set Indication field and the field indicating V ⁇ and 72 (corresponding TO V and respectively).
  • the UE may be configured with one SRS resource set (the SRS resource in the SRS resource set may support up to 8 ports) with usage of ‘codebook’ and one SRI field is indicated in the DCI.
  • the UE may be configured with two SRS resource sets (the SRS resource in the SRS resource set may support up to 4 ports) with usage of ‘codebook’ and two SRI fields are indicated in the DCI.
  • the association between SRI/SRS resource set and the PUSCH port group/TPMI field may be implicit or explicit.
  • the first SRI field/SRS resource set corresponds to the first PUSCH port group (port #0 to port #3)/the first TPMI
  • the second SRI field/SRS resource set corresponds to the second PUSCH port group (port #0 to port #3)/the second TPMI.
  • a new field may be added or the existing field (e g., the field of SRS Resource Set Indication) may be re-used.
  • this embodiment can also be applied to the case that multiple codewords (e.g., two codewords) are used for uplink transmission.
  • the 1 st codeword corresponds to the 1 st PUSCH port group (port #0 ⁇ port #3), and the 2 nd codeword corresponds to the 2 nd PUSCH port group (port #4 ⁇ port #7).
  • the 1 st TPMI is used for the 1 st codeword
  • the 2 nd TPMI is used for the 2 nd codeword. are used for the 1 st codeword, and are used for the 2nd codeword.
  • a new DCI field to indicate which equation is used to generate the precoder, i.e., whether Equation (l)/(2)/(3)/(4)/(5) is used.
  • which Equation is used may be predefined, or configured by higher layer signaling (RRC/MAC-CE).
  • the SRS configuration may be different considering full power operation mode.
  • one SRS resource set may be configured and up to two SRS resources can be configured in the SRS resource set.
  • the number of SRS antenna ports may be the same for all the SRS resources in the SRS resource set. In this case, the maximum number of SRS antenna ports is 4.
  • one SRS resource set may be configured and up to 2 or 4 SRS resources can be configured in the SRS resource set.
  • the number of SRS antenna ports may be the same or different. In this case, the maximum number of SRS antenna ports is 4.
  • the uplink transmission may support up to 8 Tx (8 ports)
  • the gNB configures fewer ports for uplink transmission for power saving, for example, 4 ports or 2 ports.
  • RRC reconfiguration is used to switch between different number of antenna ports, which leads to extra signaling overhead. Therefore, it may be preferable to allow the gNB and UE to quickly switch between different antenna ports operation in Rel-18.
  • the UE may be configured with one or multiple SRS resource sets with usage of ‘codebook’.
  • the number of SRS resource sets configured for codebook-based transmission is N SRS , and N SRS > 1.
  • N SRS The number of SRS resource sets configured for codebook-based transmission
  • N SRS Within each SRS resource set, one or multiple SRS resources may be configured.
  • M SRS The number of SRS resources within one SRS resource set.
  • the number of SRS ports for all the SRS resources within the SRS resource set may be the same, i.e., P is the same for all the SRS resources and P E ⁇ 1, 2, 4, 8 ⁇ .
  • This embodiment may be applied for codebook-based transmission when full power operation is not enabled, or when full power operation is enabled and set to full power Mode 0 or full power Mode 1.
  • One or multiple SRI fields may be included in the DCI.
  • One or multiple TPMI fields may be included in the DCI.
  • the number of SRS ports for all the SRS resources within the SRS resource set may be the same or different. For example, 4 SRS resources are configured in the SRS resource set and the number of SRS ports of the 4 SRS resources are ⁇ 1, 2, 4, 8 ⁇ respectively.
  • One or multiple SRI fields may be included in the DCI.
  • One or multiple TPMI fields may be included in the DCI.
  • the TPMI field length is determined by the maximum number of ports of the configured SRS resource.
  • This embodiment may be applied for codebook-based transmission when full power operation is enabled and set to full power Mode 2.
  • this embodiment can also be used for codebook-based transmission when full power operation is not enabled, or when full power operation is enabled and set to full power Mode 0 or full power Mode 1.
  • FIG. 10 illustrates an SRS configuration for codebook-based transmission in accordance with some embodiments.
  • multiple SRS resource sets may be configured (N SRS > 1).
  • the number of SRS ports for the SRS resources within one SRS resource set is the same.
  • the number of SRS ports for SRS resources across different SRS resource set may be different.
  • one or multiple SRI fields should be included.
  • the number of SRI fields may be the same or less than the number of SRS resource sets.
  • M SRS 2
  • the number of SRS ports of the two SRS resources is 8.
  • two SRIs are included.
  • the 1 st SRI corresponds to the 1 st SRS resource set
  • the 2 nd SRI corresponds to the 2 nd SRS resource set.
  • one or multiple TPMI fields may be included, e.g., two TPMI fields.
  • the 1 st TPMI field corresponds to the 1 st SRI and is based on 2-ports
  • the 2 nd TPMI field corresponds to the 2 nd SRI and is based on 8-ports.
  • Whether the SRI/TPMI field is used may be implicitly or explicitly indicated. With implicit indication, if one SRI/TPMI field is not used for transmission, one specific value (for example, one reserved value) of the SRI/TPMI field may be used to indicate that the corresponding SRI/TPMI field is not used for transmission. With explicit indication, a new field may be added to the DCI or the existing field may be reused/repurposed.
  • FIG. 11 illustrates DCI-based switching between different ports for codebook-based transmission in accordance with some embodiments.
  • the existing field of SRS Resource Set Indication is used to indicate which SRI/TPMI field is used. In this way, the gNB and the UE may quickly switch between 2-port and 8-port operation.
  • a medium access control control element may be introduced to select a subset of the configured SRS resource sets.
  • the selected SRS resource sets configured via MAC-CE are used and are mapped to the SRI fields.
  • This embodiment may be applied for codebook-based transmission when full power operation is enabled and set to full power Mode 2.
  • this embodiment can also be used for codebook-based transmission when full power operation is not enabled, or when full power operation is enabled and set to full power Mode 0 or full power Mode 1.
  • multiple codewords/panels may be used, e.g., two codewords/panels.
  • port group may be defined with the number of port group is M.
  • the 8 antenna ports are split into two port groups. The 1 st port group includes port #0 to port #3, and the 2 nd port group includes port #4 to port #7.
  • one SRS resource set is configured.
  • one or multiple (e.g., two) SRI fields are included, and one or multiple (e.g., two) TPMI fields are included.
  • the SRI/TPMI field may be mapped to the codeword/panel/port group. The mapping may be implicit or explicit. For example, the 1 st SRI/TPMI field is used for the 1 st codeword/panel/port group, and the 2 nd SRI/TPMI field is used for the 2 nd codeword/panel/port group.
  • the number of the antenna ports for the SRS resources in the SRS resource set should be the same. This may be applied for codebook -based transmission when full power operation is not enabled, or when full power operation is enabled and set to full power Mode 0 or full power Mode 1.
  • the number of the antenna ports for the SRS resources in the SRS resource set may be the same or different. This may be applied for codebook-based transmission when full power operation is enabled and set to full power Mode 2. Alternatively, this may also be applied for codebook-based transmission when full power operation is not enabled, or when full power operation is enabled and set to full power Mode 0 or full power Mode 1.
  • multiple SRS resource sets (e.g., two) are configured.
  • multiple (e.g., two) SRI fields are included, and multiple (e.g., two) TPMI fields are included.
  • the SRI/TPMI field may be mapped to the SRS resource set and/or codeword/panel/port group. The mapping may be implicit or explicit.
  • the 1 st SRI/TPMI field is used for the 1 st SRS resource set and/or the 1 st codeword/panel/port group
  • the 2 nd SRI/TPMI field is used for the 2 nd SRS resource set and/or the 2 nd codeword/panel/port group.
  • the number of the antenna ports for the SRS resources within one SRS resource set may be the same.
  • the number of antenna ports for the SRS resources across different SRS resource set may be the same or different.
  • the number of SRS resources across different SRS resource set may be the same or different. This may be applied for codebook-based transmission when full power operation is not enabled, or when full power operation is enabled and set to full power Mode 0 or full power Mode 1.
  • the number of the antenna ports for the SRS resources within one SRS resource set may be the same or different.
  • the number of antenna ports for the SRS resources across different SRS resource sets may be the same or different.
  • the number of SRS resources across different SRS resource sets may be the same or different. This may be applied for codebook-based transmission when full power operation is enabled and set to full power Mode 2. Alternatively, this may also be applied for codebook-based transmission when full power operation is not enabled, or when full power operation is enabled and set to full power Mode 0 or full power Mode 1
  • the 8-port precoding matrix ( s i ze °f 8 X X) with Rank X may be generated according to Equation (1) and/or Equation (2), where means Rank X, Rank XI, Rank X2, respectively.
  • Equation (7) may be used for 8 Tx with Rank X E [1,2, 3, 4, 6, 8 ⁇ . is a 2-port precoder with Rank XI, and (size °f 4x X2) is a 4-port precoder with Rank X2. is as shown in TPMI Tables 1-2. 1S as shown in TPMI Tables 3-7. The constrain is . where XI and X2 are non-zero positive integers, and
  • Equation (8) below may be used for 8Tx with Rank X G (size of 4 x X1) and (size of 4 x X2) are 4-port precodmg matrix with Rank XI and X2. respectively. and as shown in TPMI Tables 3-7.
  • the precodmg matrix generated by Equation (8) may be mutually orthogonal among columns (i.e., any two columns are orthogonal).
  • the precoding matrix for 8-Tx may be all the codebooks generated by Equation (7) and/or Equation (8) (or the union set of all the codebooks generated by Equation (7) and Equation (8)). Or the precoding matrix for 8-Tx may be subset of all the codebooks generated by Equation (7) and/or Equation (8) (or the subset of the union set of all the codebooks generated by Equation (7) and Equation (8)).
  • (8) may select one matrix as shown in Table 9 (i.e., the candidate values for and include the Rank-1 precoder with 2-ports plus
  • Equation (8) may be used to generate 8-port precoding matrix for all the Ranks, i.e., Rank X G [1, 2, 3, 4 ... 8 ⁇ .
  • Equation (7) may be covered by Equation (8), i.e., all the 8-port precoding matrix can be generated solely from Equation (8).
  • the precodmg matrix for 8-Tx may be all the codebooks generated by Equation (8).
  • the precoding matrix for 8-Tx may be subset of all the codebooks generated by Equation (8). After the precoder is constructed, the column with all zeros may be removed.
  • Equation (7) may be used for 8 Tx with Rank X G ⁇ 1,2, 3, 4, 5, 6, 7, 8 ⁇
  • the precoding matrix may be generated by dropping one specific column, e.g., the last column, from the precoder of Rank X + 1 that is generated according to Equation (7).
  • One field may be added to DCI to indicate the rank of the indicated TPMI is reduced by one, and the one specific column (the last column) is dropped.
  • the 8-port precoding matrix VF 8Tx R(-X ) (size of 8 x X) with Rank X may be generated according to Equation (9) and/or Equation (10) below.
  • 8-port partial coherent TPMI when it is generated by Equation (7)/(9), may be a 2-port non-coherent TPMI with Rank XI, and may be a 4-port partial coherent or full coherent TPMI with Rank X2 as shown in Table . Or is a 2-port full coherent TPMI with Rank XI, and is a 4-port partial coherent or non coherent TPMI with Rank X2 as shown in Table .
  • 8-port partial coherent TPMI when it is generated by Equation (8)/(10), and may be 2-port non-coherent precoder with Rank-1, may be a 4-port partial coherent or full coherent TPMI with Rank XI, and maY be a 4-port partial coherent or full coherent TPMI with Rank X2, as shown in Table .
  • 2-port full coherent precoder with Rank-1 may be a 4-port partial coherent or non-coherent TPMI with Rank XI, and may be a 4-port partial coherent or non-coherent TPMI with Rank X2, as shown in Table .
  • the partial coherent UE supports 4 co-phasing ports (the UE can maintain relative phase among 4 ports), then when the precoder is generated by Equation (7)/(9), may be a 2-port non coherent TPMI with Rank XI, and may be a 4-port full coherent TPMI with Rank X2 as shown in Table . Or is a 2-port full coherent TP MI with Rank XI, and is a 4-port partial coherent TPMI with Rank X2 as shown in Table .
  • the partial coherent UE supports 4 co-phasing ports
  • the precoder when the precoder is generated by Equation (8)/(l 0), may be 2 -port non-coherent precoder with Rank-1, may be a 4-port full coherent TPMI with Rank XI, and may be a 4-port full coherent TPMI with Rank X2, as shown in Table .
  • V and V2 2TX,R(X) maY be 2- port full coherent precoder with Rank-1, may be a 4-port partial coherent TPMI with Rank XI, and may be a 4-port partial coherent TPMI with Rank X2, as shown in Table .
  • the partial coherent UE supports 2 co-phasing ports (the UE can maintain relative phase among 2 ports), then when the precoder is generated by Equation (7)/(9), may be a 2-port non-coherent TPMI with Rank XI, and ( ) maY be a 4-port partial coherent TPMI with Rank X2 as shown in Table . Or is a 2-port full coherent TPMI with Rank XI, and is a 4-port non-coherent TPMI with Rank X2 as shown in Table
  • the partial coherent UE supports 2 co-phasmg ports
  • maY be 2-port non-coherent precoder with Rank-1
  • maz ze a 4-port partial coherent TPMI with Rank XI
  • 2- port full coherent precoder with Rank-1 may be a 4-port noncoherent TPMI with Rank XI
  • maY be a 4-port non-coherent TPMI with Rank X2, as shown in Table .
  • 8-port full coherent TPMI when it is generated by Equation (7)/(9), is a 2-port full coherent TPMI with Rank XI, and 1S a 4-port full coherent TPMI with Rank X2. as shown in Table .
  • 2-port full coherent precoder with Rank-1 as shown in Table
  • is a 4-port full coherent TPMI with Rank XI is a 4-port full coherent TPMI with Rank X2. as shown in Table . If and are the same then and may be different. If and are the same, then V and may be different.
  • V are 2-port full coherent precoder with Rank-1 as shown in Table plus [0 0] T .
  • the precoders with 8-ports for Rank-1 to
  • a UE different coherence including maintaining the relative phase among all (full coherence), a subset (partial coherence), or none (non-coherence) of the transmit chains/antenna ports over time.
  • the UE may be configured to operate with a subset of precoders in the UL codebook according to the reported coherence capability.
  • a UE capable of "fullCoherent’ transmission may be configured with codebook subset of "fullAndPartialAndNonCoherent ’, "partialAndNonCoherenf, or 'noncoherent ’.
  • a UE capable of 'partiaK 'ohercnt ’ transmission may be configured with codebook subset of "partialAndNonCoherent’ or "noncoherent’.
  • a UE capable of "noncoherent’ transmission may be configured with codebook subset of "noncoherent’ .
  • the UE may report its coherence capability as shown by pusch- TransCoherence below:
  • full power operation is supported including full power Mode 0, full power Mode 1, and full power Mode 2 as described above.
  • the UE reports its capability on full power operation (whether full power Mode 0, Mode 1, or Mode 2 is supported).
  • the UE coherence capability and full power capability do not consider different capabilities for different numbers of antenna ports.
  • the gNB may configure the UE wdth 4-port operation. In this case, the UE coherence capability and full power capability may be enhanced, i.e., the coherence and/or full power capability may be different for different numbers of antenna ports.
  • the UE coherence capability is reported for each number of antenna ports supported by the UE or a subset of the number of antenna ports supported by the UE. For different number of antenna ports, the coherence capability may be the same or different.
  • the UE may report coherence capability for 8 ports, (6 ports, which may not be reported if 6 port is not supported), 4 ports, and 2 ports.
  • the same or different codebook subsets may be configured to the UE for difference numbers of ports depending on the UE capability.
  • One or multiple codebook subsets may be configured to the UE simultaneously.
  • the codebook subsets may be the same or different for different numbers of ports.
  • FIG. 12 illustrates a UE with portdependent coherence in accordance with some embodiments, in particular the third example.
  • the number of co-phasing ports i.e., co-phasing ports means the ports that the UE can maintain relative phase
  • the 1 st four ports are co-phasing, and the second four ports (port #4 to #7) are co-phasing.
  • the UE is partial coherent.
  • For 4-port and 2-port the UE is full coherent.
  • FIG. 13 illustrates a UE with portdependent coherence in accordance with some embodiments, in particular the fourth example.
  • the number of co-phasing ports is 4. Port ⁇ #0, #2, #4, #6 ⁇ are co-phasing; port ⁇ #1, #3, #5 #7 ⁇ are co-phasing.
  • 8-port the UE is partial coherent.
  • 4-port the UE is partial coherent.
  • 2-port the UE is noncoherent.
  • FIG. 14 illustrates a UE with port-dependent coherence in accordance with some embodiments. In FIG.
  • the number of co-phasing ports is 2. Port ⁇ #0, #2 ⁇ , ⁇ #1, #3 ⁇ , ⁇ #4, #6 ⁇ and ⁇ #5, #7 ⁇ are co-phasing.
  • 8-port the UE is partial coherent.
  • 4-port the UE is partial coherent.
  • 2-port the UE is non-coherent.
  • FIG. 15 illustrates a UE with portdependent coherence in accordance with some embodiments, in particular the fifth example.
  • the number of co-phasing ports is 2.
  • Port ⁇ #0, #1 ⁇ , ⁇ #2, #3 ⁇ , ⁇ #4, #5 ⁇ and ⁇ #6, #7 ⁇ are co-phasing.
  • the UE is partial coherent.
  • 4-port the UE is partial coherent.
  • 2-port the UE is full coherent.
  • the UE when the UE reports coherence capability for 8-port, if the coherence is partial coherence, the UE may report the number of co-phasing ports, and/or the port combination among which the UE is able to maintain relative phase. For example, for the UE show n in FIG. 12, the UE reports partial coherence for 8-port, the number of co-phasing port is 4, and/or the UE reports the port combination of ⁇ #0, #1, #2, #3 ⁇ and ⁇ #4, #5, #6, #7 ⁇ over which the UE is able to maintain relative phase. For the UE shown in FIG.
  • the UE reports partial coherence for 8-port, the number of co-phasing port is 4, and/or the UE reports the port combination of ⁇ #0, #2, #4, #6 ⁇ and ⁇ #1, #3, #5, #7 ⁇ over which the UE is able to maintain relative phase.
  • the UE shown in FIG. 14 the UE reports partial coherence for 8-port, the number of cophasing port is 2, and/or the UE reports the port combination of ⁇ #0, #2 ⁇ , ⁇ #1, #3 ⁇ , ⁇ #4, #6 ⁇ and ⁇ #5, #7 ⁇ over which the UE is able to maintain relative phase.
  • the UE reports partial coherence for 8-port, the number of co-phasing port is 2, and/or the UE reports the port combination of ⁇ #0, #1 ⁇ , ⁇ #2, #3 ⁇ , ⁇ #4, #5 ⁇ and ⁇ #6, #7 ⁇ over which the UE is able to maintain relative phase.
  • the same or different UE coherence capability may be reported for different codeword/panels.
  • the same or different codebook subset may be configured for different codeword/panels.
  • various port groups may be defined with the number of port groups being M. For example, 8 antenna ports may be split into two port groups, in which the 1 st port group includes port #0 to port #3, and the 2 nd port group includes port #4 to port #7.
  • the UE may report the same or different coherence capability for different port group.
  • the same or different codebook subsets may be configured for different port groups.
  • the UE capability on full power operation is reported for each number of antenna ports supported by the UE or a subset of the number of antenna ports supported by the UE. For different numbers of antenna ports, the UE full power operation capability may be the same or different.
  • the same or different full power modes may be configured to the UE for difference numbers of ports depending on the UE capability.
  • One or multiple full power operation modes may be configured to the UE simultaneously.
  • the full power modes may be the same or different for different numbers of ports.
  • FIG. 16 illustrates a UE with port-dependent full power mode in accordance with some embodiments.
  • each PA is 23 dBm.
  • each PA is 17 dBm.
  • the UE may support full power Mode 2.
  • the UE may support full power Mode 0.
  • the UE may support full power Mode 2 for 8- port.
  • the UE may support full power Mode 0, and for 4-port with port combination ⁇ #4, #5, #6, #7 ⁇ , the UE may support full power Mode 1.
  • the UE may support full power Mode 0, and for 2-port with port combination ⁇ #4, #5 ⁇ and ⁇ #6, #7 ⁇ , the UE may not support full power operation.
  • the same or different UE full power capability may be reported for different codeword/panels.
  • the same or different full power mode may be configured for different codeword/panels.
  • multiple port groups may be defined with the number of port group being M.
  • the 8 antenna ports are split into two port groups, with the 1 st port group including port #0 to port #3, and the 2 nd port group including port #4 to port #7.
  • the UE may report the same or different full power operation capability for different port groups.
  • the same or different full power mode may be configured for different port groups.
  • a UE that is able support uplink transmission with up to 8 ports reports a coherence capability and full power operation capability to a gNB.
  • the gNB may configure the UE with a corresponding codebook subset and full power operation mode dependent on the coherence capability.
  • the coherence capability is reported for each number of antenna ports supported by the UE or a subset of the number of antenna ports supported by the UE.
  • the coherence capability is able to be identical or different for different numbers of antenna ports.
  • Identical or different codebook subsets are configured to the UE for different numbers of ports depending on the UE capability.
  • the codebook subsets are simultaneously configured to the UE.
  • the UE reports at least one of a number of co-phasing ports or port combinations among which the UE is able to maintain relative phase.
  • identical or different UE coherence capabilities are reported for at least one of different codewords or panels.
  • identical or different codebook subsets are configured for the at least one of different codewords or panels.
  • a predetermined number of port groups are defined for uplink transmission with up to N ports. For 8 antenna ports split into two port groups, a first port group includes port #0 to port #3, and a second port group includes port #4 to port #7.
  • the UE reports identical or different coherence capabilities for the different port groups. Identical or different codebook subset are configured for the different port groups.
  • the full power operation capability is reported for each antenna port supported by the UE or a subset of the antenna ports supported by the UE.
  • the full power operation capability is identical or different for different numbers of antenna ports.
  • identical or different full power modes are configured to the UE for different numbers of ports depending on the full power operation capability.
  • One or more full power operation modes are simultaneously configured to the UE.
  • Example 1 is an apparatus for a user equipment (UE), the apparatus comprising: memory; and processing circuitry, to configure the UE to: receive, from a 5th generation NodeB (gNB), a codebook for eight port uplink physical shared channel (PUSCH) transmission, the codebook containing a plurality of Transmit Precoder Matrix Indicators (TP Mis) that includes, a non- coherent TPMI, a partial coherent TPMI, and a full coherent TPMI; receive, from the gNB, downlink channel information (DCI) scheduling a PUSCH, the DCI indicating one of the TPMIs; and transmit, to the gNB, the PUSCH on eight ports of the UE based on the DCI; and wherein the memory is configured to store the codebook.
  • gNB 5th generation NodeB
  • PUSCH physical shared channel
  • TP Mis Transmit Precoder Matrix Indicators
  • Example 2 the subject matter of Example 1 includes, wherein: the processing circuitry configures the UE as a partial coherent UE to transmit the PUSCH, and one of: the UE has four panels, each panel contains two cophasing antenna ports, and the partial coherent TPMI includes two co-phasing ports, or the UE has two panels, each panel contains four co-phasing antenna ports, and the partial coherent TPMI includes four co-phasing ports.
  • Example 3 the subject matter of Example 2 includes, wherein the processing circuitry configures the UE to report, to the gNB, UE capacity that indicates which one of both of two or four co-phasing ports in the partial coherent TPMI is supported by the UE.
  • Example 4 the subject matter of Example 3 includes, wherein: the codebook contains a partial coherent codebook subset that includes partial coherent TPMIs that are dependent on the UE capacity , and for UE support of two co-phasing ports in the partial coherent TPMI, one of: partial coherent TPMIs with two co-phasing ports are able to be configured to the UE in the partial coherent codebook subset, or partial coherent TPMIs with two co-phasing ports are able to be configured to the UE in the partial coherent codebook subset and partial coherent TPMIs with four co-phasing TPMIs are unable to be configured to the UE in the partial coherent codebook subset, and for UE support of four co-phasing ports in the partial coherent TPMI, one of: partial coherent TPMIs with four co-phasing ports are able to be configured to the UE in the partial coherent codebook subset, or partial coherent TPMIs with four cophasing ports and partial coherent TPMIs with two
  • Example 5 the subject matter of Examples 3-4 includes, wherein the processing circuitry configures the UE to: support full power Mode 1, report, to the gNB, whether the UE is able to support full power delivery for partial coherent TPMIs with two port co-phasing or four port co-phasing, and in response to the UE supporting full power for partial coherent TPMIs, at least one of set a power scaling factor for corresponding partial coherent TPMIs to be 1 or report to the gNB partial coherent TPMIs that can deliver full pow er.
  • Example 6 the subject matter of Examples 3-5 includes, wherein the processing circuitry configures the UE to: split the partial coherent TPMIs into groups including a first group with two port co-phasing and a second group with four port co-phasing, report, to the gNB, a supported power scaling factor for corresponding TPMIs in each group, and use the reported power scaling factor for the corresponding TPMIs when performing power control.
  • Example 7 the subject matter of Examples 1-6 includes, wherein: the processing circuitry configures the UE as a full coherent UE to transmit the PUSCH, one of: the UE has four panels, each panel contains tw o cophasing antenna ports, and the partial coherent TPMI includes two co-phasing ports, or the UE has two panels, each panel contains four co-phasing antenna ports, and the partial coherent TPMI includes four co-phasing ports, and partial coherent TPMIs containing two co-phasing ports and partial coherent TPMIs containing four co-phasing ports are able to be configured to the UE in a full coherent codebook subset of the codebook.
  • Example 8 the subject matter of Examples 1-7 includes, wherein: the UE has eight ports with multiple port groups of an identical number of ports, and the DCI indicates the one of the TPMIs in a “Precoding information and number of layers” field for each port group.
  • Example 9 the subject matter of Example 8 includes, wherein one of: an 8-port precoding matrix with Rank X is generated according to where ® is a Kronecker product operation, an 8-port precoding matrix with Rank X (X E ⁇ 1,2, 3, 4, 6, 8 ⁇ ) is generated according to or an 8-port precoding matrix with Rank is generated according to
  • Example 10 the subject matter of Examples 8-9 includes, - port precoding matnx, and the field is one of a new field or a sounding reference signal (SRS) Resource Set Indication field for configuration of two SRS resource sets with codebook usage.
  • SRS sounding reference signal
  • Example 11 the subject matter of Examples 1-10 includes, wherein: the UE is configured with at least one sounding reference signal (SRS) Resource Set resource set with usage of ‘codebook’, and a number of SRS resource sets configured for codebook-based transmission is N_SRS, and N_SRS>1.
  • SRS sounding reference signal
  • Example 12 the subject matter of Examples 1-11 includes, wherein for codebook-based PUSCH transmission with up to eight ports: one sounding reference signal (SRS) resource set is configured, up to two or four SRS resources are configured in the SRS resource set, a number of SRS ports for SRS resources within the SRS resource set are identical for up to two SRS resources configured in the SRS resource set and are able to be different for up to four SRS resources configured in the SRS resource set, and for up to two SRS resources configured in the SRS resource set, the processing circuitry configures the UE to apply the codebook-based PUSCH transmission during periods in which full power operation is not enabled and full power operation is enabled and set to full power Mode 0 or full power Mode 1.
  • SRS sounding reference signal
  • Example 13 the subject matter of Example 12 includes, wherein: different number of ports are configured for the SRS resources within the SRS resource set, TPMI field length is determined by a maximum number of ports of a configured SRS resource, and for up to four SRS resources configured in the SRS resource set, the processing circuitry configures the UE to apply the codebook-based PUSCH transmission during periods in which full power operation is not enabled and full power operation is enabled and set to full power Mode 0, full power Mode 1, or full power Mode 2.
  • Example 14 the subject matter of Examples 1-13 includes, wherein for codebook-based PUSCH transmission with up to eight ports: multiple sounding reference signal (SRS) resource sets are configured, a number of SRS ports for SRS resources within one SRS resource set are identical, a number of SRS ports for SRS resources across different SRS resource sets are able to be different, and the DCI includes at least one SRS resource indicator (SRI) field and at least one TPMI field, a number of SRI fields being at most a number of SRS resource sets.
  • SRS sounding reference signal
  • Example 15 the subject matter of Examples 1-14 includes, wherein: an eight port precoding matrix with Rank X is generated according at least one of: or where is respectively, and ® is a Kronecker product operation.
  • Example 16 the subject matter of Example 15 includes, wherein at least one of: and in (2) selects a matrix from: in which candidate values for V_(l,2Tx,R(l)) and V_(2,2Tx,R(l)) include a Rank-1 precoder with 2-ports plus then (2) is used to generate the eight port precoding matrix for the ranks, or (1) is used for eight ports with Rank for Rank of the eight port precoding matrix is generated by dropping one column from the precoder of Rank X+l which is generated according to (1), and a field is added to the DCI to indicate a rank of an indicated TPMI is reduced by one, and the column dropped.
  • Example 17 is an apparatus for a 5th generation NodeB (gNB), the apparatus comprising: memory; and processing circuitry, to configure the gNB to: transmit, to a user equipment (UE), a codebook for eight port uplink physical shared channel (PUSCH) transmission, the codebook containing a plurality of Transmit Precoder Matrix Indicators (TP Mis) that includes, a non- coherent TPMI, a partial coherent TPMI, and a full coherent TPMI; transmit, to the UE, downlink channel information (DCI) scheduling a PUSCH, the DCI indicating one of the TPMIs; and receive, from the UE, the PUSCH on eight ports of the UE based on the DCI; and wherein the memory is configured to store the codebook.
  • UE user equipment
  • PUSCH uplink physical shared channel
  • TP Mis Transmit Precoder Matrix Indicators
  • Example 18 the subject matter of Example 17 includes, wherein the processing circuitry configures the gNB to receive, from the UE, UE capacity that indicates which one of both of two or four co-phasing ports in the partial coherent TPMI is supported by the UE.
  • Example 19 is a computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE), the one or more processors to configure the UE, when the instructions are executed: receive, from a 5th generation NodeB (gNB), a codebook for eight port uplink physical shared channel (PUSCH) transmission, the codebook containing a plurality of Transmit Precoder Matrix Indicators (TPMIs) that includes, a non-coherent TPMI, a partial coherent TPMI, and a full coherent TPMI; receive, from the gNB, downlink channel information (DCI) scheduling a PUSCH, the DCI indicating one of the TPMIs; and transmit, to the gNB, the PUSCH on eight ports of the UE based on the DCI.
  • TPMIs Transmit Precoder Matrix Indicators
  • Example 20 the subject matter of Example 19 includes, wherein the instructions configure the one or more processors to configure the UE to report, to the gNB, UE capacity that indicates which one of both of two or four co-phasing ports in the partial coherent TPMI is supported by the UE.
  • Example 21 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-20.
  • Example 22 is an apparatus comprising means to implement of any of Examples 1-20.
  • Example 23 is a system to implement of any of Examples 1-20.
  • Example 24 is a method to implement of any of Examples 1-20.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un appareil et un système de transmission en liaison montante avec huit ports. Des précodeurs pour des transmissions en liaison montante d'UE partielles et complètes cohérentes sont décrits, de même que des améliorations d'informations de commande de liaison descendante (DCI) et des configurations de signal de référence de sondage (SRS) pour une transmission en liaison montante basée sur un livre de codes. Des matrices de précodeur sont fournies pour différents rangs pour les transmissions à huit ports.
PCT/US2023/014610 2022-03-14 2023-03-06 Améliorations de transmission en liaison montante à huit ports WO2023177547A1 (fr)

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
CN2022080592 2022-03-14
CNPCT/CN2022/080592 2022-03-14
CNPCT/CN2022/083001 2022-03-25
CN2022083001 2022-03-25
CN2022085305 2022-04-06
CNPCT/CN2022/085273 2022-04-06
CNPCT/CN2022/085305 2022-04-06
CN2022085273 2022-04-06
CNPCT/CN2022/086950 2022-04-15
CN2022086950 2022-04-15

Publications (1)

Publication Number Publication Date
WO2023177547A1 true WO2023177547A1 (fr) 2023-09-21

Family

ID=88024081

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/014610 WO2023177547A1 (fr) 2022-03-14 2023-03-06 Améliorations de transmission en liaison montante à huit ports

Country Status (1)

Country Link
WO (1) WO2023177547A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200083939A1 (en) * 2017-03-31 2020-03-12 Lg Electronics Inc. Wireless communication system enhancement link data transfer method and apparatus thereof
US20200100327A1 (en) * 2017-07-27 2020-03-26 Intel IP Corporation Physical uplink shared channel (pusch) transmission based on robust codebook
US20200177261A1 (en) * 2017-09-07 2020-06-04 Lg Electronics Inc. Method for transmitting an uplink signal based on a codebook in a wireless communication system and apparatus therefor
US20210314873A1 (en) * 2018-05-11 2021-10-07 Datang Mobile Communications Equipment Co., Ltd. Uplink power control method, terminal and network device
US20210337534A1 (en) * 2020-05-13 2021-10-28 Intel Corporation Ue configured for pusch repetition based on tpmi index and sri

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200083939A1 (en) * 2017-03-31 2020-03-12 Lg Electronics Inc. Wireless communication system enhancement link data transfer method and apparatus thereof
US20200100327A1 (en) * 2017-07-27 2020-03-26 Intel IP Corporation Physical uplink shared channel (pusch) transmission based on robust codebook
US20200177261A1 (en) * 2017-09-07 2020-06-04 Lg Electronics Inc. Method for transmitting an uplink signal based on a codebook in a wireless communication system and apparatus therefor
US20210314873A1 (en) * 2018-05-11 2021-10-07 Datang Mobile Communications Equipment Co., Ltd. Uplink power control method, terminal and network device
US20210337534A1 (en) * 2020-05-13 2021-10-28 Intel Corporation Ue configured for pusch repetition based on tpmi index and sri

Similar Documents

Publication Publication Date Title
US20240155517A1 (en) Enhanced uplink power control
US20240155536A1 (en) Ue uplink timing for non-terrestrial networks
US20220030606A1 (en) Enhanced repetition mechanism for physical uplink control channel
WO2022232098A1 (fr) Interfaces à base de service ran
WO2023177547A1 (fr) Améliorations de transmission en liaison montante à huit ports
US20230023383A1 (en) Edge application servers and 5gc network function measurements
US20240163897A1 (en) Enhanced group dci format 2_3 for srs transmission
US20240178976A1 (en) Enhanced srs carrier switching in 5g networks
US20230224845A1 (en) Receive timing difference definition for high subcarrier spacing
US20240195549A1 (en) Scell dormancy switching with scell-pcell cross-carrier scheduling
US20230147905A1 (en) Multi-slot physical downlink control channel monitoring
US20240214888A1 (en) Radio resource management requirements for inter cell beam measurement
US20240072912A1 (en) Rstd measurement accuracy requirements applicability
US20240154731A1 (en) Cancelled and dropped harq feedback retransmission techniques
WO2024019888A1 (fr) Transmission simultanée multi-panneaux et multi-trp
WO2023154331A1 (fr) Retard de commutation tci commun pour agrégation de porteuses
KR20230155478A (ko) 채널 상태 정보 보고
WO2023014847A1 (fr) Exigences de gestion de ressources radio pour cadre d'indicateur de configuration de transmission unifiée
WO2024025707A1 (fr) Gestion de collisions et génération d'un livre de codes de harq-ack pour agrégation de porteuses de liaison latérale
WO2023141074A1 (fr) Attribution de ressources pour transmissions sur porteuses composantes multiples
WO2023154386A1 (fr) Procédure lbt multiporteuse/multifaisceau au-dessus de 52.6ghz
WO2023069688A1 (fr) Ajustement temporel de liaison montante dans des déploiements à grande vitesse
WO2023081058A1 (fr) Association d'informations d'emplacement de point de référence et de mesure ao
WO2024019880A1 (fr) Mécanismes de multiplexage pour transmission sl prs et pscch
WO2023069680A1 (fr) Mesures d'équipement utilisateur non terrestre

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23771240

Country of ref document: EP

Kind code of ref document: A1