Wireless Priority Access Services Docume

ETEL Systems
Wireless Priority Access Services
m bs
Document Type: Architecture and Survey and study on standards
Document Number
Revision
XXXXX
0.1
r Gu
icto
Revision Date 03/26/01
04/13/01
tV
04/18/01
4/23/01
igh
4/29/01
5/14/01
pyr
5/28/01
Co
This document contains trade secrets and proprietary information of

No use or disclosure of the information contained herein is permitted
without prior written consent.
Victor Gumbs
Technology Development Group
Redmond, WA 98073
© 2001 All rights reserved.
The following are trademarks or registered trademarks for products discussed in this document:
Revision History
Date Revision Description
03/26/01 0.1 Priority Access Service (This document is currently at the Draft stage.)
04/13/01 PAS implemented via e-MLPP (This document is currently at the Draft stage.)
04/20/01 0.3 PAS implemented via e-MLPP (This document is currently at the Draft stage.)
04/23/01 1.0 PAS/e-MLPP SRD Outline (This document is currently at the Draft stage.)
4/25/01 1.0 PAS Implementations GSM 02.11 and eMLPP Further Contrasted
bs
5/15/01 1.0 PAS Imps. 3GPPP 22.11 Supercedes GSM 02.11 Contrasted to eMLPP
m
05/28/01 1.1 PAS Imps. 3GPPP 22.11 Supercedes GSM 02.11 Contrasted to eMLPP
Gu
Final Approval Signatures
r
icto
Prepared By Date Prepared
tV
Sponsor - Date
igh
Steering Committee - Date

pyr
Co
For questions about this document, please contact:

Victor Gumbs
Technology Development Group
Redmond, WA 98073
(425) 315-8903
Contents
1. Executive Summary
1.1. Scope
1.1.1. FCC SRO 7-13-00 Docket 96-86
2. Priority Access Service Standards Compared
2.1.1 Enhanced Priority Access and Channel Assignment (PACA-E)
2.1.1.1.1 Advantages
2.1.1.2 Disadvantages
2.1.2 Enhanced Multi-level Precedence and Pre-emption (eMLPP)
2.1.2.1 Advantages
bs
m
2.1.3 GSM 02.11, Service Accessibility (Access Control)
2.1.3.1 Advantages
Gu
3. Selection: Enhanced Multi-level Precedence and Pre-emption (eMLPP)
r
3.1.1 Introduction … Meeting the FCC R&O
icto
3.1.2 Rough order of magnitude time and cost to implement
tV
3.1.3 Response from Vendors

3.1.3.1 Nokia
igh
3.1.3.2 Lucent
3.2.3.3 Ericsson
pyr
3.2.3.4 Nortel Networks

3.1.3.4 Nortel Networks 4. Overview of the GSM Network Normal vs. Priority Call processing
Co
4.1
5. Multi-vendor PLMN Integration
5.1 Executive Summary
5.1.1 Interoperability Risks
6. PSTN Network Integration and Interfacing Considerations
6.1 Government Emergency Telecommunications Service (GETS)
6.1.1 Introduction
6.2 System Architecture
4.1.0.0Error! Unknown document property name. © 2001 AT&T Wireless Services, Inc. ETEL Systems
1 Executive Summary
Background:
On July 13, 2000, the FCC set out as rules for a Priority Access Services or PAS to all Commercial Mobile Radio
Service (CMRS) carriers for the offering of such services. . The FCC Report and Order, released as FCC Document
"FCC 00-242" to implement FCC Docket No. 96-86, published in the Federal Register on August 8, 2000; Order
effective date, October 10, 2000. The Order places administration of the PAS in the TSP1 Program Office in the
NCC2.
PAS provides the means for NSEP (National Security and Emergency Preparedness) telecommunications users to
obtain priority access to available radio channels when necessary to initiate emergency calls. It does not preempt
calls in progress and is to be used during situations when CMRS network congestion is blocking NSEP call attempts.
PAS is to be available to authorized NSEP users at all times in equipped CMRS markets where the service provider
has decided to provide such service. Authorized users would activate the feature on a per call basis by dialing a
feature code such as *XX. There are multiple priorities, which provide different classes of authorized users with
bs
different access privileges. The Communications Act does not prevent carriers from treating users differently; it bars
only unjust or unreasonable discrimination. A CMRS provider therefore does not violate the Communications Act
m
by offering Federal users the ability to achieve that access; and is provided immunity from all types of liability under
Federal Law as well as most types of liability under State law, especially with regard to emergency calls.
Gu
NCS3 proposes that, in the public interest, the Federal Communications Commission requires CMRS carriers that
voluntarily choose to offer PAS to adhere to uniform operating protocols. NCS is primarily concerned about the
r
compatibility of a peacetime PAS system under the FCC’s Rules with a wartime system that would be adopted by the
icto
Director of OSTP (the Office of Science and Technology Policy). NCS worries that NSEP communications users
would have to change systems under exactly the conditions when compatibility amongst the industry players is most
important.
tV
The Office of Priority Telecommunications (OPT) in the NCC will be on the fast track to develop procedures for the
administration of PAS and the existing Oversight Committee will have oversight responsibility.
igh
Harry W. Underhill, the AT&T Government markets manager4 in the NCC/NSIE5 who is a member of this Oversight
Committee, expects that there will be a strong demand for the feature from state, local, and Federal government
pyr
emergency responders. Some states, such as Oregon and Florida, have been very vocal about their desire for this
service. PAS for wireless has surfaced as an issue in the after action reports following hurricanes and earthquakes as
far back as the Loma Prietta quake and Hurricane Andrew. PAS almost always comes up as an issue during the
Co
Federal Response Plan (FRP) seminars that the NCC/NSIE has been conducting for the past several years. For this
reason, Mr. Underhill expects that PAS will soon begin to show up as a requirement in the Statement of Work for
service procurements by government.
1 Telecommunications Service Priority: A system developed by the Federal Communications Commission (FCC) to ensure priority treatment to
the nation's most important telecommunication services.
2 National Coordinating Center: A confederation of 23 federal government departments and agencies chartered to support the Executive Office
on telecommunications matters relating to national security and emergency preparedness (NSEP). Located in Washington, D.C., the NCC exists
under the management and operation of the Office of the Manager, National Communications System (OMNCS).
3 NCS is an organization created by Executive Order to administer and manage the telecommunications assets of 23 Federal organizations in
serving the NSEP needs of Federal, State and local governments.

4 Harry Underhill is with AT&T's Law and Government Affairs Department, which is the equivalent of our AWS Legal and External Affairs
Department.
5 NSIE = National (Network) Security Information Exchange. Art Maria (our AWS Business Security & Fraud Logical Security Project Manager
who reports directly up to Mary B. Anderson, the Director of the National Business Security Department) represents AWS at this group, and
Harry Underhill represents AT&T Government Markets. This is a meeting hosted/coordinated by the National Communication System (NCS)
and the Defense Information Systems Agency (DISA). NSIE is sponsored by NSTAC, which is the National Security Telecommunications
Advisory Committee which reports to the President of the United States through the National Security Council staff.
4 AT&T — PROPRIETARY Document Type: Architecture and Survey and
study on standards
Use pursuant to Company instructions XXXXX Rev. 1.0 5/28/01
Scope
It is the intent of this document to explore existing standards, contrast and compare them for suitability first to meet
the government recommendation or specification for PAS, as well as point out necessary possible areas of
modification of those standards in order to conform to those requirements, which may be viewed as a subset of those
standards or feature reduction. The reality of which may not be desirable, and further study, analysis and design is
warranted for the verification and validation of said system under high resource contention, within an asynchronous
event driven environment that is required to perform in. It has been an observation that specifications of a system6
should also evolve through the various processes prior to implementation, as more understanding of the problem
domain is gained. Such conclusions should lead to the building of a computer simulation of the system to test the
standard and or it’s subset.
Both the GSM and TDMA platforms have been chosen for this study, in conjunction with three PAS standards
implementations of enhanced Multilevel Priority and Pre-emption (eMLPP), Enhanced Priority Access Channel
Assignment (PACA-E), and GSM 02.11, though primary emphasis and contrast will be focused upon e-MLPP and
PACA-e, on the GSM platform.
Reasoning is because both Ericsson and Lucent both have full implementations of the e-MLPP ETSI standard, within
the GSM framework, and with at least Lucent having an implementation on TDMA of PACA and e-MLPP.
bs
Conclusions to FCC SRO 7-13-00 Docket 96-86
m
Brief Summary and Overview of the Requirements to PAS above demonstrate that there exist significant merit to the
Gu
offering of the service, as several standards are already exist that may be adopted with specific modification.
However, it should be pointed out that both PACA-e and eMLPP both appear to have a relatively high dependencies
upon call preemption, for proper operation, which is specifically disallowed in the FCC R&O.
r
icto
Therefore, there needs to be some early determinations made with the vendors if this feature is a easily configurable
item, what is the statistical probability of the successful call set-up on a precedence priority reservation alone, will its
omission or disabling require any architectural changes, will priority channel reservation be required to augment or
tV
even enable the successful operation this feature?

igh
Additionally, the question needs to be asked, as to what is practical usefulness of a system of Priority Access based
upon a traffic channel priority reservation architecture, during high resource contention, that has a high probability
pyr
even after a call set up for it to dropped during handover, should the subscriber be mobile and roaming, because it
cannot preempt in progress low priority calls, to perform the successful handover.
Co
A channel reservation scheme would further deplete resources during this period of limited resource availability. So
there are several issues here open to discussion.
Finally, to reiterate the point that a simulation model should be built as a preliminary verification and validation, not
only of the R&O specification, but of its practical viability under high resource contention.
Priority Access Service Standards Compared

There are three main recognized industry standards. eMLPP or Enhanced Multi-level Precedence and
Preemption, GSM 02.11, and PACA-e or Enhanced Priority Access Channel Assignment.
6 Grady Booch. Object Oriented Analysis and Design with Applications, 2 nd Ed. [ISBN 0-8053-5340-2] Addison Wesley Longman, Inc. 1994
The following are Excerpts from the T1P1.3/200-165r1 Document of the Ad-Hoc Committee
Some Key Points:
A.) PAS, as defined in the R&O, does not allow for priority calls to preempt calls in progress, nor does it
guarantee the completion of the priority call. The FCC recognized that there may be times during
emergencies when non-NS/EP subscribers are not able to obtain access to their wireless services
because NS/EP personnel are using the radio access channels. The FCC determined that the benefits of
PAS as described in the record, outweigh any inconvenience to non-NS/EP subscribers that result from
such use. However, the FCC also found it in the public interest to permit carriers to limit PAS to a
portion of their spectrum. Lastly, the FCC adopted the NCS’s suggestion to limit priority access to key
personnel and those with leadership responsibilities
B.) The FCC ruled that carriers may voluntarily offer PAS, but if offered, the service must conform to standard
uniform operating protocols. A single nationwide mechanism for accessing this service must be standardized so
bs
that NS/EP responders that subscribe with a PCS-1900 (GSM) service do not have to know multiple access codes
and protocols that differ depending on the local system. In addition, a single access method will facilitate
m
seamless roaming between systems, if/when carriers offer that service.
Gu
The following are Excerpts from the T1P1.3/200-165r1 Document of the Ad-Hoc Committee
r
icto
Brief Summarizations of the PACA-e, e-MLPP, and GSM 02.11 Standards
tV
Enhanced Priority Access and Channel Assignment (PACA-E)

igh
Advantages
pyr
The PACA-E Stage 1 and Stage 2 standards exist and allow feature code access. (See References 4 and 5) PACA-E
also allows egress, which is not initially addressed in the FCC R&O, but is a highly desirable feature. PACA-E
supports up to 15 levels of subscribers and does not require radio resource reservations. PACA-E queued subscribers
Co
get radio access before non PACA-E calls.
Disadvantages
PACA-E is not currently implemented in any PCS-1900 (GSM) network. The standard would need to be modified
for use to implement PAS. Queuing management tasks are resource intensive for the network to support.
Discussion
A significant amount of development work is foreseen to make PACA-E usable to implement PAS. It may be
appropriate for later phases, but it does not appear to be something that could easily be accomplished for a fairly
immediate fielding of the PAS capability.

study on standards
Enhanced Multi-level Precedence and Pre-emption (eMLPP)
Advantages
All three stages of service descriptions for eMLPP exist. (See References 1-3) eMLPP does allow feature code
access. There are seven levels identified in the standard. Like PACA-E, it also supports egress, and even will
support pre-emption, which is specifically disallowed in the R&O. Also, eMLPP can be applied to any domain of a
network (i.e. the entire network or a sub-set of the network).
Disadvantages
As with the case of PACA-E, eMLPP is not implemented in PCS-1900 (GSM) networks and the standard would
need some significant modification for it to support the PAS requirements. The levels would need to be redefined to
match with the R&O.
Discussion
bs
This standard might be more appropriate FFS and implementation in a phase 3 environment. As with PACA-E,
m
significant development may be required.
GSM 02.11, Service Accessibility (Access Control) r Gu

icto
Advantages
tV
There are 15 classes of subscribers that can be defined (number 10 being assigned to emergency “911” callers) and
the network broadcasts which classes of subscribers are barred from network access. The intention of this capability
allows the network operator to prevent overload of the access channel under critical conditions. With some
igh
administrative changes, this capability could be used to decrease the number of subscribers allowed access, thus
providing NS/EP responders with improved access to the network. The specific details that would need to be
developed include how subscribers are assigned to the classes and if/when/how the operator would activate this
pyr
access control on their networks, and the time duration the subscribers would be barred from access.
Co
Disadvantages
There are some unknowns with this approach. First of which, is how PCS-1900 (GSM) operators assign subscribers
to classes. Additional study is needed to determine if the handsets recognize their assigned class and if they receive
and process the broadcast message from the network. This method does not use a feature code, but the SIM card can
be programmed with the NS/EP responder’s access priority. The difficulty in creating new SIM cards would need to
be investigated as well. Since this method temporarily bars some subscribers from the network, PCS-1900 (GSM)
operators might receive a higher amount of customer complaints.
Discussion
GSM 02.11 Service Accessibility is initially thought to have been implemented since Release 96. It is now under
investigation to ensure that the handsets are capable of receiving and processing the broadcast message and that the
networks are capable of implementing access control.
Feature PACA-e GSM 02.11 e-MLPP
Multiple Priority Levels 15 levels with 1 the Supports 15 classes of 7 priority levels, of which
subscribers and has A&B at the highest
highest priority 15 lowest dependencies upon the levels, and operable
5 required in the R&O network operator to within one MSC (Intra-
broadcast the MSC), and subscriber
initialization of service levels 0-4 operable
failing the availability test between MSC’s (Inter-
in the R&O. MSC)
bs
Feature code accessible Yes No Yes
m
Receive/originate Yes No Yes
Gu
prioritization
Roaming Support Yes r Yes Yes
Across MSC No Yes Yes

icto
Priority assignment by Yes Yes Yes
subscriber
tV
Allows for egress (not Yes No Yes

igh
required in R&O, but

desirable)
pyr
Co
Table 1.0 Key Feature Requirements form the R&O Compared

