0291_6 BTS SW Management Database Description

8/13/2019 0291_6 BTS SW Management Database Description

http://slidepdf.com/reader/full/02916-bts-sw-management-database-description 1/13

Document number/Issue Copyright © Nokia Telecommunications Oy

NTC TAN 0291/6 en

1

NOKIA NMS/2000FOR MANAGING CELLULAR NETWORKS

DATABASE DESCRIPTION FOR BTS SOFTWARECONFIGURATION MANAGEMENT

Reference Guide




NTC TAN 0291/6 en2

The information in this document is subject to change without notice and describes only the product defined

in the introduction of this documentation. This document is intended for the use of Nokia

Telecommunications' customers only for the purposes of the agreement under which the document is

submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written

permission of Nokia Telecommunications. The document has been prepared to be used by professional and

properly trained personnel, and the customer assumes full responsibility when using it. NokiaTelecommunications welcomes customer comments as part of the process of continuous development and

improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of

the mentioned hardware or software products cannot be considered binding but shall be defined in the

agreement made between Nokia Telecommunications and the customer. However, Nokia

Telecommunications has made all reasonable efforts to ensure that the instructions contained in the

document are adequate and free of material errors and omissions. Nokia Telecommunications will, if

necessary, explain issues which may not be covered by the document.

Nokia Telecommunications' liability for any errors in the document is limited to the documentary correction of

errors. Nokia Telecommunications WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS

DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY

LOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according to the

applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respective companies, and

they are mentioned for identification purposes only.

Copyright © Nokia Telecommunications Oy 1997. All rights reserved.

No. of Edited by Author Approved by Previous issuepages (5) approved

J Haro R Ropponen J Hartikainen

13/JuHa 29 Sep 1997 29 Sep 1997 29 Sep 1997 6 Sep 1996




NTC TAN 0291/6 en3

TABLE OF CONTENTS

1 WHAT IS NEW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.1 Changes from T9 to T10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 ABOUT THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1 Where to Find More. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 DATABASE ARCHITECTURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4 DATABASE TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.1 K_SW_PACKAGE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.2 K_SW_MODULE Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4.3 K_SW_NETWORK_ELEMENT Table . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4.4 K_SWBCF_DOWNLOAD Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.5 K_SWBCF_OPERATION Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.6 K_SWBCF_NE_OPERATION Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.7 K_SW_CHANGES Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.8 K_SW_NE_ID_TMP Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.9 K_SW_PACK_ID_TMP Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.10 S_PACKAGE_ID Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.11 S_DOWNLOAD_ID Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-



What is New


NTC TAN 0291/6 en4

1 WHAT IS NEW

1.1 Changes from T9 to T10

Some changes have been made to K_SWBCF_DOWNLOAD and

K_SWBCF_OPERATION tables.



About This Manual


NTC TAN 0291/6 en5

2 ABOUT THIS MANUAL

This document explains the contents of the BTS Software Configuration

Management database. This document relates to Nokia NMS release T10.

The following chapters explain the architecture of each of the databases and

present the tables contained in the databases.

2.1 Where to Find More

If you are unfamiliar with any of the concepts or abbreviations in this document,

please refer to the Glossary, TAN 0717 en.

For details on other Nokia NMS manuals, see the NMS/2000 Description of

Documentation, TAN 0442 en.

The other parts of the NMS database are described in the following documents:

• Database Description for BTS Hardware Configuration Management,

TAN 0292 en

• Database Description for Radio Network Management, TAN 0295 en

• Database Description for Fault Management, TAN 0290 en

• Database Description for Test and Diagnostics Management, TAN 0805

en

• Database Description for BSC Measurements, TAN 0422 en

• Database Description for Managed Objects, TAN 0294 en

• Database Description for MSC/HLR Measurements, TAN 0423 en

• Database Description for System Management, TAN 1213 en



Database Architecture


NTC TAN 0291/6 en6

3 DATABASE ARCHITECTURE

The BTS software management database consists of the following tables and

sequences:

• Software package table K_SW_PACKAGE

• Software module table K_SW_MODULE

• Network element table K_SW_NETWORK_ELEMENT

• Download table K_SWBCF_DOWNLOAD

