ZXG10-BSC (V2)

Base Station Controller

Engineering Debugging
Guide
(V2005-01)

ZTE CORPORATION
ZXG10-BSC (V2) Base Station Controller
Engineering Debugging Guide (V2005-01)

* * * *

ZTE CORPORATION

ZTE Plaza, Keji Road South, Hi-Tech Industrial Park, Nanshan District, Shenzhen, P.R. China

Website: http://www.zte.com.cn

Postcode: 518057

Customer Support Center: (+86755) 26771900 800-9830-9830

Fax: (+86755) 26770801

Email: [email protected]

* * * *
 Statement

All rights reserved. No part of this documentation may be excerpted, reproduced,

translated, annotated or duplicated, in any form or by any means without the prior written
permission of ZTE Corporation.

and are the registered trade marks of ZTE Corporation. The names and
logos of ZTE products are proprietary logos or registered trade marks. The names of other
products and companies mentioned in this manual may be proprietary to their owners
respectively. Without the prior written permission of ZTE or the owners of third-party trade
marks or trade names, this manual does not grant the reader any permission or right to
use any marker appeared in the manual.

The product described herein conforms to the design requirements of environment

protection and human security. The storage, usage, and discard of the product shall
comply with the manual, related contract, or laws and regulations of related countries.

The actual product may differ from what is described in this standard 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.

For the latest document information, please visit http://support.zte.com.cn

Preface

This manual is provided to effectively avoid system equipment instability caused by

problems not found and solved, raise the equipment operation reliability, and set up the
systematic and standard debugging procedure.

It is applicable to the ZXG10-BSC (V2) base station controller of ZTE and serves as a
reference for site debugging of the ZXG10-BSC (V2) equipment.

Should you have any suggestions or comments, please feel free to contact us. Thank
you!

-i-
Contents

1 Debugging Preparation.............................................................................................................................1-1

1.1 Project Information..........................................................................................................................1-1

1.2 Tools & Instruments.........................................................................................................................1-1

1.3 Engineering Documents...................................................................................................................1-2

1.4 Equipment Configurations...............................................................................................................1-2

1.4.1 Data Configuration Flow.......................................................................................................1-2

1.4.2 Creating MSC and BSC........................................................................................................1-2

1.4.3 Setting up the Test Connection Site......................................................................................1-3

1.4.4 Hardware/Board Configuration.............................................................................................1-3

1.4.5 A Interface and Abis Interface Data Configuration..............................................................1-3

1.4.6 SS7 Signaling Data Configuration........................................................................................1-3

1.4.7 Software Configuration.........................................................................................................1-4

1.4.8 Creating the Transmit Command Set....................................................................................1-4

2 Power-on Inspection..................................................................................................................................2-1

3 Debugging Flow.........................................................................................................................................3-1

3.1 Self-Test & Debugging Procedure...................................................................................................3-1

4 Local Debugging........................................................................................................................................4-1

4.1 Checking Installation and Configuration.........................................................................................4-1

4.2 Power Voltage Test...........................................................................................................................4-1

4.3 Fan Power-On Check.......................................................................................................................4-1

4.4 Checking the Power Board...............................................................................................................4-2

4.5 Checking the Board Status...............................................................................................................4-2

4.6 Equipment Power-on/-off Sequence................................................................................................4-3

-i-
 4.7 NM Connection................................................................................................................................4-3

4.8 Configuring the IP Address of MP...................................................................................................4-3

4.9 Downloading the Created Initial Configuration Data to the Foreground MP.................................4-4

4.10 Checking the NM Connections......................................................................................................4-4

4.11 Alarm Function Test.......................................................................................................................4-4

4.12 Data Probe Observation.................................................................................................................4-5

4.13 Observing the Board Running Indication......................................................................................4-5

5 Joint Debugging.........................................................................................................................................5-1

5.1 System Joint Debugging Flow.........................................................................................................5-1

5.2 Physical Link Connectivity..............................................................................................................5-2

5.3 Checking the Boards and the NMS..................................................................................................5-2

5.4 Dial Performance Test......................................................................................................................5-2

5.5 Testing the A Interface Circuit Service............................................................................................5-3

