5G RAN Feature Part1(Post)
This article simplifies the basic understanding of 4 features and explains how to verify features functionalities from the traces and field testing. The same content was already explained earlier in a YouTube video (shared below)
Feature 1: UL 256QAM
Introduction
UL 256QAM is a basic feature in 5G. UL 256QAM provides around 33% gain in 5G UL Peak speed compared with 64QM, as UL256QAM transfer 8 bits per symbol while 64QAM transfer 6 bits per symbol.
Under favorable radio environments where users are near the cell center and are enjoying a very good SINR, Peak UL User throughput using 256QAM can increase up to 33% compared to 64QAM.
Feature Verification Steps
During Field testing:
1) Confirm UE Capability – 256QAM support
Before starting field testing, confirm that the test device supports UL 256 from the below-given message, which can be checked through the UE Capability message.
2) After starting the test, you need to check and confirm that MCS-Table: 256qam is delivered in RRC Reconfiguration msg to the test UE
The below is a 3GPP comparison tables between 256QAM & 64QAM for reference
Feature 2: PUSCH Waveform Adaptation
Introduction
The waveform is the baseband signal which is mixed to RF before being radiated across the air interface. 3GPP has specified two waveforms for New Radio(NR) based upon Orthogonal Frequency Division Multiplexing(OFDM):
The following table summarizes the differences between CP-OFDM
and DFT-S-OFDM
The BTS may dynamically reconfigure the UE according to the coverage conditions. Usually, BTS relies upon a pre-defined threshold for PUSCH SINR to switch between both waveforms. As shown in the below-given figure, BTS switched to DFT-S OFDM once the user moved to Cell Edge.
After the uplink waveform adaptation function is enabled, compatibility issues may occur on UEs not supporting the DFT-S-OFDM waveform, causing service drops.
The BTS instructs the UE to switch or use a specific mode by sending RRC reconfiguration message, where you need to check the transform precoder value under Pusch-Config message
Recommended by LinkedIn
Feature 3: DL Beamforming weight calculation based on SRS feedback
Introduction:
Generally, BTS Adjusts the shape and direction of downlink beams, and the BTS calculates the weight based on the UE feedback for the DL Channel Characteristics.
DL Beamforming weight calculation is measured by the BTS after receiving the feedback UE. 2 different methods can be used by the Users to provide feedback.
1) Through measuring CSI-RS “Codebook-based transmission.
2) Through transmitting SRS, “Reciprocity-based transmission.”
The main differences between both methods are that:
SRS DL-Based Beamforming ”Test Verification”
BTS can use SRS to estimate the downlink propagation if the UE supports any of the following categories:
The below highlighted parameter " supportedSRS-TXPortSwitch if not included in the UE capability message this means the device does not support
To Confirm the current SRS Usage, you can check the below-highlighted message in the RRC reconfiguration message. USAGE= Antenna switching indicates that the SRS will be used for DL estimation purpose
Feature 4: Signaling Radio Bearer Activation"SRB3"
SRB3 is optional and provides a direct SRB between the Secondary RAN Node and the device.
RRC Signaling through using NR SRB3 might reduce the latency.
The following RRC messages will be handled through SRB3 For EN-DC operation:
•RRC Reconfiguration.
•RRC Reconfiguration Complete.
•Measurement Report.
Section 7.5 "SRB3" in 3GPP TS 37.340 V15.7.0,
If the UE does not support SRB3, signaling cannot be directly exchanged between the gNodeB and the UE
14 Years of Professional Experience in | 2G | 3G | 4G | 5G | RF Optimization | Planning | Performance | Team Management
1yThat means there would be two CQI/MCS index tables with 64 and 256 QAM on the a gNodeB side, depending on what criteria the schedule will switch between them, or would it be based on UE capability? Suppose UE supports 256 QAM, but once it moves from good coverage to weak coverage, which MCS index table will follow, the 256 QAM table, or will switch to 64 QAM? I'd be grateful if you could clear up my basic misunderstanding.