Operation Manual-Data Configuration

Data Configuration of Small-capacity BSC
Table of Contents ......................................................................................... i

Chapter 1 Overview of Data Configuration................................................... 1-1
1.1 Configuration Procedures ................................................................. 1-1
1.2 Data Configuration Mode .................................................................. 1-3
1.3 Preparation for Data Configuration ................................................... 1-4
Chapter 2 Route Data Configuration ............................................................ 2-1
2.1 Overview ........................................................................................... 2-1
2.1.1 Physical Connection ................................................................. 2-1
2.1.2 Setting of the Subrack DIP Switches ........................................ 2-1
2.1.3 Configuration Procedures ......................................................... 2-2
2.2 Configuration of Routes between BAM and Boards ......................... 2-2
2.3 Configuration of Routes between BAM and BTSs ............................ 2-5
Chapter 3 Basic Information Configuration .................................................. 3-1
3.1 Overview ........................................................................................... 3-1
3.2 Configuration of BSC Basic Information ........................................... 3-1
Chapter 4 Equipment Data Configuration .................................................... 4-1
4.1 Overview ........................................................................................... 4-1
4.1.1 BSC Hardware System ............................................................. 4-1
4.2 Configuration of Hardware ................................................................ 4-3
4.2.1 Adding Racks ........................................................................... 4-3
4.2.2 Adding Subracks ...................................................................... 4-4
4.2.3 Adding Boards .......................................................................... 4-6
4.3 Configuration of Subrack Loading Information .................................. 4-7
4.4 Configuration of Inter-subrack E1/T1 Connection ............................. 4-8
4.4.1 Adding IMA Group and Link ..................................................... 4-9
4.4.2 Adding Inter-subrack E1/T1 Connection ................................... 4-11
4.5 Configuration of Inter-subrack SHO Terrestrial Link ......................... 4-12
4.6 Configuration of Module .................................................................... 4-13
4.7 Configuration of Board Parameters .................................................. 4-14
4.7.1 Modifying Loading Control Mode .............................................. 4-14
4.7.2 Modifying Subsystem Parameters ............................................ 4-15
Chapter 5 Clock System Configuration ........................................................ 5-1
5.1 Overview ........................................................................................... 5-1
5.1.1 Introduction to Clock System .................................................... 5-1
5.2 Configuration of GCKP ..................................................................... 5-4
5.3 Configuration of CAIE ....................................................................... 5-6
5.4 Configuration of CRPS CMUX .......................................................... 5-7
5.5 Configuration of CRPS CBIE/CXIE ................................................... 5-7
5.6 Configuration of CIPS CBIE/CXIE .................................................... 5-8
5.7 Configuration of CIPS CMUX............................................................ 5-9
Chapter 6 A1/A2 Interface Configuration ..................................................... 6-1
6.1 Overview ........................................................................................... 6-1
6.1.1 A1/A2 Interface Protocol Stack ................................................. 6-1
6.1.2 Physical Equipment .................................................................. 6-1
6.2 Configuration of DSP ........................................................................ 6-2
6.3 Configuration of OSP ........................................................................ 6-3
6.3.1 Adding Relationship between Module and Signaling Point ...... 6-4
6.3.2 Adding Originating Signaling Point ........................................... 6-4
6.4 Configuration of SS7 Standard ......................................................... 6-6
6.5 Configuration of Trunk Circuit ........................................................... 6-7
6.6 Configuration of MTP Link ................................................................ 6-8
6.7 Data to be Negotiated ....................................................................... 6-9
7.1 Overview ........................................................................................... 7-1
7.1.1 A3/A7 Interface Protocol Stack ................................................. 7-1
7.2 Configuration of Neighbor BSC......................................................... 7-3
7.3 Configuration of Connection Mode of Interface Boards .................... 7-4
7.4 Configuration of A7 Link .................................................................... 7-5
7.5 Configuration of A3 link ..................................................................... 7-6
7.6 Configuration of Inter-BSC SHO Terrestrial Link .............................. 7-7
Chapter 8 Abis Interface Configuration ........................................................ 8-1
8.1 Overview ........................................................................................... 8-1
8.1.1 Abis Interface Protocol Stack ................................................... 8-1
8.2 Configuration of Abis Interface Connection Mode ............................ 8-3
8.2.1 Configuration of IMA Group ...................................................... 8-4
8.2.2 Configuration of UNI Link ......................................................... 8-6
8.2.3 Configuration of Fractional ATM Link ....................................... 8-7
8.3 Configuration of BTS Basic Information ............................................ 8-8
8.3.1 BTS O&M Channel ................................................................... 8-9
8.3.2 BTS Signaling Channel ............................................................ 8-10
8.4 Configuration of BTS O&M Link ........................................................ 8-10
8.5 Configuration of BTS Signaling Link ................................................. 8-12
8.6 Configuration of BTS Traffic Link ...................................................... 8-13
Chapter 9 Cell Channel Configuration .......................................................... 9-1
9.1 Overview ........................................................................................... 9-1
9.1.1 Relevant Concepts ................................................................... 9-1
9.2 Configuration of Cell and Sector ....................................................... 9-3
9.3 Configuration of Sector Carrier ......................................................... 9-4
9.3.1 Configuration of Local BSC Carrier .......................................... 9-4
9.3.2 Configuration of External Carrier .............................................. 9-6
9.4 Configuration of Carrier Neighbor Relation ....................................... 9-7
Chapter 10 Packet Data Service Configuration ............................................ 10-1
10.1 Overview ......................................................................................... 10-1
10.1.1 Packet Data Service Networking ............................................ 10-1
10.1.2 Configuration Procedures ....................................................... 10-2
10.2 Configuration of PCF ...................................................................... 10-2
10.2.1 Adding PCF ............................................................................ 10-3
10.2.2 Setting PCF Access Network Parameters .............................. 10-3
10.3 Configuration of PCF Gateway ....................................................... 10-4
10.4 Configuration of PDSN .................................................................... 10-5
Chapter 11 Circuit Data Service Configuration ............................................ 11-1
11.1 Overview ......................................................................................... 11-1
11.1.1 Hardware Equipment .............................................................. 11-1
11.1.2 Configuration Procedures ....................................................... 11-1
11.2 Configuration of CIWF Board .......................................................... 11-2
11.3 Configuration of CIWF Modem Parameter ...................................... 11-3
11.4 Configuration of CIWF Interface IP Address ................................... 11-3
11.5 Configuration of CIWF IP Pool ........................................................ 11-4
11.6 Configuration of IWF Function Switch Parameter ........................... 11-5
Data Configuration of Large-capacity BSC
Chapter 1 Overview of Data Configuration................................................... 1-1
1.1 Configuration Procedures ................................................................. 1-1
1.2 Data Configuration Mode .................................................................. 1-3
1.3 Preparation for Data Configuration ................................................... 1-4
Chapter 2 CSWS Configuration ................................................................... 2-1
2.1 Overview of CSWS Configuration ..................................................... 2-1
2.1.1 CSWS Hardware ...................................................................... 2-1
2.2 Configuration of Basic Information through Serial Port ..................... 2-5
2.2.1 Setting up Configuration Environment ...................................... 2-6
2.2.2 Configuring Basic Information .................................................. 2-9
2.3 Formatting and Loading of CSWS Data ............................................ 2-11
2.4 Configuration of Service Data ........................................................... 2-11
2.4.1 Activating Ports ......................................................................... 2-12
2.4.2 Configuring Active/Standby Relation on Ports .......................... 2-14
2.4.3 Configuring Corresponding Relation between Subracks and
Ports .................................................................................................. 2-14
2.4.4 Configuring Route Data ............................................................ 2-15
Chapter 3 Basic Information Configuration .................................................. 3-1
3.1 Overview ........................................................................................... 3-1
3.2 Configuration of BSC Basic Information ........................................... 3-1
Chapter 4 Equipment Data Configuration .................................................... 4-1
4.1 Overview ........................................................................................... 4-1
4.1.1 BSC Hardware System ............................................................. 4-1
4.2 Configuration of Hardware ................................................................ 4-5
4.2.1 Adding Racks ........................................................................... 4-5
4.2.2 Adding Subracks ...................................................................... 4-6
4.2.3 Adding Boards .......................................................................... 4-9
4.3 Configuration of Subrack Optical Interface ....................................... 4-10
4.4 Configuration of Inter-subrack SHO Terrestrial Link ......................... 4-11
4.5 Configuration of Module .................................................................... 4-12
4.6 Configuration of Board Parameters .................................................. 4-13
4.6.1 Modifying Loading Control Mode .............................................. 4-14
4.6.2 Modifying Subsystem Parameters ............................................ 4-15
Chapter 5 Clock System Configuration ........................................................ 5-1
5.1 Overview ........................................................................................... 5-1
5.1.1 Transmission Synchronization .................................................. 5-1
5.1.2 Time Synchronization ............................................................... 5-1
5.1.3 Physical connection .................................................................. 5-2
5.2 Configuration of GCKP ..................................................................... 5-4
5.3 Configuration of CAIE ....................................................................... 5-5
5.4 Configuration of CRPS/CRMS CMUX .............................................. 5-6
5.5 Configuration of CSWS CLPC .......................................................... 5-7
5.6 Configuration of CMUX in Service Subrack ...................................... 5-8
7.1 Overview ........................................................................................... 7-1
7.1.1 A3/A7 Interface Protocol Stacks ............................................... 7-1
7.2 Configuration of Neighbor BSC......................................................... 7-3
7.5 Configuration of A3/A7 Interface PVC .............................................. 7-6
7.6 Configuration of Inter-BSC SHO Terrestrial Link .............................. 7-6
Chapter 8 Abis Interface Configuration ........................................................ 8-1
8.1 Overview ........................................................................................... 8-1
8.1.1 Abis Interface Protocol Stack ................................................... 8-1
8.2 Configuration of Abis Interface Connection Mode ............................ 8-3
8.2.1 Configuration of IMA Group ...................................................... 8-4
8.2.2 Configuration of UNI Link ......................................................... 8-6
8.2.3 Configuration of Fractional ATM Link ....................................... 8-7
8.3 Configuration of BTS Basic Information ............................................ 8-8
8.3.1 BTS O&M Channel ................................................................... 8-9
8.3.2 BTS Signaling Channel ............................................................ 8-10
8.4 Configuration of BTS O&M Link ........................................................ 8-11
8.5 Configuration of BTS Signaling Link ................................................. 8-12
8.6 Configuration of BTS Traffic Link ...................................................... 8-13
Chapter 9 Cell Channel Configuration .......................................................... 9-1
Chapter 10 Packet Data Service Configuration ............................................ 10-1
Chapter 11 Circuit Data Service Configuration ............................................ 11-1
Abbreviations and Acronyms
Appendix A Abbreviations and Acronyms .................................................... A-1
HUAWEI
1.Data Configuration of Small-capacity BSC
2.Data Configuration of Large-capacity BSC
3.Abbreviations and Acronyms
Airbridge cBSC6600 CDMA Base Station Controller

Operation Manual - Data Configuration
V100R003
Operation Manual
Volume Data Configuration
Manual Version T2-031640-20040415-C-1.31
Product Version V100R003
BOM 31161140
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.
Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © 2004 Huawei Technologies Co., Ltd.
All Rights Reserved
No part of this manual may be reproduced or transmitted in any form or by any

means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye,
Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co.,
Ltd.
All other trademarks mentioned in this manual are the property of their respective
holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
About This Manual
Release Notes
This manual applies to Airbridge cBSC6600 CDMA Base Station Controller V100R003.
Related Manuals
The related manuals are listed in the following table.
Manual Content
Airbridge cBSC6600 CDMA Base Station Describes documentation package of the cBSC6600,
Controller Documentation Guide including the organization, content and methods of using it.
Describes regulatory compliance statement and regulatory

Airbridge cBSC6600 CDMA Base Station
compliance information of the cBSC6600, and safety
Controller Compliance and Safety Manual
information needed to install and maintain the equipment.
Introduces the development of the CDMA network, and the

product features, system configuration, system functions,
Controller Technical Manual-System
related operation and maintenance, and technical
Description
specifications of the cBSC6600.
Airbridge cBSC6600 CDMA Base Station Describes the general architecture of the cBSC6600, the
Controller Technical Manual-System subracks, clock system, O&M system, and power supply
Architecture system, and signal flows.

Details the external interfaces, related protocols and
Controller Technical Manual-Interfaces and
standards, and typical service flows for the cBSC6600.
Protocols
Introduces the supporting bands, networking capacity, radio

Airbridge cBSC6600 CDMA Base Station channel management, power control, handoff decision,
Controller Technical Manual-System Function performance management, alarm management, dynamic
configuration, and reliability design of the cBSC6600.
Airbridge cBSC6600 CDMA Base Station Details the structures and working principles of the cables,
Controller Hardware Description Manual boards, subracks, and cabinets of the cBSC6600.

Controller Installation Manual-Hardware Covers the hardware installation of the cBSC6600.
Installation

Controller Installation Manual-Software Describes the software installation of the cBSC6600.
Installation
Airbridge cBSC6600 CDMA Base Station Describes procedures of commissioning the cBSC6600 after
Controller Installation Manual-System the hardware and software installation to ensure normal
Commissioning operation.

Covers the data configuration of the cBSC6600 for
Controller Operation Manual-Data
large-capacity and small-capacity offices.
Configuration
Manual Content

Describes contents and methods of routine maintenance over
Controller Maintenance Manual-Routine
the cBSC6600.
Maintenance

Controller Maintenance Details the troubleshooting for the cBSC6600.
Manual-Troubleshooting

Presents procedures and methods of replacing boards and
Controller Maintenance Manual-Parts
components of the cBSC6600.
Replacement
Organization
This manual introduces data configuration of Airbridge cBSC6600 CDMA Base Station
Controller systematically. There are three modules in the manual.
z Module 1 Data Configuration of Small-capacity BSC introduces data
configuration of CDMA Base Station Subsystem in case of small capacity,
including the configuration of the route, basic information, clock, interface, cell and
data service.
z Module 2 Data Configuration of Large-capacity BSC introduces data
configuration of CDMA Base Station Subsystem in case of large capacity. Some of
its chapters are directly quoted from Module 1.
z Module 3 Abbreviations and Acronyms lists all the abbreviations, acronyms
and the corresponding full names used in this manual.
Intended Audience
The manual is intended for the following readers:

z Technical engineers & technicians
z Telecom management staff
Conventions
This manual uses the following conventions:
I. General conventions
Convention Description
Arial Normal paragraphs are in Arial.
Arial Narrow Warnings, Cautions, Notes and Tips are in Arial Narrow.
Boldface Headings are in Boldface.

Courier New Terminal Display is in Courier New.
II. Command conventions
Boldface The keywords of a command line are in Boldface.
italic Command arguments are in italic.
[] Items (keywords or arguments) in square brackets [ ] are optional.
Alternative items are grouped in braces and separated by vertical bars. One is
{ x | y | ... }
selected.
Optional alternative items are grouped in square brackets and separated by

[ x | y | ... ]
vertical bars. One or none is selected.
Alternative items are grouped in braces and separated by vertical bars. A minimum
{ x | y | ... } *
of one or a maximum of all can be selected.
Optional alternative items are grouped in square brackets and separated by

[ x | y | ... ] *
vertical bars. Many or none can be selected.
III. GUI conventions
<> Button names are inside angle brackets. For example, click <OK> button.
Window names, menu items, data table and field names are inside square
[]
brackets. For example, pop up the [New User] window.
Multi-level menus are separated by forward slashes. For example,

/
[File/Create/Folder].
IV. Keyboard operation
Format Description
Press the key with the key name inside angle brackets. For example, <Enter>,
<Key>
<Tab>, <Backspace>, or <A>.
Press the keys concurrently. For example, <Ctrl+Alt+A> means the three keys
<Key1+Key2>
should be pressed concurrently.
Press the keys in turn. For example, <Alt, A> means the two keys should be
<Key1, Key2>
pressed in turn.
V. Mouse operation
Action Description
Click Press the left button or right button quickly (left button by default).
Double Click Press the left button twice continuously and quickly.
Drag Press and hold the left button and drag it to a certain position.
VI. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Caution: Means reader be extremely careful during the operation.
Note: Means a complementary description.

Airbridge cBSC6600 CDMA Base Station Controller Table of Contents
Table of Contents
Module 1 Data Configuration of Small-capacity BSC
Chapter 1 Overview of Data Configuration................................................................................. 1-1

1.1 Configuration Procedures .................................................................................................. 1-1
1.2 Data Configuration Mode................................................................................................... 1-3
1.3 Preparation for Data Configuration .................................................................................... 1-4
Chapter 2 Route Data Configuration ........................................................................................... 2-1

2.1 Overview ............................................................................................................................ 2-1
2.1.1 Physical Connection................................................................................................ 2-1
2.1.2 Setting of the Subrack DIP Switches ...................................................................... 2-1
2.1.3 Configuration Procedures ....................................................................................... 2-2
2.2 Configuration of Routes between BAM and Boards .......................................................... 2-2
2.3 Configuration of Routes between BAM and BTSs............................................................. 2-5
Chapter 3 Basic Information Configuration................................................................................ 3-1

3.1 Overview ............................................................................................................................ 3-1
3.2 Configuration of BSC Basic Information ............................................................................ 3-1
Chapter 4 Equipment Data Configuration................................................................................... 4-1

4.1 Overview ............................................................................................................................ 4-1
4.1.1 BSC Hardware System ........................................................................................... 4-1
4.2 Configuration of Hardware................................................................................................. 4-3
4.2.1 Adding Racks .......................................................................................................... 4-3
4.2.2 Adding Subracks ..................................................................................................... 4-4
4.2.3 Adding Boards......................................................................................................... 4-6
4.3 Configuration of Subrack Loading Information .................................................................. 4-7
4.4 Configuration of Inter-subrack E1/T1 Connection ............................................................. 4-8
4.4.1 Adding IMA Group and Link .................................................................................... 4-9
4.4.2 Adding Inter-subrack E1/T1 Connection ............................................................... 4-11
4.5 Configuration of Inter-subrack SHO Terrestrial Link........................................................ 4-12
4.6 Configuration of Module................................................................................................... 4-13
4.7 Configuration of Board Parameters ................................................................................. 4-14
4.7.1 Modifying Loading Control Mode .......................................................................... 4-14
4.7.2 Modifying Subsystem Parameters ........................................................................ 4-15
Chapter 5 Clock System Configuration ...................................................................................... 5-1

5.1 Overview ............................................................................................................................ 5-1
5.1.1 Introduction to Clock System .................................................................................. 5-1
i

5.2 Configuration of GCKP ...................................................................................................... 5-4
5.3 Configuration of CAIE ........................................................................................................ 5-6
5.4 Configuration of CRPS CMUX........................................................................................... 5-7
5.5 Configuration of CRPS CBIE/CXIE.................................................................................... 5-7
5.6 Configuration of CIPS CBIE/CXIE ..................................................................................... 5-8
5.7 Configuration of CIPS CMUX ............................................................................................ 5-9
Chapter 6 A1/A2 Interface Configuration .................................................................................... 6-1

6.1 Overview ............................................................................................................................ 6-1
6.1.1 A1/A2 Interface Protocol Stack ............................................................................... 6-1
6.1.2 Physical Equipment................................................................................................. 6-1
6.2 Configuration of DSP ......................................................................................................... 6-2
6.3 Configuration of OSP......................................................................................................... 6-3
6.3.1 Adding Relationship between Module and Signaling Point .................................... 6-4
6.3.2 Adding Originating Signaling Point.......................................................................... 6-4
6.4 Configuration of SS7 Standard .......................................................................................... 6-6
6.5 Configuration of Trunk Circuit ............................................................................................ 6-7
6.6 Configuration of MTP Link ................................................................................................. 6-8
6.7 Data to be Negotiated........................................................................................................ 6-9

7.1 Overview ............................................................................................................................ 7-1
7.2 Configuration of Neighbor BSC ......................................................................................... 7-3
7.3 Configuration of Connection Mode of Interface Boards..................................................... 7-4
7.4 Configuration of A7 Link .................................................................................................... 7-5
7.5 Configuration of A3 link...................................................................................................... 7-6
7.6 Configuration of Inter-BSC SHO Terrestrial Link............................................................... 7-7
Chapter 8 Abis Interface Configuration ...................................................................................... 8-1

8.1 Overview ............................................................................................................................ 8-1
8.1.1 Abis Interface Protocol Stack .................................................................................. 8-1
8.2 Configuration of Abis Interface Connection Mode ............................................................. 8-3
8.2.1 Configuration of IMA Group .................................................................................... 8-4
8.2.2 Configuration of UNI Link ........................................................................................ 8-6
8.2.3 Configuration of Fractional ATM Link...................................................................... 8-7
8.3 Configuration of BTS Basic Information ............................................................................ 8-8
ii
8.3.1 BTS O&M Channel.................................................................................................. 8-9

8.3.2 BTS Signaling Channel ......................................................................................... 8-10
8.4 Configuration of BTS O&M Link....................................................................................... 8-10
8.5 Configuration of BTS Signaling Link ................................................................................ 8-12
8.6 Configuration of BTS Traffic Link..................................................................................... 8-13
8.7 Data to be Negotiated...................................................................................................... 8-14
Chapter 9 Cell Channel Configuration ........................................................................................ 9-1

9.1 Overview ............................................................................................................................ 9-1
9.1.1 Relevant Concepts.................................................................................................. 9-1
9.2 Configuration of Cell and Sector........................................................................................ 9-3
9.3 Configuration of Sector Carrier .......................................................................................... 9-4
9.3.1 Configuration of Local BSC Carrier......................................................................... 9-4
9.3.2 Configuration of External Carrier............................................................................. 9-6
9.4 Configuration of Carrier Neighbor Relation ....................................................................... 9-7
Chapter 10 Packet Data Service Configuration........................................................................ 10-1

10.1 Overview ........................................................................................................................ 10-1
10.1.1 Packet Data Service Networking......................................................................... 10-1
10.1.2 Configuration Procedures ................................................................................... 10-2
10.2 Configuration of PCF ..................................................................................................... 10-2
10.2.1 Adding PCF ......................................................................................................... 10-3
10.2.2 Setting PCF Access Network Parameters .......................................................... 10-3
10.3 Configuration of PCF Gateway ...................................................................................... 10-4
10.4 Configuration of PDSN .................................................................................................. 10-5
Chapter 11 Circuit Data Service Configuration ........................................................................ 11-1

11.1 Overview ........................................................................................................................ 11-1
11.1.1 Hardware Equipment .......................................................................................... 11-1
11.2 Configuration of CIWF Board......................................................................................... 11-2
11.3 Configuration of CIWF Modem Parameter .................................................................... 11-3
11.4 Configuration of CIWF Interface IP Address ................................................................. 11-3
11.5 Configuration of CIWF IP Pool....................................................................................... 11-4
11.6 Configuration of IWF Function Switch Parameter ......................................................... 11-5
Module 2 Data Configuration of Large-capacity BSC

iii
Chapter 2 CSWS Configuration ................................................................................................... 2-1

2.1 Overview of CSWS Configuration...................................................................................... 2-1
2.1.1 CSWS Hardware ..................................................................................................... 2-1
2.2 Configuration of Basic Information through Serial Port ..................................................... 2-5
2.2.1 Setting up Configuration Environment .................................................................... 2-6
2.2.2 Configuring Basic Information ................................................................................. 2-9
2.3 Formatting and Loading of CSWS Data .......................................................................... 2-11
2.4 Configuration of Service Data.......................................................................................... 2-11
2.4.1 Activating Ports ..................................................................................................... 2-12
2.4.2 Configuring Active/Standby Relation on Ports ...................................................... 2-14
2.4.3 Configuring Corresponding Relation between Subracks and Ports...................... 2-14
2.4.4 Configuring Route Data......................................................................................... 2-15

3.1 Overview ............................................................................................................................ 3-1

4.1 Overview ............................................................................................................................ 4-1
4.2.1 Adding Racks .......................................................................................................... 4-5
4.2.2 Adding Subracks ..................................................................................................... 4-6
4.2.3 Adding Boards......................................................................................................... 4-9
4.3 Configuration of Subrack Optical Interface...................................................................... 4-10

5.1 Overview ............................................................................................................................ 5-1
5.1.1 Transmission Synchronization ................................................................................ 5-1
5.1.2 Time Synchronization.............................................................................................. 5-1
5.1.3 Physical connection ................................................................................................ 5-2
5.4 Configuration of CRPS/CRMS CMUX ............................................................................... 5-6
5.5 Configuration of CSWS CLPC ........................................................................................... 5-7
iv
5.6 Configuration of CMUX in Service Subrack....................................................................... 5-8

7.1 Overview ............................................................................................................................ 7-1
7.1.1 A3/A7 Interface Protocol Stacks ............................................................................. 7-1
7.5 Configuration of A3/A7 Interface PVC ............................................................................... 7-6

8.1 Overview ............................................................................................................................ 8-1
8.3.1 BTS O&M Channel.................................................................................................. 8-9
Module 3 Abbreviations and Acronyms
Appendix A Abbreviations and Acronyms .................................................................................A-1
v
HUAWEI

Data Configuration of Small-capacity

BSC
Operation Manual - Data Configuration Data Configuration of Small-capacity BSC
Table of Contents

Chapter 2 Route Data Configuration ........................................................................................... 2-1

2.1 Overview ............................................................................................................................ 2-1
2.1.2 Setting of the Subrack DIP Switches ...................................................................... 2-1
2.2 Configuration of Routes between BAM and Boards .......................................................... 2-2
2.3 Configuration of Routes between BAM and BTSs............................................................. 2-5

3.1 Overview ............................................................................................................................ 3-1

4.1 Overview ............................................................................................................................ 4-1
4.2.1 Adding Racks .......................................................................................................... 4-3
4.2.2 Adding Subracks ..................................................................................................... 4-4
4.2.3 Adding Boards......................................................................................................... 4-6
4.3 Configuration of Subrack Loading Information .................................................................. 4-7
4.4 Configuration of Inter-subrack E1/T1 Connection ............................................................. 4-8
4.4.1 Adding IMA Group and Link .................................................................................... 4-9
4.4.2 Adding Inter-subrack E1/T1 Connection ............................................................... 4-11

5.1 Overview ............................................................................................................................ 5-1
5.1.1 Introduction to Clock System .................................................................................. 5-1
i

5.4 Configuration of CRPS CMUX........................................................................................... 5-7
5.5 Configuration of CRPS CBIE/CXIE.................................................................................... 5-7
5.6 Configuration of CIPS CBIE/CXIE ..................................................................................... 5-8
5.7 Configuration of CIPS CMUX ............................................................................................ 5-9

6.1 Overview ............................................................................................................................ 6-1
6.2 Configuration of DSP ......................................................................................................... 6-2
6.3 Configuration of OSP......................................................................................................... 6-3
6.3.1 Adding Relationship between Module and Signaling Point .................................... 6-4
6.3.2 Adding Originating Signaling Point.......................................................................... 6-4
6.4 Configuration of SS7 Standard .......................................................................................... 6-6
6.5 Configuration of Trunk Circuit ............................................................................................ 6-7
6.6 Configuration of MTP Link ................................................................................................. 6-8

7.1 Overview ............................................................................................................................ 7-1
7.3 Configuration of Connection Mode of Interface Boards..................................................... 7-4
7.5 Configuration of A3 link...................................................................................................... 7-6

8.1 Overview ............................................................................................................................ 8-1
8.3.1 BTS O&M Channel.................................................................................................. 8-9
ii


9.1 Overview ............................................................................................................................ 9-1
9.1.1 Relevant Concepts.................................................................................................. 9-1
9.2 Configuration of Cell and Sector........................................................................................ 9-3
9.3 Configuration of Sector Carrier .......................................................................................... 9-4
9.3.1 Configuration of Local BSC Carrier......................................................................... 9-4
9.3.2 Configuration of External Carrier............................................................................. 9-6
9.4 Configuration of Carrier Neighbor Relation ....................................................................... 9-7

10.1 Overview ........................................................................................................................ 10-1
10.1.1 Packet Data Service Networking......................................................................... 10-1
10.2 Configuration of PCF ..................................................................................................... 10-2
10.2.1 Adding PCF ......................................................................................................... 10-3
10.2.2 Setting PCF Access Network Parameters .......................................................... 10-3
10.3 Configuration of PCF Gateway ...................................................................................... 10-4
10.4 Configuration of PDSN .................................................................................................. 10-5

11.1 Overview ........................................................................................................................ 11-1
11.1.1 Hardware Equipment .......................................................................................... 11-1
11.2 Configuration of CIWF Board......................................................................................... 11-2
11.3 Configuration of CIWF Modem Parameter .................................................................... 11-3
11.4 Configuration of CIWF Interface IP Address ................................................................. 11-3
11.5 Configuration of CIWF IP Pool....................................................................................... 11-4
11.6 Configuration of IWF Function Switch Parameter ......................................................... 11-5
iii
Airbridge cBSC6600 CDMA Base Station Controller Chapter 1 Overview of Data Configuration
Chapter 1 Overview of Data Configuration
This module introduces methods and procedures of data configuration in the

small-capacity cBSC6600 system.
Man-machine language (MML) commands are used for the data configuration. The key
parameters involved are described. For the rest configuration commands and detailed
descriptions of the parameters, see the MML on-line help.
1.1 Configuration Procedures

The data configuration of the small-capacity BSC is divided into ten sections.
Figure 1-1 shows the configuration procedures.
1-1
Route data
configuration
Basic information
configuration
Equipment data
configuration
Clock system
configuration
A1/A2 interface
configuration
A3/A7 interface
configuration
Abis interface
configuration
Cell channel
configuration
Packet data service

configuration
Circuit data service

configuration
Figure 1-1 Procedures of data configuration
Note:
The procedure enclosed by the dotted block is optional. That is, it is subject to the actual application.
The following are specific configuration procedures.

1) Route data configuration: Configuring the dial in-line package (DIP) switches of
BSC service processing subracks and the routes between back administration
module (BAM) and boards and BTSs. For details, see Chapter 2, "Route Data
Configuration".
2) Basic information configuration: Configuring some system-level parameters of the
BSC. For details, see Chapter 3, "Basic Information Configuration".
1-2
3) Equipment data configuration: Configuring module and hardware equipment such

as rack, subrack and board of small-capacity BSC. For details, see Chapter 4,
"Equipment Data Configuration".
4) Clock system configuration: Configuring the clock system of the small-capacity
BSC. The composition and configuration of the clock system are detailed in
Chapter 5, "Clock System Configuration".
5) A1/A2 interface configuration: Configuring SS7 and trunk data on A1/A2 interface.
For details, see Chapter 6, "A1/A2 Interface Configuration".
6) A3/A7 interface configuration: configuring the A3/A7 interface between adjacent
BSCs if the system needs to support the inter-BSC soft handoff. For details, see
Chapter 7, “A3/A7 Interface Configuration”.
7) Abis interface configuration: Configuring traffic and signaling data on Abis
interface. For details, see Chapter 8, "Abis Interface Configuration".
8) Cell channel configuration: Configuring the logic resources of the BTS, such as
cell and channel. For details, see Chapter 9, "Cell Channel Configuration".
9) Packet data service configuration: Configuring the data-service-specific
parameters if the BSC needs to support the packet data service, such as the
configuration of the packet control function (PCF), packet data service node
(PDSN), and related parameters. For details, see Chapter 10, “Packet Data
Service Configuration”.
10) Circuit data service configuration: configuring the parameters related to the circuit
data service if the system needs to support the circuit data service. As the
interworking function (IWF) equipment may be configured in the BSC or in the
MSC, the configurations in these two cases are respectively introduced in Chapter
11, “Circuit Data Service Configuration”.
1.2 Data Configuration Mode

During the data configuration, the route data should be configured through the DOS
window on the BAM. The rest data can be configured by executing the MML commands
on the BSC service maintenance system.
Two modes are available for the configuration through MML commands: online mode
and offline mode.
I. Online mode
When the system is in online status, the commands you execute not only modify the
data tables and data loading files in BAM, but also load the data modified to the BSC.
You may use the command LON to set the system to online status.
II. Offline mode
When the system is in offline status, the commands you execute modify the data tables
and data loading files in BAM only. The data modified cannot be loaded to the BSC.
1-3
When you execute the command LON to switch over the system to online status, the
commands executed in offline mode is loaded to the foreground Host automatically.
You may use the command LOF to set the system to offline status.
1.3 Preparation for Data Configuration

