Priority Service Support in the Core Network

Damir Buric, Lovre Hribar, Alen Bulic

Ericsson Nikola Tesla, d.d.
Poljicka 39, Split, Croatia
Phone: +38521434937 Fax: +38521434834 E-mail: Damir.D.B.Buric@ericsson.com
Abstract: Certain system
conditions (e.g. emergency
situations, network
overload) result in
congested networks with
blocking call attempts and
thus an inability to handle
emergency service calls.
Under these situations, it
should be possible to
priorities certain calls and
provide greater support to
national, regional and
international emergency
organizations. United States
(US) regulators defined the
Wireless Priority Service
(WPS) intended for
National Security and
Emergency Preparedness
(NS/EP) leaders and key
personnel in the US.
Layered architecture was
not taken into account.
Standardization activities
for Priority Service that
should cover the layered
architecture within 3GPP
and ITU-T has started.
Point of congestion that the
layered architecture
introduces will be stated in
this paper.
I. INTRODUCTION
As defined in the Ref.[1],
Priority Service allows
qualified and authorized
users to obtain priority
access to the next available
radio (voice or data traffic)
channels on a priority
basis before other PLMN
users during situations
when PLMN congestion is
blocking call attempts. In
addition, Priority Service
supports priority call
progression and call
completion to support an
“end-to-end” priority call.
Priority Service is
intended to be used by
qualified and authorized
users, i.e., emergency
service personnel, only
during times of emergency
situations and network
congestion. Access to
Priority Service is limited
to key personnel and those
with leadership
responsibilities and is not
intended for use by all
emergency service
personnel. This is to
ensure that non-emergency
service personnel cannot
“take over” the network
and deny the other non-
emergency service
subscribers a reasonably
level of service.
An Industry
Requirement document,
Ref.[2] was developed
under the auspices of the
National Communications
System (NCS) in the
United States and in co-
operation with companies
from the
telecommunication
industry in order to
standardize the Wireless
Priority Service (WPS) for
GSM systems. The first
phase called WPS-IOC
(Initial Operating
Capabilities) and the
second phase called WPS-
FOC (Full Operating
Capabilities). WPS is
intended to facilitate
emergency response and
recovery operations in
response to natural and
man-made disasters and
events, such as floods,
earthquakes, hurricanes,
and terrorist attacks. WPS
is also intended to support
both national and
international emergency
communications. It will
provide National Security
and Emergency
Preparedness (NS/EP)
leaders and key personnel
in the United States
priority treatment when
using telecommunication
networks. It will be
implemented in GSM-
based systems and in the
PSTN; i.e. NS/EP calls
will be given end-to-end
priority treatment, across
all call paths, mobile-
mobile, mobile-fixed, and
fixed-mobile. The
regulatory requirements
for WPS-IOC and WPS-
FOC do not take the
layered architecture into
account.
However, it can be
foreseen that the layered
architecture must be
supported in a longer time
perspective for the network resources for WPS
following reasons : subscribers. WPS makes,
 There could come within the network, use of
the access priority levels
additional
requirements on provided by the enhanced
WPS-FOC from Multi-Level Precedence
the US regulatory and Pre-emption (eMLPP)
organisation to feature. Invoking WPS
support also the calls on a per call basis by
layered dialling the prefix (i.e.,
architecture; *272) avoids the need for
 The installed eMLPP compatible User
based of layered Equipment. Besides WPS
calls there are another
architecture
reaches a critical kind of priority calls, so
level where lack called Government
of support for Emergency
WPS becomes Telecommunication
apparent; Service (GETS) calls. For
 Standardization a GETS call no prefix is
