lte rl50fz 0.1 release documentation

8/15/2019 LTE RL50FZ 0.1 Release Documentation

http://slidepdf.com/reader/full/lte-rl50fz-01-release-documentation 1/50

LTE_RL50FZ_0.1 – Release Documentation - / 1 Version 1.0Confidential

© Nokia Solutions and Networks 2014

Contact

Contact your local Nokia Solutions and Networks support

Summary of changes:

30-Sept-2014 1.0 Approved version

LNF5.0 0.1 Maintenance Release

Base Stations

Flexi Zone BTS

LNF5.0 0.1

LTE_RL50FZ_0.1

Document name:

LTE_RL50FZ_0.1 Summary of corrections and enhancements

LTE_RL50FZ_0.1 Impact Document

LTE_RL50FZ_0.1 Change Note Forms

LTE_RL50FZ_0.1 Installation Instructions

LTE_RL50FZ_0.1 SW Update Verifi cation Report

Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its

products and services. We would like to encourage you as our customers and users to join us in 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.



LTE_LNF5.0_0.1 - Summary of Corrections and Enhancements - Page 1/21 © Nokia Solutions and Networks 2014Version 1.0Confidential

Summary of Corrections andEnhancements

Id: LTE_LNF5.0_0.1Product Family: Base Stations

Product: Flexi Zone BTS

Release: LNF5.0 0.1Release Delivery: RL50FZ 0.1

Approved version: 30-Sept-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 the recommendationsfor power use and proper disposal of our products and their components.





Table of Contents1. CORRECTIONS ............................................................................................................................................ 3 2. NEW / CHANGED FUNCTIONALITY ........................................................................................................... 4 3. PREVIOUS DELIVERIES FOR THE RELEASE ......................................................................................... 20 4. RELEASED OBJECTS ................................................................................................................................ 20 5. APPENDICES / REFERENCES.................................................................................................................. 20

ContactContact your local Nokia Solutions and Networks support

Summary of changes





Purpose

The purpose of this document is to give a brief summary on the RL50FZ 0.1 SW Deliverycorrections content.

1. CORRECTIONS

Pronto ID Title

118221ESPE04 * RL50: SW upgrade from one load to the same should not be processed

85615ESPE03 Cell doesn't get disabled when VSWR major alarm is raised

NA05685936 RL50 Flexi Zone: VSWR alarm active for some sites- the sites are not on-air

146040ESPE02 Auto Config / Auto Connection fails to properly commission TRS.

NA05681287 Paging messages cannot be sent sometimes to UE in a weak/strong electric field.

NA05704730 NPI:RL50FZ -Problem it is not possible to recommissioning BTS_ID

* - see special conditions in Installation Instructions document, section 5 and 6.2.




LTE27

Open loop ULpower control

and DL power

setting

Basic LTE call

handling and

interworking

RELEASED

LTE28Closed loop UL

power control

Coverage,

capacity and

peak rates

RELEASED

LTE30CQI adaption

(DL)

Coverage,

capacity and

peak rates

RELEASED

LTE31Link adaptation

by AMC (UL/DL)

Coverage,

capacity

and

peak

rates

RELEASED

LTE37 Ciphering

Basic LTE call

handling and

interworking

RELEASED

LTE38

Integrity

protection

Basic LTE call

handling andinterworking

RELEASED

LTE39

System

information

broadcast

Mobility RELEASED

LTE40

Physical &

transport

channels

Basic LTE call

handling and

interworking

RELEASED

LTE41

PDCP, RLC &

MAC support

Basic LTE call

handling andinterworking

RELEASED

LTE42

DRX in RRC

connected

mode

QoS, services

and end user

experience

RELEASED

LTE43Support of 64

QAM in DL

Coverage,

capacity and

peak rates

RELEASED




LTE45Fair scheduler

(UL/DL)

Basic LTE call

handling and

interworking

RELEASED

LTE46Channel-aware

Scheduler (UL)

Coverage,

capacity and

peak rates

RELEASED

LTE48Support of High

Speed Users

Basic LTE call

handling and

interworking

RELEASED

LTE49 Paging

Basic LTE call

handling and

interworking

RELEASED

LTE50UE state

management

Basic LTE call

handling and

interworking

RELEASED

LTE51Cell selection

and re-selectionMobility RELEASED

LTE53Intra and intereNB handover

with X2

Mobility RELEASED

LTE54Intra-LTE

handover via S1Mobility RELEASED

LTE55Inter-frequency

handoverMobility RELEASED

LTE56

Inter RAT

handover to

WCDMA

Mobility RELEASED

LTE68

Support of cell

based location

service

QoS, services

and end user

experience

RELEASED

LTE69

Transmit

diversity for two

antennas

Coverage,

capacity and

peak rates

RELEASED

LTE70

Downlink

adaptive open

loop MIMO for

two antennas

Coverage,

capacity and

peak rates

RELEASED




LTE712-way RX

diversity (MRC)BTS Site Solution RELEASED

LTE80GPS

synchronisationBTS Site Solution RELEASED

LTE81Cell range up to

14.5 kmBTS Site Solution RELEASED

LTE112 Cell Bandwidth -

20 MHz

BTS Site SolutionRELEASED

LTE113 Cell Bandwidth -15 MHz

BTS Site Solution RELEASED

LTE114Cell Bandwidth -

10 MHzBTS Site Solution RELEASED

LTE115Cell Bandwidth -

5 MHzBTS Site Solution RELEASED

LTE118

