U MTS

UE UTRA N SGSN GGSN IP Serv er UE

CHAPTER 3 A pplic ation

Lay er SIP End-to-End Serv ice SIP SIP

Trans port UDP

UDP UDP
Lay er
Quality of Service IP IP IP

Sy s tem
UMTS Bearer Serv ic e External Bearer Serv ice
Lay er

rd
The 3 Generation system is envisioned as a service driven wireless communication Netw ork R adio Radio A c c es s Bearer CN Bearer
Lay er
system. The UMTS infrastructure introduces a wide variety of packet data service ranging Lay ers

Trans port R adio Bearer Iu Bearer Bac k bone

from real-time services, as voice over IP, to services with no real-time requirement such as Lay er
U TR A Phy s ic al
e-mail, web browsing, etc. F D D /TD D

However, since wireless networks are bandwidth-constrained and operate in error-prone

environments, mechanisms need to be put in place in order to manage the availability of Figure 3.1 – End-to-end QoS architecture

these services efficiently. With Quality of Service (QoS) UMTS provides facilities,
adequate bandwidth and quality for the end-user and their applications, contributing to
3.1 UMTS BEARER SERVICE
fulfil the end-to-end services requirements.
The UMTS Bearer Service (BS) consists of the Radio Access bearer (RAB) service and the
From the service perspective, the system architecture proposed by 3GPP is logically
Core Network bearer service (CN BS) [29] according to the functional architecture
divided into layers and bearer services as shown in Figure 3.1. At the first level, the
introduced/described in the previous chapter. Both services reflect the optimised way to
application level, end-to-end service allows communication among a range of networks and
set-up and support the Bearer Service over UMTS using the aforementioned control and
terminal equipment. This service uses the bearer services of the underlying networks,
data protocols.
UMTS Bearer Service (UMTS BS) and External Bearer Service.
The Radio Access Bearer service (RAB) provides confidential transport of signalling and
The UMTS bearer service contains mechanisms to allocate QoS over UMTS/3G networks
user data between UE and SGSN with the QoS adequate to the negotiated UMTS BS. This
consisting of a UTRAN and UMTS CN [27]. Since the UMTS network is typically
service is based on the characteristics of the radio interface and is maintained for a moving
attached to external network(s), the end-user QoS requirements must be handled at the
UE. The RAB itself consist of a Radio Bearer Service and and Iu-bearer service. The Radio
interface to other networks, too [28]. The IP external bearer service in turn consists of the
Link Control layer (RLC) between RNC and UE supports the Radio bearer service for both
necessary extension of the UMTS BS to do this.
user and control planes providing radio interface transport and error protection. The Iu
Chapter 2 presented some aspects of the UMTS protocol architecture at the network layer
bearer provides transport services between RNC and SGSN. The Core Network Bearer
level. However, in this chapter the UMTS Bearer Service is studied in more detail
Service provides transport services within the UMTS core network.
illustrating the QoS mechanisms required in each level and the services. Additional features
concerning end-to-end services will also be explained.