Before the data configuration, you should collect the following information and make
relevant preparations.
I. Networking mode
Familiarize yourself with the BSS-related networking topology structure.
II. BSC hardware information
Learn the BSC hardware configuration, including:

z Position of the rack
z Configuration of the service processing subracks and the boards equipped
z Hardware configuration of A1/A2, A3/A7 interfaces and Abis interface
z The correspondence between subrack and module
III. IP address assignment
Learn the planning and assignment of IP addresses in BSS, including:

z BSC IP address
z The signaling IP address of CSPU
z The BTS operation & maintenance (O&M) gateway IP address
z The external IP address of the CPPU
z PCF IP address
z PDSN IP address
z IP address of CIWF
IV. MSC-specific data
When A1/A2 interface is configured, some system parameters, SS7 and trunk
parameters should be consistent with those configured at MSC. The data include:
z A-interface version
z MSC identification (MSC ID)
z Network identification (NID) and system identification (SID)
z Local area code (LAC)
z Destination signaling point code (DPC)
z Originating signaling point code (OPC) and the OPC-CIPS correspondence
z The type of network indicator and the number of digits of signaling point code
z Cell identity (CELL ID)
z Signaling link code (SLC) and SLC send
z No. of the time slot occupied by the signaling link
1-4
z Signaling connection control part (SCCP) subsystem No.

z E1/T1 No., trunk group No., and circuit identification code (CIC) corresponding to
each CIPS
V. BTS-specific data
When Abis interface is configured, the following data should be consistent with those
configured at BTS.
z BTS signaling IP address
z BTS signaling link ID and bootstrap protocol (BOOTP) ID
z BTS O&M IP address
z BTS O&M link ID
z Connection mode and traffic link ID of the Abis interface
VI. Adjacent BSC-specific data
When the A3/A7 interface is configured, the following data should be consistent with
those configured at the adjacent BSC.
z Local entity attribute
z A3 port No.
z A7 link ID
z A3 link IDs of the local and peer BSCs
1-5
Airbridge cBSC6600 CDMA Base Station Controller Chapter 2 Route Data Configuration
Chapter 2 Route Data Configuration
2.1 Overview
2.1.1 Physical Connection
The network ports of the CMUXs in BSC service subracks connect with BAM through
the LAN Switch, as shown in Figure 2-1.
Straight network cables compliant with EIA/TIA 5688 standard are used. The loading
and O&M of all the subracks are implemented through the CMUX network ports.
RUN RUN
ALM ALM
ACT ACT
RESET RESET
LAN Switch TX TX
RX RX
ETH ETH
1PPS 1PPS
COM1 COM1
COM2 COM2
BAM
CMUX(CRPS) CMUX(CIPS)
Figure 2-1 The connection between BAM and CMUXs in service subracks
2.1.2 Setting of the Subrack DIP Switches
In the small-capacity BSC system, the subrack No. of the board should be carried in the
message when a board sends the BOOTP request to BAM. The DIP switch on the
backpanel of the service subrack determines the subrack No.
From left to right on the backpanel of each service subrack, there are DIP switches SD7
through SD0, which represent an 8-digit binary code from high order to low order. There
are two settings for each switch, of which "ON" stands for "0" and "OFF" for "1".
For example, the No. of subrack 5 can be converted into the binary code "00000101".
On the backpanel, set SD0 and SD2 to "OFF", and the rest to "ON". See Figure 2-2.
2-1
ON
OFF
SD7 SD6 SD5 SD4 SD3 SD2 SD1 SD0
Figure 2-2 DIP switches
Note:
The DIP switches upon delivery are set to all "ON" or all "OFF". Manual setting on site is necessary.
2.1.3 Configuration Procedures
The route data configuration includes two parts:

z The configuration of routes between BAM and boards.
z The configuration of routes between BAM and BTS.
Start
Configure the routes

between
BAMand boards
Configure the routes

between
BAMand BTSs
End
Figure 2-3 Procedures of route data configuration
2.2 Configuration of Routes between BAM and Boards

An example is used here to illustrate the configuration of system route data, as shown
in Figure 2-4.
z BAM IP address is 10.12.3.128 and the subnet mask is 255.255.0.0. There is no
need to set the gateway.
z BSC comprises 3 service subracks: CRPS (subrack 2), CIPS (Subrack 5) and
CIPS (Subrack 6).
z The O&M IP address of BTS 1 is 129.8.10.4. It is connected to CIPS 5.
z The O&M IP address of BTS 2 is 129.9.10.5. It is connected to CIPS 6.
2-2
Board network
CMUX address segment address
10.12.3.2 80.8.0.0
CRPS (In Subrack No.2)
80.20.0.0 BTS
10.12.3.5
10.12.3.128 129.8.10.4
CIPS (In Subrack No.5)
BAM 80.24.0.0 BTS

10.12.3.6
129.9.10.5
LAN CIPS (In Subrack No.6)
Figure 2-4 Route configuration
The network ports of the active and standby CMUXs in the service subracks are
connected to the BAM through the same LAN Switch. After the DIP switches are
properly set, the IP address of network port on the active CMUX consists of the first
three segments of the BAM IP address and the subrack No. That is, the IP address of
the CMUX network port in the subrack N is 10.12.3.N. The network port of the standby
CMUX does not get the IP address until the active-standby switchover occurs and it
becomes the active board.
To transmit the loading and O&M information to boards through the CMUX network port,
you should configure the routes between BAM and boards. In the BSC system, the
network segment address of boards in subrack N is usually set to 80.4×N.0.0, the
subnet mask to 255.252.0.0.
The system route data is configured through BAM as below:
1) Select [Start\Run…] in the BAM operating system.
2) Type the command CMD into the dialog box [Run] to display the command line
input window as shown in Figure 2-5.
3) Type the command to configure the route data.
2-3
Figure 2-5 Route data configuration interface
[Example]
1) Configure the route between BAM and boards of CPRS (subrack 2). The network
segment address of the board is 80.8.0.0. CMUX network port address is
10.12.3.2. The mask must be set to 255.252.0.0.
c:\>route -p add 80.8.0.0 mask 255.252.0.0 10.12.3.2
2) Configure the routes between BAM and boards of CIPSs (in subracks 5 and 6) one
by one.
c:\>route -p add 80.20.0.0 mask 255.252.0.0 10.12.3.5
c:\>route -p add 80.24.0.0 mask 255.252.0.0 10.12.3.6
3) After the configuration, execute the command route print to check the routes
configured.
c:\>route print
Active Routes:
Network Destination Netmask Gateway Interface Metric
80.8.0.0 255.252.0.0 10.12.3.2 10.12.3.128 1
80.20.0.0 255.252.0.0 10.12.3.5 10.12.3.128 1
80.24.0.0 255.252.0.0 10.12.3.6 10.12.3.128 1
The routes between BAM and subracks 2, 5 and 6 should be in the route list.
You can delete a route configured using the command route –p delete.
[Example]
Delete the route between subrack 5 and BAM.
c:\>route –p delete 80.20.0.0
2-4
Note:
When you use the command route -p add to add or route -p delete to delete the route data, the BAM
automatically saves the data configured. However, if you use the commands route add and route delete,
the data configured cannot be saved and needs reconfiguration after the BAM is restarted.
2.3 Configuration of Routes between BAM and BTSs

To transmit the loading and O&M information to BTS through the CMUX network port,
the routes between BAM and BTS O&M IP address must be configured.
Here, the example shown in Figure 2-4 is also used to explain the configuration of
routes between BAM and BTSs.
[Example]
z The O&M IP address of BTS1 is 129.8.10.4 and is connected to the CIPS in
subrack 5.
z The O&M IP address of BTS2 is 129.9.10.5 and is connected to the CIPS in
subrack 6.
To configure the routes betweem BAM and BTSs, perform the following operations.
1) Execute the following command in BAM to configure the route between BAM and
BTS 1. Set the network segment address of the BTS connecting with the CIPS in
subrack 5 to “129.8.0.0” and the mask to “255.255.0.0”.
c:\>route -p add 129.8.0.0 mask 255.255.0.0 10.12.3.5
2) Configure the route between BAM and BTS2 (connecting with the CIPS in subrack
6).
c:\>route -p add 129.9.0.0 mask 255.255.0.0 10.12.3.6
If there are multiple CIPSs, configure them one by one.

3) After the configuration, execute the command route print to check the routes
configured.
c:\>route print
Active Routes:
Network Destination Netmask Gateway Interface Metric
80.8.0.0 255.252.0.0 10.12.3.2 10.12.3.128 1
80.20.0.0 255.252.0.0 10.12.3.5 10.12.3.128 1
80.24.0.0 255.252.0.0 10.12.3.6 10.12.3.128 1
129.8.0.0 255.255.0.0 10.12.3.5 10.12.3.128 1
129.9.0.0 255.255.0.0 10.12.3.6 10.12.3.128 1
You can view the two routes between BAM and the BTSs in the route list.
2-5
Airbridge cBSC6600 CDMA Base Station Controller Chapter 3 Basic Information Configuration
Chapter 3 Basic Information Configuration
3.1 Overview
The BSC basic information configuration involves the configuration of the attributes of
BSC system parameters. These parameters are listed below.
z BSC IP address
z MSC ID
z Market ID
z Entity ID
z Mobile country code (MCC)
z Mobile network code (MNC)
z A-interface version No
Note:
The BSC basic information is the first to be configured using MML commands.
3.2 Configuration of BSC Basic Information

You can configure the BSC basic information using the command ADD BSCINF.
The following are related parameters.
z [BSC IP Address]: The BSC IP address identifies each BSC in the same MSC.
The MSC assigns the BSC IP addresses in a uniform way for inter-BSC soft
handoff.
z [BSC Subnet Mask]: The default configuration is “255.255.0.0”.
z [Market ID]: Market ID identifies the equipment made by different vendors. It is
assigned across the overall network and shall be consistent with that configured at
MSC.
z [Entity ID]: The Entity ID identifies different BSC entities in the network.
z [Mobile Country Code] and [Mobile Network Code]: They correspond to the first
five high-order digits, as shown in Figure 3-1. By default, they are set to “460” and
“3” respectively.
3-1
IMSI
MCC MNC MSIN
3digits 2digits 10digits
IMSI: International mobile subscriber identity

MCC: Mobile country code
MNC: Mobile network code
MSIN (MIN): Mobile subscriber identification number
Figure 3-1 IMSI
z [MSC ID]: It contains six hexadecimal digits and is provided by the MSC engineers.
An MSC ID comprises the market ID and the SWNO. The market ID is the first two
bytes of the MSC ID and the SWNO is the serial No. of the MSC, corresponding to
the last byte of the MSC ID.
z [A Interface Version No.]: This parameter is used to specify the protocol version of
the A-interface base station subsystem application part (BSSAP). It shall be
consistent with interface version at the MSC side.
z [Pilot PN Sequence Offset Index]: It is the PN increment for the whole BSC. By
default, it is “4”. A cell PN shall be a multiple of pilot PN increment. Otherwise, pilot
pollution alarm may be generated while networking.
z [Max. SDB]: By default, it is “80”.
z [SWF Type]: It is configured according to actual conditions. In a small-capacity
BSC, it is set to “SWT_E1T1 (E1/T1 SWF)”.
z [RFN CLK Board]: It is configured according to actual conditions. In a
small-capacity BSC, it is set to “GCKP (GCKP Board)”.
z [A5 Enable Selection]: Set it to “YES” when the system needs to support the circuit
data service and the IWF equipment is configured on the MSC. Otherwise, set it to
“NO”.
After completing the configuration, you can use the command LST BSCINF to query
BSC basic information.
You can use the command MOD BSCINF to modify BSC basic information, including
the market ID, entity ID, mobile country code, mobile network code, A interface version
No., A5 enable selection, and so on.
[Example]
Configure BSC basic information as follows:
z BSC IP Address is 129.11.17.1; Mask is 255.255.0.0.
z Market ID is 14001; Entity ID is 5.
z Mobile country code is 460; mobile network code is 3.
z MSC ID is 0x36b101; A Interface version No. is ISO4.1.
z Both pilot PN sequence offset index increment and Max. SDB adopt default values,
which are 4 and 80 respectively.
3-2
z The BSC is a small-capacity one and the A5 interface is not required. The clock
module uses GCKP board.
ADD BSCINF: BSCID="129.11.17.1", BSCSNM="255.255.0.0", MRKTID=14001, ENTID=5,
MSCID="0x36b101", APVER=IOS4.1, SWT=SWT_E1T1, RFNBRDCLK=GCKP,
A5ENABLEFLAG=NO;
[Relevant commands]
Table 3-1 shows the commands related to the configuration of BSC basic information.
Table 3-1 Commands related to configuration of BSC basic information
Operation Command
Add BSC Basic Information ADD BSCINF
Modify BSC Basic Information MOD BSCINF
Query BSC Basic Information LST BSCINF
3-3
Airbridge cBSC6600 CDMA Base Station Controller Chapter 4 Equipment Data Configuration
Chapter 4 Equipment Data Configuration
4.1 Overview
4.1.1 BSC Hardware System
I. System architecture
The BSC system comprises the following four functional modules (subrack level):
z CDMA integrated processing subrack (CIPS)
z CDMA resource & packet subrack (CRPS)
z Clock processing module (CLKM)
z CDMA integrated management system (CIMS)
Figure 4-1 shows the BSC system structure.
E1/T1 E1/T1
To/From BTS CIPS To/From MSC
E1/T1
GE/FE E1/T1
To/From PDSN CRPS To/From other BSC
FE
FE
FE FE
To/From NMS CIMS CLKM
Figure 4-1 BSC system structure
II. Hierarchical structure
The hardware of BSC system is of modular structure. The whole system can be divided
into 4 levels: BSC system, rack, subrack (module), and board, as shown in Figure 4-2.
Figure 4-3 shows the hardware configuration of a BSC with a capacity of 120,000
subscribers.
4-1
BSC system
Rack ... Rack
Subrack ... Subrack
Board ... Board
Figure 4-2 BSC hardware hierarchy
Power distribution box Power distribution box
CRPS CIPS
Cable trough Cable trough

Fan box Fan box
Air deflector Air deflector
LCD
LAN Switch
Cable trough
LAN Switch
Dummy panel CIPS
Keyboard
CLKM
Cable trough
Cable trough
BAM Server
Fan box
Air deflector Air deflector
CIPS CIPS
Cable trough Cable trough

Fan box Fan box
Dummy panel Dummy panel
Figure 4-3 BSC hardware configuration
The equipment data configuration involves the configuration of the following parts.
z BSC hardware system
z Subrack loading information
z Inter-subrack E1/T1 connection
4-2
z Inter-subrack soft handoff terrestrial link

z Module data
z Board parameters
Start
Configure
hardware
Configure subrack
loading info
Configure
inter-subrack
E1/T1 connection
Configure
inter-subrack
soft handoff
terrestrial link
Configure
module
Configure Board
parameter
End
Figure 4-4 Procedures of equipment data configuration
Note:
The procedure enclosed by the dotted block is optional. That is, it is subject to the actual application.
4.2 Configuration of Hardware

4.2.1 Adding Racks
As the biggest hardware units in BSC configuration, racks must be configured before
the subracks and boards.
You can add a rack using the command ADD RCK.
4-3
The Rack No., Rack Type, Rack Description and Location of the rack to be added
should be specified.
Note:
The Rack No. is determined according to the actual position of the rack.
[Example]
Add racks 1 and 2.
Rack Type: BSC Rack; Rack Description: "RACK1" and "RACK2"; Location: 2nd floor.
ADD RCK: RN=1, RT=BSC, RD="RCAK1", LOC="2nd floor";
[Relevant commands]
Table 4-1 shows the commands related to rack configuration.
Table 4-1 Commands related to rack configuration
Operation Command
Add a Rack ADD RCK

Remove a Rack RMV RCK
Modify Rack Information MOD RCK
Query Rack Information LST RCK
4.2.2 Adding Subracks
The small-capacity BSC supports two types of service processing subracks, namely
CRPS and CIPS.
You can add a subrack using the command ADD FRM.
z [Subrack No.], [Rack No.] and [Position in Rack]: Specify the position where the
subrack is added.
The No. of the subrack and the position information is configured according to
actual situation.
In the first rack, the top layer is usually loaded with the CRPS (subrack No.: 2), and
the middle layer is reserved for integrated management system. The CIPSs can
be installed in any other layers.
z [Typical Subrack]: Specifies the subrack to be configured.
4-4
For small-capacity BSC, you may select either CRPS or CIPS here.
z [Board Select]: Specifies the boards to be configured in the typical subrack added.
Figure 4-5and Figure 4-6 show the board configuration of CRPS and CIPS.
z Other parameters:
If CRPS is configured as the typical subrack, the IP address and subnet mask of
each CPPU in the CRPS should be specified.
If CIPS is configured as the typical subrack, the corresponding BTS gateway IP
address and subnet mask should be specified.
C C C C C C C C C C C C C C
B B R R P P H M M H B P P B
I P M M C C A U U A P P P I
E U U U U U C X X C U U U E
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Figure 4-5 Boards in CRPS
B F F F E E M M E E L S S A
I M M M V V U U V V A P P I
E R R R C C X X C C P U U E
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Figure 4-6 Boards in CIPS
[Example]
Add a CRPS. The boards configured in it are shown in Figure 4-5.
Subrack No.: 2; Rack No.: 1; Position in Rack: Top;
IP address of CPPU in slot 11: 129.11.17.30; Subnet Mask of CPPU slot 11:
255.255.0.0; IP address of CPPU in slot 12: 129.11.17.31; Subnet Mask of CPPU in
slot 12: 255.255.0.0.
4-5
ADD FRM: FN=2, RN=1, RP=UP, FT=CRPS_CBIE,

CRPSBIEBRD=CBIE_SN0&CBPU_SN1&CRMU_SN2&CRMU_SN3&CPCU_SN4&CPCU_SN5&CHAC_SN6&
CMUX_SN7&CMUX_SN8&CHAC_SN9&CBPU_SN10&CPPU_SN11&CPPU_SN12&CBIE_SN15,
SN11PPUIP="129.11.17.30", SN11PPUSNM="255.255.0.0",
SN12PPUIP="129.11.17.31", SN12PPUSNM="255.255.0.0";
Add a CIPS. The boards configured in it are shown in Figure 4-6.

Subrack No.: 5; Rack No.: 1; Position in Rack: Bottom;
BTS Gateway IP address: 129.8.10.2; BTS Gateway Subnet Mask: 255.255.0.0.
ADD FRM: FN=5, RN=1, RP=DWN, FT=CIPS_CBIECAIE,
CIPSBIEAIEBRD=CBIE_SN0&CFMR_SN1&CFMR_SN2&CFMR_SN3&CEVC_SN5&CEVC_SN6&CMUX_S
N7&CMUX_SN8&CEVC_SN9&CEVC_SN10&CLAP_SN11&CSPU_SN12&CSPU_SN13&CAIE_SN15,
BTSGWIP="129.8.10.2", BTSGWSNM="255.255.0.0";
Add a CIPS. Subrack No.: 6; Rack No.: 2; Position in Rack: Bottom;

Typical subrack: CIPS subrack with CAIE board;
BTS Gateway IP address: 129.9.10.2; BTS Gateway Subnet Mask: 255.255.0.0.
ADD FRM: FN=6, RN=2, RP=DWN, FT=CIPS_CBIECAIE,
CIPSBIEAIEBRD=CBIE_SN0&CFMR_SN1&CFMR_SN2&CEVC_SN6&CMUX_SN7&CMUX_SN8&CEVC_S
N9&CEVC_SN10&CLAP_SN11&CSPU_SN12&CSPU_SN13&CAIE_SN15, BTSGWIP="129.9.10.2",
BTSGWSNM="255.255.0.0";
[Relevant commands]
Table 4-2 shows the commands related to subrack configuration.
Table 4-2 Commands related to subrack configuration
Operation Command
Add a Subrack ADD FRM

Remove a Subrack RMV FRM
Query Subrack Information LST FRM
4.2.3 Adding Boards
Normally, the boards in a subrack are configured at the same time as the subrack is
configured. If a board needs to be added after the configuration of the subrack, you can
use the command ADD BRD. When a board is added, the [Subrack No.], [Slot No.] and
[Board Type] of the board should be specified.
4-6
[Example]
Add a CFMR in slot 3 of CIPS 6.
ADD BRD: FN=6, SN=3, BTP=CFMR;
[Relevant commands]
Table 4-3 shows the commands related to board configuration.
Table 4-3 Command related to board configuration
Operation Command
Add a Board ADD BRD

Remove a Board RMV BRD
Query Board Information LST BRD
4.3 Configuration of Subrack Loading Information

In the small-capacity BSC, the CMUX network port in each service processing subrack
is connected to the BAM through LAN Switch, serving as the data loading path.
You can use the command ADD FRMPRTMAP to configure BOOTP and loading
information of the service processing subracks.
Since the system is of small capacity, the CSWS is not used. The parameter [SWF
Type] should be set to "SWT_E1T1".
[Example]
Configure the loading information for CRPS 2, CIPS 5 and CIPS 6.
ADD FRMPRTMAP: SWT=SWT_E1T1, FN=2;
[Relevant commands]
Table 4-4 shows the commands related to the configuration of subrack loading
information.
Table 4-4 Commands related to the configuration of subrack loading information
Operation Command
Add Subrack Optical Port ADD FRMPRTMAP

Remove Subrack Optical Port RMV FRMPRTMAP
Query Subrack Optical Port LST FRMPRTMAP
4-7
4.4 Configuration of Inter-subrack E1/T1 Connection

In the small-capacity BSC, the CRPS needs to connect to each CIPS through the E1/T1
provided by the CDMA BSC interface equipment (CBIE) or the CDMA general (X)
interface equipment (CXIE). The purpose is to implement the inter-subrack permanent
virtual connection (PVC) and the operation and maintenance of the routes.
Each CXIE provides 24 E1s/T1s. The E1s/T1s are distributed to three ports (with eight
E1s/T1s at each port), numbered 0, 1 and 2 from the bottom up. The three ports
correspond to three IMA chips. The following lists the correspondence between the port
No., E1/T1 No. and the IMA group No..
Table 4-5 Correspondence between port No., E1 No. and IMA group No.
Port No. E1/T1 No. IMA group No.
0 0-7 0-3
1 8-15 4-7
2 16-23 8-11
RUN
ALM
ACT
No.2 port IMA group No.: 8-11

No.16-23 E1s/T1s
E1/T1
No.1 port IMA group No.: 4-7

No.8-15 E1s/T1s
E1/T1
IMA group No.: 0-3

No.0 port
No.0-7 E1s/T1s
E1/T1
CLK1
CLK2
Figure 4-7 E1/T1 ports on CXIE
Each CIXE provides thirty-two E1s/T1s, which are allocated into four ports (eight
E1s/T1s for each port), numbered 0, 1, 2, and 3 from the bottom up. The CBIE can be
configured with IMA groups numbered from 0 to 31, and the correspondence between
the IMA group and the E1/T1 port is not restricted like the CXIE.
4-8
The CBIE/CXIEs in the CRPS are permanently configured in slot 0 and slot 15. The
E1/T1 ports can be used as the CRPS-CIPS interworking channel or as the A3/A7
interface
The CBIE/CXIEs in the CIPS are permanently configured in the slot 0. The E1/T1 ports
can be used as the CRPS-CIPS interworking channel or as the Abis interface
The configuration of inter-subrack E1/T1 connection comprises two parts:
z Adding IMA group and link
z Adding inter-subrack E1/T1 connection
4.4.1 Adding IMA Group and Link
The IMA technology allows the even distribution of a high-speed ATM cell flow to one or
more E1/T1 links for transmission; hence, the dynamic expansion of bandwidth can be
realized.
Figure 4-8 shows how IMA works. On the transmitting end, the high-speed ATM cell
flow on one transmission link is inversely multiplexed to several low-speed links for
transmission. On the receiving end, the cell flows transmitted from these low-speed
links are tuned into the original high-speed ATM cell flow.
IMA group Low-speed physical link IMA group

PHY PHY
Low-speed physical link

PHY PHY
Single ATM cell flow
Original ATM cell flow
(from ATM layer)
(to ATM layer)
Low-speed physical link
PHY PHY
Transmitting direction: cyclically distribute the cell flow into the low-speed physical links.
Receiving direction: combine the cells from the low-speed physical links into a single cell flow.
Figure 4-8 Multiplexing and de-multiplexing of IMA group
IMA-related data is configured on CBIE/CXIE.

z IMA group: The link set at a certain end when IMA connection is set up, that is, a
group of links serves as a physical interface.
z IMA link: An IMA link corresponds to a unidirectional logical channel.
You can use the command ADD IMAGRP to add IMA group and IMA link to CBIE/CXIE
for inter-subrack connection.
The following are parameters involved.
z [Subrack No.] and [Slot No.]: Subrack No. and slot No. of the CBIE/CXIE, where
the IMA group is to be added.
z [Board Type]: Select the CBIE or the CXIE according to the actual configuration of
boards in the subrack.
4-9
z [IMA Group No.] and [E1/T1 No. List]: No. of the IMA group and the E1/T1 Nos
corresponding to the IMA links in an IMA group.
To ensure enough bandwidth for inter-subrack service, it is suggested that eight
E1s/T1s be configured in the IMA group.
z [Min. Number of Activated Links]: Minimum number of activated links.
It cannot be greater than the number of links configured in the IMA group.
[Example]
Add an IMA group respectively to CBIEs in slots 0 and 15 of CRPS 2.
IMA Group No.: 0; E1 No. List: 0 to 7.
ADD IMAGRP: FN=2, SN=SN0, BTP=CBIE, BIEIMAGN=0, BIEE1LST="0,1,2,3,4,5,6,7",
MINTXLNK=8, BIETXCLKMD=CTC, TXFRMLEN=L128, IMAVER=VER11;
ADD IMAGRP: FN=2, SN=SN15, BTP=CBIE, BIEIMAGN=0, BIEE1LST="0,1,2,3,4,5,6,7",
MINTXLNK=8, BIETXCLKMD=CTC, TXFRMLEN=L128, IMAVER=VER11;
Add an IMA group to port 3 of CBIE in slot 0 of CIPS 5.

ADD IMAGRP: FN=5, SN=SN0, BTP=CBIE, BIEIMAGN=31,
BIEE1LST="24,25,26,27,28,29,30,31", MINTXLNK=8, BIETXCLKMD=CTC,
TXFRMLEN=L128, IMAVER=VER11;
Add an IMA group to port 3 of CBIE in slot 0 of CIPS 6.

ADD IMAGRP: FN=6, SN=SN0, BTP=CBIE, BIEIMAGN=31,
BIEE1LST="24,25,26,27,28,29,30,31", MINTXLNK=8, BIETXCLKMD=CTC,
TXFRMLEN=L128, IMAVER=VER11;
[Relevant commands]
Table 4-6 shows the commands related to the configuration of IMA group and IMA link.
Table 4-6 Command related to configuration of IMA group and link
Operation Command
Add IMA Group And Link ADD IMAGRP

Remove IMA Group And Link RMV IMAGRP
Query IMA Group LST IMAGRP
4-10
4.4.2 Adding Inter-subrack E1/T1 Connection
After IMA group is configured, you can add the E1/T1 connection between subracks
using the command ADD INTERFRM.
z [Source Subrack No.] and [Source Slot No.]: The former is the No. of the CIPS
used for inter-subrack connection, and the latter is the slot No. of the CBIE/CXIE in
the subrack.
z [Source IMA Group No.]: No. of the IMA group configured to the CBIE/CXIE in
CIPS.
z [Destination Subrack No.] and [Destination Slot No.]: The former is the No. of the
CRPS, and the latter is the slot No. of the CBIE/CXIE in the subrack. The
[Destination subrack No.] may not be specified.
z [Destination IMA Group No.]: No. of the IMA group configured to the CBIE/CXIE in
CRPS.
[Example]
Add E1 connection between CRPS 2 and CIPS 5.
CIPS CBIE Slot No.: 0; CIPS IMA Group No.: 31; CRPS CBIE Slot No.: 0; CRPS IMA
Group No: 0.
ADD INTERFRM: SRCFN=5, SRCSN=SN0, SRCIMAGN=31, DESFN=2, DESSN=SN0,
DESIMAGN=0;
Add E1 connection between CRPS 2 and CIPS 6.

CIPS CBIE Slot No.: 0; CIPS IMA Group No.: 31; CRPS CBIE Slot No.: 15; CRPS IMA
Group No: 0.
ADD INTERFRM: SRCFN=6, SRCSN=SN0, SRCIMAGN=31, DESFN=2, DESSN=SN15,
DESIMAGN=0;
[Relevant commands]
Table 4-7 shows the commands related to the configuration of inter-subrack E1/T1
connection.
Table 4-7 Commands related to configuration of inter-subrack E1/T1 connection
Operation Command
Add Inter-Subrack E1/T1 Connection ADD INTERFRM

Remove Inter-Subrack E1/T1 Connection RMV INTERFRM
Query Inter-Subrack E1/T1 Connection LST INTERFRM
4-11
4.5 Configuration of Inter-subrack SHO Terrestrial Link

The configuration of soft handoff terrestrial link comprises the following two parts:
z Configuration of the links for BSC inter-subrack soft handoff.
z Configuration of A3/A7 links for inter-BSC soft handoff.
This section details the configuration of the links for BSC Inter-subrack soft handoff.
In a MS soft handoff, signals of several branches are sent through different BTSs to
CFMR in CIPS for processing. If the connected BTSs belong to different CIPSs, the soft
handoff terrestrial links between CIPSs should be configured, that is, an ALAAL2 link
should be added between the CBIE/CXIE and the CFMR in the neighboring CIPS, as
shown in Figure 4-9.
C C
F B Abis
M I BTS2
R E
CIPS
AL AAL2 Link
MS
C C
F B Abis
M I BTS1
R E
CIPS
BSC
Figure 4-9 AL AAL2 link between CBIE and the CFMR in neighboring CIPS
You can add the soft handoff terrestrial link between CIPSs using the command ADD
SHOLINK.
z [Link Type]: It should be set to "IBSC (INTER-SUBRACK SOFT HO LINK IN
BSC)".
z [Subrack No.] and [Adjacent Subrack No.]: No. of the two CIPSs, where the soft
handoff terrestrial link is configured. The neighboring relation is bi-directional.
z [Bandwidth]: It should be configured according to the actual traffic. The default
value is BW1.0 M (1.0 M).
Note:
In the configuration of small-capacity BSC, use the command ADD INTERFRM to configure the
Inter-subrack E1/T1 connection before the inter-subrack soft handoff terrestrial link is configured.
4-12
[Example]
Configure soft handoff link between CIPS 5 and CIPS 6.
ADD SHOLINK: HOLNKTP=IBSC, FN=5, NBRFN=6, BANDWIDTH=BW1.0M;
[Relevant commands]
Table 4-8 shows the commands related to the configuration of inter-subrack soft
handoff terrestrial link.
Table 4-8 Commands related to configuration of inter-subrack soft handoff terrestrial link
Operation Command
Add Soft Handoff Terrestrial Link ADD SHOLINK

Remove Soft Handoff Terrestrial Link RMV SHOLINK
Query Soft Handoff Terrestrial Link LST SHOLINK
4.6 Configuration of Module

Module configuration is to add the logical module attributes to a physical subrack,
including the module No., protocol version, band class and the allocation of module
channel element (CE) resource. The physical subrack must be CIPS, and the CIPS and
the module configured are in one-to-one correspondence.
Execute the command ADD MDU to add module attributes to a CIPS.
z [Subrack No.]: No. of the CIPS to be added with module attributes.
z [Module No.]: Starting from 0, the module No. is in one-to-one correspondence
with the subrack No.
z [Protocol Version] and [Min. Protocol Version]: According to band class and actual
situation, different systems can be configured with different protocol version and
minimum protocol version to prevent the access of the MS not supported by the
BSC.
z [Bandclass]: Type of the band class supported by the module.
After the configuration, you can use the command MOD PREV to modify the BTS
protocol version and the minimum protocol version of the module.
[Example]
Configure the CIPS 5 to be module 0. The protocol version and minimum protocol
version are 6 and 2 respectively, and the bandclass is 800 MHz.
ADD MDU: FN=5, MN=0, PREV=6, MINPREV=2, BNDCLS=BC800;
4-13
Configure the CIPS 6 to be module 1. The protocol version and minimum protocol
version are 6 and 2 respectively and the bandclass is 800 MHz.
[Relevant commands]
Table 4-9 shows the commands related to adding module.
Table 4-9 Commands related to adding module
Operation Command
Add a Module ADD MDU

