PCU

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5
CHAPTER 6 CHAPTER 7 ANNEX A ANNEX B GLOSSARY

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5
Toolbag PCU
TG03 Version 1 Rev 1

Training Manual
GSM Software Release 5
FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

GSM Software Release 5
Version 1 Rev 1
TG03
Training Manual
Toolbag PCU
Toolbag PCU
TG03
Training
Positin mark for TED spine
Manual
Version 1 Rev 1
FOR TRAINING
PURPOSES ONLY
THIS MANUAL WILL
NOT BE UPDATED
Version 1 Rev 1
Software Release GSR5
TG03
Toolbag PCU
Motorola 2002
All Rights Reserved
Printed in the U.K.
MOTOROLA LTD. 2002 TG03: Toolbag PCU i

Version 1 Rev 1
Copyrights, notices and trademarks
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer
programs stored in semiconductor memories or other media. Laws in the United States and other
countries preserve for Motorola certain exclusive rights for copyright computer programs, including the
exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any
copyright Motorola computer programs contained in the Motorola products described in this document
may not be copied or reproduced in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by
implication, estoppel or otherwise, any license under the copyrights, patents or patent applications of
Motorola, except for the rights that arise by operation of law in the sale of a product.
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
and MOTOROLA are registered trademarks of Motorola Inc.

intelligence everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
.
ii TG03: Toolbag PCU MOTOROLA LTD. 2002

Version 1 Rev 1
Contents
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 1
Chapter title goes here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
. ......................................................................... 11
. .................................................................... 11
. ......................................................................... 13
. .................................................................... 13
Chapter 2
Chapter title goes here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
. ......................................................................... 21
. .................................................................... 21
. ......................................................................... 23
. .................................................................... 23
Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . G1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I1
MOTOROLA LTD. 2002 TG03: Toolbag PCU iii

Version 1 Rev 1 General information
General information
Important notice
If this manual was obtained when attending 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 cellular communications manuals are intended to instruct and assist personnel
in the operation, installation and maintenance of the Motorola cellular infrastructure
equipment and ancillary devices. It is recommended that all personnel engaged in such
activities be properly trained by Motorola.
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.
MOTOROLA LTD. 2002 TG03: Toolbag PCU 1

General information Version 1 Rev 1
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.
Special key sequences

Special key sequences are represented as follows:
CTRL-c Press the Control and c keys at the same time.

ALT-f Press the Alt and f keys at the same time.
| Press the pipe symbol key.
CR or RETURN Press the Return (Enter) key. The Return key is
identified with the symbol on both the X terminal and
the SPARCstation keyboards. The SPARCstation
keyboard Return key is also identified with the word
Return.
2 TG03: Toolbag PCU MOTOROLA LTD. 2002

Version 1 Rev 1 First aid in case of electric shock
First aid in case of electric shock
Warning
WARNING Do not touch the victim with your bare hands until the
electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry
insulating material and pull or push the victim clear of the
conductor.
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. Do not attempt to remove clothing adhering to the burn.
2. If help is available, or as soon as artificial respiration is no longer required, cover
the wound with a dry dressing.
3. Do not apply oil or grease in any form.

Reporting safety issues Version 1 Rev 1
Reporting safety issues
Introduction
Whenever a safety issue arises, carry out the following procedure in all instances.
Ensure that all site personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
1. Make the equipment concerned safe, for example, by removing power.
2. Make no further attempt to tamper with the equipment.
3. Report the problem directly to the Customer Network Resolution Centre, Swindon
+44 (0)1793 565444 or China +86 10 68437733 (telephone) and follow up with a
written report by fax, Swindon +44 (0)1793 430987 or China +86 10
68423633 (fax).
4. Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.

Version 1 Rev 1 Warnings and cautions
Warnings and cautions
Introduction
The following describes how warnings and cautions are used in this manual and in all
manuals of this Motorola manual set.
Warnings
Definition of Warning
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.
Example and format

WARNING Do not look directly into fibre optic cables or 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.
Cautions
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual
items of equipment within a system. However, this presents no danger to personnel.
Example and format

CAUTION Do not use test equipment that is beyond its calibration due date
when testing Motorola base stations.

General warnings Version 1 Rev 1
General warnings
Introduction
Observe the following warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola manuals. Failure to comply with
these warnings, or with specific warnings elsewhere in the Motorola 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 supply which is potentially lethal. Therefore, the areas
where the ac supply 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 ac 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:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human
Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High
Frequency (10 kHz to 300 GHz).
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.

Version 1 Rev 1 General warnings
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 equipment may incorporate components containing the highly toxic material
Beryllium or its oxide Beryllia or both. These materials are especially hazardous if:
Beryllium materials are absorbed into the body tissues through the skin, mouth, or
a wound.
The dust created by breakage of Beryllia is inhaled.
Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
Beryllium warning labels are fitted to equipment incorporating Beryllium or Beryllium
Oxide. Observe all safety instructions given on warning labels.
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 or burnt, the Beryllium Oxide, in the form of dust or fumes, could be
released, with the potential for harm.
Lithium batteries
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective lithium
batteries must not be removed or replaced. Any boards containing defective lithium
batteries must be returned to Motorola for repair.

General cautions Version 1 Rev 1
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the
equipment described in the Motorola manuals. Failure to comply with these cautions or
with specific cautions elsewhere in the Motorola 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.

Version 1 Rev 1 Devices sensitive to static
Devices sensitive to static
Introduction
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied
to the leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into
high insulation packing material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads shorted
together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into
conductive plastic foam. Provided the leads are shorted it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced, observe the following
precautions when handling the replacement:
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.
Take care when removing components connected to electrostatic sensitive
devices. These components may be providing protection to the device.
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.

Chapter 1
PCU Tools

Version 1 Rev 1