21 22
On the start of a packet-switched user application, a Bearer Service connection (PDP Once the RRC connection has been established, the UE sends the message ‘RRC Initial
context with specific Radio Access Bearer and Radio Bearer) needs to be established to direct transfer’ to RNC which in turn maps it in the SGSN into a RANAP message (RAN
enable transfer of data. However, before a RNC can control any requested bearer, it needs application part). After that, Authentication is performed and the Bearer Service setup is
to create a signalling connection between the UE and the CN. This connection transfers the triggered.
higher layer information between entities in the Non Access Stratum. Between the UE and
the UTRAN, RNC uses the Radio Resource Control (RRC) connection services in creation 3.1.2 UMTS Bearer Service Management
the Signalling Radio Bearer (SBR), and through the Iu interface a signalling bearer is then
In the Packet Switched sub-system domain the UMTS bearer service is realised by a
created.
packet data protocol (PDP) context. A PDP context describes the quality of the UMTS
In this section the functions and procedures required to establish the signalling and bearer
bearer service (BS) offered to the user for a specific application on a specific NSAPI
connections are described in detail as defined by 3GPP [30].
(Network Service Access Point Identifier). It also contains routing information that is used
to transfer the PDP PDUs between the UE and the GGSN. Consequently, every context
3.1.1 Signalling Connection Management
establishes an association between the UE and CN with a negotiated set of QoS attributes.
On power on, the UE establishes at most one radio control connection in order to access Those contexts are managed by the high-level Session Management (SM) entity and its
the UTRAN [21]. The set-up procedure, as shown in Figure 3.2, is always initiated by the activity depends on the lower level entities PMM (PS mobility management) and RRC
UE with the ‘RRC Connection Request’ message. Upon receiving this message, the RNC (radio resource control). The SM, located in the UE and GGSN, as a logical entity has two
transmits a ‘RRC Connection Set-up’ message to the UE and then the UE changes its RRC main states, INACTIVE and ACTIVE. In the INACTIVE state, the packet data transfer is
state from IDLE to CONNECTED. Finally the UE confirms the RRC connection not possible whereas in the ACTIVE state it is possible and also valid routing information
establishment by sending the ‘RRC Connection Set-up complete’ message indicating its is present and defined.
capabilities. With the Radio Resource Control (RRC) connection one or more Signalling The Session set-up starts with the UE sending an ‘Activate PDP Context Request’ message
Radio Bearers (SRBs) are created to transmit RRC signalling. to the SGSN indicating the NSAPI, the PDP Address if static, the Access Point Name and
the QoS requested. This request is carried in the RRC payload through UTRAN and to the
UE N ode B RNC
CN in a RANAP message. Upon receiving the message, the SGSN validates it, according
1 . R R C C o n n e c t io n R e q u e s t
RRC RRC to the subscription records. Subsequently, the SGSN starts the Radio Access Bearer
{ C C C H ( o n R A C H ) : R R C C o n n e c t io n R e q u e st }
allocation by sending a ‘RAB Assignment Request’ message over the Iu interface. When the
2 . R R C C o n n e c t io n S e t u p
RRC RRC RNC receives the message, the Radio Resource Management Admission Control algorithm
{ C C C H (o n F A C H ) : R R C C o n n e c t io n S e t u p }
checks if the Radio Bearer (RB) for this transaction can be established with the requested
3 . R R C C o n n e c t io n S e t u p C o m p le t e QoS parameters. If so, the RB is established with the given parameters. Depending on the
RRC RRC
{ D C C H (o n D C H ) : R R C C o n n e c t io n S e t u p C o m p le t e } bit rate associated with the service the radio bearers may be set-up on RACH/FACH
UE N ode B RNC (Random access channel/forward access channel) or DCH (dedicated channel). As soon as
the UE is able to receive data from the new RB it acknowledges this by sending the ‘Radio
Figure 3.2 - RRC Connection

23 24
bearer set-up complete’ message to the RNC, which in turn maps it to the CN with a ‘RAB 3.2 UMTS PROCEDURES
assignment response’ message. After that the SGSN informs the GGSN about the
downgraded QoS attributes with the ‘Create PDP context request’ message. Finally, once In addition to the establishment of the UMTS bearer service within the PDP context
the RAB is established, the CN confirms the packet session establishment with the activation procedure, UMTS also supports others QoS management functions in order to
‘Activate PDP context accept’ message. The procedure is shown in Figure 3.3 [30]. control the established bearers. Two main QoS management groups can be differentiated,
UE N ode B RN C SGSN GGSN Mobility Management and Radio Resource Management [26, 30].
1 . D ir e c t T ra n sfe r: A c tiv a te P D P C o n te x t R e q u e s t
SM SM

RAB
2 . R A B A s s ignm e nt R e q ue s t 3.2.1 Mobility Management
RAN AP RAN AP
3 . R a d io L ink S e tup
RB N BAP N BAP
Unlike fixed networks, a mobile network such as the UMTS network requires a set of
4 . R e s p o ns e
N BAP N BAP functions and procedures to manage the subscriber location and mobility together with its
5 . A L C A P Iub D a ta T ra ns p o rt B e a re r S e tup
identities and security aspects. Those aspects affect the UMTS bearer service and therefore
6 . R a d io B e a re r S e tup
RRC
{D C C H : R a d io B e a re r S e tup }
RRC need to be considered in this approach. In order to track the UE, the cells (i.e. NodeBs) in
RRC
7 . R a d io B e a re r S e tup C o m p le te
RRC
the UMTS service area are partitioned into several groups as shown in Figure 3.4.
8 . R A B A s s ignm e nt R e s p o ns e
RAN AP RAN AP
LA
9 . C re a te P D P C o nte xt R e q ue s t
RA
G TP GTP
URA URA
Cell Cell Cell Cell
1 0 . R e s p o ns e
GTP GTP Cell
Cell
Cell
Cell Cell Cell Cell
1 1 . D ir e c t T r a n s f e r : A c tiva te P D P C o nte xt
SM SM

RA
URA URA
UE N ode B RN C SGSN GGSN Cell Cell Cell
Cell
Cell Cell

Figure 3.3 - PDP Context Activation Cell Cell Cell Cell

Cell

This procedure can also be initiated by the GGSN, through a ‘Network Initiated PDP
Context Activation’ procedure. On Mobile Terminated sessions, when GGSN receives a Figure 3.4 - MM logical entities

