Gprs 014444

CHAPTER 1 GPRS REVIEW

CHAPTER 2 PCU ARCHITECTURE

CHAPTER 3 BSS/PCU COMMANDS AND STATISTICS

CHAPTER 4 PCU STATISTICS

CHAPTER 5 GSN ARCHITECTURE

CHAPTER 6 SGSN CONFIGURATION PARAMETERS

CHAPTER 7 SGSN STATISTICS ATTRIBUTES

CHAPTER 8 GGSN STATISTICS ATTRIBUTES

CHAPTER 9 APPENDIX

CHAPTER 10 GLOSSARY

Network Solutions Sector

ISSUE 1 REVISION 2

GPRS01 GPRS ARCHITECTURE

FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

GPRS01 GPRS ARCHITECTURE

FOR TRAINING PURPOSES ONLY

GPRS01 GPRS ARCHITECTURE

ISSUE 1 REVISION 2

GPRS01 GPRS Architecture

E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999 All Rights Reserved Printed in the U.K.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

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 trademarks of Motorola Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Tandem, Integrity, Integrity S2, and Non-Stop-UX are trademarks of Tandem Computers Incorporated. X Window System, X and X11 are trademarks of the Massachusetts Institute of Technology. Looking Glass is a registered trademark of Visix Software Ltd. OSF/Motif is a trademark of the Open Software Foundation. Ethernet is a trademark of the Xerox Corporation. Wingz is a trademark and INFORMIX is a registered trademark of Informix Software Ltd. SUN, SPARC, and SPARCStation are trademarks of Sun Microsystems Computer Corporation. IBM is a registered trademark of International Business Machines Corporation. HP is a registered trademark of Hewlett Packard Inc. EMOTOROLA LTD. 2000

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

General information

General information
Important notice
If this manual was obtained when you attended a Motorola training course, it will not be updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then corrections will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs).

Purpose
Motorola Global System for Mobile Communications (GSM) Technical Education manuals are intended to support the delivery of Technical Education only and are not intended to replace the use of Customer Product Documentation. WARNING Failure to comply with Motorola’s 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.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1

General information

ISSUE 1 REVISION 2

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 ALT–f | CR or RETURN Press the Control and c keys at the same time. Press the Alt and f keys at the same time. Press the pipe symbol key. 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

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

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
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. 1. 2. 3. Do not attempt to remove clothing adhering to the burn. If help is available, or as soon as artificial respiration is no longer required, cover the wound with a dry dressing. Do not apply oil or grease in any form.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3

Reporting safety issues

ISSUE 1 REVISION 2

Reporting safety issues
Introduction
A caution means that there is a possibility of damage to systems, or individual items of equipment within a system. However, this presents no danger to personnel.

Procedure
Whenever a safety issue arises: 1. 2. 3. Make the equipment concerned safe, for example, by removing power. Make no further attempt to tamper with the equipment. Report the problem directly to GSM Customer Network Resolution Centre +44 (0)1793 430040 (telephone) and follow up with a written report by fax +44 (0)1793 430987 (fax). Collect evidence from the equipment under the guidance of the Customer Network Resolution Centre.

4.

4

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Warnings and cautions

Warnings and cautions
Introduction
The following describes how warnings and cautions are used in this manual and in all manuals of the Motorola GSM manual set.

Warnings
Definition
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents, as well as those inherent in the equipment.

Example and format
WARNING 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.

Cautions
Definition
A caution means that there is a possibility of damage to systems, or individual items of equipment within a system. However, this presents no danger to personnel.

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

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5

General warnings

ISSUE 1 REVISION 2

General warnings
Introduction
Observe the following warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola GSM manuals, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customer’s failure to comply with these requirements.

Warning labels
Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning labels must not be removed, painted over or obscured in any way.

Specific warnings
Warnings particularly applicable to the equipment are positioned on the equipment and within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other warnings given in text, on the illustrations and on the equipment.

High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single phase or 415 V ac three phase mains which is potentially lethal. Therefore, the areas where the ac mains power is present must not be approached until the warnings and cautions in the text and on the equipment have been complied with. To achieve isolation of the equipment from the ac supply, the mains input isolator must be set to off and locked. Within the United Kingdom (UK) regard must be paid to the requirements of the Electricity at Work Regulations 1989. There may also be specific country legislation which need to be complied with, depending on where the equipment is used.

RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment when in operation. Ensure that all transmitters are switched off when any antenna connections have to be changed. Do not key transmitters connected to unterminated cavities or feeders. Refer to the following standards: S S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz. CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10kHz to 300GHz).

Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors.
6

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

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 Motorola equipment incorporates components containing the highly toxic material Beryllium or its oxide Beryllia or both. These materials are especially hazardous if: S S S 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.

See the Beryllium health and safety precautions section for further information.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7

Human exposure to radio frequency energy (PCS1900 only)

ISSUE 1 REVISION 2

Human exposure to radio frequency energy (PCS1900 only)
Introduction
This equipment is designed to generate and radiate radio frequency (RF) energy. It should be installed and maintained only by trained technicians. Licensees of the Federal Communications Commission (FCC) using this equipment are responsible for insuring that its installation and operation comply with FCC regulations designed to limit human exposure to RF radiation in accordance with the American National Standards Institute IEEE Standard C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.

Definitions
This standard establishes two sets of maximum permitted exposure limits, one for controlled environments and another, that allows less exposure, for uncontrolled environments. These terms are defined by the standard, as follows:

Uncontrolled environment
Uncontrolled environments are locations where there is the exposure of individuals who have no knowledge or control of their exposure. The exposures may occur in living quarters or workplaces where there are no expectations that the exposure levels may exceed those shown for uncontrolled environments in the table of maximum permitted exposure ceilings.

Controlled environment
Controlled environments are locations where there is exposure that may be incurred by persons who are aware of the potential for exposure as a concomitant of employment, by other cognizant persons, or as the incidental result of transient passage through areas where analysis shows the exposure levels may be above those shown for uncontrolled environments but do not exceed the values shown for controlled environments in the table of maximum permitted exposure ceilings.

Maximum permitted exposures
The maximum permitted exposures prescribed by the standard are set in terms of different parameters of effects, depending on the frequency generated by the equipment in question. At the frequency range of this Personal Communication System equipment, 1930-1970MHz, the maximum permitted exposure levels are set in terms of power density, whose definition and relationship to electric field and magnetic field strengths are described by the standard as follows:

Power density (S)
Power per unit area normal to the direction of propagation, usually expressed in units of watts per square metre (W/m2) or, for convenience, units such as milliwatts per square centimetre (mW/cm2). For plane waves, power density, electric field strength (E) and magnetic field strength (H) are related by the impedance of free space, 377 ohms. In particular,
2 S + E + 377 377

H2

where E and H are expressed in units of V/m and A/m, respectively, and S in units of W/m 2. Although many survey instruments indicate power density units, the actual quantities measured are E or E2 or H or H2.
8

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Human exposure to radio frequency energy (PCS1900 only)

Maximum permitted exposure ceilings
Within the frequency range, the maximum permitted exposure ceiling for uncontrolled environments is a power density (mW/cm2) that equals f/1500, where f is the frequency expressed in MHz, and measurements are averaged over a period of 30 minutes. The maximum permitted exposure ceiling for controlled environments, also expressed in mW/cm 2, is f/300 where measurements are averaged over 6 minutes. Applying these principles to the minimum and maximum frequencies for which this equipment is intended to be used yields the following maximum permitted exposure levels: Uncontrolled Environment 1930MHz Ceiling 1970MHz Controlled Environment 1930MHz 1970MHz

1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2 6.567mW/cm 2

If you plan to operate the equipment at more than one frequency, compliance should be assured at the frequency which produces the lowest exposure ceiling (among the frequencies at which operation will occur). Licensees must be able to certify to the FCC that their facilities meet the above ceilings. Some lower power PCS devices, 100 milliwatts or less, are excluded from demonstrating compliance, but this equipment operates at power levels orders of magnitude higher, and the exclusion is not applicable. Whether a given installation meets the maximum permitted exposure ceilings depends, in part, upon antenna type, antenna placement and the output power to which this equipment is adjusted. The following example sets forth the distances from the antenna to which access should be prevented in order to comply with the uncontrolled and controlled environment exposure limits as set forth in the ANSI IEEE standards and computed above.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

9

Human exposure to radio frequency energy (PCS1900 only)

ISSUE 1 REVISION 2

Example calculation
For a base station with the following characteristics, what is the minimum distance from the antenna necessary to meet the requirements of an uncontrolled environment? Transmit frequency Base station cabinet output power, P Antenna feeder cable loss, CL Antenna input power Pin Antenna gain, G Using the following relationship: G + 4p r W Pin
2

1930MHz +39.0 dBm (8 watts) 2.0dB P–CL = +39.0–2.0 = +37.0dB (5watts) 16.4dBi (43.65)

Where W is the maximum permissible power density in W/m2 and r is the safe distance from the antenna in metres, the desired distance can be calculated as follows: r+

ǸGPin + Ǹ 43.65 5 + 1.16m 4p W 4p 12.87

where W = 12.87 W/m2 was obtained from table listed above and converting from mW/cm 2 to W/m2. NOTE The above result applies only in the direction of maximum radiation of the antenna. Actual installations may employ antennas that have defined radiation patterns and gains that differ from the example set forth above. The distances calculated can vary depending on the actual antenna pattern and gain.

Power density measurements
While installation calculations such as the above are useful and essential in planning and design, validation that the operating facility using this equipment actually complies will require making power density measurements. For information on measuring RF fields for determining compliance with ANSI IEEE C95.1-1991, see IEEE Recommended Practice for the Measure of Potentially Hazardous Electromagnetic Fields - RF and Microwave, IEEE Std C95.3-1991. Copies of IEEE C95.1-1991 and IEEE C95.3-1991 may be purchased from the Institute of Electrical and Electronics Engineers, Inc., Attn: Publication Sales, 445 Hoes Lane, P.O. Box 1331, Piscattaway, NJ 08855-1331, (800) 678-IEEE or from ANSI, (212) 642-4900. Persons responsible for installation of this equipment are urged to consult these standards in determining whether a given installation complies with the applicable limits.

Other equipment
Whether a given installation meets ANSI standards for human exposure to radio frequency radiation may depend not only on this equipment but also on whether the environments being assessed are being affected by radio frequency fields from other equipment, the effects of which may add to the level of exposure. Accordingly, the overall exposure may be affected by radio frequency generating facilities that exist at the time the licensee’s equipment is being installed or even by equipment installed later. Therefore, the effects of any such facilities must be considered in site selection and in determining whether a particular installation meets the FCC requirements.
10

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Beryllium health and safety precautions

Beryllium health and safety precautions
Introduction
Beryllium (Be), is a hard silver/white metal. It is stable in air, but burns brilliantly in Oxygen. With the exception of the naturally occurring Beryl ore (Beryllium Silicate), all Beryllium compounds and Beryllium metal are potentially highly toxic.

Health issues
Beryllium Oxide is used within some components as an electrical insulator. Captive within the component it presents no health risk whatsoever. However, if the component should be broken open and the Beryllium Oxide, which is in the form of dust, released, there exists the potential for harm.

Inhalation
Inhalation of Beryllium Oxide can lead to a condition known as Berylliosis, the symptoms of Berylliosis are similar to Pneumonia and may be identified by all or any of the following: Mild poisoning causes fever, shortness of breath, and a cough that produces yellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucous membranes of the nose, throat, and chest with discomfort, possibly pain, and difficulty with swallowing and breathing. Severe poisoning causes chest pain and wheezing which may progress to severe shortness of breath due to congestion of the lungs. Incubation period for lung symptoms is 2-20 days. Exposure to moderately high concentrations of Beryllium in air may produce a very serious condition of the lungs. The injured person may become blue, feverish with rapid breathing and raised pulse rate. Recovery is usual but may take several months. There have been deaths in the acute stage. Chronic response. This condition is more truly a general one although the lungs are mainly affected. There may be lesions in the kidneys and the skin. Certain features support the view that the condition is allergic. There is no relationship between the degree of exposure and the severity of response and there is usually a time lag of up to 10 years between exposure and the onset of the illness. Both sexes are equally susceptible. The onset of the illness is insidious but only a small number of exposed persons develop this reaction.

First aid
Seek immediate medical assistance. The casualty should be removed immediately from the exposure area and placed in a fresh air environment with breathing supported with Oxygen where required. Any contaminated clothing should be removed. The casualty should be kept warm and at rest until medical aid arrives.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

11

Beryllium health and safety precautions

ISSUE 1 REVISION 2

Skin contact
Possible irritation and redness at the contact area. Persistent itching and blister formations can occur which usually resolve on removal from exposure.

First aid
Wash area thoroughly with soap and water. If skin is broken seek immediate medical assistance.

Eye contact
May cause severe irritation, redness and swelling of eyelid(s) and inflammation of the mucous membranes of the eyes.

First aid
Flush eyes with running water for at least 15 minutes. Seek medical assistance as soon as possible.

Handling procedures
Removal of components from printed circuit boards (PCBs) is to take place only at Motorola approved repair centres. The removal station will be equipped with extraction equipment and all other protective equipment necessary for the safe removal of components containing Beryllium Oxide. If during removal a component is accidently opened, the Beryllium Oxide dust is to be wetted into a paste and put into a container with a spatula or similar tool. The spatula/tool used to collect the paste is also to be placed in the container. The container is then to be sealed and labelled. A suitable respirator is to be worn at all times during this operation. Components which are successfully removed are to be placed in a separate bag, sealed and labelled.

Disposal methods
Beryllium Oxide or components containing Beryllium Oxide are to be treated as hazardous waste. All components must be removed where possible from boards and put into sealed bags labelled Beryllium Oxide components. These bags must be given to the safety and environmental adviser for disposal. Under no circumstances are boards or components containing Beryllium Oxide to be put into the general waste skips or incinerated.

Product life cycle implications
Motorola GSM and analogue equipment includes components containing Beryllium Oxide (identified in text as appropriate and indicated by warning labels on the equipment). These components require specific disposal measures as indicated in the preceding (Disposal methods) paragraph. Motorola will arrange for the disposal of all such hazardous waste as part of its Total Customer Satisfaction philosophy and will arrange for the most environmentally ‘friendly’ disposal available at that time.
12

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

General cautions

General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola GSM manuals may result in damage to the equipment. Motorola assumes no liability for the customer’s 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.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

13

Devices sensitive to static

ISSUE 1 REVISION 2

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: S S S S S S Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible work on an earthed metal surface. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. All metal tools should be used and when not in use they should be placed on an earthed surface. 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.

14

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Motorola GSM manual set

Motorola GSM manual set
Introduction
The following manuals provide the information needed to operate, install and maintain the Motorola GSM equipment.

Generic manuals
The following are the generic manuals in the GSM manual set, these manuals are release dependent: Classification number GSM-100-101 GSM-100-201 GSM-100-202 GSM-100-311 GSM-100-313 GSM-100-320 GSM-100-321 GSM-100-403 GSM-100-423 GSM-100-413 GSM-100-501 GSM-100-520 GSM-100-521 GSM-100-523 GSM-100-503 GSM-100-721 GSM-100-712 Name System Information: General . . . . . . . . . . . . . . . . . . . Operating Information: GSM System Operation . . . Operating Information: Scaleable OMC System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description: OMC in a GSM System . . . . Technical Description: OMC Database Schema . . . Technical Description: BSS Implementation . . . . . . . Technical Description: BSS Command Reference . Installation & Configuration: GSM System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: BSS Optimization . . . . Installation & Configuration: Scaleable OMC Clean Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Information: Alarm Handling at the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Information: BSS Timers . . . . . . . . . . . Maintenance Information: Device State Transitions Maintenance Information: BSS Field Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maintenance Information: GSM Statistics Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Release Notes: BSS/RXCDR . . . . . . . . . . Software Release Notes: Scaleable OMC System . Index of Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . Order number 68P02901W01 68P02901W14 68P02901W19 68P02901W31 68P02901W34 68P02901W36 68P02901W23 68P02901W17 68P02901W43 68P02901W47 68P02901W26 68P02901W58 68P02901W57 68P02901W51 68P02901W56 68P02901W72 68P02901W74 68P02900W81

Related manuals
The following are related Motorola GSM manuals: Classification number GSM-001-103 GSM-002-103 GSM-002-703 GSM-005-103 GSM-008-403 GSM-008-703 GSM-006-202 GSM-006-413 GSM-006-712 Name System Information: BSS Equipment Planning . . . . System Information: DataGen . . . . . . . . . . . . . . . . . . Software Release Notes: DataGen . . . . . . . . . . . . . . System Information: Advance Operational Impact . Installation & Configuration: Network Health Analyst Software Release Notes: Network Health Analyst . Operating Information: OMC System Administration (OSI) . . . . . . . . . . . . . . . . . . . . . . . . . . Installation & Configuration: OSI Clean Install . . . . . Software Release Notes: OMC OSI System . . . . . . Order number 68P02900W21 68P02900W22 68P02900W76 68P02900W25 68P02900W36 68P02900W77 68P02901W10 68P02901W39 68P02901W70

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

15

Motorola GSM manual set

ISSUE 1 REVISION 2

Service manuals
The following are the service manuals in the GSM manual set, these manuals are not release dependent. The internal organization and makeup of service manual sets may vary, they may consist of from one to four separate manuals, but they can all be ordered using the overall catalogue number shown below: Classification number GSM-100-020 GSM-100-030 GSM-105-020 GSM-106-020 GSM-201-020 GSM-202-020 GSM-203-020 GSM-206-020 GSM-205-020 GSM-204-020 GSM-207-020 GSM-101-SERIES GSM-103-SERIES GSM-102-SERIES GSM-104-SERIES GSM-200-SERIES Name Service Manual: BTS . . . . . . . . . . . . . . . . . . . . . . . . . . Service Manual: BSC/RXCDR . . . . . . . . . . . . . . . . . . Service Manual: M-Cell2 . . . . . . . . . . . . . . . . . . . . . . . Service Manual: M-Cell6 . . . . . . . . . . . . . . . . . . . . . . . Service Manual: M-Cellcity . . . . . . . . . . . . . . . . . . . . . Service Manual: M-Cellaccess . . . . . . . . . . . . . . . . . . Service Manual: M-Cellarena . . . . . . . . . . . . . . . . . . . Service Manual: M-Cellarena macro . . . . . . . . . . . . . . . Service Manual: Horizonmacro Indoor . . . . . . . . . . . Service Manual: Horizonmacro Outdoor . . . . . . . . . . Service Manual: Horizonoffice . . . . . . . . . . . . . . . . . . ExCell4 Documentation Set . . . . . . . . . . . . . . . . . . . . ExCell6 Documentation Set . . . . . . . . . . . . . . . . . . . . TopCell Documentation Set (GSM900) . . . . . . . . . . . TopCell Documentation Set (DCS1800) . . . . . . . . . . M-Cellmicro Documentation Set . . . . . . . . . . . . . . . . . Order number 68P02901W37 68P02901W38 68P02901W75 68P02901W85 68P02901W95 68P02901W65 68P02902W36 68P02902W15 68P02902W06 68P02902W12 68P02902W46 68P02900W50 68P02900W70 68P02901W80 68P02902W80 68P02901W90

Classification number
The classification number is used to identify the type and level of a manual. For example, manuals with the classification number GSM-100-2xx contain operating information.

Order number
The Motorola 68P order (catalogue) number is used to order manuals.

Ordering manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or Representative. Manuals are ordered using the order (catalogue) number. Remember, specify the manual issue required by quoting the correct suffix letter.

16

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GMR amendment

GMR amendment
Introduction to GMRs
Changes to a manual that occur after the printing date are incorporated into the manual using General Manual Revisions (GMRs). GMRs are issued to correct Motorola manuals as and when required. A GMR has the same identity as the target manual. Each GMR is identified by a number in a sequence that starts at 01 for each manual at each issue. GMRs are issued in the form of loose leaf pages, with a pink instruction sheet on the front.

GMR procedure
When a GMR is received, check on the GMR amendment record page of this manual that previous GMRs, if any, have been incorporated. If not, contact your administrator or Motorola Local Office to obtain the missing GMRs. Remove and replace pages in this manual, as detailed on the GMR pink instruction sheet.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

17

GMR amendment record

ISSUE 1 REVISION 2

GMR amendment record
Instructions
When a GMR is inserted in this manual, the amendment record below must be filled in to record the insertion. Retain the pink instruction sheet that accompanies each GMR and insert it in a suitable place in this manual for future reference.

Amendment record
Record the insertion of GMRs in this manual in the following table:

GMR number 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

Incorporated by (signature)

Date

18

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GMR amendment record

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

19

Chapter 1

GPRS Review

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Chapter 1 GPRS Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Network Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The GPRS Support Node Network (GSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC–G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Base Station System (BSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Mobile Station (MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Application Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station System GPRS Protocol (BSSGP) . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Link Control (LLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subnetwork Dependant Convergence Protocol (SNDCP) . . . . . . . . . . . . . . . . . . . Network Service (NS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Tunnelling Protocol (GTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet Protocol (IP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User Datagram Protocol/Transmission Control Protocol (UDP/TCP) . . . . . . . . . . GPRS Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS 52 Multiframe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Um Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timeslot Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS Classes with Multislot Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fixed Allocation Timeslot Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobility Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing Advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Continuous Timing Advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Originated Packet Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Mobile Terminated Packet Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Uplink Packet Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Terminated Packet Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Link Control (RLC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RLC Data ACK/NACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release of Uplink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging for GPRS Downlink Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP Context Modification Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP Context Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP Context Deactivation Initiated by GGSN Procedure . . . . . . . . . . . . . . . . . . . Routing Area Update Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Combined RA/LA Update in the case of Inter SGSN RA Update Procedure . .

i
1–1 1–2 1–2 1–2 1–2 1–2 1–4 1–4 1–4 1–4 1–6 1–6 1–6 1–6 1–8 1–8 1–10 1–12 1–14 1–16 1–18 1–20 1–22 1–24 1–26 1–28 1–30 1–32 1–34 1–36 1–38 1–40 1–42 1–46 1–48 1–50 1–54 1–54 1–54 1–56 1–58

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

iii

ISSUE 1 REVISION 2

iv

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Objectives

Objectives
On completion of this chapter the student will be able to: S S S Identify the functional entities of GPRS Describe the GPRS network with regards to GSM Identify the GPRS/GSM control channels

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–1

GPRS Network Overview

ISSUE 1 REVISION 2

GPRS Network Overview
The diagram opposite shows a simplified General Packet Radio Service (GPRS) network. Each network component is illustrated once, however, many of the components will occur several times throughout a network. The principal network component groups are:

The GPRS Support Node Network (GSN)
The GPRS Support Node Network (GSN) is the main element in the GPRS infrastructure. It is a high performance, broadband packet switching node that provides connection and interworking with various data networks, mobility management and delivery of data packets to mobile stations. The GSN Network is made of the following component groups. S CommHub – The GSN CommHub is the central connection point for the components in a GPRS system. It provides LAN connectivity between GPRS components through Ethernet and WAN connectivity to data networks outside the GPRS system. ISS – The Integrated Support Services provides GPRS system components with the current time, domain name translation and network information. GGSN – The Gateway GPRS Support Node provides network access to external hosts so they can communicate with MSs. It also decapsulates and forwards external data networks packets to the appropriate data network. SGSN – The Serving GPRS Support Node detects and tracks GPRS MSs in its service area and provides a reliable, secure data channel as the MS moves between cells.

S S

S

OMC–G
The OMC-G enables operators to use an NT graphical user interface (GUI) when managing the GPRS components. System operators use the OMC–G to configure and monitor system components and view performance data.

The Base Station System (BSS)
The Base Station System provides the radio frequency link between the GPRS network infrastructure and mobile subscribers throughout the operational area. A BSS consists of three components: S S S Base Station Controller (BSC) Base Station Transceiver (BTS) Packet Control Unit (PCU) – The Packet Control Unit (PCU) performs radio functions and GPRS network functions. It has interfaces to the OMC-R, BSC and the SGSN.

The Mobile Station (MS)
The MSs can belong to three classes A, B or C the class determines whether GPRS and Circuit Switched services can be carried out at the same time or not. The mobiles are also divided in to multi slot classes that determine the mobile capability of sending and receiving over multiple slots in a TDMA frame.
1–2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Network Overview

BSC Abis GDS PCU Gb BTS Frame Relay

A RXCDR MSC

Internet

SGSN CommHub Gi Router

GSN Network

GGSN

ISS

Course code – Section ?

For Training Purposes Only

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–3

GPRS Application Protocols

ISSUE 1 REVISION 2

GPRS Application Protocols
Base Station System GPRS Protocol (BSSGP)
Base Station System GPRS Protocol uses Frame relay protocol to provide the radio related Qualiity Of Service (QOS) and routing information required to transmit user data between an SGSN and a BSS. In the SGSN, it forms an interface between Radio Link Control (RLC)/ Media Access Control (MAC) derived information from the BSS and Logical Link Control (LLC) frames from the SGSN. In the BSS, it acts as an interface between LLC frames from the SGSN and RLC/MAC from the BSS. The functions of the BSSGP protocol are to: S S S S S S Provide a connectionless link between the SGSN and the BSS. Transfer data unconfirmed between the SGSN and the BSS. Provide tools for the bi-directional control of the flow of data between the SGSN and the BSS. Handle paging requests from the SGSN to the BSS. Give support for the flushing of old messages from the BSS, for example when an MS changes BSSs. Support multiple layer 2 links between the SGSN and the BSS.

Logical Link Control (LLC)
The LLC provides a highly reliable logical connection between the SGSN and the MS and as such spans the Gb and Um interfaces. In addition the LLC has been designed to be independent of the underlying radio interface protocols. The LLC includes functions for: S S S S S Provision of one or more logical link connections discriminated between by means of the Service Access Point Identifier (SAPI). Sequence Control Error detection and Recovery Flow Control Ciphering

Subnetwork Dependant Convergence Protocol (SNDCP)
Network Layer protocols are intended to be capable of operating over services derived from a wide variety of submetworks and data links. GPRS supports several network layer protocols providing protocol transparency for the users of the service. Introduction of new network layer protocols to be transferred over GPRS shall be possible without any changes to GPRS. Therefore, all functions related to the transfer of Network layer Protocol Data Units (N–PDUs) shall be carried out in a transparent way by GPRS network entities using Subnetwork Dependant Convergence Protocol (SNDCP). Another function of SNDCP is to improve channel efficiency fulfilled by protocol compression and data compression.
1–4

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Application Protocols

IP

IP

SNDCP

SNDCP

GTP

GTP

LLC

LLC

TCP/ UDP

TCP/ UDP

BSSGP RLC/ MAC RLC/ MAC Network Service GSM RF GSM RF L1 Bis

BSSGP Network Service L1 Bis

IP

IP

L2

L2

L1

L1

MS

BSS

SGSN

GGSN

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–5

GPRS Application Protocols

ISSUE 1 REVISION 2

Network Service (NS)
The Network Service (NS) transports the BSSGP PDUs. The Network Service Control entity is responsible for the following functions: S NS SDU transmission: The NS SDUs shall be transmitted on the NS–VCs. The NS SDUs are encapsulated into Network Service Control PDUs, which in turn are encapsulated into Sub–Network Service PDUs. Load sharing: The load sharing function distributes the NS SDU traffic amongst the available (i.e. unblocked) NS–VCs of a group. NS–VC management: A blocking procedure is used by an NS entity to inform an NS peer entity when an NS–VC becomes unavailable for NS user traffic. An unblocking procedure is used for the reverse operation. A reset procedure is used between peer NS entities in order to set an NS–VC to a determined state, after events resulting in possibly inconsistent states of the NS–VC at both sides of the Gb interface. A test procedure is used to check that an NS–VC is operating properly between peer NS entities.

S S

GPRS Tunnelling Protocol (GTP)
GPRS Tunnelling Protocol (GTP) allows multiprotocol packets to be tunnelled through the GPRS backbone between GPRS Support Nodes (GSNs). GTP tunnels user data and signalling between GSNs in the GPRS network. GTP uses Transmission Control Protocol/Internet Protocol (TCP/IP) and User Datagram Protocol/Internet Protocol (UDP/IP) protocols to communicate between SGSN and GGSN. GTP simultaneously supports two operation modes for information transfer between the GGSN and the SGSN: acknowledged and unacknowledged.

Internet Protocol (IP)
Internet Protocol is the GPRS protocol used for routing user data and control signalling within the GSN, as well as from the Internet.

User Datagram Protocol/Transmi ssion Control Protocol (UDP/TCP)
User Datagram Protocol (UDP) carries GTP PDUs for protocols that do not need a reliable data link. UDP also provides protection against corrupted GTP PDUs. Transmission Control Protocol (TCP)_carries GTP PDUs for protocols requiring reliable data link. TCP also provides flow control and protection against lost and corrupted GTP PDUs.

1–6

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Application Protocols

IP

IP

SNDCP

SNDCP

GTP

GTP

LLC

LLC

TCP/ UDP

TCP/ UDP

BSSGP RLC/ MAC RLC/ MAC Network Service GSM RF GSM RF L1 Bis

BSSGP Network Service L1 Bis

IP

IP

L2

L2

L1

L1

MS

BSS

SGSN

GGSN

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–7

GPRS Review

ISSUE 1 REVISION 2

GPRS Review
System Overview
GPRS is a set of new GSM Bearer and Teleservices providing Packet mode Transmission with the PLMN and external networks. It allows the MSs to send and receive data in an end to end packet transfer without using resources used for circuit switches. GPRS will be able to provide both Point to Point (PTP) and Point to Multipoint (PTM). The GSM radio is broken down for efficient use by data users. S S S S S Multiple MSs may use a single timeslot Multiple MSs may share multiple timeslots A single MS may use multiple timeslots (up to eight) Different MSs may use uplink or downlink radio resource Each radio may use one of four channel coding schemes to get up to 21.4kbps of data per timeslot

The channel coder firmware will support CS1 and CS2 for GPRS at GSNI. Scheme CS1 CS2 CS3 CS4 Data Rate 9.05 13.4 15.6 21.4 Supported YES YES NO NO

1–8

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

System Overview

S S S S S

Multiple MSs may use a single TS Multiple MSs may share multiple TS A single MS may use multiple TS (up to 8) Different MSs may use one of four channel coding schemes Each radio may use one of four channel coding schemes

Scheme CS1 CS2 CS3 CS4

Data Rate 9.05 13.4 15.6 21.4

Supported YES YES FUTURE FUTURE

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–9

GPRS Review

ISSUE 1 REVISION 2

GPRS 52 Multiframe
The 52 frame structure shown opposite is a new frame. Its structure is totally different from the existing 51 and 26 frame structures. The 52 Multiframe does not have a rigid structure. Essentially the different channels are identified by message type. The Multiframe can carry control channels or data channels. CONTROL CHANNELS PBCCH PPCH PAGCH PNCH TRAFFIC CHANNELS PDTCH PACCH

1–10

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

52 Multiframe structure
B0 B1 B2 I B3 B4 B5 I B6 B7 B8 I B9 B10 B11 I
I = IDLE FRAME B(n)= 4 Frame radio block

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–11

GPRS Review

ISSUE 1 REVISION 2

Um Air Interface
GPRS uses one or more timeslots per call known as Packet Data Channel (PDCH). PDCHs are physical channels which consist of various logical channels. Packet Common Control Channel (PCCH) – comprises logical channels for common control signalling of packet data. Packet Random Access Channel (PRACH) – Ul only. Uplink only, mapped on to the PDCH or the PACH. Used by the MS to initiate uplink transfer, e.g. sending data or paging response. Packet Paging Channel (PPCH) – downlink only PPCH is used to page an MS prior to downlink transfer. Packet Access Grant Channel (PAGCH) – downlink only PAGCH used in packet transfer establishment phase to send resource assignment to an MS prior to packet transfer. Note: Resource Assignment for a downlink assignment can be sent on the PACCH if the MS is currently involved in a Packet Transfer. Packet Broadcast Control Channel (PBCCH) – downlink only PBCCH broadcasts Packet Data specific information if the PBCCH is not allocated then the BCCH is used to broadcast Packet Data Specific Information.

1–12

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Um Air Interface

CCH

CCCH

BCCH

RACH

PCH/AGCH

CBCH

PCCH PBCCH

PCCCH

RACH

PPCH

PAGCH

PNCH

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–13

GPRS Review

ISSUE 1 REVISION 2

Timeslot Configuration
The BSS will support the GPRS carrier per cell. This carrier can be either the BCCH or Non–BCCH. GPRS timeslots are divided into Reserved and Switchable timeslots.

Reserved GPRS Timeslot
A reserved GPRS timeslot is a timeslot that is used only for GPRS services.

Switchable GPRS Timeslot
A switchable timeslot is a timeslot that can be switched from GPRS service to circuit switched service and vice versa.

GPRS vs CS
For switchable GPRS timeslots, circuit switched services always have priority. So, if the number of idle TCHs falls to zero and the BSS needs to set up a circuit switched call then the BSS will reconfigure a switchable GPRS TS to a circuit switched timeslot.

Timeslot Configuration
Reserved GPRS timeslots are placed above Switchable GPRS timeslots which are placed above circuit switched.

1–14

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Timeslot configuration

TS0

TCH

TS1

TCH

TS2

TCH

TS3

SW
TCH= Circuit switched TS SW= GPRS Switchable TS RES= GPRS Reserved TS

TS4

SW

TS5

RES

TS6

RES

TS7

RES

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–15

GPRS Review

ISSUE 1 REVISION 2

Packet Traffic Channels
One Packet Data Traffic Channel (PDTCH) is mapped to one physical channel. Up to 8 PDTCH with different TS but some frequency parameters can be allocated to one MS at the same time.

Packet Associated Control Channel (PACCH)
One Packet Associated Control Channel (PACCH) is mapped on to one physical channel. PACCH is dynamically allocated on a block basis. It provides signalling information including acknowledgements, power control and timing advance information. The PACCH can also be used for resource allocation messages, whilst the MS is already carrying out packet transfer. If a single PDTCH is assigned to an MS then the PACCH will be assigned on the same physical channel. If multiple PDTCHs are assigned to a mobile then the PACCH is always allocated on one of the Packet Data Channels (PDCHs) on which the PDTCHs are allocated. PACCH is bi-directional in nature. In other words whilst the assignment might be uplink or downlink, if PDTCHs are assigned on the uplink then one corresponding downlink timeslot must be monitored for the possible occurrences of the PACCH. At the same time, the MS can use the uplink assignment to send a PACCH at any time.

PDTCHs Dynamic Allocation
Dynamic Allocation allows multiple MSs to use the same uplink resource. This is accomplished by using the Uplink State Flag (USF) , a 3 bit flag that can be used to allow up to 7 mobiles to access the same resource. If, for example, a mobile is allocated in the assignment command timeslot 0, 2 and 3 then the mobile will monitor the downlink PDCH timeslots 0, 2 and 3 for its assigned USF value. If the mobile receives the USF on a downlink block then on the next uplink block the mobile will transmit and also on the next 3 blocks if USF granularity is set to 1.

UL PDTCH Fixed Allocation
Fixed Allocation uses the Packet Uplink Assignment to communicate a detailed fixed uplink resource allocation to the MS. This fixed allocation consists of a start frame, slot assignment and block assignment bitmap to represent the assigned blocks per timeslot. PACCH the MS will transmit a ul PACCH at any time. To gain a dl PACCH the fixed allocation will purposely have gaps to allow the MS to monitor all PDCH for a PACCH addressed to it. To this purpose the network will leave sets of 3 timeslot gaps in the uplink fixed allocation for the purpose of transmission of the dl PACCH. During transfer of RLC/MAC blocks a mobile station may request to continue the Tempoary Block Flow (TBF) by transmitting a Packet Resource Request on the ul PACCH. The network then responds with a Packet Resource Reassignment on the dl PACCH.

1–16

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

UL PDTCH Fixed Allocation

TS0

TS1 TS2 ÈÈÈÈÈ ÈÈÈÈÈ ÈÈÈÈÈ ÈÈÈÈÈ ÈÈÈÈÈ ÈÈÈÈÈ

TS3

TS4

TS5 TS6 ÈÈÈÈÈ ÈÈÈÈÈ ÈÈÈÈÈ ÈÈÈÈÈ ÈÈÈÈÈ ÈÈÈÈÈ

TS7

ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ B0ÈÈÈ B1ÈÈÈ B2 I ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ

B3 B4 B5 I

ÈÈÈ ÈÈÈ ÈÈÈ B6 ÈÈÈ B7 ÈÈÈ B8 IÈÈÈ B9 B10 B11 I ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈÈÈÈ

ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ B0 B1 B2 ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ

I

ÈÈÈ ÈÈÈ = MS assigned blocks + timeslots ÈÈÈ ÈÈÈ
GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ B3 B4 B5 I B6 B7 B8 I ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈ ÈÈÈÈÈÈ ÈÈÈ

B9 B10 B11 I

EMOTOROLA LTD. 2000

1–17

GPRS Review

ISSUE 1 REVISION 2

MS Classes with Multislot Capability
Phase 2+ Mobiles have the capability to use multiple slots in one TDMA frame in both uplink and downlink. They are split into classes 1 through 29. The mobiles are split into two types: S S Type 1 MS are not required to transmit and receive at the same time Type 2 MS are required to transmit and receive at the same time

Tt = Time to transmit. Tr = Time to receive. a = A measurement report is made b = No measurement report made a) = = b) = = c) = = 1 with frequency hopping 0 without frequency hopping 1 with frequency hopping or change from Rx to Tx 0 without frequency hopping or no change from Rx to Tx 1 with frequency hopping or change from Tx to Rx 0 without frequency hopping and no change from Tx to Rx

Type 1 MS are not required to transmit and receive at the same time Type 2 MS are required to be able to transmit and receive at the same time.

1–18

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

MS Classes with Multislot capabilities
Multislot Maximum number of slots Rx 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 26 27 28 29 1 2 2 3 2 3 3 4 3 4 4 4 3 4 5 6 7 8 6 6 6 6 6 8 8 8 8 8 8 1 1 2 1 2 2 3 1 2 2 3 4 3 4 5 6 7 8 2 3 4 4 6 2 3 4 4 6 8 Tx 2 3 3 4 4 4 4 5 5 5 5 5 NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA Sum 3 3 3 3 3 3 3 3 3 3 3 2 NA NA NA NA NA NA 3 3 3 2 2 3 3 3 2 2 2 Tta 2 2 2 1 1 1 1 1 1 1 1 1 a) a) a) a) a) 0 b) b) b) b) b) b) b) b) b) b) b) Minimum number of slots Ttb 4 3 3 3 3 3 3 2 2 2 2 2 3 3 3 2 1 0 2 2 2 2 2 2 2 2 2 2 2 Tra 2 1 1 1 1 1 1 1 1 1 1 1 a) a) a) a) 0 0 c) c) c) c) c) c) c) c) c) c) c) Trb Type Default 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 1

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–19

GPRS Review

ISSUE 1 REVISION 2

Fixed Allocation Timeslot Assignment
Fixed allocation presents particular restrictions to the allocation of Packet Data Channels (PDCHs) to multislot mobiles. In particular, the assignment must not conflict with the rules for Packet Associated Control Channel (PACCH) monitoring or transmission and measurements of neighbour cells. If for instance a multislot mobile station Class 4 is assigned a 3 timeslot Temporary Block Flow (TBF) downlink and no uplink TBF. In this example the Packet Downlink Assignment does not assign Measurement Mapping Parameters to the mobile so the MS must make neighbour cell power measurement in 24 out of every 26 TDMA frames. For multislot Class 4 mobiles the time needed for the MS to make a neighbour cell signal measurement and then get ready to transmit is 3 timeslots. Therefore the mobile can make a measurement in every TDMA frame. If the mobile is polled on timeslot 1, with a Relative Reserved Block Period (RRBP) of zero (to send PACCH from next RLC/MAC Block on timeslot 1), then the mobile will transmit a PACCH on timeslot 1. This transmission obeys the time needed for the mobile to transmit for multislot Class 4 which is 1 TS. It also conforms to the time needed to carry out neighbour cell measurements.

1–20

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Fixed Allocation Timeslot Assignment

Downlink
Ttb= 1 Tra= 3

ÄÄ É É ÉÉ ÄÄ ÉÉ ÄÄ ÉÉ ÄÄ
poll

01234567

ÉÉÉÉ É Ä Ä É É ÉÉ Ä ÉÉ Ä É É ÉÉ Ä ÉÉ Ä É É ÉÉ Ä ÉÉ Ä É

ÉÉ Ä É ÉÉ Ä É ÉÉ Ä É ÉÉ Ä É

01234567

ÉÉ É É ÉÉ É ÉÉ ÉÉ ÉÉ É ÉÉ ÉÉ É ÉÉ ÉÉ É ÉÉ ÉÉ É ÉÉ ÉÉ É ÉÉ É ÉÉ É

ÉÉÉÉ É É ÉÉ ÉÉ É ÉÉ ÉÉ É ÉÉ ÉÉ ÉÉÉÉ ÉÉ ÉÉÉÉ ÉÉ ÉÉÉÉ ÉÉ ÉÉÉÉ ÉÉ É É É É

ÉÉ É É ÉÉ ÉÉ ÉÉ ÉÉ ÉÉ ÉÉ

ÉÉ É É ÉÉ É ÉÉ É ÉÉ

RLC/MAC Block

Uplink

Multislot class 4 (Rx= 3, Tx= 1, Sum= 4, 3 timeslot downlink TBF, with a poll on timeslot 1 (the natural timeslot)

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–21

GPRS Review

ISSUE 1 REVISION 2

Mobility Management
Mobility Management (MM) activities are related to a GPRS subscriber and characterised by 3 MM states. Each state describes a different level of functionality and information allocated. These information sets are denoted by MM contexts at the SGSN and the MS.

Idle
In GPRS IDLE the subscriber is not attached to the GPRS Mobility Management. The MS and SGSN context hold no location or routing information for the mobile. The GPRS Mobile is seen as not reachable for PTP data transfers. PLMN selection and reselection are performed by the MS.

Standby State (Stby)
In Stby state the subscriber is attached to the GPRS Mobility Management. The MS and the SGSN have established MM contexts for the subscribers IMSI. The subscriber may now receive pages for data transfers. Transmission and reception of data is not possible in this state. S S S MS performs GPRS cell reselection and routing area MS updates SGSN if it enters a new RA MS may activate or deactivate PDP contexts

Ready State
The Ready state corresponds to the Stby state extended by location information for the subscriber at call level. The MS performs MM procedures to notify the network with the actual selected cell. GPRS cell selection and reselection may be done by the MS, or optionally controlled by the network. An identifier of the cell is placed in the BSSGP header of the packet data from the MS. The MS may send and receive PTP PDUs in this state. The network initiates no network pages for an MS in the Ready State. – – MS may activate or deactivate PDP contexts MS may stay in the Ready State with or without Radio Resources allocated.

1–22

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Idle/Stby/Ready

IDLE

IDLE

GPRS Attach GPRS Detach

GPRS Attach GPRS Detach or Cancel Location

STANDBY timer expiry

READY

STANDBY timer expiry or cancel location

READY

READY timer expiry or Force to STANDBY PDU transmission

READY timer expiry or Force to STANDBY or Abnormal RLC condition

PDU reception

STANDBY

STANDBY

MM State Model of MS

MM State Model of SGSN

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–23

GPRS Review

ISSUE 1 REVISION 2

Timing Advance
Packet Data Transmission is inherently ‘bursty’, by this the data transfer is not continuous. This presents problems with maintaining the correct timing advance for an MS during a data transfer.

1–24

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Timing advance

Data Transmission

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–25

GPRS Review

ISSUE 1 REVISION 2

Continuous Timing Advance
The initial timing advance is based on the single access burst carrying the Packet Channel Request. The estimated timing advance value is passed to the MS via the Packet Immediate Assignment. This value is used by the MS until continuous timing advance update provides a new value. In continuous timing advance the mobile sends in a special access burst in an idle slot for the network to derive the timing advance. In the downlink the network sends a timing advance value via the Packet Associated Control Channel (PACCH) which is transmitted during the idle timeslots of the 52 multiframe. Timing Advance Index gives the MS the position to send the access burst. For example, TAI = 1 refers to idle timeslot 2. The network will then update the MS timing advance in the next Timing Advance Message and also the next 3 TA messages. The mobile only has to read the message once.

1–26

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Timing advance
52-multiframe number n: Uplink TAI=0 B0 B1 B2 0 B3 B4 B5 1 B6 B7 B8 TAI=1 2 B9 B10 B11 3

Downlink TA message 1 52-multiframe number n + 1: Uplink TAI=2 B0 B1 B2 4 B3 B4 B5 5 B6 B7 B8

TAI message 1 TAI=3 6 B9 B10 B11 7

Downlink TA message 1 52-multiframe number n + 2: Uplink TAI=4 B0 B1 B2 8 B3 B4 B5 9 B6 B7 B8

TAI message 1 TAI=5 10 B9 B10 B11 11

Downlink TA message 2 52-multiframe number n + 3: Uplink TAI=6 B0 B1 B2 12 B3 B4 B5 13 B6 B7 B8

TAI= message 2 TAI=7 14 B9 B10 B11 15

Downlink TA message 2 52-multiframe number n + 4: Uplink TAI=8 B0 B1 B2 16 B3 B4 B5 17 B6 B7 B8

TAI= message 2 TAI=9 18 B9 B10 B11 19

Downlink TA message 3 52-multiframe number n + 5: Uplink TAI=10 B0 B1 B2 20 B3 B4 B5 21 B6 B7 B8

TAI message 3 TAI=11 22 B9 B10 B11 23

Downlink TA message 3 52-multiframe number n + 6: Uplink TAI=12 B0 B1 B2 24 B3 B4 B5 25 B6 B7 B8

TAI message 3 TAI=13 26 B9 B10 B11 27

Downlink TA message 4 52-multiframe number n + 7: Uplink TAI=14 B0 B1 B2 28 B3 B4 B5 29 B6 B7 B8

TAI= message 4 TAI=15 30 B9 B10 B11 31

Downlink

TA message 4 idle bursts are numbered from 0 to 31

TAI= message 4

B0 – B11= Radio blocks

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–27

GPRS Review

ISSUE 1 REVISION 2

Mobile Originated Packet Transfer
On entry into a cell, the mobile will read System Information Messages 3,4,7 or 8. The cell, if it supports GPRS, will transmit System Information message 13 and optionally 14 and 15. The MS initiates the Packet Access Procedure by the sending of a Channel Request message on the RACH. The RSS forwards the RACH to the Pack Control Unit (PCU). The PCU then generates the Immediate Assignment allocating a Packet Data Channel (PDCH) from its pool of resources. The MS now sends on the PDCH a Packet Resource Request requesting Fixed Allocation , which will indicate the priority of the data, the number of octets of data the MS uses to transfer and the requested bandwidth, e.g. 500 Kbps. The PCU will respond with the Packet Resource Assignment on the Packet Associated Control Channel (PACCH). This message assigns timeslots to the mobile and the allocated blocks to transmit on. Also within the message will be the Temporary Flow Indentifier (TFI) to identify the Temporary Block Flow (TBF) for transmitting the air interface. TFI Temporary Flow Indentifier TBF Temporary Block Flow

1–28

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Mobile Originated Packet Transfer (No PBCCH)

PCU

RSS

MS

SYSTEM INFORMATION

SYSTEM INFORMATION BCCH

PACKET CHANNEL REQUEST RACH GSL TO RSL

PACKET IMMEDIATE ASSIGNMENT AGCH

PACKET RESOURCE REQUEST PACCH

PACKET RESOURCE ASSIGNMENT PACCH DATA BLOCK PDTCH

DATA BLOCK PDTCH

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–29

GPRS Review

ISSUE 1 REVISION 2

Downlink Mobile Terminated Packet Transfer
As before, on entry to the cell the mobile will read system information messages on the BCCH. If GPRS is present in the cell then the system information messages will indicate this and also the presence of system information message 13. The Information message 13 gives the information of power control, priority access, classes allowed. Information message 14 gives information of reference frequency lists and mobile allocations applicable to packet access in a cell. Information message 15 gives information on packet power control interference measurements. If the mobile is in the Standby state then the network may page the mobile to transfer PDUs. Paging sent from the SGSN will be handled by the Packet Control Unit (PCU) and dependent on the state of the mobile will result in paging by routing area or in a cell. The mobile will respond with an RACH with a cause value indicating GPRS. The RSS will pass this channel request to the PCU which will allocate a PDCH for 2 phase access. This is sent to the mobile on the AGCH. The set up is now as before as mobile originated Packet Transfer.

1–30

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Downlink Mobile Terminated Packet Transfer (No PBCCH)

PCU

RSS

MS

SYSTEM INFORMATION SYSTEM INFORMATION 3, 13 BCCH PAGING PACKET PAGING REQUEST (PCH) PACKET CHANNEL REQUEST (RACH) PACKET IMMEDIATE ASSIGNMENT (AGCH)

PACKET RESOURCE REQUEST PACCH

PACKET RESOURCE ASSIGNMENT PACCH PDU (PDTCH)

PDU (PDTCH)

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–31

GPRS Review

ISSUE 1 REVISION 2

Uplink Packet Transfer
Once the Access and Assignment is complete, the mobile awaits its allocated blocks on the allocated Packet Data Channels (PDCHs). Once the allocated blocks arrive the MS shall begin to transmit Radio Link Control (RLC) data blocks on its Packet Data Traffic Channels (PDTCHs). These RLC data blocks are all uniquely identified by the Temporary Flow Indentifier (TFI). The unique identification on the TFI is included in every RLC data or control block related to the Temporary Block Flow (TBF). Because each radio block contains an identifier (TFI) all received blocks are correctly associated a particular LLC frame and a particular MS. The network will acknowledge transfers by sending Packet Uplink ACK/NACK messages on the Packet Associated Control Channel (PACCH) during gaps in the uplink allocation. The message contains the status of the received RLC data blocks. The message may also update the timing advance, power control parameters and assign uplink resources to a fixed mobile. The mobile will continue transmitting the RLC data blocks, retransmitting those data blocks indicated by the network until it reaches its last RLC data block.

1–32

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Uplink Packet Transfer

Network
ACCESS AND ASSIGNMENT

MS

DATA BLOCK DATA BLOCK DATA BLOCK DATA BLOCK TEMP ACK/NACK DATA BLOCK DATA BLOCK DATA BLOCK DATA BLOCK PACKET RESOURCE ASSIGNMENT DATA BLOCK DATA BLOCK (LAST) FINAL PACKET ACK//NACK

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–33

GPRS Review

ISSUE 1 REVISION 2

Mobile Terminated Packet Transfer
As before with Mobile Originate Packet Transfer the network assigns a unique Temporary Flow Identifier (TFI) with regards to the downlink Temproary Block Flow (TBF) and a set of Packet Data Channels (PDCHs) to be used for the downlink transfer and a TBF stating time (optional ). The MS on reception of the downlink assignment will either attempt to decode every downlink block on its assigned PDCHs or it is sent on TBF starting time, wait on the CCCH until the TDMA framenumber indicated by the TBF starting time. When the mobile receives an Radio Link Control (RLC) data block addressed to itself and with a polling indication in the uplink radio block specified in the header, then the mobile will transmit an ACK/NACK or control message (mobile will only transmit a RLC/MAC control message instead of ACK/NACK, at most, every fourth time it is polled). The network initiates a release of a downlink TBF by sending an RLC data block with the Final Bit Indicator (FBI) and a valid polling indication. The mobile shall transmit a Packet ACK/NACK in the uplink radio block specified.

1–34

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Mobile terminated packet transfer

PCU
ACCESS AND ASSIGNMENT

MS

DATA BLOCK PDTCH

DATA BLOCK (POLLING) PDTCH

TEMP PACKET ACK/NACK PACCH

DATA BLOCK PDTCH

DATA BLOCK (LAST/POLLING)

FINAL PACKET ACK/NACK PACCH

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–35

GPRS Review

ISSUE 1 REVISION 2

Radio Link Control (RLC)
The Radio Link Control (RLC) function is responsible for: S S S Interface allowing transfer of UC PDUs between the Logical Link Control (LLC) Layer and the Media Access Control (MAC) function Segmentation of LLC PDUs into RLC data blocks and re-assembly of RLC data blocks into LLC PDUs Backwards Error Correction (BEC) Procedures enabling selective retransmission of RLC data blocks

An RLC connection comprises two peer entities. Each RLC endpoint has a receiver that receives RLC data blocks. Each RLC endpoint has a transmitter that transmits RLC data blocks.

1–36

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Radio link control (RLC)

LLC

LLC

RLC

RLC

MAC Physical Layer

MAC Physical Layer

FH

INFORMATION FIELD

FCS

LLC

BH INFO FIELD BCS BH INFO FIELD BCS BH INFO FIELD BCS

RLC/MAC

NORMAL BURST

NORMAL BURST

NORMAL BURST

NORMAL BURST

PHYSICAL LAYER

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–37

GPRS Review

ISSUE 1 REVISION 2

RLC Data ACK/NACK
The Radio Link Control (RLC) peers each have a receive and transmit window of 0 – 127. The window size is 64 blocks. The sending side can transmit blocks within a window of 64 blocks and the receiving side periodically sends temporary ACK/NACK messages. Every such message acknowledges all correctly received blocks and can request erroneously received RLC data blocks for retransmission. Each RLC data block contains a block sequence number (BSN) in the range 0 – 127. In the send side a variable V(s) denotes the next in sequence RLC data block to be sent, on the receive side a variable V(R) denotes the next in sequence RLC block to be received. Acknowledge state variables, the send side has an acknowledge variable V(a) that contains the BSN of the oldest RLC block that has not been acknowledged. On the Receive side the variable V(Q) denotes the oldest RLC data block that has not been received. The send side maintains an Acknowledge state array V(B), an array of 128 elements indicating the acknowledgement status of transmitted RLC data blocks that are either pending – ACK or NACKED or INVALID. The order of transmitted RLC blocks is the oldest RLC block that has been NACKED. If the sliding window is still open, i.e. V(S) <V(A) +K then the next RLC data block with BSN = V(S) shall be transmitted and the V(B) array element set to PENDING – ACK. Once the V(S) = V(A) + K, in other words the window is stalled. Then the send side shall transmit the oldest element in V(B) that has the value PENDING – ACK.

1–38

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Radio Link Control (RLC) data Ack/Nack

MS
RLC BLOCK BSN= 0 Va= 0 RLC BLOCK BSN= 1 RLC BLOCK BSN= 2 ACK 0, 1 NACK 2 BSN= 2 BSN= 3 Va= 2

PCU

Vq= 2

BSN= 65 BSN= 2 Stalled BSN= 3 ACK 2 – 65 BSN= 66

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–39

GPRS Review

ISSUE 1 REVISION 2

Release of Uplink
Temporary Block Flow (TBF)
The mobile station sends in the Radio Link Control (RLC) data block a Countdown Value (CV) to indicate to the network the last RLC data block that will be sent in the uplink TBF. The CV is calculated as a value dependant on the number of Timeslots assigned on the uplink and the total number of RLC data blocks in the TBF and a broadcast parameter BS – CV – MAX. BS – CV – MAX is the number of blocks the countdown will begin before the last block is transmitted. For example, as BS – CV – MAX of 4 would mean that the last 4 blocks will count down to 0. A CV of 15 is the norm value for RLC data blocks.

1–40

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Release of uplink

15

3

2

1

0

BS_CV_MAX= 4

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–41

GPRS Review

ISSUE 1 REVISION 2

GPRS Attach
The procedure as shown opposite details a combined GPRS and IMSI attach. Taking each state in turn: 1. The MS initiates the procedure by issuing an ‘Attach Request’ which includes; IMSI or P–TMSI – – – – – – 2. Old RAI Classmark CKSN Attach Type DRX Old P–TMSI signature (Routing Area Identification) (multislot capabilities, GPRS cipher algorithms) (Cipher Key Sequence Number) (GPRS/IMSI/both) (discontinuous reception) (if one exists)

The New SGSN sees from the RAI sent by the MS that it was previously attached to the Old SGSN, therefore the New SGSN sends an ‘Identity Request’ message to the Old SGSN. The response back from the Old SGSN will include the IMSI and Authentication Triplets. If the MS is unknown to the New and Old SGSNs, then an ‘Identity Request’ is sent, and the response should contain its IMSI. Authentication and ciphering procedures may be initiated to ensure MS and data security. A further check can be made of the MS against its IMEI. If the SGSN has changed since the MNS was last attached to the network: The SGSN sends an ‘Update Location’ to the HLR: – – – SGSN number SGSN address IMSI

3. 4. 5. 6. A.

B. C. D.

HLR send cancel location to Old SGSN The Old SGSN acknowledges before removing Mobility Management (MM) and PDP contexts. HLR inserts subscriber information into New SGSN – – IMSI GPRS Subscription data

E. F. 7.

New SGSN acknowledges and creates new MM context HLR updates its own records and returns an acknowledgement to the New SGSN. Assuming the Gs interface exists then the VLR will be updated by use of ‘Location Update’ by the SGSN. This is particularly true when considering a combined GPRS/IMSI attach: Location Update: – – – – New LAI IMSI SGSN number Location Update Type GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000

A.

1–42

ISSUE 1 REVISION 2

GPRS Review

Attach
MS BSS NEW SGSN OLD SGSN GGSN EIR NEW MSC/VLR HLR OLD MSC/VLR

1. Attach Request 2. Identification Request 2. Identification Response 3. Identity Request 3. Identity Response 4. Authentication 5. IMEI Check 6a. Update Location 6b. Cancel Location 6c. Cancel Location Ack 6d. Insert Subscriber Data 6e. Insert Subscriber Data Ack 6f. Update Location Ack 7a. Location Updating Request 7b. Update Location 7c. Cancel Loc Ack 7d. Cancel Loc Ack 7e. Insert Subscriber Data 7f. Insert Subscriber Data 7g. Update Location Ack 7h. Location Updating Accept 8. Attach Accept 9. Attach Complete 10. TMSI Reallocation Complete

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–43

GPRS Review

ISSUE 1 REVISION 2

B.

New VLR indicates to HLR of a location update HLR takes over and cancels the location in the Old VLR (c and D), before inserting new subscriber information in the New VLR (e). Finally the HLR acknowledges to the New VLR.

C. 8.

The New VLR acknowledges the ‘Location Update’ back to the SGSN. The SGSN sends an ‘Attach Accept’ to the MS containing: – – P–TMSI VLR TMSI

9. 10.

If the P–TMSI or VLR TMSI have been changed by the SGSN then the MS needs to acknowledge. If the VLR TMSI has been changed and acknowledged by the MS, then the SGSN needs to acknowledge back to the VLR.

1–44

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Attach
MS BSS NEW SGSN OLD SGSN GGSN EIR NEW MSC/VLR HLR OLD MSC/VLR

1. Attach Request 2. Identification Request 2. Identification Response 3. Identity Request 3. Identity Response 4. Authentication 5. IMEI Check 6a. Update Location 6b. Cancel Location 6c. Cancel Location Ack 6d. Insert Subscriber Data 6e. Insert Subscriber Data Ack 6f. Update Location Ack 7a. Location Updating Request 7b. Update Location 7c. Cancel Loc Ack 7d. Cancel Loc Ack 7e. Insert Subscriber Data 7f. Insert Subscriber Data 7g. Update Location Ack 7h. Location Updating Accept 8. Attach Accept 9. Attach Complete 10. TMSI Reallocation Complete

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–45

GPRS Review

ISSUE 1 REVISION 2

GPRS Detach
With respect to the diagrams shown opposite we should consider the three defined detach procedures. The top diagram on the opposite page details the Detach procedure that is initiated by the MS. 1. The MS initiates by sending Detach Request – – 2. 3. 4. 5. Detach Type Switch Off (switch off or not)

If GPRS detach then the PDP context needs to be deleted in the GGSN If IMSI detach, the SGSN sends IMSI detach to the VLR If the MS wishes to remain IMSI attached and remove its GPRS context in the VLR If the switch off parameter indicated that the MS was being switched off, then the ‘Detach Accept’ is not sent.

If the detach is initiated by the SGSN, then the sequence is similar to that above, except that the initial message detailed in 1 above is started by the SGSN. Stages 2 and 4 above are used as shown in the middle diagram on the opposite page. The detach sequence could be started by the HLR as shown in bottom diagram on the oppsite page, by the use of a ‘Cancel Location’ MAP message. Following the ‘Cancel Location’ message, the procedure is much the same as for the SGSN initiated detach procedure.

1–46

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Detach
MS BSS SGSN GGSN MSC/VLR HLR

1. Detach Request 2. Delete PDP Context Request 2. Delete PDP Context Response 3. IMSI Detach Indication 4. GPRS Detach Indication 5. Detach Accept

MS

BSS

SGSN

GGSN

MSC/VLR

HLR

1. Detach Request 2. Delete PDP Context Request 2. Delete PDP Context Response 3. GPRS Detach Indication 4. Detach Accept

MS

BSS 2. Detach Request

SGSN

GGSN

MSC/VLR

HLR

1. Cancel Location 3. Delete PDP Context Request 3. Delete PDP Context Response 4. GPRS Detach Indication 5. Detach Request 6. Cancel Location Ack

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–47

GPRS Review

ISSUE 1 REVISION 2

Paging for GPRS Downlink Transfer
An MS has to be paged by the SGSN before a downlink transfer can occur. The paging process is shown opposite and detailed below: 1. 2. SGSN receives Protocol Data Units (PDUs) for an MS from the network and pages the MS. The SGSN sends a BSSGP Paging Request: – – – – – – 3. IMSI P–TMSI Area Channel Needed QoS DRX (Routing Area) (indicates GPRS paging) (Quality of Service)

The BSS pages the MS with: – – P–TMSI Channel Needed

4. 5.

The MS shall respond by use of a Receive Ready or Information frame The BSS, upon receipt of the Logical Link Control (LLC) frame, adds an identifier of the cell and sends the complete LLC frame to the SGSN.

1–48

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

GPRS Paging Area

MS

BSS

SGSN

1. PDP PDU 2. Paging Request 3. GPRS Page Request 4. Any LLC Frame 5. Any LLC Frame

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–49

GPRS Review

ISSUE 1 REVISION 2

PDP Context Activation
PDP Context Activation is shown in the diagram oppsite and follows the sequence shown here: 1. The MS sends an ‘Activate PDP Context Request’ containing: – – – – – – 2. 3. NSAPI PDP type PDP Address Access Point Name DNS) QoS Requested PDP Configuration Options (leaves blank to request dynamic address) (reference point to external network, via

Security Functions may be executed The SGSN then determines the GGSN to address via a combination of: – – – – – – – – – – – – – – – – IMSI + NSAPI (= TID) (GGSN will allocate dynamic PDP Address if left blank above) PDP Type PDP Address Access Point Name QoS Negotiated TID Selection Mode PDP Configuration Options TID PDP Address BB Protocol Reordering Required PDP configuration options QoS Negotiated Cause (TCP or UDP over Gn) (reorder of N–PDUs from GGSN before delivery) (subscribed or non–subscribed APN)

‘Create PDP Context Request’ containing:

‘Create PDP Context Response’ containing:

4.

The SGSN inserts the NSAPI along with the GGSN address in its PDP context. If the MS requested a dynamic address then it is inserted into the SGSNs PDP context. SGSN returns: – – – – – – PDP Type PDP Address NSAPI QoS Negotiated Radio Priority Level PDP Configuration Options

The SGSN is now able to route PDUs between the GGSN and MS.
1–50

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

PDP Context

MS

SGSN

GGSN

1. Activate PDP Context Request 2. Security Functions 3.Create PDP Context Request 3.Create PDP Context Response 3.Activate PDP Context Accept

PDP Context Activation Procedure

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–51

GPRS Review

ISSUE 1 REVISION 2

In the diagram opposite the network is requesting PDP context activation. In this instance the GGSN has received PDP PDUs from an external network and because no PDP context has been previously established then the network has to start the sequence. The network may employ techniques such as: Mobile station Not Reachable for GPRS flag (MNRG), the SGSN, GGSN and HLR, which will prevent the GGSN from trying to contact the mobile when it is switched off or out of coverage area. The GGSN may decide to discard future PDP PDUs as a result of previous unsuccessful delivery attempts. The GGSN may store the address of the SGSN for a particular PDP context and so eliminate the need for communicating with the HLR. 1. 2. The GGSN has received PDP PDU for an MS and has decided to initiate the Network–Requested PDP Context Activation procedure. The GGSN may need to request routing information from the HLR for a mobile it is unaware of the supporting SGSN. The response from the HLR would include: IMSI SGSN Address Mobile State Not Reachable Reason (containing MNRG flag) 3. GGSN sends a ‘PDU Notification Request’ containing: IMSI PDP Type PDP Address With the SGSN responding to the request to indicate that it will communicate with the MS. 4. The SGSN sends a ‘Request PDP Context Activation’ containing: PDP Type PDP Address 5. The PDP context activation procedure detailed earlier is now used to complete the process, before PDUs can be transported.

1–52

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

PDP Context

MS

SGSN

HLR

GGSN 1. PDP PDU

2. Send Routeing Info for GPRS 2. Send Routeing Info for GPRS Ack 3.PDU Notfication Request 3.PDU Notfication Response 4.Request PDP Context Activation 5. PDP Context Activation Procedure

Successful Network-requested PDP Context Activation Procedure

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–53

GPRS Review

ISSUE 1 REVISION 2

PDP Context Modification Procedure
In the upper diagram opposite the PDP context can be modified by the procedure shown. This would be requested in particular instances, e.g. change of Quality of Service (QoS) parameters, possibly because the GGSN was unable to provide the full range of parameters. Thus: 1. The SGSN could request an ‘Update PDP Context Request’ TID Qos Negotiated 2. The GGSN will return with: TID QoS Negotiated 3. The SGSN sends a ‘Modify PDP Context’

NSAPI QoS Negotiated Radio Priority Level 4. The MS should acknowledge the new parameters before they take effect.

PDP Context Deactivation
The next diagrams detail how the PDP context may be deactivated PDP Context Deactivation Initiated by MS Procedure: 1. 2. 3. 4. MS sends a ‘Deactivate PDP Context Request’ containing the NSAPI to the SGSN. Security Functions (optional) The SGSN sends a ‘Delete PDP Context Request’ containing TID. GGSN removes PDP context and sends a valid response. The SGSN sends a ‘response’ to the MS containing the NSAPI.

PDP Context Deactivation Initiated by GGSN Procedure
1. 2. The GGSN sends a ‘ Delete PDP Context Request’ containing the TID. The SGSN sends a ‘Deactivate PDP Context’ message together with the NSAPI to the MS, which deletes the PDP context and responds with the same NSAPI to the SGSN. The SGSN then responds with the TID to the GGSN. If the PDP Address was dynamic, then the GGSN releases the PDP Address for use by a subsequent activation. GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000

3.

1–54

ISSUE 1 REVISION 2

GPRS Review

Altering PDP Context
MS SGSN GGSN

1.Update PDP Context Request 2.Update PDP Context Response 3. Modify PDP Context Request 4. Modify PDP Context Accept

PDP Context Modification Procedure
MS SGSN GGSN

1. Deactivate PDP Context Request 2. Security Functions 3. Delete PDP Context Request 3. Delete PDP Context Response 4. Deactivate PDP Context Accept

PDP Context Deactivation Initiated by MS Procedure
MS SGSN GGSN

1. Delete PDP Context Request 2. Deactivate PDP Context Request 2. Deactivate PDP Context Accept 3. Delete PDP Context Accept

PDP Context Deactivation Initiated by GGSN
EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–55

GPRS Review

ISSUE 1 REVISION 2

Routing Area Update Procedure
When an MS is on the move it will cross cell boundaries and will need to update the cell information held as part of its Mobility Management (MM) context in the MS and SGSN. Routing Area updates will be required for an MS on the move and enters a new routing area (RA) or when a periodic RA update timer has expired. The RA size is dependent upon network implementation. A RA is identified as a subset of a single LA and so cannot span more than one location area (LA). The following rules apply to routing area: S S S RAI (Routing Area Identity) = MCC + MNC + LAC + RAC – (MCC – Mobile Country Code)

LAI (Location Area Identity) = MCC + MNC + LAC – (MNC – Mobile Network Code)

CGI (Cell Global Identity) = LAI + CI – – (LAC – Location Area Code) (RAC – Routing Area Code)

If a mobile moves between cells which are supported by a single SGSN and is in the READY or STANDBY MM state, then it performs an intra–SGSN Routing area Update as shown opposite and detailed below: 1. The MS sends a ‘Routing Area Update Request’ containing: – – – 2. 3. 4. Old RAI Old P–TMSI Update Type (RA update indicated)

Security Functions may be executed The SGSN validates the MS and may issue a new P–TMSI If a new P–TMSI is allocated then the MS needs to acknowledge receipt of this.

If the routing area update fails over a number of times, then the MS should enter the IDLE state.

1–56

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

MS

BSS

SGSN

1. Routeing Area Update Request 2. Security Functions 3. Routeing Area Update Accepts 4. Routeing Area Update Acknowledge

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–57

GPRS Review

ISSUE 1 REVISION 2

Combined RA/LA Update in the case of Inter SGSN RA Update Procedure
If the moving MS crosses cell/Routing Area (RA) boundaries which are supported by different SGSNs, then an Inter SGSN RA Update should be performed. There may be a need to update the Routing Area (RA) and additionally the LA may need to be updated for the IMSI attached mobile. To prevent excess messages to the VLR/HLR, then the LA update can be combined into the GPRS RA update. A combined RA/LA update is shown opposite and detailed below: 1. The MS sends a ‘Routing Area Update Request’ containing: – – – Old RAI Old P–TMSI Signature Update Type (allocated by SGSN)

The BSS shall add an identifier of the cell where the message was received before passing the message to the SGSN. 2. The New SGSN shall be able to determine the Old SGSN from the old Routing Area identity (RAI) and the new RAI and Location Area Identity (LAI) from the cell identifier added by the BSS.

The new SGSN context request to the Old SGSN containing: – – – – Old RAI Temporary Logical Link Identity (TLLI) Old P–TMSI Signature New SGSN Address

In order to get the MM and PDP contexts for the MS. The Old SGSN responds with: – – – MM Context PDP Contexts LLC Acknowledge

The Old SGSN stores the New SGSN Address until the old MM context is cancelled to allow the Old SGSN to forward data packets to the new SGSN. The Old SGSN starts a timer. 3. 4. 5. Security Functions. Optional New SGSN sends ‘SGSN Context Acknowledge’ to Old SGSN. The Old SGSN starts tunnelling of buffered N–PDUs to the New SGSN. Additional N–PDUs received from the GGSN before timer in 2) above expires is also tunneled. The New SGSN sends ‘Update PDP Context’ to GGSN: – –
1–58

6.

New SGSN Address, TID and Negotiated Quality of Service (QoS). GGSN responds with TID. GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY
EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Review

Combined RA/LA Update
MS BSS NEW SGSN OLD SGSN GGSN NEW MSC/VLR HLR OLD MSC/VLR

1. Routing Area Update request 2. SGSN Context Request 2. SGSN Context Response 3. Security Functions 4. SGSN context Acknowledge 5. Forward packets 6. Update PDP Context Request 6. Update PDP Context Response 7. Update location 8. Cancel Location 8. Cancel Location Ack 9. Insert Subscriber Data 9. Insert Subscriber Data Ack 10. Update Location Ack 11. Location Updating Request 12a. Update Location 12b. Cancel Location 12c Cancel Location Ack 12d. Insert Subscriber Data 12e. Insert Subscriber Data Ack 12f. Update Location Ack 13. Location Updating Accept 14 Routing Area Update Accept 15. Routing Area Update Complete 16. TMSI Reallocation Complete

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

1–59

GPRS Review

ISSUE 1 REVISION 2

7.

The New SGSN informs the HLR of the change of SGSN by sending ‘Update Location’: – – – SGSN Number SGSN Address IMSI

8. 9.

HLR sends a ‘Cancel Location’ to the Old SGSN in order to remove the MM and PDP contexts. The HLR ‘Inserts Subscriber Data’ into the New SGSN: – – IMSI GPRS Subscription Data

10. 11.

The HLR acknowledges the ‘Update Location’ with IMSI to New SGSN. The New SGSN ‘Location Update Request’ to the VLR to update the LA, containing: – – – – New LAI IMSI SGSN Number Location Update Type

12. 13. 14.

If the Location Update is Inter–MSC the New VLR informs the HLR. The HLR cancels the old location and inserts the new data into the New VLR. If the location update is successful the new VLR allocates a new TMSI to the SGSN. The New SGSN establishes MM and PDP contexts for the MS and responds to the MS with: – – – – P–TMSI VLR TMSI LLC Acknowledge P–TMSI Signature

15. 16.

MS confirms allocation of TMSI and P–TMSI and LLC acknowledge. The New SGSN sends TMSI reallocation complete message to VLR.

1–60

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 2

PCU Architecture

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Chapter 2 PCU Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Control Unit (PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The GPRS solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Equipage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC Site Device Equipage Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU Site Device Equipage Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Interface Control Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU System Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packet Resource Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell INS/OOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSL and RSL State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Carrier Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Originated Packet Access and Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Terminated Packet Access and Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frame Relay Functional Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb Functional Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb Router (GR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gateway Transmit Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Service Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flow Control Buffer Manager (FBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault Detection and Handling System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Audit Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU Central Authority (pCA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

i
2–1 2–2 2–4 2–6 2–6 2–8 2–10 2–12 2–14 2–16 2–18 2–20 2–22 2–24 2–26 2–28 2–30 2–32 2–34 2–36 2–36 2–36 2–36 2–38 2–40 2–42 2–44 2–46

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

iii

ISSUE 1 REVISION 2

iv

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Objectives

Objectives
On completion of this section the student will be able to: S S Understand the generic function of the Packet Control Unit (PCU) Entities Identify the functional units of the: – – – – S PCU System Processor Packet Resource Processor Packet Interface Control Processor PCI to PCI Bridge

Identify the signalling between functional entities of the PCU and the BSS and SGSN

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–1

Packet Control Unit (PCU)

ISSUE 1 REVISION 2

Packet Control Unit (PCU)
The new BSS functionality for GPRS mainly resides at the Packet Controller Unit (PCU). The PCU includes the handling of frame relay, Network Services Signalling, BSSGP signalling, routing of signalling messages, Radio Link Control (RLC) and Media Access Control (MAC) preload and transferring of user data. User data is routed to the PCU via the CCU uplink from the BTS to the BSC and then over E1 to the PCU. At the PCU the RLC Blocks are reformulated in Logical Link Control (LLC) frames and forwarded to the SGSN. BSSGP signalling and NS signalling shall occur between the PCU and the SGSN using frame relay protocol. There is also signalling between existing functional process at the BSC such as the BSP and the PCU via the E1 Span, as well as between the PCU and Channel Coders.

2–2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Packet Control Unit (PCU)

SGSN

NS – SIG BSSGP SIG

GDS (LAPD) GSL

BSC
GDS (TRAU)

PCU

RSL RTF

BTS

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–3

Packet Control Unit (PCU)

ISSUE 1 REVISION 2

The GPRS solution
The GPRS solution is a compact PCI based solution. The CPCI–PCU cabinet is connected to the BSC using E1 spans and the SGSN by E1 using frame relay as the network service. The Packet Control Unit (PCU) comprises 3 different boards which are defined below:

MPROC
The MPROC is the system slot processor which is responsible for bus arbitration and CPCI clock generation. It shall contain interface and BSSGP protocol functions and shall be called the PCU System Processor. Only one PCU System Processor (PSP) may be equipped at a PCU.

DPROC
The DPROC boards are non–system slot boards which have two PMC sockets and can host two different functions. The DPROC can be configured as either a Packet Interface Control Processor (PICP) or as a Packet Resource Processor (PRP). If configured as the PICP the DPROC shall contain up to 2 PMC modules to provide the E1 interfaces. The E1 interface can support the Gb interface or the GPRS Data Stream (GDS) interface, including the GPRS Signalling Link (GSL). If configured as a PRP, the DPROC performs Air Interface scheduling and either one or two of the PMC sockets may also be used for the PMC modules which provide GDS links for data only not signalling. A single processor can support a pool of 120 radio timeslots of which 30 radio timeslots can be active at any one time.

Bridge
The Bridge known as the PCI to PCI Bridge (PPB) allows an MPROC to be linked to a separate bus. The PPB and MPROC are paired boards.

2–4

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Packet Control Unit (PCU)

PCU Cage

PRP or PICP

PRP or PICP

PRP or PICP

PRP or PICP

PRP or PICP

PRP or PICP

PRP or PICP

PRP or PICP

PRP or PICP

PRP or PICP

PRP or PICP

1

2

3

4

5

6

7

8

9

10

11 12 13

14 15 16

EMOTOROLA LTD. 2000

PRP or PICP
2–5

PSP

PPB

PSP

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

PPB

Device Equipage

ISSUE 1 REVISION 2

Device Equipage
BSC Site Device Equipage Hierarchy
Two new devices, the Packet Control Unit (PCU) and GPRS Signalling Link (GSL) may be equipped and managed at the BSC. The PCU appears much like a remote site at the BSC and may only be equipped at the BSC. A PCU device is equipped and managed at the BSC. A GSL device is managed at both the BSC and the PCU site. The operator must equip the GSL at the PCU site and a corresponding GSL device will be equipped at the BSC.

2–6

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

BSC Site Device Equipage Hierarchy
BSC SITE

BTS SITE CAB

PCU

CELL

CAGE

COMB KSW GCLK BSP BTP GPROC CSFP DHP EAS

MSI MMS*

DRI

LCF OMF BTF

XBL MTL

OML CBL GSL*

PATH

16Kbps RSL

64Kbps RSL

RTF

Associated RTF
*Indicates auto-equipped device

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–7

Device Equipage

ISSUE 1 REVISION 2

PCU Site Device Equipage Hierarchy
When a Packet Control Unit (PCU) device is equipped at the BSC a CAB and CAGE will automatically be equipped at the PCU site. Devices managed under the PCU site use the text “pcu” rather than a location number in commands, e.g. “equip pcu DPROC”.

2–8

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

PCU Site – Device Equipage Hierarchy

When a PCU is equipped at the BSC, a CAB and CAGE device will be automatically equipped at the PCU site. The PCU device exists only at the BSC. The highest device in the PCU site equippage hierarchy is the CAB device.

CAB* CAGE*

PSP

DPROC (PICP) MSI

DPROC (PRP) MSI

MMS*

MMS*

GBL

GDS (TRAU)

GDS (LAPD) GSL

GDS (TRAU)

* Indicates auto-equipped device

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–9

Device Equipage

ISSUE 1 REVISION 2

Packet Interface Control Processor
The Packet Interface Control Processor (PICP) is a function residing on a DPROC. A PICP is made up of functional units. A Gb functional unit to terminate the Gb links, the function to determine whether an Logical Link Control (LLC) frame is user data, SGSN – MS signalling or BSSGP signalling. The LLC frame is then routed to the appropriate board based on LLC frame type. S S S S Route signalling for paging messages to appropriate cell. Routing of flushing of queued SDU at appropriate cell Routing flow control of downlink traffic Queuing MS Packets based on priority queues

GPRS Signalling Link (GSL) LAPD functional unit for synchronisation of LAPD link over GSL between the PCU and the BSC. A TRAU functional unit created for the synchronisation and handling of Packet Control Unit (PCU) frames between the PCU and the BSC. A PICP Status functional unit for debugging mechanisms, statistics and alarms. Finally an I/O functional unit is created for routing messages between the functional units on the PICP and the functional units on the PCU System Processor (PSP).

2–10

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

Packet Interface Control Processor
To PRP To PSP

PICP PMC 860 Dual E1 BSC Comm E1 TRAU I/O TRAU FU Gateway Manager (GWM) TO GWM FUs PMC 860 Dual E1 Gb link E1 FRAME RELAY Gb link E1 PPC 860 Dual E1 GB FU To other GB FUs

BSC Comm E1

GSL LAPD MGR

PP750

PICP GSL/TRAU Frame Relay

I/O

PICP status (alarms, stats, debugging)

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–11

Device Equipage

ISSUE 1 REVISION 2

PCU System Processor
The PCU System Processor (PSP) resides on the MPROC. As well as control of bus arbitration the PSP has the following functional units:

GB Manager
GB manager handling blocking/unblocking and reset

Gateway Manager (GWM)
The Gateway Manager handles the following function: 1. 2. 3. 4. 5. 6. 7. 8. 9. Code loading of objects during initialisation and reset Board initialisation and startup for software processes Handling database information and changing affected functional units Fault management functions (i.e. fault detection, fault recovery, etc.) Collection of statistics from functional units and forwarding to the CSP on the GPROC Collection of cell list for BSC – BTS Dynamic Allocation purposes Audit Procedures Alarm Collection and Relaying Cell resource sharing (i.e. balancing of cells) across equipped PRPs

The PCU GWM acts as the interface to the BSC FM, SM, IP, CM, MMI, CP, Stats process, CSP as well as RSS. An I/O function is created on the PSP for communication with the Packet Resource Processor (PRP) and PICP functional units. Finally a PSP status unit provision for delaying mechanisms, alarms, stats.

2–12

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

PCU System Processor (PSP)
PICP GSL/TRAU Frame Relay PICP status (alarms, stats, debugging)

I/O

PSP (Gateway Manager) Interface to: CM FM RSS CP CSP I/O Gb manager PSP status (alarms, stats, debugging)

PRP PRP status (alarms, stats, debugging) Cell 1 Paging, Sys Info, Access grants FCBM Cell 2 I/O Cell N

Packet Scheduler

RLC Segmenting Power control Timing Advance UPLINK DOWNLINK

LLC Cat

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–13

Device Equipage

ISSUE 1 REVISION 2

Packet Resource Processor
The Packet Resource Processor (PRP) is where all radio related processing takes place. The PRP performs all of RLC/MAC processing, air interface scheduling and frame synchronisation on the BTS facing channels. The following functional units provide this functionality:

Packet Scheduler
Packet Scheduler is created to handle all scheduling of Packet Data Channels (PDCHs) on a per call per Quality of Service (QoS) level basis.

CCCH Paging Manager
The CCCH Paging Manager processes the paging messages coming from the SGSN to the BSC/BTS.

Downlink Segmentor
Downlink Segmentor segments Logical Link Control (LLC) frames into Radio Link Control (RLC) data blocks to be transmitted over the air interface.

Uplink Concentrator
Uplink Concentrator concentrates all the RLC data blocks for a Temporary Block Flow (TBF) into a LLC frame.

Timeslot Resource Shifter (TRS)
Determines which TS are active in the PRP board to support GPRS traffic.

System Information Manager (SYM)
The Systems Information Manager builds and sends GPRS system information over the BCCH.

I/O Function
I/O function is used for routing between the functional units on the PRP and the PICP and PSP/

Flow Control Buffer Management (FBM)
Flow Control Buffer management is a functional unit residing on the PRP to handle all packets received by the SGSN.

2–14

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

PCU Resource Processor
PICP GSL/TRAU Frame Relay PICP status (alarms, stats, debugging)

I/O

PSP (Gateway Manager) Interface to: CM FM RSS CP CSP I/O Gb manager PSP status (alarms, stats, debugging)

PRP PRP status (alarms, stats, debugging) Cell 1 Paging, Sys Info, Access grants FCBM Cell 2 I/O Cell N

Packet Scheduler

RLC Segmenting Power control Timing Advance UPLINK DOWNLINK

LLC Cat

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–15

Device Equipage

ISSUE 1 REVISION 2

Initial Configuration
1. To begin Initialisation, the BSC IP will instruct the BSC Exec DISP to bring up the GSL as specified in the database. On the PCU at the PCU System Processor (PSP) an IP (pIP) and EXEC DLSP bring up the other side of the default GSL. Once communication is established the BSC IP queries the pIP for the set of objects currently residing at the PCU to determine which new objects require sending. The required set are transferred from the BSC to the PCU. The database is included in this transfer. The PSP, once the download is complete, will determine which card is in each slot of the PCU and download the appropriate objects and database information to each DPROC and PMC. The database is stored in non–volatile memory at the PSP. The PSP now distributes the configured number of cells in the database across the PRPs. It also creates router tables of cell to router and distributes this table to all boards to allow communications. The Gateway Manager (GWM) now initiates process startup at the PRPs and PICPs The GBL interface is now initialised as the GSL is brought into service. The PSP now indicates to the BSC CA that the PCU is enabled and registers for calls.

2.

3.

4.

5. 6.

2–16

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

pIP + BSC IP bring up default GSL

BSC IP queries PCU pIP for set of objects

BSC IP download objects if required

pIP downloads appropriate objects to each DPROC + PMC

PSP distributes configured cells across PRPs

GWM starts up PRPs + PICPs

GBL initialised + GSL brought into service

PSP indicates PCU enabled + registers for cells

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–17

Device Equipage

ISSUE 1 REVISION 2

Cell INS/OOS
For cells using the BCCH, when a cell comes in service the BSC CA will send a Cell State Change message to the Gateway Manager (GWM) indicating INS. The GWM responds with an acknowledgement. The GWM forwards this information to the GB manager who acknowledges and indicates to the correct Packet Resource Processor (PRP) that the cell is now available for GPRS. The Packet Resource Manager (PRP) will formulate new packet system information messages to the Cell Resource Manager (CRM) indicating Quality of Service (QoS) barred. The GBM also notifies the SGSN via a BSSGP Virtual Circuit (BVC) unblock that the cell has come into service. After acknowledgement from the SGSN the GBM will indicate that the cell is in service to the PRP, will generate system information and unbar the QoS levels via the CRM. Cell OOS follows the same format only that the BVC block message to the SGSN from the GBM is independent of the PRP acknowledgement of GPRS being unavailable in the cell.

2–18

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

BSC CA

GWM

GBM

PRP

SGSN

CP

RSS

CCU

Cell State Change Ins Cell Ins Cell Ins Ack Cell State Change Ack GPRS Available System Information BCCH Sys Info

New PSI (QOS Barred) GPRS Available Ack New GPRS Sys Info BVC Unblock BVC Unblock Ack

Cell Ins New PSI (QOS Un-barred) New GPRS Sys Info

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–19

Device Equipage

ISSUE 1 REVISION 2

GSL and RSL State Changes
GPRS Signalling Link (GSL) State Changes
The PCU Central Authority CA (pCA) maintains a table on the current GSLs available. When a GSL goes out of service the pCA will update the tables. When the last GSL goes out of service the BSC FTP will create a GSL alarm and the PCU will reset. The BSC and pCA shall attempt to restart the link. If the resynchronisation procedures are unsuccessful then the PCU is declared disabled and GPRS resources (air timeslots and terrestrial backing) are made available for circuit switched use.

RSL State Change
When an RSL changes state the PCU receives notification for all the cells under that specified site. If the RSL comes back into service the specified cells come back into service. At BTS site initialisation the BTS initiates registration with the BSC CA for the PCU. The BTS Cell Resource Manager (CRM) is informed when the PCU becomes available or unavailable.

2–20

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

GPRS Signalling Link (GSL) State Changes
Last GSL OOS
– – – GSL ALARM PCU RESET GB DISCONNECT

RSL State Changes
– – PCU notified of cell state change BTS CRM QUERY BSC CA for PCU STATUS

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–21

Device Equipage

ISSUE 1 REVISION 2

Carrier State Changes
The respective packet scheduler for the cell receives Carrier State Change message from the Cell Resource Manager (CRM) when a GPRS carrier it is responsible for goes out of service. The Packet Scheduler (PS) notifies the SGSN of the cell being out of service via the GB manager. If the carrier out of service is not the BCCH carrier then new system information may be sent to indicate GPRS unavailable.

2–22

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

CRM

PS/SYS INFO CARRIER STATE CHANGE CELL OOS

GBM

SGSN

BVC BLOCK

CARRIER STATE CHANGE ACK

BVC BLOCK ACK

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–23

Device Equipage

ISSUE 1 REVISION 2

Carrier Activation
When the BTS CRM startup, the CRM will register with the BSC CA for PCU status. The CA informs the CRM when the PCU becomes available. The CRM configures all the GPRS timeslots with the RSS and Channel Coders to Packet Data Channels (PDCHs). The CRM now notifies the Packet Resource Processor (PRP) that the GPRS radio timeslot activation was successful. The PRP now requests via the PCU System Processor (PSP) for connection of the GPRS Data Stream (GDS) timeslots to radio timeslots. Additionally, the Gateway Manager (GWM) connects the PCU timeslots to the appropriate GDS timeslot. Once the connections are set up the PRP initiates synchronisation procedures with the Channel Coders. Once the site and carrier are in, the CRM, with help from the PRP gradually unbars the cell and indicates GPRS available.

2–24

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

BSC SM

BSC CA

BTS Note that the BTS shall initiate entity notification registration at site init and RSL inservice

PSP

PICP

PRP (per cell procedures)

BSC CA has been notified the PCU is in–service PCU Available PCU Ins GPRS Carrier Status

PCU Connection Requests (radio channel/PCU timeslot) PCU Connection Requests (radio channel/PCU timeslot) OK PCU Connection Assignments PCU Connection Assignments

Initiate synchronization with the Channel Coders Packet System Information (to bar mobiles)

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–25

Device Equipage

ISSUE 1 REVISION 2

Mobile Originated Packet Access and Transfer
On initiation of uplink packet transfer the BSS shall provide the capability to handle a packet channel request on a Packet Associated Control Channel (PACCH). On receipt of a RACH the RSS forwards the RACH to the Packet Scheduler. The resource is assigned by the Packet Scheduler and the Access Grant functional unit generates the immediate assignment which is returned to the RSS for transmission on AGCH. After access and assignment the Uplink functional unit will collect all the radio blocks sent from the MS, identified by the Temporary Flow Indentifier (TFI) and reassemble all the radio blocks for each TFI into an Logical Link Control (LLC) frame. The LLC frame is then sent to the Gb functional unit to be placed in an uplink queue to be serviced by Frame Relay and sent to the SGSN.

2–26

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

MS

RSS

ACCESS GRANT FU

CHANNEL REQUEST IMMEDIATE ASSIGNMENT

CHANNEL REQUEST IMMEDIATE ASSIGNMENT

(ON THE RACH) (ON THE AGCH)

MS

ACCESS AND ASSIGNMENT

UPLINK FU

ASSEMBLE FU

GB

FR

SGSN

PDTCH PDTCH PDTCH PACCH

DATA BLOCK DATA BLOCK DATA BLOCK TEMPORARY PACKET ACK/NACK DATA BLOCK

PDTCH PDTCH PACCH DATA BLOCK (LAST) FINAL PACKET ACK/NACK

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–27

Device Equipage

ISSUE 1 REVISION 2

Mobile Terminated Packet Access and Transfer
On receipt of a Paging message from the SGSN, the pCA will forward a Packet Paging Request over the PCH. The MS will respond with a Packet Channel Request on the PACH and following an assignment will move to the assigned Packet Data Channels (PDCHs) and send a Packet Paging Response, which has a Temporary Logical Link Identity (TLLI) and an Logical Link Control (LLC) frame with a TLLI. On receipt of the LLC frame from the SGSN, the Frame Relay unit strips out the Frame Relay header and passes the frame onto the Gb functional unit, which strips off the BSSGP header and passes the frame down to the segmentation functional unit, which splits the frame into RLC/MAC radio blocks for sending on PDCHs assigned to the mobile.

2–28

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

MS PACKET CHANNEL REQUEST PACKET IMMEDIATE ASSIGNMENT

ACCESS GRANT FU (ON THE RACH)

(ON THE AGCH) PACKET RESOURCE REQUEST OPTIONAL PACKET RESOURCE ASSIGNMENT PACCH PACCH

MS

ACCESS AND ASSIGNMENT

DL FU

SEGMENTATI ON

GB

FR

SGSN

PDTCH PDTCH PDTCH PACCH

DATA BLOCK DATA BLOCK DATA BLOCK (POLLING) TEMPORARY PACKET ACK/NACK DATA BLOCK

PDTCH DATA BLOCK DATA BLOCK (LAST POLLING)) FINAL PACKET ACK/NACK

PDTCH PACCH

PACCH

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–29

Device Equipage

ISSUE 1 REVISION 2

Gb Interface
The interface to the SGSN is a new network interface for the BSS defined by GPRS as the Gb interface. The Gb interface is a packet interface using Frame Relay PVCs. Two types of information flow on the Gb interface, signalling and data. Two protocols work over the Gb interface, these are the Base Station System GPRS Protocol (BSSGP) protocol and the underlying NS (Frame Relay). Frame Relay includes Network and Link layer functions. It performs data transmission, load sharing and link layer node management. The BSSGP layer provides Quality of Service (QoS), radio and routing and signalling for node management between the BSS and the SGSN. The BSS provides downlink flow control between the BSS and the SGSN, it consists of: S S One queue per cell provided in the BSSGP layer Flow Control

2–30

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

BSSGP

BSSGP

NS

NS

FR

FR

EI
PCU

EI
SGSN

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–31

Device Equipage

ISSUE 1 REVISION 2

Frame Relay Functional Unit
At the time of system setup of the Packet Control Unit (PCU), the Frame Relay functional unit will be initialised. The transmit and receive buffers and the timer resources are initialised on the Packet Interface Control Processor (PICP) for Layer 2 buffering of uplink and downlink data on the Gb interface. The Frame Relay functional unit will hold in Non Volatile memory a mapping of local DLCI and the physical interface (i.e. E1). The SGSN also holds a similar mapping. Each PCU will only be able to connect to one and only one SGSN. DLCI 0 is used to send PVC status messages. The maximum number of DLCIs that can be indicated in the frame size of 1600 octets is 318. This means that 318 DLCIs can be set up per physical bearer. The status messages are used to confirm the end to end availability of all PVCs on a GBL.

2–32

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

Frame Relay Functional Unit

– – –

Transmit and Receive Buffers NVRAM MAPPING DLCI + GBL DLCI O PVC STATUS MESSAGES

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–33

Device Equipage

ISSUE 1 REVISION 2

Gb Functional Unit
The Gb functional unit is divided into the following processes: S S S S S Gb Manager (GBM) Gb Router (GR) Gateway Transmit Manager (GTM) Network Service Test (NST) Flow Control Buffer Manager (FBM)

GBM
The GB Manager manages BSSGP Virtual Circuit (BVC) (cell) and NS–VC (PVC) management procedures. The Gb Manager (GBM) maintains internal tables monitoring the state of BVCs and NS–VCs and the mapping between them. The GBM is responsible for the monitoring of the Gbl link status and generating the appropriate alarms. The GBM will inform the Gateway Manager (GWM) of any change in GBL status. The GBM manages the BVC and NS–VC block, reset and unblock procedures. It shall generate the appropriate alarms. The FR functional unit at the Packet Control Unit (PCU) shall detect when the last GBL goes out of service and reports it to the GBM, which in turn reports the event to the pFTP and informs the pFCP to generate an alarm. The GBM is also responsible for sending Radio Status messages to the SGSN (i.e. BTS not MS) and the handling of Routing Area (RA) capability procedures.

2–34

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

Gb Functional Unit

NST

Gb Router Gb Manager

Gateway Transmit Manager Flow Control Buffer Manager

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–35

Device Equipage

ISSUE 1 REVISION 2

Gb Router (GR)
The Gb Router (GR) validates and routes downlink PDUs. The GR routes the downlink PDUs to the appropriate Flow Control Buffer Manager (FBM) which will pass the PDU to the air functional units for transmission over the air. The GR is also responsible for the routing of paging messages to the appropriate Paging function on a Packet Resource Processor.

Gateway Transmit Manager
The Gateway Transmit Manager (GTM) gathers and transmits uplink PDUs on the correct NS–VC. The air functional unit concatenates the uplink Logical Link Control (LLC) frame and the load sharing function chooses the appropriate NS–VC from the NS–VC group serving the BSSGP Virtual Circuit Identifier (BVCI) for transmission by the GbFu to the SGSN. The GTM gathers the PDUs from the various cells and passes them to the FR functional unit for transmission over a given DLCI and Gbl.

Network Service Test
The Network Service Test (NST) periodically tests NS–VCs to see if they are alive. The NST also sends test messages on each alive NS–VC and responds to test messages from the SGSN by sending back an acknowledgement on the same NS–VC.

Flow Control Buffer Manager (FBM)
The Flow Control Buffer Manager ensures that opened downlink LLC frames are transmitted over the air within their delay class limitations. The FBM performs flow control using either XON/XOFF or the ‘leaky bucket’ algorithm. When using the ‘leaky bucket’ algorithm the configurable parameters of the maximum size of the downlink buffer and maximum data rate the SGSN can transmit data to the mobiles will govern the algorithm. The FBM will send at a configurable interval flow control messages to the SGDN to govern the downlink data transfer. The FBM is also responsible for the flushing of a mobile LLC PDUs from a cell queue for that mobile and informing the packet scheduler to delete the mobiles context for that cell.

2–36

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

NST
– Periodic testing of NSVCs

FBM

– –

Ensure queued dl LLC frames transmitted within their delay class Flushing of LLC frames

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–37

Device Equipage

ISSUE 1 REVISION 2

Fault Management
The Fault Management software at the Packet Control Unit (PCU) may be split into two main areas; the fault detection and handling system and the Central Authority (pCA). The Fault Management software is responsible for the detection of any alarms and deciding upon any hardware /software reconfiguration in response to these alarms. The PCU Central Authority, under the direction of the fault handling and detection system, is responsible for carrying out the reconfiguration.

2–38

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

Fault Management

Fault Detection and Handling

Central Authority

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–39

Device Equipage

ISSUE 1 REVISION 2

Fault Detection and Handling System
This area of Operations and Maintenance is responsible for the detection, collection, reporting and deciding actions to be taken if faults appear in the Packet Control Unit (PCU). The system is based around three processes: 1. The Fault Collection Process (pFCP)

This process exists at every DPROC at a site. It collects alarm reports from all processes that exist on its particular DPROC. This process automatically acknowledges receipt of an alarm and then passes all alarms indications up to the fault translation process. 2. Fault Translation Process (pFTP)

This process exists on the PCU System Processor (PSP) as part of the GWM functional unit, and works with various processes to keep the integrity of the site. All alarms at the PCU are reported to the pFTP. The pFTP forwards alarms to the Agent at the BSC and generates messages to the pCA for device transitions, as needed, based on faults reported. 3. System Audit Process (pSAP)

The System Audit Process exists on every DPROC at a site. This process periodically audits the PCU software and any faults found are forwarded to the Fault Translation Process via the Fault Collection Process.

2–40

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

Fault Translation Process
OMC-R

AGENT

pCA

pFTP

pFCP

PCU DEVICES

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–41

Device Equipage

ISSUE 1 REVISION 2

System Audit Process
The Packet Control Unit (PCU) System Audit Process follows much the same architecture as the BSS. A Site System Audit Process (pSSAP) resides on the PCU System Processor (PSP) as part of the Gateway Manager (GWM) functional unit. The PSP performs the audits of the PCU and communicates directly with the BSC MMI and SAP. The DPROCs contain a local process responsible for auditing the DPROC upon which it resides. The SAP will detect faulty/degrading hardware and software through the use of audit tests and if a failure is detected it is reported to the pfTP. There are three types of System Audit Process: S S S Site System Audit Process – one per site and will result in an audit of all available hardware in the PCU. Cage System Audit Process – has the same functionality as the Site System Audit Process. This has been provided for future multi cage PCUs. Device System Audit Process – responsible for auditing the device on which it resides.

The System Operator can turn the audit functionality ON/OFF on a device, cage or per site basis. The System Operator can modify the audit schedules for a specific device or cage, e.g. device audit.

2–42

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

System Audit Process
S Monitor the status of the PCU

S

Three types of Audit process – – – Site System Audit Process (pSSAP) Cage System Audit Process (pCSAP) Device Audit Process

S

MMI Control (OMC, TTY)

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–43

Device Equipage

ISSUE 1 REVISION 2

Configuration Management
The Configuration Management (CM) Software is responsible for managing and updating the main configuration database at either a BSC, BTS or PCU. This database is downloaded as an object file and contains all the site parameters such as site configuration and device functionality distribution. The CM process at the BSC communicates with the pCM process in the same manner as a remote BTS. If database changes are listed as at the PCU then the BSC CM will forward the changes to the PCU Configuration Management (pCM). There is no MMI functionality at the PCU so the pCM has reduced functionality compared to the CM at the BSC. The pCM process resides on the PCU System Processor (PSP) as part of the Gateway Manager functional unit. The pCM receives the CM database object from the BSC. After translation the database object is stored on compact flash on the PSP. The translated object is cross–loaded to the DPROC boards equipped in the database with code objects at initialisation.

2–44

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

Configuration Management

BSC CM

BSC CA

Compact Flash Memory

PSP pCM

MASTER DATABASE

Slave pCM Database Copy

Slave pCM Database Copy

DPROC

DPROC

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–45

Device Equipage

ISSUE 1 REVISION 2

PCU Central Authority (pCA)
On site initialisation, the central authority (pCA) process is created and queries the database to obtain site configuration and device equipage data. The central authority is then responsible for creating all the necessary software processes on the DPROCS, as well as downloading and ”bringing into service” all peripheral boards and devices. On completion of site initialisation, the pCA then works as an independent process with a dynamic database keeping track of the state of all devices and software functions on its site. If a fault indication occurs at the site and the fault detection and handling system decides that a device or software identity must be taken out of service, then it is the pCA that will perform this task. If the fault detection and handling system decides to bring another device or software entity into service, in response to that alarm indication then it is the pCA that will supervise the downloading/initialisation of the device or software entity. It may be the case that the system operator wishes to remove or insert a device from service with a MMI command, it is the pCA that carries out the action. In both of the above cases, once the reconfiguration has occurred, the pCA will update the device state of each entity in its dynamic database. However, if the site is re–initialised the pCA process is lost and the device states are erased. The pCA is then created by the initialisation process, the pCA reads the database and the initialisation procedure starts again. The pCA is responsible for informing the router process when software processes are created, destroyed or moved. This allows the router process to modify the router tables which are used by the executive to support the ”flexible interprocess communications” feature.

2–46

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Device Equipage

PCU Central Authority Functions

A. 1. 2. 3. 4. 5.

Site Initialisation Queries for database for site configuration and equipage. Downloading software to the hardware Create Software on DPROCS Creating routing tables Creating state tables

B. 1. 2. 3. 4.

Initiate and Direct Configuration Changes Hardware Software Updating Router Updating state tables

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

2–47

Device Equipage

ISSUE 1 REVISION 2

2–48

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 3

BSS/PCU Commands

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Chapter 3 BSS/PCU Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMS Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MMS Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GDS or GBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Data Stream (GDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Signalling Link (GSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LCF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reconfiguration of suitable GPRS PDCHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSGP Virtual Circuit (BVC) Blocking and Unblocking . . . . . . . . . . . . . . . . . . . . . . . . . . . BVC Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Service Block, Reset, Unblock, Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Service Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Service Virtual Connection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gb Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Service Virtual Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSSGP Virtual Circuit Identifier (BVCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Signalling BVCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N3102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

i
3–1 3–2 3–2 3–2 3–4 3–6 3–8 3–8 3–8 3–10 3–12 3–14 3–16 3–18 3–20 3–22 3–24 3–26 3–28 3–30 3–32 3–34 3–36 3–38 3–40 3–42 3–44 3–46

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

iii

ISSUE 1 REVISION 2

iv

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Objectives

Objectives
On completion of this chapter the student will be able to: S S Describe the device/function dependancy within the database structure Equip and understand the database fields associated with equipping a PCU

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–1

PCU

ISSUE 1 REVISION 2

PCU
Equipping a PCU at a BSS is done using the equip 0 pcu command. Equipping the PCU automatically equips the cab and cage. Only one CAB and one cage can be equipped with a PCU. Restrictions to the PCU equipage are: S S S PCU cannot be equipped when the GPRS feature is restricted. One PCU only per BSS PCU can only be equipped if land_layer_l_mode is set to E1

PSP
The PCU System Processor (PSP) is equipped on the MPROC at the PCU. Is the device that describes an MPROC board which is the master processor in the PCU.

Dependencies
S S S GPRS feature must be unrestricted PSP may only be equipped at a PCU Sysgen mode cannot be left if a PCU is equipped and no PSP is equipped

3–2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

PCU

equip 0 pcu

automatically equip: Cabinet Cage

equip PCU PSP

Enter the PSP identifier: 0

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–3

DPROC

ISSUE 1 REVISION 2

DPROC
The Data Processor Board is the non–system processor board at the PCU. These boards may have up to two PMC modules fitted dependent on the required function. DPROCs may only be fitted and equipped in slots 1 – 6 and slots 11 – 16, the remaining slots being taken by the MPROC and the PCI to PCI Bridge (PPB). There are two types of DPROC, Packet Interface Control Processor (PICP) and Packet Resource Processor. A maximum of 6 PICPs may be equipped at the PCU and a maximum of 10 PRPs may be equipped at the PCU. PRPs should not be equipped in slots 1 and 2 of the PCU cage as the default slot on initialisation to bring up the GPRS Signalling Link (GSL) to gain code download is via slot 1 or 2 through a PICP.

3–4

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

DPROC

equip PCU DPROC

Enter the DPROC ID: <*> * 1–6, 11–16

Enter the DPROC type: <*> * PRP or PICP

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–5

MSI

ISSUE 1 REVISION 2

MSI
To equip the PMC module the MSI device has been modified. The PMC module is used to support the connection of the GBL to the PCU or the GPRS Data Stream (GDS) and GPRS Signalling Link (GSL) to the PCU. These is a new MSI type called the E1–PMC to add this interface card to the MSI device. To equip the E1–PMC MSI can only be carried out at a PCU. A maximum of 12 DPROC PICP MSIs can be equipped with a maximum of two E1–PMCs to any PICP. Each PRP may be equiped with up to 2 MSI. The first identifier of the E1–PMC must be unique, the second refers to the DPROC that the E1–PMC is mounted on. The final prompt for the DPROC socket refers to the module identifier for the DPROC board that the E1–PMC is being equipped. Each DPROC is capable of holding two E1–PMCs.

3–6

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

MSI

equip PCU MSI

Enter the MSI identifier: <*> * 0–23

Enter the DPROC id: <*> * 1–6, 11–16

Enter the DPROC Socket: <*> * 1,2

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–7

MMS Device

ISSUE 1 REVISION 2

MMS Device
To equip the two ports on the PMC module the MMS command has been extended. The MMSs for a PMC are automatically equipped when a MSI is equipped.

MMS Priority
The MMS priority for a PICP MMS may not be set to a non–zero value, nor can the MMS at the BSC that is part of a GPRS Data Stream (GDS).

GDS or GBL
All MMSs on the same MSI must be configured for the same destination.

3–8

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

MMS Device

MMS Device PICP E1 GDS E1 PMC 860 E1

E1 GBL E1

PMC 860 E1

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–9

GPRS Data Stream (GDS)

ISSUE 1 REVISION 2

GPRS Data Stream (GDS)
The GPRS Data Stream device refers to the traffic route between the PCU and the BSC. This is a E1 connection between a BSC MMS and a PCU MMS. The GPRS Data Stream (GDS) may or may not have an associated GPRS Signalling Link (GSL). If the GDS carries a GSL then one timeslot is required for GSL LAPD signalling, the rest for GPRS traffic. A maximum of 12 GDSs may be equipped and to allow default connectivity for code download for the PCU a GDS must be equipped and GSL equipped to the GDS (LAPD) of either: S S Timeslot 1 of span 0 of an E1–PMC Module in PMC Socket 1 of a PICP in Slot 1 Timeslot 1 of span 0 of an E1–PMC module in PMC Socket 1 of a PICP in Slot 2

3–10

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Data Stream (GDS)

equip PCU GDS

Enter the GDS Identifier: <*> * 0–11 Enter the BSC MMS Identifier: <*> <*> Enter the PCU MMS Identifier: <*> <*> Enter the GDS type: <*> 0 – TRAU GDS 1 – LAPD GDS

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–11

GPRS Signalling Link (GSL)

ISSUE 1 REVISION 2

GPRS Signalling Link (GSL)
The GPRS Signalling LInk (GSL) is a 64Kbps LAPD signalling link on a timeslot on a GPRS Data Stream (GDS). The GSL is used for signalling and code download for communication between the PCU and the GSL. The maximum GSLs that may be equipped to a PCU are 6, with a maximum of two GSLs to any GDS. The first GSL equipped to a GDS will use timeslot 1 of the GDS and the second GSL equipped to the same GDS will use timeslot 2. A GSL must be equipped to the default location to allow code download. The maximum number of GSLs equipped must not exceed the maximum number of GSLs that the LCFs can manage.

3–12

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Signalling Link (GSL)

equip PCU GSL

Enter the GSL identifier: <*> * 0–5

Enter the Unique GDS identifier: <*> * 0–11

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–13

GBL Device

ISSUE 1 REVISION 2

GBL Device
The GBL device refers to the configured number of timeslots on a E1 span between the PCU and the SGSN. This is the physical interface for the Frame Relay network service. One GBL is allowed per E1 span, the number of timeslots is a configurable parameter. To maintain the Frame Relay link, unidirectional signalling incorporates periodic polling between the PCU and the network. The PCU sends a STATUS ENQUIRY message every polling cycle (governed by T391) the network responds with a STATUS message. A count of the polling cycles is kept by the counter N391 at a set number of polling cycles called a FULL STATED ENQUIRY message is sent. The network may also POLL the PCU set by a Polling Verification timer T392. The Error Threshold counter (N392) and the Monitored Events counter (N393) keep track of events and errors on the link.

3–14

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GBL Device

equip PCU GBL

Enter the GBL identifier: <*> * 0–3 Enter the 1st and 2nd MMS identifier: <*> <*> * MSI id 0–11 * MMS id 0 or 1 Enter starting timeslot: <*> * 1–31 Enter the ending timeslot: <*> * 1–31 Enter the T391 timer: <*> * 5–29 seconds Enter the T392 timer: <*> * 6–30 seconds Enter the N391 counter: <*> * 1–255 polling cycles Enter the N392 counter: <*> * 1–10 number of errors Enter the N393 counter: <*> * 1–10 number of events
EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–15

LCF

ISSUE 1 REVISION 2

LCF
GPRS Signalling Link (GSL) Links are managed at the BSC by LCFs. To manage this the LCF device has been modified. The number of GSLs that an LCF can manage is referred to by max_gsls. This maximum may not exceed 6. The LCF can manage GSLs along with any combination of other link devices, for example RSLs, CBLs, GSLs, MTLs. The number of GSLs supported by the LCF must not exceed the maximum number it can support. The maximum number of GSLs per LCF are defined by the number of available GPROC slots and is limited to six. During LCF equipage the maximum number of MTLs , MBLs and GSLs are specified. The total number of these combined must be less than gproc_slots – Reserved HDLC Channels

3–16

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

LCF

equip bsc LCF

Enter the function ID for the LCF: Enter the number of MTLS the LCF can manage: Enter the number of CBLs the LCF can manage: Enter the number of GSLs the LCF can manage: <*> * 0–6

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–17

GPRS Carrier

ISSUE 1 REVISION 2

GPRS Carrier
The BSS shall support Reserved and Switchable GPRS timeslots. A reserved GPRS Timeslot is a timeslot used for GPRS use only. A Switchable GPRS Timeslot is a timeslot that can be switched from GPRS usage to circuit switched and vice versa. The BSS supports one GPRS carrier per cell and this carrier may be the BCCH or the non–BCCH. The maximum number of GPRS timeslots configured depends on whether a separate GPRS carrier is provided. If a non–BCCH carrier is chosen then up to 8 timeslots may be configured for GPRS. To support this new RTF, parameters have been added: S S max_gprs_pdch res_gprs_pdch

The parameter max_gprs_pdch specifies the maximum number of Packet Data Channels (PDCHs)s which will be configured on the carrier starting from the highest order timeslot. The parameter res_gprs_pdch specifies the number of PDCHs configured on the carrier that will be reserved for GPRS use only. The number of Reserved GPRS timeslots must not exceed the maximum GPRS PDCH. All GPRS timeslots must have the same FHI and the same Training Sequence Code.

3–18

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Carrier

Timeslot Configuration Examples

Example A 0 1 2 3 4 5 6 7
BCCH TCH TCH SW SW RES RES RES BCCH CARRIER TCH TCH TCH TCH TCH TCH TCH TCH CARRIER 2

Example B
BCCH TCH TCH TCH TCH TCH TCH TCH BCCH CARRIER SW SW SW RES RES RES RES RES CARRIER 2

Example C
BCCH TCH TCH TCH TCH TCH TCH TCH BCCH CARRIER SW SW SW SW SW SW SW SW CARRIER 2

max_gprs_pdch <*> * 0 – 8 res_gprs_pdch <*> * 0 – 8

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–19

Reconfiguration of suitable GPRS PDCHs

ISSUE 1 REVISION 2

Reconfiguration of suitable GPRS PDCHs
The order of priority within a cell is circuit switched calls followed by packet data calls. The BSS supports dynamic switching between Packet Data Traffic Channels (PDTCH)s and TCHs and vice versa. If it is necessary for the BSS to use any switched timeslots the BSS shall use them by triggering a reconfiguration frame PDTCH to TCH. If the timeslot was in use by any GPRS mobiles, the PCU will broadcast the release notification on the Packet Associated Control Channels (PACCHs). If there is additional downlink data to send the BSS will reassign a channel using the AGCH. If the MS has more data to send the PCU will rely on the MS to Re RACH. When a circuit switched call is greater than gprs_reconfig_thresh_idle_tch then the BSS will reconfigure the channel back to a PDTCH. If the threshold of idle TCHs has been exceeded and the cell has gprs_intraho_allwd set then the BSS will perform an intracell handover of the mobile to an idle TCH and reconfigure the channel to a PDTCH.

3–20

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Reconfiguration of suitable GPRS PDCHs

Reconfiguration

gprs_intraho_allwd <*> * 0 = NO INTRACELL HANDOVERS ALLOWED 1 = INTRACELL HANDOVERS ALLOWED

gprs_reconfig_thresh_idle_tch <*> * 1–5 IDLE RESOURCES

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–21

BSSGP Virtual Circuit (BVC) Blocking and Unblocking

ISSUE 1 REVISION 2

BSSGP Virtual Circuit (BVC) Blocking and Unblocking
A BSS may block a BVC because of: S S S S Operation and maintenance of a cell Equipment failure at the BSS Cell equipment failure at the BSS Cell traffic congestion

The BSS when blocking a BSSGP Virtual Circuit (BVC) will mark the BVC as blocked, discarding any traffic sent to the BVC in the uplink direction. The cell associated with the BVC will not accept any data in the downlink. The BSS sends a BVC_BLOCK PDU to the SGSN (containing the BSSGP Virtual Circuit Identifier (BVCI) of the BVC to be blocked and a cause element) and starts the timer T1. The SGSN on receipt of the BVC_BLOCK PDU will mark the BVC as blocked and stop transmitting traffic on that BVC. The SGSN then acknowledges the blocking of the BVC with a BVC_BLOCK_ACK PDU to the BSS. Receipt of the BVC_BLOCK_ACK PDU will stop T1. If the BVC_BLOCK_ACK PDU is not received before expiry of T1 then the BSS shall repeat sending the BVC_BLOCK PDU for a maximum of BVC_BLOCK RETRIED. Unblocking operates in the same method using a BVC_UNBLOCK PDU sent to the SGSN and starting T1, the BSS will re–send the BVC_UNBLOCK PDU for BVC_UNBLOCK RETRIED. On receipt of a BVC_UNBLOCK ACK from a SGSN the BVC is marked as unblocked.

3–22

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

BSSGP Virtual Circuit (BVC) Blocking and Unblocking

BVC Block/Unblock
PCU
T1

SGSN BVC – BLOCK PDU

T1

BVC – BLOCK PDU
Exceeded Stopped

BVC – BLOCK ACK PDU

T1

BVC – UNBLOCK PDU

BVC – UNBLOCK ACK PDU

change_element s bs s gp_t1_timer <*> PCU * 1-120 s econds bs s gp_block_retries <*> PCU 1 - 3 number of retries bs s gp_unblock_retries <*> PCU 1 - 3 number of retries

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–23

BVC Reset

ISSUE 1 REVISION 2

BVC Reset
The purpose of the BVC_Reset procedure is to resynchronise the GPRS BSSGP Virtual Circuit (BVC) contexts at a BSS and SGSN. This ensures communication in a known state. A BVC_Reset procedure could be initiated due to a system failure, an underlying network service failure or a change in the transmission capability of the underlying network service. The sequence is similar to the BVC block/unblock procedure. The BSS or SGSN sends a BVC_RESET PDU to its Peer and starts the guard timer. bssgp_t2_timer if the entity does not receive a BVC_RESET_ACK before expiry of T2 then the entity will re–send the BVC_RESET PDU for BVC_RESET_RETRIES before stopping the procedure and informing the O&M system. On receipt of a BVC_RESET_ACK the T2 timer is stopped.

3–24

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

BVC Reset

BVC Reset

PCU
T2

SGSN BVC – RESET PDU

ACTIVATED

T2

BVC – RESET PDU
EXCEEDED BSSGP_RESET RETRIES

T2

BVC – RESET PDU
STOPPED

BVC – RESET ACK PDU

change_element s bs s gp_t2_timer <*> PCU * 1-120 s econds bs s gp_res et_retries <*> PCU 1 - 3 number of retries

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–25

Flow Control

ISSUE 1 REVISION 2

Flow Control
The principle of flow control is the BSS sends to the SGSN flow control parameters. The SGSN performs flow control on each MS and BSSGP Virtual Circuit (BVC). The flow control is performed first on each LLC_SDU, first by MS flow control mechanism, and then by the BVC flow control mechanism. The convention is that the SGSN should not transmit more data than can be contained in the BSS buffer for a BVC or individual MS. The variables sent are a Bucket size for each cell and MS the Bmax should be large enough to accommodate at least one LLC–SDU. Also sent is the leak rate (R) to be applied to the bucket. The frequency of flow control information is governed by a setable parameter C. The formula B* = B + L(p) – (Tc – Tp) x R Where: B = Bucket Counter – size of last LLC SDU sent to PCU from the SGSN B* = Predicted Value of Bucket Counter, which includes the size of the LLC PDU awaiting transmission to the PCU L(p) = Length of LLC – SDU waiting to be transmitted from the SGSN Tp = Time the last LLC– SDU was transferred to the PCU Tc = Arrival time of LLC–SDU at the SGSN from the GGSN R = Leak rate of the bucket at the PCU When an LLC–SDU packet arrives at current time Tc, the variable B* is set to the predicted bucket size as if the LLC–SDU was sent to the BSS. This is given by the previous bucket size plus the new LLC–SDU size B* = B + L(p). To take account of the leakage since the last compliant LLC–SDU packet the calculation R* (Tc–Tp) is used. If B* is less than zero then the Bucket Counter is set to the L(p) of the LLC–SDU as is Tp set to Tc and the LLC–SDU is passed as the BSS is ready to receive another LLC packet. If B* is not equal to zero but is less than Bmax, in other words would not exceed the buffer, the LLC packet is passed to the BSS and B is set to B* and Tp to Tc.

3–26

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Flow Control

Flow Control
Arrival of LLC PDU p with length L(p) at time Tc

B*= B + L(p) – (Tc – Tp) x R

B* < 0 ? no

yes B= L(p)

B* >Bmax ?

no B= B* Tp= Tc

change_element s bs s p_fc_period_c <*> PCU * 1-1000 units 10ths of a s econd

Delay LLC PDU

Pass LLC PDU

max_ms _dl_buffer <*> cell <cell id> * 1600 - 3000 Octets max_ms_dl_rate <*> cell <cell id> * 1 - 80000 1 = 1 bps 2 = 2 bps
GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY
3–27

EMOTOROLA LTD. 2000

Network Service Block, Reset, Unblock, Test

ISSUE 1 REVISION 2

Network Service Block, Reset, Unblock, Test
The Gb Manager (GBM) manages the NS–VC block, reset and unblock procedures. Any NS–VC failure reported by the FR functional unit will result in an NS–VC block being sent to the SGSN by the GBM and informing other PCU processes of the change in NS–VC status. The NS–VC Block PDU will be sent at the expiry of ns_block_timer and for ns_block_retries until receipt of NS_BLOCK–ACK PDU. When an NS_VC comes into service, the GBM first starts a reset procedure to ensure that both ends are at the same state. The peer entity sends an NS_RESET PDU to its peer and starts ns_reset timer. At the expiry of the timer the peer re–sends the NS_RESET PDU for a period of time governed by ns_reset_period. Once an NS_RESET ACK has been received the ns_reset_timer is stopped and the NS_VC is marked as blocked. The GBM then initiates the Test Procedure on the NS_VC. After initiation of the test procedure the GBM then unblocks the NS_VC. The peer entity sends an NS_UNBLOCK PDU and starts ns_block_timer. On expiry of the timer the peer entity sends another NS UNBLOCK PDU for NS_UNBLOCK_RETRIES. On receipt of an NS_UNBLOCK_ACK PDU the timer is stopped.

3–28

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Network Service Block, Reset, Unblock, Test

Network Service
NS_BLOCK TIMER

PCU

NS_BLOCK PDU NS_BLOCK PDU

SGSN

NS_BLOCK TIMER

NS_BLOCKACK PDU NS_RESET BLOCK PDU
NS_RESET TIMER

NS_RESET ACK PDU

NS_UNBLOCK PDU
NS_BLOCK TIMER

NS_UNBLOCK ACK PDU

change_element s ns _block_timer <*> PCU * 1 - 30 s econds ns block_retries <*> PCU ns _unblock_retries <*> PCU * 1-3 retries ns _res et_timer <*> PCU * 1 - 120 s econds ns _res et_period <*> PCU * 1-250 s econds
EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–29

Network Service Test

ISSUE 1 REVISION 2

Network Service Test
The test procedure is used when a BSS or SGSN wishes to check the end to end communication with its peer entity on an NS–VC. Both sides may initiate this procedure independently of each other. The process is initiated on completion of a reset procedure and then periodically repeated. The procedure is governed by the ns_test_timer, On expiry the peer entity sends an NS_ALIVE PDU on the NS–VC to be checked and starts ns_alive_timer. Upon receipt of an NS_ALIVE_ACK PDU on the NS–VC the originator stops ns_alive_timer and restarts ns_test_timer and the process begins again. If the originator does not receive an NS_ALIVE_ACK PDU before expiry of ns–alive_timer then it will re–send an NS_ALIVE PDU for ns_alive_retries times.

3–30

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Network Service Test

Network Service Test
PCU NS_ALIVE PDU SGSN

NS_ALIVE TIMER

NS_ALIVE PDU

NS_ALIVE ACK PDU
NS_ALIVE TIMER

change_element s ns _tes t_timer <*> PCU * 1 - 60 s econds ns alive_timer <*> PCU * 1 - 30 s econds ns _alive_retries <*> PCU *1-3

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–31

Network Service

ISSUE 1 REVISION 2

Network Service
The Network Service performs the transport of NS SDUs between the SGSN and the BSS. The services provided are: S S S Network Service SDU transfer Network congestion indication Status indication

An SGSN and a BSS may use different physical links for connecting to each other. Each physical link is locally (at each side of Gb interface) identified by means of a physical link identifier. Each physical link supports one or more Network Service Virtual Links (NS–VL). Each NS–VL is identified by means of a Network Service Virtual Link Identifier. The significance (i.e. local or end to end) depends on the configuration of the Gb interface. The NS_VLI is the association of the Frame Relay DLCI and the bearer channel identifier. In order to provide end to end communication between the SGSN and the BSS irrespective of the exact configuration of the Gb interface the Network Service Virtual Connection is used. The NS_VCs are end to end virtual connections between the BSS and the SGSN. At each end of the Gb interface there is a one to one correspondence between NS_VCs and NS_VLs. An NS_VC is identified by the means of a Network Service Virtual Connection Identifier (NS_VCI).

3–32

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Network Service

Network Service

LLC RELAY BSSGP FR MAC LI L1 BSSGP FR

RLC

Gb BSS
END TO END NS–VC

SGSN

FRAME RELAY

BSS
NETWORK

SGSN

NS_VL AT BSS SIDE

NS_VL AT SGSN SIDE

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–33

Network Service Virtual Connection Group

ISSUE 1 REVISION 2

Network Service Virtual Connection Group
The Network Service Virtual Connection Group groups together all the NS_VC providing communication between the same peer NS entities. The network service provides a communication path between remote NS user entities. These communication paths are called BSSGP Virtual Cicuits (BVCs). Each BVC is identified by a BSSGP Virtual Connection Identifier and is unique amongst all network elements connected to the SGSN. Each BVC is supported by one group of NS_VCs. Each group of NS_VCs may support one or more BVCs.

3–34

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Network Service Virtual Connection Group

Network Service Virtual Group

BVCI BSSGP NS – VCI BSSGP

NS CONTROL FR NS – VLI

NS CONTROL NS – VLI FR

FR NETWORK

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–35

Gb Addressing

ISSUE 1 REVISION 2

Gb Addressing
In the diagram opposite, an example of two types of Gb interface are shown; an intermediate frame relay network and a point to point frame relay network. In an intermediate network the Network Service Virtual Link identifier, made up of the DLCI and bearer channel identification, has only local significance. The Network Service Virtual Connection Identification has an end to end significance and is part of an NSVC group serving a BSSGP Virtual Connection Identification which identifies a cell or signalling channel for a BSS at both ends of the Gb interface. In a point to point frame relay network, where the BSS and SGSN are directly connected, the major change is that the DLCI and Bearer Channel identification no longer have local significance but have end to end significance.

3–36

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Gb Addressing

Gb Addressing
BSS #1
SGSN BVC1=2 NS–VC1=a NS–VC1=b BVC1=3 DLCI=137 NS–VC1=a BVC1=2 DLCI=16 PTP Cell 1 DLCI=98 NS–VC1=b DLCI=17

E1

Bearer Channel = 5

Bearer Channel = 1

E1

NS–VC1=e DLCI=16

BVC1=3

PTP Cell 2 NSE1=1

NS–VC1=c DLCI=51 NS–VC1=d DLCI=43

Bearer Channel = 2 E1
FRAME RELAY

NSE1=1 BVC1=0

Signalling

BVC1=0

BSS #2
BVC1=2 NS–VC1=e DLCI=16 PTP Cell 1 NSE1=2 NS–VC1=f DLCI=259 Signalling BVC1=0

NETWORK

Bearer Channel = 3 Bearer Channel = 6 E1
NS–VC1=c DLCI=21 NS–VC1=d DLCI=302 NS–VC1=f DLCI=511 BVC1=0 BVC1=2

Bearer Channel = 4 E1

EMOTOROLA LTD. 2000

E1

NSE1=2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–37

Network Service Virtual Connection

ISSUE 1 REVISION 2

Network Service Virtual Connection
The NSVC command associates an NSVCI to a Network Service Virtual Link Identification and also specifies the committed information rate and burst size and burst excess. The NSVC must be mapped to a GBL before it can be mapped to an NSVC group or groups. A DLCI must be unique within a single GBL and may be received within other GBLs. Parameter NS_VCI DLCI GBL_ID 0 16 0 Minimum Maximum 65535 991 3

An NSVCI is a unique identification between the BSS and SGSN.

3–38

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Network Service Virtual Connection

Network Service Virtual Connection (NSVC)

add_nsvc <NS_VCI><GBL_ID><DLCI> Enter the committed Information Rate <*> * 0 –1984 in Kbps Enter the committed Burst Size <*> * 0 – 1984 in Kbps Enter the Burst Excess <*> * 0 – 1984 Kbps

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–39

BSSGP Virtual Circuit Identifier (BVCI)

ISSUE 1 REVISION 2

BSSGP Virtual Circuit Identifier (BVCI)
The BSSGP Virtual Connection Identifier uniquely identifies a cell within a BSS or a signalling BVCI to that cell. The PCU maintains a table mapping each cell to a unique BVCI and all BSSGP signalling such as paging to a separate BVCI. The BVCI is a new cell element and is included in the prompt for add_cell. A BVCI must be unique within a BSS. Parameter BVCI 2 Minimum Maximum 65535 Definition Specifies the BVCI

A BVCI must be mapped to a cell before a BVCI may be mapped to an NSVC group.

3–40

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

BSSGP Virtual Circuit Identifier (BVCI)

BSSGP Virtual Circuit Identifier (BVCI)

MMI–RAM 0115 –> add_cell 0 0 1 0 1 1 3 Enter the frequency type: frequency_type= pgsm Enter base station identity code: bsic= 10h Enter wait indication parameters: wait_indication_parameters= 20 Enter common control channel configuration: ccch_conf= 0 : : (existing addcell prompts unchanged) : Enter rapid power down procedure active: rapid_pwr_down=0 Enter rapid power down trigger threshold: rpd_trigger= 51 Enter rapid power down level offset: rpd_offset= 8 Enter rapid power down averaging period rpd_period= 2 Enter the BVCI for this cell: bvci=120 add_cell: LOCAL_CELL_ID selected is= 0 add_cell: cell will be added to site: 0 COMMAND ACCEPTED

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–41

GPRS Signalling BVCI

ISSUE 1 REVISION 2

GPRS Signalling BVCI
The GB map command allows an NSVC group to be allocated for BSSGP signalling but the command does not specify the BSSGP Virtual Circuit Identifier (BVCI) identification. Traffic BVCIs are associated with cells and are equipped with add_cell. To equip a BVCI within a BSS for signalling the element gprs_sig_bvci has been added. This command specifies the unique value for the BVCI for BSSGP signalling.

3–42

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Signalling BVCI

SIG BVCI

change _element gprs_sig_bvci <*> PCU * 0–65535 BVCI identifier

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–43

Routing Area

ISSUE 1 REVISION 2

Routing Area
The Routing Area is a new definition to allow the separation of the network into routing areas. This has the advantage of allowing the tracking of mobiles within routing areas as a mobile will carry out routing area updates when crossing routing area boundaries. The Routing Area Code is an additional one byte identifier in the cell identifier of GPRS cells and is broadcast in System Information message 3. To allow the mobile to quickly discover if a cell is GPRS enabled and in a different routing area, Routing Area (RA) colour is used. RA colour has 8 possible variations and is broadcast in system information message 3, allowing the mobile to quickly identify a routing area boundary and apply the correct response of a routing area update and also cell reselect hystersis. The location of an MS in STANDBY state is known in the SGSN on RA level. This means that the mobile is paged in the Routing Area where the MS is located when mobile terminated packet data arrives at the SGSN. A Routing area is a subset of one and only one location area. LAI = MCC + MNC + LAC RAI = MCC + MNC + LAC + RAC CGI = LAI + (RAC) + CI

3–44

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Routing Area

Routing Area

Bits 7 1 2 Octets 3 4 5 6 1 6 5 4 3 2 1 0

MCC DIG 2 1 1 1

MCC DIG 1 MCC DIG 1 MNC DIG 1 LAC LAC RAC ROUTING AREA IDENTITY

MNC DIG 2

chg_element RAC <*> Cell <cell id> * 0 – 255 chg_element ra_colour<*> <site id> Cell <cell id> *0–7

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–45

N3102

ISSUE 1 REVISION 2

N3102
To ensure that a mobile does not continue transmission of an uplink data transfer when connection to the network has been lost the counter N3102 and timer T3182 are used. Every time an uplink ACK/NACK message is received by the mobile the counter N3102 is incremented by a value set by gprs_ms_pan_inc up to the maximum of gprs_ms_pan_max which sets the upper limit of counter N3102. If the transmit window is stalled as V(S) = V(a) + K (the next RLC/MAC block to be sent is equal to the oldest RLC/MAC block pending acknowledgement, plus the window size K). Then the timer T3182 is started and the mobile will retransmit the oldest RLC/MAC block with a NACKED value of the oldest block pending ACK. These blocks are transmitted with a Stall Indicator set to indicate to the network that the mobile is stalled awaiting an ACK/NACK. If T3182 expires the mobile decrements the counter N3102 by gprs_ms_pan_dec and performs an Abnormal release and then a random access to gain resources to send the uplink. This condition repeats every time T3132 expires, until N3102 < 0 at which the mobile will perform an abnormal release and a cell reselection.

3–46

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

N3102

N3102

V(s)= V(a) + K

gprs_ms_pa_max N3102
T3182

gprs_ms_pan_dec <*><site id> Cell <cell id> *0–7 gprs_ms_pan_inc <*><site id> Cell <cell id> gprs_ms_pan_max <*> <site id> Cell <cell id>

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

3–47

N3102

ISSUE 1 REVISION 2

3–48

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 4

PCU Statistics Application

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Chapter 4 PCU Statistics Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCU Statistics Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Performance Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to GPRS performance statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of accessibility statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessibility statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Throughput statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic allocation statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL Statistic Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL_DL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL_FLOW_CTRL_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL_FLUSH_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL_LINK_INS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL_PAGING_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL_UL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GBL_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessibility Statistic Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHANNEL_REQS_REC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CHANNEL_REQS_REJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS_ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS_ACCESS_PER_PCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS_ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS_CLASS_1_10_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS_CLASS_11_20_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS_CLASS_21_29_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Throughput Statistic Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIR_DL_DATA_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIR_UL_DATA_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DL_CHAN_ASGN_DURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TOTAL_AIR_DL_AVAILABLE_BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TOTAL_AIR_UL_AVAILABLE_BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UL_CHAN_ASGN_DURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

i
4–1 4–1 4–2 4–2 4–2 4–2 4–3 4–3 4–3 4–3 4–4 4–9 4–10 4–11 4–12 4–13 4–14 4–15 4–16 4–17 4–18 4–23 4–24 4–25 4–26 4–27 4–28 4–29 4–30 4–31 4–33 4–37 4–38 4–39 4–40 4–41 4–42

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

iii

ISSUE 1 REVISION 2

iv

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

PCU Statistics Application

PCU Statistics Application
Objectives
On completion of this chapter the student will be able to: S Understand the meaning of each Statistic pegged at the PCU.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–1

GPRS Performance Measurements

ISSUE 1 REVISION 2

GPRS Performance Measurements
Introduction to GPRS performance statistics
This chapter includes descriptions of the General Packet Radio Service (GPRS) statistics. GPRS statistics are organized in the following groups: S S S S Gb link (GBL) statistics. Accessibility statistics. Throughput statistics. Dynamic allocation statistics.

Description of Gb interface
The GBL device refers to the configured number of timeslots on an E1 span between the Packet Control Unit (PCU) and the Serving GPRS Support Node (SGSN). This interface is referred to as the Gb interface. The Gb interface allows many users to be multiplexed over a common physical resource. GPRS signalling and user data are sent on the same physical resource. That is, no dedicated physical resources are required to be allocated for signalling purposes.

GBL statistics
The GBL measurement types are listed as follows: S S S S S S S S S GBL_DL_DATA_THRPUT GBL_DL_DATA_THRPUT_HIST GBL_FLOW_CTRL_SENT GBL_FLUSH_REQS GBL_LINK_INS GBL_PAGING_REQS GBL_UL_DATA_THRPUT GBL_UL_DATA_THRUT_HIST GBL_UNAVAILABLE

4–2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Performance Measurements

Description of accessibility statistics
Accessiblility statistics are used to measure how effectively GPRS resources are being accessed. These measurements are used to assist the operator in planning the necessary resources needed for the mobile to efficiently access the network.

Accessibility statistics
The accessiblility statistics are listed as follows: S S S S S S S S CHANNEL_REQS_REC CHANNEL_REQS_REJECT DL_CHAN_ASGN_DURATION GPRS_ACCESS_PER_AGCH GPRS_ACCESS_PER_PCH GPRS_ACCESS_PER_RACH GPRS_CHANNELS_SWITCHED UL_CHAN_ASGN_DURATION

Throughput statistics
The throughput statistics are listed as follows: S S S S S S S S S S AIR_UL_DATA_BLKS AIR_DL_DATA_BLKS DL_CHAN_ASGN_DURATION GBL_DL_DATA_THRPUT GBL_DL_DATA_THRPUT_HIST GBL_UL_DATA_THRPUT GBL_UL_DATA_THRPUT_HIST TOTAL_AIR_UL_AVAILABLE_BW TOTAL_AIR_DL_AVAILABLE_BW UL_CHAN_ASGN_DURATION

Dynamic allocation statistics
The dynamic allocation statistics are listed as follows: S S S
EMOTOROLA LTD. 2000

GPRS_DYNET_FAILURES GPRS_DYNET_RES_REQS GPRS_DYNET_SWI_REQS

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–3

GBL Statistic Diagrams

ISSUE 1 REVISION 2

GBL Statistic Diagrams
Figure 4-1 to Figure 4-5 show how the GBL statistics function within the BSS/PCU.

DLCI = 45 Bearer chan 1 DLCI = 55

DLCI = 45

DLCI = 55

GBL_DL_DATA_THRPUT

GBL_DL_DATA_THRPUT_TIME_PERIOD

Figure 4-1 GBL_DL_DATA_THRPUT

4–4

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GBL Statistic Diagrams

Figure 4-2 is a ladder diagram detailing the statistic gbl_flow_ctrl_sent when it is pegged. It also shows the request and the response messages sent from the BSS/PCU to the SGSN.

BSS/PCU

SGSN

BSSGP FLOW CONTROL PDU

GBL_FLOW_CTRL_SENT

BSSGP FLOW CONTROL ACK PDU

Figure 4-2 GBL_FLOW_CTRL_SENT

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–5

GBL Statistic Diagrams

ISSUE 1 REVISION 2

Figure 4-3 illustrates the statistic gbl_flush_reqs when it is pegged. It also shows the request and the response sent from the SGSN to the PS.

SGSN

GB FU

PS

FLUSH PDU

FLUSH PDU

GBL_FLUSH_REQS

Figure 4-3 GBL_FLUSH_REQS

4–6

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GBL Statistic Diagrams

Figure 4-4 is a ladder diagram detailing the statistic gbl_paging_reqs when it is pegged. It also shows the request and the response messages sent from the SGSN to the BSS/PCU and the mobile station.

SGSN

BSS/PCU

MS

BSSGP PS PDU GBL_PAGING_REQS

PACKET PAGING REQEST (PCH)

Channel Request (RACH)

Immediate Assignment (AGCH)

Figure 4-4 GBL_PAGING_REQS

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–7

GBL Statistic Diagrams

ISSUE 1 REVISION 2

Figure 4-5 illustrates the statistic gbl_ul_data_thrput .

DLCI = 45 Bearer chan 1 DLCI = 55

DLCI = 45

DLCI = 55

GBL_UL_DATA_THRPUT

GBL_UL_DATA_THRPUT_TIME_PERIOD

Figure 4-5 GBL_UL_DATA_THRPUT

4–8

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GBL_DL_DATA_THRPUT

GBL_DL_DATA_THRPUT
Description
This statistic measures the number of megabits transmitted on the downlink Gb link (GBL) for a given period of time. The Packet Control Unit (PCU) will then calculate the instantaneous throughput by dividing the number of megabits received in the time interval. The time interval gbl_dl_thrput_time_period will be programmable. The PCU will filter this statistic by computing a moving average of the instantaneous throughput. The number of instantaneous throughput samples num_gbl_dl_data_thrput_samples used to compute the moving average will also be programmable. Refer to Figure 4-5 for an illustration of this statistic.

Pegging
This statistic is pegged by calculating the number of megabits received by the PCU during the interval, gbl_dl_thrput_time_period .

Analysis
This statistic can be used for the trend analysis of the average downlink throughput of the GBL. Reference Usage None. Network planning. Congestion. GBL Gauge.

Basis Type

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–9

GBL_DL_DATA_THRPUT_HIST

ISSUE 1 REVISION 2

GBL_DL_DATA_THRPUT_HIST
Description
This statistic is a histogram of the total downlink data throughput on the GBL for a measurement period at the PCU. The number of bins in the histogram is 10 and the ranges are programmable shown in Table 4-1. Table 4-1 GBL_DL_DATA_THRPUT_HIST bins 0 – 600 Bin 0 1 2 3 4 5 6 7 8 9 Range 0 – 30 31 – 71 71 – 110 111 – 140 141 – 170 171 – 230 231 – 300 301 – 400 401 – 500 501 – 600

Pegging
This statistic is pegged by calculating the number of megabits transmitted by the PCU during the interval gbl_dl_thrput_time_period .

Analysis
This statistic can be used for the trend analysis of GBL downlink throughput. Reference Usage None. Network planning. Congestion. Quality of service monitoring: Network accessibility. GBL. Normal Distribution.

Basis Type

4–10

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GBL_FLOW_CTRL_SENT

GBL_FLOW_CTRL_SENT
Description
This statistic indicates the number of flow control messages sent by the BSS to the Serving GPRS Support Node (SGSN). Each cell has a buffer that holds downlink data. When a cell buffer reaches a predetermined threshold, a flow control message is sent to the SGSN. Flow control is performed to match the flow of downlink data with air throughput. Refer to Figure 4-2 for an illustration of this statistic.

Pegging
This statistic pegs the number of flow control messages sent by the BSS and is pegged every time a flow control message is sent.

Analysis
This statistic can be used for trend analysis of the number of flow control messages sent by the BSS. Reference Usage None. Network planning. Congestion. Quality of service monitoring: Network accessibility. Cell. Counter.

Basis Type

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–11

GBL_FLUSH_REQS

ISSUE 1 REVISION 2

GBL_FLUSH_REQS
Description
This statistic counts the number of flush requests received on the GBL. Refer to Figure 4-3 for an illustration of this statistic.

Pegging
This statistic is pegged each time a flush request is received on the GBL to flush the Logical Link Control (LLC) Protocol Data Unit (PDU) for a particular mobile station.

Analysis
This statistic can be used for the trend analysis of the number of flushable messages received by the BSS. Reference Usage None. Network planning. Congestion. BSS. Counter.

Basis Type

4–12

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GBL_LINK_INS

GBL_LINK_INS
Description
This duration statistic will be started by the GPRS PCU each time the GBL becomes in service (INS). The statistic GBL_LINK_INS willl stop each time the GBL has gone out of service. The time available for this statistic will be reported in milliseconds.

Pegging
The timer for this statistic will start once the GBL transitions to the B-U state. The timer for this statistic will stop once the GBL is no longer in the B-U state.

Analysis
This statistic can be used for trend analysis of the utilization of in-service GBL. Reference Usage None. Network accessibility Fault finding. Protocol utiliztion. GBL. Duration.

Basis Type

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–13

GBL_PAGING_REQS

ISSUE 1 REVISION 2

GBL_PAGING_REQS
Description
This statistic counts the number of paging requests received on the GBL. Refer to Figure 4-4 and Figure 4-8 for an illustration of this statistic.

Pegging
This statistic is pegged each time a page request is received on the GBL to page a mobile.

Analysis
This statistic can be used for the trend analysis of the number of circuit switched and packet switched pages received by the BSS from the SGSN. Reference Usage None. Network planning. Congestion. BSS. Counter.

Basis Type

4–14

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GBL_UL_DATA_THRPUT

GBL_UL_DATA_THRPUT
Description
This statistic measures the number of kilobits of data information transmitted on the uplink of the GBL for a given period of time. The PCU will then calculate the instantaneous throughput by dividing the number of megabits transmitted by the time interval. The time interval gbl_ul_thrput_period will be programmable. The PCU will filter this statistic by computing a moving average of the instantaneous throughput. The number of instantaneous throughput samples num_gbl_ul_thrput_samples used to compute the moving average will also be programmable. Refer to Figure 4-5 for an illustration of this statistic.

Pegging
This statistic is pegged by calculating the number of megabits received by the PCU during the interval, gbl_ul_thrput_period . The number of bins in the histogram is 10 and the ranges are programmable shown in Table 4-2. Table 4-2 GBL_UL_DATA_THRPUT_HIST bins 0 – 600 Bin 0 1 2 3 4 5 6 7 8 9 Range 0 – 30 31 – 71 71 – 110 111 – 140 141 – 170 171 – 230 231 – 300 301 – 400 401 – 500 501 – 600

Analysis
This statistic can be used for the trend analysis of the average uplink throughput of the GBL. Reference Usage None. Network planning. Congestion. GBL. Gauge.

Basis Type

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–15

GBL_UL_DATA_THRPUT_HIST

ISSUE 1 REVISION 2

GBL_UL_DATA_THRPUT_HIST
Description
This statistic is a histogram of the total uplink data throughput on the GBL for a measurement period at the PCU. The number of bins in the histogram is 10 and the ranges are programmable.

Pegging
This statistic is pegged by calculating the number of megabits transmitted by the PCU during the interval gbl_ul_thrput_time_period .

Analysis
This statistic can be used for the trend analysis of GBL uplink throughput. Reference Usage None. Network planning. Congestion. Quality of service monitoring: Network accessiblility. GBL. Normal Distribution.

Basis Type

4–16

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GBL_UNAVAILABLE

GBL_UNAVAILABLE
Description
This statistic is the duration that the GBL is out of service. This statistic will stop when the GBL becomes in service. The available time will be reported in milliseconds.

Pegging
The timer for this statistic is started when the GBL transitions to a state which is not B-U. It is stopped when the GBL is in the B-U state.

Analysis
This statistic can be used for trend analysis of the duration of GBL outages, including those caused by operator interaction. Reference Usage None. Network accessibility. Fault finding. GBL. Duration.

Basis Type

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–17

Accessibility Statistic Diagrams

ISSUE 1 REVISION 2

Accessibility Statistic Diagrams
Figure 4-6 is a ladder diagram detailing the statistic channel_req_rej when it is pegged. It also shows the request and the response messages sent from the BSS/PCU to the mobile station. BSS/PCU MS

Immediate Assignment (AGCH)

Packet Resource Request

CHANNEL_REQ_REJ

PACKET ACESS REJECT

Figure 4-6 Accessibility CHANNEL_REQ_REJ

4–18

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Accessibility Statistic Diagrams

Figure 4-7 is a ladder diagram detailing the statistics gprs_access_per_rach and gprs_access_per_agch when pegging occurs. It also shows the request and the response messages sent from the BSS/PCU to the mobile station. BSS/PCU MS

Channel Request (RACH)

GPRS_ACCESS_PER_RACH

GPRS_ACCESS_PER_AGCH Immediate Assignment (AGCH)

Figure 4-7 GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–19

Accessibility Statistic Diagrams

ISSUE 1 REVISION 2

Figure 4-8 is a ladder diagram detailing the statistics gbl_paging_reqs , gprs_access_per_pch, gprs_access_per_rach, and gprs_access_per_agch when pegging occurs. It also shows the request and response messages sent from the SGSN to the BSS/PCU and to the mobile station. SGSN BSS/PCU MS

BSSGP PS PDU

GBL_PAGING_REQS GPRS_ACCESS_PER_PCH PACKET PAGING REQEST (PCH)

Channel Request (RACH) GPRS_ACCESS_PER_RACH

GPRS_ACCESS_PER_AGCH Immediate Assignment (AGCH)

Figure 4-8 Accessiblility and GBL statistics

4–20

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Accessibility Statistic Diagrams

Figure 4-9 is a ladder diagram detailing three MS class type statistics and when pegging occurs. It also shows the request and response messages sent from the BSS/PCU to the mobile station. BSS/PCU MS

Immediate Assignment (AGCH)

Packet Resource Request

MS_CLASS_1_10_REQ

MS_CLASS_11_20_REQ

MS_CLASS_21_29_REQ

CHANNEL_REQ_REC

Figure 4-9 MS CLASS Statistics

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–21

Accessibility Statistic Diagrams

ISSUE 1 REVISION 2

Figure 4-10 details the gprs_channels_switched statistic.

TCH

SW SW SW RES RES RES GPRS GPRS GPRS GPRS GPRS GPRS GPRS

SW

GPRS_CHANNELS_SWITCHED

TCH

TCH

SW SW SW RES RES RES GPRS GPRS GPRS GPRS GPRS GPRS

Figure 4-10 CHANNELS_SWITCHED

4–22

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

CHANNEL_REQS_REC

CHANNEL_REQS_REC
Description
This statistic counts the number of channel or resource request messages received by the Packet Control Unit (PCU). Refer to Figure 4-9 for an illustration of this statistic.

Pegging
This statistic pegs for each channel request message received by the PCU.

Analysis

Reference Usage Basis Type

None. Network planning. Cell. Counter.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–23

CHANNEL_REQS_REJECT

ISSUE 1 REVISION 2

CHANNEL_REQS_REJECT
Description
This statistic measures the number of packet channel or resource request received by the PCU that were rejected. Refer to Figure 4-6 for an illustration of this statistic.

Pegging
This statistic is pegged when an immediate assignment reject message is sent to the MS in response to a packet channel or resource request. This is due to no channels being available to be allocated.

Analysis

Reference Usage

None. Network planning. Congestion. Cell. Counter.

Basis Type

4–24

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS_ACCESS_PER_AGCH

GPRS_ACCESS_PER_AGCH
Description
This statistic counts the Immediate Assignment messages sent on the Access Grant Channel (AGCH) of a cell for packet data service. The air interface message on the AGCH for packet immediate assignment and immediate assignment reject, will contain only on MS. Access Grants for more than one MS may be contained in one Access Grant message. An Access Grant for more than one MS is only pegged once. This count includes Immediate Assignment, Immediate Extended, and Immediate Assignment Reject messages sent on the AGCH of a cell. Refer to Figure 4-7 and Figure 4-8 for an illustration of this statistic.

Pegging
This statistic is pegged when an access grant message is sent on the AGCH on a cell for packet data service.

Analysis
This statistic can be used for trend analysis of Immediate Assignment messages sent on the AGCH of a cell. Reference Usage None. Radio resource allocation statistics. Network planning. Cell. Counter.

Basis Type

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–25

GPRS_ACCESS_PER_PCH

ISSUE 1 REVISION 2

GPRS_ACCESS_PER_PCH
Description
This statistic counts Paging Request messages sent on the Paging Channel (PCH) of a cell for GPRS mobiles. Pages for circuit switch and packet switch MS can be combined in on PCH message. Refer to Figure 4-8 for an illustration of this statistic.

Pegging
This statistic is pegged when at least one general packet radio system (GPRS) mobile is contained in the message sent over the PCH.

Analysis
This statistic can be used for trend analysis of paging request messages sent on the PCH of a cell for packet and GPRS mobile system. Reference Usage None. Radio resource allocation statistics. Network planning. Cell. Counter.

Basis Type

4–26

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS_ACCESS_PER_RACH

GPRS_ACCESS_PER_RACH
Description
This statistic counts Channel Request messages sent on the Random Access Channel (RACH) of a cell.

Pegging
Refer to Figure 4-7 and Figure 4-8 for an illustration of this statistic.

Analysis
This statistic can be used for trend analysis of Immediate Assignment messages sent on the RACH of a cell. Reference Usage None. Radio resource allocation statistics. Network planning. Cell. Counter.

Basis Type

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–27

GPRS_CHANNELS_SWITCHED

ISSUE 1 REVISION 2

GPRS_CHANNELS_SWITCHED
Description
This statistic counts the number of times that a Packet Data Traffic Channel (PDTCH) is switched to a Traffic Channel (TCH). Refer to Figure 4-10 for an illustration for this statistic.

Pegging
This statistic will be incremented each time a PDTCH is switched to a TCH or when a TCH is switched to a PDTCH.

Analysis

Reference Usage Basis Type

None.

Cell. Counter.

4–28

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

MS_CLASS_1_10_REQ

MS_CLASS_1_10_REQ
Description
This counter array statistic tracks the number of requests received for the mobile station classes 1 through 10. Refer to Figure 4-9 for an illustration of this statistic. The units of each bin are 10 requests shown in Table 4-3. Table 4-3 MS_CLASS_1_10_REQ bins 1 through 10 Bin 0 1 2 3 4 5 6 7 8 9 Scenario MS_CLASS_1_REQ MS_CLASS_2_REQ MS_CLASS_3_REQ MS_CLASS_4_REQ MS_CLASS_5_REQ MS_CLASS_6_REQ MS_CLASS_7_REQ MS_CLASS_8_REQ MS_CLASS_9_REQ MS_CLASS_10_REQ Description Number of requests for class 1 Number of requests for class 2 Number of requests for class 3 Number of requests for class 4 Number of requests for class 5 Number of requests for class 6 Number of requests for class 7 Number of requests for class 8 Number of requests for class 9 Number of requests for class 10

Pegging
This is one of three stats that is pegged every time there is an uplink request from an MS. The other two are MS_CLASS_11_19_REQ and MS_CLASS_20_29_REQ.

Analysis

Reference Usage Basis Type

GSM 05.02, 6.2.0, Annex B. Network planning. Cell. Counter array.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–29

MS_CLASS_11_20_REQ

ISSUE 1 REVISION 2

MS_CLASS_11_20_REQ
Description
This counter array statistic tracks the number of requests received for the mobile station classes 11 through 20. Refer to Figure 4-9 for an illustration for this statistic. The units of each bin are in 10 requests shown in Table 4-4. Table 4-4 MS_CLASS_11_20_REQ bins 11 through 20 Bin 0 1 2 3 4 5 6 7 8 9 Scenario MS_CLASS_11_REQ MS_CLASS_12_REQ MS_CLASS_13_REQ MS_CLASS_14_REQ MS_CLASS_15_REQ MS_CLASS_16_REQ MS_CLASS_17_REQ MS_CLASS_18_REQ MS_CLASS_19_REQ MS_CLASS_20_REQ Description Number of requests for class 11 Number of requests for class 12 Number of requests for class 13 Number of requests for class 14 Number of requests for class 15 Number of requests for class 16 Number of requests for class 17 Number of requests for class 18 Number of requests for class 19 Number of requests for class 20

Pegging
This is one of three stats that is pegged every time there is an uplink request from an MS. This is one of three stats that is pegged every time there is an uplink request from an MS. The other two are MS_CLASS_1_10_REQ and MS_CLASS_20_29_REQ.

Analysis

Reference Usage Basis Type

GSM 05.02, 6.2.0, Annex B. Network planning. Cell. Counter array.

4–30

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

MS_CLASS_21_29_REQ

MS_CLASS_21_29_REQ
Description
This counter array statistic tracks the number of requests received for the mobile station classes 21 through 29. Refer to Figure 4-9 for an illustration for this statistic. The units of each bin are in 10 requests shown in Table 4-5. Table 4-5 MS_CLASS_21_29_REQ bins 21 through 29 Bin 0 1 2 3 4 5 6 7 8 Scenario MS_CLASS_21_REQ MS_CLASS_22_REQ MS_CLASS_23_REQ MS_CLASS_24_REQ MS_CLASS_25_REQ MS_CLASS_26_REQ MS_CLASS_27_REQ MS_CLASS_28_REQ MS_CLASS_29_REQ Description Number of requests for class 21 Number of requests for class 22 Number of requests for class 23 Number of requests for class 24 Number of requests for class 25 Number of requests for class 26 Number of requests for class 27 Number of requests for class 28 Number of requests for class 29

Pegging
This is one of three stats that is pegged every time there is an uplink request from an MS. This is one of three stats that is pegged every time there is an uplink request from an MS. The other two are MS_CLASS_1_10_REQ and MS_CLASS_11_19_REQ.

Analysis

Reference Usage Basis Type

GSM 05.02, 6.2.0, Annex B. Network planning. Cell. Counter array.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–31

MS_CLASS_21_29_REQ

ISSUE 1 REVISION 2

4–32

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Throughput Statistic Diagrams

Throughput Statistic Diagrams
Figure 4-11 is a ladder diagram detailing the statistic air_ul_data_blks and when pegging occurs. It also shows the request and response messages sent from the BSS/PCU to the mobile station.

BSS/PCU

MS

PACKET UPLINK ASSIGNMENT

DATA BLOCK

AIR_UL_DATA_BLKS

QOS1 QOS2 QOS3 QOS4 CS1 CS1 CS1 CS1

QOS1 QOS2 QOS3 QOS4 CS2 CS2 CS2 CS2

Figure 4-11 Uplink Data Transfer

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–33

Throughput Statistic Diagrams

ISSUE 1 REVISION 2

Figure 4-12 is a ladder diagram detailing the statistic air_dl_data_blks and when pegging occurs. It also shows the request and response messages sent from the BSS/PCU to the mobile station.

BSS/PCU

MS

PACKET DOWNLINK ASSIGNMENT

DATA BLOCK

AIR_DL_DATA_BLKS

QOS1 QOS2 QOS3 QOS4 CS1 CS1 CS1 CS1

QOS1 QOS2 QOS3 QOS4 CS2 CS2 CS2 CS2

Figure 4-12 Downlink Data Transfer

4–34

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Throughput Statistic Diagrams

Figure 4-13 illustrates the dl_chan_asgn_duration statistic.

MS 5

MS DL_CHAN_ASGN_DURATION

INC IN DECISECONDS 25 25 1 PDCH

35
2 PDCH

II
1

I
2 3 4 5

7 6 8 PDCH PDCH PDCH PDCH PDCH PDCH PDCH PDCH

Figure 4-13 Downlink Channels Assigned Duration

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–35

Throughput Statistic Diagrams

ISSUE 1 REVISION 2

Figure 4-14 illustrates the ul_chan_asgn_duration statistic.

MS 5

MS UL_CHAN_ASGN_DURATION

INC IN DECISECONDS 25 25 1 PDCH

35
2 PDCH

II
1

I
2 3 4 5

7 6 8 PDCH PDCH PDCH PDCH PDCH PDCH PDCH PDCH

Figure 4-14 Uplink Channels Assigned Duration

4–36

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

AIR_DL_DATA_BLKS

AIR_DL_DATA_BLKS
Description
This counter array statistic reports the number of blocks sent by the PCU for each quality of service level and coding scheme combination. The count is rounded to the nearest 100 blocks. Refer to Figure 4-12 for an illustration of this diagram. The counters are defined in Table 4-6. Table 4-6 AIR_DL_DATA_BLKS counters Bin 0 1 2 3 4 5 6 7 Scenario QOS1_CS1 QOS2_CS1 QOS3_CS1 QOS4_CS1 QOS1_CS2 QOS2_CS2 QOS3_CS2 QOS4_CS2 Description Quality of service level 1, coding scheme 1 Quality of service level 2, coding scheme 1 Quality of service level 3, coding scheme 1 Quality of service level 4, coding scheme 1 Quality of service level 1, coding scheme 2 Quality of service level 2, coding scheme 2 Quality of service level 3, coding scheme 2 Quality of service level 4, coding scheme 2

Pegging
The appropriate bin is incremented by the amount of data blocks sent for the quality of service and coding scheme.

Analysis
This statistic shall be pegged at the PCU. Reference Usage Basis Type Network planning. Cell. Counter array.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–37

AIR_UL_DATA_BLKS

ISSUE 1 REVISION 2

AIR_UL_DATA_BLKS
Description
This counter array statistic reports the number of data blocks received by the PCU for each qualilty of service level and coding scheme combination. The count is rounded to the nearest 100 blocks. Refer to Figure 4-11 for an illustration of this statistic. The counters are defined in Table 4-7. Table 4-7 AIR_UL_DATA_BLKS counters Bin 0 1 2 3 4 5 6 7 Scenario QOS1_CS1 QOS2_CS1 QOS3_CS1 QOS4_CS1 QOS1_CS2 QOS2_CS2 QOS3_CS2 QOS4_CS2 Description Quality of service level 1, coding scheme 1 Quality of service level 2, coding scheme 1 Quality of service level 3, coding scheme 1 Quality of service level 4, coding scheme 1 Quality of service level 1, coding scheme 2 Quality of service level 2, coding scheme 2 Quality of service level 3, coding scheme 2 Quality of service level 4, coding scheme 2

Pegging
The appropriate bin is incremented by the amount of data blocks received for the quality of service and coding scheme.

Analysis
This statistic shall be pegged at the PCU. Reference Usage Basis Type None. Network planning. Cell. Counter array.

4–38

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

DL_CHAN_ASGN_DURATION

DL_CHAN_ASGN_DURATION
Description
This counter array statistic tracks the number of channels that are simultaneously in use (assigned) by an mobile station in the downlink direction. The bins are durations in that they measure the amount of time in deciseconds that each number of channels were used. Refer to Figure 4-13 for an illustration of this statistic. Channels 1 to 8 are shown in Table 4-8. Table 4-8 DL_CHAN_ASGN_DURATION channels 1 through 8 Bin 0 1 2 3 4 5 6 7 Scenario 1_DATA_CHAN_ASGND 2_DATA_CHAN_ASGND 3_DATA_CHAN_ASGND 4_DATA_CHAN_ASGND 5_DATA_CHAN_ASGND 6_DATA_CHAN_ASGND 7_DATA_CHAN_ASGND 8_DATA_CHAN_ASGND Description 1 data channel assigned 2 data channel assigned 3 data channel assigned 4 data channel assigned 5 data channel assigned 6 data channel assigned 7 data channel assigned 8 data channel assigned

Pegging
The appropriate bin (according to the number of timeslots that are in use for the cell) will be increased by 1 for the cell. Thus, each bin is measured in units of deciseconds.

Analysis
This statistic can be used for trend analysis of channel assignment in the downlink direction for the cell. By observing a daily or weekly trend of the amount of time allocated to each of the bins, the information may be used to determine where or not additional resources may be needed. Reference Usage None. Network planning. Optimization. Cell. Counter array.

Basis Type

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–39

TOTAL_AIR_DL_AVAILABLE_BW

ISSUE 1 REVISION 2

TOTAL_AIR_DL_AVAILABLE_BW
Description
This statistic counts the total number of Radio Link Control (RLC) data blocks available for downlink transfer at the PCU.

Pegging
The amount of available bandwidth is calculated by summing up the number of available RLC blocks in a second (50, each takes up 20 milliseconds) and then multiplying by the number of timeslots both in use and not in use for GPRS.

Analysis

Reference Usage

None. Network planning. Network accessiblility. Cell. Counter.

Basis Type

4–40

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

TOTAL_AIR_UL_AVAILABLE_BW

TOTAL_AIR_UL_AVAILABLE_BW
Description
This statistic counts the total number of RLC data blocks available for uplink transfer at the PCU.

Pegging
The amount of available bandwidth is calculated by summing up the number of available RLC blocks in a second (50, each one takes up 20 milliseconds), and then multiplying by the number of timeslots both in use and not in use for GPRS.

Analysis

Reference Usage

None. Network planning. Network accessiblity. Cell. Counter.

Basis Type

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

4–41

UL_CHAN_ASGN_DURATION

ISSUE 1 REVISION 2

UL_CHAN_ASGN_DURATION
Description
This counter array statistic tracks the number of channels that are simultaneously in use (assigned) by a mobile station in the uplink direction. The bins are durations in that they measure the amount of time in deciseconds that each number of channels were used. Refer to Figure 4-14 for an illustration of this statistic. Channels 1 to 8 are shown in Table 4-9. Table 4-9 DL_CHAN_ASGN_DURATION channels 1 through 8 Bin 0 1 2 3 4 5 6 7 Scenario 1_DATA_CHAN_ASGND 2_DATA_CHAN_ASGND 3_DATA_CHAN_ASGND 4_DATA_CHAN_ASGND 5_DATA_CHAN_ASGND 6_DATA_CHAN_ASGND 7_DATA_CHAN_ASGND 8_DATA_CHAN_ASGND Description 1 data channel assigned 2 data channel assigned 3 data channel assigned 4 data channel assigned 5 data channel assigned 6 data channel assigned 7 data channel assigned 8 data channel assigned

Pegging
The appropriate bin (according to the number of timeslots are in use for the cell) will be increased by 1 for the cell. Thus, each bin is measured in units of deciseconds.

Analysis
This statistic can be used for trend analysis of channel assignment in the uplink direction for the cell. By observing a daily or weekly trend of the amount of time allocated to each of the bins, the information may be used to determine where or not additional resources may be needed. Reference Usage None. Network planning. Optimization. Cell. Counter array.

Basis Type

4–42

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 5

GSN Architecture

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Chapter 5 GSN Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSN in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSN Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SGSN Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functional Entities and Hardware Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPX 8216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I/O Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCP 750 – L252 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCP750 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PMC 860 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATTACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATTACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATTACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATTACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Explicit Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Explicit Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implicit Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routing Area Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking User Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modify GMM Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Session Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP Context Activation MS Initiated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP Context Activation – Transmission function . . . . . . . . . . . . . . . . . . . . . . . . . . . Uplink Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP Context Accept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activate Downlink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDP Context Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging for GPRS Downlink Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmission Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNDCP Peer to Peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNDCP XID Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LLC Peer to Peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN – PDP Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

i
5–1 5–2 5–2 5–4 5–6 5–8 5–10 5–12 5–14 5–16 5–18 5–20 5–22 5–24 5–26 5–28 5–30 5–32 5–34 5–36 5–38 5–40 5–40 5–40 5–42 5–44 5–46 5–48 5–48 5–50 5–52 5–54 5–56 5–58 5–60 5–60 5–62 5–64

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

iii

ISSUE 1 REVISION 2

iv

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Objectives

Objectives
On completion of this course the students will be able to: S S S Identify the major components of the GSN Understand the Generic function of GSN entities Identify the signalling between GSN entities for Mobility Management and Session Management

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–1

GPRS Overview

ISSUE 1 REVISION 2

GPRS Overview
General Packet Radio Service (GPRS) is a Global System for Mobile communications (GSM) service that enables mobile subscribers to send data packets over GSM radio channels to external data networks. The main benefit of GPRS is that it reserves specifically for times when there is something to send. the same radio resource is shared by all mobile stations (MSs) in a cell, providing effective use of scarce resources. GPRS facilitates several applications, such as telemetry, train control systems, interactive data access, toll road charging systems, and internet browsing using the World Wide Web. See illustration opposite.

GSN in GPRS
The GPRS Support Node (GSN) is the main element in the GPRS infrastructure. It is a high performance, broadband packet-switching node that provides connection and interworking with various data networks, mobility management with the GPRS registers, and delivery of data packets to mobile stations. The GSN can be physically integrated with the mobile switching centre (MSC) or it can be a separate network element based on the architecture of data network routers. the user data flows directly between the GSN and the base station subsystem (BSS). Physically, the data can flow transparently through the MSC. All GSNs must implement the Gn interface protocols in order to communicate with other GSNs in the same Public Land Mobile Network (PLMN). A limited internal home location register (HLR) function within the (Serving GPRS Support Node) SGSN is provided for basic subscriber management purposes.

5–2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

Example of a GPRS system

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–3

GPRS Overview

ISSUE 1 REVISION 2

GSN Software Architecture
The GSN software architecture is designed on five functional planes. They are: 1. S S 2. S S 3. S S S S 4. S S 5. S S Control function Signalling information between different GPRS components, such as MS Attach and PDP activate. Macroscopic MS Context information Transmission function Data traffic transmission between different GPRS components Microscopic MS Context Information OAMP function Interface with OMC–G Interface with Control and Transmission function for collection of OAMP data (e.g. Statistics) Interface for forwarding of alarms to the OMC–G from the Control function and Transmission function Configuration Management of Control and Transmission function Accounting Metering function Interface with external billing system Collection of billing information from Control and Transmission function Network Support function Domain name server Time server

5–4

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

System Framework

Billing/ Accounting System

Network Support Server

OMC-G

Accounting Metering Function

Control Function OAMP Function Transmission Function
GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY
5–5

EMOTOROLA LTD. 2000

GPRS Overview

ISSUE 1 REVISION 2

SGSN Architecture
Functional Entities
The SGSN consists of the following software functional entities: SGSN – CONTROL Part of the Control Plane, the SGSN–CONTROL is responsible for handling SGSN signalling, such as MS attach, PDP activate. It contains macroscopic information about the MS, i.e. VLR

Transmission Function
The SGSN Transmission function is made up of two functional entities, the SGSN–GNPROC and the SGSN–GBPROC. SGSN–GNPROC – Part of the transmission plane and responsible for GTP, Relay, SNDCP and LLC protocols. It serves as an anchor and point for an MS within an SGSN. Responsible for paging of MSs and receiving/forwarding data to/from the appropriate SGSN–GBPROC. The GNPROC contains microscopic MS context information; MS MM state, PDP state and cell location. SGSN–GBPROC – Also part of the transmission plane responsible for BSSGP protocol. Each GBPROC is connected to one BSS via a number of E1 links. The GBPROC is responsible for QOS scheduling and flow control. The functional entity contains cell and frame relay PVC mapping.

SS7 Function
The SGSN has a number of interfaces to other network entities that use the SS7 protocol stack for signalling exchange. The SS7 function is the functional component identified to handle these interfaces. For the trial system the SGSN SS7 function holds a internal HLR database to simulate a GR interface to a HLR.

5–6

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

SGSN Architecture
SS7 FUNCTION SF

HLR

CONTROL FUNCTION

SGSN – CONTROL COMMHUB

SGSN GNPROC SGSN GbPROC FR E1 FR E1

BSS

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–7

GPRS Overview

ISSUE 1 REVISION 2

Functional Entities and Hardware Mapping
The functional entities for the SGSN can be mapped to the same processor board or distributed among processor boards. This allows the configuration of GSN to adapt to the different needs of networks.

SGSN Architecture
The SGSN functional entities will be split into functions. The Control function and the Transmission function.

Control Function
The Control function will comprise an instance of SGSN–control and SGSN–OAMP. The Control function holds the OAMP function for the CF and the TF.

Transmission Function
The SGSN–GBPROC and SGSN–GNPROC are combined together to form the Transmission function on a processor board. The board will have 2 mezzanine interface boards supporting up to 4 E1s to allow connection to the BSS.

SS7 Function
The SS7 function holds a internal HLR simulating a Gr interface to a HLR.

5–8

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

Functional entities and hardware mapping

SF

SGSN–CF

SGSN TF

SF

OAMP tf

sgsn – gbproc HLR sgsn – control sgsn – gnproc E1 I/F

BSC

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–9

GPRS Overview

ISSUE 1 REVISION 2

CPX 8216
The CPX 8216 is a sixteen slot, high availability Compact PCI system with two separate six slot Compact PCI 1/0 domains and the capability to contain redundant CPU modules and redundant Hot–Swap Controller (HSC) modules in the remaining 2 slots of each domain. CPX 8216 is designed as a highly reliable system by providing several levels of system reliability based on hardware and software. The system allows for integration of standard off–the–shelf Compact PCI hardware.

5–10

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–11

GPRS Overview

ISSUE 1 REVISION 2

System Configuration
The CPX 8216 is a flexible system that allows for multiple configuration of processor control, its redundancy and peripheral configurations. Three possible configurations: S S S Simpler system containing a single CPU and Hop Swap Controller controlling both domains. An active/passive system where one pair of CPU and HSC control both domains with a stby CPU and HSC. Active/Active – each CPU runs a single domain while also serving as a backup to the other CPU.

For field trial the backplane is not used and there is no system slot processor.

5–12

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

Simplex
I/O C P U I/O H S C A I/O

I/O DOMAIN A
I/O I/O I/O I/O I/O I/O

A

I/O DOMAIN B
I/O I/O I/O I/O I/O

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

Active /Passive
I/O C P U I/O H S C B I/O C P U B I/O H S C A I/O

I/O DOMAIN A
I/O I/O I/O I/O I/O I/O

A

I/O DOMAIN B
I/O I/O I/O I/O I/O

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

Active/Active
ACTIVE CPU
I/O C P U I/O H S C B I/O C P U B I/O H S C A I/O

ACTIVE HSC

I/O DOMAIN A
I/O I/O I/O I/O I/O I/O

A

I/O DOMAIN B
I/O I/O I/O I/O I/O

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

PASSIVE CU/HSC

S L O T

S L O T

S L O T

S L O T

S L O T

S L O T

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–13

GPRS Overview

ISSUE 1 REVISION 2

I/O Configurations
The CPX 8216 contains two independent eight slot Compact PCI buses. One slot in each bus is dedicated to a system processor and the other is needed for the hop swap controller (HSC). This leaves six slots on each bus to support 1/0 devices or non–system processors.

5–14

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

EMOTOROLA LTD. 2000

I/O Slot (Black I/O Slot (Black I/O Slot (Black I/O Slot (Black I/O Slot (Black I/O Slot (Black CPU (Red) None CPU (Red) None I/O Slot (Black I/O Slot (Black I/O Slot (Black I/O Slot (Black I/O Slot (Black I/O Slot (Black

I/O Tms (Black I/O Tms (Black I/O Tms (Black I/O Tms (Black I/O Tms (Black I/O Tms (Black CPU Tms (Red) Bridge (Tan) CPU Tms (Red) Bridge (Tan) I/O Tms (Black I/O Tms (Black I/O Tms (Black I/O Tms (Black I/O Tms (Black I/O Tms (Black
Backplane

1 2 3 4 5 6

FOR TRAINING PURPOSES ONLY

7

GPRS01: GPRS Architecture
5–15

Rear Slots

Front Slots

8 9 10 11 12 13 14 15 16

GPRS Overview

GPRS Overview

ISSUE 1 REVISION 2

Power Supply
The CPX 8216 requires a minimum of two power/fan slot modules and a fan only slot module to provide adequate cooling. The system can contain a third power supply/fan slot as part of an N+1 strategy. The modules are hot swapable for AC and DC environments. The fans on the power supplies provide the forced air cooling for the cage. Only two fans are necessary for adequate system cooling with the third fan providing N+1 cooling redundancy. The power distribution panel is located in the rear of the chassis below the transition module card cage, distributes Ac or DC input power to the system power supplies. These three versions of power distribution power supply; AC, single input DC and dual input DC.

Power Supply O/P
VOLTAGE +5.06V +3.36V –12.1V +12.1V REGULATION $3% $3% $5% $5% MINIMUM LOAD 0.5A 0.5A 0.3A 0.3A MAXIMUM LOAD 40.0A 40.0A 8.0A 4.0A

Power Supply I/P
VOLTAGE AC 90 – 132 or 190 – 260Vac DC 40 – 72Vdc FREQUENCY 47 – 63Hz – INPUT CURRENT 6.0A max at 115Vac 3A max at 220Vac 113A – 48Vdc at 475V

5–16

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–17

GPRS Overview

ISSUE 1 REVISION 2

MCP 750 – L252
MCP 750 is a single slot single board computer equipped with an MCP 750 power PC TM 750 series microprocessor. The card has the following characteristics: S S S S S S S S 128 MB DRAM One MB flash memory on board (16 bit) Additional 64 bit 8 MB flash memory Compact flash memory with 48MB compact flash One 10/100 Base TX Ethernet port One Async Serial port One PMC slot USB

5–18

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–19

GPRS Overview

ISSUE 1 REVISION 2

MCP750
MCP 750 offers many features desirable in a Compact PCI computer system, such as: Compact PCI Bus – MCP750 interfaces to a Compact Peripheral Component Bus (CPCI) using a PCI to PCI bridge. This device allows 64 bit primary and secondary data access to the CPCI bus on the cage backplane and the on–board local CPCI bus. The I/0 peripheral interfaces present on the onboard PCI bus include: S S S S S S S S S S S S 10/100 Base T Ethernet interface UDB host controller Fast EIDE interface One PMC slot

From the ISA bus are: 2 async serial ports 2 async/synch serial ports keyboard port mouse port floppy disk controller parallel port real time clock NVRAM

Key to the MCP750 is the industry standard mezzanine interface (DCI Mezzanine Card). PCI modules offer a variety of possibility for 1/0 expansion.

5–20

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

MCP 750 Block Diagram

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–21

GPRS Overview

ISSUE 1 REVISION 2

PMC 860 Module
The PMC/860 module has been designed to provide network interface functionality for E1 or T1 lines on a single slot PMC format via the front panel or via rear transition module 1/0. PMC/860 provides: S S S S S S S PCI bus interface via PMC connectors 2 E1 or T1 line interfaces via front panel Serial 1/0 port 40mhz Power DUICC processor 4MB DRAM 128 KB span Up to 2MB boot flash PROM

5–22

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

FORCE SERIAL

Line 1

Line 2

E1–IRD

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–23

GPRS Overview

ISSUE 1 REVISION 2

ATTACH
The MS makes an Attach procedure by the sending of an Attach Request to the SGSN. The Request contains the information elements:– S S S S S S S S S Attach Type – GPRS or IMSI or Combined Attach MS Network Capability – SMS + Encryption Algorithm capab Ciphering Key Sequence QOS Parameters Force to Stby Old P–TMSI or IMSI MS Radio Access Capabilities – includes power capability multiple class Old RAI Requested ready timer value

If the mobile identifies itself using a PTMSI for which the SGSN CF has no GPRS Mobility Management (GMM) context, then Subscriber Identification takes place to gain the MS IMSI. If the IMSI is included in the Attach Request then examination of the IMSI to determine if the MS belongs to the SGSN PLMN is carried out. Subscriber Identification is performed by the SGSN CF sending an Identity Request to the MS requesting the MS IMSI. The MS will respond with an IDENTITY RESPONSE containing the IMSI.

5–24

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

MS
ATTACH REQUEST

CF

IDENTITY REQUEST

IDENTITY RESPONSE

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–25

GPRS Overview

ISSUE 1 REVISION 2

ATTACH
HLR Interaction
As the SGSN CF does not have a GMM context for the MS, the HLR must be updated with the location of the MS by sending an HPDATE LOCATION LOCATION message identifying the SGSN and including the MS IMSI. Updating the HLR with the new MS location results in the HLR sending the SGSN the subscriber data. FIELD IMSI MSISDN SGSN Number SGSN Address SMS Parameters MS Purged for GPRS MNRG DESCRIPTION IMSI is the main reference key. The basic MSISDN of the MS. The SS7 address of the SGSN currently serving this MS. The IP address of the SGSN currently serving this MS. SMS–related parameters, e.g. operator–determined barring. Indicates that the MM and PDP contexts of the MS are deleted from the SGSN. Indicates that the MS is not reachable through an SGSN, and that the MS is marked as not reachable for GPRS at the SGSN and possibly at the GGSN. The GSN number and optional IP address pair related to the GGSN that shall be contacted when activity from the MS is detected and MNRG is set. The GSN number shall be either the number of the GGSN or the protocol–converting GSN as described in the subclauses “MAP–based GGSN – HLR Signalling” and “GTP and MAP–based GGSN – HLR Signalling”.

GGSN–list

Each IMSI contains zero or more of the following PDP context subscription records: PDP Type PDP Address QoS Profile Subscribed PDP type, e.g. X.25 or IP. PDP address, e.g. an X.121 address. This field shall be empty if dynamic addressign is allowed. The quality of service profile subscribed for this PDP context. QoS Profile Subscribed is the default level if a particular QoS profile is not requested. Specifies whether the MS is allowed to use the APN in the domain of the HPLMN only, or additionally the APN in the domain of the VPLMN. A label according to DNS naming conventions describing the access point to the external packet data network.

VPLMN Address Allowed

Access Point Name

The SGSN CF creates an MM Context for MS and stores the MS GMM Context information (IMSI, MS NETWORK CAPABILITIES, DRX PARAMETERS, CELL ID and RAI) and the MS PDP CONTEXT information (IMSI, PDP Address, QoS Subscribed, Dynamic Address Allowed, VPLMN address allowed and Access Point Name.
5–26

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

MS
ATTACH REQUEST IDENTITY REQUEST IDENTITY RESPONSE

CF

HLR

UPDATE LOCATION INSERT SUBSCRIBER DATA INSERT SUBSCRIBER DATA ACK

UPDATE LOCATION

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–27

GPRS Overview

ISSUE 1 REVISION 2

ATTACH
If the Attach Request message is valid, and the SGSN CF has identified the MS and it belongs to the SGSN PLM, then the SGSN CF will attempt to configure the Transmission Function (TF). The configuration will allocate a new Local TLLI and create a TF GMM context.

TLLI Assignment Procedure
Temporary Logical Link Identity (TLLI) consists of 32 bits built either on the basis of a P–TMSI in the case of local or foreign TLLI or a random number in the case of Random TLLI. MS derives TLLI from the P–TMSI allocated to it from the SGSN. TLLI BITS 31 1 1 0 30 1 0 1 29 T T 1 28 T T 1 27 T T 1 26–0 T T R TYPE OF TLLI Local Foreign Random

T = Bits derived from P–TMSI R = Random Bits A local TLLI is the same as a P–TMSI with the high order bits 31 and 30 set to one and the rest of the bits set to the P–TMSI. The CF and Tf share the responsibility for the formation of the TLLI, the CL being responsible for the top 16 bits and the TF being responsible for the bottom 16 bits. The CF encodes the portion of the local TLLI and passes it to the TF in the Create MMCtx_REQ message along with GMM context information for the MS for the TF to store in its Mobility Management (MM) context. The TF creates an MM entity for the MS, storing the MM timer values, IMSI, Radio Access Capabilities and DRX Parameters. The TF concedes its half of the TLLI and returns the completed local TLLI to the SGSN CF in the CREATEMMCtx_CNF message. The CF now has the complete local TLLI and therefore the P–TMSI as Local TLLI = P–TMSI.

5–28

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

MS
ATTACH REQUEST IDENTITY REQUEST

CF

HLR

TF

IDENTITY RESPONSE UPDATE LOCATION

INSERT SUBSCRIBER DATA INSERT SUBSCRIBER DATA ACK

UPDATE LOCATION ACK

CREATE MMCTx – REQ

CREATE MMCTx – CNF ATTACH ACCEPT

ATTACH COMPLETE

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–29

GPRS Overview

ISSUE 1 REVISION 2

ATTACH
The SGSN CF, upon return of the complete Local TLLI/P–TMSI from the TF, will send the ATTACH ACCEPT message to the MS containing:– S S S S S S Attach Result – GPRS only or combined GPRS/IMSI attached Force to Stby Periodic RA Timer Radio Priority for SMS – Radio Priority Level 1–4 Routing Area Identification Alloc PTMSI – P–TMSI = Local TLLI Ready Timer Value – SGSN Configured Value

The GPRS Mobility Management (GMM) context at the SGSN CF will go to GMM–REGISTERED PENDING until the MS replies with the ATTACH Complete Message. On receipt of the complete message from the MS using the assigned Local TLLI the GMM state goes to GMM–REGISTERED.

GPRS Attach Failure Response
Identity Request Timer RANGE 8 SECS RE–SEND MAXIMUM T3322 STARTED STOPPED IDENTITY REQ IDENTITY RESP

MAX_ACCEPT_ATTEMPT

Attach Accept

T3350

STARTED STOPPED

ACCEPT ACCEPT ATTACH COMPLETE

RE–SEND MAXIMUM

MAX_IDENTIFICATION_ATTEMPT

If the Attach fails due to either HLR having no need of IMSI or Failure of Transmission function or Communication failure, the CF will send an Attach Reject to the MS and perform an Implicit Detach and log the event.

5–30

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

MS
ATTACH REQUEST

CF

HLR

TF

IDENTITY REQUEST START T3322 IDENTITY RESPONSE STOP T3322

UPDATE LOCATION

INSERT SUBSCRIBER DATA INSERT SUBSCRIBER DATA ACK

UPDATE LOCATION ACK

CREATE MMCTx – REQ

CREATE MMCTx – CNF ATTACH ACCEPT START T3350 ATTACH COMPLETE STOP T3350

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–31

GPRS Overview

ISSUE 1 REVISION 2

Detach
The Detach function enables a mobile to become detached from the network or for the network to detach a mobile from the network. There are two types of detach; Implicit and Explicit detach. Explicit Detach: Implicit Detach: MS or Network explicitly requests detach. Occurs in either or both MS and SGSN. No messages exchanged between MS and SGSN. Reason: Mobile Reachable Timer Expiration Lower Layer Failure occurs Paging Fault occurs Transmission Configuration occurs

Switch Off
If the Detach is implicit then messaging is passed between the MS and SGSN which will indicate if the detach is due to switch off or not. The result of a detach request with a detach type indicating switch off = TRUE means a Detach Accept message would not be returned by the network.

5–32

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

MS
DETACH REQUEST

SGSN

DETACH RESPONSE or DETACH REQUEST

DETACH RESPONSE

MS

SGSN

DETACH REQUEST SWITCH OFF = TRUE

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–33

GPRS Overview

ISSUE 1 REVISION 2

Explicit Detach
Explicit Detach is an MS or SGSN detach explicitly requested by one of the elements. Reasons for an Explicit detach could be due to: 1. 2. 3. Insert Subscriber Data from the HLR Unexpected signalling or PTP PDU transfer faults GTP error indication from GGSN

The Control Function (CF) on initiation of an Explicit Detach will attempt to: 1. 2. 3. 4. Message the MS to Detach Delete all active associated PDP contexts in the GGSN if possible Deactivate active associated PDP contexts in the SSGN TF Deactivate associated GMM context in the TF and move to GMM_Deregistered state for MS

On initiation of an Explicit Detach from the MS the SGSN CF uses the detach type to determine the actions required for the detach. The SGSN CF retrieves the GMM context and PDP context information from its own GMM context and PDP context and the TF GMM context + PDP context using the GetMMCtx_PE2 message.

5–34

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

MS
DETACH REQUEST

SGSN CF SGSN TF
GET MMCTx – REQ (TLLI, IMSI) GET MMCTx – CNF TLLI, IMSI, MM CTX INFO

TLLI, IMSI, DETACH TYPE, FORCE TO STBY

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–35

GPRS Overview

ISSUE 1 REVISION 2

Explicit Detach
Once the GMM context and active associated PDP contexts have been recovered by the SGSN CF, the PDP contexts are deactivated by sending a Delete PDP Context Request message to GGSN, identifying the PDP contexts by their TID (IMSI and NSAPI). To delete the PDP contexts at the SGSN TF the message Delete Contx_Req is sent identifying each PDP context by their IMSI, NSAPI, TLLI. On return of response messages from the GGSN and TF that the PDP contexts have been deleted the CF can put its PDP contexts for the MS to INACTIVE. The SGSN CF can now send the Detach Accept message (identified by TLLI) to the MS. To allow this message the GMM context for MS is maintained at the TF to allow this message to be sent. The time T_CF_TXCTL_DELAY01 controls a delay after sending of Detach Accept before the SGSN CF can send Delete MMCntx_Req to the TF to remove the GMM context for the MS and put the MM context at the SGSN CF to idle.

Network Initiated Explicit Detach
A network initiated detach follows the same procedure as an MS initiated detach. The difference is that the Detach Request contains a GMM cause value to indicate why the detach was initiated. The network will proceed to delete all PDP contexts for the MS and will wait until the reception of Detach Accept before deleting the GMM Context for the TF and putting the SGSN CF GMM Context to idle for the MS.

5–36

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

MS

SGSN CF
DETACH REQUEST

SGSN TF

TLLI, IMSI, detach type, force to stby GET MMCtx – REQ GET MMCtx – CNF (TLLI, IMSI) (TLLI, IMSI, MMCTx info)

GGSN
Delete PDP Context Request (TID) Delete PDP Context Response (TID)

SGSN TF
Delete PDP Cntx – Req Delete PDP Cntx – Cnf DETACH ACCEPT START T_CF_TxCTL_DELAY01 (TLLI) (TLLI, NSAPI, IMSI) (TLLI, NSAPI, IMSI RESULT CODE)

EXPIRY T_CF_TxCTL_DELAY01

DELETE MMCTX – Req DELETE MMCTX – Cnf

(TLLI, IMSI) (TLLI, IMSI, RESULT CODE)

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–37

GPRS Overview

ISSUE 1 REVISION 2

Implicit Detach
Implicit Detach occurs when a Lower Layer Failure occurs or GMM Mobile Reachable Timer expires. This occurs in both the MS and SGSN and each separately follow a procedure to become GPRS detached. It is called Implicit Detach as there is no messaging between the MS and the SGSN. The procedure for an Implicit Detach is on the arrival of a Status_Ind message from the Transmission Function (TF) indicating Mobile Reachable Timer expiry or Lower Layer Failure or a Page Ind where the SGSN cannot find a GMM context associated with the IMSI. The SGSN CF then follows the detach procedure without sending a Detach Required message to the MS. Removing GMM and PDP contexts from the TF and GGSN and changing the PDP context to inactive and the GMM Context is idle for the MS.

5–38

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

MS

SGSN CF
TLLI, IMSI

SGSN TF

GET MMCtx – REQ

GET MMCtx – CNF TLLI, IMSI, MMCtx info

GGSN
Delete PDP Context Request (TID) Delete PDP Context Response (TID)

SGSN TF
Delete PDP Ctx – Req Delete PDP Ctx – Cnf (TLLI, NSAPI, IMSI) (TLLI, NSAPI, IMSI RESULT CODE)

DELETE MMCTX – Req

(TLLI, IMSI)

DELETE MMCTX – Cnf

(TLLI, IMSI, RESULT CODE)

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–39

GPRS Overview

ISSUE 1 REVISION 2

Routing Area Update
A Routing area update occurs when a GPRS attached MS enters a new Routing Area (RA) or when the Periodic Routing Area timer has expired. There are two types of Routing area updates; Intra SGSN – where the MS has moved into a Routing Area controlled by the same SGSN, or Inter SGSN – where the MS has entered a new Routing Area controlled by a new SGSN.

Intra SGSN
On receipt of a Routing Area Update, the SGSN CF must determine if there is a GMM context for the MS. If the MS used a Local TLLI then there must be a GMM context for the MS for the Routing Area Update to be an Intra SGSN. If the MS uses a foreign TLLI, the TF can not determine the IMSI for the MS. The CF can convert the foreign TLLI to a Local TLLI and query the TF for the IMSI and MM Context information to check the Ready, Mobile Reachable, MS Radio Access Capability.

Blocking User Data Transfer
As the MS has entered into a new cell location, downlink user data transfer is suspended for the MS until the TF is updated with the new cell location. SGSN CF commands the TL using BLOCKTX_Req to stop dl data transfer.

Modify GMM Context
The CF now processes the Routing Area Update, the new Routing Area ld is desired from the BSSGP layer which contains the Cell Global ID. If GMM context information requires change, such as Ready Timer values, the CF will modify the TF GMM context and then send the Routing Area Accept. The SGSN CF, upon completion of the Routing Area Update function, will unblock the downlink data transfer at the SGSN TF.

5–40

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Overview

MS

SGSN CF
ROUTING AREA UPDATE REQUEST fTLLI, UPDATE TYPE, OLD RAI, MS RADIO ACCESS CAPABILITIES, REQ READY TIMER VALUES

SGSN TF

GET MMCTx – REQ (TLLI) GET MMCTx – CNF TLLI, IMSI, MMCTx INFO BLOCKTx–REQ (TLLI) BLOCKTx–REQ (TLLI) MODIFY MMCtx–REQ TLLI, IMSI, NEW CGI, TIMER VALUES, MS RADIO ACCESS CAPAB, DRX PARAMETERS MODIFY MMCtx–CNF

ROUTING AREA ACCEPT TLLI, IMSI, Force to Stby, update result, RDY timer TLLI, IMSI, RESULT Unblock Tx–REQ Unblock Tx–CNF (TLLI)

(TLLI)

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–41

Session Management

ISSUE 1 REVISION 2

Session Management
Session Management is concerned with the management of virtual connections (PDP contexts) between an MS and an SGSN and a GGSN. Each active PDP context defines a virtual path between the MS and a Destination PTP address. Point to Point subscriptions contain subscriptions to one or more PDP addresses. Each PDP address is described by a PDP context in the MS, SGSN and the GGSN. The Session Activation function activates a PDP context for a subscriber. The PDP context established will be for a specified quality of service (QoS) on a specified NSAPI. The PDP state model for a PDP context has two states; Active – the context holds the routing information necessary to process PDUs for a PDP address between an MS and GGSN. During Active state the PDP context is updated according to changed subscriber location. Active state is permitted only when the Mobility Management state is Standby or Ready. Inactive – The PDP context does not contain the routing information necessary to process a PDU for a particular address . PDP contexts are moved to inactive state during deactivation procedure. The active PDP contexts for an MS are moved to INACTIVE when the MM state changes to IDLE.

5–42

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

PDP State Model

INACTIVE

ACTIVATE PDP CONTEXT

DEACTIVATE PDP CONTEXT or MM STATE changes to idle

ACTIVE

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–43

Session Management

ISSUE 1 REVISION 2

PDP Context Activation MS Initiated
The MS initiates PDP context activation with an Activate PDP context request message. The message contains PDP context parameters required to set up a PDP context between an MS and an SGSN and a GGSN. Information elements include: – – – – NSAPI PDP type PDP Address Access Point Name (leaves blank to request dynamic address) (reference point to external network, via DNS)

The SGSN CF on receipt of a session activation request retrieves the Mobility Management context and the PDP context associated with the subscriber. This information was stored during the GPRS attach procedure. The Control Function now validates the PDP context request to ensure that the requested QOS can be met. If the message is valid then the function continues. The CF first configures the Transmission function before the GGSN for the PDP context, thus allowing the buffering of PDUs from the GGSN to be buffered.

5–44

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

MS

SGSN CF
ACTIVATE PDP CONTEXT REQUEST

CONTEXT FOR MS

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–45

Session Management

ISSUE 1 REVISION 2

PDP Context Activation – Transmission function
The Control Function (CF) sends a PDP context activation message detailing the TLLI, IMSI, NSAPI, QOS and GGSN IP address. This information allows the Transmission function to set up and identify the virtual paths to route PDUs to and from the MS and GGSN. The Transmission Function (TF) will inform the SGSN of the result of configuration for the PDP context.

GGSN Configuration
Once the TF has been configured for the PDP context, enabling the buffering of PDUs to the MS from the GGSN, then the Control function attempts to activate the PDP context in the GGSN. The GGSN that the SGSN CF selects can be determined from three sources: S S S Access Point Name from Subscriber data from HLR Access Point Name from MS in PDP Context Request, used if APN is not specified in Subscriber data. Default GGSN address configured in SGSN CF.

The Create PDP Context Request message is sent to the GGSN with the PDP context information elements required to create a PDP context at the GGSN for the MS, including; SGSN address, TID, PDU negotiated, End User address and protocol configuration options. The GGSN creates a new entry in its PDP context table, storing the information necessary to route PDUs from the SGSN to an external network entity. The GGSN returns a PDP Context Response message indicating whether TCP or UDP will be used to transport PDU between the SGSN and GGSN. Also included are the TID, GGSN address, Cause Value indicating the success of the function.

5–46

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

MS
Activate PDP Context Request

SGSN CF

SGSN TF

CONTEXT FOR MS

Create PDPCtx_REQ

Create PDPCtx_CNF

GGSN
Create PDP Context Request

Create PDP Context Response

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–47

Session Management

ISSUE 1 REVISION 2

Uplink Activation
Once the SGSN Control Function (CF) has received a successful PDP Context Response from the GGSN, the function will activate the Uplink MS to External Network Entity. This ensures that the Transmission Function (TF) can process uplink PDUs from the MS when the Activate PDP Context Accept is sent to the MS. The Control Function sends an Activate Uplink Req message to TF referring to the context by TLLI, IMSI and NSAPI and including the path protocol to be used for transport of PDUs, UDP or TCP. The TF will respond with Activate Uplink_CNF with result of function.

PDP Context Accept
After receipt from the Transmission function of successful activation of the uplink, the control function sends an Activate PDP Context Accept message to the MS. The message returns the PDP parameters for a PDP context. Included in the message are: Transaction Identifier – from MS PDP Context Request Message Negotiated QOS – Returned QOS profile Negotiated LLC SAPI – Returned LLC SAPI Radio Priority – Value for QOS PDP Address – PDP address for MS After sending the PDP Context Accept message the SGSN CF sets the CF PDP Context fields with the PDP context information, NSAPI, Negotiated QOS, State, GGSN address in use, PDP address, QOS Requested.

5–48

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

MS
Activate PDP Context Request

SGSN CF

SGSN TF

CONTEXT FOR MS

Create PDPCtx_REQ

Create PDPCtx_CNF

GGSN
Create PDP Context Request

Create PDP Context Response

SGSN TF
Activate Uplink_REQ Activate Uplink_CNF

Activate PDP Context Accept

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–49

Session Management

ISSUE 1 REVISION 2

Activate Downlink
After sending an Activate PDP Context Accept message to the MS, the SGSN CF will activate the Downlink with Activate Downlink_REQ to the TF with the reorder indicator to indicate if the PDUs should be delivered in sequence to the GGSN. Upon return of the Activate Downlink_CNF with an indicated success the CF will set the PDP context to Active.

5–50

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

MS
Activate PDP Context Request

SGSN CF

SGSN TF

CONTEXT FOR MS

Create PDPCtx_REQ

Create PDPCtx_CNF

GGSN
Create PDP Context Request

Create PDP Context Response

SGSN TF
Activate Uplink_REQ Activate Uplink_CNF Activate PDP Context Accept SET PDP CONTEXT Activate Downlink_REQ Activate Uplink_CNF

ACTIVE PDP CONTEXT

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–51

Session Management

ISSUE 1 REVISION 2

PDP Context Deactivation
The deactivation of a PDP Context for an MS can be initiated by the MS or the Network. An SGSN PDP context deactivation can be carried out without messaging the MS. This may be because the MS cannot be reached or the SGSN Control function needs to clean up a session activation that has failed. An MS initiated Deactivate Context Request comprising TLLI, IMSI, TI and a cause value for the deactivation, such as regular PDP context deactivating or insufficient resources. The SGSN Control function now retrieves the GMM and PDP context for the MS from its data stores. The importance is the retrieval of the GGSN IP address to allow the messaging of the GGSN to deactivate the PDP context. The retrieved GGSN address is then used to send the Delete PDP Context Request containing the TID (IMSI, NSDPI) which uniquely identifies the PDP context at the GGSN. The SGSN CF will delete the TF PDP context regardless of whether the GGSN PDP deactivate was successful or not. The SGSN CF sends the TF a Delete PDPCtx_REQ message, identifying the TLLI, NSDPI of the PDP context to delete. After return of the Delete PDPCtx_CNF from the TF the Control Function will set the PDP context to Inactive and send a Deactivate PDP Context Accept identified by TLLI, IMSI and TI containing the result code.

5–52

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

MS
Deactivate PDP Context Request

SGSN CF
CONTEXT FOR MS

(TLLI, IMSI, TI, CAUSE) Delete PDP Context Request (GGSN IP ADDRESS, TID)

GGSN

Delete PDP Context Response (GGSN IP ADDRESS, TID)

SGSN TF
Delete PDPCtx–Request (TLLI, IMSI, NSAPI) Delete PDPCtx–Response Deactivate PDPContext Accept (TLLI, IMSI, TI, CAUSE) GO INACTIVE (TLLI, IMSI, NSAPI, RESULT CODE)

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–53

Session Management

ISSUE 1 REVISION 2

Paging for GPRS Downlink Transfer
An MS requires paging by the network if a downlink PDU or signalling PDU needs to be transferred to an MS in a Standby State. An MS in Standby cannot receive Point to Point PDUs or signalling PDUs. The Paging Procedure will move the GPRS Mobility Management (GMM) state of the MS to ready so any uplink LLC frame from the MS will put the GMM state at the SGSN to READY and is therefore a valid response to page. The SGSN only knows which routing area an MS was last in when the MMS is in standby state. The Paging function is initiated by the Transmission Function which, on receipt of downlink PDU for an MS in Standby state, notifies the SGSN CF that a PS Page is required with PDGE_IND. Prior to paging, the CF GMM Context information must be retrieved to be able to formulate the Page. The MS location is known by Routing Area, a routing area may be served by multiple BSS. Each BSS serving the routing area where the MS was last known to be located must be messaged to perform a page. A BVCI for signalling is maintained for each BSS. The SGSN CF maintains a mapping of BVCI SIG to RAI (Routing Area Identification). The SGSN CF sends out a paging PS PDU to each BSS serving the routing area of the MSs last known location.

5–54

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

SGSN TF
DOWNLINK PDU

GGSN

SGSN CF
PAGE – IND (TLLI, IMSI, CGI, DRX, MS RADIO ACCESS CAP) PAGE PSPDU (BVCI, IMSI, DRX, RAI, QOS PROFILE, PTMSI) CONTEXT MS

BSS

MS BSS
PAGE PSPDU START TIMER PAGE RESPONSE

LLC FRAME PAGE REPLIED – IND (TLLI, IMSI) STOP TIMER PAGE RESPONSE

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–55

Session Management

ISSUE 1 REVISION 2

Paging
Each Paging PSPDU contains the information elements necessary for the BSS to initiate paging for an MS within a group of cells. The IMSI and DRX parameters allow the BSS to determine the paging population number of the MS. QOS profile indicates the priority of the paging request relative to other Paging Request messages buffered in the BSS. This ensures that higher priority MS will be paged first. The MS is paged using the P_TMSI. When an MS receives a paging message it will carry out a packet access procedure and send an LLC frame. When the SGSN receives the LLC frame the GMM context is moved to ready in the SGSN TF and a Page Response Indication is sent to the Control Function. Receipt of a Page Response Indication from the TF will stop the paging function at the SGSN CF.

Page Response Timer T3313
The SGSN CF starts Page Response Timer T3133 after sending all Page PSPDU to the BSSs. Receipt of the Page Response Indication from the transmission function will stop the timer and the paging function. Expiry of the Page Response timer will result in Page PS PDUs being sent to all BSSs within the routing area. The number of transmissions is controlled by MAX_PAGE_ATTEMPT.

5–56

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

SGSN TF
DOWNLINK PDU

GGSN

SGSN CF
PAGE – IND CONTEXT MS

BSS
PAGE PSPDU

MS BSS
PAGE PSPDU START T3313

LLC FRAME PAGE REPLIED – IND STOP T3313

sgsnDnLinkPagingTimer (T3313) Range 3 – 15 Secs Default 8

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–57

Session Management

ISSUE 1 REVISION 2

Transmission Function
The SGSN Transmission Function (TF) is the functional component of the SGSN which provides. PDP PDU data transfer capabilities between the GGSN and the MS. The TF interfaces to a BSS via a PMC module socket on the Gb link allows the exchange of signalling and user data. The Gb interface uses BSSGP, NS, FR and E1 protocols. The Gn interface uses GPRS Tunnelling protocol which operates over UDP/IP and TCP/IP and defines both signalling and data transfer between GSNs.

5–58

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

GGSN

UPLINK/DOWNLINK USER DATA

SIGNALLING BETWEEN SGSN AND GGSN

Gn
CONTROL INTERFACE

Negotia tion *

Gb
L3MM

LLC + SNDCP Peer to Peer

BSSGP Peer to Peer

BSS

MS

EMOTOROLA LTD. 2000

CONTROL FUNCTION

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–59

Session Management

ISSUE 1 REVISION 2

SNDCP Peer to Peer
The Sub Network Dependant Convergence Protocol (SNDCP) layer is responsible for data compression, protocol control information compression and segmentation of PDUs. To carry out these functions the SNDCP entity at the SGSN must carry out XID negotiation with its peer at the MS. XID negotiations between SNDCP peers are carried by LLC XID commands and responses. An SNDCP XID command is an LLC XID command or a SABM command carrying proposed SNDCP XID parameters and LLC XID parameters. An SNDCP XID response is an LLC XID response or LIA response carrying negotiated SNDCP XID parameters.

SNDCP XID Parameters
Protocol Control Information Compression Compression Algorithm RFC1144 IP RFC1144 Uncompressed TCP/IP RFC1144 Compressed TCP/IP – Data Compression Algorithm V.42 bis – Algorithm type (Range 0–31) 0 1 2 Other values reserved Algorithm Type (Range 0–31) 0 Other values reserved

5–60

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

ORIGINATOR

RECEIVER

SNDCP
LL_XID_REQ

LLC

LLC

SNDCP

XID LL_XID_IND LL_XID_REQ XID

LL_XID_CNF

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–61

Session Management

ISSUE 1 REVISION 2

LLC Peer to Peer
During Attach, PDP context activation and modification, LLC may negotiate external operating XID parameters for a SAPI with its peer LLC. Negotiation takes place by exchanging XID frames or PDUs containing the parameters until a mutually acceptable set of parameters are arrived at. LLC negotiates XID parameters when an XID frame is received from an MS or during an Attach procedure to negotiate XID parameters for the signalling SAPI, or during PDP context activation when SNDCP may issue an XID request for LLC to negotiate SNDCP parameters. LLC may choose to include LLC XID parameters in the same message as the SNDCP parameters.

5–62

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–63

Session Management

ISSUE 1 REVISION 2

GGSN – PDP Context Activation
PDUs from MS to external data networks are transferred via SGSN and GGSN. The GPRS Tunnelling Protocol (GTP) is used between SGSN and GGSN. Tunnels are created between the SGSN and GGSN before PDUs can be transferred. Create PDP Context creates a tunnel between the SGSN and GGSN when the MS wants to send PDUs to an external network. Creating a tunnel between the SGSN and GGSN involves creating a PDP context at the SGSN and GGSN. The SGSN sends a Create PDP Context Request message to the GGSN specified either in the MS Create PDP Request message or the GGSN address specified in the subscriber parameters from the HLR or the default GGSN address specified in the SGSN configuration. The Create PDP Context Request from the SGSN is validated by the GGSN. If the Tunnel ID (TID) is a new PDP context then the GGSN creates a new PDP context with the values specified. The GGSN, once a PDP context has been activated, returns a Create PDP context response with a cause value to indicate the success of the function.

5–64

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Session Management

SGSN
Create PDP Context Request

GGSN

(TLLI, QOS, END USER PDPREQ)

CREATE NEW PDP CONTEXT FOR MS

Create PDP Context Reponse (Response Accepted)

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

5–65

Session Management

ISSUE 1 REVISION 2

5–66

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 6

SGSN configuration parameters

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Introduction to SGSN configuration parameters

Introduction to SGSN configuration parameters
Purpose of this chapter
The purpose of this chapter is to provide reference information for SGSN configuration parameters.

How this chapter is structured
This chapter contains SGSN configuration parameters information, using the following structure to present that information: S S S S S An introduction to the chapter and the chapter structure. Details of the MIB structure identifying the available SGSN objects. Parameter tables detailing the parameters available for each SGSN configuration object. Reference diagrams, and explanations, of the purpose of the parameters. Data sheets containing information on the individual statistics identified in the attributes tables. NOTE This information may be structured differently for training purposes

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–1

Introduction to SGSN configuration parameters

ISSUE 1 REVISION 2

SGSN OID structure
Figure 6-1 illustrates the SGSN OID structure, with the emphasis on the configuration management branch of the structure.
mot-gprs-sgsn (1) System (2) Tx (1) SM (2) SNDCP (3) LLC (4) BSSGP (5) NS (1) Params (2) Tables (1) E1 Link (3) FrameRelay (5) NsvcFrPvc (8) Nse (12) (3) Sig (1) GTP (2) GMM (8) RaiNsei (4) Meter (5) Perf (6) SW (7) HA (8) Op (9) OAMP (1) GbLoadShareTransact NseNsvc

Figure 6-1 SGSN OID structure

6–2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Introduction to SGSN configuration parameters

Parameter Tables
Details of the parameters available for each configuration management object can be found in the following tables: Table 6-1 Table 6-2 Table 6-3 Table 6-4 Table 6-5 Table 6-6 Table 6-7 Table 6-8 Table 6-9 Table 6-10 Table 6-11 Table 6-12 Table 6-13 Sig – GTP Sig – GMM Sig – Plane Information System Tx – SM Tx – SNDCP TX – LLC TX – BSSGP TX – NS Params Tx – NS Tables FrameRelay NSVC BVC Cell-BVC

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–3

Introduction to SGSN configuration parameters

ISSUE 1 REVISION 2

Reference diagrams
Reference diagrams provide an explanation of the role or function of the configuration parameters. Several parameters may be displayed on a single diagram. The following reference diagrams are available

System
The following general system parameter diagrams are available: Figure 6-2 Figure 6-3 System addresses Configuration file handling

Sig – GTP
The following signalling GTP parameter diagrams are available: Figure 6-4 GTP Request Attempts

Sig – GMM
The following GPRS Mobility Management parameter diagrams are available: Figure 6-5 Figure 6-6 Figure 6-7 Mobility Management timers Downlink paging timer Maximum paging attempts

Tx – BSSGP
The following BSSGP parameter diagrams are available: Figure 6-22 BVC block timer Figure 6-23 BVC reset timer Figure 6-24 BVC block retries Figure 6-25 BVC unblock retries Figure 6-26 BVC set retries

Tx – NS Params
The following NS parameter diagrams are available: Figure 6-8 Figure 6-9 TNS block timer NSVC reset timer

Figure 6-10 NSVC Test Figure 6-11 NSVC block retries Figure 6-12 NSVC unblock retries Figure 6-13 NSVC alive retries Figure 6-14 NSVC resetting
EMOTOROLA LTD. 2000

6–4

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

Introduction to SGSN configuration parameters

Tx – NS Tables
The following NS parameter diagrams are available: Figure 6-15 Gb channel Id Figure 6-16 SGSN WAN terminations Figure 6-17 Frame Relay Status Enquiry Figure 6-18 Gb interface error monitoring Figure 6-19 NSVCI mapping Figure 6-20 NSVC Link Id Figure 6-21 Committed Information Rate

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–5

Configuration parameter tables

ISSUE 1 REVISION 2

Configuration parameter tables
Introduction to configuration parameter tables
This section of the manual details the parameters available for each SGSN configuration object. The parameters available for each object are identified in individual object tables.

System parameters
The following table lists the SGSN general system parameters: Table 6-1 SGSN general system parameters OID number 1 2 3 4 5 6 7 8 9 10 11 sgsnIpAddress sgsnOMC–IpAddress sgsnDefaultAPN sgsnVersion sgsnNetwork OperatorId–MCC sgsnNetworkOperatorId-MNC sgsnDiagConfigFileName sgsnDumpConfigFileName sgsnLoadConfigFileName sgsnLoggingState sgsnTracingState parameter

Session Management parameters
The following table lists the SGSN transmit function Session Management parameters: Table 6-2 SGSN Tx Session Management parameters OID number 1 parameter sgsnMaxActivePDP-Context–PerIMSI

6–6

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Configuration parameter tables

SNDCP parameters
The following table lists the SGSN transmit function SNDCP parameters: Table 6-3 SGSN Tx SNDCP parameters OID number 1 2 3 4 5 6 7 parameter sgsnSNDCP–VersionNum sgsnSNDCP–DataCompressionAlgorithm sgsnNDCP–HeaderCompressionAlgorithm sgsnNDCP–CompressionDirection sgsnNDCP–MaxCompressionCodewords sgsnNDCP–MaxCodewordLength sgsnNDCP–CompressorShared

LLC parameters
The following table lists the SGSN transmit function LLC parameters: Table 6-4 SGSN Tx LLC parameters OID number 1 sgsnLLC-VersionNum parameter

BSSGP parameters
The following table lists the SGSN transmit function BSSGP parameters: Table 6-5 SGSN Tx BSSGP parameters OID number 1 2 3 4 5 sgsnBSSGP-T1 sgsnBSSGP-T2 sgsnBSSGP-Bvc-BlockRetries sgsnBSSGP-Bvc-UnblockRetries sgsnBSSGP-Bvc-ResetRetries parameter

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–7

Configuration parameter tables

ISSUE 1 REVISION 2

NS parameters
The following table lists the SGSN transmit function NS parameters: Table 6-6 SGSN Tx NS parameters OID number 1 2 3 4 5 6 7 8 sgsnNS-TnsBlockTimer sgsnNS-TnsResetTimer sgsnNS-TnsTestInterval sgsnNS-TnsAliveTimer sgsnNS-BlockRetries sgsnNS-UnblockRetries sgsnNS-AliveRetries sgsnNS-ResetPeriod parameter

NS Frame Relay table parameters
The following table lists the SGSN transmit function NS Frame Relay table parameters: Table 6-7 SGSN Tx NS Frame Relay table parameters OID number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 sgsnGb–FRRowStatus sgsnGb–FRLinkId sgsnGb–FRBearerChannelId sgsnGb–FRDTE-DCE sgsnGb–FRLMI-DLCI sgsnGb–FRLMI-Std sgsnGb–FRLMI-STDConform sgsnGb–FRT391 sgsnGb–FRT392 sgsnGb–FRN391 sgsnGb–FRN392 sgsnGb–FRN393 sgsnGb–FRTimeSlot sgsnGb–FR–EndTimeslot sgsnGb-FR-MaxFrame sgsnGb-FR-BitMask sgsnGb-FR-FramingFormat sgsnGb-FR-Encoding
EMOTOROLA LTD. 2000

parameter

6–8

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

Configuration parameter tables

OID number 19 20 sganGb-FR-Clocking

parameter sgsnGb–FR–LineBuildOut

NS NsvcFrPvc table parameters
The following table lists the SGSN transmit function NS NsvcFrPvc table parameters: Table 6-8 SGSN Tx NS NSVCFrPvc table parameters OID number 1 2 3 4 5 6 7 8 9 10 sgsnGb–NSVC-NSVCI sgsnGb–NSVC-DLCI sgsnGb–NSVC-LinkId sgsnGb–NSVC-BearerChannelId sgsnGb–NSVC-Frpvc-CIR sgsnGb–NSVC-Frpvc-Bc sgsnGb–NSVC-Frpvc-Be sgsnGb–NSVC-Frpvc-StepCount sgsnGb–NSVC-Frpvc-FlowStyle parameter sgsnGb–NSVC-RowStatus

BVC table parameters
The following table lists the SGSN transmit function BVC table parameters: Table 6-9 SGSN Tx NS table parameters OID number 1 2 3 4 5 sgsnGb–BVC–BVCI sgsnGb–BVC–BCVI–Type sgsnGb–BVC–NSVCI sgsnGb-BVC–SigBVCI parameter sgsnGb–BVC–NseNsvcRowStatus

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–9

Configuration parameter tables

ISSUE 1 REVISION 2

Cell-PVC parameters
The following table lists the SGSN transmit function Cell-BVC table parameters: Table 6-10 SGSN Cell-BVC parameters OID number 1 2 3 4 5 6 sgsnGb-Cell-BVC-MCC sgsnGb-Cell-BVC-MNC sgsnGb-Cell-BVC-LAC sgsnGb-Cell-BVC-CI sgsnGb-Cell-BVC-PTP-BVCI parameter sgsnGb-Cell-BVC-Rowstatus

Signalling GTP parameters
The following table lists the SGSN signalling GTP parameters: Table 6-11 SGSN signalling GTP parameters OID number 1 parameter sgsnGTP-N3RequestAttempts

Signalling GPRS Mobility Management parameters
The following table lists the SGSN signalling GPRS Mobility Management parameters: Table 6-12 SGSN signalling GPRS Mobility Management parameters OID number 1 2 3 4 5 sgsnStandbyTimer sgsnReadyTimer sgsnDnLinkPagingT imer sgsnMaxPagingAttempts sgsnPeriodicRAU-Timer parameter

6–10

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Configuration parameter tables

Plane Control parameters
The following table lists the SGSN signalling plane control table parameters: Table 6-13 Plane Control parameters OID number 1 2 3 4 5 6 7 sgsnSigPlaneInfo-MCC sgsnSigPlaneInfo-MNC sgsnSigPlaneInfo-LAC sgsnSigPlaneInfo-CI sgsnSigPlaneInfo-RAC sgsnSigPlaneInfo-BVC parameter sgsnSigPlaneInfoRowStatus

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–11

System parameter diagrams

ISSUE 1 REVISION 2

System parameter diagrams
System addresses
The following diagram identifies the relationship of the system addresses of the SGSN configuration parameters. The sgsnIpAddress parameter specifies the logical IP address of the OAMP Agent within an SGSN. The sgsnOmcIpAddress parameter specifies the IP address of the OMC-G for routing SNMP commands.

OMC-G

IP Address = sgsnOmcIpAddress

Commhub IP Address = sgsnIpAddress

SGSN

OAMP Agent

Figure 6-2 System addresses

6–12

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

System parameter diagrams

Configuration file handling
The following diagram details how configuration files are handled within the GSN. System parameters (sgsnDiagConfigFileName and sgsnDumpConfigFileName ) create a file name, or specify one that already exists, for storage of configuration information for diagnostic or archive (dump) purposes. The sgsnLoadConfigFileName parameter creates a file name, or specifies one that already exists, for use when loading a configuration file.

OMC-G

SNMP

Interface

GSN OAMP Agent

Configuration Data Store

GSN Sub Agent

Configuration Data Store

SNMP

SGSN Application

Figure 6-3 Configuration file handling

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–13

sgsnIpAddress

ISSUE 1 REVISION 2

sgsnIpAddress
Description
This parameter identifies the IP address of a specific SGSN in a network. Each SGSN has multiple IP addresses internally. The address defined here is the one used by the OMC-G, that is, this is where the SGSN agent is running. This parameter is initialized from /etc/hosts file using alias host name oamphost

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory Integer IP Address x.x.x.x x = 0 to 255 0.0.0.0

Format
dot format, x.x.x.x where: 0 <= x <= 255

Example

References

6–14

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnOMC-IpAddress

sgsnOMC-IpAddress
Description
This parameter identifies the IP address of the managing OMC-G. This parameter is initialized from /etc/hosts file using alias host name omcghost

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory Integer 0 to 255 0.0.0.0

Format
dot format, x.x.x.x where: 0 <= x <= 255

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–15

sgsnDefaultAPN

ISSUE 1 REVISION 2

sgsnDefaultAPN
Description
This parameter identifies the default APN that the SGSN uses, according to the APN selection algorithm specified in GSM 03.60 v6.3.1. The APN requirement is defined in GSM 03.03. This parameter contains only the Network Identifier, it does not contain the APN Operator Identifier.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory 0 to 63

Format

Example

References
GSM 03.60 v6.3.1. GSM 03.03

6–16

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnVersion

sgsnVersion
Description
This parameter identifies the software version that runs on the currently identified SGSN.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory hexidecimal 00 to ff (using lower case letters) GSN00.00.00.00

Format
GSN<system>.<major>.<minor>.<patch> where: <system> <major> <minor> <patch> : : : : GPRS system release number GSN major release number GSN minor release number GSN patch level

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–17

sgsnNetworkOperatorId-MCC

ISSUE 1 REVISION 2

sgsnNetworkOperatorId-MCC
Description
This parameter is the Network Operator Identification - Mobile Country Code.

Attributes
Value type Valid range Default value
decimal 0 to 9 (in ASCII format) 000

Dependencies None Access Status
read - write mandatory

Format
3 decimal digits in ASCII format, with 0 padded at the front.

Example

References
CCITT Rec E.212 Annex A

6–18

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNetworkOperatorId-MNC

sgsnNetworkOperatorId-MNC
Description
This parameter is the Network Operator Identification - Mobile Network Code.

Attributes
Value type Valid range Default value
decimal 0 to 9 (in ASCII format) 00

Dependencies None Access Status
read - write mandatory

Format
2 decimal digits in ASCII format, with 0 padded at the front.

Example

References
GSM 03.03 v6.1.0

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–19

sgsnDiagConfigFileName

ISSUE 1 REVISION 2

sgsnDiagConfigFileName
Description
This parameter is the full path name of a configuration file to be sanity checked. When this variable is SET the GSN checks whether the file exists or not. If not, the GSN creates the file.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory 0 to 256

Format

Example

References

6–20

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnDumpConfigFileName

sgsnDumpConfigFileName
Description
This parameter is the full path name of a configuration file used for a configuration dump. The SGSN creates the file if it does not already exist.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory 0 to 256

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–21

sgsnLoadConfigFileName

ISSUE 1 REVISION 2

sgsnLoadConfigFileName
Description
This parameter is the full path name of a configuration file used for SGSN configuration synchronization, or for configuration through a configuration file.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory 0 to 256

Format

Example

References

6–22

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnLoggingState

sgsnLoggingState
Description
This parameter is used to specify the current level of SGSN logging. Disable(0) EnableLevel1(1) S S S S : Default, only the traps are logged. : Enable, INFO level.

Provide supplementary information to an alarm. Security alert (for example: unauthorised access). Startup/shutdown logging. Failure of external components (for example: BSS and GGSN - from the perspective of the SGSN). : Enable, Medium Verbose level.

EnableLevel2(2) S S S S S

GPRS signalling failure (for example: Attach Reject, Activate Reject, Deactivate Reject). MS protocol failure (LLC, SNDCP, MM, SM). : Enable, Verbose level.

EnableLevel3(3)

All signalling messages (L3MM. GAP, GTP), except the ones logged at the Medium Verbose level. LLC reset. : Enable, DEBUG level.

EnableLevel4(4)

Detailed logging of internal events, enabling support staff to perform debugging (for example: sequence of function calls, value of variable etc). Logs generated at this level are not expected to be fully understood by the operators.

Enabling the logging at a higher level automatically enables the logging at all lower levels.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory Integer 0 to 4 0

Format
Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–23

sgsnTracingState

ISSUE 1 REVISION 2

sgsnTracingState
Description
This parameter is used to enable/disable SGSN tracing. (For R0 either all protocol traces are enabled or all disabled). Disable(0) Enable(1)

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory Integer 0 or 1 0

Format

Example

References

6–24

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Signalling GTP parameter diagrams

Signalling GTP parameter diagrams
GTP Request Attempts
The following diagram details the PDP Context Request message, which is repeated if no response is received during period T3 (mandatory timer). The sgsnGtpN3RequestAttempts parameter is used to set the number of times (N3 counter) that the request is repeated, each request lasting T3.

SGSN
Create PDP Context Request

GGSN

T3

Create PDP Context Request

Create PDP Context Request

repeated N3 times

sgsnGTPN3RequestAttempts Figure 6-4 GTP Request Attempts

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–25

sgsnGTP-N3RequestAttempts

ISSUE 1 REVISION 2

sgsnGTP-N3RequestAttempts
Description
The counter N3-REQUESTS holds the maximum number of attempts made by the SGSN to send a signalling request message.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 5 3

Format

Example

References
GSM 09.60 v5.0.0

6–26

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Mobility Management parameter diagrams

GPRS Mobility Management parameter diagrams
Mobility Management timers
The following diagram details the Mobility Management states of the mobile subscriber (MS). The Ready timer determines how long the MS remains in the Ready state. The MS is returned to the Idle state if a Detach command is received during the timer period. If the timer expires (reaches the preset value) the MS is placed into the Standby state. The timer is over-ridden, and the MS placed into the Standy mode, if a Force to Standby command or Abnormal condition occurs. The Standby timer determines how long the MS remains in the Standby state. The MS is returned to the Ready state if a PDU is received during the timer period. If the timer expires the MS is returned to the Idle state.

IDLE

GPRS Attach

GPRS Detach

Standby Timer Expiry

READY

sgsnReadyTimer –1 = Deactivated 0 = Force to Standby Valid Range: 2 – 1800

Ready Timer Expiry or Force to Standby or Abnormal Condition

PDU Reception

STANDBY

sgsnStanbyTimer –1 = Deactivated Valid Range: 6 – 186 (in multiples of 6)

Figure 6-5 Mobility Management timers
EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–27

GPRS Mobility Management parameter diagrams

ISSUE 1 REVISION 2

Downlink paging timer
The following diagram details PDU paging messages used to determine the location of the recipient Mobile Subscriber (MS) in the routing area. The sgsnDnLinkPagingT imer parameter determines the value of the downlink paging timer, T3313. The timer governs the waiting period between a PSPDU paging message being sent to all BSSs and the expected Page Replied Indication response. GGSN SGSN TF
Downlink PDU

BSS#1 SGSN CF
Page–Ind

Page PSPDU

Start T3313

BSS#2

MS

LLC FRAME Page Replied –IND

Stop T3313

sgsnDnLinkPagingT imer
Range 3 – 15 Secs Default 8

Figure 6-6 Downlink paging timer

6–28

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GPRS Mobility Management parameter diagrams

Maximum paging attempts
The following diagram details PDU paging messages. The PSPDU paging message is sent to all BSS in a routing area and is repeated if a Page Replied Indicator response is not received from the BSS before the expiry of T3313. The sgsnMaxPagingAttempts parameter determines the number of times the paging attempt is repeated. SGSN TF BSS#1 SGSN CF

Page–Ind

Page PSPDU

Start T3313

BSS#2

BSS#1

Page PSPDU

BSS#2 for MaxPagingAttempts

sgsnMaxPagingAttempts
Range 1 – 5 Default 2

Figure 6-7 Maximum paging attempts

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–29

Network Service parameter diagrams

ISSUE 1 REVISION 2

Network Service parameter diagrams
NSVC block timer
The following diagram details NS block and unblock PDUs. The sgsnNsTnsBlockTimer parameter determines the period of the TNS block timer, which controls the NSVC blocking and unblocking procedures. PCU
NS Block or Unblock PDU

SGSN TNS Block

NS Block or Unblock Ack PDU

sgsnNsTnsBlockTimer
Range 1 – 30 Secs Default 3

Figure 6-8 NSVC block timer

6–30

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Network Service parameter diagrams

NSVC reset timer
The following diagram details NS reset PDUs. The sgsnNsTnsResetTimer parameter determines the period of the NSVC reset timer. The timer is started when the reset PDU is sent and stopped on receipt of the reset acknowledgement. The NSVC Reset forces peer entities to a known (blocked) state. Once both entities are at the same state the NSVC unblock procedures can be carried out to bring the NSVC into service. PCU
NS Reset PDU

SGSN TNS Reset

NS Reset Ack PDU

sgsnNsTnsResetTimer
Range 1 – 60 Secs Default 3

Figure 6-9 NSVC reset timer

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–31

Network Service parameter diagrams

ISSUE 1 REVISION 2

NSVC Test
The following diagram details the Network Service Test procedure. The sgsnNsTnsAliveTimer parameter controls the NSVC test procedure. The timer is started when an NS alive PDU is sent to a peer entity, and is stopped on receipt of an NS Alive Acknowledge PDU. The sgsnNsTnsTestInterval parameter governs the time between NSVC tests. The test interval is started on receipt of the NS alive Acknowledge PDU, and when it expires the next NSVC test is started. PCU SGSN TNS TestInterval

NS Alive PDU

TNS Alive sgsnNsTnsAliveTimer
Range 1 – 60 Secs NS Alive Ack PDU Default 3

TNS TestInterval sgsnNsTnsTestInterval
Range 1 – 60 Secs Default 10

Figure 6-10 NSVC Test

6–32

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Network Service parameter diagrams

NSVC block retries
The following diagram details the NSVC Block PDU, which is repeated if no response is received before the timer expires. The sgsnNsTnsBlockRetries parameter is used to set the number of times that the NSVC Block PDU is sent. PCU
NS Block PDU

SGSN

TNS Block

NS Block PDU

TNS Block

sgsnNsTnsBlockRetries
Range 1 – 30 Default 3

Figure 6-11 NSVC block retries

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–33

Network Service parameter diagrams

ISSUE 1 REVISION 2

NSVC unblock retries
The following diagram details the NSVC Unblock PDU, which is repeated if no response is received before the timer expires. The sgsnNsTnsUnblockRetries parameter is used to set the number of times that the NSVC Unblock PDU is sent. PCU
NS Unblock PDU

SGSN

TNS Unblock

NS Unblock PDU

TNS Unblock

sgsnNsTnsUnblockRetries
Range 1 – 30 Default 3

Figure 6-12 NSVC unblock retries

6–34

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Network Service parameter diagrams

NSVC alive retries
The following diagram details the NSVC Alive PDU which attempts to query the status of an NSVC. The query is repeated if no response is received before the timer expires. The sgsnNsTnsAliveRetries parameter is used to set the number of times that the NSVC Alive PDU is sent. PCU
NS Alive PDU

SGSN

TNS Alive

NS Alive PDU

TNS Alive

sgsnNsTnsAliveRetries
Range 1 – 30 Default 3

Figure 6-13 NSVC alive retries

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–35

Network Service parameter diagrams

ISSUE 1 REVISION 2

NSVC resetting
The following diagram details the NSVC resetting procedure. The sgsnNsTnsResetPeriod parameter sets the period for the NSVC reset procedure. During this period NS Reset PDUs are sent to the peer entity, governed by the Reset Timer. Rest PDUs are sent until a rest acknowledgement is received or the Reset Period expires. For this procedure to function the Rest Period must be set to a greater value than that of the Reset Timer. PCU
NS Reset PDU

SGSN TnsResetTimer

NS Reset PDU

ResetPeriod TnsResetTimer

sgsnNsTnsResetPeriod
Range 1 – 1000 Secs Default 3

ResetPeriod > TnsResetTimer

Figure 6-14 NSVC resetting

6–36

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNS-TnsBlockTimer

sgsnNS-TnsBlockTimer
Description
This parameter is the timer, in seconds, that guards the NS blocking and unblocking procedures. The blocking or unblocking message is attempted every sgsnNsTnsBlockTimer seconds, until the peer NS acknowledges or the number of retries (sgsnNsBlockRetries or sgsnNsUnblockRetries ) for the procedure is completed.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 30 3

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–37

sgsnNS-TnsResetTimer

ISSUE 1 REVISION 2

sgsnNS-TnsResetTimer
Description
This parameter is the timer, in seconds, that guards the NS reset procedure. The reset is sent every sgsnNS–TnsResetTimer seconds, until the peer NS acknowledges or the sgsnNsResetPeriod expires. It must be less than sgsnNsResetPeriod .

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 60 3

Format

Example

References

6–38

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNS-TnsTestInterval

sgsnNS-TnsTestInterval
Description
This parameter indicates the periodicity of the NS-VC test procedure, in seconds. It must be greater than sgsnNS-TnsAliveTimer.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 60 10

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–39

sgsnNS-TnsAliveTimer

ISSUE 1 REVISION 2

sgsnNS-TnsAliveTimer
Description
This parameter is the timer, in seconds, that guards the NS-VC test procedure. The NsAlive PDU is sent to the peer every sgsnNsTnsAliveTimer seconds, until the peer acknowledges or the number of retries (sgsnNsAliveRetries) is completed. It must be less than the sgsnNsTnsTestInterval.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 30 3

Format

Example

References

6–40

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNS-BlockRetries

sgsnNS-BlockRetries
Description
This parameter is the number of attempts to retry an NS-BLOCK.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 30 3

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–41

sgsnNsUnblockRetries

ISSUE 1 REVISION 2

sgsnNsUnblockRetries
Description
This parameter is the number of attempts to retry an NS-UNBLOCK.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 30 3

Format

Example

References

6–42

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNS-AliveRetries

sgsnNS-AliveRetries
Description
This parameter is the number of attempts to retry the NS-VC test procedure.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 30 3

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–43

sgsnNS-ResetPeriod

ISSUE 1 REVISION 2

sgsnNS-ResetPeriod
Description
This parameter is the period, in seconds, during which reset is attempted. It must be greater than sgsnNsTnsResetTimer.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 1000 30

Format

Example

References

6–44

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnStandbyTimer

sgsnStandbyTimer
Description
T3315: The value of the Standby Timer in minutes. As the timer will be encoded in decihours (1/10 of an hour) the unit of increment should be 6 minutes. If the value X of the timer is not set to a multiple of 6, it will be truncated. The truncated value Y is the nearest multiple of 6, with: X–6 < Y < X If truncation occurs, while value Y will be used by the GSN applications, value X is still returned in response to a GET request on this variable. The truncated value of sgsnStandbyTimer should always be greater than the truncated value of sgsnPeriodicRAU-Timer by a multiple of 6.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory Integer –1 : indicates deactivated 6 - 186 : actual timer value 60

Format

Example

References
GSM 04.08 v5.6.2, CR A265

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–45

sgsnReadyTimer

ISSUE 1 REVISION 2

sgsnReadyTimer
Description
T3314: The value of the Ready Timer in seconds. The timer will be encoded in seconds or minutes with certain units of increment, depending on the value to be encoded. From 2 to 60 seconds, the encoding will be in seconds with the unit of increment 2 seconds. If the value X of the timer, in the range 2 - 60 seconds, is not set to a multiple of 2 it will be truncated. The truncated value Y is the nearest multiple of 2, with: X–2 < Y < X From 61 to 1800 seconds, the encoding will be in minutes with the unit of increment 60 seconds (1 minute). If the value X of the timer, in the range 61 - 1800 seconds, is not set to a multiple of 60 it will be truncated. The truncated value Y is the nearest multiple of 60, with: X–60 < Y < X If truncation occurs, while value Y will be used by the GSN applications, value X is still returned in response to a GET request on this variable.

Attributes
Value type Valid range
Integer –1 : indicates deactivated 0 : indicates Force to Standby 2 - 1800: actual timer value 32

Default value Dependencies Access Status

read - write mandatory

Format

Example

References
GSM 04.08 v5.6.2, CR A265 Rev 5

6–46

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnDnLinkPagingTimer

sgsnDnLinkPagingTimer
Description
T3313: The value of the Downlink transfer paging Timer in seconds.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory Integer 3 to 15 8

Format

Example

References
GSM 04.08 v5.6.2, CR A265 Rev 5

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–47

sgsnMaxPagingAttempts

ISSUE 1 REVISION 2

sgsnMaxPagingAttempts
Description
This parameter identifies the maximum number of attempts to page an MS.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory Integer 1 to 5 2

Format

Example

References
GSM introduced.

6–48

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnPeriodicRAU-Timer

sgsnPeriodicRAU-Timer
Description
T3312: The value of the Periodic RAU (Routing Area Update) Timer in minutes. As the timer will be encode in decihours (1/10 of an hour) the unit of increment should be 6 minutes. If the value X of the timer is not set to a multiple of 6, it will be truncated. The truncated value Y is the nearest multiple of 6, with: X–6 < Y < X If truncation occurs, while value Y will be used by the GSN applications, value X is still returned in response to a GET request on this variable. The truncated value of sgsnPeriodicRAU-Timer should always be smaller than the truncated value of sgsnStandbyTimer by a multiple of 6.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory Integer –1 : indicates deactivated 6 - 180 : actual timer value 54

Format

Example

References
GSM 04.08 v5.6.2, CR A562

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–49

NS Tables parameter diagrams

ISSUE 1 REVISION 2

NS Tables parameter diagrams
Gb channel Id
The following diagram details an E1 bearer channel. The Id of this channel can be specified by use of the sgsnFrBearerChannelId parameter.

DLCI = 45 Bearer Channel DLCI = 177

DLCI = 45

DLCI = 177

sgsnFrBearerChannelId
Range: 0 – 30 Default 0

Figure 6-15 Gb channel Id

6–50

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

NS Tables parameter diagrams

SGSN WAN terminations
The following diagram provides SGSN WAN termination details. The SGSN has to function as Data Terminal Equipment (DTE) or Data Communications Equipment (DCE), depending on the type of WAN interface. The SGSN is set to function as DTE or DCE by use of the sgsnFrDteDce parameter. BSS DTE Gb Direct Connection DCE SGSN

BSS

DTE Gb

Frame Relay Connection

DTE Gb

SGSN

sgsnFrDteDce
Range: 0 = DCE 1 = DTE

Figure 6-16 SGSN WAN terminations

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–51

NS Tables parameter diagrams

ISSUE 1 REVISION 2

Frame Relay Status Enquiry
The following diagram details the Frame Relay Status Enquiry procedure. The sgsnFrT391 parameter sets the period between Status Enquiry messages being sent from the user to the network. Timer T392 is started when the Status response is sent from the network to the user, and the next Status Enquiry should arrive before the timer expires. Parameter sgsnFrT392 sets the value of the timer. The complete status enquiry procedure is governed by counter N391, which determines the number of Status Enquiries that have to be sent before a Full Status Enquiry is sent. Parameter sgsnFrN391 sets the value of the counter. Network
Status Enquiry

User

T391 T392
Status

N391

Status Enquiry

Status

Full Status Enquiry

Full Status

sgsnFrN391
Range: 1 – 255 Default 6

sgsnFrT392
Range: 6 – 30 Secs Default 15

sgsnFrT391
Range: 5 – 29 Secs Default 10

sgsnFrT392 > sgsnFrT391 Figure 6-17 Frame Relay Status Enquiry

6–52

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

NS Tables parameter diagrams

Gb Interface error monitoring
The following diagram details the Gb Interface error monitoring, used in conjunction with the Status response timer T392. Counter N393 monitors the number of error events, and is incremented each time the timer expires or an invalid Status Enquiry is received. Counter N392 monitors the number of contiguous error events. Parameter sgsnFrN393 sets the maximum number of error events to be counted, and parameter sgsnFrN392 sets the number of contiguous error events to be counted. Network

No Status Enquiry

N393

T392

N392

sgsnFrN392
Range 1 – 10 Default 3

sgsnFrN393
Range 1 – 10 Default 4

sgsnFrN392 <= sgsnFrN393 Figure 6-18 Gb interface error monitoring

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–53

NS Tables parameter diagrams

ISSUE 1 REVISION 2

NSVCI mapping
The following diagram details the mapping between protocol layers. In a Point to Point connection the NSVCI and DLCI have end to end significance. In an intermediate Frame Relay network only the NSVCI has end to end significance.

BSSGP

BSSGP sgsnNsvcFrPvcNSVCI

NS Frame Relay

NSVCI

NS Frame Relay

Range: 1 – 65535

DLCI

sgsnNsvcFrPvcDLCI
Range: 16 – 991 Default 16

E1

E1

BSSGP

BSSGP

NS Frame Relay

NSVCI

NS Frame Relay

DLCI

DLCI

E1

Chan ID

Chan ID

E1

Figure 6-19 NSVCI mapping

6–54

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

NS Tables parameter diagrams

NSVC Link Id
The following diagram details a NSVC Link. Parameter sgsnNsvcFrPvcBearerChannelId specifies the identity of a bearer channel within the link, and parameter sgsnNsvcFrPvcPhyLinkId specifies the identity of the bearer link.

DLCI = 45 Bearer Channel 1 DLCI = 55

Bearer Link
DLCI = 177 Bearer Channel 2 DLCI = 23

sgsnNsvcFrPvcBearerChannelId
Range: 0 – 30 Default 0

sgsnNsvcFrPvcPhyLinkId
Range: 0 – 3 Default 0

Figure 6-20 NSVC Link Id

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–55

NS Tables parameter diagrams

ISSUE 1 REVISION 2

Committed Information Rate
The following diagram provides details of the Committed Information Rate (CIR). The CIR is effectively the amount of information that can be transferred over a given period, and is set by parameter sgsnNsvcFrPvcCIR. Information transferred at the CIR rate is guaranteed to be delivered. Due to the burst nature of information transfer, the required transfer may exceed the guaranteed limit. An agreed excess, Bc, may be permitted but the information may be eligible for discard. The size of the excess is set using parameter sgsnNsvcFrPvcBc. It is possible that the excess may also be insufficient. An additional amount, Be, may be agreed but the information is likely to be discarded on entry. The size of the additional amount is set using parameter sgsnNsvcFrPvcBe. Bits

Bc + Be

Discard On Entry

4 Bc 3 2 CIR 1 Guaranteed Discard Eligible

T sgsnNsvcFrPvcBc
Range: 1 – 2048000 Default 1

sgsnNsvcFrPvcCIR
Range 1 – 2048000 Default 1

sgsnNsvcFrPvcBe
Range: 1 – 2048000 Default 0

Figure 6-21 Committed Information Rate

6–56

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-FR-Table

sgsnGb-FR-Table
Description
This table lists the Frame Relay Bearer Channels for this SGSN. Row Creation: Row Deletion: For the successful creation of a row in this table, the underlying physical E1/T1 links must have already been in service. If the Bearer Channel defined by the row is not being referenced by any rows in the sgsnGb-Nsvc-Table, it is allowed to be deleted. Any other attempt at deleting it should be rejected. Currently, the software does not have provision to update individual entry values for a row after it has been created. Updates can only be achieved by deleting the existing row and then inserting a new row containing the new values, through separate management requests.

Row Update

Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–57

sgsnGb-FR-Entry

ISSUE 1 REVISION 2

sgsnGb-FR-Entry
Description
This parameter defines an entry for a single Frame Relay Bearer Channel.

Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory

Format
sgsnFrameRelayEntry ::= SEQUENCE{ sgsnGb-FRRowStatus sgsnGb-FRLinkId sgsnGb-FRBearerChannelId sgsnGb-FRDTE-Dce sgsnGb-FRLMI-DLCI sgsnGb-FRLMI-STD sgsnGb-FRLMI-STD-Conform sgsnGb-FRT391 sgsnGb-FRT392 sgsnGb-FRN391 sgsnGb-FRN392 sgsnGb-FRN393 sgsnGb-FRStartTimeSlot sgsnGb-FR-EndTimeslot sgsnGb-FR-MaxFrame sgsnGb-FR-BitMask sgsnGb-FR-FramingFormat sgsnGb-FR-Encoding sgsnGb-FR-LineBuildout sgsnGb-FR-Clocking }
EMOTOROLA LTD. 2000

GSN-RowStatus, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER INTEGER OCTET STRING INTEGER INTEGER INTEGER INTEGER

6–58

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

sgsnGb-FR-Entry

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–59

sgsnGb-FR-RowStatus

ISSUE 1 REVISION 2

sgsnGb-FR-RowStatus
Description
This parameter indicates the status of a table row.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory undefined

Format

Example

References

6–60

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb–FR-LinkId

sgsnGb–FR-LinkId
Description
This parameter is the identifier of the Frame Relay bearer E1 link, unique within an SGSN. It is used by the SGSN to identify the physical E1/T1 link for configuring the Frame Relay WAN interfaces.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 3

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–61

sgsnGb-FR-BearerChannelId

ISSUE 1 REVISION 2

sgsnGb-FR-BearerChannelId
Description
This parameter is the identifier of the Bearer Channel, unique within the SGSN for R0, unique within an E1/T1 link in R1. It is used by the SGSN to configure the Frame Relay WAN interfaces.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 30

Format

Example

References

6–62

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-FR-Dte-Dce

sgsnGb-FR-Dte-Dce
Description
This parameter identifies the type of WAN interface, indicating which side of the network the SGSN is operating as. The allowable values are DCE (network side) and DTE (user side).

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 1 1 DCE DTE

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–63

sgsnGb–FR-LMI-DLCI

ISSUE 1 REVISION 2

sgsnGb–FR-LMI-DLCI
Description
This parameter identifies the DLCI value used by the Local Management Interface (LMI). This should be set to 0, which implies the default for the standard being used.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 991 0

Format

Example

References

6–64

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-FR-LMI-STD

sgsnGb-FR-LMI-STD
Description
This parameter identifies the LMI standard to be used by FRS. The following options are available: ITU: ANSI: Old ANSI: OGOF: ITU-T Q.933 Annex-A Current version of ANSI T1.617 Annex D 1991 version of ANSI T1.617 Annex D Original group of 4

Attributes
Value type Valid range
integer 0 1 2 3 0 ITU ANSI Old ANSI OGOF

Default value Dependencies Access Status

read only mandatory

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–65

sgsnGb-FR-LMI-STD-Conform

ISSUE 1 REVISION 2

sgsnGb-FR-LMI-STD-Conform
Description
This parameter identifies conformance requirements over and above the local management standard.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 1 0 none Sprint

Format

Example

References

6–66

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-FR-T391

sgsnGb-FR-T391
Description
This parameter is the link integrity verification polling timer. This is the time, in seconds, between the STATUS ENQUIRY messages sent by FRS. The value should be less than that of the T392 timer, and is used when the SGSN is configured as DTE.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 5 to 29 10

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–67

sgsnGb-FR-T392

ISSUE 1 REVISION 2

sgsnGb-FR-T392
Description
This parameter is the polling verification timer. This is the time, in seconds, between the STATUS ENQUIRY messages, as expected by FRS when configured by FRS to detect errors at the network side. The value should be greater than that of the T391 timer, and is used when the SGSN is configured as DCE.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 6 to 30 15

Format

Example

References

6–68

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-FR-N391

sgsnGb-FR-N391
Description
This parameter is the full status polling counter. Every N391 cycles FRS requests a FULL STATUS ENQUIRY from the network to all PVCs.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 255 6

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–69

sgsnGb-FR-N392

ISSUE 1 REVISION 2

sgsnGb-FR-N392
Description
This parameter is the error threshold value. If the number of errors detected by FRS reaches the threshold value within the last N393 events, the FRS can assume there is a service affecting condition at the user-network interface. FRS stops transmitting data and continues link verification procedures. FRS detects service restoration by detecting N392 consecutive events have occurred without error. N392 should be less than or equal to N393

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 10 3

Format

Example

References

6–70

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-FR-N393

sgsnGb-FR-N393
Description
This parameter is the monitored events count. This value is used to set the count cycle used when counting consecutive error or non-error events. It allows FRS to detect whether error or non-error events predominate. N393 should be greater than or equal to N392. If N393 is set to a value much less than N391, the link could go in and out of the error condition without the user equipment or network being notified.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 10 4

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–71

sgsnGb-FR-StartTimeslot

ISSUE 1 REVISION 2

sgsnGb-FR-StartTimeslot
Description
This parameter specifies the timeslots of the bearer channel over the E1/T1 link. This parameter, together with sgsnGb-FR-EndTimeslot specifies a continuous span of the E1/T1 timeslots to be used for fractional support. For an E1 interface, timeslots 0 and 16 are reserved.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory Integer 1 to 31 1

Format
Timeslots number range is from 0 to 31 and is mapped to the bits in the mask as follows: timeslot #: Bit in Mask: 0 1 2 3 4 ... 31 0 1 2 3 4 ... 31

(counting from the least significant bit

Example
MSD 000000fe hex = 00000000 00000000 00000000 11111110 Hence, timeslots 1 to 7 are being used by this bearer channel (timeslot 0 is reserved). LSD

References

6–72

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-FR-EndTimeslot

sgsnGb-FR-EndTimeslot
Description
This parameter is the last timeslot of the bearer channel over the E1/T1 link. Together with sgsnGb-FR-StartTimeslot this parameter specifies a continuous span of the E1/T1 timeslots (DSO) to be used for fractional support. For an E1 interface, timeslots 0 and 16 are reserved.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 31 31

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–73

sgsnGb-FR-MaxFrame

ISSUE 1 REVISION 2

sgsnGb-FR-MaxFrame
Description
This parameter specifies the maximum size of the HDLC frame that the channel can receive, inlusive of the 2 bytes CRC and 2 byte address.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 1604 1604

Format

Example

References

6–74

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-FR-BitMask

sgsnGb-FR-BitMask
Description
This parameter defines the valid bits in each timeslot used for this channel. For example, a 64bps timeslot would be specified with a BitMask 0xFF and a 56kbps would be specified with BitMask 0x7F.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory Octet String 1 ff

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–75

sgsnGb-FR-FramingFormat

ISSUE 1 REVISION 2

sgsnGb-FR-FramingFormat
Description
This parameter specifies the E1 framing format to be used on the entire E1 interface.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory Integer 0 1 E1CRC4 E1BF

Format

Example

References

6–76

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-FR-Encoding

sgsnGb-FR-Encoding
Description
This parameter defines the E1 encoding to be used on the entire E1 interface.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 1 AMI HDB3

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–77

sgsnGb-FR-LineBuildout

ISSUE 1 REVISION 2

sgsnGb-FR-LineBuildout
Description
This parameter defines the line buildout to be used on the entire E1 interface.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 1 OHM_75 OHM_120

Format

Example

References

6–78

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-FR-Clocking

sgsnGb-FR-Clocking
Description
This parameter defines the transmitter clock reference to be used on the entire E1 interface.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 1 CLOCK_LOCAL CLOCK_LOOP

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–79

sgsnMaxActivePDP-Context–PerIMSI

ISSUE 1 REVISION 2

sgsnMaxActivePDP-Context–PerIMSI
Description
This parameter identifies the maximum number of Active PDP Context per IMSI. When set the parameter affects all IMSI, the number is not maintained for individual IMSI.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 10 1

Format

Example

References

6–80

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnSNDCP-VersionNum

sgsnSNDCP-VersionNum
Description
This parameter identifies the version of GPRS SNDCP that is running.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 15 0

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–81

sgsnSNDCP-DataCompressionAlgorithm

ISSUE 1 REVISION 2

sgsnSNDCP-DataCompressionAlgorithm
Description
This parameter identifies the preferred data compression algorithm.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 0 1 1 : no compression : v.42 bis

Format

Example

References

6–82

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnSNDCP-HeaderCompressionAlgorithm

sgsnSNDCP-HeaderCompressionAlgorithm
Description
This parameter identifies the preferred header compression algorithm.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 0 1 1 : no compression : tcp-ip

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–83

sgsnSNDCP–CompressionDirection

ISSUE 1 REVISION 2

sgsnSNDCP–CompressionDirection
Description
v.42 bis P0. This parameter identifies the direction of the data compression. It defines whether compression will be done on the uplink only, downlink only, both or none.

Attributes
Value type Valid range
integer 0 1 2 3 3 : none : uplink : downlink : both

Default value Dependencies Access Status

read - write mandatory

Format

Example

References

6–84

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnSNDCP-MaxCompressionCodewords

sgsnSNDCP-MaxCompressionCodewords
Description
v.42 bis P1. This parameter identifies the maximum number of codewords the dictionary may contain.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 512 to 2048 2048

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–85

sgsnSNDCP-MaxCodewordLength

ISSUE 1 REVISION 2

sgsnSNDCP-MaxCodewordLength
Description
v.42 bis P2. This parameter identifies the maximum length of text a codeword may represent.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 6 to 250 20

Format

Example

References

6–86

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnSNDCP-CompressorShared

sgsnSNDCP-CompressorShared
Description
This parameter identifies whether the preference is to have one data compressor per SAPI (that is, shared by multiple NSAPIs) or one compressor per NSAPI.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 0 1 1 : not shared : shared

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–87

sgsnGb-NSVC-Table

ISSUE 1 REVISION 2

sgsnGb-NSVC-Table
Description
This table lists the NS–VCs defined for this SGSN, and their mappings to the FR PVC. Row Creation: For the successful creation of a row in this table, the referred FR PVC must exist and have already been properly configured within the FR network or via direct connection with the BSS. The FR bearer channel referred must have been configured. A row can only be deleted when no link Set has any reference to the NS-VC defined by it. Any other attempt at deleting it will be rejected. Currently, the software does not have provision to update individual entry values for a row after it has been created. Updates can only be achieved by deleting the existing row and then inserting a new row containing the new values, through separate management requests.

Row Deletion:

Row Update

Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory

Format

Example

References

6–88

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-NSVCTableEntry

sgsnGb-NSVCTableEntry
Description
Each entry contains one PVC definition and its mapping to the NS - VC.

Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory

Format
sgsnGb-NSVCTableEntry ::= SEQUENCE{ sgsnGb-NSVC-RowStatus sgsnGb-NSVC-NSVCI sgsnGb-NSVC-DLCI sgsnNGb-NSVC-PhyLinkId sgsnGb-NSVC-BearerChannelId sgsnGb-NSVC-CIR sgsnGb-NSVC-Bc sgsnGb-NSVC-Be sgsnGb-NSVC-StepCount sgsnGb-NSVCF-lowStyle } GSN-RowStatus, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER,

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–89

sgsnGb-NSVC-RowStatus

ISSUE 1 REVISION 2

sgsnGb-NSVC-RowStatus
Description
This parameter indicates the status of conceptual rows.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory undefined

Format

Example

References

6–90

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-NSVC-NSVCI

sgsnGb-NSVC-NSVCI
Description
This parameter is the identifier of a NS-VC, unique within the SGSN. It is used by Gb to maintain the NS-VC List and the mapping to the FR PVC.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 65535

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–91

sgsnGb-NSVC-DLCI

ISSUE 1 REVISION 2

sgsnGb-NSVC-DLCI
Description
This parameter is the FR PVC Data Link Connection ID, unique per FR BearerChannel. It is used, together with the BearerChannelId, by Gb to maintain the NS-VCI to PVC mapping. The valid range is 16 to 991; 0 to 15 are reserved for FR and are therefore not available for general use.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 16 to 991 16

Format

Example

References

6–92

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-NSVC-LinkId

sgsnGb-NSVC-LinkId
Description
This parameter is the identifier for the physical link (E1/T1) as defined in the sgsnGb-FR-Table.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 3 0

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–93

sgsnGb-NSVC-BearerChannelId

ISSUE 1 REVISION 2

sgsnGb-NSVC-BearerChannelId
Description
This parameter is the FR Channel Identifier of the PVC associated with the NS-VC, as defined in the sgsnGb-FR-Table.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 30 0

Format

Example

References

6–94

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-NSVC-FR-PVC-CIR

sgsnGb-NSVC-FR-PVC-CIR
Description
This parameter is the committed information rate (bits/sec) at which the FR network transfers information to the end system under normal conditions. The rate is averaged over time interval T, where T is calculated to be Bc/CIR. The maximum value will be the rate of full E1 (32 x 64k)

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 2048000 1

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–95

sgsnGb-NSVCFRPVCBc

ISSUE 1 REVISION 2

sgsnGb-NSVCFRPVCBc
Description
This parameter is the committed burst size. This is the maximum amount of data (in bits) that the FR network agrees to transfer under normal conditions, during time interval T. This data may or may not be interrupted (that is, it may appear in one frame or several frames).

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 2048000 1

Format

Example

References

6–96

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-NSVC-FR-PVC-Be

sgsnGb-NSVC-FR-PVC-Be
Description
This parameter is the maximum amount of uncommitted data (in bits) in excess of Bc that the FR network will attempt to deliver, during time interval T. This data may or may not be interrupted (that is, it may appear in one frame or several frames). Excess burst is marked discard eligible (DE) by the FRS driver.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 2048000 0

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–97

sgsnGb-NSVC-FR-PVC-StepCount

ISSUE 1 REVISION 2

sgsnGb-NSVC-FR-PVC-StepCount
Description
This parameter is the value used by FRS when transmitting frames to increase or reduce CIR. If FRS receives stepcount frames with the BECN bit set, it reduces the CIR to the next step rate below the current offered rate. If it receives stepcount/2 consecutive frames with the BECN bit not set it increases the CIR.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 2 to 1000 8

Format

Example

References

6–98

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-NSVC-FR-PVC-FlowStyle

sgsnGb-NSVC-FR-PVC-FlowStyle
Description
This parameter determines the type of congestion control used by the FRS.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 7 3 (FECN + BECN)

Format
Bit Map: FECN - 0x01, BECN - 0x02, CLLM - 0x04

Example
The default value is 3, which sets the first two bits (011). This initiates FECN and BECN congestion control.

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–99

sgsnLLC-VersionNum

ISSUE 1 REVISION 2

sgsnLLC-VersionNum
Description
This parameter identifies the version of GPRS LLC that is running.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 15 0

Format

Example

References

6–100

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

BSSGP parameter diagrams

BSSGP parameter diagrams
BVC block timer
The following diagram details BVC block and unblock messages. The sgsnBssgpT1 parameter determines the period of the BVC block timer,T1, which controls the blocking and unblocking procedures. A block or unblock message is sent every T1 seconds until the appropriate acknowlegement is received. PCU
BVC Block OR BVC Unblock

SGSN START T1

BVC Block ACK OR BVC Unblock ACK

STOP T1

sgsnBssgpT1
Range 1 – 30 Secs Default 3

Figure 6-22 BVC block timer

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–101

BSSGP parameter diagrams

ISSUE 1 REVISION 2

BVC reset timer
The following diagram details BVC reset messages. The sgsnBssgpT2 parameter determines the period of the BVC reset timer, T2. The timer is started when the reset message is sent and stopped on receipt of the reset acknowledgement. The BVC Reset forces peer entities to a known (blocked) state. Once both entities are at the same state the BVC unblock procedures can be carried out to bring the BVC into service. PCU
BVC Reset

SGSN START T2

BVC Reset ACK

STOP T2

sgsnBssgpT2
Range 1 – 1000 Secs Default 60

Figure 6-23 BVC reset timer

6–102

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

BSSGP parameter diagrams

BVC block retries
The following diagram details the BVC Block message, which is repeated if no response is received during period T1. The sgsnBssgpBvcBlockRetries parameter is used to set the number of times that the BVC Block message is sent. PCU
BVC Block

SGSN T1

repeated for BVC BlockRetries

BVC Block

T1

sgsnBssgpBvcBlockRetries
Range 1 – 30 Default 3

Figure 6-24 BVC block retries

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–103

BSSGP parameter diagrams

ISSUE 1 REVISION 2

BVC unblock retries
The following diagram details the BVC Unblock message, which is repeated if no response is received during period T1. The sgsnBssgpBvcUnblockRetries parameter is used to set the number of times that the BVC Unblock message is sent. PCU
BVC Unblock

SGSN T1

repeated for BVC UnblockRetries

BVC Unblock

T1

sgsnBssgpBvcUnblockRetries
Range 1 – 30 Default 3

Figure 6-25 BVC unblock retries

6–104

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

BSSGP parameter diagrams

BVC reset retries
The following diagram details the BVC Reset message, which is repeated if no response is received during period T2. The sgsnBssgpBvcResetRetries parameter is used to set the number of times that the BVC Reset message is sent. PCU
BVC Reset

SGSN T2

repeated for BVC ResetRetries

BVC Reset

T2

sgsnBssgpBvcResetRetries
Range 1 – 30 Default 3

Figure 6-26 BVC set retries

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–105

sgsnGb-BVC-Table

ISSUE 1 REVISION 2

sgsnGb-BVC-Table
Description
This table lists the BVCI to NS-VCI mappings for this SGSN. Row Creation: For the successful creation of a row in this table, the referred NS-VCI must have already been defined in the sgsnGb-NSVC-Table. A row may be deleted if the BVC defined by the row is not being referenced by any rows in sgsnGb-CellTable or sgsnSigPlaneInfoTable. Currently, the software does not have provision to update individual entry values for a row after it has been created. Updates can only be achieved by deleting the existing row and then inserting a new row containing the new values, through separate management requests.

Row Deletion:

Row Update

Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory

Format

Example

References

6–106

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-BVC-TableEntry

sgsnGb-BVC-TableEntry
Description
This parameter defines one BVCI.

Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory ??? ??? ???

Format
sgsnGb-BVC-TableEntry ::= SEQUENCE{ sgsnGb-BVC-RowStatus sgsnGb-BVC-BVCI sgsnGb-BVC-BVCI-Type sgsnGb-BVC-NSVCI sgsnNGb-BVC-SigBVCI } GSN-RowStatus, INTEGER, INTEGER, INTEGER, INTEGER,

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–107

sgsnGb-BVC-RowStatus

ISSUE 1 REVISION 2

sgsnGb-BVC-RowStatus
Description
This parameter indicates the status of a table row.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory undefined

Format

Example

References

6–108

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-BVC-BVCI

sgsnGb-BVC-BVCI
Description
This parameter is the identifier of the BVC, unique within the SGSN. It is used by Gb to communicate with BSS over the end-to-end BVCs.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 65535 (ffff hex)

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–109

sgsnGb-BVC-BVCI-Type

ISSUE 1 REVISION 2

sgsnGb-BVC-BVCI-Type
Description
This parameter identifies the type of BVC : PTP, PTM OR Sig (Signalling).

Attributes
Value type Valid range
integer 0 1 2 1 Sig PTP PTM

Default value Dependencies Access Status

read only mandatory

Format

Example

References

6–110

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-BVC-NSVCI

sgsnGb-BVC-NSVCI
Description
This parameter identifies the NS-VC that serves this BVC. It is used by Gb to maintain the BVCI to NS-VCI mapping. The parameter must be defined in sgsnGb-NSVC-Table.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 65535 (ffff hex) 0

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–111

sgsnGb-BVC-SigBVCI

ISSUE 1 REVISION 2

sgsnGb-BVC-SigBVCI
Description
This parameter identifies the signalling BVC associated with the BVC/NS-VC pair (when the BVC is of the type PTP or PTM) being defined by the table row. It is used by Gb to communicate with BSS when the data BVC fails. When the BVC in the BVC/NS-VC pair is a signalling BVC itself, this field will have a value of 0. If the value of this field is not 0, it should already have been previously defined in the BVC table. It should be noted, that while 0 is not a valid BVCI value, it is allowed for this field.

Attributes
Value type Valid range Default value Dependencies sgsnGb-BVC-BVCI Access Status
read only mandatory integer 0 to 65535 (ffff hex)

Format

Example

References

6–112

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnBSSGP-T1

sgsnBSSGP-T1
Description
This parameter is the timer, in seconds, that guards the blocking and unblocking procedures. The block or unblock is sent every sgsnBssgpT1 seconds until the peer acknowledges or the number of retries (sgsnBssgpBvcBlockRetries or sgsnBssgpBvcUnblockRetries ) is completed.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 30 3

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–113

sgsnBSSGP–T2

ISSUE 1 REVISION 2

sgsnBSSGP–T2
Description
This parameter is the timer, in seconds, that guards the reset procedure. The reset is sent every sgsnBssgpT2 seconds until the peer acknowledges or the number of retries (sgsnBssgpBvcResetRetries) is completed.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 1000 60

Format

Example

References

6–114

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnBSSGP–BVC-BlockRetries

sgsnBSSGP–BVC-BlockRetries
Description
This parameter indicates the number of attempts to retry a BVC-BLOCK.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 30 3

Format

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–115

sgsnBSSGP-BVC-UnblockRetries

ISSUE 1 REVISION 2

sgsnBSSGP-BVC-UnblockRetries
Description
This parameter indicates the number of attempts to retry a BVC-UNBLOCK.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory integer 1 to 30 3

Format

Example

References

6–116

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnBSSGP-BVC-ResetRetries

sgsnBSSGP-BVC-ResetRetries
Description
This parameter indicates the number of attempts to retry a BVC-RESET.

Dependencies Access Status
read - write mandatory

Format

Example

Attributes
Value type Valid range Default value
integer 1 to 30 3

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–117

sgsnGb-Cell-Table

ISSUE 1 REVISION 2

sgsnGb-Cell-Table
Description
This table provides the Cell to BVCI mappings that are defined for this SGSN. Row Creation: Row Deletion: Row Update For the successful creation of a row in this table, the referred BVCI must have already been defined in the sgsnGb-BVC-Table. There is no restriction on row deletion. Currently, the software does not have provision to update individual entry values for a row after it has been created. Updates can only be achieved by deleting the existing row and then inserting a new row containing the new values, through separate management requests.

Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory

Format

Example

References

6–118

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-Cell-BVC-TableEntry

sgsnGb-Cell-BVC-TableEntry
Description
Each entry defines one <CGI, PTP–BVCI> pair.

Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory

Format
sgsnRaiNseiEntry ::= SEQUENCE{ sgsnGb-Cell-BVCRowStatus sgsnGb-Cell-BVCMCC sgsnGb-Cell-BVCMNC sgsnGb-Cell-BVCLAC sgsnGb-Cell-BVC-CI sgsnGb-Cell-BVC-PTP-BVCI } GSN-RowStatus, Display String, Display String, INTEGER, INTEGER, INTEGER

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–119

sgsnGb-Cell-BVCRowStatus

ISSUE 1 REVISION 2

sgsnGb-Cell-BVCRowStatus
Description
This parameter indicates the status of a table row.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory undefined

Format

Example

References

6–120

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-Cell-BVC-MCC

sgsnGb-Cell-BVC-MCC
Description
This parameter identifies the Mobile Country Code.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory display string

Format
3 decimal digits in ASCII format, according to CCITT Rec E.212.

Example

References
CCITT Rec E.212

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–121

sgsnGb-Cell-BVCMNC

ISSUE 1 REVISION 2

sgsnGb-Cell-BVCMNC
Description
This parameter identifies the Mobile Network Code.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory display string

Format
2 decimal digits in ASCII format, according to CCITT Rec E.212.

Example

References
CCITT Rec E.212

6–122

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-Cell-BVCLAC

sgsnGb-Cell-BVCLAC
Description
This parameter identifies the Location Area Code.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 65535

Format
2 bytes integer, according to TS GSM 04.08

Example

References
TS GSM 04.08

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–123

sgsnGb-Cell-BVC-CI

ISSUE 1 REVISION 2

sgsnGb-Cell-BVC-CI
Description
This parameter identifies the cell identity.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 65535

Format
2 bytes integer, according to TS GSM 04.08

Example

References
TS GSM 04.08

6–124

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnGb-Cell-BVC-PTP-BVCI

sgsnGb-Cell-BVC-PTP-BVCI
Description
This parameter is the identifier of the PTP BVCI serving this cell. It is used by Gb to maintain the CGI to PTP BVCI mappings. It must be defined in sgsnGb-BVC-Table.

Attributes
Value type Valid range Default value Dependencies sgsnGb-BVC-BVCI Access Status
read only mandatory integer 0 to 65535

Format

Example

References
TS GSM 04.08

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–125

sgsnSigPlaneInfoTable

ISSUE 1 REVISION 2

sgsnSigPlaneInfoTable
Description
This table provides Signalling Plane Control Information for this SGSN. It is used by the SGSN to obtain the following mappings: CGI > RAI, CGI > SIG BVCI and RAI > SIG BVCI (PCU). Row Creation: For succesful row creation, the referred BVCI must have already been defined in the sgsnGb-BVC-Table. No restrictions. The software does not currently have the provision to update individual entry values after a row has been created. Updates can only be achieved by deleting the existing row and then inserting a new row with the new values.

Row Deletion: Row Update

Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory

Format

Example

References

6–126

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnSigPlaneInfoTableEntry

sgsnSigPlaneInfoTableEntry
Description
This parameter defines the entry structure for the sgsnSigPlaneInfoTable.

Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory

Format
sgsnSigPlaneInfoTableEntry::= SEQUENCE{ sgsnSigPlaneInfotRowStatus sgsnSigPlaneInfo-MCC sgsnSigPlaneInfo-MNC sgsnSigPlaneInfo-LAC sgsnSigPlaneInfo-CI sgsnSigPlaneInfo-RAC sgsnSigPlaneInfoSIG-BVCI } GSN-RowStatus, DISPLAYSTRING, DISPLAYSTRING, INTEGER, INTEGER, INTEGER, INTEGER

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–127

sgsnSigPlaneInfoRowStatus

ISSUE 1 REVISION 2

sgsnSigPlaneInfoRowStatus
Description
This parameter indicates the status of a table row.

Attributes
Value type Valid range Default value Dependencies Access Status
read - write mandatory undefined

Format

Example

References

6–128

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnSigPlaneInfo-MCC

sgsnSigPlaneInfo-MCC
Description
This parameter identifies the Mobile Country Code.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer

Format
2 digits decimal in ASCII format, according to CCITT Rec E.212

Example

References
CCITT Rec E.212

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–129

sgsnSigPlaneInfo-MNC

ISSUE 1 REVISION 2

sgsnSigPlaneInfo-MNC
Description
This parameter identifies the Mobile Network Code.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory

Format
2 digits decimal in ASCII format, according to CCITT Rec E.212

Example

References
CCITT Rec E.212

6–130

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnSigPlaneInfo-LAC

sgsnSigPlaneInfo-LAC
Description
This parameter identifies the Location Area Code.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 65535

Format
2 digits decimal in ASCII format, according to TS GSM 04.08.

Example

References
TS GSM 04.08

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–131

sgsnSigPlaneInfo-CI

ISSUE 1 REVISION 2

sgsnSigPlaneInfo-CI
Description
This parameter identifies the Cell Identity.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 65535

Format
2 bytes integer, according to TS GSM 04.08

Example

References
TS GSM 04.08

6–132

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnSigPlaneInfo-RAC

sgsnSigPlaneInfo-RAC
Description
This parameter identifies the Routing Area Code, part of a Global identifier of a Routing Area. RAI is defined as MCC + MNV + LAC + RAC, since the MCC, MNC and LAC are previously defined, the only remaining requirement is RAC, to form the RAI.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 0 to 255

Format
1 bytes integer

Example

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

6–133

sgsnSigPlaneInfoSIG-BVCI

ISSUE 1 REVISION 2

sgsnSigPlaneInfoSIG-BVCI
Description
This parameter identifies the Signalling BVCI of a PCU and must be defined in sgsnGb–BVC-Table.

Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 65535

Format
1 bytes integer

Example

References

6–134

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 7

SGSN Statistics Attributes

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Introduction to SGSN statistics

Introduction to SGSN statistics
Purpose of this chapter
This chapter describes statistical measurements generated by the SGSN element of the GSN, in response to monitored network and system events.

How this chapter is structured
This chapters contains SGSN statistics information, using the following structure to present that information: S S S S S S An introduction to the chapter and the chapter structure. Details of the MIB structure identifying the available SGSN objects. Attributes tables detailing the statistics attributes available for each SGSN object. Ladder diagrams describing when the statistics are generated (pegged). Traffic direction diagrams indicating the statistics applicable to uplink and downlink traffic. Data sheets containing the attribute information of the individual statistics identified in the attributes tables. NOTE This information may be structured differently for training purposes

SGSN OID structure
The following illustration identifies the SGSN OID structure, which forms part of the overall OID structure.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–1

Introduction to SGSN statistics

ISSUE 1 REVISION 2

mot-gprs-sgsm (1) System (2) OAMP (3) HA (4) OP (1) diag (2) action (5) Gb (1) bssgp (2) NS (6) Gn (1) SM (2) SNDCP (3) LLC (7) Sig (1) GTP (2) GMM (8) Meter (9) Perf (10) SW

Figure 7-1 SGSN OID structure

Attributes Tables
Details of the attributes available for each performance management object can be found in the following tables:
7–2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Introduction to SGSN statistics

Sig GTP GTP_Gn SNDCP LLC BSSGP NS FR L3MM Misc

Table 7-1 Table 7-2 Table 7-3 Table 7-4 Table 7-5 Table 7-6 NO TAG Table 7-7 Table 7-8

Ladder diagrams
The following performance management ladder diagrams are available: Figure 7-2 Figure 7-3 Figure 7-9 Signalling GTP Session Activation statistics Signalling GTP Protocol Error statistics L3MM Attach statistics

Figure 7-10 L3MM Detach statistics Figure 7-11 L3MM Session Activation statistics Figure 7-12 L3MM Deactivation statistics Figure 7-13 L3MM RA Update statistics

Traffic direction diagrams
The following performance management traffic direction diagrams are available: Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Figure 2-8 GTP_Gn protocol layer SNDCP protocol layer LLC protocol layer BSSGP protocol layer NS protocol layer

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–3

Signalling GTP statistics tables and diagrams

ISSUE 1 REVISION 2

Signalling GTP statistics tables and diagrams
Introduction to signalling GTP tables and diagrams
The information in this section is an aid to understanding the statistics function of a particular SGSN object. Table 7-1 identifies the statistics attributes available for the signalling GTP interface. The following diagrams are used to explain when the statistics are pegged: Figure 7-2 Signalling GTP Session Activation. Figure 7-3 Signalling GTP Protocol Error.

Signalling interface over GTP statistics
The following table details the statistics attributes available for sgsn-perf-gtp-sig : Table 7-1 SGSN signalling GTP statistics attributes OID number 1 2 3 4 5 6 attribute sgsnNumSuccessSessionActivationRcvd sgsnNumUnsuccessSessionActivationRcvd sgsnNumSessionActivationSent sgsnNumProtocolErrorTooShort sgsnNumProtocolErrorWrongHeader sgsnNumProtocolErrorUnexpectedMsg

7–4

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Signalling GTP statistics tables and diagrams

Signalling GTP Session Activation statistics
The following is a ladder diagram detailing a Signalling GTP Session Activation Sent from a SGSN to a GGSN, and the expected responses. It also indicates the statistics pegged for the Request and the responses.
SGSN PDP CONTEXT REQUEST GGSN

sgsnNumSessionActivationSent

PDP CONTEXT ACCEPT

sgsnNumSuccessSessionActivationRcvd
OR PDP CONTEXT REJECT

sgsnNumUnsuccessSessionActivationRcvd

Figure 7-2 Signalling GTP Session Activation

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–5

Signalling GTP statistics tables and diagrams

ISSUE 1 REVISION 2

Signalling GTP Protocol Error statistics
The following is a ladder diagram detailing a Signalling GTP Protocol Error statistics pegged as a result of incorrect signalling information received from the GGSN.
SGSN BAD SIGNALLING PDU GGSN

sgsnNumProtocolErrorTooShort

BAD SIGNALLING PDU

sgsnNumProtocolErrorWrongHeader

SIGNALLING PDU

sgsnNumProtocolErrorUnexpectedMsg

Figure 7-3 Signalling GTP Protocol Error

7–6

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

GTP_Gn statistics tables and diagrams

GTP_Gn statistics tables and diagrams
Introduction to GTP_Gn tables and diagrams
The information in this section is an aid to understanding the statistics function of a particular SGSN object. Table 7-2 identifies the statistics attributes available for the GTP_Gn interface. The following diagram is used to explain when the statistics are pegged: Figure 7-4 GTP protocol layer.

Gn interface statistics
The following table details the statistics attributes available for sgsn-perf-gtp-gn : Table 7-2 SGSN GTP_Gn interface statistics attributes OID number 1 2 3 4 5 6 7 8 9 10 11 attribute sgsnNumCurrentGgsnConnections sgsnNumGtpDataPacketSentToGGSN sgsnNumGtpDatabytesSentToGGSN sgsnNumGtpDataPacketsRcvdFromGGSN sgsnNumGtpDataBytesRcvdFromGGSN sgsnNumGtpDownLinkDataPacketsSent sgsnNumGtpDownLinkDataBytesSent sgsnNumGtpUpLinkDataPacketsRcvd sgsnNumGtpUpLinkDataBytesRcvd sgsnNumGtpUpLinkDataPacketsDropped sgsnNumGtpDownLinkDataPacketsDropped

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–7

GTP_Gn statistics tables and diagrams

ISSUE 1 REVISION 2

GTP_Gn protocol layer
The following diagram details the traffic direction and statistics associated with the SGSN GTP_Gn protocol layer Downlink
sgsnNumGtpDownLinkDataPacketsSent sgsnNumGtpDownLinkDataBytesSent sgsnNumGtpDataPacketsRcvdFromGGSN sgsnNumGtpDataBytesRcvdFromGGSN sgsnNumGtpDownLinkDataPacketsDropped

Uplink
sgsnNumGtpUpLinkDataPacketsRcvd sgsnNumGtpUpLinkDataBytesRcvd sgsnNumGtpDataPacketsSentT oGGSN sgsnNumGtpDataBytesSentT oGGSN sgsnNumGtpUpLinkDataPacketsDropped

Downlink Sent Uplink Rcvd IP IP

SNDCP

SNDCP

GTP TCP/ UDP

GTP TCP/ UDP

LLC

LLC

RLC MAC GSM RF

RLC MAC GSM RF

BSSGP Network Service L1 Bis

Downlink Rcvd BSSGP IP IP Uplink Sent Network Service L1 Bis L2 L1 L2 L1

MS

BSS

SGSN

GGSN

Figure 7-4 GTP protocol layer

7–8

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

SNDCP statistics tables and diagrams

SNDCP statistics tables and diagrams
Introduction to SNDCP tables and diagrams
The information in this section is an aid to understanding the statistics function of a particular SGSN object. Table 7-3 identifies the statistics attributes available for the SNDCP protocol layer. The following diagram is used to explain when the statistics are pegged: Figure 7-5 SNDCP protocol layer.

SNDCP statistics
The following table details the statistics attributes available for sgsn-perf-sndcp : Table 7-3 SGSN SNDCP statistics attributes OID number 1 2 3 4 5 6 7 8 9 10 attribute sgsnNumSndcpUpLinkDataPacketsSent sgsnNumSndcpUpLinkDataBytesSent sgsnNumSndcpDownLinkDataPacketsRcvd sgsnNumsndcpDownLinkDataBytesRcvd sgsnNumSndcpDownLinkDataPacketsSent sgsnNumSndcpDownLinkDataBytesSent sgsnNumSndcpUpLinkDataPacketsRcvd sgsnNumSndcpUpLinkDataBytesRcvd sgsnNumSndcpUpLinkDataPacketsDropped sgsnNumSndcpDownLinkDataPacketsDropped

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–9

SNDCP statistics tables and diagrams

ISSUE 1 REVISION 2

SNDCP protocol layer
The following diagram details the traffic direction and statistics associated with the SGSN SNDCP protocol layer Downlink
sgsnNumSndcpDownLinkDataPacketsSent sgsnNumSndcpDownLinkDataBytesSent sgsnNumSndcpDownLinkDataPacketsRcvd sgsnNumSndcpDownLinkDataBytesRcvd sgsnNumSndcpDownLinkDataPacketsDropped

Uplink
sgsnNumSndcpUpLinkDataPacketsRcvd sgsnNumSndcpUpLinkDataBytesRcvd sgsnNumSndcpUpLinkDataPacketsSent sgsnNumSndcpUpLinkDataBytesSent sgsnNumSndcpUpLinkDataPacketsDropped

Uplink Sent Downlink Rcvd IP IP

SNDCP

SNDCP

GTP TCP/ UDP

GTP TCP/ UDP IP L2 L1

LLC

LLC

RLC MAC GSM RF

RLC MAC GSM RF

Uplink Rcvd BSSGP BSSGP IP Downlink Sent Network Network L2 Service Service L1 Bis L1 Bis L1

MS

BSS

SGSN

GGSN

Figure 7-5 SNDCP protocol layer

7–10

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

LLC statistics tables and diagrams

LLC statistics tables and diagrams
Introduction to LLC tables and diagrams
The information in this section is an aid to understanding the statistics function of a particular SGSN object. Table 7-4 identifies the statistics attributes available for the LLC protocol layer. The following diagram is used to explain when the statistics are pegged: Figure 7-6 LLC protocol layer.

LLC statistics
The following table details the statistics attributes available for sgsn-perf-llc : Table 7-4 SGSN LLC statistics attributes OID number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 attribute sgsnNumLlcDownLinkDataPacketsSent sgsnNumLlcDownLinkDataBytesSent sgsnNumLlcUpLinkDataPacketsRcvd sgsnNumLlcUpLinkDataBytesRcvd sgsnNumLlcDownLinkSignalPacketsSent sgsnNumLlcDownLinkSignalBytesSent sgsnNumLlcUpLinkSignalPacketsRcvd sgsnNumLlcUpLinkSignalBytesRcvd sgsnNumLlcUpLinkDataPacketsSent sgsnNumLlcUpLinkDataBytesSent sgsnNumLlcDownLinkDataPacketsRcvd sgsnNumLlcDownLinkDataBytesRcvd sgsnNumLlcUpLinkSignalPacketsSent sgsnNumLlcUpLinkSignalBytesSent sgsnNumLlcDownLinkSignalPacketsRcvd sgsnNumLlcDownLinkSignalBytesRcvd sgsnNumLlcUpLinkDataPacketsDropped sgsnNumLlcDownLinkDataPacketsDropped sgsnNumLlcUpLinkSignalPacketsDropped sgsnNumLlcDownLinkSignalPacketsDropped sgsnNumLlcPacketsResent

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–11

LLC statistics tables and diagrams

ISSUE 1 REVISION 2

LLC protocol layer
The following diagram details the traffic direction and statistics associated with the SGSN LLC protocol layer Downlink
sgsnNumLlcDownLinkDataPacketsSent sgsnNumLlcDownLinkDataBytesSent sgsnNumLlcDownLinkSignalPacketsSent sgsnNumLlcDownLinkSignalBytesSent sgsnNumLlcDownLinkDataPacketsRcvd sgsnNumLlcDownLinkDataBytesRcvd sgsnNumLlcDownLinkSignalPacketsRcvd sgsnNumLlcDownLinkSignalBytesRcvd sgsnNumLlcDownLinkDataPacketsDropped sgsnNumLlcDownLinkSignalPacketsDropped

Uplink
sgsnNumLlcUpLinkDataPacketsRcvd sgsnNumLlcUpLinkDataBytesRcvd sgsnNumLlcUpLinkSignalPacketsRcvd sgsnNumLlcUpLinkSignalBytesRcvd sgsnNumLlcUpLinkDataPacketsSent sgsnNumLlcUpLinkDataBytesSent sgsnNumLlcUpLinkSignalPacketsSent sgsnNumLlcUpLinkSignalBytesSent sgsnNumLlcUpLinkDataPacketsDropped sgsnNumLlcUpLinkSignalPacketsDropped

Uplink Sent IP Downlink Rcvd SNDCP GTP TCP/ UDP IP IP

SNDCP

GTP TCP/ UDP IP L2 L1

LLC

LLC

RLC MAC GSM RF

RLC MAC GSM RF

BSSGP Network Service

BSSGP

Network L2 Uplink Rcvd Service L1

Sent L1 Downlink Bis L1 Bis

MS

BSS

SGSN

GGSN

Figure 7-6 LLC protocol layer

7–12

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

BSSGP statistics tables and diagrams

BSSGP statistics tables and diagrams
Introduction to BSSGP tables and diagrams
The information in this section is an aid to understanding the statistics function of a particular SGSN object. Table 7-5 identifies the statistics attributes available for the BSSGP protocol layer. The following diagram is used to explain when the statistics are pegged: Figure 7-7 BSSGP protocol layer.

BSSGP statistics
The following table details the statistics attributes available for sgsn-perf-bssgp : Table 7-5 SGSN BSSGP statistics attributes OID number 1 2 3 4 5 6 7 8 9 10 attribute sgsnNumBssgpDownLinkDataPacketsSent sgsnNumBssgDownLinkdataBytesSent sgsnNumBssgpUpLinkDataPacketsRcvd sgsnNumBssgpUpLinkDataBytesRcvd sgsnNumBssgpUpLinkDataPacketsSent sgsnNumBssgpUpLinkDataBytesSent sgsnNumBssgpDownLinkDataPacketsRcvd sgsnNumBssgpDownLinkDataBytesRcvd sgsnNumBssgpUpLinkDataPacketsDropped sgsnNumBssgpDownLinkDataPacketsDropped

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–13

BSSGP statistics tables and diagrams

ISSUE 1 REVISION 2

BSSGP protocol layer
The following diagam details the traffic direction and statistics associated with the SGSN BSSGP protocol layer Downlink
sgsnNumBssgpDownLinkDataPacketsSent sgsnNumBssgpDownLinkDataBytesSent sgsnNumBssgpDownLinkDataPacketsRcvd sgsnNumBssgpDownLinkDataBytesRcvd sgsnNumBssgpDownLinkDataPacketsDropped

Uplink
sgsnNumBssgpUpLinkDataPacketsRcvd sgsnNumBssgpUpLinkDataBytesRcvd sgsnNumBssgpUpLinkDataPacketsSent sgsnNumBssgpUpLinkDataBytesSent sgsnNumBssgpUpLinkDataPacketsDropped

IP Uplink Sent GTP SNDCP Downlink Rcvd LLC TCP/ UDP IP L2 L1 Uplink Rcvd

IP

SNDCP

GTP TCP/ UDP IP L2 L1

LLC

RLC MAC GSM RF

RLC MAC GSM RF

BSSGP Network Service L1 Bis

BSSGP Network Service L1 Bis

Downlink Sent MS BSS SGSN GGSN

Figure 7-7 BSSGP protocol layer

7–14

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

NS statistics tables and diagrams

NS statistics tables and diagrams
Introduction to NS tables and diagrams
The information in this section is an aid to understanding the statistics function of a particular SGSN object. Table 7-6 identifies the statistics attributes available for the NS protocol layer. The following diagram is used to explain when the statistics are pegged: Figure 7-8 NS protocol layer.

NS statistics
The following table details the statistics attributes available for sgsn-perf-ns : Table 7-6 SGSN NS statistics attributes OID number 1 2 3 4 5 6 7 8 9 10 attribute sgsnNumNsDownLinkDataPacketsRcvd sgsnNumNsDownLinkDataBytesRcvd sgsnNumNsUpLinkDataPacketsSent sgsnNumNsUpLinkDataBytesSent sgsnNumNsUpLinkDataPacketsRcvd sgsnNumNsUpLinkDataBytesRcvd sgsnNumNsDownLinkDataPacketsSent sgsnNumNsDownLinkDataBytesSent sgsnNumNsUpLinkDataPacketsDropped sgsnNumNsDownLinkDataPacketsDropped

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–15

NS statistics tables and diagrams

ISSUE 1 REVISION 2

NS protocol layer
The following diagram details the traffic direction and statistics associated with the SGSN NS protocol layer Downlink
sgsnNumNsDownLinkDataPacketsSent sgsnNumNsDownLinkDataBytesSent sgsnNumNsDownLinkDataPacketsRcvd sgsnNumNsDownLinkDataBytesRcvd sgsnNumNsDownLinkDataPacketsDropped

Uplink
sgsnNumNsUpLinkDataPacketsRcvd sgsnNumNsUpLinkDataBytesRcvd sgsnNumNsUpLinkDataPacketsSent sgsnNumNsUpLinkDataBytesSent sgsnNumNsUpLinkDataPacketsDropped

IP

IP

SNDCP

SNDCP

GTP

GTP TCP/ UDP IP L2 L1

LLC

Uplink Sent TCP/ LLC Downlink Rcvd UDP RLC MAC GSM RF BSSGP Network Service L1 Bis BSSGP Network Service L1 Bis IP L2 L1

RLC MAC GSM RF

MS

BSS

Downlink Sent

Uplink Rcvd SGSN

GGSN

Figure 7-8 NS protocol layer

7–16

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

L3MM statistics tables and diagrams

L3MM statistics tables and diagrams
Introduction to L3MM tables and diagrams
The information in this section is an aid to understanding the statistics function of a particular SGSN object. Table 7-7 identifies the statistics attributes available for the L3MM interface. The following diagrams are used to explain when the statistics are pegged: Figure 7-9 L3MM Attach. Figure 7-10 L3MM Detach. Figure 7-11 L3MM Session Activation. Figure 7-12 L3MM Session Deactivation. Figure 7-13 L3MM RA Update.

L3MM statistics
The following table details the statistics attributes available for sgsn-perf-l3mm : Table 7-7 SGSN L3MM statistics attributes OID number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 attribute sgsnNumL3mmAttachReqRcvd sgsnNumL3mmAttachAcceptSent sgsnNumL3mmAttachRejectSent sgsnNumL3mmDetachReqRcvd sgsnNumL3mmDetachAcceptSent sgsnNumL3mmSessionActivateReqRcvd sgsnNumL3mmSessionActivateAcceptSent sgsnNumL3mmSessionActivateRejectSent sgsnNumL3SessionDeactivateReqRcvd sgsnNumL3mmSessionDeactivateAcceptSent sgsnNumL3mmRaUpdateReqRcvd sgsnNumL3mmRaUpdateAcceptSent sgsnNumL3mmRaUpdateRejectSent sgsnNumL3mmMsPagingReqSent sgsnNumL3mmSuccessfulPages

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–17

L3MM statistics tables and diagrams

ISSUE 1 REVISION 2

L3MM Attach statistics
The following is a ladder diagram detailing an L3MM Attach Request from an MS to the SGSN, and the expected responses. It also indicates the statistics pegged for the Request and the responses.
MS ATTACH REQUEST SGSN

sgsnNumL3mmAttachReqRcvd

ATTACH ACCEPT

sgsnNumL3mmAttachAcceptSent
OR ATTACH REJECT

sgsnNumL3mmAttachRejectSent

Figure 7-9 L3MM Attach

7–18

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

L3MM statistics tables and diagrams

L3MM Detach statistics
The following is a ladder diagram detailing an L3MM Detach Request from an MS to the SGSN, and the expected response. It also indicates the statistics pegged for the Request and the response.
MS DETACH REQUEST SGSN

sgsnNumL3mmDetachReqRcvd

DETACH ACCEPT

sgsnNumL3mmDetachAcceptSent

Figure 7-10 L3MM Detach

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–19

L3MM statistics tables and diagrams

ISSUE 1 REVISION 2

L3MM Session Activation statistics
The following is a ladder diagram detailing an L3MM Session Activation Request from an MS to the SGSN, and the expected responses. It also indicates the statistics pegged for the Request and the responses.
MS SESSION ACTIVATION REQUEST SGSN

sgsnNumL3mmSessionActivateReqRcvd

SESSION ACTIVATION ACCEPT

sgsnNumL3mmSessionActivateAcceptSent
OR SESSION ACTIVATION REJECT

sgsnNumL3mmSessionActivateRejectSent

Figure 7-11 L3MM Session Activation

7–20

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

L3MM statistics tables and diagrams

L3MM Session Deactivation statistics
The following is a ladder diagram detailing an L3MM Session Deactivation Request from an MS to the SGSN, and the expected response. It also indicates the statistics pegged for the Request and the response.
MS SESSION DEACTIVATION REQUEST SGSN

sgsnNumL3mmSessionDeactivateReqRcvd

SESSION DEACTIVATION ACCEPT

sgsnNumL3mmSessionDeactivateAcceptSent

Figure 7-12 L3MM Session Deactivation

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–21

L3MM statistics tables and diagrams

ISSUE 1 REVISION 2

L3MM RA Update statistics
The following is a ladder diagram detailing an L3MM RA Update Request from an MS to the SGSN, and the expected responses. It also indicates the statistics pegged for the Request and the responses.
MS RA UPDATE REQUEST SGSN

sgsnNumL3mmRAUpdateReqRcvd

RA UPDATE ACCEPT

sgsnNumL3mmRAUpdateAcceptSent
OR RA UPDATE REJECT

sgsnNumL3mmRAUpdateRejectSent

Figure 7-13 L3MM RA Update

7–22

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Miscellaneous statistics tables and diagrams

Miscellaneous statistics tables and diagrams
Introduction to miscellaneous tables and diagrams
The information in this section is an aid to understanding the statistics function of a particular SGSN object. Table 7-8 identifies the miscellaneous statistics attributes available. The following diagram is used to explain when the statistics are pegged:

Miscellaneous statistics
The following table details the statistics attributes available for sgsn-perf-misc : Table 7-8 SGSN miscellaneous statistics attributes OID number 1 2 3 attribute sgsnCurrentNumGprsAttachedMS sgsnCurrentNumActivePdpSession sgsnNumCells

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–23

sgsnNumSuccessSessionActivationRcvd

ISSUE 1 REVISION 2

sgsnNumSuccessSessionActivationRcvd
Description
This signalling statistic indicates the total number of Successful Session Activation Requests received.

Pegging
The statistic is pegged when the SGSN receives a PDP Context Accept from the GGSN.

Analysis
This statistic indicates the number of session management contexts activated within the GSN.

Reference
None

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–24

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumUnsuccessSessionActivationRcvd

sgsnNumUnsuccessSessionActivationRcvd
Description
This signalling statistic indicates the total number of Unsuccessful Session Activation Requests received.

Pegging
The statistic is pegged when the SGSN receives a PDP Context Reject from the GGSN.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–25

sgsnNumSessionActivationSent

ISSUE 1 REVISION 2

sgsnNumSessionActivationSent
Description
This signalling statistic indicates the total number of Session Activation Requests sent.

Pegging
The statistic is pegged when the SGSN sends a PDP Context Request to the GGSN.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service issues

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–26

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumProtocolError-TooShort

sgsnNumProtocolError-TooShort
Description
This signalling statistic indicates the total number of protocol errors - message too short.

Pegging
The statistic is pegged when the SGSN receives a Bad Signalling PDU from the GGSN, such as a PDP Context Accept that is too short.

Analysis

Reference

Usage
Protocol Utilization Fault Finding

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–27

sgsnNumProtocolError-WrongHeader

ISSUE 1 REVISION 2

sgsnNumProtocolError-WrongHeader
Description
This signalling statistic indicates the total number of protocol errors - unknown or erroneous header.

Pegging
The statistic is pegged when the SGSN receives a Bad Signalling PDU from the GGSN, such PDP Context Accept with the wrong header.

Analysis

Reference

Usage
Protocol Utilization Fault Finding

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–28

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumProtocolError-UnexpectedMsg

sgsnNumProtocolError-UnexpectedMsg
Description
This signalling statistic indicates the total number of protocol errors - unexpected message.

Pegging
The statistic is pegged when the SGSN receives a signalling PDU from the GGSN that was not expected. For example, if the SGSN receives a PDP Context Accept without having first sent a PDP Context Request.

Analysis

Reference

Usage
Protocol Utilization Fault Finding

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–29

sgsnNumCurrentGgsn-Connections

ISSUE 1 REVISION 2

sgsnNumCurrentGgsn-Connections
Description
This statistic indicates the current number of GGSN connections.

Pegging
The statistic is pegged when a new GGSN connection is made at the SGSN.

Analysis
The statistic can be used to monitor the connection load on an SGSN.

Reference

Usage
Network Planning Congestion Identification

Basis
GTP Gn

Statistic
Statistic Type
Guage

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–30

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumGtpDataPacketsSentToGGSN

sgsnNumGtpDataPacketsSentToGGSN
Description
This statistic indicates the total number of GTP data packets sent to the GGSN.

Pegging
The statistic is pegged each time the GTP protocol layer sends a data packet to the GGSN.

Analysis
The statistic can be used in conjunction with sgsnNumGtpUpLinkDataPacketsRcvd to show the SGSN data packet throughput in the uplink direction across the GTP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–31

sgsnNumGtpDataBytesSentToGGSN

ISSUE 1 REVISION 2

sgsnNumGtpDataBytesSentToGGSN
Description
This statistic indicates the total number of GTP data bytes (including protocol headers) sent to the GGSN.

Pegging
The statistic is pegged each time the GTP protocol layer sends a data byte to the GGSN.

Analysis
The statistic can be used in conjunction with sgsnNumGtpUpLinkDataBytesRcvd to show the SGSN data byte throughput in the uplink direction across the GTP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–32

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumGtpDataPacketsRcvdFromGGSN

sgsnNumGtpDataPacketsRcvdFromGGSN
Description
This statistic indicates the total number of GTP data packets received from the GGSN.

Pegging
The statistic is pegged each time the GTP protocol layer receives a data packet from the GGSN.

Analysis
The statistic can be used in conjunction with sgsnNumGtpDownLinkDataPacketsRcvd to show the SGSN data packet throughput in the downlink direction across the GTP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–33

sgsnNumGtpDataBytesRcvdFromGGSN

ISSUE 1 REVISION 2

sgsnNumGtpDataBytesRcvdFromGGSN
Description
This statistic indicates the total number of GTP data bytes (including protocol headers) received from the GGSN.

Pegging
The statistic is pegged each time the GTP protocol layer receives a data byte from the GGSN.

Analysis
The statistic can be used in conjunction with sgsnNumGtpDownLinkDataBytesRcvd to show the SGSN data byte throughput in the downlink direction across the GTP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–34

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumGtpDownLinkDataPacketsSent

sgsnNumGtpDownLinkDataPacketsSent
Description
This statistic indicates the total number of data packets sent in the downlink direction (to SNDCP protocol layer).

Pegging
The statistic is pegged each time the GTP protocol layer sends a data packet to the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumGtpDataPacketsRcvdFrom GGSN to show the SGSN data packet throughput in the downlink direction across the GTP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–35

sgsnNumGtpDownLinkDataBytesSent

ISSUE 1 REVISION 2

sgsnNumGtpDownLinkDataBytesSent
Description
This statistic indicates the total number of data bytes (including protocol headers) sent in the downlink direction (to SNDCP protocol layer).

Pegging
The statistic is pegged each time the GTP protocol layer sends a data byte to the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumGtpDataBytesRcvdFromGGSN to show the SGSN data byte throughput in the downlink direction across the GTP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–36

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumGtpUpLinkDataPacketsRcvd

sgsnNumGtpUpLinkDataPacketsRcvd
Description
This statistic indicates the total number of data packets received in the uplink direction (from SNDCP protocol layer).

Pegging
The statistic is pegged each time the GTP protocol layer receives a data packet from the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumGtpDataPacketsSentToGGSN to show the SGSN data packet throughput in the uplink direction across the GTP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–37

sgsnNumGtpUpLinkDataBytesRcvd

ISSUE 1 REVISION 2

sgsnNumGtpUpLinkDataBytesRcvd
Description
This Gn statistic indicates the total number of data bytes (including protocol headers) received in the uplink direction (from SNDCP protocol layer).

Pegging
The statistic is pegged each time the GTP protocol layer receives a data byte from the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumGtpDataBytesSentToGGSN to show the SGSN data byte throughput in the uplink direction across the GTP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–38

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumGtpUpLinkDataPacketsDropped

sgsnNumGtpUpLinkDataPacketsDropped
Description
This statistic indicates the total number of data packets dropped in the uplink direction.

Pegging
The statistic is pegged each time the GTP protocol layer drops a data packet received from the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with GTP uplink throughput statistics to identify uplink loss rates across the GTP protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–39

sgsnNumGtpDownLinkDataPacketsDropped

ISSUE 1 REVISION 2

sgsnNumGtpDownLinkDataPacketsDropped
Description
This statistic indicates the total number of data packets dropped in the downlink direction.

Pegging
The statistic is pegged each time the GTP protocol layer drops a data packet received from the GGSN.

Analysis
The statistic can be used in conjunction with GTP downlink throughput statistics to identify downlink loss rates across the GTP protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–40

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumSndcpUpLinkDataPacketsSent

sgsnNumSndcpUpLinkDataPacketsSent
Description
This statistic indicates the total number of SNDCP data packets sent to the GTP protocol layer.

Pegging
The statistic is pegged each time the SNDCP protocol layer sends a data packet to the GTP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumSndcpUpLinkDataPacketsRcvd to show the SGSN data packet throughput in the uplink direction across the SNDCP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
SNDCP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–41

sgsnNumSndcpUpLinkDataBytesSent

ISSUE 1 REVISION 2

sgsnNumSndcpUpLinkDataBytesSent
Description
This statistic indicates the total number of SNDCP data bytes (including protocol headers) sent to the GTP protocol layer.

Pegging
The statistic is pegged each time the SNDCP protocol layer sends a data byte to the GTP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumSndcpUpLinkDataBytesRcvd to show the SGSN data byte throughput in the uplink direction across the SNDCP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
SNDCP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–42

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumSndcpDownLinkDataPacketsRcvd

sgsnNumSndcpDownLinkDataPacketsRcvd
Description
This statistic indicates the total number of SNDCP data packets received from the GTP protocol layer.

Pegging
The statistic is pegged each time the SNDCP protocol layer receives a data packet from the GTP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumSndcpDownLinkDataPackets Sent to show the SGSN data packet throughput in the downlink direction across the SNDCP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
SNDCP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–43

sgsnNumSndcpDownLinkDataBytesRcvd

ISSUE 1 REVISION 2

sgsnNumSndcpDownLinkDataBytesRcvd
Description
This statistic indicates the total number of SNDCP data bytes (including protocol headers) received from the GTP protocol layer.

Pegging
The statistic is pegged each time the SNDCP protocol layer receives a data byte from the GTP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumSndcpDownLinkDataBytesSent to show the SGSN data byte throughput in the downlink direction across the SNDCP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
SNDCP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–44

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumSndcpDownLinkDataPacketsSent

sgsnNumSndcpDownLinkDataPacketsSent
Description
This statistic indicates the total number of SNDCP data packets sent to the LLC protocol layer.

Pegging
The statistic is pegged each time the SNDCP protocol layer sends a data packet to the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumSndcpDownLinkDataPackets Rcvd to show the SGSN data packet throughput in the downlink direction across the SNDCP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
SNDCP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–45

sgsnNumSndcpDownLinkDataBytesSent

ISSUE 1 REVISION 2

sgsnNumSndcpDownLinkDataBytesSent
Description
This statistic indicates the total number of SNDCP data bytes (including protocol headers) sent to the LLC protocol layer.

Pegging
The statistic is pegged each time the SNDCP protocol layer sends a data byte to the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumSndcpDownLinkDataBytes Rcvd to show the SGSN data packet throughput in the downlink direction across the SNDCP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
SNDCP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–46

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumSndcpUpLinkDataPacketsRcvd

sgsnNumSndcpUpLinkDataPacketsRcvd
Description
This statistic indicates the total number of SNDCP data packets received from the LLC protocol layer.

Pegging
The statistic is pegged each time the SNDCP protocol layer receives a data packet from the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumSndcpUpLinkDataPacketsSent to show the SGSN data packet throughput in the uplink direction across the SNDCP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
SNDCP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–47

sgsnNumSndcpUpLinkDataBytesRcvd

ISSUE 1 REVISION 2

sgsnNumSndcpUpLinkDataBytesRcvd
Description
This statistic indicates the total number of SNDCP data bytes (including protocol headers) received from the LLC protocol layer.

Pegging
The statistic is pegged each time the SNDCP protocol layer receives a data byte from the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumSndcpUpLinkDataBytesSent to show the SGSN data packet throughput in the uplink direction across the SNDCP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
SNDCP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–48

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumSndcpUpLinkDataPacketsDropped

sgsnNumSndcpUpLinkDataPacketsDropped
Description
This statistic indicates the total number of SNDCP data packets dropped in the uplink direction.

Pegging
The statistic is pegged each time the SNDCP protocol layer drops a data packet received from the LLC protocol layer.

Analysis
The statistic can be used in conjunction with SNDCP uplink throughput statistics to identify uplink loss rates across the SNDCP protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
SNDCP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–49

sgsnNumSndcpDownLinkDataPacketsDropped

ISSUE 1 REVISION 2

sgsnNumSndcpDownLinkDataPacketsDropped
Description
This statistic indicates the total number of SNDCP data packets dropped in the downlink direction.

Pegging
The statistic is pegged each time the SNDCP protocol layer drops a data packet received from the GTP protocol layer.

Analysis
The statistic can be used in conjunction with SNDCP downlink throughput statistics to identify downlink loss rates across the SNDCP protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
SNDCP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–50

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcDownLinkDataPacketsSent

sgsnNumLlcDownLinkDataPacketsSent
Description
This statistic indicates the total number of LLC data packets sent to the BSSGP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer sends a data packet to the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcDownLinkDataPacketsRcvd to show the SGSN data packet throughput in the downlink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–51

sgsnNumLlcDownLinkDataBytesSent

ISSUE 1 REVISION 2

sgsnNumLlcDownLinkDataBytesSent
Description
This statistic indicates the total number of LLC data bytes (including protocol headers) sent to the BSSGP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer sends a data byte to the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcDownLinkDataBytesRcvd to show the SGSN data byte throughput in the downlink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–52

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcUpLinkDataPacketsRcvd

sgsnNumLlcUpLinkDataPacketsRcvd
Description
This statistic indicates the total number of LLC data packets received from the BSSGP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer receives a data packet from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcUpLinkDataPacketsSent to show the SGSN data packet throughput in the uplink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–53

sgsnNumLlcUpLinkDataBytesRcvd

ISSUE 1 REVISION 2

sgsnNumLlcUpLinkDataBytesRcvd
Description
This statistic indicates the total number of LLC data bytes (including protocol headers) received from the BSSGP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer receives a data byte from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcUpLinkDataBytesSent to show the SGSN data byte throughput in the uplink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–54

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcDownLinkSignalPacketsSent

sgsnNumLlcDownLinkSignalPacketsSent
Description
This statistic indicates the total number of LLC signalling packets sent to the BSSGP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer sends a signalling packet to the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcDownLinkSignalPackets Rcvd to show the SGSN signal packet throughput in the downlink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–55

sgsnNumLlcDownLinkSignalBytesSent

ISSUE 1 REVISION 2

sgsnNumLlcDownLinkSignalBytesSent
Description
This statistic indicates the total number of LLC signalling bytes (including protocol headers) sent to the BSSGP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer sends a signalling byte to the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcDownLinkSignalBytesRcvd to show the SGSN signalling byte throughput in the downlink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–56

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcUpLinkSignalPacketsRcvd

sgsnNumLlcUpLinkSignalPacketsRcvd
Description
This statistic indicates the total number of LLC signalling packets received from the BSSGP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer receives a signalling packet from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcUpLinkSignalPacketsSent to show the SGSN signalling packet throughput in the uplink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–57

sgsnNumLlcUpLinkSignalBytesRcvd

ISSUE 1 REVISION 2

sgsnNumLlcUpLinkSignalBytesRcvd
Description
This statistic indicates the total number of LLC signalling bytes (including protocol headers) received from the BSSGP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer receives a signalling byte from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcUpLinkSignalBytesSent to show the SGSN signalling byte throughput in the uplink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–58

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcUpLinkDataPacketsSent

sgsnNumLlcUpLinkDataPacketsSent
Description
This statistic indicates the total number of LLC data packets sent to the SNDCP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer sends a data packet to the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcUpLinkDataPacketsRcvd to show the SGSN data packet throughput in the Uplink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–59

sgsnNumLlcUpLinkDataBytesSent

ISSUE 1 REVISION 2

sgsnNumLlcUpLinkDataBytesSent
Description
This statistic indicates the total number of LLC data bytes (including protocol headers) sent to the SNDCP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer sends a data byte to the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcUpLinkDataBytesRcvd to show the SGSN data byte throughput in the Uplink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–60

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcDownLinkDataPacketsRcvd

sgsnNumLlcDownLinkDataPacketsRcvd
Description
This statistic indicates the total number of LLC data packets received from the SNDCP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer receives a data packet from the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcDownLinkDataPacketsSent to show the SGSN data packet throughput in the downlink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–61

sgsnNumLlcDownLinkDataBytesRcvd

ISSUE 1 REVISION 2

sgsnNumLlcDownLinkDataBytesRcvd
Description
This statistic indicates the total number of LLC data bytes (including protocol headers) received from the SNDCP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer receives a data byte from the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcDownLinkDataBytesSent to show the SGSN data byte throughput in the downlink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–62

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcUpLinkSignalPacketsSent

sgsnNumLlcUpLinkSignalPacketsSent
Description
This statistic indicates the total number of LLC signalling packets sent to the SNDCP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer sends a signalling packet to the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcUpLinkSignalPacketsRcvd to show the SGSN signal packet throughput in the uplink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–63

sgsnNumLlcUpLinkSignalBytesSent

ISSUE 1 REVISION 2

sgsnNumLlcUpLinkSignalBytesSent
Description
This statistic indicates the total number of LLC signalling bytes (including protocol headers) sent to the SNDCP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer sends a signalling byte to the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcUpLinkSignalBytesRcvd to show the SGSN signalling byte throughput in the uplink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–64

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcDownLinkSignalPacketsRcvd

sgsnNumLlcDownLinkSignalPacketsRcvd
Description
This statistic indicates the total number of LLC signalling packets received from the SNDCP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer receives a signalling packet from the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcDownLinkSignalPackets Sent to show the SGSN signalling packet throughput in the downlink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–65

sgsnNumLlcDownLinkSignalBytesRcvd

ISSUE 1 REVISION 2

sgsnNumLlcDownLinkSignalBytesRcvd
Description
This statistic indicates the total number of LLC signalling bytes (including protocol headers) received from the SNDCP protocol layer.

Pegging
The statistic is pegged each time the LLC protocol layer receives a signalling byte from the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumLlcDownLinkSignalBytesSent to show the SGSN signalling byte throughput in the downlink direction across the LLC protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–66

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcUpLinkDataPacketsDropped

sgsnNumLlcUpLinkDataPacketsDropped
Description
This statistic indicates the total number of LLC data packets dropped in the uplink direction.

Pegging
The statistic is pegged each time the LLC protocol layer drops a data packet received from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with LLC uplink data throughput statistics to identify uplink data loss rates across the LLC protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–67

sgsnNumLlcDownLinkDataPacketsDropped

ISSUE 1 REVISION 2

sgsnNumLlcDownLinkDataPacketsDropped
Description
This statistic indicates the total number of LLC data packets dropped in the downlink direction.

Pegging
The statistic is pegged each time the LLC protocol layer drops a data packet received from the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with LLC downlink data throughput statistics to identify downlink data loss rates across the LLC protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–68

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcUpLinkSignalPacketsDropped

sgsnNumLlcUpLinkSignalPacketsDropped
Description
This statistic indicates the total number of LLC signalling packets dropped in the uplink direction.

Pegging
The statistic is pegged each time the LLC protocol layer drops a signalling packet received from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with LLC uplink signalling throughput statistics to identify uplink signalling loss rates across the LLC protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–69

sgsnNumLlcDownLinkSignalPacketsDropped

ISSUE 1 REVISION 2

sgsnNumLlcDownLinkSignalPacketsDropped
Description
This statistic indicates the total number of LLC signalling packets dropped in the downlink direction.

Pegging
The statistic is pegged each time the LLC protocol layer drops a signalling packet received from the SNDCP protocol layer.

Analysis
The statistic can be used in conjunction with LLC downlink signalling throughput statistics to identify downlink signalling loss rates across the LLC protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–70

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumLlcPacketsResent

sgsnNumLlcPacketsResent
Description
This statistic indicates the total number of LLC packets resent.

Pegging

Analysis

Reference

Usage

Basis
LLC

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–71

sgsnNumBssgpDownLinkDataPacketsSent

ISSUE 1 REVISION 2

sgsnNumBssgpDownLinkDataPacketsSent
Description
This BSSGP attribute indicates the total number of BSSGP data packets sent to the NS protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer sends a data packet to the NS protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpDownLinkDataPackets Rcvd to show the SGSN data packet throughput in the downlink direction across the BSSGP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–72

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumBssgpDownLinkDataBytesSent

sgsnNumBssgpDownLinkDataBytesSent
Description
This BSSGP attribute indicates the total number of BSSGP data bytes (including protocol headers) sent to the NS protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer sends a data byte to the NS protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpDownLinkDataBytes Rcvd to show the SGSN data byte throughput in the downlink direction across the BSSGP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–73

sgsnNumBssgpUpLinkDataPacketsRcvd

ISSUE 1 REVISION 2

sgsnNumBssgpUpLinkDataPacketsRcvd
Description
This BSSGP attribute indicates the total number of BSSGP data packets received from NS protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer receives a data packet from the NS protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpUpLinkDataPacketsSent to show the SGSN data packet throughput in the uplink direction across the BSSGP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–74

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumBssgpUpLinkDataBytesRcvd

sgsnNumBssgpUpLinkDataBytesRcvd
Description
This BSSGP attribute indicates the total number of BSSGP data bytes (including protocol headers) received from NS protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer receives a data byte from the NS protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpUpLinkDataBytesSent to show the SGSN data byte throughput in the uplink direction across the BSSGP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–75

sgsnNumBssgpUpLinkDataPacketsSent

ISSUE 1 REVISION 2

sgsnNumBssgpUpLinkDataPacketsSent
Description
This BSSGP attribute indicates the total number of BSSGP data packets sent to the LLC protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer sends a data packet to the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpUpLinkDataPacketsRcvd to show the SGSN data packet throughput in the uplink direction across the BSSGP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–76

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumBssgpUpLinkDataBytesSent

sgsnNumBssgpUpLinkDataBytesSent
Description
This BSSGP attribute indicates the total number of BSSGP data bytes (including protocol headers) sent to the LLC protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer sends a data byte to the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpUpLinkDataBytesRcvd to show the SGSN data byte throughput in the uplink direction across the BSSGP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–77

sgsnNumBssgpDownLinkDataPacketsRcvd

ISSUE 1 REVISION 2

sgsnNumBssgpDownLinkDataPacketsRcvd
Description
This BSSGP attribute indicates the total number of BSSGP data packets received from the LLC protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer receives a data packet from the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpDownLinkDataPackets Sent to show the SGSN data packet throughput in the downlink direction across the BSSGP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–78

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumBssgpDownLinkDataBytesRcvd

sgsnNumBssgpDownLinkDataBytesRcvd
Description
This BSSGP attribute indicates the total number of BSSGP data bytes (including protocol headers) received from the LLC protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer receives a data byte from the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpDownLinkDataBytesSent to show the SGSN data byte throughput in the downlink direction across the BSSGP protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–79

sgsnNumBssgpUpLinkDataPacketsDropped

ISSUE 1 REVISION 2

sgsnNumBssgpUpLinkDataPacketsDropped
Description
This BSSGP attribute indicates the total number of BSSGP data packets dropped in the uplink direction.

Pegging
The statistic is pegged each time the BSSGP protocol layer drops a data packet received from the NS protocol layer.

Analysis
The statistic can be used in conjunction with BSSGP uplink throughput statistics to identify uplink loss rates across the BSSGP protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–80

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumBssgpDownLinkDataPacketsDropped

sgsnNumBssgpDownLinkDataPacketsDropped
Description
This BSSGP attribute indicates the total number of BSSGP data packets dropped in the downlink direction.

Pegging
The statistic is pegged each time the BSSGP protocol layer drops a data packet received from the LLC protocol layer.

Analysis
The statistic can be used in conjunction with BSSGP downlink throughput statistics to identify downlink loss rates across the BSSGP protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–81

sgsnNumNsDownLinkDataPacketsRcvd

ISSUE 1 REVISION 2

sgsnNumNsDownLinkDataPacketsRcvd
Description
This statistic indicates the total number of NS data packets received from the BSSGP protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer receives a data packet from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsDownLinkDataPacketsSent to show the SGSN data packet throughput in the downlink direction across the NS protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–82

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumNsDownLinkDataBytesRcvd

sgsnNumNsDownLinkDataBytesRcvd
Description
This statistic indicates the total number of NS data bytes (including protocol headers) received from the BSSGP protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer receives a data byte from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsDownLinkDataBytesSent to show the SGSN data byte throughput in the downlink direction across the NS protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–83

sgsnNumNsUpLinkDataPacketsSent

ISSUE 1 REVISION 2

sgsnNumNsUpLinkDataPacketsSent
Description
This statistic indicates the total number of NS data packets sent to the BSSGP protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer sends a data packet to the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsUpLinkDataPacketsRcvd to show the SGSN data packet throughput in the uplink direction across the NS protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–84

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumNsUpLinkDataBytesSent

sgsnNumNsUpLinkDataBytesSent
Description
This statistic indicates the total number of NS data bytes (including protocol headers) sent to the BSSGP protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer sends a data byte to the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsUpLinkDataBytesRcvd to show the SGSN data byte throughput in the uplink direction across the NS protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–85

sgsnNumNsUpLinkDataPacketsRcvd

ISSUE 1 REVISION 2

sgsnNumNsUpLinkDataPacketsRcvd
Description
This statistic indicates the total number of NS data packets received from the FR protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer receives a data packet from the FR protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsUpLinkDataPacketsSent to show the SGSN data packet throughput in the uplink direction across the NS protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–86

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumNsUpLinkDataBytesRcvd

sgsnNumNsUpLinkDataBytesRcvd
Description
This statistic indicates the total number of NS data bytes (including protocol headers) received from the FR protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer receives a data byte from the FR protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsUpLinkDataBytesSent to show the SGSN data byte throughput in the uplink direction across the NS protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–87

sgsnNumNsDownLinkDataPacketsSent

ISSUE 1 REVISION 2

sgsnNumNsDownLinkDataPacketsSent
Description
This statistic indicates the total number of NS data packets sent to the FR protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer sends a data packet to the FR protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsDownLinkDataPacketsRcvd to show the SGSN data packet throughput in the downlink direction across the NS protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–88

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumNsDownLinkDataBytesSent

sgsnNumNsDownLinkDataBytesSent
Description
This statistic indicates the total number of NS data bytes (including protocol headers) sent to the FR protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer sends a data byte to the FR protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsDownLinkDataBytesRcvd to show the SGSN data byte throughput in the downlink direction across the NS protocol layer.

Reference

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–89

sgsnNumNsUpLinkDataPacketsDropped

ISSUE 1 REVISION 2

sgsnNumNsUpLinkDataPacketsDropped
Description
This statistic indicates the total number of NS data packets dropped in the uplink direction.

Pegging
The statistic is pegged each time the NS protocol layer drops a data packet received from the FR protocol layer.

Analysis
The statistic can be used in conjunction with NS uplink throughput statistics to identify uplink loss rates across the NS protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–90

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumNsDownLinkDataPacketsDropped

sgsnNumNsDownLinkDataPacketsDropped
Description
This statistic indicates the total number of NS data packets dropped in the downlink direction.

Pegging
The statistic is pegged each time the NS protocol layer drops a data packet received from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with NS downlink throughput statistics to identify downlink loss rates across the NS protocol layer.

Reference

Usage
Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–91

sgsnNumL3mmAttachReqRcvd

ISSUE 1 REVISION 2

sgsnNumL3mmAttachReqRcvd
Description
This statistic indicates the total number of L3MM Attach Requests received.

Pegging
The statistic is pegged when the SGSN receives an Attach Request from a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–92

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmAttachAcceptSent

sgsnNumL3mmAttachAcceptSent
Description
This statistic indicates the total number of L3MM Attach Accepts sent.

Pegging
The statistic is pegged when the SGSN sends an Attach Accept to a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–93

sgsnNumL3mmAttachRejectSent

ISSUE 1 REVISION 2

sgsnNumL3mmAttachRejectSent
Description
This statistic indicates the total number of L3MM Attach Rejects sent.

Pegging
The statistic is pegged when the SGSN sends an Attach Reject to a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–94

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmDetachReqRcvd

sgsnNumL3mmDetachReqRcvd
Description
This statistic indicates the total number of L3MM Detach Requests received.

Pegging
The statistic is pegged when the SGSN receives a Detach Request from a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–95

sgsnNumL3mmDetachAcceptSent

ISSUE 1 REVISION 2

sgsnNumL3mmDetachAcceptSent
Description
This statistic indicates the total number of L3MM Detach Accepts sent.

Pegging
The statistic is pegged when the SGSN sends a Detach Request to a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–96

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmSessionActivateReqRcvd

sgsnNumL3mmSessionActivateReqRcvd
Description
This statistic indicates the total number of L3MM Session Activate requests received.

Pegging
The statistic is pegged when the SGSN receives a Session Activation Request from a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–97

sgsnNumL3mmSessionActivateAcceptSent

ISSUE 1 REVISION 2

sgsnNumL3mmSessionActivateAcceptSent
Description
This statistic indicates the total number of L3MM Session Activate accepts sent.

Pegging
The statistic is pegged when the SGSN sends a Session Activation Accept to a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–98

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmSessionActivateRejectSent

sgsnNumL3mmSessionActivateRejectSent
Description
This statistic indicates the total number of L3MM Session Activate rejects sent.

Pegging
The statistic is pegged when the SGSN sends a Session Activation Reject to a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–99

sgsnNumL3mmSessionDeactivateReqRcvd

ISSUE 1 REVISION 2

sgsnNumL3mmSessionDeactivateReqRcvd
Description
This statistic indicates the total number of L3MM Session Deactivate requests received.

Pegging
The statistic is pegged when the SGSN receives a Session Deactivation Request from a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–100

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmSessionDeactivateAcceptSent

sgsnNumL3mmSessionDeactivateAcceptSent
Description
This statistic indicates the total number of L3MM Session Deactivate accepts sent.

Pegging
The statistic is pegged when the SGSN sends a Session Deactivation Accept to a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–101

sgsnNumL3mmRaUpdateReqRcvd

ISSUE 1 REVISION 2

sgsnNumL3mmRaUpdateReqRcvd
Description
This statistic indicates the total number of L3MM RA Update requests received.

Pegging
The statistic is pegged when the SGSN receives a RA Update Request from a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–102

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmRaUpdateAcceptSent

sgsnNumL3mmRaUpdateAcceptSent
Description
This statistic indicates the total number of L3MM RA Update accepts sent.

Pegging
The statistic is pegged when the SGSN sends a RA Update Accept to a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–103

sgsnNumL3mmRaUpdateRejectSent

ISSUE 1 REVISION 2

sgsnNumL3mmRaUpdateRejectSent
Description
This statistic indicates the total number of L3MM RA Update rejects sent.

Pegging
The statistic is pegged when the SGSN sends a RA Update Reject to a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–104

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmMsPagingReqSent

sgsnNumL3mmMsPagingReqSent
Description
This statistic indicates the total number of L3MM MS paging requests sent (not the number of paging PCUs, in case a page request needs to be sent to multiple PCUs).

Pegging
The statistic is pegged when the SGSN sends a MS Paging Request to a MS.

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–105

sgsnNumL3mmSuccessfulPages

ISSUE 1 REVISION 2

sgsnNumL3mmSuccessfulPages
Description
This statistic indicates the total number of successful pages (where the paged MS is successfully located).

Pegging

Analysis

Reference

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–106

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnCurrentNumGprsAttachedMS

sgsnCurrentNumGprsAttachedMS
Description
This statistic indicates the current number of GPRS attached MS.

Pegging

Analysis

Reference

Usage
Network Planning Congestion Identification

Basis
Miscellaneous

Statistic
Statistic Type
Gauge

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–107

sgsnCurrentNumActivePdpSession

ISSUE 1 REVISION 2

sgsnCurrentNumActivePdpSession
Description
This statistic indicates the current number of active PDP sessions.

Pegging

Analysis

Reference

Usage
Network Planning Congestion Identification

Basis
Miscellaneous

Statistic
Statistic Type
Gauge

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–108

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumCells

sgsnNumCells
Description
This statistic indicates the total number of cells.

Pegging

Analysis

Reference

Usage
Network Planning Congestion Identification

Basis
Miscellaneous

Statistic
Statistic Type
Gauge

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–109

sgsnNumCells

ISSUE 1 REVISION 2

7–110

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumBssgpDownLinkDataPacketsSent

sgsnNumBssgpDownLinkDataPacketsSent
Description
This BSSGP attribute indicates the total number of BSSGP data packets sent to the NS protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer sends a data packet to the NS protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpDownLinkDataPackets Rcvd to show the SGSN data packet throughput in the downlink direction across the BSSGP protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–111

sgsnNumBssgpDownLinkDataBytesSent

ISSUE 1 REVISION 2

sgsnNumBssgpDownLinkDataBytesSent
Description
This BSSGP attribute indicates the total number of BSSGP data bytes (including protocol headers) sent to the NS protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer sends a data byte to the NS protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpDownLinkDataBytes Rcvd to show the SGSN data byte throughput in the downlink direction across the BSSGP protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–112

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumBssgpUpLinkDataPacketsRcvd

sgsnNumBssgpUpLinkDataPacketsRcvd
Description
This BSSGP attribute indicates the total number of BSSGP data packets received from NS protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer receives a data packet from the NS protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpUpLinkDataPacketsSent to show the SGSN data packet throughput in the uplink direction across the BSSGP protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–113

sgsnNumBssgpUpLinkDataBytesRcvd

ISSUE 1 REVISION 2

sgsnNumBssgpUpLinkDataBytesRcvd
Description
This BSSGP attribute indicates the total number of BSSGP data bytes (including protocol headers) received from NS protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer receives a data byte from the NS protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpUpLinkDataBytesSent to show the SGSN data byte throughput in the uplink direction across the BSSGP protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–114

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumBssgpUpLinkDataPacketsSent

sgsnNumBssgpUpLinkDataPacketsSent
Description
This BSSGP attribute indicates the total number of BSSGP data packets sent to the LLC protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer sends a data packet to the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpUpLinkDataPacketsRcvd to show the SGSN data packet throughput in the uplink direction across the BSSGP protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–115

sgsnNumBssgpUpLinkDataBytesSent

ISSUE 1 REVISION 2

sgsnNumBssgpUpLinkDataBytesSent
Description
This BSSGP attribute indicates the total number of BSSGP data bytes (including protocol headers) sent to the LLC protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer sends a data byte to the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpUpLinkDataBytesRcvd to show the SGSN data byte throughput in the uplink direction across the BSSGP protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–116

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumBssgpDownLinkDataPacketsRcvd

sgsnNumBssgpDownLinkDataPacketsRcvd
Description
This BSSGP attribute indicates the total number of BSSGP data packets received from the LLC protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer receives a data packet from the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpDownLinkDataPackets Sent to show the SGSN data packet throughput in the downlink direction across the BSSGP protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–117

sgsnNumBssgpDownLinkDataBytesRcvd

ISSUE 1 REVISION 2

sgsnNumBssgpDownLinkDataBytesRcvd
Description
This BSSGP attribute indicates the total number of BSSGP data bytes (including protocol headers) received from the LLC protocol layer.

Pegging
The statistic is pegged each time the BSSGP protocol layer receives a data byte from the LLC protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumBssgpDownLinkDataBytesSent to show the SGSN data byte throughput in the downlink direction across the BSSGP protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–118

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumBssgpUpLinkDataPacketsDropped

sgsnNumBssgpUpLinkDataPacketsDropped
Description
This BSSGP attribute indicates the total number of BSSGP data packets dropped in the uplink direction.

Pegging
The statistic is pegged each time the BSSGP protocol layer drops a data packet received from the NS protocol layer.

Analysis
The statistic can be used in conjunction with BSSGP uplink throughput statistics to identify uplink loss rates across the BSSGP protocol layer.

Reference
?

Usage
Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–119

sgsnNumBssgpDownLinkDataPacketsDropped

ISSUE 1 REVISION 2

sgsnNumBssgpDownLinkDataPacketsDropped
Description
This BSSGP attribute indicates the total number of BSSGP data packets dropped in the downlink direction.

Pegging
The statistic is pegged each time the BSSGP protocol layer drops a data packet received from the LLC protocol layer.

Analysis
The statistic can be used in conjunction with BSSGP downlink throughput statistics to identify downlink loss rates across the BSSGP protocol layer.

Reference
?

Usage
Loss Rates Fault Finding

Basis
BSSGP

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–120

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumNsDownLinkDataPacketsRcvd

sgsnNumNsDownLinkDataPacketsRcvd
Description
This statistic indicates the total number of NS data packets received from the BSSGP protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer receives a data packet from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsDownLinkDataPacketsSent to show the SGSN data packet throughput in the downlink direction across the NS protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–121

sgsnNumNsDownLinkDataBytesRcvd

ISSUE 1 REVISION 2

sgsnNumNsDownLinkDataBytesRcvd
Description
This statistic indicates the total number of NS data bytes (including protocol headers) received from the BSSGP protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer receives a data byte from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsDownLinkDataBytesSent to show the SGSN data byte throughput in the downlink direction across the NS protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–122

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumNsUpLinkDataPacketsSent

sgsnNumNsUpLinkDataPacketsSent
Description
This statistic indicates the total number of NS data packets sent to the BSSGP protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer sends a data packet to the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsUpLinkDataPacketsRcvd to show the SGSN data packet throughput in the uplink direction across the NS protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–123

sgsnNumNsUpLinkDataBytesSent

ISSUE 1 REVISION 2

sgsnNumNsUpLinkDataBytesSent
Description
This statistic indicates the total number of NS data bytes (including protocol headers) sent to the BSSGP protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer sends a data byte to the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsUpLinkDataBytesRcvd to show the SGSN data byte throughput in the uplink direction across the NS protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–124

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumNsUpLinkDataPacketsRcvd

sgsnNumNsUpLinkDataPacketsRcvd
Description
This statistic indicates the total number of NS data packets received from the FR protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer receives a data packet from the FR protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsUpLinkDataPacketsSent to show the SGSN data packet throughput in the uplink direction across the NS protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–125

sgsnNumNsUpLinkDataBytesRcvd

ISSUE 1 REVISION 2

sgsnNumNsUpLinkDataBytesRcvd
Description
This statistic indicates the total number of NS data bytes (including protocol headers) received from the FR protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer receives a data byte from the FR protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsUpLinkDataBytesSent to show the SGSN data byte throughput in the uplink direction across the NS protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–126

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumNsDownLinkDataPacketsSent

sgsnNumNsDownLinkDataPacketsSent
Description
This statistic indicates the total number of NS data packets sent to the FR protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer sends a data packet to the FR protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsDownLinkDataPacketsRcvd to show the SGSN data packet throughput in the downlink direction across the NS protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–127

sgsnNumNsDownLinkDataBytesSent

ISSUE 1 REVISION 2

sgsnNumNsDownLinkDataBytesSent
Description
This statistic indicates the total number of NS data bytes (including protocol headers) sent to the FR protocol layer.

Pegging
The statistic is pegged each time the NS protocol layer sends a data byte to the FR protocol layer.

Analysis
The statistic can be used in conjunction with sgsnNumNsDownLinkDataBytesRcvd to show the SGSN data byte throughput in the downlink direction across the NS protocol layer.

Reference
?

Usage
Network Planning Congestion Identification Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–128

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumNsUpLinkDataPacketsDropped

sgsnNumNsUpLinkDataPacketsDropped
Description
This statistic indicates the total number of NS data packets dropped in the uplink direction.

Pegging
The statistic is pegged each time the NS protocol layer drops a data packet received from the FR protocol layer.

Analysis
The statistic can be used in conjunction with NS uplink throughput statistics to identify uplink loss rates across the NS protocol layer.

Reference
?

Usage
Loss Rates Fault Finding

Basis
NS

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–129

sgsnNumNsDownLinkDataPacketsDropped

ISSUE 1 REVISION 2

sgsnNumNsDownLinkDataPacketsDropped
Description
This statistic indicates the total number of NS data packets dropped in the downlink direction.

Pegging
The statistic is pegged each time the NS protocol layer drops a data packet received from the BSSGP protocol layer.

Analysis
The statistic can be used in conjunction with NS downlink throughput statistics to identify downlink loss rates across the NS protocol layer.

Reference
?

Usage
Loss Rates Fault Finding

Basis
GTP Gn

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–130

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

FR stats

FR stats
Details of Fr statistics attributes not available at this time.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–131

sgsnNumL3mmAttachReqRcvd

ISSUE 1 REVISION 2

sgsnNumL3mmAttachReqRcvd
Description
This statistic indicates the total number of L3MM Attach Requests received.

Pegging
The statistic is pegged when the SGSN receives an Attach Request from a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–132

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmAttachAcceptSent

sgsnNumL3mmAttachAcceptSent
Description
This statistic indicates the total number of L3MM Attach Accepts sent.

Pegging
The statistic is pegged when the SGSN sends an Attach Accept to a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–133

sgsnNumL3mmAttachRejectSent

ISSUE 1 REVISION 2

sgsnNumL3mmAttachRejectSent
Description
This statistic indicates the total number of L3MM Attach Rejects sent.

Pegging
The statistic is pegged when the SGSN sends an Attach Reject to a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–134

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmDetachReqRcvd

sgsnNumL3mmDetachReqRcvd
Description
This statistic indicates the total number of L3MM Detach Requests received.

Pegging
The statistic is pegged when the SGSN receives a Detach Request from a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–135

sgsnNumL3mmDetachAcceptSent

ISSUE 1 REVISION 2

sgsnNumL3mmDetachAcceptSent
Description
This statistic indicates the total number of L3MM Detach Accepts sent.

Pegging
The statistic is pegged when the SGSN sends a Detach Request to a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–136

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmSessionActivateReqRcvd

sgsnNumL3mmSessionActivateReqRcvd
Description
This statistic indicates the total number of L3MM Session Activate requests received.

Pegging
The statistic is pegged when the SGSN receives a Session Activation Request from a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–137

sgsnNumL3mmSessionActivateAcceptSent

ISSUE 1 REVISION 2

sgsnNumL3mmSessionActivateAcceptSent
Description
This statistic indicates the total number of L3MM Session Activate accepts sent.

Pegging
The statistic is pegged when the SGSN sends a Session Activation Accept to a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–138

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmSessionActivateRejectSent

sgsnNumL3mmSessionActivateRejectSent
Description
This statistic indicates the total number of L3MM Session Activate rejects sent.

Pegging
The statistic is pegged when the SGSN sends a Session Activation Reject to a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–139

sgsnNumL3mmSessionDeactivateReqRcvd

ISSUE 1 REVISION 2

sgsnNumL3mmSessionDeactivateReqRcvd
Description
This statistic indicates the total number of L3MM Session Deactivate requests received.

Pegging
The statistic is pegged when the SGSN receives a Session Deactivation Request from a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–140

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmSessionDeactivateAcceptSent

sgsnNumL3mmSessionDeactivateAcceptSent
Description
This statistic indicates the total number of L3MM Session Deactivate accepts sent.

Pegging
The statistic is pegged when the SGSN sends a Session Deactivation Accept to a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–141

sgsnNumL3mmRaUpdateReqRcvd

ISSUE 1 REVISION 2

sgsnNumL3mmRaUpdateReqRcvd
Description
This statistic indicates the total number of L3MM RA Update requests received.

Pegging
The statistic is pegged when the SGSN receives a RA Update Request from a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–142

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmRaUpdateAcceptSent

sgsnNumL3mmRaUpdateAcceptSent
Description
This statistic indicates the total number of L3MM RA Update accepts sent.

Pegging
The statistic is pegged when the SGSN sends a RA Update Accept to a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–143

sgsnNumL3mmRaUpdateRejectSent

ISSUE 1 REVISION 2

sgsnNumL3mmRaUpdateRejectSent
Description
This statistic indicates the total number of L3MM RA Update rejects sent.

Pegging
The statistic is pegged when the SGSN sends a RA Update Reject to a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–144

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumL3mmMsPagingReqSent

sgsnNumL3mmMsPagingReqSent
Description
This statistic indicates the total number of L3MM MS paging requests sent (not the number of paging PCUs, in case a page request needs to be sent to multiple PCUs).

Pegging
The statistic is pegged when the SGSN sends a MS Paging Request to a MS.

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–145

sgsnNumL3mmSuccessfulPages

ISSUE 1 REVISION 2

sgsnNumL3mmSuccessfulPages
Description
This statistic indicates the total number of successful pages (where the paged MS is successfully located).

Pegging
?

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification Quality of Service Issues

Basis
L3MM

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–146

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnCurrentNumGprsAttachedMS

sgsnCurrentNumGprsAttachedMS
Description
This statistic indicates the current number of GPRS attached MS.

Pegging
?

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification

Basis
Miscellaneous

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–147

sgsnCurrentNumActivePdpSession

ISSUE 1 REVISION 2

sgsnCurrentNumActivePdpSession
Description
This statistic indicates the current number of active PDP sessions.

Pegging
?

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification

Basis
Miscellaneous

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

7–148

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

sgsnNumCells

sgsnNumCells
Description
This statistic indicates the total number of cells.

Pegging
?

Analysis
?

Reference
?

Usage
Network Planning Congestion Identification

Basis
Miscellaneous

Statistic
Statistic Type
Counter

Statistic Data
Integer ( 0 - 4,294,967,295 )

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

7–149

sgsnNumCells

ISSUE 1 REVISION 2

7–150

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 8

GGSN statistics attributes

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Chapter 3 GGSN statistics attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction to Cisco GGSN statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this chapter is structured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GGSN OID structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attributes Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpCurRxPacketQueueSize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpCurActivatedPDPcontextsCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpCurUnexpectedRxGpduCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpCurRejectedPDPContextActivationCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpTotalPktsDropped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpDroppedPktsTimeFrame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpDroppedPktsCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpCurMeanThroughputForPremiumQos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpCurMeanThroughputForNormalQos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpCurMeanThroughputForBestEffortQos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpCurGSNBandwidthResourceUsed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpGSNTable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpGSNEntry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpGSNid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpGSNEchoFailedNotificationCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpTotalNumAllocIpAddr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpChargingMsgCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpLastGSNidNoRespToEcho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpGSNidOfLastUnexpectedPDPContext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpTIDOfLastUnexpectedPDPContext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpRejectReasonOfLastUnexpectedPDPContext . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpNumAllocIpAddrTable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpNumAllocIpAddrEntry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cgprsGtpNumAllocIpAddr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

i
3–1 3–1 3–1 3–2 3–2 3–5 3–6 3–7 3–8 3–9 3–10 3–11 3–12 3–13 3–14 3–15 3–16 3–18 3–19 3–20 3–21 3–22 3–23 3–24 3–25 3–26 3–27 3–28 3–29

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

iii

ISSUE 1 REVISION 2

iv

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Introduction to Cisco GGSN statistics

Introduction to Cisco GGSN statistics
Purpose of this chapter
This chapter describes statistical measurements generated by the Cisco GGSN element of the GSN, in response to monitored network and system events.

How this chapter is structured
This chapters contains SGSN statistics information, using the following structure to present that information: S S S S An introduction to the chapter and the chapter structure. Details of the MIB structure identifying the available SGSN objects. Attributes tables detailing the statistics attributes available for each SGSN object. Data sheets containing the attribute information of the individual statistics identified in the attributes tables. NOTE This information may be structured differently for training purposes

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–1

Introduction to Cisco GGSN statistics

ISSUE 1 REVISION 2

GGSN OID structure
The following illustration identifies the Cisco GGSN OID structure, with the emphasis on the performance management branch of the structure.
ciscoGprsGtp (1) Objects (1) Config

(2) Stats (1) General

(2) Ggsn

(2) Notifications

Figure 8-1 Cisco GGSN OID structure

Attributes Tables
Details of the attributes available for each performance management object can be found in the following tables: General General GSN table Ggsn Ggsn NumAllocIpAddr table Table 8-1 Table 8-2 Table 8-3

8–2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Introduction to Cisco GGSN statistics

Cisco GGSN General statistics
The following table details the statistics attributes available for cgprsGtpGeneralStats : Table 8-1 GGSN General statistics attributes OID number 1 2 3 4 5 6 7 8 9 10 11 attribute cgprsGtpCurRxPacketQueueSize cgprsGtpCurActivatedPDPcontextsCount cgprsGtpCurUnexpectedRxGpduCount cgprsGtpCurRejectedPDPContextActivationCount cgprsGtpTotalPktsDropped cgprsGtpDroppedPktsTimeFrame cgprsGtpDroppedPktsCount cgprsGtpCurMeanThroughputForPremiumQos cgprsGtpCurMeanThroughputForNormalQos cgprsGtpCurMeanThroughputForBestEffortQos cgprsGtpCurGSNBandwidthResourceUsed

Cisco GGSN General GSN table statistics
The following table details the statistics attributes available for cgprsGtpGeneralStats : Table 8-2 GGSN General GSN table statistics attributes OID number 1 2 cgprsGtpGSNid cgprsGtpGSNEchoFailedNotificationCount attribute

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–3

Introduction to Cisco GGSN statistics

ISSUE 1 REVISION 2

Cisco GGSN statistics
The following table details the statistics attributes available for cgprsGtpGgsnStats : Table 8-3 GGSN statistics attributes OID number 1 2 3 4 5 6 attribute cgprsGtpTotalNumAllocIpAddr cgprsGtpChargingMsgCount cgprsGtpLastGSNidNoRespToEcho cgprsGtpGSNidOfLastUnexpectedPDPContext cgprsGtpTIDOfLastUnexpectedPDPContext cgprsGtpRejectReasonOfLastUnexpectedPDPContext

Cisco GGSN NumAllocIpAddr table statistics
The following table details the statistics attributes available for cgprsGtpGgsnStats : Table 8-4 GGSN NumAllocIpAddr table statistics attributes OID number 1 attribute cgprsGtpNumAllocIpAddr

8–4

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpCurRxPacketQueueSize

cgprsGtpCurRxPacketQueueSize
Description
The current size of the Rx Packet Queue on the GSN node (for data received from the APN, on the Gi interface).

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Gauge 32

Statistic Data
packets

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–5

cgprsGtpCurActivatedPDPcontextsCount

ISSUE 1 REVISION 2

cgprsGtpCurActivatedPDPcontextsCount
Description
The current number of PDP contexts established on the GSN node.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Gauge 32

Statistic Data
PDP contexts

8–6

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpCurUnexpectedRxGpduCount

cgprsGtpCurUnexpectedRxGpduCount
Description
The total number of G–PDUs received from a SGSN for a non–existing or an inactive PDP context since system startup.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
PDUs

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–7

cgprsGtpCurRejectedPDPContextActivationCount

ISSUE 1 REVISION 2

cgprsGtpCurRejectedPDPContextActivationCount
Description
The total number of Rejected PDP Context activation, due to an overload or other abnormal conditions since system startup.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
PDP contexts

8–8

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpTotalPktsDropped

cgprsGtpTotalPktsDropped
Description
Total number of packets dropped due to unknown GTP header, since the system went up.

Pegging
?

Analysis
?

Reference
?

Usage

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
packets

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–9

cgprsGtpDroppedPktsTimeFrame

ISSUE 1 REVISION 2

cgprsGtpDroppedPktsTimeFrame
Description
The time frame within which the number of GTP packets, defined by cgprsGtpDroppedPktsCount, are dropped.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Integer

Statistic Data
( –2147483648..2147483647 )

8–10

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpDroppedPktsCount

cgprsGtpDroppedPktsCount
Description
The number of packets dropped by GTP within cgprsGtpDroppedPktsTimeFrame.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
?

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–11

cgprsGtpCurMeanThroughputForPremiumQos

ISSUE 1 REVISION 2

cgprsGtpCurMeanThroughputForPremiumQos
Description
The mean throughput for premium class QOS users on the GSN.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Gauge 32

Statistic Data
bits/sec

8–12

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpCurMeanThroughputForNormalQos

cgprsGtpCurMeanThroughputForNormalQos
Description
The mean throughput for normal class QOS users on the GSN.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Gauge 32

Statistic Data
bits/sec

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–13

cgprsGtpCurMeanThroughputForBestEffortQos

ISSUE 1 REVISION 2

cgprsGtpCurMeanThroughputForBestEffortQos
Description
The mean throughput for a ’best effort’ class QOS users on the GSN.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Gauge 32

Statistic Data
bits/sec

8–14

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpCurGSNBandwidthResourceUsed

cgprsGtpCurGSNBandwidthResourceUsed
Description
The current amount of bandwidth resource used on the GSN. The current amount of bandwidth resource available on GSN can be obtained by deducting the value of this object from the value of the object cgprsGtpGSNTotalBandwidthResource.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Gauge 32

Statistic Data
bits/sec

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–15

cgprsGtpGSNTable

ISSUE 1 REVISION 2

cgprsGtpGSNTable
Description
GSN peer table. The SGSN–GGSN peer relationship is established as follows: S S S S S S A table in DNS listing the APN and corresponding ip address of GGSN. When Mobile System (MS) wants service, it sends packets to a SGSN with specific APN. SGSN asks DNS for ip address of a GGSN that service this APN. DHCP returns a GGSN. SGSN requires a path to the GGSN using GTP protocol. The SGSN and GGSN peer maintains path by sending echo request message to each other. If one side fails in echo reply for certain times, the other side will send a trap to NMS. NOTE Multiple–Multiple peer relationship, i.e. A SGSN have multiple GGSN as peers, while a GGSN have multiple SGSN peers, depending on routing path NOTE Path is kept in database.

Type Supported by OMC GUI Dependencies Access Status

??? ??? ??? not accessible mandatory

Syntax
SEQUENCE OF CgprsGtpGSNEntry

Format
Example ???

Values
Value type Valid range Default value
8–16

??? ??? ???
EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

cgprsGtpGSNTable

References

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–17

cgprsGtpGSNEntry

ISSUE 1 REVISION 2

cgprsGtpGSNEntry
Description
GSN entry. The entry is created when a path between a GGSN and SGSN is set up and the end point of the path (either GGSN or SGSN) is not yet listed in the GSN peer table. The entry is deleted when the path is released, or the echo test message on the path times out after the retry number, defined as cgprsGtpN3Request.

Type Supported by OMC GUI Dependencies Access Status

??? ??? ??? not accessible mandatory

Syntax
cgprsGtpGSNEntry

Format
CgprsGtpGSNEntry ::= SEQUENCE{ cgprsGtpGSNid cgprsGtpGSNEchoFailedNotificationCount }

Example
?

Values
Value type Valid range Default value
??? ??? ???

References
?

8–18

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpGSNid

cgprsGtpGSNid
Description
IP address that uniquely identifies a GSN node.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
IpAddress

Statistic Data
?

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–19

cgprsGtpGSNEchoFailedNotificationCount

ISSUE 1 REVISION 2

cgprsGtpGSNEchoFailedNotificationCount
Description
The echo test failure count before the entry is deleted.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
?

8–20

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpTotalNumAllocIpAddr

cgprsGtpTotalNumAllocIpAddr
Description
The current number of total allocated ip addresses on the GGSN.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
allocated dynamic addresses

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–21

cgprsGtpChargingMsgCount

ISSUE 1 REVISION 2

cgprsGtpChargingMsgCount
Description
The current number of total charging messages in the queue.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Counter

Statistic Data
?

8–22

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpLastGSNidNoRespToEcho

cgprsGtpLastGSNidNoRespToEcho
Description
The name of the last peer GSN that does not reply to echo message.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
DisplayString

Statistic Data
?

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–23

cgprsGtpGSNidOfLastUnexpectedPDPContext

ISSUE 1 REVISION 2

cgprsGtpGSNidOfLastUnexpectedPDPContext
Description
The name of the peer GSN whose PDP context is unexpected.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
DisplayString

Statistic Data
?

8–24

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpTIDOfLastUnexpectedPDPContext

cgprsGtpTIDOfLastUnexpectedPDPContext
Description
The TID of the last unexpected PDP Context activation.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
DisplyString

Statistic Data
?

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–25

cgprsGtpRejectReasonOfLastUnexpectedPDPContext

ISSUE 1 REVISION 2

cgprsGtpRejectReasonOfLastUnexpectedPDPContext
Description
The reason for rejecting the PDP Context activation.

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
DisplayString

Statistic Data
?

8–26

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpNumAllocIpAddrTable

cgprsGtpNumAllocIpAddrTable
Description
The table for currently allocated number of dynamic addresses associated with a given APN.

Type Supported by OMC GUI Dependencies Access Status

??? ??? ??? not accessible mandatory

Syntax
SEQUENCE OF CgprsGtpNumAllocIpAddrEntry

Format
???

Example

Values
Value type Valid range Default value
??? ??? ???

References
?

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–27

cgprsGtpNumAllocIpAddrEntry

ISSUE 1 REVISION 2

cgprsGtpNumAllocIpAddrEntry
Description
The entry is created when a new APN is created. The entry is deleted when the associated APN is deleted.

Type Supported by OMC GUI Dependencies Access Status

??? ??? ??? not accessible mandatory

Syntax
cgprsGtpNumAllocIpAddrEntry

Format
CgprsGtpNumAllocIpAddrEntry ::= SEQUENCE{ cgprsGtpNumAllocIpAddr }

Example
?

Values
Value type Valid range Default value
??? ??? ???

References
?

8–28

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

cgprsGtpNumAllocIpAddr

cgprsGtpNumAllocIpAddr
Description
Number of ip addresses allocated for the specifified APN (as identified by cgprsGtpAPNId).

Pegging
?

Analysis
?

Reference
?

Usage
?

Basis
GTP

Statistic
Statistic Type
Gauge 32

Statistic Data
?

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

8–29

cgprsGtpNumAllocIpAddr

ISSUE 1 REVISION 2

8–30

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 9

Appendix

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Timer T3313

GSM Name T3313

Use Time out duration for page response from MS

MAX–PAGE–ATTEM PT T3312

T3312

Maximum number of attempts to page an MS GMM Periodic Routing Area Update Timer

T3314

T3314

GMM Ready Timer

T3315

T3315

GMM Standby Timer

N3

N3

bssgp_t1_timer

T1

bssgp_t2_timer

T2

bssgp_bock_retries

BVC–BLOCK– RETRIES

bssgp_unbock_retries

BVC–UNBLOC K–RETRIES

bssgp_reset_retries

BVC–RESET–R ETRIES

ns_block_timer

Tns–block

Maximum number of attempts to send a GTP message to a GSN T1 specifies the duration of the guard timer for cell blocking and unblocking T1 specifies the duration of the guard timer for reset proceedures with the SGSN bssgp_bock_retries specifeis the number of retries generated for cell block messages bssgp_unbock_retries specifeis the number of retries generated for cell unblock messages bssgp_reset_retries specifeis the number of retries generated for reset messages. Timer guards the NS–VC blocking and unblocking Timer guards the NS–VC reset proceddure Timer sets the period of the NS–VC test proceedure. The NS–VC is tested every ns_test_timer seconds

Value Default 8 Seconds Units: Seconds Range 3 –15 Ref GSM 4.08 Default: 2 Range: 1–5 Attempts Default 54 minutes Range 6 – 180 minutes in 6 minute increements –1 deactivates timer Ref GSM 3.60 Default 32 Seconds Units: Seconds Range: 2–60 Seconds in 2 second increments or 61–180 in 60 second incerments. –1 Deactivates Timer 0 will force to standby Default: 60 Minutes Units: Miniutes Range: 6–186 minutes in 6 minute incremetns. –1 deactivates timer Must be greater than T3312 Default: 3 Attempts Range: 1–5 Attempts Default: 3 Units: Seconds Range: 30–120 Default: 60 Units: Seconds Range: 1–120 Default: 3 Range: 1–3

Default: 3 Range: 1–3

Default: 3 Range: 1–3

ns_reset_timer

Tns–reset

ns_test_timer

Tns–test

Default: 3 Units: Seconds Range: 1–30 Defualt: 40 Units: Seconds Range: 1–120 Default: 30 Units: Seconds Range: 1–60

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

9–1

ISSUE 1 REVISION 2

ns_alive_timer

Tns–alive

Timer guards the NS–VC test proceedure

ns_block_retries

ns_unblock_retries

ns_alive_retries

ns_reset_period

bssgp_fc_period_c

gprs_bs_cv_max

bssgp_racap_retries

NS–BLOCK–RE Timer specifies the number TRIES of retries to block a NS–VC. NS_UNBLOCK Timer specifies the number _RETRIES of retires generated to unblock the NS–VC NS_ALIVE_RE Timer specifes the number TRIES of retries generated to establish if a NS–VC is alive Timer specifies the period over which the BSS shall attempt to reset a NS–VC Th This timer specifies the frequency of flow control form the PCU to the SGSN Maximum count down value a mobile can have for uplink RLC data transfer T5 The bssgp_recap_retries specifies the number of retries that the BSS generates for RA–Capabilty–Update messages

Default: 3 Units: Seconds Range: 1–30 Default: 3 Range: 1–3 Default: 3 Range: 1–3 Default: 3 Range: 1–10

Default: 125 Units: Seconds Range: 1–250 Default: 10 Units: 10ths of a second Range 1–1000 Default: 6 Range: 0–15 Default: 3 Range: 1–3

9–2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

Chapter 10

Glossary of technical terms and abbreviations

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

i

ISSUE 1 REVISION 2

ii

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Chapter 9 Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . .
Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A ......................................................................... B ......................................................................... C ......................................................................... D ......................................................................... E ......................................................................... F ......................................................................... G ......................................................................... H ......................................................................... I .......................................................................... K ......................................................................... L ......................................................................... M ......................................................................... N ......................................................................... O ......................................................................... P ......................................................................... Q ......................................................................... R ......................................................................... S ......................................................................... T ......................................................................... U ......................................................................... V ......................................................................... W ........................................................................ X ......................................................................... Z .........................................................................

i
9–1 9–2 9–5 9–8 9–12 9–15 9–17 9–19 9–21 9–22 9–24 9–25 9–27 9–31 9–33 9–35 9–38 9–39 9–42 9–46 9–49 9–50 9–51 9–52 9–53

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

iii

ISSUE 1 REVISION 2

iv

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Numbers

Numbers
# 2 Mbit/s link Number. 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. 4th Generation Language.

4GL

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–1

A

ISSUE 1 REVISION 2

A
A interface A3 A38 A5 A8 AA AB Abis interface Interface between MSC and BSS. Authentication algorithm that produces SRES, using RAND and Ki. A single algorithm performing the function of A3 and A8. Stream cipher algorithm, residing on an MS, that produces ciphertext out of plaintext, using Kc. Ciphering key generating algorithm that produces Kc using RAND and Ki. Anonymous Access. Access Burst. 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. Answer Bid Ratio. AC–DC Power Supply module. Alternating Current. Access Class (C0 to C15). Application Context. Automatic Congestion Control. Associated Control CHannel. ACKnowledgement. Accumulated Call meter. Address Complete Message. AC Power Interface Module. Used in M-Cell6 indor ac BTS equipment. AC Power Supply Module. Used in M-Cell6 BTS equipment. Associated Control Service Element. Antenna Combining Unit. Analogue to Digital (converter). ADministration Centre. Analogue to Digital Converter. ADvanced Communications Control Protocol. ADMinistration processor. ADMINistration. Abbreviated Dialling Number. Adaptive Differential Pulse Code Modulation. Application Entity. Accoustic Echo Control. Additional Elementary Functions.

ABR ac–dc PSM ac AC AC ACC ACCH ACK, Ack ACM ACM ACPIM AC PSM ACSE ACU A/D ADC ADC ADCCP ADM ADMIN ADN ADPCM AE AEC AEF

10–2

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

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. Automatic Frequency Control. Absolute Frame Number. Automatic Gain Control. Access Grant CHannel. A GSM common control channel used to assign MS to a SDCCH or a TCH. Action indicator. Artificial Intelligence. Alarm Interface Board. A class of processor. The radio link between the BTS and the MS. Amplitude Modulation. Automatic Message Accounting (processor). Cell broadcast mobile terminated message. A message broadcast to all MSs in a cell. Access Point Name. Advice of Change. Advice of Change Charging supplementary service. Advice of Change Information supplementary service. Automatic Output Control. Application Process. Absolute Radio Frequency Channel Number. An integer which defines the absolute RF channel number. Automatic ReQuest for retransmission. Address Resolution Protocol. 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). Application Service Element (OMC) Application Specific Entity (TCAP). Abstract Syntax Notation One. Alarm and Status Panel. Answer Seizure Ratio. All Trunks Busy. Antenna Transceiver Interface. Asynchronous Transfer Mode. ATTach. Automatic Trunk Testing Subsystem. Access Unit.

AFC AFN AGC AGCH Ai AI AIB AIO Air interface AM AMA AM/MP APN AoC AoCC AoCI AOC AP ARFCN ARQ ARP ASCE

ASE ASE ASN.1 ASP ASR ATB ATI ATM ATT (flag) ATTS AU

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–3

A

ISSUE 1 REVISION 2

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. AUThentication. AUTOmatic mode.

AUT(H) AUTO

10–4

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

B

B
B Interface BA BAIC BAOC BBBX BBH BCC BCCH Interface between MSC and VLR. BCCH Allocation. The radio frequency channels allocated in a cell for BCCH transmission. Barring of All Incoming Calls supplementary service. Barring of All Outgoing Calls supplementary service. Battery Backup Board. Base Band Hopping. BTS Colour Code. Broadcast Control CHannel. A GSM control channel used to broadcast general information about a BTS site on a per cell or sector basis. Binary Coded Decimal. 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. Bearer Capability Information Element. 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). Base Controller Unit Power. Bit Error Rate. A measure of signal quality in the GSM system. Business Exchange Services. Bad Frame Indication. Border Gateway. Border Gateway Protocol Busy Hour Call Attempt. all Barring of All Incoming call supplementary service. 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). Barring of All Incoming Calls when Roaming outside the Home PLMN Country supplementary service. Balanced-line Interconnect Module. An area in a data array used to store information. BootLoad. Also known as download. For example, databases and software can be downloaded to the NEs from the BSS. BiLLiNG. Bits per second (bps). Full rate traffic channel. Bit Number. Number which identifies the position of a particular bit period within a timeslot.

BCD BCF

BCIE BCU

BCUP BER BES BFI BG BGP BHCA BI BIB

BIC–Roam BIM Bin BL BLLNG bit/s Bm BN

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–5

B

ISSUE 1 REVISION 2

BPF BPSM BS BS

Bandpass Filter. mBCU Power Supply Module. Basic Service (group). 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. 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). Basic Service Group. 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 of an adjacent cell. Base Site control Processor (at BSC). Backward Sequence Number. 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. BSS Application Part (of Signalling System No. 7) (DTAP + BSSMAP). 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. Base Station System GPRS Protocol. Base Station System Management Application Part (6-8). BSS Operation and Maintenance Application Part (of Signalling System No. 7). 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). British Telecom. Bus Terminator. Bus Terminator Card. Base Transceiver Function. Base Transceiver Processor (at BTS). One of the six basic task groups within the GPROC.

BSC

BSG BSIC

BSIC-NCELL BSP BSN BSS

BSSAP BSSC

BSSGP BSSMAP BSSOMAP BSU

BT BT BTC BTF BTP

10–6

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

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). A period of modulated carrier less than one timeslot. The physical content of a timeslot. BSSGP Virtual Circuit Identifiers.

Burst BVCI

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–7

C

ISSUE 1 REVISION 2

C
C C Interface C7 CA CA CAB CADM Conditional. Interface between MSC and HLR/AUC. ITU-TSS Signalling System 7 (sometimes referred to as S7 or SS#7). Cell Allocation. The radio frequency channels allocated to a particular cell. Central Authority. Cabinet. Country ADMinistration. The Motorola procedure used within DataGen to create new country and network files in the DataGen database. Charge Advice Information. Cell Analysis Tool. Cell Broadcast. Circuit Breaker. Cell Broadcast Centre. Cell Broadcast CHannel. Combining Bandpass Filter. Cell Broadcast Link. Circuit Breaker Module. Cell Broadcast Message Identifier. Cell Broadcast Short Message Service. Clock Bus. Connection Confirm (Part of SCCP network connectivity). Country Code. Call Control. 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. Completion of Calls to Busy Subscriber supplementary service. Common Control CHannels. A class of GSM control channels used to control paging and grant access. Includes AGCH, PCH, and RACH. Group of MSs in idle mode. Common Channel Distributor. Channel Coding Digital Signal Processor. Conditional Call Forwarding. Control CHannel. Control channels are channels which carry system management messages. Council for Communications Harmonization (referred to in GSM Recommendations).
EMOTOROLA LTD. 2000

CAI CAT CB CB CBC CBCH CBF CBL CBM CBMI CBSMS CBUS CC CC CC CCB

CCBS CCCH

CCCH_GROUP CCD CCDSP CCF CCH CCH

10–8

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

C

CCIT

Comité Consultatif International Télégraphique et Téléphonique. This term has been superceded by ITU–TSS (International Telecommunications Union – Telecommunications Sector). Current Call Meter. Capability/Configuration Parameter. Control Channel Protocol Entity. 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. Circuit. Control Driver Board. Common Desktop Environment. Part of the SUN software (crontab – cron job file). Call Detail Records. Chargeable DURation. Control Equalizer Board (BTS). Called station identifier. Central Equipment Identity Register. 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).

CCM CCP CCPE CCS

Cct CDB CDE CDR CDUR CEB CED CEIR Cell

1 Cell = 1 Sector

Omni Site 1-Cell Site (1 BTS)

6-Sector Site or 6-Cell Site (6 BTSs)

CEND CEPT CERM CF CF CFB CFC CFNRc CFNRy

End of charge point. Conférence des administrations Européennes des Postes et Telecommunications. Circuit Error Rate Monitor. Conversion Facility. all Call Forwarding services. Call Forwarding on mobile subscriber Busy supplementary service. Conditional Call Forward. Call Forwarding on mobile subscriber Not Reachable supplementary service. Call Forwarding on No Reply supplementary service.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–9

C

ISSUE 1 REVISION 2

CFU Channel

Call Forwarding Unconditional supplementary service. 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. Coaxial Interconnect Module. Charging Gateway Function. CHarging Point. Card Holder Verification information. Ciphering Key Sequence Number. Cell Identity. A block of code which identifies a cell within a location area. CUG Index. Circuit Identity Code. Carrier to Interference Ratio. Unintelligible data produced through the use of encipherment. Ciphering Key Sequence Number. Calling Line Identity. Calling Line Identification Presentation supplementary service. Calling Line Identification Restriction supplementary service. Clock. Clock Extender half size board. The fibre optic link that distributes GCLK to boards in system (p/o BSS etc). Connectionless Manager. CLeaR. Configuration Management. An OMC application. Connection Management. CoMmanD. Channel Mode Modify. Common Management Information Protocol. 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). Cellular Manual Revision. CalliNg tone. COnnected Line Identity. Placed together; two or more items together in the same place. 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.

CIM CGF CHP CHV CKSN CI CI CIC CIR, C/I Ciphertext CKSN CLI CLIP CLIR CLK CLKX CLM CLR CM CM CMD CMM CMIP CMISE

CMR CNG COLI Collocated Coincident Cell

10–10

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

C

COLP COLR CODEX COM COM COMB CONNACK COMM, Comms CommsLink CONF CONFIG CP CPU C/R CR CR CRC CRE CREF CRM CRM-LS/HS

COnnected Line Identification Presentation supplementary service. COnnected Line Identification Restriction supplementary service. Manufacturer’s name for a type of multiplexer and packet switch commonly installed at the Motorola OMC-R. Code Object Manager. COMplete. Combiner. CONNect ACKnowledgement. COMMunications. Communications Link. (2Mbit/s) CONFerence circuit. CONFIGuration Control Program. Call Processing. Central Processing Unit. Command/Response field bit. Carriage Return (RETURN). Connection Request (Part of SCCP network connectivity). Cyclic Redundancy Check (3 bit). Call RE-establishment procedure. Connection REFused (Part of SCCP network connectivity). Cell Resource Manager. 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. Cathode Ray Tube (video display terminal). Code Storage Facility Processor (at BSC and BTS). Central Statistics Process. The statistics process in the BSC. Circuit Switched Public Data Network. Call Transfer supplementary service. Channel Tester. Channel Type. Call Trace Product (Tool). Common Technical Regulation. Clear to Send. Method of flow control (RS232 Interface). Compact Transceiver Unit (M-Cellhorizon radio). Closed User Group supplementary service. The total value for an entire statistical interval. Call Waiting supplementary service.

CRT CSFP CSP CSPDN CT CT CT CTP CTR CTS CTU CUG Cumulative value CW

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–11

D

ISSUE 1 REVISION 2

D
D Interface D/A DAB DAC DACS DAN DAS DAT DataGen dB DB DB DBA DBMS dc DCB DCCH Interface between VLR and HLR. Digital to Analogue (converter). Disribution Alarm Board. Digital to Analogue Converter. Digital Access Cross-connect System. Digital ANnouncer (for recorded announcements on MSC). Data Acquisition System. Digital Audio Tape. Sysgen Builder System. A Motorola offline BSS binary object configuration tool. Decibel. A unit of power ratio measurement. DataBase. Dummy Burst (see Dummy burst). DataBase Administration/Database Administrator. DataBase Management System. Direct Current. Diversity Control Board (p/o DRCU). Dedicated Control CHannel. A class of GSM control channels used to set up calls and report measurements. Includes SDCCH, FACCH, and SACCH. Data Carrier Detect signal. Data Circuit terminating Equipment. Data Communications Function. Duplexed Combining bandpass Filter. (Used in Horizonmacro). Data Communications Network. A DCN connects Network Elements with internal mediation functions or mediation devices to the Operations Systems. DC Power Supply Module. 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. Dual-stage Duplexed combining Filter. (Used in Horizonmacro). DataGen Directory Structure. Data Drive Storage. Direct Digital Synthesis. Diversity Equalizer Board. DETach. Decision Feedback Equalizer. Data Gathering Tool.
EMOTOROLA LTD. 2000

DCD DCE DCF DCF DCN

DC PSM DCS1800

DDF DDS DDS DDS DEQB DET DFE DGT

10–12

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

D

DHCP DHP DIA DINO E1/HDSL DINO T1 DISC Discon DIQ DIR DL DLCI DLD DLNB DLSP DLSP Dm DMA DMA DMR DMX DN DNIC DNS Downlink DP DPC

Dynamic Host Configuration Protocol. Digital Host Processor. Drum Intercept Announcer. Line termination module. Line termination module. DISConnect. Discontiuous. Diversity In phase and Quadrature phase. Device Interface Routine. Data Link (layer). Data Link Connection Identifier. Data Link Discriminator. Diversity Low Noise Block. Data Link Service Process. Digital Link Signalling Processor. Control channel (ISDN terminology applied to mobile service). Deferred Maintenance Alarm. An alarm report level; an immediate or deferred response is required (see also PMA). Direct Memory Access. Digital Mobile Radio. Distributed Electronic Mobile Exchange (Motorola’s networked EMX family). Directory Number. Data network identifier. Domain Name Server Physical link from the BTS towards the MS (BTS transmits, MS receives). Dial/Dialled Pulse. 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. Digital Processing and Control board. Digital Private Network Signalling System (BT standard for PABX interface). Dual Path Preselector. Dual Port Random Access Memory. Digital Power Supply Module. Dynamic Random Access Memory. Data Rate Converter board. Provides data and protocol conversion between PLMN and destination network for 8 circuits (p/o IWF). Diversity Radio Channel Unit. Contains transceiver, digital control circuits, and power supply (p/o BSS) (see RCU).

DPC DPNSS DPP DPR, DPRAM DPSM DRAM DRC

DRCU

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–13

D

ISSUE 1 REVISION 2

(D)RCU DRI DRIM DRIX DRX, DRx

Generic term for radio channel unit. May be standard RCU or diversity radio channel unit DRCU. Digital Radio Interface. Provides encoding/decoding and encryption/decryption for radio channel (p/o BSS). Digital Radio Interface extended Memory. A DRI with extra memory. DRI Extender half size board. Fibre optic link from DRI to BCU (p/o BSS). 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. German term for 2 Mbit/s line (PCM interface). Data Switching Exchange. Digital Speech Interpolation. Digital Signal Processor. Digital Subscriber Signalling No 1. Diversity Signal Strength Indication. Direct Transfer Application Part (6-8). Data Terminal Equipment. Digital Trunk Frame. DaTa form 1 (Part of SCCP network connectivity). Digital Trunk Interface. Dual Tone Multi-Frequency (tone signalling type). Data Terminal Ready signal. Method of flow control (RS232 Interface). Dual Transceiver Module. (Radio used in M-Cellarena and M-Cellarena macro). 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. 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. DYnamic NETwork. Used to specify BTSs sharing dynamic resources.

DS-2 DSE DSI DSP DSS1 DSSI DTAP DTE DTF DT1 DTI DTMF DTR DTRX DTX, DTx

Dummy burst

DYNET

10–14

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

E

E
E E Interface EA EAS Eb/No EBCG EC ECB ECID ECM Ec/No ECT ECT EEL EEPROM EGSM900 EI EIR EIRP EIRP EL EM EMC EMF EMI eMLPP EMMI EMU EMX en bloc See Erlang. Interface between MSC and MSC. External Alarms. External Alarm System. Energy per Bit/Noise floor. Elementary Basic Service Group. Echo Canceller. Performs echo suppression for all voice circuits. Provides echo cancelling for telephone trunks for 30 channels (EC). The Motorola European Cellular Infrastructure Division. Error Correction Mode (facsimile). Ratio of energy per modulating bit to the noise spectral density. Event Counting Tool. Explicit Call Transfer supplementary service. Electric Echo Loss. Electrically Erasable Programmable Read Only Memory. Extended GSM900. Events Interface. Part of the OMC-R GUI. Equipment Identity Register. Effective Isotropic Radiated Power. Equipment Identity Register Procedure. Echo Loss. Event Management. An OMC application. ElectroMagnetic Compatibility. Electro Motive Force. Electro Magnetic Interference. enhanced Multi-Level Precedence and Pre-emption service. Electrical Man Machine Interface. Exchange office Management Unit (p/o Horizonoffice) Electronic Mobile Exchange (Motorola’s MSC family). 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. End of Tape. Erasable Programmable Read Only Memory.

EOT EPROM

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–15

E

ISSUE 1 REVISION 2

EPSM EQB EQCP EQ DSP Erlang

Enhanced Power Supply Module (+27 V). Equalizer Board. Control circuit for equalization for 8 time slots each with equalizing circuitry and a DSP (p/o RCU). Equalizer Control Processor. Equalizer Digitizer Signal Processor. 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). Ear Reference Point. Effective Radiated Power. ERRor. Electro-static Point. Embedded SQL (Structured Query Language). An RDBMS programming interface language. Extended TACS (analogue cellular system, extended). Type of Local Area Network. ETSI Technical Report. European Telecommunication Standard. European Telecommunications Standards Institute. End of Transmission. Executive Process.

ERP ERP ERR ESP ESQL E-TACS Ethernet ETR ETS ETSI ETX EXEC

10–16

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

F

F
F Interface FA FA FA FAC FACCH Interface between MSC and EIR. Fax Adaptor. Full Allocation. Functional Area. Final Assembly Code. 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). Fast Associated Control Channel/Full rate. Fast Associated Control Channel/Half rate. Frequency correction Burst (see Frequency correction burst). Fibre Channel Arbitration Loop. (Type of hard disc). Frequency Correction CHannel. A GSM broadcast control channel which carries information for frequency correction of the mobile (MS). Fault Collection Process (in BTS). Frame Check Sequence. Frequency Division Multiplex. Frequency Division Multiple Access. Fixed Dialling Number. Fault Diagnostic Procedure. Forward Error Correction. Front End Processor. Frame Erasure Ratio. For Further Study. Frequency Hopping. Forward Indicator Bit. Finite Impulse Response (filter type). Foreign Key. A database column attribute; the foreign key indicates an index into another table. Fault Management (at OMC). Frequency Modulation. Fault Management Initiated Clear. Fibre optic MUltipleXer. Frame Number. Identifies the position of a particular TDMA frame within a hyperframe. First Office Application. Fibre Optic eXtender. 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).

FACCH/F FACCH/H FB FC-AL FCCH

FCP FCS FDM FDMA FDN FDP FEC FEP FER FFS, FS FH FIB FIR FK FM FM FMIC FMUX FN FOA FOX FR

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–17

F

ISSUE 1 REVISION 2

FR FRU Frequency correction

Frame Relay. Field Replaceable Unit. Period of RF carrier less than one timeslot whose modulation bit stream allows frequency correction to be performed easily within an MS burst. Frequency Synchronization. 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. Forward Sequence Number. File Transfer, Access, and Management. An ASE which provides a means to transfer information from file to file (OMC). forwarded-to number. Fault Translation Process (in BTS). File Transfer Protocol.

FS FSL

FSN FTAM

ftn FTP FTP

10–18

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

G

G
G Interface Gateway MSC Interface between VLR and VLR. 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. Gigabyte. Gigabit Interface Converter. Generic Clock board. System clock source, one per site (p/o BSS, BTS, BSC, IWF, RXCDR). Group Call Register. Generic DSP Processor board. Interchangeable with the XCDR board. GDP board configured for E1 link usage. GDP board configured for T1 link usage. Gateway GPRS Support Node. Giga-Hertz (109). Group ID. A unique number used by the system to identify a user’s primary group. GSM Multiplexer Board (p/o BSC). GSM Manual Revision. Gateway Mobile-services Switching Centre (see Gateway MSC). Gaussian Minimum Shift Keying. The modulation technique used in GSM. GrouND. Grade of Service. GSM PLMN Area. General Protocol Converter. Generic Processor board. GSM generic processor board: a 68030 with 4 to 16 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR). Generic Processor board. GSM generic processor board: a 68040 with 32 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR). General Packet Radio Service. Global Positioning by Satellite. GPRS Register. GSM Service Area. The area in which an MS can be reached by a fixed subscriber, without the subscriber’s knowledge of the location of the MS. A GSA may include the areas served by several GSM PLMNs. GSM System Area. The group of GSM PLMN areas accessible by GSM MSs. Groupe Spécial Mobile (the committee). Global System for Mobile communications (the system).

GB, Gbyte GBIC GCLK GCR GDP GDP E1 GDP T1 GGSN GHz GID GMB GMR GMSC GMSK GND GOS GPA GPC GPROC

GPROC2 GPRS GPS GR GSA

GSA GSM GSM

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–19

G

ISSUE 1 REVISION 2

GSM MS GSM PLMN GSN GSR GT GTE GTP Guard period GUI GUI client GUI server

GSM Mobile Station. GSM Public Land Mobile Network. GPRS Support Node. GSM Software Release. Global Title. Generic Table Editor. The Motorola procedure which allows users to display and edit MCDF input files. GPRS Tunnelling Protocol. Period at the beginning and end of timeslot during which MS transmission is attenuated. Graphical User Interface. A computer used to display a GUI from an OMC-R GUI application which is beingbrun on a 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). GateWaY (MSC/LR) interface to PSTN.

GWY

10–20

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

H

H
H Interface H-M HAD, HAP HANDO, Handover Interface between HLR and AUC. Human-Machine Terminals. HLR Authentication Distributor. 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. Hybrid Combining Unit. (Used in Horizonmacro). High level Data Link Control. High bit-rate Digital Subscriber Line. High Layer Compatibility. The HLC can carry information defining the higher layer characteristics of a teleservice active on the terminal. Home Location Register. The LR where the current location and all subscriber parameters of an MS are permanently stored. Heat Management System. The system that provides environmental control of the components inside the ExCell, TopCell and M-Cell cabinets. HandOver. (see HANDO above). Hand Portable Unit. Call hold supplementary service. Home PLMN. 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). HandSet. High Speed Interface card. HLR Subscriber Management. Hopping Sequence Number. Home Units. Hardware. 2048 superframes. The longest recurrent time period of the frame structure.

HCU HDLC HDSL HLC

HLR

HMS

HO HPU HOLD HPLMN HR

HS HSI/S HSM HSN HU HW Hyperframe

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–21

I

ISSUE 1 REVISION 2

I
I IA IA5 IADU IAM IAS IC IC IC(pref) ICB ICC ICM ICMP ID, Id IDN IDS IE IEC IEEE IEI I-ETS IF IFAM IM IMACS IMEI Information frames (RLP). Incomming Access (closed user group (CUG) SS (supplementary service)). International Alphanumeric 5. Integrated Antenna Distribution Unit. (The IADU is the equivalent of the Receive Matrix used on pre-M-Cell BTSs). Initial Address Message. Internal Alarm System. Integrated Circuit. Interlock Code (CUG SS). Interlock Code op the preferential CUG. Incoming Calls Barred. Integrated Circuit(s) Card. In-Call Modification. Internet Control Message Protocol. IDentification/IDentity/IDentifier. Integrated Digital Network. INFOMIX Database Server. (OMC-R relational database management system). Information Element (signalling). International Electrotechnical Commission. Institute of Electrical and Electronic Engineers. Information Element Identifier. Interim European Telecommunication Standard. Intermediate Frequency. Initial and Final Address Message. InterModulation. Intelligent Monitor And Control System. 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. IMMediate assignment message. 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. Intelligent Network. Interrogating Node. A switching node that interrogates an HLR, to route a call for an MS to the visited MSC. IN Service.
EMOTOROLA LTD. 2000

IMM IMSI

IN IN INS

10–22

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

I

INS InterAlg Interworking

Intelligent Network Service. Interference Algorithm. A single interference algorithm in a cell. The general term used to describe the inter-operation of networks, services, supplementary services and so on. See also IWF. A recording period of time in which a statistic is pegged. The end of an interval. Input/Output. Intelligent Optimization Platform. Initialisation Process. Internet Protocol. Inter-Process Communication. INtermodulation Products. Intellectual PRoperty. Integrated Power Supply Module (–48 V). Internet Protocol Version 4. Internet Protocol Version 6. (A hardware component). Indexed Sequential Access Method. International Switching Centre. Integrated Services Digital Network. An integrated services network that provides digital connections between user-network interfaces. Motorola Information Systems group (formally CODEX). International Organisation for Standardization. Informix Structured Query Language. IP Support Server. ISDN User Part (of signalling system No. 7). Inactivity Test (Part of SCCP network connectivity). Information Transfer Capability. International Telecommunication Union. International Telecommunication Union – Telecommunications Sector. 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. InterWorking MSC. InterWorking Unit.

Interval Interval expiry I/O IOS IP IP IPC IP, INP IPR IPSM IPV4 IPV6 IPX ISAM ISC ISDN

ISG ISO ISQL ISS ISUP IT ITC ITU ITU–TSS IWF

IWMSC IWU

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–23

K

ISSUE 1 REVISION 2

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

10–24

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

L

L
L1 L2ML L2R Layer 1. Layer 2 Management Link. Layer 2 Relay function. A function of an MS and IWF that adapts a user’s known layer2 protocol LAPB onto RLP for transmission between the MT and IWF. L2R Bit Orientated Protocol. L2R Character Orientated Protocol. Layer 3. Layer 3 Mobility Management. 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. Location Area Code. Location Area Identity. The information indicating the location area in which a cell is located. Local Area Network. LAN Extender half size board. Fibre optic distribution of LAN to/from other cabinets (p/o BSS etc). Link Access Protocol Balanced (of ITU–TSS Rec. x.25). Link Access Protocol Data. Link Access Protocol on the Dm channel. Inductor Capacitor (type of filter). Link Control Function. Local Communications Network. Link Control Processor. Local Exchange. Light Emitting Diode. Line Feed. Length Indicator. Line Identity. Lower Layer Compatibility. The LLC can carry information defining the lower layer characteristics of the terminal. Logical Link Control. LLC Protocol Data Unit. Traffic channel with capacity lower than a Bm. LAN Monitor Process. Least Mean Square. 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. Local Maintenance Terminal.

L2R BOP L2R COP L3 L3MM LA

LAC LAI LAN LANX LAPB LAPD LAPDm LC LCF LCN LCP LE LED LF LI LI LLC LLC LLC PDU Lm LMP LMS LMSI

LMT

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–25

L

ISSUE 1 REVISION 2

LNA LND Location area

Low Noise Amplifier. Last Number Dialled. 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. Linear Predictive Code. Local PLMN. Location Register. The GSM functional unit where MS location information is stored. The HLR and VLR are location registers. Link Stations Signalling Unit (Part of MTP transport system). Listener Side Tone Rating. Long Term Average. The value required in a BTS’s GCLK frequency register to produce a 16.384 MHz clock. Local Terminal Emulator. Long Term Predictive. Line Terminating Unit. Local Units. Location Update. Length and Value.

LPC LPLMN LR

LSSU LSTR LTA LTE LTP LTU LU LU LV

10–26

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

M

M
M M M-Cell M&TS Mandatory. Mega (106). Motorola Cell. 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). Mobile Allocation. The radio frequency channels allocated to an MS for use in its frequency hopping sequence. Medium Access Control. Mobile Allocation Channel Number. A cell in which the base station antenna is generally mounted away from buildings or above rooftop level. Mobile Additional Function. Mobile Access Hunting supplementary service. Mobile Allocation Index. Mean Accumulated Intrinsic Down Time. MAINTenance. Mobile Allocation Index Offset. Mobile Application Part (of signalling system No. 7). The inter-networking signalling between MSCs and LRs and EIRs. Mobile Application Part Processor. Megabyte. Megabits per second. Motorola Cellular Advanced Processor. Mobile Country Code. Motorola Customer Data Format used by DataGen for simple data entry and retrieval. Malicious Call Identification supplementary service. Motorola Customer Support Centre. Main Control Unit for M-Cell2/6. Also referred to as the Micro Control Unit in software. Main Control Unit, with dual FMUX. (Used in M-Cellhorizon). Main Control Unit for M-Cell Micro sites (M-Cellm). Also referred to as the Micro Control Unit in software. The software subtype representation of the Field Replaceable Unit (FRU) for the MCU-m. Mediation Device. Mobile Detached Flag for GPRS. (mobile) Management (entity) - Data Link (layer). Maintenance Entity (GSM Rec. 12.00).

MA MAC MACN Macrocell MAF MAH MAI MAIDT MAINT MAIO MAP MAPP MB, Mbyte Mbit/s MCAP MCC MCDF MCI MCSC MCU MCUF MCU-m MCUm MD MDG MDL ME

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–27

M

ISSUE 1 REVISION 2

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. Maintenance Entity Function (GSM Rec. 12.00). MultiFrame. Multi-Frequency (tone signalling type). MultiFunction block. Management. Manager. Message Handling System. Mobile Handling Service. Mega-Hertz (106). Maintenance Information. Management Information Base. A Motorola OMC-R database. There is a CM MIB and an EM MIB. Mobile Interface Controller. 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. minute(s). micro-second (10–6). Micro Base Control Unit. Management Information Tree. Name of a file on the Motorola OMC-R. Man Machine. Mobility Management. Mobile Management Entity. Middle Man Funnel process. Man Machine Interface. The method in which the user interfaces with the software to request a function or change parameters. A machine configured to use the OMC-R software from an MMI server. MMI client/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. Man Machine Language. The tool of MMI. Multiple Serial Interface Link. (see also 2Mbit/s link) Mobile Network Code. Mobile Not Reachable Flag.

MEF MF MF MF MGMT, mgmt MGR MHS MHS MHz MI MIB MIC Microcell

min ms mBCU MIT MM MM MME MMF MMI

MMI client MMI processor MMI server

MML MMS MNC MNR

10–28

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

M

MNT MO MO/PP MOMAP MoU MPC MPH MPTY MPX MRC MRN MRP MS MSC MSCM MSCU msec MSI MSIN MSISDN

MaiNTenance. Mobile Originated. Mobile Originated Point-to-Point messages. Motorola OMAP. Memorandum of Understanding. Multi Personal Computer (was p/o OMC). (mobile) Management (entity) - PHysical (layer) [primitive]. MultiParTY (Multi ParTY) supplementary service. MultiPleXed. Micro Radio Control Unit. Mobile Roaming Number. Mouth Reference Point. Mobile Station. The GSM subscriber unit. Mobile-services Switching Centre, Mobile Switching Centre. Mobile Station Class Mark. Mobile Station Control Unit. millisecond (.001 second). Multiple Serial Interface board. Intelligent interface to two 2 Mbit/s digital links (see 2 Mbit/s link and DS-2) (p/o BSS). Mobile Station Identification Number. 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). Multiple Subscriber Profile. Mobile Station Roaming Number. A number assigned by the MSC to service and track a visiting subscriber. 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. Mobile Terminated. Describes a call or short message destined for an MS. 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. Mean Time Between Failure. Mobile-To-Mobile (call). Message Transfer Part. Mobile Terminated Point-to-Point messages.

MSP MSRN MSU

MT MT (0, 1, 2)

MTBF MTM MTP MT/PP

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–29

M

ISSUE 1 REVISION 2

MTBF MTK MTL MTP MTTR Multiframe

Mean Time Between Failures. Message Transfer LinK. MTP Transport Layer Link (A interface). Message Transfer Part. Mean Time To Repair. 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. Mark Up. Multi User Mobile Station. Multiplexer.

MU MUMS MUX

10–30

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

N

N
NAT N/W NB NBIN NCC NCELL NCH ND Network Address Translation. Network. Normal Burst (see Normal burst). A parameter in the hoping sequence. Network (PLMN) Colour Code. Neighbouring (of current serving) Cell. Notification CHannel. No Duplicates. A database column attribute meaning the column contains unique values (used only with indexed columns). National Destination Code. Network Determined User Busy. Network Element (Network Entity). Network Element Function block. Norme Européennes de Telecommunications. Frequency planning tool. Network Function. Network File System. Network Health Analyst. Optional OMC-R processor feature. Network Interface Card. Network Independent Clocking. Network Information Service. It allows centralised control of network information for example hostnames, IP addresses and passwords. Network Interface Unit. Network Interface Unit, micro. Network LinK processor(s). Newton metres. 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. Network Management Application Service Element. 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. National Mobile Station Identification number. Nordic Mobile Telephone system. No Nulls. A database column attribute meaning the column must contain a value in all rows. A period of modulated carrier less than a timeslot.

NDC NDUB NE NEF NET NETPlan NF NFS NHA NIC NIC NIS

NIU NIU-m NLK Nm NM

NMASE NMC

NMSI NMT NN Normal burst

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–31

N

ISSUE 1 REVISION 2

NPI NRZ NSAP NSAPI NSP NSS NT NT NTAAB NTP NUA NUI NUP NV NVRAM nW

Number Plan Identifier. Non Return to Zero. Network Service Access Point. Network Layer Service Access Point Identifier. Network Service Provider. Network Status Summary. Network Termination. Non Transparent. New Type Approval Advisory Board. Network Time Protocol. Network User Access. Network User Identification. National User Part (of signalling system No. 7). NonVolatile. Non-Volatile Random Access Memory. Nano-Watt (10–9).

10–32

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

O

O
O OA O&M OASCU Optional. Outgoing Access (CUG SS). Operations and Maintenance. 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. Outgoing Calls Barred within the CUG. Oversized Voltage Controlled Crystal Oscillator. Optional for operators to implement for their aim. % OverFlow. IDS shutdown state. IDS normal operatng state. Operator Initiated Clear. Off_Line MIB. A Motorola DataGen database, used to modify and carry out Radio Frequency planning on multiple BSS binary files. Overall Loudness Rating. Operations and Maintenance Application Part (of signalling system No. 7) (was OAMP). 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. Operations and Maintenance Centre — Gateway Part. (Iridium) Operations and Maintenance Centre — GPRS Part. Operations and Maintenance Centre — Radio Part. Operations and Maintenance Centre — Switch Part. Operations and Maintenance Function (at BSC). Operations and Maintenance Link. Operation and Maintenance Processor. Operation and Maintenance System (BSC–OMC). Operation and Maintenance SubSystem. Out Of Service. 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. Olympus Radio Architecture Chipset. Operating System. Open Systems Interconnection. OSI Reference Model. Operation Systems Function block.

OCB OCXO OD OFL offline online OIC OLM

OLR OMAP OMC

OMC-G OMC-G OMC-R OMC-S OMF OML OMP OMS OMSS OOS OPC

ORAC OS OSI OSI RM OSF

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–33

O

ISSUE 1 REVISION 2

OSF/MOTIF OSS Overlap

Open Software Foundation Motif. The basis of the GUI used for the Motorola OMC-R MMI. Operator Services System. 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.

10–34

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

P

P
PA PAB PABX PACCH PAD Paging Power Amplifier. Power Alarm Board. Private Automatic Branch eXchange. Packet Associated Control Channel Packet Assembler/Disassembler facility. 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. CEPT 2 Mbit/s route through the BSS network. Processor Bus. Private Branch eXchange. Personal Computer. Paging CHannel. A GSM common control channel used to send paging messages to the MSs. Paging Channel Network. Physical Channel. Pulse Code Modulation (see also 2 Mbit/s link which is the physical bearer of PCM). Personal Communications Network. Preventative Cyclic Retransmission. A form of error correction suitable for use on links with long transmission delays, such as satellite links. Packet Control Unit (p/o GPRS). Picocell Control unit (p/o M-Cellaccess). Potential difference. Protocol Discriminator. Public Data. Power Distribution Board. Packet Data Channel. Power Distribution Frame (MSC/LR). Public Data Networks. Packet Data Network. Packet Data traffic Channel. Power Distribution Unit. Protected Data Unit. Protocol Data Unit. Pan European Digital Cellular. A single incremental action modifying the value of a statistic. Modifying a statistical value. Packet Handler. PHysical (layer).

PATH PBUS PBX PC PCH PCHN PCHN PCM PCN PCR

PCU PCU pd PD PD PDB PDCH PDF PDN PDN PDTCH PDU PDU PDU PEDC Peg Pegging PH PH

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–35

P

ISSUE 1 REVISION 2

PHI PI Picocell PICS PID PIM PIN PIN PIX PIXT PK Plaintext PlaNET PLL PLMN PM PM-UI PMA PMS PMUX PN PNE POI POTS p/o pp, p-p PP ppb PPE ppm PPP Pref CUG Primary Cell

Packet Handler Interface. Presentation Indicator. A cell site where the base station antenna is mounted within a building. Protocol Implementation Conformance Statement. Process IDentifier/Process ID. PCM Interface Module (MSC). Personal Identification Number. Problem Identification Number. Parallel Interface Extender half size board. Customer alarm interface (p/o BSS). Protocol Implementation eXtra information for Testing. Primary Key. A database column attribute, the primary key is a not-null, non-duplicate index. Unciphered data. Frequency planning tool. Phase Lock Loop (refers to phase locking the GCLK in the BTS). Public Land Mobile Network. The mobile communications network. Performance Management. An OMC application. Performance Management User Interface. Prompt Maintenance Alarm. An alarm report level; immediate action is necessary (see also DMA). Pseudo MMS. PCM MUltipleXer. Permanent Nucleus (of GSM). Présentation des Normes Européennes. Point of Interconnection (with PSTN). Plain Old Telephone Service (basic telephone services). Part of. Peak-to-peak. Point-to-Point. Parts per billion. Primative Procedure Entity. Parts per million (x 10–6). Point to Point Protocol. Preferential CUG. 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. Programmable Read Only Memory.

PROM

10–36

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

P

Ps PSA PSAP PSM PSPDN

Location probability. Periodic Supervision of Accessability. Presentation Services Access Point. Power Supply Module. Packet Switched Public Data Network. Public data communications network. x.25 links required for NE to OMC communications will probably be carried by PSPDN. Public Switched Telephone Network. The UK land line telephone network. Power Supply Unit. Pure Sine Wave. Point to Multipoint Point to Multipoint for Group. Point to Multipoint for Multicast. Public Telecommunications Operator. Point to Point. Point to Point Connectionless Service. Point to Point Connection Oriented Service. Price per Unit Currency Table. Permanent Virtual Circuit. Pass Word. Power. Private eXchange Public Data Network.

PSTN PSU PSW PTM PTM-G PTM-M PTO PTP PTP-CLNS PVC-CONS PUCT PVC PW PWR PXPDN

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–37

Q

ISSUE 1 REVISION 2

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

10–38

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

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). RAndom mode request information field. Routing Area. Random Access Burst. Routing Area Code. Random Access Control CHannel. A GSM common control channel used to originate a call or respond to a page. Random Access CHannel. Routing Area Identity. Random Access Memory. RANDom number (used for authentication). Receive Antenna Transceiver Interface. Rate Adaptation. Remote BSS Diagnostic System (a discontinued Motorola diagnostic facility). Residual Bit Error Ratio. Remote Base Transceiver Station. Radio Control Board (p/o DRCU). Radio Channel Identifier. Radio Control Processor. Radio Channel Unit. Contains transceiver, digital control circuits, and power supply (p/o BSS) (see DRCU). Receiver. Relational DataBase Management System (INFORMIX). Radio Digital Interface System. Restricted Digital Information. Reference Distribution Module. Relative Distinguished Name. A series of RDN form a unique identifier, the distinguished name, for a particular network element. RECommendation. REJect(ion). RELease. Residual Excited Linear Predictive. RELP Long Term Prediction. A name for GSM full rate (see full rate). Resynchronize/resynchronization. REQuest. A Motorola DataGen utility for producing an MMI script from a binary object database.

RA RA RAB RAC RACCH RACH RAI RAM RAND RATI RAx RBDS RBER RBTS RCB RCI RCP RCU RCVR RDBMS RDI RDIS RDM RDN

REC, Rec REJ REL RELP RELP-LTP resync REQ Revgen

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–39

R

ISSUE 1 REVISION 2

RF RFC, RFCH

Radio Frequency. Radio Frequency Channel. A partition of the system RF spectrum allocation with a defined bandwidth and centre frequency. Receiver Front End (shelf). Receiver Front End Board (p/o DRCU II). Radio Frequency Interference. Radio Frequency Module. Reduced TDMA Frame Number. Reserved for Future Use. Network cable/Connector type. Reduced Instruction Set Computer. Remote login. Release Complete. Radio Link Control. Radio Link Protocol. An ARQ protocol used to transfer user data between an MT and IWF. See GSM 04.22. Receiver Loudness Rating. ReLeaSeD. Root Mean Square (value). Remote Mobile Switching Unit. Table of 128 integers in the hopping sequence. Read Only Memory. 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). 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. Regular Pulse Excited. Regular Pulse Excitation - Long Term Prediction. The GSM digital speech coding scheme. Recognised Private Operating Agency. Read Privilege Required. Access to the column is allowed only for privileged accounts. Radio Resource management. Receive Ready (frame). Radio Resource State Machine. Standard serial interface. Radio System Entity. Radio Signalling Link. Radio System Link Function. Radio System Link Processor.

RFE RFEB RFI RFM RFN RFU RJ45 RISC RL RLC PLC RLP RLR RLSD RMS RMSU RNTABLE ROM ROSE

Roundtrip

RPE RPE-LTP RPOA RPR RR RR RRSM RS232 RSE RSL RSLF RSLP

10–40

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

R

RSS RSSI RSZI RTC RTE RTF RTF RTS RU Run level Rx RXCDR RXF RXLEV-D RXLEV-U RXQUAL-D RXQUAL-U RXU

Radio SubSystem (replaced by BSS). Received Signal Strength Indicator. Regional Subscription Zone Identity. Remotely Tuneable Channel Combiner. Remote Terminal Emulator. Radio Transceiver Function. Receive Transmit Functions. Request to Send. Method of flow control (RS232 Interface). Rack Unit. System processor operating mode. Receive(r). Remote Transcoder. Receive Function (of the RTF). Received signal level downlink. Received signal level uplink. Received signal quality downlink. Received signal quality uplink. Remote Transcoder Unit. The shelf which houses the remote transcoder modules in a BSSC cabinet at a remote transcoder site.

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–41

S

ISSUE 1 REVISION 2

S
S/W SABM SABME SACCH SoftWare. Set Asynchronous Balanced Mode. A message which establishes the signalling link over the air interface. SABM Extended. Slow Associated Control CHannel. A GSM control channel used by the MS for reporting RSSI and signal quality measurements. Slow Associated Control CHannel/SDCCH/4. Slow Associated Control CHannel/SDCCH/8. Slow Associated Control CHannel/Traffic channel. Slow Associated Control CHannel/Traffic channel Full rate. Slow Associated Control CHannel/Traffic channel Half rate. A brand of trunk test equipment. 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. System Audits Process. Service Access Point Indicator (identifier). Surface Acoustic Wave. Synchronization Burst (see Synchronization burst). Serial Bus. Service Centre (used for Short Message Service). Service Code. System Change Control Administration. Software module which allows full or partial software download to the NE (OMC). Signalling Connection Control Part (6-8). Speech Coding Experts Group (of GSM). Synchronization CHannel. A GSM broadcast control channel used to carry information for frame synchronization of MSs and identification of base stations. Status Control Interface. Serial Communication Interface Processor. Status Control Manager. Sub-Channel Number. One of the parameters defining a particular physical channel in a BS. Service Control Point (an intelligent network entity). Small Computer Systems Interface. Slim Channel Unit. Slim Channel Unit for GSM900. 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.
EMOTOROLA LTD. 2000

SACCH/C4 SACCH/C8 SACCH/T SACCH/TF SACCH/TH SAGE SAP

SAP SAPI SAW SB SBUS SC SC SCCA

SCCP SCEG SCH

SCI SCIP SCM SCN SCP SCSI SCU SCU900 SDCCH

10–42

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

S

SDL SDT SDU SDR SE Secondary Cell

Specification Description Language. SDL Developement Tool. Service Data Unit. Special Drawing Rights (an international “basket” currency for billing). Support Entity (GSM Rec. 12.00). 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. Support Entity Function (GSM Rec.12.00). Slow Frequency Hopping. Screening Indicator. Service Interworking. Supplementary Information. Supplementary Information A. Silence Descriptor. Signal Information Field. The bits of a message signal unit that carry information for a certain user transaction; the SIF always contains a label. 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. Single Inline Memory module. System Integrated Memory Module. Service Information Octet. Eight bits contained in a message signal unit, comprising the service indicator and sub-service field. BSC, BTS or collocated BSC-BTS site. 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). Secondary Key. A database column attribute, the secondary key indicates an additional index and/or usage as a composite key. Signalling Link. Serial Link. Send Loudness Rating. Signalling Link Test Message. Switch Manager. Summing Manager. System Management Application Entity (CCITT Q795, ISO 9596). Short Message Cell Broadcast.

SEF SFH SI SI SI SIA SID SIF

SIM

SIMM SIMM SIO

SITE SIX

SK

SL SLNK SLR SLTM SM SM SMAE SMCB

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–43

S

ISSUE 1 REVISION 2

SME SMG SMP SMS SMSCB SMS-SC SMS/PP Smt SN SND SNDCP SNDR SN—PDU SNR SOA SP

Short Message Entity. Special Mobile Group. Motorola Software Maintenance Program. Short Message Service. Short Message Service Cell Broadcast. Short Message Service - Service Centre. Short Message Service/Point-to-Point. Short message terminal. Subscriber Number. SeND. Subnetwork Dependant Convergence Protocol SeNDeR. SNDCP PDU. Serial NumbeR. Suppress Outgoing Access (CUG SS). Service Provider. The organisation through which the subscriber obtains GSM telecommunications services. This may be a network operator or possibly a separate body. Signalling Point. Special Product. SPare. Signalling Point Code. Suppress Preferential CUG. Signalling Point Inaccessible. Single Path Preselector. Signal Quality Error. Structured Query Language. Service Request Distributor. Signed RESponse (authentication). Supplementary Service. A modification of, or a supplement to, a basic telecommunication service. System Simulator. SCCP messages, Subsystem-allowed (see CCITT Q.712 para 1.15). Site System Audits Processor. Supplementary Service Control string. Subservice Field. The level 3 field containing the network indicator and two spare bits. Signalling State Machine. SubSystem Number. Service Switching Point (an intelligent network element).

SP SP SP SPC SPC SPI SPP SQE SQL SRD SRES SS SS SSA SSAP SSC SSF SSM SSN SSP

10–44

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

S

SSP SSP SSS SS7 STAN STAT stats STC STMR SUERM STP Superframe Super user SURF SVC SVM SVN SW SWFM sync Synchronization burst

SCCP messages, Subsystem-prohibited (see CCITT Q.712 para 1.18). SubSystem Prohibited message. Switching SubSystem (comprising the MSC and the LRs). ANSI Signalling System No. 7 (alias C7). Statistical ANalysis (processor). STATistics. Statistics. System Timing Controller. Side Tone Masking rating. Signal Unit Error Rate Monitor. Signalling Transfer Point. 51 traffic/associated control multiframes or 26 broadcast/common control multiframes (period 6.12s). User account that can access all files, regardless of protection settings, and control all user accounts. Sectorized Universal Receiver Front-end (Used in Horizonmacro). Switch Virtual Circuit. SerVice Manager. Software Version Number. Software. SoftWare Fault Management. synchronize/synchronization. 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. SYStem. SYStem GENeration. The Motorola procedure for loading a configuration database into a BTS.

SYS SYSGEN

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–45

T

ISSUE 1 REVISION 2

T
T T T T43 Timer. Transparent. Type only. Type 43 Interconnect Board. Provides interface to 12 unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for 2 Mbit/s circuits (See BIB). Terminal Adaptor. A physical entity in the MS providing terminal adaptation functions (see GSM 04.02). Timing Advance. Type Approval Code. Total Access Communications System (European analogue cellular system). Terminal Adaptation Function. Transmit Antenna Transceiver Interface. The TATI consists of RF combining equipments, either Hybrid or Cavity Combining. (See CCB). Transparent Asynchronous Transmitter/Receiver Interface (physical layer). To Be Determined. Temporary Block Flow. Technical Basis for Regulation. TDM Bus. Transaction Capabilities. Transaction Capabilities Application Part (of Signalling System No. 7). TATI Control Board. Traffic CHannel. GSM logical channels which carry either encoded speech or user data. A full rate TCH. A full rate TCH at  2.4 kbit/s. A full rate TCH at 4.8 kbit/s. A full rate TCH at 9.6 kbit/s. A full rate Speech TCH. A half rate TCH. A half rate TCH at  2.4 kbit/s. A half rate TCH at 4.8 kbit/s. A half rate Speech TCH). Transceiver Control Interface. Transmission Control Protocol/Internet Protocol. Technical Commitee Technical Report. Transceiver Control Unit. Twin Duplexed Filter. (Used in M-Cellhorizon).
EMOTOROLA LTD. 2000

TA TA TAC TACS TAF TATI

TAXI TBD TBF TBR TBUS TC TCAP TCB TCH TCH/F TCH/F2.4 TCH/F4.8 TCH/F9.6 TCH/FS TCH/H TCH/H2.4 TCH/H4.8 TCH/HS TCI TCP/IP TC-TR TCU TDF

10–46

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

ISSUE 1 REVISION 2

T

TDM TDMA TDU TE

Time Division Multiplexing. Time Division Multiple Access. TopCell Digital Unit. Terminal Equipment. Equipment that provides the functions necessary for the operation of the access protocols by the user. Terminal endpoint identifier. Terminal Equipment Identity. TEMPorary. TEST control processor. TransFer Allowed. Temporary Flow Identifier. TransFer Prohibited. Trivial File Transfer Protocol. Transaction Identifier. Tunnel Identifier. The multiplex subdivision in which voice and signalling bits are sent over the air. Each RF carrier is divided into 8 timeslots. 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. Temporary Logical Link Identity. Type, Length and Value. Traffic Manager. TDM Modem Interface board. Provides analogue interface from IWF to modems for 16 circuits (p/o IWF). Traffic Metering and Measuring. 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. 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. Timeslot Number. Type Of Number. Channels which carry user’s speech or data (see also TCH). Equivalent to an erlang. Sequence of modulating bits employed to facilitate timing recovery and channel equalization in the receiver. Transcoder Rate Adaption Unit. TopCell Radio unit.

Tei TEI TEMP TEST TFA TFI TFP TFTP TI TI Timeslot

Timing advance

TLLI TLV TM TMI TMM TMN

TMSI

TN TON Traffic channels Traffic unit Training sequence TRAU TRU

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–47

T

ISSUE 1 REVISION 2

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. Technical Specification. TeleService. TimeSlot (see Timeslot). TimeSlot Acquisition. TimeSlot Assignment. Transceiver Speech & Data Interface. Training Sequence Code. TimeSlot Interchange. Transceiver Speech and Data Interface. Transceiver Station Manager. Timeslot SWitch. Tree and Tabular Combined Notation. Transistor to Transistor Logic. TeleTYpe (refers to any terminal). Traffic Unit. Telephone User Part (SS7). Type and Value. Transmit(ter). Transmit Function (of the RTF). Transmit PoWeR. Tx power level in the MS_TXPWR_REQUEST and MS_TXPWR_CONF parameters. Transmit Bandpass Filter.

TS TS TS TSA TSA TSDA TSC TSI TSDI TSM TSW TTCN TTL TTY TU TUP TV Tx TXF TXPWR

TxBPF

10–48

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

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. Unrestricted Digital Information. User Datagram Protocol. User Determined User Busy. Ultra High Frequency. Unnumbered Information (Frame). Union International des Chemins de Fer. User ID. Unique number used by the system to identify the user. Upload (of software or database from an NE to a BSS). Air interface. Universal Mobile Telecommunication System. Uniform PCM Interface (13 bit). Up to Date. Physical link from the MS towards the BTS (MS transmits, BTS receives). Uninterruptable Power Supply. User Part Unavailable. 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. Unstructured Supplementary Service Data. User-to-User Signalling supplementary service.

UDI UDP UDUB UHF UI UIC UID UL Um UMTS UPCMI UPD Uplink UPS UPU Useful part of burst

USSD UUS

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–49

V

ISSUE 1 REVISION 2

V
V VA VAD VAP VBS VC VCO VCXO VDU VGCS VLR Value only. Viterbi Algorithm (used in channel equalizers). Voice Activity Detection. A process used to identify presence or absence of speech data bits. VAD is used with DTX. Videotex Access Point. Voice Broadcast Service. Virtual Circuit. Voltage Controlled Oscillator. Voltage Controlled Crystal Oscillator. Visual Display Unit. Voice Group Call Service. 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. Very Large Scale Integration (in ICs). Visited MSC. (Recommendation not to be used). Voice Operated Transmission. Visited PLMN. Videotex Service Centre. Send state variable. Vehicular Speaker Phone. Voltage Standing Wave Ratio. The components dedecated to Videotex service.

VLSI VMSC VOX VPLMN VSC V(SD) VSP VSWR VTX host

10–50

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

W

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

WSF WWW

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–51

X

ISSUE 1 REVISION 2

X
X.25 X.25 link XBL XCB XCDR XCDR board CCITT specification and protocols for public packet-switched networks (see PSPDN). A communications link which conforms to X.25 specifications and uses X.25 protocol (NE to OMC links). Transcoder to BSS Link. The carrier communications link between the Transcoder (XCDR) and the BSS. Transceiver Control Board (p/o Transceiver). Full-rate Transcoder. Provides speech transcoding and 4:1 submultiplexing (p/o BSS, BSC or XCDR). 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. Transfer. eXchange IDentifier. X terminal window.

XFER XID X-Term

10–52

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000

ISSUE 1 REVISION 2

Z

Z
ZC Zone Code

EMOTOROLA LTD. 2000

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

10–53

Z

ISSUE 1 REVISION 2

10–54

GPRS01: GPRS Architecture FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2000