lte_rl50 0.2.3 release documentation

8/10/2019 LTE_RL50 0.2.3 Release Documentation

http://slidepdf.com/reader/full/lterl50-023-release-documentation 1/53

LTE_RL50_0.2.3 Startpage

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

CONFIDENTIAL

APPROVED 1.0 1 (1)

Contact Contact your local Nokia Solutions and Networks support

Summary of changes:

2014-07-16 V 1.0 Approved version

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.

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.

LN5.0 0.2.3 Priori ty Release

Id: LTE_RL50_0.2.3Product Family: Base Stations,Product : Flexi Multiradio BTS LTERelease: LN5.0 0.2.3

Approved version: 16-07-2014

Document name:

LTE_RL50 0.2.3 Summary of Corrections and Enhancements

LTE_RL50 0.2.3 Change Note Forms

LTE_RL50 0.2.3 Impact document

LTE_RL50 0.2.3 Installation Instructions



LTE_RL50_0.2.3 Summary of Corrections and Enhancements

Nokia Solutions and Networks ©

CONFIDENTIAL

APPROVED 1.0 2 (21)

Table of Contents1. Purpose ......................................................................................................................................................... 3

2.

New Corrections documented in Change Notes ........................................................................................... 3

3. New Corrections NOT documented in Change Notes .................................................................................. 3

4. New / Changed functionality ......................................................................................................................... 3

4.1 Released Features ............................................................ ..................................................................... .................. 3

4.2 Restricted Released Features .................................................................. ................................................................ 3

4.3 Not Released Features ................................................................................................... ......................................... 3

5. Status Legacy Features ................................................................................................................................ 3

5.1 Released Legacy Features ................................................................................. ..................................................... 3

5.2 Restricted Released Legacy Features ....................................................................................... ............................ 17

5.3 Not Released Legacy Features ................................................................ .............................................................. 20

6. 3rd party corrections ................................................................................................................................... 20

7. Previous deliveries for the release .............................................................................................................. 20

8. Appendices / References ............................................................................................................................ 20

ContactContact your local Nokia Solutions and Networks support

Summary of changes






CONFIDENTIAL

APPROVED 1.0 3 (21)

1. PURPOSE

The purpose of this document is to give a brief summary on the RL50 0.2.3 SW Delivery correctionscontent.

2. NEW CORRECTIONS DOCUMENTED IN CHANGE NOTES

Pronto ID Title

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

SBM RL50 live ETWS feature.

3. NEW CORRECTIONS NOT DOCUMENTED IN CHANGE NOTES

Pronto ID Title

4. NEW / CHANGED FUNCTIONALITY

4.1 Released Features

N/A

4.2 Restricted Released Features

N/A

4.3 Not Released Features

N/A

5. STATUS LEGACY FEATURES

5.1 Released Legacy Features

ID Feature Name Solution Area Operator Hint

1 S1/X2 data path management Radio ResourceManagement / Telecom

2 S1 Flex Radio ResourceManagement / Telecom

3 S1, X2 and RRC common signaling Radio ResourceManagement / Telecom

4 Multi-Operator Core Network Radio ResourceManagement / Telecom

5 Radio bearer and S1 bearerestablishment and release

Radio ResourceManagement / Telecom

7 Support of multiple EPS bearer Radio ResourceManagement / Telecom





CONFIDENTIAL

APPROVED 1.0 4 (21)


9 Service differentiation Radio ResourceManagement / Telecom

10 EPS bearers for conversational voice Radio ResourceManagement / Telecom

11 Robust header compression Radio ResourceManagement / Telecom

13 Rate capping Radio ResourceManagement / Telecom

20 Admission control Radio ResourceManagement / Telecom

22 Emergency call handling Radio ResourceManagement / Telecom

27 Open loop UL power control and DLpower setting


28 Closed loop UL power control Radio ResourceManagement / Telecom

30 CQI adaption (DL) Radio ResourceManagement / Telecom

31 Link adaptation by AMC (UL/DL) Radio ResourceManagement / Telecom

37 Ciphering Radio ResourceManagement / Telecom

38 Integrity protection Radio ResourceManagement / Telecom

39 System information broadcast Radio ResourceManagement / Telecom

40 Physical & transport channels Radio ResourceManagement / Telecom

41 PDCP, RLC & MAC support Radio ResourceManagement / Telecom

42 DRX in RRC connected mode Radio ResourceManagement and Telecom

Operator Hint: By default drxProfile2 is used for all GBR related QCIs(QCI1-4). For all non-GBR related QCIs (QCI5-9) bydefault drxProfile3 is used.Customer is free to change settings (in a specific range)for the relevant drxProfiles (also Extended DRX settingsfor the non-GBR QCIs). But therefore he has to keep inmind which services should be used with a special QCIand set the timers for the relevant drxProfiles accordingto the t iming requirements these services had to fulfill.

43 Support of 64 QAM in DL Radio ResourceManagement / Telecom

45 Fair scheduler (UL/DL) Radio ResourceManagement / Telecom

46 Channel-aware Scheduler (UL) Coverage, capacity andpeak rates

48 Support of High Speed Users Basic LTE call handling andinterworking

49 Paging Radio ResourceManagement / Telecom

50 UE state management Radio ResourceManagement / Telecom

51 Cell selection and re-selection Radio ResourceManagement / Telecom

53 Intra and inter eNB handover with X2 Radio Resource

Management / Telecom





CONFIDENTIAL

APPROVED 1.0 5 (21)


54 Intra-LTE handover via S1 Radio ResourceManagement / Telecom

55 Inter-frequency handover Radio ResourceManagement / Telecom

Operator Hint for creation of the “Blacklisted cell forintra and inter freq HO" list:The elements of this list, consisting of start PCI and PCIrange, must be designed in a way, that the maximumPCI value 503 is not exceeded.Otherwise UEs with most common chipset are not ableto setup a connection.

56 Inter RAT handover to WCDMA Radio ResourceManagement and Telecom

68 Support of cell based location service Radio ResourceManagement and Telecom

Released as radio-only feature.

69 Transmit diversity for two antennas Radio ResourceManagement / Telecom

70 Downlink adaptive open loop MIMO fortwo antennas


71 2-way RX diversity (MRC) BTS Site Solution

72 4-way RX diversity BTS Site Solution

75 Up to 3 cells per Flexi LTE BTS BTS Site Solution

76 Flexi BTS legacy MHA Support BTS Site Solution

78 Flexi AC/DC with Battery PowerModule

BTS Site Solution

79 Flexi Indoor and Outdoor cabinets BTS Site Solution

80 GPS synchronisation BTS Site Solution Operator Hint: GPS cable length can be maximum 100m.

81 Cell range up to 13 km BTS Site Solution

82 High Capacity Flexi System ModuleFSME

BTS Site Solution

85 Flexi 3-sector RF Module 2600 BTS Site Solution



88 FXDA Flexi RF Module 3TX 900 BTS Site Solution

89 Flexi RRH 2TX 2600 BTS Site Solution

91 Flexi RRH 2TX 850 BTS Site Solution Operator Hints: 1. FHCA not supported for RET/MHA.2. FHCA 472169A.103 product (FPGA) should be usedin max. 2*20W DL power. This firmware must only beused under the following conditions: 20W mode -40 to+50 degrees.

94 Feederless Site BTS Site Solution

96 MIMO 2TX configuration with 3-sectorRF Module

BTS Site Solution

97 Cell radius max 77 km BTS Site Solution





CONFIDENTIAL

APPROVED 1.0 6 (21)


99 Flexi 3-sector RF Module 1.7/2.1 BTS Site Solution


103 FRLB Flexi RRH 2TX 730 (commercialversion)

BTS Site Solution


106 6 cell support with one System Module BTS Site Solution

112 Cell Bandwidth - 20 MHz BTS Site Solution





117 Cell Bandwidth - 1.4 MHz BTS Site Solution

118 Fast Ethernet (FE) / Gigabit Ethernet(GE) electrical interface

Transmission

119 Gigabit Ethernet (GE) optical interface Transmission

129 Traffic prioritization on Ethernet layer Transmission

131 Traffic prioritization on IP layer(Diffserv)

Transmission

132 VLAN based traffic differentiation Transmission

134 Timing over Packet Transmission

138 Traffic shaping (UL) Transmission

140 Ethernet OAM Transmission Operator Hint: The format of the maintenance domain name used inService OAM continuity check messages has changedwith RL50. Therefore for this functionality RL50 is notcompatible to former LTE releases.

144 Transport admission control Transmission

147 LTE Hardware Management Configuration Management

153 LTE BTS Site Manager Network Administration

154 SON LTE BTS Auto Connectivity Configuration Management

155 Flexi BTS 3rd party MHA Support BTS Site Solution

158 NTP clock time synchronization Supplementary O&Mfeatures

160 Flexi BTS 3GPP Antenna Tilt Support BTS Site Solution





CONFIDENTIAL

APPROVED 1.0 7 (21)


162 Cell trace with IMSI Network Monitoring andMaintenance

Released as radio-only feature.

Operator Hint: Feature "Cell Trace with IMSI" can be used in anenvironment with supporting 3rd party trace tool andMME. Trace Viewer itself will not support LTE162 CellTrace with IMSI in RL50.If MTRACE is configured (possible via TraceViewer)than eNB will always send the Cell Traffic Tracemessage to MME and provide respective results in eNBtrace file.The feature can only be used for testing purposes andcan activated by R&D flag in swconfig file.

