- Added PTRS extraction and estimation for DL
- Added processing for whole slot wrt PTRS estimates
- DLSIM is updated to used -T flag to enable PTRS
- DMRS compensated signal is further compensated with PTRS estimation
Integration 2020 wk44
MR923 : Fixes tun
TUN-interface related changes
MR925 : bugfix: fix frequencies in nr_bandtable
The array nr_bandtable has then been reviewed fully and all the values that were wrong have been changed. The check of correctness was done using the website https://www.sqimway.com/nr_band.php
MR931 : Finalize oaicn integration (CI)
In addition, the "known unstable scenarios" are highlighted in the CI HTML reports.
MR917 : NR CSI reporting
This is a new feature
- Added PTRS variables in transport UE header file
- Added DMRS inline symbol check function in refsig.h
- Added PTRS estimation and other related structures in defs_nr_UE.h file
- PTRSPortIndex, PTRSTimeDensity, PTRSFreqDensity, PTRSReOffset, nEpreRatioOfPDSCHToPTRS
- mcs_table : to calculate MCS table in MAC layer and pass tp PHY
- pduBitmap : same as used in DL FAPI interface, to enable or disable PTRS processing
- Added a function to add PTRS values in RRC context.
- This function can be used to overwrite the PTRS values also.
- When RRC config file contains PTRS values then this function can be used
respectively in RRC context.
Integration 2020 wk42 (2)
MR921 : Hotfix for DL DCI issue in UE
Fixing a bug from last MR.
Fix in nr_dlsim that prevents reporting false 'PDSCH ok' message
MR915 : Fix to avoid RRC->X2AP ticking every msec when x2ap task is not enabled
The aim of itti RRC_SUBFRAME_PROCESS message (MAC->RRC) is to trigger an itti X2AP_SUBFRAME_PROCESS message (RRC->X2AP)
This change avoids creating RRC_SUBFRAME_PROCESS message if x2ap task is not enabled
UE initiates the RA procedure with sending message 1 via PRACH 150 frames after synchronizing with the gNB.
As the frame numbers wrap at 1024, we have to calculate the frame number for message 1 using modulo calculation.
The T tracer macpdu2wireshark has been modified to handle the new traces.
The usage is the same as for LTE.
In NR the RACH is logged as an LTE RACH. Maybe we'll change that in the
future. Looking at the source code of wireshark, I could not find any
way to report NR RACH. Maybe they forgot it. Or I did not search correctly...
Parminder Singh