Version 1 Rev 1
Chapter 1
PCU Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Module Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Tools Chapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
TCP snoop/Windump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Windump Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Workflow of IP analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Post Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
EtherPeek . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
IP MTU Size & LLC packets in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
TCP 3way Handshake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
TCP Data Flow (Downlink FTP, TCP session) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
TCP Packet loss & Retransmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
TCP retransmission in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Introduction to AGNet Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Usage of AGNet Tools in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Ping Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
MDTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Mobile setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Mobile Installation Setup (Contd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
MDTT Functionality Decode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
User Interface Decode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Layer 3 messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
LLC messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
RLC/MAC messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Complete Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
MDTT Functionality Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Mobile EFEM Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
RTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
K1205 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Radcom/Prismlite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
PrismLite Typical Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Setting up Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Processes Control Frame Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Processes Control Line Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Processes Control Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
GB Snoop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Gbsnoop Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
TCP connection finder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
TCP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
TCP Connection Contd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Excel directed viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
BVC Flow Control Viewer output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
BSS Gather . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Checking the processing buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Excel Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Version 1 Rev 1
iv TG03: Toolbag PCU MOTOROLA LTD. 2002

Version 1 Rev 1 Overview
Overview
Module Objectives
By the end of this module the student will be able to:
Debug simple issues in the field environment.
Select relevant procedures to correct simple faults.
Collect the correct data to enable support team engineers to carry out their tasks in
a more timely manner.
Tools Chapter Objectives

This section will focus on what each of the tools listed below can provide. The detailed
Data collection Section will show how to apply these tools. Note installation and
configuration is outside the scope of this course.
TCP snoop/Windump (TCP analysis tool).
MDTT
K1205
GBSnoop
Radcom
RTA
MS engineering mode, logger bytes.
BSS Gather, Cells Barred Utility.
AGNet.

TCP snoop/Windump Version 1 Rev 1
TCP snoop/Windump
TCP Snoop is a Unix/Solaris IP analysis tool and Windump is the Windows based
version. The Tool will capture IP packets and is commonly used in GPRS to undertake
FTP Investigations.
TCP Snoop is available by default when Solaris is installed. Windump must be obtained
and installed. It can be obtained as freeware from http://windump.polito.it/
TCP Dump will produce a text output to indicate IP activity.
TCP snoop can also be run on a client or server machine.

Version 1 Rev 1 TCP snoop/Windump
TCP Snoop

Diagran Number
Figure 1-1

Windump Output
The command windump D will display all the logical ports on the Windows machine.
The command i 4 w will specify the port to be listened to and reported on. The output
file is then specified. All packets will be reported to the output file, and no activity is seen
on the Windows machine.
Ctlc will stop the process.

Windump packet recording
$ windump h
windump version 3.6.2, based on tcpdump version 3.6.2
WinPcap version 2.3, based on libpcap version 0.6.2
Usage: windump [ adDeflnNOpqStuvxX ] [ B size] [ c count] [ F file ]
[ i interface ] [ r file ] [ s snaplen ]
[ T type ] [ w file ] [ expression ]
$ windump D
1. \ Device \ Packet_{F5F93E62 7F00 4BAC 825E B8975C824B71} (Unknown)
2. \ Device \ Packet_{ACA4BD5B 5A19 46A6 A520 BAE73DC095B1} (Unknown)
3. \ Device \ Packet_{DB65E070 52B9 4577 A43A 5302F8F1B76A} (NOC Extranet Access Adapter)
4. \ Device \ Packet_{8B16CD81 8635 4122 BF5D 72562EAF4315} (3Com EtherLink PCI)
5. \ Device \ Packet_{E06DE95D D5CF 480F 9CEA 02442F94F2B1} (Xircom CardBus Ethernet 10/1
Adapter)
6. \ Device \ Packet_{88DFF086 42F6 47BB 9917 6C69B2617F45} (Unknown)
7. \ Device \ Packet_ NdisWanIp ( NdisWan Adapter)
$ windump i 4 w outputfile . dmp

windump : listening on \ Device \ Packet_{8B16CD81 8635 4122 BF5D 72562EAF4315}
CTRL C
5168 packets received by filter
0 packets dropped by kernel
Figure 1-2

Workflow of IP analysis.
The output file from windump or TCP snoop should then be run through TCPTrace
(available from http://www.tcptrace.org).
This can then be run through a third program called Xplot to obtain a graphical
representation. This is available from http://masaka.cs.ohiou.edu/software/tcptrace/jPlot/.

Workflow of IP Analysis
##$!
" $!$
" !#
"#!#'"
'"#
#"
#&#' #" $!
"''#!"%

!
Use Xplot (Unix flavour #'" "
only) or jPlot (in Java) to %
display time sequence
graph
Figure 1-3

Post Processing
The screen shot opposite shows the throughput of data during a cell reselection. Several
re transmission requests are sent before the data transfer resumes and is finally
completed.

TCP snoop/Windump (TCP analysis tool) Post Processing.
Figure 1-4

EtherPeek Version 1 Rev 1
EtherPeek
Etherpeek is a network and protocol analysis tool designed to help for troubleshooting,
optimise, plan and configure a network. It includes many Graphical displays and
statistics windows that describe the composition of traffic on a GPRS network.
Becoming familiar with network usage patterns can alert you to potential performance
and configuration problems, and provide you with the information to quickly identify and
remedy ananomalous network condition.

Version 1 Rev 1 EtherPeek
Etherpeek
Figure 1-5

LLC packet size in GPRS

IP Datagrams are (de)fragmented into LLC frames. LLC frame size is unchangeable at
the moment (limited by the mobile).
As the IP datagram size is changeable, then it should be tailored so it will fit efficiently
into units of LLC frames.
So ideally there will be no LLC frames with low, occupancy of data space.
This output is gained by running the Etherpeek results through Excel.

LLC Frame size in GPRS
IP Datagram
(de)fragmentation process
LLC Frame LLC Frame LLC Frame
Figure 1-6

TCP 3way Handshake

TCP connection establishment
Packet 1. The requesting end (client) sends SYN segment, plus the
initial sequence number (ISN).
Packet 2. The server sends the SYN, acknowledging clients SYN
(clients ISN + 1), plus its own ISN.
Packet 3. The client sends acknowledgment (servers ISN + 1)
Another info exchanged in the connection establishment is Maximum
Segment Size (largest chunk of TCP data that the receiver expect from
the other end). Both ends advertise its window size.

TCP 3way Handshake
Diagran Number
Figure 1-7

TCP Data Flow (Downlink FTP, TCP session)

Each segment received should be acknowledged. Done by sending acknowledgement of
senders sequence number+amount of data acknowledging. One acknowledgement can
be sent for several received segments. Each blue bar (segment sent by FTP server) will
never be greater than MSS negotiated between server and client. The FTP server,
initiate TCP 3way handshake (FTP needs 2 TCP sessions, data & control). The 2nd
acknowledgement in 3way handshake (packet #8) is used to indicate the roundtrip time.
The window size is advertised by both parties on each segment, indicating the free
receiving buffer that is still available.

TCP Data Flow (Downlink FTP, TCP session)
594: FTP Server

64 FTP CLient (GPRS Mobile)
Seen from FTP server
perspective
Diagran Number
Figure 1-8

TCP Packet loss & Retransmission

Exponential Backoff: The delta time between retransmission packet is exactly double the
time of the previous retransmission.
The example shows TCP implementation on the source side (win2000) will give up the
connection after 5 consecutive retransmissions.
Packet 22 is the 1st retransmission (of packet 21).
Packet 23 is the retransmission of packet 22.
Packet 24 is the retransmission of packet 23.
And so on.

TCP Packet loss & Retransmission
Diagran Number
Figure 1-9

TCP retransmission in GPRS

TCP Retransmission plays a major role in degrading the throughput. The endtoend
system can still perform properly with single retransmission but not in sequence.
In the examples shown, example one shows bad FTP Throughput, 0.85KBps with17
retransmissions.
Example 2 shows good FTP Throughput, 2.39KBps with no retransmission.

TCP retransmission in GPRS
Example 1 Bad Throughput 0.85Kbps
Example 2. Good Throughput 2.39Kbps
Figure 1-10
Both of the above graphs have an X axis of ms and a Y axis of Bytes. They represent
the same information as the Xplot graph did, in that the top line is the best throughput
available, and the bottom line is the actual thoughput.

Introduction to AGNet Tools Version 1 Rev 1
Introduction to AGNet Tools

AGNet Tools is tool used for IP network diagnostics. It is especially helpful in measuring
GPRS network latency using pings. Includes additional functions like ping scan, trace
route, name lookup, whois, throughput, all of which can be used in GPRS.
In addition to its suite of IP network diagnostic tools, AGNet Tools can present
information about the IP setup of the machine on which it is running.
AGNet Tools is available of the web at www.aggroup.com.
AGnet will not capture live packets.

Version 1 Rev 1 Introduction to AGNet Tools
AGNet Tools
PCU Tools 3
Figure 1-11

Usage of AGNet Tools in GPRS

Ping times the response to echo request (Ping) packets sent to a device of a known
address.
Ping Scan Sends echo request packets to a range of IP addresses to determine which
are currently in use.
Trace Route Identifies the intervening steps (or hops) taken by a series of test packets
on their way from your computer to any destination device with an IP address. Shows the
time required for each hop along the route.
Name Lookup Resolves names to IP addresses or IP addresses to names.
Whois Queries a specified WHOIS server for information about a particular host or other
internet entity.
Throughput Tests the rate at which information is downloaded from a specified FTP or
HTTP server.

PING parameters
Parameter Value Use

Host IP address or The target host to be tested
domain name
Interval milliseconds Interval between individual Ping packets
Timeout milliseconds Time after which nonresponse will mean
that packet is considered lost
Size bytes Payload size for the Ping request packets.
This can be greater than the actual maximum
packet sizes, in which case, the data will
be broken up into multiple packets. AGNet
tools lilmits the maximum payload size to
65535 bytes
Number of Pings A small number should suffice for most
purposes. This option is greyed out when
Continuous is selected
Continuous Yes (checked) or Sends ping packets continuously. If you check
No (unchecked) Continuous, when you click the start button to
initiate the Ping, the Start button becomes a
Stop button. You must use the Stop button to stop
the Ping. This feature is not available in
PCU Tools 4
evaluation mode
Figure 1-12

Ping Results
The results list shows Status and Response Time for each Echo Request (Packet).
Response times are shown in seconds.
The Statistics section at the bottom of the display shows the total number of packets
Sent, Received, and Lost. It also shows the Minimum, Average, and Maximum response
time for received response packets.

Ping Results
Figure 1-13

MDTT Version 1 Rev 1
MDTT
Description
The Motorola Drive Test Tool (MDTT) decodes and displays GSM and GPRS air
interface messages and parameters. It can also use log files to record and subsequently
replay the messages and parameters. The tool helps field engineers to locate problems
in the network.
It allows real time decoding and display of signaling messages.
It is designed to Help Field Engineers and Network Optimisers locate a problem in the
Network.
It has limited capability for GSM as it does not capture layer 1 or 2 messages. However
it captures layer 3 messages which make it suitable for use with GPRS.

Version 1 Rev 1 MDTT
Drive Test Tool System Diagram
GPS Device (NME 0183)
Laptop running Windows

NT/2000 and MDTT

Motorola PCS
PCMCIA
card
Figure 1-14

Mobile setup
The following Mobile software versions are supported by Motorola Drive Test Tool:
SMG 31: AF.7F.BB or higher.
Other legacy SMG 29 and 27 software.
Motorola GSM Phone (e.g. CD920, some of Vseries)
Data logger setup

To enable the data stream from the mobile to the MPLUS card
This can be done using:
TTY serial terminal (Hyperterminal)
Entered manually in test mode
To have both EFEM and test mode in the mobile is recommended for testing.

Mobile Installation Setup
Mobile software version supported by Motorola Drive Test Tool:
SMG 31: Af.7F.BB or higher

Other legacy SMG 29 and 27 Software
Plain Motorola GSM phone (e.g. CD920, Vseries)
Data logger setup
To enable the data stream from the mobile to the

MPLUS card
Can be done using
TTY serial terminal (hyperterminal)

entered manually in test mode
To have both EFEM and test mode in the mobile is recommended
for testing
Toolbag_ PCU_ Mobile Installation Setup
Figure 1-15

Mobile Installation Setup (Contd)
Enabling data logger settings in the test mode

Hold the # key for 2 seconds to enter the test modeEnter the following commands :
730000# 731063#
730170# 731100#
730202# 731200#
730304# 731301#
730480# 731406#
When complete enter 01# to leave the test mode
Command Meaning
65# Displays the International Mobile Subscriber Identify (IMSI) from the
SIM.
60# Display IMEI
19# Display the software version of the call processor
20# Display the software version of the Modem
22# Display the software version of the Speech Decoder
61xxx# Display/modify the MCC portion of the LAI, when xxx not present, then it
will display the current value
62xx# Display/modify the MNC portion of the LAI, when xx not present, then it
will display the current value=
63xxxxx# Display/modify the LAC portion of the LAI, when xxxxx not present, then
it will display the current value
68# It will zero out the forbidden PLMN list in the SIM
800# Display the TLLI
810# Display Multislot class
812# Display the RX Timeslot capability
813# Display the TX timeslot capability

Enabling data logger settings
730000# 731063#
730170# 731100#
730202# 731200#
730304# 731301#
730480# 731406#
Test Mode Commands
Command Meaning
65# Displays the International Mobile Subscriber identity (IMSI) from the SIM
60# Display IMEI
19# Display the software version of the call processor
20# Display the software version of the modem
22# Display the software version of the speech decoder
61xxx# Display/modify the MCC portion of the LAI, when xxx not present, then it
62xx# Display/modify the MNC portion of the LAI, when xx not present, then it will
display the current value
63xxxxx# Display/modify the LAC portion of the LAI, when xxxxx not present, then it
68# It will zero out the forbidden PLMN list in the SIM
800# Display the TLLI
810# Display Multislot class
812# Display the RX Timeslot capability
813# Display the TX Timeslot cabability
PCU_Logger settings_TMC
Figure 1-16
Figure 1-17

System
configuration
MDTT may be installed on a laptop or desktop PC. However, a laptop is essential if drive
tests are to be performed. Before installing the software, check that the system
configuration meets the following requirements:
Operating system: Windows NT4 Service Pack 5 or Windows 2000. Windows 98
not supported.
CPU: Pentium III 500 mHz.
RAM: 256 mb.
Available disk space: 10 mb.
PCMCIA card slot.
CD-ROM Drive.
More details on installation, update, required driver, problem report and latest firmware:
http://fieldeng.euro.csg.mot.com/field_test_tools/mplus/HTML/index.htm
Supported firmware for Motorola drive test tool is MPLUS4C5
To get Mplus card:
Kits Required
M-Plus Lite Kit CD1760A

M-Plus Lite Card 8202327T02
Cable SKN4821B
Test SIM 8102316T02
CD 8202655T01
M-Plus Kit CD1590A

Poly Insert 56C09104R01
M-Plus Card CDLN4321A
Cable SKN4821B
The M-Plus Lite differs from M-Plus as follows:

Use in car kits is NOT supported
No call control via the card is supported
Phone cannot be configured to support logging via card. This has to be done manually
via the keypad using the test SIM supplied.

Basic Installation
Mplus/Lite
PC Card
Figure 1-18

MDTT
Functionality
Decode
Decode GSM/GPRS Layer 3 messages Call Control, Mobility Management,
Radio Resource Messages
Decode RLC/MAC Messages
Decode LLC messages
Complete Decoding of L3, RLC/MAC and LLC Messages
IP Header, SNPDU Header decoding from LLC-UI frames
Decode GPS positioning messages (NMEA-0183 Standard)

Decode
Decode GSM/GPRS Layer 3 messages Call Control, Mobility

Management, Radio Resource Messages
Decode RLC/MAC Messages
Decode LLC messages
Complete Decoding of L3, RLC/MAC and LLC Messages
IP Header, SNPDU Header decoding from LLCUI frames
Decode GPS positioning messages (NMEA0183 Standard)
Figure 1-19

User Interface Decode
Decoded air interface messages

The decoded air interface messages are displayed in the following Decode windows:
Layer 3 messages.
RLC / MAC messages.
LLC messages.
All messages.
Complete message.

User Interface Decode
Figure 1-20

Layer 3
messages
The Layer 3 Messages Decode window displays layer 3 messages received from the
phone. The message structures are specified in ETSI document GSM 04.08. The
following messages are included:
BCCH system information messages of types 1, 2, 2bis, 2ter, 3, 4, 7, 8, 9 and 13.
SACCH system information messages of types 5, 5bis, 5ter and 6.
Channel request messages.
Immediate assignment messages.
Paging request messages of types 1, 2 and 3.
Measurement report messages.
All other layer 3 messages specified in GSM 04.08.

Layer 3 Message Window
Hierarchical display of completely decoded messages

Context menu options to:
Copy data to clipboard
Find messages in the tree
Synchronize all the displayed windows
according to currently selected message
Enable/disable auto scroll
Export to Excel
Clear the window
Figure 1-21

LLC messages
The LLC Messages Decode window displays LLC messages received from the phone.
The message structures are specified in ETSI document GSM 04.64. The following
information is also decoded from LLC frames, when present:
Layer 3 Headers from the LLC-UI frames.
SNPDU Headers from the LLC-UI frames.
IP Headers from the LLC-UI frames.
LLC parameters from the LLC-XID frames.
LLC message window

The LLC message window provides a hierarchical display of completely decoded
messages and a context menu provide the options to:
Synchronize all the displayed windows according to currently selected message
Enable/Disable auto scroll
Export to Excel
Clear window

LLC Message Window
Hierarchical display of completely decoded

messages
Synchronize all the displayed
windows according to currently
selected message
Export to Excel
Clear the window
Figure 1-22

RLC/MAC
messages
The RLC/MAC Messages Decode window displays all RLC/MAC messages received
from the phone. The message structures are specified in ETSI document GSM 04.60.
RLC/MAC message window

The RLC/MAC message window provides a hierarchical display of completely decoded
messages and a context menu provide the options to:
Synchronize all the displayed windows according to currently selected message
Enable/Disable auto scroll
Export to Excel
Clear window

RLC/MAC Message Window
Hierarchical display of completely decoded

messages
Synchronize all the displayed
windows according to currently
selected message
Export to Excel
Clear the window
Figure 1-23

Complete
Message
When a message header is highlighted in one of the four basic Decode windows (Layer
3, RLC/MAC, LLC or All messages), a fully expanded version of that message is
automatically displayed in the Complete Message window.
The Complete Message window only ever contains one expanded message.

Complete Message Window
Hierarchical display of completely decoded messages in

a separate window.
The user can select any message in any of the layer
message windows and a completely detailed decoded
message will be displayed in this window.
Synchronize all the displayed windows according
to currently selected message
Export to Excel
Clear the window
Figure 1-24

MDTT
Functionality
Monitor
Serving Cell Information GSM/GPRS
Neighbouring Cell Information
Radio Parameter Chart Serving Cell/Neighbouring Cell radio parameters
GPRS Uplink/Downlink throughput charts
LLC Parameter display
GPS Data (Time, Latitude, Longitude, Course, Speed, Altitude, etc.)
User Interface Radio Parameters
Decoded monitor parameters

The decoded monitor parameters are displayed in the following Monitor windows:
Serving cell GSM/GPRS.
Serving cell GPRS specific.
Neighbouring cells.
Radio parameter graph.
Uplink data transfer graph.
Downlink data transfer graph.
LLC parameters.
Decoding errors are displayed in the Errors window.

User Interface Radio Parameters
Layer message
window context
menu
Figure 1-25

Mobile EFEM Display
EFEM Enhanced Field Engineering Mode. This is a mode of operation to display field
test information, based on the idle display of the phone. This special mode also allows
the user to partly drive the behaviour of the phone.

Mobile EFEM Display
Toggle
refresh
Favorite
button
Unused Unused
(dialling ) (dialling )
Previous
screen
Next
Screen
Figure 1-26

RTA Version 1 Rev 1
RTA
Overview
Real Time Analyzer is used to acquire, save, replay and analyze data associated with a
mobile phone. It runs in a similar manner to MDTT, except it will capture layer 1 and 2
messages as well as layer 3.
Easy to install, just download from compass http://compass.mot.com/go/pst .
Can be used with USB connection or with a PCMCIA card.
Setup
Logger bits setup
From phone test mode
730016#
731121#
732191#
733133#
734144#
735127#(RLC, LLC, SNDCP & EFEM)
738003#(LLC encryption)
739139#(RLC + decode error)
Initial Startup
Parser configuration. If using parser this must be correct otherwise RTA will
not launch (use rlc.map file).
Logger preferences Check no dump file if preference is no parsing (ie log
only, no analysis).
Device configuration Configure device of choice.
Startup
Initial Logging
Show all primitives (otherwise screen will remain blank)
MS Analysis>Primitives>All logger primitives.

Version 1 Rev 1 RTA
RTA Initial Startup
Diagran Number
Figure 1-27

RTA Version 1 Rev 1
Startup
Now chose playback or start logging from the Log menu option.
During logging there are options to freeze/unfreeze, pause/unpause and stop logging.

Version 1 Rev 1 RTA
Example Window
Diagran Number
Figure 1-28

K1205 Version 1 Rev 1
K1205
Overview
Portable multi protocol tester with ability to monitor multiple interfaces.
Easy operation under Windows NT.
User Friendly help system.
Graphical and flexible protocol stack editor.
Detects interferences in individual network segments.
Does not interfere with network.

Version 1 Rev 1 K1205
Overview
Figure 1-29
MSC/VLR
BTS
SS7
BSC
HLR
Laptop
PSTN
GPRS CISCOSYSTEM
S
1 2 3 4
3
1234
1 2 3 4 12 1 2 3 4 1234 5 6 7 8
1
34 5678
FA
STETH
ERNETIN
PU
T/O
UTPUTCONTR
O
LLERSD
Backbone
FEM
Cisco 7200
II
SGSN GGSN
Series
ER
0
BLED
OKW
IOPOST
CIA
K
T
FE
E
BLE
N
AU
EJEC
0
SLOT
LL
B
PUIR
M
I
A
FEA
PDN
EN
EN
EN
PC
Firewal
GGSN
PCU SGSN

K1205 Version 1 Rev 1
Connection
Connect the cables to the interface to be monitored.
Switch K1205 on.
Choose auto configuration (for LAP based protocols this is dependant on data received
during a measurement interval).
Active signal channels available, measurements can now start.
Monitoring
Click the relevant on/off switch on the pipeline.
Click Monitor to view signalling data.
The screen should be broken into 4 segments.
These are a monitor screen, to specify the monitoring process being
undertaken.
A short view of all messages.
A decoded long view of the selected message.
A binary view of the selected message.

Version 1 Rev 1 K1205
Monitoring
Diagran Number
Figure 1-30
Figure 1-31

Radcom/Prismlite Version 1 Rev 1
Radcom/Prismlite
Note:
That the RadCom is not connected ON a link (parallel), but IN a link( serial). This means
the link has to be broken to install it.
Only two interfaces at the same time can be displayed.

Version 1 Rev 1 Radcom/Prismlite
Radcom
MSC/VLR
BTS
SS7
BSC
HLR
Laptop
PSTN
GPRS CISCOSYSTEM
S
1 2 3 4
4
1234
1 2 3 4 12 1 2 3 4 1234 5 6 7 8
2
34 5678
FA
STETH
ERNETIN
PU
T/O
UTPUTCONTR
O
LLERSD
Backbone
FEM
Cisco 7200
II
SGSN GGSN
Series
ER
0
BLED
OKW
IOPOST
CIA
K
T
E
BE
BLE
N
AU
EJEC
0
SLOT
LL
PUIR
M
I
F
A
FEA
A
PDN
EN
EN
EN
PC
C
Firewal
GGSN
PCU SGSN
Figure 1-32

PrismLite Typical Hardware Configuration

Two CPUs.
Maximum 3 Slots for LAN, WAN or ATM.
Each WAN FEP support 2 E1 Line Interface Modules (LIM).
Each Fast LAN FEP support 1 LAN LIM.
ATM ComboFEP for ATM 155Mbps.
Slot 1 & 2 are controlled by CPU1; Slot 3 is controlled by CPU2.

A Portable Computer running Win/98/NT is needed, in order to monitor the signal
information, PrismLite software is installed on the PC.
One set of cables and adaptors, compromising:
One cable connecting between RADCOM and PC.

One set of cable for E1 connection.
One set of cable for Fast Ethernet connection.

PrismLite Typical Hardware Configuration
Figure 1-33

Setting up Interfaces
GB Interface
It is important that the BSSGP version should be selected to correctly fit your system.

GB Interface Setup
GMM/SM GMM/SM
LLC LLC
Relay
RLC RLC BSSGP BSSGP
MAC MAC Network Network

Service Service
GSM RF GSM RF L1bis L1bis

Um Gb
MS BSS 2GSGSN
Figure 1-34

Gn/Gi Interface
The protocol to be selected for monitoring the Gn interface should be IP.

Gn/Gi Interface
Application
IP IP
Relay
SNDCP SNDCP GTP U GTP U
LLC LLC
Relay
UDP UDP
RLC RLC BSSGP BSSGP

IP IP
MAC MAC Network Network L2 L2

Service Service
GSM RF GSM RF L1bis L1bis L1 L1
Um Gb Gn Gi
MS BSS SGSN GGSN
Figure 1-35

Gr Interface
For the Gr interface (SS7 SFHLR) we should select the GSM09.02 Protocol.

Gr Interface
Figure 1-36

Processes Control Frame Capture

Pressing the Setup button at the bottom of the Capture window to change configuration
will stop the currently running process without saving the collected data.
Leftclicking with the mouse on any part of a particular frame will produce a red arrow
pointing to it. This arrow marks the frame as a reference point, useful during viewing or
when calculating relative timing between frames (more on Relative Timing later).
Rightclicking with the mouse anywhere in the capture display window will open a menu
of various viewing/analysis options. The most commonly used options are described
below in more detail.

Processes Control Frame Capture
Figure 1-37

Processes Control Line Status

This provides a detailed analysis, in tabular form, of both the network and user physical
errors, alarms, and performance of the line being monitored.
This is useful when setting up the Radcom and GPRS components together to ensure a
proper network connection is made. By watching the line status, one can diagnose and
rectify any network problems before starting actual GPRS testing.

Processes Control Line Status
Figure 1-38

Processes Control Statistics

The Statistics process computes basic statistics online and displays the data both
online and offline according to Kbps, Fps, or percent line utilization.
This process operates on data captured from the line under test, according to customized
filters if desired, and stores the statistics on your hard disk in a temporary file.
Here, one can select the type of capture filter, where statistics are only computed on the
desired frames filtered from the data stream.After completing the setup of the statistics
parameters, click the Go button in the Statistics window to start the process.

Processes Control Statistics
Figure 1-39

GB Snoop Version 1 Rev 1
GB Snoop
GBSnoop is the only tool on the market to analyze a GPRS networks performance.
It obtains Data (Arguments) to Manage Customer Expectations.
It provides an endtoend Troubleshooting tool.
GB Snoop will:
Manage huge amounts of log data.
Filter out problem areas.
Assign Problems to a network component.
Gbsnoop is a standalone EXE that has no further requirements. It requires to be placed
into any directory and executed from there. As input, it requires a Radcom ASCII log, raw
data, fully expanded. Also, you should under Record/Options/Timing choose Absolute
and milliseconds (default).
Alternatively, for K1205, it needs a file including the HEX message dump.
The steps are always the same:
First you must apply the Converter/Decoder.
From the File menu to obtain the required files for analysis, then use
the analyzer functions also from File.

Version 1 Rev 1 GB Snoop
Converter Module
Figure 1-40

Gbsnoop Features
GB Snoop contains converters for inputs from Radcom (Motorola) and Tektronix Gb
analyzers.
A Gb Protocol Stack Parser.
Gb link usage viewer.
TCP analyzer (find TCP connections).
Expert system to spot on Gb per TCP:
Retransmissions, round trip delays, multiple transmissions, lost blocks.
Excel OLE driver (Use Excel 97 as directed viewer).
BVC Flow Control Analyzer / Viewer.
Calculate Bmax from PCU signalling.
Integrational viewer (integrates Bmax estimation over time).

GB Snoop Functionality
Radcom Logs Tektronix K1205 Logs
Gb Link usage
Converter Converter Viewer
Legend
Device Independent Gb Parser Input
Excell viewable file
(tab separated fields)
Gb Protocol Stack Parser
Gbsnoop Software
Decoded GB Protocol Modue
TCP analyzer BVC Flow Control Analyzer

(connection lister/finder) (estimate Bmax based on PCU signalling)
TCP Connection details/ Analyzed BVC FC data Best

problem zone spotter
Excel 97 OLE driver Bmax (est)

BVC FC Viewer
(use Excel as external viewer)
CPU_TB snoop Func
Figure 1-41

TCP connection finder

This window lists all the TCP or UDP connections recorded in the logfile. This is to assist
in locating the problem area by identifying which TCP connection is having problems, and
then after that, go to TCP connection analysis by clicking the button provided.
This window provides a sample on FTP data connection. Analysis can be focused on
FTP connection, where the port source is labelled as FTP DATA.
Select the TCP connection (by row number) for further analysis. Then click the button
next to it for packet analysis on that TCP connection.

TCP connection finder
Diagran Number
Figure 1-42

TCP Connection
Roundtrip time is the amount of time for a packet being sent and acknowledged.
POSSIBLE REMARKS ON THE SPECIAL COLUMN
1. SQ: Segment is out of sequence, that is, it could be a retransmit or
there was a loss on the SGSN input side (Internet)
2. MACK(n): Multiply ACKed blocked (n=number of such Acks) This
happens, when the MS is missing a block or is expecting more data
which it is snot getting > potential RF problems or blocks missing from
Internet.
3. RT: Retransmit. This block is again transmitted later in the connection.

TCP Connection
Diagran Number
Figure 1-43

TCP Connection Contd

Based on the remarks in Special coloumn, investigation focused on the retransmitted
(RT) packets.
Typical dropped packet scenario: multiple Ack(6) followed by retransmission(RT). Having
selected line 57, when pressing the Launch Excel detailed view button you will see the
following slide:

TCP Connection (contd)
Diagran Number
Figure 1-44

Excel directed viewing

After launching Excel this way, you can see in this example that LLC segment 1 of
SNDCP PDU 77 (771) is missing.

Excel Directed Veiwing
Diagran Number
Figure 1-45

BVC Flow Control Viewer output

Graphically represent the progress of BVC buckets level within a timeframe.

BVC Flow Control Viewer Output
Diagran Number
Figure 1-46

BSS Gather Version 1 Rev 1
BSS Gather
BSS_GATHER is a script written in TCL to overcome GPRS problems in the networks.
The function of bss_gather is to check the network of a number of known fault conditions,
rectify those fault conditions and report the conditions to a log. There are facilities in the
setup to send emails or SMS to an engineer or to a list of engineers, should a threshold
or a specific fault condition be found to exist.
The bss_gather is run on the OMC splat, either on the command line with arguments or
by a cron job.
Bss_gather can identify problems in a board and automatically reset that board, sending
information to log both before and after the reset but not every network will allow a script
to reset a board automatically.
The bss_gather examines the MIB database to extract all the BSCs below an OMC.
The bss_gather logs onto each BSC in turn and sends a disp_bss command.From the
returned output from the BSC it can identify all the sites below that BSC, both GSM or
GPRS.
The bss_gather is only interested in BU sites; so all others are currently ignored.
The bss_gather sends a disp_cell status <site no> command for each site identified from
disp_bss that are BU.
The bss_gather sends a disp_gprs_enabled < site no> command for each site identified
by the disp_bss that are BU.
if the network procedures allow BSS_Gather will toggle GPRS (the gprs_enable is
disabled and enabled again). This causes the Boards to rebalance, and reinitialise.
If a toggle cannot correct the problem then the next step would be to reset the DPROC,
again if the network procedures allow. Any successful or unsuccessful toggles are
logged by default.
From the Disp_cell_s <site no> there is information about timeslots.

Version 1 Rev 1 BSS Gather
BSS Gather
disp_bss
disp_cell_status <site no>
disp_element_gprs_enabled, <site no>
OMC
BSS1 BSS4
BSS2 BSS3
Figure 1-47

Checking the processing buffers

In order to ascertain exactly what the problem with a site may be, it is necessary to
interogate the PCU. One such example of this is to interrogate the Buffers within the
site. The buffers can be checked by bss_gather by use of the pb_list command on each
DPROC.
The bss_gather sends a command disp_pcu and remote logs into the DPROC that are
present, change leveltolevel 3 and send the command pb_list and examine the
returned information.
A log would be returned with a similar output to the diagram opposite, and corrective
action would occur as described on the previous page.

PB Buffers
write ID Attach Name Device Packet Size Used Peak
...
4000000b yes HOST2NIB 1 00001a00 12 23040 30720 30732
read ID Attach Name Device Packet Size Used Peak
...
8000000c no pmc2tsn 0 00010900 12 12000 0 N/A
PB Buffers
Figure 1-48

Excel Spreadsheet
By placing the output into an Excel spreadsheet it is possible to view the information
gathered by BSS Gather, and to view the results of any action carried out. In the graph
opposite, it can quite clearly be seen that over a number of months, the number of GPRS
Timeslots that were out of use, for this particular network varied greatly over time. Each
of the 5 lower value lines represent the number of PDTCH OOS for a particular OMC
area of responsiblity. The largest value line indicates an overall Network value.
It was found after examination that the dates where there were missing timeslots were
the same dates the SGSNs were having upgrades, or where there were GB link
issues.The dates where there were no missing timeslots was the day after bss_gather
was run and the toggle GPRS was allowed for missing timeslots.

Graphical Representation
Lost Timeslots
450
400
350
300
Count
250
200
150
100
50
0
18/12/01
20/12/01
22/12/01
24/12/01
26/12/01
28/12/01
30/12/01
01/01/02
03/01/02
05/01/02
07/01/02
09/01/02
13/01/02
15/01/02
17/01/02
19/01/02
21/01/02
23/01/02
25/01/02
27/01/02
29/01/02
31/01/02
02/02/02
04/02/02
06/02/02
08/02/02
10/02/02
12/02/02
11/01/02
Date
OMC1 OMC2 OMC3 OMC4 OMC5 TOTAL
Diagran Number
Figure 1-49


Chapter 2
Data Collection

Version 1 Rev 1

Version 1 Rev 1
Chapter 2
Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Functionality and Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Functional Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Starting Downlink Data Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Continuing Downlink Data Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Uplink Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Debugging basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Filter Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Help Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
PRP/PICP Help Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
pSM Help Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
pCM Help Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
pCA Help Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Debugging Basics CB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Debugging Basics GBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Debugging Basics PRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Debugging Basics TSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Debugging Basics CRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Comments and Timestamping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Corresponding Gb, PICP, PRP, and MS logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
MMI Timeout at PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Disp_cell_status <Site_number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
GPRS Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
PDCH Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
GPRS AccClass Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
PD Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Version 1 Rev 1

Version 1 Rev 1 Objectives
Objectives
By the end of this chapter, the student will be able to:
Describe the major Software Functional Units of the PCU that you may
be expected to use for debugging purposes.
Describe the help messages for the DPROCs and the pSM, pCM and
pCA.
Carry out onsite procedures whilst observing the best CNRC practices.

Functionality and Data Collection Version 1 Rev 1
Functionality and Data Collection
Functional Units
The main software processes that we will talk about in this chapter will be:
PRP Packet Resource Processor.
Packet flow to and from the BSC/BTS .
Air interface protocol.
Scheduling of radio timeslots.
Segmentation and reassembly.
GB Gb link.
All signalling to the SGSN.
Management of Gb interface resources (links, NSVCs, BVCs).
Packet flow to and from the SGSN.
GWM Gateway Manager.

Fault and Device Management of the PCU.
Alarm collection and relaying.
Management of the local CM database.
Managing data paths between boards and data resources on GDS
timeslots.
Dynamic cell balancing of cells across available PRPs.
Collection and reporting of Statistics.
Audits.
EXEC Executive
This is a collection of support services intended to supplement the
services provided by the Real Time Operating System.
Exec DLSP acts as Layer 2 for LAPD links.

Manages PCI links between boards.

Version 1 Rev 1 Functionality and Data Collection
Functionality
PSP (PPC 750 board) PRP (PPC 750 board) PICPGb (PPC750)
CPGM Pages for CCH

DL Gb signalling GR DL test PDU
GBM NST
Pages for CCCH Cell Cell Status Changes
Status
Cell status changes
changes/ SYM Pages for PCCCH/PACCH DL Gb frames
Gb link
status Paging UL status UL test PDU
buffers DL BSSGP
GWM DB frames message
GSL notifications (per cell, Flow control
Stats message per page buffers (per
GSLI group) cell QoS) Flow control
Sysinfo To GBW:
and flush
buffers Notification
LAPD signal
(per cell) messages
PICPTRAU frame
(1/2 of a PP C860) Immediate PPGM FR DLSP
EXEC assign FBM Flow Control PDUs
GSL DLSP UL Gb
(1 or more 64K RLC FR API messages
Downlink TRAU frames
LAPD links) blocks
frames
CCTX PRM DLS
PCUCCU
PPC 860
GTM FR and
(16K circuits
on E1) Timing data, RLC UL Gb STREAMS
CCRX sync status blocks frames
ULC Go input E1
TSN UL TRAU frames UL Gb frames buffer HDLC E1
Gb link status changes (per PRP) Driver
(1/4 of a PPC750)
Data Collection 1
Figure 2-1

PRP Functional Unit Processes

SYM System Information Manager.
Builds and sends system information messages over the BCCH (Sys info
13).
Handles SYM updates.
CPGM CCCH Paging Manager.

Handles pages from SGSN and forwards to RSS or MTPL3.
PPGM PCCCH Paging Manager.

Handles pages from SGSN and forwards to PRM.
DLS Down Link Segmenter.

Handles LLC frames from buffers and disassembles into RLC blocks.
ULC Uplink Concatenator.
Handles RLC blocks and assembles into LLC frames.
LLC frames are load shared across NSVCs.
PRM Packet Resource Manager.

Schedules the GPRS timeslots.
RLC/MAC state machine i.e. access grants and timing advance.
TSN TRAU Synchronisation (Appears on PRP from GSR6).

Validate/Synchronise TRAU frames.
Converts TRAU to pseudoTRAU.
Manages TRAU timeslot to PRM input buffers.
GB Functional Unit Processes

FBM Flow Control Buffer Manager.
Flow controls downlink data over the Gb to match air throughput.
Schedule data for optimal downlink transfer.
GR Gb Router.
Validates downlink Gb packets.
Routes Gb packets to the appropriate processes.
GBM Gb Manager.
Performs the cell (BSSGP layer) management procedures.
Performs the NSVC (NS layer) management procedures.
GTM Gb Transmit Manager.

Collects LLC frames from ULC and sends them to the SGSN via GB
DLSP.
NST Network Service Tester.

Monitors each NSVC over the Gb interface.
FR Frame Relay.
STREAMS Streams manager software provided in the FR stack.
FR DLSP Frame Relay Data Link Service Provider.

Functionality
CPGM Pages for CCH

GBM NST
Pages for CCCH Cell Cell Status Changes
Status
Cell status changes
Gb link
buffers DL BSSGP
Sysinfo To GBW:
and flush
LAPD signal
(per cell) messages
PICPTRAU frame
GSL DLSP UL Gb
(1 or more 64K Downlink TRAU RLC FR API messages
frames
LAPD links) blocks
frames
CCTX PRM DLS
PCUCCU
PPC 860
GTM FR and
(16K circuits
ULC Go input E1
(1/4 of a PPC750)
Data Collection 1
Figure 2-2

GWM Functional Unit Processes

pFTP PCU Fault Translation Process.
Manages alarms.
pFCP PCU fault collection process.

Manages faults.
pCA PCU Central Authority.

Manages PCU devices.
pSM PCU Switch Manager.

Connects/disconnects data paths between PCU and BSC.
pSAP PCU system Audit Process.

Manages PCU audits.
pCM PCU Configuration Management.

Manages CM database at the PCU.
CB Cell Balancer.
Dynamically allocates resources to cells based on available GDS span
lines and PRP boards, equipped CM database GPRS air resources, and
PRP load.
Resides on MPROC.
Allocates Cells to PRPs on initialization.
Reallocates cells to PRPs if PRP goes OOS.
Updates pCA, GBM, PRM and GR of cell to PRP mapping
Gets PRM stats information from TRS to determine the number of
timeslots allocated to each cell.
Reallocate Cells in event of PRP congestion.
Timeslots in one cell may not be split across PRPs.
CB Timeslot allocation
Reserved GPRS radio timeslots in a cell are allocated first.
Switchable GPRS radio timeslots in a cell are allocated after all
reserved.
Switchable GPRS radio timeslots in a cell are released first.
Reserved GPRS radio timeslots in a cell are released after all
switchable.

Functionality
CPGM Pages for CCH

NST
Pages for CCCH GBM Cell Cell Status Changes
Status
Cell status changes
Gb link
buffers DL BSSGP
Sysinfo To GBW:
and flush
LAPD signal
(per cell) messages
PICPTRAU frame
GSL DLSP UL Gb
(1 or more 64K Downlink TRAU RLC FR API messages
frames
LAPD links) frames blocks
CCTX PRM DLS
PCUCCU
PPC 860
GTM FR and
(16K circuits
ULC Go input E1
(1/4 of a PPC750)
Data Collection 1
Figure 2-3

Starting Downlink Data Flow.

This slide shows the start of a downlink transfer. The DLS writes data to the available TX
buffer space and then issues a downlink data request. This request is queued until it is
scheduled. Once it is scheduled, the downlink assignment is sent. RLC data blocks are
sent following the assignment.

Starting Downlink Data Flow
PRM
CCRx CCTx TAPC UL DL RLC Sched Tx Buff DLS FCBM
Signal
LLC
frame
arrival
DLS gets
LLC frame
Fill TX Buffer
until full or no
more data
RLC Data Block

RLC Data Block
RLC Data Block
RLC Data Block

DL Data Req
(TLLI, TFI, # blks)
DL Assign
DL Assign
RLC Data Block
RLC Data Block w polling
RLC Packet Downlink Ack/Nack
Data Collection 2
Figure 2-4

Continuing Downlink Data Flow.

The slide opposite shows the continuation and end of a downlink assignment. When the
RLC receives an acknowledge for transmitted RLC blocks, it will mark those blocks as
free in the TX Buffer. When the free space reaches a certain threshold, usually half of
the buffer, it will signal the DLS that it can write more data into the TX buffer. The DLS
will segment more RLC data blocks and place them in the buffer. This process continues
until all the data for the TBF is sent.

Continuing Downlink Data Flow
CCRx CCTx TAPC UL DL RLC Sched Tx Buff DLS FCBM
Acks for RLC Blks

RLC Data Block
RLC Data Block Mark tx buffer blk
space as available
RLC Data Block w polling
Acks for RLC Blks
Signal TX Buffer space free
RLC Data Block

Get more data
RLC Data Block
check if another
RLC Data Block w polling LLC frame is in
RLC Packet Downlink Ack/Nack buffer
Acks for RLC Blks
RLC Data Block
RLC Data Block RLC Data Block
RLC Data Block RLC Data Block
RLC Data Block (last)
Acks for RLC Blks
Signal TX Buffer space free
Get more data
Data Collection 3
Figure 2-5

Uplink Transfer
This slide is not quite true, in the present implementation the CH Request will be
received from GSLI and the IA will be sent back on GSLI.
The slide opposite shows the start of an uplink transfer. The channel request is
forwarded by the UL to the scheduler. The scheduler schedules a downlink transfer and
send a packet immediate assignment to the DL. It also sends a Ul Assignment
Notification to the ULC. This notification allows the ULD to allocate any buffer space that
it needs for the upcoming data. After the DL sends it to the channel coders via the CCTX,
the PRM waits for uplink data to start. When the UL receives the uplink RLC data
blocks, it forwards them to the uplink concatenator which assembles them into LLC
frames.

Uplink Transfer
Figure 2-6

Debugging basics Version 1 Rev 1
Debugging basics
Message Format
The message send commands will provide the operator with a vast amount of
information. For more detailed information on the uses of message send commands,
see the BSS07 manual. For the commands contained within this course the commands
break down as follows:
msg_send [subnet <subnet_id>] [routing_type] ...args...
The routing types and respective args are defined as follows:
ROUTING_TYPE : ...ARGS...
============ : ==========
physical : d_pid d_mbid s_pid s_mbid tag data
It should be noted that even though other variations of message format are available, for
the purposes of this course, only the Physical format is discussed.
An example of the physical format is the TLLI watch enable command which is shown
below:
msg_s 0d9h 9000h 0 0 7404 4 34 1 <tlli_byte3> <tlli_byte2> <tlli_byte1> <tlli_byte0>

Version 1 Rev 1 Debugging basics
Process Identifiers
Process PID (hex) PID ( dec ) Process PID PID

pSM 0x40 64 (hex) (dec )
pCA 0x42 66 NST 0xd4 212
pFTP 0x4b 75 FBM 0xd5 213
pSSAP 0x4d 77 GbDLSP 0Xd6 214
IP 0x50 80 GR 0Xd7 215
pSSP 0x61 97 PRM 0xd9 217
pCM 0x71 113 SYM 0xda 218
CB 0xd0 208 TSN 0xdb 219
CPGM 0xd1 209 ULC 0xdc 220
GBM 0xd2 210 DLS 0xdd 221
GTM 0xd3 211
Figure 2-7

Filter Tags
Please note that the usual warnings on Filters Apply.
Filter Tags are 4 bytes long. So given the example:

tag 8002731ch
Then:
8002 Configuration type messages

73 PRP <> CP
1c Cell balancing data
Note: The Filter type byte is often not used.

Filter Tags
Byte 1 and 2 Byte 3 Byte 4

Filter type Interface Message type
agran Number
Figure 2-8
Interface Types
pFTP <> pCA

<>pCA 3a
FM <>
< > GB 70
FM<<>
FM PRP
> PRP 71
PRP<<>
PRP RSS
> RSS 72
PRP<<>
PRP > CP
CP 73
PRP <<>
PRP > GB
GB 75
8.16Interface
8.16 Interface 76
8.18Interface
8.18 Interface 77
PCU<<>CM
PCU > CM 79
PCU<<>MMI
PCU > MMI 7a
N.B. 74 is the PRM Internal Interface
Figure 2-9

Help Messages
A number of the processes in the PCU have help messages. This will print out all the
info possible with msg_send commands.
MPROC:
pSM: msg 40h 9000h 0 0 0 0ffh
pCM: msg 113 5 66 0 0abh 2 7 7 3 [object] [local cell id] Note: If object is
not specified, options will be listed.
pCA: msg 42h 9000h 0 0 0 0ffh
pFCP: msg 4ah 9000h 0 0 0 0ffh (DPROC also)
pFTP: msg 4bh 9000h 0 0 0 0ffh
pSSAP: msg 04dh 9000h 0 0 0 0ffh
pSSP: msg 61h 9000h 0 0 0 0ffh
GBM: msg 0d2h 9000h 0 0 0 0ffh
CB: msg_s 208 9000h 0 0 0 0

Debugging Help Messages
[06/11/01 09:23:52] PCU:emon_117 % msg_s 208 9000h 0 0 0 0

CB DEBUGGING OPTIONS:
Usage: msg_s 208 09000h 0 0 0 <value>
<1> Display timers
<2> Update timers
<3> Print table summary
<4> Print master table
<5> Print main table
<6> Print temp table
<7> Print PRP table
<8> Print router registration table
<9> Print CELL to PRP mappings
<10> Print SITE state table
<11> Change/Display balancer parameters
Data Collection 6
Figure 2-10

PRP/PICP Help Messages
PRP:
pLSAP: msg_send 4dh 9000h 0 0 0 0
pLSP: msg_send 62h 9000h 0 0 0 0ffh
PRM: msg_s 0d9h 9000h 0 0 7404h 04 0
SYM: msg_s 0dah 9000h 0 0 00007402h 02h 83h <local cell ID>
FBM: msg_s 0d5h 9000h 0 0 0f0h 0
PICP:
TSN: msg_s 0dbh 9000h 0 0 33h 0ffh

PRP/PICP Help Messages
PCU:emon_1101 % msg_send 62h 9000h 0 0 0 0ffh

*** pLSP major debug messages ***
to print GR state:msg_send 62h 9000h 0 0 0 1bh
to change GR state:msg_send 62h 9000h 0 0 0 1ch <UBYTE new_gr_state>
to print buffer responses:msg_send 62h 9000h 0 0 0 1dh
to set buffer responses:msg_send 62h 9000h 0 0 0 1eh <UBYTE process_id><UBYTE
response_type>
to print timer timeouts:msg_send 62h 9000h 0 0 0 6h
to change timer timeout:msg_send 62h 9000h 0 0 0 1 <UBYTE timer_msg_type><ULONG
timeout>
***End of pLSP HELP***
*** End of Debug information***
Data Collection 7
Figure 2-11

pSM Help Messages

The following help messages are available from the pSM process.
#### THE FOLLOWING DEBUG MESSAGES ARE USED BY pSM ####

1. To display the contents of the pSM GCI TABLE for a particular GDS:
msg_send 40h 09000h 0 0 0h 2 <(ubyte)gds id>
2. To display information for a cell id:
msg_send 40h 09000h 0 0 0h 3 <(ulong) cell id>
3. To display summary info for all cells:
msg_send 40h 09000h 0 0 0h 5
4. To display GCI(s) for a RCI:
msg_send 40h 09000h 0 0 0h 4 <(ulong)cell_id>
<(ubyte)carrier_id><(ubyte)channel_type> <(ubyte)timeslot>
5. To display the current values of pSM timers:
msg_send 40h 09000h 0 0 0h 7
6. To display all the RCIs mapped to a particular PRP board:
msg_send 40h 09000h 0 0 0h 8 <(uword) PRP CPU ID>
7. To change timeout value for a PSM timer:
msg_send 40h 09000h 0 0 0h 1 <(ubyte)timer_msg_type>
<*ubyte)timeout(sec)>
8. To display stats report :
msg_send 40h 09000h 0 0 0h 9
<(ubyte) start_location>(ubyte)end_location>
9. To reset the start time for stat collection :
msg_send 40h 09000h 0 0 0h 10

pSM Help Messages
1. To display the contents of the pSM GCI TABLE for a particular

GDS.
2. To display information for a cell id.
3. To display summary info for all cells.
4. To display GCI(s) for a RC.
5. To display the current values of pSM timers.
6. To display all the RCIs mapped to a particular PRP board.
7. To change timeout value for a PSM timer.
8. To display stats report .
9. To reset the start time for stat collection.
Figure 2-12

pCM Help Messages

The following help messages are available from the pCM:
Type the command :

pCM: msg 113 5 66 0 0abh 2 7 7 3 [object] [local cell id] Note: If object is not specified, options will be listed.
CM: 0 BSS elements

CM: 1 Site elements
CM: 2 PCU elements
CM: 3 Cell list
CM: 4 Cell elements (cell ID required)
CM: 5 Gb mapping (cell ID required)
CM: 10 CAB descriptors
CM: 11 CAGE descriptors
CM: 12 MSI descriptors
CM: 13 MMS descriptors
CM: 14 PSP descriptors
CM: 15 DPROC descriptors
CM: 16 GDS descriptors
CM: 17 GSL descriptors
CM: 18 GBL descriptors

pCM Help Messages
CM: 0 BSS elements

CM: 1 Site elements
CM: 2 PCU elements
CM: 3 Cell list
CM: 4 Cell elements (cell ID required)
CM: 5 Gb mapping (cell ID required)
CM: 10 CAB descriptors
CM: 11 CAGE descriptors
CM: 12 MSI descriptors
CM: 13 MMS descriptors
CM: 14 PSP descriptors
CM: 15 DPROC descriptors
CM: 16 GDS descriptors
CM: 17 GSL descriptors
CM: 18 GBL descriptors
Figure 2-13

pCA Help Messages

The following pCA messages can be used. They can be seen by entering the command:
PCU:emon_1107 % msg 42h 9000h 0 0 0 0ffh
The help menu should appear and look like the list opposite:

pCA Help Messages

INTERNAL REQUEST: msg_send 66 9000h 0 0 0 0dah 0
ROUTER REQUEST: msg_send 66 9000h 0 0 0 0dah 1
NORMAL REQUEST: msg_send 66 9000h 0 0 0 0dah 2
CMIS REQUEST: msg_send 66 9000h 0 0 0 0dah 3
ENTITY NOTIFICATION: msg_send 66 9000h 0 0 0 0deh
GDS TO PRP MAPPINGS: msg_send 66 9000h 0 0 0 0aah
Single DIB: msg_send 66 9000h 0 0 0 0ddh 1 <dev_name> <id0> <id1> <id2>
All DIBs: msg_send 66 9000h 0 0 0 0ddh 2 <dev_name>
Single History: msg_send 66 9000h 0 0 0 1 1 <dev_name> <id0> <id1> <id2>
All Histories: msg_send 66 9000h 0 0 0 1 2 <dev_name>
Clear Single History: msg_send 66 9000h 0 0 0 2 1 <dev_name> <id0> <id1> <id2>
Clear all Histories: msg_send 66 9000h 0 0 0 2 2 <dev_name>
Active Tag List (whole): msg_send 66 9000h 0 0 0 0ach 3
Active Tag List (group): msg_send 66 9000h 0 0 0 0ach 2 <start(2bytes)> <stop(2
bytes)>
Active Tag List (single): msg_send 66 9000h 0 0 0 0ach 1 <index (2 bytes)>
Affected FU List (whole): msg_send 66 9000h 0 0 0 0afh 3
Affected FU List (group): msg_send 66 9000h 0 0 0 0afh 2 <start(2bytes)> <stop(2
bytes)>
Affected FU List (single): msg_send 66 9000h 0 0 0 0afh 1 <index (2 bytes)>
Capacity Tables: msg_send 66 9000h 0 0 0 0cah
Change Timer Value: msg_send 66 9000h 0 0 0 3 <timer define> 0 <time (4 bytes)>
Change NRQ Upper thresh: msg_send 66 9000h 0 0 0 0dch 0ffh <thresh (2 bytes)>
Change NRQ Lower thresh: msg_send 66 9000h 0 0 0 0dch 0 <thresh (2 bytes)>
Figure 2-14

Debugging Basics CB Version 1 Rev 1
Debugging Basics CB
In order to interrogate the Cell Balancer use the:
CB: msg_sen 208 9000h 0 0 0 5
This will give detail the local cell ID, local RTF (carrier) ID, number of timeslots allocated,
and the PRP that controls the cell.
Prior to using this command, it would be advisable to use the
disp_gsm_cell <cell ID> command to ascertain the LCI of the cell in question.

Version 1 Rev 1 Debugging Basics CB
Debugging Basics CB
[06/11/01 09:23:33] PCU:emon_1107 % msg 208 900h 0 0 0 5

CB Main Table:
deact deact deact deact

lci rtf alloc CPU reasn timer id lci rtf alloc CPU reasn timer id

0x19 0x5 7 1106 0xff 0 0x15 0x1 7 1106 0xff 0
0 0 7 1103 0xff 0 0x15 0x2 7 1103 0xff 0
0x1 0x1 7 1104 0xff 0 0x17 0x3 7 1104 0xff 0
0x8 0 7 1105 0xff 0 0x18 0x4 7 1105 0xff 0
0x9 0x1 7 1106 0xff 0 0x1a 0 7 1103 0xff 0
0xa 0x2 7 1103 0xff 0 0x1b 0x1 7 1104 0xff 0
0xb 0x3 7 1104 0xff 0 0x1c 0x2 7 1105 0xff 0
0xc 0x4 7 1105 0xff 0 0x1d 0x3 7 1106 0xff 0
0xd 0x5 7 1106 0xff 0 0x1e 0x4 7 1103 0xff 0
0xe 0 7 1103 0xff 0 0x1f 0x5 7 1104 0xff 0
0xf 0x1 7 1105 0xff 0 0x20 0 7 1105 0xff 0
0x10 0x2 7 1105 0xff 0 0x21 0x1 7 1106 0xff 0
0x11 0x3 7 1106 0xff 0 0x22 0x2 7 1103 0xff 0
0x12 0x4 7 1103 0xff 0 0x23 0x3 7 1104 0xff 0
0x13 0x5 7 1104 0xff 0 0x24 0x4 7 1105 0xff 0
0x14 0 7 1105 0xff 0 0x25 0x5 7 1106 0xff 0
End of CB MAIN TABLE.
Data Collection 8
Figure 2-15

Debugging Basics GBM Version 1 Rev 1
Debugging Basics GBM

GBM Cell: You can see the state of the cell from GBM opposite. The most important
parts are the Cell state and Cell service state
GBM NSVC: You can see the state of the NSVC. Even though our NSVCI is 125 in the
database, the local NSVCI Ids start from 0. So our first NSVC equipped will have a local
NSVCI of 0. Notice the state of alive.

Version 1 Rev 1 Debugging Basics GBM
Debugging Basics = GBM
[06/11/01 10:02:41] PCU:emon_1107 % msg_send 0d2h 9000h 0 0 0 00h 0 0 0 0

Cell id 0, Cell state GPRS UNBLOCKED (S5), BVCI 1000 (0x3e8),
BVCI flags: Gb_avail 1, Gb_sig_ 1, BSC cell 1, site 1, CB 1, GPRS 1
BLK_cause: ff, RST_Cause 8, Retries 0, Timer 0
INS_OP 0, CB_code ff
Cell service state: GPRS INSUNBAR (S2)
[06/11/01 10:03:09] PCU:emon_1107 %
[06/11/01 10:04:33] PCU:emon_1107 % msg_send 0d2h 9000h 0 0 0 01h 0 0
[06/11/01 10:04:33] PCU:emon_1107 % msg_send 0d2h 9000h 0 0 0 01h 0 0

Local NSVCI 0, GSM NSVCI 125 (0x7d),
NSVC state NSVC UNBLOCKED (S4)
NSVCI flags: FECN 0, BECN 0, Test_pending 0,
Nsvc_alive 1, 0&M Block 0
Gbl_id 0, DLCI 33
Cause: 1, Retries 0,
Timer 0, Reset_period_tid 0
GBL 0 State: INS
Data Collection 9
Figure 2-16

Debugging Basics PRM Version 1 Rev 1
Debugging Basics PRM

The most common PRM msgs are opposite. The most frequently used are the ones that
are 12,14 and 34.
Access the following through the help msg:
msg_s 0d9h 9000h 0 0 7404h 04 0
Typically when looking at a data problem, we will want to see PRM TBF allocation
iir_m 0d9h 0c0000000h along with PRM TLLI watch described in the help for PRM. In
addition to this, we will want to see 12 And 14 above to get a snapshot of the cell and
carrier. Based on the output of this, we may need other data above.

Version 1 Rev 1 Debugging Basics PRM
Debugging Basics PRM
12. To print the carrier information: (Prints all info from PRM about the carrier)
14. To print the cell info: (Prints all info from PRM about the cell)
31. To start carrier loggingr on a carrier: (logs 3000 blocks ~1 minute)
32. To stop carrier logging on a carrier: (stops carrier log from 31)
34. To enable tlli watch.
38. To print the block log: (Prints out carrier log from 31)
41. To print out the timing advance statistics
62. To print the terse block log.
59. To print the current dl bler stats:
60. To clear dl bler stats:
79. Print TS History: (History of timeslot transitions)
83. Set or display PRM IIR (Supercoattail) msg_s 0d9h 9000h 0 0 7404h 4 255 1 0 0 0 40h
Note: to stop, msg_s 0d9h 9000h 0 0 7404h 4 255 1 0 0 0 0
Data Collection 10
Figure 2-17

Debugging Basics TSN Version 1 Rev 1
Debugging Basics TSN

The TSN debug opposite is typically used for GPRS OOS cases. See the GPRS OOS
data collection for more specific information
For the GDS TRAU, you could physically connect to a PRP or PICP. If you look at the
output from disp_pr pcu, you will sometimes see (GDS X) on a PICP board and will see
it again on a PRP. This means that the GDS TRAU is physically connected to the PRP,
but the TSN controlling this span is on the PICP.
A pb list on a PICP & PRP is used in conjunction with the first three debug messages
opposite when investigating PDs oos or an entire span OOS. (It will show you buffer
information for your span; (Attached, or not attached).

Version 1 Rev 1 Debugging Basics TSN
Debugging Basics TSN

TSN Debugging messages: msg_s 0dbh 9000h 0 0 33h 0ffh
Dump all PMC Buff Desc: msg_send 0dbh 09000h 0 0 0 2 (will show you mapping
to PRP if your GDS TRAU is on a PRP)
Print In/Out of Sync Channels msg_send 0dbh 09000h 0 0 0 44/45
Print TS array entry: msg_send 0dbh 09000h 0 0 0 4<Chan MSB><Chan LSB> (should
be done multiple times. You can get your channel number
from msg_send 0dbh 09000h 0 0 0 2 above.
Print UL TRAU Stats: msg_send 0dbh 09000h 0 0 0 33

Print DL TRAU Stats: msg_send 0dbh 09000h 0 0 0 34
Print UL PTRAU Stats: msg_send 0dbh 09000h 0 0 0 35
Print DL PTRAU Stats: msg_send 0dbh 09000h 0 0 0 36
Toggle Rlogin Output OMC/MMImsg_send 0dbh 9000h 0 0 0 1 0
Data Collection 11
Figure 2-18

Debugging Basics CRM Version 1 Rev 1
Debugging Basics CRM

CRM debug would typically be used if you have GPRS OOS or attach related problems.
msg_send 34 9000h 0 0 0 0b3h 0f0h <local cell id> (Carrier Config Manager
Detailed Display Request).
msg_send 34 9000h 0 0 0 0b9h 0f0h <local cell id> (Channel Resource View
Linked List Info Request).
msg_send 34 9000h 0 0 0 0bbh 0f0h <local cell id> (Carrier Config Manager
Display Request (for cell)).

Version 1 Rev 1 Debugging Basics CRM
Debugging Basics CRM

MCU: emon_1015 % msg 34 9000h 0 0 0 0b9h 0f0h 0
CRM CH RES VIEW (CELL ID= 00) LINKED LIST DATA:

List Type= 01, Number of channels in the list= 007
CR ID= 01, TS ID= 0, CH ID= 3
List Type= c4, Number of channels in the list= 003
Data Collection 12
Figure 2-19

Best Practices Version 1 Rev 1
Best Practices
Comments and Timestamping

Comments:
Always try to put comments in the PCU logs. Start the comment with ###. Ideally, try to
get a comment at the beginning and end of the log
Example:
### Starting 100k DL FTP
### Ending 100k DL FTP
This way, its easy for the support engineers to grep for ### to get all the comments put
in the logs.
Time Reference:
Use time_stamp on at the PCU and press return a few times at the start and end of the
log. This will give us an absolute time and makes it easy to relate this to SWFMs,
alarms, and events.

Version 1 Rev 1 Best Practices
Comments and Timestamping
PCU:emon_1107 % time_stamp on
[28/05/02 09:01:08] PCU: emon_1107%
[28/05/02 09:01:10] PCU: emon_1107%
[28/05/02 09:01:11] PCU: emon_1107%
[28/05/02 09:01:11] PCU: emon_1107%
[28/05/02 09:01:11] PCU: emon_1107%
[28/05/02 09:01:11] PCU: emon_1107%
[28/05/02 09:01:11] PCU: emon_1107%
[28/05/02 09:01:12] PCU: emon_1107%
[28/05/02 09:01:12] PCU: emon_1107%
PCU:emon_1107 % time_stamp console on
May Tue 28 09:02:14 2002
PCU:emon_11107 % time_stamp off
Data Collection 13
Figure 2-20

Baud Rate Version 1 Rev 1
Baud Rate
If you are collecting a large amount of PCU data, a TTY rlogin from the OMC or even a
connection from the BSC to PCU will not be sufficient.
This will require a direct connect to the PCU, and the baud rate should be increased to
38400.
To change baud rate at PCU:
From the Emon prompt type: baud 38400
Remember to change the baud of your communications program (Procomm,
Hyperterminal, etc) to 38400.
The cable used is the same as is used for terminal connection to an MCU or MCUF. It is
a null modem cable, and the cable shoule be connected as shown below.


Version 1 Rev 1 Baud Rate
Baud Rate
Baud Rate 38400

PCU
Emon Session
Data Collection 14
Figure 2-21

Corresponding Gb, PICP, PRP, and MS logs Version 1 Rev 1
Corresponding Gb, PICP, PRP, and MS logs
Often for performance related problems, it is required to get PICP, PRP, and MS logs all
at the same time. Sometimes, we also need the Gb log as well (but this is not typical).If
you are doing FTPs, try to keep the logs 1 to 1. So if you do one FTP, you have a single
log for PICP, PRP, and MS. Dont put multiple transfers in the logs if possible. If you do,
make sure all logs span the same time.
Put comments at the start and end of the logs with ###.
CNRC will need a time reference to sync up the logs. Set time_stamp on and press
return a number of times at the start and end of the log to provide an absolute time
reference on each processor you are logging.
GB log to PCU logs. Try to sync up the protocol analyzer time with the BSS time.
Identify any timing offset.
PCU to MS logs. See: http://www.cig.mot.com/Organization/GSM/CS/cs_web/ >
General Information > PCU > Data Collection > for information on how to match MS
logs with the PCU logs
The DPROCs are each running on a relative time from the time they last reset. If the
contents of state pcu are provided, this will allow the debugging engineer to see the
absolute time difference between the DPROCs.

Version 1 Rev 1 Corresponding Gb, PICP, PRP, and MS logs
Corresponding Gb, PICP, PRP, and MS logs
PCU
PICP
PRP
Gb Link
SGSN
Toolbag_PCU_Tools_1
Figure 2-22

MMI Timeout at PCU Version 1 Rev 1
MMI Timeout at PCU

When running a session with a DPROC or MPROC, it is important to note that there is a
default timer of 30 minutes, after which the security level at which the operator had been
working will return to level 1.
This can cause any information to be lost during the taking of a log. In order to maintain
the integrity of a logfile, it is possible to disable the security timeout.
To do this, the operator must be logged onto the BSC directly, or via the OMCR, it is not
possible to do this logged onto the BSC via the PCU. The timer must be disabled at the
BSC and PCU.
msg 112 6 0 0 1c00h 1 (BSC GPROC)

msg 23 1 0 0 08a04h 1 (PCU DPROC, MPROC
Note, there will be no reply to these messages.
To reverse this process and to enable the timer again, use a 0 in the last position.

Version 1 Rev 1 MMI Timeout at PCU
MMI timeout at PCU
PCU:emon_1107 % msg 23 1 0 0 08 904h 1 PCU Timeout Disable
PCU:emon_1107 % msg 23 1 0 0 08 904h 0 PCU Timeout Enable
GPROC2_RAM:emon_0115 % msg_send 112 6 0 0 1c00h 1 BSC timeout Off
GPROC2_RAM:emon_0115 % msg_send 112 6 0 0 1c00h 0 BSC timeout On
Data Collection 16
Figure 2-23

Disp_cell_status <Site_number> Version 1 Rev 1
Disp_cell_status <Site_number>
This command will display some very useful information in respect of the cell specified. In
disp_cell_status, there will be four GPRSrelated fields as follows:
GPRS Status
PDCH Status
Access Class
Number of PDCHs in In Use, Free, Unavailable

Version 1 Rev 1 Disp_cell_status <Site_number>
Disp_cell_status <Site_number>
[08/06/00 20:11:32] MMI_RAM 0115 > disp_cell_st 40

Start of report for LOCATION 40:
GSM CELL ID
MCC 262
MNC 01
LAC 510 (01FEh)
CI 23300 (5B04h)
RAC 4 (0004h)

Frequency Type PGSM
BCCH Frequency 77

Status Unbarred
GPRS Status Unbarred
PDCH Status Available
Reset in Prog No
GPRS Reset in Prog No
SPI in Prog No
BSS BSSAP Prhb NA
MSC BSSAP Prhb NA
SPI/MSC SCCP Prhb NA
AccClass Bar None
GPRS AccClass Bar 4
Full Power Mode OFF
Ext Range Mode OFF
FREE IN USE UNAVL

SDCCH 8 0 0
Norm Inner TCH/F 5 1 0
Norm Outer TCH/F 0
0 0
Ext Outer TCH/F 0 0 0
PD CHANNEL 3 0 0
End of Report
Figure 2-24

GPRS Status
OOS GBM Site is OOS or GSM Cell is OOS. See Status field for
more details.
GPRS DU GBM The element gprs_enabled is set to Zero.
No PRP CB CB cant map the cell to PRP board since there is no
PRP available. As the result, CB doesnt send Cell
Activation message to GBM.
No GDS CB CB cant map the cell to PRP board since there is no
GCIs available. As the result, CB doesnt send Cell
Activation message to GBM.
No PRP/GDS CB CB cant map the cell to PRP board since there is no
GCIs or PRP available. As the result, CB doesnt send
Cell Activation message to GBM.
GBL OOS GBM No GBL is BU in PCU
NSVC OOS GBM No NSVC is BU in PCU
GbSig OOS GBM Gb signaling is unavailable
PTP BVC GBM GBM fails to reset or unlock
Unaval PointToPoint BVC with SGSN.
Barred GBM No sync. PDCH is available. See PDCH Status and PD
CHANNEL fields for more details.
Unbarred GBM GPRS is ready to go

GPRS Status
Value Process Comment
NA CB Time out on the responsive message occurs

OOS GBM Site is OOS or GSM Cell is OOS. See Status field for more details
GPRS DU GBM The element gprs_enabled is set to zero
No PRP CB CB cant map the cell to PRP board since there is no PRP available.
As the result, CB doesnt send Cell Activation message to GBM.
No GDS CB CB cant map the cell to PRP board since there is no GCIs available.
No PRP/GDS CB CB cant map the cell to PRP board since there is no GCIs or PRP available
GBL OOS GBM No GBL is BU in PCU
NSVC OOS GBM No NSVC is BU in PCU
GbSig OOS GBM Gb signalling is unavailable
PTP BVC unaval GBM GBM fails to reset or unlock pointtopoint BVC with SGSN.
Barred GBM No sync. PDCH is available. See PDCH Status and PD CHANNEL fields
for more details.
Unbarred GBM GPRS is ready to go
Data Collection 18
Figure 2-25

PDCH Status
NA CM/MMI Time out on the
responsive message occurs.
No Cell Activation CRM CRM doesnt receive Cell Activation
message from PRM
In Progress CRM CRM is in progress of configuring
PDCHs
All PDCHs stolen CRM All PDCHs are stolen for circuit calls.
CRM should raise an alarm for every
minute if the situation is sustained.
Available CRM Some PDCHs are configured.
GPRS AccClass Bar

NA CB Time out on the responsive message occurs.
0 SYM Cell is barred.
13 SYM Unbarring the cell is in progress.
4 SYM Cell is completely unbarred.
PD Channel
If the reported timeslots are NA then the Cb process has generated a timeout.
If the reported timeslots are reported with actual numbers (18) and the PDCHs in Free
this means they are ready for data transfer. PDCHs in In Use means they have data
transfer in progress. PDCHs in Unaval means they are not available for data transfer.

PDCH Status
NA CM/MMI Time out on the responsive message occurs
No cell activation CRM CRM doesnt receive Cell Activation message from PRM
In progress CRM CRM is in progress of configuring PDCHs
All PDCHs stolen CRM All PDCHs are stolen for circuit calls. CRM should raise an alarm for
every minute if the situation is sustained
Available CRM Some PDCHs are configured
NA CB Time out on the responsive message occurs
0 SYM Cell is barred.
13 SYM Unbarring the cell is in progress
4 SYM Cell is completely unbarred.
Free In use Unaval Process Comment
NA NA NA CB Time out on the responsive message occurs
08 PRM PDCHs in Free means they are ready for data transfer.
08 08
PDCHs in In Use means they have data transfer in
progress. PDCHs in Unaval means they are not
available for transfer.
Data Collection 19
Figure 2-26


Chapter 3
PDTCH OOS

Version 1 Rev 1

Version 1 Rev 1
Chapter 3
PDTCH OOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Summary of All Known GPRS OOS/ PDTCH OOS Type . . . . . . . . . . . . . . . . . . . . . . . . . 32
..................................................................... 32
GPRS Cell activation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Data Collection procedure (PCUMPROC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Data Collection procedure (PCUPICP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Data Collection procedure (PCUPRP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Data Collection procedure (For NIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Data Collection procedure (on BTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Data collection procedure (type 4 CRM filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Type 1 GPRS Cell Barred, PD No Activation, PD Channel NA . . . . . . . . . . . 320
Type 2a GPRS Cell Barred, PD No Activation, PD Channel 0. . . . . . . . . 322
Type 2a GPRS Cell Barred, PD No Activation, PD Channel 0. . . . . . . . . 324
Type 2b GPRS Cell Barred, Bitmap does not match between PRM and CRM 326
Type 2c GPRS Cell Barred, Cell activation message was dropped from PRM to CRM. .
328
GDS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
GDS Architecture (contd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
GDS fault and PRP fault diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Type 3a Entire GDS Span OOS: everything on pb list logs looks fine. . . . . . . . 336
Type 3b Entire GDS Span OOS: PMC buffer (HOST2NIB) is full . . . . . . . . . . . 338
Type 3c Entire GDS Span OOS: NIB buffer not attached . . . . . . . . . . . . . . . . . . 340
Type 3c Entire GDS Span OOS: NIB buffer not attached (contd) . . . . . . . . . . . 342
Type 4a Individual PDTCH OOS: PDTCH configuring = TRUE, TS stuck on state c8 at CRM . . . . .
344
Type 4b Individual PDTCH OOS: TCH/F configuring = TRUE, TS stuck on state c8 at CRM . . . . . .
346
Type 4c Individual PDTCH OOS: SDCCH configuring = TRUE, TS stuck on state c8 at CRM . . . . .
348
Type 4d Individual PDTCH OOS: GetSDforPDTCH in progress = TRUE, TS configuration
mismatch between configuration manager and Resource view. . . . . . . . . . . . . . . 350
Timer in Timing Alignment Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
TA_ARRAY Decode (for GSR4.1 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
TA_ARRAY Decode (for GSR4.1 only contd)./ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Type 5a Individual PDTCH OOS associated with DRI [15] Alarm . . . . . . . . . . . 360
Type 5b PDTCH Unavailable, Flood SWFM happens on BSP . . . . . . . . . . . . . . 362
Type 5c PDTCH unavailable, Flood SWFM happens on PRP . . . . . . . . . . . . . . 364
Type 5d Individual PDTCH OOS: No UL Frame received on TSN . . . . . . . . . . . 366
Type 5e PD missed, comparing disp_cell_s and disp_rtf_chan . . . . . . . . . . . . . 368

Version 1 Rev 1

Objectives
By the end of this chapter the student will be able to:
Be able to collect the correct data to report a fault relating to PDTCH OOS
problems.

Summary of All Known GPRS OOS/ PDTCH OOS Type Version 1 Rev 1
Summary of All Known GPRS OOS/ PDTCH OOS Type
Type 1 GPRS Cell Barred, PD No Activation, PD Channel NA.
Type 2a GPRS Cell Barred, PD No Activation, PD Channel 0.
Type 2b GPRS Cell Barred, Bitmap do to match between PRM and CRM.
Type 2c GPRS Cell Barred, Cell activation message was dropped from PRM to CRM.
Type 3a Entire GDS Span OOS: everything on pb list logs looks fine.
Type 3b Entire GDS Span OOS: PMC buffer (host2nib) is full.
Type 3c Entire GDS Span OOS: NIB buffer not attached.
Type 4a Individual PDTCH OOS: PDTCH configuring = True, TS stuck on state c8

at CRM.
Type 4b Individual PDTCH OOS: TCH/F configuring = True, TS stuck on state c8 at

CRM.
Type 4c Individual PDTCH OOS: SDCCH configuring = True, TS stuck on state c8 at

CRM .
Type 4d Individual PDTCH OOS: GetSDforPDTCH in progress = True, TS

configuration mismatch between configure manage and Resource view.
Type 5a Individual PDTCH OOS associated with DRI [15] Alarm .
Type 5b PDTCH Unavailable, Flood SWFM happens on BSP.
Type 5c PDTCH unavailable, Flood SWFM happens on PRP.
Type 5d Individual PDTCH OOS: No UL Frame received on TSN.
Type 5e PD missed, comparing disp_cell_status and disp_rtf_chan.

Version 1 Rev 1 Summary of All Known GPRS OOS/ PDTCH OOS Type
Summary of All Known GPRS OOS/ PDTCH OOS Type
1 GPRS Cell Barred
2 GPRS Cell Barred
3 Entire GDS Span OOS
4 Individual PDTCH OOS
5 Individual PDTCH OOS/

UnAvailable
Diagran Number
Figure 3-1

GPRS Cell activation procedure Version 1 Rev 1
GPRS Cell activation procedure

For the procedure to undertake Cell activation procedure please refer to
http://www.cig.mot.com/Organization/GSM/CS/cs_web/
Open Buckets GPRS/PDTCH OOS Design Information Cell activation diagram and
messages.
Caution:
The procedure is for GSR4.1 only.
It is highly recommend not running too many filters on live system, unless you
are sure of the impact to the system.

Issue 0 Rev 0
Version 1 Rev 1
This page intentionally left blank

Data Collection Version 1 Rev 1
Data Collection
Data Collection procedure (PCUMPROC)

On an MPROC:
msg_s 0d0h 9000h 0 0 0 3 (CB summary)
msg_s 0d0h 9000h 0 0 0 4 (CB summary including carrier ID info).
msg_s 0d2h 9000h 0 0 0 0 0 0 0 <local cell id> (Cell state on GBM)
msg_send 0d0h 9000h 0 0 0 9 (determine which local cell ids are being controlled by
which DPROC)
msg_s 40h 9000h 0 0 0 2 <GDS id> (dump GDS info)
fil create src tag 0xxxx70xxh (from CB>GBM)
fil create tag 0xxxx7501h (between GBM and PRM)
fil create tag 0xxxx7502h (between GBM and PRM)
fil create tag 0xxxx77xxh (between the PCU and SGSN)
filter create tag 0xxxx71f9h

Version 1 Rev 1 Data Collection
Data Collection procedure (PCUMPROC)
BSS101_Mod1_Ch4_1
Figure 3-2

Data Collection procedure (PCUPICP)

On a PICP:
msg_s 0dbh 9000h 0 0 0 44 (Shows timeslots OOS).
msg_s 0dbh 9000h 0 0 0 45 (Shows timeslots INS).
msg_s 0dbh 9000h 0 0 0 10 (Toggles between Rlogin/MMI)
msg_s 0dbh 9000h 0 0 0 2 (tell you which slot the given PMC index is in).
msg_s 0dbh 9000h 0 0 0 4 <CN0> <CN1> (Print TS Array).
msg_s 0dbh 9000h 0 0 0 33 (print UL trau stats).
msg_s 0dbh 9000h 0 0 0 34 (print DL trau stats).
msg_s 0dbh 9000h 0 0 0 35 (print UL ptrau stats).
msg_s 0dbh 9000h 0 0 0 36 (print DL ptrau stats).
msg_s 0dbh 9000h 0 0 0 37 (print UL trau throughput).
msg_s 0dbh 9000h 0 0 0 38 (print DL trau throughput).
perf all.
pb list.

Data Collection procedure (PCUPICP)
Figure 3-3

Data Collection procedure (PCUPRP)

On PRP.
msg_s 0d9h 9000h 0 0 7404 04 15 0 0 0 <local cell id> (Cell info in PRM).
msg_s 0d9h 9000h 0 0 7404 04 14 0 0 0 <local cell id> <local carrier id> (Carrier
info in PRM).
msg_s 0d5h 9000h 0 0 0f0h <local cell id> (Cell info in FBM).
msg_send 0d9h 9000h 0 0 7404 04 80 00 00 00 <local cell id > <carrier_id> <ts>

(TS history).
perf all.
pb list.

Data Collection procedure (PCUPRP)
Figure 3-4

Data Collection procedure (For NIB)

Connect the serial cable into the DPROC (were the OOS GDS is physically linked to),
get the following information from NIB.
First type the command:
i
If any task shows status SUSPEND, take the task name and run
tt NAME
substituting the task name for NAME, in double quotes. also performs the following
commands:
d &motTS0s,1,4 ( repeat a couple of times )
d 0xff003c00,64,4
d 0xff003d00,64,4
d 0xff002000,256,4
d &timeSlotInfo,128,4
d &buffDesc,6,4
d &qmc_driver_stats,6,4 ( repeat a number of times )
d &p2t_lookup,256,4
d &ts_inuse,16
d &chanData, 384, 4
d &trauStats,2,4 ( repeat four times )
Finally, check the status of individual trau channels. GCIs name trau channels by
timeslot (131) and group (03). The PMC names trau channels by channel number
((timeslot*4)+group). So if SM and pSM say that a particular timeslot/group should be in
service on a particular GDS, find the PMC which terminates that GDS and run
trau_stats <channel_number>
Where <channel_number> is calculated as stated above. Normally channel numbers
start at 111 and go down from there, so a good first try would be
trau_stats 111
trau_stats 110
trau_stats 109
trau_stats 108
The above commands dump downlink statistics.

Data Collection procedure (For NIB)
NVRAM PROM DRAM PCI

2K 512K 16MB controller P5
32 bit local bus

P11
MCP860 EIA-232 Serial

PowerQUICC
CPU channelized P4
E1 (2 links)
P14
NVRAM PROM DRAM PCI

2K 512K 16MB controller
32 bit local bus

P11
MCP860 EIA-232 Serial

PowerQUICC
CPU channelized
E1 (2 links)
P14
P2
Local PCI Bus
CompactPCI Bus
PCI to PCI
P1
bridge
Figure 3-5

Data Collection procedure (on BTS)

On a BTP:
msg_send 34 9000h 0 0 0 0b3h 0f0h <local cell id> (Carrier Config Manager
Detailed Display Request).
msg_send 34 9000h 0 0 0 0b9h 0f0h <local cell id> (Channel Resource View
Linked List Info Request).
msg_send 34 9000h 0 0 0 0bbh 0f0h <local cell id> (Carrier Config Manager
Display Request (for cell).

Data Collection procedure (on BTS)
REDUNDANT (B) MCUF B FMUX NIU NIU BPSM

B0 B1
ALARM
MODULE
BCU CAGE
ASSEMBLY
MASTER (A) MCUF A FMUX NIU NIU BPSM
A0 A1
PDTCHhoos2
Figure 3-6

Data collection procedure (type 4 CRM filter)

Set the following filters and iirs at CRM (at the BTS, on the BTP) prior to the occurrence:
msg_send 34 9000h 0 0 0 0beh 10
msg_send 34 9000h 0 0 0 0beh 11
msg_send 34 9000h 0 0 0 0beh 12
msg_send 34 9000h 0 0 0 0beh 16
iir_mod 34 11018h
fil create tag 0xxxx73xxh
fil start all
Inject the following messages at CRM after problem is reproduced (at the BTS, on the
BTP):
msg_send 34 9000h 0 0 0 0b3h 0f0h <local cell id>
swfm list all (BTP & LCF controlling site)
swfm read all (BTP & LCF controlling site)
Disable logging (at the BTS, on the BTP):

msg_send 34 9000h 0 0 0 0beh 0

Data collection procedure (type 4 CRM filter)
AM
CRM
RRSM
RCI
CBS
CP
CFM ABIS
LAYER2 HDPC
LAYER1 RSS
PDTCHhoos3
Figure 3-7

Analysis Version 1 Rev 1
Analysis
Type 1 GPRS Cell Barred, PD No Activation, PD Channel NA

How to identify this problem:
Disp_cell_status <site>
From PRP there is no Cell info.
PCU:emon_110d % msg_send 0d9h 9000h 0 0 7404 04 15 0 0 0 27
Cell Info
No Cell Info Found For Requested Cell(s).
From GBM the cell is waiting PRM (INS,BAR) (S2)
PCU:emon_1107 % msg 0d2h 9000h 0 0 0 0 0 0 0 27

Cell id 27, Cell state WAIT PRM(INS,BAR) (S2), BVCI 20383 (0x4f9f),
BVCI flags: Gb_avail 1, Gb_sig 1, BSC cell 1, site 1, CB 1, GPRS 1
BLK_cause: ff, RST_cause 1, Retries 0, Timer 0
INS_OP 1, CB_code 1
Cell service state: GPRS OOS (S0)

Version 1 Rev 1 Analysis
Type 1 GPRS Cell Barred, PD No Activation, PD Channel NA
MMIRAM 0218 > disp _cell_s 4

GSM CELL ID
MCC 234 234
MNC 10 10
LAC 5099 (13EBh) 5099 (13EBh)
CI 14181 (3765h) 24181 (5E75h)
RAC 99 (0063h) 99 (0063h)

Frequency Type PGSM PGSM
BCCH Frequency 123 114

Status Unbarred Unbarred

GPRS Status Unbarred Barred
PDCH Status PD Available No Activation
Reset in Prog No No
GPRS Reset in Prog No No
SPI in Prog No No
BSS BSSAP Prhb NA NA
MSC BSSAP Phrb NA NA
SPI/MSC SCCP Prhb NA NA
AccClassBar None None
GPRSAccClassBar 4 NA
Full Power Mode OFF OFF
Ext Range Mode OFF OFF
FREE INUSE UNAVL FREE INUSE UNAVL

SDCCH 7 1 0 7 1 0
Norm Outer TCH/F 8 2 0 3 3 0
Norm Inner TCH/F 0 0 0 0 0 0
Ext Outer TCH/F 0 0 0 0 0 0
PD CHANNEL 4 0 0 NA NA NA
End of Report.
PDTCHhoos2a
Figure 3-8


Type:
Disp_cell_status <site>
From GBM cell status is WAIT PRM(INS,BAR) (S2)
PCU:emon_1107 % msg_s 0d2h 9000h 0 0 0 0 0 0 0 9
Cell id 9, Cell state WAIT PRM(INS,BAR) (S2), BVCI 1009 (0x3f1),
BLK_cause: ff, RST_cause 8, Retries 0, Timer 0
INS_OP 1, CB_code 1
Cell service state: GPRS OOS (S0)

Type 2a GPRS Cell Barred, PD No Activation, PD

Channel 0.
MMIRAM 0218 > disp_cell_s4
GSM CELL ID
MCC 234 234
MNC 10 10
LAC 5099 (13EBh) 5099 (13EBh)
CI 14181 (3765h) 24181 (5E75h)

RAC 99 (0063h) 99 (0063h)

Frequency Type PGSM PGSM
BCCH Frequency 123 114

Status
Status Unbarred
Unbarred Unbarred
Unbarred
GPRSStatus
GPRS Status Unbarred
Unbarred Barred
Barred
PDCHStatus
PDCH Status PDPD
Available
AvailableNo Activation
No
Activation
Reset in Prog No No
GPRS Reset in Prog No No
SPI in Prog
Prog No
No NoNo
BSS BSSAP Prhb NA NA
MSC BSSAP Prhb NA NA

SPI/MSC SCCP Prhb NA NA
AccClassBar None None

GPRSAccClassBar 4 NA
Full Power Mode OFF OFF

Ext Range Mode OFF OFF
FREE INUSE UNAVL FREE INUSE UNAVL

SDCCH 7 1 0 7 1 0
Norm Outer TCH/F 8 2 0 3 3 0
Norm Inner TCH/F 0 0 0 0 0 0

Ext Outer TCH/F 0 0 0 0 0 0
PD CHANNEL 4 0 0 0 0 0
PDTCHhoos4
End of Report.
Figure 3-9


From PRM Cell info, the Number of Carrier INS is 0
PCU:emon_1106 % msg_s 0d9h 9000h 0 0 7404 15 0 0 0 9

Type 2a GPRS Cell Barred, PD No Activation, PD

Channel 0
PCU:emon_1106% msg_s 0d9h 9000h 0 0 7 404 15 0 0 0 9
Cell Info
LCID: 9
LCIdx : 28
St: 2
BCCHCrID: 255
GSvcSt : INS
GBarSt: Barred
Next PSvcSt: OOS
NextPBarSt: Barred
Pres PSvcSt: OOS
Pres PBarSt: Barred
RSSDel: 10
GBM Cell State Change Request Pending Flag: FALSE
Cell Act Timeout: 5000
Cell Act Count: 0
Cell ActTmrID: 0x00000000
Cell ActPend: FALSE
Cell Act Rcvd: TRUE
Cell Act inProg: FALSE
CellDeactTimeout: 200
CellDeactTimer: 0x00000000
CellDeactCount: 0
Cell Deact Pend: FALSE
Cell RstTimeout: 30000
Cell RstTimer: 0x00000000
Cell Rst in Prog : FALSE
Total Cell Act/React count: 6
Total Cell Reset count: 0
Num Carriers: 1
SysInfo Req Cnt: 0
SysInfo Pend : FALSE
Num Carriers INS: 0

Curr Stat Buff: 0
MAUIP: FALSE
MAWCon: FALSE
StTim: 0x00000000
Sync Timeslots: UNAVAILABLE
PDTCHoos5 Frequency type: 1
CR[ 0] ID: 0
Figure 3-10

Type 2b GPRS Cell Barred, Bitmap does not match between PRM and CRM
From disp_cell_status, same as type 2a.
Compare PRM carrier info and CRM carrier info, bitmap is mismatched.
msg 0d9h 9000h 0 0 7404 04 14 0 0 0 21 0
MCU:emon_1015 % msg 34 9000h 0 0 0 0b3h 0f0h 21

Type 2b GPRS Cell Barred, Bitmap do to match between PRM and CRM
msg 0d9h 9000h 0 0 7404 04 14 0 0 0 21 0 MCU:emon_1105 % msg34 9000h 0 0 0 0b3h 0f0h 21

CRM: CR CONFIG MGR DATA for cell 15h:
Carrier Info Current State = 0h IDLE
Local Cell ID: 21 Number SDcapable carriers going INS = 0h
Local CR ID: 0 Number SDcapable carriers going OOS = 0h
Number timeslots going OOS = 0h
Local CR State: 1
Number SD timeslots going INS = 0h
Logging: FALSE Number SD timeslots INS = 2h
Max GPRS TS: 1 Number SD timeslots preferred = 2h

Number SD timeslots max = 6h
Number SD timeslots reconfig = 0h
ResGPRS TS: 1 SD timeslot delta = 0

BCCH carrier ID = 0h
CBCH state = 0h INACTIVE
CBCH carrier ID = ffh
TS Bitmap: 0x00 CBCH timeslot ID = 8h

next CBCH carrier ID = ffh
CRM TS Bitmap: 0x00 next CBCH timeslot ID = 8h

CBCH Abis channel number = 0h
SMSCB state = 0h INACTIVE
SD for TCH/F carrier ID = ffh
SD for TCH/F timeslot ID = 8h
MA Update Rec flag: TRUE TCH/F configuring = FALSE

SD for PDTCH carrier ID = ffh
TS[0]: ULTFI Map: 0xff 0xff DLTFI Map: 0xff 0xff PICP ID: 0xff State: INACTIVE SD for PDTCH timeslot ID = 8h
TS[1]: ULTFI Map: 0xff 0xff DLTFI Map: 0xff 0xff PICP ID: 0x ff State: INACTIVE PDTCH configuring = FALSE
Get TCH/F cause = 0h NONE
TS[2]: ULTFI Map: 0xff 0xff DLTFI Map: 0xff 0xff PICP ID: 0x ff State: INACTIVE TCH/F for SD carrier ID = ffh
TS[3]: ULTFI Map: 0xff 0xff DLTFI Map: 0xff 0xff PICP ID: 0x ff State: INACTIVE TCH/F for SD timeslot ID = 8h
TS[4]: ULTFI Map: 0xff 0xff DLTFI Map: 0xff 0xff PICP ID: 0x ff State: INACTIVE PDTCH for SD carrier ID = ffh
PDTCH for SD timeslot ID = 8h
TS[5]: ULTFI Map: 0xff 0xff DLTFI Map: 0xff 0xff PICP ID: 0x ff State: INACTIVE
SDCCH configuring = FALSE
TS[6]: ULTFI Map: 0xff 0xff DLTFI Map: 0xff 0xff PICP ID: 0x ff State: INACTIVE CBT4 timer ID = 0h
TS[7]: ULTFI Map: 0xff 0xff DLTFI Map: 0xff 0xff PICP ID: 0x ff State: INACTIVE Chanel reconfiguration enabled = FALSE
Mobile O&D enabled = FALSE
Asg Stat Cnt : 0 MS Idx /TS: 00 NUM RSS Blks : 00
BCCH timeslot(s) INS = TRUE
TS AFN MFrame # RelBlk # Blk Delay UL_CA DL_CA UL_ABN DL_ABN CBCH enabled = FALSE
GetSDforTCH/F in progress = FALSE
GetSDforCBCH in progress = FALSE
00 0 0 00 00 00 00 0 0
GetSDforPDTCH in progress = FALSE
01 0 0 00 00 00 00 0 0 CBCH allowed on SD/8 = TRUE
02 0 0 00 00 00 00 0 0 Carrier List SD load 2 count = 0h
03 0 0 00 00 00 00 0 0 Carrier List SD load 1 count = 2h carriers: 00h 01h

Carrier List SD load 0 count = 1h carriers: 02h
04 0 0 00 00 00 00 0 0 Carrier State Change List count = 3h carriers: 00h 01h 02h
05 0 0 00 00 00 00 0 0 List of all SD capable carriers count = 3h carriers: 00h 01h 02h
06 0 0 00 00 00 00 0 0 Carriers in Cell List count = 3h carriers: 00h 01h 02h

Number of GPRS carriers = 1h
07 0 0 00 00 00 00 0 0
Cell Activate Rcvd = TRUE
TS Received: 0 Cell Deactivate Rcvd = FALSE
Total TS Outstanding: 0 Number of TCHs to be configured as PDTCHs = 0h
GPRS Cell Alarm Raised = FALSE
TS: 0 MS Index: 0x00 TAI Counter: 0xff TAI Piece: 0x00000000
Number of PDTCHs to be configured as TCHs = 0h
TS: 2 MS Index: 0x00 TAI Counter: 0xff TAI Piece: 0x00000000 GPRS CR DATA for carrier 0h:
TS: 3 MS Index: 0x00 TAI Counter: 0xff TAI Piece: 0x00000000 Max GPRS Timeslots: 1h, Reserved GPRS Timeslots: 1h
CRM Switchable Bitmap : 0h, CRM Reserved Bitmap: 80h
PRM Switchable Bitmap : 0h, PRM Reserved Bitmap: 80h
RSS Block Bitmap Ma Update sent: TRUE, MA Update Ack rcvd: TRUE
TS[0] 0 0 0 0 0 0 0 0 0 0 0 0 MA update or Cr State Chg count: 0, MA update or Cr Stat e Chg timer: 0
TS[1] 0 0 0 0 0 0 0 0 0 0 0 0 Cr Status count: 1h, Cr Status timer: 0h

Cr Status reason: 0h
TS[2] 0 0 0 0 0 0 0 0 0 0 0 0 Cr Info Sent: TRUE
TS[3] 0 0 0 0 0 0 0 0 0 0 0 0 Last TS request timer: 0h
TS[4] 0 0 0 0 0 0 0 0 0 0 0 0 GPRS Carrier Alarm Raised: FALSE
TS[5] 0 0 0 0 0 0 0 0 0 0 0 0
TS[6] 0 0 0 0 0 0 0 0 0 0 0 0
TS[7] 0 0 0 0 0 0 0 0 0 0 0 0
PDTCHoos6
Figure 3-11

Type 2c GPRS Cell Barred, Cell activation message was dropped from PRM
to CRM.
From disp_cell_status this appears the same as type2a.
Compare PRP cell info and CRM cell info

PCU:emon_1103 % msg 0d9h 9000h 0 0 7404 04 15 0 0 0 15
GPROC1_RAM:emon_1015 % msg 34 9000h 0 0 0 0b3h 0f0h 15
From the PRP board which control the cell, the opposite SWFM is seen:

Type 2c GPRS Cell Barred, Cell activation message was dropped from PRM
to CRM.
PCU:emon_1103 % msg 0d9h 9000h 0 0 7404 04 15 0 0 0 15 GPROC1_RAM:emon_1015 % msg 34 9000h 0 0 0 0b3h 0f0h 15
Cell Info
LCID: 15 CRM: CR CONFIG MGR DATA for cell fh:
LCIdx: 7 Current State = 0h IDLE
St: 1 Number SDcapable carriers going INS = 0h

Number SDcapable carriers going OOS = 0h
BCCHCrID : 1 Number timeslots going OOS = 0h
GSvcSt : INS Number SD timeslots going INS = 0h
GBarSt : Barred Number SD timeslots INS = 1h

Number SD timeslots preferred = 1h
Next PSvcSt : OOS Number SD timeslots max = 2h
Next PBarSt : Barred Number SD timeslots reconfig = 0h
Pres PSvcSt : OOS SD timeslot delta = 0
Pres PBarSt : Barred CBCH state = 1h ACTIVE
RSSDel : 10 CBCH carrier ID = 2h
GBM Cell State Change Request Pending Flag: FALSE CBCH timeslot ID = 1h
Cell Act Timeout: 5000 next CBCH timeslot ID = 8h
Cell Act Count: 3 CBCH Abis channel number = 51h
Cell Act Tmr ID: 0x239603eb SMSCB state = 1h ACTIVE
SD for TCH/F carrier ID =ffh
Cell Act Pend: TRUE SD for TCH/F timeslot ID = 8h

TCH/F configuring = FALSE
SD for PDTCH carrier ID =ffh
SD for PDTCH timeslot ID = 8h
Cell Act Rcvd: FALSE PDTCH configuring = FALSE

Cell Act in Prog: TRUE

TCH/F for SD carrier ID = ffh
TCH/F for SD timeslot ID = 8h
PDTCH for SD carrier ID =ffh
Cell Deact Timeout: 200 CBT4 timer ID = 0h
Cell Deact Timer: 0x00000000 Chanel reconfiguration enabled = FALSE
Cell Deact Count: 0 Mobile O&D enabled = FALSE

Cell Deact Pend : FALSE CBCH enabled = TRUE
Cell Rst Timeout: 30000 GetSDforTCH/F in progress = FALSE
Cell Rst Timer: 0x00000000 GetSDfor CBCH in progress = FALSE
Cell Rst in Prog : FALSE GetSDfor PDTCH in progress = FALSE

CBCH allowed on SD/8 = TRUE
Total Cell Act/React count: 1 Carrier List SD load 2 count = 0h
Total Cell Reset count: 0 Carrier List SD load 1 count = 1h carriers: 02h
Num Carriers: 1
Carrier State Change List count = 2h carriers: 02h 05h
SysInfo Req Cnt :0 List of all SD capable carriers count = 2h carriers: 02h 05h
SysInfo Pend : FALSE Carriers in Cell List count = 2h carriers: 02h 05h
Num Carriers INS: 1
Curr Stat Buff: 0
MAUIP: FALSE
MAWCon : FALSE
StTim : 0x00000000
Cell Activate Rcvd = FALSE
Cell Deactivate Rcvd = FALSE
Number of TCHs to be configured as PDTCHs = 0h
Sync Timeslots: UNAVAILABLE
Frequency type: 1 Number of PDTCHs to be configured as TCHs = 0h
CR[ 0] ID: 2 GPRS CR DATA for carrier 2h:
Max GPRS Timeslots: 0h, Reserved GPRS Timeslots: 0h
CRM Switchable Bitmap: 0h, CRM Reserved Bitmap: 0h, CRM Transaction Id: 0h
PRM Switchable
Switchable
Bitmap: oh, PRM Reserved Bitmap: Oh, PRM Transaction id: 0h
Ma Update sent: FALSE, MA Update ACk rcvd: FALSE, MA Update Nack rcvd: FALSE
MA update or Cr State Chg count: 1, MA update or Cr State Chg timer: 0
Cr Status count: 0h, Cr Status timer: 0h
Cr Info Sent: TRUE
Last TS request timer: 0h
GPRS Carrier Alarm Raised: FALSE
PDTCHoos7
Figure 3-12
Type 2c GPRS Cell Barred, cell activation message was

dropped from PRM to CRM
9e8 Nonfatal SWFM Error Routine: prm_process_cell_activation_tmr

9e8 Area: 0x00000000 Error: 0x00000000 PC: 0x0114111c PID: 0xd9 (PRM)
9e8 BSS Release: 1.0.0.0.0 Obj Version: 1.0.0.0.0
9e8 02Jul2001 12:30:13.540 Subsystem: Oxfe CPU: 0x1103 Board:DPROC
9e8 Cell Activation for 15 failed for the maximum number of times 3
PDTCHoos8
Figure 3-13

GDS Architecture Version 1 Rev 1
GDS Architecture
1) GDS is in service, with pci buffers between TSN in slot 1 and TRAUPIPE in PRP slot.
(2) Physical hard reset of slot 1 causes PCIMGT to poll the board as dead and send a
PCI_EVENT_HARD_RESET event message to pFTP.
(3) PCIMGT also sends PCI_UNLINK_MSG to every other PCIMGT in the cage, telling
them that dproc 1 is dead and that all pci buffers which terminate on dproc 1 should be
marked as stale.
(4) TRAUPIPE attempts a pb_fread from TSNs buffer only to find it stale. TRAUPIPE
then tears down all its buffers (the read and write buffers to TSN, and the read and write
buffers to the NIB). TRAUPIPE the recreates an incoming buffer for a new TSN to attach
to.
(5) The NIB attempts to pb_fread from its incoming buffer and finds it stale (detached) so
it detaches and destroys, and then creates a new incoming buffer, waiting for new
connection.
(6) pFTP receives event message from PCIMGT and sends disableenablehardreset to
pCA for dproc 1.
7) pCA brings the dproc state machine down; in the process, the GDS is remapped to
TSN in dproc 2.
(8) TSN pb_creates a buffer for TRAUPIPE to write to.
(9) TSN pb_attaches to TRAUPIPE and sends a BUFFER_SELECT message, which
contains the name of the readbuffer TSN created in step 8.
(10) TRAUPIPE does pb_attach to the NIB.
(11) TRAUPIPE does pb_attach back to TSNs buffer created in step 8.
(12) TRAUPIPE does pb_create for NIB to write to.
(13) TRAUPIPE sends BUFFER_SELECT to NIB telling the NIB the name of the buffer
created in step 12.
(14) The NIB attaches to the buffer created in step 12.
(15) TSN begins sending channelenables to the NIB and channels begin coming in
service.
Some things to note:
(a) Steps 3 thru 5 occur in parallel with steps 6 thru 8.
(b) The NIB only performs pb_freads from its incoming buffer at fourmillisecond
intervals. (c) The trau pipe only performs pb_freads from its incoming buffers at
twomillisecond intervals.
(d) Trau pipe polls for buffer_select from TSN at 500 millisecond intervals before
performing step (10), so depending on when the request arrives there can be anywhere
from a 0500 ms delay in processing that request.
(e) When trau pipe does anything related to attaching or detaching buffers, it performs
printf calls to tell what its doing. Unfortunately, its not doing lprintf so you wont see
these prints over an rlogin connection. You will only see them if youre qcommed directly

Version 1 Rev 1 GDS Architecture
GDS Architecture
Host2NIBX Host2NIBXX PRPX > TSNX
GDS
GDS TRAU TSN
NIB Pipe PRM
nib2tsnXX pmc2tsnX buffy_cpuid
NIB to TSN attach sequence pb_create pb_attach
1 4 1 2
GDS TRAU
TSN
NIB Pipe
8 6 5 1
3 TSN sends bufferselect message to trau pipe

7 trau pipe sends bufferselect message to NIB
PDTCHoos9
Figure 3-14

GDS Architecture (contd)

into the dproc itself at the time the messages are printed. You also probably have to be at
level 3 to see them.
(f) If trau pipe attempts to attach to the NIBs buffer at step (10) but the NIB has not yet
destroyed and recreated its buffer, the trau pipe will fail to attach; at this time it will then
detach the buffer attached in step (9) and TSN will be left without a connection.
(g)I f TSN does not get a success code from pb_fread, it does NOT check for stale, and
will never destroy that buffer until a later reconfiguration causes TSN to reuse that PMC
index. (Actually, this may sound like a problem, but it isnt really.)

GDS Architecture
Host2NIBX Host2NIBXX PRPX > TSNX
GDS
GDS TRAU TSN
NIB Pipe PRM
nib2tsnXX pmc2tsnX buffy_cpuid
NIB to TSN attach sequence pb_create pb_attach
1 4 1 2
GDS TRAU
TSN
NIB Pipe
8 6 5 1
3 TSN sends bufferselect message to trau pipe

7 trau pipe sends bufferselect message to NIB
PDTCHoos9
Figure 3-15

GDS fault and PRP fault diagram

The diagram opposite covers the buffer setup procedure and if one GDS or PRP board
is dead, what impact to systemwill this have?

GDS fault and PRP fault diagram

Type 3a Entire GDS Span OOS: everything on pb list logs looks fine.
How to Identify this problem type:
Entire GDS Span OOS, but everything on pb list of PICP & PRP board looks fine.
From TSN TS_ARRAY, there is an indication that the CCU does not sync with DL sync
frame.

Type 3a Entire GDS Span OOS: everything on pb list logs

looks fine.
" # )021$&05+$5)1((&,,,',

,%1:' :: : 4%0):
!: ::;1'6%6):**
211:: :**: :
1(-'%6) (2)5
.:)370: .:*.: ;1':
126,%8)5;1'9-6,
//.:& :( :)//: 64%7*4%0)
:
) : 211: ))3 :*
&-5

&-5 -1'4)%5)
26: )/%;: &7656-//
56%;%6
PDTCHhoos11a
Figure 3-16

Type 3b Entire GDS Span OOS: PMC buffer (HOST2NIB) is full

How to identify this problem type:
From pb list on PRP board.

Type 3b Entire GDS Span OOS: PMC buffer (HOST2NIB)

is full
'(/4+)9
20.1%-+340/%0$2'
"(.0/#
1%-+34
2($'44$&*$.((6+&($&,(4 +:("3('($,
9(3(8(&#'-31#6$2
9(3(8(&#'-31#(6$2
9(3(8(&#'-31# '6$2

9(3 ! (

/0 ! ))))))))

9(3"
(6$2

9(3"
'6$2

9(3(8(&#'+31#$6$2
9(3/+% 43/)$)'
9(3%5))9#(
72+4(44$&*$.((6+&($&,(4 +:("3('($,

9(3(8(&#'31#
6$2
9(3(8(&#'31#
(6$2

9(3(8(&#'31#
'6$2
/ 2(-($3(4*(054154.$9%(
9(3! (6$2
% 9(3 ! $

9(3! '6$2

9(3(8(&#'31#
$6$2

9(3 ! $

9(31.& 43/(

9(3! (

PDTCHhoos12
Figure 3-17

Type 3c Entire GDS Span OOS: NIB buffer not attached

From pb list on PICP board.

PCU:emon_1101 % pb list
Read ID Attach Name Device Packet Size Used Peak
80000000 yes exec_dIsp_1107 01000000 var 51200 0 N/A

80000001 yes exec_dIsp_1102 00010d00 var 51200 0 N/A
80000002 no HOST2NIB11 ffffffff 12 23040 0 N/A
80000006 yes exec_dIsp_1103 00010c00 var 51200 0 N/A
80000007 yes GTM0 00010c00 var 16112 0 N/A
80000008 yes exec_dIsp_1105 00010a00 var 51200 0 N/A
80000009 yes GTM1 00010a00 var 16112 0 N/A
8000000a no pmc2tsn0 00010c00 12 12000 0 N/A
8000000b yes PRO0>TSN1 00010c00 60 60000 0 N/A
8000000c yes PRP1>TSN1 00010a00 60 60000 0 N/A
Write ID Attach name Device Size Used Peak
40000001 yes exec_dIsp_1101 01000000 var 51200 0 596

40000002 yes exec_dIsp_1101 00010d00 var 51200 0 0
40000003 yes exec_dIsp_1101 00010c00 var 51200 0 92
40000004 yes BUF1103000 00010c00 var 33180 0 0
40000005 yes exec_dIsp_1101 00010a00 var 51200 0 92
40000006 yes BUF1105000 00010a00 var 33180 0 0
40000007 no HOST2NIB11 00010c00 12 23040 0 480
40000008 yes buffy_1101 00010c00 60 28800 0 360
40000009 yes buffy_1101 00010a00 60 28800 0 180
PDTCHhoos13
Figure 3-18

Type 3c Entire GDS Span OOS: NIB buffer not attached (contd)
From pb list on related PRP board, there is no HOST2NIB in write buffer ID list.

Identify (cont.)
From pb list on related PRP board, there is no HOST2NIB in write buffer ID list
PCU:emon_1103 % pb list
Read ID Attach Name Device Packet Size Used Peak
80000000 yes exec_dIsp_1107 01000000 var 51200 0 N/A

80000001 yes exec_dIsp_1101 00010e00 var 51200 0 N/A
80000002 yes exec_dIsp_1102 00010d00 var 51200 0 N/A
80000003 no HOST2NIB11 00010e00 12 23040 24 N/A
80000005 yes BUF1103000 00010e00 var 33180 0 N/A
80000006 yes BUF1103001 00010d00 var 33180 0 N/A
80000007 yes exec_dIsp_1105 00010a00 var 41200 0 N/A
80000008 yes nib2tsn11 40faf4d0 12 12000 144 N/A
80000009 yes buffy_1101 00010e00 60 28800 0 N/A
Write ID Attach name Device Size Used Used Peak
40000001 yes exec_dIsp_1103 01000000 var 51200 0 1472

40000002 yes exec_dIsp_1103 00010e00 var 51200 0 220
40000003 yes exec_dIsp_1103 00010d00 var 51200 0 68
40000004 yes GTMO 00010e00 var 16112 0 0
40000005 yes GTMO 00010d00 var 16112 0 80
40000006 yes exec_disp_1103 00010a00 var 51200 0 36
40000009 yes PRP0>TSN1 00010e00 60 60000 0 300
PDTCHhoos13a
Figure 3-19

Type 4a Individual PDTCH OOS: PDTCH configuring = TRUE, TS stuck on state c8 at CRM
Run CRM debug msg_s on BTP:

Type 4a Individual PDTCH OOS: PDTCH configuring =

TRUE, TS stuck on state c8 at CRM
GPROC1_RAM:emon_1015 % msg_s 34 9000h 0 0 0 0b3h 0f0h 8e

Current State = 0h IDLE
Number SD capable carriers going INS = 0h
Number SD capable carriers going OOS = 0h
GPROC1_RAM:emon_1015 % msg_s 34 9000h 0 0 0 0b9h 0f0h 8 Number SD timeslots going INS = 0h

Number SD timeslots INS = 1h
CRM CH RES VIEW (CELL ID= 08) LINKED LIST DATA: Number SD timeslots max = 2h
List Type= 02, Number of channels in the list= 008 SD timeslot delta = 0
CR ID= 00, TS ID= 1, CH ID= 0 BCCH carrier ID = 0h

CR ID= 00, TS ID= 1, CH ID= 7 CBCH carrier ID = ffh
CBCH timeslot ID = 8h
CR ID= 00, TS ID= 1, CH ID= 1 next CBCH carrier ID = ffh
next CBCH timeslot ID = 8h
CR ID= 00, TS ID= 1, CH ID= 2 SMSCB state = 0h INACTIVE
CR ID= 00, TS ID= 1, CH ID= 3 SD for TCH/F timeslot ID = 8h
CR ID= 00, TS ID= 1, CH ID= 5 SD for PDTCH carrier ID = ffh
CR ID= 00, TS ID= 1, CH ID= 6 SD for PDTCH timeslot ID = 8h
CRCH
RES VIEW (CELL ID= 08) LINKED LIST DATA: PDTCH configuring = TRUE
List Type= 09, Number of channels in the list= 008 Get TCH/F cause = 0h NONE
CR ID= 00, TS ID= 7, CH ID= 0 TCH/F for SD timeslot ID = 8h
CR ID= 00, TS ID= 5, CH ID= 0 PDTCH for SD carrier ID = ffh
CR ID= 03, TS ID= 0, CH ID= 0 SDCCH configuring = FALSE
CBT4 timer ID = 0h
CR ID= 00, TS ID= 3, CH ID= 0 Chanel reconfiguration enabled = FALSE
CR ID= 03, TS ID= 4, CH ID= 0 Mobile O&D enabled = FALSE

CR ID= 03, TS ID= 2, CH ID= 0 CBCH enabled = FALSE
CR ID= 00, TS ID= 2, CH ID= 0 GetSDforCBCH in progress = FALSE
GetSDforPDTCH in progress = FALSE
CRMCH RES VIEW (CELL ID= 08) LINKED LIST DATA: Carrier List SD load 2 count = 0h
List Type= 1c, Number of channels in the list= 001 Carrier List SD load 0 count = 1h carriers: 03h
CR ID= 00, TS ID= 6, CH ID= 0 List of all SD capable carriers count = 2h carriers: 00h 03h
CRMCH RES VIEW (CELL ID= 08) LINKED LIST DATA: Carriers in Cell List count = 2h carriers: 00h 03h
List Type= 1d, Number of channels in the list= 002 Cell Activate Rcvd = TRUE
CR ID= 03, TS ID= 1, CH ID= 0 Number of TCHs to be configured as PDTCHs = 3h
CR ID= 00, TS ID= 4, CH ID= 0 GPRS Cell Alarm Raised = FALSE
CR Id: 3h TS Id: 7h GPRS Ch Type: 2h
CRMCH
RES VIEW (CELL ID= 08) LINKED LIST DATA: CR Id: 3h TS Id: 6h GPRS Ch Type: 1h
Number of PDTCHs to be configured as TCHs = 0
List Type=c8, Number of channels in the list= 003 GPRS CR DATA for carrier 3h:
CR ID= 03, TS ID= 7, CH ID= 0 CRM Switchable Bitmap: 0h, CRM Reserved Bitmap: 0h
PRM Switchable Bitmap: 0h, PRM Reserved Bitmap: 0h
Ma Update sent: FALSE, MA Update Ack rcvd: FALSE
CR ID= 03, TS ID= 6, CH ID= 0 MA update or Cr State Chg count: 1, MA update or Cr State Chg timer: 0
CR ID= 03, TS ID= 5, CH ID= 0 Cr Status reason: 0h

Cr Info Sent: TRUE
PDTCHhoos15
Figure 3-20

Type 4b Individual PDTCH OOS: TCH/F configuring = TRUE, TS stuck on

state c8 at CRM

Type 4b Individual PDTCH OOS: TCH/F configuring =


GPROC1_RAM:emon_1015 % msg_s 34 9000h 0 0 0 0b9h 0f0h 8 Number timeslots going OOS = 0h

CRM CH RES VIEW (CELL ID= 08) LINKED LIST DATA: Number SD timeslots preferred = 1h
List Type= 02, Number of channels in the list= 008 Number SD timeslots max = 2h
CR ID= 00, TS ID= 1, CH ID= 0 SD timeslot delta = 0
CR ID= 00, TS ID= 1, CH ID= 7 CBCH state = 0h INACTIVE
CBCH carrier ID = ffh
CR ID= 00, TS ID= 1, CH ID= 4 next CBCH carrier ID = ffh
CR ID= 00, TS ID= 1, CH ID= 2 CBCH Abis channel number = 0h
SMSCB state = 0h INACTIVE
CR ID= 00, TS ID= 1, CH ID= 6 TCH/F configuring = TRUE
CRCH
RES VIEW (CELL ID= 08) LINKED LIST DATA:
List Type= 09, Number of channels in the list= 008 TCH/F for SD carrier ID = ffh
CR ID= 00, TS ID= 7, CH ID= 0 PDTCH for SD carrier ID = ffh
CR ID= 03, TS ID= 0, CH ID= 0 CBT4 timer ID = 0h
Chanel reconfiguration enabled = FALSE
CR ID= 03, TS ID= 2, CH ID= 0 GetSDforTCH/F in progress = FALSE

CR ID= 00, TS ID= 2, CH ID= 0 GetSDforPDTCH in progress = FALSE
CR ID= 03, TS ID= 3, CH ID= 0 Carrier List SD load 2 count = 0h
CRMCH RES VIEW (CELL ID= 08) LINKED LIST DATA:
List Type= 1c, Number of channels in the list= 001 Carrier State Change List count = 2h carriers: 00h 03h
List of all SD capable carriers count = 2h carriers: 00h 03h
CR ID= 00, TS ID= 6, CH ID= 0 Carriers in Cell List count = 2h carriers: 00h 03h
List Type= 1d, Number of channels in the list= 002 Cell Deactivate Rcvd = FALSE
CR ID= 03, TS ID= 1, CH ID= 0 GPRS Cell Alarm Raised = FALSE
CRMCH
RES VIEW (CELL ID= 08) LINKED LIST DATA: Number of PDTCHs to be configured as TCHs = 0
List Type=c8, Number of channels in the list= 003 GPRS CR DATA for carrier 3h:
CRM Switchable Bitmap: 0h, CRM Reserved Bitmap: 0h
CR ID= 03, TS ID= 7, CH ID= 0 PRM Switchable Bitmap: 0h, PRM Reserved Bitmap: 0h
Ma Update sent: FALSE, MA Update Ack rcvd: FALSE
CR ID= 03, TS ID= 6, CH ID= 0 Cr Status count: 0h, Cr Status timer: 0h
Cr Info Sent: TRUE
CR ID= 03, TS ID= 5, CH ID= 0 Last TS request timer: 0h
PDTCHhoos16
Figure 3-21

Type 4c Individual PDTCH OOS: SDCCH configuring = TRUE, TS stuck on

state c8 at CRM

Type 4c Individual PDTCH OOS: SDCCH configuring =


GPROC1_RAM:emon_1015 % msg_s 34 9000h 0 0 0 0b9h 0f0h 8 Number SD timeslots going INS = 0h
List Type= 02, Number of channels in the list= 008 Number SD timeslots reconfig = 0h
SD timeslot delta = 0
CR ID= 00, TS ID= 1, CH ID= 0 BCCH carrier ID = 0h
CR ID= 00, TS ID= 1, CH ID= 7 CBCH carrier ID = ffh
CR ID= 00, TS ID= 1, CH ID= 1 CBCH timeslot ID = 8h
CR ID= 00, TS ID= 1, CH ID= 4 next CBCH timeslot ID = 8h
CR ID= 00, TS ID= 1, CH ID= 2 SMSCB state = 0h INACTIVE
CR ID= 00, TS ID= 1, CH ID= 3 SD for TCH/F carrier ID =ffh
CR ID= 00, TS ID= 1, CH ID= 5 Get TCH/F cause = 0h NONE
CR ID= 00, TS ID= 1, CH ID= 6 TCH/F for SD timeslot ID = 8h
PDTCH for SD carrier ID = ffh
CRCH RES VIEW (CELL ID= 08) LINKED LIST DATA: PDTCH for SD timeslot ID = 8h
SDCCH configuring = TRUE
Chanel reconfiguration enabled = FALSE
CR ID= 00, TS ID= 3, CH ID= 0 GetSDforTCH/F in progress = FALSE
CR ID= 03, TS ID= 4, CH ID= 0 GetSDforPDTCH in progress = FALSE
CR ID= 03, TS ID= 2, CH ID= 0 Carrier List SD load 2 count = 0h
CR ID= 03, TS ID= 3, CH ID= 0 Carrier State Change List count = 2h carriers: 00h 03h
List of all SD capable carriers count = 2h carriers: 00h 03h
CRMCH RES VIEW (CELL ID= 08) LINKED LIST DATA: Carriers in Cell List count = 2h carriers: 00h 03h
List Type= 1c, Number of channels in the list= 001 Cell Activate Rcvd = TRUE
CR ID= 00, TS ID= 6, CH ID= 0 Cell Deactivate Rcvd = FALSE
CRMCH RES VIEW (CELL ID= 08) LINKED LIST DATA: GPRS Cell Alarm Raised = FALSE
List Type= 1d, Number of channels in the list= 002 CR Id: 3h TS Id: 6h GPRS Ch Type: 1h
CR ID= 03, TS ID= 1, CH ID= 0 CR Id: 3h TS Id: 5h GPRS Ch Type: 1h
Number of PDTCHs to be configured as TCHs = 0
GPRS CR DATA for carrier 3h:
CRMCH
RES VIEW (CELL ID= 08) LINKED LIST DATA: Max GPRS Timeslots: 3h, Reserved GPRS Timeslots: 1h
List Type=c8, Number of channels in the list= 003 Ma Update sent: FALSE, MA Update Ack rcvd: FALSE
CR ID= 03, TS ID= 7, CH ID= 0 Cr Status reason: 0h
Cr Info Sent: TRUE
CR ID= 03, TS ID= 6, CH ID= 0 Last TS request timer: 0h

PDTCHhoos17
Figure 3-22

Type 4d Individual PDTCH OOS: GetSDforPDTCH in progress = TRUE,

TS configuration mismatch between configuration manager and Resource
view.
Run CRM cell info and carrier info on BTP:

Type 4d Individual PDTCH OOS: GetSDforPDTCH in

progress = TRUE, TS configuration mismatch between
configuration manager and Resource view.
CRM: CR CONFIG MGR DATA for cell 5ch:
Number SD capable
carriers going INS = 0h
Number SD capable
carriers going OOS = 0h
SD timeslot delta = 3
CBCH state = 1h ACTIVE
CBCH carrier ID = 2h
SMSCB state = 1h ACTIVE
SD for TCH/F carrier ID = ffh
SD for TCH/F timeslot ID = 8h
SD for PDTCH carrier ID = 2h
PDTCH configuring = FALSE
PDTCH for SD carrier ID = ffh
CBT4 timer ID = 0h
Chanel reconfiguration enabled = TRUE
Mobile O&D enabled = FALSE
CBCH enabled = TRUE
GetSDforPDTCH
in progress = TRUE
Carrier List SD load 1 count = 2h carriers: 03h 04h
Carrier List SD load 0 count = 0h
List of all SD capable carriers count = 3h carriers: 02h 03h 04h
Carriers in Cell List count = 3h carriers: 02h 03h 04h
Number of PDTCHs to be configured as TCHs = 0h
GPRS CR DATA for carrier 2h:

CRM Switchable Bitmap: 40h, CRM Reserved Bitmap: 0h, CRM Transaction Id; e2h
PRM Switchable Bitmap: 40h, PRM Reserved Bitmap: 0h, CRM Transaction Id; e2h
Ma Update sent: TRUE, MA Update Ack rcvd: TRUE, MA Update Nack rcvd: FALSE
MA update or Cr State Chg count: 0, MA update or Cr State Chg ti mer: 0
Cr Status Delay Flag: FALSE, Cr Status Delay Timer: 0h
Cr Info Sent: TRUE
GPROC2_RAM: emon_1015 % msg 34 9000h 0 0 0 0b9h 0f0h 92

CRMCH
RES VIEW (CELL ID= 5c) LINKED LIST DATA:
CRMCH

CRMCH
RES VIEW (CELL ID= 5c) LINKED LIST DATA:M
CRMCH
PDTCHhoos18
Figure 3-23

Timer in Timing Alignment Procedure

Four timer exist:
TsyncS: 12 Seconds
TsyncS is started when the CCU enters the Initial Time Alignment state and is stopped
when the CCU enters the Static Time Alignment state.
TsyncI: 4 Seconds
TsyncI is started by the CCU when the CCU sends the first Uplink Synchronization frame
and is cancelled when the CCU receives the first Downlink Synchronization frame.

Timer in Timing Alignment Procedure
CCUTSN time alignment procedure
CRM CCU TSN
Initial State(I) In service

first UL sync frame(eSSN=ff)
TsyncI (4 sec) start TsyncI
expired TsyncI UL sync frame(eSSN=ff)
UL sync frame(eSSN=ff)

DL sync frame (SSN=0, SSI=0)
stopped TsyncI
Initial state(ii) start TsyncS UL sync frame (eSSN=0)
DL sync frame (SSN=1, SSI=0)
UL sync frame(eSSN=1)
TsyncS (12 sec)

Static State DL sync frame (SSN=1, SSI=1)
Idle Frame
DRI 15 stop TsyncS
generated
expired TsyncS UL sync frame
Diagran Number
Figure 3-24

TsyncD: 1 Second
TsyncD is started when CCU detects loss of frame synchronization, and is cancelled
when the CCU receives three consecutive frames, which have no errors on the
synchronization pattern and the control bits.
TsyncU: 1 Second
TsyncU is start when the CCU receives three consecutive frames indicating an Uplink
Frame Error and which has no errors on the synchronization pattern and the control bits,
and cancelled when CCU receives 3 consecutive frames indicating no Uplink Frame
Error and which have no errors on the synchronization pattern and the control bits.

Timer in Timing Alignment Procedure Contd
UL frame
DL sync frame(UEF=0)
start TsyncU

Stop TsyncU

expired TsyncU first UL sync frame(eSSN=ff)
DL frame
start TsyncD

DL frame
DL frame
DL frame
stop TsyncD

expired TsyncD first UL sync frame(eSSN=ff)
Diagran Number
Figure 3-25

TA_ARRAY Decode (for GSR4.1 only)
Chan: Channel Number.

RTD: Round Trip Delay
CR: Local Carrier ID
TS: Timeslot number
Frame: Lastreceived Uplink Frame type (3 bit)
0 TSN_CS_1
1 TSN_CS_2
2 TSN_CS_3
3 TSN_CS_4
4 TSN_TRAU_SYNC
5 TSN_TRAU_IDLE
6 TSN_TRAU_UPLINK_PRACH
7 TSN_TRAU_UNKNOWN
BUFFIDX: PMC buffer index corresponding to Channel Number

TAL: Time Alignment, originated by CCU to indicate how much to retard the link.
DR: Downlink Data Ready.
00 TSN_NO_DATA_READY
01 TSN_DL_DATA_READY
SyncState: Sync State

00 In Sync
0xffh Out of Sync
SSI: Sync status Indicator, used by PCU to indicate to the CCU that PCU is ready to
enter the static time alignment state and that the round trip delay has been obtained.
0 Synchronization process is not yet complete
1 the link is in sync
UFE: Uplink Frame Error, sent in downlink frames to indicate to the CCU the
synchronization status of the uplink at the PCU
0 synchronization has been lost
1 synchronization is good
MS#: Indicate to the PCU the numbers of distinct MS that the radio can track per timeslot
for performing AGC algorithm.
CUTA: Continuous Update Timing Advance Attenuation Level (5 bit), indicated the RF
attenuation from maximum cell site power level at which the CCU shall transmit a TA
update RLC block fro the continuous timing advance update procedure.
00000 No attenuation (full power mode)
00001 2 dB of attenuation
11111 Do not transmit
Other values Reserved

Chan: 0x0041 RTD: 0x05 CR: 0x02 TS: 0x06

Frame: 0x04
BUFFIDX: 0x00000002 TAL: 0x99 DR: 0x00
SyncState:0xff
PRMConn: 0x01 SSI: 0x01 UFE: 0xff MS#: 0x08
CUTA: 0x00
UlBlk#: 0x07 Se1Num: 0x3dUlBlkBM:0x01 DlBlkBM: 0x00 # UlSync: 0x00
DlBlk#: 0x00 DLTACI: 0x01 d266: 0x00 Cell: 0x46

TTS: 0x23 eDLTACI: 0x01 CCUConn:0x01 eSeq#: 0x39
UL AFNbis:1906454 DLAFNbis:106458
TAL Tot: 0x0000008b TAL Delay:0x00000000
PDTCHoos20
Figure 3-26

TA_ARRAY Decode (for GSR4.1 only contd)./

ULBLK#: Uplink Block Number(4 bits), used by CCU to indicate to the PCU the radio
interface block number which this uplink data frame was received on.
0000 uplink block 0
0001 uplink block 1
1011 uplink block 11
1100 Illegal
1111 Illegal
Seq Num: Sequence number (7 bits) originated by TSN, the PCU shall increment the
value of Sync sequence number for every downlink sync frame sent.
#ULSync: Number of consecutive uplink syn frames received. This number is used to
determine when the TSN should start responding to uplink sync frames with downlink
sync frames. After three consecutive uplink sync frames the link is assumed to have
transitioned to initial time alignment state rather than having just received a few bit errors.
DLBLK#: Downlink block number of the last transmitted downlink block
DLTACI: Downlink Time Alignment Command Indicator originated by CCU to indicate

that a new time alignment is necessary.
Cell: Local cell ID
TTS: Used to track when a downlink frame must be send regardless of whether or not an
uplink frame has been received.
eDLTACI: Echoed to the CCU immediately before performing the requested time
alignment, used by PCU to indicate to the CCU that the requested time alignment
change has been implemented and CCU is free to perform additional time alignment
changes.
eSeq: Echoed Sequence number last received from the channel coder, the CCU shall
Initialize this field to the value of its last received syn sequence number field. If CCU
does not have synchronization with the downlink TRAU frame and has no valid sequence
number from the PCU, the CCU shall set this field to the value 0x7F.
UL AFNbis: AFN of the last received uplink block from CCU
DL AFNbis: AFN of the last transmitted downlink block to the CCU
TAL Tot: Total number of TAL received
TAL Delay: Total number of bit pairs by which the TRAU channel has been delayed, Used
to determine if more than a frame of retardation has been performed at which time a
frame has to be discarded to prevent the downlink PMC buffer from overflowing.

Chan: 0x0041 RTD: 0x05 CR: 0x02 TS: 0x06

Frame: 0x04
BUFFIDX: 0x00000002 TAL: 0x99 DR: 0x00
SyncState:0xff
PRMConn: 0x01 SSI: 0x01 UFE: 0xff MS#: 0x08
CUTA: 0x00
UlBlk#: 0x07 Se1Num: 0x3dUlBlkBM:0x01 DlBlkBM: 0x00 # UlSync: 0x00

UL AFNbis:1906454 DLAFNbis:106458
PDTCHoos20
Figure 3-27

Type 5a Individual PDTCH OOS associated with DRI [15] Alarm

From event logs, DRI alarm [15] Initial Synchronization of Radio and GPRS channel
failed is generated for the problem TS.

Type 5a Individual PDTCH OOS associated with DRI [15]

Alarm
[11/04/01 09:50:56] PCU:emon_1102 % msg_s 0dbh 9000h0 0 0 4 0 41h
Chan: 0x0041 RTD: 0x05 CR: 0x02 TS: 0x06 Frame 0x04
BUFFIDX: 0x00000002 TAL: 0x99 DR: 0x00SyncState: 0xff
PRMConn: 0x01 SSI: 0x01 UFE: 0xff MS#: 0x08 CUTA: 0x00
UlBlk#: 0x06 Seq Num: 0x1c UIBlkBM:0x07 DIBlkBM:0x00 #UISync: 0x00
DlBlk#: 0x0b DLTACI: 0x01 d266: 0x00 Cell: 0x46
TTS: 0x23 eDLTACI: 0x01 CCUConn: 0x01 eSeq#: 0x19
UL AFNbis:1911862 DLAFNbis: 1911866
PDTCHoos21
Figure 3-28

Type 5b PDTCH Unavailable, Flood SWFM happens on BSP

How to identify thisa problem type:
Flood SWFMs generated on BSP.

Type 5b PDTCH Unavailable, Flood SWFM happens on

BSP
50b8 Nonfatal SWFM Error Routine: psm_messages.c

50b8 Area: 0x00008000 Error: 0x0000ffff PC: 0xc000427a PID: 0x40 (SM BSC)
50b8 BSS Release: 1.6.1.4.6 Obj Version: 1.6.1.4.6
50b8 02Feb2001 18:47:31.910 Subsystem: 0x01 CPU: 0x0115 Board: GPROC2
50b8
50b8 SM Error [0x17]: RCI timeslot has invalid index to rci_to_port
50b8 detected in file get_rci_conn_to_gci.c at line: 120
50b8 > timeslot_rci_in = 0x031b
50b8 SM Error [0xffff]: Error getting RCI connected to GCI
50b8 detected in file pcu_con_disc_req.c at line:451
50b8 > gds_channel_id = 0x15011302
50b8 SM Error: PCU Con Disc had a Failure.
50b8 detected at line:100
PDTCHoos22
Figure 3-29

Type 5c PDTCH unavailable, Flood SWFM happens on PRP

Whole GDS span OOS.
Flood SWFM generated on PRP board.

Type 5c PDTCH unavailable, Flood SWFM happens on

PRP
Identify
Whole GDS span OOS
Flood SWFM generated on PRP board
prm_build_send_ts_switch_on.c:Attempt to write switch on TS message (Cell:0x3c
Carrier:0x1 TS:0x6) failed!
status = 5
Data buffer index = 5, buffer id = 0
prm_build_send_ts_switch_on.c:Cell Index 20!_
Cell id: 60
picp_cpu_slot_id: 2
Slot_to_data_buffer:5
PDTCHoos23
Figure 3-30

Type 5d Individual PDTCH OOS: No UL Frame received on TSN

TSN logs show UL/DL AFNbis stuck
PRM shows TS status no service pend.

Type 5d Individual PDTCH OOS: No UL Frame received

on TSN
PCU:emon_1105 % msg_s 0d9h 9000h 0 0 7404 04 14 0 0 0 191
Carrier Info
Local Cell ID: 19
Local CR ID: 1
Local CR State: 1
Logging: FALSE
Max GPRS TS: 2
Res
TS Bitmap: 0xc0
CRM TS Bitmap: 0xc0
MA Update Rec flag: TRUE
PCU:emon_1105 % task spawned: id = 0x6544c00, name = t2
TS[0]: ULTFI Map:0xff 0xff UL PACCH: 0x00 DLTFI Map:0xff 0xff DL PACCH: 0x00 PICP ID:0xff State:INACTIVE
TS[6]: ULTFI Map:0xff 0xff UL PACCH: 0x00 DLTFI Map:0xff 0xff DL PACCH: 0x00 PICP ID:0x02 State:Non Service Pend
TS[7]: ULTFI Map:0xff 0xff UL PACCH: 0x00 DLTFI Map:0xff 0xffDL PACCH: 0x00 PICP ID:0x02 State:SERVICE
Asg Stat Cnt: 0 MS IdxTX: 00 NUM RSS Blks: 01
TS AFN MFrame # RelBlk # Blk Delay UL_CA DL_CA UL_ABN DL_ABN

00 0 0 00 00 00 00 0 0
01 0 0 00 00 00 00 0 0
02 0 0 00 00 00 00 0 0
03 0 0 00 00 00 00 0 0
04 0 0 00 00 00 00 0 0
05 0 0 00 00 00 00 0 0
06 1856278 35697 08 07 20 27 428372 428379

07 2699177 51907 03 07 39 46 622887 622894
TS Received: 0
Total TS Outstanding: 1
TS: 6 MS Index: 0x00 TAI Counter: 0x0d TAI Piece: 0x00000002
TS: 7 MS Index: 0x00 TAI Counter: 0x03 TAI Piece: 0x00000000
RSS Block Bitmap
TS[0] 0 0 0 0 0 0 0 0 0 0 0 0
TS[1] 0 0 0 0 0 0 0 0 0 0 0 0
TS[2] 0 0 0 0 0 0 0 0 0 0 0 0
TS[3] 0 0 0 0 0 0 0 0 0 0 0 0
TS[4] 0 0 0 0 0 0 0 0 0 0 0 0
TS[5] 0 0 0 0 0 0 0 0 0 0 0 0
TS[6] 0 0 0 0 0 0 0 0 0 0 0 0
TS[7] 0 1 0 0 0 0 0 0 0 0 0 0
[08/06/01 10:20:11] PCU: emon _1102 % msg_s 0dbh 9000h 0 0 0 4 0 5eh
Chan: 0x005e RTD: 0x06 CR: 0x01 TS: 0x06 Frame: 0x05
BUFFIDX: 0x00000002 TAL: 0x00 DR: 0x00SyncState:0xff
PRMConn: 0x01 SSI: 0x01 UFE: 0x00 MS#: 0x08 CUTA: 0x00
UlBlk#: 0x07 Seq Num: 0x0c UlBlkBM:0x00 DlBlkBM: 0x00#UlSync: 0x00
TTS: 0x22 eDLTACI: 0x01 CCUConn0x01 :0x01
eSeq#: 0x07
UL AFNbis:1856274 DL AFNbis:1956278
TAL Tot: 0x0000003c TAL Delay:0x0000341c
PDTCHoos24
Figure 3-31

Type 5e PD missed, comparing disp_cell_s and disp_rtf_chan

From PRM carrier info, PRM and CRM show different bitmap. (PRM is less than CRM) .
From PRM TS history, switch on timer expired.

Type 5e PD missed, comparing disp_cell_s and

disp_rtf_chan
PCU:emon_1104 % print_ts_history 1 1 5
STATE TRIGGER TIMER COUNT TIMESTAMP
INACTIVE Discon. Ack 0 69096

INACTIVE GPCS1 0 70385
Connection Pending Con Ack 7 71081
STANDBY Unsched 1 71104
Non Service Switch on Pend Timer Exp 1200 191104
TSN Detach for GPCS Pend Sw off Ack 0 191104
PSM Detach for TPCS Pend Discon. Ack 0 191172
*INACTIVE
PCU:emon_1104 % task spawned: id = 0x63da488, name = (null)
PCU:emon_1104 % print_ts_history 1 1 4

Non Service Switch on Pend Sw on ACK No Sync 0 73578
Non Service Pend Sync 24
*NON SERVICE

PCU: emon _1104 % task spawned: id = 0x63da488, name = (null)
PCU:emon _1104 % print_carrier_info 1 1

PDTCHoos25 Carrier Info
Local Cell ID: 1

Local CR ID: 1
Local CR State: 1
Logging: FALSE
Max GPRS TS: 7
Res GPRS TS: 0
TS Bitmap: 0xd4
CRM TS Bitmap: 0xfe
MA Update Rec flag: TRUE
task spawned: id = 0x63da488, name = t2
PCU: emon_1104 % TS[0]: ULTFI Map:0xff 0xff UL PACCH: 0x00 DLTFI Map: 0xff 0xff DL PACCH: 0x00 PICP ID:0xff State: INACTIVE
TS[1]: ULTFI Map:0xff 0xff UL PACCH: 0x00 DLTFI Map:0xff 0xf f DL PACCH: 0x00 PICP ID:0xff State:INACTIVE
TS[2]: ULTFI Map:0xff 0xff UL PACCH: 0x00 DLTFI Map:0xff 0xf f DL PACCH: 0x00 PICP ID:0x02 State:NON SERVICE
Asg Stat Cnt : 2 MS Idx /TS: 00 NUM RSS Blks : 04
TS AFN MFrame # RelBlk # Blk Delay UL_CA DL_CA UL_ABN DL_ABN

00 0 0 00 00 00 00 0 0
01 0 0 00 00 00 00 0 0
02 1165086 22405 06 07 66 73 268866 268873
03 0 0 00 00 00 00 0 0
04 1165086 22405 06 07 66 73 268866 268873
05 0 0 00 00 00 00 0 0
06 1165086 22405 06 07 66 73 268866 268873
07 1165086 22405 06 07 66 73 268866 268873
TS Received: 1
Total TS Outstanding: 4
TS: 7 MS Index: 0x00 TAI Counter: 0x0f TAI Piece: 0x00000005
RSS Block Bitmap

TS[0] 0 0 0 0 0 0 0 0 0 0 0 0
TS[1] 0 0 0 0 0 0 0 0 0 0 0 0
TS[2] 0 0 0 0 0 0 0 0 0 0 1 0
TS[3] 0 0 0 0 0 0 0 0 0 0 0 0
TS[4] 0 0 0 0 0 0 0 1 0 0 0 0
TS[5] 0 0 0 0 0 0 0 0 0 0 0 0
TS[6] 0 0 0 0 1 0 0 0 0 0 0 0
TS[7] 0 1 0 0 0 0 0 0 0 0 0 0
Figure 3-32


Chapter 4
Device Link Failure

Version 1 Rev 1

Version 1 Rev 1
Chapter 4
Device Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Device Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
PCU Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
General Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Alternative to PCU reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
NSVC Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
NSVC Status (Contd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
NSVC Block/Unblock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
BVCI Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
BVCI Status (Contd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
BVCI Blocking/Unblocking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
RLC/MAC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
GDS Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
GDS Investigation Timeslot Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
GBL Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
GBL Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

Version 1 Rev 1

Objectives
Be able to collect the correct data to report a fault relating to Device Link Failure
problems.

Device Link Failure Version 1 Rev 1
Device Link Failure
PCU Interfaces
The PCU will be interfaced by three different type of E1 link, each performing a different
function. They are:
The GPRS Data Stream (GDS), compromising:
The GDS Trau link, which is the data route between the PCU and the
BSC. It achieves connectivity using the BSC MMS and PCU MMS ports,
via E1 physical connections.
GDS Lapd is the Siganlling link between the BSC and the PCU. It is
possible to have a maximum of 6 GSLs (64kbps LAPD timeslots) on one
E1 Lapd connection, and a maximum of two LAPD connections on any
one GDS. A GSL is a child device on the MMS and should be equipped
onto the GDS LAPD.
The Gb Interface Link (GBL).
This is a configured number of timeslots on an E1 span between the PCU and the
SGSN.
There is one GBL per MMS, but the number of timeslots on each GBL is configurable.
Maximum of 4 GBLs per PCU.

Version 1 Rev 1 Device Link Failure
PCU Interfaces
PCU
GDS Trau GBL Signalling
Data Only and Data
GDS Lapd
Signalling Only
BSC SGSN
Figure 4-1

Data Collection
General Data Collection

The commands below allows a user to develop a basic benchmark when any problems
are experienced on the GBL.
To verify that the PCU and the SGSN parameter are matched
State pcu gbl <id>
Example:
MMIRAM 0119 > state pcu gbl 0
STATUS INFORMATION:
Device: GBL 0 0 0
Administration state: UNLOCKED
Operational state: BUSY
Reason code: NO REASON
Time of last transition: Wed Jun 5 14:44:31 2002
Related Device/Function: None
END OF STATUS REPORT
From PICP with the GBL. The following command will display the NSVC mapping.
msg_send 0d6h 9000h 42h 0 7801h 1 0
Example:
PCU:emon_1102 % msg_send 0d6h 9000h 42h 0 7801h 1 0
GBL Local NSVCI DLCI FD

0 0 33 18
The following command displays the state and the local NSVCI of all the equipped
NSVCs msg_s 0d2h 9000h 0 0 0 1 0ffh
iir_mod 0d7h 0fffffff8h

From the PICP with the active GBL, this filter will display all the
messages going over the NSLayer of the GbLink (SGSN <> PCU).
The iir_mod 0d7h 000000000h command maybe used to switch off the
filter listed above.
The following commands should be used to also gather improtant data.
GBM(MPROC) iir_mod 0d2h 7f8h
GB_DLSP (PICP DPROC with GBL) iir_mod 0d6h 3ch
Mproc msg_s 0d2h 9000h 0 0 offh 0ffh

PCU State
MMIRAM 0119 > state pcu gbl 0

STATUS INFORMATION:
Device: GBL 0 0 0
Administration state: UNLOCKED
Operational state: BUSY
Reason code: NO REASON
Time of last transition: Wed Jun 5 14:44:31 2002
Related Device/Function: None
END OF STATUS REPORT
NSVC Local ID
PCU:emon_1102 % msg_send 0d6h 9000h 42h 0 7801h 1 0
GBL Local NSVCI DLCI FD

0 0 33 18
Figure 4-2

Alternative to PCU reset

GBL_CONNECT_REQUEST, GBL <id>
msg_send 0d6h 11h 42h 0 7001h 1 59h 0
GBL_DISCONNECT_REQUEST, GBL <id>

msg_send 0d6h 11h 42h 5 7003h 3 59h 0
GBL_CONNECT_REQUEST, GBL <id>

msg_send 0d6h 11h 42h 0 7001h 1 59h 1
GBL_DISCONNECT_REQUEST, GBL <id>

msg_send 0d6h 11h 42h 5 7003h 3 59h 1

Data Collection
Gb Link Toggled
PCU
SGSN
Device Link Failure 2
Figure 4-3

NSVC Status
To verify the state of the NSVCI:
PCU:emon_1107% > msg_s 0d2h 9000h 0 0 0 1 X Y
0d2h: ProcessID (destination)
90000: mailbox of the process (destination)
0 source
0: source
0: tag1: messagetype
X,Y: content that defines the local NSVC identifier
X : maps to the respective interval of 255 i.e 0 to 0255 block, 1 to the 256 510 block and so on
Y : local NSVC identifier (NSVCI) range 0255
Hint:
msg_s 0d2h 9000h 0 0 0 1 0ffh
Displays the state and the local NSVCI of all the equipped NSVCs
The example opposite demonstrates how the outcome of this can be used to find out the
necessary mapping for the local NSVCs:

NSVC Status
Example
PCU:emon_1107 % msg__s 0d2h 9000h 0 0 0 1 0ffh

Local NSVCI 0, GSM NSVCI 4401 (0x1131),
NSVC state NSVC DEAD (S0)
Nsvc_alive 0, O&M Block 0N 0, Test_pending 0,
NSVC Connection retry in progress... tid = b1
Gbl_id 0, DLCI 780

Local NSVCI 318, GSM NSVCI 4402 (0x1132),
Nsvc_alive 0, O&M Block 0N 0, Test_pending 0,
NSVC Connection retry in progress... tid = b1
Gbl_id 1, DLCI 781

Figure 4-4

NSVC Status (Contd)

in respect of previously identified Local NSVC identifiers, the following commands can be
issued:
PCU:emon_1107 % msg_s 0d2h 9000h 0 0 0 1 0 0
PCU:emon_1107 % msg_s 0d2h 9000h 0 0 0 1 6 2

NSVC Status (Contd)
For the above local NSVC the relevant commands can then be given
PCU:emon_1107 % msg_s 0d2h 9000h 0 0 0 1 0 0
Local NSVCI 0, GSM NSVCI 65532 (0xfffc),

NSVC state NSVC UNBLOCKED (S4)
NSVCI flags: FECN 0, BECN 0, Test_pending 0, Nsvc_alive 1, O&M Block 0
NSVC Connection retry in progress... tid = 40000
Gbl_id 0, DLCI 19

PCU:emon_1107 % msg_s 0d2h 9000h 0 0 0 1 6 2
1
Local NSVCI 318 , GSM NSVCI 4402 (0x1132),
NSVCI flags: FECN 0, BECN 0, Test_pending 0,
Nsvc_alive 0, O&M Block 0
Gbl_id 1, DLCI 781
GBL 0 State: INS
Figure 4-5

NSVC Block/Unblock
To block an NSVC:
PCU:emon > msg_s 0d2h 9000h 0 0 0 06h X Y
The last 2 digits define the local NSVC identifier (in previous examples).
To unblock an NSVC
PCU:emon > msg_s 0d2h 9000h 0 0 0 07h X Y
The last 2 digits define the local NSVC identifier.

NSVC Block/Unblock
LLC
RELAY
RLC BSSGP BSSGP
Network services Network services

Frame relay Frame relay
MAC
LI L1
Gb
BSS SGSN
NSVCI
FRAME RELAY
BSS SGSN
NETWORK
DLCI DLCI
AT BSS SIDE AT SGSN SIDE
Figure 4-6

BVCI Status
Where Z corresponds to the local Cell Id (LCI)
In this message no BVCI is given, instead LCI.
The necessary mapping for the individual LCIs can be found with the disp_gsm *
command.

BVCI Status
PCU: emon > msg_s 0d2h 9000h 0 0 0 00h 0 0 0 Z

Where Z corresponds to the localCellId (LCI)
In this message no BVCI is given, instead LCI.
The necessary mapping for the individual LCIs can be found with the disp_gsm * command :
e.g.

MMIRAM _
0115 > disp_gsm 1
Associated GSM cells:
GSM CELL ID Freq
MCC MNC LAC CI LCI Type Cell Name

202 05 98 (0062h) 64631 (FC77h) 0 PGSM ATRINA TEST1

RAC : 98 (062h) BVCI : 64631 (FC77h)
202 05 98 (0062h) 64632 (FC78h) 1 DCS1800 ATRINA TEST2
RAC : 98 (062h) BVCI : 64632 (FC78h)
Number of Sectors : 2
Figure 4-7

BVCI Status (Contd)

Hint:
msg_s 0d2h 9000h 0 0 0 00h 0 0 0 0ffh
Displays the state of all the equipped BVCIs. Here 0ffh= all defined BVCIs

BVCI Status (Contd)
Hint:
msg_s 0d2h 9000h 0 0 0 00h 0 0 0 0ffh
Displays the state of all the equipped BVCIs. Here 0ffh=all defined BVCIs
Example:
PCU:emon_1107 % msg_s 0d2h 9000h 0 0 0 00h 0 0 0 0ffh
Cell id 0, Cell state BLOCKED:GPRS ENABLED (S1),
BVCI 64631,
BLK_cause: ff, RST_cause 9, Retries 0, Timer 0INS_OP 1, CB_code ff

BVCI 64632,

BVCI 64641,
Figure 4-8

BVCI Blocking/Unblocking
To block/deactivate a cell (BVC) enter the following command:
PCU:emon > msg_s 0d2h 01ch 0d0h 0 070f8h 0f8h 0e0h 0 0 0 X 77h <reason
code>
Where X is the Local cell ID
Reason code:
0 PRP locked
1 PRP failed
2 Cell congestion
3 O&M intervention
Suggestion: The reasoncode for the BVCBlock should be 2 , the BLOCK will be sent
out.
To unblock/activate a cell (BVC).
This command is used to send a BVCUnblock message

PCU:emon > msg_s 0d2h 01ch 0d0h 0 070f9h 0e0h 0 0 0 X 49h 1
Where X: Local cell ID

BVCI Blocking/Unblocking
GTP SGSN
MS STBY
4 RA NSE1
ip BSSGP PAGE 5
3 2 3, 4
4
3 NSE1 3 4
NSE1 0
3 4
0
20 30
200
24 24 200
15 300 301
BSS1 200 BSS2
30 20
NSE1 0 NSE1 0
3 4
4 3 5
BVCI 3 4
Page Page Page
RA2 RA3
Figure 4-9

RLC/MAC Commands
These messages can be sent from the PRP DPROCs (positions 3 and onwards of the
PCU).
That means, in order to see the RLC/MAC messages of the 1st PRP for example, it is
necessary to remotelogin to the processor in slot 3. In order to ascertain the RLC/MAC
activity upon this processor type:
msg_s 0d9h 9000h 0 0 7408 04 34 0ffh 0 0 0
(Observe that the TLLI is enabled for all TLLIs)
Remember to Disable the TLLI watch when finished:
msg_s 0d9h 9000h 0 0 7408 04 34 0

RLC/MAC Commands
rl 254 1103h
PCU
DPROC
BSC msg_s 0d9h 9000h 0 0 7408 04 34 0ffh 0 0 0
Slot 3
GPROC
Figure 4-10

GDS Investigation
First check if there is a mismatch of GDS E1 MMS between PCU and BSC
(LAPD & TRAU)
At the MMI prompt type:
state <PCU> GDS <ID>
disp_eq PCU GDS <ID>
state GDS MMS and MSI at BSC and PCU
Lock BSC MMS and PCU MMS should go DU
if not, there is a mismatch then it may be:
Loss of GDS link (TRAU Only)

disp_pr PCU
Identify associated GDS PICP and PRP
Run pb list on both boards
If any of the circled buffers opposite is full or not attached, a problem exists.
GSL Failure (LAPD Only)
The quickest way is to check for GSL or MMS alarms and investigate the alarm/s

GDS Investigation
Figure 4-11

GDS Investigation Timeslot Availability

Trau only. If you suspect a GDS as the reason for a Timeslot not being available, verify
the pSMSM mapping of the problem timeslot. To do this we will need information from a
number of scourses
1. First find the timeslot out of sync on the PICP:

msg 0dbh 9000h 0 0 0 2
msg 0dbh 9000h 0 0 0 44
msg 0dbh 9000h 0 0 0 45
An example of the output from these commands would be:
**CN:0x12f Cell:28 CR:0 TS:6 PmcIdx:2
2. Then from the SM at the BSP:

msg 64 3 99 99 0f0ch 6 <cell> <car> 1 <ts>
So for the example msg 64 3 99 99 0f0ch 6 28h 0 1 6 we may expect an output of:
GCI (MMS ID 0, MMS ID 1, MMS TS, MMS Group #) : 18 0 20 3
3 And finally we will check on the pSM at the MPROC:

msg 40h 9000h 0 0 0 3 0 0 0 <Local cell ID>
So for the following example:
msg 40h 9000h 0 0 0 3 0 0 0 28h
we might expect to see the following output:
Debug output 10 0 20 3 0028h 0 6 in use
4. You should now match the MMS at pSM, SM and GDS disp_eq
information.

Timeslot Availability
1. Find timeslot out of sync on PICP.
CN:0x12f Cell:28 CR:0 TS:6 PmcIdx:2
2. Check the mapping of Timeslots at SM.

GCI (MMS ID 0, MMS ID 1, MMS TS, MMS Group # : 18 0 20 3
3. Check the mapping of Timeslots at the pSM.

Debug output 10 0 20 3 0028h 0 6 in use
4. Match mappings at pSM, SM and GDS disp_eq information.

GBL Investigation
State PCU GBL <ID>
Disp_nsvc gbl <ID>
NSVC Investigation (NS Messaging PCU SGSN)
filter start_new tag 7601h
filter start_new tag 760ch
BVCI/Cell investigation (BSSGP Messaging PCU SGSN )
filter start_new tag 7701h
filter start_new tag 770bh

GBL Investigation
Figure 4-12
Figure 4-13

GBL Investigation
To instigate an investigation of the communication upon the GBL type:
iir_mod 0d6h 03ch

which will show the GBL establishment and errors from the GB_dlsp.
iir_mod 0d7h 0f8h

Which will show all Downlink messages entering the PCU at GR.
iir_mod 0d3h 0fch

Which will show all Uplink messages leaving the PCU at GTM.

GBL Investigation
GBL Establishment and Errors
gb_dlsp_process_gbl_connect_req.c: GBL TS Config: 7fffffff

gb_dlsp_process_gbl_connect_req.c: GBL 0 being connected
gb_dlsp_process_gbl_connect_req.c: GBL 0 connect delay TID 1128530934
Uplink and Downlink Messages into and out of a PCU
NS_RESET_ACK PDU received on GSM NSVCI 0x13

NS_UNBLOCK_ACK PDU received on GSM NSVCI 0x13
BVC_RESET_ACK PDU received for BVCI: 0
Figure 4-14


Chapter 5
Throughput

Version 1 Rev 1

Version 1 Rev 1
Chapter 5
Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Throughput Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Ping Delay & Latency Investigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
GBL Average Throughput Analysis (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516

Version 1 Rev 1

Objectives

Collect the correct data to report a fault relating to Throughput problems.

Objectives Version 1 Rev 1
Throughput Performance
From the graph shown opposite, in can quite clearly be seen that at Carrier to
Interference ratio of 7db and higher, Coding Scheme 3 will produce a larger throughput.
Coding Scheme 4 will produce advantages at 12db C/I and higher. Levels less than this
level have not yet been tested fully.

Performance
CS3 and CS4 Motorola Radio Leadership

20
1 TS No FH
18
16
Throughput (kbps)
14
12
10
8
CS1
6
CS2
4
CS3
Speech level
1 planning today CS4
0
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
C/I
Throughput 3
Figure 5-1

Analysis
SYSTEM & TOOL FAMILIARIZATION
Refer to the GPRS BSS Support page (CS_WEB) for PCU general design and data
collection information
GPRS BSS Support web page >
http://www.cig.mot.com/Organization/GSM/CS/cs_web/
The Throughput section of CS_WEB contains all available information for throughput
investigation.
Design Information TBF Operation, E2E GPRS Signaling, Flow Control, Coding
Scheme, Supercoattail.
VERIFICATION OF SYSTEM CONFIGURATION
Refer to recommended performance Configuration Worksheet.
Complete the performance testing Configuration Worksheet.
BENCHMARKING (No logs)
Run 10 FTP transfers depending on Multislot class of mobile available, i.e. 2TS Down =
100Kbyte, 3TS 400Kbyte and 4TS 1Mbyte.
Run 10 UDP transfers (400bytes)
Run 100 pings (10bytes & 500bytes)
Compare results with AH performance from throughput section of CS_WEB.

Analysis
Parameter Parameter NPI lab Swindon Perf

SITG AH DevelopmentGPRS AH Customer Comments
Ratings System System AH Performance Settings
Load GSN
BSS
OMC Mandatory
BSS max_gprs_pdch 3 4 2 6 4 6
res_gprs_pdch 3 0 2 0 0
gprs_intraho_allwd 2 1 1 1 1 1
gprs_reconfig_thresh_idle_tch 2 1 1 1 1
protect_last_ts 2 0 0 0 1 0
bssgp_flow_control 1 2 2 2 2 2
bssgp_scheduling 1 0 0 0 0 0
bssgp_fc_period_c 1 10 100 10 10 10
max_ms_dl_buffer 1 3000 3000 3000 3000 12000
max_ms_dl_rate 1 80000 80000 80000 80000 900
ns_commit_info_rate 2 384000 512000 1984 64 1984
ns_burst_size 2 384000 512000 1984 64 1984
ns_burst_excess 2 384000 512000 1984 0 0
gprs_mac_mode 1 1 0 0 1 0
gprs_bs_cv_max 1 6 6 6 6 6
gprs_t3168 2 4000 4000 4000 2000 4000
gprs_smg30_t3192 2 500 500 500 500 500
gprs_t3192 2 500 500 500 200 200
gprs_ms_pan_dec 2 1 1 1 1 1
Figure 5-2

Investigation Version 1 Rev 1
Investigation
INVESTIGATION
Please complete the performance Investigation Worksheet.
LEVEL 1 MS only.
Coding Scheme Utilization.
RF Environment Investigation.
Radio Investigation.
PC Client & Server Investigation.
TBF Connection.

Version 1 Rev 1 Investigation
Investigation Level 1
Level 1 Investigation MS Only
Coding Scheme Utilization Comments
Does transfer session use CS 1 permanently? Describe CS activity from the MS EFEM mode:
YES/NO UL DL
RF Environment Investigation Comments
RxLev Ave Value UL DL
RxQual Ave Value UL DL
BLER Max/Min UL DL Comments (Mandatory)
Radio Investigation Comments
If hopping, disable hopping. Does problem persist?
YES/NO UL DL
Swap radio Does problem persist? Comments
YES/NO UL DL
Verify problem on multiple platforms
DRCU YES/NO UL DL
TCU A YES/NO UL DL
TCU B YES/NO UL DL
CTU YES/NO UL DL
PC Client & Server Investigation Comments
Verify problem on multiple mobiles
List all mobiles including release for Motorola mobiles
MS brands:
Verify problem on multiple PCs; WIN NT, 98, & 2000
PC (w/OS) brands:
Verify problem on multiple servers
Any difference in performance?
YES/NO UL DL
TBF Connection Comments
Does MS alternate between PDCH and
BCCH during data transfer?
YES/NO UL DL
Do you see multiple RLC retransmissions?
YES/NO UL DL
Check for cell reselections (enable the reselect beep on the ms)
Throughput 4
Figure 5-3

Investigation Version 1 Rev 1
LEVEL 2 MS, PCU & Tools.
RF Environment Investigation (Uplink BLER, RxLev, RxQual, C/I).
TBF Investigation (TBF alloc, TLLI watch & MDTT).
Flow Control Investigation (From FBM flow control).

Version 1 Rev 1 Investigation
Investigation Level 2
Level 2 Investigation MS, PCU, & Tools Logs required

See the attached for appropriate IIRs and Message sends for the investigations below
RF Environment Investigation (Uplink BLER, RxLev, RxQual, C/I)
RxLev Max/Min/Ave UL
RxQual Max/Min/Ave UL
BLER Max/Min/Ave UL
C/I Max/Min/Ave UL
TBF Investigation (TBF alloc, TLLI watch & MDTT)
See TBF operation in Throughput section of GPRS BSS Support web page
Continuous Missed Messages? (From MDTT & PRP logs) Comments (Mandatory)
Seen at PRP YES/NO UL DL
Message/s:
Seen at MDTT YES/NO UL DL
Message/s:
Retransmissions? (From MDTT & PRP logs) Comments (Mandatory)
Seen at PRP YES/NO
Message/s:
Seen at MDTT YES/NO
Message/s:
Abnormal TBFs? (From PRP) See causes on CS_WEB Comments (Mandatory)
of each abnormal TBF. YES/NO UL DL
Reason:
Flow Control Investigation (From FBM flow control)
See flow control operation in Throughput section of GPRS BSS Support web page
Provide CBL, Comments (Mandatory)
CBL Max/Min/Ave
Bmax (constant from cell PD) Value
Cell PDs equipped (SW & RES)
R Max/Min/Ave
Is = flow control activated? (From PRP logs)
YES/NO
Verify LLC transmission for cell (From PICP logs) Comments (Mandatory)
Any LLC frames for the cell (bvc)?
YES/NO UL DL
Any LLC retransmissions (From GB logs)
YES/NO UL DL
Throughput 5
Figure 5-4

Data Collection
Mandatory Handover requirements completed configuration & investigation
worksheets with all the required logs!
Direct connect to PRP and PICP boards for data collection.
Enable time_stamp on for all logs.
Log the setting of all iirs and msg_sends.
Comments on PRP and PICP logs.
General Info (mmi_log.txt.)
state 0
state pcu
state <site>
disp_cell_status <site>
disp_gsm_cell <site>
disp_cell <cell ID> FULL
disp_equip <site> <RTF ID1> <RTF ID2> (For RTF w/ PDTCHs)
disp_equip <site> <DRI ID1> <DRI ID2> full (For RTF w/PDTCHs)
disp_pr pcu
disp_pr 0
disp_pr <site>
disp_act_alarm pcu
disp_act_alarm 0
disp_act_alarm <site>

Data Collection
Ensure Investigation and Configuration

Worksheets are complete.
Observe best practices.
Collect data from:
BSC GPROC (Customer MMI)

PICP
PRP
MDTT logs
Radcom/K1205 Logs
Gb Log
Figure 5-5

Ping Delay & Latency Investigation Version 1 Rev 1
Ping Delay & Latency Investigation
Collect the following data:

PRP Logs (prp_log.txt)
Enable TLLI Watch msg_s 0d9h 9000h 0 0 7404 4 34 1 <tlli_byte3>

<tlli_byte2> <tlli_byte1> <tlli_byte0>
Enable TBF Allocation iir_m 0d9h 0c0000000h
Enable iir_mod 0dch 4000h
Enable iir_mod 0ddh 4000000h
Enable iir_mod 0d5h 0f320h to watch FBM Flow Control
PICP Logs (picp_log.txt)
Enable iir_mod 0d7h 0f8h for GTM uplink LLC frames
Enable iir_mod 0d3h 0fch for GR downlink LLC frames
MDTT Logs (mdtt_log.txt)
FTP, UDP & Ping Results (xxx_result.txt)
SWFMs (swfm_log.txt)
swfm l a then swfm d a from the all DPROC(PRP/PICP), MPROC,

BSP, LCF controlling site, BTP, DHP/TCU controlling the GPRS
PDTCHs.
Events (event_log.txt)
Event logs from 3 hours prior

Version 1 Rev 1 Ping Delay & Latency Investigation
Ping Delay & Latency Investigation
PROCESS EXPECTED REMARKS

DELAY ms
RACH IA 35 Check from MDTT
IA PRR 90 Check from MDTT and PRP logs.
PRR PUA 160 Check from MDTT and PRP logs.
PUA UL Data 80 Check from PRP logs and from MDTT.
UL Data PDA 230 Check from MS/MDTT/PCIP logs. This also includes GB delay.
PDA DL Data 100 Check from PRP logs and MDTT.
Figure 5-6

Flow Control Version 1 Rev 1
Flow Control
FBM implements leakybucket flow control algorithm. Based upon the air throughput for
a particular cell, a cell bucket is defined with various thresholds. When data comes into
FBM for a cell, the bucket for that cell starts to fill up. Similarly, when the data leaves the
buffer the bucket starts to empty out. FBMs responsibility is to send flow control
messages to the SGSN whenever necessary so as to ensure efficient bucket usage of
the cell. FBM monitors each active cells bucket against different thresholds. A cells state
is also tied to the current bucket level.
Factors that effect the buffer
1. Data input via PCI buffer from GR (increase)

2. BSSGP PDU discard caused by lifetime expiration (decrease)
3. BSSGP PDU discard caused by a flush_pdu from GR (decrease)
4. Data output via data_enqueued_notification (decrease) or Data output
via next_block_ack (decrease)
CBL: Current buffer level for cell in bytes. So here, the CBL is 9.2k
BMAX: Current max buffer level for cell. This is calculated based on the number of
timeslots in the cell and is roughly 30k per timeslot. This is calculated once and will not
change.
R: This is the leak rate. This is in 100kbps. So the leak rate here is 35.7kbps.
prm_rate: PRM does its own leak rate calculation. FBM uses this rate when there is no
data, but when there is data available, it uses the adaptive rate algorithm to calculate the
rate. The rate that is reported to the SGSN in the BVC flow control message is the rate
that FBM calculates in R: or rate_to_be_reported
Example PCU LOG:
iir_m 0d5h 0f320h
This log is UDP streaming at 60kbps.
42170181 CELL 3 CBL: 9198 BMAX: 130000 R: 357 decr
42170181 CELL 3 prm rate: 416 rate_to_be_reported: 352 fbm rate: 352
CBL: Current buffer level for cell in bytes.
So here, the CBL is 9.2K;
Bmax: Current max buffer level for cell;
R: This is the leak rate. This is in 100kbps. So the leak rate here is 35.7kbps;
prm_rate: PRM does its own leak rate calculation. FBM uses this rate when there is no
data, otherwise R is used.

Version 1 Rev 1 Flow Control
Flow Control
180000 600
160000
500
140000
120000 400
Buffer Level
Leak Rate
100000
300
80000 Current Buffer Level
Bmax
Leak Rate
60000 200
Reported Leak Rate to SGSN
Reported Bmax to SGSN
40000
100
20000
0
84
167
250
333
416
499
582
665
748
831
914
997
1080
1246
1329
1412
1495
1578
1661
1744
1827
1910
1993
2076
2159
2242
2325
2408
2491
2574
2667
2740
2823
2906
2969
1163
Throughput 6
Figure 5-7

GBL Average Throughput Analysis (PCU)

By collecting the following data, GBL data from GR and GTM you can then put this
information into a graphical representation.
iir_mod 0d7h 0f8h & iir_mod 0d3h 0fch
62001953ms : UL_UNITDATA PDU sent. BVCI 3751, PDU len: 1611, TLLI:0xc00047a8,
PRP: 0x1104
62002095ms: DL_UNITDATA PDU received. BVCI 3751, LLC len: 50, TLLI: 0xc00047a8
62002123ms : UL_UNITDATA PDU sent. BVCI 703, PDU len: 1611, TLLI: 0xc00047dc,
PRP: 0x1104
62002221ms: DL_UNITDATA PDU received. BVCI 703, LLC len: 204, TLLI: 0xc00047dc
ms time reference; UL_UNIDATA PDU uplink GTM packet data unit; DL_UNIDATA PDU
uplink GR packet data unit; BVCI local cell ID; len current data sent for user on the cell;
TLLI mobile subscriber identifier; PRP dproc identifier hosting the PRM managing the
cell.
The data is imported to excel and sorted with DL_UNIDATA to plot average DL GBL
throughput from PCU.

Version 1 Rev 1 Flow Control
GBL Average Throughput Analysis (PCU)
600000
500000
400000
300000
200000
100000
0
0 50000 100000 150000 200000 250000 300000
Series1
Throughput graph2
N.B. The X axis represents ms and the Y axis represents Bytes.
Figure 5-8


Chapter 6
Attach

Version 1 Rev 1

Version 1 Rev 1
Chapter 6
Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
GPRS Attach Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
General Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
General Data Collection (contd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Version 1 Rev 1

Objectives
Be able to collect the correct data to report a fault relating to GPRS Attach
problems.

GPRS Attach Failure Version 1 Rev 1
GPRS Attach Failure

Currently there are three known types of attach failure.
AFN problem
TSN and the CCU in the radio on the cell are not in synchronization for the AFN.
From PRM carrier information:
msg_s 0d9h 9000h 0 0 7404h 4 14 00 00 00 <local cell id> <carrier id>
you will see bad Absolute Frame Number, AFN, and/or corrupt Round Trip Delay, Blk
Delay, value. Main symptoms include TS stuck in a working state and statistic
air_dl_data_blks pegging in a lot of stats periods but with no ul data.
Eg:
TS AFN MFrame# RelBlk# Blk Delay UL_CA DL_CA UL_ABN DL_ABN

03 16777216 16777216 00 00 00 00 16777216 16777216
04 1296195 24926 10 08 82 90 299122 299130
05 296195 24926 10 16777209 82 89 299122 299129
06 1296195 24926 10 08 82 90 299122 299130
07 577161 11098 10 07 82 89 90226 90233
No PRP data
PRM and RSS at the cell are not reporting the same information. From PRP TLLI msg_s
watch and TBF allocation iir_mod you will not see any data triggered for the MS in the
problem cell. For this problem to be diagnosed correctly you will have to know that a valid
attach request is being attempted in the cell. MDTT logs, PRM carrier information, and
RSS iir_mod are required.
For example:
Immediate Assignment message:

CHANGE_MARK_1:2
System Information Type 13 message:
SI13_CHANGE_MARK:0.
No DL data seen at the PRP

Flow Buffer Manager, FBM, is not functioning correctly. Either it is full or is dead.From
TLLI watch on the PRP you will not see any DL message flow only DL
requests.Depending on whether one cell or multiple cells are affected to which part of
FBM has failed. Check the swfms on the PICP.
2bbc Nonfatal SWFM Error Routine: gr_build_send_pb_write_msg.c

2bbc Area: 0x00000000 Error: 0x00000000 PC: 0x010f056c PID: 0xd7 (GR)
2bbc BSS Release: 1.0.0.0.0 Obj Version: 1.0.0.0.0
2bbc 05Apr2002 10:30:21.764 Subsystem: 0xfe CPU: 0x1102 Board: DPROC
2bbc ERROR: Discarding data for BVCI 0x143e since FBM buffer BUF1104001 on
PRP 0x1104 is full.
2bbc

Version 1 Rev 1 GPRS Attach Failure
GPRS Attach
Type 1: AFN Problem
Type 2: No PRP Data
Type 3: No DL seen on PRP
Diagran Number
Figure 6-1


Included in the attach data collection procedure is a general procedure to be followed if
none of the above types are identified first. It includes:
A set of questions to be answered by following the collection procedure.
General system information including display commands, state commands, event
commands and database commands.
PICP log: GTM and Gr data.
PRP log: TBF allocation, TLLI watch, carrier info, FBM info.
SWFMs from all DPROCs and the MPROC.
CP log at the BTP including Carrier config detailed display, Carrier config manager
display, and Channel resource linked list .
Statistics.

/#-.'+*-.+ #*-1#,#"*"-0#"- .2.

'*.&#-..!&)#*."',#!.+,3
-.&#,#".-##*..&#
-.&#,#".-##*..&#,
-.&#,#".-##*+*.&# ((+!.'+*
-.&#,#".-##*+*.&# ((+!.'+*
&.'--##*..&#'$0'(

&.'--##*/-'*% '$0'(
..-'-.&#,#*3.&'*%/*/-/(#%

_

Figure 6-2

General Data Collection (contd)

System Information
Collect SWFMs (swfm l a then swfm d a) at the following boards:
PRP
PICPs
MPROC
LCF controlling site
DHP / TCU controlling PDTCHs
BSP
BTP
State Commands:
state 0 state pcu state <site>
Display Commands
disp_pr pcu
disp_act_alarm pcu
disp_pr 0
disp_act_alarm 0
disp_cell <cell ID> full
disp_pr <site>
Save the above as: ALARM_STATE.txt
BSC Events 3 hrs prior to when the attach problem was reported.
Save as: <DATE>_Events.txt
Database (in ASCII format)
Save as: <BSCNAME>_Database.txt

System Information
SWFM Collection
Display Commands
BSC Events
Database
Diagran Number
Figure 6-3

PICP Log
A GB log with the following IIRs turned on at the GB PICP will show if data is getting to
the PRP.
disp_pr pcu (to find Gb DPROC, then set the following iirs at the DPROC controlling the
GBL)
1102 DPROC (PICP) 2 0 BU NO REASON MSI 1 0 N/A

GBL 0 0 N/A
GBL 1 0 N/A
iir_mod 0d3h 0fch (GTM)

51380112ms : UL_UNITDATA PDU sent. BVCI 718, PDU len: 1611, TLLI:
0xc0004056, PRP: 0x1103
51432150ms : UL_UNITDATA PDU sent. BVCI 718, PDU len: 1611, TLLI:
0xc0004056, PRP: 0x1103
iir_mod 0d7h 0f8h (GR)
FLOW_CONTROL_BVC_ACK PDU received on BVCI 718
51496889ms: DL_UNITDATA PDU received. BVCI 718, LLC len: 506, TLLI:
0xc0004056
51496890ms: DL_UNITDATA PDU received. BVCI 718, LLC len: 241, TLLI:
0xc0004056
iir_d
iir_dis: iir_mask for process 0xd3 is 0x000000fc.
iir_dis: iir_mask for process 0xd7 is 0x000000f8.
Save as: <DATE>_PICP.txt

PICP Log
(GTM) (GR)
iir_mod 0d3h 0fch iir_mod 0d7h 0f8h
513801 12ms : UL_UNITDATA PDU sent. BVCI 718, PDU len: 1611, TLLI: 0xc0004056, PRP: 0x1103 FLOW_CONTROL_BVC_ACK PDU received on BVCI 718
51496889ms: DL_UNITDATA PDU received. BVCI 718, LLC len: 506, TLLI: 0xc00
51496890ms: DL_UNITDATA PDU received. BVCI 718, LLC len: 241, TLLI: 0xc00
51432150ms : UL_UNITDATA PDU sent. BVCI 718, PDU len: 1611, TLLI: 0xc0004056, PRP: 0x1103
Figure 6-4

PRP LOG
A PRP log with the following information will show if UL and DL data is seen at the PRP.
Determine the PRP controlling the cell.
disp_gsm_cell <site> (at MMI)

Primary Secondary RAC/
MCC MNC LAC CI LCI Freq Type Freq Type BVCI
001 01 9 (0009h) 11 (000Bh) 2 PGSM N/A 1 (0001h)
msg_s 208 09000h 0 0 0 9 (at the MPROC)
CB CELL TO PRP MAP:
CPU ID Local Cell Id
0x1103 0x2 0x3 0x4 0x5 0x6 0x7
PRP IIRs: (make sure youve got the baud rate high enough (57600), and collect the
following from a direct connection to the PCU console port rather than an rlogin from the
BSC.
iir_m 0d9h 0c0000000h (TBF Allocation)
53188728 :TLLI c0004056 DL tfi=20 normal_tbf_release at ulabn=580024
stats(413 2634 390 1189 4626)
55040499 TLLI c0004059 UL tfi=29 normal_tbf_release at ulabn=45926 stats(1 1
1)
iir_d
iir_dis: iir_mask for process 0xd9 is 0xc0000000.
msg 0d9h 9000h 0 0 7404 4 34 0ffh 0 0 0 0 (TLLI Watch)
Sending TLLI c0004059 TFI: 13 PTR( 7) on (4,2,7) at abn = 45913, curr_dl_abn
45913 or 55040079 ms, rrbp = 3
TLLI c0004059 DL tfi = 13 starting on (4,2,5) at 45925
TLLI c0004059 UL tfi = 29 starting on (4,2,6) at 45919
msg_s 0d9h 9000h 0 0 7404 4 34 0 (Disables TLLI watch)

PRP LOG

!!

Figure 6-5

PRP Log (Cont.)

PRP message sends:
msg_s 0d9h 9000h 0 0 7404 04 15 0 0 0 <local cell id>

(Cell info in PRM Both old and new cell)
Cell Info
LCID: 3
LCIdx: 1
St: 2
BCCHCrID: 1
msg_s 0d9h 9000h 0 0 7404 04 14 0 0 0 <local cell id> <local carrier id>
(Carrier info in PRM you can get the carrier ID from the pervious msg send for
cell info)
Carrier Info
Local Cell ID: 3
Local CR ID: 1
Local CR State: 1
msg_send 0d5h 9000h 0 0 0f0h <local cell id>
(Internal cell structure of FBM for the cell)
Cell State: [2]
B: [0] Absolute Bmax: [156000] Bmax (Hi): [120000] Bmax (Pseudo): [1000] R:
[384] Rate to be reported: [384] FBM adaptive rate: [0] Rate
Info Counter: [0] Data in buffer w/o initial fcack?: [0]
FC ACK (resend_counter): [0] Flag (ready): [0] Tag: [30] (timerId): [0]
Save as: <DATE>_PRP.txt

PRP Log (contd)

Figure 6-6

CP Log
Inject the following at the BTP of the site with the problem.

(Carrier Config Manager Detailed Display Request)
Number SDcapable carriers going INS = 0h
Number SDcapable carriers going OOS = 0h
Number timeslots going OOS = 0h Number SD timeslots going INS = 0h
(Channel Resource View Linked List Info Request)
msg_send 34 9000h 0 0 0 0bbh 0f0h <local cell id>
(Carrier Config Manager Display Request (for cell
CRM: CR CONFIG MGR DATA for all carriers in cell 3h:
CRM: CR CONFIG MGR DATA for carrier 1h:
Carrier State = 3h INS
Cell ID = 3h
SDCCH Placement Priority = 0h
Max SDCCH Placement Load = 1
Actual SD Load = 1
Save as: <DATE>_CRM.txt

CP Log
BTS msg_send 34 9000h 0 0 0 0b3h 0f0h <local cell id>
Diagran Number
Figure 6-7

Statistics
Capture the following statistics for the problem cell:
gprs_access_per_rach
gprs_access_per_pch
gprs_access_per_agch
gprs_reqs_rec
gprs_reqs_reject
air_ul_data
air_dl_data
If you see any abnormalities with these statistics, determine the first stat interval where
the problem started and also provide OMC event logs covering this interval

Chapter 7
GTSS Global Virtual Customer
Support

Version 1 Rev 1

Version 1 Rev 1
Chapter 7
GTSS Global Virtual Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
GTSS Global Virtual Customer Support (GVCS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Version 1 Rev 1

Version 1 Rev 1 GTSS Global Virtual Customer Support (GVCS).
GTSS Global Virtual Customer Support (GVCS).

GTSS Global Virtual Customer Support (GVCS). Version 1 Rev 1
GTSS Global Virtual Customer Support (GVCS).

We would like to draw your attention to the following URL
http://compass.mot.com/go/GVCS
This is our One Stop Shop for all the latest field support issues.
This site has a Common Structure and feel for PCU, BSS, GSN, OMRr, OMCg, EMEA
and APAC CNRC.

Title Page
Diagran Number
Figure 7-1

Uses compass for tracking and searching capabilities.

Check each platform regularly for data collection updates.
Note version numbers of data collection procedures.
Submit Documents for additions to the web page you think other LOs could benefit from
(using compass add_doc).
Submit procedures via GVCS data input page.
Directly linked to the subject matter of the toolbag course.
The Global Virtual Customer Support web page is designed to bring together Motorola
groups that deal with customer service requests. These web pages will include
information on current customer issues, general information about the Motorola systems
each group works with, and a list of other resources that each group finds useful in their
daily work.

PCU
Procedure to Add or Data input page
Request Data
Diagran Number
Figure 7-2


GSN
Diagran Number
Figure 7-3


OMCG
Diagran Number
Figure 7-4


OMCR
Diagran Number
Figure 7-5


APAC/EMEA CNRC
Diagran Number
Figure 7-6


BSS 2G
Diagran Number
Figure 7-7

NOTE:
If you take nothing else away from this course, please take note of the information
opposite.

Link to CS Website
http://compass.mot.com/go/GVCS


Chapter 8
Annex A

Version 1 Rev 1

Version 1 Rev 1
Chapter 8
Annex A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Annex A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Version 1 Rev 1 Annex A
Annex A
GPRS Cell OOS Data collection procedure
(For 1620 only)
(Modified at 5/9/02 by Allen Yu)
Background: After customer upgrade to 1620.e6, most known type case in 1614 load will
be fixed, also as some debug command also changed in 1620 load. This document is
intended to allow onsite engineer to identify the existing problem in 1620 and also for
further data collection for problems that do not known the root cause. The use of this
document is for customer who have a 1620 or later load.
Warning: This document has not undergone any formal inspection. Use this with extreme
caution on a live network and ensure you fully understand each command. As the
procedure may update continually, we would suggest you check the document for the
latest version at: http://www.cig.mot.com/Organization/GSM/CS/cs_web/
If you have any problems with this procedure, mail cs_gprslist@majordomo.cig.mot.com
Known PR
157699 GPRS barred when toggle from 16k to 32k on secondary RTF path, fixed in
1620.e7
158876 Toggling to 32K trau failed after a path switchover, fixed in 1620.e7
159039 cell id and carrier id not initialized in psm_switch_disc.c, fixed in 1620.e7
159659 Pds keep bouncing in and out of sync on Incell with 32k TRAU, fixed in 1620.e7
159755 GPRS barred after equiping sub equiped RTF w/ associated RSL, fixed in
1620.e7
159908 Lock/unlock of pchn causes mismatch in disp_cell_s on 32k Incell, fixed in
1620.e7
157570 PDCH status at TSN does not change from INS to OOS even site is lock,fixed
in 1620.e8
160600 PDs oos after lock of primary path, fixed in 1620.e9
160689 Use of MateChan() causes TSN bus fault in 16K only, fixed in 1620.e8.
160999 Toggeling 32k trau on 16k associated RSL causes PD OOS, fixed in 1620.e9
155174 buffer descriptor corruption that faults Cp, outstanding
157902 2773 GPRS Status barred after reinstating rtf on freed dri, raised on 1620.e3,
outstanding.
159604 PD goes oos with 32k TRAU on Incell, raised on 1620.e5, monitor.
159782 PDs oos after changeing RTF frequency, raised on 1620.e5, outstanding
161060 2773Voice on same carrier as data causes PD to lose sync momentarily
For untyped GPRS CELL/PD OOS issue on 1620, please refer to Appendix A for data
collection. For the known type issue, please follow the specific type data collection
procedures. Before start all following data collection, please enable time stamp, so it is
easier to correlate all logs together.
Type 3b
Description
Entire GDS SPAN OOS, all PDs on this GDS out of sync, PMC buffer is fully used
When the problem happens, on PRP, from pb list, it is found the host2nib buffer is fully
used, typically logs as following:

4000000a yes HOST2NIB1 00001a00 12 23040 23040 23040
Related PR
PR 143939 LAPD and TRAU NIB getting crashed fixed on 1614.b1 & 1620.d5.

Annex A Version 1 Rev 1
PR 150321 PD1080: Span of PDs OOSync due to pci buffer problem fixed in 1620.e1.
PR 159569 HOST2NIB buffer full due to PCI buffer problem fixed in 1620.e6.
Data collection procedure
1. First find a GDS that is completely OOS, by entering the following
commands at the PICPs (Do this at every PICP).
msg_s 0dbh 9000h 0 0 0 44 (Shows timeslots OOS)
msg_s 0dbh 9000h 0 0 0 45 (Shows timeslots INS)
msg_s 0dbh 9000h 0 0 0 2 (Tells you which slot the given PMC index is in, DPROC ID
for #2 below)
2. From disp_pr pcu, running following command on all DPROC:
pb list
swfm l a
swfm d a
3. Using Appendix C for NIB debug information collection.
Workaround
Reset DPROC.
Type 3c
Description
Entire GDS SPAN OOS, buffer between PRP and PICP is not properly attached
When the problem happens, run pb list on both PICP and PRP. From the output, we
can see some buffers are no attached on read or write ID list. The buffer name could be
HOST2NIB, GTM, buffy or pmc2tsn, you may not see any buffer name in some case.
Related PR
155174 buffer descriptor corruption that faults CP wait commitment.
1. First find a GDS that is completely OOS, by entering the following

commands at all PICPs.
msg_send 0dbh 09000h 0 0 0 10 (Toggle rlogin/no session)
msg_s 0dbh 9000h 0 0 0 2 (shows PMC index in which slot)

pb list
3. Dump all SWFMs of all DPROC of PCU (swfm l a; swfm d a)
4. Follow PCI buffer debug command on Appendix B.
Workaround
Reset DPROC.
Type 4a
Description
Individual PDTCH OOS, PD configuration stuck in CRM
The identification of these problems mostly focuses on BTS side. When the problem
happens, from disp_cell_s we can find individual PDCH are OOS or missed. From:
msg_s 34 9000h 0 0 0 0b3h 0f0h <local cell id> (CRM cell info)

(CRM carrier info)

Most time we can see TS stuck on C8, but in some cases, there is no TS stuck on C8.
But from CRM cell info, we can also found Cell Activate Rcvd =TURE & Ma Update
sent: FALSE, Cr Status Delay Flag = Ture. These tell us by some reason when CRM
receive Cell activate message, it is stuck somewhere and can not move forward.
Note: A helpful GPRS channel reconfiguration diagram at

http://www.cig.mot.com/Organization/GSM/rss/Helpfull_info/timeslot_reconfig.html (Need
AH access)
Related PR
PR 145151 PD configuration stuck in CRM (cleared as lacking of data)

N/A
Workaround
Reset BTS.
Type 4d
Description
From disp_cell_s PD is missed. From CRM info, GetSDforPDTCH in progress is
TRUE
From output of
msg_s 34 9000h 0 0 0 0b3h 0f0h <local cell id> (CRM info)
GetSDforPDTCH in progress = TRUE.
From output of
msg_send 34 9000h 0 0 0 0b9h 0f0h <local cell id> (carrier info)
all TS was configured properly.
Date Collection procedure

1. From the MMI, run
disp_rtf_chan <site> <rtf id 1> <rtf id 2> (for each RTF)
Note: If the timeslots are OOS, run disp_rtf_chan on that RTF a couple more times,
waiting about 30 seconds in between. (This way we can tell if the timeslot just briefly
went OOS, or if it is staying OOS.)
2. Inject the following messages into CRM:
msg 34 9000h 0 0 0 0b2h 0f0h <local cell id>
3. Dump all the SWFMs on the BTP.
swfm l a
swfm d a
4. Statistic of problem cell,
SDCCH_mean_arrival_rate
SDCCH_congestion
SDCCH_mean_holding_time
SDCCH_congestion_key
OK_ACC_PROC (all bins)
5. Configure the sd_load to 0 for the PDCH configured carrier and monitor
the site to see the problem disappeared or not.
Workaround
Reconfigure Database; make sd_load to 0 on PDCH carrier.

Appendix A: General data collection procedure for GPRS Cell/PD OOS:

1. General logs, which can show the problem happen:
state 0
disp_pr 0
state pcu
disp_pr pcu
swfm l a then swfm d a (all DPROC/MPROC of PCU, BTP/DHP/TCU on BTS)
Event logs (3 hrs prior to the cell going oos)
2. PCU logs:
login to 1107h
msg_s 0d2h 9000h 0 0 0 0 0 0 0 <local cell id> (Cell state)
login to PRP board control the problem cell
(Cell info in PRM)
(Carrier info in PRM)
msg_s 0d9h 9000h 0 0 7404 04 87 00 00 00 <local cell id > <carrier_id> <ts>
(TS history)
pb list
login to PICP board control the GDS:
msg_s 0dbh 09000h 0 0 0 10 (Toggle rlogin/no session)
msg_s 0dbh 9000h 0 0 0 2 (shows PMC index in which slot)
pb list
3. BTS logs:
login to BTP
Appendix B: PCI debug command
First of all, doing dump on large memory regions works better over RLOGIN than it does
straight onto the serial port of the dproc being investigated.
1. PCI READ BUFFERS
for pci read buffers (ids starting with 80000000):
dump 10010h 80
take the last digit of the buffer id, and count forward that many ULONGs (4 byte
quantities) forward in the dump output, starting at zero, not 1. (the first ULONG is buffer
zero). take that value as a new pointer and do another dump. for instance:
PCU:emon_1104 % dump 10010h 80
00010010: 00ff37a0 00feec58 00fea3d0 00fe5b48
00010020: 00fe12c0 00000000 00000000 00000000
00010030: 00000000 00000000 00000000 00000000
00010040: 00000000 00000000 00000000 00000000
00010050: 00000000 00000000 00000000 00000000
for buffer 80000004, count 0 1 2 3 4 ... and take the fifth ULONG, which in this
case is 00fe12c0. dump that:
dump 00fe12c0h 128

and now youve seen the reader control block.
2. PCI WRITE BUFFERS

for pci write buffers (ids starting with 40000000), run:
dump 00010110h 600h
this shows all write buffer control blocks.
Appendix C: NIB debug command
Before start the data collection, visit following web page if you do not have serial cable
for NIB:
http://www.ecid.cig.mot.com/NSSG/GPRS/NEW/documents/setting_up_a_trial/Field_T ria
l_Checklist.html#link4
Get a serial cable into the DPROC (were the OOS GDS is physically hooked to), get the
following info from NIB.
First do the command:
tt NAME
substituting the task name for NAME, in double quotes.
Then, determine the version of NIB object you have. Type in this command:
traudbg_chan 0
If you get undefined symbol: traudbg_chan then you have a type 1 nib object. If you
get a Channel Statistics table output then you have a type 2 nib object. Some
commands below are valid only for type 1 and some valid only for type 2. Those
commands are prefixed with a (1) or a (2).
Perform the following commands:
d &motTS0s,1,4 ( repeat a couple of times )
d 0xac,1,4 ( repeat a couple of times )

d 0xff003c00,64,4
d 0xff003d00,64,4
d 0xff002000,256,4
d &buffDesc,6,4
d &qmc_driver_stats,6,4 ( repeat a couple of times )
(1)d &p2t_lookup,256,4
d &ts_inuse,16
d &chanData, 384, 4
(2) d &trau_stats,6,4
((timeslot*4)+group). So if SM and pSM say that a particular timeslot/group should be in
service on a particular GDS, find the PMC that terminates the GDS and run
(1) trau_stats <channel_number>
(2) traudbg_chan <channel_number>
Where <channel_number> is calculated as stated above. On a type (2) NIB object, you
can also use the following:
(2) traudbg_chans [ this displays all channels ]
For PCI buffer problems, please dump the following information.
d *0xa4,8,4

This will display PCI buffer control headers. For example:

007a1000: 00000040 00000040 007a1000 00000000 *...@...@.z......*
007a1010: 007b9798 007b1f30 00000000 00000000 *.{...{.0........*
Take the first value on the second line (in this case 007b9798) and dump that memory,
too. This is the HOST2NIB1 buffer control data. If youre using the top E1 span, take
the second value on the second line,
for the HOST2NIB2 buffer.
d 0x007b9798,32,4
007b9790: 484f5354 324e4942 * HOST2NIB*
007b97a0: 2d310000 00000000 00007810 00005a00 *1........x...Z.*
007b97b0: 0000000c 00000010 01000200 0000010e *................*
007b97c0: 00000000 00000000 00000000 00000000 *................*
007b97d0: 00000000 400101c0 00000000 00000000 *....@...........*
007b97e0: 00000000 00000000 064e4942 32484f53 *.........NIB2HOS*
007b97f0: 542d3100 00000000 00000000 00000000 *T1.............*
007b9800: 00000000 00000000 00000000 00000000 *................*
007b9810: 00000000 00000000 *................*
If there is a number starting with 40xxxxxx on the 4th or 5th line of this output, also
dump that address. In the above example, there isa valid value on line 5 of 400101c0.
This shows the DPROCs control structure for the same buffer.
d 0x400101c0,32,4
400101c0: 484f5354 324e4942 2d310000 00000000 *HOST2NIB1......*
400101d0: 00007810 00005a00 0000000c 00000010 *..x...Z.........*
400101e0: 00000010 01000200 00000000 0000000c *................*
400101f0: 00001a00 00000000 00000000 00000000 *................*
40010200: 00000000 90fb9798 00000000 00000000 *................*
40010210: 00000000 00000000 484f5354 324e4942 *........HOST2NIB*
40010220: 2d320000 00000000 00007810 00005a00 *2........x...Z.*
40010230: 0000000c 00000010 00000010 01000200 *................*
Appendix D: Command summary

msg_s 112 6 0 0 1c00h 1 (Disable GPROC (at the BSC/BTS) level 3 timeout in
emon)
msg_s 23 1 0 0 8a04h 1 (Disable the PCUs DPROC level 3 time out)
msg_s 23 1 0 0 8a04h 0 (Enable the DPROC level 3 timeout)
msg_s 112 6 0 0 1c00h 0 (Enable GPROC level 3 timeout in emon)
MPROC:
which DPROC)
msg_s 040h 9000h 0 0 0 5 (PSM table)

msg 40h 9000h 0 0 0 0ffh (PSM debug help cmd)
msg 0d2h 9000h 0 0 0 0ffh (GBM debug help cmd)
msg_s 208 9000h 0 0 0 0 (CB debug help cmd)
PRP board:
(Cell info in PRM)


msg_s 0d5h 9000h 0 0 0f0h <local cell id>
(Cell info in FBM)
(TS history)
perf all
pb list
msg_s 0d9h 9000h 0 0 7404h 04 0 (PRM debug help cmd)
PICP board:
msg_send 0dbh 09000h 0 0 0 10 (Toggle rlogin/no session)
msg_s 0dbh 9000h 0 0 0 2 (tell you which slot the given PMC index is in)
msg_s 0dbh 9000h 0 0 0 4 <CN0> <CN1>
(Print our TS array)
msg_s 0dbh 9000h 0 0 0 33 (print UL trau stats)
msg_s 0dbh 9000h 0 0 0 34 (pint DL trau stats)
msg_s 0dbh 9000h 0 0 0 35 (pint UL ptrau stats)
msg_s 0dbh 9000h 0 0 0 36 (print DL ptrau stats)
msg_s 0dbh 9000h 0 0 0 37 (print UL trau throughput)
msg_s 0dbh 9000h 0 0 0 38 (print DL trau throughput)
perf all
pb list
msg_s 0dbh 9000h 0 0 0 0ffh (TSN debug help cmd)
BSCBSP:
(check GCI connection)
msg 64 3 99 99 0f0ch 54h <mms_id_0> <mms_id_1> <timeslot> <group>
(print info on GCI)
msg 64 3 99 99 0f0ch 26h <timeslot>
(verify GCI with TDM)
msg 64 3 99 99 0f0ch 03h <ts_msb> <ts_lsb> 0x02h <group>
(print our TDM to GCI table)
BTSMCU:
(Carrier Config Manager Display Request (for cell))
msg 34 9000h 0 0 0 0b5h 0f1h <carrier id> 018h <timeslot id>
msg 34 9000h 0 0 0 0b6h 0f1h <carrier id> 018h <timeslot id> 011h 0
msg 34 9000h 0 0 0 0beh 28 (Turn on CRM internal debug)
msg 34 9000h 0 0 0 0beh 0 (Turn off CRM internal debug)
msg 34 9000h 0 0 0 0a9h 12h 2 (abnormal TS transaction history)


Chapter 9
Annex B

Version 1 Rev 1

Version 1 Rev 1
Chapter 9
Annex B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
Data Colection Procedure for PDTCH OOS 1614 Loads. . . . . . . . . . . . . . . . . . . . . . . . . . 91
..................................................................... 91

Version 1 Rev 1 Data Colection Procedure for PDTCH OOS 1614 Loads.
Data Colection Procedure for PDTCH OOS 1614 Loads.
If you have any problems with this procedure, mail cs_gprslist@majordomo.cig.mot.com
Before start all following data collection, please enable time stamp, so it is easier to
correlate all logs together.
General Info:
swfm l a then swfm d a from the all DPROC(PRP/PICP), MPROC,

BSP, LCF controlling site, BTP, DHP/TCU controlling the GPRS
PDTCHs.
state 0
state pcu
state <site>
disp_cell <cell ID> FULL
disp_pr pcu
disp_pr 0
disp_pr <site>
disp_act_alarm pcu
disp_act_alarm 0
Save as: ALARM_STATE.txt
1. events on BSC ~3 hrs prior to the cell going oos

Save as: <DATE>_Events.txt
2.
database (ascii) Save as: <BSCNAME>_database.txt
Type 1
Description
GPRS Status Barred of one cell, PDCH status No activation, PD Channel is NA
From disp_cell_s <site> you will find GPRS is OOS for whole cell, all PDs are NA. PRM
has no cell info of those cells.
Related PR
PR 149764 GPRS cell barred after cell activation procedure fixed by 1614.c1 and
committed in 1620.d8.
PR 149776 GPRS cell barred after cell activation procedure committed in 1620.dd
General Info
Follow the general information data collection procedure, especially SWFM logs.
On the MPROC:
1. msg_s 0d0h 9000h 0 0 0 3 (CB summary)
msg_s 0d0h 9000h 0 0 0 4 (CB summary including carrier ID info). Will give you local
carrier info to use below

Data Colection Procedure for PDTCH OOS 1614 Loads. Version 1 Rev 1
.2 msg_s 0d2h 9000h 0 0 0 0 0 0 0 <local cell id> (Cell state)

3. Following filter need to be setup before the problem happen, if the PCU
is stable, this filter will not generate a big load for PCU, it monitor all the cell activation
and deactivation message GBM send. It is suggest using a PC directly connect to
MPROC to catch the logs. Before start the filter, you should also disable the timeout of
PCU:
msg_s 112 6 0 0 1c00h 1 (Disable GPROC (at the BSC/BTS) level 3 timeout in emon)
fiter start all
filter list all
Note: After finish data collection:
On the PRP controlling the cell:
One the PRP board (you can identify the PRP board from the output of message 2)
above on the MPROC.
1. msg_s 0d9h 9000h 0 0 7404 04 15 0 0 0 <local cell id> (Cell info in
PRM)
2. msg_s 0d9h 9000h 0 0 7404 04 14 0 0 0 <local cell id> <local carrier id>
(Carrier info in PRM you can get the carrier ID from the pervious msg send for the cell
info)
3. msg_s 0d5h 9000h 0 0 0f0h <local cell id> (Cell info in FBM)
On all PICPs:
Do this at every PICP
At the BTS, send the following to CRM:
msg_send 34 9000h 0 0 0 0b3h 0f0h <local cell id> (Carrier Config Manager Detailed
Display Request)
msg_send 34 9000h 0 0 0 0b9h 0f0h <local cell id> (Channel Resource View Linked List
Info Request)
msg_send 34 9000h 0 0 0 0bbh 0f0h <local cell id> (Carrier Config Manager Display
Request (for cell))
Workaround
Toggle gprs_enabled
Type 2
Description
GPRS Status Barred of one cell, PDCH status No activation, PD Channel is 0
Type 2a
Description
GPRS Cell Barred, PD No Activation, PD Channel 0
Compare to type1, from PRM cell info,
Num Carriers INS: 0
Related PR
PR 149399 After a site soft reset, GPRS is BARRED committed in 1614.c5 & 1620.d7.
PR 149764 GPRS cell barred after cell activation procedure fixed by 1614.c1 and
PR 149776 GPRS cell barred after cell activation procedure committed in 1620.dd.
PR 150791 GPRS cell barred as No. of carrier INS in PRP in 0 committed in 1620.dd.

PR 151102 GPRS stays barred due to GSM cell ins/oos/ins committed in 1620.dd.

Same as type1
Workaround
Toggle gprs_enabled
Type 2b
Description
GPRS Cell Barred, Bitmap do to match between PRM and CRM.
From disp_cell_s output, GPRS Cell Barred, PD No Activation, PD Channel 0.

PRP cell info shows there are no TS configured as PDCH, but CRM cell info shows TS
has been configured as PDCH. The problem can be identified as following step:
Run msg_s 0d9h 9000h 0 0 7404 04 14 0 0 0 <local cell id> <local carrier id> on PRP,
you will find:
TS Bitmap: 0x00
CRM TS Bitmap: 0x00
Run msg_send 34 9000h 0 0 0 0b3h 0f0h <local cell id> on BTS, you will find:

If they are mismatched between CRM and PRM, it is the problem.
Related PR
PR 142254 CRM and PRM bitmaps are out of sync fixed in 1614.0 and 1620.a6.
On the MPROC:

msg_s 0d0h 9000h 0 0 0 4 (CB summary including carrier ID info). Will give you local
carrier info to use below
If the problem is reproducible, then Setup filter on PRP(controlling the cell) and BTP
before the problem happen:
filter create tag 73xxh
filter start all

above on the MPROC.
msg_s 0d9h 9000h 0 0 7404 04 15 0 0 0 <local cell id> (Cell info in PRM)
msg_s 0d9h 9000h 0 0 7404 04 14 0 0 0 <local cell id> <local carrier id> (Carrier info in
PRM you can get the carrier ID from the pervious msg send for the cell info)


Display Request)
Info Request)
Workaround
Toggle gprs_enabled will resolves the problem.
Type2c
Description
GPRS Cell Barred, Cell activation message was dropped from PRM to CRM.
From disp_cell_s output, GPRS Cell Barred, PD No Activation, PD Channel 0.
Compare the Cell info on PRM and CRM, we can found CRM never receive cell
activation message. There are three possible reason cause this problem:
a. cell activation message is not sent by PRM.
b. The message is dropped during the path between PRM and CRM
c. CRM receive the message but discard.
Related PR:
PR 144638 Links lost between slave GPROCS on the LAN committed in 1620.d5.
MMI logs:
state pcu
state 0
disp_p pcu
disp_p 0
SWFM dump of DPROC on PCU and GPROC on BSC. (swfm l a, swfm d a)
On the MPROC:


above on the MPROC.
msg_s 0d9h 9000h 0 0 7404 04 15 0 0 0 <local cell id> (Cell info in PRM)
msg_s 0d9h 9000h 0 0 7404 04 14 0 0 0 <local cell id> <local carrier id> (Carrier info in
PRM you can get the carrier ID from the pervious msg send for the cell info)

Display Request)
Info Request)
Setup following filters before toggle GPRS, _enabled:
On PRP board that control the cell, and BTP board on the problem BTS:
filter create tag 73xxh
filter start all

Workaround
If toggle GPRS doesnt work, INS the LCF with control the site.
Type 3
Description
Entire GDS SPAN OOS, all PDs on this GDS out of sync.
This type is much easier to identify, from PICP, running following command:
msg_s 0dbh 9000h 0 0 0 44 (shows timeslot OOS)
msg_s 0dbh 9000h 0 0 0 45 (shows timeslot INS)
You will find entire GDS span are OOS, there is 0 PDs INS on the GDS Span. Although
the whole GDS span is OOS, but the disp_cell_status output may still show the GPRS
is in INS and only part of the PD unavailable
Type 3a
Description
Entire GDS SPAN OOS, all PDs on this GDS out of sync, all pb list output looks fine.
From TS_ARRAY output, we can see:

Case 1:
[12/06/01 17:56:45] PCU:emon_110b % msg_send 0dbh 9000h 0 0 0 4 00h 0c9h
Chan: 0x00c9 RTD: 0x01 CR: 0x01 TS: 0x05 Frame: 0x04
BUFFIDX: 0x00000000 TAL: 0x00 DR: 0x00 SyncState:0xff
PRMConn: 0x01 SSI: 0x00 UFE: 0xff MS#: 0x08 CUTA: 0x02
UlBlk#: 0x05 Seq Num: 0x68 UlBlkBM:0x0f DlBlkBM: 0x00 #UlSync: 0x00
DlBlk#: 0x0b DLTACI: 0x00 d266: 0x00 Cell: 0x00
TTS: 0x23 eDLTACI: 0x00 CCUConn:0x01 eSeq#: 0x7f
<==== Indicate CCU does not have sync with D/L trau frame
UL AFNbis:2653638 DL AFNbis:0
<====UL AFN increase, but DL AFN still stay at 0.
TAL Tot: 0x00000045 TAL Delay:0x00000000
Related PR
PR 151123 Span of PDs OOSync due to E1 bitshift committed in 1620.df.

1. First find a GDS that is completely OOS, by entering the follwing
for #2 below)
Run following command for a couple of times

2. Randomly select three channels from TSN OOS list, run following
command to print TS_ARRAY, which tells whether any packets have been received.
msg_s 0dbh 9000h 0 0 0 4 <CN0> <CN1>
where CN0 is the MSB (mostsignificant byte) of the channel number
and CN1 is the LSB (leastsignificant byte) of the channel number.

For example:
PCU:emon_1101 % msg_send 0dbh 9000h 0 0 0 44
The following TRAU channels are out of sync:
CN:0x1d Cell:24 CR:13 TS:5 PmcIdx:0
CN:0x1e Cell:71 CR:0 TS:5 PmcIdx:0
So to print ts_array of these TS, type following command about 4 times each:
msg_s 0dbh 9000h 0 0 0 4 0 1dh (where 0 1dh is your CN0 CN1)
msg_s 0dbh 9000h 0 0 0 4 0 1eh (where 0 1eh is your CN0 CN1)

perf all
pb list
Workaround
INS MSI hooked the GDS link.
Type 3b
Description
Entire GDS SPAN OOS, all PDs on this GDS out of sync, PMC buffer is fully used
When the problem happens, on PRP, from pb list, it is found the host2nib buffer is fully
used, typically logs as following:

4000000a yes HOST2NIB1 00001a00 12 23040 23040 23040
Related PR
PR 143939 LAPD and TRAU NIB getting crashed fixed on 1614.b1 and committed in
1620.d5.
PR 150321 PD1080: Span of PDs OOSync due to pci buffer problem, which only
happens on 1620,

for #2 below)

pb list
3. Before start the data collection, visit following web page if you do not
have serial cable for NIB:
Get a serial cable into the DPROC (were the OOS GDS is physically hooked to), get the
following info from NIB.
First do the command:
i

tt NAME
substituting the task name for NAME, in double quotes.
Then, determine the version of NIB object you have. Type in this command:
traudbg_chan 0
get a Channel Statistics table output then you have a type 2 nib object. Some
commands below are valid only for type 1 and
some valid only for type 2. Those commands are prefixed with a (1) or a (2).
Also perform the following commands:

d &motTS0s,1,4
( repeat a couple of times )
d 0xff003c00,64,4
d 0xff003d00,64,4
d 0xff002000,256,4
d &buffDesc,6,4
d &qmc_driver_stats,6,4 ( repeat a couple of times )
(1) d &p2t_lookup,256,4
d &ts_inuse,16
d &chanData, 384, 4
(2) d &trau_stats,6,4
((timeslot*4)+group). So if SM and pSM say that a
particular timeslot/group should be in service on a particular GDS, find the PMC which
terminates that GDS and run
(1) trau_stats <channel_number>
(2) traudbg_chan <channel_number>
or
(2) traudbg_chans [ this displays all channels ]
Where <channel_number> is calculated as stated above.
Normally channel numbers start at 111 and go down from there,so a good first try would
be
(1) trau_stats 111
(1) trau_stats 110
(1) trau_stats 109
(1) trau_stats 108
The above commands dump downlink statistics. For uplink stats there is not a function,
you have to dump the channel structures themselves. The command is:
(1) d &t2p_chan+64*CHANNEL,16,4
Substitute channel number for CHANNEL, so for channel 111, the command is:
(1) d &t2p_chan+64*111,16,4

to take a look at data coming in on an E1 timeslot, follow these steps below.
First, dump the QMC global parameter table:

> d 0xff003c00,24,4
ff003c00: 007f8000 0000dead 3c203c30 00010001 *........< < ....*

ff003c10: 007fb000 007fb3e8 3c203c50 00000000 *........< <X....*
ff003c20: b03f0000 00000000 00000000 00000000 *.?..............*
ff003c30: 00000000 00000000 00000000 00000000 *................*
ff003c40: 00000000 00000000 00000000 00000000 *................*
ff003c50: 00000000 00000000 00000000 00004000 *..............@.*
The fourbyte value at ff003c00 is the beginning of the space where bufferdescriptors
start. (Here, it is 007f8000.) Remember that value for later. Information for QMC
channels starts at ff003c20, and each timeslot has a twobyte entry. In the example
above, only timeslot zero is enabled, so the other 31 entries are 0000. Take the twobyte
value for timeslot zero and mask off some bits (mask is 0x7c0):
> 0xb03f & 0x7c0
value = 0 = 0x0
In this case, the result is zero. For other timeslots, it wont be zero. Add this value to
ff002000 and dump that memory:
> d 0xff002000,16,4
ff002000: 00007100 30590f1e 0079f008 00000018 *..q.0Z...y......*

ff002010: 0000aaaa 69aa01aa 00009e5d 00ff9000 *....i......]....*
ff002020: 00400050 31c0a200 0079f0f4 0048004c *.@.P1....y...H.L*
ff002030: ffffffff 2fffffff 0000e741 00000000 *..../......A....*
This is the table of parameters for a single QMC channel. The first two lines are data for
the TX hardware, the second two lines are RX hardware.
The first two bytes of each twoline section is where to locate buffer descriptors; add this
value to the fourbyte value found above at ff003c00. For instance, TX BDs for this
timeslot start at 007f8000 + 0000, and RX BDs start at 007f8000 + 0040. Now view the
RX BDs for this timeslot:
> d 0x007f8040,4,4
007f8040: 86000050 0079f0a0 a2000050 0079f0f0 *...P.y.....P.y..*
The second and fourth 4byte values actually point to the buffers of received data for this
timeslot. Examine them.
> d 0x0079f0a0,20,4
0079f0a0: ffffffff ffffffff ffffffff ffffffff *................*

0079f0b0: ffffffff ffffffff ffffffff ffffffff *................*
0079f0c0: ffffffff ffffffff ffffffff ffffffff *................*
0079f0d0: ffffffff ffffffff ffffffff ffffffff *................*
0079f0e0: ffffffff ffffffff ffffffff ffffffff *................*
> d 0x0079f0f0,20,4
0079f0f0: ffffffff ffffffff ffffffff ffffffff *................*

0079f100: ffffffff ffffffff ffffffff ffffffff *................*

In this case, we are seeing all binary 1s. This is what you should see when there is no
incoming span connected to the NIB. This NIB should currently be reporting MMS Sync
Loss OOS.
Workaround
Reset DPROC.
Type 3c
Description
Entire GDS SPAN OOS, all PDs on this GDS out of sync, NIB buffer of PRP is not
created
When the problem happens, run pb list on both PICP and PRP. From the output of PRP
board, HOST2NIB buffer is not shown on write ID list. From the output of PICP board
(control the GDS), HOST2NIB buffer will show No attached on write ID list, pmc2tsn*
buffer will show No attached on read ID list.
Related PR
PR 149792 NIB does not properly handle stale pci buffer fixed in 1614.c1 and
committed in 1620.da.
PR 151158 race condition in pci management causes pci buffer problems committed in
1620.ddt1 & 1650.0a.

msg_s 0dbh 9000h 0 0 0 2 (Tells you which slot the given PMC index is in (DPROC ID
for #2 below)

pb list
3. Dump all SWFMs of all DPROC of PCU (swfm l a; swfm d a)
Workaround
Reset DPROC.
Type 4
Description
Individual PDTCH OOS, PD configuration stuck in CRM
The identification of these problems mostly focuses on BTS side. When the problem
happens, from disp_cell_s we can find individual PDCH are OOS or missed, then we
need run following command at BTP:
msg_s 34 9000h 0 0 0 0b3h 0f0h <local cell id>
Note: GPRS channel reconfig diagram at

http://www.cig.mot.com/Organization/GSM/rss/Helpfull_info/timeslot_reconfig.html (Need
AH access)
Type 4a
Description

PDTCH configuring is TRUE, TS stuck on c8

From output of
PDTCH configuring = TRUE
From output of

Related PR
PR 145151 PD configuration stuck in CRM (Under monitor)
Attempts to recreate this problem in AH were unsuccessful. Please follow the additional
data collection below to collect further debug to verify the state of the timeslot at the time
of problem occurrence.
1. Follow the general information section of the GPRS/PDTCH OOS

document at http://www.cig.mot.com/Organization/GSM/CS/cs_web/
Collect event logs for 1 week before the problem
2. Confirm the problem

msg_s 34 9000h 0 0 0 0b3h 0f0h <local cell id>
3. Set the following TS query debug

FM & CP Set_Radio TS Monitor (Set at the BTP)
fil start_new src 022h func 05h msg[0] 03h msg[1] 0ah msg[2] 03h
fil start_new src 04ch func 07h msg[0] 13h msg[1] 0ah msg[2] 03h
fil start_new src 04ch func 07h msg[0] 23h msg[1] 0ah msg[2] 03h
fil start_new src 04ch func 01h msg[0] 56h
fil start_new src 030h func 04h msg[0] 57h
RSS TS Query & Timer monitor (Set at the RSS emon)

msg_send 50 500h 0 0 000000ddh 0ddh <dri #>
msg_send 51 500h 0 0 000000ddh 0ddh <dri #>
iir_mod 50 00000020h
FW TS Query (Set at the RSS emon)

msg_send 50 0ffh 0 0 0 1 <dri #> <ccdsp/TS> 0ffh 06 0fch (to get filter ID)
msg_send 50 0ffh 0 0 0 2 <filter ID>
msg 50 0 74 7791h 0 90 0 <ts> 4 0 2 05h 05h
4. Modify_value max_gprs_pdch so that the affected timeslot is

reconfigured. If the problem timeslot recovers stop here. Otherwise, toggle GPRS, INS
the PCHN or reset the DRI to recover. Depending on platform RSS and FW may be lost
so save them before resetting the DRI
Type 4b
Description


From output of
TCH/F configuring = TRUE
From output of


Same as type 4a
Type 4c
Description
From output of
SDCCH configuring = TRUE
From output of


Same as type 4a
Type 4d
Description
From disp_cell_s PD is missed. From CRM info, GetSDforPDTCH in progress is
TRUE
From output of
GetSDforPDTCH in progress = TRUE
From output of
all TS was configured properly.

N/A
Type 5a
Description
PDTCH OOS associated with DRI 15 alarm

When the problem happened, from event logs can found many DRI 15 alarm generated
on the DRI.
Related PR
PR 149280 A few PDs in some Incell sites out of sync in 1620.d3 fixed in 1614.c and
PR 151359 Restructure RTD(Round Trip Delay) calculation in TSN committed in
1620.dd
On BSC
disp_equip <site>DRI <id1> <id2> full (see the specific radio type and and the cell the
DRI is in)
disp_bss
disp_cell_status <site id>
disp_gsm_cell <site id> (Get the alarm DRIs local cell ID which is in decimal format)
disp_rtf_chan
disp_proc pcu
On the MPROC:
which DPROC)
1. Dump Carrier information:

At all PICP
1. Find out which GDS the TS is allocated to:

msg_send 0dbh 9000h 0 0 0 44 (shows timeslot OOS)
msg_send 0dbh 9000h 0 0 0 45 (shown timeslot INS)
msg_send 0dbh 9000h 0 0 0 2 (print all PMC buffer desc index message into TSN)
2. Print TS_ARRAY of the timeslot which got DRI 15 alarm, run following at
least twice:
msg_s 0dbh 9000h 0 0 0 4 <CN0> <CN1>
Notes: Detail example please refers to type3a step 2.
3. Run following command for a couple of times on same PICP which

contains TS got dri 15 alarm.
Note: The number of no data frames in the UL PTRAU output (message 35) will be a
high number (percentagewise) when we see this problem. Every time TSN builds a DL
frame without first receiving an uplink frame, this stat should get pegged.
Workaround
INS pchn resolves the remainder.

Type 5b
Description
PD OOS, Flood SWFM on BSP indicate Error on GCIRCI connection setup.
From disp_cell_status found some TS unavailable, found flood of BSP swfm.
Also there is flood SWFM on BSP:
50b8 Nonfatal SWFM Error Routine: psm_messages.c

50b8 Area: 0x00008000 Error: 0x0000ffff PC: 0xc000427a PID: 0x40 (SM BSC)
50b8 BSS Release: 1.6.1.4.6 Obj Version: 1.6.1.4.6
50b8 02Feb2001 18:47:31.910 Subsystem: 0x01 CPU: 0x0115 Board: GPROC2 RAM
50b8
50b8 SM Error [0x17]: RCI timeslot has invalid index to rci_to_port.
50b8 detected in file get_rci_conn_to_gci.c at line:120
50b8 > timeslot_rci_in = 0x31b
50b8 SM Error [0xffff]: Error getting RCI connected to GCI.
50b8 detected in file pcu_con_disc_req.c at line:451
50b8 > gds_channel_id = 0x15011302
50b8 SM Error: PCU Con Disc had a Failure.
50b8 detected at line:100
Related PR
PR 144288 Fix routing of pSMSM messages and redundant con reqs to SM
committed in 1614.8 & 1620.d3
PR 146839 Fix routing of pSMSM messages and redundant con reqs to SM
committed in 1614.b & 1620.d3
PR 147396 Stop Con Discon retries in PRM
PR 147464 Last GBL going OOS causes SMpSM problems Committed in 1620.d4
PR 147518 PSM SWFM in infinate loop after inservice PICP DPROC committed in
1620.d2.
PR 147749 pSMSM interface changes for PRP OOS and GDS OOS cases committed
in 1620.d4
PR 148043 pSM to SM audit message redesign committed in 1620.d5

Running following command on BSP emon:
1. Print out info on the GCI where GCI is the gci_channel_id in the SWFM
gds_channel_id = 0x15011302
msg_send 64 3 99 99 0xf0ch 0x54h <mms_id_0> <mms_id_1> <timeslot> <group>
For example, the parameters should be 0x15 0x01 0x13h 0x02h for the example above.
SM will then print TDM timeslots associated with the GCI, port state (3 is active, 2 is
idle), and will most likely fail to get RCI connected to this GCI.
2. Verify that GCI is correctly mapped to TDM timeslots.
msg_send 64 3 99 99 0xf0ch 0x26h <timeslot>
For example, the parameter should be 0x13. SM will search all MMSs and for each MMS
will print TDM timeslot mapped to this MMS timeslot. Look for MMS that matches the first
2 bytes in gds_channel_id, and the corresponding TDM timeslots must mach those
printed in 1.
3. Print TDM timeslots connected to the GCI.
msg_send 64 3 99 99 0xf0ch 0x03h <ts_msb> <ts_lsb> 0x02h <group>
Where ts_msb and ts_lsb are MSB and LSB of the GCI TDM timeslots printed by
1st message inject respectively. Group is, similarly, TDM timeslot group number printed
by 1st message injects.
Workaround

PSMSM interface redesign in 1620 will resolve BSP SWFM flood issue, related PR see
PR list at the beginning of this document. Currently a workaround as attached can also
force the GCI idle. Until you are quite confidence understand all step, then go ahead.
1. Note the GCI ids in the swfms (look for psm_messages.c SM BSC
swfms, and for gds_channel_id). 1st and 2nd byte in gds_channel_id are MSI and MMS
ids, respectively, of the span where the GCI is.
2. Lock the MMSs where these GCIs are. The swfms should stop.
3. Inject the following message:
msg_send 64 3 99 99 0f0ch 54h < mms_id_0> < mms_id_1> < timeslot> < group>
Where mms_id_0, mms_id_1, timeslot, and group are 1st, 2nd, 3rd, and 4th byte in
gds_channel_id (from the swfm).
SM will print out something like this:
******************** Debug Output ********************

Port Information for GCI 0x15011302
Timeslot Number: 0x0717

Group Number: 2
State In: 3
State Out: 3
SM Error [0x17]: RCI timeslot has invalid index to rci_to_port.

detected in file get_rci_conn_to_gci.c at line:120
> _timeslot_rci_in = 0x31b
SM ERROR: GCI active, but failed to find connected RCI
***********************************************************
4. Note the timeslot number for the GCI and make sure the state is 3
(active). Then inject the following message:
msg_send 64 3 99 99 0f0ch 3 <ts_msb> <ts_lsb> 2 <group>
Where the ts_msb and ts_lsb are MSB and LSB of the timeslot number, and group is the
group number. In the the example above, ts_msb = 07h, ts_lsb = 17h, group 2.
SM will print port_db entry that corresponds to this timeslot. For example:
******************** Debug Output ********************
** Information for TDM Timeslot 0x0717 Group 2 **
Port state in: 3
Connected to TS in
TS: 0x031b
Group: 3
Rate: 3
Port state out: 3

Connected to TS out
TS: 0x031b
Group: 3
Rate: 3
Timeslot Array Value: 7

TS used by GCI 0x15011302
*******************************************************

5. Make the GCI timeslots idle by injecting the following message:
msg_send 64 3 99 99 0f0ch 3 <ts_msb> <ts_lsb> 2 <group> 23h 2 2
Where ts_msb, ts_lsb, and group have the same meaning as in step 4. The 2s at the end
of the message means force idle state of both inbound and outbound ports.
SMs output will look like this:
******************** Debug Output ********************
New Port Inbound state: 2

New Port Outbound state: 2
** Information for TDM Timeslot 0x0717 Group 2 **
Timeslot Array Value: 7

TS used by GCI 0x15011302
***********************************************************
6. Inject the same message as in step 3 to verify that ports associated with
GCIs are idle (state = 2).
7. Repeat steps 36 for all GCIs
8. Unlock MMSs. From now on, there shouldnt be any SM swfms SM

must not complain about GCIs being already active.
Type 5c
Description
Entire GDS SPAN OOS, PD Unavailable, flood SWFM on controlled PRP board
Although the whole GDS span is OOS, but the disp_cell_status output may still show
the GPRS is in INS and only part of the PD unavailable.
When the problem happen, from cell controlled PRP board you will got flood SWFM:
prm_build_send_ts_switch_on.c:Attempt to write switch on TS message (Cell:0x3c
Carrier:0x1 TS:0x6) failed!
status = 5
Data buffer index = 5, buffer id = 0
prm_build_send_ts_switch_on.c:Cell Index 20!
Cell id: 60
picp_cpu_slot_id: 2
Slot_to_data_buffer: 5
Related PR
PR 149023 Stop retransmission of sw on/off, Con Discon due to PCI fail fixed in
1614.c and committed in 1620.d7.

for #2 below)


pb list
3. dump SWFM of all DPROC (swfm l a, swfm d a)
Workaround
Reset PRP board.
Type 5d
Description
PDTCH OOS, No alarm, No UL frame received on TSN:
Carrier info dumped from PRP board:
TS[6]: ULTFI Map:0xff 0xff UL PACCH: 0x00 DLTFI Map:0xff 0xff DL PACCH: 0x00
PICP ID:0x02 State:Non Service Pend
TS_Array print our from PICP board: (if repeat three time, we can found AFN stuck).
[08/06/01 10:20:11] PCU:emon_1102 % msg_s 0dbh 9000h 0 0 0 4 0 5eh
Chan: 0x005e RTD: 0x06 CR: 0x01 TS: 0x06 Frame: 0x05
BUFFIDX: 0x00000002 TAL: 0x00 DR: 0x00 SyncState:0xff
PRMConn: 0x01 SSI: 0x01 UFE: 0x00 MS#: 0x08 CUTA: 0x00
UlBlk#: 0x07 Seq Num: 0x0c UlBlkBM:0x00 DlBlkBM: 0x00 #UlSync: 0x00
UL AFNbis:1856274 DL AFNbis:1856278 === DL/UL stucked
TAL Tot: 0x0000003c TAL Delay:0x0000341c
Related PR
PR 148043 pSM to SM audit message redesign fixed in 1620.d5.
One known problem, pSM and SM out of sync, can cause this problem. PR 148043
commited in 1620.d5. Step 1 6 will help you identify the problem is cause by this PR. If
the problem is different, then further data collected may need some extra cable and test
equipment. (NIB debug cable, TPS, K1205)
1. Find the timeslot out of sync on the PICP

msg 0dbh 9000h 0 0 0 44
msg 0dbh 9000h 0 0 0 45
eg: PCU:emon_1101 % msg_s 0dbh 900h 0 0 0 044

CN:0x12f Cell:28 CR:0 TS:6 PmcIdx:2
Total OOS:1
2. From the output of step 1, choose three OOS PDTCH, print TS entry for
at least THREE times each:
msg_s 0dbh 9000h 0 0 0 4 <CN0> <CN1>
eg: emon_1101 % msg_s 0dbh 9000h 0 0 0 4 01h 2fh
3. Pring PRP carrier information, repeat the command for three times.

4. Check SM at BSP:
For this example: Take Cell:28, CR:0, TS:6 and check this at pSM and SM to see that
both ends link up:
msg 64 3 99 99 0f0ch 6 28h 0 1 6
******************** Debug Output ********************
** Information for RCI 0x28000106 **
rci_to_port index : 0x0422

GCI (MMS ID 0, MMS ID 1, MMS TS, MMS Group # : 18 0 20 3
GCI TDM Timeslot : timeslot 1683

group 3
SCCP number : 0xffffff
CERM Error Counter :0

CERM Alarm Set Flag :0
CERM Resync Occurred Flag :0
CERM TRAU Error Occurred Flag : 0
Inbound Information
Path 0 Timeslot : 0x064b

Group :2
Rate :3
Port State In : 3
Group :2
Rate :3
Port State In : 3
Outbound Information

Group :2
Rate :3
Port State Out : 3
Group :2
Rate :3
Port State Out : 3
RCI swap flag :0
***********************************************************
Note: GCI (MMS ID 0, MMS ID 1, MMS TS, MMS Group # : 18 0 20 3
This means the GCI for this timeslot (Local cell ID: 28h, Carrier ID: 0, Timeslot: 6) has
MMS 18 0, Timeslot 20, and Group 3 going to the PCU.
5. Now check the pSM at the MPROC:

msg 40h 9000h 0 0 0 3 0 0 0 <Local cell ID>
For this example: msg 40h 9000h 0 0 0 3 0 0 0 28h

## pSM RCI HASH TABLE DATA FOR CELL: 0028h ##
GCI:msimmstsgr CELL CAR TS STATUS

10 0 20 3 0028h 0 6 in use
8 0 16 0 0028h 0 7 in use
4 0 14 2 0028h 0 5 in use
10 0 12 3 0028h 0 4 in use
5 0 10 0 0028h 0 3 in use
** SUMMARY DATA FOR ENTIRE pSM RCI HASH TABLE **

NUMBER OF EXISTING CONNECTIONS: 717
NUMBER OF CON. REQS AWAITING RESPONSE FROM SM: 0
NUMBER OF DISCON. REQS AWAITING RESPONSE FROM SM: 0
Now look at Carrier 0, TS 6 and note the GCI info:

GCI:msimmstsgr CELL CAR TS STATUS

10 0 20 3 0028h 0 6 in use
So, the GCI has MMS 10 0, timeslot 20, group 3.
6. Now check that the GDS in the database maps the two ends at
pSM/SM:
disp_eq pcu gds <GDS ID>
In this example: MMIRAM 0115 > disp_eq pcu gds 9

The Unique GDS Identifier is: 9
The BSC MMS identifier is: 18 0
The PCU MMS identifier is: 10 0
The GDS type is: TRAU
Note:
Here, SM showed this timeslot was mapped to MMS 18 0, timeslot 20,
group 3 and pSM showed this timeslot was mapped to MMS 10 0, timeslot 20, group 3.
Looking at the disp_eq, we see that the database has the two MMSs as the two ends in
the GDS and also the timeslot/group match.
If the SM is mismatched with pSM table, then PR 148043 are hitted.
7. TPS needed for this step. Details related to TPS refer to:
http://www.ecid.cig.mot.com/GPD_ENG/GPD_FW/team_pages/mol/html/tps/index.htm
Connect TPS to the DRI which PD OOS, then catch the UL TRAU frame for that TS.
8. NIB debug cable needed for this step, Details refer to:
Connect the cable to the DPROC which physically hook the GDS, run following
command
traudbg_chan 0
get a Channel Statistics table output then you have a type 2 nib object.
For type 1 NIB objects, found the channel number from step 1, repeat 3 times run
trau_stats <channel_number>
For type 2 NIB objects, found the channel number from step 1, repeat 3 times run
traudbg_chan <channel_number>

9. K1205 needed for this step. (unfortunately we can not tested in our lab now)
Conect K1205 on the link between BSC and BTS, collect the UL/DL trau from BTS to
BSC of the problem TS. The MMS port and TS subchannel can be found from:
disp_eq <site> path <id1> <id2>
disp_mms_ts_usage 0 <id2> <id3>
Connect K1205 on the link between BSC to PCU, collect the UL/DL trau from BSC to
PCU of the problem TS. The MMS port and TS subchannel can be found from step 5.
Note:
Step 7 try to identify weather CCU send the UL sync frame to PCU.
Step 8 try to identify weather NIB receive any frame from CCU.
Step 9 try to identify did BSC receive the frame and set it down to PCU.
Workaround
INS pchn or INS DRI can resolve the problem
Type 5e
Description
PDCH are missed, comparing disp_cell_status & disp_rtf_chan
Carrier info dumped from PRP board, bitmap on PRM and CRM is mismatched.
Max GPRS TS: 7

Res GPRS TS: 0
TS Bitmap: 0xd4
CRM TS Bitmap: 0xfe
From TS history, it is because of PRM do not receive switch on ack from TSN.

Non Service Switch on Pend Timer Exp 1200 191104
TSN Detach for GPCS Pend Sw off Ack 0 191104
PSM Detach for GPCS Pend Discon. Ack 0 191172
*INACTIVE

Related PR
None.
1. General logs
state 0
state pcu
disp_p 0
disp_p pcu

disp_cell_s <site>
Event till the problem founded
SWFM dump on all DPROC board on PCU
2. Print our CB table and display PSM table: (on PSP board)
msg_s 0d0h 9000h 0 0 0 3
msg_s 040h 9000h 0 0 0 3 0 0 0 0
3. on BSC, find out which cell has PD missed, for all cell:
disp_cell_s <site>
disp_rtf_chan <cell id> <rtf id1> <rtf id2>
4. Choose three cells had PD missed, login to the PRP board controlling
the cell:
Print cell info and carrier info,
Print out the TS history of all TS of the cell, carrier on which PD is missed:
Workaround
Toggle GPRS.
Appendix A: Command summary
MPROC:
which DPROC)
msg_s 040h 9000h 0 0 0 3 0 0 0 <local cell id> (PSM table)
msg_s 112 6 0 0 1c00h 1 (Disable GPROC (at the BSC/BTS) level 3 timeout in
emon)
PRP board:
(Cell info in PRM)
msg_s 0d5h 9000h 0 0 0f0h <local cell id>
(Cell info in FBM)
(TS history)
perf all
pb list
PICP board:

msg_s 0dbh 9000h 0 0 0 4 <CN0> <CN1>
(Print our TS array)
perf all
pb list
BSCBSP:
msg_send 64 3 99 99 0xf0ch 0x54h <mms_id_0> <mms_id_1> <timeslot> <group> (print
info on GCI)
msg_send 64 3 99 99 0xf0ch 0x26h <timeslot> (verify GCI with TDM)
msg_send 64 3 99 99 0xf0ch 0x03h <ts_msb> <ts_lsb> 0x02h <group> (print our TDM
to GCI table)
BTSMCU:
(Carrier Config Manager Display Request (for cell))
msg 34 9000h 0 0 0 0b5h 0f1h <carrier id> 018h <timeslot id>
msg 34 9000h 0 0 0 0b6h 0f1h <carrier id> 018h <timeslot id> 011h 0
msg 34 9000h 0 0 0 0beh 28 (Turn on CRM internal debug)
msg 34 9000h 0 0 0 0beh 0 (Turn off CRM internal debug)
Appendix B: PCI debug command

(only works in 1620 load)
first of all, doing dump on large memory regions works better over RLOGIN than it does
straight onto the serial port of the dproc being investigated.
1. PCI READ BUFFERS
for pci read buffers (ids starting with 80000000):

dump 10010h 80
take the last digit of the buffer id, and count forward that many ULONGs (4 byte
quantities) forward in the dump output, starting at zero, not 1. (the first ULONG is buffer
zero). take that value as a new pointer and do another dump. for instance:
PCU:emon_1104 % dump 10010h 80
00010010: 00ff37a0 00feec58 00fea3d0 00fe5b48
00010020: 00fe12c0 00000000 00000000 00000000
00010030: 00000000 00000000 00000000 00000000
00010040: 00000000 00000000 00000000 00000000
00010050: 00000000 00000000 00000000 00000000

for buffer 80000004, count 0 1 2 3 4 ... and take the fifth ULONG, which in this
case is 00fe12c0. dump that:
dump 00fe12c0h 128
and now youve seen the reader control block.
2. PCI WRITE BUFFERS

for pci write buffers (ids starting with 40000000), run:
dump 00010110h 600h
this shows all write buffer control blocks.

Glossary of technical terms and
abbreviations
10TH JULY 95 Manual Title Goes Here G1

Version 1 Rev 1
G2 Manual Title Goes Here 10TH JULY 95

Version 1 Rev 1 Numbers
Numbers
# Number.
2 Mbit/s link As used in this manual set, the term applies to the European
4-wire 2.048 Mbit/s digital line or link which can carry 30
A-law PCM channels or 120 16 kbit/s GSM channels.
4GL 4th Generation Language.

A Version 1 Rev 1
A
A interface Interface between MSC and BSS.
A3 Authentication algorithm that produces SRES, using RAND
and Ki.
A38 A single algorithm performing the function of A3 and A8.
A5 Stream cipher algorithm, residing on an MS, that produces
ciphertext out of plaintext, using Kc.
A8 Ciphering key generating algorithm that produces Kc using
RAND and Ki.
AB Access Burst.
Abis interface Interface between a remote BSC and BTS. Motorola offers a
GSM standard and a unique Motorola Abis interface. The
Motorola interface reduces the amount of message traffic and
thus the number of 2 Mbit/s lines required between BSC and
BTS.
ABR Answer Bid Ratio.
acdc PSM ACDC Power Supply module.
ac Alternating Current.
AC Access Class (C0 to C15).
AC Application Context.
ACC Automatic Congestion Control.
ACCH Associated Control CHannel.
ACK, Ack ACKnowledgement.
ACM Accumulated Call meter.
ACM Address Complete Message.
ACPIM AC Power Interface Module. Used in M-Cell6 indor ac BTS
equipment.
AC PSM AC Power Supply Module. Used in M-Cell6 BTS equipment.
ACSE Associated Control Service Element.
ACU Antenna Combining Unit.
A/D Analogue to Digital (converter).
ADC ADministration Centre.
ADC Analogue to Digital Converter.
ADCCP ADvanced Communications Control Protocol.
ADM ADMinistration processor.
ADMIN ADMINistration.
ADN Abbreviated Dialling Number.
ADPCM Adaptive Differential Pulse Code Modulation.
AE Application Entity.
AEC Accoustic Echo Control.
AEF Additional Elementary Functions.

Version 1 Rev 1 A
AET Active Events Table. Alarms and events are sent to the
Events Log in the GUI. Different operators will have different
subscription lists. All alarms and events are sent to the AET
before they are re-routed to different subscription lists.
AFC Automatic Frequency Control.
AFN Absolute Frame Number.
AGC Automatic Gain Control.
AGCH Access Grant CHannel. A GSM common control channel
used to assign MS to a SDCCH or a TCH.
Ai Action indicator.
AI Artificial Intelligence.
AIB Alarm Interface Board.
AIO A class of processor.
Air interface The radio link between the BTS and the MS.
AM Amplitude Modulation.
AMA Automatic Message Accounting (processor).
AM/MP Cell broadcast mobile terminated message. A message
broadcast to all MSs in a cell.
AoC Advice of Change.
AoCC Advice of Change Charging supplementary service.
AoCI Advice of Change Information supplementary service.
AOC Automatic Output Control.
AP Application Process.
ARFCN Absolute Radio Frequency Channel Number. An integer
which defines the absolute RF channel number.
ARQ Automatic ReQuest for retransmission.
ARP Address Resolution Protocol.
ASCE Association Control Service Element. An ASE which
provides an AP with the means to establish and control an
association with an AP in a remote NE. Maps directly onto
the Presentation layer (OMC).
ASE Application Service Element (OMC)
ASE Application Specific Entity (TCAP).
ASN.1 Abstract Syntax Notation One.
ASP Alarm and Status Panel.
ASR Answer Seizure Ratio.
ATB All Trunks Busy.
ATI Antenna Transceiver Interface.
ATT (flag) ATTach.
ATTS Automatic Trunk Testing Subsystem.
AU Access Unit.
AuC Authentication Centre. A GSM network entity which provides
the functionality for verifying the identity of an MS when
requested by the system. Often a part of the HLR.

A Version 1 Rev 1
AUT(H) AUThentication.
AUTO AUTOmatic mode.

Version 1 Rev 1 B
B Interface Interface between MSC and VLR.

BA BCCH Allocation. The radio frequency channels allocated in a
cell for BCCH transmission.
BAIC Barring of All Incoming Calls supplementary service.
BAOC Barring of All Outgoing Calls supplementary service.
BBBX Battery Backup Board.
BBH Base Band Hopping.
BCC BTS Colour Code.
BCCH Broadcast Control CHannel. A GSM control channel used to
broadcast general information about a BTS site on a per cell
or sector basis.
BCD Binary Coded Decimal.
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 Bearer Capability Information Element.
BCU Base station Control Unit. A functional entity of the BSS
which provides the base control function at a BTS site. The
term no longer applies to a type of shelf (see BSC and BSU).
BCUP Base Controller Unit Power.
BER Bit Error Rate. A measure of signal quality in the GSM
system.
BES Business Exchange Services.
BFI Bad Frame Indication.
BHCA Busy Hour Call Attempt.
BI all Barring of All Incoming call supplementary service.
BIB Balanced-line Interconnect Board. Provides interface to 12
balanced (6-pair) 120 ohm (37-pin D-type connector) lines for
2 Mbit/s circuits (See also T43).
BICRoam Barring of All Incoming Calls when Roaming outside the
Home PLMN Country supplementary service.
BIM Balanced-line Interconnect Module.
Bin An area in a data array used to store information.
BL BootLoad. Also known as download. For example, databases
and software can be downloaded to the NEs from the BSS.
BLLNG BiLLiNG.
bit/s Bits per second (bps).
Bm Full rate traffic channel.
BN Bit Number. Number which identifies the position of a
particular bit period within a timeslot.
BPF Bandpass Filter.
BPSM BCU Power Supply Module.

B Version 1 Rev 1
BS Basic Service (group).

BS Bearer Service. A type of telecommunication service that
provides the capability for the transmission of signals
between user-network interfaces. The PLMN connection type
used to support a bearer service may be identical to that used
to support other types of telecommunication service.
BSC Base Station Controller. A network component in the GSM
PLMN which has the digital control function of controlling all
BTSs. The BSC can be located within a single BTS cabinet
(forming a BSS) but is more often located remotely and
controls several BTSs (see BCF, BCU, and BSU).
BSG Basic Service Group.
BSIC Base Transceiver Station Identity Code. A block of code,
consisting of the GSM PLMN colour code and a base station
colour code. One Base Station can have several Base
Station Colour Codes.
BSIC-NCELL BSIC of an adjacent cell.
BSP Base Site control Processor (at BSC).
BSN Backward Sequence Number.
BSS Base Station System. The system of base station equipment
(Transceivers, controllers and so on) which is viewed by the
MSC through a single interface as defined by the GSM 08
series of recommendations, as being the entity responsible
for communicating with MSs in a certain area. The radio
equipment of a BSS may cover one or more cells. A BSS
may consist of one or more base stations. If an internal
interface is implemented according to the GSM 08.5x series
of recommendations, then the BSS consists of one BSC and
several BTSs.
BSSAP BSS Application Part (of Signalling System No. 7) (DTAP +
BSSMAP).
BSSC Base Station System Control cabinet. The cabinet which
houses one or two BSU shelves at a BSC or one or two RXU
shelves at a remote transcoder.
BSSMAP Base Station System Management Application Part (6-8).
BSSOMAP BSS Operation and Maintenance Application Part (of
Signalling System No. 7).
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 Bus Terminator Card.
BTF Base Transceiver Function.
BTP Base Transceiver Processor (at BTS). One of the six basic
task groups within the GPROC.

Version 1 Rev 1 B
BTS Base Transceiver Station. A network component in the GSM

PLMN which serves one cell, and is controlled by a BSC.
The BTS contains one or more Transceivers (TRXs).
Burst A period of modulated carrier less than one timeslot. The
physical content of a timeslot.

C Version 1 Rev 1
C
C Conditional.
C Interface Interface between MSC and HLR/AUC.
C7 ITU-TSS Signalling System 7 (sometimes referred to as S7 or
SS#7).
CA Cell Allocation. The radio frequency channels allocated to a
particular cell.
CA Central Authority.
CAB Cabinet.
CADM Country ADMinistration. The Motorola procedure used within
DataGen to create new country and network files in the
DataGen database.
CAI Charge Advice Information.
CAT Cell Analysis Tool.
CB Cell Broadcast.
CB Circuit Breaker.
CBC Cell Broadcast Centre.
CBCH Cell Broadcast CHannel.
CBF Combining Bandpass Filter.
CBL Cell Broadcast Link.
CBM Circuit Breaker Module.
CBMI Cell Broadcast Message Identifier.
CBSMS Cell Broadcast Short Message Service.
CBUS Clock Bus.
CC Connection Confirm (Part of SCCP network connectivity).
CC Country Code.
CC Call Control.
CCB Cavity Combining Block, a three way RF combiner. There
are two types of CCB, CCB (Output) and CCB (Extension).
These, with up to two CCB Control cards, may comprise the
TATI. The second card may be used for redundancy.
CCBS Completion of Calls to Busy Subscriber supplementary
service.
CCCH Common Control CHannels. A class of GSM control
channels used to control paging and grant access. Includes
AGCH, PCH, and RACH.
CCCH_GROUP Group of MSs in idle mode.
CCD Common Channel Distributor.
CCDSP Channel Coding Digital Signal Processor.
CCF Conditional Call Forwarding.
CCH Control CHannel. Control channels are channels which carry
system management messages.
CCH Council for Communications Harmonization (referred to in
GSM Recommendations).

Version 1 Rev 1 C
CCIT Comit Consultatif International Tlgraphique et

Tlphonique. This term has been superceded by ITUTSS
(International Telecommunications Union
Telecommunications Sector).
CCM Current Call Meter.
CCP Capability/Configuration Parameter.
CCPE Control Channel Protocol Entity.
CCS Hundred call-seconds. The unit in which amounts of
telephone traffic are measured. A single call lasting one
hundred seconds is one CCS. See also erlang.
Cct Circuit.
CDB Control Driver Board.
CDE Common Desktop Environment. Part of the SUN software
(crontab cron job file).
CDR Call Detail Records.
CDUR Chargeable DURation.
CEB Control Equalizer Board (BTS).
CED Called station identifier.
CEIR Central Equipment Identity Register.
Cell By GSM definition, a cell is an RF coverage area. At an
omni-site, cell is synonymous with site; at a sectored site, cell
is synonymous with sector. This differs from analogue
systems where cell is taken to mean the same thing as site.
(See below).
1 Cell =
1 Sector
Omni Site 6-Sector Site

1-Cell Site or
(1 BTS) 6-Cell Site
(6 BTSs)
CEND End of charge point.

CEPT Confrence des administrations Europennes des Postes et
Telecommunications.
CERM Circuit Error Rate Monitor.
CF Conversion Facility.
CF all Call Forwarding services.
CFB Call Forwarding on mobile subscriber Busy supplementary
service.
CFC Conditional Call Forward.
CFNRc Call Forwarding on mobile subscriber Not Reachable
supplementary service.
CFNRy Call Forwarding on No Reply supplementary service.

C Version 1 Rev 1
CFU Call Forwarding Unconditional supplementary service.

Channel A means of one-way transmission. A defined sequence of
periods (for example, timeslots) in a TDMA system; a defined
frequency band in an FDMA system; a defined sequence of
periods and frequency bands in a frequency hopped system.
CIM Coaxial Interconnect Module.
CHP CHarging Point.
CHV Card Holder Verification information.
CKSN Ciphering Key Sequence Number.
CI Cell Identity. A block of code which identifies a cell within a
location area.
CI CUG Index.
CIC Circuit Identity Code.
CIR, C/I Carrier to Interference Ratio.
Ciphertext Unintelligible data produced through the use of encipherment.
CKSN Ciphering Key Sequence Number.
CLI Calling Line Identity.
CLIP Calling Line Identification Presentation supplementary
service.
CLIR Calling Line Identification Restriction supplementary service.
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 Configuration Management. An OMC application.
CM Connection Management.
CMD CoMmanD.
CMM Channel Mode Modify.
CMIP Common Management Information Protocol.
CMISE Common Management Information Service Element. An ASE
which provides a means to transfer management information
via CMIP messages with another NE over an association
established by ASCE using ROSE (OMC).
CMR Cellular Manual Revision.
CNG CalliNg tone.
COLI COnnected Line Identity.
Collocated Placed together; two or more items together in the same
place.
Coincident Cell A cell which has a co-located neighbour whose cell boundary
follows the boundary of the said cell. The coincident cell has
a different frequency type, but the same BSIC, as that of the
neighbour cell.
COLP COnnected Line Identification Presentation supplementary
service.

Version 1 Rev 1 C
COLR COnnected Line Identification Restriction supplementary

service.
CODEX Manufacturers name for a type of multiplexer and packet
switch commonly installed at the Motorola OMC-R.
COM Code Object Manager.
COM COMplete.
COMB Combiner.
CONNACK CONNect ACKnowledgement.
COMM, Comms COMMunications.
CommsLink Communications Link. (2Mbit/s)
CONF CONFerence circuit.
CONFIG CONFIGuration Control Program.
CP Call Processing.
CPU Central Processing Unit.
C/R Command/Response field bit.
CR Carriage Return (RETURN).
CR Connection Request (Part of SCCP network connectivity).
CRC Cyclic Redundancy Check (3 bit).
CRE Call RE-establishment procedure.
CREF Connection REFused (Part of SCCP network connectivity).
CRM Cell Resource Manager.
CRM-LS/HS Cellular Radio Modem-Low Speed/High Speed. Low speed
modem used to interwork 300 to 2400 bit/s data services
under V.22bis, V.23, or V.21 standards. High speed modem
used to interwork 1200 to 9600 bit/s data services under
V.22bis, V.32, or V.29/V.27ter/V.21 standards.
CRT Cathode Ray Tube (video display terminal).
CSFP Code Storage Facility Processor (at BSC and BTS).
CSP Central Statistics Process. The statistics process in the BSC.
CSPDN Circuit Switched Public Data Network.
CT Call Transfer supplementary service.
CT Channel Tester.
CT Channel Type.
CTP Call Trace Product (Tool).
CTR Common Technical Regulation.
CTS Clear to Send. Method of flow control (RS232 Interface).
CTU Compact Transceiver Unit (M-Cellhorizon radio).
CUG Closed User Group supplementary service.
Cumulative value The total value for an entire statistical interval.
CW Call Waiting supplementary service.

D Version 1 Rev 1
D
D Interface Interface between VLR and HLR.
D/A Digital to Analogue (converter).
DAB Disribution Alarm Board.
DAC Digital to Analogue Converter.
DACS Digital Access Cross-connect System.
DAN Digital ANnouncer (for recorded announcements on MSC).
DAS Data Acquisition System.
DAT Digital Audio Tape.
DataGen Sysgen Builder System. A Motorola offline BSS binary object
configuration tool.
dB Decibel. A unit of power ratio measurement.
DB DataBase.
DB Dummy Burst (see Dummy burst).
DBA DataBase Administration/Database Administrator.
DBMS DataBase Management System.
dc Direct Current.
DCB Diversity Control Board (p/o DRCU).
DCCH Dedicated Control CHannel. A class of GSM control
channels used to set up calls and report measurements.
Includes SDCCH, FACCH, and SACCH.
DCD Data Carrier Detect signal.
DCE Data Circuit terminating Equipment.
DCF Data Communications Function.
DCF Duplexed Combining bandpass Filter. (Used in
Horizonmacro).
DCN Data Communications Network. A DCN connects Network
Elements with internal mediation functions or mediation
devices to the Operations Systems.
DC PSM DC Power Supply Module.
DCS1800 Digital Cellular System at 1800 MHz. A cellular phone
network using digital techniques similar to those used in GSM
900, but operating on frequencies of 1710 1785 MHz and
1805 1880 MHz.
DDF Dual-stage Duplexed combining Filter. (Used in
Horizonmacro).
DDS DataGen Directory Structure.
DDS Data Drive Storage.
DDS Direct Digital Synthesis.
DEQB Diversity Equalizer Board.
DET DETach.
DFE Decision Feedback Equalizer.
DGT Data Gathering Tool.

Version 1 Rev 1 D
DHP Digital Host Processor.

DIA Drum Intercept Announcer.
DINO E1/HDSL Line termination module.
DINO T1 Line termination module.
DISC DISConnect.
Discon Discontiuous.
DIQ Diversity In phase and Quadrature phase.
DIR Device Interface Routine.
DL Data Link (layer).
DLCI Data Link Connection Identifier.
DLD Data Link Discriminator.
DLNB Diversity Low Noise Block.
DLSP Data Link Service Process.
DLSP Digital Link Signalling Processor.
Dm Control channel (ISDN terminology applied to mobile service).
DMA Deferred Maintenance Alarm. An alarm report level; an
immediate or deferred response is required (see also PMA).
DMA Direct Memory Access.
DMR Digital Mobile Radio.
DMX Distributed Electronic Mobile Exchange (Motorolas
networked EMX family).
DN Directory Number.
DNIC Data network identifier.
Downlink Physical link from the BTS towards the MS (BTS transmits,
MS receives).
DP Dial/Dialled Pulse.
DPC Destination Point Code. A part of the label in a signalling
message that uniquely identifies, in a signalling network, the
(signalling) destination point of the message.
DPC Digital Processing and Control board.
DPNSS Digital Private Network Signalling System (BT standard for
PABX interface).
DPP Dual Path Preselector.
DPR, DPRAM Dual Port Random Access Memory.
DPSM Digital Power Supply Module.
DRAM Dynamic Random Access Memory.
DRC Data Rate Converter board. Provides data and protocol
conversion between PLMN and destination network for 8
circuits (p/o IWF).
DRCU Diversity Radio Channel Unit. Contains transceiver, digital
control circuits, and power supply (p/o BSS) (see RCU).
(D)RCU Generic term for radio channel unit. May be standard RCU or
diversity radio channel unit DRCU.

D Version 1 Rev 1
DRI Digital Radio Interface. Provides encoding/decoding and

encryption/decryption for radio channel (p/o BSS).
DRIM Digital Radio Interface extended Memory. A DRI with extra
memory.
DRIX DRI Extender half size board. Fibre optic link from DRI to
BCU (p/o BSS).
DRX, DRx Discontinuous reception (mechanism). A means of saving
battery power (for example in hand-portable units) by
periodically and automatically switching the MS receiver on
and off.
DS-2 German term for 2 Mbit/s line (PCM interface).
DSE Data Switching Exchange.
DSI Digital Speech Interpolation.
DSP Digital Signal Processor.
DSS1 Digital Subscriber Signalling No 1.
DSSI Diversity Signal Strength Indication.
DTAP Direct Transfer Application Part (6-8).
DTE Data Terminal Equipment.
DTF Digital Trunk Frame.
DT1 DaTa form 1 (Part of SCCP network connectivity).
DTI Digital Trunk Interface.
DTMF Dual Tone Multi-Frequency (tone signalling type).
DTR Data Terminal Ready signal. Method of flow control (RS232
Interface).
DTRX Dual Transceiver Module. (Radio used in M-Cellarena and
M-Cellarena macro).
DTX, DTx Discontinuous Transmission (mechanism). A means of
saving battery power (for example in hand-portable units) and
reducing interference by automatically switching the
transmitter off when no speech or data are to be sent.
Dummy burst A period of carrier less than one timeslot whose modulation is
a defined sequence that carries no useful information. A
dummy burst fills a timeslot with an RF signal when no
information is to be delivered to a channel.
DYNET DYnamic NETwork. Used to specify BTSs sharing dynamic
resources.

Version 1 Rev 1 E
E
E See Erlang.
E Interface Interface between MSC and MSC.
EA External Alarms.
EAS External Alarm System.
Eb/No Energy per Bit/Noise floor.
EBCG Elementary Basic Service Group.
EC Echo Canceller. Performs echo suppression for all voice
circuits.
ECB Provides echo cancelling for telephone trunks for 30 channels
(EC).
ECID The Motorola European Cellular Infrastructure Division.
ECM Error Correction Mode (facsimile).
Ec/No Ratio of energy per modulating bit to the noise spectral
density.
ECT Event Counting Tool.
ECT Explicit Call Transfer supplementary service.
EEL Electric Echo Loss.
EEPROM Electrically Erasable Programmable Read Only Memory.
EGSM900 Extended GSM900.
EI Events Interface. Part of the OMC-R GUI.
EIR Equipment Identity Register.
EIRP Effective Isotropic Radiated Power.
EIRP Equipment Identity Register Procedure.
EL Echo Loss.
EM Event Management. An OMC application.
EMC ElectroMagnetic Compatibility.
EMF Electro Motive Force.
EMI Electro Magnetic Interference.
eMLPP enhanced Multi-Level Precedence and Pre-emption service.
EMMI Electrical Man Machine Interface.
EMU Exchange office Management Unit (p/o Horizonoffice)
EMX Electronic Mobile Exchange (Motorolas MSC family).
en bloc Fr. all at once (a CCITT #7 Digital Transmission scheme);
En bloc sending means that digits are sent from one system
to another ~ (that is, all the digits for a given call are sent at
the same time as a group). ~ sending is the opposite of
overlap sending. A system using ~ sending will wait until it
has collected all the digits for a given call before it attempts to
send digits to the next system. All the digits are then sent as
a group.
EOT End of Tape.
EPROM Erasable Programmable Read Only Memory.

E Version 1 Rev 1
EPSM Enhanced Power Supply Module (+27 V).

EQB Equalizer Board. Control circuit for equalization for 8 time
slots each with equalizing circuitry and a DSP (p/o RCU).
EQCP Equalizer Control Processor.
EQ DSP Equalizer Digitizer Signal Processor.
Erlang International (dimensionless) unit of traffic intensity defined as
the ratio of time a facility is occupied to the time it is available
for occupancy. One erlang is equal to 36 CCS. In the US
this is also known as a traffic unit (TU).
ERP Ear Reference Point.
ERP Effective Radiated Power.
ERR ERRor.
ESP Electro-static Point.
ESQL Embedded SQL (Structured Query Language). An RDBMS
programming interface language.
E-TACS Extended TACS (analogue cellular system, extended).
Ethernet Type of Local Area Network.
ETR ETSI Technical Report.
ETS European Telecommunication Standard.
ETSI European Telecommunications Standards Institute.
ETX End of Transmission.
EXEC Executive Process.

Version 1 Rev 1 F
F Interface Interface between MSC and EIR.

FA Fax Adaptor.
FA Full Allocation.
FA Functional Area.
FAC Final Assembly Code.
FACCH Fast Associated Control Channel. A GSM dedicated control
channel which is associated with a TCH and carries control
information after a call is set up (see SDCCH).
FACCH/F Fast Associated Control Channel/Full rate.
FACCH/H Fast Associated Control Channel/Half rate.
FB Frequency correction Burst (see Frequency correction burst).
FC-AL Fibre Channel Arbitration Loop. (Type of hard disc).
FCCH Frequency Correction CHannel. A GSM broadcast control
channel which carries information for frequency correction of
the mobile (MS).
FCP Fault Collection Process (in BTS).
FCS Frame Check Sequence.
FDM Frequency Division Multiplex.
FDMA Frequency Division Multiple Access.
FDN Fixed Dialling Number.
FDP Fault Diagnostic Procedure.
FEC Forward Error Correction.
FEP Front End Processor.
FER Frame Erasure Ratio.
FFS, FS For Further Study.
FH Frequency Hopping.
FIB Forward Indicator Bit.
FIR Finite Impulse Response (filter type).
FK Foreign Key. A database column attribute; the foreign key
indicates an index into another table.
FM Fault Management (at OMC).
FM Frequency Modulation.
FMIC Fault Management Initiated Clear.
FMUX Fibre optic MUltipleXer.
FN Frame Number. Identifies the position of a particular TDMA
frame within a hyperframe.
FOA First Office Application.
FOX Fibre Optic eXtender.
FR Full Rate. Refers to the current capacity of a data channel on
the GSM air interface, that is, 8 simultaneous calls per carrier
(see also HR Half Rate).

F Version 1 Rev 1
FRU Field Replaceable Unit.

Frequency correction Period of RF carrier less than one timeslot whose modulation
bit stream allows frequency correction to be performed easily
within an MS burst.
FS Frequency Synchronization.
FSL Free Space Loss. The decrease in the strength of a radio
signal as it travels between a transmitter and receiver. The
FSL is a function of the frequency of the radio signal and the
distance the radio signal has travelled from the point source.
FSN Forward Sequence Number.
FTAM File Transfer, Access, and Management. An ASE which
provides a means to transfer information from file to file
(OMC).
ftn forwarded-to number.
FTP Fault Translation Process (in BTS).
FTP File Transfer Protocol.

Version 1 Rev 1 G
G
G Interface Interface between VLR and VLR.
Gateway MSC An MSC that provides an entry point into the GSM PLMN
from another network or service. A gateway MSC is also an
interrogating node for incoming PLMN calls.
GB, Gbyte Gigabyte.
GBIC Gigabit Interface Converter.
GCLK Generic Clock board. System clock source, one per site (p/o
BSS, BTS, BSC, IWF, RXCDR).
GCR Group Call Register.
GDP Generic DSP Processor board. Interchangeable with the XCDR
board.
GDP E1 GDP board configured for E1 link usage.
GDP T1 GDP board configured for T1 link usage.
GHz Giga-Hertz (109).
GID Group ID. A unique number used by the system to identify a
users primary group.
GMB GSM Multiplexer Board (p/o BSC).
GMR GSM Manual Revision.
GMSC Gateway Mobile-services Switching Centre (see Gateway
MSC).
GMSK Gaussian Minimum Shift Keying. The modulation technique
used in GSM.
GND GrouND.
GOS Grade of Service.
GPA GSM PLMN Area.
GPC General Protocol Converter.
GPROC Generic Processor board. GSM generic processor board: a
68030 with 4 to 16 Mb RAM (p/o BSS, BTS, BSC, IWF,
RXCDR).
GPROC2 Generic Processor board. GSM generic processor board: a
68040 with 32 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR).
GPRS General Packet Radio Service.
GPS Global Positioning by Satellite.
GSA GSM Service Area. The area in which an MS can be reached
by a fixed subscriber, without the subscribers knowledge of
the location of the MS. A GSA may include the areas served
by several GSM PLMNs.
GSA GSM System Area. The group of GSM PLMN areas
accessible by GSM MSs.
GSM Groupe Spcial Mobile (the committee).
GSM Global System for Mobile communications (the system).
GSM MS GSM Mobile Station.
GSM PLMN GSM Public Land Mobile Network.

G Version 1 Rev 1
GSR GSM Software Release.

GT Global Title.
GTE Generic Table Editor. The Motorola procedure which allows
users to display and edit MCDF input files.
Guard period Period at the beginning and end of timeslot during which MS
transmission is attenuated.
GUI Graphical User Interface.
GUI client A computer used to display a GUI from an OMC-R GUI
application which is beingbrun on a GUI server.
GUI server A computer used to serve the OMC-R GUI application
process running locally (on its processor) to other computers
(Gui clients or other MMI processors).
GWY GateWaY (MSC/LR) interface to PSTN.

Version 1 Rev 1 H
H
H Interface Interface between HLR and AUC.
H-M Human-Machine Terminals.
HAD, HAP HLR Authentication Distributor.
HANDO, Handover HANDOver. The action of switching a call in progress from
one radio channel to another radio channel. Handover allows
established calls to continue by switching them to another
radio resource, as when an MS moves from one BTS area to
another. Handovers may take place between the following
GSM entities: timeslot, RF carrier, cell, BTS, BSS and MSC.
HCU Hybrid Combining Unit. (Used in Horizonmacro).
HDLC High level Data Link Control.
HDSL High bit-rate Digital Subscriber Line.
HLC High Layer Compatibility. The HLC can carry information
defining the higher layer characteristics of a teleservice active
on the terminal.
HLR Home Location Register. The LR where the current location
and all subscriber parameters of an MS are permanently
stored.
HMS Heat Management System. The system that provides
environmental control of the components inside the ExCell,
TopCell and M-Cell cabinets.
HO HandOver. (see HANDO above).
HPU Hand Portable Unit.
HOLD Call hold supplementary service.
HPLMN Home PLMN.
HR Half Rate. Refers to a type of data channel that will double
the current GSM air interface capacity to 16 simultaneous
calls per carrier (see also FR Full Rate).
HS HandSet.
HSI/S High Speed Interface card.
HSM HLR Subscriber Management.
HSN Hopping Sequence Number.
HU Home Units.
HW Hardware.
Hyperframe 2048 superframes. The longest recurrent time period of the
frame structure.

I Version 1 Rev 1
I Information frames (RLP).

IA Incomming Access (closed user group (CUG) SS
(supplementary service)).
IA5 International Alphanumeric 5.
IADU Integrated Antenna Distribution Unit. (The IADU is the
equivalent of the Receive Matrix used on pre-M-Cell BTSs).
IAM Initial Address Message.
IAS Internal Alarm System.
IC Integrated Circuit.
IC Interlock Code (CUG SS).
IC(pref) Interlock Code op the preferential CUG.
ICB Incoming Calls Barred.
ICC Integrated Circuit(s) Card.
ICM In-Call Modification.
ICMP Internet Control Message Protocol.
ID, Id IDentification/IDentity/IDentifier.
IDN Integrated Digital Network.
IDS INFOMIX Database Server. (OMC-R relational database
management system).
IE Information Element (signalling).
IEC International Electrotechnical Commission.
IEEE Institute of Electrical and Electronic Engineers.
IEI Information Element Identifier.
I-ETS Interim European Telecommunication Standard.
IF Intermediate Frequency.
IFAM Initial and Final Address Message.
IM InterModulation.
IMACS Intelligent Monitor And Control System.
IMEI International Mobile station Equipment Identity. Electronic
serial number that uniquely identifies the MS as a piece or
assembly of equipment. The IMEI is sent by the MS along
with request for service.
IMM IMMediate assignment message.
IMSI International Mobile Subscriber Identity. Published mobile
number (prior to ISDN) (see also MSISDN) that uniquely
identifies the subscription. It can serve as a key to derive
subscriber information such as directory number(s) from the
HLR.
IN Intelligent Network.
IN Interrogating Node. A switching node that interrogates an
HLR, to route a call for an MS to the visited MSC.
INS IN Service.

Version 1 Rev 1 I
INS Intelligent Network Service.

InterAlg Interference Algorithm. A single interference algorithm in a
cell.
Interworking The general term used to describe the inter-operation of
networks, services, supplementary services and so on. See
also IWF.
Interval A recording period of time in which a statistic is pegged.
Interval expiry The end of an interval.
I/O Input/Output.
IOS Intelligent Optimization Platform.
IP Initialisation Process.
IP Internet Protocol.
IPC Inter-Process Communication.
IP, INP INtermodulation Products.
IPR Intellectual PRoperty.
IPSM Integrated Power Supply Module (48 V).
IPX (A hardware component).
ISAM Indexed Sequential Access Method.
ISC International Switching Centre.
ISDN Integrated Services Digital Network. An integrated services
network that provides digital connections between
user-network interfaces.
ISG Motorola Information Systems group (formally CODEX).
ISO International Organisation for Standardization.
ISQL Informix Structured Query Language.
ISUP ISDN User Part (of signalling system No. 7).
IT Inactivity Test (Part of SCCP network connectivity).
ITC Information Transfer Capability.
ITU International Telecommunication Union.
ITUTSS International Telecommunication Union Telecommunications
Sector.
IWF InterWorking Function. A network functional entity which
provides network interworking, service interworking,
supplementary service interworking or signalling interworking.
It may be a part of one or more logical or physical entities in a
GSM PLMN.
IWMSC InterWorking MSC.
IWU InterWorking Unit.

K Version 1 Rev 1
K
k kilo (103).
k Windows size.
K Constraint length of the convolutional code.
KAIO Kernal Asynchronous Input/Output.
kb, kbit kilo-bit.
kbit/s, kbps kilo-bits per second.
kbyte kilobyte.
Kc Ciphering key. A sequence of symbols that controls the
operation of encipherment and decipherment.
kHz kilo-Hertz (103).
Ki Individual subscriber authentication Key (p/o authentication
process of AUC).
KIO A class of processor.
KSW Kiloport SWitch board. TDM timeslot interchanger to connect
calls (p/o BSS).
KSWX KSW Expander half size board. Fibre optic distribution of
TDM bus (p/o BSS).
kW kilo-Watt.

Version 1 Rev 1 L
L
L1 Layer 1.
L2ML Layer 2 Management Link.
L2R Layer 2 Relay function. A function of an MS and IWF that
adapts a users known layer2 protocol LAPB onto RLP for
transmission between the MT and IWF.
L2R BOP L2R Bit Orientated Protocol.
L2R COP L2R Character Orientated Protocol.
L3 Layer 3.
LA Location Area. An area in which an MS may move freely
without updating the location register. An LA may comprise
one or several base station areas.
LAC Location Area Code.
LAI Location Area Identity. The information indicating the location
area in which a cell is located.
LAN Local Area Network.
LANX LAN Extender half size board. Fibre optic distribution of LAN
to/from other cabinets (p/o BSS etc).
LAPB Link Access Protocol Balanced (of ITUTSS Rec. x.25).
LAPD Link Access Protocol Data.
LAPDm Link Access Protocol on the Dm channel.
LC Inductor Capacitor (type of filter).
LCF Link Control Function.
LCN Local Communications Network.
LCP Link Control Processor.
LE Local Exchange.
LED Light Emitting Diode.
LF Line Feed.
LI Length Indicator.
LI Line Identity.
LLC Lower Layer Compatibility. The LLC can carry information
defining the lower layer characteristics of the terminal.
Lm Traffic channel with capacity lower than a Bm.
LMP LAN Monitor Process.
LMS Least Mean Square.
LMSI Local Mobile Station Identity. A unique identity temporarily
allocated to visiting mobile subscribers in order to speed up
the search for subscriber data in the VLR, when the MSRN
allocation is done on a per cell basis.
LMT Local Maintenance Terminal.
LNA Low Noise Amplifier.
LND Last Number Dialled.

L Version 1 Rev 1
Location area An area in which a mobile station may move freely without
updating the location register. A location area may comprise
one or several base station areas.
LPC Linear Predictive Code.
LPLMN Local PLMN.
LR Location Register. The GSM functional unit where MS
location information is stored. The HLR and VLR are location
registers.
LSSU Link Stations Signalling Unit (Part of MTP transport system).
LSTR Listener Side Tone Rating.
LTA Long Term Average. The value required in a BTSs GCLK
frequency register to produce a 16.384 MHz clock.
LTE Local Terminal Emulator.
LTP Long Term Predictive.
LTU Line Terminating Unit.
LU Local Units.
LU Location Update.
LV Length and Value.

Version 1 Rev 1 M
M
M Mandatory.
M Mega (106).
M-Cell Motorola Cell.
M&TS Maintenance and Troubleshooting. Functional area of
Network Management software which (1) collects and
displays alarms, (2) collects and displays Software/Hardware
errors, and (3) activates test diagnostics at the NEs (OMC).
MA Mobile Allocation. The radio frequency channels allocated to
an MS for use in its frequency hopping sequence.
MAC Medium Access Control.
MACN Mobile Allocation Channel Number.
Macrocell A cell in which the base station antenna is generally mounted
away from buildings or above rooftop level.
MAF Mobile Additional Function.
MAH Mobile Access Hunting supplementary service.
MAI Mobile Allocation Index.
MAIDT Mean Accumulated Intrinsic Down Time.
MAINT MAINTenance.
MAIO Mobile Allocation Index Offset.
MAP Mobile Application Part (of signalling system No. 7). The
inter-networking signalling between MSCs and LRs and EIRs.
MAPP Mobile Application Part Processor.
MB, Mbyte Megabyte.
Mbit/s Megabits per second.
MCAP Motorola Cellular Advanced Processor.
MCC Mobile Country Code.
MCDF Motorola Customer Data Format used by DataGen for simple
data entry and retrieval.
MCI Malicious Call Identification supplementary service.
MCSC Motorola Customer Support Centre.
MCU Main Control Unit for M-Cell2/6. Also referred to as the Micro
Control Unit in software.
MCUF Main Control Unit, with dual FMUX. (Used in M-Cellhorizon).
MCU-m Main Control Unit for M-Cell Micro sites (M-Cellm). Also
referred to as the Micro Control Unit in software.
MCUm The software subtype representation of the Field Replaceable
Unit (FRU) for the MCU-m.
MD Mediation Device.
MDL (mobile) Management (entity) - Data Link (layer).
ME Maintenance Entity (GSM Rec. 12.00).

M Version 1 Rev 1
ME Mobile Equipment. Equipment intended to access a set of

GSM PLMN and/or DCS telecommunication services, but
which does not contain subscriber related information.
Services may be accessed while the equipment, capable of
surface movement within the GSM system area, is in motion
or during halts at unspecified points.
MEF Maintenance Entity Function (GSM Rec. 12.00).
MF MultiFrame.
MF Multi-Frequency (tone signalling type).
MF MultiFunction block.
MGMT, mgmt Management.
MGR Manager.
MHS Message Handling System.
MHS Mobile Handling Service.
MHz Mega-Hertz (106).
MI Maintenance Information.
MIB Management Information Base. A Motorola OMC-R
database. There is a CM MIB and an EM MIB.
MIC Mobile Interface Controller.
Microcell A cell in which the base station antenna is generally mounted
below rooftop level. Radio wave propagation is by diffraction
and scattering around buildings, the main propagation is
within street canyons.
min minute(s).
s micro-second (106).
BCU Micro Base Control Unit.
MIT Management Information Tree. Name of a file on the
Motorola OMC-R.
MM Man Machine.
MM Mobility Management.
MME Mobile Management Entity.
MMF Middle Man Funnel process.
MMI Man Machine Interface. The method in which the user
interfaces with the software to request a function or change
parameters.
MMI client A machine configured to use the OMC-R software from an
MMI server.
MMI processor MMI client/MMI server.
MMI server A computer which has its own local copy of the OMC-R
software. It can run the OMC-R software for MMI clients to
mount.
MML Man Machine Language. The tool of MMI.
MMS Multiple Serial Interface Link. (see also 2Mbit/s link)
MNC Mobile Network Code.
MNT MaiNTenance.

Version 1 Rev 1 M
MO Mobile Originated.
MO/PP Mobile Originated Point-to-Point messages.
MOMAP Motorola OMAP.
MoU Memorandum of Understanding.
MPC Multi Personal Computer (was p/o OMC).
MPH (mobile) Management (entity) - PHysical (layer) [primitive].
MPTY MultiParTY (Multi ParTY) supplementary service.
MPX MultiPleXed.
MRC Micro Radio Control Unit.
MRN Mobile Roaming Number.
MRP Mouth Reference Point.
MS Mobile Station. The GSM subscriber unit.
MSC Mobile-services Switching Centre, Mobile Switching Centre.
MSCM Mobile Station Class Mark.
MSCU Mobile Station Control Unit.
msec millisecond (.001 second).
MSI Multiple Serial Interface board. Intelligent interface to two
2 Mbit/s digital links (see 2 Mbit/s link and DS-2) (p/o BSS).
MSIN Mobile Station Identification Number.
MSISDN Mobile Station International ISDN Number. Published mobile
number (see also IMSI). Uniquely defines the mobile station
as an ISDN terminal. It consists of three parts: the Country
Code (CC), the National Destination Code (NDC) and the
Subscriber Number (SN).
MSRN Mobile Station Roaming Number. A number assigned by the
MSC to service and track a visiting subscriber.
MSU Message Signal Unit (Part of MTP transport system). A
signal unit containing a service information octet and a
signalling information field which is retransmitted by the
signalling link control, if it is received in error.
MT Mobile Terminated. Describes a call or short message
destined for an MS.
MT (0, 1, 2) Mobile Termination. The part of the MS which terminates the
radio transmission to and from the network and adapts
terminal equipment (TE) capabilities to those of the radio
transmission. MT0 is mobile termination with no support for
terminal, MT1 is mobile termination with support for an S-type
interface and MT2 is mobile termination with support for an
R-type interface.
MTM Mobile-To-Mobile (call).
MTP Message Transfer Part.
MT/PP Mobile Terminated Point-to-Point messages.
MTBF Mean Time Between Failures.
MTK Message Transfer LinK.
MTL MTP Transport Layer Link (A interface).

M Version 1 Rev 1
MTP Message Transfer Part.

MTTR Mean Time To Repair.
Multiframe Two types of multiframe are defined in the system: a
26-frame multiframe with a period of 120 ms and a 51-frame
multiframe with a period of 3060/13 ms.
MU Mark Up.
MUMS Multi User Mobile Station.
MUX Multiplexer.

Version 1 Rev 1 N
N
N/W Network.
NB Normal Burst (see Normal burst).
NBIN A parameter in the hoping sequence.
NCC Network (PLMN) Colour Code.
NCELL Neighbouring (of current serving) Cell.
NCH Notification CHannel.
ND No Duplicates. A database column attribute meaning the
column contains unique values (used only with indexed
columns).
NDC National Destination Code.
NDUB Network Determined User Busy.
NE Network Element (Network Entity).
NEF Network Element Function block.
NET Norme Europennes de Telecommunications.
NETPlan Frequency planning tool.
NF Network Function.
NFS Network File System.
NHA Network Health Analyst. Optional OMC-R processor feature.
NIC Network Interface Card.
NIC Network Independent Clocking.
NIS Network Information Service. It allows centralised control of
network information for example hostnames, IP addresses
and passwords.
NIU Network Interface Unit.
NIU-m Network Interface Unit, micro.
NLK Network LinK processor(s).
Nm Newton metres.
NM Network Management (manager). NM is all activities which
control, monitor and record the use and the performance of
resources of a telecommunications network in order to
provide telecommunication services to customers/users at a
certain level of quality.
NMASE Network Management Application Service Element.
NMC Network Management Centre. The NMC node of the GSM
TMN provides global and centralised GSM PLMN monitoring
and control, by being at the top of the TMN hierarchy and
linked to subordinate OMC nodes.
NMSI National Mobile Station Identification number.
NMT Nordic Mobile Telephone system.
NN No Nulls. A database column attribute meaning the column
must contain a value in all rows.
Normal burst A period of modulated carrier less than a timeslot.
NPI Number Plan Identifier.

N Version 1 Rev 1
NRZ Non Return to Zero.

NSAP Network Service Access Point.
NSP Network Service Provider.
NSS Network Status Summary.
NT Network Termination.
NT Non Transparent.
NTAAB New Type Approval Advisory Board.
NUA Network User Access.
NUI Network User Identification.
NUP National User Part (of signalling system No. 7).
NV NonVolatile.
NVRAM Non-Volatile Random Access Memory.
nW Nano-Watt (109).

Version 1 Rev 1 O
O
O Optional.
OA Outgoing Access (CUG SS).
O&M Operations and Maintenance.
OASCU Off-Air-Call-Set-Up. The procedure in which a
telecommunication connection is being established whilst the
RF link between the MS and the BTS is not occupied.
OCB Outgoing Calls Barred within the CUG.
OCXO Oversized Voltage Controlled Crystal Oscillator.
OD Optional for operators to implement for their aim.
OFL % OverFlow.
offline IDS shutdown state.
online IDS normal operatng state.
OIC Operator Initiated Clear.
OLM Off_Line MIB. A Motorola DataGen database, used to modify
and carry out Radio Frequency planning on multiple BSS
binary files.
OLR Overall Loudness Rating.
OMAP Operations and Maintenance Application Part (of signalling
system No. 7) (was OAMP).
OMC Operations and Maintenance Centre. The OMC node of the
GSM TMN provides dynamic O&M monitoring and control of
the PLMN nodes operating in the geographical area
controlled by the specific OMC.
OMC-G Operations and Maintenance Centre Gateway Part.
(Iridium)
OMC-G Operations and Maintenance Centre GPRS Part.
OMC-R Operations and Maintenance Centre Radio Part.
OMC-S Operations and Maintenance Centre Switch Part.
OMF Operations and Maintenance Function (at BSC).
OML Operations and Maintenance Link.
OMP Operation and Maintenance Processor.
OMS Operation and Maintenance System (BSCOMC).
OMSS Operation and Maintenance SubSystem.
OOS Out Of Service.
OPC Originating Point Code. A part of the label in a signalling
message that uniquely identifies, in a signalling network, the
(signalling) origination point of the message.
ORAC Olympus Radio Architecture Chipset.
OS Operating System.
OSI Open Systems Interconnection.
OSI RM OSI Reference Model.
OSF Operation Systems Function block.

O Version 1 Rev 1
OSF/MOTIF Open Software Foundation Motif. The basis of the GUI used
for the Motorola OMC-R MMI.
OSS Operator Services System.
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.

Version 1 Rev 1 P
P
PA Power Amplifier.
PAB Power Alarm Board.
PABX Private Automatic Branch eXchange.
PAD Packet Assembler/Disassembler facility.
Paging The procedure by which a GSM PLMN fixed infrastructure
attempts to reach an MS within its location area, before any
other network-initiated procedure can take place.
PATH CEPT 2 Mbit/s route through the BSS network.
PBUS Processor Bus.
PBX Private Branch eXchange.
PC Personal Computer.
PCH Paging CHannel. A GSM common control channel used to
send paging messages to the MSs.
PCHN Paging Channel Network.
PCHN Physical Channel.
PCM Pulse Code Modulation (see also 2 Mbit/s link which is the
physical bearer of PCM).
PCN Personal Communications Network.
PCR Preventative Cyclic Retransmission. A form of error
correction suitable for use on links with long transmission
delays, such as satellite links.
PCU Packet Control Unit (p/o GPRS).
PCU Picocell Control unit (p/o M-Cellaccess).
pd Potential difference.
PD Protocol Discriminator.
PD Public Data.
PDB Power Distribution Board.
PDF Power Distribution Frame (MSC/LR).
PDN Public Data Networks.
PDU Power Distribution Unit.
PDU Protected Data Unit.
PEDC Pan European Digital Cellular.
Peg A single incremental action modifying the value of a statistic.
Pegging Modifying a statistical value.
PH Packet Handler.
PH PHysical (layer).
PHI Packet Handler Interface.
PI Presentation Indicator.
Picocell A cell site where the base station antenna is mounted within a
building.
PICS Protocol Implementation Conformance Statement.

P Version 1 Rev 1
PID Process IDentifier/Process ID.

PIM PCM Interface Module (MSC).
PIN Personal Identification Number.
PIN Problem Identification Number.
PIX Parallel Interface Extender half size board. Customer alarm
interface (p/o BSS).
PIXT Protocol Implementation eXtra information for Testing.
PK Primary Key. A database column attribute, the primary key is
a not-null, non-duplicate index.
Plaintext Unciphered data.
PlaNET Frequency planning tool.
PLL Phase Lock Loop (refers to phase locking the GCLK in the
BTS).
PLMN Public Land Mobile Network. The mobile communications
network.
PM Performance Management. An OMC application.
PM-UI Performance Management User Interface.
PMA Prompt Maintenance Alarm. An alarm report level; immediate
action is necessary (see also DMA).
PMS Pseudo MMS.
PMUX PCM MUltipleXer.
PN Permanent Nucleus (of GSM).
PNE Prsentation des Normes Europennes.
POI Point of Interconnection (with PSTN).
POTS Plain Old Telephone Service (basic telephone services).
p/o Part of.
pp, p-p Peak-to-peak.
PP Point-to-Point.
ppb Parts per billion.
PPE Primative Procedure Entity.
ppm Parts per million (x 106).
Pref CUG Preferential CUG.
Primary Cell A cell which is already optimized in the network and has a
co-located neighbour whose cell boundary follows the
boundary of the said cell. The primary cell has a preferred
band equal to the frequency type of the coincident cell.
PROM Programmable Read Only Memory.
Ps Location probability.
PSA Periodic Supervision of Accessability.
PSAP Presentation Services Access Point.
PSM Power Supply Module.

Version 1 Rev 1 P
PSPDN Packet Switched Public Data Network. Public data

communications network. x.25 links required for NE to OMC
communications will probably be carried by PSPDN.
PSTN Public Switched Telephone Network. The UK land line
telephone network.
PSU Power Supply Unit.
PSW Pure Sine Wave.
PTO Public Telecommunications Operator.
PUCT Price per Unit Currency Table.
PVC Permanent Virtual Circuit.
PW Pass Word.
PWR Power.
PXPDN Private eXchange Public Data Network.

Q Version 1 Rev 1
Q
QA Q (Interface) Adapter.
Q3 Interface between NMC and GSM network.
Q-adapter Used to connect MEs and SEs to TMN (GSM Rec. 12.00).
QAF Q-Adapter Function.
QEI Quad European Interface. Interfaces four 2 Mbit/s circuits to
TDM switch highway (see MSI).
QIC Quarter Inch Cartridge (Data storage format).
QOS Quality Of Service.
Quiescent mode IDS intermediate state before shutdown.

Version 1 Rev 1 R
R
R Value of reduction of the MS transmitted RF power relative to
the maximum allowed output power of the highest power
class of MS (A).
RA RAndom mode request information field.
RAB Random Access Burst.
RACCH Random Access Control CHannel. A GSM common control
channel used to originate a call or respond to a page.
RACH Random Access CHannel.
RAM Random Access Memory.
RAND RANDom number (used for authentication).
RATI Receive Antenna Transceiver Interface.
RAx Rate Adaptation.
RBDS Remote BSS Diagnostic System (a discontinued Motorola
diagnostic facility).
RBER Residual Bit Error Ratio.
RBTS Remote Base Transceiver Station.
RCB Radio Control Board (p/o DRCU).
RCI Radio Channel Identifier.
RCP Radio Control Processor.
RCU Radio Channel Unit. Contains transceiver, digital control
circuits, and power supply (p/o BSS) (see DRCU).
RCVR Receiver.
RDBMS Relational DataBase Management System (INFORMIX).
RDI Radio Digital Interface System.
RDIS Restricted Digital Information.
RDM Reference Distribution Module.
RDN Relative Distinguished Name. A series of RDN form a unique
identifier, the distinguished name, for a particular network
element.
REC, Rec RECommendation.
REJ REJect(ion).
REL RELease.
RELP Residual Excited Linear Predictive.
RELP-LTP RELP Long Term Prediction. A name for GSM full rate (see
full rate).
resync Resynchronize/resynchronization.
REQ REQuest.
Revgen A Motorola DataGen utility for producing an MMI script from a
binary object database.
RF Radio Frequency.

R Version 1 Rev 1
RFC, RFCH Radio Frequency Channel. A partition of the system RF

spectrum allocation with a defined bandwidth and centre
frequency.
RFE Receiver Front End (shelf).
RFEB Receiver Front End Board (p/o DRCU II).
RFI Radio Frequency Interference.
RFM Radio Frequency Module.
RFN Reduced TDMA Frame Number.
RFU Reserved for Future Use.
RJ45 Network cable/Connector type.
RISC Reduced Instruction Set Computer.
RL Remote login.
RLC Release Complete.
RLP Radio Link Protocol. An ARQ protocol used to transfer user
data between an MT and IWF. See GSM 04.22.
RLR Receiver Loudness Rating.
RLSD ReLeaSeD.
RMS Root Mean Square (value).
RMSU Remote Mobile Switching Unit.
RNTABLE Table of 128 integers in the hopping sequence.
ROM Read Only Memory.
ROSE Remote Operations Service Element. An ASE which carries
a message between devices over an association established
by ASCE (a CCITT specification for O & M) (OMC).
Roundtrip Time period between transmit and receive instant of a
timeslot in the BTS, propagation determined by the response
behaviour of the MS and the MS to BTS delay distance.
RPE Regular Pulse Excited.
RPE-LTP Regular Pulse Excitation - Long Term Prediction. The GSM
digital speech coding scheme.
RPOA Recognised Private Operating Agency.
RPR Read Privilege Required. Access to the column is allowed
only for privileged accounts.
RR Radio Resource management.
RR Receive Ready (frame).
RRSM Radio Resource State Machine.
RS232 Standard serial interface.
RSE Radio System Entity.
RSL Radio Signalling Link.
RSLF Radio System Link Function.
RSLP Radio System Link Processor.
RSS Radio SubSystem (replaced by BSS).
RSSI Received Signal Strength Indicator.

Version 1 Rev 1 R
RSZI Regional Subscription Zone Identity.

RTC Remotely Tuneable Channel Combiner.
RTE Remote Terminal Emulator.
RTF Radio Transceiver Function.
RTF Receive Transmit Functions.
RTS Request to Send. Method of flow control (RS232 Interface).
RU Rack Unit.
Run level System processor operating mode.
Rx Receive(r).
RXCDR Remote Transcoder.
RXF Receive Function (of the RTF).
RXLEV-D Received signal level downlink.
RXLEV-U Received signal level uplink.
RXQUAL-D Received signal quality downlink.
RXQUAL-U Received signal quality uplink.
RXU Remote Transcoder Unit. The shelf which houses the
remote transcoder modules in a BSSC cabinet at a remote
transcoder site.

S Version 1 Rev 1
S
S/W SoftWare.
SABM Set Asynchronous Balanced Mode. A message which
establishes the signalling link over the air interface.
SABME SABM Extended.
SACCH Slow Associated Control CHannel. A GSM control channel
used by the MS for reporting RSSI and signal quality
measurements.
SACCH/C4 Slow Associated Control CHannel/SDCCH/4.
SACCH/C8 Slow Associated Control CHannel/SDCCH/8.
SACCH/T Slow Associated Control CHannel/Traffic channel.
SACCH/TF Slow Associated Control CHannel/Traffic channel Full rate.
SACCH/TH Slow Associated Control CHannel/Traffic channel Half rate.
SAGE A brand of trunk test equipment.
SAP Service Access Point. In the reference model for OSI, SAPs
of a layer are defined as gates through which services are
offered to an adjacent higher layer.
SAP System Audits Process.
SAPI Service Access Point Indicator (identifier).
SAW Surface Acoustic Wave.
SB Synchronization Burst (see Synchronization burst).
SBUS Serial Bus.
SC Service Centre (used for Short Message Service).
SC Service Code.
SCCA System Change Control Administration. Software module
which allows full or partial software download to the NE
(OMC).
SCCP Signalling Connection Control Part (6-8).
SCEG Speech Coding Experts Group (of GSM).
SCH Synchronization CHannel. A GSM broadcast control channel
used to carry information for frame synchronization of MSs
and identification of base stations.
SCI Status Control Interface.
SCIP Serial Communication Interface Processor.
SCM Status Control Manager.
SCN Sub-Channel Number. One of the parameters defining a
particular physical channel in a BS.
SCP Service Control Point (an intelligent network entity).
SCSI Small Computer Systems Interface.
SCU Slim Channel Unit.
SCU900 Slim Channel Unit for GSM900.
SDCCH Stand-alone Dedicated Control CHannel. A GSM control
channel where the majority of call setup occurs. Used for
MS to BTS communications before MS assigned to TCH.

Version 1 Rev 1 S
SDL Specification Description Language.

SDT SDL Developement Tool.
SDU Service Data Unit.
SDR Special Drawing Rights (an international basket currency for
billing).
SE Support Entity (GSM Rec. 12.00).
Secondary Cell A cell which is not optimized in the network and has a
co-located neighbour whose cell boundary follows the
boundary of the said cell. The secondary cell has a preferred
band the same as that of its own frequency type.
SEF Support Entity Function (GSM Rec.12.00).
SFH Slow Frequency Hopping.
SI Screening Indicator.
SI Service Interworking.
SI Supplementary Information.
SIA Supplementary Information A.
SID Silence Descriptor.
SIF Signal Information Field. The bits of a message signal unit
that carry information for a certain user transaction; the SIF
always contains a label.
SIM Subscriber Identity Module. Removable module which is
inserted into a mobile equipment; it is considered as part of
the MS. It contains security related information (IMSI, Ki,
PIN), other subscriber related information and the algorithms
A3 and A8.
SIMM Single Inline Memory module.
SIMM System Integrated Memory Module.
SIO Service Information Octet. Eight bits contained in a message
signal unit, comprising the service indicator and sub-service
field.
SITE BSC, BTS or collocated BSC-BTS site.
SIX Serial Interface eXtender. Converts interface levels to TTL
levels. Used to extend 2 serial ports from GPROC to external
devices (RS232, RS422, and fibre optics).
SK Secondary Key. A database column attribute, the secondary
key indicates an additional index and/or usage as a
composite key.
SL Signalling Link.
SLNK Serial Link.
SLR Send Loudness Rating.
SLTM Signalling Link Test Message.
SM Switch Manager.
SM Summing Manager.
SMAE System Management Application Entity (CCITT Q795, ISO
9596).
SMCB Short Message Cell Broadcast.

S Version 1 Rev 1
SME Short Message Entity.

SMG Special Mobile Group.
SMP Motorola Software Maintenance Program.
SMS Short Message Service.
SMSCB Short Message Service Cell Broadcast.
SMS-SC Short Message Service - Service Centre.
SMS/PP Short Message Service/Point-to-Point.
Smt Short message terminal.
SN Subscriber Number.
SND SeND.
SNDR SeNDeR.
SNR Serial NumbeR.
SOA Suppress Outgoing Access (CUG SS).
SP Service Provider. The organisation through which the
subscriber obtains GSM telecommunications services. This
may be a network operator or possibly a separate body.
SP Signalling Point.
SP Special Product.
SP SPare.
SPC Signalling Point Code.
SPC Suppress Preferential CUG.
SPI Signalling Point Inaccessible.
SPP Single Path Preselector.
SQE Signal Quality Error.
SQL Structured Query Language.
SRD Service Request Distributor.
SRES Signed RESponse (authentication).
SS Supplementary Service. A modification of, or a supplement
to, a basic telecommunication service.
SS System Simulator.
SSA SCCP messages, Subsystem-allowed (see CCITT Q.712
para 1.15).
SSAP Site System Audits Processor.
SSC Supplementary Service Control string.
SSF Subservice Field. The level 3 field containing the network
indicator and two spare bits.
SSM Signalling State Machine.
SSN SubSystem Number.
SSP Service Switching Point (an intelligent network element).
SSP SCCP messages, Subsystem-prohibited (see CCITT Q.712
para 1.18).
SSP SubSystem Prohibited message.

Version 1 Rev 1 S
SSS Switching SubSystem (comprising the MSC and the LRs).

SS7 ANSI Signalling System No. 7 (alias C7).
STAN Statistical ANalysis (processor).
STAT STATistics.
stats Statistics.
STC System Timing Controller.
STMR Side Tone Masking rating.
SUERM Signal Unit Error Rate Monitor.
STP Signalling Transfer Point.
Superframe 51 traffic/associated control multiframes or 26
broadcast/common control multiframes (period 6.12s).
Super user User account that can access all files, regardless of
protection settings, and control all user accounts.
SURF Sectorized Universal Receiver Front-end (Used in
Horizonmacro).
SVC Switch Virtual Circuit.
SVM SerVice Manager.
SVN Software Version Number.
SW Software.
SWFM SoftWare Fault Management.
sync synchronize/synchronization.
Synchronization burst Period of RF carrier less than one timeslot whose modulation
bit stream carries information for the MS to synchronize its
frame to that of the received signal.
SYS SYStem.
SYSGEN SYStem GENeration. The Motorola procedure for loading a
configuration database into a BTS.

T Version 1 Rev 1
T
T Timer.
T Transparent.
T Type only.
T43 Type 43 Interconnect Board. Provides interface to 12
unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for
2 Mbit/s circuits (See BIB).
TA Terminal Adaptor. A physical entity in the MS providing
terminal adaptation functions (see GSM 04.02).
TA Timing Advance.
TAC Type Approval Code.
TACS Total Access Communications System (European analogue
cellular system).
TAF Terminal Adaptation Function.
TATI Transmit Antenna Transceiver Interface. The TATI consists
of RF combining equipments, either Hybrid or Cavity
Combining. (See CCB).
TAXI Transparent Asynchronous Transmitter/Receiver Interface
(physical layer).
TBD To Be Determined.
TBR Technical Basis for Regulation.
TBUS TDM Bus.
TC Transaction Capabilities.
TCAP Transaction Capabilities Application Part (of Signalling
System No. 7).
TCB TATI Control Board.
TCH Traffic CHannel. GSM logical channels which carry either
encoded speech or user data.
TCH/F A full rate TCH.
TCH/F2.4 A full rate TCH at 2.4 kbit/s.
TCH/FS A full rate Speech TCH.
TCH/H A half rate TCH.
TCH/H2.4 A half rate TCH at 2.4 kbit/s.
TCH/H4.8 A half rate TCH at 4.8 kbit/s.
TCH/HS A half rate Speech TCH).
TCI Transceiver Control Interface.
TCP/IP Transmission Control Protocol/Internet Protocol.
TC-TR Technical Commitee Technical Report.
TCU Transceiver Control Unit.
TDF Twin Duplexed Filter. (Used in M-Cellhorizon).
TDM Time Division Multiplexing.

Version 1 Rev 1 T
TDMA Time Division Multiple Access.

TDU TopCell Digital Unit.
TE Terminal Equipment. Equipment that provides the functions
necessary for the operation of the access protocols by the
user.
Tei Terminal endpoint identifier.
TEI Terminal Equipment Identity.
TEMP TEMPorary.
TEST TEST control processor.
TFA TransFer Allowed.
TFP TransFer Prohibited.
TFTP Trivial File Transfer Protocol.
TI Transaction Identifier.
Timeslot The multiplex subdivision in which voice and signalling bits
are sent over the air. Each RF carrier is divided into 8
timeslots.
Timing advance A signal sent by the BTS to the MS. It enables the MS to
advance the timing of its transmission to the BTS so as to
compensate for propagation delay.
TLV Type, Length and Value.
TM Traffic Manager.
TMI TDM Modem Interface board. Provides analogue interface
from IWF to modems for 16 circuits (p/o IWF).
TMM Traffic Metering and Measuring.
TMN Telecommunications Management Network. The
implementation of the Network Management functionality
required for the PLMN is in terms of physical entities which
together constitute the TMN.
TMSI Temporary Mobile Subscriber Identity. A unique identity
temporarily allocated by the MSC to a visiting mobile
subscriber to process a call. May be changed between calls
and even during a call, to preserve subscriber confidentiality.
TN Timeslot Number.
TON Type Of Number.
Traffic channels Channels which carry users speech or data (see also TCH).
Traffic unit Equivalent to an erlang.
Training sequence Sequence of modulating bits employed to facilitate timing
recovery and channel equalization in the receiver.
TRAU Transcoder Rate Adaption Unit.
TRU TopCell Radio unit.
TRX Transceiver(s). A network component which can serve full
duplex communication on 8 full-rate traffic channels according
to specification GSM 05.02. If Slow Frequency Hopping
(SFH) is not used, then the TRX serves the communication
on one RF carrier.
TS Technical Specification.

T Version 1 Rev 1
TS TeleService.
TS TimeSlot (see Timeslot).
TSA TimeSlot Acquisition.
TSA TimeSlot Assignment.
TSDA Transceiver Speech & Data Interface.
TSC Training Sequence Code.
TSI TimeSlot Interchange.
TSDI Transceiver Speech and Data Interface.
TSM Transceiver Station Manager.
TSW Timeslot SWitch.
TTCN Tree and Tabular Combined Notation.
TTL Transistor to Transistor Logic.
TTY TeleTYpe (refers to any terminal).
TU Traffic Unit.
TUP Telephone User Part (SS7).
TV Type and Value.
Tx Transmit(ter).
TXF Transmit Function (of the RTF).
TXPWR Transmit PoWeR. Tx power level in the
MS_TXPWR_REQUEST and MS_TXPWR_CONF
parameters.
TxBPF Transmit Bandpass Filter.

Version 1 Rev 1 U
U
UA Unnumbered Acknowledgment. A message sent from the
MS to the BSS to acknowledge release of radio resources
when a call is being cleared.
UDI Unrestricted Digital Information.
UDP User Datagram Protocol.
UDUB User Determined User Busy.
UHF Ultra High Frequency.
UI Unnumbered Information (Frame).
UIC Union International des Chemins de Fer.
UID User ID. Unique number used by the system to identify the
user.
UL Upload (of software or database from an NE to a BSS).
Um Air interface.
UMTS Universal Mobile Telecommunication System.
UPCMI Uniform PCM Interface (13 bit).
UPD Up to Date.
Uplink Physical link from the MS towards the BTS (MS transmits,
BTS receives).
UPS Uninterruptable Power Supply.
UPU User Part Unavailable.
Useful part of burst That part of the burst used by the demodulator; differs from
the full burst because of the bit shift of the I and Q parts of
the GMSK signal.
USSD Unstructured Supplementary Service Data.
UUS User-to-User Signalling supplementary service.

V Version 1 Rev 1
V
V Value only.
VA Viterbi Algorithm (used in channel equalizers).
VAD Voice Activity Detection. A process used to identify presence
or absence of speech data bits. VAD is used with DTX.
VAP Videotex Access Point.
VBS Voice Broadcast Service.
VC Virtual Circuit.
VCO Voltage Controlled Oscillator.
VCXO Voltage Controlled Crystal Oscillator.
VDU Visual Display Unit.
VGCS Voice Group Call Service.
VLR Visitor Location Register. A GSM network element which
provides a temporary register for subscriber information for a
visiting subscriber. Often a part of the MSC.
VLSI Very Large Scale Integration (in ICs).
VMSC Visited MSC. (Recommendation not to be used).
VOX Voice Operated Transmission.
VPLMN Visited PLMN.
VSC Videotex Service Centre.
V(SD) Send state variable.
VSP Vehicular Speaker Phone.
VSWR Voltage Standing Wave Ratio.
VTX host The components dedecated to Videotex service.

Version 1 Rev 1 W
W
WAN Wide Area Network.
WPA Wrong Password Attempts (counter).
WS Work Station. The remote device via which O&M personnel
execute input and output transactions for network
management purposes.
WSF Work Station Function block.
WWW World Wide Web.

X Version 1 Rev 1
X
X.25 CCITT specification and protocols for public packet-switched
networks (see PSPDN).
X.25 link A communications link which conforms to X.25 specifications
and uses X.25 protocol (NE to OMC links).
XBL Transcoder to BSS Link. The carrier communications link
between the Transcoder (XCDR) and the BSS.
XCB Transceiver Control Board (p/o Transceiver).
XCDR Full-rate Transcoder. Provides speech transcoding and 4:1
submultiplexing (p/o BSS, BSC or XCDR).
XCDR board The circuit board required to perform speech transcoding at
the BSS or (R)XCDR). Also known as the MSI (XCDR)
board. Interchangeable with the GDP board.
XFER Transfer.
XID eXchange IDentifier.
X-Term X terminal window.

Version 1 Rev 1 Z
Z
ZC Zone Code

Z Version 1 Rev 1

PCU

Uploaded by

Copyright:

Available Formats

PCU

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PCU

Uploaded by

Copyright:

Available Formats

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5

CHAPTER 6 CHAPTER 7 ANNEX A ANNEX B GLOSSARY

TG03 Version 1 Rev 1

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

MOTOROLA LTD. 2002 TG03: Toolbag PCU i

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

Copyrights, notices and trademarks

and MOTOROLA are registered trademarks of Motorola Inc.

ii TG03: Toolbag PCU MOTOROLA LTD. 2002

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . G1

MOTOROLA LTD. 2002 TG03: Toolbag PCU iii

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

WARNING Failure to comply with Motorolas operation, installation and

MOTOROLA LTD. 2002 TG03: Toolbag PCU 1

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

Special key sequences

CTRL-c Press the Control and c keys at the same time.

2 TG03: Toolbag PCU MOTOROLA LTD. 2002

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

First aid in case of electric shock

MOTOROLA LTD. 2002 TG03: Toolbag PCU 3

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

Reporting safety issues

4 TG03: Toolbag PCU MOTOROLA LTD. 2002

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

Warnings and cautions

Example and format

Example and format

MOTOROLA LTD. 2002 TG03: Toolbag PCU 5

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

6 TG03: Toolbag PCU MOTOROLA LTD. 2002

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

MOTOROLA LTD. 2002 TG03: Toolbag PCU 7

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

8 TG03: Toolbag PCU MOTOROLA LTD. 2002

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

Devices sensitive to static

Special handling techniques

MOTOROLA LTD. 2002 TG03: Toolbag PCU 9

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

MOTOROLA LTD. 2002 TG03: Toolbag PCU i

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

ii TG03: Toolbag PCU MOTOROLA LTD. 2002

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

MOTOROLA LTD. 2002 TG03: Toolbag PCU iii

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

iv TG03: Toolbag PCU MOTOROLA LTD. 2002

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

Tools Chapter Objectives

MOTOROLA LTD. 2002 TG03: Toolbag PCU 11

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

12 TG03: Toolbag PCU MOTOROLA LTD. 2002

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

   

MOTOROLA LTD. 2002 TG03: Toolbag PCU 13

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED

Ctlc will stop the process.

14 TG03: Toolbag PCU MOTOROLA LTD. 2002

FOR TRAINING PURPOSES ONLY THIS MANUAL WILL NOT BE UPDATED