Umtsysdd043248lr14w v1 Lr14.w Upgrade Paths

LR14.W Upgrade Paths

Document number: UMT/SYS/DD/043248 Document issue: 01.09 / EN Document status: Standard-Approved Date: 11/Jul/2014

External document

Copyright 2014 Alcatel-Lucent, All Rights Reserved

Printed in France

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is write

protected; it may be altered only by authorized persons. While copies may be printed, it is not recommended.

Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be

regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-

Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information

contained herein confidential, shall disclose the information only to its employees with a need to know, and

shall protect the information from disclosure and dissemination to third parties. Except as expressly

authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained

herein. If you have received this document in error, please notify the sender and destroy it immediately.


Alcatel-Lucent Networks confidential

UMT/SYS/DD/043248 01.09 / EN Standard-Approved 11/Jul/2014 Page 3/27

PUBLICATION HISTORY

27/March/2014

Issue 01.01 / EN, Draft

Creation

1/April/2014


Updates based on review feedback, and addition of Pre-check and Non-iso-functional behaviour for each LR14 feature in section 9.

2/April/2014


Updates to section 9 to align with latest feature list for LR14.2W (as of 2 April 2014).

16/April/2014


Updates based on review feedback

16/May/2014

Issue 01.05 / EN, Preliminary-Approved


17/Jun/2014



20/Jun/2014



30/Jun/2014



11/Jul/2014

Issue 01.09 / EN, Standard-Approved




CONTENTS

1. INTRODUCTION .............................................................................................................................. 6 1.1. OBJECT ..................................................................................................................................... 6 1.2. SCOPE OF THIS DOCUMENT ............................................................................................................. 6 1.3. FRS .......................................................................................................................................... 6 1.4. AUDIENCE FOR THIS DOCUMENT ...................................................................................................... 6

2. RELATED DOCUMENTS .................................................................................................................. 7

2.1. APPLICABLE DOCUMENTS ............................................................................................................... 7

2.2. REFERENCE DOCUMENTS ................................................................................................................ 7

3. BENEFITS ........................................................................................................................................ 8 3.1. CUSTOMER/SERVICE PROVIDER BENEFITS .......................................................................................... 8 3.2. END USER/SUBSCRIBER BENEFITS ..................................................................................................... 8

4. FUNCTIONAL OVERVIEW ............................................................................................................... 9 4.1. PRINCIPLE ................................................................................................................................ 9 4.2. LR14.2W UPGRADE PATHS .........................................................................................................10

4.2.1 OAM LR14.2W ..............................................................................................................10 4.2.2 NPO6.2 LR14.2W .........................................................................................................12 4.2.3 RNC SW Upgrade Paths ...............................................................................................15 4.2.4 BTS SW Upgrade Paths ...............................................................................................16 4.2.5 RNC LR14.W and iBTS .................................................................................................17 4.2.6 RNC LR14.W and OneBTS ...........................................................................................17 4.2.7 WCE LR14.W ................................................................................................................17 4.2.8 RNS LR14.W .................................................................................................................17

5. LR14.W UPGRADE BEHAVIOUR ...................................................................................................18

6. RNC UPGRADE IMPACT SUMMARY...............................................................................................18

7. UPGRADE PERFORMANCE TARGET ...........................................................................................19

8. ABBREVIATIONS AND DEFINITIONS .............................................................................................20 8.1. ABBREVIATIONS .........................................................................................................................20 8.2. DEFINITIONS .............................................................................................................................21

9. ANNEX A: LR13.W TO LR14.W PATH .........................................................................................22 9.1. GENERAL .................................................................................................................................22

9.1.1 Capacity and Feature Licensing....................................................................................22 9.1.2 Feature Licensing ..........................................................................................................22

9.2. LR CABINETS AND CONFIGURATIONS ..............................................................................................22

9.3. LR MULTI-STANDARD RF ............................................................................................................22

9.4. SOFTWARE TRANSVERSAL ............................................................................................................23 9.4.1 Feature 174070 - PO, Capacity Improvements (Extn of 170277) .................................23

9.5. WCDMA 9370 RNC EVOLUTION .................................................................................................23 9.5.1 Feature 172767 - RNC connection dimensioning for max voice calls ..........................23




9.6. WCDMA APPLICATIONS ..............................................................................................................23 9.6.1 Feature 108103 - Enhanced CELL_FACH for UL and DL ............................................23 9.6.2 Feature 121555 - LR14.2 RNC Counter Evolutions .....................................................24 9.6.3 Feature 164968 - Support of GLONASS assistance data over IuPC (SAS centric mode) 24 9.6.4 Feature 168642 - iBTS Resource Tracking using PM Counters ...................................25 9.6.5 Feature 168705 - Noise floor self-learning algorithm for oneBTS ................................25 9.6.6 Feature 168853 - LR14W 3GPP Standards compliance ..............................................26

9.7. WCDMA NODEB EVOLUTION .......................................................................................................26 9.7.1 Feature 169488 - AISG2.0 on 9396-based RRHs Phase 1A .......................................26 9.7.2 Feature 177111 - Digital DAS using Tyco CDIU with WCDMA 9396 digital Phase 2 ..26

9.8. WCDMA RF .............................................................................................................................27




1. INTRODUCTION

1.1. OBJECT

This document does not describe the upgrades, patching procedures.

The reader is expected to have basic knowledge of UTRAN Alcatel-Lucent Networks products.

1.2. SCOPE OF THIS DOCUMENT