Appendix A Data Probe Instructions.........................................................................................................A-1

Appendix B WINNTTCP Communication Component for BSC (V2) Test Server Instructions........B-1

Appendix C Abbreviations............................................................................................................................C-1

-ii-
1 Debugging Preparation

To ensure smooth equipment debugging, the equipment debugging staff should get
ready for the debugging in advance, including knowing the project information and
preparing tools, documents and the corresponding MSC configuration data. In addition,
a small BTS (such as the microcell BTS) is needed.

1.1 Project Information

Before the equipment debugging, the equipment debugging staff should find the user’s
correct address and contact means, the person in charge from the office party and the
type of the equipment to be installed, contact the local representative office of ZTE in
time to learn the preliminary engineering preparation, and consult the related
documents to learn the detailed equipment configurations, and goods delivery and
arrival status.

1.2 Tools & Instruments

Tools, meters and instruments needed for system debugging should be ready, as listed
below. The meters and instruments should be calibrated by the relevant metering
department of the government.

1. Tools: Phillips screwdriver, M4 flathead screwdriver, diagonal pliers, sharp nose

pliers, adjustable spanner, electric iron, solder wires, soft solder, insulating
adhesive tape, snap-off knife, sharp-nose tweezers, horizontal ruler, coaxial self-
loop cable, wire stripper and wire crimper.

2. Instruments and meters: Bit error tester, earth resistance tester and multimeter.

3. The server & client of the OMCR2.0 are correctly installed and the network
cables & HUBs are connected normally.

-1-
 ZXG10-BSC (V2) Base Station Controller Engineering Debugging Guide

1.3 Engineering Documents

Prior to the project installation, the installation staff should prepare the following
technical documents:

1. Survey and design documents of the communication switch equipment room.

2. Contract for future delivery of the project (copy).

3. Product manuals of the ZXG10-BSC (V2).

4. Forms and files for engineering records.

1.4 Equipment Configurations

Generally, the project plan provided contains specific equipment capacity and board
configurations. You need to conduct the specific equipment configurations based on the
design capacity. In the case of any project configuration change, the configuration
procedure and requirements described in this section should be followed. For the
specific operations of the background NM software, see the ZXG10-BSS (V2) Base
Station Subsystem Operation Manual.

1.4.1 Data Configuration Flow

The typical flow of switch data configuration with the background NM software is
shown as follows:

Create MSC and BSC → Set up test connection site → Configure hardware/boards →
Configure A interface and Abis interface data → Configure SS7 signaling data →
Configure software → Create the transmit command set.

1.4.2 Creating MSC and BSC

Use cfggui at the client to create the initial configuration scripts. Conduct the
corresponding configuration based on the MSC and BSC signaling point data provided
by the switch equipment room survey report. Connect the BSC to the MSC, determine
the specific configuration plan, set if the TC equipment is set remotely and if
multiplexing is to be adopted, and input the corresponding configuration data.

2
 ZXG10-BSC (V2) Base Station Controller Engineering Debugging Guide

1.4.3 Setting up the Test Connection Site

Set up a logical test site according to the test site type adopted, configure logical and
physical connections of the Abis interface and the corresponding carrier frequency,
conduct cell configuration based on the cell data provided by the survey report, and
configure the logical and physical equipment.

1.4.4 Hardware/Board Configuration

Determine the rack capacity based on the contract configuration and determine the
quantities of RMU and TCU modules to be configured accordingly. Add boards to the
logical rack and perform the corresponding connection setting. In the network
switching layer, the leftmost DSNI and the rightmost DSNI must be configured. The
two rightmost DSNI boards connect to the TCPP unit, while the two leftmost DSNI
boards connect to the BIPP unit. Determine the quantities of the BIPP and TCPP units
depending on the system capacity.

1.4.5 A Interface and Abis Interface Data Configuration

Configure the A interface trunk according to the configured boards and the engineering
design requirements. For the SS7 signaling configuration, configure the SS7 signaling
evenly on the trunk circuit boards based on the load-sharing rules. Decide the
corresponding multiplexing mode at the Abis interface depending on the conditions of
the interface boards used by the BTS, and configure the corresponding logical and
physical connection links. Set the timers such as the T3212 at the BSC side by referring
to the survey documents at the early stage.