study on standards
3. Selection: Enhanced Multi-level Precedence and Pre-emption (e-MLPP)
3.1.1 Introduction … Meeting the FCC R&O
3.1.2 Rough order of magnitude time and cost to implement
3.1.3 Response from Vendors
3.1.3.1 Nokia
3.1.3.2 Lucent
3.2.3.3 Ericsson
3.1.3.4 Nortel Networks
m bs
r Gu
icto
tV
igh
pyr
Co
m bs
r Gu
icto
tV
igh
pyr
Co

study on standards
4. GSM Architectural Overview
4.1.0.0
A GSM network is composed of several functional entities, whose functions and interfaces are specified. Figure 1
shows the layout of a generic GSM network. The GSM network can be divided into three broad parts. The Mobile
Station is carried by the subscriber, and consists of the terminal or TE and the mobile termination MT. The Base
Station Subsystem controls the radio link with the Mobile Station. The Network Subsystem, the main part of which is
the Mobile services Switching Center (MSC), performs the switching of calls between the mobile users, and between
mobile and fixed network users. The MSC also handles the mobility management operations. Not shown is the
Operations and Maintenance Center, which oversees the proper operation and setup of the network. The Mobile
Station and the Base Station Subsystem communicate across the Um interface, also known as the air interface or
radio link. The Base Station Subsystem communicates with the Mobile services Switching Center across the A
interface.
m bs
r Gu
icto
tV
igh
pyr
Co
Figure 1. General architecture of a GSM network
Mobile Station
The mobile station (MS) consists of the mobile equipment (the terminal) and a smart card called the Subscriber
Identity Module (SIM). The SIM provides personal mobility, so that the user can have access to subscribed services
irrespective of a specific terminal. By inserting the SIM card into another GSM terminal, the user is able to receive
calls at that terminal, make calls from that terminal, and receive other subscribed services.
The International Mobile Equipment Identity (IMEI) uniquely identifies the mobile equipment. The SIM card
contains the International Mobile Subscriber Identity (IMSI) used to identify the subscriber to the system, a secret
key for authentication, and other information. The IMEI and the IMSI are independent, thereby allowing personal
mobility. The SIM card may be protected against unauthorized use by a password or personal identity number (PIN).
Base Station Subsystem

The Base Station Subsystem is composed of two parts, the Base Transceiver Station (BTS) and the Base Station
Controller (BSC). These communicate across the standardized Abis interface, allowing (as in the rest of the system)
operation between components made by different suppliers (Nokia, Lucent, and Ericsson) .
The Base Transceiver Station houses the radio transceivers that define a cell and handles the radio-link protocols
with the Mobile Station.
The Base Station Controller manages the radio resources for one or more BTSs. It handles radio-channel setup,
frequency hopping, and handovers, as described below. The BSC is the connection between the mobile station and
the Mobile service Switching Center (MSC).
bs
Network Subsystem (NSS)
The central component of the Network Subsystem is the Mobile services Switching Center (MSC). It acts like a
m
normal switching node of the PSTN or ISDN, and additionally provides all the functionality needed to handle a
mobile subscriber, such as registration, authentication, location updating, handovers, and call routing to a roaming
Gu
subscriber. These services are provided in conjunction with several functional entities, which together form the
Network Subsystem. The MSC provides the connection to the fixed networks (such as the PSTN or ISDN).
Signalling between functional entities in the Network Subsystem uses Signalling System Number 7 (SS7), used for
r
trunk signalling in ISDN and widely used in current public networks.
icto
The Home Location Register (HLR) and Visitor Location Register (VLR), together with the MSC, provide the call-
routing and roaming capabilities of GSM. The HLR contains all the administrative information of each subscriber
registered in the corresponding GSM network, along with the current location of the mobile. The location of the
tV
mobile is typically in the form of the signalling address of the VLR associated with the mobile station. The actual
routing procedure will be described later. There is logically one HLR per GSM network, although it may be
implemented as a distributed database.
igh
The Visitor Location Register (VLR) contains selected administrative information from the HLR, necessary for call
control and provision of the subscribed services, for each mobile currently located in the geographical area
pyr
controlled by the VLR. Although each functional entity can be implemented as an independent unit, all
manufacturers of switching equipment to date implement the VLR together with the MSC, so that the geographical
area controlled by the MSC corresponds to that controlled by the VLR, thus simplifying the signalling required. Note
Co
that the MSC contains no information about particular mobile stations --- this information is stored in the location
registers.
The other two registers are used for authentication and security purposes. The Equipment Identity Register (EIR) is a
database that contains a list of all valid mobile equipment on the network, where its International Mobile Equipment
Identity (IMEI) identifies each mobile station. An IMEI is marked as invalid if it has been reported stolen or is not
type approved. The Authentication Center (AuC) is a protected database that stores a copy of the secret key stored in
each subscriber's SIM card, which is used for authentication and encryption over the radio channel.
Radio link aspects

Communications over the Um Air Interface is highly complex and requires special attention for the most efficient use
of limited bandwidth of frequency spectrum that is allocated, and that usage plays a crucial role. The efficient use of
the spectrum is best expressed in terms of a quotient of the transmission rate in kilo-bits per second over the
allocated bandwidth.

study on standards
In the GSM standard a combination of FDMA and TDMA are used creating a two dimensional access scheme, which
is described in the following sections, as well as some of the spectral implications that result from the emission of
impulses.
To impress the signal on the medium GSM uses GMSK or Gaussian filtered Median Shift Keying, a modulation
technique the theoretically produces no AM or amplitude modulated part, and belongs to the group of FM or
frequency modulation techniques. The modulate output signal F0 depends upon the input signal E, where F0 is
switched between two frequencies (FT+ft) and (FT-ft). This represents the two binary values 0 and 1, E=0 and E=1.
Further processing beyond the scope of this document are then applied encode the rf signal.
2 Multiple access and channel structure

Since radio spectrum is a limited resource shared by all users, a method must be devised to divide up the bandwidth
among as many users as possible. The method chosen by GSM is a combination of Time- and Frequency-Division
Multiple Access (TDMA/FDMA). The FDMA part involves the division by frequency of the (maximum) 25 MHz
bandwidth into 124 carrier frequencies spaced 200 kHz apart. One or more carrier frequencies are assigned to each
base station. Each of these carrier frequencies is then divided in time, using a TDMA scheme. The fundamental unit
of time in this TDMA scheme is called a burst period and it lasts 15/26 ms (or approx. 0.577 ms). Eight burst
bs
periods are grouped into a TDMA frame (120/26 ms, or approx. 4.615 ms), which forms the basic unit for the
definition of logical channels. One physical channel is one burst period per TDMA frame.
m
The number and position of their corresponding burst periods define channels. All these definitions are cyclic, and
Gu
the entire pattern repeats approximately every 3 hours. Channels can be divided into dedicated channels, which are
allocated to a mobile station, and common channels, which are used by mobile stations in idle mode.
Traffic channels
r
icto
A traffic channel (TCH) is used to carry speech and data traffic. Traffic channels are defined using a 26-frame
multiframe, or group of 26 TDMA frames. The length of a 26-frame multiframe is 120 ms, which is how the length
of a burst period is defined (120 ms divided by 26 frames divided by 8 burst periods per frame). Out of the 26
tV
frames, 24 are used for traffic, 1 is used for the Slow Associated Control Channel (SACCH) and 1 is currently
unused (see Figure 2). TCHs for the uplink and downlink are separated in time by 3 burst periods, so that the mobile
station does not have to transmit and receive simultaneously, thus simplifying the electronics.
igh
In addition to these full-rate TCHs, there are also half-rate TCHs defined, although they are not yet implemented.
Half-rate TCHs will effectively double the capacity of a system once half-rate speech coders are specified (i.e.,
pyr
speech coding at around 7 kbps, instead of 13 kbps). Eighth-rate TCHs are also specified, and are used for
signalling. In the recommendations, they are called Stand-alone Dedicated Control Channels (SDCCH).
Co
Figure 2. Organization of bursts, TDMA frames, and multiframe for speech and data
Control channels
Common channels can be accessed both by idle mode and dedicated mode mobiles. The common channels are used
by idle mode mobiles to exchange the signalling information required to change to dedicated mode. Mobiles already
in dedicated mode monitor the surrounding base stations for handover and other information. The common channels
are defined within a 51-frame multiframe, so that dedicated mobiles using the 26-frame multiframe TCH structure
can still monitor control channels. The common channels include:
Broadcast Control Channel (BCCH)
Continually broadcasts, on the downlink, information including base station identity, frequency allocations,
and frequency-hopping sequences.
Frequency Correction Channel (FCCH) and Synchronization Channel (SCH)
Used to synchronize the mobile to the time slot structure of a cell by defining the boundaries of burst
periods, and the time slot numbering. Every cell in a GSM network broadcasts exactly one FCCH and one
SCH, which are by definition on time slot number 0 (within a TDMA frame).
Random Access Channel (RACH)
Slotted Aloha channel used by the mobile to request access to the network.
bs
Paging Channel (PCH)
Used to alert the mobile station of an incoming call.
m
Access Grant Channel (AGCH)
Used to allocate an SDCCH to a mobile for signalling (in order to obtain a dedicated channel), following a
Gu
request on the RACH.
Burst structure r
There are four different types of bursts used for transmission in GSM. The normal burst is used to carry data and
icto
most signalling. It has a total length of 156.25 bits, made up of two 57 bit information bits, a 26 bit training sequence
used for equalization, 1 stealing bit for each information block (used for FACCH), 3 tail bits at each end, and an 8.25
bit guard sequence, as shown in Figure 2. The 156.25 bits are transmitted in 0.577 ms, giving a gross bit rate of
tV
270.833 kbps.
The F burst, used on the FCCH, and the S burst, used on the SCH, have the same length as a normal burst, but a
different internal structure, which differentiates them from normal bursts (thus allowing synchronization). The access
igh
burst is shorter than the normal burst, and is used only on the RACH.
pyr
3 Speech coding
GSM is a digital system, so speech which is inherently analog, has to be digitized. The method employed by ISDN,
and by current telephone systems for multiplexing voice lines over high speed trunks and optical fiber lines, is Pulse
Co
Coded Modulation (PCM). The output stream from PCM is 64 kbps, too high a rate to be feasible over a radio link.
The 64 kbps signal, although simple to implement, contains much redundancy. The GSM group studied several
speech coding algorithms on the basis of subjective speech quality and complexity (which is related to cost,
processing delay, and power consumption once implemented) before arriving at the choice of a Regular Pulse
Excited -- Linear Predictive Coder (RPE--LPC) with a Long Term Predictor loop. Basically, information from
previous samples, which does not change very quickly, is used to predict the current sample. The coefficients of the
linear combination of the previous samples, plus an encoded form of the residual, the difference between the
predicted and actual sample, represent the signal. Speech is divided into 20 millisecond samples, each of which is
encoded as 260 bits, giving a total bit rate of 13 kbps. This is the so-called Full-Rate speech coding. Recently, an
Enhanced Full-Rate (EFR) speech coding algorithm has been implemented by some North American GSM1900
operators. This is said to provide improved speech quality using the existing 13 kbps bit rate.
4 Channel coding and modulation

Because of natural and man-made electromagnetic interference, the encoded speech or data signal transmitted over
the radio interface must be protected from errors. GSM uses convolutional encoding and block interleaving to
achieve this protection. The exact algorithms used differ for speech and for different data rates. The method used for
speech blocks will be described below.

study on standards
Recall that the speech codec produces a 260-bit block for every 20 ms speech sample. From subjective testing, it was
found that some bits of this block were more important for perceived speech quality than others. The bits are thus
divided into three classes:
 Class Ia 50 bits - most sensitive to bit errors
 Class Ib 132 bits - moderately sensitive to bit errors
 Class II 78 bits - least sensitive to bit errors

Class Ia bits have a 3 bit Cyclic Redundancy Code added for error detection. If an error is detected, the frame is
judged too damaged to be comprehensible and it is discarded. It is replaced by a slightly attenuated version of the
previous correctly received frame. These 53 bits, together with the 132 Class Ib bits and a 4 bit tail sequence (a total
of 189 bits), are input into a 1/2 rate convolution encoder of constraint length 4. Each input bit is encoded as two
output bits, based on a combination of the previous 4 input bits. The convolution encoder thus outputs 378 bits, to
which are added the 78 remaining Class II bits, which are unprotected. Thus every 20 ms speech sample is encoded
as 456 bits, giving a bit rate of 22.8 kbps.
To further protect against the burst errors common to the radio interface, each sample is interleaved. The 456 bits
bs
output by the convolution encoder are divided into 8 blocks of 57 bits, and these blocks are transmitted in eight
consecutive time-slot bursts. Since each time-slot burst can carry two 57 bit blocks, each burst carries traffic from
m
two different speech samples.
Gu
Recall that each time-slot burst is transmitted at a gross bit rate of 270.833 kbps. This digital signal is modulated
onto the analog carrier frequency using Gaussian-filtered Minimum Shift Keying (GMSK). GMSK was selected over
other modulation schemes as a compromise between spectral efficiency, complexity of the transmitter, and limited
r
spurious emissions. The complexity of the transmitter is related to power consumption, which should be minimized
icto
for the mobile station. The spurious radio emissions, outside of the allotted bandwidth, must be strictly controlled so
as to limit adjacent channel interference, and allow for the co-existence of GSM and the older analog systems (at
least for the time being).
tV
5 Multipath equalization
At the 900 MHz range, radio waves bounce off everything - buildings, hills, cars, airplanes, etc. Thus many reflected
igh
signals, each with a different phase, can reach an antenna. Equalization is used to extract the desired signal from the
unwanted reflections. It works by finding out how a known transmitted signal is modified by multipath fading, and
pyr
constructing an inverse filter to extract the rest of the desired signal. This known signal is the 26-bit training
sequence transmitted in the middle of every time-slot burst. The actual implementation of the equalizer is not
specified in the GSM specifications.
Co
6 Frequency hopping
The mobile station already has to be frequency agile, meaning it can move between transmit, receive, and monitor
time slots within one TDMA frame, which normally are on different frequencies. GSM makes use of this inherent
frequency agility to implement slow frequency hopping, where the mobile and BTS transmit each TDMA frame on a
different carrier frequency. The frequency-hopping algorithm is broadcast on the Broadcast Control Channel. Since
multipath fading is dependent on carrier frequency, slow frequency hopping helps alleviate the problem. In addition,
co-channel interference is in effect randomized.
7 Discontinuous transmission
Minimizing co-channel interference is a goal in any cellular system, since it allows better service for a given cell
size, or the use of smaller cells, thus increasing the overall capacity of the system. Discontinuous transmission (DTX)
is a method that takes advantage of the fact that a person speaks less that 40 percent of the time in normal
conversation, by turning the transmitter off during silence periods. An added benefit of DTX is that power is
conserved at the mobile unit.
The most important component of DTX is, of course, Voice Activity Detection. It must distinguish between voice
and noise inputs, a task that is not as trivial as it appears, considering background noise. If a voice signal is
misinterpreted as noise, the transmitter is turned off and a very annoying effect called clipping is heard at the
receiving end. If, on the other hand, noise is misinterpreted as a voice signal too often, the efficiency of DTX is
dramatically decreased. Another factor to consider is that when the transmitter is turned off, there is total silence
heard at the receiving end, due to the digital nature of GSM. To assure the receiver that the connection is not dead,
comfort noise is created at the receiving end by trying to match the characteristics of the transmitting end's
background noise.
8 Discontinuous reception
Another method used to conserve power at the mobile station is discontinuous reception. The paging channel, used
by the base station to signal an incoming call, is structured into sub-channels. Each mobile station needs to listen
only to its own sub-channel. In the time between successive paging sub-channels, the mobile can go into sleep mode,
when almost no power is used.
9 Power control
There are five classes of mobile stations defined, according to their peak transmitter power, rated at 20, 8, 5, 2, and
0.8 watts. To minimize co-channel interference and to conserve power, both the mobiles and the Base Transceiver
Stations operate at the lowest power level that will maintain an acceptable signal quality. Power levels can be
stepped up or down in steps of 2 dB from the peak power for the class down to a minimum of 13 dBm (20
milliwatts).
The mobile station measures the signal strength or signal quality (based on the Bit Error Ratio), and passes the
bs
information to the Base Station Controller, which ultimately decides if and when the power level should be changed.
Power control should be handled carefully, since there is the possibility of instability. This arises from having
m
mobiles in co-channel cells alternately increase their power in response to increased co-channel interference caused
by the other mobile increasing its power. This in unlikely to occur in practice but it is (or was as of 1991) under
Gu
study.
Network aspects
Ensuring the transmission of voice or data of a given quality over the radio link is only part of the function of a
r
icto
cellular mobile network. A GSM mobile can seamlessly roam nationally and internationally, which requires that
registration, authentication, call routing and location updating functions exist and are standardized in GSM networks.
In addition, the fact that the geographical area covered by the network is divided into cells necessitates the
implementation of a handover mechanism. The Network Subsystem, mainly using the Mobile Application Part
tV
(MAP) built on top of the Signalling System No. 7 protocol, performs these functions.
igh
pyr
Co
Figure 3. Signalling protocol structure in GSM
The signalling protocol in GSM is structured into three general layers, depending on the interface, as shown in
Figure 3. Layer 1 is the physical layer, which uses the channel structures discussed above over the air interface.
Layer 2 is the data link layer. Across the Um interface, the data link layer is a modified version of the LAPD
protocol used in ISDN, called LAPDm. Across the A interface, the Message Transfer Part layer 2 of Signaling
System Number 7 is used. Layer 3 of the GSM signaling protocol is itself divided into 3 sublayers.
Radio Resources Management
Controls the setup, maintenance, and termination of radio and fixed channels, including handovers.
Mobility Management
Manages the location updating and registration procedures, as well as security and authentication.

