LTE jj

7/17/2019 LTE jj

http://slidepdf.com/reader/full/lte-jj 1/96

LNT3.0 2.0 - <Delivery Content> © Nokia Solutions and Networks 2014Version 1.0Confidential

ContactContact your local Nokia Solutions and Networks support

Summary of changes:

16-7-2014 0.1 Creation date

21-7-2014 1.0 Approval date

<Delivery type>

< Base Stations ; Radio Controllers>< Flexi Mul ti radio BTS TD-LTE; LTE iOMS >< RL35 MP2><LNT3.0 2.0><Worldwide>

Document name:

Summary of corrections and enhancements

Impact Document

Release Notes

Installation Instructions

Verification Report

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and follow the recommendations forpower 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 weoffer, please contact us at Nokia Solutions and Networks for additional information.

7/17/2019 LTE jj


LNT3.0 2.0 - <Summary of Corrections and Enhancements> © Nokia Solutions and Networks 2014Version 1.0Confidential

1 (20)

Summary of Corrections and Enhancements

Id: LNT3.0 2.0Product Family: Base Stations

Radio Controllers

Product: Flexi Multiradio BTS TD-LTE

LTE iOMS

Release: RL35 MP2

Approval date: (21-7-2014)

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us in workingtowards a cleaner, safer environment. Please recycle product packaging and follow therecommendations 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 serviceswe offer, please contact us at Nokia Solutions and Networks for additional information.

7/17/2019 LTE jj



2 (20)

Table of Contents

1. Purpose ......................................................................................................................................................... 3

2. CORRECTIONS............................................................................................................................................ 3

3. New / Changed functionality ......................................................................................................................... 5

3.1 Released Features ............................................................ ..................................................................... .................. 5

3.2 Restricted Released Features .................................................................. ................................................................ 5

3.3 Not Released Features ............................................................................................................................................ 5

4. status legacy features ................................................................................................................................... 5

4.1 Released Legacy Features ...................................................................................................................................... 5

4.2 Restricted Released Legacy Features .............................................................................................................. ..... 15

4.3 Not Released Legacy Features ................................................................ .............................................................. 17

5. 3rd party corrections ................................................................................................................................... 17

6. Release objects........................................................................................................................................... 17

6.1

Flexi Multiradio BTS LTE and iOMS description .................................................................................... ................ 17 6.2 Released software versions .............................................................................................................................. ..... 17

6.2.1 eNB Software file list .................................................................... ..................................................................... ..... 17

6.2.2 iOMS Software file list .................................................................. ..................................................................... ..... 18

6.2.3 EPC Software file list .................................................................... ..................................................................... ..... 18

6.2.4 OSS Software file list ............................................................................................................................................. 18

6.2.5 Tested and recommended UE Software file list ..................................................................................... ................ 18

7. NOTES ........................................................................................................................................................ 19

7.1 Title: innofidei UE parameters setting .................................................................................................................... 19

8. Appendices / References ............................................................................................................................ 19

Contact:Contact your local Nokia Solutions and Networks support

Summary of changes:

<16-July-2014> 0.1 Creation date<21-July-2014> 1.0 Approval date

7/17/2019 LTE jj



3 (20)

1. PURPOSE

The purpose of this document is to give a brief summary on the ReleaseDelivery corrections content.

2. CORRECTIONS

List of corrections for RL35 MP2.

Problem ID Title

107203ESPE01RL60: UEContextModification(security key) procedure between the eNBand MME fails

107690ESPE01 [RL35 Main] occurred fault(4064) after reset BTS via power off/on

107858ESPE01Poster test scenarios not take effect after FSP2 external Memory testfailure

108122ESPE01[RL35 IR] System module fault (0010) or FBBA not detected after btsreset

108946ESPE01[RL35 IR]:Climate control profiling is auto enabled after enable anddisable it by SEM

109320ESPE01LNT3.1 Alarm flood of Failure in connection between BTS and iOMS or3rd party tool?

109576ESPE01 SEM report error after commissioning file active successful

112362ESPE04 [RL35 P8] can't establish the SSL connection after upgrade from RL25

113478ESPE04BTS Crash with RRU status still OK to access normally, BTS could notreset itself except repower on.

115623ESPE04Can’t detected FBBA2 and appeared 0010 alarm after UpgradeLNT3.0_ENB_1304_251_03 to LNT3.0_ENB_1304_273_00

136601ESPE02 0010&2002 alarm occurred and cell 3 crash

138723ESPE02 Lack of TRS PM counter(IP counter: Transport Ethernet interface AF4)

7/17/2019 LTE jj



4 (20)

139164ESPE02 Lack of TRS IP counter(Transport Ethernet interface AF)

140268ESPE02[RL35 Main]PM counter DATA_RB_STP_COMP Bigger thanDATA_RB_STP_ATT in 251_03

140445ESPE02BTS site manager don't show alarm information when enter an incorrectusrname and password.

140728ESPE02 modify PCI failed even though enableAutoLock=enable

46894ESPE05 [LNT3.0] Counter should be clear when changed VLAN ID

48011ESPE05 [LNT3.0][FIVE]SRS receive signal imbalanced

51057ESPE05[RL35 main] CC&S error with EU id : 441 (0x1B9) after delete config&trsfile

81251ESPE03[LNT3.0]TRS configuration missing after ENB upgrade fromLNT3.0_ENB_1304_243_02 to LNT2.0_ENB_9308_345_00

NA05634595 RL50 - FSMF fast tune does not work for SyncE, no alarm displayed

NA05640471NA05640471 (ENB)one NEW site of F band reported 0010 systemmodule failure alarm(7651)

115808ESPE04 [RL35 Main] FATAL Error during Stability test

NA05644907 LTE939 - Usage Based PDCCH Adaption for RL35 TDD sites

NA05652597(TDD LTE RL35 MP1.0)(LNT3.0_ENB_1304_251_02)SON,LTE eNBcannot process DHCP broadcast package with TTL=1

NA05656753 E NodeB fails to connect to DHCP using SON.

NA05664136 NA05664136 || VSWR Major alarm not reporting in RL35 LTE BTS

111434ESPE01 VSWR Major Alarm is not Auto Clear after return the jumper back.NA05670149 Degradation of main KPI's for neighbors sites after Power OFF/ON of

one TD-LTE eNB, Looks the site went out of synch

NA05678532 L23 TDD eNodeB with FSMF locking up requiring local reset to restoreservice.

7/17/2019 LTE jj



5 (20)

Note: Action of reconnecting the RF Antenna cable needs more than 3 minutes to cancel allVSWR related alarms after tuning VSWR Thresholds. This is expected result but not SW bug.

3. NEW / CHANGED FUNCTIONALITY

3.1 Released Features

NA

3.2 Restricted Released Features

NA

3.3 Not Released Features

NA

4. STATUS LEGACY FEATURES

4.1 Released Legacy Features

ID Feature Name Operator Hint

1S1/X2 DatapathManagement

2 S1 Flex

3S1, X2 and RRC CommonSignaling

4Multi-Operator Core

Network5

Radio Bearer and S1 BearerEstablishment and Release

7Support of Multiple EPSBearer

9 Service Differentiation

10EPS Bearers forConversational Voice

11Robust HeaderCompression

13 Rate Capping (UL/DL)

7/17/2019 LTE jj



6 (20)

20 Admission Control

22 Emergency call handling

27Open Loop UL PowerControl and DL PowerSetting

28Closed Loop UL PowerControl

30 CQI Adaption (DL)

31Link Adaptation By AMC(UL/DL)

37 Ciphering

38 Integrity Protection

39System InformationBroadcast

40Physical & TransportChannels

41 PDCP, RLC & MAC Support

42Support of DRX in RRCconnected mode

43 Support of 64 QAM in DL

45 Fair Scheduler (UL/DL)

46Channel Aware Scheduler(UL)

49 Paging

50 UE State Management

51Cell Selection andReselection

53Intra and Inter ENBHandover With X2

54 Intra-LTE Handover via S1

55 Inter-frequency Handover

56Inter RAT handover toWCDMA

68Support of Cell BasedLocation Service

69Transmit Diversity for Two Antennas

70Downlink Adaptive openLoop MIMO for Two

7/17/2019 LTE jj



7 (20)

Antennas

71 2-way RX Diversity (MRC)

78Flexi AC/DC With BatteryPower Module

79Flexi Indoor and outdoorCabinets

80 GPS Synchronization

97 Cell Radius Max 77 km

118Fast Ethernet (FE) GigabitEthernet (GE) Electrical

Interface119

Gigabit Ethernet (GE)Optical Interface

129Traffic Prioritization onEthernet Layer

131Traffic Prioritization on IPLayer (Diffserv)

132VLAN Based TrafficDifferentiation

138 Traffic Shaping (UL)

147 LTE Hardware Management

150LTE OAM Transport Layer

Security (TLS) Support

153 LTE BTS Site Manager

154SON LTE BTS AutoConnectivity

158NTP Clock TimeSynchronization

160Flexi Multiradio BTS 3GPP Antenna Tilt Support

187 Single TX Path Mode

423RRC Connection ReleaseWith Redirect

430DL power boosting forcontrol channels

432 Cell outage Detection

433 Basic LTE Cell Trace

442Network Assisted CellChange to GSM

450 MME capacity value change

7/17/2019 LTE jj



8 (20)

468 PCI Management

473 Extended DRX Settings

475 Automatic iOMS Resilience

482DNS Support for CertificateExamination managementdata

491FlexiPacket RadioConnectivity

492 ANR

502Cell Outage Triggered

Reset

513Support of SoundingReference Signal in TDDUpPTS

518 Operator specific QCI

522 S1 Partial Reset

527Distributed Resource Allocation Type 2

528Idle Mode Inter-frequencyMobility Management

539 Central ANR

540Sounding Reference Signalin Normal Frames

541 Dual Stream beamforming

550Radio Parameter OnlineChangeable

559SW monitoring Module forLTE

562CSFB to UTRAN or GERANvia redirect

570 Periodic UE measurements

571Controlled uplink packetsegmentation

593Security for Ethernet Portson FCT/FSM3

602Performance Management Administration

614 Distributed Site

622 Local Link Layer Security

7/17/2019 LTE jj



9 (20)

623 Crypto Agent

644 Configurable cell tracecontent

649QoS aware Ethernetswitching

651 Performance Monitoring I

653 LTE Operability Architecture

654LTE ConfigurationManagement

656 LTE Fault Management

657 LTE PerformanceManagement

663 GPS Location Retrieval

664LTE Transport ProtocolStack

665

LTE CertificateManagementLTE685: Infrastructures forCertification Authority (CA)and Registration Authority(RA)

666 LTE User AccountManagement

667LTE User Event LogManagement

679LTE Local User AccountManagement

681Windows 7 Support forElement Manager ClientSoftware

685

Infrastructures forCertification Authority (CA)and Registration Authority

(RA)

689 LTE IPsec Support

692 LTE Firewall Support

703Downlink Adaptive ClosedLoop MIMO for Two Antennas

720SON LTE BTS AutoConfiguration

724LTE Automatic NeighborCell Configuration

7/17/2019 LTE jj



10 (20)

735RRC ConnectionReestablishment

746 IP Based Filtering for BTSSite Support Equipment

747Support of UE RadioCapabilities

749 Link Adaptation for PDCCH

761

Advanced Target CellSelection and HandoverRetry for Intra-frequencyHandover

767Support of Aperiodic CQIReports

770Basic Performance CounterCollection II

771Optimization of Intra-LTEneighbor relations

775 SCTP Multi-homing (MME)

782 ANR - UE based

783 ANR interRAT UTRAN

788 Support of 16 QAM (UL),

793 Support of 16 QAM (DL)

796 iOMS Connectivity Increase

797 PM Counter Handover I

798 PM Counter Histograms I

805 PM Counter Capacity I

806 PM Counter Transport I

819DL Inter-cell Interference

Generation827 29 km Cell Range

829Increased Uplink MCSRange

830 LTE Automatic Lock

832TDD Cell Bandwidth - 20MHZ

835TDD Cell Bandwidth - 10MHZ

861TDD DL/UL Switching

2DL:2UL

7/17/2019 LTE jj



11 (20)