This document applies to the LR14.2W release.

1.3. FRS

The LR14.2W FRS/FSD are:

173944 LR14.W UTRAN Upgrade Paths and Compatibility

173328 LR14 - WMS LR14.W support and backward compatibility

1.4. AUDIENCE FOR THIS DOCUMENT

The audience of this document is: - External customers. - Alcatel-Lucent Networks teams: Support, PLM, R&D.




2. RELATED DOCUMENTS

2.1. APPLICABLE DOCUMENTS

[A1] 9YZ-04157-0072-RJZZA - Alcatel-Lucent 9353 Wireless Management System - Upgrades and Patches; Patch Installation

[A2] 9YZ-04157-0073-RJZZA - Alcatel-Lucent 9353 Wireless Management System - Workstation Client / Application Installation

[A3] 9YZ-04157-0074-RJZZA - Alcatel-Lucent 9353 Wireless Management System - OAM Upgrade Procedure

[A4] 9YZ-04157-0075-RJZZA - Alcatel-Lucent 9353 Wireless Management System - WAUT Installation and Administration

[A5] 9YZ-04157-0076-RJZZA - Alcatel-Lucent 9370 Radio Network Controller Software Upgrade Procedure Using OAM LR14.W - Intra Release Upgrade

[A6] 9YZ-04157-0077-RJZZA - Alcatel-Lucent 9370 Radio Network Controller - Software Upgrade Procedure Using OAM LR14.W - Inter Release Upgrade

[A7] 9YZ-04157-0078-RJZZA - Alcatel-Lucent 9300 W-CDMA Product Family Alcatel-Lucent Node B - Software Upgrade Procedure Using OAM LR14.W - Inter Release Upgrade

[A8] 9YZ-04157-0079-RJZZA - Alcatel-Lucent 9300 W-CDMA Product Family Alcatel-Lucent Node B - Software Upgrade Procedure Using OAM LR14.W - Intra Release Upgrade

[A9] 9YZ-04157-0080-RJZZA - Alcatel-Lucent OneBTS - Software Upgrade Procedure Using OAM LR14.W

2.2. REFERENCE DOCUMENTS

[R1] GR-1929 Reliability and Quality Measurements for Telecommunications Systems (RQMS-Wireless)




3. BENEFITS

3.1. CUSTOMER/SERVICE PROVIDER BENEFITS

Benefit Loss

Cost ownership (day to day operation, fault management, upgrade, preventive/curative maintenance....)

x

Capacity

Dimensioning (Connectivity, storage capacity....)

Engineering (coverage, C/I)

Traffic management (load sharing, compliance with recommendations...)

Robustness (restart/recovery enhancement) x

A primary objective for the service provider and the supplier is to minimize or prevent system outages and reduce upgrade duration. All effects of failures and service degradation resulting from OA&M activities (software updates to add new features or to fix a software fault) are taken into account for both total and partial outage calculations [R1]:

A RNC total or partial outage that occurs after a release is put in-service, or during hardware or software upgrades, shall be counted.

Software release: to add new features may be counted as "scheduled" activities.

Software maintenance release: to fix software faults should not be reported as "scheduled" activities but as supplier attributable.

Patches: to fix software faults should not be reported as RNC outage

System outage Performance

Total outage DPM Provider attributable

Supplier attributable x Software Maintenance release

Scheduled x Software release

Other

Partial outage DPM Provider attributable

Supplier attributable x Software Maintenance release

Scheduled x Software release

Other

3.2. END USER/SUBSCRIBER BENEFITS

Benefit Benefit Loss

Voice quality (HO, call handling enhancement)

Quality Of Service (call drop, availability...) x New services




4. FUNCTIONAL OVERVIEW

4.1. PRINCIPLE The Alcatel-Lucent Networks RNC/BTS software design involves software changes with or without data base structure changes.

Terminology:

A software release is a set of software changes representing a significant modification in the software design and introducing significant new features in the application, as well as fixing problems.

A software maintenance release is a set of changes to a release to fix problems that the supplier and customer wish to deploy on a timely basis rather than to wait for the release.

A Transparent Application Patch (TAP: only applicable to RNC) is a change in the operational behavior of a software module that is applied to the running software without service interruption.

Depending on the software change type, the customer will use the appropriate procedure to update the RNC or the BTS:

- software release inter upgrade (with MIB change)

- software release intra upgrade (without MIB change)

- software patching

For all upgrade paths, the associated upgrade fallback is supported, i.e. possibility to return on the previous version.

For each upgrade or patching procedure, an associated fallback procedure is defined.

There is no PCR upgrade.

MicroBTS / PicoBTS are no longer supported.

End of Line (EOL) equipment: Any equipment in the network which is EOL in LR13.W must be replaced before upgrade to LR14.W is performed. Please contact the relevant Customer support team for more information on equipment that is EOL in LR13.W.




4.2. LR14.2W UPGRADE PATHS

The following UTRAN upgrade paths are supported:

o UTRAN LR13.1W towards UTRAN LR14.2W

o UTRAN LR13.3W towards UTRAN LR14.2W

Customers not taking LR13.1W or LR13.3W will have to go through a 2 steps upgrade (UA08.1 to LR13W to LR14.2W)

UTRAN upgrade paths

To LR14.2W RFOA

load (*) LR14.2W GA and post-GA loads

From

LR13.3W GA and post-GA loads

Yes Yes

LR13.1W GA and post-GA loads