Fast Ethernet

(FE) / Gigabit

Ethernet (GE)

electrical

interface

Transmission RELEASED

LTE119

Gigabit Ethernet

(GE) optical

interface


LTE129

Traffic

prioritization on

Ethernet layer


LTE131

Traffic

prioritization on

IP layer(Diffserv)


LTE132

VLAN based

traffic

differentiation


LTE134Timing over

PacketTransmission RELEASED

LTE138Traffic shaping

(UL)Transmission RELEASED




LTE140 Ethernet OAM Transmission RELEASED

LTE144

Transport

admission

control


LTE147LTE Hardware

Management

Configuration

ManagementRELEASED

LTE150

LTE OAM

Transport LayerSecurity (TLS)

Support

O&M Security RELEASED

LTE153LTE BTS Site

Manager

Network

AdministrationRELEASED

LTE154

SON LTE BTS

Auto

Connectivity

Configuration

ManagementRELEASED

LTE158NTP clock time

synchronization

Supplementary

O&M featuresRELEASED

LTE162Cell Trace with

IMSI

Network

Monitoring and

Maintenance

RELEASED

LTE163

Subscriber and

Equipment

Trace

Network

Monitoring and

Maintenance

RELEASED

LTE187Single TX path

mode

Basic LTE call

handling and

interworking

RELEASED

LTE423

RRC connection

release with

redirect

Mobility RELEASED

LTE424

Automatic

interface alarm

correlation

Network

Monitoring and

Maintenance

RELEASED

LTE430

DL power

boosting for

control channels

Coverage,

capacity and

peak rates

RELEASED




LTE432Cell Outage

Detection

NetworkMonitoring and

Maintenance

RELEASED

LTE433 Cell Trace

Network

Monitoring and

Maintenance

RELEASED

LTE440S1 Overload

Handling

Basic LTE call

handling and

interworking

RELEASED

LTE442

Network

Assisted Cell

Change to GSM

Mobility RELEASED

LTE450MME capacity

value change

Basic LTE call

handling and

interworking

RELEASED

LTE459

LTE Timing

Advance

Evaluation

Network

Monitoring and

Maintenance

RELEASED

LTE468PCI

management

Configuration

ManagementRELEASED

LTE473Extended DRX

settings

QoS, services

and end user

experience

RELEASED

LTE475Automatic iOMS

resiliency

OMS specific

featuresRELEASED

LTE482

DNS support for

certificate

examination

Supplementary


LTE487

Idle mode

mobility load

balancing

Mobility RELEASED

LTE490

Subscriber

profile based

mobility

Mobility RELEASED

LTE492 ANRConfiguration

ManagementRELEASED




LTE494

Commercial

Mobile Alert

System

QoS, services

and end user

experience

RELEASED

LTE496Support of QCI

2, 3 and 4

QoS, services

and end user

experience

RELEASED

LTE497

Smart

Admission

Control

QoS, services

and end user

experience

RELEASED

LTE502Cell Outage

triggered reset

Network

Monitoring and

Maintenance

RELEASED

LTE507

InterRAT

neighbor

relation

Optimization

(LTE, UTRAN,

GERAN)

Configuration

ManagementRELEASED

LTE510

Synchronization

of InterRAT

neighbors

Configuration

ManagementRELEASED

LTE511Intra cell


LTE518Operator

specific QCI

QoS, services

and end user

experience

RELEASED

LTE519eRAB

Modification

QoS, services

and end user

experience RELEASED

LTE522 S1 partial reset

Basic LTE call

handling and

interworking

RELEASED

LTE523

Multi-layered

Certificate

Authorities


LTE524

Certificate

Management

for iOMS

OMS specific

featuresRELEASED




LTE533Mobility

Robustness

Configuration

ManagementRELEASED

LTE534

ARP-based

Admission

Control for E-

RABs

QoS, services

and end user

experience

RELEASED

LTE539 Central ANRConfiguration

ManagementRELEASED

LTE550

Radio

parameter

online

changeable

Configuration

ManagementRELEASED

LTE559SW Monitoring

Module for LTE

Configuration

ManagementRELEASED

LTE562

CSFB to UTRAN

or GSM via

redirect

Mobility RELEASED

LTE568

DL adaptive

closed loop

MIMO (4x2)

Coverage,

capacity and

peak rates

RELEASED

LTE570Periodic UE

measurements

Supplementary

RRM functionsRELEASED

LTE571

Controlled

uplink packet

segmentation

Coverage,

capacity and

peak rates

RELEASED

LTE572IMS emergency

sessions

QoS, services

and end user

experience

RELEASED

LTE574

IP Transport

Network

Measurement


LTE581PRACH

management

Configuration

ManagementRELEASED

LTE585 Smart DRX

QoS, services

and end user

experience

RELEASED




LTE587

Multiple GBR

EPS Bearers per

UE

QoS, services

and end user

experience

RELEASED

LTE592Link Supervision

with BFDTransmission RELEASED

LTE593Security for

Ethernet PortsO&M Security RELEASED

LTE602

Performance

Management

Administration

Network

Monitoring and

Maintenance

RELEASED

LTE616

Usage based

PDCCH

adaptation

Coverage,

capacity and

peak rates

RELEASED

LTE619

Interference

aware UL

scheduling

Coverage,

capacity and

peak rates

RELEASED

LTE623 Crypto Agent O&M Security RELEASED

LTE644Configurable cell

trace content

Network

Monitoring and

Maintenance