862TDD DwPTS, GP andUpPTS With SF

Configuration 7

875Different IP Addresses forU/C/M/S-plane

892TDD DwPTS, GP andUpPTS With SFConfiguration 5

893 ACK/NACK Bundling

895TDD Support for Random Access Preamble BurstFormat 4

905Non GBR QCI 5, 6, 7, 8 and9

906TDD DL/UL Switching3DL:1UL

911TDD Frame SynchronizedOperation

936 UL IRC receiver

940 SW Verification Agent

947Flexi Multimode SystemModule FSMF

947Flexi Multiradio SystemModule FSMF

949Flexi power distribution sub-module FPFD

950Flexi power distributorstand-alone FPFC

969Flexible SoundingConfiguration

971 Intra-LTE mobility offsets

972Flexi Baseband ModuleFBBA

999 Flexi RF Module 2300 6TXFZNC

1013Dynamic transmission modeswitch

1025DL beamforming intercellinterference generation

1034Extended Uplink Link Adaption

1035Outer Loop Link Adaptationfor PDCCH

1038 4/8Rx PRACH/PUCCH

7/17/2019 LTE jj



12 (20)

1111inter-cell load generation forPDCCH

914 Graceful cell shut down

784 ANR InterRAT GERAN

459LTE Timing AdvanceEvaluation

533 Mobility Robustness

1139 ZUC security algorithm

1222 SON Automation Modes

1045Full SON Support forDistributed Sites

1201LTE iOMS HW, HP BladeGen8

496 Support of QCI 2, 3 and 4

628FTIF Transport PDH /Ethernet

877 Adjustable PerformanceUpload

736 CS Fallback to UTRAN

495 OTDOA

1014X2 eNB ConfigurationUpdate

Online change TAC or Cell add delete will nottrigger X2 eNB configuration. Customerdocument need to be modified for thisrestriction.

953MDT (Minimization of DriveTest)

984GSM Redirect with SystemInformation

587Multiple GBR EPS Bearersper UE

1019 SON Reports

162 Cell Trace with IMSI

Released as radio-only feature. It's only testedin radio part

Operator Hint:Feature "Cell Trace with IMSI" can be used inan environment with supporting 3rd party tracetool and MME. Trace Viewer itself will notsupport LTE162 Cell Trace with IMSI in RL50.If MTRACE is configured (possible viaTraceViewer) than eNB will always send theCell Traffic Trace message to MME and

7/17/2019 LTE jj



13 (20)

provide respective results in eNB trace file.The feature can be activated/deactivated by

R&D flag in swconfig file with BTS reset.

140 Ethernet OAM (FSMr3)Not be able to execute LTE140 sincecustomer environment is not available

807-C

CRL0867 : Idle modemobility from LTE TDD toCDMA/(eHRPD, 1xRTT) -Done by LTE870-C (forRL35TD branch)

426-C

CRL0867 : Idle modemobility from LTE TDD toCDMA/(eHRPD, 1xRTT) -

Done by LTE870-C (forRL35TD branch)

870-C

CRL0867 : Idle modemobility from LTE TDD toCDMA/(eHRPD, 1xRTT) -LTE426,LTE807,LTE870(for RL35TD branch)

1013-bDynamic transmission modeswitch for TM3 and TM8

1473System Upgrade (TDDRelease)

1169DL TM8 based Dual User

Single Layer MU-MIMO

505Transport Separation forRAN Sharing

523Multi-layered Certificate Authorities

939Usage based PDCCHadaptation

574IP Transport NetworkMeasurement (FSMr3)

An alarm shall be raised (per active TWAMPsession), if at least one of the followingconditions is fulfilled:- The 1 minute average RTT threshold hasbeen exceeded- The 15 minutes packet loss threshold hasbeen exceeded.

The alarm shall be cleared, if- the RTT threshold has not been exceeded for5 minutes (and the packet loss condition is notfulfilled at that time)or- The packet loss threshold has not beenexceeded for 30 minutes (and the RTTcondition is not fulfilled at that time)

7/17/2019 LTE jj


7/17/2019 LTE jj



15 (20)

1170Inter-frequency loadbalancing

487 Idle mode mobility loadbalancing

1060 TDD - FDD handover

1407 RSRQ based Redirect

962 RACH Optimization

1099Event-triggered symptomdata collection andprovisioning

1260iOMS Certificate update andrevocation support

Operator Hints

1. If CRL checking feature” is enabled in OMS,please be aware that the downloaded CRLlists must be in status “OK”.Otherwise the OMS may send a cert requestand refuse the validation of the receivedcertificates with an out-dated CRL list.Result is the rejection of a https connection.

2. Registration Authority (RA) support nottested, because missing functionality from 3rdparty tool (INSTA5.2.3)

3. Starting from RL50 the certificates (CA certor Entity cert) without the Key Usage "digital-signature" and key-enciphment" are notaccepted by OMS.

1454Flexi RF Module 26008x15W FZHE

1457Cell trace Configuration viaConfiguration Management

1687Basic Layer3 Data Analyzer(L3DA) for LTE

1680 Active Queue Management

1405

Remote SW-managementand data backup/restoresupport for iOMS

4.2 Restric ted Released Legacy Features

ID Feature Name Restric tion Pronto IDCorrection

Plan

534

ARP-based

Admission Control for

It has not been

verified by real

7/17/2019 LTE jj



16 (20)

E-RABs NG3.1. Plan is toverify in maintenance

program when NG3.1is available.

519

eRAB Modification eRAB modificationcontains dedicatedbearer modificationwhich is notsupported in NG3.1.This feature needsNG3.1 (or evenNG3.2) supporting.

497

Smart AdmissionControl It has not beenverified by realNG3.1. Plan is toverify in maintenanceprogram when NG3.1is available.

163Subscriber andEquipment Trace

"Tested with NS2.2(N2 2.26-0);1. Some L3 messagecan’t be traced (e.g.HO related) becausethe mechanism in

MME can’t supportmillisecond interval forS1 trace signaling.MME is planned inNS4.0 currently.2. Sometimes eNBdoes not sent starttrace message afterestablishing of TCPconnection to iOMS(105298ESPE04, rootcause is in MME).

3. TraceFailure is notdisplayed in TraceViewer (NetAct 8).4. eNB cannotautomatically switchall ongoing tracesessions to newserving iOMSCN4542. "

612 Synchronization HubBBUHotelling is notused in RL35, soLTE612-b31, LTE612-

7/17/2019 LTE jj



17 (20)

b32 and LTE612-b1not tested in RL35.

655 LTE SoftwareManagement

The performance isnot achieved. RL45

4.3 Not Released Legacy Features

ID Feature NameOperator Hint/ Restriction

Pronto ID

424 Automatic interface

alarm correlation

No NAS monitor for OSS5.5available. New function willcome with NetAct 8.

5. 3RD PARTY CORRECTIONS

NA

6. RELEASE OBJECTS

6.1 Flexi Multi radio BTS LTE and iOMS descript ion

Information about Flexi Multiradio BTS LTE and iOMS can be found in Long TermEvolution Information Center, System Documentation, Chapter: “BTS and iOMSDescriptions”

6.2 Released sof tware versions

Following software version is released with this delivery.

6.2.1 eNB Software file lis t

Software Item Software File Name Checksum

eNB LNT3.0_ENB_1304_302_00b2c21a5088cc2b2912773d3b6cf094a908f9126b

Site managerBTSSiteEM-TD-LTE30-1304_083_00

c52db80a31c6883f53416f6386ffaeaf4e98a30a

GMC for 200 UEs LNT30_ Golden_2.4e5912e622af7650925694c518163a1f814eda17c

GMC for 100 UEs LNT30_Golden_1.4c270fd8f28df086272fbcac529ea44896944344b

https://online.portal.nsn.com/pic/com/nsn/extranet/pic/controller/productfinder/select.do?productfindermaincats=urn%3Ansn.com%3Amxpdm%3ARadio+Network&productfindersubcats=urn%3Ansn.com%3Amxpdm%3ARadio+Network+Solutions&productId=urn%3Ansn.com%3Amxpdm%3A133




7/17/2019 LTE jj



18 (20)

It is recommended that after downloading the SWs users should use CM_tools to doublecheck the checksums are consistent with checksum showed in NOLS page.

6.2.2 iOMS Software fil e lis t

Software Item Software File Name

iOMSiOMS5.0R_GOMS6_1.107.1.0.release_oms.corr38

6.2.3 EPC Software fil e lis t

EPC-name NE Version

SWAN(10.69.47.138)

MME N3 1.36-2

SAE R_FSPR5CAT_1.69.1.8_347045p1_r141817

HLRi MF 4.2-0

Roma(10.68.151.202)

MME NG2.1 1.80

SAE R_FSPR5CAT_1.62.1.8_325677_r128176

HLRi MF 4.2-0

6.2.4 OSS Software file list

Software Item Software File Name

OSS OSS5.5 P8 bundle+ WU0923

6.2.5 Tested and recommended UE Software fil e list

NetworkUnit Subunit Software Versions

UE IOT

HuaweiE3276

23.009.09.01.59

SamsungGalaxy S4

MiniJDQ39.I9197XXUAMF2

SamsungGalaxy S4

JDQ39I9507XXEAMH2

7/17/2019 LTE jj



19 (20)

ZTE U9815ZTE U9815V1.0.0B02

SamsungGT-N7108D

JDQ39.N7108DZMUAMI2

FiVe

Innofidei-Driving

Innofidei 400M(category4),RAPID400(category3)

Hisi-DrivingE398(category 3), E5776(category 4)

Altai rdongle ALT3100_04_05_06_00_24_TF

Altair CPE ALT3100_04_05_06_00_24_TF

Hisi-Commercial E5776(category 4)

Lab

Altai rdongle ALT3100_04_05_06_00_24_TFDeMing

CPECPE_H24_AT_v1.0.9

7. NOTES

7.1 Title: innof idei UE parameters setting

Impact: UE’s access and throughput will be impactedWorkaround:To do TM8 operations, it needs to make sure all of the following parameters changed tothese values.In SCF files (for innofidei):1

00d

189

And disable cqiAperEnable in SCF, set “false” (forTM8)

8. APPENDICES / REFERENCES

NA

http://10.68.152.99/svn/repo/Equipment%20Vendor%20tool%20and%20document/TM500_Version/Single-UE/K6.0.1/

http://10.68.152.99/svn/repo/Equipment%20Vendor%20tool%20and%20document/TM500_Version/Single-UE/K6.0.1/

7/17/2019 LTE jj



20 (20)

Disclaimer