study on standards
Connection Management
Handles general call control, similar to CCITT Recommendation Q.931, and manage Supplementary
Services and the Short Message Service.
Signaling between the different entities in the fixed part of the network, such as between the HLR and VLR, is
accomplished through the Mobile Application Part (MAP). MAP is built on top of the Transaction Capabilities
Application Part (TCAP, the top layer of Signaling System Number 7. The specification of the MAP is quite
complex, and at over 500 pages, it is one of the longest documents in the GSM recommendations.
10 Radio resources management

The radio resources management (RR) layer oversees the establishment of a link, both radio and fixed, between the
mobile station and the MSC. The main functional components involved are the mobile station, and the Base Station
Subsystem, as well as the MSC. The RR layer is concerned with the management of an RR-session, which is the time
that a mobile is in dedicated mode, as well as the configuration of radio channels including the allocation of
dedicated channels.
An RR-session is always initiated by a mobile station through the access procedure, either for an outgoing call, or in
response to a paging message. The details of the access and paging procedures, such as when a dedicated channel is
actually assigned to the mobile, and the paging sub-channel structure, are handled in the RR layer. In addition, it
handles the management of radio features such as power control, discontinuous transmission and reception, and
bs
timing advance.
m
Handover
Gu
In a cellular network, the radio and fixed links required are not permanently allocated for the duration of a call.
Handover, or handoff as it is called in North America, is the switching of an on-going call to a different channel or
cell. The execution and measurements required for handover form one of basic functions of the RR layer.
r
There are four different types of handover in the GSM system, which involve transferring a call between:
icto
 Channels (time slots) in the same cell

tV
Cells (Base Transceiver Stations) under the control of the same Base Station Controller (BSC),
 Cells under the control of different BSCs, but belonging to the same Mobile services Switching Center
igh
(MSC), and
 Cells under the control of different MSCs.

pyr
The first two types of handover, called internal handovers, involve only one Base Station Controller (BSC). To save
signaling bandwidth, they are managed by the BSC without involving the Mobile services Switching Center (MSC),
except to notify it at the completion of the handover. The last two types of handover, called external handovers, are
Co
handled by the MSCs involved. An important aspect of GSM is that the original MSC, the anchor MSC, remains
responsible for most call-related functions, with the exception of subsequent inter-BSC handovers under the control
of the new MSC, called the relay MSC.
Handovers are initiated by either the mobile or the MSC (as a means of traffic load balancing). During its idle time
slots, the mobile scans the Broadcast Control Channel of up to 16 neighboring cells, and forms a list of the six best
candidates for possible handover, based on the received signal strength. This information is passed to the BSC and
MSC, at least once per second, and is used by the handover algorithm.
The algorithm for when a handover decision should be taken is not specified in the GSM recommendations. There
are two basic algorithms used, both closely tied in with power control. This is because the BSC usually does not
know whether the poor signal quality is due to multipath fading or to the mobile having moved to another cell. This
is especially true in small urban cells.
The 'minimum acceptable performance' algorithm gives precedence to power control over handover, so that when the
signal degrades beyond a certain point, the power level of the mobile is increased. If further power increases do not
improve the signal, then a handover is considered. This is the simpler and more common method, but it creates
'smeared' cell boundaries when a mobile transmitting at peak power goes some distance beyond its original cell
boundaries into another cell.
The 'power budget' method uses handover to try to maintain or improve a certain level of signal quality at the same
or lower power level. It thus gives precedence to handover over power control. It avoids the 'smeared' cell boundary
problem and reduces co-channel interference, but it is quite complicated.
11 Mobility management
The Mobility Management layer (MM) is built on top of the RR layer, and handles the functions that arise from the
mobility of the subscriber, as well as the authentication and security aspects. Location management is concerned with
the procedures that enable the system to know the current location of a powered-on mobile station so that incoming
call routing can be completed.
Location updating
A powered-on mobile is informed of an incoming call by a paging message sent over the PAGCH channel of a cell.
One extreme would be to page every cell in the network for each call, which is obviously a waste of radio bandwidth.
The other extreme would be for the mobile to notify the system, via location updating messages, of its current
location at the individual cell level. This would require paging messages to be sent to exactly one cell, but would be
very wasteful due to the large number of location updating messages. A compromise solution used in GSM is to
group cells into location areas. Updating messages are required when moving between location areas, and mobile
stations are paged in the cells of their current location area.
bs
The location updating procedures, and subsequent call routing, use the MSC and two location registers: the Home
Location Register (HLR) and the Visitor Location Register (VLR). When a mobile station is switched on in a new
m
location area, or it moves to a new location area or different operator's PLMN, it must register with the network to
Gu
indicate its current location. In the normal case, a location update message is sent to the new MSC/VLR, which
records the location area information, and then sends the location information to the subscriber's HLR. The
information sent to the HLR is normally the SS7 address of the new VLR, although it may be a routing number. The
reason a routing number is not normally assigned, even though it would reduce signaling, is that there is only a
r
limited number of routing numbers available in the new MSC/VLR and they are allocated on demand for incoming
icto
calls. If the subscriber is entitled to service, the HLR sends a subset of the subscriber information, needed for call
control, to the new MSC/VLR, and sends a message to the old MSC/VLR to cancel the old registration.
tV
For reliability reasons, GSM also has a periodic location updating procedure. If an HLR or MSC/VLR fails, to have
each mobile register simultaneously to bring the database up to date would cause overloading. Therefore, the
database is updated as location updating events occur. The enabling of periodic updating, and the time period
igh
between periodic updates, is controlled by the operator, and is a trade-off between signaling traffic and speed of
recovery. If a mobile does not register after the updating time period, it is deregistered.
pyr
A procedure related to location updating is the IMSI attach and detach. A detach lets the network know that the
mobile station is unreachable, and avoids having to needlessly allocate channels and send paging messages. An
attach is similar to a location update, and informs the system that the mobile is reachable again. The activation of
Co
IMSI attach/detach is up to the operator on an individual cell basis.
Authentication and security

Since the radio medium can be accessed by anyone, authentication of users to prove that they are who they claim to
be, is a very important element of a mobile network. Authentication involves two functional entities, the SIM card in
the mobile, and the Authentication Center (AuC). Each subscriber is given a secret key, one copy of which is stored
in the SIM card and the other in the AuC. During authentication, the AuC generates a random number that it sends to
the mobile. Both the mobile and the AuC then use the random number, in conjunction with the subscriber's secret
key and a ciphering algorithm called A3, to generate a signed response (SRES) that is sent back to the AuC. If the
number sent by the mobile is the same as the one calculated by the AuC, the subscriber is authenticated.
The same initial random number and subscriber key are also used to compute the ciphering key using an algorithm
called A8. This ciphering key, together with the TDMA frame number, uses the A5 algorithm to create a 114-bit
sequence that is XORed (exclusive ORed) with the 114 bits of a burst (the two 57 bit blocks). Enciphering is an
option for the fairly paranoid, since the signal is already coded, interleaved, and transmitted in a TDMA manner,
thus providing protection from all but the most persistent and dedicated eavesdroppers.

study on standards
Another level of security is performed on the mobile equipment itself, as opposed to the mobile subscriber. As
mentioned earlier, a unique International Mobile Equipment Identity (IMEI) number identifies each GSM terminal.
A list of IMEIs in the network is stored in the Equipment Identity Register (EIR). The status returned in response to
an IMEI query to the EIR is one of the following:
White-listed
The terminal is allowed to connect to the network.
Grey-listed
The terminal is under observation from the network for possible problems.
Black-listed
The terminal has either been reported stolen, or is not type approved (the correct type of terminal for a
GSM network). The terminal is not allowed to connect to the network.
12 Communication management
The Communication Management layer (CM) is responsible for Call Control (CC), supplementary service
management, and short message service management. Each of these may be considered as a separate sublayer within
the CM layer. Call control attempts to follow the ISDN procedures specified in Q.931, although routing to a roaming
bs
mobile subscriber is obviously unique to GSM. Other functions of the CC sublayer include call establishment,
selection of the type of service (including alternating between services during a call), and call release.
m
Call routing
Gu
Unlike routing in the fixed network, where a terminal is semi-permanently wired to a central office, a GSM user can
roam nationally and even internationally. The directory number dialed to reach a mobile subscriber is called the
Mobile Subscriber ISDN (MSISDN), which is defined by the E.164 numbering plan. This number includes a country
r
code and a National Destination Code which identifies the subscriber's operator. The first few digits of the remaining
icto
subscriber number may identify the subscriber's HLR within the home PLMN.
An incoming mobile terminating call is directed to the Gateway MSC (GMSC) function. The GMSC is basically a
switch which is able to interrogate the subscriber's HLR to obtain routing information, and thus contains a table
tV
linking MSISDNs to their corresponding HLR. A simplification is to have a GSMC handle one specific PLMN. It
should be noted that the GMSC function is distinct from the MSC function, but is usually implemented in an MSC.
igh
The routing information that is returned to the GMSC is the Mobile Station Roaming Number (MSRN), which is also
defined by the E.164 numbering plan. MSRNs are related to the geographical numbering plan, and not assigned to
subscribers, nor are they visible to subscribers.
pyr
The most general routing procedure begins with the GMSC querying the called subscriber's HLR for an MSRN. The
HLR typically stores only the SS7 address of the subscriber's current VLR, and does not have the MSRN (see the
Co
location updating section). The HLR must therefore query the subscriber's current VLR, which will temporarily
allocate an MSRN from its pool for the call. This MSRN is returned to the HLR and back to the GMSC, which can
then route the call to the new MSC. At the new MSC, the IMSI corresponding to the MSRN is looked up, and the
mobile is paged in its current location area (see Figure 4).
Figure 4. Call routing for a mobile terminating call

Conclusion and comments
In this paper I have tried to give an overview of the GSM system. As with any overview, and especially one covering
a standard 6000 pages long, there are many details missing. I believe, however, that I gave the general flavor of GSM
and the philosophy behind its design. It was a monumental task that the original GSM committee undertook, and one
that has proven a success, showing that international cooperation on such projects between academia, industry, and
government can succeed. It is a standard that ensures interoperability without stifling competition and innovation
among suppliers, to the benefit of the public both in terms of cost and service quality. For example, by using Very
Large Scale Integration (VLSI) microprocessor technology, many functions of the mobile station can be built on one
chipset, resulting in lighter, more compact, and more energy-efficient terminals.
Telecommunications are evolving towards personal communication networks, whose objective can be stated as the
availability of all communication services anytime, anywhere, to anyone, by a single identity number and a
pocketable communication terminal. Having a multitude of incompatible systems throughout the world moves us
farther away from this ideal. The economies of scale created by a unified system are enough to justify its
implementation, not to mention the convenience to people of carrying just one communication terminal anywhere
they go, regardless of national boundaries.
bs
The GSM system, and its sibling systems operating at 1.8 GHz (called DCS1800) and 1.9 GHz (called GSM1900 or
m
PCS1900, and operating in North America), is a first approach at a true personal communication system. The SIM
card is a novel approach that implements personal mobility in addition to terminal mobility. Together with
Gu
international roaming, and support for a variety of services such as telephony, data transfer, fax, Short Message
Service, and supplementary services, GSM comes close to fulfilling the requirements for a personal communication
system: close enough that it is being used as a basis for the next generation of mobile communication technology in
r
Europe, the Universal Mobile Telecommunication System (UMTS).
icto
Another point where GSM has shown its commitment to openness, standards and interoperability is the compatibility
with the Integrated Services Digital Network (ISDN) that is evolving in most industrialized countries, and Europe in
tV
particular (the so-called Euro-ISDN). GSM is also the first system to make extensive use of the Intelligent
Networking concept, in which services like 800 numbers are concentrated and handled from a few centralized
service centers, instead of being distributed over every switch in the country. This is the concept behind the use of
igh
the various registers such as the HLR. In addition, the signaling between these functional entities uses Signaling
System Number 7, an international standard already deployed in many countries and specified as the backbone-
signaling network for ISDN.
pyr
GSM is a very complex standard, but that is probably the price that must be paid to achieve the level of integrated
service and quality offered while subject to the rather severe restrictions imposed by the radio environment.
Co

study on standards
Introduction to e-MLPP and the Contrast between Normal and Priority Calls
The enhanced multilevel precedence and preemption service (e-MLPP) actually consist of two component services:
The precedence service gives the specified called priority, and the preemption service make sure calls of high
priority get the requisite resources. The e-MLPP service belongs to the group of supplementary services to which
the user must have authorized subscription to on an as required basis, for as the name implies consists of multiple
priority levels. The service may be applied to speech and fax teleservices, as well as the bearer services category,
only utilizing the lower layers of the transport media between access points, whereby they support some terminal
equipment.
As will be outlined in later sections, the standard supports 7 priority levels, all of which are fully configurable
according to the standard implementation recommendations. The maximum level of priority of a subscriber is stored
in the SIM or subscriber identity module, described earlier in the prior sections and is just additional information
maintained in its database.
bs
Primary advantage to this user is afforded in that his higher priority provides preferential access to overall system
m
resources when other users congest the system. Sufficient resources may be freed up such that the priority user can
proceed with his call. Callers of lower priority for example may have their access to a TCH removed, and will hear a
Gu
tone or receive a message that access is not available. The logic that negotiates the resources is contained in
primarily the MSC.
Call Set-up Time Improvements