PDP PDU it checks if a PDP context is established for that PDP address. If no PDP context
In the CS domain one or more cells under control of a VLR (Visitor Location Register) are
has been established, the GGSN triggers a ‘PDP Context Activation’ message by paging the
mapped into a Local Area (LA) in which a mobile will be registered. Similarly, in the PS
UE to determine if it is reachable.
domain, the location registration is based on Routing Areas (RA). However, a RA is
Once a primary PDP context has been established for a given PDP address, a secondary
typically a subset of an LA and cannot belong to two or more LAs. The VLR tracks the LA
PDP context can be activated. Such context uses the same PDP address and other
of an UE whereas the RA is controlled by the SGSN. In addition to this, the cells in an RA
information associated with the already active PDP context, but may have a different QoS
profile.

25 26
 are further partitioned into UTRAN Registration Areas (URAs). The URA and the cell of a • PMM-IDLE. The UE is attached to the GPRS CN and therefore, both UE and SGSN
UE are tracked by the UTRAN. have established MM contexts. However, a signalling connection (RRC) is not established
This four-level logical hierarchy acts as a map for RNC and SGSN to control the location between both and the UE location is known only by the CN (with accuracy of RA). In this
of the UE with the Mobility Management procedures. state, the UE is able to receive system information (SGSN paging) and cell broadcast
messages. The transition to the PMM-CONNECTED state occurs when the service request
3.2.1.1 CN Mobility Management: RA level
procedure is executed to establish the PS signalling connection between UE and SGSN.
The MM protocol state machine in both SGSN and UE perform the mobility management
• PMM-CONNECTED. PDUs can only be delivered in this state as the PS signalling
activities for the UE on a RA level. For the UMTS PS service domain, the states in the
connection (RRC connection) is established depending on the type of traffic to be
machine are PMM-DETACHED, PMM-IDLE and PMM-CONNECTED. The MM states
transmitted. The SGSN tracks the UE with accuracy of the RA level and the serving RNC
are stored in the MM context maintained by the UE and SGSN. Figure 3.5 illustrates the
is responsible for cell-level tracking. The serving RNC relocation procedure is executed in
MM state diagrammes and the transitions among them triggered by the specific Location
this state.
Management procedure(s). Details of the Location Management procedures are presented
further on in this section. 3.2.1.2 UTRAN Mobility Management: Cell & URA level
The UTRAN tracking is triggered by the establishment of the RRC connection. This
MS MM States 3G -SGSN MM States
connection creates specific Signalling Radio Bearers (SRBs) and traffic dependent Radio
PMM
DE TACHED
PMM
DE TACHE D
Bearers. In the CONNECTED mode, the UE can have different states depending on the

PS Detach
D etach,
PS Attach Reject, PS Detach
Detach,
PS Attach Reject,
type of connection it has to the UTRAN as well as the velocity of the UE as illustrates
PS Attach R AU Reject PS Attach RAU Reject
Figure 3.6.
PS Signalling PS Signalling
PM M -IDLE Connection Release PM M - Connection Release PM M -
PM M -IDLE
SM-AC T IVE or
CONNECTED CONNECTED Connected Mode
SM-ACT IVE or SM-ACT IVE or SM-ACT IVE or
INACT IVE PS Signalling
Connection Establish INACT IVE INACT IVE PS Signalling INACT IVE Cell DCH
Connection Establish
Idle
Cell PCH
Serving RNC Mode
relocation
Cell FACH
Figure 3.5 -PMM States URA PCH

The MM states are as follows: Figure 3.6 - UE RRC States in connected mode

• PMM-DETACHED. The UE is not known, as it is not attached to the core network,

When the connection is established, the state moves from the IDLE state to Cell DCH or
therefore it is not reachable by the network. In this state the MS performs an attach
Cell FACH connected mode where the UE location is known with accuracy of a cell by the
procedure. As the attach procedure establishes the MM context and the PS signalling, it
UTRAN.
trigger the change to PMM-CONNECTED mode. In this state the SM state is always
INACTIVE.

27 28
• In the CELL DCH state the UTRAN has allocated dedicated resources for the 3.2.1.3 PMM Procedures
connection, a Dedicated Packet Data Channel (DPDCH) and Dedicated Packet Control
The Mobility Management procedures emphasizing PS-based services (PMM) can be
Channel (DPCCH). Depending on the radio connection, different RRC procedures are
grouped into Attach, Location Management and Service Request. Detailed explanation is
executed in this state. For services with high QoS class handovers are performed whereas
given in TS 23.060 [30] and TS 24.008 [26]. Security [31] and System Interchange are not
they may not be completed for the lower QoS class. The UE processes measurement
discussed here, as they are not relevant for the current investigation.
control information received from the RNC. In this state the UE is known by its serving
RNC on a cell or active set level. A. ATTACH

• In the CELL FACH state no dedicated physical channel is allocated for the UE, but The UE performs a GPRS Attach to the SGSN in order to obtain access to the GPRS