Yes Yes

UA08.1.5 No No

UA08.1.3 No No

(*) RFOA and any intermediate loads (MNCL or EP) before GA

4.2.1 OAM LR14.2W The OMC-R WMS on OAM09.1 must be upgraded to OAM LR14.2W before the RNS upgrade to UTRAN LR14.2W (i.e. LR14.W).

To

From

OAM09.1 EP1 (LR13.1)

OAM09.1 EP2 (LR13.1)

OAM09.1 EP3 (LR13.1 post-GA

/ LR13.3)

OAM09.1 EP4 (LR13.3)

OAM LR14.2W

OAM09.1 (LR13.1)

OMC-R EP1 Application




OAM09.1 EP1 (LR13.1)




OAM09.1 EP2 (LR13.1)



OAM09.1 EP3 (LR13.1 post-GA /

LR13.3)


OMC-R Upgrade (1)

OAM09.1 EP4 (LR13.3)

OMC-R Upgrade (1)

(1): WMS9.1 EP3 (or EP4) is a pre-requisite to upgrade WMS to WMS LR14.2W. WMS9.1 EP3 is not only a LR13.3W load but also a post-GA LR13.1W load. Thus a WMS upgrade path LR13.1W to LR14.2W is still maintained, but minimal LR13.1W line-up must be WMS9.1 EP3.




4.2.1.1 OAM LR14.2W & IBTS

Time OMC-R RNC iBTS Support Comment

Upgrade path UTRAN LR13.W towards UTRAN LR14.W

t0 OAM09.1 LR13.W LR13.W starting system configuration (1)

t0 + 1 OAM LR14.2W LR13.W LR13.W yes possible temporary system configuration (2)

t0 + 2 OAM LR14.2W LR14.W LR13.W yes transitory system configuration (3) t0 + 3 OAM LR14.2W LR14.W LR14.W yes goal system configuration

Legend:

(1): OAM09.1 WMS9.1 EP3 (or EP4) is a pre-requisite to upgrade WMS to WMS LR14.2W (c.f. 4.2.1).

(2): Possible temporary system configuration: related to a possible temporary stop phase of the upgrade path in order to get a same global UTRAN system release.

(3): Transitory system configuration: related to a maintenance upgrade phase in post DR5 timeframe; or in FCS DR5 time frame, related to a transitory period to enable to perform non regression on iso LR13.W functionality on a sub-part of a dedicated live pilot RNS (i.e. no new LR14.W feature activated). Only FOA experts are involved in this latter case. And the required system tests are only basic like PS/CS calls, SHO/HHO BTS13.W BTS14.W and HSPA/streaming tests with basic CM/FM/PM.

4.2.1.2 OAM LR14.2W & ONEBTS

Time OMC-R RNC OneBTS Support Comment


t0 OAM09.1 LR13.W LR13.W starting system configuration (1)

t0 + 1 OAM LR14.2W LR13.W LR13.W yes possible temporary system configuration (2)

t0 + 2 OAM LR14.2W LR14.W LR13.W yes transitory system configuration (3) t0 + 3 OAM LR14.2W LR14.W LR14.W yes goal system configuration

Legend:

(1): cf. 4.2.1.1

(2): cf. 4.2.1.1

(3): cf. 4.2.1.1

4.2.1.3 OAM LR 14.2W & ONEBTS & IBTS

Time OMC-R RNC OneBTS iBTS Support Comment


t0 OAM09.1 LR13.W LR13.W LR13.W starting system configuration (1)




t0 + 1 OAM LR14.2W LR13.W LR13.W LR13.W yes possible temporary system configuration (2)

t0 + 2 OAM LR14.2W LR14.W LR13.W LR13.W yes transitory system configuration (3)

t0 + 3 OAM LR14.2W LR14.W LR14.W LR14.W yes goal system configuration

Legend:

(1): cf. 4.2.1.1

(2): cf. 4.2.1.1

(3): cf. 4.2.1.1

4.2.2 NPO6.2 LR14.2W To

From

NPO5.5ML LR13.3W

NPO6.2 LR14.2W

NPO5.3ML2 LR13.1W NPO Upgrade (1) NPO Upgrade NPO5.5ML LR13.3W NPO Upgrade (2)

(1): Possible intermediate upgrade to NPO5.5ML LR13.3.W needed if currently using NPO5.3ML2 LR13.1.W. (2): NPO5.5ML LR13.3.W is a pre-requisite to upgrade NPO to NPO6.2 LR14.2W.

4.2.2.1 NPO6.2 LR14.2.W & OAM

NPO5.3ML2

OAM9.1

OAM9.1EP1

OAM9.1EP2

OAM9.1EP3

NPO5.5ML

OAM9.1

OAM9.1EP1

OAM9.1EP2

OAM9.1EP3

NPO6.2

OAM9.1

OAM9.1EP1

OAM9.1EP2

OAM9.1EP3

NPO5.5ML

OAM9.1EP3

OAM9.1EP4

NPO6.2

OAM9.1EP3

OAM9.1EP4

NPO6.2

OAMLR14.2W

OMC-R

EP Application

OMC-R

EP Application

OMC-R

EP Application

OMC-R

EP Application

OMC-R

EP Application

OMC-R

EP Application

OMC-R

EP Application

OMC-R

EP Application

OMC-R

Upgrade

NPO

Upgrade

NPO

Upgrade

NPO

Upgrade

OAM for LR13.1W

OAM for LR13.3W