The information in this document applies solely to the hardware/software product (“Product”) specified herein, andonly as specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not beused except for the purposes defined in the agreement between You and Nokia Solutions and Networks(“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 Solutionsand Networks. If you have not entered into an Agreement applicable to the Product, or if that Agreement hasexpired or has been terminated, You may not use this document in any manner and You are obliged to return it toNokia Solutions and Networks and destroy or delete any copies thereof.

The document has been prepared to be used by professional and properly trained personnel, and You assume fullresponsibility when using it. Nokia Solutions and Networks welcome Your comments as part of the process ofcontinuous 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 “asavailable” basis in this document, and Nokia Solutions and Networks reserves the right to change any suchinformation and statements without notice. Nokia Solutions and Networks has made all reasonable efforts toensure that the content of this document is adequate and free of material errors and omissions, and NokiaSolutions and Networks will correct errors that You identify in this document. But, Nokia Solutions and Networks'total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia Solutions andNetworks 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 ANYWARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THECONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL ORCONSEQUENTIAL 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 FROMTHIS DOCUMENT OR ITS CONTENT.

This document is Nokia Solutions and Networks’ proprietary and confidential information, which may not bedistributed or disclosed to any third parties without the prior written consent of Nokia Solutions and Networks.

NSN is a trademark of Nokia Solutions and Networks Oy. Nokia is a registered trademark of Nokia Corporation.Other product names mentioned in this document may be trademarks of their respective owners, and they arementioned for identification purposes only.

Copyright © 2014 Nokia Solutions and Networks Oy. All rights reserved.

7/17/2019 LTE jj


LNT3.0 2.0 - <Impact Document> © Nokia Solutions and Networks 2014Version 1.0Confidential

1 (7)

Impact Document


Radio Controllers

Product: Flexi Multiradio BTS TD-LTELTE iOMS

Release: RL35 MP2




7/17/2019 LTE jj


7/17/2019 LTE jj



3 (7)

1. PURPOSE

The Purpose of this document is to describe the Release Delivery effects on the relevant partiesand the new and changed functionalities that installing this Release Delivery bring to thecustomer’s network.

2. RELEASE DELIVERY EFFECT

RL35 Main (LNT3.0) is a system release for Nokia Long Term Evolution (LTE), including the followingnetwork elements and SW releases

• Flexi Multiradio BTS

• Flexi iOMS

• Flexi Network Server (NS) and Flexi Network Gateway (NG)

• NetAct Management System

Figure 1 LTE system overview

- LTE internet web pagehttp://nsn.com/portfolio/products/mobile-broadband/long-term-evolution-lte/td-lte

Soc Classification level

Presentation / Author / Date 2 © Nokia

SAE Architecture

SGi

S3

S1_MME

PCRF

Gx

S6a

HSS

Operator ’ sIP Services

Rx UE

GERAN

UTRAN

SGSN

LTE - Uu

eNB

MME

S11

S1_U Serving

SAE

Gateway

PDN SAE

Gateway

S10

S5

eNB

X2

S12

S4

NE3S/SNMP

BTSOM ASN.1

& HTTPS NetAct/OMS

http://nsn.com/portfolio/products/mobile-broadband/long-term-evolution-lte/td-lte



7/17/2019 LTE jj



4 (7)

- LTE Customer Documentationhttp://nsn.com/portfolio/products/mobile-broadband/long-term-evolution-lte/td-lte

3. HIGHLIGHTS ON END-USER

DL TM8 based Dual User Single Layer MU-MIMO

It helps to increase the cell capacity via pairing two single layer users.

Dynamic transmission mode switch

The system performance is optimized for UEs under different channel conditions.

Usage based PDCCH adaptationThe subscribers may experience better downlink throughput in scenarios with high PDSCHusage.

Support of QCI 2, 3 and 4

Support end use with GBR services like gaming or streaming.

Multiple GBR EPS Bearers per UE

Support end use with additional service combinations.

DL adaptive closed loop MIMO (4x2)

Provide multiple antenna precoding gain, Improve cell edge and cell mean throughput.

4. HIGHLIGHTS ON OPERATOR

RRU for network deployment:

FZHA RRH 2600 8x10WFZNC RRH 2300 6x10WFZNI RRH 2300 4x30W

Dual carrier operation w ith one RFM/RRU

This feature allows customer to increase the cell capacity via dual carrier

Subscriber profile based mobility

This feature allows customer to assign subscriber profile IDs (SPID) to mobility profiles.

Transport admission control

The Transport admission control enhances the resource utilization of the Flexi MultiradioBTS Transport

Graceful cell shut down

This feature allows customer to gradually reduces the downlink power in several steps,thus achieve minor service impact :UEs in RRC connected to perform a handover or aredirect and UEs in RRC idle to perform cell reselection and UEs in RRC idle to performcell reselection.

Remote SW-management and data backup/restore suppor t fo r iOMS

OPEX-savings by introducing remote SW-management for iOMS

Mobility Robustness




7/17/2019 LTE jj



5 (7)

SON-features to enables adjustment of Handover-related thresholds like HO offsets andTimeToTrigger based on performance monitor

Inter-frequency load balancingBTS supports load based inter-frequency handover between different eNode Bs connectedvia X2 or S1

Idle mode mobility load balancing

BTS supports idle mode mobility load balancing between different LTE carrier frequenciesas well as for IRAT scenarios.

RACH Optimization

BTS support optimization of PRACH / RACH parameters values by Resolution ofCollisions and Inconsistencies

MDT (Minimization of Drive Test)Operators invest considerable amount of money in drive test equipment and the executionof drive tests during delivering rollout, replacement, modernization and optimizationprojects where huge cost are incurred due the required resources to perform the drive test.

The idea is to automate collecting of trace information from eNB in a preconfigured usecase specific way, including UE measurements which would be post processed andanalyzed quickly.

This solution provides operator OPEX and CAPEX saving since not so many resourcesare needed to evaluate the performance of service and network thereby eliminating theneed to perform an expensive drive test.

Remove Wimax interference to TDLTETD-LTE BTS supports co-existent with Wimax by specific SRS handling to removeinterference.

TDD - FDD handover

Both handover directions FDD -> TDD and TDD -> FDD are supported.

Cell Specific neighbor relation

Introduce Cell specific PCI resolution to the existing ANR features to allow enhancedusage of ANR and HO related features even in difficult network setups

Multi-layered Certificate Author ities

Supports operator certificate management for multi-layer hierarchical PKI and cross-

certified PKI structures by Flexi Multiradio BTS, The customer is able to integrate NokiaIdentity Management System as sub-ordinate CA into its existing PKI and deploy anown/3rd party sub-ordinate CA to manage certificates for the Flexi Multiradio BTS

iOMS Certifi cate update and revocation support

The customer is able to use a usual Public Key Infrastructure with a Root certificate Authority on top and use case specific sub-ordinate Certificate Authorities in charge forsigning the RAN nodes also now for iOMS nodes. 3GGP compliant life cycle managementallows flexibility on PKI vendor selection and harmonized certificate management for iOMSin the same fashion as for BTS and Security Gateways which leads to severe OPEXreductions.

X2 eNB Configuration Update

7/17/2019 LTE jj



6 (7)

Supports the configuration update to neighbor eNBs viaX2AP:eNodeBConfigurationUpdate about served cell information, such as change of PCI

or EARFCN, GU Group ID

IP Transpor t Network Measurement

This feature brings OPEX savings as the operator is able to monitor the network conditionsand can react quickly to potential service degradations. The measurements provide anindication of possible violations against an SLA (Service Level Agreement). CAPEXsavings are obtained, because the built-in measurement means obsoletes expensivemeasurement equipment that would be otherwise required to supervise and troubleshootthe network

Event-triggered symptom data collection and provisioning

The feature presents a centralized function of collecting BTS Techlogs (troubleshootingdata) from Flexi Multiradio BTS when a predefined event occurs. The logs are available in

the NetAct and can be accessed by operator and sent to technical service to identifyproblems.

5. OTHER HIGHLIGHTS

Secure management protocol between iOMS and NetAct

Enhanced risk management due to improved system security. A secured transportinterface can be used for management plane between iOMS and NetAct. OPEX andCAPEX savings are achieved because investments to external IPSec device co-sited to

NetAct and manual IPSec configuration are not required to achieve system security.

6. NEW / CHANGED FUNCTIONALITY

N.A


N.A

7/17/2019 LTE jj



7 (7)

Disclaimer











7/17/2019 LTE jj


LNT3.0 2.0 - <Change Note Forms> © Nokia Solutions and Networks 2014Version 1.0Confidential

1 (40)

Change Note FormsId: LNT3.0 2.0Product Family: Base Stations

Radio Controllers


Release: RL35 MP2




7/17/2019 LTE jj



2 (40)

CN-id: LNT3.0_18203

Title:

Version of the SW-build:

LNT3.0_ENB_1304_301_00

Valid for Product(s):

Flexi LTE Base Station

References:

Reason for the Change Note:Summary of the original problem:When working with iOMS after reaching max number of connections all following connections wererejected. When used connections decrease below maximum connections eNB which was previouslyrejected could not connect correctly despite of free connections in iOMS.

How end user/operator could detect the problem:Operator should configure network with tracing feature. All sessions should be configured toward3rd party tool. User can observe the problem when number of session exceed the number ofconnections supported by the iOMS and when some of the connections are released and previouslyrejected connection will try to connect again (without the eNB reconfiguration).

Description of the fault:

No start trace is send when eNB connects to iOMS after being previously rejected. What causeconnection to be reset by iOMS.

Related feature / functionality:LTE644 LTE163

Dependency on configuration:NA

Workaround:NA

Description of the correction (incl. risk analysis):eNB send start trace toward iOMS each time the connection is re-established.

System effects:NA

Faulty component and version:LOM: LNT3.1_LOM_1209_30956

Faulty component first delivered in (e.g. release, CD):

Corrected Fault Reports:109320ESPE01 Alarm flood of failure in connection between BTS and iOMS or 3rd party tool.

7/17/2019 LTE jj


7/17/2019 LTE jj



4 (40)

References:

Reason for the Change Note:Summary of the original problem: Antenna open state, alarm 1837 and 1957 reported simultaneously

How end user/operator could detect the problem:alarm from site manager

Description of the fault:antenna open state, alarm 1837 and 1957 reported simultaneously

Related feature / functionality:N/A

Dependency on configuration:N/A

Workaround:N/A

Description of the correction (incl. risk analysis): Add VSWR Major alarm in RL35.

System effects:N/A

Faulty component and version:N/A

Corrected Fault Reports:

NA05664136NA05664136 || VSWR Major alarm not reporting in RL35 LTE BTS

Modified components:

Component Version *Net element *SW-type *Unit

TDL24.03.R03D TDL24.03.R03D

- - -

Change effects:

Effects on end-userNA

Effects on OperatorNA

Other effects

NA

New functionalityNA

Customer Impact

7/17/2019 LTE jj



5 (40)

New feature/functionality

Testing Instructions for the change

Pre-requirements:eNBs are installed with correction SW, up running, cells are configured, and On-Air state.

Test execution:

Trigger high VSWR environment (e.g. removing RF Antenna Cable) on the TRX port.

Expected results:If the VSWR value higher than the VSWR Major Threshold, VSWR Major Alarm and Radioresources switched off should be raised

Unexpected results:

VSWR Major Alarm does not raised

CN-id: LNT3.0_18344

Title:LTE939 - Usage Based PDCCH Adaption for RL35 TDD sites

Version of the SW-build:LNT3.0_ENB_1304_301_00



References:

Reason for the Change Note:116050ESPE04: Summary of the original problem:scenario which triggered the issues (mandatory):Step1: Activated load adaptive PDCCH which allows adapt number of PDCCH symbol dynamic;

Step2: Set maximum number of PDCCH symbols= 3, this would have number of PDCCH symbolsfrom 1 to 3 in terms of setting;root cause for the fixed pronto (mandatory):EFS pronto, pdcch symbol need not add one when pdcchinnumOfSymChangeTime expired.correction solution for the fixed pronto (mandatory):EFS pronto, pdcch symbol need not add one when pdcchinnumOfSymChangeTime expired.Loc (mandatory):16fault category (mandatory):EFS design errorfeature which introduced this pronto (mandatory):LTE939

Fault category description:

7/17/2019 LTE jj



6 (40)

How end user/operator could detect the problem:

System effects:NA

Corrected Fault Reports:116050ESPE04LTE939 - Usage Based PDCCH Adaption for RL35 TDD sites

NA05644907LTE939 - Usage Based PDCCH Adaption for RL35 TDD sites



fb1304.- 128677 - - -RRMT.5358 2.0.0 - - -LTE_UP_9881.- 20.0 - - -LTE_UP_8700.- 50.0 - - -

Change effects:



Other effects

NA

New functionalityNA

Customer Impact116050ESPE04:NA05644907:New feature/functionalityPDDCH symbol number will increase unintentionally.This will be noticed only when the load is low.This has no significant negative impact on performance but the behavior is strange.


Pre-requirements: As pronto test description

Test execution: As pronto test description

Expected results:

the PDCCH symbol will be stable 1 when stably no load

Unexpected results:NA

7/17/2019 LTE jj



7 (40)

CN-id: LNT3.0_18347

Title:

SEM report error after commissioning file active successful


Valid for Product(s):Flexi LTE Base Station

References:

Reason for the Change Note:From PDDB description if srsSubfrConf set to 'sc0', 'sc8', 'sc9', 'sc10' or 'sc11', srsOnTwoSymUpPtsmust be set to 'true', but when I set srsSubfrConf to 'sc0' and srsOnTwoSymUpPts set as emptySEM did not report any error.


109576ESPE01

SEM report error after commissioning file active successful



tdltebtsmanager.jar 646231 - - -

Change effects:


Effects on Operator

NA

Other effectsNA

New functionalityNA

Customer ImpactOperation & Maintenance


7/17/2019 LTE jj



8 (40)

Pre-requirements:

set srsSubfrConf to 'sc0' and srsOnTwoSymUpPts set as empty

Test execution:I set srsSubfrConf to 'sc0' and srsOnTwoSymUpPts set as empty

Expected results:

SEM report error

Unexpected results:SEM did not report any error

CN-id: LNT3.0_28268

Title:BTS Crash with RRU status still OK to access normally, BTS could not reset itself except repoweron.


LNT3.0_ENB_1304_301_00


References:

Reason for the Change Note:

PR 113478ESPE04: BTS Crash with RRU status still OK to access normally, BTS could not resetitself except repower on.

[PR 106711ESPE01][LNT3.0]BTS crash when UE attach and doing throughput

Description of the fault:BTS is on air. UE attach/UE attach and doing T-put.BTS crash and only reset by power off/on can

recover.

Related feature / functionality:NA

Description of the correction (incl. risk analysis):From the back trace we are able to confirm that crash took place while incrementing performancecounter. Crash is happening while incrementing a performance counter and an invalid reference isused while incrementing that is causing the crash. This performance counter will get incrementedwhen some unknown protocol packet with TTL=0 is received or if packet is received that is comingunder TTL violation or some other error condition.For external communication, we have defined ports 8,9, and 10. If an invalid port is received whileincrementing counter then it maps to an invalid memory reference and that handling is not done inthe code.

7/17/2019 LTE jj



9 (40)


113478ESPE04BTS Crash with RRU status still OK to access normally, BTS could not reset itself except repoweron.

106711ESPE01BTS crash when UE attach and doing throughput



aricent_r3_pm_106711.-

FTM_R3_LN50_LNT30_MP1_323.00.01

- - -

Change effects:



Other effectsNA

New functionalityNA

Customer ImpactNA


Pre-requirements:eNB on air

Test execution:UE PPOE attach for data traffic

Expected results:No abnormal issue happen, such as eNB crash in this case.

Unexpected results:eNB crash in this case, when UE PPOE attach

CN-id: LNT3.0_28269

7/17/2019 LTE jj



10 (40)

Title:[RL35 P8] can't establish the SSL connection after upgrade from RL25


LNT3.0_ENB_1304_301_00


References:


Summary of the original problem: On upgrading from RL25 to RL35 build, FTM webpage was notopening

Description of the fault:In case when FTM is only containing BTS cert and no certificate chain then in that caselighthttpd.pem file is not generated. On upgrading from FTM ln20(non-MLCA) to ln50(MLCA), ln50was not considering single certificate/key in certs directory and using bts certificate. Due to thislighthttpd.pem was not being created.

Related feature / functionality: Certificate installation, l ightHttpd.pem generation, lighttpd processstartup

Description of the correction (incl. risk analysis):In case when certificate chain is not present and bts cert is present then lighthttpd.pem is created

using BTS cert.

Corrected Fault Reports:112362ESPE04[RL35 P8] can't establish the SSL connection after upgrade from RL25



aricent_r3_ln50_112362espe04_ssl_er ror_new.-

FTM_R3_LN50_LNT30_MP1_322.00.02

- - -

Change effects:


Effects on Operator

NA

Other effectsNA

New functionalityNA

7/17/2019 LTE jj



11 (40)

Customer Impact

Operation & Maintenance


Pre-requirements:The eNB running with RL25 SW, equipped with IPSec certificate, the status is OK.

Test execution:upgrade to RL35 P8 LNT3.0_ENB_1304_243_02

Expected results:

the eNB is on air , but the SSL connection is OK

Unexpected results:the SSL connection is impossible.

CN-id: LNT3.0_28270

Title:[LNT3.0]TRS configuration missing after ENB upgrade from LNT3.0_ENB_1304_243_02 toLNT2.0_ENB_9308_345_00



References:

Reason for the Change Note:Summary of the original problem:[LNT3.0]TRS configuration missing after ENB upgrade from LNT3.0_ENB_1304_243_02 toLNT2.0_ENB_9308_345_00

Description of the correction (incl. risk analysis):issue mentioned in PR 81251ESPE03 arose because of mismatch in MOs supported in LNT3.0 vs.LNT2.0. Following MOs were supported in LNT 3.0 but not supported in LNT 2.0:

1. NMA_CLASS_IP_TWAMP2. NMA_CLASS_OAMMD3. NMA_CLASS_OAMMA4. NMA_CLASS_OAMMEP5. NMA_OAM_PROFILE

7/17/2019 LTE jj



12 (40)

But there was no provision to remove these MOs in the transformation function used for LNT2.0

adaptation.

As a fix, transformation function has been enhanced to remove the above mentioned MOs whiledoing a downgrade from LNT3.0 to LNT2.0.


81251ESPE03[LNT3.0]TRS configuration missing after ENB upgrade from LNT3.0_ENB_1304_243_02 toLNT2.0_ENB_9308_345_00


Component Version *Net element *SW-type *Unitaricent_r3_twamp.- FTM_R3_LN50_LNT30_MP1_322.00.02

- - -

Change effects:

Effects on end-user

NA


Other effectsNA

New functionalityNA

Customer Impact

NA


Pre-requirements:1.BTS is On Air with LNT3.0 build, and with feature LTE574 enabled2.prepare one LNT2.0 package

Test execution:Upgrade from LNT3.0 to LNT2.0

Expected results:Upgrade successfully, BTS is On Air, TRS commissioned

Unexpected results:BTS is not On-air, TRS is not commissioned

7/17/2019 LTE jj



13 (40)

CN-id: LNT3.0_28705

Title:BTS site manager don't show alarm information when enter an incorrect usrname and password.


LNT3.0_ENB_1304_301_00


References:


Summary of the original problem: Error being removed by ui update

How end user/operator could detect the problem: the error disappearing after wrong credentials

Description of the fault: The ui update removed the error from the launcher

Related feature / functionality: the launcher connect

Dependency on configuration: it is in all configurations

Workaround: none

Description of the correction (incl. risk analysis):The error message flash in a very short time. This problem have been fixed about 2 month agoEffects on end-user: The error message flash in a very short time. This problem have been fixedabout 2 month ago

Effects on operator: The error message flash in a very short time. This problem have been fixedabout 2 month ago

System effects: The error message flash in a very short time. This problem have been fixed about 2month ago

Other effects: N/A

Interface Effects: The error message flash in a very short time. This problem have been fixed about2 month ago

Faulty component and version: launcher/trunk

Faulty component first delivered in (e.g. release, CD):N/ADependency on configuration:

Workaround: none

Description of the correction (incl. risk analysis):The error message flash in a very short time. This problem have been fixed about 2 month agoEffects on end-user: The error message flash in a very short time. This problem have been fixedabout 2 month ago

7/17/2019 LTE jj



14 (40)

Effects on operator: The error message flash in a very short time. This problem have been fixed

about 2 month ago

System effects: N/A

Other effects: N/A

Interface Effects: The error message flash in a very short time. This problem have been fixed about2 month ago

Faulty component and version:LNT3.1_BTSSM_1209_085_00Faulty component first delivered in (e.g. release, CD):N/A


140445ESPE02BTS site manager don't show alarm information when enter an incorrect usrname and password.



cl.- - - - -

Change effects:



Other effectsNA

New functionality

NA



Pre-requirements:

BTSSM have installed normally

Test execution:1. Input correct username and error password, Or Input error username and correct password.2. click "login" button

Expected results:It should have related information if login failed.

Unexpected results:There is not any information to show .

7/17/2019 LTE jj



15 (40)

CN-id: LNT3.0_28709

Title:Lack of TRS PM counter(IP counter: Transport Ethernet interface AF4)



References:

Reason for the Change Note:Summary of the original problem:Lack of TRS PM counter(IP counter: Transport Ethernet interface AF4)

How end user/operator could detect the problem:Functional

Description of the fault:

while receiving packet from S1 interface with different dscp value, there is no PHB counterincrement according to the DSCP value



Workaround:NA

Description of the correction (incl. risk analysis):while enabling QoS from EM, there is index used to maintain at device Adapter and FastPath foreach dscp value. From Device adapter always index used to come with value 1. But FastPath usedto calculate it wrongly and while increment PHB counter it value also get wrong . So at FastPath italso made 1.

Corrected Fault Reports:138723ESPE02Lack of TRS PM counter(IP counter: Transport Ethernet interface AF4)



aricent_r3_rl50_mp in - - -

7/17/2019 LTE jj



16 (40)

2_139164espe02.-FTM_R3_LN50_LN

T30_MP1_331.00

- - - -

Change effects:


Effects on Operator

NA

Other effectsNA

New functionality

NA



Pre-requirements:all the packets show in the TRS PM counter should report the real state

Test execution:1. BTS is on air2.Configure all the DSCP in one queue

3.Configure the egress shaper information to let upload traffic to fill full bandwidth4.Do UL and DL throughput5.Check the TRS PM counter

Expected results:check TRS PM counter, the packets pass the Ethernet of eNB under vlan should as fast as you did

Unexpected results:

the ifInpackets counter of the TRS is zero, means no packets pass this port, unreasonable

CN-id: LNT3.0_31445

Title:[RL35 IR] System module fault (0010) or FBBA not detected after bts reset



7/17/2019 LTE jj



17 (40)


References:

Reason for the Change Note:Summary of the original problem:One NEW site of F band reported 0010 system module failure alarms (7651)

How end user/operator could detect the problem:FSP not starting

Description of the fault:System module failure alarm (7651) on few (1/1000) A101, A102 or A103 (before w47 2013) FSMF.

Related feature / functionality: NA

Dependency on configuration: NA

Workaround:power cycle

Description of the correction (incl. risk analysis):make add events parallel in HPD

Effects on end-user: out of serviceEffects on operator: our of serviceSystem effects: NA

Other effects: NA

Interface Effects: NA

Faulty component and version:PS_REL_20M2_99_20Faulty component first delivered in (e.g. release, CD):since mid of 2013


108122ESPE01[RL35 IR] System module fault (0010) or FBBA not detected after bts reset

139978ESPE02[R55 FSMF][Dual Carrier FZHA][routing table is not setup for one cell, another can be on-air]

NA05640471NA05640471 (TDLTE Fujian)(ENB)one NEW site of F band reported 0010 system module failurealarm(7651)

115623ESPE04][RL35 Main] Can’t detect FBBA2 and appeared 0010 alarm after UpgradeLNT3.0_ENB_1304_251_03 to LNT3.0_ENB_1304_273_00