163 Subscriber and Equipment Trace O&M Operator Hint: If NSN MME is used then messages are not tracedduring handover. Improvement expected in NS4.0.

179 Dual Band with One System Module BTS Site Solution

187 Single TX path mode Radio ResourceManagement / Telecom

423 RRC connection release with redirect Radio ResourceManagement / Telecom

426 System time broadcast for SIB8 Radio ResourceManagement and Telecom

Operator Hints: 1. Maximum holdover time was decreased to 6 hours2. GPS cable length can be maximum 100m.

430 DL power boosting for controlchannels

Radio ResourceManagement and Telecom

432 Cell Outage Detection Network Monitoring andMaintenance

433 Cell Trace O&M Feature replaced by LTE644 Configurable cell trace

content. Status see there.

435 RF sharing WCDMA-LTE BTS Site Solution For supported RF Sharing configurations please see"Flexi Multiradio BTS RF Sharing ReleasedConfigurations", DN09123381, latest issue in NOLS.

Operator Hints: 1. Special IP addresses shall be used for BTS SiteManager connection. See “Installation Instructions",

chapter 8 (Operational hints andrecommendations).2. Operator hint "New additional information in alarms ",please ee “Installation Instructions", chapter 8

(Operational hints and recommendations).

437 Flexi 3-sector RF Module 800EU BTS Site Solution

440 S1 Overload Handling Basic LTE call handling andinterworking

442 Network Assisted Cell Change to GSM Radio ResourceManagement and Telecom

447 SW support for RF sharing GSM-LTE BTS Site Solution For supported RF Sharing configurations please see"Flexi Multiradio BTS RF Sharing ReleasedConfigurations", DN09123381, latest issue in NOLS.

450 MME capacity value change Radio ResourceManagement and Telecom


459 LTE Timing Advance Evaluation Network Monitoring andMaintenance

468 PCI management Configuration Management





CONFIDENTIAL

APPROVED 1.0 8 (21)


471 LTE Dual carrier operation within oneRF band

BTS Site Solution

473 Extended DRX settings Radio ResourceManagement and Telecom

Operator Hint: By default drxProfile2 is used for all GBR related QCIs(QCI1-4). For all non-GBR related QCIs (QCI5-9) bydefault drxProfile3 is used.Customer is free to change settings (in a specific range)for the relevant drxProfiles (also Extended DRX settingsfor the non-GBR QCIs). But therefore he has to keep inmind which services should be used with a special QCIand set the timers for the relevant drxProfiles accordingto the t iming requirements these services had to fulfill.

475 Automatic iOMS resiliency O&M

482 DNS support for certificate

examination

Supplementary O&M

features487 Idle mode mobility load balancing Radio Resource


490 Subscriber profile based mobility Radio ResourceManagement and Telecom

491 FlexiPacket Radio Connectivity Transmission

492 ANR O&M

494 Commercial Mobile Alert System QoS, services and end userexperience

495 OTDOA QoS, services and end userexperience

496 Support of QCI 2, 3 and 4 QoS, services and end userexperience

497 Smart Admission Control QoS, services and end userexperience

502 Cell Outage triggered reset O&M

505 Transport Separation for RAN Sharing Transmission

507 InterRAT neighbor relationOptimization (LTE, UTRAN, GERAN)

Configuration Management

510 Synchronization of InterRAT neighbors Configuration Management

511 Intra cell handover Mobility

518 Operator specific QCI Radio ResourceManagement and Telecom

519 eRAB Modification QoS, services and end userexperience

521 Security for Ethernet ports onFCM/FSM2

O&M Security

522 S1 partial reset Radio ResourceManagement and Telecom

523 Multi-layered Certificate Authorities O&M Security Operator Hints: 1. Command updateCRL from NetAct to multiple LNBTSdoes not provide correct command feedback.updateCRL is triggered on multiple LNBTS but thecommand feedback includes only one LNBTS.Please note that in case of CRL update failure, BTS

generates an alarm and operator is informed this way.2. IPSec not tested with MLCA support, because





CONFIDENTIAL

APPROVED 1.0 9 (21)


Juniper (Junos 11.4R6-S1) only accepts IPsecconnections, when eNB is signed by the same CA (couldbe a sub CA) as its own signing CA.3. RA support not tested, because missing functionalityfrom 3. party tool (INSTA5.2.3)4. Leaked Operator Trust Anchor Manual Update in LTEtested without SeGW, because of point 15. Please note that starting from RL50 the certificates(CA cert or Entity cert) without the Key Usage "digital-signature" and “key-enciphment" cannot be used anylonger.

524 Certificate Management for iOMS OMS specific features

533 Mobility Robustness Configuration Management

534 ARP-based Admission Control for E-RABs

QoS, services and end userexperience

539 Central ANR Configuration Management

547 Flexi RRH 2TX 800 EU BTS Site Solution

559 SW Monitoring Module for LTE O&M

562 CSFB to UTRAN or GSM via redirect Radio ResourceManagement / Telecom

564 IPSec on FTIB Transmission Operator Hints: 1. For FTIB and FTLB: During IKEv2 rekeying eNBdoesn't take new SPI values immediately into account,so SEC-GW might drop some few packets.

2. The eNB transport module doesn’t support thefragmentation and reassembly of IPSec encrypted IPpackets. Therefore a) the fragmentation of IPSecencrypted IP packets either needs to be avoided byusing smaller MTU sizes at the peer sides or b) theIPSec GW needs to do the fragmentation first and thenthe encryption. For b) this is usually only possible if theDF Bit (Don’t fragment) isn’t set by peer.This doesn’t not need to be considered only for the userplane (SAE-GW), but e.g. also for the M-plane (OMS,CA-Server, ..).

568 DL adaptive closed loop MIMO (4x2) Coverage, capacity andpeak rates

570 Periodic UE measurements Radio ResourceManagement and Telecom

571 Controlled uplink packet segmentation Radio ResourceManagement and Telecom

572 IMS emergency sessions Radio ResourceManagement and Telecom

Radio only feature. Not tested end-to-end.

574 IP Transport Network Measurement Transmission

581 PRACH management Configuration Management

585 Smart DRX QoS, services and end userexperience

587 Multiple GBR EPS Bearers per UE QoS, services and end userexperience

592 Link Supervision with BFD Transmission





CONFIDENTIAL

APPROVED 1.0 10 (21)


593 Security for Ethernet Ports O&M Security Operator Hint for FSMF: For enabling/disabling „Ethernet Port Security“ theconnection to the BTS Site Manager might getinterrupted.When using BTS Site Manager menu a warning aboutpossible connection loss shows up in a pop up window.When using reconfiguration, a hint about possibleconnection loss shows up in the bubble help whenhovering with the cursor over the parameter name“Ethernet Port Security”.

Given that the operator could have changed moreparameters than this one (“Ethernet Port Security”)within the reconfiguration, the error message is quiteconfusing.This issue occurs sporadically: 4 out of 10 test runs.

602 Performance Management Administration

Network Monitoring andMaintenance

See status of LTE657 LTE Performance Management.

612 Synchronization Hub Transmission

614 Distributed Site BTS Site Solution Operator Hint: The parallel fibers to radio module shall be in samecable. This ensures that both fibers are same length andthe system works. The system now allows max. 5 meterslength difference between main and secondary fibers.

616 Usage based PDCCH adaptation Radio ResourceManagement and Telecom

619 Interference aware UL scheduling Radio ResourceManagement and Telecom

621 Flexi 10BTS Basic Configurations BTS Site Solution

622 Local Link Layer Security O&M Security

623 Crypto Agent O&M Security

628 FTIF Transport PDH / Ethernet Transmission

630 Flexi Dual MHA 800 BTS Site Solution

644 Configurable cell trace content Network Monitoring andMaintenance

Operator Hint: Cell trace for iOMS change e.g. triggered by iOMSresiliency feature is not supported.Workaround: iOMS change needs eNB reset in case atrace was active before.

646 SW Monitoring Extension with PMCounters Configuration Management

649 QoS aware Ethernet switching Transmission Operator Hint:When enabling VLAN aware Ethernet switching on FTIB,the total number of different VLAN IDs configured in theVLAN ID Lists of the Ethernet interfaces must be limited(less than 100).

In RL20 and RL30, configuration of a VLAN-ID withvalue zero (0) was possible, violating IEEE standards. Incase an operator used this value in the transport networkdesigns, it is necessary to change this networkconfiguration to standard conform values (i.e., VLAN-ID1...4094) before migrating to LTE RL40 or to LTE RL50.

651 Performance Monitoring I Performance Monitoring See status of LTE657 LTE Performance Management.





CONFIDENTIAL



653 LTE Operability Architecture Network Administration

655 LTE Software Management Configuration Management

656 LTE Fault Management Network Monitoring andMaintenance

657 LTE Performance Management Network Monitoring andMaintenance

Operator hints valid for FSME: 1. In case NTP server fails and eNB is rebooted, butGPS receiver is available, no PM measurement data isproduced as FTM is reset to 1.1.2004 and not alignedwith FSM anymore which has still correct time and date.No alarm is generated, all timestamps for alarms andnotifications are done by FSM and are correct, thereforethe user cannot detect any problem.2. Furthermore it must be ensured that the NTP server