RACH (Random access channel) and FACH (Forward access channel) common channels services. With the Packet IMSI Attach the valid routing information for the packet switched

are used instead for transmitting both signalling and user data. In this state the UE performs connection is created in every node involving the packet switched connections, which

cell reselection. After a Cell Update message is sent, so that the RNC knows the UE’s causes MM context to be established at the UE and the SGSN. During an attach, the UE is

location on a cell level. authenticated and the HLR is updated with its location information. The main procedures

Once the UE is in the Cell DCH or Cell FACH state but no data is transferred, the UE state executed during the UMTS GPRS Attach are illustrated in Figure 3.7.

will change to Cell PCH or URA PCH state after the inactivity timers expire. Cell and The UE first requests a GPRS Attach procedure. As the UE is unknown to the SGSN, the

URA PCH states are very similar. However in the URA PCH, the UE execute URA SGSN requests its Identity (IMSI). Upon receipt of UE’s identity the Authentication and

updates, avoiding periodical Cell updates after each cell reselection. If the UE mobility is Equipment check procedures are executed. Then, the SGSN sends an ‘Update Location’

high its state also changes to URA PCH. message to the HLR providing the subscriber’s IMSI and the new SGSN address. The HLR

• In the Cell PCH state, the UE’s location is still known on a cell level to the SRNC, but it sends the GPRS Subscription Data in an ‘Insert Subscriber Data’ message to the SGSN.

can be reached only via the paging channel (PCH) and listens to the system information on After that, the new SGSN validates the UE's presence in the RA. If all checks are

the broadcast channel. If the UE performs a cell reselection, it moves automatically to the successful the SGSN constructs an MM context for the MS and returns an ‘Insert

Cell FACH state to execute the Cell Update procedure, after which it re-enters the Cell Subscriber Data Ack’ (IMSI) message to the HLR. Finally, the HLR acknowledges the

PCH if no other activity is triggered. ‘Update Location’ message to the SGSN after cancelling the old MM context and insertion

• In URA PCH state, the location of the UE is known only at the URA level and hence in of a new one are finished. The SGSN sends an Attach Accept to the MS and includes a new

order to obtain the cell level location accuracy the UE is paged by the UTRAN/RNC (Iur) P-TMSI (Temporary Mobile Subscriber Identity).

on a BCH (Broadcast channel). If the UE performs a cell reselection, the UE checks if the
new cell belongs to the same URA. Only if the URA has change, the UE will enter the Cell
FACH and execute the Cell procedure.

29 30
UE RNC SGSN HLR B. LOCATION MANAGEMENT
1. P S A ttach R eq Tracking of the UE’s location is managed based on the four-levels network structure shown
RRC RRC
2 . I n it ia l U E M e ss a g e in Figure 3.4. Location Update/Management procedures are triggered either because the
RANAP RANAP
3 . I d e n tit y R e q u e st
UE detects a change on its location or because the UE is executing a periodic report to the
PM M PM M

3 . I d e n t ity R e sp o n se
network [32]. Periodic reports are controlled by timers maintained in both UE and SGSN or
PM M PM M
4 . S e n d A u th I n fo RNC. Consequently when a timer expires, the UE performs the respective periodic update.
M AP MAP
4. A ck A PS attached UE, when crossing a cell boundary, performs update procedures for RA,
M AP M AP
5 . A u t h e n tic a t io n R e q u e s t
URA and Cell depending on its PMM and RRC states as stated earlier. The procedures
PM M PM M
5 . A u t h e n tic a t io n R e sp o n s e
considered in this study are the following ones.
PM M PM M
6 . C heck IM E I C. CELL/URA UPDATE
MAP MAP
6. Ack
M AP
Whenever a mobile terminal crosses a cell boundary, a cell update is triggered if the mobile
M AP
7 . S e c u rit y M o d e C o m m a n d is not engaged in any active data session or call. In addition, if the mobile is also crossing
RRC R R C /R A N A P RANAP
SRNC boundaries, the cell update request message triggers SRNC relocation as shown in
7 . S e c u r it y M o d e C o m p le t e
RRC R R C /R A N A P RANAP Figure 3.8. However, a mobile in URA_PCH RRC state, performs URA updates to track
8 . U p d a t e L o c a tio n
MAP M AP the location of the mobile when the mobile crosses an URA boundary. Both update flows
9 . I n se rt S u b sc r ib e r D a ta are the same except that “URA update” and “URA Update Confirm” are the messages
MAP M AP
9. A ck exchanged.
M AP MAP
1 0 . U p d a t e L o c a t io n A c k
MAP M AP UE SRNC

11. A ttach A ccept 1 . C e ll U p d a te

PM M PM M RRC RRC
{ C C C H : C e ll U p d a te }

1 2 . A t t a c h C o m p le te A llo c a te
PM M PM M C -R N T I

SGSN HLR 2 . C e ll U p d a te C o n firm