LFS.- r70166 - - -

7/17/2019 LTE jj



18 (40)

Change effects:



Other effectsNA

New functionalityNA

Customer Impact108122ESPE01: StabilityNA05640471:Operation & Maintenance


Pre-requirements:NA

Test execution:NA

Expected results:NA

Unexpected results:NA

CN-id: LNT3.0_31697

Title:Poster test scenarios not take effect after FSP2 external Memory test failure



References:


7/17/2019 LTE jj



19 (40)

Summary of the original problem:when POST flag(427) isn't set in swconfig or set to 0, SPMAG doesn't verify the result of POST.

Then, BTSOM doesn't know any errors of POST when power on reset.

How end user/operator could detect the problem:test scenario described in this PR.

Description of the fault:The fault FaultId_Post_test_failedAl isn't reported to SEM.



Workaround:NA

Description of the correction (incl. risk analysis):SPMAG will always validate the result of POST even if there is no POST flag

System effects:NA

Interface Effects:NA


107858ESPE01Poster test scenarios not take effect after FSP2 external Memory test failure



FB_PS_REL_2013 _04_128.-

128 - - -

CSpmag_TaskPOST.cls

263321 - - -

48634.- 48634 - - -

Change effects:

Effects on end-user

NA


Other effectsNA

New functionalityNA


7/17/2019 LTE jj



20 (40)


Pre-requirements:n/a

Test execution:Install the new eNB SW include correction for "Post test scenarios". If DSP fail post test, eNB willrepot alarm of 69: EFaultId_Post_test_failedAl.

Expected results:If DSP fail post test, eNB will repot alarm of 69: EFaultId_Post_test_failedAl..