delivers the same time to FTM as the GPS receiver toFSM, so that both units really run with the same time.Otherwise performance measurements might bedisturbed as the start and end time of measurementintervals is different for BTS PM (FSM) and TRS PM(FTM). TRS PM measurement intervals are then shiftedso that they fit into the corresponding BTS PMmeasurement intervals. This effect cannot be detectedby the user.

663 GPS location and time retrieval Supplementary O&Mfeatures

664 LTE transport protocol stack Transmission

665 LTE Certificate Management O&M Security

666 LTE User Account Management O&M Security

667 LTE User Event Log Management O&M

679 LTE Local User Account Management O&M Security

681 Windows 7 Support for ElementManager Client Software

O&M

685 Infrastructures for Certification Authority (CA) and Registration Authority (RA)

O&M Security

689 LTE IPsec Support Transmission Operator Hints: 1. For FTIB and FTLB: During IKEv2 rekeying eNBdoesn't take new SPI values immediately into account,

so SEC-GW might drop some few packets.2. The eNB transport module doesn’t support thefragmentation and reassembly of IPSec encrypted IPpackets. Therefore a) the fragmentation of IPSecencrypted IP packets either needs to be avoided byusing smaller MTU sizes at the peer sides or b) theIPSec GW needs to do the fragmentation first and thenthe encryption. For b) this is usually only possible if theDF Bit (Don’t fragment) isn’t set by peer.This doesn’t not need to be considered only for the userplane (SAE-GW), but e.g. also for the M-plane (OMS,CA-Server, ..).

692 LTE Firewall Support O&M Security

703 DL adaptive closed loop MIMO for twoantennas






CONFIDENTIAL



707 Flexi Transport sub-module FTIB Transmission

710 Synchronization from PDH interface Transmission

711 Synchronization from 2.048MHz signal Transmission

713 Synchronous Ethernet Transmission

720 SON LTE BTS Auto Configuration Configuration Management

724 LTE Automatic Neighbor CellConfiguration


735 RRC Connection Re-establishment Radio ResourceManagement and Telecom

736 CS Fallback to UTRAN Mobility

746 IP based Filtering for BTS Site SupportEquipment

O&M Security

747 Support of UE radio capabilities Radio ResourceManagement / Telecom

748 FRHD Flexi RRH 4TX 2600 BTS Site Solution

749 Link adaptation for PDCCH Radio ResourceManagement / Telecom

761 Advanced target cell selection andhandover retry for intra frequencyhandover


762 Idle mode mobility from LTE toWCDMA, GSM or other LTE bands


763 FXFA Flexi 3-sector RF Module 1900 BTS Site Solution

767 Support of aperiodic CQI reports Radio ResourceManagement / Telecom

770 Basic Performance Counter CollectionII

Performance Monitoring See status of LTE657 LTE Performance Management.

771 Optimization of Intra-LTE neighborrelations


775 SCTP multi-homing (MME) Transmission Radio only feature. Not tested end-to-end.

782 ANR Fully UE based Configuration Management Operator hint related to UE based ANR feature: Fully UE based ANR is not working in case UE makesdata transfer (e.g. ping) and the proactive schedulingfeature (LTE815) is activated with the default periodicityof 1.5 s (cell parameter ilReactimerUl=1500 ms),because UE does not go in DRX Sleep mode andtherefore it is not able to decode the CGI of an unknownneighbor cell.

783 ANR InterRAT UTRAN Configuration Management

784 ANR InterRAT GERAN Configuration Management

786 Flexible UL Bandwidth Coverage, capacity andpeak rates

788 Support of 16 QAM (UL) Radio ResourceManagement / Telecom

793 Support of 16 QAM (DL) Radio ResourceManagement / Telecom





CONFIDENTIAL



797 PM Counter Handover I Performance Monitoring See status of LTE657 LTE Performance Management.

798 PM Counter Histograms I Performance Monitoring See status of LTE657 LTE Performance Management.

800 Flexi Transport sub-module FTLB Transmission

805 PM Counter Capacity I Performance Monitoring See status of LTE657 LTE Performance Management.

806 PM Counter Transport I Performance Monitoring See status of LTE657 LTE Performance Management.

807 Idle mode mobility LTE toCDMA/1xRTT

Radio ResourceManagement and Telecom

810 Flexi Dual MHA 2600 BTS Site Solution

819 DL inter-cell interference generation Radio ResourceManagement / Telecom

829 Increased uplink MCS range Radio ResourceManagement and Telecom

830 LTE Automatic Lock O&M

843 ETWS broadcast QoS, services and end userexperience

866 Fast IP Rerouting Transmission

870 Idle mode mobility from LTE toCDMA/eHRPD


872 SRVCC to WCDMA Mobility

873 SRVCC to GSM Mobility

875 Different IP addresses for U/C/M/S-plane

Transmission

877 Adjustable Performance Upload Performance Monitoring

899 Antenna Line Supervision BTS Site Solution

900 Flexi LTE BTS 40W Power Support BTS Site Solution


902 Flexi BTS AISG MHA Support BTS Site Solution


904 Flexi LTE BTS Branch Activation BTS Site Solution

905 Non GBR QCI 5, 6, 7, 8 and 9 Radio ResourceManagement / Telecom

907 TTI bundling Coverage, capacity andpeak rates

913 LTE NEBS Compliant OMS Supplementary O&Mfeatures

914 Graceful cell shut down Radio Resource


Operator Hint:

Graceful Cell Shut Down works only for UEs inConnected Mode. Reduction of transmission powersteps take place only in the given limits of dynamic





CONFIDENTIAL



range of attenuator in used RF unit.


931 Ethernet Jumbo Frames Transmission

940 SW Verification Agent O&M Security

947 FSMF Flexi Multiradio 10 SystemModule

BTS Site Solution

949 FPFD Flexi Power Distribution Sub-module

BTS Site Solution

950 FPFC Flexi Power Distribution Module BTS Site Solution

953 MDT (Minimization of Drive Test) Operability Operator hint: Trace recording session not closed after Intra-CellHandover, when cell tracing with 'Timing Advance' isenabled. The only way to close this Trace RecordingSession is to close the whole Cell Trace Session(remove MTRACE object from configuration or disableCell Trace feature which will close all Cell TraceSessions). To avoid this problem “Cell TA tracing”parameter needs to be set to “false” in scope of CellTrace Session.

962 RACH Optimization Configuration Management

971 Intra-LTE mobility offsets Radio ResourceManagement and Telecom

972 Flexi Baseband Module FBBA BTS Site Solution Operator Hint: SFP module from supplier Source Photonics ™ do notwork together with FBBA.

977 RF chaining BTS Site Solution

979 IRC for 2 RX Paths Coverage, capacity andpeak rates

980 IRC for 4 RX paths Coverage, capacity andpeak rates

984 GSM Redirect with System Information Mobility

985 FRGT Flexi 3-sector RF Module 2100 BTS Site Solution

1014 X2 eNB Configuration Update Basic LTE call handling and

interworking1019 SON Reports Configuration Management

1034 Extended Uplink Link Adaptation Radio ResourceManagement and Telecom

1035 Outer loop link adaptation for PDCCH Radio ResourceManagement and Telecom

1036 RSRQ based cell reselection Mobility

1040 FXEB Flexi 3-sector RF Module 1800 BTS Site Solution

1045 Full SON Support for Distributed Sites Configuration Management

1060 TDD - FDD handover Mobility





CONFIDENTIAL



1073 Measurement-based Redirect toUTRAN

Mobility

1089 Downlink carrier aggregation - 20 MHz Coverage, capacity andpeak rates

Operator Hint: 5&5 MHz BW not tested E2E due to UE un-availability.

1099 Event-triggered symptom datacollection and provisioning


Operator Hint: Feature "Event-triggered symptom data collection andprovisioning" should be used only for debuggingpurposes on selected eNBs not in a complete network.In current selection of trigger faults (special value) thereare many trigger conditions which can cause a highamount of data traffic on m-plane.

1106 Flexi low power RRH 850 2TX foroptical repeater interface

BTS Site Solution

1139 ZUC security algorithm Basic LTE call handling and

interworking

1148 FRIG Flexi RRH 4TX 1.7/2.1 BTS Site Solution

1170 Inter eNode B IF Load Balancing Mobility

1201 LTE iOMS HW, HP Blade Gen8 Supplementary O&Mfeatures

1222 SON Automation Modes Configuration Management

1247 Multiradio System Module extendedLTE configurations

BTS Site Solution

1260 iOMS Certificate update andrevocation support

OMS specific features Operator Hints:1. If CRL checking feature” is enabled in OMS, please

be aware that the downloaded CRL lists must be instatus “OK”.Otherwise the OMS may send a cert request and refusethe validation of the received certificates with an out-dated CRL list.Result is the rejection of a https connection.

2. Registration Authority (RA) support not tested,because missing functionality from 3. party tool(INSTA5.2.3)

3. Starting from RL50 the certificates (CA cert or Entitycert) without the Key Usage "digital-signature" and “key-enciphment" are not accepted by OMS.

1261 FHDB Flexi RRH 2TX 900 BTS Site Solution

1262 FHEB Flexi RRH 2TX 1800 BTS Site Solution

1306 FRMD Flexi 3-sector RF Module 800 BTS Site Solution

1337 FHEC Flexi RRH 2TX 1800 low power BTS Site Solution

1340 Trace-based Real Time Monitoring Performance Monitoring

