[go: up one dir, main page]

WO2025079051A1 - Suppression de livre de codes pour antennes tx 4 ue - Google Patents

Suppression de livre de codes pour antennes tx 4 ue Download PDF

Info

Publication number
WO2025079051A1
WO2025079051A1 PCT/IB2024/060049 IB2024060049W WO2025079051A1 WO 2025079051 A1 WO2025079051 A1 WO 2025079051A1 IB 2024060049 W IB2024060049 W IB 2024060049W WO 2025079051 A1 WO2025079051 A1 WO 2025079051A1
Authority
WO
WIPO (PCT)
Prior art keywords
srs
pusch
ports
antenna
transmission
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/IB2024/060049
Other languages
English (en)
Inventor
Sven JACOBSSON
Robert Mark Harrison
Andreas Nilsson
Chandan PRADHAN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2025079051A1 publication Critical patent/WO2025079051A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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/0404—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas the mobile station comprising multiple antennas, e.g. to provide uplink diversity
    • 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
    • H04B7/0481—Special codebook structures directed to feedback optimisation using subset selection of codebooks
    • 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/0691—Hybrid systems, i.e. switching and simultaneous transmission using subgroups of transmit antennas
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/06—TPC algorithms
    • H04W52/14—Separate analysis of uplink or downlink
    • H04W52/146—Uplink power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/30—Transmission power control [TPC] using constraints in the total amount of available transmission power
    • H04W52/32—TPC of broadcast or control channels
    • H04W52/325—Power control of control or pilot channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/38—TPC being performed in particular situations
    • H04W52/42—TPC being performed in particular situations in systems with time, space, frequency or polarisation diversity