OAM for LR14.2W

NPO for LR13.1W NPO for LR13.3W NPO for LR14.2W

NPO

Upgrade




To

From

NPO5.5ML LR13.3.W

OAM09.1, or OAM09.1 EP1, or OAM09.1 EP2, or

OAM09.1 EP3 (all LR13.1W)

NPO5.5ML LR13.3.W

OAM09.1 EP3 (LR13.3W)

NPO5.5ML LR13.3.W

OAM09.1 EP4 (LR13.3W)

NPO6.2 LR14.2W


OAM09.1 EP3 (all LR13.1W)

NPO6.2 LR14.2W

OAM09.1 EP3 (LR13.3W)

NPO6.2 LR14.2W

OAM09.1 EP4 (LR13.3W)

NPO6.2 LR14.2W

OAM LR14.2W

NPO5.3ML2 LR13.1W


OAM09.1 EP3 (All LR13.1W)

NPO Upgrade (1)

NPO Upgrade

NPO5.5ML LR13.3W

OAM09.1, or OAM09.1 EP1, or

OAM09.1 EP2 (LR13.1W)



NPO Upgrade (2)

NPO5.5ML LR13.3W

OAM09.1 EP3 (LR13.3W)


NPO Upgrade (2)

NPO5.5ML LR13.3W

OAM09.1 EP4 (LR13.3W)

NPO Upgrade (2)

NPO6.2 LR14.2W

OAM09.1, or OAM09.1 EP1, or

OAM09.1 EP2 (LR13.1W)



NPO6.2 LR14.2W

OAM09.1 EP3 (LR13.3W)


OMC-R Upgrade

NPO6.2 LR14.2W

OAM09.1 EP4 (LR13.3W)

OMC-R Upgrade

(1): Possible intermediate upgrade to NPO5.5ML LR13.3.W needed if currently using NPO5.3ML2 LR13.1.W. (2): NPO5.5ML LR13.3.W is a pre-requisite to upgrade NPO to NPO6.2 LR14.2W.

4.2.2.2 NPO6.2 LR14.2W & IBTS

Time NPO OMC-R RNC iBTS Support Comment


t0 NPO5.3ML2 LR13.1.W OAM09.1 LR13.W LR13.W starting system configuration

t0 + 1 NPO5.5ML LR13.3.W OAM09.1 LR13.W LR13.W yes

starting or possible temporary system configuration (1)(2)

t0 + 2 NPO6.2 LR14.2W OAM09.1 LR13.W LR13.W yes

possible temporary system configuration (3)

t0 + 3 NPO6.2 LR14.2W OAM LR14.2W LR13.W LR13.W yes possible temporary system




configuration (3)

t0 + 4 NPO6.2 LR14.2W OAM LR14.2W LR14.W LR13.W yes transitory system configuration (4)

t0 + 5 NPO6.2 LR14.2W OAM LR14.2W LR14.W LR14.W yes goal system configuration

Legend:

(1): NPO5.5ML LR13.3.W is a pre-requisite to upgrade NPO to NPO6.2 LR14.2W (c.f. 4.2.2). Starting system configuration: if already on NPO5.5ML LR13.3.W. Possible temporary system configuration: if involving upgrade to NPO5.5ML LR13.3.W if starting on NPO5.3ML2 LR13.1.W. (2): OAM09.1 WMS9.1 EP3 (or EP4) is a pre-requisite to upgrade WMS to WMS LR14.2W (c.f. 4.2.1).

(3): Possible temporary system configuration: related to a possible temporary stop phase of the upgrade path in order to get a same global UTRAN system release.

(4): Transitory system configuration: related to a maintenance upgrade phase in post DR5 timeframe; or in FCS DR5 time frame, related to a transitory period to enable to perform non regression on iso LR13.W functionality on a sub-part of a dedicated live pilot RNS (i.e. no new LR14.W feature activated). Only FOA experts are involved in this latter case. And the required NPO tests are only basic (i.e. no tuning).

4.2.2.2 NPO6.2 LR14.2W & ONEBTS

Time NPO OMC-R RNC OneBTS Support Comment


t0 NPO5.3ML2 LR13.1.W OAM09.1 LR13.W LR13.W starting system configuration

t0 + 1 NPO5.5ML LR13.3.W OAM09.1 LR13.W LR13.W yes

starting or possible temporary system configuration (1)(2)

t0 + 2 NPO6.2 LR14.2W OAM09.1 LR13.W LR13.W yes


t0 + 3 NPO6.2 LR14.2W OAM LR14.2W LR13.W LR13.W yes


t0 + 4 NPO6.2 LR14.2W OAM LR14.2W LR14.W LR13.W yes transitory system configuration (4)

t0 + 5 NPO6.2 LR14.2W OAM LR14.2W LR14.W LR14.W yes goal system configuration

Legend:

(1): cf. 4.2.2.2

(2): cf. 4.2.2.2

(3): cf. 4.2.2.2

(4): cf. 4.2.2.2




4.2.2.3 NPO6.2 LR14.2W & ONEBTS & IBTS

Time NPO OMC-R RNC OneBTS iBTS Support Comment


t0 NPO5.3ML2 LR13.1.W OAM09.1 LR13.W LR13.W LR13.W

starting system configuration

t0 + 1 NPO5.5ML LR13.3.W OAM09.1 LR13.W LR13.W LR13.W

Starting or possible temporary system configuration (1)(2)