• Operation table K_SWBCF_OPERATION

• Network element operation table K_SWBCF_NE_OPERATION

• Changes table K_SW_CHANGES

• Network element id table K_SW_NE_ID_TMP

• Package ID table K_SW_PACK_ID_TMP

• Package ID sequence S_PACKAGE_ID

• Download ID sequence S_DOWNLOAD_ID

The software package table contains software packages.

The software module table contains the modules of the software packages.

The network element table contains information about the BCFs and the

software packages in these network elements.

The download table contains information about the existing download

operations.

The operation table contains information about the existing operations (such as

ACTIVATION, ROLL, SWAP, DELETE, REFRESH).

The network element operation table contains the information about the existing

downloads and other Software Management operations (ACTIVATION, ROLL,

SWAP, DELETE, REFRESH) in the managed network elements.

The changes table contains the internal IDs of the network elements whose data

could be inconsistent with NMS data and should therefore be checked.

The network element ID table contains internal IDs of the network elements.

This table is used temporarily when complicated SELECT clauses are

performed. This table does not include stable data.



Database Architecture


NTC TAN 0291/6 en7

The package ID table contains package IDs. This table is used temporarily when

complicated SELECT clauses are performed. This table does not include stable

data.

The package ID sequence is used to generate the unique package IDs.

The download ID sequence is used to generate the unique download and BCF_OP

IDs.

Figure 1. Structure of BTS Software Management Database

K_SW_PACKAGEtable

PACK_ID

K_SW_MODULEtable

PACK_ID

K_SWBCF_

DOWNLOADtable

DOWNLOAD_IDPACK_ID

K_SWBCF_NE_ OPERATION

table

OP_ID

NE_ID

K_SW_NETWORK_ ELEMENTtable

K_SWBCF_

OPERATIONtable

BCF_OP_ID

K_SW_CHANGEStable

NE_IDNE_ID

STATUSPACK_ID



Database Tables


NTC TAN 0291/6 en8

4 DATABASE TABLES

4.1 K_SW_PACKAGE Table

K_SW_PACKAGE table includes one row for each software package. The

description and possible values, size, and type of each column is defined in the

table.

The K_SW_PACKAGE table contains information about the software packages in

NMS database. The information about the modules of these packages is included

in K_SW_MODULE table (see 4.2).

4.2 K_SW_MODULE Table

The following table presents one row of the module table K_SW_MODULE. The

description and possible values, size, and type of each column is defined in thetable.

Column Description and Possible Values Type

TIME_STAMP This column contains information aboutthe time and date when this row was lastupdated.

Date, not null

PACK_ID Each package has a unique identificationnumber (see 4.10).

Number, not null,primary key

PACK_NAME Name of the package (max. 16 chars). Char 16, not null

PACK_VERSION Version number of the package; valuesbetween 0-999 and column not used = -1.

Number 3, not null

PACK_SUBVERSION Subversion number of the package; valuesbetween 0-999 and column not used = -1.

Number 3, not null

PACK_RELEASE Release number of the package; valuesbetween 0-999 and column not used = -1.

Number 3, not null

PACK_NE_TYPE Network element type; BCF = 1. Number 1, not null

PACK_NE_SUBTYPE Information of the sub-type;

GSM-B = 1, DCS-B = 2, GSM-D = 3,

DCS-D = 4, GSM-F = 5, DCS-F = 6, 1900-B = 7, 1900-D = 8, 1900-F = 9.

Number 2, not null

CREATION_TIME Time and date of the creation of thepackage

Date

MASTER_FILE_

NAME

Name of the master file (max. 16characters).

Char 16

MASTER_FILE_

VERSION

Version number of the master file; valuesbetween 0-999.

Number 3, not null

MASTER_FILE_

SUBVERSION

Subversion number of the master file;values between 0-999.

Number 3, not null

MASTER_FILE_

RELEASE

Release number of the master file; valuesbetween 0-999.

Number 3, not null



Database Tables


NTC TAN 0291/6 en9

The K_SW_MODULE table contains the modules of the software packages. Each

module has a PACK_ID which is the key of the package in the K_SW_PACKAGE

table.

4.3 K_SW_NETWORK_ELEMENT Table