RELEASED

LTE646

SW Monitoring

Extension with

PM Counters

Configuration

ManagementRELEASED

LTE651Performance

Monitoring I

Performance

MonitoringRELEASED

LTE653LTE Operability

Architecture

Network


LTE654

LTE

Configuration

Management

Configuration

ManagementRELEASED

LTE655LTE Software

Management

Configuration

ManagementRELEASED

LTE656LTE Fault

Management

Network

Monitoring and

Maintenance

RELEASED




LTE657

LTE

Performance

Management

Network

Monitoring and

Maintenance

RELEASED

LTE663

GPS location

and time

retrieval

Supplementary


LTE664LTE transport

protocol stackTransmission RELEASED

LTE665LTE Certificate

Management O&M Security RELEASED

LTE666

LTE User

Account

Management


LTE667

LTE User Event

Log

Management


LTE679

LTE Local User

Account

Management


LTE681

Windows 7

Support for

Element

Manager Client

Software

Network


LTE685

Infrastructures

for Certification

Authority (CA)

and Registration

Authority (RA)


LTE689IPSec – Bearer

and ControlTransmission

RESTRICTED

RELEASE

Limited Capacity

LTE692LTE Firewall

SupportO&M Security RELEASED

LTE703

DL adaptive

closed loop

MIMO for twoantennas

Coverage,

capacity and

peak rates

RELEASED




relations

LTE775SCTP multi-

homing (MME)Transmission RELEASED

In Feature LTE775, SCTP multi-homing(MME): SCTP multihomingasymmetric configuration (onephysical interface towards eNB andtwo physical interface towards MME)has not been tested in SystemVerification lab environment becauseof the current limitations with MME.

LTE782ANR Fully UE

based

Configuration

ManagementRELEASED

LTE783ANR InterRAT

UTRAN

Configuration

ManagementRELEASED

LTE784 ANR InterRAT

GERAN

Configuration

ManagementRELEASED

LTE786Flexible UL

Bandwidth

Coverage,

capacity and

peak rates

RELEASED

LTE788Support of 16

QAM (UL)

Coverage,

capacity and

peak rates

RELEASED

LTE793Support of 16

QAM (DL)

Coverage,

capacity and

peak rates

RELEASED

LTE796

iOMS

connectivity

increase

OMS specific

featuresRELEASED

LTE797PM Counter

Handover I

Performance

MonitoringRELEASED

LTE798PM Counter

Histograms I

Performance

MonitoringRELEASED

LTE805PM Counter

Capacity I

Performance

MonitoringRELEASED

LTE806PM Counter

Transport I

Performance

MonitoringRELEASED

LTE807

Idle mode

mobility LTE to

CDMA/1xRTT

Mobility RELEASED




LTE819

DL inter-cell

interference

generation

Supplementary

RRM functionsRELEASED

LTE829Increased uplink

MCS range

Coverage,

capacity and

peak rates

RELEASED

LTE830LTE Automatic

Lock

Configuration

ManagementRELEASED

LTE843 ETWS broadcast

QoS, services

and end user

experience

RELEASED

LTE866Fast IP

ReroutingTransmission RELEASED

LTE870

Idle mode

mobility from

LTE to

CDMA/eHRPD

Mobility RELEASED

LTE872

SRVCC to

WCDMA Mobility RELEASED

LTE873 SRVCC to GSM Mobility RELEASED

LTE875

Different IP

addresses for

U/C/M/S-plane


LTE877

Adjustable

Performance

Upload

Performance

MonitoringRELEASED

LTE882

System Upgrade

with Backward

Compatibility

Configuration

ManagementRELEASED

LTE899Antenna Line

SupervisionBTS Site Solution RELEASED

LTE905Non GBR QCI 5,

6, 7, 8 and 9

QoS, services

and end user

experience

RELEASED

LTE907 TTI bundlingCoverage,

capacity and RELEASED




peak rates

LTE913LTE NEBS

Compliant OMS

Supplementary


LTE931Ethernet Jumbo

FramesTransmission RELEASED

LTE940SW Verification

AgentO&M Security RELEASED

LTE953

MDT

(Minimization of

Drive Test)

Performance

MonitoringRELEASED

LTE962RACH

Optimization

Configuration

ManagementRELEASED

LTE971Intra-LTE

mobility offsetsMobility RELEASED

LTE984

GSM Redirect

with System

Information

Mobility RELEASED

LTE1014X2 eNB

Configuration

Update

Basic LTE callhandling and

interworking

RELEASED

LTE1019 SON ReportsConfiguration

ManagementRELEASED

LTE1034Extended Uplink

Link Adaptation

Coverage,

capacity and

peak rates

RELEASED

LTE1035

Outer loop link

adaptation for

PDCCH

Coverage,

capacity and

peak rates

RELEASED

LTE1036RSRQ based cell

reselectionMobility RELEASED

LTE1045

Full SON

Support for

Distributed Sites

Configuration

ManagementRELEASED

LTE1060TDD - FDD


LTE1073 Measurement- Mobility RELEASED




based Redirectto UTRAN

LTE1099

Event-triggered

symptom data

collection and

provisioning

Network

Monitoring and

Maintenance

RELEASED

LTE1170Inter eNode B IF

Load BalancingMobility

RELEASED

LTE1201LTE iOMS HW,

HP Blade Gen8

Supplementary


LTE1222

SON

Automation

Modes

Configuration

ManagementRELEASED

LTE1260

iOMS Certificate

update and