t0 + 2 NPO6.2 LR14.2W OAM09.1 LR13.W LR13.W LR13.W yes


t0 + 3 NPO6.2 LR14.2W OAM LR14.2W LR13.W LR13.W LR13.W yes


t0 + 4 NPO6.2 LR14.2W OAM LR14.2W LR14.W LR13.W LR13.W yes

transitory system configuration (4)

t0 + 5 NPO6.2 LR14.2W OAM LR14.2W LR14.W LR14.W LR14.W yes goal system configuration

Legend:

(1): cf. 4.2.2.2

(2): cf. 4.2.2.2

(3): cf. 4.2.2.2

(4): cf. 4.2.2.2

4.2.3 RNC SW UPGRADE PATHS The following table shows the supported upgrade paths for RNC, under OAM LR14.2W:

RNC SW Upgrade Paths

TO:

FROM:

RNC LR13.1.W

RNC LR13.3.W

RNC LR14.2W RFOA (1)

RNC LR14.2W GA (2)

RNC UA08.1.3 Not Supported Not Supported Not Supported Not Supported

RNC UA08.1.5 Not Supported Not Supported Not Supported Not Supported




RNC LR13.1W Supported Supported Supported Supported

RNC LR13.3W Fallback (3) Supported Supported Supported

RNC LR14.2W RFOA (1)

Fallback (3) Fallback (3) Supported Supported

RNC LR14.2W GA (2)

Fallback (3) Fallback (3) Not Supported Supported

Legend:

(1) all RFOA and pre-GA loads

(2) all loads post-GA

(3) For fallback case, it must be checked before operation that all BTSs have been fallen-back earlier to a supported release.

4.2.4 BTS SW UPGRADE PATHS The following table shows the supported upgrade paths for NodeB, under OAM LR14.2W:

NodeB SW Upgrade Paths (3)

TO:

FROM:

BTS LR13.1.W BTS LR13.3.W BTS LR14.2W

RFOA (1)

BTS LR14.2W

GA (2)

BTS UA08.1.3 Not Supported Not Supported Not Supported Not Supported

BTS UA08.1.5 Not Supported Not Supported Not Supported Not Supported

BTS LR13.1.W Supported Supported Supported Supported

BTS LR13.3.W Fallback Supported Supported Supported

BTS LR14.2W RFOA (1)

Fallback Fallback Supported Supported

BTS LR14.2W GA (2)

Fallback Fallback Not Supported Supported

Legend:

(1) all RFOA and pre-GA loads

(2) all loads post-GA

(3) The upgrade path from LR13.W to LR14.W is not applicable for microBTS and picoBTS.




4.2.5 RNC LR14.W AND IBTS To

From

OAM LR14.2W RNC LR14.W iBTS LR13.W



RNC inter release upgrade


iBTS inter release upgrade

4.2.6 RNC LR14.W AND ONEBTS To

From

OAM LR14.2W RNC LR14.W OneBTS LR13.W


OAM LR14.2W RNC LR13.W OneBTSLR13.W

RNC inter release upgrade


OneBTS inter release upgrade

4.2.7 WCE LR14.W WCE product upgrades are out of scope of this document since WCE first official Release is LR14W.

4.2.8 RNS LR14.W

4.2.8.1 IUB INTERFACE

A RNC in LR14.W can interface with BTS in current and previous releases as per the below compatibility matrix:

RNC RNC LR14.2W RFOA

load (*) RNC LR14.2W GA and

post-GA loads

BTS

BTS LR14.2W GA and post-GA loads

No Yes

BTS LR14.2W RFOA load (*) Yes Yes


Yes Yes


Yes Yes

BTS UA08.1.5 No No

BTS UA08.1.3 No No





4.2.8.2 IUR INTERFACE

A RNC in LR14.W can interface with RNC in current and previous releases as per the below compatibility matrix:

RNC RNC LR14.2W RFOA

load (*) RNC LR14.2W GA and

post-GA loads

Peer RNC

RNC LR14.2W GA and post-GA loads

Yes Yes

RNC LR14.2W RFOA load (*) Yes Yes


Yes Yes


Yes Yes

RNC UA08.1.5 No No

RNC UA08.1.3 No No


5. LR14.W UPGRADE BEHAVIOUR

The upgrade should provide the iso behaviour (regarding the functional, the dimensioning and the performance) as far as possible.

To achieve this target and for each RNC, the operator checks the value of a set of parameters thanks to WPS & WICL scripted pre-checks.

If necessary the operator modifies the configuration and can control the sanity of the UTRAN.

6. RNC UPGRADE IMPACT SUMMARY

> Complete Loss Of Service Duration

Start: At the beginning of the first total service affecting action when the alarm Rebooting LP/0 rises.

End: At the end of the outage when the alarm The first C-Bearer (cell) set-up is completed successfully rises associated to OSI State Reporting On Whole Layout global status checks FDDCell availability on RNC object from Fault | RadioAccess WMS operator command verification.

> Service Impact Duration

Start: At the beginning of the first service affecting action. In general, this corresponds to the SW activation command.

End: At the end of the outage when the NE is fully back into service.

> Operating Impact




When a RNC upgrade Vn / Vn+1 is completed, the Vn+1 RNC operates in the prior Vn functional mode, i.e. the new Vn+1 features are not activated (as far as possible) and if this objective cannot be achieved, the exception(s) must be clearly identified (cf. Annex).

RNC targets:

Type of upgrade

RNC Complete Loss Of Service

Duration (typical)