Remove a Module RMV MDU
Query Module Information LST MDU
Modify BTS Protocol Revision Level MOD PREV
4.7 Configuration of Board Parameters

The configuration of BSC board parameters covers the board common configuration,
and the configuration of CEVC, CAIE and CFMR. This section describes some popular
configurations.
4.7.1 Modifying Loading Control Mode
In BSC system, each time when a board restarts, the data such as Host program, patch
program, data files and digital signal processor (DSP) program are loaded. Most
boards need only the Host program and patch program. But CMUX, CRMU, CSPU and
CPCU, also need the data files. CFMR and CEVC also need the DSP program.
You can use the command MOD LODCM to modify the board loading parameters.
Parameters such as [Subrack No.], [Slot No.] and [Board Type] should be specified.
The loading control modes for the program/data files include:
z BNTFLSH: The programs/data files are loaded from BAM and cannot be written to
the flash memory of the board.
z BTFLSH: The programs/data files are loaded from BAM and are written to the
board flash memory. It takes time to write them into the flash memory.
z FLSH: The board program/data files are loaded directly from the flash memory. It
takes little time.
If the board is loaded for the first time, it is suggested that the Host program loading
control mode be set to "BTFLSH (LOAD FROM BAM AND WRITE TO FLASH)", and
the data program loading control mode be set to "BNTFLSH (LOAD FROM BAM AND
NOT WRITE TO FLASH)".
4-14
Three days after the system is in stable operation, you may execute the command
MOD LODCM to modify the Host program loading control mode to be "FLSH (LOAD
FROM FLASH)”; thus, the board can restart promptly after being reset.
[Example]
Modify the loading control mode of CMUX in slot 7 of CRPS 2.
Change the Host program loading control mode to "LOAD FROM BAM AND WRITE
TO FLASH".
MOD LODCM: BTP=CMUX, FN=2, SN=7, BINLCM=BTFLSH;
[Relevant commands]
Table 4-10 shows the commands related to the configuration of loading control mode.
Table 4-10 Commands related to configuration of loading control mode
Operation Command
Modify Loading Control Mode MOD LODCM

Query Loading Control Mode LST LODCM
4.7.2 Modifying Subsystem Parameters
The modification of subsystem parameters involves the modification of the CPU

occupancy alarm threshold and recovery threshold for the subsystem. For CFMR and
CEVC, it also involves the modification of the DSP occupancy alarm threshold and
recovery threshold.
Note:
Normally, default values are recommended for the subsystem information of board. The default CPU
occupancy recovery threshold and DSP occupancy recovery threshold are 60 and the default alarm
thresholds for CPU and DSP occupancy are 80.
You can use the command MOD SUBSYS to modify the subsystem parameters of
board. The Subrack No., Slot No. and Board Type of the board should be specified.
For the boards such as CMUX, CSPU, CRMU and CPCU, the parameters of the active
and the standby boards should be modified at the same time, therefore, the Slot No.
need not be specified.
[Example]
Modify the subsystem information of the CMUX in CRPS 2 as below:
CPU occupancy recovery threshold: 55; CPU occupancy alarm threshold: 80.
4-15
MOD SUBSYS: FN=2, BTP=CMUX, CPURCVTHD=55, CPUALMTHD=80;
[Relevant commands]
Table 4-11 shows the commands related to the configuration of subsystem parameters.
Table 4-11 Commands related to subsystem parameter configuration
Operation Command
Modify Subsystem Parameters MOD SUBSYS

Query Subsystem Parameters LST SUBSYS
4-16
Airbridge cBSC6600 CDMA Base Station Controller Chapter 5 Clock System Configuration
Chapter 5 Clock System Configuration
5.1 Overview
5.1.1 Introduction to Clock System
In CDMA system, the frame No. on the air interface must be synchronous with the
satellite synchronization time. Therefore, the BSC is required to ensure both the
transmission clock synchronization and the time synchronization. The clock system is
responsible for the transmission synchronization and time synchronization of the whole
BSC.
I. Transmission synchronization
For transmission synchronization, two clock reference sources are available:

z Building integrated timing supply system (BITS) clock
z Line clock extracted from A-interface.
Being of higher priority, the BITS clock reference source should be used if it is available.
If it is unavailable, the CAIE extracts the 2 MHz line clock from A-interface, and sends it
to the GCKP in CLKM for processing through the cable. In this way, the synchronization
between BSC and MSC can be ensured.
If A-interface is configured with CSTU, the CSTU will be responsible for the line clock
extraction.
The line clock signal is extracted and transmitted as below.
The line clock signal extracted from CAIE/CSTU is sent to GCKP for phase-lock
processing.
And then, the 8 kHz BSC system clock therein generated is sent to the CMUX in CRPS,
which further distributes the clock signal to CBIEs/CXIEs in the same subrack.
Finally, the CBIEs/CXIEs in CRPS send the system clock signal through E1/T1 port to
the CBIE/CXIE in each CIPS, and then the CBIE/CXIE transfers the clock signal to
CMUX.
If the line clock reference source is selected as the system clock, the active and
standby lines used to extract the line clock must be from different CAIEs/CSTUs. If
possible, use the CAIEs/CSTUs in different CIPSs to extract the line clock.
II. Time synchronization
The time synchronization of BSC is realized through the satellite synchronization time
information received by the CLKM (configured with GCKP).
5-1
From the signals received by GPS/GLONASS antenna, the CLKM extracts the 1PPS
and the absolute time information and exports PP16S and absolute time information to
the CRPS CMUX after internal processing. The CMUX then generates a periodic
synchronization cell every other 320 ms, and broadcasts it through the CBIE/CXIE in
the same subrack to the CMUX in each CIPS.
Figure 5-1 shows the physical connection of the BSC clock system (extracting clock
from A-interface by CAIE).
GCKP1 GCKP2
RUN ALM ACT COM IN0 IN1 OUT ANT RUN ALM ACT COM IN0 IN1 OUT ANT
CLK_B COM_B ETH_B CLK_A COM_A ETH_A

GCKB
RUN RUN RUN RUN
ALM ALM ALM ALM

ACT ACT ACT ACT
RESET RESET
E1/T1 E1/T1
TX TX
RX RX
E1/T1 E1/T1
E1/T1 ETH ETH E1/T1
1PPS 1PPS
COM1 COM1
E1/T1 E1/T1
COM2 COM2
CLK1 CLK1
CLK2 CLK2
CAIE 7#CMUX(CRPS) 8#CMUX(CRPS) CAIE
Figure 5-1 Physical connection of BSC clock system
The physical connection of the clock system comprises three parts.

z Part 1: Connecting the ports IN 0 and IN 1 on GCKP with the CLK 1 of the active
and standby CAIEs/CSTUs.
Through the line, the 2 MHz line clock extracted by CAIE/CSTU is sent to GCKP
and serves as the reference clock source for BSC transmission synchronization.
The ports IN 0 and IN 1 on GCKP can also be connected to the BITS clock
reference source directly.
5-2
z Part 2: Connecting the 1PPS ports on the active and standby CMUXs in CRPS
with the ports CLK_A and CLK_B on GCKB.
The PP16S and the 8 kHz system clock output by GCKB are received through the
line connected.
z Part 3: Connecting the ports COM 1 on the active and standby CMUXs in CRPS
with the ports COM_A and COM_B on GCKB.
The absolute time information exported by GCKB is transferred through the line
connected.
The configuration of BSC clock system involves two parts.

z The configuration of transmission synchronization.
z The configuration of time synchronization.
The configuration of time synchronization involves two parts.
z The configuration of the CRPS CMUX, which extracts absolute time information
from the PP16S signal.
z The configuration of the multicast PVC, through which the CRPS broadcasts the
periodic synchronous cell to each CIPS.
The configuration of time synchronization is accomplished by the system automatically.
Therefore, you only need to configure the transmission synchronization of the clock
system. Figure 5-2 shows the configuration procedures.
5-3
Start
Configure GCKP
Configure CAIE
Configure
CRPS CMUX
Configure CRPS
CBIE/CXIE
Configure CIPS
CBIE/CXIE
Configure
CIPS CMUX
End
Figure 5-2 Procedures of clock system configuration
5.2 Configuration of GCKP

GCKP has clock sources with at most four priorities (from 0 to 3). Wherein, priorities 1
to 3 can be designated through commands, priority 0 is the clock source reserved for
the system. The GCKP can select a clock source based on the configured internal clock
reference source table.
When the BSC system transmission clock is required to synchronize with A interface
clock, you must configure the clock reference sources according to Table 5-1 (When
the standby A interface clock does not exist, you can skip the configuration.)
Table 5-1 Clock reference source table 1
Priority Reference source type

3 Active A interface clock source (connects to GCKP IN0 port)
2 Standby A interface clock source (connects to GCKP IN1 port)
1 (GPS clock)
0 FREE-RUNNING
5-4
When the BSC system transmission clock is required to synchronize with BITS clock,
you must configure the clock reference sources according to Table 5-2 (When the
standby BITS clock does not exist, you can skip the configuration.)

3 Active BITS clock source (connects to GCKP IN0 port)
2 Standby BITS clock source (connects to GCKP IN1 port)
1 GPS clock
0 FREE-RUNNING
GCKP selects the clock reference source based on the clock reference source table
and clock source switchover strategies. There are two switchover strategies available,
namely, auto switchover strategy and manual switchover strategy.
z Auto-switchover strategy: GCKP selects the clock source with highest priority
based on clock reference source table at priority. When the reference source with
the highest priority fails, the GCKP will search and switch over to the one with the
highest priority among the rest sources in the table. When the clock source with
the highest priority recovers, the GKCP will switch over to this source
automatically.
z Manual switchover strategy: Select a certain item in the clock reference source
table to be the system clock source using commands. The manual switchover
strategy only functions as the supplement to the auto-switchover strategy. It is
generally not recommended.
GCKP adopts auto-switchover strategy by default. If necessary, use the command
MOD GCKPPARA to modify the switchover strategy of clock source.
To add a piece of clock source record to the clock reference source table, use the
command ADD CLKSRC. parameters in the command are explained as follows:
z [Slot No.]: Slot No. where GCKP resides.
z [Clock source priority]: Priority of the clock source to be added in the clock
reference source table. The priority level ranges from 1 to 3. Level 1 is the lowest
while level 3 is the highest.
z [Clock source type]: The type of the clock source to be added. There are six clock
source types in total.
[Example]
Based on Table 5-1, configure the GCKPs in Slot 0 and Slot 1 to extract 2M clocks from
active/standby A interface clock sources respectively.
ADD CLKSRC: SN=SN0, CLKPRI=3, CLKTYP=SMB02M;
5-5
ADD CLKSRC: SN=SN0, CLKPRI=1, CLKTYP=GPS1PPS;

[Relevant commands]
Table 5-3 shows the commands related to configuration of the GCKP clock source.
Table 5-3 Commands related to configuration of the GCKP clock source
Operation Commands
Add Clock Source ADD CLKSRC
Modify Clock Source MOD CLKSRC
Remove Clock Source RMV CLKSRC
Query Clock Source LST CLKSRC
Modify GCKP Operation Parameters MOD GCKPPARA
Query GCKP Operation Parameters LST GCKPPARA
5.3 Configuration of CAIE

For the transmission synchronization of the clock system, if the BSS uses the BITS
clock, it is not necessary to configure the CAIE. This configuration is also unnecessary
when the BSS uses the line clock retrieved by the CSTU from the A-interface, because
the CLK port on the CSTU exports the 2 MHz clock extracted from the optical interface
by default.
Therefore, the following contents detail how to configure the CAIE so that it can extract
the A-interface line clock properly.
You can use the command MOD BRDPARA to configure CAIE. The [Subrack No.] of
the CAIE should be specified. The [Board Type] should be set to "CAIE". Other
parameters should be set as below.
z [Slot No.]: No. of the slot where the CAIE is located.
z [CAIE Clock Source]: 0 (It depends on the configuration of the E1/T1 timeslot
between BSC and MSC).
z [Panel 2M Line Extracting Clock Control]: YES (EXTRACT).
z [TDM8k clock is output to backpanel]: NO (NOT OUTPUT).
[Example]
Set the CAIEs in slot 15 of CIPSs 5 and 6 to extract the line clock.
MOD BRDPARA: FN=5, BTP=CAIE, SN=15, AIECLK=0, MAIN2M=YES, TDM8K=NO;
5-6
[Relevant commands]
Table 5-4 shows the commands related to CAIE configuration.
Table 5-4 Commands related to CAIE configuration
Operation Command
Modify Board Parameters MOD BRDPARA
Query Board Parameters LST BRDPARA
5.4 Configuration of CRPS CMUX

For the transmission synchronization of clock system, the CMUX in CRPS receives
8 kHz system clock from GCKB through 1PPS port. Therefore, the clock reference
source of the CMUX should be extracted from the panel.
You can use the command MOD BRDPARA to set CMUX parameters. The Subrack No.
of the CMUX should be specified. The Board Type should be set to "CMUX" and the
Clock Source Selection to "CKTP5".
[Example]
Configure the clock reference source of CMUX in CRPS 2 to be the 8 kHz clock
reference source provided by GCKB.
MOD BRDPARA: FN=2, BTP=CMUX, CKTP=CKTP5;
[Relevant commands]
Table 5-5 shows the commands related to CMUX configuration.
Table 5-5 Commands related to CMUX configuration
Operation Command
5.5 Configuration of CRPS CBIE/CXIE

The clock reference source for the CBIE/CXIE should be set as the backpanel clock
because the CBIEs/CXIEs in CRPS receive the 8 kHz system clock from the backpanel
for transmission synchronization.
You can use the command MOD BRDPARA to configure the CBIEs/CXIEs in CRPS.
The parameters to be specified include Subrack No., Slot No., and Board Type.
The Board Type should be set to “CBIE” or "CXIE”, and the other parameters should be
set as below:
5-7
z [CBIE Clock Source]/[CXIE Clock Source]: 0.

z [Panel 2M Line Extracting Clock Control]: NO (it indicates no extraction).
z [TDM8k Clock is Output to Backpanel]: NO (it indicates no output).
z [IMA Clock Source Selection]: CPLD_IMA_CLK_BACK_BRD (BACKPANEL
CLOCK).
[Example]
Configure the backpanel clock as the clock reference source for the CBIEs/CXIEs (in
slot 0 and slot 15 of subrack 2) in CRPS, that is, the 8 kHz clock reference from the
backpanel.
MOD BRDPARA: FN=2, BTP=CBIE, SN=0, BIECLK=0, MAIN2M=NO, TDM8K=NO,
IMACKTP=CPLD_IMA_CLK_BACK_BRD;
MOD BRDPARA: FN=2, BTP=CBIE, SN=15, BIECLK=0, MAIN2M=NO, TDM8K=NO,
[Relevant commands]
Table 5-6 shows the commands related to CBIE/CXIE configuration.
Table 5-6 Commands related to CBIE/CXIE configuration
Operation Command
5.6 Configuration of CIPS CBIE/CXIE

The CBIE/CXIE in each CIPS needs to extract the 8 kHz system clock from the
E1s/T1s connected to the CRPS to realize the transmission synchronization of the
clock system.
You can use the command MOD BRDPARA to configure the CBIE/CXIE parameters in
each CIPS. The Subrack No. and Slot No. of the CXIE should be specified. The Board
Type should be set to “CBIE” or "CXIE". Other parameters should be set as below.
z [CBIE Clock Source]/[CXIE Clock Source]: The E1/T1 port used for the
inter-subrack connection. If the E1s/T1s 16-23 are used for the inter-subrack
connection, set this parameter to 16.
z [Panel 2M Line Extracting Clock Control]: NO (NOT EXTRACT).
z [TDM8k clock is output to backpanel]: YES (OUTPUT).
z [IMA Clock Source Selection]: CPLD_IMA_CLK_BACK_BRD (BACKPANEL
CLOCK).
[Example]
Set the CBIEs in CIPS 5 and CIPS 6 to obtain the 8 kHz system clock from the E1 link
connected to CRPS.
5-8
MOD BRDPARA: FN=5, BTP=CBIE, SN=0, BIECLK=16, MAIN2M=NO, TDM8K=YES,

MOD BRDPARA: FN=6, BTP=CBIE, SN=0, BIECLK=16, MAIN2M=NO, TDM8K=YES,
[Relevant commands]
Table 5-7 shows the commands related to CBIE configuration.
Table 5-7 Commands related to CBIE configuration
Operation Command
5.7 Configuration of CIPS CMUX

After receiving the 8 kHz system clock from the E1/T1 link connected to CRPS, the
CBIE/CXIE in each CIPS sends the clock signal to the CMUX in the same subrack
through 8 kHz bus on the backpanel. After the phase-locking at the CMUX, the system
clock is distributed to all boards in the subrack as the working clock.
You can use the command MOD BRDPARA to set the parameters of CMUX in each
CIPS. The Subrack No. of the CMUX should be specified. The Board Type should be
set to "CMUX" and Clock Source Selection to "CKTP4".
[Example]
Set the clock reference source of the CMUXs in CIPS 5 and CIPS 6 as the TDM clock
reference source.
[Relevant commands]
Table 5-8 shows the commands related to CMUX parameter configuration.
Table 5-8 Command related to CMUX configuration
Operation Command
5-9
Airbridge cBSC6600 CDMA Base Station Controller Chapter 6 A1/A2 Interface Configuration
Chapter 6 A1/A2 Interface Configuration
6.1 Overview
6.1.1 A1/A2 Interface Protocol Stack
A1/A2 interface is the logical interface between BSC and MSC.

A1 interface is used to transfer the signaling for call control and mobility management
(MM) between BSC and MSC. Figure 6-1 shows its protocol stack.
A2 interface carries the subscriber traffic between BSC and MSC. Figure 6-2 shows its
protocol stack.
BSSAP
SCCP
MTP
Physical Layer
BSSAP: Base station subsystem application part

SCCP: Signaling connection control part
MTP: Message transfer part
Figure 6-1 A1 interface protocol stack
64kbit/s PCM
Ds0
DS0:Digital signal level 0
6.1.2 Physical Equipment
The CAIE/CSTU of BSC provides the A1/A2 interface. Table 6-1 shows the features of
CAIE/CSTU. This chapter mainly introduces A1/A2 interface configuration of the CAIE.
Table 6-1 Features of A1/A2 interface board
Board Function
Each CAIE provides 32 E1/T1 trunks and 960 A-interface circuits to set up the A1/A2
CAIE
interface between BSC and MSC.
Each CSTU provides 63 E1/T1 trunks and multiplexes pulse code modulation (PCM)
CSTU circuits to SDH STM-1 optical fiber for transmission and uses them to set up A1/A2
interface between BSC and MSC.
6-1
The A1/A2 interface configuration includes five parts.

Start
Configure DSP
Configure OSP
Configure
SS7 standard
Configure
trunk circuit
Configure
MTP link
End
Figure 6-3 Procedures of A1/A2 interface configuration
6.2 Configuration of DSP

The MTP is responsible for reliable message transfer between BSC and MSC, which
requires configuring OSP (originating signaling point) and DSP (Digital Signal
Processor).
You can add a DSP using the command ADD N7DPC.
The following describes the parameters in this command.
z [Network Indicator]: The signaling network where DSP resides. Its configuration
should be consistent with that on the MSC.
z [SPC Code Digits]: The signaling point code digits of the signaling network where
DSP resides. Its configuration should be consistent with that on the MSC.
z [DPC Code]: The signaling point code of the MSC. Its configuration should be
consistent with that on the MSC.
z [DSP Name]: The DSP name that identifies and describes a DSP.
6-2
Note:
z Hexadecimal coding is adopted for the BSC. If the MSC signaling point uses the decimal coding,
conversion should be conducted.
z You can configure only one DSP.
[Example]
Add a DSP (MSC). It adopts the 24-digit national standby code and the SPC is
"0xC001".
ADD N7DPCOL: NI=NAT2C, SPCLEN=BIT24, DPC="0xC001", DPNM="MSC";
[Relevant commands]
Table 6-2 shows the commands related to configuration of DSP.
Table 6-2 Commands related to the configuration of DSP
Operation Command
Add a DSP ADD N7DPC
Query DSP Information LST N7DPC
Query DSP Status DSP N7DPC
Inhibit DSP INH N7DPC
Enable DSP UNI N7DPC
6.3 Configuration of OSP

As one of the signaling points on the mobile network, the BSC has its own signaling
point code. The signaling point features of the BSC can be set through the
configuration of OSP.
The concept of virtual multi-signaling point is introduced to the BSC. That is, one
physical node is logically divided into multiple signaling points, each of which can
connect with other signaling points independently.
The protocol originally stipulates that there can be sixteen signaling links at most
between two network nodes. The multi-signaling point function breaks this restriction.
With multiple signaling points corresponding to the same DSP, the number of signaling
links increases.
Configuration of OSP includes two parts:
z Adding relationship between module and signaling point
z Adding originating signaling point (OSP)
6-3
6.3.1 Adding Relationship between Module and Signaling Point
In the BSC, each module corresponds to a CIPS/CBMS. Each module must be

allocated with an OSP. And one OSP can support multiple modules.
You can add the relationship between module and signaling point using the command
ADD MDUOPC.
z [Module No.]: The module No. shall have been configured in the system.
z [Original Signaling Point Code]: In the system planning, each BSC module is
assigned with a hexadecimal OSP code. The length of the SPC should be
consistent with that of DSP.
[Example]
Add signaling point code 0xB001 to module 0.
Add signaling point code 0xB002 to module 1.
ADD MDUOPC: MN=0, OPC="0xB001";
ADD MDUOPC: MN=1, OPC="0xB002";
[Relevant commands]
Table 6-3 shows the commands related to the configuration of the relationship between
module and signaling point.
Table 6-3 Commands related to configuration of the relationship between module and signaling point
Operation Command
Add Relationship between Module and Signaling Point ADD MDUOPC
Remove Relationship between Module and Signaling Point RMV MDUOPC
Query Correspondence between Subrack and SP LST FRMSPC
6.3.2 Adding Originating Signaling Point
Note:
Before adding an OSP, configure the relationship between module and signaling point first. Otherwise, the
system prompts error message.
After the relationship between module and signaling point is added, it is required to add
the OSP and relevant attributes of signaling connection control part (SCCP) subsystem
for the module.
6-4
In the hierarchical structure of SS7, SCCP belongs to the No.4 functional group,
providing supplementary functions for MTP. The SCCP transfers through SS7 network
circuit specific, non-circuit specific information and other information.
SCCP subsystems configured at the A interface of the BSC include:
z SCMG (SCCP Management with subsystem code “01”)
z BSSAPI (BSSAP/A Interface with subsystem code “254”)
z BSSAPGS (BSSAP/GS Interface with subsystem code “252”).
You can add an OSP using the command ADD N7OPC.
z [Original Signaling Point Code]: In the system planning, each BSC module is
assigned with an OSP code. The length of the signaling point code should be
consistent with that of DSP.
z [Original Signaling Point Name]: The OSP name identifies and describes an OSP.
z [Whether Support SCCP Management]: If the MSC is configured with SCCP
management subsystem, the BSC should be configured with the same
accordingly. That is, this parameter should be set to “YES”.
z [Subsystem Code]: Two options are available: BSSAPI (BSSAP/A Interface with
subsystem code “254”), and BSSAPGS (BSSAP/GS Interface with subsystem
code “252”). As both 254 and 252 can be used by the subsystem over the A
interface, it is required that the configuration of the subsystem code on the BSC be
consistent with that on the MSC.
z [Link Set Mask]: The link set mask is used for load sharing between different
routes of the same DSP. The default value is "M1111".
Note:
The number of 1s in the link set mask determines the maximum number of links sets. If the number of 1s is
expressed as "n", there are maximum 2n links sets. For example, M0000 stands for one link set, M0001 or
M0100 for two link sets, and M1111 for 16 link sets.
[Example]
Add attributes of two OSPs: Original Signaling Point Code: 0xB001, 0Xb002; Whether
Support SCCP Management: YES; Subsystem Code: BSSAPI; Link Set Mask: M1111.
ADD N7DPCOL: OPC="0xB001", IFSCMP=YES, SSN=BSSAPI, LNKSMSK=M1111;
ADD N7DPCOL: OPC="0xB002", IFSCMP=YES, SSN=BSSAPI, LNKSMSK=M1111;
[Relevant commands]
Table 6-4 shows the commands related to the OSP configuration.
6-5
Table 6-4 Commands related to the OSP configuration
Operation Command
Add Originating Signaling Point ADD N7OPC
Remove Originating Signaling Point RMV N7OPC
Query OSP Information LST N7OPC
Add SCCP subsystem ADD SCCPSSN
Remove SCCP subsystem RMV SCCPSSN
Modify SCCP subsystem Parameters MOD SCCPSSN
Query SCCP subsystem LST SCCPSSN
6.4 Configuration of SS7 Standard

The BSC system supports the ITU-T SS7 standard and the ANSI SS7 standard. The
system starts the message flows according to the currently configured signaling
standard.
You can modify the BSC-supported SS7 standard using the command MOD N7STD to
set the parameter “SS7 standard" to “ITU-T” or “ANSI”.
Note:
z Use this command only when the data of the original signaling point exists.
z Reset all the CSPUs of the BSC to load data after this command is executed.
[Example]
Set the SS7 standard used by the BSC to the ITU-T SS7 standard.
MOD N7STD: N7STD=ITU-T;
[Relevant commands]
Table 6-5 shows the commands related to the configuration of SS7 standard.
Table 6-5 Commands related to the configuration of SS7 standard
Operation Command
Modify SS7 Standard MOD N7STD
Query SS7 Standard LST N7STD
6-6
6.5 Configuration of Trunk Circuit

The trunk circuit is the element of trunk group. One trunk circuit occupies one PCM
timeslot. A trunk group is a collection of trunk circuits sharing the same features. It may
consist of one to several PCM systems.
The trunk circuit serves three purposes.
z Synchronization
z Traffic transfer
z Signaling link.
Each E1 mode PCM provides 32 timeslots, numbered from 0 to 31. Timeslot 0 usually
serves as the synchronization timeslot and any one of other timeslots serves as the
signaling link to transfer signaling. Except the synchronization timeslot and signaling
timeslot, the rest timeslots serve as traffic timeslots. Note that the allocation of PCM
timeslots on the BSC must be consistent with that on the MSC.
Circuit identification code (CIC) is used to identify the circuit between two signaling
points. As CIC is of 12 bits, there can be a maximum of 4,096 circuits between two
signaling points.
You can add the trunk group and trunk circuit using the command ADD TKC.
Meanwhile, E1/T1 usage flag of the CAIE/CSTU changes automatically.
The following describes the key parameters related to this command:
z [Subrack No.]: Subrack No. of CIPS/CTCS where the trunk circuit is on.
z [Slot No.]: Slot No. of the CAIE/CSTU.
z [Board Type]: Select CAIE or CSTU according to the actual configuration.
z [Start E1 No.]/ [Start T1 No.]: Starting E1/T1 No. of the batch-added trunk circuits.
It is numbered uniformly on each CAIE/CSTU.
z [Trunk Group No.]: It is recommended that one trunk group be configured for each
CIPS/CBMS.
z [CIC Start No.]: Under the same signaling point, the trunk circuit is numbered from
0 and the numbers cannot be repeated. Its configuration must be consistent with
that on MSC.
z [Circuit Table Uninstalled]: Specifies the timeslots (synchronization timeslot and
signaling timeslot) that are not for traffic transfer. The default values are 0 and 16.
Its configuration must be consistent with that on MSC.
z [Number of Batch-add Items]: The number of E1s/T1s added in batch.
[Example]
Add trunk circuits: Subrack (CIPS) No.: 5; Slot No.: 15; Board Type: CAIE; E1 Start No.:
0; Trunk Group No.: 0; CIC Start No.: 0; Circuit Table Uninstalled: 0 and 16; Number of
Batch-added Items: 32.
6-7
ADD TKC: FN=5, SN=SN15, BTP=CAIE[E1], AIESE1NO=0, TGNO=0, SCIC=0,

UINBIT=B_0&B_16, ADDNUM=32;
Add trunk circuits: Subrack (CIPS) No.: 6; Slot No.: 15; Board Type: CAIE; E1 Start No.:
0; Trunk Group No.: 1; CIC Start No.: 0; Circuit Table Uninstalled: 0 and 16; Number of
Batch-added Items: 32.
ADD TKC: FN=6, SN=SN15, BTP=CAIE[E1], AIESE1NO=0, TGNO=1, SCIC=0,
UINBIT=B_0&B_16, ADDNUM=32;
[Relevant commands]
Table 6-6 shows the commands related to the trunk data configuration.
Table 6-6 commands related to the trunk data configuration
Operation Command
Add Trunk Group ADD TG
Remove Trunk Group RMV TG
Query Trunk Group Parameters LST TG
Add Trunk Circuit ADD TKC
Remove Trunk Circuit RMV TKC
Modify Trunk Circuit Parameters MOD TKC
Query Trunk Circuit LST TKC
6.6 Configuration of MTP Link

The MTP signaling link is the physical media for the transmission of SS7 signaling. Any
timeslot except timeslot 0 in the PCM system can be designated as the signaling data
link, and here timeslot 16 is recommended.
The MTP uses signaling link code (SLC) to identify the signaling links. The signaling
link code sending (SLCSEND) is sent to the signaling entity of MSC so that it can
identify the code of this signaling link. In normal cases, SLC and SLCSEND are
configured with the same value. Meanwhile, the link of the MSC signaling entity
connected with the BSC should be configured with the same SLC and SLCSEND.
You can add MTP link in the specified E1/T1 using the command ADD N7LNK.
The following describes the key parameters related to this command:
z [Subrack No.]: Subrack No. of the CIPS/CTCS where the trunk circuit is on.
z [Slot No.]: Slot No. of the CAIE/CSTU.
z [Board Type]: Select CAIE or CSTU according to the actual configuration.
z [E1/T1 No.]: No. of E1/T1 used by the signaling link to be added.
6-8
z [Timeslot No.]: No. of E1/T1 timeslot used by the signaling link to be added. Its
default value is 16.
z [Signaling Link Code]: Generally, SLCs configured on both ends of one signaling
link should be the same. It is numbered from 0 by default.
z [Signaling Link Code Sending]: Generally, the SLCSEND to be added should be
the same as the SLC.
z [Link Priority]: The usage priority of the signaling link. Normally signaling links are
used regardless of the priority. It is recommended to set link priority to 0 by default.
[Example]
Add MTP link: Subrack (CIPS) No.: 5; Slot No.: 15; Board Type: CAIE; E1 No.: 0;
Timeslot No.: 16; Signaling Link Code: 0; Signaling Link Code Sending: 0.
ADD N7LNK: FN=5, SN=SN15, BTP=CAIE, E1T1NO=0, SLC=0, SSLC=0, SATF=FALSE;
Add MTP link: Subrack (CIPS) No.: 6; Slot No.: 15; Board Type: CAIE; E1 No.: 0;
Timeslot No.: 16; Signaling Link Code: 1; Signaling Link Code Sending: 1.
ADD N7LNK: FN=6, SN=SN15, BTP=CAIE, E1T1NO=0, SLC=1, SSLC=1, SATF=FALSE;
[Relevant commands]
Table 6-7 shows the commands related to the configuration of MTP signaling link.
Table 6-7 Commands related to the configuration of MTP signaling link
Operation Command
Add MTP link ADD N7LNK
Remove MTP link RMV N7LNK
Modify MTP link parameters MOD N7LNK
Query MTP link LST N7LNK
6.7 Data to be Negotiated

Table 6-8 lists the data that should be consistent on the BSC and on the MSC.
Table 6-8 Negotiation data for BSC-MSC interconnection
Item Value Description

INTC (international)
INT2C (international Identifies the network where the signaling point resides. The
Network indicator standby) MSC and the BSC must reside in the same network as required
(NI)
NATC (national) by the protocol.
NAT2C (national standby)
14 bits Represents the coding scheme used for the address of network
Length of signaling
where BSC is on. It must be consistent with the length of
point code 24 bits A-interface SPC on MSC.
6-9

0x0001-0x3FFF (14 bits) Represents the signaling point code of BSC. The hexadecimal
Original signaling
0x000001-0xFFFFFF (24 coding scheme is adopted. The OPC configuration must be
point code (OPC)
bits) consistent with that allocated by the MSC.
Destination 0x0001-0x3FFF (14 bits)

