FL16A 4 0 Release Summary and Impact

Release Summary and Impact Product Family: Product: Release:

Base Stations Flexi Multiradio BTS LTE FL16A 4.0

Approval date:

27-Feb-2017

FL16A 4.0 Release Summary and Impact - Page 1/29 Version 1.0 Confidential

© Nokia 2017

Table of Contents 1. 2.

3. 4.

5.

6. 7.

Purpose ................................................................................................................................................... 5 Corrections .............................................................................................................................................. 5 2.1 FSMF & AirScale ................................................................................................................................ 5 2.2 FSME .................................................................................................................................................. 7 New / Changed functionality ................................................................................................................... 7 Restrictions ............................................................................................................................................. 8 4.1 Restricted Released Features ............................................................................................................ 8 4.2 Other restrictions ................................................................................................................................ 8 DHCP Lease Renewals (Flexi & AirScale) ................................................................................ 8 DHCP Lease Time (Flexi & AirScale) ........................................................................................ 8 Radio Detection (AirScale) ......................................................................................................... 9 SFP Swapping (AirScale) .......................................................................................................... 9 Radio Detection (Flexi & AirScale) ............................................................................................. 9 Optical Cable Moves In Between eNBs Within 30 seconds (Flexi & AirScale) ......................... 9 ALD Software Download (Flexi & AirScale) ............................................................................... 9 ACF File Download (AirScale) ................................................................................................... 9 IP Addressing (Flexi & AirScale) ..............................................................................................10 Radio Detection (AirScale) .......................................................................................................10 Radio Alarm Rate (AirScale) ....................................................................................................10 Optical Cable Swaps on Same BBU (Flexi & AirScale) ...........................................................10 Amphenol Multi-RET Tilt to Zero (AirScale) .............................................................................10 Radio LEDs (AirScale) .............................................................................................................11 Rx Blocking (AirScale) .............................................................................................................11 Low Voltage Alarm (AirScale) ..................................................................................................11 Radio Detection (Flexi & AirScale) ...........................................................................................11 Overcurrent Alarm Generation (Flexi & AirScale) ....................................................................11 Radio LEDs (Flexi & AirScale) .................................................................................................12 Hot remove/insert procedure (Flexi and AirScale) ...................................................................12 dlCarFrqEut parameter issue (Flexi) ........................................................................................12 Security GW rehoming .............................................................................................................12 UHIC - unit autonomous reset issue ........................................................................................12 Cell reconfiguration data distribution failed (6257) for SyncHub configuration ........................12 Antenna Line Device Failure (1806) for FSME sites ................................................................12 Released objects...................................................................................................................................13 5.1 Flexi Multiradio BTS..........................................................................................................................13 5.2 NetAct ...............................................................................................................................................16 SW download and activation times .......................................................................................................16 Effects on operator ................................................................................................................................16 7.1 AirScale introduction in FDD-LTE16A ..............................................................................................16 7.2 Phase-Out of FSME system module ................................................................................................16 7.3 KPI changes .....................................................................................................................................16 Corrected counter: M8006C270 ERAB_REL_ENB_RNL_RED_QCI1 ....................................16 Corrected KPIs: LTE_5571d E-UTRAN E-RAB QCI1 and LTE_5582b E-UTRAN QCI1 ........17 Corrected counter: M8001C44 PUSCH_TRANS_USING_MCS28 .........................................17 Corrected counters: M8006C255 and M8006C176 .................................................................18 Corrected counters: M8048C2 .................................................................................................19 Corrected counter: M51132C3 .................................................................................................19 Corrected KPI: LTE_5143a ......................................................................................................20 Corrected KPI: LTE_5700a ......................................................................................................20 Corrected counters: M8029C* .................................................................................................21 M8006C245 increase on FSME sites ......................................................................................22


© Nokia 2017

Corrected counter M8013C33 ..................................................................................................22 Corrected KPI LTE_5240a .......................................................................................................23 Corrected counter M8012C143 ................................................................................................23 Corrected counter M8051C118 ................................................................................................24 Corrected KPIs: LTE_5571d E-UTRAN E-RAB QCI1 and LTE_5582b E-UTRAN QCI1 ........24 Corrected counters: M8006C176-M8006C180 and M8006C239-M8006C243 .......................25 Corrected counters: M8012C20, M8012C25, M8012C26, and M8012C143 ..........................26 7.4 Alarm Changes .................................................................................................................................27 Corrected alarm: “Failure in replaceable baseband unit (6700)” .............................................27 Corrected alarm: “BTS reset needed (4001)” ..........................................................................27 Corrected fault: “High interference to UL subframe (6117)” ....................................................28 8. Piloting ..................................................................................................................................................28 9. Appendices / References ......................................................................................................................28

Contact: Contact your local Nokia support.

Summary of changes: 27-Feb-2017

1.0


Approved version

© Nokia 2017

Disclaimer The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within Nokia Group of Companies with whom you have entered into the Agreement (as defined below). This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia. If You have not entered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof. The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility when using it. Nokia welcomes your comments as part of the process of continuous development and improvement of the documentation. This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such information and statements without notice. Nokia has made all reasonable efforts to ensure that the content of this document is adequate and free of material errors and omissions, and Nokia will correct errors that You identify in this document. Nokia's total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product will be uninterrupted or error-free. NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT. This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any third parties without the prior written consent of Nokia. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners. Copyright © 2017 Nokia. All rights reserved.

Important Notice on Product Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set. Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia for any additional information.


© Nokia 2017

1. PURPOSE The purpose of this document is to summarize the FL16A 4.0 SW Delivery content and impact.

2. CORRECTIONS 2.1 FSMF & AirScale

Pronto ID

Title

NA05973527

One TX failure in 2x2 MIMO configuration leading to a sleeping cell

NA05979758

[FL16A][AirScale] 1836 fault related alarm not shown in BTSSM with LTE1099 active

NA05984416 NA05990432

FL16A - [Airscale] eNB 131007 showing alarm (7654) Tx Input Overdrive alarm

NA05981865

[FL16A] LTE1891 - microDTX activated but performance counter M8010C93 is not present in eNB PM files

NA05984396

Logged MDT work properly a few hour only

NA05985351

ACLR degradation with FHEB Multicarrier(20MHz + 10 MHz)

NA05988185

