Professional Documents
Culture Documents
GPRS01
GPRS01
CHAPTER 9 APPENDIX
CHAPTER 10 GLOSSARY
ISSUE 1 REVISION 2
ISSUE 1 REVISION 2
ISSUE 1 REVISION 2
E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999 All Rights Reserved Printed in the U.K.
ISSUE 1 REVISION 2
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
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 Motorolas operation, installation and maintenance instructions may, in exceptional circumstances, lead to serious injury or death. These manuals are not intended to replace the system and equipment training offered by Motorola, although they can be used to supplement and enhance the knowledge gained through such training.
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.
ISSUE 1 REVISION 2
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.
ISSUE 1 REVISION 2
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.
ISSUE 1 REVISION 2
Warnings
Definition
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents, as well as those inherent in the equipment.
Cautions
Definition
A caution means that there is a possibility of damage to systems, or individual items of equipment within a system. However, this presents no danger to personnel.
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 customers failure to comply with these requirements.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Warnings particularly applicable to the equipment are positioned on the equipment and within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other warnings given in text, on the illustrations and on the equipment.
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single phase or 415 V ac three phase mains which is potentially lethal. Therefore, the areas where the ac mains power is present must not be approached until the warnings and cautions in the text and on the equipment have been complied with. To achieve isolation of the equipment from the ac supply, the mains input isolator must be set to off and locked. Within the United Kingdom (UK) regard must be paid to the requirements of the Electricity at Work Regulations 1989. There may also be specific country legislation which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station equipment when in operation. Ensure that all transmitters are switched off when any antenna connections have to be changed. Do not key transmitters connected to unterminated cavities or feeders. Refer to the following standards: S 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
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.
ISSUE 1 REVISION 2
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.
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
ISSUE 1 REVISION 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.
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 PCL = +39.02.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+
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.
Other equipment
Whether a given installation meets ANSI standards for human exposure to radio frequency radiation may depend not only on this equipment but also on whether the environments being assessed are being affected by radio frequency fields from other equipment, the effects of which may add to the level of exposure. Accordingly, the overall exposure may be affected by radio frequency generating facilities that exist at the time the licensees equipment is being installed or even by equipment installed later. Therefore, the effects of any such facilities must be considered in site selection and in determining whether a particular installation meets the FCC requirements.
10
ISSUE 1 REVISION 2
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.
11
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.
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 customers failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These must be observed by all personnel at all times when working with the equipment, as must any other cautions given in text, on the illustrations and on the equipment.
Fibre optics
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge. Although the damage caused by static discharge may not be immediately apparent, CMOS devices may be damaged in the long term due to static discharge caused by mishandling. Wear an approved earth strap when adjusting or handling digital boards. See Devices sensitive to static for further information.
13
ISSUE 1 REVISION 2
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and pins, they should be transferred directly from their packing to the equipment (or the other way around) and never left exposed on the workbench.
14
ISSUE 1 REVISION 2
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
15
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
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.
17
ISSUE 1 REVISION 2
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
ISSUE 1 REVISION 2
19
Chapter 1
GPRS Review
ISSUE 1 REVISION 2
ii
ISSUE 1 REVISION 2
i
11 12 12 12 12 12 14 14 14 14 16 16 16 16 18 18 110 112 114 116 118 120 122 124 126 128 130 132 134 136 138 140 142 146 148 150 154 154 154 156 158
iii
ISSUE 1 REVISION 2
iv
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
11
ISSUE 1 REVISION 2
S S
OMCG
The OMC-G enables operators to use an NT graphical user interface (GUI) when managing the GPRS components. System operators use the OMCG to configure and monitor system components and view performance data.
ISSUE 1 REVISION 2
A RXCDR MSC
Internet
GSN Network
GGSN
ISS
13
ISSUE 1 REVISION 2
ISSUE 1 REVISION 2
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
IP
IP
L2
L2
L1
L1
MS
BSS
SGSN
GGSN
15
ISSUE 1 REVISION 2
S S
16
ISSUE 1 REVISION 2
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
IP
IP
L2
L2
L1
L1
MS
BSS
SGSN
GGSN
17
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
18
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
19
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
110
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
111
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.
112
ISSUE 1 REVISION 2
GPRS Review
Um Air Interface
CCH
CCCH
BCCH
RACH
PCH/AGCH
CBCH
PCCH PBCCH
PCCCH
RACH
PPCH
PAGCH
PNCH
113
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 NonBCCH. GPRS timeslots are divided into Reserved and Switchable timeslots.
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.
114
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
115
GPRS Review
ISSUE 1 REVISION 2
116
ISSUE 1 REVISION 2
GPRS Review
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
B3 B4 B5 I B6 B7 B8 I
B9 B10 B11 I
117
GPRS Review
ISSUE 1 REVISION 2
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.
118
ISSUE 1 REVISION 2
GPRS Review
119
GPRS Review
ISSUE 1 REVISION 2
120
ISSUE 1 REVISION 2
GPRS Review
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)
121
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.
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.
122
ISSUE 1 REVISION 2
GPRS Review
Idle/Stby/Ready
IDLE
IDLE
READY
READY
PDU reception
STANDBY
STANDBY
MM State Model of MS
123
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.
124
ISSUE 1 REVISION 2
GPRS Review
Timing advance
Data Transmission
125
GPRS Review
ISSUE 1 REVISION 2
126
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
TAI= message 4
127
GPRS Review
ISSUE 1 REVISION 2
128
ISSUE 1 REVISION 2
GPRS Review
PCU
RSS
MS
SYSTEM INFORMATION
129
GPRS Review
ISSUE 1 REVISION 2
130
ISSUE 1 REVISION 2
GPRS Review
PCU
RSS
MS
SYSTEM INFORMATION SYSTEM INFORMATION 3, 13 BCCH PAGING PACKET PAGING REQUEST (PCH) PACKET CHANNEL REQUEST (RACH) PACKET IMMEDIATE ASSIGNMENT (AGCH)
PDU (PDTCH)
131
GPRS Review
ISSUE 1 REVISION 2
132
ISSUE 1 REVISION 2
GPRS Review
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
133
GPRS Review
ISSUE 1 REVISION 2
134
ISSUE 1 REVISION 2
GPRS Review
PCU
ACCESS AND ASSIGNMENT
MS
135
GPRS Review
ISSUE 1 REVISION 2
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.
136
ISSUE 1 REVISION 2
GPRS Review
LLC
LLC
RLC
RLC
FH
INFORMATION FIELD
FCS
LLC
RLC/MAC
NORMAL BURST
NORMAL BURST
NORMAL BURST
NORMAL BURST
PHYSICAL LAYER
137
GPRS Review
ISSUE 1 REVISION 2
138
ISSUE 1 REVISION 2
GPRS Review
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
139
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.
140
ISSUE 1 REVISION 2
GPRS Review
Release of uplink
15
BS_CV_MAX= 4
141
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 PTMSI 2. Old RAI Classmark CKSN Attach Type DRX Old PTMSI 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.
142
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
143
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: PTMSI VLR TMSI
9. 10.
If the PTMSI 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.
144
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
145
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.
146
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
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
147
GPRS Review
ISSUE 1 REVISION 2
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.
148
ISSUE 1 REVISION 2
GPRS Review
MS
BSS
SGSN
1. PDP PDU 2. Paging Request 3. GPRS Page Request 4. Any LLC Frame 5. Any LLC Frame
149
GPRS Review
ISSUE 1 REVISION 2
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 NPDUs from GGSN before delivery) (subscribed or nonsubscribed APN)
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.
150
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
151
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 NetworkRequested 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.
152
ISSUE 1 REVISION 2
GPRS Review
PDP Context
MS
SGSN
HLR
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
153
GPRS Review
ISSUE 1 REVISION 2
NSAPI QoS Negotiated Radio Priority Level 4. The MS should acknowledge the new parameters before they take effect.
3.
154
ISSUE 1 REVISION 2
GPRS Review
1.Update PDP Context Request 2.Update PDP Context Response 3. Modify PDP Context Request 4. Modify PDP Context Accept
1. Deactivate PDP Context Request 2. Security Functions 3. Delete PDP Context Request 3. Delete PDP Context Response 4. Deactivate PDP Context Accept
1. Delete PDP Context Request 2. Deactivate PDP Context Request 2. Deactivate PDP Context Accept 3. Delete PDP Context Accept
155
GPRS Review
ISSUE 1 REVISION 2
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 intraSGSN 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 PTMSI Update Type (RA update indicated)
Security Functions may be executed The SGSN validates the MS and may issue a new PTMSI If a new PTMSI 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.
156
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
157
GPRS Review
ISSUE 1 REVISION 2
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 PTMSI 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 NPDUs to the New SGSN. Additional NPDUs received from the GGSN before timer in 2) above expires is also tunneled. The New SGSN sends Update PDP Context to GGSN:
158
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
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
159
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
If the Location Update is InterMSC 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: PTMSI VLR TMSI LLC Acknowledge PTMSI Signature
15. 16.
MS confirms allocation of TMSI and PTMSI and LLC acknowledge. The New SGSN sends TMSI reallocation complete message to VLR.
160
Chapter 2
PCU Architecture
ISSUE 1 REVISION 2
ii
ISSUE 1 REVISION 2
i
21 22 24 26 26 28 210 212 214 216 218 220 222 224 226 228 230 232 234 236 236 236 236 238 240 242 244 246
iii
ISSUE 1 REVISION 2
iv
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
21
ISSUE 1 REVISION 2
22
ISSUE 1 REVISION 2
SGSN
BSC
GDS (TRAU)
PCU
RSL RTF
BTS
23
ISSUE 1 REVISION 2
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 nonsystem 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.
24
ISSUE 1 REVISION 2
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
10
11 12 13
14 15 16
PRP or PICP
25
PSP
PPB
PSP
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.
26
ISSUE 1 REVISION 2
Device Equipage
PCU
CELL
CAGE
MSI MMS*
DRI
XBL MTL
PATH
16Kbps RSL
64Kbps RSL
RTF
Associated RTF
*Indicates auto-equipped device
27
Device Equipage
ISSUE 1 REVISION 2
28
ISSUE 1 REVISION 2
Device Equipage
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
MMS*
MMS*
GBL
GDS (TRAU)
GDS (TRAU)
29
Device Equipage
ISSUE 1 REVISION 2
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).
210
ISSUE 1 REVISION 2
Device Equipage
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
PP750
I/O
211
Device Equipage
ISSUE 1 REVISION 2
GB Manager
GB manager handling blocking/unblocking and reset
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.
212
ISSUE 1 REVISION 2
Device Equipage
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
LLC Cat
213
Device Equipage
ISSUE 1 REVISION 2
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.
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.
I/O Function
I/O function is used for routing between the functional units on the PRP and the PICP and PSP/
214
ISSUE 1 REVISION 2
Device Equipage
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
LLC Cat
215
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 nonvolatile 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.
216
ISSUE 1 REVISION 2
Device Equipage
217
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.
218
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
219
Device Equipage
ISSUE 1 REVISION 2
220
ISSUE 1 REVISION 2
Device Equipage
221
Device Equipage
ISSUE 1 REVISION 2
222
ISSUE 1 REVISION 2
Device Equipage
CRM
GBM
SGSN
BVC BLOCK
223
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.
224
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
BSC CA has been notified the PCU is inservice 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)
225
Device Equipage
ISSUE 1 REVISION 2
226
ISSUE 1 REVISION 2
Device Equipage
MS
RSS
ACCESS GRANT FU
MS
UPLINK FU
ASSEMBLE FU
GB
FR
SGSN
DATA BLOCK DATA BLOCK DATA BLOCK TEMPORARY PACKET ACK/NACK DATA BLOCK
227
Device Equipage
ISSUE 1 REVISION 2
228
ISSUE 1 REVISION 2
Device Equipage
(ON THE AGCH) PACKET RESOURCE REQUEST OPTIONAL PACKET RESOURCE ASSIGNMENT PACCH PACCH
MS
DL FU
SEGMENTATI ON
GB
FR
SGSN
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
229
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
230
ISSUE 1 REVISION 2
Device Equipage
BSSGP
BSSGP
NS
NS
FR
FR
EI
PCU
EI
SGSN
231
Device Equipage
ISSUE 1 REVISION 2
232
ISSUE 1 REVISION 2
Device Equipage
Transmit and Receive Buffers NVRAM MAPPING DLCI + GBL DLCI O PVC STATUS MESSAGES
233
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 NSVC (PVC) management procedures. The Gb Manager (GBM) maintains internal tables monitoring the state of BVCs and NSVCs 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 NSVC 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.
234
ISSUE 1 REVISION 2
Device Equipage
Gb Functional Unit
NST
Gb Router Gb Manager
235
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.
236
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
237
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.
238
ISSUE 1 REVISION 2
Device Equipage
Fault Management
Central Authority
239
Device Equipage
ISSUE 1 REVISION 2
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.
240
ISSUE 1 REVISION 2
Device Equipage
AGENT
pCA
pFTP
pFCP
PCU DEVICES
241
Device Equipage
ISSUE 1 REVISION 2
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.
242
ISSUE 1 REVISION 2
Device Equipage
Three types of Audit process Site System Audit Process (pSSAP) Cage System Audit Process (pCSAP) Device Audit Process
243
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 crossloaded to the DPROC boards equipped in the database with code objects at initialisation.
244
ISSUE 1 REVISION 2
Device Equipage
Configuration Management
BSC CM
BSC CA
PSP pCM
MASTER DATABASE
DPROC
DPROC
245
Device Equipage
ISSUE 1 REVISION 2
246
ISSUE 1 REVISION 2
Device Equipage
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
247
Device Equipage
ISSUE 1 REVISION 2
248
Chapter 3
BSS/PCU Commands
ISSUE 1 REVISION 2
ii
ISSUE 1 REVISION 2
i
31 32 32 32 34 36 38 38 38 310 312 314 316 318 320 322 324 326 328 330 332 334 336 338 340 342 344 346
iii
ISSUE 1 REVISION 2
iv
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
31
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
32
ISSUE 1 REVISION 2
PCU
equip 0 pcu
33
DPROC
ISSUE 1 REVISION 2
DPROC
The Data Processor Board is the nonsystem 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.
34
ISSUE 1 REVISION 2
DPROC
35
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 E1PMC to add this interface card to the MSI device. To equip the E1PMC MSI can only be carried out at a PCU. A maximum of 12 DPROC PICP MSIs can be equipped with a maximum of two E1PMCs to any PICP. Each PRP may be equiped with up to 2 MSI. The first identifier of the E1PMC must be unique, the second refers to the DPROC that the E1PMC is mounted on. The final prompt for the DPROC socket refers to the module identifier for the DPROC board that the E1PMC is being equipped. Each DPROC is capable of holding two E1PMCs.
36
ISSUE 1 REVISION 2
MSI
37
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 nonzero 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.
38
ISSUE 1 REVISION 2
MMS Device
E1 GBL E1
PMC 860 E1
39
ISSUE 1 REVISION 2
310
ISSUE 1 REVISION 2
Enter the GDS Identifier: <*> * 011 Enter the BSC MMS Identifier: <*> <*> Enter the PCU MMS Identifier: <*> <*> Enter the GDS type: <*> 0 TRAU GDS 1 LAPD GDS
311
ISSUE 1 REVISION 2
312
ISSUE 1 REVISION 2
313
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.
314
ISSUE 1 REVISION 2
GBL Device
Enter the GBL identifier: <*> * 03 Enter the 1st and 2nd MMS identifier: <*> <*> * MSI id 011 * MMS id 0 or 1 Enter starting timeslot: <*> * 131 Enter the ending timeslot: <*> * 131 Enter the T391 timer: <*> * 529 seconds Enter the T392 timer: <*> * 630 seconds Enter the N391 counter: <*> * 1255 polling cycles Enter the N392 counter: <*> * 110 number of errors Enter the N393 counter: <*> * 110 number of events
EMOTOROLA LTD. 2000
315
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
316
ISSUE 1 REVISION 2
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: <*> * 06
317
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 nonBCCH. The maximum number of GPRS timeslots configured depends on whether a separate GPRS carrier is provided. If a nonBCCH 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.
318
ISSUE 1 REVISION 2
GPRS Carrier
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
319
ISSUE 1 REVISION 2
320
ISSUE 1 REVISION 2
Reconfiguration
321
ISSUE 1 REVISION 2
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 resend the BVC_UNBLOCK PDU for BVC_UNBLOCK RETRIED. On receipt of a BVC_UNBLOCK ACK from a SGSN the BVC is marked as unblocked.
322
ISSUE 1 REVISION 2
BVC Block/Unblock
PCU
T1
T1
T1
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
323
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 resend 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.
324
ISSUE 1 REVISION 2
BVC Reset
BVC Reset
PCU
T2
ACTIVATED
T2
T2
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
325
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 LLCSDU. 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 LLCSDU at the SGSN from the GGSN R = Leak rate of the bucket at the PCU When an LLCSDU packet arrives at current time Tc, the variable B* is set to the predicted bucket size as if the LLCSDU was sent to the BSS. This is given by the previous bucket size plus the new LLCSDU size B* = B + L(p). To take account of the leakage since the last compliant LLCSDU packet the calculation R* (TcTp) is used. If B* is less than zero then the Bucket Counter is set to the L(p) of the LLCSDU as is Tp set to Tc and the LLCSDU 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.
326
ISSUE 1 REVISION 2
Flow Control
Flow Control
Arrival of LLC PDU p with length L(p) at time Tc
B* < 0 ? no
yes B= L(p)
B* >Bmax ?
no B= B* Tp= Tc
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
327
ISSUE 1 REVISION 2
328
ISSUE 1 REVISION 2
Network Service
NS_BLOCK TIMER
PCU
SGSN
NS_BLOCK TIMER
NS_UNBLOCK PDU
NS_BLOCK TIMER
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
329
ISSUE 1 REVISION 2
330
ISSUE 1 REVISION 2
NS_ALIVE TIMER
NS_ALIVE PDU
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
331
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 (NSVL). Each NSVL 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).
332
ISSUE 1 REVISION 2
Network Service
Network Service
RLC
Gb BSS
END TO END NSVC
SGSN
FRAME RELAY
BSS
NETWORK
SGSN
333
ISSUE 1 REVISION 2
334
ISSUE 1 REVISION 2
NS CONTROL FR NS VLI
NS CONTROL NS VLI FR
FR NETWORK
335
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.
336
ISSUE 1 REVISION 2
Gb Addressing
Gb Addressing
BSS #1
SGSN BVC1=2 NSVC1=a NSVC1=b BVC1=3 DLCI=137 NSVC1=a BVC1=2 DLCI=16 PTP Cell 1 DLCI=98 NSVC1=b DLCI=17
E1
Bearer Channel = 5
Bearer Channel = 1
E1
NSVC1=e DLCI=16
BVC1=3
Bearer Channel = 2 E1
FRAME RELAY
NSE1=1 BVC1=0
Signalling
BVC1=0
BSS #2
BVC1=2 NSVC1=e DLCI=16 PTP Cell 1 NSE1=2 NSVC1=f DLCI=259 Signalling BVC1=0
NETWORK
Bearer Channel = 4 E1
E1
NSE1=2
337
ISSUE 1 REVISION 2
338
ISSUE 1 REVISION 2
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
339
ISSUE 1 REVISION 2
A BVCI must be mapped to a cell before a BVCI may be mapped to an NSVC group.
340
ISSUE 1 REVISION 2
MMIRAM 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
341
ISSUE 1 REVISION 2
342
ISSUE 1 REVISION 2
SIG BVCI
343
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
344
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> *07
345
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.
346
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> *07 gprs_ms_pan_inc <*><site id> Cell <cell id> gprs_ms_pan_max <*> <site id> Cell <cell id>
347
N3102
ISSUE 1 REVISION 2
348
Chapter 4
ISSUE 1 REVISION 2
ii
ISSUE 1 REVISION 2
i
41 41 42 42 42 42 43 43 43 43 44 49 410 411 412 413 414 415 416 417 418 423 424 425 426 427 428 429 430 431 433 437 438 439 440 441 442
iii
ISSUE 1 REVISION 2
iv
ISSUE 1 REVISION 2
41
ISSUE 1 REVISION 2
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
42
ISSUE 1 REVISION 2
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
43
ISSUE 1 REVISION 2
DLCI = 45
DLCI = 55
GBL_DL_DATA_THRPUT
GBL_DL_DATA_THRPUT_TIME_PERIOD
44
ISSUE 1 REVISION 2
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
GBL_FLOW_CTRL_SENT
45
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
46
ISSUE 1 REVISION 2
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
47
ISSUE 1 REVISION 2
DLCI = 45
DLCI = 55
GBL_UL_DATA_THRPUT
GBL_UL_DATA_THRPUT_TIME_PERIOD
48
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
49
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
410
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
411
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
412
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
413
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
414
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
415
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
416
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
417
ISSUE 1 REVISION 2
CHANNEL_REQ_REJ
418
ISSUE 1 REVISION 2
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
GPRS_ACCESS_PER_RACH
419
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
420
ISSUE 1 REVISION 2
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
MS_CLASS_1_10_REQ
MS_CLASS_11_20_REQ
MS_CLASS_21_29_REQ
CHANNEL_REQ_REC
421
ISSUE 1 REVISION 2
TCH
SW SW SW RES RES RES GPRS GPRS GPRS GPRS GPRS GPRS GPRS
SW
GPRS_CHANNELS_SWITCHED
TCH
TCH
422
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
423
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
Basis Type
424
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
425
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
426
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
427
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
None.
Cell. Counter.
428
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
429
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
430
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
431
MS_CLASS_21_29_REQ
ISSUE 1 REVISION 2
432
ISSUE 1 REVISION 2
BSS/PCU
MS
DATA BLOCK
AIR_UL_DATA_BLKS
433
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
DATA BLOCK
AIR_DL_DATA_BLKS
434
ISSUE 1 REVISION 2
MS 5
MS DL_CHAN_ASGN_DURATION
35
2 PDCH
II
1
I
2 3 4 5
435
ISSUE 1 REVISION 2
MS 5
MS UL_CHAN_ASGN_DURATION
35
2 PDCH
II
1
I
2 3 4 5
436
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.
437
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.
438
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
439
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
Basis Type
440
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
Basis Type
441
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
442
Chapter 5
GSN Architecture
ISSUE 1 REVISION 2
ii
ISSUE 1 REVISION 2
i
51 52 52 54 56 58 510 512 514 516 518 520 522 524 526 528 530 532 534 536 538 540 540 540 542 544 546 548 548 550 552 554 556 558 560 560 562 564
iii
ISSUE 1 REVISION 2
iv
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
51
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.
52
ISSUE 1 REVISION 2
GPRS Overview
53
GPRS Overview
ISSUE 1 REVISION 2
54
ISSUE 1 REVISION 2
GPRS Overview
System Framework
OMC-G
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 SGSNCONTROL 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 SGSNGNPROC and the SGSNGBPROC. SGSNGNPROC 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 SGSNGBPROC. The GNPROC contains microscopic MS context information; MS MM state, PDP state and cell location. SGSNGBPROC 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.
56
ISSUE 1 REVISION 2
GPRS Overview
SGSN Architecture
SS7 FUNCTION SF
HLR
CONTROL FUNCTION
BSS
57
GPRS Overview
ISSUE 1 REVISION 2
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 SGSNcontrol and SGSNOAMP. The Control function holds the OAMP function for the CF and the TF.
Transmission Function
The SGSNGBPROC and SGSNGNPROC 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.
58
ISSUE 1 REVISION 2
GPRS Overview
SF
SGSNCF
SGSN TF
SF
OAMP tf
BSC
59
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 HotSwap 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 offtheshelf Compact PCI hardware.
510
ISSUE 1 REVISION 2
GPRS Overview
511
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.
512
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
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
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
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
513
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 nonsystem processors.
514
ISSUE 1 REVISION 2
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
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.
516
ISSUE 1 REVISION 2
GPRS Overview
517
GPRS Overview
ISSUE 1 REVISION 2
518
ISSUE 1 REVISION 2
GPRS Overview
519
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 onboard 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.
520
ISSUE 1 REVISION 2
GPRS Overview
521
GPRS Overview
ISSUE 1 REVISION 2
522
ISSUE 1 REVISION 2
GPRS Overview
FORCE SERIAL
Line 1
Line 2
E1IRD
523
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 PTMSI 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.
524
ISSUE 1 REVISION 2
GPRS Overview
MS
ATTACH REQUEST
CF
IDENTITY REQUEST
IDENTITY RESPONSE
525
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. SMSrelated parameters, e.g. operatordetermined 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 protocolconverting GSN as described in the subclauses MAPbased GGSN HLR Signalling and GTP and MAPbased GGSN HLR Signalling.
GGSNlist
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.
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.
526
ISSUE 1 REVISION 2
GPRS Overview
MS
ATTACH REQUEST IDENTITY REQUEST IDENTITY RESPONSE
CF
HLR
UPDATE LOCATION
527
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.
T = Bits derived from PTMSI R = Random Bits A local TLLI is the same as a PTMSI with the high order bits 31 and 30 set to one and the rest of the bits set to the PTMSI. 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 PTMSI as Local TLLI = PTMSI.
528
ISSUE 1 REVISION 2
GPRS Overview
MS
ATTACH REQUEST IDENTITY REQUEST
CF
HLR
TF
ATTACH COMPLETE
529
GPRS Overview
ISSUE 1 REVISION 2
ATTACH
The SGSN CF, upon return of the complete Local TLLI/PTMSI 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 14 Routing Area Identification Alloc PTMSI PTMSI = Local TLLI Ready Timer Value SGSN Configured Value
The GPRS Mobility Management (GMM) context at the SGSN CF will go to GMMREGISTERED 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 GMMREGISTERED.
MAX_ACCEPT_ATTEMPT
Attach Accept
T3350
STARTED STOPPED
RESEND 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.
530
ISSUE 1 REVISION 2
GPRS Overview
MS
ATTACH REQUEST
CF
HLR
TF
UPDATE LOCATION
CREATE MMCTx CNF ATTACH ACCEPT START T3350 ATTACH COMPLETE STOP T3350
531
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.
532
ISSUE 1 REVISION 2
GPRS Overview
MS
DETACH REQUEST
SGSN
DETACH RESPONSE
MS
SGSN
533
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.
534
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
535
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.
536
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
537
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.
538
ISSUE 1 REVISION 2
GPRS Overview
MS
SGSN CF
TLLI, IMSI
SGSN TF
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)
(TLLI, IMSI)
539
GPRS Overview
ISSUE 1 REVISION 2
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.
540
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 BLOCKTxREQ (TLLI) BLOCKTxREQ (TLLI) MODIFY MMCtxREQ TLLI, IMSI, NEW CGI, TIMER VALUES, MS RADIO ACCESS CAPAB, DRX PARAMETERS MODIFY MMCtxCNF
ROUTING AREA ACCEPT TLLI, IMSI, Force to Stby, update result, RDY timer TLLI, IMSI, RESULT Unblock TxREQ Unblock TxCNF (TLLI)
(TLLI)
541
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.
542
ISSUE 1 REVISION 2
Session Management
INACTIVE
ACTIVE
543
Session Management
ISSUE 1 REVISION 2
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.
544
ISSUE 1 REVISION 2
Session Management
MS
SGSN CF
ACTIVATE PDP CONTEXT REQUEST
CONTEXT FOR MS
545
Session Management
ISSUE 1 REVISION 2
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.
546
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
547
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.
548
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
SGSN TF
Activate Uplink_REQ Activate Uplink_CNF
549
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.
550
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
SGSN TF
Activate Uplink_REQ Activate Uplink_CNF Activate PDP Context Accept SET PDP CONTEXT Activate Downlink_REQ Activate Uplink_CNF
551
Session Management
ISSUE 1 REVISION 2
552
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
SGSN TF
Delete PDPCtxRequest (TLLI, IMSI, NSAPI) Delete PDPCtxResponse Deactivate PDPContext Accept (TLLI, IMSI, TI, CAUSE) GO INACTIVE (TLLI, IMSI, NSAPI, RESULT CODE)
553
Session Management
ISSUE 1 REVISION 2
554
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
555
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.
556
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
557
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.
558
ISSUE 1 REVISION 2
Session Management
GGSN
Gn
CONTROL INTERFACE
Negotia tion *
Gb
L3MM
BSS
MS
CONTROL FUNCTION
559
Session Management
ISSUE 1 REVISION 2
560
ISSUE 1 REVISION 2
Session Management
ORIGINATOR
RECEIVER
SNDCP
LL_XID_REQ
LLC
LLC
SNDCP
LL_XID_CNF
561
Session Management
ISSUE 1 REVISION 2
562
ISSUE 1 REVISION 2
Session Management
563
Session Management
ISSUE 1 REVISION 2
564
ISSUE 1 REVISION 2
Session Management
SGSN
Create PDP Context Request
GGSN
565
Session Management
ISSUE 1 REVISION 2
566
Chapter 6
ISSUE 1 REVISION 2
ii
ISSUE 1 REVISION 2
61
ISSUE 1 REVISION 2
62
ISSUE 1 REVISION 2
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
63
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
64
ISSUE 1 REVISION 2
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
65
ISSUE 1 REVISION 2
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 sgsnOMCIpAddress sgsnDefaultAPN sgsnVersion sgsnNetwork OperatorIdMCC sgsnNetworkOperatorId-MNC sgsnDiagConfigFileName sgsnDumpConfigFileName sgsnLoadConfigFileName sgsnLoggingState sgsnTracingState parameter
66
ISSUE 1 REVISION 2
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 sgsnSNDCPVersionNum sgsnSNDCPDataCompressionAlgorithm sgsnNDCPHeaderCompressionAlgorithm sgsnNDCPCompressionDirection sgsnNDCPMaxCompressionCodewords sgsnNDCPMaxCodewordLength sgsnNDCPCompressorShared
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
67
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
parameter
68
ISSUE 1 REVISION 2
parameter sgsnGbFRLineBuildOut
69
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
610
ISSUE 1 REVISION 2
611
ISSUE 1 REVISION 2
OMC-G
IP Address = sgsnOmcIpAddress
SGSN
OAMP Agent
612
ISSUE 1 REVISION 2
OMC-G
SNMP
Interface
SNMP
SGSN Application
613
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
614
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
615
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
616
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
617
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
Format
3 decimal digits in ASCII format, with 0 padded at the front.
Example
References
CCITT Rec E.212 Annex A
618
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
Format
2 decimal digits in ASCII format, with 0 padded at the front.
Example
References
GSM 03.03 v6.1.0
619
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
620
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
621
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
622
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
623
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
624
ISSUE 1 REVISION 2
SGSN
Create PDP Context Request
GGSN
T3
repeated N3 times
625
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
626
ISSUE 1 REVISION 2
IDLE
GPRS Attach
GPRS Detach
READY
PDU Reception
STANDBY
627
ISSUE 1 REVISION 2
BSS#1 SGSN CF
PageInd
Page PSPDU
Start T3313
BSS#2
MS
Stop T3313
sgsnDnLinkPagingT imer
Range 3 15 Secs Default 8
628
ISSUE 1 REVISION 2
PageInd
Page PSPDU
Start T3313
BSS#2
BSS#1
Page PSPDU
sgsnMaxPagingAttempts
Range 1 5 Default 2
629
ISSUE 1 REVISION 2
sgsnNsTnsBlockTimer
Range 1 30 Secs Default 3
630
ISSUE 1 REVISION 2
sgsnNsTnsResetTimer
Range 1 60 Secs Default 3
631
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
632
ISSUE 1 REVISION 2
SGSN
TNS Block
NS Block PDU
TNS Block
sgsnNsTnsBlockRetries
Range 1 30 Default 3
633
ISSUE 1 REVISION 2
SGSN
TNS Unblock
NS Unblock PDU
TNS Unblock
sgsnNsTnsUnblockRetries
Range 1 30 Default 3
634
ISSUE 1 REVISION 2
SGSN
TNS Alive
NS Alive PDU
TNS Alive
sgsnNsTnsAliveRetries
Range 1 30 Default 3
635
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
636
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
637
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 sgsnNSTnsResetTimer 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
638
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
639
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
640
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
641
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
642
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
643
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
644
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: X6 < 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
645
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: X2 < 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: X60 < 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
Format
Example
References
GSM 04.08 v5.6.2, CR A265 Rev 5
646
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
647
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.
648
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: X6 < 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
649
ISSUE 1 REVISION 2
DLCI = 45
DLCI = 177
sgsnFrBearerChannelId
Range: 0 30 Default 0
650
ISSUE 1 REVISION 2
BSS
DTE Gb
DTE Gb
SGSN
sgsnFrDteDce
Range: 0 = DCE 1 = DTE
651
ISSUE 1 REVISION 2
User
T391 T392
Status
N391
Status Enquiry
Status
Full Status
sgsnFrN391
Range: 1 255 Default 6
sgsnFrT392
Range: 6 30 Secs Default 15
sgsnFrT391
Range: 5 29 Secs Default 10
652
ISSUE 1 REVISION 2
No Status Enquiry
N393
T392
N392
sgsnFrN392
Range 1 10 Default 3
sgsnFrN393
Range 1 10 Default 4
653
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
654
ISSUE 1 REVISION 2
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.
Bearer Link
DLCI = 177 Bearer Channel 2 DLCI = 23
sgsnNsvcFrPvcBearerChannelId
Range: 0 30 Default 0
sgsnNsvcFrPvcPhyLinkId
Range: 0 3 Default 0
655
ISSUE 1 REVISION 2
Bc + Be
Discard On Entry
T sgsnNsvcFrPvcBc
Range: 1 2048000 Default 1
sgsnNsvcFrPvcCIR
Range 1 2048000 Default 1
sgsnNsvcFrPvcBe
Range: 1 2048000 Default 0
656
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
657
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
658
ISSUE 1 REVISION 2
sgsnGb-FR-Entry
Example
References
659
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
660
ISSUE 1 REVISION 2
sgsnGbFR-LinkId
sgsnGbFR-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
661
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
662
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
663
sgsnGbFR-LMI-DLCI
ISSUE 1 REVISION 2
sgsnGbFR-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
664
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
Format
Example
References
665
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
666
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
667
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
668
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
669
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
670
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
671
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
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
672
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
673
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
674
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
675
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
676
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
677
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
678
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
679
sgsnMaxActivePDP-ContextPerIMSI
ISSUE 1 REVISION 2
sgsnMaxActivePDP-ContextPerIMSI
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
680
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
681
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
682
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
683
sgsnSNDCPCompressionDirection
ISSUE 1 REVISION 2
sgsnSNDCPCompressionDirection
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
Format
Example
References
684
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
685
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
686
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
687
sgsnGb-NSVC-Table
ISSUE 1 REVISION 2
sgsnGb-NSVC-Table
Description
This table lists the NSVCs 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
688
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
689
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
690
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
691
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
692
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
693
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
694
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
695
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
696
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
697
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
698
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
699
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
6100
ISSUE 1 REVISION 2
SGSN START T1
STOP T1
sgsnBssgpT1
Range 1 30 Secs Default 3
6101
ISSUE 1 REVISION 2
SGSN START T2
STOP T2
sgsnBssgpT2
Range 1 1000 Secs Default 60
6102
ISSUE 1 REVISION 2
SGSN T1
BVC Block
T1
sgsnBssgpBvcBlockRetries
Range 1 30 Default 3
6103
ISSUE 1 REVISION 2
SGSN T1
BVC Unblock
T1
sgsnBssgpBvcUnblockRetries
Range 1 30 Default 3
6104
ISSUE 1 REVISION 2
SGSN T2
BVC Reset
T2
sgsnBssgpBvcResetRetries
Range 1 30 Default 3
6105
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
6106
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
6107
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
6108
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
6109
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
Format
Example
References
6110
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
6111
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
6112
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
6113
sgsnBSSGPT2
ISSUE 1 REVISION 2
sgsnBSSGPT2
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
6114
ISSUE 1 REVISION 2
sgsnBSSGPBVC-BlockRetries
sgsnBSSGPBVC-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
6115
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
6116
ISSUE 1 REVISION 2
sgsnBSSGP-BVC-ResetRetries
sgsnBSSGP-BVC-ResetRetries
Description
This parameter indicates the number of attempts to retry a BVC-RESET.
Format
Example
Attributes
Value type Valid range Default value
integer 1 to 30 3
References
6117
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
6118
ISSUE 1 REVISION 2
sgsnGb-Cell-BVC-TableEntry
sgsnGb-Cell-BVC-TableEntry
Description
Each entry defines one <CGI, PTPBVCI> 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
6119
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
6120
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
6121
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
6122
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
6123
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
6124
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
6125
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.
Attributes
Value type Valid range Default value Dependencies Access Status
not accessible mandatory
Format
Example
References
6126
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
6127
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
6128
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
6129
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
6130
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
6131
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
6132
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
6133
sgsnSigPlaneInfoSIG-BVCI
ISSUE 1 REVISION 2
sgsnSigPlaneInfoSIG-BVCI
Description
This parameter identifies the Signalling BVCI of a PCU and must be defined in sgsnGbBVC-Table.
Attributes
Value type Valid range Default value Dependencies Access Status
read only mandatory integer 1 to 65535
Format
1 bytes integer
Example
References
6134
Chapter 7
ISSUE 1 REVISION 2
ii
ISSUE 1 REVISION 2
71
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
Attributes Tables
Details of the attributes available for each performance management object can be found in the following tables:
72
ISSUE 1 REVISION 2
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
73
ISSUE 1 REVISION 2
74
ISSUE 1 REVISION 2
sgsnNumSessionActivationSent
sgsnNumSuccessSessionActivationRcvd
OR PDP CONTEXT REJECT
sgsnNumUnsuccessSessionActivationRcvd
75
ISSUE 1 REVISION 2
sgsnNumProtocolErrorTooShort
sgsnNumProtocolErrorWrongHeader
SIGNALLING PDU
sgsnNumProtocolErrorUnexpectedMsg
76
ISSUE 1 REVISION 2
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
77
ISSUE 1 REVISION 2
Uplink
sgsnNumGtpUpLinkDataPacketsRcvd sgsnNumGtpUpLinkDataBytesRcvd sgsnNumGtpDataPacketsSentT oGGSN sgsnNumGtpDataBytesSentT oGGSN sgsnNumGtpUpLinkDataPacketsDropped
SNDCP
SNDCP
LLC
LLC
MS
BSS
SGSN
GGSN
78
ISSUE 1 REVISION 2
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
79
ISSUE 1 REVISION 2
Uplink
sgsnNumSndcpUpLinkDataPacketsRcvd sgsnNumSndcpUpLinkDataBytesRcvd sgsnNumSndcpUpLinkDataPacketsSent sgsnNumSndcpUpLinkDataBytesSent sgsnNumSndcpUpLinkDataPacketsDropped
SNDCP
SNDCP
LLC
LLC
Uplink Rcvd BSSGP BSSGP IP Downlink Sent Network Network L2 Service Service L1 Bis L1 Bis L1
MS
BSS
SGSN
GGSN
710
ISSUE 1 REVISION 2
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
711
ISSUE 1 REVISION 2
Uplink
sgsnNumLlcUpLinkDataPacketsRcvd sgsnNumLlcUpLinkDataBytesRcvd sgsnNumLlcUpLinkSignalPacketsRcvd sgsnNumLlcUpLinkSignalBytesRcvd sgsnNumLlcUpLinkDataPacketsSent sgsnNumLlcUpLinkDataBytesSent sgsnNumLlcUpLinkSignalPacketsSent sgsnNumLlcUpLinkSignalBytesSent sgsnNumLlcUpLinkDataPacketsDropped sgsnNumLlcUpLinkSignalPacketsDropped
SNDCP
LLC
LLC
BSSGP
MS
BSS
SGSN
GGSN
712
ISSUE 1 REVISION 2
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
713
ISSUE 1 REVISION 2
Uplink
sgsnNumBssgpUpLinkDataPacketsRcvd sgsnNumBssgpUpLinkDataBytesRcvd sgsnNumBssgpUpLinkDataPacketsSent sgsnNumBssgpUpLinkDataBytesSent sgsnNumBssgpUpLinkDataPacketsDropped
IP Uplink Sent GTP SNDCP Downlink Rcvd LLC TCP/ UDP IP L2 L1 Uplink Rcvd
IP
SNDCP
LLC
714
ISSUE 1 REVISION 2
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
715
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
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
MS
BSS
Downlink Sent
GGSN
716
ISSUE 1 REVISION 2
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
717
ISSUE 1 REVISION 2
sgsnNumL3mmAttachReqRcvd
ATTACH ACCEPT
sgsnNumL3mmAttachAcceptSent
OR ATTACH REJECT
sgsnNumL3mmAttachRejectSent
718
ISSUE 1 REVISION 2
sgsnNumL3mmDetachReqRcvd
DETACH ACCEPT
sgsnNumL3mmDetachAcceptSent
719
ISSUE 1 REVISION 2
sgsnNumL3mmSessionActivateReqRcvd
sgsnNumL3mmSessionActivateAcceptSent
OR SESSION ACTIVATION REJECT
sgsnNumL3mmSessionActivateRejectSent
720
ISSUE 1 REVISION 2
sgsnNumL3mmSessionDeactivateReqRcvd
sgsnNumL3mmSessionDeactivateAcceptSent
721
ISSUE 1 REVISION 2
sgsnNumL3mmRAUpdateReqRcvd
RA UPDATE ACCEPT
sgsnNumL3mmRAUpdateAcceptSent
OR RA UPDATE REJECT
sgsnNumL3mmRAUpdateRejectSent
722
ISSUE 1 REVISION 2
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
723
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 )
724
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 )
725
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 )
726
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 )
727
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 )
728
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 )
729
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 )
730
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 )
731
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 )
732
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 )
733
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 )
734
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 )
735
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 )
736
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 )
737
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 )
738
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 )
739
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 )
740
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 )
741
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 )
742
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 )
743
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 )
744
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 )
745
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 )
746
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 )
747
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 )
748
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 )
749
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 )
750
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 )
751
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 )
752
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 )
753
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 )
754
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 )
755
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 )
756
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 )
757
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 )
758
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 )
759
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 )
760
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 )
761
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 )
762
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 )
763
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 )
764
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 )
765
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 )
766
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 )
767
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 )
768
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 )
769
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 )
770
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 )
771
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 )
772
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 )
773
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 )
774
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 )
775
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 )
776
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 )
777
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 )
778
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 )
779
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 )
780
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 )
781
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 )
782
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 )
783
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 )
784
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 )
785
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 )
786
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 )
787
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 )
788
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 )
789
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 )
790
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 )
791
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 )
792
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 )
793
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 )
794
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 )
795
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 )
796
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 )
797
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 )
798
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 )
799
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 )
7100
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 )
7101
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 )
7102
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 )
7103
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 )
7104
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 )
7105
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 )
7106
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 )
7107
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 )
7108
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 )
7109
sgsnNumCells
ISSUE 1 REVISION 2
7110
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 )
7111
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 )
7112
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 )
7113
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 )
7114
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 )
7115
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 )
7116
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 )
7117
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 )
7118
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 )
7119
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 )
7120
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 )
7121
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 )
7122
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 )
7123
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 )
7124
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 )
7125
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 )
7126
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 )
7127
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 )
7128
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 )
7129
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 )
7130
ISSUE 1 REVISION 2
FR stats
FR stats
Details of Fr statistics attributes not available at this time.
7131
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 )
7132
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 )
7133
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 )
7134
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 )
7135
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 )
7136
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 )
7137
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 )
7138
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 )
7139
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 )
7140
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 )
7141
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 )
7142
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 )
7143
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 )
7144
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 )
7145
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 )
7146
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 )
7147
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 )
7148
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 )
7149
sgsnNumCells
ISSUE 1 REVISION 2
7150
Chapter 8
ISSUE 1 REVISION 2
ii
ISSUE 1 REVISION 2
i
31 31 31 32 32 35 36 37 38 39 310 311 312 313 314 315 316 318 319 320 321 322 323 324 325 326 327 328 329
iii
ISSUE 1 REVISION 2
iv
ISSUE 1 REVISION 2
81
ISSUE 1 REVISION 2
(2) Ggsn
(2) Notifications
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
82
ISSUE 1 REVISION 2
83
ISSUE 1 REVISION 2
84
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
85
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
86
ISSUE 1 REVISION 2
cgprsGtpCurUnexpectedRxGpduCount
cgprsGtpCurUnexpectedRxGpduCount
Description
The total number of GPDUs received from a SGSN for a nonexisting or an inactive PDP context since system startup.
Pegging
?
Analysis
?
Reference
?
Usage
?
Basis
GTP
Statistic
Statistic Type
Counter
Statistic Data
PDUs
87
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
88
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
89
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 )
810
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
?
811
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
812
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
813
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
814
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
815
cgprsGtpGSNTable
ISSUE 1 REVISION 2
cgprsGtpGSNTable
Description
GSN peer table. The SGSNGGSN 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 MultipleMultiple 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.
Syntax
SEQUENCE OF CgprsGtpGSNEntry
Format
Example ???
Values
Value type Valid range Default value
816
ISSUE 1 REVISION 2
cgprsGtpGSNTable
References
817
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.
Syntax
cgprsGtpGSNEntry
Format
CgprsGtpGSNEntry ::= SEQUENCE{ cgprsGtpGSNid cgprsGtpGSNEchoFailedNotificationCount }
Example
?
Values
Value type Valid range Default value
??? ??? ???
References
?
818
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
?
819
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
?
820
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
821
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
?
822
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
?
823
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
?
824
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
?
825
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
?
826
ISSUE 1 REVISION 2
cgprsGtpNumAllocIpAddrTable
cgprsGtpNumAllocIpAddrTable
Description
The table for currently allocated number of dynamic addresses associated with a given APN.
Syntax
SEQUENCE OF CgprsGtpNumAllocIpAddrEntry
Format
???
Example
Values
Value type Valid range Default value
??? ??? ???
References
?
827
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.
Syntax
cgprsGtpNumAllocIpAddrEntry
Format
CgprsGtpNumAllocIpAddrEntry ::= SEQUENCE{ cgprsGtpNumAllocIpAddr }
Example
?
Values
Value type Valid range Default value
??? ??? ???
References
?
828
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
?
829
cgprsGtpNumAllocIpAddr
ISSUE 1 REVISION 2
830
Chapter 9
Appendix
ISSUE 1 REVISION 2
ii
ISSUE 1 REVISION 2
Timer T3313
MAXPAGEATTEM PT T3312
T3312
Maximum number of attempts to page an MS GMM Periodic Routing Area Update Timer
T3314
T3314
T3315
T3315
N3
N3
bssgp_t1_timer
T1
bssgp_t2_timer
T2
bssgp_bock_retries
BVCBLOCK RETRIES
bssgp_unbock_retries
BVCUNBLOC KRETRIES
bssgp_reset_retries
BVCRESETR ETRIES
ns_block_timer
Tnsblock
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 NSVC blocking and unblocking Timer guards the NSVC reset proceddure Timer sets the period of the NSVC test proceedure. The NSVC is tested every ns_test_timer seconds
Value Default 8 Seconds Units: Seconds Range 3 15 Ref GSM 4.08 Default: 2 Range: 15 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: 260 Seconds in 2 second increments or 61180 in 60 second incerments. 1 Deactivates Timer 0 will force to standby Default: 60 Minutes Units: Miniutes Range: 6186 minutes in 6 minute incremetns. 1 deactivates timer Must be greater than T3312 Default: 3 Attempts Range: 15 Attempts Default: 3 Units: Seconds Range: 30120 Default: 60 Units: Seconds Range: 1120 Default: 3 Range: 13
Default: 3 Range: 13
Default: 3 Range: 13
ns_reset_timer
Tnsreset
ns_test_timer
Tnstest
Default: 3 Units: Seconds Range: 130 Defualt: 40 Units: Seconds Range: 1120 Default: 30 Units: Seconds Range: 160
91
ISSUE 1 REVISION 2
ns_alive_timer
Tnsalive
ns_block_retries
ns_unblock_retries
ns_alive_retries
ns_reset_period
bssgp_fc_period_c
gprs_bs_cv_max
bssgp_racap_retries
NSBLOCKRE Timer specifies the number TRIES of retries to block a NSVC. NS_UNBLOCK Timer specifies the number _RETRIES of retires generated to unblock the NSVC NS_ALIVE_RE Timer specifes the number TRIES of retries generated to establish if a NSVC is alive Timer specifies the period over which the BSS shall attempt to reset a NSVC 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 RACapabiltyUpdate messages
Default: 3 Units: Seconds Range: 130 Default: 3 Range: 13 Default: 3 Range: 13 Default: 3 Range: 110
Default: 125 Units: Seconds Range: 1250 Default: 10 Units: 10ths of a second Range 11000 Default: 6 Range: 015 Default: 3 Range: 13
92
Chapter 10
ISSUE 1 REVISION 2
ii
ISSUE 1 REVISION 2
i
91 92 95 98 912 915 917 919 921 922 924 925 927 931 933 935 938 939 942 946 949 950 951 952 953
iii
ISSUE 1 REVISION 2
iv
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
101
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. ACDC 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 acdc 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
102
ISSUE 1 REVISION 2
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
103
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
104
ISSUE 1 REVISION 2
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
105
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
BSSAP BSSC
106
ISSUE 1 REVISION 2
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
107
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
108
ISSUE 1 REVISION 2
CCIT
Comit Consultatif International Tlgraphique et Tlphonique. This term has been superceded by ITUTSS (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).
1 Cell = 1 Sector
End of charge point. Confrence des administrations Europennes 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.
109
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
1010
ISSUE 1 REVISION 2
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. Manufacturers 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
1011
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
DC PSM DCS1800
1012
ISSUE 1 REVISION 2
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 (Motorolas 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).
DRCU
1013
ISSUE 1 REVISION 2
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
1014
ISSUE 1 REVISION 2
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 (Motorolas 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
1015
ISSUE 1 REVISION 2
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
1016
ISSUE 1 REVISION 2
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).
FCP FCS FDM FDMA FDN FDP FEC FEP FER FFS, FS FH FIB FIR FK FM FM FMIC FMUX FN FOA FOX FR
1017
ISSUE 1 REVISION 2
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
1018
ISSUE 1 REVISION 2
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 users 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 subscribers 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 Spcial 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
1019
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
1020
ISSUE 1 REVISION 2
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.
HLR
HMS
1021
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
1022
ISSUE 1 REVISION 2
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
IWMSC IWU
1023
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.
1024
ISSUE 1 REVISION 2
L
L1 L2ML L2R Layer 1. Layer 2 Management Link. Layer 2 Relay function. A function of an MS and IWF that adapts a users known layer2 protocol LAPB onto RLP for transmission between the MT and IWF. L2R 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 ITUTSS 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.
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
1025
ISSUE 1 REVISION 2
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 BTSs 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
1026
ISSUE 1 REVISION 2
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
1027
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 (106). 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
1028
ISSUE 1 REVISION 2
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.
MT MT (0, 1, 2)
1029
ISSUE 1 REVISION 2
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
1030
ISSUE 1 REVISION 2
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 Europennes 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
NMASE NMC
1031
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 (109).
1032
ISSUE 1 REVISION 2
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 (BSCOMC). 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.
OMC-G OMC-G OMC-R OMC-S OMF OML OMP OMS OMSS OOS OPC
1033
ISSUE 1 REVISION 2
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.
1034
ISSUE 1 REVISION 2
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).
PCU PCU pd PD PD PDB PDCH PDF PDN PDN PDTCH PDU PDU PDU PEDC Peg Pegging PH PH
1035
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). Prsentation des Normes Europennes. 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 106). 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
1036
ISSUE 1 REVISION 2
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
1037
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.
1038
ISSUE 1 REVISION 2
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
1039
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
1040
ISSUE 1 REVISION 2
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.
1041
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
1042
ISSUE 1 REVISION 2
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.
SIM
SITE SIX
SK
1043
ISSUE 1 REVISION 2
SME SMG SMP SMS SMSCB SMS-SC SMS/PP Smt SN SND SNDCP SNDR SNPDU 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
1044
ISSUE 1 REVISION 2
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
1045
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
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
1046
ISSUE 1 REVISION 2
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 users 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.
Timing advance
TMSI
1047
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
1048
ISSUE 1 REVISION 2
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
1049
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
1050
ISSUE 1 REVISION 2
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
1051
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.
1052
ISSUE 1 REVISION 2
Z
ZC Zone Code
1053
ISSUE 1 REVISION 2
1054