UE RNC RRC RRC
{ D C C H : C e ll U p d a te C o n firm }

Figure 3.7 – Attach Procedure UE SRN C

Figure 3.8 - Cell Update Procedure

31 32
D. SRNC RELOCATION Figure 3.10 illustrates the Inter-SGSN relocation. As we can see the flow is similar to the
When a mobile terminal crosses a RNC boundary, in other words crosses cells that belong additional messages exchanged between the old and new SGSN. After the Inter-SGSN
to different RNCs, a Serving RNC relocation procedure is triggered. If the new SRNC is SRNC relocation the UE performs the RA update.
connected to the same SGSN as the old SRNC, an Intra-SGSN SRNC relocation is Target New
UE Source Old GGSN
RNC RNC SGSN SGSN
performed otherwise an Inter-SGSN SRNC procedure followed by an RA update is
1. Decision to perform
undertaken. Both types of SRNC procedures are combined with a handover procedure if the SRNS relocation

UE is in Cell DCH RRC state. Figure 3.9 illustrates the Intra-SGSN SRN procedure; steps 2. Relocation Required
RANAP RANAP
5-8 and 13 are only present when the UE in Cell DCH requires handover. 3. Forward Relocation Request
GTP GTP

4. Relocation Request
UE N ode B N o de B RNC RNC SG SN RANAP RANAP
S ou rce T arg et S ou rce T a rg et
Establishment of Radio Access Bearers
1. D ecision to in itia te S R N S
relocation
4. Relocation Request Acknowledge
2 . Up lin k S ig n allin g
T r an sfer In d ication
RANAP RANAP
RN SAP RNSA P
5. Forward Relocation Rsp
3 . R elocation R equ ired
GTP GTP
RA N AP RA NA P
4. R elocation R eq u est 6. Relocation Command
RA NA P RA NA P RANAP RANAP
5. R a dio L in k S etu p R eq u est
N BAP N BA P 7. Forwarding of data
6 . R ad io L in k S etup R esp on se RNSAP RNSAP
N BA P N BA P
8. Relocation Commit
7. A L C A P Iu b D ata T r an sp ort B ear er S etup
RNSAP RNSAP
8. D ow n lin k a n d up lin k syn ch r on isa tion
N BA P N BA P 9. Relocation Detect
9 . R elocation R eq u est A ck RANAP RANAP
RA N AP RA NA P 11. Update PDP Context Request
10. RAN Mobility Information
10 . R eloca tion C om m a n d RRC RRC GTP GTP
RA N AP RA NA P
10. Confirm 11. Response
11 . R eloca tion C om m it RRC RRC GTP
RN SAP RNSAP GTP
1 2 . R elocation D etect
RA NA P RA N AP 12. Relocation Complete
1 3. R a dio Lin k F a ilu re In dication RANAP RANAP
NBA P NBAP
12. Forward Relocation Complete
1 4. R N T I R eallocation
RRC RRC GTP GTP
15 . R N T I R ealloca tion C om p lete
12. Ack
RRC RRC GTP GTP
1 6. R elocation C om p lete
RA NA P RAN A P
13. Iu Release Command
RA N AP
1 7 . Iu R elease C om m an d
RA NA P
RANAP RANAP
13. Complete
UE N ode B N ode B RN C RNC SG S N
S ou rce T arget S ou rce T a rg et
RANAP RANAP

UE Source Target Old New GGSN

RNC RNC SGSN SGSN
Figure 3.9 - Intra-SGSN SRNC relocation

Figure 3.10 - Inter SGSN SRNC relocation procedure

33 34
E. BRANCH ADDITION F. ROUTING AREA UPDATE (RA)
If a mobile is in an active session with an active dedicated RRC Connection (Cell DCH) When a UE moves to a cell which belongs to a new Routing Area, the UE changes its state
and crosses cell boundaries, the mobile needs to add a new radio link to its active set. This to PMM-IDLE and a Routing area update is triggered as illustrated in Figure 3.12.
triggers a branch addition procedure for all sessions that the mobile is engaged in. Figure Additionally, if the new RA belongs to a new SGSN (inter-SGSN), a ‘GTP context
3.11 shows the message sequence chart detailing the branch addition procedure. transfer’ message and ‘PDP context modification’ are required.

UE N ode B RNC Node B RNC SGSN

MS

D ecisio n to setup 1-3: RRC Connection Establishment

n ew R L

RRC 4: Routeing Area Update Request RRC/RANAP RANAP

NBAP 1 . R ad io L in k S etu p R eq u est
NBAP

5: Security Mode Command

