06 02 RN33156EN10GLA0 Software Management

8/18/2019 06 02 RN33156EN10GLA0 Software Management

1/27

WCDMA RAN Software

Management

DN70225962Issue 2-1 en30/01/2009

# Nokia Siemens Networks 1 (27)

Nokia Siemens Networks WCDMA RAN, Rel.

RU10, System Library, v. 1


2/27

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 Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

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 Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS 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 OR THEINFORMATION IN IT.

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

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

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

Copyright © Nokia Siemens Networks 2009. All rights reserved.

2 (27) # Nokia Siemens Networks DN70225962Issue 2-1 en

30/01/2009

WCDMA RAN Software Management


3/27

Contents

Contents 3

List of figures 4

Summary of changes 5

1 Description of software management 71.1 NetAct software management solution 71.2 BTS and AXC software management 81.3 RNC software management 91.4 OMS software management 10

2 Architecture of software management 112.1 Architectural roles 12

3 Software download to network 13

4 Software activation (upgrade) 1 54.1 RNC upgrade 16

5 Software information upload 1 7

6 Software information notifications 19

7 Optional functionality 21

8 Features per release 23

9 Management data for software management 259.1 Alarms 259.2 Counters 259.3 Parameters 25

10 Limitations and restrictions 27

DN70225962Issue 2-1 en30/01/2009


Contents


4/27

List of figures

Figure 1. Architecture of software management 11


30/01/2009



5/27

Summary of changes

Changes between document issues are cumulative. Therefore, the latest

document issue contains all changes made to previous issues.

Changes between issues 2-0 and 2-1

. A new subsection has been added to Description of software

management .

. Information has been updated in Features per release and

Limitations and restrictions.

. Editorial corrections have been made.


Editorial corrections have been made.


Editorial changes have been made.

DN70225962Issue 2-1 en30/01/2009


Summary of changes


6/27


30/01/2009



7/27

1 Description of software managementSoftware management includes the actions needed to guarantee that the

right version of the software is running in the network elements. It involvesdownloading software files, activation of software builds, and software

build status management. A software build contains the files related to a

release of network elements. Software management also includes

installation and activation of change deliveries. Change deliveries (CD) are

small load modules of network software which include a new feature or a

correction of a detected fault. In the CD installation one or more software

files are added to the network element software build locally or remotely.

The main software management functions are software download and

software activation. In download, the new software is transferred from

NetAct to the network element, so that the operation does not affect the

service level of the network. In software activation, the new software istaken into use. Software activation is usually done at night, because

activation requires restarting the network element and causes outage for

network element services. Software build status management involves

browsing and comparing the software and the archiving of software builds

and change deliveries.

1.1 NetAct software management solution

NetAct software management solution is called Software Manager.Software Manager is part of the NetAct Administrator functionality. With the

Software Manager application, NetAct system administrators can archive,

browse, and download the configurations of network elements. The

Software Manager user interface consists of three views:

. The Network Software Status view is used for:

. viewing the software configuration in a network,

. searching and comparing network elements on the basis of the

software configuration,

DN70225962Issue 2-1 en30/01/2009


Description of software management


8/27

. uploading and downloading software configurations to and

from network elements,. activating certain network elements.

. The Software Archive view is used for:

. importing software to the archive,

. browsing and viewing archived software,

. renaming and removing archived software.

. The Tasks view is used for monitoring the status of software

management tasks.

It is also possible to take remote RNC software backups from NetAct. For

more information, see RAN1627: Remote Backup Support for RNC in

WCDMA RAN, Rel. RU10, Feature Descriptions .

For more information, see Managing Network Element Software in NetAct

product documentation.

1.2 BTS and AXC software management

Base Transceiver Station (BTS) or ATM Cross-connection (AXC) software

can be managed remotely from the NetAct Software Manager through thenetwork management interface or locally from the BTS and AXC site with

BTS and AXC element manager applications. The Radio Network

Controller (RNC) mediates BTS software management messages

between NetAct and the BTS. The RNC sends BTS software management

messages to the BTS through the BTS management interface.

The BTS and the AXC have two software builds stored: active and passive

software builds. When a new software is downloaded, it is stored as

passive software build. During the activation, the status of the passive

software build is changed to active.

