NR RAN Mid-band MTR19.13(2)

AbstractThe intention of the release notes is to supply our internal customers with information about the contents of the delivery. NR RAN Mid-band MTR19.13 Ericsson AB 2019 All rights reserved. The information in this document is the property of Ericsson. Except as specifically authorized in writing by Ericsson, the receiver of this document shall keep the information contained herein confidential and shall protect the same in whole or in part from disclosure and dissemination to third parties. Disclosure and disseminations to the receivers employees shall only be made on a strict need to know basis. The information in this document is subject to change without notice and Ericsson assumes no responsibility for factual inaccuracies or typographical errors.Contents1Executive Summary42Revision History53Release Information63.1SW Identity63.2Upcoming O&M changes needing preparation204System Level234.1Applicable HW Configurations234.2Compatibility Information244.3Dependencies and Requirements244.4Parameters, Counters, Events and Alarms254.5CPI Library285Setup Instructions286Restrictions and Limitations376.1Restrictions376.2Limitations381 Executive SummaryThis SW package is for the delivery of NR RAN Mid-Band MTR19.13 release for use by the NR-NSA LA Customers.This delivery contains the following, please see the section 3.1.5. for details. HARQ and Link adaptation improvementso Delivery of UL HARQ re-transmissions and UL LA (PHR) corrections in AD5. o Note: UL LA improvement requires LTE eNB MTR 19.13. 3 x 100 MHz cells improvementso Increased DL throughput, up to 1.5 Gbps in total in 3 cells with 3 UEs Support of 50 Connected Users on 40/100 MHz, one cells LTE Mobility, supporting different legacy handover scenarios for EN-DC connected UEs. Ready for Lab testing, requires LTE eNB 19.13. VoLTE feature is supported for the EN-DC connected UEs. Restricted in this delivery, IODT ongoing. LTE RRC Connection Re-establishment, 1st feature drop. Restricted in this delivery, IODT ongoing. Antenna Calibration 64branches + cell shaping 60MHz Removal of UL PRB/throughput limitation, full UL bandwidth is supported with 2 C2 links, 100 MHz.2 Revision HistoryTable 1Revision HistoryRevisionDateChangesChanged byPA22019-03-27First version releaseSharokh AmirijooA2019-03-28First version for MTR 19.13 AD5 deliverySharokh AmirijooB2019-03-31First version for MTR 19.13 deliveryMagnus Sundelin3 Release Information3.1 SW Identity3.1.1 Upgrade PackageThe table below defines high level data for the SW in this package. Table 2SW PackageSW PackageProduct Number5G Radio Node MTR 19.13-AD5CXP2010045/5 R17B313.1.2 Upgrade PathsThe following From states are tested: gNB MTR19.11 AD8 (R16B29) / eNB MTR19.11 (R63B27) gNB MTR 19.09 EC10 (R15B37) / eNB MTR 19.09 EC3 (R62B29)3.1.3 Trouble Report Mapping LevelN/A3.1.4 Feature contentSee following section for more details.3.1.5 New and changed functionalityNote:During out delivery test in OTA environment with real UE it was not possible to setup ENDC after upgrade to R17B31. The following error message was seen: ARP configuration does NOT allow the UE to have Split bearers. Remedy is to set splitNotAllowedUeArpLev = 0, i.e.: set EndcProfile splitNotAllowedUeArpLev 0 Following new functionalities are introduced in this MTR:LTE Mobility (Ready for Lab, requires LTE eNB 19.13):Supporting different legacy handover scenarios for EN-DC connected UEs: The eNB system constant System constant (4045) enableHoForEndcUe is used to enable the functionality. By default the functionality is disabled, meaning that the existing Intra Frequency LTE is supported where the first measurement report, MR A3 will trigger the NR leg and 2nd MR will initiate HO procedure. Two PM counters previously introduced are updated where the condition is added for intra-cell handover:o pmEndcRelMnMcgRelocAtt (MOC: EUtranCellFDD/EUtranCellTDD)o pmEndcRelMnMcgReallocSucc (MOC: EUtranCellFDD/EUtranCellTDD) One existing PM event is updated where the stop condition is added for intra-eNB handovero INTERNAL_PROC_HO_EXEC_X2_IN Packet forwarding for SN terminated bearers is not supported at this stage, planned in future MTRs. internal packet forwarding during intra cell handover with NR leg release for MN terminated bearers is not supported at this stage, planned in future MTR releases.VoLTE support (Restricted in this delivery, IODT ongoing, requires LTE eNB 19.13):The feature is also supported for the EN-DC connected UEs.The description in the CPI LTE-NR Dual Connectivity slightly deviates from the actual implemented functionality and will be corrected in the next release of CPI.Three new MOM parameters have been introduced which also control the VoLTE functionality: EndcProfilePredefined:splitNotAllowedUeArpLev Controls if configuration of split bearers is allowed for the UE (default 7). EndcProfile: splitNotAllowedUeArpLev Controls if configuration of split bearers is allowed for the UE (default 7). EnodeBFunction: endcSplitAllowedNonDynPwrShUe Default value is FALSE which means VoLTE and Split bearer are not allowed in parallel for UEs not capable of Dynamic power Sharing. At least, there is one UE vendor which does not signal capability for Dynamic power sharing, however it supports maximum transmission power per LTE and NR (23dBM + 23 dBm), which in practice would allow parallel VoLTE (MCG bearers) and Split bearers. Therefore, it is recommended to set the endcSplitAllowedNonDynPwrShUe to “true” and instead use the attribute splitNotAllowedUeArpLev to control whether parallel VoLTE and split bearer are allowed or not.The default setting of the splitNotAllowedUeArpLev is that VoLTE and Split bearers are not allowed. This results in that the Secondary Cell Group release is triggered at E-RAB Setup during the VoLTE call setup. At trigger of SCG release, the Secondary Node terminated split DRB is reconfigured to the Secondary Node terminated MCG DRB. Resources for the SCG are released, but the PDCP context is kept. Furthermore, the B1 measurement is started when the VoLTE call is released, which upon the reception of the B1 measurement report will trigger Secondary Cell Group addition and setup of SN terminated Split DRBs (NR leg) again.There is a system constant to enable/disable the X2: SgNB Modification procedure, enableSgNbModificationRequest (4072), default value: Disabled.The following describes the different settings: If the ENDC profile setting allows VoLTE and Split bearer in parallel, then the setting of the system constant does not have any meaning. If the ENDC profile does not allow VoLTE and Split bearer in parallel, then: o If the SC is set to enabled then SCG release is trigged, i.e. the Secondary Node terminated split DRB is reconfigured to the Secondary Node terminated MCG DRB.o If the SC is set to disabled, then setting of the ENDC profile is not followed, and parallel VoLTE and Split bearer is allowed anyway. It is recommended to set the enableSgNbModificationRequest (4072) to “enabled” and set the EndcProfile: splitNotAllowedUeArpLev to get the desired behavior.Events: The following PM events are introduced in the eNb: X2_SGNB_MODIFICATION_REQUEST X2_SGNB_MODIFICATION_REQUEST_ACKNOWLEDGE X2_SGNB_MODIFICATION_REQUEST_REJECT INTERNAL_PROC_X2_MN_INIT_SGNB_MOD The following PM events are introduced in the gNB (restricted in this MTR, planned for future MTRs): CuCpX2SgnbModificationRequest CuCpX2SgnbModificationRequestAcknowledge CuCpExtX2SgnbModificationRequestReject CuCpProcX2MnInitiatedSgnbModificationPreparation Counters:New Counters in the eNB: pmEndcSetupScgUeAtt pmEndcSetupScgUeSuccNew counter in the gNB (restricted in this MTR, planned for future MTRs): pmEndcSetupScgUeAtt pmEndcSetupScgUeSucc LTE RRC Connection Re-establishment, initial delivery (Restricted in this delivery, IODT ongoing, requires LTE eNB 19.13):o Supports for legacy LTE RRC Re-establishment (intra-cell, intra-eNB and inter-eNB re-establishment scenarios) for the EN-DC connected UE, i.e. the NR leg is already established and there is no other ongoing procedure, such as LTE handover, RRC Connection Reconfiguration, etc. The re-establishment procedure will trigger release of NR Leg.o After RRC Reestablishment is completed, PDCP is relocated for all bearers to the eNB in which RRC Reestablishment was triggered and the Measurement based NR leg setup is supported. If B1 measurement report is successfully received, the NR leg is setup again.o Support of Observability and configuration: System constant in eNB: enableRrcReestForEndcUe (4090) 0 : Disable 1 : Enable Modified PM counters to support the new functionality: pmFlexRrcConnReestAtt, pmFlexRrcConnReestSucc, pmEndcRelMnMcgRelocAtt, pmEndcRelMnMcgRelocSuccSupport of 50 Connected Users on 40/100 MHz one 1 cell:Up to 50 connected UEs with 1 DRB (split bearer) each has been tested.Up to 10 connected UEs with 4 DRBs (Split bearers) have been tested. Increasing the number of CUs may cause instability and system restarts.System constants setting: RP15:50, RP16:10, RP148:5 Which means:50 connected UEs, 10ms SR periodicity and 5 UEs are configured with low latency SR periodicity. RP15: maxRrcConnectedUsers, range 0, 50, Default: 5 RP16: commonSrPeriodicity; range: 0, 12; Default value: 4 Sr-Periodicity values defined in TS 38.331o 0: 2symo 1: 7symo 2:1slo 3: 2slo 4:4slo 5:5slo 6:8slo 7:10slo 8:16slo 9:20slo 10:40slo 11:80slo 12:160sl RP148: pucchLowLatencyUe, Range: 0, 20Default=00: No LowLatency UEs are configured, all UEs will beconfigured with the same PUCCH srPeriodicity.1: Used as input for minimum requested number of UEs with lowestavailable srPeriodicity (LowLatency UEs)NOTE: Actual number of LowLatency UEs might be higher if there are available PF1 resources.HARQ and Link adaptation improvements: Support of UL HARQ re-tx up to 4 re-tx (RP49=5). Please reduce the no of re-tx if instability issues are observed.o HX58855/HX57957: UL HARQ crash issue seen on AD5 Support of UL LA, delivery of the HX57160: UL LA not working due to lack of PHR. Note: this correction requires LTE 19.13 SW, as part of the correction is delivered in the LTE eNB. DL HARQ re-tx is not supported (RP46=1). Ongoing investigation to solve the open TRs in this area (HX57833, HX57344) The following corrections are delivered:o HX57466: 5G NSA NR CD 19.11 AD6 Many HARQ NACKs are detected in gNB even though UE almost sends ACK .o HX57914SKT 5G NSA NR CD MTR19.11 AD8 gNB crash: Recovery action initiated by BB via BCI, faultId: 0x30.3 x 100 MHz cells:The 3 cells feature has been improved in this release reaching up to 500 Mbps per UE with 3 UEs, one per each cell.In total, up to 1.5 Gbps per Baseband unit.Following SC configuration is used:RP14:1,RP150:50,RP17:0,RP22:18623,RP24:513,RP25:32,RP27:386,RP30:5,RP33:1408,RP67:1,RP78:125,RP85:7 CSI-RS/TRS activated. The test setup does not allow 3 simultaneously active UEs in 3 cells due to UE sim limitation. One UE has been active at the time. Long PUSCH/PUCCH (14 symbol) activated 3 UEs located, one per UE, 2 layers per UE 3 cells and LA and HARQ (with no re-TX) was activated during the testing, no issue observed during the testing with UE sim. 50 PRBs in ULAntenna Calibration 64branches + cell shaping 60MHz Feature is supported, has passed the OTA testing.Removal of UL PRB limitations (150) with 2 C2 links:With 100 MHz and 2 C2 links, the limitation of 150 UL PRBs is lifted. The RP150 can be set to max PRBs (273). With 100 MHz and 1 C2 link, the existing limitation still valid, i.e. RP150=150. This will remain until Advanced Receiver feature is delivered.3.1.6 Known Trouble Reports3.1.6.1 Common TRsThis section summarizes TRs common to Low-Band, Mid-Band and High-Band and independent on CPRI and eCPRI radios.- HX58667 NSA:HB:APC crash in apcMain after upgrade- HX38655 PD TC-FIT team NR Midband SP859: PM counter GUtranCell pmEndcRelUeAbnormalSgnbAct does not step- HX44943 NR:MTR18.49-7:Integrity flex counters Endc1to99 and Endc2to99 do not peg- HX49264 NR:MTR19.05 Request to update CPI alarm list for MO GNodeBSectorCarrier- HX48795 NR GNB SIGABRT - rcNwifX2Arm and rcNwifN2Armo Additional trace of type INFO will be added into the NWIF component code to be able to detect the cause of fault if it happens again- HX52834Swisscom:NR:MTR19.07 UL PDCP Packets dropped due to SN outside reordering windowo Temporary solution Increase MOM parameter tReorderingUlPdcp to 200 instead of 10. Intention is that this parameter should change to default 200 in MTR19.15.- HX52557VzW:NR:MTR19.05: No alarm info External Link to GNodeB Failure on ENodeBFunction=1 in eNB / NR .o X2 gNB related alarm missing in eNB CPI- HX52401MTR19.09:NR MB:STAB5G6: pmCellDowntimeAuto is stepped during stability run- HX53654NR:MTR19.09 GNB LPP_send to invalid virtual pidnpid:- HX54410NR NSA MB: System Constant PP19 changed back to default at large restart- HX55336 NR NSA: Changing channel bandwidth may result in corrupt spectrumo Always perform cell lock/unlock when changing bandwidth.- HX54441 MTR19.09-2: Program Crash in apcMain: SIGABRT- HX57451 NR:MTR19.11 LTE+NR DL-CA - less and irregular end-user throughput- HX57582 NR:MTR19.09 EC14: gNB No traffic due to gNB UL PDCP with numGtpuPktsDropThreadQueueFull incr = numGtpuPktsRx incr- HX57872 5G NSA CD MTR19.09: Counter pmCellDowntimeMan pegging when cell is unlocked/disabled3.1.6.2 eCPRI specific TRs (Midband C2)This section summarizes TRs specific for eCPRI radio configurations.- HX30386 5G NR MB - AIR6488 - Systemization issue: RiLink ENABLED unexpected behavior- HX37267 NRmid:Cold node restart with test in Gnode then no RU power sleeping cell- HX42622/HX39950 NR NSA MB: After cold DU restart sector carrier is disabled- HX52351: MT:NR:STAB5G6:AIR6488 Crash: Program: lhsh_shelld. Signal: 6. PMD: /var/log/pmd/pmd-itc_coordinator-1032-20190226-173312.tgz. Extra: CXP2030020%4_R16B10- HX52415IODT 5G NR NSA: after changing Bandwidth from 20 to 100, no SSB sento gNB node restart required to recover- HX54474NR MTR19.09: AIR6488B43 Antenna Calibration UL Failure alarms- HX54582 5G NSA NR CD MTR19.09 AIR6488B41 report Antenna Calibration UL Failure alarm after upgrade - HX559845G NSA CDMTR19.09 EC3 NR BB rpcBbrsNrArm crash Extra: Recovery action initiated by BB via B.- HX551405G NSA CDMTR19.09 EC3 NR BB rpcBbrsNrArm crash Extra: Recovery action initiated by BB via B.- HX55330NR midband: RU restarts when performing CPRI link break on one Rilink- HX560075G NSA CDMTR19.09 NR Crash : Recovery action initiated by BB via BCI, faultId: 0x301 (SwEr.- HX560515G NSA CDMTR19.09 AIR6488 Crash : Program restart. Reason: Program Crash. Program: radioapp.- HX54297NR NSA: Crash Stack overflow in DLL1NRMDBFUPE_PDSCHSETOR_handleNrdll1eiDataInd while doing retran.- HX57606/ HX56627NR NSA: Emca 4:DSP 57: crash while testing LTE co-existence patternCrash with LTE co-existence pattern and long PUCCH activated.- HX56932PM counter pmRadioRaCbFailMsg3Crc is counting both DTX and CRC failures- HX569725G NSA NR CD MTR19.09EC3 Air6488B43 2nd ASS/Sector enable, but sectorcarrier disabled witho.- HX57344IODT 5G NR NSA: 95% re-transmitted DL TB fails- HX573585G NSA NR CD MTR19.11 AD6 Rilink enable but AAS(Air6488B43) disabled without alarm- HX57606 5G NSA NR CD MTR19.11 BB crash Emca 4:DSP 47: during SU-MIMO throug.- HX576095G NSA NR CD MTR19.11 BB crash Emca 1:DSP 51: bbiXbmc_utils_send.h:190 during SU-MIMO thr.- HX57703NR NSA MB: After restart of RU Antenna Calibration UL Failure alarm is raised- X57825NR NSA: Same HARQ process ID used in consecutive HARQ reports with the LTE Co-existence pattern- HX57833 5G NSA NR CD MTR19.11 AD8 gNB crash: Program: rpcBbrsNrLocalArm, faultDescription: Emca 2:DSP 17: Stack overflownin: .- HX57909 5G NSA NR CD MTR19.11 AD8 gNB crash: Recovery action initiated by BB via BCI, faultId: 0x301 (SwError), faultDescription: Emca 4:DSP 35: upcuedlnrce_common rpc/baseband_resour- HX57914 5G NSA NR CD MTR19.11 AD8 gNB crash: Recovery action initiated by BB via BCI, faultId: 0x301 (SwError), faultDescription: Emca 4:DSP 0: Colossus fatalnFault code/Signal num rpc/baseband_resourc- HX57964 5G NSA NR CD 19.11AD8 NR TCP DL Traffic, DL MCS is 0 despite high CQIo It looks like a UE issue - HX58000AIR6488 B41K NR100: AC alarm raised during DU restart3.1.7 Corrected Trouble Reports- HX576145G NSA NR CD 19.11AD8 DL LA Crash Emca 4:DSP 26: upcuedlnrce_common- HX57825 NR NSA: Same HARQ process ID used in consecutive HARQ reports with the Sprint pattern- HX57466SKT 5G NSA NR CD 19.11 AD6 Many HARQ NACKs are detected in gNB even though UE almost sends ACK .- HX57160ServCellIndex change to 16 results in non working PHR.o Corrected an issue that result in Power Headroom report is not working res