The following table presents one row of the network element table

K_SW_NETWORK_ELEMENT. The description and possible values, size, and type

of each column is defined in the table.

The K_SW_NETWORK_ELEMENT table contains information about the software

packages and the running package of certain network element. There are three

rows in the K_SW_NETWORK_ELEMENT table or each network element, one for

each status: NEW , BACK-UP and FALL-BACK . Only one package at a time can

be RUNNING in the network element.



Date, not null

PACK_ID Each module has a unique packageidentification number inK_SW_PACKAGE table (see 4.10).


FILE_NAME Name of the module file;

(max 16 characters).

Char 16, not null,primary key

FILE_VERSION Version of the module file;

(max 11 characters).

Char 11, not null,primary key


TIME_STAMP This column contains information about

the time and date when this row was lastupdated.

Date, not null

NE_ID Each network element has a uniqueidentification number which exists in theOBJECTS table (Int_Id).


STATUS Status of the software package:

NEW = 0, BACK-UP = 1, FALL-BACK = 2.

Number 1, not null,primary key

PACK_ID Each status can have a packageidentification number in theK_SW_PACKAGE table;

column not used = -1 (see 4.10).

Number, not null

RUNNING Running info: indicates whether thispackage has RUNNING status in thenetwork element (not running = 0,running = 1).

Number, not null



Database Tables


NTC TAN 0291/6 en10

4.4 K_SWBCF_DOWNLOAD Table

The following table presents one row of the download table

K_SWBCF_DOWNLOAD. The description and possible values, size, and type of

each column is defined in the table.

The target network elements regarding this download are handled in

K_SWBCF_NE_OPERATION table (see 4.5). One row is inserted for each network

element into the K_SWBCF_NE_OPERATION table and the OP_ID is the same as

the DOWNLOAD_ID.

If activation is part of the download operation (ACTIVATE = 1), one row is

inserted into K_SWBCF_OPERATION table for handling the activation (see 4.6)

and BCF_OP_ID is the same as DOWNLOAD_ID.

4.5 K_SWBCF_OPERATION Table

The following table presents one row of the operation table

K_SWBCF_OPERATION. The description and possible values, size, and type of




Date, not null

DOWNLOAD_ID Each download has a unique identificationnumber (see 4.11).


PACK_ID Each download has a packageidentification number in theK_SW_PACKAGE table (see 4.10).

Number, not null

DL_START_COUNT The start count of the download operation;values between 1 - 99.

Number 2, not null

DL_USER_ID Not in use. Char 80, not null

DL_START_TIME The starting time of the downloadoperation; time and date.

Date, not null

DL_STATE The state of the download operation;

WAITING = 1, RUNNING = 2, STOPPED= 3, ERROR =4, COMPLETED = 5.

Number 1, not null

ACTIVATE Information column: indicates whether thedownloaded package is activated right

after the download or not; (no activation =0, activation = 1).

Number 1, not null



Date, not null

BCF_OP_ID Each operation has a unique identificationnumber (see 4.11).




Database Tables


NTC TAN 0291/6 en11

The target network elements regarding this operation are handled in theK_SWBCF_NE_OPERATION table (see 4.6). One row is inserted for each network

element into the K_SWBCF_NE_OPERATION table and the OP_ID is the same as

the BCF_OP_ID.

4.6 K_SWBCF_NE_OPERATION Table

The following table presents one row of the network element operation table

K_SWBCF_NE_OPERATION. The description and possible values, size, and type

of each column is defined in the table.

OP_TYPE The type of the operation;

ACTIVATE = 1, ROLL = 3,

SWAP = 2, DELETE = 4,REFRESH = 5.

Number 1, not null

OP_START_COUNT The start count of the operation; valuesbetween 1 - 99.

Number 2, not null

OP_USER_ID Not in use. Char 80, not null

OP_START_TIME The starting time of the operation; time anddate.

Date, not null

OP_STATE The state of the operation;

WAITING = 1, RUNNING = 2,STOPPED = 3, ERROR =4,COMPLETED = 5.

Number 1, not null

ACTIVATION_HO Not in use. Number 1, not null

PACK_ID_NEW Package ID in NEW status in the network elements; not in use in this operation = -1(see 4.10).