1356 FXCC Flexi RF Module 2TX 850 BTS Site Solution

1367 Automatic cell combinationassignment for Carrier Aggregation


1368 System Upgrade with BackwardCompatibility

Configuration Management Operator Hint: RL40 2.1 Maintenance Package is precondition thatupgrade and fallback works.





CONFIDENTIAL



1383 Cell Specific neighbor relation / PCIhandling


1387 Intra-eNB Inter-frequency LoadBalancing

Coverage, capacity andpeak rates

1407 RSRQ based redirect Mobility

1422 FXDB Flexi RF Module 3TX 900 BTS Site Solution

1457 Cell Trace config via CM O&M

1513 Mixed system module configurationswith RF sharing WCDMA-LTE

BTS Site Solution For supported RF Sharing configurations please see"Flexi Multiradio BTS RF Sharing ReleasedConfigurations", DN09123381, latest issue in NOLS.

1514 Large LTE-GSM RF sharing

Configurations

BTS Site Solution For supported RF Sharing configurations please see

"Flexi Multiradio BTS RF Sharing ReleasedConfigurations", DN09123381, latest issue in NOLS.

1542 FDD Supercell Coverage, capacity andpeak rates

1680 Active Queue Management QoS, services and end userexperience

1687 Basic Layer3 Data Analyser (L3DA) forLTE


L0518 Keep cell in service in case of one TXpath failure


L0769 Change of 3GPP baseline to R106/2012


L0782 Remove of SRI operator cofigurableparameter


L0831 Increase the number of neighbor cellsof neighbor eNBs up to 24

Operability

L0836 1pps + Time of Day Sync Output forTMO US

Transmission

L0838 LTE1504 Checkpoint Appliance asSecurity Gateway

O&M Security Operator Hint for Checkpoint:

Operation mode : Round robin for Ethernet interface onCheckpoint should be avoided as packet loss isobserved with this setting in R&D Lab. Recommendedsetting for Ethernet interface operation modeconfiguration at Checkpoint to be set to LACP(802.3ad).

IKEv1:To work with IKEv1 one need to choose exclusively“IKEv1 only” mode in community level on CP.

IKEv1:Multi tunnel configuration: Not released(Restriction for multi tunnel configurations due to CPoffering of traffic selector of 0.0.0.0/0 0.0.0.0/0 (universaltunnel) and so no IPSec SA established.)

Multi Layer Certificates:Multi Layer Certificates operation with Checkpoint is notreleased by NSN Security organization.

L0863 Hide PUSCH hopping parameter Radio ResourceManagement / Telecom

L0906 Adding PM counters Performance Monitoring

L0926 enaDrxRepGra = False Radio Resource






CONFIDENTIAL



L0936 Alarm for lost Configuration ChangeNotification

Operability

L0944 Support for forcing OBSAI link speedsto 4x 8x modes

BTS Site Solution

L0946 Certificate subject and issuer nameformat

O&M Security

L0950 Upgrade of RL30EP2 (to RL50) Configuration Management

L0954 Improved and effort reduced S1/X2link status handling in eNb

Operability

L0962 PUCCH/PRACH resourceconfiguration and parameter relations.maxPucchResourceSize


L0966 Value change of the parameter

Tx2reloccomp

Operability

L0971 Remove erroneous implementation oftimer ”timSuppGtpuErrIndPreempt


L0995 Improving eNb delta plan activation inthe context of ANR


L1002 Adding Numerator/Denominator eNBload-counters


L1008 Blocking of 7th E-RAB setup Radio ResourceManagement / Telecom

L1016 LTE140 Ethernet OAM: SFSrequirement alignment toimplementation

Transmission

CRL1025

LTE-WCDMA RF sharing with 15Mhzbandwidth

BTS Site Solution

L1042 Max value for caMinDlAmbr from 10000 to 150 000 (parameter rangeextension)


L1044 Adding_U-plane_PM-counters_For_Througput_RSSI_SINR _UsedTTI_to_RL50_RL35

Performance Monitoring

L1168 Backward Compatibility of L1configuration (3GPP CR1294)


L1274 OMS Certificate Managementparameters

O&M Security

L1651 Special duplex gap on 1800 band Radio ResourceManagement / Telecom

Operator Hint: Implementation is done on base of the 1800MHz bandand not on the exact downlink frequency.

5.2 Restricted Released Legacy Features

ID Feature Name Solution Area

Restriction Pronto ID CorrectionPlan*

150 LTE OAM Transport LayerSecurity (TLS) Support

O&M Security Restriction: NetAct CS fail to set up secured filetransfer if SHA256 algorithm is used iniOMS certificate.NetAct can only support secured SWupload via mediator OMS with certificatesignature using SHA1 hash algorithms.

See NetActcorrection plan

550 Radio parameter onlinechangeable

O&M See status of LTE654 LTE ConfigurationManagement.

RL60

654 LTE ConfigurationManagement

ConfigurationManagement

Restriction: 1. In case a NetAct is connected it reports

wrong cell OST after eNB reboot incomparison to correct information shown

RL60





CONFIDENTIAL




on BTSSM. Plan file upload corrects themistake.

Operator hints: 2. OMS replies Download ftp error whiledownloading file in case DNS serverdoesn't answer within 3 seconds. This maylead to sporadically provisioning failures.3. In case of very large configurations(SCF file size bigger then 1MB) it might bepossible that BTSSM hangs duringrecommissioning. Workaround: CloseBTSSM and restart it again, then repeatrecommissioning action.

796 iOMS connectivity increase O&M Limitation on capacity: OMS is able to handle 14,000,000

counters per one interval (15 min.)e.g.2000eNB 6cells 7000 counters per eNB1000eNB 12cells 14000 counters per eNB

open

986 FRGS Flexi 3-sector RFModule 2100

BTS SiteSolution

No volume production.

1066 FRHC Flexi RF Module6TX 2600

BTS SiteSolution

Restrictions:1. VSWR alarm functionality does not workreliably in low traffic situation.

- VSWR alarm incorrect when no trafficin cell.

- VSWR Tuning Mode in BTSSM is notOK.

- VSWR values tuned by VSWR tunermight be inaccurate, which can lead tounexpected alarms (possible false alarms).

2. Configurations using of optical cableshave a low eNB startup success rate(98%). Workaround: Restart the eNB(locally or remotely).3. With fiber between SM and RF longerthan 15 km, UE attach to cellcommissioned to ANT1 and ANT2 will beunsuccessful.4. Hot insert of module or SFP module notsupported. Workaround: Restart the eNBafter installing the module or SFP (locallyor remotely).

1.48794ESPE052.80741ESPE033. 112782ESPE04

RL50 1.0

1067 FRMC Flexi RF Module6TX 800

BTS SiteSolution


- VSWR alarm incorrect when no traffic

in cell.- VSWR Tuning Mode in BTSSM is notOK.

- VSWR values tuned by VSWR tunermight be inaccurate, which can lead tounexpected alarms (possible false alarms).2. Configurations using of optical cableshave a low eNB startup success rate(98%). Workaround: Restart the eNB(locally or remotely).3. With fiber between SM and RF longerthan 15 km, UE attach to cellcommissioned to ANT1 and ANT2 will beunsuccessful.4. Hot insert of module or SFP module notsupported. Workaround: Restart the eNB

after installing the module or SFP (locallyor remotely).

1, 48794ESPE052.80741ESPE033. 112782ESPE04

RL50 1.0





CONFIDENTIAL




1195 FHCC Flexi 850 RepeaterInterface Unit (RIU)

BTS SiteSolution

Restriction: Restrict the usage of RIU delay setting to0…59us and keep care of specified fiberlength.

RL70

1329 FRPA Flexi RF Module6TX 700

BTS SiteSolution




- VSWR values tuned by VSWR tunermight be inaccurate, which can lead tounexpected alarms (possible false alarms).2. Configurations using of optical cableshave a low eNB startup success rate

(98%). Workaround: Restart the eNB(locally or remotely).3. With fiber between SM and RF longerthan 15 km, UE attach to cellcommissioned to ANT1 and ANT2 will beunsuccessful.4. Hot insert of module or SFP module notsupported. Workaround: Restart the eNBafter installing the module or SFP (locallyor remotely).

1.48794ESPE052.80741ESPE033. 112782ESPE04

RL50 1.0

1395 FRPB Flexi RF Module6TX 700

BTS SiteSolution



- VSWR Tuning Mode in BTSSM is not

OK.- VSWR values tuned by VSWR tuner

might be inaccurate, which can lead tounexpected alarms (possible false alarms).2. Configurations using of optical cableshave a low eNB startup success rate(98%). Workaround: Restart the eNB(locally or remotely).3. With fiber between SM and RF longerthan 15 km, UE attach to cellcommissioned to ANT1 and ANT2 will beunsuccessful.4. Hot insert of module or SFP module notsupported. Workaround: Restart the eNBafter installing the module or SFP (locallyor remotely).

1. 48794ESPE052.80741ESPE033. 112782ESPE04

RL50 1.0

1405 Remote SW-managementand data backup/restoresupport for iOMS

OMS specificfeatures Restriction: After Download-Activation of OMS SW viaSWM NetAct sporadically no upload istriggered. Operator must manuallysynchronize SW status of OMS via SWMupload after installation of OMScorrections.

1. 46263ESPE05 RL50 1.0

1563 FRHF Flexi RF Module6TX 2600