In the FlexiBTS the software management functions are combined for

Flexi WCDMA BTS and its transport module (FTM). The transport module

software is included in the BTS software package, so that the transport

module is upgraded in the Flexi WCDMA BTS software upgrade as

integral part of the BTS.

BTS software management operations can be executed as a mass

operation. Mass operation means that NetAct manages software for

several BTSs at a time with one single software management command to

the RNC. NetAct sends a management command for each involved RNC

and gives the RNC an RNC specific list of the BTSs which have been


30/01/2009



9/27

selected by the user. RNC starts processing the given BTS list and sends

required messaging to each BTS through the BTS management interface.When the BTS has finished the operation, it gives feedback to the RNC

and the RNC sends BTS-specific feedback to NetAct.

For more information on AXC and BTS software management, see

WCDMA RAN Network Element Management .

1.3 RNC software management

In RNC software upgrade operations, RNC software is downloaded to

units using RNC redundant hardware structure. There are five different

software builds in RNC: backup, new, untitled, fallback, and undefined

builds.

There are five different software builds in RNC:

. Backup (BU) is a disk copy of running SW build in the memory.

. Fallback (FB) is a SW build that is a fallback copy of the backup

build, and it can be used as a safe copy build if the backup build is

corrupted.

. New (NW) is a new SW build on the disk, which has been brought

into the network element first to be tested and then to be deployed.

. Undefined (UD) is an uncreated SW, which is stored on the disk

without a name.

. Untitled (UT) is a SW build, which status has not been defined.

Backup build is normally defined as the active and running SW build. The

backup build is usually also the default build, which means that when the

network element starts up, the initial system loads the backup build from

the disk.

In principle, the fallback build is the same as the backup build except that

its data starts from the moment of copying, which means that data updated

in the backup build after the copying of the fallback build are missing.

There can be only one backup, fallback, and new build stored on the disk

at a time, but the network element can contain several SW builds that have

undefined or untitled status. Undefined and untitled builds are stored in

separate directories, so the builds can only be referred to on the basis of

the directory. When a new uncreated SW build is copied on the hard disk,

the system automatically sets it to undefined status. SW builds that have

DN70225962Issue 2-1 en30/01/2009


Description of software management


10/27

undefined status are only visible in the output commands. SW builds with

untitled status are usually old builds, and they can be deleted, but thechange delivery often introduces the update as an untitled build in the

same directory as the backup build.

Change delivery (CD) installation is needed when the user wants to add

some new features or some fault corrections to the network. It is possible

to install RNC CDs remotely with a remote RNC EM session. CD Remote

Manager Tool is a RNC GUI which enables installation of change

deliveries and management of software configuration of network elements

(network elements). CD remote management is based on a CD-specific

parameter file which is managed by a macro execution tool. This file

includes all the execution commands which were previously done

manually.

RNC software management does not include the OMS's own software

management functions.

The RNC software management functionality is described in the first

chapter of Software Configuration Management .

1.4 OMS software management

OMS software management includes management of the OMS softwareand the functionality used for mediating BTS software management

actions from NetAct to BTS.

OMS software cannot be managed from NetAct. Instead, it is managed

with a local command-line interface.

OMS software management is described in the first chapter of

Administering RNC OMS .


30/01/2009



11/27

2 Architecture of software managementThe following figure illustrates the architecture of the software

management functionality in WCDMA RAN Network.

Figure 1. Architecture of software management

Network Management Interface

NetAct

RNC

BTS AXC

BTS Management Interface

Administrator

Software Manager UI

UI SW manager O&M

mediator

SW manager SW manager

UI UI

DN70225962Issue 2-1 en30/01/2009


Architecture of software management


12/27

2.1 Architectural roles

User

The user triggers the software management operations. The user can also

schedule the operations with NetAct Software Manager.

NetAct

NetAct Software Manager controls software download, activation and

upload functions. The Software Manager also provides data storage for

the software builds and allows the viewing of the software configuration in

the different network elements.

RNC

The RNC is the target element for the RNC software upgrade and upload

operations. It also provides a local data storage for the RNC software.

The RNC provides a temporary data storage for network element SW files

during provisioning. The RNC mediates SW management actions between

NWI3 and BTS O&M management interfaces.