[FSMr3] [AirScale] Follow up_for CAS-00453-K5R0 - SRAN Testbed: PM counter discrepancy during Control Plane Overload for SIGN_CONN_ESTAB_REJ_HIPRIO

NA05986755

LTE_5240a S1 HO counter abnormal increase after FL15a 1.3 upgraded

NA05964910

ToP Sync lost in FSMF - FL16

NA05977483

[AirScale] MTRACE Jobtype=TraceOnly. Megaplexer traces only have S1Paging&X2HORequest, no normal call traces

NA05988935

System Module Failure (4019) on FDD 4G Site

NA05990798 PR206660

SPS-config release IE is occasionally included in RRC Reconfiguration message

NA05991019

Long time need when Target Cell Copy in same eNBs

NA05990959

Airscale - ABIA Subunit lost of FID 4341 and BTS reset required of FID4001 during service (FL16A_ENB_0000_001183_000000)

NA05989381

[AirScale] CELL FAULTY (TRSHId:4261000:Cell disabled due to unknown problem) after SW Upg

NA05973320 NA05990405

ABIA-2 module auto reset (not in use)

NA05978903

CA_SCELL_CONFIG_FAIL Increasing for BW B13(5Mhz), B2(20MHz), B29(10MHz)

NA05993626

[FL16A MP0.1 ENB_0000_000860_000018_LGU+] MDT RLF work properly a few hours only after DU Reset

NA05988671

No correct status of RimStatus in LNADJ object

CAS-00983-V2B5

FL16A 2.0 upgrade KPIs degradation

NA05994951

Incorrect labelling on FHED.

CAS-11453-N3S6 NA05991935 NA05998539

UE context fails and ERAB drop rate trending up on 131597 Frisco Central the past 48 72 hours


© Nokia 2017

NA05983644

[AirScale] X2 Links shows unavailable on MNL03524

NA05991235

eNB SW fallback automatic and fault 4082 reported

PR202738

[LTE2057] LNHOIF-iFPrio is unable to set blank(Default) even if it’s without the group of "fixed order within group" profile

PR203499

Handovers with Rel-11 UE with UM bearers not working

PR206327

System Module failure, Unit: 1817ASIA1

PR206949

LTE2824: SIB2 incorrectly filled with extended bands when actMFBI is active

PR202108

[FL16A 3.0][AirScale] Diagnostic Files collected during night run

PR204519

[LTE1130] Interaction with LTE1638 - RSTD meas gap offset conflicting with SR accepted without resource reconfiguration

PR201691

Wrong values of PDCP_DATA_RATE_MEAN_DL_QCI_1

PR208962

RET port is not visible for FRIE in ALD tab in site manager

PR209405

Cells went down after running mobility patter with 3 bands B13/B4/B2 open

PR207617

Parameter maxBitrateUl limits ULCA max throughput

PR208575

rrcGuardTimer (LTERLCR-16109) parameter update applied to UE only after a BTS reset

PR210569

RET that is directed connected to FRLB is not detetced by checking AISG and DC in RET port

PR212435

[LTE2276] Scell was not configured although A3 measurement report was received right after Intra-eNB handover

PR210927

[FL16A] RRC guard timer parameter causes plan validation to fail in SW Loads prior to FL16A MP3

PR212182

[LTE1092]UL Scell was not activated ever in case of UL UDP only after scell re-addition procedure

PR213143

[FL16A] Cell specific PDCCH aggregation limitation not working properly

PR213444

LTE495 OTDOA: online disabling of OTDOA does not work

PR214052

[Airscale]M8051C118 "Average number of UL CA UE with one activated Scell" growing gratuitously during overnight test run

PR213575

[AirScale]ERR/LFS/LinuxSyslog, kernel: [ 2362.455577] emtimer: no free descriptors

PR214194

Set console uart flag on AirScale BTS to factory settings

NA05990025

[AirScale] no DL SCell scheduling on 40M CA

CAS-12093-K9T6

why eNB processing of the plans is corrupting its commissioning (this eNB SEM and SW)

PR213345

After upgrade cells down with "BTS Config error (Not enough HW for LCR) (1868)" when UlCoMp is Enabled

PR212575

[FL16A] [FSMF] BTS Site Manager Loses TRS Info

PR205562

KPI : Unexpected ‘no TX power in internal filter block’ alarm raised on FHEL

PR213992

Unsupported CPRI-A RRH - B4 2x40-AWS - Comcode 201351640

PR206231

[Airscale], eNB "sleeping" after manual BBU crash and recovery

PR214325

SVM-34978: tcpdump ≤ 4.8.1 - Multiple Vulnerabilities - 4.9

NA05981921

Ragged statistics on LTE

NA05991284

BTS,SW,SIGN_CONN_ESTAB_FAIL_OVLCP


© Nokia 2017

NA05987242

TRS configuration lost

NA05969214

With LTE1103(Load Based Power Saving)enabled,cells do not switch on at the end of energy saving period

NA05994788

Site Reset - BTS reset required (4001) triggering on lot of FL16A 0.4.2 Sites

CAS-12122-J5M5

Antenna ID List mismatched with Scanned antenna line.

PR216269

After resetting enbs, Cell become disable with "Invalid Frequency Channel error"

2.2 FSME Pronto ID

Title

NA05990798

SPS-config release IE is occasionally included in RRC Reconfiguration message

NA05994951

Incorrect labelling on FHED.

NA05967694

Rach ST degradation JEC0318 and JEC0321

NA05982648

1x UPG to FL16A failed from FL15A

NA05989381

[AirScale] CELL FAULTY (TRSHId:4261000:Cell disabled due to unknown problem) after SW Upg

NA05990580

FL16A MP2.0 outage of FSME eNB during/after sw dl via SWM

NA05984175

FL15A 1.3 After CM plan executing and e-NB reset, NTP and Clock missing alarm persistent.

PR214325

SVM-34978: tcpdump ≤ 4.8.1 - Multiple Vulnerabilities - 4.9

NA05991284

BTS,SW,SIGN_CONN_ESTAB_FAIL_OVLCP

3. NEW / CHANGED FUNCTIONALITY ID

Feature Name

Remark

CRL-13575 LTE2270

TDD-FDD inter eNB CA configuration for SIMO cells

FSMF only change. This change extends FDD-TDD inter eNB CA as defined in LTE2270 to support SIMO (1Tx/2Rx) on FDD and TDD side.

