Zte Software Release Notes_zxsdr-ommb v4.11.10.14p06 v1.0

Software Release NotesConfidential ▲

ZTE Software Release Notes

Version: ZXSDR-OMMB V4.11.10.14P06

Editor NieZhiwei

Reviewed by Nie Zhiwei

Countersign

Standardization

Approved by Nie Zhiwei

ZTE Corporation

Copyright © ZTE Corporation 2008. All rights reserved


Update Record

No. VersionDrafted/

updated by

Draft/update

Date

Reason for

updateMain updating points

1 V1.0 NieZhiwei 2012-11-20 New None

Note 1: This form needs to be filled-in every time when you change the contents of an archived file (an archived file

refers to all files which have been sorted and archived at division level or company level).

2: When it is the first time to archive a file, “Reason for update”, “main updating points” may leave blank.



Table of Contents3 About This Document.............................................................................................................5

3.1 Purpose......................................................................................................................5

3.2 Scope.........................................................................................................................5

3.3 Target Readers..........................................................................................................5

4 Brief Description.....................................................................................................................5

4.1 Release Background..................................................................................................5

4.2 Software-based Hardware.........................................................................................5

4.3 Supported Hardware to the Current Software...........................................................5

4.4 Software-based Platform...........................................................................................5

4.5 Software Compatibility.............................................................................................6

4.6 New Features............................................................................................................6

4.7 Solved Issues.............................................................................................................7

5 Software Changes....................................................................................................................8

5.1 SDR PM Data Change..............................................................................................8

5.2 SDR Alarm/Notification Change..............................................................................8

5.3 New Features............................................................................................................8

5.3.1 NE ID is moved to the front of NE name in the page of TOPO-Tree in CMX. 8

5.3.2 SDR Configuration Toolkit can generate one SDR MO file for every base

station, at the same time, remains the original function....................................................8

5.3.3 KPN support increment modify import.............................................................9

5.3.4 Add mml to support blocking/unblocking GSM function.................................9

5.3.5 Increase template sheet in Nodeb configuration report...................................10

5.3.6 Open batch dynamic manage panel ,managed element tree shows node all the

v11.02.01 version node...................................................................................................10

5.3.7 Increase the function of exporting error messages into an excel file from

verified error messages panel in CMX............................................................................10

5.3.8 Add NodeBVersion information on the head of the exported all-mo-xml

file 11

5.3.9 Support the function of “SDR II Alarm Sync by Subnet” on the view of Fault

Management....................................................................................................................11

5.4 Solved Issues...........................................................................................................12

5.4.1 CQ001.............................................................................................................12

5.4.2 CQ002.............................................................................................................13

5.4.3 CQ003.............................................................................................................13

5.4.4 CQ004.............................................................................................................14

5.4.5 CQ005.............................................................................................................14

5.4.6 CQ006.............................................................................................................15

5.5 Known Issues..........................................................................................................15

5.6 Impact of Upgrading...............................................................................................15

6 SW Loading and Fallback Instructions..............................................................................15

7 Reference...............................................................................................................................15

8 Appendix................................................................................................................................16



3 About This Document

This release notes provides some important information that should be known when current

up to date software is deployed and used. It includes descriptions about compatibility,

functionality of software/hardware and defects correction.

3.1 Purpose

This document will clearly describe the current software release notes (hereafter called “the

notes”), including new features, solved issues, verification methods and expected purpose of each

modification. It will be taken as reference for field test when the release is upgraded.

3.2 Scope

This release notes mainly covers ZXSDR-OMMB V4.11.10.14P06.

3.3 Target Readers

Classification Attention Points

Purchaser’s coordinators Brief Description of Software Background

Outfield R&D support engineers New Features and Solved Issues

Outfield support engineers Brief Description of Software Background

4 Brief Description

4.1 Release Background

This is commercial release applied to commercial commissioning and network operation. It

was released by ZTE. It intends to revise some issues in the test of previous version. Its features

are inherited from previous version.

Current Ver. Previous Ver.

ZXSDR-OMMB V4.11.10.14P06 ZXSDR-OMMB V4.11.10.14P05

4.2 Software-based Hardware

Based on a Computer of at least 3G memory, 1.6GHz*4 CPU, 146G*2 HD or higher

configuration.

Notes: The hard disk should keep 30% free of the total size of 146G*2

4.3 Supported Hardware to the Current Software

