DE102021109966A1 - PROCEDURE FOR TRANSMISSION IN THE UPLINK WITH FULL POWER FOR FULLY COHERENT USER DEVICES (UE) IN NEW RADIO (NR) - Google Patents

Abstract

Apparatus for a New Radio (NR) user equipment (UE) having a radio frequency (HF) interface and one or more processors which are coupled to the HF interface and which are set up: a coherence capability information of the UE to send; receive configuration information including a codebook subset and a performance mode, the codebook subset and performance mode based on the coherency capability information; configure an uplink (UL) broadcast according to the configuration information.

Description

Cross reference to related application

This patent application claims the benefit and priority of US Provisional App. No. 63 / 015,290 , filed April 24, 2020.

Technical area

Various aspects can generally relate to the field of wireless communications.

background

The existing Release 16 (Rel-16) NR (e.g. TS 38.211) only specifies the transmission with full power for partially coherent and non-coherent UEs. For fully coherent UE, it is not specified whether the UE can be set up with uplink full power transmission and the corresponding operating mode, in particular if the codebook subset is set up as 'fullAndPartialAndNonCoherent'.

This disclosure describes various aspects of configuration and full power operation for fully coherent UE.

Figure list

• 1 ein beispielhaftes Codebuch für eine Ein-Schicht-Übertragung illustriert.
• 2 ein beispielhaftes Codebuch für eine Zwei-Schicht-Übertragung illustriert.
• 3 einen beispielhaften Codebuch-Teilsatz für ein transformationsvorkodierfähiges nichtkohärentes UE zeigt.
• 4 einen beispielhaften Codebuch-Teilsatz für ein transformationsvorkodierfähiges vollkohärentes UE zeigt.
• 5 einen beispielhaften Codebuch-Teilsatz für ein transformations-vorkodiertes, nicht-kohärentes UE zeigt.
• 6 einen beispielhaften Codebuch-Teilsatz für ein transformations-vorkodiertes, vollkohärentes UE zeigt.
• 7 ein Netzwerk gemäß verschiedenen Aspekten der vorliegenden Offenbarung illustriert.
• 8 schematisch ein Drahtlos-Netzwerk gemäß verschiedenen Aspekten der vorliegenden Offenbarung illustriert.
• 9 ein Blockdiagramm ist, das Hardwareressourcen gemäß Aspekten der vorliegenden Offenbarung veranschaulicht.
• 10 einen beispielhaften Prozess gemäß verschiedenen Aspekten der vorliegenden Offenbarung zeigt.
• 11 einen beispielhaften Prozess gemäß verschiedenen Aspekten der vorliegenden Offenbarung zeigt.

In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis generally being placed on illustrating the example principles of the disclosure. In the following description, various aspects of the disclosure are described with reference to the following drawings, in which:

• 1 illustrates an exemplary codebook for single-layer transmission.
• 2 illustrates an exemplary codebook for two-tier transmission.
• 3 Figure 3 shows an exemplary codebook subset for a transform precoded non-coherent UE.
• 4th shows an exemplary codebook subset for a transform precoded fully coherent UE.
• 5 shows an exemplary codebook subset for a transform precoded, non-coherent UE.
• 6th shows an exemplary codebook subset for a transform precoded, fully coherent UE.
• 7th illustrates a network in accordance with various aspects of the present disclosure.
• 8th schematically illustrates a wireless network in accordance with various aspects of the present disclosure.
• 9 Figure 4 is a block diagram illustrating hardware resources in accordance with aspects of the present disclosure.
• 10 Figure 8 shows an exemplary process in accordance with various aspects of the present disclosure.
• 11 Figure 8 shows an exemplary process in accordance with various aspects of the present disclosure.

Detailed description

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or like elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular structures, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of the various aspects. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various aspects can be practiced in other examples that depart from these specific details. In certain cases, descriptions of known devices, circuits, and methods are omitted in order not to obscure the description of the various aspects with unnecessary detail. For the purposes of this document, the terms “A or B” and “A / B” mean (A), (B) or (A and B).

The fifth generation (5G) NR Release 15 (Rel-15) specifies the codebook-based transmission for the uplink (UL). This transmission mode was developed taking into account various UE coherence capabilities, e.g. whether the UE can maintain the relative phase between all (full coherence), or a subset (partial coherence), or none (non-coherence) of its transmission chains / antenna ports over time.

In Rel-15, the UE can be set up in such a way that it works with a subset of precoders in the UL code book in accordance with the reported coherence capability. Note that according to the specification of the 3GPP (Third Generation Partnership Program), the UE capabilities “fullAndPartialAndNonCoherent”, “partialAndNonCoherent” and “nonCoherent” are considered fully coherent, partially coherent and not be referred to coherently. A UE capable of 'fullAndPartialAndNonCoherent' transmission can be set up with a codebook subset of 'fullAndPartialAndNonCoherent', 'partialAndNonCoherent' or 'nonCoherent'. A UE that is capable of “partialAndNonCoherent” transmission can be set up with the codebook subset “partialAndNonCoherent” or “nonCoherent”.

Using the example of a UE with two antenna connections, they show 1 until 6th the design of the uplink codebook and the codebook subset in the current NR Rel-16 specifications. 1 and 2 show the code book and TPMI (Transmission Precoding Matrix Index) illustration for two antenna ports with one or two transmission layers. 3 until 6th show the codebook subset as a function of the full power operating configuration.

1 shows the code book 100 for rank 1 with two antenna connections (TS 38.211).

2 shows the code book 200 for rank 2 with two antenna connections (TS 38.211).

3 shows codebook subset 300 for two antenna ports and maxRank = 1 with full power mode 1 (TS 38.212).

4th shows codebook subset 400 for two antenna ports and maxRank = 1 with full power mode 2 or without full power (TS 38.212).

5 shows codebook subset 500 for two antenna ports and maxRank = 2 with full power mode 1 (TS 38.212).

6th shows codebook subset 600 for two antenna ports and maxRank = 2 with full power mode 2 or without full power (TS 38.212).

oder $\frac{1}{\sqrt{2}}\left[\begin{array}{c}0\\ 1\end{array}\right]$

unterstützt, der die Übertragung entweder von der ersten oder der zweiten Antenne mit einer maximalen Leistung von 20 dBm ermöglicht.It should be noted that some coherency capabilities of the UE may not allow full power transmission. For example, with a UE with power class 3, the full transmission power is 23 dBm. If the UE has two antenna ports and a power amplifier (PA) with the maximum transmission power of 20 dBm, the full Tx power for UEs not capable of coherence could not be achieved. More precisely, only one antenna selection precoder from of $\frac{1}{\sqrt{2}}\left[\begin{array}{c}1\\ 0\end{array}\right]$

or $\frac{1}{\sqrt{2}}\left[\begin{array}{c}0\\ 1\end{array}\right]$

which enables transmission from either the first or the second antenna with a maximum power of 20 dBm.

• - UE-Fähigkeit 1
  • ◯ Jeder PA kann die Übertragung mit der vollen Leistung unterstützen. Zum Beispiel kann ein UE mit zwei PAs und jeder PA mit 23 dBm (23dBm + 23dBm) senden.
• - UE-Fähigkeit 2
  • ◯ Jeder PA kann nicht die volle Leistung liefern. Zum Beispiel UE mit zwei PAs und die maximale Tx-Leistung jedes PAs beträgt 20 dBm (20dBm + 20dBm). Kombiniert man zwei PAs miteinander, kann die volle Sendeleistung erreicht werden.
• - UE-Fähigkeit 3
  • ◯ Eine Teilmenge der PAs kann die volle Leistung liefern. Zum Beispiel kann ein UE mit zwei PAs und einem PA eine maximale Leistung von 23 dBm und der andere PA eine maximale Leistung von 20dBm (23dBm + 20 dBm) liefern.

In order to enable transmission with full power in the uplink, the following UE power amplifier architectures are taken into account:

• - UE ability 1
  • ◯ Each PA can support the transmission with full power. For example, a UE with two PAs and each PA can transmit at 23 dBm (23dBm + 23dBm).
• - UE ability 2
  • ◯ Every PA cannot deliver full performance. For example, UE with two PAs and the maximum Tx power of each PA is 20 dBm (20dBm + 20dBm). If you combine two PAs with each other, the full transmission power can be achieved.
• - UE ability 3
  • ◯ A subset of the PAs can deliver full power. For example, a UE with two PAs and one PA can deliver a maximum power of 23 dBm and the other PA a maximum power of 20dBm (23dBm + 20 dBm).

The NR Rel-16 specification defines three transmission modes for uplink full-power transmission. These are configured via the RRC parameter ul-FullPowerTransmission, which is set as a value of {full power (fullpower), full power mode 1 (fullpowerModel), full power mode 2 (fullpowerMode2)} corresponding to mode 0, mode 1 or mode 2 can be configured.

For UE capability 1, the UE is configured as full power mode 0.

For UE Capability 2 and UE Capability 3, it can be configured as Mode 1 or Mode 2.

• - Modus 0
  • ◯ Der Leistungsskalierungsfaktor ist fest auf 1 eingestellt
• - Modus 1
  • ◯ Das UE kann mit einer oder mehreren SRS-Ressourcen (Sounding Reference Signal) mit gleicher Anzahl von SRS-Ports innerhalb eines SRS-Ressourcensatzes konfiguriert werden.
  • ◯ Ein neuer Codebuch-Teilsatz, der zumindest den Nicht-Antennenauswahl-Vorkoder aufweist, wird gemäß 3 und 5 eingeführt, um die Übertragung mit voller Leistung zu unterstützen, z.B. $\frac{1}{\sqrt{2}}\left[\begin{array}{c}1\\ 1\end{array}\right].$
    