CRL-15769

AirScale System Module operating temperature increased up to +60C

CRL-15769

AirScale HW new version 473098A.102 AMIA AirScale Subrack

CRL-15863

AirScale HW new versions ASIA ABIA

CRL-16492

Allow 'dual carrier' to be configured on AirScale for different 3GPP band classes

LTE2763

Fronthaul Passive WDM


New ASIA system modules 473095A.202 and 473095A.203. New ABIA baseband module 103.

AirScale only feature.

© Nokia 2017

ID

Feature Name

Remark

LTE3302-A-f

Partial implementation of LTE3302 Concurrent LTE-CDMA operation for CPRI-A RRHs

AirScale only feature. This change enables XL Cell Sets to be used on AirScale BBU with FDD CPRI radios. An XL Cell set is required when the capacity required for a group of radios attached to an ABIA exceeds that ABIA's DSP capacity. The XL Cell set supports such configurations by splitting the Cells across two ABIAs while having physical connection to only one of the ABIAs.

LBT4368-A

Improvement of M8012C25 MAX PDCP DL THROUGHPUT counter

FSMF only change. Please refer to the chapter: 7.3.17 Corrected counters: M8012C20, M8012C25, M8012C26, and M8012C143

4. RESTRICTIONS 4.1 Restricted Released Features ID LTE1092

Feature Name Uplink Carrier Aggregation – 2CC

Remark FSMF only change. Interworking LTE1092 Uplink Carrier Aggregation - 2CC with LTE2305 Inter eNodeB Carrier Aggregation is not supported.

4.2 Other restrictions DHCP Lease Renewals (Flexi & AirScale) The UHEF and UHEC radios have an issue where they do not renew their IP address from the DHCP Server on the BBU. As a result, there is a low probability of a 3-5 min outage for one or two radios per radio reset or per radio link loss occurrence. When the IP Address DHCP Lease for this radio runs out (after 24 hours of use), the DHCP server in the BBU may consider the IP address as available for assignment to any other device, even though it is still being used by the affected radio. At any next radio reset or optical link loss & recovery within the eNB, the DHCP server may consider allocating the “unallocated IP” being used by the radio, but will first attempt to verify that the IP is not being used. The Probability is Low, but not zero, that the DHCP server is not able to verify the IP address in use. For this case, the DHCP server may assign the in-use IP to a second radio; most likely resulting in one, or at most two, radios losing heartbeats and incurring a 3-5 min outage. DHCP Lease Time (Flexi & AirScale) The affected radios may stop renewing their DHCP lease after 1000 renewals (which is equivalent to 500 days). This may result in a 3-5 min outage per affected radio which has not been reset in the last 500 days. The affected radios are: the NG2 family (UHIA, UHLA, UHMA, UHID), the AR1.0 family (UHFA, UHBA, UHEC, UHEF, UHIE, UDFA, UDIA, UDBA, UDLA, UDCA), and the NG3 family (UHHA, UHFB).


© Nokia 2017

Radio Detection (AirScale) The UHBB and UHBC radios do not send correct CPRI Control Words, preventing the radio from being detected by the Nokia BBU. An FPGA fix has been developed. However, the radio must be upgraded with this FPGA fix prior to migrating to the Nokia BBU. Specifically, before migrating any eNB to the Nokia BBU, the affected RFMs must be upgraded to a specific build of LR16.1 (see specific required build info below) while connected to an fALU BBU first, before moving to the Nokia BBU. • ENB_LR1601_D010A_E00405 or later if on the FOA load line (UHBB or UHBC) • ENB_LR1601_D0200_E00580 or later if on the CL1 load line (UHBB or UHBC) SFP Swapping (AirScale) The affected radios have an issue where, after swapping the radio SFP, the radio SFP monitoring tool still shows the data for the previous SFP until the radio receives a unit reset. As a result a radio reset after SFP swap is Mandatory. The affected radios are: the NG2 family (UHID, UHLA, UHMA, UHIA), the NG3 family (UHHA, UHFB), OEM1 (UHBC, UHBB), and for up to 60 secs, the MH Asset (UHFA, UHBA). Radio Detection (Flexi & AirScale) A radio issue in the UHEF and UHEC radios’ DHCP Client prevents the affected radios from being detected by the Nokia BBUs. Specifically, before migrating any eNB to the Nokia BBU, the affected RFMs must be upgraded to a specific build of LR15.1 (see specific required build info below) while connected to an fALU BBU first, before moving to the Nokia BBU. • ENB_LR1501_D030A_E01142, or • ENB_LR1501_D037A_E01190, or • ENB_LR1501_D037A_E01192 Optical Cable Moves In Between eNBs Within 30 seconds (Flexi & AirScale) There is a Constraint where the operator must wait 30 seconds after disconnecting a radio’s CPRI link from the source BBU prior to Re-inserting the radio’s CPRI link in a different target BBU (when moving radios across eNBs). Failure to abide by this constraint may result in an additional 30 seconds of outage on the radio being moved and an unexpected two and a half minute outage on one other radio in the target BBU. This constraint applies to all CPRI-A radios. ALD Software Download (Flexi & AirScale) If a download operation with incorrect ALD software is attempted on the affected radios, the operation will take around 20 mins before a response is provided via the generation of an 1806 “Communication Failure” alarm. A manual reset of the radio initiated by the operator is required to clear this alarm. A re-execution of the download operation with the correct ALD software would then be required. The affected radios are: the NG2 family (UHID, UHIA, UHMA, UHLA), and the ASB family (UHEA, UHFD, UHGA, UHEB, UHGB, UHLB, UHLC, UHNA). ACF File Download (AirScale)


© Nokia 2017