S tart R X
RANAP RANAP
2 . R ad io L in k Se tup R esp o n se
NBAP NBAP 6: Security Mode Command
RRC RRC
7: Security Mode Complete
3 . A L C A P Iub B earer Se tup RRC RRC
8: Sec Mode Compl
RANAP RANAP
4 . D o w nlink Synch ro nisatio n
D C H -F P D C H -F P 9: Routeing Area Update Accept
RRC RRC/RANAP RANAP
5 . U p link S ynch ro nisa tio n 10: Routeing Area Update Complete
D C H -F P D C H -F P RRC RRC/RANAP RANAP

S tart T X
11-12: RRC Connection Release
6 . A ctive S et U p d ate
RRC RRC MS Node B RNC SGSN
{ D C C H : A ctive S et U p d ate}

7 . A ctiv e S et U p d a te C o m p lete Figure 3.12 - RA Update procedure

RRC RRC
{D C C H : A ctiv e S et U p d ate C o m p lete}

UE N ode B RNC

Figure 3.11 - Branch addition Procedure

35 36
G. SERVICE REQUEST 3.2.2 Radio Resource Control & Management
The UE uses the Service Request procedure in order to establish a secure connection with
the SGSN and transfer signalling messages (Activate PDP Context Request) or user data Since the RRC layer handles the major part of the control signalling between the UE and

through an active PDP context. UTRAN by controlling and managing the RBs, it has numerous functions to perform in
The UE sends a Service Request message to the SGSN. Then, after performing the security addition to the signalling establishment mentioned above.

functions, the UE triggers the resource reservation to assign RAB or the PDP Context 3.2.2.1 Radio Resource Management
Activation procedure depending on whether there is an active PDP context or not. Figure
Radio Resource Management (RRM) is a collection of procedures UTRAN uses for
3.13 shows the messages flow for the case where there is an active PDP context.
management of the air interface resources. These procedures handle, for instance, power
UE RNC SGSN HLR GGSN control, different types of handovers, system load and admission control. Power control is
1. RRC Connection Request
needed to keep the interference level at a minimum in the air interface and to provide the
1. RRC Connection Setup
required QoS whereas handovers are needed in cellular systems to handle mobility of users.
2. Service Request In addition, in third generation networks, other RRM algorithms such as admission control,
3. Security Functions load control and packet scheduling, are required to guarantee the QoS and to maximize the

4. Service Accept
system throughput with a mix of different bit rates, service and quality requirements. A
4. RAB Assignment Request more detailed description can be found in [17].
5. RB Setup
3.2.2.2 Radio Resource Control Functions
6. RB Setup Complete
6. RAB Assignment Response
In addition to managing radio resources, UTRAN control functionality takes care of
establishment and maintenance of the radio link between UE and UTRAN.
7. SGSN-Initiated PDP Context Modification
A. SYSTEM INFORMATION BROADCASTING & PAGING
8. Uplink PDU
System information is used to maintain both the radio connections and also to control the
UE RNC SGSN HLR GGSN
overall operation of the UTRAN. The RNC broadcasts to the UE to assist the UTRAN
Figure 3.13 - Service Request procedure (active PDP context) controlling functions, such as measurements criteria, paging, assistance date for positioning
purposes etc. This system information can be received by the UE both in idle and all
If the session is initiated by the network (NI PDP Activation) or the SGSN receives a
connected states. Figure 3.14 shows as an example the broadcast of paging information
downlink packet for an UE in PMM-IDLE, the Service request is triggered by the paging
depending on the UE RRC mode (RRC Idle mode, RRC URA or Cell PCH mode and Cell
request procedure.
FACH or DCH RRC state).

37 38
 • For Case C:
UE RNC RNC MSC
NODE B An RRC Connection exists and the UE is in Cell_DCH or Cell_FACH state, i.e. DCCH
1. Paging
A) UE is in IDLE mode RANAP RANAP exists. In this case, the RNC sends an RRC Paging Type 2 message on the DCCH.
2. PCCH: Paging Type I
RRC RRC
B. INITIAL ACCESS AND SIGNALLING CONNECTION MANAGEMENT
When the UE enters the idle mode by turning on its power, it attempts to make contact with

1. Paging
the UTRAN. The UE looks for a suitable cell in the UTRAN and chooses the cell to
B) UE is in URA connected mode RANAP
or in Cell_PCH RRC state RANAP provide available services, and tunes to its control channel. This process is known as
2. Paging Request
RNSAP RNSAP ’camping on a cell’. Then the UE obtains the necessary information (by means of
3. PCCH: Paging Type I
RRC RRC broadcasting) to capture the NodeB controlled by the corresponding RNC. Once obtained,
3. PCCH: Paging Type I the UE can establish the signalling connection, as explained before.
RRC RRC
Timers are used to control the time allowed for a UE to execute a RRC connection re-
establishment in case of a radio link failure.
C) UE is in cell connected mode 1. Paging
with existing DCCH RANAP
RANAP

2. DCCH: Paging Type 2

3.3 UMTS QOS CLASSES
RRC RRC