The HP DL58075 server of Intel CPU of 1.6G*4, RAM of 16G, and HD of 146GB * 4 is

configured to support the current software.

4.4 Software-based Platform

Based on the Following platform

Type of base OS/DB/JDK Detail Applicable or not

OS Windows2000(SP2 or higher)

Windows2003(SP2 or higher)

Windows XP (SP2 or higher)

RedHat Linux(RHEL4)

Applicable



Type of base OS/DB/JDK Detail Applicable or not

Database Oracle 10g Applicable

JDK jdk1.6.0 Applicable

4.5 Software Compatibility

Software is compatible to the following versions:

OMM NodeB

V4.09.21.14

NodeB

V4.11.10.08P0x

NodeB

V4.11.10.14P04

NodeB

V4.11.10.14P05

NodeB

V4.11.10.14P06

ZXSDR-OMMB

V4.11.10.14P06√ P（Notes 1） √ √ √

OMM EMS

V12.10.040jP00

3

EMS

V12.11.40B5

EMS

V12.11.40P2

EMS

V12.11.40P3

ZXSDR-OMMB

V4.11.10.14P06

× × √（Notes 2） √

Notes：╳ means incompatible; √ means compatible

Notes1： In WOMCBV4.11.10.14P06, user can’t do the operation such as Modify Configuration Data,

Synchronize Configuration data to NE and Configure by Base Station Data in Configuration Management when

charge NodeB V4.11.10.08P0x

Notes 2： In EMS V12.11.40P2, two alarm codes added in OMCBV4.11.10.14P05 will display “ NE Alarm”. The codes are 198096474 and 198096475

4.6 New Features

New

FeaturesBrief Description

Remar

k

1

NE name consists of user label, NE type, NE version and NE ID in

order in the page of TOPO-Tree. IF user label is too long ,it is not

convenient to choose NE that we need by NE ID when there are too

many NE.

2SDR Configuration Toolkit can generate one SDR MO file for every

base station, at the same time, remains the original function

3KPN just supports import the whole table, doesn’t support import

modified data. So, add supports increment modify import.

4 Support blocking/unblocking GSM function by using mml



New

FeaturesBrief Description

Remar

k

5 Increase template sheet in Nodeb configuration report

6Open batch dynamic manage panel, managed element tree shows node

all the v11.02.01 version node.

7

When some errors occur in process of verifying data ,clicking the Error

Detail button will pop up the Error Messages panel ,Right-click on the

table in the panel ,choose export option ,all the information in table will

exported to an excel file.

8Add NodeBVersion information on the head of the exported all-mo-

xml file; also, complete the omcVersion information (including ‘P’).

9Support the function of “SDR II Alarm Sync by Subnet” on the view of

Fault Management.

4.7 Solved Issues

Defect No. Brief DescriptionInfluence Remar

k

1

When export telenor csv data

of ME 409, The first three

columns of Transmission and

radio’s MO is repeated.

void

2OMMB client become so

slowly that cannot use

User cannot manage NE

by OMMB

3

When export Telenor csv data

of ME 409, some data is lost.

The value of parameters is

empty, but actually, it isn’t

empty. For example,

SECTORID and

REFUBASEBANDPOOL_PO

OLID in ULocalCell’s csv

file.

void

4

When export Telenor csv data

of ME 409, some data’s

format is changed, Most are

ref’s parameter. For example,

REFTXDEVICE and

REFRXDEVICE in USector’s

csv file.

void

5

When export csv data of ME

411, csv file names aren’t

match with the file data.

void



Defect No. Brief DescriptionInfluence Remar

k

6

When power management

receive an assortment of

wireless network

management data stream.

Power management

memory overflow

void

5 Software Changes

5.1 SDR PM Data Change

None

5.2 SDR Alarm/Notification Change

None

5.3 New Features

5.1.1 NE ID is moved to the front of NE name in the page of TOPO-Tree in CMX

Description

NE name consists of user label, NE type, NE version and NE ID in order

in the page of TOPO-Tree. IF user label is too long ,it is not convenient

to choose NE that we need by NE ID when there are too many NE.

AdvantageIt is convenient to choose NE by NE ID after moving NE ID to the front

of NE name.

Range of Impact None

Impact to the Background None

Verification

1. Enter into the home page of CMX, choose Export Data File, and

click next.

2. Check the NE name whether the NE ID is in front of the NE

name in TOPO-Tree.

Parameter Changes None