1.4.6 SS7 Signaling Data Configuration

Configure the corresponding SS7 OSP and DSP data based on the data from the
engineering survey. Adjust the circuit data and signaling time slots at the MSC side
based on the trunk data configuration at the BSC side. For example, if the PCM line
code at the BSC side starts from 1, then the corresponding CIC should start from 33.
Generally, the signaling time slot at the BSC side is TS16 of the PCM line. Then it is
necessary to make corresponding adjustment at the MSC side. The load sharing of the
specific signaling link data rule shall be adopted on the trunk circuit boards.

3
 ZXG10-BSC (V2) Base Station Controller Engineering Debugging Guide

1.4.7 Software Configuration

Check the software version proposed in the project contract and the design, perform the
corresponding software loading and configuration at the client, and perform the
corresponding software configuration for each DSP chip on the TCPP of the TCU layer
module. Manually copy the software version of the foreground MP to the foreground,
use the OMCFTP to transfer data, and create a Class-1 version in the logical view and a
board version in the physical view.

1.4.8 Creating the Transmit Command Set

Convert the configured initial scripts with the convert tool at the client. If the DEBUG
mode is adopted, it is necessary to modify the related settings (see the operation and
maintenance manuals). The server database created can be directly written into the
running MMI command set file.

4
2 Power-on Inspection

After the equipment installation is completed, power on the equipment to check if the
units and boards are working normally and get ready for the equipment debugging. The

1
power-on flow of the ZXG10-BSC (V2) is shown in Fig. 2-1.

Fig. 2-1 Equipment Power-on Flow

Fig. 2-1 shows the first power-on flow after the equipment is installed or the equipment
fault is removed. For the power-on operations during equipment debugging and routine
maintenance, see the following sections.

2
3 Debugging Flow

3.1 Self-Test & Debugging Procedure

The system debugging flow of the ZXG10-BSC (V2) is shown in Fig. Debugging
Flow-1.

Fig. Debugging Flow-2 Self-test and Debugging Flow

1
The self-test and debugging procedure comprises steps such as power-on check, board
status check, communication check, self-loop test and software function check, while
the interconnection & joint debugging procedure comprises system connection, Abis
interface function test and A interface function test. The ZXG10-BSC (V2) can be put
into operation in the mobile communication network to connect BTSs only after the
interconnection & joint debugging succeeds.

During the equipment debugging in accordance with the standard procedure, you
should record the NE configuration data and the test data in the ZXG10-BSS Test
Acceptance Report for future reference. After completing the debugging work, you
should submit the Preliminary Acceptance Request to the user and get ready for project
acceptance.

2
4 Local Debugging

4.1 Checking Installation and Configuration

Before powering on the equipment, check the quantities and positions of the boards
and the connection lines in the interface area for the last time. In particular, carefully
check the -48V power cables lest the equipment be burnt due to incorrect connection of
power inputs.

4.2 Power Voltage Test

1. Before each power test, make sure that the loop switch of the power supply for
the equipment, the cabinet power switch at the equipment side and the power
switch on the power board are all off.

2. Check the positive and negative ends of the power input of the equipment with a
multimeter and there shall be no short circuit. The terminal label should be
correct and the protection ground should be connected. Then turn on the loop
switch of the power supply for the equipment.

3. Check the voltage of the equipment power supply with a multimeter and make
sure that the polarities are correct and the voltage is between -40V and -57V.
Record the test result in the ZXG10-BSS Digital Mobile Communication System
Engineering Documents.

4. Check the voltage between the protection ground terminal and the working
ground terminal with a multimeter. The voltage should be no more than 50 mV.

Turn off the loop switch of the power supply immediately if there is any exception
during the above tests, find the cause and remove the fault. If the tests are normal,
proceed to the fan power-on test.

4.3 Fan Power-On Check

After the power supply check, check if the fan units are normal by powering on the
fans. You may preliminarily check if the power cable connections in the equipment are

1
 normal through the fan power-on check. Record the test result in the ZXG10-BSS
Digital Mobile Communication System Engineering Documents.