• - Modus 2
  • ◯ Das UE kann mit einer SRS-Ressource oder mehreren SRS-Ressourcen mit gleicher oder unterschiedlicher Anzahl von SRS-Ports innerhalb eines SRS-Ressourcensatzes konfiguriert werden.
  • ◯ Das UE sollte TPMI(s) an den gNB melden, der die Übertragung mit voller Leistung aktivieren kann, zum Beispiel $\left[\begin{array}{c}1\\ 0\end{array}\right]$
    
    or $\left[\begin{array}{c}0\\ 1\end{array}\right].$
    
  • ◯ Das Rel-15 Codebuch und der Codebuch-Teilsatz werden verwendet

How these modes work is briefly summarized below:

• - mode 0
  • ◯ The power scaling factor is permanently set to 1
• - mode 1
  • ◯ The UE can be configured with one or more SRS resources (Sounding Reference Signal) with the same number of SRS ports within an SRS resource set.
  • ◯ A new codebook subset, which has at least the non-antenna selection precoder, is according to 3 and 5 introduced to support transmission at full power, e.g. $\frac{1}{\sqrt{2}}\left[\begin{array}{c}1\\ 1\end{array}\right].$
    
• - Mode 2
  • ◯ The UE can be configured with one SRS resource or several SRS resources with the same or different numbers of SRS ports within an SRS resource set.
  • ◯ The UE should report TPMI (s) to the gNB, which can activate the transmission at full power, for example $\left[\begin{array}{c}1\\ 0\end{array}\right]$
    
    or $\left[\begin{array}{c}0\\ 1\end{array}\right].$
    
  • ◯ The Rel-15 codebook and the codebook subset are used

However, the existing Rel-16 specification only specifies the transmission of full power for partially coherent and non-coherent UEs. For fully coherent UE, it is not specified whether the UE can be configured with ul-FullPowerTransmission and the corresponding operating mode, especially if the codebook subset is configured as 'fullAndPartialAndNonCoherent'.

This disclosure describes various aspects of configuration and full power operation for fully coherent UE.

Full power operation for fully coherent UE.

UE capability 1 (full power operating mode 0).

• - Option 1: Es wird die Legacy-Rel-15-Leistungsskalierung angewendet, d.h. der Leistungsskalierungsfaktor „s“ ist das Verhältnis der Anzahl der Antennenports mit PUSCH-Leistung ungleich Null zur maximalen Anzahl der SRS-Antennenports, die das UE unterstützen kann.
• - Option 2: für fullAndPartialAndNonCoherent Codebuch-Teilsatz mit Modus 0 ist der Leistungsskalierungsfaktor „s“ immer gleich 1.

In one aspect, for fully coherent UE, when the codebook subset is configured as "fullAndPartialAndNonCoherent" and ul-FullPowerTransmission is configured as full power (mode 0), there are two options for the UE to have power scaling on the physical uplink splitter -Channel (Physical Uplink Shared Channel - PUSCH):

• - Option 1: Legacy Rel-15 power scaling is used, ie the power scaling factor "s" is the ratio of the number of antenna ports with PUSCH power not equal to zero to the maximum number of SRS antenna ports that the UE can support.
• - Option 2: for fullAndPartialAndNonCoherent codebook subset with mode 0, the power scaling factor "s" is always equal to 1.

In comparison, option 2 enables the transmission of the full power for all transmission precoding matrix indicators (transmitted pre-coding matrix indicators - TPMI) in the FullAndPartialAndNonCoherent codebook subset. With option 1, however, only the non-antenna selection TPMIs (fully coherent TPMIs) in the fullAndPartialAndNonCoherent subset of the codebook can support full performance.

According to another aspect, for fully coherent UE, if the codebook subset is configured as "fullAndPartialAndNonCoherent", the ul-FullPowerTransmission can only be configured as full power (mode 0), ie mode 1 or mode 2 cannot be configured for the UE if the codebook subset is configured as "fullAndPartialAndNonCoherent".

Full power operating mode 1.

According to one aspect for fully coherent UE, if the codebook subset is configured as 'fullAndPartialAndNonCoherent' and the ul-FullPowerTransmission is configured as full power mode 1 (mode 1), the UE uses the codebook subset 'fullAndPartialAndNonCoherent' for mode 1 -Operation. In the specification TS 38.212 the 'fullAndPartialAndNonCoherent' codebook subset for mode 1 should be added (to e.g. 3 and 5 to change). The power scaling factor "s" is the ratio of the number of antenna ports with PUSCH power not equal to zero to the maximum number of SRS antenna ports that the UE can support.

Full power operating mode 2.

TPMI message.

• - Option 1: Für die vollkohärente UE meldet sie keine TPMIs. Dies liegt daran, dass der Codebuch-Teilsatz „fullAndPartialAndNonCoherent“ sowohl die Nicht-Antennenauswahl-TPMIs als auch die Antennenauswahl-TPMIs aufweist. Mit den Nicht-Antennenauswahl-TPMIs kann das UE den Betrieb mit voller Leistung aktivieren. Für alle TPMIs ist der Leistungsskalierungsfaktor „s“ das Verhältnis der Anzahl der Antennenports mit PUSCH-Leistung ungleich Null zur maximalen Anzahl der SRS-Antennenports, die das UE unterstützen kann.
• - Option 2: Für vollkohärente UE meldet es weiterhin TPMIs, die die volle Leistung unterstützen. Aber das TPMI-Reporting basiert auf nicht-kohärenten oder partialAndNonCoherent-Codebuch-Teilsätzen, um den Overhead zu reduzieren. Für ein vollkohärentes UE mit 2 Übertragungen (Tx) sollte es TPMIs melden, die die Übertragung mit voller Leistung innerhalb des nichtkohärenten Codebuch-Teilsatzes unterstützen. Für ein vollkohärentes UE mit 4 Tx sollte es TPMIs melden, die eine Übertragung mit voller Leistung innerhalb des Teilsatzes „partialAndNonCoherent codebook“ unterstützen. Für diese gemeldeten TPMIs sollte der Leistungsskalierungsfaktor „s“ 1 sein. Für die TPMIs innerhalb des Codebuch-Teilsatzes „fullAndPartialAndNonCoherent“ mit Ausnahme der gemeldeten TPMIs ist der Leistungsskalierungsfaktor das Verhältnis der Anzahl der Antennenports mit PUSCH-Leistung ungleich Null geteilt durch die Anzahl der SRS-Antennenports der tatsächlich genutzten SRS-Ressource.
• - Option 3: Für vollkohärente UE werden TPMIs gemeldet, die die volle Leistung innerhalb des Codebuch-Teilsatzes „fullAndPartialAndNonCoherent“ unterstützen, was einen größeren Overhead bedeutet. Für die gemeldeten TPMIs sollte der Leistungsskalierungsfaktor „s“ 1 sein. Für die nicht gemeldeten TPMIs ist der Leistungsskalierungsfaktor das Verhältnis der Anzahl der Antennenports mit PUSCH-Leistung ungleich Null geteilt durch die Anzahl der SRS-Antennenports der tatsächlich genutzten SRS-Ressource.

According to one aspect or a fully coherent UE, if the codebook subset is configured as 'fullAndPartialAndNonCoherent' and the ul-FullPowerTransmission is configured as full power mode 2 (mode 2), there are several options for the UE to do the TPMI reporting for mode 2 operation can perform:

• - Option 1: It does not report any TPMIs for the fully coherent UE. This is because the codebook subset "fullAndPartialAndNonCoherent" has both the non-antenna selection TPMIs and the antenna selection TPMIs. The non-antenna selection TPMIs allow the UE to enable full power operation. For all TPMIs, the power scaling factor "s" is the ratio of the number of antenna ports with PUSCH power not equal to zero to the maximum number of SRS antenna ports that the UE can support.
• - Option 2: For fully coherent UE, it continues to report TPMIs that support full power. But the TPMI reporting is based on non-coherent or partialAndNonCoherent codebook subsets to reduce overhead. For a fully coherent UE with 2 transmissions (Tx) it should report TPMIs that the Support full power transmission within the non-coherent codebook subset. For a fully coherent UE with 4 Tx, it should report TPMIs that support transmission at full power within the subset “partialAndNonCoherent codebook”. The power scaling factor "s" should be 1 for these reported TPMIs. For the TPMIs within the codebook subset “fullAndPartialAndNonCoherent” with the exception of the reported TPMIs, the power scaling factor is the ratio of the number of antenna ports with PUSCH power not equal to zero divided by the number of SRS antenna ports of the SRS resource actually used.
• Option 3: For fully coherent UEs, TPMIs are reported that support the full performance within the codebook subset “fullAndPartialAndNonCoherent”, which means a greater overhead. The power scaling factor "s" should be 1 for the reported TPMIs. For the unreported TPMIs, the power scaling factor is the ratio of the number of antenna ports with PUSCH power not equal to zero divided by the number of SRS antenna ports of the SRS resource actually used.

Antenna virtualization.

• - Option 1: Die Antennenvirtualisierung ist nicht erlaubt, da der Codebuch-Teilsatz ‚fullAndPartialAndNonCoherent‘ alle TPMIs aufweist und das UE vollkohärent ist. Und es ist nicht notwendig, die Antennenvirtualisierung zu aktivieren, um die volle Leistung zu unterstützen.
• - Option 2: Die Antennenvirtualisierung ist weiterhin erlaubt, wenn der Codebuch-Teilsatz ‚fullAndPartialAndNonCoherent‘ konfiguriert ist.