There is a constraint for the UHFB and UHED that in the case of an apparent failed ACF download, the operator will be required to execute a RET calibration operation. Failure to do this will result in the possibility of an uncalibrated RET after the ACF download. IP Addressing (Flexi & AirScale) CPRI-A radios sometimes use an IP Address of 192.168.255.1 which is already allocated in the Flexi & AirScale eNBs for connections from other technology radios and the BTSSM (and other tools). This causes two issues: 1) IF CPRI-A and other technology radios are mixed in some combinations on the same eNB, then the other technology radios may disconnect. As a result, there is a constraint that some Mix of RF Technologies as listed below is not supported until FL17.  CPRI-A/ OBSAI mixed RF technology on different BBU boards for AirScale and FSIH is not supported until FL17.  CPRI-A/ Nokia CPRI mixed RF technology on different BBU boards for AirScale, FSIH, and FSMF is not supported until FL17.  CPRI-A/ CPRI-Ir mixed RF technology on different BBU boards for AirScale, FSIH, and FSMF is not supported until FL17. 2) IF CPRI-A radios are used AND If Ethernet Port Security is turned OFF in the eNB (either FSMF or FSIH), then any LMP Tools, including the BTSSM, will disconnect. As a result, there is a constraint that:  Ethernet Port Security must remain ON until LTE3266 for FSMF and FSIH eNBs. Radio Detection (AirScale) The UHFD radio’s factory software load has an issue in the CPRI Control Word generation function which prevents the UHFD radio from being detected by the Nokia BBUs. Specifically, before migrating any eNB to the Nokia BBU, the affected RFMs must be upgraded to a specific build of LR15.1 (see specific required build info below) while connected to an fALU BBU first, before moving to the Nokia BBU. • ENB_LR1501_D030A_E01142 Radio Alarm Rate (AirScale) For the affected radios, it is possible, but very unlikely, that alarm events which exceed a rate of 10 events per 5 seconds from one of the affected radios may not be reported in the alarm event stream to the BBU. The affected radios are: the UHLB, UHFD, UHLC, UHFF, and UHCB. Optical Cable Swaps on Same BBU (Flexi & AirScale) There is a Constraint for all CPRI-A radios where the operator must wait 30 seconds after disconnecting two or more radio CPRI links from a BBU prior to reinserting the radio CPRI links in to different ports on the same BBU. Failure to abide by this constraint may result in the moved radios going off air and remaining in an off-air state until the operator executes a Site Reset. Amphenol Multi-RET Tilt to Zero (AirScale)


© Nokia 2017

The affected radios, when connected to the Amphenol Multi-RET, require a two step operation to change the Tilt from any value greater than 1 to 0. A Tilt command setting the Tilt to1 is required first, followed by a second Tilt command to set the Tilt to 0. Failure to use the two step operation for setting the Tilt to 0 may result in the generation of a 4239 alarm, which requires a manual reset of the radio to clear the alarm. The affected radios are: the UHIA, UHLA, UHID, and the UHMA. Radio LEDs (AirScale) The LEDs on the affected radios do not conform to the standard Nokia LED indication. There are six LEDs on the affected radios instead of the customary single LED. The six LEDs are labeled: RUN, ALM, ACT, CPRI0, CPRI1, and VSWR. However, the synthesized LEDs on the BTS Site Manager GUI do conform to the standard Nokia LED indication. The affected radios are: the UHMB, UHHB, and the UHAA. Rx Blocking (AirScale) The UHIA and UHID radios fail Rx Blocking Sensitive Requirement by ~2 dB. Up to 2 dB degradation in required sensitivity is seen for the case where there is a blocker within 2 dB of specified blocking amplitude within 7.5Hmz from wanted signal edge (Test Case: The blocker is 5MHz FRCA1-3 uplink signal offset 7.5MHz from wanted signal edge). If the blocker is > +/ - 2 dB from specified blocking level, sensitivity meets requirement. Low Voltage Alarm (AirScale) The UHFB and UHHA radios do not report a low voltage alarm for low voltage scenarios. Radio Detection (Flexi & AirScale) The UHED does not support Line Rate 3 while in 2G mode prior to RF SW Image z0o_xxn0.ecr (XXN0). This can cause detection with the Nokia BBU to fail (LTE BBUs do not support rate lower than rate 3). A new RF SW Load was generated and adopted within the factory in 4Q2105 which supports Line Rate 3 while in 2G mode eliminating this issue. For radios loaded with a RF SW Image prior to this image, and which are in 2G mode: they must be upgraded to the newer RF SW image, OR must be changed from 2G mode to 4G mode, prior to Nokia BBU Migration. There are three options for achieving this: 1. Connect the radio to a former ALU BBU (excluding eCCM2-HR). Once it is detected, it will automatically be changed to 4G mode, and the radio can be moved to an Airscale or FSMF (after a 30 second delay after disconnection). 2. Connect to the radio via an Ethernet/ Serial connection and manually change the mode from 2G to 4G and then reset the radio. 3. Return the radio to the factory for an RF SW Image upgrade (z0o_xxn0.ecr (XXN0)). Overcurrent Alarm Generation (Flexi & AirScale)


© Nokia 2017

The UHED ALD Overcurrent Behavior, including radio protection, is normal; except that the radio does not generate an Overcurrent Alarm. Radio LEDs (Flexi & AirScale) The LEDs on the affected radios do not conform to the standard Nokia LED indication. However, the synthesized LEDs on the BTS Site Manager GUI do conform to the standard Nokia LED indication. The affected radios are UHED, UHEE, UHDA, UHDB, and UHEG. Hot remove/insert procedure (Flexi and AirScale) Hot remove/hot insert procedure is not working correctly. After hot remove and then hot insert of radio module with different fiber length calls on random cells can be unavailable. The same may happen during Upgrade after SWDL. As a workaround an additional reset is needed. dlCarFrqEut parameter issue (Flexi) MRBTS/LNBTS/LNCEL/IRFIM – dlCarFrqEut can be set to too high value in the BTS Site Manager. BTS SM accepts the parameter and activates the configuration without any errors/faults after which Cell reconfiguration data distribution failed alarm is raised. In FL15A and FL16, this falsely configured parameter did not cause any harm, i.e. cells are on air and eNB fully functional. Thus, the problem can be visible after SW upgrade. The value of this parameter should be checked manually by operator according to 3GPP 36.331 chapter 6.4. Caution is advised when administering this parameter. Security GW rehoming During Security GW rehoming process (changing of the IP mapping) after provisioning via CM site loose TRS commissioning and only local action can be executed. As a workaround operator should disable TWAMP. UHIC - unit autonomous reset issue For a long running configuration with UHIC radio module and error: Unit autonomous reset as recovery action (0010) can occur. Problem is also occasionally visible during the snapshot collection. It can cause a call drop and temporary loss of service. System recovers by itself. Cell reconfiguration data distribution failed (6257) for SyncHub configuration For configurations, which are using LTE2305: Inter-eNodeB Carrier Aggregation for 2 Macro eNodeBs it was reported that after multiple reset of the synch slave can cause an error Cell reconfiguration data distribution failed (6257) on the synch master. Some of the cells on the synch master can get disabled. The workaround for such case is a reset of the eNB. Antenna Line Device Failure (1806) for FSME sites After recommissioning of the site the alarm 1806 ' Antenna Line Device Failure' can be displayed for some of the MHAs. Case is occasional and can be recovered by eNB reset.