Turn on the main power switch of the equipment cabinet and observe the operation of
the fans. For any exception, turn off the power immediately and check it. If the fans do
not run, check if the power cables inside the cabinet are correctly connected.

4.4 Checking the Power Board

POWP board check: The POWP board has over-/under-voltage alarm and lightning
protection functions. Use a multimeter to check if the input voltage at the power test
port of the POWP board is normal and check if the two -48V voltages are correctly
isolated by a diode with the resistance measurement function. The fans should work
normally and stably after being powered on.

POWB board check: The secondary power board POWB provides power to functional
unit layers. Unplug the boards in the functional layers and power on the power board.
Check the POWB power indicators. The green indicator is on and there is no alarm
indication. If there is any fault at the site, cut the power immediately and locate and
remove the fault.

Note: Wear an anti-static wrist strap before operating the board.

4.5 Checking the Board Status

After the power board check, you may power on all the system boards and check their
states.

First, set the power switch on the POWB board to “OFF”. Then insert the other boards
into their slots and set the power switch on the POWB board to “ON”. Check the states
of the running indicator on each board and those of the cabinet indicators. For any
exception, cut the power immediately and handle it.

For the equipment configured with two POWB boards, power on each POWB board
separately and observe the equipment indicator status. And then power on both boards
and observe the equipment indicator status.

For the indicator states of the functional unit boards in the rack system, see the ZXG10-
BSC (V2) Base Station Controller Technical Manual.

2
 ZXG10-BSC (V2) Base Station Controller Engineering Debugging Guide

When the indicators on the board panels are abnormal, find the cause and remove the
fault. Generally, you should check the following items:

1. If the boards do not perform self-test, check if the chip is inserted correctly, the
chip model, the burn-in content and the version.

2. If the boards reset from time to time, check the voltage.

3. Check if there is broken or damaged pin in the board slots on the backplane.

4. For interface board alarms due to that service signals are not connected,
generally you may conduct self-loop at the service port to remove the alarm.

4.6 Equipment Power-on/-off Sequence

Follow the equipment power-on and power-off sequences below during the equipment
debugging and routine maintenance:

Power-on sequence: Power switch of the cabinet → Power switch of the PWCK board

Power-off sequence: Switch on the PWCK board → power switch of the cabinet

During the power-on process, check the fan operation and board indicators according
to the power-on check contents described in this section. For any exception, find the
cause and handle the exception in time.

4.7 NM Connection
To enable the equipment to operate according to the engineering networking
requirements, you need to perform data configuration for the equipment, including
downloading the configuration data to the equipment main control board. In addition,
you need to test and monitor the foreground via the background NM equipment and
connect the network cable port on the MP rear slot with the HUB of the background
NM computer system to meet the NMS requirements.

4.8 Configuring the IP Address of MP

Based on the engineering design and site networking requirements, modify the
TCPIP.CFG file of the MP of the BSC (V2) RRM and SCM modules. Set the IP
address of the MP and the visiting IP of the background client. For details, see the
ZXG10-BSC(V2) Base Station Controller Installation Manual.

3
 ZXG10-BSC (V2) Base Station Controller Engineering Debugging Guide

4.9 Downloading the Created Initial Configuration Data to the

Foreground MP
After the MMI command set initially configured is executed in the SERVER, execute
the ZDBSVR command at the client to create the ZDB file to be run by the foreground
MP, transfer the created ZDB file to the foreground MP via OMCFTP, and import and
download the software via the client.

4.10 Checking the NM Connections

Test the NM connections after the downloading operations. Record the test result in the
ZXG10-BSS Digital Mobile Communication System Engineering Documents.

1. Check if the connection between the NM terminal and the equipment is normal.

Check in the client operation window of the NM software if there is correct

foreground equipment connection information.

2. Check if the commands can be normally issued and the data can be normally
received.

Check in the alarm interface at the NM client if the alarm status displayed by
each board is consistent with the actual equipment operation. Issue operation
commands to the boards through the NM client, and make sure that the
equipment boards can perform the corresponding operations according to the
commands, such as performing board reset and reading the current detailed
running information.

If the NM connection is abnormal, check the physical network cable connection