Unexpected results:If DSP fail post test, FSP might be failure, then report other alarm, not report alarm of 69:EFaultId_Post_test_failedAl.

CN-id: LNT3.0_31701

Title:[RL35 Main] FATAL Error during Stability test




References:

Reason for the Change Note:Summary of the original problem:Random SRIO network congestion during high DIO bandwidth utilization causing spontaneousFATAL crashes

How end user/operator could detect the problem:Execute high load test cases

Description of the fault:Insufficient VBUS priority of SRIO transfers causing SRIO response timeouts and networkcongestion

Related feature / functionality:None

Dependency on configuration:None

Workaround:

7/17/2019 LTE jj



21 (40)

None

Description of the correction (incl. risk analysis):Increased SRIO device VBUS access priority:

System effects:NA

Interface Effects:none

Faulty component and version:NA

Faulty component first delivered in (e.g. release, CD):NACorrected Fault Reports:

115808ESPE04[RL35 Main] FATAL Error during Stability test



PSDSP-3362.- - - - -

Change effects:



Other effectsNA

New functionalityNA

Customer ImpactStability


Pre-requirements:

Test execution: 200 UE with full traffic on DL/UL, run for 3~12 hours. Check FATAL error log in Syslog

Expected results:1. Stable throughput2. No fatal error happen

7/17/2019 LTE jj



22 (40)

Unexpected results:Error happened.

CN-id: LNT3.0_31702

Title:Degradation of main KPI's for neighbors sites after Power OFF/ON of one TD-LTE eNB, Looks thesite went out of synch


LNT3.0_ENB_1304_301_00


References:

Reason for the Change Note:Summary of the original problem: FYGB supply the wrong UTC time

How end user/operator could detect the problem: Several times power reset GPS

Description of the fault: NA


Dependency on configuration: FYGB was using

Workaround: NA

Description of the correction (incl. risk analysis): After EFS discuss with Tribbel person , the new msg 0x41 and 0x46 was new introduced to bechecked to promise the correct UTC time .

System effects: NA

Faulty component and version: NA

Faulty component first delivered in (e.g. release, CD): NA


NA05670149Degradation of main KPI's for neighbors sites after Power OFF/ON of one TD-LTE eNB, Looks thesite went out of synch



7/17/2019 LTE jj



23 (40)

GPS_Pkg.sbs 268619 - - -WBTS_SYNC_574

60.-

19.2 - - -

WBTS_SYNC_59934.-

8.1 - - -

WBTS_SYNC_67223.-

11.1 - - -

Change effects:



Other effectsNA

New functionalityNA

Customer ImpactCapacity & Performance


Pre-requirements:

Use FYGB

The power supply lost for the whole shelter suddenly and there is no battery backup.

Test execution:1.eNB is on air on the RL35 MP22.The GPS receiver device is FYGB.3. There is power break suddenly for all the shelter.4. the eNB recovered after the power supply is normal.5. Enable the following flag in the swconfig.330 =1428 =113=1

Expected results:The eNB is on air normally.

Unexpected results:KPI degraded.

CN-id: LNT3.0_31709

7/17/2019 LTE jj



24 (40)

Title:[LNT3.0] Counter should be clear when changed VLAN ID


LNT3.0_ENB_1304_301_00


References:


Summary of the original problem:Counter should be clear when changed VLAN ID

Description of the fault:counters not cleared when vlan id is changed

Related feature / functionality:Counters

Description of the correction (incl. risk analysis):reset request is sent to the fast path from the adapter when vlan id is changed


46894ESPE05[LNT3.0] Counter should be clear when changed VLAN ID



aricent_r3_pr_50657_ln50_mp2.-

- - - -

FTM_R3_LN50_LNT30_MP2_334.00.02

- - - -

Change effects:



Other effectsNA

New functionalityNA

Customer Impact

7/17/2019 LTE jj



25 (40)

Operation & Maintenance


Pre-requirements:eNB configured with VLAN.

Test execution:

Change the VLAN ID directly but not modify the IP address for this vlan.

Expected results:The Ethernet counter for this vlan change to 0. The counter in this 15min period will lose. Thehistory counter still keep.

Unexpected results:

Counter value too large or history counter lost.

CN-id: LN50_104

Title:E NodeB fails to connect to DHCP using SON.




References:

Reason for the Change Note:Summary of the original problem: E NodeB fails to connect to DHCP using SON.

How end user/operator could detect the problem: please see detailed description

Description of the fault:eNodeB fails to connect to DHCPDHCP server sends out the DHCP Offer message to the eNB via the Relay agent as unicastmessage which is transformed with TTLvalue as 1 (whatever you set at DHCP server, Relay Agent modifies it to TTL value-1) asbroadcast towards the eNB as destination.eNB FSM ETH-1 port decrements the TTL value to 0 and before accepting the assigned IP,NSN eNB discard the packets which in terms that eNB never sends out theDHCP Request message and the process repeats after a while

Related feature / functionality: IP

Dependency on configuration: DHCP is received with ttl=1

7/17/2019 LTE jj



26 (40)

Workaround: None

Description of the correction (incl. risk analysis):added condition to check for broadcast packets withttl value equal to 1 or 0 and accept them

Corrected Fault Reports:NA05656753E NodeB fails to connect to DHCP using SON.



aricent_r3_na05652597_rl50_mp1.-

FTM_R3_LN50_LNT30_MP1_333.00.02

- - -

Change effects:



Other effectsNA

New functionalityNA

Customer ImpactNA05656753: Capacity & Performance


Pre-requirements:FSMF and auto connection feature usage, with target HW being updated to RL50 MP1.1 first

Test execution: Auto connection process is carried out, with a dhcp server being set up accordingly. Dhcp offermessage from dhcp server even with TTL field being = 1 will be processed by eNB and thus autoconnection process completes successfully. This can be seen in wireshark, as after dhcp offermessage eNB sends out dhcp request message.

Expected results:auto connection process completes successfully

Unexpected results:auto connection process does not complete.

7/17/2019 LTE jj



27 (40)

CN-id: LN50_120

Title:L18 eNodeB with RL50 0.2 s/w locking requiring local reset to restore


LNT3.0_ENB_1304_301_00


References:


Summary of the original problem:System logger causes slowdowns.

How end user/operator could detect the problem:Overall performance impact in particular for processes that do logging.

Description of the fault:Logger causes backpressure under certain situations, which in turn leads to SW slowdown. Thisbackpressure was caused by using a "compatibility mode" flag triggered the logger bug.

Related feature / functionality:

N/A

Dependency on configuration:N/A

Workaround:N/A

Description of the correction (incl. risk analysis):Logger configuration has been updated not to use compatibility mode (which was not neededanyway anymore). Very low risk assumed.

System effects:NA

SW lockup due to logging should not happen anymore.


NA05668028L18 eNodeB with RL50 0.2 s/w locking requiring local reset to restore



LFS.- r79315 - - -

Change effects:

7/17/2019 LTE jj



28 (40)

Effects on end-user

NA


Other effectsNA

New functionalityNA

Customer ImpactNA05668028: Operation & Maintenance


Pre-requirements:This was a platform problem, difficult to be reproduced in lab environment.The issue (site not working/IPSec not coming up) should not show up any more after correctioninstallation.

Test execution:NA

Expected results:NA

Unexpected results:

NA

CN-id: LNT3.0_31699

Title:[RL35 Main]PM counter DATA_RB_STP_COMP Bigger than DATA_RB_STP_ATT in 251_03


LNT3.0_ENB_1304_301_00



References:


Summary of the original problem:

7/17/2019 LTE jj



29 (40)

Completion Counter bigger than attempt counter, i.e. completion counter is wrongly incrementedtwice

How end user/operator could detect the problem:See above.

Description of the fault:In case of the occurrence of a reestablish request while still running in a handover target scenario intarget configuration, the completion or failure counters are wrongly incremented by the reestablishprocedure



Workaround:NA

Description of the correction (incl. risk analysis):- relegated counters are not counted for intracell HO cases or target configuration scenariosanymore, low risk

System effects:NA

Other effects:NA

Faulty component and version:

NA

Corrected Fault Reports:140268ESPE02[RL35 Main]PM counter DATA_RB_STP_COMP Bigger than DATA_RB_STP_ATT in 251_03



UEC.- 208644 - - -

Change effects:



Other effects

NA

New functionalityNA


7/17/2019 LTE jj



30 (40)


Pre-requirements:BTS is in normal state, multi-ue attach in cell

Test execution:Check PM counter DATA_RB_STP_COMP and DATA_RB_STP_ATT in SEM

Expected results:DATA_RB_STP_ATT is bigger than or equal to DATA_RB_STP_COMP

Unexpected results:DATA_RB_STP_ATT is smaller than DATA_RB_STP_COMP

CN-id: LNT3.0_29009

Title:Climate control profiling is auto enabled after enable and disable it by SEM




References:

Reason for the Change Note:Summary of the original problem:Climate control profiling is auto enabled after enable and disable it by SEM

How end user/operator could detect the problem: NA

Description of the fault: NA



Workaround: NA

Description of the correction (incl. risk analysis): NA

System effects: NA


7/17/2019 LTE jj



31 (40)

Faulty component first delivered in (e.g. release, CD): NA

Corrected Fault Reports:108946ESPE01Climate control profiling is auto enabled after enable and disable it by SEM



laf.jar - - - -

Change effects:

Effects on end-user

NA


Other effectsNA

New functionality

NA



Pre-requirements:BTS is on air, all status is right.

Test execution:step1: BTS is on air, all status is right. Go to Module Settings page from BTS commissioning.step2: Click the "In use" button to enable all modules.step3: Select any one of module and click the profile to open the pull-down list.step4: Don not choose any one, just click the profile button again and Click the "In use" button againto disable all modules.step5: Click the "next" button go to next page and click "back" button to see whether the module isenable.

Expected results:The module of Climate control profiling is disabled.

Unexpected results:The module of Climate control profiling is enabled.

CN-id: LNT3.0_31700

7/17/2019 LTE jj



32 (40)

Title:[RL35 main] BTS OM crash after degrade BTS version from 275_00 to 273_99


LNT3.0_ENB_1304_301_00


References:


115838ESPE04: Summary of the original problem:Missing sync between send and SAaConfigSvcRegistry message leads send crash

How end user/operator could detect the problem:It is an occasional issue, Run many times, maybe it will be appear.

Description of the fault:BTS crash during BTS start up.

Related feature / functionality:Ext-Connection removal


Workaround:NA

Description of the correction (incl. risk analysis): Add a safe sender class to avoid crash.

Effects on end-user:BTS crash

Effects on operator:OAM crash

Faulty component and version:NA

Faulty component first delivered in (e.g. release, CD):NA

Corrected Fault Reports:115838ESPE04[RL35 main] BTS OM crash after degrade BTS version from 275_00 to 273_99

51057ESPE05[RL35 main] CC&S error with EU id : 441 (0x1B9) after delete config&trs file


7/17/2019 LTE jj



33 (40)


TECHREPAdapter.h 263324 - - -

Change effects:



Other effectsNA

New functionalityNA

Customer Impact115838ESPE04: Capacity & Performance51057ESPE05:Capacity & Performance


Pre-requirements:

OAM crash when do auto-configure & auto-connect

Test execution:1. BTS work stable on build 280_00.2. delete configure and FTM file

Expected results:ENB do auto-configure & auto-connect successfully, and ENB's status is on air

Unexpected results:ENB cannot detect RRU, and OAM crash.

CN-id: LNT3.0_31698

Title:Lack of TRS IP counter (Transport Ethernet interface AF)


7/17/2019 LTE jj



34 (40)



References:

Reason for the Change Note:Summary of the original problem:There is no PHB PM counter increment for each queue.

How end user/operator could detect the problem:System verification

Description of the fault:There is no PHB PM counter increment for each AF and BE queue.

Related feature / functionality:QoS, PM counter


Workaround:NA

Description of the correction (incl. risk analysis):while enabling QoS from EM, there is index used to maintain at device Adapter and FastPath foreach dscp value. From Device adapter always index used to come with value 1. But FastPath usedto calculate it wrongly and while increment PHB counter it value also get wrong . So at FastPath italso made 1.

System effects:NA


Corrected Fault Reports:139164ESPE02Lack of TRS IP counter (Transport Ethernet interface AF)