UE NODE B RNC RNC MSC The UMTS Bearer Services are categorized into four traffic classes: conversational,
streaming, interactive and background as defined in TS 23.107 [27]. The main
Figure 3.14 - Paging Procedure
distinguishing factor between them is the delay sensitiveness attribute as it is most directly
The first message is common for all three cases where the SGSN CN entity sends a
related to the connection quality. Nonetheless other factors such as the guaranteed bit rate
‘RANAP Paging’ message to the RNCs serving the UE’s Routing Area.
(bandwidth) and nature of traffic (symmetric/asymmetric) among others have been defined
• For Case A: in order to enable more enhanced service differentiation for UMTS bearers.
The UE is in idle mode, and the RNC broadcasts an RRC Paging Type 1 message on an Conversational and Streaming classes are intended mainly to carry real-time traffic flows as
appropriate paging occasion on the PCCH. both preserve time relation between information elements within the stream. However, the
• For Case B: conversational class has stricter and lower delay requirements, which are defined by the
An RRC connection exists and the UE is in URA_PCH or CELL_PCH RRC state. A URA human perception of video and audio conversations. On the other hand, Interactive class
may be controlled by different RNCs and the UE might be camping on a cell controlled by and Background are principally used by traditional Internet applications such as WWW, E-
a different RNC so the RNC sends a RNSAP Paging Request to the concerned RNCs. The mail, Telnet, FTP and Network News. Due to the looser delay requirements, compared to
corresponding RNCs then broadcast an RRC Paging Type 1 message as in Case A but only conversational and streaming classes, reduced bit error rates are achieved through channel
for cells belonging to the URA if the UE is in URA_PCH state, or only in the known cell if coding and retransmission. The main difference between interactive and background class
the UE is in CELL_PCH state is the traffic priority in the scheduler, which assigns the transmission resources.

39 40
Table 3.1 presents the QoS profile parameters for each class. Rate (AMR) codec, which supports eight source rates ranging form 4.75 kbps to 12.2 kbps
[35]. Those bit rates are controlled by the radio access network making an optimum use of
Table 3.1 - Traffic classes QoS Attributes
the battery power, bandwidth available and also provides adaptation to changing radio
Traffic class Conversational Streaming Interactive Background
Maximum bit rate (kbps) < 2 048 < 2 048 – overhead channel conditions through adapting source and channel codec rates for voice. To facilitate
Guaranteed bit rate (kbps) < 2 048 interoperability with existing cellular networks, some of the modes are compatible with 2G
Max. SDU size (octets) ≤1 500 or 1 502 networks. For instance, the 12.2 kbps stream corresponds to the GSM EFR (Enhanced full
-2 -2 -3 -3 -4 -6 -3 -5 -8
Residual BER 5*10 , 10 , 5*10 , 10 , 10 , 10 4*10 , 10 , 6*10 rate) codec.
-2 -3 -3 -1 -2 -3
10 , 7*10 , 10 , 10 , 10 , 7*10 , -3 -4 -6
SDU error ratio -4 -5 -3 -4 -5 10 , 10 , 10
10 , 10 10 , 10 , 10
3.3.1.2 PS Speech Services
Transfer delay max value (ms) 100 250
A voice service transmitted over the Packet Switch domain, commonly known as Voice
By being able to differentiate traffic flows in the network, four application-related service over IP, is feasible since UMTS Release 6 provides full Call Control PS capability by using
classes can be defined within UMTS accordingly. In this section some services with the IETF defined text based protocol, Session Initiation Protocol (SIP). The control of the
different traffic characteristics relevant to the current investigation are highlighted. Their call relates to inviting and synchronising the various entities involved in the session [36,
performance requirements established in the earlier UMTS specifications are also presented 37]. It also enables the participants to describe and share information about the
based on the Rel99 3GPP 25.853 [33] and 22.105 [34] standards. characteristics of the terminal equipment and the speech capabilities using the Session
Description Protocol (SDP). SIP call control signalling over the GPRS network is carried
3.3.1 Conversational Class Applications
through a PDP context established for this purpose. As the speech path requires a separate

UMTS’ most common service using the conversational QoS class is the speech service. PDP context to the SIP signalling, a user establishes a secondary PDP context to carry

The speech service in UMTS can be transmitted using the circuit or packet switched voice data once the call setup is finished. In this approach the speech service is carried like

domain depending on the UMTS specification stage it refers to. Earlier UMTS packet switched data from the terminal through the network to the Media Gateway (MGW).

specifications (R99) implemented the speech services using the CS domain, however later
3.3.2 Streaming Class Applications
versions provide full PS call control capabilities required for voice quality support. As both
approaches are relevant to this investigation, a brief call/session control description for both This application class is one of the newcomers in data communications, raising a number of
is given in this section. new requirements in both telecommunication and data communication systems. Multimedia
3.3.1.1 CS Speech Service streaming is a technology that allows compressed live or pre-recorded video and audio