According to one aspect, for fully coherent UE, when the codebook subset is configured as 'fullAndPartialAndNonCoherent' and the ul-FullPowerTransmission is configured as full power mode 2 (mode 2), there are two options for operating the antenna virtualization for mode 2:

• - Option 1: Antenna virtualization is not allowed because the codebook subset 'fullAndPartialAndNonCoherent' includes all TPMIs and the UE is fully coherent. And there is no need to enable antenna virtualization to support full performance.
• - Option 2: The antenna virtualization is still allowed if the codebook subset 'fullAndPartialAndNonCoherent' is configured.

Separate operating mode with full power for fully coherent UE.

• - Wenn Volle-Leistung konfiguriert ist (Modus 0), ist der Leistungsskalierungsfaktor „s“ 1.
• - Wenn Volle-Leistung-Modus 3 konfiguriert ist (Modus 3):
  • ◯ Das UE könnte TPMIs melden, die den Volle-Leistung-Betrieb unterstützen. Das TPMI-Reporting basiert auf nicht-kohärenten oder partialAndNonCoherent-Codebuch-Teilsätzen, um den Overhead zu reduzieren. Für ein vollkohärentes UE mit 2 Tx sollte es TPMIs melden, die eine Übertragung mit voller Leistung innerhalb des nichtkohärenten Codebuch-Teilsatzes unterstützen. Für ein voll kohärentes UE mit 4 Tx sollte es TPMIs melden, die eine Übertragung mit voller Leistung innerhalb der Teilmenge „partialAndNonCoherent codebook“ unterstützen. Für diese gemeldeten TPMIs sollte der Leistungsskalierungsfaktor „s“ 1 sein. Für die TPMIs innerhalb des Codebuch-Teilsatzes „fullAndPartialAndNonCoherent“ mit Ausnahme der gemeldeten TPMIs ist der Leistungsskalierungsfaktor das Verhältnis der Anzahl der Antennenports mit PUSCH-Leistung ungleich Null geteilt durch die Anzahl der SRS-Antennenports der tatsächlich verwendeten SRS-Ressource.
  • ◯ Das UE könnte keine TPMIs melden. In diesem Fall ist der Leistungsskalierungsfaktor für alle TPMIs innerhalb des Codebuch-Teilsatzes „fullAndPartialAndNonCoherent“ das Verhältnis der Anzahl der Antennenports mit PUSCH-Leistung ungleich Null geteilt durch die Anzahl der SRS-Antennenports der tatsächlich genutzten SRS-Ressource.

In another aspect, a separate full-power operating mode could be introduced for fully coherent UE, e.g. full-power mode 3. The parameter ul-FullPowerTransmission can be assigned a value of {full-power, full-power mode 1, full- Power mode 2, full power mode 3} can be configured. For the fully coherent UE, if the codebook subset is configured as 'fullAndPartialAndNonCoherent', the ul-FullPowerTransmission can be configured with full-power or full-power mode 3.

• - If full power is configured (mode 0), the power scaling factor "s" is 1.
• - If full power mode 3 is configured (mode 3):
  • ◯ The UE could report TPMIs that support full power operation. TPMI reporting is based on non-coherent or partialAndNonCoherent code book subsets to reduce overhead. For a fully coherent UE with 2 Tx, it should report TPMIs that support full power transmission within the non-coherent codebook subset. For a fully coherent UE with 4 Tx, it should report TPMIs that support transmission at full power within the subset “partialAndNonCoherent codebook”. The power scaling factor "s" should be 1 for these reported TPMIs. For the TPMIs within the codebook subset “fullAndPartialAndNonCoherent” with the exception of the reported TPMIs, the power scaling factor is the ratio of the number of antenna ports with PUSCH power not equal to zero divided by the number of SRS antenna ports of the SRS resource actually used.
  • ◯ The UE could not report any TPMIs. In this case, the power scaling factor for all TPMIs within the codebook subset "fullAndPartialAndNonCoherent" is the ratio of the number of antenna ports with PUSCH power not equal to zero divided by the number of SRS antenna ports of the SRS resource actually used.

Systems and implementations.

7-9 illustrate various systems, devices, and components that can implement aspects of the disclosed aspects.

7th illustrates a network 700 according to various aspects. The network 700 can be operated in a manner that complies with the technical specifications of 3GPP for LTE or 5G / NR systems with long-term development. However, the example aspects are not limited in this regard, and the aspects described can apply to other networks that benefit from the principles described here, such as future 3GPP systems or the like.

The network 700 can a UE 702 which may include any mobile or non-mobile computing device designed to be connected to a radio access network (RAN) 704 communicate over an over-the-air connection. The UE 702 can be a smartphone, a tablet computer, a portable computing device, a desktop computer, a laptop Computer, an infotainment device in the vehicle, an entertainment device in the vehicle, an instrument cluster, a head-up display device, an onboard diagnostic device, a mobile dash top device, a mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / Motor control module, embedded system, sensor, microcontroller, control unit, motor management system, networked device, machine-like communication device, machine-to-machine (M2M) or device-to-device (D2D) device, Internet-of-Things (IoT) device etc., but is not limited to

In some aspects, the network can 700 have a plurality of UEs that are directly connected to one another via a sidelink interface. The UEs can be M2M / D2D devices that communicate via physical sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink downlink channel (PSDCH), physical sidelink - Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Feedback Channel (PSFCH), etc.

In some aspects, the UE 702 additionally communicate with an access point (AP) 706 via an over-the-air connection. The AP 706 can manage a connection. The AP 606 can manage a connection that can serve to take part / all network traffic from the RAN 704 to relieve. The connection between the UE 702 and the AP 706 can conform to any Institute of Electrical and Electronics Engineers (IEEE 802.11) protocol, with the AP 706 can be a Wi-Fi® router. In some aspects, the UE 702 , the RAN 704 and the AP 706 use a cellular WLAN aggregation (e.g. LTE-WLAN-Aggregation (LWA) / LTE / WLAN Radio Level Integration with IPsec Tunnel (LWIP)). With cellular WLAN aggregation, the UE 702 from the RAN 704 configured to use both cellular and WiFi resources.

The RAN 704 can have one or more access nodes, e.g. the access network (AN) 708 . AT 708 can use air interface protocols for the UE 702 End by using access layer protocols including Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Message Authentication Code (MAC) and Layer-1 (L1) logs. In this way, the AN 708 Data / voice connectivity between the channel number (CN) 720 and the UE 702 enable. In some aspects, the AN 708 be implemented in a discrete device or as one or more software units running on server computers, for example as part of a virtual network called a cloud radio access network (CRAN) or a virtual baseband unit pool can. The AN 708 Can be used as a base station (BS), next-generation NodeB (gNB), RAN node, evolved node B (eNB), ng-evolved NodeB (ng-eNB), NodeB, Road Side Unit (RSU), transceiver point (TRxP), Broadcast reception point (TRP), etc. The AN 708 may be a macro cell base station or a low power base station to provide femtocells, picocells or similar cells that have smaller coverage areas, lower user capacity or higher bandwidth compared to macro cells.

In aspects in which the RAN 704 has a plurality of ANs, these can be accessed via an X2 interface (if the RAN 704 is an LTE-RAN) or an Xn interface (if the RAN 704 a 5G-RAN) must be coupled to one another. The X2 / Xn interfaces, which in some aspects can be subdivided into control / user plane interfaces, enable the ANs to communicate information relating to handover, data / context transfer, mobility, load management, interference coordination, etc.

The ANs of the RAN 704 can each manage one or more cells, cell groups, component carriers, etc. to the UE 702 provide an air interface for network access. The UE 702 may be connected to a plurality of cells simultaneously from the same or different ANs of the RAN 704 to be provided. For example, the UE 702 and the RAN 704 Use carrier aggregation to provide the UE 702 enable connection to a plurality of component carriers, each corresponding to a P-cell or Scell. In dual connectivity scenarios, a first AN can be a master node providing a master cell group (MCG) and a second AN can be a secondary node providing a secondary cell group (SCG). The first / second ANs can be any combination of eNB, gNB, ng-eNB, etc.

The RAN 704 can provide the air interface via a licensed spectrum or an unlicensed spectrum. For operation in the unlicensed spectrum, the nodes can use license-supported access (LAA), extended LAA (eLAA) and / or further improved LAA (feLAA) mechanisms based on Carrier Aggregation (CA) technology with PCells / Scells. Before accessing the unlicensed spectrum, the nodes can perform a media / carrier detection, for example based on a listen-before-talk (LBT) protocol.

According to V2X scenarios (Vehicle to Everything), the UE 702 or AN 708 be or act as an RSU, which can refer to any traffic infrastructure unit used for V2X communication. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE can be referred to as a “UE-Type RSU”; an eNB can be referred to as "eNB type RSU"; a gNB can be referred to as "gNB type RSU"; and the same. In one example, an RSU is a computing device that is coupled to a radio frequency circuit located on the roadside that provides connectivity to the UEs of passing vehicles. The RSU may also have internal data storage circuitry to store intersection geometry, traffic statistics, media, and applications / software for capturing and controlling ongoing vehicle and pedestrian traffic. The RSU can provide the very low latency communication required for high speed events such as accident avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU can provide other cellular / WLAN communication services. The components of the RSU can be housed in a weatherproof housing suitable for outdoor installation and can have a network interface control unit to provide a wired connection (e.g. Ethernet) to a traffic light controller or a backhaul network.