revocation

support

OMS specific

featuresRELEASED

LTE1340

Trace-based

Real Time

Monitoring

Performance

Monitoring

RELEASED

LTE1383

Cell Specific

neighbor

relation / PCI

handling

Configuration

ManagementRELEASED

LTE1387Intra-eNode B IF

Load BalancingMobility RELEASED

LTE1405

Remote SW-

management

and data

backup/restore

support for

iOMS

OMS specific

featuresRELEASED

LTE1407RSRQ based

redirectMobility RELEASED

LTE1442 Open access

home eNode B

mobility

Mobility

RELEASED

LTE1457 Cell trace Network RELEASED




Configurationvia

Configuration

Management

Monitoring andMaintenance

LTE1625

External

unlicensed

wireless

backhaul


LTE1626

External

licensed

wireless

backhaul

TransmissionRESTRICTED

RELEASE

Hardware maturity pending.

LTE1629

Integrated GPS

Sync for Flexi

Zone Micro BTS


LTE1659

FWGB Flexi

Zone BTS 2100

(Band 1)


LTE1682

FWHA Flexi

Zone BTS 2600

(Band 7)


LTE1686

Flexi Zone Micro

BTS

GPON/EPON

ONT SFP


LTE1687

Basic Layer3

Data Analyser

(L3DA)for LTE

Network

Monitoring and

Maintenance

RELEASED

LTE1702

Flexi Zone Micro

BTS Bluetooth

Support

Supplementary