r
icto
On logical area to improve for the priority access cal I is in the call set-up time. Where normal call set-up times
range from a few seconds out to 15 to 30 seconds, which is the instant that the send button is pressed to the time that
actual ringing is heard by the called party (not the ringback acknowledgement ring first heard by the caller). This is
tV
potentially too long a period of time in the instance of an emergency. Therefore, different classes of call set-up time
have been specified in the e-MLPP standard.
To achieve this various time saving measures have been taken between all of the various interfaces in terms of
igh
message level reduction minimization to limit the number of exchanges that must take place over the network
components, as in the authentication and ciphering of the call circuit.
pyr
Class Setup Time Priority Level

1 < 1 second A
Co
2 < 5 seconds B, 0
3 < 10 seconds 1, 2, 3, 4
Table 2. Nominal Call Setup Times
Automatic Answer for priority Calls
Automatic Answer of a mobile station is also provided for in the standard, for incoming calls of specified levels.
The parameter for the level of call to be answered is again stored in the SIM. If the called party is engaged on a call
and the call is of lower priority than the incoming call the, the call is placed on hold and the incoming call is given
precedence. Therefore a subscription to e-MLPP should always be setup with a subscription to call waiting, and call
hold. The only call that does not allow preemption is another emergency call, and that incoming call will be signaled
with call waiting.
Mobil Station MS Network

Channel Request 
 Channel Assignment
Service Request 
 Authentication Request
Authentication Response 
 Ciphering Mode Command
Ciphering Mode Complete 
Set-Up
 Call Proceeding
 TCH Assignment
TCH Assignment Complete
 Alerting
 Connect
Connect Acknowledgement
Communication Connection Completed  Talking
Table 3. Simplification of a Normal Call Setup
m bs
Mobil Station MS Network
Channel Request 

Gu
Channel Assignment
Service Request 
Set-UP 

r
TCH Assignment

icto
TCH Assignment Complete
Communication Connection Completed  Talking
tV
Table 4. Simplification of Fast Call Setup High Priority

Pre-emption is a function
igh
The Pre-emption is a function that allows the allocation of a traffic channel even in the case when all TCHs
of a certain cell are busy. This feature is only applied for allocation of traffic channels per
pyr
ASSIGNMENT_REQUEST. HANDOVER_ REQUESTs including BSC internal handover requests do not

trigger the pre-emption procedure.
The MSC is capable to invoke this feature and the BSC selects a suitable connection allowed to be pre-
Co
empted, and performs a release of this connection and allocates the TCH for the new request.
Pre-emption can be applied to guarantee the successful establishment for high priority calls, e.g.
emergency calls, irrespective of the traffic load of the serving network. This is essential for the efficiency of
specific emergency services.
The MSC instructs on a per call basis the serving BSC within the message ASSIGNMENT_REQUEST, if
pre-emption is allowed or not.
For each incoming ASSIGNMENT_REQUEST the BSC has to investigate if the pre-emption allowance is
set or not. If a call has the pre-emption allowance and the respective serving cell has no radio resources
available the BSC searches an adequate connection that can be pre-empted resp. released. If the BSC
detects such a pre-empted call, this call will be released and the requested channel assignment will be
performed for the new incoming call.
If a call has the pre-emption allowance and the respective serving cell still has radio resources available
the ASSIGNMENT_REQUEST is handled by the BSC according to the normal channel assignment
procedure.
Note, that if a SDCCH is requested pre-emption is not performed.
Note, that a pre-emption call bypasses waiting requests in case of active queuing. If no connection can be found for
pre-emption, the request is queued according to the priority level given in the message ASSIGNMENT_REQUEST.
If a request with pre-emption capability is queued, this request will not be handled as pre-emption candidate any
longer.

study on standards
Network Elements Affected
Network Element OMC BSC BTS MSC STF
Software N Y N Y N
Hardware N N N N N
Interfaces
Interface BSC-OMC BSC-BTS BSC-MSC BSC-STF Um
Software N N Y N N
Hardware N N N N N
m bs
r Gu
icto
tV
igh
pyr
Co
Detailed Priority Access Service with e-MLPP Main concepts

The enhanced Multi-Level Precedence and Pre-emption service (eMLPP) provides different levels of precedence for
call set-up and for call continuity in case of handover.
There are seven priority levels, which are defined in GSM 02.67. The two highest levels are reserved for network
internal use. These two levels can only be used locally, i.e. in the domain of one MSC. The other five priority levels
are offered for subscription and can be applied globally, e.g. on inter switch trunks, if supported by all related
network elements, and also for interworking with ISDN networks providing the MLPP service.
The seven priority levels are defined as follows:
A (highest, for network internal use)
B (for network internal use)
0 (for subscription)
bs
m
4 (lowest, for subscription).
Gu
Levels A and B shall be mapped to level 0 for priority treatment outside of the MSC area in which they are applied.
As a network specific configuration, the ability to pre-empt other calls of lower priority and the application of fast
call set-up procedures can be assigned to each priority level. An example for an eMLPP configuration is given in
r
icto
GSM 02.67.
tV
Considering aspects of priority handling, the following issues can be considered for each call:
a) Contention during the initial random access (no specific definitions apply for eMLPP. Delays due to access
igh
collision have to be managed by a corresponding planning of the network resources);
b) Contention in gaining radio resources during the call set-up phase and during handover (this item relates to
the assignment of SDCCH (Stand alone Dedicated Control Channels) and TCH (Traffic Channels) for which
pyr
queuing and pre-emption mechanisms are applied for eMLPP);
A pre-emption might already be performed as a network option on the basis of the establishment case if a
Co
network specific eMLPP configuration assigns a certain priority level to a particular establishment case.
c) Contention in gaining terrestrial resources inside the GSM network (this item relates to the assignment of
terrestrial channels between the GSM network nodes. Priority actions shall be performed on basis of the
MLPP (on the SS #7 subnet of the ISDN circuit) service implementations. The eMLPP priority levels A and
B shall be mapped to the MLPP priority level 0. No further specific definitions apply for eMLPP);
d) Contention in gaining terrestrial resources in external networks (this item relates to interworking with external
networks which shall be performed on basis of the MLPP service if provided in the related external
networks.);
e) Application of different call set-up procedures in relation to the priority levels and the network specific
configuration (three classes of set-up performance are defined in GSM 02.67, one very fast class for VBS or
VGCS emergency call services, one class for fast but normal set-up times and one class allowing some delay
in the set-up. The network on the basis of the requested priority level shall decide the application of the
corresponding procedures);
f) Automatic answering of calls if the incoming call is of or exceeds a defined priority level, respectively, or
called party pre-emption (if the called GSM subscriber is engaged in communication of a lower priority);
study on standards
g) The means by which the called user is informed of priority issues and is able to make appropriate decisions if
no called party pre-emption applies;
h) The accommodation of non-compatible Mobile Stations.
The definitions in the present specification focus on the issues under item b), e), f), g) and h). Items c) and d) are
related to the MLPP service implementation for the signalling system No. 7 according to ITU-T Recommendations
Q.85 and Q.735.
For a call establishment, a subscriber shall be able to select any one of the priority levels he has subscribed to.
Priorities shall be treated in the network as defined in GSM 02.67. Priority treatment is different for point-to-point
calls and voice broadcast calls or voice group calls, respectively:
- mobile originated point-to-point call:
The priority level depends on the calling subscriber. If the user has no eMLPP subscription, the call shall
have a default priority level defined in the network. If the user has an eMLPP subscription, the call shall have
the priority level selected by the user at set-up or the priority level predefined by the subscriber as default
priority level by registration.
- mobile terminated point-to-point calls:
bs
The priority level depends on the calling party. For this, interworking with the ISDN MLPP service is
m
required. If the call is not an MLPP call, i.e. no priority level is defined; the call shall be treated in the mobile
network with a default priority level. If the call is an MLPP call, the call shall be treated with the priority level
Gu
provided by the interfacing network.
- mobile to mobile point-to-point calls: r

icto
The priority shall be treated for the calling subscriber as for mobile originated calls and for the called
subscriber as for mobile terminated calls. However, an interworking with MLPP is not required if both the
calling subscriber and the called subscriber are located in the same MSC area.
tV
- Voice Broadcast Calls (VBS) and Voice Group Calls (VGCS):
The link on the voice broadcast call channel or voice group call channel shall have the priority level as
igh
defined in the corresponding registration for the related voice broadcast call or voice group call in the GCR.
At the early stage of a voice broadcast call or voice group call establishment, before the GCR request is made
and the voice broadcast call channel or voice group call channels are assigned, the procedure shall be the
pyr
same as for point-to-point calls.
Queuing and resource pre-emption shall then be applied as appropriate according to the network service
Co
configuration. In addition, automatic answering or called party pre-emption shall be applied as appropriated
according to the Mobile Station's internal service configuration.
The MSC shall maintain a record of the priority level of each call in progress in its area such that it can arbitrate over
resources in a defined manner.
The priority level can be included in the CM_SERVICE_REQUEST message in the case that a user establishing a
point-to-point call is using a compatible Mobile Station (see clause 6).
If the subscriber has not selected a priority level for that call or uses a non compatible Mobile Station (see clause 6),
the priority level shall be assigned according to the respective VLR data.
The priority level of a call shall be determined by the MSC. Accordingly, the MSC shall request channel assignment
with an indication of the priority level and the pre-emption capability of that call. For this the MSC shall use the
priority message element as defined in GSM 08.08. Mapping of the priority information in this message element on
the network specific eMLPP configuration shall be performed in the MSC. Queuing and resource pre-emption shall
be performed accordingly if necessary.
In addition to the priority signalling, the requirement for a direct assignment of a TCH shall be included in the
establishment cause of the CHAN_REQ message in order to support a fast call set-up procedure in the BSC at the
earliest possible stage of the call establishment for high priority calls if applicable.
Automatic answering or, if necessary, called-party pre-emption has to be performed by the Mobile Station as defined
in the following:
- point-to-point calls:
If the user is in idle mode, the Mobile Station shall automatically connect to an incoming call of a sufficient
priority level. The priority level shall be included in the paging message and in the set-up message. If the user
is in dedicated mode and has a subscription to Call Waiting, a Call Waiting indication including the priority
level of the call shall be given to the Mobile Station which automatically accepts the waiting call.
There is no called party pre-emption for point-to-point calls without Call Waiting.
- voice group calls and voice broadcast calls:
Notifications for other voice group calls, voice broadcast calls or information on paging for point-to-point
calls shall be given to the Mobile Stations involved in on-going voice group calls or voice broadcast calls as
defined in GSM 03.68 and GSM 03.69, respectively. The notifications include the related priority level of the
call. In case of a notified call with higher priority where called-party pre-emption applies, the Mobile Station
shall automatically leave the on-going voice group call or voice broadcast call and react according to the type
of the notified call type.
For both cases, the priority level applied shall be included, either in the paging message or Call Waiting indication,
or in the notification message, in order to enable the Mobile Station to decide on an automatic reaction (automatic
answering or called-party pre-emption) or to indicate the incoming, non pre-empting call to the user.
bs
The priority information of the assignment request shall also be applied for BSS internal handover. For external
handover, the MSC shall include the priority information in the handover request according to the definition in GSM
m
08.08 in the same way as for the assignment request.
Gu
Compatibility issues
eMLPP cannot be applied with standard Phase 1 or Phase 2 Mobile Stations (non compatible Mobile Stations) with
r
all service aspects. A dedicated Mobile Station (compatible Mobile Station) with eMLPP capability is required.
icto
Specific functions a compatible Mobile Station shall provide are:
- priority selection via MMI for call establishment in case of an eMLPP subscription including priority levels
above level 4;
tV
- analysis of the priority level included in a paging message, Call Waiting indication or notification into a voice
group call or voice broadcast call, respectively;
igh
- automatic reaction on basis of the analysed priority level in case of an incoming call while in dedicated mode,
group transmit mode or group receive mode, respectively, according to the user defined Mobile Station
configuration (for each subscribed priority level the user shall be able to configure the Mobile Station for
pyr
automatic acceptation or indication or rejection of an incoming call);
NOTE: Functions related to notifications are only required for Mobile Stations providing VBS or VGCS
Co
functions as defined in GSM 03.69 and GSM 03.68, respectively.
However, if eMLPP is provided in a network, it can be applied to non compatible Mobile Stations in the following
way:
- calls of subscribers which have no specific eMLPP subscription shall be treated for resource pre-emption with
a default priority level.
This shall also apply independent of the use of compatible or non compatible Mobile Stations;
- calls of eMLPP subscribers which use a non compatible Mobile Station shall be treated for resource pre-
emption with the subscriber's default priority level;
- calls to eMLPP subscribers which use a non compatible Mobile Station shall be indicated to the user by Call
Waiting as normal.

study on standards
Information storage
Stored in the HLR

Information concerning the maximum priority level which a subscriber is entitled to use at call establishment shall be
stored in the HLR.
If the maximum priority level is above level 4, one level shall be indicated as default level. This default level shall be
used for mobile originated calls if no priority selection is performed by the user at call establishment.
The default selection can be performed by the subscriber by means of a registration procedure.
NOTE The priority levels in the subscription are related to point-to-point calls. VBS and VGCS calls are
treated with the priority level defined in the GCR for a certain group ID in a certain group call area
which can be different to the priority levels explicitly defined in the eMLPP subscription. However,
these levels are then implicitly defined with the subscribed group IDs.
eMLPP may have the following logical states (refer to GSM 03.11 for an explanation of the notation):
Provisioning State Registration State Activation State HLR Induction State
(Not Provisioned, Not Registered, Not Active Not Induced)
(Provisioned, Registered, Active and Operative Not Induced)
bs
The HLR shall store the logical state of eMLPP (which shall be one of the valid states listed above) on a per
subscriber basis.
m
Gu
State transition model
The following figure shows the successful cases of transition between the applicable logical states of eMLPP. The
state changes are caused by actions of the service provider.
r
Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some
icto
successful requests may not cause a state change. Hence they are not shown in the diagram.
Provision
tV
(Not Provisioned, (Provisioned,

igh
Not Registered, Registered,

Not Active, Active and Operative,
pyr
Not Induced) Not Induced)

Co
Withdrawal
Figure 5: State transition model for eMLPP
Transfer of information from HLR to VLR

If the provisioning state for eMLPP is “Provisioned” then, when the subscriber registers on a VLR, the HLR shall
send that VLR information about the logical state of eMLPP, the maximum priority level and the default priority
level.
If any of the eMLPP subscriber data is changed, the HLR shall send to the VLR the complete eMLPP subscriber
data.
Stored in the VLR

For eMLPP, the VLR shall store the service state information, the maximum priority level a subscriber is entitled to
use and the default priority level received from the HLR.
Stored in the MSC