© Nokia 2017

5. RELEASED OBJECTS 5.1 Flexi Multiradio BTS SW update delivery

FL16A P8/C5

FL16A 0.1

FL16A 0.2

FL16A 0.3

Delivery date

16-Sep-2016

04-Oct-2016

11-Oct-2016

21-Oct-2016

Software Item

Software File Name

BTS Site Manager FL16A/FSMF

FL16A_BTSSM_0000_000237_000000.zip

BTS Site Manager FL15A/FSME

FL15A_BTSSM_0000_000164_000000.zip

Golden SCF

Golden_SCF-FL16A-ENB_0000_000457000000-onwards_2016-06-29.zip

eNB

FL16A_ENB_0000_000833_000086_release_ BTSSM_downloadable.zip


FL16A_BTSSM_0000_000237_000000.zip


FL15A_BTSSM_0000_000164_000000.zip

Golden SCF FSME

Golden Config FL15A_ENB_001030_28onwards_2015-09-02.zip

Golden SCF FSMF

Golden_SCF_2016-08-17-FL16A-ENB-833onwards

eNB



FL16A_BTSSM_0000_000237_000000.zip


FL15A_BTSSM_0000_000164_000000.zip

Golden SCF FSME


Golden SCF FSMF


eNB



FL16A_BTSSM_0000_000237_000000.zip


FL15A_BTSSM_0000_000164_000000.zip

Golden SCF FSME


Golden SCF FSMF



© Nokia 2017

SW update delivery

FL16A 1.0

FL16A 0.4

FL16A 1.1

FL16A 2.0

Delivery date

31-Oct-2016

04-Nov-2016

14-Nov-2016

28-Nov-2016

Software Item

Software File Name

eNB



BTS Site Manager (ltesdkroot)_FL16A_BTSSM_0000_000248_00 0000.zip



Golden SCF FSME


Golden SCF FSMF

GoldenConfig-FL16A-ENB-1100-onwards2016-09-29.zip

eNB



FL16A_BTSSM_0000_000237_000000.zip


FL15A_BTSSM_0000_000164_000000.zip

Golden SCF FSME


Golden SCF FSMF


eNB


BTS Site Manager FL16A FSMF&AirScale




Golden SCF FSME


Golden SCF FSMF


eNB




BTS Site Manager FL15A FSME



© Nokia 2017

SW update delivery

FL16A 2.1

FL16A 3.0

FL16A 4.0

Delivery date

05-Dec-2016

12-Jan-2017

27-Feb-2017

Software Item

Software File Name

Golden SCF FSME


Golden SCF FSMF


eNB






Golden SCF FSME


Golden SCF FSMF


eNB






Golden SCF FSME


Golden SCF FSMF


eNB






Golden SCF FSME


Golden SCF FSMF


eNB



© Nokia 2017

5.2 NetAct SW update delivery

Delivery date

Software Item

Software File Name

FL16A 1.0

31-Oct-2016

NetAct Validator

netact-PPLTE16AMP1-5-disc1.iso

FL16A 2.0

28-Nov-2016

NetAct Validator


FL16A 2.1

08-Dec-2016

NetAct Validator


FL16A 3.0

12-Jan-2017

NetAct Validator


FL16A 4.0

27-Feb-2017

NetAct Validator


6. SW DOWNLOAD AND ACTIVATION TIMES FL16A 4.0 can be background downloaded to the FCM prior to activation. Activation of the eNB software will cause momentary loss of service in the serving cells as the FCM will be reset. The rough SW download and activation times are:

SW SW SW SW

The rough SW download and activation times download to eNB with FSMF download to eNB with FSME download to eNB with AirScale activation (including eNB reset), causing temporary loss of service

~ 15 min ~ 40 min ~ 13 min ~ 7 min

7. EFFECTS ON OPERATOR 7.1 AirScale introduction in FDD-LTE16A FDD-LTE16A is introducing new Nokia AirScale base station with the following components: - AirScale System Module Indoor - AirScale RRHs  This Release Delivery provides the support for AirScale RRHs (FRIJ and FHEL) which can be integrated with FSMF System Module.  Subsequent FDD-LTE16A Release Deliveries (FDD-LTE16A MP) will expand its support to AirScale System Module Indoor (planned general availability in November 2016). 7.2 Phase-Out of FSME system module FSME system modules are now under phase out process. The FL15A is the last release handling FSME corrections. This delivery contains the same FSME SW level: FL15A_ENB_0107_001818_000000. 7.3 KPI changes Corrected counter: M8006C270 ERAB_REL_ENB_RNL_RED_QCI1 Release where the change will be introduced: FL16A 1.0 (FSME & FSMF) NE SW version: FL16A, FL15A, FL16 FL16A 4.0 Release Summary and Impact - Page 16/29 Version 1.0 Confidential

© Nokia 2017

Relation to features or corrections: NA05954210: When a2RedirectQci1 = disabled, Inter-RAT redirection is triggered before ERABReleaseResponse for QCI1 and M8006C270 is incremented Short description / Expected impact: Inter-RAT redirection is triggered despite a2RedirectQci1 = disabled. Counter M8006C270 is increased despite a2RedirectQci1 = disabled Reasoning why the change was made: In order to avoid unnecessary increase of counter M8006C270 system will not add frequency to target cell list if autoadapt is true and B2 measurement deactivation ongoing Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW Impacted counters/KPIs: M8006C270 eNB initiated QCI1 E-RAB releases due to redirect to another cell

