Professional Documents
Culture Documents
RSR10
68P02909W07-A
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no
liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in content
hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability
arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others. It is possible that this publication may contain references to, or
information about Motorola products (machines and programs), programming, or services that are not announced
in your country. Such references or information must not be construed to mean that Motorola intends to announce
such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include
or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right
to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,
any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the
Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a
product.
A list of 3rd Party supplied software copyrights are contained in the Supplemental information section of this
document.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials
Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT
designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments
requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication
Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Office.
Aug 2008
Table
of
Contents
Contents
2
2
2
2
3
3
3
4
5
5
5
5
6
7
7
7
7
8
8
8
9
9
9
10
11
11
11
11
1-2
Revision history . . . . . . . . . . . .
Version information . . . . . . . .
Resolution of Service Requests . .
Incorporation of Change Notices. .
General information . . . . . . . . . .
Purpose . . . . . . . . . . . . . .
Cross references . . . . . . . . . .
Text conventions . . . . . . . . . .
Contacting Motorola . . . . . . . . . .
24hour support . . . . . . . . . .
Questions and comments . . . . .
Errors . . . . . . . . . . . . . . .
Security advice. . . . . . . . . . . . .
Warnings, cautions, and notes . . . . .
Warnings. . . . . . . . . . . . . .
Cautions . . . . . . . . . . . . . .
Notes . . . . . . . . . . . . . . .
Safety . . . . . . . . . . . . . . . . .
General safety . . . . . . . . . . .
Electromagnetic energy . . . . . .
Caring for the environment . . . . . .
In EU countries . . . . . . . . . .
In non-EU countries . . . . . . . .
CMM labeling and disclosure table . .
Motorola document set . . . . . . . .
Ordering documents and CD-ROMs
Document banner definitions . . .
Data encryption . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
Transmission Mode on
. . . . . . . . . . . .
68P02909W07-A
Aug 2008
. . . .
. . . .
. . . .
. . . .
. . . .
the A
. . . .
.
.
.
.
.
2-2
2-3
2-3
2-3
2-3
. .
2-5
.
.
.
.
.
Contents
.
.
.
.
.
.
.
.
.
.
2-7
2-12
2-12
2-12
2-12
.
.
.
.
.
.
.
.
.
.
.
.
2-14
2-16
2-21
2-21
2-21
2-21
. .
. .
2-24
2-25
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-2
3-3
3-3
3-5
3-11
3-13
3-13
3-14
3-21
3-23
3-71
3-73
3-84
3-84
3-93
3-100
3-114
3-126
3-126
3-129
3-131
3-134
3-136
3-137
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-2
4-3
4-3
4-5
4-11
4-13
4-13
4-14
4-17
4-20
4-62
4-64
4-72
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
ii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02909W07-A
Aug 2008
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-72
4-78
4-92
4-104
4-104
4-107
4-109
4-111
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
5-3
5-3
5-5
5-12
5-14
5-14
5-15
5-18
5-21
5-69
5-71
5-79
5-79
5-86
5-100
5-112
5-112
5-114
5-115
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-2
6-3
6-3
6-17
6-32
6-32
6-35
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-2
7-3
7-3
7-3
7-4
7-6
7-6
7-7
7-7
7-7
7-8
7-8
7-8
7-9
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02909W07-A
Aug 2008
iii
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-9
7-9
7-11
7-13
7-13
7-13
7-13
7-15
7-15
7-15
7-16
7-18
7-18
7-18
7-19
7-19
7-20
7-20
7-21
7-21
7-21
7-23
7-23
7-23
7-24
7-26
7-26
7-26
7-27
7-28
7-28
7-28
7-29
7-29
7-31
7-34
7-34
7-34
7-35
7-37
7-39
7-39
7-41
7-43
7-46
7-51
7-52
7-53
8-2
8-2
Gb Interface Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Links on the A and Ater Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timeslots on the Ater Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of the BSC Clock (BM/TC Separated). . . . . . . . . . . . . . . . .
GMPS/GEPS Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GTCS Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration principles of BSC clock . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of the BSC Devices (BM/TC Combined) . . . . . . . . . . . . . . .
Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of the BSC Transmission (BM/TC Combined) . . . . . . . . . . . . .
Subrack Communication Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Semipermanent Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A Interface E1/T1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SS7 Signaling Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SS7 Signaling Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gb Interface Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of the BSC Clock (BM/TC Combined). . . . . . . . . . . . . . . . .
GMPS/GEPS Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration principles of BSC clock . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of the BSC Devices (IP Transmission Mode on the A Interface) . . .
Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of the BSC Transmission (IP Transmission Mode on the A Interface) .
Subrack Communication Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Semipermanent Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gb Interface Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of the BSC Clock (IP Transmission Mode on the A Interface). . . . .
GMPS/GEPS Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration principles of BSC clock . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of the Built-in PCU Devices. . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of the Gb Interface Links . . . . . . . . . . . . . . . . . . . . . . .
External Cells and Neighbor Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
External Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Neighbor Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration Principles of the FH Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRXs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timeslots on the Abis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BTS Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timeslot Assignment on the Abis Interface. . . . . . . . . . . . . . . . . . . . . . . . .
Timeslot Arrangement on the Abis Interface . . . . . . . . . . . . . . . . . . . . . . . .
BTS Multiplexing Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual Timeslot Assignment on the Abis Interface . . . . . . . . . . . . . . . . . . . .
Semipermanent Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Principles of Idle Timeslot Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
68P02909W07-A
Aug 2008
List
of
Figures
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02909W07-A
Aug 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-5
3-7
3-7
3-8
3-9
3-10
3-10
3-12
3-14
3-16
3-17
3-19
3-20
3-22
3-23
3-25
3-26
3-27
3-28
3-29
3-30
3-31
3-32
3-33
3-34
3-36
3-37
3-38
3-40
3-41
3-43
3-44
3-45
3-46
3-47
3-49
3-50
3-51
3-53
3-54
3-55
3-57
3-58
3-59
3-61
v
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
vi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-62
3-62
3-63
3-64
3-65
3-66
3-67
3-68
3-69
3-70
3-72
3-73
3-76
3-77
3-78
3-79
3-80
3-81
3-82
3-83
3-86
3-87
3-89
3-90
3-92
3-93
3-95
3-96
3-98
3-99
3-100
3-102
3-103
3-105
3-106
3-108
3-110
3-111
3-113
3-114
3-116
3-117
3-119
3-120
3-121
3-122
3-124
3-125
3-128
3-129
3-130
3-132
3-133
3-135
3-137
3-139
4-5
4-7
68P02909W07-A
Aug 2008
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
List of Figures
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02909W07-A
Aug 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-7
4-8
4-9
4-10
4-10
4-12
4-14
4-16
4-17
4-19
4-20
4-22
4-23
4-24
4-25
4-26
4-27
4-28
4-29
4-30
4-31
4-33
4-34
4-35
4-37
4-38
4-40
4-41
4-42
4-43
4-44
4-46
4-47
4-48
4-50
4-51
4-52
4-54
4-55
4-55
4-56
4-57
4-58
4-58
4-59
4-60
4-61
4-61
4-63
4-64
4-66
4-67
4-68
4-69
4-70
4-71
4-73
4-74
vii
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
viii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-76
4-77
4-78
4-80
4-81
4-83
4-84
4-86
4-88
4-89
4-91
4-92
4-94
4-95
4-97
4-98
4-99
4-100
4-102
4-103
4-106
4-107
4-109
4-111
4-113
5-5
5-7
5-8
5-9
5-9
5-11
5-11
5-13
5-15
5-17
5-18
5-20
5-21
5-23
5-24
5-25
5-26
5-28
5-29
5-30
5-31
5-32
5-34
5-36
5-37
5-38
5-40
5-41
5-43
5-44
5-44
5-45
5-46
68P02909W07-A
Aug 2008
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
List of Figures
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02909W07-A
Aug 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-47
5-47
5-48
5-49
5-50
5-50
5-53
5-54
5-55
5-57
5-58
5-59
5-61
5-62
5-62
5-63
5-64
5-65
5-65
5-66
5-67
5-68
5-68
5-70
5-71
5-73
5-74
5-75
5-76
5-77
5-78
5-80
5-81
5-83
5-84
5-85
5-86
5-88
5-89
5-91
5-92
5-94
5-96
5-97
5-99
5-100
5-102
5-103
5-105
5-106
5-107
5-108
5-110
5-111
5-113
5-115
5-117
6-5
ix
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
on the BSC side)
on the MSC side)
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-6
6-7
6-8
6-8
6-9
6-10
6-11
6-12
6-13
6-14
6-15
6-16
6-19
6-20
6-21
6-22
6-22
6-23
6-24
6-25
6-26
6-27
6-28
6-29
6-30
6-33
6-34
6-35
6-37
6-38
6-40
6-41
6-43
6-44
6-45
7-10
7-11
7-32
7-37
7-39
7-40
7-40
7-41
7-46
7-49
68P02909W07-A
Aug 2008
List
of
Tables
List of Tables
2-2
2-4
2-4
2-5
2-5
2-5
2-6
2-6
2-6
2-8
2-8
2-8
2-8
2-9
2-9
2-9
2-10
2-10
2-10
2-10
2-11
2-13
2-13
2-14
2-14
2-14
2-14
2-15
2-15
2-17
2-17
2-17
xi
List of Tables
Table 2-33: Example of the data negotiated and planned for configuring the BSC router . . . .
Table 2-34: Example of the data negotiated and planned for configuring the NSE on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-35: Example of the data negotiated and planned for configuring the BC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-36: Example of the data negotiated and planned for configuring the NSVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-37: Example of the data negotiated and planned for configuring the PTPBVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-38: Example of the data negotiated and planned for configuring the NSE on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-39: Example of the data negotiated and planned for configuring the local NSVL on the
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-40: Example of the data negotiated and planned for configuring the remote NSVL on the
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-41: Example of the data negotiated and planned for configuring the PTPBVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-42: Example of the data negotiated and planned for configuring BSC attributes . . . .
Table 2-43: Example of the data negotiated and planned for configuring the M3AU data . . . .
Table 2-44: Example of the data negotiated and planned for configuring the STP . . . . . . . .
Table 2-45: Example of the data negotiated and planned for configuring the subrack-OSP
mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-46: M3UA data negotiated for interconnection . . . . . . . . . . . . . . . . . . . . .
Table 2-47: CGI negotiated for interconnection . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-48: M3UA link data negotiated for interconnection . . . . . . . . . . . . . . . . . . .
Table 2-49: Example of the data negotiated and planned for configuring the GEPUG
attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-50: Example of the data negotiated and planned for configuring the device IP address . .
Table 2-51: Example of the data negotiated and planned for configuring the port IP address . .
Table 2-52: Example of the data negotiated and planned for configuring the BSC router . . . .
Table 2-53: Example of the data negotiated and planned for configuring the NSE on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-54: Example of the data negotiated and planned for configuring the BC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-55: Example of the data negotiated and planned for configuring the NSVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-56: Example of the data negotiated and planned for configuring the PTPBVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-57: Example of the data negotiated and planned for configuring the NSE on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-58: Example of the data negotiated and planned for configuring the local NSVL on the
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-59: Example of the data negotiated and planned for configuring the remote NSVL on the
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-60: Example of the data negotiated and planned for configuring the PTPBVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-1: Example of the data negotiated and planned for configuring BSC attributes (BM/TC
separated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-2: Example of the data negotiated and planned for configuring the SS7 OSP and DSP . .
Table 3-3: Example of the data negotiated and planned for configuring the STP . . . . . . . . .
Table 3-4: Example of the data negotiated and planned for configuring the subrack-OSP
mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-5: Example of the data negotiated and planned for configuring a GBSR cabinet . . . . .
Table 3-6: Example of the data negotiated and planned for configuring a GEPS . . . . . . . . .
Table 3-7: Example of the data negotiated and planned for adding a GTCS . . . . . . . . . . .
Table 3-8: Example of the data negotiated and planned for configuring a power distribution
box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-9: Example of the data negotiated and planned for configuring the GXPUM . . . . . . .
xii
2-17
2-18
2-18
2-18
2-19
2-19
2-19
2-19
2-20
2-22
2-22
2-23
2-23
2-24
2-24
2-25
2-26
2-26
2-26
2-26
2-27
2-27
2-27
2-28
2-28
2-28
2-28
2-29
3-4
3-6
3-6
3-11
3-13
3-15
3-18
3-21
3-25
68P02909W07-A
Aug 2008
List of Tables
Table 3-10: Example of the data negotiated and planned for configuring the GXPUT . . . . . .
Table 3-11: Example of the data negotiated and planned for configuring the GTNU . . . . . . .
Table 3-12: Example of the data negotiated and planned for configuring the GSCU . . . . . . .
Table 3-13: Example of the data negotiated and planned for configuring the GGCU . . . . . . .
Table 3-14: Example of the data negotiated and planned for configuring the GDPUX . . . . . .
Table 3-15: Example of the data negotiated and planned for configuring the GDPUP . . . . . .
Table 3-16: Example of the data negotiated and planned for configuring the GEIUA. . . . . . .
Table 3-17: Example of the data negotiated and planned for configuring the GOIUA . . . . . .
Table 3-18: Example of the data negotiated and planned for configuring a GEIUT . . . . . . . .
Table 3-19: Example of the data negotiated and planned for configuring the GOIUT . . . . . .
Table 3-20: Example of the data negotiated and planned for configuring a GEIUB. . . . . . . .
Table 3-21: Example of the data negotiated and planned for configuring the GOIUB . . . . . .
Table 3-22: Example of the data negotiated and planned for configuring the GEPUG . . . . . .
Table 3-23: Example of the data negotiated and planned for configuring the GFGUG . . . . . .
Table 3-24: Example of the data negotiated and planned for configuring the communication link
between GMPS 0 and GEPS 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-25: Example of the data negotiated and planned for configuring the communication link
between GMPS 0 and GEPS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-26: Example of the data negotiated and planned for configuring the communication link
between GEPS 1 and GEPS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-27: Example of the data negotiated and planned for configuring the communication link
between GTCS 6 and GTCS 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-28: Example of the data negotiated and planned for configuring the Ater connection path
between the GMPS and the GTCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-29: Example of the data negotiated and planned for configuring the Ater connection path
between the GEPS and the GTCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-30: Example of the data negotiated and planned for adding an OML . . . . . . . . . .
Table 3-31: Example of the data negotiated and planned for adding an Ater signaling link . . .
Table 3-32: Example of the data negotiated and planned for configuring an A Interface E1/T1 . .
Table 3-33: Example of the data negotiated and planned for adding an SS7 signaling link. . . .
Table 3-34: Example of the data negotiated and planned for configuring the NSE on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-35: Example of the data negotiated and planned for configuring the BC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-36: Example of the data negotiated and planned for configuring the SGSN clock . . . .
Table 3-37: Example of the data negotiated and planned for configuring the NSVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-38: Example of the data negotiated and planned for configuring the PTPBVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-39: Example of the data negotiated and planned for configuring the NSE on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-40: Example of the data negotiated and planned for configuring the local NSVL on the
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-41: Example of the data negotiated and planned for configuring the remote NSVL on the
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-42: Example of the data negotiated and planned for configuring the PTPBVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-43: Example of the data negotiated and planned for configuring the clock on line 0 for
the GTCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-44: Example of the data negotiated and planned for configuring the clock on line 1 for
the GTCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-45: Example of the data negotiated and planned for configuring the 8K reference clock
for the GTCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-46: Example of the data negotiated and planned for configuring the clock on line 0 for
the GMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-47: Example of the data negotiated and planned for configuring the clock on line 1 for
the GMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-48: Example of the data negotiated and planned for configuring the system clock . . .
68P02909W07-A
Aug 2008
3-29
3-31
3-32
3-34
3-35
3-39
3-42
3-42
3-48
3-48
3-52
3-52
3-56
3-60
3-74
3-74
3-75
3-75
3-85
3-85
3-88
3-91
3-94
3-97
3-101
3-104
3-107
3-109
3-112
3-115
3-118
3-121
3-123
3-127
3-127
3-130
3-131
3-132
3-134
xiii
List of Tables
Table 3-49: Example of data negotiated and planned for configuring the 8K reference clock for
the GMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-50: Example of the data negotiated and planned for configuring the 8K reference clock
for the GEPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-1: Example of the data negotiated and planned for configuring BSC attributes (BM/TC
combined) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-2: Example of the data negotiated and planned for configuring the SS7 OSP and DSP . .
Table 4-3: Example of the data negotiated and planned for configuring the STP . . . . . . . . .
Table 4-4: Example of the data negotiated and planned for configuring the subrack-OSP
mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-5: Example of the data negotiated and planned for configuring a GBSR cabinet . . . . .
Table 4-6: Example of the data negotiated and planned for configuring a GEPS . . . . . . . . .
Table 4-7: Example of the data negotiated and planned for configuring a power distribution
box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-8: Example of the data negotiated and planned for configuring the GXPUM . . . . . . .
Table 4-9: Example of the data negotiated and planned for configuring the GXPUT . . . . . . .
Table 4-10: Example of the data negotiated and planned for configuring the GSCU . . . . . . .
Table 4-11: Example of the data negotiated and planned for configuring the GTNU . . . . . . .
Table 4-12: Example of the data negotiated and planned for configuring the GGCU . . . . . . .
Table 4-13: Example of the data negotiated and planned for configuring the GDPUX . . . . . .
Table 4-14: Example of the data negotiated and planned for configuring the GDPUP . . . . . .
Table 4-15: Example of the data negotiated and planned for configuring the GEIUA. . . . . . .
Table 4-16: Example of the data negotiated and planned for configuring the GOIUA . . . . . .
Table 4-17: Example of the data negotiated and planned for configuring a GEIUB. . . . . . . .
Table 4-18: Example of the data negotiated and planned for configuring the GOIUB . . . . . .
Table 4-19: Example of the data negotiated and planned for configuring the GEPUG . . . . . .
Table 4-20: Example of the data negotiated and planned for configuring the GFGUG . . . . . .
Table 4-21: Example of the data negotiated and planned for configuring the communication link
between GMPS 0 and GEPS 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-22: Example of the data negotiated and planned for configuring the communication link
between GMPS 0 and GEPS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-23: Example of the data negotiated and planned for configuring the communication link
between GEPS 1 and GEPS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-24: Example of the data negotiated and planned for configuring an A Interface E1/T1 . .
Table 4-25: Example of the data negotiated and planned for adding an SS7 signaling link. . . .
Table 4-26: Example of the data negotiated and planned for configuring the NSE on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-27: Example of the data negotiated and planned for configuring the BC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-28: Example of the data negotiated and planned for configuring the SGSN clock . . . .
Table 4-29: Example of the data negotiated and planned for configuring the NSVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-30: Example of the data negotiated and planned for configuring the PTPBVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-31: Example of the data negotiated and planned for configuring the NSE on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-32: Example of the data negotiated and planned for configuring the local NSVL on the
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-33: Example of the data negotiated and planned for configuring the remote NSVL on the
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-34: Example of the data negotiated and planned for configuring the PTPBVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-35: Example of the data negotiated and planned for configuring the clock on line 0 for
the GMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-36: Example of the data negotiated and planned for configuring the clock on line 1 for
the GMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-37: Example of the data negotiated and planned for configuring the system clock . . .
xiv
3-136
3-138
4-4
4-6
4-6
4-11
4-13
4-15
4-18
4-21
4-26
4-28
4-30
4-31
4-32
4-36
4-39
4-39
4-45
4-45
4-49
4-53
4-65
4-65
4-66
4-72
4-75
4-79
4-82
4-85
4-87
4-90
4-93
4-96
4-99
4-101
4-105
4-105
4-108
68P02909W07-A
Aug 2008
List of Tables
Table 4-38: Example of data negotiated and planned for configuring the 8K reference clock for
the GMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-39: Example of the data negotiated and planned for configuring the 8K reference clock
for the GEPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-1: Example of the data negotiated and planned for configuring BSC attributes (BM/TC
combined) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-2: Example of the data negotiated and planned for configuring the M3AU entities . . .
Table 5-3: Example of the data negotiated and planned for configuring the signaling transfer
entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-4: Example of the data negotiated and planned for configuring the subrack-OSP
mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-5: Example of the data negotiated and planned for configuring a GBSR cabinet . . . . .
Table 5-6: Example of the data negotiated and planned for configuring a GEPS . . . . . . . . .
Table 5-7: Example of the data negotiated and planned for configuring a power distribution
box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-8: Example of the data negotiated and planned for configuring the GXPUM . . . . . . .
Table 5-9: Example of the data negotiated and planned for configuring the GXPUT . . . . . . .
Table 5-10: Example of the data negotiated and planned for configuring the GSCU . . . . . . .
Table 5-11: Example of the data negotiated and planned for configuring the GTNU . . . . . . .
Table 5-12: Example of the data negotiated and planned for configuring the GGCU . . . . . . .
Table 5-13: Example of the data negotiated and planned for configuring the GDPUX . . . . . .
Table 5-14: Example of the data negotiated and planned for configuring the GDPUP . . . . . .
Table 5-15: Example of the data negotiated and planned for configuring the GFGUA . . . . . .
Table 5-16: Example of the data negotiated and planned for configuring a GEIUB. . . . . . . .
Table 5-17: Example of the data negotiated and planned for configuring the GOIUB . . . . . .
Table 5-18: Example of the data negotiated and planned for configuring the GEPUG . . . . . .
Table 5-19: Example of the data negotiated and planned for configuring the GFGUG . . . . . .
Table 5-20: Example of the data negotiated and planned for configuring the communication link
between GMPS 0 and GEPS 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-21: Example of the data negotiated and planned for configuring the communication link
between GMPS 0 and GEPS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-22: Example of the data negotiated and planned for configuring the communication link
between GEPS 1 and GEPS 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-23: Example of the data negotiated and planned for configuring the M3UA link set . . .
Table 5-24: Example of the data negotiated and planned for configuring the M3UA link. . . . .
Table 5-25: Example of the data negotiated and planned for configuring the M3UA route . . . .
Table 5-26: Example of the data negotiated and planned for configuring the NSE on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-27: Example of the data negotiated and planned for configuring the BC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-28: Example of the data negotiated and planned for configuring the SGSN clock . . . .
Table 5-29: Example of the data negotiated and planned for configuring the NSVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-30: Example of the data negotiated and planned for configuring the PTPBVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-31: Example of the data negotiated and planned for configuring the NSE on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-32: Example of the data negotiated and planned for configuring the local NSVL on the
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-33: Example of the data negotiated and planned for configuring the remote NSVL on the
Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-34: Example of the data negotiated and planned for configuring the PTPBVC on the Gb
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-35: Example of the data negotiated and planned for configuring the system clock . . .
Table 5-36: Example of data negotiated and planned for configuring the 8K reference clock for
the GMPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5-37: Example of the data negotiated and planned for configuring the 8K reference clock
for the GEPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68P02909W07-A
Aug 2008
4-110
4-112
5-4
5-6
5-7
5-12
5-14
5-16
5-19
5-22
5-27
5-30
5-32
5-33
5-35
5-39
5-42
5-51
5-51
5-56
5-60
5-72
5-72
5-73
5-79
5-82
5-85
5-87
5-90
5-93
5-95
5-98
5-101
5-104
5-107
5-109
5-112
5-114
5-116
xv
List of Tables
Table 6-1: Example of the data negotiated and planned for adding a HorizonMacro BTS . .
Table 6-2: Example of the data negotiated and planned for adding a HorizonMacro BTS . .
Table 6-3: Example of the data negotiated and planned for configuring a site chain . . . . .
Table 6-4: Example of the data negotiated and planned for configuring a 2G external cell . .
Table 6-5: Example of the data negotiated and planned for configuring a 3G external cell . .
Table 6-6: Example of the data negotiated and planned for configuring adjacent cells . . . .
Table 7-1: Configuration principles of BSC boards . . . . . . . . . . . . . . . . . . . . . .
Table 7-2: Links on the A and Ater Interfaces . . . . . . . . . . . . . . . . . . . . . . . .
Table 7-3: Bandwidth of OM timeslots and signaling timeslots on the Ater interface. . . . .
Table 7-4: Configuration principles of BSC clock. . . . . . . . . . . . . . . . . . . . . . .
Table 7-5: Configuration principles of BSC boards . . . . . . . . . . . . . . . . . . . . . .
Table 7-6: Configuration principles of BSC clock. . . . . . . . . . . . . . . . . . . . . . .
Table 7-7: Configuration principles of BSC boards . . . . . . . . . . . . . . . . . . . . . .
Table 7-8: Configuration principles of BSC clock. . . . . . . . . . . . . . . . . . . . . . .
Table 7-9: Coding scheme and transmission rate . . . . . . . . . . . . . . . . . . . . . .
Table 7-10: Parameters of the Gb interface links . . . . . . . . . . . . . . . . . . . . . . .
Table 7-11: Mapping between the frequency bands and the frequency ranges . . . . . . . .
Table 7-12: Timeslot distribution on the Abis interface before timeslot arrangement by the
BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7-13: Timeslot distribution on the Abis interface after timeslot arrangement by the
BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7-14: Timeslot assignment in 1:1 multiplexing mode . . . . . . . . . . . . . . . . .
Table 7-15: Timeslot assignment in 2:1 multiplexing mode . . . . . . . . . . . . . . . . .
Table 7-16: Timeslot assignment in 4:1 multiplexing mode . . . . . . . . . . . . . . . . .
Table 7-17: Timeslot assignment on A0 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7-18: Timeslot assignment on A1 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7-19: Timeslot assignment on A2 . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-4
6-18
6-32
6-36
6-39
6-42
7-4
7-9
7-12
7-13
7-16
7-21
7-24
7-28
7-29
7-31
7-38
. .
7-44
.
.
.
.
.
.
.
7-45
7-47
7-48
7-48
7-50
7-51
7-51
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02909W07-A
Aug 2008
About
This
Manual
Related information
For changes in the document, refer to Appendix: Changes in BSC Initial Configuration Guide on
page 8-2.
68P02909W07-A
Aug 2008
Revision history
Revision history
Version information
The following table lists the supported versions of this manual in order of issue:
Issue
Date of issue
Remarks
Aug 2008
Initial Release
CMBP
Number
N/A
N/A
Remarks
CN Number
N/A
N/A
Title
68P02909W07-A
Aug 2008
General information
General information
Purpose
Motorola documents are intended to instruct and assist personnel in the operation, installation,
and maintenance of the Motorola equipment and ancillary devices. It is recommended that all
personnel engaged in such activities be properly trained by Motorola.
Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
NOTE
If this document was obtained when attending a Motorola training course, it is not
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then Motorola automatically supplies corrections and posts on the Motorola
customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.
68P02909W07-A
Aug 2008
Text conventions
Text conventions
The following conventions are used in the Motorola documents to represent keyboard input
text, screen output text, and special key sequences.
Input
Characters typed in at the keyboard are shown like this sentence.
Items of interest within a command appear like this sentence.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this sentence.
Items of interest within a screen display appear like this sentence.
CTRL-SHIFT-c or
CTRL+SHIFT+C
ALT-f or ALT+F
ALT+SHIFT+F11
Press the Alt, Shift and F11 keys at the same time.
RETURN or ENTER
68P02909W07-A
Aug 2008
Contacting Motorola
Contacting Motorola
24hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Office.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
68P02909W07-A
Aug 2008
Security advice
Security advice
Motorola systems and equipment provide security parameters that the operator configures
based on their particular operating environment. Motorola recommends setting and using
these parameters following industry recognized security practices. Consider protecting the
confidentiality, integrity, and availability of information and assets. Assets include the ability
to communicate, information about the nature of the communications, and information about
the parties involved.
In certain instances, Motorola makes specific recommendations regarding security practices.
The implementation of these recommendations and final responsibility for the security of the
system lies with the operator of the system.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information, from the menu located to the left of the
Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local
Motorola Office.
68P02909W07-A
Aug 2008
The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
WARNING
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
CAUTION
Caution text and consequence for not following the instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or provides additional
information to help the reader understand a topic or concept. A note has the following format:
NOTE
Note text.
68P02909W07-A
Aug 2008
Safety
Safety
General safety
The following general safety guidelines apply to Motorola equipment:
The power jack and mating plug of the power cable must meet International
Electrotechnical Commission (IEC) safety standards.
NOTE
Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.
Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on
the minimum health and safety requirements regarding the exposure of workers to the
risks arising from physical agents (electromagnetic fields) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
68P02909W07-A
Aug 2008
The following information describes national or regional requirements for the disposal of
Motorola supplied equipment and for the approved disposal of surplus packaging.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Office.
In EU countries
The following information is provided to enable regulatory compliance with the European
Union (EU) directives and any amendments to these directives when using Motorola equipment
in EU countries.
In non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance
with national and regional regulations.
68P02909W07-A
Aug 2008
The Peoples Republic of China requires that our products comply with China Management
Methods (CMM) environmental regulations. (China Management Methods refers to the
regulation Management Methods for Controlling Pollution by Electronic Information Products.)
Two items are used to demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.
Logo 1 means the product contains no substances in excess of the maximum concentration
value for materials identified in the China Management Methods regulation.
Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identified in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years. The example shown
uses 50 years.
Logo 1
Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic
and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)
will not leak or mutate causing environmental pollution or bodily injury from the use of the
EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain
field-replaceable parts, such as battery modules, can have a different EFUP and are marked
separately.
The Disclosure table is intended only to communicate compliance with China requirements.
It is not intended to communicate compliance with EU RoHS or any other environmental
requirements.
10
68P02909W07-A
Aug 2008
The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
68P02909W07-A
Aug 2008
11
Data encryption
12
68P02909W07-A
Aug 2008
Chapter
1
Definition of BSC Initial Configuration
68P02909W07-A
Aug 2008
1-1
BSC initial configuration refers to the configuration performed after BSC installation. BSC
initial configuration is based on the hardware configuration, network planning, and data
negotiated with other devices.
A BSC initial configuration file in .dat format is generated after initial configuration. The data in
this file must be complete, correct, and valid. Thus, the data can take effect after being loaded
to the LMT and GOMU for online BSC commissioning.
BSC initial configuration is performed on the LMT in offline mode. The configuration data is
used for BSC commissioning and loading. The correct initial configuration data is a prerequisite
for the proper operation of the BSC.
For the data configuration after the BSC is operational, refer to BSC Reconfiguration Guide.
1-2
68P02909W07-A
Aug 2008
Chapter
2
Scenarios of BSC Initial Configuration
68P02909W07-A
Aug 2008
2-1
Table 2-1
Configuration Mode
Description
BM/TC Separate
The BSC is configured with the GMPS, GEPS, and GTCS. In this
case, the A interface uses the TDM transmission mode.
BM/TC Together
The BSC is configured with the GMPS and GEPS. The boards of the
GTCS are configured in the GMPS and GEPS. In this case, the A
interface uses the TDM transmission mode.
IP on A Interface
The BSC is configured with the GMPS and GEPS. The GTCS is not
configured. The A interface uses the IP transmission mode. In this
case, the BSC must be connected to Motorola core network and the
TC must be integrated with Motorola MGW.
NOTE
The GMPS and GEPS are called BM in general. The GTCS is called TC for short. The
BM and TC have three combination modes. Only one of them can be selected.
There are three scenarios of BSC initial configuration in terms of subrack combination. Select
one according to actual requirements.
The BSC initial configuration is based on the initial configuration scenario. The procedure for
BSC initial configuration varies with scenarios.
2-2
68P02909W07-A
Aug 2008
When the BM and TC are configured in different subracks, follow the fixed procedures and
methods to perform the BSC initial configuration.
Prerequisites
The BSC global data is prepared. For details, refer to BSC Global Data (BM/TC Separated)
on page 2-3.
The A Interface data is negotiated for interconnection. For details, refer to A Interface Data
Negotiated for Interconnection (Non-IP Transmission Mode on the A Interface) on page 2-5.
The Gb interface data is negotiated for interconnection. For details, refer to Gb Interface
Data Negotiated for Interconnection on page 2-7.
Procedure
Procedure 2-1
68P02909W07-A
2-3
Aug 2008
BSC Attributes
Table 2-2
Example of the data negotiated and planned for configuring BSC attributes
Parameter
Parameter to Be
Configured
Example
Source
Basic Data
BSC Name
BSC001
Network planning
Country Code
86
Network planning
City Code
021
Network planning
MCC
460
Network planning
MNC
10
Network planning
A Interface Tag
GSM_PHASE_2+
Network planning
Um Interface Tag
GSM_PHASE_2+
Network planning
GSM_PHASE_2+
Network planning
NTP Server
10.161.72.251
BSC Subrack
Combination Type
BM/TC Separate
Network planning
Example of the data negotiated and planned for configuring the SS7 OSP
Parameter
Parameter to Be
Configured
Example
Source
OSP
OSP Name
BSC001
OPC (Hex)
B1
Network planning
Encoding Scheme
14
Network planning
Network Indicator
NATB
Network planning
DSP Name
MSC001
DSP (Hex)
D1
Network planning
DSP
If there is no direct physical link between the OSP and the DSP, configure the STPs. In this
case, set Using STP to Yes. For examples of the data negotiated and planned for configuring
the STP, refer to Table 2-4.
2-4
68P02909W07-A
Aug 2008
Table 2-4
A Interface
Example of the data negotiated and planned for configuring the STP
Parameter
Parameter to Be
Configured
Example
Source
STP
STP Name
STPMSC001
STP (Hex)
C1
Network planning
ITU-T
Network planning
Subrack-OSP Mapping
Table 2-5 Example of the data negotiated and planned for configuring the
subrack-OSP mapping
Parameter
Example
Source
Subrack No.
OSP
B1
Network planning
Parameter
Parameter to Be Configured
Example
Source
OSP
OSP Name
BSC001
OPC (Hex)
B1
Network planning
Network Indicator
NATB
Network planning
DSP Name
MSC001
DSP (Hex)
D1
Network planning
DSP
68P02909W07-A
2-5
Aug 2008
A Interface Data Negotiated for Interconnection (Non-IP Transmission Mode on the A Interface)
Scenarios of BSC Initial Configuration
Table 2-7
Chapter 2:
Parameter
Parameter to Be Configured
Example
Source
Basic Attribute
Parameters
MCC
460
Network planning
MNC
01
Network planning
LAC
8240
Network planning
CI
Network planning
Table 2-8
Parameter
Parameter to Be
Configured
Example
Source
SS7 Link
SLC
SLC Send
TS
TS16
CIC range
0-65535
Rate Type
64 kbit/s
A Interface Tag
GSM_PHASE_2+
Network planning
Basic Data
Table 2-9
Parameter
Parameter to Be
Configured
SubBoard
Attribute
Attributes of
the Ports on
the OIUa Board
Example
Source
Tributary
Numbering
HuaWei mode
TX J0 Byte
Expect RX J0 Byte
TX J1 Byte
Expect RX J1 Byte
TX J2 Byte
Expect RX J2 Byte
TX Frame Format
DOUBLE_FRAME
RX Frame Format
DOUBLE_FRAME
2-6
68P02909W07-A
Aug 2008
CGI parameters
CGI identifies a cell in the GSM system. CGI consists of the MCC, MNC, LAC, and CI. The
settings of the parameters on the BSC side and on the MSC side must be consistent.
A Interface tag
A Interface tag can be set to GSM_PHASE_1, GSM_PHASE_2, or GSM_PHASE_2+. The
setting of this parameter on the BSC side and that on the MSC side must be consistent.
68P02909W07-A
2-7
Aug 2008
Board Attributes
Table 2-10
attributes
Example of the data negotiated and planned for configuring the GEPUG
Parameter
Example
Source
WorkMode
E1
Frame Format
CRC4_MULTIFRAME
Table 2-11
IP address
Example of the data negotiated and planned for configuring the device
Parameter
Example
Source
Subrack No.
Slot No.
18
Port No.
IP Address
192.168.70.1
Subnet Mask
255.255.255.128
Table 2-12
IP address
Example of the data negotiated and planned for configuring the port
Parameter
Example
Source
Subrack No.
Slot No.
18
IP Address
192.168.70.132
Subnet Mask
255.255.255.128
Table 2-13
router
Example of the data negotiated and planned for configuring the BSC
Parameter
Example
Source
Subrack No.
Slot No.
18
Destination IP Address
192.168.70.0
Subnet Mask
255.255.255.128
Gateway
192.168.70.136
2-8
68P02909W07-A
Aug 2008
Gb over FR
Table 2-14 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over FR
Network planning
Network planning
Table 2-15 Example of the data negotiated and planned for configuring the BC on
the Gb interface
Parameter
Example
Source
Subrack No.
Slot No.
18
Port No.
Bearer Channel ID
Q933
Occupied Timeslot
T1-T16
10
Table 2-16 Example of the data negotiated and planned for configuring the NSVC
on the Gb interface
Parameter
Example
Source
NSVC Identifier
NSE Identifier
Subrack No.
Slot No.
18
Port No.
Bearer Channel ID
16
68P02909W07-A
2-9
Aug 2008
Table 2-17 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
BVC Identifier
Cell Name
Cell 1
Gb over IP
Table 2-18 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over IP
Network planning
Network planning
Table 2-19 Example of the data negotiated and planned for configuring the local
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.70.1
18
100
100
Table 2-20 Example of the data negotiated and planned for configuring the remote
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.80.1
IP Port No.
100
100
2-10
68P02909W07-A
Aug 2008
Table 2-21 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
BVC Identifier
Cell Name
Cell 1
68P02909W07-A
2-11
Aug 2008
When the BM and TC are configured in the same subrack, follow the fixed procedures and
methods to perform the BSC initial configuration.
Prerequisites
The BSC global data is prepared. For details, refer to BSC Global Data (BM/TC Combined,
Built-in PCU) on page 2-12.
The A Interface data is negotiated for interconnection. For details, refer to A Interface Data
Negotiated for Interconnection (Non-IP Transmission Mode on the A Interface) on page 2-5.
The Gb interface data is negotiated for interconnection. For details, refer to Gb Interface
Data Negotiated for Interconnection on page 2-7.
Procedure
Procedure 2-2
2-12
68P02909W07-A
Aug 2008
BSC Attributes
Table 2-22
Example of the data negotiated and planned for configuring BSC attributes
Parameter
Parameter to Be
Configured
Example
Source
Base Data
BSC Name
BSC001
Network planning
Country Code
86
Network planning
City Code
021
Network planning
MCC
460
Network planning
MNC
10
Network planning
A Interface Tag
GSM_PHASE_2+
Network planning
Um Interface Tag
GSM_PHASE_2+
Network planning
GSM_PHASE_2+
Network planning
NTP Server
10.161.72.251
BSC Subrack
Combination Type
BM/TC Together
Network planning
PCU Type
Inner
Network planning
Software
Parameters
Parameter to Be Configured
Example
Source
OSP
OSP Name
BSC001
OPC (Hex)
B1
Network planning
Encoding Scheme
14
Network planning
Network Indicator
NATB
Network planning
DSP Name
MSC001
DSP (Hex)
D1
Network planning
DSP
If there is no direct physical link between the OSP and the DSP, configure the STPs. In this
case, set Using STP to Yes. For examples of the data negotiated and planned for configuring
the STP, refer to Table 2-24.
68P02909W07-A
2-13
Aug 2008
A Interface Data Negotiated for Interconnection (Non-IP Transmission Mode on the A Interface)
Scenarios of BSC Initial Configuration
Table 2-24
Chapter 2:
Example of the data negotiated and planned for configuring the STP
Parameter
Parameter to Be Configured
Example
Source
STP
STP Name
STPMSC001
STP (Hex)
C1
Network planning
ITU-T
Network planning
Subrack-OSP Mapping
Table 2-25 Example of the data negotiated and planned for configuring the
subrack-OSP mapping
Parameter
Example
Source
Subrack No.
OSP
B1
Network planning
Parameter
Parameter to Be
Configured
Example
Source
OSP
OSP Name
BSC001
OPC (Hex)
B1
Network planning
Network Indicator
NATB
Network planning
DSP Name
MSC001
DSP (Hex)
D1
Network planning
DSP
Table 2-27
Parameter
Basic Attribute
Parameters
Parameter to Be
Configured
Example
Source
MCC
460
Network planning
MNC
01
Network planning
LAC
8240
Network planning
CI
Network planning
2-14
68P02909W07-A
Aug 2008
Table 2-28
A Interface
Parameter
Parameter to Be
Configured
Example
Source
SS7 Link
SLC
SLC Send
TS
TS16
CIC range
0-65535
Rate Type
64 kbit/s
A Interface Tag
GSM_PHASE_2+
Network planning
Basic Data
Table 2-29
Parameter
SubBoard Attribute
Attributes of the
Ports on the OIUa
Board
Example
Source
Tributary
Numbering
HuaWei mode
TX J0 Byte
MGW SDH
DEFAULT
(character string)
Expect RX J0 Byte
MGW SDH
DEFAULT
(character string)
TX J1 Byte
MGW SDH
DEFAULT
(character string)
Expect RX J1 Byte
MGW SDH
DEFAULT
(character string)
TX J2 Byte
MGW SDH
DEFAULT
(character string)
Expect RX J2 Byte
MGW SDH
DEFAULT
(character string)
TX Frame Format
DOUBLE_FRAME
RX Frame Format
DOUBLE_FRAME
68P02909W07-A
2-15
Aug 2008
CGI parameters
CGI identifies a cell in the GSM system. CGI consists of the MCC, MNC, LAC, and CI. The
settings of the parameters on the BSC side and on the MSC side must be consistent.
A Interface tag
A Interface tag can be set to GSM_PHASE_1, GSM_PHASE_2, or GSM_PHASE_2+. The
setting of this parameter on the BSC side and that on the MSC side must be consistent.
2-16
68P02909W07-A
Aug 2008
Board Attributes
Table 2-30
attributes
Example of the data negotiated and planned for configuring the GEPUG
Parameter
Example
Source
WorkMode
E1
Frame Format
CRC4_MULTIFRAME
Table 2-31
IP address
Example of the data negotiated and planned for configuring the device
Parameter
Example
Source
Subrack No.
Slot No.
18
Port No.
IP Address
192.168.70.1
Subnet Mask
255.255.255.128
Table 2-32
IP address
Example of the data negotiated and planned for configuring the port
Parameter
Example
Source
Subrack No.
Slot No.
18
IP Address
192.168.70.132
Subnet Mask
255.255.255.128
Table 2-33
router
Example of the data negotiated and planned for configuring the BSC
Parameter
Example
Source
Subrack No.
Slot No.
18
Destination IP Address
192.168.70.0
Subnet Mask
255.255.255.128
Gateway
192.168.70.136
68P02909W07-A
2-17
Aug 2008
Gb over FR
Table 2-34 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over FR
Network planning
Network planning
Table 2-35 Example of the data negotiated and planned for configuring the BC on
the Gb interface
Parameter
Example
Source
Subrack No.
Slot No.
18
Port No.
Bearer Channel ID
Q933
Occupied Timeslot
T1-T16
10
Table 2-36 Example of the data negotiated and planned for configuring the NSVC
on the Gb interface
Parameter
Example
Source
NSVC Identifier
NSE Identifier
Subrack No.
Slot No.
18
Port No.
Bearer Channel ID
16
2-18
68P02909W07-A
Aug 2008
Table 2-37 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
BVC Identifier
Cell Name
Cell 1
Gb over IP
Table 2-38 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over IP
Network planning
Network planning
Table 2-39 Example of the data negotiated and planned for configuring the local
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.70.1
18
100
100
Table 2-40 Example of the data negotiated and planned for configuring the remote
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.80.1
IP Port No.
100
100
68P02909W07-A
2-19
Aug 2008
Table 2-41 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
BVC Identifier
Cell Name
Cell 1
2-20
68P02909W07-A
Aug 2008
When the BSC is configured with IP transmission mode on the A Interface, follow the fixed
procedures and methods to perform the BSC initial configuration.
Prerequisites
The BSC global data is prepared. For details, refer to BSC Global Data (IP on A Interface,
Built-in PCU) on page 2-21.
The A Interface data is negotiated for interconnection. For details, refer to A Interface Data
Negotiated for Interconnection (IP Transmission Mode on the A Interface) on page 2-24.
The Gb interface data is negotiated for interconnection. For details, refer to Gb Interface
Data Negotiated for Interconnection on page 2-7.
Procedure
Procedure 2-3
2-21
Aug 2008
BSC global data includes BSC attributes, M3UA data, and subrack-OSP mapping. The examples
of configurations of the BSC global data are as follows:
BSC Attributes
Table 2-42
Example of the data negotiated and planned for configuring BSC attributes
Parameter
Parameter to Be
Configured
Example
Source
Basic Data
BSC Name
BSC001
Network planning
Country Code
86
Network planning
City Code
021
Network planning
MCC
460
Network planning
MNC
10
Network planning
A Interface Tag
GSM_PHASE_2+
Network planning
Um Interface Tag
GSM_PHASE_2+
Network planning
GSM_PHASE_2+
Network planning
NTP Server
10.161.72.251
BSC Subrack
Combination Type
IP on A Interface
Network planning
PCUType
Inner
Network planning
Software
Parameters
M3AU Data
Table 2-43
data
Example of the data negotiated and planned for configuring the M3AU
Parameter
Parameter to Be
Configured
Example
Source
Local Entity
BSC001
OPC (Hex)
B1
Network planning
Encoding Scheme
14
Network planning
Network Indicator
NATB
Network planning
Entity Name
MSC001
DSP (Hex)
D1
Network planning
LinkSet Name
Network planning
Adjacent Destination
Entity Name
MSC001
Network planning
Destination Entity
M3UA Config
Linkset
Continued
2-22
68P02909W07-A
Aug 2008
Table 2-43 Example of the data negotiated and planned for configuring the M3AU
data (Continued)
Parameter
Parameter to Be
Configured
Example
Source
MSC001
Network planning
Linkset Name
Network planning
If there is no direct physical link between the local entity and the destination entity, configure
a signaling transfer entity. When configuring the destination entity, set Using STP to Yes.
When configuring the M3UA link set, set Adjacent Destination Entity Name to the signaling
transfer entity name. For examples of the data negotiated and planned for configuring the
signaling transfer entity, refer to Table 2-44.
Table 2-44
Example of the data negotiated and planned for configuring the STP
Parameter
Parameter to Be
Configured
Example
Source
STP Entity
STE Name
MGW001
STP (Hex)
C1
Network planning
Protocol
RFC3332
Network planning
Subrack-OSP Mapping
Table 2-45 Example of the data negotiated and planned for configuring the
subrack-OSP mapping
Parameter
Example
Source
Subrack No.
OSP
B1
Network planning
68P02909W07-A
2-23
Aug 2008
A Interface Data Negotiated for Interconnection (IP Transmission Mode on the A Interface)
Scenarios of BSC Initial Configuration
Chapter 2:
Parameter
Parameter to Be
Configured
Example
Source
Local Entity
BSC001
BSC internal
planning
OPC (Hex)
B1
Network planning
Network Indicator
NATB
Network planning
Destination Entity
Name
MSC001
BSC internal
planning
DSP (Hex)
D1
Network planning
Linkset Name
Network planning
Adjacent Destination
Entity Name
MSC001
Network planning
Destination Entity
Name
MSC001
Network planning
Linkset Name
Network planning
Destination Entity
M3UA Route
Table 2-47
Parameter
Basic Attribute
Parameters
Parameter to Be
Configured
Example
Source
MCC
460
Network planning
MNC
01
Network planning
LAC
8240
Network planning
CI
Network planning
2-24
68P02909W07-A
Aug 2008
Table 2-48
Parameter
Parameter to Be Configured
Example
Source
M3UA
Linkset Name
Local Address 1
192.168.10.2
Peer Address 1
192.168.30.1
Yes
Network planning
CRC32
SCTP
M3UA data
M3UA data involves the M3UA entities, M3UA link set, and M3UA route. The M3UA data
on the BSC side and that on the MSC side must be consistent.
CGI parameters
CGI identifies a cell in the GSM system. CGI consists of the MCC, MNC, LAC, and CI. The
settings of the parameters on the BSC side and on the MSC side must be consistent.
A Interface tag
A Interface tag can be set to GSM_PHASE_1, GSM_PHASE_2, or GSM_PHASE_2+. The
setting of this parameter on the BSC side and that on the MSC side must be consistent.
2-25
Aug 2008
Board Attributes
Table 2-49
attributes
Example of the data negotiated and planned for configuring the GEPUG
Parameter
Example
Source
WorkMode
E1
Frame Format
CRC4_MULTIFRAME
Table 2-50
IP address
Example of the data negotiated and planned for configuring the device
Parameter
Example
Source
Subrack No.
Slot No.
18
Port No.
IP Address
192.168.70.1
Subnet Mask
255.255.255.128
Table 2-51
IP address
Example of the data negotiated and planned for configuring the port
Parameter
Example
Source
Subrack No.
Slot No.
18
IP Address
192.168.70.132
Subnet Mask
255.255.255.128
Table 2-52
router
Example of the data negotiated and planned for configuring the BSC
Parameter
Example
Source
Subrack No.
Slot No.
18
Destination IP Address
192.168.70.0
Subnet Mask
255.255.255.128
Gateway
192.168.70.136
2-26
68P02909W07-A
Aug 2008
Gb over FR
Table 2-53 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over FR
Network planning
Network planning
Table 2-54 Example of the data negotiated and planned for configuring the BC on
the Gb interface
Parameter
Example
Source
Subrack No.
Slot No.
18
Port No.
Bearer Channel ID
Q933
Occupied Timeslot
T1-T16
10
Table 2-55 Example of the data negotiated and planned for configuring the NSVC
on the Gb interface
Parameter
Example
Source
NSVC Identifier
NSE Identifier
Subrack No.
Slot No.
18
Port No.
Bearer Channel ID
16
68P02909W07-A
2-27
Aug 2008
Table 2-56 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
BVC Identifier
Cell Name
Cell 1
Gb over IP
Table 2-57 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over IP
Network planning
Network planning
Table 2-58 Example of the data negotiated and planned for configuring the local
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.70.1
18
100
100
Table 2-59 Example of the data negotiated and planned for configuring the remote
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.80.1
IP Port No.
100
100
2-28
68P02909W07-A
Aug 2008
Table 2-60 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
BVC Identifier
Cell Name
Cell 1
68P02909W07-A
Aug 2008
2-29
2-30
68P02909W07-A
Aug 2008
Chapter
3
Configuring the BSC (BM/TC Separated)
68P02909W07-A
Aug 2008
3-1
This section describes how to configure the BSC global data, the devices, the links, and the clock
on the BSC Local Manager when the BM and the TC are configured in different subracks.
3-2
68P02909W07-A
Aug 2008
When the BM and the TC are configured in different subracks, the BSC global data includes
BSC attributes, SS7 signaling point data, and subrack-OSP mapping.
Basic Data
BSC Timer
Software Parameters
SCCP
IP Transfers
Scenario
Mandatory/Optional
Mandatory
Prerequisites
The BSC attributes have been determined in network planning.
68P02909W07-A
3-3
Aug 2008
Preparation
Table 3-1 Example of the data negotiated and planned for configuring BSC attributes
(BM/TC separated)
Parameter
Example
Source
BSC Name
BSC001
Network planning
Country Code
86
Network planning
City Code
021
Network planning
MCC
460
Network planning
MNC
10
Network planning
A Interface Tag
GSM_PHASE_2+
Network planning
Um Interface Tag
GSM_PHASE_2+
Network planning
GSM_PHASE_2+
Network planning
NTP Server
10.161.72.251
BM/TC Separate
Network planning
Procedure
Procedure 3-1
1
3-4
68P02909W07-A
Aug 2008
Procedure 3-1
2
Choose Configure BSC Attributes from the shortcut menu. A dialog box is displayed, as
shown in Figure 3-1.
Figure 3-1
On the Basic Data tab page, set the parameters by referring to Figure 3-1.
NOTE
The parameters not listed in Table 3-1 are optional. Use the default settings of the
parameters or modify them according to actual requirements.
4
Mandatory/Optional
Mandatory
68P02909W07-A
3-5
Aug 2008
CAUTION
The OSP and DSP must be configured before the STP is configured.
The BSC can be configured with up to four OSPs, 32 DSPs, and 32 STPs. For
details on the configuration of multiple OSPs, refer to Local Multiple Signaling
Points.
Prerequisites
None.
Preparation
Table 3-2
and DSP
Example of the data negotiated and planned for configuring the SS7 OSP
Parameter
Example
Source
OPC Name
BSC001
OPC (Hex)
B1
Network planning
Encoding Scheme
14
Network planning
Network Indicator
NATB
Network planning
DPC Name
MSC001
DPC (Hex)
D1
Network planning
Table 3-3
Example of the data negotiated and planned for configuring the STP
Parameter
Example
Source
STP Name
STPMSC001
STP (Hex)
C1
Network planning
ITU-T
Network planning
The following procedure describes how to configure the SS7 Signaling Points.
Procedure
b.
Choose Configure SS7 Signaling Point from the shortcut menu. A dialog box is
displayed, as shown in Figure 3-2.
3-6
68P02909W07-A
Aug 2008
Figure 3-2
c.
On the OPC tab page, click Add OPC. A dialog box is displayed, as shown in
Figure 3-3.
Figure 3-3
68P02909W07-A
3-7
Aug 2008
NOTE
If an OPC exists, OPC Name, Encoding Scheme, and Network Indicator
of the OSP are displayed by default in the dialog box shown in Figure 3-3.
d.
e.
In the dialog box shown in Figure 3-2, click the DPC tab to display the tab page,
as shown in Figure 3-4.
Figure 3-4
b.
3-8
68P02909W07-A
Aug 2008
Figure 3-5
NOTE
If there is no direct physical link between the OSP and the DSP, configure
the STPs. In the dialog box shown in Figure 3-5, set Using STP to Yes.
c.
d.
Check whether there is a direct physical link between the OSP and the DSP.
If...
Then...
In the dialog box shown in Figure 3-2, click the STP tab to display the tab page,
as shown in Figure 3-6.
68P02909W07-A
3-9
Aug 2008
Figure 3-6
b.
Figure 3-7
3-10
68P02909W07-A
Aug 2008
c.
d.
Mandatory/Optional
Mandatory
NOTE
The GMPS is displayed by default on the LMT. Configure only its OSP on the LMT.
For the GEPS, configure the GEPS and its OSP on the LMT. The GTCS does not
require an OSP.
Prerequisites
The OSP is already configured.
Preparation
Table 3-4 Example of the data negotiated and planned for configuring the
subrack-OSP mapping
Parameter
Example
Source
Subrack No.
OSP
B1
Network planning
Procedure
Procedure 3-2
1
68P02909W07-A
3-11
Aug 2008
Procedure 3-2
2
Choose Configure Subrack-OSP Mapping configuring the PTPBVC from the shortcut
menu. A dialog box is displayed, as shown in Figure 3-8.
Figure 3-8
3-12
68P02909W07-A
Aug 2008
This section describes how to configure the BSC devices on the LMT, when the BM and TC are
configured in different subracks.
Mandatory/Optional
NOTE
When the BM and TC are configured in different subracks, the GBSR cabinet can be
configured on the BSC side or on the MSC side. When the GBSR cabinet is placed on
the BSC side, it is a local GBSR cabinet. When the GBSR cabinet is placed on the
MSC side, it is a remote GBSR cabinet. The local GBSR cabinet holds the GEPS or
the GTCS. The remote GBSR holds the GTCS. Zero to four GBSR cabinets can be
configured on the basis of the actual traffic volume, transmission mode on the A
Interface, and GTCS configuration mode.
Prerequisites
None.
Preparation
Table 3-5
Example of the data negotiated and planned for configuring a GBSR cabinet
Parameter
Example
Source
Cabinet No.
Cabinet Type
Remote cabinet
68P02909W07-A
3-13
Aug 2008
Procedure
Procedure 3-3
Choose Add BSC Cabinet from the shortcut menu. A dialog box is displayed, as shown
in Figure 3-9.
Figure 3-9
3-14
68P02909W07-A
Aug 2008
Adding a GEPS
This section describes how to add a GEPS and configure its attributes on the LMT.
Scenario
Mandatory/Optional
NOTE
The GEPS processes the basic services of the BSC. The settings of the GEPS depend
on the traffic volume of the BSC. When the BM and TC are configured in different
subracks, the BSC can be configured with up to three GEPSs to form the 1 GMPS
+ 3 GEPSs combination. This combination can hold up to 2048 TRXs. A fan box is
automatically added when you add a subrack. Configure only the attributes of the
fan box.
Prerequisites
The OSP is already configured. For details, refer to Configuring the SS7 Signaling Points
on page 3-5.
Preparation
Table 3-6
Parameter
Example
Source
Subrack Type
GEPS
OPC
B1
Network planning
68P02909W07-A
3-15
Aug 2008
Procedure
Procedure 3-4
Adding a GEPS
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
Figure 3-10
3-16
68P02909W07-A
Aug 2008
Procedure 3-4
7
Choose Configure Fan Box Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-11.
Figure 3-11
For the parameters in the dialog box shown in Figure 3-11, use the default settings of the
parameters or modify them according to actual requirements.
10
Postrequisites
Before deleting the GEPSs that are initially configured, ensure that they are powered off.
68P02909W07-A
3-17
Aug 2008
Adding a GTCS
This section describes how to add a GTCS and configure its attributes on the LMT when the BM
and TC are configured in different subracks.
Scenario
Mandatory/Optional
Mandatory
NOTE
The number of GTCSs to be configured depends on the traffic volume of the BSC.
When the BM and TC are configured in different subracks, the BSC can be configured
with up to four GTCSs to support 15360 speech channels (maximum configuration). A
fan box is automatically added when you add a subrack. Configure only the attributes
of the fan box.
Prerequisites
The OSP is already configured. For details, refer to Configuring the SS7 Signaling Points
on page 3-5.
Preparation
Table 3-7
Parameter
Example
Source
Subrack Type
GTCS
Is Main Subrack
Selected
Procedure
Procedure 3-5
Adding a GTCS
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
3-18
68P02909W07-A
Aug 2008
Procedure 3-5
3
Figure 3-12
68P02909W07-A
3-19
Aug 2008
Procedure 3-5
7
Choose Configure Fan Box Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-13.
Figure 3-13
For the parameters in the dialog box shown in Figure 3-13, use the default settings of the
parameters or modify them according to actual requirements.
10
Postrequisites
To add a GTCS that was a functional GTCS configured on the MSC side (remote
GTCS), do as follows:
Reconfigure the original remote path and reset the remote GTCS.
3-20
68P02909W07-A
Aug 2008
Mandatory/Optional
Mandatory
NOTE
Any subrack in the cabinet can be configured as the management subrack for the
power distribution box.
Prerequisites
The subrack that manages the power distribution box is configured.
Preparation
Table 3-8 Example of the data negotiated and planned for configuring a power
distribution box
Parameter
Example
Source
Cabinet No.
Procedure
Procedure 3-6
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
68P02909W07-A
3-21
Aug 2008
Procedure 3-6
3
Choose Add Power Distribution Box. A dialog box is displayed, as shown in Figure 3-14.
Figure 3-14
3-22
68P02909W07-A
Aug 2008
Procedure 3-6
7
Choose Configure Power Distribution Box Attributes from the shortcut menu. A dialog
box is displayed, as shown in Figure 3-15.
Figure 3-15
For the parameters in the dialog box shown in Figure 3-15, use the default settings of the
parameters or modify them according to actual requirements.
10
Repeat step 1 through step 9 to configure power distribution boxes for more subracks.
68P02909W07-A
3-23
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
None.
NOTE
When the GXPUM is configured in the GMPS, parameters such as Load Key and Port
Attributes can be configured. When the GXPUM is configured in the GEPS, only
Load Key can be configured.
3-24
68P02909W07-A
Aug 2008
Preparation
Table 3-9
Example of the data negotiated and planned for configuring the GXPUM
Parameter
Example
Source
Load Key
Server
Selected
Procedure
Procedure 3-7
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet where the
GMPS is located from the Current Cabinet drop-down list.
Figure 3-16
68P02909W07-A
3-25
Aug 2008
Procedure 3-7
Right-click GXPUM.
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-17.
Figure 3-17
3-26
68P02909W07-A
Aug 2008
Procedure 3-7
9
Figure 3-18
10
68P02909W07-A
3-27
Aug 2008
Procedure 3-7
11
Figure 3-19
12
13
Mandatory/Optional
Prerequisites
None.
3-28
68P02909W07-A
Aug 2008
Preparation
Table 3-10
Example of the data negotiated and planned for configuring the GXPUT
Parameter
Example
Source
Board Type
GXPUT
Active/Standby Mode
Selected
Load Key
Server
Procedure
Procedure 3-8
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet where the
GMPS is located from the Current Cabinet drop-down list.
Figure 3-20
68P02909W07-A
3-29
Aug 2008
Procedure 3-8
Right-click a GXPUT.
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-21.
Figure 3-21
Mandatory/Optional
Mandatory
Prerequisites
None.
3-30
68P02909W07-A
Aug 2008
Preparation
Table 3-11
Example of the data negotiated and planned for configuring the GTNU
Parameter
Example
Source
Load Key
Server
Procedure
Procedure 3-9
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-22.
Figure 3-22
68P02909W07-A
3-31
Aug 2008
Scenario
Mandatory/Optional
Mandatory
Prerequisites
None.
Preparation
Table 3-12
Example of the data negotiated and planned for configuring the GSCU
Parameter
Example
Source
Load Key
Server
Procedure
Procedure 3-10
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-23.
Figure 3-23
3-32
68P02909W07-A
Aug 2008
Procedure 3-10
4
Figure 3-24
NOTE
Among the 12 ports on the GSCU, the alarm reporting function of all the
ports, except for ports 0, 1, 10, and 11, are disabled by default on the LMT.
Enable the alarm reporting function of the port connected to the Ethernet
cable to monitor whether the port is normal.
Mandatory/Optional
Mandatory
Prerequisites
None.
68P02909W07-A
3-33
Aug 2008
Preparation
Table 3-13
Example of the data negotiated and planned for configuring the GGCU
Parameter
Example
Source
Load Key
Server
Procedure
Procedure 3-11
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-25.
Figure 3-25
3-34
68P02909W07-A
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
The GMPS/GEPS/GTCS has empty slots to hold the GDPUX.
Preparation
Table 3-14
Example of the data negotiated and planned for configuring the GDPUX
Parameter
Example
Source
FuncType
Other board
Board Type
GDPUX
Load Key
Server
The following procedure describes how to configure the GDPUX in the GTCS.
Procedure
Procedure 3-12
68P02909W07-A
3-35
Aug 2008
Procedure 3-12
3
Figure 3-26
Set FuncType to Other board, and set Board Type to GDPUX. Then click Finish. A
GDPUX is added.
Right-click GDPUX.
Continued
3-36
68P02909W07-A
Aug 2008
Procedure 3-12
6
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-27.
Figure 3-27
68P02909W07-A
3-37
Aug 2008
Procedure 3-12
8
Figure 3-28
NOTE
When configuring the DSP TC attributes, select a DSP TC number first, and
then configure the attributes of this DSP TC.
If you select Configure All, all the DSP TCs will be configured based on the
settings of the current DSP TC displayed in the DSP TC No. drop-down
list box.
Modify the parameters in the dialog box shown in Figure 3-28 according to actual
requirements.
10
Mandatory/Optional
Mandatory
3-38
68P02909W07-A
Aug 2008
Prerequisites
The GMPS/GEPS has empty slots to hold the GDPUP.
Preparation
Table 3-15
Example of the data negotiated and planned for configuring the GDPUP
Parameter
Example
Source
Subrack No.
Slot No.
Board Type
GDPUP
Load Key
Server
Procedure
Procedure 3-13
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
68P02909W07-A
3-39
Aug 2008
Procedure 3-13
3
Figure 3-29
Set FuncType to Other board, and set Board Type to GDPUP. Then click Finish. A
GDPUP is added.
Right-click GDPUP.
Continued
3-40
68P02909W07-A
Aug 2008
Procedure 3-13
6
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-30.
Figure 3-30
Mandatory/Optional
Mandatory
Prerequisites
The GTCS has empty slots to hold the GEIUA/GOIUA.
68P02909W07-A
3-41
Aug 2008
Preparation
Table 3-16
Example of the data negotiated and planned for configuring the GEIUA
Parameter
Example
Source
Board Type
GEIUA
WorkMode
E1
Active/Standby Mode
Selected
Load Key
Server
Frame Format
DOUBLE_FRAME
Table 3-17
Example of the data negotiated and planned for configuring the GOIUA
Parameter
Example
Source
Board Type
GOIUA
WorkMode
E1
Active/Standby Mode
Selected
Load Key
Server
Tributary Numbering
HuaWei mode
TX J0 Byte
Expect RX J0 Byte
TX J1 Byte
Expect RX J1 Byte
TX J2 Byte
Expect RX J2 Byte
TX Frame Format
DOUBLE_FRAME
RX Frame Format
DOUBLE_FRAME
The procedures for configuring the GEIUA and GOIUA are the same. The following procedure
describes how to add a pair of GOIUAs (in active/standby mode) in the GTCS.
3-42
68P02909W07-A
Aug 2008
Procedure
Procedure 3-14
On the BSC Local Manager, click the BSC Device Panel tab. Select the cabinet where the
GTCS is located from the Current Cabinet drop-down list.
Figure 3-31
Set FuncType to A interface board, and set Board Type to GOIUA. Set the parameters
by referring to Table 3-16.
Right-click GOIUA.
Continued
68P02909W07-A
3-43
Aug 2008
Procedure 3-14
7
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-32.
Figure 3-32
Continued
3-44
68P02909W07-A
Aug 2008
Procedure 3-14
8
Set Load Key, and click Next. A dialog box is displayed, as shown in Figure 3-33.
Figure 3-33
Set the attributes of the sub-board of the GOIUA by referring to Table 3-16.
Continued
68P02909W07-A
3-45
Aug 2008
Procedure 3-14
10
Figure 3-34
NOTE
TX Frame Format and RX Frame Format should be negotiated with the peer.
For other parameters, use the default settings. By default, J2 Byte Alarm Report
Switch is set to Close. Modify it according to actual requirements. The BSC
recognizes only the J2 byte alarms of the SDH suggested format. If J2 Byte Alarm
Report Switch is set to Open, Motorola recommends that the peer expected RX
J2 byte be set to the SDH suggested format.
11
Set the attributes of the port on the GOIUA by referring to Table 3-16.
Continued
3-46
68P02909W07-A
Aug 2008
Procedure 3-14
12
Figure 3-35
NOTE
Protect mode, Switch mode, and recover mode should be negotiated with the
peer. For other parameters, use the default settings.
13
Mandatory/Optional
Mandatory
68P02909W07-A
3-47
Aug 2008
Prerequisites
The GMPS/GEPS/GTCS has empty slots to hold the GEIUT/GOIUT.
NOTE
If the GEIUT/GOIUT in independent mode is configured in the GTCS, the
corresponding active/standby slot cannot be configured with any board.
Preparation
Table 3-18
Parameter
Example
Source
Board Type
GEIUT
WorkMode
E1
Active/Standby Mode
Selected
Load Key
Server
Frame Format
DOUBLE_FRAME
Table 3-19
Example of the data negotiated and planned for configuring the GOIUT
Parameter
Example
Source
Board Type
GOIUT
WorkMode
E1
Active/Standby Mode
Selected
Load Key
Server
Tributary Numbering
HuaWei mode
TX J0 Byte
Expect RX J0 Byte
TX J1 Byte
Expect RX J1 Byte
TX J2 Byte
Expect RX J2 Byte
TX Frame Format
DOUBLE_FRAME
RX Frame Format
DOUBLE_FRAME
The procedures for configuring the GEIUT and GOIUT are the same. The following procedure
describes how to add a pair of GEIUTs (in active/standby mode) in the GTCS.
3-48
68P02909W07-A
Aug 2008
Procedure
Procedure 3-15
On the BSC Local Manager, click the BSC Device Panel tab. Select the cabinet where the
GTCS is located from the Current Cabinet drop-down list.
Figure 3-36
Set FuncType to Ater interface board, and set Board Type to GEIUT. Set the parameters
by referring to Table 3-18.
Right-click GEIUT.
Continued
68P02909W07-A
3-49
Aug 2008
Procedure 3-15
7
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-37.
Figure 3-37
Continued
3-50
68P02909W07-A
Aug 2008
Procedure 3-15
8
Set Load Key, and click Next. A dialog box is displayed, as shown in Figure 3-38.
Figure 3-38
Set the attributes of the port on the GEIUT by referring to Table 3-18.
10
Mandatory/Optional
Mandatory
Prerequisites
The subrack has empty slots to hold the GEIUB/GOIUB.
68P02909W07-A
3-51
Aug 2008
Preparation
Table 3-20
Parameter
Example
Source
Board Type
GEIUB
WorkMode
E1
Active/Standby Mode
Selected
Load Key
Server
Table 3-21
Example of the data negotiated and planned for configuring the GOIUB
Parameter
Example
Source
Board Type
GOIUB
WorkMode
E1
Active/Standby Mode
Selected
Load Key
Server
Tributary Numbering
HuaWei mode
TX J0 Byte
Expect RX J0 Byte
TX J1 Byte
Expect RX J1 Byte
TX J2 Byte
Expect RX J2 Byte
TX Frame Format
DOUBLE_FRAME
RX Frame Format
DOUBLE_FRAME
The procedures for configuring the GEIUB and GOIUB are the same. The following procedure
describes how to add a pair of GEIUBs (in active/standby mode) in the GMPS.
3-52
68P02909W07-A
Aug 2008
Procedure
Procedure 3-16
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
Figure 3-39
Set FuncType to Abis interface board, and set Board Type to GEIUB. Set the parameters
by referring to Table 3-20.
Right-click GEIUB.
Continued
68P02909W07-A
3-53
Aug 2008
Procedure 3-16
7
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-40.
Figure 3-40
Continued
3-54
68P02909W07-A
Aug 2008
Procedure 3-16
8
Set Load Key, and click Next. A dialog box is displayed, as shown in Figure 3-41.
Figure 3-41
NOTE
When configuring the port attributes of the GEIUB, select a port number
first, and configure the attributes of this port.
If you select Configure All, all the ports will be configured based on the
settings of the current port displayed in the Port No. drop-down list box.
For the parameters in the dialog box shown in Figure 3-41, use the default settings of the
parameters or modify them according to actual requirements.
10
Mandatory/Optional
68P02909W07-A
3-55
Aug 2008
Prerequisites
The subrack has empty slots to hold the GEPUG.
Preparation
Table 3-22
Example of the data negotiated and planned for configuring the GEPUG
Parameter
Example
Source
Subrack No.
Slot No.
14
FuncType
Gb interface board
Board Type
GEPUG
WorkMode
E1
Active/Standby Mode
Selected
Load Key
Server
Frame Format
CRC4_MULTIFRAME
The following procedure describes how to configure a pair of GEPUGs (in active/standby
mode) in the GMPS.
Procedure
Procedure 3-17
On the BSC Local Manager, click the BSC Device Panel tab. Select the cabinet where the
GMPS/GEPS is located from the Current Cabinet drop-down list.
3-56
68P02909W07-A
Aug 2008
Procedure 3-17
3
Figure 3-42
Set FuncType to Gb interface board, and set Board Type to GEPUG. Set the parameters
by referring to Table 3-22. Click Finish. A pair of GEPUGs is added.
Right-click GEPUG.
Continued
68P02909W07-A
3-57
Aug 2008
Procedure 3-17
6
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-43.
Figure 3-43
Continued
3-58
68P02909W07-A
Aug 2008
Procedure 3-17
7
Set Load Key by referring to Table 3-22, and then click Next. A dialog box is displayed,
as shown in Figure 3-44.
Figure 3-44
Set Frame Format by referring to Table 3-22. For other parameters in the dialog box shown
in Figure 3-44, use the default settings or modify them according to actual requirements.
Mandatory/Optional
Prerequisites
The subrack has empty slots to hold the GFGUG.
68P02909W07-A
3-59
Aug 2008
Preparation
Table 3-23
Example of the data negotiated and planned for configuring the GFGUG
Parameter
Example
Source
Subrack No.
Slot No.
18
FuncType
Gb interface board
Board Type
GFGUG
Net Mode
Independent Mode
Port Type
FE
Load Key
Server
ACTIVE
Logical IP Address
192.168.70.2
Subnet Mask
255.255.255.128
IP Address
192.168.70.132
Subnet Mask
255.255.255.128
Destination IP Address
192.168.80.0
Subnet Mask
255.255.255.128
Gateway
192.168.70.136
Device IP
Port IP
BSC Router
Procedure
Adding a board
a.
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet
number from the Current Cabinet drop-down list.
b.
3-60
68P02909W07-A
Aug 2008
c.
Figure 3-45
d.
Set FuncType to Gb interface board, and set Board Type to GFGUG. Set the
parameters by referring to Table 3-23.
e.
Right-click GFGUG.
b.
Choose Configure Board Attributes from the shortcut menu. A dialog box is
displayed, as shown in Figure 3-46.
68P02909W07-A
3-61
Aug 2008
Figure 3-46
c.
Set Load Key by referring to Table 3-23, and then click Next. A dialog box is
displayed, as shown in Figure 3-47.
Figure 3-47
3-62
68P02909W07-A
Aug 2008
d.
NOTE
When the attribute of a port on the GFGUG is modified, the port becomes
faulty temporarily. If the board is in active/standby mode, an active/standby
switchover is performed automatically.
e.
Figure 3-48
f.
Set the QoS attributes according to actual requirements, and then click Next. A
dialog box is displayed, as shown in Figure 3-49.
68P02909W07-A
3-63
Aug 2008
Figure 3-49
g.
h.
3-64
68P02909W07-A
Aug 2008
Right-click GFGUG and choose Configure Device IP from the shortcut menu. A
dialog box is displayed, as shown in Figure 3-50.
Figure 3-50
b.
68P02909W07-A
3-65
Aug 2008
Figure 3-51
c.
Set the parameters by referring to Table 3-23. Click OK to return to the dialog box
shown in Figure 3-50.
NOTE
Device IP address is the logical IP address for communication. This IP
address is valid for the IP addresses of all the ports of the board. The device
IP addresses for the interface boards operating in active/standby mode
are the same. The IP addresses for the interface boards not operating in
active/standby mode should not be arranged in the same network segment.
d.
3-66
68P02909W07-A
Aug 2008
Right-click GFGUG and choose Configure Ethernet Port IP from the shortcut menu.
A dialog box is displayed, as shown in Figure 3-52.
Figure 3-52
68P02909W07-A
3-67
Aug 2008
b.
Figure 3-53
c.
Set the parameters by referring to Table 3-23. Click OK to return to the dialog box
shown in Figure 3-52.
NOTE
If Port Type is set to FE, one board can be configured with eight port
IP addresses on different network segments. If Port Type is set to GE,
one board can be configured with two port IP addresses on different
network segments. The port IP address and the device IP address must
be configured on different network segments. The port IP addresses for
the active and standby GFGUGs must be configured on the same network
segment.
d.
3-68
68P02909W07-A
Aug 2008
Right-click GFGUG and choose Configure BSC Router from the shortcut menu. A
dialog box is displayed, as shown in Figure 3-54.
Figure 3-54
68P02909W07-A
3-69
Aug 2008
b.
Figure 3-55
c.
CAUTION
Destination IP Address must be set to the network address, and it cannot
be configured on the same network segment with the port IP address of
the GFGUG. Otherwise, Destination IP Address is invalid. Gateway IP
Address and the port IP address of the GFGUG must be configured on
the same network segment.
d.
e.
3-70
68P02909W07-A
Aug 2008
Mandatory/Optional
NOTE
One BSC cabinet can be configured with only one EAC.
Prerequisites
The subrack that holds the EAC is configured.
Preparation
None.
Procedure
Procedure 3-18
1
68P02909W07-A
3-71
Aug 2008
Procedure 3-18
2
Choose Configure BSC EAC from the shortcut menu. A dialog box is displayed, as shown
in Figure 3-56.
Figure 3-56
NOTE
Use the default settings of the parameters or modify them according to actual
requirements.
Continued
3-72
68P02909W07-A
Aug 2008
Procedure 3-18
3
Figure 3-57
NOTE
Use the default settings of the parameters or modify them according to actual
requirements.
4
Mandatory/Optional
Mandatory
68P02909W07-A
3-73
Aug 2008
NOTE
Prerequisites
Configure the two subracks between which the communication link is to be established.
Preparation
NOTE
Assume that the BSC is configured with one GMPS, two GEPSs, and two GTCSs. The
GMPS is subrack 0, GEPSs are subracks 1 and 3, and GTCSs are subracks 6 and 7.
Table 3-24 Example of the data negotiated and planned for configuring the
communication link between GMPS 0 and GEPS 1
Parameter
Example
Source
Subrack1 No.
Subrack2 No.
0 (active), 1 (standby)
0 (active), 1 (standby)
Table 3-25 Example of the data negotiated and planned for configuring the
communication link between GMPS 0 and GEPS 3
Parameter
Example
Source
Subrack1 No.
Subrack2 No.
2 (active), 3 (standby)
0 (active), 1 (standby)
3-74
68P02909W07-A
Aug 2008
Table 3-26 Example of the data negotiated and planned for configuring the
communication link between GEPS 1 and GEPS 3
Parameter
Example
Source
Subrack1 No.
Subrack2 No.
2 (active), 3 (standby)
2 (active), 3 (standby)
Table 3-27 Example of the data negotiated and planned for configuring the
communication link between GTCS 6 and GTCS 7
Parameter
Example
Source
Subrack1 No.
Subrack2 No.
0 (active), 1 (standby)
0 (active), 1 (standby)
The following procedure describes how to configure the mesh interconnection between subracks
through TDM ports.
Procedure
68P02909W07-A
3-75
Aug 2008
b.
Choose Configure Subrack Communication Link from the shortcut menu. A dialog
box is displayed, as shown in Figure 3-58.
Figure 3-58
3-76
68P02909W07-A
Aug 2008
c.
Figure 3-59
d.
e.
Click OK. The first communication link between GMPS 0 and GEPS 1 is configured.
f.
Repeat Step a through Step e to configure the second communication link between
GMPS 0 and GEPS 1.
68P02909W07-A
3-77
Aug 2008
b.
Choose Configure Subrack Communication Link from the shortcut menu. A dialog
box is displayed, as shown in Figure 3-60.
Figure 3-60
3-78
68P02909W07-A
Aug 2008
c.
Figure 3-61
d.
e.
Click OK. The first communication link between GMPS 0 and GEPS 3 is configured.
f.
Repeat Step a through Step e to configure the second communication link between
GMPS 0 and GEPS 3.
68P02909W07-A
3-79
Aug 2008
b.
Choose Configure Subrack Communication Link from the shortcut menu. A dialog
box is displayed, as shown in Figure 3-62.
Figure 3-62
3-80
68P02909W07-A
Aug 2008
c.
Figure 3-63
d.
e.
Click OK. The first communication link between GEPS 1 and GEPS 3 is configured.
f.
Repeat Step a through Step e to configure the second communication link between
GEPS 1 and GEPS 3.
68P02909W07-A
3-81
Aug 2008
a.
b.
Choose Configure Subrack Communication Link from the shortcut menu. A dialog
box is displayed, as shown in Figure 3-64.
Figure 3-64
3-82
68P02909W07-A
Aug 2008
c.
Figure 3-65
d.
e.
Click OK. The first communication link between GTCS 6 and GTCS 7 is configured.
f.
Repeat Step a through Step e to configure the second communication link between
GTCS 6 and GTCS 7.
68P02909W07-A
3-83
Aug 2008
This section describes how to configure the BSC links on the Ater Interface , A Interface and Gb
Interface when the BM and TC are configured in different subracks. These links are responsible
for the signaling transmission within the BSC and between the BSC and other NEs. BSC links
are the links on the Ater interface, A Interface, and Gb interface.
Mandatory/Optional
Mandatory
CAUTION
If the GTCS is configured on the MSC side, an Ater connection path should be
established between the GMPS/GEPS and the main GTCS. The Ater connection path is
established between GEIUTs or between GOIUTs. Specify different ports to configure
more than one Ater connection path between interface boards. A maximum of 32 Ater
connection paths can be configured between GEIUTs/GOIUTs.
3-84
68P02909W07-A
Aug 2008
Prerequisites
The subracks between which the Ater connection path is to be established, are configured
and the GMPS or the GEPS is configured with the subrack-OSP mapping. For changes in
the document, refer to Configuring the Subrack-OSP Mapping on page 3-11.
The GEIUT/GOIUT in the two subracks between which the Ater connection path is to
be established, is configured. For changes in the document, refer to Configuring the
GEIUT/GOIUT on page 3-47.
Preparation
Table 3-28 Example of the data negotiated and planned for configuring the Ater
connection path between the GMPS and the GTCS
Parameter
Example
Source
BM Subrack No.
BM Slot No.
16
BM Port No.
TC Subrack No.
TC Slot No.
16
TC Port No.
Table 3-29 Example of the data negotiated and planned for configuring the Ater
connection path between the GEPS and the GTCS
Parameter
Example
Source
BM Subrack No.
BM Slot No.
16
BM Port No.
TC Subrack No.
TC Slot No.
16
TC Port No.
The following procedure describes how to configure the Ater connection path between the
GMPS and the GTCS. On the LMT, the GMPS and the GEPS are collectively known as the BM
subrack. They are identified by different subrack numbers.
68P02909W07-A
3-85
Aug 2008
Procedure
Procedure 3-19
Choose Configure Ater Connection Path from the shortcut menu. A dialog box is
displayed, as shown in Figure 3-66.
Figure 3-66
Continued
3-86
68P02909W07-A
Aug 2008
Procedure 3-19
3
Figure 3-67
Click Finish. The Ater connection path between the GMPS and the GTCS is configured.
Repeat step 1 through step 6 to add more Ater connection paths between the GMPS and
the GTCS.
Mandatory/Optional
68P02909W07-A
3-87
Aug 2008
CAUTION
The timeslot mask of an Ater OML must contain TS1. By default, TS1 is selected
on the LMT. Except TS1, at least four consecutive timeslots must be selected.
Prerequisites
The Ater connection path between the GMPS and the main GTCS is configured.
Preparation
Table 3-30
Parameter
Example
Source
Timeslot Mask
TS1, TS2TS17
Procedure
Procedure 3-20
3-88
68P02909W07-A
Aug 2008
Procedure 3-20
2
Choose Add Ater OML from the shortcut menu. A dialog box is displayed, as shown in
Figure 3-68.
Figure 3-68
Continued
68P02909W07-A
3-89
Aug 2008
Procedure 3-20
3
Figure 3-69
NOTE
By default, TS1 is configured. Configure TS2TS17 by referring to Table 3-30.
When the total number of the GMPSs and GEPSs is not greater than two,
you can select timeslots TS1T17.
When the total number of the GMPSs and GEPSs exceeds two, you can select
timeslots TS1TS31.
Postrequisites
If the bandwidth of the Ater OML is modified during the loading of the interface
board in the remote subrack, the load path is disrupted. The interface board will
be reset after five minutes of loading attempts.
3-90
68P02909W07-A
Aug 2008
If you delete all the Ater OMLs, it is possible that the assignment is successful but there is no
speech when you make a call. This problem disappears after you configure the Ater OMLs again.
Mandatory/Optional
NOTE
A maximum of eight Ater signaling links can be configured for the GMPS or the
GEPS where the Ater connection path is located.
Prerequisites
The Ater connection path between the GMPS/GEPS and the GTCS is configured. For
details, refer to Configuring the Ater Connection Path on page 3-84.
Preparation
Table 3-31
link
Example of the data negotiated and planned for adding an Ater signaling
Parameter
Example
Source
Timeslot No.
18
Transfer Mode
Terrestrial Transmission
90
60
Window Size
16
68P02909W07-A
3-91
Aug 2008
Procedure
Procedure 3-21
Choose Add Ater Signaling Link from the shortcut menu. A dialog box is displayed, as
shown in Figure 3-70.
Figure 3-70
Continued
3-92
68P02909W07-A
Aug 2008
Procedure 3-21
3
Figure 3-71
NOTE
One 64 kbit/s Ater signaling link can be configured with only one timeslot. In
addition, the Timeslot Mask of the Ater signaling link cannot be TS1.
4
68P02909W07-A
3-93
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
The GEIUA/GOIUA in the GTCS is configured. For details, refer to Configuring the
GEIUA/GOIUA on page 3-41.
Preparation
Table 3-32 Example of the data negotiated and planned for configuring an A
Interface E1/T1
Parameter
Example
Source
Subrack No.
Slot No.
20
Port Number
Start CIC
Procedure
Procedure 3-22
3-94
68P02909W07-A
Aug 2008
Procedure 3-22
2
Choose Configure A Interface E1/T1 from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-72.
Figure 3-72
Continued
68P02909W07-A
3-95
Aug 2008
Procedure 3-22
3
Figure 3-73
On the A Interface E1/T1 Attributes tab page, set the parameters by referring to
Table 3-32.
NOTE
One CIC group contains 32 CICs. If multiple E1s/T1s have the same OSP and the
same DSP group, the start CIC for each E1/T1 must be unique. If the start CIC of
the first E1/T1 is 0, then the start CIC of the second E1/T1 and that of the first
E1/T1 must be in different groups, and the start CIC of the second E1/T1 must
be greater than 31. On the CIC Attributes tab page, use the default settings or
modify them according to actual requirements.
5
Repeat step 1 through step 6 to add more E1/T1 connections on the A interface.
3-96
68P02909W07-A
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
The SS7 DSP is configured. For details, refer to Configuring the SS7 Signaling Points on
page 3-5.
The GXPUM is configured in the GMPS or GEPS that is connected to the GTCS. The Ater
connection path is configured. For details, refer to Configuring the GXPUM on page 3-24
and Configuring the Ater Connection Path on page 3-84.
Preparation
Table 3-33
link
Example of the data negotiated and planned for adding an SS7 signaling
Parameter
Example
Source
Rate Type
64 kbit/s
A Subrack No.
A Slot No.
20
A Port No.
TS19
TS16
SLC
SLC Send
The following procedure provides an example of configuring a 64 kbit/s SS7 signaling link
on the GEIUA in the GTCS.
68P02909W07-A
3-97
Aug 2008
Procedure
Procedure 3-23
Choose Configure SS7 Signaling Link from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-74.
Figure 3-74
Continued
3-98
68P02909W07-A
Aug 2008
Procedure 3-23
3
Figure 3-75
NOTE
In BM/TC separated mode, if the GTCS is configured on the MSC side, do not
set Ater Timeslot Mask to TS1 for the SS7 signaling link configured in the
main GTCS.
4
On the MPT2 tab page, set the parameters by referring to Table 3-33.
NOTE
The number of timeslots on the A interface must be the same as that on the Ater
interface.
Continued
68P02909W07-A
3-99
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Procedure 3-23
5
Chapter
Click the MTP3 tab, the tab page is displayed, as shown in Figure 3-76.
Figure 3-76
3-100
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Mandatory/Optional
Mandatory
NOTE
When adding an NSE, set the NSE identifier, subnetwork protocol type, and
agent subrack number.
One BSC can be configured with a maximum of 128 NSEs. Multiple NSEs can be
assigned on the same agent subrack.
Prerequisites
None.
Preparation
Table 3-34 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over FR
Network planning
Network planning
Procedure
Procedure 3-24
68P02909W07-A
3-101
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Procedure 3-24
2
Chapter
Choose Configure PCU Data>Configure NSE from the shortcut menu. A dialog box is
displayed, as shown in Figure 3-77.
Figure 3-77
Continued
3-102
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 3-24
3
Figure 3-78
Set the parameters by referring to Table 3-34. Click OK to return to the dialog box shown
in Figure 3-77.
Configuring the BC
This section describes how to configure the bearer channel (BC) on the Gb interface when the
Gb interface uses the FR transmission mode. The BC is responsible for the data transmission
between the BSC and the SGSN.
Scenario
Mandatory/Optional
NOTE
BC refers to a fixed number of timeslots on the E1/T1 when the Gb interface uses the
FR transmission mode.
68P02909W07-A
3-103
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Chapter
Prerequisites
The GEPUG is configured. For details, refer to Configuring the GEPUG (Gb over FR)
on page 3-55.
Preparation
Table 3-35 Example of the data negotiated and planned for configuring the BC on
the Gb interface
Parameter
Example
Source
Subrack No.
Slot No.
18
Port No.
Bearer Channel ID
Q933
Occupied Timeslot
T1-T16
10
Procedure
Procedure 3-25
Configuring the BC
3-104
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 3-25
2
Choose Configure BC from the shortcut menu. A dialog box is displayed, as shown in
Figure 3-79.
Figure 3-79
Continued
68P02909W07-A
3-105
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Procedure 3-25
3
Chapter
Figure 3-80
Mandatory/Optional
3-106
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
NOTE
The clock signal on the SGSN side is carried by the BC. Configure the SGSN clock by
specifying the port of the BC.
Prerequisites
The GEPUG is configured. For details, refer to Configuring the GEPUG (Gb over FR)
on page 3-55.
Preparation
Table 3-36
clock
Example of the data negotiated and planned for configuring the SGSN
Parameter
Example
Source
Procedure
Procedure 3-26
68P02909W07-A
3-107
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Procedure 3-26
2
Chapter
Choose Config SGSN Clock from the shortcut menu. A dialog box is displayed, as shown
in Figure 3-81.
Figure 3-81
Mandatory/Optional
3-108
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
NOTE
NSVC refers to the virtual connection on the NS layer. One NSVC is located on
the BC of one E1/T1 and belongs to one BC/NSE. One BC/NSE can be configured
with multiple NSVCs.
One NSVC corresponds to one PVC. When configuring an NSVC, specify the
corresponding PVC.
Prerequisites
The GEPUG is configured. For details, refer to Configuring the GEPUG (Gb over FR)
on page 3-55.
The NSE is configured. For details, refer to Configuring the NSE on page 3-101.
The BC is configured.
Preparation
Table 3-37 Example of the data negotiated and planned for configuring the NSVC
on the Gb interface
Parameter
Example
Source
NSVC Identifier
NSE Identifier
Subrack No.
Slot No.
18
Port Number
Bearer Channel ID
16
Procedure
Procedure 3-27
68P02909W07-A
3-109
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Procedure 3-27
2
Chapter
Choose Configure NSVC from the shortcut menu. A dialog box is displayed, as shown
in Figure 3-82.
Figure 3-82
Continued
3-110
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 3-27
3
Figure 3-83
Mandatory/Optional
Mandatory
NOTE
One GPRS cell can be configured with only one PTPBVC. One NSE can be configured
with multiple PTPBVCs.
68P02909W07-A
3-111
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Chapter
Prerequisites
The NSE is configured. For details, refer to Configuring the NSE on page 3-101.
A GPRS cell is configured and the activity state of the cell is Activated.
Preparation
Table 3-38 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
Cell Name
Cell 1
Procedure
Procedure 3-28
3-112
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 3-28
2
Choose Configure PCU Data>Configure PTPBVC from the shortcut menu. A dialog
box is displayed, as shown in Figure 3-84.
Figure 3-84
Continued
68P02909W07-A
3-113
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Procedure 3-28
3
Chapter
Figure 3-85
3-114
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Mandatory/Optional
Mandatory
NOTE
When adding an NSE, set the NSE identifier, subnetwork protocol type, and
agent subrack number.
One BSC can be configured with a maximum of 128 NSEs. Multiple NSEs can
be assigned on the same agent subrack.
Prerequisites
None.
Preparation
Table 3-39 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over IP
Network planning
Network planning
Procedure
Procedure 3-29
68P02909W07-A
3-115
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Procedure 3-29
2
Chapter
Choose Configure PCU Data>Configure NSE from the shortcut menu. A dialog box is
displayed, as shown in Figure 3-86.
Figure 3-86
Continued
3-116
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Procedure 3-29
3
Figure 3-87
Mandatory/Optional
Prerequisites
The GFGUG is configured. For details, refer to Configuring the GFGUG (Gb over IP) on
page 3-59.
68P02909W07-A
3-117
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Chapter
Preparation
Table 3-40 Example of the data negotiated and planned for configuring the local
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.70.1
18
100
100
Procedure
Procedure 3-30
3-118
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Procedure 3-30
2
Choose Configure Local NSVL from the shortcut menu. A dialog box is displayed, as
shown in Figure 3-88.
Figure 3-88
Continued
68P02909W07-A
3-119
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Procedure 3-30
3
Chapter
Figure 3-89
Mandatory/Optional
Prerequisites
The GFGUG is configured. For details, refer to Configuring the GFGUG (Gb over IP) on
page 3-59.
3-120
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Preparation
Table 3-41 Example of the data negotiated and planned for configuring the remote
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.80.1
IP Port No.
100
100
Procedure
Procedure 3-31
Choose Configure PCU Data>Configure Remote NSVL from the shortcut menu. A dialog
box is displayed, as shown in Figure 3-90.
Figure 3-90
Continued
68P02909W07-A
3-121
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Procedure 3-31
3
Chapter
Figure 3-91
Mandatory/Optional
Mandatory
NOTE
One GPRS cell can be configured with only one PTPBVC. One NSE can be configured
with multiple PTPBVCs.
3-122
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Prerequisites
The NSE is configured. For details, refer to Configuring the NSE on page 3-115.
A GPRS cell is configured and the activity state of the cell is Activated.
Preparation
Table 3-42 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
Cell Name
Cell 1
Procedure
Procedure 3-32
68P02909W07-A
3-123
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
3: Configuring the BSC (BM/TC Separated)
Procedure 3-32
2
Chapter
Choose Configure PCU Data>Configure PTPBVC from the shortcut menu. A dialog
box is displayed, as shown in Figure 3-92.
Figure 3-92
Continued
3-124
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Procedure 3-32
3
Figure 3-93
68P02909W07-A
3-125
Aug 2008
This section describes how to configure BSC clock signals when the BM and TC are configured
in different subracks. The BSC clock signals are responsible for the synchronization of boards in
each subrack.
Mandatory/Optional
Mandatory
NOTE
If the GEIUA is configured in the GTCS, two line clock signals, line 0 and line
1, can be configured on the A Interface E1/T1 of the GTCS. If the GOIUA is
configured in the GTCS, only one line clock signal can be configured for each
GOIUA and the line clock signal must be configured on port 0 on the GOIUA.
Prerequisites
The GEIUA/GOIUA in the GTCS is configured. For details, refer to Configuring the
GEIUA/GOIUA on page 3-41.
If the line clock is to be configured on the GEIUA, an A Interface E1/T1 in the GTCS
must be configured. For changes in the document, refer to Adding an A Interface E1/T1
on page 3-94.
3-126
68P02909W07-A
Aug 2008
Preparation
Table 3-43 Example of the data negotiated and planned for configuring the clock
on line 0 for the GTCS
Parameter
Example
Source
Line No.
LINE0
8K
20
Table 3-44 Example of the data negotiated and planned for configuring the clock
on line 1 for the GTCS
Parameter
Example
Source
Line No.
LINE1
8K
20
The following procedure describes how to configure two line clock signals on the GEIUA in
the GTCS.
Procedure
Procedure 3-33
1
68P02909W07-A
3-127
Aug 2008
Procedure 3-33
2
Choose Configure Line Clock from the shortcut menu. A dialog box is displayed, as shown
in Figure 3-94.
Figure 3-94
NOTE
When the A interface E1 where the port of the selected Board Port No. is located
incurs a fault, the GTCS cannot extract the line clock from the A interface. In this
case, the GTCS can extract the line clock from the A interface through the A
interface E1 where the port of the selected Backup Port No. is located.
Board Slot No.: Number of the slot where the GEIUA/GOIUA configured
with the A interface E1 is located.
3-128
68P02909W07-A
Aug 2008
Procedure 3-33
6
Select LINE1 and set the parameters by referring to Table 3-44, as shown in Figure 3-95.
Figure 3-95
Repeat step 1 through step 7 to configure the line clock for each GTCS.
Mandatory/Optional
Mandatory
Prerequisites
The GSCU in the GTCS is configured. For details, refer to Configuring the GSCU on page
3-31.
68P02909W07-A
3-129
Aug 2008
Preparation
Table 3-45 Example of the data negotiated and planned for configuring the 8K
reference clock for the GTCS
Parameter
Example
Source
LINE CLOCK
Procedure
Procedure 3-34
Choose Configure 8K Reference Clock from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-96.
Figure 3-96
3-130
68P02909W07-A
Aug 2008
Mandatory/Optional
Mandatory
NOTE
On the GEIUT, up to two line clock signals can be configured on the Ater connection
paths of the GMPS. One line clock corresponds to one Ater connection path. On the
GEIUT, only one line clock can be configured on port 0 of the GOIUT.
Prerequisites
The GEIUT/GOIUT in the GMPS is configured. For details, refer to Configuring the
GEIUT/GOIUT on page 3-47.
The GGCU in the GMPS is configured. For details, refer to Configuring the GGCU on
page 3-33.
If the line clock is to be configured on the GEIUT, the Ater connection path in the
GMPS must be configured. For changes in the document, refer to Configuring the Ater
Connection Path on page 3-84.
Preparation
Table 3-46 Example of the data negotiated and planned for configuring the clock
on line 0 for the GMPS
Parameter
Example
Source
Line No.
LINE0
8K
16
68P02909W07-A
3-131
Aug 2008
Table 3-47 Example of the data negotiated and planned for configuring the clock
on line 1 for the GMPS
Parameter
Example
Source
Line No.
LINE1
8K
16
The following procedure describes how to configure two line clock signals on the GEIUT in
the GMPS.
Procedure
Procedure 3-35
Choose Configure Line Clock from the shortcut menu. A dialog box is displayed, as shown
in Figure 3-97.
Figure 3-97
Continued
3-132
68P02909W07-A
Aug 2008
Procedure 3-35
NOTE
If the Ater connection path, where the port of the selected Board Port No. is
located, incurs a fault, the GMPS cannot extract the line clock from the Ater
interface. In this case, the GMPS can extract the line clock from the Ater interface
through the Ater connection path where the port of the selected Backup Port
No. is located.
Board Slot No.: Number of the slot where the GEIUT/GOIUT configured
with the Ater connection path is located.
Board Port No.: Number of the port connected to one Ater connection
path on the GEIUT/GOIUT.
Backup Port No.: Number of the port connected to another Ater connection
path on the GEIUT.
Select LINE1 and set the parameters by referring to Table 3-47, as shown in Figure 3-98.
Figure 3-98
68P02909W07-A
3-133
Aug 2008
Mandatory/Optional
Mandatory
NOTE
The clock for the GGCU can be the BITS clock or the line clock extracted by the
GEIUT/GOIUT from the GTCS connected. The GGCU processes the input clock and
generates the 8 kHz clock, which is used as the transmission synchronization clock
and the time synchronization clock for the boards in the GMPS or GEPS.
The system clock has four priorities: priority 1 to priority 4, from the highest
to the lowest.
When the BITS clock is provided, it should be configured as the system clock
and enjoys the highest priority.
Prerequisites
The GGCU in the GMPS is configured. For details, refer to Configuring the GGCU on
page 3-33.
The BITS clock is ready, or the line clock for the GMPS is configured.
Preparation
Table 3-48
clock
Example of the data negotiated and planned for configuring the system
Parameter
Example
Source
Priority
2M external clock 0
LINE0
LINE1
2 MHz
8 kHz
8 kHz
Source Type
Source Sub-type
3-134
68P02909W07-A
Aug 2008
Procedure
Procedure 3-36
Choose Configure System Clock from the shortcut menu. A dialog box is displayed, as
shown in Figure 3-99.
Figure 3-99
CAUTION
Source Type and Work Mode cannot be configured in one operation. Configure
them separately. After configuring Source Type, exit the configuration wizard,
and then start the configuration wizard again to configure Work Mode.
3
68P02909W07-A
3-135
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
The GSCU in the GMPS is configured. For details, refer to Configuring the GSCU on
page 3-31.
The GGCU in the GMPS is configured. For details, refer to Configuring the GGCU on
page 3-33.
Preparation
Table 3-49 Example of data negotiated and planned for configuring the 8K reference
clock for the GMPS
Parameter
Example
Source
GGCU Backplane
Procedure
Procedure 3-37
1
3-136
68P02909W07-A
Aug 2008
Procedure 3-37
2
Choose Configure 8K Reference Clock from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-100.
Figure 3-100
Mandatory/Optional
Mandatory
68P02909W07-A
3-137
Aug 2008
Prerequisites
The GSCU in the GEPS is configured. For details, refer to Configuring the GSCU on page
3-31.
The GGCU in the GMPS is configured. For details, refer to Configuring the GGCU on
page 3-33.
Preparation
Table 3-50 Example of the data negotiated and planned for configuring the 8K
reference clock for the GEPS
Parameter
Example
Source
GGCU Panel
Procedure
Procedure 3-38
1
3-138
68P02909W07-A
Aug 2008
Procedure 3-38
2
Choose Configure 8K Reference Clock from the shortcut menu. A dialog box is displayed,
as shown in Figure 3-101.
Figure 3-101
Repeat step 1 through step 4 to configure the 8K reference clock for more GEPSs.
68P02909W07-A
Aug 2008
3-139
3-140
68P02909W07-A
Aug 2008
Chapter
4
Configuring the BSC (BM/TC Combined)
68P02909W07-A
Aug 2008
4-1
This section describes how to configure the BSC global data, devices, links, and clock on the
BSC Local Manager when the BM and TC are configured in same subracks.
4-2
68P02909W07-A
Aug 2008
When the BM and TC are configured in the same subrack, the BSC global data includes BSC
attributes, SS7 signaling point data, and subrack-OSP mapping.
Basic Data
BSC Timer
Software Parameters
SCCP
IP Transfers
Scenario
Mandatory/Optional
Mandatory
Prerequisites
The BSC attributes have been determined in network planning.
68P02909W07-A
4-3
Aug 2008
Preparation
Table 4-1 Example of the data negotiated and planned for configuring BSC attributes
(BM/TC combined)
Parameter
Example
Source
BSC Name
BSC001
Network planning
Country Code
86
Network planning
City Code
021
Network planning
MCC
460
Network planning
MNC
10
Network planning
A Interface Tag
GSM_PHASE_2+
Network planning
Um Interface Tag
GSM_PHASE_2+
Network planning
GSM_PHASE_2+
Network planning
NTP Server
10.161.72.251
BM/TC Together
Network planning
Procedure
Procedure 4-1
1
4-4
68P02909W07-A
Aug 2008
Procedure 4-1
2
Choose Configure BSC Attributes from the shortcut menu. A dialog box is displayed, as
shown in Figure 4-1.
Figure 4-1
On the Basic Data tab page, set the parameters by referring to Table 4-1.
NOTE
The parameters not listed in Table 4-1 are optional. Retain their default settings
or modify them according to actual requirements.
4
Mandatory/Optional
Mandatory
68P02909W07-A
4-5
Aug 2008
CAUTION
The OSP and DSP must be configured before the STP is configured.
The BSC can be configured with up to four OSPs, 32 DSPs, and 32 STPs. For
details on the configuration of multiple OSPs, refer to Local multiple signaling
points.
Prerequisites
None.
Preparation
Table 4-2
and DSP
Example of the data negotiated and planned for configuring the SS7 OSP
Parameter
Example
Source
OPC Name
BSC001
OPC (Hex)
B1
Network planning
Encoding Scheme
14
Network planning
Network Indicator
NATB
Network planning
DPC Name
MSC001
DPC (Hex)
D1
Network planning
Table 4-3
Example of the data negotiated and planned for configuring the STP
Parameter
Example
Source
STP Name
STPMSC001
STP (Hex)
C1
Network planning
ITU-T
Network planning
The following procedure describes how to configure the SS7 Signaling Points
Procedure
b.
Choose Configure SS7 Signaling Point from the shortcut menu. A dialog box is
displayed, as shown in Figure 4-2.
4-6
68P02909W07-A
Aug 2008
Figure 4-2
c.
On the OPC tab page, click Add OPC. A dialog box is displayed, as shown in
Figure 4-3.
Figure 4-3
68P02909W07-A
4-7
Aug 2008
NOTE
If an OPC exists, OPC Name, Encoding Scheme, and Network Indicator
of the OSP are displayed by default in the dialog box shown in Figure 4-3.
d.
e.
In the dialog box shown in Figure 4-2, click the DPC tab to display the tab page,
as shown in Figure 4-4.
Figure 4-4
b.
4-8
68P02909W07-A
Aug 2008
Figure 4-5
NOTE
If there is no direct physical link between the OSP and the DSP, configure
STPs. In the dialog box shown in Figure 4-5, set Using STP to Yes.
c.
d.
Check whether there is a direct physical link between the OSP and the DSP.
Then...
If...
There is a direct physical link between the OSP and
the DSP
In the dialog box shown in Figure 4-2, click the STP tab to display the tab page,
as shown in Figure 4-6.
68P02909W07-A
4-9
Aug 2008
Figure 4-6
b.
Figure 4-7
4-10
68P02909W07-A
Aug 2008
c.
d.
Mandatory/Optional
Mandatory
NOTE
By default, the GMPS is displayed on the LMT. Configure only its OSP on the LMT. For
the GEPS, configure it and its OSP on the LMT.
Prerequisites
The SS7 OSP is already configured.
Preparation
Table 4-4 Example of the data negotiated and planned for configuring the
subrack-OSP mapping
Parameter
Example
Source
Subrack No.
OSP
B1
Network planning
Procedure
Procedure 4-2
1
68P02909W07-A
4-11
Aug 2008
Procedure 4-2
2
Choose Configure Subrack-OSP Mapping from the shortcut menu. A dialog box is
displayed, as shown in Figure 4-8.
Figure 4-8
4-12
68P02909W07-A
Aug 2008
This section describes how to configure BSC devices on the LMT when the BM and TC are
configured in the same subrack.
Mandatory/Optional
NOTE
The GBCR cabinet is displayed by default on the LMT. Configure the GBSR cabinet
on the LMT. Zero or one GBSR cabinet can be configured on the basis of the actual
traffic volume and transmission mode on the A Interface.
Prerequisites
None.
Preparation
Table 4-5
Example of the data negotiated and planned for configuring a GBSR cabinet
Parameter
Example
Source
Cabinet No.
Cabinet Type
Local Cabinet
Procedure
Procedure 4-3
1
68P02909W07-A
4-13
Aug 2008
Adding a GEPS
Procedure 4-3
2
Choose Add BSC Cabinet from the shortcut menu. A dialog box is displayed, as shown
in Figure 4-9.
Figure 4-9
Adding a GEPS
This section describes how to add a GEPS and configure its attributes on the LMT.
Scenario
Mandatory/Optional
NOTE
The GEPS processes the basic services of the BSC. The settings of the GEPS depend
on the traffic volume of the BSC. When the BM and TC are configured in the same
subrack, the BSC can be configured with up to three GEPSs. A fan box is automatically
added when you add a subrack. Configure only the attributes of the fan box.
4-14
68P02909W07-A
Aug 2008
Adding a GEPS
Prerequisites
The OSP is already configured. For details, refer to Configuring the SS7 Signaling Points
on page 3-5.
Preparation
Table 4-6
Parameter
Example
Source
Subrack Type
GEPS
OPC
B1
Network planning
Procedure
Procedure 4-4
Adding a GEPS
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
68P02909W07-A
4-15
Aug 2008
Adding a GEPS
Procedure 4-4
3
Figure 4-10
4-16
68P02909W07-A
Aug 2008
Procedure 4-4
7
Choose Configure Fan Box Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-11.
Figure 4-11
For the parameters in the dialog box shown in Figure 4-11, use the default settings or modify
them according to actual requirements.
10
Postrequisites
Before deleting the GEPSs that are initially configured, ensure that they are powered off.
Mandatory/Optional
Mandatory
68P02909W07-A
4-17
Aug 2008
NOTE
Any subrack in the cabinet can be configured as the management subrack for the
power distribution box.
Prerequisites
The subrack that manages the power distribution box is configured.
Preparation
Table 4-7 Example of the data negotiated and planned for configuring a power
distribution box
Parameter
Example
Source
Cabinet No.
Normal Power
Distribution Box
Procedure
Procedure 4-5
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
4-18
68P02909W07-A
Aug 2008
Procedure 4-5
3
Choose Add Power Distribution Box. A dialog box is displayed, as shown in Figure 4-12.
Figure 4-12
68P02909W07-A
4-19
Aug 2008
Procedure 4-5
7
Choose Configure Power Distribution Box Attributes from the shortcut menu. A dialog
box is displayed, as shown in Figure 4-13.
Figure 4-13
For the parameters in the dialog box shown in Figure 4-13, use the default settings or modify
them according to actual requirements.
10
Repeat step 1 through step 9 to configure power distribution boxes for more subracks.
4-20
68P02909W07-A
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
None.
NOTE
When the GXPUM is configured in the GMPS, parameters such as Load Key and Port
Attributes can be configured. When the GXPUM is configured in the GEPS, only
Load Key can be configured.
Preparation
Table 4-8
Example of the data negotiated and planned for configuring the GXPUM
Parameter
Example
Source
Load Key
Server
Selected
68P02909W07-A
4-21
Aug 2008
Procedure
Procedure 4-6
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet where the
GMPS is located from the Current Cabinet drop-down list.
Figure 4-14
Right-click GXPUM.
Continued
4-22
68P02909W07-A
Aug 2008
Procedure 4-6
7
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-15.
Figure 4-15
68P02909W07-A
4-23
Aug 2008
Procedure 4-6
9
Figure 4-16
10
4-24
68P02909W07-A
Aug 2008
Procedure 4-6
11
Figure 4-17
12
13
Mandatory/Optional
Prerequisites
None.
68P02909W07-A
4-25
Aug 2008
Preparation
Table 4-9
Example of the data negotiated and planned for configuring the GXPUT
Parameter
Example
Source
Board Type
GXPUT
Active/Standby Mode
Selected
Load Key
Server
Procedure
Procedure 4-7
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet where the
GMPS is located from the Current Cabinet drop-down list.
Figure 4-18
4-26
68P02909W07-A
Aug 2008
Procedure 4-7
Right-click a GXPUT.
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-19.
Figure 4-19
Mandatory/Optional
Mandatory
Prerequisites
None.
68P02909W07-A
4-27
Aug 2008
Preparation
Table 4-10
Example of the data negotiated and planned for configuring the GSCU
Parameter
Example
Source
Load Key
Server
Procedure
Procedure 4-8
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-20.
Figure 4-20
4-28
68P02909W07-A
Aug 2008
Procedure 4-8
4
Figure 4-21
NOTE
Among the 12 ports on the GSCU, the alarm reporting function of all the
ports, except for ports 0, 1, 10, and 11, are disabled by default on the LMT.
Enable the alarm reporting function of the port connected to the Ethernet
cable to monitor whether the port is normal.
Mandatory/Optional
Mandatory
Prerequisites
None.
68P02909W07-A
4-29
Aug 2008
Preparation
Table 4-11
Example of the data negotiated and planned for configuring the GTNU
Parameter
Example
Source
Load Key
Server
Procedure
Procedure 4-9
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-22.
Figure 4-22
4-30
68P02909W07-A
Aug 2008
Scenario
Mandatory/Optional
Mandatory
Prerequisites
None.
Preparation
Table 4-12
Example of the data negotiated and planned for configuring the GGCU
Parameter
Example
Source
Load Key
Server
Procedure
Procedure 4-10
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-23.
Figure 4-23
68P02909W07-A
4-31
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
The GMPS/GEPS has empty slots to hold the GDPUX.
Preparation
Table 4-13
Example of the data negotiated and planned for configuring the GDPUX
Parameter
Example
Source
FuncType
Other board
Board Type
GDPUX
Load Key
Server
The following procedure describes how to configure the GDPUX in the GMPS.
Procedure
Procedure 4-11
4-32
68P02909W07-A
Aug 2008
Procedure 4-11
3
Figure 4-24
Set FuncType to Other board, and set Board Type to GDPUX. Then click Finish. A
GDPUX is added.
Right-click GDPUX.
Continued
68P02909W07-A
4-33
Aug 2008
Procedure 4-11
6
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-25.
Figure 4-25
Continued
4-34
68P02909W07-A
Aug 2008
Procedure 4-11
Figure 4-26
NOTE
When configuring the DSP TC attributes, select a DSP TC number first, and
then configure the attributes of this DSP TC.
If you select Configure All, all the DSP TCs will be configured based on the
settings of the current DSP TC displayed in the DSP TC No. drop-down
list box.
Modify the parameters in the dialog box shown in Figure 4-26 according to actual
requirements.
10
68P02909W07-A
4-35
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
The GMPS/GEPS has empty slots to hold the GDPUP.
Preparation
Table 4-14
Example of the data negotiated and planned for configuring the GDPUP
Parameter
Example
Source
Subrack No.
Slot No.
Board Type
GDPUP
Load Key
Server
Procedure
Procedure 4-12
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
4-36
68P02909W07-A
Aug 2008
Procedure 4-12
3
Figure 4-27
Set FuncType to Other board, and set Board Type to GDPUP. Then click Finish. A
GDPUP is added.
Right-click GDPUP.
Continued
68P02909W07-A
4-37
Aug 2008
Procedure 4-12
6
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-28.
Figure 4-28
Mandatory/Optional
Mandatory
Prerequisites
The GMPS/GEPS has empty slots to hold the GEIUA/GOIUA.
4-38
68P02909W07-A
Aug 2008
Preparation
Table 4-15
Example of the data negotiated and planned for configuring the GEIUA
Parameter
Example
Source
Board Type
GEIUA
WorkMode
E1
Active/Standby Mode
Selected
Load Key
Server
Frame Format
DOUBLE_FRAME
Table 4-16
Example of the data negotiated and planned for configuring the GOIUA
Parameter
Example
Source
Board Type
GOIUA
WorkMode
E1
Active/Standby Mode
Selected
Load Key
Server
Tributary Numbering
HuaWei mode
TX J0 Byte
Expect RX J0 Byte
TX J1 Byte
Expect RX J1 Byte
TX J2 Byte
Expect RX J2 Byte
TX Frame Format
DOUBLE_FRAME
RX Frame Format
DOUBLE_FRAME
The procedures for configuring the GEIUA and GOIUA are the same. The following procedure
describes how to add a pair of GOIUAs (in active/standby mode) in the GMPS.
68P02909W07-A
4-39
Aug 2008
Procedure
Procedure 4-13
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
Figure 4-29
Set FuncType to A interface board, and set Board Type to GOIUA. Set the parameters
by referring to Table 4-15.
Right-click GOIUA.
Continued
4-40
68P02909W07-A
Aug 2008
Procedure 4-13
7
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-30.
Figure 4-30
Continued
68P02909W07-A
4-41
Aug 2008
Procedure 4-13
8
Set Load Key, and then click Next. A dialog box is displayed, as shown in Figure 4-31.
Figure 4-31
Continued
4-42
68P02909W07-A
Aug 2008
Procedure 4-13
Set the attributes of the sub-board of the GOIUA by referring to Table 4-15.
10
Figure 4-32
NOTE
TX Frame Format and RX Frame Format should be negotiated with the peer.
For other parameters, use the default settings. By default, J2 Byte Alarm Report
Switch is set to Close. Modify it according to actual requirements. The BSC
recognizes only the J2 byte alarms of the SDH suggested format. If J2 Byte Alarm
Report Switch is set to Open, Motorola recommends that the peer expected RX
J2 byte be set to the SDH suggested format.
11
Set the attributes of the port on the GOIUA by referring to Table 4-15.
Continued
68P02909W07-A
4-43
Aug 2008
Procedure 4-13
12
Figure 4-33
NOTE
Protect mode, Switch mode, and Recover mode should be negotiated with the
peer. For other parameters, use the default settings.
13
Mandatory/Optional
Mandatory
Prerequisites
The subrack has empty slots to hold the GEIUB/GOIUB.
4-44
68P02909W07-A
Aug 2008
Preparation
Table 4-17
Parameter
Example
Source
Board Type
GEIUB
Work Mode
E1
Active/Standby Mode
Selected
Load Key
Server
Table 4-18
Example of the data negotiated and planned for configuring the GOIUB
Parameter
Example
Source
Board Type
GOIUB
Work Mode
E1
Active/Standby
Mode
Selected
Load Key
Server
Tributary
Numbering
HuaWei mode
TX J0 Byte
Expect RX J0 Byte
TX J1 Byte
Expect RX J1 Byte
TX J2 Byte
Expect RX J2 Byte
TX Frame Format
DOUBLE_FRAME
RX Frame Format
DOUBLE_FRAME
The procedures for configuring the GEIUB and GOIUB are the same. The following procedure
describes how to add a pair of GEIUBs (in active/standby mode) in the GMPS.
68P02909W07-A
4-45
Aug 2008
Procedure
Procedure 4-14
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
Figure 4-34
Set Board Type to GEIUB and set the parameters by referring to Table 4-17.
Right-click GEIUB.
Continued
4-46
68P02909W07-A
Aug 2008
Procedure 4-14
7
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-35.
Figure 4-35
Continued
68P02909W07-A
4-47
Aug 2008
Procedure 4-14
8
Set Load Key, and then click Next. A dialog box is displayed, as shown in Figure 4-36.
Figure 4-36
NOTE
When configuring the port attributes of the GEIUB, select a port number
first, and then configure the attributes of this port.
If you select Configure All, all the ports will be configured based on the
settings of the current port displayed in the Port No. drop-down list box.
For the parameters in the dialog box shown in Figure 4-36, use the default settings of the
parameters or modify them according to actual requirements.
10
Mandatory/Optional
4-48
68P02909W07-A
Aug 2008
Prerequisites
The subrack has empty slots to hold the GEPUG.
Preparation
Table 4-19
Example of the data negotiated and planned for configuring the GEPUG
Parameter
Example
Source
Subrack No.
Slot No.
14
FuncType
Gb interface board
Board Type
GEPUG
Work Mode
E1
Active/Standby Mode
Selected
Load Key
Server
Frame Format
CRC4_MULTIFRAME
The following procedure describes how to configure a pair of GEPUGs (in active/standby
mode) in the GMPS.
Procedure
Procedure 4-15
On the BSC Local Manager, click the BSC Device Panel tab. Select the cabinet where the
GMPS/GEPS is located from the Current Cabinet drop-down list.
68P02909W07-A
4-49
Aug 2008
Procedure 4-15
3
Figure 4-37
Set FuncType to Gb interface board, and set Board Type to GEPUG. Set the parameters
by referring to Table 4-19. Then click Finish. A pair of GEPUGs is added.
Right-click GEPUG.
Continued
4-50
68P02909W07-A
Aug 2008
Procedure 4-15
6
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-38.
Figure 4-38
Continued
68P02909W07-A
4-51
Aug 2008
Procedure 4-15
7
Set Load Key by referring to Table 4-19, and then click Next. A dialog box is displayed,
as shown in Figure 4-39.
Figure 4-39
Set Frame Format by referring to Table 4-19. For other parameters in the dialog box shown
in Figure 4-39, use the default settings or modify them according to actual requirements.
Mandatory/Optional
Prerequisites
The subrack has empty slots to hold the GFGUG.
4-52
68P02909W07-A
Aug 2008
Preparation
Table 4-20
Example of the data negotiated and planned for configuring the GFGUG
Parameter
Example
Source
Subrack No.
Slot No.
18
FuncType
Gb interface board
Board Type
GFGUG
Net Mode
Independent Mode
Port Type
FE
Load Key
Server
ACTIVE
Device IP
Logical IP Address
192.168.70.2
Subnet Mask
255.255.255.128
IP Address
192.168.70.132
Subnet Mask
255.255.255.128
Destination IP Address
192.168.80.0
Subnet Mask
255.255.255.128
Gateway
192.168.70.136
Port IP
BSC Router
Procedure
Adding a board.
a.
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet
number from the Current Cabinet drop-down list.
b.
c.
68P02909W07-A
4-53
Aug 2008
Figure 4-40
d.
Set FuncType to Gb interface board, and set Board Type to GFGUG. Set the
parameters by referring to Table 4-20.
e.
Right-click GFGUG.
b.
Choose Configure Board Attributes from the shortcut menu. A dialog box is
displayed, as shown in Figure 4-41.
4-54
68P02909W07-A
Aug 2008
Figure 4-41
c.
Set Load Key by referring to Table 4-20, and then click Next. A dialog box is
displayed, as shown in Figure 4-42.
Figure 4-42
68P02909W07-A
4-55
Aug 2008
d.
NOTE
When you modify the attribute of a port on the GFGUG, the port becomes
faulty temporarily. If the board is in active/standby mode, an active/standby
switchover is performed automatically.
e.
Figure 4-43
f.
Set the QoS attributes according to actual requirements, and then click Next. A
dialog box is displayed, as shown in Figure 4-44.
4-56
68P02909W07-A
Aug 2008
Figure 4-44
g.
h.
Right-click GFGUG and choose Configure Device IP from the shortcut menu. A
dialog box is displayed, as shown in Figure 4-45.
68P02909W07-A
4-57
Aug 2008
Figure 4-45
b.
Figure 4-46
4-58
68P02909W07-A
Aug 2008
c.
Set the parameters by referring to Table 4-20. Click OK to return to the dialog box
shown in Figure 4-45.
NOTE
Device IP address is the logical IP address for communication. This IP
address is valid for the IP addresses of all the ports of the board. The device
IP addresses for the interface boards operating in active/standby mode
are the same. The IP addresses for the interface boards not operating in
active/standby mode should not be arranged in the same network segment.
d.
Right-click GFGUG and choose Configure Ethernet Port IP from the shortcut menu.
A dialog box is displayed, as shown in Figure 4-47.
Figure 4-47
b.
68P02909W07-A
4-59
Aug 2008
Figure 4-48
c.
Set the parameters by referring to Table 4-20. Click OK to return to the dialog box
shown in Figure 4-47.
NOTE
If Port Type is set to FE, one board can be configured with eight port
IP addresses on different network segments. If Port Type is set to GE,
one board can be configured with two port IP addresses on different
network segments. The port IP address and the device IP address must
be configured on different network segments. The port IP addresses for
the active and standby GFGUGs must be configured on the same network
segment.
d.
Right-click GFGUG and choose Configure BSC Router from the shortcut menu. A
dialog box is displayed, as shown in Figure 4-49.
4-60
68P02909W07-A
Aug 2008
Figure 4-49
b.
Figure 4-50
68P02909W07-A
4-61
Aug 2008
c.
CAUTION
Destination IP Address must be set to the network address, and it cannot
be configured on the same network segment with the port IP address of
the GFGUG. Otherwise, Destination IP Address is invalid. Gateway IP
Address and the port IP address of the GFGUG must be configured on
the same network segment.
d.
e.
Mandatory/Optional
NOTE
One BSC cabinet can be configured with only one EAC.
Prerequisites
The subrack that holds the EAC is configured.
Preparation
None.
Procedure
Procedure 4-16
1
4-62
68P02909W07-A
Aug 2008
Procedure 4-16
2
Choose Configure BSC EAC from the shortcut menu. A dialog box is displayed, as shown
in Figure 4-51.
Figure 4-51
NOTE
Use the default settings of the parameters or modify them according to actual
requirements.
Continued
68P02909W07-A
4-63
Aug 2008
Procedure 4-16
3
Figure 4-52
NOTE
Use the default settings of the parameters or modify them according to actual
requirements.
4
Mandatory/Optional
Mandatory
4-64
68P02909W07-A
Aug 2008
NOTE
Prerequisites
The two subracks between which the communication link is to be established are configured.
Preparation
NOTE
Assume that the BSC is configured with one GMPS and two GEPSs. The GMPS is
subrack 0, and GEPSs are subracks 1 and 3.
Table 4-21 Example of the data negotiated and planned for configuring the
communication link between GMPS 0 and GEPS 1
Parameter
Example
Source
Subrack1 No.
Subrack2 No.
0 (active), 1 (standby)
0 (active), 1 (standby)
Table 4-22 Example of the data negotiated and planned for configuring the
communication link between GMPS 0 and GEPS 3
Parameter
Example
Source
Subrack1 No.
Subrack2 No.
2 (active), 3 (standby)
0 (active), 1 (standby)
68P02909W07-A
4-65
Aug 2008
Table 4-23 Example of the data negotiated and planned for configuring the
communication link between GEPS 1 and GEPS 3
Parameter
Example
Source
Subrack1 No.
Subrack2 No.
2 (active), 3 (standby)
2 (active), 3 (standby)
The following procedure describes how to configure the mesh interconnection between subracks
through TDM ports.
Procedure
b.
Choose Configure Subrack Communication Link from the shortcut menu. A dialog
box is displayed, as shown in Figure 4-53.
Figure 4-53
4-66
68P02909W07-A
Aug 2008
c.
Figure 4-54
d.
e.
Click OK. The first communication link between GMPS 0 and GEPS 1 is configured.
f.
Repeat Step a through Step e to configure the second communication link between
GMPS 0 and GEPS 1.
68P02909W07-A
4-67
Aug 2008
b.
Choose Configure Subrack Communication Link from the shortcut menu. A dialog
box is displayed, as shown in Figure 4-55.
Figure 4-55
4-68
68P02909W07-A
Aug 2008
c.
Figure 4-56
d.
e.
Click OK. The first communication link between GMPS 0 and GEPS 3 is configured.
f.
Repeat Step a through Step e to configure the second communication link between
GMPS 0 and GEPS 3.
68P02909W07-A
4-69
Aug 2008
b.
Choose Configure Subrack Communication Link from the shortcut menu. A dialog
box is displayed, as shown in Figure 4-57.
Figure 4-57
4-70
68P02909W07-A
Aug 2008
c.
Figure 4-58
d.
e.
Click OK. The first communication link between GEPS 1 and GEPS 3 is configured.
f.
Repeat Step a through Step e to configure the second communication link between
GEPS 1 and GEPS 3.
68P02909W07-A
4-71
Aug 2008
This section describes how to configure BSC links on the A Interface and the Gb interface
when the BM and TC are configured in the same subracks. These links are responsible for the
signaling transmission between the BSC and other NEs.
Mandatory/Optional
Mandatory
Prerequisites
The GEIUA/GOIUA in the GMPS/GEPS is configured. For details, refer to Configuring the
GEIUA/GOIUA on page 4-38.
Preparation
Table 4-24 Example of the data negotiated and planned for configuring an A
Interface E1/T1
Parameter
Example
Source
Subrack No.
Slot No.
18
Port No.
Start CIC
4-72
68P02909W07-A
Aug 2008
Procedure
Procedure 4-17
Choose Configure A Interface E1/T1 from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-59.
Figure 4-59
Continued
68P02909W07-A
4-73
Aug 2008
Procedure 4-17
3
Figure 4-60
On the A Interface E1/T1 Attributes tab page, set the parameters by referring to
Table 4-24.
NOTE
One CIC group contains 32 CICs. If multiple E1s/T1s have the same OSP and the
same DSP group, the start CIC for each E1/T1 must be unique. If the start CIC of
the first E1/T1 is 0, then the start CIC of the second E1/T1 and that of the first
E1/T1 must be in different groups, and the start CIC of the second E1/T1 must
be greater than 31. On the CIC Attributes tab page, use the default settings or
modify them according to actual requirements.
5
Repeat step 1 through step 6 to add more E1/T1 connections on the A interface.
4-74
68P02909W07-A
Aug 2008
Scenario
Mandatory/Optional
Mandatory
NOTE
For details about the configuration of the 2 Mbit/s signaling link, refer to Configuring
Prerequisites
The SS7 DSP is configured. For details, refer to Configuring the SS7 Signaling Points on
page 3-5.
The GMPS or the GEPS is configured with the GXPUM. For details, refer to Configuring
the GXPUM on page 3-24.
The following procedure describes how to configure a 64 kbit/s SS7 signaling link on the
GOIUA in the GMPS.
Preparation
Table 4-25
link
Example of the data negotiated and planned for adding an SS7 signaling
Parameter
Example
Source
Rate Type
64 kbit/s
A Subrack No.
A Slot No.
18
A Port No.
TS16
SLC
SLC Send
Procedure
Procedure 4-18
68P02909W07-A
4-75
Aug 2008
Procedure 4-18
2
Choose Configure SS7 Signaling Link from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-61.
Figure 4-61
Continued
4-76
68P02909W07-A
Aug 2008
Procedure 4-18
3
Figure 4-62
Continued
68P02909W07-A
4-77
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Procedure 4-18
On the MPT2 tab page, set the parameters by referring to Table 4-25.
Click the MTP3 tab, the tab page is displayed, as shown in Figure 4-63.
Figure 4-63
Chapter
4-78
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Mandatory/Optional
Mandatory
NOTE
When adding an NSE, set the NSE identifier, subnetwork protocol type, and
agent subrack number.
One BSC can be configured with a maximum of 128 NSEs. Multiple NSEs can be
assigned on the same agent subrack.
Prerequisites
None.
Preparation
Table 4-26 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over FR
Network planning
Network planning
68P02909W07-A
4-79
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Chapter
Procedure
Procedure 4-19
Choose Configure PCU Data>Configure NSE from the shortcut menu. A dialog box is
displayed, as shown in Figure 4-64.
Figure 4-64
Continued
4-80
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 4-19
3
Figure 4-65
Set the parameters by referring to Table 4-26. Click OK to return to the dialog box shown
in Figure 4-64.
Configuring the BC
This section describes how to configure the bearer channel (BC) on the Gb interface when the
Gb interface uses the FR transmission mode. The BC is responsible for the data transmission
between the BSC and the SGSN.
Scenario
Mandatory/Optional
NOTE
BC refers to a fixed number of timeslots on the E1/T1 when the Gb interface uses the
FR transmission mode.
68P02909W07-A
4-81
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Chapter
Prerequisites
The GEPUG is configured. For details, refer to Configuring the GEPUG (Gb over FR)
on page 3-55.
Preparation
Table 4-27 Example of the data negotiated and planned for configuring the BC on
the Gb interface
Parameter
Example
Source
Subrack No.
Slot No.
18
Port No.
Bearer Channel ID
Q933
Occupied Timeslot
T1-T16
10
Procedure
Procedure 4-20
Configuring the BC
4-82
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 4-20
2
Choose Configure BC from the shortcut menu. A dialog box is displayed, as shown in
Figure 4-66.
Figure 4-66
Continued
68P02909W07-A
4-83
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Procedure 4-20
3
Chapter
Figure 4-67
Mandatory/Optional
4-84
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
NOTE
The clock signal on the SGSN side is carried by the BC. Configure the SGSN clock by
specifying the port of the BC.
Prerequisites
The GEPUG is configured. For details, refer to Configuring the GEPUG (Gb over FR)
on page 3-55.
Preparation
Table 4-28
clock
Example of the data negotiated and planned for configuring the SGSN
Parameter
Example
Source
Procedure
Procedure 4-21
68P02909W07-A
4-85
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Procedure 4-21
2
Chapter
Choose Config SGSN Clock from the shortcut menu. A dialog box is displayed, as shown
in Figure 4-68.
Figure 4-68
Mandatory/Optional
4-86
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
NOTE
NSVC refers to the virtual connection on the NS layer. One NSVC is located on
the BC of one E1/T1 and belongs to one BC/NSE. One BC/NSE can be configured
with multiple NSVCs.
One NSVC corresponds to one PVC. When configuring an NSVC, specify the
corresponding PVC.
Prerequisites
The GEPUG is configured. For details, refer to Configuring the GEPUG (Gb over FR)
on page 3-55.
The NSE is configured. For details, refer to Configuring the NSE on page 3-101.
The BC is configured.
Preparation
Table 4-29 Example of the data negotiated and planned for configuring the NSVC
on the Gb interface
Parameter
Example
Source
NSVC Identifier
NSE Identifier
Subrack No.
Slot No.
18
Port Number
Bearer Channel ID
16
Procedure
Procedure 4-22
68P02909W07-A
4-87
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Procedure 4-22
2
Chapter
Choose Configure NSVC from the shortcut menu. A dialog box is displayed, as shown
in Figure 4-69.
Figure 4-69
Continued
4-88
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 4-22
3
Figure 4-70
Mandatory/Optional
Mandatory
NOTE
One GPRS cell can be configured with only one PTPBVC. One NSE can be configured
with multiple PTPBVCs.
68P02909W07-A
4-89
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Chapter
Prerequisites
The NSE is configured. For details, refer to Configuring the NSE on page 3-101.
A GPRS cell is configured and the activity state of the cell is Activated.
Preparation
Table 4-30 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
Cell Name
Cell 1
Procedure
Procedure 4-23
4-90
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 4-23
2
Choose Configure PCU Data>Configure PTPBVC from the shortcut menu. A dialog
box is displayed, as shown in Figure 4-71.
Figure 4-71
Continued
68P02909W07-A
4-91
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Procedure 4-23
3
Chapter
Figure 4-72
4-92
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Mandatory/Optional
Mandatory
NOTE
When adding an NSE, set the NSE identifier, subnetwork protocol type, and
agent subrack number.
One BSC can be configured with a maximum of 128 NSEs. Multiple NSEs can
be assigned on the same agent subrack.
Prerequisites
None.
Preparation
Table 4-31 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over IP
Network planning
Network planning
Procedure
Procedure 4-24
68P02909W07-A
4-93
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Procedure 4-24
2
Chapter
Choose Configure PCU Data>Configure NSE from the shortcut menu. A dialog box is
displayed, as shown in Figure 4-73.
Figure 4-73
Continued
4-94
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Procedure 4-24
3
Figure 4-74
Mandatory/Optional
Prerequisites
The GFGUG is configured. For details, refer to Configuring the GFGUG (Gb over IP) on
page 3-59.
68P02909W07-A
4-95
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Chapter
Preparation
Table 4-32 Example of the data negotiated and planned for configuring the local
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.70.1
18
100
100
Procedure
Procedure 4-25
4-96
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Procedure 4-25
2
Choose Configure Local NSVL from the shortcut menu. A dialog box is displayed, as
shown in Figure 4-75.
Figure 4-75
Continued
68P02909W07-A
4-97
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Procedure 4-25
3
Chapter
Figure 4-76
Mandatory/Optional
Prerequisites
The GFGUG is configured. For details, refer to Configuring the GFGUG (Gb over IP) on
page 3-59.
4-98
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Preparation
Table 4-33 Example of the data negotiated and planned for configuring the remote
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.80.1
IP Port No.
100
100
Procedure
Procedure 4-26
Choose Configure PCU Data>Configure Remote NSVL from the shortcut menu. A dialog
box is displayed, as shown in Figure 4-77.
Figure 4-77
Continued
68P02909W07-A
4-99
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Procedure 4-26
3
Chapter
Figure 4-78
Mandatory/Optional
Mandatory
NOTE
One GPRS cell can be configured with only one PTPBVC. One NSE can be configured
with multiple PTPBVCs.
4-100
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Prerequisites
The NSE is configured. For details, refer to Configuring the NSE on page 3-115.
A GPRS cell is configured and the activity state of the cell is Activated.
Preparation
Table 4-34 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
Cell Name
Cell 1
Procedure
Procedure 4-27
68P02909W07-A
4-101
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
4: Configuring the BSC (BM/TC Combined)
Procedure 4-27
2
Chapter
Choose Configure PCU Data>Configure PTPBVC from the shortcut menu. A dialog
box is displayed, as shown in Figure 4-79.
Figure 4-79
Continued
4-102
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Procedure 4-27
3
Figure 4-80
68P02909W07-A
4-103
Aug 2008
This section describes how to configure BSC clock signals when the BM and TC are configured
in the same subracks. The BSC clock signals are responsible for the synchronization of boards
in each subrack.
Mandatory/Optional
Mandatory
NOTE
If the GEIUA is configured in the GMPS, two line clock signals, line 0 and line 1, can
be configured. If the GOIUA is configured in the GMPS, only one line clock signal can
be configured and the line clock signal must be configured on port 0 on the GOIUA.
Prerequisites
If the line clock is to be configured on the GEIUA, an A Interface E1/T1 must be configured.
For changes in the document, refer to Adding an A Interface E1/T1 on page 3-94.
4-104
68P02909W07-A
Aug 2008
Preparation
Table 4-35 Example of the data negotiated and planned for configuring the clock
on line 0 for the GMPS
Parameter
Example
Source
Line No.
LINE0
8K
18
Table 4-36 Example of the data negotiated and planned for configuring the clock
on line 1 for the GMPS
Parameter
Example
Source
Line No.
LINE1
8K
18
The following procedure describes how to configure two line clock signals on the GEIUA in
the GMPS.
Procedure
Procedure 4-28
1
68P02909W07-A
4-105
Aug 2008
Procedure 4-28
2
Choose Configure Line Clock from the shortcut menu. A dialog box is displayed, as shown
in Figure 4-81.
Figure 4-81
NOTE
When the A Interface E1 where the port of the selected Board Port No. is located
incurs a fault, the GMPS cannot extract the line clock from the A Interface. In
this case, the GMPS can extract the line clock from the A Interface through the A
Interface E1 where the port of the selected Backup Port No. is located.
Board Slot No.: Number of the slot where the GEIUA/GOIUA configured
with the A Interface E1 is located.
4-106
68P02909W07-A
Aug 2008
Procedure 4-28
6
Select LINE1 and set the parameters by referring to Table 4-36, as shown in Figure 4-82.
Figure 4-82
Mandatory/Optional
Mandatory
NOTE
The clock for the GGCU can be the 2M external clock or the line clock extracted from
the MSC through the A Interface board. The GGCU processes the input clock and
generates the 8 kHz clock, which is used as the transmission synchronization clock
and the time synchronization clock for the boards in the GMPS or GEPS.
The system clock has four priorities: priority 1 to priority 4, from the highest
to the lowest.
When the BITS clock is provided, it should be configured as the system clock
and enjoys the highest priority.
68P02909W07-A
4-107
Aug 2008
Prerequisites
The GGCU in the GMPS is configured. For details, refer to Configuring the GGCU on
page 3-33.
The BITS clock is ready, or the line clock for the GMPS is configured.
Preparation
Table 4-37
clock
Example of the data negotiated and planned for configuring the system
Parameter
Example
Source
Priority
2M external clock 0
LINE0
LINE1
2 MHz
8 kHz
8 kHz
Source Type
Source Sub-type
Procedure
Procedure 4-29
1
4-108
68P02909W07-A
Aug 2008
Procedure 4-29
2
Choose Configure System Clock from the shortcut menu. A dialog box is displayed, as
shown in Figure 4-83.
Figure 4-83
CAUTION
Source Type and Work Mode cannot be configured in one operation. Configure
them separately. After configuring Source Type, exit the configuration wizard,
and then start the configuration wizard again to configure Work Mode.
3
Mandatory/Optional
Mandatory
68P02909W07-A
4-109
Aug 2008
Prerequisites
The GSCU in the GMPS is configured. For details, refer to Configuring the GSCU on
page 3-31.
The GGCU in the GMPS is configured. For details, refer to Configuring the GGCU on
page 3-33.
Preparation
Table 4-38 Example of data negotiated and planned for configuring the 8K reference
clock for the GMPS
Parameter
Example
Source
GGCU Backplane
Procedure
Procedure 4-30
1
4-110
68P02909W07-A
Aug 2008
Procedure 4-30
2
Choose Configure 8K Reference Clock from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-84.
Figure 4-84
Mandatory/Optional
Mandatory
68P02909W07-A
4-111
Aug 2008
Prerequisites
The GSCU in the GEPS is configured. For details, refer to Configuring the GSCU on page
3-31.
The GGCU in the GMPS is configured. For details, refer to Configuring the GGCU on
page 3-33.
Preparation
Table 4-39 Example of the data negotiated and planned for configuring the 8K
reference clock for the GEPS
Parameter
Example
Source
GGCU Panel
Procedure
Procedure 4-31
1
4-112
68P02909W07-A
Aug 2008
Procedure 4-31
2
Choose Configure 8K Reference Clock from the shortcut menu. A dialog box is displayed,
as shown in Figure 4-85.
Figure 4-85
Repeat step 1 through step 4 to configure the 8K reference clock for more GEPSs.
68P02909W07-A
Aug 2008
4-113
4-114
68P02909W07-A
Aug 2008
Chapter
5
Configuring the BSC (IP Transmission Mode
on the A Interface)
68P02909W07-A
Aug 2008
5-1
Chapter 5:
This section describes how to configure the BSC global data, devices, links, and clock on the
BSC Local Manager when the A Interface uses the IP transmission mode.
5-2
68P02909W07-A
Aug 2008
Configuring the BSC Global Data (IP Transmission Mode on the A Interface)
When the A Interface uses the IP transmission mode, the BSC global data includes BSC
attributes, M3UA data, and subrack-OSP mapping.
Basic Data
BSC Timer
Software Parameters
SCCP
IP Transfers
Scenario
Mandatory/Optional
Mandatory
Prerequisites
The BSC attributes have been determined in network planning.
68P02909W07-A
5-3
Aug 2008
Preparation
Table 5-1 Example of the data negotiated and planned for configuring BSC attributes
(BM/TC combined)
Parameter
Example
Source
BSC Name
BSC001
Network planning
Country Code
86
Network planning
City Code
021
Network planning
MCC
460
Network planning
MNC
10
Network planning
A Interface Tag
GSM_PHASE_2+
Network planning
Um Interface Tag
GSM_PHASE_2+
Network planning
GSM_PHASE_2+
Network planning
NTP Server
10.161.72.251
IP on A Interface
Network planning
Procedure
Procedure 5-1
1
5-4
68P02909W07-A
Aug 2008
Procedure 5-1
2
Choose Configure BSC Attributes from the shortcut menu. A dialog box is displayed, as
shown in Figure 5-1.
Figure 5-1
On the Basic Data tab page, set the parameters by referring to Table 5-1.
NOTE
The parameters not listed in Table 5-1 are optional. Use the default settings or
modify them according to actual requirements.
4
Mandatory/Optional
Mandatory
68P02909W07-A
5-5
Aug 2008
CAUTION
The local entity must be configured before the destination entity is configured.
The local entity and destination entity must be configured before the signaling
transfer entity is configured.
Prerequisites
None.
Preparation
Table 5-2
entities
Example of the data negotiated and planned for configuring the M3AU
Parameter
Example
Source
BSC001
OPC (Hex)
B1
Network planning
Route Context
4294967295
Encoding Scheme
14
Network planning
Network Indicator
NATB
Network planning
Entity Name
MSC001
DSP (Hex)
D1
Network planning
Using STP
Yes
Network planning
Protocol
RFC3332
5-6
68P02909W07-A
Aug 2008
Table 5-3 Example of the data negotiated and planned for configuring the signaling
transfer entity
Parameter
Example
Source
STE Name
MGW001
STP (Hex)
C1
Network planning
Protocol
RFC3332
Network planning
Procedure
b.
Choose Configure M3UA Data>Configure M3UA Entity from the shortcut menu.
A dialog box is displayed, as shown in Figure 5-2.
Figure 5-2
c.
On the M3UA LE tab page, click Add. A dialog box is displayed, as shown in
Figure 5-3.
68P02909W07-A
5-7
Aug 2008
Figure 5-3
NOTE
If a local entity exists, Local Entity Name, Encoding Scheme, and
Network Indicator of the local entity are displayed by default in the
dialog box shown in Figure 5-3.
d.
e.
In the dialog box shown in Figure 5-2, click the M3UA DE tab to display the tab
page, as shown in Figure 5-4.
5-8
68P02909W07-A
Aug 2008
Figure 5-4
b.
Figure 5-5
68P02909W07-A
5-9
Aug 2008
NOTE
If there is no direct physical link between the local entity and the
destination entity, configure a signaling transfer entity. In the dialog box
shown in Figure 5-5, set Using STP to Yes. Route Context is mapped
to a destination entity/signaling transfer entity. Except the invalid value
4294967295, the Route Context of a destination entity/signaling transfer
entity must be unique. Otherwise, the configuration is invalid.
c.
d.
Check whether there is a direct physical link between the local entity and the destination
entity.
Then...
If...
There is a direct physical link between the local
entity and the destination entity
In the dialog box shown in Figure 5-2, click the M3UA STE tab to display the tab
page, as shown in Figure 5-6.
5-10
68P02909W07-A
Aug 2008
Figure 5-6
b.
Figure 5-7
68P02909W07-A
5-11
Aug 2008
c.
d.
Mandatory/Optional
Mandatory
NOTE
The GMPS is displayed by default on the LMT. Configure only its OSP on the LMT. For
the GEPS, configure it and its OSP on the LMT.
Prerequisites
The M3UA local entity is configured.
Preparation
Table 5-4 Example of the data negotiated and planned for configuring the
subrack-OSP mapping
Parameter
Example
Source
Subrack No.
OSP
B1
Network planning
Procedure
Procedure 5-2
1
5-12
68P02909W07-A
Aug 2008
Procedure 5-2
2
Choose Configure Subrack-OPC Mapping from the shortcut menu. A dialog box is
displayed, as shown in Figure 5-8.
Figure 5-8
68P02909W07-A
5-13
Aug 2008
Chapter 5:
This section describes how to configure the BSC devices on the LMT when the A Interface uses
the IP transmission mode.
Mandatory/Optional
NOTE
The GBCR cabinet is displayed by default on the LMT. Configure the GBSR cabinet
on the LMT. Zero or one GBSR cabinet can be configured on the basis of the actual
traffic volume.
Prerequisites
None.
Preparation
Table 5-5
Example of the data negotiated and planned for configuring a GBSR cabinet
Parameter
Example
Source
Cabinet No.
Cabinet Type
Local Cabinet
5-14
68P02909W07-A
Aug 2008
Adding a GEPS
Procedure
Procedure 5-3
Choose Add BSC Cabinet from the shortcut menu. A dialog box is displayed, as shown
in Figure 5-9.
Figure 5-9
Adding a GEPS
This section describes how to add a GEPS and configure its attributes on the LMT.
Scenario
Mandatory/Optional
68P02909W07-A
5-15
Aug 2008
Adding a GEPS
NOTE
The GEPS processes the basic services of the BSC. The settings of the GEPS depend
on the traffic volume of the BSC. When the A Interface uses the IP transmission mode,
the BSC can be configured with up to two GEPSs to form the 1 GMPS + 2 GEPSs
combination. This combination can hold up to 2048 TRXs. A fan box is automatically
added when you add a subrack. Configure only the attributes of the fan box.
Prerequisites
The BSC is configured with the M3UA entities. For details, refer to Configuring the M3UA
Entities on page 5-5.
Preparation
Table 5-6
Parameter
Example
Source
Subrack Type
GEPS
OPC
B1
Network planning
Procedure
Procedure 5-4
Adding a GEPS
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
5-16
68P02909W07-A
Aug 2008
Procedure 5-4
3
Adding a GEPS
Figure 5-10
68P02909W07-A
5-17
Aug 2008
Procedure 5-4
7
Choose Configure Fan Box Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-11.
Figure 5-11
For the parameters in the dialog box shown in Figure 5-11, use the default settings or modify
them according to actual requirements.
10
Postrequisites
Before deleting the GEPSs that are initially configured, ensure that they are powered off.
Mandatory/Optional
Mandatory
5-18
68P02909W07-A
Aug 2008
NOTE
Any subrack in the cabinet can be configured as the management subrack for the
power distribution box.
Prerequisites
The subrack that manages the power distribution box is configured.
Preparation
Table 5-7 Example of the data negotiated and planned for configuring a power
distribution box
Parameter
Example
Source
Cabinet No.
Procedure
Procedure 5-5
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
68P02909W07-A
5-19
Aug 2008
Procedure 5-5
3
Choose Add Power Distribution Box. A dialog box is displayed, as shown in Figure 5-12.
Figure 5-12
5-20
68P02909W07-A
Aug 2008
Procedure 5-5
7
Choose Configure Power Distribution Box Attributes from the shortcut menu. A dialog
box is displayed, as shown in Figure 5-13.
Figure 5-13
For the parameters in the dialog box shown in Figure 5-13, use the default settings or modify
them according to actual requirements.
10
Repeat step 1 through step 9 to configure power distribution boxes for more subracks.
68P02909W07-A
5-21
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
None.
NOTE
When the GXPUM is configured in the GMPS, parameters such as Load Key and Port
Attributes can be configured. When the GXPUM is configured in the GEPS, only
Load Key can be configured.
Preparation
Table 5-8
Example of the data negotiated and planned for configuring the GXPUM
Parameter
Example
Source
Load Key
Server
Selected
5-22
68P02909W07-A
Aug 2008
Procedure
Procedure 5-6
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet where the
GMPS is located from the Current Cabinet drop-down list.
Figure 5-14
Right-click GXPUM.
Continued
68P02909W07-A
5-23
Aug 2008
Procedure 5-6
7
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-15.
Figure 5-15
Continued
5-24
68P02909W07-A
Aug 2008
Procedure 5-6
Figure 5-16
Continued
68P02909W07-A
5-25
Aug 2008
Procedure 5-6
10
11
Figure 5-17
12
13
Mandatory/Optional
5-26
68P02909W07-A
Aug 2008
Prerequisites
None.
Preparation
Table 5-9
Example of the data negotiated and planned for configuring the GXPUT
Parameter
Example
Source
Board Type
GXPUT
Active/Standby Mode
Selected
Load Key
Server
Procedure
Procedure 5-7
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet where the
GMPS is located from the Current Cabinet drop-down list.
Continued
68P02909W07-A
5-27
Aug 2008
Procedure 5-7
Figure 5-18
Right-click a GXPUT.
Continued
5-28
68P02909W07-A
Aug 2008
Procedure 5-7
7
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-19.
Figure 5-19
Mandatory/Optional
Mandatory
Prerequisites
None.
68P02909W07-A
5-29
Aug 2008
Preparation
Table 5-10
Example of the data negotiated and planned for configuring the GSCU
Parameter
Example
Source
Load Key
Server
Procedure
Procedure 5-8
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-20.
Figure 5-20
5-30
68P02909W07-A
Aug 2008
Procedure 5-8
4
Figure 5-21
NOTE
Among the 12 ports on the GSCU, the alarm reporting function of all the
ports, except for ports 0, 1, 10, and 11, are disabled by default on the LMT.
Enable the alarm reporting function of the port connected to the Ethernet
cable to monitor whether the port is normal.
Mandatory/Optional
Mandatory
Prerequisites
None.
68P02909W07-A
5-31
Aug 2008
Preparation
Table 5-11
Example of the data negotiated and planned for configuring the GTNU
Parameter
Example
Source
Load Key
Server
Procedure
Procedure 5-9
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-22.
Figure 5-22
5-32
68P02909W07-A
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
None.
Preparation
Table 5-12
Example of the data negotiated and planned for configuring the GGCU
Parameter
Example
Source
Load Key
Server
Procedure
Procedure 5-10
68P02909W07-A
5-33
Aug 2008
Procedure 5-10
2
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-23.
Figure 5-23
Mandatory/Optional
Mandatory
Prerequisites
The GMPS/GEPS has empty slots to hold the GDPUX.
5-34
68P02909W07-A
Aug 2008
Preparation
Table 5-13
Example of the data negotiated and planned for configuring the GDPUX
Parameter
Example
Source
FuncType
Other board
Board Type
GDPUX
Load Key
Server
The following procedure describes how to configure the GDPUX in the GMPS.
Procedure
Procedure 5-11
68P02909W07-A
5-35
Aug 2008
Procedure 5-11
3
Figure 5-24
Set FuncType to Other board, and set Board Type to GDPUX. Then click Finish. A
GDPUX is added.
Right-click GDPUX.
Continued
5-36
68P02909W07-A
Aug 2008
Procedure 5-11
6
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-25.
Figure 5-25
Continued
68P02909W07-A
5-37
Aug 2008
Procedure 5-11
Figure 5-26
NOTE
When configuring the DSP TC attributes, select a DSP TC number first, and
then configure the attributes of this DSP TC.
If you select Configure All, all the DSP TCs will be configured based on the
settings of the current DSP TC displayed in the DSP TC No. drop-down
list box.
Modify the parameters in the dialog box shown in Figure 5-26 according to actual
requirements.
10
5-38
68P02909W07-A
Aug 2008
Mandatory/Optional
Mandatory
Prerequisites
The GMPS/GEPS has empty slots to hold the GDPUP.
Preparation
Table 5-14
Example of the data negotiated and planned for configuring the GDPUP
Parameter
Example
Source
Subrack No.
Slot No.
Board Type
GDPUP
Load Key
Server
Procedure
Procedure 5-12
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
68P02909W07-A
5-39
Aug 2008
Procedure 5-12
3
Figure 5-27
Set FuncType to Other board, and set Board Type to GDPUP. Then click Finish. A
GDPUP is added.
Right-click GDPUP.
Continued
5-40
68P02909W07-A
Aug 2008
Procedure 5-12
6
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-28.
Figure 5-28
Mandatory/Optional
Mandatory
Prerequisites
The GMPS/GEPS has empty slots to hold the GFGUA/GOGUA.
68P02909W07-A
5-41
Aug 2008
Preparation
Table 5-15
Example of the data negotiated and planned for configuring the GFGUA
Parameter
Example
Source
Subrack No.
Slot No.
19
Board Type
GFGUA
Net Mode
Independent Mode
Port Type
FE
Load Key
Server
ACTIVE
Logical IP Address
192.168.10.2
Subnet Mask
255.255.255.128
IP Address
192.168.10.131
Subnet Mask
255.255.255.128
Destination IP Address
192.168.30.0
Subnet Mask
255.255.255.128
Gateway
192.168.10.136
Device IP
Port IP
BSC Router
The procedures for configuring the GFGUA and GOGUA are the same. The following procedure
describes how to configure a GFGUA in the GMPS.
Procedure
Adding a board.
a.
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet
number from the Current Cabinet drop-down list.
b.
c.
Choose Add Board from the shortcut menu. A dialog box is displayed, as shown in
Figure 5-29.
5-42
68P02909W07-A
Aug 2008
Figure 5-29
d.
Set FuncType to A interface board, and set Board Type to GFGUA. Set the
parameters by referring to Table 5-15.
e.
Right-click GFGUA.
b.
Choose Configure Board Attributes from the shortcut menu. A dialog box is
displayed, as shown in Figure 5-30.
68P02909W07-A
5-43
Aug 2008
Figure 5-30
c.
Set Load Key, and then click Next. A dialog box is displayed, as shown in Figure 5-31.
Figure 5-31
d.
5-44
68P02909W07-A
Aug 2008
NOTE
When you modify the attribute of a port on the GFGUA, the port becomes
faulty temporarily. If the board is in active/standby mode, an active/standby
switchover is performed automatically.
e.
Figure 5-32
f.
Set the QoS attributes according to actual requirements, and then click Next. A
dialog box is displayed, as shown in Figure 5-33.
68P02909W07-A
5-45
Aug 2008
Figure 5-33
g.
h.
Right-click GFGUA and choose Configure Device IP from the shortcut menu. A
dialog box is displayed, as shown in Figure 5-34.
5-46
68P02909W07-A
Aug 2008
Figure 5-34
b.
Figure 5-35
68P02909W07-A
5-47
Aug 2008
c.
Set the parameters by referring to Table 5-15. Click OK to return to the dialog box
shown in Figure 5-34.
NOTE
Device IP address is the logical IP address for communication. This IP
address is valid for the IP addresses of all the ports of the board. The device
IP addresses for the interface boards operating in active/standby mode
are the same. The IP addresses for the interface boards not operating in
active/standby mode should not be arranged in the same network segment.
d.
Right-click GFGUA and choose Configure Ethernet Port IP from the shortcut menu.
A dialog box is displayed, as shown in Figure 5-36.
Figure 5-36
b.
5-48
68P02909W07-A
Aug 2008
Figure 5-37
c.
Set the parameters by referring to Table 5-15. Click OK to return to the dialog box
shown in Figure 5-36.
NOTE
If Port Type is set to FE, one board can be configured with eight port
IP addresses on different network segments. If Port Type is set to GE,
one board can be configured with two port IP addresses on different
network segments. The port IP address and the device IP address must
be configured on different network segments. The port IP addresses for
the active and standby GFGUAs must be configured on the same network
segment.
d.
Right-click GFGUA and choose Configure BSC Router from the shortcut menu. A
dialog box is displayed, as shown in Figure 5-38.
68P02909W07-A
5-49
Aug 2008
Figure 5-38
b.
Figure 5-39
5-50
68P02909W07-A
Aug 2008
c.
CAUTION
Destination IP Address must be set to the network address, and it cannot
be configured on the same network segment with the port IP address of
the GFGUA. Otherwise, Destination IP Address is invalid. Gateway IP
Address and the port IP address of the GFGUA must be configured on
the same network segment.
d.
e.
Mandatory/Optional
Mandatory
Prerequisites
The subrack has empty slots to hold the GEIUB/GOIUB.
Preparation
Table 5-16
Parameter
Example
Source
Board Type
GEIUB
Work Mode
E1
Active/Standby Mode
Selected
Load Key
Server
Table 5-17
Example of the data negotiated and planned for configuring the GOIUB
Parameter
Example
Source
Board Type
GOIUB
Work Mode
E1
Active/Standby Mode
Selected
Continued
68P02909W07-A
5-51
Aug 2008
Table 5-17
(Continued)
Example of the data negotiated and planned for configuring the GOIUB
Parameter
Example
Source
Load Key
Server
Tributary Numbering
HuaWei mode
TX J0 Byte
Expect RX J0 Byte
TX J1 Byte
Expect RX J1 Byte
TX J2 Byte
Expect RX J2 Byte
TX Frame Format
DOUBLE_FRAME
RX Frame Format
DOUBLE_FRAME
The procedures for configuring the GEIUB and GOIUB are the same. The following procedure
describes how to add a pair of GEIUBs (in active/standby mode) in the GMPS.
Procedure
Procedure 5-13
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet number
from the Current Cabinet drop-down list.
Continued
5-52
68P02909W07-A
Aug 2008
Procedure 5-13
Figure 5-40
Set Board Type to GEIUB and set the parameters by referring to Table 5-16.
Right-click GEIUB.
Continued
68P02909W07-A
5-53
Aug 2008
Procedure 5-13
7
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-41.
Figure 5-41
Continued
5-54
68P02909W07-A
Aug 2008
Procedure 5-13
8
Set Load Key, and then click Next. A dialog box is displayed, as shown in Figure 5-42.
Figure 5-42
NOTE
When configuring the port attributes of the GEIUB, select a port number
first, and then configure the attributes of this port.
If you select Configure All, all the ports will be configured based on the
settings of the current port displayed in the Port No. drop-down list box.
For the parameters in the dialog box shown in Figure 5-42, use the default settings of the
parameters or modify them according to actual requirements.
10
Mandatory/Optional
68P02909W07-A
5-55
Aug 2008
Prerequisites
The subrack has empty slots to hold the GEPUG.
Preparation
Table 5-18
Example of the data negotiated and planned for configuring the GEPUG
Parameter
Example
Source
Subrack No.
Slot No.
14
FuncType
Gb interface board
Board Type
GEPUG
Work Mode
E1
Active/Standby Mode
Selected
Load Key
Server
Frame Format
CRC4_MULTIFRAME
The following procedure describes how to configure a pair of GEPUGs (in active/standby
mode) in the GMPS.
Procedure
Procedure 5-14
On the BSC Local Manager, click the BSC Device Panel tab. Select the cabinet where the
GMPS/GEPS is located from the Current Cabinet drop-down list.
5-56
68P02909W07-A
Aug 2008
Procedure 5-14
3
Figure 5-43
Set FuncType to Gb interface board, and set Board Type to GEPUG. Set the parameters
by referring to Table 5-18. Then click Finish. A pair of GEPUGs is added.
Right-click GEPUG.
Continued
68P02909W07-A
5-57
Aug 2008
Procedure 5-14
6
Choose Configure Board Attributes from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-44.
Figure 5-44
Continued
5-58
68P02909W07-A
Aug 2008
Procedure 5-14
7
Set Load Key by referring to Table 5-18, and then click Next. A dialog box is displayed,
as shown in Figure 5-45.
Figure 5-45
Set Frame Format by referring to Table 5-18. For other parameters in the dialog box shown
in Figure 5-45, use the default settings or modify them according to actual requirements.
Mandatory/Optional
Prerequisites
The subrack has empty slots to hold the GFGUG.
68P02909W07-A
5-59
Aug 2008
Preparation
Table 5-19
Example of the data negotiated and planned for configuring the GFGUG
Parameter
Example
Source
Subrack No.
Slot No.
18
FuncType
Gb interface board
Board Type
GFGUG
Net Mode
Independent Mode
Port Type
FE
Load Key
Server
ACTIVE
Device IP
Logical IP Address
192.168.70.2
Subnet Mask
255.255.255.128
IP Address
192.168.70.132
Subnet Mask
255.255.255.128
Destination IP Address
192.168.80.0
Subnet Mask
255.255.255.128
Gateway
192.168.70.136
Port IP
BSC Router
Procedure
Adding a board.
a.
On the BSC Local Manager, click the BSC Device Panel tab. Select a cabinet
number from the Current Cabinet drop-down list.
b.
c.
5-60
68P02909W07-A
Aug 2008
Figure 5-46
d.
Set FuncType to Gb interface board, and set Board Type to GFGUG. Set the
parameters by referring to Table 5-19.
e.
Right-click GFGUG.
b.
Choose Configure Board Attributes from the shortcut menu. A dialog box is
displayed, as shown in Figure 5-47.
68P02909W07-A
5-61
Aug 2008
Figure 5-47
c.
Set Load Key by referring to Table 5-19, and then click Next. A dialog box is
displayed, as shown in Figure 5-48.
Figure 5-48
5-62
68P02909W07-A
Aug 2008
d.
NOTE
When you modify the attribute of a port on the GFGUG, the port becomes
faulty temporarily. If the board is in active/standby mode, an active/standby
switchover is performed automatically.
e.
Figure 5-49
f.
Set the QoS attributes according to actual requirements, and then click Next. A
dialog box is displayed, as shown in Figure 5-50.
68P02909W07-A
5-63
Aug 2008
Figure 5-50
g.
h.
Right-click GFGUG and choose Configure Device IP from the shortcut menu. A
dialog box is displayed, as shown in Figure 5-51.
5-64
68P02909W07-A
Aug 2008
Figure 5-51
b.
Figure 5-52
68P02909W07-A
5-65
Aug 2008
c.
Set the parameters by referring to Table 5-19. Click OK to return to the dialog box
shown in Figure 5-51.
NOTE
Device IP address is the logical IP address for communication. This IP
address is valid for the IP addresses of all the ports of the board. The device
IP addresses for the interface boards operating in active/standby mode
are the same. The IP addresses for the interface boards not operating in
active/standby mode should not be arranged in the same network segment.
d.
Right-click GFGUG and choose Configure Ethernet Port IP from the shortcut menu.
A dialog box is displayed, as shown in Figure 5-53.
Figure 5-53
b.
5-66
68P02909W07-A
Aug 2008
Figure 5-54
c.
Set the parameters by referring to Table 5-19. Click OK to return to the dialog box
shown in Figure 5-53.
NOTE
If Port Type is set to FE, one board can be configured with eight port
IP addresses on different network segments. If Port Type is set to GE,
one board can be configured with two port IP addresses on different
network segments. The port IP address and the device IP address must
be configured on different network segments. The port IP addresses for
the active and standby GFGUGs must be configured on the same network
segment.
d.
Right-click GFGUG and choose Configure BSC Router from the shortcut menu. A
dialog box is displayed, as shown in Figure 5-55.
68P02909W07-A
5-67
Aug 2008
Figure 5-55
b.
Figure 5-56
5-68
68P02909W07-A
Aug 2008
c.
CAUTION
Destination IP Address must be set to the network address, and it cannot
be configured on the same network segment with the port IP address of
the GFGUG. Otherwise, Destination IP Address is invalid. Gateway IP
Address and the port IP address of the GFGUG must be configured on
the same network segment.
d.
e.
Mandatory/Optional
NOTE
One BSC cabinet can be configured with only one EAC.
Prerequisites
The subrack that holds the EAC is configured.
Preparation
None.
Procedure
Procedure 5-15
1
68P02909W07-A
5-69
Aug 2008
Procedure 5-15
2
Choose Configure BSC EAC from the shortcut menu. A dialog box is displayed, as shown
in Figure 5-57.
Figure 5-57
NOTE
Use the default settings of the parameters or modify them according to actual
requirements.
Continued
5-70
68P02909W07-A
Aug 2008
Procedure 5-15
3
Figure 5-58
NOTE
Use the default settings of the parameters or modify them according to actual
requirements.
4
Mandatory/Optional
Mandatory
68P02909W07-A
5-71
Aug 2008
NOTE
Prerequisites
The two subracks between which the communication link is to be established are configured.
Preparation
NOTE
Assume that the BSC is configured with one GMPS and two GEPSs. The GMPS is
subrack 0, and GEPSs are subracks 1 and 3.
Table 5-20 Example of the data negotiated and planned for configuring the
communication link between GMPS 0 and GEPS 1
Parameter
Example
Source
Subrack1 No.
Subrack2 No.
0 (active), 1 (standby)
0 (active), 1 (standby)
Table 5-21 Example of the data negotiated and planned for configuring the
communication link between GMPS 0 and GEPS 3
Parameter
Example
Source
Subrack1 No.
Subrack2 No.
2 (active), 3 (standby)
0 (active), 1 (standby)
5-72
68P02909W07-A
Aug 2008
Table 5-22 Example of the data negotiated and planned for configuring the
communication link between GEPS 1 and GEPS 3
Parameter
Example
Source
Subrack1 No.
Subrack2 No.
2 (active), 3 (standby)
2 (active), 3 (standby)
The following procedure describes how to configure the mesh interconnection between subracks
through TDM ports.
Procedure
b.
Choose Configure Subrack Communication Link from the shortcut menu. A dialog
box is displayed, as shown in Figure 5-59.
Figure 5-59
68P02909W07-A
5-73
Aug 2008
c.
Figure 5-60
d.
e.
Click OK. The first communication link between GMPS 0 and GEPS 1 is configured.
f.
Repeat Step a through Step e to configure the second communication link between
GMPS 0 and GEPS 1.
5-74
68P02909W07-A
Aug 2008
b.
Choose Configure Subrack Communication Link from the shortcut menu. A dialog
box is displayed, as shown in Figure 5-61.
Figure 5-61
68P02909W07-A
5-75
Aug 2008
c.
Figure 5-62
d.
e.
Click OK. The first communication link between GMPS 0 and GEPS 3 is configured.
f.
Repeat Step a through Step e to configure the second communication link between
GMPS 0 and GEPS 3.
5-76
68P02909W07-A
Aug 2008
b.
Choose Configure Subrack Communication Link from the shortcut menu. A dialog
box is displayed, as shown in Figure 5-63.
Figure 5-63
68P02909W07-A
5-77
Aug 2008
c.
Figure 5-64
d.
e.
Click OK. The first communication link between GEPS 1 and GEPS 3 is configured.
f.
Repeat Step a through Step e to configure the second communication link between
GEPS 1 and GEPS 3.
5-78
68P02909W07-A
Aug 2008
This section describes how to configure the M3UA links on the A Interface when the A Interface
uses the IP transmission mode. The M3UA links are responsible for the signaling transmission
between the BSC and the MSC.
Mandatory/Optional
Mandatory
Prerequisites
The M3UA entities are configured. For details, refer to Configuring the
M3UA Entities on page 5-5.
Preparation
Table 5-23
link set
Example of the data negotiated and planned for configuring the M3UA
Parameter
Example
Source
Linkset Name
MSC001
68P02909W07-A
5-79
Aug 2008
Procedure
Procedure 5-16
Choose Configure M3UA Data>Configure M3UA Linkset from the shortcut menu. A
dialog box is displayed, as shown in Figure 5-65.
Figure 5-65
Continued
5-80
68P02909W07-A
Aug 2008
Procedure 5-16
3
Figure 5-66
Mandatory/Optional
Mandatory
Prerequisites
The DSP for the M3UA entity is configured. For details, refer to Configuring the M3UA
Entities on page 5-5.
The subrack-OSP mapping is configured. For details, refer to Configuring the Subrack-OSP
Mapping on page 5-12.
The GMPS/GEPS is configured with the GXPUM. For details, refer to Configuring the
GXPUM on page 3-24.
68P02909W07-A
5-81
Aug 2008
The GMPS/GEPS is configured with the GFGUA/GOGUA. For details, refer to Configuring
the GFGUA/GOGUA on page 5-41.
Preparation
Table 5-24
Example of the data negotiated and planned for configuring the M3UA link
Parameter
Example
Source
Linkset Name
CPU No.
Local Address 1
192.168.10.2
Peer Address 1
192.168.30.1
Procedure
Procedure 5-17
5-82
68P02909W07-A
Aug 2008
Procedure 5-17
2
Choose Configure M3UA Link>Add M3UA Link from the shortcut menu. A dialog box is
displayed, as shown in Figure 5-67.
Figure 5-67
Continued
68P02909W07-A
5-83
Aug 2008
Procedure 5-17
3
Figure 5-68
Mandatory/Optional
Mandatory
Prerequisites
The DSP for the M3UA entity is configured. For details, refer to Configuring the M3UA
Entities on page 5-5.
5-84
68P02909W07-A
Aug 2008
Preparation
Table 5-25
route
Example of the data negotiated and planned for configuring the M3UA
Parameter
Example
Source
MSC001
Linkset Name
Procedure
Procedure 5-18
Choose Configure M3UA Data>Configure M3UA Route from the shortcut menu. A dialog
box is displayed, as shown in Figure 5-69.
Figure 5-69
Continued
68P02909W07-A
5-85
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-18
3
Chapter 5:
Figure 5-70
5-86
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Mandatory/Optional
Mandatory
NOTE
When adding an NSE, set the NSE identifier, subnetwork protocol type, and
agent subrack number.
One BSC can be configured with a maximum of 128 NSEs. Multiple NSEs can be
assigned on the same agent subrack.
Prerequisites
None.
Preparation
Table 5-26 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over FR
Network planning
Network planning
Procedure
Procedure 5-19
68P02909W07-A
5-87
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-19
2
Chapter 5:
Choose Configure PCU Data>Configure NSE from the shortcut menu. A dialog box is
displayed, as shown in Figure 5-71.
Figure 5-71
Continued
5-88
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 5-19
3
Figure 5-72
Set the parameters by referring to Table 5-26. Click OK to return to the dialog box shown
in Figure 5-71.
Configuring the BC
This section describes how to configure the bearer channel (BC) on the Gb interface when the
Gb interface uses the FR transmission mode. The BC is responsible for the data transmission
between the BSC and the SGSN.
Scenario
Mandatory/Optional
NOTE
BC refers to a fixed number of timeslots on the E1/T1 when the Gb interface uses the
FR transmission mode.
68P02909W07-A
5-89
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Chapter 5:
Prerequisites
The GEPUG is configured. For details, refer to Configuring the GEPUG (Gb over FR)
on page 3-55.
Preparation
Table 5-27 Example of the data negotiated and planned for configuring the BC on
the Gb interface
Parameter
Example
Source
Subrack No.
Slot No.
18
Port No.
Bearer Channel ID
Q933
Occupied Timeslot
T1-T16
10
Procedure
Procedure 5-20
Configuring the BC
5-90
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 5-20
2
Choose Configure BC from the shortcut menu. A dialog box is displayed, as shown in
Figure 5-73.
Figure 5-73
Continued
68P02909W07-A
5-91
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-20
3
Chapter 5:
Figure 5-74
Mandatory/Optional
5-92
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
NOTE
The BC carries the clock signal on the SGSN side. Configure the SGSN clock by
specifying the port of the BC.
Prerequisites
The GEPUG is configured. For details, refer to Configuring the GEPUG (Gb over FR)
on page 3-55.
Preparation
Table 5-28
clock
Example of the data negotiated and planned for configuring the SGSN
Parameter
Example
Source
Procedure
Procedure 5-21
68P02909W07-A
5-93
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-21
2
Chapter 5:
Choose Config SGSN Clock from the shortcut menu. A dialog box is displayed, as shown
in Figure 5-75.
Figure 5-75
Mandatory/Optional
5-94
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
NOTE
NSVC refers to the virtual connection on the NS layer. One NSVC is located on
the BC of one E1/T1 and belongs to one BC/NSE. One BC/NSE can be configured
with multiple NSVCs.
One NSVC corresponds to one PVC. When configuring an NSVC, specify the
corresponding PVC.
Prerequisites
The GEPUG is configured. For details, refer to Configuring the GEPUG (Gb over FR)
on page 3-55.
The NSE is configured. For details, refer to Configuring the NSE on page 3-101.
The BC is configured.
Preparation
Table 5-29 Example of the data negotiated and planned for configuring the NSVC
on the Gb interface
Parameter
Example
Source
NSVC Identifier
NSE Identifier
Subrack No.
Slot No.
18
Port Number
Bearer Channel ID
16
Procedure
Procedure 5-22
68P02909W07-A
5-95
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-22
2
Chapter 5:
Choose Configure NSVC from the shortcut menu. A dialog box is displayed, as shown
in Figure 5-76.
Figure 5-76
Continued
5-96
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 5-22
3
Figure 5-77
Mandatory/Optional
Mandatory
NOTE
One GPRS cell can be configured with only one PTPBVC. One NSE can be configured
with multiple PTPBVCs.
68P02909W07-A
5-97
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Chapter 5:
Prerequisites
The NSE is configured. For details, refer to Configuring the NSE on page 3-101.
A GPRS cell is configured and the activity state of the cell is Activated.
Preparation
Table 5-30 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
Cell Name
Cell 1
Procedure
Procedure 5-23
5-98
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (FR Transmission Mode on the Gb Interface)
Procedure 5-23
2
Choose Configure PCU Data>Configure PTPBVC from the shortcut menu. A dialog
box is displayed, as shown in Figure 5-78.
Figure 5-78
Continued
68P02909W07-A
5-99
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-23
3
Chapter 5:
Figure 5-79
5-100
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Mandatory/Optional
Mandatory
NOTE
When adding an NSE, set the NSE identifier, subnetwork protocol type, and
agent subrack number.
One BSC can be configured with a maximum of 128 NSEs. Multiple NSEs can
be assigned on the same agent subrack.
Prerequisites
None.
Preparation
Table 5-31 Example of the data negotiated and planned for configuring the NSE
on the Gb interface
Parameter
Example
Source
NSE Identifier
Gb over IP
Network planning
Network planning
Procedure
Procedure 5-24
68P02909W07-A
5-101
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-24
2
Chapter 5:
Choose Configure PCU Data>Configure NSE from the shortcut menu. A dialog box is
displayed, as shown in Figure 5-80.
Figure 5-80
Continued
5-102
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Procedure 5-24
3
Figure 5-81
Mandatory/Optional
Prerequisites
The GFGUG is configured. For details, refer to Configuring the GFGUG (Gb over IP) on
page 3-59.
68P02909W07-A
5-103
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Chapter 5:
Preparation
Table 5-32 Example of the data negotiated and planned for configuring the local
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.70.1
18
100
100
Procedure
Procedure 5-25
5-104
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Procedure 5-25
2
Choose Configure Local NSVL from the shortcut menu. A dialog box is displayed, as
shown in Figure 5-82.
Figure 5-82
Continued
68P02909W07-A
5-105
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-25
3
Chapter 5:
Figure 5-83
Mandatory/Optional
Prerequisites
The GFGUG is configured. For details, refer to Configuring the GFGUG (Gb over IP) on
page 3-59.
5-106
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Preparation
Table 5-33 Example of the data negotiated and planned for configuring the remote
NSVL on the Gb interface
Parameter
Example
Source
NSE Identifier
IP Address
192.168.80.1
IP Port No.
100
100
Procedure
Procedure 5-26
Choose Configure PCU Data>Configure Remote NSVL from the shortcut menu. A dialog
box is displayed, as shown in Figure 5-84.
Figure 5-84
Continued
68P02909W07-A
5-107
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-26
3
Chapter 5:
Figure 5-85
Mandatory/Optional
Mandatory
NOTE
One GPRS cell can be configured with only one PTPBVC. One NSE can be configured
with multiple PTPBVCs.
5-108
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Prerequisites
The NSE is configured. For details, refer to Configuring the NSE on page 3-115.
A GPRS cell is configured and the activity state of the cell is Activated.
Preparation
Table 5-34 Example of the data negotiated and planned for configuring the PTPBVC
on the Gb interface
Parameter
Example
Source
NSE Identifier
Cell Name
Cell 1
Procedure
Procedure 5-27
68P02909W07-A
5-109
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-27
2
Chapter 5:
Choose Configure PCU Data>Configure PTPBVC from the shortcut menu. A dialog
box is displayed, as shown in Figure 5-86.
Figure 5-86
Continued
5-110
68P02909W07-A
Aug 2008
Configuring the Links on the Gb Interface (IP Transmission Mode on the Gb Interface)
Procedure 5-27
3
Figure 5-87
68P02909W07-A
5-111
Aug 2008
Chapter 5:
This section describes how to configure BSC clock signals when the A Interface uses the IP
transmission mode. The BSC clock signals are responsible for the synchronization of boards in
each subrack.
Mandatory/Optional
Mandatory
NOTE
When the A Interface uses the IP transmission mode, the clock source for the BSC
can be extracted only by the GGCU from the BITS clock. The GGCU processes
the input clock and generates the 8 kHz clock, which is used as the transmission
synchronization clock and the time synchronization clock for the boards in the GMPS
or GEPS.
The system clock has two priorities: priority 1 and priority 2. Priority 1 is
higher than priority 2.
Prerequisites
The GGCU in the GMPS is configured. For details, refer to Configuring the GGCU on
page 3-33.
The BITS clock is ready, or the line clock for the GMPS is configured.
Preparation
Table 5-35
clock
Example of the data negotiated and planned for configuring the system
Parameter
Example
Source
Priority
5-112
68P02909W07-A
Aug 2008
Table 5-35 Example of the data negotiated and planned for configuring the system
clock (Continued)
Parameter
Example
Source
Source Type
2M external clock 0
2M external clock 1
2 MHz
2 Mbit/s
Source Sub-type
Procedure
Procedure 5-28
Choose Configure System Clock from the shortcut menu. A dialog box is displayed, as
shown in Figure 5-88.
Figure 5-88
Continued
68P02909W07-A
5-113
Aug 2008
Configuring the 8K Reference Clock for the GMPS Chapter 5: Configuring the BSC (IP Transmission Mode on the A Interface)
Procedure 5-28
CAUTION
Source Type and Work Mode cannot be configured in one operation. Configure
them separately. After configuring Source Type, exit the configuration wizard,
and then start the configuration wizard again to configure Work Mode.
3
Mandatory/Optional
Mandatory
Prerequisites
The GSCU in the GMPS is configured. For details, refer to Configuring the GSCU on
page 3-31.
The GGCU in the GMPS is configured. For details, refer to Configuring the GGCU on
page 3-33.
Preparation
Table 5-36 Example of data negotiated and planned for configuring the 8K reference
clock for the GMPS
Parameter
Example
Source
GGCU Backplane
5-114
68P02909W07-A
Aug 2008
Procedure
Procedure 5-29
Choose Configure 8K Reference Clock from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-89.
Figure 5-89
Mandatory/Optional
Mandatory
68P02909W07-A
5-115
Aug 2008
Configuring the 8K Reference Clock for the GEPS Chapter 5: Configuring the BSC (IP Transmission Mode on the A Interface)
Prerequisites
The GSCU in the GEPS is configured. For details, refer to Configuring the GSCU on page
3-31.
The GGCU in the GMPS is configured. For details, refer to Configuring the GGCU on
page 3-33.
Preparation
Table 5-37 Example of the data negotiated and planned for configuring the 8K
reference clock for the GEPS
Parameter
Example
Source
GGCU Panel
Procedure
Procedure 5-30
1
5-116
68P02909W07-A
Aug 2008
Procedure 5-30
2
Choose Configure 8K Reference Clock from the shortcut menu. A dialog box is displayed,
as shown in Figure 5-90.
Figure 5-90
Repeat step 1 through step 4 to configure the 8K reference clock for more GEPSs.
68P02909W07-A
Aug 2008
5-117
Configuring the 8K Reference Clock for the GEPS Chapter 5: Configuring the BSC (IP Transmission Mode on the A Interface)
5-118
68P02909W07-A
Aug 2008
Chapter
6
Configuring the BTS
68P02909W07-A
Aug 2008
6-1
This section describes how to configure a BTS for the BSC. This configuration enables the radio
transmit/receive function of the BTS and the radio coverage of the cells. The configuration
also enables the BSC to perform centralized control and management of the BTS and allocate
radio resources for the BTS.
6-2
68P02909W07-A
Aug 2008
Adding a BTS
Adding a BTS
This section describes how to add a BTS of the MOTO BTS family. The MOTO BTS family
consists of the HorizonMacro, the HorizonMacro2, the Horizon2Mini, and the Horizon2Micro.
Mandatory/Optional
Mandatory
Prerequisites
The GXPUM is configured for the GMPS or GEPS where the GEIUB/GOIUB is located. For
changes in the document, refer to Configuring the GXPUM on page 3-24.
NOTE
The configuration of the HorizonMacro2 BTS is similar to that of HorozonMacro BTS.
There are four types of TRX board, the CTU, the SCTU2, the DCTU2, and the CCTU2.
On the CTU and the SCTU2, one physical TRX maps one logical TRX. On the DCTU2
and the CCTU2, one physical TRX maps two logical TRXs, and these two logical TRXs
must be configured in one cell. The HorizonMacro BTS supports configuration of the
CTU,the SCTU2, and the DCTU2. The HorizonMacro2 BTS supports configuration
of the CTU, the SCTU2, the DCTU2, and the CCTU2.
68P02909W07-A
6-3
Aug 2008
Preparation
Table 6-1
Example of the data negotiated and planned for adding a HorizonMacro BTS
Parameter
BTS attributes
Cell attributes
TRX attributes
Antenna feeder
attributes
Example
Source
Site Name
BTS 1
Network planning
Site Type
HorizonMacro
Network planning
0 GEIUB Port
Network planning
Multiplexing Mode
4:1
Network planning
FlexAbis Mode
Fix
Network planning
Service Mode
TDM
Network planning
Config Ring
NO
Network planning
Config AbisByPass
NO
Network planning
Cell Name
Cell 1
Network planning
Frequency Band
GSM900
Network planning
MCC
460
Network planning
MNC
01
Network planning
LAC
8240
Network planning
CI
Network planning
BCC
Network planning
NCC
Network planning
Normal Cell
Network planning
Cell Type
Normal Cell
Network planning
TRX TYPE
CTU
Network planning
Assigned Cell
Cell 1
Network planning
Frequency
configuration
Network planning
TRX configuration
TRX 0, TRX 1
Network planning
Antenna Select
ANT 0A/0B
Network planning
The following procedure describes how to add a HorizonMacro on the GEIUB in the GMPS
and configured with CTU.
6-4
68P02909W07-A
Aug 2008
Procedure
Procedure 6-1
1
When adding a BTS for the first time, start the wizard for adding a BTS only on the
GEIUB/GOIUB in the GMPS or GEPS. On the BSC Local Manager, right-click a GEIUB
in the GMPS.
If a BTS already exists, add a cascaded BTS under this BTS. On the Management Tree
tab page, right-click a BTS.
Figure 6-1
Continued
68P02909W07-A
6-5
Aug 2008
Procedure 6-1
3
Figure 6-2
NOTE
Set Config Ring to Yes and click OK. The Set Rev Info dialog box is displayed.
The HorizonMacro and the HorizonMacro2 does not support the Config
AbisByPass function. For the HorizonMacro and the HorizonMacro2, Support
Separate is selected by default.
Continued
6-6
68P02909W07-A
Aug 2008
Procedure 6-1
5
Figure 6-3
Continued
68P02909W07-A
6-7
Aug 2008
Procedure 6-1
6
Figure 6-4
Select a BTS, and then click Add Cell. A dialog box is displayed, as shown in Figure 6-5.
Figure 6-5
Adding a cell
Continued
6-8
68P02909W07-A
Aug 2008
Procedure 6-1
8
NOTE
To add more than one cell at a time, set Number of Cells. The added cells are
named the current Cell Name plus a number in sequence.
9
Figure 6-6
Continued
68P02909W07-A
6-9
Aug 2008
Procedure 6-1
10
Figure 6-7
Continued
6-10
68P02909W07-A
Aug 2008
Procedure 6-1
11
Figure 6-8
12
In the dialog box shown in Figure 6-8, right-click an empty slot in the subrack2 and choose
Add Board>CTU from the shortcut menu. A CTU is added.
Continued
68P02909W07-A
6-11
Aug 2008
Procedure 6-1
13
Right-click the added CTU and choose Configure Board Attributes from the shortcut
menu. A dialog box is displayed, as shown in Figure 6-9.
Figure 6-9
14
15
6-12
68P02909W07-A
Aug 2008
Procedure 6-1
16
Choose the logical TRX on the CTU, and double-click. A dialog box is displayed, as shown
in Figure 6-10.
Figure 6-10
Continued
68P02909W07-A
6-13
Aug 2008
Procedure 6-1
17
Click the Configure Site Board Attributes tab to display the tab page, as shown in
Figure 6-11.
Figure 6-11
18
19
Continued
6-14
68P02909W07-A
Aug 2008
Procedure 6-1
20
21
Figure 6-12
Continued
68P02909W07-A
6-15
Aug 2008
Procedure 6-1
22
Figure 6-13
Continued
6-16
68P02909W07-A
Aug 2008
Procedure 6-1
23
NOTE
If you select GPRS Support, the BSC must be configured with GDPUP.
If the BTS does not support the GPRS function or the GPRS services are
unavailable in the cell, do not select GPRS Support.
24
25
Mandatory/Optional
Mandatory
Prerequisites
The GXPUM is configured for the GMPS or GEPS where the GEIUB/GOIUB is located. For
changes in the document, refer to Configuring the GXPUM on page 3-24.
NOTE
The configuration of the Horizon2Micro BTS is similar to that of HorozonMacro BTS.
There are four types of TRX board, the CTU, the SCTU2, the DCTU2, and the CCTU2.
On the CTU and the SCTU2, one physical TRX maps one logical TRX. On the DCTU2
and the CCTU2, one physical TRX maps two logical TRXs, and these two logical TRXs
must be configured in one cell.
68P02909W07-A
6-17
Aug 2008
Preparation
Table 6-2
Example of the data negotiated and planned for adding a HorizonMacro BTS
Parameter
BTS attributes
Cell attributes
TRX attributes
Antenna feeder
attributes
Example
Source
Site Name
BTS 1
Network planning
Site Type
Horizon2Mini
Network planning
0 GEIUB Port
Network planning
Multiplexing Mode
4:1
Network planning
FlexAbis Mode
Fix
Network planning
Service Mode
TDM
Network planning
Config Ring
NO
Network planning
Config AbisByPass
NO
Network planning
Cell Name
Cell 1
Network planning
Frequency Band
GSM900
Network planning
MCC
460
Network planning
MNC
01
Network planning
LAC
8240
Network planning
CI
Network planning
BCC
Network planning
NCC
Network planning
Normal Cell
Network planning
Cell Type
Normal Cell
Network planning
TRX TYPE
CTU
Network planning
Assigned Cell
Cell 1
Network planning
Frequency
configuration
Network planning
TRX configuration
TRX 0, TRX 1
Network planning
Antenna Select
ANT 0A/0B
Network planning
The following procedure describes how to add a Horizon2Mini on the GEIUB in the GMPS,
and configured with CCTU2.
6-18
68P02909W07-A
Aug 2008
Procedure
Procedure 6-2
1
When adding a BTS for the first time, start the wizard for adding a BTS only on the
GEIUB/GOIUB in the GMPS or GEPS. On the BSC Local Manager, right-click a GEIUB
in the GMPS.
If a BTS already exists, add a cascaded BTS under this BTS. On the Management Tree
tab page, right-click a BTS.
Figure 6-14
Continued
68P02909W07-A
6-19
Aug 2008
Procedure 6-2
3
Figure 6-15
NOTE
Set Config Ring to Yes and click OK. The Set Rev Info dialog box is displayed.
The HorizonMacro and the HorizonMacro2 does not support the Config
AbisByPass function. For the Horizon2Mini and the Horizon2Micro, Support
Separate is selected by default.
Continued
6-20
68P02909W07-A
Aug 2008
Procedure 6-2
5
Figure 6-16
Continued
68P02909W07-A
6-21
Aug 2008
Procedure 6-2
6
Figure 6-17
Select a BTS, and then click Add Cell. A dialog box is displayed, as shown in Figure 6-18.
Figure 6-18
Adding a cell
Continued
6-22
68P02909W07-A
Aug 2008
Procedure 6-2
8
NOTE
To add more than one cell at a time, set Number of Cells. The added cells are
named the current Cell Name plus a number in sequence.
9
Figure 6-19
Continued
68P02909W07-A
6-23
Aug 2008
Procedure 6-2
10
Figure 6-20
Continued
6-24
68P02909W07-A
Aug 2008
Procedure 6-2
11
Figure 6-21
12
In the dialog box shown in Figure 6-21, right-click an empty slot in the subrack2 and choose
Add Board>CCTU2 from the shortcut menu. A CCTU2 is added.
Continued
68P02909W07-A
6-25
Aug 2008
Procedure 6-2
13
Right-click the added CCTU2 and choose Configure Board Attributes from the shortcut
menu. A dialog box is displayed, as shown in Figure 6-22.
Figure 6-22
14
15
6-26
68P02909W07-A
Aug 2008
Procedure 6-2
16
Choose the logical TRX on the CCTU2, and double-click. A dialog box is displayed, as shown
in Figure 6-23.
Figure 6-23
Continued
68P02909W07-A
6-27
Aug 2008
Procedure 6-2
17
Click the Configure Site Board Attributes tab to display the tab page, as shown in
Figure 6-24
Figure 6-24
18
19
20
6-28
68P02909W07-A
Aug 2008
Procedure 6-2
21
Figure 6-25
Continued
68P02909W07-A
6-29
Aug 2008
Procedure 6-2
22
Figure 6-26
Continued
6-30
68P02909W07-A
Aug 2008
Procedure 6-2
23
NOTE
If you select GPRS Support, the BSC must be configured with GDPUP.
If the BTS does not support the GPRS function or the GPRS services are
unavailable in the cell, do not select GPRS Support.
24
25
68P02909W07-A
6-31
Aug 2008
This section describes how to configure the optional BTS attributes, such as site chain and
reciprocal relations between cells.
Mandatory/Optional
CAUTION
Do not add a site chain between BTSs that are configured on the GEIUB/GOIUB in
different subracks. If two BTSs are configured on two boards that are in different work
modes, a site chain cannot be established between the two BTSs. A site chain cannot
be configured for the BTS in IP transmission mode.
Prerequisites
Preparation
Table 6-3
Example of the data negotiated and planned for configuring a site chain
Parameter
Example
Source
Subrack No.
Subrack 0
Slot 18
Port No.
1 GEIUB Port
1 Site Port
The following procedure describes how to add a site chain between a DBS3036 site and a
GEIUB in the GMPS.
6-32
68P02909W07-A
Aug 2008
Procedure
Procedure 6-3
Choose Add or Delete Site Chain from the shortcut menu. A dialog box is displayed,
as shown in Figure 6-27.
Figure 6-27
Continued
68P02909W07-A
6-33
Aug 2008
Procedure 6-3
3
Select the BTS and then click Add or Delete Chain. A dialog box is displayed, as shown
in Figure 6-28.
Figure 6-28
Continued
6-34
68P02909W07-A
Aug 2008
Procedure 6-3
4
Figure 6-29
Click OK to save the configurations and return to the dialog box shown in Figure 6-28.
68P02909W07-A
6-35
Aug 2008
Scenario
Mandatory/Optional
Prerequisites
None.
Preparation
Table 6-4
cell
Parameter
Example
Source
Cell Name
2G External Cell-1
Network planning
Network planning
MCC
460
Network planning
MNC
01
Network planning
LAC
8240
Network planning
CI
Network planning
BCCH FD
88
Network planning
BCC
Network planning
NCC
Network planning
Cell Priority
Prior-1
Network planning
Co-MSC
Yes
Network planning
Procedure
Procedure 6-4
6-36
68P02909W07-A
Aug 2008
Procedure 6-4
2
Choose Add 2G External Cell from the shortcut menu. A dialog box is displayed, as shown
in Figure 6-30.
Figure 6-30
Continued
68P02909W07-A
6-37
Aug 2008
Procedure 6-4
3
Figure 6-31
NOTE
To add 2G external cells in batches, set the number of 2G external cells in
6-38
68P02909W07-A
Aug 2008
Mandatory/Optional
Prerequisites
None.
Preparation
Table 6-5
cell
Parameter
Example
Source
Cell Name
3G External Cell-1
Network planning
MCC
460
Network planning
MNC
10
Network planning
LAC
8240
Network planning
CI
Network planning
RNC ID
Network planning
DL UARFCN
10680
Network planning
10
Network planning
Diversity
NO
Network planning
Procedure
Procedure 6-5
68P02909W07-A
6-39
Aug 2008
Procedure 6-5
2
Choose Add 3G External Cell from the shortcut menu. A dialog box is displayed, as shown
in Figure 6-32.
Figure 6-32
Continued
6-40
68P02909W07-A
Aug 2008
Procedure 6-5
3
Figure 6-33
NOTE
To add 3G external cells in batches, set the number of 3G external cells in
68P02909W07-A
6-41
Aug 2008
Mandatory/Optional
NOTE
The cells in the BSC can be set to bidirectional adjacent cells or single
directional adjacent cells.
The cells in another BSC can be set to only single directional adjacent cells
of the cells in the BSC.
Adjacent cells indicate the reciprocal relations between cells. The cell where an MS
is handed over from is called originating cell. The cell where an MS is handed over to
is called neighbor cell or adjacent cell.
Prerequisites
A 2G or 3G external cell is configured.
Preparation
Table 6-6
Example of the data negotiated and planned for configuring adjacent cells
Parameter
Example
Source
Source cell
Cell 1
Network planning
Adjacent cell
Cell 2
Network planning
Unidirectional neighbor
cell
2G external cell-13G
external cell-1
Network planning
6-42
68P02909W07-A
Aug 2008
Procedure
Procedure 6-6
Choose Configure Adjacent Cell. A dialog box is displayed, as shown in Figure 6-34.
Figure 6-34
Continued
68P02909W07-A
6-43
Aug 2008
Procedure 6-6
3
Select Cell1 from the Cell view list box and add it to theSelected cell list box. Click Next.
A dialog box is displayed, as shown in Figure 6-35.
Figure 6-35
Continued
6-44
68P02909W07-A
Aug 2008
Procedure 6-6
4
Select Cell 1 and click Set Adjacent Cells. A dialog box is displayed, as shown in
Figure 6-36.
Figure 6-36
68P02909W07-A
Aug 2008
6-45
6-46
68P02909W07-A
Aug 2008
Chapter
7
Reference to BSC Data Configuration
68P02909W07-A
Aug 2008
7-1
This provides the principles and reference information of BSC data configuration.
7-2
68P02909W07-A
Aug 2008
This section describes the configuration principles of the BSC cabinets, subracks, and boards
when the BM and TC are configured in different subracks.
Cabinet
The configuration principles of BSC cabinets are as follows:
The GBCR cabinet is configured on the BSC side and only one GBCR cabinet can be
configured. The GBSR cabinet is configured on the BSC side or on the MSC side and up
to two GBSR cabinets can be configured.
By default the GBCR cabinet, numbered 0, is displayed on the LMT. The newly added
cabinets are numbered in sequence.
The cabinet placed on the BSC side is called local cabinet. It holds the GEPS and the GTCS.
The cabinet placed on the MSC side is called the remote cabinet. It holds only the GTCS.
Each cabinet must be configured with a power distribution box and a management subrack
for the power distribution box.
Subrack
The configuration principles of BSC subracks are as follows:
The GMPS is mandatory in the BSC. Each BSC must be configured with one GMPS and
zero to three GEPSs.
The GMPS, GEPS, and GTCS, including the boards in these subracks, must be configured
in order.
All the GTCSs must be configured in only the local cabinet or in only the remote cabinet. In
the local cabinet, a maximum of two GTCSs can be configured; in the remote subrack, a
maximum of three GTCSs can be configured.
Each subrack is configured with a fan box. The fan box is added automatically when
you add a subrack.
Two GGCUs (in active/standby mode), two GTNUs (in active/standby mode), two GSCUs (in
active/standby mode), and two GOMUs (in active/standby mode) are displayed in the GMPS
by default on the LMT. By default, two GTNUs (in active/standby mode) and two GSCUs (in
active/standby mode) are displayed in the GEPS/GTCS on the LMT. These boards can be
deleted only when you delete the subracks where these boards are located.
68P02909W07-A
7-3
Aug 2008
Board
Board
The configuration principles of BSC boards are as follows:
The A Interface, Abis interface, Ater interface, and Gb interface support the E1/T1, and
STM-1 transmission modes. The A Interface also supports the FE/GE transmission mode.
The E1/T1, STM-1, and FE/GE transmission modes can coexist in one subrack. To facilitate
configuration and maintenance, Motorola recommends that one interface use one type of
interface boards. Do not configure two types of interface boards together.
To ensure the system reliability, Motorola recommends that all the boards, except for the
GDPUX/GDPUP, be configured in active/standby mode.
The GOIUA, GOIUB, and GOUIT support the APS function. If the GOIUB, and GOUIT are in
active/standby mode, the APS function is selected by default.
The GGCU, GSCU, GTNU, and GOMU are displayed by default on the LMT. Table 7-1 lists the
configuration principles of the boards except for the boards displayed by default on the LMT.
Table 7-1
Board
Configuration Principles
GDPUX
GEIUA/GOIUA
These boards support the independent mode and the active/standby mode.
The active/standby mode is recommended.
The GEIUA and the GOIUA can be configured in one subrack if required.
GEIUB/GOIUB
These boards support the independent mode and the active/standby mode.
The active/standby mode is recommended.
The GEIUB and the GOIUB can be configured in one subrack if required.
GEIUT/GOIUT
These boards support the independent mode and the active/standby mode.
The active/standby mode is recommended.
The GEIUT and the GOIUT can be configured in one subrack if required.
Continued
7-4
68P02909W07-A
Aug 2008
Table 7-1
Board
Board
Configuration Principles
GEPUG/GFGUG
These boards support the independent mode and the active/standby mode.
The active/standby mode is recommended.
These boards support the independent mode and the active/standby mode.
The active/standby mode is recommended.
These boards support the independent mode and the active/standby mode.
The active/standby mode is recommended.
GDPUP
GXPUM
GXPUT
NOTE
On the BSC Local Manager, the types of boards that can be configured depend on
the type of the subrack that holds the boards and the serial numbers of slots in the
subrack. Table 7-1 provides the recommended configurations of the boards. Modify
the configurations according to actual requirements.
68P02909W07-A
7-5
Aug 2008
This section describes the configuration principles of BSC communication links and signaling
links when the BM and TC are configured in different subracks.
The subrack communication links are configured between the GMPS and the GEPS,
between GEPSs, or between GTCSs.
A maximum of three subrack communication links can be configured between two subracks.
The communication between subracks is achieved through the GTNU in each subrack.
There are six external ports, numbered TDM0TDM5, on the panel of the GTNU. Only one
subrack communication link can use each port.
7-6
68P02909W07-A
Aug 2008
Semipermanent Link
Semipermanent Link
The configuration principles are as follows:
The semipermanent link is configured between the GMPS and the GEPS, between GEPSs,
or between GTCSs.
For a semipermanent link, at least one of the following pairs of numbers must be different:
The In-BSC subrack number and the Out-BSC subrack number
The In-BSC slot number and the Out-BSC slot number
The In-BSC port number and the Out-BSC port number
If the data rate of a semipermanent link is 16 kbit/s, In-BSC Timeslot No. and Out-BSC
Timeslot No. must be set to 0, 2, 4, or 6.
If the data rate of a semipermanent link is 32 kbit/s, the In-BSC Timeslot No., and the
Out-BSC Timeslot No. must be set to 0 or 4.
If the data rate of a semipermanent link is 64 kbit/s, the In-BSC Timeslot No., and the
Out-BSC Timeslot No. must be set to 0.
If the data rate of a semipermanent link is 8 kbit/s, the In-BSC Timeslot No., and the
Out-BSC Timeslot No. can be set to any value.
The timeslots on semipermanent links can be multiplexed onto the 64 kbit/s E1/T1 timeslot
on one BSC port. The timeslots on semipermanent links and the monitoring timeslots can
be multiplexed onto the 64 kbit/s E1/T1 timeslot on one BSC port.
The specified BSC port timeslot for a semipermanent link must be NULL or FlexTS.
The Ater signaling links must be configured when the GTCS is configured on the MSC side.
Each GEIUT/GOIUT in the GMPS/GEPS can be configured with up to eight 64 kbit/s Ater
signaling links.
68P02909W07-A
7-7
Aug 2008
Ater OML
Ater OML
The configuration principles are as follows:
The Ater OML must be configured when the GTCS is configured on the MSC side.
A maximum of two Ater OMLs can be configured between the GMPS and the main GTCS.
The timeslot masks of the two Ater OMLs can be different.
At least four consecutive timeslots must be selected for the timeslot mask of each Ater
OML.
A Interface E1/T1
The configuration principles are as follows:
The CICs of the A Interface E1/T1 range from 0 to 65535. These CICs do not have to be
consecutive. You can manually change the number of the CIC.
The CICs (except for 65535) of the A Interface E1/T1 must be unique in a signaling point.
The CICs of the A Interface E1/T1 between the BSC and different MSCs can be duplicate.
For example, the CICs between the BSC and MSC 1, between the BSC and MSC 2, and
between the BSC and MGW 1 can be duplicate.
The CICs of the A Interface E1 between the BSC and multiple MGWs (DPC groups) can
be duplicate. For example, the CICs between the BSC and MGW 1, and between the
BSC and MGW 2 can be duplicate.
If multiple E1s/T1s of the BSC are connected to one MGW, the CIC of each A Interface
E1 must be unique.
7-8
68P02909W07-A
Aug 2008
The SS7 signaling link supports two types of rates: 64 kbit/s and 2 Mbit/s. The 2 Mbit/s
signaling link can be 2.048 Mbit/s or N x 64 kbit/s (1<N<32). One BSC supports only
one rate type.
Each SS7 signaling link can be configured with different bandwidths. The SS7 signaling
links are in load sharing mode. Therefore, Motorola recommends that all the SS7 signaling
links be configured with the same bandwidth. Each 2 Mbit/s signaling link can be the
combination of any timeslots (except for timeslot 0) on an E1.
One pair of signaling points can be configured with up to sixteen 64 kbit/s SS7 signaling
links. In configuration, to balance the load, the recommended number of SS7 signaling
links is 2 to the power of N, that is, 2, 4, 8, or 16.
One signaling point must be configured with at least two 2 Mbit/s signaling links, and it
is recommended that the two signaling links be configured on different E1/T1 cables or
different STM-1 cables.
If the GTCS maps one DSP, each GMPS/GEPS can be configured with a maximum of sixteen
64 kbit/s SS7 signaling links; if the GTCS maps multiple DSPs, each GMPS/GEPS can be
configured with a maximum of thirty-two 64 kbit/s SS7 signaling links.
Each GMPS/GEPS can be configured with up to eight 2 kbit/s SS7 signaling links.
In E1 transmission mode, the total bandwidth of SS7 signaling links cannot exceed 4
Mbit/s. In T1 transmission mode, the total bandwidth of SS7 signaling links cannot exceed
3 Mbit/s. In E1 transmission mode, if 16 timeslots is selected for each signaling link of 64
kbit/s, the total bandwidth amounts to 1 Mbit/s. A maximum of three signaling links of 64
kbit/s can be configured because the total bandwidth cannot exceed 4 Mbit/s.
Gb Interface Link
For details on the configuration principles of Gb interface links, refer to Configuration Principles
of the Gb Interface Links on page 7-31.
Table 7-2
Interface
A interface
Ater interface
68P02909W07-A
7-9
Aug 2008
Figure 7-1 lists the links that should be configured on the A and Ater interfaces when the
GTCS is placed on the BSC side. The GMPS communicates with the main GTCS through the
GSCU to transmit SS7, internal signaling, and OM information. Through the GSCU, the SS7 is
transparently transmitted to the GXPUM/GXPUT in the GMPS/GEPS for further processing.
Figure 7-1
Links on the A and Ater interfaces (GTCS configured on the BSC side)
Figure 7-2 lists the links that should be configured on the A and Ater interfaces when the GTCS
is placed on the MSC side. Through the Ater interface, the SS7 is transparently transmitted to
the GEIUT/GXPUM/GXPUT in the GMPS/GEPS for further processing.
7-10
68P02909W07-A
Aug 2008
Figure 7-2
Links on the A and Ater interfaces (GTCS configured on the MSC side)
68P02909W07-A
7-11
Aug 2008
When the GTCS is configured on the MSC side, the Ater OM links, the Ater signaling links, and
the transparently transmitted SS7 occupy the Ater interface timeslots. The bandwidth of the
timeslots occupied by the SS7 on the Ater interface is the same as that on the A Interface. The
bandwidth of the interface timeslots occupied by the Ater OM links and Ater signaling links is
subject to the BSC configuration. Table 7-3 lists the bandwidth of OM timeslots and signaling
timeslots on the Ater interface.
Table 7-3
BSC Configuration
GMPS + GTCS
16 timeslots of 64 kbit/s
GMPS + GEPS + 2
GTCSs
16 timeslots of 64 kbit/s
GMPS + 2 GEPSs + 3
GTCSs
31 timeslots of 64 kbit/s
GMPS + 3 GEPSs + 4
GTCSs
31 timeslots of 64 kbit/s
16 timeslots of 64 kbit/s
GMPS + 3 GEPS + 2
GTCS
31 timeslots of 64 kbit/s
NOTE
The GMPS and the GEPS are collectively known as the BM subrack.
7-12
68P02909W07-A
Aug 2008
This section describes the configuration principles of the BSC clock when the BM and TC are
configured in different subracks.
GMPS/GEPS Clock
The GGCU in the GMPS traces the upper-level clock, and then provides clock signals for the
GMPS and the GEPS.
The reference clock for the GGCU is of two types: the line clock extracted from the Ater
interface by the GMPS and the BITS clock. The BITS clock is more accurate and more reliable.
Therefore, the BITS clock is preferred.
GTCS Clock
The GTCS traces the clock from the A Interface. Each GTCS extracts the line clock from the A
Interface. The configuration of the GTCS clock is the same regardless of whether the GTCS is
configured on the BSC side or on the MSC side.
Table 7-4
Clock
Configuration Principles
If the GEIUA is configured in the GTCS, two line clock signals, line
0 and line 1, can be configured. If the GOIUA is configured in the
GTCS, only one line clock signal can be configured and the line clock
signal must be configured on port 0 on the GOIUA.
If the BSC is configured with more than one GTCS, the GTCSs
extract clock signals from the A interface as their line clock signals.
8K reference
clock of the GTCS
If the configured line clock signals are selected for the 8K reference
clock, do not delete any line clock.
The line clock of the GMPS must be configured on the Ater connection
path of the GMPS.
Continued
68P02909W07-A
7-13
Aug 2008
Table 7-4
Clock
Configuration Principles
System clock
The clock source and the clock source priority have a one-to-one
mapping.
By default, the priority of the BITS clock is higher than that of the
line clock. Modify the priority of the clock source to set the priority
of the line clock higher than that of the BITS clock.
Switchover strategy of the current clock source: The BSC requires only
one clock source when running. Select a handover strategy to switch the
faulty clock source to a normal clock source. The clock source has three
working modes: AUTO, MANUAL, and FREE.
The FREE mode is the default clock working mode of the BSC.
7-14
68P02909W07-A
Aug 2008
This section describes the configuration principles of the BSC cabinets, subracks, and boards
with the BM/TC combined.
Cabinet
The configuration principles of BSC cabinets are as follows:
By default, the GBCR cabinet, numbered 0, is displayed on the LMT. The newly added
cabinets are numbered in sequence.
The GBSR cabinet is configured on the BSC side. It holds the GEPS and GMPS. A maximum
of three GBSR cabinets can be configured.
Each cabinet must be configured with a power distribution box and a management subrack
for the power distribution box.
Subrack
The configuration principles of BSC subracks are as follows:
By default, the GMPS is displayed on the LMT. Zero to three GEPSs can be configured
according to actual requirements.
The GMPS and GEPS, including the boards in these subracks, must be configured in order.
Each subrack is configured with a fan box. The fan box is added automatically when
you add a subrack.
Two GGCUs (in active/standby mode), two GTNUs (in active/standby mode), two GSCUs
(in active/standby mode), and two GOMUs (in active/standby mode) are displayed in the
GMPS by default on the LMT. By default, two GTNUs (in active/standby mode) and two
GSCUs (in active/standby mode) are displayed in the GEPS on the LMT. These boards can
be deleted only when you delete the subracks where these boards are located.
68P02909W07-A
7-15
Aug 2008
Board
Board
The configuration principles of BSC boards are as follows:
The A Interface, Abis interface, and Gb interface support the E1/T1 and STM-1 transmission
modes. The A Interface also supports the GE/FE transmission mode. The E1/T1, STM-1,
and GE/FE transmission modes can coexist in one subrack. To facilitate configuration and
maintenance, Motorola recommends that one interface use one type of interface boards.
Do not configure two types of interface boards together.
To ensure the system reliability, Motorola recommends that all the boards, except for the
GDPUX/GDPUP, be configured in active/standby mode.
The GOIUA, and GOIUB support the APS function. If the GOIUA and the GOIUB are in
active/standby mode, the APS function is selected by default.
The GGCU, GSCU, GTNU, and GOMU are displayed by default on the LMT. Table 7-5 lists the
configuration principles of the boards except for the boards displayed by default on the LMT.
Table 7-5
Board
Configuration Principles
GDPUX
The GEIUA and the GOIUA can be configured in one subrack if required.
GEIUA/GOIUA
GEIUB/GOIUB
Continued
7-16
68P02909W07-A
Aug 2008
Table 7-5
Board
Board
Configuration Principles
GFGUG/GEPUG
The GDPUP is configured when the BSC is configured with the built-in
PCU.
GDPUP
GXPUM
GXPUT
NOTE
On the BSC Local Manager, the types of boards that can be configured depend on
the type of the subrack that holds the boards and the serial numbers of slots in the
subrack. Table 7-5 provides the recommended configurations of the boards. Modify
the configurations according to actual requirements.
68P02909W07-A
7-17
Aug 2008
This section describes the configuration principles of the BSC communication links and signaling
links when the BM and TC are configured in the same subrack.
The subrack communication link is established between the GMPS and the GEPS.
A maximum of three subrack communication links can be configured between two subracks.
The communication between subracks is achieved through the GTNU in each subrack.
There are six external ports, numbered TDM0TDM5, on the panel of the GTNU. Each port
can be used by only one subrack communication link.
Semipermanent Link
The semipermanent link is established between the GMPS and the GEPS.
For a semipermanent link, at least one of the following pairs of numbers must be different:
The In-BSC subrack number and the Out-BSC subrack number
The In-BSC slot number and the Out-BSC slot number
The In-BSC port number and the Out-BSC port number
If the data rate of a semipermanent link is 16 kbit/s, In-BSC Timeslot No. and Out-BSC
Timeslot No. should be set to 0, 2, 4, and 6.
If the data rate of a semipermanent link is 32 kbit/s, In-BSC Timeslot No., and the Out-BSC
Timeslot No. should be set to 0 and 4.
If the data rate of a semipermanent link is 64 kbit/s, In-BSC Timeslot No., and the Out-BSC
Timeslot No. should be set to 0.
If the data rate of a semipermanent link is 8 kbit/s, In-BSC Timeslot No., and the Out-BSC
Timeslot No. can be set to any value.
The timeslots on semipermanent links can be multiplexed onto the 64 kbit/s timeslot on
one BSC port. The timeslots on semipermanent links and the monitoring timeslots can be
multiplexed onto the 64 kbit/s timeslot on one BSC port.
The specified BSC port timeslot for a semipermanent link must be NULL or FlexTS.
7-18
68P02909W07-A
Aug 2008
A Interface E1/T1
A Interface E1/T1
The CICs of the A Interface E1/T1 range from 0 to 65535. These CICs do not have to be
consecutive. You can manually change the number of the CIC.
The CIC (except for 65535) of each A Interface E1/T1 must be unique in a signaling point.
The CICs of the A Interface E1/T1 between the BSC and different MSCs can be duplicate.
For example, the CICs between the BSC and MSC 1, between the BSC and MSC 2, and
between the BSC and MGW 1 can be duplicate.
The CICs of the A Interface E1/T1 between the BSC and multiple MGWs (DPC groups) can
be duplicate. For example, the CICs between the BSC and MGW 1, and between the
BSC and MGW 2 can be duplicate.
If multiple E1s/T1s of the BSC are connected to one MGW, the CIC of each A Interface
E1/T1 must be unique.
68P02909W07-A
7-19
Aug 2008
The SS7 signaling link supports two types of rates: 64 kbit/s and 2 Mbit/s. The 2 Mbit/s
signaling link can be a 2.048 Mbit/s link or N x 64 kbit/s (1<N<32) links. One BSC
supports only one rate type.
Each SS7 signaling link can be configured with different bandwidths. The SS7 signaling
links are in load sharing mode. Therefore, Motorola recommends that all the SS7 signaling
links be configured with the same bandwidth. Each 2 Mbit/s signaling link can be the
combination of any timeslots (except for timeslot 0) on an E1.
One pair of signaling points can be configured with up to sixteen 64 kbit/s SS7 signaling
links. In configuration, to balance the load, the recommended number of SS7 signaling
links is 2 to the power of N, that is, 2, 4, 8, or 16.
One signaling point must be configured with at least two 2 Mbit/s signaling links, and it
is recommended that the two signaling links are configured on different E1/T1 cables or
different STM-1 cables.
If the GTCS maps one DSP, each GMPS/GEPS can be configured with a maximum of sixteen
64 kbit/s SS7 signaling links; if the GTCS maps multiple DSPs, each GMPS/GEPS can be
configured with a maximum of thirty-two 64 kbit/s SS7 signaling links.
Each GMPS/GEPS can be configured with up to eight 2 kbit/s SS7 signaling links.
In E1 transmission mode, the total bandwidth of SS7 signaling links cannot exceed 4
Mbit/s. In T1 transmission mode, the total bandwidth of SS7 signaling links cannot exceed
3 Mbit/s. In E1 transmission mode, if each signaling link of 64 kbit/s has 16 timeslots, the
total bandwidth amounts to 1 Mbit/s. A maximum of three signaling links of 64 kbit/s can
be configured because the total bandwidth cannot exceed 4 Mbit/s.
Gb Interface Link
For details on the configuration principles of Gb interface links, refer to Configuration Principles
of the Gb Interface Links on page 7-31.
7-20
68P02909W07-A
Aug 2008
This section describes the configuration principles of the BSC clock when the BM and TC
are configured in the same subrack.
GMPS/GEPS Clock
The GGCU in the GMPS traces the upper-level clock, and then provides clock signals for the
GMPS and the GEPS.
The reference clock for the GGCU is of two types: BITS clock and line clock. The BITS clock is
more accurate and more reliable. Therefore, the BITS clock is preferred.
Table 7-6
Clock
Configuration Principles
Line clock
If the GEIUA is configured, two line clock signals, line 0 and line 1, can
be configured. If the GOIUA is configured, only one line clock signal can
be configured and the line clock signal must be configured on port 0
on the GOIUA.
8K reference
clock
If the configured line clock signals are selected for the 8K reference
clock, do not delete any line clock.
System clock
The clock source and the clock source priority have a one-to-one
mapping.
By default, the priority of the BITS clock is higher than that of the
line clock. Modify the priority of the clock source to set the priority
of the line clock higher than that of the BITS clock.
Switchover strategy of the current clock source: The BSC requires only
one clock source when running. Select a handover strategy to switch the
faulty clock source to a normal clock source. The clock source has three
working modes: AUTO, MANUAL, and FREE.
Continued
68P02909W07-A
7-21
Aug 2008
Table 7-6
Clock
Configuration Principles
The FREE mode is the default clock working mode of the BSC.
7-22
68P02909W07-A
Aug 2008
Configuration Principles of the BSC Devices (IP Transmission Mode on the A Interface)
This section describes the configuration principles of the BSC cabinets, subracks, and boards
when the A Interface uses the IP transmission mode.
Cabinet
The configuration principles of BSC cabinets are as follows:
Each cabinet must be configured with a power distribution box and a management subrack
for the power distribution box.
Subrack
The configuration principles of BSC subracks are as follows:
The GMPS is mandatory in the BSC. Each BSC must be configured with one GMPS and
zero to two GEPSs.
The GMPS and GEPS, including the boards in these subracks, must be configured in order.
Each subrack is configured with a fan box. The fan box is added automatically when
you add a subrack.
Two GGCUs (in active/standby mode), two GTNUs (in active/standby mode), two GSCUs
(in active/standby mode), and two GOMUs (in active/standby mode) are displayed in the
GMPS by default on the LMT. By default, two GTNUs (in active/standby mode) and two
GSCUs (in active/standby mode) are displayed in the GEPS on the LMT. These boards can
be deleted only when you delete the subracks where these boards are located.
68P02909W07-A
7-23
Aug 2008
Board
Board
The configuration principles of BSC boards are as follows:
The A Interface, Abis interface, and Gb interface support the E1/T1 and STM-1
transmission modes. The A Interface also supports the GE/FE transmission mode. The
E1/T1 transmission mode and STM-1 transmission mode can coexist in one subrack. To
facilitate configuration and maintenance, Motorola recommends that one interface use one
type of interface boards. Do not configure two types of interface boards together.
To ensure the system reliability, Motorola recommends that all the boards, except for the
GDPUX/GDPUP, be configured in active/standby mode.
The GOIUA and GOIUB support the APS function. If the GOIUB and GOIUA are in
active/standby mode, the APS function is selected by default.
The GGCU, GSCU, GTNU, and GOMU are displayed by default on the LMT. Table 7-7 lists the
configuration principles of the boards except for those displayed by default on the LMT.
Table 7-7
Board
Configuration Principles
GDPUX
GOGUA/GFGUA
The GEIUB and the GOIUB can be configured in one subrack if required.
GEIUB/GOIUB
Continued
7-24
68P02909W07-A
Aug 2008
Table 7-7
Board
Board
Configuration Principles
GFGUG/GEPUG
The GDPUP is configured when the BSC is configured with the built-in
PCU.
GDPUP
GXPUM
GXPUT
NOTE
On the BSC Local Manager, the types of boards that can be configured depend on
the type of the subrack that holds the boards and the serial numbers of slots in the
subrack. Table 7-7 provides the recommended configurations of the boards. Modify
the configurations according to actual requirements.
68P02909W07-A
7-25
Aug 2008
Configuration Principles of the BSC Transmission (IP Transmission Mode on the A Interface)
Reference to BSC Data Configuration
Chapter 7:
This section describes the configuration principles of the BSC communication links and signaling
links when the BM and TC are configured in the same subrack.
The subrack communication link is established between the GMPS and the GEPS.
A maximum of three subrack communication links can be configured between two subracks.
The communication between subracks is achieved through the GTNU in each subrack.
There are six external ports, numbered TDM0TDM5, on the panel of the GTNU. Only one
subrack communication link uses each port .
Semipermanent Link
The semipermanent link is established between the GMPS and the GEPS.
For a semipermanent link, at least one of the following pairs of numbers must be different:
The In-BSC subrack number and the Out-BSC subrack number
The In-BSC slot number and the Out-BSC slot number
The In-BSC port number and the Out-BSC port number
If the data rate of a semipermanent link is 16 kbit/s, In-BSC Timeslot No. and Out-BSC
Timeslot No. should be set to 0, 2, 4, and 6.
If the data rate of a semipermanent link is 32 kbit/s, In-BSC Timeslot No., and the Out-BSC
Timeslot No. should be set to 0 and 4.
If the data rate of a semipermanent link is 64 kbit/s, In-BSC Timeslot No., and the Out-BSC
Timeslot No. should be set to 0.
If the data rate of a semipermanent link is 8 kbit/s, In-BSC Timeslot No., and the Out-BSC
Timeslot No. can be set to any value.
The timeslots on semipermanent links can be multiplexed onto the 64 kbit/s timeslot on
one BSC port. The timeslots on semipermanent links and the monitoring timeslots can be
multiplexed onto the 64 kbit/s timeslot on one BSC port.
The specified BSC port timeslot for a semipermanent link must be NULL, CIC, or FlexTS.
7-26
68P02909W07-A
Aug 2008
Gb Interface Link
Gb Interface Link
For details on the configuration principles of Gb interface links, refer to Configuration Principles
of the Gb Interface Links on page 7-31.
68P02909W07-A
7-27
Aug 2008
Configuration Principles of the BSC Clock (IP Transmission Mode on the A Interface)
Reference to BSC Data Configuration
Chapter 7:
This section describes the configuration principles of the BSC clock when the A Interface uses
the IP transmission mode.
GMPS/GEPS Clock
The GGCU in the GMPS traces the upper-level clock, and then provides clock signals for the
GMPS and the GEPS.
The reference clock for the GGCU is the BITS clock
Table 7-8
Clock
Configuration Principles
8K reference
clock
When the A interface uses the IP transmission mode, the clock source for
the BSC cannot be the line clock.
System clock
The clock source and the clock source priority have a one-to-one
mapping.
Switchover strategy of the current clock source: The BSC requires only
one clock source when running. Select a handover strategy to switch the
faulty clock source to a normal clock source. The clock source has three
working modes: AUTO, MANUAL, and FREE.
The FREE mode is the default clock working mode of the BSC.
7-28
68P02909W07-A
Aug 2008
This section describes the configuration principles of the built-in PCU devices. When the built-in
PCU is used, the BSC must be configured with the related boards to handle the PS services, and
the configuration must follow the related principles.
The data transmission rate on the Um interface varies with the coding scheme. See Table 7-9.
Table 7-9
Coding Scheme
CS-1
9.05
CS-2
13.4
CS-3
15.6
CS-4
21.4
MCS-1
8.8
MCS-2
11.2
MCS-3
14.8
MCS-4
17.6
MCS-5
22.4
MCS-6
29.6
MCS-7
44.8
MCS-8
54.4
MCS-9
59.2
68P02909W07-A
7-29
Aug 2008
Each GDPUP can handle the services on 1024 PDCHs (including static and dynamic packet
channels). One redundant GDPUP is configured to improve the system reliability.
Each pair of GEPUPs/GFGUGs can handle the services on eight GDPUPs. One BSC is
usually configured with one pair of Gb interface boards. If more than one pair of Gb
interface boards is required, configure them uniformly in subracks.
Each pair of GEPUGs provides 32 E1 links, which support the traffic flow of 64 Mbit/s.
Each pair of GFGUGs provides eight FE ports or two GE ports, which support the traffic
flow of 128 Mbit/s.
The number of E1 links to be configured on the Gb interface depends on the factors such
as the number of PDCHs.
7-30
68P02909W07-A
Aug 2008
The Gb interface can use the FR protocol or the IP protocol. For different protocols, the
configuration objects and configuration principles of the Gb interface links are different.
When the Gb interface uses the FR protocol, the configuration of Gb interface links involves the
NSE, BC, NSVC, and PTPBVC. When the Gb interface uses the IP protocol, the configuration of
Gb interface links involves the NSE, BC, NSVC, and PTPBVC. Table 7-10 lists these objects.
Table 7-10
Object
Description
NSVC is the virtual connection between the BSC and the SGSN.
The NSVC on the BSC side and the NSVC on the SGSN side have
a one-to-one relationship. Their NSVCIs are the same. The NS
divides the NSVC into different groups. Each group is identified
by an NSEI. The NSVCs in the same group use the loading
sharing mode. If an NSVC is unavailable, the NS switches the
data from this NSVC to another NSVC for transmission. One
NSVC group is connected to one SGSN. In FR transmission
mode, one NSVC corresponds to one PVC. In IP transmission
mode, one NSVC is identified by the local IP address, local port,
peer IP address, and peer port.
Permanent Virtual
Connection (PVC)
NSE
68P02909W07-A
7-31
Aug 2008
Table 7-10
Object
Local NSVL and remote
NSVL
Figure 7-3 shows the connections of the configuration objects between the BSC and the SGSN.
Figure 7-3
7-32
68P02909W07-A
Aug 2008
One SGSN can correspond to multiple NSEs in one BSC, but all the NSVCs and PTPBVCs
in one NSE serve only one SGSN. If the FR protocol is selected, the NSVC ID on the BSC
side and that on the SGSN side must be the same.
The NSVC serves the NSE in the same subrack. All the NSVCs in one NSE must be
configured in the same subrack.
The cells in one routing area (RA) must belong to the same NSE, that is, the cells in one RA
must belong to the same BSC and SGSN.
In the case of direct point-to-point connections between the BSC and the SGSN, Motorola
recommends that multiple timeslots on the E1 be bound to form a BC.
Multiple NSVCs can be configured on one BC. Motorola recommends that a maximum of
two NSVCs on one BC serve one NSE and that the NSVCs be uniformly distributed.
68P02909W07-A
7-33
Aug 2008
This section describes the definitions and configuration principles of external cells and neighbor
cells.
External Cells
External cells are not controlled by the local BSC. External cells can be 2G external cells or 3G
external cells. 2G external cells are the GSM/GPRS cells. 3G external cells are the WCDMA cells.
Neighbor Cells
Neighbor cells are adjacent to the serving cell. Neighbor cells can be the local BSC cells, 2G
external cells, or 3G external cells. The configuration principles of neighbor cells are as follows:
One cell can be configured with up to thirty-two 2G neighbor cells and thirty-two 3G
neighbor cells.
Any two 2G external neighbor cells of a cell should not have the same main BCCH
frequencies or the same BSIC.
Any two 3G external neighbor cells of a cell should not have the same frequencies,
scrambling code, or diversity indication.
The cell configured with the enhanced concentric cell function must be set to the neighbor
cell of itself. Therefore, the cell configured with the enhanced concentric cell function
(except for the cell itself) can be configured with up to sixty-three 2G neighbor cells and
sixty-three 3G neighbor cells.
7-34
68P02909W07-A
Aug 2008
This section describes the configuration principles of the frequency hopping (FH) cell.
When configuring an FH cell, adhere to the following principles:
The GSM900 is classified into three sub frequency bands: P-GSM, E-GSM, and R-GSM.
The P-GSM (900P) band provides the frequencies numbered from 1 to 124, the E-GSM
(900E) band provides the frequencies 0 and those numbered from 975 to 1023, and the
R-GSM (900R) band provides the frequencies numbered from 955 to 974. The Motorala
BSC only supports the 900P and the 900E.
In initial configuration, the first channel to be configured is the main BCCH by default.
If the main BCCH frequency belongs to the 900P band, the 900P band is the compatible
frequency band while the 900E and 1800M bands are the incompatible frequency bands. If
the main BCCH frequency belongs to the 900E band, the 900P and 900E bands are the
compatible frequency bands while the 1800M band is the incompatible frequency bands. If
the main BCCH frequency belongs to the 900P band, the cells cannot have the frequencies
from the incompatible EGSM or 1800M band.
The TRX that carries the SDCCH should not operate on the frequency band higher than
the frequency band on which the TRX carrying the main BCCH operates. The PDCH must
be configured on the TRX whose frequency belongs to the frequency bands that are
compatible with the frequency band that provides the main BCCH.
If a cell is configured with less than two TRXs, the cell cannot be configured as an FH cell.
In a double-timeslot cell, the TRX carrying the main BCCH must be configured in the
underlaid subcell.
In a double-timeslot and concentric cell, a minimum of one static PDCH must be configured
in the overlaid subcell.
In a double-timeslot cell, the odd-numbered channels on the TRXs in the underlaid subcell
must be SDCCHs.
If a double-timeslot cell is configured with baseband FH, the TRXs in the underlaid subcell
cannot be in the same FH group as other TRXs.
If a COBCCH cell is configured with FH, all the frequencies in an FH group must be on
the same frequency band.
The main BCCH, combined BCCH, BCCH+CBCH, and BCCH should not participate in FH.
If the baseband FH and the EDGE functionality conflict, the baseband FH and the EDGE
functionality cannot be configured simultaneously.
The Base station Color Code (BCC) of a cell must be the same as the Training Sequence
Code (TSC) in the FH data table.
In baseband FH, the FH group that contains the frequencies of the TRXs not carrying the
main BCCH on timeslot 0 cannot contain the main BCCH frequency.
68P02909W07-A
7-35
Aug 2008
In RF FH, the TRX carrying the main BCCH must be set to No FH.
For the FH TRXs, the frequencies of the timeslots of the same number cannot belong to
the same FH group. If the FH group numbers are the same, the Mobile Allocation Index
Offsets (MAIOs) cannot be the same.
In a common cell, the number of frequencies in the compatible frequency bands of the main
BCCH for the GPRS cell must be smaller than or equal to 24; the number of frequencies in
the compatible frequency bands of the main BCCH for the EDGE cell must be smaller than
or equal to 16. The number of frequencies in the incompatible frequency bands of the main
BCCH is not restricted; however, the PDCH cannot be configured on the TRXs that operate
on the incompatible frequency bands of the main BCCH.
For a common cell, if the number of frequencies required in the compatible frequency
bands of the main BCCH for the GPRS cell is greater than 24 or if the number of
frequencies required in the compatible frequency bands of the main BCCH for the EDGE
cell is greater than 16, then the PDCH must be configured on only one of the TRXs that
operate on the compatible frequency bands of the main BCCH. Channel conversion is
allowed only on the channels on this TRX. Channel conversion is not allowed on the
channels on other TRXs that operate on the compatible frequency bands of the main BCCH;
that is, the maximum number of PDCHs on these TRXs is set to 0.
For a concentric cell, the number of frequencies of the TRX that carries the main BCCH in
the underlaid subcell and the channel configuration principles are the same as those of a
common cell; the number of frequencies of the TRX in the overlaid subcell and channel
configuration principles are not restricted.
In a common cell, only the TCH in the TRX that operates on the frequency bands
compatible with the frequency band that provides the main BCCH can be converted to the
PDCH. In a concentric cell, only the channel in the TRX that operates on the frequency
bands compatible with the frequency band that provides the main BCCH frequency in
the underlaid subcell can be converted to the PDCH. The TRXs that operate on the
frequency bands incompatible with the frequency band that provides the main BCCH
cannot be configured with the PDCH, and the TCHs in those TRXs cannot be converted to
PDCHs. The TRXs in the overlaid subcell can be configured with PDCHs and TCHs can
be converted to PDCHs.
7-36
68P02909W07-A
Aug 2008
TRXs
TRXs
This section describes how to assign TRXs for a cell and how to assign frequencies for TRXs.
When configuring the attributes of TRXs in a cell, assign TRXs for the cell, and then assign
frequencies for TRXs, as shown in Figure 7-4.
Figure 7-4
Available TRXs: TRXs that can be assigned to the cell. Each TRX maps a TRX board.
NOTE
Different types of BTSs are assigned different numbers of TRXs.
Frequencies: frequencies that can be assigned to the TRXs. For a non-FH cell, each TRX
is assigned one frequency to process services.
The BSC supports frequency bands GSM900, DSC1800, and GSM900 and DCS1800. Different
frequency bands are in different frequency ranges. Table 7-11 lists the mapping between the
frequency bands and the frequency ranges.
68P02909W07-A
7-37
Aug 2008
TRXs
Table 7-11
Frequency Range
GSM900
0-124, 975-1023
DCS1800
512-885
GSM900&DCS1800
The number of TRXs carried on each E1 port on the Abis interface board as follow:
When the BTS local switching and the Flex Abis mode are not used, each E1 port supports 13 to
15 TRXs. When all the TRXs on the E1 port of the Abis interface work in full-rate mode, each
E1 port carries 15 TRXs.
When all the TRXs on the E1 port of the Abis interface work in half-rate mode, each E1 port
carries 13 TRXs. When the BTS local switching and the Flex Abis mode are used, each E1 port
carries 13 to 18 TRXs. Each E1 port can carry up to 18 TRXs.
7-38
68P02909W07-A
Aug 2008
BTS Topology
This section describes the BTS topologies. The BSC provides flexible BTS topologies on the
Abis interface. These topologies are the star topology, chain topology, tree topology, and ring
topology.
Star Topology
Star topology refers to the topology in which the BTSs connect to the BSC directly. These BTSs
do not have lower-level BTSs. Star topology is a commonly used network topology.
Star topology features simple network structure, convenient capacity expansion, and high
reliability. If a BTS incurs a fault, other BTSs are not affected. Therefore, the star topology is
widely used. However, the transmission resources of the star topology cannot be fully used in
mini BTSs. In this case, the timeslot integration device can be used to optimize the transmission.
Figure 7-5 shows the star topology.
Figure 7-5
Star topology
In star topology, the Abis interface can use the TDM transmission mode. For details on the
relation between the transmission mode and the topology, refer to Transmission and Networking
68P02909W07-A
7-39
Aug 2008
BTS Topology
Chain Topology
In the belt-shaped areas (such as highways) where the traffic volume is low, it is a waste of
transmission resources to use the star topology. In this case, the chain topology can be used.
In the chain topology, a cascaded BTS processes the timeslots of itself and transparently
transmits the timeslots of the lower-level BTSs.
The accuracy of clock signals decreases when the cascades increase. Too many cascades
deteriorate the BTS performance. Therefore, do not use the chain topology with too many
cascades. The chain topology has some disadvantages, such as inconvenient capacity expansion
and low reliability. If the BTS in the middle of the chain incurs a fault, the lower-level BTSs are
affected. Figure 7-6 shows the chain topology.
Figure 7-6
Chain topology
In chain topology, the Abis interface can use the TDM or HDLC transmission mode. For details
on the relation between the transmission mode and the topology, refer to Transmission and
Tree Topology
In the tree topology, the BTS directly connecting to the BSC is the parent BTS. All the children
BTSs connect to the parent BTS. The parent BTS exchanges timeslots with each child BTS. You
can control the timeslot exchange on the LMT.
The tree topology combines the features of star topology and chain topology. Its reliability is
lower than the star topology but higher than the chain topology. The structure of the tree
topology is complicated. Therefore, the capacity expansion and maintenance of the network is
difficult. Figure 7-7 shows the tree topology.
Figure 7-7
Tree topology
In tree topology, the Abis interface can use the TDM or HDLC transmission mode. For details
on the relation between the transmission mode and the topology, refer to Transmission and
7-40
68P02909W07-A
Aug 2008
Ring Topology
Ring topology is a special chain topology. All the BTSs connect with each other to form a normal
chain and the last-level BTS connects with the BSC to form a ring. If the communication of the
ring is broken at a point, the topology of the BTSs before the breakpoint remains the same. After
the breakpoint, the BTSs form a new chain connection in the reverse direction.
Therefore, two chains are formed and the BTSs can still offer services. This improves the
robustness of the system. Figure 7-8 shows the ring topology.
Figure 7-8
Ring topology
In ring topology, the Abis interface can use the TDM transmission mode. For details on the
relation between the transmission mode and the topology, refer to Transmission and Networking
NOTE
The MoTo BTS supports three multiplexing modes: Fix Abis 16k, Fix Abis 64k,
and Flex Abis. The multiplexing ratio in Flex Abis multiplexing mode can be
1:1, 2:1, 4:1, 5:1, or 6:1.
Statistic multiplexing means that n channels use one 64 kbit/s timeslot. Each
channel uses the 64 kbit/s bandwidth in a different time slice, that is, Time
Division Multiplexing (TDM). In statistic multiplexing mode, more than one
channel is multiplexed onto one 64 kbit/s bandwidth.
68P02909W07-A
7-41
Aug 2008
The n:1 statistic multiplexing and physical 16 kbit/s multiplexing cannot coexist on one link.
The OMLs, RSLs, ESLs, idle timeslots, monitoring timeslots, and TCHs are assigned
based on sub-timeslots.
When using the n:1 64 kbit/s statistic multiplexing mode, adhere to the following principles:
The timeslots of different BTSs cannot be multiplexed onto one 64 kbit/s timeslot.
Traffic channels and signaling channels cannot be multiplexed onto one 64 kbit/s
timeslot.
One 64 kbit/s timeslot must be used even if one signaling channel or traffic channel
is configured.
Monitoring timeslots cannot share the same 64 kbit/s timeslot with other timeslots,
except for the semipermanent connection.
In different E1s of cascaded BTSs, all the objects multiplexed onto one 64 kbit/s
timeslot must stay in the same 64 kbit/s timeslot and the relative positions of their
corresponding sub-timeslot numbers must remain the same.
Idle timeslots and the timeslots on TRXs cannot use the same 64 kbit/s bandwidth
with the semipermanent connection.
The number of OMLs for the GEIUB/GOIUB cannot exceed 256.
The number of RSLs for the GEIUB/GOIUB cannot exceed 256.
When use the FIX Abis 64 kbit/s statistic multiplexing mode, adhere to the following
principles:
The idle timeslots and the TCHs cannot be multiplexed. The TCHs carried on different
TRXs cannot be multiplexed onto the same 64 kbit/s channel, and one TRX can occupy
up to two 64 kbit/s channels.
The two RSLs corresponding to the two logical TRXs on the double-transceiver TRX
board must be multiplexed onto one 64 kbit/s channel.
When BTSs, cells, TRXs, idle timeslots, or monitoring timeslots are added, timeslots on the
Abis interface must be assigned. The resources on the Abis interface should be assigned to
the following objects: OMLs, RSLs, channels, idle timeslots, and monitoring timeslots.
7-42
68P02909W07-A
Aug 2008
Each E1 port of the BTS manages sub-timeslots 0255. Sub-timeslots 07 are used for
synchronization. They cannot be assigned to any object.
The OML of a BTS is assigned on timeslot 31. In n:1 statistic multiplexing mode, the OML
is assigned on sub-timeslot 0 of timeslot 31. In physical 16 kbit/s multiplexing mode, the
OML is assigned on sub-timeslot 3 of timeslot 31.
Except for the incoming E1 timeslot, the E1 port directly connected to the BSC is selected
preferentially during the timeslot assignment of the upper-level BTS.
Monitoring timeslots and idle timeslots can be assigned only on the ports of the main
cabinets in the main cabinet groups.
Lower-level BTSs can be established only on the ports of the main cabinets in the main
cabinet groups.
Before the OML between the BTS and the BSC is established, the BTS scans different
timeslots and tries to establish the OML to the BSC. The number of BTS cascades is limited
to reduce the link setup time.
Adding a BTS
Adding a cell
Adding a TRX
Moving a BTS
Blocking a timeslot
68P02909W07-A
7-43
Aug 2008
Assume that there are two cascaded BTSs. Level 1 BTS uses timeslots 4-59 and level 2 BTS uses
timeslots 68-127. Four idle timeslots of level 1 BTS are deleted and timeslots 6, 7, 8, and 9 are
released. A new TRX is added to level 2 BTS. The TRX carries six TCHs. Only two complete
64 kbit/s timeslots and two 32 kbit/s timeslots are available. The RSLs cannot be multiplexed
onto the TCHs and the timeslots of different BTSs cannot be multiplexed. Therefore, timeslot
resources are insufficient.
The LMT displays a dialog box, requesting you to decide whether to allow automatic timeslot
arrangement by the BSC.
If the existing timeslot distribution meets the requirements for BSC automatic
arrangement, the BSC starts to arrange timeslots.
If the existing timeslot distribution does not meet the requirements for BSC automatic
arrangement, add physical E1 links and add the corresponding site chains on the LMT.
Use the following methods to arrange timeslots to meet the requirement of the newly added
TRX for timeslots.
Arrange the timeslots of level 1 BTS. Move the services on timeslots 4 and 5 to timeslots 8
and 9. Therefore, an E1 contains three complete 64 kbit/s timeslots. There are sufficient
timeslot resources to add a TRX.
The RSL of the added TRX can use timeslots 4, 5, 6, and 7. The remaining two complete 64
kbit/s timeslots can be assigned to six TCHs.
Table 7-12 shows the timeslot distribution on the Abis interface before timeslot arrangement by
the BSC.
Table 7-12
by the BSC
Timeslot
0, 1
2, 3
4, 5
6, 7
Synchronization
Synchronization
Synchronization
Synchronization
Idle
Idle
Idle
Idle
...
...
...
...
...
12
13
14
Idle
Idle
Idle
Idle
15
Idle
Idle
Idle
Idle
16
17
...
...
...
...
...
30
31
7-44
68P02909W07-A
Aug 2008
Table 7-13 shows the timeslot distribution on the Abis interface after timeslot arrangement by
the BSC.
Table 7-13
the BSC
Timeslot
0, 1
2, 3
4, 5
6, 7
Synchronization
Synchronization
Synchronization
Synchronization
Idle
Idle
Idle
Idle
...
...
...
...
...
12
13
14
Idle
Idle
Idle
Idle
15
Idle
Idle
Idle
Idle
16
17
...
...
...
...
...
30
31
The BSC releases all the timeslots that are used by the cascaded BTSs except for the
timeslots assigned manually.
The manual assignment of Abis timeslots does not involve timeslot arrangement.
If the timeslot arrangement fails, the timeslot distribution before the timeslot arrangement
is restored.
68P02909W07-A
7-45
Aug 2008
Figure 7-9
The four E1s are A0, A1, and A2, as shown in Figure 7-9. If the multiplexing modes of BTS 0,
BTS 1, and BTS 3 are 1:1, 2:1,and 4:1, then three multiplexing modes exist on the GEIUB. The
multiplexing mode of each E1 on the link where the BTS is located depends on the multiplexing
mode of the BTS itself.
Three multiplexing modes exist on A0. They are 1:1, 2:1,and 4:1.
Two multiplexing modes exist on A1. They are 2:1 and 4:1.
7-46
68P02909W07-A
Aug 2008
NOTE
The timeslot assignment of each multiplexing mode is based on the following
conditions:
The speech rate is 16 kbit/s. Four channels of speech occupy one 64 kbit/s
timeslot on the Abis interface.
For the first TRX, channel 0 (T00C0) is the BCCH and channel 1 (T00C1) is
the SDCCH.
If the BTS multiplexing mode is 5:1 or 6:1, each BTS must be configured with
one ESL.
If the BTS multiplexing mode is 5:1, the OML, ESL, and RSL multiplexing
mode is 1:1:3. If the BTS multiplexing mode is 6:1, the OML, ESL, and RSL
multiplexing mode is 1:1:4. The difference between multiplexing modes 5:1, 6:1,
and 4:1 lies in the multiplexing of RSLs. The BCCH and SDCCH use RSLs, that
is, the timeslots occupied by T00C0 and T00C1 are included in the timeslots
occupied by RSLs. Therefore, the 5:1 and 6:1 multiplexing modes are not listed
in the following tables.
1:1 Multiplexing Mode In the following example, BTS 0 is configured with a cell, the cell is
configured with four TRXs, the channels in the cell use default settings, and the multiplexing
mode is 1:1. Table 7-14 lists the timeslot assignment on the Abis interface.
Table 7-14
Timeslot
No
2, 3
4, 5
6, 7
Synchronization
Synchronization
Synchronization
Synchronization
RSL00
T00C2
T00C3
T00C4
T00C5
T00C6
T00C7
T01C0
T01C1
RSL01
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
T02C0
T02C1
RSL02
T02C2
T02C3
T02C4
T02C5
T02C6
T02C7
T03C0
T03C1
10
RSL03
11
T03C2
T03C3
T03C4
T03C5
12
T03C6
T03C7
...
31
OML0
68P02909W07-A
7-47
Aug 2008
2:1 Multiplexing Mode In the following example, BTS 0 is configured with a cell, the cell is
configured with four TRXs, the channels in the cell use default settings, and the multiplexing
mode is 2:1. Table 7-15 lists the timeslot assignment on the Abis interface.
Table 7-15
Timeslot
No.
2, 3
4, 5
6, 7
Synchronization
Synchronization
Synchronization
Synchronization
T00C2
T00C3
T00C4
T00C5
T00C6
T00C7
T01C0
T01C1
RSL01+RSL02
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
T02C0
T02C1
T02C2
T02C3
T02C4
T02C5
T02C6
T02C7
T03C0
T03C1
RSL03
T03C2
T03C3
T03C4
T03C5
10
T03C6
T03C7
11
...
31
OML0+RSL00
4:1 Multiplexing Mode In the following example, BTS 0 is configured with a cell, the cell is
configured with four TRXs, the channels in the cell use default settings, and the multiplexing
mode is 4:1. Table 7-16 lists the timeslot assignment on the Abis interface.
Table 7-16
Timeslot
No.
0, 1
2, 3
4, 5
6, 7
Synchronization
Synchronization
Synchronization
Synchronization
T00C2
T00C3
T00C4
T00C5
T00C6
T00C7
T01C0
T01C1
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
T02C0
T02C1
T02C2
T02C3
T02C4
T02C5
T02C6
T02C7
T03C0
T03C1
RSL03
T03C2
T03C3
T03C4
T03C5
T03C6
T03C7
Continued
7-48
68P02909W07-A
Aug 2008
Table 7-16
10
...
31
OML0+RSL00+RSL01+RSL02
NOTE
The timeslot assignment of each multiplexing mode is based on the following
conditions:
The speech rate is 16 kbit/s. Four channels of speech occupy one 64 kbit/s
timeslot on the Abis interface.
For the first TRX, channel 0 (T00C0) is the BCCH and channel 1 (T00C1) is
the SDCCH.
The BCCH and the SDCCH use the RSL, that is, the timeslots on the RSL contain
the timeslots on the T00C0 and T00C1. Therefore, T00C0 and T00C1 are not
listed in the following tables.
Figure 7-10
BTS 0 is the root node. Table 7-17 to Table 7-19 show the timeslot assignment on E1s (A0A2) of
BTSs.
68P02909W07-A
7-49
Aug 2008
Table 7-17
Timeslot No.
Timeslot assignment on A0
Sub-Timeslot No.
0, 1
2, 3
4, 5
6, 7
Synchronization
Synchronization
Synchronization
Synchronization
RSL00
T00C2
T00C3
T00C4
T00C5
T00C6
T00C7
T01C0
T01C1
RSL01
T01C2
T01C3
T01C4
T01C5
T01C6
T01C7
OML1+RSL10
T10C2
T10C3
T10C4
T10C5
T10C6
T10C7
T11C0
T11C1
10
RSL11
11
T11C2
T11C3
T11C4
T11C5
12
T11C06
T11C7
13
OML2+RSL20+RSL21
14
T20C2
T20C3
T20C4
T20C5
15
T20C6
T20C7
T21C0
T21C1
16
T21C2
T21C3
T21C4
T21C5
17
T21C6
T21C7
18
OML3+ RSL30+RSL31
19
T30C2
T30C3
T30C4
T30C5
20
T30C6
T30C7
T31C0
T31C1
21
T31C2
T31C3
T31C4
T31C5
22
T31C6
T31C7
23
...
31
OML0
7-50
68P02909W07-A
Aug 2008
Table 7-18
Timeslot assignment on A1
Sub-Timeslot No.
Timeslot
No.
0, 1
2, 3
Synchronization
Synchronization Synchronization
Synchronization
T10C2
T10C3
T10C4
T10C5
T10C6
T10C7
T11C0
T11C1
RSL11
T11C2
T11C3
T11C4
T11C5
T11C6
T11C7
OML3+RSL30 + RSL31
T30C2
T30C3
T30C4
T30C5
T30C6
T30C7
T31C0
T31C1
T31C2
T31C3
T31C4
T31C5
T31C06
T31C7
10
4, 5
6, 7
11
...
31
OML1+ RSL10
Table 7-19
Timeslot No.
Timeslot assignment on A2
Sub-Timeslot No.
0, 1
2, 3
4, 5
6, 7
Synchronization
Synchronization
Synchronization
Synchronization
T30C2
T30C3
T30C4
T30C5
T30C6
T30C7
T31C0
T31C1
T31C2
T31C3
T31C4
T31C5
T31C6
T31C7
5
...
31
OML3+RSL30+RSL31
68P02909W07-A
7-51
Aug 2008
Semipermanent Connection
When manually assigning timeslots on the Abis interface, adhere to the following principles:
The objects that support manual timeslot assignment are OMLs, RSLs, channels, idle
timeslots, and monitoring timeslots.
You can assign timeslots on the Abis interface for multiple objects at a time.
If you manually assign timeslots on the Abis interface for a cascaded BTS, also manually
assign the incoming Abis timeslots for all the cascaded BTSs on the link.
The multiplexing mode of assigned timeslots must be the same as the multiplexing mode
of the BTS. If the BTS uses the 2:1 multiplexing mode, do not multiplex four signaling
links together.
In the incoming E1 and outgoing E1 links of all the cascaded BTSs on a link, all the objects
multiplexed onto one 64 kbit/s timeslot must be located in the same 64 kbit/s timeslot and
all the relative positions of sub-timeslots must remain unchanged. For example, three
objects of a BTS use timeslots 8, 9, and 10 of level-1 BTS and timeslots 4, 5, and 6 of level-2
BTS. When assigning timeslots for another object of the BTS, do not assign timeslot 11 of
level-1 BTS or timeslot 7 of level-2 BTS. You can assign a timeslot of level-1 BTS except for
timeslot 11 and a timeslot of level-2 BTS except for timeslot 7.
When adding BTSs, cells, TRXs, idle timeslots, and monitoring timeslots, you can manually
assign timeslots for only the newly added objects. The timeslots of existing objects cannot
be manually assigned. If you only manually assign timeslots on the Abis interface without
performing other operations, you can assign timeslots for all the objects on the entire link.
When you change the assignment mode of the timeslots of an object from manual mode to
auto mode, the timeslots are released and assigned automatically. When you change the
assignment mode of the timeslots of an object from auto mode to manual mode, the Abis
timeslots automatically assigned for the object are released.
You can manually assign the timeslots on the Abis interface for the BTSs on the same link
in a topology at a time.
Semipermanent Connection
Semipermanent connection refers to the transmission channel comprised of some idle timeslots
in the existing network. The semipermanent connection is used to transfer business hall
information, alarm information about the BTS AC power supply, and other maintenance
information.
When the network operator has to transmit some data from one terminal to another terminal and
the data does not have a high requirement for the transmission bandwidth, the idle transmission
resources in the GSM network can be specially used to transfer the data.
Semipermanent connection is a transparent channel that can be used to transfer information
specified by a subscriber. The BSC provides four types of semipermanent connections: 8 kbit/s,
16 kbit/s, 32 kbit/s, and 64 kbit/s.
7-52
68P02909W07-A
Aug 2008
Monitoring timeslotConnection configured between the interface board and the BTS The
rates of monitoring timeslots are 8 kbit/s, 16 kbit/s, 32 kbit/s, and 64 kbit/s. You can assign
multiple monitoring timeslots for the BTSs on a link at a time.
When you assign idle timeslots for a BTS, you can set the related attribute to manually
assign timeslots on the Abis interface for the newly added idle timeslots.
The idle timeslot configuration consists of addition and deletion of idle timeslots.
You can configure idle timeslots for the BTSs that are on only one link at a time.
68P02909W07-A
Aug 2008
7-53
7-54
68P02909W07-A
Aug 2008
Chapter
8
Appendix: Changes in BSC Initial
Configuration Guide
68P02909W07-A
Aug 2008
8-1
This section describes the changes in the BSC Initial Configuration Guide.
01 (2008-07-21)
This is the initial commercial release.
8-2
68P02909W07-A
Aug 2008