Represents the signaling point code of MSC A interface.
signaling point 0x000001-0xFFFFFF (24 Hexadecimal coding scheme is adopted.
code (DPC) bits)
Represents the signaling link identification code between BSC

and MSC, used to identify the signaling link. For the same
SLC and
0-255 signaling link, BSC and MSC respectively have their own SLC
SLCSEND
and SLCSEND. Therefore, there are four codes in total.
Generally, these four codes should be the same.
BSSAPI (0xFE,254)
SCCP subsystem
BSSAPGS (0xFC,252) It must be consistent with that of MSC A-interface.
No. (SCCPSSN)
SCMG (0x01,01)
Circuit
Identifies the trunk circuit between BSC and MSC. The CICs of
identification code 0-4095
the same circuit on BSC and on MSC must be the same.
(CIC)
At least one timeslot in one E1/T1 cable is required to transmit
One or more circuits among synchronization signals.
Circuit table the circuits 0 to 31.
uninstalled Generally, circuit 0 and The configuration of synchronization timeslot and signaling
circuit 16 are selected. timeslot on the BSC should be consistent with those on the MSC
to ensure the correct transmission of these two types of signals.
Protocol version IOS2.4 (2.4 version)
No. of A interface It must be consistent with that of the MSC A-interface.
(A Phase) IOS4.1 (4.1 version)
System
0-32767 Exclusively identifies one CDMA cellular network system.
identification (SID)
Network Exclusively identifies one network within a CDMA cellular
0-65535
identification (NID) system.
MSC identification
0-0xFFFFFF Identifies one MSC during hard handoff.
(MSC ID)
Vendor
Market ID and Entity ID together are used to identify the source
identification 0-65535
BSC during inter-BSC soft handoff.
(Market ID)
Market ID and Entity ID together are used to identify the source
Entity identification
0-65535 BSC during inter-BSC soft handoff. Its value cannot be repeated
(Entity ID)
within the range of one operator.
Packet zone In a specific SID/NID zone, PZID is used to exclusively identify
identification 0-255 the area covered by PCF. The combination of SID/NID/PZID
(PZID) corresponds to the configuration at PCF side.
Location area code
0-0xFFFF Planned in a centralized way to define one cell group
(LAC)
6-10

Planned in a centralized way to number the cell. It consists of
Cell identity 0-65535
CELL ID and SECTOR ID.
6-11
7.1 Overview
7.1.1 A3/A7 Interface Protocol Stack
A3/A7 interface is a logical interface between two neighbor BSCs to support inter-BSC
soft handoff.
The A3 interface includes A3 signaling and A3 traffic. The channels for transferring the
A3 signaling and the A3 traffic are different. The A3 traffic channel is to transfer the user
traffic and the A3 signaling channel is to control and allocate the user traffic transferred.
Figure 7-1 and Figure 7-2 show the protocol stacks for A3 signaling and A3 traffic
respectively.
The A7 interface is used to transfer the signaling messages between the source BSC
and the destination BSC. Figure 7-3 shows the protocol stack.
A3 Signaling
TCP
IP
AAL5
ATM
Physical Layer
AAL5: ATM adaptation layer 5
Figure 7-1 A3 interface signaling protocol stack
User Traffic Frame
SSSAR
AAL2
ATM
Physical Layer
SSSAR: Special service segmentation and reassemble

AAL2: ATM adaptation Layer 2
Figure 7-2 A3 interface traffic protocol stack
7-1
IOS Application
TCP
IP
AAL5
ATM
Physical Layer
The small-capacity BSC provides A3/A7 interface through the CBIE/CXIE in the CRPS.
Table 7-1 shows the board features. This chapter introduces the configuration of A3/A7
interface when CBIE is used.
Table 7-1 Features of A3/A7 interface boards
Board Function
Each CBIE provides 32 E1/T1 interfaces for the transmission of ATM cells. It supports the
CBIE
IMA/UNI mode and ATM over Fractional E1/T1 mode for the transmission.
Each CXIE provides 24 E1/T1 interfaces for the transmission of ATM cells. It supports
CXIE
IMA/UNI mode for the transmission.
The configuration of the A3/A7 interface involves the following parts.

z Neighbor BSC
z Connection mode of interface board
z A7 link
z A3 link
z Inter-BSC soft handoff terrestrial link
7-2
Start
Configure
neighbor BSC
Configure
connection mode
of interface board
Configure A7 link
Configure A3 link
Configure
inter-BSC
soft handoff
terrestrial link
End
7.2 Configuration of Neighbor BSC

The basic information configuration is to add some parameters of system level to the
neighbor BSC. For one BSC, five neighbor BSCs can be configured at most.
You can execute the command ADD NBRBSC to add basic information of the neighbor
BSC.
z [Neighbor BSC IP Address]: The BSCs in a MSC are identified with BSC IP for the
inter-BSC soft handoff. The IP addresses are uniformly allocated in the whole
MSC.
z [Peer Market ID]: A unified value within the whole network to identify the
equipment of different vendors. It should be identical with that configured at the
MSC.
z [Peer Entity ID]: It identifies different BSC entities.
z [Local Entity Attribute]: This parameter specifies whether the local BSC acts as a
server or a client. The BSCs are connected through TCP; therefore, for two
neighbor BSCs, one must be configured as server and the other as client.
z [A3 Port No. Sequence]: It specifies the No. of the A3 port. You may type multiple
values separated by comma here.
7-3
[Example]
Add the basic information of an neighbor BSC as below.
z Neighbor BSC IP address: 129.11.17.10
z Peer Market ID: 14001
z Peer entity ID: 6
z Local entity attribute: server
z A3 port No. sequences: 5600 and 5601.
ADD NBRBSC: BSCID="129.11.17.10", MRKTID=14001, ENTID=6, ENTATTR=SVR,
A3PNLST="5600,5601";
[Relevant commands]
Table 7-2 shows the commands related to the configuration of the neighbor BSC basic
information.
Table 7-2 Commands related to the configuration of neighbor BSC basic information
Operation Command
Add Neighbor BSC ADD NBRBSC
Remove Neighbor BSC RMV NBRBSC
Query Neighbor BSC Basic Information LST NBRBSCINF
7.3 Configuration of Connection Mode of Interface Boards

The small-capacity BSC provides A3/A7 interface through the CBIE/CXIE in the CRPS.
The CBIE/CXIE offers multiple connection modes, including IMA group (contains IMA
link or FRACTIONAL IMA link), UNI link and electrical interface FRACTIONAL IMA link.
For configuration of CBIE/CXIE connection, see section 8.2, "Configuration of Abis
Interface Connection Mode". The following describes the connections of the A3/A7
interface when IMA group is configured in the CBIE.
[Example]
Add an IMA group.
Subrack (CRPS) No.: 2; Slot No.: 0; Board Type: CBIE; IMA Group No.: 31; E1 No. List:
30, 31.
ADD IMAGRP: FN=2, SN=SN0, BTP=CBIE, BIEIMAGN=31, BIEE1LST="30,31",
BIETXCLKMD=CTC, TXFRMLEN=L128, IMAVER=VER11;
[Relevant commands]
Table 7-3 shows the commands related to the configuration of the interface board
connection. Only the commands for adding entities are listed.
7-4
Table 7-3 Commands related to configuration of interface board connection
Operation Command
Add IMA Group and Link ADD IMAGRP
Add IMA Group and Fractional IMA Link ADD FRACIMAGRP
Add UNI Link ADD UNILNK
Add Electrical Port Fractional ATM Link ADD EFRACATM
7.4 Configuration of A7 Link

The A7 interface signaling channel is borne by permanent virtual connection (PVC).
When the A7 link between two neighbor BSCs is established, the corresponding PVC
parameters should be configured, and the virtual path identifier (VPI) and the virtual
channel identifier (VCI) need to be specified.
You can use the command ADD A7LNK to add A7 physical link PVC to the neighbor
BSC.
The following describe the parameters in this command.
z [Neighbor BSC IP Address]: It should be consistent with the IP address configured
in the neighbor BSC basic information.
z [Connection Mode]: Except OPTLNK, other modes can be selected in the
small-capacity BSC.
z [Slot No.]: It specifies the slot where the CBIE/CXIE (connected with the neighbor
BSC) resides.
z [IMA Group No.]/[E1/T1 No.]/[FRACTIONAL ATM Link No.]: It specifies the logical
link on the A7 interface. This parameter may vary with the connection mode.
z [A7 Link Flag]: It identifies the A7 link PVC parameter, that is, the VPI/VCI value. It
must be consistent with that configured at the peer BSC.
[Example]
Add an A7 link to neighbor BSC.
Neighbor BSC IP address: 129.11.17.10; Link mode: IMA; IMG group No.: 31; A7 link
flag: 8-60.
ADD A7LNK: BSCID="129.11.17.10", LM=IMALNK, SN=SN0, IMAGN=31, A7LFLG="8-60";
[Relevant commands]
Table 7-4 shows the commands related to A7 link configuration.
Table 7-4 Commands related to A7 link configuration
Operation Command
Add A7 Link between Neighbor BSCs ADD A7LNK
7-5
Operation Command
Remove A7 Link between Neighbor BSCs RMV A7LNK
7.5 Configuration of A3 link

Two A3 links (local and peer) should be configured for the A3 interface between
neighbor BSCs, and the corresponding AAL2 link flag should be specified.
You can use the command ADD A3LNK to add A3 physical link PVC to the neighbor
BSC.
in the neighbor BSC basic information.
z [Connection Mode]: Except OPTLNK, other modes can be selected in the
small-capacity BSC.
z [Slot No.]: It specifies the slot where the CBIE/CXIE (connected with the neighbor
BSC) resides.
z [IMA Group No.]/[E1/T1 No.]/[FRACTIONAL ATM Link No.]: It specifies the logical
link on the A3 interface. This parameter may vary with the connection mode.
z [Local A3 Link Flag] and [Peer A3 Link Flag]: They are used to configure the AAL2
link flags for the local and the peer A3 interfaces. Parameters as VPI, VCI, VCCI
(PVC index No.) of the corresponding link must be configured. The input format is
VPI-VCI-VCCI. If multiple AAL2 links need be configured, the parameters should
be separated by commas. The local link flag and the peer link flag should be
different. However, they must be consistent with those configured at the peer
BSC.
z [Link Bandwidth]: Bandwidth of the A3 interface traffic link. It should be configured
according to the actual traffic requirement. The total bandwidth of traffic links shall
be not more than that of physical links.
[Example]
Add an A3 link to neighbor BSC.
z Neighbor BSC IP address: 129.11.17.10
z Link mode: IMA
z IMA group No.: 31
z Local A3 link flag: 8-61-1
z Peer A3 link flag: 8-62-2
z Link bandwidth: 2.4 Mbit/s
ADD A3LNK: BSCID="129.11.17.10", LM=IMALNK, SN=SN0, IMAGN=31,
CA3LFLG="8-61-1", PA3LFLG="8-62-2", LNKBW=BW2.4M;
7-6
[Relevant commands]
Operation Command
7.6 Configuration of Inter-BSC SHO Terrestrial Link

The terrestrial link configuration is to add soft hand-off terrestrial link between the board
in the BSC boarder subrack and the CMUX in the CRPS to transfer the soft handoff
messages.
You can use the command ADD SHOLINK to add terrestrial link for inter-BSC soft
handoff.
z [Link Type]: It is set to OBSC (inter-BSC soft handoff link) by default.
z [Subrack No.]: If certain cell served by the CIPS resides at the BSC boarder, the
CIPS shall be designated as the boarder subrack when inter-BSC soft handoff is
triggered.
z [Link Bandwidth]: Configured according to the actual traffic requirement. It is
BW1.0 M (1.0 M) by default.
[Example]
Set CIPSs 5 and 6 as the border subracks and add a terrestrial link for inter-BSC soft
handoff.
ADD SHOLINK: HOLNKTP=OBSC, MGFN=5, BANDWIDTH=BW1.0M;
[Relevant commands]
Table 7-6 shows the commands related to for the configuration of terrestrial link for
inter-BSC soft handoff.
Table 7-6 Commands related to the configuration of inter-BSC soft handoff terrestrial link
Operation Command
7-7

Table 7-7 lists the data requiring negotiation when two neighbor BSCs are
interconnected.
Table 7-7 Data to be negotiated for neighbor BSCs interconnection

Neighbor BSC IP
Allocated uniformly within the whole MSC.
address
Used together with entity ID to identify the source
Peer Market ID 0-65535
BSC during inter-BSC soft handoff.
The IDs of the entities cannot be repeated within the
Peer entity ID 0-65535
range of one operator. See Market ID for details.
It is meaningful only when a peer entity is configured.
Local entity attribute Server/client
One acts as the server and the other as the client.
Multiple values can be configured. A BSC can
A3 port No. 1-65535
provide up to 12 A3 ports to the neighbor BSC.
It must be identical with the A7 link flag of the
A7 link flag VPI-VCI
neighbor BSC.
VPI-VCI-VCCI value of the ATM link The local A3 link flag must be identical with the peer
Local A3 link flag/ corresponding to the A3 link flag. It A3 link flag configured in neighbor BSC, and the peer
Peer A3 link flag should be numbered in the sequences A3 link flag must be identical with the local A3 link
like "1-250-1", "1-249-2" and "1-248-3". flag configured in neighbor BSC.
7-8
Airbridge cBSC6600 CDMA Base Station Controller Chapter 8 Abis Interface Configuration
Chapter 8 Abis Interface Configuration
8.1 Overview
8.1.1 Abis Interface Protocol Stack
As the logical interface between the BSC and the BTS, the Abis interface comprises the
Abis signaling, Abis traffic and operation and maintenance link (OML) signaling. The
following is function description of the three parts.
z Abis signaling part serves as the channel transferring signaling between the BSC
and the BTS. Figure 8-1 shows the signaling protocol stack of the Abis interface.
z Carrying the subscriber traffic, the Abis traffic part serves as the interface between
SDU of BSC and the channel element of BTS. Figure 8-2 shows the Abis interface
traffic protocol stack.
z OML signaling part implements relevant operation and maintenance. At Abis
interface, IPOA channel is set up, serving as OML.
A bis S ign a lin g A p plic a tio n
TCP
IP
AAL5
AT M
P h ys ic a l L a ye r

Figure 8-1 Abis interface signaling protocol stack
Abis Traffic
SSSAR
AAL2
ATM
Physical Layer

Figure 8-2 Abis interface traffic protocol stack
8-1
The CBIE/CXIE in the CIPS provides Abis interface. Table 8-1 shows the features of
these boards. This chapter introduces the configuration of Abis interface when the
CBIE is used.
Table 8-1 Features of Abis interface board
Board Function
Each CBIE provides 32 E1/T1 interfaces for the transmission of ATM cells. It supports
CBIE
CXIE
The Abis interface configuration involves the following parts.

z Abis interface connection mode
z BTS basic information
z BTS OML
z BTS signaling link
z BTS traffic link
The last three configuration items are related to the OML signaling, Abis signaling and
Abis traffic in the Abis interface signaling protocol stack.
8-2
Start
Configure
Abis interface
connection mode
Configure BTS
basic information
Configure
OML
Configure
signaling link
Configure
traffic link
End
Figure 8-3 Procedures of Abis interface configuration
8.2 Configuration of Abis Interface Connection Mode

The Abis interface supports multiple connection modes.
z IMA group (including IMA link or fractional IMA link)
z UNI link
z Electrical interface fractional ATM link
Table 8-2 details the connection modes.
Table 8-2 Abis interface connection mode
Corresponding
Connection mode Object included Object configured
board type
CBIE/CXIE IMA link E1/T1
IMA group E1/T1 and its
CBIE Fractional IMA link
timeslots
UNI link CBIE/CXIE None E1/T1
E1/T1 and its
Fractional ATM link CBIE None
timeslots
Note that each interface board allocates its own E1s/T1s and their timeslot resources to
avoid repetition in the configuration.
8-3
One CBIE provides 32 E1s/T1s, which are allocated into four ports (eight E1s/T1s for
each port), numbered 0, 1, 2, and 3 from the bottom up. It can support multiple
connection modes such as the IMA group, UNI link and fractional ATM link. When
configured, the IMA group can be numbered from 0 to 31.
One CXIE provides 24 E1s/T1s, which are allocated into three ports (eight E1s/T1s for
each port), numbered 0, 1, and 2 from the bottom up. It can only support the IMA group
and UNI link. Table 8-3 lists the value range of the E1/T1 Nos. and IMA group Nos.
corresponding to different ports upon the configuration of the IMA group.
Table 8-3 Correspondence of E1/T1 Nos. and IMA group Nos. on a CXIE
Port E1/T1 No. IMA group No.

0 0-7 0-3
1 8-15 4-7
2 16-23 8-11
The following details the configuration of different connection modes of the Abis
interface.
8.2.1 Configuration of IMA Group
more links for transmission to realize the dynamic expansion of bandwidth. For the
IMA-related fundamentals, see section 4.4.1, “Adding IMA Group and Link”.
You can configure IMA links and CBIE fractional IMA links in the IMA group.
I. Adding IMA group and links
You can execute the command ADD IMAGRP to add IMA groups and IMA links for the
Abis interface to the CBIE/CXIE. The following are related parameters.
z [Subrack No.] and [Slot No.]: The Nos. of the subrack and slot where the
CBIE/CXIE (to which IMA group belongs) resides.
z [Board Type]: Select the CBIE or CXIE according to the actual application.
z [IMA Group No.] and [E1/T1 No. List]: The IMA group No. and E1/T1 No.
corresponding to IMA link in the group.
After completing the configuration, you can use the command LST IMAGRP to query
the IMA group information, ADD IMALINK to add or RMV IMALNK to remove an IMA
link.
[Example]
Add an IMA group. Subrack (CIPS) No.: 5; Slot No.: 0; Board Type: CBIE; IMA Group
No.: 0; E1 No. List: 0 and 1.
8-4

[Relevant commands]
Table 8-4 shows the commands related to adding IMA group and link.
Table 8-4 Commands related to adding IMA group and link
Operation Command
Remove IMA Group and Link RMV IMAGRP
Query IMA Group and Link LST IMAGRP
Add IMA Link ADD IMALNK
Remove IMA Link RMV IMALNK
Query IMA Links LST IMALNK
II. Adding IMA group and fractional IMA link
You can use the command ADD FRACIMAGRP to add IMA groups and fractional IMA
links to the CBIE. The following are related parameters.
z [Subrack No.] and [Slot No.]: The Nos. of the subrack and slot where the CBIE (to
which IMA group belongs) resides.
z [IMA Group No.]: The No. of the IMA group.
z [FRACTIONAL ATM link No.]: The No. of the fractional ATM link to be added.
z [E1/T1 Mode]: E1 or T1 mode, which must be comply with the actual one.
z [E1 No.]/[T1 No.]: The No. of the E1/T1 where the fractional ATM link to be added
resides.
z [Timeslot]: The E1/T1 timeslots that this fractional ATM link contains.
After completing the configuration, you can use the command LST FRACIMAGRP to
query the IMA group information, ADD FRACIMALNK to add or RMV FRACIMALNK
to remove a fractional IMA link.
8-5
Note:
z In one IMA group, the IMA link and the fractional IMA link cannot coexist.
z The number of timeslots occupied by each fractional IMA link in an IMA group shall be the same.
z Multiple fractional IMA links can be configured on an E1/T1 circuit.
[Example]
Add IMA group 0 to the CBIE in slot 0 of CIPS 5. The Nos. of fractional IMA links are 1
and 2. The two links occupies timeslots 1 to 15 and 17 to 31 of No.0 E1 respectively.
ADD FRACIMAGRP: FN=5, SN=SN0, IMAGN=0, TXCLKMD=CTC, TXFRMLEN=L128,
IMAVER=VER11, FRACIMAID=1, E1T1MODE=E1, E1NO=0, E1TSBITMAP=
TS_1&TS_2&TS_3&TS_4&TS_5&TS_6&TS_7&TS_8&TS_9&TS_10&TS_11&TS_12&TS_13&TS_14
&TS_15, TXCLKMD=CTC, TXFRMLEN=L128, IMAVER=VER11;

TS_17&TS_18&TS_19&TS_20&TS_21&TS_22&TS_23&TS_24&TS_25&TS_26&TS_27&TS_28&TS
_29&TS_30&TS_31;
[Relevant commands]
Table 8-5 shows the commands related to the configuration of IMA group and fractional
IMA link.
Table 8-5 Commands related to the configuration of IMA group and fractional IMA link
Operation Command
Add IMA Group and Fractional IMA Link ADD FRACIMALNK
Add Fractional IMA Link ADD FRACIMALNK
Remove Fractional IMA Link RMV FRACIMALNK
Query Fractional IMA Links LST FRACIMALNK
8.2.2 Configuration of UNI Link
The UNI mode is applied to transmit ATM cells on one E1/T1.

You can execute the command ADD UNILNK to add UNI links for the Abis interface to
the CBIE/CXIE. The following are related parameters.
CBIE/CXIE (to which the UNI link belongs) resides.
8-6
z [E1/T1 No.]: The No. of the E1 of the UNI link to be configured. The No. of E1s/T1s
on the CBIE: 0 to 31; No of E1s/T1s on the CXIE: 0 to 23.
[Example]
Add a UNI link. Subrack (CIPS) No.: 5; Slot No.: 0; E1 No.: 0.
ADD UNILNK: FN=5, SN=SN0, E1T1NO=0;

[Relevant commands]
Table 8-6 shows the commands related to the configuration of UNI link.
Table 8-6 Commands related to the configuration of UNI link
Operation Command
Remove UNI Link RMV UNILNK
Query UNI Link LST UNILNK
8.2.3 Configuration of Fractional ATM Link
The fractional ATM link can be configured to the CBIE.

You can use the command ADD EFRACATM to add the fractional ATM link to the CBIE.
which the fractional ATM link belongs) resides.
z [E1 No.]/[T1 No.]: The No. of the E1/T1 where the electrical interface fractional
ATM link to be added resides.
[Example]
Add one electrical interface fractional ATM link to the CBIE that resides in slot 0 of the 5
CIPS 5. The link No. is 8 and the link occupies the timeslots 0 to 15 of the No. 8 E1.
ADD EFRACATM: FN=5, SN=SN0, FRACATMID=8, E1T1MODE=E1, E1NO=8,
E1TSBITMAP=TS_1&TS_2&TS_3&TS_4&TS_5&TS_6&TS_7&TS_8&TS_9&TS_10&TS_11&TS_12&
TS_13&TS_14&TS_15;
[Relevant commands]
Table 8-7 shows the commands related to the configuration of the fractional ATM link.
8-7
Table 8-7 Commands related to the configuration of fractional ATM link
Operation Command
Remove Electrical Port Fractional ATM Link RMV EFRACATM
Query Electrical Port Fractional ATM Link LST EFRACATM
8.3 Configuration of BTS Basic Information

The configuration of BTS basic information is to add a BTS , a cascaded BTS in the
BSC or a BTS outside the BSC. The basic BTS information includes the following.
z module No.
z BTS ID
z BTS Name
z IP address of BTS operation and maintenance
z IP address of BTS signaling.
Other commands shall be used to add OML link, Abis signaling link, and traffic link for
the BTS.
You can use the command ADD BSCBTSINF to configure the BTS basic information.
z [BTS Type]: Type of the BTS to be added, including BTS inside the BSC,
cascaded BTS in the BSC, and BTS outside the BSC.
z [Module No.]: No. of the module corresponding to the BTS to be added. In the BSC,
each module corresponds to a CIPS.
z [BTS ID]: It identifies a BTS in a BSC. Its configuration must be consistent with that
on the BTS.
z [BTS Name]: It describes a BTS to be added. If nothing is entered, the BTS will be
named as "BTS000+ [BTS ID]" by default.
z [BTS Operation Maintenance IP Address]: It shall be configured with the same
network segment as BTS operation & maintenance gateway of the corresponding
CIPS. For details of this parameter, see 8.3.1 BTS O&M Channel.
z [BTS Signaling IP Address]: It shall be configured within the same network
segment as internal IP address of the CSPU of the corresponding CIPS. It is used
for the communication between the CSPU of the CIPS subrack and the signaling
processing module of the BCKM in the BTS. For details of this parameter, see
8.3.2 BTS Signaling Channel.
[Example]
Add a BTS inside the BSC:
8-8
Module No.: 0; BTS ID: 0; BTS Name: BTS-A; BTS Operation Maintenance IP Address:
129.8.10.4; BTS Signaling IP Address: 80.21.130.116.
ADD BSCBTSINF: BTSTP=IBSC, MN=0, IBTSID=0, BTSNM="BTS-A", OMIP="129.8.10.4",
SIGIP="80.21.130.116";
Add a BTS cascaded with module1 in the BSC:

Module No.: 1; BTS ID: 1; BTS Name: BTS-B; BTS Operation Maintenance IP Address:
ADD BSCBTSINF: BTSTP=IBSC, MN=1, IBTSID=1, BTSNM="BTS-B", OMIP="129.9.10.5",
SIGIP="80.25.130.116";
[Relevant commands]
Table 8-8 shows the commands related to the configuration of BTS basic information.
Table 8-8 Commands related to the configuration of BTS basic information
Operation Command
Add BTS Basic Information ADD BSCBTSINF
Remove BTS Basic Information RMV BSCBTSINF
Query BTS Basic Information LST BSCBTSINF
8.3.1 BTS O&M Channel
In the small-capacity BSC, the O&M channel between BSC and BTS is illustrated in
Figure 8-4. This channel spans the following network segments before it reaches BTS:
z Network segment 10.12.3.0 (mask: 255.255.255.0) between BAM and CMUX of
CIPS
z Network segment 129.m.10.0 (mask: 255.255.255.0) between CMUX of CIPS and
BTS
129.m.10.0 10.12.3.0
BTS 129.m.10.4
BTS 129.m.10.5 CMUX

BAM
129.m.10.n
BTS 129.m.10.6 TCP/IP TCP/IP 10.12.3.128
10.12.3.f
BTS 129.m.10.N
BSC
Figure 8-4 Operation and maintenance channel between BSC and BTS (small-capacity BSC)
8-9
The IP addresses of the CMUX in CIPS subrack is 129.m.10.n and 10.12.3.f, where,
"m" starts from 8 and increases along with No. of CIPS; "n" ranges from 1 to 3 and "f" is
the No. of CIPS where CMUX board resides.
"129.m.10.n" is the IP address of BTS operation and maintenance gateway in the
CIPS.
The BTS O&M IP address is 129.m.10.N. "m" here equals to the one in IP address of
CMUX. "N" is related to BTS ID, starting from 4 and increasing along with the BTS ID.
8.3.2 BTS Signaling Channel
The communication on the signaling part of the Abis interface relies on the TCP/IP
protocol. The BSC CSPU processes the interface signaling and the call signaling, and
distributes the service processing resources.
The BTS signaling IP address shall be located at the same segment as the internal IP
address of CSPU in the corresponding CIPS, as shown in Figure 8-5.
80.m.130.0
BTS 80.m.130.116
BTS 80.m.130.117 CSPU

BTS 80.m.130.118 TCP/IP 80.m.130.0
BSC
BTS 80.m.130.n
Figure 8-5 BTS signaling channel
The IP address of the CSPU is 80.m.130.0 (mask: 255.255.0.0), where

m=f%4+1
Here, "f" refers to the No. of the CIPS where the CSPU resides.
The IP address of BTS signaling is 80.m.130.n (mask: 255.255.0.0), where
m=f%4+1
Here, "f" refers to the No. of the CIPS where the CSPU resides. Starting from 116, "n" is
related to the BTS ID and increases along with BTS ID.
8.4 Configuration of BTS O&M Link

The BTS O&M link configuration is to set up the O&M IPOA channel for a BTS inside
the BSC, through which operation and maintenance are implemented and BOOTUP
information of BTS is obtained. One BTS can be configured with one O&M link only.
8-10
The O&M IPOA channel is carried by a PVC. To set up the PVC link for the BSC-to-BTS
O&M channel, the parameters related to the PVC from the CBIE/CXIE to the CMUX in
the same CIPS must be configured. The system generates other data automatically.
You can use the command ADD BTSOMLNK to configure the BTS O&M link.
z [BTS ID]: No. of the BTS to which the O&M link is added.
z [Subrack No.] and [Slot No.]: Nos. of subrack and slot where CBIE/CXIE resides.
z [Connection Mode]: The Abis interface connection mode selected according to the
physical port on the corresponding interface board on the BTS.
z [IMA group No.]/[E1/T1 No.]/[FRACTIONAL ATM link No.]: An identifier used to
specify the logical link on the Abis interface. This parameter might vary with the
connection mode.
z [BOOTP ID]: It specifies parameters of the PVC connecting the CBIE/CXIE to the
CMUX of the same subrack. The BTS uses this PVC link for BOOTP request. The
recommended value range of VPI is 2 to 15, and that of VCI is 32 to 80.
z [Operation Maintenance Link ID]: It specifies parameters of the PVC connecting
CBIE/CXIE to CMUX of the same subrack. The BSC uses this PVC link to operate
and maintain the BTS. The recommended value range of VPI is 1 to 64, and that of
VCI is 81 to 255. The VPI/VCI value shall be unique.
[Example]
Add a BTS O&M link:
BTS ID: 0; Subrack (CIPS) No.: 5; Slot (CBIE) No.: 0; IMA Group No.: 0; BOOTP ID:
2-44; Operation Maintenance Link ID: 1-255.
ADD BTSOMLNK: BTSID=0, FN=5, SN=SN0, LM=IMA, IMAGN=0, BTPFLG="2-44",
OMLNKFLG="1-255", LNKBW=BW110K;
Add a BTS O&M link:

[Relevant commands]
Table 8-9 shows the commands related to the BTS O&M link configuration.
Table 8-9 Commands related to BTS O&M link configuration
Operation Command
Add BTS O&M Link ADD BTSOMLNK
8-11
Operation Command
Remove BTS O&M Link RMV BTSOMLNK
8.5 Configuration of BTS Signaling Link

The configuration of BTS signaling link is to add the signaling IPOA channel for a BTS
inside the BSC. Each BTS can be configured with one signaling link.
The BTS signaling IPOA channel is carried by a PVC. Therefore, to establish the Abis
signaling link of the BTS, the parameters related to the PVC from the CBIE/CXIE to the
CSPU in the same CIPS must be configured. The VPI and VCI values should be
specified.
You can use the command ADD BTSSIGLNK to add a BTS Abis signaling link.
z [BTS ID]: No. of the BTS to which Abis signaling ink is added.
specify the logical link on the Abis interface. This parameter may vary with the
connection mode.
z [Abis Link ID]: It specifies the parameters of the PVC connecting CBIE/CXIE of the
BTS to CSPU in the same subrack. The recommended value range of VPI is 1 to
64, and that of VCI is 32 to 255. The VPI/VCI value shall be unique.
[Example]
Add an Abis signaling link:
BTS ID: 0, Subrack (CIPS) No.: 5; Slot (CBIE) No.:0; IMA Group No.: 0; Abis Link ID:
1-254.
ADD BTSSIGLNK: BTSID=0, FN=5, SN=SN0, LM=IMA, IMAGN=0, SIGLNKFLG="1-254",
LNKBW=BW110K;

1-254.
LNKBW=BW110K;
8-12
[Relevant commands]
Table 8-10 shows the commands related to the configuration of the BTS signaling link.
Table 8-10 Commands related to the configuration of the BTS signaling link
Operation Command
Add BTS Signaling Link ADD BTSSIGLNK
Remove BTS Signaling Link RMV BTSSIGLNK
8.6 Configuration of BTS Traffic Link