Corrected KPIs: LTE_5571d E-UTRAN E-RAB QCI1 and LTE_5582b E-UTRAN QCI1 Release where the change will be introduced: FL16A 1.0 (FSME only) NE SW version: FL15A Relation to features or corrections: NA05941612: VoLTE Drop Ratio and Success Ratio (RNL with UE lost) -> degraded (on FSME (FL15A) and 800 Layer only) Short description / Expected impact: Operator specific QCI's are reported to M8006C176, which is QCI 1 counter. M8006C176 is showing a little bit too high values. Reasoning why the change was made: In order to avoid KPI degradation system will check whether the RB standardized QCI and if it is not, value is excluded from counters. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW Impacted counters/KPIs: LTE_5571d E-UTRAN E-RAB QCI1 with data in the queue drop ratio, RAN View, RNL Failure with UE Lost LTE_5582b E-UTRAN QCI1 E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost Corrected counter: M8001C44 PUSCH_TRANS_USING_MCS28 Release where the change will be introduced: FL16A 1.0 (FSMF) NE SW version: FL16A 4.0 Release Summary and Impact - Page 17/29 Version 1.0 Confidential

© Nokia 2017

FL16A Relation to features or corrections: PR182725: [FL16A][FSMr3] PUSCH_TRANS_USING_MCS28 counter is incremented by UCIonly reports Short description / Expected impact: PUSCH transmission using MCS28 (M8001C44) counter is incremented although there is no transmission with MCS28. The counter value is corresponding to amount of UCI only reports with MCS29. Reasoning why the change was made: In order to correct the fault PR182725 it was necessary to change the implementation so that the PUSCH_TRANS_USING_MCS28 is not updated while uciOnly transmission is sent. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW Impacted counters/KPIs: M8001C44 PUSCH transmissions using MCS28 Corrected counters: M8006C255 and M8006C176 Release where the change will be introduced: FL16A 2.0 NE SW version: FL16A Relation to features or corrections: NA05958413: High SIP 481 Failures in Nokia Markets Short description / Expected impact: QCI1 UE is released with incorrect reason (RNL: UE Inactivity) when out-of-sync is detected and T311+T310 is longer than regular inactivity timer. If UE is in out-of-sync-final - MAC_RadioLinkInd with out-of-sync-final received - UEC moves UE to idle and starts T_RLF (which will release UE with proper release cause when expired). If afterwards – before T_RLF expiration - a second MAC_RadioLinkInd with out-of-sync-final is received UE is released immediately. UE is released with wrong cause: "radioNetwork: user inactivity" istade of "radio connection with ue lost". Slight increase in VoLTE DCR after the correction due to some release due to user inactivity will be counted as drop due to radio Reasoning why the change was made: It was necessary to check if RLF timer is running. And if it is then ignore seconde UEC_UEM_RADIOLINKSTATUS_OUTOFSYNCFINAL message Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: FL16A 4.0 Release Summary and Impact - Page 18/29 Version 1.0 Confidential

© Nokia 2017

VoLTE DCR counters/KPIs Corrected counters: M8048C2 Release where the change will be introduced: FL16A 2.0 NE SW version: FL16A Relation to features or corrections: PR192792: LTE2766: M8048C2 is not always counting correctly. Short description / Expected impact: LTE2766 counter M8048C2 was incremented too often in case of failed Initial Context Setup or GSM Redirect. If there were failed setups or redirects, counter M8048C2 would have incorrect value in given PM time interval. Reasoning why the change was made: Problem was solved by proper handling of failed procedures. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: M8048C2 E-RABs Normal releases per Profile Corrected counter: M51132C3 Release where the change will be introduced: FL15A 1.5; FL16A 2.0 NE SW version: FL15A Relation to features or corrections: NA05945312: TWAMP/QoS problem Short description / Expected impact: TWAMP packet loss is seen in FTIB eNode, Counter M51132C3 increment is seen. Default route added during start up is not getting deleted even after the route for configured default gateway gets added once BFD is up in FTIB units. Hence two defaults routes in the linux routing table in FTIB can be seen. This leads to a scenario were all SCTP packets get lifted to host and gets forwarded in slow path without the route getting configured in fast path. Host processor gets overloaded with the task of SCTP forwarding and as a result TWAMP packets are not picked for processing before the socket wait time out and the packets are considered as lost. Reasoning why the change was made: Change was made to remove the default gateway when a new default GW is added based on BFD status. FL16A 4.0 Release Summary and Impact - Page 19/29 Version 1.0 Confidential

© Nokia 2017

Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: M51132C3 lostTwampMessages Corrected KPI: LTE_5143a Release where the change will be introduced: FL15A 1.5; FL16A 2.1 NE SW version: FL15A Relation to features or corrections: NA05956078: Degradation in RRC Conn re-est SR seen with the P8 candidate load Short description / Expected impact: The average observed RRC Conn rest SR (KPI LTE_5143a) can be lower than on previous releases. It is not predictable to quantify the improvement. This depends on occurence of scenario UEs performing RRC Conn re-establishment procedure with RLF triggered handover in high mobility conditions. From the end user perspective short disconnection of UE after failed reestablishment can be observed before this correction is applied. Reasoning why the change was made: Change was made to change the behavior so that when the eNB_1 receives X2:RlfIndication for UE from eNB_3. Flag m_supportHoRetry will be set to true only for this specific case Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: M8008C4 Number of RRC Connection Re-establishment attempts M8008C5 Number of successful RRC Connection Re-establishment procedures LTE_5143a Total E-UTRAN RRC Connection Re-establishment Success Ratio Corrected KPI: LTE_5700a Release where the change will be introduced: FL15A 1.5; FL16A 2.1 NE SW version: FL15A Relation to features or corrections: NA05960891: Increase of LTE_5700a after activation of LTE2006 FL16A 4.0 Release Summary and Impact - Page 20/29 Version 1.0 Confidential

© Nokia 2017

Short description / Expected impact: After activating LTE2006 on eNB an increase of KPI LTE_5700a can be observed. Reasoning why the change was made: The observed difference is that in case of actFlexScellSelect=true the PUCCH resources are distributed to the SCells by MAC-PS whereas in case of actFlexScellSelect=false the PUCCH resources are distributed by C-Plane. In case of C-Plane distributes the resources we have a fixed distribution. I.e. first SCell gets the first half of the available PUCCH resources and second SCell gets the second half (In case of one SCell this SCell gets all resources). In case of MAC-PS does the distribution MAC-PS selects one of the resources assigned to the UE and assigns this resource to the SCell the UE is configured for. So in the latter case the number of resources assigned to an SCell is lower. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: LTE_5700a E-UTRAN SCell Scheduling Blocking Rate due to Conflicts on PUCCH Format 1bwcs Resources Corrected counters: M8029C* Release where the change will be introduced: FL16A 3.0 NE SW version: FL16A Relation to features or corrections: NA05982894: M8029C* TIMING_ADV_BIN_* Raw Counter Abnormal Spikes NA05929040: hourly spikes in Higher Timing Advance Bins while no increase in Hourly Traffic or RACH Attempts Short description / Expected impact: With tis correction raw counters TIMING_ADV_BIN_* will not report abnormal counter spikes. Reasoning why the change was made: Histogram counter value calculation did not work if the initial Time Alignment Command was missing. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: M8029C* Timing Advance bin*