Cell Service Impact Duration

(typical) Comments

inter release RNC upgrade

9 mn outage 9 mn outage use of RNC upgrade procedure (with new MIB)

intra release RNC upgrade

7 mn outage 7 mn outage use of RNC upgrade procedure

RNC patching hitless patching hitless patching use of RNC patching procedure

7. UPGRADE PERFORMANCE TARGET

Total upgrade duration < 8 hours Upgrade outage duration - RNC < 9 mn Upgrade outage duration - iBTS < 3 mn 15 Upgrade outage duration - OneBTS < 5 mn Upgrade outage duration - WMS < 180 mn




8. ABBREVIATIONS AND DEFINITIONS

8.1. ABBREVIATIONS

AP Adjunct Processor running on RNC PSFP (aka PMC), ATM Asynchronous Transfer Mode CN Core Network CNode Control Node CP Control Processor board DPM Downtime Performance Measurement FAP Feature Activation Procedure FP Functional Processor board GUI Graphical User Interface INode Interface Node IP Internet Protocol MBS Multistandard Base Station MIB Managed Information Base MNCL Maintenance Non CM Load aka Maintenance Load MPC Main Processor Card NE Network Element (BTS, RNC) NodeB UMTS name of the BTS NPO Network Performance Optimiser NSP Network Service Platform NTPs Alcatel-Lucent Technical Publications OMC-R Operations and Maintenance Centre - RNC OMU Operation and Maintenance Unit (RNC PSFP PMC) PC Protocol Converter (RNC PSFP PMC) PCR Passport Carrier Release: the Passport software for both PP7480 and PP

(including the Wireless applications for the PP15k). PCS Passport processor Control System PDC Passport Processor Daughter Card (RNC PSFP) PMC PCI mezzanine card (aka AP) PMC_M PMC Master (RNC PSFP) PS-FP Packet Server Functional Processor card (RNC) RNC Radio Resource Control SA Service Active (Passport) SIM Shelf Interface Module SP Service Processor board SRS Software Repository Server TAP Transparent Application Patch (Passport) TMU Traffic Management Unit (RNC PSFP PMC) TS Technical Specification [R5] UE User Equipment (the mobile) UTRAN Universal Terrestrial Radio Access Network WICL Wireless Internet Command Language WPS Wireless Provisioning System (Offline configuration for access network) WMS Wireless Management System




8.2. DEFINITIONS

Term Definition

Downgrade The downgrade can only be done after the full completion of an upgrade. It consists in installing a Vn-x software version instead of a Vn software version. The downgrade process is almost the same as the upgrade process.

Downtime This happens when there is a loss of communication services due to a failure or a reset.

Fallback A fallback consists of stopping the upgrade in progress and restoring the initial state (before the upgrade).

Generic release A generic release is a combination of software, hardware, firmware, and/or documentation, which is issued by the supplier to provide new, improved, or changed functionality.

Maintenance release A maintenance release is a set of corrective patches, which is issued by the supplier to fix a software fault.

Outage duration A outage duration is the duration of a total network element outage.

A total outage occurs when there is a total (100%) loss of capacity for originations and/or terminations for voice and data for > 30 seconds.

(Telcordia Technologies GR-1929 RQMS Wireless)

Patch The code that is replacing the faulty code. A patch is any interim software change, such as object code change, to an in-service release

Patching The process involved from developing a patch, and packaging the patch for delivery to the customer, to applying the patch on the switch.




9. ANNEX A: LR13.W TO LR14.W PATH

9.1. GENERAL

9.1.1 CAPACITY AND FEATURE LICENSING PRE-CHECK

Context: A temporary license is a license file that contains token values that are valid for a defined period of time, and above all for a system release Pre-check rule: Before starting UTRAN upgrade process (i.e. at the pre-check time), it must be checked that an LR14.W permanent license is present. In case a temporary license is still in use, the project manager shall request for use of permanent license. Note: A temporary, infinite license is admitted only in special cases (eg FOA or network extension).

NON-ISO-FUNCTIONAL BEHAVIOUR

N/A

9.1.2 FEATURE LICENSING PRE-CHECK

The feature 159290 Multiple RRH per cell is introduced in LR13.3W; in that release, this feature is not under licensing. In LR14.W, its status is changed, and becomes subject of licensing. Therefore, if the feature is activated in LR13.3W (BTSEquipment.reserved0.bit1 = 1), an action is needed to be done before upgrade to LR14.W:

o de-activate the feature before upgrade (in LR13.3W), if the customer does not

take the feature in LR14.W.

or

o make sure the UTRAN License file contains the activation flag

(multipleRrhPerCellActivation) for this feature, if customer will take the

feature in LR14.W too.


N/A

9.2. LR CABINETS AND CONFIGURATIONS

No features identified

9.3. LR MULTI-STANDARD RF





9.4. SOFTWARE TRANSVERSAL

9.4.1 FEATURE 174070 - PO, CAPACITY IMPROVEMENTS (EXTN OF 170277) PRE-CHECK

None


174070 is an internal feature. Impact is only on iBTS x/eCEM modem (only on PQ3). This feature brings in CPU load optimization and certain % gain will be noticed on CEM PQ3. Details are captured in the LR14.2 iBTS KPI documentation.

9.5. WCDMA 9370 RNC EVOLUTION

9.5.1 FEATURE 172767 - RNC CONNECTION DIMENSIONING FOR MAX VOICE CALLS PRE-CHECK

None