5.3.8SDR Configuration Toolkit can generate one SDR MO file for every base station, at the

same time, remains the original function.

DescriptionSDR Configuration Toolkit generate one SDR MO file for every base

station.

Advantage

In SDR Configuration Toolkit, when import negotiation file, users can

select “Abstract Single Base Station Data” checkbox, the toolkit will

generate one SDR MO file for every base station in negotiation file. If

users don’t select the checkbox, the toolkit will generate one SDR MO

file for one negotiation file.





Verification

Run SDR Configuration Toolkit, In Import tab, includes “Abstract Single

Base Station Data” checkbox. When select the checkbox, assign a

directory in “Export SDR MO File”, Execute import. The toolkit will

generate one SDR MO file for every base station in negotiation file.


5.3.9KPN support increment modify import

DescriptionKPN just supports import the whole table, doesn’t support import

modified data.

Advantage Add supports increment modify import.



Verification

1. Ready increment xml file, compress for zip file.

2.Click View -> MML Terminal of OMCB;

3.Enter "SET NETYPE:SDR";

Press "Execute(F5)" button;

4. Enter "GET SET DATAFILE: serialno="", STYLE=3,

DESFILE="****.zip";****.zip is file name of step 1.


5. The operation results will be shown on the "Command Execute

Result".

If the increment file is right, base station’s data will be modified.

Otherwise create error log file.


5.3.10 Add mml to support blocking/unblocking GSM function

Description Support blocking/unblocking GSM function by using mml

Advantage Support blocking/unblocking GSM function by using mml



Verification 1.Pre-condition for a test:

OMCB system runs normally.

2.Test Procedure:

1. Enter the MML Terminal of OMCB

2. Execute the following commands:

Set netype:sdr

DDM

BTSFUNCTION:SUBNETID=0,TYPE=0;//TYPE=1,unblock

action

3.Expected result:



The GSM function is supposed to be blocked or unblocked.


5.3.11 Increase template sheet in Nodeb configuration report

Description Increase template sheet in Nodeb configuration report

Advantage Increase template sheet in Nodeb configuration report. Report which

contains all Mo can be used in CMX



Verification When export Nodeb configuration report, choose all mo. Exported

report can be used in CMX to configuration data


5.3.12 Open batch dynamic manage panel ,managed element tree shows node all the v11.02.01

version node

DescriptionOpen batch dynamic manage panel, managed element tree shows node

all the v11.02.01 version node.

AdvantageGet v11.02.01 version managed element in batch dynamic manage

panel directly



Verification

1.Pre-condition for a test:


2.Test Procedure:

1. open batch dynamic manage panel

3.Expected result:

Managed element tree shows nodes are the entire v11.02.01 version

node. .


5.3.13 Increase the function of exporting error messages into an excel file from verified error

messages panel in CMX

Description

When some errors occur in process of verifying data ,clicking the Error

Detail button will pop up the Error Messages panel ,Right-click on the

table in the panel ,choose export option ,all the information in table will

exported to an excel file.

AdvantageIt is more convenient to query error messages when there are too many

error messages.





Verification



2.Test Procedure:

Some errors occur in process of verifying data in CMX.

Clicking the Error Detail button will pop up the Error Messages

panel, Right-click on the table in the panel, choose export option

3.Expected result:

Check whether the excel file exists.


5.3.14 Add NodeBVersion information on the head of the exported all-mo-xml file

DescriptionAdd NodeBVersion information on the head of the exported all-mo-xml file; also, complete

the omcVersion information (including ‘P’).

AdvantageAdd NodeBVersion information on the head of the exported all-mo-xml file; also, complete

the omcVersion information(including ‘P’)


Impact to the

BackgroundNone

Verification

1. Open file ums-svr\deploy\deploy-020sdrmap.properties, and modify the K-V

neversion.flag=false to neversion.flag=true

2. Export the ME all-mo-data xml file

3. Observe the head of the xml file:

2.1 If the linkstate is built, there is a NodeBVersion segment

2.2 If the linkstate is break, there is no NodeBVersion segment

Parameter Changes OmcVersion means OMCB version; modelVersion means data version.

5.3.15 Support the function of “SDR II Alarm Sync by Subnet” on the view of Fault

Management.



DescriptionSupport the function of “SDR II Alarm Sync by Subnet” on the view of

Fault Management.

Advantage It is convenient for user to synchronizing alarm by Subnet



Verification



