NR+RAN+Mid-band+MTR1911(1)

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.11 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 History43Release Information53.1SW Identity53.2Upcoming O&M changes needing preparation134System Level164.1Applicable HW Configurations164.2Compatibility Information174.3Dependencies and Requirements174.4Parameters, Counters, Events and Alarms184.5CPI Library215Setup Instructions216Restrictions and Limitations296.1Restrictions296.2Limitations291 Executive SummaryThis SW package is for the delivery of NR RAN Mid-Band MTR19.11 release for use by the NR-NSA LA Customers.This delivery contains following functionalities: Support for CSI-RS and CSI reporting Support of Maximum cell range up to 4.8 Km (HX52157) MOM switch from the PpFunction MOM sub-tree to the GNBCUUPFunction MOM sub-tree. The Split mode configuration is restricted in this UP.2 Revision HistoryTable 1Revision HistoryRevisionDateChangesChanged byPA22019-03-13First version releaseSharokh AmirijooA2019-03-13Final versionSharokh Amirijoo3 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.11CXP2010045/5 R16B153.1.2 Upgrade PathsThe following From states are tested: gNB MTR 19.09 EC10 (R15B37) / eNB MTR 19.09 EC3 (R62B29)Note: The gNB MTR 19.11 is compatible with eNB MTR 19.09 and EC3. 3.1.3 Trouble Report Mapping LevelN/A3.1.4 Feature contentSee following section for more details.3.1.5 New and changed functionalityFollowing new functionalities are introduced in this MTR: Support for CSI-RS and CSI reporting. The functionality supports the following capabilitieso TRS enabledo CSI-RS enabledo Wideband CQI/wideband PMI aperiodic CSI reportingo PDSCH scheduling in a TRS/CSI-RS sloto 0 dB TRS power-boostingMOM configuration:o set GUtranDUCell attribute trsPeriodicity = 40 millisecondsNo other configuration is needed. A note:Three structures have been introduced in the MOM to enable in future releases, independent activation of CSI-RS using 32, 16 and 8 ports and the configuration of associated codebookAssumptions. These structures, within GNBDU.NRCellDU, have the following names: csiRsConfig32P; csiRsConfig16P; and csiRsConfig8P.Each structure has the attributes: csiRsControlXPorts (X= 32,16,8); i11Restriction; and i12Restriction.Note: default configuration (unchangeable) is according to the following and not possible to change in this MTR:csiRsRowIndex = 8 , and codebookConfig (2,2). System constant settings:o RP17=0 (14 symbol PUSCH)o RP14 = 1 enables aperiodic CSI reporting slot offset selectiono RP22 = 18623 enables: TRS reference signal generation CSI-RS reference signal generation PDSCH scheduling in a TRS/CSI-RS sloto RP27 = 386 enables: Aperiodic CSI reporting Wideband CQI reporting Wideband PMI reportingo RP33: bit nr 0,31 1152 with default TDD pattern (bit 7=1 activates CSI-RS; bit 10=1 sets the 3GPP version) 1408 with other TDD patterns (bit 7=1; bit10=1; bit 8=1 activates multiple TDD patterns) 1280: deactivates CSI-RSo RP67 = 1 enables CSI-RS related UE RRC configuration Support of Maximum cell range up to 4.8 Kmo The introduced system constant, zeroCorrelationZoneConfig RP169, has a range from -1 to 15. In future releases, the SC will be replaced by an ordinary MOM parametero -1 is the default value and this corresponds to the legacy behavior for configuration of zeroCorrelationZoneConfig, which is 14 for FR1 and 0 for FR2. The other valid values will override the hardcoded values for zeroCorrelationZoneConfig.3.1.6 Known Trouble Reports- 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- HX38655 PD TC-FIT team NR Midband SP859: PM counter GUtranCell pmEndcRelUeAbnormalSgnbAct does not step- HX42622/HX39950 NR NSA MB: After cold DU restart sector carrier is disabled- 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- HX49237 AIR6488 B43 - RU restart - RU DPD could not be started - TX failo UE attach issue. Remedy is to restart FieldReplaceableUnit=AAS-1- 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- 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- HX52788: Unable to attach on NR leg with Korean TDD pattern or when changing the BWo Node restart solves the issue.- 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.- HX52912MTR_19.09:NR:MB:STAB5G6:CRASH: Emca 4:DSP 16: draulnrmdbfce_pu rpc/baseband_.o Been identified connected to simulation tools. - 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- HX52415IODT 5G NR NSA: after changing Bandwidth from 20 to 100, no SSB sento gNB node restart required to recover- HX52401MTR19.09:NR MB:STAB5G6: pmCellDowntimeAuto is stepped during stability run- HX52351MT:NR:STAB5G6:AIR6488 Crash: Program: lhsh_shelld. Signal: 6. PMD: /var/log/pmd/pmd-itc_coordinat.- HX52415IODT 5G NR NSA: after changing Bandwidth from 20 to 100, no SSB sento Node restart recover the fault- HX52788Unable to attach on NR leg with Korean TDD pattern or when changing the BWo Node restart recover the fault- HX53617MTR19.09:NR:STAB5G6:NR KPI degradation Retainability- HX53654NR:MTR19.09 GNB LPP_send to invalid virtual pidnpid:- HX54004NR:MTR19.09: eNB ERAB ID is included in to-be-modified list with invalid transport address & gtp.- HX54275MTR_19.09:NR:MB:STAB5G6:CRASH: Emca 1:DSP 56: Unhandled interrupt: Software contro rpc/baseband_.- HX543555G NSA NR CD MTR19.09 gNB AIR6488B43 crash after radio restart by Recovery action bcz of- HX543975G NSA NR CD MTR19.09 eNB retainability rate increased- HX54410NR NSA MB: System Constant PP19 changed back to default at large restart- HX54474NR MTR19.09: AIR6488B43 Antenna Calibration UL Failure alarms- HX54569NR:MTR19.09 AIR6488 Program: restart. Rank: Cold. Extra: Managed- HX54290IODT NSA HB: eNB sets 0 IP at E-RABModification- HX54568UL Data stops at NR PDCP when UL on LTE with NR NEA2 Ciphering is enabled (initialUplinkConf 0 (M.- HX54893Compared to LTE CRS RSRP, measured NR SSB RSRP is lower than expected3.1.7 Corrected Trouble Reports- HX48190NR:MTR19.03-2: PTP delay request messages non compliance- HX52414 MTR19.09:NR:STAB5G6:NR KPI degradation on RA and Retainabilityo Looks like there is an issue with Random access counter, pmRadioRaCbSuccMsg3, investigation ongoing.- HX50258NRmidband: The cell never come up after c2/Cpri link breaks test and the node has NO alarms eithero Fault not reproduced in later UP- HX50414NR Midband NSA UP revision R15A111 faultId: 0x301 (SwError), faultDescription: Emca 1:DSP 21: 19 (throughput150Mb/s) in DL for 100Mhz causes BB-crashe: !Another L1 Alloc I.- HX39411 NR MTR18.49-ppeArmLm-Bearer inactivity detected while waiting for response on node internal- HX22561 NR midband NSA: R6A56 - SectorCarrier goes disabled when Cell is deblocked then recovers to enabled- HX25984 AIR6488: illegal access due to sXP failureo Duplicate: HX31513 MTR18.43 during Iperf DL traffic - AIR6488 pmd-xenonSpi_0.0.2-4691 crasho Duplicate: HX29447 AIR 6488 R1C/A are cyclic restart after power on- HX26592 Crashing radio applic is continuously loadedo This was due to bad radio load module. A fail-safe solution is being considered in future releases.o Improvements planned in coming releases.- HX29397 5G NR MB - Lose AIR6488 communication when you swap CPRIs between two DUs- HX46515 CPI NR NSA Midband: Baseband Radio Node MTR 18.49: Ambiguous probable cause gsm1211LinkFailure (517) for alarm ExternalLinktoGNodeBFailureo No fault- HX48832 NR: rrcConnectionReconfiguration not recived by the UE after NR RLFo No fault- HX48637 NR: NR leg setup failing due to SgNBAdditionRequestReject:transport-resource-unavailable- HX48168 NR Restart: State timeout received type STATE_TIMEOUTo Restart seen when missing license CXC4012272 MassiveMIMOMidBand not being enbled- HX48153 NR GNB Emca 1 - ULPDCPNRPE_ELEMENTNRTOR_ unknownSignalHandler.c:86: ULPDCPNRPE_elementNrTor received an unknown signal id: 0x76fbo No fault- HX47335 NR Antenna Calibration UL Failure- HX47973 Spontaneously restart seen, Emca 3:DSP 42: dlrlcnrpe_rbstatus_q rpc/baseband_resource_set/handler/src/eqmhi_baseband_state_machine_impl.cc:8653.1.8 General Public Licensed Source CodeThis Baseband SW package includes Free and Open Source SW (FOSS) under the terms of GNU General Public License (GPL) and GNU Lesser General Public License (LGPL). These programs are free software, which can bere-distributed and/or modified under the terms of GPL respectively LGPL as published by the Free Software Foundation.In order to fulfill the GPL terms, the corresponding source code can be delivered upon customer request through SW Gateway.Table 3FOSS in SW GatewayProduct in SW GatewayFunction DesignationR-State3/CXP 201 0045/5 Baseband SW FOSS LicensesR3AA list of all included FOSS can be found in document Free and Open Source Software.3.2 Upcoming O&M changes needing preparationMTR releaseMajor O&M changeMTR 19.11Upgrade to SW package MTR19.11 will cause a gNB MOM switch from the PpFunction MOM sub-tree to the GNBCUUPFunction MOM sub-tree. All attributes in the GNBCUUPFunction MOM sub-tree must be configured prior to the upgrade.MTR 19.15Upgrade to SW package MTR19.15 changes the currently inactive GNBDUFunction MOM sub-tree. These changes enable a complete pre-configuration of the 3GPP aligned gNB MOM, and this as a preparation for needed activities planned for MTR19.19.MTR 19.17Upgrade to SW package MTR19.17 requires that gNB have been previously migrated in ENM from neType / meType 5GRadioNode to RadioNode.RadioNode migration requires ENM 19.05.MTR 19.19Upgrade to SW package MTR19.19 enables a possibility to switch from the Ericsson proprietary gNB MOM to the 3GPP aligned gNB MOM (MOM sub-trees with top MO classes GNBDUFunction and GNBCUCPFunction). Activation of the 3GPP aligned gNB MOM requires a complete configuration of the 3GPP aligned gNB MOM prior to the switch (if not done previously). As from MTR 19.19 all future functional growth will be on the 3GPP aligned gNB MOM.MTR 19.23Upgrade to SW package MTR19.23 will execute the switch from the Ericsson proprietary gNB MOM to the 3GPP aligned gNB MOM (MOM sub-trees with top MO classes GNBDUFunction and GNBCUCPFunction) unless this has already been done. Performing the switch as a part of the upgrade requires a complete configuration of the 3GPP aligned gNB MOM prior to the upgrade.For further information please contact the PDU. Detailed information will be provided in release documentation for each MTR3.2.1 MTR19.11 PpFunction - GNBCUUPFunctionIn SW Package MTR19.11 there is a non-backwards compatible change in the gNB MOM. The PpFunction MO tree is replaced by the GNBCUUPFunction MO tree.In MTR19.11 all attributes in the PpFunction MO tree become inactive, and the corresponding attributes in the GNBCUUPFunction MO tree become active.These changes require a re-configuration before a gNB upgrade to MTR19.11 SW, no matter what the upgrade from-state is. This change has been announced in previous Early Delivery Notes for previous SW Packages, and a pre-configuration of attributes in the GNBCUUPFunction MO tree has been recommended. If this recommendation has been followed, and the attributes are already correctly configured, there should be no need for further changes to the gNB configuration.In case no previous pre-configuration has been made, attributes in the GNBCUUPFunction MO tree must be configured prior to the gNB upgrade to MTR19.11, or to any later SW Package.This change will also have an impact on configuration scripts used to integrate new nodes on gNB SW Package MTR19.11 or later. When SW Package MTR19.11 is in use during the integration, both attributes in the PpFunction MO tree and attributes in the GNBCUUPFunction MO tree can be included configuration scripts simultaneously. But as the PpFunction MO tree will be removed in a coming SW Package, the corresponding parts of the configuration scripts must eventually be removed.For assistance with the re-configuration (unless done previously), a script which can be run via ENM/AMOS is provided. The mos script can be run in batch mode. Below is an instruction which can be used if this option is chosen.What the script doesThe script reads attributes in PpFunction MO, then creates GNBCUUPFunction MO instance applying the attribute values just read.If a GNBCUUPFunction MO instance already exist in the node, this will be deleted, and then recreated applying the PpFunction MO attribute values.After the script is completed, the node will have both a PpFunction MO tree and a GNBCUUPFunction MO tree, both with same attribute values (i.e. PpFunction will not be removed by the script).Preparations- AMOS/moshell version 19.0c (recently released) is recommended, but as a minimum version 18.0p is needed (older versions than 18.0p will be rejected by the script).