The configuration of the BTS traffic link is to add an AAL2 traffic link between the
CBIE/CXIE of CIPS and the BTS.
You can use the command ADD BTSTRFLNK to configure the BTS traffic link.
z [BTS ID]: No. of the BTS to which traffic link is added.
z [Subrack No.] and [Slot No.]: Nos. of the subrack and the slot where the
CBIE/CXIE resides.
connection mode.
z [Traffic Link ID List]: When the AAL2 traffic link is added, parameters such as VPI,
VCI, VCCI (PVC index) of the corresponding ATM link must be specified. The input
format is VPI-VCI-VCCI. If multiple AAL2 traffic links are added, use comma to
separate the parameters. Its configuration must be consistent with that on the BTS.
The recommended value range of VPI is 1 to 64, and that of VCI is 32 to 255.
z [Link Bandwidth]: It specifies the total bandwidth of the BTS traffic links. The
default bandwidth of one traffic link is 1.6 Mbit/s. The total bandwidth of traffic links
configured for the BTS shall not be more than that of physical links.
[Example]
Add BTS traffic link:
BTS ID: 0; Subrack (CIPS) No.: 5; Slot (CBIE) No.: 0; IMA Group No.: 0; Traffic Link ID
List: 1-250-1, 1-249-2; Link Bandwidth: 3.2 Mbit/s.
ADD BTSTRFLNK: BTSID=0, FN=5, SN=SN0, LM=IMA, IMAGN=0,
TRFLNKLST="1-250-1,1-249-2", LNKBW=BW3.2M;
8-13
[Relevant commands]
Table 8-11 shows the command related to of the configuration of BTS traffic link.
Table 8-11 Command related to of the configuration of BTS traffic link
Operation Command
Add BTS Traffic Link ADD BTSTRFLNK
Remove BTS Traffic Link RMV BTSTRFLNK

Table 8-12 lists the data that should be consistent on the BSC and the MSC when BSC
is interconnected with BTS.
Table 8-12 Negotiation data for BSC-to-BTS interconnection

BTS inside the BSC: 0-959 IDs of BTSs controlled by the same BSC are
BTS ID
BTS outside the BSC: 960–1919 allocated in a uniform way.
The parameter of the PVC connecting the

VPI: 2-15 CBIE/CXIE of CIPS to the CMUX in the same
BTS BOOTP ID subrack.
VCI: 32-80
The BTS uses this PVC link for BOOTP request.
CBIE/CXIE of CIPS to the CMUX in the same
VPI: 1-64
BTS O&M link ID subrack.
VCI: 81-255
This PVC link is used to operate and maintain
the BTS.
129.m.10.N:
The "m" here equals to the one in IP address
BTS O&M IP Its configuration must be consistent with that on
of the CMUX on the CIPS.
address the BTS.
Starting from 4, the "N" is related to the BST
ID and increases along with the BTS ID.
8-14

80.m.130.n (mask: 255.255.0.0):
m = f % 4 + 1.
It must be in the same network segment as the
BTS signaling IP "f" refers to the No. of CIPS where CSPU of CSPU IP address. Its configuration must be
address BTS signaling processing unit resides. consistent with that on the BTS.
“n” starts from 116 and is related to the BTS
ID. It increases along with the BTS ID.
BSC signaling IP The configuration on the BSC must be

80.m.130.0
address consistent with that on the BTS.
Carrier ID It is numbered from 0 within the same sector.

The "VPI-VCI-VCCI" of ATM link
corresponding to the traffic link ID. The configuration on the BSC must be
Traffic link ID
It is usually numbered in the way like consistent with that on the BTS.
"1-250-1", "1-249-2", "1-248-3", and so on.
Planned in the uniform way to number the cell. It
Cell Identity 0-65535
consists of the CELL ID and the SECTOR ID.
8-15
Airbridge cBSC6600 CDMA Base Station Controller Chapter 9 Cell Channel Configuration
Chapter 9 Cell Channel Configuration
9.1 Overview
9.1.1 Relevant Concepts
I. SID and NID
In the CDMA network, the service area consists of systems and networks, which are
identified respectively by the system identification (SID) and network identification
(NID). Network is a sub-set of the system, as shown in Figure 9-1.
SID=M
NID= t
NID= u NID= v
SID=K
SID=L
SID=N
Figure 9-1 SID and NID
The SID is a 15-bit number. Normally, each mobile local network corresponds to a SID.
The NID is a 16-bit number, specified according to the planning of the local network.
The system judges whether the MS is roaming according to the SID and NID.
II. Location area
In the CDMA system, each MSC-covered area consists of several location areas (LAs).
When a MS enters a new LA, location update starts.
The LAs in the CDMA network are identified by the location area identity (LAI), as
shown in Figure 9-2. The LAI and Cell ID (CI) together form the cell global identification
(CGI), which exclusively identifies a cell within the global system.
LAI
MCC MNC LAC
3digits 2digits
LAI: Location area identification
LAC: Location area code
Figure 9-2 LAI structure
9-1
III. Cell and sector
Both the cell and sector are the logical IDs of a certain coverage. In this system, a cell,
identified by the CI, corresponds to an area served by a BTS. Meanwhile, a cell is
divided into several sectors, identified by the sector ID.
The sector is the basic unit for processing. Normally, the CI (12 bits) and Sector ID (4
bits) are regarded as one unit, corresponding to the CI (16 bits) in CGI, as shown in
Figure 9-3.
CGI
MCC MNC LAC CI
LAI
CGI: Cell global identification

Figure 9-3 CGI structure
IV. PN
In CDMA system, the sectors are identified by the pseudo number (PN) sequence with
a length of 215-1 bits. Different sectors are modulated using PN sequences with
different phases. The phase difference is at least 64 bits. Therefore, a maximum of 512
different phases are available. The application of the PN offset should be planned to
avoid interference.
The cell channel configuration involves the following parts.

z The configuration of cell and sector
z The configuration of sector carrier
z The configuration of carrier neighbor relation
9-2
Start
Configure
cell and sector
Configure
sector carrier
Configure carrier
Neighbor Relation
End
Figure 9-4 Procedures of cell channel configuration
9.2 Configuration of Cell and Sector

This configuration is to add cells or sectors to a certain BTS under the local BSC. The
sector added is identified by the PN. The number of sectors to be added depends on
the number of PNs. A BTS can be configured with a maximum of 36 cells.
You can add a cell or add sectors to the cell using the command ADD CELL. At most
six sectors can be added at a time.
z [BTS ID]: The ID of the BTS, to which the cell and sector are to be added.
z [Cell ID]: The cells are numbered from 1 on within local MSC.
z [Sector ID List]: The sectors are numbered from 0 on within the same cell.
z [PN code List]: The PNs corresponding to sectors. Multiple values can be entered
with commas in between, for example, "PN1, PN2, PN3".
In addition, the PN must be the integral multiple of the [Pilot PN Sequence Offset
Index], otherwise the alarm of pilot pollution may be generated during networking.
The [Pilot PN Sequence Offset Index] is configured by using the command ADD
BSCINF and its default value is "4".
z [System ID]: It is assigned within the whole CDMA network.
z [Network ID]: It is subject to the planning of local network.
z [Data Packet Area ID]: It is subject to the planning of the data traffic in each area of
local network.
z [Local Area Code]: If the MSC is set to page by LAC, the system will broadcast the
paging message to all the sectors in the corresponding LAs to page the MS.
Therefore, the setup of this parameter should be consistent with that configured on
the MSC. The [Local Area Code] is a hexadecimal number, ranging from 0 to
0xFFFF.
9-3
After the configuration, you can execute the command LST CELL to check the
configuration. If necessary, execute the command MOD CELL to modify relevant
parameters of the cell.
[Example]
Add three sectors to the BTS 0 as below.
Cell ID: 1; Sector ID List: 0, 1, and 2; PN List: 20, 24, and 28; System ID: 14001;
Network ID: 1; Data Packet Area ID: 1; Local Area Code: 0x10.
ADD CELL: BTSID=0, CN=1, SCTIDLST="0,1,2", PNLST="20,24,28", SID=14001, NID=1,
PZID=1, LAC="0x10", IFASSALW=NO;
Add three sectors to the BTS No.1.

Cell ID: 2; Sector ID List: 0, 1, and 2; PN List: 32, 36, and 40.
The other parameters are the same as those of cell No.1.
ADD CELL: BTSID=1, CN=2, SCTIDLST="0,1,2", PNLST="32,36,40", SID=14001, NID=1,
PZID=1, LAC="0x10", IFASSALW=NO;
[Relevant commands]
Table 9-1 shows the commands related to the cell and sector configuration.
Table 9-1 Commands related to the cell and sector configuration
Operation Command
Add Sectors ADD CELL
Remove Sectors RMV CELL
Modify Cell Information MOD CELL
Query Cell Information LST CELL
9.3 Configuration of Sector Carrier

9.3.1 Configuration of Local BSC Carrier
In the CDMA system, a bandwidth of 1.2288 MHz corresponds to a carrier. After the
Walsh code orthogonal modulation, the carrier can be divided into several channels,
providing communication service to multiple subscribers. Such forward channels
include the common channel and the traffic channel. The forward common channel can
be further divided into pilot channel, synchronization channel and paging channel.
The carrier of a local BSC can be classified into common carrier and pilot beacon. The
pilot beacon refers to the carrier containing forward common channels only, that is,
9-4
there is no traffic channel on pilot beacon. Instead of carrying traffic, the pilot beacon is
for guide handoff.
You can add the carrier resource to sector using the command ADD CDMACH. Each
sector can be configured with maximum six carriers.
The [Cell ID] and [Sector ID] corresponding to the carrier should be specified.
Other key parameters are described as below:
z [Carrier ID List]: By default, it is numbered from 0 on in the sector. Multiple values
can be entered with commas in between. The configuration of this parameter
should be consistent with that on the BTS.
z [Frequency Point List]: The frequency corresponding to each carrier. Multiple
values can be entered with commas in between. The number of values entered
should be consistent with that entered in the [Carrier ID List].
z [Pilot Beacon Flag]: It specifies whether the carrier added is a pilot beacon. Its
default value is No.
Note:
A cell can be configured with maximum 36 carriers and a sector can be configured with maximum six
carriers.
After the configuration, you can execute the command LST CDMACH to check the
configuration for error. You can also use the command MOD CDMACH to modify
parameters such as Carrier Gain, Frequency Point]and Pilot Priority Level.
[Example]
Add carriers with channel Nos. of "78" and "119" to sectors 0, 1 and 2 in cell 1
respectively.
Carrier IDs are "0" and "1" respectively.
The carriers added are all common carriers.
ADD CDMACH: CN=1, SCTID=0, CRRIDLST="0,1", ARFCNLST="78,119", IFBCDMACH=NO,
ECCLMFLG=YES;
ECCLMFLG=YES;
ECCLMFLG=YES;
[Relevant commands]
Table 9-2 shows the commands related to the carrier configuration of local BSC.
9-5
Table 9-2 Commands related to the carrier configuration of local BSC
Operation Command
Add Carriers ADD CDMACH
Remove Carriers RMV CDMACH
Modify Sector Carrier Parameters MOD CDMACH
Query Carrier Information LST CDMACH
9.3.2 Configuration of External Carrier
The external carrier is the carrier of a foreign BSC, a concept in contrast with the local
BSC carrier. The external carrier is for inter-BSC handoff, including soft handoff and
hard handoff.
Through the configuration of the external carrier, the local BSC can learn the carrier
resources at the neighboring BSCs for easy handoff.
The external carrier falls into common carrier and pilot beacon.
You can use the command ADD OUTCDMACH to configure external carriers of the
local BSC.
z [BTS ID]: ID of the BTS, to which the external carrier belongs. It ranges from 960 to
1919.
z [Cell ID], [Sector ID], [Frequency Point], [PN], [Local Area Code], [Bandclass] and
[MSC ID]: They should be configured according to the actual attributes of the
external carriers.
z [BSC IP Address]: IP address of the BSC, to which the external carrier belongs. If
it is set to "0", it indicates that there is no soft handoff channel between this
external carrier and the local BSC. Different carriers may have different SIDs and
NIDs. If it is not set to "0", the carriers in the same BSC must have the same SID
and NID.
z [System ID] and [Network ID]: System ID and network ID of the sector where the
external carrier is located.
z [Pseudo Pilot (Pilot Beacon) Flag]: It specifies whether the external carrier added
is a pilot beacon.
After the configuration, you can execute the command LST CDMACH to check the
configuration for error.
[Example]
Add a BSC external carrier to local MSC.
MSC ID: 0x36B102; BSC IP Address: 129.11.17.2; BTS ID: 960;
9-6
Cell ID: 10; Sector ID: 0; Local Area Code: 0x12;

System ID: 14001; Network ID: 1;
Frequency Point: 160; PN: 48; Bandclass: 800 MHz;
Pseudo Pilot Flag: No.
ADD OUTCDMACH: BTSID=960, CN=10, SCTID=0, ARFCN=160, PN=48, LAC="0x12",
BNDCLS=BC800, MSCID="0x36B102", BSCID="129.11.17.2", SID=14001, NID=1,
VHOTP=HHO, DHOTP=HHO, IFBCDMACH=NO;
[Relevant commands]
Table 9-3 shows the commands related to the external carrier configuration.
Table 9-3 Commands related to the external carrier configuration
Operation Command
Add External Carrier ADD OUTCDMACH
Remove External Carrier RMV OUTCDMACH
Modify External Carrier Parameters MOD OUTCDMACH
Query Carrier Information LST CDMACH
9.4 Configuration of Carrier Neighbor Relation

The carrier Neighbor Relation is configured for MS handoff between different carriers. It
involves the configurations of idle handoff relationship, intra-frequency handoff
relationship and inter-frequency handoff relationship.
z The configuration of the idle handoff relationship is applicable to the handoff of MS
in idle status. When the MS in idle status moves from one area to another, the MS
can detect the change of the carrier strength. By configuring the carrier
neighborhood and issuing it over the common channel, the BSC can implement
the MS handoff in idle status.
z The configuration of the intra-frequency relationship is applicable to the MS soft
handoff. When the MS in conversation moves from one area to another with the
same channel No., the MS can maintain the communication with the BTSs in
these two areas concurrently. To ensure the success of the soft handoff, it is
necessary to configure the intra-frequency relationship for the carriers with the
same channel No.
z The configuration of the inter-frequency handoff relationship is applicable to MS
hard handoff. It functions the same way as the intra-frequency handoff
relationship.
You can add the carrier neighborhood using the command ADD NBRCDMACH.
9-7
z [Central Carrier]: Carrier in the local BSC, based on which the neighborhood is
configured. Its format is BTS_ID-CN-SCTID-ARFCN (BTS ID-Cell ID-Sector
ID-Channel No.).
z [Neighbor Carrier Set]: The carrier set configured as neighboring with the central
carrier. The format is same as that of the [Central Carrier]. Multiple values can be
entered with comma in between.
z [Idle Handoff Relationship], [Inter-frequency Handoff Relationship] and
[Intra-frequency Handoff Relationship]: It can be set to "Single (Unidirectional)" or
"Null (No Neighborhood)". The "Unidirectional" means that the two carriers are
adjacent in one direction only, while "No Neighborhood" means that the carriers
are not adjacent. These two parameters should be configured according to the
actual network planning.
The neighboring relationship between carriers is bi-directional. That is, carriers A and B
become adjacent only when the A-to-B neighboring relationship and the B-to-A
neighboring relationship are both configured.
[Example]
For the channel No "78" in sectors 0, 1 and 2 of cell 1, configure them to be pair wise
adjacent for idle handoff and intra-frequency handoff.
ADD NBRCDMACH: CCDMACH="0-1-0-78", NBRCDMACHS="0-1-1-78,0-1-2-78",
SFFLAG=SINGLE, DFFLAG=NULL, NBFLAG=SINGLE;
[Relevant commands]
Table 9-4 shows the commands related to the carrier neighborhood configuration.
Table 9-4 Commands related to the carrier neighborhood configuration
Operation Command
Add Neighbor Relation ADD NBRCDMACH
Remove Neighbor Relation RMV NBRCDMACH
Query Neighbor Relation LST NBRCDMACH
9-8
Airbridge cBSC6600 CDMA Base Station Controller Chapter 10 Packet Data Service Configuration
Chapter 10 Packet Data Service Configuration
10.1 Overview
10.1.1 Packet Data Service Networking
Two modes are available for the networking of BSC packet data service.
Generally, the IP addresses of packet control function (PCF) and packet data serving
node (PDSN) are in the same network segment. The PCF and PDSN are connected
through LAN Switch, as shown in Figure 10-1.
If their IP addresses are not in the same network segment, a router is necessary for
connection, as shown in Figure 10-2. Meanwhile, a gateway must be configured on
PCF.
BSC
Internet
PCF LAN Switch
PDSN
Figure 10-1 Packet data service networking mode (1)
BSC
PCF LAN Switch
Other network Internet

equipment
Router
PDSN
Figure 10-2 Packet data service networking mode (2)
10-1
Note:
When the PDSN is connected to the PCF through router or other network equipment, it is recommended
that the router or other network equipment be configured first.
The configuration of BSC data service involves the following parts.

z The configuration of PCF
z The configuration of PCF gateway
z The configuration of PDSN
Start
Configure PCF
Are PCF and

YES
PDSN in the
same network
segment?
NO
Configure
PCF gateway
Configure PDSN
End
Figure 10-3 Procedures of data service configuration
10.2 Configuration of PCF
The configuration of PCF includes two parts.

z Adding PCF
z Setting PCF access network parameters
10-2
10.2.1 Adding PCF
In the CDMA system, the PCF processes the interface signaling and access of the
packet data service. It provides the A10/A11 interface for the system.
The CRPS or CPMS of BSC realizes PCF functions such as generic routing
encapsulation (GRE), IP route header replacement and transfer, and so on. In addition,
it provides the A10/A11 interface to the PDSN through CHAC. The reverse A8 interface
service data are converted into A10 interface service data and sent to the PDSN, while
the forward A10 interface service data are buffered and sent to BSC.
You can add a PCF using the command ADD PCF.
The parameters of this command include [Subrack No.], [PCF IP] and [PCF Subnet
Mask].
When adding PCF, the system automatically adds the IPOA link on the PCF side. As
the CPPU IP address and BSC IP address are used in this command, they must be
configured in advance. The PCF IP address must be configured in the same network
segment with these two IP addresses.
[Example]
Add a PCF:
Subrack (CRPS) No.: 2; PCF IP: 129.11.17.200; PCF Subnet Mask: 255.255.255.0.
ADD PCF: FN=2, PCFIP="129.11.17.200", PCFSNM="255.255.0.0";
[Relevant commands]
Table 10-1 shows the commands related to the PCF configuration.
Table 10-1 Commands related to the PCF configuration
Operation Command
Add a PCF ADD PCF
Remove a PCF RMV PCF
Query PCF Information LST PCF
10.2.2 Setting PCF Access Network Parameters
You can use the command MOD PCFAN to configure the PCF access network
parameters.
10-3
z [Max. Size of SDB Packet]: The short data burst (SDB) refers to the transmission
mode in which small traffic is transferred throughthe signaling link when the MS is
in dormant state.
The size of the packet refers to the size of SDB packet. When the size of packet
received by the PCF is smaller than the value specified here, the packet issent in
SDB mode. Otherwise, the traffic channel is activated to let the MS enter the active
state.
z [Use Sequence No.]: The packet sequence No. is used to guarantee the sequence
of packets. If the sequence No. is used, the CBPU re-sequences the disordered
packets according to the size of the sequence window. Use the default value “Yes
(Use)” unless the disorder of packet does not occur.
Note:
Keep the parameter [Use Sequence No.] consistent on both the PCF and PDSN sides.
[Example]
Set the [Max. Size of SDB Packet] to 250 and [Use Sequence No.] to “Yes (Use)” for
PCF.
MOD PCFAN: SDBMAXSIZE=250, IFSEQN=YES;
[Relevant commands]
Table 10-2 shows commands related to the configuration of PCF access network
parameters.
Table 10-2 Commands related to the configuration of PCF access network parameters
Operation Command
Modify PCF Access Network Parameters MOD PCFAN
Query PCF Access Network Parameters LST PCFAN
10.3 Configuration of PCF Gateway
When the PCF and PDSN are not in the same network segment, a router is required for
the networking. In this case, the PCF gateway must be configured.
The IP address of the router connected to the PCF is the PCF gateway IP address.
After the gateway configuration, the PCF can transfer the packets to the destination
PDSN through the gateway.
10-4
You can add a PCF gateway using the command ADD PCFGW. The parameters such
as Subrack No., PCF Gateway IP Address and PCF Gateway Mask should be specified.
The PCF Gateway IP Address shall be in the same network segment as the PCF IP
address. Moreover, the PCF Gateway IP Address and PCF Gateway Mask must be the
same as the IP address of the router connected to PCF.
After the configuration, the PCF gateway can be modified, queried or removed using
the relevant commands.
[Example]
Add a PCF gateway:
Subrack (CRPS) No.: 2; PCF Gateway IP Address: 129.11.17.201; PCF Gateway Mask:
255.255.0.0.
ADD PCFGW: FN=2, PCFGWIP="129.11.17.201", PCFGWSNM="255.255.0.0";
[Relevant commands]
Table 10-3 shows the commands related to the PCF gateway configuration.
Table 10-3 Commands related to the PCF gateway configuration
Operation Command
Add PCF Gateway ADD PCFGW
Remove PCF Gateway RMV PCFGW
Modify PCF Gateway Parameters MOD PCFGW
Query PCF Gateway LST PCFGW
10.4 Configuration of PDSN
As an important entity in the implementation of CDMA data service, the PDSN offers
the A10/A11 interface between PCF and PDSN to connect the user with the external
network.
You can add a PDSN using the command ADD PDSN.

z [PDSN IP Address], [Security Parameter Index], and [Key]: The configuration of
these three parameters on the PCF should be consistent with those configured on
the PDSN.
z [Encryption Algorithm], [Encryption Algorithm Mode], and [Re-transmit Protection
Mode]: The default values are recommended.
10-5
After a PDSN is added, you can use the command LST PDSN to check the
configuration. If necessary, use the command MOD PDSN to modify relevant
parameters.
[Example]
Add a PDSN whose IP address is 129.11.17.136, key is 12345678901234, and security

parameter index is 0x100. Other parameters are set to default values.
ADD PDSN: PDSNIP="129.11.17.136", SCRKEY="12345678901234", SPI="0x100";
[Relevant commands]
Table 10-4 shows the commands related to the PDSN configuration.
Table 10-4 Commands related to the PDSN configuration
Operation Command
Add PDSN ADD PDSN
Remove PDSN RMV PDSN
Modify PDSN Parameters MOD PDSN
Query PDSN Security Parameters LST PDSN
10-6
Airbridge cBSC6600 CDMA Base Station Controller Chapter 11 Circuit Data Service Configuration
Chapter 11 Circuit Data Service Configuration
11.1 Overview
In the CDMA system, the circuit data service can be handled either by the BSC or by
the MSC. However, the data configuration differs in these two cases.
11.1.1 Hardware Equipment
When the circuit data service is handled by the MSC, the interworking function (IWF)
equipment is configured in the MSC and no hardware equipment is added to the BSC.
When the circuit data service is handled by the BSC, the IWF equipment is configured
in the BSC. That is, the CDMA interworking function board (CIWF) should be added to
the BSC. One CIWF can process up to eighteen integrated IWF services.
By default, one CDMA integrated processing subrack (CIPS) is configured with two
CIWFs in slots 4 and 14, as shown in Figure 11-1. In a large-capacity BSC, the CDMA
transcoder subrack (CTCS) can also be configured with the CIWFs in slots 1 and 14.
C C C C C C C C C C C C C C C C
B F F F I E E M M E E L S S I A
I M M M W V V U U V V A P P W I
E R R R F C C X X C C P U U F E
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Figure 11-1 Location of CIWF in a CIPS
When the circuit data service is handled by the BSC, the following five parts should be
configured on the BSC.
z CIWF board
z CIWF modem parameter
z CIWF interface IP address
z CIWF IP pool
11-1
z IWF function switch parameter

When the circuit data service is handled by the MSC, you only need to modify the
software parameters on the BSC.
Start
Configure
CIWF board
Configure
CIWF modem
parameter
Configure
CIWF interface
IP address
Configure
CIWF IP pool
Configure IWF
function switch
parameter
End
Figure 11-2 Procedures of circuit data service configuration
11.2 Configuration of CIWF Board

To support circuit data service, the BSC must be configured with the CIWF.
You can execute the command ADD BRD to add a CIWF by specifying the parameters
[Subrack No.], [Slot No.] and [Board Type].
You can query the CIWF configured using the command LST BRD.
[Example]
Add two CIWFs. Subrack No.: 6 (CIPS). Slot No.: 4 and 14.
ADD BRD: FN=6, SN=4, BTP=CIWF;
ADD BRD: FN=6, SN=14, BTP=CIWF;
[Relevant commands]
Table 11-1 shows the commands related to the board configuration.
11-2
Table 11-1 Commands related to board configuration
Operation Command
Add a Board ADD BRD
11.3 Configuration of CIWF Modem Parameter

To realize the circuit data service, you can use the command MOD IWFMODEM to
modify the modem parameter, that is, the compressed attitude of modem includes A
law and µ law.
The parameters related to the command are:
z [Subrack No.] and [Slot No.]: The subrack No. and slot No. of the CIWF.
z [Modem Parameter]: The compressed attitude of the modem. U stands for µ law
and A for A law. This parameter depends on the modem type of the public
switched telephone network (PSTN) in this area.
You can query the modem parameter configured using the command LST
IWFMODEM.
[Example]
For the CIWFs in slots 4 and 14 of CIPS 6, set their external modem parameter to A law.
MOD IWFMODEM: FN=6, SN=4, PRM=A;
MOD IWFMODEM: FN=6, SN=14, PRM=A;
[Relevant commands]
Table 11-2 shows the commands related to the configuration of the CIWF modem
parameter.
Table 11-2 Commands related to the configuration of CIWF modem parameter
Operation Command
Modify CIWF Modem Parameters MOD IWFMODEM
Query CIWF Modem Parameters LST IWFMODEM
11.4 Configuration of CIWF Interface IP Address

The interface IP address of a CIWF is used to identify the CIWF to terminate the
peer-peer protocol (PPP) link between the mobile station (MS) and the CIWF. Each
11-3
CIWF shall be configured with one interface IP address, whose network segment is not
specified.
You can use the command ADD IWFITFIP to add an interface IP address to a CIWF.
z [Interface Name]: The interface name of the CIWF, which must be unique in the
subrack.
z [Interface IP Address] and [Subnet Mask]: The IP address and subnet mask of this
CIWF interface.
You can query the CIWF interface IP address configured using the command LST
IWFITFIP.
[Example]
Configure the interface name of the CIWF in slot 4 of CIPS 6 as "INTERFACE1", the IP
address of the interface as 10.11.3.1 and the subnet mask as 255.255.0.0.
ADD IWFITFIP: FN=6, SN=4, NM="INTERFACE1", IP="10.11.3.2", SNM="255.255.0.0";
Configure the interface name of the CIWF in slot 14 of CIPS 6 as "INTERFACE2", the
IP address of the interface as 10.11.3.2 and the subnet mask as 255.255.0.0.
ADD IWFITFIP: FN=6, SN=14, NM="INTERFACE1", IP="10.11.3.2",
SNM="255.255.0.0";
[Relevant commands]
Table 11-3 shows the commands related to the configuration of CIWF interface IP
address.
Table 11-3 Commands related to the configuration of CIWF interface IP address
Operation Command
Add CIWF Interface IP Address ADD IWFITFIP
Remove CIWF Interface IP Address RMV IWFITFIP
Query CIWF Interface IP Address LST IWFITFIP
11.5 Configuration of CIWF IP Pool

The IP address pool of a CIWF is used to store the IP addresses. When an MS applies
a circuit data service, the CIWF allocates an IP address to the MS from the pool.
11-4
Each CIWF in the BSC shall be configured with one IP address pool and 18 IP
addresses. The network segments of these IP addresses shall not overlap those of the
CIWF interface IP addresses.
You can use the command ADD IWFIPPOOL to add an IP address pool to a CIWF. The
following are related parameters.
z [Pool Name]: The name of the IP address pool.
z [Start IP Address] and [End IP Address]: The start and end IP addresses of the IP
address pool.
z [Subnet Mask]: Subnet mask of the IP address pool, depending on the address
range of the pool.
[Example]
Add an IP address pool named "POOL1" to the CIWF in slot 4 of CIPS 6. The start IP
address is 10.0.0.1, the end one is 10.0.0.18, and the subnet mask is 255.255.0.0.
ADD IWFIPPOOL: FN=6, SN=4, POOLNM="POOL1", SIP="10.0.0.1", EIP="10.0.0.18",
SNM="255.255.0.0";
Add an IP address pool named "POOL2" to the CIWF in slot 14 of CIPS 6. The start IP
address is 10.0.1.1, the end one is 10.0.1.18, and the subnet mask is 255.255.0.0.
ADD IWFIPPOOL: FN=6, SN=14, POOLNM="POOL2", SIP="10.0.1.1", EIP="10.0.1.18",
SNM="255.255.0.0";
[Relevant commands]
Table 11-4 shows the commands related to the configuration of the CIWF IP pool.
Table 11-4 Commands related to the configuration of CIWF IP pool
Operation Command
Add CIWF IP Pool ADD IWFIPPOOL
Remove CIWF IP Pool RMV IWFIPPOOL
Query CIWF IP Pool Information LST IWFIPPOOL
11.6 Configuration of IWF Function Switch Parameter

The IWF function is not supported by default upon the factory settings of the BSC. To
realize the IWF function, you can modify the software parameters using the command
MOD SOFTPARA. The following are related parameters.
z [Service Module No.]: CCM should be selected.
11-5
z [Soft Parameter No.]: Specified as 6.

z [Soft Parameter value]: “0x01” means to activate the IWF and “0x0” is to
deactivate the IWF.
[Example]
Activate the IWF function.
MOD SOFTPARA: SRVMN=CCM, PRMNO=6, PRMV="0x01";
Deactivate the IWF function.

MOD SOFTPARA: SRVMN=CCM, PRMNO=6, PRMV="0x0";
[Relevant commands]
Table 11-5 shows the commands related to the configuration of software parameters.
Table 11-5 Commands related to the configuration of software parameters
Operation Command
Modify Software Parameters MOD SOFTPARA
Query Software Parameters LST SOFTPARA
11-6
HUAWEI

Data Configuration of Large-capacity

BSC
Operation Manual - Data Configuration Data Configuration of Large-capacity BSC
Table of Contents

Chapter 2 CSWS Configuration ................................................................................................... 2-1

2.1 Overview of CSWS Configuration...................................................................................... 2-1
2.1.1 CSWS Hardware ..................................................................................................... 2-1
2.2 Configuration of Basic Information through Serial Port ..................................................... 2-5
2.2.1 Setting up Configuration Environment .................................................................... 2-6
2.2.2 Configuring Basic Information ................................................................................. 2-9
2.3 Formatting and Loading of CSWS Data .......................................................................... 2-11
2.4 Configuration of Service Data.......................................................................................... 2-11
2.4.1 Activating Ports ..................................................................................................... 2-12
2.4.2 Configuring Active/Standby Relation on Ports ...................................................... 2-14
2.4.3 Configuring Corresponding Relation between Subracks and Ports...................... 2-14
2.4.4 Configuring Route Data......................................................................................... 2-15

3.1 Overview ............................................................................................................................ 3-1

4.1 Overview ............................................................................................................................ 4-1
4.2.1 Adding Racks .......................................................................................................... 4-5
4.2.2 Adding Subracks ..................................................................................................... 4-6
4.2.3 Adding Boards......................................................................................................... 4-9
4.3 Configuration of Subrack Optical Interface...................................................................... 4-10
i

5.1 Overview ............................................................................................................................ 5-1
5.1.1 Transmission Synchronization ................................................................................ 5-1
5.1.2 Time Synchronization.............................................................................................. 5-1
5.1.3 Physical connection ................................................................................................ 5-2
5.4 Configuration of CRPS/CRMS CMUX ............................................................................... 5-6
5.5 Configuration of CSWS CLPC ........................................................................................... 5-7
5.6 Configuration of CMUX in Service Subrack....................................................................... 5-8

7.1 Overview ............................................................................................................................ 7-1
7.1.1 A3/A7 Interface Protocol Stacks ............................................................................. 7-1
7.5 Configuration of A3/A7 Interface PVC ............................................................................... 7-6

8.1 Overview ............................................................................................................................ 8-1
8.3.1 BTS O&M Channel.................................................................................................. 8-9
ii
iii
Chapter 1 Overview of Data Configuration
This module introduces the methods and procedures of data configuration in the
large-capacity cBSC6600 system.
Man-machine language (MML) commands are used for the data configuration. This
module describes the key parameters involved. For the rest configuration commands
and the detailed descriptions of the parameters, see the MML on-line help.
1.1 Configuration Procedures