activities within used. A GETS call is
3GPP and ITU-T invoked by dialling
dedicated numbers e.g.
has started for
710-NCS-GETS (710-627-
WPS services and
they will cover 4387). In total five
different numbers can be
the layered
architecture. As a used to identify a GETS
result from this, call. Compared to a WPS
operators might call no priority levels are
demand WPS used for a GETS call.
with support for WPS and GETS calls are
3G and layered both priority calls or so
architecture also called NS/EP calls.
outside of the US. Priority handling for such
At the moment calls is only applicable
only a frame has during call setup.
been discussed Procedures proposed in
and there is no Ref.[2] include two
indication as to in general categories of
which direction functions:
the solutions will • Capabilities used to mark
go. calls that require special
WPS processing (e.g.,
including an NS/EP call
II. WIRELESS indication and the Service
PRIORITY SERVICE IN User’s priority level) and
MONOLITHIC to pass this special
ARCHITECTURE marking to subsequent
nodes along the call path
WPS is invoked on a per (in order to enable
call basis using WPS subsequent WPS
dialling procedures, i.e., processing); and
WPS calls are originated • Capabilities used to
by dialling increase the probability of
*272+Destination Number. WPS call completion as
WPS is a subscription the call progresses from
service. Subscriptions are the originating node,
only granted on through any transit nodes,
recommendation of an and on to the terminating
authorising agency (in the node.
U.S.A. that will be the WPS requirements are
NCS). WPS does not pre- based on the functions
empt established calls in defined by the HPC
progress; rather, WPS, Network Capability
provides priority access to requirements, Ref.[3]. The
HPC Network Capability progresses through the The following items in PS domain SMS-SC LCS

requirements specify the originating and any transit Fig. 1 are addressed: GGS
N
SGSN SM
IWMSC/GM
S
GML
C
SC
setting of the Calling networks, and on to the 1. (ISUP/CAS) Lh
10 7
Party’s Category (CPC) terminating network. connections between RAN Gs Lg
parameter and MTP • Provide a higher MTP nodes or towards other Um BSS HLR
H
AUC

priority values in the message priority for all networks: congestion 3 RNS
CTM
(ANSI)
D
2
Initial Address Message MAP messages that are and priority handling MS
8 2 2 C gsmSSF
1
A
(IAM) (i.e., the CPC required to successfully set 2. TCAP interfaces IuCS
2
Nc 2
GMSC
5 Nc

parameter value set to up a WPS call. These between GMSC, HLR, gsmSSF
MSC
1
Nc TSC
2
“NS/EP call” and IAM procedures increase the MSC/VLR, EIR, and PABX
PRA 4
LNP
6

MTP priority set to “1”). probability of the LNP-DB: priority F

2 DB
Control plane
The HPC Network corresponding messages handling for TCAP EIR
User plane
User & contro
Capability provides for being successfully dialogues
treatment triggered by the transferred to their 3. No radio channel Fig. 1. Congestion or
CPC parameter set to destination in the case of available at radio blocking points in Monolithic
“NS/EP call” or based on congestion in the signaling interface Network Architecture
the recognition of a pre- network. 4. MSC/VLR:
defined dialed digit • Set the (optional) ISUP  network
pattern. The HPC Precedence parameter management 7. Interface between
Capability includes the within the IAM to indicate controls gsmSSF and gsmSCF
marking of specified calls the specific priority of the  interactions with 8. BSC - MSC trunk
and the execution of WPS call as assigned in supplementary congestion.
additional network the originating Service services 9. Congestion in SS7
treatment to increase the Provider’s network. The signalling network:
 shortage of
probability of call Precedence parameter is STP not part of the
system resources,
completion. These used in conjunction with MSC/VLR, GMSC, or
which could be:
treatments include the the MLPP service. This TSC therefore not in
too few software
following: parameter will be used for the scope of the
individuals, not
• Exemption from certain WPS, without invoking the report. The STP will
enough hardware
restrictive network pre-emption capabilities of send the received
devices, or lack of
management controls. MLPP. MTP priority level
Mobile Station
• Trunk queuing. • Pass the Precedence transparently to the
Roaming
The HPC Network parameter through the next node. The MTP
Numbers
Capability relies on the telecommunications congestion function
5. GMSC:
deployment of SS7 network. can be used in the STP
 network in the same way as in
switching system • Recognize the management
capabilities, including the Precedence parameter in an MSC (see chapter
controls TCAP signalling).
ability to: the IAM in order to afford
 interactions with 10. Gs interface.