BTS

The BTS is the target element for the BTS software package download,

activation, and upload operations. It also provides a local data storage for

the BTS software.

AXC

The AXC is the target element for the AXC software package download,

activation and upload operations. It also provides a local data storage for

the AXC software.


30/01/2009



13/27

3 Software download to networkIn software download operations the new software is transferred to the

network element. AXC and BTS software download can be started either from NetAct Software Manager manually by selecting the particular

network element, or the download can be scheduled in the NetAct. AXC

and BTS software download can also be started from the AXC and BTS

local element manager tool. The RNC software is downloaded to the RNC

from the RNC local management tool.

The AXC software is downloaded to one AXC at a time through the

network management interface. BTS softwares can be downloaded as a

mass operation, so that NetAct sends one download command for each

involved RNC with a list of BTSs to be downloaded through the network

management interface. The software is first downloaded to the RNC. The

RNC sends download command to each BTS in the list through the BTSmanagement interface, and every BTS downloads the software package

from the RNC to itself. The BTS then gives feedback of the operation

status to the RNC, and the RNC sends BTS-specific feedback to NetAct.

Software download to network

Actors: NetAct Software Manager user or a scheduled

download plan

Tools: NetAct Software Manager application, NetAct UI

Frequency: Twice a year when a new version of network elementsoftware package is available.

1. Start NetAct Software Manager and select/accept the software build.

2. NetAct checks and validates the correctness of the software build,

inspects the software build suitability, and makes proposal of target

network elements.

3. Select/accept the network element(s) where the software build is

downloaded and start downloading the software build.

DN70225962Issue 2-1 en30/01/2009


Software download to network


14/27

4. The network element downloads the software files from a fileserver

and notifies NetAct when it succeeds.5. NetAct reports the result of the operation.

The network element software package is downloaded to the network

element. Software Registry in NetAct is updated.


30/01/2009



15/27

4 Software activation (upgrade)In software activation the new software is taken into use. The activation of

the software is usually done at night, because activation requires restartingthe network element, and it causes outage of network element services.

The AXC and BTS software activation can be started either from NetAct

Software Manager manually by selecting the particular network element,

or the activation can be scheduled in the NetAct. The AXC and BTS

software can also be activated from the AXC and BTS local element

manager tool.

The RNC upgrade is executed with RNC local management tool.

The AXC software activation is done for one AXC at a time through the

network management interface. The BTS software can be activated in amass operation, so that NetAct sends a list of the BTSs and the software

version to be activated to the RNC through the network management

interface, and the RNC delivers the activation commands to each BTS

through the BTS management interface.

Software activation

Actors: NetAct Software Manager user or a scheduled

activation plan


Frequency: Twice a year when a new version of network element

software build is available.

1. Start NetAct Software Manager and select all network elements you

want to activate with the new software build.

2. NetAct sends the software activation request to the selected network

elements.

DN70225962Issue 2-1 en30/01/2009


Software activation (upgrade)


16/27

3. The network element sends software activation reply to NetAct to

indicate that the software activation request is received andunderstood, and activates the new software build (by restarting the

complete software or the needed parts only).

4. NetAct reports the result of the operation.

5. NetAct updates its own software registry.

The new software build is in active state in the network element. The

software registry in NetAct is updated.

4.1 RNC upgrade

Actor: Configuration Management Engineer

Tool: RNC local management tool

Frequency: Twice a year when a new version of RNC software

build is available.

1. Open the file transfer session to file server using the given address

and download the files from a file server.

2. Configure the software in the RNC for activation phase (by executingconversions, installing change deliveries, and copying the converted

files to the new packet).

3. Check that the upgrade operation is successfully completed: the

RNC and the radio network are up and running, traffic is OK, and no

destructive alarm is active.

4. Finish the upgrade to the new software build.

5. Change the new software build status to backup (BU).

6. The RNC software management application sends a notification to

NetAct.

The RNC is up and running with the new software build.


30/01/2009



17/27

5 Software information uploadSoftware information upload is executed when the NetAct user wants to

see the contents of the software files in a certain network element.

The RNC, AXC, and BTS software information can be uploaded to NetAct

either manually by selecting the particular network element, or the upload

can be scheduled in the NetAct. Network element software information can

