Professional Documents
Culture Documents
68P02901W01 PDF
68P02901W01 PDF
68P02901W01 PDF
System Information
GSR9
68P02901W01-S
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Office.
Jul 2008
Table
of
Contents
Contents
68P02901W01-S i
Jul 2008
Contents
ii 68P02901W01-S
Jul 2008
System Information: GSM Overview Contents
68P02901W01-S iii
Jul 2008
Contents
E1 links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
Link types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
E1 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
BSC daisy chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
Standardized interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54
Interface types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54
GSM functional layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55
BSSAP messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56
ISDN messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
MSC to MS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
Location register interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
OMC interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
NMC interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
Interface summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Signaling links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
The A interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59
Abis interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59
Air interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60
Lb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
Network protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64
Protocol types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64
OSI/protocol relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-65
ITU-TSS signaling system 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-67
X.25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68
LAPDm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68
Signaling link protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68
GSM frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-69
Introduction to frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . 1-69
GSM850 frequencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-69
GSM850 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-70
Primary GSM900 frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-77
Primary GSM900 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-78
EGSM frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-84
EGSM channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-85
DCS1800 frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-88
DCS1800 frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-88
DCS1800 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-89
PCS1900 frequencies and channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-108
PCS1900 frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-108
PCS1900 channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-109
iv 68P02901W01-S
Jul 2008
System Information: GSM Overview Contents
68P02901W01-S v
Jul 2008
Contents
vi 68P02901W01-S
Jul 2008
System Information: GSM Overview Contents
68P02901W01-S vii
Jul 2008
Contents
viii 68P02901W01-S
Jul 2008
System Information: GSM Overview Contents
68P02901W01-S ix
Jul 2008
Contents
x 68P02901W01-S
Jul 2008
System Information: GSM Overview Contents
68P02901W01-S xi
Jul 2008
Contents
xii 68P02901W01-S
Jul 2008
System Information: GSM Overview Contents
68P02901W01-S xiii
Jul 2008
Contents
xiv 68P02901W01-S
Jul 2008
Contents
68P02901W01-S xv
Jul 2008
Contents
xvi 68P02901W01-S
Jul 2008
List
of
Figures
List of Figures
68P02901W01-S xvii
Jul 2008
List of Figures
xviii 68P02901W01-S
Jul 2008
List
of
Tables
List of Tables
Table 1-1: OMC-R functions and GSM and ITU-TSS references . . . . . . . . . . . . . . . . . 1-8
Table 1-2: OMC configurations (maximum values) . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Table 1-3: OMC-R/X.25 capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Table 1-4: Receiver specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Table 1-5: BSS software functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
Table 1-6: GSM interface summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Table 1-7: Network element signaling links . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Table 1-8: GSM Frequency types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-69
Table 1-9: GSM850 channels 128 to 130 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-70
Table 1-10: GSM850 channels 131 to 140 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71
Table 1-11: GSM850 channels 141 to 150 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71
Table 1-12: GSM850 channels 151 to 160 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-72
Table 1-13: GSM850 channels 161 to 170 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-72
Table 1-14: GSM850 channels 171 to 180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-73
Table 1-15: GSM850 channels 181 to 190 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-73
Table 1-16: GSM850 channels 191 to 200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-74
Table 1-17: GSM850 channels 201 to 210 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-74
Table 1-18: GSM850 channels 211 to 220 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-75
Table 1-19: GSM850 channels 221 to 230 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-75
Table 1-20: GSM850 channels 231 to 240 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-76
Table 1-21: GSM850 channels 241 to 251 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-76
Table 1-22: PGSM channels 1 to 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-78
Table 1-23: PGSM channels 11 to 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-78
Table 1-24: PGSM channels 21 to 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-79
Table 1-25: PGSM channels 31 to 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-79
Table 1-26: PGSM channels 41 to 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-80
Table 1-27: PGSM channels 51 to 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-80
Table 1-28: PGSM channels 61 to 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81
Table 1-29: PGSM channels 71 to 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81
Table 1-30: PGSM channels 81 to 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-82
Table 1-31: PGSM channels 91 to 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-82
Table 1-32: PGSM channels 101 to 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-83
Table 1-33: PGSM channels 111 to 120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-83
Table 1-34: PGSM channels 111 to 120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-84
Table 1-35: EGSM channels 975 to 984 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-85
Table 1-36: EGSM channels 985 to 994 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-86
Table 1-37: EGSM channels 995 to 1004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-86
Table 1-38: EGSM channels 1005 to 1014 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-87
Table 1-39: EGSM channels 1015 to 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-87
Table 1-40: DCS1800 channels 512 to 520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-89
Table 1-41: DCS1800 channels 521 to 530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-89
Table 1-42: DCS1800 channels 531 to 540 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-90
Table 1-43: DCS1800 channels 541 to 550 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-90
Table 1-44: DCS1800 channels 551 to 560 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91
Table 1-45: DCS1800 channels 561 to 570 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91
68P02901W01-S xix
Jul 2008
List of Tables
xx 68P02901W01-S
Jul 2008
System Information: GSM Overview List of Tables
68P02901W01-S xxi
Jul 2008
List of Tables
xxii 68P02901W01-S
Jul 2008
About
This
Manual
This manual supports the following Motorola BSS equipment: BTS4, BTS5, BTS6, BSSC, BSSC2,
ExCell4, ExCell6, TopCell, M-Cell2, M-Cell6, M-Cellmicro, M-Cellcity, M-Cellcity+, Horizon II
micro, Horizoncompact2, M-Cellaccess, Horizoncompact, Horizonmicro, Horizonmacro, and
Horizon II macro. The manual is an overview of the Global System for Mobile Communications
(GSM) as implemented by Motorola, and includes:
Chapter 1, Introduction to Motorola GSM.
The information is intended for use by GSM Operation and Maintenance staff.
68P02901W01-S 1
Jul 2008
Revision history
Revision history
Version information
The following table lists the supported versions of this manual in order of issue:
Service
CMBP Number Remarks
Request
NA NA NA
2 68P02901W01-S
Jul 2008
General information
General information
Purpose
Motorola documents are intended to instruct and assist personnel in the operation, installation,
and maintenance of the Motorola equipment and ancillary devices. It is recommended that all
personnel engaged in such activities be properly trained by Motorola.
Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
NOTE
If this document was obtained when attending a Motorola training course, it is not
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then Motorola automatically supplies corrections and posts on the Motorola
customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.
68P02901W01-S 3
Jul 2008
Text conventions
Text conventions
The following conventions are used in the Motorola documents to represent keyboard input
text, screen output text, and special key sequences.
Input
Output
CTRL-c or CTRL+C Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or Press the Ctrl, Shift, and C keys at the same time.
CTRL+SHIFT+C
ALT-f or ALT+F Press the Alt and F keys at the same time.
ALT+SHIFT+F11 Press the Alt, Shift and F11 keys at the same time.
Press the pipe symbol key.
RETURN or ENTER Press the Return or Enter key.
4 68P02901W01-S
Jul 2008
Contacting Motorola
Contacting Motorola
24hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Office.
Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
The document type
68P02901W01-S 5
Jul 2008
Security advice
Security advice
Motorola systems and equipment provide security parameters that the operator configures
based on their particular operating environment. Motorola recommends setting and using
these parameters following industry recognized security practices. Consider protecting the
confidentiality, integrity, and availability of information and assets. Assets include the ability
to communicate, information about the nature of the communications, and information about
the parties involved.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information, from the menu located to the left of the
Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local
Motorola Office.
6 68P02901W01-S
Jul 2008
Warnings, cautions, and notes
The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
WARNING
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
CAUTION
Caution text and consequence for not following the instructions in the caution.
Notes
NOTE
Note text.
68P02901W01-S 7
Jul 2008
Safety
Safety
General safety
NOTE
Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.
Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on
the minimum health and safety requirements regarding the exposure of workers to the
risks arising from physical agents (electromagnetic fields) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
8 68P02901W01-S
Jul 2008
Caring for the environment
The following information describes national or regional requirements for the disposal of
Motorola supplied equipment and for the approved disposal of surplus packaging.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Office.
In EU countries
The following information is provided to enable regulatory compliance with the European
Union (EU) directives and any amendments to these directives when using Motorola equipment
in EU countries.
European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction
with a recycling partner ensures that equipment is collected and recycled according to the
requirements of EU environmental law.
European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste
Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients
responsibility to ensure that packaging materials are collected and recycled according to the
requirements of EU environmental law.
In non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance
with national and regional regulations.
68P02901W01-S 9
Jul 2008
CMM labeling and disclosure table
The Peoples Republic of China requires that our products comply with China Management
Methods (CMM) environmental regulations. (China Management Methods refers to the
regulation Management Methods for Controlling Pollution by Electronic Information Products.)
Two items are used to demonstrate compliance; the label and the disclosure table.
Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identified in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years. The example shown
uses 50 years.
Logo 1 Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic
and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)
will not leak or mutate causing environmental pollution or bodily injury from the use of the
EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain
field-replaceable parts, such as battery modules, can have a different EFUP and are marked
separately.
The Disclosure table is intended only to communicate compliance with China requirements.
It is not intended to communicate compliance with EU RoHS or any other environmental
requirements.
10 68P02901W01-S
Jul 2008
Motorola document set
The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
With internet access available, to view, download, or order documents (original or revised), visit
the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or
contact your Motorola account representative.
Without internet access available, order hard-copy documents or CD-ROMs from your Motorola
Local Office or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.
A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY UNDER DEVELOPMENT.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
68P02901W01-S 11
Jul 2008
Data encryption
12 68P02901W01-S
Jul 2008
Chapter
This chapter provides a high-level overview of the Global System for Mobile communications
(GSM) that includes GSM850, GSM900, Extended GSM (EGSM), Digital Communications System
1800 (DCS1800) and Personal Communications System 1900 (PCS1900) digital cellular systems.
68P02901W01-S 1-1
Jul 2008
Overview of the Motorola GSM system Chapter 1: Introduction to Motorola GSM
The Motorola GSM cellular system provides radio coverage for communications with GSM
subscribers in a defined area. Its principle role is to support signaling and traffic channels for
Mobile Stations (MSs) across the Public Land Mobile Network (PLMN).
The GSM network incorporates a number of network elements to support mobile telephones and
other mobile equipment, known collectively as Mobile Stations, or MSs. These elements form
the major components of the GSM network.
The Network Management Center (NMC) administers the entire cellular network to provide
Operation and Maintenance at the network level. Figure 1-1 shows the NMC relationship
with the other network elements.
The Operation and Maintenance Center-Radio (OMC-R) is a regional site, which controls and
monitors the daily operation of network elements within its region and the quality of service
provided by the network. Figure 1-1 shows the OMC-R relationship with the other network
elements.
The Mobile services Switching Center (MSC) is a telephone switching office for handling calls
to and from the MSs within a defined geographical area. The MSC also provides the interface
between the cellular network and the ordinary land-based Public Switched Telephone Network
(PSTN). The MSC allows the GSM cellular system to function as an extension of the PSTN. It
also allows the GSM network to interface to other PLMNs. There can be a number of MSCs
within the region controlled by an OMC. Figure 1-1 shows the MSC relationship with the other
network elements.
1-2 68P02901W01-S
Jul 2008
System Information: GSM Overview Network element overview
Location registers
Three Location Registers (LR) are collocated with the MSC. These elements are
database-oriented processing nodes that manage subscriber data and keep track of the location
of the MS as it roams around the network. For detailed information regarding the LRs, see
Introduction to the MSC on page 1-23 in this chapter.
The Base Station System (BSS) is the fixed end of the radio interface that provides control
and radio coverage functions for one or more cells and their associated MSs. BSS is the link
between the MS and the MSC. The BSS comprises one or more Base Transceiver Stations
(BTSs). Each BTS contains radio components that communicate with MSs in a given area and a
Base Site Controller (BSC). The BSC supports call processing functions and the interfaces to
the MSC. Digital radio techniques are used for the radio communications link, known as the
Air Interface, between the BSS and the MS.
The BSC controls one or more Base Transceiver Stations (BTSs) and acts as a digital
processing interface between the BTS and the MSC. Detailed information regarding the
BSC can be found in BSC description on page 2-5 of this manual.
The BTS contains the radio components that provide the interface to Mobile Stations for
one or more coverage areas or cells. Detailed information regarding the BTS can be found
in BTS description on page 2-7 of this manual.
The Full-rate Transcoder (XCDR) is the digital signal processing equipment required to
perform GSM-defined speech encoding and decoding. In terms of data transmission, the
speech transcoder interfaces the 64 kbps PCM in the land network to the 13 kbps vocoder
format used on the Air Interface.
The Remote Transcoder (RXCDR) is used when the transcoding is performed at a site away
from the BSC, which is at or near the MSC. This enables 4:1 multiplexing with GSM or
8:1 with AMR half rate. The transcoded data for four logical channels is combined onto
one 64 kbps link. Thus, reducing the number of links required for interconnection to
the BSCs. Detailed information regarding the XCDR and RXCDR can be found in Base
station system on page 2-2 of this manual.
68P02901W01-S 1-3
Jul 2008
Network element overview Chapter 1: Introduction to Motorola GSM
The PCU is an interface adaptor handler unit that permits the Motorola GSM facility the
access to the packet network. As such, the PCU needs interfaces with the BSC on the
GSM side, and the SGSN on the packet network side. The PCU manages the packet radio
interface and also enables the interface from the BSS to the SGSN. The existing OMC-R
manages the PCU. Detailed information regarding the PCU can be found in General
packet radio service on page 2-33 of this manual.
The Motorola GSM equipment architecture is shown in Figure 1-1 with other associated
network elements. The BSS components are shown shaded. Also shown is the GPRS network
architecture.
RXCDR OMC-G
(Including Shelf
Manager)
OMC-R
BSSn GSN
BTSs COMMHUB
BSS2 GSNn
BSS1 GSN1
ti-GSM-GSM equipmentarchitecture-00020-ai-sw
1-4 68P02901W01-S
Jul 2008
System Information: GSM Overview Typical GSM system
Figure 1-2 shows a typical layout of a system with two BSSs. Each BSS contains several
components to make the link between the MS and the MSC. The BSS components are described
in more detail later in this manual.
MOBILE n MOBILE n
VLR VLR
MSC MSC
XCDR XCDR
EC
IWF
OMC-S
1001 101 1001 101
EC
BSS
BSC
NMC
modems to
other networks
BSS
BTS BTS
BSC
OMC-R
PSTN
and
ISDN
MS MS
68P02901W01-S 1-5
Jul 2008
Unique features of Motorola GSM Chapter 1: Introduction to Motorola GSM
The section describes the aspects of the GSM equipment that are unique to Motorola. See
Chapter 2 BSS General Description of this manual for a general description of the Motorola BSS.
Systems advantages
Features of Motorola systems that can be used to maximize the GSM capacity include unique
reuse patterns, sector sharing, and equipment sharing. Many of these features are ideal for the
system operator who has a limited number of radio channels for initiating system operation.
Other features take maximum advantage of these unique capabilities. For example,
synchronization is provided to allow the rapid handover in Motorola systems. It also provides
enhanced frequency hopping and flexible traffic channel allocation when a limited number of
GSM channels are available. Enhanced algorithms and techniques improve handover decisions
and minimize handover traffic loading on the system.
System planning
A computer program (using artificial intelligence techniques) for system planning assists and
provides a degree of automation for frequency planning. A plan checker feature is also included.
The system includes facilities for user interaction and user friendly (graphical) presentation of
plan results and system statistics. Future interconnection with the OMC to provide a feedback
path for performance assessment and learning is also anticipated.
Fault tolerance
Motorola network equipment is designed with inherent fault tolerance. All network elements
except the BTS are designed to be fault tolerant to any single point failure. The BTS is designed
to provide redundancy economically, as required.
1-6 68P02901W01-S
Jul 2008
System Information: GSM Overview Maintenance
Maintenance
The cost of maintenance is an issue in the operation of a cellular network, especially where cell
sites are widely separated. The Motorola equipment is of high quality and incorporates highly
tolerant engineering design and manufacturing.
Extensive board-level self-diagnostics.
Circuit designs that do not require tuning and are immune to drift. (For example, direct
digital synthesis for the modulation).
Remotely and software controllable parameters, including transmitter power and cavity
frequency.
High-performance circuit and system designs that meet the GSM recommendations. (For
example, a low noise figure receiver achieving GSM intermodulation rejection and spurious
response rejection specifications).
68P02901W01-S 1-7
Jul 2008
Motorola network specifications Chapter 1: Introduction to Motorola GSM
The following sections provide specifications for the Motorola Network Elements (NEs) in the
GSM system. Specifications described in this section are:
OMC-R
Receiver
Transmitter
OMC-R specifications
The Motorola Operation and Maintenance Center - Radio (OMC-R) is a UNIX-based system.
Specifications and performance data are provided in the following sections.
The functions of the OMC-R are specified in the GSM Recommendations series. These functions
are based on ITU-TSS recommendations such as, ITU-TSS Rec. M.30. Table 1-1 shows a list of
functions together with appropriate GSM and ITU-TSS references.
Function Reference
Event and Alarm Management GSM 12.07
Fault Management GSM 12.07
Performance Management GSM 12.04 and 12.07 (based on ITU-TSS
E.411, for example)
Configuration Management GSM 12.07
Security Management GSM 12.03
OMC-R Man Machine Interface (MMI) and ITU-TSS M.251 [44], and Z.301 to Z.337
MML [97 to 114]
Safety and protection aspects of OMC ITU-TSS E.410
operation
1-8 68P02901W01-S
Jul 2008
System Information: GSM Overview System processor
System processor
The Netra 20, Netra 440, Sunfire 4800 or Sunfire 4900 system processors are UNIX systems.
The OMC system processor runs the OMC application software which handles all Operation
and Maintenance communication with NEs. It processes all incoming events, alarms, uploads
and downloads, and performance statistics, and the setup of remote login sessions to different
NEs. The system processor contains a database based on an INFORMIX Database Management
System. This database is configured for storing performance statistics, subscription lists, and
network and map configuration data, enabling operators to monitor incoming events and alarms.
Table 1-2 provides a comparison between the Low-end (10 k TCH), Mid-range (10 k and 30 k
TCH) and High-end (45 k TCH) OMC configurations.
68P02901W01-S 1-9
Jul 2008
Operator workstations Chapter 1: Introduction to Motorola GSM
Operator workstations
The rest of the OMC is made up of operator workstations, and is primarily concerned with
running the OMC operator interface, the OMC Graphical User Interface (GUI). Typically,
the OMC configuration contains a single application GUI server, and several Sunblade 150
workstations as GUI clients. Alternatively, newer workstations can be connected directly as GUI
servers. Each operator workstation is a complete UNIX system.
The operator workstations run the OMC GUI software for various operations.
Optional processors
Optional processors used for Mediation Device (OSI), Remote Login, and Offline BSS
Configuration can be included in the basic OMC configuration.
OMC configuration
The OMC, a system configuration based on SunFire 4900 System Processor hardware, is
supplied in Low-end (5 k TCH), Mid-range (10 k or 30 k TCH) and High-end (45 k TCH) versions.
The hardware requirements (hard disks, CPUs, and so on) vary depending on the version and the
processor in use, as does the disk partitioning. This section describes the hardware architecture
requirements for each processor and each version, and the common software requirements.
Data communication
OMC-R uses standard X.25 communication protocols on the interfaces with other entities in the
network.
For example, the NMC-OMC interface is defined in GSM 12.01 and corresponds to the Q3 type
of interface according to ITU-TSS M.30 [1]. The OMC-R X.25 capacities are shown in Table 1-3.
1-10 68P02901W01-S
Jul 2008
System Information: GSM Overview Receiver specifications
Receiver specifications
Functionality Specification
Frequency range GSM850 824 MHz to 849 MHz.
GSM900 890 MHz to 915 MHz.
Extended GSM900 880 MHz to 915 MHz.
DCS1800 1710 MHz to 1785 MHz.
PCS1900 1850 MHz to 1910 MHz.
Channel spacing 200 kHz.
Frequency stability 0.05 ppm.
RF sensitivity The Receiver minimum sensitivity levels for GSM850,
(reference sensitivity) GSM900/EGSM900, DCS1800, and PCS1900 are as follows:
CTU, DRCU, SCU, TCU Each receiver input has a minimum sensitivity of - 104
dBm complying with GSM 05.05, section 6.2, as
measured according to the method of GSM 11.20/11.21.
Static BER < 0.1% for input levels > -40 dBm.
Continued
68P02901W01-S 1-11
Jul 2008
Receiver specifications Chapter 1: Introduction to Motorola GSM
1-12 68P02901W01-S
Jul 2008
System Information: GSM Overview Security management
Security management
Password levels
Passwords are required to access some commands in the BSS system. There are four levels of
security in the BSS system:
Level 1 - Permits only the display of certain system elements. This level is the entrance
level after booting up.
Level 3 - Permits access as for level 2, and access to the executive monitor. Two passwords
are required at this level. Only users who have purchased the level 3 password option
have access at this level.
Level 4: The omcadmin user can create a username and assign a profile to the user. The
profile defines the BSS and EMON command sets that the user can access at the BSS. The
omcadmin user can set a NE access level for a NE user account. On login to the OMC, the
user is placed at that access level.
The chg_password command can be used to change passwords by the level 4 user.
System impact
At the OMC-R GUI, the TTY (login) and CACS interfaces support the modified chg_password
MMI command.
68P02901W01-S 1-13
Jul 2008
Mobile station Chapter 1: Introduction to Motorola GSM
Mobile station
Subscribers use a Mobile Station (MS) to access the services provided by the PLMN. MSs can
be installed in vehicles or can be portable or hand held stations. An MS can include provisions
for data communication as well as voice communication.
Different types of MSs can provide different types of data interfaces. To provide a common
model for describing these different MS configurations, GSM defines reference configurations
for MSs similar to the configurations defined for ISDN land stations.
The Mobile Station (MS) together with the Subscriber Identity Module (SIM) is defined as
the radio equipment, and a subscriber needs Man Machine Interface (MMI) to access PLMN
services. Typically, it is a mobile telephone though it can also be a mobile data communications
unit.
The Mobile Station consists of the Mobile Equipment (ME) and the Subscriber Identity Module
(SIM).
Mobile equipment
The Mobile Equipment is the hardware used by the subscriber to access the network. There
are three types:
Vehicle mounted, with the antenna physically mounted on the outside of the vehicle.
Portable mobile unit, which can be hand held, but the antenna is not on the handset.
Hand portable unit, which consists of a small handset with the antenna attached to the
handset.
The SIM is a removable card that plugs into the ME. It identifies the mobile subscriber and
provides information about the service that the subscriber receives.
1-14 68P02901W01-S
Jul 2008
System Information: GSM Overview Hand portable viability
The GSM specifications for hand portable MSs aim to minimize power consumption by design
features such as:
Discontinuous Transmission (DTx)
It ensures that the hand portable transmitter is energized only when there is speech or
data traffic to transmit.
It is a group paging technique that allows the hand portable to cycle to a low drain standby
mode as much as 98% of the time.
As the hand portable gets closer to the BTS, it uses less power to transmit. Thus it saves
on battery life.
The PLMN maintains a list of the allowed IMEIs, in the Equipment Identity Register (EIR),
to validate the mobile equipment.
Subscriber identification
Just as the IMEI identifies the mobile equipment, other numbers are used to identify the mobile
subscriber. Different subscriber identities are used in different phases of call setup. The
International Mobile Subscriber Identity (IMSI) is the primary identity of the subscriber within
the mobile network and is permanently assigned to that subscriber.
68P02901W01-S 1-15
Jul 2008
Subscriber identification Chapter 1: Introduction to Motorola GSM
The GSM system can also assign a Temporary Mobile Subscriber Identity (TMSI). After the
subscriber's IMSI has been initialized on the system, the TMSI can be sent across the network
to identify the subscriber. The system automatically changes the TMSI at regular intervals,
thus protecting the subscriber from being identified by someone attempting to monitor the
radio channels. The TMSI is a local number and is always transmitted with the Location Area
Identification (LAI) to avoid ambiguities.
The Mobile Subscriber ISDN (MSISDN) number is the telephone number of the MS. It is the
number a calling party dials to reach the subscriber. The land network uses this number to
route calls toward the MSC.
The PLMN holds subscriber data in two registers: the Home Location Register (HLR) and
the Visitor Location Register (VLR).
By making a distinction between the subscriber identity and the mobile equipment identity, a
GSM PLMN can route calls and perform billing tasks based on the identity of the subscriber
rather than the mobile equipment being used. It can be done using a removable Subscriber
Information Module (SIM). A smart card is one possible implementation of a SIM module.
Local Area Identity (LAI) - LAI identifies the current location of the subscriber.
When the SIM is inserted in the mobile equipment, a location update procedure registers the
subscriber's new location, allowing the correct routing of incoming calls.
1-16 68P02901W01-S
Jul 2008
System Information: GSM Overview GSM network specifications and recommendations
GSM advantages
Increased capacity and low error rates compared with analog networks.
Digital networks
GSM networks are digital and can cater for high system capacities. They are consistent with
the worldwide digitization of the telephone network, and are an extension of the Integrated
Services Digital Network (ISDN), using a digital radio interface between the cellular network
and the mobile subscriber equipment.
Increase capacity
GSM allows 25 kHz per user, that is, eight conversations per 200 kHz channel pair (a pair
comprising one transmit channel and one receive channel). Use of digital channel coding
and the modulation makes the signal resistant to interference from cells where the same
frequencies are reused (co-channel interference); a Carrier to Interference Ratio (C/I) level of
9 dB is achieved, as opposed to the 18 dB, typical with analog cellular. This allows increased
geographic reuse by permitting a reduction in the number of cells in the reuse pattern. Since
this number is directly controlled by the amount of interference, the radio transmission design
can deliver acceptable performance.
Frequency reuse
Cellular networks were developed to circumvent the needs of increasingly powerful radio
equipment and having to use a greater number of individual frequencies. With a GSM cellular
network, the mobile equipment is not more than a few kilometers from the transceiver.
Therefore, pairs of frequencies (one for transmit, one for receive), called reuse groups, can
be reused in a geographic repeat pattern across the network. Figure 1-3 shows a four-cell
frequency reuse pattern.
68P02901W01-S 1-17
Jul 2008
Audio capacity Chapter 1: Introduction to Motorola GSM
FRE QUENCY
RE US E
GROUP 1
RE US ED
Audio capacity
Digital transmission of speech and high performance digital signal processors provide good
quality speech transmission. In regions of interference or noise-limited operation, the speech
quality is noticeably better than analog transmission. Where noise or interference obliterate
speech frames, error correction is used to put back some of the missing information. If too much
information is lost, a digital extrapolation algorithm is used to fill the gap. While the precise
implementation of the extrapolation algorithm is up to the manufacturer, GSM recommends
minimum and maximum permitted extrapolations.
Link integrity
GSM incorporates several features to achieve a high-integrity communication link and to ensure
high quality signaling performance. Call re-establishment procedures allow lost subscribers to
reconnect to an interrupted connection. These procedures reduce the number of dropped or
lost calls.
A unique feature of digital communication is the use of the error control coding to estimate the
bit error rate of the channel being used. Thus, the system evaluates link quality and can take
action on co-channel and adjacent channel interference, even when signal levels are relatively
high. If detrimental interference is sensed, a subscriber is handed over to a different cell
or channel.
1-18 68P02901W01-S
Jul 2008
System Information: GSM Overview Subscriber services
Subscriber services
Under GSM, subscriber services similar to the services provided by an ISDN land network can
be made available to portable mobile and hand portable Mobile Stations. The Mobile Station is
provided with control channels (like the D channel on ISDN) and a traffic channel for user data
or digitized voice (similar to the ISDN B channel).
Both data and voice are carried in digital form on the radio interface, allowing end-to-end digital
connections through land and GSM networks. The control channels also provide the mobile
subscriber with supplementary services similar to the services in the ISDN land network. For
example, calling number presentation, closed user groups, and in-call modifications.
Data communications
In addition to provisions for voice communication, GSM MSs can provide either an ISDN S
interface point, or an ITU-TSS X or V-series interface, to connect standard data terminal
equipment. A data inter working function allows inter working with other data networks such as
the ISDN land network. For interworking with an analog-oriented Public Switched Telephone
Network (PSTN), the function connects data from the mobile through a modem and converts the
modem audio to Pulse Code Modulation (PCM) format for connection to a PSTN digital trunk.
Other types of inter working, such as access to packet-switched and circuit-switched public data
networks can be provided. The call setup message from the MS includes information on the
MSs bearer capability to indicate which type of data call is being set up.
Teleservices
GSM provides several categories of teleservices, including basic speech, Short Message Service
(SMS) (for messages sent to a pager built into the MS), message handling service, facsimile,
videotext, and teletext. Data services are also available in both circuit and packet modes,
and with a diversity of inter working functions, to support interfaces between the PSTN and
the ISDN.
Traditional landline analog modems provides interfacing with the land network. Transparent
transmission can be used, which includes error correction. Data rates from 300 bits per second
to 12,000 bits per second are provided.
If improved error control is desired, data services using a non-transparent protocol can be
invoked. This error detection or retransmission scheme provides for much reduced net error
rates, though the throughput rate is dependent on the radio channel quality and is not affected
by the error control.
Security features
Security features of GSM protect both users and operators against eavesdropping and the
misuse of valuable resources. Specific provisions protect subscriber identity and authentication,
user data, and elements of the signaling information.
68P02901W01-S 1-19
Jul 2008
GSM network elements Chapter 1: Introduction to Motorola GSM
The GSM network incorporates a number of network elements to support mobile telephones and
other mobile equipment (known collectively as Mobile Stations, or MSs). These elements form
the major components of the GSM network.
The Network Management Center (NMC) is an element defined by the GSM recommendations
for managing an entire GSM cellular network to provide Operation and Maintenance at the
network level.
Passes information from one OMC-R region to another to the improve problem solving
strategies.
The NMC, being responsible for Operation and Maintenance at the network level and managing
traffic on the network, performs overall management of the PLMN. It is a single control point
in systems with multiple MSCs, with the ability to coordinate interconnects to networks such
as alternative PSTNs.
Both the OMC-S and OMC-R systems provide the NMC with information about the network
equipment. The NMC monitors this information for high-level alarms, such as a failed or
overloaded network node, and also monitors the status of automatic controls applied at
the network equipment in response to conditions such as overload. NMC operators monitor
the network status, and in the event of a problem, are able to give guidance to staff at the
appropriate OMC, according to the ability of other regions to handle increased traffic flow.
1-20 68P02901W01-S
Jul 2008
System Information: GSM Overview Monitoring the routes
The NMC monitors the signaling and trunk routes between nodes to prevent an overload
condition propagating through the network. Routes between the PLMN and the PSTN are also
monitored to avoid propagation of overload conditions between networks. The NMC staff can
coordinate network management controls with the NMC facilities supporting the other networks.
The NMC also manages traffic on the BSS network equipment. In extreme circumstances,
NMC operators are able to invoke controls such as priority access, as described in GSM
recommendation 2.11. The control of traffic on the signaling and traffic routes between the
MSC and BSS can be used to isolate overloading problems within a region. The NMC provides
its operators with the ability to reconfigure cell parameters as needed and to force handovers.
The NMC is able to take regional responsibility when an OMC-R is not manned, with the OMC-R
acting as a transit point between the NMC and the network equipment. In this instance, the
NMC can provide operators with functions equivalent to those available at the OMC-R. The
NMC also supports planned changes to, or expansion of, the network.
Interface
GSM defines the interface between the NMC and OMC-R to use Q3 protocol on a 64 kbps
digital link.
68P02901W01-S 1-21
Jul 2008
Operation and Maintenance center Chapter 1: Introduction to Motorola GSM
The GSM recommendations identify an element that controls and monitors the other network
elements within a region. In the Motorola GSM network, the Operation and Maintenance Center
(OMC-R) performs this function. The OMC-R also monitors the quality of service provided by
the network. The OMC-R is connected to the other network elements through an X.25 packet
network, and sends and receives only the control and network information and, not speech
or data traffic.
1-22 68P02901W01-S
Jul 2008
System Information: GSM Overview Mobile services switching center
The Mobile services Switching Center (MSC) coordinates the setting up of calls to and from
the GSM users within a defined geographical area. It is the telephone switching office for the
traffic originated or terminated at the MS traffic and provides the appropriate bearer services,
teleservices, and supplementary services. It controls a number of Base Station Sites (BSSs)
within a specified geographical coverage area and gives the radio subsystem access with the
subscriber and equipment databases.
The MSC also provides the interface between the cellular network and the ordinary land-based
Public Switched Telephone Network (PSTN), allowing the GSM cellular system to function as an
extension of the PSTN. It also allows the GSM network to interface to other PLMNs. There can
be a number of MSCs within the region controlled by an OMC.
The MSC controls the call setup and routing procedures in a way similar to a land network end
office controlling landline calls. On the land network side, the MSC performs call-signaling
functions using the ITU-TSS C7 communications protocol. The forms of the protocol used
are Telephone User Parts (TUPs) on the interface to the PSTN and ISDN User Part (ISUP) on
the interface to the ISDN.
MSC functions
The MSC acts as an exchange for all types of mobile calls. They are local, national, and
international. The following are mobile-specific call processing functions in the MSC:
Provision of access to the VLR and HLR.
Paging
Handover
Call re-establishment
68P02901W01-S 1-23
Jul 2008
Gateway MSC Chapter 1: Introduction to Motorola GSM
Inter working between the signaling systems of fixed networks and the signaling system of
the BSS.
Resource handling:
Queuing
Security functions
Gateway MSC
When the MSC provides an interface between the fixed and mobile networks, it is known as
the Gateway MSC (GMSC), since it gives the mobile network access to the landlines of the
PSTN, ISDN and data networks. It can also provide specific Inter Working Functions (IWFs) to
other networks.
The GSM recommendations define the functions of the MSC, but allow flexibility in its design.
The most common solution is to combine the functions of the MSC, VLR, HLR, AUC, and
EIR into one functional node. This has the advantage that the dynamic load, caused, for
example, by inter working through C7 signaling links, is kept to a minimum.
Another approach is to separate all functional elements into separate network nodes.
In practice, due to the transmission capacity of C7, the MSC must not be separated from the
VLR, nor the HLR from the AUC.
1-24 68P02901W01-S
Jul 2008
System Information: GSM Overview Interfaces
Interfaces
BSSs
The A interface
The interface between the MSC and the BSS is defined as the A Interface. The interface uses
one or more E1 digital links. The channels on these links can be used for traffic or signaling.
The A Interface provides facilities to the traffic channels and signaling links for the following
functions:
Terrestrial management - allocation and blocking of the terrestrial traffic channels.
Layered signaling
The signaling is layered, similar to the signaling in the OSI reference model. However, the
layers referred to are not identical but specified by ITU-TSS C7.
The A Interface carries messages between the BSC and the MSC and the BTS (MS). These
two data flows are referred to as BSSMAP and DTAP. In addition, the general BSC BSSMAP
messages must be distinguished from the DTAP messages specific to the mobile station
connection, with the DTAP messages identified between themselves. For the DTAP messages,
the virtual circuit approach is used with independent connections established and released.
68P02901W01-S 1-25
Jul 2008
Location register interfaces Chapter 1: Introduction to Motorola GSM
Protocols
Figure 1-4 shows how the signaling messages are transferred between the BSC (or different
mobile stations) and the MSC by using the C7 MTP-SCCP stack and protocols.
DISTRIBUTION LAYER
SCCP
MTP
PHYSICAL LAYER
The SCCP defines several classes of services, of which only two are used in the GSM A Interface.
They are the connectionless mode and a connection orientated mode. These modes are referred
to as class 0 and class 2 SCCP services.
The lower level communication functions for the interfaces between the MSC, VLR, HLR, and
EIR follow the ITU-TSS recommendations for C7. At the application level, GSM specifies the
messages used on these interfaces as the Mobile Application Part, or MAP.
The Message Transfer Link (MTL) is the Motorola name given to the signaling link between the
MSC and BSC. It takes up one timeslot on the E1 link.
Call control
The MSC performs call control functions such as number translations and routing, matrix
path control, and allocation of outgoing trunks. It maintains PLMN synchronization and
provides synchronization to its BSSs. The MSC also collects traffic statistics for performance
management.
Emergency calls
An international emergency number allows GSM subscribers to make emergency calls wherever
they are located. The MSC receives emergency call setup messages, and routes the calls to
the appropriate emergency center.
1-26 68P02901W01-S
Jul 2008
System Information: GSM Overview Short message service
The Service Center (SC) sends point-to-point short messages destined for the MS to the GMSC.
The GMSC checks for errors, interrogates the HLR to determine the location of the MS
and transfers the message to the appropriate MSC (The GMSC and the MSC is the same
equipment). The MSC uses call setup parameters from the VLR to establish the call and
reports the outcome back to the GMSC, which in turn reports to the MSC.
If the message is unsuccessful, the GMSC requests the HLR to store the SC address as a
Message Waiting Data for the MSISDN. The HLR determines when the MS is next ready to
receive a message, and informs the MSC that has the inter working interface with the SC
(The inter working MSC and the MSC is the same equipment). The inter working MSC in
turn informs the SC so that a further attempt to send the message can be made.
MSCs also handle short messages sent from the MS. The MSC local to the MS checks
the message for errors and transfers it to the appropriate inter working MSC. The inter
working MSC transfers the message to the destination SC, receives the outcome and
reports it back to the MSC, which reports to the MS.
MSCs only handle point-to-point short messages. The OMC-R and the BSS handle short
messages broadcast to all MSs in a cell.
Security procedures
Other functions performed by the MSC are unique to the mobile environment. The MSC supports
the security procedures used to control access to the radio channels. These procedures include:
Passing the keys used to validate the identity of the mobile equipment and the subscriber
to the BSS.
Encrypting the data sent on the traffic channel and control channels.
In addition to the call setup procedures, the MSC also controls location registration and some
handover procedures. Location registration and location update allow MSs to report changes in
their locations, enabling automatic completion of MS terminated calls. The handover procedure
preserves call connections as MSs moves from one radio coverage area to another during an
established call. A single and the same BSC controls handovers within cells. When handovers
are between cells controlled by different BSCs, the primary control is at the MSC. Figure 1-5
shows how the two types of handover are achieved.
68P02901W01-S 1-27
Jul 2008
Inter-MSC handovers Chapter 1: Introduction to Motorola GSM
BSC
MS
EACH CELL CONTROLLED BY A
DIFFERENT BSC, SO MSC
CONTROLS HANDOVER
HANDOVER
BTS BTS
MSC
BSC BSC
BSC CONTROLS BOTH
CELLS, SO IT CONT ROLS
HANDOVER MS
HANDOVER
BTS BTS
ti-GSM-HO control-00024-ai-sw
Inter-MSC handovers
Handovers between MSCs can also be performed between BSSs connected to two different
MSCs. In these handovers, the MSC where the call originates functions as the primary MSC,
and retains ultimate control of the call through out its duration, even though the call processing
tasks are handed over to another MSC.
The Equipment Identity Register (EIR) option, is a centralized database for validating the
International Mobile station Equipment Identity (IMEI).
The gray list contains IMEIs of equipment to be monitored and observed for location
and correct functioning.
The black list contains IMEIs of MSs which have been reported stolen or are to be denied
service.
1-28 68P02901W01-S
Jul 2008
System Information: GSM Overview Home location register
The MSCs in the network can remotely access the EIR database. The MSC in a different PLMN
can also access the EIR. A given PLMN can contain more than one EIR, in which case each EIR
controls certain blocks of IMEI numbers. The MSC contains a translation facility, which, when
given an IMEI, returns the address of the proper EIR to access. Figure 1-6 summarizes the
three database lists.
Figure 1-7 shows the Home Location Register (HLR), which is a database of subscriber
information used in setting up calls. Various identification numbers and addresses are stored as
well as authentication parameters, services subscribed for and special routing information are
stored in the HLR. The current status of the subscriber is maintained.
MSC
MSISDN HLR
HOME LOCATION
REGISTER
MSISDN
or IMSI BASIC SER VICE LIST MSISDN
EXTERNAL VLR
PLMN SUPPL SER VICE LIST
CURRENT VLR
CALL FOR WARD
NUMBER and so on
IMSI
IMSI
VLR MSC
ti-GSM-HLR config-00026-ai-sw
68P02901W01-S 1-29
Jul 2008
HLR master database Chapter 1: Introduction to Motorola GSM
The HLR contains the master database of the subscribers to a PLMN. The MSCs and VLRs in the
network can remotely access this data. A PLMN can include more than one HLR, in which case
each HLR contains a portion of the total subscriber database. Either the IMSI or the mobile
subscriber ISDN number can access the subscriber data. The MSC or a VLR in a different PLMN
can also access the data, to allow inter-system and inter-country roaming.
HLR data
The data stored in the HLR indicates the basic and supplementary services a given subscriber
is allowed to use. This data is changed only when new subscribers are added or deleted, or
the specific services they subscribe to are changed. The HLR data also includes temporary
information related to supplementary services such as the current call forwarding number.
A subscriber's HLR entry also includes the address of the current VLR. This information, in
connection with the VLR data, allows completion of calls to the mobile subscriber.
Authentication center
The HLR function can also include the Authentication Center (AUC) as shown in Figure 1-8. The
AUC generates and stores the parameters necessary to authenticate a subscriber's identity to
guard against fraudulent system use.
AUTHENTICATION CENTRE
AUTHENTICATION
KEY
ONE PER
REQUEST FOR SUBSCRIBER SIGNED
AUTHENTICATION RESPONSE
ALGORITHM
PROCESS To VLR
RANDOM
NUMBER RANDOM
GENERATOR NUMBER
To MS
ti-GSM-AUC config-00027-ai-sw
1-30 68P02901W01-S
Jul 2008
System Information: GSM Overview Authentication key
Authentication key
To support the authentication process, each subscriber is assigned an authentication key (Ki),
which is stored only in the SIM of the MS and at the authentication center. The AUC generates a
random number that is an input to the authentication algorithm along with the authentication
key. The algorithm produces a new number called the signed response. To authenticate a
subscriber, the random number is sent to the MS.
If the mobile is a valid one, it executes the same authentication algorithm as the AUC and using
its known Ki produces the same signed response that is sent back on the signaling channel.
Producing the same signed response from the same random number proves the authenticity
of the subscriber. This method provides increased security because anyone monitoring the
radio channel cannot acquire any fixed keys.
Figure 1-9 shows the Visitor Location Register (VLR), which is a local subscriber database,
holding the details of those subscribers who enter the area of the network that it covers. The
details are held in the VLR until the subscriber moves into the area serviced by another VLR.
The data includes most of the information stored at the HLR, as well as more precise location
and status information. The VLR provides the system elements local to the subscriber, with
basic information on that subscriber, thus removing the need to access the HLR every time any
subscriber information is required.
VLR
VISITOR LOCATION
REGISTER
MSRN
(MOBILE STATION
VLR Database ROAMING MSRN
NUMBER)
GENERATOR
COPY OF SELECTED
IMSI DATA FROM HLR HANDOVER
INTERROGATION TMSI DATABASE FOR ALL HANDOVER NUMBER
ACCESS MODES SUBSCRIBERS NUMBER
MSRN CURRENTLY IN AREA GENERATOR
SER VICED BY THIS
VLR
TMSI
(TEMPORAR Y MOBILE NEW TMSI
SUBSCRIBER IDENTITY)
GENERATOR
68P02901W01-S 1-31
Jul 2008
Controlling LAIs Chapter 1: Introduction to Motorola GSM
Controlling LAIs
Cells in the PLMN are grouped into geographic areas and each is assigned a Location Area
Identification (LAI). Each VLR controls a certain set of LAIs. When a mobile subscriber roams
from one LAI to another, the current location is updated in the VLR entry using the location
validate procedure.
If the old and new LAIs are under control of two different VLRs, the entry on the old VLR is
deleted and a new entry is created at the new VLR by copying the basic data from the HLR entry.
The subscriber's current VLR address, stored at the HLR, is also updated thus providing the
information necessary to complete calls to the mobile subscriber.
Controlling MSRNs
The VLR also controls the assignment of Mobile Station Roaming Numbers (MSRNs). When the
MS receives an incoming call, the HLR requests the correct VLR for an MSRN. The VLR selects
the MSRN from its pool of numbers and returns it to the MSC that initially handled the call. The
call is then forwarded using the MSRN as the called address. The MSRN causes the call to be
routed to the MSC which controls the base stations in the area where the MS is currently located.
The VLR also allocates handover numbers for use in inter-MSC handovers. These handovers
require the call to be rerouted from the source MSC to the target MSC. The handover number
functions similarly to the MSRN, as it allows the required trunk connection to be set up by
routing the call through the land network.
The VLR also controls allocation of new Temporary Mobile Subscriber Identity (TMSI) numbers.
A subscriber's TMSI can be periodically changed to secure the subscriber's identity. The system
configuration database controls when the TMSIs are changed. Options include changing the
TMSI during each location update procedure or changing it within each call setup procedure.
IMSI, TMSI, or MSRN can access the database in the VLR. Typically, there is one VLR per
MSC, but other configurations are possible.
Call handling
The following figures illustrate the functions of the MSC in handling mobile originated or
terminated traffic.
1-32 68P02901W01-S
Jul 2008
System Information: GSM Overview MS to PSTN subscriber
MS to PSTN subscriber
Figure 1-10 shows a call from the MS to a subscriber in the land network (that is, the PSTN).
The MSC acts as an outgoing exchange. If the call is directed to another country, the MSC
routes it to the International Switching Center. If the call is to a subscriber on the national
network, the call is routed to the PSTN, which sets up the connection to the PSTN subscriber.
The MSC performs the same function for a call directed to the ISDN.
68P02901W01-S 1-33
Jul 2008
PSTN subscriber to MS Chapter 1: Introduction to Motorola GSM
PSTN subscriber to MS
Figure 1-11 shows a call from a subscriber in the land network (that is, the PSTN) to the MS.
The assumption is that the PSTN cannot interrogate the HLR, and so the call has to be directed
to the Gateway MSC, which performs the interrogation. The MSRN is then used to route the call
to MSC-B which pages MS-B and sets up the call to it. The connection between the Gateway
MSC and MSC-B is routed through one or more transit exchanges of the national ISDN or PSTN.
PSTN or ISDN
PLMN
MSC-B GMSC
BSS
VLR HLR
MS-B
ti-GSM-PSTN MS call-00030-ai-sw
MS to MS calls
1-34 68P02901W01-S
Jul 2008
System Information: GSM Overview MS to MS calls
MS to MS (same PLMN)
Figure 1-12 shows a call between a calling MS (MS-A) and a called MS (MS-B) in the same
PLMN. The MSC-A analyses the called number for MS-B, through the VLR. It interrogates the
HLR to retrieve the MSRN which it uses to route the call to MSC-B. The MSC-B acts as an
incoming exchange and establishes the call to MS-B. The connection between the two MSCs is
routed through one or more transit exchanges of the national ISDN or PSTN.
PLMN
HLR VLR
MSRN of MS-B
RETRIEVED
MSC-A
BSS
MS-A
VLR
PSTN/ISDN
MSC-B
BSS
MS-B
68P02901W01-S 1-35
Jul 2008
MS to MS calls Chapter 1: Introduction to Motorola GSM
Figure 1-13 shows a call between a calling MS (MS-A) in one PLMN and a called MS (MS-B) in
another PLMN. MSC-A analyses the called number for MS-B. It interrogates the HLR of the
other PLMN to retrieve the MSRN which it uses to route the call to MSC-B. MSC-B acts as an
incoming exchange and establishes the call to MS-B.
PLMN
VLR
MSC-A
BSS
MS-A
PSTN or
ISDN
PLMN
HLR VLR
MSC-B
BSS
MS-B
1-36 68P02901W01-S
Jul 2008
System Information: GSM Overview MS to MS calls
Figure 1-14 shows a call from the MS (MS-A) in one PLMN to the MS (MS-B) in a PLMN in
another country. The MSC-A determines from the international prefix that the call is directed
to another country but cannot determine the location of the called MS. The call is therefore
routed to the Gateway MSC in the other country, which interrogates the HLR to discover the
MSC area where MS-B is currently located. The HLR returns the MSRN and the call is routed to
MSC-B. MSC-B acts as an incoming exchange and establishes the call to MS-B. The connection
between the GMSC and whichever MSC area an MS-B roams to, is routed through one or
more exchanges of the national ISDN or PSTN.
68P02901W01-S 1-37
Jul 2008
Base station system Chapter 1: Introduction to Motorola GSM
The Base Station System (BSS) is the fixed end of the radio interface that provides control and
radio coverage functions for one or more cells and their associated MSs. It is the interface
between the MS and the MSC. The BSS comprises one or more Base Transceiver Stations (BTSs),
each containing the radio components that communicate with MSs in a given area, and a Base
Site Controller (BSC), which supports call processing functions and the interfaces to the MSC.
Digital radio techniques are used for the radio communications link, known as the Air Interface,
between the BSS and the MS.
The BSS and the Air Interface are described in detail in Base station system on page 2-2.
BSS configurations
Physically, a BTS is remote from its BSC. Where the BTSs are remote from the BSC, they are
linked in a variety of ways. Three possible configurations are shown in Figure 1-15.
BSS 1 is a simple configuration, with a direct link from the BSC to a single BTS.
BSS 2 shows a spoke configuration, where each of the BTSs has its own link to the BSC.
BSS 3 shows a closed loop configuration, with each BTS linked to the next, and a link
from the last BTS back to the BSC.
1-38 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS configurations
BSS #2 BSS #3
MS
BTS
SITE
MS MS
BTS
SITE
BTS BTS
MS SITE
SITE
BSC
SITE
WITH BTS
XCDR SITE
MS
BTS
SITE
BSC
SITE
BTS
SITE
RXCDR
(NOTE 2)
A MSC
LEGEND
Air Interface
NOTE:
(1) DASHED LINES ENCLOSE NETWORK COMPONENTS
OF A PARTICULAR BSS AND DO NOT SHOW THE BSS
SER VICE AREA.
(2) REMOTE TRANSCODING (RXCDR) IS LOCA TED AT
MSC SITE, BUT IS P ART OF BSS #2.
ti-GSM-BSS configs-00034-ai-sw
The configuration used at any particular site depends on a number of factors, and a mixture of
configurations can be used within a single BSS. The BTS configurations are described in greater
detail in the manual Service Manual: 68P02901W37.
68P02901W01-S 1-39
Jul 2008
Software functions Chapter 1: Introduction to Motorola GSM
Software functions
Motorola BSS
In Motorola systems, the BSS equipment can be used both as a concentrator hub and as a single
site. The Motorola add and delete option allows BTSs to be strung one to another in an open or
closed loop topology. This enhancement provides reduced line charges in low density coverage
regions, such as sparse rural areas or along highways.
The BSC controls the selection of signaling channels, and speech channels, and manages the
radio channels. It transfers signaling information to and from MSs through the BTS.
Connection of MSC
The relationship between the radio channels at the BSS and the terrestrial circuits, which
connect the BSS to the MSC is not fixed. A radio channel and terrestrial circuit must be
selected and assigned every time a call is set up. The BSC selects the radio channel, while the
MSC selects the terrestrial circuit. The BSC then uses a digital switching matrix to connect
the two together. The switching matrix also allows the BSS to perform inter-BSS handovers
without involving the MSC.
1-40 68P02901W01-S
Jul 2008
System Information: GSM Overview Speech transcoding
Speech transcoding
Speech transmitted on the GSM radio channel must be transcoded to reduce the bandwidth
requirement on the Air Interface. The speech transcoder (XCDR) performs this function.
Transcoding is performed at the BSC, or remotely at or near the MSC. When transcoding is
performed remotely, it can be combined with 4:1 multiplexing (with GSM or AMR half rate 8:1 is
possible in the optimum case) in which the data for four logical channels is combined onto one
64 kbps link, thus reducing the number of links required for interconnection of the BSCs.
At the application levels of the C7 communications protocol, GSM defines a special set of
messages, unique to the mobile application, called the BSS Application Part (BSSAP).
The Direct Transfer Application Part (DTAP), which is used over the radio interface to
the MS.
BSS interfaces
The A interface
The interface between the MSC and the BSS is a standardized C7 interface and is fully defined
in the GSM recommendations. It enables the system operator to purchase switching equipment
(such as an MSC) from one supplier, and radio equipment (such as a BSS) from another supplier,
and still retain equipment compatibility.
The interface between the BSC and a remote BTS is also a standard interface. However,
Motorola offers a unique Motorola Abis Interface, called Mobis, which reduces the amount of
message traffic and thus the number of E1 links required between a BSC and a BTS.
The radio communications link between the BSS and the MS is known as the Air Interface.
The GSM Air Interface is a noise-robust transmission medium. The speed of a radio channel used
in GSM is 270.833 kbps. The modulation is 0.3 BT Gaussian Minimum Shift Keying (GMSK).
68P02901W01-S 1-41
Jul 2008
Physical channels Chapter 1: Introduction to Motorola GSM
Physical channels
The Air Interface is capable of handling simultaneous calls; any call sent on an RF carrier
can share that carrier with up to seven other calls. GSM systems achieve this by virtue of
the high speed of digital radio communication, which allows each call to take its turn on the
carrier with no loss of transmission quality.
Logical channels
The different types of information sent over GSM physical channels are called logical channels.
The term channel is therefore used differently when applied to logical channels. The physical
channel is a pathway for the information; the logical channel is the type of information sent.
There are two types of logical channel on the Air Interface: control (or signaling) channels
and traffic channels.
Control channels
The control channels are used to carry signaling information between the MS and BSS. The four
control channel groups are:
Frequency Correction CHannel (FCCH) - Used by the MS to correct the frequency of its
internal time base.
Random Access CHannel (RACH) - Transmitted by the MS to gain access to the system.
Access Grant CHannel (AGCH) - Transmitted by the BTS to grant or refuse a specific
MS access to the system.
Cell Broadcast CHannel (CBCH) - Used to broadcast messages to all MSs in a specific cell.
1-42 68P02901W01-S
Jul 2008
System Information: GSM Overview Traffic channels
Standalone Dedicated Control CHannel (SDCCH) - Used during call setup or to transmit short
messages.
Slow Associated Control CHannel (SACCH) - Used by the BSS to transmit power and timing
information to the MS and to receive measurement reports from the MS.
Traffic channels
These channels are used to carry speech or data information between the MS and BSS, and
include:
Speech channels - These channels carry speech information over the Air Interface. There
are two types of speech channels:
Full rate
Half rate
Data channels - These channels carry data information over the Air Interface. There are
three types of data channels, each named according to the data rate it supports:
9.6 kbps
4.8 kbps
2.4 kbps
68P02901W01-S 1-43
Jul 2008
GSM subsystems (non-network elements) Chapter 1: Introduction to Motorola GSM
The GSM network also includes the following additional subsystems, which are not formally
recognized as network elements.
The Inter Working Function (IWF) performs the data rate adaptation between the PLMN and
networks such as the PSTN, the Integrated Services Digital Network (ISDN), and packet
networks. Other functions of the IWF include provisions for mobile subscribers to communicate
with a PSTN-based modem, or to connect directly to customer provided equipment, such as X.25
Packet Assembly/Disassembly facilities (PADs).
Echo canceler
The Echo Canceler (EC) eliminates echo from voice circuits. The voice signal from the PLMN
must be transformed from the 4-wire PLMN circuit to the 2-wire circuit on the land network. If
it is not canceled, the total round-trip delay introduced by the GSM system (typically 180 ms)
would become audible to the PLMN subscriber as an echo.
Billing center
The billing center is a system provided by the PLMN administration which collects the billing
data from the GSM network elements and applies the billing data to the accounts of the
subscribers. The GSM does not address the details of operation of the billing center, and the
billing center is not considered as a network element of the PLMN.
The MSC produces call records, and provides facilities for storing the completed call
records, as well as forwarding them to the billing center. The records are stored in a disk
file as they are being generated. In this case, the file has a fixed maximum size and when
the file becomes full, it is automatically closed and a new one is opened. The completed file
is then automatically transferred to the billing center using X.25 communication links and
the File Transfer Access and Management (FTAM) file transfer protocol. A backup of the
completed billing files can be manually copied to a magnetic tape. The same storage and
communication facilities can also be provided at HLRs and VLRs for handling event records.
Event records
The HLRs and VLRs produce event records. An event record contains the location updates
for the MS and the forwarding of MS terminated calls.
1-44 68P02901W01-S
Jul 2008
System Information: GSM Overview Cell broadcast center
The Cell Broadcast Center (CBC) is the call processing center for Cell Broadcast Short Message
Service (CBSMS) messages, which are unacknowledged short messages (maximum of 128
bytes) that are broadcast to all MSs in a particular cell.
68P02901W01-S 1-45
Jul 2008
GSM system features Chapter 1: Introduction to Motorola GSM
The following section describes GSM features and its technological requirements, and
summarizes the GSM specifications.
Technological requirements
Selection of proper filters to minimize spurious emissions without corrupting the desired
signal.
Stable quasi-linear RF PA to provide the rapid ramping for achieving GSM specified time
and spectral masks.
Adequate power supply decoupling and regulation to reduce transmitter pulsing transients.
Proper distribution of gain and AGC receiver stages to achieve the necessary 100 dB
of dynamic range.
Self calibrating techniques for generating and demodulating Gaussian Minimum Shift
Keying (GMSK) that do not require tuning and are immune to drift or ageing.
Adequate diagnostic capability, fault analysis tools, test equipment, and key servicing
test points.
Synthesizer technology that meets the high switching speeds required for frequency
hopping.
Features supplying:
Subscriber services
System-related features
Increased capacity
1-46 68P02901W01-S
Jul 2008
System Information: GSM Overview Standardized electrical interfaces
GSM defines standardized electrical interfaces and communications protocols for both the
fixed and subscriber equipment. This guarantees compatibility and inter working between
systems designed by different manufacturers and also allows the user to choose equipment at
the subsystem level, as well as the overall system level.
GSM interfaces
BTS - MS
LR - LR
ISDN compatibility
GSM is compatible with the Integrated Services Digital Network (ISDN) which carries both
voice and data on standard telephone lines. Many countries are committed to implement this
telecommunication network.
Signaling System 7
As an extension of the landline telephone network, GSM clearly relies heavily on Signaling
System 7 (SS7/C7) to provide the bearer level communications protocol.
The use of a hierarchical network architecture is another feature that can be exploited by
system designers and individual equipment providers to reduce the operating cost, particularly
inline charges. A hierarchical network architecture employs intermediate BSC controllers
between the MSC and the radio channel equipment.
68P02901W01-S 1-47
Jul 2008
Subscriber services Chapter 1: Introduction to Motorola GSM
Subscriber services
GSM systems can offer an enhanced range of services, such as teleservices, data and speech
services. These services can be augmented with a variety of supplementary subscriber services.
Charging services
Emergency services
Call forwarding
Call queuing
Conference calls
Security
GSM security features include the authentication of the mobile equipment and the subscriber.
Control information is encrypted, and speech is digitally encoded. These features provide
confidentiality and prevent stolen equipment from being used.
Handovers
GSM handovers are more tightly controlled than analog handovers. MSs have built-in
intelligence to assist in the handovers, which ensures that the network is relieved of unnecessary
measurement reporting and associated overheads.
During the handover procedures, extensive measurements are made both by the MS and the
BSS of such parameters as uplink (MS-to-BSS) and downlink (BSS-to-MS) signal levels, downlink
signal levels of adjacent cells, BSS-to-MS distance, and so on.
Many of these measurements are crosschecked to ensure trustworthiness. For example, not
only is the received level of adjacent cells measured, but also the associated control channel ID
is also received, decoded, and reported together with the quality of reception (bit error rate).
Both the BTS and the MS measure signal quality and signal strength. The MS also monitors
signal strengths in up to 32 adjacent cells.
1-48 68P02901W01-S
Jul 2008
System Information: GSM Overview Link integrity
Link integrity
GSM incorporates several features to achieve a high-integrity communication link and to ensure
high quality signaling performance. Call re-establishment procedures allow lost subscribers to
reconnect to an interrupted connection. These procedures reduce the number of dropped or
lost calls.
A unique feature of digital communication is the use of the error control coding to estimate the
bit error rate of the channel being used. Thus, the system evaluates link quality and can take
action on co-channel and adjacent channel interference, even when signal levels are relatively
high. If detrimental interference is sensed, a subscriber is handed over to a different cell
or channel.
Tracking
GSM systems keep track of the MS by updating it location. When the MS moves to a new
location area, the VLR is updated. The system also knows whether an MS is switched off, and
so, does not waste resources trying to page the MS unsuccessfully.
Power saving
GSM uses methods that save on power usage and extend battery life in the MS:
MS and base station power control
Increased capacity
GSM systems have more capacity than analog systems. Eight simultaneous calls can be active
on one RF carrier (as opposed to one call per carrier in analog). Less RF hardware is therefore
required to expand a GSM system. GSM uses a radio channel structure (TDMA) that leads to an
increased capacity of 16 simultaneous calls per carrier if half rate is used.
For data communications, the GSM offers a better match, than analog, of provided radio
spectrum to data rate. GSM provides specialized data and message services, such as a
point-to-point Short Message Service (for messages sent to a pager built into the MS). The call
lengths of these data services average much less than the corresponding speech calls.
68P02901W01-S 1-49
Jul 2008
Lower cost of infrastructure Chapter 1: Introduction to Motorola GSM
GSM design is intended to minimize the cost of the service provided. For example, the
signaling rate, and Time Division Multiplexing Access (TDMA) structure of 8 was selected as
a compromise between equipment complexity, system issues and performance. The use of a
single radio carrier for multiple traffic channels reduces the cost per channel. Half rate speech
coding provides further cost reduction.
The GSM digital cellular system uses a 9-site or a 3-site (3-sectored) pattern and 120 degree
sector arrangement, which provides a 12 dB Carrier to Interference Ratio (C/I) for 90% location
reliability.
In addition, a unique Motorola design proposes a 2-site (6-sectored) repeat pattern using 60
degree sectors. The capacity of this pattern is 40% greater than the 3-site repeat generic
pattern and provides nearly equivalent C/I performance.
A trunking efficiency factor influences this capacity improvement further because the reduced
cell reuse patterns allow a smaller number of frequency groups. The improved C/I, in conjunction
with the more accurate and sophisticated handover technique, allows microcells to be used.
Timing adjustment
The farther the MS is from the base station, the longer it takes for the bursts of transmission
to travel the distance between them. The short duration of the TDMA burst demands a high
degree of accuracy, and so, the problem of a varying time lag must be overcome by timing
corrections performed by the MS. The base station measures the distance between the MS and
the base station, and uses it to calculate a timing advance, which the MS is instructed to use
for all uplink transmissions. This timing advance information is sent to the MS twice a second
using the SACCH. The advance is superimposed on the 3-timeslot offset of the frame structure,
which the MS uses when transmitting.
Echo cancelers
Another problem is that of echo, which is made noticeable by hybrid transformers converting
the signal from 4-wire circuits in the PLMN to the traditional 2-wire circuits in the land
telephone network. High-performance echo cancelers are therefore provided for every speech
conversation in the interface between the MSC and the PSTN.
Synchronization
Synchronization is a key feature of the GSM. All frequencies and times are locked to a high
stability (0.05 ppm) reference, which can be referenced to a system-wide standard. MSs lock to
a reference transmitted from the base station.
Synchronizing clocks over a wide geographic area gives GSM system advantages such as rapid
and reduced interruption and handovers as specified in the GSM recommendations.
1-50 68P02901W01-S
Jul 2008
System Information: GSM Overview Noise robustness
Synchronization also allows the effective number of channels available for frequency hopping
to be increased and the capacity of a limited number of radio channels to be distributed
more evenly. Both these enhancements are useful where a limited spectrum is available for
implementing the GSM system.
Noise robustness
Frequency hopping, makes GSM systems more resistant to the effects of multipath fading,
apart from providing security.
The use of two antennas at the BTS, placed several wavelengths apart, creates diversity of
radio paths from the MS, leading to improved reception.
The Location Services (LCS) feature implements emergency services functionality in GSM
systems (compliant with the Federal Communications Commission (FCC) 911 requirements)
in two phases:
Phase 1
To transmit the originating number of an emergency call (911 in the United States) and the
location of the serving site to the Public Safety Answering Point (PSAP).
Phase 2
To transmit the emergency caller's estimated position, expressed in latitude and longitude
coordinates within specified limits of accuracy.
Applications that request location estimates from location services can be located in the MS, the
network, or externally to the PLMN.
Locations services currently specify three positioning mechanisms to determine the location
of a Mobile Station. These positioning processes involve two main steps: signal measurement
and position computation based on the measured signals. The standard SMG (Special Mobile
Group) positioning mechanisms are:
Enhanced Observed Time Difference (E-OTD) - not implemented in this release.
68P02901W01-S 1-51
Jul 2008
Timing Advance positioning (TA) Chapter 1: Introduction to Motorola GSM
Conventional GSM Timing Advance (TA) measurements can also be used in conjunction with
Cell ID determination to provide a coarser, lower quality location estimate.
Examples of applications to which LCS MS position determination can be applied are to deliver
tailored content to MSs in a physical locality (location-specific advertising), or to determine the
routing of voice traffic (location sensitive routing). Motorola supports Timing Advance (TA),
Enhanced Observed Time Difference (E-OTD) and Assisted GPS (A-GPS) positioning mechanisms.
The Timing Advance positioning mechanism is based on the existing GSM timing advance
measurements and the frequency of sending specified by the timing_advance_period
parameter. The timing advance value is known for the serving BTS and when returned to the
requesting LCS client with the cell ID, provides the approximate physical position of the MS.
1-52 68P02901W01-S
Jul 2008
System Information: GSM Overview E1 links
E1 links
Link types
GSM uses E1 operating link, to provide the physical links on the network. Communication
between the PSTN, MSC, and BSS equipment is over E1 links. X.25 and C7 information is sent
using the physical protocols on these links.
NOTE
Throughout this manual, reference is made to E1 links. Read the information in the
context of the type of link used.
E1 link
The E1 link has a signaling rate of 2.048 Mbps and provides thirty-two 64 kbps timeslots,
of which 30 are available:
Timeslot 0 is always reserved for synchronization purposes.
Although the remaining 31 are available for PCM or data channels, one is normally
reserved for control.
NOTE
The E1 link is sometimes referred to as a 2 Mbps link or bearer.
When using the High bit-rate Digital Subscriber Line (HDSL) feature, a modem converts E1
lines for less expensive transmission lines. The modem is daisy chain connected at the BSC or at
a point where the HDSL link is required to change to an E1 connection.
68P02901W01-S 1-53
Jul 2008
Standardized interfaces Chapter 1: Introduction to Motorola GSM
Standardized interfaces
Interface types
A major portion of GSM recommendations deals with standards for interfaces between network
elements. Communication between the PSTN, MSC, and BSS equipment is over the E1 physical
links.
A Interface: BSC-to-MSC
B Interface: MSC-to-VLR
C Interface: MSC-to-HLR/AUC
E Interface: MSC-to-MSC
F Interface: MSC-to-EIR
G Interface: VLR-to-VLR
H Interface: HLR-to-AUC
The use of these standardized interfaces throughout the mobile network allows compatibility
between network elements from different manufacturers.
For example, ITU-TSS Signaling System 7 (SS7/C7) is extensively used as the communications
protocol from the BSS through the MSC to the PSTN.
NOTE
ITU-TSS was previously known as CCITT. Signaling System 7 (C7) is sometimes
referred to as SS7 or C7.
1-54 68P02901W01-S
Jul 2008
System Information: GSM Overview GSM functional layering
The layering of GSM functions is partially based on the seven layer model for open systems
interconnection suggested by the ISO. Each layer performs a specific set of functions that are
isolated and enhances the functions performed by the lower layers. This philosophy facilitates a
modular approach to implementation. The functions occurring at one layer have only limited
interaction with the functions at another. This fact provides a degree of flexibility for future
improvements without redesigning the entire system.
Layer 1 - Physical
Layer 1 comprises the physical channel layer and is concerned with transmitting and receiving
coded information symbols over the radio link. Layer 1 features include the TDMA frame
structure and frequency hopping.
Layer 2 - Transport
Layer 3 - Management
68P02901W01-S 1-55
Jul 2008
BSSAP messaging Chapter 1: Introduction to Motorola GSM
Management Layer
BSSAP messaging
The A-interface and the Lb-interface carry C7 BSSAP messaging. The four types of BSSAP
messaging on these interfaces are:
BSSMAP (-LE) on the BSS-based SMLC-BSS link (Lb Interface, a two-way SMLC-BSS
protocol).
DTAP (-LE) on the BSS-based SMLC-LMU link (a two-way SMLC-LMU protocol). The BSS
transparently forwards DTAP-LE messages which the BSS-based SMLC and LMU use to
communicate with each other. There is, however, no direct link between BSS-based SMLC
and LMU.
DTAP on the BSS-MS link (Air Interface, a two-way MSC-MS protocol). The BSS
transparently forwards DTAP messages which the MSC and MS use to communicate with
each other. There is, however, no direct link between the MSC and MS.
1-56 68P02901W01-S
Jul 2008
System Information: GSM Overview ISDN messaging
ISDN messaging
Integrated Services Digital Network (ISDN) messaging is provided from the mobile subscribers
and extends throughout the terrestrial network, including other PLMNs.
MSC to MS
The BSS Application Part (BSSAP) of C7 specifies the MSC-MS interface. The two types of
BSSAP messaging on these interfaces are:
BSSMAP on the MSC-BSS link (A Interface).
For the interfaces between the MSC, VLR, HLR, and EIR, the lower level communication
functions also follow the ITU-TSS recommendations for C7. At the application level, the GSM
specifies the messages used on these interfaces as the Mobile Application Part, or MAP.
OMC interfaces
For the interfaces between the OMC and the other network elements, X.25 and OSI upper layer
protocols are used as specified by ISO open standards.
NMC interface
GSM defines the interface between the NMC and OMC to use a Q3 protocol on a 64 kbps
digital link.
68P02901W01-S 1-57
Jul 2008
Interface summary Chapter 1: Introduction to Motorola GSM
Interface summary
Signaling links
The signaling links between the various network elements are listed in Table 1-7.
Element Link
Remote BTS-to-BSC Radio Signaling Link (RSL)
BSC-to-BSS based SMLC Location Services Message Transfer Link (MTL)
OMC(R)-to-BSS Operation and Maintenance Link (OML)
Remote XCDR-to-BSC XCDR signaling Link (XBL)
CBC-to-BSC Cell Broadcast Link (CBL)
1-58 68P02901W01-S
Jul 2008
System Information: GSM Overview The A interface
The A interface
The interface between the MSC and the BSS is a standard interface, called the A Interface. The
A Interface is fully defined in the GSM recommendations.
The signaling portion of the interface between the MSC and the BSC uses the C7 protocol, for
which application parts are defined. For example, the Base Station System Application Part
(BSSAP).
The A Interface allows customers to purchase the switching equipment (for example, the MSC)
from one supplier, and the radio equipment (such as the BSS) from another supplier, and still
have equipment compatibility.
For support of location services, there are modifications to the A-interface: changes to various
protocols to support SMLC-BSS signaling through the MSC when the SMLC is NSS-based.
The new messages for the Motorola implementation of location services for the BSSMAP
protocol are:
BSSMAP Connection Oriented Information
A new protocol, BSSLAP, has also been added. This protocol is used for SMLC-BSS
communication as well as a carrier for SMLC-MS messages. The BSSLAP messages, which are
supported are:
BSSLAP TA Request
BSSLAP TA Response
BSSLAP Abort
BSSLAP Reset
BSSLAP Reject
Abis interface
The GSM defined interface between the BSC and the remotely located BTS equipment is called
the Abis interface. It uses Link Access Procedure D (LAPD).
At the application levels, GSM defines a special set of messages unique to the mobile application.
68P02901W01-S 1-59
Jul 2008
Air interface Chapter 1: Introduction to Motorola GSM
Mobis
The Motorola defined BSC-to-BTS interface is a modification of the Abis standard called Mobis.
It distributes functionality between the BSC and the remote BTS equipment, and offers several
advantages:
Reduced signaling link traffic which permits efficient use of E1 links. The BTS performs
handover data processing. This reduces the amount of data sent to the BSC over the
signaling link and significantly reduces the amount of processing required in the BSC.
Better synchronization of the BSC and BTS ensuring better handover from one traffic
channel to another.
For support of location services, the Mobis interface is modified to support new BSC-BTS
signaling for location services. The following messages are new for this interface:
Ta request
Ta response
Application information
Air interface
The GSM recommendations include detailed specifications for the radio channel (Air Interface)
between the MS and the BTS. The Air Interface uses a three layer protocol.
Layer 1 is the physical channel layer. This layer transmits and receives coded information
symbols over the radio link. Layer 1 provides the basic time division multiplexing (TDM)
frame structure including timeslot, frame, multiframe, and so on. Layer 1 also provides for
multiplexing and demultiplexing (channel encoding or decoding) of the different types of logical
channels that the network requires, such as traffic channels, signaling or control channels and
synchronization channels.
Layer 2 is a transport mechanism between layer 3 and layer 1. Layer 2 provides for error
free transport of layer 3 signaling.
1-60 68P02901W01-S
Jul 2008
System Information: GSM Overview Lb interface
Call management (call setup, supplementary services, dual tone multifrequency (DTMF),
and short message service).
A new message has been added to the RR protocol for transport of SMLC-MS messages. The
new message is RR Application Information.
RR Application Information.
In addition, LMUs are a new device for Location Services that use the Air Interface. However,
these LMUs act similarly to regular mobiles as far as the Air Interface is concerned, but they are
restricted in the messages they can send or accept.
Lb interface
The Lb-interface is for the support of location services. It is located between the BSS and a
BSS-based SMLC. The interface uses a C7 protocol, and is modeled (from the BSS viewpoint)
from the A-Interface. The interface is not present when the SMLC is NSS-based.
At the physical level, the interface supports one or multiple 64 kbps signaling timeslots on E1
signaling link. By convention, these timeslots are typically placed only on timeslot 16 of a given
E1 signaling link. The Lb-interface, like the A-interface, may consist of one or multiple E1s
between the BSS and the BSS-based SMLC. Unlike the A-Interface, no traffic carriers (CICs) are
present on the E1 links (this could change in the future if LMUs on a TCH must be supported).
The Lb-interface fully supports all procedures in the MTPL2, MTPL3, and SCCP protocols.
68P02901W01-S 1-61
Jul 2008
Lb interface Chapter 1: Introduction to Motorola GSM
BSSMAP Paging.
BSSMAP Confusion.
An enhancement to BSSMAP has been created for the Lb-interface called BSSMAP-LE. The
messages used for the BSSMAP-LE protocol are:
BSSMAP-LE Perform Location Request.
BSSMAP-LE Reset.
All MM messages.
DTAP enhancements
An enhancement to DTAP has been created for the Lb-interface called DTAP-LE. This is used for
SMLC-LMU communication. The messages used for DTAP-LE are:
DTAP-LE Register.
DTAP-LE Facility.
1-62 68P02901W01-S
Jul 2008
System Information: GSM Overview Lb interface
BSSLAP protocol
A new protocol, BSSLAP, has been created for direct SMLC-BSS communication, as well as a
carrier for SMLC-MS messages. The messages used for BSSLAP are:
BSSLAP TA Request.
BSSLAP TA Response.
BSSLAP Abort.
BSSLAP Reset.
BSSLAP Reject.
68P02901W01-S 1-63
Jul 2008
Network protocols Chapter 1: Introduction to Motorola GSM
Network protocols
Protocol types
The network protocols define the format of communication between two network entities.
X.25
NOTE
ITU-TSS was previously known as CCITT. Signaling System 7 (C7) is sometimes
referred to as SS7.
X.25 and C7 information is sent using the physical protocols on the E1 links.
1-64 68P02901W01-S
Jul 2008
System Information: GSM Overview OSI/protocol relationship
OSI/protocol relationship
Figure 1-17 shows the relationship between the OSI layers and the main protocols. Figure 1-18
shows the overall network protocols. The individual C7 protocols are shown, but not the
interfaces on which these protocols are used.
68P02901W01-S 1-65
Jul 2008
OSI/protocol relationship Chapter 1: Introduction to Motorola GSM
NMC CBE
PSTN
RXCDR
EIR EC
LAPD
C7
BSC
MSC
HLR VLR
BTS BTS
AUC
Base Station System
LAPDm
SIM
ti-GSM-Networkprotocols-00037-ai-sw
1-66 68P02901W01-S
Jul 2008
System Information: GSM Overview ITU-TSS signaling system 7
The ITU-TSS signaling system 7 (C7) protocol is composed of several parts: the Message
Transfer Part (MTP), the Signaling Connection Control Part (SCCP), the X.25 link, the LAPDm
protocol, and various signaling link protocols.
MTP is part of the C7 protocol that is used throughout the network. MTP provides layers 1, 2
and 3 of the seven layer model. MTP is the transport system for reliable transfer of messages
between users.
Defines the functions and procedures for controlling the transfer of signaling messages
over a signaling link.
Defines the methods for message handling and routing on a signaling link.
The SCCP forms part of the Signaling Information Field (SIF) in the MTP signaling unit.
The SCCP can operate in four modes. Two of these modes are used for GSM. Protocol class
numbers carried in the mandatory fixed field of the SCCP message indicate which mode is
being used. The two modes used for GSM are:
Connectionless. Protocol Class 0 - Single messages are sent to other SCCP users. The Unit
Data (UDT) is the only type of message sent in connectionless mode.
68P02901W01-S 1-67
Jul 2008
X.25 Chapter 1: Introduction to Motorola GSM
CC - Connection Confirm
IT - Inactivity Test
Once the communication is complete, the link must be released. The following SCCP
message types are used to release the connection:
RLSD - Released.
X.25
The X.25 link uses LAPB and LAPD protocols for layer 2 messaging. Both LAPB and LAPD
protocols are variants of HDLC:
LAPB is used on the OML.
LAPDm
The LAPDm protocol is a variation of LAPD link protocol used exclusively on the Air Interface.
1-68 68P02901W01-S
Jul 2008
System Information: GSM Overview GSM frequencies and channels
The following sections describe frequency allocations for GSM850, GSM900, EGSM900,
DCS1800, and PCS1900 digital cellular systems with their channel numbers in both decimal
and hexadecimal notation.
Table 1-8 lists and describes GSM, DCS, and PCS frequency types.
GSM850 frequencies
GSM850 systems use radio frequencies between 824-849 MHz for receive and between 869-894
MHz for transmit, as shown in Figure 1-19. RF carriers are spaced every 200 kHz, allowing a
total of 124 carriers for use. Other frequencies between 851 MHz and 869 MHz are available
for use by other (non-GSM) cellular systems. A guard band of 2 MHz of unused frequencies
between 849 MHz and 851 MHz protects against interference between the transmit and receive
frequencies. Guard bands between GSM and non-GSM frequencies depend on the prevailing
standards in the country concerned and on agreements reached by network operators. Any
such guard bands are likely to be small, for example, the last carrier of the frequency range
is left unused.
Transmit and receive frequencies are separated by 45 MHz, and this fixed frequency gap
reduces the possibility of interference.
68P02901W01-S 1-69
Jul 2008
GSM850 channels Chapter 1: Introduction to Motorola GSM
GSM850 channels
Channels 128-130
Table 1-9 shows the frequencies for GSM850 channels 128 to 130.
1-70 68P02901W01-S
Jul 2008
System Information: GSM Overview GSM850 channels
Channels 131-140
Table 1-10 shows the frequencies for GSM850 channels 113 to 140.
Channels 141-150
Table 1-11 shows the frequencies for GSM850 channels 141 to 150.
68P02901W01-S 1-71
Jul 2008
GSM850 channels Chapter 1: Introduction to Motorola GSM
Channels 151-160
Table 1-12 shows the frequencies for GSM850 channels 151 to 160.
Channels 161-170
Table 1-13 shows the frequencies for GSM850 channels 161 to 170.
1-72 68P02901W01-S
Jul 2008
System Information: GSM Overview GSM850 channels
Channels 171-180
Table 1-14 shows the frequencies for GSM850 channels 171 to 180.
Channels 181-190
Table 1-15 shows the frequencies for GSM850 channels 181 to 190.
68P02901W01-S 1-73
Jul 2008
GSM850 channels Chapter 1: Introduction to Motorola GSM
Channels 191-200
Table 1-16 shows the frequencies for GSM850 channels 191 to 200.
Channels 201-210
Table 1-17 shows the frequencies for GSM850 channels 201 to 210.
1-74 68P02901W01-S
Jul 2008
System Information: GSM Overview GSM850 channels
Channels 211-220
Table 1-18 shows the frequencies for GSM850 channels 211 to 220.
Channels 221-230
Table 1-19 shows the frequencies for GSM850 channels 221 to 230.
68P02901W01-S 1-75
Jul 2008
GSM850 channels Chapter 1: Introduction to Motorola GSM
Channels 231-240
Table 1-20 shows the frequencies for GSM850 channels 231 to -240.
Channels 241-251
Table 1-21 shows the frequencies for GSM850 channels 241 to 251.
1-76 68P02901W01-S
Jul 2008
System Information: GSM Overview Primary GSM900 frequencies
This section lists all the frequencies used in Primary GSM (PGSM), with their channel numbers
in both decimal and hexadecimal notation.
GSM900 systems use radio frequencies between 890 MHz and 915 MHz for receive and
between 935 MHz and 960 MHz for transmit, as shown in Figure 1-20. RF carriers are spaced
every 200 kHz, allowing a total of 124 carriers for use. Other frequencies between 917 MHz and
935 MHz are available for use by other (non-GSM) cellular systems. A guard band of 2 MHz
of unused frequencies between 915 MHz and 917 MHz protects against interference between
the transmit and receive frequencies. Guard bands between GSM and non-GSM frequencies
depend on the prevailing standards in the country concerned and on agreements reached by
network operators. Any such guard bands are likely to be small; for example, the last carrier of
the frequency range is left unused.
Transmit and receive frequencies are separated by 45 MHz, and this fixed frequency gap
reduces the possibility of interference.
68P02901W01-S 1-77
Jul 2008
Primary GSM900 channels Chapter 1: Introduction to Motorola GSM
Channels 1-10
Table 1-22 shows the frequencies for Primary GSM (PGSM) channels 1 to 10.
Channels 11-20
1-78 68P02901W01-S
Jul 2008
System Information: GSM Overview Primary GSM900 channels
Channels 21-30
Channels 31-40
68P02901W01-S 1-79
Jul 2008
Primary GSM900 channels Chapter 1: Introduction to Motorola GSM
Channels 41-50
Channels 51-60
1-80 68P02901W01-S
Jul 2008
System Information: GSM Overview Primary GSM900 channels
Channels 61-70
Channels 71-80
68P02901W01-S 1-81
Jul 2008
Primary GSM900 channels Chapter 1: Introduction to Motorola GSM
Channels 81-90
Channels 91-100
1-82 68P02901W01-S
Jul 2008
System Information: GSM Overview Primary GSM900 channels
Channels 101-110
Table 1-32 shows the frequencies for PGSM channels 101 to 110.
Channels 111-120
Table 1-33 shows the frequencies for PGSM channels 111 to 120.
68P02901W01-S 1-83
Jul 2008
EGSM frequencies Chapter 1: Introduction to Motorola GSM
Channels 121-124
Table 1-34 shows the frequencies for PGSM channels 121 to 124.
EGSM frequencies
This section lists all the extra frequencies used in Extended GSM (EGSM), with their channel
numbers in both decimal and hexadecimal notation. EGSM also uses all frequencies listed in
PGSM frequencies and PGSM channels.
Figure 1-21 shows that further 10 MHz of bandwidth on both transmit and receive allocations
has now extended the GSM900 bandwidth.
1-84 68P02901W01-S
Jul 2008
System Information: GSM Overview EGSM channels
Extension band system with origination across the entire 35 MHz (BCCH+SDCCH in
EGSM).
The advanced load handover management function offers, the operator, the ability to specify
EGSM band handovers only to other EGSM bands. Otherwise EGSM handovers can occur to
neighboring cells that do not have an EGSM band available. DCS1800 band is used wastefully,
particularly if the band_preference parameter is set, for example, to DCS1800. A new
parameter bss_egsm_alm_allowed enables the feature and EGSM handovers occur only to
EGSM sites, whatever the setting of band_preference.
EGSM channels
Channels 975-984
Table 1-35 shows the frequencies for EGSM channels 975 to 984.
68P02901W01-S 1-85
Jul 2008
EGSM channels Chapter 1: Introduction to Motorola GSM
Channels 985-994
Table 1-36 shows the frequencies for EGSM channels 985 to 994.
Channels 995-1004
Table 1-37 shows the frequencies for EGSM channels 995 to 1004.
1-86 68P02901W01-S
Jul 2008
System Information: GSM Overview EGSM channels
Channels 1005-1014
Table 1-38 shows the frequencies for EGSM channels 1005 to 1014.
Channels 1015-0
68P02901W01-S 1-87
Jul 2008
DCS1800 frequencies and channels Chapter 1: Introduction to Motorola GSM
DCS1800 frequencies
This section lists the frequencies used in Digital Cellular System (DCS) 1800, with their channel
numbers in both decimal and hexadecimal notation.
DCS1800 systems use radio frequencies between 1710-1785 MHz for receive and between
1805-1880 MHz for transmit, as shown in Figure 1-22. RF carriers are spaced every 200 kHz,
allowing a total of 373 carriers for use, with one used as a guard band. A guard band of 20 MHz
of unused frequencies between 1785 MHz and 1805 MHz protects against interference between
the transmit and receive frequencies. There is a 100 kHz guard band between 1710.0 MHz and
1710.1 MHz and between 1784.9 MHz and 1785.0 MHz for receive, and between 1805.0 MHz
and 1805.1 MHz and between 1879.9 MHz and 1880.0 MHz for transmit.
Transmit and receive frequencies are separated by 95 MHz, and this fixed frequency gap
reduces the possibility of interference.
1-88 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
DCS1800 channels
Channels 512-520
Table 1-40 shows the frequencies for DCS1800 channels 512 to 520.
Channels 521-530
Table 1-41 shows the frequencies for DCS1800 channels 521 to 530.
68P02901W01-S 1-89
Jul 2008
DCS1800 channels Chapter 1: Introduction to Motorola GSM
Channels 531-540
Table 1-42 shows the frequencies for DCS1800 channels 531 to 540.
Channels 541-550
Table 1-43 shows the frequencies for DCS1800 channels 541 to 550.
1-90 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
Channels 551-560
Table 1-44 shows the frequencies for DCS1800 channels 551 to 560.
Channels 561-570
Table 1-45 shows the frequencies for DCS1800 channels 561 to 570.
68P02901W01-S 1-91
Jul 2008
DCS1800 channels Chapter 1: Introduction to Motorola GSM
Channels 571-580
Table 1-46 shows the frequencies for DCS1800 channels 571 to 580.
Channels 581-590
Table 1-47 shows the frequencies for DCS1800 channels 581 to 590.
1-92 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
Channels 591-600
Table 1-48 shows the frequencies for DCS1800 channels 591 to 600.
Channels 601-610
Table 1-49 shows the frequencies for DCS1800 channels 601 to 610.
68P02901W01-S 1-93
Jul 2008
DCS1800 channels Chapter 1: Introduction to Motorola GSM
Channels 611-620
Table 1-50 shows the frequencies for DCS1800 channels 611 to 620.
Channels 621-630
Table 1-51 shows the frequencies for DCS1800 channels 621 to 630.
1-94 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
Channels 631-640
Table 1-52 shows the frequencies for DCS1800 channels 631 to 640.
Channels 641-650
Table 1-53 shows the frequencies for DCS1800 channels 641 to 650.
68P02901W01-S 1-95
Jul 2008
DCS1800 channels Chapter 1: Introduction to Motorola GSM
Channels 651-660
Table 1-54 shows the frequencies for DCS1800 channels 651 to 660.
Channels 661-670
Table 1-55 shows the frequencies for DCS1800 channels 661 to 670.
1-96 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
Channels 671-680
Table 1-56 shows the frequencies for DCS1800 channels 671 to 680.
Channels 681-690
Table 1-57 shows the frequencies for DCS1800 channels 681 to 690.
68P02901W01-S 1-97
Jul 2008
DCS1800 channels Chapter 1: Introduction to Motorola GSM
Channels 691-700
Table 1-58 shows the frequencies for DCS1800 channels 691 to 700.
Channels 701-710
Table 1-59 shows the frequencies for DCS1800 channels 701 to 710.
1-98 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
Channels 711-720
Table 1-60 shows the frequencies for DCS1800 channels 711 to 720.
Channels 721-730
Table 1-61 shows the frequencies for DCS1800 channels 721 to 730.
68P02901W01-S 1-99
Jul 2008
DCS1800 channels Chapter 1: Introduction to Motorola GSM
Channels 731-740
Table 1-62 shows the frequencies for DCS1800 channels 731 to 740.
Channels 741-750
Table 1-63 shows the frequencies for DCS1800 channels 741 to 750.
1-100 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
Channels 751-760
Table 1-64 shows the frequencies for DCS1800 channels 751 to 760.
Channels 761-770
Table 1-65 shows the frequencies for DCS1800 channels 761 to 770.
68P02901W01-S 1-101
Jul 2008
DCS1800 channels Chapter 1: Introduction to Motorola GSM
Channels 771-780
Table 1-66 shows the frequencies for DCS1800 channels 771 to 780.
Channels 781-790
Table 1-67 shows the frequencies for DCS1800 channels 781 to 790.
1-102 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
Channels 791-800
Table 1-68 shows the frequencies for DCS1800 channels 791 to 800.
Channels 801-810
Table 1-69 shows the frequencies for DCS1800 channels 801 to 810.
68P02901W01-S 1-103
Jul 2008
DCS1800 channels Chapter 1: Introduction to Motorola GSM
Channels 811-820
Table 1-70 shows the frequencies for DCS1800 channels 811 to 820.
Channels 821-830
Table 1-71 shows the frequencies for DCS1800 channels 821 to 830.
1-104 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
Channels 831-840
Table 1-72 shows the frequencies for DCS1800 channels 831 to 840.
Channels 841-850
Table 1-73 shows the frequencies for DCS1800 channels 841 to 850.
68P02901W01-S 1-105
Jul 2008
DCS1800 channels Chapter 1: Introduction to Motorola GSM
Channels 851-860
Table 1-74 shows the frequencies for DCS1800 channels 851 to 860.
Channels 861-870
Table 1-75 shows the frequencies for DCS1800 channels 861 to 870.
1-106 68P02901W01-S
Jul 2008
System Information: GSM Overview DCS1800 channels
Channels 871-880
Table 1-76 shows the frequencies for DCS1800 channels 871 to 880.
Channels 881-885
Table 1-77 shows the frequencies for DCS1800 channels 881 to 885.
68P02901W01-S 1-107
Jul 2008
PCS1900 frequencies and channels Chapter 1: Introduction to Motorola GSM
PCS1900 frequencies
This section lists the frequencies used in PCS1900, with their channel numbers in both decimal
and hexadecimal notation.
PCS1900 systems use radio frequencies between 1850-1910 MHz for receive and between
1930-1990 MHz for transmit, as shown in Figure 1-23. RF carriers are spaced every 200 kHz,
allowing a total of 299 carriers for use. A guard band of 20 MHz of unused frequencies between
1910 MHz and 1930 MHz protects against interference between the transmit and receive
frequencies. There is a 100 kHz guard band between 1850.0 MHz and 1850.1 MHz and between
1909.9 MHz and 1910.0 MHz for receive, and between 1930.0 MHz and 1930.1 MHz and
between 1989.9 MHz and 1990.0 MHz for transmit.
Transmit and receive frequencies are separated by 80 MHz, and this fixed frequency gap
reduces the possibility of interference.
1-108 68P02901W01-S
Jul 2008
System Information: GSM Overview PCS1900 channels
PCS1900 channels
Channels 512-520
Table 1-78 shows the frequencies for PCS1900 channels 512 to 520.
Channels 521-530
Table 1-79 shows the frequencies for PCS1900 channels 521 to 530.
68P02901W01-S 1-109
Jul 2008
PCS1900 channels Chapter 1: Introduction to Motorola GSM
Channels 531-540
Table 1-80 shows the frequencies for PCS1900 channels 531 to 540.
Channels 541-550
Table 1-81 shows the frequencies for PCS1900 channels 541 to 550.
1-110 68P02901W01-S
Jul 2008
System Information: GSM Overview PCS1900 channels
Channels 551-560
Table 1-82 shows the frequencies for PCS1900 channels 551 to 560.
Channels 561-570
Table 1-83 shows the frequencies for PCS1900 channels 561 to 570.
68P02901W01-S 1-111
Jul 2008
PCS1900 channels Chapter 1: Introduction to Motorola GSM
Channels 571-580
Table 1-84 shows the frequencies for PCS1900 channels 571 to 580.
Channels 581-590
Table 1-85 shows the frequencies for PCS1900 channels 581 to 590.
1-112 68P02901W01-S
Jul 2008
System Information: GSM Overview PCS1900 channels
Channels 591-600
Table 1-86 shows the frequencies for PCS1900 channels 591 to 600.
Channels 601-610
Table 1-87 shows the frequencies for PCS1900 channels 601 to 610.
68P02901W01-S 1-113
Jul 2008
PCS1900 channels Chapter 1: Introduction to Motorola GSM
Channels 611-620
Table 1-88 shows the frequencies for PCS1900 channels 611 to 620.
Channels 621-630
Table 1-89 shows the frequencies for PCS1900 channels 621 to 630.
1-114 68P02901W01-S
Jul 2008
System Information: GSM Overview PCS1900 channels
Channels 631-640
Table 1-90 shows the frequencies for PCS1900 channels 631 to 640.
Channels 641-650
Table 1-91 shows the frequencies for PCS1900 channels 641 to 650.
68P02901W01-S 1-115
Jul 2008
PCS1900 channels Chapter 1: Introduction to Motorola GSM
Channels 651-660
Table 1-92 shows the frequencies for PCS1900 channels 651 to 660.
Channels 661-670
Table 1-93 shows the frequencies for PCS1900 channels 661 to 670.
1-116 68P02901W01-S
Jul 2008
System Information: GSM Overview PCS1900 channels
Channels 671-680
Table 1-94 shows the frequencies for PCS1900 channels 671 to 680.
Channels 681-690
Table 1-95 shows the frequencies for PCS1900 channels 681 to 690.
68P02901W01-S 1-117
Jul 2008
PCS1900 channels Chapter 1: Introduction to Motorola GSM
Channels 691-700
Table 1-96 shows the frequencies for PCS1900 channels 691 to 700.
Channels 701-710
Table 1-97 shows the frequencies for PCS1900 channels 701 to 710.
1-118 68P02901W01-S
Jul 2008
System Information: GSM Overview PCS1900 channels
Channels 711-720
Table 1-98 shows the frequencies for PCS1900 channels 711 to 720.
Channels 721-730
Table 1-99 shows the frequencies for PCS1900 channels 721 to 730.
68P02901W01-S 1-119
Jul 2008
PCS1900 channels Chapter 1: Introduction to Motorola GSM
Channels 731-740
Table 1-100 shows the frequencies for PCS1900 channels 731 to 740.
Channels 741-750
Table 1-101 shows the frequencies for PCS1900 channels 741 to 750.
1-120 68P02901W01-S
Jul 2008
System Information: GSM Overview PCS1900 channels
Channels 751-760
Table 1-102 shows the frequencies for PCS1900 channels 751 to 760.
Channels 761-770
Table 1-103 shows the frequencies for PCS1900 channels 761 to 770.
68P02901W01-S 1-121
Jul 2008
PCS1900 channels Chapter 1: Introduction to Motorola GSM
Channels 771-780
Table 1-104 shows the frequencies for PCS1900 channels 771 to 780.
Channels 781-790
Table 1-105 shows the frequencies for PCS1900 channels 781 to 790.
1-122 68P02901W01-S
Jul 2008
System Information: GSM Overview PCS1900 channels
Channels 791-800
Table 1-106 shows the frequencies for PCS1900 channels 791 to 800.
Channels 801-810
Table 1-107 shows the frequencies for PCS1900 channels 801 to 810.
68P02901W01-S 1-123
Jul 2008
PCS1900 channels Chapter 1: Introduction to Motorola GSM
1-124 68P02901W01-S
Jul 2008
Chapter
This chapter provides a general description of the Motorola Base Station System (BSS), which
forms part of the GSM digital cellular system.
The GSM recommendations define the functions of the BSS, but allow flexibility in its design.
This chapter also describes some of the unique features of the Motorola BSS.
68P02901W01-S 2-1
Jul 2008
Base station system Chapter 2: BSS General Description
The BSS is the interface between the Mobile Station (MS) and the Mobile services Switching
Center (MSC) elements of the network.
The BSS performs a variety of functions. The following comprise the functions provided by the
BSS:
Radio coverage areas and control functions for one or more cells.
Radio coverage areas and control functions for the MSs in the cells.
Signaling data processing and routing of the traffic data exchanged between the MS
and the MSC.
Digital signal interfaces to the land circuits linking the BSS and the MSC.
Links
The BSS has links to the MSC and the MSs. The following comprise the links:
Interface links
Land circuits link the Base Station Controller (BSC) to the MSC. Each interface link contains a
multiplexed E1 serial data stream. The BSS places MS originated or MS terminated subscriber
(signaling or traffic) data in a timeslot (channel) on a serial data stream.
The communication link, or Air Interface, between the BSS and the MS uses digital radio
techniques.
2-2 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS network elements
The BSS consists of three basic Network Elements (NEs). The following comprise the network
elements:
Base Station Controller (BSC).
Speech transcoder (XCDR) or remote speech transcoder (RXCDR) assigned to the BSC.
Figure 2-1 shows the layout of a typical system with two BSSs. Each BSS contains several
components to make the link between the MS and the MSC. The BSS components are described
in more detail in the following sections.
68P02901W01-S 2-3
Jul 2008
Typical BSS layout Chapter 2: BSS General Description
BSS #1 BSS #2
MS
BTS
SITE
MS MS
BTS
SITE
BTS BTS
MS SITE
SITE
BSC
SITE
WITH BTS
XCDR SITE
MS
BTS
SITE
BSC
SITE
BTS
SITE
RXCDR
(NOTE 2)
A MSC
LEGEND
Air Interface
NOTE
(1) DASHED LINES ENCLOSE NETWORK COMPONENTS
OF A PARTICULAR BSS AND DO NOT SHOW THE BSS
SER VICE AREA.
(2) REMOTE TRANSCODING (RXCDR) IS LOCA TED AT
MSC SITE, BUT IS P ART OF BSS #2.
ti-GSM-Dual BSS-00043-ai-sw
2-4 68P02901W01-S
Jul 2008
System Information: GSM Overview BSC description
BSC description
The BSC network element provides the control for the BSS. It controls and manages the
associated BTSs, and interfaces with the Operation and Maintenance Center (OMC).
The purpose of the BSC is to perform a variety of functions. The following comprise the
functions provided by the BSC:
Controls the BTS components.
Provides the Operation and Maintenance link (OML) between the BSS and the OMC.
The MSC communicates with, and passes signaling and traffic data to BSCs. The BSCs provide
the opportunity for remote switching, distributed control, and traffic concentration.
Many types of call handling signal do not affect the BSC directly. In these cases, the BSC serves
as a relay point between an MS and the MSC.
The BSC includes a digital switching matrix. There is no fixed correspondence between the
radio channels at the BSS and the terrestrial circuits (trunks), which connect the BSS to the
MSC. While the BSC selects the radio channel, the MSC selects the trunks.
The BSC connects the traffic channel (TCH) assigned to a particular MS with the trunk assigned
by the MSC.
The switching matrix also lets the BSS perform handovers within a single BSS without involving
the MSC.
68P02901W01-S 2-5
Jul 2008
Terrestrial circuit device management Chapter 2: BSS General Description
This feature enables CICs to be identified in three ways: By CIC number, on the MMS basis, on
the MMS basis providing timeslot and, if appropriate, group within a timeslot.
BSC capacity
Scalable BSC capacity is enabled through the further exploitation of the increased processing
performance and memory of the GPROC2/ GPROC3. As a result GPROC2s and/or GPROC3s are
required throughout the BSC. The BSC maximum capacity is increased as shown in Table 2-1.
{28398}
Table 2-1 BSC maximum capacities
This increased capacity is achieved through the deployment of GPROC2s, GPROC3s for each
function at the BSC, including Base Station Processor (BSP) and Link Control Function (LCF).
BSCs for a given capacity are available, with hardware and software, according to the required
capacity.
2-6 68P02901W01-S
Jul 2008
System Information: GSM Overview BTS description
BTS description
The BTS network element consists of the hardware components, such as radios, interface
modules and antenna systems. The network elements provide the Air Interface between the
BSS and the MSs.
The BTS radio equipment used must be able to support the type of operation required, that is,
GSM900, EGSM900, DCS1800, or PCS1900. Refer to GSM frequencies and channels on
page 1-69 for an explanation of the characteristics of these systems.
The BTS provides radio channels (RF carriers) for a specific RF coverage area. The radio
channel is the communication link between the MSs within the RF coverage area and the
BSS. A single BTS site contains all the BTS network components that provide RF channels for
the same geographic area.
The BTS also has a limited amount of control functionality, which reduces the amount of traffic
between the BTS and BSC.
The RF frequency of the channels that each BTS site in the network provides.
RF coverage areas
The term, cell defines a single RF coverage area which is either a multidirectional and sectored
area, or an omnidirectional single area.
The antenna system at the BTS site determines the type of RF coverage area.
68P02901W01-S 2-7
Jul 2008
Antenna systems Chapter 2: BSS General Description
Antenna systems
BTS site equipment (RF hardware) can be configured for operation with the following types
of antenna systems for RF coverage areas:
One omnidirectional sector.
2-8 68P02901W01-S
Jul 2008
System Information: GSM Overview Transcoder description
Transcoder description
The speech transcoder (XCDR) is the digital signal processing equipment that performs GSM
defined speech encoding and decoding within the network.
The speech transcoder is the interface between the 64 kbps PCM channel in the land network
and the 13 kbps vocoder (22.8 kbps after channel coding) channel used on the Air Interface.
This reduces the amount of information carried on the Air Interface and hence, its bandwidth.
NOTE
13 kbps is the data rate of speech. This is mapped onto 16 kbps Transcoder
Rate Adaption Unit (TRAU) frames and then channel coded for protection, finally
comprising 22.8 kbps.
The transcoder can multiplex four traffic channels (with GSM or AMR half rate, eight traffic
channels are possible in the optimum case) into a single 64 kbps channel (timeslot). Therefore,
an E1 serial link can carry four times as many channels which can reduce the number of E1
leased lines required to connect remotely located equipment.
Remote transcoder
Speech transcoding can take place either at the BSC or between the MSC and BSC. When the
transcoder is between the MSC and the BSC it is called a remote transcoder (RXCDR).
Transcoding location
The location of the XCDR affects the overall cost of leased lines.
If transcoding takes place at the BSC, then the number of leased lines required to connect the
BSC to the required BTSs is reduced.
If transcoding takes place remotely at the MSC, then the number of leased lines from the MSC
(RXCDR) to the BSC is also reduced, thus providing greater savings.
68P02901W01-S 2-9
Jul 2008
BSS site configuration Chapter 2: BSS General Description
The Motorola BSS uses a variety of BSC, BTS, and RXCDR site configurations to meet a wide
range of requirements.
The following items must be considered when meeting requirements for cell site configuration:
The number of RF carriers.
Congestion relief.
BSS configurations
The BSS is set up to perform a variety of functions. In order to perform those functions, the
following equipment is required:
A BSC site.
An RXCDR site is necessary if XCDR functionality is not integrated with the BSC. However,
note that the RXCDR is considered a separate site which is not part of the BSS.
Flexibility
Motorola BSS equipment uses a flexible architecture that expands easily. The BSC, BTS, and
RXCDR can start small and expand incrementally. The size of the Motorola BSC provides
significant switching capability to handle a variety of different BTS sites and network
configurations.
2-10 68P02901W01-S
Jul 2008
System Information: GSM Overview Definitions
Definitions
BSC
Provides the BSC function for controlling BTS sites. A Base Station System Control (BSSC)
cabinet can contain the necessary modules for the BSC-to-BTS line interface and for the
BSC-to-MSC line interface, acting as different BSCs. Alternatively, the equipment can be
connected to form a single BSC.
RXCDR
Provides the RXCDR function for speech transcoding. For example, the BSSC2 cabinet, contains
the necessary modules for the BSC-to-RXCDR line interface and speech transcoder modules
as part of the line interface to the MSC. Alternatively, the two shelves can be combined for
more capacity.
The BSSC2 cabinet is equipped to provide both the BSC function for controlling BTS sites and
the XCDR function for speech transcoding within one shelf. Alternatively, it could have the BSC
in one shelf and the XCDR in the other. This cabinet contains the modules needed for the
BSC-to-BTS, BSC-to-MSC, and XCDR functions.
The maximum capacity of a BSS is 2400 trunks from the MSC (3200 with the Enhanced Capacity
option). This maximum is independent of the number of BTS sites.
In order to achieve 384 carriers for the BSC on the Dense Urban Call model (the primary
motivation for this feature), the following assumptions regarding the BSC are made:
Support of two Message Transfer Links (MTLs) per Link Control Function (LCF) at 40%
MTL link utilization.
Support of 25 LCFs.
NOTE
Increasing the number of trunks limit does not provide value for Dense Urban
environments unless these assumptions hold true.
68P02901W01-S 2-11
Jul 2008
BTS cabinet Chapter 2: BSS General Description
BTS cabinet
A BTS cabinet contains the radio transceivers and associated Air Interface modules that make
up the BTS function. The BTS cabinet can contain equipment for up to six RF carriers and
support up to three different RF coverage areas or sectors.
A BTS cabinet can be configured to provide the BTS functions only. For this type of cabinet,
the following are the BTS functions provided:
The Air Interface to the MSs.
BSSC cabinet
BSS/MSC configurations
If a BSSC2 cabinet with the XCDR is not implemented, speech transcoding can be integrated
into the BSSC2 cabinet with the BSC function.
Figure 2-2 shows examples of two BSSs, designated BSS #1 and #2, with more than one BTS
site. The BTS sites in these BSSs contain BTS cabinets that perform the BTS function only; they
do not include the BSC function or transcoding.
A separate BSC site operates the BTS sites of BSS #1 remotely. The BSSC2 cabinet for this
BSS integrates transcoding for this BSS with the BSC function.
A separate BSC operates the BTS sites of BSS #2 remotely. Transcoding for this BSS is located
remotely in a BSSC2 cabinet at the MSC site.
2-12 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS with more than one BTS
RXCDR OMC-G
(Including Shelf
Manager)
OMC-R
BSSn GSN
BTSs COMMHUB
BSS2 GSNn
BSS1 GSN1
ti-GSM-GSM equipmentarchitecture-00020-ai-sw
For correct implementation of the multiple BTS feature, the BSS supports the following
functionality:
The source cell does not attempt a congestion relief handover, to a target cell which had rejected
a previous handover attempt. The attempt is not made for a period of time, both imperative
and congestion relief. A new timer element is used to control this period of time. It does not,
however, affect any imperative handover retries. These handovers are allowed to take place
regardless of such timers, as they have to keep the call active.
68P02901W01-S 2-13
Jul 2008
Flexible neighbor cell processing Chapter 2: BSS General Description
If a BSS target cell rejects an incoming handover, the target cell attempts to inform the source
cell of its future, intra-BSS only accessibility status. The rejection is because that handover
would trigger congestion relief procedures. If the target cell is configured to optionally invoke
congestion relief procedures after rejecting the handover request, then it is capable of handling
the necessary handovers.
If a BSS target cell accepts an incoming handover, the target cell does not trigger any handover
attempts back to the source cell. The acceptance occurs when the handover itself triggers
the target cell congestion relief procedures.
Handover retry
The source cell optionally retries an imperative, intra-BSS only handover to target cells, which
rejected the initial handover request and initiated a congestion relief procedure.
If the servicing of a handover causes the percentage to exceed, the BSS does not allow an
incoming band preference handover. If such a handover is serviced, the net result is simply the
movement of a Multiband congestion problem from one cell to another.
This feature enhances the existing handover decision process by adding more flexibility in the
way neighbor cell processing is handled for handovers.
Neighbor cells with lower RXLEV readings than the servicing cell are valid candidates for
handovers.
Neighbor cells whose disuse count is less than or equal to the maximum disuse count are valid
candidates for handovers.
Neighbor cells use RXQUAL or RXLEV handovers only when the Base or the Mobile is at full
power. This feature removes all candidates for interference handovers until the mobile or the
base reaches full power (Applicable only for decision algorithm 1).
2-14 68P02901W01-S
Jul 2008
System Information: GSM Overview Flexible neighbor cell processing
This parameter allows no warm-up period for neighbor cells. Averaging and power budget
calculations begin immediately.
68P02901W01-S 2-15
Jul 2008
Network topology Chapter 2: BSS General Description
Network topology
Basic configurations
Combinations of these configurations can be used to connect the BSC-to-remote BTS sites.
Topology model
Network topology is specified in terms of the continuous traffic routes between the BSC and
a terminating remote BTS site, including any intermediate remote BTS sites. Physical site
interconnections are through E1 links.
Figure 2-3 shows a possible topology using combinations of the three basic configurations. Site
interconnections in the figure represent E1 links, not traffic routes. The actual connections
between network sites can consist of single or multiple E1 links.
The subsections that follow describe typical traffic routes for each configuration.
2-16 68P02901W01-S
Jul 2008
System Information: GSM Overview Star (spoke)
Star (spoke)
The traffic route is from the BSC site to terminating site BTS 10.
The BSC site through intermediate site BTS 12 to terminating site BTS 13.
The BSC site through intermediate sites BTS 12 and BTS 13 to terminating site BTS 14.
Table 2-2 shows the main paths to the BSC for each BTS and the alternate path for each BTS
in the looped part of the network.
Table 2-2 BTS - BSC main and alternate paths (fork with return loop)
Fault condition
If there is a fault anywhere in the fork, the return loop provides an alternative communications
route between the BSC and BTS 9.
For example, a break in the E1 links between BTSs 6 and 9 causes BTSs 5, 6, 7, 8 and 9 to
function like an open-ended chain. The chain allows site BTS 9 to communicate with the BSC.
68P02901W01-S 2-17
Jul 2008
Daisy chain with fork and return loop to BSC Chapter 2: BSS General Description
Table 2-3 shows that for each BTS, one main path and at least one alternate path exist to the BSC.
Table 2-3 BTS - BSC main and alternate paths (chain with return loop)
Fault condition
If there is a fault anywhere in the chain, alternate paths provide each BTS site on the chain or
fork with an alternate communication route to the BSC.
For example, assume there is a break in the E1 link(s) between BTSs 2 and 3. BTSs 11, 2,
and 1 function like an open-ended chain and communicate with the BSC through the traffic
routes on the operational part of the loop. BTSs 3 and 4 function like an open-ended chain and
communicate with the BSC through the traffic routes on the operational part of the loop.
The drop and insert option enhances the flexibility of Motorola BSS equipment configuration.
This option allows a single E1 circuit to connect several BTS sites in either a linear daisy chain
or a ring topology. The closing end of the ring of BTS sites connects to a BSC.
Fault tolerance
A closed-loop or closed-ring topology enhances the fault tolerance of the drop and insert
configuration. This topology prevents any single line fault from interrupting communication
to any site.
The Motorola drop and insert option for BTS sites saves on leased line costs when addressing
sparse rural or special coverage requirements such as highways.
GSM compliance
A maximum of 10 BTS sites can be chained together in a closed loop and still comply with GSM
system timing and delay recommendations.
2-18 68P02901W01-S
Jul 2008
System Information: GSM Overview Drop and insert BTS site configuration
Maximum size
Each BTS site in the drop and insert configuration has one or more BTS cabinets. While
chaining the maximum number of BTS sites together, each BTS cabinet in the drop and insert
configuration contains one radio transceiver and associated air interface modules. The cabinet
also contains modules to provide the line interfaces to a BSSC or a BTS cabinet.
If a particular site requires additional transceivers, the maximum number of sites chained
together must be reduced proportionately.
68P02901W01-S 2-19
Jul 2008
BSS standardized interfaces Chapter 2: BSS General Description
Many GSM recommendations deal with standards for interfaces between network elements.
Motorola employs internationally recognized standards for most of the network communications.
For example, Motorola uses ITU-TSS Signaling System 7 (C7) and X.25 protocols extensively
throughout the network.
Using Standardized interfaces throughout the GSM digital cellular system ensures compatibility
of network elements from different manufacturers.
Protocol layering
The functional layering of protocols is based in part on the seven layer model for open systems
interconnection suggested by the International Standards Organization (ISO). Each layer
performs a specific set of functions that are isolated from the other layers. However, the
functions of a particular layer enhance the functions performed by the lower layers.
The following subsections detail the BSS-related equipment-to-equipment interfaces that are
standardized and specified by GSM.
A interface
The interface between the MSC and the BSS is a standard interface, called the A Interface. The
A Interface is fully defined in the GSM recommendations.
The signaling portion of the interface between the MSC and the BSC uses the C7 protocol.
Application parts are defined for the C7 protocol. For example, the base station system
application part (BSSAP) is defined.
The A Interface allows customers to purchase the switching equipment from different suppliers.
For example, the MSC from one supplier, and the radio equipment (such as the BSS) from
another supplier, and still have equipment compatibility.
Abis interface
The GSM defined interface between the BSC and the remotely located BTS equipment is called
the Abis interface. It uses Link Access Procedure D (LAPD).
At the application levels, GSM defines a special set of messages unique to the mobile application.
2-20 68P02901W01-S
Jul 2008
System Information: GSM Overview Air interface
Mobis
The Motorola defined BSC-to-BTS interface is a modification of the Abis standard called Mobis.
It distributes functionality between the BSC and the remote BTS equipment, and offers several
advantages:
Reduced signaling link traffic, which permits efficient use of E1 links. The BTS performs
handover data processing which reduces the amount of data sent to the BSC over the
signaling link. This significantly reduces the amount of processing required in the BSC.
Better synchronization of the BSC and BTS ensures better handover from one traffic
channel to another.
Air interface
The GSM recommendations include detailed specifications for the radio channel (Air Interface)
between the MS and the BTS. The Air Interface uses a three layer protocol.
Layer 1 is the physical channel layer. This layer transmits and receives coded information
symbols over the radio link. Layer 1 provides the basic time division multiplexing (TDM)
frame structure including timeslot, frame, multiframe, and so on. Layer 1 also provides for
multiplexing and demultiplexing (channel encoding/decoding) of the different types of logical
channels that the network requires, such as traffic channels, signaling or control channels and
synchronization channels.
Layer 2 is a transport mechanism between layer 3 and layer 1. Layer 2 provides for error
free transport of layer 3 signaling.
Call management (call setup, supplementary services, Dual Tone Multi-Frequency (DTMF),
short message service).
68P02901W01-S 2-21
Jul 2008
Lb interface Chapter 2: BSS General Description
Lb interface
The Lb-interface is for the support of location services. It is located between the BSS and a
BSS-based SMLC. The interface uses the C7 protocol, and is modeled (from the BSS viewpoint)
from the A-Interface. The interface is not present when the SMLC is NSS-based.
2-22 68P02901W01-S
Jul 2008
System Information: GSM Overview Radio system and control functions
The Air Interface provides an associated control channel. This allows communication of signaling
control channel data simultaneously with (and transparent to) user traffic channel (TCH) data.
The associated control channel is available for both the uplink and the downlink. It allows
continuous information reporting from the MS to the BSS, and continuous control of the MS
from the BSS.
Handover
The GSM handover process uses a mobile assisted technique for accurate and fast handovers, to:
Maintain the user connection link quality.
Minimize interference.
3-timeslot offset
The TDMA frame structure for uplink transmission is offset by three timeslots from the downlink
frame structure; this interval allows the MS to have only one synthesizer to assess the signal
level of adjacent cells. SACCH and other signaling information, which is sent transparently with
user traffic, allows continuous reporting of information from the subscriber to the base and the
continuous control of the mobile from the base.
Because of this offset, the MS never has to transmit and receive simultaneously. The ability of
the MS to change frequency and monitor a neighbor channel while engaged in a speech or data
conversation is important for the high performance MS assisted handover scheme employed.
MS assisted technique
The MS assists the handover decision process by performing certain measurements. When the
MS is engaged in a speech (or data) conversation, a portion of the TDMA frame is idle while
the rest of the frame is used for uplink (BTS receive) and downlink (BTS transmit) timeslots.
During the idle time period of the frame, the MS changes radio channel frequency and monitors
and measures the signal level of the six best adjacent cells.
Measurements, which feed the handover decision algorithm are made at both ends of the
radio link.
68P02901W01-S 2-23
Jul 2008
Dynamic power control Chapter 2: BSS General Description
MS end
At the MS end, measurements are continuously signaled, through the associated control
channel, to the BSS where the decision for handover is ultimately made.
MS measurements include:
Serving cell downlink quality (bit error rate (BER) estimate).
Serving cell downlink received signal level, and adjacent cells downlink received signal
level.
The MS also decodes the Base Station ID Code (BSIC) from the six best adjacent cells, and
reports the BSICs and the measurement information to the BTS.
BTS end
At the BTS site end, measurements involve only the uplink communication path, link quality,
received signal level, and MS to BTS site distance. The measurements are available to the
handover algorithm. The MS RF transmit output power budget is also considered in the
handover decision. If an adjacent cell serves the MS at a lower power, the handover is
recommended. From a system perspective, handover is considered due to loading or congestion
conditions. In this case, the MSC or BSC tries to balance channel usage among cells.
ti-GSM-HO measurements-00046-ai-sw
As the MS gets closer to the BTS, both use less power to transmit. Over a 30 dB range, power
is stepped up or down in 2 dB steps. Power control reduces interference with other calls and
extends the battery life of MSs, which is important in hand portables.
2-24 68P02901W01-S
Jul 2008
System Information: GSM Overview Discontinuous transmission
Discontinuous transmission
The speech transcoder is equipped with a Voice Activity Detector (VAD) that detects the
presence of speech data. Transmission is stopped in the intervals when speech is absent. This is
called Discontinuous Transmission (DTx) of speech. The system operator controls this feature
and enables it in either or both directions.
The potential for interference is reduced since transmitters are only energized when
needed. This has the side-effect of improving the system spectrum efficiency.
The algorithm used to calculate the DTx maximizes the amount of off-time, while avoiding
speech clipping or distortion. The VAD encodes the silences in the speech pattern at a rate
of 500 bps rather than the full 13 kbps. The encoding produces background noise called
comfort noise, which reduces noise contrast effects. The continuous transmission of signaling
information is unaffected by DTx.
Discontinuous reception
Once the MS is in synchronization with the BTS (it uses the FCCH and SCH channels to get into
synchronization), it monitors two control channels: the Broadcast Control CHannel (BCCH) and
the Paging Channel (PCH). If the MS is not in use, it can determine when control information is
next due, and switch off between signals. This is called Discontinuous Reception (DRx). The
potential for 2% power cycling in standby extends battery life in MSs.
Timing adjustment
The TDMA bursts transmitted by MSs over the same radio channel must be kept apart for proper
recovery of received data at the BTS site. The MSs are not stationary, therefore propagation
delay of MS transmissions can vary. Sometimes the delay becomes significantly long and a burst
overlaps into the next timeslot. This causes undesirable errors in the recovered data.
Timing correction is provided to maintain the guard time needed between bursts. A closed loop
mechanism provides timing correction for the MS. The BSS detects changes in timing through a
timing advance algorithm. If necessary, the BSS sends timing advance messages to the MS,
commanding it to transmit earlier or later, as required, to offset the modified propagation delay.
In addition, the timing advance algorithm provides an estimation of the distance between
the MS and the BTS site. This distance estimation can be a valuable parameter in handover
decision algorithms.
68P02901W01-S 2-25
Jul 2008
Frequency synchronization Chapter 2: BSS General Description
Frequency synchronization
All BSS frequencies and timing signals are synchronized to a high stability reference oscillator
in the BSS. This oscillator can free run or be synchronized to the recovered clock signal from a
selected E1 serial link. Either case provides better than 0.05 ppm stability. MSs lock to a
reference contained in a synchronization burst transmitted from the BTS site. This reference
has a stability of 0.1 ppm.
Equipping one cabinet with reference clock circuits and distributing the synchronized reference
signals to other cabinets saves cost considerably in sites with collocated cabinets. This
distribution is through fiber optic cables.
A full description of this feature is provided in Intelligent Multi Layer Resource Management
(IMRM) on page 4-100.
2-26 68P02901W01-S
Jul 2008
System Information: GSM Overview Cell system radio channel reuse
Because the C/I level is relatively small, RF frequencies used in a cell can be reused in other
cells that are relatively small distance apart. Thus, the frequency reuse patterns are smaller,
which permits more frequency reuse within a geographic area.
GSM digital cellular systems typically use a 9-site omni or 4-site/3-sector pattern. A 2-site
(sectored) pattern, which requires a unique Motorola design, is also available.
Figure 2-5 shows how GSM cellular systems using a 9-site reuse pattern, are configured with
sites providing omnidirectional RF coverage areas. These sites provide about a 15 dB C/I
for 90% location reliability.
68P02901W01-S 2-27
Jul 2008
3-site 3-sector reuse pattern Chapter 2: BSS General Description
In this arrangement, the allocated frequencies are divided into 9 reuse groups.
Figure 2-6 shows a GSM cellular system using a 3-site (3-sectored), 120 degree sector
arrangement. This system provides about a 12 dB C/I for 90% location reliability.
2-28 68P02901W01-S
Jul 2008
System Information: GSM Overview 4-site reuse pattern
Systems using sites with three 120 RF coverage sectors provide about a 13.6 dB C/I for 90%
location reliability. This arrangement requires dividing the allocated frequencies into nine
reuse groups.
Systems using sites with six 60 RF coverage sectors provide about a 13.5 dB C/I for 90%
location reliability. This arrangement requires dividing the allocated frequencies into 18 reuse
groups.
The Motorola unique 2-site reuse pattern is a 4-site repeat pattern that reuses each frequency
group twice. Therefore, this plan is an effective 2-site repeat pattern. Each site is sectored
into six 60 RF coverage areas. The capacity of this pattern is 40% greater than the generic
3-site reuse pattern using cells sectored into three 120 RF coverage areas, and provides an
equivalent C/I performance.
In this arrangement, the allocated frequencies are divided into 12 reuse groups.
68P02901W01-S 2-29
Jul 2008
Cell pattern reuse comparisons Chapter 2: BSS General Description
2-30 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS redundancy
BSS redundancy
Redundancy can optionally be added to prevent single faults from producing a capacity loss.
Redundancy means adding more modules than necessary to support a given capacity. These
additional modules are in standby mode until the system requires them to replace a failed
module. Fault management of the redundant modules minimizes the number of additional
modules the system requires to provide full redundancy. This design is achieved by using
N+1 redundancy wherever possible.
When failures occur, the BSS software fault diagnostics can usually isolate the failure down to a
replaceable module. Fault Management (FM) classifies failures as type A or B.
Type A failures cause an alarm at the Operation and Maintenance Center (OMC) and/or
local terminal (TTY), and result in the faulty module being taken Out Of Service (OOS).
Type B failures cause an alarm at the OMC and/or TTY, but the module is not taken OOS.
Failed modules
68P02901W01-S 2-31
Jul 2008
RF carrier redundancy Chapter 2: BSS General Description
RF carrier redundancy
All RF carrier equipment can provide both signaling and traffic channels. Redundancy can be
provided by equipping the cell/sector with more carrier equipment than traffic requirements
dictate:
If additional radio channel frequencies for the cell/sector are available, the redundant
carrier can provide additional capacity until a carrier or associated equipment fails.
If additional radio channel frequencies for the cell/sector are not available, the redundant
carrier is only switched into service in response to a failure.
Interface redundancy
Each site connects to the BSC or MSC through E1 serial links as digital carriers. Therefore,
each site requires at least one line interface module (A interface or Abis interface). Each line
interface module provides an interface for two E1 serial links.
To provide redundancy at the interface, an additional E1 serial link and an additional interface
module are added.
BTS redundancy
To provide BTS redundancy, one set of RF carrier modules and associated digital modules for
each cell or sector RF coverage area within one or more BTS cabinets at a site are required.
BSC redundancy
To provide BSC redundancy, duplicate digital modules within the same BTS/BSSC cabinet are
required.
N+1 redundancy is available for the processing and power supply modules.
RXCDR redundancy
To provide RXCDR redundancy, duplicate digital modules within the same shelf of the same
BSSC cabinet are required.
N+1 redundancy is available for the processing and power supply modules.
2-32 68P02901W01-S
Jul 2008
System Information: GSM Overview General packet radio service
General Packet Radio Service and Enhanced GPRS (E)GPRS are a packet radio system that
allows mobile subscriber (MS) units to access data services (such as World Wide Web (WWW) or
email). Access to WWW or email is through a modified GSM air interface protocol. The modified
air interface protocol allows multiple MS units to share a single timeslot, and also allows
different mobiles to utilize the uplink and downlink timeslots. This enables a more cost-effective
use of network resources for data transfer.
A cell can have all GPRS and EGPRS carriers, or a combination of the two.
The GSN complex module (SGSN, GGSN, GSN CommHub, and ISS).
A interface
BSC MSC HLR
Gr
BSS-PCU Gs
interface Gc
Mobis
Gd
Um
Gp
SMC-GMSC
SMC-IWMSC
MS GGSN
Other PLMN
ti-GSM-EGPRS network-00049-ai-sw
68P02901W01-S 2-33
Jul 2008
Packet control unit Chapter 2: BSS General Description
GPRS introduced a new device at the BSS, known as the Packet Control Unit (PCU). The PCU is
an interface adaptor handler unit that permits the Motorola GSM facility access to the packet
network. As such, the PCU needs interfaces with the BSC on the GSM side, and the SGSN on
the packet network side. The PCU manages the packet radio interface and also enables the
interface from the BSS to the SGSN. The existing OMC-R manages the PCU.
See General packet radio service on page 2-33 section for full details.
GSN complex
Network elements
GPRS introduced the following new network elements, as shown in Figure 2-8:
The Serving GPRS Support Node (SGSN)
The SGSN keeps track of the individual MS locations, and performs security functions and
access control. The SGSN is connected to the BSS through a Frame Relay network.
The GGSN provides inter working with external packet-switched networks and is connected
with SGSNs through an IP-based (E)GPRS backbone network. This backbone network includes
the CommHub and ISS (IP Support Server) nodes.
The Shelf Manager at the OMC-G allows an operator to monitor the hardware in a shelf. The
Shelf Manager is displayed in the Navigator under its parent Complex and at the same level as
SGSN, GGSN, and so on.
NOTE
A shelf is an entity housing 16 cPCI slots plus cooling fans and power supply units.
Four of the slots are taken up by system cards. Twelve slots are available for SGSNs.
Each SGSN is a two-card unit in release 1.6.1.3, one for the Control Function (CF)
and the other for the Transmission Function (TF) function.
2-34 68P02901W01-S
Jul 2008
System Information: GSM Overview GSN complex
GSN complex
NOTE
The GSN complex is not described in this manual. For further information on the
GSN complex, see the Motorola GSN Service Manual.
68P02901W01-S 2-35
Jul 2008
GSM/(E)GPRS network architecture Chapter 2: BSS General Description
The new GPRS equipment consists of a PCU attached to the BSC, as part of the BSS. The SGSN,
GGSN, GSN CommHub, and ISS are included as part of the GSN complex equipment.
Each BSC has a dedicated PCU, and multiple BSSs can be attached to one GSN complex.
Several GSN complexes can be networked together to serve one PLMN. One OMC-G can
manage several GSN complexes.
Figure 2-8 (E)GPRS network architecture showing the PCU and GSN complex
GSM EQUIPMENT GSN EQUIPMENT
RXCDR OMC-G
(Including Shelf
Manager)
OMC-R
BSSn GSN
BTSs COMMHUB
BSS2 GSNn
BSS1 GSN1
2-36 68P02901W01-S
Jul 2008
System Information: GSM Overview Overview of VersaTRAU
Overview of VersaTRAU
The VersaTRAU feature provides dynamic TRAU capability to EGPRS Carriers to optimize
backhaul usage and reduce costs to the customer. Without VersaTRAU, a GSM TDMA timeslot
(containing voice or GPRS data) is framed and sent on a 64 kbps backhaul timeslot between the
BSC and a remotely located BTS site. With VersaTRAU, both voice and GPRS/EGPRS frames
are combined into one large frame, which reduces backhaul wasted due to extra padding.
Additionally, when congestion occurs on the backhaul, GPRS/EGPRS data and control blocks are
scheduled accordingly at the PCU to fit the available backhaul. The combined VersaTRAU frame
can still be sent on a reduced backhaul link.
UL_EGPRS_BACKHAUL_DEMAND
DL_ EGPRS_BACKHAUL_USED
DL_ EGPRS_BACKHAUL_DEMAND
EGPRS_64K_CHANNEL_WIDTH
Using the above statistics, the OMC provides a new utility. The utility presents the user an
analysis on the VersaTrau performance over a period of time specified by the user. The
summarized report details the total statistics interval data considered for analysis:
Maximum and mean bytes lost over all the statistics intervals.
Number of intervals where the demand was less than or equal to 80% backhaul.
Number of intervals where the demand was greater than 80% and less than or equal
to 100% backhaul.
Number of intervals where the demand was greater than 100% backhaul.
The VersaTRAU feature updates two existing alarms: CERM and GDS OOS.
This feature introduces a new RTF element namely rtf_ds0_count. This element specifies the
number of RTF backhaul timeslots allocated for a 64K carrier.
The VersaTRAU feature extends the existing debug functionality in the PCU:
TSN TRAU/PTRAU log - An operator can capture and display all uplink and downlink
VersaTRAU frames on a VersaTRAU channel.
PRM Carrier log - An operator can capture and display all the uplink and downlink PTRAU
frames on a VersaTRAU channel. In addition, it is possible to:
Issue disp_rtf_channel on a 64K RTF to display the current VersaTRAU configuration.
68P02901W01-S 2-37
Jul 2008
Overview of VersaTRAU Chapter 2: BSS General Description
Use PRM per-carrier internal stats to monitor the uplink omission information.
Use the five new per-carrier stats to monitor the backhaul usage and demand on
a 64K carrier.
Use the extra information carried in UL/DL Sync frames to debug any problems
related to the Time Alignment procedure for each VT subchannel. See PCU-CCU
IDS[4] for the UL/DL Sync frame on a 64K carrier.
The VersaTRAU feature eliminates the static mapping between a PDCH and backhaul resources.
All the PDCHs on a 64K carrier share a group of DS0s defined by a VersaTRAU channel.
Figure 2-9 shows PDTCHs to Backhaul Mapping on a 64K carrier.
The new TRAU frame formats on 64K carriers. In VersaTRAU, the backhaul available for a 64K
PDCH in the uplink direction for a block period depends on all the following factors:
The number of DS0s is currently allocated for the VersaTRAU channel.
The user data (CS1-4, MCS1-9) or signaling (CS1 or PRACH) traffic is scheduled on each
PDCH on the carrier for a block period.
The backhaul available for a PDCH on a 64K carrier may not be enough to carry the user data
or signaling received on the PDCH for a block period. In this case, the CCU omits the uplink
RLC/MAC radio block and send the omission frame to the PCU.
2-38 68P02901W01-S
Jul 2008
System Information: GSM Overview Packet control unit
The following text provides a general description of the Motorola Packet Control Unit (PCU),
which links between the GPRS Support Node (GSN) and the Motorola BSS.
The GSM recommendations define the functions of the GPRS, but allow flexibility in its design.
The following text describes some of the unique features of the Motorola PCU.
PCU information
The following sections contain the following information about the PCU:
PCU overview on page 2-40.
68P02901W01-S 2-39
Jul 2008
PCU overview Chapter 2: BSS General Description
PCU overview
PCU summary
Taking small uplink packets from the E1 links connected to the BSS that are carrying
user data from the MS units. The PCU then forms larger uplink packets to be sent over
the E1 links to the SGSN.
Packet segmentation and packetization on the frame relay link to the SGSN network entity.
Taking downlink packets from the SGSN and segmenting these packets into small packets
to be sent to the MS units.
NOTE
{27955A} The BSC supports one PCU cage when the software is upgraded to GSR9.
For EGPRS, each PCU requires one or two E1 Interface panels depending on the configuration.
For high capacity PCUs requiring more than 600 Air TS and 24 E1s, it is necessary to add a
second T43 patch panel to the PCU.
All connectivity (GDS) between BSC and PCU is through Ethernet. The Ethernet ports can
support either 100 Mbps or 1000 Mbps operation.
2-40 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU environment
PCU environment
Figure 2-10 shows the PCU positioned within the GSM/(E)GPRS network.
HLR
PDN TE
MAP-G Gr
Gs Gn Gi
Gb Gn
PCU
BSC GGSN
Um
Abis OTHER
MS BTS PLMN
SIGNALLING
SIGNALLING AND DATA TRANSFER
68P02901W01-S 2-41
Jul 2008
PCU features Chapter 2: BSS General Description
PCU features
Support of MS classes
Gb interface
MS flow control
(E)GPRS provides a new set of bearer services supporting packet mode transmission. This
supporting low-speed and high-speed signaling, a data transmission technique with improved
efficiency compared with circuit based techniques.
(E)GPRS enables the subscriber to send and receive data in an end-to-end packet transfer mode,
without utilizing circuit switched network resources. General characteristics where (E)GPRS
offers superior performance compared with circuit technology include applications where:
The transmission of small volumes of data is frequent.
The time between successive transmissions greatly exceeds the average transfer delay.
2-42 68P02901W01-S
Jul 2008
System Information: GSM Overview (E)GPRS radio channel allocation
The network operator can size the network optimally for efficient support of a mix of (E)GPRS
and voice traffic. To support this mix, each timeslot on a GPRS carrier can be configured as
dedicated to circuit traffic, or (E)GPRS traffic. The timeslot can also switch between the two
types of traffic In the case of switchable timeslots, (E)GPRS traffic has precedence over circuit
switched traffic on the last remaining timeslot.
The (E)GPRS network supports cell reselection modes as shown in Table 2-6.
The reselection modes allow the network to provide the Mobile Station (MS) with information
regarding the quality and signal strength of the link. The MS then uses this information to
determine whether to perform a cell reselection based upon signal strength of neighbor cells.
(E)GPRS carriers can also be configured to support the GSM discontinuous transmission feature,
defined for circuit switched traffic in an effort to conserve MS battery life. In network operation
mode 2, the network uses the CCCH paging channel for both CS and GPRS paging.
Table 2-6 Cell reselection modes
Dynamic allocation of radio resources allows an operator to configure the radio resources of a
cell as dedicated circuit switched, dedicated (E)GPRS, or switchable between circuits switched
and (E)GPRS. This enables efficient use of air interface resources, and allows an operator to
tailor the cellular network to the packet data traffic requirements of the operator.
This feature provides the flexibility for a cell supporting (E)GPRS to allocate a given radio
resource to handle circuit switched voice/data or packet data, as required. A radio resource
can be configured as dedicated to circuit switched traffic, packet data traffic, or switchable
between the two. In the latter case, the traffic demands of the network determine the type
of traffic handled by the air interface timeslot. This provides the operator with a degree of
flexibility when configuring a (E)GPRS capable network, and also facilitates maximum utilization
of resources. In a (E)GPRS capable cell approaching congestion, (E)GPRS traffic can be given
preference over the last switchable radio resource, by setting a database parameter.
Originally the Motorola GPRS product offered the capability to configure up to eight GPRS
timeslots on a single carrier in a cell. The network operator can now configure multiple (E)GPRS
carriers per cell for increased (E)GPRS traffic handling capability to meet the increase in packet
data traffic and the expanding base of (E)GPRS subscribers with increased data throughput.
68P02901W01-S 2-43
Jul 2008
Medium access control mode - dynamic allocation Chapter 2: BSS General Description
Medium Access Control (MAC) includes the functions related to the management of the common
transmission resources. These include the packet data physical channels and the radio link
connections on packet data physical channels.
MAC supports the assignment of radio resources to MSs for transmission of (E)GPRS protocol
data units (PDUs). In all cases, the network determines the assignment and transmits this
information for a given radio resource to all MSs sharing that resource.
The MAC also supports the provision of Temporary Block Flows (TBFs) allowing the
point-to-point transfer of signaling and user data between the network and the MS. A temporary
block flow is a physical connection used by the two entities to support the transfer of (E)GPRS
protocol data units (PDUs) on packet data channels (PDCH). A TBF is temporary and is
maintained only for the duration of the data transfer.
MAC operates in dynamic allocation mode. In this mode, three Uplink State Flag (USF) bits
are transmitted in every downlink block. Through these USF bits, the network instructs one of
the MSs sharing a timeslot to transmit data on the uplink. MSs monitor the channel for their
instruction to transmit. The advantage offered by dynamic allocation mode is flexibility in
the assignment of the air interface resource.
{23292}
The optional EDMAC feature supports class 11 and 12 mobiles with 3 and 4 UL timeslots
capability. When 3 or 4 uplink timeslot allocation is assigned, EDMAC is required for the
request uplink TBF. When a class 11 or 12 mobile requests an uplink TBF, the network assigns
the EDMAC for the uplink TBF if the mobile supports EDMAC and the TBF allocation requires
EDMAC mode. The network assigns the lowest numbered timeslot in the allocation as PACCH
timeslot.
Support of MS classes
The (E)GPRS network currently provides some form of support for all 29 multi-slot class MSs,
supporting multiple timeslot allocations in the UL and DL directions. An MS that supports
multiple UL timeslot allocation is always allocated a maximum of two UL timeslots, for multi-slot
classes mapped to (E)GPRS classes 5, 6, 9, or 10. All other mapped classes only allow allocation
of one UL timeslot. Table 2-7 shows the mobile multi-slot class mapping for all the (E)GPRS
multi-slot classes.
2-44 68P02901W01-S
Jul 2008
System Information: GSM Overview Coding schemes
Table 2-7 MS multi-slot class mapping for all (E)GPRS multi-slot classes
06, 07 06
08 08
09, 13 09
10 - 12, 14 - 29 10
GSM voice MSs are semi-duplex. The direction of speech information transfer alternates
rapidly, about 210 times per second, between the uplink and the downlink directions. This rapid
switching emulates a full duplex speech connection.
The basic GPRS MSs are semi-duplex as well. These MSs spend a significant proportion of time
switching directions, which significantly limits their total throughput. For example, the most
capable semi-duplex MS can receive four timeslots while transmitting one timeslot, or receive
three timeslots while transmitting two timeslots.
Coding schemes
Four separate coding schemes, CS-1 to CS-1 are supported for GPRS and nine coding schemes,
MCS1 to MCS9, are supported for EGPRS. These schemes are described in the text that follows.
Four separate coding schemes, CS-1 to CS-1 are supported for GPRS; these schemes provide
differing throughput rates, as shown in Table 2-8.
Effective approximate
Coding scheme Throughput/TimeSlot (kbps)
convolutional coding rate
CS-1 9.05 1/2
CS-2 13.4 2/3
CS-3* 15.6 3/4
CS-4* 21.4 1
* switchable option only
All the coding schemes, except CS-4, provide a degree of forward error correction, depending
upon the prevailing RF conditions. Through the support of these four coding schemes, a
higher throughput is enabled for MSs operating in those areas of the network with excellent
68P02901W01-S 2-45
Jul 2008
Coding schemes Chapter 2: BSS General Description
RF coverage, based upon reduced requirement for error correction. In those areas of the
network where RF coverage suffers, error correction can be boosted, thereby maintaining a
quality transmission, at a reduced throughput.
In the BSS architecture, the link which the (E)GPRS data traverses from the channel coders in
the BTS to the PCU is currently implemented using 16 kbps TRAU-like links. These links are
carried over sub-rate switched E1 timeslots which have some signaling included to ensure that
the link is synchronized between the channel coders and the PCU.
As additional protection and identification bits are included in the transmitted frame, there
is not enough bandwidth available on a 16 kbps link to carry CS-3 and CS-4. Thus a new
mechanism for associating two 16 kbps TRAU channels together, giving a 32 kbps TRAU, must
be implemented to provide the bandwidth necessary to implement CS-3 and CS-4.
Nine coding schemes, MCS1 to MCS9, are supported for EGPRS; these schemes provide
differing throughput rates, as shown in Table 2-9.
The BSS supports all EGPRS coding schemes (MCS1 to MCS9) for EGPRS TBFs on a 64 kbps
terrestrial channel. EGPRS coding schemes are only used to transmit data blocks.
When an MS is performing bidirectional packet transfer, the PCU allows independent coding
scheme selections for each direction. If the mobile does not support 8PSK modulation, the BSS
limits the uplink coding scheme usage to EGPRS-GMSK MCS1 to MCS9 for an EGPRS mode TBF.
For uplink data transfers, the BSS selects one of the EGPRS coding schemes on a per mobile
basis according to measurement information.
For downlink data transfers, the BSS selects one of the EGPRS coding schemes on a per mobile
basis. The selection is according to measurement information, unless interleaving with GPRS
requires GMSK only (CS1 to CS4 or MCS1 to MCS4) blocks to be sent.
The BSS transmits all EGPRS RLC/MAC control blocks using CS1 and uses MCS1 for all LLC
dummy blocks during delayed downlink TBF release mode.
2-46 68P02901W01-S
Jul 2008
System Information: GSM Overview Dynamic adaptation of coding schemes
This feature enables the network to change the coding scheme between MS transmissions
based upon the radio characteristics of the link.
During a (E)GPRS transmission, the network monitors the characteristics of the radio link.
Based upon these measured characteristics, the network is able to change the coding scheme in
use to maximize throughput of the link. As an example, an MS with a fairly high-quality radio
connection can maximize throughput, with no error correction, using CS-4. If the quality of
the link deteriorates, the number of retransmissions required would begin to increase due to
the lack of forward error correction. In this case, there would eventually be a point at which
the throughput enabled by CS-3 would exceed that of CS-4. It is based upon the fact that the
added error correction would reduce the number of retransmissions. Similarly, if the link quality
deteriorates still further, CS-2 would become the better option.
GPRS supports two-phase packet access. This feature allows an exchange of information to take
place between the MS and the network before the assignment of resources.
The purpose of the packet access procedure is to establish an uplink transmission to support
the transfer of packet data units from the MS to the network. The packet access procedure
can take place in either one or two phases. Two-phase packet access avoids contention. In
this procedure, the MS requests a packet resource on the random access burst. The network
provides an immediate assignment of a single block. The MS responds to the single block with
its radio access capability (classmark) and MS ID, and the number of octets of user data. Based
upon this information, the network assigns a resource for the uplink transmission.
GPRS one phase uplink TBF access is an improvement over the two-phase uplink TBF access
procedure.
In a GPRS one phase uplink TBF access, the MS initiates an uplink TBF by sending a Random
Access Channel (RACH) to the BSS. The RACH is received at the BTS, which is then forwarded
to the PCU. The PCU responds to the RACH with an Immediate Assignment message containing
an uplink assignment. The MS moves to the assigned Packet Data (Traffic) Channel (PDTCH)
and begins its uplink data transfer. This procedure allows the MS to gain access to the network
much quicker when comparing against the two-phase establishment procedure.
The enhanced GPRS one phase uplink TBF access procedure speeds up the one phase packet
access procedure even further.
The enhanced GPRS one phase access procedure improves PCU assignment of resources for a
one phase uplink TBF. The procedure involves enabling the BTS to react more quickly to a one
phase RACH without forwarding the RACH to the PCU. This obviates RSL delay and increasing
RSL load. Depending on the RSL load, the RACH to Immediate Assignment delay reduces
by approximately 60 ms or more.
68P02901W01-S 2-47
Jul 2008
Frequency hopping of PDCH Chapter 2: BSS General Description
If the TS pre-allocated by the PCU is in the USF active state, the timeslot broadcasts a valid
USF continuously. Once the MS moves to the pre-allocated timeslot (after the MS receives
the Immediate Assignment message), the MS receives the assigned USF immediately. This
is the earliest possible opportunity for the MS to transmit in the uplink. The only delay
between the Immediate Assignment message and the uplink data transmission is the
MS reaction time.
Refer to Technical Description: BSS Implementation (68P02901W36) for a full description of the
differences between the two access methods.
The (E)GPRS network support frequency hopping of the packet data channel (PDCH).
Frequency hopping is one of the Motorola key techniques to improve capacity and quality in
a highly loaded GSM network. These same benefits are realized when frequency hopping is
implemented on (E)GPRS carriers. For (E)GPRS, all packet data channels assigned to a single
MS are included in the same frequency hopping system, which specifies the frequencies over
which the timeslots hop and the hopping sequence.
The principle of frequency hopping is as simple as changing the frequency used in transmission
at regular intervals. It has been included in GSM specifications mainly in order to deal with
two specific problems which can affect transmission quality:
Multipath fading
Interference
Interference coming from neighbor cells transmitting the same or adjacent frequencies can
be reduced by using frequency hopping. This is because calls are moving through different
frequencies that are not equally affected by interfering signals.
If the master cabinet is a Horizon II cabinet, the only restriction is that EGPRS and non-EGPRS
RTFs cannot base band hop (BBH) together. They can BBH independently, EGPRS carriers
must be in their own BBH system.
If the master cabinet is not a Horizon II cabinet, only single density DRIs can BBH.
The power control feature enables power adjustment over the radio link based upon the
characteristics of the link.
Power control is supported over the radio interface on both the uplink and downlink. The
network directs power adjustments based upon the measured characteristics of the radio link.
2-48 68P02901W01-S
Jul 2008
System Information: GSM Overview Gb interface
Gb interface
The PCU interface/Gb interface provides connection between the BSS and the SGSN.
The Gb interface connects the BSS/PCU to the SGSN, allowing the exchange of signaling
information and user data. The Gb interface allows many users to share the same physical
resource. To facilitate cost-effective transmission, the Motorola (E)GPRS offering also supports
infrastructure sharing, which allows the operator to carry A interface (CS) and Gb interface
(packet) traffic on a single E1 using the nailed connections capability. These two features
enable a cost-effective transmission solution in a (E)GPRS capable network. As (E)GPRS
traffic increases, it is appropriate to dedicate one or more E1 link lines to (E)GPRS traffic. To
accommodate this scenario, the network also supports a direct connection between the PCU
and the SGSN.
The Gb interface link layer is based on frame relay. Frame relay virtual circuits are established
between the SGSN and BSS, where PDUs from many users are multiplexed on these virtual
circuits. The virtual circuits are multi-hop, and traverse a network of frame relay switching
nodes. Frame relay is used for both signaling and data transmission.
This feature provides high reliability through efficient resource management. It also manages
the movement of resources from one part of a BSS to another to meet varying peak capacity
requirements in a network designed primarily for coverage.
The primary objective of this feature is to support the use of multiple timeslots per cell
economically, with no delay penalty, in a BSS configured for coverage rather than capacity. A
coverage based (E)GPRS network provides coverage over a large number of cells, and assumes
a low average throughput per cell. This feature allows a network to move or enable resources
effectively as needed throughout a BSS, to handle traffic peaks. If there is a PCU failure (with
multiple PCUs), cells move from one PCU to another.
Another objective of this feature is to provide high reliability. During periods when the
designated resource is not required due to a failure, the spare resource can be used to manage
peak loads. This is accomplished with load sharing of E1 link lines and other key components
within the BSS. A BSS/PCU can be configured to support a maximum capacity of 270*3 (810)
active timeslots.
If the link line or equipment fails, the BSS provides load sharing of the following resources:
E1 link lines on the BTS-BSC link.
MS flow control
MS flow control is implemented to regulate the flow of data from the SGSN to the MS by
sending a message containing the MSs logical identifier (TLLI), the current maximum buffer
depth (MS_Bmax) and the current buffer leak rate (MS_R). The flow of data is then controlled
on a per MS basis.
68P02901W01-S 2-49
Jul 2008
MS flow control Chapter 2: BSS General Description
The BSS attempts a preset maximum number of times to send the message, in case the SGSN
does not acknowledge it within the maximum time allowed. Successive messages are sent a
pre-defined delay (C) apart, unless the messages are unacknowledged.
2-50 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU description
PCU description
PCU purpose
The new BSS functionality for (E)GPRS mainly resides at the Packet Control Unit (PCU). The
functions of the PCU include the following:
Handling of frame relay.
BSSGP signaling.
Radio Link Control (RLC) and Medium Access Control (MAC) preload.
User data is routed to the PCU through the Channel Codec Unit (CCU) uplink from the BTS to
the BSC. Then over E1 to the PCU. At the PCU, the RLC blocks are reformulated in Logical Link
Control (LLC) frames and forwarded to the SGSN.
BSSGP signaling and NS signaling occur between the PCU and the SGSN using frame relay
protocol. There is also signaling between existing functional processes at the BSC such as the
signaling between the Base Station control Processor (BSP) at the BSC and the PCU through the
E1 interface, as well as between the PCU and channel coders.
The purpose of the PCU is to perform a variety of functions and is responsible for the following
(E)GPRS MAC and RLC layer functions:
LLC layer PDU segmentation into RLC blocks for downlink transmission.
LLC layer PDU reassembly from RLC blocks for uplink transmissions.
PDCH scheduling functions for the uplink and downlink data transfers.
PDCH downlink ARQ function, including buffering and retransmission of RLC blocks.
Radio channel measurement functions, including received quality level, received signal
level, and information related to timing advance measurements.
68P02901W01-S 2-51
Jul 2008
PCU management Chapter 2: BSS General Description
The BSS is responsible for allocation and de-allocation of radio resources. A PCU frame can
be transferred between the PCU and the CCU every 20 ms.
PCU management
The PCU is managed, including software download and operations, by the OMC-R as an
extension to the BSS. The OMC information destined for the PCU is passed through the BSC.
The Common Management Information Protocol (CMIP) interface is modified on the BSC to
include the management of the PCU as a new device.
OML GSL
OMC-R BSC PCU
X.25 64 kbps
E1
2-52 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU devices and equipage
Figure 2-12 Device and equipment hierarchy for the PCU device
NOTE:
.
..
68P02901W01-S 2-53
Jul 2008
PCU architecture Chapter 2: BSS General Description
PCU architecture
The PCU hardware is off-the-shelf equipment that is based upon the compact PCI (cPCI)
standards. The cPCI is a set of standards that define a common chassis, power supplies, and
processor boards.
{28351}A new board, U-DPROC2, replaces the DPROC board. The U-DPROC2 board is
configured with PXP function. PXP combines the functionality of PICP and PRP.
MPROC
The MPROC is the system slot processor that is responsible for bus arbitration and CPCI clock
generation. It contains interface and BSSGP protocol functions, and is called the PCU System
Processor (PSP). Two PSPs are automatically equipped for each PCU; one acts as the primary
and the second acts as the redundant, and so, MPROCs are redundant.
The MPROC is the main control processor for the system, and works in conjunction with
the PPB. It acts as PCI system host, and in conjunction with the PPB supports hot removal
control for all board slots. It performs resource allocation, fault management, and gateway
management functions (such as control of allocation of cells to PRP boards). These functions
comprise the PSP, which resides on the MPROC.
The MPROC requires a high-performance processor system such as the 266 MHz MPC750 with
an 83 MHz bus for the memory subsystem. A minimum of 128 M bytes of DRAM is supported,
upgradeable to 256 MBs.
2-54 68P02901W01-S
Jul 2008
System Information: GSM Overview Bridge (PPB)
Bridge (PPB)
The bridge, also referred to as the PCI to PCI Bridge (PPB), allows the MPROC to be linked to a
separate bus. The PPB and MPROC are paired boards.
The PPB allows the redundant operation of the system host MPROC board, and gives the host
MPROC access to all boards in the system. It supports control of hot swap for all boards
and a communication link between bridge boards. This allows migration to a fully hot swap,
redundant, high-availability system, including hot standby/load sharing between MPROC boards
in the future, if necessary.
DPROC
The DPROC boards are non-system slot boards that have two PMC sockets and can host two
different functions. The DPROC can be configured as either a PICP or a PRP.
If configured as the PICP, the DPROC contains up to two PMC modules to provide the E1
interfaces. The E1 interface can support the LAPD GDS interface (GSL) and the Gb interface;
TRAU GDS devices are no longer supported.
If configured as a PRP, the DPROC performs air interface scheduling and the PMC sockets can
be used to support TRAU GDS devices. A single processor can support a pool of 120 radio
timeslots, of which 30 radio timeslots can be active at any one time.
DPROC (PICP)
The DPROC (PICP) is used for all network interfacing functions to the outside world, such
as the SGSN and BSC. The PICP has up to two interface modules installed and data to/from
these interfaces passes through the onboard processor. This processor has different functions
dependent on the interface type. It includes features such as packet routing on an incoming
SGSN link, and packet scheduling to an outgoing SGSN link.
DPROC (PRP)
The DPROC (PRP) is the processor where all of the radio-related processing takes place. Each of
the (E)GPRS channels is routed to a PRP. The PRP performs all of the RLC/MAC processing, air
interface scheduling, and frame synchronization on BTS facing channels.
The performance required from this board is such that it supports a minimum of 30 active air
interface timeslots, with the ability to monitor another 90 timeslots. A future tripling of this
capacity is envisaged. The PRP maintains synchronization to the air interface by the exchange
of the PCU-CCU frames (which is transmitted even on inactive timeslots).
U-DPROC2
{28351} A new hardware named Universal DPROC2 (U-DPROC2) replaces the legacy DPROC to
increase GPRS capacity in GSR9. The U-DPROC2 board is configured with PXP function. PXP
combines the functionality of PICP and PRP. The U-DPROC2 increases the GPRS capacity on the
current PCU and BSC hardware platform. The U-DPROC2 board can support Ethernet link and
hence, the process capability of TS for the board is improved highly.
68P02901W01-S 2-55
Jul 2008
U-DPROC2 Chapter 2: BSS General Description
A U-DPROC2 serving as PXP supports a 1000BASE-T or CAT 5e link from the PCU to the BSC
completing connection to the new PSI board.
With the introduction of new U-DPROC2, there are three PCU configurations. DD1 (Deployment
Diagram 1) is a legacy configuration utilizing DPROCs and/or U-DPROC2s configured as
PICPs and PRPs. In DD2, the PCU is configured with all U-DPROC2 boards configured as
PXP. All boards are connected with PSI board in BSC through Ethernet link. DD3 is a mixed
configuration mode in which the PCU has PRP/PICP and PXP in its cage.
2-56 68P02901W01-S
Jul 2008
System Information: GSM Overview U-DPROC2
68P02901W01-S 2-57
Jul 2008
E1 PMC module Chapter 2: BSS General Description
U-DPROC2 PXP supports IPv4 and UDP protocols for Ethernet connection to PSI board at the
BSC. Therefore, both TRAU data and GSL signaling are transported over IP/UDP protocol
between U-DPROC2 and PSI when U-DPROC2 serves as a PXP.
E1 PMC module
A single PMC module residing on the U-DPROC2 provides the E1 interfaces to both the BSS
and the SGSN. The PMC board has a 8560 800 MHz PowerQUICC III processor and 512 MB
DDR266 ECC RAM.
This onboard processor is used for frame relay termination on the Gb link and contains a
small process to route the Gb interface signaling (control) information to the Gb manager on
the MPROC. E1 links are also used to interface the PCU to the BSC for transfer of signaling
information through LAPD protocol, as well as serial user data in the remaining timeslots.
The clock on the PMC module is free run and not synchronized to an external signal from E1
interface. The memory on the PMC module is used for the code object storage of the frame
relay protocol as well as the buffers which are necessary for both the transmit and receive
sides of the frame relay link.
The E1 interface can support the Gb interface or the TRAU (E)GPRS Data Stream (GDS)
interface, and LAPD GDS including the (E)GPRS signaling link. The GSL is a 64 kbps TCL and is
used to manage and control the PCU/BSC system. Multiple GSLs can be used to manage and
control the PCU/BSC system. Figure 2-18 shows a system where E1 PMCs are used to connect
the TDM data to the BSC. The MSIs used for these links can be equipped in any chassis of a
multi-chassis BSC system.
(TRAU) GDS
Gb interface
Chassis
The chassis houses a maximum of 16 cPCI boards, with the ability to support redundant
host processors. The power supply system is part of this OEM solution. The host processor,
redundant host processor, and their associated bridge boards occupy four of the slots, leaving
12 generic slots for the remaining boards. Hot removal of all boards is supported.
The PCU is an additional chassis that is collocated with any BSC that supports (E)GPRS
functionality and interfaces to the BSC, utilizing E1 PMC modules on a DPROC (PICP) board.
This requires corresponding Multiple Serial Interface boards (MSIs) to be present in the BSC.
The chassis is a 19-inch rack-mounting module supporting sixteen 6U PCI slots, four of these
slots are taken by the two MPROC/bridge pairs for redundant systems. Any combination of PICP,
and PRP boards with their associated PMC modules take up the remaining 12 generic slots.
It supports front access for all replaceable modules, redundant/load sharing PSU system, and
status LEDs. The interconnect cabling is routable from the rear, front, or bottom of the chassis.
2-58 68P02901W01-S
Jul 2008
System Information: GSM Overview Fault tolerance
Fault tolerance
The PCU supports load sharing across the PRP, PICP, and E1 PMC. The hardware can be N +
M redundant (and would generally be equipped as N + 1 when load sharing is active), but
software loads share across all installed boards, with any failures causing a loss in total capacity
capability. The operator determines whether the hardware is provisioned for greater capacity
than required, such that failures do not affect the system capabilities.
68P02901W01-S 2-59
Jul 2008
PCU interfaces Chapter 2: BSS General Description
PCU interfaces
RXCDR SGSN
A Gb
X.25
OMC-R BSC PCU
Abis
BTS
Um
KEY:
MS optional
ABSCONDER (X.25)
BSC-RXCDR (A)
BSC-PCU
PCU-SGSN (Gb)
2-60 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU interfaces
This section defines the interfaces the PCU has with other elements of the (E)GPRS.
PCU interfaces
PCU-BSC interface
The PCU-BSC interface carries user data and radio resource management information, called
Radio Link Control/Medium Access Control (RLC/MAC) packets, between the PCU and BTS. The
(E)GPRS Signaling Links (GSL) carry signaling information on 64 kbps E1 timeslots between the
PCU and BSC.
GDS connections carrying traffic and signaling are supported by E1 and Ethernet. ETH is an
Ethernet port on the PSI card at the BSC or on the PXP DPROC card at the PCU used for
GDS functionality.
An RSL carries the signaling information on 16 kbps or 64 kbps E1 timeslots between the
BSC and BTS.
Another 16 kbps E1 TS or channel carries the TRAU-like framed data between the BSC and BTS.
A BCCH or CCCH carries the signaling information between the BTS and MS.
Between the BTS and MS, the packet data is carried over CS1, CS2, CS3, or CS4 encoded
PDCHs (see Figure 2-17).
Figure 2-17 Data and signaling paths between the PCU and MS
68P02901W01-S 2-61
Jul 2008
PCU interfaces Chapter 2: BSS General Description
E1 LINKS
BSC
E1PMC
DPROC
DPROC
(PICP)
(PICP)
MSI
MSI
E1PMC
The number of MSI links
needed is dependent on the
PCU capacity . All MSIs can
reside in a single BSC
chassis even in expanded PCU
systems.
E1 LINKS
2-62 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU interfaces
Gb interface
The Gb traffic, user data, and signaling, can take different paths between the PCU and SGSN
depending upon the needs of the voice and data networks. In all cases, the Gb traffic is always
carried over 64 kbps E1 channels. See Figure 2-19 for a summary of the three connection
methods. Option C, routing a connection through the transcoder, is a convenient way to bring
(E)GPRS traffic from multiple PCUs to a single SGSN.
Figure 2-19 Data and signaling paths between the PCU and SGSN
ALL INTERFACES ARE Gb n x 64 kbps E1 CHANNELS LAPF
BSC BSC
RXCDR
68P02901W01-S 2-63
Jul 2008
PCU system and control functions Chapter 2: BSS General Description
BSC
SGSN
Radio functions
The PCU is responsible for the following (E)GPRS MAC and RLC layer functions, as defined
in GSM 03.64:
LLC layer PDU segmentation into RLC blocks for downlink transmission.
LLC layer PDU reassembly from RLC blocks for uplink transmissions.
PDCH scheduling functions for the uplink and downlink data transfers.
PDCH downlink ARQ function, including buffering and retransmissions of RLC blocks.
Interacting with existing BSS software for allocation/de-allocation of radio resources for
(E)GPRS.
SGSN functions
The PCU and the SGSN use frame relay and the Base Station System (E)GPRS Protocol (BSSGP)
protocols to exchange user data and signaling information. The frame relay network can be
point-to-point or an actual network. Signaling data, used for flow control and congestion
management, is exchanged between the PCU and SGSN.
2-64 68P02901W01-S
Jul 2008
System Information: GSM Overview PCU processes
PCU processes
Gb processes
GWM processes
PRP processes
The DownLink Segmentator (DLS) segments LLC frames into RLC data blocks to be
transmitted over the air interface.
The UpLink Concatenator (ULC) concatenates RLC data blocks into LLC frames.
The SYstem information Manager (SYM) builds and sends (E)GPRS system information
messages over the BCCH.
CCCH Paging Manager (CPGM) processes the paging messages coming from the SGSN
to the BSC or BTS.
Gb processes
The Flow control Buffer Manager (FBM) controls buffer capacity for each cell and each
mobile and so, that the incoming data from the SGSN matches the air throughput.
The Gb Manager (GBM) manages the state of all cell and signaling links between the
PCU and the SGSN.
The Gb Transmit Manager GTM) collects all UL frames from various ULCs and sends
them on the appropriate NS-VC.
The Network Service Tester (NST) periodically tests all alive Network Service-Virtual
Circuit (NS-VC) on a PICP board.
The Frame Relay (FR) performs the frame relay protocol functions.
68P02901W01-S 2-65
Jul 2008
PCU processes Chapter 2: BSS General Description
GWM processes
The PCU Fault Collection Process (pFCP) resides on every DPROC and MPROC and collects
all software faults (SWFMs) and sends them to pFTP.
The PCU Central Authority (pCA) initializes devices, brings them in or out of service, tests
the devices, and performs fault recovery of the PCU (through out of service/in-service
request from pFTP).
The PCU System Audit Process (pSAP) periodically audits devices to maintain the reliability
of the system.
The PCU Configuration Management (pCM) distributes all database changes performed at
the BSC to the PCU boards.
The Cell Balancer (CB) handles the load balancing of cells across all PRPs.
2-66 68P02901W01-S
Jul 2008
Chapter
OMC-R Overview
This chapter provides an overview of the OMC-R hardware configurations for the SunFire 4900,
SunFire 4800, Netra 20 and Netra 440 based high-end and low-end systems. The OMC-R
hardware and software components for each system are identified.
Operation and Maintenance information flow between OMC-R and NEs on page 3-34.
68P02901W01-S 3-1
Jul 2008
PCU processes Chapter 3: OMC-R Overview
3-2 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R network management functions
Fault management
Fault management provides the facility to change the status of any device using fault handling
procedures. From the OMC-R, the GSM network operator can react to changes in the network.
The operator reconfigures the site by taking devices in or out of service as required, thus
maintaining continuity of service to mobile phone users. Fault management tasks can be
performed from the map, the alarm window, the Navigation Tree and through the contained
devices.
Event/alarm management
A primary function of an OMC-R is to maintain the quality of service to customers or users of the
GSM network by monitoring the state of Motorola equipment in the network. Event or alarm
messages containing information on the state of the network, devices, and links in the system
are sent through the X.25 network to the OMC-R. These messages notify the operators of any
potential problems occurring in the network. There is the optional alarm notification through
Paging feature, which automatically notifies key personnel of certain alarm or state changes.
Operators can filter and select the way in which alarms are displayed and handled. For example,
alarms, which have been handled, but not yet cleared, can be deferred. With the optional
Network Health Analyst (NHA), operators can move from being purely reactive to a more
proactive role by observing a combination of events, statistical information, and configuration
data that notifies them of network problems before any faults are raised.
Performance management
68P02901W01-S 3-3
Jul 2008
Configuration management Chapter 3: OMC-R Overview
Configuration management
The OMC-R provides the configuration management facilities for a scalable system that can
cater for an expanding GSM network. The system processor can be configured for a variety
of expandable traffic channel capacities on the same basic platform. The OMC-R system
allows customers to expand their network Operation and Maintenance support according to
their business growth. The system provides orderly migration for existing users and rapid
deployment for new users. Network Expansion and Cell Parameter Import/Export under the
control of the OMC-R enables rapid and widescale network expansion. The OMC-R also includes
the Call Trace function.
Configuration management also provides centralized software load management, database load
management, and the management of operating parameters. The OMC-R provides facilities
to initiate uploads and downloads of NE operating software, or to back up or download
configuration databases for the different NEs. The OMC-R also provides the facilities to
reconfigure the operating parameters of NEs using the remote login facility and facilities to
optimize through the GUI.
Network configuration from the OMC-R also includes the optional Packet Control Unit (PCU)
interface to the (E)GPRS system. The interface incorporates the packet switching logical
connections and devices.
Load management
Load management forms part of the Configuration Management. It provides the operator with a
central location to load all the NEs remotely with the latest compatible version of operating
software. New software loads are installed at the OMC-R and later downloaded to the NEs
under the control of the OMC-R.
3-4 68P02901W01-S
Jul 2008
System Information: GSM Overview The OMC-R in GSM network management architecture
Network hierarchy
The position of the OMC-R within the GSM network management hierarchy, is shown in
Figure 3-1.
PHYSICAL IMPLEMENTATION
SER VICES OF THE LOWER THREE LAYERS
MANAGEMENT
NETWORK
NMC
MANAGEMENT
NETWORK
ELEMENT OMC-R OMC-R
MANAGEMENT
NETWORK ELEMENT
LEVEL NE NE NE NE NE NE
Network levels
Operation and Maintenance management of the BSS and RXCDR can be performed at several
network levels:
Local level
Local level monitoring, where reconfiguration, and software loading can be performed by
connecting a personal computer to the BSC or RXCDR (Remote Transcoder).
68P02901W01-S 3-5
Jul 2008
Network levels Chapter 3: OMC-R Overview
Regional level
The OMC-R provides facilities for performing functions on NEs at a regional level. Built in
alarm and event management, configuration management, and fault handling facilities enable
operators at remote OMC-R sites to manage Operation and Maintenance in a consistent and
standardized manner. The OMC-R provides monitoring and control for a number of BSSs in
a specific geographical area. The prime function of the OMC-R is maintaining the quality
of service to customers or users by monitoring the performance of the radio equipment.
Procedures are provided which can dynamically reconfigure the radio resources, and rectify
faults from a single remote location. Additionally, the OMC-R provides databases for Operation
and Maintenance data and system performance statistics.
Top level
The Network Management Center (NMC) implements the top level of the network management.
The NMC could perform Operation and Maintenance functions at a network-wide level with
OMC-Rs as its subordinates.
3-6 68P02901W01-S
Jul 2008
System Information: GSM Overview The OMC-R system
The OMC-R platform can be expanded in a cost-effective manner as the cellular network grows.
Based on the SUN computer product line, the OMC-R supports networks of different sizes:
Low-end
High-end
The hardware configuration of the system processor varies depending on whether a Low-end
or High-end OMC-R is chosen. For example, the number of CPU processors, memory, disk
capacity determines the configuration.
The RTF (Receive Transmit Function) and the number of Network elements (NEs) determine the
choice of Low-end or High-end OMC-R platform, the OMC-R is required to manage.
Several GUI client processors which provide operator workstations (for example, Sunblade
150).
Each processor is a complete UNIX system. An Ethernet Local Area Network (LAN) enables
interaction between all processors.
The OMC-R interfaces with the cellular network using of X.25 Packet Switched protocol.
68P02901W01-S 3-7
Jul 2008
OMC-R system configuration Chapter 3: OMC-R Overview
OMC-R specifications
The SunFire 4900, SunFire 4800, Netra 20 or Netra 440 is a UNIX system that acts as the
OMC-R system processor, running the OMC-R application software. The OMC-R handles all
Operation and Maintenance communication with the Network Elements (NEs). A Packet
Switch or Multiplexer and the system processor HSI/S or HSI/P hardware enable the OMC-R to
interface to the GSM Network. The OMC-R system processor processes all incoming events,
alarms, uploads, downloads, performance statistics, and the setting up of remote login sessions
to different NEs.
The OMC-R system processor contains two databases constructed on a Relational Database
Management System model (RDBMS), Informix. One database (PM) is configured for storing
performance statistics and subscription lists; the other (CM) is configured for network and map
configuration data. The PM and CM enable operators to monitor incoming events and alarms
using map displays.
The OMC-R system processor uses the Solaris 10 Operating System (OS) as the UNIX platform.
3-8 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R system configuration
In addition to the OMC-R system processor, Graphical User Interface (GUI) servers and clients
based on SUN ULTRASparc processors, can be used as operator workstations managing and
monitoring NEs.
A comparison between Low-end and High-end OMC-R specifications is shown in Table 3-1.
GUI sessions
Operator workstations
The OMC-R system comprises of a Single Platform system processor and a number of operator
workstations. Each operators workstation is a complete UNIX system and runs the OMC-R
Graphical User Interface (GUI).
GUI client:
Sunblade 150.
Refer to the Software Release Notes: OMC-R System (68P02901W74) for configuration details.
68P02901W01-S 3-9
Jul 2008
OMC-R system configuration Chapter 3: OMC-R Overview
Optional processors
Datagen
Software requirements
The software requirements for the OMC-R are contained on two GSR9 DVDs:
OMCR.1900xy.JS.ALL.ALL.DVD.0.00 and OMCR.1900xy.SW.ALL.ALL.DVD.0.00.
Continued
3-10 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R system configuration
Mozilla 1.7
Python 2.2.3
Sun VTS 6.2
Solstice Backup Server 7.3 Yes
Solstice Backup Client 7.3
68P02901W01-S 3-11
Jul 2008
The OMC-R user interfaces Chapter 3: OMC-R Overview
User interfaces
The OMC-R has two user interfaces to operate the OMC-R system:
The Graphical User Interface (GUI)
The OMC-R GUI provides a Graphical User Interface (GUI), based on the Open Software
Foundation Motif (OSF-Motif).
GUI interface
The GUI presents the user with a front panel displaying icons that represent all the modules of
the OMC-R, shown in Figure 3-3. A smaller expert front panel, which does not have icon titles,
is also available for experienced personnel. The expert front panel prevents desktop clutter
and is shown in Figure 3-4.
The OMC-R GUI enables operators to interact with the OMC-R and to carry out network
management functions. All maintenance, network reconfiguration, troubleshooting, and
network administration, apart from equipment repair and replacement can be executed through
a single interface.
The UNIX-based system utilities are executed at the command line of an Xterm window, which is
opened from the GUI front panel.
The GUI front panel contains icons that represent different modules of the OMC-R GUI. A
summary of the current alarms in the network is always displayed on the right-hand side of the
GUI front panel. Figure 3-3 shows the OMC-R front panel and Figure 3-4 shows the expert
OMC-R GUI front panel.
3-12 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R front panel
1 2 3 4 5 6 7 8
16 15 14 13 12 11 10 9
Table 3-3 describes the icons on the OMC-R GUI front panel (see Figure 3-3).
Table 3-3 Front panel icon description
Number Description
1 Operator (user name)
2 Access to OMC-R console
3 Access to configuration management
Continued
68P02901W01-S 3-13
Jul 2008
OMC-R front panel Chapter 3: OMC-R Overview
3-14 68P02901W01-S
Jul 2008
System Information: GSM Overview The command line interface
UNIX-based utilities
UNIX-based utilities are provided to give additional network management functionality to the
OMC-R GUI in the following functional areas:
Remote login
Event management
Performance management
NE database management
68P02901W01-S 3-15
Jul 2008
The OMC-R in a GSM network Chapter 3: OMC-R Overview
A typical GSM network (900 MHz, 1800 MHz, or 900/1800 MHz), is shown in Figure 3-5. It
consists of an Operation and Maintenance Center Radio (OMC-R) and one or more Network
Elements (NE or nodes). The nodes are a Base Station System (BSS), a Remote Transcoder
(RXCDR), Mobile Switching Center (MSC) or Cell Broadcast Center (CBC) and so on.
3-16 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R functions
OMC-R functions
Management of the NE devices associated with the links (on the RXCDR side) between
the MSC, the BSSs, and RXCDRs. It is done using the Operation and Maintenance data
packets sent to or from the NE.
Provides a centralized facility for the network management of up to 120 NEs with up to
90,000 traffic channels for the scalable OMC-R.
Handling faults.
Reconfiguring NEs.
RXCDR functions
The RXCDR routes the Operation and Maintenance data packets between the BSS and the
OMC-R, and traffic channels (voice) between the BSS and MSC. The Operation and Maintenance
data packets are routed between the OMC-R and the RXCDR using X.25 packet switching.
Each 2 Mbps link between the BSSs and the RXCDR typically consists of two 64 kbps Operation
and Maintenance links plus 120 ((30 kbps x 64 kbps) x (64 kbps)) traffic channels.
The primary feature of the RXCDR is that it converts the 64 kbps PCM output of the MSC to a
16 kbps rate required for transmission over the air interface (between the BSS and the MS).
The location of RXCDR between the MSC and the BSS, usually in the same area as the MSC
is the most efficient arrangement. Thus, four 16 kbps channels from the RXCDR can be fitted
on each 64 kbps terrestrial circuit. Thus, each 30 channel 2 Mbps PCM link can carry 120
GSM-specified channels with obvious cost savings.
Configurations
A BSS consists of a Base Site Controller (BSC) and one or more remote Base Transceiver
Stations (BTS). Every BTS must be physically connected to its controlling BSC using a 2 Mbps
link. A BTS can also be located in a BSC cabinet, thus creating a collocated BSC or BTS,
usually connected using a LAN. A BSS configuration can have all BTSs directly connected to
the controlling BSC (spoke connection) or the BSS is connected through another BTS (daisy
chaining). A BTS can also have more than one connection to its controlling BSC for redundancy.
The GPROC2 (second-generation processor) and GPROC3 (third-generation processor) boards
allow the BSC to support 100 sites.
68P02901W01-S 3-17
Jul 2008
BSS and RXCDR configuration (SITES) Chapter 3: OMC-R Overview
BSS configuration
In a GSM network, the BSS is configured to contain a series of one or more SITES. SITE 0
always contains the BSC equipment; it can also contain BTS equipment. Sites 1 to 100 contain
only BTS equipment, they cannot contain the BSC.
Remote BTS site - This site forms the remote part of a BSS controlled by the BSC site. The
BSC provides the interface with the MSC.
Example
RXCDR configuration
3-18 68P02901W01-S
Jul 2008
System Information: GSM Overview NE device containment
NE device containment
Containment relationship
There is a containment relationship between each entity in the GSM Network that is modeled
at the OMC-R. This hierarchical structure is known as the Containment Tree. Each entity is
contained within a container, which can consist of more than one entity known as containees.
For example, the MMS (the Multiple Serial interface link) is contained within the MSI (the
Multiple Serial Interface board), which is contained within a SITE. This containment relationship
is used for logical naming, configuration, and event management.
For more details on containment relationships, refer to manual Installation and Configuration:
GSM System Configuration (69P02901W17).
Ports
There are two MMS ports on the MSI board. There can be up to 96 MSI boards in a SITE and up
to 100 SITEs in a BSS. An instance of the MMS can be uniquely identified to the MSI/XCDR
as follows:
Example
MMS port 1 on MSI board 2 in SITE 0 would be named MMS 2 1 X. The first digit is the parent
MSI card, the second refers to the port number and the third is not required.
68P02901W01-S 3-19
Jul 2008
Site configuration Chapter 3: OMC-R Overview
Site configuration
CELL resources
In the Motorola implementation of GSM, a single BTS consists of one or more cabinets and
controls one or more CELLs. The Motorola term CELL is equivalent to the GSM term BTS, since
the Motorola BTS sites can contain more than one cell. GSM requirements specify one cell
per BTS.
The different related resources of a CELL configuration are shown in Figure 3-7.
One or more carriers service each CELL, and a single radio unit services each carrier. Each
carrier has eight TDMA timeslots.
3-20 68P02901W01-S
Jul 2008
System Information: GSM Overview BTS software relating to traffic
From a software perspective, a BTS contains the following software devices or functions:
Digital Radio Interface (DRI) Groups, which contains DRIs.
There is one DRI Group per cell on each site for redundancy purposes.
There is one RTF Group per cell on each site for redundancy purposes.
CELLs.
68P02901W01-S 3-21
Jul 2008
DRI/RTF groups - transceiving Chapter 3: OMC-R Overview
Transceiving functionality
Motorola has implemented transceiving functionality using the DRIs and RTFs. This
functionality provides the radio carrier, which, in a GSM digital system, consists of eight TDMA
timeslots. These digital channels carry speech and various control data. One of the more
important of these control channels is the Broadcast Control CHannel (BCCH). Every CELL
must have at least one BCCH.
Types of RTF
RTFs are used to carry the traffic part of the call (speech or data). They are defined as functions
rather than devices as they are a logical representation of the traffic, rather than relating to
a physical piece of hardware. The RTF contains eight digital channels, one for each timeslot
on the air interface.
Non-BCCH
To provide redundancy of RTF traffic, it is possible to specify two routes or PATHs. The routes
are potentially able to carry the RTF traffic from the BTS to the BSC. These PATHs are called the
Primary and Secondary PATHs. If two PATHs are available, then the shorter is the connected
PATH and the longer is the redundant PATH. If the PATH availability changes and a shorter
PATH becomes available to the RTF, then a switchover occurs. Then the RTF starts to use this
new PATH. Refer to Physical links - PATH on page 3-26 for more details of PATHS.
Each RTF function, equipped to a remote SITE, uses two PCM (that is, 2 x 64 kbps, where 64
= 4 x 16 kbps) timeslots per PATH device.
Each OMC-R is limited to support a particular number of RTFs, called the RTF Limit. The
Motorola engineers set the RTF Limit during staging. Each OMC-R has a threshold RTF value,
which is 90% of the RTF Limit.
The DRI Group and RTF Group are used to support transceiving redundancy for CELLs.
Typically, for n RTFs, there is n+1 DRI devices equipped. When the RTF is equipped, it attaches
itself to an available In Service (INS) DRI. If the DRI goes Out Of Service (OOS), the RTF
attaches itself to another available DRI to maintain transceiving functionality to the CELL.
3-22 68P02901W01-S
Jul 2008
System Information: GSM Overview CELL configuration
CELL configuration
Logical devices
Handover control
Power control
Handover control
Handover means switching a call from a channel in a given CELL, to another channel in to
another channel in the same or another CELL. This handover is done keeping disturbance to a
minimum, ideally in a way not noticeable by the users.
The BSS allows adaptive power budget handovers (if enabled) on a per cell or neighbor
basis. The adaptive handover methodology allows handovers to be recognized based on a
cumulative area rather than a vote. At each measurement report, the cumulative area is
updated and compared to a cumulative trigger. If the power budget (pbgt) dips below the
handover margin temporarily, the cumulative area is decremented by the difference and not
reset. If this cumulative area is then greater than the cumulative pbgt trigger, a need for a
handover is recognized. The cumulative area is based on either a per cell or a per neighbor
basis as decided by the operator.
Handover control is the functionality required to detect and effect a handover, to maintain
acceptable service to the user.
There are a number of parameters used to detect when a handover occurs. A number of factors
are input to this algorithm. These factors are as follows:
Uplink and downlink receive signal strength.
Power budget.
When a power budget handover is enabled, the call is handedover to a neighboring cell.
The handover is at the point where a lower power budget can be achieved (both the MS
and the BTS can reduce their TX power).
68P02901W01-S 3-23
Jul 2008
Power control Chapter 3: OMC-R Overview
Interference.
NOTE
Uplink is from the Mobile Station (MS) to the BTS, downlink is from the BTS to
the MS.
There are thresholds supported for each measurement and when a threshold is exceeded,
a handover occurs.
Power control
In order to reduce radio frequency interference in the network, and increase battery life on
MSs, it is desirable to run all the BTSs and MSs in the network at the minimum TX power. This
provides adequate rxqual (quality) and rxlev (level) for a call.
Power control is the functionality to detect and effect the modification of transmission power,
both for the MS and BTS, to maintain an acceptable service to the user.
A dynamic power reduction algorithm can be used in conjunction with the standard power
control algorithm. In the event that the power level exceeds the upper level threshold, the
algorithm allows the decrement step size to change dynamically based on the proximity to the
upper power threshold. The algorithm is used to reduce the power level to one under the
threshold level. The calculations are made for both uplink and downlink power control.
There are a number of parameters, which are used to detect when power control occurs.
There are thresholds supported for each measurement. When a threshold is exceeded,
transmission power modification can occur.
3-24 68P02901W01-S
Jul 2008
System Information: GSM Overview Links in a GSM network: overview
Information on links
A link to a BSS, is a link to the SITE configured as a BSC within the BSS.
Similarly, links within a BSS, links between the BSC and BTSs and that between one BTS
and another, are all links between SITEs.
Every SITE must contain at least one Multiple Serial Interface (MSI) board (NIU for Horizon),
which is a communication controller containing two 2 Mbps (MMS) ports.
Link types
Logical links
68P02901W01-S 3-25
Jul 2008
Physical links - PATH Chapter 3: OMC-R Overview
Connection
A physical link between two SITEs is made by connecting the MMS port of the MSI (NIU for
Horizon) card on one SITE, to that on another SITE.
Similarly, every BSC must be physically connected to its controlling MSC. A BSC is directly
connected to its controlling MSC or it is connected through the RXCDR.
Every BTS must be physically connected to its controlling BSC. A BTS is directly connected
to its controlling BSC or it is connected through another BTS (daisy chaining). A BTS can
have more than one signaling and traffic connection to its controlling BSC giving load
sharing and redundancy.
PATH devices
A PATH device defines the connectivity between a BSC site and BTS sites under its control.
It is a logical representation of a 2 Mbps route between the BSC and a destination BTS.
This connectivity specifies the physical route from the BSC, through intermediary BTSs to
the destination BTS. A PATH can contain a route through a maximum of 10 BTS sites. The
connection information between any two sites consists of the MSI (NIU for Horizon)/MMS
device at each end of the link.
3-26 68P02901W01-S
Jul 2008
System Information: GSM Overview PATH devices
Figure 3-8 shows two PATHs connecting BSC 0 with BTS 3, a PATH through BTS 1 and BTS 2,
(A-B-C), and one direct connection between BSC 0 and BTS 3 (D).
BSC 0
A BTS 1
D
B BTS 2
C BTS 3
PATH 1 = A-B-C
PATH 2 = D
ti-GS M-BS S pa th s e ttings e xa mple -00067-a i-s w
68P02901W01-S 3-27
Jul 2008
Logical links Chapter 3: OMC-R Overview
Logical links
Introduction to links
The 2 Mbps physical links in the GSM network, are configured to carry (as well as the voice
traffic channels) many logical links. The links contain signaling information or Operation and
Maintenance data. The OMC-R monitors these links.
Types of link
The types of logical links are shown in Figure 3-9. These links generate events, alarms, and
performance statistics, at the BSC (or RXCDR) site where they are equipped, and are reported
to the OMC-R.
The purpose of the OML is to provide communication between an OMC-R and a BSC, or RXCDR
for transferring network management (Operation and Maintenance) data. Up to four OML links
can be configured between an OMC-R and BSC, or RXCDR. One OML is used at any given time.
The other three OMLs exist for redundancy purposes.
The purpose of the MTL is to provide a link for signaling information between the BSC and the
MSC. In the Motorola system, when local transcoding is used, MTL is a physical connection
between the BSC and the MSC. When a Remote Transcoder is used, the logical MTL is made
up of two physical parts. One connection is between the BSC and the RXCDR and the other is
between the RXCDR and the MSC.
When more than one MTL is configured between the BSC and MSC, both load sharing and
redundancy are present. Up to 16 MTLs can be configured between a BSC and MSC.
A signaling link between a BSC and a remote BTS is called a Radio System Link (RSL). The
purpose of an RSL is to provide signaling information between a BSC and a remote BTS. The
timeslots used, are chosen automatically by the Motorola software, thus ensuring that new
BTSs, added to the network, can be communicated with on default timeslots.
Each RSL link is associated with a PATH. It is possible to have multiple (up to eight) RSLs
between a BSC and a remote BTS. For example, in Figure 3-9, there are two RSLs between
BTS2 and the BSC. It is possible because of the daisy chain connection in the BSS. The two RSLs
provide both load sharing and redundancy functions for the signaling link.
3-28 68P02901W01-S
Jul 2008
System Information: GSM Overview Requirements
An XBL link is configured between the BSC and the RXCDR for exchanging internal Fault
Management (FM) data between them. An Enhanced XBL (EXBL) will allow generic messaging
between the RXCDR and the BSC in support of current and future operator needs.
A CBL link can be configured between the BSC or RXCDR and the Cell Broadcast Center (CBC).
This link is used for downloading messages to broadcast along with other necessary information
such as repetition rate and number of broadcasts.
Requirements
Figure 3-9 shows the different logical links in a GSM network. Logical link requirements:
A BSC always contains at least one OML (with a maximum of four), one MTL or XBL/EXBL
(depending on how it is connected to the MSC) and at least one RSL for each remote
BTS under its control.
An RXCDR always contains at least one OML, and at least one XBL/EXBL.
68P02901W01-S 3-29
Jul 2008
Requirements Chapter 3: OMC-R Overview
L O -BS I
)
2 M bps lin
k
CB C
2 M bp slink
RS L11
)
BTS 1
)
BTS 2
3-30 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R connection to the network
Transferring data
For every BSC in the network, one or two timeslots (64 kbps) on a 2 Mbps link is used to carry
the Operation and Maintenance data between the BSC and the RXCDR. All the timeslots from
the different BSC-RXCDR links are grouped onto one or more 2 Mbps links by the RXCDR or the
MSC. The RXCDR transfers the information to a packet switch/multiplexer.
The X.21 links are connected to the OMC-R through a public or private X.25 network/switch.
Figure 3-10 illustrates the method of transferring the Operation and Maintenance data between
the BSS and OMC-R network elements (NEs). Other NEs can also communicate with the
network.
The physical connection between the OMC-R processor and the packet switch/multiplexer
consists of two to seven X.21 connections. Each physical connection can support up to 256
virtual circuits. There are four types of virtual circuits that can be made on the OML:
Event Interface (EI) transfers data packets (events and alarms), plus the OMC-BSS
message from a NE (for example, a BSS) to the OMC-R. The circuit is made by the NE
calling the OMC-R.
Boot Load (BL), also called Download, transfers the BSS software and the BSS databases
to the NE. The NE calling the OMC-R makes the circuit.
Upload (UL) transfers the BSS database backups and raw statistics (performance data) to
the OMC-R. The OMC-R calling a NE makes the circuit.
Remote login (RL) provides sessions for transfer of BSS GUI commands or responses to a
NE. The OMC-R calling the NE makes the circuit.
The virtual circuits EI and BL can be accepted on any of the X.21 connections on the OMC-R.
Normally two connections are set up for EI and BL. If a given port is not working, then
the packet switch/multiplexer switches to a different port. The UL circuit consists of four
processes and each is assigned to a single OMC-R connection. The RL is assigned to a single
OMC-R connection.
Figure 3-10 shows the communication between the OMC-R and other network elements.
68P02901W01-S 3-31
Jul 2008
X.21 connection configuration Chapter 3: OMC-R Overview
Figure 3-10 Communication between the OMC-R and other network elements
PROCESSOR
O and M
(two to seven
2 Mbps link
NAILED CONNECTIONS
(ONE PER O and M TIMESLOT)
64 kbps O and M
TIMESLOT
3-32 68P02901W01-S
Jul 2008
System Information: GSM Overview Operation and Maintenance of a BSS or RXCDR
Simplified network
A simplified network showing some of the hardware devices in the different sites, and the links
between them, is shown in Figure 3-11. BSS1 from Figure 3-10 is used as the example BSS.
Figure 3-11 Simplified GSM network showing devices and links at BSSs
68P02901W01-S 3-33
Jul 2008
Operation and Maintenance information flow between OMC-R and NEs Chapter 3: OMC-R Overview
A summary of the information flow between the OMC-R and other NEs (for example, RXCDR
and BSS) is shown in Figure 3-12. The primary function of the OMC-R is to monitor the health
of the radio network.
NE NE NE NE NE
Information flow
Events such as changes of state of a hardware device, link, or function and alarms which could
be service affecting are sent to the OMC-R, through the RXCDR and the X.25 packet switch. In
the OMC-R, they are processed into a standard format. The alarms can be configured to update
a network map, which gives the operator a visual warning by causing the appropriate BTS or
BSC to flash. The alarms or events can also be displayed on the operator terminals. They
are displayed within different windows, depending on how the network operator (or OMC-R
administrator) has configured them.
The RXCDR contains several of the same devices, links and functions as the BSS, and generates
events and alarms in the same way.
3-34 68P02901W01-S
Jul 2008
System Information: GSM Overview Information flow
Regardless of the number of BTSs, the BSS is regarded as a single NE, and runs only one
software load, for example, BSSGSM 1.6.0.x. When loading a BSS, the entire load is first sent to
the BSC, which then distributes the appropriate load objects to the configured BTSs. A copy of
the active BSS load is stored at the OMC-R as it is a copy of the previous version of the BSS
software. These software loads must be compatible with the load installed on the OMC-R. The
RXCDR receives the same software load as a BSS, it just implements a different part of it.
Each BSS and RXCDR contains an operational database. The database has the configuration
data for all the devices and links in the SITES within the NE is stored. A backup copy of the
active database is kept at the OMC-R.
Performance measurements for the different BSS and RXCDR are periodically routed every 30
minutes or 60 minutes to the OMC-R as raw statistics in a data file. This data is stored in a
database at the OMC-R, and processed into statistics which provide valuable information for
efficient network management and planning.
68P02901W01-S 3-35
Jul 2008
OMC-R system configuration Chapter 3: OMC-R Overview
Motorola OMC-R
An OMC-R comprises a central system processor and several GUI processors. Each processor is
a complete UNIX system, which provides a GUI interface presented on a color monitor. The
system is connected through a LAN allowing all workstations access to a laser printer. The
GUI server is a server that allows the GUI processors to run on a fast machine while using
the slower machine for the display process.
NOTE
Some systems are configured differently; for specific information the OMC-R Bill
Of Materials (BOM) must be consulted.
3-36 68P02901W01-S
Jul 2008
System Information: GSM Overview Communications handling
Communications handling
Communications software
The OMC-R communications software provides control and support for the protocol stacks
which interface the OMC-R with the following:
Internal OMC-R communications:
TCP/IP
Ethernet
X.11
The X.25 software is loaded in the system processor, and the X.11 driver software is loaded in the
GUI Processors. The remaining communication software is shared between the two processors.
The operating processes are linked between machines by the Interprocess Communication
(IPC). The OMC-R network can be extended to include further GUI Processors, or secondary GUI
servers, connected either locally or through a Wide Area Network (WAN). Bridges and gateways
can also be used to connect to other computer systems such as an NMC, or other OMC-Rs.
68P02901W01-S 3-37
Jul 2008
Packet switch or multiplexer Chapter 3: OMC-R Overview
Connections
The OMC-R is connected to the GSM Network, to receive the Operation and Maintenance data
using a packet switch/multiplexer (as shown in Figure 3-14). The Packet Switch makes available
a maximum of 256 x X.25 virtual circuits for the exchange of Operation and Maintenance data
between the OMC-R and the NEs.
OMC-R
System processor system
processor
Packet switch
The connection between the system processor and the Packet Switch could be direct or
connected through a Private eXchange Public Data Network (PXPDN).
3-38 68P02901W01-S
Jul 2008
System Information: GSM Overview Operation and Maintenance network traffic capacity
The system processor supports the following Operation and Maintenance peak network traffic
capacities:
100 x X.25 packets per second, with a packet length of 128 bytes, aggregate.
The system processor can be configured to handle up to 90,000 traffic channels. The traffic
channels are associated with a maximum of 120 NEs through the 256 x X.25 virtual circuits.
68P02901W01-S 3-39
Jul 2008
OMC-R system processor Chapter 3: OMC-R Overview
The hardware configuration of the system processor (for example, the number of CPU
processors, memory and disk capacity) can be varied depending on whether the low-capacity,
mid-capacity, or high-capacity TCH OMC-R is chosen. Thus, the scalable OMC-R provides easy
and cost effective expansion or reduction from low-capacity TCH through mid-capacity TCH
to high-capacity TCH configuration. The software requirements are the same for all capacity
Scalable OMC-R configurations.
System processor
System specifications
The system processor software is installed on internal and external disks depending on the
system processor in use. All system and data areas are mirrored for redundancy.
14
14
The Scalable OMC-R uses Sunlink X.25 application software and connects to the network using
a HSI/S card. This allows the Scalable high-end OMC-R to be used where there is existing
packet switching and multiplexing equipment available, or to be connected to a public packet
switched network.
3-40 68P02901W01-S
Jul 2008
System Information: GSM Overview Feature description
Existing system processor OMC-R application software has been ported to work on the Solaris
10 OS.
Feature description
Table 3-4 gives a comparison between the four Scalable OMC-R configurations.
The high-end Scalable OMC-R does not affect the OMC-R-BSS (rlogin) and the SMASE-NMASE
interface.
68P02901W01-S 3-41
Jul 2008
Configuration Chapter 3: OMC-R Overview
Configuration
The configuration of the system processor is shown in Figure 3-16. It uses a Solaris 10 UNIX
operating system and contains a DataBase Management System (DBMS) from Informix (which is
configured for storing the performance statistics). The Event Management Information Base
(EM MIB) containing the incoming events and alarms, updates the map displays. The map
displays present the operator with visual indication of alarms in the network. The System
processor also contains the CM MIB, which holds the configuration data required to run the
network maps.
10
3-42 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R GSM application software: overview
OMC-R processes
The functional software areas of the OMC-R are split between the OMC-R system processor
and the GUI processor. The processes of the OMC-R application software installed on the
OMC-R system processor are shown in Figure 3-17. The operator is provided with a front
end to all these processes at the OMC-R GUI. The command line utilities provide additional
front-end functionality.
Performance SW Load
Management Management
Configuration Event/Alarm
Management Management
Device Remote
Management Event Login
Interface
The software elements constituting the system processor software perform the following
functions:
Performs network element Operation and Maintenance management tasks.
Provides the interface to the network elements through the X.25 network.
The OMC-R system processor software elements are as follows:
Configuration management
Configuration management allows the operator to perform the network configuration tasks, and
to maintain all details of the network configuration at the OMC-R.
68P02901W01-S 3-43
Jul 2008
System processor software elements Chapter 3: OMC-R Overview
Performance management
Load management provides a facility for uploading and downloading the NE software loads, and
NE operational databases. It also provides a means of managing multiple copies of software
loads for back up purposes.
Event/alarm management
Remote login
The remote login software manages the X.25 connection for remote login to network elements
from the OMC-R. Remote login is a means by which the operator performs configuration
management, fault management, and some performance management procedures at the
network elements.
Event interface
The event interface handles the X.25 alarm connections to the network elements, then translates
and forwards incoming events and alarms to the event/alarm management functional software.
Device management
Device management allows the operator to perform fault management and configuration
management at the OMC-R. The OMC-R supports most hardware devices and software functions
located at the remote network elements.
3-44 68P02901W01-S
Jul 2008
System Information: GSM Overview UNIX: Solaris 10 operating system
Platform
The system processor operates under the Solaris 10 operating system. It provides the platform
for the OMC-R software applications and provides facilities for system administration.
Advantages
The main advantages of this operating system are that it is designed to provide:
An enhanced multi-architecture solution for systems to support Internet or Intranet
connectivity.
Features
Included with this release is the Common Desktop Environment (CDE). It provides users with
a flexible open user environment that has a common look and feel across all major UNIX
desktops. This environment allows transparent access to the network resources; and allows
frequently used UNIX commands to be iconised. It is also possible to drag and drop between
files and commands.
The Solaris 10 operating system includes the following tools and applications:
The Solstice backup software allows a Solaris operating system server to provide
automated, high performance backup, recovery and storage management services to
machines on the network.
Solstice backup provides simple centralized administration, through a single unified view
of the entire data management operation from any point on the network. Intuitive user
interfaces simplify administrative tasks such as configuring clients and servers, and setting
up backup schedules for file systems and databases.
68P02901W01-S 3-45
Jul 2008
Tools and applications Chapter 3: OMC-R Overview
Solstice AdminSuite
The Solaris operating system allows the OMC-R to be administered as a typical UNIX system.
3-46 68P02901W01-S
Jul 2008
System Information: GSM Overview The OMC-R database
RDBMS
The OMC-R database, maintained at the system processor, uses an industry standard Relational
Database Management System (RDBMS) known as INFORMIX. The DBMS manages access to
its own stored data and provides its own data protection. It is made up of a PM sub-schema, a
CM sub-schema, and an EM sub-schema. The PM sub-schema is used for storing processed
performance statistics from the GSM network. The CM sub-schema holds the configuration
data needed for network maps used by the OMC-R GUI and for cell parameter optimization.
The EM sub-schema stores the subscription lists used to subscribe to incoming events and
alarms (see Figure 3-18).
Database schema
The OMC-R database is a centralized data store for data that has to be further manipulated,
either by system users or by other OMC-R application areas. A database schema is a data
model of a precise, complete definition of the data to be stored. It provides a formal notation
data model of tables, rows, columns, and keys. The database schema predefines the tables in
which the data is stored. The physical structure of the tables cannot be altered, only their
contents can be manipulated.
68P02901W01-S 3-47
Jul 2008
Database size Chapter 3: OMC-R Overview
Database size
The database can be sized at installation to meet the requirements of the GSM Network. The
disk is hardware mirrored to provide a high level of protection against loss of data in case
of hardware failure.
Structured Query Language (SQL) and Applix access for custom reporting
SQL and Applix are industry standard languages, which can be used to write applications to
extract performance management data from the database. Read-only access to the data is
available.
The OMC-R system administrator is provided with a facility for online back up of the OMC-R
database. This back up avoids halting the OMC-R during routine back up operations.
3-48 68P02901W01-S
Jul 2008
System Information: GSM Overview The OMC-R GUI configuration
Typically the OMC-R configuration contains several processors; one Netra 210 or Sunblade 150
GUI server and Sunblade 150s as GUI clients. A second can be configured as a GUI server
or the system processor can fulfill this GUI server role. Two GUI servers are the preferred
arrangement and each supports half of the GUI clients. This arrangement allows system
operation to continue if one of the GUI servers fails.
Each machine is a complete UNIX system, which runs the same GUI version.
The OMC-R GUI expects all the GUI clients to be configured as standalone NFS (Network File
System) machines. This configuration allows each machine some degree of independence
while still allowing resources to be shared.
LAN configurations
The Sunblade 150s execute the display process and function as operator workstations. The
OMC-R GUI software is made accessible over the LAN by configuring the machines in the
following way:
A Sunblade 150 is installed as a GUI Server to the Sunblade 150 GUI clients.
Other configurations
Other network configurations can also exist, such as a GUI processor configured to run the
OMC-R GUI from a remote site. In networks containing two OMC-Rs, a GUI processor in the
local OMC-R is configured to monitor a remote OMC-R during the night. The local OMC-R
is known as the night concentration center.
68P02901W01-S 3-49
Jul 2008
GUI processor Chapter 3: OMC-R Overview
GUI processor
Up to 10 additional processors can be added to the system to support the GUI interface. One of
the machines must be configured as a GUI server. The additional machines mount the display
software from the GUI server. The total number of GUI sessions supported is 30 as on the
standard OMC-R. Each processor supports one GUI session.
An example of a GUI processor hardware configuration is shown in Table 3-5. The GUI processor
is configured with software as shown in Table 3-6.
3-50 68P02901W01-S
Jul 2008
System Information: GSM Overview The network status summary feature
Maps
Figure 3-19 shows the maps icon on the OMC-R GUI front panel.
ti-GSM-Maps icon-00078-ai-sw
The role of the OMC-R in a GSM network is to allow network operators to perform network
management functions to ensure that the network operates efficiently, and the service to the
customer is maintained. The OMC-R acts as a central collection point for measurement data
used in the analysis of current performance and future planning of the network.
Features
Alarms icon
Alarm summary
68P02901W01-S 3-51
Jul 2008
Features Chapter 3: OMC-R Overview
Figure 3-20 The network status summary options on the GUI front panel
3-52 68P02901W01-S
Jul 2008
System Information: GSM Overview The CM MIB
The CM MIB
The system processor contains the CM Management Information Base (CM MIB) that holds all
the configuration data. The data is required for the network maps of the OMC-R GUI and for
cell parameter optimization. Information in the CM MIB includes lists of the various types of
nodes in the GSM network, with their attributes and interconnections. The CM MIB also lists
maps containing nodes and connections on each map. All the GUI processors which run the NSS
feature, communicate with the CM MIB using an internal process called cm_mib.
or
68P02901W01-S 3-53
Jul 2008
GUI client Chapter 3: OMC-R Overview
GUI client
Software configuration
Sun Micro systems Sunblade 150 (operator workstations) display the GUI data. This GUI
client is installed on either the system processor, or on one of the Sunblade 150 stations. In
all cases, the OMC-R GUI client software is executed on the local Sunblade 150s. A Netra
210 or Sunblade 150 machine is designated as a GUI server to half the GUI clients, providing
redundancy if one of the GUI servers fail.
Figure 3-21 shows the GUI client hardware and software configuration.
Hardware features
The GUI clients are configured as standalone NFS (Network File System) machines.
3-54 68P02901W01-S
Jul 2008
System Information: GSM Overview Night concentration
Night concentration
Figure 3-22 shows a night concentration center with one ULTRA5/Sunblade 150 configured as a
GUI Server for both region A and region B. That is, only one workstation is required during the
quiet night periods enabling a reduction in operating personnel.
Printer
Printer
Concentration centre
Printer
LAN
GUI Server
Bridge/ Router X.21
GUI Server
GUI Client
System Processor
68P02901W01-S 3-55
Jul 2008
Network status summary Chapter 3: OMC-R Overview
Map process
When a network map, for example, Network 1600b: Device Mode (see Figure 3-23), is selected
using the Maps icon on the OMC-R front panel, a map process is invoked on the GUI processor.
Active
NSS subscription List
3-56 68P02901W01-S
Jul 2008
System Information: GSM Overview Configuration data
Configuration data
All the configuration data required to run the network map are stored in the CM MIB, which is
maintained on the OMC-R system processor. The CM MIB stores a series of managed objects to
which relevant network configuration data and data required to configure maps are assigned.
For example, both a BSS and a Map are regarded as managed objects with different data. All
the GUI processors that run the network maps communicate with the CM MIB using an internal
process called cm_mib.
The EM Proxy process contains a list of all NEs, SITEs, cells, and links. The process examines
the incoming alarm messages and compares it to the list. It updates the list if a change has
occurred. Every two seconds, a changed list is forwarded to the GUI processor. The list contains
attributes, which reflect the severity of the alarm and its handling state. These attributes
in turn update the Alarm Summary on the GUI front panel, and the attributes of the links
and nodes on the active map, as configured in the CM MIB. The Contained Devices form and
alarm icons are also updated. Similarly, incoming State Changed Events from SITEs and MMSs
change the state of the attributes in the CM MIB. It reflects the administrative and operational
states of the different SITE and CommsLink configuration objects, representing the physical
devices in the network.
68P02901W01-S 3-57
Jul 2008
GUI clients and servers: Overview Chapter 3: OMC-R Overview
The client or server concept is a common form of distributed system in which software processes
are split between server tasks and client tasks. A client sends requests to a server, according
to a standard protocol, asking for information or action. The server responds by sending the
requested information or by performing the required action.
This operation is analogous to a customer (the client) who sends an order (request) on an
order form to a supplier (the server). The supplier despatches the goods and sends an invoice
(response). The order form and invoice are part of the protocol used to communicate in this
analogy.
The connection between a GUI client and GUI server is through message passing, which is over
a network or even within a single machine. There is a single centralized server or several
distributed servers, depending on workloads. This model allows clients and servers to be placed
independently on nodes in a network, possibly on different hardware and operating systems.
The GUI servers and GUI clients have now replaced the older MMI servers and clients. However,
MMI servers and clients can both be re-deployed as GUI clients, but only the high-end MMI
servers have the power to run as a GUI server.
3-58 68P02901W01-S
Jul 2008
System Information: GSM Overview Network maps
Network maps
Functionality
Network maps show status information on the network and enable the following different types
of functionality to be invoked for a selected NE:
Network maps present the current network topology. Network configurations can be updated
using the Detailed Views and an Audit, initiated to ensure consistency between the MIB and
the Network. A full network map, which displays all NEs and links in the network is available.
Each NE can be expanded to show the SITEs and links within the NE. Maps can be zoomed or
expanded when displayed (refer to Figure 3-23). If the system is configured, more detailed maps
of any part of the network can be displayed.
Alarm state
A color change in the NE and link icons on the map indicate the incoming alarms. The alarms
icon on the front panel also flashes, and wherever available, there is an audible warning.
The map display uses three different icon types to represent state changes in SITEs (represented
by SITE map nodes) and MMS devices (represented by map links). Refer to The map display
on page 3-61 in the Map Display section. The icon types represent in-service (INS),
out-of-service (OOS), and unknown states. The operational and administrative states of the
SITE or MMS determine the state changes.
Each map provides an alarm display window that subscribes only to incoming alarm messages
for selected NEs or SITEs. This window allows standard alarm handling to be performed.
Remote login, through a TTY window for a selected NE, allows BSS GUI commands to be sent to
the NE. The responses to the commands can be monitored.
The system checks the active alarm list for any unhandled alarms and retransmits any state
changes that have occurred since the previous Resync operation.
68P02901W01-S 3-59
Jul 2008
Different maps available Chapter 3: OMC-R Overview
One map for each BSS or RXCDR, containing all configured SITEs and links.
Map modes
There are two map modes available from the View menu:
Device Mode displays severities according to the impact of faults on devices. For example,
a critical redundant device produces a critical severity.
Subscriber Mode displays severities according to the impact of faults on subscribers. For
example, service loss, capacity loss, or redundancy loss.
Map configuration
Different maps of the network can be displayed, depending on what type of information the
operator has to monitor. This is achieved by adding the new map configuration data to the CM
MIB through the Detailed View forms and Audit. The OMC-R GUI provides facilities for the
automated process, followed by operator input for longitude and latitude data.
When the MIB is initially populated with data from configuration files, default maps are created.
In the absence of any geographical map background files, the maps are displayed on a default
map background consisting of a single solid color. To use map backgrounds other than the
default, a background map, usually a geographical map, is assigned to the map object, which
configures the network map.
3-60 68P02901W01-S
Jul 2008
System Information: GSM Overview The map display
Map backgrounds
When maps are initially configured, they are displayed on a default map background of a single
solid color. A background, usually a geographical map background, is assigned to the network
map. Each map background is specified when defining the MapNode object. This map points to
a physical file describing the actual shape of the background map.
Map links
Each map link represents one or more 2 Mbps links between the NEs or SITEs in the network.
This is set when the map is configured. A cluster icon is used to represent a group of icons,
which are too close together to be displayed separately on the map.
Alarm reporting
If an icon on a map is flashing, it indicates that there are alarms which are not handled for
the device or devices it contains. Alarms from links cause both the link and the node, where
the faulty MSI/MMS is contained, to flash. The icon color is automatically reset to the color
representing Clear (defaulted to green) when the operator clears the alarm, or an alarm clear
message is received from the network.
State changes
The status of a SITE or MMS in the network determines whether it is in service (INS), or Out Of
Service (OOS. INS indicates it is supporting (or able to support) user traffic and OOS indicates
that it is unable to support user traffic. The administrative state (controlled by the operator)
and the operational state (controlled by the NE fault management application) determine the
device status.
The different combinations of operational and administrative states determine whether the node
or link is INS, OOS, or has an unknown state. For example, a SITE is INS if its operational state
is enabled or busy, and its administrative state is unlocked.
The normal state of a device is INS (busy or unlocked, or enabled/unlocked for a redundant
device). An operator or the NE fault management software can take a device OOS by issuing a
LOCK command or a SHUT-DOWN command. A LOCK is intrusive as it terminates all activity on
the device when the command is executed. The SHUTDOWN command permits the operator to
specify a time interval before the device changes from UNLOCKED to LOCKED state.
The map display uses different icon types to represent a change in state of devices.
Figure 3-24 shows the indications of the icons for an INS, unknown, and OOS device:
68P02901W01-S 3-61
Jul 2008
Additional information Chapter 3: OMC-R Overview
Additional information
Refer to the OMC-R Online Help facility for a complete description of the following:
Network map display.
Icon colors.
Pending state
An asterisk *, on a node icon represents nodes in a pending state. Figure 3-24 shows the map
icons.
3-62 68P02901W01-S
Jul 2008
System Information: GSM Overview Additional information
68P02901W01-S 3-63
Jul 2008
How administrative and operational state changes work Chapter 3: OMC-R Overview
State changes
Administrative and operational state changes are only relevant for SITEs and links on the map.
Figure 3-25 illustrates how the icons representing the SITEs or links are changed to reflect
the change in state of the physical device.
3-64 68P02901W01-S
Jul 2008
System Information: GSM Overview State changes
68P02901W01-S 3-65
Jul 2008
How alarms work Chapter 3: OMC-R Overview
Alarm icons
Incoming alarms are reported by a flashing MapNode or MapLink icon, colored to represent
different alarm severities. If an icon on a map is flashing, it denotes the presence of unhandled
alarms for the device or devices it represents. Alarms from links cause both the MapLink and
the MapNode containing the faulty MMS to flash and change color.
3-66 68P02901W01-S
Jul 2008
System Information: GSM Overview Alarm icons
68P02901W01-S 3-67
Jul 2008
Colors Chapter 3: OMC-R Overview
Colors
The color of any displayed icon or link reflects the severity of alarms in the device or group of
devices represented by the icon. The default colors are defined in Table 3-7.
When an icon represents a group of devices an alarm occurrence in any device within the
group is shown at the displayed icon.For example, a BSS represents all the devices in the BSC
and BTSs within the BSS.
If there are alarms of different severities existing for the same device, or group of devices the
display color reflects the most severe alarm condition.
The icon color is automatically reset to the Clear color when the operator clears the alarm or an
alarm clear message is received from the network.
3-68 68P02901W01-S
Jul 2008
System Information: GSM Overview Map configuration
Map configuration
The CM MIB stores a series of managed objects to which relevant configuration data is assigned.
For example, both a BSS and a Map are considered to be managed objects requiring different
data. All the GUI processors that run the Network Map communicate with the CM MIB using
an internal process called cm_mib.
Figure 3-27 shows the CM MIB showing the different groups of managed objects.
Figure 3-27 The CM MIB showing the different groups of managed objects
68P02901W01-S 3-69
Jul 2008
Two object groups Chapter 3: OMC-R Overview
Used to build the different maps and which take their data from the configuration objects.
Configuration objects
Hold all the data about the physical network. There is a containment relationship between
the different managed objects.
3-70 68P02901W01-S
Jul 2008
System Information: GSM Overview Graphic objects
Graphic objects
Graphic objects
There are three graphic objects in the CM MIB. Figure 3-28 shows the containment relationship
between the graphic objects.
Map
The Map graphic object represents a map, which appears in the Map List Display menu on
selecting the Maps icon from the front panel. It defines the map name and the background
map used with it.
MapNode
The MapNode graphic object specifies the type of NE or SITE to be represented on the map.
BSC
MSC
RXCDR
BSC-BTS
BTS
68P02901W01-S 3-71
Jul 2008
MapLink Chapter 3: OMC-R Overview
MapLink
3-72 68P02901W01-S
Jul 2008
System Information: GSM Overview Configuration objects
Configuration objects
Configuration objects
68P02901W01-S 3-73
Jul 2008
Configuration objects Chapter 3: OMC-R Overview
3-74 68P02901W01-S
Jul 2008
System Information: GSM Overview Configuration objects
Network
The network configuration object represents the overall network being managed. There is only
one Network configuration object in the MIB, and it is already configured on delivery.
OMC-R
The OMC-R configuration object represents the Operation and Maintenance Center. There is
usually only one OMC-R object in the MIB.
SoftwareLoad
The SoftwareLoad object is used to point to a BSS or RXCDR software load currently stored
in the OMC-R. A maximum of 2147 483 647 SoftwareLoad objects can be contained within an
SW Inventory object.
MSC
The MSC configuration object represents the Mobile Switching Center. The OMC-R does not
directly manage the MSC, but manages the links between the BSSs, RXCDRs, and the MSC.
There are usually only two of these objects in the MIB.
BSS
The BSS configuration object represents the Base Station System. An object represents each
BSS in the physical network (maximum of 120).
RXCDR
The RXCDR configuration object represents the Remote Transcoder. There are as many of these
objects as exist in the physical network (maximum of 120).
CommsLink
The CommsLink configuration object defines the two MMS ports in the different SITES that
establish the 2 Mbps link between the SITES.
PCU
The Packet Control Unit (PCU) configuration object manages the packet radio interface, and
also enables the interface from the BSS to the Serving (E)GPRS Support Node (SGSN).
SITE
The SITE configuration object represents a BSS SITE in the network. The functionality of any
given SITE depends on the devices it contains.
68P02901W01-S 3-75
Jul 2008
Hardware devices Chapter 3: OMC-R Overview
Hardware configuration
All the different hardware cages in a SITE are connected by a LAN, and configured as a BSC
or a BTS. SITE 0 must always contain the BSC functionality, and is configured as a BSC or a
BSC-BTS. The remaining SITEs can only be configured as BTSs. There are as many of these
objects as exist in the physical network (maximum of 100 per BSS). An RXCDR can also have a
SITE 0 associated with it.
Hardware devices
The hardware devices object represents an abstract logical container class. It is used to group
the different hardware devices on the BSS.
Cabinet
The cabinet object class describes a single cabinet within the site.
Cage
EAS
The EAS configuration object represents the detection of a single External Alarm System device
within the site.
Processors
The processors object represents a logical container class. It provides a grouping for the
GPROC (Generic Processor Boards), BSP (Base Site Control) and CSFP (Code Storage Facility)
processors within the site.
KSW pair
The KSW pair object is used to represent a pair of KSW (Kiloport Switch board) devices, which
manage a single TDM highway.
GCLK
The GCLK object represents a Generic clock board. There is one per site.
IAS
The IAS configuration object represents the detection of an Internal Alarm Systems such as
a power supply failure. There is one IAS device per cabinet.
3-76 68P02901W01-S
Jul 2008
System Information: GSM Overview Software functions
LAN
The LAN object represents a single Local Area Network within a site.
TDM
The TDM object represents a single Time Division Multiplex highway within a site.
MSI
The MSI configuration object represents a Multiple Serial Interface (MSI) board, which controls
two MMS ports. There is a maximum of 101 MSIs at SITE 0 and 51 at other SITEs.
COMB
The COMB is a general abbreviation used for a Combiner, which combines two or more RF
transmissions, from a BTS Transceiver Control Unit (TCU), for a simultaneous broadcast to a
single antenna.
Software functions
The software functions represent an abstract logical container class. It is used to group the
different software functions on the BSC.
BTF
The BTF object represents a Base Transceiver Function. There is a single instance of this
class in BSC site 0.
LCF
The LCF object represents a Link Control Function. There is a single instance of this class
in BSC site 0.
OMF
The OMF object represents an OMF GPROC Function. There is a single instance of this class
in BSC site 0.
Logical links
The logical links represent an abstract logical container class. It provides the grouping for
the various links present at the site.
68P02901W01-S 3-77
Jul 2008
Radio frequency Chapter 3: OMC-R Overview
CBL
A CBL link can be configured between the BSC or RXCDR and the Cell Broadcast Center (CBC).
This is used for downloading messages to broadcast along with other necessary information
such as repetition rate and number of broadcasts.
MTL
The purpose of the MTL is to provide a link for signaling information between the BSC and the
MSC. In the Motorola system, when local transcoding is used, this is a physical connection
between the BSC and the MSC. When a Remote Transcoder is used, the logical MTL is made
up of two physical parts; the connection between the BSC and the RXCDR and the connection
between the RXCDR and the MSC.
OML
This link is for control and communication between the BSS and the OMC. The RXCDR provides
an OML, for each BSC connected to it.
XBL
An XBL link is configured between the BSC and the RXCDR for exchanging internal Fault
Management (FM) data between them.
RSL
The RSL represent a Radio Signaling Link. The RSL can only be contained within the remote
BTS in which it terminates.
PATH
The PATH object specifies the path connection between a BSC and a specific BTS site. The path
connection is described as a series of MMS connections between sites. There can be a maximum
of 10 PATH objects contained in a SITE object.
Radio frequency
The radio frequency represents an abstract logical container class. This provides the grouping
for the various radio-related objects.
RTFGroup
The RTFGroup object is used to represent a single RTF function grouping within a site. A
maximum of six RTFGroup objects can be contained in a SITE object.
3-78 68P02901W01-S
Jul 2008
System Information: GSM Overview Radio frequency
RTF
The RTF object is used to represent a single RTF function within a site. A maximum of 25 RTF
objects can be contained in an RTFGroup object.
DRIGroup
The DRIGroup object is used to represent a single DRI device grouping within a site. It contains
one or more DRIs, which are connected to the same antenna and use the same portion of the
TDM highway. A maximum of six DRIGroup objects can be contained in a SITE object.
DRI
The DRI object is used to represent a single Digital Radio Interface (DRI) device within a site. It
provides the interface between the DRCU and the digital portion of a BSS. A maximum of 25
DRI objects can be contained in a DRIGroup object.
CELL
The CELL object is used to describe the cells within a BTS site. Up to six CELL objects can be
created under a SITE object. A maximum of 250 CELLs can be contained within a BSS.
FreqHopSys
The FreqHopSys object is used to represent a single frequency hopping system within a cell.
SMSCBmsg
The SMSCBmsg object is used to represent a single Short Message Cell Broadcast (SMS CB)
message within a cell.
Neighbor
The Neighbor object is used to identify a neighbor cell for a specific cell, that is, those cells
to which it can handover calls. A maximum of 64 Neighbor objects can be created under
a CELL object.
TestNeighbor
The TestNeighbour object is used to describe the test neighbor cells for a specific cell. One
instance of this class represents one test neighbor cell.
Handover control
68P02901W01-S 3-79
Jul 2008
ProxyCell Chapter 3: OMC-R Overview
Power control
Power Control objects are RxlevDlPC, RxlevUlPC, RxqualDlPC, and RxqualUlPC. These objects
describe the power control algorithms based on certain criteria. For more details, refer to
the OMC-R Online Help.
ProxyCell
The ProxyCell object represents CELLs outside the current PLMN. A maximum of 500 ProxyCell
objects can be contained in a SITE object.
UserProfile
The UserProfile object represents an OMC-R user who uses the OMC-R GUI. A maximum of
256 UserProfile objects can be contained in an OMC-R object.
The network objects, which the CM MIB process creates automatically, are as follows:
NESoftware
The NESoftware object is automatically created when a BSS or RXCDR object is created.
SW Inventory
The SW Inventory object is automatically created when an OMC-R object, with the active flag
set to TRUE, is created.
MMS
TRX
A TRX object is automatically created in a CELL object when an RTF object of type BCCH is
created at a SITE with its carrier attribute assigned to the relevant CELL.
Source
A Source object is automatically created when a Neighbor object is created if the CELL it
identifies exists. Otherwise, a Source object is automatically created when the CELL object
is created.
3-80 68P02901W01-S
Jul 2008
System Information: GSM Overview Automatically created map display objects
The map display objects, which the CM MIB process creates automatically, are as follows:
Map
A Map object is automatically created when a Network, BSS, or RXCDR object is created.
MapNode
A MapNode object is automatically created when a BSS, OMC-R, MSC, RXCDR, or SITE object is
created. The map node must be associated with an object of the relevant type.
MapLink
68P02901W01-S 3-81
Jul 2008
Periodic Supervision of Accessibility (PSA) Chapter 3: OMC-R Overview
Definition of PSA
PSA failure
If a BSS fails to respond to a PSA request for its status, the OMC-R generates an alarm for that
BSS. This alarm indicates that the BSS failed to respond to a message requesting its status, and
is indicative of a problem at the BSS. The OMC-R continues to send messages periodically to the
BSS requesting its status. On receipt of a response message from the BSS, the OMC-R changes
the alarm severity of the message to Clear.
An alarm is also generated when the BSS informs the OMC-R that it is not operational. The
OMC-R continues to send messages periodically to the BSS requesting its status. On being
informed that the BSS has returned to operating correctly, the OMC-R changes the alarm
severity of the message to Clear.
3-82 68P02901W01-S
Jul 2008
System Information: GSM Overview Disk usage exceeded
An alarm is raised when either of the two (upper and lower) threshold values of disk usage are
exceeded on the /, the /home, the /usr, and the /usr/gsm/ne_data partitions of the system
processor.
The System removes any logfiles older than three days from the $OMC_TOP/logs directory
using routine maintenance cron jobs, or if the upper disk usage threshold is exceeded. The
threshold value must return to the default value of 90%.
The file $OMC_TOP/config/global/FM_audit.CNFG contains the values that are used for
setting the timers for each audit and disk usage limits. These values are set at the installation
time, and the system administrator can only change the values.
Further information
For information on setting the related parameters, see Maintenance Information: Alarm
Handling at the OMC-R, (68P02901W26).
68P02901W01-S 3-83
Jul 2008
DataGen Chapter 3: OMC-R Overview
DataGen
Introduction to DataGen
DataGen is a GSM product used to create BSS databases offline. DataGen can store past,
current, and future versions in an Informix database. These databases can be transferred to the
OMC-R, and then they are downloaded to the live BSSs. DataGen runs on its own processor and
can be integrated with the OMC-R if they are both on the same LAN.
DataGen is used to make major changes to a network, for example, upgrades to the BSS
software, frequency replans, and network expansion. Figure 3-30 shows the DataGen
configuration in a GSM environment.
3-84 68P02901W01-S
Jul 2008
System Information: GSM Overview DataGen configuration management
DataGen provides the user with the capability of performing offline configuration of the
Motorola GSM network entities (NEs). The Informix database contains two types of information:
A representation of the information required to create a Sysgen script for all supported
BSS releases.
Details relating to syntax, parameters, elements, and their associated ranges for the GUI
commands in the Sysgen script are included.
These areas are identified by country or network, name, software release, and
configuration number. The configuration number allows multiple BSSs to exist within the
DataGen database.
Off-line MIB
Figure 3-32 shows the off-line MIB, which is used to create new networks, visualize, and validate
networks before deployment into a live network. It has a common user interface with the
online OMC-R. BSS binary files are used to create the network which is displayed as a tree like
representation called the Navigation Tree. It is possible to update multiple BSS binary files
simultaneously, for example, propagating neighbor changes from one BSS binary file to another.
Neighbor propagation.
68P02901W01-S 3-85
Jul 2008
Off-line MIB Chapter 3: OMC-R Overview
3-86 68P02901W01-S
Jul 2008
System Information: GSM Overview Feature Capacity Licensing and Audit
The License Audit tool monitors the usage of carriers across the network on a per feature basis.
Information is gathered by running scheduled audits against the OMC-R CM database. The
audits produce a report indicating the number of RTFs equipped in the database to support
each feature.
The audit is triggered by a configurable interval parameter in the OMC software. If the interval
parameter is not set, or set outside the permissible range of 2 to 48 hours, the default value of
12 hours is used. The result of the audit (actual usage) is compared with the license file per
feature. An alarm is generated for each feature where the license usage is exceeded. If the
usage is within the limit, the License Audit Tool generates a corresponding event. The alarms
and events are displayed at one or all OMCs in the network as configured during the installation.
68P02901W01-S 3-87
Jul 2008
Feature Capacity Licensing and Audit Chapter 3: OMC-R Overview
3-88 68P02901W01-S
Jul 2008
Chapter
This chapter provides a summary of the features of Motorola BSS software releases. Releases of
software before GSR2 were identified by four-digit release numbers, such as 1.2.1.1. After the
1.4.1.x release, the numbering system was revised; release 1.5.0.x was renamed GSR2.
68P02901W01-S 4-1
Jul 2008
Feature Capacity Licensing and Audit Chapter 4: BSS Software Release Features
4-2 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release 1.1.1.0
Feature Description
Teleservice 11 Compliant with GSM 02.03 for speech, data,
and signal transmission from the PSTN/ISDN.
Connectionless call processing Provides the functionality for dialogue
between the MSC and MS.
MTP Part of the MSC-BSS A interface. Supports
point-to-point signaling, compliant with
ITU-TSS SS7.
SCCP Part of the MSC-BSS A interface. Compliant
with ITU-TSS SS7 and ITU-TSS Q.711-Q.714
and GSM 08.06 para 5.2 - para 5.5.
BSSAP Part of the MSC-BSS A interface.
Comprises two distinct parts.
BSSMAP,
compliant with GSM 08.08 para 3.DTAP,
compliant with GSM 08.06.
RR status Sent by MS or network, can contain error
conditions (refer to GSM recommendation
4.08).
Multiplexing Compliant with GSM 05.02, supports logical
channels for full rate speech channels.
Layer 3 Specifies the procedures used at
the radio interface for call control,
mobility management, and radio resource
management.
Modified Abis (Mobis) Reduces 2 Mbps link traffic by increasing BSS
processing in the BTS.
MMI entry/response at local TTY Compliant with GSM 12.01, 12.06 allows
command entry and printing of responses
and alarm messages for the local network
element.
System change control administration Provides services for the management and
administration of configuration or data
changes.
Continued
68P02901W01-S 4-3
Jul 2008
Release 1.1.1.0 features Chapter 4: BSS Software Release Features
Continued
4-4 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.1.1.0 features
68P02901W01-S 4-5
Jul 2008
BSS software release 1.1.2.0 Chapter 4: BSS Software Release Features
Feature Description
BSS-OMC agent statistics reporting facility Statistics can be reported to the OMC based on
X.25 (without FTAM or CMISE).
Additional statistics provided A series of measurements as required by GSM
12.04, and some Motorola-unique measurements
are provided.
Collect and provide access to listed Provides additional functionality for statistics
statistics values through MMI commands.
BSC-OMC agent: Software reporting Reports software alarms to the OMC from the
BSC.
BSC-OMC agent: Hardware reporting Reports hardware alarms to the OMC from the
BSC.
Diversity option commands Turns On or Off the diversity option for a site
using a MMI command.
Support antenna diversity (BTS4-D) Modification to the BSS software to provide
support for BTS4-D.
Fault management Provides enhanced fault detection and
management.
Fault reporting to the OMC Collects alarms within the BSS and reports them
locally to the OMC.
Maximum system configuration Supports a database up to six MB in size.
MMI commands MMI commands are added or enhanced to
support the diversity option, XCDR maintenance
and BSS database control.
System commands System commands are added or enhanced to
support fault management and configuration
management.
Device management of a site Supports a number of implementation commands
for a site.
Continued
4-6 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.1.2.0 features
68P02901W01-S 4-7
Jul 2008
BSS software release 1.1.2.1 Chapter 4: BSS Software Release Features
Function Description
Handover algorithm - D1 Supports algorithm as specified in FEIN
specifications for Detecon (FS 05.08.1.1 (2.2),
Chapter 3.3.1).
Force OMC download of EEPROMs Forces an OMC download of GPROC flash
EEPROM manually.
Device management of BSS device (EAS) Supports implementation commands on the
EAS device PIX.
System commands Supports fault management and configuration
management.
4-8 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release 1.1.2.2
Feature Description
BTS daisy chain with return loop The return loop feature, now known as a
closed loop, adds a closed loop capability for
open loop BTS configurations.
Signaling Point Inaccessible SPI implements the BSSMAP procedures for
signaling point inaccessible and user OOS.
Remote tuning combiner Allows combination of multiple RCUs.
Flash EEPROM Prevents accidental write to the flash
EEPROM. Provides a downloadable bootstrap
flash EEPROM for GPROCS.
EAS enhancements Includes optocoupler number and alarm text
in EAS optocoupler alarms sent to the OMC.
68P02901W01-S 4-9
Jul 2008
BSS software release 1.1.2.3 Chapter 4: BSS Software Release Features
Feature Description
Advanced RCU download Reduces BTS outage time during BTS
initialization by improving overall DRI/RCU
download and configuration time. The
time reduction increases as the number of
DRI/RCUs increases at a site.
4-10 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release 1.2.0.0
Feature Description
Baseband hopping Switches information generated by the channel
coding/interleaving function on the DRI to the
appropriate RCU.
Synthesizer hopping Re-tunes RCUs in real time from frequency to
frequency.
Data services full-rate traffic channels Supports data services on full-rate radio traffic
channels.
Support alternate speech and data Allows MSC/BSS co-ordinated switching between
speech and data using in-call modification
procedures.
GPROC device management Removes the need for BTS reinitialization when
RSL links to the BSC are interrupted.
Device management of GPROCs Ensure synchronization of the BSC and BTS call
processing after loss of all links or reinitialization.
Cross load time improvement Reduces the time to cross load between GPROCs
at a site.
Paging distributor optimization Ensures that only one message is sent to a BTS per
A interface paging message.
Short message service, point to point The BSS supports Short Message Service (MS
originated and MS terminated). Motorola is phase 1
compatible as the BSS responds to a SAPI n' clear
with a SAPI n' clear complete although the SAPI 3
connection is not torn down.
Simple flow control Provides BSS overload management by barring MS
access classes as necessary when call information
block usage reaches a predetermined threshold.
Intra-BTS synchronized handover Allows handovers that do not require the BSS
to send a physical information (timing advance)
message to the MSC.
LAN device management and swap over Provides management for the LAN hardware
devices and enables switching between the two
LAN hardware loops that interconnect all GPROCs
at a BSC or BTS site.
Continued
68P02901W01-S 4-11
Jul 2008
Release 1.2.0.0 features Chapter 4: BSS Software Release Features
Continued
4-12 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.2.0.0 features
68P02901W01-S 4-13
Jul 2008
BSS software release 1.2.0.3 Chapter 4: BSS Software Release Features
Feature Description
Alarm and status synchronization The BSS supports future development of
the OMC alarm and status synchronization
feature within the OMC. Impacted
areas are Fault Management (CA
and FTP) and the OMC interface.
The alarm and state synchronization feature
provides a mechanism for synchronization
of the OMC and BSS/RXCDR device status.
Status information is composed of both alarm
and device state information. Normally, the
BSS/RXCDR sends alarms and device state
change events to the OMC as they occur, so
the OMC keeps up to date with changes to the
network element device status. However, a
mechanism for device status synchronization
is required both at OMC initialization time,
and after a failure of the OMC, BSS/RXCDR or
the links between them. Synchronization can
be initiated through operator request OMC
init, or it can be set up to occur automatically
at a configurable interval.
4-14 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release 1.2.2.0
Feature Description
Switchover improvement When a 2 Mbps link between a BSC and a remote BTS
fails, traffic is switched to a redundant 2 Mbps link if
one is available. The switchover improvement feature
reduces the time taken to switch links, thus minimizing
any break in voice or data transmission.
GCLK synchronization Ensures that air interface data timing and RF
frequencies remain within the GSM recommendations
and eliminates frame slips over the E1 interface.
Database level number The database level number feature keeps a database
level number for each site in the BSS. Database level
number increments are sent to a remote BTS only if
the database changes for that site. This feature helps
prevent unnecessary database downloads to remote
BTSs and also reduce the message traffic in the BSS.
BSC-BTS download compression This feature reduces the time taken by a BSC to
download the CM database to its BTSs. The BSC
compresses the information before downloading it,
and the BTS decompresses it on receipt. Checksum
procedures prevent data loss or corruption during
compression and decompression.
Preventative cyclic retransmission Preventive Cyclic Retransmission (PCR) involves the
retention of a signal unit at the transmitting terminal
until Acknowledgment is received from the receiving
terminal. During the period when there are no new
signal units to be transmitted, the transmitting terminal
cyclically retransmits all the signal units that have not
yet been acknowledged by the receiving terminal.
Multiple digital host processor The multiple DHP cage feature allows more than one
DHP per cage.
Timeslot reservation This feature allows ranges of timeslots on specified 2
Mbps links to be barred from use by a BSS (reserved)
using a MMI option or the OMC.
Continued
68P02901W01-S 4-15
Jul 2008
Release 1.2.2.0 features Chapter 4: BSS Software Release Features
4-16 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release 1.2.2.2
Feature Description
TopCell alarm enhancement The BSS software supports the additional
alarms that are generated for each TopCell
cabinet.
TopCell base The BSS software supports the new TopCell
hardware. The TopCell product is a complete
cell site (BTS).
TopCell requirements Defines the new requirements for a TopCell
site.
Six carrier BTS shelf The BSS supports a six carrier BTS shelf for
DRCU3.
ExCell 6 The BSS supports a six carrier version of the
ExCell product.
68P02901W01-S 4-17
Jul 2008
BSS software release 1.2.2.3 Chapter 4: BSS Software Release Features
Release 1.2.2.3 addresses an internal problem that could pose a potential risk to customers with
medium to large configurations. This release supersedes release 1.2.2.2 and should be used
instead of release 1.2.2.2.
4-18 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release 1.2.3.0
Important information
GSM BSS 1.2.3.0 is released on a limited basis to support DCS1800 First Office Application
(FOA). The extent of functionality supported by this release is limited to basic cellular phone
service. The following feature functionality is excluded until sufficient testing has been
accomplished to release these features for use in the DCS1800 environment.
Feature Description
Excluded features The following features are excluded from
this release: 1800 MHz Remote Tuned
Combiner (RTC). DTX (Discontinuous
Transmission). Short Message Service
(SMS) point to point. Short Message Service
(SMS) cell broadcast single background
message. Data services alternate speech;
data services full rate. Frequency hopping,
baseband; frequency hopping, synthesizer.
A BSS operating with BSGSM 1.2.3.0 in
GSM900 mode has not been qualified to
operate with another BSS in DCS1800
mode, while both the BSSs are connected
to the same OMC. It is recommended that
all BSS connected to a single OMC remain
homogenous with respect to the radio
spectrum they serve.
Fault isolation (enhanced) This feature provides enhancements to
existing fault isolation capabilities for the DRI
and GPROC devices.
Continued
68P02901W01-S 4-19
Jul 2008
Release 1.2.3.0 features Chapter 4: BSS Software Release Features
Continued
4-20 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.2.3.0 features
68P02901W01-S 4-21
Jul 2008
BSS software release 1.3.0.x Chapter 4: BSS Software Release Features
Release 1.2.3.0 features integrated into 1.3.0.x are included for customers upgrading from
release 1.2.2.3.
Feature Description
Large BSS configuration capacity This feature introduces capacity support for a
system consisting of 50 sites, 90 cells, and 90
active RCUs (TRXs).
Fault isolation (enhanced) DRI and GPROC This feature provides enhancements to
existing fault isolation capabilities for the DRI
and GPROC devices.
KSW, TDM, and TBUS management Provides control for configuration of the listed
devices and allows switching between TDMs
without re-booting the system.
Manage inactive GPROCS This feature enhances the Operation and
Maintenance of GPROC devices.
BSC LCF swaps Allows switching of logical links to the MPT
layer 2 physical links if an MTL GPROC fails
during transmission.
BSC OMF The BSS provides the capability to handle
the OMF function (OMF GPROC) failures
independently without impacting the
remaining GPROCs at the BSS site. This
capability does not prevent an interruption to
call processing service.
BTS DHP swaps Shifts functionality of the RF carrier from a
failed DHP to a healthy device, thus limiting
the effect of the failed DHP recovery to a
subset of the carriers at the BSS/BTS site. All
carriers on the failed DHP are disabled and
re-enabled on other surviving DHPs/BTP/BTF
within the same cage, if there is available
capacity.
BSC BTF swaps Allows BTF swapping to ensure no loss of
function resources if a GPROC fails.
Continued
4-22 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.3.0.x features
Continued
68P02901W01-S 4-23
Jul 2008
Release 1.3.0.x features Chapter 4: BSS Software Release Features
4-24 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release 1.4.0.0
Feature Description
GCLK synchronization This is a standard 1.4.0.0 feature which
enables any current generation SITE to be
configured so that it can synchronize its GCLK
to a known good clock source in an uplink
SITE through an E1 link.
68P02901W01-S 4-25
Jul 2008
BSS software release 1.4.0.1 Chapter 4: BSS Software Release Features
Parameter Description
Preserve RCU/SITE calibration Enables all types or versions of a
malfunctioning radio channel unit to be
replaced without the need to remove the Cell
from service, in Cell configurations with two
or more radio channel units.
Indication of flow control invocation Provides a new Cell level statistic,
FLOW_CONTROL_BARRED, which measures
the duration for which channel access to the
cell is unavailable to any access class.
GSM short message service The Motorola BSS supports GSM Short
Message Service - Cell Broadcast (SMS CB).
Mobile subscribers with access to the
short message service are able to receive
alphanumeric information messages at any
time while their Mobile Station (MS) is in
contact with a BSS.
SMS - Cell broadcast: multiple background Enables the BSS to support the SMS Cell
messages broadcast directly for single or multiple (up
to four) alphanumeric information messages
to be sent to any suitably configured MS.
SMS - Cell broadcast center support Supports the use of a third-party SMS Cell
Broadcast Center (CBC) on the Motorola
GSM network. The BSS database and MMI
commands have been modified to support this
feature.
Added nailed connections (optional) Enables non-GSM connections used by
third-party services, such as, a paging
network or analog mobile phone network, to
share the use of the E1 link through a BSS
without the need for external multiplexing
equipment. The existing Timeslot reservation
feature is modified to enable the reserving of
timeslots on E1 link. The RESERVE operation
is currently allowed for MMSs on a PATH only.
Continued
4-26 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.4.0.1 features
68P02901W01-S 4-27
Jul 2008
BSS software release 1.4.0.6 Chapter 4: BSS Software Release Features
Function Description
Software support of M-Cell2/6 GSM for 900 This feature introduces BSS software support
MHz of the core M-Cell hardware, plus MCU, NIU
and TCU support.
Software support of M-Cell2/6 GSM for 1800 This feature introduces support of DCS1800
MHz with both the M-Cell2 and M-Cell6 BTS
hardware platforms.
M-Cell EGSM This feature introduces an EGSM-capable
Transceiver Control Unit (TCU) at 900 MHz.
A TCU combines the Radio Subsystem, DRI,
and DRCU functions into a single package.
TCU backwards compatibility Enables older generation BTSs to operate the
current TCU.
RSS functionality port to carrier equipment This feature provides for the porting of RSS
(TCU) M-Cell and DRI functions to the Transceiver Station
Manager (TSM) board, which resides in the
TCU.
Recovery escalation (M-Cell) A new soft_reset command is available for
M-Cell BTS SITEs only. A soft reset is defined
as a reset where no equipment requires a
code load and the reset switch of no piece
of equipment has been tripped. No object
comparisons or checksums are done at a soft
reset. This fulfils the requirements of the
Recovery escalation (Roadmap ID 31240)
feature.
M-Cell6 remote tuner combiner (900 MHz This feature comprises BSS software support
only) of a Remote Tuning Combiner (RTC) for an
M-Cell6 at 900 MHz only.
M-Cell6 receive matrix (900 MHz only) This feature introduces an Extended GSM
(EGSM)-capable receiver RF matrix, which
supports up to six carriers in a single cabinet.
Continued
4-28 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.4.0.6 features
68P02901W01-S 4-29
Jul 2008
BSS software release 1.4.0.7 Chapter 4: BSS Software Release Features
Feature Description
M-Cellmicro GSM900 Software support for the M-Cellmicro site for
GSM900 operation is provided in this release.
Low power DCS1800 BTS-site M-Cellmicro Software support for the M-Cellmicro site for
DCS1800 operation is provided in this release.
DCS1800 mast mounted preamplifiers An independently powered mast mounted
preamplifier for DCS1800 only. The
preamplifier is manually configured on-site.
Preamplifier power failure and device failure
are reported through a single EAS alarm.
Optional filtering for front end This feature is a receive bandpass filter with
a narrow specification specifically designed
for when ETACS frequency spectrum is used
in conjuncture with a GSM network.
4-30 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release 1.4.1.1
Feature Description
Transient alarm handling Enables the BSS software to perform more
verification and filtering of fault indications,
to eliminate transient alarm messages from
the Transcoder TRAU, the RSL, XBL and clock
failures. The main impact of this feature
is that it decreases the number of alarms
reported by the BSS. This results in less alarm
handling required at the OMC.
Multiple trigger call trace events Enhances existing Call Trace functionality by
providing a finer trigger scope for call trace.
This feature allows triggers to be set on a
Cell level and multiple Cell level. All current
triggering capability is supported on a per
Cell or per BSS level.
BSS level trace events - RF failure (RF loss) Enhances existing RF failure trace
functionality by providing the option to
enable RF loss reporting on a per cell basis
(previously it was BSS level). It also provides
the facility to forward the RF failure trace
information through the event interface to
the OMC.
MSI-2 board with E1 MSI-2 boards can be ordered with E1
interconnections. The software support at the
BSS and OMC is already available to support
this.
Direct retry Redirects new traffic when a Cell is congested
resulting in the new call being moved to the
next most suitable cell.
Congestion relief: directed retry alternative An alternative to Directed Retry for the case
of a congested cell. This feature differs in
that it chooses the best candidates from
all existing calls in the cell to be moved to
the alternate cell, thus freeing TCHs in the
congested cell.
Continued
68P02901W01-S 4-31
Jul 2008
Release 1.4.1.1 features Chapter 4: BSS Software Release Features
Continued
4-32 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.4.1.1 features
68P02901W01-S 4-33
Jul 2008
BSS software release GSR2 Chapter 4: BSS Software Release Features
GSR2 features
Table 4-17 summarizes the features provided in the BSGSM-GSR2 release with OMC/BSS
software support.
Feature Description
GPROC2 Supports the introduction of the GPROC2.
Because of the increased reliability of the
GPROC2 board, there is a decrease in the BSS
unavailability due to unplanned outages. The
error correcting RAM on the GPROC2 board
provides increased reliability.
Cell level/carrier level tracing Enhances the existing Call Trace capabilities
available in the BSS.
Call trace through IMSI Allows a Mobile Station (MS) to be tracked as
it moves across the network.
DCS1800 RTC Supports the DCS1800 M-Cell CCB (Cavity
Combining Block) at M-Cell sites. As a result,
the BSS software is required to modify the
management of remote tuned combiners at
an M-Cell site.
Transcoder Online Expansion Allows the transcoder capacity of equipped
transcoder cards to be increased while online.
The BSS remains available while the equipped
hardware is increased and configured.
This eliminates any site outages during the
expansion.
Type 7 Microcellular Neighbor Cell Adds a Type 7 Microcellular neighbor cell.
Device (SITE/MTL/CBL) Redistribution Provides the capability to redistribute the
SITE, MTL, and CBL devices to different
parent LCF functions. This reassignment is
service affecting.
Continued
4-34 68P02901W01-S
Jul 2008
System Information: GSM Overview GSR2 features
68P02901W01-S 4-35
Jul 2008
BSS software release GSR3 Chapter 4: BSS Software Release Features
GSR3 features
Table 4-18 summarizes the features are provided in the BSGSM-GSR3 release with OMC/BSS
software support.
Feature Description
Concentric Cells Allows the RF resource allocation for a cell to
consist of two frequency channel groups with
a single BCCH frequency to operate in the
same coverage area.
Support for Extended Range Cell Allows the BTS to handle successfully the
uplink transmissions of an MS whose absolute
timing advance exceeds 63-bit periods.
16 kbps XBL Eliminates the requirement for a full E1
timeslot for each XBL.
Non-redundant RTF-PATH Fault Containment Allows a cell to be available for calls even
when all of the paths on which an RTF is
equipped fails, provided there is another
in-service RTF-PATH available for the cell.
Traffic capacity can be increased by removing
any redundant RTF-PATHs and using this
feature to manage RTF-PATH failures. This
also results in a cell not being barred ifthere
is at least one in-service RTF-PATH available
for the cell.
PCS1900 MHz Band (M-Cell2/6) Supports the PCS1900 GSM band 8 Watt
(after first stage of combining) product on
both the M-Cell2 and M-Cell6 BTS hardware
platforms. No remote tuning combining is
supported. This feature is for M-Cell2/6 only
and supports all GSM900/DCS1800 features
except multiband.
Infrastructure Sharing Supports cells of different frequency bands in
a single BTS-site. This feature also supports
the conversion of single band BTS-BTUs and
BCU-BTSs to multiband BTS-sites.
16 kbps RSL for Preserving Timeslots Supports an interface between the BSC and
the BTS-site using a 16 kbps LAPD and the
Motorola proprietary signaling.
Continued
4-36 68P02901W01-S
Jul 2008
System Information: GSM Overview GSR3 features
Continued
68P02901W01-S 4-37
Jul 2008
GSR3 features Chapter 4: BSS Software Release Features
Continued
4-38 68P02901W01-S
Jul 2008
System Information: GSM Overview GSR3 features
68P02901W01-S 4-39
Jul 2008
BSS software release GSR4 Chapter 4: BSS Software Release Features
GSR4 features
Table 4-19 summarizes the hardware/software features provided in the BSGSM-GSR4 release
with OMC/BSS software support.
Feature Description
Call trace expansion Provides enhanced operator features through
the OMC GUI for call tracing.
Carrier prioritization for SDCCH Provides the operator with the flexibility of
prioritizing the selection of Traffic Channels
(TCHs) and Standalone Dedicated Control
Channels (SDCCHs) in order to minimize the
overall interference level in a GSM network.
SMS alphabet extensions Adds three new alphabets to the list of default
alphabets supported by the Short Message
Service feature.
BTS concentration Provides the customer with an alternative
mechanism for allocating terrestrial backhaul
for radio resources between the BSC and
the BTS. This feature preserves the existing
mechanism, but allows the operator the
choice, on a per BTS site basis, of whether
to use the existing mechanism, or the new
dynamic allocation.
M-Cell HDSL interface Introduces a High bit-rate Digital Subscriber
Line (HDSL) interface into the Motorola BSS
product line. HDSL is a data transmission
mechanism which supports duplex high speed
digital communication (at E1 rates) on one or
more unshielded twisted pair lines.
Increased BSC capacity Expands the capacity of a BSC, must be
GPROC2s for all functions at a BSC.
Terrestrial circuit device management Allows the customer to manage terrestrial
circuits in much the same way as other
devices.
Optimized power control Improves uplink and downlink power control.
This is done by adding flexibility in defined
power steps, modifying the range of power
steps, by allowing power step sizes to be
changed dynamically, and by performing
downlink oscillation prevention.
Continued
4-40 68P02901W01-S
Jul 2008
System Information: GSM Overview GSR4 features
The OMC provides the appropriate information to remind the operator that the BSC must be all
GPROC2 boards, before a conventional or CSFP download of release GSR4.
68P02901W01-S 4-41
Jul 2008
BSS software release GSR4.1 Chapter 4: BSS Software Release Features
GSR4.1 features
Table 4-20 summarizes the hardware features provided in the BSGSM-GSR4.1 release with
OMC/BSS software support.
Feature Description
Point-to-point GPRS service. Supports implementation of one to eight
timeslots on a single carrier per cell for the
transmission of GPRS traffic. This enables
the Network Operator to optimally size the
network for efficient support of a mix of GPRS
and voice traffic.
GPRS radio channel allocation. Provides the flexibility for a cell supporting
GPRS to allocate a given radio resource to
handle circuit switched voice/data or packet
data as required. A radio resource can be
configured as dedicated to circuit switched
traffic, packet data traffic, or switchable
between the two.
Medium Access Control modes: fixed/dynamic Includes the functions related to the
allocation. management of the common transmission
resources. These include the packet
data physical channels and the radio link
connections on packet data physical channels.
Support of MS classes. Supports multislot MS classes 1-12, 19 and
20. This includes support of both semi-duplex
(classes 1-12) and half-duplex (classes 19 and
20). Semi-duplex MSs can support up to 4
TimeSlot (TS) downlink and 1 TS uplink, or
2 TS downlink and 2 TS uplink. Half-duplex
MSs, can support 6 TS downlink or 2 TS
uplink, or 1 TS downlink and 4 TS uplink
(fixed allocation MAC mode).
GPRS codes schemes CS-1 and CS-2. Coding schemes CS-1 and CS-2, providing
9.05 kbps, and 13.4 kbps respectively, are
supported.
Dynamic adaption of coding schemes. Enables the network to change the coding
scheme between MS transmissions based
upon the radio characteristics of the link.
Movement between CS-1 and CS-2 is
supported in the initial GPRS release.
Continued
4-42 68P02901W01-S
Jul 2008
System Information: GSM Overview GSR4.1 features
68P02901W01-S 4-43
Jul 2008
BSS software release GSR5 Chapter 4: BSS Software Release Features
GSR5 features
Description
BSC Overload Protection
SMS CB upgrade
Integrated RF loopback on Horizonmacro
Dynamic allocation of RXCDR-BSC circuits
Enhanced XBL
Horizonmicro2/Horizoncompact2 generic BTS software
Code corruption immune design
Propagate TSC changes to all timeslots
Single BCCH for dual band cells
Support for E1 conversion
Enhanced Power Outage Recovery
Improved MTL load balancing
BTS concentration resource optimization for handovers
Handover parameter
Per neighbor area for adaptive handovers
Optimized power control
Support for MTL stat
Support for frame erasure rate statistic
BTS concentration call priority handling
RF head external alarm
GPROC function preemption
Parallel cage enable
Enhanced MMI Link Device Warnings
4-44 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS overload protection
The MSC Overload control feature introduces a mechanism for temporarily reducing traffic
between the MSC and the BSS. This mechanism allows the MSC to notify the BSS that it is
becoming overloaded and the amount of information being sent to the MSC from the BSS should
start to reduce. The BSS receives the notification and starts to reduce the traffic loading on
the MSC immediately. The BSS reduces the traffic load on the MSC by barring mobile access
classes within cells in the BSS. A timer controls the unbarring of the access classes to increase
the traffic to the MSC.
SMS CB upgrade
The short message service (SMS) cell broadcast (CB) attracts subscribers to the network by
broadcasting information of interest to the general public, for example, road conditions, traffic
information, news flashes, weather reports, and so on.
The SMS CB upgrade feature integrates changes made to the ETSI GSM standards and
recommendations since the initial development of the SMS CB features, and provides support
for large SMS CB messages.
Different message categories. Message categories have been introduced. These categories
are defined as High Priority, Background, or Normal. The introduction of different priority
messages affects the scheduling of both the message itself and the DRX scheduling
messages. A new message is supported from the CBC which reserves certain slots for
potential High Priority messages.
CBC configurable DRX period. A configurable DRX message has been introduced. The
DRX message is turned on and off through messages from the CBC. In addition, the CBC
sets the period of the DRX message.
CBC-BSC interface upgrade. The definition of the Repetition-rate parameter has changed.
Support of extended SMS alphabets. ETSI 03.38 provides definitions of the extended
alphabets which can be used for SMS cell broadcast messages. Extended SMS alphabets
defined by the CBC are supported for messages. The extended SMS alphabet is not
supported for SMS cell broadcast messages which are defined through the OMC/customer
MMI.
68P02901W01-S 4-45
Jul 2008
Receive antenna VSWR and radio loopback test Chapter 4: BSS Software Release Features
The Receive Antenna VSWR and Radio Loopback Test feature provides added radio diagnostics
to aid in fault detection in the field. Specifically, this feature provides:
Reduced maintenance costs; through quick and accurate verification of radio serviceability,
and prevention of unnecessary site visits.
Enhanced system operability and reliability; through minimizing operator procedures for
fault management, and enabling standby devices to be tested to detect latent faults.
Receive Antenna VSWR. Horizonmacro supports this diagnostic. Receive Antenna VSWR
testing is first performed by gathering results from the Receive Preamplifier Input
Loopback test. Next, the receive-frequency-translated transmitter output is directed to the
receive antenna and the reflected signal strength is measured. These two sets of results
are used to compute a VSWR measurement.
The dynamic allocation of an RXCDR to the BSC circuits feature introduces fault management
for call traffic on the BSC to RXCDR interface (referred to as the Ater interface) by managing
the individual 16 kbps channels (called Ater channels) on this interface. In addition, this feature
provides for validation of the Circuit Identity Code (CIC) and Ater channel provisioning between
the BSC and RXCDR to ensure that calls are placed on the correct circuit between the BSC and
the MSC. Without this feature in place, no fault management of the Ater channels would be
possible, and all Ater and CIC information must be manually verified by the operator, resulting
in a higher Operation and Maintenance cost for the Motorola BSS.
The dynamic allocation and release of RXCDR to BSC circuits provides the following benefits:
Simplified network provisioning; there is no need to manually map CICs to Ater channels
at both the BSC and RXCDR.
Simplified network debugging; through automatic and manual audits of CIC and Ater
channel information between a BSC and RXCDR.
Better fault tolerance for call traffic, since calls do not necessarily need to be terminated
due to a single failure on the link set between an RXCDR-BSC.
This feature will remain consistent with the Terrestrial Circuit Device Management feature,
with respect to how the operator is permitted to manage the CIC devices.
4-46 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced XBL
Enhanced XBL
The term XBL, refers to a BSC-RXCDR link. The new Enhanced XBL (EXBL) feature improves the
robustness of communication between the BSC and the RXCDR. The basis of this feature is to
provide a generic messaging system between the BSC and the RXCDR. This generic messaging
system is used to suit both current operator needs and the needs of future BSS features.
Operator-visible aspects of the EXBL feature are that runtime checks of database consistency
and connectivity are performed between the BSC and RXCDR to ensure that traffic pathways are
properly configured, and that every E1 link to an RXCDR device, at the BSC has a corresponding
link configured at the appropriate RXCDR. Operators are notified of any failure of these
connectivity checks so that they can take the appropriate action.
In the event of a verification failure, the BSS automatically disables the relevant CIC devices
to ensure that they are not used.
In addition, indications regarding maintenance activity, or faults, occurring at the RXCDR, which
indirectly affect the BSC link devices, are forwarded to the BSC for processing.
There are no new code objects required exclusively for the master Horizonmicro2
BTS, they remain the same as existing Horizonmicro BTS platforms. The 900/1800
Horizonmicro2/Horizoncompact2 feature is implemented by modifying existing code objects.
Dynamic power control is also supported on the Horizonmicro2 and Horizoncompact2 BTSs.
Synthesizer frequency hopping is also available over multiple BTSs in the same cell.
This feature aims to reduce the number of field returns of M-Cell, and Horizon based equipment
due to code corruption. It also maintains backward compatibility with previous hardware and
software loads.
Code corruption usually occurs during field code upgrades and a power outage disturbs the
programming process. In order to reduce the number of equipment returns, modifications have
been made to both software and hardware.
Hardware
Flash (non-volatile memory) is doubled in size. The flash is divided into two banks; the first bank
stores a master copy of the operational code, while the second bank stores the recovery copy.
A hardware switch is required to select either of the banks.
68P02901W01-S 4-47
Jul 2008
Propagate TSC changes to all timeslots Chapter 4: BSS Software Release Features
Software
The software validates the operational code in both banks of flash. If there are no problems,
then the operation of the equipment is allowed to continue. If one of the banks has corrupt
operation code, then a copy of the valid bank is made to immediately overwrite the corrupt bank.
This feature provides more flexibility for automatically updating Training Sequence Codes
(TSCs) of RTFs within a cell when a BSIC is changed. Three options are provided:
Current Implementation - only update TSCs of BCCH/CCCH timeslots.
The Single BCCH for Dual Band Cells feature is an enhancement to the GSR3 multiband feature,
to allow more efficient network operation by enabling a single BCCH carrier to serve GSM900
and DCS1800 cells in the same coverage area.
The Enhanced Power Recovery feature improves system availability in the event of a total
power loss to the site, by providing a non-volatile storage mechanism for BSS Software. This
feature works in conjunction with the present battery back up feature. The non-volatile memory
resides on a new piece of hardware, the Non-Volatile Memory Card (NVM card). This card is
located only at BSC and RXCDR sites.
A background task ensures that the NVM is loaded, and periodically updated, with the same
BSS software objects as the master GPROC board. When powering up after a power loss, the
site will retrieve code from the NVM board, if necessary.
This feature improves the loadsharing of traffic on message transfer links (MTLs) in the
uplink direction from the Base Station System (BSS) to the Mobile Switching Center (MSC).
Loadsharing from the MSC to the BSC is based on the routing function implemented at the MSC
and is beyond the scope of this feature. The granularity of the load distribution is increased
from 16 to 64, resulting in a more even distribution of traffic across the MTLs.
4-48 68P02901W01-S
Jul 2008
System Information: GSM Overview BTS concentration resource optimization for handovers
The implementation of test traffic generation at the BSS for message transfer part (MTP)
Layer 3 testing is modified to support the new loadsharing mechanism. A new MTP Layer
3 test message is added which allows the remote side to determine how the virtual circuits
are distributed over the active MTLs. A database element is added for setting the loadshare
granularity to either 16 or 64.
The BTS Concentration Resource Optimization for Handovers (BCROH) feature optimizes the
terrestrial backhaul between a BSC and BTS during handovers, when the BTS concentration
feature is applied. Previously when a handover occurred, a new circuit for the destination radio
channel was always allocated between the BSC and the BTS. The BCROH feature means that if
the source and destination BTS in a handover are the same, then a new circuit is not allocated
and the existing circuit is reused for the radio destination channel. It can only be used in
conjunction with BTS equipment that supports BTS concentration.
The BCROH feature reduces the number of resources required when intra-cell handovers
or inter cell handovers (within the same site) occur and are controlled by the BSC. In these
handover scenarios the switch connections for the voice traffic from the radio channel to the
MSC are no longer made at the BSC during the handover. The BTS to MSC path remains
constant and the BTS must simply move the switch connection of the Abis circuit from the
source radio channel to the destination radio channel.
Handover parameter
Additionally, this feature converts any test object functionality into MMI commands. Extended
range cell prioritization and the uplink quality value of 7 on a missing measurement report is
supported by CM/MMI commands.
The adaptive handover methodology allows handovers to occur more rapidly when conditions
are deteriorating quickly and less rapidly when conditions are only marginally poor.
This enhancement to adaptive handovers provides the operator with the option of setting the
cumulative area for adaptive power budget handovers on a per cell or per neighbor basis.
This enhancement to the existing optimized power control feature, allows the operator to enable
a power control algorithm that allows RXLEV based power reductions. Calculations are made
for both uplink and downlink power control.
68P02901W01-S 4-49
Jul 2008
Support for the MTL statistics Chapter 4: BSS Software Release Features
Dynamic power reduction is used in the event of the RXLEV exceeding the upper level threshold.
If the algorithm is enabled, power level reduction step sizes can be changed dynamically,
based on the current proximity to the upper power level threshold. This will allow the power
to be brought down at a faster rate when it has strayed out of the power box. The dynamic
power reduction feature is enabled in addition to the good quality, poor quality, and low-level
adjustments. These three adjustments may also be chosen without the high-level adjustment
provided by this feature.
The weighted distribution statistics produce a mean value indicating the average number of
circuit identity codes (CICs) in use during a statistic interval.
This feature implements frame erasure rate (FER) and residual bit error rate (RBER) statistics
at the BSS.
Meaningful call quality metrics for hopping network benchmarking and health reporting.
The BCCPH feature enables the BSS to prioritize the order in which non-emergency circuit
switched calls are preempted by emergency calls.
This feature preempts circuit switched calls based on priority as well as age. The BSS
attempts to preempt a non-emergency circuit switch call with the lowest priority first and a
non-emergency circuit switch call with the highest priority last. If two calls exist with the same
priority level then the oldest is chosen first.
This feature searches for a Busy-Unlocked generic processor board (GPROC) running a lower
priority function, when a GPROC hosting a higher priority function goes out of service, and
there are no Enabled-Unlocked GPROCs to host the higher priority function. If such a GPROC is
found, the lower priority function is preempted by the higher priority function. The operator is
able to configure the preemption algorithm using a database element.
4-50 68P02901W01-S
Jul 2008
System Information: GSM Overview Parallel cage enable
Intra function level preemption: If a function of lower priority is running on a GPROC, that
function is preempted. If a GPROC running the LCF goes out of service and there is no
lower priority function type (for example, BTF) running on a pool GPROC, the function
tables are searched for a lower priority LCF to preempt.
CAGEs at an InCell multi-cage site were previously brought into service serially. This feature
brings the CAGEs at InCell BSCs and RXCDRs into service in parallel. Cages at an InCell BTS
site is brought into service in parallel when the master BTP is a GPROC2.
Cages at an InCell BTS site will continue to be brought into service serially when the master
BTP is a GPROC1.
MMI issues confirmation warnings when the operator uses the lock, ins_device, or reset_device
commands on some link devices. Additionally, in some cases, MMI issues confirmation warnings
when the MSI, MMS, or DPROC is locked and it has an associated link device.
The Enhanced MMI Link Device Warnings feature addresses a number of problems that existed
with the MMI link device warnings. The previous link warnings have been replaced with a
new, comprehensive set of warnings.
MMI issues a warning message and prompt for confirmation whenever the lock, ins_device,
or reset_device commands are used on a parent device that supports link devices.
MMI issues confirmation warnings for link devices regardless of their current state.
The warnings that MMI issues for link devices define the link affected and the
consequences of locking the link device.
The warning that MMI issues for a particular link device is the same for all of the MMI
state change commands.
68P02901W01-S 4-51
Jul 2008
BSS software release GSR5.1 Chapter 4: BSS Software Release Features
GSR5.1 features
Description
BSS processing of suspend message
CS3, CS4, and 32 kbps TRAU
GPROC fast reset
Unequip TCU/CTU cabinet
850 MHz frequency range
1900 MHz Horizon
Single BCCH for dual band cells
Feature overview
Previously, the BSS did not process the suspend message received from the mobile. As stated
in GSM 04.08, the BSS needs to process this message and to communicate it to the Serving
GPRS Support Node (SGSN) (GSM 08.18). This feature enables the BSS to communicate the
suspend message to the SGSN.
Feature description
When a GPRS attached MS enters CS dedicated mode to answer a CS page, and MS limitations
make it unable to continue to communicate for GPRS, the MS will request to suspend GPRS
services. The BSS processes this message from the mobile to suspend its GPRS service and sends
a suspend message to the SGSN through a Gb link (interface between an SGSN and a BSC).
The SGSN, in turn, does not initiate any paging for this mobile while it's in the suspend state.
When the mobile switches from the CS dedicated mode back to the GPRS mode, it sends a
routing area update message asking the SGSN to resume the data transfers.
4-52 68P02901W01-S
Jul 2008
System Information: GSM Overview CS3, CS4, and 32 kbps TRAU
Feature overview
The GPRS Coding Scheme 3, Coding Scheme 4 (CS3/CS4) and 32 kbps Transcoder Rate
Adaption Unit (TRAU) feature implements an alternative channel coding algorithm over the air
which enables increased data rates to GPRS mobile stations.
Software changes
The BSS and PCU changes necessary to implement Coding Scheme 3 and Coding Scheme 4
are software changes. There are no hardware modifications or additions necessary to support
this feature.
The BSS supports 32 kbps TRAU channels that are comprised of two independently synchronized
16 kbps TRAU channels. Both component 16 kbps TRAU channels of any given 32 kbps TRAU
channel reside on a single GDS to ensure that a single TRAU processing entity can handle
the reassembly of the individual channels.
CM database parameters
Additionally, two new CM database parameters are necessary to control whether the CS3,
CS4, and 32 kbps TRAU is allowed in the BSS. If CS3, CS4, and 32 kbps TRAU is allowed in
the BSS, then cs34_enabled must be enabled. To support the feature on a per carrier basis,
every timeslot dedicated to GPRS must have sufficient backhaul present to support the 32
kbps TRAU. This is enabled by a per carrier parameter as part of the equip_rtf command
called allow_32k_trau.
New statistic
Dynamic allocation
The use of the dynamic allocation feature in conjunction with the CS3, CS4, and 32 kbps TRAU
feature is not supported at this time. In a network at sites using dynamic allocation, the CS3,
CS4, and 32 kbps TRAU feature is not allowed.
Restrictions
Every firmware platform that currently supports GPRS supports CS3, CS4, and 32 kbps TRAU,
consequently no additional restrictions need be placed on the carriers or RTF equipage due
to this feature.
68P02901W01-S 4-53
Jul 2008
GPROC fast reset Chapter 4: BSS Software Release Features
Feature overview
The Fast Reset (Soft Reset) feature enables a GPROC to come back into service quicker, when
recovering from a fatal Software Fault Management (SWFM). If the GPROC is functioning as
the master BSP/BTP, then the fast reset feature has the effect of bringing the site into service
sooner. This feature reduces the outage time for the involved GPROC(s) and increases the
total availability of the site.
Feature description
The fast reset feature decreases the recovery time for a reset by having the GPROCs transition
software from RAM back to RAM during a reset, without going through the ROM process. The
differences between a RAM-RAM software transition and a RAM-ROM software transition is that
the RAM-RAM procedure does not execute the functionality in ROM, as it is passed over.
During a RAM-RAM software transition, the GPROC that incurred the fatal SWFM is taken off
the LAN and all TDM connections for that GPROC are cleared. Then, instead of performing
a software transition to ROM, the GPROC comes back on the LAN in RAM and performs the
RAM initialization procedure.
The theory behind the fast reset feature is that a process executing in RAM, which encounters
a bus fault or any other fatal SWFM event, does not need to go through the ROM transition
to restore the GPROC. By halting all processes on that GPROC and reinitializing it, the fault
generating condition should no longer exist. If the fatal SWFM condition still exists, an
escalation mechanism eventually transitions (points) the GPROC software into ROM.
This feature enables the unequipage of extension cabinets of types TCU_2, TCU_6, and
Horizonmacro_ext at M-Cell, and Horizonmacro sites without having to unequip the site. This
action can be done, if the cabinet is locked and there are no DRIs or EASs equipped to the
cabinet. All other cabinet types are not supported by this feature.
Provides software support for a BSS to operate in the 850 MHz frequency range using features
already introduced in prior releases.
Provides software support for a BSS to operate in the 1900 MHz frequency range using features
already introduced in prior releases.
4-54 68P02901W01-S
Jul 2008
System Information: GSM Overview Single BCCH for dual band cells
The Single BCCH for Dual Band Cells feature is an enhancement to the GSR3 multiband feature,
to allow more efficient network operation by enabling a single BCCH carrier to serve GSM900
and DCS1800 carriers in the same coverage area.
The main impacts of the Single BCCH for dual band cells feature are as follows:
Support of two different frequency bands within a single cell, using a concentric cells
configuration.
The operator can define the coverage area of the secondary band by use of BSS database
parameters.
Power level conversions are provided for intra-cell channel changes and incoming inter-cell
handover between channels on different frequency bands.
Other optional features that must be unrestricted in order to configure dual band cells are:
Multiband handover - Refer Multiband inter-cell handover in BSS software release
GSR3 on page 4-36.
Concentric cells - Refer Concentric cells in the BSS software release GSR3 on page
4-36 section.
Dual band cells - Refer BCCH frequency, SDCCH in EGSM in the BSS software release
GSR6 on page 4-56 section.
The functions of these features on which the Single BCCH for dual band cells is dependent
are described in this manual. A technical description of the Single BCCH for dual band
cells feature, and these features are contained in the manual Technical Description: BSS
Implementation (68P02901W36).
Homogeneous cabinet - Refer the equip CAB command in the manual Technical Description:
BSS Command Reference (68P02901W23).
Heterogeneous cabinet (for combined cabinet configurations) - Refer the equip CAB command
in the manual Technical Description: BSS Command Reference (68P02901W23).
68P02901W01-S 4-55
Jul 2008
BSS software release GSR6 Chapter 4: BSS Software Release Features
GSR6 features
Description
Enhanced Circuit Error Rate Monitor
Multiple GPRS carriers per cell
Enhanced GDP provisioning
Call downgrade on CIC capability mismatch
GPRS PCU recovery on last GSL failure
Network controlled cell reselection
Location Services (LCS)
Basic MPROC redundancy
Enhanced BSC capacity phase 2
Improved MPROC SW failures detection and recovery
Clean Install (E3x00)
Inter Radio Access Technology (RAT) 2G to 3G handover
GPRS interleaving TBFs
Link utilization improvements
Advanced load management for EGSM carriers
Enhanced GPRS One Phase Access
Remove support for collocated BSC
Compress all BTS objects at the BSC
4-56 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced circuit error rate monitor
Feature overview
The original Circuit Error Rate Monitor (CERM) optional feature provides a means for
identifying when discontinuity is detected on a circuit. The customer can:
Reduce cost of ownership.
A circuit is considered to be the path along which a connection is made, from the entry point in
the BSS (for example, a radio at the BTS) to the exit point in the BSS (for example, the MMS
timeslot that connects to the MSC or PCU).
The CERM is used to monitor the continuity and sanity of hardware processing elements in a
circuit, on a per call basis. Whenever a discontinuity is detected for a circuit during a call, error
counts are updated for the points monitored for the call. When the error count at a particular
monitoring point reaches or exceed an operator specified threshold, an alarm is generated. The
alarm contains information identifying the monitored path in which the error is detected, thus
allowing the operator to identify potentially faulty devices.
Feature description
The CERM feature is enhanced, enabling the monitoring at various points in a GSM network
circuit, thus improving the ability of an operator to narrow down where a faulty device is
located. Although having these monitoring points in the circuit path narrows down the list of
potentially faulty devices, it does not confirm that a device is faulty. It is still up to the operator
to determine which device is faulty.
ATER Channel Identifier (ACI) groups on a link between the RXCDR and the BSC.
Path Identity Code (PIC) on a link between the BSC and a BTS.
The PIC is a special case because it is measured on a from-BSC-to-site basis. So, for example,
with a path leading from a BSC to two daisy chained BTSs, the PIC for the second BTS
encompasses the path through the first BTS to the BSC.
68P02901W01-S 4-57
Jul 2008
Multiple GPRS carriers per Cell Chapter 4: BSS Software Release Features
Feature overview
Before GSR6, the Motorola GPRS product offered the capability to configure up to eight GPRS
TimeSlots (TSs) on a single carrier in a cell. The increase in packet data traffic and availability
of multiple timeslot GPRS MSs have increased the need for additional GPRS capacity.
The Multiple GPRS carrier feature enables the network operator to configure multiple GPRS
carriers per cell for increased GPRS traffic handling capability to meet this increase in packet
data traffic and the expanding base of GPRS subscribers with increased data throughput.
The operator is offered two options to configure GPRS TSs on multiple GPRS carriers per cell:
Configure for performance
Operator specified
Configuration performance
Configure for performance provides the network the capability to configure all the reserved
and switchable GPRS timeslots in a cell contiguously to maximize performance. The contiguous
GPRS TSs configured on a carrier in a cell provide ease in scheduling packet data and the
capability to service multiple TS GPRS mobiles.
Table 4-24 is an example of multiple GPRS carriers where the default option, configured for
performance, is specified. The GPRS resources are configured contiguously on GPRS carriers
in the cell to maximize performance. The cell has five GPRS carriers, ten reserved TSs, and
eleven Switchable TSs.
TS 0 TS 1 TS 2 TS 3 TS 4 TS 5 TS 6 TS 7
BCCH SDCCH RES RES RES RES RES RES
SW SW SW SW RES RES RES RES
TCH SW SW SW SW SW SW SW
TCH TCH TCH TCH TCH TCH TCH TCH
TCH TCH TCH TCH TCH TCH TCH TCH
Operator specified
The operator specified option provides customers with the flexibility to configure the maximum
and minimum number of reserve and switchable GPRS timeslots on a per carrier basis in a
cell. Table 4-25 is an example of GPRS timeslots distributed over carriers in the cell. The
cell has five GPRS carriers, ten reserved timeslots, and eleven switchable timeslots. The
max_gprs_ts_per_carrier element is set to 6.
4-58 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced GDP provisioning
TS 0 TS 1 TS 2 TS 3 TS 4 TS 5 TS 6 TS 7
BCCH SDCCH RES RES RES RES RES RES
TCH TCH SW SW RES RES RES RES
TCH TCH SW SW SW SW SW SW
TCH TCH TCH TCH TCH SW SW SW
TCH TCH TCH TCH TCH TCH TCH TCH
When a carrier that has GPRS timeslots goes out of service, GPRS timeslots are reconfigured on
a different carrier that supports GPRS based on the radio resources available in the cell.
Feature overview
Enhanced GDP provisioning is an enabler for future features which require a reduction in
board channel capacity for example, AMR.
Types of transcoding
A user can select the type of transcoding used by a GDP. The transcoding types are:
Basic - Transcoding for GSM Full Rate speech, Enhanced Full Rate speech and phase 2
data services.
Enhanced - Transcoding for future applications, particularly Adaptive Multi Rate (AMR)
speech coding, in addition to existing GSM Full Rate speech, Enhanced Full Rate speech
and phase 2 data services.
Allows GDPs to provide additional enhanced transcoding resources only without making
use of the E1 line interfaces.
68P02901W01-S 4-59
Jul 2008
Call downgrade on CIC capability mismatch Chapter 4: BSS Software Release Features
Feature description
A Secondary GSD in a pair provides DSPs for transcoding for a set of CIC devices routed
to the MSC through the E1 interface of a Primary GDP. Secondary GDP can provide
Enhanced transcoding only.
Supports provisioning for GDPs to provide additional enhanced transcoding resources only,
without making use of their E1 link line interface.
For Enhanced GDP Provisioning to be used for new transcoding applications, the following
feature must also be implemented:
The related MMS must exist before specifying it as the MSC MMS for a secondary GDP or, if the
MSC MMS is the GDP's own MMS, it is equipped (automatically). A GDP can only provide the
MSC MMS for one secondary GDP.
Feature overview
The call downgrade on CIC capability mismatch feature resolves erroneous call handling that
could cause loss of speech due to the requested speech version not matching the capabilities of
the underlying transcoding equipment.
This feature also enhances the support of the Generic DSP Processing board, adding Enhance
Full Rate capability as well as allowing a staged migration to future advanced transcoding
technologies such as AMR.
4-60 68P02901W01-S
Jul 2008
System Information: GSM Overview Call downgrade on CIC capability mismatch
Feature description
The Generic DSP Processor (GDP) board was introduced into the BSS and RXCDRs to support
EFR speech as the previous transcoder, the XCDR was not re-programmable and could only
support Full Rate (FR) speech and ETSI Phase 2 Data Services.
Previously, Motorola mandated that for EFR to be provided, all transcoders must be GDPs.
With local transcoding, this was easily enforced by not enabling EFR if XCDR boards were
fitted at the BSC. However, for remote transcoding, because no specific signaling in terms of
capabilities existed between the BSC and RXCDR, EFR could be enabled at the BSC even
though the RXCDR contained XCDRs.
Pooled transcoding at the MSC and the RXCDR was introduced to support this co-existence of
XCDRs and GDP within the BSS. EFR capable CICs terminating on GDP boards, FR capable CICs
terminating on XCDR boards with data services being supported by both types of transcoder.
This configuration is satisfactory provided the pool of transcoders at the RXCDR match that
of the MSC. However, if mismatches do occur, EFR calls could be routed to XCDR boards,
resulting in calls with no speech.
Call downgrade on CIC capability mismatch resolves this problem by allowing the co-existence
of differing capability platforms, which match the capabilities of the underlying hardware with
those for incoming call requests. These are:
Calls specifying a preference for EFR, but also allowing the use of GSM FR, would use EFR
when utilizing a CIC supported by a GDP board.
Calls specifying a preference for EFR, but also allowing the use of GSM FR, would use
GSM FR when utilizing a CIC supported by an XCDR board.
Until the inclusion of AMR capable hardware is available, requests for AMR would be
targeted to match the capabilities of the associated CIC or supporting hardware and use
either GSM FR or EFR.
It also enhances the capability of the Generic DSP Processing board by adding EFR and allowing
a staged migration to AMR.
Support of transcoding platforms with different capabilities within the BSS, to allow the
XCDR and GDP boards to co-exist within the same BSC (in the case of local transcoding) or
RXCDR (in the case of remote transcoding).
Detection of CIC speech version capabilities by the BSS, based on the supporting
transcoding platform.
Validation of MSC call setup, in-call modification, and handover requests to ensure that the
given permitted speech version(s) included are supported by the specified CIC.
68P02901W01-S 4-61
Jul 2008
GPRS PCU recovery on last GSL failure Chapter 4: BSS Software Release Features
The GPRS Signaling Link (GSL) is a control link between the Base Station Controller (BSC) and
the Packet Control Unit (PCU). It is a required resource for providing the packet data services
as well as for operation and maintenance of the PCU. Previously, if all the GSL links went out
of service, the PCU reset itself to simplify the releasing and rebuilding of the resources in the
data services.
A problem with the previous design was that once the PCU reset itself, it took unnecessary
time to re-establish the link between the BSC and PCU and then to bring back the PCU into
service in order to process data calls again.
NOTE
If no GSL connection is made within 30 minutes the PCU will go into RAM mode reset.
At the first GSL restoration, the first GSL IN Service (INS) procedure will not be
started until the last GSL Out Of Service (OOS) procedures are completed. This
protects the BSC and PCU from unstable GSLs.
This feature enhances the availability of the PCU by preventing the PCU from resetting upon the
last GSL disconnection and quickly brings it up in service again upon the GSL reconnection.
When the last GSL goes out of service, the system software in the PCU and BSC now manages
and reconfigures the network resources promptly, smoothly deallocating the resources for data
calls and reallocating them for voice calls.
This feature also improves the problem analysis of the PCU because the processes on the PCU
stay up and continue to run during the last GSL failure allowing the operator to interrogate
the processes for problem analysis, locally.
Feature overview
In a GPRS network, cell reselection is equivalent of a GSM circuit switched handover triggered
by, for example:
change in location of the mobile.
change in RF conditions.
cell congestion.
GPRS cell reselection offers mobility and performs network traffic management. The different
modes of cell reselection in GPRS network are referred as NC0, NC1, NC2, and RESET. In the
initial Motorola GPRS product offering, NC0 was provided. In cell reselection mode NC0, the
mobile performs autonomous cell reselection based upon on the radio environment. This feature
release provides the remaining two modes of cell reselection NC1 and NC2 to enhance the
existing product offering. Table 4-26 shows the different cell reselection modes, responsible
network element, and functionality.
4-62 68P02901W01-S
Jul 2008
System Information: GSM Overview Network Controlled (NC1 and NC2) cell reselection
Feature description
In the current Motorola GPRS network, the MS autonomously performs cell reselection based
solely on the RF measurements of the serving and neighboring cells. The GPRS MS is unable
to reselect to a neighbor cell based on important factors: such as congestion, availability of
GPRS, ability to support mobiles and current grade of service.
The main objective of the network controlled cell reselection and congestion relief feature is to
increase network capacity and to provide the network operator with a tool for network planning
and improved quality of service. The operator is able to specify GPRS cell reselection mode
on a per cell basis, within the network of cells with the same cell reselection command, thus
providing the flexibility of virtual zones. A significant portion of this feature incorporates the
addition or modification of statistics that reflect radio conditions at the MS and congestion in
the GPRS network. Benefits of statistics collection are as follows:
Provide network information to change cell reselection mode on a per MS basis.
Provide network planning information and configuration of NC2 mode parameter. In cell
reselection mode, NC2 enables the BSS to take appropriate action to reduce congestion if
the originating cell is congested.
68P02901W01-S 4-63
Jul 2008
Location services Chapter 4: BSS Software Release Features
Location services
The Location Services (LCS) feature implements emergency services functionality in GSM
systems (compliant with the Federal Communications Commission (FCC) 911 requirements)
in two phases:
Phase To transmit the originating number of an emergency call (911 in the United States)
1 and the location of the serving site to the Public Safety Answering Point (PSAP).
Phase To transmit the emergency caller's estimated position, expressed in latitude and
2 longitude co-ordinates within specified limits of accuracy.
Applications that request location estimates from location services can be located in the MS, the
network, or externally to the PLMN.
LCS currently specifies three positioning mechanisms in order to determine the location of a
Mobile Station. These positioning processes involve two main steps: signal measurement
and position computation based on the measured signals. The standard SMG (Special Mobile
Group) positioning mechanisms are:
Network-based uplink Time of Arrival (TOA)
Conventional GSM Timing Advance (TA) measurements can also be used in conjunction with
Cell ID determination to provide a coarser, lower quality location estimate.
Examples of applications to which LCS MS position determination can be applied are to deliver
tailored content to MSs in a physical locality (location-specific advertising), or to determine the
routing of voice traffic (location sensitive routing). Motorola supports Timing Advance (TA),
Enhanced Observed Time Difference (E-OTD) and Assisted GPS (A-GPS) positioning mechanisms.
The Timing Advance (TA) positioning mechanism is based on the existing GSM timing advance
measurements, the frequency of sending of which is specified by the timing_advance_period
parameter. The timing advance value is known for the serving BTS and when returned to the
requesting LCS client, with the cell ID, provides the approximate physical position of the MS.
4-64 68P02901W01-S
Jul 2008
System Information: GSM Overview Basic MPROC redundancy
Feature overview
The purpose of the complete Master Processor (MPROC) redundancy feature is to support a 2N
redundancy scheme for the MPROC hardware within the Packet Control Unit (PCU) platform.
NOTE
2N Redundancy is also called pair redundant. Essentially, it means that there is
twice the amount of hardware than there would be for a non-redundant system. One
unit is active while the other is waiting in standby mode should the first unit fail.
In this scheme, one MPROC board serves as the active controller for the Packet Control Unit
(PCU) with a second MPROC board waiting in standby mode. Should the active board fail or
go out of service for some reason, the standby MPROC automatically takes over control of the
cage and continue normal system operation.
NOTE
MPROC failure results in a PCU cage reset until the reserve MPROC assumes control.
In addition to supporting the redundant hardware, this feature focuses on providing a fast
recovery from failures of the active MPROC. In the worst case, the PCU should make a complete
recovery within three to five minutes of the failure.
Feature description
This particular feature supports two MPROC boards within the PCU cage and provides for
an automatic switchover to the redundant board, should the active board fail. The following
benefits are provided by this feature:
Hardware-level failure of the MPROC board
Should such a failure occur, and a redundant MPROC is not available, the PCU remains out
of service until field personnel are able to perform an on-site replacement of the faulty
board. Once the board is replaced, the PCU will remain out of service until all code and
database objects are downloaded from the BSC. By having a redundant MPROC in place,
the PCU is able to remain in service until the on-site replacement can be made.
68P02901W01-S 4-65
Jul 2008
Enhanced BSC capacity phase 2 Chapter 4: BSS Software Release Features
The redundant hardware constantly monitors the other MPROC board. When the
redundant board detects that the active board is no longer in charge of the PCU cage, the
redundant assumes that the other board has failed and, therefore, take over ownership of
the cage (and re-initialize the PCU accordingly). Although the assumption made by the
redundant board is incorrect, the operation of the PCU will not be adversely affected, the
only consequence is a longer recovery time than would be necessary under ideal conditions.
While this feature is not introducing ideal recovery times, this feature is able to recover
from MPROC software faults faster than if redundant hardware were not present. This
improvement is possible because the PCU is in recovery as soon as the active board fails.
Without this feature, the PCU would not be able to begin recovery until the failed MPROC
finished resetting.
Feature overview
This feature increases the number of carriers to 512 and the number of Circuit Identity Codes
(CICs) to 3200.
The BSS supports the standard database configuration for 2400 CICs if the enhanced
BSC capacity feature is restricted.
The BSS supports the enhanced database configuration for 512 carriers if the enhanced
BSC capacity feature is not restricted.
The BSS supports the enhanced database configuration for 3200 CICs if the enhanced BSC
capacity feature is not restricted.
To increase the number of CICs to 3200, 27 BSC-RXCDR connectivities are required at the user
interface, as each connectivity is equivalent to a physical MMS port/2.04 Mbps link capable of
supporting 120 traffic channels, as follows:
20 x 120 = 2400.
27 x 120 = 3200.
Because of this, the BSC-RXCDR connectivity table at the BSS needs to be increased from
21 to 27 entries.
4-66 68P02901W01-S
Jul 2008
System Information: GSM Overview Improved MPROC software failures detection and recovery
Feature overview
To improve recovery time for extreme software failures, the MPROC board implements a
watchdog timer. A low-level software process on the board resets the timer on a regular basis to
keep it from expiring. If this process is impeded for some reason (for example, the processing is
locked-up on some other task) the timer expires.
Should a watchdog timer expire, an interrupt is generated to low-level software which then
attempts to collect information about the current task, stores its registers or stack in compact
Flash memory, and then immediately resets the board. Upon subsequent initialization of the
board, the software reads the compact flash memory and if any watchdog reset information is
stored, prints that information out to the internal Executive Monitor (EMON) program.
Feature overview
This GSM feature supports handovers between different Radio Access Technology (RAT)
networks in the Circuit Switched (CS) domain. The RAT can be either 3G Universal Mobile
Telecommunication System (UMTS) or 2G GSM.
Feature description
Current evolving 3G UMTS networks soon will allow operators to provide UMTS coverage along
with GSM/GPRS coverage in their networks.
This feature enables a multi-RAT Mobile Station (MS), a mobile station that can function in
multiple Radio Access Networks (RAN) to hand over calls between a GSM Radio Access Network
(RAN) and a 3G UMTS Radio Access Network (UTRAN). To accomplish this, support is needed
from the MS, Core Network elements of the MSC and UMTS/GSM network elements.
Being a completely new GSM function, a full description is available in the Technical Description:
BSS Implementation (68P02901W36) manual.
68P02901W01-S 4-67
Jul 2008
Clean install Chapter 4: BSS Software Release Features
Clean install
Feature overview
The purpose of this feature is to install the OMC-R on a SunFire 4800/4900 server. As Sun are
making their current Solaris system obsolete, from 2001 only Solaris 10 is shipped. Therefore,
the Operation and Maintenance Center-Radio (OMC-R) has its operating system upgraded.
Feature description
This feature installs the OMC-R on a SunFire 4800/4900 server. As part of the clean install,
OMC-R customers are using the Solaris 10 operating system.
For customers upgrading from a previous OMC-R release, a procedure to upgrade from Solaris
2.51 to Solaris 10 is included in the OMC-R Upgrade.
Feature overview
This release is an extension to the software feature which introduced the General Packet Radio
Service (GPRS).
The Interleaving Temporary Block Flow (TBF) feature allows the rapid multiplexing of Radio
Signaling Link (RLC) data blocks of many different MSs onto a common air resource. Multiple
MSs are then able to share a common air resource although effective throughput of each MS on
that shared resource is decreased.
Feature description
Each MS sharing a common air resource is given a certain percentage of the shared resource
bandwidth. For example, if two MSs are interleaved on the same air timeslot, one MS is given
70% of the timeslot, while the second MS is given the remaining 30% of the timeslot. This
is illustrated in Figure 4-1.
4-68 68P02901W01-S
Jul 2008
System Information: GSM Overview GPRS interleaving TBFs
MOBILE A
MOBILE B
ti-GSM-Interleaving DL TBFs-00092-ai-sw
This interleaving increases the number of users that can be on a single timeslot, increasing the
overall capacity of a serving cell.
Interleaving TBFs in the uplink and downlink direction use block-by-block multiplexing, in which
two or more MSs are multiplexed on a timeslot with the capability of switching between MSs
every block period.
All of the MSs on a timeslot are all simultaneously active in TBFs. The TBF setup phase, TBF
release phase, or data transfer phase of one MS TBF may overlap with the TBF setup phase,
TBF release phase, or data transfer phase of other TBFs belonging to other MSs.
68P02901W01-S 4-69
Jul 2008
Link utilization improvements Chapter 4: BSS Software Release Features
NOTE
Delayed release of downlink TBF is sometimes known as Supercoattail.
The delayed release of downlink TBF extends the downlink Temporary Block Flow (TBF) period
by 4.5 seconds by transmitting dummy Logical Link Control (LLC) frames. By delaying the
downlink TBF release, there is no need to send a new Packet Downlink Assignment (PDA),
allowing data to be sent straight away in the next block period. It also means that if the MS
uplink needs to be established while being polled during the extended downlink TBF period, the
CCCH and RACH do not have to be accessed, and a channel request in the DAK message is sent
instead, reducing the UL TBF establishment time by 500 ms.
Before the dummy LLC frames are sent, all previous LLCs are acknowledged by the MS. If no
meaningful data is sent by the MS on the PD channel for 4.5 seconds, interference to other MSs
transferring data can be caused. To reduce this interference, the CS1 data blocks corresponding
to the dummy LLCs are only sent on the Packet Associated Control Channel (PACCH) timeslot
when the MS needs to be polled.
Feature overview
Previously, within the BSS software, the signaling messages exchanged between the Radio
subsystem (RSS) and Packet Resource Manager (PRM) processes, over the Radio Signaling Link
(RSL) and the GPRS Signaling Link (GSL), had a large header compared with the data part
of the message and consequently this produced a transmission delay. In addition, the BSS
software sent one message per Link Access Procedure for ISDN D-Channel (LAPD) frame on
the RSL and GSL links; this did not fully utilize the maximum size of the LAPD Unnumbered
Information (UI) frame.
This feature improves the performance of the RSL/GSL links and alleviates the expected
pressure on the capacity and speed of the links from the expanded capacity and high speed
GPRS features. The link utilization improvements feature reduces the message transmission
time between the BTS and PCU for the InCell, Horizonmacro and Horizonmicro/Horizoncompact
by 35% to 40%, 20% to 35% and 15% to 30% respectively. The number of GPRS timeslots that
the RSL can support should be increased by 40% in most GPRS BTS configurations.
4-70 68P02901W01-S
Jul 2008
System Information: GSM Overview Advanced load management for EGSM carriers
Feature description
The link utilization improvements feature addresses the above issues to speed up messages
exchanged between the RSS and PRM. The following enhancements have been made:
Smaller header for delivering messages between the RSS and PRM.
The new message header is eight bytes and contains minimum information necessary to
deliver the messages between the two processes. The functionality of the existing routing
functions will not change and a new set of routing methods and Application Programmer
Interfaces (APIs) are created for the application processes to use.
This improves both speed and utilization of the RSL/GSL links by packing more than one
signaling messages into the same LAPD frame thus reducing the LAPD header overhead.
Messages waiting in the RSL/GSL mailboxes are packed in one LAPD frame before writing
it to the link, and it is unpacked when it is read from the link.
The feature creates a high priority mailbox call LUI mailbox in the Executive Data Link
Service Process (Exec DLSP) for certain high priority messages between the RSS and PRM.
This mailbox is created at both the BTS and PCU. This enables processing of messages in
the LUI mailbox at a higher priority than messages in all other RSL/GSL mailboxes.
The RSS and PRM uses the small header with high priority for only certain high priority
messages. The messages sent with this option are routed to the LUI mailbox and all other
messages between the RSS and PRM (using the small header/normal header) are sent to the
RSL/GSL mailboxes. With this feature, the RSS and PRM can send and receive the following
messages:
Messages with normal headers, which go to RSL/GSL mailboxes.
High priority messages with small headers, which go to the high priority LUI mailbox.
Normal priority messages with small headers, which go to the RSL/GSL mailbox.
The advanced load handover management function offers the operator the ability to specify
EGSM band handovers only to other EGSM bands. Otherwise EGSM handovers can occur
to neighboring cells that may not have an EGSM band available. DCS1800 bands is used
wastefully, particularly if the band_preference parameter is set, for example, to DCS1800. A
new parameter bss_egsm_alm_allowed enables the feature and EGSM handovers will occur to
EGSM sites if available, whatever the setting of band_preference.
When a handover is triggered with this feature set, the neighbor list of an EGSM MS on an
EGSM resource is manipulated such that EGSM internal neighbor cells are given preference
over non-EGSM neighbor cells.
68P02901W01-S 4-71
Jul 2008
Enhanced GPRS One Phase Access Chapter 4: BSS Software Release Features
Feature overview
This feature enables Enhanced General Packet Radio Service (GPRS) One Phase Access with the
Packet Control Unit (PCU) at the Base Station Controller (BSC) (Pre-load).
In a GPRS network, there are two packet access procedures that the mobile can use to establish
an uplink TBF. The packet access can be done in either one phase or in two phases. In the
current GPRS software architecture, the Base Station System (BSS) only supports the two-phase
access procedure. The intent of this feature is to introduce the one phase procedure, as well as
improvements to both procedures.
Enhanced GPRS One phase uplink TBF access is an improvement over the two-phase uplink TBF
access procedure. In a one phase uplink TBF access, the MS initiates an uplink TBF by sending
a Random Access Channel (RACH) to the BSS. The RACH is received at the BTS, which is then
forwarded to the PCU. The PCU responds to the RACH with an Immediate Assignment message
containing an uplink assignment. The MS moves to the assigned Packet Data (Traffic) Channel
(PDTCH) and begins its uplink data transfer. This procedure allows the MS to gain access to the
network much quicker when compared to the Two-Phase establishment procedure.
Refer to Technical Description: BSS Implementation (68P02901W36) for a full description of the
differences between the two access methods.
Feature overview
Support for the collocated InCell/BSC is disabled in GSR6 to enable compressed BTS objects to
be stored at the BSC in order to free up memory for new GSM and GPRS features.
A collocated InCell/BSC site will not be able to continue to operate in GSR6 release.
This feature enables all BTS objects to be stored in compressed form at the BSC in order to free
up memory for new GSM and GPRS features.
Support for the collocated InCell/BSC is disabled by blocking access to key commands to
prevent equipage of a collocated BSC.
All collocated BSCs should remain at pre-1650 release, while remainder of network is
upgraded to 1650.
4-72 68P02901W01-S
Jul 2008
System Information: GSM Overview Compress all BTS objects at the BSC
Feature overview
This feature is designed to save memory at the BSC by compressing all BTS objects at the
BSC and uncompressing them at the BTS. In addition, it speeds up OMC to BSC and BSC to
BTS download times.
All non-BSC objects (Incell BTS, M-Cell, and so on) are compressed as part of the object build
and are stored in compressed form at the BSC to save memory.
The compressed objects are downloaded to the BTS and uncompressed as part of BTS
initialization.
68P02901W01-S 4-73
Jul 2008
BSS software release GSR6 (Horizon II) Chapter 4: BSS Software Release Features
Table 4-27 summarizes the BSS features provided at software release GSR6 (Horizon II).
Description
Horizon II
Enhanced two uplink timeslots
Removal of support for Horizonoffice
Horizon II
Feature overview
The Horizon II feature provides support for the new Horizon II macro BTS and the CTU2
transceiver.
Support of up to six double density CTU2s in the Horizonmacro and Horizon II macro
platforms.
The CTU2 transceiver supports two logical carriers and can operate in either single or dual
carrier mode. It is backward compatible with the Horizonmacro platform, and is operated in
single or dual carrier mode in both the Horizonmacro and Horizon II macro BTS cabinets.
Combinations of TCU-A, TCU-B, CTU, and CTU2 in single carrier mode and dual carrier mode
are allowed within a cell providing RF power restrictions are obeyed.
Transmit power capability is different for single and dual carrier modes, see Table 4-28.
4-74 68P02901W01-S
Jul 2008
System Information: GSM Overview Horizon II
In single carrier mode, the CTU2 capabilities are similar to those of the existing CTU, and the
CTU2 can be used as a replacement for the CTU providing GSR6 (or later) software is used.
In dual carrier mode, the CTU2 enables the Horizonmacro or Horizon II macro to support up
to twelve carriers. There are, however, certain restrictions when the CTU2 operates in dual
carrier mode:
Baseband hopping is not supported when the controlling cabinets are either Horizonmacro
or M-Cell, due to the switching capability of the MCU/MCUF.
Maximum output power capacity is reduced due to internal combination within the CTU2.
Remote Tune Combining (RTC) is not supported if the CTU2 is operating as a master
or standby controller of an RTC, however RTC is used if the CTU2 is not the master or
standby controller.
Both carriers must be in the same cell because the CTU2 has one single RF output.
The Horizon II macro BTS can be either the controlling cabinet or extension cabinet connected
to a controlling Horizon II macro/Horizonmacro/M-Cell BTS cabinet.
NOTE
BTS sites with Horizonmacro/M-Cell6 as the controlling cabinet must have a PCMCIA
card fitted for CTU2 to be supported.
Horizon II macro Site Controller (H2SC) with integrated NIU and FMUX, E1 support and
enhanced E1 redundancy, and increased removable flash media.
XMUX
68P02901W01-S 4-75
Jul 2008
Enhanced two uplink timeslots Chapter 4: BSS Software Release Features
Horizon II macro cabinets only support a single frequency band, 900 MHz, or 1800 MHz.
Multiband cabinets are not available.
Feature overview
Enhanced two uplink timeslots (2UL) is an extension to the GPRS feature (RDB2773) introduced
in GSR4.1, and the Multiple GPRS carriers per cell (RDB3725), Interleaving TBFs (RDB4253),
and Enhanced one phase access (RDB4386) features introduced in GSR6.
This feature improves MS GPRS performance by allocating multiple timeslots in the uplink
direction.
Feature description
In GSR6, GPRS multi-slot class MSs which support multiple timeslot allocations in the uplink
and downlink directions, were only allocated one uplink timeslot. The Enhanced 2UL feature
provides allocation of up to two uplink timeslots for the MSs that support multiple uplink
timeslot allocation.
This feature improves the performance of MSs that support multiple uplink timeslot allocation
and comprises two sub-features:
Enhanced 2UL timeslot scheduling
This enables the operation of two uplink timeslots for MS multi-slot classes that support it.
All multi-slot classes that support multiple uplink timeslots in dynamic mode are mapped to
multi-slot class 5, 6, 9 or 10.
Table 4-29 shows the MS multi-slot class mapping for all GPRS multi-slot classes.
4-76 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced two uplink timeslots
Table 4-29 MS multi-slot class mapping for all GPRS multi-slot classes
For some multi-slot class MSs the maximum number of uplink and downlink timeslots in the
MSs allocation is less than the sum of the maximum number of timeslots that can allocate in an
individual TBF direction. These MSs can be allocated more timeslots in one direction at the
expense of fewer timeslots in the opposite direction. This type of multi-slot class is called
a biasable multi-slot class. The Enhanced Two Uplink Timeslots feature supports biasable
multi-slot classes 6 and 10.
Figure 4-2 shows the multi-slot class 6 MS uplink bias configuration of two timeslots in both
downlink and uplink directions, or downlink bias of three downlink timeslots and one uplink
timeslot.
Figure 4-3 shows multi-slot class 10 MS uplink bias configuration of two uplink timeslots and
three downlink timeslots, or downlink bias of four downlink timeslots and one uplink timeslot.
68P02901W01-S 4-77
Jul 2008
Enhanced two uplink timeslots Chapter 4: BSS Software Release Features
The bias change mechanism is based on the data transfer characteristics in the uplink and
downlink directions. During uplink data transfer for example, the uplink direction is highly
active when compared to the downlink direction, the MS therefore receives an uplink biased
timeslots allocation.
Although MS multi-slot classes 5 and 9 support multiple uplink timeslots, these MSs do not have
the restrictions of biasable classes. Consequently, uplink/downlink biasing does not apply to
MSs of class 5 or 9.
4-78 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release GSR7
GSR7 features
Description
PCU 3X capacity increase
Enhanced Scheduling
Performance Enhancements Under Load
Seamless cell reselection
DSW/DSWX to be backwards compatible with KSW/KSWX
Adaptive Multi-Rate
Move PCU and BTS objects from BSP
GPRS PBCCH/PCCCH support
EGPRS
Feature overview
The primary purpose of the PCU 3X capacity increase feature is to allow an increase in PCU
capacity. The extra PCUs allow improved redundancy for PCUs.
The PCU 3X capacity increase feature allows the operator to enable redundancy for any or all
PCUs when more than one PCU is equipped. If three PCUs are equipped, a first and second
redundant PCU cell mapping can be set by the operator when redundancy is enabled.
The PCU 3X capacity increase feature allows the operator to add PCUs to a maximum of 3 per
BSC, which a single BSC must now manage. The other elements of the BSS (that is, BSC, BTS
PCUs) will not undergo any hardware or firmware changes for this feature, nor will the PCUs
have the capability to communicate directly with each other.
68P02901W01-S 4-79
Jul 2008
PCU 3X capacity increase Chapter 4: BSS Software Release Features
Feature description
Figure 4-4 shows a general representation of a GSM BSS configuration with 3 PCUs equipped.
During certain fault conditions which render the Primary PCU inoperable, the cells are
moved from the Primary PCU to the first redundant PCU. If the Primary PCU return to the
IN-Service (INS) state, the cells are remapped back to the Primary PCU. If both the Primary
and first redundant PCU fail, the cells can be mapped to the second redundant PCU. If the first
redundant PCU returns to the INS state, the cells are mapped back to the first redundant
PCU. If at anytime the Primary PCU returns to the INS state, the cells are mapped back to
their respective Primary PCU.
NOTE
The BSC may interface with a range of 0 to 3 PCUs, where each PCU interfaces with
only that BSC. On the Gb interface, all PCUs which are attached to a single BSC
must interface with the same SGSN. All PCUs attached to a single BSC must also be
managed by the same OMC-R.
A PCU can terminate 60 single timeslot GSLs (30/E1 PMC) and support 4 GBLs. All combinations
of the various coding schemes (CS1 to CS4) are supported.
4-80 68P02901W01-S
Jul 2008
System Information: GSM Overview GPROC3
GPROC3
Feature overview
GPROC boards are used in the BSC, RXCDR, and InCell BTS network platforms to provide
the processing power required to operate the mobile network. However, as the capacity and
functionality of the GSM network product range has developed, system resources required to
power the network have increased and for GSR7 greater processing power is needed.
The original GPROC board was superseded by the GPROC2, which in turn is now being replaced
by the next generation of processor board, the GPROC3.
GPROC3 system performance is almost two times that of the GPROC2. This performance
increase is due to a culmination of several hardware factors, including:
Motorola 68060 processor
Synchronous DRAM
NOTE
The Battery Backup Extension (BBX) system does not support the GPROC3.
Table 4-31 provides a comparison between the GPROC3 and GPROC2 processor boards.
The GPROC3 is fully functionally backward compatible with the GPROC and GPROC2, and
can be used as a FRU at the following locations without impacting existing functionality or
external interfaces:
BSC
RXCDR
InCell BTS
68P02901W01-S 4-81
Jul 2008
Enhanced scheduling Chapter 4: BSS Software Release Features
The GPROC3 has dual boot ROM functionality to provide additional protection in the event of
hardware, software, or flash failure.
Enhanced scheduling
Feature overview
Enhanced Scheduling is an extension to the GPRS feature introduced in GSR4.1, Multiple GPRS
Carriers Per Cell, Interleaving TBFs, and Enhanced One Phase Access features introduced in
GSR6, and the Two Uplink Timeslots feature introduced in GSR6.
Feature description
In GPRS One-Phase (EOP) access, when a Random Access CHannel (RACH) is received at a
BTS, the BTS uses an EOP assignment if available. When the EOP assignments are exhausted,
and the RACH throttle threshold has not been reached, the RACH is sent to the PCU. The
PCU then responds by sending a one-phase immediate assignment message back to BTS, for
transmission to the mobile station (MS).
Two-phase access is only used if the MS explicitly requests it. The two-phase RACH is processed
at the PCU and the required messaging is carried over RSL/GSL.
The number of messages exchanged between the PCU and BTS over the RSL by these different
TBF establishment methods may cause the RSL to overload at high RACH arrival rates. This
overloading may adversely affect circuit switched traffic and reduce GPRS traffic handling
capability.
The Enhanced Scheduling feature introduces mechanism that allow the BSS to dynamically
select the most appropriate access method, allowing fast access while reducing the load on the
signaling links. This feature comprises the following sub-features:
Dynamic allocation of reserved blocks for two-phase access.
Increased number of GPRS MSs that can be serviced by each PRP from the previous
number of 120.
Provides control for the percentage of RSL bandwidth reserved for circuit switched traffic.
These changes together increase scheduling efficiency leading to a greater amount of GPRS
traffic handling capacity in a given cell while reducing the impact of the data traffic on circuit
switched traffic.
4-82 68P02901W01-S
Jul 2008
System Information: GSM Overview Performance enhancements under load
Feature overview
The Performance Enhancements Under Load feature is an extension to the General Packet Radio
Service (GPRS) feature introduced in GSR4.1, and the Coding Scheme 3 or Coding Scheme 4
and Interleaving TBFs features introduced in GSR6.
It also provides support for the GSR7 features GPRS Seamless Cell Reselection, Enhanced
Scheduling, and PBCCH/PCCCH.
Feature description
Cell Partitioning
In GSR7, Packet Resource Processor (PRP) capacity and data traffic are increased in the
Enhanced Scheduling feature, and Seamless Cell Reselection between PRP boards introduces a
new data through the PCI backplane of the PCU.
Cell Partitioning is a software modification that reduces backplane traffic to prevent system
overload. It places the critical data for maintaining the synchronous radio link within a single
slot, and passes the larger more efficient Gb packets over the backplane.
The software processes that work with the TRAU data are repartitioned. The packetization
process is relocated to the PRP and is merged into the scheduling process to facilitate data
transfer with low overhead. The TRAU type GDS is equipped on a PRP board, and data path
latency is minimized. Processor overhead of the messages on the bus is reduced, and the
recovered CPU time is used for scheduling or increased capacity.
The GSR6 feature RDB4253 Interleaving TBFs introduced the parameter delay_dl_rel_dur to
set the downlink Temporary Block Flow (TBF) release duration.
As the number of simultaneous calls in a GPRS cell increases, a large percentage of mobiles
with assigned downlink resources are in delayed downlink TBF release mode with no actual
downlink traffic. The PCU scheduler assigns up to a maximum of four mobiles per PDCH,
and any additional mobiles requesting allocation are blocked until an existing TBF ends. The
longer the delayed downlink TBF release duration, the greater the possibility of new mobiles
requesting access in a cell being blocked. Mobiles in delayed downlink TBF release mode for an
extended period can be terminated, but this takes at least 500 msec (or T3193 period).
68P02901W01-S 4-83
Jul 2008
Seamless cell reselection Chapter 4: BSS Software Release Features
To reduce the possibility of mobiles being blocked, the scheduler in the PCU monitors the
availability of timeslot resources in the cell, and terminates downlink TBFs in delayed
downlink release mode before the cell is blocked. The maximum duration is determined by the
delay_dl_rel_dur parameter and ranges from 300 msecs to 10 seconds, with a typical value of
1 second.
Cell availability is calculated and monitored when timeslot resources that take a mobile from
idle to transfer state are assigned, and when release procedures are initiated that returns the
mobile to idle state. If the availability is less than the threshold, the scheduler selects one or
more downlink TBFs in delayed release mode to terminate. The criteria for termination of TBFs
comprise no uplink TBF in progress and a duration of at least 300 msecs in delayed release mode.
The downlink TBF establishment duration is minimized if a Packet Downlink Assignment is sent
on the PACCH while uplink TBF is in progress.
If no downlink TBF exists for a mobile while releasing the uplink TBF, the uplink TBF can be
extended by delaying the final PUAK by a configurable number of block periods.
Before GSR7, all downlink and uplink TBFs used Coding Scheme 2 (CS-2). This feature enables
the initial downlink coding scheme to be set to improve throughput of cells in which all the
mobiles are capable of higher coding schemes.
The initial coding scheme is only set for TBFs with local Temporary Logical Link Identities
(TLLIs). Coding Scheme-2 is used for TBFs with non-local TLLIs, and when the carrier or PDCHs
assigned for the TBFs are not capable of the initial coding scheme CS-3 or CS-4.
The TLLI Block Coding Scheme in one-phase uplink TBFs is always set to CS-1 to ensure that
the contention is resolved quickly.
This parameter determines the extent of system efficiency against fairness among the users.
Share of throughput for each user is determined by using the current coding scheme (CS)
information, to allocate the available bandwidth among the active users with established TBFs.
2 This favors mobiles with higher coding scheme, providing maximum overall throughput.
Feature overview
GPRS cell reselection offers mobility and performs network traffic management. The Seamless
cell reselection is performed with minimal data loss capability.
4-84 68P02901W01-S
Jul 2008
System Information: GSM Overview DSW/DSWX backward compatible with KSW/KSWX
Feature description
The term seamless cell reselection implies the completion of a cell change procedure at the
RLC/MAC layer in a controlled manner so that the higher layers do not notice the effect.
Seamless cell reselection is proposed to help Transmission Control Protocol (TCP) during cell
reselection. Cell reselection is performed with a minimal data loss capability, because no
segments need to be retransmitted and the TCP does not even notice that a cell reselection
is performed underneath.
Feature overview
The DSW/DSWX are replacements to the KSW/KSWX and are backwards compatible with the
KSW/KSWX in the GSR7 loadline. The DSW/DSWX can therefore be deployed into an existing
site without any configuration changes.
68P02901W01-S 4-85
Jul 2008
DSW/DSWX backward compatible with KSW/KSWX Chapter 4: BSS Software Release Features
Feature description
The DSWX board is an enhanced version of the KSWX board that allows expansion and extension
to other cages. The operator is not required to specify the difference between the KSW and
the DSW device. The existing KSW device can be equipped and either KSW hardware or DSW
hardware can be deployed.
The DSW can be used as a replacement to the KSW and upgrades to the DSW hardware is
gradual so a mixture of KSW and DSW is likely to be required. A KSW board and DSW board can
co-exist within one cage, one acting as the slave and the other as primary switch. This will allow
the operator to change the slave KSWs that make up the redundant TDM highway to DSWs,
swap the primary and redundant highways to allow the DSW features and then replace the
KSWs that now make up the redundant TDM highway. Mixing KSWXs and DSWXs can occur in
the same cage as the DSWX acts as a KSWX and operates in single rate mode.
NOTE
Pairing a KSWX and DSWX together through fiber is not possible since the TDM fiber
data streams are incompatible.
ECM is configured on the new Double Kiloport Switch (DSW) and Double Kiloport Switch
(Extended) (DSWX). This allows timeslots for a double rate TDM bus (clocked at twice the rate
of a single-rate bus) to have the bit rate reduced so that the timing of the signals within the cage
is appropriate for existing boards; for example, MSI, XCDR, GDP, GPROC2 which do not support
the double-capacity mode. GDP2s can therefore occupy the same cages as these existing boards.
In order to use the GDP board as a 60-channel, two span line transcoder card and the following
changes to the system are required:
Use of 2048 timeslot mode (no KSW or KSWX used).
All RXU cages that are planned to house GDP2 boards are to be replaced with (Next
Generation) ngRXU cages.
All local transcoding BSC and RXCDR BSSC cabinets housing GDP2 boards are to be
replaced with (Next Generation) ngBSSC cabinets.
It is possible, however, for the GDP2 to operate as a 30-channel, one span line transcoder card
as a replacement to the GDP board and is capable of processing an AMR calls if the feature is
unrestricted. It can therefore be positioned in a regular RXU cage within a regular BSSC cabinet.
The DSW/DSWX is an enhanced version of the KSW/KSWX to support double the number of
ports and extended sub-rate switching down to 8 kbps (single bit). To achieve double rate the
TDM bus bandwidth is increased to 128 Mbps divided into 2048 timeslots.
4-86 68P02901W01-S
Jul 2008
System Information: GSM Overview Adaptive Multi-Rate (AMR)
Feature overview
The AMR feature set provides improvements in system capacity and speech quality. The AMR
speech codec includes a set of fixed rate speech codec modes for full rate (FR) and half rate
(HR.) operations, with the ability to switch between the different channel coding modes as a
function of the propagation error conditions. An AMR HR for speech gives enhanced capacity
over the air interface and speech quality using codec mode adaptation. This requires selecting
the optimum channel (HR or FR) and codec mode (speech and channel bit rates) to deliver the
best combination of speech quality and system capacity.
An AMR HR call can occupy an 8 kbps timeslot (an Ater channel) on the terrestrial resource
from the BSC to the RXCDR, rather than the 16 kbps timeslot required for FR calls. If a
percentage of the active calls can be assumed to be HR, then efficiency can be gained by
reducing the number of terrestrial resources between the BSC and RXCDR. This is possible
only if the BSC can dynamically allocate a timeslot to a CIC. This allocation is performed across
the Ater interface and is considered to be an enhancement to the existing Auto Connect mode,
referred to as Enhanced Auto Connect or EAC mode.
NOTE
If the 7.95 kbps codec mode is included in the HR AMR Codec Set (ACS), a 16 kbps
timeslot is always required.
The initial AMR release supports the FR, HR, and link adaptation features on Horizonmacro
cabinets with CTU radio platforms. In this release, the AMR feature is available on the CTU,
TCU-A and TCU-B radio platforms.
68P02901W01-S 4-87
Jul 2008
Adaptive Multi-Rate (AMR) Chapter 4: BSS Software Release Features
Feature description
The AMR feature set can be divided into four component parts as follows:
Full-rate channel mode
The AMR full-rate channel is a full-rate channel that employs an AMR speech codec to provide
higher speech quality in areas of poor RF conditions. Full rate channels achieve improved
call speech quality at the expense of the increased cell capacity offered by half rate. Calls
designated as half rate is transferred to a full rate carrier if the speech quality of the call
is impaired by interference and the necessary resources are available. Conversely, if cell
congestion exceeds a preset threshold, full rate calls is reassigned to half rate to release extra
traffic channels, provided the cell RTFs are enabled as half rate capable.
Full-rate AMR link adaptation provides the mechanism for the BSS to adapt between
speech codec modes, in an AMR codec on the uplink and downlink of an AMR full-rate call.
This adaptation mechanism provides the most suitable level of error correction for the RF
environment. Uplink and downlink codec modes are monitored separately, and can be adapted
separately. With full-rate link adaptation, up to four codec modes can be placed in the per cell
Full-Rate Active Codec Set (FR ACS). Calls are adapted over this active codec set, according to
the quality of the link between the MS and the BSS.
The full-rate Adaptive Full-Speech (AFS) codec modes supported are as follows:
12.2 kbps
10.2 kbps
7.4 kbps
6.7 kbps
5.15 kbps
The higher the bit rate of the codec mode, the higher the speech rate and lower the error
correction rate. Up to 4 of these codec modes can be included in the FR ACS.
The AMR half-rate channel mode allows two AMR calls to be placed on a single air interface
timeslot. Use of the AMR half-rate channel mode increases cell capacity, without the need for
extra radio hardware. The cost of the increase in cell capacity with this release of the AMR
half-rate channel mode is the need for the provisioning of extra backhaul between the BSC and
BTS and the lower quality of service provided by AMR half-rate calls.
The BSS software allows the AMR half-rate channel mode to be enabled and disabled on a
per cell basis. Specific RTFs within a cell can be configured based on AMR half-rate channel
mode capability. Half-rate enabled RTFs are allocated an additional two E1 timeslots between
the BSC and BTS. Extra timeslot allocation is necessary if the BSC does not support 8 kbps
4-88 68P02901W01-S
Jul 2008
System Information: GSM Overview Adaptive Multi-Rate (AMR)
switching, so AMR half-rate call speech data must be carried in 16 kbps TRAU format between
the BSC and BTS. If DSW/DSWXs are used at the BSC 8 kbps switching is supported and 8
kbps backhaul can be used.
Given that, potentially, 16 AMR half-rate calls can be supported on an AMR half-rate carrier. An
AMR half-rate RTF must have four associated E1 timeslots provisioned between the BSC and
BTS. Due to reduced bandwidth, an AMR half-rate call has, in general, a lower perceived Quality
of Service (QoS) than a full-rate call. For this reason, a per cell database threshold is provided
to allow the operator to specify the level of congestion that must exceed in an AMR half-rate
capable cell before new calls can be assigned to half-rate traffic channels.
When the received Bit Error Rate (BER) rxqual indicates that a half-rate channel is suffering
interference and that the speech quality of the call is therefore impaired, an intra-cell handovers
back to full-rate (or to another half-rate channel) is supported to maintain quality of service.
Alternatively, a database parameter is set in order to override any MSC channel rate preference,
if given, and the cell's congestion threshold, causing AMR calls to be assigned directly to
half-rate channels. This allows temporary forcing (from the OMC) of half-rate usage during busy
periods. Intra-cell handovers for quality reasons from half-rate are still permitted when the
override flag is set, but the target resource for the intra-cell handover is forced to half-rate.
In addition to the ability to specify that new half-rate capable calls be assigned to half-rate traffic
channels when cell congestion exceeds the threshold, a second (or alternative) congestion
threshold can be specified. When this congestion threshold is exceeded in an AMR half-rate
channel mode cell, the BSS reassigns half-rate capable full-rate calls to half-rate traffic channels.
NOTE
Intra-cell handovers from full rate to half rate are not allowed.
Half-rate AMR link adaptation provides similar functionality to full-rate AMR link adaptation for
the half-rate AMR channel.
In half-rate AMR link adaptation there is a different half-rate ACS. This ACS can contain up to
four of the half-rate AMR codec modes that are supported. The half-rate Adaptive Half-rate
Speech (AHS) codec modes supported are:
7.95 kbps
7.4 kbps
6.7 kbps
5.9 kbps
5.15 kbps
There are different half-rate initial codec mode and associated uplink and downlink codec mode
adaptation thresholds and hysteresis values for half-rate AMR calls.
The existing GSM handover and power control algorithms are still used for the half-rate AMR
channel but, similar to full-rate link adaptation, a new set of handover and power control
thresholds are introduced. The new half-rate AMR handover and power control rxqual
thresholds are different to the full-rate AMR handover and power control thresholds because
the half-rate channel displays different characteristics to a full-rate AMR channel. For these
68P02901W01-S 4-89
Jul 2008
Move PCU and BTS objects from BSP Chapter 4: BSS Software Release Features
reasons handover and power control algorithms are configured in a different manner to cater
for the half-rate AMR channel. The MS Monitor introduced in full-rate AMR link adaptation
also applies to half-rate AMR calls.
Feature Overview
This feature reduces the code object sizes. It also enables smart management of the location of
code objects for the Base Site Processor (BSP).
Feature description
The BSP is near capacity and will exceed the physical memory available (32 MBs) with the
addition of the GSR6.1 and GSR7 GPRS features, H2, and AMR. To relieve the situation this
feature performs the following actions:
Removes the BTS and PCU objects from the BSP.
Optimizes compilers.
The BSC no longer stores the BTS and PCU objects on the BSP. These objects are stored on
other GPROCs within the BSC. Initialization Process (IP), Central Authority (CA) and the Code
Object Manager (COM) are modified to remove these objects at the initialization time of a BSP.
The BTS and PCU objects are loaded from other GPROCs, such as a Link Control Processor
(LCP) within the BSC.
NOTE
Type 0 BSC is no longer supported, therefore there must be at least a BSP and an
LCP at a BSC.
The network entity affected is the BSC only; all changes are confined to the BSC.
This sub-feature optimizes the way that PCU objects for the DPROC and MPROC are built
and initialized. Memory saving is gained by removing duplicated EXEC and PCM code from
the MPROC and DPROC objects and creating a single new object for each. A copy of each
object is then loaded on to both the MPROC and the DPROC after it is downloaded to the
PCU from the BSC.
4-90 68P02901W01-S
Jul 2008
System Information: GSM Overview GPRS PBCCH/PCCCH support
BSC - 2 new objects to store and download to the PCU, resulting in memory savings.
Predicted memory saving is 600 kbytes on the LCP boards storing the PCU objects.
Compiler optimizations
Compiler optimizations are updated to remove unused source level debugging information from
objects built for the BSC and BTS. Other compiler options to optimize for space utilization
versus performance are made for specific processes that do not require performance.
The network entities affected are the BSC or BTS, so that all objects are smaller and built using
compiler options that are appropriate for the function of the object or process.
Feature overview
The PBCCH/PCCCH feature (RDB 3723) is a software-only feature that introduces support for
the Packet Common Control Channels (PCCCH) and Packet Broadcast Control Channel (PBCCH)
to the Motorola BSS. The PCCCH consists of the following logical channels for common control
signaling used for GPRS:
Previous to this feature, the Motorola BSS provided the functions of all these logical channels
using the CCCH. Therefore, GPRS-capable MSs served by a Motorola BSS would camp on
the CCCH. With this feature, GPRS-capable MSs served by a Motorola BSS will camp on the
PCCCH and use the PCCCH channels instead.
PBCCH/PCCCH are the packet data logical channels dedicated for GPRS signaling. With
PBCCH/PCCCH configured in a cell, MS reads system information on PBCCH and perform
packet access activities on PCCCH. Table 4-32 shows the functionality of each packet logical
channels on PBCCH/PCCCH.
68P02901W01-S 4-91
Jul 2008
Enhanced GPRS (EGPRS) Chapter 4: BSS Software Release Features
Feature overview
The EGPRS feature is an extension to the software architecture introduced by the General
Packet Radio Service (GPRS) feature and the Coding Scheme 3 or Coding Scheme 4 feature. This
means that a network supporting EGPRS also provides support for GSM voice and GPRS data.
EGPRS employs a new set of GSM modulation and channel coding techniques that increase a
user's packet data throughput from a maximum of 21.4 kbps per air timeslot with GPRS to
a maximum of 59.2 kbps per air timeslot with EGPRS. The maximum data throughput for a
multi-slot mobile utilizing all eight air timeslots with EGPRS is 473.6 kbps compared to 171.2
kbps in GPRS.
Operational requirements
The BSS is compliant with the 3GPP R99 December 2002 version of the standards on the air and
Gb interfaces.
EDGE standards
EDGE standards define enhancements to both General Packet Radio Services (referred to as
EGPRS) and High Speed Circuit Switched Data (referred to as ECSD). Software release GSR7
only provides support for the EGPRS portion of EDGE; support for ECSD is not provided.
Throughout this manual and in the set of manuals accompanying this manual, reference is
therefore made only to EGPRS.
4-92 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced GPRS (EGPRS)
Feature description
The initial release of EGPRS provides support for a multi-slot mobile using four air timeslots.
Support for the mobile classes, which dictate the multi-slot capabilities of a mobile, are the same
for EGPRS as in GPRS (classes 1 - 12). Although a large portion of the EGPRS impact to the BSS
software is focused on the air interface, impacts also exist on the terrestrial interfaces to carry
the large volume of data traffic produced by these new data rates.
The 3GPP specification refers to two modes of operation for EGPRS, Classic and Compact. Only
the Classic mode of operation is supported for EGPRS. References to Compact mode are no
longer applicable in the standards and therefore they are not supported.
An EGPRS system encompasses changes to the existing GPRS BSS to support the higher data
rates that EGPRS provides.
68P02901W01-S 4-93
Jul 2008
BSS software release GSR7 (GSM Half Rate) Chapter 4: BSS Software Release Features
Table 4-33 summarizes the BSS features provided at software release GSR7 (GSM Half Rate).
Description
GSM Half Rate
Feature overview
The GSM Half Rate (GSM-HR) feature provides enhanced capacity over the air interface. An air
timeslot is split into two sub-channels, each containing a GSM-HR channel.
A GSM-HR call can fit within an 8 kbps timeslot (an Ater channel) on the terrestrial resource
from the BSC to the RXCDR, rather than the 16 kbps timeslot required for FR calls. If a
percentage of the active calls is HR, then efficiency can be gained by reducing the number
of terrestrial resources between the BSC and RXCDR. This is possible only if the BSC can
dynamically allocate a timeslot to a CIC on an 8 kbps/16 kbps basis. This dynamic allocation is
performed across a trunked interface between the BSC and an RXCDR, the Ater interface. The
dynamic allocation is an enhancement to the existing Auto Connect mode feature, Enhanced
Auto Connect mode. Enhanced Auto Connect is part of the AMR feature and is mentioned here
only to point out that GSM-HR will enjoy the same benefit.
The backhaul between the BTS and BSC is 8 kbps or 16 kbps. 8 kbps requires that subrate
(8K) switching is present at the BSC.
4-94 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release GSR8
Description
Stop BTS transmission after the last RSL fails
GPRS resources (PDTCH) configured
Out_inter_bss_ho statistical counter
Support for CGI for Inter PLMN
BSC Reset Management
Intelligent multi-layer resource management for voice
GPRS Trace
New GPRS alarms
GPRS Statistics and enhancements
NACC Network Assisted Cell Change
Enhanced 2G-3G handover
VersaTRAU
Support of QoS Release 99 (was 22889)
Support for Horizon II Mini
GPRS R4 Compatibility
eMLPP
Support for Half Rate on GDP2
Fast Call Setup
RSL Congestion Control
Increased SDCCH capacity
Improved Timeslot Sharing (ITS)
68P02901W01-S 4-95
Jul 2008
Stop BTS transmission after the last RSL fails Chapter 4: BSS Software Release Features
Feature Description
This feature stops DRIs transmission when the CELL, they are in, goes out of service (OOS) for a
specified period of time. The DRIs start transmitting again when the CELL returns to service
(INS). This feature can be enabled or disabled per BSS in SYSGEN mode.
A cell timer, which provides flexibility on how long the DRIs continue transmitting after
the cell they are in has gone out of service. It can be used to prevent DRIs ceasing
transmission for short cell outages.
New reasons are included in state change events sent by the BSS to the OMC-R. The text for
each reason is coded by BSS in a rsn file that is loaded on the OMC-R. It activated when its
associated BSS load is activated at the BSS. No additional OMC-R functionality is required
to support these new state change reasons.
Feature Description
This feature displays the static configuration of PDTCHs on a PCU and cells mapping on a PRP
DPROC at the BSC using the disp_equipment command. OMC-R and MMI statistics monitor the
demand of PDTCHs and GCIs on a PRP DPROC.
The BSS issues a rejection message if more PDTCHs are required that can be handled by the
RTFs or PRPs on the PCU. A warning message is printed if insufficient PMC or GDS resources
are available.
The statistics only count the PRP PDTCHs or GCIs demanded on cells that are dynamically
mapped on a PRP DPROC. If a cell is unmapped to a PRP DPROC or out of service, alarms are
generated to indicate the problem.
4-96 68P02901W01-S
Jul 2008
System Information: GSM Overview Out_inter_bss_ho statistical counter
Feature Description
This feature improves the OUT_INTER_BSS_HO statistic pegging so that the global statistic
DROP_CALLS can be calculated accurately. The OUT_INTER_BSS_HO statistic has seven bins:
OUT_INTER_BSS_REQ_TO_MSC
OUT_INTER_BSS_HO_ATMPT
OUT_INTER_BSS_HO_SUC
OUT_INTER_BSS_HO_LOSTMS
OUT_INTER_BSS_HO_RETURN
OUT_INTER_BSS_EQUIP_FAIL
OUT_INTER_BSS_HO_CLEARED
NOTE
Some of these are included in DROP_CALLS formula and are pegged incorrectly, This
results in DROP_CALLS being calculated incorrectly. Pegging method for some bins
are improved in this enhancement feature.
68P02901W01-S 4-97
Jul 2008
BSS support for full Cell ID Chapter 4: BSS Software Release Features
Feature Description
This feature causes both the OMC and BSS to send the full GSM Cell ID (MCC, MNC, LAC, CI)
when transmitting the cell information over the OMC-BSS interface.
The GSM Cell ID is a unique identifier that identifies the cell within a network. GSM Cell ID
consists of four identifiers:
Mobile Country Code (MCC)
GSM standard specifications requires that the GSM Cell ID is unique for all cells within the
world.
Because cells could exist in a BSS with the same LAC and CI, but having different MCC and/or
MNC, the LAC and CI is not sufficient to uniquely identify a Cell in a BSS to the OMC. The
GSM Cell ID feature overcomes this by sending the full GSM Cell ID (MCC, MNC, LAC, CI)
when transmitting cell information.
With the addition of UTRAN neighbors as a result of the Inter RAT handover feature (RDB4225)
it is possible for GSM cells to have 3G external neighbors. The BSS database allows the
provisioning of UTRAN cells to be specified as neighbors of existing GSM cells.
In the case of a UTRAN neighbor of a GSM cell, it is essential that the OMC-BSS interface
supports full UTRAN Cell IDs. Both OMC and BSS sends full Cell ID over the OMC-BSS interface.
Feature Description
The BSC reset management feature introduces the capability to swap between active and
standby BSPs when the master BSP GPROC fails. The BSP recovers the most useful information
automatically (instead of users restoring it manually), and a greater amount of diagnostic
data is collected for analysis.
Provides more BSC diagnostic data (such as timing, time-outs, measurements of common
factors, system utilization) for great error handling control and understanding of fault
diagnostic.
Provides the capability of preserving device and function unit states before the BSP
switchover.
Provides the capability of preserving the alarm history before the BSP switchover.
4-98 68P02901W01-S
Jul 2008
System Information: GSM Overview BSC Reset Management
After switchover, the BSC initiates a global reset to ensure that the MSC/RXCDR/BSC or BTS
gets status synchronized. For the PCU, the BSC achieves this by disabling and re-enabling all
the GSLs in service. This leads to all the established calls (data and voice) being dropped.
NOTE
The third BSP reset, regardless of the reasons, within a 30 minute period will cause
the BSC to do a complete reset. Thus deploying this feature:
The statistics collected before the BSP switchover on the master BSP are lost. In addition,
if the BSC is type 1, the BSC fails to collect the statistics during BSP switchover.
If this feature is deployed, the impacts on the current BSS system are:
CBC The CBL is managed by an LCP (GPROC with LCF function), so it is kept INS during
BSP switchover. However, the BSC does not send any service request to the CBC during
the BSP switchover.
RXCDR (when the BSC is configured with remote transcoders) Includes two cases:
For type 1 BSC, the XBL links are managed by the BSP, and are OOS when the
master BSP fails. The RXCDR connected with this BSC experiences the loss of XBL
links to the BSC during the BSP switchover. After the BSC switchover, the XBL links
are recovered at the RXCDR, and a global reset is performed at the RXCDR along
with the BSC and BTSs.
For type 2 BSC, the XBL links are managed by OMP (GPROC with OMF) and they
are kept INS during switchover. After BSP switchover, the RXCDR performs a global
reset along with the BSC and BTSs.
For type 2 BSC, the OML links are managed by OMP (GPROC with OMF) and are kept
INS during switchover. The OMC-R is not impacted.
MSC The MTLs are managed by an LCP (GPROC with LCF function) and are kept INS
during BSP switchover. After BSP switchover, the associated MSC is requested to perform
a global reset to release the affected calls and put the associated circuits into idle state.
BTS The RSLs are managed by an LCP and they are kept during BSP switchover. After
BSP switchover, all the associated BTSs are requested to perform a global reset to clear
calls and release the related resources.
GPRS - The BSC disables the GSLs in service and then re-enables those GSLs in order to
clear the data calls established before the BSP switchover, and release related resources.
68P02901W01-S 4-99
Jul 2008
Intelligent Multi Layer Resource Management (IMRM) Chapter 4: BSS Software Release Features
IMRM allows users to better match overall traffic distribution to intrinsic network capacity and
MS penetration. By supporting, on a per cell basis, weightings for each of the available bands,
the system can effect a more dynamic distribution based on factors such as:
Neighbor (For example, micro underlay, macro overlay) per band capacity
EGSM
DCS1800
UMTS
The individual layer weightings are dynamically combined with a requesting MS capabilities to
define a set of probabilities for each of the supported layers; a random selection based on these
probabilities then effects the traffic distribution. The higher the layer weighting the higher the
probability and hence more likely selection. Setting any layer weighting to the maximum defined
value results in a fixed (to that layer) preference selection as per existing ALM procedures.
The default for all available layers is set to Unsupported. Where, IMRM is enabled in a cell with
all layers set to Unsupported, the system applies a set of fixed internal defaults for input into
the Preference Selection Algorithm. The system supports 2 sets of defaults with selection
based on local EGSM availability.
EGSM
PGSM EGSM DCS1800 PCS850 PCS1900 GSM450 UMTS
Support
Yes 45 10 45 N/A N/A N/A 0
No 50 0 50 N/A N/A N/A 0
4-100 68P02901W01-S
Jul 2008
System Information: GSM Overview GPRS Trace
The Preference Selection Algorithm is run for each initial network resource request
(Assignment and incoming External Handover) and is used in conjunction with the existing
band_preference_mode parameter to determine both initial resource targeting and also any
subsequent handover activity. The selected preference is then retained or utilized for the call
while it remains within the current BSS. There are situations whereby the Preference Selection
Algorithm can be re-run for existing calls, either due to system operation and/or operator
control as follows:
Intra-BSS hand-in from non-IMRM Source to IMRM Target.
GPRS Trace
Feature Description
The GPRS Trace feature is an extension of the existing GSM Call Trace implementation. The
GPRS Trace feature enables the user to trace information on GPRS MSs. It provides similar
functionality to GSM Call Trace.
GPRS Trace differs from GSM Call Trace in the following respects:
GPRS signaling is more frequent due to the bursty packet nature of GPRS data transfers.
GPRS MSs may leave a cell without informing the BSS. Therefore, the continue beyond
scope option is not applicable in GPRS Trace. However, for ease of implementation, a
continue beyond scope value is always included in the trace Create action. This value is
ignored by the BSS, if the trace type is GPRS.
For GPRS Trace, the lifetime of an invoked trace will correspond to the lifetime of a GPRS
MS meeting the GPRS Trace criteria within a PCU. A number of GPRS data transfers
may occur within this period. Due to cell reselection, a GPRS MS may leave the scope of
the criteria and/or the PCU without prior warning. When the PCU detects that a GPRS
MS has left, the invoked trace ends. Since cell reselection can take up to 15 seconds,
the PCU waits 15 seconds for the MS to reappear before ending the invoked trace. This
differs from GSM Call Trace, where the lifetime of an invoked trace (and corresponding log
file) corresponds to a single call.
GPRS Trace is created and managed from the OMC and BSS MMI only.
NOTE
Unlike GSM Call Trace, creation of GPRS Trace criteria is not supported from
the MSC. Also, in this release, GPRS Trace Records will not be forwarded to
the NMC.
68P02901W01-S 4-101
Jul 2008
GPRS Trace Chapter 4: BSS Software Release Features
Trace scope options for GPRS Trace: BSS, site, Cell, RTF (as for GSM).
Trace selector options for GPRS Trace: IMSI (International Mobile Subscriber Identity),
TLLI (Temporary Logical Link Identity), Nth GPRS MS.
Trace selector options for GPRS Trace: IMSI (International Mobile Subscriber Identity),
TLLI (Temporary Logical Link Identity), Nth GPRS MS.
GPRS Trace Record type: Basic or Radio. If Radio is selected, the user may select some or
all of the following:
LLC (Logical Link Control) information.
NOTE
This information is counted per-PRP. The trace criteria are complete at the BSS,
when the total numbers of MSs have been traced for at least one PRP. The
overall number of MSs traced during this period may exceed the total number
setting. This behavior is similar to the counting of Total number of calls at the
LCF level for Call Trace.
Measurement interval: This value applies for Packet Measurement Reports and UL/DL
Measurement data.
NOTE
This information is counted per-PRP. Therefore, the number of simultaneous
calls at any specific time may exceed the maximum number setting.
Users may request a combined trace of both GSM and GPRS information in the specific case
of an IMSI trace selector. In this case, the BSS forwards trace records relating to both GSM
calls and GPRS data transfers for that IMSI. GSM and GPRS trace information are written
to separate log files.
4-102 68P02901W01-S
Jul 2008
System Information: GSM Overview New GPRS alarms
Feature Description
The BSS detects when GPRS (or EGPRS) becomes unavailable and there is no other GPRS
Unavailable alarm raised. On arrival of this alarm, an attempt to toggle GPRS/EGPRS is
made to correct the problem. The alarm is cleared if GPRS becomes available again. GPRS
toggling is not attempted for existing GPRS unavailable alarms.
The BSS detects when all PDs on a GDS go out of sync and there is no associated
MSI/MMS alarm.
68P02901W01-S 4-103
Jul 2008
GPRS Statistics and enhancements Chapter 4: BSS Software Release Features
NSVC Failure
The NSVC failure alarm is reported upon the first NSVC failure on a GBL. It indicates one
or more NSVCs have failed. The alarm is cleared when all NSVCs have come into service.
The 50% NSVC Failure alarm is deleted as it is no longer needed with the addition of
the NSVC failure alarm.
Feature Description
This feature introduces statistics to measure the performance of the GPRS/BSS system. The
new statistics provide accurate information about the use of system resources, the quality of
data transfer, the traffic at different GPRS protocol levels, and load distribution.
These statistics enable users to adjust the system configuration to enhance the performance
of the system.
The new GPRS statistics are split into the following six categories based on the different aspects
of the system performance to which the collected statistics data contribute.
Packet Congestion
BLER
Paging Load
Miscellaneous
Feature Description
The Network Assisted Cell Change feature improves GPRS performance by reducing delays in
the cell reselection process. It overcomes the potential problem of the MS selecting a congested
target cell, or that the cell may have GPRS/EGPRS disabled. Network Assisted Cell Change
consists of two independent procedures. The first procedure allows the MS to indicate to the
network the need for a cell change. In the second procedure, the network provides neighbor
cell data to the MS.
4-104 68P02901W01-S
Jul 2008
System Information: GSM Overview Enhanced 2G-3G handover
Neighbor Cell Data procedure - After the target cell has been determined, the network
sends the mobile station a Packet Neighbor Cell Data (PNCD) message containing the
information needed for the mobile station to access the target cell. The neighbor cell
information is sent to the MS in the source cell before the MS performs cell reselection so
that the MS can perform packet access without reading all of the system information in
the target cell.
Feature Description
The Enhanced 2G-3G handover and Cell Reselection feature provides support in the BSS for:
Outgoing dedicated mode handover from 2G to 3G (basic measurement based and service
based handover triggers).
This feature allows a multi-RAT MS to perform a handover while in dedicated mode from GSM
cell to a UTRAN FDD mode cell (2G to 3G). This feature allows the BSS to support handovers
from 2G to 3G based on radio measurements and the service capability of the MS.
68P02901W01-S 4-105
Jul 2008
VersaTRAU Chapter 4: BSS Software Release Features
VersaTRAU
Feature Description
Without the feature, a GSM TDMA timeslot, containing voice or GPRS data, is framed and sent on
a 64 kbps backhaul timeslot between the BSC and a remotely located BTS site. With VersaTRAU,
both voice and GPRS/EGPRS frames are combined into one large frame, which reduces
backhaul wasted due to extra padding. Additionally, when congestion occurs on the backhaul,
GPRS/EGPRS data and control blocks are scheduled accordingly at the PCU to fit the available
backhaul, so the combined VersaTRAU frame can still be sent on a reduced backhaul link.
The VersaTRAU feature provides dynamic TRAU capability to EGPRS Carriers to optimize
backhaul usage and reduce costs to the user.
UL_EGPRS_BACKHAUL_DEMAND
DL_ EGPRS_BACKHAUL_USED
DL_ EGPRS_BACKHAUL_DEMAND
EGPRS_64K_CHANNEL_WIDTH
Using the above statistics the OMC provides a new utility which presents the user an analysis on
the VersaTrau performance over a period of time specified by the user. The summarized report
details the total statistics interval data considered for analysis:
Maximum and mean bytes lost over all the statistics intervals.
Number of intervals where the demand was less than or equal to 80% backhaul.
Number of intervals where the demand was greater than 80% and less than or equal
to 100% backhaul.
Number of intervals where the demand was greater than 100% backhaul.
This information enables users to configure DS0s effectively.
This feature also introduces a new RTF element namely rtf_ds0_count. This element specifies
the number of RTF backhaul timeslots allocated for a 64K carrier.
4-106 68P02901W01-S
Jul 2008
System Information: GSM Overview Support of QoS Release 4 (R4)
Feature Description
This feature provides for aggregation of similar QoS profiles into a single Packet Flow Context
(PFC) and allows the BSS to negotiate and modify QoS parameters.
The Aggregate BSS QoS Profile (ABQP) field, contained in Packet Flow Management (PFM)
signals, describes the QoS characteristics for a single PFC, identified by a Packet Flow Identifier
(PFI). The ABQP field contains a full set of QoS parameters including:
Traffic class
Transfer delay
Other fields describing error rate/ratio characteristics are included in the ABQP to provide a
more specific differentiation of services to users. With the added parameters contained in the
ABQP field, and the ability to negotiate and modify these QoS parameters, the BSS now provides
differentiated services to users inline with the QoS requested by the mobile, and consistent to
those offered to the mobile by the other network entities, thus providing a more consistent end
to end QoS. QoS feature is a purchasable feature in GSR8. QoS feature is available only if the
GPRS feature is purchased and the NACC feature is enabled.
68P02901W01-S 4-107
Jul 2008
Support for Horizon II Mini Chapter 4: BSS Software Release Features
Feature Description
The Horizon II mini platform is a smaller version of Horizon II macro, supporting less capacity,
and hence lesser backhaul (RTF). The OMC-R software needs to identify the Horizon II Mini
from the cabinet ID and enable the option to provision lesser number of carriers for the Horizon
II Mini cabinet. When configured in a Horizon II Mini network, the maximum number of carriers
supported by the Horizon II Mini network is limited to 16.
The Horizon II mini fills the gap in the market left by Horizon Micro2. It should be noted
however that Horizon II mini is not a direct replacement for Horizon Micro2 - there is no
upgrade path in software from micro cabinet types to Horizon II mini.
Replaceable FRUs
Better Rx sensitivity
Better expandability
The Horizon II mini behaves as if it were a Horizon II macro cabinet. Software distinguishes
Horizon II mini cabinets from macro varieties.
The Horizon II mini supports CTU2 radios. These are operated in double density mode, that
is, four carriers are possible at a Horizon II mini cabinet. Furthermore, CTU2 supports the
EDGE feature.
4-108 68P02901W01-S
Jul 2008
System Information: GSM Overview GPRS R4 Compliance
GPRS R4 Compliance
Feature Description
The GPRS R4 Compliance feature makes the BSS compliant to all mandatory aspects of the
March 2003 release of the 3GPP GERAN Release 4 standards and offers the following benefits:
Supports the packet radio functionality of R4 mobiles.
Facilitates operation of optional R4 features such as Network Assisted Cell Change (NACC).
The GPRS R4 Compliance feature is unrestricted and compliance to the mandatory aspects of
the GERAN R4 specifications is unconditional.
Enable Packet SI Status procedure in cells without PBCCH - Reduces data outage time
during acquisition of system information. For example, after cell (re)selection, when the
Packet SI Status procedure is available in a cell without PBCCH, the MS may enter packet
transfer mode after receiving broadcasts of SI3, SI13, and, if present, SI1 messages, the
Packet SI Status procedure allows the MS to request additional system information after
entering packet transfer mode.
Feature Description
The eMLPP service allows calls to be allocated a precedence dependent on their function. For
example, a premium rate subscriber would have a higher precedence than a low tariff subscriber.
This is to allow users of high importance, for example, emergency services, or premium rate
subscribers to be given preferential treatment. The BSS uses this precedence to manage the
active calls in situations such as call setup and for call continuity in case of handover.
The priority, preemption capability, preemption vulnerability, and queuing ability criteria are
allocated by the MSC and is utilized by the BSS to provide the appropriate level of service.
The eMLPP feature enables Users to implement support for preemption within the network. The
eMLPP feature is enabled or disabled on a BSS basis.
The eMLPP feature includes the following optional User-controlled BSS functionality:
Priority protection of PDTCH
68P02901W01-S 4-109
Jul 2008
Support for Half Rate on GDP2 Chapter 4: BSS Software Release Features
Feature Description
The GSM Half-Rate feature increases capacity over the air and terrestrial interfaces. It enables
the network to carry up to twice as much traffic, allowing it to cope with increased congestion.
GSM Half-Rate introduced in GSR7, was limited to the GDP platform. Furthermore, the GDP
was unable to support both Half-Rate (HR) and Adaptive Multi-Rate (AMR).
The Support for Half Rate on GDP2 feature extends HR functionality by enabling HR support on
the GDP2 RXCDR platform. In addition, the GDP2 can support both HR and AMR. A combination
of up to 60 channels at SFR, EFR, HR, and AMR is available.
NOTE
AMR encompasses both AMR full-rate and AMR half rate.
Feature Description
This feature reduces the time required for call setup by assigning the MS directly to the TCH
during the IMMEDIATE ASSIGNMENT message, while the available TCHs for the BCCH band
are below a user configured threshold. Once the TCH usage for the BCCH band has equaled or
exceeded this threshold, the BSS performs assignment through the SDCCH.
The data throughout on the TCH is faster than that of the SDCCH.
The operator configured thresholds can help avoid cell congestion due to phantom RACHs.
4-110 68P02901W01-S
Jul 2008
System Information: GSM Overview RSL Congestion Control
Feature Description
The Radio Signaling Link Congestion Control feature is designed to protect downlink RSLs
from (GSM) paging surges.
When the RSL Congestion Control feature detects the onset of RSL congestion it rejects any
new service requirements and notifies the MSC with an Overload message until the congestion
abates.
During the congestion the BSS sends an alarm to the OMC and provides a statistic with the
amount of time a processor was in a congested state and number of OVERLOAD messages
sent to MSC.
Feature Description
This feature allows configuration of up to 128 SDCCH per cell. In a site with three cells with
24 carriers configured in an 8/8/8 fashion up to 128 SDCCH can be configured per cell. The
feature allows a configuration of up to 8 timeslots for SDCCH on a carrier, so up to 64 SDCCH
can be supported on a single carrier.
Feature Description
The Improved Timeslot Sharing (ITS) feature enables Double Density (DD) CTU2 support of
EGPRS. It does not double voice capacity per CTU2 compared with EGPRS on a Single Density
(SD) CTU2, but provides more channels available for voice users with the EGPRS service in
parallel.
Modifications to CTU2 hardware, BSS Software, or Horizon II Firmware are not required.
The timeslots on one carrier of a DD CTU2 is configured for EGPRS, while the corresponding
timeslots on the other carrier are set OOS.
ITS interacts with and affects other network features, such as VersaTRAU, EGPRS, Increased
SDCCH, and Switchable/Reserved PDTCH allocation.
Improve_ts_enabled specifies the enable or disable status of this feature in the BSS.
The EGPRS Unavailable - No EGPRS capable carriers available alarm is modified in this
feature.
68P02901W01-S 4-111
Jul 2008
BSS software release GSR9 Chapter 4: BSS Software Release Features
Description
{22168} Enhanced BSC Capacity Using DSW2.
{22169} Support for 96 Multiple Serial Interface (MSI) at BSC.
{22266} RSL dimensioning statistics.
{22415} Increase the PCU database capacity.
{23306} BSC Overload Protection.
{25002} TDM Availability Enhancements.
{25423} Software patching.
{25424} PCU Upgrade without BSC Reset.
{25867} New drop call rate classes statistics.
{26481} Support for Horizon II Micro.
{29241} Extended Range for Electronic IDs of Cabinet Power
Supplies.
{30365} Software support for High power Horizon II Micro.
{26740} PCU high bandwidth interconnection.
{27236} 4 Branch Receive Diversity.
{27703A} Quality of Service PhaseII Feature.
{27717} Support of RESUME at intra-BSC level.
{27955A} Software support for High Bandwidth and/or existing E1
BSC/PCU interconnect.
{27962} LCF Memory saving to prolong the life of existing GPROC2.
{28000} Increase the Throughput of PRP with the PCU.
{28333} BSS LAN Packing.
{28337} HSP MTL.
{28340} BSP CPU utilization reduction for higher call handling
capacity.
{28351} Addition of new PCU hardware to increase GPRS capacity.
{28398} Increased Network Capacity.
{28938} Support of Incell as an Optional Feature.
{30828} CTU2D.
{31400} TD-SCDMA and GSM interworking feature.
Continued
4-112 68P02901W01-S
Jul 2008
System Information: GSM Overview BSS software release GSR9
68P02901W01-S 4-113
Jul 2008
Enhanced BSC Capacity Using DSW2 Chapter 4: BSS Software Release Features
{22168}
Feature description
This is a default feature in GSR9, which is also unrestricted. This feature doubles the TDM
timeslots in BSC from 1024 to 2048 in one switch cage using bank 0/1 extension mode. When
this switch cage has one or more extension cages, the switch cage uses 1024 TSs (BANK0), and
the other extension cages share the rest 1024 TSs (BANK1). The maximum capacity is 8192 TSs
when up to 4 expansion cages are configured, making it possible to equip more devices (for
example, MSI, PSI, and so on) in multiple cages.
This feature is implemented automatically when BSC is up and without requiring changes to
any parameter when:
Primary and redundant TDM highways are fully equipped with DSW2/DSWX.
The MMI command reset_device TDM x x brings the BSC from Single Rate Mode to Double
Rate mode when hardware configuration is changed from KSW/KSWX/DSW2/DSWX to ALL
DSW2/DSWX.
{22169}
Feature description
This feature provides support for expanding the number of Multiple serial interfaces (MSIs)
from 56 to 96 and additional E1s between the BSC and the BTSs, RXCDR(s), and PCU.
This allows for a greater fan-out on the links to the BTSs, allowing the BSC to support 12 MSIs
per cage on 8 cages. It also paves the way for additional call capacity if the BSC is modified to
support additional erlangs.
4-114 68P02901W01-S
Jul 2008
System Information: GSM Overview RSL dimensioning statistics
{22266}
Feature description
This feature provides new RSL dimensioning statistics generated by the BSS to monitor network
and system events.
RSL dimensioning statistics provide an indication of RSL link utilization. Two RSL raw statistics,
RSL_TX_OCTETS and RSL_RX_OCTETS provided by the BSS enable the operator to determine
the octets sent over the Abis interface. Both, 16k and 64k RSL links are supported. Another new
raw statistic, RSL_LINK_INS indicates the RSL link in-service duration.
{22415}
Feature description
The Increase the PCU database capacity feature allows an explicit request for more PDCH
for use by the PRP/PXP resources than are equipped in the database.
The PCU maps GPRS capable cells to PRPs activating and de-activating PDCH resources in
response to changes in the system (devices going INS, OOS, changes in cell demand, and so on)
with the objective of maximizing GPRS performance.
The PCU(CB) performs the cell balancing algorithm between cells mapped to a PRP instance at
a multiple of the rate at which it is performed between PRP instances. The rate at which cell
balancing is performed between PRP entities is maintained at the legacy duration of 20s.
{23306}
Feature description
This feature provides CPU utilization overload protection for the BSP. It monitors the BSP CPU
utilization in real time. When the BSP CPU utilization crosses the overload threshold with heavy
call load, the feature starts controlling the number of calls and handovers handled by the
system, so that the CPU utilization of BSP is maintained at a safe level. The feature ensures that
the BSP works reliably even at 90% CPU utilization when the system receives excessive number
of calls and handovers that exceed the maximum processing capability of the BSP.
The feature is triggered automatically when the BSP goes into CPU overload state. The operator
can enable or disable by changing the value of database element bsp_overload_protection.
68P02901W01-S 4-115
Jul 2008
TDM Availability Enhancements Chapter 4: BSS Software Release Features
{25002}
Feature description
This feature enhances the existing fault recovery and detection mechanism of the TDM buses
in the BSC and the RXCDR. This feature is supported only by configurations with expansion
TDM sites.
On detecting a fault in the active KSW/DSW2 expansion matrix, the system swaps to the
redundant TDM highway without waiting for the OMC to initiate the swap. The primary TDM
highway changes to EU state.
This feature also allows the automatic swap to the redundant TDM highway at a specified time
on a daily basis. If no fault is detected, the redundant TDM highway will be continued to be
used. When the redundant highway fails, the system swaps back to the primary highway.
NOTE
Avoid swapping to the redundant highway when audit on the current TDM and/or
KSW is scheduled to occur.
4-116 68P02901W01-S
Jul 2008
System Information: GSM Overview Software patching
Software patching
{25423}
Feature description
Software Patching allows processes running on any executive/exec API supported processors to
load a software patch without resetting or restarting the processor.
A software patch allows changes to be applied to a process in active status. This feature allows
small object changes to be downloaded and updated in real time without board or network
element outage. Certain software problems can be fixed on the system quickly, without causing
any system outage.
A patch level corresponds to a patch, which resolves a single problem or an SR. A patch object
contains one or more patch levels compiled together into an object. A patch object is identified
by a unique code object number, that is, object number 251.
Applying higher patch level also applies all lower patch levels on the BSS. For example,
installation of patch 4 installs patches 1 to 4 on the BSS.
A new version of patch object for the same point release is generated accumulatively from the
previous version of patch object. The new version of patch object contains all software patch
levels from the previous version of patch object. New patch levels are built on top of the patch
levels from the previous version of patch object.
In pre-GSR9 versions of the BSS, all network entities reset in order to upgrade to the new
load. In GSR9, the BSS determines the type of upgrade and communicates it to the OMC. The
type of upgrade is one of:
Full BSC reset (which may or may not include patch object update and/or patch level
update).
PCU upgrade only (which may or may not include patch object update and/or patch level
update).
The BSC communicates the type of upgrade to the OMC. The OMC acknowledges with the
type of upgrade desired by the user.
The BSS continues to process voice calls and GPRS data sessions until the upgrade type is
received by the OMC. The entire BSC is reset only if Full BSC Reset is chosen. Otherwise, if
only a PCU upgrade is required, the BSC directs the PCU to reset and loads the new software,
and the BSC does not reset. Voice calls are not impacted during PCU upgrade.
When Patch Object Upgrade is acknowledged by the OMC, if a new patch object was loaded
with the CSFP download, the patch object is distributed to all network entities.
NOTE
If a patch level install fails at the BTS, then patch level will be reverted to level 0
on all other BTS.
68P02901W01-S 4-117
Jul 2008
PCU Software Upgrade without BSC Outage Chapter 4: BSS Software Release Features
{25424}
Feature description
Before GSR9, a new release of PCU software always caused a full BSC reset, even without any
change to the BSC software load. The PCU Software Upgrade without BSC Outage feature
allows the load of new software release on the PCU without impacting the BSC. Voice calls are
not affected and only GPRS calls drop while the PCU upgrade occurs. This enables to upgrade
the PCU service packs without impacting voice call revenue.
The system uses CSFP download and swap procedure to support this functionality. The BSC
recognizes that the BSC objects are not changed. Therefore, the BSC does not reset during
PCU software upgrade. The PCU downloads the software to CSFP in background mode and
swaps code objects after CFSP code download is complete.
{25867}
Feature description
This feature provides modified drop call statistics generated by the BSS to monitor network
and system events.
The new drop call rate classes statistics automatically give the cause for a dropped call on
both TCH and SDCCH. The existing statistics RF_LOSSES_TCH, RF_LOSSES_TCH_HR
and RF_LOSSES_SD are modified to give more details for the dropped call. When a call is
terminated because of RF problems on TCH or SDCCH, BTS implements an algorithm to
determine the cause for the dropped call. The drop call classification algorithm analyzes the
latest measurement report to ascertain the cause for the call being dropped.
4-118 68P02901W01-S
Jul 2008
System Information: GSM Overview Support for Horizon II Micro, Extended Range for Electronic
IDs of Cabinet Power Supplies, Software support for High power Horizon II Micro
{26481}{29241} {30365}
Feature description
FR26481 introduces a new platform constraint into GSR9, if the operator needs to explicitly
identify the cabinet type as Horizon II micro. Two new cabinet subtypes, HORIZON2MICRO,
and HORIZON2MICRO_EXT, are introduced for this purpose.
The software allows the operator to equip only Opto alarms 1 to 6 to EAS at Horizon II
micro master and extension cabinets. If the operator attempts to enable an alarm in the PIX
range 7-16, software aborts the EAS equipage. A mismatch of PIX inputs and EAS database
information occurs if the operator modifies a cabinet subtype to or from Horizon II micro. The
software forces the EAS to be unequipped before a cabinets subtype is modified. The software
reads PIX inputs through the CTU2 and alarm card; hence both these FRUs must be in service
to determine cabinet type.
FR29241 adds software support to read the PSU vendor electronic ID in a Horizon II macro,
mini or micro cabinet. It supports the modified alarm to provide the manufacture ID of BCUP
for all Horizon II-derivative cabinets containing CTU2. The range of manufacture ID of BCUP
is extended from 7 to 15 for each BCUP type (AC, DC28v, DC48v). This feature provides an
easy way to manage the power supply unit.
FR30365 introduces a new version of Horizon II micro cabinet which can reach full power.
Hardware differences with the standard Horizon II micro cabinet include a dongle, which is
used to identify a Horizon II micro cabinet as a high-power version and also a more powerful fan
unit, as the standard cabinet cannot dissipate heat quickly enough to maintain full power. The
cabinet type is detected by the software through reading the PIX ports that are controlled by the
dongle. A new FRU type H2MICRO_HIGH_PWR is used for high-power Horizon II micro cabinet.
High-power Horizon II micro BTS supports all Horizon II micro functionality. The maximum
power output of CTU2 in a high-power Horizon II micro cabinet can reach 63 Watts for single
density and 2X20 watts for double density.
This feature provides a unique identifier to determine which cabinets are standard power
Horizon II micro and which are the high-power variant of Horizon II micro. The standard power
Horizon II micro supports 2 W per carrier in double density mode. The high-power variant
supports up to 20 W per carrier in double density mode or 63 W in single density mode.
68P02901W01-S 4-119
Jul 2008
PCU high bandwidth interconnection Chapter 4: BSS Software Release Features
{26740}
Feature description
This feature includes the support of the PSI into the current GSM BSC product. The PSI
interfaces are used to connect the GSM BSC to the PCU. The PSI occupies an MSI slot in the
current BSC cage, restricted to slots 13, 12, 7 and 6. Instead of using two MSIs to allow up to
120 timeslots of EDGE data, one slot is occupied by a PSI to allow up to 320 timeslots of EDGE
data. A PSI can process 480 timeslots of EDGE data itself, and the constraint lies in TDM
highway timeslot allocation. The freed MSI slot can be used for 2 downstream or upstream span
lines. The PSI provides an Ethernet link from the BSC to the PCU.
PSI has an MPC8260 controller with 17 56311 DSPs. The MPC8260 controller (MCU) has the
following functions:
Code-loading for all DSPs.
The MCU also has access to the TDM bus through its communication processor HDLC ports.
The feature supports the GSL over Ethernet. To establish a GSL, the software sets up TDM
connection between LCF HDLC channel and MCU HDLC channel through the KSW. As each
GSL can be identified by (IP+UDP port) on the Ethernet, the MCU sets up an internal router
between the HDLC channel and the UDP port.
The feature introduces an ALIVE protocol between the PSI and PXP. The ALIVE protocol uses
UDP frame and the default UDP port 0xE300. The ALIVE protocol is used by both PSI and PXP
to detect alive status of peer side. When the BSC and PCU detect the Ethernet connection on
one PSI/PXP board, they will automatically try to establish the ALIVE protocol for the board. The
connection status of ALIVE protocol also represents the state of GDS equipped on the board.
The ALIVE protocol can also provide ability to detect exceptional reset of remote board and GDS
locking operation from remote. It can also provide BSC the ROM-RAM status of PCU.
Two new device types are introduced by this feature. One is PSI and another is ETH. The PSI
is a child device of CAGE, and ETH is a child device of PSI.
4-120 68P02901W01-S
Jul 2008
System Information: GSM Overview 4-Branch receive diversity
{27236}
Feature Description
The 4-branch receive diversity feature provides the BSS an ability to support configuration of 4
branch receive diversity for each DRI (Digital Radio Interface).
The BSC supports the configuration of 4 branch receive diversity through the DRI diversity_flag
database parameter.
The BSC allows the configuration of a single cabinet with 4 branch receive diversity. The BSC
also allows the configuration of a dual band cell with 4 branch receive diversity capability
with the restriction that the cell contains multiple single band cabinets, one or more of each
frequency band type. For example, a dual band cell could consist of one or more 900 and one or
more 1800 Horizon II Macro cabinets, each of which contains DRIs configured for 4 branch
receive diversity.
The BSC allows the co-existence of dual band cabinets, single band cabinets with 4 branch
receive diversity configured DRIs, single band cabinets without 4 branch receive diversity
configured DRIs in the same site.
NOTE
Dual band and 4 branch receive diversity configurations are mutually exclusive
on a per cabinet basis because both require different SURF and cable harness
modules.
The non-4 branch receive diversity configured cabinets can be any Horizon II
or legacy cabinet type.
Dependencies
The BSC allows 4 branch receive diversity configuration on DRIs only within a single
band Horizon II Macro cabinet.
The BSC allows 4 branch receive diversity configuration only on a CTU2 transceiver
operating in single density mode.
68P02901W01-S 4-121
Jul 2008
Quality of Service PhaseII Feature Chapter 4: BSS Software Release Features
{27703A}
Feature description
This feature is an enhancement of the GSR8 QoS feature. This feature includes the following
components:
Support for Streaming Traffic Class: Support for Streaming Traffic Class allows the
operator to specify a service that requires constraints on delay and jitter as well as
minimum bit rate. Support for PFCs requesting streaming traffic class can be enabled or
disabled using the streaming_enabled BSS parameter. If support for streaming traffic
class is disabled, BSS will still try to admit the streaming traffic classes as one of the
matching interactive traffic classes, determined based on the MTBR settings.
Support for Maximum Bit Rate enforcement: Maximum Bit Rate enforcement allows
the BSS to throttle the throughput of user to the maximum bit - rate stated in the QoS
parameters (ABQP) even if there is capacity to provide the user a higher throughput.
Controlling triggering of PFM messaging to SGSN when a non-real time PFC is downgraded
or upgraded due to admission control or retention.
The DELETE-BSS-PFC.REQ PDU and the associated procedures defined in the 3GPP R6
specifications is also supported. BSS sends this PDU when it deletes or preempts a PFC.
This feature is a restricted feature and requires the GPRS QoS feature to be unrestricted.
The BSS is enhanced to include changes based on R6 standards. The key modification is the
ability of the SGSN to communicate the Allocation and Retention Priority (ARP) using the ARP
Information Element (IE) as a part of the BSS Create PFC procedures. If this information
element is received, the BSS considers the priority level of the requested PFC when deciding
on the resource allocation. If the ARP IE is not provided in the Create PFC PDU by the
SGSN, parameters are provided to configure the ARP based on precedence class for all traffic
classes/PFCs for which the BSS does not receive the ARP IE from the SGSN.
4-122 68P02901W01-S
Jul 2008
System Information: GSM Overview Support of RESUME at intra-BSC level
{27717}
Feature Description
The Support of RESUME at intra-BSC level feature provides BSS system, the flexibility to
suspend or resume GPRS services. The MS requests the network for suspension of GPRS
services by sending Suspend message to the network when:
A GPRS-attached MS enters dedicated mode and the support of Class A mode of operation
is not possible.
An MS in class A mode of operation is handed over to a cell where the support of Class A
mode of operation is not possible.
The BSC tracks the MS status as Suspended when it receives Suspend Ack message from
the SGSN. If the BSS detects that the conditions for the GPRS suspension have disappeared
for an MS in suspended state and there is no RA change, the BSS sends a Resume message
to the SGSN to resume GPRS services. If a Resume Ack is received from the SGSN, the BSS
sends a Channel Release message with a GPRS Resumption bit to the MS, to notify the MS
to resume GPRS service.
The MS resumes GPRS services by sending a Routing Area Update Request message to
the SGSN in the following cases:
If the BSS fails to request the SGSN to resume GPRS services.
If the RR Channel Release message was not received before the MS left the dedicated
mode.
If the MS locally determines that the conditions for the GPRS suspension have disappeared.
The bssgp_t4_timer starts when the BSS sends either Suspend or Resume request to the
SGSN. After the timer expires, the BSS restarts the timer and resends the message. The BSS
aborts Suspend or Resume requests after three attempts.
When the lower level calls are preempted, BSS initiated resume procedure is not initiated
due to the performance of eMLPP.
68P02901W01-S 4-123
Jul 2008
Software support for High Bandwidth and/or existing E1 BSC/PCU interconnect Chapter 4: BSS Software Release Features
{27955A}
Feature Description
This feature provides backward compatibility for GSR9 software. It allows network operators
to reuse existing DPROC hardware in the PCU. The GSR9 software treats the U-DPROC2 as
legacy DPROC. It also has a mixed mode operation (old DPROCs working with new U-DPROC2
boards). This feature disables the 3xPCU feature.
This feature supports two deployment modes when U-DPROC2 and legacy DPROC are used at
the same time in the PCU.
In the first mode of deployment, the U-DPROC2 serves as a PRP or PICP just as legacy DPROC.
The PRP capacity/throughput is 280/70 in this mode (with rolling blackout mechanism). The
PRP capacity/throughput is 140/140 with the rolling blackout mechanism disabled. Therefore,
capacity is reduced for increased throughput. All connectivity between the BSC and PCU
is through E1 links.
GSR 9 supports one PCU equipped at a BSS to provide the necessary functionality for
GPRS/EGPRS. When a PCU is equipped, a corresponding cabinet and cage device are
automatically equipped.
It allows both legacy DPROCs and U-DPROC2s to coexist and operate within the same
PCU shelf.
It supports and provides for hardware upgrade from legacy DPROC to U-DPROC2 board.
The BSC supports the same alarms, device states, statistics generated on legacy MSI board for
E1 BSC-PCU connectivity.
4-124 68P02901W01-S
Jul 2008
System Information: GSM Overview LCF Memory saving to prolong the life of existing GPROC2
Dependencies
{27962}
Feature Description
The increase in the capacity of the BSC in terms of carriers, sites, CICs, and so on requires
additional memory for the database object and the normal increase in object sizes due to
addition of functionality in feature releases. With this feature, the system will not load PSI or
PCU objects, onto a GPROC2 during initialization of board or BSC. This prevents the failure of
GPROC cross load due to the GPROC2 being out of memory. This feature also removes some
of the BTS objects from each of the GPROC2-LCFs in order to save memory, so processes
can be run on these LCFs.
As the GPROC2 no longer stores PSI or PCU objects, the source must be a GPROC3 when
GPROC cross load is done using LAN broadcasting mode since it contains all the BSS objects.
While cross loading from GPROC2 to GPROC3, GPROC3 has highest priority. But when GPROC2
is chosen, the BSC uses two GPROCs as the source. One GPROC2 is used as the load controller
and the other, which must be GPROC3, is used as a second source.
NOTE
A GPROC can be assigned as the second source multiple times but can be the
controlling source for only one download session at a time.
68P02901W01-S 4-125
Jul 2008
Increase the throughput of PRP with the PCU Chapter 4: BSS Software Release Features
{28000}
Feature description
The current PRP processor has a fanout/throughput of 120/30 PDCHs. A rolling blackout
mechanism determines which 30 of the 120 PDCHs is serviced in any 20 ms block period.
This feature provides an option to disable the rolling blackout mechanism on the PCU so that
the throughput of the PRP processor is the same as the fanout of the PRP.
A new database parameter, prp_fanout_mode is introduced in this feature to support two types
of PRP fanout mode. In mode 1, with rolling blackout mechanism enabled, a maximum of the
total In Service timeslots in a PRP are allowed to perform data transfers in each direction for
every block period. Refer to Table 4-37. In mode 2 with rolling blackout mechanism disabled, a
maximum of total In Service timeslots in a PRP can transmit data in each direction for every
block period. Table 4-37 depicts the detailed processing capacity in mode 1 and 2. As a new
hardware U-DPROC2 is introduced in GSR9, PXP configured by this new board has much higher
capacity and throughput.
{28333}
Feature description
This feature increases the efficiency of the LAN by reducing the number of messages sent. It
allows the BSC to support 180kBHCA under the GSR9 call model.
4-126 68P02901W01-S
Jul 2008
System Information: GSM Overview HSP MTL
HSP MTL
{28337}
Feature description
The restricted HSP MTL (High Speed MTP Transport Layer Link) feature offers enhanced
capacity and flexibility of MTL. The BSC implements this feature. It increases the capacity of
MTL from 64k to 2M to support huge BSC configurations and the BSC supports High Speed
MTL (HSP MTL) link utilization maximally at 13%.
This feature introduces one new timer, ss7_hsp_l2_t1. The ss7_hsp_l2_t1 timer is used for
signaling link alignment procedure called Timer alignment ready in ITU Q703.
NOTE
FR28337 is only supported when GPROC3-2 is available at BSC for hosting HSP LCF.
This feature is depended on FR28398 Increased Network Capacity.
{28340}
Feature description
The BSP CPU Utilisation Improvement feature supports a call load of 180K BHCA (96s call
duration). This is to improve the CPU utilization at the BSP by improving the efficiency of the
Ater allocation algorithm.
With the memory restriction removed, the CPU efficiency can be improved at the cost of higher
memory usage. A list-based Ater search algorithm allocates resources when a new call (mobile
originated, mobile terminated, external handover from MSC), CIC remap or Ater switchover is
initiated and also for an existing call with rate change. The Aters are allocated from the top
of the available lists to minimize the search. This enables the BSC to assure that the mean
BSP CPU utilization does not exceed 70%. The new Ater search algorithm is provided with a
mean computation complexity of O(1). The list searching enhancement also applies to internal
handover where the backhaul rate changes when the Allocation Manager process is called
for a CPU intensive task.
68P02901W01-S 4-127
Jul 2008
Addition of new PCU hardware to increase GPRS capacity Chapter 4: BSS Software Release Features
{28351}
Feature description
This feature increases the GPRS capacity on the current PCU and BSC hardware platform by
introducing a new board, Universal DPROC-2, (U-DPROC2). Accordingly, it also introduces a
new rear transition module U-DPROC2 RTM as a new replacement board for the PCU.
Each U-DPROC2 is mated with a U-DPROC2 RTM. Pairing a U-DPROC2 board with a legacy RTM
module or pairing a legacy DPROC board with a U-DPROC2 RTM module is not supported. The
U-DPROC2 replaces existing DPROC and creates new functionality called PXP which combines
PRP and PICP functionality on the same board.
A U-DPROC2 serving as PXP supports a 1000BASE-T or CAT-5e link from the PCU to the BSC
completing connection to the new PSI board.
Also, the U-DPROC2 can coexist with legacy DPROC which serves as PRP or PICP. U-DPROC2
can function as PRP or PICP.
U-DPROC2 PXP supports IPv4 and UDP protocols for Ethernet connection to PSI board at the
BSC. Therefore, both TRAU data and GSL signaling are transported over IP/UDP protocol
between U-DPROC2 and PSI when U-DPROC2 serves as a PXP.
The U-DPROC2 uses more power than the original DPROC. To ensure that the U-DPROC2 can
be used in the same functionality of the DPROC card without any additional power and cooling
considerations, the core frequency of the U-DPROC2 processor is scaled back to reduce power.
This mode is used while operating in PICP and PRP mode of operation.
While operating the U-DPROC2 in PXP mode, the card is operated in full 1GHz mode. Additional
baffling is added to the cabinet supporting the PCUs to increase the cooling capacity.
4-128 68P02901W01-S
Jul 2008
System Information: GSM Overview Increased Network Capacity
{28398}
Feature description
The optional feature, Increased network capacity enhances the network capacity and
supports database capacity up to 8 MB.
The Maximum number of sites that a BSC supports increases from 100 to 140.
The Maximum number of circuits that a BSC supports increases from 3200 to 4800.
The maximum number of BSC-XCDR connectivity that a BSC supports increases from
27 to 42.
This feature has an impact on the collection and dispatch of the additional statistics due to the
increased number of managed objects. The upload and collection of statistics to the OMC takes
place at 30 or 60 minute intervals, and completes in 20 minutes.
{28938}
Feature description
This feature is to provide the option to restrict the use of Incell BTS sites within a network if
required. During the database upgrade (that is, upgrading GSR8 database to GSR9) the system
does not allow any Incell site to be equipped in the database unless the customer has purchased
this feature. This feature would also restrict the adding of Incell hardware if the option has
not been purchased.
The IncellOpt parameter indicates whether the Incell Support feature functionality is
unrestricted in the BSS software.
68P02901W01-S 4-129
Jul 2008
CTU2D Chapter 4: BSS Software Release Features
CTU2D
{30828}
Feature Description
This feature introduces CTU2D radios that can support both SD (Single Density) and DD
(Double Density)) EDGE architectures. This is an optional feature. The CTU2D radio supports
the following EDGE modes:
CTU2D SD: This mode is identical in operation to the existing CTU2 SD.
CTU2D PWR: This mode is also known as ITS mode as the operation is identical to that of
CTU2 in ITS mode.
CTU2D CAP: In this mode, carrier A is fully EDGE capable and carrier B supports
GPRS/TCH. No timeslot blanking is required.
The CTU2D in Capacity mode enables the BTS to support BBH for GMSK carriers assigned to
carrier B irrespective of the EDGE capabilities and PD support for carrier A.
The Capacity mode is only applicable to the new CTU2D radio platform. As it is not possible to
detect the radio platform in all scenarios, radio configuration mismatch handling is enhanced to
support the new mode as follows:
When a non-CTU2 radio is configured in Capacity mode, it remains OOS.
When a CTU2 is configured in Capacity mode, it assumes double density behavior but
with EDGE restriction.
This feature introduces a new parameter, ctu2dcapopt. The ctu2dcapopt parameter indicates
whether the CTU2D Capacity feature is restricted or unrestricted in the BSS. The range of
the dri_density parameter is extended to 3.
Dependencies
4-130 68P02901W01-S
Jul 2008
System Information: GSM Overview TD-SCDMA and GSM interworking feature
{31400}
Feature description
NOTE
When TD-SCDMA and GSM interworking is disabled if the feature is restricted, all
functions described above will not be available.
When TD-SCDMA and GSM interworking is enabled, the user can add/change/delete/display
TD-SCDMA neighbor list from BSS MMI or from OMC-R.
{32173}
Feature description
68P02901W01-S 4-131
Jul 2008
Cell OOS Enhancement Chapter 4: BSS Software Release Features
{32340}
Feature description
This feature introduces an operator configurable delay to postpone system information update
message for System Information types 1, 2, 2bis, 3 and 4 to the MS when a BSC is undergoing
reset during master BSP failover. This delays cell reselection procedure by the MS during
a global reset.
This feature is designed to extend the time the MS remains on the network undergoing a reset
procedure and enables the operator to maintain roaming subscribers.
Call processing at the BSS is responsible for the delay of system information update message to
the MS when the BSS is undergoing reset. OMC is responsible for providing the mechanism to
configure value of the delay.
A new database parameter cell_barred_delay specifies the delay of cell bar information to the
MS. The BSS parameter specifies the time the BSS delays sending SystemInformationUpdate
message to the MS during global reset procedure.
{30830}
Feature description
This is an optional feature which enables EDGE capability on both DRIs of the CTU2D. This
feature can be supported only on Horizon II macro, Horizon II micro and Horizon II mini sites.
In the asymmetric mode, carrier A is fully EDGE capable and carrier B supports EDGE on the
downlink and GMSK on the uplink. Same timeslots on both the carriers cannot support 8PSK
simultaneously. The asymmetric feature requires the remapping of the internal TDM allocations
to provide two EDGE carriers. Hence, BBH support for EDGE is removed for the entire site.
The CTU2D can process only GMSK coding schemes in uplink on timeslots of Carrier B when
the corresponding timeslot on Carrier A has an uplink 8PSK capable TBF. Hence, an EGPRS
MS cannot use MCS 5-9.
Call processing at the BSS is responsible for the delay of system information update message to
the MS when the BSS is undergoing reset. OMC is responsible for providing the mechanism to
configure value of the delay.
This feature introduces two new parameters, ctu2dasymopt and asym_edge_enabled. The
ctu2dasymopt parameter indicates whether the CTU2D asymmetric feature is restricted or
unrestricted. The asym_edge_enabled parameter enables or disables asymmetric EGPRS for
CTU2D on per SITE basis. The CTU2D asymmetric feature must be unrestricted to enable
this. The site cabinets have to be Horizon II macro, Horizon II micro, Horizon II mini.
Dependencies
The asymmetric EDGE feature requires the EGPRS feature and the CTU2D Capacity feature to
be unrestricted.
4-132 68P02901W01-S
Jul 2008
System Information: GSM Overview UL Retransmission Measurement
UL Retransmission Measurement
{33863}
Feature description
This feature provides an accurate method to calculate the UL RLC abnormal retransmission
rate on a cell basis. This feature introduces two statistics UL_RLC_NACK_BLKS and
UL_RLC_STALLED_BLKS, which are used to calculate the UL RLC retransmission rate.
In addition, these statistics are used to distinguish the reason for the retransmissions, and
obtain the overall and specific retransmission ratios.
68P02901W01-S 4-133
Jul 2008
BSS software release GSR9 FP1 Chapter 4: BSS Software Release Features
Table 4-38 summarizes the features provided at software release GSR9 FP1.
Table 4-38 Release GSR9 FP1 features
Description
{34145} Support the display of GPRS resource allocation per PCU.
{34144} Support the usage of idle TCH for packet burst traffic.
{31565} Support a switch and additional stats for AGCH flow control.
{33397} Add paging discard stats for RCC feature related link.
{26881} Support for Release 6 based Extended Uplink TBF mode.
{23292} Support for the extended dynamic MAC mode at the air
interface.
{27703A} Quality of Service Phase II Feature.
{34145}
Feature description
The main function of this feature is to display the actual PDTCH and backhaul configuration for
each cell per PCU and per PRP/ PXP DPROC and PPROC level. This feature provides information
on the GPRS configuration per PCU side to facilitate the GPRS configuration and deployment.
The MMI command disp_equipment displays the actual cell GPRS configuration information
per PCU and PRP/PXP level along with the existing equipment information. When full option
is set on disp_equipment command, it displays the actual PDTCHs configuration and the
information of whether all requirements are satisfied at cell level for all the cells belonging to
this PCU or PRP/PXP DPROC or PPROC board.
NOTE
To display the actual PDTCH and backhaul configuration, update the message from
PRP to PCU CB for the cell PD configuration status and use the message from MMI to
PCU CB.
4-134 68P02901W01-S
Jul 2008
System Information: GSM Overview Support the usage of idle TCH for packet burst traffic
{34144}
Feature description
Reserved PDTCH channels and Switchable PDTCH channels are used for GPRS traffic. Without
this feature, TCH channels are used only for voice call traffic and cannot be used for GPRS traffic.
This feature introduces a mechanism which allocates the idle TCH channels as additional
switchable PDTCH resource when there is GPRS traffic congestion in a cell. It returns these
PDTCH resources back to the TCH resources when the GPRS traffic congestion is relieved. The
additional switchable PDTCH resources are defaulted as TCH resources which have no impact
on normal voice call.
This feature is available only for EDGE enabled cell (at least one 64k PDTCH available in the
cell). The number of additional switchable PDTCHs are calculated based on the EDGE carrier
configuration.
{31565}
Feature description
This feature allows the user to manually enable or disable Access Grant Channel (AGCH) flow
control. The users can enable AGCH flow control on the required cells and disable the AGCH
flow control on other cells based on different network situations.
This feature provides the users with the option to avoid frequent triggering of AGCH overload
due to the trigger of Immediate Assign Reject (IAR). It also adds additional counter array stats
to monitor the number of Immediate Assign (IA) or IAR messages sent over CCCH or discarded
when AGCH overload respectively.
The BSS supports a per cell element _cell_data, 20 which indicates whether the functionality of
the AGCH flow control is enabled or disabled. It also specifies the triggers associated with IA
or IAR that can trigger the AGCH overload.
When the functionality of AGCH flow control is disabled, the overall flow control works by
appropriately configuring other parameters that affect RACH/TCH/SSM flow control.
NOTE
To make the overall functionality of flow control efficiently on system level, it is
recommended that at least one flow control must be enabled and work well.
68P02901W01-S 4-135
Jul 2008
Add paging discard stats for RCC feature related link Chapter 4: BSS Software Release Features
{33397}
Feature description
This feature provides a mechanism to count the number of paging messages discarded from a
specific point between the A interface and Air interface, for Network Operation Mode II (NOM2)
and Network Operation Mode III (NOM3).
{26881}
Feature description
The feature introduces two new parameters, ext_ul_dur and ext_utbf_nodata. The ext_ul_dur
parameter determines if the feature is enabled or disabled and the duration of the Extended
Uplink TBF. The feature is disabled when ext_ul_dur is set as 0 and is enabled when it is set
within a range of 24 to 250. The maximum duration of Extended Uplink TBF is 5 seconds (250
data blocks). The uplink TBF is released when ext_ul_dur expires.
The ext_utbf_nodata parameter determines whether R6 mobile sends UL Dummy Control Block
or not during Extended Uplink TBF mode when USFs are assigned for the mobile. When the
ext_utbf_nodata is set as 0, R6 mobile sends UL Dummy Control Block during Extended Uplink
TBF period. When the ext_utbf_nodata is set as 1, R6 mobile does not send UL Dummy Control
Block during Extended Uplink TBF period.
4-136 68P02901W01-S
Jul 2008
System Information: GSM Overview Support for the Extended Dynamic MAC mode at the air interface (EDMAC)
{23292}
Feature description
The EDMAC feature is introduced to support class 11 and 12 mobiles with 3 and 4 UL (uplink)
timeslots capability. When 3 or 4 uplink timeslot allocation is assigned, EDMAC is required
for the request uplink TBF.
This is an optional feature for the network. When a class 11 or 12 mobile requests an uplink
TBF, the network assigns the EDMAC for the uplink TBF if the mobile supports EDMAC and the
TBF allocation requires EDMAC mode. The network assigns the lowest numbered timeslot in
the allocation as PACCH timeslot.
The PCU attempts to assign three timeslots to the EDA capable class 11 and class 12 mobile if
gprs_ul_dl_bias is set to UL bias. During the uplink TBF in EDMAC, the network schedules
USFs in the lowest or the second timeslot in the allocation, the mobile station transmits a
single RLC/MAC block on the same PDCH and all higher numbered assigned PDCHs. The PCU
schedules periodic PUAKs for 3 or 4 UL TBFs frequently enough to prevent stalling dependent
on number of uplink timeslot (3 or 4) used and GPRS or EGPRS TBF mode.
The EDMAC feature increases the users throughput in UL (for example, video and email
uploads) with ability to support 3 and 4 UL timeslots.
Dependencies
The Extended Dynamic Allocation feature requires the GPRS feature to be unrestricted.
The gprs_mac_mode parameter enables the support of Extended Dynamic Allocation (EDA)
when set to 2.
The edaOpt parameter indicates whether or not the Extended Dynamic Allocation feature
functionality is unrestricted in the BSS software.
UL_RADIO_BLKS_GMSK_4_TS
UL_RADIO_BLKS_8PSK_4_TS
UL_RADIO_BLKS_GMSK_3_TS
UL_TBF_TIME_GMSK_3_TS
UL_TBF_TIME_GMSK_4_TS
UL_TBF_TIME_8PSK_3_TS
UL_TBF_TIME_8PSK_4_TS
68P02901W01-S 4-137
Jul 2008
Quality of Service Phase II Feature Chapter 4: BSS Software Release Features
{27703A}
Feature description
This feature is an enhancement of the GSR9 QoS feature. This feature includes the following
components:
Support for Streaming Traffic Class: Support for Streaming Traffic Class allows the
operator to specify a service that requires constraints on delay and jitter as well as
minimum bit rate. Support for PFCs requesting streaming traffic class can be enabled or
disabled using the streaming_enabled BSS parameter. If support for streaming traffic
class is disabled, BSS will still try to admit the streaming traffic classes as one of the
matching interactive traffic classes, determined based on the MTBR settings.
Support for Maximum Bit Rate enforcement: Maximum Bit Rate enforcement allows
the BSS to throttle the throughput of user to the maximum bit-rate stated in the QoS
parameters (ABQP) even if there is capacity to provide the user a higher throughput.
Controlling triggering of PFM messaging to SGSN when a non-real time PFC is downgraded
or upgraded due to admission control or retention.
The DELETE-BSS-PFC.REQ PDU and the associated procedures defined in the 3GPP R6
specifications is also supported. BSS sends this PDU when it deletes or pre-empts a PFC.
This feature is a restricted feature and requires the GPRS QoS feature to be unrestricted.
The BSS is enhanced to include changes based on R6 standards. The key modification is the
ability of the SGSN to communicate the Allocation and Retention Priority (ARP) using the ARP
Information Element (IE) as a part of the BSS Create PFC procedures. If this information
element is received, the BSS considers the priority level of the requested PFC when deciding
on the resource allocation. If the ARP IE is not provided in the Create PFC PDU by the
SGSN, parameters are provided to configure the ARP based on precedence class for all traffic
classes/PFCs for which the BSS does not receive the ARP IE from the SGSN.
4-138 68P02901W01-S
Jul 2008
Chapter
This chapter provides a summary of the features of Motorola OMC-R software releases. Releases
of software before GSR2 were identified by four-digit release numbers, such as 1.2.1.1. After
the 1.4.1.x release, the numbering system was revised; release 1.5.0.x was renamed GSR2.
68P02901W01-S 5-1
Jul 2008
Quality of Service Phase II Feature Chapter 5: OMC-R Software Release Features
5-2 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release 1.1.2.0
Configuration
A timeout variable for the supervision of IPC response messages from both CM and LM
(Uploader).
Two versions of tabular key statistics reports, together with an interactive graph option.
Filename.bad_header.
Filename.FATAL_ERROR.
Fatal errors cause the Parser to terminate (For example, unable to connect to db).
The parser expects a DURATION field in file headers. Durations of plus or minus 5 seconds
are accepted for parsing. No other files are parsed.
An MMI printer command is provided, and the ability to change the font of text in
Subscription List windows.
68P02901W01-S 5-3
Jul 2008
Release 1.1.2.0 features Chapter 5: OMC-R Software Release Features
The Event Interface subsystem generates a critical alarm for all Network Elements (NEs)
in the network as reported by CM on system start up. It generates a clear alarm for each
NE link brought into service, that is, for each link for which a connect request is received.
Subsequent link failures or recoveries are accompanied by corresponding alarms and
clears. In addition, whenever a link goes down or comes up, a message is written to the
OMC-R audit file indicating the current time and the NE device ID associated with the link.
5-4 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release 1.1.2.1
Configuration
MMI Processor
OMC-R Database Schema upgraded to remove some indexes on the PM stats tables.
The OMC-R Watchman script (omc_watchman) provides facilities for monitoring the
OMC-R processes running on the system processor. If any of the OMC-R processes
terminate, it provides facilities for informing OMC-R operators.
The rate at which MMI attempts to process events and what action MMI takes when
flooded with events can be configured through environment variables.
Six new parameters added to the BSS Add Cell command. The Change, Add, and Display
Cell commands modified. The added parameters are:
d1_ncell_proc (0-1)
d1_missing_rpt (0-1)
d1_ba_alloc_proc (0-1)
full_pwr_rfloss (0-1)
d1_sdcch_ho (0-1)
d1_sdcch_timer_ho (0-31)
68P02901W01-S 5-5
Jul 2008
OMC-R software release 1.1.2.2 Chapter 5: OMC-R Software Release Features
Configuration
MMI Processor
Installation: size of logical logs increased, number of logical logs decreased, size of
physical logs increased.
Manually handled and cleared alarms are written to the event log. The alarm is written to
the log with the current time, new status field, and user name of the operator handling or
clearing the alarm.
NOTE
The original alarm appears with a status field NOT APPL in the event log.
Subscription list sorting: events extracted from AET are displayed in chronological order.
5-6 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.1.2.2 features
Filter CHAN_REQ_MS_FAIL
PM_SD_FILTER
Front End updates for release 1.1.2.2. The OMC release 1.1.2.2 Front End supports both
BSS version 1.1.2.1 and version 1.1.2.2. To change which BSS version is supported, the
BSS_VER environment variable can be set appropriately. A new menu option, Version, has
been added to display the current value of BSS_VER.
Input buffer size for X.25 data in the Event Interface application has been increased from
165 bytes to 1024 bytes.
Logging of messages added to the Event Router and List Manager processes.
68P02901W01-S 5-7
Jul 2008
OMC-R software release 1.1.2.3 Chapter 5: OMC-R Software Release Features
Configuration
Feature Description
load_db and activate_db Two scripts allow the installation from tape
of a NE database, generated on a test BSS
system, on to the OMC-R. The load_db script
reads a NE database from tape and installs it
on the OMC-R. The activate_db script moves
a NE database, installed through load_db,
from the installation directory to the current
database location of a specified NE.
Critical alarm threshold exceeded Supports for MMS alarm. Critical alarm
threshold exceeded to inform the operator
when the critical MMS alarm threshold is
exceeded and the MMS is disabled. The alarm
string is included in MMI MIT data file.
Confirmation dialogues Relates to confirmation of user commands.
Throughout the MMI area for delete and
modify commands and potentially dangerous
commands (for example, Disable Logging)
the operator is prompted with a confirmation
dialogue box. The operator can select OK to
continue or CANCEL to cancel the operation.
Date/time on event logs A date/time stamp written at the start of every
event log file when it is first opened. It is not
visible to the OMC-R operator and is intended
to be used only by event post processing
utilities.
Continued
5-8 68P02901W01-S
Jul 2008
System Information: GSM Overview Additional features
Additional features
Support for new EAS alarm: the alarm Bad Daughter Board ID read - possible bad EAS
board replaced the Bad ID alarm to get output when an EAS board is unseated.
MMI maintains its local list of selectable NEs. There is no need to log out MMI sessions
after deletion of a node.
Potentially separate Subscription Lists for Events and Alarms, configurable using MIT file.
EM router no longer exits on an error return code from the IPC subsystem.
68P02901W01-S 5-9
Jul 2008
OMC-R software release 1.1.2.4 Chapter 5: OMC-R Software Release Features
Configuration
MMI processor
Feature Description
Enhancement for omc_watchman script The omc_watchman script sends a mail
message to the users specified by the
variable MAIL_ADDRESS when an OMC-R
process terminates. The message specifies
which process has terminated. In addition,
watchman.log logs any processes reports on
omcinit, and logs any processes that have
terminated while watchman.live reports
which processes are currently alive.
Disconnecting applications for online DB The OMC-R database can be brought down
maintenance to single user mode for certain types of
maintenance. The applications connected
to the database (EM and PM) can handle
database disconnection and reconnection.
This is to cater for db online maintenance.
5-10 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release 1.2.0.0
Configuration
Feature Description
Display of loads on i-CM modify window As part of the X upgrade to X11R4 the
horizontal scroll bar for the Load Names list
(in the i-CM Node Modify window) is not
included by default. This list is automatically
resized, if possible, and the horizontal scroll
bar is only present when it is not possible to
resize the list.
Graph of raw stats Default worksheets enable the graph option
for all statistics as soon as they become
available.
Command Constructor closing on X.25 Command Constructor closes following
connection break confirmation of X.25 connection break error
message and the Wingz license is freed.
Add alarm strings for transcoder to BSC link BSS Release 1.2.0.0 and the OMC-R support
(XBL) the XBL alarms. The XBL alarms include
twelve hardware alarms and three PM alarms.
The PM alarms are similar to those defined
for RSL and OML devices.
Support XBL stats A parser, database, and PM-UI are provided
to support XBL statistics.
Continued
68P02901W01-S 5-11
Jul 2008
Release 1.2.0.0 features Chapter 5: OMC-R Software Release Features
Continued
5-12 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.2.0.0 features
Continued
68P02901W01-S 5-13
Jul 2008
Release 1.2.0.0 features Chapter 5: OMC-R Software Release Features
5-14 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release 1.2.2.1
Configuration
Feature Description
Network status summary Allows the operator to select a map of all, or
part of the network. The selected map can be
configured to display the Network Elements
(NEs), links in the network and the sites and
links contained within the NE. Maps can be
topological or geographical.
Alarm and state synchronization Provides a mechanism for synchronization
of the OMC-R and BSS/RXCDR device status
at OMC-R initialization time, and after a
failure of the OMC-R or BSS/RXCDR or the
links between them. Status information
is composed of both alarm and device
state information. Synchronization occurs
automatically at a configurable interval.
Audible alarm The OMC-R provides an output to drive
an audible alarm. The output is activated
whenever alarms higher than a programmable
severity are detected. The alarm severity
level is configurable on a system-wide basis
only.
Continued
68P02901W01-S 5-15
Jul 2008
Release 1.2.2.1 features Chapter 5: OMC-R Software Release Features
Continued
5-16 68P02901W01-S
Jul 2008
System Information: GSM Overview Release 1.2.2.1 features
68P02901W01-S 5-17
Jul 2008
OMC-R software release 1.2.2.2 Chapter 5: OMC-R Software Release Features
Table 5-5 summarizes the OMC-R release 1.2.2.2 features to support the BTS6, ExCell6, and
TopCell cabinets.
Feature Description
BSS support activities Provides support for the statistics and alarms
defined by BSS release BSGSM 1.2.2.2.
Auto initiate alarm windows Allows alarm/event subscription windows to
be automatically opened on start up of a MMI
session.
Total calls statistics The key statistic total calls replaces the
existing paging load in the call summary key
statistic.
Forms updates A new parameter called TRU identifier is
added to the EquipDRI worksheet after the
Slot number.
Database management A new script, delete_CELL is added for
deleting cells from the schema. This script
provides similar functionality as the scripts
for managing the deletion of BSS and SITE
information.
5-18 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release 1.2.3.0
Configuration
Feature Description
NMC-OMC-R security application (optional) Supports the optional security application
on the interface to the NMC. The purpose of
this feature is to provide secure access to the
OMC-R through Remote Login over an OSI
Stack.
System administration Provides the necessary procedures and
scripts to install the 1.2.3.0 OMC-R and to
install the SAC application on the OSI and
RLP processors.
BSS support activities Provides support for the statistics and alarms
defined by BSS release BSGSM 1.2.3.0.
Graphical key statistics - save selection Enables the Operator to save the Date and
Time selection and the NE selection.
MMI audit trail - BSS MMIs Stores the commands carried out on the BSS,
from the OMC-R, along with a time stamp.
Rlogin modifications Enables an Operator to remote login to a NE
while a database upload is in progress. The
Operator is warned of the database upload.
Batch based time updates Provides a script which sets the time
automatically at the BSS, controlled by an
OMC-R. The time is set using BSS MMIs.
68P02901W01-S 5-19
Jul 2008
OMC-R software release 1.3.0.0 Chapter 5: OMC-R Software Release Features
The OMC-R software is supplied on one CDROM which includes software for the System
Processor (Tandem), the MMI Processor (SPARC) and the MIB Processor (SPARC). In addition to
the OMC software, the CDROM also contains third-party product software for Solaris patches,
Informix, Motif, and X11R5.
In addition to the OMC-R CDROM, one additional CDROM is supplied with it. The CDROM
contains the Worldview version 2.0.1 software release, and one cartridge tape is supplied
containing the Wingz software release.
Table 5-7 summarizes the new OMC-R software release features for 1.3.0.0.
Feature Description
Network Configuration Augments the BSS configuration data maintained at the
Management (NCM) OMC-R, allows the manipulation of the data from the OMC-R
and supports the synchronization of this data with the BSS. It
centralizes the configuration data at the OMC-R, supports the
logging of changes and creates the infrastructure to support
the creation of BSS binary from the OMC-R.
Code Storage Facility Allows the online download of a new BSS load, from the
Processor (CSFP) OMC-R to the BSS, to support the fast swap over to a new
load, thus reducing BSS downtime. This feature also includes
support for electronic transfer of BSS databases from the
Datagen platform to the OMC-R.
Online help from GSM Provides the OMC-R user with a context sensitive help
documentation facility, covering all aspects of work at the OMC-R, including
information on the BSS.
1.3.0.x systems Provides the mechanisms for doing a clean installation of
administration the GSM OMC-R system or for upgrading a current (1.2.2.
X/1.2.3.0) OMC-R system to the 1.3.0.0 software release.
Utilities for administrating the OMC-R databases and log files
are also included.
Operability enhancements Provides a forms interface to support the following Operation
and Maintenance procedures: Report all out of service
devices. Add devices. Interface to the OMC-R batch facility.
5-20 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release 1.4.0.0
Most of the new features and enhancements to the OMC-R software for 1.4.0.0 are brought
about by the introduction of a revised hardware platform.
New OMC-R systems use the new OMC-R System Processor, the Tandem Integrity S1475, while
existing Tandems are upgraded to UNIX SV.4. (B series OS).
Feature Description
Upgrade of Tandem operating system The OMC-R System Processor Operating
software to UNIX SV.4 (B series) including System (OS) has been upgraded to UNIX SV.4
Veritas file system manager. (B series OS). The OMC-R System Processor
software applications have been ported to
run on this operating system. The B series
Operating System on the System Processor
is fully compatible with the existing Solaris
configuration on the SPARC stations.
Port to Spider X.25. The OMC-R X.25 application has been ported
from TITN X.25 to Spider X.25 on the System
Processor to facilitate the new operating
system. The main impact of this feature is that
the X.25 troubleshooting procedures change.
Dual 64 kbps file upload circuits. Provides support for an additional upload
circuit. This gives the OMC-R two 64 kbps
X.25 circuits for file uploads from the BSS to
the OMC-R. The impact of this feature is that
up to eight simultaneous uploads are now
supported (four uploads was the previous
limit). The extra upload circuit increases
redundancy.
Upgrade of database software to INFORMIX The port to the B operating system also
online 5.0. necessitates a move to Informix 5.0 software
as INFORMIX 4.1 is not supported on the B
series OS.
System Administration Backup menus. The backup menu program handles online
backups, file locking and data consistency as
well as providing an easy to use front end
for both backups and restores across the
network.
Continued
68P02901W01-S 5-21
Jul 2008
Release 1.4.0.0 features Chapter 5: OMC-R Software Release Features
5-22 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release 1.4.0.1
Most of the new features and enhancements to the OMC-R software for 1.4.0.1 are brought
about by the introduction of a revised hardware platform and are identical to the enhancements
described in release 1.4.0.0, so a brief summary is included here followed by the specific
enhancements unique to 1.4.0.1.
New OMC-R systems use the new OMC-R System Processor, the Tandem Integrity 1475, while
existing Tandems are upgraded to UNIX SV.4 (B series OS).
The following items summarize the features of 1.4.0.0 included in release 1.4.0.1:
Upgrade of Tandem operating system software to UNIX SV.4 (B series) including Veritas
file system manager.
Online documentation.
Table 5-9 summarizes the features that are only available from release 1.4.0.1.
Feature Description
Cell parameter propagation Allows the operator, through the CM MIB at
the OMC-R, to change parameters in any Cell
in the GSM network and apply any of those
changes to other Cells in the network.
Neighbor propagation Automatically aligns the settings of some
attributes of the Cell and RTF objects, with
dependent attributes of the Neighbor object
(and also DRI, RTF, and Source objects).
Continued
68P02901W01-S 5-23
Jul 2008
Further features of OMC-R software release 1.4.0.1 Chapter 5: OMC-R Software Release Features
5-24 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release 1.4.0.6
There were no OMC-R specific features for 1.4.0.6. The OMC-R 1.4.0.6 release supported
the following BSS features:
M-Cell2 GSM900 MHz band
Recovery escalation
68P02901W01-S 5-25
Jul 2008
OMC-R software release 1.4.0.7 Chapter 5: OMC-R Software Release Features
There were no OMC-R specific features for 1.4.0.7. The OMC 1.4.0.7 release supported the
following BSS features:
M-Cellmicro GSM900 MHz band
5-26 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release 1.4.1.0
The OMC-R software release supports both BSS and OMC-R features. Although there is no
OMC-R 1.4.1.1 release, the OMC-R 1.4.1.0 software release supports the following BSS 1.4.1.1
software release features:
M-Cell2/6 MCU redundancy
Phase/frequency lock
Sync boot
Feature Description
BSS device management through OMC-R GUI Enhances the functionality already provided
by the OMC-R GUI for performing network
level Fault Management and Configuration
Management activities from the OMC-R GUIs
Navigation Tree.
Proxy cell Enables cells from external GSM Networks
(managed by another Motorola OMC-R or
that of another vendor) to be modeled at the
OMC-R so that when changed, they can be
updated through neighbor propagation. It is
particularly useful in microcellular networks
employing equipment from more than one
vendor.
Alarm context sensitive help Provides online context sensitive information
on any selected alarm when alarm handling.
Improved PM GUI Provides a new enhanced PM GUI, which can
be selected from the OMC-R GUI front panel.
The graphing capability has been improved to
support multiple traces.
PM activation from MAP Provides the facility to invoke the new PM
GUI with devices already preselected from
other areas of the OMC-R GUI such as the
network maps or the Navigation Tree.
Continued
68P02901W01-S 5-27
Jul 2008
Release 1.4.1.0 features Chapter 5: OMC-R Software Release Features
5-28 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release GSR2
GSR2 features
Table 5-11 summarizes the OMC-R features supported by the GSR2 (1.5.0.0) software release.
Feature Description
Expanded Call Trace With the introduction of the call trace
expansion feature, the BSS will expand the
data collected to be compliant with GSM
standards. This includes the collection of RR
and Abis messages.
MSC Initiated IMSI and IMEI Call Trace Allows the MS to be tracked as it moves across
the network.
Online Transcoder expansion Allows the transcoder capacity, associated with
equipped transcoder cards, to be increased
online while cellular service is maintained to
subscribers within the associated Base Station
System (BSS).
Online Add/Copy/Delete Cell Supports the online modification to the cell
configuration of the SITEs within a BSS while
cellular service is maintained to subscribers.
Microcellular neighbor class 7 Provides additional microcellular functionality
to cater for special handover situations in
contiguous microcells in networks with limited
frequency spectrum, where it is impossible
to avoid deploying adjacent cells on adjacent
BCCH frequencies.
Satellite BSC/XCDR interface (optional) Provides the BSS software support for
transmission of the OML link through satellite.
This gives the facility for the interconnection,
through satellite, of the BSC or RXCDR with
the OMC-R.
Satellite XBL support (optional) Provides the BSS software support
transmission of the XBL link through satellite.
This gives the facility for the interconnection
of RXCDR to BSCs deployed in areas where
land based and microwave links needed
for interconnection are unavailable or cost
prohibitive.
Continued
68P02901W01-S 5-29
Jul 2008
GSR2 features Chapter 5: OMC-R Software Release Features
Continued
5-30 68P02901W01-S
Jul 2008
System Information: GSM Overview GSR2 features
The following list summarizes the hardware features provided in the BSGSM-1.5.0.0 release
with OMC-R/BSS software support:
GPROC2, enhanced processor board
68P02901W01-S 5-31
Jul 2008
OMC-R software release GSR3 Chapter 5: OMC-R Software Release Features
GSR3 features
Table 5-12 summarizes the OMC-R features supported by the GSR3 software release.
Feature Description
Web Access to the OMC-R Provides access to OMC-R Performance Management
(PM) data through a standard web browser (Netscape)
on a client machine connected to the OMC-R LAN. The
browser is supported on both Sun Solaris and Windows
NT (Intel-based) platforms to access OMC-R PM data.
BSS Device Management through Enhances the BSS device and function management
OMC-R GUI capabilities from the OMC-R GUI.
Metrica Statistics Introduces new statistics to support the BSS. Metrica is a
tool that gathers statistics from various types of OMC-Rs
and compares and consolidates those statistics.
5-32 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release GSR4
GSR4 features
Table 5-13 summarizes the OMC-R features supported by software release GSR4.
Feature Description
Network geographical access control N/A
Transfer Motorola text detab format to Converts Motorola text detab format files
PlaNET into a format acceptable to PlaNET, which is
necessary to transfer data to PlaNET.
Task-based Routine Operation and Provides a new OMC-R user interface
Maintenance that integrates the tools necessary for
routine maintenance of the Motorola radio
infrastructure equipment.
Operator-specific regions N/A
Network optimization: cell optimized GUI N/A
Scalable OMC-R The System Processor and the MIB Processor
have been consolidated into a single SunFire
4800/4900 server. This provides further
reductions in cost of ownership and improved
system administration, performance, and
reliability.
Process restartability Allows a subset of system processor
processes (Restartable processes) to restart
automatically, if the processes fail, without
the need for a full OMC-R stop/start. Other
system processes (Non-restartable vital
processes) cause an automatic OMC-R
stop/start on failure.
New Millennium Addresses all aspects of the Motorola system;
OMC-R, BSS, and the BTS and BSC hardware.
It concerns itself with internal clock operation
and the use of the date in various parts of the
product, for example, within the Event and
Alarm reports.
68P02901W01-S 5-33
Jul 2008
OMC-R software release GSR4.1 Chapter 5: OMC-R Software Release Features
GSR4.1 features
Table 5-14 summarizes the OMC-R features supported by software release GSR4.1.
Feature Description
GPRS OMC-R (PCU) Provides a fully integrated solution within the existing
OMC-R architecture. It consists of support for the PCU as
part of the BSS.
OMC-R capacity increased to Increases the OMC-R capacity from the previous rating of
30k TCH and 120 NE 20 kTCH and 64 network elements, to 30k TCH and 120
network elements without requiring hardware upgrades
to the E3500. Also increases the network traffic and
NE count of the OMC-R by extending the object model
and increasing capacity of the OMC-R databases and
data storage areas. This means that the increased size
network can be managed without altering the data storage
arrangements.
5-34 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release GSR5
GSR5 features
Table 5-15 summarizes the OMC-R features supported by software release GSR5.
Description
BTS concentration
Optimized power control
Propagation after audit
EAS relay MMI output control for InCell, M-Cell, and Horizon
Intelligent congestion relief
Adaptive handovers
Support of BCCH and SDCCH for EGSM
Coincident multiband boundaries
Reporting the results of alarms recovery action
Flexible neighbor processing
Dynamic call trace flow control
Proxy cell autocreation
Proxy cell import/export
Completion of OMC-R support for Horizonmacro
Q3 support
DRI and combiner operability improvement
NHA support maximum size GSM OMC-R
Integration of NHA with OMC-R EM
Bay level cal default data
Cell parameter import/export
Applix 4.41 upgrade
System upgrade
Enhanced SDCCH to TCH assignment
Changing NE ID of Assoc_BSSs or Assoc_RXDRs
OMC-R GUI usability
Datagen support
Continued
68P02901W01-S 5-35
Jul 2008
BTS concentration Chapter 5: OMC-R Software Release Features
BTS concentration
The BTS concentration feature provides an alternative mechanism for allocating terrestrial
backhaul for radio resources between the BSC and the BTS. Previous to the introduction of this
feature, these resources were allocated when RTFs were equipped. This feature preserves the
existing mechanism, but allows the operator the choice, on a per BTS site basis, of whether to
use the existing mechanism, or the new dynamic allocation. This feature is optional.
This feature, previously called Dynamic Downlink Power Control Steps, provides optimized
uplink and downlink power control. This is achieved by:
Adding flexibility in defining power steps.
Modifying the range of power steps (by allowing power step sizes to be changed
dynamically).
These power control modifications cause the mobile and BSS to respond more effectively to
changing power level and quality conditions. This minimizes power output both for the MS and
the BSS, as well as reducing interference.
This feature provides data consistency between different BSSs with the main focus is on
synchronizing neighbor information across BSSs.
5-36 68P02901W01-S
Jul 2008
System Information: GSM Overview EAS relay MMI control for InCell, M-Cell, and Horizon
This external alarm system (EAS) relay configuration feature gives the operator the capability to
set a default relay state for the PIX relays at an InCell site, an M-Cell site or a Horizon site and
display the relay states from the OMC-R GUI.
With the implementation of the Intelligent Congestion Relief feature, the existing congestion
relief procedures can benefit from the following advantages:
Faster congestion relief (non-ideal targets will not be tried).
Less congestion and fewer congestion relief triggers (handovers that can lead to congestion
are not accepted).
Adaptive handover
This feature allows support of adaptive handovers and optimizes type 3 and type 5 power
budget handovers from the OMC-R.
This feature allows the configuration of BCCH carriers and the placement of SDCCH in the
EGSM band. This impacts the operation of non-EGSM mobiles in that they may not have service,
since they are not able to access the BCCH frequency and SDCCH channels in the EGSM band.
The support of the BCCH frequency and SDCCH channels in the EGSM band is based on an
operator defined database parameter.
The operator also has the capability to configure a standalone EGSM band cell by selecting
EGSM band frequencies.
With this feature, the operator is allowed to implement a multiband/dualband network with
EGSM as one of the supported frequency bands. It is possible for the operator to select the
EGSM band as the preferred band over the DCS1800 or GSM900 band.
In addition, this feature allows hopping systems to support the EGSM frequency band.
In a dual band system (EGSM and DCS1800), hopping is only supported within the bands
but not between the bands.
68P02901W01-S 5-37
Jul 2008
Coincident multiband boundaries Chapter 5: OMC-R Software Release Features
This feature allows operators to install new radios in a different frequency band and easily
configure multiple frequencies. The installation of new radios allows an operator to have
Multiband capabilities. The major hurdle to this type of upgrade is that the operator has already
spent significant time and money optimizing the existing infrastructure.
With the addition of a second frequency band, with different propagation characteristics, the
operator has to increase efforts to optimize the infrastructure. This is a major stumbling block
to many operators who want the capacity increase but are reluctant to configure and optimize
two frequency bands.
To circumvent this multiple frequency band issue, the new secondary frequency band
compliments the existing infrastructure. To do this, the software allows a cell with a new
frequency band to be configured with the same cell boundaries established by the original
frequency band. Also, it allows the new frequency band cells to use the handover measurement
reports based on the cells in the original frequency band.
This can be done by using mobile reported measurement reports from the primary frequency
band while a call is established on the secondary frequency band. This enables the mobile to be
handled as if it were on the primary frequency band, while not taking any primary frequency
band resources.
This feature is designed to compliment the Multiband Inter-Cell Handover feature and its use is
dependent upon Multiband being enabled.
The Alarms Consolidation feature provides the operator the ability to view all state changes and
secondary alarms associated with a primary alarm in a hands free manner, that is, without the
need to search through alarm and event logs. The Reporting the Results of Alarm Recovery
Action feature, enhances this hands free operation for the end user by including information
describing the result of an alarm recovery action.
This feature modifies the criteria for handover between neighbors. It has four main elements
that can be activated independent of each other.
The Dynamic Call Trace Flow Control feature significantly enhances the existing Call Trace
capabilities available in the BSS and is now supported by the OMC-R. The main uses for Call
Trace in GSM are fault management, optimization, and security.
A network can be optimized by analyzing call trace data that is collected from a call made by a
designated MS as it travels through the network. Call Trace can be used to locate stolen or
defective GSM equipment. Network Operators can also use this feature to determine why calls
are being dropped due to RF Loss.
5-38 68P02901W01-S
Jul 2008
System Information: GSM Overview Proxy cell autocreation
Depending on the amount of traffic between the BSS and OMC-R, the call trace flow control
techniques include:
Modifications of active call trace criteria.
The operator can also choose whether MSC initiated call traces are exempt to the call trace flow
control mechanism.
NOTE
This feature consists of the operator enabled triggering of flow control and the
associated OMC-R GUI configuration support.
The intent of this feature is to address the outstanding issues surrounding the current Call
Trace functionality in the BSS, covering call trace usability.
When the NeighbourGsmCellId is entered and the Neighbor has been initialized, if the
NeighbourGsmCellId does not exist either as a Cell or a Proxy Cell in the OMC-R MIB, the
feature informs the user that the Proxy Cell has been created using the parameters of the
neighbor created.
During a BSS-OMC-R audit, the NeighbourGsmCellIds are checked against the complete list of
Cells and Proxy Cells existing in the MIB. If the NeighbourGsmCellId does not exist a Proxy Cell
is autocreated using the NeighbourGsmCellId.
The Proxy Cell Synchronization feature ensures that Neighbor OMC-Rs are consistent across all
OMC-Rs managing a network by ensuring that the Proxy Cells in an OMC-R are consistent with
the original cell that exists in another OMC.
The OMC-R supplies the user with a program pcellExport that exports Neighbor-related
parameters of all cells within the OMC-R that have Neighbor relationships with cells in other
OMCs, into an ASCII file.
The user then transfers this ASCII file to all other OMCs and the pcellImport run on it.
Create/Update of Proxy Cells, results in all related Neighbors getting updated. Thus
CELL-Neighbor relationships across all OMCs are synchronized through the Proxy Cell
Export/Import mechanism.
68P02901W01-S 5-39
Jul 2008
Completion of OMC-R support for Horizonmacro Chapter 5: OMC-R Software Release Features
The OMC-R also provides a single script pcellSync that synchronizes all OMCs in one shot
without any manual intervention.
This program in turn runs export and import on all OMCs connected in the network.
Detailed feature information was not available at the time of publication. Further information is
included in the next revision of this manual.
This feature provides the completion of OMC-R support for the Horizonmacro.
Q3 support
The purpose of this feature is to port the GSR4 mediation device to GSR5 to enable continued
operation of Q3 in the field.
Motorola's Q3 OMC-R Mediation device support for GSR5 includes the following:
Inter-operability testing of Q3 OMC-R interface functionality with GSR5 and BSS.
This enhancement improves the operability of the Digital Radio Interface (DRI) and Combiner
devices by increasing the flexibility with which these devices can be equipped, and unequipped.
This feature is achieved by specifying the DRIs role in system combining during the equip
of the DRI.
This feature enables Expert Adviser (EA) Network Health Analyst (NHA) to support the
maximum size GSM OMC-R (that is, 45 k TCH).
This feature allows the OMC-R operators to view Network Health Analyst (NHA) problems
through the standard OMC-R alarm windows.
The NHA sends the problems in the correct format to the OMC-R as alarms. The OMC-R Event
Manager (EM) is able to accept the messages and deal with them as standard alarms and passes
them to the GUI for viewing and handling in the standard manner.
5-40 68P02901W01-S
Jul 2008
System Information: GSM Overview Bay level cal default data
There is a new event type on the OMC-R for the NHA to facilitate easy filtering.
Detailed feature information was not available at the time of publication. Further information is
included in the next revision of this manual.
NOTE
A site visit is required for accurate calibration of radios.
NOTE
Current RF Planning data can be exported from the live OMC-R.
The export function generates two ASCII tab delimited files for cell and neighbor parameters
within the network.
User defines the parameters that are exported or imported. The cell file contains a list of cells,
their basics, frequencies and other information. The neighbor file contains a list of neighbors for
each cell. The file format is published and is in ASCII format. RF planning tools, for example,
NetPlan can import these files and use it to carry out a network frequency replan.
The output of the frequency replan can be imported into the OMC-R, and then used to
update the relevant network elements, new base station id codes (bsics) and frequencies are
propagated to neighbor relations.
RF Planning data import and export is carried out from the Navigation form of the OMC-R
or from the command line.
This feature provides an upgrade of Applix from 4.3 to 4.41, so that PRs dependent on this
upgrade can be fixed. Some of these PRs are customer commitments. Applix 4.41 depends
on having an Informix 7.2 engine.
68P02901W01-S 5-41
Jul 2008
System upgrade Chapter 5: OMC-R Software Release Features
System upgrade
NOTE
This feature maintains compatibility with BSS GSR4 and GSR4.1 releases. GSR4.1
was a limited release for GPRS customers only; GSR5 contains all GSR4.1 features. It
is not possible to upgrade the OMC-R directly from GSR3 release to GSR5 release due
to the Y2K compliant release being GSR4.
BSS GSR5 release can be directly upgraded from GSR4 and GSR4.1 release.
OMC GSR5 release is capable of managing a network of BSSs running GSR4, GSR4.1
and GSR5 releases simultaneously.
OMC GSR5 release can be directly downgraded to GSR4 and GSR4.1 for roll-back.
BSS GSR5 release can be directly downgraded to GSR4 and GSR4.1 for roll-back.
An enhancement has been made to increase the success rate of assignment to a preferred
band cell, that is, going from an SDCCH in a non-preferred band cell directly to a TCH in a
preferred band cell.
With the new GSR5 software release, the Enhanced XBL (EXBL) feature introduces the AXCDR
and ABSS devices.
The Dynamic Allocation RXCDR to BSC Circuits (DARBC) feature expands upon these new
devices. During initial configuration of these devices, it is possible that the operator makes a
configuration mistake which, if not caught early, can cause the operator to enter upwards of
a 100 commands to correct it. This feature enables an easy mechanism to correct an early
configuration mistake. Without this feature, the total number of commands could be (21 + 10 +
10) x 2 = 82, to make a simple, device identification number, change.
With this feature, an easy mechanism is provided to correct a mistake. The OMC-R is able to
propagate the BSS or RXCDR identifier (network_entity_id) changes to its associated BSS or
RXCDR devices and its contained devices (XBLs, CICs, and Conn_Links) by initiating a single
operation from the GUI instead of <82> or more BSS MMI commands. The GUI provides a
simple screen to rectify these configuration mistakes.
5-42 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R GUI usability
For example, the operator can select the AXCDR device whose network identifier has to be
changed and initiate the Change Assoc NE ID operation. The operator must note that a
single invocation of the Change Assoc NE ID operation changes the identifier for only one
AXCDR (or ABSS) in a BSS (or RXCDR) database. If the operator changes the identifier of the
NE, the identifier must be changed in the NEs database. The Change Assoc NE ID operation
can be invoked to change the associated device id in each database which includes the NE as
an associated device.
Consider a BSS-1 and BSS-2 which are connected to RXCDR-3. The AXCDR-3 is equipped in the
databases of both BSS-1 and BSS-2. To change the NE id of the RXCDR from 3 to 5, the operator
must change the id of the RXCDR in the RXCDR database and can then invoke the Change Assoc
NE ID operation on the AXCDR-3 at BSS-1 and BSS-2 to set the new AXCDR identifier to 5.
OMC-R GUI usability has been enhanced; the new procedures can be contained within the
following five categories:
Handling Attribute Value Change Notifications from the BSS.
Datagen support
The purpose of this feature is to support all parameter changes introduced in this release.
68P02901W01-S 5-43
Jul 2008
Increased OMC-R neighbor statistics Chapter 5: OMC-R Software Release Features
This feature provides an increase in the volume of neighbor statistics data that can be stored at
the OMC-R, that is, the number of cells with neighbor statistics enabled.
GPRS is a service supported under GSR4.1 and GSR5 which allows for the packet-mode
transmission of data within a GSM network. Using GPRS, an MS can send and receive data in
an end-to-end packet transfer. This enables a more cost-effective and efficient use of network
resources for data transfer.
The purpose of this feature is to support large scale network expansion in an online or offline
environment providing a batch capability to allow for the grouping of multiple expansion
activities.
Delete a BTS with its associated hardware devices and software functions in a single
operation.
Network Expansion can be performed either on the off-line MIB or OMC-R platform.
In the case of online operations, the network expansion application performs mandatory
Fault Management procedures. If deleting or re-parenting a Site, then the Site is gracefully
shutdown, for example, DRIs are shutdown and RSLs are locked.
For both platforms the Network Expansion application maintains Performance Management data
on devices. Specifically during a copy SITE operation, the application copies the Performance
Management configuration (enables statistics and thresholds, and so on), from the original
SITE to the new SITE. Similarly, during a re parent SITE operation the application maintains
the Performance Management configuration.
5-44 68P02901W01-S
Jul 2008
System Information: GSM Overview Increased capacity OMC-R
This feature expands the capacity of the OMC-R to cater for a higher number of receive transmit
functions (RTFs) on a single platform. The capacity is 6000 RTF (45 k TCH).
To cater for the handling of a larger network, a number of usability enhancements are included,
mostly notably the alarm deferral and split-screen alarm window option.
This feature increases the maximum number of trunks (CICs) supported at the BSC from the
previous database limit of 1920 to a new limit of 2400. This is required to support large capacity
BSCs supporting up to 384 carriers using an aggressive Dense Urban call model (as used in
China). It was determined that a minimum of 2300 trunks are required for the Dense Urban call
model to support 384 carriers and the remaining trunks would be used for redundancy.
NOTE
These new CICs must also be known to the MSC.
This feature allows the operator to provision larger capacity BSCs in networks supporting
heavy call traffic, provided that other limitations specified in the Planning Guide have not
already been reached.
The main impacts to the subsystems in the Base Station System (BSS) for increasing the BSC
trunk limitation from 1920 to 2400 trunks are in ensuring data consistency throughout the
system. For example, increasing the number of CICs requires increasing the number of nails, so
connections can be nailed through at the RXCDR.
NOTE
A nailed control link is a fixed 64 kbps link such as an MTL or OML which passes
through the RXCDR without the RXCDR having any impact on that link, it is simply
being used as a medium to get the control link to the destination. This medium is
called a nail.
In order to achieve 384 carriers for the BSC on the Dense Urban Call model (the primary
motivation for this feature), the following assumptions regarding the BSC are made:
Support of two Message Transfer Links (MTLs) per Link Control Function (LCF) at 40%
MTL link utilization.
Support of 25 LCFs.
NOTE
Increasing the number of trunks limit does not provide value for Dense Urban
environments unless these assumptions hold true.
68P02901W01-S 5-45
Jul 2008
Expansion or de-expansion Chapter 5: OMC-R Software Release Features
Expansion or de-expansion
This feature enables the capacity of the OMC-R to cater for a higher number of TCHs.
The lowest level is a 5 k TCH system which can be expanded to a 10 k or 30 k TCH system. The
30 k TCH can be expanded to 45 k TCH system. In ascending order there are four available
TCH sizes:
5 k TCH (low-end)
45 k TCH (high-end)
Motorola's Information Systems Group, Network Systems Division (NSD), in its commitment to
provide the highest value wide area multimedia access solutions, provides upgrade support for
all routers. Software in the field is upgraded to the latest Vanguard router software.
Motorola's Information Systems Group, Network Systems Division (NSD), in its commitment
to provide the highest value wide area multimedia access solutions introduces the Vanguard
6455 router (software and hardware). The Vanguard 6400 Series from Motorola provides
multi service EDGE networking solutions for multimedia, IP, and serial traffic simultaneously
over the WAN.
5-46 68P02901W01-S
Jul 2008
System Information: GSM Overview Removal of the clear stats command
Provides software functionality to enable detection of PSU failures on a PCU cage. When a
failure is detected, an alarm is raised, and the operator notified. The alarm status is also
reflected through the LED indicators (when activated) on the PCU alarm panel board.
68P02901W01-S 5-47
Jul 2008
OMC-R software release GSR5.1 Chapter 5: OMC-R Software Release Features
GSR5.1 features
Table 5-16 summarizes the OMC-R features supported by software release GSR5.1.
Description
Web MMI
CS3, CS4, and 32 kbps TRAU
GPROC fast reset
Unequip TCU/CTU Cabinet
WebMMI
The Web MMI is a new feature which provides a remote service to any user who has access to
the network that a PCU resides on. Through the Intranet, and the availability of the PCU cage
and its Ethernet capability, the BSS can be monitored and maintained.
NOTE
The functionality that is offered consists only of the functionality that the Operation
and Maintenance Man Machine Interface (MMI) and the Executive Monitor (EMON)
provide for a single BSS, as opposed to the functionality that the OMC might provide
as a whole.
The OMC-R to BSS interface is updated to include the new database parameters allow_32k_trau
as well as the new and modified statistics.
The allow_32k_trau parameter is restricted by the GPRS restrictable feature and the 32k
TRAU CS3/CS4 restrictable feature and can only be used if the GPRS and 32k TRAU CS3/CS4
features are unrestricted. Additionally, the dynamic allocation of terrestrial resources feature
must be disabled for any sites using GPRS. This parameter prevents GPRS usage on RTFs that
are sub equipped in the database. This parameter can only be enabled if max_gprs_pdch
is set to a non-zero value. Additionally, if allow_32k_trau parameter is enabled, the value
of max_gprs_pdch cannot be set to zero without first disabling allow_32k_trau. Perform
the verifications to ensure that there are enough terrestrial resources available when
max_gprs_pdch is increased and allow_32k_trau is enabled.
5-48 68P02901W01-S
Jul 2008
System Information: GSM Overview GPROC fast reset
The OMC-R supports fast reset for all types of sites except:
PCU sites from Navig
This feature enables support for the unequipage of extension cabinets of types TCU_2, TCU_6
and Horizonmacro_ext at M-Cell, and Horizonmacro sites without having to unequip the site.
This action can be done provided that the cabinet is locked and there are no DRIs or EASs
equipped to the cabinet. This feature does not support all other cabinet types.
68P02901W01-S 5-49
Jul 2008
OMC-R software release GSR6 Chapter 5: OMC-R Software Release Features
GSR6 features
Table 5-17 summarizes the OMC-R features supported by software release GSR6.
Description
Geographic command partitioning and region support.
Enhanced circuit error rate monitor.
OMC-R GUI usability for large network support.
Enable cyclic neighbor statistics.
Online network expansion - phase 3.
Cell Xchange.
Feature overview
The feature enables operators to set up geographical regions, populate these regions with
network elements (Base Station System (BSS) and Remote Transcoder (RXCDR)) and assign
read and/or write access for these regions to individual users.
Feature description
As the networks grow in size, the amount of information available to the operator is increased.
The feature provides a method of reducing the amount of data visible to the operator by allowing
them to subscribe to a defined set of network elements. This provides each Operation and
Maintenance Center-Radio (OMC-R) operator with a sub network for them to manage.
The feature provides a mechanism for defining geographic regions. Network elements (BSS and
RXCDR) can be added to these regions to represent sub networks. Once the regions are set
up, the system administrator has the ability to create, modify and remove access controls to
particular regions for each operator.
5-50 68P02901W01-S
Jul 2008
System Information: GSM Overview Geographic command partitioning and region support
Benefits
This feature permits network operators to create geographical domains over which specific
operators have control. The restricted user access provides a level of security to ensure that
only authorized users can access certain geographical areas. The ability to manage multiple
networks on one OMC-R reduces the cost of ownership of the networks.
Applications
This feature finds application in those networks where control of the network is exercised in
geographic regions.
The GSR6 version of the OMC-R supports the Geographic command partitioning and region
support. No changes are required to the network elements.
68P02901W01-S 5-51
Jul 2008
Enhanced circuit error rate monitor Chapter 5: OMC-R Software Release Features
Feature overview
The original Circuit Error Rate Monitor (CERM) optional feature provides a means for
identifying when discontinuity is detected on a circuit. The customer can:
Reduce cost of ownership.
A circuit is considered to be the path along which a connection is made, from the entry point in
the BSS (for example, a radio at the BTS) to the exit point in the BSS (for example, the MMS
timeslot that connects to the MSC or PCU).
The CERM is used to monitor the continuity and sanity of hardware processing elements in a
circuit, on a per call basis. Whenever a discontinuity is detected for a circuit during a call, error
counts are updated for the points monitored for the call. When the error count at a particular
monitoring point reaches or exceeds an operator specified threshold, an alarm is generated.
The alarm contains information identifying the monitored path in which the error is detected,
thus allowing the operator to identify potentially faulty devices.
Feature description
The CERM feature is enhanced enabling the monitoring at various points in a GSM network
circuit, thus improving the ability of an operator to narrow down where a faulty device is
located. Although having these monitoring points in the circuit path narrows down the list of
potentially faulty devices, it does not conform that a device is faulty. It is still up to the operator
to determine which device is faulty.
ATER Channel Identifier (ACI) groups on a link between the RXCDR and the BSC.
GPRS Circuit Identifier (GCI) group on a link between the BSC and the PCU.
Path Identity Code (PIC) on a link between the BSC and a BTS.
The PIC is a special case because it is measured on a from-BSC-to-site basis. For example, with
a path leading from a BSC to two daisy chained BTSs, the PIC for the second BTS encompasses
the path through the first BTS to the BSC.
5-52 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R GUI usability for large network support
Feature overview
This feature aims to provide an enhanced Graphical User Interface (GUI) and tools. The GUI
and tools enable the operator to help operate and maintain large networks with relative ease.
The main enhancements are described below:
Neighbor Reciprocity: Previously, a significant number of cells in a network exhibit
neighbor reciprocity. This means that if cell A is a neighbor of cell B, then cell B must be a
neighbor of cell A (two-way relationships).
Enhancements to the OMC-R to view reciprocal relations between cells in the OMC-R, add
or drop reciprocal neighbors enable operators manage large networks with greater ease.
The source neighbor view is also now enhanced to provide the user with information
about neighbor reciprocity.
Auto Reciprocation of Neighbors: Since most cells in a real network exhibit Neighbor
reciprocity, the user now has the option of auto creating the reciprocal Neighbor when a
neighbor is created.
Enhanced Find: The find form option is enhanced to support search for parameters. The
user is able to locate the container of the given parameter name.
Feature description
The OMC-R now supports the following enhancements to the GUI and Configuration
Management Information Base (CM MIB):
The OMC-R GUI is enhanced to provide a menu option on the navigation tree. The menu option
lets the operator view all sources (cells in which mobile phones are located) and neighbors for
cells in the network being managed by the OMC-R.
The new GUI screen is an enhanced version of the source neighbor view. The new view enables
the user to add or remove neighbors and sources and hence manage reciprocal relations.
The OMC-R also enables fully automated creation of reciprocal neighbors with an environment
variable, since most of the neighbors in a practical network are two-way neighbors.
The ProxyCell synchronization processes are extended to synchronize sources along with
neighbors between OMC-Rs so that the correct cross OMC-R reciprocal relations are presented
to the user.
The OMC-R now provides the user the ability to reciprocate neighbors if they wish to during
the equipage of the neighbors. The user is also able to specify, on a per neighbor basis, if it
can be reciprocated or not.
68P02901W01-S 5-53
Jul 2008
Enable cyclic neighbor statistics Chapter 5: OMC-R Software Release Features
Enhanced find
The OMC-R GUI is enhanced to let user find the container of the given parameter. The find form
option also supports the task of find attributes (parameters) in addition to the find devices option.
Feature overview
The BSS and OMC-R were restricted in their ability to provide full neighbor statistic coverage to
the network operators. These limitations were based on hardware and processing limitations.
This feature introduces the ability to traverse the OMC-R network automatically on a per BSS
basis and enable the neighbor statistics in rotation.
The feature also provides the operator with the ability to enable statistics based on analysis
carried out by the Network Health Analyst (NHA) and create a list of their own favorite cells for
enabling.
Feature overview
The network expansion phase 3 feature extends the functional capabilities of the network
expansion phase 2 feature delivered in GSR5.
Feature description
The Online Network Expansion - Phase 3 feature provides the following enhancements:
The Network Expansion Copy-SITE, Delete-SITE and Re-parent-SITE operations are enhanced
to facilitate the insertion or deletion of a Base Transceiver Station (BTS) within a static daisy
chain Base Station System (BSS) configuration.
A stand-alone functionality, referred to as the Path Configure handles the path dependencies.
It is also possible to invoke the Path Configure from the Navigation Tree Configuration
Management menu, for any given site that is not within a DYnamic NETwork (DYNET) device.
The Path Configure enables the operator to un-equip the devices temporarily, to delete paths,
to create new paths and to re-equip the devices with their original settings. Network Expansion
invokes the Path Configure when it determines that the operation selected by the user involves
a site within a daisy chain.
5-54 68P02901W01-S
Jul 2008
System Information: GSM Overview Cell Xchange
Benefits
The main benefit of this phase of network expansion is to improve the feature applicability by
introducing daisy chain support. It also extends the scheduler functionality by adding support
for CellXChange.
Cell Xchange
Feature overview
This feature is an extension of the RF Planning Interface feature (RDB 3416) and of the Cell
Parameter Import Export Feature (RDB 3780). It now allows the user to export and import
SITE/RTF/DRI parameters for direct amendment, as previously for CELL parameters. The
specific parameters to export/import are configurable by the user. The name of the configuration
file is:
/usr/omc/config/global/RF.CNFG
This feature is available both on the Offline Management Information Base (MIB) and on the
Operation and Maintenance Center-Radio (OMC-R) providing a mechanism to make large
scale changes online.
68P02901W01-S 5-55
Jul 2008
OMC-R software release GSR6 (Horizon II) Chapter 5: OMC-R Software Release Features
Table 5-18 summarizes the OMC-R features supported by software release GSR6 (Horizon II).
Description
Support for new UNIX server
Feature overview
From GSR6 (Horizon II) Volume Deployment onwards, a new OMC platform replaces the
existing OMC-R platform.
SunFire 4800
The Netra 20 is intended for smaller configurations of up to 45000 TCH, while the SunFire 4800
platform is for larger configurations of up to 60000 TCH.
5-56 68P02901W01-S
Jul 2008
System Information: GSM Overview Support for new UNIX server
Netra20 is used in configurations of up to 45000 TCH. The platform comprises a Netra 20 server
with two 900 MHz CPUs, 2 Gb memory, two I/O controllers and two HSI/P cards. An external
disk array of twelve 36 Gb disks is attached.
68P02901W01-S 5-57
Jul 2008
Support for new UNIX server Chapter 5: OMC-R Software Release Features
This platform comprises a SunFire 4800 server configured as a single domain. There are four
900 MHz processors on two CPU boards, providing a total memory of 4 Gb. The system also
comprises dual differential SCSI interfaces, dual HSI cards, and quad fast Ethernet cards for
I/O. An external disk array of twelve 36 Gb disks is attached.
The OMC-R GUI platform comprises a Sunblade 150 server with 650 MHz CPU, 1 GB RAM,
and two internal disks.
5-58 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release GSR7
GSR7 features
Table 5-19 summarizes the OMC-R features supported by software release GSR7.
Description
Cell Xchange - BSS Support.
Network Expansion - Phase 4.
Performance Enhancements for GPRS.
Web Access Server.
Feature overview
The Cell Xchange - BSS support feature is an extension of RDB4301 Cell XChange introduced
in GSR6.
This feature enables user-configurable BSS parameters to be imported and exported, and is
available on both the Off-line MIB and the OMC-R.
Feature overview
The Network Expansion - Phase 4 feature extends the functionality of Network Expansion -
Phase 3 introduced in GSR6.
This feature contains the enhancement Support for timeslot switch in PATH configure.
Where a Radio Transceiver Function (RTF) or Radio Signaling Link (RSL) are equipped against
a PATH containing a Timeslot Switch (TS) or adjacent Timeslot Switches, this enhancement
enables the RTFs and RSLs to be equipped on timeslots on Multiple Serial Interface Links
(MMSs) connected directly to the TS.
68P02901W01-S 5-59
Jul 2008
Performance Enhancements for GPRS Chapter 5: OMC-R Software Release Features
Feature overview
The Performance Enhancements for GPRS feature is an extension to the General Packet Radio
Service (GPRS) feature introduced in GSR4.1 and the Coding Scheme 3/Coding Scheme and
Interleaving TBFs features introduced in GSR6.
It also provides support for the GSR7 features GPRS Seamless Cell Reselection, Enhanced
Scheduling and PBCCH/PCCCH. Performance Enhancements for GPRS is a combination of
four sub features:
Cell Partitioning
Feature description
Cell Partitioning
Packet Resource Processor (PRP) capacity and data traffic are increased in the Enhanced
Scheduling feature, and Seamless Cell Reselection between PRP boards introduces new data
through PCI backplane of the PCU.
Cell Partitioning is a software modification that reduces backplane traffic to prevent system
overload. It places the critical data for maintaining the synchronous radio link within a single
slot, and passes the larger more efficient Gb packets over the backplane.
The software processes that work with the TRAU data are repartitioned. The packetization
process is relocated to the PRP and is merged into the scheduling process to facilitate data
transfer with low overhead. The TRAU type GDS is equipped on PRP board, and data path
latency is minimized. Processor overhead of the messages on the bus is reduced, and the
recovered CPU time is used for scheduling or increased capacity.
The feature Interleaving TBFs introduced the parameter delay_dl_rel_dur to set the downlink
Temporary Block Flow (TBF) release duration.
As the number of simultaneous calls in a GPRS cell increases, a large percentage of mobiles
with assigned downlink resources are in delayed downlink TBF release mode with no actual
downlink traffic. The PCU scheduler assigns up to a maximum of four mobiles per PDCH,
and any additional mobiles requesting allocation are blocked until an existing TBF ends. The
longer the delayed downlink TBF release duration, the greater the possibility of new mobiles
requesting access in a cell being blocked. Mobiles in delayed downlink TBF release mode for an
extended period can be terminated, but this takes at least 500 msec (or T3193 period).
To reduce the possibility of mobiles being blocked, the scheduler in the PCU monitors the
availability of timeslot resources in the cell, and terminates downlink TBFs in delayed downlink
release mode before the cell is blocked. The delay_dl_rel_dur parameter determines the
maximum duration and ranges from 300 msecs to 10 seconds, with a typical value of 1 second.
5-60 68P02901W01-S
Jul 2008
System Information: GSM Overview Performance Enhancements for GPRS
Cell availability is calculated and monitored when timeslot resources that take a mobile from
idle to transfer state are assigned, and when release procedures are initiated that return the
mobile to idle state. If the availability is less than the threshold, the scheduler selects one or
more downlink TBFs in delayed release mode to terminate. The criteria for termination of
TBFs comprises no uplink TBF in progress and a duration of at least 300 msecs in delayed
release mode.
The downlink TBF establishment duration is minimized if a Packet Downlink Assignment is sent
on the PACCH while uplink TBF is in progress.
If no downlink TBF exists for a mobile while releasing the uplink TBF, the uplink TBF can be
extended by delaying the final PUAK by a configurable number of block periods.
Before GSR7, all downlink and uplink TBFs used Coding Scheme 2 (CS-2). This feature enables
the initial downlink coding scheme to be set to improve throughput of cells in which all the
mobiles are capable of higher coding schemes.
The initial coding scheme is only set for TBFs with local Temporary Logical Link Identities
(TLLIs). Coding Scheme-2 is used for TBFs with non-local TLLIs, and when the carrier or PDCHs
assigned for the TBFs are not capable of the initial coding scheme CS-3 or CS-4.
The TLLI Block Coding Scheme in one-phase uplink TBFs is always set to CS-1 to ensure the
contention resolved quickly.
This parameter determines the extent of system efficiency against fairness among the users.
Share of throughput for each user is determined by using the current coding scheme (CS)
information to allocate the available bandwidth among the active users with established TBFs.
2 This favors mobiles with higher coding scheme, providing maximum overall throughput.
68P02901W01-S 5-61
Jul 2008
Web Access Server Chapter 5: OMC-R Software Release Features
Feature overview
The Web Access Server feature provides OMC functionality remote from the management
center. It enables consolidation of OMC operation to a single location without the need for a
full Network Management Center (NMC), or alternatively allows OMC operators to manage
multiple OMCs remotely.
Operators are not restricted to dedicated OMC terminals, and can carry out multiple tasks
from a single workstation.
The use of web browser access allows operators to achieve flexibility in their operator terminal
architecture. The web access interface exactly replicates the standard OMC screen, preserving
full OMC functionality.
The Web Access Server platform is a Netra 20 or similar with the following specification:
2 x 900 MHz CPU
8 GB RAM
2 x 73 Gb disk (internal)
The Web Access Server software connects to GUI servers running GSR6 onwards. The
supported browsers are
Netscape Navigator 4.61, 4.7x, and 6.x
5-62 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release GSR7 (GSM Half Rate)
Table 5-20 summarizes the OMC-R features provided at software release GSR7 (GSM Half Rate).
Description
GSM Half Rate
Feature overview
The GSM Half Rate (GSM-HR) feature provides enhanced capacity over the air interface,
corresponding to the proportion of mobiles that supports HR within a coverage area. An air
timeslot is split into two sub channels, each containing an HR channel.
The GSM OMC-R supports GSM-HR as a restricted optional feature on the BSS and RXCDR.
In addition the GSM OMC-R allows the operator to enable or disable GSM-HR on a per BSS
and per CELL basis.
The GSM-HR feature builds on the AMR-HR feature. It introduces new attributes and associated
groups to configure GSM-HR and modifies a number of existing AMR-HR attributes making
them generic. The Detailed Views affected are the BSS, Cell, and RTF. It also introduces and
modifies a number of statistics to enable the Performance Management Reporting of the
GSM-HR. The feature also supports an additional Alarm to inform the Operator of problems
enabling both GSM and AMR Half Rate at the NE.
68P02901W01-S 5-63
Jul 2008
OMC-R software release GSR8 Chapter 5: OMC-R Software Release Features
Description
User Barred Cell
Intelligent Audit
120K TCH OMC - Capacity Expansion
Upgrade OS to Solaris 2.9
Channel and Circuit Status (CACS)
Feature Capacity Licensing and Audit
Feature description
The User Barred Cell feature enables the user to see the list of cells that are currently barred.
The scope can be set to Network/Region/NE/Site. This list is presented to the user in a new
GUI Screen.
The list is dynamically updated. If the barring status is updated while the list is open, the same
changes will be reflected in the list.
Single or multiple cells can be selected from this list and can be unbarred as a single menu
operation. Double clicking on any cell in the list opens the detail view of the User Barred cell.
5-64 68P02901W01-S
Jul 2008
System Information: GSM Overview Intelligent Audit
Intelligent Audit
Feature description
This feature enhances the existing Audit functionality. The major enhancement is to facilitate
the user to intervene on pending and blocked-pending scheduled audits.
This feature also provides information on the time of the last audit gather and audit apply
operations performed on a Network, Region, BSS, SITE, RXCDR, and PCU.
Users can also traverse the Navigation Tree opening Detailed Views for devices in read mode
during the audit/apply phases. The intelligent audit feature has also had some of the menu
options that were only available in the audit inconsistency list brought forward to the audit logs
window. This allows users to apply audit inconsistencies without the need to open the audit
inconsistency window. The options that are now also available on the Audit Log window are
Apply to OMC under the Options menu, and an additional menu named Display has also been
added. Five options are available under it, namely: All, Success, Others, Error, and Failure.
Feature description
The 120K TCH OMC-R feature expands the capacity of the GSM OMC-R to support a maximum
of 120K Traffic Channels and/or a maximum of 254 Network Entities. This feature does not
affect the BSS.
Usability
Resync
MIB Locking
Multi NE Audit
The supported platforms for 120K are a SunFire4800 System Processor, SunFire4900 System
Processor, and a SunBlade150 GUI Server.
68P02901W01-S 5-65
Jul 2008
120K TCH OMC - Capacity Expansion Chapter 5: OMC-R Software Release Features
Characterization
Allows the OMC-R to support up to 120,000 Traffic Channels and 254 NEs. Increases the
limitations on specific system parameters:
Increase in the number of simultaneous downloads to 36 per X25 link.
Increase in the number of alarms stored in the active event table (AET) to 12,000 alarms.
NOTE
Increases in system parameters are only available on 120K platforms.
Alarm and state initialization now occur within the initialization progress dialog.
Usability
Allows enhanced Region and Find support to manage the increase in the TCH and Network
Elements supported. For example:
Audit can be performed on a region.
Resync
Cell Propagation
Cell-X
Events
OOS devices
5-66 68P02901W01-S
Jul 2008
System Information: GSM Overview 120K TCH OMC - Capacity Expansion
Resync
MIB Locking
Two types of locking are now available Intelligent and Global (backward compatible) locking.
Allows operations that affect devices not contained by a Network Element to progress without a
lock. For example, Organize Nodes for the Map will no longer produce a lock.
Two new scripts are added as part of the MIB Locking feature:
LockUtility allows a user to monitor the locks on the system. When executed the script
lists all locks on the system. When executed as omcadmin the LockUtility allows users to
remove locks.
CheckValidLockPID script is set up to run every 15 minutes, it checks to see if there are
any dead locks on the system and removes them.
MIB Locking is available on all supported platforms not just 120K platforms.
NOTE
For more information on the MIB Locking feature refer to the manual Operating
Information: OMC-R System Administration (68P02901W19).
68P02901W01-S 5-67
Jul 2008
Upgrade OS to Solaris 10 Chapter 5: OMC-R Software Release Features
Multi NE Audit
The Multi NE Audit feature allows users to select two or more BSSs/RXCDRs and initiate
an audit on those selected Network Elements, which decreases the time taken for an
Audit Gather to complete.
The Audit Gather phase for each NE of a network audit now runs in parallel.
Users can schedule audits for multiple BSSs/RXCDRs and multiple SITEs.
A new menu item, Audit Progress, is added to the Edit menu of the Audit Log window. This
displays the Element Name, the Status, the Actual Start Time and the Actual End Time.
A new menu item, NE List, is added to the Edit menu of the Audit Scheduler window. This
displays the name of network elements that the scheduled audit is running on.
Multi NE Audit is available on all supported platforms not just 120K platforms.
NOTE
For more information on the Multi NE Audit feature, refer to the manual Operating
Information: OMC-R System Administration (68P02901W19).
Upgrade OS to Solaris 10
Feature description
The OS upgrade applies to the core OMC platform plus ALL related platforms such as NHA,
Datagen, Corba server, Web Server, GUI Servers, and so on.
5-68 68P02901W01-S
Jul 2008
System Information: GSM Overview Channel and Circuit Status (CACS)
Feature description
The new GSR8 CACS feature replaces the Wingz feature familiar to users with previous OMC-R
releases.
The Circuit Status dialog enables users to monitor timeslot usage on an MMS link, and also to
view the status of all eight timeslots on an RTF carrier. These dialogs are refreshed on a periodic
interval which is set by the user. Each refresh operation results in an invocation of a BSS
command to a network element and the parsing of information returned by the network element
via the Remote Login process. OMC-R users can use both dialogs for diagnostic purposes.
The Circuit Status dialog provides a GUI front end to the BSS MMI commands
disp_mms_ts_usage and disp_rft_channel.
The disp_mms_ts_usage command is issued to the BSS when the Circuit dialog is launched
from an MMS or when this dialog is refreshed periodically or on demand.
The disp_rft_channel command is issued to the BSS when the Channel dialog is launched
from an RTF or when this dialog is refreshed periodically or on demand.
The parameters required for these commands are gathered from the selected node. The
corresponding generated MMI commands are sent to the Remote Login process. The Remote
Login process then executes the command at minimum intervals of 15 seconds, this interval is
configurable by the user. The results are sent back to the front-end, parsed, and displayed on
the front-end GUI dialogs.
68P02901W01-S 5-69
Jul 2008
Feature Capacity Licensing and Audit Chapter 5: OMC-R Software Release Features
Feature description
The License Audit tool introduces a mechanism to monitor the usage of the carriers across the
customer network on a per feature basis. Information is gathered by running scheduled audits
against the OMC-R Configuration Management database to produce a report indicating how
many RTF(s) are equipped in the database to support each feature. This feature extends the
License Audit only functionality to provide license file comparison and customer notification
of license overruns.
Each software release has a list of features that are monitored for carrier capacity usage. The
OMC software triggers the License Audit tool at pre-defined intervals, which can be configured
by the customer.
The License Audit tool will be extended on each release to incorporate new features in the audit
functions. For each customer a license file is issued which contains the information on current
licensed capacity for every licensable feature. A single license key is provided to control this
information per network.
The License Audit Tool is distributed with the OMC software and installed and configured by
the user. The audit is triggered by a configurable interval parameter in the OMC software. If
the interval parameter is not set, or set outside the permissible range [2 hours, 48 hours],
the default value of 12 hours is used. The result of the audit (actual usage) is compared with
the license file per feature. An alarm is generated when the carrier usage for one or more
features exceeds the carriers purchased for those features. If the usage is within the limit, the
License Audit Tool generates an event which indicates that the carrier usage is within the
license purchased. The alarms and events are displayed at one or all OMC(s) in the network as
previously configured during installation and configuration.
The License Audit Tool produces a report which is stored in a predefined location containing the
result of the latest audit and license file comparison. Users and Motorola have access to this
report by physically accessing the location where the file is stored.
5-70 68P02901W01-S
Jul 2008
System Information: GSM Overview OMC-R software release GSR9
Table 5-22 summarizes the OMC-R features supported by software release GSR9.
Feature Description
{25663} Implementation of Secure Services on Solaris based O and M
products.
{27508} BSS User Security Management.
{27751} 3GPP Release 6 Performance Management IRP 2G.
{27752} 3GPP Upgrade to Release 6 for 2G element manager FM and
CM functionality.
{25663}
Feature description
This feature replaces the older insecure Solaris services such as rsh with more secure ssh
versions. All UNIX based platforms are updated: OMC-R, GUI server, GUI client, NHA, Corba
server, and Web access server.
OMC-R and NHA sysadmin disable all insecure services such as, telnet, rsh, rlogin, rcp, and ftp
and replace them with more secure services such as ssh, scp, and sftp.
The OMC-R currently has a facility for users to rlogin directly to the BSC. This is not related to
the standard UNIX rlogin., Hence, disabling the UNIX rlogin command does not impact this
facility. Therefore, there is no impact on BSC or BTS.
{27508}
Feature description
The BSS User Security Management feature provides enhanced user security functionality to a
customer network, by providing the operator with the ability to define individual usernames
and passwords for BSS access from the OMC-R, and also locally at the BSS TTY. This provides
information about the users logged into the network through their username and ID. The
usernames and passwords have standard password control features such as complexity
checking, ageing and storage in encrypted format, and are managed from the OMC-R.
68P02901W01-S 5-71
Jul 2008
BSS User Security Management Chapter 5: OMC-R Software Release Features
A user profile is associated with each username, which provides controlled access to a
partitioned command set at the BSS. Both standard BSS commands and EMON commands are
partitioned. The OMC-R administrator can create a username and assign a profile to each user
which defines the BSS and EMON command sets that the user can access at the BSS.
A user is authenticated at the OMC-R whenever logging in using a UNIX account setup by
OMCADMIN. The UNIX login details are compared to an NE user list held at the OMC-R, to
determine which NEs the user has access rights to if it is needed to access the remote network
while logged on to the OMC-R.
There are two types of user accounts maintained as part of the feature implementation:
NE User Account: This is the normal user account which has to be maintained and
managed at the managing OMC-R, and is identified with the OMC-R user having a UNIX
login ID and password ( unixid / unixpasswd ) on the splat server. The OMC-R administrator
is able to create a username and assign a profile to the user which defines the BSS and
EMON command sets that the user can access at the BSS. The omcadmin user can set a
NE access level for a NE user account and when the user login to OMC they will be placed
at that access level. The default NE access level for the omcadmin and non omcadmin
user is 4. The NE user account passwords expire after a certain age set at the UNIX
and can also be blocked.
NE Field Engineer Account : This account is used only when a field engineer physically
visits a Site. The fieldeng2, fieldeng3, fieldeng4 accounts are meant only for qcomm or
local login purposes. The fieldengX accounts are meant only for qcomm purpose. These
account passwords never expire. Also blocking is not supported for these passwords. They
can also be used when the OML is up or down and is configurable from NE.
NOTE
emon_access_level 0 means no access to the EMON commands.
5-72 68P02901W01-S
Jul 2008
System Information: GSM Overview 3GPP Release 6 Performance Management IRP 2G
{27751}{27752}
Feature Description
Fault Management IRP (Integration Reference Point), Bulk Configuration management IRP and
State management IRP features are all upgraded to be Release 6 compliant. In addition, the
Performance Management file is also upgraded to be Release 6 compliant.
GenericNRM (Release 6)
StnNrm (Release 6)
UtranNRM (Release 6)
NOTE
The upgrade to the latest NBI Core partner release of GSR9 requires a clean install.
68P02901W01-S 5-73
Jul 2008
3GPP Release 6 Performance Management IRP 2G Chapter 5: OMC-R Software Release Features
5-74 68P02901W01-S
Jul 2008
Chapter
This chapter provides a glossary of technical terms, standard Motorola acronyms, and
abbreviations used throughout the documentation set.
68P02901W01-S 6-1
Jul 2008
Glossary of technical terms Chapter 6: Glossary of Technical Terms
A Interface - AUTO
Continued
6-2 68P02901W01-S
Jul 2008
System Information: GSM Overview A Interface - AUTO
Continued
68P02901W01-S 6-3
Jul 2008
A Interface - AUTO Chapter 6: Glossary of Technical Terms
Continued
6-4 68P02901W01-S
Jul 2008
System Information: GSM Overview A Interface - AUTO
Continued
68P02901W01-S 6-5
Jul 2008
B Interface - Byte Chapter 6: Glossary of Technical Terms
B Interface - Byte
Continued
6-6 68P02901W01-S
Jul 2008
System Information: GSM Overview B Interface - Byte
Continued
68P02901W01-S 6-7
Jul 2008
B Interface - Byte Chapter 6: Glossary of Technical Terms
Continued
6-8 68P02901W01-S
Jul 2008
System Information: GSM Overview B Interface - Byte
Continued
68P02901W01-S 6-9
Jul 2008
C - CW Chapter 6: Glossary of Technical Terms
BTP Base Transceiver Processor (at BTS). One of the six basic
task groups within the GPROC.
BTS Base Transceiver Station. BSC controls the network
component in the GSM PLMN which serves one cell. The
BTS contains one or more Transceivers (TRXs).
Burst A period of modulated carrier less than one timeslot. The
physical content of a timeslot.
Byte A sequence of adjacent binary digits operated upon as a unit.
Generally consists of eight bits, usually presented in parallel.
A byte is usually the smallest addressable unit of information
in a data store or memory.
C - CW
C Conditional.
C Interface Interface between MSC and HLR/AUC.
C7 See SS7.
CA Cell Allocation. The radio frequency channels allocated to
a particular cell.
CA Central Authority. Software process that controls the BSS.
CAB Cabinet.
CADM Country ADMinistration. The Motorola procedure used
within DataGen to create new country and network files in
the DataGen database.
CAI Charge Advice Information.
CAT Cell Analysis Tool. The CAT is part of the Motorola Cell
optimization product. It is intended for engineering staff
and OMC administrators. CAT provides information about
GSM network cell performance.
CB Cell Balancer. The CB process balances the cells configured
for GPRS across PRPs. If there is a PRP outage, this process
sends message(s). The message indicates that GPRS service
is unavailable to the appropriate CRM(s) for the cells that
could not be moved to an INS (IN Service) PRP.
CB Cell Broadcast. See CBSMS.
CB Circuit Breaker.
CBA Cell Broadcast Agent.
CBC Cell Broadcast Center. The call processing center for CBSMS
messages.
CBCH Cell Broadcast CHannel. The channel which is used to
broadcast messages to all MSs in a specific cell.
CBF Combining Bandpass Filter.
Continued
6-10 68P02901W01-S
Jul 2008
System Information: GSM Overview C - CW
Continued
68P02901W01-S 6-11
Jul 2008
C - CW Chapter 6: Glossary of Technical Terms
6-12 68P02901W01-S
Jul 2008
System Information: GSM Overview C - CW
1 C e ll =
1 S e c to r
O m n i S ite 6 -S e c to r S ite
1 -C e ll S ite or
(1 B T S ) 6 -C e ll S ite
(6 B T S s )
CEND End of charge point. The time at which the calling, or called
party stops charging by the termination of the call or by an
equivalent procedure invoked by the network or by failure
of the radio path.
CEPT Confrence des administrations Europennes des Postes et
Telecommunications.
CERM Circuit Error Rate Monitor. Identifies when discontinuity is
detected in a circuit. An alarm is generated and sent to the
OMC-R when the error count exceeds an operator specified
threshold. The alarm identifies the RCI or CIC and the path
where the error is detected.
CF Conversion Facility.
CF Call Forwarding. A feature whereby, after initiation of
the feature by an authorised subscriber, calls dialled to
the mobile telephone of an authorised subscriber will
automatically be routed to the desired number. See also
CFC and CFU.
CF Control Function. CF performs the SGSN mobility
management functions and OA and M functions for the GSN
module.
CFB Call Forwarding on mobile subscriber Busy supplementary
service. Service automatically redirects incoming calls for
phone busy situations.
CFC Call Forwarding Conditional supplementary service. Service
automatically redirects incoming calls for busy, no reply,
or not reachable situations. See also CFB, CFNRc, and
CFNRy.
CFM Configuration Fault Management RSS process.
CFNRc Call Forwarding on mobile subscriber Not Reachable
supplementary service. Service automatically redirects
incoming calls for not reachable situations.
CFNRy Call Forwarding on No Reply supplementary service. Service
automatically redirects incoming calls for no reply situations.
CFU Call Forwarding Unconditional supplementary service.
Service automatically redirects all incoming calls.
CG Charging Gateway.
Continued
68P02901W01-S 6-13
Jul 2008
C - CW Chapter 6: Glossary of Technical Terms
Continued
6-14 68P02901W01-S
Jul 2008
System Information: GSM Overview C - CW
Continued
68P02901W01-S 6-15
Jul 2008
C - CW Chapter 6: Glossary of Technical Terms
Continued
6-16 68P02901W01-S
Jul 2008
System Information: GSM Overview C - CW
Continued
68P02901W01-S 6-17
Jul 2008
D Interface - DYNET Chapter 6: Glossary of Technical Terms
D Interface - DYNET
Continued
6-18 68P02901W01-S
Jul 2008
System Information: GSM Overview D Interface - DYNET
Continued
68P02901W01-S 6-19
Jul 2008
D Interface - DYNET Chapter 6: Glossary of Technical Terms
Continued
6-20 68P02901W01-S
Jul 2008
System Information: GSM Overview D Interface - DYNET
NOTE
There are several variations of differential
pulse-code modulation.
DPNSS Digital Private Network Signaling System (BT standard for
PABX interface).
DPP Dual Path Preselector. BTS module.
DPR, DPRAM Dual Port Random Access Memory.
DPROC Data PROCessor.
DPSM Digital Power Supply Module.
DRAM Dynamic Random Access Memory. A type of semiconductor
memory in which the information is stored in capacitors on
an integrated circuit.
DRC Data Rate Converter board. Provides data and protocol
conversion between PLMN and destination network for eight
circuits. Part of IWF.
DRCU Diversity Radio Channel Unit. Contains transceiver, digital
control circuits, and power supply. Part of the BSS.
DRI Digital Radio Interface. Provides encoding/decoding and
encryption/decryption for radio channels. Part of BSS.
DRIM Digital Radio Interface extended Memory. A DRI with extra
memory.
DRIX DRI Extender half size board. Fiber optic link from DRI to
BCU. Part of the BSS.
Continued
68P02901W01-S 6-21
Jul 2008
D Interface - DYNET Chapter 6: Glossary of Technical Terms
Continued
6-22 68P02901W01-S
Jul 2008
System Information: GSM Overview E - EXEC
E - EXEC
E See Erlang.
E1 Also known as CEPT1. The 2.048 Mbps rate used by
European CEPT carrier to transmit 30 64 kbps digital
channels for voice or data calls, plus a 64 kbps signaling
channel and a 64 kbps channel for framing and maintenance.
E Interface Interface between MSC and MSC.
EA External Alarm. Refer EAS. Typical external alarms are Door
open, High humidity, Low humidity, Fire, Intruder.
EAS External Alarm System. The EAS is responsible for the
monitoring of all customer-defined environmental alarms at a
site. The customer defines the alarm string and the severity
of the alarms based on the individual requirements of the site.
Indications are provided when the alarms are set or cleared.
Eb/No Energy per Bit/Noise floor, where Eb is the signal energy per
bit and No is the noise energy per hertz of noise bandwidth.
EBCG Elementary Basic Service Group.
EC Echo Canceler. Performs echo suppression for all voice
circuits. If cancelation does not take place, the PLMN
subscriber hears the voice signal as an echo, due to the total
round-trip delay introduced by the GSM system (typically
180 ms).
ECB Provides echo canceling for telephone trunks for 30 channels
(EC).
ECID The Motorola European Cellular Infrastructure Division.
ECM Error Correction Mode. A facsimile mode, in which the
sending machine attempts to send a partial page up to four
times.
Ec/No Ratio of energy per modulating bit to the noise spectral
density.
Continued
68P02901W01-S 6-23
Jul 2008
E - EXEC Chapter 6: Glossary of Technical Terms
ECT Event Counting Tool. The ECT provides information about the
number and type of events and alarms generated throughout
the network. It extracts data from the event log files for
specified dates, allowing the user to generate reports on
individual network elements, groups of elements, or the
whole network.
ECT Explicit Call Transfer supplementary service. ECT enables
a user to connect two other parties with which the user is
engaged in a telephone call and leave the connection himself.
EDGE Enhanced Data-rates for Global Evolution.
EEL Electric Echo Loss.
EEPROM Electrically Erasable Programmable Read Only Memory.
An EEPROM is a special type of PROM that can be erased
by exposing it to an electrical charge. Like other types of
PROM, EEPROM retains its contents even when the power
is turned off.
EGPRS Enhanced GPRS.
EGSM900 Extended GSM900. EGSM900 provides the BSS with a
further range of frequencies for MS and BSS transmit. EGSM
MSs can use the extended frequency band as well as the
primary band, while non-EGSM MSs cannot use the extended
frequency band. A GSM900 cell can contain both GSM900
and EGSM900 carrier hardware. EGSM operates on the
frequency range, 880 MHz to 915 MHz (receive) and 925
MHz to 960 MHz (transmit).
EI Events Interface. Part of the OMC-R GUI.
EIA Electronic Industries Alliance.
EIR Equipment Identity Register. The EIR contains a centralized
database for validating the IMEI. The register consists of
lists of IMEIs organized as follows: White List - IMEIs which
are known to have been assigned to valid MS equipment.
Black List - IMEIs which have been reported stolen or which
are to be denied service for some other reason. Grey List -
IMEIs which have problems (for example, faulty software).
These are not, however, sufficiently significant to warrant a
black listing.
EIRP Effective Isotropically Radiated Power. The arithmetic
product of the power supplied to an antenna and its gain.
EIRP Equipment Identity Register Procedure.
EL Echo Loss.
EM Event Management. An OMC-R application. It provides a
centralized facility for reporting network-wide generated
events and alarms, and for monitoring the status of the
Network.
Continued
6-24 68P02901W01-S
Jul 2008
System Information: GSM Overview E - EXEC
Continued
68P02901W01-S 6-25
Jul 2008
F Interface - Full Rate Chapter 6: Glossary of Technical Terms
Continued
6-26 68P02901W01-S
Jul 2008
System Information: GSM Overview F Interface - Full Rate
Continued
68P02901W01-S 6-27
Jul 2008
F Interface - Full Rate Chapter 6: Glossary of Technical Terms
Continued
6-28 68P02901W01-S
Jul 2008
System Information: GSM Overview F Interface - Full Rate
68P02901W01-S 6-29
Jul 2008
G Interface - GWY Chapter 6: Glossary of Technical Terms
G Interface - GWY
Continued
6-30 68P02901W01-S
Jul 2008
System Information: GSM Overview G Interface - GWY
Continued
68P02901W01-S 6-31
Jul 2008
H Interface - Hyperframe Chapter 6: Glossary of Technical Terms
H Interface - Hyperframe
Continued
6-32 68P02901W01-S
Jul 2008
System Information: GSM Overview H Interface - Hyperframe
68P02901W01-S 6-33
Jul 2008
I - IWU Chapter 6: Glossary of Technical Terms
I - IWU
ID, Id IDentification/IDentity/IDentifier.
IDN Integrated Digital Network. A network that uses both
digital transmission and digital switching.
IDS Interface Design Specification.
IDS Informix Dynamic Server. The OMC-R relational database
management system.
Continued
6-34 68P02901W01-S
Jul 2008
System Information: GSM Overview I - IWU
Continued
68P02901W01-S 6-35
Jul 2008
I - IWU Chapter 6: Glossary of Technical Terms
INS IN Service.
INS Intelligent Network Service. A service provided using the
capabilities of an intelligent network. See also IN.
InterAlg Interference Algorithm.
Intermittent Intermittent alarms are transient and not usually
associated with a serious fault condition. After the
intermittent alarms are displayed in the Alarm window,
the operator must handle and clear the alarm. The system
reports every occurrence of an intermittent alarm unless it
is throttled. See also FMIC and OIC.
inter working The general term used to describe the inter-operation of
networks, services, supplementary services, and so on.
See also IWF.
Interval A recording period of time in which a statistic is pegged.
Interval expiry The end of an interval.
I/O Input/Output.
IOS Intelligent Optimization Service. Tool for improving the
network quality. The IOS generates reports based on
performance data from the BTS and OMC-R.
IP Initialization Process. The IP is primarily responsible for
bringing up the site from a reset, including code loading
the site from a suitable code source. IP also provides the
CSFP functionality, allowing two BSS code load version to
be swapped quickly, allowing the site to return to service
as soon as possible.
IP Internet Protocol. A standard protocol designed for
use in interconnected systems of packet-switched
computer communication networks. IP provides for
transmitting blocks of data called datagrams from sources
to destinations, where sources and destinations are
hosts identified by fixed-length addresses. The internet
protocol also provides for fragmentation and reassembly
of long datagrams, if necessary, for transmission through
small-packet networks. See also TCP and TCP/IP.
IPC Inter-Process Communication. Exchange of data between
one process and another, either within the same computer
or over a network.
IP, INP INtermodulation Products. Distortion. A type of spurious
emission.
IPR Intellectual PRoperty.
IPSM Integrated Power Supply Module (-48 V).
IPX Internet work Packet EXchange A networking protocol
used by the Novell NetWare operating systems. Like
UDP/IP, IPX is a datagram protocol used for connectionless
communications. Higher-level protocols are used for
additional error recovery services.
IR Incremental Redundancy (Hybrid Type II ARQ).
Continued
6-36 68P02901W01-S
Jul 2008
System Information: GSM Overview I - IWU
Continued
68P02901W01-S 6-37
Jul 2008
k - KW Chapter 6: Glossary of Technical Terms
k - KW
k kilo (103).
k Windows size.
K Constraint length of the convolutional code.
KAIO Kernel Asynchronous Input/Output. Part of the OMC-R
relational database management system.
kb, kbit kilo-bit.
L1 - LV
Continued
6-38 68P02901W01-S
Jul 2008
System Information: GSM Overview L1 - LV
Continued
68P02901W01-S 6-39
Jul 2008
L1 - LV Chapter 6: Glossary of Technical Terms
Continued
6-40 68P02901W01-S
Jul 2008
System Information: GSM Overview M - MUX
M - MUX
M Mandatory.
M Mega (106).
M-Cell Motorola Cell.
Continued
68P02901W01-S 6-41
Jul 2008
M - MUX Chapter 6: Glossary of Technical Terms
Continued
6-42 68P02901W01-S
Jul 2008
System Information: GSM Overview M - MUX
Continued
68P02901W01-S 6-43
Jul 2008
M - MUX Chapter 6: Glossary of Technical Terms
min minute(s).
s micro second (10-6).
BCU Micro Base Control Unit. The BCU is the Macro or
Microcell implementation of a BTS site controller.
MIT Management Information Tree. A file on the Motorola
OMC-R. The MIT file effectively monitors data on every
device and every parameter of each device that is in
the current versions of software on the OMC-R. The
data is stored as a text file on the OMC-R. The MIT file
also contains the hierarchical relationships between the
network devices.
MM Man Machine. Refer MMI.
MM Mobility Management. MM functions include
authorization, location updating, IMSI attach or detach,
periodic registration, ID confidentiality, paging, handover,
and so on.
MME Mobile Management Entity.
MMF Middle Man Funnel process.
MMI Man Machine Interface. The method by which the user
interfaces with the software to request a function or
change parameters. The MMI can run on a terminal at
the OMC, or the LMT. The MMI is used to display alarm
reports, retrieve device status, take modules out of service
and put modules into service.
MMI client A machine configured to use the OMC-R software from
the MMI server.
MMI processor MMI client or MMI server.
MMI server A computer which has its own local copy of the OMC-R
software. It can run the OMC-R software for MMI clients
to mount.
MML Man Machine Language. The tool of MMI.
MMS Multiple Serial Interface Link. (Refer also 2 Mbps link).
MNC Mobile Network Code. The fourth, fifth and optionally
sixth digits of the IMSI, used to identify the network.
MNT MaiNTenance.
Mobis Motorola Signaling Link between the BSC and BTS.
MO Mobile Originated.
MO/PP Mobile Originated Point-to-Point messages. Transmission
of a SMS from a mobile to a message handling system.
The maximum length of the message is 160 characters.
The message can be sent whether the MS is engaged in
a call or not.
MOMAP Motorola OMAP.
Continued
6-44 68P02901W01-S
Jul 2008
System Information: GSM Overview M - MUX
Continued
68P02901W01-S 6-45
Jul 2008
M - MUX Chapter 6: Glossary of Technical Terms
6-46 68P02901W01-S
Jul 2008
System Information: GSM Overview NACK - nW
NACK - nW
Continued
68P02901W01-S 6-47
Jul 2008
NACK - nW Chapter 6: Glossary of Technical Terms
NF Network Function.
NFS Network File System. A file system that is distributed
over a computer network. Also, a file system, on a single
computer, that contains the low-level networking files for
an entire network.
NHA Network Health Analyst. The NHA is an optional feature.
It detects problems by monitoring network statistics and
events through the OMC-R. The NHA analyses the event
history, statistics, and network configuration data to try to
determine the cause of the detected problems.
NIB Network Interface Board.
NIC Network Interface Card. A network interface device in the
form of a circuit card that provides network access.
NIC Network Independent Clocking.
NIS Network Information Service. It allows centralized control
of network information for example, hostnames, IP
addresses, and passwords.
N-ISDN Narrowband Integrated Services Digital Network: Services
include basic rate interface (2B + D or BRI) and primary
rate interface (30B + D - Europe and 23B + D - North
America or PRI). Supports narrowband speeds at/or below
1.5 Mbps.
NIU Network Interface Unit. A device that performs interface
functions, such as code conversion, protocol conversion,
and buffering, required for communications to and from a
network.
NIU-m Network Interface Unit, micro. M-Cellmicro MSI.
NL See Network Layer.
NLK Network LinK processor(s).
Nm Newton metres.
NM Network Management (manager). NM is all activities
which control, monitor, and record the use and the
performance of resources of a telecommunications
network in order to provide telecommunication services to
customers or users at a certain level of quality.
NMASE Network Management Application Service Element.
NMC Network Management Center. The NMC node of the
GSM TMN provides global and centralized GSM PLMN
monitoring and control, by being at the top of the TMN
hierarchy and linked to subordinate OMC nodes.
NMSI National Mobile Station Identification number, or, National
Mobile Subscriber Identity. The NMSI consists of the MNC
and the MSIN.
NMT Nordic Mobile Telephone system. NMT produced the
world's first automatic international mobile telephone
system.
Continued
6-48 68P02901W01-S
Jul 2008
System Information: GSM Overview NACK - nW
Continued
68P02901W01-S 6-49
Jul 2008
O - Overlap Chapter 6: Glossary of Technical Terms
NV Non-Volatile.
NVRAM Non-Volatile Random Access Memory. Static random
access memory which is made into non-volatile storage
either by having a battery permanently connected, or, by
saving its contents to EEPROM before turning the power
off and reloading it when power is restored.
nW Nano-Watt (10-9).
O - Overlap
O Optional.
OA Outgoing Access supplementary service. An arrangement
which allows a member of a CUG to place calls outside
the CUG.
OA and M Operation, Administration, and Management.
OAMP Operation, Administration, Maintenance, and Provisioning.
O and M Operation and Maintenance.
OASCU Off-Air-Call-SetUp. The procedure in which a
telecommunication connection is being established while
the RF link between the MS and the BTS is not occupied.
OCB Outgoing Calls Barred within the CUG supplementary
service. An access restriction that prevents a CUG member
from placing calls to other members of that group.
OCXO Oven Controlled Crystal Oscillator. High stability clock
source used for frequency synchronization.
OD Optional for operators to implement for their aim.
OFL % OverFlow.
Offline IDS shutdown state.
Online IDS normal operating state.
OIC Operator Initiated Clear. An alarm type. The OMC-R
operator must clear the OIC alarms after the fault
condition that caused the alarm is resolved. See also FMIC
and Intermittent.
OLM Off_Line MIB. A Motorola DataGen database, used to
modify and carry out radio frequency planning on multiple
BSS binary files.
OLR Overall Loudness Rating.
OMAP Operation and Maintenance Application Part (part of SS7
standard) (was OAMP).
OMC Operation and Maintenance Center. The OMC node of the
GSM TMN provides dynamic Operation and Maintenance
monitoring and control of the PLMN nodes operating in
the geographical area controlled by the specific OMC.
Continued
6-50 68P02901W01-S
Jul 2008
System Information: GSM Overview O - Overlap
Continued
68P02901W01-S 6-51
Jul 2008
PA - PXPDN Chapter 6: Glossary of Technical Terms
Overlap Overlap sending means that digits are sent from one
system to another as soon as they are received by the
sending system. A system using ~ will not wait until it
has received all digits of a call before it starts to send the
digits to the next system. This is the opposite of en bloc
sending where all digits for a given call are sent at one
time. Refer en bloc.
PA - PXPDN
Continued
6-52 68P02901W01-S
Jul 2008
System Information: GSM Overview PA - PXPDN
Continued
68P02901W01-S 6-53
Jul 2008
PA - PXPDN Chapter 6: Glossary of Technical Terms
NOTE
As used here, facilities includes hardware,
software, and network components such as
transmission facilities, switching facilities,
signaling facilities, and databases.
PCS1900 A cellular phone network using the higher frequency
range allocated in countries such as the USA. It operates
on the frequency range, 1850 - 1910 MHz (receive) and
1930 - 1990 MHz (transmit).
PCU Packet Control Unit. A BSS component that provides GPRS
with packet scheduling over the air interface with the MS,
and packet segmentization and packetization across the
Frame Relay link with the SGSN.
PCU Picocell Control unit. Part of M-Cellaccess.
pd Potential difference. Voltage.
PD Protocol Discriminator field. The first octet of the packet
header that identifies the protocol used to transport the
frame.
PD Public Data. Refer PDN.
PDB Power Distribution Board.
PDCH Packet Data Channel. PDCH carries a combination of
PBCCH and PDTCH logical channels.
PDF Power Distribution Frame (MSC/LR).
PDN Public Data Network. A network established and operated
by a telecommunications administration, or a recognized
private operating agency, for the specific purpose of
providing data transmission services for the public.
PDP Packet Data Protocol.
PDTCH Packet Data Traffic Channels.
PDU Power Distribution Unit. The PDU consists consisting of
the Alarm Interface Board (AIB) and the Power Distribution
Board (PDB).
PDU Protected Data Unit.
PDU Protocol Data Unit. A term used in TCP/IP to refer to a unit
of data, headers, and trailers at any layer in a network.
PEDC Pan-European Digital Cellular network. The GSM network
in Europe.
Continued
6-54 68P02901W01-S
Jul 2008
System Information: GSM Overview PA - PXPDN
Continued
68P02901W01-S 6-55
Jul 2008
PA - PXPDN Chapter 6: Glossary of Technical Terms
Continued
6-56 68P02901W01-S
Jul 2008
System Information: GSM Overview PA - PXPDN
Continued
68P02901W01-S 6-57
Jul 2008
QA- Quiesent mode Chapter 6: Glossary of Technical Terms
Continued
6-58 68P02901W01-S
Jul 2008
System Information: GSM Overview R - RXU
R - RXU
Continued
68P02901W01-S 6-59
Jul 2008
R - RXU Chapter 6: Glossary of Technical Terms
Continued
6-60 68P02901W01-S
Jul 2008
System Information: GSM Overview R - RXU
Continued
68P02901W01-S 6-61
Jul 2008
R - RXU Chapter 6: Glossary of Technical Terms
Continued
6-62 68P02901W01-S
Jul 2008
System Information: GSM Overview R - RXU
Continued
68P02901W01-S 6-63
Jul 2008
S7- SYSGEN Chapter 6: Glossary of Technical Terms
S7- SYSGEN
S7 See SS7.
S/W SoftWare.
SABM Set Asynchronous Balanced Mode. A message which
establishes the signaling link over the air interface.
SABME SABM Extended.
SACCH Slow Associated Control CHannel. A GSM control channel
used by the MS for conveying power control and timing
advance information in the downlink direction, and RSSI
and link quality reports in the uplink direction.
Continued
6-64 68P02901W01-S
Jul 2008
System Information: GSM Overview S7- SYSGEN
Continued
68P02901W01-S 6-65
Jul 2008
S7- SYSGEN Chapter 6: Glossary of Technical Terms
Continued
6-66 68P02901W01-S
Jul 2008
System Information: GSM Overview S7- SYSGEN
Continued
68P02901W01-S 6-67
Jul 2008
S7- SYSGEN Chapter 6: Glossary of Technical Terms
Continued
6-68 68P02901W01-S
Jul 2008
System Information: GSM Overview S7- SYSGEN
Continued
68P02901W01-S 6-69
Jul 2008
S7- SYSGEN Chapter 6: Glossary of Technical Terms
Continued
6-70 68P02901W01-S
Jul 2008
System Information: GSM Overview S7- SYSGEN
Continued
68P02901W01-S 6-71
Jul 2008
T -TxBPF Chapter 6: Glossary of Technical Terms
T -TxBPF
T Timer.
T Transparent.
T Type only.
T1 Digital WAN carrier facility that transmits DS-1-formatted
data at 1544 kbps through the telephone-switching
network companies. T1 lines are widely used for
private networks as well as interconnections between an
Organization's PBX or LAN and the telco.
T43 Type 43 Interconnect Board. Provides interface to 12
unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for
2 Mbps circuits (Refer BIB).
TA Terminal Adaptor. A physical entity in the MS providing
terminal adaptation functions (see GSM 04.02).
TA See Timing Advance.
TAC Type Approval Code. Part of the IMEISV.
Continued
6-72 68P02901W01-S
Jul 2008
System Information: GSM Overview T -TxBPF
Continued
68P02901W01-S 6-73
Jul 2008
T -TxBPF Chapter 6: Glossary of Technical Terms
Continued
6-74 68P02901W01-S
Jul 2008
System Information: GSM Overview T -TxBPF
Continued
68P02901W01-S 6-75
Jul 2008
T -TxBPF Chapter 6: Glossary of Technical Terms
Continued
6-76 68P02901W01-S
Jul 2008
System Information: GSM Overview U - UUS
U - UUS
Continued
68P02901W01-S 6-77
Jul 2008
U - UUS Chapter 6: Glossary of Technical Terms
Continued
6-78 68P02901W01-S
Jul 2008
System Information: GSM Overview V - VTX host
Useful part of burst That part of the burst used by the demodulator; differs
from the full burst because of the bit shift of the I and Q
parts of the GMSK signal.
USF Uplink State Flag.
USSD Unstructured Supplementary Service Data. The USSD
mechanism allows the MS user and a PLMN operator
defined application to communicate in a way which is
transparent to the MS and to intermediate network
entities. The mechanism allows development of PLMN
specific supplementary services.
UTRAN UMTS Radio Access Network.
UUS User-to-User Signaling supplementary service. The UUS
supplementary service allows a mobile subscriber to
send/receive a limited amount of information to/from
another PLMN or ISDN subscriber over the signaling
channel in association with a call to the other subscriber.
V - VTX host
V Value only.
VA Viterbi Algorithm (used in channel equalizers). An
algorithm to compute the optimal (most likely) state
sequence in a model given a sequence of observed outputs.
VAD Voice Activity Detection. A process used to identify
presence or absence of speech data bits. VAD is used with
DTX.
VAP Videotext Access Point.
VBS Voice Broadcast Service. VBS allows the distribution of
speech (or other signals which can be transmitted through
the speech codec), generated by a service subscriber, into
a predefined geographical area to all or a group of service
subscribers located in this area.
VC See Virtual Circuit.
VCO Voltage Controlled Oscillator. An oscillator whose clock
frequency is determined by the magnitude of the voltage
presented at its input. The frequency changes when the
voltage changes.
VCXO Voltage Controlled Crystal Oscillator.
VDU Visual Display Unit. A device used for the real time
temporary display of computer output data. Monitor.
VersaTRAU Allows both voice and GPRS/EGPRS frames to be combined
into one large frame to reduces backhaul. See TRAU
(Transcoder Rate Adaption Unit).
Continued
68P02901W01-S 6-79
Jul 2008
V - VTX host Chapter 6: Glossary of Technical Terms
6-80 68P02901W01-S
Jul 2008
System Information: GSM Overview W - WWW
W - WWW
X - X Window
Continued
68P02901W01-S 6-81
Jul 2008
ZC Chapter 6: Glossary of Technical Terms
ZC
6-82 68P02901W01-S
Jul 2008
Index
Index
68P02901W01-S IX-83
Jul 2008
Index
IX-84 68P02901W01-S
Jul 2008
Index
68P02901W01-S IX-85
Jul 2008
Index
IX-86 68P02901W01-S
Jul 2008
Index
68P02901W01-S IX-87
Jul 2008
Index
IX-88 68P02901W01-S
Jul 2008
Index
68P02901W01-S IX-89
Jul 2008
Index
IX-90 68P02901W01-S
Jul 2008
Index
68P02901W01-S IX-91
Jul 2008
Index
IX-92 68P02901W01-S
Jul 2008
Index
68P02901W01-S IX-93
Jul 2008
Index
IX-94 68P02901W01-S
Jul 2008
Index
68P02901W01-S IX-95
Jul 2008
Index
IX-96 68P02901W01-S
Jul 2008