Definitions

  • the present disclosure relates generally to a wireless communications system and, more specifically, blanking transmissions in a wireless communications system.
  • PUSCH Physical Uplink Shared Channel
  • NW Network
  • UE User Equipment
  • CB codebook
  • NCB non-CB
  • CB-based PUSCH is enabled if the higher-layer parameter txConfig in PUSCH-Config IE is set to codebook.
  • CB-based PUSCH transmission can be summarized in the following steps, which are illustrated in Figure 1.
  • the UE transmits up to two Sounding Reference Signal (SRS) resources in an SRS resource set with usage ‘codebook’, with up to four SRS ports each.
  • SRS Sounding Reference Signal
  • the gNodeB i.e., the NR base station
  • TPMI Precoding Matrix Indicator
  • SRI SRS Resource Indicator
  • the UE transmits PUSCH according to the received indication.
  • SRS resource 0 and 1 belong to an SRS resource set configured with usage ‘codebook’.
  • the number of SRS ports per SRS resource is 1, 2, or 4.
  • the UE transmits SRS, which is configured in an SRS resource set with higher-layer parameter usage in SRS-Config IE set to codebook.
  • SRS which is configured in an SRS resource set with higher-layer parameter usage in SRS-Config IE set to codebook.
  • the gNB selects a TPMI value, which specifies a rank and a precoding matrix, and indicates said TPMI via the Downlink Control Information (DCI) field “Precoding information and number of layers”.
  • DCI Downlink Control Information
  • DMRS Demodulation Reference Signal
  • the gNB indicates the selected SRS resource via the 1 -bit SRI field in the DCI scheduling the PUSCH transmission. If only one SRS resource is configured in the SRS resource set, the SRI field is not present in the DCI.
  • the rank must be less than a maximum number of layers, which is configured by the higher-layer parameter maxRank in PUSCH-Config IE (see above snippet of ASN code from 3GPP TS 38.331 version 17.2.0), based on reported UE capability.
  • the precoder is selected from a codebook subset, which is configured via the higher- layer parameter codebookSubset _in PUSCH-Config IE (see above snippet of ASN code from 3GPP TS 38.331 version 17.2.0), based on reported UE capability, and is one of fully coherent, partially coherent, or non-coherent.
  • the UE receives the DCI and performs PUSCH transmission, where the indicated number of PUSCH layers (and associated DMRS ports) are mapped to the antenna ports corresponding to the SRS ports in the indicated SRS resource via the indicated precoding matrix.
  • the number of bits in DCI used for indicating the number of layers (if transform precoding is enabled, the number of layers is limited to 1) and the precoder (the precoder candidates are tabulated in Clause 6.3.1.5 of 3GPP TS 38.211) is determined as follows:
  • NCB-based PUSCH is enabled if the higher-layer parameter txConfig in PUSCH-Config IE is set to nonCodebook and is intended for reciprocitybased UL transmission.
  • NW i.e., gNB
  • CSI-RS Channel State Information Reference Signal
  • the UE transmits up to four single-port SRS resources in an SRS resource set with usage ‘nonCodebook’.
  • the gNB sends an SRI that indicates which SRS resources that UE should use for PUSCH.
  • UE transmits PUSCH according to the received indication, where one PUSCH layer is transmitted per SRS resource.
  • the NW transmits CSI- RS which enables UE to estimate the DL channel and to compute an UL precoder.
  • the UE transmits SRS, which is configured in an SRS resource set with higher-layer parameter usage in SRS-Config UE set to nonCodebook.
  • SRS Signal-to-SIG
  • Up to four SRS resources (depending on UE capability), each with a single SRS port, can be configured in the SRS resource set, where the UE selects a suitable precoder for each SRS resource based on the CSI-RS.
  • the NW measures the UL channel based on the received SRS, selects the preferred SRS resource(s), and indicates the selection via the SRI field in DCI.
  • the UE receives the DCI and performs PUSCH transmission with a transmission rank that equals the number of indicated SRS resources (one PUSCH layer per SRS resource, or, equivalently, one PUSCH layer per SRS port).
  • 1V SRS is the number of SRS resources and L max is maximum number of layers.
  • the N2 antenna port precoder is one of a predefined set of N2 antenna port precoders, but the network node is only allowed to indicate one of a subset of the predefined set of N2 antenna port precoders.
  • N 1 3
  • the UE capability further informs the network node that a maximum rank supported by the UE is 3.
  • the UE capability further indicates that the UE supports full power mode 2 for 3 transmit, Tx, codebook, CB, -based PUSCH.
  • the UE capability further indicates a supported SRS configuration with different number of antenna ports per SRS resource for uplink full power Mode 2 operation, where the indication can consist of one or more of the following options: two SRS resources with 1 SRS port and 2 SRS ports, respectively; two SRS resources with 1 SRS port and 3 SRS ports, respectively; two SRS resources with 2 SRS ports and 3 SRS ports, respectively; and three SRS resource with 1, SRS port, 2 SRS ports and 3 SRS ports, respectively.
  • reporting the UE capability further comprises reporting an indication of SRS ports used to attain full power with a bitfield of size 3, say (s 0 , s 2 ), which signals the SRS ports that should be transmitted using a configured Transmit Precoding Matrix Indicator (TPMI).
  • TPMI Transmit Precoding Matrix Indicator
  • the SRS configuration comprises one or more of: a blanked Import SRS resource, a Ni-port SRS resource, a combination of SRS resources consisting of one or more 1-port SRS resources and 2-port SRS resources, and an N2-port SRS resource for which the network node expects the UE to map PUSCH layers to at most Ni out of the N2 SRS ports.
  • the SRS configuration comprises Ni single-port SRS resources.
  • a UE is adapted to report, to a network node, a UE capability for transmission on Ni antenna ports and receive, from the network node, information that configures the UE to transmit an SRS resource with N2 antenna ports, where N2 > Ni.
  • the UE is further adapted to determine a total power for a PUSCH transmission using an Ni antenna port subset of an N2 antenna port precoder, after scaling, by scaling a linear power value for the PUSCH transmission by a ratio of a number of antenna ports with a non-zero PUSCH transmission power to Ni and splitting the scaled power value equally across the antenna ports on which the UE transmits the PUSCH with non-zero PUSCH transmission power.
  • the UE is further adapted to transmit the PUSCH transmission using the Ni antenna port subset of the N2 antenna port precoder.
  • a UE comprises a communication interface comprising a transmitter and a receiver, and processing circuitry associated with the communication interface configured to cause the UE to report, to a network node, a UE capability for transmission on Ni antenna ports and receive, from the network node, information that configures the UE to transmit an SRS resource with N2 antenna ports, where N2 > Ni.
  • the processing circuitry is further configured to cause the UE to determine a total power for a PUSCH transmission using an Ni antenna port subset of an N2 antenna port precoder, after scaling, by scaling a linear power value for the PUSCH transmission by a ratio of a number of antenna ports with a non-zero PUSCH transmission power to Ni and splitting the scaled power value equally across the antenna ports on which the UE transmits the PUSCH with non-zero PUSCH transmission power.
  • the processing circuitry is further configured to cause the UE to transmit the PUSCH transmission using the Ni antenna port subset of the N2 antenna port precoder.
  • a method performed by a network node comprises receiving, from a UE, information indicative of a UE capability for transmission on Ni antenna ports and transmitting, to the UE, information that configures the UE to transmit an SRS resource with N2 antenna ports, where N2 > Ni.
  • the method further comprises receiving, from the UE, a PUSCH transmission that uses an Ni antenna port subset of an N2 antenna port precoder.
  • Figure 2 illustrates non-CB (NCB)-based precoding in a wireless communications system
  • FIGS. 4A and 4B illustrate an example where the UE is indicated with a 4-port precoder for rank 1, and maps three of the entries of the 4-port precoder to three previously transmitted Sounding Reference Signal (SRS) ports, in accordance with an embodiment of the present disclosure;
  • SRS Sounding Reference Signal
  • Figure 6 shows a UE in accordance with some embodiments
  • Figure 8 is a block diagram of a host, which may be an embodiment of the host of
  • Figure 10 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • NR New Radio
  • 3GPP 3 rd Generation Partnership Project
  • UL uplink
  • Tx transmit
  • UEs User Equipments
  • PA Power Amplifier
  • CPE Customer Premises Equipment
  • FWA Fixed Wireless Access
  • 3 Tx chains e.g., MediaTek T830 CPE platform
  • CA Carrier Aggregation
  • FDD Frequency Division Duplexing
  • TDD Time Division Duplexing
  • Legacy NR does not support 3 Tx UL transmission in the same cell.
  • a Sounding Reference Signal (SRS) resource only can be configured with 1, 2, 4, or 8 SRS ports
  • a Transmit Precoding Matrix Indicator (TPMI) field can only indicate a precoder over 1, 2, 4 or 8 SRS ports
  • an SRS Resource Indicator (SRI) field can only indicate up to 1, 2, 4, or 8 SRS resources.
  • SRS Sounding Reference Signal
  • TPMI Transmit Precoding Matrix Indicator
  • SRI SRS Resource Indicator
  • the UE determines a total power for transmission after scaling by scaling the linear value of the PUSCH transmission by the ratio of the number of antenna ports with a non-zero PUSCH transmission power to and splitting the power equally across the antenna ports on which the UE transmits the PUSCH with nonzero power.
  • a UE reports support for 3 Tx UL transmission.
  • UE capability signaling may be different for codebook (CB)-based and non-CB (NCB)-based PUSCH, e.g., as per the following:
  • CB-based PUSCH In legacy NR (i.e., in existing NR specification), for CB-based PUSCH, a UE can indicate, via UE capability signaling, that the maximum number of supported SRS ports and PUSCH layers is one of 1, 2, 4, or 8. Based on this indication, the network (NW) (e.g., gNB) can configure a number of SRS ports that is less than or equal to the reported maximum rank, and PUSCH maximum rank that is less than or equal to the configured number of SRS ports, which, in turn, will determine the size of the TPMI in the Downlink Control Information (DCI) scheduling PUSCH.
  • DCI Downlink Control Information
  • this also informs the NW that the maximum number of SRS ports per SRS resource in an SRS resource set with usage ‘codebook’ that can be configured for the UE is 3. o In one embodiment, for 3 Tx UEs, new UE capability reporting is introduced such that UE can report support for 3 Tx CB-based PUSCH.
  • this also informs the NW that the supported maximum rank is 3.
  • the UE indicates the supported SRS configuration with different number of antenna ports per SRS resource for uplink full power Mode 2 operation, where the indication can consist of one or more of the following options:
  • the NW should indicate a TPMI that maps the layer to SRS port 1000, 1001 and 1002.
  • new UE capability reporting is introduced such that UE can report that the maximum number of PUSCH layers is 3.
  • new UE capability reporting is introduced such that UE can report support for 3 Tx NCB-based PUSCH.
  • this also informs the NW that the maximum number of SRS resources in an SRS resource set with usage ‘nonCodebook’ that can be configured for the UE is 3
  • this also informs the NW that the supported maximum rank is 3.
  • the maximum PUSCH rank is signaled via legacy UE capability signaling.
  • a second step the UE is configured, in Radio Resource Control (RRC), with 3 Tx CB-based PUSCH or 3 Tx NCB-based PUSCH, and associated SRS configuration:
  • RRC Radio Resource Control
  • the SRS configuration comprises one or more of: o
  • a new blanked 4-port SRS resource enables a 3 Tx UE to support 3-port SRS transmission with reusing a 4- port SRS resource by muting one of the ports of the configured 4-port SRS resource.
  • a new 3-port SRS resource o
  • a new combination of SRS resources consisting of one or more 1-port SRS resources and 2-port SRS resources o
  • a legacy (i.e., in existing specification) 4-port SRS resource but for which the NW expects UE to map PUSCH layers to at most 3 out of the 4 SRS ports (a subset of a larger set of SRS ports, in a more general embodiment). For this option, legacy SRS design can be reused.
  • UE will not map PUSCH to the SRS with highest port index.
  • UE if UE is configured with 3 Tx CB-based PUSCH, it shall not transmit the SRS port that PUSCH will not be mapped to.
  • the SRS configuration comprises 3 single-port SRS resources (as in legacy specification).
  • a 3 Tx UE is configured with a 4-port fully-coherent codebook, and the maximum rank is set to 1, which means that the precoders seen in the upper part of the figure can be indicated for PUSCH transmission.
  • each precoder has 4 different entries, corresponding to the PUSCH precoder weight for each of 4 SRS ports (where the first entry is associated with SRS port 1000, the second entry is associated with SRS port 1001, the third entry is associated with SRS port 1002, and the fourth entry is associated with SRS port 1003).
  • the UE since the UE only has 3 Tx chains, we here assume that the UE only has transmitted three SRS ports; SRS Port 1000, SRS port 1001 and SRS port 1002.
  • the UE ignores the entry of the indicated PUSCH precoder associated with the SRS port that has not previously been transmitted (i.e., SRS port 1003, in this example). I.e., the UE should apply only the three first entries of the indicated PUSCH precoder over the three or more previously transmitted associated SRS ports, and the UE should ignore the last entry of the indicated precoder, as illustrated in the figure.
  • UE will not map a PUSCH layer to the SRS/PUSCH port(s) with highest port index.
  • the UE is not expected to be indicated with TPMI values for which a PUSCH layer is mapped solely to the PUSCH/SRS port in the subset that is not transmitted.
  • the TPMI field in DCI does not contain such precoders (to reduce overhead).
  • a subset of partially-coherent 4 Tx precoders for rank 1 are additionally included, wherein the subset fulfills above requirements (e.g., does not map a PUSCH layer to the SRS/PUSCH port with highest port index).
  • UE transmits PUSCH according to the received indication wherein the PUSCH is mapped to at most of the > configured (and possibly transmitted) number of SRS ports (for CB-based PUSCH) or N 1 SRS resources (for NCB-based PUSCH).
  • NW receives the PUSCH.
  • a UE can use a codebook designed for more ports than the number of Tx chains the UE has, the network should still be aware of the number of Tx chains, or equivalently the maximum number of ports that the UE supports in an SRS resource. This is because the UE will not be able to transmit more layers than Tx chains and may also in some cases allow the network to determine which elements of the precoder the UE will actually use for transmission. Therefore, it can be beneficial for the UE to signal its capability to transmit on antenna ports to the network.
  • an N 2 port codebook of precoders can already be used for by UEs that support N 2 ports in an SRS resource, the control signaling and transmission precoders should already be designed. Then by configuring the UE to transmit an SRS resource with N 2 ports, where N 2 > N- , considerable design effort can be saved. The UE will then operate as it would with the N 2 port configuration by receiving and transmitting using N 2 port TPMIs, as long as they have at most N- layers.
  • the UE will transmit zero power on an N 2 — port subset of the antenna ports, that is it will transmit non-zero power on port subset of the N 2 ports supported by the precoders that are indicated to it by the network. This can be further understood with an example where
  • a 3 row precoder matrix W can be defined where w ., Wp ., Wp k are each a row of a precoder for 4 SRS ports.
  • the 3 row precoder can be taken from a 4 row precoder defined for the 4 port codebook by selecting a subset of antenna ports to be use for transmission.
  • the UE may scale the transmitted power such that the transmitted power on a given antenna port is at most 1/N, where N is the number of ports supported by the codebook and/or the maximum number of SRS ports in one resource that are supported by the UE.
  • the UE may first calculate a linear value q d , I), with parameters as defined in clause 7.1.1 of 3GPP TS 38.213.
  • the UE may also scale the linear value by the ratio of the number of antenna ports with a non-zero PUSCH transmission power to the maximum number of SRS ports supported by the UE in one SRS resource, and then split the power equally across the antenna ports on which the UE transmits the PUSCH with non-zero power.
  • the UE uses the number of ports in an SRS resource indicated by SRI instead of the maximum number of SRS ports supported by the UE in one SRS resource.
  • the UE would scale the power by N /N 2 ⁇ 1 when transmitting on all its TX chains, and so would not reach full power transmission. Therefore, it is beneficial in some embodiments for the UE to determine a total power for transmission after scaling by scaling the linear value of the PUSCH transmission by the ratio of the number of antenna ports with a non-zero PUSCH transmission power to and splitting the power equally across the antenna ports on which the UE transmits the PUSCH with non-zero power.
  • a UE indicates capability to transmit on at most N- antenna ports (see Step 300).
  • the UE is configured to transmit an SRS resource with N 2 ports, where N 2 > (see Step 302).
  • the UE further receives an indication of an N 2 port precoder to use for transmission (i.e., PUSH transmission) (see Step 308).
  • the UE also transmits using an lport subset of the N 2 port precoder (see Step 310).
  • the UE determines a total power for transmission after scaling by scaling the linear value of the PUSCH transmission by the ratio of the number of antenna ports with a non-zero PUSCH transmission power to and splitting the power equally across the antenna ports on which the UE transmits the PUSCH with non-zero power (step 1104). Note that the determination of the total power for transmission after scaling may be considered as part of Step 310 or be considered as a step prior to the transmission in Step 310.
  • Figure 5 shows an example of a communication system 500 in accordance with some embodiments.
  • the communication system 500 includes a telecommunication network 502 that includes an access network 504, such as a Radio Access Network (RAN), and a core network 506, which includes one or more core network nodes 508.
  • the access network 504 includes one or more access network nodes, such as network nodes 510A and 510B (one or more of which may be generally referred to as network nodes 510), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs).
  • 3GPP Third Generation Partnership Project
  • APs non-3GPP Access Points
  • a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor.
  • network nodes include disaggregated implementations or portions thereof.
  • the telecommunication network 502 includes one or more Open-RAN (ORAN) network nodes.
  • ORAN network node is a node in the telecommunication network 502 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 502, including one or more network nodes 510 and/or core network nodes 508.
  • ORAN Open-RAN
  • Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O- CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non- real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification).
  • a near-real time control application e.g., xApp
  • rApp non-real time control application
  • the network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface.
  • an ORAN access node may be a logical node in a physical node.
  • an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized.
  • the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.
  • the network nodes 510 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.
  • UE User Equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 500 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 510 and other communication devices.
  • the network nodes 510 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 512 and/or with other network nodes or equipment in the telecommunication network 502 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 502.
  • the core network 506 connects the network nodes 510 to one or more hosts, such as host 516. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 506 includes one more core network nodes (e.g., core network node 508) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-Concealing Function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the communication system 500 of Figure 5 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 500 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile
  • the telecommunication network 502 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 502. For example, the telecommunication network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and/or massive Machine Type Communication (mMTC)/massive Internet of Things (loT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • LoT massive Internet of Things
  • the UEs 512 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504.
  • a UE may be configured for operating in single- or multi -Radio Access Technology (RAT) or multi -standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e., being configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • MR-DC Multi-Radio Dual Connectivity
  • E-UTRAN Evolved UMTS Terrestrial RAN
  • EN-DC Dual Connectivity
  • the input/output interface 606 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 600.
  • a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an 0-RAN access node), and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS).
  • DAS Distributed Antenna System
  • the network node 700 does not include separate radio front-end circuitry 718; instead, the processing circuitry 702 includes radio front-end circuitry and is connected to the antenna 710. Similarly, in some embodiments, all or some of the RF transceiver circuitry 712 is part of the communication interface 706. In still other embodiments, the communication interface 706 includes the one or more ports or terminals 716, the radio front-end circuitry 718, and the RF transceiver circuitry 712 as part of a radio unit (not shown), and the communication interface 706 communicates with the baseband processing circuitry 714, which is part of a digital unit (not shown).
  • the antenna 710, the communication interface 706, and/or the processing circuitry 702 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 700. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 710, the communication interface 706, and/or the processing circuitry 702 may be configured to perform any transmitting operations described herein as being performed by the network node 700. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 708 provides power to the various components of the network node 700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 700 with power for performing the functionality described herein.
  • the network node 700 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 708.
  • the power source 708 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 700 may include additional components beyond those shown in Figure 7 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 700 may include user interface equipment to allow input of information into the network node 700 and to allow output of information from the network node 700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 700.
  • FIG 8 is a block diagram of a host 800, which may be an embodiment of the host 516 of Figure 5, in accordance with various aspects described herein.
  • the host 800 may be or comprise various combinations of hardware and/or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 800 may provide one or more services to one or more UEs.
  • the host 800 includes processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and memory 812.
  • processing circuitry 802 that is operatively coupled via a bus 804 to an input/output interface 806, a network interface 808, a power source 810, and memory 812.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 6 and 7, such that the descriptions thereof are generally applicable to the corresponding components of the host 800.
  • the memory 812 may include one or more computer programs including one or more host application programs 814 and data 816, which may include user data, e.g. data generated by a UE for the host 800 or data generated by the host 800 for a UE.
  • Embodiments of the host 800 may utilize only a subset or all of the components shown.
  • the host application programs 814 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of LEs (e.g., handsets, desktop computers, wearable display systems, and heads-up display systems).
  • VVC Versatile Video Coding
  • HEVC High Efficiency Video Coding
  • AVC Advanced Video Coding
  • MPEG Moving Picture Experts Group
  • VP9 Moving Picture Experts Group
  • audio codecs e.g., Free Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711
  • the host application programs 814 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 800 may select and/or indicate a different host for Over-The-Top (OTT) services for a LE.
  • the host application programs 814 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • DASH or MPEG-DASH Dynamic Adaptive Streaming over HTTP
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtual environments 900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs Virtual Machines
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • the virtualization environment 900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
  • Applications 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 900 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 904 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 906 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 908A and 908B (one or more of which may be generally referred to as VMs 908), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 906 may present a virtual operating platform that appears like networking hardware to the VMs 908.
  • a VM 908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 908, and that part of the hardware 904 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 908, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 908 on top of the hardware 904 and corresponds to the application 902.
  • the hardware 904 may be implemented in a standalone network node with generic or specific components.
  • the hardware 904 may implement some functions via virtualization.
  • the hardware 904 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 910, which, among others, oversees lifecycle management of the applications 902.
  • the hardware 904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a RAN or a base station.
  • some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 10 shows a communication diagram of a host 1002 communicating via a network node 1004 with a UE 1006 over a partially wireless connection in accordance with some embodiments.
  • Example implementations, in accordance with various embodiments, of the UE (such as the UE 512A of Figure 5 and/or the UE 600 of Figure 6), the network node (such as the network node 510A of Figure 5 and/or the network node 700 of Figure 7), and the host (such as the host 516 of Figure 5 and/or the host 800 of Figure 8) discussed in the preceding paragraphs will now be described with reference to Figure 10.
  • embodiments of the host 1002 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1002 also includes software, which is stored in or is accessible by the host 1002 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1006 connecting via an OTT connection 1050 extending between the UE 1006 and the host 1002.
  • a host application may provide user data which is transmitted using the OTT connection 1050.
  • the network node 1004 includes hardware enabling it to communicate with the host 1002 and the UE 1006.
  • the connection 1060 may be direct or pass through a core network (like the core network 506 of Figure 5) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like the core network 506 of Figure 5
  • one or more other intermediate networks such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1006 includes hardware and software, which is stored in or accessible by the UE 1006 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 1006 with the support of the host 1002.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 1006 with the support of the host 1002.
  • an executing host application may communicate with the executing client application via the OTT connection 1050 terminating at the UE 1006 and the host 1002.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1050 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application
  • the OTT connection 1050 may extend via the connection 1060 between the host 1002 and the network node 1004 and via a wireless connection 1070 between the network node 1004 and the UE 1006 to provide the connection between the host 1002 and the UE 1006.
  • the connection 1060 and the wireless connection 1070, over which the OTT connection 1050 may be provided, have been drawn abstractly to illustrate the communication between the host 1002 and the UE 1006 via the network node 1004, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1002 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 1006.
  • the user data is associated with a UE 1006 that shares data with the host 1002 without explicit human interaction.
  • the host 1002 initiates a transmission carrying the user data towards the UE 1006.
  • the host 1002 may initiate the transmission responsive to a request transmitted by the UE 1006.
  • the request may be caused by human interaction with the UE 1006 or by operation of the client application executing on the UE 1006.
  • the transmission may pass via the network node 1004 in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1012, the network node 1004 transmits to the UE 1006 the user data that was carried in the transmission that the host 1002 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1014, the UE 1006 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1006 associated with the host application executed by the host 1002.
  • the UE 1006 executes a client application which provides user data to the host 1002.
  • the user data may be provided in reaction or response to the data received from the host 1002.
  • the UE 1006 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1006. Regardless of the specific manner in which the user data was provided, the UE 1006 initiates, in step 1018, transmission of the user data towards the host 1002 via the network node 1004.
  • the network node 1004 receives user data from the UE 1006 and initiates transmission of the received user data towards the host 1002.
  • the host 1002 receives the user data carried in the transmission initiated by the UE 1006.
  • sensors may be deployed in or in association with other devices through which the OTT connection 1050 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1050 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1004. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 1002.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1050 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device but are enjoyed by the computing device as a whole and/or by end users and a wireless network generally.
  • Embodiment 1 A method performed by a user equipment, the method comprising one or more of
  • Embodiment 2 The method of any of the previous embodiments wherein the precoder candidates that can be indicated is limited to a subset of existing N 2 Tx precoders, wherein the subset is restricted according to some rules (e.g., depending on coherency, which PUSCH ports in the indicated precoder that has non-zero power, etc.).
  • Embodiment 3 The method of any of the previous embodiments wherein the precoder candidates that can be indicated (i.e., included/encoded in the TPMI field DCI) are all existing (i.e., in legacy specification) N 2 Tx precoders, but NW is allowed to indicate only a subset of them.
  • Embodiment 4 The method of any of the previous embodiments, the method further comprises: indicating capability to transmit on at most antenna ports.
  • Embodiment 5 The method of any of the previous embodiments the UE is configured to transmit an SRS resource with N 2 ports, where N 2 > N r .
  • Embodiment 6 The method of any of the previous embodiments the UE receives an indication of an N 2 port precoder to use for transmission.
  • Embodiment 7 The method of any of the previous embodiments the UE transmits using an Alport subset of the N 2 port precoder.
  • Embodiment 10 The method of any of the previous embodiments wherein for 3 Tx UEs, new UE capability reporting is introduced such that UE can report support for 3 Tx CB- based PUSCH.
  • Embodiment 11 The method of any of the previous embodiments wherein the new UE capability also informs the NW that the maximum number of SRS ports per SRS resource in an SRS resource set with usage ‘codebook’ that can be configured for the UE is 3.
  • Embodiment 18 The method of any of the previous embodiments wherein, if the bitfield is (0,1,0), then SRS port 1001 can transmit with full power, accordingly the NW should indicate a TPMI that maps the layer to SRS port 1001.
  • Embodiment 19 The method of any of the previous embodiments wherein, if the bitfield is (1,1,0), then SRS port 1000 and 1001 can transmit with full power, accordingly the NW should indicate a TPMI that maps the layer to SRS port 1000 and 1001.
  • Embodiment 20 The method of any of the previous embodiments wherein, if the bitfield is (1,1,1), then SRS port 1000, 1001 and 1002 can transmit with full power, accordingly the NW should indicate a TPMI that maps the layer to SRS port 1000, 1001 and 1002.
  • Embodiment 21 The method of any of the previous embodiments wherein each bit in the bitfield can indicate two different values of the PA configuration for each SRS port, i.e., 1 and 0 for Sj, i E ⁇ 0,1,2 ⁇ , signal that the SRS port (1000 + 1) can transmit either with maximum power P max or a fraction of maximum power P m(lx lx'.. i respectively, where x depends on UE capability.
  • Embodiment 22 The method of any of the previous embodiments wherein the NW indicates a TPMI that attains full power by transmitting the layer (e.g., in case of rank 1) on either one SRS port with maximum power, or on more than one SRS port such that maximum power can be attained.
  • Embodiment 23 The method of any of the previous embodiments wherein, for 3 Tx UEs, new UE capability reporting is introduced such that UE can report that the maximum number of PUSCH layers is 3.
  • Embodiment 24 The method of any of the previous embodiments wherein, for 3 Tx UEs, new UE capability reporting is introduced such that UE can report support for 3 Tx NCB- based PUSCH.
  • Embodiment 25 The method of any of the previous embodiments wherein the maximum PUSCH rank is signaled via legacy UE capability signaling.
  • Embodiment 26 The method of any of the previous embodiments wherein if UE capability signaling indicates support for rank > 3 and support for 3 Tx NCB, NW should not indicate UE with PUSCH transmission (e.g., UE is not expected to receive SRI indication) of more than 3 layers.
  • Embodiment 27 The method of any of the previous embodiments wherein the SRS configuration comprises one or more of:
  • Embodiment 28 The method of any of the previous embodiments wherein the SRS configuration comprises 3 single-port SRS resources (e.g., as in legacy specification).
  • Embodiment 29 The method of any of the previous embodiments, further comprising:
  • mapping lV 2 -port PUSCH precoder to up to N SRS/PUSCH ports out of N 2 > N SRS/PUSCH ports;
  • Embodiment 31 The method of the previous claim further including any of the features of the Group B Embodiments.

Landscapes

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

Abstract

L'invention divulgue des systèmes et des procédés associés à une transmission en liaison montante N1 par un équipement utilisateur (UE) (Tx) par la suppression d'un N2 Tx prédicteur. Dans un mode de réalisation, un procédé mis en œuvre par un équipement utilisateur (UE) comprend le rapport d'une capacité d'UE pour une transmission sur N1 ports d'antenne, la réception d'informations qui configurent l'UE pour transmettre une ressource de signal de référence de sondage (SRS) avec N2 > N1 ports d'antenne, et la détermination d'une puissance totale mise à l'échelle pour une transmission de canal partagé de liaison montante physique (PUSCH) à l'aide d'un sous-ensemble de N1 ports d'antenne d'un N2 prédicteur de port d'antenne. La mise à l'échelle est effectuée à l'aide d'une valeur de puissance linéaire pour la transmission PUSCH par un rapport d'un nombre de ports d'antenne avec une puissance de transmission PUSCH différente de zéro à N1 et la division de la valeur de puissance mise à l'échelle de manière égale à travers les ports d'antenne avec une puissance de transmission PUSCH différente de zéro. Le procédé consiste en outre à transmettre la transmission PUSCH à l'aide du sous-ensemble de N1 ports d'antenne du N2 prédicteur de port
PCT/IB2024/060049 2023-10-13 2024-10-14 Suppression de livre de codes pour antennes tx 4 ue Pending WO2025079051A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202363590172P 2023-10-13 2023-10-13
US63/590,172 2023-10-13
US202363590578P 2023-10-16 2023-10-16
US63/590,578 2023-10-16

Publications (1)

Publication Number Publication Date
WO2025079051A1 true WO2025079051A1 (fr) 2025-04-17

Family

ID=93258845

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2024/060049 Pending WO2025079051A1 (fr) 2023-10-13 2024-10-14 Suppression de livre de codes pour antennes tx 4 ue

Country Status (1)

Country Link
WO (1) WO2025079051A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220109474A1 (en) * 2019-02-13 2022-04-07 Idac Holdings, Inc. Ul mimo full tx power

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220109474A1 (en) * 2019-02-13 2022-04-07 Idac Holdings, Inc. Ul mimo full tx power

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SPREADTRUM COMMUNICATIONS: "Discussion on full TX power for UL transmission", vol. RAN WG1, no. Xi'an, China; 20190408 - 20190412, 7 April 2019 (2019-04-07), XP051699962, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN1/Docs/R1%2D1904797%2Ezip> [retrieved on 20190407] *

Similar Documents

Publication Publication Date Title
WO2023211352A1 (fr) Indication de format de créneau dynamique
WO2023166498A1 (fr) Systèmes et procédés d&#39;association implicite entre une transmission pusch à trp multiples et des états tci unifiés
US20250030512A1 (en) Configured grant for multi-panel uplink transmission
WO2024161343A1 (fr) Saut à décalage en peigne et à décalage cyclique srs combinés/séparés
WO2024094806A1 (fr) Ensembles de ressources de commande et blocs de signaux de synchronisation pour nouvelle radio ayant une largeur de bande inférieure à 5 mhz
WO2024033731A1 (fr) Rapport de faisceau basé sur un groupe pour une transmission et une réception simultanées à panneaux multiples
EP4494294A1 (fr) Tables de port d&#39;antenne pour canal physique partagé de liaison montante ayant un nombre accru de codes de domaine de fréquence
WO2023073677A2 (fr) Mesures dans un réseau de communication
WO2025079051A1 (fr) Suppression de livre de codes pour antennes tx 4 ue
US20250063574A1 (en) Mac ce signaling for supporting both joint dl/ul tci and separate dl/ul tci operations
WO2024125362A1 (fr) Procédé et appareil de commande de liaison de communication entre dispositifs de communication
US20250293749A1 (en) Methods and nodes to perform precoder candidate restriction for multi-antenna ue
WO2024152307A1 (fr) Procédé et appareils pour la transmission sans fil
WO2024171151A1 (fr) Signalisation de configuration de csi-rs pour réseau d&#39;antennes ultralarge
WO2025038022A1 (fr) Livre de codes non cohérent en mode 1 à pleine puissance pour ue 8 tx
WO2024189602A1 (fr) Rapport d&#39;interférence
WO2024033890A1 (fr) Restrictions de livre de codes pour livres de codes de liaison montante partiellement cohérent
WO2024172749A1 (fr) Rapport d&#39;informations csi basé sur de multiples décalages de puissance
EP4666462A1 (fr) Rapport d&#39;informations csi basé sur de multiples décalages de puissance
WO2024157177A1 (fr) Procédés et nœuds pour indication de puissance de sortie srs
WO2025027480A1 (fr) Rétroaction par ue de différences de fréquence de liaison descendante entre des trp
WO2025027504A2 (fr) Procédés de signalisation d&#39;agrégation de ressources de csi-rs pour grands réseaux
WO2024141989A1 (fr) Amplification de puissance adaptative pour signal de référence de sondage
WO2025010020A1 (fr) Sélection de mode duplex d&#39;ue pour économie d&#39;énergie
WO2024043817A1 (fr) Association de ports de signal de référence de démodulation (dmrs) pour un équipement utilisateur de transmission multi-panneau simultanée

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: 24795292

Country of ref document: EP

Kind code of ref document: A1