© Nokia 2017

M8006C245 increase on FSME sites Release where the change will be introduced: FL16A, FL16 NE SW version: FL16A, FL16 Relation to features or corrections: NA05963065: FL16 and FL16A - M8006C245 increase on FSME sites Short description / Expected impact: After upgrade to FL16A, some FSME sites can show increase in M8006C245 (ERAB setup failures due to transport no enough resource). After site reset, M8006C245 drops to 0 for some time. But later on M8006C245 starts to increase again. Reasoning why the change was made: Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: M8006C245 Failed setup attempts for initial E-RABs due to "Transport Network Layer Cause - Transport Resources Unavailable" Corrected counter M8013C33 Release where the change will be introduced: FL16A 4.0, FL16 7.0 NE SW version: FL16A, FL16 Relation to features or corrections: NA05988185: [FSMr3] [AirScale] Follow up_for CAS-00453-K5R0 - PM counter discrepancy during Control Plane Overload for SIGN_CONN_ESTAB_REJ_HIPRIO Short description / Expected impact: The M8013C33 counter has been corrected and delivered for C-Plane. Reasoning why the change was made: Counter SIGN_CONN_ESTAB_REJ_HIPRIO (M8013C33) is incremented too many times without any reason during timeout for RRC_CONNECTION_SETUP_COMPLETE message or incorrect RRC_CONNECTION_SETUP_COMPLETE message. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: FL16A 4.0 Release Summary and Impact - Page 22/29 Version 1.0 Confidential

© Nokia 2017

Impacted counters/KPIs: M8013C33 Number of rejected Signaling Connection Establishment Requests for high priority calls -> decrease LTE_5391a Total E-UTRAN RRC Connection Setup Rejection Ratio for high priority calls -> decrease

Corrected KPI LTE_5240a Release where the change will be introduced: FL16A 4.0, FL16 8.0 NE SW version: FL16A, FL16, FL15A Relation to features or corrections: NA05986755: LTE_5240a S1 HO counter abnormal increase after FL15a 1.3 upgraded Short description / Expected impact: LTE_5240a S1 HO counter abnormal increase after upgrade to FL15A 1.3. Reasoning why the change was made: The abnormal increase of this counter was caused by X2 link unavailable after eNB Reset. The root cause for such behavior was a race condition during eNB startup. During the TUPc startup there is a short period of time when the X2 socket is open for incoming connections but the common signaling handler is not yet registered. This makes it impossible to finish the X2AP link setup procedure so TUPc drops such connections. However, this rollback mechanism relied on associationId mapping that is only added after successful link setup. This resulted in hanging resources in the SCTP stack. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: LTE_5240a E-UTRAN HO Attempts, inter eNB S1 based -> decrease

Corrected counter M8012C143 Release where the change will be introduced: FL16A, FL17 NE SW version: FL16A Relation to features or corrections: PR201691: Wrong values of PDCP_DATA_RATE_MEAN_DL_QCI_1 [FL17] Short description / Expected impact: UL/DL counter values were different.


© Nokia 2017

Reasoning why the change was made: The root cause of this problem was that the sdu size used for counter value calculation was wrong. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: M8012C116 PDCP UL throughput Mean for QCI 1-> decrease Corrected counter M8051C118 Release where the change will be introduced: FL16A 4.0 NE SW version: FL16A Relation to features or corrections: PR214052: [FL17][Airscale]M8051C118 "Average number of UL CA UE with one activated Scell" growing gratuitously during overnight test run Short description / Expected impact: M8051C118 counter for the Intra-eNB handover with 3CC carrier aggregation in FL17 AirScale will show lower values. Reasoning why the change was made: M8051C118 "Average number of UL CA UE with one activated Scell" counter does not show reliable values. This counter was not decreased properly in some circumstances. It depended on flag isUlCa() which seems to be cleared earlier in the process of UE deletion. As a correction, a new dedicated flag was introduced. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: M8051C118 Average number of UL CA UE with one activated Scell LTE_5293c E-UTRAN average PDCP Layer Active Cell Throughput DL for QCI1 DRBs Corrected KPIs: LTE_5571d E-UTRAN E-RAB QCI1 and LTE_5582b E-UTRAN QCI1 Release where the change will be introduced: FL16A 1.0 (FSME only) NE SW version: FL15A Relation to features or corrections: FL16A 4.0 Release Summary and Impact - Page 24/29 Version 1.0 Confidential

© Nokia 2017

NA05941612: VoLTE Drop Ratio and Success Ratio (RNL with UE lost) -> degraded (on FSME (FL15A) and 800 Layer only) Short description / Expected impact: All the released active E-RABs (initiated by the eNB due to radio connectivity problems) with operator specific CQI QCI are reported by mistake to QCI1 counter (M8006C176 ERAB_REL_ENB_ACT_QCI1). There are no dedicated counters for that purpose available in the system. Reasoning why the change was made: In order to avoid KPI degradation system will check whether the RB standardized QCI and if it is not, value is excluded from counters. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW Impacted counters/KPIs: LTE_5571d E-UTRAN E-RAB QCI1 with data in the queue drop ratio, RAN View, RNL Failure with UE Lost LTE_5582b E-UTRAN QCI1 E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost M8006C176 ERAB_REL_ENB_ACT_QCI1 Corrected counters: M8006C176-M8006C180 and M8006C239-M8006C243 Release where the change will be introduced: FL16 7.0; FL15A 1.5 NE SW version: FL16; FL15A Relation to features or corrections: NA05972490: (TDD-LTE TL15A) The dropping rate of Counter is abnormal PR181615: QCI specific attempt and release counters not updated expected way Reasoning why the change was made: In cases: - When there is problem on the radio link (lower layers) and maximum number of RLC -