aricent_r3_rl50_mp2_139164espe02.-

FTM_R3_LN50_LNT30_MP1_331.00

- - -

Change effects:



Other effectsNA

7/17/2019 LTE jj



35 (40)

New functionalityNA



Pre-requirements:

Check the AF counter is OK for operation

Test execution:1. BTS is on air2. Configure all the DSCP in one queue3. Configure the egress shaper information to let upload traffic to fill full bandwidth4. Do UL and DL throughput

Expected results:There are ifInPackets and ifOutPackets counters in SEM in one AF display

Unexpected results:

There is only ifOutPackets counter in SEM in one AF display, lacking of ifInPackets counter

CN-id: LNT3.0_18345

Title:Modify PCI failed even though enableAutoLock=enable


LNT3.0_ENB_1304_301_00


References:


Summary of the original problem: when modify pci, should check enableAutoLock in plan file

How end user/operator could detect the problem: modify pci and enableAutoLock in plan file, thendo commission

Description of the fault: in code not check enableAutoLock, but check administrative State.

Related feature / functionality: no

Dependency on configuration: no

Workaround: no

Description of the correction (incl. risk analysis): in code check enableAutoLock in plan file

7/17/2019 LTE jj



36 (40)

Effects on end-user: no

Effects on operator: no

System effects: no

Other effects: no

Interface Effects: no

Faulty component and version: no

Faulty component first delivered in (e.g. release, CD): no

Corrected Fault Reports:140728ESPE02modify PCI failed even though enableAutoLock=enable



CConf_validator.cls 263015 - - -

Change effects:



Other effectsNA

New functionality

NA



Pre-requirements:

1. eNB is working normally on-air with LNT3.0 load (newer than LNT3.0_ENB_1304_279_00)2. Keep LNBTS Enable automatic locking value as enable

Test execution:Modify physical layer cell identity value for one or more cells via BTS Site manager commissionpage and send the commission file to eNB

Expected results:New physical layer cell identity value was commissioned and activated successfully.

Unexpected results:Commissioned and activation failed, and physical layer cell identity kept as old value.

7/17/2019 LTE jj



37 (40)

CN-id: LN50_127

Title:

RL50 - FSMF fast tune does not work for SyncE, no alarm displayed

Version of the SW-build:xyz


References:


Summary of the original problem:When using the BTS fast tune option for transmission synchronization when there is SyncE beingdelivered to the BTS, SSM flag ok, the BTS does not alarm when the fast tune fails. We have tried anumber of times to fast tune, each time we click fast tune option, nothing happens, the BTS clockingdoes not update (BTS Clock Tuning history) but the BTS never alarms. SyncE is definitelyconfigured on the trs, SSM is showing PRC.

This fault is to track the lack of alarming, the BTS should alarm if it fails fast tune or even if fast tuneis not used, when the BTS periodically tunes the clock every 20mins, if this fails, it should alarm

How end user/operator could detect the problem: Reference clock with poor quality

Description of the fault:no alarm of 1831 rose when tuning not success.



Workaround: NA

Description of the correction (incl. risk analysis):adding the FD rule for handling of fault 1831System effects:N/A

Faulty component and version:FlexiFDrules.txt/26411

Corrected Fault Reports:NA05634595RL50 - FSMF fast tune does not work for SyncE, no alarm displayed


7/17/2019 LTE jj



38 (40)


FlexiFDrules.txt 264115 - - -

Change effects:



Other effectsNA

New functionality

NA



Pre-requirements:eNB on air and SyncE synchronization source available.

Test execution:Select SyncE as synchronization source for the eNB. Start the fast tune process for the eNB.

Expected results:Fast tune is successful and a DAC word calculated and displayed in the tuning history.

Unexpected results:No DAC word is written to the tuning history.

CN-id: LNT3.0_31720

Title:VSWR Major Alarm is not Auto Clear after return the jumper back.


LNT3.0_ENB_1304_301_00



7/17/2019 LTE jj



39 (40)

References:

Reason for the Change Note:Operation & MaintenanceFault Description: When VSWR Major alarm is triggered, the alarm itself cannot be automaticallycleared

Impact Statement: To Cancel this alarm, it's required eNB resetting. From customer perspective,alarm should be clear automatically when VSWR below the threshold value without resetting eNBTrigger: Trigger VSWR Major Alarm by removing Ant. Cable from the RRU port. After alarmgenerate, return the Ant Cable back to the port. (Alarm should be exist)

Occurrence Rate: 10/10

Detection: VSWR Major Alarm Exist

Recovery: In the previous version, it will require RRU resetting or eNB resetting. With newcorrection, Alarm can be cleared without eNB resetting by start VSWR tuning mode and run it untilalarm is cleared.

Corrected Fault Reports:111434ESPE01VSWR Major Alarm is not Auto Clear after return the jumper back.



TDL24.03.R04D TDL24.03.R0

4D

- - -

Change effects:



Other effectsNA

New functionalityNA


Fault Description: When VSWR Major Alarm is triggered, the alarm itself cannot be automaticallycleared

Impact Statement: To cancel this alarm, it's required eNB resetting. From customer perspective,alarm should be clear automatically when VSWR below the threshold value without resetting eNB

Trigger: Trigger VSWR Major Alarm by removing Ant. Cable from the RRU port. After alarmgenerate, return the Ant Cable back to the port. (Alarm should be exist)

7/17/2019 LTE jj



40 (40)

Occurrence Rate: 10/10

Detection: VSWR Major Alarm Exist

Recovery: In the previous version, it will required RRU resetting or eNB resetting. With newcorrection, Alarm can be cleared without eNB resetting by start VSWR tuning mode and run it untilalarm is cleared.


Pre-requirements:eNB is running on RL35 MP2 load, and cells are on air without any alarms.

Test execution:1. remove the jumper cables, and VSWR major alarms and Radio resource switched off alarm

appear on the antenna line.2. return the jumper cable back.3. try to Tune VSWR threshold, and wait for about 3 minutes, and see that VSWR major alarm andRadio resource switched off are cancelled.4. exit the VSWR threshold Tune mode.

Expected results:VSWR alarm and Radio resource switched off alarm disappeared and never come back again.

Unexpected results:VSWR major alarm still there.

7/17/2019 LTE jj


LNT3.0 2.0 - <Installation Instruction> © Nokia Solutions and Networks 2014Version 1.0Confidential

1 (23)

Installation Instruction


Radio Controllers


Release: RL35 MP2



If you should have questions regarding our Environmental Policy or any of the environmental services

we offer, please contact us at Nokia Solutions and Networks for additional information.

7/17/2019 LTE jj



2 (23)

Table of Contents

1. Purpose ......................................................................................................................................................... 3

2. Overview ....................................................................................................................................................... 3

2.1 Other Relevant Installation Instructions ............................................................... ..................................................... 3

2.2 Supported Hardware and SFP ........................................................................................ ......................................... 3

3. Preparations .................................................................................................................................................. 4

4. SW downloading instructions ........................................................................................................................ 4

5. Special conditions ......................................................................................................................................... 5

5.1 Flexi Multiradio BTS LTE eNB............................................................................. ..................................................... 5

5.2 LTE iOMS ................................................................................................................................................................ 5

5.3 LTE NetAct ............................................................ ..................................................................... .............................. 5

5.4 Control PC configuration ............................................................................................................ .............................. 5

6. Release delivery upgrade instructions .......................................................................................................... 5

6.1

Flexi Multiradio BTS LTE eNB............................................................................. ..................................................... 5 6.2 Using Site Manager to upgrade SW .................................................................... ..................................................... 6

6.3 Using NetAct ..................................................................... ..................................................................... .................. 7

7. iOMS ........................................................................................................................................................... 14

7.1 First Installation ................................................................. ..................................................................... ................ 15

7.2 Upgrade from iOMS3.0 (R_GOMS6_1.27.1.1 Corr35) to iOMS5.0 ................................................................... ..... 15

7.3 Upgrade from iOMS4.0 (R_GOMS6_1.82.1.0 corr37) to iOMS5.0.................................................................... ..... 19

7.4 Upgrade iOMS5.0 to corr24 ................................................................................ ................................................... 19

7.5 Upgrade iOMS5.0 corr24 to corr38 ............................................................................................ ............................ 20

7.6 SON ....................................................................................................................................................................... 21

8. Operational hints and recommendations .................................................................................................... 21

9. Checking of the package consistency ........................................................................................................ 22

9.1 Flexi Multiradio BTS LTE eNB............................................................................. ................................................... 22

9.2 LTE iOMS .............................................................................................................................................................. 22

10.

Fallback ....................................................................................................................................................... 22 11. Appendices / References ............................................................................................................................ 22


Summary of changes:

<16-July-2014> 0.1 Creation date

<21-July-2014> 1.0 Approval date

7/17/2019 LTE jj



3 (23)

1. PURPOSE

The purpose of this document is to describe the actions needed for installing and or upgradingthis Release Delivery into the customer’s network.

2. OVERVIEW

This document covers Installation Instruction for 2 LTE entities:

• Flexi Multiradio BTS LTE (eNB)

• LTE iOMS And informs about preparations needed to use SON (Self Organizing Network) features.Standard installation instructions are available in the Customer Documentation libraryaccessible through NOLS [1] at:

• Nokia Long Term Evolution Information Center [3]

It is required to carefully study content of the library and follow on detailed procedures describedin the documents. It will be specified in this document which instruction should be used forinstallation of certain entity, all exceptions from base procedure will be listed in this document.During the execution of the procedure user will be asked to stop following the official CustomerDocumentation and execute steps mentioned here.

2.1 Other Relevant Installation Instruct ions

All LTE Customer Documentation, including standard installation procedures, is accessiblethrough NOLS [1] in the section “Product Information Center”Nokia Long Term Evolution Information Center [7]

It is very important to check if new Change Deliveries are available – they may contain newerversion of the documents

2.2 Suppor ted Hardware and SFP

The supported Hardware version as below:

Hardware Supported Hardware

FZHA A101, A102, A103, A104

FZNC A101, A102

FZNI A101FSMF A101, A102, A103

FBBA A101, A102, A103

Note: According to maintenance policy, X version proto type HW are not supported inmaintenance phase.

https://online.portal.nsn.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:134-007609&RId=urn:temp:Flexi-TD-LBTS3.0&CId=urn:temp:Operating-documentation&FId=

https://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:134-007609

https://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:134-007609

https://online.portal.nsn.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:134-007609&RId=urn:temp:Flexi-TD-LBTS3.0&CId=urn:temp:Operating-documentation&FId=

7/17/2019 LTE jj



4 (23)

3. PREPARATIONS

1. Hardware used for the installation should be integrated according to the hardware installation guide and allnecessary cabling should be already done. Necessary documents can be found in the section “Install andcommission” in the Customer Documentation library• For the Flexi Multiradio BTS LTE reference documents are named “Installing Flexi Multiradio BTS LTE…” [2](Figure 1)

Figure 1

4. SW DOWNLOADING INSTRUCTIONS

Software for the eNB and iOMS can be downloaded from NOLS:

• Flexi Multiradio BTS LTE:

https://online.portal.nsn.com/SWD/?access_key=MTA2OTY2

• LTE iOMS:

RL50 1.0: LN5.0 RL50 1.0 SW

https://online.portal.nsn.com/SWD/?access_key=MTA4NDQ1

RL50 1.1: LN5.0 RL50 1.1 SW

https://online.portal.nsn.com/SWD/?access_key=MTA3Nzg1

RL50 1.2: LN5.0 RL50 1.2 SW

https://online.portal.nsn.com/SWD/?access_key=MTA2OTI2

https://online.portal.nokiasiemensnetworks.com/









https://online.portal.nokiasiemensnetworks.com/

7/17/2019 LTE jj



5 (23)

5. SPECIAL CONDITIONS

5.1 Flexi Multiradio BTS LTE eNB

NA

5.2 LTE iOMS

Before starting the iOMS installation the HW clock in the BIOS of the unit, where software is to beinstalled should be corrected to reflect current time in UTC/GMT time zone.

5.3 LTE NetAct

LTE NetAct should to be upgrade to OSS5.5 in advance.