BTS SiteSolution




- VSWR values tuned by VSWR tunermight be inaccurate, which can lead to

unexpected alarms (possible false alarms).2. Configurations using of optical cableshave a low eNB startup success rate

1 48794ESPE052.80741ESPE033. 112782ESPE04

RL50 1.0





CONFIDENTIAL




(98%). Workaround: Restart the eNB(locally or remotely).3. With fiber between SM and RF longerthan 15 km, UE attach to cellcommissioned to ANT1 and ANT2 will beunsuccessful.4. Hot insert of module or SFP module notsupported. Workaround: Restart the eNBafter installing the module or SFP (locallyor remotely).

1662 FRHE Flexi RRH 4TX2600

BTS SiteSolution

No volume production. RL50 1.0

L0905 Inform reduced cell tracecapacity figures withNetAct TraceViewer

O&M Restriction: NetAct TraceViewer is not suitable tocollect Trace Data of high Traffic. For thispropose L3DC is recommended.

See NetActCorrectionPlan

Correction Plan*RL50 1.0 released on 30.04.2014RL60 released on 02.07.2014RL70 E12/2014

5.3 Not Released Legacy Features

ID Feature Name Solution Area Remark CorrectionPlan*

424 Automatic interface alarm correlation Network Monitoring andMaintenance

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

RL60

Correction Plan*

RL60 released on 02.07.2014

6. 3RD PARTY CORRECTIONS

N/A

7. PREVIOUS DELIVERIES FOR THE RELEASE

History information for the same release deliveries. In case of generic SW, this table does not includecustomer specific deliveries.

8. APPENDICES / REFERENCES

SW update delivery Delivery type Delivery date Note

LN5.0 Release 23.12.2013 C5

LN5.0 0.1 Priority Update 04.02.2014

LN5.0 0.2 Priority Update 25.02.2014





CONFIDENTIAL


Disclaimer

The information in this document is subject to change without notice and describesonly the product defined in the introduction of this documentation. This documentationis intended for the use of Nokia Solutions and Networks customers only for thepurposes of the agreement under which the document is submitted, and no part of itmay be used, reproduced, modified or transmitted in any form or means without theprior written permission of Nokia Solutions and Networks. The documentation hasbeen prepared to be used by professional and properly trained personnel, and thecustomer assumes full responsibility when using it. Nokia Solutions and Networkswelcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this documentation concerning the suitability,

capacity, or performance of the mentioned hardware or software products are given“as is” and all liability arising in connection with such hardware or software productsshall be defined conclusively and finally in a separate agreement between NokiaSolutions and Networks and the customer. However, Nokia Solutions and Networkshas made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia Solutions andNetworks will, if deemed necessary by Nokia Solutions and Networks, explain issueswhich may not be covered by the document.

Nokia Solutions and Networks will correct errors in this documentation as soon aspossible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLEFOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDINGBUT 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 ORDATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected bycopyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Solutions and Networks Oy. Nokia is aregistered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of theirrespective owners, and they are mentioned for identification purposes only.

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



LTE_RL50_0.2.3 Change Note Forms

Copyright © 2014 Nokia Solutions and Networks. All rights reserved

CONFIDENTIAL

APPROVED 1.0 Page 1

Change Note Forms

Id: LTE_RL50_0.2.3Release Delivery: RL50 0.2.3Product Family: Base StationsProduct: Flexi Multiradio BTS LTERelease: LN5.0 0.2.3

Approved version: 16-Jul-2014

Nokia Solutions and Networks is continually striving to reduce the adverse environmentaleffects of its products and services. We would like to encourage you as our customers andusers to join us in working towards a cleaner, safer environment. Please recycle productpackaging and follow the recommendations for power use and proper disposal of ourproducts and their components.

If you should have questions regarding our Environmental Policy or any of theenvironmental services we offer, please contact us at Nokia Solutions and Networks foradditional information.





CONFIDENTIAL

APPROVED 1.0 Page 2

CN-id: LN50_00060

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

Version of the SW-build :LN5.0_ENB_1304_647_34

Valid for Product(s):

Flexi LTE Base Station

References:

Reason fo r the Change Note:

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 (notvisible over the air).The problem was reproduced in the field, it was observed that the occurrence depends onRF conditions (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 wastriggered:• 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 somepaging operation successfully as long as “incoming rate of paging related requestedtowards MAC doesn’t exceed ~1/20ms” if it does – operation will fail due to lack ofmessage array resources.

In poor RF conditions, more re-tries triggered by MME are expected if normal pagingdoesn’t go through which implies higher message array utilization – increased probabilityof ETWS failure.

Related feature / funct ionality:

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 forthe starting time of previous paging to expire.





CONFIDENTIAL

APPROVED 1.0 Page 3

Corrected Fault Reports :NA05681287

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

Modified components:

Component Version *Net element *SW-type *Unit

fb_13_04_02.- 315747 - - -

Change effects:

Effects on end-user

NA

Effects on Operator

NA

Other effects

NA

New functionality

NA

Customer Impact

User Plane QualityReliabilty of ETWS BCCH paging in high load paging scenario and high interference

environment.

Testing Instructions for the change

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 newBcchMod messages:

- 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. 0715: 52: 16. 895953> 21 ERR/ LTEMAC/ DLMAC/ 012/ FFFFFFFF: FFFFFFFF/ CMacPcchDat aSendReqMsgAr r ay: : AddMe

ssage: Message arr ay f ul l y occupi ed! ( msgAr r aySi ze=34)





CONFIDENTIAL

APPROVED 1.0 Page 4

025203 03. 07 16: 52: 12. 664 [ 192. 168. 255. 129] 12 FSP- 1231 <03. 07

15: 52: 16. 895957> 21 ERR/ LTEMAC/ DLMAC/ 012/ FFFFFFFF: FFFFFFFF/ CDl Suppor t PcchSend: : handl eMAC_BcchModI ndReq: Moddi ng of pagi ng el ement f ai l ed!

Unexpected results :

The syslog has below prints:

025202 03. 07 16: 52: 12. 664 [ 192. 168. 255. 129] 11 FSP- 1231 <03. 0715: 52: 16. 895953> 21 ERR/ LTEMAC/ DLMAC/ 012/ FFFFFFFF: FFFFFFFF/ CMacPcchDat aSendReqMsgAr r ay: : AddMessage: Message arr ay f ul l y occupi ed! ( msgAr r aySi ze=34)

025203 03. 07 16: 52: 12. 664 [ 192. 168. 255. 129] 12 FSP- 1231 <03. 07

15: 52: 16. 895957> 21 ERR/ LTEMAC/ DLMAC/ 012/ FFFFFFFF: FFFFFFFF/ CDl Suppor t PcchSend: : handl eMAC_BcchModI ndReq: Moddi ng of pagi ng el ement f ai l ed!



LTE_RL50_0.2.3 Impact Document


CONFIDENTIAL

APPROVED 1.0 1 (4)

Impact Document

Id: LTE_RL50_0.2.3Release Delivery: RL50 0.2.3Product Family: Base StationsProduct: Flexi Multiradio BTS LTE Release: LN5.0 0.2.3


Nokia Solutions and Networks is continually striving to reduce the adverse environmentaleffects of its products and services. We would like to encourage you as our customers andusers to join us in working towards a cleaner, safer environment. Please recycle productpackaging and follow the recommendations for power use and proper disposal of ourproducts and their components.

If you should have questions regarding our Environmental Policy or any of theenvironmental services we offer, please contact us at Nokia Solutions and Networks foradditional information.





CONFIDENTIAL

APPROVED 1.0

2 (4)

Table of Contents

1

Purpose ......................................................................................................................................................... 3 2 Release 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:






CONFIDENTIAL

APPROVED 1.0

3 (4)

1 PURPOSE

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

This document describes the new corrections and feature enhancements delivered inFlexi Multiradio BTS LTE RL50_0.2.3.

2 RELEASE DELIVERY EFFECT

This LTE_RL50_0.2.3 software priority package contains:

• 1 new correction

RL50 0.2.3 can be background downloaded to the FCM prior to activation. Activation of theeNB software will cause momentary loss of service in the serving cells as the FCM will bereset.

The rough SW download and activation times:

SW downloadeNB with FSME ~ 36 min

eNB with FSMF ~ 15 min

SW activation (including eNB reset), causing temporary loss of service ~ 8 min

3 EFFECTS ON END-USER

N/A

4 EFFECTS ON OPERATOR

Flexi Multiradio LTE Base station operability is improved with the corrections and featureenhancement listed in Summary of Corrections and Enhancements document.

5 OTHER EFFECTS

N/A

6 NEW / CHANGED FUNCTIONALITY

N/A

7 APPENDICES / REFERENCES





CONFIDENTIAL

APPROVED 1.0

4 (4)

Disclaimer

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Solutions and Networks customers only for the purposes of the agreement underwhich the document is submitted, and no part of it may be used, reproduced, modified ortransmitted in any form or means without the prior written permission of Nokia Solutions andNetworks. The documentation has been prepared to be used by professional and properlytrained personnel, and the customer assumes full responsibility when using it. Nokia Solutionsand Networks welcomes customer comments as part of the process of continuous developmentand improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity,or performance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Solutions and Networks and the customer.However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the

instructions contained in the document are adequate and free of material errors and omissions.Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks,explain issues which may not be covered by the document.

Nokia Solutions and Networks will correct errors in this documentation as soon as possible. INNO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT ORTHE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

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

Corporation. Other product names mentioned in this document may be trademarks of theirrespective owners, and they are mentioned for identification purposes only.




LTE_RL50_0.2.3 Installation Instructions


CONFIDENTIAL

APPROVED 1.0 1 (23)

Installation Instructions

Id: LTE_RL50_0.2.3Release Delivery: RL50 0.2.3

Product Family: Base StationsProduct: Flexi Multiradio BTS LTERelease: LN5.0 0.2.3


Nokia Solutions and Networks is continually striving to reduce the adverseenvironmental effects of its products and services. We would like to encourageyou as our customers and users to join us in working towards a cleaner, saferenvironment. Please recycle product packaging and follow the recommendationsfor power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of theenvironmental services we offer, please contact us at Nokia Solutions andNetworks for additional information.





CONFIDENTIAL

APPROVED 1.0 2 (23)

Table of Contents1. Purpose ......................................................................................................................................................... 3

2.

Overview ....................................................................................................................................................... 3

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

3. Preparations .................................................................................................................................................. 3

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

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

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

5.2 RF sharing ............................................................................................................................................................... 5

5.2.1 LTE-GSM RF Sharing .................................................................. ..................................................................... ....... 5

5.2.2 WCDMA-LTE RF Sharing ............................................................................................... ......................................... 7

5.3 Compatibility Matrix ........................................................... ..................................................................... .................. 7

6. Data migration ............................................................................................................................................... 8

7. Release delivery upgrade instructions .......................................................................................................... 8

7.1 Flexi Multiradio BTS LTE ......................................................................... ................................................................ 8

7.1.1 First installation and commissioning .................................................................... ..................................................... 8

7.1.2

Project upgrade ................................................................. ..................................................................... .................. 8

7.2 SON ........................................................... ..................................................................... ......................................... 9

8. Operational hints and recommendations .................................................................................................... 10

9. Checking of the package consistency ........................................................................................................ 21

9.1 Flexi Multiradio BTS LTE ......................................................................... .............................................................. 21

9.2 LTE iOMS .............................................................................................................................................................. 21

10. Fallback ....................................................................................................................................................... 21

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

Contact:

Contact your local Nokia Solutions and Networks support

Summary of changes:






CONFIDENTIAL

APPROVED 1.0 3 (23)

1. PURPOSE

The purpose of this document is to describe the actions needed for this Release Delivery forinstall at lab for trials.

2. OVERVIEW

This document covers Installation Instruction Flexi Multiradio BTS LTE (eNB) and LTE iOMS.Standard installation instructions are available in the Customer Documentation libraryaccessible through NOLS [1] at:

• Nokia Solutions and Networks Long Term Evolution Information Center [4]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 for

installation 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. A way to access Customer Documentationis described in point 2.1.

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 Solutions and Networks Long Term Evolution Information Center [4]

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

3. PREPARATIONS

1. 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 found inthe section “Install and commission” in the Customer Documentation library

• For the Flexi Multiradio BTS LTE reference documents are named “Installing FlexiMultiradio BTS LTE…” [2] (Figure 1)

https://online.portal.nokiasiemensnetworks.com/pic/gateway/finder







CONFIDENTIAL

APPROVED 1.0 4 (23)

Figure 1 Documents needed for preparations in Customer Documentation library

2. To enable usage of SON features some preparation steps must be taken. It is described inCustomer Documentation library in section “Functional Area Description-Operability-Configuration Management-SON management” chapter 4 “Functional description for SONmanagement” [5].





CONFIDENTIAL

APPROVED 1.0 5 (23)

4. SW DOWNLOADING INSTRUCTIONS

The software for the released products is available in NOLS.

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

• Flexi Multiradio BTS LTE:

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

After downloading the software it is important to generate SH1 checksum for files and compareit with the one provided in the Summary of Corrections and Enhancements document, this willensure that the files were not corrupted during downloading.

• LTE iOMS:

There is no new version of LTE iOMS SW.The last released LTE iOMS SW version was published in LTE_RL50 available under belowlink:

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

After downloading the software it is important to generate SH1 checksum for files and compareit with the one provided in the Summary of Corrections and Enhancements document, this willensure that the files were not corrupted during downloading. After downloading the software it is important to generate SH1 checksum for files and compareit with the one provided in the Summary of Corrections and Enhancements document, this willensure that the files were not corrupted during downloading.

5. SPECIAL CONDITIONS

5.1 Flexi Multiradio BTS LTE

FHCA 472169A.103 product (FPGA) should be used in max. 2*20W DL power. Thisfirmware must only be used under the following conditions: 20W mode -40 to +50 degrees.

FRGP should be used in 2*15W DL power .

5.2 RF sharing

RL50 0.2.3 has the same compatibility as RL50 0.2.

5.2.1 LTE-GSM RF Sharing

The released GSM BTS SW for RF Sharing with RL50 are EX5 and EX5.1 (RG20 EP2, RG30 and RG30EP1) according to the table below. It is recommended to use the latest released GSM SW, i.e. EX5.1.

Software Item Software File Name SHA1 checksumeNB LN5.0_ENB_1304_647_34_release_BTSSM_

downloadable.zip BF50DF1CDDF99F630714A5844EB97FB544071F5F

BTS Site Manager BTS_Site_Manager_LN5.0_BTSSM_1304_07

9_00.zip

CBA088A2789F275D1919DC53683

44413ACBF4CDE Golden SCF Golden_SCF-FB1304_619--onwards-2014-

01-22.zip D41BE4D9D81D08F04F83404A4BDA5A2F30DD6581

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














CONFIDENTIAL

APPROVED 1.0 6 (23)

EX5 EX5.1

P8 0.0.11.0.X

(x=0..3)

2.1.X

(x=0,1,2) P8

RL50

P8- Rel. Rel. Rel. REC.

RL50

0.2- Rel. Rel. Rel. REC.

Rel. SW combination releasedREC. SW combination recommended

- SW combination not released

For details on supported configurations, such as: power levels, antenna configuration types,requirements, bands, and so on, see Flexi Multiradio BTS RF Sharing Supported Configurations excelfile.

Release Upgrade Instructions - Project upgradeThe following upgrade paths in case of GSM-LTE RF Sharing are recommended:

LN4.0 1.1.0/EX5 1.0.2 to LN5.0 0.2/EX5.1 orLN4.0 2.0/EX5 2.1.1 to LN5.0 0.2/EX5.1 or

LN4.0 2.1/EX5 2.1.1 to LN5.0 0.2/EX5.1 orLN4.0 3.0/EX5.1 to LN5.0 0.2/EX5.1 orLN5.0/EX5.1 to LN5.0 0.2/EX5.1

It is recommended to first upgrade the master technology (i.e. LTE) as the SW management of RadioModules in RF sharing is done via the master System Module only.





CONFIDENTIAL

APPROVED 1.0 7 (23)

5.2.2 WCDMA-LTE RF Sharing

The released WCDMA BTS SW for RF Sharing with RL50 0.2 is WN8.0 (RU40) according to the tablebelow. It is recommended to use the latest released WCDMA SW, i.e. WN8.0 2.1.

LN5.0

P8 0.2

RU40

P8-

RU40

MP1.0REC.* Rel.*

RU40

MP2.1Rel.* REC.*

* only for WCMDA FSMC/D/E

Rel. SW combination releasedREC. SW combination recommended

- SW combination not released


Release Upgrade Instructions:The following upgrade paths in case of WCDMA-LTE RF Sharing are recommended:

WN8.0 1.0/LN5.0 to WN8.0 2.1/LN5.0 0.2

Unless otherwise stated, it is recommended to first upgrade the master technology (i.e. WCDMA) as theSW management of Radio Modules in RF sharing is done via the master System Module only.


5.3 Compatibility Matrix

SWdelivery

Flexi Multiradio BTSLTE

BTSSM LTE iOMS NetActSEM

validator

RL50 LN5.0_ENB_1304_619_02LN5.0_BTSSM_1304_074

_00R_GOMS6_1.107.1.0_corr24

OSS5.5+

WU0914

LN5.0_BTSSM_1304 _074_00

RL50 0.1 LN5.0_ENB_1304_645_03LN5.0_BTSSM_1304_076

_00R_GOMS6_1.107.1.0_corr24

OSS5.5+

WU0925

LN5.0_BTSSM_1304 _076_00

RL50 0.2 LN5.0_ENB_1304_647_28

LN5.0_BTSS

M_1304_079 _00

R_GOMS6_1.107.1.0_corr24

OSS5.5

+WU0929

LN5.0_BT

SSM_1304 _077_00





CONFIDENTIAL

APPROVED 1.0 8 (23)

RL50 0.2.1 LN5.0_ENB_1304_647_33LN5.0_BTSSM_1304_079

_00

R_GOMS6_1.107.1.0_corr24OSS5.5

+

WU0929

LN5.0_BTSSM_1304

_077_00

RL50 0.2.3 LN5.0_ENB_1304_647_34LN5.0_BTSSM_1304_079

_00R_GOMS6_1.107.1.0_corr24

OSS5.5+

WU0929

LN5.0_BTSSM_1304 _077_00

6. DATA MIGRATION

n/a

7. RELEASE DELIVERY UPGRADE INSTRUCTIONS


7.1.1 First installation and commissioning

The commissioning procedure of the Flexi Multiradio BTS LTE is described in the document“Commissioning Flexi Multiradio BTS LTE” [3].Please be aware that BTS Site Manager shall be updated before the BTS SW.

LTE940 U-boot security is active!For all upcoming RL50 releases the feature LTE940 SW Verification Agent is active per default.With this feature only certified SW packages will be accepted at eNB to get active. For thispurpose the U-Boot SW already in RL40 has to be activated/prepared. Therefore every upgradefrom RL40 to RL50 has to pass the RL40MP1.1.x. Which means RL40MP1.1.x has to beinstalled first, before upgrade to RL50. In case the RL40 MP1.1.x or later releases are alreadyinstalled no special activities are necessary.

7.1.2 Project upgrade

System upgrade is described in customer documentation "LTE System Upgrade" [7].

Following update/upgrade paths are suppor ted:

• Customer specific RL50 0.2.1 (LN5.0_ENB_1304_647_33) -> RL50 0.2.3

Update/upgrade from mentioned above SW load to RL50 0.2.3 SW was tested and this arerecommended update/upgrade paths.

Note:HW configuration changes should not be done during SW upgrade as this may lead toinconsistencies in the internal configuration files. Changes in configurations should either beexecuted before SW upgrade or after SW upgrade. In case the changes has been executedbefore SW upgrade a SW fallback will keep the configuration changes. In case the configurationchange will be done direct after SW upgrade and then a SW fallback will be initiated, thechanged configuration may lead to start up problems with former SW. Reason would be that theinternal configuration file of pre-upgrade will be used and this may not match the changedconfiguration.

LTE940 U-boot security is active!For all upcoming RL50 releases the feature LTE940 SW Verification Agent is active per default.

With this feature only certified SW packages will be accepted at eNB to get active. For thispurpose the U-Boot SW already in RL40 has to be activated/prepared. Therefore every upgrade





CONFIDENTIAL

APPROVED 1.0 9 (23)

from RL40 to RL50 has to pass the RL40MP1.1.x. Which means RL40MP1.1.x has to beinstalled first, before upgrade to RL50. In case the RL40 MP1.1.x or later releases are already

installed no special activities are necessary.

Note: In case the upgrade to RL50 has been done via RL40MP1.1.x or later releases, there isno way back to RL40 releases before RL40MP1.1.x. Executing downgrades from RL50 to preRL40MP1.1.x will destroy the FSMF and it has to be send back to factory for repairing.

See Technical Support Notes:

• TS-LTE_BTS_FDD-SW-0047: Severe issue - introduction of the LTE940 - SWVerification Agent

• TS-LTE_BTS_FDD-SW-0042: FSMF A102 U-boot downgrade is not possible

RF Sharing

Unless otherwise stated, it is recommended to first upgrade the master technology (i.e. LTE) asthe SW management of Radio Modules in RF sharing is done via the master System Moduleonly.

7.2 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].Descriptions and hints about SON feature usage can be found also in Customer Documentationfor NetAct.