The network specific service configuration of eMLPP defined by the network operator as specified in
GSM 02.67 shall be stored within each MSC. This includes information on resource pre-emption actions for any
given levels of incoming and on-going call priority. An example for a network specific service configuration is given
in GSM 02.67.
Stored in the SIM

Each compatible Mobile Station shall be aware of the automatic answering actions for any given levels of priority so
that when in idle mode or dedicated mode or group receive mode or group transmit mode, it can decide on the
necessary reactions to be taken according to the priority information of the incoming call.
For this, the SIM shall store the following data:
Priority level Subscription available Automatic answering applies Fast set-up actions (note)
A yes/no yes/no yes/no
B yes/no yes/no yes/no
0 yes/no yes/no yes/no
bs
4 yes/no -- yes/no
m
NOTE: Fast set-up actions, which shall be performed by the Mobile Stations if indicated in the SIM data, are
Gu
the use of the appropriate establishment cause and the reaction on accelerated establishment
procedures allowed by the network.
r
The user via MMI shall predefine the automatic reaction of the Mobile Station for automatic answering or called
icto
party pre-emption. For each subscribed priority level the user shall be able to configure the Mobile Station for
automatic acceptation or indication or rejection of an incoming call.
In addition, the Mobile Station shall verify a priority level selected by the user at call establishment against the
tV
priority levels stored on the SIM and act accordingly as defined in subclause.
The Mobile Station shall perform automatically the related functions for a fast call set-up if related with a selected
priority.
igh
pyr
Stored in the GCR

In the network, specific service configurations for VBS and VGCS calls which are registered in the GCR, a priority
Co
level shall be assigned to each voice broadcast call or voice group call configuration, according to GSM 03.69 and
GSM 03.68, respectively.
Identities
No specific requirements are identified.
Operation and maintenance aspects

NOTE: A list and short description of the operation and maintenance aspects will be given. This includes the
options and parameters which can be set by the operator.
- handling of timers;
- registration aspects etc.

study on standards
Functions and information flow
Subscription
When the subscriber record is created in the HLR, the maximum priority level a subscriber is entitled to use shall be
included.
Change of subscription
The network operator can change the maximum priority level of any eMLPP subscriber at any time. A change of
subscription shall not affect any on-going calls at the moment of change. The subscriber cannot change the maximum
priority level via the MMI.
Call set-up
bs
Mobile originated calls (MOC)
m
Indication of priority
Gu
The Mobile Station may indicate the priority of each call initiated. If no priority is indicated by the user or a non-
compatible Mobile Station is used then the default priority level shall be applied which is stored in the VLR. The
selection of priority shall be an MMI function. r
Mobile stations indicate the priority of their call in the signalling that takes place during the call establishment
icto
process.
No preferential treatment will be possible during this initial random access until the point at which the priority
information is received by the network (CM_SERV_REQ message). Alternatively, a resource pre-emption might
already take place on basis of an establishment cause.
tV
Prior to the indication of the selected priority level in the CM_SERV_REQ message, the BSC may decide on the
assignment of an SDCCH or direct assignment of a TCH on the basis of the establishment cause in the CHAN_REQ
igh
message. This allows the BSC to support a fast call set-up at the earliest stage of the call establishment. The
establishment cause for emergency calls or an establishment cause indicating the request for fast call set-up shall be
able to trigger this function.
pyr
Subscription checking
The Mobile Station shall verify the selected priority level against the priority levels stored in the SIM. If the selected
Co
priority is not allowed, then the priority of the call shall be modified to that of the nearest allowed priority level
below the requested level.
The MSC shall request the VLR to verify if the subscriber is allowed to use the selected priority level.
Authentication and ciphering

The user or the network may wish to omit or postpone authentication and ciphering in order to provide for a faster
call set-up.
If the network decides to omit or postpone authentication and ciphering for a call it can send a CM_SERV_ACC
message in reply to the CM_SERV_REQ message.
For further study:
The network, however, may allow the Mobile Station to send the SETUP message immediately or to wait for
the AUTH_REQ message by an indication in the system information broadcasted on the BCCH. The Mobile
Station shall be able to decide on the immediate sending of a SETUP message on the basis of the information
received on the BCCH and the data stored in the SIM as defined in subclause 8.4.
NOTE: The postponed authentication by sending a CM_SERV_ACC message is an application of an
available function. The provisional grant of the MM connection is a new function which is to be
specified.
Indication of priority to the BSC

The channel assignment request to the BSC shall also include the priority level and pre-emption capability of the
connection as defined in GSM 08.08. The MSC maps the eMLPP priority on these priority levels. In addition, the
eMLPP priority shall be explicitly indicated to the BSC in the assignment request. The BSC shall store the priority
level in order to decide on later actions, e.g. to arrange notifications to the Mobile Station according to priorities.
Choice of radio channel

If an appropriate radio channel is available the BSC shall assign it as normal. If no channels are available then the
BSC shall perform queuing according to the priority levels. If the assignment request has a pre-emption capability
indicator, pre-emption shall be performed.
In addition, the network related service configuration defines the set-up class in relation to a priority level and
therefore the allowable delay of the call establishment (see GSM 02.67). By using this information, the MSC shall
decide whether OACSU may be applied for a call or not.
Indication of priority to the Mobile Station

If the network assigns a priority level to the call different to the one requested by the user for any reasons or if the
Mobile Station does not know what priority level will be applied since no priority was included in the service
bs
request, the network can inform the Mobile Station on the assigned priority level by sending a
CALL_PROCEEDING message including a priority information element.
m
The Mobile Station shall store the priority level requested by the user, possibly overridden by the level received by
the network, to perform automatic answering of calls or pre-emption of on-going calls.
Mobile terminated calls (MTC) r Gu

icto
Indication of priority
For a mobile terminated call, the priority level is defined in the ISUP set-up message to the VMSC. The priority and
pre-emption indications used in the ISUP shall follow the definitions of the MLPP service as defined in the ITU-T
tV
recommendations Q.85 and Q.735, respectively.
Indication of priority to the BSC

igh
The paging command message includes the requested priority.

The channel assignment request to the BSC shall include the priority level and pre-emption capability of the
connection as defined in GSM 08.08. The MSC maps the eMLPP priority on these priority levels. In addition, the
pyr
eMLPP priority shall be explicitly indicated to the BSC in the assignment request. The BSC shall store the priority
level in order to decide on later actions, e.g. to arrange notifications to the Mobile Station according to priorities.
Co

The network may wish to omit or postpone authentication and ciphering in order to provide for a faster call set-up
according to the priority level to be applied for the call and the network specific service configuration stored in the
MSC.
If the network decides to omit or postpone authentication and ciphering for a call it, can send the SETUP message
immediately after reception of the initial layer 3 message.
Termination with called subscriber in idle mode or group receive mode

In this case the Mobile Station shall be paged in the normal manner, but with the paging messages also containing
the priority level of the call. In addition, the priority level will be provided with the SETUP message.
The Mobile Station in group receive mode shall consult the internal service configuration list stored on the SIM to
establish whether it should automatically respond to the paging request.
The Mobile Station in idle mode does not need to analyze the priority level from the paging request message but can
derive it from the SETUP message and then decide on automatic acceptance of the call.
In the case where the called subscriber is using a non compatible Mobile Station, automatic answering is not
possible.

study on standards
Termination with called subscriber in dedicated mode
In the case where the called subscriber has a subscription for eMLPP and for Call Waiting and is using a compatible
Mobile Station, the Mobile Station shall be informed of the priority of the new call together with the call waiting
indication. The Mobile Station will then consult the internal service configuration list stored on the SIM to establish
whether it should automatically accept the waiting call without consulting the user, or whether the call waiting
facility will be used as normal.
In the case where the called subscriber has no subscription for Call Waiting, called party pre-emption is not possible.
In the case where the called subscriber is using a non-compatible Mobile Station and has a subscription for Call
Waiting, Call Waiting shall be performed as normal.
Voice group call or voice broadcast call
Indication of priority to the related MSC

For each voice group call or voice broadcast call service configuration registered in the GCR as defined in GSM
03.68 and GSM 03.69, respectively, a priority level is assigned at registration of the GCR data by the service
provider. The priority level will be provided by the GCR together with the call attributes.
bs
m
Authentication of the calling service subscriber shall be performed equivalent to the standard mobile originated call
case as defined in subclause 11.5.1.3. The calling service subscriber shall be treated with his selected priority or with
Gu
his default priority as known in the VLR as long as he has an own link with the network (see GSM 03.68 and GSM
03.69). The priority, which applies to the voice group call channel or voice broadcast call channel, is defined in the
GCR. r
Authentication and ciphering of the calling service subscriber might therefore be performed, omitted or postponed
icto
(see subclause 11.3.1.3).
Indication of priority to the called Mobile Stations

tV
The priority level shall be indicated together with the related paging messages or notification messages and treated in
the Mobile Station as defined in GSM 03.68 and GSM 03.69, respectively.
igh
Pre-emption
pyr
Choice of communication to pre-empt

For all resources where pre-emption may be required, namely radio channels, A-interface channels and inter switch
trunks, the network specific service configuration stored within the MSC shall be used to determine whether pre-
Co
emption should occur, and if so, which communication to pre-empt. The MSC shall inform the BSS about priority
and pre-emption by using the priority message element in the assignment request as defined in GSM 08.08. Mapping
of the priority information in this message element on the network specific eMLPP configuration shall be performed
in the MSC.
Release procedures
Suitable messages shall be passed from the point at which the pre-emption is to occur, to other affected entities. In
the case of fast call set-up, such pre-indication may need to be foregone to meet the required set-up time.
The indication to the pre-empted user shall be performed by an indication for congestion as defined in GSM 02.40.
Pre-emption at handover
When an on-going call is handed over into a fully used cell, the BSC shall perform queuing and pre-emption if
necessary according to the priority and pre-emption capability information received with the assignment request.
In case of BSS external handover, the priority and pre-emption capability information shall be included in the
handover request as defined in GSM 08.08.
Overview of call related signalling

In this overview, the message structures to implement the specified concept are identified, and brief details are given
of each message.
A diagrammatic representation of the transport procedures to be used to carry the priority information in case of
standard point-to-point calls are given in figures 1 to 6. The message flow is not represented completely.
The corresponding message flows in case of voice group calls or voice broadcast calls are given in GSM 03.68 and
GSM 03.69, respectively.
Initial RACH
CHAN_REQ: Standard
message.
IMM_ASS: Standard
message.
bs
SABM (SERV_REQ):
m
Modified form of the current
L3-MM CM SERVICE
Gu
REQUEST where the
priority level is provided in
addition if the user performs
a priority selection. In case
r of no priority selection or
icto
use of a non-compatible
Mobile Station the Mobile
Station shall send a standard
tV
service request message and

the network shall apply a
default priority to their
igh
request.
pyr
Co
Figure 1: Signalling for the

prioritization at mobile
originating call establishment
without fast call set-up
UA (SERV_REQ): Standard message.

COM_L3_INFO: The MSC is provided with initial information about the requested service together with the
selected priority level if applicable.
AUTH_REQ: Standard message.
AUTH_RES: Standard message.
CIPH_MOD_CMD: Standard message.
CIPH_MOD_COM: Standard message.
SETUP: Standard message.
CALL_PROCEEDING: The network may include the assigned priority level in a CALL_PROCEEDING message
if no priority level was indicated in the CM_SERVICE_REQUEST message or the assigned priority level is different
to the one requested.

study on standards
ASS_REQ: This message is sent from the MSC to the BSC including the call priority and pre-emption capability to
be applied as defined in GSM 08.08, according to the priority information the MSC has obtained from the service
request or from the VLR data. In addition, the eMLPP level is included as explicit information.
ASS_CMD: Standard message.
SABM: Standard message.
UA: Standard message.
ASS_COM: Standard message.
For further study:

SYSTEM INFO: The network may
provide information on the BCCH system
information, that a MM connection is
provisional granted after establishment of the
main signalling link.
If such information is provided on the

BCCH and the user has selected a fast call set-
bs
up, the Mobile Station shall immediately send
a SETUP message to the network after the
m
main signalling link is established.
Gu
Initial RACH CHAN_REQ: Standard
message.
r For further study:
A new establishment cause shall be
icto
provided to indicate the requirement for the
direct assignment of a TCH (very early
assignment) for the support of fast call set-up
tV
procedure.
igh
pyr
Figure 6: Signalling for the prioritization of

mobile originating call with fast call set-up
Co
IMM_ASS: Standard message.

SABM (SERV_REQ): Modified form of the current L3-MM CM SERVICE REQUEST where the priority level is
provided in addition if a priority selection is performed by the user.
UA (SERV_REQ): Standard message.
COM_L3_INFO: The MSC is provided with initial information about the requested service together with the
selected priority level if applicable.
If the network itself decides not to perform ciphering, it shall send an CM_SERV_ACC message.
CALL_PROCEEDING: The network may include the assigned priority level in a CALL_PROCEEDING message
if no priority level was indicated in the CM_SERVICE_REQUEST message or the assigned priority level is different
to the one requested.
ASS_REQ: This standard message is sent from the MSC to the BSC including the call priority and pre-emption
capability to be applied as defined in GSM 08.08, according to the priority information the MSC has obtained from
the service request or from the VLR data.
In addition, the eMLPP level is included
as explicit information.
CHAN_MOD_MODIFY: Standard
message.
CHAN_MOD_MODIFY_ACK:
Standard message.
SETUP (prec.) req. ind.: In addition to
the basic call requirements, the contents
of the set-up information flow shall
contain the information on the requested
MLPP priority level.
PAGING: Modified paging command
including the priority level to be applied.
PAG_REQ: Modified paging message
bs
including the related priority level.
Initial RACH CHAN_REQ: Standard
m
message.
Gu
SABM (PAG_RSP): Standard message.
UA (PAG_RSP): Standard message.
r PAG_RSP: Standard message.
AUTH_REQ: Standard message.
icto
AUTH_RES: Standard message.
CIPH_MOD_CMD: Standard message.
Figure 7: Signalling for
prioritization at mobile
tV
terminating call
without fast call set-up and
igh
without called-party pre-

emption
pyr
CIPH_MOD_COM: Standard message.

CALL_CONF: Standard message.
Co
ASS_REQ: This standard message is sent from

the MSC to the BSC including the call priority
and pre-emption capability to be applied as
defined in GSM 08.08, according to the
priority information the MSC has obtained
from the incoming set-up message. In addition,
the eMLPP level is included as explicit
information.
ASS_CMD: Standard message.
SABM: Standard message.
UA: Standard message.
ASS_COM: Standard message.
SETUP (prec.) req. ind.: In addition to the
basic call requirements, the contents of the set-
up information flow shall contain the
information on the requested MLPP priority
level.

study on standards
PAGING: Modified paging command including the priority level to be applied.
PAG_REQ: Modified paging message including the related priority level.
Initial RACH CHAN_REQ: Standard message. A new establishment cause shall be provided to indicate the
requirement for the direct assignment of a TCH (very early assignment) for the support of fast call set-up procedure.
SABM (PAG_RSP): Standard message.
Figure 8: Signalling for the prioritization at mobile terminating call

establishment with fast call set-up and without called-party pre-emption
UA (PAG_RSP): Standard message.