In some aspects, the RAN 704 an LTE-RAN 710 with eNBs, e.g. B. eNB 712 , be. The LTE-RAN 710 can provide an LTE air interface with the following features: subcarrier spacing (SCS) of 15 kHz; Control Plane (CP) waveform - orthogonal frequency division multiplexing (OFDM) for the downlink (DL) and single carrier frequency division multiplexing (SC-FDMA) waveform for the uplink (UL); Turbo codes for data and tail-biting convolutional codes (TBCC) for control; etc. The LTE air interface can refer to the Channel State Information (CSI) reference signal (RS) for CSI acquisition and beam management, the PDSCH / PDCCH demodulation reference signal (DMRS) for PDSCH / PDCCH demodulation and the Base cell reference signal (CRS) for cell search and initial acquisition, channel quality measurements and channel estimation for coherent demodulation / detection at the UE. The LTE air interface can work on bands below 6 GHz.

In some aspects, the RAN 704 a next generation (NG) RAN 714 with gNBs, for example gNB 716 , or ng-eNBs, for example ng-eNB 718 , be. The gNB 716 can connect to 5G-capable UEs via a 5G-NR interface. The gNB 716 can connect to a 5G core via an NG interface, which can have an N2 interface or an N3 interface. The ng-eNB 718 can also connect to the 5G core via an NG interface, but can connect to a UE via an LTE air interface. The gNB 716 and the ng-eNB 718 can connect to each other via an Xn interface.

In some aspects, the NG interface can be split into two parts, an NG-U interface (NG-U), which carries traffic data between the nodes of the NG-RAN 714 and a user plane function (UPF) 748 (e.g. N3 interface) transmits, and an NG-C interface (NG-C), which is a signaling interface between the nodes of the NG-RAN 714 and an access and mobility management function (AMF) 744 (e.g. N2 interface) is.

The NG-RAN 714 can provide a 5G NR air interface with the following features: variable SCS; CP-OFDM for DL, CP-OFDM and Discrete Fourier Transform (Discrete Fourier Transform) spread OFDM (DFT-s-OFDM) DFT-s-OFDM for UL; Polar, repetition, simplex and reed-Muller codes for control and low-density parity check (LDPC) for data. The 5G-NR air interface can be based on CSI-RS, physical downlink shared channel (PDSCH) / physical downlink control channel (PDCCH) demodulation reference signal (DMRS) similar to the LTE air interface . The 5G-NR air interface must not use CRS, but can use Physical Broadcast Channel (PBCH) DMRS for PBCH demodulation, phase tracking reference signal (PTRS) for phase tracking for PDSCH and tracking reference signal for time tracking. The 5G NR air interface can operate on FR1 bands, which have bands below 6 GHz, or FR2 bands, which have bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may comprise a synchronization signal block (SSB) which is a portion of a downlink resource grid that comprises the primary synchronization signal / sideband synchronization signal / physical broadcast channel (PSS / SSS / PBCH).

In some aspects, the 5G NR air interface can use parts of bandwidth (BWP) for different purposes. For example, BWP can be used to dynamically adjust the SCS. For example, the UE 702 be set up with several BWPs, each BWP configuration having a different SCS. If the UE 702 a BWP change is indicated, the SCS of the transfer is also changed. Another use case example for BWP relates to energy saving. In particular, several BWPs can be used for the UE 702 be set up with a different number of frequency resources (e.g. physical resource blocks (PRBs)) to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with a low traffic load and at the same time enables power savings at the UE 702 and in some cases with the gNB 716 . A BWP that contains a larger number of PRBs can be used for scenarios with a higher traffic load.

The RAN 704 is communicative with the CN 720 coupled, which has network elements, the various functions to support data and telecommunication services for customers / subscribers (e.g. users of the UE 702 ) provide. The components of the CN 720 can be implemented in a physical node or in separate physical nodes. In some aspects, Network Function Visualization (NFV) can be used to identify some or all of the functions performed by the network elements of the CN 720 provided to virtualize on physical computing / storage resources in servers, switches, etc. A logical instantiation of the CN 720 can be referred to as a network slice, and a logical instantiation of part of the CN 720 can be referred to as a network sub-slice.

In some aspects, the CN 720 an LTE CN 722 which can also be referred to as evolved packet control (EPC). The LTE CN 722 can a Mobility Management Entity (MME) 724 , a serving gateway (SGW or S-GW) 726 , a Serving GPRS Support Node (SGSN) 728 , a Home Subscriber Server (HSS) 730 , a Packet Data Network (PDN) Gateway (PGW or P-GW) 732 and a Policy Control and Charging Rules Function (PCRF) 734 that are coupled to one another via interfaces (or "reference points"), as shown. The functions of the elements of the LTE CN 722 can be briefly introduced as follows.

The MME 724 can implement mobility management functions to a current location of the UE 702 track to enable paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

The SGW 726 can terminate an S1 interface to the RAN and data packets between the RAN and the LTE CN 722 forward onto. The SGW 726 can be a local mobility anchor point for inter-RAN node handover and can also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, billing, and some policy enforcement.

The Serving General Packet Radio Service (GPRS) support node 728 can find a location of the UE 702 track and perform security functions and access control. In addition, the SGSN 728 perform inter-EPC node signaling for mobility between different RAT networks (Radio Access Technology); PDN and S-GW selection according to MME 724 ; MME selection for handover; etc. The S3 reference point between the MME 724 and the SGSN 728 can enable the exchange of user and bearer information for inter-3GPP access network mobility in the idle / active state.

The HSS 730 may have a database for network users, including subscription-related information to aid in the handling of communication sessions by the network entities. The HSS 730 can provide support for routing / roaming, authentication, authorization, name / addressing resolution, location dependencies, etc. An S6a reference point between the HSS 730 and the MME 724 can transfer subscription and authentication data for authentication / authorization of user access to the LTE CN 720 enable.

The PGW 732 can be an SGi interface to a data network (DN) 736 complete an application / content server 738 may have. The PGW 732 can send data packets between the LTE CN 722 and the data network 736 forward onto. The PGW 732 can with the SGW 726 be coupled via an S5 reference point in order to facilitate tunneling at the user level and tunnel management. The PGW 732 may also have a policy enforcement and charge data collection node (eg, the Policy and Charging Enforcement Function (PCEF)). In addition, the SGi reference point between the PGW 732 and the data network 736 an operator-external public, a private PDN or an operator-internal packet data network, e.g. for the provision of international mobile subscriber identity services (IMS). The PGW 732 can with a PCRF 734 be coupled via a Gx reference point.

The PCRF 734 is the element of policy and charge control of the LTE CN 722 . The PCRF 734 can be communicative with the app / content server 738 be coupled to determine appropriate quality of service (QoS) and charging parameters for service flows. The PCRF 732 can provide associated rules in a PCEF (via the Gx reference point) with suitable TFT and QCI.

In some aspects, the CN 720 a 5G core network (5GC) 740 be. The 5GC 740 an Authentication Server Function (AUSF) 742 , AMF 744 , Session Management Function (SMF) 746 , UPF 748 , Network Slice Selection Function (NSSF) 750 , Network Exposure Function (NEF) 752 , Network Repository Function (NRF) 754 , Policy Control Function (PCF) 756 , Unified Data Management (UDM) 758 and application function (AF) 760 that are coupled to one another via interfaces (or "reference points") as shown. The functions of the elements of the 5GC 740 can be briefly introduced as follows.

The AUSF 742 can provide data for the authentication of the UE 702 store and process authentication-related functions. The AUSF 742 can enable a common authentication framework for different types of access. In addition to communicating with other elements of the 5GC 740 Via reference points, as shown, the AUSF 742 have a Nausf service based interface.

The AMF 744 can do other functions of the 5GC 740 allow with the UE 702 and the RAN 704 to communicate and notify of mobility events related to the UE 702 to subscribe. The AMF 744 can be used for registration management (e.g. for the registration of the UE 702 ), connection management, availability management, mobility management, lawful interception of AMF-related events and access authentication and authorization. The AMF 744 can transport for session management messages (SM) between the UE 702 and the session management function (SMF) 746 and act as a transparent proxy for routing SM messages. AMF 744 can also provide transport for SMS (Short Message Service) messages between the UE 702 and an SMS function (SMSF). AMF 744 can with the AUSF 742 and the UE 702 interact to perform various security anchor and context management functions. In addition, AMF 744 be a termination point of a RAN-CP interface, which is an N2 reference point between the RAN 704 and the AMF 744 can have or be; and the AMF 744 can be a termination point of the NAS ( N1 ) Signaling and performing NAS encryption and integrity protection. The AMF 744 can also do NAS signaling with the UE 702 via an N3 Internetworking Function (IWF) interface.

The SMF 746 can be responsible for SM (e.g. session setup, tunnel management between UPF 748 and on 708 ); Assignment and management of UE IP addresses (including optional authorization); Selection and control of user levels (User Plane - UP) function; Configure traffic control on the UPF 748 to get traffic to the right destination; Terminating interfaces towards policy control functions; Control parts of policy enforcement, billing and QoS; legally compliant interception (for SM events and the interface to the LI system); Termination of SM parts of Non-Access Stratum (NAS) messages; Downlink data notification; Initiation of AN-specific SM information that is sent via AMF 744 via N2 to AN 708 be sent; and determining the session and service continuity mode (SSC) of a session. SM may refer to the management of a Protocol Data Unit (PDU) session, and a PDU session or "session" may refer to a PDU link service which enables the exchange of PDUs between the UE 702 and the data network 736 provides or enables.

