Professional Documents
Culture Documents
BSS12 PDF
BSS12 PDF
COURSE ADMINISTRATION
CHAPTER 2
BTS FUNCTIONALITY
REQUIREMENTS
CHAPTER 3
INTRODUCTION TO
COMMANDS
CHAPTER 4
CUSTOMER MMI COMMAND
EXERCISE
CHAPTER 5
BSC INITIALIZATION
CHAPTER 6
HORIZONMACRO
OPTIMIZATI0N
CHAPTER 7
CUSTOMER BTS
CONFIGURATION EXERCISE
ANNEX A
SUGGESTED
CONFIGURATIONS
GLOSSARY OF TERMS
ISSUE 1 REVISION 0
BSS12
BASE STATION SYSTEMS MMI AND
OPTIMIZATION
FOR TRAINING PURPOSES ONLY
ISSUE 1
REVISION 0
BSS12
BASE STATION
SYSTEMS MMI AND
OPTIMIZATION
FOR TRAINING
PURPOSES ONLY
BSS12
BASE STATION SYSTEMS MMI AND
OPTIMIZATION
ISSUE 1 REVISION 0
BSS12
Base Station Systems MMI and
Optimization
ISSUE 1 REVISION 0
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license
agreement and may be used and/or disclosed only in accordance with the terms of the agreement.
Software and documentation are copyright 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.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola
assumes no liability resulting from any inaccuracies or omissions in this document, or from the use
of the information obtained herein. Motorola 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 does not assume any liability arising out of the application
or use of any product or circuit described herein; neither does it convey license under its patent
rights of others.
Trademarks
ii
ISSUE 1 REVISION 0
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Important notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1
1
2
2
3
3
3
3
4
4
4
5
5
5
5
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specific warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
High voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RF radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Laser radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Lifting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Do not ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Battery supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Toxic material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6
6
6
6
6
6
6
7
7
7
7
8
8
8
8
9
10
10
10
11
11
11
11
12
12
12
12
12
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Caution labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fibre optics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Static discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
13
13
13
13
iii
ISSUE 1 REVISION 0
iv
14
14
14
15
15
15
15
16
16
16
17
17
17
Chapter 1
Course Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
Chapter 2
BTS Functionality Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
22
22
26
26
28
Chapter 3
Introduction to Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
32
32
33
33
33
33
34
34
34
35
35
36
36
37
37
37
38
38
38
ISSUE 1 REVISION 0
39
39
314
318
318
318
319
Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data array location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EAS alarm table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
320
320
320
321
321
Chapter 4
Customer MMI Command Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
41
42
42
MMI Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44
Chapter 5
BSC Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSC Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
51
BSC Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LANLOAD/SYSGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
52
52
SYSGEN mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SYSGEN OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SYSGEN ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database changes in SYSGEN ON mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initial SYSGEN mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SYSGEN safety features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
54
54
55
55
56
56
Chapter 6
Horizonmacro Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
61
62
62
62
63
63
66
66
67
67
68
610
610
ISSUE 1 REVISION 0
vi
612
612
613
614
615
617
617
619
624
625
625
625
626
627
629
632
633
634
634
635
637
638
638
638
638
639
639
640
640
640
640
641
641
642
642
642
643
643
643
644
644
644
644
645
646
Chapter 7
Customer BTS Configuration Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
71
ISSUE 1 REVISION 0
72
72
74
Annex A
Horizonmacro Suggested Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . .
A1
A1
Suggested RF configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of configuration diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for omni 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for omni 1 or 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for omni 3 or 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for omni 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for omni 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for omni 5 or 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for sector 1/1 or 2/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for sector 1/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for single cabinet sector 3/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for 2 cabinet sector 3/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for 2 cabinet sector 4/4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for 2 cabinet sector 5/5 or 6/6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for single cabinet sector 1/1/1, 1/1/2, 1/2/2 or 2/2/2 . . . . . . . . . . . .
Configuration for 2 cabinet sector 2/2/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for 2 cabinet sector 3/3/3 or 4/4/4 . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for 2 cabinet sector 4/4/4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for 3 cabinet sector 4/4/4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for sector 5/5/5 or 6/6/6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for sector 8/8/8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration for dual band 1/1/1-3/3/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A2
A2
A2
A3
A4
A4
A5
A5
A6
A7
A7
A8
A8
A9
A10
A11
A12
A13
A14
A15
A16
A17
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Glos1
A .........................................................................
Glos2
B .........................................................................
Glos5
C .........................................................................
Glos8
D .........................................................................
Glos12
E .........................................................................
Glos15
F .........................................................................
Glos17
G .........................................................................
Glos19
H .........................................................................
Glos21
I ..........................................................................
Glos22
K .........................................................................
Glos24
L .........................................................................
Glos25
M .........................................................................
Glos27
N .........................................................................
Glos31
O .........................................................................
Glos33
vii
ISSUE 1 REVISION 0
viii
P .........................................................................
Glos35
Q .........................................................................
Glos38
R .........................................................................
Glos39
S .........................................................................
Glos42
T .........................................................................
Glos46
U .........................................................................
Glos49
V .........................................................................
Glos50
W ........................................................................
Glos51
X .........................................................................
Glos52
Z .........................................................................
Glos53
General information
ISSUE 1 REVISION 0
General information
Important notice
If this manual was obtained when you attended a Motorola training course, it will not be
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 corrections will be supplied automatically by Motorola in the form of
General Manual Revisions (GMRs).
Purpose
Motorola Global System for Mobile Communications (GSM) Technical Education manuals
are intended to support the delivery of Technical Education only and are not intended to
replace the use of Customer Product Documentation.
WARNING
Failure to comply with Motorolas operation, installation and maintenance
instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by
Motorola, although they can be used to supplement and enhance the knowledge gained
through such training.
ISSUE 1 REVISION 0
General information
Cross references
Throughout this manual, cross references are made to the chapter numbers and section
names. The section name cross references are printed bold in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, 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.
Text conventions
The following conventions are used in the Motorola GSM manuals to represent keyboard
input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
CTRL-c
ALT-f
CR or RETURN
ISSUE 1 REVISION 0
Artificial
respiration
In the event of an electric shock it may be necessary to carry out artificial respiration.
Send for medical assistance immediately.
Burns treatment
If the patient is also suffering from burns, then, without hindrance to artificial respiration,
carry out the following:
1.
2.
3.
ISSUE 1 REVISION 0
Procedure
Whenever a safety issue arises:
1.
2.
3.
Report the problem directly to GSM MCSC +44 (0)1793 430040 (telephone) and
follow up with a written report by fax +44 (0)1793 430987 (fax).
4.
Collect evidence from the equipment under the guidance of the MCSC.
ISSUE 1 REVISION 0
Warnings
Definition
A warning is used to alert the reader to possible hazards that could cause loss of life,
physical injury, or ill health. This includes hazards introduced during maintenance, for
example, the use of adhesives and solvents, as well as those inherent in the equipment.
Cautions
Definition
A caution means that there is a possibility of damage to systems, or individual items of
equipment within a system. However, this presents no danger to personnel.
ISSUE 1 REVISION 0
General warnings
General warnings
Introduction
Observe the following warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola GSM manuals. Failure to
comply with these warnings, or with specific warnings elsewhere in the Motorola GSM
manuals, violates safety standards of design, manufacture and intended use of the
equipment. Motorola assumes no liability for the customers failure to comply with these
requirements.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning
labels fitted to the equipment. Warning labels must not be removed, painted over or
obscured in any way.
Specific
warnings
Warnings particularly applicable to the equipment are positioned on the equipment and
within the text of this manual. These must be observed by all personnel at all times when
working with the equipment, as must any other warnings given in text, on the illustrations
and on the equipment.
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single
phase or 415 V ac three phase mains which is potentially lethal. Therefore, the areas
where the ac mains power is present must not be approached until the warnings and
cautions in the text and on the equipment have been complied with.
To achieve isolation of the equipment from the ac supply, the mains input isolator must
be set to off and locked.
Within the United Kingdom (UK) regard must be paid to the requirements of the
Electricity at Work Regulations 1989. There may also be specific country legislation
which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment
when in operation. Ensure that all transmitters are switched off when any antenna
connections have to be changed. Do not key transmitters connected to unterminated
cavities or feeders.
Refer to the following standards:
S
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated fibre optic
cables connected to data in/out connectors.
6
General warnings
ISSUE 1 REVISION 0
Lifting
equipment
When dismantling heavy assemblies, or removing or replacing equipment, the competent
responsible person must ensure that adequate lifting facilities are available. Where
provided, lifting frames must be used for these operations. When equipments have to be
manhandled, reference must be made to the Manual Handling of Loads Regulations
1992 (UK) or to the relevant manual handling of loads legislation for the country in which
the equipment is used.
Do not ...
... substitute parts or modify equipment.
Because of the danger of introducing additional hazards, do not install substitute parts or
perform any unauthorized modification of equipment. Contact Motorola if in doubt to
ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with standby battery supplies.
Toxic material
Certain Motorola equipment incorporates components containing the highly toxic material
Beryllium or its oxide Beryllia or both. These materials are especially hazardous if:
S
Beryllium materials are absorbed into the body tissues through the skin, mouth, or
a wound.
See the Beryllium health and safety precautions section for further information.
ISSUE 1 REVISION 0
Definitions
This standard establishes two sets of maximum permitted exposure limits, one for
controlled environments and another, that allows less exposure, for uncontrolled
environments. These terms are defined by the standard, as follows:
Uncontrolled environment
Uncontrolled environments are locations where there is the exposure of individuals who
have no knowledge or control of their exposure. The exposures may occur in living
quarters or workplaces where there are no expectations that the exposure levels may
exceed those shown for uncontrolled environments in the table of maximum permitted
exposure ceilings.
Controlled environment
Controlled environments are locations where there is exposure that may be incurred by
persons who are aware of the potential for exposure as a concomitant of employment, by
other cognizant persons, or as the incidental result of transient passage through areas
where analysis shows the exposure levels may be above those shown for uncontrolled
environments but do not exceed the values shown for controlled environments in the
table of maximum permitted exposure ceilings.
Maximum
permitted
exposures
The maximum permitted exposures prescribed by the standard are set in terms of
different parameters of effects, depending on the frequency generated by the equipment
in question. At the frequency range of this Personal Communication System equipment,
1930-1970MHz, the maximum permitted exposure levels are set in terms of power
density, whose definition and relationship to electric field and magnetic field strengths are
described by the standard as follows:
H2
where E and H are expressed in units of V/m and A/m, respectively, and S in units of
W/m 2. Although many survey instruments indicate power density units, the actual
quantities measured are E or E2 or H or H2.
ISSUE 1 REVISION 0
Maximum
permitted
exposure
ceilings
Within the frequency range, the maximum permitted exposure ceiling for uncontrolled
environments is a power density (mW/cm2) that equals f/1500, where f is the frequency
expressed in MHz, and measurements are averaged over a period of 30 minutes. The
maximum permitted exposure ceiling for controlled environments, also expressed in
mW/cm 2, is f/300 where measurements are averaged over 6 minutes. Applying these
principles to the minimum and maximum frequencies for which this equipment is intended
to be used yields the following maximum permitted exposure levels:
Uncontrolled Environment
1930MHz
Ceiling
1970MHz
Controlled Environment
1930MHz
1970MHz
If you plan to operate the equipment at more than one frequency, compliance should be
assured at the frequency which produces the lowest exposure ceiling (among the
frequencies at which operation will occur).
Licensees must be able to certify to the FCC that their facilities meet the above ceilings.
Some lower power PCS devices, 100 milliwatts or less, are excluded from demonstrating
compliance, but this equipment operates at power levels orders of magnitude higher, and
the exclusion is not applicable.
Whether a given installation meets the maximum permitted exposure ceilings depends, in
part, upon antenna type, antenna placement and the output power to which this
equipment is adjusted. The following example sets forth the distances from the antenna
to which access should be prevented in order to comply with the uncontrolled and
controlled environment exposure limits as set forth in the ANSI IEEE standards and
computed above.
ISSUE 1 REVISION 0
Example
calculation
For a base station with the following characteristics, what is the minimum distance from
the antenna necessary to meet the requirements of an uncontrolled environment?
Transmit frequency
1930MHz
2.0dB
Antenna gain, G
16.4dBi (43.65)
Where W is the maximum permissible power density in W/m2 and r is the safe distance
from the antenna in metres, the desired distance can be calculated as follows:
r+
GPin
+ 43.65 5 + 1.16m
4pW
4p 12.87
where W = 12.87 W/m2 was obtained from table listed above and converting from
mW/cm 2 to W/m2.
NOTE
The above result applies only in the direction of maximum radiation of the
antenna. Actual installations may employ antennas that have defined radiation
patterns and gains that differ from the example set forth above. The distances
calculated can vary depending on the actual antenna pattern and gain.
Power density
measurements
While installation calculations such as the above are useful and essential in planning and
design, validation that the operating facility using this equipment actually complies will
require making power density measurements. For information on measuring RF fields for
determining compliance with ANSI IEEE C95.1-1991, see IEEE Recommended Practice
for the Measure of Potentially Hazardous Electromagnetic Fields - RF and Microwave,
IEEE Std C95.3-1991. Copies of IEEE C95.1-1991 and IEEE C95.3-1991 may be
purchased from the Institute of Electrical and Electronics Engineers, Inc., Attn:
Publication Sales, 445 Hoes Lane, P.O. Box 1331, Piscattaway, NJ 08855-1331,
(800) 678-IEEE or from ANSI, (212) 642-4900. Persons responsible for installation of this
equipment are urged to consult these standards in determining whether a given
installation complies with the applicable limits.
Other equipment
Whether a given installation meets ANSI standards for human exposure to radio
frequency radiation may depend not only on this equipment but also on whether the
environments being assessed are being affected by radio frequency fields from other
equipment, the effects of which may add to the level of exposure. Accordingly, the overall
exposure may be affected by radio frequency generating facilities that exist at the time
the licensees equipment is being installed or even by equipment installed later.
Therefore, the effects of any such facilities must be considered in site selection and in
determining whether a particular installation meets the FCC requirements.
10
ISSUE 1 REVISION 0
Health issues
Beryllium Oxide is used within some components as an electrical insulator. Captive
within the component it presents no health risk whatsoever. However, if the component
should be broken open and the Beryllium Oxide, which is in the form of dust, released,
there exists the potential for harm.
Inhalation
Inhalation of Beryllium Oxide can lead to a condition known as Berylliosis, the symptoms
of Berylliosis are similar to Pneumonia and may be identified by all or any of the
following:
Mild poisoning causes fever, shortness of breath, and a cough that produces
yellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucous
membranes of the nose, throat, and chest with discomfort, possibly pain, and difficulty
with swallowing and breathing.
Severe poisoning causes chest pain and wheezing which may progress to severe
shortness of breath due to congestion of the lungs. Incubation period for lung symptoms
is 220 days.
Exposure to moderately high concentrations of Beryllium in air may produce a very
serious condition of the lungs. The injured person may become blue, feverish with rapid
breathing and raised pulse rate. Recovery is usual but may take several months. There
have been deaths in the acute stage.
Chronic response. This condition is more truly a general one although the lungs are
mainly affected. There may be lesions in the kidneys and the skin. Certain features
support the view that the condition is allergic. There is no relationship between the
degree of exposure and the severity of response and there is usually a time lag of up to
10 years between exposure and the onset of the illness. Both sexes are equally
susceptible. The onset of the illness is insidious but only a small number of exposed
persons develop this reaction.
First aid
Seek immediate medical assistance. The casualty should be removed immediately from
the exposure area and placed in a fresh air environment with breathing supported with
Oxygen where required. Any contaminated clothing should be removed. The casualty
should be kept warm and at rest until medical aid arrives.
11
ISSUE 1 REVISION 0
Skin contact
Possible irritation and redness at the contact area. Persistent itching and blister
formations can occur which usually resolve on removal from exposure.
First aid
Wash area thoroughly with soap and water. If skin is broken seek immediate medical
assistance.
Eye contact
May cause severe irritation, redness and swelling of eyelid(s) and inflammation of the
mucous membranes of the eyes.
First aid
Flush eyes with running water for at least 15 minutes. Seek medical assistance as soon
as possible.
Handling
procedures
Removal of components from printed circuit boards (PCBs) is to take place only at
Motorola approved repair centres.
The removal station will be equipped with extraction equipment and all other protective
equipment necessary for the safe removal of components containing Beryllium Oxide.
If during removal a component is accidently opened, the Beryllium Oxide dust is to be
wetted into a paste and put into a container with a spatula or similar tool. The
spatula/tool used to collect the paste is also to be placed in the container. The container
is then to be sealed and labelled. A suitable respirator is to be worn at all times during
this operation.
Components which are successfully removed are to be placed in a separate bag, sealed
and labelled.
Disposal
methods
Beryllium Oxide or components containing Beryllium Oxide are to be treated as
hazardous waste. All components must be removed where possible from boards and put
into sealed bags labelled Beryllium Oxide components. These bags must be given to the
safety and environmental adviser for disposal.
Under no circumstances are boards or components containing Beryllium Oxide to be put
into the general waste skips or incinerated.
General cautions
ISSUE 1 REVISION 0
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the
equipment described in the Motorola GSM manuals. Failure to comply with these
cautions or with specific cautions elsewhere in the Motorola GSM manuals may result in
damage to the equipment. Motorola assumes no liability for the customers failure to
comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution
labels fitted to the equipment. Caution labels must not be removed, painted over or
obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this
manual. These must be observed by all personnel at all times when working with the
equipment, as must any other cautions given in text, on the illustrations and on the
equipment.
Fibre optics
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge.
Although the damage caused by static discharge may not be immediately apparent,
CMOS devices may be damaged in the long term due to static discharge caused by
mishandling. Wear an approved earth strap when adjusting or handling digital boards.
See Devices sensitive to static for further information.
13
ISSUE 1 REVISION 0
Special handling
techniques
In the event of one of these devices having to be replaced observe the following
precautions when handling the replacement:
S
Always wear an earth strap which must be connected to the electrostatic point
(ESP) on the equipment.
Leave the short circuit on the leads until the last moment. It may be necessary to
replace the conductive foam by a piece of wire to enable the device to be fitted.
Do not wear outer clothing made of nylon or similar man made material. A cotton
overall is preferable.
If possible work on an earthed metal surface. Wipe insulated plastic work surfaces
with an anti-static cloth before starting the operation.
All metal tools should be used and when not in use they should be placed on an
earthed surface.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less
susceptible to electrostatic damage. However PCBs should be handled with care,
preferably by their edges and not by their tracks and pins, they should be transferred
directly from their packing to the equipment (or the other way around) and never left
exposed on the workbench.
14
ISSUE 1 REVISION 0
Generic manuals
The following are the generic manuals in the GSM manual set, these manuals are
release dependent:
Category
number
Name
Catalogue
number
GSM-100-101
68P02901W01
GSM-100-201
GSM-100-311
GSM-100-313
GSM-100-320
68P02901W36
GSM-100-321
68P02901W23
GSM-100-403
68P02901W17
GSM-100-423
68P02901W43
GSM-100-501
68P02901W26
GSM-100-521
68P02901W57
GSM-100-523
68P02901W51
GSM-100-503
68P02901W56
GSM-100-721
68P02901W72
68P02901W31
Tandem OMC
The following Tandem OMC manuals are part of the GSM manual set for systems
deploying Tandem S300 and 1475:
Category
number
Name
Catalogue
number
GSM-100-202
68P02901W13
GSM-100-712
68P02901W71
15
ISSUE 1 REVISION 0
Scaleable OMC
The following Scaleable OMC manuals replace the equivalent Tandem OMC manuals in
the GSM manual set:
Category
number
Name
Catalogue
number
GSM-100-202
GSM-100-413
68P02901W47
GSM-100-712
68P02901W74
Related manuals
The following are related Motorola GSM manuals:
Category
number
Name
Catalogue
number
GSM-001-103
68P02900W21
GSM-002-103
68P02900W22
GSM-005-103
68P02900W25
GSM-008-403
68P02900W36
Service manuals
The following are the service manuals in the GSM manual set, these manuals are not
release dependent. The internal organization and makeup of service manual sets may
vary, they may consist of from one to four separate manuals, but they can all be ordered
using the overall catalogue number shown below:
Category
number
16
Name
Catalogue
number
GSM-100-020
68P02901W37
GSM-100-030
68P02901W38
GSM-105-020
68P02901W75
GSM-106-020
68P02901W85
GSM-201-020
68P02901W95
GSM-202-020
68P02901W65
GSM-101-SERIES
68P02900W50
GSM-103-SERIES
68P02900W70
GSM-102-SERIES
68P02901W80
GSM-200-SERIES
68P02901W90
ISSUE 1 REVISION 0
Category number
The category number is used to identify the type and level of a manual. For example,
manuals with the category number GSM-100-2xx contain operating information.
Catalogue
number
The Motorola 68P catalogue number is used to order manuals.
Ordering
manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or
Representative. Manuals are ordered using the catalogue number. Remember, specify
the manual issue required by quoting the correct suffix letter.
17
ISSUE 1 REVISION 0
18
Chapter 1
Course Administration
ISSUE 1 REVISION 0
ii
ISSUE 1 REVISION 0
Chapter 1
Course Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
iii
ISSUE 1 REVISION 0
iv
Chapter Objectives
ISSUE 1 REVISION 0
Chapter Objectives
On completion of this chapter the student should be able to:
S
11
ISSUE 1 REVISION 0
Course Introduction
Course Introduction
Facility Entry and exit:
Control of movement whilst attending the Motorola training facility at Europark is by the
use of the pac tag system. A pac tag will be issued daily upon signing in at the front
security reception desk.
Fire Drill:
In the event of the fire alarm sounding all students are to proceed as instructed and
assemble at the front of the building, outside reception, on the grass verge.
Fire exit points/routes are displayed in reception and at the entrance of the classroom
corridor. Students are advised to familiarise themselves with this information.
Participant List:
All students are to complete the participant list as indicated. Correct spelling of the
students name is essential, it is from this form that the name of the student will be taken
for inclusion on the end of course certificate.
Name Cards:
All students are to complete the name card found at the front of their course manuals,
and place it in a prominent position on their desk.
Toilets:
Toilets are located through the door at the base of the stairs to the rear of the front
security desk. Alternative toilets are at the top of the stairs behind the front security
desk.
Smoke Room:
The designated smoking room is located in the vicinity of the ground floor toilets through
the pac tag controlled door. Other than this location smoking is allowed nowhere on
Motorola premises. Students who wish to smoke outside must do so beyond the
perimeter fence.
Course Introduction
ISSUE 1 REVISION 0
Mobile Phones:
Mobile phones are to be turned to silent (vibrate) mode, or switched off during lessons. If
a student has to make or receive a call they must leave the room to do so.
Student Badge:
A student badge will be issued on a daily basis whilst the student is attending a course at
Motorola. The front security desk at Europark main entrance reception will issue the
student badge.
The issued badge entitles the holder to:
S
Free hot drinks from the restaurant vending machines throughout the day.
Course Brochure:
A course brochure advertising all courses run by Motorola, Technical Education and
Documentation, is available on request.
Prerequisites:
All students attending this course should have attended CP02 Introduction to Digital
Cellular.
Course Assessment:
The assessment paper, which is to be undertaken at the end of the course, is for
Motorola evaluation purposes only. Certificates will be issued regardless of the
assessment mark obtained.
13
ISSUE 1 REVISION 0
Course Introduction
14
Chapter 2
ISSUE 1 REVISION 0
ii
ISSUE 1 REVISION 0
Chapter 2
BTS Functionality Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
22
22
26
26
28
iii
ISSUE 1 REVISION 0
iv
ISSUE 1 REVISION 0
21
ISSUE 1 REVISION 0
RX/TX Modules
These provide the modulation/demodulation and the amplification of the downlink to the
MS and uplink from the MS. It also provides the raw data to measure the signal strength
and quality of the two-way link.
Static Switch
This section switches the channels containing traffic from the radio sections of the BTS
to the terrestrial connections section, thus connecting the air interface channel with the
rest of the network and eventually to another party. The static switch also routes any
control information sent from entities further up in the network to the correct controlling
software, usually the resident on the control processor. The static switch means that
once it has been initialized it will keep the switching matrix the same all the time, thus
keeping the same connections routed through.
Terrestrial Interface
The terrestrial interface provides the necessary connection to the network via a suitable
link. This interface provides the correct formatting and impedance matching to the
relevant physical link. The most common link types are 2.048Mbit/s E1 link or
1.544Mbit/s T1 link.
22
ISSUE 1 REVISION 0
Functions of a BTS
S ynchronizing
clock
S ite
Control
GS M Call
Processing
GS M
Timeslot
Monitoring
Control
Processor
Terrestrial
Interface
Terrestrial
Interface
Static Switch
GS M Control S oftware
GS M Control S oftware
RX/TX Modules
RX/TX Modules
BSS11_Ch4_01
23
ISSUE 1 REVISION 0
Control Processor
The control processor is the main processor of the site and can really be split into three
main areas:
S
Site Control
This section is in control of the main processes and hardware to maintain the site
integrity. The main functions include internal data bus control and initialization of
the site at power up as well as reporting any faults or operational problems back to
the controlling BSC further up in the network.
Synchronizing clock
As all the above processes need specific and accurate timing signals, each BTS will be
equipped with a clock to make sure everything is synchronized.
24
ISSUE 1 REVISION 0
25
ISSUE 1 REVISION 0
26
ISSUE 1 REVISION 0
0
1
SYNC
RSL
To synchronize link
and provide error protection
2
To provide a signalling
link from BSC to BTS
3
E1 = 32 x 64 kbit/s
28
RTF1
29
RTF1
30
RTF0
31
RTF0
BSS11_Ch4_02
27
ISSUE 1 REVISION 0
28
ISSUE 1 REVISION 0
BTS1
BSC
0
BTS2
BTS3
0
SYNC
RSL3
RTF2
30
RTF3
RTF2
31
RTF3
SYNC
RSL1
RSL2
24
RTF3
25
RTF3
26
RSL3
27
RTF2
27
RTF3
28
RTF2
28
RTF3
29
RSL2
29
RSL3
30
RTF1
30
31
RTF1
31
SYNC
BSS11_Ch4_03
29
210
ISSUE 1 REVISION 0
Chapter 3
Introduction to Commands
ISSUE 1 REVISION 0
ii
ISSUE 1 REVISION 0
Chapter 3
Introduction to Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
31
32
32
33
33
33
33
34
34
34
35
35
36
36
37
37
37
38
38
38
39
39
314
318
318
318
319
Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data array location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EAS alarm table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
320
320
320
321
321
iii
ISSUE 1 REVISION 0
iv
Introduction to Commands
ISSUE 1 REVISION 0
Introduction to Commands
Chapter
Objectives
On completion of this chapter the student should be able to:
S
31
ISSUE 1 REVISION 0
Network Management
32
ISSUE 1 REVISION 0
BSS initialization
process
The Initialization Process (IP) may load code from three sources:
S
GPROC.
Upon initialization, code is loaded on the BSS. Initialization occurs when the BSS is
reset, the existing code is damaged, or a new version of code exists.
Security
management
Passwords are required to access the system. These ensure that only authorized
persons have access, and establishes a system/command permissions level
commensurate with the person.
If an incorrect password is entered, access to a security level is denied. Also, passwords
may be changed in accordance with the parameters shown in the chg_level and
chg_password command descriptions.
Fault
management
Fault Management commands are used to display and modify the administrative state of
devices or functions. Alarms are one example of this type of control.
Configuration
management
Configuration Management commands are used to:
S
33
ISSUE 1 REVISION 0
Call Processing
(CP)
Call Processing (CP) commands are used to trace the progress of a specified call, via
random trace, either by call rate, or SCCP connection number. The total data resulting
from the call progress events can be collected for later analysis.
Central statistics
processing
Statistics commands are used to:
S
Enable/Disable statistics.
Miscellaneous
commands
Miscellaneous commands are those that do not conveniently fit into the categories
already outlined. These commands are used to:
34
Perform miscellaneous procedures, such as displaying the DTE link address, ROM
checksum, and so on.
ISSUE 1 REVISION 0
Level 1
This level permits the display of system parameters. Access is restricted primarily to
system monitoring commands.
Level 2
This level permits access to all system commands, including the ability to change the
system database.
This security level also permits the operator to change passwords for both Level 1 and
Level 2 users.
Level 3
This level provides all of the features accessible in security Level 2 plus the executive
monitor. Two passwords are used to access security Level 3.
The passwords for this level may not be changed unless the Optional Level 3 Password
Feature is purchased. This feature will enhance BSS security by allowing the Level 3
passwords to be changed in the event the Level 3 passwords are compromised.
35
ISSUE 1 REVISION 0
Type A
No special user action is required to enter a Type A command or change a Type A
database parameter.
Type B
The operator is required to perform one or more actions when entering a Type B
command or changing a Type B database parameter. Operator actions may be required
before or after the command entry or database change.
Specific required actions are listed in the Operator actions section of each command and
database parameter description.
36
ISSUE 1 REVISION 0
Command syntax
The following guidelines must be followed when entering MMI commands.
S
Command names are case sensitive, and may not be entered as mixed upper
and lower case characters in a command string. Where there are exceptions to
this rule, this is made clear in the text.
Example
BSS PROMPT>add_rtf_path
MMI command
The following demonstrates how MMI command examples are represented in this
manual:
chg_element bsic 1 0 5 4 3 2 1 61986 34944
Where:
bsic
is:
element_name
value
location
5 4 3 2 1 61986 34944
cell_desc
System response
COMMAND ACCEPTED
37
ISSUE 1 REVISION 0
Timeouts
If a response is not entered within 60 seconds, the command or response will be
rejected. The following message is presented if a response is not entered within 60
seconds:
COMMAND REJECTED: No response to prompt.
Ambiguous
command
response
If the command name is entered incorrectly, the system will respond with a message
stating that the entered command was ambiguous and will include a listing of commands
with similar command names.
Example:
MMIRAM 0115 > disp_rtf
disp_rtf: Command ambiguous with:
disp_rtf_calls disp_rtf_channel disp_rtf_path
Entering
hexadecimal
values
Some fields will accept hexadecimal values. If hexadecimal (hex) values are used:
S
For example, the hexadecimal value for 255 is ff. To enter the hexadecimal value for
255, type:
0ffh
38
ISSUE 1 REVISION 0
MMI
ROM
Locations Allowed
BSC
BTS
add_bss_conn
add_cell
add_channel
add_link
add_neighbor
add_rtf_path
alias
assess
cage_audit
cell_name
chg_a5_alg_pr
chg_act_alg_data
chg_audit_sched
chg_cell_element
chg_cell_id
chg_csfp
chg_dte
chg_eas_alarm
chg_eas_report
chg_element
X
chg_hdsl_settings
X
chg_hop_params
chg_hopping
chg_ksw_config
chg_level
RXCDR
chg_password
chg_rtf_freq
chg_severity
chg_smscb_msg
X
X
X
X
39
ISSUE 1 REVISION 0
Command
MMI
ROM
Locations Allowed
BSC
BTS
chg_stat_prop
chg_throttle
chg_ts_usage
chg_time
chg_x25config
X
X
X
clear_cal_data
clear_database
clear_gclk_avgs
clear_stats
configure_csfp
copy_cell
copy_path
del_act_alarm
del_bss_conn
del_cell
X
X
del_channel
del_link
del_neighbor
del_nsvc
del_rtf_path
del_smscb_msg
device_audit
disable_alarm
disp_a5_alg_pr
disp_act_alarm
disp_alarm_sites
disp_bss
disp_bss_conn
disp_cal_data
disp_cbch_state
disp_cell
disp_cell_status
disp_channel
310
RXCDR
disp_csfp
disp_csfp_status
disp_dte
ISSUE 1 REVISION 0
Command
MMI
ROM
Locations Allowed
BSC
BTS
RXCDR
disp_enable_stat
disp_equipment
disp_flash
disp_gsm_cells
disp_gclk_avgs
disp_gclk_cal
disp_hdlc
disp_hopping
disp_interval
disp_level
disp_element
X
disp_hdsl_settings
X
disp_link
disp_link_usage
disp_mms_ts_usage
disp_neighbor
disp_nsvc
disp_options
disp_processor
disp_relay_contact
disp_rtf_channel
disp_rtf_path
disp_severity
disp_site
disp_stats
disp_stat_prop
disp_throttle
disp_time
disp_trace_call
disp_traffic
disp_version
disp_x25config
X
download_ltu
X
X
enable_alarm
equip
freq_types_allowed
X
X
311
ISSUE 1 REVISION 0
Command
MMI
ROM
Locations Allowed
BSC
gclk_cal_mode
BTS
X
help
history
ins_device
lock_device
man
map_eas_opto
mod_bss_conn
mod_nsvc
modify_neighbor
modify_value
page
query_audits
reassign
reattempt_pl
reset_device
reset_ltu
reset_site
set_full_power
set_relay_contact
shutdown_device
site_audit
soft_reset
stat_mode
state
status_mode
store_cal_data
sysgen_mode
swap_devices
swfm_enable
time_stamp
trace_call
trace_stop
unalias
set_site
tcu_clock
312
RXCDR
X
X
ISSUE 1 REVISION 0
Command
MMI
ROM
Locations Allowed
BSC
BTS
RXCDR
unconfigure_csfp
unequip
unlock_device
These commands are not available for MMI ROM processes running on TCU
boards. Also note that these commands do not accept the location or cell parameters
used in the ram version of these commands.
These commands are only available for MMI ROM processes running on MCU
boards.
These commands are only available for MMI ROM processes running on TCU boards.
These commands are only available for MMI ROM processes running on GPROC
boards.
313
ISSUE 1 REVISION 0
Command
availability by
SYSGEN mode
Table 3-2 shows the availability of commands in the various SYSGEN modes.
Table 3-2 Summary of MMI command availability (2)
Command
314
SYSGEN
MODE
ON
CM
READY
SITE
READY
add_bss_conn
add_cell
add_channel
add_link
add_neighbor
add_rtf_path
alias
assess
cage_audit
cell_name
chg_a5_alg_pr
chg_act_alg_data
chg_audit_sched
chg_cell_element
chg_cell_id
chg_csfp
chg_dte
chg_eas_alarm
chg_eas_report
chg_element
chg_hop_params
chg_hopping
chg_ksw_config
chg_level
chg_password
chg_rtf_freq
chg_severity
chg_smscb_msg
chg_stat_prop
chg_throttle
chg_ts_usage
X
X
ISSUE 1 REVISION 0
Command
SYSGEN
MODE
ON
CM
READY
chg_time
chg_x25config
clear_cal_data
clear_database
X
X
clear_gclk_avgs
clear_stats
configure_csfp
copy_cell
copy_path
del_act_alarm
del_bss_conn
del_cell
del_channel
del_link
del_neighbor
del_nsvc
del_rtf_path
del_smscb_msg
device_audit
disable_alarm
disp_a5_alg_pr
disp_act_alarm
disp_alarm_sites
X
X
disp_bss
disp_bss_conn
disp_cal_data
X
X
disp_cbch_state
disp_cell
X
X
disp_cell_status
X
X
disp_channel
disp_csfp
disp_csfp_status
SITE
READY
disp_dte
disp_element
disp_enable_stat
315
ISSUE 1 REVISION 0
Command
SYSGEN
MODE
ON
CM
READY
SITE
READY
disp_equipment
disp_flash
disp_gsm_cells
disp_gclk_avgs
disp_gclk_cal
disp_hdlc
disp_hopping
disp_interval
disp_level
disp_link
disp_link_usage
disp_mms_ts_usage
disp_neighbor
disp_nsvc
disp_options
X
X
X
X
disp_processor
disp_relay_contact
disp_rtf_channel
disp_rtf_path
disp_severity
disp_site
disp_stats
X
X
disp_stat_prop
disp_throttle
disp_time
disp_trace_call
disp_traffic
X
X
disp_version
disp_x25config
download_ltu
enable_alarm
equip
freq_types_allowed
gclk_cal_mode
help
316
X
X
ISSUE 1 REVISION 0
Command
history
SYSGEN
MODE
ON
X
CM
READY
SITE
READY
ins_device
lock_device
man
map_eas_opto
mod_bss_conn
mod_nsvc
modify_neighbor
modify_value
page
query_audits
X
X
reassign
reattempt_pl
reset_device
reset_ltu
reset_site
set_full_power
set_relay_contact
shutdown_device
site_audit
soft_reset
stat_mode
state
status_mode
store_cal_data
sysgen_mode
X
X
swap_devices
X
X
swfm_enable
time_stamp
X
X
trace_call
trace_stop
unalias
unconfigure_csfp
unequip
unlock_device
X
X
317
ISSUE 1 REVISION 0
61986 (F222h)
34944 (8880h)
543
is:
MCC
21
MNC
61986
LAC
34944
CI
NOTE
The LAC and CI values may also be displayed as hexadecimal values in
parentheses, depending on the command.
Input format
There are two types of input format that can be used. The format is set with the
mmi_cell_id_format parameter. The different formats accept seven elements or four
elements.
Seven-element format
The system uses the seven-element format when mmi_cell_id_format parameter=0.
cell=5 4 3 2 1
Where:
61986
is:
34944
61986
LAC
34944
CI
This format cannot be used if the optional third MNC digit is necessary. It cannot
be used in PCS1900 systems. It is valid for PGSM, EGSM and DCS 1800
systems.
318
ISSUE 1 REVISION 0
Four-element format
The system uses the four-element format when mmi_cell_id_format parameter=1.
cell=543 021 61986 34944
Where:
is:
61986
LAC
34944
CI
This format must be used if the optional third MNC digit is necessary. It must be
used in PCS1900 systems. It may be used for PGSM, EGSM and DCS 1800
systems.
If the first and/or second digit of the MCC is a zero, it may be omitted from the input.
The system would recognize either of these examples as being in valid format:
001 011 98765 54321
1 011 98765 54321
NOTE
If the third MNC digit is required, all three MNC digits must be entered. For
example, if the MNC = 001, and the third MNC digit is required, the MNC must
be entered as 001. If the MNC is entered as 01 or 1, the system will interpret
the entry as MNC=01, which would be incorrect.
Cell name
Each GSM cell may also be assigned a cell name using the cell_name command. The
cell_name may be used in place of the GSM cell id in most of the BSS MMI commands.
Refer to the individual command descriptions to determine if the cell_name may be used
for a specific command.
319
ISSUE 1 REVISION 0
Indexes
Indexes
Device indexes
Device indexes are used with the disp_element command for displaying information
associated with the System Audit Process (SAP).
Device Type
Index
KSW
KSW
DRI
GCLK
GPROC
BSP
12
BTP
14
DHP
16
SITE
18
TDM
20
Data array
location
An index is used to identify the location of information in a data array.
Indexes
ISSUE 1 REVISION 0
Bins
A single row of a data array may be referred to as a bin. When a command uses bin
numbers to specify the row in a data array, the index number will specify the position of
the data element in the bin.
The following represents an array with four bins with 32 elements in each bin:
bin 0 [0
bin 1 [0
bin 2 [0
bin 3 [0
1
1
1
1
2 ...
2 ...
2 ...
2 ...
31]
31]
31]
31]
The following example shows the command string that would be used to assign or
change the value of the rxlev_ul_ho parameter. The value of the parameter is located in
the first column (index = 0) of the second bin (bin_num = 1)
chg_act_alg_data rxlev_ul_ho 2 6 2 0 2 2868 3100 1 0 8,0
bin_num
index
The following example shows the command string that would be used to display the
contents of a bin. The index value used with the disp_element command is the bin
number that was used when assigning or changing the value of one of the elements of
the parameter.
disp_element rxlev_dl_ho,1 0 cell_number=2 6 2 0 2 2868 3100
rxlev_dl_ho = alg_num: 1 alg_data: 8 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0
Thresholds
Gauge and some counter statistics may be assigned thresholds. An alarm is sent to the
OMCR when the threshold is exceeded. The severity of the alarm associated with a
statistical parameter may be displayed using the disp_element command using an index
value of 1. For example, the command string
disp_element invalid_frames_rx,1 0
will display the severity of the alarm associated with the invalid_frames_rx statistical
parameter
invalid_frames_rx = 2
The following table shows the alarm severities:
Alarm Number
Severity
Investigate
Critical
Major
Minor
Warning
321
ISSUE 1 REVISION 0
Indexes
322
Chapter 4
ISSUE 1 REVISION 0
ii
ISSUE 1 REVISION 0
Chapter 4
Customer MMI Command Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
41
42
42
MMI Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44
iii
ISSUE 1 REVISION 0
iv
ISSUE 1 REVISION 0
41
ISSUE 1 REVISION 0
42
ISSUE 1 REVISION 0
An on screen manual is also available and provides detailed information about each
command.
MMIRAM 0113 > man page
Command: page [OFF|
<lines per page> ]
Function: Modifies or displays the setting for pagination
Security Level: Can be executed from any security level.
Sysgen Mode: Can be executed in or out of sysgen mode.
OFF
<lines per page>
43
ISSUE 1 REVISION 0
MMI Exercise
MMI Exercise
1.
2.
3.
4.
5.
6.
44
MMI Exercise
ISSUE 1 REVISION 0
7.
8.
Prompt =
9.
10.
11.
12.
NOTE: These parameters are entered using the addcell command when initialising a
new cell.
45
ISSUE 1 REVISION 0
MMI Exercise
13.
MNC
01
LAC
678
MNC
01
LAC
678
Cl
<site No.>
TO
MCC
234
Cl
<another available site No.>
Note: That you will have to login to the BSC to perform this command please ask your
instructor to help you with this.
Command(s) used:
14.
15.
16.
Now that we are registered to receive alarms at the local TTY we can
verify that the Internal Alarm Services (IAS) feature is operating. Power
off a CTU at your site. And observe the response at the screen
Note: As the IAS is a polling process, this may mean that there is a short delay after the
removal of a link before the alarm is generated.
Now display the active alarms list at your site, ensure that it contains the
alarms we have just generated.
Command(s) used:
Restore power to the CTU, and ensure that it comes back into service.
46
MMI Exercise
ISSUE 1 REVISION 0
17.
Display the text component and Severity assigned to each of the PIX
alarm inputs at your site.
Command(s) used:
Text String
Severity
1
2
3
4
5
6
7
8
Command(s) used:
18.
Determine the status of the four PIX output relay contacts at your site.
Command(s) used:
19.
20.
Administrative State:
Operational State:
47
ISSUE 1 REVISION 0
MMI Exercise
21.
State of TCU:
22.
23.
NOTE: During the execution of this command move into RAM: EMON of the BTP and
monitor the code loading of the DRI and CTU.
24.
25.
26.
48
MMI Exercise
ISSUE 1 REVISION 0
27.
Display the state of timeslot 0 of the ARFCN carrying the BCCH group of
Chans
Command(s) used:
Administrative State:
Operational State:
28.
30.
Display the circuit allocation on the 2Mbit/s link which connects your site
to the upstream BTS or the BSC.
Command(s) used:
31.
What is the Base Station Identity Code (BSIC) for the first/only cell at
your site?
Command(s) used:
49
ISSUE 1 REVISION 0
MMI Exercise
32.
33.
Copy the calibration from the CTU at your site, to the Configuration
Management data base at the BSC. Verify that the operation has been
successful.
Command(s) used:
34.
35.
Determine the period of time that the upstream Network Link (E1/T1)
must be above the specified BER before it is taken Out Of Service
(OOS)
Command(s) used:
36.
Add an additional Radio System Link (RSL) to your site, on the primary
BSCtoBTS Path. Determine in which E1 link timeslot the signalling
link has been placed.
Command(s) used:
37.
410
MMI Exercise
ISSUE 1 REVISION 0
411
ISSUE 1 REVISION 0
MMI Exercise
412
Chapter 5
BSC Initialization
ISSUE 1 REVISION 0
ii
ISSUE 1 REVISION 0
Chapter 4
BSC Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BSC Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
51
BSC Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LANLOAD/SYSGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
52
52
SYSGEN mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SYSGEN OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SYSGEN ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database changes in SYSGEN ON mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initial SYSGEN mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SYSGEN safety features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
54
54
55
55
56
56
iii
ISSUE 1 REVISION 0
iv
BSC Initialization
ISSUE 1 REVISION 0
BSC Initialization
Chapter
Objectives
On completion of this chapter the student should be able to:
S
51
ISSUE 1 REVISION 0
BSC Initialization
BSC Initialization
LANLOAD/SYSG
EN
The lanload utility is the only method available to input code objects to a BSC if
connectivity to an OMC is unavailable. The equipment required to carry out a Lanload is
as follows:
1.
2.
3.
The following text describes the procedure for using the lanload tool, combined with
Sysgen, to input code objects and a valid database to bring a BSC online, and ultimately
to operational status.
1.
Ensure all digital boards and cabinet components are correctly installed and
secured prior to applying power.
2.
Apply power to the BSSC2 cabinet and ensure circuit breakers for the power
supply modules are switched to the on position.
Note: If the BSSC2 cabinet is already powered up prior to step 1, remove power and
re-seat the GPROC cards. This will have the effect of making sure no residual code
object information remains on the cards in the DRAM.
Once the GPROC cards are back in their correct positions proceed from step 2.
3.
Connect a PC, with the Procom Plus application installed, to the master GPROC
as described in chapter 9 of BSS11 MMI.
4.
5.
At level 3 the user can now enter the executive monitor (EMON) by pressing
Controln on the keyboard.This shows the current process the Initialization
Process (IP) is running in ROM, in an attempt to bring the site up in to a fully
operational state.
6.
The user now has to commence the Lanload procedure to load the code objects
on to the GPROCs at the site.To do this first remove the loopback from the fibre
optic ports on the LANX card in the halfsize card shelf. Connect a PC, with the
Lanload software and code objects installed, to the fibre optic ports on the LANX
card.
Note: Removing the fibre optic loopback from the LANX card will cause the site to
reset, restarting the IP. If the PC is operating correctly on the LAN then the top 4 lights
on the Lan adaptor will be illuminated.
7.
52
Start the Lanload software application.The PC connected to the LANX card will
now be seen by the IP as another GPROC on the LAN, with code objects. Once
all the GPROCs have announced themselves onto the LAN then Alt9 will
jump to the next stage. (Otherwise the cabinet will wait for 1.5 minutes for
any other GPROCs to come onto the LAN). The IP will crossload the code
objects from the PC to all the GPROCs on the LAN. Once the crossload is
successful the IP will jump to RAM.
BSS12: Base Station Systems MMI and Optimization
FOR TRAINING PURPOSES ONLY
BSC Initialization
ISSUE 1 REVISION 0
8.
Upon initialization in RAM, the IP will look for a link to the OMC. The system
will wait for 6 minutes for this link to be established. Press Alt9 to bypass
this period. Once in RAM the IP checks for a valid database. If loaded as a code
object this would have appeared as code object 2. If code object 2 is not detected
the IP will prompt the user to enter sysgen mode, allowing a database to be input
as a text file. Sysgen_mode on must be entered at the prompt (at level 3). The
user will have 45secs to do this before the IP resets back to the beginning of
ROM. Once sysgen_mode on is entered the user is requested to reset the site.
9.
The BSC can be reset in one of two ways, either by entering the reset_site
command or by removing the fibre optic connections between the Lanload PC
and the LANX card, and replacing the fibre optic loopback.
Once the site is reset and sysgen mode entered the user must enter the script
database file, an ASCII text file. Before entering the new database the command
clear_data must be entered. The new database can now be selected and
uploaded from the PC connected to the master GPROC. If using Procom Plus,
select page up. This will open the window entitled Upload protocols. From the list
of available protocols press A to select ASCII. The ASCII upload window will now
open allowing a full path and file name to be entered at the prompt:
e.g. c:\somerset.scp for the database file somerset.scp stored on the cdrive.
Press the return key after typing in the correct path and filename to start uploading
the database to the master GPROC.
10.
After the database upload is complete the command sysgen_mode off is required
to be entered. This will be done automatically if the command is written at the end
of the database script file. Before the sysgen_mode off command is accepted a
validity check is carried out on the database. If it is found not to be a good
database the IP remains in sysgen and corrections required to the database script
file need to be made by the user. Once it is found to be a valid database the
sysgen_mode off command will be accepted and the database will be
cross-loaded to the other GPROCs over the LAN.
11.
The IP now hands control over to the Central Authority process, which continues
with the site initialization and configuration in accordance with the database script
file.
12.
The Lanload and sysgen operations are now complete. Once the site
initialisation is complete MMI commands can be input in accordance with the BSS
command reference manual.
53
ISSUE 1 REVISION 0
SYSGEN mode
SYSGEN mode
SYSGEN OFF
The SYSGEN OFF mode is the normal system mode of operation. The sysgen_mode
off command is used to place the system in the SYSGEN OFF mode.
If the system is in the SYSGEN ON mode and the sysgen_mode off command is
entered, any changes made to the database will be checked.
*******VERIFYING DATABASE BEFORE COMPLETING SYSGEN*******
Frequency hopping verification in progress.
SITE 0 Verification.
DB Verification passed.
COMMAND ACCEPTED.
SYSGEN ON
The system must be placed in the SYSGEN ON mode of operation to enter some
commands or change some parameters. When the system is in the SYSGEN ON mode,
changes may be entered into the database without being checked until the system is
returned to its normal mode of operation.
CAUTION
Do NOT enter the sysgen_mode on or the sysgen_mode off commands
at the OMC-R.
If the system is in the SYSGEN OFF mode and the sysgen_mode on command is
entered, the system will prompt the user to reinitialize the site.
COMMAND ACCEPTED: You must reinit the site to start SYSGEN
The system will reject the sysgen_mode command if it is entered at a GPROC that is
not acting as the master GPROC.
COMMAND REJECTED: Command only allowed at active BSP.
54
SYSGEN mode
ISSUE 1 REVISION 0
Database
changes in
SYSGEN ON
mode
In a network the BSC will be connected to an OMC. A copy of the BSC database is
stored at the OMC. When a difference is detected between the database load in the
OMC and the BSC, the OMC will automatically download a copy of the database in its
memory to the BSC. Any changes made while the BSC was in the SYSGEN ON mode
will be overwritten by the download from the OMC.
If the changes to be made while the BSC is in SYSGEN ON mode are to be retained, the
following procedure must be used:
Step
Action
a.
b.
c.
d.
e.
f.
g.
Initial SYSGEN
mode
The initial SYSGEN mode occurs when the system is placed in the SYSGEN ON mode
without a Configuration Management (CM) database. The initial SYSGEN mode is used
to load the CM database using a script.
CAUTION
The clear_database command should only be used by personnel who are
fully aware of the consequences.
The system is placed in the initial SYSGEN mode by placing the system in the SYSGEN
ON mode then entering the clear_database command.
55
ISSUE 1 REVISION 0
SYSGEN mode
Scripts
A script is a file that contains a series of commands which load the CM database into the
system.
A script is loaded in the initial SYSGEN mode. This permits large amounts of information
to be efficiently loaded onto the system.
After the database is loaded using a script, the system must be returned to the SYSGEN
OFF mode to verify the script contents. If errors are detected, the system will not return
to the SYSGEN OFF mode. When this occurs, the script has to be corrected and
reloaded before the system will be able to return to its normal operating state.
SYSGEN safety
features
Automatic GPROC addition
If the initial SYSGEN mode is entered from a GPROC which is not included in the script,
a GPROC will automatically be added to the slot from which the initial SYSGEN mode
was entered.
It is recommended that the initial SYSGEN mode be entered from the same type of
system for which the database is being loaded. For example, if the script to be loaded is
for an RXCDR, the initial SYSGEN mode should be entered from the master slot of an
RXCDR (011ah). If the script to be loaded is for a BSS, the initial SYSGEN mode should
be entered from the master slot of a BSC (0115h).
Safety timer
While the system is in the SYSGEN ON mode, a timer is used to insure that a GPROC
cannot be left in the SYSGEN ON mode indefinitely. The timer is started when no activity
is detected from the TTY terminal. If activity is detected before the timer expires, the
timer will be reset to its initial value and restarted.
If the timer expires, the GPROC will be reset with a Global Kill SWFM. Within the SWFM,
a message will include a textual description that the timer expired.
56
SYSGEN mode
ISSUE 1 REVISION 0
57
ISSUE 1 REVISION 0
SYSGEN mode
58
Chapter 6
Horizonmacro Optimization
ISSUE 1 REVISION 0
ii
ISSUE 1 REVISION 0
Chapter 6
Horizonmacro Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
61
62
62
62
63
63
66
66
67
67
68
610
610
612
612
613
614
615
617
617
619
624
625
625
625
626
627
629
632
633
634
634
635
637
638
638
638
638
639
639
640
640
640
640
641
641
642
642
642
643
643
643
iii
ISSUE 1 REVISION 0
iv
644
644
644
644
645
646
ISSUE 1 REVISION 0
Checking the antenna VSWR and calibrating the transmit output power.
Checking the serial connections, power supply module version and alarm status.
CAUTION
The Horizonmacro and all associated site equipment must be completely
optimized before integrating the base site for operation.
61
ISSUE 1 REVISION 0
Test equipment
Table 6-1 provides details of the test equipment required to perform the Hardware
Optimization procedures provided in this chapter:
Table 6-1 Hardware optimization equipment
Quantity
62
Description
Comments
PC
Signal generator
Up to 2GHz
Digital multimeter
30dB attenuator
100 W minimum
RF adaptor kit
RTLXQ98088 or equivalent
N to N barrel adaptor
Must be calibrated
Must be calibrated
ISSUE 1 REVISION 0
Test lead
calibration
To minimize variations in test results, ensure that all appropriate test leads used in
Hardware Optimization procedures are calibrated.
CAUTION
A recognized laboratory must calibrate all test equipment and associated test
leads annually.
Do not calibrate test equipment or test leads in the field.
Test leads
Connections for a TTY test lead
Figure 6-1 shows the connections for the test lead used in the Hardware Optimization
procedures:
PIN NUMBER
PIN NUMBER
6
7
8
4 m LONG SCREENED CABLE
TO PC COMMUNICATIONS PORT
9 WAY D-TYPE F
TO CTU CONNECTOR
9 WAY D-TYPE M
63
ISSUE 1 REVISION 0
PIN NUMBER
2
9
EQCP PINS
RSS PINS
8
5
5
SELECTOR
SWITCH
4m SCREENED CABLE
9-WAY D-TYPE
9-WAY D-TYPE
F CONNECTOR
M CONNECTOR
(TO PC COMMUNICATIONS
PORT)
64
ISSUE 1 REVISION 0
To PIN
20
21
22
23
24
25
26
27
N/A
11
29
NOTE
65
ISSUE 1 REVISION 0
The Preparing for test procedure at the end of this section should be completed before
attempting the VSWR and cellsite power calibration procedures.
66
ISSUE 1 REVISION 0
Test stages
There are four stages to the procedure:
S
Test equipment
The following test equipment is required during the VSWR and output power calibration
procedure:
S
67
ISSUE 1 REVISION 0
Commands
Table 6-3 lists the commands for the VSWR and output power calibration procedure:
NOTE
1. The symbol 0 used in the commands in this procedure is a zero.
2. BSS MMI commands may be entered in upper or lower case. All other
commands must be entered in the case shown.
Function
ins_device
lock_device
unlock_device
clear_cal_dataA
CTU command
Function
Stops the CTU hunting between link A and link B and forces
the CTU to look only at link A.
tcu_clock 0
CTU emulator
command
TEST
ACT C
CSPWR
Cell Site Power. Allows the Cell Site power to be set to the
maximum output power.
HALT C
TS <T> CHAN
68
Function
XXX
WRENB
SAVE CAL TX
WRPTC
FR TX
ISSUE 1 REVISION 0
CTU emulator
command
Function
MR TX
SNDCMB
69
ISSUE 1 REVISION 0
If CCBs are fitted, set all DIP switches on the CCB control board to zero (this
assists programming and checksum calculations).
2.
Connect the 9 to 9-way cable from the PC serial A port to MCU TTY port.
3.
4.
is:
NOTE
The radio must be brought into service as there is no Flash EPROM storage of
code at the radio control processor level.
If a connection to the BSC is not available a PCMCIA commissioning card
must be used.
5.
is:
WARNING
An RF hazard exists during DRI transmissions. As one antenna may be
connected to a number of DRIs, the lock command must be repeated for all
DRIs on the antenna being worked on before connecting the wattmeter.
NOTE
For ease of calibration, all CTUs in a cell should be initialized and then locked.
Always lock the transceiver providing the BCCH last, as this prevents the
BCCH being switched to alternate transceivers.
610
ISSUE 1 REVISION 0
6.
Type:
clear_cal_data # dri A * 0
Where:
is:
NOTE
The clear_cal_data command clears all calibration data out of the CM
database. This is required to overide the preserve calibration feature, if
enabled.
7.
Connect port COM1 on the PC to the TTY Interface port on the transceiver using
the 9 to 9-way RSS cable.
8.
NOTE
Do not reset the CTU at this point. The reset is carried out on completion of
the CTU VSWR and cellsite power calibration procedure, as detailed in section
Restoring the site.
9.
Remove the 9 to 9-way RSS cable from the transceiver and replace it with the 9 to
9-way EQCP cable.
611
ISSUE 1 REVISION 0
TS A CHAN 700
TS A TXP 00
MDLTR UC
Prior to executing the CSPWR command, it assumes that the synthesizers are in normal
mode (not locked), as is the case after the unit is powered up for the first time.
612
ISSUE 1 REVISION 0
VSWR Method 1
(automatic)
The first method for normal VSWR checking uses automatic channel selection. The
CSPWR command automatically selects a midpoint channel number (channel 31 or 700),
but if required a manual process can be performed as shown in method 2.
Disconnect antenna. Connect a dummy load to the meter and ensure the meter is
fitted with a 50 W element. Connect the meter to the TX output.
2.
3.
Monitor and record the wattmeter reading (the forward output power).
4.
5.
Replace the 50 W element in the wattmeter with a 5 W element and reverse the
direction on the power meter.
6.
Remove the dummy load and connect the power meter through to the antenna.
WARNING
Full power is transmitted during VSWR checks. Ensure all personnel are
clear of the antenna. Do not carry out this check unless antenna installation is
complete.
CAUTION
To reduce the possibility of interference with other users, minimize the time
that the radio is powered up.
7.
8.
Monitor and record the reverse power reading indicated on the power meter.
NOTE
Readings should show reflected (reverse) power of no more than 5% of the
forward power at the point of measurement, but less than 1W.
If the ratio of the forward and reverse readings is unacceptable, suspect an
improper termination of the antenna feeder and connector.
9.
10.
11.
EMOTOROLA LTD. 2000
613
ISSUE 1 REVISION 0
VSWR Method 2
(manual)
The second method for normal VSWR checking allows the manual selection of a
channel.
Disconnect antenna. Connect a dummy load to the meter and ensure the meter is
fitted with a 50 W element. Connect the meter to the TX output.
2.
3.
is:
nnn
4.
is:
00
5.
Monitor and record the wattmeter reading (the forward output power).
6.
is:
FF
7.
Replace the 50 W element in the wattmeter with a 5 W element and reverse the
direction on the power meter.
8.
Remove the dummy load and connect the power meter through to the antenna.
WARNING
Full power is transmitted during VSWR checks. Ensure all personnel are
clear of the antenna. Do not carry out this check unless antenna installation is
complete.
CAUTION
To reduce the possibility of interference with other users, minimize the time
that the radio is powered up.
614
ISSUE 1 REVISION 0
9.
10.
Monitor and record the reverse power reading indicated on the power meter.
NOTE
Readings should show reflected (reverse) power of no more than 5% of the
forward power at the point of measurement, but less than 1 W.
If the ratio of the forward and reverse readings is unacceptable, suspect an
improper termination of the antenna feeder and connector.
11.
12.
13.
14.
Calibrating CTU
transmit output
power
NOTE
Calibration is not required unless the desired configuration is different to the
shipped configuration.
To calibrate CTU transmit output power:
1.
Disconnect antenna. Connect a dummy load to the meter and ensure the meter is
fitted with a 50 W element. Connect the meter to the TX output.
2.
3.
Enter CSPWR
The following message is displayed:
Hit U or D until desired max is measured then
hit ESC, CTRL-Y or CTRL-C
615
ISSUE 1 REVISION 0
4.
Achievable value
CTU900
CTU1800
40 W (46.0 dBm)
32 W (45.1 dBm)
Duplexed Combining
bandpass Filter (DCF)
20 W (43.0 dBm)
16 W (42.1 dBm)
Dual-stage Duplexed
combining Filter (DDF)
7 W (38.5 dBm)
20 W (43.0 dBm)
16 W (42.1 dBm)
All
5.
P: 46.8 dBm
When the required output level is achieved, press ESC or CTRL-Y or CTRL-C
6.
616
7.
8.
9.
Use the Restoring the site procedure to return the site to service.
ISSUE 1 REVISION 0
off
on
off
off
on
off
on
on
Binary value of
each switch
128
64
32
16
NOTE
617
ISSUE 1 REVISION 0
618
ISSUE 1 REVISION 0
Calibration
procedures
The procedures Tuning the CCB cavities, VSWR calibration procedure, Calibrating
cellsite power and Parking the CCB cavities should be used for VSWR and cellsite
calibration of Horizonmacro cabinets equipped with CTUs and CCB RF combiners.
NOTE
The four calibration procedures should be completed sequentially, and without
pause, for each radio.
Failure to do so could result in the associated CCB being parked on the wrong
channel.
Disconnect antenna. Connect a dummy load to the meter and ensure the meter is
fitted with a 50 W element. Connect the meter to the TX output.
2.
3.
4.
Issue the full tuning command to the CCB. To tune cavity 0, at the EQCP TEST
prompt:
For...
Type...
CTU900
SNDCMB 02 05 00 01 00 1F 00 27
CTU1800
SNDCMB 02 05 00 01 02 BC 00 C6
Where:
02 is the parameter download message ID.
05 is the number of bytes to follow, excluding final checksum.
00 is the CCB address (as set on the DIP switches).
01 is the hex value of the address of the cavity to be tuned. (set for cavity 0)
00 is the channel high byte for CTU900 (02 for CTU1800).
1F is the channel low byte for a CTU 900 set to channel 31
(BC for a CTU1800 set to channel 700).
00 is the power level always 00.
27 is the low byte of the checksum 02 + 05 + 00 + 01 + 00 + 1F + 00 for a
CTU900
(C6 is the low byte of checksum 02 + 05 + 00 + 01 + 02 + BC + 00 for a
CTU1800).
EMOTOROLA LTD. 2000
619
ISSUE 1 REVISION 0
The response should occur in under 12 seconds and begin with 01.
A typical response, if OK, is:
01 04 00 01 00 00 06
Table 6-7 (CTU900) and Table 6-8 (CTU1800) details the tuning commands for all
possible cavities.
2.
Monitor and record the wattmeter reading (the forward output power).
3.
4.
Replace the 50 W element in the wattmeter with a 5 W element and reverse the
direction on the power meter.
5.
Remove the dummy load and connect the power meter through to the antenna.
WARNING
Full power is transmitted during VSWR checks. Ensure all personnel are
clear of the antenna. Do not carry out this check unless antenna installation is
complete.
CAUTION
To reduce the possibility of interference with other users, minimize the time
that the radio is powered up.
6.
620
ISSUE 1 REVISION 0
7.
Monitor and record the reverse power reading indicated on the power meter.
NOTE
Readings should show reflected (reverse) power of no more than 5% of the
forward power at the point of measurement, but less than 1 W .
If the ratio of the forward and reverse readings is unacceptable, suspect an
improper termination of the antenna feeder and connector.
8.
Enter CSPWR
The following message is displayed:
Hit U or D until desired max is measured then
hit ESC, CTRL-Y or CTRL-C
2.
Achievable value
CTU900
CTU1800
40 W (46.0 dBm)
32 W (45.1 dBm)
Duplexed Combining
bandpass Filter (DCF)
20 W (43.0 dBm)
16 W (42.1 dBm)
Dual-stage Duplexed
combining Filter (DDF)
7 W (38.5 dBm)
20 W (43.0 dBm)
16 W (42.1 dBm)
All
3.
P: 46.8 dBm
When the required output level is achieved, press ESC or CTRL-Y or CTRL-C
4.
Save the transmit power calibration. At the EQCP TEST prompt type:
HALT C
WRENB
SAVE CAL TX
WRPTC
621
ISSUE 1 REVISION 0
02
05
00
01
00
1F
00
27
02
05
00
02
00
1F
00
28
02
05
00
04
00
1F
00
2A
02
05
00
08
00
1F
00
2E
02
05
00
10
00
1F
00
36
02
05
00
20
00
1F
00
46
622
02
05
00
01
02
BC
00
C6
02
05
00
02
02
BC
00
C7
02
05
00
04
02
BC
00
C9
02
05
00
08
02
BC
00
CD
02
05
00
10
02
BC
00
D5
02
05
00
20
02
BC
00
E5
ISSUE 1 REVISION 0
C2
02
00
01
C5
C2
02
00
02
C6
C2
02
00
04
C8
C2
02
00
08
CC
C2
02
00
10
D4
C2
02
00
20
E4
1.
2.
Use the Restoring the site procedure to return the site to service.
623
ISSUE 1 REVISION 0
Restoring the
site
After all installed CTUs have been checked and calibrated, perform the following steps to
restore the site:
1.
Disconnect antenna. Connect a dummy load to the meter and ensure the meter is
fitted with a 50 W element. Connect the meter to the TX output.
2.
Return the DIP switches on the CCB control boards to their original positions.
3.
Remove the 9 to 9-way EQCP cable from the TTY port and connect the 9 to 9-way
cable to the MCU MMI port.
CAUTION
The following step must be carried out to initialize software and so ensure the
CTU is correctly brought into service.
4.
5.
is:
This returns the CTU to the Unlocked_Busy state (confirmed by the state
command).
6.
7.
624
is:
8.
9.
Remove the wattmeter and reconnect the antenna lead to the TX port.
10.
11.
Inform the OMC the VSWR and cellsite power calibration has been completed.
ISSUE 1 REVISION 0
A CTU is replaced.
Test equipment
The following test equipment is required:
S
9 to 9-way cable.
625
ISSUE 1 REVISION 0
Commands
Table 6-10 details the commands that must be used to carry out the procedure:
NOTE
1. The symbol 0 used in the commands in this procedure is a zero.
2. BSS MMI commands may be entered in upper or lower case. All other
commands must be entered in the case shown below.
CTU passwords are not case sensitive.
Table 6-10
BSS MMI command
Function
ins_device
lock_device
unlock_device
clear_cal_data
Function
TEST
AIC OUT
ACT C
TS A CHAN #
TS A ANT #
SYNTH 1
SYNTH NRM
BAYDONE @N
HALT C
WRENB
WRPTC
FR BAY
MR BAY
CTU command
tcu_clock 0
626
Function
Stops the CTU hunting between fibre A and fibre B and forces
the CTU to look only at fibre A.
ISSUE 1 REVISION 0
Preparation for
bay level
calibration
The RF path has to be prepared for Bay Level Calibration. The radio has to be reset and
locked, a dummy load connected if no antenna and the alarms disabled. Proceed as
follows:
1.
Connect the 9 to 9-way cable from the PC serial A port to MCUF TTY port.
2.
3.
is:
NOTE
The radio must be brought into service as there is no Flash EPROM storage of
code at the radio control processor level.
If a connection to the BSC is not available a PCMCIA commissioning card
must be used.
4.
is:
NOTE
For ease of calibration, all CTUs in a cell should be initialized and then locked.
Always lock the transceiver providing the BCCH last as this prevents the
BCCH being switched to alternate transceivers.
627
ISSUE 1 REVISION 0
5.
Type:
clear_cal_data # dri A * 0
Where:
is:
NOTE
The clear_cal_data command clears all calibration data out of the CM
database. This is required to overide the preserve calibration feature, if
enabled.
6.
Connect port COM1 on the PC to the TTY Interface port on the radio using a
9 to 9-way RSS cable.
7.
8.
9.
Remove the 9 pin RSS connector from the radio and replace it with a 9 to 9-way
EQCP cable.
10.
628
ISSUE 1 REVISION 0
Bay level
calibration for
branch 1 RX0A
Proceed as follows:
1.
Connect the output of the signal generator to branch 1 of the antenna port at the
top of the Horizonmacro cabinet.
NOTE
It is important to choose the correct number in the TS
If RX path is A0 or B0 of SURF then antenna is TS A
If RX path is A1 or B1 of SURF then antenna is TS A
If RX path is A2 or B2 of SURF then antenna is TS A
A ANT command.
ANT1.
ANT2.
ANT3.
The antenna number can also be found by using the disp_equipment # DRI A * 0
command. The number next to antenna_select is the antenna number.
2.
Set the signal generator to provide 65.0 dBm at the antenna port and to the first
channel test frequency shown in Table 6-11 (EGSM900) or Table 6-12 (DCS1800)
Table 6-11 EGSM900 test frequency table
Channel
Frequency (MHz)
Channel
Frequency (MHz)
979
881.001
43
898.601
987
882.601
51
900.201
995
884.201
59
901.801
1003
885.801
67
903.401
1011
887.401
75
905.001
1019
889.001
83
906.601
03
890.601
91
908.201
11
892.201
99
909.801
19
893.801
107
911.401
27
895.401
115
913.001
35
897.001
123
914.601
629
ISSUE 1 REVISION 0
3.
Channel
Frequency (MHz)
Channel
Frequency (MHz)
516
1711.001
708
1749.401
524
1712.601
716
1751.001
532
1714.201
724
1752.601
540
1715.801
732
1754.201
548
1717.401
740
1755.801
556
1719.001
748
1757.401
564
1720.601
756
1759.001
572
1722.201
764
1760.601
580
1723.801
772
1762.201
588
1725.401
780
1763.801
596
1727.001
788
1765.401
604
1728.601
796
1767.001
612
1730.201
804
1768.601
620
1731.801
812
1770.201
628
1733.401
820
1771.801
636
1735.001
828
1773.401
644
1736.601
836
1775.001
652
1738.201
844
1776.601
660
1739.801
852
1778.201
668
1741.401
860
1779.801
676
1743.001
868
1781.401
684
1744.601
876
1783.001
692
1746.201
883
1784.401
700
1747.801
TS A ANT 1
The system responds with the following:
All timeslots are under user control.
630
ISSUE 1 REVISION 0
4.
is:
5.
Where
XX
XX
6.
Set the signal generator to the next frequency and repeat steps 4 and 5 for all the
test frequencies in Table 6-11 or Table 6-12.
631
ISSUE 1 REVISION 0
2.
Set the signal generator to provide 65.0 dBm at the antenna port and to the first
channel test frequency shown in Table 6-11 or Table 6-12.
3.
4.
5.
is:
6.
632
Set the signal generator to the next frequency and repeat steps 4 and 5 for all the
test frequencies in Table 6-11 or Table 6-12.
ISSUE 1 REVISION 0
2.
Set the signal generator to provide 65.0 dBm at the antenna port and to the first
channel test frequency shown in Table 6-11 or Table 6-12.
3.
4.
5.
is:
6.
Set the signal generator to the next frequency and repeat steps 4 and 5 for all the
test frequencies in Table 6-11 or Table 6-12.
633
ISSUE 1 REVISION 0
Branch
completion
To complete the bay level procedure for the branch, at the EQCP TEST prompt type:
BAYDONE @1
The system responds with the following:
BAY LEVEL CALIBRATION IS DONE
Branch 2
Repeat the procedures Bay level calibration branch 1 RX0A, Bay level repeat for
RX1A and Bay level repeat for RX2A for branch 2 by connecting to RX0B, RX1B and
RX2B alternately. Enter @2 instead of @1 in the cal bay and baydone commands.
634
ISSUE 1 REVISION 0
Checking
calibration
The following procedure should be used to check the bay level calibration has been
successful.
1.
To verify that the bay level offset values have been stored in EPROM, use the read
command with the required offset table location as an argument.
FR BAY
MR BAY
Flash Address
A000700
A000703
Branch 1 Checksum
A000706
Branch 2 Checksum
A000709
A00070C A00074D
A00074E A00078F
A000790 A0007D1
A0007D2 A000813
A000814 A000855
A000856 A000897
CTU900s cover the EGSM range and store offsets in 22 locations in each memory
area per antenna per branch.
CTU1800s cover the DCS range and store offsets in 47 locations in each memory
area per antenna per branch.
NOTE
Each location consists of three bytes. For example, the branch 1 valid flag
data is stored in address locations A000700, A000701 and A000702.
2.
The following is an example of the first line of the FLASH BAY LEVEL OFFSET
table when using the FR BAY command, and a description of the fields displayed:
Address
BR1
BR2
flag
BR1
Cksum
BR2
Cksum
BL
offset
BL
offset
BL
offset
BL
offset
A000700
000001
000001
000595
000595
000060
000002
000005
000002
635
3.
ISSUE 1 REVISION 0
If the Bay Level Calibration is successful, each appropriate table location will
contain valid offsets, and not the factory default of 80.
NOTE
The presence of 80 will result in error alarm DRI 218: Invalid Transceiver
Calibration Data being reported when the unit is unlocked.
However, unused data columns in a site configuration may have value 80; no
alarm will be reported as such table locations are inappropriate to the site.
4.
636
ISSUE 1 REVISION 0
End procedure
restoring site
After the Bay Level Calibration procedure is completed, restore the site by the following:
1.
Remove the signal generator and dummy load and refit the site RF cables.
2.
Remove the 9 to 9-way cable from the TTY INTERFACE port on the CTU.
3.
Connect the 9 to 9-way cable from the PC serial A port to a MCUF TTY port.
CAUTION
The following step must be carried out to initialize software and so ensure the
CTU is correctly brought into service.
4.
5.
Type:
unlock_device # dri A * 0
Where:
is:
Type:
disp_act_alarm # dri A * 0
Where:
is:
Confirm that there is no DRI 218 alarm. If there is a DRI 218 alarm, redo the
whole Bay Level Calibration procedure
7.
637
ISSUE 1 REVISION 0
Commands
The following commands are used during the procedure:
NOTE
The symbol 0 used in the commands in this procedure is a zero.
S
disp_site
disp_equipment
Test equipment
The following test equipment is required during the procedure:
S
638
ISSUE 1 REVISION 0
2.
Connect the serial A port on the PC to a MCUF TTY port using the 9-way to 9-way
cable.
3.
Checking the
database
equipage
To check the database for devices and functions:
1.
2.
Enter:
disp_equipment #
where # = the number of the site logged into.
A complete list of the equipment and functions in the database is displayed, for
example:
GPROC 0 0 0
GPROC 1 0 0
BSP
0 0 0
DRI
0 0 0
DRI
0 1 0
MSI
0 0 0
MMS
0 0 0
MMS
0 1 0
GCLK 0 0 0
KSW
0 0 0
CAB
0 0 0
SITE 0 0 0
RTF
0 0 0
RTF
0 1 0
3.
639
ISSUE 1 REVISION 0
Commands
The following command is used to carry out the procedure:
S
state
Test equipment
The 2.048 Mbit/s link checks require the following test equipment:
S
A 9-to 9-way cable (a diagram of this cable is provided in the Test equipment,
leads and plugs section).
CAUTION
All test equipment and test leads must be calibrated annually by a recognized
laboratory. Test equipment and test leads must not be calibrated in the field.
Do not optimize Motorola Cellular Base Stations with test equipment that is
beyond its calibration due date.
Allow test equipment to warm up for 30 minutes before use.
640
ISSUE 1 REVISION 0
2.
Connect the serial A port on the PC to an MCUF TTY port using the 9-way to
9-way cable.
3.
The system and the hardware are set up to check the 2.048 Mbit/s links.
Checking the
2.048 Mbit/s link
To check the 2.048 Mbit/s link:
1.
Contact the end point of the 2.048 Mbit/s you want to test, BSC/MSC, and request
a loopback on the relevant Digital Distribution Frame (DDF) port.
NOTE
Repeat for all NIUs and 2 Mbit/s links.
S
If the 2.048 Mbit/s link has not been installed, perform this test at the
Digital Distribution Frame (DDF) in the site.
S
2.
3.
If this display shows Unlocked and Busy, then the NIU port (MMS), T43, cabling and
the 2.048 Mbit/s link are all good.
If the loop is removed and the command re-entered, the result will be Unlocked and
Disabled.
NOTE
The NIU requires a minimum of 20 seconds after receiving these commands
before it registers a change in status.
If the display continues to show Unlocked and Busy, this may be because:
1. The wrong connection is looped, if the cabling is direct.
2. The MMS may be terminated by a device generating a 2.048 Mbit/s link.
641
ISSUE 1 REVISION 0
Testing the PIX connections using the database external alarm system (EAS).
Test equipment
The serial and alarm tests require the following test equipment:
S
642
ISSUE 1 REVISION 0
Commands
The following commands are used to test the PIX connections:
S
enable_alarm
2.
Connect the serial A port on the PC to the master MCUF using the 9 to 25 way
cable.
3.
4.
2.
3.
643
ISSUE 1 REVISION 0
When to calibrate
the GCLK
This calibration procedure is to be used on the following occasions:
S
When more than one frame slip per hour is observed at the OMC
Whenever calibration is required. (Display the active alarms for a site, if calibration
is required, there will be an alarm stating this.)
CAUTION
This procedure should only be carried out by by fully trained, GSM qualified
personnel. Under NO circumstances should this procedure be undertaken,
unless all the correct test equipment is readily available.
NOTE
S
No call processing can occur involving the MCU during calibration mode.
Test equipment
required
The test equipment required to carry out the GCLK calibration is as follows:
644
Universal counter with external reference, for example, the Hewlett Packard model
HP5385A or equivalent.
ISSUE 1 REVISION 0
Setting up for
calibration
To prepare the MCUF (GCLK) for calibration, carry out the following steps:
1.
Connect the serial A port of the PC to the MCU TTY port using the 9 to 9 way TTY
cable.
2.
3.
Connect the output from the 10 MHz standard to the reference input of the
frequency counter, select external standard.
4.
Set the frequency gate time to 10 seconds and the display to 10 significant digits.
5.
Connect the test cable extracting the 8 kHz output signal from the front of the
MCUF to the input of the counter.
Pin 3 Ground (top pin)
Pin 1 8 kHz signal (bottom pin)
Figure 6-3 illustrates how the equipment is to be connected to the unit under calibration.
MCU TTY
MCU
8 kHz Out
8000.000000
10 MHz REFERENCE
UNIVERSAL COUNTER
645
ISSUE 1 REVISION 0
Test Procedure
CAUTION
This procedure should only be carried out by by fully trained, GSM qualified
personnel. Under NO circumstances should this procedure be undertaken,
unless all the correct test equipment is readily available.
NOTE
1.
The gclk_cal_mode command is used to tell the sync function and MCUF software that
a calibration is to be performed.
NOTE
The gclk_cal_mode command can only be executed at Horizonmacro sites,
outside of sysgen mode. The command is NOT allowed on a Master MCUF
when a Standby MCUF is available.
The system will prompt for the following verification when the command is executed:
Site <local site number> starting GCLK CALIBRATION MODE.
this is a single MCU site, the site will be down until
calibration is complete.
If
3.
Adjust the OCXO control voltage using the +/ and 0 to 3 keys until the measured
frequency is exactly 8000,000000 Hz.
The values entered here, change the frequency by varying degrees. For example, +0 will
increase the output by a small amount.
+1 will increase the frequency by approximately 10 times.
+2 will increase the frequency by approximately 100 times.
+3 will increase the frequency by approximately 1000 times.
The above values are not exact as every OCXO has a different gain, this method gives
sufficient control to pull-in the frequency within a short time.
646
ISSUE 1 REVISION 0
4.
5.
After calibration, the MCUF applies a set of voltages to the DAC that feeds the OCXO,
this requires the user to input the corresponding output frequency. This is because the
OCXO frequency V voltage characteristic is not linear, and by taking readings across a
range of DAC voltages, the MCU can make adjustments for non-linearity.
6.
To calibrate the OCXO, gain, enter the measured frequency value from the counter
after the value has settled in response to the MMI prompts.
When taking frequency measurements, ensure that a full gate period elapses from the
time the new value is set to reading the counter. This wait may be up to seconds
depending on the counter.
A typical sequence of frequency measurements may be presented as follows:
Dac set to 1.0 volts, Enter Freq Value or a to abort > 7999.99853
Dac set to 2.0 volts, Enter Freq Value or a to abort > 7999.99915
Dac set to 3.0 volts, Enter Freq Value or a to abort > 7999.99969
Dac set to 4.0 volts, Enter Freq Value or a to abort > 8000.00020
Dac set to 5.0 volts, Enter Freq Value or a to abort > 8000.00070
Dac set to 6.0 volts, Enter Freq Value or a to abort > 8000.00122
Dac set to 7.0 volts, Enter Freq Value or a to abort > 8000.00176
Calibration Gain 3.865560e-01
SYNC>
7.
On completion the user should ensure that the Calibration Gain is between 0 and
1.5. Values other than this may indicate a poor OCXO, or an error in performing
the procedure. The most common error is in reading the counter when locating
the decimal point by eye.
8.
If the Calibration Gain value is not in the range, calibration should be performed
again as a double check. If it fails a second time with the same or similar value,
the OCXO, may be operating outside of the Motorola specification. If this occurs,
the MCU is deemed faulty and should be replaced. Otherwise the calibration
procedure is complete.
NOTE
The MCUF will be reset when the calibration is complete.
647
ISSUE 1 REVISION 0
648
Chapter 7
ISSUE 1 REVISION 0
ii
ISSUE 1 REVISION 0
Chapter 7
Customer BTS Configuration Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
71
72
72
74
iii
ISSUE 1 REVISION 0
iv
ISSUE 1 REVISION 0
71
ISSUE 1 REVISION 0
72
1.
You are an Engineer currently situated at a BTS. Another BTS has been situated
near to your location and is to be configured in a daisy chain through your current
location.
2.
You are to physically connect the two BTSs, using the E1 links that will be made
available to you by your instructor.
3.
You are to configure the link between the BSC and the new BTS.
4.
As the necessary codes will be downloaded from the BSC, you have to get the site
to a state where it will be able to receive such a download across the link that you
have configured.
5.
All the information you require to carry out this task is located within this manual,
and in the Command Reference Manual, situated by your workstation.
ISSUE 1 REVISION 0
73
ISSUE 1 REVISION 0
74
ISSUE 1 REVISION 0
BS S
S ITE
CELL
COMB
CAB
MCU (BTP)
NIU (MS I)
TCU (DRI)
GCLK
CS FP
PATH
RTF
16 kbit/s RS L
64 kbit/s RS L
Associated RTF
75
76
ISSUE 1 REVISION 0
Annex A
Horizonmacro Suggested
Configurations
ISSUE 1 REVISION 0
ii
ISSUE 1 REVISION 0
A1
ISSUE 1 REVISION 0
Suggested RF configurations
Suggested RF configurations
Overview of
configuration
diagrams
The following series of RF configuration diagrams show suggested ways of connecting
together Horizonmacro SURF and Tx blocks to meet different operational requirements.
The series of diagrams is by no means exhaustive, and numerous alternative
configurations may be adopted to achieve the same aim.
Each Horizonmacro cabinet is represented by a SURF module and three Tx blocks.
Interconnecting cables are identified by a label; N01, 2, 3 or 4. Antenna connecting
cables, not supplied as part of the Horizonmacro equipment, are shown in dotted lines.
With the exception of Figure 7-20, each diagram is applicable to either EGSM 900 or
DCS 1800 operation though the SURF module illustrated is an 1800 SURF. For EGSM
900 operation a 900 SURF (dual band) is required. Connections to the 900 SURF are
identified in the same way as those to the 1800 SURF, with two additional connectors
provided for dual band 1800 use.
Figure 7-20 shows one way of achieving dual band operation using two Horizonmacro
cabinets. An 1800 SURF is installed in one cabinet and a 900 SURF (dual band) in the
other.
Configuration for
omni 1
Figure 7-1 shows a suggested configuration, using one Horizonmacro cabinet, for omni 1
with twin duplexed filter.
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
RX
RX
ANT ANT
BLANK
BLANK
TDF
A2
Suggested RF configurations
ISSUE 1 REVISION 0
Configuration for
omni 1 or 2
Figure 7-2 shows a suggested configuration, using a single Horizonmacro cabinet, for
omni 1 or omni 2 with duplexed combining bandpass filter.
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
ANT
RX
BLANK
BLANK
DCF
If configured for...
omni 1
DCF 0
A3
ISSUE 1 REVISION 0
Suggested RF configurations
Configuration for
omni 3 or 4
Figure 7-3 shows a suggested configuration, using a single Horizonmacro cabinet, for
omni 3 or omni 4 with duplexed combining bandpass filter.
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
N01
ANT
ANT
RX
RX
BLANK
DCF
DCF
omni 3
DCF 1
Configuration for
omni 3
Figure 7-4 shows a suggested configuration, using one Horizonmacro cabinet, for omni 3
with dual stage duplexed combining filter.
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
ANT
N02
BLANK
2
FEED
THRU
1
RX
TX
DDF
0
Suggested RF configurations
ISSUE 1 REVISION 0
Configuration for
omni 4
Figure 7-5 shows a suggested configuration, using a single Horizonmacro cabinet, for
omni 4 with dual stage duplexed combining filter and hybrid combining unit.
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
ANT
N02
TX
RX
TX
BLANK
HCU
DDF
Configuration for
omni 5 or 6
Figure 7-6 shows a suggested configuration, using one Horizonmacro cabinet, for omni 5
or 6 with dual stage duplexed combining filter and air combining.
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
N01
ANT
ANT
N02
N02
RX
TX
DDF
2
FEED
THRU
1
RX
TX
DDF
0
Figure 7-6 Single cabinet omni 5 or 6 with DDF and air combining
Unused SMA connectors must be fitted with 50 ohm terminating loads as shown below.
If configured for...
omni 5
DDF 2
A5
ISSUE 1 REVISION 0
Suggested RF configurations
Configuration for
sector 1/1 or 2/2
Figure 7-7 shows a suggested configuration, using a single Horizonmacro cabinet, for
sector 1/1 or 2/2 with duplexed combining bandpass filter.
SECTOR 2
SECTOR 1
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
N01
ANT
ANT
RX
RX
DCF
BLANK
DCF
A6
If configured for...
sector 1/1
Suggested RF configurations
ISSUE 1 REVISION 0
Configuration for
sector 1/1
Figure 7-8 shows a suggested configuration, using one Horizonmacro cabinet, for sector
1/1 with twin duplexed filter.
SECTOR 2
SECTOR 1
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
N01
RX
RX
ANT ANT
BLANK
BLANK
TDF
Configuration for
single cabinet
sector 3/3
Figure 7-9 shows a suggested configuration, using one Horizonmacro cabinet, for sector
3/3 with dual stage duplexed combining filter.
SECTOR 1
SECTOR 2
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
N01
ANT
ANT
RX
TX
DDF
2
N02
N02
FEED
THRU
1
RX
TX
DDF
0
A7
ISSUE 1 REVISION 0
Suggested RF configurations
Configuration for
2 cabinet sector
3/3
Figure 7-10 shows a suggested configuration, using two Horizonmacro cabinets, for
sector 3/3 with dual stage duplexed combining filter.
SECTOR 2
SECTOR 1
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
2B 1B 0B 2A 1A 0A
N01
ANT
ANT
N02
RX RX RX RX RX RX EXT EXT
N01
BLANK
N02
RX
TX
FEED
THRU
1
DDF
BLANK
RX
TX
FEED
THRU
1
DDF
0
Configuration for
2 cabinet sector
4/4
Figure 7-11 shows a suggested configuration, using two Horizonmacro cabinets, for
sector 4/4 with dual stage duplexed combining filter and hybrid combining unit.
SECTOR 1
2B 1B 0B 2A 1A 0A
SECTOR 2
RX RX RX RX RX RX EXT EXT
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
N01
ANT
TX
N02
ANT
RX
TX
N02
TX
RX
TX
BLANK
HCU
DDF
BLANK
HCU
DDF
Figure 7-11 Two cabinet sector 4/4 with DDF and HCU
A8
Suggested RF configurations
ISSUE 1 REVISION 0
Configuration for
2 cabinet sector
5/5 or 6/6
Figure 7-12 shows a suggested configuration, using two Horizonmacro cabinets, for
sector 5/5 or 6/6 with dual stage duplexed combining filter and air combining.
SECTOR 1
SECTOR 2
2B 1B 0B 2A 1A 0A
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
RX
TX
DDF
2
N01
ANT
N02
N02
FEED
THRU
1
RX RX RX RX RX RX EXT EXT
N01
ANT
N01
ANT
ANT
RX
RX
TX
TX
DDF
DDF
N02
N02
FEED
THRU
1
RX
TX
DDF
0
Figure 7-12 Two cabinet sector 5/5 or 6/6 with DDF and air combining
Unused SMA connectors must be fitted with 50 ohm terminating loads as shown below.
If configured for...
sector 5/5
A9
ISSUE 1 REVISION 0
Suggested RF configurations
Configuration for
single cabinet
sector 1/1/1,
1/1/2, 1/2/2 or
2/2/2
Figure 7-13 shows a suggested configuration, using a single Horizonmacro cabinet, for
sector 1/1/1, 1/1/2, 1/2/2 or 2/2/2 with duplexed combining bandpass filter.
SECTOR 2
SECTOR 3
SECTOR 1
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
N01
N01
ANT
ANT
ANT
RX
RX
RX
DCF
DCF
DCF
Figure 7-13 Single cabinet sector 1/1/1, 1/1/2, 1/2/2 or 2/2/2 with DCF
Unused SMA connectors must be fitted with 50 ohm terminating loads as shown below.
A10
If configured for...
Sector 1/1/1
DCF 0, 1 and 2
Sector 1/1/2
DCF 1 and 2
Sector 1/2/2
DCF 2
Suggested RF configurations
ISSUE 1 REVISION 0
Configuration for
2 cabinet sector
2/2/2
Figure 7-14 shows a suggested configuration, using two Horizonmacro cabinets, for
sector 2/2/2 with duplexed combining bandpass filter.
SECTOR 2
SECTOR 3
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
SECTOR 1
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
N01 N01
ANT
ANT
ANT
RX
RX
RX
BLANK
DCF
BLANK
DCF
BLANK
DCF
0
A11
ISSUE 1 REVISION 0
Suggested RF configurations
Configuration for
2 cabinet sector
3/3/3 or 4/4/4
Figure 7-15 shows a suggested configuration, using two Horizonmacro cabinets, for
sector 3/3/3 or sector 4/4/4 with duplexed combining bandpass filter and air combining.
SECTOR 1
SECTOR 3
2B 1B 0B 2A 1A 0A
SECTOR 2
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
ANT
ANT
RX RX RX RX RX RX EXT EXT
N01 N01
N01
N01
ANT
N01 N01
ANT
ANT
ANT
RX
RX
RX
RX
RX
RX
DCF
DCF
DCF
DCF
DCF
DCF
CABINET 2
CABINET 1
N03
N03
Figure 7-15 Two cabinet sector 3/3/3 or sector 4/4/4 with DCF and air combining
Unused SMA connectors must be fitted with 50 ohm terminating loads as shown below.
A12
If configured for...
sector 3/3/3
cabinet 1, DCF 1
cabinet 2, DCF 0 and DCF 2
Suggested RF configurations
ISSUE 1 REVISION 0
Configuration for
2 cabinet sector
4/4/4
Figure 7-16 shows a suggested configuration, using two Horizonmacro cabinets, for
sector 4/4/4 with dual stage duplexed combining filter and hybrid combining unit.
SECTOR 1
SECTOR 3
2B 1B 0B 2A 1A 0A
SECTOR 2
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
ANT
N02
RX RX RX RX RX RX EXT EXT
N01
TX
RX
ANT
TX
RX
TX
ANT
TX
TX
N02
RX
TX
HCU
DDF
HCU
DDF
HCU
DDF
N04
N03
N03
Figure 7-16 Two cabinet sector 4/4/4 with DDF and HCU
A13
ISSUE 1 REVISION 0
Suggested RF configurations
Configuration for
3 cabinet sector
4/4/4
Figure 7-17 shows a suggested configuration, using three Horizonmacro cabinets, for
sector 4/4/4 with dual stage duplexed combining filter and hybrid combining unit.
SECTOR 3
SECTOR 1
2B 1B 0B 2A 1A 0A
SECTOR 2
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
ANT
BLANK
2
HCU
1
RX RX RX RX RX RX EXT EXT
N01
TX
N02
ANT
RX
TX
N02
RX
TX
TX
DDF
DDF
BLANK
2
2B 1B 0B 2A 1A 0A
HCU
1
RX RX RX RX RX RX EXT EXT
N01
ANT
TX
N02
RX
TX
BLANK
2
HCU
1
DDF
0
Figure 7-17 Three cabinet sector 4/4/4 with DDF and HCU
A14
Suggested RF configurations
ISSUE 1 REVISION 0
Configuration for
sector 5/5/5 or
6/6/6
Figure 7-18 shows a suggested configuration, using three Horizonmacro cabinets, for
sector 5/5/5 or sector 6/6/6 with dual stage duplexed combining filter and air combining.
SECTOR 3
SECTOR 1
2B 1B 0B 2A 1A 0A
SECTOR 2
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
RX
DDF
2
N01
N02
FEED
THRU
1
N01
ANT
ANT
N02
TX
RX RX RX RX RX RX EXT EXT
N01
ANT
RX
RX
TX
TX
DDF
DDF
2B 1B 0B 2A 1A 0A
ANT
N02
N02
FEED
THRU
1
RX
TX
DDF
0
RX RX RX RX RX RX EXT EXT
N01
N01
ANT
RX
TX
DDF
2
ANT
N02
N02
FEED
THRU
1
RX
TX
DDF
0
Figure 7-18 Sector 5/5/5 or sector 6/6/6 with DDF and air combining
Unused SMA connectors must be fitted with 50 ohm terminating loads as shown below.
If configured for...
sector 5/5/5
A15
ISSUE 1 REVISION 0
Suggested RF configurations
Configuration for
sector 8/8/8
Figure 7-19 shows a suggested configuration, using four Horizonmacro cabinets, for
sector 8/8/8 with dual stage duplexed combining filter, hybrid combining unit and air
combining.
SECTOR 3
SECTOR 1
2B 1B 0B 2A 1A 0A
SECTOR 2
RX RX RX RX RX RX EXT EXT
N01
RX
N01
ANT
N02
TX
TX
RX RX RX RX RX RX EXT EXT
N01
ANT
2B 1B 0B 2A 1A 0A
N01
ANT
RX
RX
TX
TX
ANT
TX
N02
RX
TX
DDF
HCU
DDF
DDF
HCU
DDF
N04
N03
N03
N03
N03
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
2B 1B 0B 2A 1A 0A
RX RX RX RX RX RX EXT EXT
N01
N01
ANT
TX
RX
ANT
N02
TX
TX
N02
TX
N04
RX
TX
TX
HCU
DDF
HCU
HCU
DDF
HCU
0
N03
N03
Figure 7-19 Sector 8/8/8 with DDF, HCU and air combining
A16
Suggested RF configurations
ISSUE 1 REVISION 0
Configuration for
dual band
1/1/1-3/3/3
Figure 7-20 shows a suggested configuration, using two Horizonmacro cabinets, for dual
band sector 1/1/13/3/3 operation, where sector 1/1/1 is EGSM 900 and sector 3/3/3 is
DCS 1800. This dual band configuration requires one 1800 SURF and one 900 SURF
(dual band).
SECTOR 3
900
SECTOR 2
900
SECTOR 1
900
1800
OB
2B 1B 0B
1800
OA
2A 1A 0A
RX RX RX RX RX RX RX RX EXT EXT
N01
N01
ANT
RX
RX
N01 N01
RX
RX
N01
RX
ANT ANT
900 1800
ANT ANT
1800
DCF
DUAL
BAND
TDF
900
TDF
SECTOR 3
1800
SECTOR 2
1800
2B 1B 0B 2A 1A 0A
SECTOR 1
1800
RX RX RX RX RX RX EXT EXT
N01 N01
ANT
ANT
RX
N02
N02
RX
TX
TX
1800
DDF
FEED
THRU
1800
DDF
A17
ISSUE 1 REVISION 0
Suggested RF configurations
A18
Glossary of Terms
ISSUE 1 REVISION 0
ii
ISSUE 1 REVISION 0
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A .........................................................................
B .........................................................................
C .........................................................................
D .........................................................................
13
E .........................................................................
16
F .........................................................................
18
G .........................................................................
20
H .........................................................................
22
I ..........................................................................
23
K .........................................................................
25
L .........................................................................
26
M .........................................................................
28
N .........................................................................
32
O .........................................................................
34
P .........................................................................
36
Q .........................................................................
39
R .........................................................................
40
S .........................................................................
43
T .........................................................................
47
U .........................................................................
50
V .........................................................................
51
W ........................................................................
52
X .........................................................................
53
Z .........................................................................
54
iii
ISSUE 1 REVISION 0
iv
Numbers
ISSUE 1 REVISION 0
Numbers
Number.
2 Mbit/s link
4GL
Glos1
ISSUE 1 REVISION 0
Glos2
A interface
A3
A38
A5
A8
AB
Access Burst.
Abis interface
ABR
acdc PSM
ac
Alternating Current.
AC
AC
Application Context.
ACC
ACCH
ACK, Ack
ACKnowledgement.
ACM
ACM
ACPIM
AC PSM
ACSE
ACU
A/D
ADC
ADministration Centre.
ADC
ADCCP
ADM
ADMinistration processor.
ADMIN
ADMINistration.
ADN
ADPCM
AE
Application Entity.
AEC
AEF
ISSUE 1 REVISION 0
AET
AFC
AFN
AGC
AGCH
Ai
Action indicator.
AI
Artificial Intelligence.
AIB
AIO
A class of processor.
Air interface
AM
Amplitude Modulation.
AMA
AM/MP
AoC
Advice of Change.
AoCC
AoCI
AOC
AP
Application Process.
ARFCN
ARQ
ARP
ASCE
ASE
ASE
ASN.1
ASP
ASR
ATB
ATI
ATT (flag)
ATTach.
ATTS
AU
Access Unit.
AuC
Glos3
ISSUE 1 REVISION 0
Glos4
AUT(H)
AUThentication.
AUTO
AUTOmatic mode.
ISSUE 1 REVISION 0
B Interface
BA
BAIC
BAOC
BBBX
BBH
BCC
BCCH
BCD
BCF
Base station Control Function. The GSM term for the digital
control circuitry which controls the BTS. In Motorola cell sites
this is a normally a BCU which includes DRI modules and is
located in the BTS cabinet.
BCIE
BCU
BCUP
BER
BES
BFI
BHCA
BI
BIB
BICRoam
BIM
Bin
BL
BLLNG
BiLLiNG.
bit/s
Bm
BN
BPF
Bandpass Filter.
BPSM
Glos5
ISSUE 1 REVISION 0
Glos6
BS
BS
BSC
BSG
BSIC
BSIC-NCELL
BSP
BSN
BSS
BSSAP
BSSC
BSSMAP
BSSOMAP
BSU
Base Station Unit shelf. The shelf which houses the digital
control modules for the BTS (p/o BTS cabinet) or BSC (p/o
BSSC cabinet).
BT
British Telecom.
BT
Bus Terminator.
BTC
BTF
BTP
ISSUE 1 REVISION 0
BTS
Burst
Glos7
ISSUE 1 REVISION 0
Glos8
Conditional.
C Interface
C7
CA
CA
Central Authority.
CAB
Cabinet.
CADM
CAI
CAT
CB
Cell Broadcast.
CB
Circuit Breaker.
CBC
CBCH
CBF
CBL
CBM
CBMI
CBSMS
CBUS
Clock Bus.
CC
CC
Country Code.
CC
Call Control.
CCB
CCBS
CCCH
CCCH_GROUP
CCD
CCDSP
CCF
CCH
CCH
ISSUE 1 REVISION 0
CCIT
CCM
CCP
Capability/Configuration Parameter.
CCPE
CCS
Cct
Circuit.
CDB
CDE
CDR
CDUR
Chargeable DURation.
CEB
CED
CEIR
Cell
1 Cell =
1 Sector
Omni Site
1-Cell Site
(1 BTS)
6-Sector Site
or
6-Cell Site
(6 BTSs)
CEND
CEPT
CERM
CF
Conversion Facility.
CF
CFB
CFC
CFNRc
CFNRy
Glos9
ISSUE 1 REVISION 0
Glos10
CFU
Channel
CIM
CHP
CHarging Point.
CHV
CKSN
CI
CI
CUG Index.
CIC
CIR, C/I
Ciphertext
CKSN
CLI
CLIP
CLIR
CLK
Clock.
CLKX
Clock Extender half size board. The fibre optic link that
distributes GCLK to boards in system (p/o BSS etc).
CLM
Connectionless Manager.
CLR
CLeaR.
CM
CM
Connection Management.
CMD
CoMmanD.
CMM
CMIP
CMISE
CMR
CNG
CalliNg tone.
COLI
Collocated
Coincident Cell
COLP
ISSUE 1 REVISION 0
COLR
CODEX
COM
COM
COMplete.
COMB
Combiner.
CONNACK
CONNect ACKnowledgement.
COMM, Comms
COMMunications.
CommsLink
CONF
CONFerence circuit.
CONFIG
CP
Call Processing.
CPU
C/R
CR
CR
CRC
CRE
CREF
CRM
CRM-LS/HS
CRT
CSFP
CSP
CSPDN
CT
CT
Channel Tester.
CT
Channel Type.
CTP
CTR
CTS
CTU
CUG
Cumulative value
CW
Glos11
ISSUE 1 REVISION 0
Glos12
D Interface
D/A
DAB
DAC
DACS
DAN
DAS
DAT
DataGen
dB
DB
DataBase.
DB
DBA
DBMS
dc
Direct Current.
DCB
DCCH
DCD
DCE
DCF
DCF
DCN
DC PSM
DCS1800
DDF
DDS
DDS
DDS
DEQB
DET
DETach.
DFE
DGT
ISSUE 1 REVISION 0
DHP
DIA
DINO E1/HDSL
DINO T1
DISC
DISConnect.
Discon
Discontiuous.
DIQ
DIR
DL
DLCI
DLD
DLNB
DLSP
DLSP
Dm
DMA
DMA
DMR
DMX
DN
Directory Number.
DNIC
Downlink
DP
Dial/Dialled Pulse.
DPC
DPC
DPNSS
DPP
DPR, DPRAM
DPSM
DRAM
DRC
DRCU
(D)RCU
Glos13
ISSUE 1 REVISION 0
Glos14
DRI
DRIM
DRIX
DRI Extender half size board. Fibre optic link from DRI to
BCU (p/o BSS).
DRX, DRx
DS-2
DSE
DSI
DSP
DSS1
DSSI
DTAP
DTE
DTF
DT1
DTI
DTMF
DTR
DTRX
DTX, DTx
Dummy burst
DYNET
ISSUE 1 REVISION 0
See Erlang.
E Interface
EA
External Alarms.
EAS
Eb/No
EBCG
EC
ECB
ECID
ECM
Ec/No
ECT
ECT
EEL
EEPROM
EGSM900
Extended GSM900.
EI
EIR
EIRP
EIRP
EL
Echo Loss.
EM
EMC
ElectroMagnetic Compatibility.
EMF
EMI
eMLPP
EMMI
EMU
EMX
en bloc
EOT
End of Tape.
EPROM
Glos15
ISSUE 1 REVISION 0
Glos16
EPSM
EQB
EQCP
EQ DSP
Erlang
ERP
ERP
ERR
ERRor.
ESP
Electro-static Point.
ESQL
E-TACS
Ethernet
ETR
ETS
ETSI
ETX
End of Transmission.
EXEC
Executive Process.
ISSUE 1 REVISION 0
F Interface
FA
Fax Adaptor.
FA
Full Allocation.
FA
Functional Area.
FAC
FACCH
FACCH/F
FACCH/H
FB
FC-AL
FCCH
FCP
FCS
FDM
FDMA
FDN
FDP
FEC
FEP
FER
FFS, FS
FH
Frequency Hopping.
FIB
FIR
FK
FM
FM
Frequency Modulation.
FMIC
FMUX
FN
FOA
FOX
FR
Glos17
ISSUE 1 REVISION 0
Glos18
FRU
Frequency correction
FS
Frequency Synchronization.
FSL
FSN
FTAM
ftn
forwarded-to number.
FTP
FTP
ISSUE 1 REVISION 0
G Interface
Gateway MSC
GB, Gbyte
Gigabyte.
GBIC
GCLK
Generic Clock board. System clock source, one per site (p/o
BSS, BTS, BSC, IWF, RXCDR).
GCR
GDP
GDP E1
GDP T1
GHz
Giga-Hertz (109).
GID
GMB
GMR
GMSC
GMSK
GND
GrouND.
GOS
Grade of Service.
GPA
GPC
GPROC
GPROC2
GPRS
GPS
GSA
GSA
GSM
GSM
GSM MS
GSM PLMN
Glos19
ISSUE 1 REVISION 0
Glos20
GSR
GT
Global Title.
GTE
Guard period
GUI
GUI client
GUI server
GWY
ISSUE 1 REVISION 0
H Interface
H-M
Human-Machine Terminals.
HAD, HAP
HANDO, Handover
HCU
HDLC
HDSL
HLC
HLR
HMS
HO
HPU
HOLD
HPLMN
Home PLMN.
HR
HS
HandSet.
HSI/S
HSM
HSN
HU
Home Units.
HW
Hardware.
Hyperframe
Glos21
ISSUE 1 REVISION 0
Glos22
IA
IA5
International Alphanumeric 5.
IADU
IAM
IAS
IC
Integrated Circuit.
IC
IC(pref)
ICB
ICC
ICM
In-Call Modification.
ICMP
ID, Id
IDentification/IDentity/IDentifier.
IDN
IDS
IE
IEC
IEEE
IEI
I-ETS
IF
Intermediate Frequency.
IFAM
IM
InterModulation.
IMACS
IMEI
IMM
IMSI
IN
Intelligent Network.
IN
INS
IN Service.
ISSUE 1 REVISION 0
INS
InterAlg
Interworking
Interval
Interval expiry
I/O
Input/Output.
IOS
IP
Initialisation Process.
IP
Internet Protocol.
IPC
Inter-Process Communication.
IP, INP
INtermodulation Products.
IPR
Intellectual PRoperty.
IPSM
IPX
(A hardware component).
ISAM
ISC
ISDN
ISG
ISO
ISQL
ISUP
IT
ITC
ITU
ITUTSS
IWF
IWMSC
InterWorking MSC.
IWU
InterWorking Unit.
Glos23
ISSUE 1 REVISION 0
Glos24
kilo (103).
Windows size.
KAIO
kb, kbit
kilo-bit.
kbit/s, kbps
kbyte
kilobyte.
Kc
kHz
kilo-Hertz (103).
Ki
KIO
A class of processor.
KSW
KSWX
kW
kilo-Watt.
ISSUE 1 REVISION 0
L1
Layer 1.
L2ML
L2R
L2R BOP
L2R COP
L3
Layer 3.
LA
LAC
LAI
LAN
LANX
LAPB
LAPD
LAPDm
LC
LCF
LCN
LCP
LE
Local Exchange.
LED
LF
Line Feed.
LI
Length Indicator.
LI
Line Identity.
LLC
Lm
LMP
LMS
LMSI
LMT
LNA
LND
Glos25
ISSUE 1 REVISION 0
Glos26
Location area
LPC
LPLMN
Local PLMN.
LR
LSSU
LSTR
LTA
LTE
LTP
LTU
LU
Local Units.
LU
Location Update.
LV
ISSUE 1 REVISION 0
Mandatory.
Mega (106).
M-Cell
Motorola Cell.
M&TS
MA
MAC
MACN
Macrocell
MAF
MAH
MAI
MAIDT
MAINT
MAINTenance.
MAIO
MAP
MAPP
MB, Mbyte
Megabyte.
Mbit/s
MCAP
MCC
MCDF
MCI
MCSC
MCU
MCUF
MCU-m
MCUm
MD
Mediation Device.
MDL
ME
Glos27
ISSUE 1 REVISION 0
Glos28
ME
MEF
MF
MultiFrame.
MF
MF
MultiFunction block.
MGMT, mgmt
Management.
MGR
Manager.
MHS
MHS
MHz
Mega-Hertz (106).
MI
Maintenance Information.
MIB
MIC
Microcell
min
minute(s).
ms
micro-second (106).
mBCU
MIT
MM
Man Machine.
MM
Mobility Management.
MME
MMF
MMI
MMI client
MMI processor
MMI server
MML
MMS
MNC
MNT
MaiNTenance.
ISSUE 1 REVISION 0
MO
Mobile Originated.
MO/PP
MOMAP
Motorola OMAP.
MoU
Memorandum of Understanding.
MPC
MPH
MPTY
MPX
MultiPleXed.
MRC
MRN
MRP
MS
MSC
MSCM
MSCU
msec
MSI
MSIN
MSISDN
MSRN
MSU
MT
MT (0, 1, 2)
MTM
Mobile-To-Mobile (call).
MTP
MT/PP
MTBF
MTK
MTL
Glos29
ISSUE 1 REVISION 0
Glos30
MTP
MTTR
Multiframe
MU
Mark Up.
MUMS
MUX
Multiplexer.
ISSUE 1 REVISION 0
N/W
Network.
NB
NBIN
NCC
NCELL
NCH
Notification CHannel.
ND
NDC
NDUB
NE
NEF
NET
NETPlan
NF
Network Function.
NFS
NHA
NIC
NIC
NIS
NIU
NIU-m
NLK
Nm
Newton metres.
NM
NMASE
NMC
NMSI
NMT
NN
Normal burst
NPI
Glos31
ISSUE 1 REVISION 0
Glos32
NRZ
NSAP
NSP
NSS
NT
Network Termination.
NT
Non Transparent.
NTAAB
NUA
NUI
NUP
NV
NonVolatile.
NVRAM
nW
Nano-Watt (109).
ISSUE 1 REVISION 0
Optional.
OA
O&M
OASCU
OCB
OCXO
OD
OFL
% OverFlow.
offline
online
OIC
OLM
OLR
OMAP
OMC
OMC-G
OMC-G
OMC-R
OMC-S
OMF
OML
OMP
OMS
OMSS
OOS
Out Of Service.
OPC
ORAC
OS
Operating System.
OSI
OSI RM
OSF
Glos33
ISSUE 1 REVISION 0
Glos34
OSF/MOTIF
OSS
Overlap
Overlap sending means that digits are sent from one system
to another as soon as they are received by the sending
system. A system using ~ will not wait until it has received all
digits of a call before it starts to send the digits to the next
system. This is the opposite of en bloc sending where all
digits for a given call are sent at one time.
ISSUE 1 REVISION 0
PA
Power Amplifier.
PAB
PABX
PAD
Paging
PATH
PBUS
Processor Bus.
PBX
PC
Personal Computer.
PCH
PCHN
PCHN
Physical Channel.
PCM
PCN
PCR
PCU
PCU
pd
Potential difference.
PD
Protocol Discriminator.
PD
Public Data.
PDB
PDN
PDU
PDU
PEDC
Peg
Pegging
PH
Packet Handler.
PH
PHysical (layer).
PHI
PI
Presentation Indicator.
Picocell
PICS
Glos35
ISSUE 1 REVISION 0
Glos36
PID
PIM
PIN
PIN
PIX
PIXT
PK
Plaintext
Unciphered data.
PlaNET
PLL
PLMN
PM
PM-UI
PMA
PMS
Pseudo MMS.
PMUX
PCM MUltipleXer.
PN
PNE
POI
POTS
p/o
Part of.
pp, p-p
Peak-to-peak.
PP
Point-to-Point.
ppb
PPE
ppm
Pref CUG
Preferential CUG.
Primary Cell
PROM
Ps
Location probability.
PSA
PSAP
PSM
ISSUE 1 REVISION 0
PSPDN
PSTN
PSU
PSW
PTO
PUCT
PVC
PW
Pass Word.
PWR
Power.
PXPDN
Glos37
ISSUE 1 REVISION 0
Glos38
QA
Q (Interface) Adapter.
Q3
Q-adapter
QAF
Q-Adapter Function.
QEI
QIC
QOS
Quality Of Service.
Quiescent mode
ISSUE 1 REVISION 0
RA
RAB
RACCH
RACH
RAM
RAND
RATI
RAx
Rate Adaptation.
RBDS
RBER
RBTS
RCB
RCI
RCP
RCU
RCVR
Receiver.
RDBMS
RDI
RDIS
RDM
RDN
REC, Rec
RECommendation.
REJ
REJect(ion).
REL
RELease.
RELP
RELP-LTP
RELP Long Term Prediction. A name for GSM full rate (see
full rate).
resync
Resynchronize/resynchronization.
REQ
REQuest.
Revgen
RF
Radio Frequency.
Glos39
ISSUE 1 REVISION 0
Glos40
RFC, RFCH
RFE
RFEB
RFI
RFM
RFN
RFU
RJ45
RISC
RL
Remote login.
RLC
Release Complete.
RLP
RLR
RLSD
ReLeaSeD.
RMS
RMSU
RNTABLE
ROM
ROSE
Roundtrip
RPE
RPE-LTP
RPOA
RPR
RR
RR
RRSM
RS232
RSE
RSL
RSLF
RSLP
RSS
RSSI
ISSUE 1 REVISION 0
RSZI
RTC
RTE
RTF
RTF
RTS
RU
Rack Unit.
Run level
Rx
Receive(r).
RXCDR
Remote Transcoder.
RXF
RXLEV-D
RXLEV-U
RXQUAL-D
RXQUAL-U
RXU
Glos41
ISSUE 1 REVISION 0
Glos42
S/W
SoftWare.
SABM
SABME
SABM Extended.
SACCH
SACCH/C4
SACCH/C8
SACCH/T
SACCH/TF
SACCH/TH
SAGE
SAP
SAP
SAPI
SAW
SB
SBUS
Serial Bus.
SC
SC
Service Code.
SCCA
SCCP
SCEG
SCH
SCI
SCIP
SCM
SCN
SCP
SCSI
SCU
SCU900
SDCCH
ISSUE 1 REVISION 0
SDL
SDT
SDU
SDR
SE
Secondary Cell
SEF
SFH
SI
Screening Indicator.
SI
Service Interworking.
SI
Supplementary Information.
SIA
Supplementary Information A.
SID
Silence Descriptor.
SIF
SIM
SIMM
SIMM
SIO
SITE
SIX
SK
SL
Signalling Link.
SLNK
Serial Link.
SLR
SLTM
SM
Switch Manager.
SM
Summing Manager.
SMAE
SMCB
Glos43
ISSUE 1 REVISION 0
Glos44
SME
SMG
SMP
SMS
SMSCB
SMS-SC
SMS/PP
Smt
SN
Subscriber Number.
SND
SeND.
SNDR
SeNDeR.
SNR
Serial NumbeR.
SOA
SP
SP
Signalling Point.
SP
Special Product.
SP
SPare.
SPC
SPC
SPI
SPP
SQE
SQL
SRD
SRES
SS
SS
System Simulator.
SSA
SSAP
SSC
SSF
SSM
SSN
SubSystem Number.
SSP
SSP
SSP
ISSUE 1 REVISION 0
SSS
SS7
STAN
STAT
STATistics.
stats
Statistics.
STC
STMR
SUERM
STP
Superframe
Super user
SURF
SVC
SVM
SerVice Manager.
SVN
SW
Software.
SWFM
sync
synchronize/synchronization.
Synchronization burst
SYS
SYStem.
SYSGEN
Glos45
ISSUE 1 REVISION 0
Glos46
Timer.
Transparent.
Type only.
T43
TA
TA
Timing Advance.
TAC
TACS
TAF
TATI
TAXI
TBD
To Be Determined.
TBR
TBUS
TDM Bus.
TC
Transaction Capabilities.
TCAP
TCB
TCH
TCH/F
TCH/F2.4
TCH/F4.8
TCH/F9.6
TCH/FS
TCH/H
TCH/H2.4
TCH/H4.8
TCH/HS
TCI
TCP/IP
TC-TR
TCU
TDF
TDM
ISSUE 1 REVISION 0
TDMA
TDU
TE
Tei
TEI
TEMP
TEMPorary.
TEST
TFA
TransFer Allowed.
TFP
TransFer Prohibited.
TFTP
TI
Transaction Identifier.
Timeslot
Timing advance
TLV
TM
Traffic Manager.
TMI
TMM
TMN
TMSI
TN
Timeslot Number.
TON
Type Of Number.
Traffic channels
Traffic unit
Equivalent to an erlang.
Training sequence
TRAU
TRU
TRX
TS
Technical Specification.
Glos47
ISSUE 1 REVISION 0
Glos48
TS
TeleService.
TS
TSA
TimeSlot Acquisition.
TSA
TimeSlot Assignment.
TSDA
TSC
TSI
TimeSlot Interchange.
TSDI
TSM
TSW
Timeslot SWitch.
TTCN
TTL
TTY
TU
Traffic Unit.
TUP
TV
Tx
Transmit(ter).
TXF
TXPWR
TxBPF
ISSUE 1 REVISION 0
UA
UDI
UDP
UDUB
UHF
UI
UIC
UID
UL
Um
Air interface.
UMTS
UPCMI
UPD
Up to Date.
Uplink
UPS
UPU
USSD
UUS
Glos49
ISSUE 1 REVISION 0
Glos50
Value only.
VA
VAD
VAP
VBS
VC
Virtual Circuit.
VCO
VCXO
VDU
VGCS
VLR
VLSI
VMSC
VOX
VPLMN
Visited PLMN.
VSC
V(SD)
VSP
VSWR
VTX host
ISSUE 1 REVISION 0
WAN
WPA
WS
WSF
WWW
Glos51
ISSUE 1 REVISION 0
Glos52
X.25
X.25 link
XBL
XCB
XCDR
XCDR board
XFER
Transfer.
XID
eXchange IDentifier.
X-Term
X terminal window.
ISSUE 1 REVISION 0
Z
ZC
Zone Code
Glos53
ISSUE 1 REVISION 0
Glos54