PAG_RSP: Standard message.
For fast call set-up the network shall immediately send a SETUP message to the Mobile Station. Authentication and
ciphering may not be performed or delayed by the network.]
SETUP: Modified message with an indication of the priority level.
CALL_CONF: Standard message.
bs
ASS_REQ: This standard message is sent from the MSC to the BSC including the call priority and pre-emption
capability to be applied as defined in GSM 08.08, according to the priority information the MSC has obtained from
m
incoming set-up message. In addition, the eMLPP level is included as explicit information.
CHAN_MOD_MODIFY: Standard message.
Gu
CHAN_MOD_MODIFY_ACK: Standard message.
Call Waiting should always be subscribed together with eMLPP. If not, no called party pre-emption
r
is possible for point-to-point calls.
icto
SETUP (prec.) req. ind.: In addition to the basic call requirements, the contents of the set-up information flow shall
tV

SETUP: Modified SETUP message with
an indication of the priority level.
igh
CALL_CONF: Standard message with

cause user busy.
On reception of the SETUP message a
pyr
compatible Mobile Station decides on

called party pre-emption. If called party
pre-emption applies, the Mobile Station
Co
shall automatically accept the waiting

call and put the other call on hold.
A non compatible Mobile Station shall
not be harmed by the priority
information and shall perform Call
Waiting functions as normal.
Figure 9: Signalling for called-

party pre-emption in case
of an existing telephony call and
subscription for HOLD7
ALERT: Standard message.
7 NOTE: In case of an incoming data call a mode modify procedure has to be performed which is not included in figure 9.
ALERTING may be omitted in case of called party pre-emption.

HOLD: Standard message.
HOLD_ACK: Standard message.
CONNECT: Standard message.
CONN_ACK: Standard message.
Call Waiting should always be subscribed

together with eMLPP. If not, no called
party pre-emption is possible for point-to-
point calls.
SETUP (prec.) req. ind.: In addition to
the basic call requirements, the contents
of the set-up information flow shall
bs
SETUP: Modified SETUP message with
an indication of the priority level.
m
r Gu Figure10: Signalling for called-
party pre-emption in case of
icto
point-to-point data calls or no
subscription for HOLD
tV
CALL_CONF: Standard message with

cause user busy.
igh
On reception of the SETUP message a compatible Mobile Station decides on called party pre-emption. If called
party pre-emption applies, the Mobile Station shall automatically accept the waiting call and clear the existing data
call.
pyr
A non compatible Mobile Station shall not be harmed by the priority information and shall perform Call Waiting
functions as normal.
ALERT: Standard message. ALERTING may be omitted in case of called party pre-emption.
Co
RELEASE_COM: Standard message which shall be send immediately after the ALERT with a new cause for called
party pre-emption.
CONNECT: Standard message.
CONN_ACK: Standard message.

study on standards
Overview of call independent signalling
Registration
At the beginning of registration subscription, provision of the supplementary service and sufficiency of registration
information has to be checked.
The default priority level has to be registered in the network.
When the mobile subscriber registers eMLPP, the network shall attempt to register the service. The network will
return notification of acceptance of the request. This notification will include the default priority level.
If the system cannot accept a registration request, the network sends a notification that eMLPP registration was not
successful to the served mobile subscriber.
The information flow for registration of eMLPP is shown in figure 7.
m bs
r Gu
icto
tV
igh
pyr
Co
Figure 11: Registration of eMLPP

Interrogation
The mobile subscriber can request the status of the supplementary service, the maximum and default priority levels
and be informed if the service is provided to him/her and on the actual maximum and default priority levels. This
procedure is illustrated in figure 8.
m bs
r Gu
icto
Figure 12: Interrogation of eMLPP
tV
igh
pyr
Co

study on standards
Detailed view of the End-to-End Call Message Flows for Normal and Emergency Callsi
Introduction
In the GSM System, as seen previously, there are many components that are touched in order to process both normal
calls and priority calls whether they are MOC (mobile originated calls) or MTC (mobile terminated calls) and the
processing further varies based upon origination in the PSTN (public switched telephone network) or the PLMN
(public land mobile network). GSM services are global and must make minor adaptations as the boundaries between
vendors and countries are traversed. There are two variations of SS7 that are used as well: CCITT SS7 for most of
the world, and ANSI SS7 for North America and some countries. SS7 is an ISDN subnet component used for inter-
MSC communications and must be considered for the cases of inter-MSC handoffs, etc. When considering certain
aspects of the call flow signaling PAS architecture.
System Services
bs
The GSM PLMN services are divided into three categories, bearer services, teleservices, and supplemental or
m
augmentative services. Although in certain specific implementations (namely GSM-R where bearer services support
ATC), all three are marshaled for the purposes of supporting priority access; we will focus primarily on the
Gu
teleservices components as the other two play little or no role in our Priority Access Services model (e.g. call-waiting
is a recommended supplementary service to eMLPP).
r
icto
QoS GSM Quality of Service Requirements
tV
QoS aspects had been mentioned in prior sections and will just be amplified upon here once again for greater depth
igh
of understanding into the expectations, requirements and limitations in response times of any complex electronic
signaling system, which is subject to propagation and group delays inherent in both the wired and wireless network
portions.
pyr
It was shown in a previous section how call set-up times were improved by the bypass of some of the normal call set-
up functions to achieve sub-second response times by scaled back authentication, ciphering, and limiting the number
Co
of hand shake signaling to achieve this. However, there are other areas of consideration as well that must be
considered, and are applicable in some instances to the entire subscriber population. Namely, issues as switching to
a service ready mode should occur within 4 seconds in the home and within 10 seconds in the visitor system. The
area not mentioned or considered before is in the handover timing for both intra-MSC and inter-MSC. The nominal
time frames for the message passing and switching is 100 ms and 150 ms respectively. In consideration of normal
QoS for an MSC in regard to dropped calls no further improvement in performance is deemed necessary in this area.
Messaging in the GSM Network

In prior sections messaging has been discussed in some relative depth to the extent of that which occurs within the
GSM network itself. However for successful call handoffs between MSC’s and MTC calls originated outside the
PLMN, messaging on other Interworking networks must be considered namely the SS#7. Last the role of the SIM
card in relation to messaging and authentication and priority level evaluation of the PAS subscriber will be
discussed.
MS-BS Interface
Messages between the BS and MS are sent over a layered protocol stack, as that depicted in the OSI seven-layer
model with some modifications. A low level set of primitives are defined for transmission of messages and layer 3
the networking and transmission layer messages are transmitted within those primitives. Upper layers on the one
side of the interface communicate with the corresponding layer on the other side of the interface by sending
messages to its adjacent layer, and this is repeated until the message reaches the physical layer.
Messaging Primitives
 Request. This primitive is used when a higher layer requests a service from a lower layer.
 Indication. A lower layer on the other side indicates the request to the next higher layer using the indicator
primitive.
 Response. This higher layer on the other side acknowledges the indicator using the response primitive.
 Confirm. The lower layer on the requesting side confirms the request by sending a confirm primitive to the
next higher layer.
bs
Some layer 3 messages travel
between the BS and MS.
m
Others can only travel between
the Ms and the BS. A few
Gu
messages, which are call
control and mobility
management messages, travel r
directly between the MS and
icto
the MSC via the BS lower
levels of the stack only as they
are network in nature and do
tV
not terminate or originate in

the BS, and are classified
strictly as Mobility
igh
Management (MM) messages,

and circuit switched Call
Control messages (CC).

pyr
RR Radio Resource
messages control the
physical layer of the
Co
system, for channel

assignment, handover, ciphering, system information, paging, and MS information, and can be summarized
as follows:
Message BS MS MS BS Key Parameters Description

Additional CH Description, Mobile
Assignment
X Allocation
Assigns additional dedicated channels
Permits the BS to change the MS channel

Assignment CH Description, Mobile
Command
X Allocation
frequency to another channel in the same
cell
Assignment MS has established main signaling link
Complete
X Reason Code
successfully
Indicates that the MS did not seize the
Assignment Failure X Reason Code
new channel
Channel Mode CH Mode (Voice or
Modify
X Data)
Changes the Mode of the Channel

study on standards
Channel Mode CH Mode (Voice or
Modify Ack.
X Data)
Acknowledges Mode
Channel Release X Reason Code Releases the indicated channel

Channel Request X Establishment Code MS makes a request for a channel
Ciphering Mode
Command
X Start Ciphering Indicates to the MS to begin ciphering
Ciphering Mode Indicates that the MS has started

Complete
X ---
ciphering
Indicates that the class mark of the MS
Class Mark Change X MS Class Mark
has changed
BS requests class mark information from
Class Mark Enquiry X ---
the MS (GSM Phase 2)
Frequency CH Description Mobile Indicates that the frequencies and
Redefinition
X Allocation hopping sequence have changed
Initial message sent on the new channel
Handover Access X --- to inform new BS of the presence of the
bs
MS on that channel
CH Desc. Mobile Alloc.
Handover Command X Changes the channel allocation of the MS
m
Freq. CH Seq.
Indicates that a MS has established the
Handover Complete X Reason Code
Gu
signaling link on a new channel
Sent on the old mobile channel to
Handover Failure X Reason Code indicate the MS has failed to seize a new
channel
r
icto
Immediate
Assignment
X CH Description Moves an idle MS to a dedicated channel
Immediate
CH Description (1) CH Moves two idle MS’s each to a dedicated
Assignment X
tV
Description (2) channel

Extended
Immediate
Sent to up to 5 MS’s to indicate that no
Assignment X Wait Indication
igh
channel is available
Rejected
Reports on Signal strength from serving
Measurement Report X Measurement Results
and neighboring cells
pyr
Pages up to 4 MS, by their IMSI or TMSI…

Paging Request 1-3 X MS Identify (1-4)
1=1-2 MS; 2=2-3 MS; 3=1-4MS
Indicates that the MS has responded to
Co
Paging Response X MS Identity Classmark

the page
Indicates that he MS should release some
Partial Release X Channel Description
of the dedicated channels in use
Partial Release Confirms that MS has deactivated some
Complete
X ---
to the dedicated channel
Informs the MS to stop sending Access
Physical Information X ---
Bursts
Sent by either side to indicate error
RR Status X X RR Cause
condition
Synchronization
Channel Information
X --- Sent By BS to synchronize the MS
Call CH Desc., Call

System Information Selection Param. Sent By BS to Indicate the characteristics
Types 1-8
X Neighbor Cell Desc. of the BS
RACH Param
 Mobility Management messages are those that are unique to a phone that moves from one area to
another. These messages are associated with determining the IMSI and the assignment of a
TMSI, locating the MS, and authenticating the MS, and are summarized as follows:

BS requests that all mobility
Abort X Reason management connections be aborted
(GSM Phase 2)
Authentication
X --- Indicates that Authentication has failed
Reject
Authentication RAND (random Network request that the MS send
X
Request number) authentication
Authentication MS sends the response to the
X SRES (signal result)
Response authentication request
Circuit Mode
MS Identity, MS requests at reestablishment of a
Reestablishment X
MS Classmark failed connection
Request
MS requests that first mobility
Circuit Mode
X Message Type management connection be aborted
Service Abort
(GSM Phase 2)
Circuit Mode Informs the MS that its request for
X ---
Service Accept service has been accepted
bs
Circuit Mode Informs the MS that it request for
X ---
Service Reject service has been rejected
m
CM Service Type MS
Circuit Mode MS request a service of any of the three
X Classmark,
Service Request classes
Gu
MS Identity
Network request that the MS send its
Identity Request X Identity Type
Identity
Identity Response X MS Identity MS sends its Identity
IMSI detach
r
MS Classmark, MS MS request that its Identity be removed
icto
X
Indication Identity the MSC/VLR
Location Area
Location Update Indicates successful completion of
X Identification, MS
Accept update request
tV
Identity
Location Update
X Reject Cause Indicates failure to update request
Reject
igh
Location Area
Location Update MS request that its identity be updated
X Identification, MS
Request in the MSC/VLR
Classmark, MS Identity
pyr
Mobility Sent by either side to indicate an error

X X Reject Cause
Management Status condition
Co

TMSI Reallocation
X Mobile Identity Assigns New TMSI
Command
TMSI Allocation Indicates that MS has accepted new
Complete
X ---
TMSI
 A third class of message, the Circuit Switched Call Control message are similar to those found in the wireline
networks and includes call set-up, call disconnect, call status, and call progress messages and are summarized in greater
detail below:

Facility Progress Alerting is sent from one side to
Alerting X X Indicator, User-User the other, and can also be sent
Data from user to user
Call Confirmed X Bearer Capabilities Confirm Incoming all request
Call Proceeding X Bearer Capabilities Confirms Incoming Call Request
Used to flow control user 2 user
Congestion Control X X Congestion Level
Information

study on standards
Connect
X X --- Acknowledges Connection
Acknowledge
Cause, User 2 User Indicates that the network or the
Disconnect X X
Data MS has released the call
Sent by MS to indicate an
Emergency Setup X Bearer Capability
emergency call setup
MS requests that the current call
Hold X ---
be put on hold
BS confirms hold request of the
Hold Acknowledge X ---
MS
Hold Reject X --- BS rejects the request of the MS
Sending side requests a change in
Modify X X Bearer Capability
bearer capabilities
Modify Complete X X Bearer Capability Confirms a modify request
Bearer Capability Indicates a failure of modify
Modify Reject X X
Cause request
Notification Indicates that the other side has
Notify X X
bs
Indicator placed the call on hold
Indicates tht the call progress
m
Progress Indicator information is handled by tones
Progress X
User 2 User Data or announcements instead of
Gu
ISDN Messages
Cause, Facility, User Sending side requests that the
Release X X
2 User Data
r connection be released
Cause, Facility, User
Release Completed X X Confirms Release Message
icto
2 User Data
Retrieve X --- Retrieves a call on Hold
Retrieve
X --- Acknowledges a retrieve request
tV
Acknowledgement
Indicates that the retrieval
Retrieve Reject X ---
request cannot be processed
igh
Mobility Identity,
Calling Party
Setup X Starts a Call
Number, Facility,
pyr
User 2 User Data

Co
Indicates that the network should

Start DTMF X Keypad Facility convert the message into DTMF
tones
Start DTMF
X Keypad Facility Acknowledges start DTMF message
Acknowledgement
Indicates that the network cannot
Start DTMF Reject X Cause
accept and thus send DTMF tones
Indicates that the Network should
Stop DTMF X ---
stop sending DTMF tones
Stop DTMF
X --- Acknowledges Stop DTMF message
Acknowledge
Reports an error condition to the
Status X Cause, Call State
other side
Request a status report form the
Status Inquiry X X ---
other side
User Information X X User-User Data Sends User 2 User Information
BS to MSC Messages on the A Interface is done over one or more E1 circuits at data rates of 2048 kbps.
The signaling protocol layers are as follows:
 Physical Layer
 Message Transfer Part (MTP)
 Signaling Connection Control Part (SCCP)
 Base Station System Application Part (BSSAP)
 Base Station System Management Part (BSSMAP)
 Direct Transfer Application Part (DTAP)
 Base Station Operations Maintenance Application Part (BSSOMAP)
m bs
r Gu
icto
tV
igh
pyr
BSS -->
Message MSC --> BSS Key Parameters Description
MSC
Radio Channel, Circuit
Co
Assignment Request X Assigns Radio Resource at BSS