retransmission is exceeded, the eNB requests the affected UE to perform an intra cell handover. When this intracell handover does not succeed because of the already poor radio conditions and specific race conditions occur during the message processing it can happen that the UEs are released without special "abnormal release" treatment.

In the previous SW versions, the counters M8006C176-M8006C180, M8006C239M8006C243 were not incremented when the above-described scenario occurred. Short description / Expected impact: In the described failed intracell handover scenario, the eNB ‘memorizes’ the UE’s preceding lower layer problems, thus knowing that the intracell handover was originally triggered by bad radio conditions. When the resources are released after the failed intracell handover, the stored information of the UE’s preceding RLC problems allow the eNB to recognize the scenario as an ‘abnormal release’, hence the related counters are triggered. This will cause some increased values of counters and KPIs mentioned in Impacted counters/KPIs section, but it will not affect the end-user experience. FL16A 4.0 Release Summary and Impact - Page 25/29 Version 1.0 Confidential

© Nokia 2017

Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW UE dependency: Impacted counters/KPIs: Counters M8006C176-M8006C180 and M8006C239-M8006C243 LTE_5570b E-UTRAN E-RAB active drop ratio with data in the buffer due to RNL Radio Connection with UE Lost. - depends on (M8006C176-M8006C180) LTE_5571b E-UTRAN E-RAB QCI1 with data in the queue drop ratio, RAN View, RNL Failure with UE Lost - depends on (M8006C176) LTE_5581b E-UTRAN E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost depends on (M8006C176-M8006C180) LTE_5582b E-UTRAN QCI1 E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost - depends on (M8006C176) LTE_5583b E-UTRAN QCI2 E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost - depends on (M8006C177) LTE_5584b E-UTRAN QCI3 E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost - depends on (M8006C178) LTE_5585b E-UTRAN QCI4 E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost - depends on (M8006C179) LTE_5586b E-UTRAN non GBR E-RAB Retainability Rate, RAN View, RNL Failure with UE Lost - depends on (M8006C180) Corrected counters: M8012C20, M8012C25, M8012C26, and M8012C143 Release where the change will be introduced: FL16 7.0 NE SW version: FL16 Relation to features or corrections: LBT4368-A: Improvement of M8012C25 MAX PDCP DL THROUGHPUT counter Reasoning why the change was made: PM Counter reported for M8012C25 MAX PDCP DL THROUGHPUT more than maximum theoretical value. The reason for misleading values for M8012C25 counter was RLC AM bearer related acks which were taken into account and were not possible to synch for the correct sampling period causing in some cases data shift to next sampling period and too high throughput values visible in the max count. Additionally, during the change there was a rounding errors found in the previous implementation which had caused too high values and correction for this error may impact values of other counters as well. Short description / Expected impact: With the change also counters related to RLC AM bearer are updated according to new data transmission and RLC layer acks are not considered anymore. User experience is not affected by this change. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW FL16A 4.0 Release Summary and Impact - Page 26/29 Version 1.0 Confidential

© Nokia 2017

UE dependency: Impacted counters/KPIs: M8012C20 PDCP SDU data volume on eUu Interface downlink M8012C25 PDCP Throughput DL Max M8012C26 PDCP Throughput DL Mean M8012C143 PDCP DL throughput Mean for QCI 1 7.4 Alarm Changes Corrected alarm: “Failure in replaceable baseband unit (6700)” Release where the change will be introduced: FL16A 0.3 (FSMF only) NE SW version: FL16A Relation to features or corrections: NA05957689: Failure in Replaceable Baseband Unit (6700) alarm after module block/unblock Short description / Expected impact: After upgrade and execution of cell block/unblock on FRHF alarm "Failure in replaceable baseband unit (6700)" is raised on FBBC. This alarm is visible permanently despite that the correction actions are already in place and problem is solved. Reasoning why the change was made: Fault 6700 was made transient in order to not cause any confusion. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW Impacted alarms: 6700 Failure in replaceable baseband unit Corrected alarm: “BTS reset needed (4001)” Release where the change will be introduced: FL16A 2.0 NE SW version: FL16A Relation to features or corrections: NA05966136: L7 cells went faulty with BTS reset required (4001) Short description / Expected impact: After commissioning unsupported configuration, cells are disabled with misleading alarm 4001 (BTS reset needed). Despite the alarm "BTS reset needed", reset does not recover the issue. Reasoning why the change was made:


© Nokia 2017

Bug in U-plane deployment corrected - restricted amount of cells than can have 4RX ULCOMP in a single BTS - in case too many such cells are commissioned, reasoning status "not enough DSP capacity" is reported, which to BTS operator is indicated as alarm 1868 (not enough HW for cell). For the case where 4RX ULCOMP cells are assigned to local mode BBU, validation is added that single BBU can't supported feature which requires 4DSP deployment, therefore also the same reasoning status is added. Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW Impacted alarms: 1868 Not enough HW for cell 4001 BTS reset needed Corrected fault: “High interference to UL subframe (6117)” Release where the change will be introduced: FL16A 2.0 NE SW version: FL16A Relation to features or corrections: PR187240: [FL16A] Fault 6117 is not raised. Short description / Expected impact: Operator is not informed about overload when eNB is in user plane overload. End user equipment is not attaches are rejected in case of in case of user plane overload. Reasoning why the change was made: Alarm 6117 has to be raised in case of U-plane overload Type of change: generic in the SW, license-based or activated by PRFILE: Generic in the SW Impacted fault: 6117 High interference to UL subframe

8. Piloting N/A

9. Appendices / References The software for the released products is available in NOLS. The newly released software can be downloaded from the direct links: Flexi Multiradio BTS LTE: https://online.networks.nokia.com/SWD/?access_key=MTI2Mjk3 NetAct PP: https://online.networks.nokia.com/SWD/?access_key=MTI2Mjk3 FL16A 4.0 Release Summary and Impact - Page 28/29 Version 1.0 Confidential

© Nokia 2017

After downloading the software it is important to generate SHA1 checksum for files and compare it with the one provided in the Installation Instructions document, this will ensure that the files were not corrupted during downloading.


© Nokia 2017

FL16A 4 0 Release Summary and Impact

Recommend Documents