and the IP address setting of the foreground MP. When the board status in the
NMS is inconsistent with the actual equipment, check if the board slot and
version configured in the NMS are consistent with the actual equipment
configuration.

4.11 Alarm Function Test

To timely find NM equipment faults during the equipment debugging, test the
equipment alarm functions and record the test result in the ZXG10-BSS Digital Mobile
Communication System Engineering Documents.

1. Check if the alarm indicator is normal

4
 ZXG10-BSC (V2) Base Station Controller Engineering Debugging Guide

When a minor alarm occurs to a running board on the foreground, the fault
indicator of the board or a combination of indicators should indicate the alarm,
and the alarm information should be sent to the background alarm collection
system at the same time. If there is no corresponding alarm information at the
background, check the connecting network cable, and check if the MP board is
working normally and if the alarm severity setting is correct. Restart the
background management program to refresh the display if necessary.

2. Check if the alarm buzzer is normal

When alarms occur to the rack boards, the buzzer in the external alarm box
should buzz. If the buzzer is abnormal, first check if the buzzer is set to “mute”,
and then check the IP address setting of the alarm box, the connecting network
cable and cables, and if the alarm box is normally powered on and works
normally.

4.12 Data Probe Observation

Use the data probe to observe the foreground running table before the equipment joint
debugging to judge the current status of the foreground operation, the traffic and
signaling, and the data configuration.

Use the data probe to first check if the IP address setting of the probe client in the
foreground MP is correct, then check if the current version of the data probe matches
the OMCR version, and make sure that the probe function can be normally
implemented.

Use the probe to check if the last field of the foreground R_OFFICE table is 0, if the
SS7 signaling is smooth, if the STATUS of the R_CHANNEL table of the radio
resource field is 0, and if the traffic channel is available. Observe the R_BTS and
R_BSC field tables to check the configured traffic and signaling point data, and check
the cell code setting and the frequency setting.

4.13 Observing the Board Running Indication

Check if the running states of the PP boards at the foreground are normal after the
configuration data are uploaded. When the data uploading is completed, it is necessary
to reset the MP module. When the system is stable, observe the indicators of the

5
 ZXG10-BSC (V2) Base Station Controller Engineering Debugging Guide

running boards and check if the boards are running normally. And check the connected
sites and if the carrier indicators correctly indicate the transmit status.

6
5 Joint Debugging

5.1 System Joint Debugging Flow

The system joint debugging flow chart is shown in Fig. Joint Debugging-3.

Fig. Joint Debugging-3 System Joint Debugging Flow

1
5.2 Physical Link Connectivity
Check if the physical links between the BSC and the MSC and between the BSC and
the site are smooth, and if the link active indicator of the corresponding port of the
trunk interface circuit board is on. The link connection is normal when the indicator
flashes regularly. Check if the digital trunk connection indicators corresponding to the
TIC boards of the BIU module and the TCU module are working normally.

5.3 Checking the Boards and the NMS

For the running BSC V2.0, you should check the running boards to judge if the
functional boards of the BSC are running normally: First check the functional boards in
the BCTL-SCU shelf, the MP unit, the changeover function and the COMM boards,
and check if the running indicator of the SS7 signaling board is fast flashing to indicate
normal link activation and operation. And then check the functional boards in the
BCTL-RMU shelf, the MP module and the running indicators of the external
communication boards. For the trunk interface boards, check if the running indicator of
the corresponding connection port indicates normal link activation and operation.

After the hardware check, use the OMCR operation program of the background client
to monitor the foreground running status. Monitor the running states of the functional
boards through alarm management and observe if there is any alarm. Use test
management to test the foreground boards, the transmission condition inside the rack
and the board working states. Use data probe to observe the foreground tables, analyze
the fields, judge the foreground running status, and check the data configuration.

5.4 Dial Performance Test

After the software and hardware check, use a test MS to lock the frequency of the test
site and conduct the dial test. Check the conversation voice quality and the signal
receive quality. Use the background OMCR operating system and the signaling tracing
function to trace the signaling at the A and Abis interfaces, and check if the signaling
cooperation flow of the conversation is normal. Use the dynamic data management tool
of the background OMCR operating system to check the utilization of the dial channel.
Test a long conversation and check if the settings of the related timers at the A interface
are correct. And initiate call tracing with the help of the MSC side to trace the call
connection process and judge and analyze the call flow.