2.Test Procedure:

1) Open the “View” -->”Fault Management”

2) Move the mouse on the Subent node in the Topo tree, click

the right button

3) Select “SDR II Alarm Sync by Subnet”

3.Expected result:

All the NEs in the Subnet will synchronize alarm by one

operation.


5.4 Solved Issues

5.1.1 CQ001

Defect ID 614002629147

Defect Level General

Test Version WOMCBV4.11.10.14P05

Symptoms When export telenor csv data of ME 409, The first three columns of

Transmission and radio’s MO is repeated.

Impact to end user void

Impact to the operator void

Analysis Method of export data repeats the first three columns.

Solution Modify the method of export data.



2.Test Procedure:

1.Click View -> MML Terminal of OMCB;



3.Expected result:

1.Enter "GET

CMBCSV:SUBNETID="a",MEID="a",SCOPE="a",SERIALNO="

123"";





Result".

Check export files in \ums-svr\tmp\ftp\nodeb_csv folder. The first

three columns of the csv file are not repeated.

5.4.7 CQ002

Defect ID 614002574712



Symptoms OMMB client become so slowly that cannot use

Impact to end user User cannot manage NE by OMMB


Analysis Option of listener in OMMB client refresh topo tree is useless and

make client become slow.

Solution Remove this option.


Open batch Configuration Management panel, select managed

element unless 100. Then modify attribute of managed element.

2.Test Procedure:

Check whether OMMB client become slow so much.

3.Expected result:

OMMB client can use smoothly.

5.4.8 CQ003

Defect ID 614002651444



Symptoms When export Telenor csv data of ME 409, some data is lost. The

value of parameters is empty, but actually, it isn’t empty. For

example, SECTORID and REFUBASEBANDPOOL_POOLID in

ULocalCell’s csv file.



Analysis When Telenor export transferred to version 411 from version 409,

some function is lost.

Solution Add lost function.

Verification 1.Click View -> MML Terminal of OMCB;



3.Enter "GET


123"";





Result".

Check export files in \ums-svr\tmp\ftp\nodeb_csv folder. The data in

csv file is the same as database.

5.4.9 CQ004

Defect ID 614002651425



Symptoms When export Telenor csv data of ME 409, some data’s format is

changed, Most are ref’s parameter. For example, REFTXDEVICE

and REFRXDEVICE in USector’s csv file.



Analysis When Telenor export transferred to version 411 from version 409,

some function is lost.

Solution Add lost function.




3.Enter "GET


123"";



Result".

Check export files in \ums-svr\tmp\ftp\nodeb_csv folder. The data’s

format in csv file is the same as version 409.

5.4.10 CQ005

Defect ID 614002693007



Symptoms When export Telenor csv data of ME 411, the file names are not

match with the file data.



Analysis Two new objects are not exported.

Solution Add the two new objects.






3.Enter "GET


123"";



Result".

Check exported files in \ums-svr\tmp\ftp\nodeb_csv folder. The file

name should match with the file data.

5.4.11 CQ006

Defect ID 614002750094



Symptoms When power management receive an assortment of wireless

network management data stream. Power management memory

overflow



Analysis Lack of protection for multiple thread Socket write data at the same

time.

Solution Multithreaded write-through Socket data at the same time, together

with protection.

Verification Because it is a multithreading issues, No way leads to inevitable

reappearance . Send heartbeat information power management

conversion into minimum time interval. Meanwhile reported the

greatest number of warning messages.

5.5 Known Issues

None

5.6 Impact of Upgrading

See the isolated document.

6 SW Loading and Fallback Instructions

None.

7 Reference

In order to guarantee OMM SW and EMS SW synchronization, EMS SW is designed

such that it must be backward compatible with old OMM, SW version of network element

must be upgraded in the following order:

EMS---->OMM

In case of OMM new version is not compatible with EMS old version. When the old EMS is



compatible with the new OMM version, it is not needed to follow this order.

OMM---->RNC---->Node B

In case of RNC or Node B new version is not compatible with OMM old version. When the

old OMM is compatible with the new RNC and Node B version, it is not needed to follow

this order; and we strongly recommend the RNC and OMM should be upgraded in one

night.

8 Appendix

OMMB port list：


Zte Software Release Notes_zxsdr-ommb v4.11.10.14p06 v1.0

Documents

Transcript of Zte Software Release Notes_zxsdr-ommb v4.11.10.14p06 v1.0