This feature modifies the 9370 RNC internal implementation to remove current dimensioning limits that are restricting the RNC CS call capacity from going beyond 16K calls. Although applicable to both ATM and IP transport configurations, the IP configuration is more relevant due to field populations migrating more toward IP. None of the RNC external interfaces are impacted as a result of this feature.

9.6. WCDMA APPLICATIONS

9.6.1 FEATURE 108103 - ENHANCED CELL_FACH FOR UL AND DL PRE-CHECK

None


Less resources available for dedicated E-DCH users in Cell_DCH, the E-DCH resources have to be shared between CELL_DCH users and eFACH users: Depending on expected user loading, proper dimensioning of parameters such as numberOfCommonEdchResources, maxNumberofCommonEdchResourcePerBoard, HsdschCommonMacFlow/DlCacTransportInfo, CommonEdchMacFlowInfo/UlCacTransportInfo (see 5.2.1 and 5.2.2), edchMaxUsersPerCell (see 9.6) would be required. The NodeB board capacity is limited. The OC resources are shared between dedicated, common E-DCH, and RACH users. Each eCEM board has 4 OCs which in turn has 64




resources each. As a result, depending on the cell configuration (e.g. 3-cell vs 6-cell, expected E-FACH and CELL_DCH loading, etc), the parameter BtsEquipment.maxNumberofCommonEdchResourcePerBoard that controls the maximum number of common E-DCH resources per eCEM board has to be configured properly to ensure adequate trade-off. UA07.1.2 PM34441 and UA08 82602 E-DCH CAC: PM34441 introduced E-DCH CAC for CELL_DCH state in RNC based on two OAM parameters from EdchCellClass: edchMaxUsersPerCell and edchMaxLegs2msPerCell. It is expected that the operator will adapt the CELL_DCH CAC thresholds when common EDCH is configured in the cell. - for example, if the common E-DCH is configured with 10ms TTI: edchMaxUsersPerCell w/ common E-FACH configured = Max(edchMaxUsersPerCell w/o common E-FACH configured numberOfCommonEdchResources, 0) - edchMaxLegs2msPerCell w/ common E-FACH configured = Max(edchMaxLegs2msPerCell w/o common E-FACH configured 2msTtiCostFactor * numberOfCommonEdchResources, 0) Assuming that from UA08.1 CELL_DCH CAC for 2ms TTI is moved from RNC to NodeB via PM82602 hence edchMaxLegs2msPerCell will be set to 128.

9.6.2 FEATURE 121555 - LR14.2 RNC COUNTER EVOLUTIONS PRE-CHECK

None


This feature should not impact any pre-existing features / functionality / call processing. Following the introduction of this feature new performance counters will be available to the customer to further aid network performance analysis. Not all new counters are activated by default after upgrade in LR14W. This activation is done as needed, being used a specific procedure during inter-release upgrade, involving a recommended counter list provided by NEA.

9.6.3 FEATURE 164968 - SUPPORT OF GLONASS ASSISTANCE DATA OVER IUPC (SAS CENTRIC MODE) PRE-CHECK

None


164968 introduces the following non-ISO behaviours over the software upgrade: Non-ISO#1: Permanent activation of the Reference Time forwarding feature

116687. In other words, RRC IEs UE Positioning GPS Reference Time and UE Positioning GANSS reference time will be sent in the 1st RRC segmentation message, irrespective of the value of configuration parameter AgpsUebasedLocationTechnology/referenceTimeFirstPosition.

o Note: TIS are in the process of FFAing Reference Time forwarding in LR13.3 in AT&T. If successful, provided it is activated network wide in LR13.3, this non-ISO will be moot in the AT&T network.




Non-ISO#2: Movement of RRC IEs UE Positioning GPS Reference Location and UE Positioning GANSS Reference Location from the 2nd RRC segmentation message to the 1st RRC segmentation message.

Non-ISO#2: The conveyance of the following new post-Rel7 IEs to post-Rel7 UEs, irrespective of the activation status of 164598. Introduction of support for these IEs will only introduce a non-ISO condition if the SAS chooses to send them to the 9370 in the PCAP PAR, in which case the 9370 will send them to all post-Rel7 UEs:

o Applicable to both GPS and GANSS: IMSI IMEI Complete Almanac Provided UDRE Growth Rate Time of Validity for UDRE Growth Rate

o Only applicable to GPS: GPS Week Cycle Number

9.6.4 FEATURE 168642 - IBTS RESOURCE TRACKING USING PM COUNTERS PRE-CHECK

None


Following the introduction of this feature new performance counters will be visible in the iBTS PM model to aid iBTS performance analysis / debugging.

9.6.5 FEATURE 168705 - NOISE FLOOR SELF-LEARNING ALGORITHM FOR ONEBTS PRE-CHECK

None


This feature has an activation flag which is defaulted to FALSE. This feature should enhance the pre-existing features / functionality / call processing. A better determination of the noise floor is expected to improve the Connection Admission Control as well as Load Control criteria. Following the introduction of this feature new performance counters will be available to the customer to further aid network performance analysis. This feature has 2 PM counters added which will be reported if the feature is active or one of them will be reported even if the feature is not activated, but a reference RTWP is provided by RNC. For cells where the feature is not activated, the operator has the possibility to provide manually a specific RTWPref value. If the feature is neither activated nor a reference RTWP value available, the counter value will be empty.




9.6.6 FEATURE 168853 - LR14W 3GPP STANDARDS COMPLIANCE PRE-CHECK