also be uploaded to some local storage from the local element manager

tool.

The AXC software upload is done for one AXC at a time through the

network management interface. The BTS software can be uploaded in a

mass operation, so that NetAct sends a list of the BTSs and the software

file version to be uploaded to the RNC through the network management

interface, and the RNC delivers the upload commands to each BTSthrough the BTS management interface.

Software information upload

Actor: NetAct Software Manager user or a scheduled

upload plan


Frequency: Seldom

1. Select a network element from NetAct Software Manager.2. NetAct requests software file versions from the network element.

3. The network element creates an XML file and sends location

information of the file to NetAct.

4. NetAct uploads the XML file to NetAct and stores the file.

5. NetAct reports the result of the operation.

Software information is available in NetAct database. You can examine the

software configuration with NetAct Software Manager.

DN70225962Issue 2-1 en30/01/2009


Software information upload


18/27


30/01/2009



19/27

6 Software information notificationsNetwork elements can send software information notifications to NetAct

when local changes have been made to the network element softwareconfiguration.

The RNC can be configured to send software information notification to

NetAct of the following situations:

. New software build is created and set in the new (NW) status.

. New software build is taken into use.

. New change delivery (CD) is installed.

. The new software build is changed to active.

. Software build identifier is updated.

. The fallback build (FB) is changed to default.

. Software statuses of already created builds have been rolled back

(status of the FB build is changed to BU, status of the build which

functioned as BU is changed to NW, and if there is a build with NW

status, it is changed to UT status).

. Local fallback copy of the software build is taken.

The BTS and the AXC send software change notification to NetAct when

the software file configuration has been changed locally by using the BTS/

AXC element manager.

Software information notifications

Actor: User

Tool: Local element management application

Frequency: Seldom

DN70225962Issue 2-1 en30/01/2009


Software information notifications


20/27

1. Modify the software configuration of a network element locally.

2. Network element sends a notification to NetAct about the changes inthe software configuration.

NetAct has been notified about the local software configuration change.


30/01/2009



21/27

7 Optional functionalitySoftware Manager is the application software (ASW) in NetAct.

DN70225962Issue 2-1 en30/01/2009


Optional functionality


22/27


30/01/2009



23/27

8 Features per releaseThe following table lists the features related to this functional area. The

features are arranged according to the release in which they wereintroduced. Note that a feature may belong to more than one functional

area.

Table 1. Features related to software management

RAN1.5 and RAN04

RAN1.045: SW Management

RAS05

None

RAS05.1

RAN817: Combined SW Management for Flexi WCDMA BTS and its Transport Module

RAN1091: BTS SW Management with RNC / NEMU Mediation

RAS05.1 ED

None

RAS06

None

RU10

RAN1627: Remote Backup Support for RNC

DN70225962Issue 2-1 en30/01/2009


Features per release


24/27


30/01/2009



25/27

9 Management data for softwaremanagement

9.1 Alarms

Table 2. RAN817: Combined SW Management for Flexi WCDMA BTS and its

Transport Module

Alarm number Alarm name

7650 Base Station Faulty

7651 Base Station operation degraded

7652 Base Station Notification

9.2 Counters

There are no counters related to this functionality.

9.3 Parameters

There are no parameters related to this functionality

DN70225962Issue 2-1 en30/01/2009


Management data for software management


26/27


30/01/2009



27/27

10 Limitations and restrictionsThis functionality has the following limitations and restrictions in WCDMA

RAN.

Table 3. Limitations

Feature Max number of

Nwi3 sessions

Multi request/same

operation to

several BTSs (max

number)

RAN1.045: SW Management 5

RAN1091: BTS SW Management with

RNC/NEMU Mediation

5 100

Table 4. Restrictions

Feature Limitation

RAN1.045: SW Management BTS supports only one SW operation at a time.

So if an upload is ongoing and a download

request comes to the BTS, the BTS sends a

message with nack reason “busy”.

RAN1091: BTS SW Management with

RNC/NEMU Mediation

Only one download request can be ongoing at

a time, because OMS keeps only one BTS SW

package on its own disc.

Limitations and restrictions

06 02 RN33156EN10GLA0 Software Management

Documents

Transcript of 06 02 RN33156EN10GLA0 Software Management