The data configuration of large-capacity BSC covers ten sections.
1-1
CSWS
configuration
Basic information
configuration
Equipment data
configuration
Clock system
configuration
A1/A2 interface
configuration
A3/A7 interface
configuration
Abis interface
configuration
Cell channel
configuration
Packet data service

configuration
Circuit Data service

configuration
Figure 1-1 Procedures of data configuration
Note:
The procedures enclosed by dotted blocks are optional. That is, they are subject to actual application.
The following are the specific configuration procedures:

1) CSWS configuration: Configures CSWS-specific data. For details, see Chapter 2,
“CSWS Configuration”.
2) Basic information configuration: Configures some system-level parameters of
BSC. For details, see Chapter 3, "Basic Information Configuration".
3) Equipment data configuration: Configures module and hardware equipment such
as rack, subrack, and board of the large-capacity BSC. For details, see Chapter 4,
"Equipment Data Configuration".
1-2
4) Clock system configuration: Configures the clock system of large-capacity BSC.

For details, see Chapter 5, "Clock System Configuration".
5) A1/A2 interface configuration: Configures SS7 and trunk data on A1/A2 interface.
For details, see Chapter 6, "A1/A2 Interface Configuration".
6) A3/A7 interface configuration: Configures A3/A7 interface between adjacent BSCs
if the system needs to support inter-BSC soft handoff. For details, see Chapter 7,
“A3/A7 Interface Configuration”.
7) Abis interface configuration: Configures traffic and signaling data on Abis interface.
For details, see Chapter 8, "Abis Interface Configuration".
8) Cell channel configuration: Configures logic resources of the BTS, such as cell
and channel. For details, see Chapter 9, "Cell Channel Configuration".
9) Packet data service configuration: Configures the data-service-specific
parameters if the BSC needs to provide the packet data service, such as the
configuration of the packet control function (PCF), packet data service node
(PDSN), and related parameters. For details, see Chapter 10, “Packet Data
Service Configuration”.
10) Circuit data service configuration: Configures the parameters related to circuit
data services if the system needs to support circuit data services. The interworking
function (IWF) equipment may be configured in the BSC or in the MSC. For the
configurations in these two cases, see Chapter 11, “Circuit Data Service
Configuration”.
1.2 Data Configuration Mode

To configure CSWS and some interface data, you must log on to the switching module
(that is, CSWS) through Telnet. For configuration of the rest data, execute the MML
commands on the BSC service maintenance system.
You can perform the configuration using MML commands online or offline.
I. Online configuration
When the system is online, the execution of the commands modifies the data tables
and data loading files in the back administration module (BAM), and loads the modified
data to the BSC.
To set the system to online state, use the command LON.
II. Offline mode
When the system is offline, the execution of the commands modifies the data tables
and data loading files in the BAM only.
When you execute the command LON to switch over the system to online state, the
commands executed offline are loaded to the BSC automatically.
To set the system to offline state, use the command LOF.
1-3
1.3 Preparation for Data Configuration

Before data configuration, collect the following information and make relevant
preparations.
I. Networking mode
Familiarize yourself with the BSS-related networking topology structure.
II. BSC hardware information
Learn the BSC hardware configuration, including:

z Position of the rack
z Configuration of subracks and the boards equipped
z Hardware configuration of A1/A2, A3/A7 interface, and Abis interface
z Correspondence between subracks and modules
III. IP address assignment
Learn the planning and assignment of IP addresses in BSS, including:

z BSC IP address
z Signaling IP address of the CSPU
z IP address of BTS operation & maintenance (O&M) gateway
z External IP address of the CPPU
z PCF IP address
z PDSN IP address
z CIWF IP address
IV. MSC-specific data
When you configure A1/A2 interface, such data as some system parameters as well as
SS7 and trunk parameters should be consistent with those configured at the MSC. The
data includes:
z A-interface version
z MSC ID
z Network identification (NID) and system identification (SID)
z Local area code (LAC)
z Destination signaling point code (DPC)
z Originating signaling point code (OPC) and OPC-CIPS correspondence
z Type of network indicator and number of digits of signaling point code
z Cell ID
z Signaling link code (SLC) and SLC send
z No. of the timeslot occupied by the signaling link
z Signaling connection control part (SCCP) subsystem No.
z E1/T1 No., trunk group No., and circuit identification code (CIC) corresponding to
each CIPS.
1-4
V. BTS-specific data
When you configure Abis interface, the following data should be consistent with those
configured at the BTS:
z BTS signaling IP address
z BTS signaling link ID and bootstrap protocol (BOOTP) ID
z BTS O&M IP address
z BTS O&M link ID
z Connection mode and traffic link ID of Abis interface
VI. BSC-specific data
When you configure A3/A7 interface, the following data should be consistent with those
configured at the adjacent BSC:
z Local entity attribute
z A3 port No.
z A7 link ID
z A3 link IDs of the local and peer BSCs
1-5
Airbridge cBSC6600 CDMA Base Station Controller Chapter 2 CSWS Configuration
Chapter 2 CSWS Configuration
2.1 Overview of CSWS Configuration

2.1.1 CSWS Hardware
I. Function
The CSWS is installed in the BSC controlling cabinet. As the core of the BSC ATM
switching, the CSWS performs the following:
z Implement central switching.
z Provide channels for the information exchange among service processing
subracks.
z Provide system clock and maintenance management agent functions for the
service processing subracks.
Currently, the large-capacity BSC supports two hardware configuration solutions:
z CIPS
z CBMS+CTCS
Figure 2-1 illustrates the position of the CSWS in the system of CIPS solution and
Figure 2-2 shows that in the system of CBMS+CTCS solution.
to/from BTS E1/T1 Optical fiber

CIPS
E1/T1
to/from MSC
FE FE
to/from NMS CIMS
GE Optical fiber
to/from PDSN CPMS
CSWS
CLKM
GE Optical fiber
to/from PDSN CRPS
Figure 2-1 Position of CSWS in BSC system (CIPS solution)
2-1
Optical fiber
to/from BTS E1/T1
CBMS
Optical fiber
E1/T1
to/from MSC CTCS
FE FE
to/from NMS CIMS
CSWS
GE Optical fiber
to/from PDSN CPMS
CCRM
Optical fiber
CRMS
Figure 2-2 Position of CSWS in BSC system (CBMS+CTCS solution)
II. Slot configuration
With totally 15 slots, the CSWS can be configured with:

z CDMA main process unit (CMPU)
z CDMA network transfer and switch (CNET)
z CDMA line process unit with two 622 M engines(CLPC).
Figure 2-3 shows the layout of CSWS slots when fully configured.
Note:
The CLPU can replace the CLPC depending on actual requirments.
2-2
M M L L L L L N N L L L L L
P P P P P P P E E P P P P P
U U C C C C C T T C C C C C
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Figure 2-3 CSWS slot configuration
III. DIP switch
Set the DIP switches (DIP1 – DIP4) on the CSWS as follows when the system operates
normally.
Table 2-1 Setup of DIP switches on CSWS
Boards Setup of DIP switches

CMPU DIP1-ON DIP2-ON DIP3-OFF DIP4-ON
CLPC DIP1-ON DIP2-ON DIP3-OFF DIP4-ON
CNET DIP1-ON DIP2-ON DIP3-OFF DIP4-ON
I. Connections of optical fibers
As the central switching module, the CSWS connects with various service subracks of
the BSC through the CLPC. It is responsible for the switching of service data.
Figure 2-4 shows fiber connections between the CLPC and CMUXs in CDMA resource
and packet subrack (CRPS) and CDMA integrated processing subrack (CIPS).
2-3
RUN RUN RUN
ALM ALM
ACT ACT
RESET RESET
TX TX
RX RX
ETH ETH
1PPS 1PPS
COM1 COM1
COM2 COM2
CLPC CMUX (CRPS) CMUX (CIPS)
Figure 2-4 Optical connections between CLPC and service subracks
II. Connections of network cables
The network port on the CMPU in the CSWS connects to the BAM through a LAN
Switch using straight network cables, as shown in Figure 2-5. The loading and
maintenance operations on the BSC system are carried out through the network port.
RUN
ALM
ACT
LAN Switch
RESET
Straight
network cable
BAM
CMPU
Figure 2-5 Connection between the BAM and CMPU
2-4
CSWS data configuration mainly includes configuration of basic information through

serial port, formatting and loading of CSWS data, configuration of service data, and so
on. Figure 2-6 shows the configuration procedures.
Start
Configure basic
information through
serial port
Format and load

CSWS data
Configure
service data
End
Figure 2-6 Procedures of CSWS data configuration
Note:
The procedure enclosed by dotted block is optional. That is, it is subject to the actual application.
2.2 Configuration of Basic Information through Serial Port

Basic parameters information of the CSWS such as IP address and mask of CMPU
network port, IP address and mask of the BAM, and whether to load files from BAM has
been configured before the delivery of BSC equipment. If you must modify these
parameters for system expansion and other reasons, configure them through serial
port.
After the configuration, the information of these parameters is stored in Flash memory
of CMPU. Thus, when restarting the CSWS next time, there is no need to re-configure
them.
Configuration of basic information through serial port comprises two parts: Setting up
configuration environment through serial port and configuring basic information.
2-5
2.2.1 Setting up Configuration Environment
You can perform serial port configuration using the hyper terminal tool in Windows
operating system. Here take Windows2000 operation system as example for
description. The procedure of setting up configuration environment through the serial
port is as below:
1) Connect the serial port of a computer with the configuration serial port on CMPU in
CSWS through a standard RS232 serial port cable, as shown in Figure 2-7.
RU
N
ALM
ACT
RESET
Serial port
cable
Computer CMPU
Figure 2-7 Setup of the configuration environment through serial port
2) Enable the hyper terminal on the computer, and then select serial port 1 or serial
port 2 based on actual physical connection.
3) Configure the communication parameters of serial port as below: [Bits per second]:
9600, [Data bits]: 8, [Stop bits]: 1, [Parity]: None, [Flow control]: None, as shown in
Figure 2-8
2-6
Figure 2-8 Configuration of Serial Port Properties
4) Set terminal type and ASCII code, as shown in Figure 2-9 and Figure 2-10.
Figure 2-9 Setting the terminal type
2-7
Figure 2-10 Setting ASCII code
5) Enter commands through a hyper terminal for configuration, as shown in Figure

2-11
Figure 2-11 Interface of a hyper terminal
2-8
2.2.2 Configuring Basic Information
When configuring through a hyper terminal, it outputs the print information as follows,
wherein, the part in bold is the content to be configured.
After this configuration, the connection between the CSWS and BAM has been set up.
Thus, the BAM can issue operation and maintenance commands to the CSWS and the
CSWS can also download related programs and data from the BAM.
%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*
% ESR MPUB Mini BootRom Launching %
% Copyright (c) 2000-2010, Huawei Tech. Co., Ltd. %
% System Supporting Group %
%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*%*
Main Boot Porgram Exist!
To DownLoad The Program Again, Please Press 'M' Within 3 Seconds.
To Run Main Boot Program Directly, Please Press 'C'.
OutTime For Inputing Key Will Be Continued!
Will You Input Either Key[C/M]?:
Reading Main BootRom System Done.
Uncompressing Main BootRom System Done. Now Start Main BootRom...
The Size of SDRAM is 0x20000000 bytes.

Initialize PCI ...... Done!
PCI device listing ...

vendor_id dev_id bus_num dev_num func_num Class_ID cfg_addr
1057 4 0 0 0 60000 0H
14f1 8236 0 c 0 20300 6000H
8086 1209 0 d 0 20000 6800H
8086 1209 0 e 0 20000 7000H
10ad 565 0 12 0 60100 9000H
10ad 105 0 12 1 1018f 9100H
BS22MPUB BIOS V804

Copyright 2000-2010, Huawei Tech. Co., Ltd.
Read Dip Mode ... Done!

DipCode[0004]:1[ON] 2[ON] 3[OFF] 4[ON]
!!!System Running Mode For V5 Version.

--------------------------------------------------------------------
CONFIG RESUME MODE:
2-9
Resume By Configs File In Disk.

NETWORK INTERFACE PARAMETERS:
IP address on LAN1 is 10.129.10.240
LAN1 interface's subnet mask is 0xffff0000
IP address on LAN2 is 10.12.3.64
LAN2 interface's subnet mask is 0xffff0000
HARDWARE PARAMETERS:
Serial channels will use a baud rate of 9600
HARDWARE PARAMETERS:
This board's Ethernet hardware address is 00:00:F0:41:54:4D
-------------------------------------------------------------------
To change any of this, press any key within 3 seconds
Found PCI/IDE device, ID = 5

Initialized ATA hard disk ...
Hard Disk 0 Found
Model : IC25N010ATDA04-0
Serial : 170172C2265
Rev# : DACOA76A
Size : 16498944
Part ID: 1, Start : 64, Size : 4193217 WP: 0
S Cyl : 0, S_Head: 1, S_Sec: 1
E_Cyl : 1023, E_Head: 15, E_Sec: 63
Mount file system(7.0.1) ... Done!
Create dir 7.0.1/ESR...Ok!
Create dir 7.0.1/ESR/BIN...Ok!
Create dir 7.0.1/ESR/CONFIG...Ok!
Create dir 7.0.1/ESR/BIN/NEW...Ok!
Create dir 7.0.1/ESR/BIN/OLD...Ok!
Read boot file mpub.vfs from disk... OK
Running boot file...

The Size of SDRAM is 0x20000000 bytes.
Initialize PCI ...... Done!
PCI device listing ...

vendor_id dev_id bus_num dev_num func_num Class_ID cfg_addr
2-10
1057 4 0 0 0 60000 0H
14f1 8236 0 c 0 20300 6000H
8086 1209 0 d 0 20000 6800H
8086 1209 0 e 0 20000 7000H
10ad 565 0 12 0 60100 9000H
10ad 105 0 12 1 1018f 9100H
Config for 3G !
|---------------------------------------------------|
The MPU will Connect with BAM .
The config file will be Resumed from MPU disk .
The Lan2 IP is [10.12.3.64].
The Lan2 subnetMask is [255.255.0.0].
The BAM IP is [10.12.3.128].
|---------------------------------------------------|
To change any of this, press any key within 3 seconds
Connecting with BAM or not (Y or N)? [Y] Y

Resume config file by BAM (Y or N)? [N] Y
The Lan2 IP is [10.12.3.64].
The Lan2 subnetMask is [255.255.0.0].
The Connected BAM IP address(0.0.0.0 = RARP)? [10.12.3.128]
… …
… …
Boot selection :¡¡Resume by BAM !
[BINA]MPU is master board and need connect BAM.
2.3 Formatting and Loading of CSWS Data

After the installation of BAM database, there will be some initial data related to the
CSWS in the data tables. You must format the initial data and load it on the CSWS
before executing MML commands to configure related service data. The procedure of
formatting and loading CSWS data is as below:
1) Format the CSWS data with the command FMT SWDATA. After the successful
execution, a data loading file named “Bnet.dat” is generated under the directory
D:\cdma2000\LoadDATA\config on the BAM.
2) Reset the CMPU in the CSWS. Upon the restart of the CMPU, the file Bnet.dat is
automatically loaded on the CMPU.
2.4 Configuration of Service Data

The procedure of configuring service data on the CSWS comprises:
2-11
1) Activating ports
2) Configuring active/standby relation on ports
3) Configuring corresponding relation between subracks and optical ports
4) Configuring route data
The following subsections illustrate the procedure using the example hereinafter.
BSC hardware configuration is as below:
z Five subracks: CSWS, CRPS (Subrack 2), CPMS (Subrack 3), CIPS (Subrack 5),
and CIPS (Subrack 6).
z CSWS hardware configuration: CMPU (Slot 0), CLPC (Slot 3, with optical
sub-boards 0 and 2), CLPC (Slot 4, with optical sub-boards 0 and 2), and CNET
(Slot 7).
z Connections between CLPC optical ports and other service subracks:
Optical port 0 (3/0/0) of optical sub-board 0 of the CLPC in slot 3 connects with the
active CMUX of CRPS 2. Optical port 1 (3/0/1) connects with the active CMUX of
CPMS 3.
Optical port 0 (3/2/0) of optical sub-board 2 of the CLPC in slot 3 connects with the
active CMUX of CIPS 5. Optical port 1 (3/2/1) connects with the active CMUX of
CIPS 6.
The standby optical ports connect with the standby CMUXs of service subracks.
Table 2-2 lists the detailed physical connections and corresponding relation
between active and standby optical ports.
Table 2-2 Corresponding relation between service subracks and optical ports
Active optical port Standby optical port

Subrack Name Slot No./SubSlot No./Optical port Slot No./SubSlot No./Optical port
No. No.
2 CRPS 3/0/0 4/0/0
3 CPMS 3/0/1 4/0/1
5 CIPS 3/2/0 4/2/0
6 CIPS 3/2/1 4/2/1
2.4.1 Activating Ports
An ATM port, also referred to as optical port, is in non-activated state by default. You
must activate it before it can work normally.
You cannot configure active/standby relation on a non-activated port or configure
corresponding relation between the port and a subrack.
The sub-slot Nos. and optical port Nos. on a CLPC are shown in Figure 2-12.
2-12
RUN
SubSlot No.: 0
Optical port No.: 0-3
(From top to bottom)
SubSlot No.: 1
SubSlot No.: 2
SubSlot No.: 3
CLPC/CLPU
Figure 2-12 Sub-slot No. and optical port No. on a CLPC
You can use the command ACT SWATMPORT to activate an ATM port on the CLPC by
specifying the parameters [Slot No.], [SubSlot No.] and [Port No.].
[Example]
Activate all ATM ports to use on the CLPCs in Slots 3# and 4#.
ACT SWATMPORT: SN=3, SSN=0, PN=0;

[Relevant commands]
Table 2-3 lists the commands related to port activation.
Table 2-3 Commands related to port activation
Operation Command
Activate ATM Port of CSWS ACT SWATMPORT
Deactivate ATM Port of CSWS DEA SWATMPORT
Query Configuration of CSWS ATM Port LST SWATMPORT
2-13
2.4.2 Configuring Active/Standby Relation on Ports
When you configure active/standby relation on two ports of the CLPC, no permanent
virtual path (PVP) or permanent virtual connection (PVC) is allowed to exist on the two
ports. Therefore, you must configure active/standby relation on ports before configuring
corresponding relations of subracks and ports. Otherwise, a configuration error will
occur.
You can use the command ADD SWREDPORT to configure active/standby relation on
ports by specifying slot No., sub-slot No. and port No. of low-end and high-end ports
respectively.
[Example]
According to the active/standby relation on optical ports listed in Table 2-2, configure
the active/standby ports.
ADD SWREDPORT: PSN=3, PSSN=0, PPN=0, SSN=4, SSSN=0, SPN=0;
[Relevant commands]
Table 2-4 lists commands related to configuration of active/standby relation on ports.
Table 2-4 Commands related to configuration of active/standby relation on ports
Operation Command
Add Redundant Port ADD SWREDPORT
Modify Redundant Port MOD SWREDPORT
Remove Redundant Port RMV SWREDPORT
Query Port Redundancy Configuration LST SWREDPORT
2.4.3 Configuring Corresponding Relation between Subracks and Ports
Before configuring corresponding relation between subracks and ports, you must
activate the corresponding ports. You must configure corresponding relation between
the subracks (CRPS or CRMS) that generate the reduced TDMA frame number (RFN)
signal and ports firstly. Otherwise, you cannot configure the relation between other
subracks and ports.
You can use the command SET SWFRMPORT to configure corresponding relation
between subracks and ports by specifying the parameters [Subrack No.], [CLPC Slot
No.], [CLPC SubSlot No.], and [Optical Port No.].
For two ports with active/standby relation, it is required to configure one of the ports
only.
2-14
After you configure the corresponding relation between various service subracks and
ports on the CLPC, the system automatically sets up inter-subrack switching data such
as the PVP, IPOA PVC, and RFN multicasting PVC. Then you can use the commands
LST SWPVP and LST SWPVC to query the PVP and PVC connections.
[Example]
According to the information in Table 2-2, configure the corresponding relation between
subracks and ports.
SET SWFRMPORT: FN=2, SN=3, SSN=0, PN=0;
[Relevant commands]
Table 2-5 lists commands related to configuration of corresponding relation between
subracks and ports.
Table 2-5 Commands related to configuration of corresponding relation between subracks and ports
Operation Command
Set Correspondence between CBSC Subracks and ATM ports SET SWFRMPORT
RMV Correspondence between CBSC Subracks and ATM ports RMV SWFRMPORT
Query Correspondence between CBSC Subracks and ATM ports LST SWFRMPORT
2.4.4 Configuring Route Data
Configuring route data mainly comprises two parts: configuring route data on the
CSWS and configuring route data on the BAM.
I. Configuring route data on the CSWS
After configuring the corresponding relation between subracks and ports, you need to
configure the route data on the CSWS to realize the functions of route forwarding and
operation maintenance. For the CIPS and CBMS, you must also configure routes to the
BTS.
In the BSC system, the IP address of corresponding port in Subrack N is 192.1.1.N, the
address of network section in Subrack N is 80.4XN.0.0.
You can use the command ADD SWIPRT to configure route data. The following
describes the parameters in this command.
z [Destination Network IP Address]: If configuring the route to a service subracks,
you must configure it as 80.4XN.0.0. If configuring the route to the BTS, you must
configure it as 129.m.0.0.
2-15
z [Destination Address Mask]: The AND operation of the [Destination Network IP

Address] and the [Destination Address Mask] must be equal to the [Destination
Network Address]. Otherwise you cannot add the route successfully.
z [IP Address of Next Hop Route]: It is a gateway address. It must be in the same
network segment as IP interface address of 192.1.1.254.
[Example]
Configure IP routes to service subracks No.2, No.3. No.5 and No.6.
ADD SWIPRT: RTDEST="80.8.0.0", RTDESTMASK="255.252.0.0",
NEXTHOP="192.1.1.2";
NEXTHOP="192.1.1.3";
NEXTHOP="192.1.1.5";
NEXTHOP="192.1.1.6";
Configure the routes from corresponding ports of No.5 and No.6 CIPSs to the BTS.
NEXTHOP="192.1.1.5";
NEXTHOP="192.1.1.6"
[Relevant commands]
Table 2-6 lists commands related to configuration of route data.
Table 2-6 Commands related to configuration of route data.
Operation Commands
Add IP Route ADD SWIPRT
Remove IP Route RMV SWIPRT
Query IP Route LST SWIPRT
II. Configuring route data on the BAM
Since there may be several network adapters on the BAM, there are several default
BAM routes. If the route data is incorrect, the system will fail to select correct route
when operations or maintenance are issued. For example, no reply returns when the
BAM receives BOOTP information.
To configure the route from the CSWS to the BAM, proceed as follows:
1) Click [Start/Run…] in the BAM operating system, and type the command CMD in
the dialog box.
2-16
2) A command input window is displayed, as shown in Figure 2-13.

3) Execute the following commands to configure the route data.
Figure 2-13 Route data configuration
c:\>route -p add 80.0.0.0 mask 255.0.0.0 10.12.3.64

c:\>route -p add 192.1.0.0 mask 255.255.0.0 10.12.3.64
c:\>route -p add 129.0.0.0 mask 255.0.0.0 10.12.3.64
You can use the command route -p delete to delete a route configured. For example:
c:\>route -p delete 80.0.0.0
Note:
z When you use the command route -p add to add or route -p delete to delete the route data, the BAM
automatically saves the data configured.
z However, if you use the commands route add or route delete, the configured data will not be saved.
You need to re-configure it after the BAM restarts.
2-17
Chapter 3 Basic Information Configuration
3.1 Overview
The BSC basic information configuration involves the configuration of the attributes of
BSC system parameters, such as BSC IP Address, MSC ID, Market ID, Entity ID,
mobile country code (MCC), mobile network code (MNC), and A-interface Version No..
Note:
The BSC basic information is the first to be configured using MML commands.
3.2 Configuration of BSC Basic Information

You can use the command ADD BSCINF to configure basic BSC information.
The related parameters are as follows:
z [BSC IP Address]: It identifies each BSC in the same MSC for the purpose of
inter-BSC soft handoff. The MSC assigns it in the centralized way.
z [BSC Subnet Mask]: It is “255.255.0.0” by default.
z [Market ID]: It identifies the equipment made by different vendors. It is assigned
across the overall network and must be consistent with that configured at the
MSC.
z [Entity ID]: It identifies different BSC entities in the network.
z [MCC] and [MNC]: They must correspond to the first five high-order digits, as
shown in Figure 3-1. By default, they are “460” and “3” respectively.
IMSI
MCC MNC MSIN
3digits 2digits 10digits
IMSI: International mobile subscriber identity

MSIN(MIN): Mobile subscriber identification number
Figure 3-1 IMSI
z [MSC ID]: It contains six hexadecimal digits, provided by the MSC engineers. A
Market ID and an SWNO compose an MSC ID. The Market ID is the first two bytes
3-1
of the MSC ID and the SWNO is the serial No. of the MSC, corresponding to the
last byte of the MSC ID.
z [A-interface Version No.]: It specifies the protocol version of the A-interface base
station subsystem application part (BSSAP). It must be consistent with the
interface version at the MSC side.
z [Pilot PN Sequence Offset Index]: It is the PN increment for the whole BSC. By
default, it is “4”. A cell PN must be a multiple of pilot PN increment. Otherwise, a
pilot pollution alarm may occur during networking.
z [Max. SDB]: By default, it is “80”.
z [SWF Type]: Configure it according to actual conditions. In a large-capacity BSC, if
switch subrack type “8850” is used, select “SWT_8850 (8850 SWF). If switch
subrack type “8750” is used, select “SWT_8750 (8750 SWF).
z [RFN CLK Board]: Select “GCKP“or “UTCP” according to actual conditions.
z [A5 Enable Selection]: Set it to “Yes” when the system needs to support the circuit
data service and the IWF equipment is configured on the MSC. Otherwise, set it to
“No”.
After completing the configuration, you can use the command LST BSCINF to query
BSC basic information.
You can use the command MOD BSCINF to modify BSC basic information, such as
Market ID, Entity ID, MCC, MNC, A-interface Version No., and A5 Enable Selection.
[Example]
Configure BSC basic information as follows:
z BSC IP Address is 129.11.17.1.
z Mask is 255.255.0.0.
z Market ID is 14001.
z Entity ID is 5.
z Mobile Country Code is 460.
z Mobile Network Code is 3.
z MSC ID is 0x36b101.
z A-interface Version No. is ISO4.1.
z Pilot PN Sequence Offset Index Increment and Max. SDB are 4 and 80
respectively by default.
z The BSC is a large-capacity one, which is configured with the 8850 switch subrack.
The A5 interface is not required.
z The clock module uses the GCKP.
ADD BSCINF: BSCID="129.11.17.1", BSCSNM="255.255.0.0", MRKTID=14001, ENTID=5,
MSCID="0x36b101", APVER=IOS4.1, SWT=SWT_8850, RFNBRDCLK=GCKP,
A5ENABLEFLAG=NO;
[Relevant commands]
Table 3-1 shows the command related to the configuration of BSC basic information.
3-2
Table 3-1 Commands related to configuration of BSC basic information
Operation Command
Add BSC Basic Information ADD BSCINF
Modify BSC Basic Information MOD BSCINF
Query BSC Basic Information LST BSCINF
3-3
Chapter 4 Equipment Data Configuration
4.1 Overview
4.1.1 BSC Hardware System
I. System architecture
The large-capacity BSC supports two hardware configuration solutions: CIPS solution
and CBMS+CTCS solution.
In CIPS solution, BSC system comprises six functional modules:
z CDMA switch subrack (CSWS)
z CDMA integrated processing subrack (CIPS)
z CDMA resource and packet subrack (CRPS)
z CDMA packet module subrack (CPMS)
z Clock processing module (CLKM)
z CDMA integrated management system (CIMS)
Figure 4-1 shows the structure of the BSC in CIPS solution.
In CBMS+CTCS solution, independent CDMA basic processing subrack (CBMS) and
CDMA transcoder subrack (CTCS) substitute for the CIPS, and CDMA resources
management subrack (CRMS) and CPMS substitute for the CRPS.
Figure 4-2 shows the structure of the BSC in CBMS+CTCS solution.
4-1
to/from BTS E1/T1 Optical fiber

CIPS
E1/T1
to/from MSC
FE FE
to/from NMS CIMS
GE Optical fiber
to/from PDSN CPMS
CSWS
CLKM
GE Optical fiber
to/from PDSN CRPS
Figure 4-1 BSC system architecture (CIPS solution)
Optical fiber
to/from BTS E1/T1
CBMS
Optical fiber
E1/T1
to/from MSC CTCS
FE
FE CIMS
to/from NMS
CSWS
GE Optical fiber
to/from PDSN CPMS
CCRM
Optical fiber
CRMS
Figure 4-2 BSC system architecture (CBMS+CTCS solution)
II. Hierarchical structure
The hardware of BSC system is of modular structure. The whole system consists of
four levels: BSC system, rack, subrack (module), and board, as shown in Figure 4-3.
4-2
Figure 4-4 and Figure 4-5 show the hardware configuration of a BSC supporting
300,000 subscribers.
BSC system
Rack ... Rack
Subrack ... Subrack
Board ... Board
Figure 4-3 BSC hardware hierarchy
Power distribution box Power distribution box Power distribution box Power distribution box Power distribution box
Dummy
CRPS CIPS CIPS CIPS panel
Cable trough Cable trough Cable trough Cable trough Cable trough
Fan box Fan box Fan box Fan box Fan box
Air deflector Air deflector Air deflector Air deflector Air deflector
LCD
LAN Switch
Cable trough
LAN Switch
Dummy panel CIPS CIPS CIPS CIPS
Keyboard
CLKM
Cable trough
Cable trough Cable trough Cable trough Cable trough
BAM Server
Fan box Fan box Fan box Fan box
CSWS CPMS CIPS CIPS CIPS
Dummy panel Dummy panel Dummy panel Dummy panel Dummy panel
Figure 4-4 BSC hardware configuration (CIPS solution)
4-3
Power distribution box Power distribution box Power distribution box Power distribution box Power distribution box
Dummy
CRMS CTCS CBMS CTCS panel
LCD
LANSwitch
Cable trough
LANSwitch
Dummy panel CBMS CTCS CBMS CTCS
Keyboard
CCRM
Cable trough
Cable trough Cable trough Cable trough Cable trough
BAM Server
Fan box Fan box Fan box Fan box
CSWS CPMS CBMS CTCS CBMS
Dummy panel Dummy panel Dummy panel Dummy panel Dummy panel
Figure 4-5 BSC hardware configuration (CBMS+CTCS solution)
The equipment data configuration involves the configuration of:

z BSC hardware system
z Subrack loading information
z Terrestrial link of inter-subrack soft handoff (SHO)
z Module data
z Board parameters
4-4
Start
Configure
hardware
Configure subrack
optical interface
Configure
inter-subrack
soft handoff
terrestrial link
Configure
module
Configure board
parameter
End
Figure 4-6 Procedures of equipment data configuration
Note:
The procedure enclosed by dotted block is optional. That is, it is subject to the actual application.
4.2 Configuration of Hardware

4.2.1 Adding Racks
As the biggest hardware unit in BSC configuration, you must configure racks before
subracks and boards.
To add a rack, use the command ADD RCK. Specify the Rack No., Rack Type, Rack
Description, and Location of the rack to be added.
Note:
The Rack No. depends on the actual position of the rack.
4-5
[Example]
Add racks 1 and 2.
Rack Type: BSC rack; Rack Description: rack 1 and rack 2; Location: 2nd floor.
[Relevant commands]
Table 4-1 shows the commands related to rack configuration.
Table 4-1 Commands related to rack configuration
Operation Command
Add a Rack ADD RCK
Remove a Rack RMV RCK
Modify Rack Information MOD RCK
Query Rack Information LST RCK
4.2.2 Adding Subracks
The subracks to be configured in a large-capacity BSC vary with the hardware