• Set the CPC parameter special WPS treatment at
supplementary
within the IAM to identify the terminating node (for
services
the call as an NS/EP call calls that are destined for a
based on the dialled digits. wireless user). The priority  shortage of III. WIRELESS
• Pass the CPC parameter of the WPS call is system resources; PRIORITY SERVICE IN
through the considered in allocating e.g. too few LAYERED
telecommunications terminating radio traffic software ARCHITECTURE
network. channel resources if no individuals
• Pass the SS7 MTP radio traffic channel is 6. TSC: Layered architecture was
priority of “1” for the SS7 available.  network not taken into account in
IAM to increase the Several possible points of management Ref.[2]. When introducing
probability of delivery of congestion where WPS controls layered architecture with
the SS7 IAM to the next calls may experience  shortage of ATM or IP backbone
exchange in case of blocking in their end-to- system resources; networks, the WPS user
congestion in the signaling end call path will need to e.g. too few will expect the same
network. be overcome. Some of software handling as in the non-
• Recognize the NS/EP call these congestion points are individuals layered architecture: the
indication in the CPC in identified in Fig. 1. While probability of completion
the IAM. these are not the only should not worsen. In
Beyond the HPC congestion points within order to ensure this, longer
capabilities several the various call paths, they delays are accepted during
additional capabilities are the most likely and the call establishment to
would increase the will significantly impact allow e.g. waiting for a
probability of WPS call the call flow before other requested resource to
completion. These blocking points are become available.
additional procedures are expected to begin to have NS/EP calls should be
applied to a WPS call as it an impact. prioritized whenever
possible over any other Priority handling: the 4.There could be 7. For WCDMA only:
type of calls, including MGW could reserve some congestion on the Nc There could be congestion
emergency calls. processor capacity only for interface which would in the Iu interface.
In a layered architecture NS/EP calls, that is, if the cause call control RAB assignment requests
there are additional points processor load reaches a messages (e.g. IAM, should be queued if no air
of congestion that don’t certain level, the MGW ACM) to be delayed or resources are available, in
exist in a non-layered should reject all MSC discarded. There are two a similar way as it is
network. server attempts of different possible protocols proposed in Ref.[1] for the
Fig. 2 shows those establishing new calls, on the Nc interface: ISUP A-interface.
additional points of except for NS/EP calls. and BICC. (IPBCP is
congestion that the layered Alternatively, the NS/EP tunnelled in BICC and not IV. HIGH LEVEL
architecture and WCDMA calls could share some regarded as a separate REQUIREMENTS FOR
introduce. reserved processor capacity protocol) PRIORITY SERVICE IN
with emergency calls. Priority handling: 3GPP
The following points of The MSC could use the M3UA/MTP3b priorities
congestion have been MGW congestion should be applied to BICC Standardization activities
identified: information, which is a messages related to a WPS for Priority Service that
1.There could be reflection of the processor call on the same way as it should cover the layered
congestion on the Mc link load in the MGW, to avoid is proposed in WPS FOC architecture has started. At
between MSC server and selecting congested MGWs for ISUP messages that use this stage, the Ref. [1]
MGW with the result that and, in case no other the MTP priority . performs a Gap Analysis to
messages to control the MGW is available, only 5.There could be assess the ability of
bearer signalling do not allow NS/EP calls to congestion in the Nb existing 3GPP
reach the other node or are attempt the congested interface, that is, in the specifications to meet the
delayed. MGW. bearer connectivity high-level Priority Service
Priority handling: Another advantage is that resources. This is a requirements.
MTP3b/M3UA priority MSC could attempt network-type-of congestion 1.Priority Call Origination
could be applied to GCP different MGWs and/or as opposed to e.g. the A call shall receive priority
messages related to a WPS repeated times each MGW bearer handling resources, treatment (priority access
call. if an attempt meets which is an internal node to voice or traffic
2. There could be congestion in the MGW. congestion. channels) on the
processor load congestion 3.There could be Priority handling: Q.AAL2 originating side, when the
in the MGW with the congestion in the bearer priority should be applied call is setup by a Service
result that the MGW is not handling resources in the to bearer control messages User using the priority
able to execute GCP MGW, that is, in software related to a WPS call. service dialling procedure.
commands. or hardware resources in Q.AAL2 priority requires 2.Priority Call Termination
the MGW. CS3. A call shall receive priority
Priority handling: The MTP3b priority should be treatment (priority access
MGW could reserve some applied to Q.AAL2 to voice or traffic
LCS
LCS
CSE/SN
extra software LIS and messages related to a WPS channels) on the
GMLC client gsmSCF
hardware resources -
for the
LI IMS LEMF
call. terminating side, when the
Lh NS/EP usage only
X1,X2
(these
HI3
IP admission control could call is setup by a Service
PS domain
Lg FNR HLR
H
AUC
resources are dynamic). be by-passed for WPS User using the priority
GGSN SGSN
Alternatively, NS/EP calls calls. service dialling procedure.
Multi Service
RAN CTM
Gs D
C gsmSSF could use the existing -
Network For ATM, the MGW 3.Priority Progression
BSS
node
gsmSSF Nc 4
GMS
server
C resource
Nc TSC
6 reservation should queue the MSC The user should receive
A/A ter MSC
server Mc mechanismserver for emergency PLMN
server request until priority call
EIR
RNS
IuCS 7 1 Mc
F
MGW
calls. Mc
ISDN/PSTN
bandwidth (BA & BIR) is treatment/progression
MGW 5
Nb The Nb
MSC
MGW
6
could repeat the available. through the mobile
2 3
PL BH
BC
attempt several times to For ATM, the MSC should network(s). A priority call
Controlrequest
plane thelegacyresources CAS, if TUPit attempt different MGWs should be given higher
PRA User plane
User &meets congestion. It Legacy
may and/or repeated times each
PABX NW
access control
access
priority over normal calls
Fig. 2. Layered Architecture as well repeat the attempts MGW if an attempt meets in the originating mobile
Specific Congestion or on different MGWs. congestion in the MGW. network, to interconnected
Blocking Points in The MGW could queue the 6. There could be networks supporting
WCDMA/GSM CS Core request until the needed congestion on the external priority (including the
Network resources are available. TDM trunks PSTN) and in the
Remote trunk queuing: terminating network.
The MSC should perform Vendor specific
trunk queuing in a similar functionality is needed to
way as it is proposed in set priorities for each leg.
Ref.[1] for local ISUP in This may not be supported
the non-layered in all interfaces or some
architecture. nodes on path may not
have needed functionality.
4.Priority Radio Resource
Queuing
When a Priority Service
call encounters a “no radio
available” condition in the
call path involving an
access or egress air-
interface, or both, and, at
call origination, and upon
recognition of the Priority
Service dialing pattern, the
Priority Service call is
queued in the cell serving
the calling party and
processed for the next
available radio channel in
that cell in accordance
with the caller’s priority
level and call initiation
time. At call termination
upon recognition of a
priority call indication in
an incoming call, the
Priority Service call is
queued in the cell serving
the called party and
processed for the next
available radio channel in
that cell in accordance
with the call’s priority
level and arrival time.
5.Priority Level
The subscriber should be
assigned one of n priority
levels. Priority levels are
defined as 1, 2, 3,…,n ,
with 1 being the highest
priority level and n being
the lowest priority level.
6.Invocation on Demand
Priority Service is invoked
only when requested and
an idle voice or traffic
channel required for an
origination request is not
available.
7.Applicability to
Telecommunications
Services Priority Service
shall be applicable to voice
and data
telecommunications
services that require a
voice or traffic channel
assignment.
8.Authorization
A subscriber invoking
Priority Service on call
origination is authorized
based on the caller’s
subscription. It should also
be possible for an
additional second level of
authentication (e.g., by the
use of PIN) to identify that
the user is authorized to
make a priority call. In
this case, authorization of
the subscriber may be
realized..
9.Priority Service service
code.
Priority Service is
manually requested by
adding on the Priority
Service service code to the
origination request.
10.Roaming
Priority Service shall be
supported during roaming
when the roaming network
supports Priority Service.
11.Handover
Priority Service shall be
supported during
handover.
12.Priority Service
charging data record
The system should record
the following Priority
Service charging data
information, in addition to
non-Priority Service CDR
information: Priority
Service invocation
attempts,
Call legs (origination
and/or termination) on
which Priority Service was
used to gain access to the
radio channel.
Recording of appropriate
Priority Service
information.
13.Priority Trunk Queuing
Priority Service shall be
able to support queuing of
Priority Service calls for
trunk resources.
14.Coexistence with
eMLPP
As a service provider
option, it shall be possible
to offer Priority Service
and eMLPP within the
same network, but not to
the same user.
This standardization work
in 3GPP is in the begining
and there are no final
conclusion on
requirements for Priority
Service.
V. PRIORITY SERVICE
SUPPORT BY ITU-T
STANDARDS
The main principle of study. On the international
Priority Service defined by level, work has started on
ITU-T, Ref.[4], is valid for amending Q.764,
ISUP. It is agreed and Q.1902.4 and Q.1950 to
there are activities within include handling of
the ITU-T to include the priority calls. The IEPS
I.255.4 Priority Service (International Emergency
with 5 levels of priority Preference Scheme) is
into the BICC protocol equivalent to the WPS
that exists in the Layered NS/EP indication.
Network, Ref.[5]. Fig.3 ITU-T ISUP does not
shows an example of support message priority
congestion in the Bearer handling as it is proposed
Network. in ANSI standard T1.111.
ANSI-ISUP has developed
a method to increase the
GSN-1 performance
GSN-2
in case of a
BICC congested signalling
CSF-G CSF-G
network, by having
specified dedicated
BCF-G BCF-R
priorities per message: e.g.
BCF-G
IAM has priority 0, ACM,
IAM CPG and REL have
ADD Req. (Prepare BNC, Priority)
priority 1 and ANM and
ADD Resp. (Prepare BNC, RLC have priority 2. This
Priority)
IAM is specified in T1.111.5,
Annex A. This is the
reason
ADD Req.why WPS solution
from Ref.BNC,
Establish Req. (Establish [2] could
Priority)not be
(Priority) simply applied in ITU-T.
ADD Resp.
Resource Congestion
Encountered VI. CONCLUSION
(Priority) NOTIFY Ind.
(BNC Release)
The great deal of attention
REL
will be given to Priority
Service more and more
Fig. 3. Example of because of the terrorist
Congestion in the Bearer attacks and natural
Network disasters. Special and
It should be noted that important calls will need
support of this service has to have a priority handling
already been introduced since there is a great
into B-ISUP (Q.2726.2) possibility of network
and DSS2 (Q.2959.2), congestion because of
where support of 5 values great number of
are specified. subscribers and increased
It has been agreed that one number of call attempts in
of the methods of priority specific situations.
call handling in congestion Customers will probably
situation is via access to request the Priority Service
resources specifically as basic function.
reserved for priority
calls/connections. The
methods of managing
these resources within a
node are implementation
specific. The other method
of ensuring preferential
treatment to priority calls
(a queuing function, pre-
emtion of lower priority
calls, re-routing the
call/connection to an
alternative destination) are
considered to be for further
 Completion (HPC)