`LTE1716

System

Introduction of

RL50FZ

Configuration

ManagementRELEASED

LTE1727

FWIB Flexi Zone

BTS 1700/2100

(Band 4)





LTE1857 Basic EthernetSwitching


LTE1885

Flexi Zone BTS

Integrated

Directional

Antenna


3. PREVIOUS DELIVERIES FOR THE RELEASE

History information for the same release deliveries. In case of generic SW, this table doesnot include customer specific deliveries.

SW update delivery Delivery type Delivery date Note

LNF5.0 Release 31.07.2014 C5

4. RELEASED OBJECTS

Software Item Software File Name SHA1 check sum

BTS Site Manager BTSSiteManager_LNF5.0_BTSSM1309_35_00.zip

1470af b60673dd01528d0acf 1416b8

f 795758271

Golden SCFFZM_Golden_Comissioning_File_ENB_1304_125_00_onwards.zip

a9a021ed20a50724f 2d1b0daf b7182

71b71b00d3

eNBLNF5.0_ENB_1304_168_00_release_BTSSM_downloadable.zip

10c40d11a7d0f 0c715d0bf 1719c1b8

b7760ab567

Flexi Zone Authentication toolsEXT_FZAUTHREL_FZAUTHREL_LNF5.0_V1.1_20140731_2.zip

a2a06553b63a6f 50937a0f 7c6c4aab

993e79632f

Flexi Zone Authentication tools archive password: A1F135F2548148C776D8BB1952052CFD8DFA27E95AA4FC98FD

5. APPENDICES / REFERENCES

The software for the released products is available in NOLS.

The newly released software can be downloaded from the direct links:

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

After downloading the software it is important to generate SH1 checksum for files andcompare it with the one provided in the Summary of Corrections and Enhancementsdocument, this will ensure that the files were not corrupted during downloading.

https://online.portal.nsn.com/








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

This document is intended for use by Nokia Solutions and Networks' customers (“You”) only, and it may not be usedexcept 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 ortransmitted in any form or means without the prior written permission of Nokia Solutions and Networks. If you have notentered into an Agreement applicable to the Product, or if that Agreement has expired or has been terminated, Youmay not use this document in any manner and You are obliged to return it to Nokia Solutions and Networks anddestroy 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 thesuitability, capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available”basis in this document, and Nokia Solutions and Networks reserves the right to change any such information andstatements without notice. Nokia Solutions and Networks has made all reasonable efforts to ensure that the content ofthis document is adequate and free of material errors and omissions, and Nokia Solutions and Networks will correcterrors that You identify in this document. But, Nokia Solutions and Networks' total liability for any errors in thedocument is strictly limited to the correction of such error(s). Nokia Solutions and Networks does not warrant that theuse 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, MERCHANTABILITYOR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT.IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ANY DAMAGES, INCLUDING BUTNOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS

BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY ORDATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THECASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

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

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may betrademarks of their respective owners, and they are mentioned for identification purposes only.

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



LTE_LNF5.0_0.1 – Impact Document - Page 1/4 © Nokia Solutions and Networks 2014Version 1.0Confidential

Impact Document

Id: LTE_LNF5.0_0.1Product Family: Base Stations Product: Flexi Zone BTS Release: LNF5.0 0.1Release Delivery: RL50FZ 0.1


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.





Table of Contents1. PURPOSE ................................................................................................................................... 3

2. SW UPDATE DELIVERY EFFECT.............................................................................................. 3

3.

EFFECTS ON END-USER .......................................................................................................... 3

4. EFFECTS ON OPERATOR ......................................................................................................... 3

5. OTHER EFFECTS....................................................................................................................... 3

6.

NEW / CHANGED FUNCTIONALITY .......................................................................................... 3

7. APPENDICES / REFERENCES.................................................................................................. 3

Contact:Contact your local Nokia Solutions and Networks support

Summary of changes:





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 it maynot be used except for the purposes defined in the agreement between You and Nokia Solutions andNetworks (“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 ofNokia Solutions and Networks. If you have not entered into an Agreement applicable to the Product, or ifthat Agreement has expired or has been terminated, You may not use this document in any manner andYou are obliged to return it to Nokia 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 full responsibility when using it. Nokia Solutions and Networks welcome Your comments as part ofthe 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 solely onan “as is” and “as available” basis in this document, and Nokia Solutions and Networks reserves the rightto change any such information and statements without notice. Nokia Solutions and Networks has made allreasonable efforts to ensure that the content of this document is adequate and free of material errors andomissions, and Nokia Solutions 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 correctionof such error(s). Nokia Solutions and Networks does not warrant that the use of the software in the Productwill be uninterrupted or error-free.

NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO

ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THECONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BELIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, 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 OFERRORS IN OR OMISSIONS FROM THIS 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 andNetworks.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document

may be trademarks of their respective owners, and they are mentioned for identification purposes only.




LTE_LNF5.0_0.1 – Change Note Forms - Page 1/14 © Nokia Solutions and Networks 2014Version 1.0Confidential

Change Note Forms




Draft version: 30-Sept-2014

Summary of changes:







CN-id: LNF50_001

Title:RL50: SW upgrade from one load to the same should not be processed

Version of the SW-build:

LNF5.0_ENB_1304_168_00

Valid for Product(s):

FlexiZone Micro

References:See special conditions in Installation Instructions document, section 5 and 6.2.

Reason fo r the Change Note:

Summary of the original problem:In RL50 FZM BTS SM upgrades to the same release are allowed. Because of this,commissioning data gets lost after the upgrade completes and a manual recommission andan additional reboot is required.

How end user/operator could detect the problem:If the operator mistakenly attempts to upgrade to a release that is already running, the

problem outlined in the "Summary" section above will occur.

Description of the fault:See "Summary" section above.

Workaround:The best workaround is to avoid upgrading to the same release that is currently running onthe FZM.

Description of the correction (incl. risk analysis):Medium high risk. Approximately 20 lines of code modified. Correction provides a fix thatdoesn't allow the same release to be installed.

Effects on operator:Biggest impact to operator is manual recommissioning from the BTS SM.

Effects on end-user:Biggest impact to end-user is an additional reboot of the FZM after manual recommissioningstep by operator. The reboot triggers a short break of server for the end-user.

System effects: After manual recommissioning and reboot, the FZM should stabilize and resume healthyoperation.

Faulty component and version:System Release 162_00 through 165_00 contains the defect.

Corrected Fault Reports :




118221ESPE04RL50: SW upgrade from one load to the same should not be processed

Modified components:

Component Version *Net element *SW-type *Unit

upgrade.- 1.0 - - -

Change effects:

Effects on end-userN/A

Effects on Operator

N/A

Other effectsN/A

New functionality

N/A

Customer ImpactStabilityObserved Problem: what is the symptom? In FZM releases 162_00 and beyond, upgrading tothe same release using BTS SM is allowed. In releases prior to 162_00 this was not allowed.Scope of Impact: what is affected and how? Because of this, commissioning data gets lostafter the upgrade goes through and a manual recommission and an additional reboot isrequired. There is an additional impact if a customer is running an RL70 release and invokesthe fallback feature. This feature allows an operator to fallback to the release on the standbypartition. When fallback is invoked an an RL50FZ release resides in the standby partition, thefallback will not occur.Known Triggers: what causes the problem? Allowing upgrade to same release in FZM 162_00and beyond.Frequency of Occurrence: how often is the problem seen? 100% on releases 1620_00 andbeyond. 100% if fallback is invoked and an RL50FZ release is installed in the standbypartition.Problem Signature: how can problem be identified? Site will lose commissioning after theupgrade. In the fallback case, fallback will not occur when requested.Workaround (if available): how can problem be avoided? For the lost commissioning case,avoid upgrading to the same release. NA for the fallback case.Recovery Procedure (if known): how can problem be neutralized? NASolution and Risk (if known): what needs to change and how might it affect load stability?medium high risk. There are a lot of test cases. 20 LOC.




Testing Instructions for the change

Pre-requirements:

This test is possible only when upgrading directly from Factory Load(LNF5.0_ENB_1304_131_80) to RL50FZ 0.1.Due to bug in RL50FZ P8/C5 SW, this test should not be attempted after upgrade fromRL50FZ P8/C5 to RL50FZ 0.1

Test execution:

Perform upgrade to the same release as currently running on the FZM.

Expected results:

Upgrade to the same release will not be performed.

Unexpected results:

Upgrade to the same release will be performed, and commissioning data will be lost.




CN-id: LNF50_002

Title:Cell doesn't get disabled when VSWR major alarm is raised


LNF5.0_ENB_1304_168_00


FlexiZone Micro

References:


Summary of the original problem:Cell doesn't get disabled when VSWR major alarm is raised

How end user/operator could detect the problem:cell is not disabled even if VSWR major alarm is raised

Description of the fault:

Bug in source code: If cellId was equal 0 or if cellId was greater than 1 (in RL50 case) methodFR_DisableCellRecovery::isCellReportHwStateRequired was returning 'false' incorrectly. Alarm was raised but cell doesn't get disabled because of dependency of this method (for celldown method should return 'true').

Related feature / functionality:LTE899 Antenna line supervision

Workaround:Manually block the cell when Major VSWR alarm appears

Description of the correction (incl. risk analysis):Bug in source code (unnecessary if statement): If cellId was equal 0 or if cellId was greater

than 1 (in RL50 case) method FR_DisableCellRecovery::isCellReportHwStateRequired wasreturning 'false' incorrectly. Alarm was raised but cell doesn't get disabled because ofdependency of this method (for cell down method should return 'true').There was a solution for 'cellId equals 0 or cellId greater than 1' issue already implemented sothis if statement was unnecessary and it was removed.

Effects on end-user:Degraded quality.

Effects on operator: Additional tasks need to be performed

Faulty component and version:BTSOM




Corrected Fault Reports :85615ESPE03Cell doesn't get disabled when VSWR major alarm is raised



BTSOM.- 3897 - - -

Change effects:

Effects on end-user

N/A

Effects on Operator

N/A

Other effects

N/A

New functionality

N/A

Customer Impact

Operation & MaintenanceIn case antenna is faulty, cell will remain on-air which may result in degraded performance.


Pre-requirements:

(Local) cell ID equals 1; FZM is on-air

Test execution:

Detach TX/RX antennas from FZM so that VSWR raises

Expected results:VSWR major alarm is raised and cell is blocked automatically

Unexpected results:

VSWR major alarm is raised but cell stays on-air




CN-id: LNF50_003

Title:RL50 Flexi Zone: VSWR alarm active for some sites- the sites are not on-air


LNF5.0_ENB_1304_168_00


FlexiZone Micro

References:


Summary of the original problem:BTSOM sets the default value for the vswrMajorAlarm if no value was set by the end-user inBTSSM. Therefore RFSW will not replace it with the correct default value of 5.8.

How end user/operator could detect the problem:If the operator doesn't specify any value for vswrMajorAlarm in BTSSM, he will detect thisproblem (this will trigger VSWR Alarm and the corresponding Cell will be “Blocked”)

Description of the fault:BTSOM sets the default value, but RFSW software should do that instead.

Workaround:The operator should set vswrMajorAlarm value for the ANTL to 3.5.

Description of the correction (incl. risk analysis):We removed the setting of the default value in the BTSOM software.

Effects on operator:Operator will not see any more issues or alarms in regards to vswr if the operator doesn’t set itin BTSSM.

Faulty component and version: All versions of BTSOM software on RL50 branch. This is aLEGACY issue.

Corrected Fault Reports :NA05685936RL50 Flexi Zone: VSWR alarm active for some sites- the sites are not on-air



BTSOM.- LNF5.0_ENB_1304_167 _00

- - -




Change effects:

Effects on end-user

N/A

Effects on Operator

N/A

Other effects

N/A

New functionality

N/A

Customer Impact

Operation & MaintenanceUnnecessary and unwanted major alarms may appear resulting in unnecessary workload foroperator maintenance teams.


Pre-requirements:

FZM on-air

Test execution:

Cause the VSWR level to raise above level of 3.0 but below 5.8 (by slightly unscrewing TX/RXmain or diversity antenna or attaching attenuator and setting attenuation to some level).VSWR level can be read by executing command “power tx @RFSWexe” at Aashell; Aashellcan be accessed from command line using command “telnet localhost 15007”. After 5 minutesraise VSWR level above 5.8 and wait a few minutes.

Expected results:

VSWR major alarm is not triggered when VSWR level is below 5.8 and is triggered whenVSWR is above 5.8 level.

Unexpected results:VSWR major alarm is triggered when VSWR is below 5.8 level




CN-id: LNF50_004

Title: Auto Config / Auto Connection fails to properly commission TRS.


LNF5.0_ENB_1304_168_00

Valid for Product(s):FlexiZone Micro

References:


Summary of the original problem:1) AutoConfig / AutoConnect not working properly, leaving the TRS in 'not Commissioned'state2) Template re-commissioning does not work for BTSID in TRS config.

How end user/operator could detect the problem:

After somewhat lengthy plannning and setup, the actual execution of this would fail as thedownloaded commissioning information does not get populated on the site properly. Thereforethe site does not come into service.

Also template re-commissioning does not work when attempting to change BTSID in TRSconfig.

Description of the fault:When modify state request is sent before sending a modify state response, TRS will generatea backup file though not used for any purpose. This file generation takes long time sometimesand a reboot will be triggered before modify state response is sent, hence the config file willnot be marked for activation.

Related feature / functionality:SON - Plug and Play

Description of the correction (incl. risk analysis):The unnecessary backup file generation before sending the modify state response isremoved.

Effects on operator:Feature (SON - Plug and Play) does not work.

System effects:FZM not OnAir




Corrected Fault Reports :146040ESPE02 Auto Config / Auto Connection fails to properly commission TRS.

NA05704730NPI:RL50FZ -Problem it is not possible to recommissioning BTS_ID



scrumc_asg_conf ig_activation_fix.-

FTM_FZM50 _302.00

- - -

Change effects:

Effects on end-user

Effects on Operator

Other effects

New functionality

Customer Impact

Operation & Maintenance


Pre-requirements:Target build that contains this correction must be installed on NetAct (if a SW upgrade isplanned as part of the Auto connect / Auto config process) or the site must be manuallyupgraded to this target build prior to the Auto Connect / Auto Configuration execution. All the preconditions listed in SON.2004 have to be fulfilled – i.e. SON.2001, SON.2002 and

SON.2003

Test execution:

Perform the Auto Connect / Auto Configuration process normally as described in SON.2004 ATMN

Expected results:

Site will complete all planned actions as part of the Auto Connect / Auto Configuration processand come on Air.

Unexpected results:

The Auto Connect / Auto configuration process completes, however the site will not comeonAir due to key configuration items missing from the TRS provisioning




CN-id: LNF50_005

Title:Paging messages cannot be sent sometimes to UE in a weak/strong electric field.


LNF5.0_ENB_1304_168_00


FlexiZone Micro

References:


Summary of the original problem:In some sites involved in ETWS (Earthquake and Tsunami Warning System) testing it wasobserved that occasionally (3/11) ETWS broadcast failed due to missing paging (not visibleover the air).The problem was reproduced in the field, it was observed that the occurrence depends on RFconditions (problem more frequent in poor radio conditions)

How end user/operator could detect the problem:• ETWS testing while parameter changes ongoing (unlikely)• Frequent ETWS broadcast i.e. field testing (most probably)

Description of the fault:ETWS broadcast problem was caused by MAC layer SW defect. Once problem was triggered:• wrong message array allocation limits overall paging capacity for both types of paging (Pcch/ Bcch) leading to occasional paging scheduling failures.• depending on the amount of paging procedure: it is still possible to handle some pagingoperation successfully as long as “incoming rate of paging related requested towards MACdoesn’t exceed ~1/20ms” if it does – operation will fail due to lack of message arrayresources.

In poor RF conditions, more re-tries triggered by MME are expected if normal paging doesn’tgo through which implies higher message array utilization – increased probability of ETWSfailure.

Related feature / functionality:ETWS

Workaround:Cell resource re-initialization (SM restart or cell lock / unlock operation)

Description of the correction (incl. risk analysis):Updating the buffer status variable after receiving ETWS Bcch paging during waiting for thestarting time of previous paging to expire.

Corrected Fault Reports :




NA05681287Paging messages cannot be sent sometimes to UE in a weak/strong electric field.



fb13_04.- 315595 - - -

Change effects:

Effects on end-user

Effects on Operator

Other effects

New functionality

Customer ImpactUser Plane QualityReliabilty of ETWS BCCH paging in high load paging scenario and high interferenceenvironment.


Pre-requirements:Site involved in ETWS testing

Test execution:

Frequent S1AP (Write Replace Warning Request) are necessary to trigger the problem.

The first BcchMod (A) with a valid Activation Time is received by MACBefore the ActivationTime of (A) is reached an ETWS is simulated

This means that in a short time interval (less than 10 TTI) MAC will receive two new BcchModmessages:- the first one without Activation Time (B) (which shall be sent ASAP) (B)- the second BcchMod with Activation Time (C)Before start to send (C) a new ETWS procedure is started.The cycle 3-4 is repeated

Expected results:

The syslog should not have below prints:

025202 03.07 16:52:12.664 [192.168.255.129] 11 FSP-1231 <03.07 15:52:16.895953> 21ERR/LTEMAC/DLMAC/012/FFFFFFFF:FFFFFFFF/CMacPcchDataSendReqMsgArray::AddMessage:

Message array fully occupied! (msgArraySize=34)




025203 03.07 16:52:12.664 [192.168.255.129] 12 FSP-1231 <03.07 15:52:16.895957> 21ERR/LTEMAC/DLMAC/012/FFFFFFFF:FFFFFFFF/CDlSupportPcchSend::handleMAC_BcchModIndReq: Modding of paging element failed!

Unexpected results:

The syslog has below prints:

025202 03.07 16:52:12.664 [192.168.255.129] 11 FSP-1231 <03.07 15:52:16.895953> 21ERR/LTEMAC/DLMAC/012/FFFFFFFF:FFFFFFFF/CMacPcchDataSendReqMsgArray::AddMessage:Message array fully occupied! (msgArraySize=34)

025203 03.07 16:52:12.664 [192.168.255.129] 12 FSP-1231 <03.07 15:52:16.895957> 21ERR/LTEMAC/DLMAC/012/FFFFFFFF:FFFFFFFF/CDlSupportPcchSend::handleMAC_BcchModIndReq: Modding of paging element failed!




Disclaimer














LTE_LNF5.0_0.1 - Installation Instructions - Page 1/6 © Nokia Solutions and Networks 2014Version 1.0Confidential

Installation Instructions










Table of Contents1.OVERVIEW ...................................................................................................................................... 3

1.1 OTHER RELEVANT INSTALLATION INSTRUCTIONS......................................................... 3

2.PREPARATIONS ............................................................................................................................. 3

3.SW UPDATE DOWNLOADING INSTRUCTIONS ............................................................................ 3

4.SPECIAL CONDITIONS ................................................................................................................... 4

4.1

FLEXI ZONE MICRO BTS LTE ............................................................................................. 4

4.2 LTE IOMS.............................................................................................................................. 4

5.OPERATIONAL HINTS AND RECOMMENDATIONS ...................................................................... 4

6.SW UPDATE INSTALLATION .......................................................................................................... 4

6.1

FIRST INSTALLATION AND COMMISSIONING ................................................................... 4

6.2

PROJECT UPDATE .............................................................................................................. 5

7.FALLBACK ....................................................................................................................................... 5

8.APPENDICES / REFERENCES ....................................................................................................... 5

Contact:

Contact your local Nokia Solutions and Networks support

Summary of changes:





PurposeThe purpose of this document is to describe the actions needed for installing this SW updateDelivery SW into the customer’s network.

1. OVERVIEW

This document covers Installation Instruction Flexi Zone BTS. Standard installation instructionsare available in the Customer Documentation library accessible through NOLS [1] atProduct Information Center [4].It is required to carefully study content of the library and follow on detailed proceduresdescribed in the documents. All exceptions from base procedure will be listed in thisdocument.

1.1 OTHER RELEVANT INSTALLATION INSTRUCTIONS

All LTE Customer Documentation, including standard installation procedures, is accessiblethrough NOLS [1] in the section “Product Information Center” [4]

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

2. PREPARATIONS

Hardware used for the installation should be integrated according to the hardware installationguide and all necessary cabling should be already done. Necessary documents can be foundin the section “Install and commission” in the Customer Documentation library

3. SW UPDATE DOWNLOADING INSTRUCTIONS

The software for the released products is available in NOLS.

The newly released software can be downloaded from the direct links:

• Flexi Zone BTS:


Software Item Software File Name SHA1 check sum

BTS Site ManagerBTSSiteManager_LNF5.0_BTSSM1309_35_00.zip

1470af b60673dd01528d0acf 1416

b8f 795758271

Golden SCFFZM_Golden_Comissioning_File_ENB_1304_125_00_onwards.zip

a9a021ed20a50724f 2d1b0daf b71

8271b71b00d3

eNBLNF5.0_ENB_1304_168_00_release_BTSSM_downloadable.zip

10c40d11a7d0f 0c715d0bf 1719c1

b8b7760ab567

Flexi Zone Authentication toolsEXT_FZAUTHREL_FZAUTHREL _LNF5.0_V1.1_20140731_2.zip

a2a06553b63a6f 50937a0f 7c6c4a

ab993e79632f

After downloading the software it is important to generate SH1 checksum for files andcompare it with the one provided in the Summary of Corrections and Enhancements

document, this will ensure that the files were not corrupted during downloading.











4. SPECIAL CONDITIONS

4.1 Flexi Zone Micro BTS LTE

During commissioning of FZMs in a daisy chain configuration the following steps need to beperformed to set static routes during commissioning:

During commissioning of the chained enodeB on the Routing Page, a static route needs to beconfigured with the destination IP as Chained eNodeB IP, corresponding netmask and defaultgateway.Similarly on the routing page during commissioning of the chaining eNodeB, a static routeneeds to be configured with the destination IP as chaining eNode B IP, corresponding netmaskand default gateway.

For example:1. Chaining FzM (10.52.182.142) - set static route:

• Destination: 10.52.182.141

• Netmask: 255.255.255.255

• Gateway: 10.52.182.1292. Chained FzM2 (10.52.182.141) - set static route:

• Destination: 10.52.182.142

• Netmask: 255.255.255.255

• Gateway: 10.52.182.129

4.2 LTE iOMS

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

5. OPERATIONAL HINTS AND RECOMMENDATIONS

Support for IPSec in RL50FZ for Bearer, Control and Management Traffic only with limitedcapacity.

FZM will use a hard coded VSWR detection value and ignore any operator configured values. Any VSWR operator configuration changes will be overwritten by the hardcoded value at theFZM which will eliminate false VSWR detection alarms.

SW upgrade to the same SW version is not supported.

SW upgrade to the same SW version as currently active, results in loss of BTS commissioning. As recover action operator needs to re-commission BTS from the BTS Site Manager by usingManual/ Template/Planned commissioning type.

6. SW UPDATE INSTALLATION

6.1 FIRST INSTALLATION AND COMMISSIONING

The commissioning procedure of the Flexi Zone BTS is described in the document

“Commissioning Flexi Zone Micro BTS LTE” [2].Please be aware that BTS Site Manager shall be updated before the BTS SW.




Disclaimer














LTE_LNF5.0_0.1 – SW Update Verification Report - Page 1/4 © Nokia Solutions and Networks 2014Version 1.0Confidential

SW Update Verification Report


Product: FlexiZone BTS








Table of Contents1. INTRODUCTION......................................................................................................................... 3

2. TEST ENVIRONMENT ................................................................................................................ 3

3.

DESCRIPTION OF TEST PHASE ENTITIES .............................................................................. 3

4. REMAINING OPEN FAULTS FOUND IN TESTING .................................................................... 3

5. APPENDICES / REFERENCES.................................................................................................. 3

Contact:Contact your local Nokia Solutions and Networks support

Summary of changes:





1. INTRODUCTION

This document presents the testing results for RL50FZ 0.1 including the findings made. Thetest environment is also presented in this document.The following table summarizes the amount of test cases.

Test Phase Total Passed Passed Rate

Correction testing 6 6 100%

Quick Tests 16 16 100%

Regression testing 146 146 100%

Total 168 168 100%

2. TEST ENVIRONMENT

Test environment is build according to chapter “System Descriptions” [1] in CustomerDocumentation library.

3. DESCRIPTION OF TEST PHASE ENTITIES

Correction Testing

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

Quick Tests

Quick Test (QT) integrates the software build and verifies basic FZM functionality like SWDownload, commissioning, FTP/UDP Downloads and Uploads and Ping.

Regression Testing

Regression test verifies the unchanged parts of a product after parts of the product have beenchanged. It is a way to ensure that the change did not affect anything else and that there areno unexpected side effects.

4. REMAINING OPEN FAULTS FOUND IN TESTING

Remaining open faults are listed in document “LGF-LTE-RL50FZ-2014-w38 ”.

5. APPENDICES / REFERENCES

[1] “LTE RAN and EPC System Description”, DN09158585



Disclaimer












lte rl50fz 0.1 release documentation

Documents