The UPF 748 Can be used as an anchor point for intra-RAT and inter-RAT mobility, as an external PDU session connection point to the data network 736 and serve as a branch point to support multi-homed PDU sessions. The UPF 748 can also perform packet routing and forwarding, perform packet inspection, enforce the part of the policy rules for the user level, intercept packets lawfully (UP collection), create traffic usage reports, perform QoS handling for a user level (e.g. packet filtering, gating, UL / DL rate enforcement) ), Perform uplink traffic checking (e.g. SDF-to-QoS flow mapping), perform packet marking on the transport level in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 748 may have an uplink classifier to support the routing of traffic flows to a data network.

The NSSF 750 can select a set of network slice instances that the UE 702 serve. The NSSF 750 can also determine allowed network slice selection assistance information (NSSAI) and the association with the subscribed individual NSSAIs (S-NSSAI), if necessary. The NSSF 750 can also determine the AMF rate required to operate the UE 702 to be used, or a list of candidate AMFs based on appropriate configuration and possibly by querying the NRF 754 . The selection of a set of network slice instances for the UE 702 can from the AMF 744 , where the UE 702 is registered by interacting with the NSSF 750 triggered, which can lead to a change in the AMF. The NSSF 750 can with the AMF 744 interact via an N22 reference point; and can communicate with another NSSF on a visited network through an N31 reference point (not shown). In addition, the NSSF 750 have an Nnssf service based interface.

The NEF 752 can services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g. AF 760 ), Edge computing or fog computing systems etc. securely deploy. In such aspects, the NEF 752 authenticate, authorize or throttle the AFs. The NEF 752 can also provide information related to the AF 760 and translate information exchanged with internal network functions. For example, the NEF 752 Translate between an AF service identifier and internal 5GC information. The NEF 752 can also receive information from other NFs based on the exposed capabilities of other NFs. This information can be found in the NEF 752 be stored as structured data or in a data-storing NF using standardized interfaces. The stored information can then be used by the NEF 752 passed on to other NFs and AFs or used for other purposes, such as analysis. In addition, the NEF 752 have an Nnef service based interface.

The NRF 754 can support service discovery functions, receive NF discovery requests from NF instances and provide the information of the discovered NF instances to the NF instances. The NRF 754 also manages information about available NF instances and their supported services. As used herein, the terms “instantiating”, “instantiating” and the like can relate to the creation of an instance, and an “instance” can relate to a specific occurrence of an object that can occur, for example, during the execution of program code. In addition, the NRF 754 have the nnrf service based interface.

The PCF 756 can provide policy rules to the functions of the control plane to enforce them, and can also support a unified policy framework to control network behavior. The PCF 756 can also implement a front end to access subscription information necessary for policy decisions in the Unified Data Repository (UDR) of Unified Data Management (UDM) 758 are relevant. In addition to communicating with functions via reference points, as shown, the PCF 756 an npcf service based interface.

The UDM 758 can manage subscription-related information to aid in the handling of communication sessions by the network entities and subscription data of the UE 702 to save. For example, subscription data can be shared between the UDM 758 and the AMF 744 communicated. The UDM 758 can have two parts, an application front end and a UDR. The UDR can store subscription data and policy data for the UDM 758 and the PCF 756 and / or structured data for exposure and application data (including PFDs for application discovery, application requirement information for multiple UEs 702 ) for the NEF 752 to save. The Nudr service-based interface can be used by the UDR 221 issued to the UDM 758 , the PCF 756 and the NEF 752 enable access to a specific set of stored data as well as reading, updating (e.g. adding, changing), deleting and subscribing to notifications of relevant data changes in the UDR. The UDM may have a UDM VU that is responsible for credential processing, site management, subscription management, and so on. Several different front ends can serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and carries out the processing of authentication data, the handling of the user identification, the access authorization, the management of the registration / mobility and the subscription management. In addition to communicating with other NFs via reference points, as shown, the UDM 758 have the nudm service based interface.

The AF 760 can provide application impact on traffic routing, provide access to NEF, and interact with the policy framework to control policies.

In some aspects, the 5GC 740 Enable edge computing by providing services of the Operator / third party so that they are geographically close to a point where the UE 702 connected to the network. This can reduce latency and load on the network. To provide edge computing implementations, the 5GC 740 a UPF 748 near the UE 702 and select a traffic control from the UPF 748 to the data network 736 Carry out via the N6 interface. This can be based on the subscription data of the UE, the location of the UE and information provided by the AF 760 are provided. In this way, the AF 760 Influence the UPF (re-) selection and the traffic routing. When the AF 760 is viewed as a trustworthy entity, the network operator of the AF 760 allow you to interact directly with relevant NFs. In addition, the AF 760 have a Naf service based interface.

The data network 736 can represent various network operator services, Internet access, or third-party services that can be provided by one or more servers, including, for example, application / content servers 738 .

8th schematically illustrates a wireless network 800 according to various aspects. The wireless network 800 can a UE 802 that is in wireless communication with an AN 804 stands. The UE 802 and the AN 804 may be similar and substantially interchangeable with like components described elsewhere herein.

The UE 802 can through the connection 806 with the AN 804 be communicatively coupled. The connection 806 is shown as an air interface to enable communicative coupling and can be consistent with cellular communication protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 802 can be a host platform 808 having that with a modem platform 810 is coupled. The host platform 808 can be an application processing circuit 812 having that with a protocol processing circuit 814 the fashion platform 810 can be coupled. The application processing circuit 812 can have different applications for the UE 802 execute, generate / sink application data. The application processing circuit 812 can also implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations can have transport (eg User Datagram Protocol (UDP)) and Internet (eg Internet Protocol (IP)) operations

The protocol processing circuit 814 may implement one or more of the layer operations to transmit or receive data over the link 806 to facilitate. The one from the protocol processing circuit 814 implemented layer operations can have, for example, MAC, RLC, PDCP, RRC and NAS operations.

The fashion platform 810 can also have a digital baseband circuit 816 that can implement one or more layer operations that are “below” layer operations that are performed by the protocol processing circuit 814 run on a network protocol stack. These operations can include, for example, physical layer (PHY) operations, including one or more hybrid automatic repeat request (HARQ) and acknowledgment functions (ACK), scrambling / descrambling, encoding / decoding, layer mapping / de-mapping, modulation symbol mapping , Determination of the received symbols / bit metrics, precoding / decoding of multi-antenna connections, which can have one or more of the following functions: space-time, space-frequency or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals and other related functions.

The fashion platform 810 can also have a transmission circuit 818 , a receiving circuit 820 , an RF circuit 822 and an RF front end (RFFE) 824 have one or more antenna fields 826 may contain or be associated with them. In short, the transmission circuit can 818 a digital-to-analog converter, a mixer, intermediate frequency components, etc. The receiving circuit 820 can have an analog-to-digital converter, mixer, IF components, etc.; the RF circuit 822 may include a low noise amplifier, a power amplifier, power tracking components, etc .; the RFFE 824 can have filters (e.g. surface / bulk acoustic wave filters), switches, antenna tuners, beam shaping components (e.g. phase array antenna components), etc. The selection and arrangement of the components of the transmission circuit 818 , the receiving circuit 820 , the RF circuit 822 , the RFFE 824 and the antenna panels 826 (commonly referred to as "transmit / receive components") can be specific to the details of a particular implementation, such as whether the communication is time division multiplex (TDM) or frequency division multiplex (FDM), mmWave or sub-6 GHz frequencies , etc. In some aspects, the transmit / receive components can be in multiple parallel transmit / receive chains can be arranged in the same or in different chips / modules, etc.

In some aspects, the protocol processing circuit 814 have one or more instances of control circuits (not shown) in order to provide control functions for the transmitting / receiving components.

UE reception can be through and via the antenna fields 826 who have favourited RFFE 824 who have favourited RF circuit 822 , the receiving circuit 820 who have favourited digital baseband circuit 816 and the protocol processing circuit 814 getting produced. In some aspects the antenna fields 826 a transfer from the contractor 804 by receive beamforming of signals received from a plurality of antenna / antenna elements of the one or more antenna arrays 826 be received.

A UE transmission can be to and from the protocol processing circuit 814 who have favourited digital baseband circuit 816 , the transmission circuit 818 who have favourited RF circuit 822 , the RFFE 824 and the antenna fields 826 being constructed. In some aspects, the transmission components of the UE 804 apply a spatial filter to the data to be transmitted in order to form a transmit beam that is emitted by the antenna elements of the antenna arrays 826 is sent out.

Similar to the UE 802 can do that 804 a host platform 828 having that with a modem platform 830 is coupled. The host platform 828 can be an application processing circuit 832 having that with a circuit for protocol processing 834 the fashion platform 830 is coupled. The modem platform may also have a digital baseband circuit 836 , a transmission circuit 838 , a receiving circuit 840 , an RF circuit 842 , an RFFE circuit 844 and antenna fields 846 exhibit. The components of the contractor 804 can be similar and essentially interchangeable with components of the UE of the same name 802 be. In addition to performing data transmission / reception as described above, the components of the AN 808 perform various logical functions, including functions of the radio network control unit (RNC), such as radio bearer management, dynamic management of radio resources in the uplink and downlink direction and the planning of data packets.