Enable “swUpdateEvent” configuration flag in NetAct tool:Enable “swUpdateEvent” is used to trigger SW download again to LTE eNB when RF module SW doesn’tmatched during eNB upgrade with NetAct. This will trigger eNB restart automatically.

Notes: this function flag is controlled by NetAct server side.

5.4 Control PC configuration

If Control PC is directly connected to the eNB by LMP interface, PC must be set up with IP address &subnet as follows:1) IP address: 192.168.255.1262) Network mask: 255.255.252.0

FZNI1 192.168.253.196

FZNI2 192.168.253.204

FZNI3 192.168.253.212

FZNI4 192.168.253.220

FZNI5 192.168.253.228

FZNI6 192.168.253.236

If Control PC is remote connected to the eNB, you just make sure that it can access the M-planeapplication IP address of the eNB.

If you use BTSSM to do SWDL, please make sure the matching BTSSM has been installed well.

6. RELEASE DELIVERY UPGRADE INSTRUCTIONS


Following Upgrade Paths have been verified in lab:

• RL35 P8(LNT3.0_ENB_1304_243_02)MP2

site configurations are:

7/17/2019 LTE jj



6 (23)

FSMF+FZNC

FSMF+FZHA

• RL35 PP1.1(LNT3.0_ENB_1304_251_03)MP2

site configurations are: FSMF+FZNI

FSMF+FZNC

FSMF+FZHA

• RL35 MP1(LNT3.0_ENB_1304_251_02)MP2

site configurations are: FSMF+FZHA

FSMF+FZNC

FSMF+FZNI

6.2 Using Site Manager to upgrade SW

• eNB is running on air with old Software version.

• Select the Software on menu bar; click Update SW to BTS Site.Browse the file folder, and

choose the desired software version.

7/17/2019 LTE jj



7 (23)

• Click the Update button to do the upgrade. We can monitor the upgrade progress; the

elapse time of downloading files is about 10 minutes. Then the eNB will restart.

• After the eNB startup, login BTSSM, the eNB should be at on air status.

6.3 Using NetAct

Pre-checking before SW upgrade:

7/17/2019 LTE jj



8 (23)

1. Before the SW upgrade, check and make sure that eNBs are working normally with existing SW build.

2. Make sure that eNBs have already been integrated normally to the correct iOMS/NetAct, and make sure thateNBs can be managed by NetAct normally

3. Start NetAct/Adiministration/Software Manager tool:

4. The eNBs to be upgraded shall be viewed via this tool:

7/17/2019 LTE jj



9 (23)

5. Try to get the active SW running in eNBs by initiating an SW upload task via this tool, following picture shows

the steps:

6. From task table, the SW upload task can be viewed and monitored:

7. After SW version upload, the running SW build can be shown via this tool:

7/17/2019 LTE jj



10(23)

8. Import the new SW build into NetAct, this SW build will be used to upgrade the eNBs later

7/17/2019 LTE jj



11(23)

SW upgrade:

9. In order to upgrade the target eNBs, a task shall be started manually

From task table, the SW DA task can be viewed and monitored:

10. Several minutes later(after OMS has downloaded the SW to its local folder, OMS will send a message toeNBs to initial SW update), check the local BTSSM connected to the eNB, the following message windowshall pop out:

7/17/2019 LTE jj



12(23)

11. About 20 minutes later, SW upgrade will finish, eNBs will reboot automatically and also BTSSM reconnected,following message window will be shown on BTSSM:

The following message window may be pop out to reminder the operator to update the BTSSEM version:

Then, normally the eNB will startup with new SW build.

12. After finishing upgrade, NetAct will automatically schedule an SW upload task, the purpose is to upload thelatest eNBs’ SW build 20 minutes later after SW activation:

7/17/2019 LTE jj



13(23)

13. After SW upload task finished, the eNBs’ SW build information have been updated to NetAct:

7/17/2019 LTE jj



14(23)

7. IOMSRemark 1:

If upgrade/update procedure is executed remotely it is recommended to have additional remote connection toStandard Integrated Lights-Out (iLO) management functions for HP ProLiant Blade via iLO management port.iLO allows additional access to blade server serial, text-based console. It gives possibility to monitor and restartblade even when standard access is not available.

Please test the possibility of remote access to blade via iLO before starting of iOMS upgrade/update procedure.

Remark 2:

Possible system crash and continuous reset during major LTE iOMS SW upgrade commit phase

iOMS system may be affected by I/O buffer overload which results in kernel crash and system reset. If thishappens during MSU (Major Software Upgrade) commit phase it will cause outage and continuous reset of iOMS.

To prevent I/O buffer overload before MSU commit phase it is advised to change maximum available speed forsynchronization to 15000.

To reduce RAID synchronization speed please execute following command from root account:# echo “15000” > /proc/sys/dev/raid/speed_limit_max

To check if change was successful please execute:cat /proc/sys/dev/raid/speed_limit_max

More details will be provided in Technical Support Note:TS-LTE_iOMS-SW-0017: Possible system crash and continuous reset during major LTE iOMS SW upgradecommit phase

7/17/2019 LTE jj



15(23)

7.1 First Installation

For more detail information about iOMS, please refer to documents in NOLS

Please access it from here:

https://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:134-004636&RId=urn:temp:iOMS5.0&CId=&FId=

HW Specification:- HPBlade G6- HPBlade G8- HDD 2x300GB

Download USB_full_R_GOMS6_1.107.1.0.release_oms.corr16_2x300_G8_HPBladeBelow files should be included.

InstallGOMS_USB.shrestoretools.tgzUSB_full_R_GOMS6_1.107.1.0.release_oms.corr16_2x300_G8_HPBlade.tar.gzUSB_full_R_GOMS6_1.107.1.0.release_oms.corr16_2x300_G8_HPBlade.tar.gz.md5sum

1 Prepare USB installation stick by using iOMS4.0 FP_USBboot_v2.5.7, the file size is 765845KB inwindows from NOLS. Copy the iOMS software to the USB stick.

2 Mount the USB stick, copy the installation script. Then start installation script by./InstallGOMS_USB.sh

3 .Wait for script finished, and remove USB stick, and reboot iOMS. After iOMS is running, go to belowfolder and complete the installation.cd /opt/Nokia/SS_OMSINST/usb/./CompleteGOMS_USBInstallation.sh

After this step you will be prompted to enter the necessary parameters.

4.Reboot again to finish installation.

7.2 Upgrade from iOMS3.0 (R_GOMS6_1.27.1.1 Corr35) to iOMS5.0

1 Transferring MSU file to OMS

1.1 MSU archive contentMSU image is delivered as *.zip file containing:

• MSU itself,

• partitions description,

• md5 sum file for MSU image,

• amsurt_std installation scripts package

• amsurt script

Separate targetBD files for R_GOMS6_1.27.1.1 and R_GOMS6_1.82.1.0 delivered as .tgz file:R_GOMS6_1.27.1.1

• targetBD_R_GOMS6_1.27.1.1.c20_to_R_GOMS6_1.107.1.0.oms64.c16_G6_HPBlade.tgz


R_GOMS6_1.82.1.0



https://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:134-004636&RId=urn:temp:iOMS5.0&CId=&FId




7/17/2019 LTE jj



16(23)

1.2 Copying MSU fileMSU may be transferred to OMS using SFTP, SCP FTP or USB stick.

MSU packages should be copied to /var/mnt/local/backup/ as in this directory usually is a lot of free diskspace.Note that proper for OMS release targetBD zip file need to be copied to amsurt_std directory andunpacked, example below.

1.3 Unpacking MSU fileTo unpack MSU file, simply execute:unzip <msu_file_name>

To unpack targetBD file, simply execute:tar xvf <targetBD_file_name>Note that compressing with zip doesn’t save permissions so after unzipping you have to add executepermission to all amsurt scripts.

1.4 Checking amsurt_std content

For R_GOMS6_1.82.1.0 and R_GOMS6_1.27.1.1 amsurt_std directory should contain:• MSU .tgz

• MSU .md5

• data/ folder

• omsswm_major script

• partitionsSchema.tgz

• proper targetBD .xml

• proper targetBD .md5

2 Installing MSUBefore you start check if you have technology licence installed on RL30. You should not have it installedand you can verify this using command lmcli listAllLicence. If you have technology licence you shoulddelete it using lmcli deleteLicence <LicenceFilename> before starting MSU procedure.

2.1 Performing pre installation checkGo to directory with MSU file:cd /var/mnt/local/backup/amsurt_std/To check if MSU can be installed on OMS, execute command:./omsswm_major --check <targetDB file>Results will be displayed on screen and stored in /var/log/msu.log

2.2 Installing in two steps: install – activateThis scenario should be normally in use.Go to directory with MSU file:cd /var/mnt/local/backup/amsurt_std/Execute MSU installation:./omsswm_major <targetDB file>

Logs from operation will be stored in /var/log/ directory.Wait until installation is done. If it’s finished successfully you can activate new software set. WARNING –this will cause OMS reboot twice../omsswm_major --activate <targetBD file> After OMS reboots postconfiguration is done automatically in silent mode.

2.3 Installing in single stepThere is an option to install MSU completely handsfree. In this scenario installer will not interact withoperator and will not wait for activation command. OMS will reboot automatically, when installation isdone.Go to directory with MSU file:cd /var/mnt/local/backup/amsurt_std/To start upgrading OMS this way, execute:./omssm_major --full <targetBD file>

7/17/2019 LTE jj



17(23)

After OMS reboots postconfiguration is done automatically in silent mode.

2.4 Installing step by stepThis gives you more control over installation process.Go to directory with MSU file:cd /var/mnt/local/backup/amsurt_std/Break disk mirroring:./omsswm_major --separate --disk <disk name>Disk names are:/dev/cciss/c0d0//dev/cciss/c0d1/By default /dev/cciss/c0d1/ is used. It is recommended to use default settings.Install MSU:./omsswm_major --install <targetBD_xx.xml file>Convert data:./omsswm_major --convert <targetBD_xx.xml file> Activate new software (WARNING – this will cause OMS reboot twice):

./omsswm_major --activate <targetBD_xx.xml file> After OMS reboots postconfiguration is done automatically in silent mode.

3 Using execution switches

3.1 Error checkingOMS checks for following errors after activation phase is executed:

• Postconfiguration – OMS checks if postconfiguration is executed successfully.

• Network settings – OMS checks its network settings.

• RG’s and RU’s – Oms checks if all RG’s and RU’s are unlocked and enabled.

• Network security – OMS checks if network security related information were converted successfully and

imported to new software set

• Licence files – OMS checks if licence files were imported to new software set

• NWI3 connection – OMS checks if NetAct connection can be established

• BTSOM connection – OMS checks if is able to accept requests from RNC

If any of listed above fails, OMS will trigger automatic fallback to previous version. Automatic fallback requires Recovery Groups to be manually unlocked after fallback is done.You can do it by command:fshascli --unlock --noerror /You can verify MSU procedure in /var/log/msu.log and see if any errors occurred.When automatic postconfiguration starts in RU40 you log is in /var/log/postconfig*.log

3.2 Ignoring all errorsIt is possible to ignore all errors and disable automatic fallback. It is not recommended to do so.Ignoring errors in single step scenario:./omsswm_major --full --noHLF <targetBD file>In any other case:./omsswm_major --activate --noHLF <targetBD file>

3.3 Ignoring NetAct connection problemsIt is possible to ignore problems with NetAct connection. This option should be used, when there is noNetAct available for any reason.Ignoring NetAct problem in single step scenario:./omsswm_major --full --noNetActchecking <targetBD file>In any other case:./omsswm_major --activate -- noNetActchecking <targetBD file>

3.4 Locking non default diskIt is possible to point, which disk will be locked during upgrade. In normal cases it is recommended to usedefault value.

7/17/2019 LTE jj



18(23)

Using switch in single step scenario:./omsswm_major --full --disk <disk name> <targetBD file>

In step by step scenario:./omsswm_major --separate --disk <disk name>

4 Additional conversion scriptsIf some additional conversion scripts are needed, they are always delivered together with MSU. Scriptsare stored in conversionScripts.zip file. Scripts are handled completely handsfree. There is no need foroperator to take any action regarding these scripts.