Identity Code
Assignment Complete X Radio Channel Confirms Radio Resource Assignment
Assignment Failure X Reason Code Indicates that assignment failed
Block X Circuit Identity Code Blocks use of time slot
Acknowledges the blocking of the time
Blocking Acknowledge X Circuit Identity Code
slot
Circuit Identity Code, Blocks the use of several time slots
Circuit Group Block X
Circuit Group List (GSM Phase 2)
Circuit Group Circuit Identity Code, Acknowledges the blocking of several
X
Blocking Acknowledge Circuit Group List time slots (GSM Phase 2)
Unblocks several time slots and
Circuit Identity Code,
Circuit Group Unblock X indicates that they may be returned to
Circuit Group List
service (GSM Phase 2)
Circuit Group Acknowledges unblocking of several
Circuit Identity Code,
Unblocking X time slots and returns them to service
Circuit Group List
Acknowledge (GSM Phase 2)
Clear Command X Cause Clears the indicated resource
Indicates that the resources has been
Clear Complete X ---
cleared

study on standards
BSS -->
MSC
Requests that the indicated resource be
Clear Request X Cause
released
Unblock X Circuit Identity Code Unblocks a time slot
Unblocking Acknowledges the Unblocking of the
X Circuit identity Code
Acknowledge time slot
Handover Candidate Requests the number of the MS’s where
X Number of MS’s
Enquire handover is required
Handover Candidate Indicates the number of MS’s where
X Number of MS’s
Response handover is required
Cell-ID (Serving),
Handover Request X Handover to this new BSS is requested
Cell-ID (Targeted)
Cell Identifier List The MS needs a handover to a new
Handover Required X
Preferred channel
Handover Required
X Cause Indicates that handover has not occurred
Reject
Hanover Request Indicates that the BSS can support the
X ---
Acknowledge handover request
bs
Indicates the new channel the MS must
Handover Command X ---
retune
m
Indicates successful handover to the new
Handover Complete X ---
BS
Gu
MSC sends indication to old BS
Handover Succeeded X ---
indicating that the handover succeeded
Handover has been aborted due to
Handover Failure X Reason Code
resource allocation failure
r Indicates that the BSS has performed a
icto
Handover Performed X Cause Radio Channel
handover internal to the cell
Indicates that the MS has successfully
Handover Detect X ---
accessed the target cell
tV
MSC requests the spare and optionally

Resource Request X Cell Identifier
the total resources at the BS
Indicates that the sending side has lost
Reset X X Cause
igh
all call state memory

Indicates that sending side has cleared
Reset Acknowledge X X ---
all calls and is ready to resume service
pyr
Cell Identifier, BS reports on spare and optionally the

Resource Indication X
Resources total resources
Paging X IMSI, TMSI Requests that the MS be paged
Overload X X Cause Cell Identifier Indicates that processor is in overload
Co
MSC Invoke Trace X Trace Type, BSS Invokes a trace record at the MSC
MSC Invoke Trace X Mobile Identifier (GSM Phase 2)
Invokes a trace record at the receiving
Trace Invocation X X Trace Number
entity (GSM Phase 1)
Classmark Update X Classmark Information MS has changed Classmark
MSC ask BS For the Classmark (on the
Classmark Request X ---
channel associated with the MS)
Cipher Mode Updates encryption information for the
X Encryption Information
Command specified MS
Cipher Mode Indicates that successful cipher mode
X Algorithm
Complete has been achieved on the air interface
Cipher Mode Reject X Cause Cipher mode cannot be started
BS sends layer 3 information when on
Complete Layer 3
X Layer 3 Information receipt of initial layer 3 messages (GSM
Information
Phase 2)
Indicates a delay in the assignment of
Queuing Indication X ---
the TCH (GSM Phase 2)
Service Access Point
Indicates that a message has been
Identifier (SAPI) n X Cause
rejected
Reject
SAPI n Clear X X --- Instructs the receiving entity to clear
BSS -->
MSC
Command resources
SAPI n Clear Indicates that all resources for SAPI n
X X ---
Complete have been released
Indicates that the circuit state is
Reset Circuit X X Circuit Identity
unknown due to a failure
Indicates the call using the circuit is
Reset Circuit
X X Circuit Identity cleared and the circuit is available for
Acknowledge
service
Indicates that the message sent by the
other side cannot be acted upon and no
Confusion X X Cause
other failure message is available (GSM
Phase 2)
Circuit Identity Code, The other side is attempting to use a
Unequipped Circuit X X Circuit Identity Code circuit that the sending does not
List recognize (GSM Phase 2)
Indicates that the resources are in
Cell Identifier,
Load Indication X X overload or unavailable at the BSS
Resource, Cause
bs
(GSM Phase 2)
Sets up a Group voice Call to MS Group
VGCS/VBS Setup X Group Call Reference
m
Members (GSM Phase 2)
VGCS/VBS Setup Confirms that the BSS will support the
X ---
Gu
Acknowledge group call (GSM Phase 2)
VGCS/VBS Setup BSS rejects the requested group call
X Cause
Refuse (GSM Phase 2)
Request to BSS to assign radio
VGCS/VBS Setup Group Call Reference,
X
r resources for the group call (GSM Phase
icto
Assignment Request Circuit Identity Code
2)
Channel Type, Cell Indicates that the radio resources for the
VGCS/VBS Setup
X Identifier, Chosen group call have been assigned (GSM
Assignment Result
Channel Phase 2)
tV
VGCS/VBS Setup Circuit Pool, Circuit Indicates failure of the assignment

X
Assignment Failure Pool List, Cause request (GSM Phase 2)
Indicates delay in the assignment of
igh
VGCS/VBS Setup
X --- radio resources for the group call (GSM
Queuing Indication
Phase 2)
Indicates that an MS has access to the
pyr
Uplink Request X ---

uplink of a group call (GSM Phase 2)
Uplink Request Acknowledges uplink request (GSM
X ---
Acknowledge Phase 2)
Co
Uplink Request Uplink has been successfully established

X Cell Identifier
Confirmation (GSM Phase 2)
Uplink Release Uplink has been released (GSM Phase
X Cause
Indication 2)
Uplink Reject Request for Uplink has been rejected
X Cause
Command (GSM Phase 2)
Uplink Release MSC has released uplink and it is
X Cause
Command available for allocation (GSM Phase 2)
Uplink Seized Uplink is no longer available for
X Cause
Command allocation (GSM Phase 2)
BSS has detected an overload in the
DLCI (Data Link
Suspend X corresponding connection (GSM Phase
Connection Identifier)
2)
DLCI (Data Link Overload situation no longer exists
Resume X
Connection Identifier) (GSM Phase 2)
Signaling and Messaging between the MSC to VLR/HLR

study on standards
The MSC communicates with the HLR and the VLR to manage those functions that are unique to the
mobile environment, as well as communicate over the various switching networks to other MSC’s via the
SS #7 subnet of the ISDN.
m bs
There are messages that which are directly related to the mobility management and are summarized below, and are basically
transmitted by one side of the an interface and confirmed by the receiving side, using the request, indication, response, and
Gu
confirm set of primitives as previously described in section Messaging Primitives for the BS-MSC Interface. As such, these
messages are segmented into several categories…
 Location management services… to update the HLR and VLR entries such that the network can
r
icto
locate a give MS.
 Paging and search services… to page an MS.
 Access management services… supports access to the network by the MS.
 Handover services… supports the movement of a mobile MS from cell to cell or servicing BTS
tV
to BTS and all combinations thereof.

 Authentication management services… supports the confirmation of an MS identity by using
igh
cryptographic techniques.
 Security services… provides privacy of the MS-BS link through cryptography.
 Subscriber management services… support HLR database updates as the subscriber changes
pyr
service subscription.
 Identity management services… support for IMSI and TMSI for MS’s.
 Fault recovery services… support for error recovery in the MS network signaling.
Co
The following tables summarizes all the messaging and signaling for each of the categories under
the general heading of Mobility Services…
Location management
Message Key Parameters Description
services…
MSC-VLR: updates the
UPDATE_LOCATION_AREA IMSI, TMSI, LAI VLR when the MS moves to
a new location area
VLR-HLR: updates the
UPDATE_LOCATION IMSI, VLR Number
HLR entry
HLR-VLR: Cancels the
CANCEL_LOCATION IMSI
VLR entry
VLR-VLR: Sends
TMSI (New VLR); information from old VLR
SEND_IDENTIFICATION
IMSI (Old VLR) to the new VLR, requested
bs
by new VLR
MSC-VLR: Removes DB
DETACH_IMSI IMSI or TMSI
m
entry in VLR
VLR-HLR: Removes DB
PURGE_MS IMSI, VLR Number
Gu
entry in HLR
Paging and search

r
icto
Message Key Parameters Description
services…
MSC-VLR: initiates paging
PAGE IMSI, TMSI, LAI
of an MS
tV
VLR-MSC: Used for paging

SEARCH_FOR_MS IMSI MS; used when VLR does
not know LAI the MS is in.
igh
Access management MSC-VLR: Initiates the

IMSI, IMEI, TMSI, LAI,
pyr
services… PROCESS_ACCESS_REQUEST
MS-ISDN Number
processing of an MS access
request
Co
Handover services… Target Cell ID, BSS-

MSC-A to MSC-B
PREPARE_HANDOVER used for inter MSC
APDU
handover
MSC-A to MSC-B For
inter-MSC handover to
SEND_END_SIGNAL BSS-APDU
release call records in
MSC-B
MSC-B to MSC-A
used to pass A
PROCESS_ACCESS_SIGNALING BSS-APDU
interface information
from MSC-B
MSC-A to MSC-B
used to pass A
FORWARD_ACCESS_SIGNALING BSS-APDU
interface information
to MSC-B

study on standards
MSC-A to MSC-B
used to indicate that a
BSS-APDU, Target MSC
PREPARE_SUBSEQUENT_HANDOVER handover back to
Number, Target Cell ID
MSC-A or to a third
MSC is needed
Handover services… MSC-VLR used to
(CONTINUED) ALLOCATE_HANDOVER_NUMBER --- request handover
number from VLR
VLR to MSC-B used
to transfer handover
SEND_HANDOVER_REPORT Handover number
number from MSC-B
to MAS-A
Authentication RAND (From VLR); SRES VLR-MSC: used to

AUTHENTICATE
management services… (From MS) authenticate the MS
IMSI (From VLR),
VLR-HLR: VLR requests
SEND_AUTHENTICATION_INFO Authentication Set (From
authentication information
bs
HLR)
m
Security services…
Gu
VLR-MSC: used to start
SET_CIPHERING_MODE Kt
encryption of radio link
r
icto
Subscriber management HLR-VLR: used when the
services… INSERT_SUBSCRIBER_DATA
IMSI, MS-ISDN Number HLR data has changed
Services because subscriber has
tV
changed subscription
HLR-VLR: used to update
the VLR when the HLR
igh
IMSI, MS-ISDN Number

DELETE_SUBSCRIPTION_DATA data has changed because
Services
subscriber has changed
subscription
pyr
Co
Identity management VLR-MSC: used to obtain

services… IMSI from MS when the
PROVIDE_IMSI IMSI TMSI transmitted by the MS
cannot be associated with a
known system
VLR-MSC used to allocate a
FORWARD_NEW_TMSI IMSI, TMSI new TMSI to a MS during
an ongoing transaction
Fault recovery HLR-VLR: indicates

HLR Number, HLR
services… RESET that the HLR has just
ID List
been reset
Fault recovery HLR-VLR: Indicates
services… that supplementary
FORWARED_CHECK_SS_INDICATION --- services may have bee
(Continued)
altered due to an HLR
reset
VLR-HLR: used when

IMSI, Local MSI, local roaming number
RESTORE_DATA
HLR Number for an MS maps to an
unknown MS
When a MS makes an outgoing call or receives an incoming call, the MSC, VLR, and HLR must
communicate with each other to obtain information pertaining to the MS. Including the MS Identity, MS
Services, MS temporary identities, MS roaming number in the system, etc.
Therefore, a group of Call Handling Messages are required to communicate this data.
Call Handling Message

Key Parameter Description
Messages…
Bearer Service, MS MSC-VLR: used on
SEND_INFO_FOR_INCOMING_CALL Roaming Number, incoming call to obtain
MS-ISDN Number information about an MS
bs
MSC-VLR: Used on
Bearer Service, Called
SEND_INFO_FOR_OUTGOING_CALL outgoing call to obtain
m
Number
information on an MS
MS-ISDN Number from MSC-HLR: used to
Gu
MSC, IMSI Number obtain information on and
SEND_ROUTING_INFORMATION
from HLR, MS Roaming MS in order to route the
r Number from HLR call to the
Call Handling Message
Key Parameter Description
icto
Messages…
IMSI, MSC Number,
HLR-VLR: used by HLR
MS-ISDN Number,
PROVIDE_ROAMING_NUMBER to obtain a roaming
tV
Local MS Identity LMSI,

number from the VLR
Roaming Number
VLR-MSC: used by the
MS-ISDN Number,
COMPLETE_CALL VLR to request that an
igh
IMEI, Bearer Capability

incoming call be set up
VLR-MSC: used by VLR
MS-ISDN Number,
PROCESS_CALL_WAITING to invoke call waiting at
pyr
Bearer Capability
the MSC
Co

study on standards
Expanded Details and summaries for Normal and Emergency Call Flow Scenarios in the GSM Network for GSMNA-1900
eMLPP and 02.11
Normal Call Flow

In these following scenarios we are give the following assumptions as a baseline consideration, as it will cover the
most complex of case conditions to be normally encountered. Under other basic considerations you are referred to
prior sections where this subject is first covered from a high level perspective and the flows, as mention therein, have
been simplified for the sake of the discussion purely for the basic understanding of its nature.
Here we will assume that the MS enters the new MSC area and has just powered up his unit, requires a location
update procedure involving registration, authentication, ciphering, and equipment validation.
Call setup by an MS is shown in the following figure, and step by step follows in the legend.
m bs
r Gu
icto
tV
igh
pyr
Co
First a MOC (Mobile Originated Call)
1. The user dials a number and presses the SEND button or other action to initiate a call. The MS sends a setup
message to the MSC after it begins ciphering the radio channel. This message includes the dialed digits.
2. Upon receiving the setup message, the MSC request the VLR to supply the subscriber parameters necessary
for the handling of the call via the Send_Info_for_Outgoing_Call message. The message contains the called
number and Service Indication.
3. The VLR checks for call barring conditions. If the VLR determines that the call cannot be processed, the
VLR provides the reason to the MSC. In this case, we assume that the procedure is successful and the call can
be processed. The VLR returns a complete message to the MSC containing the service parameters for the
subscriber.
4. The MSC sends a Call_Proceeding message to the MS.
5. The MSC allocates an available trunk to the BSS currently serving the MS. The MSC sends an Assignment
message to the BSS supplying it with trunk number allocation data, and asks to assign a radio TCH for the
MS.
First a MOC (Mobile Originated Call) continued…
6. The BSS allocates a radio channel and sends an Assignment message to the MS over the SDCCH.
7. The MS tunes to the assigned radio channel and sends an Assignment _Complete message to the BSS.
8. The BSS connects the radio TCH to the assigned trunk to the MSC and deallocates the SDCCH. The BSS
informs the MSC with a trunk and radio Assignment _Complete message. At this point the voice path is
established between the MS and MSC. The MS user still hears silence or comfort noises to indicate that the
call is progressing, until the voice path is completed, in subsequent steps.
9. The MSC sends the Initial_Address_Message message to the PSTN to request call setup. This message
includes the digits dialed by the MS and details of the trunk that will be used for the call.
10. The PSTN sets up the call and notifies the MSC with the Address_Complete message.
11. The MSC informs the MS that the destination number is being alerted. The MS hears the ringing tone from
the destination local exchange through the established voice path. The MSC sends an Alerting message to
the MS.
bs
12. When the destination party goes off-hook, the PSTN informs the MSC via the Answer message.
13. The MSC informs the MS that the connection has been established via the Connect message.
m
14. The MS sends a Connect_Acknowledgement to the MSC and the voice path is complete and talking can
begin.
Mobile Terminated Call (MTC)