CONFIDENTIAL


8. OPERATIONAL HINTS AND RECOMMENDATIONS

Instructions to force 4X link speed for FRIG RRH module:

A) Disable the Ethernet Port Security with the BTS Manager in order to be able to login withtelnet to the RF-modules:BTS Manager / Tools / Ethernet Port Security

Disable the Port Security.

Now you are able to do whatever is needed, but be carefully.





CONFIDENTIAL


B) Force 4X link speed for FRIG RRH module via telnet (Command lines will be writtendirectly in RF shell Unix and will be permanently stored).

1. First login with telnet to first RFmodule, then to second RF module and finally tothird RF module, always with port 2323. IP addresses see table below.

Example: From RUN cmd “ telnet 192.168.253.196 2323”

2. Enter command for deactivation 8X link speed:

r ad - pw 0xef 13. Unit reset or site reset is needed.

This has to be done once for each FRIG unit.

During startup the command lines will be stored automatically within RF unit /ram.

RF module/heads IP addresses (changed in RL50):

Addresses of the fist RF modulesRF 1.1.1 192.168.253.196RF 1.2.1 192.168.253.204RF 1.3.1 192.168.253.212RF 1.4.1 192.168.253.220RF 1.5.1 192.168.253.228RF 1.6.1 192.168.253.236

Addresses of the second RF modules in a chainRF 1.1.2 192.168.253.197RF 1.2.2 192.168.253.205RF 1.3.2 192.168.253.213RF 1.4.2 192.168.253.221RF 1.5.2 192.168.253.229RF 1.6.2 192.168.253.237

Addresses of the third RF modules in a chainRF 1.1.3 192.168.253.198RF 1.2.3 192.168.253.206RF 1.3.3 192.168.253.214RF 1.4.3 192.168.253.222RF 1.5.3 192.168.253.230RF 1.6.3 192.168.253.238

C) Enable the Ethernet Port Security with the BTS Manager (see above).





CONFIDENTIAL


Operator Hint fo r LTE649:

In RL20 and RL30, configuration of a VLAN-ID with value zero (0) was possible, violating IEEEstandards. In case an operator used this value in the transport network designs, it is necessaryto change this network configuration to standard conform values (i.e., VLAN-ID 1...4094) beforemigrating to LTE RL40 or to LTE RL50

Restrict ion for Installation Factory FSMF plus FTIF

Factory new FSMF having SW version LN4.0_ENB_9402_280_00 installed must not beequipped with FTIF before SW-Update to LN4.0_ENB_1202_XXX_YY.FSMF module will reboot every 5 min and no proper SW Download will be possible.

Workaround if FTIF was already physically installed:1. Power off FSMF.

2. Remove FTIF Module.3. Power on FSMF. If FTIF is removed from FSMF, alarm "Transport Module missing" willappear. SW Download will fail, since recognized module FTIF cannot be properlyinstalled.

4. Recover FTM needs to be executed via https://192.168.255.129. 5. Afterwards start normal SW Download procedure without FTIF to a SW Load equal or

newer than LN4.0_ENB_1202_XXX_YY.6. Install FTIF after successful reboot of FSMF.

UPDATE FROM LN5.0_ENB_1304_255_00 TO RL50

1. Check if "LNCELL - SCell deactivation timer eNB" is set to rf128/128, if yes, change it to rf64

2. Downgrade first from LN5.0_ENB_1304_255_00 to LN5.0_ENB_1304_251_003. Now Update from LN5.0_ENB_1304_251_00 to LN5.0_ENB_1304_344_264. Change back "LNCELL - SCell deactivation timer eNB" to 128

Operator Hint for Juniper:

While using Multi-Layered Certificates in combination with Juniper (JunOS 11.4R6S1 Junos11.4R6-S1) as SEC-GW, IPsec Connections between eNB and SEC-GW are only possible if theusedcertificates for both devices are at the same branch and the same level of the Certificate Chain. Any other combination of different certificate level or branches for eNB and SEC-GW are not

working.

https://192.168.255.129/

https://192.168.255.129/

https://192.168.255.129/





CONFIDENTIAL


Operator Hint for Checkpoint :

Operation mode : Round robin for Ethernet interface on Checkpoint should be avoided aspacket loss is observed with this setting in R&D Lab. Recommended setting for Ethernetinterface operation mode configuration at Checkpoint to be set to LACP(802.3ad) .

IKEv1:To work with IKEv1 one need to choose exclusively “IKEv1 only” mode in community level onCP.

IKEv1:Multi tunnel configuration: Not released(Restriction for multi tunnel configurations due to CP offering of traffic selector of 0.0.0.0/00.0.0.0/0 (universal tunnel) and so no IPSec SA established.)

Multi Layer Certificates:Multi Layer Certificates operation with Checkpoint is not released by NSN Security organization.

SFP hot swapping at FSMF or FXEB

If exchanging any SFP connector to another SFP with a different speed capability (hot swap),

Radio Unit gets rebooted and all the cell goes on air without any alarm or warning. But all RACHattempts fail and no call setups are possible.

Solution: If the SFP connection was hot swapped, a Site Reset is required.

Operator Hint for LTE523:

Manual key and certificate commissioning: BTS and eNB does not support slash “/” as subjectname element separator.





CONFIDENTIAL


Operator Hint fo r LTE497:

When 'Enhanced AC and GBR services' are activated, i.e. if actEnhAcandGbrServices equals'true', it is highly recommended to configure gbrCongHandling to 'l2andl3'. If it not configured likethis, GBR admission in empty cells may fail.

Cabling: Fibers to radio module:

The parallel fibers to radio module shall be in same cable. This ensures that both fibers aresame length and the system works. The system now allows max. 5 meters length differencebetween main and secondary fibers.

MTU size in OMS, CA Server and LDAP Server needs to be reduced to 1400 bytes whenIP-Sec is used:

IPSec requires add. IP overhead. In case the default MTU size of 1500 Bytes is used, the IPSecGateway needs to fragment the IP packets before encrypting is done. Some applications aresetting the ‘don’t fragment’ bit, which is prohibiting the fragmentation, but in this case the IPpackets are dropped and not transferred at all. In order to avoid this the MTU size of OMS, CAServer and LDAP Server shall be limited.For OMS:

f si pnet bond modi f y bond0 node CLA- 0 mt u 1400f si pr econf i gur e commi t

IPsec PROTECT / BYPASS pol icies defini tion :