9 FIG. 13 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (eg, a non-transitory machine-readable storage medium) and performing one or more of the methods discussed herein, in accordance with some example aspects. In particular shows 9 a schematic representation of hardware resources 900 that have one or more processors (or processor cores) 910 , one or more storage / storage devices 920 and one or more communication resources 930 each of which has a bus 940 or other interface circuits can be communicatively coupled. For aspects where node virtualization (e.g. NFV) is used, a hypervisor 902 be executed in order to provide an execution environment for one or more network slices / sub-slices to the hardware resources 900 to use.

The processors 910 can eg use a processor 912 and a processor 914 exhibit. The processors 910 For example, a central processing unit (CPU), a RISC processor (Reduced Instruction Set Computing), a CISC processor (Complex Instruction Set Computing), a graphics processing unit (GPU), a digital signal processor ( DSP), such as a baseband processor, an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination exhibit of it.

The storage / storage devices 920 may include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 920 can have any type of volatile, non-volatile or semi-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, etc. but not limited to that.

The communication resources 930 can control units, components or other suitable devices for communication with one or more peripheral devices 904 or one or more databases 906 or other network elements over a network 908 exhibit. The communication resources 930 can, for example, have wired communication components (e.g. for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components and other communication components.

The instructions 950 can be software, a program, an application, an applet, an app or other executable code to at least one of the processors 910 cause one or more of the methods discussed here to be performed. The instructions 950 can be fully or partially in at least one of the processors 910 (e.g. in the processor's cache memory), in the storage / storage devices 920 or in a suitable combination thereof. In addition, any part of the instructions can 950 from any combination of the peripheral devices 904 or the databases 906 to the hardware resources 900 be transmitted. The memory of the processors are accordingly 910 who have favourited Storage / Storage Devices 920 who have favourited Peripherals 904 and the databases 906 Examples of computer readable and machine readable media.

Example procedures.

In some aspects, the electronic device (s), network (s), system (s), chip (s) or component (s), or parts or implementations thereof the 7-9 or any other figure herein may be adapted to perform one or more processes, techniques or methods as described herein, or parts thereof. Such a process is in 10 shown. The process 1000 the 10 can be carried out by a UE or part of it.

For example, the process can 1000 comprise at 1001 receiving a codebook indication to use a full coherence codebook for uplink transmissions, the full coherence codebook corresponding to a set of precoders for uplink transmissions for UEs that support full coherence of transmit chains and / or antenna ports.

at 1002 the process may further include receiving a power mode indication to indicate a transmit power mode to use for the uplink transmissions.

11 illustrates another process 1100 according to various aspects. In some aspects, the process of 11 be carried out by a gNB or part of it.

For example, the process 1100 at 1101 encoding a codebook display for transmission to a UE to use a full coherence codebook for uplink transmissions, the full coherence codebook corresponding to a set of precoders for uplink transmissions for UEs, the full coherence of transmit chains and / or antenna ports support.

at 1102 For transmission to the UE, the method may further encode a power mode indicator to indicate a transmit power mode to be used for the uplink transmissions.

In one or more aspects, at least one of the components illustrated in one or more of the preceding figures can be set up to carry out one or more operations, techniques, processes and / or methods in accordance with the following example section. For example, as described above in connection with one or more of the preceding figures, the baseband circuit can be set up in such a way that it operates in accordance with one or more of the examples listed below. As a further example, the circuit associated with a UE, a base station, a network element, etc., as described above in accordance with one or more of the preceding figures, can be set up in such a way that it operates in accordance with one or more of the examples listed below in the example section.

EXAMPLES

Example 1 may have the UE where it may report its ability to be coherent, including fully coherent, partially coherent, and incoherent. The UE may also exhibit its full power uplink operation capability, including Mode 0, Mode 1, and Mode 2.

Example 2 may have the gNode B, where it can configure the UE with a codebook subset via RRC signaling, including fullAndPartialAndNonCoherent, partialAndNonCoherent and nonCoherent. The gNB can also configure the full power mode of operation via RRC signaling, which includes mode 0, mode 1 and mode 2.

Example 3 may have the method of Example 1 and Example 2 or another example herein, wherein when the gNB sets up fullAndPartialAndNonCoherent codebook subset, the UE can also be set up with ul-FullPowerTransmission to enable full power transmission in the uplink.

Example 4 may include the method of Example 3 or another example herein, where when mode 0 is established, the power scaling factor is always 1. Alternatively, the power scaling factor is the ratio of the number of antenna ports with non-zero PUSCH power to the maximum number of SRS antenna ports that the UE can support.

Example 5 may include the method of Example 3 or any other example herein, wherein if fullAndPartialAndNonCoherent codebook subset is set up, ul-FullPowerTransmission can be configured as mode 0 for the UE.

Example 6 may include the method of Example 3, or another example herein, wherein when Mode 1 is established, the UE should use fullAndPartialAndNonCoherent 'codebook subset for Mode 1 operation. And the 'fullAndPartialAndNonCoherent' codebook subset should be added to Mode 1. The power scaling factor 's' is the ratio of the number of antenna ports with PUSCH power not equal to zero to the maximum number of SRS antenna ports that the UE can support.

Example 7 may include the method of Example 3, or another example herein, wherein when Mode 2 is established, the UE does not report any TPMIs that support full power. For all TPMIs, the power scaling factor is the ratio of the number of antenna ports with non-zero PUSCH power to the maximum number of SRS antenna ports that the UE can support.

Example 8 may include the method of Example 3, or another example herein, wherein when Mode 2 is established the UE is still reporting TPMIs that support full power. And the TPMI reporting is based on non-coherent or partialAndNonCoherent code book subsets. For a fully coherent UE with 2 Tx it should report TPMIs that support transmission at full power within the non-coherent codebook subset. For a fully coherent UE with 4 Tx, it should report TPMIs that support transmission at full power within the subset “partialAndNonCoherent codebook”. For these reported TPMIs, the power scaling factor should be 1. For those TPMIs within the codebook subset "fullAndPartialAndNonCoherent", with the exception of the reported ones, the power scaling factor is the ratio of the number of antenna ports with PUSCH power not equal to zero divided by the number of SRS antenna ports of the SRS resource actually used.

Example 9 may include the method of Example 3, or another example herein, wherein when mode 2 is established, the UE reports TPMIs that support full performance within the codebook subset “fullAndPartialAndNonCoherent”. For the reported TPMIs, the power scaling factor 's' should be 1. For the unreported TPMIs, the power scaling factor is the ratio of the number of antenna ports with PUSCH power not equal to zero divided by the number of SRS antenna ports of the SRS resource actually used.

Example 10 may include the method of Example 3 or any other example herein, wherein when mode 2 is configured, antenna virtualization is not allowed. While in another option the antenna virtualization could be allowed.

Example 11 may include the method of Example 1 and Example 2 or another example herein wherein a separate full power mode of operation could be introduced for fully coherent UE, e.g. full power mode 3. The parameter ul-FullPowerTransmission can have a value can be configured from {full power mode, full power mode 1, full power mode 2, full power mode 3}. For the fully coherent UE, if the codebook subset is configured as 'fullAndPartialAndNonCoherent', the ul-FullPowerTransmission can be configured with full-power or full-power mode 3.

Example 12 may include the method of Example 11, or another example herein, wherein when full power is configured (mode 0) the power scaling factor "s" is 1.

Example 13 may include the method of Example 11, or another example herein, wherein if full power mode 3 is established (mode 3), the UE could report TPMIs that support full power operation. The TPMI reporting is based on non-coherent or partialAndNonCoherent code book subsets. For a fully coherent UE with 2 Tx it should report TPMIs that support full power transmission within the non-coherent codebook subset. For a fully coherent UE with 4 Tx, it should report TPMIs that support transmission at full power within the subset “partialAndNonCoherent codebook”. The power scaling factor "s" should be 1 for these reported TPMIs. For those TPMIs within the codebook subset 'fullAndPartialAndNonCoherent', with the exception of the reported ones, the power scaling factor is the ratio of the number of antenna ports with PUSCH power not equal to zero divided by the number of SRS antenna ports of the SRS resource actually used.

Example 14 may include the method of Example 11 or another example herein, with full power mode 3 configured (mode 3), if the UE is not reporting any TPMIs, for all TPMIs within the 'fullAndPartialAndNonCoherent' codebook subset, where the power scaling factor is the ratio of the number of antenna ports with non-zero PUSCH power divided by the number of SRS antenna ports of the SRS resource actually used.

Example 15 may include a method of a UE, the method comprising: receiving a codebook indication to use a full coherence codebook for uplink transmissions, the full coherence codebook corresponding to a set of precoders for uplink transmissions for UEs, the full coherence support of transmission chains and / or antenna ports; and receiving a power mode indication to indicate a transmit power mode to be used for the uplink transmissions.

Example 16 may include the method of Example 15, or another example herein, wherein the full coherence codebook further includes precoders used for UEs that support partial coherence or no coherence.

Example 17 may include the method of Examples 15-16, or another example herein, wherein the transmit power mode is one of Mode 0, Mode 1, or Mode 2 as defined herein.

Example 18 may include the method of Example 15-17, further comprising applying a power scaling factor to the uplink transmissions based on the specified transmit power mode.

Example 19 may include the method of Example 18 or another example herein, where the transmit power mode is mode 0 and the power scaling factor is a ratio of a number of antenna ports with non-zero PUSCH power over a number of SRS antenna ports supported by the UE will.

Example 20 may include the method of Example 18 or another example herein, where the transmit power mode is mode 0 and the power scaling factor is 1.

Example 21 may include the method of Example 18 or another example herein, where the transmit power mode is mode 1 and the power scaling factor is a ratio of a number of antenna ports with non-zero PUSCH power over a number of SRS antenna ports supported by the UE will.

Example 22 may include the method of Example 15-21 or another example herein, where the transmit power mode is mode 2.

Example 23 may include the method of Example 22, or any other example herein, wherein the UE does not report TPMIs.

Example 24 may include the method of Example 22-23, or any other example herein, further including applying a power scaling factor to the uplink transmissions associated with all TPMIs that is a ratio of a number of antenna ports with non-zero PUSCH power via a number of SRS antenna ports supported by the UE.

Example 25 may include the method of Examples 22-24 or any other example herein, further comprising: generating TPMI reports based on a non-coherent code book or a partial and non-coherent code book; and encoding the generated TPMI reports for transmission.

Example 26 may include the method of Example 25, or another example herein, wherein the UE has two transmission chains, and wherein the TPMI reports are generated based on the non-coherent codebook.

Example 27 may include the method of Example 25-26 or another example herein, where the UE has four transmission chains, and where the TPMI reports are generated based on the partial and non-coherent codebook.

Example 28 may include the method of Example 25-27 or any other example herein, further applying a first power scaling factor to upstream transmissions associated with TPMIs of the generated TPMI reports, and applying a second power scaling factor to upstream transmissions associated with TPMIs of the There are associated full coherence codebooks for which a TPMI report has not been generated.

Example 29 may include the method of Example 28 or another example herein, wherein the first power scaling factor is 1 and / or the second scaling factor is a ratio of a number of antenna ports with non-zero PUSCH power divided by a number of SRS antenna ports of SRS used -Resources is.

Example 30 may include the method of Examples 22-24 or any other example herein, further comprising: generating TPMI reports for TPMIs of the full coherence codebook that support full performance; and encoding the generated TPMI reports for transmission.

Example 31 may include the method of Example 30 or any other example herein, further comprising: applying a first power scaling factor to uplink transmissions associated with TPMIs of the generated TPMI reports, and applying a second power scaling factor to uplink transmissions associated with TPMIs of the full coherence codebook for which no TPMI report was generated.

Example 32 may include the method of Example 31 or another example herein, wherein the first power scaling factor is 1 and / or the second scaling factor is a ratio of a number of antenna ports with non-zero PUSCH power divided by a number of SRS antenna ports of used SRS resources is.

Example 33 may include the method of Examples 22-32 or any other example herein, further applying antenna virtualization to one or more of the UL transmissions.

Example 34 may include the method of Examples 15-16 or another example herein, where the transmit power mode is Mode 3 as defined herein.

Example 35 may include the method of Example 34, or another example herein, wherein the UE does not report TPMIs for Mode 3.

Example 36 may include the method of Example 34-35, or another example herein, further including applying a power scaling factor to the uplink transmissions associated with all TPMIs that has a ratio of a number of antenna ports with non-zero PUSCH power is a number of SRS antenna ports supported by the UE.

Example 37 may include the method of Example 34 or any other example herein, further comprising: generating TPMI reports based on a non-coherent code book or a partial and non-coherent code book; and encoding the generated TPMI reports for transmission.

Example 38 may include the method of Example 37 or another example herein, wherein the UE has two transmission chains, and wherein the TPMI reports are generated based on the non-coherent codebook.

Example 39 may include the method of Example 37-38 or another example herein, wherein the UE has four transmission chains, and wherein the TPMI reports are generated based on the partial and non-coherent codebook.

Example 40 may include the method of Example 37-39, or any other example described herein, further comprising applying a first power scaling factor to upstream transmissions associated with TPMIs of the generated TPMI reports and applying a second power scaling factor to upstream transmissions associated with TPMIs of the fully coherent codebook for which no TPMI report was generated.

Example 41 may include the method of Example 40 or another example herein, wherein the first power scaling factor is 1 and / or the second scaling factor is a ratio of a number of antenna ports with non-zero PUSCH power divided by a number of SRS antenna ports of SRS used -Resources is.

Example 42 may include a method of a gNB, the method comprising: encoding a codebook indication for transmission to a UE to use a full coherence codebook for uplink transmissions, the full coherence codebook being a set of precoders for uplink transmissions for UEs that support full coherence of transmission chains and / or antenna ports; and encoding a power mode indicator for transmission to the UE to indicate a transmit power mode to be used for the uplink transmissions.

Example 43 may include the method of Example 42, or any other example herein, wherein the full coherence codebook further includes precoders used for UEs that support partial coherence or no coherence.

Example 44 may include the method of Example 42-43, or another example herein, wherein the transmit power mode is one of Mode 0, Mode 1, or Mode 2 as defined herein.

Example 45 may include the method of Example 42-44, where the UE is to apply a power scaling factor to the uplink transmissions based on the specified transmit power mode.

Example 46 may include the method of Example 45, or another example herein, where the transmit power mode is mode 0 and the power scaling factor is a ratio of a number of antenna ports with non-zero PUSCH power over a number of SRS antenna ports different from the UE are supported.

Example 47 may include the method of Example 45, or another example herein, where the transmit power mode is mode 0 and the power scaling factor is 1.

Example 48 may include the method of Example 45, or another example herein, where the transmit power mode is mode 1 and the power scaling factor is a ratio of one Number of antenna ports with non-zero PUSCH power over a number of SRS antenna ports supported by the UE.

Example 49 may include the method of Examples 42-45, or another example herein, where the transmit power mode is Mode 2.

Example 50 may include the method of Example 49, or another example herein, wherein the UE does not report TPMIs for Mode 2.

Example 51 may include the method of Example 49-50, or another example herein, wherein the UE is to apply a power scaling factor to the uplink transmissions connected to all TPMIs that is a ratio of a number of antenna ports with PUSCH- Non-zero performance across a number of SRS antenna ports supported by the UE.

Example 52 may include the method of Example 49, 51, or any other example herein, further receiving TPMI reports based on a non-coherent code book or a partial and non-coherent code book.

Example 53 may include the method of Example 52 or another example herein, where the UE has two transmission chains, and where the TPMI reports are based on the non-coherent codebook.

Example 54 may include the method of Example 52-53 or another example herein, where the UE has four transmission chains and where the TPMI reports are based on the partial and non-coherent codebook.

Example 55 may include the method of Example 52-54, or any other example herein, further wherein the UE is to apply a first power scaling factor to uplink transmissions associated with TPMIs of the received TPMI reports and a second power scaling factor to uplink transmissions associated with TPMIs of the full coherence codebook for which no TPMI report has been received.

Example 56 may include the method of Example 55 or another example herein, wherein the first power scaling factor is 1 and / or the second scaling factor is a ratio of a number of antenna ports with non-zero PUSCH power divided by a number of SRS antenna ports with SRS used -Resources is.

Example 57 may include the method of Example 49, 51, or any other example herein, further comprising: receiving TPMI reports for TPMIs of the full coherence codebook that support full performance.

Example 58 may include the method of Example 57, or another example herein, wherein the UE should apply a first power scaling factor to uplink transmissions associated with TPMIs of the received TPMI reports and apply a second power scaling factor to uplink transmissions, associated with TPMIs of the full coherence codebook for which no TPMI report was received.

Example 59 may include the method of Example 58, or another example herein, wherein the first power scaling factor is 1 and / or the second scaling factor is a ratio of a number of antenna ports with non-zero PUSCH power divided by a number of SRS antenna ports used SRS resources is.

Example 60 may include the method of Example 49-59 or any other example herein, further receiving one or more of the UL transmissions with antenna virtualization.

Example 61 may include the method of Examples 42-43 or another example herein, where the transmit power mode is Mode 3 as defined herein.

Example 62 may include the method of Example 61, or another example herein, wherein the UE does not report TPMIs for Mode 3.

Example 63 may include the method of Example 61-62, or another example herein, further including applying a power scaling factor to the uplink transmissions associated with all TPMIs that has a ratio of a number of antenna ports with non-zero PUSCH power is a number of SRS antenna ports supported by the UE.

Example 64 may include the method of Example 61 or any other example herein, further comprising: receiving TPMI reports based on a non-coherent code book or a partial and non-coherent code book.

Example 65 may include the method of Example 64 or another example herein, where the UE has two transmission chains, and where the TPMI reports are based on the non-coherent codebook.

Example 66 may include the method of Example 64-65 or another example herein, where the UE has four transmission chains and where the TPMI reports are based on the partial and non-coherent codebook.

Example 67 may include the method of Example 64-66, or another example herein, wherein the UE is to apply a first power scaling factor to uplink transmissions associated with TPMIs of the received TPMI reports and to apply a second power scaling factor to uplink transmissions associated with TPMIs of the full coherence codebook for which no TPMI report was received.

Example 68 may include the method of Example 67 or another example herein, wherein the first power scaling factor is 1 and / or the second scaling factor is a ratio of a number of antenna ports with non-zero PUSCH power divided by a number of SRS antenna ports of SRS used -Resources is.

Example 69 may include apparatus that includes means for performing one or more elements of a method described in or related to any of Examples 1-68, or any other method or process described herein.

Example 70 may include one or more non-transitory computer-readable media containing instructions to cause an electronic device, when the instructions are executed by one or more processors of the electronic device, to perform one or more elements of a method described in any of Examples 1 -68, or any other method or process described herein.

Example 71 may include apparatus that includes logic, modules, or circuitry to carry out one or more elements of a method described in, or relating to, any of Examples 1-68, or any other method or any of the methods described herein different process.

Example 72 may include a method, technique, or process as described or related to any of Examples 1-68, or portions thereof.

Example 73 may include an apparatus comprising: one or more processors and one or more computer readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform the method to perform the technique or process as described in or associated with any of Examples 1-68, or any portion thereof.

Example 74 may include a signal as described in or associated with any of Examples 1-68, or portions thereof.

Example 75 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described or related to any of Examples 1-68, or portions thereof, or otherwise described in the present disclosure.

Example 76 may include a signal encoded with data as described or associated with any of Examples 1-68, or portions thereof, or otherwise described in the present disclosure.

Example 77 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described or related to any of Examples 1-68, or with sections or parts thereof, or as otherwise described in the present disclosure.

Example 78 may include an electromagnetic signal carrying computer-readable instructions, the execution of the computer-readable instructions by one or more processors serving to cause the one or more processors to use the method, techniques, or process according to any of Examples 1- 68 or parts thereof.

Example 79 may comprise a computer program containing instructions, the execution of the program by a processing element serving to cause the processing element to use the method, technique, or process as described in or related to any of Examples 1-68, or To carry out parts of it.

Example 80 may include a signal on a wireless network as shown and described herein.

Example 81 may include a method of communicating in a wireless network as illustrated and described herein.

Example 82 may include a system for providing wireless communication as shown and described herein.

Example 83 may include an apparatus for providing wireless communication as shown and described herein.

Each of the examples described above can be combined with any other example (or any combination of examples), unless expressly stated otherwise. The foregoing description of one or more implementations has been presented for purposes of illustration and description, but is not intended to be exhaustive or to limit the scope of the aspects to the precise form disclosed. Modifications and variations are possible in light of the above teachings or can be learned from practice of the various aspects.

Terminology.

For the purposes of this document, the following terms and definitions apply to the examples and aspects discussed here.

As used herein, the term “circuit” refers to, is part of, or comprises 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 component (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic component (PLD), a complex PLD (CPLD), a PLD with high Capacity (HCPLD), a structured ASIC or a programmable SoC), digital signal processors (DSPs) etc. that are set up to provide the functionality described. In some aspects, the circuit can execute one or more software or firmware programs to provide at least a portion of the functionality described. The term “circuit” can 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. According to these aspects, the combination of hardware elements and program code can be referred to as a certain type of circuit.

As used herein, the term “processor circuit” refers to a circuit that is or is capable of sequentially and automatically executing a series of arithmetic or logical operations or recording, storing and / or transmitting digital data Part of such. The processor circuit can have one or more processor cores for executing instructions and one or more memory structures for storing program and data information. The term "processor circuit" can refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-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. The processing circuit can have further hardware accelerators, which can be microprocessors, programmable processing devices or the like. The one or more hardware accelerators can e.g. B. computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuits” and / or “baseband circuits” can be viewed as synonymous with “processor circuits” and can be designated as such.

As used herein, the term “interface circuit” refers to a circuit that enables the exchange of information between two or more components or devices, is part of them, or has such a circuit. The term "interface circuit" can refer to one or more hardware interfaces, e.g. B. on buses, I / O interfaces, interfaces of peripheral components, network interface cards and / or the like.

As used herein, the term “user device” or “UE” refers to a device with radio communication capabilities and can describe a remote user of network resources on a communication network. The term "user device" or "UE" can be used as a synonym for client, mobile device, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable radio , reconfigurable mobile device, etc., and can be referred to as such. Additionally, the term “user device” or “UE” can include any type of wireless / wired device or any computing device that includes a wireless communication interface.

As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" can be used as a synonym for a networked computer, network hardware, network equipment, network node, router, switch, hub, bridge, radio network control unit, RAN device, RAN node, gateway, server, virtualized VNF, NFVI and / or the like can be considered and / or designated.

As used herein, the term "computer system" refers to any type of interconnected electronic device, computing device, or component thereof. In addition, the term “computer system” and / or “system” can refer to various components of a computer that are communicatively coupled to one another. In addition, the term “computer system” and / or “system” can refer to a plurality of computer devices and / or a plurality of computer systems that are communicatively coupled to one another and are set up to share computer and / or network resources.

As used herein, the term “device”, “computing device” or the like refers to a computing device or computer system with program code (e.g. software or firmware) that is specifically designed to provide a particular computer resource. A “virtual device” is a virtual machine image that is implemented by a hypervisor-equipped device that virtualizes or emulates a computing device, or is otherwise designed to provide a particular computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a particular device, such as a computer. B. Computing devices, mechanical devices, storage space, processor / CPU time, processor / CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input / output operations, ports or network sockets, channel / Link allocation, throughput, memory usage, storage, network, database and applications, workload units and / or the like. A “hardware resource” can refer to computing, storage and / or network resources provided by one or more physical hardware element (s). A “virtualized resource” can refer to computing, storage, and / or network resources provided by a virtualization infrastructure for an application, device, system, and so on. The term “network resource” or “communication resource” may refer to resources that computing devices / systems can access over a communication network. The term “system resources” can refer to any type of shared device that provides services and can include computer and / or network resources. System resources can be viewed as a set of interrelated functions, network data objects, or services accessible through a server, such system resources residing on a single host or multiple hosts and being uniquely identifiable.

The term “channel” as used here refers to any tangible or intangible transmission medium that is used to transmit data or a data stream. The term "channel" can be synonymous and / or synonymous with "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "connection", "data connection", "carrier", " Radio Frequency Carrier ”and / or any other similar term used to designate a path or medium over which data is transmitted. In addition, as used herein, the term “link” refers to a connection between two devices over a RAT for the purpose of sending and receiving information.

The terms "instantiating", "instantiating" and the like, as used here, refer to the creation of an instance. An “instance” also refers to a specific occurrence of an object, e.g. B. can occur during the execution of program code.

The terms “coupled”, “communicatively coupled” and derivatives thereof are used here. The term “coupled” can mean that two or more elements are in direct physical or electrical contact with one another, can mean that two or more elements are indirectly in contact with one another but still cooperate or interact with one another, and / or can mean that one or more other elements between the elements that are considered to be coupled, coupled or connected to one another. The term “directly coupled” can mean that two or more elements are in direct contact with one another. The term “communicatively coupled” can mean that two or more elements can be in contact with one another via a communication medium, including via a wire or other connection link, via a wireless communication channel or link, and / or the like.

The term “information element” refers to a structure element that contains one or more fields. The term “field” refers to the individual content of an information element or to a data element that contains content.

The term “SMTC” refers to an SSB-based measurement timing configuration that is compatible with SSB-MeasurementTimingConfiguration is set up.

The term “SSB” refers to an SS / PBCH block.

The term "a" primary cell "refers to the MCG cell operating on the primary frequency on which the UE either performs the initial connection setup procedure or initiates the connection setup procedure.

The term “primary SCG cell” refers to the SCG cell in which the UE carries out random access when it carries out the reconfiguration procedure with sync for DC operation.

The term “secondary cell” refers to a cell that provides additional radio resources in addition to a special cell for a UE established with CA.

The term “secondary cell group” refers to the subset of serving cells that includes the PSCell and zero or more secondary cells for a UE that is established with DC.

The term “serving cell” refers to the primary cell for a UE in RRC_CONNECTED that is not set up with CA / DC as there is only one serving cell including the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells that includes the special cell (s) and all secondary cells for a UE in RRC_CONNECTED that is established to with CA /.

The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG in DC operation, otherwise the term “Special Cell” refers to the Pcell.

QUOTES INCLUDED IN THE DESCRIPTION

This list of the documents listed by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent literature cited

• US 63/015290 [0001]

Claims (10)

A device for a New Radio (NR) user equipment (UE) having a radio frequency (RF) interface and one or more processors coupled to and set up with the RF interface; transmit coherency capability information of the UE; receive configuration information including a codebook subset and a full power mode, the codebook subset and full power mode based on the coherency capability information; set up an uplink (UL) transmission according to the configuration information. The device according to Claim 1 wherein the coherence capability information comprises full coherence information of the UE, and / or wherein the coherence capability information comprises a number of antenna ports. The device according to one of the Claims 1 or 2 wherein the coherency capability information comprises a number of transmission layers, and / or wherein the coherence capability information comprises a UE full capability. The device according to one of the Claims 1 until 3 wherein the codebook subset includes precoding information for the UL transmission based on the number of antenna ports and the coherence capability information; and / or wherein the full power mode comprises a transmit full power mode for the UL transmission. The device according to one of the Claims 1 until 4th wherein the configuration information further comprises a power scaling factor for the UL transmission based on the full power mode. A user equipment (UE), which UE may exhibit its coherence capabilities, including fully coherent, partially coherent and non-coherent. The UE can also report its full power uplink operation capability, including Mode 0, Mode 1 and Mode 2. Apparatus for a New Radio (NR) telecommunications node that has a radio frequency (HF) interface and one or more processors that are coupled to the HF interface and are set up: to receive coherency capability information of a user equipment (UE) to determine a codebook subset based on the coherency capability; determine a full power mode based on the coherency capability; configure configuration information for an uplink (UL) transmission of the UE based on the codebook subset and the power mode. The device according to Claim 7 further configured to transmit the configuration information via a radio resource control (RRC) signal; and / or wherein the coherence capability information comprises full coherence information of the UE. The device according to one of the Claims 7 or 8th wherein the coherency capability information comprises a number of antenna ports; and / or wherein the coherency capability information has a number of transmission layers. The device according to one of the Claims 7 until 9 wherein the coherency capability information has a UE full power capability.

Images