r Gu
In this scenario let us assume that the MS is already registered in the system and has been assigned a TMSI. It will
icto
further be assumed that the MS is in his home system. The fixed network subscriber dials the directory number of the
mobile subscriber.
tV
igh
pyr
Co
1. The PSTN routes the call to the MSC assigned this directory number. The directory number in the IAM
message is the MS-ISDN Number (MSISDN).
52 AT&T — PROPRIETARY Document Type: Architecture and Survey and study on standards
2. The MSC sends the Send_Routing_Information message to the HLR to provide the routing information for
the MSISDN.
3. The HLR acknowledges the Send_Routing_Information message to the MSC. This message contains
MSRN. If the MS is roaming within the serving area of this MSC, the MSRN returned by the HLR will
most likely be the same as MSISDN. In the current scenario we are assuming that the mobile is not roaming.
Mobile Terminated Call (MTC) continued…
4. The MSC informs the VLR about the incoming call using a Send_Info_for_Incoming_Call message that
includes the MSRN.
5. The VLR responds to the MSC through a Page message that specifies the LAI and TMSI of the MS.
6. The MSC uses the LAI provided by the VLR to determine which
BSS’s will page the MS. The MSC sends the page message to
each of the BSS’s (on the PCH) to perform paging of the MS.
The paging request message may contain one or more MS
identifier, depending upon how many MS’s need to be paged up
to a maximum of four, when only TMSI’s are used for
bs
identification. Upon receipt of the paging request message, if
m
access to the network is allowed, the addressed MS initiates the
assignment procedure by requesting a channel through the
Gu
RACH. Upon receiving the message, one designated BSS sends
an acknowledgement message over the AGCH (access grant
channel), with the same random number as originally received
r
and the channel number for the SDCCH. The MS sends a Set
icto
Asynchronous Balance Mode (SABM) frame containing the
paging response.
tV
7. Each BSS broadcasts the TMSI of the MS is the Page Request message on the PCH.
8. When the MS receives its TMSI broadcast on the PCH, it responds to the BSS with a Channel Request
igh
Message over the common access channel, RACH.

9. On receiving the Channel Request Message from the MS, the BSS allocates an SDCCH and sends the
Immediate Assignment Message to the MS over the AGCH. It is over the SDCCH that the MS communicates
pyr
with the BSS and MSC until a TCH is assigned.

10. The MS sends a Page Response Message to the BSS over the SDCCH. The message contents are the MS’s
TMSI and LAI.
Co
11. The BSS forwards the Page Response Message to the MSC.
12. The MSC sends a Process Access Request message to the VLR.
13. The VLR responds with a Complete Call Message.
14. The MSC then sends a Setup Message to the MS.
15. The MS responds with a call confirmed Message.
16. The MSC then sends an Alert Message to the MS.
17. The MSC sends an Address Complete Message to the PSTN.
18. When the user answers, the MS sends a connect message to the MSC.
19. The MSC in turn sends a Connect Acknowledgement to the MS.
20. The MSC sends an Answer Message to the PSTN. The two parties can now talk.
21. The VLR closes the dialog with the MSC by sending a Send Info for the Incoming Call acknowledgement to
the MSC.
Call Release
Under normal conditions, there are two basic ways a call is terminated: mobile initiated and network initiated. In
this scenario, shown in the figure below, we assume that the mobile user initiates the release of the call.
1. At the end of the call the MS sends the Disconnect message to the MSC.
2. On receiving the Disconnect message, the MSC sends a Release message to the PSTN to release the call.
3. The MSC asks the MS to

begin its clearing procedure
using the Release message.
4. After the MS has
performed its
clearing procedure,
it informs the MSC
bs
through the
Release_Complete
m
message.
5. The PSTN sends a
Gu
Release_Complete
message to the
r MSC. The order of
steps 4 and 5 may
icto
be reversed
depending upon the
network timing.
tV
6. The MSC then

sends the Clear_Command message to the BSS to ask it to release all the allocated dedicated resources
for a given SCCP connection.
igh
7. The BSS sends the Channel_Release message to the MS to release the TCH.
8. The BSS sends a Clear_Complete message to the MSC informing it that all allocated dedicated
resources have been released.
pyr
Handover
Co
Basically there are two types of Handover of the nature of internal or external. If the serving and target BTS’s
are located within the same BSS, the BSC for the BSS can perform the Handover without the involvement of
the MSC. This type of Handover is referred to as intra-BSS Handover. However, if the serving and target
BTS’s do not reside within the same BSS, an external Handover is performed. In this type of Handover the
MSC orchestrates the Handover and performs the switching task between the serving and target BTS’s. The
external Handovers can be classified further as an intra-MSC or an inter-MSC.
Intra-MSC Handover The MSC constantly monitors the signal quality of the BSS-MS link, in terms of SNR,
BER, etc. The BSS may also optionally forward its own measurements to the MS. When a quality of signal
threshold is crossed the MS may attempt to maintain the desired signal quality of the radio link by requesting a
handover if an adjacent BTS signal quality is better.
1. The MS determines that a Handover is required; it sends the Measurement_Report message to the
serving BSS. This message contains the signal strength measurements.
4.1.0.0© 2001 AT&T Wireless Services, Inc. Wireless Priority Access Services
2. The Serving BSS sends a Handover_Request message to the MSC. This message contains a Rank-
Ordered-List of the qualifying target BSS’s that are able to receive the call.
3. The MSC assesses the global cell identity associated with the best candidate to determine if one of the
BSSs it controls is responsible for the cell area. In this scenario the MSC determines that the cell area
is associated with the target BSS. To perform the an intra-MSC Handover, two resources are
required… a Trunk between the MSC and the target BSS, and a radio TCH in the new cell area. The
MSC reserves a Trunk, and send the Handover_Request message to the target BSS. This message
includes the desired cell area for the Handover, the identity of the MSC-BSS Trunk that was
reserved, and the encryption key (Ki).
4. The target BSS selects and reserves the appropriate resources to support the Handover pending
connection execution. The target BSS sends a Handover_Request_Acknowledgement message to the
MSC. The message contains the radio channel identification.
5.
m bs
r Gu
icto
tV
igh
pyr
Co
Document Type: Architecture and Survey and study on standards AT&T — PROPRIETARY 55
XXXXX Rev. 1.0 5/28/01 Use pursuant to Company instructions
4.1.0.0Wireless Priority Access Services © 2001 AT&T Wireless Services, Inc.
Glossary of Terms
AIN: Advanced Intelligent Network
ALI: Automatic Location Identification
ANSI: American National Standards Institute
AP: Adjunct Processor
API: Application Program Interface
Applic.: ENS service applications, such as personal number
AuC: Authentication Center
AC: Authentication Center
BER: Bit Error Rate
bs
CAMA: Centralized Automatic Message Accounting
CCITT: Consultative Committee on International Telephone and
m
Telegraph
CCS: Common Channel Signaling
Gu
CCS: Compaq Customer Services
CDC: Call Detail Record r
CDMA: Code Division Multiple Access
icto
CO: Central Office
CPC: Carrier Portability Code
CS: Compaq CustomSystems
tV
CTNS: Compaq Telecommunications Network Solutions

EIR: Equipment Identity Register
igh
ENS: Enhanced Network Services

ETSI: European Telecommunications Standards Institute
pyr
FDD: Frequency Division Duplexing

FDMA: Frequency Division Multiple Access
Co
FGA: Feature Group A

FGD: Feature Group D
GSM: Global System for Mobile Communications
HLR: Home Location Register
IESP: Internet Enhanced Services Platform
IMEI: International Mobile Equipment Identity
IMSI: International Mobile Subscriber Identity
IN: Intelligent Network
INAP: Intelligent Network Application Protocol
INS: Intelligent Network Services
INSDP: Intelligent Network Services Delivery Platform (SS7)
4.1.0.0© 2001 AT&T Wireless Services, Inc. Wireless Priority Access Services
IP/SN: Intelligent Peripheral and Service Node

IP: Intelligen Peripheral
IP: Internet Protocol
IS-41: Interim Standard 41
ISO: International Standards Organization
ISUP: ISDN User Part
IVR: Interactive Voice Response
LAPD: Link Access Protocol on the D Channel
LDAP: Lightweight Directory Access Protocol
LRN: Location Routing Number
MIN: Mobile Identification Number
bs
MM: Mobile Management
MSC: Mobile Switching Center
m
NEBS: Network Equipment Building System
Gu
NSIS: Network Systems Integration Services
OA&M: Operating, Administration & Maintenance
OAM&P: Operations, Administration, Maintenance & Provisioning
r
Open Database Connectivity
icto
ODBC:
OMC Operations Management Control
OSS: Operation Support Systems
tV
pANI: pseudo Automatic Number Identification

PLMN: Public Land Mobile Network
igh
PSAP: Public Safety Answering Points

PSTN: Public-Switched Telephone Network
RAD: Rapid Application Development
pyr
SCE: Service Creation Environment

SCP: Service Control Point
Co
SCSA: Signal Computing System Architecture

SCCP: Signaling Connection Control Point
SDCCH: Stand Alone Dedicated Control Chanel
SDMA: Spatial Division Multiple Access
SIBS: Service-Independent Building-blocks
SMSC: Short Messaging Service Center
SMS: Service Management System
SN: Service Node
SP: Signaling Point
SPAM: random indiscriminate posting of items (often advertisements) on
computer bulletin boards or in email
Document Type: Architecture and Survey and study on standards AT&T — PROPRIETARY 57
XXXXX Rev. 1.0 5/28/01 Use pursuant to Company instructions
4.1.0.0Wireless Priority Access Services © 2001 AT&T Wireless Services, Inc.
SS # 7: Signaling System 7
STP: Signal Transfer Point
TCH: Traffic Control Channel
TCU: See TRAU:
TEM: Telecommunications Equipment Manufacturers
TRAU: Transcoder and Adaptation Control Unit
VAS: Value-Added Services
VLR: Visitor Location Register
VoIP: Voice over Internet Protocol
WAP: Wireless Application Protocol
WIN: Wireless Intelligent Network
m bs
r Gu
icto
i
REFERENCES
tV
http://www.etsi.org/download/home.htm
1. GSM Specifications Series 01.02-01.06, “GSM Overview, Glossary, Abbreviations, Service Phrases.”
2. GSM Specifications Series 02.01-02.88, “GSM Services and Features.”
igh
3. GSM Specifications Series 03.01-03.88, “GSM PLMN Functions and Architecture, Numbering and Addressing Procedures.”
4. GSM Specifications Series 04.01-04.88, “MS-BSS Interfacing.”
5. GSM Specifications Series 05.01-05-10, “Radio Link.”
GSM Specifications Series 06.01-06.32, “Speech processing.”
pyr
6.
7. GSM Specifications Series 07.01-07.03 “Terminal Adaptation.”
8. GSM Specifications Series 08.01-08.60 “BSS-MSC Interface; BSC-BTS Interface.”
9. GSM Specifications Series 09.01-09.11 “Network Interworking, MAP.”
Co
10. Russell, Travis, “Signaling System #7” 3rd Edition, ISBN0-07-136119-7, McGraw Hill Telecommunications, 2000
11. Heine, Gunner, “GSM Networks: Protocols, Terminology, and Implementation” ISBN 0-890006-471-7, Artech House Mobile
Communications Series, 1998
12. Schiller, Jochen, “Mobile Communications” ISBN 0-201-39836-2, Pearson Education Ltd., Addison Wesley, 2001 i

Wireless Priority Access Services Docume

Uploaded by

Copyright:

Available Formats

Wireless Priority Access Services Docume

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Wireless Priority Access Services Docume

Uploaded by

Copyright:

Available Formats

ETEL Systems

Wireless Priority Access Services

This document contains trade secrets and proprietary information of

Date Revision Description

Steering Committee - Date

For questions about this document, please contact:

3.1.3 Response from Vendors

3.2.3.4 Nortel Networks

serving the NSEP needs of Federal, State and local governments.

even enable the successful operation this feature?

Priority Access Service Standards Compared

Some Key Points:

Enhanced Priority Access and Channel Assignment (PACA-E)

get radio access before non PACA-E calls.

6 AT&T — PROPRIETARY Document Type: Architecture and Survey and

GSM 02.11, Service Accessibility (Access Control) r Gu

Feature PACA-e GSM 02.11 e-MLPP

Roaming Support Yes r Yes Yes

Across MSC No Yes Yes

Allows for egress (not Yes No Yes

required in R&O, but

Table 1.0 Key Feature Requirements form the R&O Compared

8 AT&T — PROPRIETARY Document Type: Architecture and Survey and

10 AT&T — PROPRIETARY Document Type: Architecture and Survey and

Figure 1. General architecture of a GSM network

Base Station Subsystem

Radio link aspects

12 AT&T — PROPRIETARY Document Type: Architecture and Survey and

2 Multiple access and channel structure

4 Channel coding and modulation

14 AT&T — PROPRIETARY Document Type: Architecture and Survey and

 Class Ia 50 bits - most sensitive to bit errors

 Class Ib 132 bits - moderately sensitive to bit errors

 Class II 78 bits - least sensitive to bit errors

Figure 3. Signalling protocol structure in GSM

16 AT&T — PROPRIETARY Document Type: Architecture and Survey and

10 Radio resources management

 Cells under the control of different MSCs.

IMSI attach/detach is up to the operator on an individual cell basis.

Authentication and security

18 AT&T — PROPRIETARY Document Type: Architecture and Survey and

Figure 4. Call routing for a mobile terminating call

20 AT&T — PROPRIETARY Document Type: Architecture and Survey and

Call Set-up Time Improvements

Class Setup Time Priority Level

Table 2. Nominal Call Setup Times

Automatic Answer for priority Calls

Mobil Station MS Network

Table 3. Simplification of a Normal Call Setup

Table 4. Simplification of Fast Call Setup High Priority

ASSIGNMENT_REQUEST. HANDOVER_ REQUESTs including BSC internal handover requests do not

22 AT&T — PROPRIETARY Document Type: Architecture and Survey and

Detailed Priority Access Service with e-MLPP Main concepts

B (for network internal use)

collision have to be managed by a corresponding planning of the network resources);

queuing and pre-emption mechanisms are applied for eMLPP);

h) The accommodation of non-compatible Mobile Stations.

- mobile terminated point-to-point calls:

- mobile to mobile point-to-point calls: r