2
 ZXG10-BSC (V2) Base Station Controller Engineering Debugging Guide

In the case the site transmit frequency works normally, use the test MS to measure the
transmit frequency signal, and check the information related to the system broadcast:
Setting of the national code, network code, cell code. And measure the signal quality.

5.5 Testing the A Interface Circuit Service

After the software and hardware check of the A interface service path, check the
service utilization of the A interface circuit through the dial test. Observe the trunk
through dynamic data management of the background OMCR, block the A interface
service trunk in use, conduct dial test on the service circuits one by one, and judge the
application status of the trunk circuits.

Block the SS7 signaling link configured for the A interface and conduct separate dial
test of each SS7 signaling to check the configuration and application of the SS7
signaling.

3
Appendix A Data Probe Instructions

Installation and usage:

1. Run the installation program or directly copy the executable file to the required
directory.

2. Copy ShowStrp.dll, zxglang.dll and ZxUTools.dll to the system directory.

3. Configure win_mgt.ini based on the foreground IP addresses.

4. Add the IP address of the local machine and restart the machine.

5. Run Winnttcp.exe and start the connection.

6. Run ProbeApp.exe.

It is only necessary to execute Steps 5 and 6 in the future. To modify the

configurations, execute Steps 3 and 4.

Precautions:

1. Make sure that the TCP/IP connection is correct. See the appendix.

2. The automatic mode is adopted for the probe. Moving the focus on the interface
will trigger data requests. Before the previous batch of data is completely
transmitted, the newly issued command may not be executed correctly.

3. Since fixed BSC module configuration is used, there will be 9 BSCs in the
interface. Not all the modules may be available.

4. The error report caused by continuous sending of requests generally does not
affect the use of the probe. You only need to shut off the probe.

1
Appendix B WINNTTCP Communication
Component for BSC (V2) Test Server
Instructions

Components:

Name Path Description

WINNTTCP.EXE System directory or installation directory Communication

service program

COMMDLL.DLL System directory or installation directory Communication

function dynamic connection library

ZXCOMM.DLL System directory or installation directory ATL version with

the same function as COMMDLL. Only one of them will be used.

WIN_MGT.INI System directory Communication configuration file used

to configure the local IP address and the foreground address

Installation instructions:

The above files will be installed to the corresponding places during the installation of
common application programs. However, you need to manually change some contents
of the files.

ZXCOMM.DLL needs to be registered to the system. Generally, the setup program will
automatically register it. You may execute the REGSVR32 command to manually
register it.

WIN_MGT.INI needs to be manually modified to keep consistent with the foreground

setting and the local IP address. It comprises two parts: Local setting and BSC setting.
Please note that the space mark in the IP address is a comma instead of a dot.

Operating instructions:

1. WINNTTCP.EXE should be started before the application program; otherwise,

the application program cannot be successfully registered.

1
 2. The local address setting should be consistent with the TEST IP address setting
at the foreground.

3. The IP address of the BSC module should be consistent with the setting at the
foreground.

Common errors:

1. Prompt "Config file error!" indicates the configuration file format error. Check
the contents of WIN_MGT.INI and if the file path is correct.

2. Prompt "Socket bind error!" indicates that the local address set in the
configuration file does not exist in the local TCP/IP configuration. Please check
and modify the network configuration. You may need to restart the computer.

2
Appendix C 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

1
 ZXG10-BSC (V2) Base Station Controller Engineering Debugging Guide

Abbreviation Full Name

FRP FR Protocol
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

2
 ZXG10-BSC (V2) Base Station Controller Engineering Debugging Guide

Abbreviation Full Name

OMC Operation Maintenance Center
OMCR Operation Maintenance Center Radio
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
TMM Transport Management Module
TMN Telecommunication Management Network
TRAU Transcoder and Rate Adaptor Unit
TRX Transceiver
UISF User Interface Support Function
WAF Windows Administration Function
WSF WorkStation Function