Network Capability.
[4] ITU-T Recommendation
I.255.4 (07/1990):
Community of interest
supplementary services :
Priority service
[5] ITU-T Technical Report
TRQ.BICC.CS3 General
– Signalling
Requirements for the
Standardization activities Support of Narrowband
within 3GPP and ITU-T Services over Broadband
regarding the layered Transport Technologies,
architecture and WCDMA Capability Set 3,
support for priority November 2002.
services are still in
progress. There are
number of ongoing
activities. Some solutions
and proposals from Ref.[2]
should be taken into
account although the ANSI
system has some specific
characteristics.
WPS FOC did not consider
the layered architecture
and this article has
analyzed some additional
blocking points in addition
to monolithic GSM
system. There are number
of possibilities to improve
the progress of the call
with priority indication
which are indicated here
but the standardization
will offer the final and
aligned solution.

REFERENCES
[1] 3GPP TR 22.950 V.6.2.0
(2003-03), Technical
Specification
Group Services and
System Aspects; Priority
Service feasibility
study; (Release 6)
[2] Industry Requirement
(IR) Document,
Wireless Priority
Service (WPS)
Industry Requirements
for the Full Operating
Capability (FOC) for
GSM-Based Systems,
Issue 1.0, September
2002
[3] American National
Standard for
Telecommunications,
ANSI
T1.631-1993, Signalling
System No.7 (SS7) –
High Probability of