Voice service in earlier UMTS specifications use the CS domain inherited from GSM, content to be delivered to the user in real-time. With streaming, the transfer of data is

however the Call Control (CC) is enhanced to encompass the new radio resource control processed by the user terminal as a steady and continuous stream, being mainly

protocol RRC and UTRAN based mobility as defined in [24.008][26]. unidirectional. The main characteristic is that the time relations (variation) between

A user’s speech is digitally sampled by the mobile equipment and then coded for information entities (i.e. samples, packets) within a flow must be preserved, although it

transmission. The speech coding used in terminals and the UTRAN is the Adaptive Multi- does not have any requirements on low transfer delay.

41 42
3.3.3 Interactive Class Applications 0 to 150 ms: preferred range
<30ms, user does not notice any delay
Interactive traffic is one of the classical data communication modes that at an overall level <100ms, user does not notice delay if echo cancellation is provided and
are characterized by the request response pattern of the end-user. At the message there are no distortions on the link
destination there is an entity expecting the message (response) within a certain time. Round
150 to 400 ms: acceptable range (but with increasing degradation)
trip delay time is therefore one of the key attributes. Another characteristic is that the
content of the packets shall be transparently transferred. > 400 ms: unacceptable range

The human ear is highly intolerant of short-term delay variation (jitter) it is therefore
3.3.4 Background Class Applications paramount that delay variation is maintained as low as possible. A lower limit of 1 ms is
suggested as a target. The human ear, on the other hand, is tolerant to certain amount of
Data traffic generated by applications such as server-to-server e-mail, SMS and
speech signal distortion and therefore requirements for information loss are less tight. It has
downloading of database data can be delivered in the background since such applications
been suggested in studies that acceptable performance is typically obtained with frame
do not require immediate action. Background traffic is one of the classical data
erasure rates (FER) of up to 3 %.
communication schemes supporting non-real time services without any special requirement
A connection for a conversation normally requires the allocation of symmetrical
on delay. The scheme is thus delivery time insensitive. Another characteristic is that the
communication resources, with the average holding time of a call being in the region of 2
content of the packets must be transparently transferred.
minutes.
3.3.5 QoS Performance Requirements for end user applications 3.3.5.2 Interactive Services Requirements
Different data application services are examined such as web browsing and e-mail
This section outlines the expected QoS requirements of typical end user application, set as
application services. Although there may be some exceptions, a prime requirement for any
initial UMTS requirements by 3GPP in specification 22.105 Release 99 [34]. These
data transfer application is to guarantee essentially zero loss of information. At the same
requirements represent end-to-end performance summarising the major groups of
time, delay variation is not applicable. The different applications therefore tend to
applications in terms of QoS requirement.
distinguish themselves on the basis of the delay that can be tolerated by the end-user from
3.3.5.1 Conversational/ Real Time Services Requirements the time the source content is requested until it is presented to the user.
Audio transfer delay requirements depend on the level of interactivity of the end users. To
A. WEB BROWSING
preclude difficulties related to the dynamics of voice communications, ITU-T
This category refers to retrieving and viewing the HTML component of a Web page and
Recommendation G.114 recommends the following general limits for one-way
other components such as images or audio/video clips. From the user point of view, the
transmission time:
main performance factor is how fast a page appears after it has been requested. A value of
2-4 seconds per page is proposed, however improvement on these figures to a target figure
of 0.5 seconds would be desirable.

43 44
 B. E-mail
E-mail is generally a store and forward service, which in principle can tolerate delays of
several minutes or even hours. However, it is important to differentiate between
communications between the user and the local e-mail server and server-to-server transfer.
When the user communicates with the local mail server, there is an expectation that the
mail will be transferred quite rapidly, although not necessarily instantaneously. Consistent
with the research findings on delay tolerance for Web-browsing, a requirement of 2-4
seconds is proposed.

3.3.5.3 Streaming Service Requirements

The resulting overall requirements for this communication scheme is to support streaming
real time services having unidirectional data flows with continuous utilisation. The delay
requirements are relaxed, as there is no conversational element involved (one-way
communication), even more so than for interactive services.

3.3.5.4 Background Service Requirements

In principle, according to the above mention service characteristics, the only requirement
for applications in this category is that information should be delivered to the user
essentially error free. However, there is some delay constraint, since data is effectively
useless if it is received too late for any practical purpose.

A. SMS OR OTHER LOW PRIORITY TRANSACTION SERVICES

30 seconds is proposed as an acceptable delivery delay value for the SMS case.

B. E-MAIL (SERVER-TO-SERVER)
This category is included for completeness, since as mentioned earlier, the prime interest in
email is in the access time. There is a wide spread in user expectation, with a median value
of several hours.

45