For the configuration of IPsec policies in the eNB, the following rule needs to be considered. Incase of several matching IPsec policies, the policy rule which shall be applied needs to have alower number than the other matching policy. The lowest number of several matching policies isapplied first.

For example, if a wide-ranging PROTECT policy is defined (e.g. ANY-TO-ANY) and a dedicatedtraffic type shall bypass the IPSec tunnel, than the BYPASS policy needs to be configured with alower ‘Policy Order Number’ than the protect policy.

LTE710 Synchronization from PDH interface

LTE713 Synchronous EthernetLTE134 Timing over Packet

If PDH is chosen as synchronization source and Synchronous Ethernet or Timing over Packetas secondary synchronization source, but no PDH signal is connected, then after an eNB resetthe transport module is forwarding an internal clock to system module for some seconds, beforethe correct clock derived from chosen secondary synchronization is forwarded.This disturbs BTS internal tuning and the next calculated DAC word is wrong by max. 6 digits(about 5 ppb). The disturbance is not service affecting. After 20 minutes the next DAC word is again correct. This can be followed by Site Manager (SiteInformation > Site information > BTS clock tuning history).

ICMP rate limiting





CONFIDENTIAL


In order to avoid a system outage due to DoS attacks (ICMP flood) the ingress and egressICMP packet rates are limited. Only a burst of 8 ICMP_ECHO_REQUESTS /

ICMP_ECHO_REPLY are allowed. If e.g. more than 8 ICMP_ECHO_REQUESTS are sent in aburst, eNB will only reply to the first 8. This is applicable for the eNB interface address(es)(Ethernet and VLAN).

LTE574 IP Transport Network Measurements

Configuration of the UDP Port number of the TWAMP Responder

Currently, the UDP port of the TWAMP Reflector can be freely configured in the range from 0 to65535, with a default value of 5000. Free configuration of this parameter requires special care,since the entries may conflict with port numbers which are already assigned to other

applications. E.g. the port numbers 0 … 1023 and 5001 … 5010 are reserved and must not beused for the TWAMP responder function. Currently, the system does not support a completecheck of the configured TWAMP responder port number against all other port numbers used inthe system.

To avoid conflicts between the TWAMP UDP port number and other port numbers, it isrecommended to always use the default value of 5000. It has been found that the flexibility inconfiguring the port number does not provide a real benefit, and using a fixed value eliminatesthe possibility of mis-configurations.

BTS Site Manager:

Date/time included in fault name of transmission alarms is misleading in BTS Site Manager.Same issue is correctly displayed in NetAct Alarm Monitor.

Recommendations for RF Sharing WCDMA-LTE dual band configurations:

• During FSMF rollout 3G SM optIf4 should be connected to 4G FSMF optIf6 for sync Advantage: No change of sync port during upgrade to dual band configuration

• Install FBBA during FSMF rollout Advantage: No additional power off/on reset during upgrade from single band RFsharing

RF Sharing WCDMA-LTE Synchronization:

• Clock source switching from OCXO to clock received from RP3-01, when operating asan extension system module or as a synchronization slave system module.

• At slave system module, the setting about the sync is not necessary. Synchronizationwill be fixed to master system module.

• If system module is synchronized to master system module, Site manager will displaythe synchronization source as “Other BTS”.

Operator hin t for RF sharing WCDMA-LTE with FSMF used for the LTE side

LTE side:





CONFIDENTIAL


Local Maintenance Terminal (LMT) of the LTE eNB:Set the IP address of the LMT PC to 192.168.255.126/24.

LTE BTS Site Manager:It is possible to use local or remote IP addresses to login to the LTE eNB with BTS SiteManager.In case of using the local IP address, for a standalone LTE eNB choose the option “Local”:





CONFIDENTIAL


For an LTE eNB running in RF sharing WCDMA-LTE configuration, choose “Local(192.168.255.127)”:





CONFIDENTIAL


After enabling or disabling RF sharing for the LTE eNB, please restart the BTS Site Managerwith the correct option.

Alternatively the remote IP address of the LTE eNB can be used.





CONFIDENTIAL


WCDMA side:

Local Maintenance Terminal (LMT) of the LTE eNB:Set the IP address of the LMT PC to 192.168.255.130/24.

WCDMA BTS Site Manager:It is possible to login with local or remote IP addresses to the WCDMA BTS with BTS SiteManager. Use the option Local, or the remote IP address of the BTS.For example, using the option Local:





CONFIDENTIAL


Don’t configure LTE-3G RF sharing in use if shared BTS site does not contain3G system module

If 3G system module does not exist AND if LTE-3G RF sharing has been taken into use thenBTS remains in initializing state because 3G system module is fixedly synchronization master inLTE-3G RF sharing and if it does not exist then BTS remains in initializing state. Initializing statein BTS SW prevents reconfiguration commissioning from BTSSM

Workaround:If this accidently happens it is possible to commission BTS to the synchronization master modevia NetAct, because Flexi Radio auto-detection is not required, when commissioned via NetAct.

New additional i nformation in alarms

In NetAct following new information is included in the field Supplementery Information of thealarms:shared:M, shared:S, shared:D or shared:N.

The letters mean following:

N - Not shared, default valueD - Alarm is related only to dedicated resourcesS - Alarm is from slave RATM - Alarm is from master RAT





CONFIDENTIAL


By default the alarms from the slave RAT (shared:S) are hidden in NetAct, i.e. not listed in the Alarm Monitor. Only alarms from the master RAT are shown in the Alarm Monitor. In the NetActapplication FM Rule Editor it is possible to switch off the Rfsharing filter that filters the slavealarms out.

The additional information can be seen in BTS Site Manager as well, in the field Additionalinformation.E.g. Sharing mode information: Fault from slave RAT.

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

n/a

10. FALLBACK

When OAM System Preference is set to Secondary Forced in RL50 and Fallback to RL40 P8 orRL40 MP1.0 or RL40 MP1.1 is started, the serving OMS will be Primary after the fallback isfinished in spite of Secondary Forced. It is necessary to adjust the correct OMS via switching toprimary and back to secondary.

RL40 2.1 Maintenance Package is precondition that upgrade and fallback works.





CONFIDENTIAL


11. APPENDICES / REFERENCES

[1] NOLS - Nokia Solutions and Networks Online Services log in link:https://online.portal.nokiasiemensnetworks.com

[2]- "Installing Flexi Multiradio 10 Base Station for Stack, Wall, and Pole Configurations",DN09107819, Issue 06- "Installing Flexi Multiradio BTS LTE Modules for Stack, Wall, and Pole Configurations",DN0951987, Issue 05- "Installing Flexi Multiradio Base Station and Flexi Multiradio 10 Base Station Modules inCabinets", DN09147506, Issue 01A- "Installing Flexi Multiradio Base Station and Flexi Multiradio 10 Base Station Optional Items",DN09142359, Issue 01A- "Installing Flexi Cabinet for Outdoor (FCOA)", DN09144084, Issue 01- "Installing Flexi Cabinet for Indoor (FCIA)", DN09144096, Issue 01- "Cabling Flexi Multiradio 10 Base Station", DN09107822, Issue 04

- "Cabling Flexi Multiradio BTS LTE", DN0951881, Issue 04A[3] "Commissioning Flexi Multiradio BTS LTE", DN0951893, Issue 05A[4] Link to Nokia Solutions and Networks Long Term Evolution Information Center:https://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:133-047489&RId=urn:temp:Flexi-LBTS5.0 (LTE Radio Access, Rel. RL50, Operating Documentation, Issue 02) [5] "SON Management", DN0944055, Issue 05[6] "Upgrading from LTE OMS 3.0 or LTE OMS 4.0 to LTE OMS 5.0", DN0983101, Issue 01[7] "LTE System Upgrade", DN09147545, Issue 01[8] "Installing and Commissioning LTE iOMS", DN0956464, Issue 05A[9] "Flexi Multiradio BTS RF Sharing Released Configurations", DN09123381, Issue 11

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


https://online.portal.nokiasiemensnetworks.com/pic/com/nsn/extranet/pic/controller/productinfoview/pivdocumentation.do?productId=urn:nsn.com:mxpdm:133-047489&RId=urn:temp:Flexi-LBTS5.0










Disclaimer

The information in this document is subject to change without notice and describesonly the product defined in the introduction of this documentation. This documentationis intended for the use of Nokia Solutions and Networks customers only for thepurposes of the agreement under which the document is submitted, and no part of itmay be used, reproduced, modified or transmitted in any form or means without theprior written permission of Nokia Solutions and Networks. The documentation hasbeen prepared to be used by professional and properly trained personnel, and thecustomer assumes full responsibility when using it. Nokia Solutions and Networkswelcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this documentation concerning the suitability,capacity, or performance of the mentioned hardware or software products are given“as is” and all liability arising in connection with such hardware or software products

shall be defined conclusively and finally in a separate agreement between NokiaSolutions and Networks and the customer. However, Nokia Solutions and Networkshas made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia Solutions andNetworks will, if deemed necessary by Nokia Solutions and Networks, explain issueswhich may not be covered by the document.

Nokia Solutions and Networks will correct errors in this documentation as soon aspossible. IN NO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLEFOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDINGBUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL ORCONSEQUENTIAL 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 THEINFORMATION IN IT.

This documentation and the product it describes are considered protected bycopyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Solutions and Networks Oy. Nokia is aregistered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of theirrespective owners, and they are mentioned for identification purposes only.

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