configuration solution adopted.
In CIPS solution, the BSC supports three types of subracks, namely, CIPS, CRPS, and
CPMS.
In CBMS+CTCS solution, the BSC supports four types of subracks, namely, CBMS,
CTCS, CRMS, and CPMS.
To add a subrack, use the command ADD FRM.
The parameters related to the command are as below:
z [Subrack No.], [Rack No.] and [Position in Rack]:
Configure subrack numbers and position information according to actual situation.
Normally, configure no service processing subrack in the bottom layer and the
middle layer of the first rack. The bottom layer is always loaded with the CSWS,
whereas the middle layer is reserved for the integrated management system.
Configure the CRPS or CRMS in the top layer of the first rack, and service
processing subracks in other layers of the rack.
z [Typical Subrack]: Configure proper subracks according to the CIPS solution or
CBMS+CTCS solution supported.
z [Board Select]: Specify the board configured in the typical subrack selected.
z Other parameters.
4-6
If the CRPS or CPMS is configured as the typical subrack, specify the IP address
and subnet mask of each CPPU in it.
If the CIPS or CBMS is configured as the typical subrack, specify the
corresponding BTS gateway IP address and BTS gateway subnet mask.
If the CTCS is configured as the typical subrack, specify the No. of the CBMS
subrack controlling the CTCS.
[Example]
1) CIPS solution
Add a CRPS as below:
Subrack No.: 2; Rack No.: 1; Position in Rack: Top; Typical Subrack: CRPS.
IP Address of the CPPU in slot 11: 129.11.17.30.
Subnet Mask of the CPPU in slot 11: 255.255.0.0.
ADD FRM: FN=2, RN=1, RP=UP, FT=CRPS_CBIE,
CRPSBIEBRD=CBPU_SN1&CRMU_SN2&CRMU_SN3&CPCU_SN4&CPCU_SN5&CHAC_SN6&CMUX_SN7&
CMUX_SN8&CHAC_SN9&CBPU_SN10&CPPU_SN11&CPPU_SN12, SN11PPUIP="129.11.17.30",
SN11PPUSNM="255.255.0.0", SN12PPUIP="129.11.17.31",
SN12PPUSNM="255.255.0.0";
Add a CPMS as below:

Subrack No.: 3; Rack No.: 2; Position in Rack: Bottom; Typical Subrack: CPMS.
ADD FRM: FN=3, RN=2, RP=DWN, FT=CPMS,
PMBRD=CHAC_SN0&CHAC_SN1&CBPU_SN2&CBPU_SN3&CMUX_SN7&CMUX_SN8&CPPU_SN11&CPPU
_SN12&CPCU_SN14&CPCU_SN15, SN11PPUIP="129.11.17.32",
SN12PPUSNM="255.255.0.0";
Add a CIPS as below:

Subrack No.: 5; Rack No.: 2; Position in Rack: Middle; Typical Subrack: CIPS with
CAIE; BTS Gateway IP Address: 129.8.10.2; BTS Gateway Subnet Mask: 255.255.0.0.
ADD FRM: FN=5, RN=2, RP=MID, FT=CIPS_CBIECAIE,
CIPSBIEAIEBRD=CBIE_SN0&CFMR_SN1&CFMR_SN2&CFMR_SN3&CEVC_SN5&CEVC_SN6&CMUX_S
4-7
N7&CMUX_SN8&CEVC_SN9&CEVC_SN10&CLAP_SN11&CSPU_SN12&CSPU_SN13&CAIE_SN15,
BTSGWIP="129.8.10.2", BTSGWSNM="255.255.0.0";
Add a CIPS as below:

Subrack No.: 6; Rack No.: 2; Position in Rack: Top; Typical Subrack: CIPS with CAIE;
BTS Gateway IP Address: 129.9.10.2; BTS Gateway Subnet Mask: 255.255.0.0.
ADD FRM: FN=6, RN=2, RP=UP, FT=CIPS_CBIECAIE,
CIPSBIEAIEBRD=CBIE_SN0&CFMR_SN1&CFMR_SN2&CEVC_SN6&CMUX_SN7&CMUX_SN8&CEVC_S
N9&CEVC_SN10&CLAP_SN11&CSPU_SN12&CSPU_SN13&CAIE_SN15, BTSGWIP="129.9.10.2",
BTSGWSNM="255.255.0.0";
2) CBMS+CTCS solution
Add a CRMS as below:
Subrack No.: 2; Rack No.: 1; Position in Rack: Top; Typical Subrack: CRMS.
ADD FRM: FN=2, RN=1, RP=UP, FT=CRMS_CBIE,
RMBIEBRD=CRMU_SN2&CRMU_SN3&CMUX_SN7&CMUX_SN8;
Add a CPMS as below:

Subrack No.: 3; Rack No.: 2; Position in Rack: Bottom; Typical Subrack: CPMS.
ADD FRM: FN=3, RN=2, RP=DWN, FT=CPMS,
PMBRD=CHAC_SN0&CHAC_SN1&CBPU_SN2&CBPU_SN3&CMUX_SN7&CMUX_SN8&CPPU_SN11&CPPU
_SN12&CPCU_SN14&CPCU_SN15, SN11PPUIP="129.11.17.30",
SN12PPUSNM="255.255.0.0";
Add a CBMS as below:

Subrack No.: 5; Rack No.: 2; Position in Rack: Middle; Typical Subrack: CBMS with
CBIE but without CRMU; BTS Gateway IP Address: 129.8.10.2; BTS Gateway Subnet
Mask: 255.255.0.0.
ADD FRM: FN=5, RN=2, RP=MID, FT=CBMS_NCRMU_CBIE,
BMNRBBRD=CBIE_SN0&CFMR_SN2&CFMR_SN3&CFMR_SN4&CFMR_SN5&CMUX_SN7&CMUX_SN8&CF
MR_SN10&CFMR_SN11&CSPU_SN12&CSPU_SN13&CBIE_SN15, BTSGWIP="129.8.10.2",
BTSGWSNM="255.255.0.0";
Add a CTCS.
4-8
Subrack No.: 6; Rack No.: 2; Position in Rack: Top; Typical Subrack: CTCS with CAIE;
Control Subrack of CTCS: CBMS 5.
ADD FRM: FN=6, RN=2, RP=UP, FT=CTCS_CAIE,
TCAIEBRD=CAIE_SN0&CLAP_SN1&CEVC_SN3&CEVC_SN4&CEVC_SN5&CEVC_SN6&CMUX_SN7&CM
UX_SN8&CEVC_SN9&CEVC_SN10&CEVC_SN11&CEVC_SN12&CEVC_SN13&CEVC_SN14&CAIE_SN1
5, CFN=5;
[Relevant commands]
Table 4-2 shows the commands related to subrack configuration.
Table 4-2 Commands related to subrack configuration
Operation Command
Add a Subrack ADD FRM
Remove a Subrack RMV FRM
Query Subrack Information LST FRM
4.2.3 Adding Boards
Normally, add boards in a subrack at the same time as adding the subrack. To add a
board after the subrack configuration, use the command ADD BRD. When adding a
board, specify the Subrack No., Slot No., and Board Type of the board.
[Example]
Add a CFMR as below:
Subrack No.: 6; Slot No.:3.
ADD BRD: FN=6, SN=3, BTP=CFMR;
[Relevant commands]
Table 4-3 shows the commands related to board configuration.
Table 4-3 Commands related to board configuration
Operation Command
Add a Board ADD BRD
4-9
4.3 Configuration of Subrack Optical Interface

In a large-capacity BSC, the optical interfaces of the active and standby CMUXs in
various service processing subracks are connected with the switching subrack through
optical fibers, which serve as the path for loading services and data between subracks.
The correspondence between various service processing subracks and the optical
interfaces of switching subrack must be consistent with actual physical connection.
You can use the command ADD FRMPRTMAP to configure the correspondence
between service processing subracks and optical interfaces.
The parameters related to the command are as below:
z [SWF Type]: It depends on actual situation. In a large-capacity BSC, if 8850
switching subrack is used, set it to "SWT_8850 (8850 SWF)"; if 8750 switching
subrack is used, set it to "SWT_8750 (8750 SWF)".
z [Subrack No.]: No. of the service processing subrack connecting with the
switching subrack.
z [LPC Slot No.]: No. of the slot where the CLPC connecting with the service
processing subrack resides.
z [LPC Subslot No.]: No. of the subslot where the optical subboard resides.
z [Port No. of Optical Interface Board]: No. of the optical interface.
[Example]
Configure the correspondence between various service processing subracks and the
optical interfaces according to the configuration examples given in Chapter 2, "CSWS
Configuration".
Table 4-4 shows the specific correspondence.
Table 4-4 Correspondence between service processing subracks and optical ports
Active optical port Standby optical port

Subrack Name Slot No./SubSlot No./Optical port Slot No./SubSlot No./Optical port
No. No.
2 CRPS 3/0/0 4/0/0
3 CPMS 3/0/1 4/0/1
5 CIPS 3/2/0 4/2/0
6 CIPS 3/2/1 4/2/1
Configure the correspondence between each service processing subrack and its active
and standby optical interfaces.
ADD FRMPRTMAP: SWT=SWT_8850, FN=2, SN=SN3, SSN=0, PN=0;
4-10



[Relevant commands]
Table 4-5 shows the commands related to the configuration of subrack-optical interface
correspondence.
Table 4-5 Commands related to the configuration of subrack-optical interface correspondence
Operation Command
Add Subrack Optical Port ADD FRMPRTMAP
Remove Subrack Optical Port RMV FRMPRTMAP
Query Subrack Optical Port LST FRMPRTMAP
4.4 Configuration of Inter-subrack SHO Terrestrial Link

Configuration of SHO terrestrial link comprises the following two parts:
z Configuration of the links for BSC inter-subrack SHO.
z Configuration of A3/A7 links for inter-BSC SHO.
This section details the configuration of links for BSC inter-subrack SHO.
In an MS SHO, signals of several branches are sent through different BTSs to CFMRs
in CIPSs/CBMSs for processing. If the connected BTSs belong to different
CIPSs/CBMSs, configure the SHO terrestrial links between CIPSs/CBMSs. That is,
add an AL AAL2 link between the CBIE/CXIE/COIE and the CFMR in the neighboring
CIPS/CBMS, as shown in Figure 4-7.
4-11
C C
F B Abis
M I BTS2
R E
CIPS
AL AAL2 Link
MS
C C
F B Abis
M I BTS1
R E
CIPS
BSC
Figure 4-7 AL AAL2 link between CBIE and CFMR in neighboring CIPS
You can use the command ADD SHOLINK to add the SHO terrestrial link between
CIPSs/CBMSs.
The parameters related are as below:
z [Link Type]: Select "IBSC (INTER-SUBRACK SOFT HO LINK IN BSC)".
z [Subrack No.] and [Adjacent Subrack No.]: Nos. of the two CIPSs/CBMSs, where
the SHO terrestrial link is configured. The neighboring relation is bi-directional.
z [Bandwidth]: It depends on the actual traffic. The default value is BW1.0M (1.0M).
[Example]
Configure the SHO link between CIPS 5 and CIPS 6.
ADD SHOLINK: HOLNKTP=IBSC, FN=5, NBRFN=6, BANDWIDTH=BW1.0M;
[Relevant commands]
Table 4-6 shows the commands related to the configuration of inter-subrack SHO
terrestrial link.
Table 4-6 Commands related to the configuration of Inter-subrack SHO terrestrial link
Operation Command
4.5 Configuration of Module

Module configuration is to add the logical module attributes to a physical subrack,
including module No., protocol version, band class, and allocation of module channel
4-12
element (CE) resources. The physical subrack must be CIPS/CBMS. One CIPS/CBMS
corresponds to one module.
You can use the command ADD MDU to add module attributes to a CIPS/CBMS.
The parameters related are as below:
z [Subrack No.]: No. of the CIPS/CBMS to be added with module attributes.
z [Module No.]: It starts from 0, each corresponding to one Subrack No.
z [Protocol Version] and [Min. Protocol Version]: According to band class and actual
situation, different systems can be configured with different protocol version and
minimum protocol version to prevent the access of the MS not supported by the
BSC.
z [Bandclass]: Type of the band class supported by the module.
After the configuration, you can use the command MOD PREV to modify the BTS
protocol version and the minimum protocol version of the module.
[Example]
Configure CIPS 5 to be module 0.
Protocol Version: 6; Min. Protocol Version: 2; Bandclass: 800 MHz.
Configure CIPS 6 to be module 1.

Protocol Version: 6; Min. Protocol Version: 2; Bandclass: 800 MHz.
[Relevant commands]
Table 4-7 shows the commands related to module configuration.
Table 4-7 Commands related to module configuration
Operation Command
Add a Module ADD MDU
Remove a Module RMV MDU
Query module Information LST MDU
Modify BTS Protocol Version Level MOD PREV
4.6 Configuration of Board Parameters

Configuration of BSC board parameters covers common configuration of boards and
configuration of CEVC, CAIE, and CFMR. This section only describes some popular
configurations.
4-13
4.6.1 Modifying Loading Control Mode
In BSC system, each time when a board is reset, the data such as host program, patch
program, data files, and digital signal processor (DSP) program is loaded. Most boards
require only the host program and patch program. The CMUX, CRMU, CSPU, and
CPCU, however, also require data files. The CFMR and CEVC require DSP program as
well.
To modify loading parameters of a board, use the command MOD LODCM.
You must specify such parameters as Subrack No., Slot No., and Board Type.
The loading control modes for program/data files in the parameters include:
z BNTFLSH: Programs/data files are loaded from BAM and not written to the Flash
memory of the board.
z BTFLSH: Programs/data files are loaded from BAM and written to the board Flash
memory. It takes time to write them into the Flash memory.
z FLSH: Board program/data files are loaded directly from the Flash memory. It
takes little time.
If the board is loaded for the first time, it is suggested that you set the loading control
mode of host program to "BTFLSH (LOAD FROM BAM AND WRITE TO FLASH)", and
that of data program to "BNTFLSH (LOAD FROM BAM AND NOT WRITE TO FLASH)".
Three days after the system is in stable operation, you can use the command MOD
LODCM to modify the loading control mode of host program to be "FLSH (LOAD FROM
FLASH)”. Thus, the board can restart promptly after reset.
[Example]
Modify the loading control mode of the CMUX in slot 7 of CRPS 2.
Change the loading control mode of host program to "LOAD FROM BAM AND WRITE
TO FLASH".
MOD LODCM: BTP=CMUX, FN=2, SN=7, BINLCM=BTFLSH;
[Relevant commands]
Table 4-8 shows the commands related to the configuration of loading control mode.
Table 4-8 Commands related to the configuration of loading control mode
Operation Command
Modify Loading Control Mode MOD LODCM
Query Loading Control Mode LST LODCM
4-14
4.6.2 Modifying Subsystem Parameters
Modification of subsystem parameters involves the modification of the CPU occupancy

alarm threshold and recovery threshold for the subsystem. For the CFMR and CEVC, it
also involves the modification of the DSP occupancy alarm threshold and recovery
threshold.
Note:
Normally, default values are recommended for subsystem information of board. The default CPU
Occupancy Recovery Threshold and DSP Occupancy Recovery Threshold are 60 and the default Alarm
Thresholds for CPU and DSP occupancy are 80.
You can use the command MOD SUBSYS to modify subsystem parameters of a board.
You must specify the Subrack No., Slot No. and Board Type of the board.
For the boards such as CMUX, CSPU, CRMU, and CPCU, you must modify the
parameters of the active and the standby boards at the same time. Therefore, you do
not need to specify the [Slot No.].
[Example]
Modify the subsystem information of the CMUX in CRPS 2 as below:
CPU Occupancy Recovery Threshold: 55; CPU Occupancy Alarm Threshold: 80.
MOD SUBSYS: FN=2, BTP=CMUX, CPURCVTHD=55, CPUALMTHD=80;
[Relevant commands]
Table 4-9 shows the commands related to the configuration of subsystem parameters.
Table 4-9 Commands related to subsystem parameter configuration
Operation Command
Modify Subsystem Parameters MOD SUBSYS
Query Subsystem Parameters LST SUBSYS
4-15
Chapter 5 Clock System Configuration
5.1 Overview
In CDMA system, frame numbers on the air interface must be synchronous with the
satellite synchronization time. Therefore, the BSC must ensure transmission clock
synchronization and time synchronization. The clock system is responsible for
transmission synchronization and time synchronization of the whole BSC.
5.1.1 Transmission Synchronization
For transmission synchronization, three clock reference sources are available:

z Building integrated timing supply system (BITS) clock
z Line clock extracted from A-interface
z global position system (GPS) clock
If a BITS clock is available, you must select it. If it is unavailable, you can extract line
clocks from A-interface. The CAIE extracts a 2 MHz line clock from A-interface, and
send it through cables to the GCKP in the CLKM for processing. In this way, the
synchronization between the BSC and MSC can be ensured.
If A-interface is configured with CSTUs, the CSTU is responsible for line clock
extraction.
Line clock signals extracted by CAIEs or CSTUs are sent to GCKPs for phase-lock
processing. The 8 kHz BSC system clock generated is sent to the CMUX in
CRPSs/CRMSs, through which clock signals are sent to the CSWS through optical
fibers. The system clock is finally distributed to each service processing subrack
through the CSWS.
If you select a link clock as the system clock reference source, the active-standby lines
used to extract the line clock must be from different CAIEs/CSTUs. If possible, always
use the CAIEs/CSTUs in different CIPSs/CTCSs to extract the line clock.
5.1.2 Time Synchronization
Time synchronization of BSC is realized through satellite synchronization time

information received by the CLKM (configured with the GCKP).
From the signals received by global position system (GPS)/global navigation satellite
system (GLONASS) antenna, the CLKM extracts the 1PPS and the absolute time
information and outputs PP16S and the absolute time information to the CMUX in
CRPS/CRMS after internal processing.
5-1
Based on the signals received, the CMUX generates a periodic synchronization cell
every 320 ms, and broadcasts it to the CMUX in each CIPS/CBMS through multicast
PVC. Then, the CMUX in each CIPS/CBMS generates periodic synchronization pulses,
which are transmitted to the CFMR and CSPU using the backplane bus.
5.1.3 Physical connection
Figure 5-1 shows the BSC clock system (extracting clocks from A-interface by the CAIE)
in GCKP solution.
GCKP1 GCKP2
RUN ALM ACT COM IN0 IN1 OUT ANT RUN ALM ACT COM IN0 IN1 OUT ANT
CLK_B COM_B ETH_B CLK_A COM_A ETH_A

GCKB
RUN RUN RUN RUN
ALM ALM ALM ALM

ACT ACT ACT ACT
RESET RESET
E1/T1 E1/T1
TX TX
RX RX
E1/T1 E1/T1
E1/T1 ETH ETH E1/T1
1PPS 1PPS
COM1 COM1
E1/T1 E1/T1
COM2 COM2
CLK1 CLK1
CLK2 CLK2
CAIE 7#CMUX(CRPS) 8#CMUX(CRPS) CAIE
Figure 5-1 Physical connection of BSC clock system (GCKP solution)
The physical connection of the clock system comprises four parts:

z Part 1: Connects the ports IN0 and IN1 on the GCKP with CLK1 or CLK2 of the
active and standby CAIEs or CSTUs.
Through the lines connected, the 2 MHz line clock extracted by the CAIE or CSTU
is sent to the GCKP, and serves as the reference clock source for BSC
transmission synchronization.
The ports IN0 and IN1 on the GCKP can also be connected to the BITS clock
reference source directly.
5-2
z Part 2: Connects the 1PPS ports on the active and standby CMUXs in the
CRPS/CRMS with the ports CLK_A and CLK_B on the GCKB.
The PP16S and 8 kHz system clock output by the GCKB are received through the
lines connected.
z Part 3: Connectes the COM1 ports on the active and standby CMUXs in the
CRPS/CRMS with the ports COM_A and COM_B on the GCKB.
The absolute time information output by the GCKB is received through the lines
connected.
z part 4: Connectes the CMUX in each service processing subrack with the switch
subrack through optical fibers.
The configuration of BSC clock system involves two parts.

z The configuration of transmission synchronization.
z The configuration of time synchronization.
The configuration of time synchronization is accomplished by the system automatically.
Therefore, you only need to configure the transmission synchronization of the clock
system. Figure 5-2 shows the configuration procedures.
Start
Configure GCKP
Configure CAIE
Configure
CRPS/CRMS CMUX
Configure
CSWS CLPC
Configure CMUX
in Service Subrack
End
Figure 5-2 Procedures of clock system configuration
5-3
5.2 Configuration of GCKP

GCKP has clock sources with at most four priorities (from 0 to 3). Wherein, priorities 1
to 3 can be designated through commands, priority 0 is the clock source reserved for
the system. The GCKP can select a clock source based on the configured internal clock
reference source table.
When the BSC system transmission clock is required to synchronize with A interface
clock, you must configure the clock reference sources according to Table 5-1 (When
the standby A interface clock does not exist, you can skip the configuration.)

3 Active A interface clock source (connects to GCKP IN0 port)
2 Standby A interface clock source (connects to GCKP IN1 port)
1 (GPS clock)
0 FREE-RUNNING
When the BSC system transmission clock is required to synchronize with BITS clock,
you must configure the clock reference sources according to Table 5-2 (When the
standby BITS clock does not exist, you can skip the configuration.)

3 Active BITS clock source (connects to GCKP IN0 port)
2 Standby BITS clock source (connects to GCKP IN1 port)
1 GPS clock
0 FREE-RUNNING
GCKP selects the clock reference source based on the clock reference source table
and clock source switchover strategies. There are two switchover strategies available,
namely, auto switchover strategy and manual switchover strategy.
z Auto-switchover strategy: GCKP selects the clock source with highest priority
based on clock reference source table at priority. When the reference source with
the highest priority fails, the GCKP will search and switch over to the one with the
highest priority among the rest sources in the table. When the clock source with
the highest priority recovers, the GKCP will switch over to this source
automatically.
z Manual switchover strategy: Select a certain item in the clock reference source
table to be the system clock source using commands. The manual switchover
5-4
strategy only functions as the supplement to the auto-switchover strategy. It is

generally not recommended.
GCKP adopts auto-switchover strategy by default. If necessary, use the command
MOD GCKPPARA to modify the switchover strategy of clock source.
To add a piece of clock source record to the clock reference source table, use the
command ADD CLKSRC. parameters in the command are explained as follows:
z [Slot No.]: Slot No. where GCKP resides.
z [Clock source priority]: Priority of the clock source to be added in the clock
reference source table. The priority level ranges from 1 to 3. Level 1 is the lowest
while level 3 is the highest.
z [Clock source type]: The type of the clock source to be added. There are six clock
source types in total.
[Example]
Based on Table 5-1, configure the GCKPs in Slot 0 and Slot 1 to extract 2M clocks from
active/standby A interface clock sources respectively.

[Relevant commands]
Table 5-3 shows the commands related to configuration of the GCKP clock source.
Table 5-3 Commands related to configuration of the GCKP clock source
Operation Commands
Add Clock Source ADD CLKSRC
Modify Clock Source MOD CLKSRC
Remove Clock Source RMV CLKSRC
Query Clock Source LST CLKSRC
Modify GCKP Operation Parameters MOD GCKPPARA
Query GCKP Operation Parameters LST GCKPPARA
5.3 Configuration of CAIE

For transmission synchronization of clock system, if the BSS uses BITS clocks, it is
unnecessary to configure the CAIE. You can also skip this configuration when the BSS
5-5
uses line clocks retrieved by the CSTU from the A interface, because the CLK port on
the CSTU outputs 2 MHz clocks extracted from the optical port by default.
Therefore, the following part details how to configure the CAIE so that it can extract
A-interface line clocks properly.
You can use the command MOD BRDPARA to configure CAIE.
You must specify the [Subrack No.] of CAIE and set the [Board Type] to "CAIE".
Set other parameters as below:
z [Slot No.]: No. of the slot where the CAIE resides.
z [CAIE Clock Source]: 0 (It depends on the configuration of E1/T1 timeslots
between the BSC and MSC).
z [Extract Panel 2M Circuit Clock]: Yes (extract).
z [Output TDM8K Clock to Backplane]: No (not output).
[Example]
Configure the CAIEs in slot 15 of CIPSs 5 and 6 to extract line clocks (as the active and
standby line clock reference sources).
[Relevant commands]
Table 5-4 shows the commands related to CAIE configuration.
Table 5-4 Commands related to CAIE configuration
Operation Command
5.4 Configuration of CRPS/CRMS CMUX

For transmission synchronization of clock system, the CMUX in the CRPS/CRMS
receives 8 kHz system clocks from the GCKB through 1PPS ports. Therefore, you
should set the clock reference source of the CMUX to 1PPS port clock source.
You can use the command MOD BRDPARA to set CMUX parameters. Ensure to
specify the Subrack No. of CMUX and set the Board Type to "CMUX" and Clock Source
Selection to "CKTP5".
[Example]
Configure the clock reference source of the CMUX in CRPS 2 to be the 8 kHz clock
reference source provided by the GCKB.
5-6
[Relevant commands]
Operation Command
5.5 Configuration of CSWS CLPC

The CSWS needs to extract a line clock from the optical port connected to the
CRPS/CRMS to serve as the clock reference source of the current subrack.
If the optical ports connected to active/standby CMUXs in CRPS/CRMS are in different
CLPC, you must configure the clock source of active/standby optical ports respectively.
Otherwise, you only need to configure the clock source of active optical port.
You can use the command ADD SWCLKSRC to add clock reference source of CSWS.
The parameters in the command are explained as below:
z [Clock source grade]: The grades of clock source to be added. It ranges from 1 to
4. Level 1 is the lowest and level 4 is the highest.
z [Clock source type]: Type of the clock source to be added. To extract clock from
the optical port on the CLPC, configure it to optical port SDH.
z [Slot No.], [Subslot No.] and [Port No.]: Determine the position of optical port on
CLPC.
After configuring the clock sources for the active/standby optical ports, use the
command SET SWCLKMODE to set the switchover strategy of the clock source.
Generally, set it to "Preemptive Automatic Switchover Strategy".
[Example]
See Chapter 2 CSWS Configuration "Examples". In CRPS, the optical ports connected
to active/standby CMUX are 3/0/0 and 4/0/0 respectively. Configure the clock source
levels of the optical ports to 4 and 3 respectively, with "Preemptive Automatic
Switchover Strategy" adopted.
ADD SWCLKSRC: SRCGRD=4, SRCT=SDH, SN=3, SSN=0, PN=0;
ADD SWCLKSRC: SRCGRD=3, SRCT=SDH, SN=4, SSN=0, PN=0;
SET SWCLKMODE: CLKWMODE=PREEMPTIVE_AUTO_HANDOVER;
[Relevant commands]
Table 5-6 shows the commands related to line clock configuration of the CSWS..
5-7
Table 5-6 Commands related to line clock configuration of CSWS
Operation Commands
Add Clock Source ADD SWCLKSRC
Remove Clock Source RMV SWCLKSRC
Query Clock Source LST SWCLKSRC
Set Current Clock Mode and Switchover Strategy SET SWCLKMODE
Query Current Clock Mode and Switchover Strategy LST SWCLKMODE
5.6 Configuration of CMUX in Service Subrack

Except the CRPS/CRMS, CMUXs in other service subracks need to receive clock
reference sources from the optical port connecting with the switch subrack and then
distribute clock signals to all the boards in the subrack as working clock.
You can use the command MOD BRDPARA to set the parameters of CMUX in each
service processing subrack. Ensure to specify the Subrack No. of the CMUX and set
the Board Type to "CMUX" and the Clock Source Selection to "CKTP1".
Note:
By default, the Clock Source Selection of CMUX is "CKTP1 (8 K clock is from optical board. Select PBOP
0)". If it disagrees with actual situation, you can modify it using the command MOD BRDPARA.
[Example]
Configure CMUXs in each service processing subrack to extract clock reference
sources from optical ports.
[Relevant commands]
Operation Command
5-8
See Chapter 6, “A1/A2 Interface Configuration” of Data Configuration of Small-capacity

BSC in this manual.
6-1
7.1 Overview
7.1.1 A3/A7 Interface Protocol Stacks
A3/A7 interface is a logical interface between two neighbor BSCs to support inter-BSC
soft handoff (SHO).
The A3 interface includes A3 signaling and A3 traffic. The channels for transferring A3
signaling and A3 traffic are different. A3 traffic channels transfer user traffic and A3
signaling channels control and allocate the user traffic transferred. Figure 7-1 shows
the protocol stack for A3 signaling and Figure 7-2 shows that for A3 traffic.
The A7 interface transfers signaling messages between the source BSC and the
destination BSC. Figure 7-3 shows the protocol stack.
A3 signaling
TCP
IP
AAL5
ATM
Physical layer
Figure 7-1 Protocol stack for A3 interface signaling
User traffic frame
SSSAR
AAL2
ATM
Physical layer

Figure 7-2 Protocol stack for A3 interface traffic
7-1
IOS application
TCP
IP
AAL5
ATM
Physical layer
Figure 7-3 Protocol stack for A7 interface
A large-capacity BSC provides A3/A7 interface through the CLPC in the CDMA switch
subrack (CSWS). Optical fibers connect the CLPCs in the CSWSs of the neighbor
BSCs.
Configured in the slots for universal boards in the CSWS, each CLPC provides two 622
M line processing engines to process eight 155 Mbit/s ATM optical interfaces.
The configuration of the A3/A7 interface involves the following parts.

z Basic information of Neighbor BSC
z PVC of A3/A7 interface
z A7 link
z A3 link
z Territorial link of Inter-BSC SHO
7-2
Start
Configure
neighbor BSC
Configure A7 link
Configure A3 link
Configure PVC of
A3/A7 interface
Configure
inter-BSC
soft handoff
terrestrial link
End
7.2 Configuration of Neighbor BSC

Through basic information configuration, you can add some parameters of system level
to the neighbor BSC. For one BSC, you can add five neighbor BSCs at most.
To add basic information of neighbor BSC, use the command ADD NBRBSC.
z [Neighbor BSC IP Address]: It identifies the BSCs in an MSC for the purpose of
inter-BSC SHO, uniformly allocated by the MSC.
z [Peer Market ID]: It identifies the equipment of different vendors, uniformly
allocated by the whole network. It should be identical with that configured at the
MSC.
z [Peer Entity ID]: It identifies different BSC entities.
z [Local Entity Attribute]: It specifies whether the local BSC acts as a server or a
client. BSCs are connected through transport control protocol (TCP). Therefore,
for two neighbor BSCs, you must configure one as server and the other as client.
z [A3 Port No. Sequence]: It specifies the No. of the A3 port. You can enter several
values separated by commas.
[Example]
Add basic information of an neighbor BSC as below:
z Neighbor BSC IP Address: 129.11.17.10
7-3
z Peer Market ID: 14001

z Peer Entity ID: 6
z Local Entity Attribute: Server
z A3 Port No. Sequence: 5600 and 5601
ADD NBRBSC: BSCID="129.11.17.10", MRKTID=14001, ENTID=6, ENTATTR=SVR,
A3PNLST="5600,5601";
[Relevant commands]
Table 7-1 shows the commands related to the configuration of basic information of
neighbor BSC.
Table 7-1 Commands related to the configuration of neighbor BSC
Operation Command
Add Neighbor BSC ADD NBRBSC
Remove Neighbor BSC RMV NBRBSC
Query Neighbor BSC Basic Information LST NBRBSCINF

A7 interface signaling channels are carried through permanent virtual connections
(PVCs). When establishing the A7 link between two neighbor BSCs, you must
configure the corresponding PVC parameters and specify the virtual path identifier (VPI)
and the virtual channel identifier (VCI).
You can use the command ADD A7LNK to add A7 physical link PVCs to an neighbor
BSC.
z [Neighbor BSC IP address]: It should be consistent with the IP address configured
in the basic information of neighbor BSC.
z [Connection mode]: Set it to “OPTLNK”.
z [A7 link identifier]: It identifies the parameters of A7 link PVC, that is, the VPI/VCI
value. It must be consistent with that configured at the peer BSC.
[Example]
Add an A7 link to an neighbor BSC.
Neighbor BSC IP Address: 129.11.17.10; A7 Link Flag: 8-60.
ADD A7LNK: BSCID="129.11.17.10", LM=OPTLNK, A7LFLG="8-60";
[Relevant commands]
7-4
Operation Command