5 Committing new so ftware After MSU new software is not committed automatically. Commit has to be done by operator. Beforecommitting, make sure, that new OMS is working properly. After commit rollback is not possible.To commit, execute:omsswm_major -c

6 Rollback

Rollback can be performed manually with command:fsswcli --major --cutoverRollback requires Recovery Groups to be manually unlocked after rollback is done.You can do it by command:fshascli --unlock --noerror /

OMS upgrade step by step example:1. Download MSU image file to local from Tosco server via winSCP tool(set transfer mode as binary);

Figure 26: download file from server with tool

2. Upload MSU image file to OMS /var/mnt/local/users/home/Nemuadmin via winSCP tool(set transfer

mode as binary);

7/17/2019 LTE jj



19(23)

Figure 27: set transfer mode as binary

3. SSH to OMS as root user;4. mkdir /var/mnt/local/backup/amsurt_std;5. cd /var/mnt/local/backup/amsurt_std/;6. mv /home/Nemuadmin/MSU_image_file /var/mnt/local/backup/amsurt_std/;7. tar xvf targetBD_***.tgz;8. ./omsswm_major --check targetBD_***.xml;9. ./omsswm_major --separate --disk <disk name>;

10. ./omsswm_major --install targetBD_***.xml;11. ./omsswm_major --convert targetBD_***.xml;12. ./omsswm_major --activate targetBD_***.xml;13. After activate, some process will be startup within 20 minutes, please check whether new OMSsoftware is working properly,1) If yes, you need to commit new software with command “omsswm_major –c”2) If no, rollback can be performed with command “fsswcli --major --cutover” and “fshascli --unlock --noerror /”;

7.3 Upgrade from iOMS4.0 (R_GOMS6_1.82.1.0 corr37) to iOMS5.0

As above

7.4 Upgrade iOMS5.0 to corr24

NOTICE: the correction can be upgrade after MSU upgrade with executed command“omsswm_major –c”.

1. Install 1 correction level.

Files needed for the update are:targetBD_R_GOMS6_1.107.1.0.release_oms.corr17.xmlR_GOMS6_1.107.1.0.release_oms.corr17.tar

Install correction and create new SW Set (new SW Set will be passive):omsswm_install --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr17.xml Activate SW Set:

7/17/2019 LTE jj



20(23)

omsswm_activate --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr17.xml

2. Install more that 1 correction level.For the following example R_GOMS6_1.107.1.0.release_oms.corr16 is installedand update is being done to R_GOMS6_1.107.debug_oms.corr24. Files needed for the update are:R_GOMS6_1.107.1.0.release_oms.corr17.tarR_GOMS6_1.107.1.0.release_oms.corr18.tarR_GOMS6_1.107.1.0.release_oms.corr19.tarR_GOMS6_1.107.1.0.release_oms.corr20.tarR_GOMS6_1.107.1.0.release_oms.corr21.tarR_GOMS6_1.107.1.0.release_oms.corr22.tarR_GOMS6_1.107.1.0.release_oms.corr23.tarR_GOMS6_1.107.1.0.release_oms.corr24.tar

targetBD_R_GOMS6_1.107.1.0.release_oms.corr24.xml

Install multiple corrections and create new SW Set (new SW Set will be passive):

omsswm_install --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr24.xml Activate SW Set:

omsswm_activate --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr24.xml

* Note, in case of the correction is need to downgrade, then Files needed - only one xml file to correctionlevel you want to downgrade, like:

targetBD_R_GOMS6_1.107.1.0.release_oms.corr16.xml

Uninstall corrections and create new SW Set (new SW Set will be passive):omsswm_install --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr16.xml

Activate SW Set:omsswm_activate --full targetBD_R_GOMS6_1.107.1.0.release_oms.corr16.xml

7.5 Upgrade iOMS5.0 corr24 to corr38

Download SW from following three links to get correction 25 to correction 38.

RL50 1.0: LN5.0 RL50 1.0 SW


RL50 1.1: LN5.0 RL50 1.1 SW


RL50 1.2: LN5.0 RL50 1.2 SW


Check SH1 check sum of the downloaded files..Unzip all archives R_GOMS6_1.107.1.0.release_oms.corrXX.zip and install the corrections Corr25 toCorr38:Files needed for update are:R_GOMS6_1.107.1.0.release_oms.corr25R_GOMS6_1.107.1.0.release_oms.corr26R_GOMS6_1.107.1.0.release_oms.corr27R_GOMS6_1.107.1.0.release_oms.corr28R_GOMS6_1.107.1.0.release_oms.corr29R_GOMS6_1.107.1.0.release_oms.corr30R_GOMS6_1.107.1.0.release_oms.corr31R_GOMS6_1.107.1.0.release_oms.corr32R_GOMS6_1.107.1.0.release_oms.corr33R_GOMS6_1.107.1.0.release_oms.corr34







7/17/2019 LTE jj



21(23)

R_GOMS6_1.107.1.0.release_oms.corr35R_GOMS6_1.107.1.0.release_oms.corr36

R_GOMS6_1.107.1.0.release_oms.corr37R_GOMS6_1.107.1.0.release_oms.corr38

targetBD_ R_GOMS6_1.107.1.0.release__oms.corr38.xmlFor all needed files there must be a checksum file with the same file name but extension ‘md5’. Pleasedo not change this file, it has to be in UNIX format and will be used by the installation procedure.Install multiple corrections and create new SW Set :omsswm_install --full targetBD_ R_GOMS6_1.107.1.0.release_oms.corr38.xmlomsswm_activate --full targetBD_ R_GOMS6_1.107.1.0.release_oms.corr38.xml

If during activation following error will appear:OMS will be restarted after successful activation...CRITICAL error: FlexiPlatform activation script returned error code: 1Please use following workaround:Unpack corr tar files to obtain postupgrade scripts and copy it to iOMS

Activate corr using fsswcli activation scriptfsswcli --set --activate R_GOMS6_1.107.1.0.release_oms.corr38

after reboot run Post-upgrade activation scripts one by one with approximately 30 sec interval.Important:Please carefully check name of script. It should be:R_GOMS6_1.107.1.0.release_oms.corrXXX_postsh_upgrade.sh• “ R_GOMS6_1.107.1.0.release_oms.corr25_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.corr26_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.corr27_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.corr28_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.corr29_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.cor r30_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.cor r31_postsh_upgrade.sh”

• “ R_GOMS6_1.107.1.0.release_oms.cor r32_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.corr33_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.corr34_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.corr35_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.corr36_postsh_upgrade.sh”• “ R_GOMS6_1.107.1.0.release_oms.corr38_postsh_upgrade.sh”

7.6 SON

SON is a set of features which enables operator to configure base station by connecting it to thenetwork. To enable usage of SON facilities some preparation steps must be taken. It isdescribed in Customer Documentation library in section “Functional Area Description-

Operability-Configuration Management-SON management” chapter 4 “SON management” [5].Main activities concern DHCP server configuration and certificates management.Descriptions and hints about SON feature usage can be found also in Customer Documentationfor NetAct.

8. OPERATIONAL HINTS AND RECOMMENDATIONS

N/A

7/17/2019 LTE jj



22(23)

9. CHECKING OF THE PACKAGE CONSISTENCY


In order to check the package consistency after Flexi Multiradio BTS LTE SW update, pleaseensure that the procedure “Update SW to BTS site” is terminating successfully.

9.2 LTE iOMS

Chapter 6 “Performing checks after installation and commissioning of iOMS” from “Installing andcommissioning LTE iOMS” [6] document contains steps, which should be executed to doublecheck if the installation of iOMS was finished successfully. Document is available in theCustomer Documentation library.

10. FALLBACK

N/A


[1] NOLS - Nokia Online Services log in link:https://online.portal.nsn.com[2] "Commissioning Flexi Multiradio BTS LTE", DN0972163, Issue 02[3] Link to Nokia Long Term Evolution Information Center:https://online.portal.nsn.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:134-007609&RId=urn:temp:Flexi-TD-LBTS3.0&CId=urn:temp:Operating-documentation&FId= [4] "Upgrading from LTE OMS 3.0 or LTE OMS 4.0 to LTE OMS 5.0", DN0983101, Issue 01[5] "LTE System Upgrade", DN09147545, Issue 01[6] "Installing and Commissioning LTE iOMS", DN0956464, Issue 05A[7] Nokia Online Services TD-LTE LNT3.0 customer documentation:https://online.portal.nsn.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:134-007609

https://online.portal.nsn.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:134-007609&RId=urn:temp:Flexi-TD-LBTS3.0&CId=urn:temp:Operating-documentation&FId


https://online.portal.nsn.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:134-007609






7/17/2019 LTE jj



23(23)

Disclaimer











7/17/2019 LTE jj


LNT3.0 2.0 - <SW update Verification Report> © Nokia Solutions and Networks 2014Version 1.0Confidential

1 (5)

SW update Verification Report


Radio Controllers


Release: RL35 MP2




7/17/2019 LTE jj


LNT3.0 2.0 - <SW update Verification Report > © Nokia Solutions and Networks 2014Version 1.0Confidential

Company Confidential

2 (5)

Table of Contents

1. Purpose ....................................................................................................................................... 3

2. Test phases and Amount of test cases ........................................................................................ 3

3. Test Environment ........................................................................................................................ 3

4.

Description of test phase entities ................................................................................................. 3

5.

Appendices / References............................................................................................................. 4


Summary of changes:

<16-July-2014> 0.1 Creation date

<21-July-2014> 1.0 Approval date

7/17/2019 LTE jj




3 (5)

1. PURPOSE

This document presents the testing results for LTE RL35 MP2 release delivery..

2. TEST PHASES AND AMOUNT OF TEST CASES

The following table summarizes the amount of test cases.

Test Phase Total Passed Passed Rate

Correction Testing 56 56 100%

Regression Testing 317 317 100%

Software UpdateInstallation Testing

338 338 100%

Note: FiVe test cases are all passed and KPI performance is same as P8’s.

3. TEST ENVIRONMENT

Test environment is build according to chapter “System Descriptions” [1] inCustomer Documentation library

4. DESCRIPTION OF TEST PHASE ENTITIES

Correction Testing All individual corrections have passed sub-system testing. All individual corrections have passed entity testing.

Regression TestingRegression test verifies the unchanged parts of a product after parts of the producthave been changed. It is a way to ensure that the change did not affect anything elseand that there are no unexpected side effects.

Software Update Installation TestingThe target is to validate that the entity in an older version can be updated as expectedto the version to be released.Update was tested from RL35 P8//MP1/PP1.1 to RL35 MP2.0.

7/17/2019 LTE jj




4 (5)


[1] “System Descriptions “consists of: “LTE RAN and EPC System Description”DN0993921

7/17/2019 LTE jj


Disclaimer

The information in this document applies solely to the hardware/software product (“Product”) specifiedherein, and only as specified herein.

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and itmay not be used except for the purposes defined in the agreement between You and Nokia Solutionsand Networks (“Agreement”) under which this document is distributed. No part of this document maybe used, copied, reproduced, modified or transmitted in any form or means without the prior writtenpermission of Nokia Solutions and Networks. If you have not entered into an Agreement applicable tothe Product, or if that Agreement has expired or has been terminated, You may not use this documentin any manner and You are obliged to return it to Nokia Solutions and Networks and destroy or deleteany 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 Solutions and Networks welcome Your comments aspart 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 statementsconcerning the suitability, capacity, fitness for purpose or performance of the Product are given solelyon an “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves theright to change any such information and statements without notice. Nokia Solutions and Networks hasmade all reasonable efforts to ensure that the content of this document is adequate and free ofmaterial errors and omissions, and Nokia Solutions and Networks will correct errors that You identify inthis document. But, Nokia Solutions and Networks' total liability for any errors in the document is strictlylimited to the correction of such error(s). Nokia Solutions and Networks does not warrant that the useof 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 TOTHE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKSBE LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT,INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITEDTO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY ORDATA 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 Solutions and Networks’ proprietary and confidential information, which maynot be distributed or disclosed to any third parties without the prior written consent of Nokia Solutionsand Networks.

NSN is a trademark of Nokia Solutions and Networks Oy. Nokia is a registered trademark of Nokia

LTE jj

Documents