Number, not null

PACK_ID_BACKUP Package ID in BACKUP status in thenetwork elements; not in use in thisoperation = -1 (see 4.10).

Number, not null

PACK_ID_FALLBACK

Package ID in FALLBACK status in thenetwork elements; not in use in thisoperation = -1 (see 4.10).

Number, not null


TIME_STAMP This column contains information about thetime and date when this row was lastupdated.

Date, not null

OP_ID Each network element operation has aunique identification number which is eitherthe same as the DOWNLOAD_ID in theK_SWBCF_DOWNLOAD table or theBCF_OP_ID in the K_SWBCF_OPERATION table; (see 4.11).


NE_ID Each row has a network element

identification number which is the same asone of the NE_IDs in K_SW_NETWORK_ELEMENT table.

Number, not null,

primary key




Database Tables


NTC TAN 0291/6 en12

The K_SWBCF_NE_OPERATION table includes information about those network

elements which are part of certain download or other software management

operations (ACTIVATE, ROLL, SWAP, DELETE, REFRESH).

If the network element is part of a download, only the DL_START_COUNT and

DL_STATE columns are used.

4.7 K_SW_CHANGES Table

The following table presents one row of the changes table K_SW_CHANGES. The

description and possible values, size, and type of each column is defined in the

table.

The K_SW_CHANGES table includes information about the network elementswhose data may be inconsistent with the data in the NMS database, or where an

DL_START_COUNT The start count of the download operation if this row refers to a download operation;values between 1 - 99 and column not

used = -1.

Number 2, not null

DL_STATE The state of the download operation in thenetwork element concerned if this row refersto a download operation;

WAITING = 1, RUNNING = 2,STOPPED = 3, ERROR =4,COMPLETED = 5.

Number 1, not null

OP_START_COUNT The start count of the operation if this rowrefers to an operation; values between 1 - 99and column not used = -1.

Number 2, not null

OP_STATE The state of the operation in the network element concerned if this row refers to an

operation;WAITING = 1, RUNNING = 2,STOPPED = 3, ERROR =4,COMPLETED = 5.

Number 1, not null

ERROR_TEXT Error text if the operation in the network element concerned has failed (max. 255characters).

Char 255



Date, not null

NE_ID The identification number of the network element whose data may be inconsistentwith the data in the NMS database. This IDis the same as one of the NE_IDs in theK_SW_NETWORK_ELEMENT table.


STATE Indicates whether the state of the changesis new or quit;

NEW_STATE = 1, QUIT_STATE = 2.

Number 1, not null




Database Tables


NTC TAN 0291/6 en13

error has occurred when performing one of the management operations ROLL,

SWAP or DELETE.

4.8 K_SW_NE_ID_TMP Table

The following table presents one row of the temporary table K_SW_NE_ID_TMP.

The description and possible values, size, and type of each column is defined in

the table.

The K_SW_NE_ID_TMP table is used temporarily when complex SELECT

clauses are performed. This table is usually empty.

4.9 K_SW_PACK_ID_TMP Table

The following table presents one row of the temporary table

K_SW_PACK_ID_TMP. The description and possible values, size, and type of


The K_SW_PACK_ID_TMP table is used temporarily when complex SELECT

clauses are performed. This table is usually empty.

4.10 S_PACKAGE_ID Sequence

The S_PACKAGE_ID is the sequence from which a unique PACK_ID is

generated. The sequence is cyclical; when the maximum value is reached,

sequencing starts again from the minimum value.

The values range between 1 - 4294967295.

4.11 S_DOWNLOAD_ID Sequence

The S_DOWNLOAD_ID is the sequence from which a unique DOWNLOAD_ID and

BCF_OP_ID are generated. The sequence is cyclical; when the maximum value

is reached, sequencing starts again from the minimum value.

The values range between 1 - 4294967295.


NE_ID The network element identificationnumber (Int_Id in the OBJECTS table).

Number, not null


PACK_ID The package identification number (see

4.10). (Pack_Id in K_SW_PACKAGEtable, see 4.1).

Number, not null

0291_6 BTS SW Management Database Description

Documents

Transcript of 0291_6 BTS SW Management Database Description