None


This feature takes into account many 3GPP Specification corrections and has respective activation flags which are defaulted to FALSE. There are PM counters created for respective 3GPP CR monitoring. This feature should enhance the pre-existing features / functionality / call processing as this corresponds to 3GPP specification correction. Following the introduction of this feature new performance counters will be available to the customer to further aid network performance analysis. Counters will be activated by default, but those for the RNC can be controlled / de-activated if required.

9.7. WCDMA NODEB EVOLUTION

9.7.1 FEATURE 169488 - AISG2.0 ON 9396-BASED RRHS PHASE 1A PRE-CHECK

None


Alarm Clear: Alarm Clear Action for the operator to use at WMS. S/W Download: Download with ALD Device. This functionality includes Download Start, Download Application function, and Download End. These are AISG procedures described in the AISG standards. Cell Degraded: Cell Degraded from RET Faults and RET accessibility (e.g. if it was disconnected). Asynchronous operation: All procedures are now supported as asynchronously allowing for queuing. Calibration Progress Status: Replacement of Calibration Status by Calibration Progress Status indicator. ACF File download: ALD Configuration File download management is supported by the WMS.

9.7.2 FEATURE 177111 - DIGITAL DAS USING TYCO CDIU WITH WCDMA 9396 DIGITAL PHASE 2 PRE-CHECK

None





The following data migration is implemented for dDAS: In LR13.3 the OneBTS RAN model (aka MIM) was not modified for dDAS. The CDIU is modelled as an MO of class RFHead. For the two attributes RFHead:detectedRFHeadHardwareModel and RFHead:expectedRFHeadHardwareModel the spare enum values used are rRH10_08 for dDAS 850 MHz and rRH10_19 for dDAS 1900 MHz. These two enum values were originally foreseen for 10W RRHs but have never been developed. In LR14.2 new enum values dDAS1x_850, dDAS1x_1900, dDAS2x_850 and dDAS2x_1900 have been introduced. The 1x variants are for single Rx, the 2x variants for Rx diversity configurations. As part of the upgrade rRH10_08 is migrated to dDAS1x_850 and rRH10_19 is migrated to dDAS1x_1900. After upgrade the behavior of the CDIU is otherwise the same as before.

9.8. WCDMA RF


END OF DOCUMENT

Title PagePublication HistoryContents1. INTRODUCTION1.1. OBJECT1.2. SCOPE OF THIS DOCUMENT1.3. FRS1.4. AUDIENCE FOR THIS DOCUMENT

2. RELATED DOCUMENTS2.1. APPLICABLE DOCUMENTS2.2. REFERENCE DOCUMENTS

3. BENEFITS3.1. CUSTOMER/SERVICE PROVIDER BENEFITS3.2. END USER/SUBSCRIBER BENEFITS

4. FUNCTIONAL OVERVIEW4.1. PRINCIPLE4.2. LR14.2W UPGRADE PATHS4.2.1 OAM LR14.2W4.2.2 NPO6.2 LR14.2W4.2.3 RNC SW UPGRADE PATHS4.2.4 BTS SW UPGRADE PATHS4.2.5 RNC LR14.W AND IBTS4.2.6 RNC LR14.W AND ONEBTS4.2.7 WCE LR14.W4.2.8 RNS LR14.W

5. LR14.W UPGRADE BEHAVIOUR6. RNC UPGRADE IMPACT SUMMARY7. UPGRADE PERFORMANCE TARGET8. ABBREVIATIONS AND DEFINITIONS8.1. ABBREVIATIONS8.2. DEFINITIONS

9. ANNEX A: LR13.W TO LR14.W PATH9.1. GENERAL9.1.1 CAPACITY AND FEATURE LICENSING9.1.2 FEATURE LICENSING

9.2. LR CABINETS AND CONFIGURATIONS9.3. LR MULTI-STANDARD RF9.4. SOFTWARE TRANSVERSAL9.4.1 FEATURE 174070 - PO, CAPACITY IMPROVEMENTS (EXTN OF 170277)

9.5. WCDMA 9370 RNC EVOLUTION9.5.1 FEATURE 172767 - RNC CONNECTION DIMENSIONING FOR MAX VOICE CALLS

9.6. WCDMA APPLICATIONS9.6.1 FEATURE 108103 - ENHANCED CELL_FACH FOR UL AND DL9.6.2 FEATURE 121555 - LR14.2 RNC COUNTER EVOLUTIONS9.6.3 FEATURE 164968 - SUPPORT OF GLONASS ASSISTANCE DATA OVER IUPC (SAS CENTRIC MODE)9.6.4 FEATURE 168642 - IBTS RESOURCE TRACKING USING PM COUNTERS9.6.5 FEATURE 168705 - NOISE FLOOR SELF-LEARNING ALGORITHM FOR ONEBTS9.6.6 FEATURE 168853 - LR14W 3GPP STANDARDS COMPLIANCE

9.7. WCDMA NODEB EVOLUTION9.7.1 FEATURE 169488 - AISG2.0 ON 9396-BASED RRHS PHASE 1A9.7.2 FEATURE 177111 - DIGITAL DAS USING TYCO CDIU WITH WCDMA 9396 DIGITAL PHASE 2

9.8. WCDMA RF

Umtsysdd043248lr14w v1 Lr14.w Upgrade Paths

Documents

Transcript of Umtsysdd043248lr14w v1 Lr14.w Upgrade Paths