You must configure two A3 links (local and peer) should be configured for the A3
interface between neighbor BSCs and specify the corresponding AAL2 link flags.
To add A3 physical link PVCs to an neighbor BSC, use the command ADD A3LNK.
in the basic information of neighbor BSC.
z [Connection Mode]: Set it to “OPTLNK”.
z [Local A3 Link Flag] and [Peer A3 Link Flag]: AAL2 link flag for the local A3
interface and that for the peer A3 interface. You must configure them separately.
Ensure to configure parameters of the corresponding link such as VPI, VCI, and
VCCI (PVC index No.). The entered format is VPI-VCI-VCCI. If you need to
configure several AAL2 links, separate the parameters with commas. Local link
flags must differ from peer link flags. However, they must be consistent with those
configured at the peer BSC.
z [Link Bandwidth]: Bandwidth of A3 interface traffic link. It depends on the actual
traffic requirements. The total bandwidth of traffic links shall not be more than that
of physical links.
[Example]
Add an A3 link to an neighbor BSC.
Neighbor BSC IP Address: 129.11.17.10; Local A3 Link Flag: 8-61-1; Peer A3 Link Flag:
8-62-2; Link Bandwidth: 2.4 M.
ADD A3LNK: BSCID="129.11.17.10", LM=OPTLNK, CA3LFLG="8-61-1",
PA3LFLG="8-62-2", LNKBW=BW2.4M;
[Relevant commands]
Operation Command
7-5
7.5 Configuration of A3/A7 Interface PVC

In the large-capacity BSC system, you must configure at least three PVCs to support
inter-BSC SHO, including one AAL5 link at the A7 interface and two or more AAL2 links
at the A3 interface. One of the two links at the A3 interface is provided for the local BSC
and the other for the peer BSC. Similarly, you need to configure PVC links to the local
BSC in the peer neighbor BSC.
Seen from the CSWS, the PVC links connect the CMUXs in the CRPS/CRMS to the
optical interfaces (connecting the neighbor BSC) in the CLPC.
Figure 7-5 shows the specific connections.
Optical interface 4/2/4
8-61 Optical interface 3/0/0 8-61

8-62 8-62
C C C C
R M M R
M U U M
U X X U
CRPS/CRMS CSWS CSWS CRPS/CRMS

8-60 8-60
Local BSC Adjacent BSC
AAL2 PVC
AAL5 PVC
Figure 7-5 PVC connection between BSCs
You can configure the PVC links of A3/A7 interface by logging in to the CSWS through
the Telnet.
7.6 Configuration of Inter-BSC SHO Terrestrial Link

Through this terrestrial link configuration, you can configure SHO terrestrial links
between the boards in the BSC border subrack and the CMUX in the CRPS/CRMS to
transfer SHO messages.
To add terrestrial links for inter-BSC SHO, use the command ADD SHOLINK.
z [Link Type]: Select “OBSC (inter-BSC SHO A3/A7 link)”.
z [Border Subrack No.]: If the cells contained in a CIPS/CBMS reside at the BSC
border, you must specify the CIPS/CBMS as border subrack when an inter-BSC
SHO is triggered.
z [Link Bandwidth]: It depends on the actual traffic requirements. It is BW1.0M (1.0M)
by default.
7-6
[Example]
Set CIPSs 5 and 6 as border subracks and add a terrestrial link for inter-BSC SHO.
[Relevant commands]
Table 7-4 shows the commands related to the configuration of terrestrial link for
inter-BSC SHO.
Table 7-4 Commands related to the configuration of terrestrial link of inter-BSC SHO
Operation Command

Table 7-5 lists the data requiring negotiation when two neighbor BSCs are
interconnected.
Table 7-5 Data to be negotiated for interconnection of neighbor BSCs

Neighbor BSC IP
Allocated uniformly within the whole MSC.
address
Used together with entity ID to identify the source
Peer Market ID 0–65535
BSC during inter-BSC SHO.
The IDs of the entities must be different within the
Peer Entity ID 0–65535
range of one operator. See Market ID for details.
It is meaningful only when a peer entity is configured.
Local Entity Attribute Server/client
One acts as the server and the other as the client.
Several values can be configured. A BSC can
A3 Port No. 1–65535
provide up to 12 A3 ports to the neighbor BSC.
It must be identical with the A7 link flag of the
A7 Link Flag VPI-VCI
neighbor BSC.
VPI-VCI-VCCI value of the ATM link The Local A3 Link Flag must be identical with the
Local A3 Link Flag/ corresponding to the A3 link flag. Peer A3 Link Flag configured at the neighbor BSC.
Peer A3 Link Flag Number it in the sequences like The Peer A3 Link Flag must be identical with the
"1-250-1", "1-249-2" and "1-248-3". Local A3 Link Flag configured at the neighbor BSC.
7-7
Chapter 8 Abis Interface Configuration
8.1 Overview
8.1.1 Abis Interface Protocol Stack
As the logical interface between the BSC and the BTS, the Abis interface comprises the
Abis signaling, Abis traffic and operation and maintenance link (OML) signaling. The
following is function description of the three parts.
z Abis signaling part serves as the channel transferring signaling between the BSC
and the BTS. Figure 8-1 shows the signaling protocol stack of the Abis interface.
z Carrying the subscriber traffic, the Abis traffic part serves as the interface between
SDU of BSC and the channel element of BTS. Figure 8-2 shows the Abis interface
traffic protocol stack.
z OML signaling part implements relevant operation and maintenance. At Abis
interface, IPOA channel is set up, serving as OML.
A bis S ign a lin g A p plic a tio n
TCP
IP
AAL5
AT M
P h ys ic a l L a ye r

Figure 8-1 Abis interface signaling protocol stack
Abis Traffic
SSSAR
AAL2
ATM
Physical Layer

Figure 8-2 Abis interface traffic protocol stack
8-1
The CBIE/CXIE in the CIPS/CBMS provides Abis interface. Table 8-1 shows the
features of these boards. This chapter introduces the configuration of Abis interface
when the CBIE is used.
Table 8-1 Features of Abis interface board
Board Function
Each CBIE provides 32 E1/T1 interfaces for the transmission of ATM cells. It supports
CBIE
CXIE
The Abis interface configuration involves the following parts.

z Abis interface connection mode
z BTS basic information
z BTS OML
z BTS signaling link
z BTS traffic link
The last three configuration items are related to the OML signaling, Abis signaling and
Abis traffic in the Abis interface signaling protocol stack.
8-2
Start
Configure
Abis interface
connection mode
Configure BTS
basic information
Configure
OML
Configure
signaling link
Configure
traffic link
End
Figure 8-3 Procedures of Abis interface configuration
8.2 Configuration of Abis Interface Connection Mode

The Abis interface supports multiple connection modes.
z IMA group (including IMA link or fractional IMA link)
z UNI link
z Electrical interface fractional ATM link
Table 8-2 details the connection modes.
Table 8-2 Abis interface connection mode
Corresponding
Connection mode Object included Object configured
board type
CBIE/CXIE IMA link E1/T1
IMA group E1/T1 and its
CBIE Fractional IMA link
timeslots
UNI link CBIE/CXIE None E1/T1
E1/T1 and its
Fractional ATM link CBIE None
timeslots
Note that each interface board allocates its own E1s/T1s and their timeslot resources to
avoid repetition in the configuration.
8-3
One CBIE provides 32 E1s/T1s, which are allocated into four ports (eight E1s/T1s for
each port), numbered 0, 1, 2, and 3 from the bottom up. It can support multiple
connection modes such as the IMA group, UNI link and fractional ATM link. When
configured, the IMA group can be numbered from 0 to 31.
One CXIE provides 24 E1s/T1s, which are allocated into three ports (eight E1s/T1s for
each port), numbered 0, 1, and 2 from the bottom up. It can only support the IMA group
and UNI link. Table 8-3 lists the value range of the E1/T1 Nos. and IMA group Nos.
corresponding to different ports upon the configuration of the IMA group.
Table 8-3 Correspondence of E1/T1 Nos. and IMA group Nos. on a CXIE
Port E1/T1 No. IMA group No.

0 0-7 0-3
1 8-15 4-7
2 16-23 8-11
The following details the configuration of different connection modes of the Abis
interface.
8.2.1 Configuration of IMA Group
more links for transmission to realize the dynamic expansion of bandwidth. For the
IMA-related fundamentals, see section 4.4.1, “Adding IMA Group and Link”.
You can configure IMA links and CBIE fractional IMA links in the IMA group.
I. Adding IMA group and link
You can execute the command ADD IMAGRP to add IMA groups and IMA links for the
Abis interface to the CBIE/CXIE. The following are related parameters.
CBIE/CXIE (to which IMA group belongs) resides.
z [Board Type]: Select the CBIE or CXIE according to the actual application.
z [IMA Group No.] and [E1/T1 No. List]: The IMA group No. and E1/T1 No.
corresponding to IMA link in the group.
After completing the configuration, you can use the command LST IMAGRP to query
the IMA group information, ADD IMALINK to add or RMV IMALNK to remove an IMA
link.
[Example]
8-4

[Relevant commands]
Table 8-4 shows the commands related to adding IMA group and links.
Table 8-4 Commands related to adding IMA group and links
Operation Command
Query IMA Group and Link LST IMAGRP
Add IMA Link ADD IMALNK
Remove IMA Link RMV IMALNK
Query IMA Links LST IMALNK
II. Adding IMA group and fractional IMA link
You can use the command ADD FRACIMAGRP to add IMA groups and fractional IMA
links to the CBIE. The following are related parameters.
which IMA group belongs) resides.
z [IMA Group No.]: The No. of the IMA group.
z [E1 No.]/[T1 No.]: The No. of the E1/T1 where the fractional ATM link to be added
resides.
After completing the configuration, you can use the command LST FRACIMAGRP to
query the IMA group information, ADD FRACIMALNK to add or RMV FRACIMALNK
to remove a fractional IMA link.
8-5
Note:
z In one IMA group, the IMA link and the fractional IMA link cannot coexist.
z The number of timeslots occupied by each fractional IMA link in an IMA group shall be the same.
z Multiple fractional IMA links can be configured on an E1/T1 circuit.
[Example]
Add IMA group 0 to the CBIE in slot 0 of CIPS 5. The Nos. of fractional IMA links are 1
and 2. The two links occupies timeslots 1 to 15 and 17 to 31 of No.0 E1 respectively.
TS_1&TS_2&TS_3&TS_4&TS_5&TS_6&TS_7&TS_8&TS_9&TS_10&TS_11&TS_12&TS_13&TS_14
&TS_15, TXCLKMD=CTC, TXFRMLEN=L128, IMAVER=VER11;

TS_17&TS_18&TS_19&TS_20&TS_21&TS_22&TS_23&TS_24&TS_25&TS_26&TS_27&TS_28&TS
_29&TS_30&TS_31;
[Relevant commands]
Table 8-5 shows the commands related to the configuration of IMA group and fractional
IMA link.
Table 8-5 Commands related to the configuration of IMA group and fractional IMA link
Operation Command
Add IMA Group and Fractional IMA Link ADD FRACIMALNK
Add Fractional IMA Link ADD FRACIMALNK
Remove Fractional IMA Link RMV FRACIMALNK
Query Fractional IMA Links LST FRACIMALNK
8.2.2 Configuration of UNI Link
The UNI mode is applied to transmit ATM cells on one E1/T1.

You can execute the command ADD UNILNK to add UNI links for the Abis interface to
the CBIE/CXIE. The following are related parameters.
CBIE/CXIE (to which the UNI link belongs) resides.
8-6
z [E1/T1 No.]: The No. of the E1 of the UNI link to be configured. The No. of E1s/T1s
on the CBIE: 0 to 31; No of E1s/T1s on the CXIE: 0 to 23.
[Example]

[Relevant commands]
Table 8-6 shows the commands related to the configuration of UNI link.
Table 8-6 Commands related to the configuration of UNI link
Operation Command
Remove UNI Link RMV UNILNK
Query UNI Link LST UNILNK
8.2.3 Configuration of Fractional ATM Link
The fractional ATM link can be configured to the CBIE.

You can use the command ADD EFRACATM to add the fractional ATM link to the CBIE.
which the fractional ATM link belongs) resides.
z [E1 No.]/[T1 No.]: The No. of the E1/T1 where the electrical interface fractional
ATM link to be added resides.
[Example]
Add one electrical interface fractional ATM link to the CBIE that resides in slot 0 of the 5
CIPS 5. The link No. is 8 and the link occupies the timeslots 0 to 15 of the No. 8 E1.
ADD EFRACATM: FN=5, SN=SN0, FRACATMID=8, E1T1MODE=E1, E1NO=8,
E1TSBITMAP=TS_1&TS_2&TS_3&TS_4&TS_5&TS_6&TS_7&TS_8&TS_9&TS_10&TS_11&TS_12&
TS_13&TS_14&TS_15;
[Relevant commands]
Table 8-7 shows the commands related to the configuration of the fractional ATM link.
8-7
Table 8-7 Commands related to the configuration of fractional ATM link
Operation Command
Remove Electrical Port Fractional ATM Link RMV EFRACATM
Query Electrical Port Fractional ATM Link LST EFRACATM
8.3 Configuration of BTS Basic Information

The configuration of BTS basic information is to add a BTS , a cascaded BTS in the
BSC or a BTS outside the BSC. The basic BTS information includes the following.
z module No.
z BTS ID
z BTS Name
z IP address of BTS operation and maintenance
z IP address of BTS signaling.
Other commands shall be used to add OML link, Abis signaling link, and traffic link for
the BTS.
You can use the command ADD BSCBTSINF to configure the BTS basic information.
z [BTS Type]: Type of the BTS to be added, including BTS inside the BSC,
cascaded BTS in the BSC, and BTS outside the BSC.
z [Module No.]: No. of the module corresponding to the BTS to be added. In the BSC,
each module corresponds to a CIPS/CBMS.
z [BTS ID]: It identifies a BTS in a BSC. Its configuration must be consistent with that
on the BTS.
z [BTS Name]: It describes a BTS to be added. If nothing is entered, the BTS will be
named as "BTS000+ [BTS ID]" by default.
z [BTS Operation Maintenance IP Address]: It shall be configured with the same
network segment as BTS operation & maintenance gateway of the corresponding
CIPS/CBMS. For details of this parameter, see 8.3.1 BTS O&M Channel.
z [BTS Signaling IP Address]: It shall be configured within the same network
segment as internal IP address of the CSPU of the corresponding CIPS/CBMS. It
is used for the communication between the CSPU of the CIPS/CBMS subrack and
the signaling processing module of the BCKM in the BTS. For details of this
parameter, see 8.3.2 BTS Signaling Channel.
[Example]
Add a BTS inside the BSC:
8-8
Module No.: 0; BTS ID: 0; BTS Name: BTS-A; BTS Operation Maintenance IP Address:
ADD BSCBTSINF: BTSTP=IBSC, MN=0, IBTSID=0, BTSNM="BTS-A", OMIP="129.8.10.4",
SIGIP="80.21.130.116";
Add a BTS cascaded with module1 in the BSC:

Module No.: 1; BTS ID: 1; BTS Name: BTS-B; BTS Operation Maintenance IP Address:
ADD BSCBTSINF: BTSTP=IBSC, MN=1, IBTSID=1, BTSNM="BTS-B", OMIP="129.9.10.5",
SIGIP="80.25.130.116";
[Relevant commands]
Table 8-8 shows the commands related to the configuration of BTS basic information.
Table 8-8 Commands related to the configuration of BTS basic information
Operation Command
Add BTS Basic Information ADD BSCBTSINF
Remove BTS Basic Information RMV BSCBTSINF
Query BTS Basic Information LST BSCBTSINF
8.3.1 BTS O&M Channel
In a large-capacity BSC, Figure 8-4 shows the O&M channel between the BSC and
BTS. This channel spans the following network segments before it reaches BTS:
z Network segment 10.12.3.0 (mask: 255.255.255.0) between the BAM and the
CSWS CMPU
z Network segment 192.1.1.0 (mask: 255.255.255.0) between the CMPU of CSWS
and the CMUX of CIPS/CBMS
z Network segment 129.m.10.0 (mask: 255.255.255.0) between the CMUX of
CIPS/CBMS and the BTS
8-9
192.1.1.0 10.12.3.0
129.m.10.0
BTS 129.m.10.4
129.m.10.5 CMUX CMPU

BTS BAM
129.m.10.n 10.12.3.64
BTS 129.m.10.6 TCP/IP TCP/IP TCP/IP 10.12.3.128
192.1.1.f 192.1.1.254
BTS 129.m.10.N
BSC
Figure 8-4 O&M channel between BSC and BTS (large-capacity BSC)
The IP addresses of the CMUX in the CIPS/CBMS are 129.m.10.n and 192.1.1.f, where
"m" starts from 8 and increases along with the No. of the CIPS/CBMS, "n" ranges from
1 to 3 and "f" is the No. of the CIPS/CBMS where the CMUX resides.
"129.m.10.n" is the IP address of BTS O&M gateway in the CIPS/CBMS.
The BTS O&M IP address is 129.m.10.N. The "m" equals the one in the IP address of
CMUX. The "N" is related with BTS ID, starting from 4 and increases along with the
BTS ID.
8.3.2 BTS Signaling Channel
Communication on the signaling part of the Abis interface relies on the transport control
protocol (TCP)/IP. The BSC CSPU processes interface signaling and call signaling, and
distributes service processing resources.
You must locate BTS signaling IP addresses at the same segment as internal IP
addresses of the CSPU in the corresponding CIPS/CBMS, as shown in Figure 8-5.
80.m.130.0
BTS 80.m.130.116
BTS 80.m.130.117 CSPU

BTS 80.m.130.118 TCP/IP 80.m.130.0
BSC
BTS 80.m.130.n
Figure 8-5 BTS signaling channel
The IP address of CSPU is 80.m.130.0 (mask: 255.255.0.0), where

m=f%4+1
Here, "f" refers to the No. of the CIPS/CBMS where the CSPU resides.
The IP address of BTS signaling is 80.m.130.n (mask: 255.255.0.0), where
8-10
m=f%4+1
Here, "f" refers to the No. of the CIPS/CBMS where the CSPU resides. Starting from
116, "n" is related to the BTS ID and increases along with the BTS ID.
8.4 Configuration of BTS O&M Link

The BTS O&M link configuration is to set up the O&M IPOA channel for a BTS inside
the BSC, through which operation and maintenance are implemented and BOOTUP
information of BTS is obtained. One BTS can be configured with one O&M link only.
The O&M IPOA channel is carried by a PVC. To set up the PVC link for the BSC-to-BTS
O&M channel, the parameters related to the PVC from the CBIE/CXIE to the CMUX in
the same CIPS/CBMS must be configured. The system generates other data
automatically.
You can use the command ADD BTSOMLNK to configure the BTS O&M link.
z [BTS ID]: No. of the BTS to which the O&M link is added.
specify the logical link on the Abis interface. This parameter might vary with the
connection mode.
z [BOOTP ID]: It specifies parameters of the PVC connecting the CBIE/CXIE to the
CMUX of the same subrack. The BTS uses this PVC link for BOOTP request. The
recommended value range of VPI is 2 to 15, and that of VCI is 32 to 80.
z [Operation Maintenance Link ID]: It specifies parameters of the PVC connecting
CBIE/CXIE to CMUX of the same subrack. The BSC uses this PVC link to operate
and maintain the BTS. The recommended value range of VPI is 1 to 64, and that of
VCI is 81 to 255. The VPI/VCI value shall be unique.
[Example]
Add a BTS O&M link:
Add a BTS O&M link:

8-11

[Relevant commands]
Table 8-9 shows the commands related to the BTS O&M link configuration.
Table 8-9 Commands related to BTS O&M link configuration
Operation Command
Add BTS O&M Link ADD BTSOMLNK
Remove BTS O&M Link RMV BTSOMLNK
8.5 Configuration of BTS Signaling Link

The configuration of BTS signaling link is to add the signaling IPOA channel for a BTS
inside the BSC. Each BTS can be configured with one signaling link.
The BTS signaling IPOA channel is carried by a PVC. Therefore, to establish the Abis
signaling link of the BTS, the parameters related to the PVC from the CBIE/CXIE to the
CSPU in the same CIPS/CBMS must be configured. The VPI and VCI values should be
specified.
You can use the command ADD BTSSIGLNK to add a BTS Abis signaling link.
z [BTS ID]: No. of the BTS to which Abis signaling ink is added.
connection mode.
z [Abis Link ID]: It specifies the parameters of the PVC connecting CBIE/CXIE of the
BTS to CSPU in the same subrack. The recommended value range of VPI is 1 to
64, and that of VCI is 32 to 255. The VPI/VCI value shall be unique.
[Example]
1-254.
LNKBW=BW110K;
8-12

1-254.
LNKBW=BW110K;
[Relevant commands]
Table 8-10 shows the commands related to the configuration of the BTS signaling link.
Table 8-10 Commands related to the configuration of the BTS signaling link
Operation Command
Add BTS Signaling Link ADD BTSSIGLNK
Remove BTS Signaling Link RMV BTSSIGLNK
8.6 Configuration of BTS Traffic Link

The configuration of the BTS traffic link is to add an AAL2 traffic link between the
CBIE/CXIE of CIPS/CBMS and the BTS.
You can use the command ADD BTSTRFLNK to configure the BTS traffic link.
z [BTS ID]: No. of the BTS to which traffic link is added.
z [Subrack No.] and [Slot No.]: Nos. of the subrack and the slot where the
CBIE/CXIE resides.
connection mode.
z [Traffic Link ID List]: When the AAL2 traffic link is added, parameters such as VPI,
VCI, VCCI (PVC index) of the corresponding ATM link must be specified. The input
format is VPI-VCI-VCCI. If multiple AAL2 traffic links are added, use comma to
separate the parameters. Its configuration must be consistent with that on the BTS.
The recommended value range of VPI is 1 to 64, and that of VCI is 32 to 255.
z [Link Bandwidth]: It specifies the total bandwidth of the BTS traffic links. The
default bandwidth of one traffic link is 1.6 Mbit/s. The total bandwidth of traffic links
configured for the BTS shall not be more than that of physical links.
[Example]
8-13

[Relevant commands]
Table 8-11 shows the command related to of the configuration of BTS traffic link.
Table 8-11 Commands related to of the configuration of BTS traffic link
Operation Command
Add BTS Traffic Link ADD BTSTRFLNK
Remove BTS Traffic Link RMV BTSTRFLNK

Table 8-12 lists the data that should be consistent on the BSC and the MSC when BSC
is interconnected with BTS.
Table 8-12 Negotiation data for BSC-to-BTS interconnection

BTS inside the BSC: 0-959 IDs of BTSs controlled by the same BSC are
BTS ID
BTS outside the BSC: 960–1919 allocated in a uniform way.

VPI: 2-15 CBIE/CXIE of CIPS/CBMS to the CMUX in the
BTS BOOTP ID same subrack.
VCI: 32-80
The BTS uses this PVC link for BOOTP request.
CBIE/CXIE of CIPS/CBMS to the CMUX in the
VPI: 1-64
BTS O&M link ID same subrack.
VCI: 81-255
This PVC link is used to operate and maintain
the BTS.
8-14

129.m.10.N:
The "m" here equals to the one in IP address
BTS O&M IP Its configuration must be consistent with that on
of the CMUX on the CIPS/CBMS.
address the BTS.
Starting from 4, the "N" is related to the BST
ID and increases along with the BTS ID.
80.m.130.n (mask: 255.255.0.0):
m = f % 4 + 1.
"f" refers to the No. of CIPS/CBMS where It must be in the same network segment as the
BTS signaling IP
CSPU of BTS signaling processing unit CSPU IP address. Its configuration must be
address
resides. consistent with that on the BTS.
“n” starts from 116 and is related to the BTS
ID. It increases along with the BTS ID.
BSC signaling IP The configuration on the BSC must be

80.m.130.0
address consistent with that on the BTS.
Carrier ID It is numbered from 0 within the same sector.

The "VPI-VCI-VCCI" of ATM link
corresponding to the traffic link ID. The configuration on the BSC must be
Traffic link ID
It is usually numbered in the way like consistent with that on the BTS.
"1-250-1", "1-249-2", "1-248-3", and so on.
Planned in the uniform way to number the cell. It
Cell Identity 0-65535
consists of the CELL ID and the SECTOR ID.
8-15
Chapter 9 Cell Channel Configuration
See Chapter 9, “Cell Channel Configuration” of Data Configuration of Small-capacity

BSC in this manual.
9-1
Chapter 10 Packet Data Service Configuration
See Chapter 10, “Packet Data Service Configuration” in Data Configuration of

Small-capacity BSC in this manual.
10-1
Chapter 11 Circuit Data Service Configuration
See Chapter 11, “Circuit Data Service Configuration” of Data Configuration of

Small-capacity BSC in this manual.
11-1
HUAWEI

Abbreviations and Acronyms

Operation Manual - Data Configuration Abbreviations and Acronyms
Table of Contents
Appendix A Abbreviations and Acronyms .................................................................................A-1
i
Airbridge cBSC6600 CDMA Base Station Controller Appendix A Abbreviations and Acronyms
Appendix A Abbreviations and Acronyms
A
AAL ATM Adaptation Layer
AAL2 ATM Adaptation Layer type 2
AAL5 ATM Adaptation Layer type 5
ARFCN Absolute Radio Frequency-Channel Number
ARP Address Resolution Protocol
ATM Asynchronous Transfer Mode
BAM Back Administration Module

BCKM BTS Control & Clock Module
BITS Building Integrated Timing Supply system
BOOTP Bootstrap Protocol
BSC Base Station Controller
BSS Base Station Subsystem
BSSAP Base Station Subsystem Application Part
BSSMAP Base Station Subsystem Management-Application Part
BTRM BTS Transceiver Module
BTS Base Transceiver Station
C
CAIE CDMA A Interface Equipment
CBMS CDMA Basic processing Subrack
CBPU CDMA Buffer Process Unit
CBR Constant Bit Rate
CCRM CDMA Satellite synchronization Clock Receiver Module
CDMA Code Division Multiple Access
CEVC CDMA Enhanced Vocoder with echo Canceller board
CEVD CDMA Enhanced Vocoder with echo canceller Disable
CFMR CDMA radio frame process (FP MAC RLC) board
CGI Cell Global Identification
CHAC CDMA High-speed Access Controller
A-1
CIC Circuit Identification Code

CIMS CDMA Integrated Management System
CIPS CDMA Integrated Processing Subrack
CIWF CDMA InterWorking Function board
CLAP CDMA Link Access Protocol board
CLKC ClocK C
CLKM CLocK processing Module
CLPC CDMA Line Process Unit with 2 622M engine
CLPU CDMA Line Process Unit
CMPU CDMA Main Process Unit
CMUX CDMA system MUltipleXer unit
CNET CDMA NETwork transfer and switch
COIE CDMA single mode Optical Interface Equipment
CPCU CDMA PCF Control Unit
CPMS CDMA Packet Module Subrack
CPPU CDMA Packet Process Unit
CPU Center Processing Unit
CRC Cyclical Redundancy Check
CRMS CDMA Resources Management Subrack
CRMU CDMA Resource Management Unit
CRPS CDMA Resource & Packet Subrack
CSPU CDMA Signal Process Unit
CSTU CDMA Synchronous Transport Unit
CSWS CDMA Switch Subrack
CTCS CDMA TransCoder Subrack
CXIE CDMA general (X) Interface Equipment
D
DPC Destination Point Code
DSP Digital Signal Processor
DTAP Direct Transfer Application Part
E
EIA Electronics Industry Association
A-2
FPGA Field Programmable Gate Array
G
GCKB GPS/GLONASS& ClocK Subrack Backplane
GCKP GPS/GLONASS& ClocK Processing Board
GE Gigabit Ethernet
GLONASS Global Navigation Satellite System
GPS Global Position System
GRE Generic Routing Encapsulation
H
HHO Hard Handoff
I
IMA Inverse Multiplexing on ATM
IMSI International Mobile Subscriber Identity
IP Internet Protocol
IPC Inter-process Communication
IPOA IP Over ATM
IS-2000 Interim Standards 2000
IS-95 Interim Standards 95
ISUP ISDN User Part
ITU International Telecommunications Union
ITU-T ITU Telecommunication Standardization Sector
IWF InterWorking Function
L
LAC Location Area Code
LAI Location Area Identification
LAN Local Area Network
M
MAP Mobile Application Part
MCC Mobile Country Code
MML Man Machine Language
MNC Mobile Network Code
A-3
MS Mobile Station
MSC Mobile Switching Center
MTP Message Transfer Part
N
NMS Network Management System
O
OAM Operation, Administration and Maintenance
OMC Operation & Maintenance Center
OML Operation & Maintenance Link
OMU Operation & Maintenance Unit
P
PCF Packet Control Function
PCM Pulse Code Modulation
PDSN Packet Data Service Node
PN Pseudo Number
PPP Peer-Peer Protocol
PSU Power Supply Unit
PVC Permanent Virtual Connection
PVP Permanent Virtual Path
Q
QoS Quality of Service
R
RFN Reduced TDMA Frame Number
S
SAR Segmentation And Reassembly
SCCP Signaling Connection Control Part
SDB Short Data Burst
SDH Synchronous Digital Hierarchy
SDU Selection/Distribution Unit
SHO Soft Handoff
SLC Signaling Link Code
SLS Signaling Link Selection
SQL Structured Query Language
A-4
SSN Sub-System Number

SSSAR Special Service Segmentation and Reassemble
T
TCAP Transaction Capability Application Part
TCP Transport Control Protocol
TIA Telecommunications Industry Association
TM Terminal Multiplexer
U
UNI User-to-Network Interface
UTCP UTC (Coordinated Universal Time) Provider Board
V
VCC Virtual Channel Connection
VCI Virtual Channel Identifier
VBR Variable Bit Rate
VPI Virtual Path Identifier
W
WS Work Station
A-5

Operation Manual-Data Configuration

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Operation Manual-Data Configuration

Загружено:

Авторское право:

Доступные форматы

Data Configuration of Small-capacity BSC

Table of Contents ......................................................................................... i

1.Data Configuration of Small-capacity BSC

2.Data Configuration of Large-capacity BSC

3.Abbreviations and Acronyms

Airbridge cBSC6600 CDMA Base Station Controller

Volume Data Configuration

Manual Version T2-031640-20040415-C-1.31

Product Version V100R003

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

The related manuals are listed in the following table.

Describes regulatory compliance statement and regulatory

Introduces the development of the CDMA network, and the

Airbridge cBSC6600 CDMA Base Station

Introduces the supporting bands, networking capacity, radio

Airbridge cBSC6600 CDMA Base Station

Airbridge cBSC6600 CDMA Base Station

Airbridge cBSC6600 CDMA Base Station

Airbridge cBSC6600 CDMA Base Station

Airbridge cBSC6600 CDMA Base Station

Airbridge cBSC6600 CDMA Base Station

The manual is intended for the following readers:

This manual uses the following conventions:

Arial Normal paragraphs are in Arial.

Boldface Headings are in Boldface.

Courier New Terminal Display is in Courier New.

II. Command conventions

Boldface The keywords of a command line are in Boldface.

italic Command arguments are in italic.

[] Items (keywords or arguments) in square brackets [ ] are optional.

Optional alternative items are grouped in square brackets and separated by

Optional alternative items are grouped in square brackets and separated by

III. GUI conventions

Multi-level menus are separated by forward slashes. For example,

IV. Keyboard operation

Caution: Means reader be extremely careful during the operation.

Note: Means a complementary description.

Module 1 Data Configuration of Small-capacity BSC

Chapter 1 Overview of Data Configuration................................................................................. 1-1

Chapter 2 Route Data Configuration ........................................................................................... 2-1

Chapter 3 Basic Information Configuration................................................................................ 3-1

Chapter 4 Equipment Data Configuration................................................................................... 4-1

Chapter 5 Clock System Configuration ...................................................................................... 5-1

5.1.3 Configuration Procedures ....................................................................................... 5-3

Chapter 6 A1/A2 Interface Configuration .................................................................................... 6-1

Chapter 7 A3/A7 Interface Configuration .................................................................................... 7-1

Chapter 8 Abis Interface Configuration ...................................................................................... 8-1

8.3.1 BTS O&M Channel.................................................................................................. 8-9

Chapter 9 Cell Channel Configuration ........................................................................................ 9-1

Chapter 10 Packet Data Service Configuration........................................................................ 10-1

Chapter 11 Circuit Data Service Configuration ........................................................................ 11-1

Module 2 Data Configuration of Large-capacity BSC

Chapter 1 Overview of Data Configuration................................................................................. 1-1

Chapter 2 CSWS Configuration ................................................................................................... 2-1

Chapter 3 Basic Information Configuration................................................................................ 3-1

Chapter 4 Equipment Data Configuration................................................................................... 4-1

Chapter 5 Clock System Configuration ...................................................................................... 5-1

5.6 Configuration of CMUX in Service Subrack....................................................................... 5-8