zxg10-bsc(v2)operation manual vol 1

ZXG10 Z T E G S M W L L S Y S T E M

GGSSMM WWLLLL SSYYSSTTEEMM

OOppeerraattiioonn MMaannuuaall OOFF

ZZXXGG1100--BBSSCC ((VV22))

VVooll.. 11

SSHHEENNZZHHEENN,, CCHHIINNAA

Operation Manual of ZXG10-BSC (V2)-Vol 1

Preface

ZXG10 is the GSM mobile communication system independently developed by ZTE. It is composed of ZXG10-MSS mobile switching system and ZXG10-BSS base station subsystem. The ZXG10-BSS base station subsystem is responsible for providing and managing wireless transmission in GSM, and comprises the ZXG10-BSC base station controller and the ZXG10-BTS base station transceiver, etc. ZXG10-OMCR (V2) is the operation & maintenance platform of the ZXG10-BSS (V2) base station subsystem, and the ZXG10-BSC Base Station Controller Operation Manual mainly introduces the operation of the ZXG10-OMCR (V2).

Unless otherwise specified in this manual, OMCR (V2) refers to the operation and maintenance center of ZXG10-OMCR (V2) base station sub-system, and BSC (V2) refers to ZXG10-BSC (V2) base station controller.

This manual is divided into Volume I and Volume II.

Volume I includes 7 chapters: Chapter 1 outlines the position, function and composition of the OMCR (V2) system; Chapter 2 mainly introduces the running environment of OMCR (V2) system and the procedure of installing the server and client; Chapter 3 introduces in detail the safety management functions of the OMCR (V2) system, including user management and operation log; Chapter 4 introduces specifically the fault management functions of the OMCR (V2) system, including alarm management and test management; Chapter 5 introduces in detail the performance management functions of the OMCR (V2) system, including performance management, performance analysis console, invoke tracing and signaling tracing; Chapter 6 introduces in detail the configuration management functions of the OMCR (V2), including radio resource management, software loading, integrated configuration management and dynamic data management; Chapter 7 introduces in detail the database configuration and monitoring functions of the OMCR (V2) system; Appendix sums up the used abbreviations for ease of reading this manual.

Volume II consists of two chapters and appendixes. Chapter 1 introduces the man-machine commands of each module of the OMCR (V2) system;


Chapter 2 describes in detail the common basic operations of each module of the OMCR (V2) system according to the functional category; Appendix A lists all performance measurement counters and their descriptions; Appendix B sums up all mentioned abbreviations for the ease of reading this manual.

This set of the manuals also include the following documents:

Technical Manual for ZXG10-BSC (V2) Base Station Controller

Installation Manual for ZXG10-BSC (V2) Base Station Controller.

Maintenance Manual for ZXG10-BSC (V2) Base Station Controller.

Statement: The actual product may differ from what is described in this manual due to frequent update of ZTE products and fast development of technologies. Please contact the local ZTE office for the latest updating information of the product.


Page I of III

Contents

1 OVERVIEW .....................................................................................................................1

1.1 OVERVIEW ........................................................................................................................1 1.1.1 System position ...............................................................................................................1 1.1.2 Functions and structure ...................................................................................................2 1.2 COMPOSITION OF THE OPERATION AND MAINTENANCE SYSTEM...............................................5 1.2.1 WSF module....................................................................................................................6 1.2.2 LMF module.....................................................................................................................7 1.2.3 LAF module .....................................................................................................................8 1.2.4 MSF module ....................................................................................................................8 1.2.5 BMF module ....................................................................................................................8 1.2.6 NAF module.....................................................................................................................9

2 INSTALLATION OF THE O&M SYSTEM......................................................................10

2.1 RUNNING ENVIRONMENT...................................................................................................10 2.1.1 Server requirements ......................................................................................................10 2.1.2 Client requirements........................................................................................................11 2.2 SERVER INSTALLATION......................................................................................................12 2.2.1 Software requirements...................................................................................................12 2.2.2 Installation Procedure ....................................................................................................13 2.3 CLIENT INSTALLATION .......................................................................................................33 2.3.1 Software requirements...................................................................................................33 2.3.2 Installation procedure ....................................................................................................34 2.4 MAIN INTERFACE..............................................................................................................38 2.4.1 User logon .....................................................................................................................39 2.4.2 Main interface ................................................................................................................40 2.4.3 Exiting the system..........................................................................................................44

3 SECURITY MANAGEMENT..........................................................................................46

3.1 USER MANAGEMENT.........................................................................................................46 3.1.1 Overview........................................................................................................................46 3.1.2 Operations of user management interface.....................................................................48 3.2 OPERATION LOG ..............................................................................................................64 3.2.1 Overview........................................................................................................................64 3.2.2 Operations of the operation log interface .......................................................................65


Page II of III

4 FAULT MANAGEMENT ................................................................................................72

4.1 ALARM MANAGEMENT.......................................................................................................73 4.1.1 Overview........................................................................................................................73 4.1.2 Classification of alarm information .................................................................................74 4.1.3 Operations of the alarm management interface .............................................................75 4.2 TEST MANAGEMENT........................................................................................................114 4.2.1 Overview......................................................................................................................114 4.2.2 Operations of the test management interface ..............................................................117

5 PERFORMANCE MANAGEMENT..............................................................................129

5.1 PERFORMANCE MANAGEMENT.........................................................................................130 5.1.1 Performance management items.................................................................................130 5.1.2 Operations of the performance management interface................................................138 5.2 PERFORMANCE ANALYSIS CONSOLE.................................................................................166 5.2.1 Overview......................................................................................................................166 5.2.2 Operations of the performance analysis console interface...........................................167 5.3 CALL TRACING ...............................................................................................................178 5.3.1 Overview......................................................................................................................178 5.3.2 Operations of the call tracing interface.........................................................................179 5.4 SIGNALING TRACING.......................................................................................................185 5.4.1 Overview......................................................................................................................185 5.4.2 Operations of the signaling tracing interface................................................................185

6 CONFIGURATION MANAGEMENT............................................................................197

6.1 RADIO RESOURCES MANAGEMENT...................................................................................197 6.1.1 Overview......................................................................................................................197 6.1.2 BSS .............................................................................................................................199 6.1.3 Cell parameters ...........................................................................................................263 6.1.4 Configuring Cell ...........................................................................................................359 6.2 SOFTWARE LOADING ......................................................................................................426 6.2.1 Overview......................................................................................................................426 6.2.2 Software loading flow...................................................................................................427 6.2.3 Version information......................................................................................................429 6.2.4 Operations of the software loading interface................................................................431 6.2.5 Troubleshooting ...........................................................................................................447 6.3 INTEGRATED CONFIGURATION MANAGEMENT.....................................................................448 6.3.1 Overview......................................................................................................................448


Page III of III

6.3.2 Operations of the integrated configuration management interface...............................450 6.4 DYNAMIC DATA MANAGEMENT..........................................................................................499 6.4.1 Overview......................................................................................................................499 6.4.2 Operations of the dynamic data management interface...............................................500 6.4.3 Troubleshooting ...........................................................................................................505

7 DATABASE CONFIGURATION AND MONITORING..................................................507

7.1 OVERVIEW ....................................................................................................................507 7.2 INTERFACE OPERATIONS .................................................................................................507 7.2.1 Selecting monitoring contents......................................................................................509 7.2.2 Monitoring database information..................................................................................511 7.2.3 Monitoring alarm threshold ..........................................................................................511 7.2.4 Setting threshold parameters.......................................................................................512

APPENDIX ABBREVIATIONS...................................................................................................514


Page 1 of 516

1 Overview

1.1 Overview

OMC (Operation and Maintenance Center) refers to the management center of BSS (Base Station Subsystem) and MSS (Mobile Switching System). In GSM specifications, OMC is divided into two parts in light of different objects: OMCS and OMCR. OMCR refers to the operation and maintenance center of BSS and OMCS refers to the operation and maintenance center of MSS. This manual mainly introduces OMCR (V2) of ZTE.

With the managed object as its core, OMCR (V2) provides management function in addition to other management tools. It features powerful functions, reasonable structure, high modularity, high flexibility and reliability. It supports ZXG10-BSS base station subsystem and the new-type base station equipment developed by ZTE, such as micro-BTS (micro base station transceiver).

1.1.1 System position

OMCR (V2) controls the object called BSS, which includes Base Station Controller (BSC) and Base Station Transceiver (BTS). The main functions of MCR (V2) include the following: perform effective configuration management of BSS equipment, reflect the BSS fault information in the course of running in real time, make analysis and statistics of BSS performance, and provide the access interface to Network Management Center (NMC). As shown in Fig. 1-1, OMCR (V2) provides the standard interface to NMS, accepts the management operations from NMC, and reports the operation results and events; it manages BSS via the standard or non-standard interface and accepts the information reported by BSS.


Page 2 of 516

Network managementcenter (NMC)

Operation & maintenancecenter (OMCR)

Base stat ion subsystem (BSS)

Network managementlayer (NML)

Element managementlayer (EML)

Network elementlayer (NEL)

Fig. 1-1 Position of OMCR (V2) in the PLMN system and its functions

In TMN logical layered architecture, BSS is located at the NE layer, OMCR (V2) at NE management layer and NMC at NM layer.

1.1.2 Functions and structure

ZXG10-OMCR (V2) is based on the client/server structure; the application is achieved by the application server, the client application does not directly establish the communication connection with MP of the BSC; the client application is not involved with the implementation of the application, it only enables the operator to input the operation commands and output the operation results, as shown in Fig. 1-2.

SUN (development environment) is used in the server, and Oracle as the database system, so as to meet the performance requirements during system running. Meanwhile, the modular division of system software lays a solid foundation for system expandability so that multiple software modules are able to run on several servers in a distributed manner according to different requirements so as to enhance the processing capacity of the system.

The overall system structure is designed in compliance with the TMN (telecom management network) system structure as described in ITU-T. TMN is designed by ITU-T as a standard for system management within the telecom field. Using standard specifications in open system interconnection (OSI) for reference, TMN puts forward the functional model, information model and physical model for system interconnection. TMN stipulates not only the management system structure but also the mechanism for specific management functions, including configuration, fault, performance etc. TMN utilizes managed object (MO) to abstract the


Page 3 of 516

managed resources, that is, the operations on managed objects in the system management are mapped to MO.

Thanks to its modular design plan, OMCR (V2) provides guarantee in terms of expandability and reliability, so that it is able to configure the system size in light of system load.

The functions of OMCR (V2) system are designed in line with TMN specifications and GSM specifications of ETSI. On the basis of standard management functions, the system also provides the users with more additional applications. The system functions are organized based on the managed objects as the core in addition to a variety of management tools.

OMCR (V2) system follows the development specifications recommended by TMN in its whole development process from setting up the information model, which is the general reflection of the objectives to be reached in the entire system.

Operationterminal

Operationterminal

Operationterminal

Application server

BSS

TCP/IP,X.25 etc.

BSSBSS

Fig. 1-2 Architecture of OMCR (V2) distributed applications

OMCR (V2) system mainly offers such functions: configuration management, performance management, fault management and security management

1. Configuration management

It is to configure the BSS system equipment and the radio resource data, including: integrated configuration management, radio resource management, software loading and dynamic data management.


Page 4 of 516

2. Performance management

1) The operator creates measurement task to gather the system running data,

which will be finally stored in the measurement database and no longer

have any connection with the measurement task. The operator may either

analyze these data using the performance analysis console or export these

data intended for other analysis platform or network optimization software.

2) As for the measurement task ongoing with data collection, the operator may

observe the current value of a counter for a certain measurement object in

time.

3) The operator may observe some designated events occurring in a cell,

including handover observation and channel assignment observation. The

handover observation involves the observation of intra-cell handover,

intra-BSS handover and inter-BSS handover.

4) The operator is able to set the statistical interval and indexes for BSS quality

of service (QoS) alarm. When the system QOS index exceeds the specified

value, an alarm will occur. QoS alarm measurement is independent of

performance data collection and still can collect or calculate the related data

when no measurement job is assigned.

3. Fault management

Fault management serves to display the alarm at the administrator side. The core of fault management lies in the accurate location of system faults. The relevance judgment may help display the real alarms on the interface.

Fault management also involves diagnostic test, which mainly functions to test the BSS system by setting test tasks, so as to locate the fault or discover the hidden fault.

4. Security management

Security management guarantees the security of handling administrative affairs. The system security architecture can be divided into three levels: the user, operation and managed object. The security management has four major functional modules: authorization module, authentication module, data management module and network transmission security module. Meanwhile,


Page 5 of 516

security management also enables the query and cancellation of user operation history records.

1.2 Composition of the operation and maintenance system

The application system is based on the client/server structure. Four application entities are available on the server. They are Management Support Function (MSF), NMC Management Access Function (NAF), Local Management Function (LMF) and Local Access Function (LAF). The relationship among these entities, WSF of the local operation and maintenance, and the BMF running on the MP is shown in Fig. 1-3.

MSF

LMF LAF

WSF BMF

NAF

Fig. 1-3 Overall structure of the system software

Of which: WSF refers to Workstation Function, NAF to NMC Access Function, LMF to Local Management Function, LAF to Local Access Function, MSF to Management Support Function, and BMF to BSS Management Function.

NAF provides the interface for the management access of the NMC; LMF provides the interface for the WSF management application access, and it is the core of achieving the system management; LAF implements the proxy function specified by TMN, and maintains one MIT tree. The information exchange in the management activity is based on the Managed Objects, the MO set is called Management Information Base (MIB). MIB is organized just like a tree, which is called the Management Information Tree (MIT), also called MO instance tree.); MSF is the common function of the system, such as Database Information Function (DIF) and Message Communication Function (MCF), which are the links of each part and the set of common functions.

Fig. 1-4 shows the overall functional architecture of system software. As BMF

and NAF serve as the extended part of the system, they are not marked in the


Page 6 of 516

figure.

Instancemanagement

Agencyfunction

Communicationmanagement

Topologymanagement

Operationauthentication

Eventmanagement

Logmanagement

Relevancemanagement

System equipmentmanagement

System processmanagement

Status andinformation display

Usermanagement

Groupmanagement

Viewmanagement

Operationmanagement

Taskmanagement

Thresholdmanagement

Instant view

History query

Network planninginterface

Sy stemsy nchronization

Radio resourcemanagement

Versionmanagement

Fault handling rule

Historical fault query

Fault customizationhandling

Diagnostics test

Database accessinterface

State machinemanagement

MSF

LAF

LMF

(Basic components)

LMF

(managementfunctions)

File transfer interface

Securitymanagement

Performancemanagement

Configurationmanagement

Faultmanagement

Sy stem postoffice service

(Agent)

(Common functions)

Fig. 1-4 Functional architecture of OMCR (V2) software

1.2.1 WSF module

WSF is an application located at the client workstation to provide F and G interface functions as stated in TMN, so that the information can be presented to the customers in a correct and consistent manner. F interface exchanges the information between LMFs on the server, and G interface provides character and graphical operation modes. As all application functions are implemented on the server, the WSF is required to resolve the user’s commands and the result returned by the server correctly. To achieve these functions, it is necessary to provide the appropriate communication management mechanism responsible for the session between the management user and the server. Therefore, WSF mainly involves user interface support function (UISF), network communication function (NCF), command resolution function (CRF), MMI kernel function (MKF) and window administration function (WAF).


Page 7 of 516

1.2.2 LMF module

From the angle of TMN information model, LMF acts an administrator mainly to achieve the operating system functions as stipulated in TMN. It works to process information related to BSS management, support and control the realization of BSS equipment management functions, process original data and generate value-added data, such as data concentration, alarm modification, statistics and performance analysis, and responds to the received information. LMF is still required to support user management access function WSF. Its functions mainly include data acquisition and data control, action activation and confirmation as well as notice delivery.

LMF mainly functions to achieve BSS management. LMF receives the resolved operation requests from the client, and implements the operations using different application processing functions in light of operation contents. The user’s operations can be done whether to MIT tree or not. The former is mainly of interests to the operation on the current management resources; while the later mainly aims at the system itself and the operations on the management resource historical data, such as data query of the performance management and some non-query operations (e.g. security management).

Organized in line with TMN specifications, LMF management functions can be divided into security management, performance management, configuration management and fault management. The basic LMF components serve as the foundation for the realization of system functions. For example, topology management provides the system with topology data, and the configuration management and fault management can modify the system topology information by way of topology management. LMF includes the following functions: command distribution function (CDF), command log management function (CLF), session service function (SSF), management application function (MAF) and operation output function (OOF). MAF is composed of configuration management function (CMF), performance management function (PMF), fault management function (FMF) and security management function (SMF).

LMF has two interfaces. One is the F interface between it and WSF and the other is the Q interface between it and LAF. The messages at Q interface falls into two types: One is the operation request of the LMF for


Page 8 of 516

the MIT tree and the response returned by the LAF; the other is the alarm notice that has been transmitted after the LAF has received the alarms generated by the NE.

1.2.3 LAF module

From the view point of TMN information model, LAF acts as the agent and is the general agent of the system-controlled BSS. Its main functions are to maintain the MO management instance trees (MIT), transmit information between BSS and OMCR (V2), and ensure the correct interpretation of messages from BSS. The main functions include temporary storage, filter, threshold management and test, etc. These functions are to implement the management functions of LMF.

LAF functions to support the realization of administrative operations. Its application core is MO instance tree (MIT) and manage BSS by way of MIT maintenance. The nodes on MIT tree stand for the specific and manageable resources in a network. Information contained on the nodes gives a description of all the managed resources. The modification of MIT must correspond to the change in the current network resources. If the modification cannot keep in step with the real resource state, it is necessary to synchronize it to the real state of network resources.

LAF has two interfaces, one with LMF and the other with BMF.

1.2.4 MSF module

MSF provides management support functions and serves as the base for other functions, including database interface, system post office server and state machine management and so on.

MSF is a set of common functions of the system. Its main functional modules include: database access, system process running monitoring, system intra-module (node) communications, system resource occupation monitoring, etc.

1.2.5 BMF module

From the view point of TMN information model, BMF serves as the agent for its BSC. The MO instances it manages is part of MIT tree in LAF. The


Page 9 of 516

specific storage forms of MO instances are transparent to OMCR (V2).

As an application on BSC main processor (MP), BMF serves as the agent for background applications. As an agent, BMF serves to translate the operation commands on MO from OMCR (V2) into MP database operations and operations on various boards, so as to finalize the administrative operations of OMCR (V2).

To support the application of local maintenance terminal (LMT) in BSC, BMF should be able to receive LMT commands. These commands are divided into two types: inquiry and operation. If the operation instruction has changed the state or attribute of the corresponding MO resources, BMF is expected to notify OMCR (V2) of the information change in the form of event report.

BMF should also have the function of access authentication to prevent invalid host access.

BMF interface serves externally as LAF and internally as MP database system.

1.2.6 NAF module

NAF is able to provide access functions in line with NMC requirements. OMCR (V2) system shall provide database access interface. This interface is developed by NMC and OMCR (V2) through mutual cooperation. OMCR (V2) provides the database and its structure, while the data scan process is developed by NMC and runs in NMC system.

NAF functions to provide an interface for NMC access, i.e. the Q3 interface.


Page 10 of 516

2 Installation of the O&M System

OMCR (V2) server is located in the UNIX platform, while client in the NT platform. This chapter introduces the system installation of OMCR (V2) server and client, as well as the OMCR (V2) main interface displayed after the client is installed. Note: For specific usage of UNIX commands in this section, please refer to Solaris online help.

2.1 Running environment

2.1.1 Server requirements

1. Install Solaris Unix operating system, requiring Solaris version 5.6 with relevant Patch packages released by SUN (they are preinstalled on SUN’s computer).

2. Create DBA user group and Oracle user.

3. Install Oracle 8.0.5 database system in Oracle user mode.

4. Create “omc” user group and “omc” user, “ftpuser” user and “omclog” user.

5. Install and configure OMCR (V2) server system in “omc” user mode.

For server hardware configuration, many factors should be considered for good balance, such as database, CPU processing ability and number of managed objects, as well as the influence of system response time to user commands on the performance of the whole system.

Table 2-1 contains typical server system hardware configurations. In actual deployment, respective configuration parameters can be adjusted according to system contributing factors and overall performance for a better adaptability to various possible applications. For example, to increase the number of TRXs manageable by system, some component configurations can be improved, such as CPU primary frequency and CPU amount, etc.


Page 11 of 516

Table 2-1 Typical system hardware configurations (main components)

Configuration capacity System

configurations Small capacity Medium capacity

Large capacity

Super large capacity

Server quantity

1 pcs 2 pcs 3 pcs ≥3 pcs

CPU 400MHz×2 400MHz×4

400MHz×4

LMF: 400MHz×4

DB: 400MHz×8

LAF: 400MHz×8

≥400MHz×8

Memory 512MB 1GB

1GB

LMF: 1GB

DB: 2GB

LAF: 2GB

≥2GB

RAID 40GB 80GB 120GB ≥120GB

Number of

TRXs

manageable

1 ~ 2 BSS

1024 TRX

2 ~ 4 BSS

5000 TRX

5 ~ 10BSS

10000 TRX

≥10 BSS

≥10000 TRX

Remarks

LMF, LAF and

DB module

run on one

server.

Used in

situation with

low reliability

requirement

(users do not

want high

investment).

Two servers

compose

(LAF+LMF)+DB,

LAF+(LMF+DB)

or

(LAF+DB)+LMF.

It is

recommended to

adopt RAID for

high-speed data

access and high

reliability.

Consist of

three servers

running LMF,

LAF and DB

module

respectively.

It is

recommende

d to adopt

RAID for

high-speed

data access

and high

reliability.

Expand based on large

capacity configuration.

First expand various

components (vertical

expansion),

then expand the

number of servers

(horizontal expansion).

Note: 1. Server here refers to SUN’s server.

2. In specific design, redundant disk capacity for RAID adoption should be added, which is related to the

specific disk type.

2.1.2 Client requirements

1. Install Microsoft Windows NT 4.0 Workstation (or Windows 2000


Page 12 of 516

professional Edition);

2. If Windows NT 4.0 is to be installed, Windows NT Service Pack 4 version or higher is required.

3. Install the Excel of Microsoft Office 97 or versions above.

4. Install OMCR (V2) client program.

5. Install printer for the system requiring printer.

This chapter mainly introduces the installation of OMCR (V2) server system and client system. For the installation of other software systems, please refer to relevant installation instructions.

2.2 Server installation

This section introduces the installation of OMCR (V2) server program.

OMCR (V2) server installation is performed under UNIX environment. Before it is started, first install Solaris and Oracle system, and create “omc” user group and “omc” user. For the installation of Solaris and Oracle system, please refer to ZXG10-BSC (V2) Base Station Controller Installation Manual.

In Oracle system installation process, two points should be noted for our system:

1. Select AMERICAN for SERVER database language NLS_LANGUAGE.

2. Select WE8ISO8859P1 for SERVER database character set NLS_CHARACTERSET.

2.2.1 Software requirements

System software required for server installation includes:

1. OMCR (V2) server program.

2. Solaris version 5.6 with relevant Patch packages released by SUN.


Page 13 of 516

3. Oracle 8.0.5.

Before installing OMCR (V2) server program, please install Solaris and Oracle first.

2.2.2 Installation Procedure

The specific steps of installing the OMCR (V2) are as follows:

1. Preparations before installation

2. Conduct the installation.

3. Confirmation and check after installation

2.2.2.1 Installation preparations

1. Installation environment

Before the OMCR (V2) server software is installed, the software environment of SUN server should satisfy some requirements, namely: the operating system is Solaris 5.6, the database system is Oracle 8.0.5, the NLS_LANGUAGE of Oracle is AMERICAN and the NLS_CHARACTERSET is WE8ISO8859P1.

Use the “uname –a” command to check the version of the operating system, if it does not meet the above requirements, obtain correct version of the operating system and reinstall. Please refer to ZXG10-BSC (V2) Base Station Controller Installation Manual.

Use the “sqlplus” command and “system” user to login Oracle database, and Oracle version will be displayed after successful login, then use the “select userenv ('language') from dual;” SQL command to view language and character set. If they are inconsistent with above requirements, obtain correct version of Oracle 8.0.5 and reinstall. Please refer to ZXG10-BSC (V2) Base

Station Controller Installation Manual.

2. User and authority

OMCR(V2) server running needs to set an “omc” user group, which includes three users: running user “omc”, FTP user “ftpuser” and Log file view user “omclog”. Of which: the user “omc” is to run


Page 14 of 516

the server program of OMCR (V2), its HOME directory should be set as the start directory OMCHOME in principle; the user “fptuser” is used for the OMCR (V2) client to transmit files via the FPT service and the server, this user can only run the OMCHOME/tmp/ftp directory and only has the read authority; the user “omclog” is to view the log file of the server and he only has the authority of reading the log file.

To set above users and their authorities, first obtain the password of the “root” user, then run the following commands under root user environment:

1) Add the omc user group: groupadd omc

2) Add the omc user: useradd –g omc –d /export/home/omc omc

3) Set the password for the user omc: passwd omc

4) Setting the directory for the user omc: mkdir /export/home/omc

5) Assign the authority of accessing the directory to the user omc: chown omc:

omc /export/home/omc

The setting method of ftpuser user and omclog user are the same as that of omc user. All installation procedures below are implemented under omc user environment.

2.2.2.2 Installation procedure

1. File copying

1) Copy the server software package “omc20.xxxx-sparc.tar.Z” of the OMCR

(V2) software package to the directory specified by the environmental

variable OMCHOME.

2) Run the “uncompress omc20.xxxx-sparc.tar.Z” command to tar the software

package so as to create the “omc20.xxxx-sparc.tar” file.

3) Run the “tar –vxf omc20.xxxx-sparc.tar” command to install the software

package in the OMCHOME directory. Note that the key files should be

backed up beforehand because the previous directory will be overwritten if it

exists.

2. Write environment variables


Page 15 of 516

Enter the HOME directory via the user omc and edit the profile file of the user via “vi”. Add the following contents in the file. Then save and exit.

OMCHOME = /export/home/omc

export OMCHOME

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib:$OMCHOME/lib

export LD_LIBRARY_PATH

PATH = $PATH:$OMCHOME/bin

export PATH

OMCLOCALE=CHINESE

export OMCLOCALE

3. Write the Config. file

1) ampcfg.ini

A. Section name: MODULE

MaxModule indicates the number of modules in the system. Currently, there

are three modules. The number of modules can be extended, with the value

range being: 0 ~ 3. The default value is 0.

ModuleX indicates the module name. The value of X is less than or equal to

MaxModule, and is not allowed to repeat within a section.

B. Section name: LOAD

MaxLoad indicates the number of modules to be loaded for the server, with

the value range being: 0 ~ MaxModule.

LoadX indicates the module list to be loaded for the server. The value of X is

less than or equal to MaxLoas and is not allowed to repeat within a section.

C. Section name: COMMON

MaxProcess indicates the number of processes in the module, with the

value range being: 0~255.

The value format of ProcessX is: “process mapping name + predefined


Page 16 of 516

process No. + time delay constant”, which represents the loaded process

information. The value of X should be less than that of MaxProcess, and it is

now allowed to repeat within the module. The number must be equal to the

set value of MaxProcess. The predefined process No. and the time delay

constant are optional. The predefined process No. indicates the allocated

process No. after the process is loaded. If the process No. is not specified, it

will be allocated by the system after the process is loaded. The time delay

constant decides the time delayed to load the next process of the module

after the current process is successfully loaded. The time delay constant

should start with “D”. If not specified, the time delay constant is 0.

D. Section name: Application module

ModuleNo is the module No., and must be consistent with that of the

corresponding item in the [MODULE] section.

MaxProcess indicates the number of processes in the module, with the

value range being: 0 to 255. The default value is 0.

ProcessX indicates the information of the loaded process. The value of X

should be less than or equal to that of MaxProcess and is not allowed to

repeat with the module. The number of this item must be equal to the set

value of MaxProcess. For the value format, please refer to the description in

the [COMMON] section.

MaxTakeover indicates the number of other modules that can be taken over

by the module. It is used for migration and the value range is: 0 to

[MODULE]/MaxModule. The default value is 0.

TakeoverX indicates the names of modules that can be taken over. The

value of X is less than or equal to that of Takeover and is not allowed to

repeat.

E. Section name: PARAMETER

AmpBCInterval indicates the broadcasting interval between the AMP

machines (in 100ms).

ModuleNoackTimeout indicates the module response timeout between the

machines (in 100ms).

ModuleLoadTimeout indicates the module loading timeout (in 100ms).

ModuleLoadTimeout indicates the module unloading timeout (in 100ms).


Page 17 of 516

PsTestTimeout indicates the process test timeout (in 100ms).

PsUnloadTimeout indicates the process unloading timeout (in 100ms).

PsTestInterval indicates the process test interval (in 100ms).

PsTestRetry indicates the retry times of testing the process.

PsShutdownTimeout indicates the process shut-down timeout (in 100ms).

PsLoadTimeout indicates the process loading timeout (in 100ms).

PsTestEnable indicates the process test enable switch.

F. Configuration example

[MODULE]

MaxModule = 3

Module1 = COM

Module2 = DB

Module3 = AP

[LOAD]

MaxLoad = 2

Load1 = DB

Load2 = COM

Load3 = AP

[COMMON]

MaxProcess = 1

Process1 = GPO 1

[COM]

ModuleNo = 1

MaxProcess = 6

Process1 = MPCOMM 2

Process2 = CCF D10

Process3 = MPAC


Page 18 of 516

Process4 = PMONLAF

Process5 = AGT

Process6 = BAF

MaxTakeover = 2

Takeover1 = DB

Takeover2 = AP

[DB]

ModuleNo = 2

MaxProcess = 1

Process1 = DIF

MaxTakeover = 1

Takeover1 = COM

[AP]

ModuleNo = 3

MaxProcess = 1

Process1 = MPAA

Process2 = ACF D10

Process3 = LMF 4 D10

Process4 = SMF

Process5 = MCM

Process6 = FMDISP

Process7 = FMRELATE

Process8 = FMFILTER

Process9 = FMDBM

Process10 = TOPM

Process11 = DIAGLMF

Process12 = OPMADMD


Page 19 of 516

Process13 = PMONLMF

MaxTakeover = 0

[PARAMETER]

AmpBCInterval = 30

ModuleNoackTimeout = 90

ModuleLoadTimeout = 1200

ModuleUnloadTimeout = 1200

PsTestInterval = 100

PsTestRetry = 3

PsUnloadTimeout = 800

PsShutdownTimeout = 300

PsLoadTimeout = 50

F. Description of the example

As this configuration file is the configuration scheme for the standalone

server, all the migration parameters in the configuration file are invalid.

The configuration file defines the OMCR system. It includes three logical

modules altogether, which are COM module, DB module and AP module.

This machine is loaded with all three modules and one common module. Of

which, the common module include one process GPO. The process No. is

fixed as 1 after the loading.

COM module No. is 1. COM module comprises 6 processes altogether,

which are: MPCOMM, CCF, MPAC, PMONLAF, AGT and BAF in sequence

of the loading. MPCOMM is started via Process 2. MPAC is started one

second later after the CCF is successfully started.

DB module No. is 2. It comprises one process DIF in total.

AP module No. is 3. It comprises 13 processes in total, which are MPAA,

ACF, LMF, SMF, MCM, FMDISP, FMRELATE, FMFILTER, FMDBM, TOPM,

DIAGLMF, OPMADMD and PMONLMF in sequence of the loading. LMF

needs to be started via Process 4 one second later when ACF is

successfully started. SMF needs to be started one second later when LMF


Page 20 of 516

is successfully started.

The running parameters of AMP are described as follows: The heart-beat

test period among the AMP multi-servers is 3 seconds; no response timeout

of the logical module among the multi-servers is 9 seconds; both the loading

and unloading timeout of the logical module are 120 seconds; the process

test period within the server is 10 seconds; the retry times for the process

test failure are 3; the unloading timeout of a single Daemon process is 80

seconds; the shutdown timeout of a single process is 30 seconds; the

loading timeout of a single process is 5 seconds.

2) syscfg.ini

A. Section name: LOCAL

”Server” indicates that this configuration file is used for the server or the

client. It shall be set to 1 for the server, and set to 0 for the client.

Mno indicates the machine No. to uniquely identify one machine in the

network management system (NMS).For Server: 128 ~ 139; for Client:

0~255.

The nmdomain indicates the network management domain, used to identify

a set of NMS. The machine No. of different NMSS may be the same.

The ip indicates the IP address of the machine.

B. Section name: SVRINFO (This section is invalid at the server)

The svrnum indicates the number of servers in the system.

The svrmno1 indicates the machine No. of Server 1.

The svrip1 indicates the IP address of Server 1.

The svrmno2 indicates the machine No. of Server 2.

The svrip2 indicates the IP address of Server 2.

C. Section name: PROCESSNAME

Process mapping name is used to set the information of the process when

being loaded. The process mapping name is not allowed to contain more

than 8 characters. The parameters of the command line are described as

follows:

Item Default value Description


Page 21 of 516

-C 100 Allowable max. number of the consumer threads within the

process

-A 0 Size of the signal pool for the thread-level synchronous

invoking

-M 128 Size of the mailbox of internal AMPA in the process

D. Section name: SYSCFG

The trace indicates whether to record the debugging information in the LOG

file. 1 stands for Yes, and 0 for No.

The traceprint indicates whether to print the debugging information on the

screen or not. 1 stands for Yes, and 0 for No.

The tracemode indicates the output mode of the debugging information. 1

means to store all the debugging information in the same file (tracelog), 2

means to respectively output the debugging information according to the

process name.

The tracepath indicates the output path of the LOG file. If it is null, the

output is to the current path.

The cmdlogfile indicates the path for storing the client command record file

(used at the client).

Environment indicates the current environment of the OMCR (V2) system.

GSM indicates that the OMCR (V2) system is used in the GSM environment

and GPRS indicates that the OMCR (V2) system is used in the GPRS

environment. As some windows are different in different environments, the

graphics shown in the two environments will be separately listed in this

manual.

E. Section name: AMPACFG

FsmTestInterval indicates the Finite State Machine (FSM) test time interval,

with the value range being: 0~0xffffffff. The default value is 200 (in 100ms).

FsmTestRetry indicates the FSM test retry times, with the value range being:

0 to 5. The default value is 3.

AmpExist indicates the AMP existence flag (0 for the client). The value

range is: 0 or 1. The default value is 1.

FsmShutdownTimeout indicates the FSM shutdown timeout constant.


Page 22 of 516

AmpNoackTimeout indicates the AMP no response timeout constant (invalid

at the client).

FsmTestNumEach indicates the number of FSMs tested each time.

AmpDependence indicates whether the process exists depending on the

AMP. The value range is 0 or 1. The default value is 1.

FsmTestEnable indicates the FSM test enable flag. The value range is 0 or

1. The default value is 1.

F. Section name: CMISCFG

TraceCode is the flag of displaying the encoding and decoding bit stream.

The value range is 0 or 1. The default value is 0.

TraceErrorCode is used for debugging to output the errored bit stream. The

value range is 0 or 1. The default value is 0.

MANumber indicates the number of CMIPM channels of LMF-LAF. The

value range is 1 ~ 10. The default value is 1.

AANumber indicates the number of CMIPM channels of LAF-LAF. The value

range is 1 ~ 10. The default value is 1.

ABNumber indicates the number of CMIPM channels of LAF-BAF. The

value range is 1 ~ 10. The default value is 1.

G. Section name: MITCFG

LoadLevel indicates the layer at which the AGT starts to load the data.

The value range is 1~255. The default value is 4.

MoThreshold indicates that the multi-threads should be adopted to load

the data if the number of MOs in the database exceeds the specified

value when the AGT starts to load the data. The value range is 1~255

and the default value is 4.

H. Configuration example (syscfg.ini used by the server)

[LOCAL]

server = 1

mno = 129

nmdomain = 2


Page 23 of 516

ip = 138.1.20.11

[PROCESSNAME]

GPO = gpo

MPCOMM = mpcomm

CCF = ccf

DIF = difsvr

ACF = acf

BAF = baf

bafctrl = bafctrl

LMF = lmf

AGT = agt -dbg -C1024 -M1024

MCM = cmproc

SMF = fakesmf

MPAC = mpac

MPAA = mpaa

DIFPROC = difproc

TOPM = topm

FMFILTER = fmfilter

FMRELATE = fmrelate

FMDISP = fmdisp

FMDBM = fmdbm

DIAGLMF = diaglmf

OPMADMD = opmadmd

[SYSCFG]

trace = 1

traceprint=1

tracemode=2


Page 24 of 516

tracepath=

showeventmap=0

[AMPACFG]

FsmTestInterval = 200

FsmTestRetry = 3

FsmShutdownTimeout = 300

FsmTestNumEach = 20

AmpExist = 1

AmpNoackTimeout = 1000

AmpaTrace = 0

[CMISCFG]

#TraceCode = 1

TraceErrorCode = 1

#CMIPM channel number configuration: MA stands for LMF-LAF, AA for

LAF-LAF and AB for LAF-BAF.

#MANumber = 2

#AANumber = 2

#ABNumber = 2

[MITCFG]

LoadLevel = 4

MoThreshold = 500

I. Description of the syscfg.ini example at the server

Machine No. of the server is 129, the IP address is 138.1.20.11 and the

network management domain where the server resides is 29.

The debugging record will be written into the file (stored at the current

directory) according to the process, and will be shown on the screen

simultaneously. The message mapping will not be shown.

The FSM test time interval within the process is 20 seconds. The test retry

times is 3. The FSM shutdown timeout is 30 seconds. The number of FSMs


Page 25 of 516

tested each time is 40. The AMP no response timeout is 100 seconds.

The errored bit stream is shown. The number of CIMPM channels is 1.

The AGT starts to load the data at layer 4.

J. Configuration example (syscfg.ini used in the client)

[LOCAL]

server = 0

mno = 224

ip = 138.1.3.154

[SVRINFO]

svrnum = 1

svrmno1 = 129

svrip1 = 138.1.20.11

[PROCESSNAME]

GPO = gpocc.exe

WAF = wafc.exe

MKF = mkfc.exe

TESTTOOL = CliWin.exe

SOFTLOAD = swwsf.exe

RADIORESOURCE = rrcwsf.exe

ALARM = fmwsf.exe

DIAGTEST = diagwsf.exe

PERFORMANCE = wpmadmx.exe

PERFORMANCEAN = pap.exe

TRACE = ivktrc.exe

OPLOG = logop.exe

AUTH = smclient.exe

DATABASEMONI= pmonwsf.exe


Page 26 of 516

[SYSCFG]

trace = 1

cmdlogfile = e:\OMCHOME\Client\dat\cmd.log

[AMPACFG]

FsmTestInterval = 1000

AmpExist=0

K. Description of the syscfg.ini example at the client

Machine No. at the client is 224. The IP address is 138.1.3.154.

The client is connected with the server whose machine No. is 129 and IP

address is 138.1.20.11.

The path for storing the client command record file is

e:\OMCHOME\Client\dat\cmd.log.

3) bscfg.ini

A. Section name: GENERAL

BSCNum indicates the number of BSCs managed by the OMC-R.

B. Section name: BSCi, where the value of i is from 1 to n.

BSCID is the identity of BSC, which must be consistent with that configured

at the BSC.

IsRemote shows the physical location of the BSC relative to that of OMC-R,

based on the central module.

ModuleNum indicates all modules of the BSC (including the central and

peripheral modules).

LocalModuleNum indicates the number of local modules of the BSC.

Ipj (the value of j is 1 ~ m, where m is the module identity) indicates the IP

address of MP at each module. The previous one is for the left MP and the

later one is for the right MP.

BmfRecePno indicates the No. of the foreground receiving process.

BmfSendPno indicates the No. of the foreground sending process.

ModuleIDj (the value of j is 1 ~ m, where m represents the number of


Page 27 of 516

modules) indicates the information of each module. The first module must

be the central module, namely, the module No. is 1.

C. Configuration example

#GENERAL section stores the general information of OMC-R.

[GENERAL]

# The number of BSCs managed by the OMC-R.

BSCNum = 2

# The name of each section in the following respectively indicates BSC1 ~

BSCn.

#BSC1: example, for local BSC, all modules are local.

[BSC1]

#BSC ID is the identity of BSC, which must be consistent with that

configured at the BSC.

BSCID = 55

# Show the physical location of the BSC relative to that of OMC-R, based on

the central module.

IsRemote = 0

# The number of all modules at the BSC (including the central and

peripheral modules).

ModuleNum = 4

# The number of local modules at the BSC

LocalModuleNum = 4

# The IP address of the Main Processor (MP) at each module: the previous

one is for the left MP and the later one is for the right MP.

# As all modules are local, their IP addresses should be in the same

network segment with that of OMC-R.

IP1 = 192.200.73.21 192.200.73.119

IP2 = 192.200.73.4 192.200.73.19

IP3 = 192.200.73.8 192.200.73.38


Page 28 of 516

IP4 = 192.200.73.17 192.200.73.77

# Numbers of the foreground sending and receiving processes

BmfRecePno = 90

BmfSendPno = 91

# Information of each module. The first module must be the central module,

namely, Module No. is 1.

ModuleID1 = 1

ModuleID2 = 3

ModuleID3 = 8

ModuleID4 = 5

#BSC: The remote BSC of the three modules

[BSC2]

BSCID = 10

IsRemote = 1

ModuleNum = 3

# The local module is unavailable for the remote BSC. This item must be 0.

LocalModuleNum = 0

# It is only necessary to write the IP address of the central module for the

remote module. This IP address is not allowed to be in the same network

segment with that of OMC-R to facilitate the IP routing.

IP1 = 192.89.89.89 192.89.89.90

BmfRecePno = 90

BmfSendPno = 91

ModuleID1 = 1

ModuleID2 = 5

ModuleID3 = 2

D. Description of the example

Two BSCs are configured in this example. BSC1 is the local BSC and BSC2


Page 29 of 516

is the remote BSC. The lines starting with the “#” symbol are the comment

line.

4) dbcfg.ini

A. Section name: SPACE

MAXSERVERCACHETIME indicates the Max. cache time requested by the

server (in seconds).

MAXQUERYCACHETIME indicates the Max. holding time of querying the

cache (in seconds).

MAXSERVERWAITTIME indicates the Max. wait time for the server

execution (in seconds).

MAXQUERYRESULTTIME indicates the Max. holding time of querying the

result (in seconds).

B. Section name: ALARM

ALMDIFSERVERABANDON indicates the service abandon request

proportion alarm threshold (permillage).

ALMDIFQUERYABANDON indicates the query abandon request proportion

alarm threshold (permillage).

ALMDIFSERVERFAILURE indicates the service failure request proportion


ALMDIFQUERYFAILURE indicates the query failure request proportion


DBCFGREMAINSPACE indicates the alarm threshold of the remaining

space for the configuration table.

DBCFGREMAINPROP indicates the proportion alarm threshold of the

remaining space of the configuration table.

DBALMREMAINSPACE indicates the alarm threshold of the remaining

space of the alarm table.

DBALMREMAINPROP indicates the proportion alarm threshold of the

remaining space of the alarm table.

DBPFMREMAINSPACE indicates the alarm threshold of the remaining

space of the performance table.


Page 30 of 516

DBPFMREMAINPROP indicates the percentage threshold of the remaining

space proportion alarm of the performance table.

C. Section name: SESSION

IND_SESSIONNUM indicates the number of connections of the

independent (non-transaction) database.

TRANS_SESSIONNUM indicates the number of connections of the

transaction database.

D. Section name: DELAY

PRE_PROC_DELAY indicates the time delay before the DIFSVR FSM

starts several DIFPROC FSMs.

PROC_INTERVAL_DELAY indicates the time delay when the DIFSVR FSM

starts the DIFPROC FSM.

INIT_CONFIG_FILE indicates the file-writing flag of the initial configuration.

E. Section name: DATABASE

DBMSTYPE indicates the database type.

DBINSTANCE indicates the database instance No.

DIFVERSION indicates the DIF version No.

DIFVERSION indicates the database version No.

USERNAME indicates the user name used to connect the database.

PASSWORD indicates the password used to connect the database.

F. Configuration example

[SPACE]

MAXSERVERCACHETIME = 50

MAXQUERYCACHETIME = 200

MAXSERVERWAITTIME = 50

MAXQUERYRESULTTIME = 200

[ALARM]

ALMDIFSERVERABANDON = 50

ALMDIFSERVERFAILURE = 50


Page 31 of 516

ALMDIFQUERYFAILURE = 50

DBCFGREMAINSPACE = 10

DBCFGREMAINPROP = 85

DBALMREMAINSPACE = 10

DBALMREMAINPROP = 85

DBPFMREMAINSPACE = 10

DBPFMREMAINPROP = 85

[SESSION]

IND_SESSIONNUM = 3

TRANS_SESSIONNUM = 3

[DELAY]

PRE_PROC_DELAY = 0

PROC_INTERVAL_DELAY = 5

INIT_CONFIG_FILE = 0

[DATABASE]

DBMSTYPE = ORACLE

DBINSTANCE = OMC

DIFVERSION = V1.0

USERNAME = omc

PASSWORD = omc

G. Description of the example

The max. cache time of the service request is 50s; the max. waiting time for

the service execution is 50s; the max. holding time of querying the result is

200s; the alarm threshold of the service abandon request proportion is 5%;

the alarm threshold of the service failure request proportion is 5%; the alarm

threshold of query failure request proportion is 5%; the number of

connections of the independent database is 3; the number of connections of

the transaction database is 3; the database type is ORACLE; the database

instance No. is OMC; the DIF version No. is 1.0; the user name of


Page 32 of 516

connecting the database is OMC; the password for connecting the database

is OMC.

H. Description

The dbcfg.ini is the configuration file of the database, which stores the

database user and the password, and which can only be read by the

authorized system administrator.

4. Run the database setup script in the sqlplus

@/export/omc/sql/setup.sql parameter1 parameter2;

Where: parameter1 indicates the directory where the setup.sql script is

stored, such as /export/omc/sql/; parameter2 indicates the data file path of

the database, such as /export/oracle/omcdb/.

2.2.2.3 Installation check

1. Directory structure

After the installation is completed, there is the following structure under the OMCHOME directory of OMCR (V2) server:

OMCHOME: System initial directory, usually corresponding to /export/home/omc directory

bin: System executable file directory

lib: System dynamic link library directory

conf: System configuration file directory

Chinese: Special Chinese configuration file required for internationalization

English: Special English configuration file required for internationalization

dat: System data file directory

rlog: Directory to store system operation log

omcboot: Directory to store system boot script


Page 33 of 516

utility: Directory to store some system tools

locale: Internationalized resource directory

Chinese: Chinese resource

English: English resource

tmp: System temporary file directory

ftp: Directory used by the ftp client

log: Directory to store LOG file (changeable)

pmmeas: Directory to store the files reported by the foreground performance data (changeable)

2. Running environment

Run the “echo” command to check whether such environmental variables as OMCHOME, PATH, LD_LIBRARY_PATH are properly configured according to the above directory structure, e.g. echo $OMCHOME. Run the “vi” command to check whether the configuration files such as syscfg.ini, ampcfg.ini, lmfcfg.ini, dbcfg.ini and bsccfg.ini are correctly set according to the OMCR (V2) server and the actual situations of BSC MP, e.g. vi syscfg.ini.

2.3 Client installation

This part introduces the installation of the OMCR (V2) client. One mobile office can be configured with multiple clients, supporting OMCR (V2) multi-terminal operation. OMCR (V2) client installation is performed under NT environment. Before it is started, first install Windows NT and Excel.

2.3.1 Software requirements

The client has the following requirements on system software and machine performance:

1. OMCR (V2) client program.

2. Microsoft Windows NT Workstation 4.0 (or Windows 2000


Page 34 of 516

professional Edition).

3. To install Windows NT 4.0, Microsoft Windows NT Service Pack 4 or higher version is required.

4. A space of at least 50MB is required for client program and help file Help file can be installed in another directory. More disk space will be needed during operation.

5. 64MB memory is required for program running, and 128MB or more is recommended.

6. Before installing OMCR (V2) client program, please properly install NT Workstation and Excel in Microsoft Office first.

2.3.2 Installation procedure

The client is installed after Windows NT and Service Pack 4 have been installed, and the server should be also installed. Also ensure that the client setup tool and the client software are in the directory of the same level.

The installation of the client in the OMCR (V2) system should be conducted on the basis of the wizard mode. Click setup.exe to enter the language selection window shown in Fig. 2-1.

Fig. 2-1 Client setup wizard 1

Select Chinese to install the client of Chinese version; select U.S. English to install the client of English version. After selecting the necessary language, click <OK> to pop up the window shown in Fig. 2-2.


Page 35 of 516


Click <Next> to pop up the window of entering the machine No., as shown in Fig. 2-3.


Input the machine No. of the local host, with the value range of 140 ~ 254. Click <Next> to enter the window of inputting the IP address of the local


Page 36 of 516

host, as shown in Fig. 2-4.


Check whether the displayed IP address is consistent with that of the local host. If not, manually change the IP address of the local host. Then click <Next> to pop up the window shown in Fig. 2-5.



Page 37 of 516

Input the client setup directory in the window. Click <Next> to pop up the window shown in Fig. 2-6.


Input the setup directory of the Help file. Click <Next> to start the setup program. Then the server setting window will pop up, as shown in Fig. 2-7.


Page 38 of 516


Add the configuration information of the server domain. Click <OK>, as shown in Fig. 2-8.


Select the restart computer item. Click <OK> to end the installation. After the computer is restarted, you can log on to the OMCR (V2) system and enter various operation/maintenance interfaces via the main interface for operation and maintenance.

2.4 Main interface

OMCR (V2) system main interface is a client process, and it is the process started most earlier by the client. It mainly implements the following functions:

1. Establish the session with server application. Realize user logon and obtain information from server after logon succeeds.

2. Disconnection. Realize the process for the user to exit the whole system.

3. Realize main interface application of the client, providing graphical interface to operation user for convenient and quick operation of the OMCR (V2) system. The main interface shows the basic configuration of the system in the topology mode. The user can also activate the appropriate application module via the menus in


Page 39 of 516

the main interface (e.g. configuration management, alarm management, performance management, security management and tool management} or start the character terminal.

4. Special protection for client and server application link.

2.4.1 User logon

From the point view of the system security, if the user intends to enter the system, he should first log on to the system to be authenticated so as to ensure that only a legal user can execute the authorized operation. If the user name and the password are verified to be correct, the user will be allowed to enter the OMCR (V2) system. Otherwise, the system will prompt the user for the login failure and the user will be refused to enter the OMCR (V2) system. After the system is logged on successfully, it will obtain relevant topology tree information, interface configuration information and command syntax structure table information required for syntax check, alarm code information and error message code from the server, then the enter OMCR (V2) system main interface.

Please note that one user on the client can only log on the system with one identity at the same time.

In the WINDOW NT desktop, double click the icon of starting the OMCR (V2) system to enter the system. First the user will enter the system logon interface, where he is requested to input the user name and password. The logon interface is shown in Fig. 2-9.

Fig. 2-9 System logon

User name: It is required to input 3~20 visible characters (including uppercase and lowercase letters, figures and underlines. The name shall contain 3 characters at least, and 20 characters at most. It must start with


Page 40 of 516

a letter.)

Password: It is required to input 6~10 visible characters (including uppercase and lower case letters, figures and punctuation marks. The password shall contain 6 characters at least and 10 characters at most. )

“OK” button: Click this button to establish the link between client and server. If the link is successfully created, it will enter the main interface (as shown in Fig. 2-10). Otherwise, it prompts “System login failure! Please try again!”. The cursor will focus on the position of inputting the user name.

“Cancel” button: Click this button to exit the process of the main interface.

“Help” button: Click it to enter the help system of OMCR (V2) system.

2.4.2 Main interface

The main interface is as shown in Fig. 2-10 after a successful login. The main interface provides graphical interface and displays system basic configuration information in topology map or map for users’ convenient and quick operation of this system. Through the main interface, the user can enter the corresponding application module interface as desired (e.g. configuration management, alarm management, performance management, security management and tool management} or start the character terminal.


Page 41 of 516

Fig. 2-10 The main interface

System topology map is displayed on the main interface, so users can learn about the current configuration of the system clearly. The smallest nodes on the topology map indicates BTSs, and each BSC has a base station icon to represent all the BTSs under it. Double click a BTS icon to pop up the interface for displaying all BTS configurations under the BSC, as shown in Fig. 2-11.


Page 42 of 516

Fig. 2-11 BSC – BTS topology map

The OMCR (V2) nodes on the main interface topology map indicate the link states between OMCR (V2) server and various modules of the BSC managed by it.If one link disconnects, the node will flash. If all the links are normal, the node will not flash. Right click the node to display the link states between the server and all modules of the BSC, as shown in Fig. 2-12.


Page 43 of 516

Fig. 2-12 Link state display

There is a menu bar under the system topology map, which contains the following menus:

1. Configuration management: Includes radio resource management, software loading, dynamic data management and integrated configuration management;

2. Fault management: Includes alarm management and test management;

3. Performance Management: Includes performance management, performance analysis console, invoke trace and signaling trace.

4. Security management: Includes operation log management and user management;

5. System Tools: Include character terminal, database configuration and monitoring, refresh, and background selection.

6. Help: OMCR (V2) Help, Directory and index, About OMCR (V2).

7. Exit.

Users may select the desired menu item to enter the corresponding man


Page 44 of 516

machine interface for operation and maintenance. Click “Character terminal” under “System Tools” to enter the character command inputting mode, which is used for inputting MMI man-machine commands. In this case, the window is blank. Meanwhile, the command result will be shown. The command equals to the operation on the man-machine window, with the same effects of the command box at the bottom of the man-machine interface. “Refresh” under "System Tools" is used to refresh the contents displayed on the main interface. “Background selection” under “System Tools” is used to select different background settings so as to change the background shown on the main interface.

The system will perform special processing under some special situations. As for the normal disconnection, such as the interruption due to the server migration or physical causes, the main interface will automatically re-establish the link and prompt the user about this. The user need not log in to the system again. The main interface will also monitor the service process at the client and handle the abnormal service process so as to realize the system security and the normal shutdown.

2.4.3 Exiting the system

To exit OMCR (V2) system, click “Exit” on the menu bar of the main interface. The main interface process will disconnect all application links and pop up a prompt box. Click <OK> to exit the system, as shown in Fig. 2-13.


Page 45 of 516

Fig. 2-13 Exit the system


Page 46 of 516

3 Security Management

Security management includes user access security and network security. The final requirement on the user access security is that only users with legal identities and network resources access rights can access the network resources. The requirements can be classified into identification, access right verification, illegal access reject, etc. The network security includes two aspects: network transmission security and network node security. The network transmission security includes prevention of the data transmitted on the network from being eavesdropped, intercepted, modified or falsified. The node security includes the application process security and the protection of the data integrity. In conclusion, security management includes the following four parts: user access control, network transmission security, application process security and data integrity control.

Security management involves user management and operation log modules on the background workstation. User management is mainly used to set legal users and their corresponding operation/administration right, while operation log is used to record logon information and system fault detection.

3.1 User management

User management handles contents related to user right and network transmission security.

Users must have a certain right to perform the corresponding BSS and OMCR (V2) management operations.

3.1.1 Overview

OMCR (V2) user management module ensures management transaction processing security, including verification, access control and data consistency between systems, between system and client, and between system and internal users. The security system is divided into three levels: user, operation and managed object.


Page 47 of 516

User management function is a functional module in OMCR (V2) system, it handles contents related to user right and network transmission security.

According to different management functions and different management resource ranges, user management divides users into multiple user groups. User’s right can be organized by user group and role. Operations requiring verification are written into configuration files, if such operations are performed in the system, security management will authenticate them according to the configuration in configuration files.

First, rights of different users are organized via grant operations on the client using the user group and role. Then, different users log on from the client and perform various operations. Operation commands from the client are sent to LMF, which distributes them to various application modules for them to perform verification invoke, which then authenticate the operations according to user ID, operation and operated object and return the commands to the invoked modules.

The security management has four major function modules: Grant module, verification module, data management module and network transmission security module. The grant module mainly completes the grant function. The verification module mainly completes the verification function. The network transmission security module mainly completes the function of encrypting and decrypting information between the server and the client. The data management module mainly completes the secure data management and provides other modules with interfaces, so as to ensure the synchronization of the data in the memory and the database. Security management accepts security operation requests from various applications, and then handles them in the corresponding modules.

The grant module accomplishes the creation, modification, deletion and query function of OMCR (V2) user operation right information. The operated objects of grant include all manageable resources such as MO, user, user group, role, etc.

Operation verification module verifies each user operation to make sure that it is granted. Security verification includes user operation verification and compound command verification, the later of which is not available for now.


Page 48 of 516

Data management module mainly accomplishes the management of data in memory and database, including the creation, modification, deletion and query of security data, and provides data interfaces for other modules.

The objects of security management grant are user, user group and role. Granted objects include operated objects and special commands.

1. Role: A set of executable management operations. Role is a group unit of right. It can be granted directly. One role can contain other roles, but cyclic nesting (self-contain) is not allowed. Role’s right is the sum of direct rights and rights of all contained roles.

2. User group: User group is a set of a group of users. User group is also a set of roles. It can be granted directly. User group’s right is the sum of direct rights and rights of all contained roles.

3. User: system user with certain rights. Users cannot be granted directly, and one user has all rights of all user groups containing the user. Users are classified as local management users and non-management users. Local management users can modify the rights of other users. Non-management user cannot perform grant operations. User’s right is the sum of the rights of all user groups containing the user.

Granted objects include operated objects and special commands. The grant of operated objects is to define on which operated objects the operation can be performed. Since there is no operated object for special commands, the grant of special commands defines whether the command is available for use.

3.1.2 Operations of user management interface

3.1.2.1 Brief introduction to operations

After OMCR (V2) system is installed, a root user and some other default users are created automatically. If these users are not enough for actual application, corresponding adjustments and settings should be done with user management. The operation procedure is as follows:

1. Role setting: Create the role then add or delete rights of the role.


Page 49 of 516

2. User group setting: Create a user group, add or delete role in the user group, or directly add or delete right of the user group.

3. User setting: Create a user, then add the user into one or more user groups.

Rights already set can be checked, modified, added or deleted.

Only local management user with user management right can perform user management operations.

3.1.2.2 Entering the user management interface

After successful logon, select “Security Management” -> “User Management” on OMCR (V2) main interface to enter the user management interface, as shown in Fig. 3-1.

Fig. 3-1 User Management

On the interface from the top down, there are menu bar, tool bar, display column and command box.

The menus on the menu-bar are:


Page 50 of 516

1. File: Create User Wizard and Exit.

2. Operation: Create User, Delete Use, Modify User Attribute, Grant Attached User Group, Create User Group, Delete User Group, Modify Group Attribute, Role Grant of User Group, User Group Grant, Create Role, Delete Role, Modify Role Attribute, Role Grant of Role and Role Grant.

3. View: Toolbar, Status Bar, Command Box, Refresh, Operation, Operated Object.

4. Help: OMCR (V2) Help Topic, Directory and Index, About OMCR (V2).

From left to right, the buttons on the toolbar in turn are: User Group Grant of the User, User Group Role Grant, Role Grant, User Group Grant, Role Grant, Refresh, Help and Exit. The buttons on the toolbar correspond to the menus in the menu bar.

The left list in Fig. 3-1 displays the tree view of all current users, user groups and roles. The list on the right displays user group information of the user, role information of the user group or role information of the role and right information of the operated object.

The user can directly input the MML command in the command box to complete an operation. When the operation is performed at the interface, the relevant MML command will be displayed in the command box. It is necessary to point out that, except the compound command, only the command related with the user management can be input in the user management application window.

Since there are other terminals operating user management, the display can be refreshed in order to display the current user management information in real time. The procedure is as follows: select the menu item: View -> Refresh.

3.1.2.3 Role management

In Fig. 3-1, click “Role” in the left tree topology diagram to enter the “Role management” interface shown in Fig. 3-2.


Page 51 of 516

Fig. 3-2 Role management

The list on the right displays the names and descriptions of all current roles.

1. Create a role

In the main menu, select “Operate → Create Role” to pop up the “Create Role” dialog box, as shown in Fig. 3-3.

Fig. 3-3 Create a role

2. Modify a role

Select “Operation → Modify Role Attribute” in the main menu to enter

the “Modify Role” dialog box shown in Fig. 3-4. Then you can view or

modify the settings of the selected role in the dialog box.


Page 52 of 516

Fig. 3-4 Modify role

The “Modify Role” dialog box is similar to the “Create Role” dialog box, except that the role name cannot be changed.

3. Delete a role

In the main menu, select “Operation → Delete Role” to delete the role.

4. Role grant of the role

In the main menu, select “Operation → Role Grant of the Role”, as shown in Fig. 3-5.


Page 53 of 516

Fig. 3-5 Role grant of the role

5. Role grant

In the main menu, select “Operation →Role Grant”. The following scenarios exist:

1) Special command grant, as shown in Fig. 3-6.


Page 54 of 516

Fig. 3-6 Special command grant

2) Managed object grant, as shown in Fig. 3-7.

Fig. 3-7 Managed object grant


Page 55 of 516

3) Managed object type grant, as shown in Fig. 3-8.

Fig. 3-8 Managed object type grant

3.1.2.4 User group management

In Fig. 3-1, click “User Group” in the tree topology diagram on the left to enter the “User Group Management” interface shown in Fig. 3-9.


Page 56 of 516

F

Fig. 3-9 User group management

The list on the right displays the names and descriptions of all current roles.

1. Create a user group

In the main menu, select “Operation → Create User Group” to pop up the “Create User Group” dialog box shown in Fig. 3-10.

Fig. 3-10 Create user group

In the “Create User Group” dialog box, you can set the name of the new group and give a brief description. Once a group is created, its name cannot be changed unless it is deleted.

2. Modify a user group


Page 57 of 516

Select “Operation → Modify Group Attribute” in the main menu to enter the “Modify User Group” dialog box shown in Fig. 3-11. Then you can view or modify the settings of the selected user group in the dialog box.

Fig. 3-11 Modify user group

The “Modify User Group” dialog box is similar to the “Create User Group” dialog box, except that the group name cannot be changed.

3. Delete a user group

In the main menu, select “Operation → Delete User Group” to delete a user group.

4. Role grant of the user group

In the main menu, select “Operation → Role Grant of the User Group”, as shown in Fig. 3-12. The role grant of the user group can be carried out.


Page 58 of 516

Fig. 3-12 Role grant of the user group

3.1.2.5 User management

User refers to the legal operation/maintenance personnel that administrates and maintains the whole BSS LAN and OMCR (V2) system itself via OMCR (V2) system. User belongs to a user group, and has the operation/maintenance rights of the user group. One user may belong to one or more user groups.

The display column displays the logon names and descriptions of all legal users in list form:

User management involves operations such as create user, view, modify, and delete user information.

In Fig. 3-1, click “User” in the tree topology diagram on the left to view the user list shown in Fig. 3-13.


Page 59 of 516

Fig. 3-13 User management

The display column displays the names and descriptions of all current user groups.

You can perform operations such as create user, view, modify, and delete user information.

1. Create a user

In the main menu, select “Operation → Create User”, as shown in Fig. 3-14.

Fig. 3-14 Create user


Page 60 of 516

Input the user logon name, password and description, and select whether the user is a local administrator or not in the dialog box.

Input the logon password of the user and repeat it.

Input a brief description for the user.

User name and password format:

1) User name should consist of upper-case or lowercase letters, digits and

underlines, 3 characters at least, 20 characters at most, and must start with

letters.

2) Password should consist of upper-case letters, lowercase letters, digits and

punctuation marks, 6 characters at least, and 10 characters at most.

2. View and modify user information

Double click the user to be modified in the display column shown in Fig. 3-13 or select the user to be modified and click “Modify” button to enter the “Modify User” dialog box, as shown in Fig. 3-15. Then you can view or modify the settings of selected user in the dialog box.

Fig. 3-15 Modify a user

The logon name of the user cannot be modified. Yet the password and description of the user can be modified.

3. Delete a user

Select the user to be deleted on the user management interface shown in Fig. 3-13, then click “Delete” button to delete it.

4. Modify attached user group of the user


Page 61 of 516

In the main menu, select “Operation → Attached Group Grant”, as shown in Fig. 3-16.

Fig. 3-16 Attached user group grant

3.1.2.6 Viewing rights

1. View all operations

In Fig. 3-1, select “View → Operation” to enter all operation lists shown in Fig. 3-17.


Page 62 of 516

Fig. 3-17 View all rights

2. View all operated objects

Select “View -> Operated Object” in the main menu shown in Fig. 3-1, and a dialog box will pop up for you to select the operation code. Then all operations of the operation code will be displayed after selection, as shown in Fig. 3-18:


Page 63 of 516

Fig. 3-18 View operated objects

3.1.2.7 Creating the user wizard

In Fig. 3-1, select “File → Create User Wizard” to enter all operation lists shown in Fig. 3-19.


Page 64 of 516

Fig. 3-19 The wizard: select the operation function

Select the user-required functions to be created and select or not select “Full Control”, “Read”. Click “Cancel” to exit the wizard. Click “Next” to pop up the dialog box, then select ranges of the operated objects required by the user to be created. Only nodes in layer 1 and layer 2 of the topology tree can be selected, as shown in Fig. 3-20.

Fig. 3-20 The wizard: select the operated object

Then click “Cancel” to exit or select “Next” to pop up the dialog box of creating the user. After “Next” is selected in the dialog box of creating the user, the commands of creating the user and granting can be input.

3.2 Operation log

3.2.1 Overview

Operation log is used to record all operations initialized from the client and performed on the server, including operator, operation time and operation content. The interface of operation log on the workstation client provides log view for observing fault in time, tracing the modification of system parameters, and locating relevant responsible terminals and operators.


Page 65 of 516

3.2.2 Operations of the operation log interface

After successful logon, select “Security Management” -> “Operation Log” on OMCR (V2) main interface to enter the operation log interface (as shown in Fig. 3-21). Due to the large data size in operation log, users may use filter at startup to locate concerned records, or click “OK” button to view the latest 1000 records in the last week.

Fig. 3-21 Operation log main interface – initial filter

After “OK” is clicked in Fig. 3-21, the operation log main interface shown in Fig. 3-22 will appear.


Page 66 of 516

Fig. 3-22 Operation log main interface

On the interface from the top down, there are menu bar, tool bar, display column and command box.


1. Log: Open…, Save As…, Printer Setup…, Print…, Clear All Events, Exit.

2. View: All Events, Filter Events, Detailed Information, Toolbar, Status Bar, Command Box and Refresh.

3. OMCR (V2) Help Topic, Directory and Index, About OMCR (V2).

From left to right, the buttons on the toolbar in turn are: Open File, Save As…, Clear All Events, Detailed Information, Refresh, Cancel Log Query Operation, Help and Exit.

In the display column, the log information is shown in the list form. It includes: Start time, End time, Operation class, Command code, Operation status, Operator and terminal number.

Command box is the character input interface. The user can directly input the MML command in the command box to complete an operation. When


Page 67 of 516

the interface operation is performed, the relevant MML command will be displayed in the command box.

If filter event is selected, the system will first enter the dialog box shown in Fig. 3-23 to filter events, then enter the operation log main interface shown in Fig. 3-22 to display the log events that match the filter condition.

3.2.2.1 Viewing log

Multiple modes are provided in the menu for convenient viewing of log information.

1. View all events

Select menu “View -> All Events” to view all log information in the current database.

2. Filter Events

Filter events is to set log query condition. User may filter log information displayed on the interface to display the records that match the condition, while not matched records are not displayed on the interface. Select menu “View -> Filter Events”, and the “Filter” dialog box will pop up, as shown in Fig. 3-23.


Page 68 of 516

Fig. 3-23 Filter events

Events can be filtered by the combination of time, operation status, operator, operation terminal and operation class.

Begin time and end time can be set to display only the records between them. The first event of begin time refers to the earliest event in the current database, the last event of end time refers to the last event in the current database.

After the filter is confirmed, the display column on Fig. 3-22 operation log interface will display the log information that matches the filter condition.

3. View detailed information

The command code of log item is represented by code, and the detailed information in text form can also be displayed.

Select the desired log item in the display column shown in Fig. 3-22 operation log interface, double click it or select menu “View


Page 69 of 516

-> Detailed Information”, and the “Detailed Information” dialog box will pop up, as shown in Fig. 3-24.

Fig. 3-24 Detailed Information

Information description in text form is given on the lower part of the dialog box, including specific content of the MML command of the operation.

4. Refresh

New operation records will be produced along with the running of the system, so the display can be refreshed in order to display the current log information in real time. The procedure is as follows: select menu “View -> Refresh”.


Page 70 of 516

3.2.2.2 Log operation

1. Save log

All records displayed on the current interface can be saved into log files manually. This means that you can save all log information in the current database, or save log information in the specific period of specific class after filtering events, or save an opened log file as another log file with different file name.

Select menu “Log -> Save As…”, the “Save As” dialog box will pop up, as shown in Fig. 3-25.

Fig. 3-25 Save As

Select the directory to save the log file and input the file name, with “save as type” being *.zlg file.

The “Save As” dialog box adopts WIN WORD style, same as all that in OMCR (V2) system, only the “Save as type” is different, so it is not described in detail here.

2. Open log

Opening log is used to open a log file.

Select menu “Log -> Open” or click “Open File” button on the tool bar, and the dialog box shown in Fig. 3-26 will pop up.


Page 71 of 516

Fig. 3-26 Open a log file

Select the desired log file and click “Open”. The “Open” dialog box adopts WIN WORD style, same as that in

OMCR (V2) system, so it is not described in detail here.

Detailed information of the log item displayed in the opened log file can be viewed.

For opened log file, select menu “View -> All Events” to reread the log database, display the current log, and auto close the log file.

3. Delete the log

Clearing all events is used to delete all operation log items from the database.

Select menu “Log → Clear All Events” to delete the log. Before the deletion, the dialog box shown in Fig. 3-27 will pop up and ask whether to save the contents currently displayed.

Fig. 3-27 Log deletion confirmation

To save the current contents, click “Yes” button, the “Save Log” dialog box will pop up to save the log fie.


Page 72 of 516

4 Fault Management

Fault management is one of the main management functions of a Telecom Management Network (TMN). In ZXG10-BSS system, for the sake of the normal operation and maintenance of the system, fault management detects, reports and processes the abnormality of a telecom network and its environment. And the functions of fault management are realized by means of fault alarm and alarm diagnosis.

1. Main functions of fault management

1) Alarm management: Alarm display and query, alarm rack diagram

management, unconfirmed alarm display in the audible and visual forms.

providing operations of query, addition, deletion, modification, enable and

disable according to various alarm rules (filter rule, re-classification rule,

correlation processing rule).

2) Alarm processing knowledge base management: It provides the ability to

query the alarm processing methods, according to the alarm code or alarm

reason code. And this function enables users to update and enrich this

database. This module is combined with other modules to provide services,

for example, alarm monitoring module.

3) Diagnosis test management: This module provides a diagnosis test

management interface, by means of which a user can make an instant test

task and scheduled test task, and modify, delete or suspend the routine test

task. And the user can also query, print test results, etc.

2. Main features of fault management

1) Real-time: monitoring the states and changes of NEs in the whole system

and reporting any abnormality in time.

2) Accurate: reporting abnormalities accurately, without any alarm unreported

or any false alarm.

3) Automatic: the system has the function of processing faults in somewhat

intelligent and automatic mode. Besides the mode in which an operator

gives the fault processing command, the system has partial capabilities of

automatic control, such as automatic fault isolation, prevention of faults from


Page 73 of 516

diffusing, starting of backup resource and automatic recovery.

4) Network-like: query, setting and command operations of multiple terminals

are made possible.

5) The system supports the operations of users in two modes: GUI and

character terminal.

4.1 Alarm management

Alarm management is to find any abnormality in network operation in time and accurately, locate, isolate and eliminate faults accurately based on observation and analysis of the status information reported by various NEs.

4.1.1 Overview

Alarm management implements alarm display, synchronization, query and man-machine command sending for BSS (including BSC and BTS). Alarm types include: equipment alarm, communication alarm, environment alarm, quality of service alarm, processing error alarm, etc.

For the sake of preventing alarm reports being lost when broken link occurs to a network unit and OMCR (V2), each BSC should be capable of keeping an alarm event for at least 3 days.

Alarm management provides users with a friendly operation interface on the client side and presents any information before them accurately, consistently and in real time. Alarm management can implement the following main functions:

1. Alarm display: displaying the current alarm in real time in the alarm main interface and unconfirmed alarms in audible/visible form. As long as there is enough authority, an alarm can be confirmed or cleared.

2. Alarm query: The history recovered alarm, current alarm or common notification can be queried as required.

3. Rack diagram management: displaying the alarm status of a rack diagram and board dynamically and visually, capable of updating


Page 74 of 516

the rack diagram based on event reporting and conducting man-machine command operations.

4. Alarm setting: providing the settings of various alarm rules (filtering rule, reclassification rule and correlation processing rule), trunk node alarm and environment alarm, making alarm display meet users’ needs and display fault causes more visually and providing correlated alarm query.

5. Management of alarm processing knowledge base: providing the capability of querying alarm processing methods based on an alarm code or alarm reason code and enabling users to update and enrich this database.

4.1.2 Classification of alarm information

From the angle of real-timeness, the alarm includes notification and alarm.

1. Notification

Notification refers to the unrepeatable or instant fault in the running process of BSS. Usually, the not-so-frequent notification may be caused by haphazard environmental factors, and the maintenance personnel do not need to conduct any processing; however, if the notification is frequent and lasts long, the maintenance personnel must track down the cause and solve it in time.

2. Alarm

The alarm may last for a period of time, and usually, affect the system’s normal services, maintainability and running reliability to different degrees; according to the severities, the alarm can be divided into four classes.

1) Class 1 alarm: Critical alarm, showing that normal services are affected and

need recovering immediately, for example, the complete interruption of an

MO service.

2) Class 2 alarm: major alarm, showing that there is sign of normal services

being affected and emergent recovery is needed, for example, serious

deterioration in the quality of service of a certain piece of equipment.


Page 75 of 516

3) Class 3 alarm: minor alarm, showing that there exist some factors not

affecting normal services and corrective measures should be taken lest that

more serious faults should occur.

4) Class 4 alarm: warning alarm, showing that there exist potential problems or

normal services will be affected, and some measures should be taken to

solve them lest that they become more serious faults that will affect normal

services.

The ongoing alarm is called the current alarm, the ended (recovered) alarm is called the history alarm.

For the alarm type, alarm class, alarm cause, notification type and notification cause, see Online Help.

Some alarms, such as timeout no report of boards and broken communication links, can be recovered in a certain period of time. A recovered alarm will be cleared in background display, but the alarm time and recovery time still exist in the alarm database. The maintenance personnel can query alarms by querying history alarms, thus facilitating the equipment maintenance.

Some alarms should be recovered manually if they cannot be recovered after a long time or need processing manually.

4.1.3 Operations of the alarm management interface


Real-time monitoring of alarms means displaying the current network alarm status in the form of an alarm list in the alarm main interface. This list can be sorted by alarm time or alarm class and will be refreshed automatically by the system once a new alarm occurs or an existing alarm is recovered.

Users can set alarm rules to make the alarm list display more flexible and more conformable to users’ needs. The setting of the alarm filter rule enables the user to select alarms that he wants to view in the alarm list. For example, he only wants to view certain MO alarms, certain specified types of alarms, certain levels of alarms, etc., alarms meeting specific conditions can be reclassified into a new alarm level by setting the alarm


Page 76 of 516

reclassification rule, so as to enhance or weaken alarms of this kind. The correlation rule between alarms can be found out by setting the alarm correlation rule, so as to find out the real fault source and reduce the alarm numbers shown to the user. These rules can be saved for future use. For a correlated alarm occurring in an alarm list, correlation query can be used to view the detailed information about this correlated alarm.

Besides real-time monitoring of alarms, alarms can be processed. As long as there is corresponding authority, alarms can be confirmed, printed or manually cleared.

And a rack diagram alarm interface can be used to view the alarm status of various boards on the rack and conduct man-machine command operations of various boards on the BSC rack.

Knowledge base management can be used to obtain the causes and corresponding processing methods of various alarms.

Query operations can be made to view a history alarm recovered, alarms not recovered currently or common notifications as required.

4.1.3.2 Entry to the alarm management interface

After successful login, users may select “Fault Management” —> “Alarm Management” in the OMCR (V2) main interface to enter the “Alarm Management” main interface (as shown in Fig. 4-1).


Page 77 of 516

Fig. 4-1 The main interface of Alarm Management


1. File: OK, Recover Manually, Query History, Correlation Query, Statistical Analysis, Database Management, Knowledge Base Management, Print and Exit.

2. Setting: Alarm Rule, Trunk Node Alarm, Environment Alarm, and Alarm Display Mode. Alarm Rule has the following submenus: Alarm Filter Rule, Alarm Reclassification Rule, Alarm Correlation Rule, and Alarm Forwarding Rule.

3. View: Detailed Information, Physical View/Logical View, Toolbar, Status bar, Command Box, Expand, Collapse, Expand All, Collapse All, and Refresh.

4. Help: Alarm Management Help, Directory and Index, About…

The tool bar includes most of the functions provided by the above mentioned menu items. The buttons from left to right in turn are: OK, Recover Manually, Query Historical Alarm or Notification, Correlation Query, Alarm Frequency Analysis, Database Management, Knowledge Base Management, Select Detailed Information of Alarm or Notification, Physical View/Logical View, Set Alarm Filter Rule, Set Alarm


Page 78 of 516

Reclassification Rule, Set Alarm Correlation Rule, Set Trunk Node Alarm, Set Environment Alarm, Display/Hide Command Box, Expand, Collapse, Expand All, Collapse All, Refresh, Help and Exit.

Under the tool bar, there are 3 counter displays, displaying respectively the current number of all alarms, current number of alarms within the last hour and current number of alarms within the last day. The format is: total numbers [Class 1 alarm/Class 2 alarm/Class 3 alarm/Class 4 alarm]. Asterisks are put before each alarm to indicate the alarm level and the quantity of the asterisks shows the alarm level: *** means class 1 alarm, ** means class 2 alarm, * means class 3 alarm, no asterisk means class 4 alarm. Note that the current number of alarms displayed in an alarm counter is not that displayed in the alarm list, but the number of alarms not recovered before correlation processing, including common alarms and source alarm generating correlated alarms, instead of the filtered alarms and the correlated alarms generated by source alarms.

On the left of the main window is a browse tree displaying system configuration, by means of which users can select nodes conveniently to view current alarms. The hierarchy is as follows: ZTE --- BSS--- BSC, BTS---Rack.

On the upper right of the main window is a current alarm list and real-time monitoring of alarms means displaying the current network alarm status in the form of an alarm list. The alarm list displays all the current alarms under the designated node in the browse tree, including alarm generation time, serial number, alarm source, alarm class, alarm location, alarm content, alarm cause and additional information. In the default case, alarms are displayed in the order of the time when they are generated and the display of users by class is supported. You may click the corresponding table heading to achieve sorting display. Once a new alarm occurs or an existing alarm is recovered, the system will automatically refresh the list and counter display.

The unconfirmed alarms in the alarm list are shown in the flashing mode. Click the “OK” button in the toolbar to confirm the setting. The confirmed alarms are shown in the non-flashing mode, which indicates that the operator has seen the faults.

Confirmed alarms will record the confirming operator and confirmation


Page 79 of 516

time.

For a selected alarm option, click the “Recover Manually” tool on the toolbar to clear it. An alarm, when cleared, will no longer be seen in an alarm list, but still will be saved in the alarm database for future query and view. A correlated alarm will be identified with “+” displayed before it. Users can open a correlated alarm explanation dialog box to view all source alarms and correlation rules by querying correlation. With enough authority, users can confirm or clear (namely, recover manually) a source alarm in this dialog box.

On the lower right of the main window is a notification list, displaying all announcement messages under the designated node in the browse tree, including the notification source, notification location, notification content, time of notification and additional information related to this notification. All notifications will be displayed based on the time when they are given. The unconfirmed notification is shown in the flashing mode. Click the “OK” button on the toolbar to confirm it. The confirmed notification will be cleared from the list automatically, but still saved in the alarm database for query and viewing.

Users can adjust as required the size of a notification list display window and that of an alarm list display window.

A command column is a character input interface. Users can directly input an MML command in the command column to perform an operation. During an interface operation, the corresponding MML command will be displayed in the command column. Note that besides compound commands, only the commands related to alarm management can be input in the application window of alarm management. Click the “Display/Hide Command Box” button on the toolbar to close the command window.

Select one alarm option or notification option in an alarm list or notification list and click the “Details” button on the toolbar or double click the selected alarm option or notification option. A dialog box (as shown in Fig. 4-2) will pop up, providing the detailed information about the selected alarm option or notification option. Press the “Previous” or “Next” button to display the detailed information about the previous or next of the selected alarm option or notification option given in the list.


Page 80 of 516

Fig. 4-2 Details

4.1.3.3 Rack diagram management

Alarm rack diagram management, in combination with alarm status, is responsible for real-time display and update of a rack diagram. The system can provide such racks as BSC (V2), BTS (V1A), microcell MB, BTS (V2) and outdoor BTS and different racks are provided with different slot numbers to identify their types and board display modes. A rack diagram displays the actual configuration of the boards in a system. The alarm status of a board will be displayed by means of each status indicator on each board, and various classes of alarms and normal status correspond to status indicators in different colors. When the status indicator on a board is in flashing status, it shows that currently an alarm occurs to the board and has not yet been recovered. The color of the status indicator corresponds to the highest class of the alarm occurring to the board.

Users can observe the status of a board in the rack diagram and confirm or clear unconfirmed alarms and alarms not cleared. And they can perform such man-machine command operations as active/standby changeover of a board on the BSC rack.

1. Rack diagram display;

Select the rack to be viewed in the browse tree or click the


Page 81 of 516

“Physical View” button on the toolbar in the case of BSC or BTS in the selected browse tree to enter the display interface of the alarm management rack diagram (as shown in Fig. 4-3).

Fig. 4-3 BSC alarm management rack diagram display

Shown in Fig. 4-3 is the rack diagram display of BSC alarm management. The rack diagram on the right side of the interface not only displays the rack running in the foreground in real time, but the color of the round status indicator on the board in the rack diagram also shows the status of the board: alarm or normal.

For the implications of various colors, please refer to the legend on the right of the rack diagram.

Warning:

1) When an alarm occurs currently to a board, the color of the alarm status

indicator is that of the alarm in the highest class.

2) When an unconfirmed alarm occurs to a board, its status indicator flashes.

The status indicator will not flash any more only when all the alarms of the

board are confirmed.

2. Man-machine command operations


Page 82 of 516

Users with corresponding authority can perform man-machine command operations on some BSC boards.

1) The man-machine commands of alarm management part are roughly

categorized based on functions as follows:

A. Query of board status

B. Changeover of the active/standby

C. Resetting

D. Offline and cancellation of offline (MP)

E. Changeover enable and changeover disable (SYCK)

F. Set clock reference (SYCK)

G. Set clock mode (SYCK)

H. Set periodic changeover and cancel periodic changeover (MP)

2) The boards that allow man-machine command operations and the

corresponding man-machine commands

Only the boards on the BSC rack allow man-machine command operations.

The boards that allow man-machine command operations and the

corresponding man-machine commands are as follows:

A. MP: (active MP) active/standby changeover, reset, (standby MP) offline,

(standby MP) cancellation of offline, (active MP) set periodic changeover,

cancel periodic changeover and query board status.

B. SMB, DRT, DTI: query board status, resetting.

C. SYCK: active/standby changeover, set clock reference, set clock mode,

changeover enable, changeover disable, query board status.

D. DSNI: board active/standby changeover

E. BOSN: active/standby changeover, resetting.

F. AIPP, BIPP, COMI, TCPP: query board status, active/standby changeover,

resetting.

G. TIC: reset, query board status.

H. PUC, GIPP, BRP, FRP, HMS, TIC (GPRS): query board status, resetting.

I. PUG, GIPP, HMS: active/standby changeover.


Page 83 of 516

3) Man-machine command operations

A. Query board status

This command is applicable to MP, SMB, DRT, DTI, SYCK, AIPP, BIPP,

COMI, TCPP, TIC, PUC, GIPP, BRP, FRP, HMS and TIC (GPRS).

Take MP for example. Right click the board on the BSC rack diagram and

select the “Query Board Status” option on the shortcut menu to pop up the

“Board Status” dialog box, as shown in Fig. 4-4:

Fig. 4-4 “Board Status” dialog box

Shown in the dialog box are board location, power-on time, changeover

times, and whether periodic changeover can be performed.

B. Switchover of the active/standby

This man-machine command is applicable to active MP, SYCK, BOSN,

DSNI, BIPP, AIPP, COMI, TCPP, PUC, GIPP and HMS.

Take MP for example. Right click the active MP board on the BSC rack

diagram and select the “Active/Standby Changeover” option on the shortcut

menu to implement active/standby changeover of the active MP.

C. Set periodic changeover

This man-machine command is only fit for the active MP.

Right click the MP board on the BSC rack diagram and click “Set Periodic


Page 84 of 516

Changeover” in the pop-up shortcut menu to pop up the dialog box of

setting board command parameters, as shown in Fig. 4-5.

Fig. 4-5 MP periodic changeover

D. Set the clock reference

This command is only applicable to SYCK boards. Right click the SYCK

board in the rack diagram and click “Set SYCK Clock Mode” in the pop-up

shortcut menu to pop up the dialog box of setting board command

parameters, as shown in Fig. 4-6. Select one reference from the existing

clock references as that of the SYCK board.


Page 85 of 516

Fig. 4-6 Set the clock reference of SYCK

E. Set clock mode

Setting a clock mode is applicable only to an SYCK board. Right click the

SYCK board in the rack diagram and click “Set Clock Mode” in the pop-up

shortcut menu to pop up the dialog box of setting board command

parameters, as shown in Fig. 4-7. Select one mode from the existing clock

modes as that of SYCK.


Page 86 of 516

Fig. 4-7 Set the clock mode of SYCK

F. MP offline and cancellation of offline

Offline and cancellation of offline are only fit for the standby MP. An offline

operation is generally used for maintenance.

After the standby MP is offline, the standby MP will not monitor the active

MP within 6 minutes. That is, the power-off of the active MP will not lead to

the standby MP being an active one. If the “offline” mode is not cancelled

after 6 minutes, the offline mode of the standby MP will be cancelled

automatically and change to the online status.

Right click the standby MP board in the BSC rack diagram, select “Offline”

in the pop-up shortcut menu and send the offline command of the standby

MP to the foreground after confirmation. The confirmation dialog box is

shown in Fig. 4-8:


Page 87 of 516

Fig. 4-8 Standby MP offline

Press “Yes” button to confirm offline, or press “Cancel” button to cancel the

offline operation.

When offline is to be cancelled in offline status, perform the same

operations as an offline operation.

Reset, changeover enable, changeover disable and cancellation of periodic

changeover need similar shortcut menus and confirmation operations before

they are sent to the foreground. Following will not reiterate this.

4.1.3.4 Alarm rule setting

Alarm rule settings include the setting of alarm filtering rules, that of alarm reclassification rules and alarm correlation rules.

The processing sequence of filtering, reclassification and correlation of the alarm is: First the filtering, then reclassification and finally correlation.

The setting of alarm rules is responsible for providing such operations as the query, addition, deletion, modification, enabling and disabling of various alarm rules (filtering rules, reclassification rules and correlation processing rules).

This section introduces the settings of various alarm rules and the correlated alarm query operation.

1. Setting of alarm filtering rules

For the sake of preventing some unimportant or uninteresting alarms from affecting a user’ line of sight and making really important alarms found in time, alarm filtering enables users to filter them and confirm them automatically.

Alarm filtering enables users to set an alarm as not being


Page 88 of 516

displayed in the alarm real-time observation interface (this will not result in the color change of any NE icon in the high layer interface) or not being written to an alarm database. The filtering conditions may be the filtering of a specific MO (a logic entity or physical entity), that of some alarm classes and that of some type of alarms. There are two forms of filtering: wirte into the database but not display it, neither writer into the database nor display it. Besides, a confirmation mode can be set and the confirmation dealt with here means to confirm that this alarm information has been read. Three confirmation modes can be set in the alarm filtering: unconfirmed, automatically confirmed upon receiving the alarm, automatically confirmed when the alarm is recovered

Click the “Set Alarm Filtering Rule” button on the toolbar to enter the “Alarm Filtering Rule Editor” dialog box (as shown in Fig. 4-9).

Fig. 4-9 “Alarm Filtering Rule Editor” dialog box

The buttons on the toolbar of the “Alarm Filtering Rule Editor” dialog box in turn are: Create Alarm Filtering Rule, Modify Alarm Filtering Rule, Delete Alarm Filtering Rule, Refresh Rule, Print Alarm Filtering Rule, About and Exit.

Below the toolbar, all current alarm filtering rules are listed in the form of a list. All rules in the active status are in application. Rules


Page 89 of 516

not in the active status do not work, but are only listed.

1) Create alarm filtering rule

Click the “Create Alarm Filtering Rule” button to enter the dialog box of

creating the filtering rule (as shown in Fig. 4-10).

Fig. 4-10 Create alarm filtering rule

First select the object on which a filtering rule is to act. The object of alarm

filtering and confirmation may be the following:

A. All alarms or designated alarms of a type of objects.

B. All alarms or designated alarms of a specific object.

C. Specific alarm codes.

E. Specific alarm classes.

Press “Rule Object…” button to enter the “Select Object” dialog box (as

shown in Fig. 4-11).


Page 90 of 516

Fig. 4-11 “Select Object” dialog box

Select from all the following object browse trees to display the selected

objects in the above single-line box. Press the “OK” button to confirm object

selection and return to the dialog box as shown in Fig. 4-10.

Then, select a filtering rule mode. There are four modes: Object, Object +

Alarm code, Object + Alarm class, Object + Inform code. If “Object + Alarm

code” is selected, the alarm code shall be selected in the alarm code box. If

“Object + Alarm class” is selected, the alarm class shall be selected.

Then, select a filtering mode. The alarm filtering is divided into in-database

filtering and display filtering. The in-database filtering indicates the alarm is

completely discarded, that is, the alarm does not go into the database and is

not processed in other forms. The display filtering only makes the alarm

invisible in the alarm list but the user can view the alarm information by

querying when necessary.

For display filtering, the selection of a confirmation mode is also necessary.

The confirmation dealt with here means to indicate that this alarm

information has been read. The confirmation modes include no confirmation,

confirmation of receiving and Clear confirmation. A confirmation mode can

be selected based on the importance of display-filtering alarm. An alarm


Page 91 of 516

after display filtering still can be queried and viewed. Unconfirmed filtering

alarm is in the unconfirmed status in query. It can be manually confirmed by

the users. Therefore, users can easily detect the occurrence of the alarm in

query, which can be used for important filtering alarm. Confirmation of

receiving means that the system confirms the receipt after receiving the

alarm, which can be used in unimportant filtering alarm. Clear confirmation

means that the system confirms the clearance automatically after the alarm

is recovered, which can be used in rather important filtering alarm.

Finally select a rule status. The rule status includes active and inactive, and

only those rules in active status can be applied.

Press the “OK” button to confirm a newly-created filtering rule and return to

the dialog box shown in Fig. 4-9. In this case, the created filtering rule will

be listed in the alarm filtering rule list.

2) Modify the alarm filtering rule

The alarm filtering rule already established can be modified, but the

modification is restricted to its filtering mode, confirmation mode and rule

status.

Select one filtering rule from the alarm filtering list and click the “Modify

Alarm Filtering Rule” button to enter the dialog box of editing the filtering

rule, as shown in Fig. 4-12.


Page 92 of 516

Fig. 4-12 Edit the filtering rule

3) Delete a filtering rule

Select the rule to be deleted in the alarm filtering list and press the “Delete

Filtering Rule” button to delete the selected rule.

4) Refresh rule

Because OMCR (V2) system supports multi-terminal operations, the

“Refresh Rule” button can be used to conduct a Refresh operation and

enable a list to display the current latest filtering rule in real time.

A new alarm, when filtered, can filter the alarm message of a database and

other messages are all sent to the alarm reclassification process for

processing. Because some of these alarms are not displayed, these

messages need distinguishing.

2. Setting of alarm reclassification rules

The alarm reclassification process is used to reclassify the alarms


Page 93 of 516

satisfying specific conditions to a new alarm class. This can be used to enhance or weaken this type of alarm. The conditions mentioned above can be: Designated alarm for a class of objects, designated alarm for specified objects and alarm of specified alarm code.

An alarm will be reclassified after the alarm is filtered. After an alarm is reclassified, both the new alarm class and the original one will be stored in the alarm database, but only the new alarm class after reclassification will be displayed in the alarm interface.

Click the “Set Alarm Reclassification Rule” button on the toolbar to enter the “Alarm Reclassification Rule Editor” dialog box (as shown in Fig. 4-13).

Fig. 4-13 “Alarm Reclassification Rule Editor” dialog box

The “Alarm Reclassification Rule Editor” dialog box is similar to the “Alarm Filtering Rule Editor” dialog box.

The buttons on the toolbar of the “Alarm Reclassification Rule Editor” dialog box in turn are: Create Alarm Reclassification Rule, Modify Alarm Reclassification Rule, Delete Alarm Reclassification Rule, Refresh Rule, Print Alarm Reclassification Rule, About and Exit.


Page 94 of 516

In the dialog box, all current alarm reclassification rules are listed in the form of a list. The states of the rules can be divided into two types: Activate and inactive. Rules in the active status are in the application. Rules in the inactive status do not work, but only are listed.

Click the “Create Alarm Reclassification Rule” button to enter the dialog box of creating reclassification rule (as shown in Fig. 4-14).

Fig. 4-14 Create reclassification rule

A reclassification rule alarm must satisfy the requirements of both an object and alarm code, but either an object or alarm code can be set when a reclassification rule is established.

If the “Rule Object” check box is selected, press the Rule Object…” button to enter the object selection dialog box (as shown in Fig. 4-11) to select an object. The specific operation is the same as the object selection of filtering rule.

All alarm codes are listed in the selection box of the alarm code box and an alarm code can be selected as required.

An alarm class box displays the original class, and the


Page 95 of 516

reclassification class is set by a user.

Rule status can be a new active status or inactive status but only the rule in active status can be applied.

Press the “OK” button to confirm the created reclassification rule and return to the dialog box as shown in Fig. 4-14. In this case, the alarm reclassification rule list will display the new reclassification rule.

The alarm reclassification rule already established can be modified, but the modification is limited to only the reclassification class and rule status. Select one reclassification rule from the alarm reclassification rule list and click the “Modify Alarm Reclassification Rule” button to enter the dialog box of editing the reclassification rule. The dialog box of editing the reclassification rule is similar to that of creating the reclassification rule. For its operation, please refer to that of creating the reclassification rule.

In addition, the operations of deleting an alarm reclassification rule and refreshing a rule are the same as corresponding ones in the alarm filtering rule. Please refer to corresponding operations in the above alarm filtering rule.

A new alarm passes the filtering process and reclassification process, and enters the correlation process.

3. Setting of alarm correlation rules

Alarm management is of vital importance to fault locating and

processing. Generally, there are quite a lot of alarms in the whole

network and in practice, a fault will always result in multiple alarms in

terms of time and space. For example, when a link is broken, a

communication fault alarm will occur to the equipment on both ends of

the link. And alarm correlation processing aims to find the correlation

between alarms, locate the real fault source and decrease the number

of alarms presented to users. Alarm correlation processing, in

combination with alarm filtering, can be used to effectively decrease the

number of alarms presented to users and find out the fundamental

cause of a fault conveniently. Only one of correlated alarms will be

presented to users in the end, which will greatly relieve the labor


Page 96 of 516

intensity of an operator. Users can query correlated alarms to view all

source alarms:

1) The main principles of alarm correlation processing are as follows:

A. Decrease the alarms presented to users.

B. Process multiple correlated alarms as an alarm.

C. Hide minor alarms when a major alarm is activated.

2) The user can ultimately see the following information:

A. Alarm after correlation processing.

B. Source alarm.

C. Explanations of correlation merging, namely, the implementation cause of

correlation rules.

A new alarm, after correlation processing, will be displayed in the alarm list of the alarm main interface.

Click the “Set Alarm Correlation Rule” button on the toolbar to enter the “Alarm Correlation Rule Editor” dialog box (as shown in Fig. 4-15).

Fig. 4-15 “Alarm Correlation Rule Editor” dialog box

The “Alarm Correlation Rule Editor” dialog box of is similar to the


Page 97 of 516

“Alarm Filtering Rule Editor” dialog box.

The buttons on the toolbar of the “Alarm Correlation Rule Editor” dialog box in turn are: Create Alarm Correlation Rule, Modify Alarm Correlation Rule, Delete Alarm Correlation Rule, Refresh Rule, Print Alarm Correlation Rule, About and Exit.

The dialog box lists all current alarm correlation rules in the form of a list. Rules in the active status are in the application, rules in the inactive status do not function but are only listed in the table.

Click the “Create Alarm Correlation Rule” button to enter the dialog box of correlation rule creation (as shown in Fig. 4-16).

Fig. 4-16 Create correlation rule

3) A correlation rule is established as follows:

A. Select the type of a correlation rule. The type of a correlation rule includes:

Suppress rule: that is, when two different alarms caused by the same cause


Page 98 of 516

occur simultaneously, the primary alarm will substitute the secondary alarm

for display. When the primary alarm instead of the secondary alarm is

cleared, users can select whether to display the latter.

Count rule: some unimportant alarms, when occurring once or twice, do not

count. However, if there are so many alarms occurring frequently within a

short period of time and are automatically recovered rapidly, it shows that

there is a serious fault and a new alarm will occur. The new alarm has its

alarm code, alarm class and alarm information, all of which can be defined

by users themselves.

Merging rule: multiple alarms caused by the same cause have different

alarm objects, but have the same alarm code. Such alarms can be merged

into one alarm, but the alarm after being merged displays some additional

information to show the times of occurring, the time of the last alarm, etc.

B. Select whether the rule status is active or inactive. Only those rules in active

status will be applied.

C. Set other options based on the selection of a correlation rule:

If the suppress rule is selected, the managed object and alarm code of the

main/secondary alarm must be set and the selection of whether the

secondary alarm will be displayed after the primary alarm is cleared should

be made. The operation of the managed object setting is the same as the

operation of object selection in the filter rule and reclassification rule.

If the count rule is selected, the setting of the primary alarm and a new

alarm is necessary. When the primary alarms reach the set count within the

set count interval, a new alarm will occur. The alarm class, alarm code and

alarm content of the new alarm are set by the operator.

If the merging rule is selected, only the alarm code of the primary alarm

needs to be selected. The alarm with the same alarm code after the

merging will be merged in the alarm list of the main interface into an alarm.

That is, only the first primary alarm not recovered will be displayed.

D. Input the comment of this created rule in the rule comment text box.

Press the “OK” button to confirm the created correlation rule and return to

the dialog box as shown in Fig. 4-15. In this case, the alarm correlation rule

list will list the created correlation rule.


Page 99 of 516

The alarm correlation rule already established can be modified and different

types of correlation rules need modifying differently. Select one correlation

rule from the alarm correlation rule list and click the “Modify Alarm

Correlation Rule” button to enter the dialog box of editing the correlation rule.

The edit dialog boxes of the suppress rule, count rule and merging rules are

respectively shown in Fig. 4-17, Fig. 4-18 and Fig. 4-19.

A suppress rule can be modified in terms of its rule status, whether the

secondary alarm is displayed after the primary alarm is cleared, and the rule

comment.

Fig. 4-17 Edit the correlation rule (1)---suppress rule

A count rule can be modified in terms of its rule status, the count, count interval, new alarm class, new alarm code, alarm content, and rule comment.


Page 100 of 516

Fig. 4-18 Edit the correlation rule (2)---count rule

A merging rule can only be modified in terms of its rule status and rule comment.


Page 101 of 516

Fig. 4-19 Edit the correlation rule (3)---merging rule

4. Query of a correlated alarm

A correlated alarm is identified with “+” in the alarm list.

Select the correlated alarm to be queried and click the “Correlation Query” button. Then the interface will pop up the dialog box of “Correlated Alarm Detail Information” (as shown in Fig. 4-20). Given in the “Correlated Alarm Detail Information” dialog box are the correlated alarm information, original alarm information and applied correlation rule.


Page 102 of 516

Fig. 4-20 “Correlated Alarm Detail Information” dialog box

4.1.3.5 Trunk node alarm

At most 12 trunk node alarms can be defined for each site. The definition of the trunk node alarm includes the classes and contents of alarms. At different sites, the same or different templates of trunk node alarm can be applied. The advantages for adopting template mode for the trunk nodes are as follows:

1. Different sites can have different trunk node alarm settings.

2. Some sites can have the same trunk node alarm settings as others.

Click the “Set Trunk Node Alarm” button on the toolbar to enter the dialog box of trunk node alarm setting shown in Fig. 4-21:


Page 103 of 516

Fig. 4-21 Setting of trunk node alarm (1)

First select the base station subsystem, site and rack where a trunk node alarm

is to be set and then the template number to be set from the template number

pull-down list. Then, the list in the dialog box will display the classes and

contents of various trunk nodes under this template, as shown in Fig. 4-22.

Fig. 4-22 Setting of trunk node alarm (2)

Press the “Set” button to apply the contents of the selected template to the selected rack of the selected site of the selected base station subsystem.

If the selected rack of the selected site of the selected base station subsystem has been applied to the template of trunk node alarm, then the dialog box will automatically display its template No., and the classes and contents of various trunk node alarms of this template. A new template No.


Page 104 of 516

can be selected to enable other templates to be applied to this site.

1. Create the template

Users can create a template themselves and suite it to actual use.

Click the “New Template” button in the dialog box of trunk node alarm setting (Fig. 4-21) to enter the “Create trunk node template” dialog box, as shown in Fig. 4-23:

Fig. 4-23 Create trunk node alarm template

First input the number of this created template, which should be a different number from the set one.

Then set the trunk nodes of this template. Set the alarm classes and alarm contents of various trunk nodes. Not every node must be set in terms of the above.

Note: the alarm content is input by the user, and it is not necessarily the true cause of the system alarms.

After the trunk node template is created, press the “OK” button to save it and return to the trunk node alarm setting interface. At the time, the new template has been listed in the pull-down list of the new template selection box.

2. Modify the template

Click the “Modify Template” button in the dialog box of trunk node


Page 105 of 516

alarm setting to enter the “Modify trunk node template” dialog box. This dialog box is similar to the “Create trunk node template” dialog box, as shown in Fig. 4-23. During the operation, first select the template number to be modified and then modify the classes and contents of various node alarms of this template.

3. Delete a template

A useless template can be deleted. Click the “Delete Template” button in the dialog box of trunk node alarm setting to enter the “Delete Template” dialog box, as shown in Fig. 4-24:

Fig. 4-24 “Delete Template” dialog box

In the "Delete Template” dialog box, the templates being used are displayed in the form of a list. Click the pull-down button at the lower left of the dialog box and select the template number to be deleted from the pull-down list. Then, press the “Delete” button to delete it.

The deleted template cannot be the one in use, therefore the template in use is not listed in the “Please Select the Template Number you want to delete” pull-down box.

4.1.3.6 Environment alarm

Environment alarm is the alarm generated when the external environment of the system exceeds the designated scope. It includes


Page 106 of 516

temperature-humidity alarm, infrared alarm, etc. The system applies the correlation rule to environment alarm. When an environment alarm is recovered, the corresponding correlated alarm must be cleared manually by users to ensure security. The setting of environment alarm is directed toward a base station controller only and is required in both the SCM rack and RRM rack of BSC.

Click the “Set Environment Alarm” button of the toolbar in the alarm management main interface to enter the dialog box of environment parameter setting, as shown in Fig. 4-25:

Fig. 4-25 Environment Parameter setting----temperature humidity

It can be seen from the dialog box shown in Fig. 4-25 that environment parameter setting involves two tabs: temperature/humidity and infrared.

1. Setting of temperature/humidity parameters

Select one SCM/RRM of BSC in the browse tree on the left and click the temperature/humidity page to set temperature/humidity parameters. The dialog box is shown in Fig. 4-25.

Input the upper and lower limits of temperature and humidity respectively. Temperature values lower than the lower limit or higher than the upper limit are both abnormal, and alarms will


Page 107 of 516

occur.

The maximum scope of temperature setting: 0~450C.

The maximum scope of temperature setting: 20~80%.

2. Setting of infrared parameters

Select one SCM/RRM of BSC in the browse tree on the left and click the infrared page to set infrared parameters. The dialog box is shown in Fig. 4-26.

Fig. 4-26 Environment Parameter setting---infrared

First select the “Enable Infrared Alarm” check box to set whether to enable infrared alarm. If infrared alarm is not enabled, no infrared alarm will occur in the system.

If the time segment of Infrared Alarm Disable is set in the Disable time segment box, then no infrared alarm will be generated in this time segment. There are two modes: periodical setting and specific interval setting.

If the “Periodic Setting” is selected, then only the hour, minute and second of the start time and that of end time can be set. When the infrared alarm is enabled, the infrared alarm is prohibited to be


Page 108 of 516

carried out in the interval between the start time and the end time of each day. If the “Periodic Setting” check box is not selected, it means that the interval shall be specified. Then you need to set the start date and time. When the infrared alarm is enabled, the infrared alarm is forbidden during the set interval.

4.1.3.7 Alarm query

Alarm query is used to display the history alarms recovered, alarms currently not recovered or common notification as required by users, including the display of a display filtering alarm, and that of the source alarm and new alarm of a reclassification alarm and correlated alarm. A current alarm can be confirmed or cleared as long as there is enough authority.

Alarm query can be used to view a cleared or recovered alarm, an alarm filtered by means of the alarm display filtering rule and a source alarm not displayed in the alarm main interface list as a result of the reclassification rule and correlation rule. Therefore, alarm query can provide the most detailed alarm information.

Click the “Query Alarm” button on the toolbar of the main interface of alarm management to enter the “Wizard to Alarm Query” dialog box, as shown in Fig. 4-27:


Page 109 of 516

Fig. 4-27 Wizard to Alarm Query 1

First select a query type from the history alarm recovered, alarm currently not recovered alarm and common notification.

If the history alarm recovered or common notification is selected, the start time and end time of a query must be set.

Press the “Next” button to enter the “Wizard to Alarm Query 2” interface, as shown in Fig. 4-28.


Select alarm source in the dialog box. It is a multiple choice.

Press the “Next” button to enter the “Wizard to Alarm Query 3” interface (as shown in Fig. 4-29).


Page 110 of 516


Select whether to query by Alarm Class or by Alarm Code in this dialog box.

To select the alarm class, you need to select the alarm codes you want to query in the alarm code list in the “Select alarm code” box, which is on the right of the dialog box , and then list them on the right list. To select alarm class, you can select any. This is also a multiple choice. Click the “All” button to select all classes.

Click the "Finish" button to display the query results shown in Fig. 4-30.


Page 111 of 516

Fig. 4-30 Query result display

As shown in Fig. 4-30, the dialog box displays all those alarms or notifications satisfying the query conditions in the form of a list.

You may select an alarm and right click to confirm or clear it by means of the shortcut menu.

Click the “Report” button to output the query results in the Microsoft Excel format through a series of report wizard settings. The alarm query result report in Excel format is shown in Fig. 4-31.

Fig. 4-31 Alarm query result report

Further modification, typesetting and printing of the report can be made in Excel.

4.1.3.8 Alarm knowledge base management

Alarm processing knowledge base provides fault processing help, finds the alarm knowledge base based on an alarm code or reason code input by users, and offers users a troubleshooting suggestion. Alarm processing knowledge base can be used as an auxiliary tool in troubleshooting or a


Page 112 of 516

teaching material for users to learn troubleshooting. In the course of troubleshooting, users can add some of their own ideas about this fault or update the solution to share experience with other users.

Click the “Knowledge Base Management” button in the main interface of alarm management to enter the “Alarm Knowledge Setting” dialog box shown in Fig. 4-32:

Fig. 4-32 Alarm Knowledge Setting

First select the Alarm Code or Alarm Reason Code and then one alarm option from the list of the upper dialog box. The general processing method of this alarm will be given in the “System Content” box.

Users can input the processing method of the selected alarm in the “Users’ Methods” box at the bottommost of the interface for future reference when they or other users process this alarm.


Page 113 of 516

4.1.3.9 80W power amplification support

In BTS (V1A), two PAs are connected in parallel to achieve 80W PA transmitting power. That is, first divide the power of TRU into two parts and then add them to the input of the two PAs. Then the powers of the two PAs are combined into 80W and output. In actual design, a combiner/divider module PEU (Power Extension Unit) is added and installed where TRU is located. PEU implements the function of splitting one power into two parts. Two-into-one function can be implemented by the combiner on HYC or by PEU. 3 alarms (For details, see online help) about 80W power amplification are newly added to the foreground and reported to the PEU panel. The interface display is shown in Fig. 4-33:

Fig. 4-33 80W power amplification alarm interface


Page 114 of 516

4.2 Test management

4.2.1 Overview

OMCR (V2) test management is responsible for the testing of BSS and ensures that the whole system runs normally and stably. In routine maintenance, tests on physical equipment and communication links can be achieved through scheduled tests by test management. Therefore, faults and hidden troubles can be timely detected and avoided. When fault occurs, the instant test can accurately locate the fault and remove it as soon as possible. After the fault is removed, the physical equipment and the system can be tested to see whether they have returned to normal work, therefore to ensure the normal and stable operation of the system.

Test management, adopting the client/server structure, tests BSS, including the testing of various multiple units of BSC, various boards in each multiple unit and the communication links between central module MP and peripheral module MP, and between MP and the control units of various multiple units.

Test management provides users with a man-machine interface (including GUI and MMI) at the client. During the testing, more emphasis is put on various boards to see whether they work normally. If they cannot work normally, further tests are needed until a fault point resulting in board abnormality is located. Test management as a tool can also be used when a fault occurs to the system. In this case, first the related links are tested and then the next object to be tested is decided on the basis of the returned test results to locate the fault at the board level. Besides, any test will not affect the system running and normal conversation services.

It should be noted that certain test operations may influence the normal function of the system. Therefore, you are recommended to perform them only in debugging or the faulty system. When the system functions stably, you’d better not perform test management operations.

4.2.1.1 Test mode

In terms of test modes, there are scheduled test and instant test in a system and in terms of test content, there are board test, link test and E1 line test.


Page 115 of 516

Scheduled test, namely, periodic test task, is mainly used for routine monitoring of various units and link status in a system. Users can set as required the items, interval and test time of a scheduled test at the client and the system will begin to test BSS once setting conditions are satisfied.

Instant test is mainly used for fault locating when a fault occurs and the detection of both the system and fault points after the troubleshooting. Besides, instant test can be used to make a further detection of it when a hidden risk is found in a scheduled test. Users may select the test items at the client for instant test. After the testing begins, the system tests them item by item, analyses test results and stores them in the database. Then, test results will be sent to the client and displayed.

A user with related authority can set, suspend, start and delete a scheduled test item, and create or make an instant test in the client MML interface. Besides, he can query or delete all scheduled test results and instant test results.

4.2.1.2 Test items

Test items depend on the system configuration of BSS. The test items on BSC side are as follows:

1. Testing of TCPP control unit and its DRT boards

2. Testing of AIPP control unit and its TIC boards

3. Testing of BIPP control unit and its TIC boards, ComI boards and SMB boards

4. Testing of GIPP control unit and its TIC boards

5. Test of PCU control unit and its BRP and FRP boards

6. Testing of NSPP control unit and its TIC boards

7. Testing of FSPP control unit and its TIC boards

8. Testing of BOSN boards

9. Testing of the link between central module MP and peripheral module MP

10. Testing of the links between MP and various control units

11. Testing of the loop (E1 line) between BSC and BTS


Page 116 of 516

12. Compatible downward with the test items in V1A (including the testing of DRT, DTI, SMT1, SMT2 boards and links in V1A)


Page 117 of 516

4.2.2 Operations of the test management interface

4.2.2.1 Brief introduction to operation steps

For an instant test, first create the tasks of the instant test, then begin to test and finally display the results of the instant test. The instant test result can be queried and viewed in future.

For a scheduled test, first create the task of the scheduled test (it is recommended that this should be done at midnight, when there is a small amount of traffic). Subsequently, the scheduled test result within a certain period of time after the task creating can be queried and viewed.

4.2.2.2 Entry to the test management interface

After login, users can select “Fault Management” —> “Test Management in OMCR (V2) main interface to enter the main interface of Test Management (as shown in Fig. 4-34).

Fig. 4-34 The main interface for test management


1. Test Mode:Instant Test, Scheduled Test and Exit.


Page 118 of 516

2. Instant Test: Create Test Task, Start Test.

3. Scheduled Test: Set Scheduled Test, Suspend Scheduled Test, Restart Scheduled Test, Delete Scheduled Test.

4. Test Result: Query Test Results, Delete Test Results.

5. View: Toolbar, Status Bar, Command Box, Expand, Collapse, Expand All, Collapse All, Refresh.

6. Help: Test Management Help, Directory and Index, About.

From left to right, the buttons on the toolbar in turn are: Instant Test, Scheduled Test, Start Test, Expand, Collapse, Expand All, Collapse All, Refresh, Help and Exit. All the buttons on the toolbar have the corresponding options in the menu.

The left side of the main window shows the browse tree, which can be Expanded to display all BSCs in the BBS system. The test task column is on the top right of the main window. It displays the instant test task and the scheduled test task in the instant test status and the scheduled test status respectively. The test result column is on the bottom right of the main window. It displays the instant test results or the queried test results.

A command column is a character input interface. Users can directly input an MML man-machine command in the command column to perform an operation. During an interface operation, the corresponding MML command will be displayed in the command column. Note that besides a compound command, only the command related to test management can be input in the application window of test management.

The status bar shows the terminal number, operator and the status of the link between the client and server.

4.2.2.3 Instant test

Expand the browse tree shown in Fig. 4-34, select the BSC to be tested and click the “Instant Test” button on the toolbar to enter the “Instant Test” interface, as shown in Fig. 4-35.


Page 119 of 516

Fig. 4-35 Instant Test

Select the menu “Instant Test —>Create Test Task” to pop up the “Test Items” dialog box, as shown in Fig. 4-36.

Fig. 4-36 Create an instant test task

Two pages will appear in the dialog box of creating an instant test task: “MUnit/Unit Test Items” and “PCM Test Items”. Fig. 4-36 is the M Unit/Unit Test Items tab, in which the selection can be made of unit/multiple unit test items.


Page 120 of 516

The left side of the page is various multiple units, which are generated based on the configuration of this BSC. After a multiple unit is selected, all its subordinate multiple units and their multiple unit numbers will be correspondingly displayed in the display box, which is in the middle of the dialog box. After a multiple unit in the middle display box is selected, units under the multiple unit and their multiple unit numbers as well as unit numbers will be displayed in the display box, which is on the right of the dialog box. One multiple unit or several multiple units can be selected. Once a certain multiple unit is selected, its subordinate units are all selected.

The selection of test items on PCM Test Items page is similar to that on M Unit/Unit Test Items tab. Therefore, further description is not provided here.

Click “OK” to confirm the creation of the instant test task and return to the interface shown in Fig. 4-35. The test column will display the newly-created instant test task.

Click the “Begin to Test” button on the toolbar to begin an instant test. The status of a test task varies with the test progress and the test result column displays the test result of the test task already tested, as shown in Fig. 4-37.


Page 121 of 516

Fig. 4-37 Make an instant test

PCM test items/test results and unit/multiple unit/link test items (results) are displayed on respective pages. The test results will be saved in the test database.

The information of some test results cannot be fully displayed in a test result column, but its details can be viewed. Right click the selected test result and select the pop-up shortcut menu “View Detail Information” to pop up the “Detail Information” dialog box, as shown in Fig. 4-38.

Fig. 4-38 Detail Information

4.2.2.4 Scheduled test

Select the BSC to be tested and click the “Scheduled Test” button on the toolbar shown in Fig. 4-34 to enter the “Scheduled Test” interface shown in Fig. 4-39.


Page 122 of 516

Fig. 4-39 Scheduled Test

In the “Scheduled Test” interface, if a scheduled test task has been created in the selected BSC, then the test task column will display the created scheduled test task.

The scheduled test result will be saved in the test database and can be viewed by means of query of test results.

A scheduled test can also be suspended. If the “Scheduled Test —> Suspend Scheduled Test” menu is selected, then all current scheduled test tasks will be suspended and the states of all test tasks in the test task column are “Suspend”. After suspension, all scheduled test tasks will not be tested until the set time comes, but the test results before the suspension still will be saved in the test database.

The suspended scheduled test can be resumed to active running status. If the “Scheduled Test —> Restart Scheduled Test” menu is selected, the scheduled test task will restore to the “Active” status and will be tested again at the set time.

The “Scheduled Test—>Delete Scheduled Test” menu can be selected to delete a current scheduled test task, but the existing test result still is saved.


Page 123 of 516

The setting of a scheduled test means creating a new scheduled test task. It is used for this scheduled testing of the local client and includes the scheduled test item, scheduled test initiation time, test interval, etc.

After a new scheduled test task is created, the original scheduled test task will be deleted automatically. The test result generated after the execution of a new scheduled test task, together with the original one, will be saved in the test database. Select the “Scheduled Test→Set Scheduled Test” menu to enter the “Test Items” dialog box in the GSM environment shown in Fig. 4-40. Settings in the GPRS environment are shown in Fig. 4-41.

Fig. 4-40 Scheduled test setting - GSM

Fig. 4-41 Scheduled test setting - GPRS


Page 124 of 516

Scheduled Test Setting is similar to Create Instant Test Task, the only difference being the former having the settings of test cycle and test time.

The range for test cycle is 1 ~ 31 days and that for test time is within 24 hours, which can be set as required. For example: If the test cycle is set to two days, the test time is set to 6:30: 00, then in each morning of every two days at 6:30: 00, test on the scheduled test items will be carried out.

4.2.2.5 Test result operation

If not deleted manually, all test results will be kept in the database for up to 3 months. Operations on the test results include: Query test results, delete test results.

1. Query the test results

Both an instant test result and scheduled test result can be queried and viewed. In Fig. 4-34, select “Test Result → Query Test Result” to pop up the “Query condition” dialog box in the GSM environment shown in Fig. 4-42 or that in the GPRS environment shown in Fig. 4-43.

Fig. 4-42 Query condition (1)---GSM


Page 125 of 516

Fig. 4-43 Query condition (1)---GPRS

Query conditions are made up of BSC, Test Items, Test Type, Test Mode, Test Result and Test Time.

1) First select the BSC to query a test result.

2) Then, select a test item. If "Specify Test Items” is selected, the test items

can be designated by ticking the check boxes above it. Select the query

conditions after "Specify Test Items” is selected. If “Not Specify Test Items” is

selected, all test items will be selected. Settings in the GSM environment

are shown in Fig. 4-44. Settings in the GPRS environment are shown in Fig.

4-45.


Page 126 of 516

Fig. 4-44 Query condition (2)---GSM

Fig. 4-45 Query condition (2)---GPRS

3) Select test type: When test items are designated, the test type can be

selected from three forms of MUnit/Unit test, Link Test, MUnit/Unit Test, and

Link Test. If the test items are not designated, the test types can be selected

from six forms of Munit/Unit Test, Link Test, MUnit/Unit and Link Test, MPMP

Lnk Test, E1 Line Test, All Tests.The third test type of MUnit/Unit and Link

Test includes the first Munit/Unit Test and the second Link Test. While if the


Page 127 of 516

MPMP Link Test or E1 Line Test is selected for the test type, there is no

need to select the test items.

4) The test modes include: Scheduled, Instant and All.

5) The test results include: Normal, Abnormal and All. Abnormal results include

all abnormal test results (including the case when a test fails) and can help

locate a fault or find an incipient fault.

6) Select the test time. If "Specify Test Time” is selected, the begin time and

end time of the test interval for query and deletion can be set. If “Not Specify

Test Time” is selected, all test results satisfying the above mentioned items

of 1~5 and saved in current test database will be queried.

Press “OK” to confirm the query condition setting and begin to query. The

query result will be displayed in a test result column, as shown in Fig. 4-46.

Fig. 4-46 Test result query/display

2. Delete a test result

A test result will be automatically saved in the test database. And any test result in the test database can be deleted. Select the “Test Result—>Delete Test Result” menu to pop up the dialog box of deletion conditions. The dialog box of deletion condition is the same as that of test result query and the specific operation is also


Page 128 of 516

the same. After the deletion conditions are set, the test results satisfying all the deletion conditions will be deleted completely.

Because the test result, once deleted, cannot be recovered, it is recommended that before the deletion, any useful test results in the test database should be saved in a disk in the form of backup.


Page 129 of 516

5 Performance Management

To make the network run more efficiently and provide users with the best QoS at the lowest cost, the network maintenance personnel should be well familiar with various performance indexes of BSC and the wireless network, such as traffics of respective cells, congestion of SDCCH and TCH, successful or unsuccessful handover, etc. Such basic data information is provided by performance management. By analyzing this information, the maintenance personnel can find such problems as network load allocation, excessively high or low load existing in a system. In this case, the maintenance personnel can take corresponding measures to balance the network load so as to improve network performance.

Performance management aims to monitor the performance of a network, network unit or equipment, collects related statistical data of performance, evaluates the effectiveness of a network and network unit, reports the status of the telecom equipment, monitors the quality of service of a network and supports network planning and network analysis. Thus, practical network running can be used to obtain the technical data to optimize a network, to improve network performance and efficiency and to provide data bases and reasonable suggestions for the allocation and planning of network resources.

Performance management implements the following functions:

1. Create a measurement job to collect the system running data and store them in the measurement database. Users can analyze these data by means of a performance analysis console or export these data for other analysis platforms or network optimization software to use.

2. For a measurement job collecting data, the current value of a certain counter of a certain measurement object can be observed on demand.

3. Observe some specified events happening in a cell, including handover observation and channel assignment observation. Handover observation includes inner handover observation in a


Page 130 of 516

cell, in-handover/out-handover observation of BSS inner handover, in-handover/out-handover observation between BSSs.

4. Set the measurement interval and indices of BSS Quality of Service (QoS) alarm. When the QoS index in a system exceeds the given value, an alarm will occur. QoS alarm measurement is independent of performance data collecting and still can collect or calculated related data when no measurement job is assigned.

5. When some abnormal factors lead to the inconsistency of the measurement job and observation job information in a BSS with corresponding information in OMCR (V2), the task information stored in OMCR (V2) can be synchronized to the BSS. The previously collected data in BSS system will not be lost as a result of synchronization. ZXG10 BSC (V2) also supports the function of synchronizing one module only.

A performance management system includes 4 modules: performance management, performance analysis console, call tracing and signaling tracing, all of which will be introduced respectively, together with their operations, in this chapter.

5.1 Performance management

Performance management is mainly embodies in its four functions: measurement job, event observation job, QoS control and performance management synchronization control.

5.1.1 Performance management items

NE performance data are not collected all the time, instead, the collection is driven by the task. The user can work out and manage various tasks through the performance management client interface. A task is the unit of performance data measurement.

In the performance management, the user can process two kinds of jobs: They are measurement job and observation job. The alarm monitoring and the synchronization control can be carried out by setting the performance alarm threshold


Page 131 of 516

1. Measurement job

A measurement job object represents a specific measurement job and users can inform the system to collect data by creating a measurement job object.

A measurement job collects data based on certain task dispatching rules and specific measurement granularity to generate a measurement report, which can be reported periodically or instantly and the reporting granularity is larger than or equal to the measurement granularity.

The foreground scans a measurement job regularly and views a task time dispatching table and measurement time table to enable a task to collect data.

The measurement types supported by a measurement job are shown in Table 5-1:

Table 5-1 Measurement job list

SN Measurement

type Measurement

item Range description

00 Basic measurement

CELL Measurement generating basic performance reports

01 BTS measurement

TRX Measure the transceiver powers, power change and signal quality of various TRXs.

02 Cell wireless measurement

CELL

Measure the wireless parameters of various cells, including the channel quality, channel transmitting strength, TA and interference band measurement

03 Wireless access measurement

CELL Measure the wireless random access process of a mobile station

04 SDCCH measurement

CELL Measure the resource allocation, occupation, assignment and use related to SDCCH.

05 TCH measurement

CELL The resource allocation, occupation, assignment and use related to TCH, including TCH/F and TCH/H

06 SAPI3 measurement

CELL Measure the link set-up and load of point-to-point short messages.

07 RMM assignment

CELL Measure the assignment process of an RMM to see how the forced release, queuing and


Page 132 of 516

SN Measurement

type Measurement


measurement directed retry contribute to assignment success rate and also measure the related queuing data.

08 RMM call drop measurement

CELL Measure various call drop cases.

09 Handover cause measurement

CELL Measure the times of out-handover resulting from various causes in this cell.

10 Common handover measurement

CELL Measure the times of out-handover/in-handover in this cell.

11

Measurement of handover synchronization mode

CELL Measure the times of various handover synchronization forms happening in this cell.

12 Paging count CELL Measure the number of transmitted paging messages.

13 Abis interface signaling measurement

CELL Measure the number of various transmitted signaling messages.

14 Measurement of radio resource availability

CELL Measure the utilization ratio of TCH and SDCCH, and completion rate of TRX in this cell.

15 A interface signaling measurement

BSC Measure the number of signaling messages generated or forwarded by this BSC according to the signaling type and signaling name.

16

Measurement of the assignment, call drop and handover of A interface

BSC Measure the times of assignment, call drop and handover of A interface.

17

Measurement of SCCP connections and resource availability of land circuits.

BSC Measure the SCCP connection times of A interface and resource availability of land circuits.

18 TRX LAPD link measurement

TRX Measure the signaling exchange of LAPD signaling links connecting each TRX

19 O&M LAPD link measurement

SITE

Measure the signaling exchange of the LAPD signaling link connecting the O&M module of each SITE. In the case of 3 CMMs on a BTS2, the merging is implemented by the agent on an


Page 133 of 516

SN Measurement

type Measurement


MP.

20 SCCP link measurement

SCCP LINK Measure the signaling exchange on each SCCP signaling link.

21 Processor load measurement

MODULE Measure the CPU load, memory consumption and BHCA of various SMM and RMM modules

22 NS sublayer performance measurement

NSVC Collect data in the FR and NS processes on the FRP board

23 BSSGP performance measurement

CELL Measure the BSSGP layer in the pn module, which is on the BRP board

24 Paging performance measurement

NSE Measure messages in the BSSGP layer, which is in the lower part of NSE in p0 module.

25 Traffic statistics performance measurement

CELL Measure the RLC/MAC layer data in the BRP board

26

Resource management performance measurement

CELL Measure the packet resource data on the p0 module

A performance management terminal program supports up to 30 jobs, each of which can be of one type only. For the names of various job types and the counters (namely, measurement variable) they belong to, see Appendix A.

2. Observation job

An observation job is established to reflect some performance indices during current running in real time. Data collection of an observation object is triggered mainly by an event. That is, once an observation event is triggered, an observation report will be generated and reported instantly. If an event observation window is opened at the management terminal, all events currently happening can be observed. And they can be filtered and displayed as required or stored at the client terminal for future redisplay.


Page 134 of 516

Currently the performance management deals with four types of observation jobs: Inner handover observation, in-handover observation, out-handover observation and assignment failure observation. They can be used to obtain the following information:

1) Inner handover observation

Handover cause

Handover results (success, return to the original channel, timeout no

response and other failures)

Handover time

Handover duration

Cell identification number of a source cell (location area, cell identification

number)

Cell identification number of a destination cell (location area, cell

identification number)

Cell frequency band

Channel type

Whether a source channel is internal or external

Whether a destination channel is internal or external

2) In-handover observation.

Handover cause

Handover result (success, timeout no response, other failures)

Handover time

Handover duration


number)



Frequency band of a source cell

Frequency band of a destination cell


Page 135 of 516

Hierarchical relation between a source cell and a destination cell (SAME,

UPPER, LOWER, undefined)

Channel type

3) Out-handover observation.

Handover cause

Handover results (success, returning to the original channel, timeout no

response and other failures)

Handover time

Handover duration


number)



Frequency band of a source cell

Frequency band of a destination cell

Hierarchical relation between a source cell and a destination cell (SAME,

UPPER, LOWER, undefined)

Channel type

4) Assignment failure observation

Cell identification number (location area, cell identification number)

Channel type

Channel number

Time of assignment failure

Causes of assignment failure (allocation failure (no channel can be

allocated after forced release, queuing and directed retry), failure of

occupation, assignment timeout no reply, assignment returning to the

original channel)

RR cause

3. Alarm watch


Page 136 of 516

Alarm watch means performance alarm threshold management, which automatically compares the value of a current performance counter or the average of counters within a certain period of time with the set threshold rules. If conditions are satisfied, an alarm at a corresponding level will occur. Once conditions are no longer satisfied, the alarm will be recovered automatically and in time based on performance alarm cancellation rules.

The implementation of alarm watch features the following:

1) There are fixed types of BSS QoS alarms. These types are worked out

mainly based on 99’ Local Operation & Maintenance Center Requirements

by Mobile Bureau and do not provide any user-defined QoS alarm.

2) The measurement and threshold setting of QoS alarms are directed toward

the whole BSS, with the objects being all the cells, processing units or No.7

links in a BSS, and no single object can be set in terms of its threshold and

duration.

3) The data collection of QoS alarms is independent of that of a universal

measurement job. Therefore, even if there is no setting of a measurement

job, QoS threshold calculation and alarm are available.

Alarm threshold management mainly includes such operations as setting a threshold, modifying a threshold, etc. Threshold management corresponds to the measurement object of a specific measurement job.

The measurement items of QoS are shown in Table 5-2 below:

Table 5-2 Table of QoS measurement items

Full Name Meaning Corresponding

measurement object

Default value/unit

RMMCPMeanLoad Mean load of peripheral module processors

Module >80%

RMMCPPeakLoad Peak load of peripheral module processors

Module >90%

SMMCPMeanLoad Mean load of central module processors

Module >80%

SMMCPPeakLoad Peak load of central module processors

Module >90%


Page 137 of 516

Full Name Meaning Corresponding

measurement object

Default value/unit

CallEstablishSuccRate Call completion ratio of a cell Cell <10%

No7TrunkAssignmentSuccRate

Answering attempt ratio of a trunk route

BSC <10%

TFAvailableRate TCH/F availability Cell <10%

THAvailableRate TCH/H availability Cell <10%

SdAvailableRate SDCCH availability Cell <10%

No7TrunkAvailableRate No.7 trunk availability BSC <10%

TFMeanTrafficLoad Mean traffic of a cell TCH/F Cell 0.5 Erl

THMeanTrafficLoad Mean traffic of a cell TCH/H Cell 0.5 Erl

No7TrunkMeanTrafficLoad Mean traffic of a trunk route N7 LINK 0.5 Erl

SdDropRate SDCCH call drop rate Cell >90%

FaFDropRate FACCH/F call drop rate Cell >90%

FaHDropRate FACCH/H call drop rate Cell >90%

TFVoiceDropRate TCH/F voice drop rate Cell >90%

TFDataDropRate TCH/F data drop rate Cell >90%

THVoiceDropRate TCH/H voice drop rate Cell >90%

THDataDropRate TCH/H data drop rate Cell >90%

InHOSuccRate In-handover success rate BSC <10%

OutHOSuccRate Out-handover success rate BSC <10%

IntraBSSHOSuccRate Handover success rate between the cells controlled by BSS

BSC <10%

IntraCELLHOSuccRate Intra-cell handover success rate

BSC <10%

The major differences between measurement job and observation job are result output mode and data collection mode. The measurement job timely outputs the measurement report or immediately submits the measurement report and the data collection has a certain granularity. While the observation job outputs the result when trigged by event and reports it immediately, such as the generation of the handover.

The performance data obtained from a measurement job can be displayed at the performance analysis console in the form of a report.


Page 138 of 516

5.1.2 Operations of the performance management interface


A measurement job can be created, modified, deleted, suspended/recovered, displayed, and counter query can be used to obtain counter instant data.

An event observation job can be created, modified, deleted, displayed, etc.

Alarm watch is used for the generation and modification of an alarm threshold rule.

5.1.2.2 Entry into the performance management interface

After login, users can select “Performance Management”—> “Performance

Management” in the OMCR (V2) main interface to enter the main interface of

performance management (as shown in Fig. 5-1).

Fig. 5-1 Main interface of performance management

The upper part of the interface are the menu bar and toolbar, the left window in the middle of the interface is a browse tree displaying the measurement job, observation job name and alarm watch, and the lower part of the interface are the command column and status bar.


Page 139 of 516

The items on the menu bar in turn are:

1. Performance Management: Create, Delete, Modify, Synchronize, Suspend, Recover, Exit.

2. Measurement job: Counter Query.

3. Observation Job: Event Observation.

4. View: Toolbar, Status Bar, Command Box, Expand, Collapse, Expand All, Collapse All, Refresh.

5. Help: Performance Management Help, Directory and Index, About.

The buttons from left to right in the toolbar in turn are: Create, Delete, Modify, History Data Query, Counter Query, Synchronize, Suspend, Recover, Event Observation, Expand, Collapse, Expand All, Collapse All, Refresh, Help and Exit.

Listed in the browse tree are the names of the whole mobile communication system. Click “ ” or “ ” in the browse tree or select Expand, Collapse, Expand All, Collapse All on the tool bar to Expand or Collapse a browse tree and display the measurement job name, observation job name and alarm watch of various BSS systems currently existing. Listed under the measurement job and observation job are respectively the job names currently created.

The right window of the interface corresponds to the selected content and operation on the left. In the left-hand browse tree, if you click a measurement job in a certain BSC, the right-hand window will display all current measurement job lists and their simple attributes in this BSS. If you click a specific measurement job, the right-hand window will display its parameter attribute details. The display for an observation job is similar to that for a measurement job. Because there is only one QoS alarm MO in each BSC, the right window will display the corresponding threshold value in this BSS when you click the alarm threshold in a certain BSS in the browse tree on the left.

A command column is a character input interface. Users can directly input an MML man-machine command in the command column to perform an operation. During an interface operation, the corresponding MML command will be displayed in the command column. Note that besides a


Page 140 of 516

multiple command, only those commands related to performance management can be input in the application window of performance management. You may select/cancel the “View—>Command Box” menu to open/close a command window.

With this interface, users can make the selection of handover between different measurement jobs, observation jobs and threshold management jobs so as to further implement other management functions.


Page 141 of 516

5.1.2.3 Measurement job

Expand a browse tree fully in the performance management main interface shown in Fig. 5-1 and select a measurement job node in the BSS. Then, the right side of the interface will display all current measurement job lists in this BSS (as shown in Fig. 5-2).

Fig. 5-2 Display of measurement jobs

The measurement job list on the right side of the interface lists the names, types, states, start date and stop date of all established measurement jobs. The items in a measurement job list correspond to various jobs in the measurement jobs in the browse tree. The jobs with their type being basic measurement are automatically created after the system is initialized.

Click the “Create” button on the toolbar to create a measurement job. Then, select the measurement job list item and click the “Delete” button to delete this measurement job or click the “Modify” button to pop up a dialog box for modifying this measurement job. Click the “Counter Query” button to view the performance data measured by this measurement job according to conditions.

Select the “Suspend” or “Recover” button after the selection of measurement job list item to suspend/recover this measurement job.


Page 142 of 516

1. Specific display of a measurement job

Select a specific measurement job in the browse tree, and the right side of the interface is divided into 3 boxes, displaying respectively the list display, measurement schedule and measurement job of this job, as shown in Fig. 5-3.

Fig. 5-3 Display of a single measurement job

2. Create a measurement job

A new measurement job must include the description of all required job features, therefore a measurement job to be created must be set in terms of the measurement type, measurement start time, measurement stop time (including the measurement start date, measurement stop date and measurement time segment in a day), measurement time interval, cycle of granularity and measurement object.

A measurement job to be created cannot have the same measurement time with an existing one of the same measurement type that contains the same measurement object in this BSS. That is, multiple measurement jobs of the same measurement type that contain the same measurement object can be created as long as


Page 143 of 516

they do not overlay in terms of measurement time.

Click the “Create” button to enter “MJ CreateWizard 1” interface (as shown in Fig. 5-4).

Fig. 5-4 MJ Create Wizard 1

1) Select a measurement type. For optional measurement types, see Table 5-1

Measurement Job List.

2) Input a measurement job name.

3) Select the BSS.

4) Select a measurement granularity. The time interval for measurement data

collection depends on the measurement granularity. Click the pull-down list

box on the right of GP to select the required measurement granularity. The

optional measurement granularities are: 5 N, 15 N, 30 N and 60 N.

5) Select a measurement object. There are different kinds of measurement

objects for different measurement types. Users can specify up to 255

measurement objects in a measurement job. In the optional measurement

object box, display all measurable objects of this measurement job, select a

measurement object and press the “>” button to add the selected object to

the “Selected Objects” box.


Page 144 of 516

After the setting, press the “Next” button to enter the next MJ CreateWizard 2 (as shown in Fig. 5-5).


Select and set a measurement interval in this dialog box. The measurement job will collect data within the set measurement interval.

1) There are two clock icons in this dialog box. Click the clock icon on the top

and select a start time from the generated time flag. At the same time, click

the clock icon at the bottom and select the end time from the generated time

flag.

2) Press the “Input” button to add the set interval to the “Selected Interval” box.

3) Repeat Steps 1) and 2) to set other measurement intervals.

Warning:

A. The time between various time intervals cannot be the same.

B. The minimum cycle of collection is 5 minutes and a measurement time

interval must be the integer multiple of 5 minutes.

C. If no time interval is set, the system will use the default one. The default

interval range is 00:00 ~00:00 (24:00), i.e. it will be executed in all intervals.


Page 145 of 516

Press the “Next” button to enter the next MJ Create Wizard 3 (as shown in

Fig. 5-6):


1) Set the start and stop date of the measurement job. The start/stop date

should be set as follows:

A. The start date for a job should be more than or equal to the current date,

which is used as the default start date.

B. The stop date for a job should be more than or equal to the start date for a

job. If the “Execute until be deleted” check box is selected, the job will never

stop until users delete it in forced mode.

2) Select one or multiple measurement days. Only on the set days, can

measurement data be collected.

3) Input the Report Information. Set the FR Date and FR Time of the data

measured by this measurement job, and PR. There are 7 kinds of PRs: 0,

15 minutes, 30 minutes, 1 hour, 6 hours, 12 hours and 24 hours, 0

representing instant report of measured data. The setting of Report

Information can be used to report data at a fixed point of time so as to avoid

traffic peak. A PR should be more than or equal to the measurement

granularity. Report Information, when set as FR, cannot be modified.


Page 146 of 516

Press the “Next” button to enter the next MJ Create Wizard (as shown in Fig.

5-7):


This dialog box lists all information of this measurement job set in the previous 3 MJ Create Wizards.

Take Fig. 5-7 as an example to explain the creation of a measurement job: The measurement job is named “basic” and the measurement type is basic measurement. The measurement object is No.1, No. 2 and No. 3 cells of No. 1 SITE in BSC-18 (BSC1). The job starts with Sept.5th, 2000 and will not end until users delete it in forced mode. Every Sunday, Monday, Tuesday, Wednesday, Friday, Saturday, at 00: 45 ~01:40, 04:00 ~06:20, 09:25 ~12:35, measurements are carried out in the three intervals. The measurement granularity is 5N. The FR Time is 10:35 a.m. of Sept.5th, 2000 and the PR is 30 minutes.

Press the “Finish” button to finish creating the new measurement job. If the creation is successful, the system will show the successful prompt and the job will be added in the browse tree and the measurement job list. If the creation is unsuccessful, the system will prompt the failure cause.


Page 147 of 516

3. Modify a measurement job

A created measurement job can be modified in terms of partial settings.

Select the measurement job to be modified, as shown in Fig. 5-1, and click the “Modify” button to enter the modification dialog box shown in Fig. 5-8:

Fig. 5-8 MJ Modify Wizard –Time Option

There are two pages in the interface: Time Option and Other Option. Shown in the above Fig. 5-8 is the Time Option tab. In Time Option, the measurement start time cannot be modified once the foreground begins to measure data. The FR Date and Time cannot be modified after the first report of data.

The "Main Option” dialog box of MJ Create Wizard is shown in Fig. 5-9. In Main Option, only the measurement job name can be changed. And the base station controller a measurement job belongs to, measurement granularity and measurement type cannot be modified once a measurement job is created.


Page 148 of 516

Fig. 5-9 MJ Create Wizard ---Main Option

4. Delete a measurement job

Select the measurement job to be deleted and click the “Delete” button to delete it. The deletion operation will delete all records this job has collected as it deletes this job. Thus, this job will no longer collect any data.

5.1.2.4 Counter query

Counter Query can be used to instantly view the current value of a certain counter of a certain measurement object of a certain measurement job in data collecting.

Select the measurement job to be queried and click the “Counter Query” button on the toolbar to enter the dialog box of PM - Counter Query (as shown in Fig. 5-10).


Page 149 of 516

Fig. 5-10 Counter Query---Condition

First set query conditions, including the selection of a counter type and that of a measurement object. Press the “Query” button, and a query result page will appear in this dialog box. Then, you will automatically enter this query result page, which will display a counter satisfying query conditions (as shown in Fig. 5-11).

Fig. 5-11 Counter Query---Result


Page 150 of 516

Press the “Continue” button to return to the query condition page to continue querying other counters. Press the “Return” to finish Counter Query.

5.1.2.5 History data query

History data query can be used to obtain the history data that a corresponding type of measurement job collects.

Click the “History Data Query” button on the toolbar to enter the interface of selecting the measurement type and measurement object for history data query (as shown in Fig. 5-12).

Fig. 5-12 History data query – selection of measurement type and object

Select the type of the measurement job and measurement object and press “Next” to enter the interface of selecting a measurement counter (as shown in Fig. 5-13).


Page 151 of 516

Fig. 5-13 History data query – select a measurement counter

Select the measurement counter and press “Next” to enter the interface of setting query start time (as shown in Fig. 5-14).

Fig. 5-14 History data query – set query start time

Input a legal start time and end time for the date to be queried and press the “Finish” button to query the data. The returned result is shown in Fig. 5-15.


Page 152 of 516

Fig. 5-15 History data query – query result display

5.1.2.6 Observation job

In the browse tree in the performance management main interface shown in Fig. 5-1, select an observation job node of one BSS system, all current observation job lists of the BSS system will be displayed on the right of the interface, as shown in Fig. 5-16.

Fig. 5-16 Observation job display


Page 153 of 516

The observation job list on the right side of the interface lists the names, types, states and stop time of all established observation jobs. The items in the observation job list correspond to various jobs in the browse tree.

To create an observation job, click the “Create” button on the toolbar. To delete this observation job, select it and click the “Delete” button. To modify this observation job, select it and click the “Modify” button to pop up a dialog box and modify it.

To suspend/recover an observation job, select it and click the “Suspend” or ”Recover” button.

1. Display of a specific observation job

Select an observation job in the browse tree, and the right side of this interface will be divided into two boxes, displaying the lists and other pieces of information of this job, as shown in Fig. 5-17.

Fig. 5-17 Display of a single observation job

2. Create an observation job

A newly created observation job cannot overlay in terms of time with an existing one of the same observation type that contains the same measurement object. That is, multiple measurement jobs of


Page 154 of 516

the same measurement type that contain the same measurement job can be created as long as they do not overlay in the time

Click the “Create” button on the toolbar to enter the dialog box of OJ Create Wizard (as shown in Fig. 5-18).

Fig. 5-18 OJ CreateWizard

1) Select the observation type. The observation type includes cell inner

handover observation in a BSS, inter-cell in-handover observation in a BSS,

inter-cell out-handover observation in a BSS and assignment failure

observation.

2) Select the BSS.

3) Input an observation job name.

4) Select an observation object.

5) Input the observation stop time. When the StopTime comes, this

observation job will be deleted automatically.

An observation job can only have an observation object. If the stop date is set to the default, the job will be executed until it is deleted forcefully. If only the stop date is input, the job will be stopped at 0'clock that day.


Page 155 of 516

Press the “OK” button to finish creating a new observation job. If creation succeeds, the system will give the prompt of success and the newly created job will be added to both the browse tree and the observation job list.

3. Modify an observation job

Select the observation job to be modified and click the “Modify” button to enter the modification dialog box shown in Fig. 5-19:

Fig. 5-19 OJ Modify Wizard

An observation job can be modified in terms of its job name and stop time only.


Page 156 of 516

5.1.2.7 Event observation

An observation event, once triggered, will be reported. You may open an event observation window to receive any event information.

Click the “Event Observe” button to enter the dialog box of PM - Event Observe (as shown in Fig. 5-20).

Fig. 5-20 Event Observe

The buttons on the toolbar in turn are: Open, Save, Delete, Clear, Event Filter, Continue Observation and Exit.

Event observation information is made up of two parts: the upper window informs users in time of the general information of all current observation events in a BSS in the form of a list and the lower text box displays the detailed information of the observation event selected by a user from the list.

1. Event filter

A filter operation is used to make sure that only an event generated by the selected observation job can be received.


Page 157 of 516

Click the “Event Filter” button on the toolbar of the “Event Filter” dialog box to enter the dialog of Event Filter (as shown in Fig. 5-21).

Fig. 5-21 Event Filter

Select the observation type to be filtered and press the “OK” button to confirm this filter operation. Then, all events whose observation types are filtered will not be displayed when generating.

2. Event Save

An observation event can be saved as a file for future view or for other client terminals to view. Click the “Save” button on the “Event Observe” dialog box, and all observation events displayed in the current “Event Observe” dialog box will be saved as files.

The file from which an observation event is saved can be opened. Click the “Open” button in the “Event Observe” dialog box and select the file to be opened. Then, the observation event saved in this file will be displayed in the dialog box.

Event information is stored beforehand in a temporal file and users can use “File → Save” menu to save it. In the case of exit from this window, users should also be reminded of whether to save it. In addition, users can select “File → Open” to open a saved observation time file.


Page 158 of 516

5.1.2.8 Alarm watch

Select the observation alarm watch in the browse tree of the performance management main interface (as shown in Fig. 5-1) to enter the display interface of Alarm watch (as shown in Fig. 5-22).

Fig. 5-22 Alarm watch—CPU load

The upper right of the alarm watch display interface is the BSS number and the alarm status list, and the lower right is the alarm watch threshold display. The alarm watch threshold displays the classification of different thresholds. Altogether there are six tabs: CPU Load, Call Establishment Rate, Available Rate, Traffic Load, Drop Rate, HO Success Rate

Displayed on each page are the set QoS alarm threshold value, cycle of collection and active status. Only the activated QoS alarm threshold functions.

If the average of any QoS item in active status within the cycle of collection exceeds the alarm threshold value, a corresponding alarm will occur.

Select one alarm watch item in a BSS and click the “Suspend” or


Page 159 of 516

“Recover” button to suspend/recover all performance alarm watch in this BSS.

Fig. 5-22 is the CPU Load page of alarm watch. This page displays the threshold values, cycles of collection and active states of the following performance alarms. RMMCPMeanLoad, RMMCPPeakLoad, SMMCPMeanLoad and SMMCPPeakLoad

Various units are represented as follows:

The threshold of the percentage type: XX%, the value range is from 0 to 100%.

The threshold of the Irish type: XX, the value range is from 0 to 100%.

Cycle of collection: 5N, 15N, 30N, 60N. (N representing minute)

Fig. 5-23 is the Call Establishment Rate page of alarm watch. This page displays the threshold values, cycles of collection and active states of the following few performance alarms: Call completion ratio of a cell Answering attempt ratio of a trunk route

Fig. 5-23 Alarm watch---CallEstablishSuccRate


Page 160 of 516

Fig. 5-24 is the AvailRate page of alarm watch. This page displays the threshold values, cycles of collection and active states of the following few performance alarms: TCH/F available rate, TCH/H available rate, SDCCH available rate, trunk circuit available rate.

Fig. 5-24 Alarm watch----availability rate

Fig. 5-25 is the Traffic Load page of alarm watch. This page displays the threshold values, cycles of collection and active states of several performance alarms: TCH/F average traffic load, TCH/H average traffic load, trunk circuit average traffic load.


Page 161 of 516

Fig. 5-25 Alarm watch---TrafficLoad

Fig. 5-26 is the DropRate page of alarm watch. This page displays the threshold values, cycles of collection and active states of the following performance alarms: SDCCH channel drop rate, FACCH/F channel drop rate, FACCH/H channel drop rate, TCH/F voice channel drop rate, TCH/F data channel drop rate, TCH/H voice channel drop rate, TCH/H data channel drop rate.


Page 162 of 516

Fig. 5-26 Alarm watch--DropRate

Fig. 5-27 is the HOSuccRate page of Alarm watch. This page displays the threshold values, cycles of collection and active states of the following performance alarms, in-handover success rate, out-handover success rate, inter-cell HO success rate controlled by BSC and intra-cell HO success rate.


Page 163 of 516

Fig. 5-27 Alarm watch--HOSuccRate

The modification operation can be used to establish or modify the threshold value, cycle of collection and active status. Click the “Modify” button on the toolbar to enter the “Revise QoS Value” interface as shown in Fig. 5-28: Likewise, alarm watch modification is set in terms of CPU load, CallEstabSuc Rate, AvailRate, Traffic Load, Drop Rate and HO SucRate. If an input value exceeds the range for the threshold value, the system will prompt the error and requires a second input.


Page 164 of 516

Fig. 5-28 Alarm watch---modification

5.1.2.9 Synchronize and refresh

1. Refreshing

Because the OMCR (V2) system supports multi-terminal operations, Refresh operation can be made to display a task in real time. The specific operation is as follows: click the “Refresh” button on the toolbar shown in Fig. 5-1.

2. Synchronization

In actual equipment running, a synchronization operation is needed if the data in the measurement job, observation job and QoS managed object and those in OMCR (V2) are accidentally made inconsistent. Most of the predictable inconsistencies can be automatically processed by the system in a synchronous mode. The inconsistencies include failures in restarting the module, synchronization failure at CPU changeover. When some undetectable a synchronization cases happen, the operator needs to carry out the synchronization operation, such as the synchronization in restarting OMCR (V2) together with BSS, so as


Page 165 of 516

to ensure the smooth running of the system. Click the ”Synchronize” button on the toolbar to enter the dialog box of PM - Synchronize MP (as shown in Fig. 5-29).

Fig. 5-29 Synchronize MP

Select first a base station controller and then a module number to be synchronized. Press the “OK” button to synchronize the data in the background to the foreground. After the synchronization is completed, the system will give the prompt showing what module is successfully synchronized and what module is not (as shown in Fig. 5-30).

Fig. 5-30 Synchronization prompt


Page 166 of 516

5.2 Performance analysis console

For the sake of making clear the performance level of an entity, the performance data collected by a measurement job must be further processed. Thus, when users present analysis requests, the system can report the analysis & processing result. A performance analysis console aims to implement the above-mentioned functions.

5.2.1 Overview

A performance analysis console mainly implements the function of querying the performance data reported to a database by a measurement job, making a statistical analysis of the specified performance indices as required by customers and presenting the statistical results to client users in the form of a list. Besides, a performance analysis console is required to be capable of processing a performance report.

A performance analysis console implements the following main functions:

1. Query the performance data

It mainly completes the query of the performance data reported in the measurement job, so as to carry out further analysis calculations.

2. Analyze and display the performance data

Calculate and analyze the recorded performance data according to the calculation formulas of performance indices specified by users, and present the analysis results to users in the form of a list so that users can find and solve problems in time.

3. Process performance reports

This means to convert the electronic data collected and analyzed by performance data into electronic reports or paper reports in other report formats. Report output supports work B Report, C Report and BSC service report in the format of EXCEL.


Page 167 of 516

5.2.2 Operations of the performance analysis console interface


A performance analysis console mainly has two kinds of operations:

1. Query and analysis of performance indices.

Make a required analysis of the performance indices of a measurement object by means of the analysis task creation wizard with the analysis result displayed in the form of a list.

2. Output work report.

Three kinds of reports can be output: System performance report (B report), C report and BSC service report.

5.2.2.2 Entry into the interface of performance analysis console

After login, select “Performance Management”—> “Performance Analysis Console” in the OMCR (V2) main interface to enter the main interface of Performance Analysis (as shown in Fig. 5-31).

Fig. 5-31 Main interface of Performance Analysis


Page 168 of 516

The upper part of the interface is the menu bar and toolbar, the left window in the middle of the interface displays the browse tree of the whole configuration, the right window is the display of current processing result (performance analysis or report) and the lower part of the interface is a status bar.


1. Performance Analysis: Create Graphic Analysis, Output EXCEL, Graphic Switching, Exit.

2. Performance Report: Create Configuration Information Report, Create Performance Report, Create GPRS Report, Define Report Option.

3. Toolbar, Status bar, Expand, Collapse, Expand All, Collapse All, Refresh.

4. Help: Performance Analysis Console Help, Directory and Index, About.

The buttons on the toolbar from left to right in turn are: Create Configuration Information Report, Create Performance Report, Create Graphic Analysis, Define Report Option, Output EXCEL, Graphic Switching, Expand, Collapse, Expand All, Collapse All, Refresh, Help and Exit.

A browse tree displays the configurations of the whole mobile communication system. Click “ ” or “ ” in the browse tree or select Expand, Collapse, Expand All or Collapse All to Expand or Collapse the browse tree and display the configurations of various existing BSSs.

Performance Analysis has no command column.

The configuration information report can be created on the performance analysis console. The operations are as follows: Click the “Create Configuration Information Report” button.

The interface is as shown in Fig. 5-32.


Page 169 of 516

Fig. 5-32 Display of Performance Analysis

5.2.2.3 Performance report

A performance report means selecting some counters for the counter values collected by those created tasks and making a summary of them within a specified time range to form a report. The output of the report supports multiple formats, such as system performance report, C1 report, C2 report and 24-hour traffic report, for which the EXCEL format is used as the basic report format.

A work report includes three kinds: daily report, monthly report and self-defined report, and can be output as required according to a day, a month or a selected date.

In Fig. 5-31, click the “Create Performance Report” button to enter the work report parameter input wizard shown in Fig. 5-33.


Page 170 of 516

Fig. 5-33 Work report parameter input wizard 1

Select the type of the report in this dialog box, click the “Next” button to enter the next wizard dialog box shown in Fig. 5-34.


Select a work report analysis object. Press the “Next” button to enter the next

wizard interface (as shown in Fig. 5-35).


Page 171 of 516


The statistical report has three types: Daily report, monthly report and self-defined report. If it is a daily report, a certain date shall be selected. If it is a monthly report, a certain month shall be selected. If it is a self-defined report, the start and stop dates shall be selected.

Then, select a busy hour time segment for a statistical report and set the StartTime and StopTime of the busy hour. The busy hour time segment can only be set as one hour.

Press the “Finish” button to finish parameter input. If the monthly report is selected, you can enter the next wizard interface to set the StartDate and StopDate shown in Fig. 5-36. Otherwise, you will enter the report wizard interface shown in Fig. 5-37 to set the report output format.


Page 172 of 516


Fig. 5-37 Report style wizard 1

A report wizard is used to create report styles meeting different requirements.

“Finish” can be directly clicked in each of the interface of the report wizard to end the report wizard and display reports with existed settings. Click the “Cancel” button to cancel the display of the performance report. Click the “Back” button to return to the previous wizard interface for modification setting (except report style wizard 1). Click the “Next” button to enter the


Page 173 of 516

next wizard interface for other settings.

Click the “Next” button in Fig. 5-37 to pop up the page setting interface shown in Fig. 5-38.

Fig. 5-38 Report style wizard 2---page setting

In Fig. 5-38, select the “Font Setting” page shown in Fig. 5-39 to set the fonts in the selected parts of the report and the alignment mode of the page header and data items in the report.

Fig. 5-39 Report style wizard 2----font setting


Page 174 of 516

Press the “Font” button to enter the dialog box of font setting (as shown in Fig. 5-40).

Fig. 5-40 Font setting

Press the “Next” button to enter report style wizard 3 (as shown Fig. 5-41). First input a report name. Then select a heading to be printed on the report page header.



Page 175 of 516

Based on the selection of Wizard 3, Wizard 4 (as shown in Fig. 5-42) lists the heading included in the report page header. To add, input other headings in the text box of the upper interface and press the “Add” button to add them to a lower page header heading list. To print a page header heading, select Horizontally or Vertically. For an existing page header heading, you may select it in the list and press the “Delete” button at the lower part of the list to delete it or press the “Upward” or “Downward” button to adjust the order of headings.


Click “Next” button to enter the interface shown in Fig. 5-43 to select the heading printed at the page footing of the report.



Page 176 of 516

Based on the selection of Wizard 5, Wizard 6 (as shown in Fig. 5-44) displays the heading included in the report page footing. To add, input other headings in the text box of the upper interface and press the “Add” button to add them to a lower page footing heading list. To print a page footing heading, select Horizontally or Vertically. For an existing page header heading, you may select it in the list and press the “Delete” button at the lower part of the list to delete it or press the “Upward” or “Downward” button to adjust the order of headings.


Report style wizard 7 (as shown in Fig. 5-45) is the last report format wizard interface used to prompt that the settings of a report format are completed.


Page 177 of 516


Press the “Finish” button to enter the work report display. A work report is displayed in an EXCEL. Given below are the examples of B report and C report, as shown in Fig. 5-46 and Fig. 5-47 respectively.

Fig. 5-46 System performance report display

Fig. 5-47 C1 report display


Page 178 of 516

5.3 Call tracing

The tracing of users in a public land mobile network system is implemented by call tracing, which provides user administrators or network administrators with an effective and practical tool to observe users.

Call tracing records put more emphasis on process tracing instead of user behavior. The data in call tracing records are also used for auxiliary analysis of network management.

5.3.1 Overview

Call tracing enables mobile user administrators to trace the activated entities in a public land mobile network.

The tracing records of the activated entities are not collected at every moment, but are activated by MSC. An operator manages call tracing via a call tracing interface at the BSC terminal. The service flow of a traced entity after a call is established is the unit of a tracing record. The system operating personnel implements the tracing function of a mobile user or a piece of mobile equipment by collecting various tracing messages from a BSC. Call tracing supports multiple examples and a series of standardization operations.

The descriptive features of call tracing include:

1. Tracing object: Specified user designated by MSC.

2. Tracing type: basic tracing, handover tracing, wireless tracing, etc.

3. Tracing receipt time: Year/month/date/hour/minute/second. It is the time in each message of a traced entity a call tracing program receives.

A call tracing program supports the tracing of up to 16 entities, each of which in a call can only be assigned a tracing type by MSC, but different calls of the same entity can have different tracing types. A tracing entity is specified by MSC. The tracing type can support the following tracing types stipulated in GSM12.08.

1. Basic tracing: basic information related to a call service flow, such


Page 179 of 516

as call tracing messages, BTS identification, TRX identification, TRAU identification, radio channel description, base station color code, establishment cause, end indication, mobile station classmark, circuit identity code, etc.

2. Handover tracing: besides the information of basic tracing, it includes the mobile station power, base station power, timing advance, synchronization information, handover cause, handover destination cell list, handover result, handover duration, BSSMAP message, SCCP message, RR message. When necessary, it also includes the measurement report before/after handover, power control and Abis message.

3. Wireless tracing: It is almost the same as the information of the handover tracing.

5.3.2 Operations of the call tracing interface


An entity to be traced is selected by MSC, which also initiates the tracing of one or multiple entities.

After MSC activates the BSC for call tracing by means of messages, you may press the “Begin Tracing” button in the call tracing interface to view the tracing records of the object being currently traced.

Tracing messages can be saved as files for future view.

5.3.2.2 Entry into the call tracing interface

After login, select “Performance Management” —> “Call Tracing” in the OMCR (V2) main interface to enter the main interface of call tracing (as shown in Fig. 5-48).


Page 180 of 516

Fig. 7-48 The main interface of call tracing

The upper interface is the menu bar and toolbar, the middle of the window is tracing message display and the lower interface is the status bar.


1. Tracing: Begin Tracing, End Tracing, Suspend Tracing, Recover Tracing, Save Record, History Record, Exit.

2. View: Toolbar, Status Bar, Clear Screen, Refresh.

3. Help: Call Tracing Help, Directory and Index, About.

The buttons from left to right in the toolbar in turn are: Begin Tracing, End Tracing, Suspend Tracing, Recover Tracing, Save Records, History Records, Clean Screen, Refresh, Help and Exit.

One call of a tracing entity is made up of many tracing messages. The contents of and the order between these messages represent various service flows. For example, assignment of channel flow, release of channel flow and cell handover flow, etc. can be represented by the information included in tracing messages. Therefore, for one call of a traced entity, the tracing messages generated during this call must be displayed on an integrated basis. A call tracing interface can display all tracing messages generated during a cal.


Page 181 of 516

The trace messages are displayed in the window according to types of the tracing messages, altogether five pages are displayed. Basic information, radio channel, Handover process, A interface message and Abis interface message. RR message and measurement report message can be obtained in the Abis interface message page.

Call tracing has no command column.

5.3.2.3 Begin tracing

Click the “Begin Tracing” button, and the workstation initiates call tracing handshake (namely, communication) with BSC. If MSC has activated BSC by means of messages for call tracing, BSC also initiates handshake to the workstation. If handshake succeeds, the tracing program decodes, classifies and displays any tracing information received. If a handshake lasts for over 1 minute but does not succeed, this handshake is considered as a failure and the system will prompt users to end tracing and reinitiate tracing.

After a successful handshake, once there is any tracing information, the program will decode the information and show it in the interface in real time (as shown in Fig. 5-49).


Page 182 of 516

Fig. 5-49 Tracing message display

The above Fig. 5-49 is the Abis interface message page of call tracing message display and various pages in the interface display various corresponding messages, including the message number, tracing example number, tracing type, message type and message generation time.

Double click one tracing message to pop up a dialog box providing the detailed information of this tracing message (as shown in Fig. 5-50).

Fig. 5-50 Detailed message of call tracing

The basic information and radio channel pages of the call tracing interface also display specific index values corresponding to some tracing messages, as shown in Fig. 5-51. Click one tracing message in the Basic Message page. If this message has one or multiple index values listed at the upper part of this window, it will be displayed in the index value box. Otherwise, the index value box is null.


Page 183 of 516

Fig. 5-51 Tracing message display---basic message

5.3.2.4 Other operations

1. End tracing

Click the “End Tracing” button to terminate all tracings and ignore all tracing messages. That is, the message of the original traced entity will no longer be added to tracing records and the tracing message of a new traced entity will not be included in tracing records. In this case, the original tracing records will not be deleted, but will be when tracing is resumed.

2. Suspend/recover tracing

Click the “Suspend Tracing” button, and all tracings will be suspended and none of the tracing messages will be processed. That is, the message of the original traced entity will no longer be added to tracing records and the tracing message of a new traced entity will not be included in tracing records. In this case, the original tracing records will not be deleted and new tracing messages will be added when Recover Tracing is selected.

Click the “Recover Tracing” button on the tool bar, and all


Page 184 of 516

suspended tracings will resume to the status of tracing. The original tracing records still will be retained. Once there is any tracing information, the tracing program will decode and classify any tracing information received in real time, and displays them in real time on the interface on the basis of the original tracing records. However, any tracing message within the suspend time segment cannot be recovered.

3. Save records

Click the “Save Tracing” button. Then this button is pressed down and this status is saved. All tracing messages in the current interface and subsequent ones will be saved automatically as files until the “Save Tracing” button is clicked again to cancel the press-down status.

The saved files are automatically included under the “itlog” directory with the same directory as call tracing running files. A tracing message saving file has the extension name “trc”. If the file name is invoke +year/month/day-hour/minute, then the name of the file where the call tracing starting on at 9:23 on Sept.21, 2000 is saved as invoke2000921-923.trc. A saved file cannot be put to cyclic use. The files saved at different times will not be overwritten.

4. View history records

So-called history records are those tracing records saved by means of Save Tracing. Open a call tracing file, and you may view history records.

Click the “History Records” button, and select and open a history record file. Thus, you may view any history tracing message in this history record.

5. Clear screen

Click the “Clear Screen” button to clear all tracing messages in the current call tracing interface from the screen.


Page 185 of 516

5.4 Signaling tracing

5.4.1 Overview

The major task of signaling tracing is to trace signals involved in BSC. The major operational environment is the tracing of one terminal to one BSC, which can convert the signaling code stream into words in the small traffic situation, so as to facilitate the observation. A traced signaling can be stored for future opening and provides the filtering function. The major involved protocols include A interface No.7 signaling, messages in MTP, SCCP, MAP and messages in Abis interface layer 3 and internal Abis interface management messages, so as to facilitate the viewing of the signaling flow during debugging and commissioning and problem detection in the signaling cooperation process. Besides the tracing, a saved file will be generated for future view. The size of a tracing file depends only on disk capacity and the viewing of a tracing file has no such restriction.

After the GPRS service is added, the decoding that supports Gb interface signaling is correspondingly added in the signaling tracing module, due to the newly added BSSGP message in the Gb interface. At the same time, messages related with PS service are added at the Abis interface and the signaling tracing also provides functions of related message tracing and decoding. For the GPRS service, the signaling tracing mainly provides the tracing and decoding of the RLC (PS) message, MAC message on the Abis interface and BSSGP message on the Gb interface.

5.4.2 Operations of the signaling tracing interface

After login, select “Performance Management” —> “Signaling Tracing” in the OMCR (V2) main interface to enter the main interface of signaling tracing (as shown in Fig. 5-52).


Page 186 of 516

Fig. 5-52 Main interface of Signaling Tracing

The upper interface is the menu bar, which includes the following:

1. File: Open…, Save…. Exit

2. Signaling Tracing: Start, Suspend, End, Background Filter

3. Window: Tile Horizontally, Tile Vertically, Cascade

4. Tools: Clean Up, Find, Next, Previous

5. View: Toolbar, Status Bar;

6. Help: Signaling Tracing Help, Directory and Index, About…

The buttons on the toolbar are in turn Begin Tracing, Suspend Tracing, End Tracing, Background Filtering, Open, Save, Tile Horizontally, Tile Vertically, Cascade, Clean Up, Find, Find Next, Find Previous, Help and Exit.

”Open”: open an existing tracing file.

”Save”: save the tracing message of the current active window as a file.

”Begin”: begin signaling tracing.


Page 187 of 516

”Suspend: stop signaling tracing.

”End”: end signaling tracing and close the tracing window.

”Scroll”: display automatically the last signaling (excluding filtered signaling) when any signaling arrives.

”Background Filtering”: filter received signaling in terms of their types.

”Details”: display the details of a tracing message.

“Tile Vertically”, “Tile Horizontally”, “Cascade”: Different arranging modes are displayed in the interface.

”Clean Up”: clean up all tracing information in the current window.

“Find”, “Find Next”, “Find Previous”: Search information required by the user in the active window.

At the bottom of the interface is the status bar which shows the current interface, the operation terminal No. and the operator.

5.4.2.1 Begin tracing

In Fig. 5-52, click the “Start Tracing” button or select the “Begin” in the “Signaling Tracing” menu to start a tracing. First enter the “Configuration of Signal Trace” interface in the GSM environment shown in Fig. 5-53. Configurations in the GPRS environment are shown in Fig. 5-54.


Page 188 of 516

Fig. 5-53 Configuration of signal trace--GSM

Fig. 5-54 Configuration of signal trace--GPRS

Select first the base station controller of the signaling to be traced in the

pull-down menu and then a message type. Press the “OK” button to begin

signaling tracing, and the interface displays the tracing message in real time

(as shown in Fig. 5-55).


Page 189 of 516

Fig. 5-55 Tracing message display

In the dialog box of tracing setting, there is the same number of message types as tracing message windows. The window of the interface in the above Fig. 5-55 displays the tracing message list of an RSL message, which includes the message name, SITE, BTS, TRX, channel number, time of generation, length and content.

Because the information traced in real time is displayed in real time, the window automatically displays the last valid message in scroll mode as more and more information is generated.

Press the “Suspend” button or select the “Suspend” option in the “Signaling Tracing” menu to stop signaling tracing.

Click the “Clean Up” button or select the “Clean Up” option in the menu “Tools” to clear all tracing messages in the current active window. After the operation of cleaning up messages, the active window will display any tracing messages generated after that moment.

The window displays up to 5,000 tracing messages. If there are over 5,000 tracing messages displayed, the earliest one will be overwritten and only the latest 5,000 ones will be displayed.


Page 190 of 516

Click the “End” button to stop this signaling tracing. And the window displays all tracing messages (except for the earliest one deleted as a result of more than 5,000) of this tracing.

If save is started, signaling messages can still be saved in the disk file even if they exceed 5000 pieces in this window.

5.4.2.2 Tracing message operations

Contents of the message are displayed in the code form. In the tracing message display window shown in Fig. 5-55, double click a tracing message to view detailed information of it, as shown in Fig. 5-56. In this case, a small window will appear in the lower part of the interface, displaying the details of the selected tracing message.

Fig. 5-56 Display of detailed information

5.4.2.3 Tracing window operations

In the dialog box of tracing setting, there is the same number of message types as tracing message windows. There are three arranging modes of the tracing message window: Tile Horizontally, Tile Vertically and Cascade. The window shown in Fig. 5-55 is arranged in Cascade. The following


Page 191 of 516

example is one window arranged in Tile Horizontally mode, as shown in Fig. 5-57:

Fig. 5-57 Window tiled horizontally

5.4.2.4 Tracing filtering

Because some messages unrelated to tracing objective are frequently generated during the tracing, background filtering can be used to filter some tracing messages.

In Fig. 5-55, click the “Background Filter” button in the toolbar to carry out the background filter operation and pop up the “Message Filter” dialog box in the GSM environment shown in Fig. 5-58. The “Message Filter” dialog box in the GPRS environment is shown in Fig. 5-59.


Page 192 of 516

Fig. 5-58 Background filter---GSM

Fig. 5-59 Background filter---GPRS

Background filtering adopts a two-level filtering mode.

The left-hand window lists the measurement types the background is


Page 193 of 516

capable of filtering in the three-level tree structure. Click to select the first two levels of nodes in the tree structure. Then, you can select from the message types included in the selected types of messages in the right-hand window.

Select the first two levels of nodes of the tree structure and press the “All” or “None” button to select all or none of message types.

Press the “OK” button to confirm the selection of filtered options. Then, the same background filtering can be implemented in each signaling tracing before background filtering is set again.

5.4.2.5 Find

Because there are too many tracing messages, Find can be used to locate a specific type of or a tracing message.

Click the “Find” button or select the “Find” option in the “Tools” menu to pop up a dialog box of Find, as shown in Fig. 5-60:

Fig. 5-60 Find

Input any field of the message to be found in “Find what” box and select the Find direction as required. Then, press the “Find Next” button to find. Find is implemented in the current active window and the first found objective containing this field will be located and highlighted.

Click the “Previous” or “Next” button on the toolbar. Then, the previous or next objective containing the character of the objective to be found will be located and highlighted.

5.4.2.6 Save a tracing file

During the tracing, the tracing information in the current active window can be saved as a tracing file.


Page 194 of 516

Select the “Save” button or select the “Save” option in the menu “File” to pop up the “Save As” dialog box shown in Fig. 5-61:

Fig. 5-61 “Save As” dialog box

Select the path of a tracing file, input a file name, select a “Save as type” (the default value being a tracing file *.tra) and click “Save”. Thus, the tracing message in the active window can be saved as a tracing file.

After Save is set, the “Save” button on the toolbar will be in the press-down status. All current tracing messages and those ones being generated will be saved as a tracing file until the “Save” button on the toolbar is clicked again to cancel the press-down status.

5.4.2.7 Open a tracing file

A tracing file can be opened and viewed.

Click the “Open” button or select the “Open” option in the menu “File” to pop up a dialog box of opening a tracing file, as shown in Fig. 5-62:


Page 195 of 516

Fig. 5-62 Open a tracing file

Select the tracing file to be opened and click the “Open” button to open the

selected tracing file. Then, any tracing message saved in this file will be

displayed in the interface.


Page 197 of 516

6 Configuration Management

This chapter mainly describes how to configure and operate the ZXG10-OMCR (V2) system during deployment and how to do related maintenance after the system is put into operation. It also provides brief introductions to the concepts involved. The configuration management involves the configuration of the radio resources data as well as the software loading for the base station, transceiver, communication links, cells, channels, for instance, the configuration conditions of the base station, transceiver and transmission equipment inside the equipment, the cell configuration and coverage conditions of the system, the communication links between the BSC, BS, transceiver and transmission equipment, channel configuration and application status, etc.. The configured data are stored in the database subsystem, which are generated according to the system configuration data and vary with the specific application status during the system operations. Meanwhile the related configuration commands are afforded to modify the configured conditions and generate the statistic data.

6.1 Radio resources management

6.1.1 Overview

The position and range of the management system of ZXG10 radio resources is shown in Fig. 6-1. ZXG10 radio resource configuration management (RRC in short) mainly enables the configuration and management on the BSS radio resources of GSM. It provides the maintenance personnel with the man-machine interface for radio resource configuration and management. It also synchronizes the configuration information provided by the maintenance personnel to the background database table of the radio resources so as to support the foreground database. The foreground part mainly executes the configuration results of the background; that is, the background configures the data into DBS and BTS via an agent to enable the parameters, while MS gets the latest configuration via the RMS broadcasting information.


Page 198 of 516

RRCMMI

Radio ResourceManagementDatabase

Manager

Radio ResourceManagementDatabase

UNIX/ Window NT Server MP

RRC Agent

SITE(OMU)

MSServer MP

Fig. 6-1 System location and range

The objects of radio resources in the BSC system include: Base Station Controller (BSC), Site, Base Transceiver Station (BTS), Transceiver (TRX), Radio Carrier, logic traffic channel (CHAN), Handover Control parameter (HOC), Power Control parameter (POC), Adjacent handover cell (AHANDOVERCELL), Adjacent reselection cell (ARESELECTCELL), Adjacent handover & reselection cell (AHO&RESELECTCELL), interference cell (ICELL), external cell (ECELL), logic PCM (PCMCIRCUIT), logic LAPD link (LAPDLINK) and frequency hopping system (FHS).

The configuration management includes the following three parts: BSS, cell parameters and configuration cells.

After login to the system, select “Configuration Management Radio Resources Management” in the OMCR (V2) main interface (Fig. 2-10) for the system to enter the “ZXG10 Radio Resources Management” interface, as shown in Fig. 6-2.


Page 199 of 516

Fig. 6-2 The main interface

The main interface shows three windows: the tree in the left window shows the objects to be created and maintained, the right window describes the relationship between BSC and SITE with a logic illustration, and the window below shows the man-machine command – MMI command created by the operations. The status bar at the bottom of the interface shows the linking status with the server and the machine number of the client terminal.

6.1.2 BSS

The configuration of the BSS includes configuration of the base station controller, PCM circuits, LAPD links, logical sites, and external cells.

On the main interface, select the “BSS” node, and right click to display the pull-down short-cut menu. The short-cut menu includes: Create BSC, Create PCM Circuits, Create LAPD links, Create Logical Site, Create External Cells, etc., and each option will be described below in detail.

6.1.2.1 Creating BSC

Select “BSS” node in the browse tree of Fig. 6-2. Then right click to pop up


Page 200 of 516

the floating menu, select “Create BSC”. The interface shown in Fig. 6-3 for configuring the BSC will pop up, where you can configure the basic property and timer of the BSC.

1. Basic property

The basic property setting of the BSC in GSM is shown in Fig. 6-3 and that

in GPRS is shown in Fig. 6-4.

Fig. 6-3 Configuring BSC (1) GSM

Fig. 6-4 Configuring BSC (1) GPRS


Page 201 of 516

1) BSC ID

Description: uniquely identifies the BSC.

Value range: 1 ~ 255

2) Alias:

Description: BSC alias.

3) Mobile Country Code (MCC)

Description: MCC consists of three decimal digits, which is used to uniquely identify the home country of a mobile subscriber (or system).


Default: 460

4) Mobile network code (MNC)

Description: MNC consists of two decimal numbers, which uniquely identifies a specific GSM PLMN network in a country (decided by MCC).

Value range: 0 ~ 99

Default: 0

5) LoadValidTime

Description: During load indication, BSC periodically sends “BSSAP LOAD INDICATION” message to MSC, and notifies MSC of the load status, and the message contents include time indication information, indicating the valid time length of the service load information. And then, MSC will notify the neighboring BSC of these information in the “BSSAP LOAD INDICATION” message. These parameters are used to indicate the valid time length of the load information.

Value range: See Table 6-1.

Table 6-1 The value range of “LoadValidTime”

Value Meaning

0 Reserved.

1 Valid in 10s

… …

254 Valid in 2540s

255 Valid permanently

Default: 5


Page 202 of 516

6) Load Ind Period

Description: During load indication, BSC periodically sends “BSSAP LOAD

INDICATION” message to MSC, and notifies MSC of the load status, and

the message contents include time indication information, indicating the

valid time length of the service load information. And then, MSC will notify

the neighboring BSC of these information in the “BSSAP LOAD

INDICATION” message. When the load indication message is sent

periodically, this parameter determines the period for BSC sending the load

indication message.


Table 6-2 The value range of “Load Ind Period”

Value Time length

1 0.1s

2 0.2s

… …

65535 6553.5s

other values Reserved.

Default: 600

7) Flow Control

Description: “OverLevel” defines the flow control policy for the specific cell.


Table 6-3 The value range of “ Flow Control”

Overload

Level

Barred Class

Number

Rxlev_ Access

_Min

Penalty Time

Cell select

Offset

Tx-

integer

Max- Retrans

0 0 0 0 0 0 0

1 0 0 0 0 1 -1 (255)

2 0 1 0 0 2 -2 (254)

3 1 2 0 -2 (254) 3 -3 (253)

4 2 3 0 -3 (253) 4 -3 (253)

5 3 4 0 -4 (252) 4 -3 (253)


Page 203 of 516

Overload

Level

Barred Class

Number

Rxlev_ Access

_Min

Penalty Time

Cell select

Offset

Tx-

integer

Max- Retrans

6 4 4 0 -4 (252) 4 -3 (253)

7 5 4 11111 -3 (253) 4 -3 (253)

8 6 4 11111 -2 (254) 4 -3 (253)

9 7 4 11111 -1 (255) 4 -3 (253)

10 8 4 11111 0 4 -3 (253)

11 9 4 11111 0 4 -3 (253)

12 10 4 11111 0 4 -3 (253)

8) Allow Inter-Cell Handover

Description: Whether to allow the handover between cells inside a BSC.

BSS should support the internal handover inside the cell (handover between

different channels in the same cell) and the handover between cells

controlled by MSC. It can also support the handover between different cells

inside BSS. This can be set via OMS. Internal handover between different

cells of a BSS can reduce the messages between BSS and MSC because

no message will be sent to MSC before the execution of handover. Only

after the handover is completed, will BSS send the “HANDOVER

EXECUTION” message to MSC.

Value range: True / False

Default: True

9) Resource Position Info

Description: The geographic name of the position where BSC is located.

10) ResourceIndTs

Description: This is the threshold value that BSC automatically indicates

MSC, that is, the percentage of the present available channels over the

total channels. This parameter is used for the threshold of automatic

indication mode, that is, the percentage of the current available channels

over the total channels. When the available resources of the cell is less

than the parameter, the resource indication that is configured by the O&M

should be given to MSC, notifying the cell condition. During the resource

indication by BSC, there are four modes as such:


Page 204 of 516

A. Auto mode: After the “BSSAP RESOURCE REQUEST” message is

received, BSC instantly returns a “BSSAP RESOURCE INDICATION”

message as an acknowledgement without containing any resource

information. And then, once the auto condition (service threshold or the

interval between any two messages) set by O&M of BSC is satisfied, BSC

automatically sends the “BSSAP RESUORCE INDICATION” message to

MSC, and uses the “Periodicity IE” in the “BSSAP RESOURCE REQUEST”

to determine the interval of the indication messages (unless the “Periodicity

IE” is 0, BSC will ignore 0).

B. One-off mode: After the “BSSAP RESOURCE REQUEST” message is


message with resource information. If the “BSSAP RESOURCE REQUEST”

message does not contain the “Extended Resource Indication IE”, BSC will

stop sending and wait for the next “BSSAP RESOURCE REQUEST”. If it

does, BSC will follow the rules of “Subsequent Mode” element in the

message, same as mode 4. If the previous mode is 1 or 3, then mode 1 or 3

is adopted, otherwise mode 4 applies.

C. Period mode: After BSC receives the “BSSAP RESOURCE REQUEST”

message, it will immediately return a “BSSAP RESOURCE INDICATION”

message that contains the resource information. After that, BSC periodically

sends the “BSSAP RESOURCE INDICATION” message. If the Periodicity

IE in the “BSSAP RESOURCE REQUEST” message is not 0, then the

period to send the message is the value of Periodicity IE times 100ms. If

Periodicity IE is 0, then the message is wrong and the whole “BSSAP

RESOURCE REQUEST” message is regarded as wrong.

D. Stop mode: After the “BSSAP RESOURCE REQUEST” message is


message as an acknowledgement without any resource information. And

then, the cell resource information will no longer be sent to MSC.

Value range: The auto indication thresholds are shown in Table 6-4.


Page 205 of 516

Table 6-4 The value range of “ResourceIndTs”

Value Meaning

0 0%

1 1%

… …

100 100%

Default: 30

11) BSC Max Reset Num

Description: The maximum number of resets during BSC resetting. When

BSC sends the “BSSAP RESET” message to MSC and if the “BSSAP

RESET ACKNOWLEDGE” message sent by MSC has not been received in

the specified T4 time, the whole resetting process should be repeated. The

“BSSAP RESET” message can be repeated up to N times. If no reply is

obtains after N times, MSC will end the resetting process and inform OMS.

N is decided by the “BscMaxResetNum” parameter.

Default: 3

12) Cict Max Reset Num

Description: The maximum number of resets during BSC circuit resetting.

When BSC sends the “BSSAP RESET CIRCUIT” message to MSC and if

the “BSSAP RESET CIRCUIT ACKNOWLEDG” message has not been

received in the GSM-specified T19 time, the whole circuit resetting process

should be repeated. The “BSSAP RESET CIRCUIT” message can be

repeated up to N times. If no reply is obtains after N times, MSC will end the

resetting process and inform OMS.N is determined by CircMaxResetNum.

Default: 3

13) Can Send Confusion Message

Description: This parameter determines whether BSC is allowed to send the

“BSSAP CONFUSION” message. This message is bi-directional, indicating

that the received message cannot be correctly processed due to some

reasons while there are no other suitable fault messages to return, the

confusion message will be sent.

Value range: True: BSC is allowed to send “BSSAP CONFUSION” message;


Page 206 of 516

False: BSC is not allowed to send “BSSAP CONFUSION” message.

Default: False

14) Customize retry can send failure

Description: Whether the external customized directed retry is allowed to

send the indication failure.

Value range: True/False

Default: False

15) Load Indication

Description: Whether the load indication process can be used. The load

indication process is an optional item of BSC, which enables the

neighboring BSCs to know their cell load conditions outside the boundary,

so that even more information can be consulted during the common

handover and the intra-BSC traffic handover. This parameter decides

whether the load indication process can be used, meanwhile the validity of

parameters “LoadValidTime” and “LoadIndPrd” are determined, that is,

when the parameter is 0 (the load indication process cannot be used), the

two parameters followed be invalid, otherwise, they will be valid.

Value range: False: Load indication cannot be used; True: Load indication

can be used.

Default: False

16) Broad Area

Description: Broadcast scope

Value range: Basic GSM900 frequency band P-GSM (ARFCN = 1 ~ 124),

the expanded GSM900 frequency band E-GSM (ARFCN = 0~124,

975~1023), GSM1800 frequency band GSM1800 (ARFCN =512 ~ 885),

railway GSM900 frequency band R-GSM (ARFCN =0~124, 955~1023).


Page 207 of 516

2. Timer

The setting of the BSC timer in GSM environment is illustrated in Fig. 6-5

and that in GPRS environment is illustrated in Fig. 6-6.

Fig. 6-5 Configuring BSC (2) -- GSM

Fig. 6-6 Configuring BSC (2) -- GPRS

Parameters of each timer are described as follows:

1) T1: Blocking/unblocking period

Description: Due to some reasons (O&M intervention; equipment


Page 208 of 516

failure/recovery; radio resources unavailable/available), BSS will block/unblock a land circuit and send “BLOCK/UNBLOCK” message to MSC; After MSC receives the message, it sends “BLOCK/UNBLOCK ACKNOWLEDGE” message to BSS. This period of time is defined by T1.

Value range: 1 ~ 1200. See Table 6-5.

Table 6-5 The value range of blocking/unblocking period

Code Duration represented

1 0.1s

2 0.2s

… …

1200 120s


Default: 80

2) T4: Global resetting period

Description: T4 is used to monitor the “BSSAP RESET” message sent by BSC to MSC.

A. Start conditions of the timer: When there is a global reset for BSC, T4 starts.

B. Stop conditions of the timer: When the “BSSAP RESET ACKNOWLEDGE” message is received from MSC.

C. Timeout: If T4 expires, BSC will repeat the whole process.


Table 6-6 The value range of the global resetting period

T4 Duration represented

100 10s

101 10.1s

102 10.2s

… …

1200 120s


Default: 100


Page 209 of 516

3) T7: The protective period for handover request

Description: T7 monitors the “BSSAP HANDOVER REQUIRED” message.

The maximum time taken from the “BSSAP HANDOVER REQIURED”

message sent by BSC to the “BSSAP HANDOVER COMMAND” message

returned by MSC. In case of failure, MSC can send the “BSSAP

HANDOVER REQUIRED REJECT” message to BSC. Similarly, BSC will

stop the T7 timer.

A. Start conditions of the timer: When BSC sends “BSSAP HANDOVER

REQUIRED” message to MSC, T7 starts.

B. Stop conditions of the timer: MSC receives “BSSAP HANDOVER

COMMAND” or “BSSAP HANDOVER REQUIRED REJECT” message.

When the “BSSAP HANDOVER REQUIRED REJECT” message is received,

BSC can send other “BSSAP HANDOVER REQIURED” messages to MSC.

C. Timeout: If T7 expires but the external handover conditions are still satisfied,

BSC will instantly repeat the “HANDOVER REQUIRED” process.


Table 6-7 The value range of the protective period for handover request


50 5s

51 5.1s

52 5.2s

… …

300 30s


Default: 100

4) T8: Source BSC handover executing period

Description: T8 supervises the external handover process of the source

BSC

A. Start conditions of the timer: T8 starts when the “BSSAP HANDOVER

COMMAND” message is received from MSC.

B. Stop conditions of the timer: When the “BSSAP CLEAR COMMAND”


Page 210 of 516

message is received from MSC or if the “RIL3_RR HANDOVER FAILURE”

message is received from MSC, T8 will stop.

C. Timeout: When the T8 timer expires, BSC will send the “BSSAP CLEAR

REQUEST” message to MSC.


Table 6-8 The value range of the source BSC handover executing period


80 8s

81 8.1s

82 8.2s

… …

150 15s


Default: 120

5) T10: Assignment period

Description: T10 supervises the assignment process.

A. Start conditions of the timer: T10 starts when the “ASSIGNMENT

COMMAND” message is sent to MS.

B. Stop conditions of the timer: When MS receives “ASSIGNMENT

COMPLETE” and “ASSIGNMENT FAILURE” messages, T10 stops.

C. Timeout: When T10 timer expires, BSC sends a “BSSAP ASSIGNMENT

FAILURE” message to MSC.

Value range: 40 ~ 140. See 6-9.


Page 211 of 516

Table 6-9 The value range of the assignment period


40 4s

41 4.1s

42 4.2s

… …

140 14s


Default: 80

6) T13: Protective period for global resetting

Description: T13 is a protection time for a local call clearing process.

A. Start conditions of the timer: When BSC receives the “BSSAP RESET”

message from MSC, T13 starts.

B. Stop conditions of the timer: When SCCP receives a SSP/SPI (“subsystem

prohibited/signaling point inhibited”) message.

C. Timeout: When T13 expires, BSS sends the “BSSAP RESET

ACKNOWLEDGEMENT” message to MSC.


Table 6-10 The value range of the protective period for the global resetting


50 5s

51 5.1s

52 5.2s

… …

300 30s


Default: 150

7) T17: The first overload period of flow control

Description: T17 supervises the flow control process of MSC overload.


Page 212 of 516

A. Start conditions of the timer: When BSC receives the “BSSAP OVERLOAD”

message from MSC, T17 starts.

B. Stop conditions of the timer: No.

C. Timeout: When T17 timer expires, BSC observes whether there is a

“BSSAP OVERLOAD” message received from MSC.


Table 6-11 The value range of the first overload period of flow control


10 1s

11 1.1s

12 1.2s

… …

100 10s


Default: 80

8) T18: The second overload period of flow control

Description: T18 supervises the flow control process of MSC overload.

A. Start conditions of the timer: When BSC receives the “BSSAP OVERLOAD”

message from MSC, T18 starts and the service degrades by one level. .

B. Stop conditions of the timer: No.

C. Timeout: When T18 timer expires, services will be increased by one level.


Table 6-12 The value range of the second overload period of flow control


30 3s

31 3.1s

… …

200 20s


Default: 150


Page 213 of 516

9) T19: The circuit resetting period at the BSS side.

Description: If because of exceptional BSC SCCP connection, the circuits

must be released to idle state, and BSS will send “BSSAP CIRCUIT

RESET” message to MSC to start T19. After MSC receives that message, it

releases the corresponding services and the circuits to the idle state and

send “BSSAP CIRCUIT RESET ACKNOWLEDGE” message to BSC.

When the BSC receives the “RESET CIRCUIT ACKNOWLEDGE” message,

the timer will stop.


Table 6-13 The value range of the circuit resetting period at the BSS side


1 0.1s

2 0.2s

… …

1200 120s


Default: 80

10)T20: Circuit group blocking/unblocking period

Description: If because of some reasons (O&M intervention; equipment

fault/recovery; radio resources unavailable/available), BSS will

block/unblock a group of land circuits, then send “BSSAP CIRCIUIT

GROUP BLOCK/UNBLOCK” message to MSC. After the message is

received, the MSC will send the “BSSAP CIRCIUIT GROUP

BLOCK/UNBLOCK ACKNOWKEDGE” message to BSS, notifying BSS that

the blocking/unblocking message has been received.


Table 6-14 The value range of the circuit group blocking/unblocking period


Page 214 of 516


1 0.1s

2 0.2s

… …

1200 120s


Default: 80

11)T9101: Supervises the RLSD message receiving.

Description: T9101 timer supervises the RLSD message receiving.

A. Start conditions of the timer: When BSC sends “BSSAP CLEAR

COMPLETE” message to MSC, T9101 starts.

B. Stop conditions of the timer: When BSC receives RLSD message from MSC,

T9101 stops.

C. Timeout: When the T9101 timer expires, BSC will send the RLSD message

to release the SCCP connection.

Value range: 100. See Table 6-15.

Table 6-15 The value range of the timer T9101


100 10s


Setting: not subject to change.

12)T9103: Supervises the channel activation process.

Description: Timer T9103 is used to supervise the channel activation

process.

A. Start conditions of the timer: When BSC sends CHANNEL ACTIVATION to

BTS, T9103 starts.

B. Stop conditions of the timer: When BSC receives “CHANNEL ACTIVATION

ACK” or “CHANNEL ACTIVATION NACK” message from BTS, T9103 stops.

C. Timeout: When T9103 expires, BSC sends RF CHANNEL RELEASE to

BTS.


Page 215 of 516


Table 6-16 The value range of T9103

RmsT9103 Duration represented

20 2s



13)T9104: Supervises the “CLEAR COMMAND” sent from MSC.

Description: The T9104 timer supervises the “CLEAR COMMAND” sent

from MSC.

A. Start conditions of the timer: When BSC sends “CLEAR REQUEST”

message to MSC, T9104 starts.

B. Stop conditions of the timer: When BSC receives “CLEAR COMMAND”

message from MSC, T9101 stops.

C. Timeout: When the T9104 expires, the “CLEAR REQUEST” message is

resent (four times at most).




50 5s

… …

200 20s


Default: 150

14)T9105: Supervises the SCCP connection process.

Description: The timer T9105 is used to supervise the SCCP connection

process.

A. Start conditions of the timer: When BSC sends

“SCCP_CONNECTION_REQ” message to MSC, T9105 starts.

B. Stop conditions of the timer: When BSC receives


Page 216 of 516

“SCCP_CONNECTION_CONFIRM” or “SCCP_CONNECTION_REFUSED”

message from MSC, T9105 stops.

C. Timeout: When the T9105 timer expires, BSC will send the “CHANNEL

RELEASE” message to MS.




20 2s

… …

2400 240s


Default: 100

15)T9108: Supervises the physical context request process

Description: The T9108 timer is used to supervise the physical context

request process.

A. Start conditions of the timer: When BSC sends “PHYSICAL CONTEXT

REQUEST” message to BTS, T9108 starts.

B. Stop conditions of the timer: When BSC receives “PHYSICAL CONTEXT

CONFIRM” message from BTS, T9108 stops.

C. Timeout: When the T9108 timer expires, BSC will send the “ASSIGNMENT

FAILURE” message to MSC.




20 2s



16)T9113: Supervises the external handover in the destination cell.

Description: The T9113 timer is used to supervise the external handover in


Page 217 of 516

the destination cell.

A. Start conditions of the timer: When BSC sends “HANDOVER REQUEST

ACK” message to MSC, T9113 starts.

B. When BSC receives the “HANDOVER COMPLETE” message from MS or

the “CLEAR COMMAND” message from MSC, the T9113 timer stops.

C. Timeout: When the T9113 timer expires, BSC will send the “CLEAR

REQUEST” message to MSC.




80 8s

81 8.1s

… …

150 15s


Default: 130

17)zxgT1: The protection time for channel activation

Description: The protection time to wait for MS access during assignment or

handover after the channel is activated.

A. Start conditions of the timer: The destination channel receives

CHLACTIVATION ACK and sends RADIO AVAILABLE to the source

channel.

B. Stop conditions of the timer: MS accesses and the destination channel

receives ASSIGNMENT COM or HANDOVER COM.


Table 6-21 The value range of zxgT1

Value Time length


Page 218 of 516

50 5.1s

51 5.1s

… …

120 12.0s

Default: 70

18)zxgT2: The protection time for applying a channel

Description: The protection time for applying a channel

A. Start conditions of the timer: The new channel sends RADIO APPLY.

B. Stop conditions of the timer: Channel request succeeds and the new

channel receives RADIO AVAILABLE; or the channel request fails and the

new channel receives RADIO UNAVAILABLE; or in case of queuing, the

new channel receives RAIO PROCEEDING.

Value range: 10 ~50. See Table 6-22.


Value Time length

10 1.0s

11 1.1s

… …

50 5.0s

Setting: T2 > T3103

Default: 30

19) zxgT3: The protection time for link establishment response

Description: In case of instant assignment, the protection time to wait for the

central module’s link establishment response.

A. Start conditions of the timer: The Pn instance sends ESTABLISHING to the

P0 instance.

B. Stop conditions of the timer: Pn sample receives the “CONNECT CONF”

sent by P0 instance, or the “CONNECT FAIL” when P0 failed to establish

link.



Page 219 of 516


Value Time length

50 5.0s

51 5.1s

… …

650 65.0s

Setting: T3 > T9105

Default: 120

20) zxgT4

Description: The protection time to wait for the confirmation by P0 to the

“HO COM” or “ASS COM” message.

A. Start conditions of the timer: After Pn receives the “HO COM” or “ASS COM”

message of MS and forwards it to P0.

B. Stop conditions of the timer: Pn receives the HO COM or ASS COM

acknowledgement from P0.


Default: 30

21) zxgT5: Supervises the ciphering mode modify process.

Description: The T5 timer supervises the ciphering mode modify process.

A. Start conditions of the timer: When BSC receives CIPHER MODE

COMMAND from MSC, zxgT5 starts.

B. Stop conditions of the timer: When BSC receives CIPHER MODE

COMPLETE from MS, zxgT5 stops.

C. Timeout: When zxgT5 expires, BSSAP CIPHER MODE REJECT is sent to

MSC.



Value Time length

50 5.0s


Page 220 of 516

51 5.1s

… …

120 12.0s

Default: 100

22) zxgT6: Supervises the SAPI3 link establishment.

Description: The zxgT6 timer supervises the SAPI3 link establishment.

A. Start conditions of the timer: When BSC receives the “DTAP (SAPI=3)”

message from MSC but no SAPI3 link, the zxgT6 timer starts.

B. Stop conditions of the timer: When BSC receives “ESTABLISH CONFIRM”

message from BTS, zxgT6 stops.

C. Timeout: When the zxgT6 timer expires, the “BSSMAP SAPI”n” REJECT”

message will be sent to MSC.



Value Time length

10 1.0s

11 1.1s

… …

300 30.0s

Default: 100

23) zxgT7: The protection time to wait for P0 to respond to the assignment or

handover complete message.

Description: The protection time to wait for P0 to respond to the assignment

or handover complete message.

A. Start conditions of the timer: After the Pn instance sends HO ROD to the P0

instance, zxgT7 starts.

B. Stop conditions of the timer: Pn receives HO CMD from P0.




Page 221 of 516

Value Time length

1 0.1s

2 0.2s

… …

200 20.0s

Default: 100

24) zxgT8

Description: External handover protection time.


Default: 100

25) zxgT9

Description: The protection time for the RF channel release.

A. Start conditions of the timer: Pn instance sends RF CHL REL to BTS when it

is released.

B. Stop conditions of the timer: Pn instance receives the response from BTS.



Value Time length

10 1.0s

11 1.1s

… ….

50 5.0s

Default: 20

26) zxgT10: The protection time for channel request queuing.

Description: The protection time for channel request queuing.



Value Time length


Page 222 of 516

50 5.0s

51 5.1s

… …

200 20.0s

Setting: T10 > T3109 + T3111 + T9103 or T10 > T11 /Tqho should be

ensured in case queuing is allowed.

Default: 130

27) zxgT11: Assignment queue period

Description: The maximum allowed queuing time for assignment attempts,

calculated from the assignment request.



Value Time length

1 0.1s

2 0.2s

… …

150 15s


Default: 60

28) zxgT12: The interval for periodical status confirmation.

Description: The interval for periodical status confirmation.

A. Start conditions of the timer: After Pn receives the “CONNECT CONF” from

P0 and decides to perform the peer activity checking, the timer is started for

the first time. And then, it will be periodically started.

B. Stop conditions of the timer: Pn instance receives the release message.


Default: 200

29) zxgT13: Supervises the mode modify procedure of BTS and MS.

Description: The zxgT13 timer supervises the mode modification process of

BTS and MS.


Page 223 of 516

A. Start conditions of the timer: When BSC sends the “MODE MODIFY”

message to BTS and sends the “CHANNEL MODE MODIFY” message to

MS.

B. Stop conditions of the timer: When BSC receives “MODE MODIFY

ACK/NACK” message from BTS and the “CHANNEL MODE MODIFY”

message from MS.

C. Timeout: When zxgT3 timer expires, a “BSSMAP ASSIGNMENT FAILURE”

message is sent to MSC.



Value Time length

50 5.0s

51 5.1s

… …

120 12.0s

Default: 100

30) zxgT14

Description: The time from the “Ass/Ho Com” sent to the “Ass/Ho Com Ack”

received by the target instance.


Default: 60

31) zxgT15: The available time to wait for resources by the target instance in

the case of forced release. Description: The available time to wait for resources by the target instance

in the case of forced release..

A. Start conditions of the timer: The target instance decides forced release and

sends PREEMPT APPLY to the object to be disconnected.

B.Stop conditions of the timer: The target instance receives RESOURCE

AVAILABLE from the disconnected object, indicating that the resources are

available.



Page 224 of 516


Value Time length

60 6.0s

61 6.1s

… …

120 12.0s

Setting: T15 > T3109 (10) + T3111 (0.1)

Default: 60

32) zxgT16: The waiting time for directed retry.

Description: The waiting time for directed retry.



Value Duration represented

20 2s

21 2.1s

… …

60 6s


Default: 20

33) rmsTaho: The handover queuing period

Description: The maximum allowed queuing time for handover attempt,

calculated from the handover request.


Table 6-33 The value range of msTqho

Value Time length

1 0.1s

2 0.2s

…

150 15s


Page 225 of 516


Default: 60

34) zxgmT7: The external handover protection time.

Description: The external handover protection time. After BSS requests for

external handover, it will receive the “HO REJECT” message from MSC.

BSS must wait for some time (zxgmT7) before it can receive other

commands related to handover.zxgmT7 < T7.


Table 6-34 The value range of zxgmT7


1 0.1s

2 0.2s

…

65535 6553.5s

Setting: 100 by default.

35) zxgmT11

Description: A clock that is adopted when flow control is applied due to the

cell overload. This clock is used together with zxgmT12 to modify the

“ACCESS CONTROL” parameter configured in the cell, and notify this in the

system information to MS, therefore to achieve flow control. The set value of

the clock must be less than zxgmT12.


Default: 100

36) zxgmT12

Description: A clock that is adopted when flow control is performed due to

the cell overload. This clock is used together with zxgmT11 to modify the

“ACCESS CONTROL” parameter configured in the cell, and notify this in the

system information to MS, therefore to realize flow control. The set value of

the clock must be greater than zxgmT11. The procedure for the two clocks

to control the cell traffic is as follows: When the network side receives the

overload message for the first time, the system lowers the traffic by one


Page 226 of 516

level and starts zxgmT11 and zxgmT12. The “OVERLOAD” message

occurring during zxgmT11 will be ignored. If the “OVERLOAD” message is

received between zxgmT11 and zxgmT12, the flow will be decreased by

another level and the zxgmT11 and zxgmT12 will be restarted. If zxgmT12

still does not receive the “OVERLOAD” message after expiry of zxgmT12,

one level of flow will be increased, and then, zxgmT12 will be restarted. The

illustration for the two clocks that control cell flow is as shown in Fig. 6-7:

BTS BSC

overload

overload

overload

zxgmT11

zxgmT12

Fig. 6-7 The illustration for the two clocks to control the cell flow


Default: 150

37) Tmicro: The delay timer for micro-micro handover

Description: In the micro-micro handover control, a delay time length value

is required (the timer value). When a call enters a micro cell, the related

timer will be started, and before the timer expires, it is not allowed to hand

over to the neighboring cells in the same layer (any algorithm). Only when

the timer expires, the micro cell in the same layer of the neighboring cell can

be used as the candidate cell. In this way, the fast moving mobiles staying in

the micro cell layer can be avoided.


Table 6-35 The value range of Tmirco

Value Time length


Page 227 of 516

0 0s

1 0.1s

…

65535 6553.5s

Default: 100

Setting: The setting of this parameter is related to the standard that is used

to measure the average size of the micro cell and the moving speed of the

mobile.

38) T6101: The immediate assignment period.

Description: T3101 supervises the immediate assignment process.

A. Start conditions of the timer: When BSC sends IMMEDIATE ASSIGNMENT

COMMAND, T3101 starts.

B. Stop conditions of the timer: When “ESTABLISH INDICATION” message is

received from MS, T3101 stops.

C. Timeout: When the T3101 timer expires, BSC will send the “CHANNEL

RELEASE” message to BTS.




10 1s

11 1.1s

12 1.2s

… …

50 5s


Default: 30

39) T3103: Source cell handover period

Description: The T3101 timer supervises the internal handover process of

BSC.

A. Start conditions of the timer: When BSC sends “HANDOVER COMMAND”


Page 228 of 516

message to MSC, T3103 starts.

B. Stop conditions of the timer: When BSC receives the “HANDOVER

COMPLETE” message on a new channel or the “HANDOVER FAILURE”

message on the old channel from MS, the timer T3103 stops.

C. Timeout: When the timer T3103 expires, a “CLEAR REQUEST” message

will be sent to MSC, and the new channel will be released.




35 3.5s

36 3.6s

37 3.7s

… …

100 10s


Setting: When setting this timer, T3103 shall be less than T10.

Default: 60

40) T3107: Assignment period

Description: T3107 is used to supervise the assignment process and the

internal handover of a cell (< T10).

A. Start conditions of the timer: When BSC sends “RIL3_RR ASSIGNMENT

COMMAND” message to MS, T3107 starts.

B. When BSC receives the “RIL3_RR ASSIGNMENT COMPLETE” message

or “RIL3_RR ASSIGNMENT FAILURE” message, the timer T3107 stops.

C. Timeout: When T3107 expires, for the assignment procedure, the old and

new channels will be released, the corresponding MS connection will be

cleared, and a “BSSAP ASSIGNMENT FAILURE” message will be sent to

MSC; for intra-cell handover procedure, a “CLEAR REQUEST” message will

be sent to MSC.



Page 229 of 516



35 3.5s

36 3.6s

37 3.7s

…

100 10s


Setting: When setting this timer, T3107 shall be less than T10.

Default: 60

41) T3109: Channel release period.

Description: T3109 supervises the channel release process.

A. Start conditions of the timer: When BSC sends “RIL3_RR CHANNEL

RELEASE” message to MS, T3109 starts.

B. Stop conditions of the timer: When BSC receives the “RELEASE

INDICATION” message from BTS (when BTS receives DISC frame from

MS), the timer T3109 stops.

C. Timeout: When the T3109 timer expires, BSC will send the “RF CHANNEL

RELEASE” message to BTS.




80 8s

81 8.1s

82 8.2s

…

150 15s


Default: 120


Page 230 of 516

42) T3111: Channel deactivation delay

Description: After the Um interface radio link layer is released, a protection

time T3111 is set to ensure the radio link layer is disconnected. The radio

channel will be released and deactivated after the T3111 timer expires.

A. Start conditions of the timer: When BSC receives “RELEASE INDICATION”

message, T3111 starts.

B. Timeout: When T3111 expires, the “RF CHANNEL RELEASE” message is

sent to BTS.




1 0.1

2 0.2

…

5 0.5s


Default: 1

43) Tbsic: Tbsic: BSIC decode period

Description: The “Tbsic” parameter defines a period, which is calculated

from the call establishment or handover complete (inter-cell or intra-cell).

TC/I evaluation is considered as incredible during this period, thus, it is not

allowed to handover to a special TRX. During this period, MS can decode

BSICs that interfere with (neighboring) cells before the handover decision

takes place.


Table 6-41 The value range of Tbsic

Value Time length

5 0.5s

10 1.0s

…


Page 231 of 516

640 64.0s

Default: 50

44) AisT1

Description: AppAssignReq-AppAssignCom”, the “Assigning” status

protection timer. Before sending “App_Ass_Req” and receiving the

“App_Ass_Com”, it is in the “Assigning” status.


Default: 100

45) AisT4

Description: AppRadioApp-AppRadioAvail” (handover from the external),

the “RadioApplying” status protection timer. After receiving the message

“A_Ho_Req” and before receiving the “APP_RADIO_AVAIL”, it is in the

“RadioApplying” status.


Default: 100

46) AisT12

Description: Timer for protecting the Serving status. It is in Serving status

after CR is sent and CC is received and before any further message is

received; or after the “App Ass Com” message is received and before the

call is cleared; or after the “App Ho Com” message is received at the

handover from the external and before the call is cleared.


Default: 200

47) AisT8

Description: AisT8 is the “OutGoHoing” status protection timer when the

HoCmd (sending the “AppHOCmd” to Rms)- ClearCmd is received. After

receiving the “A_Ho_Cmd” to start the external handover and before the

“A_Clear_Cmd” is received once the handover is successful, it is in the

“OutGoHoing” status.


Default: 80


Page 232 of 516

3. GPRS Max

See Fig. 6-8 for the setting of the GPRS maximum reattempts.

Fig. 6-8 Configuring BSC (3)

1) BVCBlkMax

Description: BSSGP layer parameter. If the PTP BVC needs to be blocked

due to OAM intervention or device faults (disable the blocking and

unblocking of signaling BVC), BSS will first set the BVC status to “Blocked”

and discard the uplink service data. To notify SGSN to stop sending the

downlink data, BSS will also initiate the “BVC blocking” procedure. After

sending the “BVC block” message to SGSN, if it fails to receive the “BVC

BLOCK ACKNOWLEDGE” message from SGSN in BSSGPT1, it will repeat

the “BVC blocking” procedure. “BVC blocking” can be repeated for a

maximum of N times. If for N times there is no answer, then BSC will stop

“BVC blocking” and notify OMS of such. N is determined by the maximum

reattempts of BVC BLOCK.


Setting: 3

2) BVCUBlkMax

Description: BSSGP layer parameter. If the PTP BVC needs to be


Page 233 of 516

unblocked due to the OAM intervention or recovery of the device faults

(disable the blocking and unblocking of signaling BVC), BSS will first set the

BVC status to “Unblocked”. To notify SGSN to start sending the downlink

data, BSS will also initiate the “BVC unblocking” procedure. After sending

the “BVC UNBLOCK” message to SGSN, if it fails to receive the “BVC

UNBLOCK ACKNOWLEDGE” message from SGSN in BSSGPT1, it will

repeat the “BVC unblocking” procedure. “BVC unblocking” can be repeated

for a maximum of N times. If for N times there is no answer, then BSC will

stop “BVC unblocking” and notify OMS of such. N is determined by the

maximum reattempts of BVC UNBLOCK.


Setting: 3

3) BVCResetMax

Description: BSSGP layer parameter. In case of 1} system faults that affect

the BVC function in BSS or SGSN (such as restart upon power-on); 2) lower

layer network service entity failure (such as frame relay fault); 3) lower layer

network service entity capability update (e.g., frame relay capability changes

from 0kbps to greater than 0kbps); 4) change of the corresponding

relationship between BVC and cell, to keep the initial status consistent

between the two BVC sides, the “Reset BVC” procedure must be initiated.

For faults that affect NSE, the “Signaling BVC reset” procedure is initiated;

For faults that affect a single BVC, the “PTP BVC reset” procedure is

initiated. After a “signaling BVC reset” is initiated, all the “PTP BVC reset”

under that NSE must be initiated. After sending the “BVC RESET” message

to SGSN, if it fails to receive the “BVC RESET ACKNOWLEDGE” message

from SGSN in BSSGPT2, it will repeat the “BVC reset” procedure. “BVC

reset” can be repeated for a maximum of N times. If for N times there is no

answer, then BSC will stop “BVC reset” and notify OMS of such. N is

determined by the maximum reattempts of BVC Reset.


Setting: 3

4) NSBlkMax

Description: NS link layer parameter. The maximum number of repetitions

during BSC blocking. When BSC sends the “NS BLOCK” message to SGSN,


Page 234 of 516

if the “NS BLOCK ACKNOWLEDGE” message sent by SGNS has not

been received in the specified NS_T1 time, the whole blocking process shall

be repeated. The “NS BLOCK” message can be repeated for a maximum of

N times. If for N times there is still no answer, then BSC will stop the

BLOCK procedure and notify OMS of such. N is determined by the

maximum reattempts of NS BLOCK.

Value range: 0 ~ 10

Setting: 3

5) NSUnBlkMax

Description: NS link layer parameter. The maximum number of repetitions

during BSC unblocking. After BSC sends the “NS UNBLOCK” message to

SGSN, if it fails to receive the “NS BLOCK ACKNOWLEDGE” message from

SGSN in the time specified by the timer NS_T1, the whole UNBLOCK

procedure shall be repeated. The “NS UNBLOCK” message can be

repeated for a maximum of N times. If for N times there is still no answer,

then BSC will stop the UNBLOCK procedure and notify OMS of such. N is

determined by the maximum reattempts of NS UNBLOCK.

Value range: 0 ~ 10

Setting: 3

6) NSAliveMax

Description: Maximum number of repetitions of the BSC Alive procedure.

After BSC sends the “NS Alive” message to SGSN, if it fails to receive the

“NS Alive ACKNOWLEDGE” message from SGSN in the time specified by

the timer NS_T4, the whole Alive procedure shall be repeated. The “NS

Alive” message can be repeated for a maximum of N times. If for N times

there is still no answer, then BSC will stop the Alive procedure and notify

OMS of such. N is determined by the maximum reattempts of NS Alive.

Value range: 0 ~ 20

Setting:

7) SuspendMax

Description: BSSGP layer parameter. When the Class B GPRS MS is about

to initiate the voice service, the MS will first send a “SUSPEND” message to


Page 235 of 516

the BSS over SDCCH; after BSS receives it, it initiates the “Suspend”

procedure to SGSN for the purpose of notifying SGSN to stop sending “PS

paging” and “downlink packet data”. After sending the “SUSPEND”

message to SGSN, if it fails to receive the “SUSPEND ACK/NACK”

message from SGSN in BSSGPT3, it will repeat the “Suspend” procedure.

“Suspend” procedure can be repeated for a maximum of N times. If for N

times there is no answer, then BSC will stop “Suspend” and notify OMS of

such. N is determined by the maximum Suspend reattempts.


Setting: 3

8) ResumeMax

Description: BSSGP layer parameter. When the “GPRS-attached” MS is not

in the dedicated mode, BSS can adopt one of the following two policies: 1}

Notify MS to perform “Routing Area Update”; 2} Notify SGSN to “Resume”

the GPRS service. In case of “Routing Area Update”, then MS and SGSN

will directly negotiate “GMM status” and BSS need not do any thing. In case

of Resume (tailored to the MS in packet transmission status), BSS will

initiate the “Resume” procedure to SGSN for the purpose of notifying SGSN

to start the normal packet downlink transmission action. After sending the

“RESUME” message to SGSN, if it fails to receive the “RESUME

ACK/NACK” message from SGSN in BSSGPT4, it will repeat the “Resume”

procedure. “Resume” procedure can be repeated for a maximum of N times.

If for N times there is no answer, then BSC will stop “Resume” and notify

OMS of such. N is determined by the maximum Resume reattempts.

Value range: 0~255

Setting: 3

9) UpdateMax

Description: BSSGP layer parameter. When MS is establishing the

uplink/downlink TBF, to assign the appropriate packet channel to the MSs

that have different access capabilities, BSS needs to know the radio access

capability of that MS. If BSS does not have that information yet, then it can

obtain that information from SGSN by the “Radio Access Capabilities

Update” procedure. After sending the “RADIO ACCESS CAPABILITIES

UPDATE” message to SGSN, if it fails to receive the “RADIO ACCESS


Page 236 of 516

CAPABILITIES UPDATE ACK/NACK” message from SGSN in BSSGP T5,

then the procedure shall be repeated. The “Radio Access Capabilities

Update” procedure can be repeated for a maximum of N times. For N times

if there is still no answer, then BSC will stop the “Radio Access Capabilities

Update” procedure and notify OMS of such. N is determined by the

maximum Update reattempts.


Setting: 3

4. GPRS Timer

See Fig. 6-9 for the BSC GPRS Timer setting.


1) BSSGP T1 “BVC block/unblock” reattempt time

Description: Timer that monitors the BSSGP block/unblock procedure.

Parameter used by the global process in the central module MP. If a

point-to-point BVC block/unblock is required due to OAM intervention or

device faults, BSS will initiate the “BVC block/unblock” procedure. If SGSN

does not return “BVC BLOCK/UNBLOCK ACK/NACK” message, then the

“BVC block/unblock” procedure shall be repeated. The interval between

them is Bssgp T1.


Page 237 of 516

Value range: 10 ~ 300 (100ms)

Setting: 30

2) BSSGP T2 “BVC Reset” reattempt time

Description: Timer that monitors the reset procedure of BSSGP. Parameter

used by the global process in the central module MP. If the BVC (including

PTP BVC and signaling BVC) reset is required due to some reasons, BSS

will initiate “BVC Reset” procedure. If SGSN does not return “BVC RESET

ACK/NACK” message, then the “BVC Reset” procedure shall be repeated.

The interval between them is Bssgp T2.


Setting: 30

3) BSSGP T3 “Suspend” reattempt time

Description: Timer that monitors the Suspend procedure of BSSGP.

Parameter used by the service process in the peripheral module MP. When

the Class B MS is ready to perform the voice service, it will notify the

network to “Suspend” the packet service. After BSS receives the

“SUSPEND” message from MS, it will initiate the “Suspend SGSN”

procedure. If SGSN does not return “SUSPEND ACK/NACK” message, then

the “Suspend SGSN” procedure shall be repeated. The interval between

them is Bssgp T3.


Setting: 30

4) BSSGP T4 “Resume” reattempt time

Description: Timer that monitors the Resume procedure of BSSGP.

Parameter used by the service process in the peripheral module MP. When

the “GPRS-attached” MS is not in the dedicated mode and the BSS uses

“Notify SGSN to resume GPRS service” policy, BSS will initiate the

“Resume” procedure to SGSN. If SGSN does not return “RESUME

ACK/NACK” message, then the “Resume” procedure shall be repeated. The

interval between them is Bssgp T4.


Setting: 30


Page 238 of 516

5) BSSGP T5 “Radio Access Capabilities Update” reattempt time

Description: Timer that monitors the RA_CAPABILITY procedure of BSSGP.

Parameter used by the service process in the peripheral module MP. After

BSS initiates “RA_CAPABILITY” procedure to SGSN, if SGSN does not

return the “RA_CAPABILITY UPDATE ACK/NACK” message, then the

“Radio Access Capability Update” procedure shall be repeated. The interval

between them is Bssgp T5.


Setting: 30

6) NS T1

Description: Timer that monitors the block/unblock procedure at the NS

layer.

Value range: 1 ~ 120s

Setting: 60

7) NS T2

Description: Timer that monitors the reset procedure at the NS layer.


Setting: 60

8) NS T3

Description: The test period of NS-VC.


Setting: 30

9) NS T4

Description: Timer that monitors the alive procedure of the NSVC.

Value range: 3s

Setting: 3s by default.

10) NS T5 (not use

Description: The maximum attempt period of Reset.

Value range: 3 minutes


Page 239 of 516

Setting: 3*60s by default.

11) T3169

Description: BRP’s timer at the RLC/MAC layer. During the packet uplink

transmission, if the timer N3101 or N3103 expires, BSS will start the timer

T3169. When T3169 expires, the TFI and USF resources are released for

use by the network.

A. Start conditions of the timer: When N3101 = N3101_MAX or N3103 =

N3103_MAX.

B. Stop conditions of the timer: None.

C. Timeout: USF and TFI resources are released.

Value range: 0 ~ 0xFFFF (10ms)

Setting: 500 by default, i.e., 5 seconds.

12) T3191

Description: BRP’s timer at the RLC/MAC layer. During the packet downlink

transmission, if the BSN of the RLC data block to be transmitted is the

maximum (i.e., the final downlink data block), the network will send a RLC

data block whose Final Block Identifier (FBI) field is 1 and which includes

effective RRBP field to initialize the release of the downlink TBF. At this time

the network starts the timer T3191. For each RLC data block received

whose FBI is 1 and which includes effective RRBP field, 1) In acknowledged

mode, the MS should send the “PACKET DOWNLINK ACK/NACK”

message whose FAI field is 1 in the uplink block specified by the RRBP field.

If the network receives the “PACKET DOWNLINK ACK/NACK” message

before T3191 expires and is required to re-transmit it, then T3191 is stopped

and the required RLC data block is re-transmitted. If re-transmission is not

required, then T3191 is stopped and T3193 is started. When T3191 expires,

the network releases TBF. When T3191 expires, the network releases TBF

also; 2) In unacknowledged mode, the MS should send the “PACKET

CONTROL ACKNOWLEDGE” message in the uplink block specified by the

RRBP field. If the network receives the “PACKET CONTROL

ACKNOWLEDGE” message before T3191 expires, then T3191 is stopped

and T3193 is started. When T3193 expires, the network releases TBF.

When T3191 expires, the network releases TBF also.


Page 240 of 516



13) T3193

Description: BRP’s timer at the RLC/MAC layer. Used for protection at the

release of TBF during the packet downlink transmission. For details, see the

description of the timer T3191.

A. Start conditions of the timer: When the final “PACKET DOWNLINK

ACK/NACK” or “PACKET CONTROL ACKNOWLEDGE” message is

received.

B. Stop conditions of the timer: When the network has established a new

downlink TBF.

C. Timeout: TFI is released.


Setting: 51. The value of this parameter needs to be greater than T3192 for

ensuring the uniqueness of TFI of MS at one moment.

14) T3195

Description: BRP’s timer at the RLC/MAC layer. Protection time of TBF

when the radio link failure or the cell change leads to MS’s failure to

respond. During the packet downlink transmission, if the timer N3105

expires, BSS will start the timer T3195. When T3195 expires, the TFI

resource is available again for use by the network.

A. Start conditions of the timer: N3105 = N3105_MAX.

B. Stop conditions of the timer: None.

C. Timeout: TFI is released.



5. Other GPRS Property

See Fig. 6-10 for other properties setting of BSC GPRS.


Page 241 of 516


A. CELL Threshold of the Bssgp Flow Control

Description: This parameter is the trigger threshold for “BVC flow control”.

The BVC flow control is conducted in the Gb interface between SGSN and

BSS in the downlink only. In practice, BSS provides the control parameter

and SGSN executes it to avoid the situation that part of the LLC data is

discarded due to the timeout caused by packet channel busy in BVC

(excess LLS frames buffered) and that the new downlink LLC data is

discarded due to the limited memory resources (LLC frame buffer overflow).

The BSSGP process on the BSS side periodically (long or short) counts the

current leakage ratio of BVC. If the long count timer overflows, then the

“BVC flow control” procedure is initiated unconditionally. If the difference

between the two consecutive leakage ratios is more than CellFcThs, the

SGSN confirmation is also required. If the short count timer overflows and

the difference between the two consecutive leakage ratios is more than

CellFcThs, then the “BVC flow control” is initiated, which also needs the

SGSN confirmation.

Value range: 1 ~ 100 (%)

Setting: 80

2) MS Threshold of the Bssgp Flow Control

Description: This parameter is the trigger threshold for “MS flow control”.


Page 242 of 516

The MS flow control is conducted in the Gb interface between SGSN and

BSS in the downlink only. In practice, BSS provides the control parameter

and SGSN executes it to avoid the situation that part of the LLC data is

discarded due to the timeout caused by packet channel busy in MS

(excessive LLS frames buffered) and that the new downlink LLC data is

discarded due to the limited memory resources (LLC frame buffer overflow).

The BSSGP process on the BSS side periodically (long or short) counts the

current leakage ratio of MS. If the long count timer overflows, then the “MS

flow control” procedure is initiated unconditionally. If the difference between

the two consecutive leakage ratios is more than MsFcThs, the SGSN

confirmation is also required. If the short count timer overflows and the

difference between the two consecutive leakage ratios is more than

MsFcThs, then the “MS flow control” is initiated, which also needs the

SGSN confirmation.


Setting: 80

3) CELL Trigger Period of the Bssgp Flow Control

Description: This parameter is the BVC leakage ratio measurement period

at the “BVC flow control” procedure, i.e., BVC long measurement period. To

provide reference to the BVC flow control at the SGSN side, the BSSGP

process at the BSS side periodically measures the current BVC leakage

ratio. When the long measurement timer overflows, the “BVC flow control”

procedure is initiated unconditionally; if the difference of the leakage ratios

between the two times exceeds CellFcThs, it needs to be confirmed by

SGSN; if the short measurement timer overflows, and the difference of the

leakage ratio between the two times exceeds CellFcThs, then the “BVC flow

control” procedure is also initiated, which also needs to be confirmed by

SGSN. In the OMCR (V2) system, BVC short measurement period is equal

to BVC long measurement period divided by 3.

Value range: 0 ~ 0xffff (10ms)

Setting: 3000

4) MS Trigger Period of the Bssgp Flow Control

Description: This parameter is the MS leakage ratio measurement period at

the “MS flow control” procedure, i.e., MS long duration measurement period.


Page 243 of 516

To provide reference to the flow control at the SGSN side, the BSSGP

process at the BSS side periodically measures the current leakage ratio of

each MS. When the long measurement timer overflows, the “MS flow

control” procedure is initiated unconditionally; if the difference of the leakage

ratios between the two times exceeds MsFcThs, it needs to be confirmed by

SGSN; if the short measurement timer overflows, and the difference of the

leakage ratio between the two times exceeds MsFcThs, then the “MS flow

control” procedure is initiated, which also needs to be confirmed by SGSN.

In the OMCR (V2) system, MS short measurement period is equal to MS

long measurement period divided by 3.


Setting: 3000

5) N3101: Maximum allowed number of continuous losses of uplink data

blocks

Description: This is the parameter used at the RLC/MAC layer of BRP.

During the packet uplink transmission, BSS will specify USF (corresponding

to one uplink TBF) for each uplink block. For a USF, if the network receives

the correct data from the specified uplink block, then the timer N3101 is

cleared for that TBF; if the number of losses in the specified uplink block

exceeds N3101, then timer T3169 is started. When T3169 expires, the TFI

and USF resources are available again for use by the network.


Setting: 10

6) N3103: Number of “Packet Uplink ACK/NACK” reattempts


During the packet uplink transmission, if the network detects that the uplink

TBF ends (CV=0 and V(Q)=V(R) ) and that all the RLC data blocks have

been received, the network will send a “PACKET UPLINK ACK/NACK”

message and mark the Final Acknowledgement Identifier (FAI) as 1. The

header of the RLC/MAC control block contains a valid RRBP field. And the

counter N3103 is cleared. If the MS receives the “PACKET UPLINK

ACK/NACK” message whose FAI is 1 from the network side, then it will

send the “PACKET CONTROL ACKNOWLEDGE” message in the block

specified by the RRBP and release TBF. If the network fails to receive the


Page 244 of 516

“PACKET CONTROL ACKNOWLEDGE” message in the radio block

specified by the RRBP field, then the value of the counter N3103 is

incremented and the “PACKET UPLINK ACK/NACK” message is

retransmitted. If the value of N3103 exceeds the limiting N3103max, the

network will start T3169. When T3169 expires, the TFI and USF resources

are available again for use by the network.


Setting: 10

7) N3105: Allowed maximum number of continuous losses of the uplink

“RLC/MAC CONTROL” message


During the packet downlink transmission, BSS will set RRBP field in the

downlink RLC data block at a certain interval to notify MS to send the

“RLC/MAC CONTROL” message in the corresponding uplink block. For a

TBF, if the number of consecutive losses of the “RLC/MAC CONTROL”

message in the specified uplink block exceeds N3105max, then the timer

T3195 is started. When T3195 expires, the TFI resource is available for use

by the network.


Setting: 10

8) MS CSMode

Description: This parameter refers to the channel coding mode.


Table 6-42 The value range of “MS CSMode”

Value Coding mode

0 CS-2 by default, but the coding mode may vary dynamically between CS-2 and CS-1.

1 CS-1

2 CS-2

3 CS-3

4 CS-4

Setting: 1


Page 245 of 516

9) Cn Level: for determining the increase of the level of the coding mode


Unlike the unified coding mode of the circuit channel, the GPRS data block

may use the CS-1 to CS-4 coding modes, whose data rates are 9.05kbps,

13.4kbps, 15.6kbps, and 21.4kbps respectively. The low level coding mode

has higher error correction capability and lower data throughput. You can

choose different coding modes for each timeslot or even each TBF. At the

transmission of the GRPR data, to reach the maximum radio throughput, the

network will select the coding mode dynamically according to the data rate

requirement and radio transmission quality. Good radio transmission quality

means that the probability of retransmitting the errored radio blocks is small.

At this time the coding mode that carries large data volume (i.e., high level

coding mode) can be used. When the number of data blocks transmitted

consecutively and correctly in the coding mode CSn (1 n 3) for TBF (uplink

and downlink) exceeds the predefined parameter Cn[n-1], the coding level is

increased by one level.


Setting: 10

10) Nn Level: for determining the decrease of the level of the coding mode




13.4kbps, 15.6kbps, and 21.4kbps, respectively. The low level coding mode





requirement and radio transmission quality. When the radio transmission

quality is poor, the coding mode with higher anti-interference capability (i.e.,

low level coding mode) should be used. If of the Nn[n-2] data blocks

transmitted, the number of consecutive losses of the data blocks in the

coding mode CSn (2 n 4) for the TBF (downlink and uplink) is Xn[n-2]%,

the coding level is decreased by one.



Page 246 of 516

Setting: 20

11) Xn Level: threshold for determining the decrease of the level of the coding

mode Description: This is the parameter used at the RLC/MAC layer of BRP.



13.4kbps, 15.6kbps, and 21.4kbps, respectively. The low level coding mode





requirement and radio transmission quality. When the radio transmission

quality is poor, the coding mode with higher anti-interference capability (i.e.,

low level coding mode) should be used. If of the Nn[n-2] data blocks

transmitted, the number of consecutive losses of the data blocks in the

coding mode CSn (2 n 4) for the TBF (downlink and uplink) is Xn[n-2]%,

the coding level is decreased by one.


Setting: 80

12) NSVC Delay

Description: This is a NS link layer parameter. NSVC is an end-to-end

concept. The NSVC delay is the basis for flow control in frame relay. It is

configured in the background subject to the actual circumstances.

Value range: 1 ~ 20ms

Setting: 10ms

13) Fail Report Period (52 Frames)

Description: This parameter is the report period for the channel failure ratio

(52 multiframes)


Setting: 10

14) PS Overload Th

Description: This parameter is used by the database in the peripheral

module MP. The allocation of the uplink and downlink PS radio resources of


Page 247 of 516

the GPRS takes two steps: The first step allocates the timeslot, that is, the

PDCH channel. This is carried out by the database in the MP; the second

step allocates the RLC/MAC data block resources in each channel. This is

implemented by the packet control module. In MP, to prevent one PS

channel from being used infinitely, the system sets a “Maximum bearing

rate” threshold for the packet channel. If the bearing rate of that packet

channel has exceeded that threshold, it is set in “Channel busy” state. The

succeeding packet access will not take that channel into account, hence

avoiding the occurrence of congestion from the timeslot level.

Value range: 0 ~ 65535 (100bps)

Setting: 65535

15) Default Access

Description: This parameter is used by the database in the peripheral

module MP. At the initial access of the MS (especially the first step (channel

request) of the two-stage access procedure), it may not have the resource

request information. The network side will allocate the PS channel at the

default rate. Also, during the TBF establishment, the resource rate is less

than DefRate, the database will not take the extra timeslot capability of the

MS into account but allocate a single PS channel to it for utilizing the

channel resources effectively.

Value range: 0 ~ 65535 (100bps)

Setting: 10


Page 248 of 516

6.1.2.2 Creating PCM circuit

Select “BSS” node in the browse tree of the main interface shown in Fig. 6-2 and right click to select “Configure PCM Circuits” in the pop-up menu, as illustrated in Fig. 6-11.

Fig. 6-11 Configure PCM circuits

1. PCM Circuit No.

Description: Used to identify the connection relationship between

management units.

Value range: 1 ~ 384.

2. Relevant PCM Equipment

Description: Used to indicate the relationship between the management

functional entity and the physical equipment entity that implements the

specific function. The configuration of standby equipment can point to the

related standby equipment via the assignment of this attribute value.

Value range: Complex unit number –unit number –PCM number


Page 249 of 516

6.1.2.3 Creating LAPD link

Select “BSS” node in the browse tree of the main interface shown in Fig. 6-2 and right click to select “Configure LAPD Link” in the pop-up menu, as illustrated in Fig. 6-12.

Fig. 6-12 Configure the LAPD link

1. LAPD Link No.

Description: Used to define the logic LAPD connection on the physical

signaling link of the Abis interface. Here O&M and Telecom signaling are

included. The LAPD link object is associated with one PCM time slot via the

AbisSigChannel attribute.


2. PCM No. (Pcm No.)

Description: This parameter represents the PCM circuit number of the LAPD

signaling link on the Abis interface.


3. Ts No.

Description: This parameter represents the PCM time slot of the LAPD

signaling link on the Abis interface.

Value range: 0 ~ 31

4. Local Terminal Identity (Tei)


Page 250 of 516

Description: Local terminal number.

Value range: 0 ~ 4

6.1.2.4 Configuring the base station

Select “BSS” in the browse tree of the main interface shown in Fig. 6-2 and right click to select “Create Logical Site” in the pop-up menu, as illustrated in Fig. 6-13.

Fig. 6-13 Configure the base station

To create a logic site is to create a base station.

Where:

1. BTS Index: the SITE number in the BSC it belongs to. One SITE can manage three cells at most.

2. BTS Username Alias: The name of the SITE in Chinese or symbols.

3. Resource Location Information: Description of the place where the BTS is

located.

4. Module No.: The Pn module number (radio module number) corresponding

to the cell.

5. Relation Physical Site DN: The DN of the physical site of the local BSS system: BssId-SiteId.


Page 251 of 516

6. Site Operation Preserve Channel: The logical Lapdlink corresponding to the

site.

6.1.2.5 Creating an external cell

Select “BSS” in the browse tree of the main interface shown in Fig. 6-2 and right click to select “Create External Cell” in the pop-up menu, as illustrated in Fig. 6-14 for GSM. For GPRS there are two tabs: Basic Property and GPRS Property. The former is shown in Fig. 6-15 and the later in Fig. 6-16.

Fig. 6-14 Configure External Cell – Basic Property (GSM)


Page 252 of 516

Fig. 6-15 Configure External Cell – Basic Property (GPRS)


Page 253 of 516

Fig. 6-16 Configure External Cell – GPRS Property (GPRS)

1. BCCH ARFCN:

Description: The ARFCN of BCCH carrier frequency of cells.


2. Mobile Country Code (MCC)

Description: MCC consists of three decimal digits, used to uniquely identify the home country of mobile subscribers (or systems).


Default: 460 (the MCC of China)

3. Mobile Network Code (MNC)


Page 254 of 516

Description: MNC consists of two decimal digits, which uniquely identifies a specific GSM PLMN network in a country (decided by MCC).

Value range: 0 ~ 99

Setting: If a country has more than one GSM public land mobile networks, each network should have a different MNC. Generally, MNC is uniformly allocated by the national telecom administration department, and the same operator can have one or more MNCs (depending on the service scale offered), but different operators cannot share the same MNC. At present, China has two GSM networks, China Mobile and China Unicom with the MNCs being 00 and 01 respectively.

Default: 00

4. Location Area Code (LAC)

Description: To determine the location of the mobile station, the coverage of each GSM PLMN can be divided into many location areas, and the location code is used to identify each location area. LAC is one of the parts to compose the LAI (LAI = MCC + MNC + LAC). One location area contains multiple cells.

Value range: 0x0001 ~ 0xFFFE (0xFFFE cannot be used)

5. Cell ID (CI)

Description: To uniquely indicate each cell in the GSM PLMN, network operators should allocate a unique code for each cell in a location area, that is, cell ID (CI).

Value range: 0x0000 ~ 0xFFFF

6. Network Color Code (NCC)

Description: NCC is one of the parts to compose the base station ID code (BSIC), i.e. BSIC = NCC + BCC. NCC is used to enable mobile stations to distinguish adjacent and different GSM PLMN cells. Normally, neighboring operators should have different NCCs. The parameter related to NCC is the “NccPermitted” parameter of the cell. By prohibiting MS to report relative NCC in the cell, MS is disabled to measure the cell information of the related operators.


Page 255 of 516

Actually, NCC occupies three bits. NCC is one of the network identification parameters.

Value range: 0 ~ 7

Setting: Normally, neighboring GSM PLMN should select different NCCs.

7. BS Color Code (BCC)

Description: BCC is one of the parts to compose the base station ID code (BSIC), i.e. BSIC = NCC + BCC. Normally, BCC is used to enable mobile stations to distinguish adjacent cells with the same BCCH carrier frequency and belonging to the same GSM PLMN. In addition, the GSM specifications stipulate that the TSC (Training Sequence Code) of broadcasting channel of the cell be equal to cell BCC. BCC occupies three bits. BCC is one of the network identification parameters.

Value range: 0 ~ 7

Setting: It should be ensured that neighboring or adjacent cells using the same BCCH carrier frequency have different BSICs.

8. Handover PBGT Threshold

Description: According to GSM specifications, after a series of average values obtained, handover decision can be performed. IF the PBGT value of a neighboring cell is also a factor for the handover, the decision procedure is as follows: If the PBGT value of a neighboring cell is greater than the threshold value of that cell, then handover should occur. The handover reason is to find a more suitable cell. This parameter is the threshold that must be used at the handover decision when the adjacent cell wants to hand over to the cell via PBGT.


Table 6-43 The handover PBGT threshold and the value range

Handover PBGT threshold Value represented

0 -24dB

1 -23dB


Page 256 of 516

…

47 23dB

48 24dB

Default: 30

9. Handover Level Threshold

Description: According to GSM specifications, after a series of average values obtained, handover decision can be made. At the time of handover because of level, adjacent cells should be screened and sequenced according to the following principle: This parameter is the threshold that must be used during the handover decision when the adjacent cell wants to hand over to the cell via signal intensity.


Table 6-44 The handover level threshold and value range

Handover Level Threshold Value represented

0 -24dB

1 -23dB

…

47 23dB

48 24dB

Default: 24

10. Handover Quality Threshold

Description: According to GSM specifications, after a series of average values obtained, handover decision can be performed. At the time of handover because of quality, adjacent cells should be screened and sequenced according to the following principle: This parameter is the threshold that must be used during the handover decision when the adjacent cell wants to hand over to the cell via signal quality.


Table 6-45 The handover quality threshold and value range


Page 257 of 516

Handover quality threshold Value represented

0 -24dB

1 -23dB

…

47 23dB

48 24dB

Default: 22

11. Support SoLSA MS Access

Description: This parameter is broadcast to the MS in the SI4, SI6, and SI7 messages and in the PSI3 and Psi3bis messages of the local and neighboring cells. It is used by the network to prevent the MS from residing in the cell.

Value range: 0: The cell is not used as the SoLSA exclusive access; 1: The cell is used as the SoLSA exclusive access.

Setting: 0

12. LSA Mark

Description: This parameter is broadcast to the MS in the SI4, SI6, SI7, and

PSI3 messages and in the PSI3 and Psi3bis messages of the neighboring

cells. It specifies the LSA identifier of the cell.

Setting: Determined by the network operator after the planning.

13. RAC

Description: Like the GSM system using the location area to manage a

group of cells, the GPRS system further divides the location area to several

routing areas that are identified by RAI (MCC+MNC+LAC+RAC). In case of

MS cell reselection in attach state, if the RAIs of the old and new cells

change, “Routing area update” procedure is initiated. The MS and SGSN in

Standby state know the routing area information, thus when the network has

the packet data or circuit data to transmit, it pages the MS in that routing

area. RAI cannot span more than one SGSN.


Setting: Uniformly planned by the network operator.

14. MS Min RxLev to Access


Page 258 of 516

Description: Parameter used on the MS side. This parameter is broadcast to

the MS in the PSI3 message of the local cell and PSI3 and Psi3bis

messages of the neighboring cells. This parameter specifies the minimum

receiving level for the MS to access the GPRS. To prevent the MS from

accessing the system in case of the low receiving signal level (usually, the

communication quality cannot guarantee normal communication after

access), and from unreasonably wasting the radio sources of network, it is

prescribed in the GSM system that the receiving level must be larger than a

threshold when the MS needs to access the network, that is: MS Min RxLev

to Access (the minimum receiving level for allowing the MS to access the

network). In addition, it is also one of the discrimination standards (a

parameter to calculate C31 and C32) for MS to make the cell selection and

the cell reselection.


Table 6-46 The value range of “MS Min RxLev to Access”

Value Corresponding level value (dBm)

0 < -110

1 -110 ~ -109

2 -109 ~ -108

… …

61 -50 ~ -49

62 -49 ~ -48

63 > -48

Setting: Generally, the recommended value should be approximate to

the MS receiving sensitivity, and for some cells with traffic overload, the

cell “RxLevAccessMin” may be increased appropriately, so as to

decrease the C1 and C2 values of the cell and the cell effective

coverage range of the cell; but, the “RxLevAccessMin” value cannot be

too large, or, the “blind spot” will be caused at the cell boundaries. When

the measure is adopted to balance the traffic, it is recommended that

the level value not exceed -90dBm.At the network’s preliminary running

stage, this parameter can be set as 10 (i.e., -101dBm~-100dBm) or

lower, which is higher than the MS’s receiving sensitivity -102dBm;

When the network capacity is expanded or the radio coverage is not a


Page 259 of 516

problem, the parameter of the cell can be increased by 2 (dB). Therefore,

the default value of this parameter can be set as 12 (-99dBm~-98dBm).

15. MS Max TxPwr Before Network POC

Description: Parameter used on the MS side. This parameter is broadcast to

the MS in the PSI3 message of the local cell and PSI3 and Psi3bis

messages of the neighboring cells. The transmitting power of MS is

controlled by the network during its communication with BTS. The network

controls the MS power by the power command and the MS must use the

transmitting power specified by the network as its output power. If the MS

cannot output that power value, then it uses the power that is closest to the

specified value as its transmitting power. When the MS is receiving PBCCH,

the power before the MS receives the network power control information is

determined by GPRS_TXPWR_MAX_CCH. This parameter is also a

parameter for cell selection and reselection by MS, involving in calculation

of C1 and C2 values.


Table 6-47 The Value range of “MS Max TxPwr Before Network POC”

Value MS output power (dBm)

GSM900


GSM1800

0~2 39 29 36

3 37 30 34

4 35 31 32

5 33 0 30 …

… 1 28

16 11

…

…

17 9 13 4

18 7 14 2

19~31 5 15~28 0

Setting: If this parameter is set too large, the MSs near BTS will interfere the neighboring channels. If it is too small, the MSs at the cell boundary will have low access success rate. The principle of setting this parameter is as follows: Under the precondition that the MS at the cell boundary is guaranteed with a certain access


Page 260 of 516

success rate, the MS access level should be reduced as much as possible. The value of this parameter is 5 (for GSM900MS) and 2 (for GSM1800MS). In practical applications, after the parameter is set, you can test it in the experiment mode, that is, make a dial test at the cell boundary, and test MS access success rate and access time with different parameter settings so as to determine whether to increase or decrease the value of the parameter.

16. Offset (dB)

Description: a parameter used on the MS side. It is broadcast to the MS in

the Adjacent Cell option of the PSI3 message. In the GPRS system, the cell

reselection shall adopt C32 as the standard. Similar to the C2 standard in

GSM, the calculation of the C32 standard also involves a cell reselection

offset parameter (ReselOff). When the parameter value is 0dB, the packet

system message may or may not contain it.


Table 6-48 The value range of the offset

ReselOffset The related level value represented (dB)

0 -52dB

1 -48dB …

…

31 +48dB


17. Temp Offset (dB)

Description: Parameter used on the MS side. It is broadcast to the MS in the

PSI3 message. In the GPRS system, the cell reselection adopts C32. Like

the C2 in the GSM system, there is a temporary offset “TempOffset” in the

C32 that provides a negative offset. The effective time is determined by the

“Penalty Time” parameter.


Table 6-49 The Value range of “Temporary Offset”

Value The related level value represented (dB)


Page 261 of 516

0 0

1 10

2 20

3 30

4 40

5 50

6 60

7 Infinity

Setting: Preferably set the same as the offset in the C2 standard of the

GSM system.

18. Penalty Time (10s)

Description: Parameter used on the MS side. It is broadcast to the MS in the

PSI3 message. In the GPRS system, the cell reselection adopts C32. Like

the C2 in the GSM system, there is a temporary offset “TempOffset” in the

C32 that provides a negative offset. The effective time is determined by the

“Penalty Time” parameter.


Table 6-50 The Values of “Penalty Time”


0 10s

1 20s …

…

31 320s


19. HCS parameters

Description: Parameter used on the MS side. They belong to the

Hierarchical Cell Structure (HCS) parameters and are broadcast to the MS

in the PSI3 message, to indicate whether the HCS parameters (PrioClass

and HCS_THR) exist in the cell. If the local cell does not use HCS

parameters, the HCS parameters of other cells will also be ignored, that is,

all the cells use the HCS signal strength threshold of infinity.

Value range: 0: Not use HCS parameters; 1: Use HCS parameters.


Page 262 of 516


20. Level Threshold

Description: Parameter used on the MS side. It belongs to HCS parameter

and is broadcast to the MS in the PSI3 message of the local cell and

neighboring cells. It shows the HCS signal strength threshold of the cell.



Page 263 of 516

Table 6-51 The value range of “Level Threshold”

Value Corresponding HCS signal intensity threshold value

0 -110dB

1 -108dB …

…

63 -48dB


21. Priority

Description: Parameter used on the MS side. It belongs to the HCS

parameter and is broadcast to the MS in the PSI3 message, showing the

HCS priority of the cell.

Value range: 0 ~ 7


22. Cell Reselection Status

Description: This parameter belongs to HCS parameter and is broadcast to

the MS in the PSI3 message. It shows the cell reselection status.

Value range: 0: Restrict the cell reselection; 1: Allow cell reselection.

6.1.3 Cell parameters

On the main interface shown in Fig. 6-2, select the “Logical Site” node, and right click to pop up two option menus “Modify” and “Create Cell”.

6.1.3.1 Configuring cell parameters

In the pop-up menu, select “Create Cell”. Then an interface will appear, which is as shown in Fig. 6-17 in the GSM environment and as shown in Fig. 6-18 in the GPRS environment.


Page 264 of 516

Fig. 6-17 Configuring a cell (1) – GSM

Fig. 6-18 Configuring a cell (1) –GPRS

1. Basic Params 1


Page 265 of 516

1) Cell No. (btsid)

Description: The logic BTS number inside a SITE. Here, one BTS is a cell or

a sector frequently mentioned in the network planning.

Value range: 1 ~ 3

2) Cell Type

Description: The type of the cell.


Table 6-52 The value range of the cell type

Value Cell Type

0 Umbrella cellular

1 macro-cellular

2 micro-cellular

3 micro-micro-cellular

4 Extension cell (TA>63)

Default: 1

3) Location Area Code (LAC)

Description: To determine the location of the mobile station, the coverage of

each GSM PLMN can be divided into many location areas, and the location

area code is used to identify different location areas. LAC is one of the parts

to compose LAI (LAI = MCC + MNC + LAC). One location area contains

multiple cells.

Value range: 0x0001 ~ 0xFFFF (0xFFFE cannot be used)

4) Cell ID (CI)

Description: To uniquely represent each cell in the GSM PLMN, network

operators should allocate a unique code for each cell in a location area, that

is, cell ID (CI).

Value range: 0x0000 ~ 0xFFFF

5) Network Color Code (NCC)

Description: NCC is one of the parts to compose the base station ID code

(BSIC) (BSIC = NCC + BCC), which is used to enable mobile stations to


Page 266 of 516

distinguish adjacent and different GSM PLMN cells. Normally, neighboring

operators should have different NCCs. The parameter related to NCC is the

“NccPermitted” parameter of the cell. By disabling MS to report relative NCC

in the cell, MS is disabled to measure the cell information of the related

operators. Actually, NCC occupies three bits. NCC is one of the network

identification parameters.

Value range: 0 ~ 7

Setting: Normally, neighboring GSM PLMN should select different NCCs.

6) Bts Color Code (BCC)

BCC is one of the parts to compose the base station ID code (BSIC) (BSIC

= NCC + BCC). Normally, BCC is used to enable mobile stations to

distinguish among neighboring cells with the same BCCH carrier frequency

and belonging to the same GSM PLMN. In addition, the GSM specifications

stipulate that the TSC (Training Sequence Code) of broadcasting channel of

the cell be equal to cell BCC. BCC occupies three bits. BCC is one of the

network identification parameters.

Value range: 0 ~ 7

Setting: It should be ensured that neighboring or adjacent cells using the

same BCCH carrier frequency have different BSICs.

7) Cell Frequency Band: The system supports three frequency bands. See

Table 6-53.

Table 6-53 The value range of the cell frequency band

Value Cell frequency band

900 GSM900: 890 ~915 MHZ (uplink)

935 ~ 960 MHZ (downlink)

EXT900 EGSM900: 880 ~915 MHZ (uplink)


DCS1800 GSM1800: 1710 ~1785 MHZ (uplink)


8) Reselect Hysteresis Power Level (CRH)

Description: When MS reselects the cell, if the original cell and destination

cell belong to different location areas, MS should initialize a location


Page 267 of 516

updating process after cell reselection. Due to the fading characteristic of

the radio channel, normally, the C2 values of two cells measured at the

adjacent cell boundary will have relatively great fluctuation, resulting in MS

to frequently reselect cells. Although the interval of reselecting two cells by

MS will be no less than 15s, it is extremely short in terms of location

updating. It not only dramatically increases the signaling flow of networks,

while the radio resources can not be fully utilized, but also decreases the

call completion rate of the system due to paging unable to be responded

during MS location updating. To reduce the impact of this issue, one

parameter is set in the GSM specification, called cell reselection delay

hysteresis (CRH). It is required that the signal level of the adjacent cell

(location area is different from that of the local cell) be greater than that of

the local cell and that its difference be greater than the value specified by

the CRH. Only in this way, will MS start the cell reselection procedure. This

parameter is broadcast to the MS in the cell via the “RIL3_RR SYSTEM

INFORMATION TYPE3” and “TYPE4”, and is one of the cell selection

parameters.


Table 6-54 The value range of “Reselect Hysteresis Power Level”

Value The specified CRH level

0 0 dB

1 2 dB

2 4 dB

3 6 dB

4 8 dB

5 10 dB

6 12 dB

7 14 dB

Setting: Normally it is suggested to set ReselHysteresis as 4 or 5 (i.e. the

reselection hysteresis level is 8dB or 10dB). In the following cases, proper

adjustments are recommended. When the traffic is enormous in a place and

the signaling traffic overload often occurs, it is suggested to increase the

ReselHysteresis parameters of the adjacent cells belonging to different

LACs. When the overlap coverage of the adjacent cells belonging to


Page 268 of 516

different LACs is rather big, it is also suggested to increase the

ReselHysteresis parameters. If the coverage of adjacent cells belonging to

different LACs is bad at the joint places, i.e. the coverage hole appears, or if

this joint place is an area where there are few moving objects with low

speeds like the highway, etc., it is suggested to set the ReselHysteresis

parameter to 1~3 (i.e. the reselection hysteresis level is between 2dB and

6dB).

Default: 4

9) Ny1 Times: The maximum number of repetitions for sending physical

information messages

Description: In accordance with the GSM specifications, during

asynchronous handover process, BTS should send the “RIL3_RR

PHYSICAL INFORMATION” message to notify MS of the timing advance

that will be used by MS. After the “ RIL3_RR PHYSICAL INFORMATION”

message is sent once, BTS starts the timer T3105. If the timer expires and

cannot correctly decode the frames in the second layer (format A or format

B) or TCH frames, BTS will resend the “RIL3_RR PHYSICAL

INFORMATION” message and restart the timer T3105. The parameter Ny1

(the Max Number of Repetition) decides the maximum number of resending

times for the “RIL3_RR PHYSICAL INFORMATION” message. This

parameter is one of the configuration parameters of BTS.

Value range: 5 ~ 35

Default: 5

10) Notification CCCH Message Period

Description: In accordance with the GSM specifications, when the CCCH

channel (RACH and PCH channels) load level of BTS is over a threshold

value (overload) set by O&M, BTS will periodically send the “CCCH LOAD

INDICATION” message to BSC till the CCCH channel is no longer over the

threshold value. Among them, the period for sending the “CCCH LOAD

INDICATION” message is decided by this parameter, which is one of the

configuration parameters of BTS.

Value range: 1 ~ 255 (in the unit of 102TDMA frame)

Default: 10


Page 269 of 516

11) The RACH take powerlevel threshold (RbusyThs)

Description: The threshold for receiving signal level in the RACH bursts

period. If the value is exceeded (that is, less than - RachBusyThs dBm), it

will be considered as a busy RACH.


Table 6-55 The value range of “RACH take powerlevel threshold (RbusyThs)”


0 < -110

1 -110 ~ -109

2 -109 ~ -108 ...

...

61 -50 ~ -49

62 -49 ~ -48

63 > -48

Default: 40

12) TA Max.

Description: The Max. TA supported by the extended carrier frequency.


13) TA Allowed

Description: The permitted Max. TA that allows MS access to this cell.

Value range: It ranges between 0 and 219 for the extended cell and

between 0 and 63 for the common cell.

14) BCCH

Description: BCCH carrier frequency absolute frequency number.

Value range: According to the setting of the network plan report, the value is

taken within the frequency range set by the BSC broadcast range.

15) Radio Frequency

Description: The radio frequency set of the BTS.

Value range: Frequency set, and the value range of each frequency is the


Page 270 of 516

same as BCCH.

16) PLMN Table

Description: This indicates the PLMN table that allows MS to report the

measurement results.

Value range: 0 ~ 7

Default: 0 ~ 7

17) Support GPRS

Description: This parameter indicates if this cell supports GPRS.

Value range: 0: Not support; 1:Support.

Setting: Set according to the actual conditions.

18) NSE No. (Network Service Entity No.)

Description: At the BSSGP layer of the GPRS protocol stack, to facilitate the

management, each GPRS cell is assigned with one BSSGP Virtual

Connection (BVC) (NSEI+BVCI). Each BVC must belong to one NSE. Here,

NSE is the network service entity. It is numbered uniformly in the entire

network, marked with NSEI. Generally, one BSE is divided into one service

entity. Considering the scalability, the ZXG10 system also allows BSC to be

attached with several NSEs.

Value range: 0 ~ 0xFFFF


19) BVC No. (BSSGP virtual connection identifier)

Description: BSSGP Virtual Connection (BVC) provides an approach for the

communications among different BSSGP entities. The peer-to-peer

Point-to-Point (PTP), or Point-to-Multipoint (PTM) or inter-signaling entity

transmission of BSSGP PDU is based on BVC. Each virtual connection has

one identifier, i.e. BVCI. It enables the network service layer at the bottom

layer to route BSSGP PDU to the peer entity very effectively. In one NSE,

each GPRS cell can be identified by BVCI uniquely. One NSE has and only

has one piece of signaling BVC (BVCI=0).




Page 271 of 516

20) Route Area No.

Description: Like the GSM system, which uses the location area to manage

a group of cells, the GPRS system further divides one location area into

several routing areas that are identified by RAI (MCC+MNC+LAC+RAC). In

case of MS cell reselection in the attach state, if the old and new RAIs

change, the “Routing area update” process will be initiated. The MS and

SGSN in the Standby state know their routing area information. Thus, when

the network has the packet data or circuit service data to transmit, it will

page the MS in that routing area. RAI cannot cross SGSNs.



21) PUC MUnit No.

Description: The composite unit No. of SPCU corresponding to a cell.

Value range: 0 ~ 255. “0” indicates that the SPCU composite unit is not

configured.

22) BRP Group

Description: BRP group corresponding to a cell.

Value range: 1 ~ 6

2. Basic Params 2

The configuration of the cell basic parameters 2 is as shown in Fig. 6-19 in

the GSM environment while as shown in Fig. 6-20 in the GPRS

environment.


Page 272 of 516




Page 273 of 516

1) Survey Average Burst Count by RACH

Description: The number of bursts measured at RACH. If some receiving

signal levels of “AvgSlots” BPs are less than the RachBusyThs, the RACH

channel is overloaded. It is a parameter used by BTS.


Default: 60

2) Bss Link Layer Error Counter Maximal

Description: The maximum value of the counter S that measures the radio

link faults at the BSS side.

Value range: 0 ~ 15

Default: 15

3) Ms Link Layer Error Counter Maximal

Description: The maximum value of the counter S that measures the radio

link faults at the MS side.

Value range: 0 ~ 15

Default: 15

4) MS Get the Minimal Intensity When Visit this Cell

Description: It is the minimal receiving level that allows MS to access the

cell. To prevent MS from accessing the system when the level of the

receiving signal is quite low, in which case the satisfactory communication

quality cannot be provided and the radio resources of the network will be

wasted in vain, it is stipulated in the GSM system that when MS needs to

access the network, its receiving level must be bigger than one threshold

level, i.e. the Min. receiving level of MS when it is allowed to access the

network. Also, it is a decision criteria for MS to make cell selection and cell

reselection. The parameter will be broadcast to all the MSs in a cell via the

“RIL3_RR SYSTEM INFORMATION TYPE3” and “TYPE4” messages.

RxLevAccessMin is also one of the cell selection parameters.

Value range: 0 ~ 63.See Table 6-56.

Table 6-56 The value range of “MS Get the Minimal Intensity When Visit this Cell”


Page 274 of 516


0 < -110

1 -110 ~ -109 ...

...

62 -49 ~ -48

63 > -48

Setting: Generally, the recommended value should be approximate to the

MS receiving sensitivity, and for some cells with traffic overload, the cell

“RxLevAccessMin” may be appropriately increased, so as to decrease the

C1 and C2 values of the cell and the cell effective coverage; but, the

“RxLevAccessMin” value cannot be too large, otherwise, “blind spot” will be

caused at the cell boundaries. When the measure is adopted to balance the

traffic, it is recommended that the level value not exceed -90dB.At the

preliminary running stage of the network, this parameter can be set as 10

(i.e., -101dBm~-100dBm) or below, which is higher than the MS’s receiving

sensitivity (-102dBm). However, when the network capacity is expanded or

the radio coverage is not a problem in some areas, the parameter of related

cells can be increased by 2.

Default: 12 (-99dBm ~ -98dBm)

5) RACH Load Indication Threshold (RLIT)


channel (the RACH channel among them) load level of BTS is over a

threshold value (overload) set by O&M, BTS will periodically send the

“CCCH LOAD INDICATION” message to BSC till the CCCH channel is no

longer over the threshold value. Among them, the threshold is decided by

the “CcchLoadThs” parameter, which is one of the configuration parameters

of BTS.


Table 6-57 The value range of the RACH load indication threshold

Value Meaning

0 CCCH load percentage 0%

1 CCCH load percentage 1% ...

...



Page 275 of 516

6) PCH Load Indication Threshold (PLIT)


channel (the PCH channel among them) load level of BTS is over a

threshold value (overload) set by O&M, BTS will periodically send the

“CCCH LOAD INDICATION” message to BSC till the CCCH channel is no

longer over the threshold value. Among them, the threshold is decided by

the “CcchLoadThs” parameter. This parameter is one of the configuration

parameters of BTS.


Table 6-58 The value range of the PCH load indication threshold

Value Meaning


1 CCCH load percentage 1% ...

...



7) The Most Count of RACH Access Resend Last Time (MaxRetrans)

Description: When MS starts the immediate assignment process (such as

MS needs to update the location, originate a call or respond to the paging),

it will send the channel request message in the RACH channel to the

network. Since RACH is an ALOHA channel, the network enables the MS to

send multiple channel request messages before it receives the immediate

assignment message in order to improve the access success rate of MS,

and the maximum number of allowed resending times is decided by the

“MaxRetrans”. This parameter notifies the MS in the cell via “RIL3_RR

SYSTEM INFORMATION TYPE1”, “Type 2”, “Type 2bis”, “Type 3” and

“Type4” messages. The “MaxRetrans” is one of the control parameters of

the system.



Page 276 of 516

Table 6-59 The value range of “Most Count of RACH Access Resend Last Time

(MaxRetrans)”

Value MaxRetrans

0 1

1 2

2 4

3 7

Setting: You can refer to the following methods for setting MaxRetrans:

A. For the cell radius over 3km and the area with relatively less traffic, it can be

set as 3 (i.e. the maximum number of resending times is 7) to improve the

access success rate of MS.

B. For the cell radius less than 3km and the area with medium traffic, it can be

set as 2 (i.e. the maximum number of resending times is 4).

C. For the micro cellular, it is recommended to set it as 1 (i.e. the maximum

number of resending times is 2).

D. For the micro cell with heavy traffic and the cell with obvious congestion, it is

recommended to set it as 0 (i.e. the maximum number of resending times is

1).

Default: 2

8) MsTxPwrMax When Access (MTPMax)

Description: During the communication between MS and BTS, the

transmitting power is controlled by the network, the network sets the power

for MS via the power command and the command is transmitted on SACCH

(the SACCH has 2 header bytes, one is the power control byte and the

other is the timing advance). The MS must extract the power control header

from the downlink SACCH and takes the specified transmitting power as the

output power; if the power level of MS cannot output the power value, it will

output the closest transmitting power that can be outputted. Since the

SACCH is the associated channel signaling, it must be used with other

channels, such as SDCCH, TCH; thus, the MS power control by the network

actually begins after the MS receives SACCH. The power (i.e. the power

used when the channel request is sent on RACH) used by the MS before

receiving SACCH is decided by the control channel maximum power level


Page 277 of 516

“MsTxPwrMaxCch”. The “MsTxPwrMaxCch” is also a parameter for cell

selection and reselection by MS, involving in the calculation of C1 and C2

values. This parameter is broadcast to all the MSs in the cell via the

“RIL3_RR SYSTEM INFORMATION TYPE3” and “TYPE4” messages, and

is one of the cell selection parameters.


Table 6-60 The value range of “MsTxPwrMax When Access (MTPMax)”

GSM900 GSM1800



0 ~ 2 39 29 36

3 37 30 34

4 35 31 32

5 33 0 30 ...

...

...

...

17 9 13 4

18 7 14 2

19 ~ 31 5 15 ~ 28 0

Setting: If this parameter is set too large, the MS near BTS will interfere the

neighboring channels. If it is too small, the MS at the cell boundary will have

low access success rate. Principle of setting this parameter: On condition

that the MS at the cell boundary is guaranteed with certain access success

rate, the MS access level should be reduced as much as possible.

Obviously, the larger the cell coverage, the higher MS output power level is.

Normally, this parameter is recommended to be set as 5 (corresponding to

GSM900MS) and 0 (corresponding to GSM1800MS). In practical

applications, after the parameter is set, you can test it in an experiment

mode, that is, make a dial test at the cell boundary, and test MS access

success rate and access time with different parameter settings so as to

determine whether to increase or decrease the value of this parameter.

Default: 2

9) AGCH Model Count

Description: This is the number of blocks used for AGCH in the 51


Page 278 of 516

multiframes (BS-AG-BLK-RES). Table 6-61 shows the CCCH channel

information blocks contained in each BCCH multi-frame (51 frames

contained) in the case of different common control channel configurations.

Since the CCCH channels contain both the access grant channel and

paging channel, it must be set how many blocks out of the CCCH channel

message blocks on the network will be reserved for the access grant

channel. To make the MS know this configuration information, the system

message of each cell contains a configuration parameter, that is, the

BsAgBlkRes used for PCH can be calculated via “CCCHConf” and

“BsAgBlkRes”. This parameter can be dynamically adjusted during the

actual running according to the load status of various common channels.

This parameter is broadcast to all MSs in the cell via “RIL3_RR SYSTEM

INFORMATION TYPE3” message.


Table 6-61 The value range of “AGCH Model Count”

CCCH_CONF

BS_AG_BLK_RES

The number of AGCH blocks reserved in each

BCCH multi-frame

The number of PCH blocks reserved in

each BCCH multi-frame

0 0 3

1 1 2

2 2 1

1

Others (illegal) - -

0 0 9

1 1 8

2 2 7

3 3 6

4 4 5

5 5 4

6 6 3

Others

7 7 2

Setting: 1 (when CcchConf = 1), or 2 (CcchConf is not 1).

10) Call Team Account for Multiframe Count

Description: The number of multi-frames (BS-PA-MFRMS) of 51 TDMA


Page 279 of 516

frames of MS sent in the paging information to the same paging group. In

accordance with the GSM specifications, each mobile subscriber (i.e.

corresponding to each IMSI) belongs to one paging group, and each paging

group in every cell is corresponding to one paging sub-channel. MS

calculates its paging group in the light of its own IMSI, so that the paging

sub-channel location of the paging group can be calculated. In the practical

network, MS only “tunes in” the paging sub-channel to which it belongs and

ignores the contents of other paging sub-channels, and shuts off the power

supply of some hardware equipment in the MS so as to save the power

overhead of MS. The multi-frame quantity (BsPaMframs) of the paging

channel means how many multiframes will act as one cycle for the paging

sub-channel. Actually, the parameter determines how many sub-channels

will be allocated for the paging channel in a cell. This parameter is mainly

used by the MS to calculate its own paging group, so that the related paging

sub-channel can be monitored. This parameter is broadcast to all the MSs

in the cell via the “SYSTEM INFORMATION” message. BsPaMframs is

broadcast to the MS in the cell via the “RIL3_RR SYSTEM INFORMATION

TYPE3” message. BsPaMframs is one of the system control parameters.


Table 6-62 The value range of “Call Team Account for Multiframe Count”

Value The number of multi-frames cycled on the same

paging channel in the same paging group

0 2

1 3

2 4

3 5

4 6

5 7

6 8

7 9

Setting: On the condition of guaranteeing no overload for the paging

channel, the parameter should be as small as possible. Generally, for the

area with heavy traffic, this parameter should be set as 6 or 7 (i.e. 8 or 9

multiframes will be a cycle for the paging group). In the area with modest


Page 280 of 516

traffic, this parameter can be set as 4 or 5 (i.e. 6 or 7 multi-frames will be a

cycle for the paging group). For the area with very small traffic, this

parameter can be set as 2 or 3 (i.e. 4 or 5 multiframes will be a cycle for the

paging group).

Default: 2

11) The Most Time Interval of MR Resend at RACH (T3122)

Description: After the network receives the channel request message sent

by MS, if there is no proper channel to be allocated to the MS, the network

will send the “IMMEDIATE ASSIGNMENT REJECT” message to the MS. To

avoid the MS continuously sending the channel request that will result in

further congestion of radio channels, the timer parameter T3122 will be

contained in the “IMMEDIATE ASSIGNMENT REJECT” message, that is,

the waiting indication information element. After receiving “IMMEDIATELY

ASSIGNMENT REJECT”, MS must wait for a time indicated by T3122

before initiating a new call. This parameter is also one of the system control

parameters and is sent to MS in “IMMEDIATELY ASSIGNMENT REJECT”

message.


Table 6-63 The value range of “The Most Time Interval of MR Resend at RACH (T3122)”

T3122 Meaning

0 0s

1 1s

2 2s ...

...

255 255s

Setting: Generally, it is recommended to set the T3122 as 10 ~ 15s, and 15

~25s for the area with high density traffic.

Default: 10

3. Optional Params

The configuration of the cell optional parameters is as shown in Fig. 6-21 in


environment.


Page 281 of 516

Fig. 6-21 Configuring a cell (3) - GSM

Fig. 6-22 Configuring a cell (3) - GPRS

1) Allow IMSI attach/detach


Page 282 of 516

Description: Whether to allow IMSI Attach/Detach in a cell. IMSI detach

process means that the MS reports entering non-working status to the

network, that is, switch-off or the process to take the SIM card out from the

MS. The network (normally VLR) marks the IMSI subscriber in a

non-working status, and the called connection request of the subscriber will

be denied now, so it is unnecessary to page. Accordingly, the attach process

of IMSI means that the MS reports entering the working status to the

network or reinserting the SIM card into the MS, and the MS checks

whether the LAI where the MS is located is consistent with the original one

saved. If yes, the IMSI attach process is started; otherwise, the location

updating process is started. Upon receiving the IMSI attach or the location

updating process, the network marks the working status of the subscriber.

This parameter is contained in the “Control channel description”

information element, used for “RIL3_RR SYSTEM INFORMATION TYPE3”.

Value range: True: Allow MS to conduct the attach and detach operations in

the cell; False: Not allow MS to conduct the attach and detach operations in

the cell.

Setting: For different cells in the same location area, this parameter value

should be the same.

Default: True

2) Cell Bar Access

Description: PLMN operators can determine whether to allow the MS

residing in the specific cell (for instance, the cell under the test or the cell for

absorbing handover traffic only). This parameter is notified to the MS in the

cell via “RIL3_RR SYSTEM INFORMATION TYPE1”, “TYPE 2”, “TYPE

2bis”, “TYPE3” and “TYPE 4” messages. “CellBarAccess” is combined with

“CellBarQulify” (cell disable limit) to decide the priority of the cell selection

and reselection.

Default: False

3) Allow Downlink DTX

Description: Applying DTX in the downlink direction is an optional procedure

of BSC. Discontinuous transmission (DTX) refers to the process in which the

system does not transmit signals in the speech pause period during the

subscriber conversation. This parameter participates in controlling whether


Page 283 of 516

the DTX mode is applied in the downlink direction. Practically, whether DTX

(the “CHANNEL ACTIVATION” and “MODE MODIFY” messages given to

BTS) is applied in the downlink direction will be jointly decided by this

parameter and the indication about whether to adopt DTX in the downlink

direction in the “ASSIGNMENT REQUEST” and “HANDOVER REQUEST”

messages of MSC.

Value range: True: The DTX mode can be adopted in the downlink direction;

False: The DTX mode cannot be adopted in the downlink direction.

Default: True

4) Allow Call Reestablish In Cell

Description: Since “blind spot” caused by burst interference or high-rise

building will result in call disconnection due to radio link fault, MS can

originate the call re-establishment process to resume the conversation. But

the network has the right to allow the re-establishment. This function is

implemented via setting the “CallReestablish” parameter. It is broadcast to

the MS in the cell via the “RIL3_RR SYSTEM INFORMATION TYPE1”,

“TYPE2”, “TYPE 2bis”, “TYPE 3” and “TYPE 4” messages, and is one of the

network function parameters.

Value range: True: The call reestablishment is allowed inside this cell; False:

The call reestablishment is not allowed inside this cell.

Default: False

5) Allow Emergency Call

Description: Generally, any MS on the GSM network must have a valid

subscriber identification module (SIM) card to get various services support

from the network. As to the MS without a SIM card or the MS having a SIM

but its access class (one of classes from C0~C9) has been closed by the

current cell (i.e. according to the system message of the current cell, it

cannot start the access program), operators have the right to decide

whether to allow the MS for making an Emergency Call (EC), such as

burglary alarm. This function is implemented by setting the “EmergencyCall”

parameter, which is broadcast to the MS in the cell via the “RIL3_RR

SYSTEM INFORMATION TYPE1”, “TYPE 2”, “TYPE 2bis”, “TYPE 3” and

“TYPE 4” messages, and is one of the network function parameters.


Page 284 of 516

Value range: True: the MSs with the access classes 0~9 are not allowed to

make an emergency call, while the MSs with the access classes 11~15 are

not allowed to make an emergency call if the related access control bit is set

to T; False: All MSs are allowed to make an emergency call.

Setting: In the GSM specifications, the emergency call phone number is

defined as 112, which is different from China telephone number allocation.

But on the network, generally, 112 is connected to the answer phone,

notifying subscribers of various special service numbers. Therefore, EC

setting should be “False”, that is, the emergency call is allowed.

Default: False

6) T3212 Timer: The timer for periodic location update.

Description: In the GSM system, there are two major causes resulting in

location updating, one is that the MS finds its location area has been

changed (different LACs), and the other is that the network specifies the MS

to periodically update its location. The interval for periodic location updating

is controlled by the network and the period length is decided by the T3212

parameter. This parameter is broadcast to all MSs in the cell via “RIL3_RR

SYSTEM INFORMATION TYPE3” message. T3212 is one of the system

control parameters.


Table 6-64 The value range of the T3212 timer

T3212 Time indicated (min.) Time indicated (hr.)

0 Infinite (without needing location updating)

Infinite (without needing location updating)

1 6 0.1

2 12 0.2 ...

...

...

254 1524 25.4

255 1530 25.5

Setting: The setting of this parameter will affect the overall service

performance and utilization rate of radio resources of the network. As to the

area with relatively high traffic, a larger period can be chosen (i.e. 16 or 20

hours, even 25 hours). But for the area with ordinary traffic, T3212 can be


Page 285 of 516

relatively set small (such as 3 or 6 hours). For the area with extreme traffic

overload, it is recommended to set T3212 as 0.

Default: 10

7) Cell Bar Qualify

Description: For the overlapped areas in a cell, normally, operators hope

that the MS preferably selects some cells in the cell selection according to

the capacity, traffic and functional difference of each cell, that is, set the

priority of the cell. This function can be implemented via setting the

“CellBarQualify” parameter. The “Cell Bar Qualify” is used to set the cell

priority in some special cases. This parameter is broadcast to all the MSs in

the cell via the “RIL3_RR SYSTEM INFORMATION TYPE3” and “TYPE4”

messages, and is one of the cell selection parameters. Whether this

parameter is valid will be decided by “CellReselPI”.


Table 6-65 The value range of the “Cell Bar Qualify”

CellBarQualify CellBarAccess Cell selection priority Cell reselection status

F F Normal Normal

F T Barred Barred

T F Low Normal

T T Low Normal

Setting: Generally, “CellBarAccess” should be set as F, and “CellBarQulify”

is also set as F, namely, the cell priority is set as normal. But in some cases,

such as micro-cell application, dual-frequency networking, etc., operators

would hope that the MS preferably enter some types of cells first, in which

case the priority of this type cell shall be set as “Normal”, while the priorities

of other cells shall be set as “Low”. Note: This setting will not affect the cell

reselection.

Default: False

(8) MS Type Can not Visit Cell

Description: In the GSM system, all the MSs have a access class (15

classes in total). The MSs with the class ranging between 0 and 9 are


Page 286 of 516

common ones, while those with the class ranging between 11 and 15 are

special MSs (no access class 10). Based on this, the system can disable

the MSs with certain access classes to access the cell (e.g. during the

installation commissioning or the congestion control). These pieces of

information can reach the MS inside the cell in RIL3_RR SYSTEM

INFORMATION TYPE1, 2, 2bis, 3 and 4 messages through the

“AccessControl” parameter. AccessControl is also one of the system control

parameters. During the congestion control, for any overload due to CCCH or

processor, the degree of congestion can be reduced by temporarily

prohibiting one type or multiple types of subscribers from accessing the

system (mainly for subscribers of access classes 0~9). Generally speaking,

the system may have the following overload conditions:

A. RACH overload, which shall be detected in the “CCCH LOAD INDICATION”

message and processed by BSS according to the standard GSM08.58.

B. AGCH overload, which shall be detected in the “DELETE INDICATION”

message first, and handled by BSS by not sending the “IMMEDIATE

REJECT” message.

C. PCH overload, which shall be detected in the “CCCH LOAD INDICATION”

message, and shall not be handled by the BSS but shall be notified to the

MSC.

D. Other overload, which can be detected via the “OVERLOAD” message (e.g.

MTP overload), and shall handled according to the algorithm as described in

the GSM08.58.

Value range: False: MSs of related access classes are not prohibited, and

can access the cell; True: MSs of related access classes are prohibited from

accessing the cell.

Default: Generally, for C0 ~ C15 (excluding C10) these bits should be set as

True, so that during commission or in the process of maintenance and test

in some cells, unnecessary impact on the installation or maintenance may

be reduced.

4. Cell Selection Params

The configuration of the cell selection parameters is as shown in Fig. 6-23 in


environment.


Page 287 of 516




Page 288 of 516

1) Additional Reselection PI

Description: According to the definition in the GSM specification, the cell

selection and reselection of MS depend on parameters C1 and C2, and

whether C2 is used as the cell reselection parameter is determined by the

network operators. AdditionReselPI (Additional Reselect Param Ind, ACS) is

used to notify the MS about whether C2 is adopted during the cell

reselection. This parameter is broadcast to the MS in the cell via the

“RIL3_RR SYSTEM INFORMATION TYPE3” and “TYPE4” messages, and

is one of the cell selection parameters.

Value range: False: If the rest Octets of SYSTEM INFORMATION TYPE4

(SI4 Rest Octets) exist, MS shall extract from them the parameter PI related

to the cell reselection and the parameters related to the C2 calculation. True:

MS shall extract the parameter PI related to the cell reselection and the

parameters related to the C2 calculation from the rest Octets of SYSTEM

INFORMATION TYPE7 or TYPE8 (SI7/8 Rest Octets).

Setting: Generally, system messages 7 and 8 are seldom used. So the

“AdditionReselPI” is set as False normally. When the system adopts system

messages 7 and 8, and the cell reselection uses C2, the “AdditionReselPI”

should be set as True.

Default: False

2) Cell Reselection PI (C2)

Description: The cell reselection parameter index is employed to notify the

MS about whether to use the C2 as the cell reselection parameter and

whether there is the parameter for calculating C2. It indicates whether the

related parameter for calculating cell reselection standard C2 is contained in

the “SYSTEM INFORMATION” message and whether C2 standard is

adopted in the cell reselection. When this value is False, the successive

“ReselOff”, “TempOffset” and “PenalTim” will be invalid, and the MS will take

C1 as the cell reselection standard. This parameter will be broadcast to all

the MSs in the cell via the “RIL3_RR SYSTEM INFORMATION TYPE3” and

“TYPE4” messages. “CellReselPI” is one of the cell selection parameters.

Value range: False: MS shall take the parameter C1 as the standard for the

cell reselection, while parameters like CellBarQualify, ReselOffset,

TemporaryOffset and PenaltyTime are invalid. True: MS shall extract


Page 289 of 516

parameters from the system messages of the cell broadcast to calculate the

value of C2 and take it as the standard for the cell reselection. Meanwhile,

parameters like CellBarQualify, ReselOffset, TemporaryOffset and

PenaltyTime are valid.

Setting: If the related cell adopts C2 as the cell reselection standard, the

“CellReselPI” must be set as True; otherwise, it should be as False.

Default: True

3) Cell Reselection Offset (CRO)

Description: The cell reselection caused by the radio channel quality takes

the C2 as the standard. The C2 is formed on the basis of parameter C1 plus

some man-made offset parameters; to add the man-made influence is to

encourage the MS to enter some cells in priority, or to block the MS from

entering some cells. Usually, such measures are adopted to balance the

traffic on the network. Factors affecting C2, besides C1, include three

following ones: Cell reselection offset (ReselOffset), temporary offset

(TemporaryOffset), and penalty time (PenaltyTime). The ReselOffset (Cell

Reselect Offset, CRO) is a magnitude, which indicates the man-made

correction to C2. To calculate the correction of the cell C2 reselect standard

is to encourage or block the MS to enter a cell, so that, the network load

balance can be realized. This parameter is broadcast to all the MSs in the

cell via the “RIL3_RR SYSTEM INFORMATION TYPE3” and “TYPE4”




Table 6-66 The value range of CRO


0 0

1 2

2 4 ...

...

62 124

63 126

Setting: The setting of the cell reselection offset (ReselOffset), the


Page 290 of 516

temporary offset (TemporaryOffset) and the penalty time (PenaltyTime), can

be divided into three cases:

A. In case of large traffic or low communication quality inside a cell due to

certain causes, normally MS is expected not to work in that cell (i.e. having

certain repellency for that cell). In that case, the PenaltyTime can be set as

31. Thus, the “TemporaryOffset” parameter is invalid, and the numerical

value of C2 equals to C1 minus “Reseloffset”; therefore, the C2 value

corresponding to the cell is factitiously decreased, to reduce the possibility

of the MS to reselect this cell. Besides, according to the repellent condition

of the cell, the ReselOffset can be set properly: The much repellent, the

larger ReselOffset; the less repellant, the smaller ReselOffset.

B. For cells with small traffic and low equipment usage, normally MS is

encouraged to work in that cell (i.e. having a certain tendency toward that

cell). .In this case, the ReselOffset is recommended to be set between 0 ~

10 (corresponding to 0 ~ 20dB); based on the level of tendency toward the

cell, set the ReselOffset: The much tendency, the larger ReselOffset; the

less tendency, the smaller ReselOffset. Usually, the TemporaryOffset is

recommended to be set as same as ReselOffset, or a little higher than

“ReselOffset”. The main function of PenaltyTime is to avoid frequent cell

reselection of MS, and it is generally recommended to be set as 0 (20

seconds) or 1 (40 seconds) (the 1800 cell of dual-frequency network is such

a case).

C. For cells with mediate traffic, normally it is suggested to set ReselOffset as

0 and PenaltyTime as 31. Thus, C2 is equal to C1, i.e. bring no man-made

influence on the cell.

Default: 0

4) Temp Offset (TO)









Page 291 of 516

(TemporaryOffset), and penalty time (PenaltyTime). The TemporaryOffset

indicates the temporary correction value for C2. What “temporary” means is

that it only acts on C2 in a period, and the period is determined by the

“PenaltyTime” parameter. This parameter is broadcast to all the MSs in the





Table 6-67 The value range of “Temp Offset (TO)”

Value Related level value represented (dB)

0 0

1 10

2 20

3 30

4 40

5 50

6 60

7 Infinity

Default: 0

5) Penalty Time (PT)








(TemporaryOffset), and penalty time (PenaltyTime). The TemporaryOffset

indicates the temporary correction value for C2. What “temporary” means is

that it only acts on C2 in a period, and the period is determined by the

“PenaltyTime” parameter. This parameter is broadcast to all the MSs in the





Page 292 of 516



Page 293 of 516

Table 6-68 The value range of “Penalty Time (PO)”

Value The time value represented (second)

0 20

1 40

2 60 ...

...

29 600

30 620

31 TemporaryOffset is invalid, and the action direction of ReselOffset is reverse.

Default: 20

6) Early Class Mark Transmission Control (ECSC)

Description: According to the GSM specifications, when the MS is equipped

with the ECSC function that is also supported by the network, the MS will

transmit the additional class mark information (Classmark 3) to the network

via the “CLASSMARK CHANGE” message as soon as possible after the

immediate assignment. Whether the network supports the ECSC function is

controlled by the “ECSC” parameter. The parameter is broadcast to the MSs

in the cell via the “RIL3_RR SYSTEM INFORMATION TYPE3” message.

Value range: False: Disable ECSC of MS. True: Enable ECSC of MS.

Setting: If there is another frequency band in the adjacent cell for handover

or the cell is an extended GSM cell and the network supports the ECSC

function, the “ECSC” here shall be set as True. Otherwise, it shall be set as

False.

Default: True

7) Hardware Support Half Rate (NECI)

Description: Based on the GSM specifications, the traffic channels in the

GSM system can be classified into the channel with full rate and the channel

with half rate. The common GSM systems all support the channel with full

rate; whether the network supports the half-rate service is decided by

network operators. The NECI is used to notify the MS if the area supports

the half rate service. The parameter is notified to the MS via the “RIL3_RR


Page 294 of 516

SYSTEM INFORMATION TYPE3” and “TYPE4” messages and is one of

network functional parameters.

Value range: False: This cell does not support the access of the half rate

service. True: This cell supports the access of the half rate service.

Setting: False.

Default: False

8) MS Power Offset

A. Power Offset Index

Description: In the GSM specifications, for the Class 3 MS of GSM1800, the

transmitting power for sending an access request message on RACH is to

add an offset value on the basis of the MsTxPwrMaxCCH value, which is

specified by the “PwrOffset” parameter. But, whether the offset value is

required is indicated by the “PwrOffsetInd” parameter, that is, the

“PwrOffsetInd” parameter decides if the “PwrOffse” parameter is valid. The

parameter is broadcast to the MSs in the cell via the “RIL3_RR SYSTEM

INFORMATION TYPE3”,”TYPE 4”, “TYPE 7” and “TYPE 8” messages.

Value range: False: The “PwrOffset” parameter is invalid. True: The

“PwrOffset” parameter is valid.

Default: False

B. Power Offset Value

Description: In the GSM specifications, for the Class 3 MS of GSM1800, the

transmitting power for sending an access request message on RACH is to

add an offset value on the basis of MsTxPwrMaxCCH value, which is

specified by the “PwrOffset” parameter. But, whether the offset value is

required is denoted by the “PwrOffsetInd” parameter, that is, the

“PwrOffsetInd” parameter decides if the “PwrOffse” parameter is valid. The

“PwrOffset” parameter also affects the MS in the cell selection and cell

reselection calculation standards C1 and C2. The parameter is broadcast to

the MSs in the cell via the “RIL3_RR SYSTEM INFORMATION TYPE3”,

“TYPE4”, “TYPE7” and “TYPE8” messages.



Page 295 of 516

Table 6-69 The value range of “Power Offset Value”

Value The power offset represented(dB)

0 0

1 2

2 4

3 6

Default: 0

5. Operation Course Addition Params

The configuration of the operation course additional parameters is as shown

in Fig. 6-25 in the GSM environment while as shown in Fig. 6-26 in the

GPRS environment.



Page 296 of 516


1) Use Directed Retry

Description: Whether the Directed Retry process is used. In the assignment

process, if there is no traffic channel to be assigned in the served cell while

the system adopts the directed retry, it will assign a traffic channel for MS in

an adjacent cell according to the measurement report from MS. This is a

special handover process that can reduce the call drop rate. The directed

retry can be divided into the directed retry inside BSC and that between the

BSCs, the former of which does not require the participation of the MSC but

the latter does.


Table6-70 The value range of “Use Directed Retry”

Value The directed retry inside BSC (with no MSC participation)

The directed retry between BSCs

(with MSC participation)

0 No No

1 Yes No

2 No Yes


Page 297 of 516

3 Yes Yes

Default: 0

2) Allow Queue when Assign

Description: The parameter decides if the queuing can be performed in the

process of assignment when there is no channel available in the cell.


Default: False

3) Allow Queue when Handover.

Description: The parameter decides if the queuing can be performed in the

process of handover when there is no channel available in the cell.


Default: False

4) Assign Remove Mark (Choose, Damage) and HandOver Remove Mark

(Choose, Damage)

Description: Whether to allow the forced release in the process of

assignment and handover. The “forced release” process means that, when

the priority in the request of assignment or handover is valid and also the

preemption is valid, forcedly disconnect (handover) those easily damaged

connections before they are not allocated with the resources, then, allocate

the released resources to this assignment or handover request. Whether a

call is easily damaged will be shown in the requests of assignment and

handover.


Table 6-71 The value ranges of “Assign Remove Mark (Choose, Damage)” and “HandOver

Remove Mark (Choose, Damage)”

Value Meaning

0 True: The assignment request allows forced occupancy

False: The assignment request does not allow forced occupancy

1 True: The handover request allows the forced occupancy

False: The handover request does not allow the forced


Page 298 of 516

occupancy

Default: False for both.

5) Allow Rapid Average after Call Setup/Handover/Power Control

Description: Due to few measurement data, the corresponding handover

and power control may not be performed in the process of call, since, these

processes generally require the numbers of values that can be measured to

reach a certain window value before the process of calculating the average

value can be started. For example, when the window value to calculate the

average value is 8, but here, the BSC only receives 5 measurement values,

the common average process can do nothing at the time, anyhow, if the

rapid average process is adopted, then, the BSC will directly calculate the

average value of the 5 measurement values. In the entire process of the call,

there will be three cases resulting in insufficient measurement value for

calculating the average value, i.e. the call setup period, after handover and

after power control. It is necessary to point out that, after the power control

is performed once, the former measurement value is meaningless to the

power control, it even might cause incorrect control, therefore, all the old

measurement values for power control must be discarded in such a case

(the measurement values without affecting the handover control still exist).

Similarly, after the handover occurred (intra-BSC handover), the former

measurement value is meaningless, it even might cause incorrect control,

therefore, all the old measurement values for power control and handover

control must be discarded in such a case. The “FastAvg” parameter decides

whether the rapid average process can be separately used in the three

phases.


Table 6-72 The value range of “Rapid Average”

Position Meaning

1 1: The call setup phase allows the rapid average process

0: The call setup phase does not allow the rapid average process

2 1: The rapid average process is allowed after handover

0: The rapid average process is not allowed after handover

3 1: The rapid average process is allowed after power control


Page 299 of 516

0: The rapid average process is not allowed after power control

4 ~ 8 Reserved, always 0

Setting: The generally-followed policies are as follows:

A. When the SDCCH handover is allowed, position 1 can be set as 1;

B. When the minimum time interval for handover is less than the time

represented by some window value (the preprocessing of BTS shall be

taken into account), we can consider setting position 2 to 1.

C. When the preprocessing of BTS is performed, position 3 can be set as 1.

Default: All the average values of call setup, handover and power control

are “True”.

6) FACCH Call Setup

Description: When an MS attempts to access the network, and there is no

SDCCH available in the cell, here, the BSC can allocate the TCH channel

according to the situation, i.e. the FACCH call setup process. Whether and

how to use the FACCH call setup process is controlled by the

“FacchCallInd” parameter.


Table 6-73 The value range of “FACCH Call Setup”

Position Meaning

1 1: The emergency call allows the FACCH call setup process

0: The emergency call does not allow the FACCH call setup process

2 1: The paging response allows the FACCH call setup process

0: The paging response does not allow the FACCH call setup process

3 1: The originating call allows the FACCH call setup process

0: The originating call does not allow the FACCH call setup process

4 1: The call re-setup allows the FACCH call setup process

0: The call re-setup does not allow the FACCH call setup process

5 ~ 8 Reserved, always 0

Default: All the values of call setup are “True”.


Page 300 of 516

7) Optimize TxPwr

Description: By introducing the concept of optimal signal level, the

transmitting power of the mobile station and the BS can be optimized after

the assignment and handover of the mobile station and the BS (including

the directed retry), thus, it can avoid the increased interference of entire

GSM system caused by always using the maximum transmitting power, or

the failure of the MS access and the reduction of system call completion

ratio caused by using a smaller transmitting power (when it is intra-cell

handover or when assigning) Of course, it is an optional item also, therefore,

the “OptTxPwrInd” parameter is used to decide if the relevant function of

transmitting power optimization is enabled. It is necessary to point out that

the optimization of uplink transmitting power is related to the smallest

acceptable carrier-to-noise ratio allocated by channel. Moreover, the

parameter also decides the validity of parameters “OptRxLevUL” and

“OptRxLevDL”, i.e. when a process in the uplink direction requires to be

optimized, the “OptRxLevUL” parameter is valid; Otherwise it is invalid; so is

with the downlink direction.


Table 6-74 The value range of “Optimize TxPwr”

Position Meaning

1 1: Optimize the transmitting power when assigning in the uplink direction

0: Do not perform the transmitting power optimization when assigning in the uplink direction

2 1: Optimize the transmitting power during the intra-cell handover in the uplink direction (including the concentric handover)

0: Do not optimize the transmitting power during the intra-cell handover in the uplink direction (including the concentric handover)

3 1: Optimize the transmitting power during the inter-cell handover in the uplink direction(including the directed retry)

0: Do not optimize the transmitting power during the inter-cell handover in the uplink direction (including the directed retry)

4 Reserved, always 0

5 1: Optimize the transmitting power when assigning in the downlink direction

0: Do not optimize the transmitting power when assigning in the downlink direction


Page 301 of 516

6 1: Optimize the transmitting power during the intra-cell handover in the downlink direction (including the concentric handover)

0: Do not optimize the transmitting power during the intra-cell handover in the downlink direction (including the concentric handover)

7 1: Optimize the transmitting power during the inter-cell handover in the downlink direction(including the directed retry)

0: Do not optimize the transmitting power during the inter-cell handover in the downlink direction (including the directed retry)


Default: All the seven kinds of power optimization settings are “False”.

8) Allow to Assign from SCDDH to TCH of Special TRX

Description: Whether it is allowed to perform the assignment process from

the SDCCH to the TCH of special TRX. On the basis of C/I concentric

technology, when there is no TCH channel on a common TRX and if there is

proper TRX channel on the special TRX, besides queuing to wait, it is also

possible to directly assign the MS to the TCH channel on the special TRX

from SDCCH to avoid the occurrence of call drop. The “CiAssignInd”

parameter decides whether it can be done. Note: Whether the parameter is

valid is decided by the bit related to the concentric circle in the “HoControl”

field of the “R_HOC” table.

Value range: False: The assignment procedure from SDCCH to TCH of

special TRX cannot be executed. True: The assignment procedure from

SDCCH to TCH of special TRX can be executed.

Default: True

(9) Uplink Best Signal Level

Description: The parameter indicates the best receiving intensity of the

uplink signal in the cell, i.e. under this receiving intensity, usually, the good

signal quality and small interference can be guaranteed. So, in the process

of assignment or handover, if the optimization of transmitting power in the

uplink direction is performed, the “OptRxLevUl” is the mobile signal level

that the BS expects to receive.


Table 6-75 The value range of “Uplink Best Signal Level”


Page 302 of 516


0 < -110

1 -110 ~ -109 ...

...

62 -49 ~ -48

63 > -48

Setting: For the parameter setting, you can refer to the descending

threshold value controlled by the uplink power.

Default: 22

10) Downlink Best Signal Level

Description: The parameter indicates the best receiving intensity of the

downlink signal in the cell, i.e. under this receiving intensity, usually, the

good signal quality and small interference can be guaranteed. So, in the

process of assignment or handover, if the optimization of transmitting power

in the downlink direction is performed, the “OptRxLevDl” is the mobile signal

level that the BS expects to receive.


Table 6-76 The value range of “Downlink Best Signal Level”


0 < -110

1 -110 ~ -109

2 -109 ~ -108 ...

...

62 -49 ~ -48

63 > -48


threshold value controlled by the downlink power.

Default: 22

11) Candidate Cell Maximal Count

Description: According to the relevant specifications, when the BSC sends

the “BSSAP HANDOVER REQUIRED” message to MSC, a certain number


Page 303 of 516

of candidate cells are required to be given, and this parameter specifies the

largest number of candidate cells that can be contained in the “BSSAP

HANDOVER REQUIRED” message.

Value range: 1 ~ 16

Default: 6

12) Up-Downlink Signal Balance

Description: The parameter indicates the difference between the uplink

signal level and the downlink signal level in the area covered by the cell.

The calculation method is: RxLevBalance = downlink signal – uplink signal,

e.g. the value 5dB means that the downlink signal is 5dB stronger than the

uplink signal.


Table 6-77 The value range of “Up-Downlink Signal Balance”


0 0

1 1 ...

...

19 19

20 20


threshold value controlled by the uplink power.

Default: 0

13) Allow Uplink Minimal Signal Level

Description: On the basis of C/I concentric technology and in the process of

performing the assignment from SDCCH to the TCH of special TRX, when

there is no TCH channel on the common TRX and if there is proper TRX

channel on the special TRX, it is also possible to directly assign the MS to

the TCH channel on the special TRX from SDCCH to avoid the occurrence

of call drop. The "CiAssignThs” parameter determines the level value that

must be exceeded by the signal level in the uplink direction (after correcting

the power control).


Page 304 of 516


Table 6-78 The value range of “Allow Uplink Minimal Signal Level”


0 < -110

1 -110 ~ -109 ...

...

62 -49 ~ -48

63 > -48

Default: 25

14) Minimal Resource Level

Description: In case of some special frequency multiplexing modes, as the

guarantee for the normal service needs the restriction on certain traffic (e.g.

a better conversation quality can be obtained only in case of 50% of traffic),

this parameter is a threshold value of the traffic that a cell or its surrounding

cells at the same layer can reach. When the TCH channel occupancy rate of

a cell and its adjacent cell of the same layer (quantity of TCHs occupied by

a cell and its adjacent cells of the same layer/total of TCHs occupied by a

cell and its adjacent cells of the same layer) reaches this value, no channels

will be allocated to the assignment procedure in the cell. Meanwhile, the

handover will not be affected by this parameter.


Default: 100

15) Access Minimal C/N Value

Description: When distributing a channel to a call, a minimal acceptable C/N

value can be specified, which will be used to make the channel selection.

The “CnThresInd” parameter specifies the minimal acceptable C/N value.

The principle of channel allocation is to select the idle channel that can

meet this value as much as possible. The parameter also affects the

optimization of the uplink mobile transmitting power.

Value range: 0 ~ 63, separately representing 0 ~ 63dB.

Default: 15

6. System Params


Page 305 of 516

The configuration of the system parameters is as shown in Fig. 6-27 in the

GSM environment while as shown in Fig. 6-28 in the GPRS environment.



Page 306 of 516


1) Survey Period

Description: BTS needs to measure the interference on the unassigned

traffic channels, calculate the average of the recent interference values

periodically and convert it into the corresponding interference band

information, and transfer it to BSC in the “RF RESOURCE INDICATION”

message as a factor to be considered when BSC assigns channels. The

value of the period is determined by the “InterfAvgPrd“ (Interference

Averaging Period, AP) parameter. This parameter is one of the configuration

parameters of BTS.


Table 6-79 The value range of “Survey Period”

Value Meaning

0 Reserved.

1 1 SACCH multi-frame is reported to BSC once ...

...

31 31 SACCH multi-frames are reported to BSC once

Default: 31

2) Interference Boundary

Description: BTS needs to measure the interference on the unassigned

traffic channels, calculate the average of the recent interference values

periodically and convert it into the corresponding interference band

information, transfer it to BSC in the “RF RESOURCE INDICATION”

message as a factor to be considered when BSC assigns channels. Some

corresponding relations are needed in converting interference level

(average) value into the corresponding interference band information. These

corresponding relations are respective interference boundaries. Altogether

six boundaries determine five interference bands. Actually, the interference

boundary 0 and the interference boundary 5 need not be set and BTS need

not consider these two boundaries. one of them stands for infinity and the

other for negative infinity. This parameter, used for describing the remaining

four boundaries, is one of the configuration parameters of BTS.


Page 307 of 516


Table 6-80 The value range of “Interference Boundary”

Value of the interference boundary n The level value represented

0 -110 dBm

1 -109 dBm ...

... 63 -47 dBm


Setting: Interference boundaries 1 ~ 4 are usually set between -85dBm and

-115dBm.

Default: Interference boundaries 0 ~ 5: 0, 10, 15, 20, 25, and 63.

3) Radio Link Failure (RLF) Judge Standard

Description: The network side (BTS) may judge whether the radio link fails

according to two standards, one of which is based on uplink SACCH error

rate, and the other is based on the measurement value of RXLEV/RXQUAL.

This parameter determines which method BTS uses as the standard to

judge connection failure. If SACCH error rate is used as the standard to

judge connection failure, BTS will use the same “RadioLkTimeout”

parameter value and the same process as MS does, thus avoiding

inconsistent judgment standards in the uplink and downlink directions.

Meanwhile, parameters “RxLevThs” and “RxQualThs” are invalid. If the

measurement value of RXLEV/RXQUAL is used as the standard to judge

connection failure, BTS will use the flowing two parameters: “RxLevThs”

and “RxQualThs”. Parameter “ConFailCriterion” (Connect Failure Criterion)

is one the configuration parameters of BTS.

Value range: 1: Based on uplink SACCH error rate (in order to ensure the

same judgment standard in the uplink and downlink directions); 2: The

measurement value based on RXLEV/RXQUAL.

Default: 1

4) Level Threshold of Survey RLF

Description: The network side (BTS) may judge whether the radio link fails

according to two standards, one of which is based on uplink SACCH error


Page 308 of 516

rate, and the other is based on the measurement value of RXLEV/RXQUAL.

If the measurement value of RXLEV/RXQUAL is used as the standard to

judge connection failure (parameter ConFailCriterion is 2), the radio link will

be considered as having failed when BTS detects that the uplink receiving

level is smaller than a certain threshold or the uplink receiving quality is

greater than a certain threshold. Parameter “RxLevThs” specifies the

threshold of the receiving level. If uplink SACCH error rate is used as the

standard to judge connection failure (parameter ConFailCriterion is 1), this

parameter is invalid. RxLevThs is one of the configuration parameters of

BTS.


Table 6-81 The value range of “ Level Threshold of Survey RLF”


0 < -110

1 -110 ~ -109

2 -109 ~ -108 ...

...

62 -49 ~ -48

63 > -48

Default: 10

5) Quality Threshold of Survey RLF

Description: According to GSM Specifications, the network side (BTS) may

judge whether the radio link fails according to two standards, one of which is

based on uplink SACCH error rate, and the other is based on the

measurement value of RXLEV/RXQUAL. If the measurement value of

RXLEV/RXQUAL is used as the standard to judge connection failure

(parameter ConFailCriterion is 2), the radio link will be considered as having

failed when BTS detects that the uplink receiving level is smaller than a

certain threshold or the uplink receiving quality is greater than a certain

threshold. Parameter “RxQualThs” specifies the threshold of the receiving

quality. If uplink SACCH error rate is used as the standard to judge

connection failure (parameter ConFailCriterion is 1), this parameter is invalid.

RxQualThs is one of the configuration parameters of BTS.


Page 309 of 516


Table 6-82 The value range of “ Quality Threshold of Survey RLF”

Value The corresponding BER range

0 <0.2%

1 0.2% ~ 0.4%

2 0.4% ~ 0.8%

3 0.8% ~ 1.6%

4 1.6% ~ 3.2%

5 3.2% ~ 6.4%

6 6.4% ~ 12.8%

7 > 12.8%

Default: 6

6) Survey RLF Period

Description: The period of the network side to check the radio link fault (in

units of SACCH multi-frame).


Default: 10

7) Send OverLoad Msg. Minimal Period

Description: According to GSM Specifications, in case of the CPU overload

of TRX, or downlink CCCH channel overload, or AGCH channel overload,

TRX will notify BSC of this by sending the “OVERLOAD” message

periodically until the overload disappears. Parameter “OverloadPrd”

specifies the period for TRX to send the “OVERLOAD” message.

OverloadPrd is one of the configuration parameters of BTS (all TRXs under

BTS use the same period).

Value range: 1 ~ 31 (in the unit of 102TDMA frame)

Default: 10


Page 310 of 516

8) PHY Info Message Resend Time Interval during Handover On SDCCH Channel

Description: The interval of re-sending “RIL3_RR PHYSICAL I”formation" message during asynchronous handover of SDCCH channel. This timer is one of the configuration parameters of BTS.

A. Start conditions of the timer: After the network side sends the “RIL3_RR PHYSICAL INFORMATION message”, T3105[0] starts.

B. Stop conditions of the timer: If the network receives a layer-2 frame that can be correctly decoded or receives the “HANDOVER FAILURE” message from the old channel, T3105[0] stops.

C. Timeout: When the timer T3105[0] expires, RIL3_RR PHYSICAL INFORMATION will be sent again.


Table 6-83 The value range of “PHY Info Message Resend Time Interval during Handover

On SDCCH Channel”

T3105[0] Duration represented

28 0.28s


Setting: Unchangeable.

Default: 28

9) PHY Info Message Resend Time Interval during Handover On TCH Channel

Description: The interval of re-sending RIL3_RR PHYSICAL INFOMATION during asynchronous handover of TCH channel. This timer is one of the configuration parameters of BTS.

A. Start conditions of the timer: After the network side sends the “RIL3_RR PHYSICAL INFORMATION” message, T3105[1] starts.

B. Stop conditions of the timer: If the network receives a layer-2 frame that can be correctly decoded or receives “HANDOVER FAILURE” message from the old channel, timer T3105[1] stops.

C. Timeout: When the timer T3105[1] expires, RIL3_RR PHYSICAL INFORMATION will be sent again.



Page 311 of 516

Table 6-84 The value range of “PHY Info Message Resend Time Interval during Handover

On TCH Channel”

T3105[1] Duration represented

10 0.1s


Setting: Unchangeable.

Default: 10

10) BA Indication (or TS No. indication of BCCH)

Description: The timeslot where the common control channel BCCH is

located. One cell may have 4 BCCHs at most.

Default: Dynamic.

7. Cell Option Params

The configuration of the cell optional parameters is as shown in Fig. 6-29 in


environment.



Page 312 of 516


1) Time Interval of MS Access Attempt after an Access Failure: (T3122)

Description: After the network receives the channel request message sent

by MS, if there is no proper channel to be allocated to the MS, the network

will send the “IMMEDIATE ASSIGNMENT REJECT” message to the MS. To

prevent MS from making repeated channel requests thus resulting in radio

channel blocking, the “IMMEDIATE ASSIGNMENT REJECT” message

contains timer parameter T3122, i.e. Wait indication information element.

After receiving the “IMMEDIATE ASSIGNMENT REJECT” message, MS

must wait for a time indicated by T3122 before starting a new call. This

parameter is also one of the system control parameters and is sent to MS in

the “IMMEDIATE ASSIGNMENT REJECT” message.


Table 6-85 The value range of “Time Interval of MS Access Attempt after an Access


Page 313 of 516

Failure”


0 0s

1 1s ...

...

255 255s

Setting: Generally, it is recommended to set the T3122 as 10 ~ 15s, and 15

~25s for the area with high density traffic.

Default: 10

2) Adjacent Cell Num of neighbor Band Reported in MultiBand

Description: In single-band GSM system, when MS reports the survey result

of the adjacent cells to the network, it only needs to report the contents of

the 6 adjacent cells with the strongest signals in a frequency band. In

multi-band networking, according to actual network conditions, the operator

usually hopes that MS first enters into a specific frequency band during

handover, thus hoping that MS reports the survey result not only according

to the signal level but also based on the frequency band of the signals. The

"MulbandReport” parameter is used to notify MS that the adjacent cell

contents of multiple frequency bands shall be reported. It is one of the

system control parameters.


Table 6-86 The value range of “Adjacent Cell Num of neighbor Band Reported in

MultiBand”

Value Meaning

0 MS reports the survey results of six known and allowed adjacent cells with the strongest NCC according to the signal level of the adjacent cells, regardless of which frequency band the adjacent cells are in.

1 MS reports the survey result of one adjacent cell with the strongest signals in the frequency bands (except the frequency band of the local cell) in the adjacent cell table. In the remaining locations, MS reports the adjacent cell in the local cell frequency band. If there are still more locations remaining, MS reports the remaining adjacent cells,


Page 314 of 516

Value Meaning

regardless of which frequency bands they are in.

2 MS reports the survey result of two adjacent cells with the strongest signals in the frequency bands (except the frequency band of the local cell) in the adjacent cell table. In the remaining locations, MS reports the adjacent cell in the local cell frequency band. If there are still more locations remaining, MS reports the remaining adjacent cells, regardless of which frequency bands they are in.

3 MS reports the survey result of three adjacent cell with the strongest signals in the frequency bands (except the frequency band of the local cell) in the adjacent cell table. In the remaining locations, MS reports the adjacent cell in the local cell frequency band. If there are still more locations remaining, MS reports the remaining adjacent cells, regardless of which frequency bands they are in.

Setting: The setting of this parameter is related to the traffic in various

frequency bands. Generally, please refer to the following principles in setting

the value:

A. The traffic of various frequency bands is basically the same. If the operator

cannot select frequency bands, it should be set to 0;

B. The traffic of various frequency bands is sharply different. If the operator

hopes that MS first enters into a specific frequency band, it should be set to

3;

C. If the situation is between these two cases above, this parameter can be set

to 1 or 2.

Default: 0

3) SMS Mode in Cell

Description: According to the Specifications, cell broadcast short message is

also an optional service of BSC. Through this service, it is possible to

broadcast to MS in the cell some useful information such as weather

forecast and traffic conditions. This parameter determines whether it is

allowed to use cell broadcast short message service or adopt DRX

(discontinuous reception) mode. However, the fact that BSC can use cell

broadcast short message does not mean that MS is sure to receive the

broadcast short message. It is also necessary to configure CBCH for the


Page 315 of 516

cell. DRX mode in cell broadcast short message service may save the

battery of MS on one hand, and on the other hand, MS can even choose to

receive only “interesting” broadcast short message.

Value range: 0: Not use the cell broadcast short message procedure. 1: Use

the cell broadcast short message procedure, but not to adopt the DRX

mode. 2: Use the cell broadcast short message procedure and adopt the

DRX mode.

Default: 0

4) MS DTX Mode (BCCH)

Description: Discontinuous transmission (DTX) refers to the process that the


subscriber communication process. This parameter controls the way MS

uses DTX mode. On one hand, “RIL3_RR SYSTEM INFORMATION TYPE3

message” should be broadcast to all MSs in the cell, and on the other hand

it may be necessary to notify MS of older versions (the first stage) via

“RIL3_RR SYSTEM INFORMATION TYPE6 message” on SACCH. For MS

of the new version, “RIL3_RR SYSTEM INFORMATION TYPE6” message

contains DtxUplinkSacch. This parameter is one of the network function

parameters.


Table 6-87 The value range of “ MS DTX Mode (BCCH)”

Value Meaning

0 MS may use DTX

1 MS should use DTX

2 MS should not use DTX

3 Reserved.

Setting: It is usually set to 1 (i.e. using DTX) if BTS and TRAU provide

support. Otherwise it is set to 2 (not using DTX).

Default: 1

5) MS DTX Mode (SACCH)

Description: Discontinuous transmission (DTX) refers to the process that the



Page 316 of 516

subscriber communication process. This parameter controls the way MS of

the new version uses DTX mode, i.e. notifying MS of the new version via

“RIL3_RR SYSTEM INFORMATION TYPE6” message on SACCH. What is

notified to MS of older versions (the first stage) via “RIL3_RR SYSTEM

INFORMATION TYPE6” message on SACCH, and what “RIL3_RR

SYSTEM INFORMATION TYPE3” message on SACCH contains is

DtxUplinkBcch parameter. This parameter is one of the network function

parameters.


Table 6-88 The value range of “MS DTX Mode (SACCH}”

Value range TCH/F channel TCH/H channel

0 MS may use DTX MS should not use DTX

1 MS should use DTX MS should not use DTX

2 MS should not use MS should not use DTX

3 MS should use DTX MS may use DTX

4 MS may use DTX MS may use DTX

5 MS should use DTX MS should use DTX

6 MS should not use DTX MS should use DTX

7 MS should use DTX MS should use DTX

Setting: It is usually set to 1 (i.e. using DTX) if BTS and TRAU provide

support. Otherwise it is set to 2 (not using DTX).

Default: 1

8. Other Params

The configuration of other cell parameters is as shown in Fig. 6-31 in the

GSM environment while as shown in Fig. 6-32 in the GPRS environment.


Page 317 of 516



1) T200 Timer


Page 318 of 516

Description: T200 (altogether 7 kinds of T200) is the timer used on various

control channels in LapDm protocol of BTS.

Value range: This parameter has 7 bytes, each standing for the value (in

5ms) of a kind of timer.


Table 6-89 The value range of “T200 Timer”

Parameter Default value

SDCCH 1 (5ms)

FACCH/Full rate 1 (5ms)

FACCH/Half rate 1 (5ms)

SACCH with TCH SAPI0 2 (10ms)

SACCH with SDCCH 2 (10ms)

SDCCH SAPI3 1 (5ms)

SACCH with TCH SAPI3 2 (10ms)

Setting: Refer to the above table for the default settings. Usually, the values

of these timers cannot be modified.

2) Handover Pretreat and Report Period

Description: Measurement report is the information of Abis interface with the

biggest quantity (information amount). To lighten the load of Abis interface

link, we may let BTS complete the report pretreatment. After using

pretreatment, BTS will calculate the average of its own survey data and that

of MS, then report to BSC at a low frequency. The period of averaging and

report may be 2, 3 or 4 SACCH multi-frames (480ms), i.e. the frequency

decreases from the original twice/s to once/2s, so the message amount of

Abis interface becomes smaller (whether the message amount becomes

smaller depends on whether the length of the message before and after

pretreatment is the same). But one negative effect of pretreatment is the

untimely handover control and power control and bigger possibility of

disconnection. This parameter determines the use and period of

pretreatment.


Table 6-90 The value range of “Handover Pretreat and Report Period”


Page 319 of 516

Value Meaning

0 No pretreatment

2 Pretreatment, and averaging and report period is 2 SACCH multi-frames




Default:

3) CCCH Structure Parameter

Description: Common control channel configuration parameter

CCCH_CONF. In GSM system, CCCHs mainly include AGCH (Access

Grant Channel) and PCH (Paging Channel), whose main functions are to

send access grant (i.e. Immediate assignment) message and paging

message. All traffic channels in every cell share CCCH. Depending on the

configurations of traffic channels in a cell and the traffic model of the cell,

CCCH may be borne by one or several physical channels, and CCCH and

SDCCH may share one physical channel. The way the common control

channels in a cell are combined depends on the “CcchConf” parameter.

Through this parameter, we can get: 1. BS_CC_CHANS (quantity of

CCCHs); 2. BS_CCCH_SDCCH_COMB (whether used together with

SDCCH). This parameter is broadcast to all MSs in the cell via “RIL3_RR

SYSTEM INFORMATION TYPE3” message. CcchConf is one of the system

control parameters.


Table 6-91 The value range of “CCCH Structure Parameter”

CCCH-CONF

Meaning: The number of CCCH message blocks in one BCCH multi-frame

0 One basic physical channel used by CCCH, which is not used together with SDCCH

9

1 One basic physical channel used by CCCH, which is used together with SDCCH

3


Page 320 of 516

CCCH-CONF

Meaning: The number of CCCH message blocks in one BCCH multi-frame

2 Two basic physical channels used by CCCH, which are not used together with SDCCH

18

4 Three basic physical channels used by CCCH, which are not used together with SDCCH

27

6 Four basic physical channels used by CCCH, which are not used together with SDCCH

36

Others Reserved. —

Setting: The setting of CcchConf in the cell must be the same as the actual

configurations of CCCHs in the cell. Value range: See Table 6-92.

Table 6-92 The value range of cell configurations

TRX quantity 1 2 3 4 5 6

CcchConf 1 0 0 0 0 2

TCH 7 14 22 29 37 44

SDCCH 4 8 8 16 16 16

4) Resource Location Information

Description: Description of the geographical place where the cell is located.

5) Cell Support Encrypt Mode

Description: This is the ciphering algorithm supported by BSC. If a “BSSAP

CIPHER MODE COMMAND” or “BSSAP ASSIGNMENT REQUEST” or

“BSSAP HANDOVER COMMAND” is received from MSC, which contains

the required encryption algorithm, BSC will, by checking this parameter,

learn whether the cell supports the required encryption algorithm and thus

give the correct response.



Page 321 of 516

Table 6-93 The value range of “Cell Support Encrypt Mode”

Value Meaning

1 Supporting/not supporting A5/1 algorithm






Bit8=1/0 Supporting/not supporting A5/7 algorithm

Setting: Currently GSM in China does not use encryption, so 0 may be set

as the default value.

Default: 09.

9. GPRS Cell Reselection.

The configuration of “GPRS Cell Reselection” is shown in Fig. 6-33.

Fig. 6-33 Configuring cell (9)


Page 322 of 516

1) GPRS Cell Reselection Offset

Description: This is a usage parameter at the MS side. It is broadcast to MS

in the adjacent cell option of the PSI3 message. In GRPS, the cell

reselection will adopt C32 as the standard, which is similar to the C2

standard in GSM. In the C32 standard calculation, there is also a cell

reselection parameter ReselOff. When the offset represented by this

parameter is 0dB, it need not appear in the packet system message.


Table 6-94 The value range of the GPRS Cell Reselection Offset


0 -52dB

1 -48dB ...

...

22 +12dB

23 +16dB ...

...

31 +48dB

Setting: 0

2) Temp Offset of Cell Reselection


in the PSI3 message. In the GRPS system, the cell reselection will adopt

C32 as the standard, which is similar to the C2 standard in GSM. In the C32

standard calculation, there is also a temporary offset parameter TempOffset.

For the C32 standard, a minus offset is donated, whose effective period is

determined by the “PenaltyTime” parameter.


Table 6-95 Value range for the Temp Offset of Cell Reselection


Page 323 of 516


0 0

1 10

2 20

3 30

4 40

5 50

6 60

7 ???

Setting: The same as the offset in the C2 standard of the GSM system.

3) Penalty Time of Cell Reselection


in the PSI3 message. In the GRPS system, the cell reselection will adopt

C32 as the standard, which is similar to the C2 standard in GSM. In the C32

standard calculation, there is also a temporary offset parameter TempOffset.

For the C32 standard, a minus offset is donated, whose effective period is

determined by the “PenaltyTime” parameter.


Table 6-96 Value range for the cell reselection penalty time

Value Time length represented

0 10s

1 20s ...

...

31 320s

Setting: 0

4) Minimal interval of Cell Reselection


in the PSI3 message. When MS executes one cell reselection, which

causes the abnormal release in this cell, it is not permitted to reselect that

cell for MS within the period of T_RESEL unless there is no other cell for

selection. When the duration represented by this parameter is the default

value of 5 s, it need not be broadcast to MS in the PSI message.


Page 324 of 516


Table 6-97 Value range for the Minimal interval of Cell Reselection

Value Time interval represented

0 5s

1 10s

2 15s

3 20s

4 30s

5 60s

6 120s

7 300s

Setting: 0 (i.e. the time interval is 5 s).

5) Power Level Threshold of HCS

Description: This is a usage parameter at the MS side, belonging to the

HCS parameters. It is broadcast to MS in the PSI3 message of this cell and

adjacent cells, indicating the HCS power level threshold of the cell.


Table 6-98 The value range of Power Level Threshold of HCS

Value Corresponding HCS Power Level Threshold

0 -110 dBm

1 -108 dBm ...

...

63 -48 dBm

Setting: 0

6) HCS Priority


HCS parameters. It is broadcast to MS in the PSI3 message, indicating the

HCS priority of the cell.

Value range: 0 ~ 7

Setting: 0


Page 325 of 516

7) Reselection Hysteresis on C31


in the PSI3 message, indicating whether to apply the CellReselHys

parameter to the C31 standard.

Value range: 0: Not apply. 1: Apply.

Setting: 0

8) Reselection Hyst.


in the PSI3 message. When MS conducts GPRS cell reselection, if the

original cell and destination cell belong to different location areas, MS

should initialize a location updating process after cell reselection. Due to the

fading characteristic of the radio channel, normally, the C32 values of two

cells measured at the adjacent cell boundary will have a relatively big

fluctuation, thus resulting in MS to frequently reselect cells. Although the

interval of reselecting two cells by MS will not be less than 15s, it is

extremely short in terms of location updating. It not only dramatically

increases the signaling flow of networks, causing the radio resources unable

to be fully utilized, but also decreases the call completion rate of the system

due to paging unable to be responded during MS location updating. To

reduce the impact of this issue, one parameter is set in the specification,

called Cell Reselection Hysteresis (CRH) that requires the signal level of the

adjacent cell (the location area is different from that of this cell) to be greater

than the local cell signal level and its difference to be greater than the value

specified by the CRH before MS starts the cell reselection process.



Page 326 of 516

Table 6-99 The value range of the GPRS Cell Reselection Hysteresis

Value The specified hysteresis level

0 0dB

1 2dB

2 4dB

3 6dB

4 8dB

5 10dB

6 12dB

7 14dB

Setting: Generally, “4” or “5” is recommended (that is, the CRH is 8dB or

10dB). Proper adjustment is suggested for the following cases:

A. When there is very large traffic in an area and the overload phenomena of

signal flow frequently occurs, it is suggested to increase the CRH

parameters of neighboring cells with different LACs in the area.

B. When the overlap coverage of the adjacent cells belonging to different

location areas is rather big, it is suggested to increase the cell reselection

hysteresis parameter.

C. If the coverage of adjacent cells belonging to different LACs is poor at the

joint places, i.e. the coverage hole appears, or if this joint place is an area

where there are few slow moving objects like the highway, etc., it is

suggested to set the reselection hysteresis parameter to 1~3 (i.e. the

reselection hysteresis level is between 2dB and 6dB).

9) Route Area Reselection Hyst.


in the PSI3 message. It indicates a hysteresis value that will be used when

MS selects a cell of another routing area in the STANDBY and READY

states. When the value of this parameter is the same as that of

CellReselHys, it need not be broadcast in the PSI3 message.



Page 327 of 516

Table 6-100 The value range of the “Route Area Reselection Hyst.”

Value The specified CRH level

0 0dB

1 2dB

2 4dB

3 6dB

4 8dB

5 10dB

6 12dB

7 14dB

Setting: 7

10) Reselection Offset Rules

Description: This is a usage parameter at the MS side. It is broadcast to MS in the PSI3 message, indicating whether to adopt extra rules when ReselOff is used.

Value range: 0: Use the positive ReselectOffset for all adjacent cells. 1: Use the positive ReselectOffset only for the adjacent cells with the Max. receiving level.

Setting: 0

11) MS Level Minimal to Access

Description: It is a usage parameter at the MS side. It is broadcast to MS in

the PSI3 message of this cell and the PSI3 and PSI3bis messages of the

adjacent cell. This parameter indicates the Min. receiving level for enabling

MS to access this system (GRPS).To prevent the MS from accessing the

system in case of the low receiving signal level (usually, the communication

quality cannot guarantee normal communication process after accessing),

and from unreasonably wasting the radio sources of the network, it is

stipulated in the GSM system that the receiving level be larger than a

threshold level when the MS needs to access the network, that is:MS Level

Minimal to Access. In addition, it is also one of the decision standards (a

parameter to calculate C31 and C32) for MS to make the cell selection and

reselection.


Page 328 of 516



Page 329 of 516

Table 6-101 The value range of “MS Level Minimal to Access”


0 < -110

1 -110 ~ -109

2 -109 ~ -108 ...

... 61 -50 ~ -49

62 -49 ~ -48

63 > -48

Setting: Commonly, the recommended value should be approximate to the

MS receiving sensitivity, and for some cells with overloaded traffic, the cell

“RxLevAcMin” may be relevantly increased, so as to decrease the C1 and

C2 values of the cell and the cell effective coverage; but, the “RxLevAcMin”

value cannot be too large, otherwise “blind spot” will be created at the cell

boundaries factitiously. When the measure is adopted to balance the traffic,

it is recommended that the level value not exceed -90dBm.At the

preliminary running stage of the network, this parameter can be set as 10

(i.e., -101dBm~-100dBm) or below, which is higher than the MS’s receiving

sensitivity of -102dBm. However, when the network capacity is expanded or

the radio coverage is not a problem in some places, the parameter of

related cells can be set to 2 (i.e. -99dBm~-98dBm).

12) Maximum power of the MS before it receives the network power control

(MS Max TxPwr before POC by Network) Description: This is a usage parameter at the MS side, it is broadcast to MS

in the PSI message of this cell and the PSI13 and PSI3bis messages of the

adjacent cell. During the communication between MS and BTS, its

transmitting power is controlled by the network. The network conducts the

power setting for MS via the power command. MS must output the power

according to the transmitting power planned by the network. If MS cannot

output that power, it will output a power that is closest to that power. When

MS receives the messages from the PBCCH channel, the power used

before receiving the network power control information is determined by

MsTxPwrMaxCCH. This parameter is also a parameter for cell selection and

reselection by MS, involving in calculation of C1 and C2 values.



Page 330 of 516

Table 6-102 The value range of “MS Max TxPwr before POC by Network”


GSM900

Value MS output power (dBm) GSM1800

0~2 39 29 36

3 37 30 34

4 35 31 32

5 33 0 30 ...

...

...

...

17 9 13 4

18 7 14 2

19~31 5 15~28 0

Setting: If this parameter is set too large, the MS near BTS will interfere the

neighboring channels. If it is too small, the MS at the cell boundary will have

low access success rate. Principle of setting this parameter: Under the

precondition that the MS at the cell boundary is guaranteed with certain

access success rate, the MS access level should be reduced as much as

possible. Obviously, the larger the cell coverage, the higher MS output

power level is. Normally, this parameter is recommended to set as 5

(corresponding to GSM900MS) and 2 (corresponding to GSM1800MS). In

practical applications, after the parameter is set, you can test it in an

experiment mode, that is, make a dial test at the cell boundary, and test MS

access success rate and access time with different parameter settings so as

to determine whether to increase or decrease the value of the parameter.

13) Use HCS


HCS parameter. It is broadcast to MS in the PSI3 message, indicating if the

HCS parameters (PriorityClass and HCSThr) exist. If this cell does not use

the HCS parameters, the HCS parameters of other cells will be ignored as

well. That is, all the cells use the infinite HCS signal intensity threshold.

Value range: 0: Not to use the HCS parameters. 1: To use the HCS

parameters.

Setting: 0


Page 331 of 516

14) LSA Index

Description: This parameter is broadcast to MS in the SI4, SI6, SI7 and

PSI3 messages and in the PSI3 and PSI3bis messages of the adjacent

cells. It is used to indicate the LSA identifier of the cell.

Value range: 24bit valid.

Setting: Determined by the network operator after the planning.

15) Allow MS Attempt Access Another

Description: This is a usage parameter at the MS side, broadcast to MS in

the PSI3 message. It indicates if MS is enabled to attempt to access

another cell (if any). If abnormal releases occur during the packet

transmission, MS will abandon all the TBFs that are running. If MS is

enabled to access other cells (RadAcRetry=1), it shall execute abnormal

cell reselection and initialize the establishment of the uplink TBF in the new

cell. If there are other appropriate cells, MS cannot reselect the previous cell

within the period of T_RESEL seconds.

Value range: 0: Disabled. 1: Enabled.

Setting: 0

16) Offset between Same LSA Cell

Description: This parameter is broadcast to MS in the SI4, SI6 and SI7

messages. It is an offset value that will be used when MS is informed to

conduct the LSA reselection between two cells with the same LSA priority.


Table 6-103 The value range of “Offset between Same LSA Cell”

Value Offset

0 0B

1 4B

2 8dB

3 16dB

4 24dB

5 32dB

6 48dB

7 64dB


Page 332 of 516

Setting: 0

17) MS Level Ths. When High Priority Cell Reselect

Description: This parameter is broadcast to MS in the SI4, SI6 and SI7

messages. It is related to the RXLEV_ACCESS_MIN parameter, used to

calculate the C4 standard.


Table 6-104 Value range of “ MS Level Ths. When High Priority Cell Reselect”

Value Offset

0 0dB

1 6dB

2 12dB

3 18dB

4 24dB

5 30dB

6 36dB

7 Infinity

Setting: 1

10. GPRS NC Survey

Fig. 6-34 shows the parameter configuration of the GPRS NC Survey.


Page 333 of 516

Fig. 6-34 Configuring a cell (10)

1) Cell Reselection Survey Report Period (Packet Idle Mode)

Description: This is a usage parameter at the MS side, belonging to the NC

survey parameters. It is broadcast to MS in the PSI5 message, indicating

the report period of the cell reselection survey report when MS is in the

packet idle mode. When NetworkCtrlOrder is NC0, it need not be broadcast

in the PSI5 message.



Page 334 of 516

Table 6-105 Value range of “Cell Reselection Survey Report Period (Packet Idle Mode)”

Value Meaning

0 0.48s

1 0.96s

2 1.92s

3 3.84s

4 7.68s

5 15.36s

6 30.72s

7 61.44s (default value)

Setting: 7

2) Cell Reselection Survey Report Period (Packet Transmission Mode)

Description: This is a usage parameter at the MS side, belonging to the NC survey parameters. It is broadcast to MS in the PSI5 message, indicating the report period of the cell reselection survey report when MS is in the packet transmission mode. When NetworkCtrlOrder is NC0, it need not be broadcast in the PSI5 message.


Table 6-106 The value range of Cell Reselection Survey Report Period (Packet

Transmission Mode)

Value Meaning

0 0.48s

1 0.96s

2 1.92s


4 7.68s

5 15.36s

6 30.72s

7 61.44s

Setting: 3

3) Ns Survey Report Command



Page 335 of 516

PSI1. It indicates the survey report command of MS in the cell.


Table 6-107 The value range of “NS Survey Report Command”

Value Meaning

0 MS controls the cell reselection (=NC0) in the packet idle and packet transmission modes; no survey report shall be sent to the network (=NC0 and EM0); and the PSI5 message shall not be broadcast.

1 MS shall send the survey report and/or the extended survey report to the network, which are used for the cell reselection. Details about further cell selection and survey are included in the PSI5 message.

Setting: 0

4) Network Control Command

Description: This is a usage parameter of MS, belonging to the network

control survey parameters. It is broadcast to MS in the PSI5, PSI13 and SI3

messages, indicating the network control command used in the cell. If is

equal to NC0, the NC survey parameters (NcNoDrxPer, NcRepPerI and

NcRepPerT) can be ignored. If it is equal to NC1 or NC2, while NC survey

parameter is ignored, the default value shall be adopted.


Table 6-108 The value range of “Network Control Command”

Value Meaning

0 NC0: MS controls the cell reselection, without survey reports.

1 NC1: MS controls the cell reselection and sends the survey reports.

2 NC2: The network controls the cell reselection and sends the survey reports.

3 Reserved and interpreted as NC0.

Setting: 0

5) Minimal Time in non-DRX Mode

Description: This is a usage parameter at the MS side, belonging to the NC

survey parameters. It is broadcast to MS in the PSI5 message, indicating

the minimal time within which MS shall be in the non-DRX mode after

sending the NC survey report once. When NetworkCtrlOrder is NC0, it need

not be broadcast in the PSI5 message.


Page 336 of 516


Table 6-109 The value range of “Minimal Time in non-DRX Mode”

Value Meaning

0 No non-DRX mode

1 0.24s


3 0.72s

4 0.96s

5 1.20s

6 1.44s

7 1.92s

Setting: 2

6) MS Extend Survey Command


extend survey parameters. It is broadcast to MS in the PSI5 message,

indicating whether MS conducts the extend survey and how to interpret the

rest extend survey parameters (ExtRepType, NccPermited, ExtRepPer,

etc.).


Table 6-110 The value range of “Ms Extend Survey Command”

Value Meaning

0 EM0. MS shall not conduct the extend survey.

1 EM1. MS shall send the extend survey report to the network.

2 Reserved.

3 Reserved and will be interpreted as EM0.

Setting: 0

7) MS Extend Survey Report Type



indicating the report type of the MS extend survey report. When the

ExtMeaOrder parameter is EM1, it is valid and is sent in the PSI5 message.



Page 337 of 516

Table 6-111 The value range of “MS Extend Survey Report”

Value Meaning

0 Type-1 survey report. If the frequency points of the extend survey are in the six strongest carrier frequencies, it shall be reported no matter if it succeeds in BSIC decoding. The report includes the receiving signal level and BSIC successfully decoded (if any).

1 Type-2 survey report. If the frequency points of the extend survey are in the six strongest carrier frequencies, it succeeds in BSIC decoding, and the survey of the NCC part is permitted, it shall be reported. The report includes the receiving signal level and BSIC successfully decoded.

2 Type-3 survey report. The frequency points of the extend survey shall be reported, while the BSIC decoding is unnecessary. The survey report includes the receiving signal level. Besides, the interference of each carrier frequency shall be reported too.

3 Reserved.

Setting: 0

8) Extend Survey Report Interval



indicating the report interval of the extend survey report. When the

ExtMeaOrder parameter is EM1, it is valid and is sent in the PSI5 message.

Value range: See Table 6-112. Table 6-112 The value range of “Extend Survey Report Interval”

Value Meaning 0 60s 1 120s 2 240s 3 480s 4 960s 5 1920s 6 3840s

7 7680s

Setting: 0


Page 338 of 516

11. GPRS Cell Option

Fig. 6-35 shows the parameter configuration of the GPRS Cell Option.


1) T3168


GPRS cell option parameters. It is broadcast to MS in the PSI1, PSI13 and

SI13 messages. It indicates the Max. time for MS to wait for the “PACKET

UPLINK ASSIGNMENT” message after it sends the “PACKET RESOURCE

REQUEST” (or when the “PACKET DOWNLINK ACK/NACK” message

contains Channel Request Description IE) message.




Page 339 of 516


0 0.0s

1 0.5s

...

...

7 3.5s

Setting: 4 (2 seconds)

2) T3192

Description: This is a usage parameter at the MS side. During the packet

downlink transmission, if the RLC data block to be transmitted is the final

downlink data block, the network will initialize the release of the downlink

TBF by sending one RLC data block whose Final Block Identifier (FBI) is 1

and which has one valid RRBP domain. For each received RLC data block

whose FBI is 1 and which has the valid RRBP domain: A.In the

acknowledged mode, MS shall send the “PACKET DOWNLINK ACK/NACK”

message with the FAI domain of 1 on the uplink block specified by the

RRBP domain. B. In the unacknowledged mode. MS shall send the

“PACKET CONTROL ACKNOWLEDGE” message with the FAI domain of 1

on the uplink block specified by the RRBP domain. In this case, MS starts

the T3192 timer. After T3192 expires, the resources will be released and the

detection of the PDCCH channel will be stopped. Meanwhile, the detection

will turn to the paging channel. In the protection period of the T3192 timer, if

MS receives the “PACKET DOWNLINK ASSIGNMENT” message or

“PACKET TIMESLOT RECONFIGURE” message, the T3192 timer will be

stopped and turn to the packet transmission state.




0 0.0s

1 0.5s

2 1.0s

...

...

7 3.5s

Setting: 1 (0.5 s). The time represented by T3192 must be less than the


Page 340 of 516

protection time T3193 of the downlink TBF at the network side, thus

ensuring TFI of MS is unique at any moment.

3) N3102 Decrease Step (PanDec), N3102 Increase Step (PanInc), and N3102

Max (PanMax)

Description: These are the usage parameters at the MS side, belonging to

the GPRS cell option parameters. They are broadcast to MS in the PSI1,

PSI13 and SI13 messages, indicating the values of PAN_DEC, PAN_INC

and PAN_MAX. Each time MS conducts the cell reselection, the initial value

of the timer N3102 will be set to the PanMax value. 1} When MS receives

the “PACKET UPLINK ACK/NACK” message so that V (S) can advance,

PanInc will be added to N3102 (but no more than PanMax). 2). When MS

detects the stall condition (stall condition, V(S) = V(A) + WS), the timer

T3182 will be started. After receiving the “PACKET UPLINK ACK/NACK”

message that causes V(S) to be less than V(A) + WS, T3182 will be

stopped. If T3182 expires, MS will deduct PanDec from N3102. When

N3102≤0 is met, MS will conduct the cell reselection as an abnormal

release.


Table 6-115 The value range of N3102

Value Value represented

0 4

1 8

2 12

...

...

7 32

Setting: PanDec(0), PanInc(1) and PanMax(7)

4) Network Mode

Description: These are the usage parameters at the MS side, belonging to

the GPRS cell option parameters. They are broadcast to MS in the PSI1,

PSI13 and SI13 messages, indicating the network operation mode in the

cell, which is divided into following three modes:

A. Network mode 1: The network sends the CS paging message to “GPRS


Page 341 of 516

attached” MS over the channel the same as the GPRS paging channel

(packet paging channel or CCCH paging channel), or over the GPRS traffic

channel (when it is assigned with one packet data channel). This means

that MS only needs to monitor one paging channel.

B. Network mode 2: The network sends the CS paging message to “GPRS

attach” MS over the CCCH paging channel, which is also used for the

GPRS paging. This means that MS only needs to monitor the CCCH paging

channel. However, when it is assigned with one packet data channel, the

CS paging message is still transmitted over the CCCH paging channel.

C. Network mode 3: The network sends the CS paging message to “GPRS

attached” MS over the CCCH paging channel. The GPRS paging message

is sent over either the packet paging channel (if available in the cell) or over

the CCCH paging channel. This means MS must monitor two paging

channels to receiving the CS or GPRS paging message (if the packet

paging channel is available in the cell).

Value range: Table 6-116 shows the value of the network modes:

Table 6-116 The value range of the network mode

Value Meaning

0 Network mode 1

1 Network mode 2

2 Network mode 3

3 Reserved

Setting: By default, mode 2 can be set. Like the cells under RAC, NMO must be the same. When the Gs interface exists, MSC can send the CS paging message to “GPRS attached” MS through SGSN. In this case, the network mode 1 can be adopted. When the Gs interface does not exist, only the A interface can be used for sending the CS paging message to “GPRS attached” MS. In this case, we can use: 1) Network mode 2, which means the PCCCH channel may not be assigned for BSS . 2) Network mode 3.

5) Time To Non-Drx Mode



Page 342 of 516


SI13 messages, indicating the value of DRX_TIMER_MAX. MS shall first

enter into the non-DRX mode after changing from the packet transmission

mode to the packet idle mode. The duration of being in the non-DRX mode

is determined by the smaller value of the NON_DRX_TIMER and

DRX_TIMER_MAX parameters.


Table 6-117 The value range of “Time To Non-Drx Mode” parameter

Value Time interval represented

0 0s

1 1s

2 2s

3 4s

...

...

7 64s

Setting: 2

6) Max. Blocks Transmission in Each TS



SI13 messages, indicating the value of the Max. quantity of blocks

(BS_CV_MAX) permitted to be transmitted in each Time Slot (TS). This

parameter determines the time duration (time represented by BS_CV_MAX)

of the timer T3198 that shall be used by MS when it acts as the sending

party and the time duration (time represented by 4×BS_CV_MAX) of the

timer T3200 that is used by MS when it is in the non-DRX mode. Also, it

determines the value of N3104max (=3 × (BS_CV_MAX+3) × quantity of uplink

assignment time slots). All the uplink data blocks sent by MS contain the CV

(COUNT DOWN VALUE) field. The network can use that field to calculate

the data blocks that need to be sent on the current TBF by using that field.


Table 6-118 The value range of “Max. Blocks Transmission in Each TS”

Value Meaning 0 One block (duration) 1 One block (duration)


Page 343 of 516

...

...

15 Fifteen blocks (duration)

Setting: 15

7) Package Control Acknowledgement Default Format

Description: This is a usage parameter at the RLC/MAC layer and at the MS

side on BRP, belonging to the GPRS cell option parameters. It is broadcast

to MS in the PSI1, PSI13 and SI13 messages, indicating the default format

when MS sends the “PACKET CONTROL ACKNOWLEDGEMENT”

message.


Table 6-119 The value range of “ Package Control Acknowledgement Default Format”

Value Meaning

0 The default format is four access bursts.

1 The default format is RLC/MAC block.

Setting: 1

8) Access Burst Bit Type



SI13 messages, indicating whether the 8-bit or 11-bit access burst will be

used in the PRACH, PTCCH/U and PACKET CONTROL

ACKNOWLEDGEMNT messages. The 11-bit access burst has more

abundant contents than the 8-bit access burst, without any other essential

difference.


Table 6-120 The value range of “Access Burst Bit Type”

Value Meaning

0 To use 8-bit access burst

1 To use 11-bit access burst

Setting: 0

12. GPRS Other


Page 344 of 516

Fig. 6-36 shows the parameter configuration of other GPRS parameters.


1) Allow Send SYS16 and SYS17 of System Information on BCCH

Description: According to the definition in the GSM specification, the cell

selection and reselection of MS depend on the parameter C1 and C2, and

whether C2 is used as the cell reselection parameter is determined by the

network operators. AdditionReselPI (Additional Reselect Param Ind, ACS) is

used to notify the MS whether C2 is adopted during the cell reselection. This

parameter is broadcast to the MS in the cell via the “RIL3_RR SYSTEM

INFORMATION TYPE3” and “TYPE4” messages, and is one of the cell

selection parameters.

Value range: 0: If the rest Octets of SYSTEM INFORMATION TYPE4 (SI4

Rest Octets) exist, MS shall derive the parameter PI related to the cell

reselection and the parameters related to the C2 calculation from them. 1:

MS shall derive the parameter PI related to the cell reselection and the

parameters related to the C2 calculation from the rest Octets of SYSTEM

INFORMATION TYPE7 or 8 (SI7/8 Rest Octets).


Page 345 of 516

Setting: Normally, the system messages 7 and 8 are seldom used, and

AdditionReselPI must be set to 0. Otherwise most of MSs (NEC) cannot

access the network.

2) Si3 Position


SI3, SI4, SI7 and SI8 and in PSI3 of the adjacent cells. It indicates the

scheduling position of SI13 on BCCH. The system information 13 is related

to the GPRS service only, and can be sent either at the BCCH Norm

position (in this case the BCCH block whose TC is equal to 4 is occupied;

TC=(FN DIV 51)mod(8))) or at the BCCH Ext position (in this case one fixed

AGCH block whose TC is equal to 0 is occupied). When it is sent at the

BCCH Ext position, the possibility that SI13 can be sent successfully is

small as it needs to compete with other messages (e.g. the immediate

assignment message) for the sending opportunity. In this case, the “Quantity

of access permit reserved blocks” (BsAgBlkRes in the R_BTS table) must

be bigger than 0. Otherwise, SI13 will have no chance to be transmitted.

Value range: 0: To send on BCCH Norm. 1: To send on BCCH Ext.

Setting: 0

3) Route Area Color Code


in SI3, SI4, SI7 and SI8, with the usage similar to that of BTS Color Code

(BCC) in the GSM system. In some cases (cell reselection spanning BSCs),

to ensure MS can originate the “Routing area update” process, the GPRS

network will allocate different RaColor values to adjacent cells with the

same routing area code. Thus, when MS receives different RaColor values

in the cells having the same routing area code, it will originate the “Routing

area update” process just like the case where it spans two different routing

areas.

Value range: 0 ~ 7


4) Priority Of Package Access Allow


in PSI13 and SI13 messages, indicating the priority of the MS package


Page 346 of 516

access allowed by the cell. Its functions are similar to those of ACCESS

CLASS.


Table 6-121 The value range of “ Priority Of Package Access Allow”

Value Meaning

0 Package access not allowed in the cell.

1 Not used. It shall be interpreted as that package access is not allowed in the cell.

2 Not used. It shall be interpreted as that package access is not allowed in the cell.

3 It is allowed to access the package with the priority 1.

4 It is allowed to access the packet with the priorities 1 and 2.

5 It is allowed to access the package with the priorities 1 ~ 3.

6 It is allowed to access the package with the priorities 1 ~ 4.

7 Package access allowed in the cell.

Setting: 7

5) Idle Channel Num Ths on CS Mode (PS+CS=>PS)

Description: This is a DBS usage parameter on Pn. It indicates the Min.

threshold of the idle channel number in the CS mode when the network

decides to convert one PS+CS channel into a PS channel. If the idle

channel number is smaller than this threshold, it is not allowed to convert

one dynamic PS+CS channel into a PS channel. When one PS+CS channel

in the CS mode is released, if the total number of idle channels in the cell is

bigger than that threshold, the PS+CS channel can be converted into the

PS channel.


Setting: 2

6) High Rate System Information

Description: This is a global process usage parameter on BRP, indicating if

various PSI messages need to be sent at high rates. As the total amount (16)

of package system messages that can be transmitted at high rates is limited,

and the amount of messages to be transmitted always varies since each


Page 347 of 516

kind of package system message has different content lengths, users can

only roughly determine the requirements of the transmission rate of each

kind of system message. Before the transmission, the global process will

dynamically determine the transmission rate of each kind of system

package message according to the user requirements (analyzing according

to the array subscripts 0~5 of SendSpeed in turn) and system restrictions.

The package system messages corresponding to the array subscripts are

as follows: 0: PSI2; 1: PSI3; 2: PSI3BIS; 3: PSI4; 4: PSI5; 5: PSI13.


Table 6-122 Value range of “High Rate System Information”

Value Meaning

0 Not transmitted at high rates

1 It is allowed to transmit at high rates

Setting: 1

7) Support SPLIT_PG_CYCLE on CCCH

Description: This is a usage parameter at the MS and FUC sides, broadcast

to MS in the PSI13 and SI13 messages. It indicates if the “SplitPgCycle”

function is supported on the cell CCCH. The “SplitPgCycle” function means

that messages like “Package immediate assignment”, “Package paging”,

“Package immediate assignment reject”, etc., can be sent on several

BLOCKs.

Value range: 0: The cell CCCH does not support SPLIT_PG_CYCLE; 1: The

cell CCCH supports SPLIT_PG_CYCLE.

Setting: 0

8) PSI1 Msg. Repeat Prd

Description: This is a usage parameter at the MS and FUC sides, broadcast

to MS in the PSI1 message and in the PSI13 and SI3 messages of this cell

and adjacent cells. It indicates if the transmitting period and transmission

position of the cell PSI1 message. PSI includes the information about the

cell reselection, PRACH control, description of the control channel, possible

global power control parameters, etc. If only PBCCH exists, it will be sent at

a high repeat rate.


Page 348 of 516


Table 6-123 The value range of “ PSI1 Msg. Repeat Prd”

Value Meaning

0 The PSI1 repeat period is equal to 1 multiframe.

1 The PSI1 repeat period is equal to 2 multiframes.

...

...

15 The PSI1 repeat period is equal to 16 multiframes.

Setting: 1

9) Support PACKET PSI STATUS Msg.

Description: This is a usage parameter at the MS side and on BRP,

broadcast to MS in the PSI1 message. It indicates if the network supports

the “PACKET PSI STATUS” message. This function is optional. When

PsiStaInd is equal to 1, MS can send the “PACKET PSI STATUS” message

to the network, indicating the current value of the PSI message saved in MS.

Then, the network can set the PSI message needed by this MS on PACCH,

so as to speed the background follow-up processes (otherwise the PSI

message can be detected only at the time planned by the network).


Table 6-124 The value range of “Support PACKET PSI STATUS Msg.”

Value Meaning

0 The network does not support the “PACKET PSI STATUS” message.

1 The network supports the “PACKET PSI STATUS” message.

Setting: 0

10) PPCH Load Calculation Prd.

Description: PPCH load calculation period is a BRP usage parameter.

Value range: 0 ~ 16


Page 349 of 516

Setting: 10

11) PRACH Load Report Period

Description: PRACH load report period

Value range: 0 ~ 255 (s)

Setting: 10 s

12) Initial Value Of Link Error Timer

Description: Initial value of the link error timer


Setting: 20

13) Power Threshold of PRACH Load

Description: Power threshold of PRACH load

Value range: 0 ~ 100(%)

Setting: 20

14) Support Extend Page Mode in Cell

Description: To indicate if the extend paging mode is supported.

Vale range: 0 or 1.

Setting: 0

13. GPRS Channel

Fig. 6-37 shows the parameter configuration of the GPRS channel.


Page 350 of 516


1) Blocks for PBCCH in Frames

Description: This is a usage parameter at the MS side, one of the PCCCH

structure parameters. It is broadcast to MS in the PSI1 message. It indicates

the amount of blocks used as PBCCH in a 52-multiframe (12 blocks). The

PBCCH block is used by the package system messages transmitted at the

high and low rates at the same time. The message transmitted at high rate

has a higher priority. This parameter needs to be configured together with

the “PSI1_REPEAT_PERIOD” parameter in the PSI1 message, so as to

ensure both the high-rate and low-rate package system messages have the

block resources for transmission.


Table 6-125 The value range of “Blocks for PBCCH in Frames”

Value Meaning

0 PBCCH occupies one block in the multiframe.

1 PBCCH occupies two blocks in the multiframe.

2 PBCCH occupies three blocks in the multiframe.


Page 351 of 516

Value Meaning

3 PBCCH occupies four blocks in the multiframe.

Setting: 0

2) Blocks for PAGCH in Frames


organization parameters. It is broadcast to MS in the PSI1 message. It

indicates the amount of blocks on which neither the package paging nor the

PBCCH can appear in a 52- multiframe. On these blocks, only PAGCH,

PDTCH and PACCH appear. The “UPLINK ASSIGNMENT” message will be

sent on these fixed blocks by preference, so as to speed the establishment

of the uplink TBF. When MS sends the channel request on the PRACH

channel, it will wait “UPLINK ASSIGNMENT” message on all the PCCCH

channels whose time slots are the same as those of the PRACH channels.


Table 6-126 The value range of “Blocks for PAGCH in Frames”

Value Meaning

0 The amount of blocks reserved for PAGCH, PDTCH and PACCH is 0.


...

...


13~15 The same as 0.

Setting: 5

3) Fixed Block for PRACH on PCCCH


organization parameters. It is broadcast to MS in the PSI1 message. It

indicates the amount of fixed blocks reserved for the PRACH channel by the

PDCH channel bearing PCCCH. These blocks need to be marked with

“USF=FREE”. MS can use this parameter or “USF=FREE” to determine the

allocation of PRACH.


Page 352 of 516


Table 6-127 The value range of “Fixed Block for PRACH on PCCCH”

Value Meaning

0 The amount of fixed blocks reserved for the PRACH channel is 0.


...

...


13~15 The same as 0.

Setting: 2

4) Max Retrans. Times on Different Priority

Description: This is a usage parameter at the MS side, one of the PRACH

control parameters. It is broadcast to MS in the PSI1 message. It indicates

the Max. times of random access attempts of MS with priorities 1 ~ 4

permitted on PRACH.

Value range: This parameter is an array and the array element is 4. The first

array element corresponds to the Max. times of attempts permitted of

priority 1 and so on. Table 6-128 shows the value range of Max.

retransmission times of different priorities.

Table 6-128 Value range of “Max Retrans. Times on Different Priority”

Value Meaning

0 One attempt allowed.

1 Two attempts allowed.

2 Four attempts allowed.

3 Seven attempts allowed.

Setting: 2

5) Access and Persist Level of Different Radio Priority


control parameters. It is broadcast to MS in the PSI1 message. The network

sets corresponding level threshold P[i](i=1, 2, 3, 4) for MS of each radio

priority. For each package access attempt, MS will derive one random value

R with even probability distribution from the set {0, 1, ..., 15}. Only when P[i]


Page 353 of 516

is less than or equal to R, will MS be allowed to originate the package

access attempt.

Value range: This parameter is an array and the array element is 4. The first

array element corresponds to the access persist level of radio priority 1 and

so on. Table 6-129 shows the value range of “Access and Persist Level of

Different Radio Priority”.

Table 6-129 Value range of “Access and Persist Level of Different Radio Priority”

Value Meaning

0 Persist level 0

1 Persist level 1

...

...

14 Persist level 14

15 Persist level 16

Setting: 0

6) Min TS Interval of Adj Channel Requirement


control parameters. It is broadcast to MS in the PSI1 message. Each time a

new connection is created, MS normally will send the channel request

message to the network on the PRACH channel. As PRACH is one ALOHA

channel, the network allows MS to send multiple channel request messages

before receiving the package assignment message so as to enhance the

success probability of MS access. When no response to the previous

channel request message is returned, MS will wait a random period of time

and then send the channel request message again. The parameter TxInt is

used to determine the random period of wait.


Table 6-130 The value range of “Min TS Interval of Adj Channel Requirement”

Value Meaning

0 The amount of extended TSs is 2.




Page 354 of 516

Value Meaning














Setting: 2

7) TS Number of Trans. Random Access


control parameters. It is broadcast to MS in the PSI1 message. Each time a

new connection is created, MS normally will send the channel request

message to the network on the PRACH channel. As PRACH is one ALOHA

channel, the network allows MS to send multiple channel request messages

before receiving the package assignment message so as to enhance the

success probability of MS access. When no response to the previous

channel request message is returned, MS will wait a random period of time

and then send the channel request message again. The parameter S is

used to determine the random period of wait.


Table 6-131 Value range of “TS Number of Trans. Random Access”

Value Meaning

0 S=12

1 S=15

2 S=20

3 S=30


Page 355 of 516

Value Meaning

4 S=41

5 S=55

6 S=76

7 S=109

8 S=163

9 S=217

10~15 Reserved.

Setting: 2

14. GPRS Power Control

Fig. 6-38 shows the parameter configuration of the GPRS power control.



Page 356 of 516

1) MS Power Control Parameter Alpha

Description: This is a usage parameter at the MS side, one of the global

power control parameters and GPRS power control parameters. It is

broadcast to MS in the PSI1, PSI13 and SI13 messages. It determines the

value of the MS power control parameter Alpha(α).


Table 6-132 Value range of “MS Power Control Parameter Alpha”

Value Meaning

0 α = 0.0

1 α = 0.1

...

...

10 α = 1.0

11~15 α = 1.0

Setting: 0

2) Filter Period of Power (Frames): Packet Idle Mode




filter period of one signal power during the power control in the packet idle

mode.


Table 6-133 The value range of the filter period of power (frames) in packet idle mode

Value Meaning

0 Multiframes with the filter period of 2(0/2)/6


...

...


26~31 Multiframes with the filter period of 2(25/2)/6

Setting: 0

3) Filter Period of Power (Frames): Packet Transmission Mode


Page 357 of 516




filter period of one signal power during the power control in the packet

transmission mode.


Table 6-134 The value range of the filter period of power (frames) in the packet

transmission mode

Value Meaning



...

... 25 Multiframes with the filter period of 2(25/2)/6

26~31 Reserved.

Setting: 0

4) PBCCH Power Decrease according to BCCH (-2dB)


power control parameters and PBCCH descriptive parameters. It is


power decrease value corresponding to the output power of BCCH used on

the PBCCH block.


Table 6-135 The value range of “ PBCCH Power Decrease according to BCCH (-2dB)”

Value Meaning

0 Pb = 0dB

1 Pb = -2dB

...

...

15 Pb = -30dB

Setting: When PBCCH is on the BCCH frequency, Pb must adopt 0.

5) Survey Position


Page 358 of 516




position where the downlink power shall be surveyed for the sake of uplink

power control.


Table 6-136 The value range of “Survey Position”

Value Meaning

0 Downlink survey shall be made on BCCH for the power control.

1 Downlink survey shall be made on PDCH for the power control.

Setting: 0

6) Sending PSI4

Description: This is a usage parameter at the MS side, i.e.

INT_MEAS_CHANNEL_LIST_AVAIL. It is one of the global power control

parameters, broadcast to MS in the PSI1 message. This parameter

indicates whether to broadcast the optional PSI4 message. If yes, the

channel list of interference survey will be included.

Value range: 0: Not to broadcast the PSI4 message. 1: To broadcast the

PSI4 message.

Setting: 0

7) Filter Const of Interference Signal Power



broadcast to MS in the PSI1, PSI13 and SI13 messages. It determines a

filter constant of interference signal power for the power control.


Table 6-137 The value range of “ Filter Const of Interference Signal Power”

Value Meaning

0 Filter constant 2(0/2)



Page 359 of 516

...

...


Setting: 0

6.1.4 Configuring Cell

In the main interface (shown in Fig. 6-2), select “Cell” and right click to pop up a menu of options: Configure TRX, Configure Disturbance Cell, Configure CA Frequency, Configure Handover Control, Configure Power Control, Configure Adjacent Cell Handover and Reselection, Configure Adjacent Cell Handover, Configure Adjacent Cell Reselection, and Configure Frequency Hopping System (FHS). The radio parameters related to these options will be detailed in the following.

6.1.4.1 Configuring a transceiver (TRX)

In the main interface (shown in Fig. 6-2), select “Cell” and right click to pop up a menu of options. Select “Configure TRX” from the menu, as shown in Fig. 6-39.

Fig. 6-39 Configuring TRX

1. Transceiver No. (trxid)

Description: the No. of the current TRX.

2. TRX Type (trxtype)

Description: the type of TRX, usually used in concentric circle.


Page 360 of 516


Table 6-138 TRX type

TrxType Type

0 Common type (outer circle)

1 Special type (inner circle)

Default: 0

3. Correlation TelecomLapdLink DN

Description: DN of Lapdlink used by baseband TRX. It is the internal

parameter of OMCR (V2).

4. Correlation RadioCarrier No.

Description: the radio carrier No. corresponding to this baseband TRX.

5. Allocation priority of the same carrier frequency type

Description: the allocation priority of the carrier frequencies of the same type.

6. Correlation Bts Board

Description: the DN of the relevant equipment under this BSS: SiteId-Rack-Shelf-Panel.

6.1.4.2 Configuring a disturbance cell

In the main interface (shown in Fig. 6-2), select “Cell” and right click to pop up a menu of options. Select “Configure Disturbance Cell” from the menu, as shown in Fig. 6-40.


Page 361 of 516

Fig. 6-40 Configuring a disturbance cell

1. InterferenceCell No.

Description: No. of the current interference cell.

2. Relation Cell DN:

Description: the DN of the external cell under this BSS: BssId-EcId.

6.1.4.3 Configuring CA frequency

In the main interface (shown in Fig. 6-2), select “Cell” and right click to pop up a menu of options. Select “Configure CA Frequency” from the menu, as shown in Fig. 6-41.

Fig. 6-41 Configuring CA frequency


Page 362 of 516

1. Carrier No.: ID of the carrier frequency.

2. TxPwrMax: the power level of the corresponding carrier frequency.

Description: the power level of the corresponding carrier frequency.

Value range: 1 ~ 8

Default: dynamic

3. TxPwrMax Modulate Value

Description: the static power level of TRX of the cell, used to adjust the transmitting power of the carrier frequency.

Value range: 0 ~ 6

Default: 0

4. Absolute Radio Carrier

1) Cell frequency list

Description: the list of the absolute RF channel numbers of various

frequencies used by the cell. This parameter should be broadcast in some

form to MSs in the cell via “RIL3_RR SYSTEM INFORMATION TYPE1”

message. This parameter is broadcast to MSs mainly to decode the Mobile

Allocation (MA) table used for frequency hopping. At present, appearance of

two frequencies (900M and 1800M) in the same cell is not supported.

Value range: this parameter can be regarded as an array, each element of

which is the size of a word (16bit), standing for a frequency. The value

range of each element is 0 ~ 1023, and elements should be sequenced

according to the following rules:

A. The GSM900 frequencies in the range of 1 ~ 124 and 975 ~ 1023 are

sequenced in ascending order; frequency 0, if any, is sequenced at the last.

B. GSM1800M frequencies are sequenced in ascending order.

The number of valid elements (counted from the beginning) in an array is

determined by the previous parameter CaFreqNum (number of cell

frequencies).

2) BA frequency list

Description: the list of the absolute RF channel numbers of BCCH carrier


Page 363 of 516

monitored by the idle MS. This parameter should be broadcast in some form

to MSs in the cell via “RIL3_RR SYSTEM INFORMATION TYPE2”, “2bis” or

“2ter” message.

Value range: this parameter can be regarded as an array, each element of

which is the size of a word (16bit), standing for a frequency. The value

range of each element is 0 ~ 1023, and elements should be sequenced

according to the following rules:

A. Frequencies 1 ~ 124 are lined at the head in ascending order;

B. Frequencies 975 ~ 1023 and frequency 0, if any, are lined behind 1) in

ascending order. Frequency 0, if any, is behind 975 ~ 1023;

C. Frequencies 512 ~ 885, if any, are lined behind 2) in ascending order.

The number of valid elements (counted from the beginning) in an array is

determined by the previous parameter BaFreqNum (number of BA

frequencies).

Setting: This parameter must contain ARFCN of BCCH of this cell.

6.1.4.4 Configuring power control

In the main interface (shown in Fig. 6-2), select “Cell” and right click to pop up a menu of options. Select “Configure Power Control” from the menu, as shown in Fig. 6-42 and Fig. 6-43.

1. Power Survey

The parameters of Power Survey in GSM environment are shown in Fig.

6-42, and those in GPRS environment are shown in Fig. 6-43.


Page 364 of 516

Fig. 6-42 Power survey - GSM

Fig. 6-43 Power survey - GPRS

1) Sample Count of Uplink Level

Description: In GSM system, BSC makes power control decision according

to the measurement data. To avoid the bad effect of burst measurement


Page 365 of 516

value resulting from complicated radio transmission, BSC, when making

power control decision, no longer uses the original measurement data but

uses a series of average values of the measurement data, thus reducing the

effect of burst measurement value. Parameter PcUlLevWindow (power

control uplink level average window) is the size of the window used to

calculate the average value of uplink signal level. This size is the number of

samples used in averaging.

Value range: 1 ~ 32

Default: 6

2) Reserve Count of Uplink Level

Description: According to GSM Specifications, discontinuous transmission

(DTX) refers to the process that the system does not transmit signals in the

speech pause period during the subscriber communication process. If DTX

mode is used, the measurement data reported to BSC include two types.

One is the average of the measurement results of all timeslots in a

measurement period in non-DTX mode, and the other is the average of the

measurement results of some special timeslots in a measurement period in

DTX mode. BSC needs to select one type of measurement data according

to the actual conditions and use the data to calculate the average value.

The first type of measurement data is the average of the measurement

results of all timeslots, so it is quite accurate. But the second type of

measurement data is the average of the measurement results of some

timeslots, so it is less accurate. Therefore, BSC, when averaging the

measurement values, should use different weights for the two types of

measurement data. Parameter PcUlLevWeight determines the weight for

the first type (for all timeslots) of measurement data when averaging

downlink signal intensity for power control. The weight for the second type

(for some timeslots) of measurement data is 1 by default.

Value range: 1 ~ 3

Default: 2

3) Sample Count of Downlink Level





Page 366 of 516



effect of burst measurement value. Parameter PcDlLevWindow (power

control downlink intensity average window) is the size of the window used to

calculate the average value of downlink signal intensity. This size is the

number of samples used in averaging.

Value range: 1 ~ 32

Default: 6

4) Reserve Count of Downlink Level















measurement data. Parameter PcDlLevWeight determines the weight for


downlink signal intensity for power control. The weight for the second type

(for some timeslots) of measurement data is 1 by default.

Value range: 1 ~ 3

Default: 2

5) Sample Count of Uplink Quality






Page 367 of 516


effect of burst measurement value. Parameter PcUlQualWindow (power

control uplink quality average window) is the size of the window used to

calculate the average value of uplink signal quality. This size is the number

of samples used in averaging.

Value range: 1 ~ 32

Default: 6

6) Reserve Count of Uplink Quality















measurement data. Parameter PcUlQualWeight determines the weight for

the first type (for all timeslots) of measurement data when averaging uplink

signal quality for power control. The weight for the second type (for some

timeslots) of measurement data is 1 by default.

Value range: 1 ~ 3

Default: 2

7) Sample Count of Downlink Quality







Page 368 of 516

effect of burst measurement value. Parameter PcDlQualWindow (power

control downlink quality average window) is the size of the window used to

calculate the average value of downlink signal quality. This size is the


Value range: 1 ~ 32

Default: 6

8) Reserve Count of Downlink Quality















measurement data. Parameter PcDlQualWeight determines the weight for


downlink signal quality for power control. The weight for the second type (for

some timeslots) of measurement data is 1 by default.

Value range: 1 ~ 3

Default: 2

9) Performance Survey Report Period

Description: Power control performance survey report period (51

multi-frames).

Default: 10

2. Power Adjust Threshold

The parameters of Power Adjust Threshold in GSM environment are shown


Page 369 of 516

in Fig. 6-44, and those in GPRS environment are shown in Fig. 6-45.

Fig. 6-44 Power adjust threshold - GSM

Fig. 6-45 Power adjust threshold - GPRS

1) Threshold, Value P and Value N of Pwr. INC due to Uplink Level

Description: according to GSM Specifications, after a series of averages are


Page 370 of 516

obtained, power control decision can be made. One of the factors which

may lead to MS (uplink) power increase. The decision process is like this: if

P out of N recent uplink signal intensity averages are smaller than the

related threshold, then MS (uplink) transmitting power should be increased,

because the uplink signals are too weak. Parameter PcUlInclLevThs defines

the related threshold, parameter PcUlInclLevN defines the related N value,

and parameter PcUlInclLevP defines the related P value.

Value range: 1≤PcUlInclLevP≤PcUlInclLevN≤31; the value range of the

threshold is shown in Table 6-139.


Page 371 of 516

Table 6-139 Value range of “Threshold of Pwr. INC due to Uplink Level”

Threshold Corresponding level value (dBm)

0 < -110

1 -110 ~ -109 …

…

62 -49 ~ -48

63 > -48

Default: 18, P=3, N=4

2) Threshold, Value P and Value N of Pwr. INC due to Downlink Level



may lead to BTS (downlink) power increase. The decision process is like

this: if P out of N recent downlink signal intensity averages are smaller than

the related threshold, then BTS (downlink) transmitting power should be

increased, because the downlink signals are too weak. Parameter

PcDlInclLevThs defines the related threshold, parameter PcDlInclLevN

defines the related N value, and parameter PcDlInclLevP defines the related

P value.

Value range: 1≤PcDlInclLevP≤PcDlInclLevN≤31; the value range of the


Table 6-140 Value range of “Threshold of Pwr.. INC due to Downlink Level”


0 < -110

1 -110 ~ -109 …

…

62 -49 ~ -48

63 > -48


3) Threshold, Value P and Value N of Pwr. DEC due to Uplink Level




Page 372 of 516

may lead to MS (uplink) power decrease. The decision process is like this: if

P out of N recent uplink signal intensity averages are larger than the related

threshold, then MS (uplink) transmitting power should be decreased,

because the uplink signals are too strong. Parameter PcUlRedLevThs

defines the related threshold, parameter PcUlRedLevN defines the related

N value, and parameter PcUlRedLevP defines the related P value.

Value range: 1≤PcUlRedLevP≤PcUlRedLevN≤31; the value range of the


Table 6-141 Value range of “Threshold of Pwr. DEC due to Uplink Level”


0 < -110

1 -110 ~ -109

2 -109 ~ -108 …

…

61 -50 ~ -49

62 -49 ~ -48

63 > -48


4) Threshold, Value P and Value N of Pwr. DEC due to Downlink Level



may lead to BTS (downlink) power decrease. The decision process is like

this: if P out of N recent downlink signal intensity averages are larger than


decreased, because the downlink signals are too strong. Parameter

PcDlRedLevThs defines the related threshold, parameter PcDlRedLevN

defines the related N value, and parameter PcDlRedLevP defines the

related P value.

Value range: 1≤PcDlRedLevP≤PcDlRedLevN≤31; the value range of the

threshold is in Table 6-142.

Table 6-142 Value range of “Threshold of Pwr. DEC due to Downlink Level”


Page 373 of 516


0 < -110

1 -110 ~ -109

2 -109 ~ -108 …

…

62 -49 ~ -48

63 > -48


5) Threshold, Value P and Value N of Pwr. INC due to Uplink Quality


obtained, power control decision can be made. one of the factors which

may lead to MS (uplink) power increase. The decision process is like this: if

P out of N recent uplink signal intensity averages are larger than the related

threshold, then MS (uplink) transmitting power should be increased,

because the uplink signal quality is too poor. Parameter PcUlInclQualThs

defines the related threshold, parameter PcUlInclQualN defines the related

N value, and parameter PcUlInclQualP defines the related P value.

Value range: 1≤PcUlInclQualP≤PcUlInclQualN≤31; the value range of the


Table 6-143 Value range of “Threshold of Pwr. INC due to Uplink Quality”

Threshold Corresponding quality level Meaning

0 0 BER<0.2%

1 1 0.2%<BER<0.4% …

…

…

6 6 6.4%<BER<12.8%

7 7 12.8%<BER


6) Threshold, Value P and Value N of Pwr. INC due to Downlink Quality



may lead to BTS (downlink) power increase. The decision process is like

this: if P out of N recent downlink signal intensity averages are larger than


Page 374 of 516


increased, because the downlink signal quality is too poor. Parameter

PcDlInclQualThs defines the related threshold, parameter PcDlInclQualN

defines the related N value, and parameter PcDlInclQualP defines the

related P value.

Value range: 1≤PcDlInclQualP≤PcDlInclQualN≤31; the value range of the


Table 6-144 Value range of “Threshold of Pwr. INC due to Downlink Quality”

Threshold Corresponding quality level

Meaning

0 0 BER<0.2%

1 1 0.2%<BER<0.4%

2 2 0.4%<BER<0.8% …

…

…

7 7 12.8%<BER


7) Threshold, Value P and Value N of Pwr. DEC due to Uplink Quality



may lead to MS (uplink) power decrease. The decision process is like this: if

P out of N recent uplink signal intensity averages are smaller than the

related threshold, then MS (uplink) transmitting power should be decreased,

because the uplink signal quality is too good. Parameter PcUlRedQualThs

defines the related threshold, parameter PcUlRedQualN defines the related

N value, and parameter PcUlRedQualP defines the related P value.

Value range: 1≤PcUlRedQualP≤PcUlRedQualN≤31; the value range of the


Table 6-145 Value range of “Threshold of Pwr. DEC due to Uplink Quality”

Threshold Corresponding quality level

Meaning

0 0 BER<0.2%

1 1 0.2%<BER<0.4%


Page 375 of 516

2 2 0.4%<BER<0.8% …

…

…

6 6 6.4%<BER<12.8%

7 7 12.8%<BER


8) Threshold, Value P and Value N of Pwr. DEC due to Downlink Quality


obtained, power control decision can be made.Downlink receiving quality is

one of the causes for BTS (downlink) power decrease. The decision

process is like this: if P out of N recent downlink signal quality averages are

smaller than the related threshold, BTS (downlink) transmitting power

should be decreased, because the downlink signal quality is too good.

Parameter PcDlRedQualThs defines the related threshold, parameter

PcDlRedQualN defines the related N value, and parameter PcDlRedQualP

defines the related P value.

Value range: 1≤PcDlRedQualP≤PcDlRedQualN≤31; the value range of the


Table 6-146 Value range of “Threshold of Pwr. DEC due to Downlink Quality”

Threshold Corresponding quality level Meaning

0 0 BER<0.2%

1 1 0.2%<BER<0.4%

2 2 0.4%<BER<0.8% …

…

…

6 6 6.4%<BER<12.8%

7 7 12.8%<BER


3. Power Control

The parameters of Power Control in GSM environment are shown in Fig.

6-46, and those in GPRS environment are shown in Fig. 6-47.


Page 376 of 516

Fig. 6-46 Power Control parameters - GSM

Fig. 6-47 Power Control parameters - GPRS

1) Power Control Object No.

Description: No. of the power control object.

2) Allow Rapid Power Control


Page 377 of 516

Description: whether rapid power control process is allowed. Rapid power

control process is an option of BSC. Rapid power control can decrease the

interference of the whole system and meet the need of dynamic power

control of rapidly moving MS. The amplitude of power control used by rapid

power control process each time is no longer a fixed value, but a integer

multiple of cell parameter power control step (increase and decrease).

Parameter RapidPc determines whether rapid power control process is

allowed.

Value range: False: the rapid power control process is not used; True: the

rapid power control process is used

Fault: False

3) Max. Value of Power DEC

Description: when the system can perform rapid power control for the

reason of quality, to prevent MS call drop due to too rapid power decrease,

the corresponding power decrease max. limit is set, corresponding to the

respective quality level. E.g. PwrDecrLimit[0] determines the max. power

decrease limit for (BER<0.2%) calls whose quality level is 0. Note that this

parameter is valid for both uplink and downlink.

Value range: This parameter can be regarded as a array with eight elements,

each of which is a byte. PwrDecrLimit[n] determines the max. power

decrease available to calls whose quality level is n. The value range of each

element is 0 ~ 38, standing for 0 ~ 38dB

Setting: 38 may be set as the default value. If performance statistics

parameter shows that power decrease leads to a lot of call drops, then

corresponding limits should be set according to the performance statistics

parameter.

Default: 38

4. Other

Other parameters in GSM environment are shown in Fig. 6-48, and those in

GPRS environment are shown in Fig. 6-49.


Page 378 of 516

Fig. 6-48 Other power control parameters - GSM

Fig. 6-49 Other power control parameters - GPRS

1) Min. Time Interval of RxLev Power Adjust

Description: this parameter specifies the minimal interval of power control.

Usually, after power control, it is likely to receive two survey reports using


Page 379 of 516

the original transmitting power. The signal level information in the reports is

not accurate and thus should be ignored (other information like adjacent cell

information is still valid), therefore there should be a minimal interval of

power control, during which signal level information etc. is ignored.

Value range: 0 ~ 32

Default: 2

2) Allow Uplink Power Control

Description: whether uplink power control is allowed in the cell, i.e. whether

power control is performed on MS.

Value range: True: allow uplink power control; False: do not allow uplink

power control.

Default: True

3) Allow Downlink Power Control

Description: whether downlink power control is allowed in the cell, i.e.

whether power control is performed on BTS.

Value range: True: allow downlink power control; False: do not allow

downlink power control.

Default: True

4) MS TxPwr Increase Step

Description: power increase step. This parameter is used in both directions.

Value range: see Table 6-147.

Table 6-147 The value range of “MS TxPwr Increase Step”

Value Step represented

0 2 dB

1 4 dB

2 6 dB

Default: 0

5) MS TxPwr Decrease Step

Description: power decrease step. This parameter is used in both directions.


Page 380 of 516


Table 6-148 The value range of “MS TxPwr Decrease Step”

Value Step represented

0 2dB

1 4dB

2 6dB

Default: 0

6) MS Max. TxPwr

Description: During the communication between MS and BTS, the transmitting power of MS is controlled by the network, the network sets the power for MS via the power command and the command is transmitted on SACCH (the SACCH has 2 header bytes, one is the power control byte and the other is the timing advance). The MS must extract the control header from the downlink SACCH and takes the specified transmitting power as the output power; if the power level of MS cannot output the power value, it will output the closest transmitting power that can be outputted. When the BSC controls the power, the parameter is the maximum transmitting power that can be adopted by MS in the cell. MsTxPwrMax is also a parameter used by BSC to calculate PBGT value.


Table 6-149 The value range of “MS Max. TxPwr”

GSM900 GSM1800

Value The MS output power (dBm)


0 ~ 2 39 29 36

3 37 30 34

4 35 31 32

5 33 0 30 …

…

…

…

17 9 13 4

18 7 14 2

19 ~ 31 5 15 ~ 28 0

Setting: This parameter is usually set to a value identical to

MsTxPwrMaxCch of the cell.


Page 381 of 516

Default: 5 (GSM900), 0 (GSM1800)

7) MS Min. TxPwr

Description: During the communication between MS and BTS, the

transmitting power of MS is controlled by the network, the network sets the

power for MS via the power command and the command is transmitted on

SACCH (the SACCH has 2 header bytes, one is the power control byte and

the other is the timing advance). The MS must extract the control header

from the downlink SACCH and takes the specified transmitting power as the

output power; if the power level of MS cannot output the power value, it will

output the closest transmitting power that can be outputted. When BSC is

performing power control, this parameter is the minimal transmitting power

(i.e. lower limit of power control) that can be used by MS in the cell.


Table 6-150 The value range of “ MS Min. TxPwr”

GSM900 GSM1800



0 ~ 2 39 29 36

3 37 30 34

4 35 31 32 …

…

…

…

17 9 13 4

18 7 14 2

19 ~ 31 5 15 ~ 28 0

Setting: for GSM900 cell, this parameter can be set to 19 ~ 31 (i.e. 5dBm)

by default. For GSM1800 cell, this parameter can be set to 15 ~ 28 (i.e.

0dBm) by default.

Default: 19

8) BS Min. TxPwr

Description: when BTS communicates with MS, its transmitting power is

controlled by the network. The network sets the power of BTS through

power command. BTS must take the transmitting power specified by the


Page 382 of 516

power command as the output power. When BSC is performing power

control, this parameter is the minimal transmitting power (i.e. lower limit of

power control) that can be used by BTS in the cell. The maximum power

level of BTS is Pn.


Table 6-151 The value range of “ BS Min. TxPwr”

Value BTS minimal power level

0 Pn

1 Pn –2dB …

…

15 Pn –30dB

Default: 15

5. GPRS Power Control

The parameters of GPRS Power Control are shown in Fig. 6-50.

Fig. 6-50 Parameters of GPRS Power Control

1) Uplink Power Control Strategy

Description: this parameter determines the uplink power control strategy of

the GPRS.


Page 383 of 516


Table 6-152 The value range of uplink power control strategy.

Value Uplink power control strategy

0 Non-control

1 Open loop control

2 Closed loop control

3 Quality-based control

Others Reserved.

Setting: 0

2) Downlink Power Control Strategy

Description: this parameter determines the downlink power control strategy

of the GPRS.


Table 6-153 The value range of downlink power control strategy.

Value Downlink power control strategy

0 Non-control

1 Open loop control

2 Closed loop control

3 Quality-based control

Others Reserved.

Setting: 0

3) Downlink Power Control Mode

Description: the downlink power control mode adopted at the BTS side. The

BTS has two power control modes: A and B. Mode A may be used for any

allocation mode, while mode B can only be used for the fixed allocation

mode. Which power control mode will be used is decided by the

“BTS_PWR_CTRL_MODE” parameter.


Table 6-154 The value range of the downlink power control mode


Page 384 of 516

Value MODE

0 A

1 B

Setting: 0

4) Value of Power Dec. based on BCCH on Mode A

Description: an optional downlink power control parameter, included in the

assignment message. If P0 exists, the power control is used; otherwise, the

power control is not used. During the packet transfer mode, P0 value shall

not change unless re-assignment or new assignment is established and the

assignment does not include the PDCH(s) of any previous assignment.


Table 6-155 The value range of “ Value of Power Dec. based on BCCH on Mode A”

Value Value represented by P0

0 P0=0dB

1 P0=2dB …

…

15 P0=30dB

Setting: 0

5) Precision

Description: this parameter determines the power control precision of the

GPRS.

Value range: 0 ~ 31

Setting: 0

6) Receive Power Strength from MS Needed

Description: this parameter is used for the uplink open-loop power control.


Table 6-156 The value range of “Receive Power Strength from MS Needed”

Value Meaning

0 -110 dBm


Page 385 of 516

1 -109 dBm

…

…

63 -47 dBm

Setting: 1

6.1.4.5 Configuring the handover control

In the main interface (shown in Fig. 6-2), select “Cell” and right click to pop up a menu of options. Select “Configure Handover Control” from the menu, as shown in Fig. 6-51.

1. Handover Pretreatment

The parameter configuration of “Handover Pretreatment” is shown in Fig.

6-51.

Fig. 6-51 Configuring handover pretreatment

1) Handover Control No.

Description: No. of the handover control object

2) Static state PRI of cell handover

Description: According to the specification, in the course of handover, the


Page 386 of 516

cell priority should be considered when sorting candidate cells. Therefore,

three factors decide sequencing of the candidate cells: priority, traffic, and

radio conditions. Among them, the priority and the traffic are the major

impact; in case the same results come out of these two factors, you can sort

on the basis of radio conditions.

Value range: 0 ~ 7, the larger of the value, the higher level of priority.

Default: 3

3) Sampling Count of Uplink Intensity

Description: in GSM system, BSC makes handover decision according to

the measurement data. To avoid the bad effect of burst measurement value

resulting from complicated radio transmission, BSC, when making handover

decision, no longer uses the original measurement data but uses a series of

average values of the measurement data, thus reducing the effect of burst

measurement value. Parameter HoUlLevWindow (Sampling Count of Uplink

Intensity) is the size of the window used to calculate the average value of

uplink signal intensity. This size is the number of samples used in

averaging.

Value range: 1 ~ 31

Default: 2

4) Reserve Count of Uplink Intensity






measurement value. Parameter “Reserve Count of Adjacent Cell” is the

number of uplink intensity averages transferred in handover required

message.

5) Power of Uplink Intensity

Description: according to GSM Specifications, discontinuous transmission (DTX) refers to the process that the system does not transmit signals in the speech pause period during the subscriber communication process. If DTX mode is used, the measurement data reported to BSC include two types.


Page 387 of 516

One is the average of the measurement results of all timeslots in a measurement period in non-DTX mode, and the other is the average of the measurement results of some special timeslots in a measurement period in DTX mode. BSC needs to select one type of measurement data according to the actual conditions and use the data to calculate the average value. The first type of measurement data is the average of the measurement results of all timeslots, so it is quite accurate. But the second type of measurement data is the average of the measurement results of some timeslots, so it is less accurate. Therefore, BSC, when averaging the measurement values, should use different weights for the two types of measurement data. Parameter HoUlLevWeight determines the weight for the first type (for all timeslots) of measurement data when averaging uplink signal intensity for handover. The weight for the second type (for some timeslots) of measurement data is 1 by default.

Value range: 1 ~ 3

Default: 2

6) Sampling Count of Downlink Intensity

Description: in GSM system, BSC makes handover decision according to the measurement data. To avoid the bad effect of burst measurement value resulting from complicated radio transmission, BSC, when making handover decision, no longer uses the original measurement data but uses a series of average values of the measurement data, thus reducing the effect of burst measurement value. “HoDlLevWindow” (averaging window of handover downlink intensity) parameter is the size of the window used to calculate the average value of downlink signal intensity. This size is the number of samples used in averaging.

Value range: 1 ~ 31

Default: 2

7) Reserve Count of Downlink Intensity

Description: in GSM system, BSC makes handover decision according to the measurement data. To avoid the bad effect of burst measurement value resulting from complicated radio transmission, BSC, when making handover decision, no longer uses the original measurement data but uses a series of average values of the measurement data, thus reducing the effect of burst measurement value. Parameter “Reserve Count of Adjacent Cell” is the number of downlink intensity averages transferred in the “handover


Page 388 of 516

required” message.

8) Power of Downlink Intensity

Description: according to GSM Specifications, discontinuous transmission (DTX) refers to the process that the system does not transmit signals in the speech pause period during the subscriber communication process. If DTX mode is used, the measurement data reported to BSC include two types. One is the average of the measurement results of all timeslots in a measurement period in non-DTX mode, and the other is the average of the measurement results of some special timeslots in a measurement period in DTX mode. BSC needs to select one type of measurement data according to the actual conditions and use the data to calculate the average value. The first type of measurement data is the average of the measurement results of all timeslots, so it is quite accurate. But the second type of measurement data is the average of the measurement results of some timeslots, so it is less accurate. Therefore, BSC, when averaging the measurement values, should use different weights for the two types of measurement data. Parameter HoDlLevWeight determines the weight for the first type (for all timeslots) of measurement data when averaging downlink signal intensity for handover. The weight for the second type (for some timeslots) of measurement data is 1 by default.

Value range: 1 ~ 3

Default: 2

9) Sampling Count of Uplink Quality

Description: in GSM system, BSC makes handover decision according to the measurement data. To avoid the bad effect of burst measurement value resulting from complicated radio transmission, BSC, when making handover decision, no longer uses the original measurement data but uses a series of average values of the measurement data, thus reducing the effect of burst measurement value. The “HoUlQualWindow” (handover uplink quality average window) Parameter is the size of the window used to calculate the average value of uplink signal quality. This size is the number of samples used in averaging.

Value range: 1 ~ 31

Default: 2

10) Reserve Count of Uplink Quality


Page 389 of 516

Description: in GSM system, BSC makes handover decision according to the measurement data. To avoid the bad effect of burst measurement value resulting from complicated radio transmission, BSC, when making handover decision, no longer uses the original measurement data but uses a series of average values of the measurement data, thus reducing the effect of burst measurement value. Parameter “Reserve Count of Adjacent Cell” is the number of uplink quality averages transferred in “handover required” message.

11) Power of Uplink Quality

Description: according to GSM Specifications, discontinuous transmission (DTX) refers to the process that the system does not transmit signals in the speech pause period during the subscriber communication process. If DTX mode is used, the measurement data reported to BSC include two types. One is the average of the measurement results of all timeslots in a measurement period in non-DTX mode, and the other is the average of the measurement results of some special timeslots in a measurement period in DTX mode. BSC needs to select one type of measurement data according to the actual conditions and use the data to calculate the average value. The first type of measurement data is the average of the measurement results of all timeslots, so it is quite accurate. But the second type of measurement data is the average of the measurement results of some timeslots, so it is less accurate. Therefore, BSC, when averaging the measurement values, should use different weights for the two types of measurement data. Parameter HoUlQualWeight determines the weight for the first type (for all timeslots) of measurement data when averaging uplink signal quality for handover. The weight for the second type (for some timeslots) of measurement data is 1 by default.

Value range: 1 ~ 3

Default: 2

12) Sampling Count of Downlink Quality

Description: in GSM system, BSC makes handover decision according to the measurement data. To avoid the bad effect of burst measurement value resulting from complicated radio transmission, BSC, when making handover decision, no longer uses the original measurement data but uses a series of average values of the measurement data, thus reducing the effect of burst measurement value. Parameter HoDlQualWindow (handover downlink


Page 390 of 516

quality average window) is the size of the window used to calculate the average value of downlink signal quality. This size is the number of samples used in averaging.

Value range: 1 ~ 32

Default: 2

13) Reserve Count of Downlink Quality

Description: in GSM system, BSC makes handover decision according to the measurement data. To avoid the bad effect of burst measurement value resulting from complicated radio transmission, BSC, when making handover decision, no longer uses the original measurement data but uses a series of average values of the measurement data, thus reducing the effect of burst measurement value. Parameter “Reserve Count of Adjacent Cell” is the number of downlink quality averages transferred in “handover required” message.

14) Power of Downlink Quality

Description: according to GSM Specifications, discontinuous transmission (DTX) refers to the process that the system does not transmit signals in the speech pause period during the subscriber communication process. If DTX mode is used, the measurement data reported to BSC include two types. One is the average of the measurement results of all timeslots in a measurement period in non-DTX mode, and the other is the average of the measurement results of some special timeslots in a measurement period in DTX mode. BSC needs to select one type of measurement data according to the actual conditions and use the data to calculate the average value. The first type of measurement data is the average of the measurement results of all timeslots, so it is quite accurate. But the second type of measurement data is the average of the measurement results of some timeslots, so it is less accurate. Therefore, BSC, when averaging the measurement values, should use different weights for the two types of measurement data. Parameter HoDlQualWeight determines the weight for the first type (for all timeslots) of measurement data when averaging downlink signal quality for handover. The weight for the second type (for some timeslots) of measurement data is 1 by default.

Value range: 1 ~ 3

Default: 2


Page 391 of 516

15) Sampling Count of Adjacent Cell






measurement value. Parameter NCellWindow (adjacent cell average

window) is the size of the window used to calculate the average value of

adjacent cell signal intensity. This size is the number of samples used in

averaging.

Value range: 1 ~ 31

Default: 2

16) Reserve Count of Adjacent Cell






measurement value. Parameter “Reserve Count of Adjacent Cell” is the

number of adjacent cell intensity averages transferred in “handover

required” message.

17) Power of Adjacent Cell

Description: according to GSM Specifications, discontinuous transmission













Page 392 of 516



measurement data. Parameter “Power of Adjacent Cell” determines the

weight for the first type (for all timeslots) of measurement data when

averaging adjacent cell signal intensity. The weight for the second type (for

some timeslots) of measurement data is 1 by default.

18) Sampling Count of Distance






measurement value. Parameter DistanceWindow (Sampling Count of

Distance) is the size of the window used to calculate the average value of

the distance from MS to BTS (actually the timing ahead TA). This size is the


Value range: 1 ~ 31

Default: 2

19) Reserve Count of Distance






measurement value. Parameter “Reserve Count of Distance” is the number

of distance averages transferred in “handover required” message.

20) Allow Zero

Description: according to GSM Specifications, MS can only report the

measurement data of six adjacent cells with the strongest signal strength,

so the measurement results of adjacent cells recorded by BSC may be

discontinuous, and the measurement data of the missing cell shall thus be

recorded as 0 (i.e. smaller than -110dBm). To avoid the bad effect of 0 on

averaging, we suppose occasional 0’s are allowed and are not used in

averaging, but excessive 0’s indicate that the signals of this adjacent cell


Page 393 of 516

are not good. Parameter Zero Allowed is used to determine how many 0’s

are normal, i.e. can be ignored, in averaging. To be specific, during

averaging, if the number of 0’s in the sampling count goes beyond Zero.

Allowed, these sampling values are hardly credible and the measurement

average = sum of the reported values / NCellWindow. If the number of 0’s in

the reported values does not go beyond ZeroAllowed, the sampling values

are much credible and the measurement average = sum of the reported

values / (NCellWindow – the number of 0’s).

Value range: 0 ~ 31

Default: 1

2. Handover Level

The parameters of Handover Level are shown in Fig. 6-52.

Fig. 6-52 Configuring handover level

1) Level, N value and P value of Uplink RxLev

Description: according to GSM Specifications, after a series of average

values are obtained, handover decision can be performed. The uplink

RxLev is one of the causes for the handover. The decision process is like

this: if P out of N recent uplink signal intensity averages are smaller than the


Page 394 of 516

related threshold, handover shall be performed, because the uplink signal

level is too low. Parameter HoUlLevThs defines the related threshold,

parameter HoUlLevN defines the related N value, and parameter HoUlLevP


Value range: 1≤HoUlLevP≤HoUlLevN≤31; level values are shown in Table

6-157.


Page 395 of 516

Table 6-157 The value range of “Uplink RxLev Level”


0 < -110

1 -110 ~ -109 …

…

62 -49 ~ -48

63 > -48

Setting: usually the value of HoUlLevThs should be smaller than the

threshold (PcUlInclLevThs parameter in R_POC table) for uplink power

control (increase), i.e. power control is preferred. If power control does not

work, then handover is necessary.


2) Level, N value and P value of Downlink RxLev


values are obtained, handover decision can be performed. The downlink

RxLev is one of the causes for the handover. The decision process is like

this: if P out of N recent downlink signal intensity averages are smaller than

the related threshold, handover shall be performed, because the downlink

signal level is too low. Parameter HoDlLevThs defines the related threshold,

parameter HoDlLevN defines the related N value, and parameter HoDlLevP


range: 1≤HoDlLevP≤HoDlLevN≤31; level values are shown in Table 6-158.

Table 6-158 The value range of “Downlink RxLev Level”


0 < -110

1 -110 ~ -109

2 -109 ~ -108 …

…

61 -50 ~ -49

62 -49 ~ -48

63 > -48

Setting: usually the value of HoDlLevThs should be smaller than the


Page 396 of 516

threshold (PcDlInclLevThs parameter in R_POC table) for downlink power


work, then handover is necessary. This parameter can be set to 15 (i.e.

-96dBm ~ -95dBm) by default. Note that it is 3dB greater than the value of

RxLevAccessMin of the cell.


3) Level, N value and P value of Uplink RxQual



RxQual is one of the causes for the handover. The decision process is like

this: if P out of N recent uplink signal quality averages are larger than the

related threshold, handover shall be performed, because the uplink signal

quality is too poor. Parameter HoUlQualThs defines the related threshold,

parameter HoUlQualN defines the related N value, and parameter

HoUlQualP defines the related P value.

Value range: 1≤HoUlQualP≤HoUlQualN≤31; level values are shown in Table

6-159.

Table 6-159 The value range of “Uplink RxQual Level”

Value Corresponding quality level

Meaning

0 0 BER<0.2%

1 1 0.2%<BER<0.4%

2 2 0.4%<BER<0.8% …

…

…

6 6 6.4%<BER<12.8%

7 7 12.8%<BER

Setting: usually the value of HoUlQualThs should be greater than the

threshold (PcUlInclQualThs parameter in R_POC table) for uplink power




4) Level, N value and P value of Downlink RxQual


Page 397 of 516



RxQual is one of the causes for the handover. The decision process is like

this: if P out of N recent downlink signal quality averages are larger than the

related threshold, handover shall be performed, because the downlink

signal quality is too poor. Parameter HoDlQualThs defines the related

threshold, parameter HoDlQualN defines the related N value, and

parameter HoDlQualP defines the related P value.

Value range: 1≤HoDlQualP≤HoDlQualN≤31; level values are shown in Table

6-160.

Table 6-160 The value range of “Downlink RxQual Level”

Value Corresponding quality level

Meaning

0 0 BER<0.2%

1 1 0.2%<BER<0.4%

2 2 0.4%<BER<0.8% …

…

…

6 6 6.4%<BER<12.8%

7 7 12.8%<BER

Setting: usually the value of HoDlQualThs should be greater than the

threshold (PcDlInclQualThs parameter in R_POC table) for downlink power




5) Level, N value and P value of Uplink RxLev of Internal Handover



(co-frequency) interference is one of the causes for handover. The decision

process is like this: if the uplink quality condition for handover is met and P

out of N recent uplink signal intensity averages are larger than the related

threshold, handover shall be performed, because the uplink (co-frequency)

interference is too serious. Parameter IntraHoUlLevThs defines the related

threshold, parameter IntraHoUlLevN defines the related N value, and


Page 398 of 516

parameter IntraHoUlLevP defines the related P value. If this handover

condition is met, there will be an cell internal handover.

Value range: 1≤IntraHoUlLevP≤IntraHoUlLevN≤31; level values are shown

in Table 6-161.

Table 6-161 Levels of “Uplink RxLev of Internal Handover”


0 < -110

1 -110 ~ -109

2 -109 ~ -108 …

…

61 -50 ~ -49

62 -49 ~ -48

63 > -48

Setting: usually the value of IntraHoUlLevThs should be greater than the

threshold (PcUlRedLevThs parameter in R_POC table) for uplink power

control (decrease).


6) Level, N value and P value of Downlink RxLev of Internal Handover



co-frequency interference is one of the causes for handover. The decision

process is like this: if the downlink quality condition for handover is met and

P out of N recent downlink signal intensity averages are larger than the

related threshold, handover shall be performed, because the downlink

co-frequency interference is too serious. Parameter IntraHoDlLevThs

defines the related threshold, parameter IntraHoDlLevN defines the related

N value, and parameter IntraHoDlLevP defines the related P value. If this

handover condition is met, there will be an cell internal handover.

Value range: 1≤IntraHoDlLevP≤IntraHoDlLevN≤31; threshold values are

shown in Table 6-162.


Page 399 of 516

Table 6-162 Value range of “Level of Downlink RxLev of Internal Handover”


0 < -110

1 -110 ~ -109

2 -109 ~ -108 …

…

61 -50 ~ -49

62 -49 ~ -48

63 > -48

Setting: usually the value of IntraHoDlLevThs should be smaller than (or

equal to) the threshold (PcDlRedLevThs parameter in R_POC table) for

downlink power control (decrease).


7) Level, N value and P value of C/I Allow to Access Special TRX

Description: If the system adopts concentricity technology, after a series of

averages are obtained, handover decision can be made. Good C/I of the

current special layer frequency is one of the causes for concentric handover.

The decision process is like this: when the current call is at the common

TRX (frequency), if P out of N recent C/I values are larger than the relevant

threshold, a handover from the common TRX to the special TRX shall be

performed for Good C/I Parameter GoodCiThs defines the related threshold,

parameter GoodCiN defines the related N value, and parameter GoodCiP


Value range: 1≤GoodCiP≤GoodCiN≤31; level values are shown in Table

6-163.

Table 6-163 Value range of “Level of C/I Allow to Access Special TRX”

Value Corresponding C/I value

0 -127Db

1 -126dB …

…

255 128dB


Page 400 of 516


8) Level, N value and P value of C/I When Allow Handover From Special TRX

Description: If the system adopts concentricity technology, after a series of

averages are obtained, handover decision can be made. Bad C/I of the

current special layer frequency is one of the causes for concentric handover.

The decision process is like this: when the current call is at the special TRX

(frequency), if P out of N recent C/I values are smaller than the relevant

threshold, a handover from the special TRX to the common TRX shall be

performed for Bad C/I Parameter BadCiThs defines the related threshold,

parameter BadCiN defines the related N value, and parameter BadCiP


Value range: 1≤BadCiP≤BadCiN≤31; level values are shown in Table 6-164.

Table 6-164 Value range of “Level of C/I When Allow Handover From Special TRX”

Value Corresponding C/I value

0 -127dB

1 -126dB

2 -125dB …

…

255 128dB


9 Level and N value of Rapid Handover

Description: some parameters are needed in rapid attenuation handover.

RapidHoThs is a signal intensity threshold. If the measured signal intensity

of a call is lower than this threshold continuously, then the condition for rapid

attenuation handover is satisfied. Candidate cell is a special associated cell

in the adjacent cell. RapidHoN is a counter value, i.e. the minimal times

when the measured value of the signal intensity of the call is continually

lower than the threshold.

Value range: The value range of RapidHoThs is shown in Table 6-165, and

the level ranges 1 ~ 31.


Page 401 of 516

Table 6-165 The value range of “Rapid Handover Level”


0 < -110

1 -110 ~ -109 …

…

62 -49 ~ -48

63 > -48

Setting: parameter RapidHoThs may be set to 15 (i.e. -96dBm ~ -95dBm)

by default like the level threshold of ordinary handover. Parameter

RapidHoN should be set in such a way as to ensure that rapid handover is

faster than the ordinary signal level handover.

Default: 10, N=1

10) Level of Macro-Micro Handover

Description: some parameters are needed during macro-micro handover.

The macro-micro handover level is a signal intensity threshold. When the

measured value of the signal intensity of an adjacent micro cell is

continuously larger than the MacroMicroHoThs value (threshold) for a

number of times, the call can be handed over to this adjacent micro cell.

That may enable a slowly moving MS to enter the micro cell. The times are

determined by MacroMicroHoN of each adjacent cell


Table 6-166 The value range of “Macro-Micro Handover Level”


0 < -110

1 -110 ~ -109 …

…

61 -50 ~ -49

62 -49 ~ -48

63 > -48

Default: 20

11) N value of Macro-Micro Handover


Page 402 of 516

Description: some parameters are needed during macro-micro handover.

There is a signal intensity threshold and a counter value.N value of

macro-micro handover (MacroMicroHoN) is a counter value that is related to

a given adjacent micro cell. When the measured value of the signal intensity

of this adjacent micro cell is continuously larger than the MacroMicroHoThs

value for MacroMicroHoN times, the call can be handed over to this

adjacent micro cell. That may enable a slowly moving MS to enter the micro

cell layer. This parameter describes the counter value that the local cell, as

a micro cell, should use.


Setting: The setting of the parameter MacroMicroHoN in the local micro cell

is related to the local cell size and the standard used in measuring MS

moving speed.

Default: 2

12) P value and N value of Distance Handover


values are obtained, handover decision can be performed. The distance

from the MS to the BTS is also one of the causes for the handover. The

decision process is like this: if P out of N recent time advance (distance)

averages are larger than the related threshold, handover shall be performed,

because the MS goes beyond the service coverage of the cell.Parameter

DistanceN defines the relevant N value, and parameter DistanceP defines

the relevant P value.

Value range: 1≤DistanceP≤DistanceN≤32; refer to Table 6-167.

Table 6-167 The value range of “Distance Handover Level”

DistanceThs Corresponding timing advance

Corresponding distance from MS to BTS

(approx.)

0 0 550m

1 1 1,100m

2 2 1,650m …

…

…

63 63 34,650m


Page 403 of 516

Default: P=3, N=4

3. Handover Condition

The parameters of Handover Condition are shown in Fig. 6-53.

Fig. 6-53 Configuring handover condition

1) Time Advance (DistanceThs)

Description: according to GSM Specifications, after a series of average values are obtained, handover decision can be performed. The distance from the MS to the BTS is also one of the causes for the handover. The decision process is like this: if P out of N recent time advance (distance) averages are larger than the related threshold, handover shall be performed, because the MS goes beyond the service coverage of the cell.Parameter DistanceThs defines the relevant threshold. DistanceThs is also used as max. TA to allow MS access.


Table 6-168 The value range of “Time Advance”

Value Corresponding time advance

Corresponding distance from MS to BTS (approx.)

0 0 550m

1 1 1,100m …

…

…

62 62 34,100m


Page 404 of 516

63 63 34,650m

Setting: the threshold parameter may be set to 63 by default.

2) Minimal Interval

Description: to prevent an MS just handed over to a cell from being handed

over to another cell immediately (this case often happens on the border of

two cells), the system may restrict frequent inter-cell handover via

parameter HoMinInterval so as to avoid effect on the user’s communication

quality and system performance. This parameter defines a time length. The

next handover is allowed only if the time from the last handover of MS is

longer than that time length. Note that this parameter is only valid for

inter-cell handover, but invalid for ordinary intra-cell handover or intra-cell

concentric handover. In addition, a micro cell has its own handover policies,

so this parameter is only valid for macro cell layer or its upper layers.


Table 6-169 The value range of “Minimal Interval”


0 0s

1 1s …

…

31 31s

Setting: this parameter can be set as 5 by default for a macro cell, but can

only be set as 0 for a micro cell.

Default: 5

3) Hierarchy Priority Choose Parameter: for the level/quality handover.

Description: if level/quality handover (signal level and signal quality)

condition is satisfied, there are three options in selecting and sequencing

the candidate cells for calls:

A. First hand over to adjacent cells on the upper layer of the local cell, then to

those on the same layer, and finally to other adjacent cells;

B. First hand over to adjacent cells on the same layer of the local cell, then to

those on the upper layer, and finally to other adjacent cells;


Page 405 of 516

C. All adjacent cells are treated alike.

This parameter determines which of the above options is selected. During

related level/quality handover control performed by the service process, this

parameter has a priority higher than that of the adjacent cell. Value range: 1

(UPPER_LAYER): priority is given to adjacent cells on the upper layer, then

to those on the same layer, and finally to other adjacent cells; 2

(SAME_LAYER): priority is given to adjacent cells on the same layer, then to

those on the upper layer, and finally to other adjacent cells; 3 (ALL_LAYER):

all adjacent cells are treated alike.

Setting: for a micro cell, this parameter is usually set to 1 (the first option),

that is, first hand over to the macro cell layer if any call in a micro cell needs

to be handed over because of signal quality or intensity. For a macro cell,

this parameter is usually set to 2 (the second option), that is, first hand over

to another macro cell if any call in a macro cell needs to be handed over

because of signal quality or intensity.

4) Hierarchy Can Use standard PBGT HO

Description: in multi-layer network and dual-band network applications,

standard PBGT handover needs some restrictions or controls. Parameter

PbgtHoLayer is used to control the applications of PBGT handover.


Table 6-170 The value range of “Hierarchy Can Use standard PBGT HO”

Value Meaning

0 0: Disallow PBGT handover to any adjacent cell on the same layer with different frequencies

1: Allow PBGT handover to a adjacent cell on the same layer with different frequencies

1 0: Disallow PBGT handover to the adjacent cell without hierarchy

1: allow PBGT handover to the adjacent cell without hierarchy

2 0: Disallow PBGT handover to any adjacent cell on the upper layer

1: Allow PBGT handover to a adjacent cell on the upper layer

3 0: Disallow PBGT handover to any adjacent cell on the lower layer

1: Allow PBGT handover to a adjacent cell on the lower layer


Page 406 of 516

Default: 0

5) Minimal PBGT Threshold


values are obtained, handover decision can be performed. The PBGT value

of an adjacent cell is also one of the causes for handover. The decision

process is like this: if the PBGT value of an adjacent cell is larger than the

relevant threshold of this cell, handover shall be performed to find a better

cell. The parameter HoMarginPbgt is the threshold that must be used during

the handover decision when an adjacent cell wants to hand over to this cell

via PBGT.


Table 6-171 The value range of “Minimal PBGT Threshold”


0

1 …

…

47

48

Default: 30

6) Micro Level of Quality Handover


values are obtained, handover decision can be performed. In handover

because of quality, adjacent cells should be screened and sequenced. The

parameter HoMarginRxQual is the threshold that must be used during the

handover decision when an adjacent cell wants to hand over to this cell via

signal quality.


Table 6-172 The value range of “Micro Level of Quality Handover”


0

1


Page 407 of 516

…

…

47

48

Default: 30

7) Minimal Threshold of RxLev HO


values are obtained, handover decision can be performed. In handover

because of level, adjacent cells should be screened and sequenced. The

parameter HoMarginRxLev is the threshold that must be used during the

handover decision when an adjacent cell wants to hand over to this cell via

signal level.


Table 6-173 The value range of “Minimal Threshold of RxLev HO”


0

1 …

…

48

Default: 30

8) Maximal TxPwr

Description: the maximum transmitting power that MS can use in adjacent

cells.

9) Level of Minimal RxLev

Description: the minimum receiving intensity level (on BCCH channel)

needed to allow MS to hand over to the cell. This is one of the parameters in

priority cell judgment in the handover control process. MS in the cell

constantly monitors the intensity on the BCCH channel of the adjacent cell.

However, only adjacent cells larger than RxLevMin can become candidate

cells for handover. Handover may occur if RxLevMin of MS required by the

adjacent cell is smaller than RxLevMin of MS required by this cell. This

indicates that MS is at the edge of the cell.


Page 408 of 516


Table 6-174 The value range of “Level of Minimal RxLev”


0 < -110

1 -110 ~ -109

2 -109 ~ -108 …

…

63 > -48

Default: 15

10) Handover Method (HoPatternInd)

Description: according to the Specifications, there are four handover modes:

A. Allow synchronization handover: the time advance of the destination cell is

the same as that of the source cell;

B. Allow asynchronization handover: the time advance of the destination cell

cannot be known.

C. Allow pseu-synchronization handover: the MS can figure out the time

advance of the destination cell.

D. Allow pre-synchronization handover: the BSC knows the time advance of

the destination cell.

This parameter determines what handover modes BSC can use.


Table 6-175 The value range of “Handover Method”

Position Meaning

Bit 1 1: Allow synchronous handover

0: Disallow synchronous handover

Bit 2 1: Allow asynchronization handover

0: Disallow asynchronization handover


Page 409 of 516

Bit 3 1: Allow pseu-synchronization handover

0: Disallow pseu-synchronization handover

Bit 4 1: Allow pre-synchronization handover

0: Disallow pre-synchronization handover

Bit 5 ~ 8 Reserved, always 0

Setting: 1 and 2 may usually be set to False. If partial handover speeds are

to be accelerated, 3 may also be set to False. At present 4 is always set to

True.

Default: allow synchronization handover: True; allow asynchronization

handover: True; allow pseu-synchronization handover: False; allow

pre-synchronization handover: False.

4. Handover Control

The parameters of Handover Control are shown in Fig. 6-54.

Fig. 6-54 Configuring handover control parameters

Description: multiple handover trigger conditions are defined in the

Specifications, and the introduction of micro cells also brings many

handover algorithms. Except for some basic types of handover based on

receiving intensity and receiving quality, some other optional types of


Page 410 of 516

handover are not always adopted in the cell. Parameter HoControl

determines whether to implement other types of handover in the cell.

Value range: HoControl is a 16-bit bitmap, as shown in Table 6-176.


Page 411 of 516

Table 6-176 The value range of HoControl

Position Meaning

1 1: Allow SDCCH handover 0: Disallow SDCCH handover

2 1: Allow intra-cell handover due to uplink interference 0: Disallow intra-cell handover due to uplink interference

3 1: Allow intra-cell handover due to downlink interference 0: Disallow intra-cell handover due to downlink interference

4 1: Allow handover due to distance 0: Disallow handover due to distance

5 1: Allow standard PBGT handover 0: Disallow standard PBGT handover

6 1: Allow automatic handover base on traffic 0: Disallow automatic handover base on traffic

7 1: Allow handover based on direction 0: Disallow handover based on direction

8 1: Allow concentric handover 0: Disallow concentric handover

9 1: Allow intra-cell handover due to downlink interference between super TRX channels 0: Disallow intra-cell handover due to downlink interference between super TRX channels

10 1: Allow intra-cell handover due to uplink interference between super TRX channels 0: Disallow intra-cell handover due to uplink interference between super TRX channels

11 1: Allow PBGT handover between adjacent cells in TRX channel 0: Disallow PBGT handover between adjacent cells in TRX channel

12 1: Allow dynamic adjustment of handover priority 0: Disallow dynamic adjustment of handover priority

13 1: Allow rapid handover 0: Disallow rapid handover

14 1: Allow macro-micro delay handover 0: Disallow macro-micro delay handover

15 1: Allow micro-micro delay handover 0: Disallow micro-micro delay handover


Setting: positions 1 and 4 may usually be set to True, 2 and 3 to False, 5 to

False, 6 to False when multi-layer or dual-band network is used, 7 to True, 8,

9 and 10 depending on specific conditions, usually to True. For a micro cell,


Page 412 of 516

position 15 shall be set to False and 14 to True. For a macro cell, position

14 shall be set to False and 15 to True. 12 and 3 are usually set to True and

11 to False.

5. Other

The other parameters are shown in Fig. 6-55.

Fig. 6-55 Configuring other parameters

1) Handover Failure Penalty Period

Description: a protection period for preventing immediate handover after

handover failure. Unit time is the period of survey or pretreatment survey

report.


Default: 7

2) Allowed Dynamic Priority Difference

Description: dynamic priority difference between the destination cell and the

local cell that can be tolerated during handover. In the algorithm of the cell

handover, check in turn the tolerable dynamic priority difference, tolerable

power budget difference, moving direction of MS, etc.


Page 413 of 516

Value range: 1 ~ 7

Default: 1

3) Allowed PBGT Difference

Description: Allowable power budget difference between the destination cell

and this cell during handover.

Value range: 1 ~ 20

Default: 3

4) Control Value of Handover on Traffic (hierarchy)

Description: the layered control value for traffic handover, i.e. which layer

should be preferred for handover

Value range: 0 ~ 3

Default: 1 (at the same layer)

5) Control Value of Handover on Traffic (frequency)

Description: the layered control value for traffic handover, i.e. which

frequency band should be preferred for handover.

Value range: 0 ~ 1

Default: 0

6) Threshold of Handover on Traffic

Description: the threshold at which the database gives an alarm on the

traffic of a cell.


Default: 70

7) Default Minimal RxLev.

Description: the default minimum receiving level threshold for handover to

the undefined adjacent cell.

Value range: 15

8) Default Maximal TxPwr.

Description: the default maximum transmitting power needed by MS in the

undefined adjacent cell.


Page 414 of 516

Value range: 15

9) Default Minimal PBGT Threshold

Description: the default minimum receiving intensity threshold needed to

hand over to the undefined adjacent cell.

Value range: 15

6.1.4.6 Configuring adjacent cell handover and reselection

In the main interface (shown in Fig. 6-2), select “Cell” and right click to pop up a menu of options. Select “Configure AdjCell handover and reselection”, as shown in Fig. 6-56.

Fig. 6-56 Configuring adjacent cell handover and reselection

1. Adjacent Cell Handover Object No. (hrid)

Description: the unique ID of the adjacent cell handover and reselection object.


2. Handover Priority

Description: according to the Specifications, during the handover, the cell priority should be considered when sequencing candidate cells. Therefore, three factors decide the sequencing of the candidate cells: priority, traffic, and radio conditions. Among them,


Page 415 of 516

the priority and the traffic are the major factors; in case the same results come out of these two factors, you can sequence them on the basis of radio conditions.

Value range: 0~ 7; the larger the value, the higher cell priority.

Default: 3.

3. Adjacent Cell Max TxPwr.

Description: during the communication between MS and BTS, the transmitting power of MS is controlled by the network. The network sets the power for MS via the power command and the command is transmitted on SACCH (the SACCH has 2 header bytes, one is the power control byte and the other is the timing advance byte). The MS must extract the power control header from the downlink SACCH and takes the specified transmitting power as the output power; if the power level of MS cannot output the power value, it will output the closest transmitting power that can be output. When the BSC controls the power, this parameter is the maximum transmitting power that can be adopted by MS in the cell. MsTxPwrMax is also a parameter for BSC to calculate the PBGT value.


Table 6-177 The value range of “ Adjacent Cell Max TxPwr.”

GSM900 GSM1800

Value Output power of the MS (dBm)

Value Output power of the MS (dBm)

0 ~ 2 39 29 36

3 37 30 34

4 35 31 32

5 33 0 30 …

…

…

…

17 9 13 4

18 7 14 2

19 ~ 31 5 15 ~ 28 0

Setting: this parameter is usually set as the same value as


Page 416 of 516

MsTxPwrMaxCch (the maximum power level of the control channel in a cell).

4. Min RxLev Needed

Description: the minimal receiving level that allows MS to access the cell. To prevent the MS from accessing the system in case of the low receiving signal level (usually, the communication quality cannot guarantee normal communication process after accessing) and from unreasonably wasting the radio source of the network, it is stipulated in the GSM system that the receiving level be larger than a threshold level when the MS needs to access the network, that is: Min RxLev Needed (the minimal receiving level that allows MS to access the cell). In addition, it is also one of the standards (a parameter to calculate C1 and C2) for MS to make the cell selection and reselection. This parameter will be broadcast to all the MSs in a cell via the “RIL3_RR SYSTEM INFORMATION TYPE3” and “TYPE4” messages. RxLevMin is also one of the cell selection parameters.


Table 6-178 The value range of “Min RxLev Needed”


0 < -110

1 -110 ~ -109

2 -109 ~ -108 …

…

62 -49 ~ -48

63 > -48

Setting: generally, the recommended value should be approximate to the MS receiving sensitivity. For some cells with overloaded traffic, the “RxLevAccessMin” of the cell may be relevantly increased, so as to decrease the C1 and C2 values of the cell and the cell effective coverage. However, the “RxLevAccessMin” value cannot be too large, otherwise “blind spot” will be created at the cell boundaries factitiously. When this measure is adopted to


Page 417 of 516

balance the traffic, it is recommended that the level value not exceed -90dB.At the network’s preliminary running stage, this parameter can be generally set as 10 (i.e., -101dBm~-100dBm) or below, which is higher than the MS’s receiving sensitivity -102dBm; However, when the network capacity is expanded or the radio coverage in a cell is not a problem, this parameter of the cell can be increased by 2 (dB).

Default: 15

5. Cell Layer Num

Description: with the introduction of multi-layer network technology and dual-frequency network technology, the multi-layer radio coverage will be formed in the same physical area, so the various corresponding handover strategies are introduced. The detailed description of handover policies is outside the scope of this document. However, in a word, limiting the PBGT handover defined in the Specifications to one layer can reduce the number of handovers during the call, thus improving the system reliability and communication quality. Policies of handover between a macro cell layer and a micro cell layer mainly depend on the moving speed of the MS: an MS with a higher moving speed will try its best to stay at the macro cell layer (upper layer of the micro cell layer), and an MS with a lower moving speed will try its best to enter the micro cell layer (lower layer of the macro cell layer). Only in the case of non-PBGT handover and emergency, will the undefined cell of the service cell be considered as a candidate cell.

Value range: this parameter may be regarded as an array, and each element determines the hierarchical relationship between the relevant adjacent cell and the local cell. The number of cells in the array is decided by the “NCellNum” parameter. The value range of each element is shown in Table 6-179.


Page 418 of 516

Table 6-179 The value range of cell layers

Value Meaning

0 N, undefined

1 SAME, the adjacent cell and the local cell are in the same layer (it can perform the PBGT handover)

2 UPPER, the adjacent cell is the upper layer of the local cell (when the local cell is a micro cell)

3 LOWER, the adjacent cell is the lower layer of the local cell (when the cell is a macro cell)

others Reserved.

Setting: the following standards can be referred to when you make the settings, as shown in Table 6-180:

Table 6-180 Settings of the number of cell layers

Adjacent cell

The local cell

Sector cell

GSM

900M

macro-cell

GSM

900M

micro-cell

GSM

1800M

macro-cell

GSM

1800M

micro-cell

micro-micro cell

Sector cell N N N N N N

GSM900M macro cell N SAME LOWER N LOWER LOWER

GSM900M micro cell N UPPER SAME UPPER N LOWER

GSM1800M macro cell

N N LOWER SAME LOWER LOWER

GSM1800M micro cell

N UPPER N UPPER SAME LOWER

Micro-micro-cell N UPPER N UPPER N N

6. Is Related Cell

Description: in the fast fading handover, the candidate destination cell can only be the related cell of the service cell. This is one parameter of the adjacent cell, which is used to indicate if the adjacent cell is the related cell of the service cell.

Value range: False: this adjacent cell is not the related cell of the


Page 419 of 516

service cell; True: this adjacent cell is the related cell of the service cell;

Default: False.

7. Synchronize to Adjacent Cell

Description: if it belongs to a central module.


8. Related Cell DN

Description: DN(BssId-SiteId-BtsId-Hold) of the handover cell or DN (BssId-EcId) of the external cell.


Page 420 of 516

6.1.4.7 Configuring the adjacent cell handover

In the main interface (shown in Fig. 6-2), select “Cell” and right click to pop up a menu of options. Select “Configure AdjCell handover”, as shown in Fig. 6-57.

Fig. 6-57 Configuring the adjacent cell handover

Please refer to section 6.1.4.6 “Configuring adjacent cell handover and reselection”.

6.1.4.8 Configuring the adjacent cell reselection

In the main interface (shown in Fig. 6-2), select “Cell” and right click to pop up

a menu of options. Select “Configure AdjCell reselection”, as shown in Fig.

6-58.

Fig. 6-58 Configuring the adjacent cell reselection


Page 421 of 516

Please refer to section 6.1.4.6 “Configuring adjacent cell handover and reselection”.


Page 422 of 516

6.1.4.9 Configuring the frequency hopping system

In the main interface (shown in Fig. 6-2), select “Cell” and right click to pop up a menu of options. Select “Configure PHS”, as shown in Fig. 6-59.

Fig. 6-59 Configuring the FHS

1. Frequency Hopping No.

Description: based on the FH algorithm defined by GSM Specifications 05.02, the MAI is a function of Frame Number (FN) of TDMA, Hopping Serial Number (HSN) and Mobile Allocation Index Offset (MAIO), of which, the HSN determines the operation track of the frequency in the course of FH. For the cells close to each other that adopt the same MA, different HSNs can ensure that there is no conflict of usage of frequency in the FH course. Different TSs can share a group of MAs and the relevant HSNs, and the only difference is that the MAIO is put in the TS attribute.

Value range: 0 ~ 63, of which HSN=0 is a special FH, i.e. the cyclic FH.

Setting: for the cells close to each other that adopt the same MA, different HSNs can ensure that there is no conflict of usage of frequency in the FH course.

Default: 0


Page 423 of 516

2. Frequency Hopping Mode

Description: the frequency modulation mode adopted for the cell.

Value range: 0: no frequency hopping; 1: baseband frequency hopping; 2: radio frequency hopping;

Default: 0

3. Frequency Group

Description: a list of the absolute RF channel numbers of each frequency in the frequency hopping group. It is a sub-set of the CA of the cell. When it notifies the MS which channel should be used, it will issue the related information to the MS.

Value range: no more than 64.

6.1.4.10 Configuring the channel

In the main interface (shown in Fig. 6-2), select “TRX” and right click to pop up a menu of options. Select “Create Channel”. According to the channel combination, there are two configuration options for the channel creator, as shown in Fig. 6-60, Fig. 6-61, and Fig. 6-62.

Fig. 6-60 Configuring a channel (traffic channel) - GSM


Page 424 of 516

Fig. 6-61 Configuring a channel (traffic channel)-GPRS

Fig. 6-62 Configuring a channel creator (control channel)

1. Channel No.

Description: the number to identify the channel.

2. TS radio Channel Combination

Description: this parameter is used to indicate the channel combination mode of the TS. It is a very important configuration information and is closely related to the CELL’s attribute “BcchArfcn” and “CcchConf”, and it can serve as one of the conditions to check if the configuration is correct.


Table 6-181 Settings of “TS radio Channel Combination”

Value Explanation

0 TCH/F + FACCH/F + SACCH/TF

1 TCH/H(0, 1) + FACCH/H(0, 1) + SACCH/TH (0, 1)

2 TCH/H (0, 0) + FACCH/H (0, 1) + SACCH/TH (0, 1) + TCH/H(1, 1)

3 SDCCH/8 (0..7) + SACCH/C8(0..7)

4 FCCH + SCH + BCCH + CCCH

5 FCCH + SCH + BCCH + CCCH + SDCCH/4(0..3) + SACCH/C4(0..3)

6 BCCH + CCCH

7 FCCH + SCH + BCCH + CCCH + SDCCH/4(0..3)+ SACCH/C4 (0..3)+ CBCH

8 SDCCH/8(0..7) + SACCH/C8 (0..7) + CBCH

9 TCH/F + FACCH/F + SACCH/M


Page 425 of 516

Value Explanation

10 TCH/F + SACCH/M

11 TCH/FD + SACCH/MD

12 PBCCH+PCCCH+PDTCH+PACCH+PTCCH

13 PCCCH+PDTCH+PACCH+PTCCH

14 PDTCH+PACCH+PTCCH

15 CTSBCH+CTSPCH+CTSARCH+CTSAGCH

16 CTSPCH+CTSARCH+CTSAGCH

17 CTSBCH

18 CTSBCH+TCH/F+FACCH/F+SACCH/CTS

19 E-TCH/F+E-FACCH/F+SACCH/TF

20 E-TCH/F+E-FACCH/F+SACCH/M

21 E-TCH/F+SACCH/M

22 E-TCH/FD+SACCH/MD

Setting: the default can be set as 0.

3. Train Serial Code

Description: it is the train serial code of the TS. There are 8 kinds of train serial codes, with little relation between them. It is used by the self-adaptive equalization circuit at the receiving end for reference in time delay compensation. For the TS where the BCCH channel is located, this parameter must be equal to the BCC of the cell.

Value range: 0 ~ 7

Setting: for the TS where the BCCH channel is located, this parameter must be equal to the BCC of the cell.

Default: 0

4. PCM Line No.

Description: serial number of the PCM circuit.

5. Time Slot No.

Description: it is the physical TS number of CHANNEL in TRX.

Value range: 0 ~ 7

6. Sub Time Slot No.


Page 426 of 516

Description: it is the sub-channel number of the logical channel (traffic channel) in the physical channel (TS).


Table 6-182 The value range of “Sub Time Slot No.”

Value Conditions

0 When the “TS radio Channel Combination” field is 0 (TS_COMB_TCHF)

0 ~ 1 When the “TS radio Channel Combination” field is 1 (TS_COMB_TCHH0) or 2 (TS_COMB_TCHH1)

0 ~ 3 When the “TS radio Channel Combination” field is 5 (TS_COMB_MBCCHC)

0 ~ 7 When the “TS radio Channel Combination” field is 3 (TS_COMB_SDCCH)

6.2 Software loading

The software loading mainly provides the upgrading and loading of card software in ZXG10-BSC, ZXG10-BTS (V1A and V2), ZXG10-OBTS and ZXG10-MB. It enables you to make software upgrading and loading without traveling to the site, thus facilitating the management of GSM equipment and offering the management function of software versions.

6.2.1 Overview

The software loading mainly offers such software version management functions as software storing, software version setting, software loading, software upgrading and so on. It is equipped with the ability of concurrently processing and can load multiple boards at the same time, thus to greatly save the loading time and quickly complete the loading tasks of various boards.

The functions of software loading are as follows:

1. The OMCR (V2) server software storing

It copies the software files to the specified directory on the OMCR (V2) server and the foreground MP, and makes the relevant


Page 427 of 516

records in the databases of the foreground and the background. The software storing is the foundation of all software loading operations (including the software version setting and software loading actions).

2. Transferring the software to MP

It transmits a stored software to the MP of the specified module of the specified BSC.

3. Software version setting

It involves creating and modifying the software version, which means creating or modifying the software version records of some specified object boards or some specified kinds of software. Such records are the foundation of the software loading action.

4. Software loading

It notifies the MP to load a software or a kind of software onto a specified object board or an object rack.

5. Viewing the foreground running version

It transmits the inquiry command to a foreground board, and the board returns its running version number to the OMCR (V2) server. The server forwards this version number to the client for display.

6. Software upgrading

Upgrading the board software at the control layer such as BSC_MP is done through class-1 software. If this operation is done, the MP of the specified module of the specified BSC will restart, and then the specified MP version will run. Note that the version file of this MP must exist in the hard disk of the MP of this MP (special regulations of BSC: the version file of the MP must be under the $OMCHOME/tmp/ftp/Version directory).

6.2.2 Software loading flow

Software loading flow is shown in Fig. 6-63.


Page 428 of 516

Software version

Software storing

Software version setting(create, modify )

Software loading

Software running

Fig. 6-63 The software loading flow

The software must be stored first, and then it can be loaded. . When storing the software, the relevant software should be connected to the BSC module to be configured, saved in the $OMCHOME/tmp/ftp/version” directory on the server, and copied to the MP of the relevant module MP of the BSC by being transmitted to the foreground. Besides, the relevant version information is written in the databases of the foreground and the background.

The software version setting involves creating and modifying the software version, which means creating or modifying the software version records of some specified object boards or some specified kind of software. The records are the foundation of the software loading action.

The version loading notifies the MP to load the software or a kind of software onto a specified object board or object rack. This is a CMIS action. For the control layer software, it means the software upgrade, and it is only necessary to copy the software to the MP and then update it.

To improve the speed of software loading, the files stored on MP will be used in priority during BSC board loading and BTS, MB equipment loading. Only when MP does not contain the required files, the files will be requested from the server. So, the stored software that has been sent to the foreground can save the loading time.

After version updating, if the new version cannot correctly start or has


Page 429 of 516

serious faults due to some reasons, the system might break down. Therefore, the old version should be saved before updating the version. When the above situation appears, use the old version to restore the system.

6.2.3 Version information

6.2.3.1 Software ID

The software ID is used to indicate the function of software, and is defined in “prefix+function” mode. There are two prefixes: BSC and BTS, indicating respectively whether the software belongs to BSC or BTS. The function field that follows indicates the usage of the software, and it is normally represented by the board name. See Table 6-183.

Table 6-183 List of software IDs and their usage

Software ID Function

BTS_BIE BS interface equipment unit

BTS_CHP Channel processor

BTS_CKU Clock panel

BTS_CMM Common management module

BTS_CUI Carrier frequency interface

BTS_EAM Environment alarm panel

BTS_DSP0 Micro cell: DSP0, belonging to the TRU panel.

BTS_DSP1 Micro cell: DSP1, belonging to the TRU panel.

BTS_FUC Frame unit controller

BTS_RCU Micro cell: radio frequency interface unit

BTS_SCU Micro cell: signaling control unit board

BTS_OMU Operation and maintenance unit software

BTS_CHP Channel processor software

BSC_EDRT Enhanced DRT

BSC_EFREN The DSP version on EDRT

BTS_FUC Frame unit controller software

BSC_MP Module processor software

BSC_SMB Sub-multiplexing board software

BSC_SMT1 Sub-multiplexing board 1 software

BSC_SMT2 Sub-multiplexing board 2 software


Page 430 of 516

Software ID Function

BSC_DRT Dual rate transcoder board software

BSC_DTI Digital trunk interface software

BSC_FR Full-rate voice-coded DSP algorithm

BSC_HR Half-rate voice-coded DSP algorithm

BSC_EFR Enhanced full-rate voice/data circuit

BSC_MTPEN Enhanced No.7 signaling board

BSC_IPCBEN The MPPP communication board on ECOM board

BSC_GPP General peripheral processor (GPP) board

BSC_BOSN Bit Oriented Switching Network

BSC_LAPDEN Enhanced LAPD signaling board

BSC_BRP BSSGP RLC/MAC protocol board

BSC_FRP Frame relay protocol board

BSC_BRPDSP The DSP version on BRP

BSC_GIPP Peripheral processor board of the Gb interface

BSC_PUC Access unit control board

6.2.3.2 Software version

The software version consists of four fields, each of which contains two digitals, such as “HH.VV.FF.XX”. Meanings of each field are as follows:

1. HH: a number related to the hardware platform, ranging 00 ~ 99. For a software, the HH value will remain unchanged unless the software is modified due to the modification of the hardware platform on which it is running.

2. VV: the version number independent of the hardware platform, ranging 00~99. The value of VV decides the main functions of the software. If there is structural adjustment in software, VV should be updated.

3. FF: the version number independent of the hardware platform, ranging 00~99. The value of FF decides the local functional features of the software. If they are added or modified, FF will be upgraded.

4. XX: the version number independent of the hardware platform, ranging 00~99. If the software itself remains unchanged both


Page 431 of 516

structurally and functionally, and only some errors and BUGs are corrected, XX should be upgraded. The defined meaning of XX is as follows: when XX=”00”, the meaning is “a”, when XX=”01”, the meaning is “b”…, when XX=”25”, the meaning is “z”, when XX=”26”, the meaning is “A”…, when XX=”51”, the meaning is “Z”, and when XX=”99”, the meaning is “Formal version”. Among them, the XX= “52”~“98” are not defined.

For example, the first software version number of ZXG10-BSC&BTS is defined as “01.00.00.00”, so you may input “01.00.00a” during software storing.

6.2.4 Operations of the software loading interface


For the new software version, first save the software. For the software to be loaded, it is recommended to perform the storing operation first, and then the software loading operation.

As for the BSC, the software loading of each board is carried out through the boards on the rack diagram; for the BS (including the micro-cell), you can either load the board software independently on the rack diagram, or load multiple board software at a time on a physical site. You can also create, set, and load versions of the same type in a batch operation.

Besides, all stored software versions can be seen by browsing the versions; through software setting, the BSC software, BTS software and DSP software can be set as the existing software version that is the basis for loading.

6.2.4.2 Entry into the software loading interface

After a user succeeds in logon, he (she) can select the “Configuration Management → Software Loading” on the main interface (as shown in Fig. 2-10) to enter the software loading main interface (as shown in Fig. 6-64).


Page 432 of 516

Fig. 6-64 Software loading main interface


1. Setting: Select All, Click to Inquire, and Exit.

2. Operation: this is a dynamic menu, and the menus vary with the contents clicked by the mouse, including Store Software, Delete the Stored Software, Create Version, Modify Version, Inquire Version, Delete Version, Load Version, etc..

3. View: Logical View, Physical View, Toolbar, Status Bar, Command Box, Expand, Collapse, Expand All, Collapse All, and Refresh.

4. Help: Software Loading Help, Directory and Index, About …

From left to right, the tool buttons on the toolbar in turn are: Switch View, Expand, Collapse, Expand All, Collapse All, Refresh, Help, and Exit. All the buttons on the toolbar have the corresponding options in the menu.

The left side of the main window is the browse tree. After the tree is Expanded, it can present all the BSCs and their racks under the BSS and the managed BTS if it is the physical view. If it is the logical view, it will present the stored software version, Class-1 software version and the software package. To switch the view, use the “Switch View” button.

The lower part of the interface is the command box, i.e. the character input


Page 433 of 516

interface. The user can directly input the MML command in the command box to complete an operation. During the interface operation, the relevant MML command will be displayed in the command box. It is necessary to point out that, except the multiplexing command, only the command related to the software loading can be input in the software loading application window.

6.2.4.3 Version management

The software version management involves storing the software, browsing the version, transmitting it to the foreground and setting the software, etc..

1. Storing software

Prior to the software loading, the software must be stored first. During the storing operation, the software will be copied to the OMCR (V2) server and the corresponding directory on MP of the relevant module of the BSC, and the relevant record will be added in the database for loading in the future. The software storing is performed in the logical view as illustrated in Fig. 6-65.Click “Operation→Store Software” to pop up the “Store Software” interface, as shown in Fig. 6-66 (in the GSM environment) and Fig. 6-67 (in the GPRS environment).

Fig. 6-65 The logical view


Page 434 of 516

Fig. 6-66 Store Software - GSM

Fig. 6-67 Store Software - GPRS

The software of boards of the same type is generally put in the same path.

The auto search function can be used to add respectively the versions and

paths to the version number boxes and path boxes of the relevant boards.

Select an appropriate path in the root directory, and click “Auto Search”

button in the interface. The system will search based on the root directory,


Page 435 of 516

and automatically match the found software version to the relevant board,

as shown in Fig. 6-68 (in the GSM environment) and Fig. 6-69 (in the GPRS

environment).

Fig. 6-68 Auto search - GSM

Fig. 6-69 Auto search - GPRS


Page 436 of 516

After the auto-search, the system will match the first appropriate software version it finds to the relevant board. However, there may be multiple appropriate software versions under the root directory. Therefore, you can modify the software singly and manually in the lower window, i.e. press the “Browse” key and select the actual path to find out the software version that really needs to be stored.

Certainly, you can select the software, arrange the version number and path directly and manually in the lower window without auto-search.

In the case of the BTS, the MB also needs to select the module to be configured, so as to determine the applicable scope of the software. The module number of the BSC software need not be selected since it is specified as 1.

Finally, click the “Store Software” key to store it. There is a prompt on whether the software storing is successful or failed.

When the storing is finished, press the “Exit” key to return to the software loading interface.

2. Browsing the software version

The version browse function can be used to check the stored software and their versions. By clicking the version node to view, you can view its relevant software version information. View the software version information of BSC_GPP, as illustrated in Fig. 6-70. The software ID, software version, file size and file name of every stored software are listed in the window.


Page 437 of 516

Fig. 6-70 Browsing the software

3. Sending software to the foreground

Because the files stored on MP are used in priority to load software, the software can be first stored on the MP hard disk of BSC to save the time for software loading before loading the BS equipment; and the “Sending software to the foreground” operation can be used for this purpose.

With the function of sending software to the foreground, the software to be loaded can be sent to the MP hard disk of the foreground in order to get ready for loading the software.

The sending-software-to-the-foreground” operation is not necessary because all the software versions are sent via FTP to the OMCR (V2) server and the relevant directory of the corresponding MP module of the BSC while storing the software. Moreover, if there are no required files on the MP (i.e. the required files are not transmitted to the foreground) while loading, the system will automatically copy the files from the server to the MP. So, due to the process of copying files from the server to the MP, the software loading time will be relatively longer. Select the


Page 438 of 516

software version to be transmitted in the “Browse Version” interface shown in Fig. 6-70, right click to pup up the “Send to Foreground” menu, and the operation can be completed.

6.2.4.4 Class 1 software loading

Class 1 software version refers to the operations to create, set and load versions with the same type in a batch of operations, which are performed in the logical view. By clicking the browse tree on the logical view interface of the software loading, you can browse all the current version information of Class 1 software as illustrated in Fig. 6-71.

Fig. 6-71 Class 1 software version

In Fig. 6-71, right click “Class 1 Software” to pop up a menu. Select “Create Version” from this menu to pop up the interface for creating Class-1 software, as shown in Fig. 6-72. First create the relevant software version when Class 1 software is loaded. After the version is created, you can modify, delete and load the software version. The relevant software version for storing must be available before creating Class 1 software version The interface for modifying, deleting or loading Class 1 software is similar to that for creating Class 1 software. For example, Class 1 software


Page 439 of 516

version is created as follows:

1. Select the big type;

2. Select the board type;

3. Select the software version that will be set on the selected module in BSC.

4. In the case of the BTS software, select the module number and site type also.

5. Press the “Create” key. Then the software version information to be created will be created as the selected available software version information.

If the create operation is successful, the system will send a broadcast message,

notifying all workstations in the system that this software version is successfully

created; if the create operation fails, the system will give a prompt of failure in

the interface.

Press the “Exit” key to go back to the Class 1 software interface as illustrated in Fig. 6-71.

Fig. 6-72 Class 1 software loading version

6.2.4.5 Rack software loading

The software loading of each board on BSC is processed directly on the


Page 440 of 516

rack diagram, including setting and loading the software version. Setting software version is, on the basis of the stored software version, to create or modify the software version records of a specified destination board or a specified kind of software. Such records are the foundation of the software loading action. Loading software version indicates the action that MP is notified to load certain software or a kind of software to a specified destination board or a destination rack. Only after the software version of the specified board is created, can the operations of inquiring, modifying and deleting the software version and loading software for the board be performed.

The system provides in real time the rack diagram of the BSC, displaying different racks in different ways.

For the BSC (V2), the boards for which the software loading or upgrading can be conducted are as follows:

1. MP: software upgrading

2. DRT: software loading/DSP software loading

3. BOSN, AIPP, TIC, TCPP: software loading

In the browse tree on the software loading physical view interface, select the rack that needs to load the software under the BSC, and the interface display is as illustrated in Fig. 6-73.


Page 441 of 516

Fig. 6-73 BSC loading - the rack diagram display

We take the BOSN board and DRT board as an example to introduce the software loading carried out directly on the board in the rack diagram.

1. BOSN software loading

Right click the BOSN board to pop up the shortcut menu of the BOSN board in the interface: Create Version, and Inquire the Current Running Version. If the software version of the relevant board has been created, the menu will be: Modify Version, Inquire Version, Delete Version, Load Version, and Inquire the Running Version. Right click to pop up the “Create Version” menu, whose interface is shown in Fig. 6-74.


Page 442 of 516

Fig. 6-74 Creating the BOSN board software

The board information of the selected board in the rack diagram (here is the selected BOSN board) is presented at the upper part of Fig. 6-74, including the “BSC No.”, “Module No.”, “Munit No.”, “Unit No.”, “Port No.”, “Board Type”, ”Rack No.”, “Shelf No.” and “Slot No.”, etc. The currently configured software version of the board is presented in the “Current Software Version” box.

Select the version to be updated to from the “Update To” in the lower “Update Software Version” box, and press the “Create” key. The new software version can thus be created. If the create operation is successful, the system will send a broadcast message, notifying all workstations in the system that this software version is successfully created; if the create operation fails, the system will give a prompt of failure in the interface.

Press the “Exit” key to go back to the rack diagram interface as illustrated in Fig. 6-73.

After create operation is successful, the interface for modifying, deleting, and loading the software is similar to that shown in Fig.


Page 443 of 516

6-74, except for the command buttons in the interface. For loading, click “Load” button to complete the board software loading.

The software loading operations of DRT, AIPP, TIC and TCPP are as the same as the BOSN software loading.

2. DSP software loading

Right click the DRT board to pop up the shortcut menu of the DRT board in the interface: Create Version, Inquire the Current Running Version, Create DSP Version, and Inquire the Current Running Version of DSP. If the software version of the relevant board or the DSP software version has been created, the menu will be: Modify Version, Inquire Version, Delete Version, Load Version, and Inquire the Current Running Version. Right click to pop up the menu, and the processing interface of the DSP software loading will appear, as shown in Fig. 6-75.(Since the interfaces of create, modify, delete, and load are similar, here only one figure is provided.)

Fig. 6-75 Creating the DSP board software


Page 444 of 516

The software information is presented at the right upper part of the interface, including the “BSC No.”, “Module No.”, “Munit No.”, “Unit No.”, “Rack No.”, “Shelf No.” and “Slot No.”.

Select the “DSP No.”, then the current version information used by this DSP is presented at the lower part.

Select the version to be updated to from “Update To” in the lower “Update Software Version” box, and press the “Create” key. The new DSP software version can thus be created. If the create operation is successful, the system will send a broadcast message, notifying all workstations in the system that this software version is successfully created; if the create operation fails, the system will give a prompt of failure in the interface.

Press the “Exit” key to go back to the rack diagram interface as illustrated in Fig. 6-73.

After the create operation is successful, the interface for modifying, deleting, and loading the DSP software is similar to that shown in Fig. 6-75, except for the command buttons in the interface. For loading, click “Load” button to complete the DSP software loading.

6.2.4.6 Physical site software loading

The software loading of BTS (including micro-cell BTS) is different from that of the BSC. In the browse tree on the software loading physical view interface as shown in Fig. 6-73, select the BTS that needs software loading under the BSC, and the interface display is as illustrated in Fig. 6-76.


Page 445 of 516

Fig. 6-76 The BTS software loading

The software information of the selected BS is presented at the right upper part of the interface, including the “BSC No”, “Site No.” and the description of BS. Various software versions currently used by BS are presented below the software information. The selected BS in Fig. 6-76 is BTS (V1A), which has only the software of FUC, CHP and OMU.

Select the version to be updated from the check box of the board in the “Update Version” box and set the relevant update software.

In the “Operation” menu, you can select “Create Version”, “Modify Version”, “Inquire Version” and “Load Version” to execute the corresponding operations. To create and modify the version, you should ensure that there is the relevant record in the stored software versions. Click the check box before the relevant software in “Update Version”, then the relevant available stored version record will be automatically added to the “Update Version” drop-down list box for selection. After the operation succeeds, the system will send a broadcast message, notifying all workstations in the system that the operation on the selected software version is successful; if the operation fails, the system will give a prompt of failure in the interface.


Page 446 of 516

In addition, the BTS software loading may also be performed in the BTS rack

diagram as illustrated in Fig. 6-77:

Fig. 6-77 The BTS rack diagram

In Fig. 6-77, right click on the relevant panel to pop up the shortcut menu in the interface: Create Version, Modify Version, Inquire Version, Delete Version, Load Version, and Inquire the Current Running Version. For example, by clicking “Create Version”, the interface for creating the BTS software version will pop up, as shown in Fig. 6-78:

Fig. 6-78 BTS rack software loading


Page 447 of 516

When creating the version, you should ensure that there is the relevant record

in the stored software versions. The relevant record will be automatically added

to the “Update Version” drop-down list box for selection. After the operation

succeeds, the system will send a broadcast message, notifying all workstations

in the system that the operation on the selected software version is successful;

if the operation fails, the system will give a prompt of failure in the interface.

6.2.5 Troubleshooting

The software loading is a complex job that involves the database operation, the communication between the foreground and the background, and the version management. The multi-party cooperation is needed to bring it into normal play. Below are the problems likely to occur in the software loading process:

1. Unable to create or find files

The operations of software storing and downloading are performed in a specified path on the server. The specified path is assigned at the client, and the file directory is required to be set up in advance when assigning; the later versions will check if the directory exists, if not, it will be created automatically. If the software has not been stored or has been lost after being stored, the files cannot be found during loading.

When the program exits abnormally (i.e. accidental power-off or restarting), and the opened files have not been closed in time. As a result, the error that the files cannot be created and some files cannot be deleted might occur. At this time, you can first get rid off the shared directory on the server, and then share it again.

2. No response from the foreground or too many communication errors

Software loading needs to be implemented with the cooperation of both the foreground and the background. Sometimes if the corresponding process in the foreground has not been started or has errors, or a certain board is not plugged firmly, or the power has not been turned on, the foreground may possibly give no response to the background messages. Another common reason


Page 448 of 516

for this error is that the equipment data have not been configured properly, i.e., the data in the database do not conform to the actual equipment in the rack.

3. The software loading failed again and again

The largest possibility lies in the board software itself that is unable to run normally, or in the hardware failure. In this case, please replace it with another version and try it again.

4. An error message of “Version ID or version No. is inconsistent with files” is displayed during storing

To avoid loading a wrong version, the corresponding identification information is added to the version files. This information will be checked during storing or initial version setting. If the files to be stored are inconsistent with the input version ID or the version No., such an error message will appear. So this problem may be eliminated by entering the correct version information and using the right version files.

5. Data synchronization failure during software loading or storing

In this case, first check whether the communication with MP is normal. If it is, then it is possible that the active MP is synchronizing data to the standby MP. You need to wait for a while before performing operations.

6.3 Integrated configuration management

6.3.1 Overview

The integrated configuration management is used for initial configuration and for modification to the configuration data. It establishes for the user a flow that enables the operator and maintainer to conduct physical configuration easily, and provides the user with a good graphical user interface based on the flow, so that the user can complete the initial configuration or incremental configuration conveniently.

After successful login, click “Configuration Management→Integrated Configuration Management” menu item in the main interface of the OMCR


Page 449 of 516

(V2) client (Fig. 2-10). First, select the configuration mode, as shown in Fig. 6-79. To enter the initial configuration wizard, select “Initial Configuration” and then click “OK”. To enter the modify configuration wizard, select “Modify Configuration” and then click “OK”; If you click “Cancel”, you will enter the state where you can only edit the script. The specific settings according to the wizard will be introduced in the subsequent chapters. After the settings in the wizard are completed, the main interface for integrated configuration management will appear, as shown in Fig. 6-80.

Fig. 6-79 Selecting the configuration mode

Fig. 6-80 Main interface of the integrated configuration management


Page 450 of 516

6.3.2 Operations of the integrated configuration management interface

6.3.2.1 Initial configuration

This section will focus on the initial configuration, and modify configuration will be introduced in the next section.

There are many MML commands for the initial configuration, so, to improve the efficiency, the debug mode is recommended for the initial configuration. In this mode, first write the data into the background database, then generate the ZDB file through the zdbsvr conversion tool, and finally send the ZDB file to the foreground.

Select “Initial Configuration” shown in Fig. 6-79, and click “OK” to enter the interface as shown in Fig. 6-81.

Fig. 6-81 Opening and editing the script

If the OMCHOME/ftpc/cmclient/configscript.tmp file currently exists, the user

can directly open it and continuously edit it. Otherwise, click “New” (as shown

in Fig. 6-82) and click “Next” to enter the wizard for editing the MSC.


Page 451 of 516

Fig. 6-82 Creating a new script and editing it

Click “Next” to enter the wizard for creating the MSC, as shown in Fig. 6-83.

Fig. 6-83 Editing the MSC

If there is an existing MSC, only the BSC will be added during this initial

configuration and the MSCID shall be the same as the existing one. Click


Page 452 of 516

“Next” to enter the part for editing the BSC, as shown in Fig. 6-84.

In the interface shown in Fig. 6-84, input the parameters such as BSCID, alias, longitude and latitude, and select “Initialization Radio Info”. In this way, during generation of the BSC, the program will automatically generate the corresponding radio information. The specific parameters can certainly be modified through the interface of the radio part in the integrated configuration management.

Fig. 6-84 Configuring the BSC

After the BSC parameters are properly configured, click “OK”. The information about the nodes such as the MSC and BSC will be generated. Right click the “MSC” node in the physical view, as shown in Fig. 6-85, and select the “MSC Properties” menu.


Page 453 of 516

Fig. 6-85 Modifying the MSC

In this way, the interface for editing the MSC will be displayed. The MSCID cannot be modified, as shown in Fig. 6-86.

Fig. 6-86 Modifying the MSC


Page 454 of 516

In Fig. 6-85, right click the “BSC” node in the physical view to pop up the menu as shown in Fig. 6-87 (in the GSM environment) or in Fig. 6-88 (in the GPRS environment). Select the “BSC Properties” menu. Then the user can modify the BSC parameters.

Fig. 6-87 Selecting and modifying the BSC - GSM


Page 455 of 516

Fig. 6-88 Selecting and modifying the BSC - GPRS

In the right-click menus shown in Fig. 6-87 or Fig. 6-88, select “Add Rack” to

enter the interface for adding the racks, as shown in Fig. 6-89 (in the GSM

environment) or in Fig. 6-90 (in the GPRS environment).


Page 456 of 516

Fig. 6-89 Adding a rack - GSM

Fig. 6-90 Adding a rack - GPRS

Select the shelves in turn (first select those at the control layer) and click “OK”. The program will automatically add the default rack, shelf, and board, as shown in Fig. 6-91.


Page 457 of 516

Fig. 6-91 Default rack

1. Adding a new DRT board

Right click the DRT board to pop up a menu as shown in Fig. 6-92.

Fig. 6-92 Adding a DRT board (1)

In the right-click menus as shown in Fig. 6-92, select the “Add Board” to enter the interface for setting the DRT parameters, as shown in Fig. 6-93.Select the DRT type and the DSP type, and then just click “OK”.


Page 458 of 516

Fig. 6-93 Adding a DRT board (2)

2. Adding a TIC board for A interface

Right click the TIC board to pop up a menu. In this menu, select the “Add Board” menu to enter the interface for setting the TIC parameters, as shown in Fig. 6-94. The user can click an item in the N7Lik list. By selecting in the list, the user can specify the corresponding SLC and then click “OK”.


Page 459 of 516

Fig. 6-94 Adding a TIC for A interface

3. Configuring the MTP

Right click the MTP board to pop up a menu. In this menu, select the “Board Properties” menu to enter the interface for setting the MTP parameters, as shown in Fig. 6-95. If it is configured as 2M No. 7, select the CMT_ZXG10_2MMTP; otherwise, the default is CMT_ZXG10_MTP. Note that the communication types of two MTP boards must be the same.

Fig. 6-95 Configuring the MTP

4. Configuring the BIPP

Right click the BIPP board to pop up a menu. In this menu, select the “Board Properties” menu to enter the interface for setting the BIPP parameters, as shown in Fig. 6-96. Among them: HW1 is an odd number, and HW2 equals to the selected HW1 value plus 1 and cannot be modified. During the incremental configuration, the HW number cannot be modified because the connection has been configured.


Page 460 of 516

Fig. 6-96 Configuring the BIPP

5. Configuring the TIC board with Abis interface

Right click the TIC board to pop up a menu. In this menu, select the “Board Properties” menu to enter the interface for setting the TIC parameters, as shown in Fig. 6-97.Generally, all the PCMs are allocated. If a PCM connects to the Site, the connection information will be displayed. When this TIC panel or the PCM is deleted in this interface, the connection information will also be deleted.


Page 461 of 516

Fig. 6-97 Configuring the TIC with Abis interface

6. Configuring the SITE

In Fig. 6-85, right click the “Physical Equipment” node in the physical view, as shown in Fig. 6-98.


Page 462 of 516

Fig. 6-98 Configuring the SITE (1)

In the pop-up menu, select “Add BTS” menu to enter the wizard for adding the Site, as shown in Fig. 6-99.Input the information such as SITEID and SITE Type. The maximal length of the alias is 40, and ModuleNo. corresponds to the number of the module connected to the BIEPCM. After the Site is created, neither SITEID nor the Site Type can be modified.


Click “Next” to enter the interface shown in Fig. 6-100.


Page 463 of 516


Select “Initialization Panel” and click “Next” to begin to configure the BIEPCM. Select the connection type corresponding to the PCM, as shown in Fig. 6-101.



Page 464 of 516

Click “Connect” to pup up a dialog box as shown in Fig. 6-102. Select the PCM to be connected.


Select a PCM and then click “OK”. Then the user will enter the interface as shown in Fig. 6-103.



Page 465 of 516

Click “Finish”. The Site, rack, shelf, and panel will be automatically generated, as shown in Fig. 6-104.


7. Modifying the BIE panel

Right click the BIE/EBIE board, as shown in Fig. 6-105.


Page 466 of 516

Fig. 6-105 Modifying the BIE panel (1)

In the pop-up menu, select the “Panel Properties” menu to enter the interface for setting the BIE/EBIE parameters, as shown in Fig. 6-106.Through the “PanelType” selection box, the BIE panel type can be modified, for example, modify EBIE to the BIE. If the connection type is set to “Empty”, it indicates that the PCM is not allocated. Note: when configuring the connection relationship of the fourth PCM, the EBIE cannot be modified to the BIE. It can be modified to the BIE after the connection relationship is deleted.


Page 467 of 516

Fig. 6-106 Modifying the BIE panel (2)

8. Configuring the divider/combiner

Right click the TRU panel to pop up a menu as shown in Fig. 6-107.

Fig. 6-107 Adding a new TRU board


Page 468 of 516

In the right-click menu, select “Add Panel” to pop up a dialog box for selecting the divider and combiner. If the BTS type is BTSV1A, one divider and one combiner must be configured, as shown in Fig. 6-108. If the BTS type is BTSV2, one CDU can serve as both the divider and combiner, and the diversity receiver can be configured, as shown in Fig. 6-109.

Fig. 6-108 Configuring the divider/combiner (1)


Page 469 of 516

Fig. 6-109 Configuring the divider/combiner (2)

9. Modifying the CDU type

On the CDU panel, right click to pop up the menu, as shown in Fig. 6-110.


Page 470 of 516

Fig. 6-110 Modifying the CDU type (1)

In the pop-up menu, select the “Panel Properties” menu, and then the panel type can be modified, as shown in Fig. 6-111.Click “OK”, then modify is successful. Note that if the connection relationship of this CDU has been configured, the panel type cannot be modified.

Fig. 6-111 Modifying the CDU type (2)

10. Configuring 80W

Right click the TRU panel to pop up the menu. Select “Set As PEU” from the menu, as shown in Fig. 6-112.Then the “PEU” panel appears, as shown in Fig. 6-113.


Page 471 of 516

Fig. 6-112 Configuring 80W (1)

Fig. 6-113 Configuring 80W (2)

11. Configuring the radio information

Right click “Site 1” node in the physical view to pop up the menu as shown in Fig. 6-114.


Page 472 of 516

Fig. 6-114 Configuring the radio information (1)

Select the “Set Radio” menu to enter the wizard, as shown in Fig. 6-115.


The list displays the radio information that has been configured to this site.

Click “Next”, as shown in Fig. 6-116.


Page 473 of 516


After the “Finish” is clicked, the program will automatically add the corresponding logical site into the radio view. Right click the logical site in the radio view to pup up the menu as shown in Fig. 6-117.The functions of the menus will be introduced in detail in the subsequent chapters.



Page 474 of 516

12. Modifying the BSC

In the radio view, right click the “BSC” node to pop up the menu as shown in Fig. 6-118.

Fig. 6-118 Pop-up menu of the BSC

In the pop-up menu, select “BSC Radio Information”. Then the user can edit the BSC radio information, as shown in Fig. 6-119.Once a command is sent, it cannot be modified. So, the mobile country code and the mobile network code should be correct during the initial configuration.


Page 475 of 516

Fig. 6-119 Modifying the BSC

13. Configuring the cell information

In the radio view, right click the “Logical Site” node to pop up the menu as shown in Fig. 6-120.

Fig. 6-120 Configuring the cell information (1)

In the pop-up menu, select “Create Cell Radio Information” menu


Page 476 of 516

to pop up the interface for editing the cell radio information, as shown in Fig. 6-121 (in the GSM environment) or in Fig. 6-122 and Fig. 6-123 (in the GPRS environment). The LAC and Cell Code (CI) are allocated by the MSC, and the MCC+MNC+LAC+CI is unique.

Fig. 6-121 Configuring the cell information (2) – GSM

Fig. 6-122 Configuring the cell information (2) - cell information (GPRS)


Page 477 of 516

Fig. 6-123 Configuring the cell information (2) - GPRS info (GPRS)

14. Configuring TRX

In the logical view, right click “Cell 1” to pop up the menu as shown in Fig. 6-124.

Fig. 6-124 Pop-up menu of the cell


Page 478 of 516

In the pop-up menu, select “Create TRX Radio Information” to configure the TRX parameters, as shown in Fig. 6-125 (in the GSM environment) or in Fig. 6-126 (in the GPRS environment). One and only one BCCH carrier frequency must be configured in a cell.

Fig. 6-125 Configuring TRX - GSM

Fig. 6-126 Configuring TRX - GPRS


Page 479 of 516

15. Configuring the related cell

In the radio view, right click the “Cell” node to pop up the menu as shown in Fig. 6-127.

Fig. 6-127 Configuring the related cell (1)

In the right-click menu, select “Add the Related Cell” to pop up the interface for editing the related cell, as shown in Fig. 6-128.Which kind of related cell to be configured can be selected. A kind of related cells can be created through the menu, such as “Create Cell Handover and Reselection”, and “Create Interference Cell”.


Page 480 of 516

Fig. 6-128 Configuring the related cell (2)

16. Configuring the external cell

In the radio view, right click the “Physical Equipment” node to pop up the menu as shown in Fig. 6-129.

Fig. 6-129 Configuring the external cell (1)


Page 481 of 516

In the pop-up menu, select “Create External Cell Radio Information” to pop up the interface for editing the external cell, as shown in Fig. 6-130.

Fig. 6-130 Configuring the external cell (2)

17. Configuring the EasyWay

In the physical view, right click the “BSC” node to pop up the menu as shown in Fig. 6-131 (in the GSM environment) or in Fig. 6-132 (in the GPRS environment).


Page 482 of 516

Fig. 6-131 Configuring the EasyWay (1) - GSM

Fig. 6-132 Configuring the EasyWay (1) - GPRS

In the pop-up menu, select the “Configure EasyWay” to pop up the interface for editing the EasyWay, as shown in Fig. 6-133 (in the


Page 483 of 516

GSM environment) or in Fig. 6-134 (in the GPRS environment). First input the BTS. The system will automatically input the rack No. of this BTS. Select the rack No., PCM, and TS in turn.Select the EasyWay type. In the case of the PECM, the DROP must be configured, e.g. hanging line.

Fig. 6-133 Configuring the EasyWay (2) - GSM


Page 484 of 516

Fig. 6-134 Configuring the EasyWay (2) - GPRS

18. Saving the file

After the configuration is finished, click the “Save” button on the toolbar. Then the user will first enter the validity check phase, as shown in Fig. 6-135.

Fig. 6-135 Saving the file (1)

After “OK” is clicked, the list of checking results will be displayed, as shown in Fig. 6-136.


Page 485 of 516


If the validity checks result has an error prompt, please modify the configuration according to the prompt information. When a user conducts the initial configuration, the user needs to confirm whether the MSC will be added, as shown in Fig. 6-137.


To add MSC, click “OK”; otherwise, only the BSC will be added. After the user succeeds, he will enter step 3 of wizard: send the script to the server for ICC resolution, as shown in Fig. 6-138.


Page 486 of 516

Fig. 6-138 Process of generating the MML command (1)

Directly click “Next”. The script will be sent to the server, as shown in Fig. 6-139.


After the resolution succeeds, the system will automatically enter step 4, as shown in Fig. 6-140.


Page 487 of 516


The Batch mode is recommended. After the command is successfully sent, the command window will prompt: batch submission is successful. Now, the initial configuration is finished.


Page 488 of 516

6.3.2.2 Modifying the configuration

If the user selects “Modify Configuration” shown in Fig. 6-79, the system will first obtain the data script from the database, as shown in Fig. 6-141.

To improve the efficiency of executing the MML command script, it is recommended that the sites be added one by one during modification to the configuration.

Fig. 6-141 Incremental configuration (1)

Input the BSCID whose configuration needs to be modified. Note that this BSCID must exist in the system. Click “Next”. At this time, the system starts to obtain the data, as shown in Fig. 6-142.


After this succeeds, the dialog box for entering step 2 of wizard will automatically pop up, as shown in Fig. 6-143.


Page 489 of 516


Click “Next” to enter the phase of editing the script. The operations that follow are the same as those in the initial configuration.


Page 490 of 516

6.3.2.3 Configuring GPRS

1. Configuring the GPRS shelf

In the pop-up menu shown in Fig. 6-132, select the “Add Rack” menu to pop up a dialog box, as shown in Fig. 6-144.

Fig. 6-144 Dialog box for adding racks

Select the GIU and SPCU racks and then click “OK”, as shown in Fig. 6-145.


Page 491 of 516

Fig. 6-145 Racks

In Fig. 6-145, right click the PUC board, as shown in Fig. 6-146.

Fig. 6-146 Configuring the PUC (1)

In the pop-up menu, select the “Add Board” menu to pop up the dialog box as shown in Fig. 6-147.


Page 492 of 516

Fig. 6-147 Configuring the PUC (2)

In Fig. 6-145, right click the FRP, as shown in Fig. 6-148. In the pop-up menu, select the “Add Board” menu. Then the FRP board can be added.

Fig. 6-148 Adding the FRP board


Page 493 of 516

In Fig. 6-145, right click the BRP, as shown in Fig. 6-149. In the pop-up menu, select the “Add Board” menu. Then the BRP board can be added.

Fig. 6-149 Adding the BRP board

Then configure the TIC and the BRCH with GB interface. Select the TIC of the GIU shelf, and right click to select the “Add Board” menu to pop up a dialog box as shown in Fig. 6-150.


Page 494 of 516

Fig. 6-150 Configuring the TIC with GB interface

Click “Configure BRCH” to display the following dialog box, as shown in Fig. 6-151.

Fig. 6-151 Configuring BRCH (1)


Page 495 of 516

Select “PUC Location of BRCH”, as shown in Fig. 6-152.

Fig. 6-152 Configuring BRCH (2)

Then configure the NSE and the NSVC. In the physical view, right click the “BSC” node to pop up the menu as shown in Fig. 6-153.

Fig. 6-153 Configuring NSVC (1)


Page 496 of 516

In the right-click menu, select “Edit NSVC” menu to pop up a dialog box for editing the NSE, as shown in Fig. 6-154.


Click the “Add NSVC” button to pup up a dialog box for editing NSVC, as shown in Fig. 6-155.



Page 497 of 516

2. Configuring the GPRS cell

Select the “Logical Site” node, and right click to select the “Create Cell Radio Information” as shown in Fig. 6-156.If the cell is a GPRS cell, select “Support GPRS”.

Fig. 6-156 Configuring a GPRS cell (1)

In this way, the relevant parameters of the GPRS cell can be configured. The “GPRS Info” tab is shown in Fig. 6-157.


Page 498 of 516

Fig. 6-157 Configuring a GPRS cell (2)

3. Configuring the GPRS TRX

Right click the “Cell” node to pup up the menu. Select the “Create TRX Radio Information” menu to edit the relevant parameters of the GPRS TRX, as shown in Fig. 6-158.

Fig. 6-158 Configuring GPRS TRX


Page 499 of 516

6.4 Dynamic data management

6.4.1 Overview

Dynamic data management mainly provides the function of dynamically managing various land resources at the OMCR (V2) client, so as to implement the dynamic management of the land resource state, including inquiry, block, unblock, activate, deactivate, assemble, and disassemble operations. It mainly initiates from the client the operations of inquiring or modifying the states of various land resources and displays the operation results.

After a user successfully logs in, he can click “Configuration Management → Dynamic Data Management” menu in the OMCR (V2) client main interface (as shown in Fig. 2-10) to enter the main interface for dynamic data management (as shown in Fig. 6-159).

Fig. 6-159 The main interface for dynamic data management


Page 500 of 516

6.4.2 Operations of the dynamic data management interface

6.4.2.1 Inquiring/refreshing

The state of the land resources with dynamic attribute can be inquired. As shown in Fig. 6-160, select the channel to be queried, and right click to pup up the menu. Select the “Observe” key from the pop-up menu to obtain the inquiry result of this channel state.

Fig. 6-160 Inquiring the state

Refresh is to inquire the state of all channels or TSs. As shown in Fig. 6-161, right click in the list at the right lower part of the main interface to pop up the menu. Select the “Refresh” key of the menu to obtain the state of all channels.


Page 501 of 516

Fig. 6-161 Refreshing the state

6.4.2.2 Blocking/unblocking

Block/unblock serves to modify the state bit of the land resources with dynamic attribute such as BSC, BTS, and TRX. Take the channel for example. In the list on the right, select channel 2 to be queried and right click to pop up a menu. Select the “Block” or “Unblock” in the pop-up menu to initiate the operation for modifying the management state of channel 2, as shown in Fig. 6-162.


Page 502 of 516

Fig. 6-162 Blocking/unblocking

6.4.2.3 Activating/deactivating

Activate/deactivate is used to activate/deactivate the N7LINK. Select the “LINKID” node in the browse tree on the left, and select the N7LINK1 to be activated or deactivated from the list on the right. Then right click to pop up a menu. Select “Activate” or “Deactivate” from the pop-up menu to initiate the operation for activating/deactivating the N7LINK1, as shown in Fig. 6-163.


Page 503 of 516

Fig. 6-163 Activating/deactivating

6.4.2.4 PCM circuit assemble/disassemble

Circuit assemble/disassemble serves to assemble/disassemble the PCM circuit. Select the PCM circuit to be assembled/disassembled from the list on the right, and right click to pop up a menu. Select “Circuit Assemble” or “Circuit Disassemble” from the pop-up menu to initiate the operation for assembling/disassembling the PCM circuit, as shown in Fig. 6-164.


Page 504 of 516

Fig. 6-164 PCM circuit assemble/disassemble

6.4.2.5 Global resetting

In the tree-shaped list on the left of the main interface, select “GSM Equipment” or “BTS Equipment” and then right click to pop up a menu. Select the “Global Reset” from the pop-up menu to initiate the operation for global resetting, as shown in Fig. 6-165.


Page 505 of 516

Fig. 6-165 Global resetting

6.4.3 Troubleshooting

The dynamic data management is a multi-aspect and multi-module complex job that involves the database operation, the background MO operation, the communication between the foreground and the background, and the foreground operation. It needs the cooperation between many aspects to operate normally. The following problems are easily seen during the dynamic data management:

1. Dynamic data management serves to manage the land resources with dynamic attribute. Any resource without the dynamic attribute will not be embodied in the dynamic management interface.

2. Dynamic data management serves to modify the states of land resources with dynamic attribute on the foreground, so the operation must be initiated to the foreground. Any operation in DEBUG mode where the foreground is not connected will certainly fail.

3. The operation of dynamic data management will affect the state of the operated land resource, so it will affect the conversation. Be careful when using it.


Page 506 of 516

4. The foreground environment has a big effect on the operation of dynamic data management. Any error of the foreground operation will possibly be embodied by operation failure of the dynamic data management.


Page 507 of 516

7 Database Configuration and Monitoring

7.1 Overview

The database management includes the provisioning of the interfaces for the application modules to invoke the database and the monitoring and management on the database and interface functions. The database configuration and monitoring belongs to one part of the database management. It is responsible for setting and acquiring the database and related parameters of the interface module, as well as monitoring the operational status. These parameters include:

1. Total spaces of the configuration table, performance table and alarm table.

2. Used spaces of the configuration table, performance table and alarm table.

3. Whether DIF has established the normal connection with the database.

4. Free space alarm thresholds of the tables

Through the database configuration and the monitoring graphical interface, the following information can be obtained: The usage of the configuration table space, performance table space and alarm table space, whether normal connection has been established between DIF (Database Interface Function) and the database, and the alarm threshold of the free space of each table. At the same time, the alarm threshold value can be dynamically set.

7.2 Interface operations

After successful login, select “System Tools → Database Configuration and Monitoring” to enter the database configuration and monitoring interface shown in Fig. 7-1.


Page 508 of 516

Fig. 7-1 The main interface of database configuration and monitoring

On the interface from the top down, there are menu bar, tool bar, display column, command window and status bar. The menus on the menu-bar are in turn as follows:

1. Monitor contents: Monitor database information, Monitor alarm threshold, Exit.

2. Acquire parameters: Database parameter, Alarm threshold parameter.

3. Set parameters: Set alarm threshold.

4. View: Tool bar, Status bar, Command box, Expand, Collapse, Expand all, Collapse all, Refresh.

5. Help: Database configuration and monitoring help, Directory and index, About…

From left to right, the tool buttons on the toolbar in turn are: Monitor database information, Monitor alarm threshold, Database parameter, Alarm threshold parameter, Set alarm threshold, Expand, Collapse, Expand all, Collapse all, Refresh, Database configuration and monitoring help, Exit. The buttons on the toolbar correspond to the menus in the menu bar.


Page 509 of 516

The browse tree, which displays the database configuration and monitoring items, is on the left of the display column. The right side of the display column is divided into two tabs. The first tab is “Database space information”, which displays the database monitoring results. It includes the information of each table space and DIF status. The tab is again divided into two parts, the upper of which shows the detailed information in the form of a list, while the lower part of which displays the results in a more vivid way by using graphics. The second tab is "Alarm threshold information”, which shows each alarm threshold value of the free space of the table.

The command box is the character input interface, in which the user can directly input the MMI command to finish a certain operation. When the interface operation is performed, the relevant MML command will be displayed in the command box. It shall be noted that apart from compound commands, only commands related with database configuration and monitoring can be input in the application window of database configuration and monitoring.

Information such as operation terminal, operator and communication status are listed in the status bar.

7.2.1 Selecting monitoring contents

In Fig. 7-1, click the “Database parameter” and “Alarm threshold parameter” tool buttons on the toolbar or related menu items to enter the interface of monitoring contents selection, as shown in Fig. 7-2 and Fig. 7-3.


Page 510 of 516

Fig. 7-2 Database parameters

Fig. 7-3 Alarm threshold parameters

The monitoring contents include: configuration table space (Config Tablespace), performance table space (Perform Tablespace), alarm table space (Alarm Tablespace), alarm thresholds of the free space of the tables (FreeSpace of Config Tablespace, FreeSpace of Perform Tablespace, FreeSpace of Alarm Tablespace), and whether normal connection has been established between DIF and the database (Connect Status of DIF and DB).


Page 511 of 516

7.2.2 Monitoring database information

After the database monitoring contents are set, select the “Monitor database information” tool button on the toolbar to start acquiring the corresponding database monitoring information.

After the monitoring is started and the server successfully returns the result, the system will automatically display the acquired parameters in the monitoring result column shown in Fig. 7-4. The description is shown in the upper part of the interface, while the graphics are shown in the lower part of the interface.

Fig. 7-4 Database information monitoring results

The interface displays the latest information after the user acquires the information each time.

7.2.3 Monitoring alarm threshold

The alarm threshold means that when the available free space of each table reaches a certain degree, the monitoring server of the database will generate the alarm information to prompt the user about necessary preparations. Otherwise the database can not function normally at a


Page 512 of 516

certain time. In specific, the alarm threshold is divided into two types: Space alarm and percentage alarm. The space alarm means that when the free space of a certain table is less than the threshold value, the alarm will be generated. The percentage alarm means that when the free space percentage of a certain table is less than the alarm threshold value, the alarm will be generated. The alarm information will be shown in the alarm management interface.

Since the alarm threshold values are saved in the server, the user can only get the corresponding values after acquiring the threshold parameters.

Select the “Monitor alarm threshold” tool button in the toolbar to start acquiring the threshold value. The acquired parameters will be shown in the second tab of the monitoring result interface shown in Fig. 7-5.

Fig. 7-5 Alarm threshold results

7.2.4 Setting threshold parameters

Apart from viewing the alarm threshold information and using the default threshold value, the user also can set the more reasonable threshold value by himself, then the system will use the latest setting as the basis of alarm generation.

Click the “Set alarm threshold” tool button in the toolbar to enter the


Page 513 of 516

parameter setting interface shown in Fig. 7-6.

Fig. 7-6 Set DB alarm threshold

Each threshold value is an integer. After the setting is finished successfully, the system will automatically acquire the latest setting for the user’s reference.


Page 514 of 516

Appendix Abbreviations

Abbreviation Full name

Abis A-bis Interface

AIPP A Interface Peripheral Processor

AIU A Interface Unit

AUC Access Unit Controller

BAF BSS Adapter Function

BCCH Broadcast Channel

BIE Base station Interface Equipment

BIPP aBis Interface Peripheral Processor

BIU aBis Interface Unit

BOSN Bit Oriented Switching Network

BRP BSSGP RLC/MAC Protocol

BSIA Base Station Interface Adapter

BSC Base Station Controller

BSS Base station Sub System

BSSAP Base station Sub System Application Part

BSSGP Base station Sub System GPRS Protocol

BTS Base Transceiver Station

BVC BSSGP Virtual Connect

CBCH Cell Broadcast Channel

CCCH Common Control Channel

CDF Commands Dispatching Function

CLF Commands Logging Function

CMIP Common Management Information Protocol

CMIS Common Management Information Service

CRF Commands Resolution Function

CS Circuit Switched

DRT Dual-Rate Transcoder

DSP Digital Signal Processor

EDRT Enhanced DRT

EFD Event Forwarding Discriminator

EGSM Extend GSM

ESU Executable Software Unit

FN Frame Number

FR Frame Relay

FRP FR Protocol


Page 515 of 516


FTAM File Transfer Access Maintenance

FU Frame Unit

FUC Frame Unit Controller

GGSN Gateway GPRS Support Node

GIPP Gb Interface Peripheral Processor

GIU GPRS Interface Unit

GPRS General Packet Radio Service

GSM Globe System for Mobile communication

GSN GPRS Support Node

HMS ZXIP10-AS HMS

HSN Hopping Sequence Number

LAF Local Access Function

LAPD Link Access Protocol of D-Channel

LMF Local Management Function

LMT Local Management Terminal

MAC Medium Access Control

MAF Management Application Functions

MAIO Mobile Allocation Index Offset

MIB Management Information Base

MIT MO Instance Tree

MF Mediation Function

MKF MMI Kernel Function

MMI Man Machine Interface

MML Man Machine Language

MO Managed Object

MOC Managed Object Class

MOF MO administration Function

MP Main Processor

MS Mobile Station

MSC Mobile Switch Center

MSF Management Support Function

MTP Message Transfer Part

NAF NMC Access Function

NC Network Control

NEF Network Element Function

NMC Network Management Center

NS Network Service

NSVC NS Virtual Circuit

OMC Operation Maintenance Center

OMCR Operation Maintenance Center Radio


Page 516 of 516


OOF Operation Outputting Function

OSF Operations Systems Function

PACCH Packet Associated Control Channel

PAGCH Paging & Access Granted Channel

PCU Packet Control Unit

PDCH Packet Data Channel

PDTCH Packet Data Traffic Channel

PDU Protocol Data Unit

PP Peripheral Processor

PS Packet Switched

PTM Point To Multipoint

PTP Point To Point

PUC Packet Unit Control

PVC Permanent Virtual Circuit

RACH Random Access Channel

RMM Radio Management Module

RLC Radio Link Control

SDCCH Specified Control Channel

SGSN Serving GPRS Support Node

SMB Short Message Broadcast

SMM Service Management Module

SMS Short Message Service

SSF Session Services Function

TC TransCoder

TCH Traffic Channel

TCPP TransCoder unit Peripheral Processor

TIC Trunk Interface Circuit

TMN Telecommunication Management Network

TRAU Transcoder and Rate Adaptor Unit

TRX Transceiver

UISF User Interface Support Function

WAF Windows Administration Function

WSF WorkStation Function

zxg10-bsc(v2)operation manual vol 1

Documents

zxg10omcr v2

omcr v2 system chapter

omcr v2 system appendix

bsc v2vol

preface zxg10

maintenance center of

maintenance manual

test management chapter