Vous êtes sur la page 1sur 86

The UMTS Architecture

Understanding UMTS
Sec2 ©Informa Telecoms
The UMTS Architecture

The UMTS Architecture


1 UMTS ARCHITECTURE – THE REQUIREMENTS
1.1 Aims of the UMTS Architecture 1
1.2 Key new features in UMTS vs. GSM/GPRS 3
1.3 The Two Modes of W-CDMA Access 5
1.4 Elements & Domains in a UMTS network 7
2 THE USER DOMAIN (USIM + ME DOMAINS) 9
3 THE ACCESS NETWORK
3.1 The Access Domain and Interfaces 11
3.2 Requirements of the UTRAN 13
3.3 Further UTRAN features 17
3.4 UTRAN Architecture – General 17
3.5 The Node B 19
3.6 The RNC 21
3.7 RNC Terminology 23
3.8 Functions of the RNC 25
3.8.1 Controlling RNC Functions 25
3.8.2 Serving RNC Functions 25
3.8.3 Drift RNC Functions 25
3.9 Further UTRAN features 27
3.10 Handovers 29
3.10.1 Softer Handover 29
3.10.2 Soft Handover 31
3.11 Functions Of The UTRAN Protocols 33
4 THE UTRAN TRANSPORT NETWORK
4.1 Requirements Of The Transport Network 35
4.2 The Options 35
4.3 ATM Operation 37
4.4 The ATM Cell 39
4.5 ATM and Quality Of Service 41
5 THE CORE NETWORK
5.1 The Core Network Domain 43
5.2 Specific Entities in the UMTS Release ’99 Core
Network Architecture 45
5.3 The Circuit Switched Domain & GSM Core
Network Elements 47
5.4 The GSM Location Registers 49
5.5 The Packet-Switched Domain & GPRS Core
Network Elements 51

Understanding UMTS
©Informa Telecoms
The UMTS Architecture

5.6 Operation in the Core Network CS Domain 53


5.6.1 User and Control Information in the CS Domain 53
5.6.2 Signalling in the CS Domain – SS7 Overview 55
5.7 Operation in the Core Network PS Domain 57
5.7.1 User and Control Information in the PS Domain 57
5.8 OTHER NETWORK ENTITIES 59
5.8.1 Some other entities for specific services 59
6 IN/CAMEL IN UMTS
6.1 Intelligent Networks 61
6.2 CAMEL 63
7 CHARGING 65
8 CORE NETWORK TRANSPORT 67
9 MOBILE IP
9.1 Mobile IP: Basics 69
9.2 Mobile IPv4 vs. IPv6 71
10 RELEASE 4
10.1 Release 4 – Control & Data Separation
in the CS domain 73
10.2 The IP Multimedia Subsystem 75
10.3 New Domain Concept in Release 4 and Beyond 77
11 NETWORK EVOLUTION
11.1 3GPP Release ’00/Release 4 79
ANNEX 1 DOMAINS AND STRATA
a.1 UMTS Domains 81

Understanding UMTS
©Informa Telecoms
The UMTS Architecture

1. UMTS ARCHITECTURE – THE REQUIREMENTS

1.1 Aims of the UMTS Architecture

The fundamental difference between GSM/GPRS and UMTS is in the need for the
latter to support high bit rate bearer services, plus the notion of negotiated QoS and
traffic characteristics. In particular, UMTS needs to support bursty and asymmetric
traffic in an efficient way, and to allow support of single and multimedia N-ISDN
applications and single & multimedia IP applications.

However, no one knows what precise future service requirements will be. Therefore it
is essential that the UMTS system is designed to be as flexible as possible. For this
reason, a modular approach has been followed, with network nodes defined that
implement some specific functionality, and open interfaces defined between such
nodes.

A modular approach also increases the chances of being able to implement future
seamless roaming between the various IMT2000 family standards.

In order to ensure that UMTS is implemented as quickly as possible, it also became


obvious that its design needed to take account of the cost for operators.

The optimisation of the signalling load as well as reduction in the overall transmission
capacity are critical cost factors for operators, and so the aim is for an architecture
which will minimise signalling traffic and optimise transmission infrastructure. The
architecture also needs to protect existing investments which operators have, and
re-use as many elements of these as possible. In particular, the first release of UMTS
(UMTS Release ’99) builds directly upon an evolved GSM (GSM Phase 2+) network,
including the addition of GPRS.

Of course, different phases of release of UMTS will need to be compatible with each
other.

Understanding UMTS
1 ©Informa Telecoms
• Flexibility

• IMT2000 interworking

• Minimise signalling

• Optimise transmission

• Protect existing investments

• Enable evolution

Modular approach, building on evolved GSM

Fig. 1 – Aims of the UMTS Architecture

©Informa Telecoms 2
The UMTS Architecture

1.2 Key new features in UMTS vs. GSM/GPRS

The UMTS Core network in Release ’99 is based on the GSM/GPRS network. Most
of the individual elements are re-used, although they require extensions (e.g. MSC,
VLR etc.), but the UTRAN elements are completely new. UMTS core networks must
be able to interoperate both this new UTRAN and the existing GSM BSS access
network.

In order to support more data intensive services, operators will need to upgrade
capacity throughout their networks in order to cope with the expected increase in
traffic, and use transport protocols which are more efficiently suited to data and
packet transport. Thus, in UMTS Release ’99, ATM is specified as the transport
mechanism in the new interfaces in the radio access and between radio access and
core network.

A new, standard default speech codec (adaptive multi-rate) is also standardised for
UMTS, and supports tandem free operation both to lower transmission costs and to
improve speech quality.

Among other key features provided by UMTS networks but not previously
standardised within GSM:

• the enabling of set-up, renegotiation and clearing of connections (both circuit-


switched calls & packet-switched sessions), with a range of performance
characteristics. The connections can also vary during their lifetime. This provides
for flexible, multimedia services, in which media elements may be added or
removed dynamically during the call

• support for a range of traffic and performance for connectionless (multicast,


broadcast, unicast) traffic, defined using bearer services. Once established, bearers
do not prevent the set-up of new bearers, again permitting services to be flexible

• support for the Virtual Home Environment (VHE), provided through toolkits

• the generation of additional charging records, for example based on number, call
duration, traffic, QoS and so on, in order to provide operators with the capability to
offer new pricing models. These new charging methods are also set up in such a
way as to provide support for on-line billing

• interworking and roaming with PSTN, N-ISDN, GSM, X.25 and IP signalling, and
with their respective numbering schemes

• the measurement of traffic flows and so on, in order to optimise congestion control
and other management & efficiency techniques

• support for IP mobility between different environments (e.g. fixed & mobile)

Understanding UMTS
3 ©Informa Telecoms
• Upgrades to existing GSM/GPRS elements

• ATM transport

• New speech codec

• Flexibility in connection set-up, re-negotiation


& clearing

• Flexibility in bearers

• Support for VHE

• Enhanced charging & billing support

• Interworking with other networks &


numbering schemes

• Traffic flow measurements to enable


management efficiencies

• Enhanced IP mobility support

Fig. 2 – Some Key New Features of UMTS Networks

©Informa Telecoms 4
The UMTS Architecture

1.3 The Two Modes of W-CDMA Access

Two modes are defined for the W-CDMA access scheme, according to the two different
ways in which duplex operation is dealt with. Duplex refers to the combination of both
uplink (mobile to base station) and downlink (base station to mobile) transmission.

FDD (Frequency Division Duplex)


This is the name for the UMTS mode which is designed to give wide area mobile
coverage in UMTS. It can support 384kb/s in a mobile environment and uses a 5Mhz
frequency band for uplink and a separate 5Mhz for downlink. This is termed paired
spectrum channel allocation and operators in the UK for example have two or three
channels of paired spectrum depending on their licence (10Mhz or 15MHz).

TDD (Time Division Duplex)


TDD uses W-CDMA as the modulation scheme, as in FDD, but shares a single 5Mhz
channel for both uplink and downlink. To do this, the system allocates time slots for
both the uplink and downlink transmissions. The system is capable of very high data
rates (up to 2Mb/s) but is not suitable for anything above pedestrian mobility, due to
the slower power control loop.

Note that adding TDD mode to FDD will require a new Node B, likely to be smaller,
with lower power output and up to two antennas serving a range of 100m or so. TDD
is therefore sometimes described as equivalent to a cordless level of mobility.The
typical uses envisaged include offices, stations, supermarkets, airports and so on,
where traffic levels may be high but users are moving slowly. The channel allocation is
called unpaired spectrum, and is absent in Japan, although present in four of the five
licences in the UK.

In future, a further multi-carrier UTRA mode is expected to define compatibility


between UMTS and cdma2000.

Given the different wide and local area advantages of the two access schemes, the
concept of cell hierarchies arises, and may also include GSM/EDGE for the widest
area coverage in the early stages of UMTS deployment.

Understanding UMTS
5 ©Informa Telecoms
GSM/EDGE? FDD TDD

t t

f f

Fig. 3 – Two Modes of W-CDMA Access

©Informa Telecoms 6
The UMTS Architecture

1.4 Elements & Domains in a UMTS network

A UMTS network can be divided into the following physical domains:

1. User Domain

2. Infrastructure Domain, itself subdivided into:

a. Radio Access Network

b. Core Network

Each domain is further described in the following pages, and each may involve further
subdivisions and elements.

An important feature in the standardisation of UMTS is that the internal functionality


of domains is NOT specified. Instead the interfaces between them are defined and
open. This means that in theory it is possible to have several network elements of the
same type, with the minimum requirement for a fully featured network being to have
one of each.

A UMTS system could be divided into sub-networks, operational either alone or


together, but each with unique identities. A single such network is described as a
Public Land Mobile Network (PLMN), and may be connected to other PLMNs, or
other networks such as ISDN, PSTN or the Internet.

For example, in practical application this might mean that a single physical UTRAN
infrastructure could be shared by a number of core network domains. It also means
that different domain elements can be more easily sourced from different equipment
manufacturers, with interoperability ensured by the standardised interfaces, thus
leading to more competition and greater operator choice in sourcing infrastructure.

Understanding UMTS
7 ©Informa Telecoms
USER DOMAIN

Uu Interface
(Radio Interface)

INFRASTRUCTURE DOMAIN

RADIO ACCESS DOMAIN

Iu Interface

CORE NETWORK

Other PLMN,
Other Networks

Fig. 4 – UMTS Domains Overview

©Informa Telecoms 8
The UMTS Architecture

2. THE USER DOMAIN (USIM + ME DOMAINS)


The user domain describes the equipment needed by the user to access UMTS
services.

Within this domain are further subdivisions into the Mobile Equipment (ME) domain
and USIM domain. The combined ME and USIM is sometimes referred to as the
Mobile Station (MS).

The USIM domain contains the data and procedures allowing the ME to securely
identify itself, and is linked to the ME by the defined Cu Interface.

The ME domain performs radio transmission and contains applications. It may itself
be further subdivided, into the Mobile Termination MT (radio functions only) and
Terminal Equipment TE (contains end-to-end application, and may be a separate
device from the radio equipment, for example a laptop).

The functionality of the MT is entirely new in UMTS, in being able to interact with the
access network over the all new UMTS radio interface, Uu. In almost all cases in the
early deployment of UMTS, the mobile terminal must also be multi-mode, able to
receive/transmit between both GSM-based and UMTS-based radio access schemes.

Note that it is also possible to define the following terms relevant to this domain, to
describe the various types of human user involved:

• the subscriber, who is associated with the home environment & responsible for
payment

• the user, who is authorised to use services by the subscriber (and may have their
own user profile)

• another party, for example the calling party in a call, the called party and so on.
They may not be a 3G user

The User Domain is linked via the standardised Uu Interface (“air interface”) to the
Access Domain.

Understanding UMTS
9 ©Informa Telecoms
USER ACCESS CORE

Uu Interface

MS
MT
Radio

TE
ME
TE
Applications

Cu Interface

UICC/USIM
External
Applications

ME – Mobile Equipment
MS – Mobile Station
MT – Mobile Termination
TE – Terminal Equipment
USIM – UMTS Subscriber Identity Module

Fig. 5 – User Domain

©Informa Telecoms 10
The UMTS Architecture

3. THE ACCESS NETWORK

3.1 The Access Domain and Interfaces

The Access Domain is in direct contact with the User equipment and the core
network. This split is intended to decouple access functionality from non-access
functionality.

The Access domain contains the physical entities to manage resources of the access
network and provide the user with a way to access the core network domain. In
UMTS, the Access Domain refers to the radio access mechanism, and is also known
as the UTRAN (UMTS Terrestrial Access Network).

For UMTS phase 1, only the new UTRAN is considered as part of UMTS Access.
However the modular approach, and split between core and access network, means
that there is no reason to preclude other types of access network developed later on.
However all access methods will require use of the USIM.

In the early roll-out of UMTS, it remains relevant to also include the GSM/EDGE radio
network as an alternative within the access domain, since interworking will be
required until UTRAN coverage is fully achieved.

The UTRAN is connected via another standardised, open interface, the Iu to the Core
Network Domain.

Understanding UMTS
11 ©Informa Telecoms
UTRAN
Uu (UMTS Iu
User
Terrestrial Radio
Access Network)
Core
Network
A

GERAN
Um (GSM/EDGE
User
Radio
Access Network)

SAN
User (Satellite Access
Network)

Future
User Radio
Access

Fig. 6 – Access Domain & Interfaces

©Informa Telecoms 12
The UMTS Architecture

3.2 Requirements of the UTRAN

In defining the UMTS Terrestrial Radio Access Network (UTRAN), a number of


requirements and assumptions were identified. These are specified to ensure
maximum flexibility in the future evolution of the UMTS concept, and to ensure easy
evolution to the UMTS concept from second generation networks. In addition, they
provide flexibility in accessing the core network from not only the UTRAN, but from
evolved GPRS/EDGE GSM networks, Satellite access networks, fixed access
(narrowband and broadband), and future access types such as the Broadband Radio
Access Network.

The UTRAN is considered a separate entity to the core network, with a defined
interface connecting them. This interface is designed to provide a logical separation
of signalling and user data transport (this fits in with the evolved GSM network
specified for use in UMTS at Release 99). The interfaces are designed to be fully
specified, allowing as few options as possible and based on the logical model of the
entities concerned. This ensures maximum compatibility between manufacturers.

All radio procedures and aspects are fully handled within the UTRAN, including
mobility of the radio connection (soft handover, relocation of serving entities etc.).
This allows replacement of this radio access network with another access technology,
fulfilling one of the basic requirements.

Understanding UMTS
13 ©Informa Telecoms
CORE
NETWORK

UTRAN

• Logical Separation of Signalling and Data Transport


• CN and UTRAN functions separate from Transport Functions
• Macro diversity fully handled in UTRAN
• Mobility for RRC connection is fully controlled by UTRAN
• Interfaces based on logical model of the entities (with as few functional options
as possible).

Fig. 7 – Requirements of the UTRAN

©Informa Telecoms 14
The UMTS Architecture

3.3 Functions of the UTRAN

UTRAN functions have been specified to provide support for all radio activities
needed within the network infrastructure. They can be split into four main areas –
System Access, Mobility, Radio Channel Ciphering, and Radio Resource Management
and Control.

System access functions involve broadcasting system information to allow the mobile
to configure for access, admission control and radio channel congestion.

Mobility functions within the UTRAN are extensive in that they comprise handovers,
Serving Radio Network Controller (SRNC) relocations, and additionally, UTRAN
Registration Area (URA) and Cell updates for packet mode procedures. These are
used so that the UE can fall back to a less active state whilst retaining its packet data
“virtual connection”, known as a Packet Data Protocol Context (which describes the
quality of service required as well as specifying the address). In this case, the mobile
is tracked at URA or Cell level and paged accordingly when required to receive data.

Radio channel ciphering occurs in the UE and Serving RNC (at the RLC or MAC
layer), unlike GSM, where only the air interface is ciphered.

Understanding UMTS
15 ©Informa Telecoms
Systems Access
Control (Admission,
Radio Channel Congestion,
Ciphering and System information
Deciphering broadcast)

UTRAN
FUNCTIONS

Mobility Radio Resource


(Handover, SRNS Management and
Relocation) Control

Fig. 8 – UTRAN Functions

©Informa Telecoms 16
The UMTS Architecture

3.4 UTRAN Architecture – General

The UTRAN architecture comprises of one or more Radio Network Controllers (RNCs),
each controlling a number of base sites, known as Node B. Each grouping of RNC
and its associated Node Bs are collectively known as a Radio Network Sub-system
(RNS). Hence an UTRAN is comprised of one or more RNS.

Standard interfaces connect each RNS to the Core Network (both Circuit Switched
and Packet Switched Domains), and to the User Equipment. These interfaces are
known as IuCS, IuPS, and Uu respectively.

The UTRAN internal interfaces are also standardised. The Iur connects RNC (and
hence RNS), whilst the Iub connects the RNC and Node B.

Understanding UMTS
17 ©Informa Telecoms
CORE NETWORK

Iu (CS
& PS)

Radio Iur
Network RNS
RNC
Controller

Radio Network
Sub-system
(RNS)
Iub
Node B

Fig. 9 – UTRAN Architecture and Terminology

©Informa Telecoms 18
The UMTS Architecture

3.5 The Node B

The term Node B refers to the base station equipment which communicates with the
subscriber’s handset via the radio link (and of course with the main network via a
telecoms link).

It provides radio resources for a UMTS network, and uses UMTS channel allocation to
communicate with the handset. It provides all the RF processing, enabling
transmission and reception information to and from the mobile terminal. This
information is encoded using the W-CDMA scheme.

A single UMTS channel can be used on adjacent Node B sites and in different sectors
of the same Node B antenna system. A typical Node B may support a three sector
antenna and one or two UMTS carriers, although it is possible to configure up to six
sectors and up to three UMTS carriers. Each sector can be used as a different cell.

Node B tasks are as follows:

• conversion of data to and from the radio interface

• forward error correction

• rate adaptation

• W-CDMA spreading & despreading

• QPSK modulation (Quadrature Phase Shift Keying)

• measuring the quality & strength of connection

• determining the frame error rate

• handover between different sectors on the same Node B (“softer handover”)

• participation in power control, enabling the user terminal to adjust its power (“inner
loop power control”)

Understanding UMTS
19 ©Informa Telecoms
NODE B
FUNCTIONS

• Radio Resource Provider • May support multiple cells


• W-CDMA spreading through sectored antenna
and despreading • Supports Softer Handover
• QPSK Modulation
• Signal quality & strength
measurement • Converts data to/from W-CDMA transport
• Inner loop power control • Forward error correction and frame error
rate determination
• Rate adaptation

Fig. 10 – Node B Functions

©Informa Telecoms 20
The UMTS Architecture

3.6 The RNC

The RNC controls the operation of multiple Node Bs, managing resources such
as allocating capacity for data calls, and providing critical signalling such as
connection set-up, plus switching and traffic routing functionality.

Compared to 2G systems, it is broadly equivalent to the BSC, but also includes some
functionality of the MSC. In particular, it enables autonomous Radio Resource
Management by the UTRAN by allowing RNCs to directly communicate (via the Iur
interface), eliminating this burden from the core network. So all handover processes,
even where moving between cells controlled by different RNCs, are kept within the
UTRAN. Compare this with the situation in GSM, where handover between different
BSC areas required involvement of the MSC, and hence the core network.

The RNC can manage many Node Bs, and allocates radio resources and maintains
the equilibrium of a live and dynamic network. It must also interface with the core
network to provide access to the network operator services, applications, Internet
and gateways to networks such as GSM and PSTN.

The Iub is the first example of a fully standardised base-station-to-controller interface


within commercial mobile networks, and is defined thus in order to increase
competition between manufacturers in this very costly part of the network. For
example it is now possible to source Node B and RNC equipment from different
vendors, and hence for specialist vendors for Node B only, for example, to enter the
market.

The key features of the RNC are:

• management of radio resources

• channelisation code allocation

• QoS monitoring

• handover of users between cells on the same site (softer handover)

• handover of users between cells on different sites (soft handover)

• handover of users between different UMTS carriers (hard handover)

• handover of users to GSM networks (hard handover)

• power control management of user and Node B equipment

• network alarm correlation

Understanding UMTS
21 ©Informa Telecoms
• Controls functions of multiple Node Bs
• Radio resource management kept within the UTRAN
• Interfaces with core network
• Manages handover
• Power Control Management

CN

RNC

Node B

Fig. 11 – The RNC – General Functionality

©Informa Telecoms 22
The UMTS Architecture

3.7 RNC Terminology

The RNC operates in three main modes – Controlling, Serving, and Drift, depending
on whether an RRC connection is established, and how it is configured. The
descriptions of each mode are with respect to a single User Equipment, since each
physical RNC contains all the functionality needed for all three modes and is likely to
be acting in different modes with respect to different UE.

Controlling RNC

When mobiles are in idle mode, no RRC connection exists. Hence this mode simply
describes the functionality of the RNC which controls the Node B on which the
mobile is camped (i.e. the selected Node B). Any RRC messages relevant to the UE
are terminated at the UE and Node B.

Serving and Drift RNC

Once a mobile enters the RRC Connected mode, an RRC connection exists, and
RRC messages relevant only to the UE are terminated at the UE and Serving RNC
(SRNC).

In Soft Handover, the mobile is effectively served by two or more Node B. In the case
where the Node B are connected to different RNC, the Serving RNC remains as the
only Serving RNC, whilst the new RNC (now called the Drift RNC, or DRNC) simply
provides the radio resources necessary for the added radio link, and acts to carry the
Radio Resource messages and user data between the SRNC and UE transparently
over the Iur and Iub interfaces on the relevant channels.

As a result of Soft Handover, the original radio link may be deleted from the "active
set" of links, leaving the Serving RNC without any of its Node B in the active set. In
this case, the DRNC could become the SRNC by a process called SRNC relocation.
This procedure is considered optional.

If another RNC is involved in the active connection through soft handover, it is


declared a Drift RNC. The Drift RNC is responsible only for the allocation of code
resources, with the original Serving RNC continuing to handle control functions such
as admission, radio resource control, congestion, handover and so on.

It is possible to reallocate the Serving RNC to the former Drift RNC, if this becomes
necessary.

Understanding UMTS
23 ©Informa Telecoms
Node Controlling MSC/VLR Core
B RNC or SGSN Network

"Idle" Mode

Node Serving MSC/VLR Core


B RNC or SGSN Network

"Connected" Mode

Node Serving MSC/VLR Core


B RNC or SGSN Network

Node Drift
B RNC
Soft Handover

Node Serving MSC/VLR Core


B RNC or SGSN Network

Node Drift
B RNC
"Connected" Mode
(After Soft Handover)

Node MSC/VLR Core


RNC
B or SGSN Network

Node Serving
B RNC
SRNC Relocation
(Optional)

Fig. 12 – RNC Terminology

©Informa Telecoms 24
The UMTS Architecture

3.8 Functions of the RNC

3.8.1 Controlling RNC Functions


The CRNC controls one or more Node B. In practice, this is likely to be tens of Node
B. It is responsible for loading and congestion of cells, as well as allocating codes
and controlling admission. System information broadcasts for mobiles in idle mode
(or packet switched cell or URA paging modes) are originated from the controlling
RNC.

3.8.2 Serving RNC Functions


The radio bearers and signalling radio bearers for mobiles in connected mode are
terminated here (as well as in the User Equipment). All layer two (data link) processing
of information to/from the radio interface is processed here for UE in connected mode
(layer 1, the physical layer, is provided by the node B).

Outer loop power control is supported as well as the handover decisions.

Each User Equipment will have only one SRNC. The Serving RNC will often also be
the Controlling RNC for the Node B used by the mobile.

3.8.3 Drift RNC Functions


The DRNC is any RNC other than the SRNC which controls cells currently used by
the mobile. There may be zero, one or more DRNC at any one time for the specified
mobile. The DRNC may itself be performing macro-diversity combining and splitting
in support of Soft Handover.

No layer 2 processing of the data destined for, or received from, the radio interface is
performed in the DRNC.

Understanding UMTS
25 ©Informa Telecoms
Controlling RNC (CRNC)
• Controls one or more Node Bs.
• One Node B will have only one CRNC.
• Controls load and congestion of own cells.
• Executes admission control and code allocation for new radio links.

Serving RNC (SRNC)


• Terminates Radio Bearers and Signalling Radio bearers for the mobile
(ie RRC is terminated here in RRC connected mode).
• Performs Layer 2 processing of data to/from radio interface.
• Controls handover decisions.
• Outer loop power control.
• SRNC may also be CRNC for Node B(s) used by the mobile.
• Each connected UE has only one SRNC.

Drift RNC (DRNC)


• Any RNC, other than SRNC which controls cells used by the mobile.
• May perform macrodiversity combining and splitting.
• No layer 2 processing, unless mobile is using common or shared
transport channel.
• A mobile may have one or more DRNCs.

Fig. 13 – Controlling, Serving and Drift RNC Functions

©Informa Telecoms 26
The UMTS Architecture

3.9 Further UTRAN features

In addition to the elements just described, the main new feature of the UTRAN is the
existence of a new modulation scheme (W-CDMA) with two modes of access, FDD
and TDD.

In order to cope with broadband, multimedia traffic which could be circuit or packet,
asymmetric or symmetric, a suitable upgrade to the transport layer transmission
technology was also required. ATM was selected for this in Release ’99, and is
applicable to the Iur, Iub and Iu interfaces.

Other basic features of the UTRAN are as follows:

• it is contained within only one UMTS network

• it supports set-up, renegotiation & clearing of connections with a range of traffic


and performance characteristics

• it supports radio access bearers for broadcast and multicast applications

• it allows a mobile terminal to handle more than one radio access bearer service
simultaneously

• it permits seamless handover of active radio access bearer services from a single
terminal between the cells of one UTRAN. This handover happens with
imperceptible loss of speech and without degrading any QoS requirements for data

• it performs monitoring of cells in idle mode (cell reselection) and in active mode
(handover)

• for UTRANs with different UTRA modes (TDD and FDD), cell selection and paging
procedures will accommodate the fact that service areas may be covered by cells
supporting just one or both modes. It also supports handover between cells
supporting one or both modes

• it performs determination of the location of the mobile terminal

The market reality is that UTRANs will likely start as islands in a sea of GSM BSS, so
UMTS is specified to support dual system UMTS/GSM terminals. Issues like cell
reselection, paging procedures, handover and so on must therefore be supported in
both directions between GSM BSS and UTRAN (although the different bearer
capabilities mean that some traffic flows may have to be released or renegotiated
during handover).

Understanding UMTS
27 ©Informa Telecoms
• W-CDMA

• ATM transport

• Flexible bearer support & connection


management

• Handover functions

• Location determination

• Support for procedure and function interworking


with GSM BSS

Fig. 14 – Further New UTRAN Features

©Informa Telecoms 28
The UMTS Architecture

3.10 Handovers

A handover primarily allows a moving mobile to remain connected with the network
as different coverage areas (cells) are transited. Alternatively, it allows the network
operator to control congestion and cell loading by compelling a mobile to hand over
between adjacent cells in the overlap region (or even between hierarchical overlaid
cells).

Of increased importance for UMTS, though, is the possibility to hand over between
cells, frequencies, or even access network types for reasons of service requirements
(data rates, capacity, and quality of service issues).

Different handover types exist. Hard handovers (as seen in GSM) are needed for
handover between different UMTS carrier frequencies and between systems. Soft
handover provides handover between cells handled by different Node Bs, whilst
softer handover allows handover between cells handled by the same Node B.

Soft and softer handovers can be handled entirely within the UTRAN. Hard handovers
may be handled entirely within the UTRAN for handovers between carrier frequencies.
The Core Network will be involved for inter-system hard handovers.

3.10.1 Softer Handover


In around 10% of connections at any time, the mobile will be served by more than
one cell or sector operating on the same frequency and provided by the same Node
B. With the same codes used, the received signals are simply input into the Rake
Receiver as different components of the same signal. This process, together with the
Rake combining of any multi-path components enhances the signal.

Combining in this case is achieved entirely within the Node B and the User
Equipment. The process is known as micro-diversity. Only a single power control loop
is active per connection, provided by the Node B.

Understanding UMTS
29 ©Informa Telecoms
Core
Network

SRNC

Node B
Combined
signal received
via Rake
processing

• Communication via more than one air interface concurrently


• Rake receivers at Node B and mobile station used to combine
signal (similar to multipath reception)
• Occurs in about 10% of connections
• Only one power control loop per connection is active.

Fig. 15 – Softer Handover (Micro Diversity)

©Informa Telecoms 30
The UMTS Architecture

3.10.2 Soft Handover


In the case of the soft handover, combining is done in the RNC, with the different
arriving signals being continually assessed and the best signal chosen (every 10 –
80ms) for inclusion in the combined signal. The process is known as macro-diversity.

Soft handover is generally thought to occur in about 20 – 40% of connections, and


hence increases the overall requirement for transmission capacity in the UTRAN
transport network. Additional Rake fingers are also required to cope with the
increased number of "wanted" paths.

One of the main reasons for employing the soft and softer handover techniques in
CDMA is to mitigate the near-far effect, where a closer mobile contributes
disproportionately to the overall interference levels. Hence in all handover cases,
power control is critical.

For softer handover, only one power control loop is active (i.e. only one Node B
involved), but for soft handover, more than one power control loop is active (power
control is now being provided by more than one Node B). This does not present a
problem since the mobile simply responds to the Node B with the lower power
requirement, minimising overall interference in the system.

Soft and softer handover can be used simultaneously.

Understanding UMTS
31 ©Informa Telecoms
Combining/Splitting
Node B

Core
SRNC
Network

Node B

DRNC
Node B
• Communication via more than one air interface concurrently.
• Signal split/combined at RNC (best frame chosen)
• Requires additional:
– Rake receiver channels in Node Bs
– Transmission links Node B <-> RNC
– Rake fingers in mobile stations
• Occurs in about 20 - 40% of connections
• Power control active for each Node B (mobile responds to Node B
with lowest uplink power requirements).
• Can be combined with softer handover

Fig. 16 – Soft Handover (Macro Diversity)

©Informa Telecoms 32
The UMTS Architecture

UTRAN PROTOCOLS

3.11 Functions Of The UTRAN Protocols

The functions of each of the UTRAN control protocols are outlined opposite.

RANAP includes those functions needed to manage location procedures which may
need Core Network interaction, such as Hard Handover, and SRNS relocation. Radio
access bearer management, security, paging, identity management, and transparent
transfer of Non-Access Stratum signalling are all supported by RANAP.

RNSAP provides functions which are split into four modules. Basic inter RNC mobility
is supported in order to provide soft handover between RNS and to transfer waiting
data during SRNS relocations.

In addition, support is provided for both dedicated channel traffic (transparently


transferred between SRNC and UE in dedicated transport channels) and common
channel traffic (transferred from the SRNC to the DRNC for inclusion in the common
channels being supported by that DRNC – which is also acting as the CRNC for the
Node B in question).

NBAP functions are classed as either common or dedicated, depending on whether


they are concerned with common or dedicated channels. RNC in Controlling, Serving
or Drift Modes are supported. The functions are generally concerned with the use or
configuration of the radio channels, including paging, access requests, radio link
measurements, handovers and fault management.

Understanding UMTS
33 ©Informa Telecoms
RANAP FUNCTIONS INCLUDE:
Core • Relocation SRNS & Hard Handover
Network • Radio Access Bearer Management
• Paging and ID Management
• UE <-> CN Signalling Transfer (Transparently)
• Security Mode Control
• Location Reporting

RNSAP FUNCTIONS INCLUDE:


RANAP

• Basic Inter - RNC Mobility


• Dedicated Channel Traffic Support
• Common Channel Traffic Support
• Global Resource Management (optional)
(Implemented in Four Separate
Modules Shown Above)

SRNC RNSAP DRNC

NBAP FUNCTIONS INCLUDE:


Common -
NBAP
• Setup First Radio Link of UE
• RACH, FACH & PCH Handling
• Reporting Cell/Node B Measurements
• Cell Configuration
• Fault Management

Dedicated NODE B
• RL Addition, Release & Reconfiguration for
one UE context
• Dedicated and Shared Channel Handling
• Softer Combining Support
• Reporting of RL Specific Measurements
• RL Fault Management

Fig. 17 – UTRAN Protocol Functions

©Informa Telecoms 34
The UMTS Architecture

4. THE UTRAN TRANSPORT NETWORK

4.1 Requirements Of The Transport Network

As a network of interconnected nodes, the UTRAN presents familiar problems to the


designer of a transport network.

The UTRAN provides the User Equipment (UE) with access to the Core Network (CN)
for both Circuit Switched and Packet Switched services as well as providing transport
for all signalling interactions, including those confined within the UTRAN, those
between the UTRAN and the Core Network, and those being transferred through the
UTRAN from UE to CN or vice-versa.

The W-CDMA air interface has been designed to support services which vary widely
in terms of acceptable quality of service. Hence services with varying data rates,
delay tolerance, delay variance, and acceptable error rates are all possible.

The UTRAN transport network has therefore been specified to support the varying
qualities of service required for all the data types.

4.2 The Options

In choosing the technology, reliability, cost, flexibility, scalability, delivery time scales,
and not least suitability for the task at hand were all factors. Specifying a protocol
especially for UMTS was deemed not necessary since ATM (Asynchronous Transfer
Mode) already existed and provided a relatively close match to the requirements.
Fortunately, the transport protocol has been specified separately from the UTRAN
protocols themselves, hence future flexibility in choice of technology is assured.

At the moment, ATM is specified rather than an Internet Protocol (IP) solution,
however the continuing work on IP is bringing it closer to satisfying the requirements
(and at an inevitably low cost).

Understanding UMTS
35 ©Informa Telecoms
Rest of
SGSN Network
UTRAN
Transport (CS & PS)
Network

RNC MSC

Packet Switched
Node & Circuit Switched
B User Data & Signalling

RNC
RNC
S
n t ig n a R a d
I

e r lli i o B
fa c n g e
e C R a d i a re r s
ont o Bearers
rol In
f o r m a ti o n

Node
B

• ATM Chosen

Fig. 18 – UTRAN Transport Network Requirements

©Informa Telecoms 36
The UMTS Architecture

4.3 ATM Operation

Within a network of ATM switches, virtual channels and virtual paths through the
network from entry point to exit point can be provided by ensuring that the switches
have the relevant identifiers and routing information available. This information can be
pre-configured, or set up within the switches dynamically by specific signalling
messages as a requirement for a path or channel through the network arises.

Switching is achieved by the use of fixed length (53 Octet) cells with appropriate
identifiers. Each cell is identified at each ATM switch and simply directed on to the
next switch in accordance with the routing information held in the switch. The
identifiers will change as the cell passes through the switch, however, each switch will
have been programmed with the correct identifiers and the overall path or channel will
still be valid.

Switching can occur on two levels – at the path level, which may simply switch by
analysing only the "virtual path identifier" (irrespective of the "virtual channel
identifier"); and at the channel level, where both identifiers are analysed and the cell
routed accordingly. This can allow flexibility in network provision by allowing simpler
processing at virtual path switches, and more in-depth at virtual channel switches.
ATM physical switches can of course have both levels of switching available.

Understanding UMTS
37 ©Informa Telecoms
B

ATM
NETWORK

B A

• Virtual channels/paths through the network are set up by O&M


action or dynamically using signalling
• Channels and paths identified using VCIs (Virtual Channel
Identifiers) and VPIs (Virtual Path Identifiers) in the ATM Cell Header

ATM Switch

Fig. 19 – ATM Operation

©Informa Telecoms 38
The UMTS Architecture

4.4 The ATM Cell

On any link between switches, the cells for a single path or channel will be allocated
as required (asynchronously) within the overall synchronous cell stream.

The cell itself is made up of 48 octets of data (which may include higher layer control
information) with 5 octets of ATM header information. This information includes:

The Virtual Path Identifier (VPI)


The Virtual Channel Identifier (VCI)
Payload Type (PT)
Cell Loss Priority (CLP)
Header Error Correction (HEC)

The VPI and VCI are used in the switching process. The PT identifies the type of
payload. The Cell Loss Priority allows cells to be prioritised in terms of which ones
could be discarded first in congestion situations. HEC provides a mechanism for
checking for errors within the header (only).

Understanding UMTS
39 ©Informa Telecoms
The ATM Cell:

48 Octets 5 Octets

HEADER:
DATA (VPI/VCI/PT/
CLP/HEC)

Contains User Data and


Adaptation Information (Quality
of service requirements)

ATM Cell Streams:

Continuous stream of cells

A B

Asynchronous allocation of cells


in synchronious stream

Fig. 20 – The ATM Cell

©Informa Telecoms 40
The UMTS Architecture

4.5 ATM and Quality Of Service

It is not the ATM cell itself which provides the necessary control and protocols to
support different Qualities of Service (QoS), but the specified adaptation process
which occurs between the data to be transported and the ATM cell.

The adaptation process introduces extra overhead (control data) onto the data to be
placed within the 48 octets of data within the ATM cell. In terms of protocol, the ATM
Adaptation Layer (AAL) lies directly between the data to be carried and the ATM layer.
Four different AALs have been specified for use with ATM, and two have been
adopted within the UTRAN – AAL2 and AAL5.

The characteristics of each are shown opposite. Between them, they provide support
for all necessary UTRAN QoS requirements.

Understanding UMTS
41 ©Informa Telecoms
• Variable bit rates
• Packet type data
AAL5 • Segmentation & Reassembly
• Constant delays not required
• Suitable for signalling, packet user,
data transfer etc

AAL5 AAL5

ATM NETWORK

AAL2 AAL2

• Variable bit rates


• Circuit type data
AAL2 • Segmentation & Reassembly
• Constant delays required
• Suitable for multimedia, video etc

AAL-ATM Adaptation Layer

Fig. 21 – ATM and Quality of Service

©Informa Telecoms 42
The UMTS Architecture

5. THE CORE NETWORK

5.1 The Core Network Domain

The core network contains the physical entities providing support for the network
features and telecoms services, for example the management of user location, control
of network services; and switching & transmission mechanisms for signalling & user
information.

An important logical split is made within the core network for UMTS Release ’99,
between a circuit-switched and packet-switched domain.

CS (circuit-switched) Domain
This refers to the set of all core network entities offering “CS type connection”,
i.e. one for which dedicated network resources are allocated at connection
establishment and held until connection release. PSTN and ISDN are examples of
other circuit-switched networks. In UMTS the CS domain provides data service
support of at least 64kb/s.

PS (packet-switched) Domain
This refers to all core network entities for “PS type connection”, i.e. one which
transports user information using autonomous concatenation of bits called packets,
where each packet can be routed independently of the previous one. The Internet is
the most well known example of a packet-switched network, although other public
data networks (PDNs) do exist, including Mobitex, RAM, CDPD and so on. In UMTS,
the PS domain provides support for data service capability of up to 2Mb/s.

The Iu interface is therefore subdivided into IuCS and IuPS in order to support connection
of each of these core network domains to the single access network (UTRAN).

Understanding UMTS
43 ©Informa Telecoms
User Domain

UTRAN

IuPS IuCS

CORE
NETWORK PS Domain CS Domain
DOMAIN

PS Networks CS Networks

Fig. 22 – The Core Network Domains

©Informa Telecoms 44
The UMTS Architecture

5.2 Specific Entities in the UMTS Release ’99 Core Network Architecture

It is possible to define three categories of network elements in Release ’99:

1. GSM core network elements: MSC, VLR, HLR, AuC and EIR

2. GSM enhancements (GSM Phase 2+):

– GPRS to support packet-switching

– CAMEL (and other toolkits) as a basis for the VHE

3. New UMTS-specific enhancements, in particular the new UTRAN and USIM. This
new UTRAN can be connected to the GSM Phase 2+ core network.

We have already discussed the basic elements of the UTRAN, whereas the first two
categories above refer to elements within the core network.

Release ’00 takes the first steps towards integrating circuit switched domain and
packet switched domain transports.

Understanding UMTS
45 ©Informa Telecoms
1. GSM Core Network Elements

• circuit switching

• databases

2. GSM Phase 2+ Enhancements

• packet switching through GPRS

• CAMEL and other toolkits

3. UMTS specific elements

• UTRAN

• USIM

Fig. 23 – The Concept of Strata

©Informa Telecoms 46
The UMTS Architecture

5.3 The Circuit Switched Domain & GSM Core Network Elements

The GSM core network elements form the basis for the circuit-switched domain in
UMTS, albeit with some enhancements to support the higher data rates and other
requirements of UMTS services. The entities specific to CS domain are: MSC, GMSC,
VLR.

MSC
The MSC provides the interface between the radio system and fixed network,
performing all necessary functions to handle CS services to and from mobile
terminals. As such, an MSC will interface with several base stations.

In effect it is an exchange which performs switching and signalling functions for


mobiles within its designated area of control. It needs to take into account the
allocation of radio resources and the mobile nature of users, which impact the
location registration & handover between cells.

Gateway MSC
The GMSC provides routing to the appropriate MSC where a mobile terminal is
located, after having interfaced with the databases within the home environment.

VLR
The Visitor Location Register is used by an MSC to retrieve information for mobile
stations currently in its area. A mobile terminal registers as it enters the area, at which
point the VLR and HLR (Home Location Register – see below) exchange information
on the subscriber and his/her service capabilities. It is the VLR which tracks the
current location of the terminal, although the HLR will know on which VLR the
subscriber is registered.

An additional element which is required in UMTS is:

Interworking Function (IWF)


In generic terms, an IWF provides the functionality to allow interworking of differing
networks such as ISDN, PSTN and PDNs (i.e. protocol conversion). A new element
required for the CS part of the core network in UMTS is such an interworking function
to provide protocol conversion between the A (GSM) and Iu-CS (UMTS) interfaces
where the radio network joins the Core Network. This requirement is in order to enable
the core network to operate with both the existing 2G and new UMTS radio access.

Understanding UMTS
47 ©Informa Telecoms
UMTS ME GSM ME

GSM/
UTRAN
EDGE BSS

IuCS

IWF A

MSC
VLR

GMSC

New in UMTS
GSM Phase 2+ PSTN, ISDN, etc…

Fig. 24 – Circuit-Switched Domain

©Informa Telecoms 48
The UMTS Architecture

5.4 The GSM Location Registers

The core GSM elements also include some further databases, which are carried
forward into UMTS with appropriate modifications as required:

HLR
The Home Location register contains subscriber information, and is the register to
which a subscriber is assigned. It will also contain information enabling charging and
packet routing of messages to the area where the mobile is currently registered
(for GPRS support), plus various location-service related information if that is also
supported.

Subscriber information consist of:

• the IMSI (international Mobile Subscriber ID)

• Mobile Station ISDN numbers

• Packet Data Protocol Addresses for GPRS

• LMU indicator for location services

• information on service access/restrictions

Authentication Centre (AuC)


The AuC stores data for each subscriber to allow the IMSI to be authenticated and to
allow ciphering of communication over the radio path. In short, it allows the mobile to
use the network. The data required for these two processes is transmitted via the
HLR to the VLR, MSC and SGSN as required.

Equipment ID Register (EIR)


The EIR is responsible for storing the International Mobile Equipment IDs (IMEIs) in
the GSM system. These classify equipment as white, grey or blacklisted, and so
enable service to be prevented to stolen or uncertified terminals.

This set of registers can be grouped together for simplicity to define the “Home
Subscriber Server” (HSS).

Understanding UMTS
49 ©Informa Telecoms
UMTS ME GSM ME

GSM/
UTRAN
EDGE BSS

IuCS

IWF A

MSC
EIR VLR

HLR

AUC
GMSC

HSS

PSTN, ISDN etc…

Fig. 25 – Location Registers

©Informa Telecoms 50
The UMTS Architecture

5.5 The Packet-Switched Domain & GPRS Core Network Elements

Since the circuit-switched side of the network is limited to 64kb/s by its ISDN-based
switching capability, whereas GPRS allows direct interconnect with data networks of
much higher bit-rates, GPRS is a prerequisite for the introduction of UMTS.

Entities specific to PS are the GPRS-specific entities, the SGSN (serving GPRS
support node) and GGSN (gateway GSN).

The GGSN and SGSN have comparable functions and architectural positions as the
GMSC and MSC/VLR in the circuit-switched domain. They are IP routers, which allow
direct transmission between mobile terminals and data networks such as the Internet,
Intranets, X25 and so on.

The SGSN includes a location register function which stores subscription information
and location information for packet-switched services for each subscriber registered
in the SGSN.

The GGSN stores subscription information and routing information for each
subscriber for which the GGSN has at least one PDP context active. This information
is used to tunnel packet data destined for a GPRS terminal through to the SGSN
where this terminal is registered.

Once again, a new interworking function is required in order that the SGSN can
communicate both with the new UTRAN and the existing GSM BSS.

Understanding UMTS
51 ©Informa Telecoms
UMTS ME GSM ME

Gb GSM/
UTRAN
EDGE BSS

IuPS

IWF IWF

MSC
SGSN EIR VLR

HLR

AUC
GGSN GSMC

HSS

Internet, X25 etc…

Fig. 26 – Packet-Switched Domain

©Informa Telecoms 52
The UMTS Architecture

5.6 Operation in the Core Network CS Domain

5.6.1 User and Control Information in the CS Domain


Within the CS Domain of the Core Network, MSCs provide the switching functionality
and control for setting up, tearing down and supervising circuits, as well as some
support for supplementary services. In addition, the HLR and SCP provide support for
Mobility and Operator Specific Services respectively. The VLR also provides support
for mobility and is co-located with the MSC. This is illustrated in Fig 4.

User data is transferred between MSCs, and between the GMSC and external
network via traffic circuits, without further protocols being added (although overhead
is introduced at the physical level, the amount and format being dependent on the
transmission system being used).

The control information is passed within Signalling System Number 7 protocols, and
makes use of the lower layer signalling network (which would usually share the same
transmission infrastructure as the user data).

Understanding UMTS
53 ©Informa Telecoms
Signalling
HLR (Control Information)
Circuits
(User Data)

SCP 4

MSC

MSC/
GMSC
VLR 2

MSC

1
)
Cir
cui D ata
t ( U se r

Core Network

1 User Data
Traffic Channel Set Up, Clear Down and Supervision
2
(includes Supplementary Service Support)
3 Service Control
4 Mobility Management

Fig. 27 – User and Control Information in the CS Domain

©Informa Telecoms 54
The UMTS Architecture

5.6.2 Signalling in the CS Domain – SS7 Overview


In the circuit-switched domain, MSCs are switching centres which hold all the
switching functions needed to support mobiles in their area, routing transmission
paths for both the actual user data, and the signalling messages needed to control
services. They may also hold interworking functions required to interwork with other
networks such as the PSTN.

These MSCs are connected to each other and to the HLR and other databases using
a variation of the ITU standardised SS7 (signalling system 7). SS7 is a “common-
channel” signalling system, and the circuit-switched user data network is actually
separated from the packet-switched SS7 signalling network. SS7 operates using a
specified stack of protocols.

SS7 provides call control by exchanging control messaging between the MSCs and
fixed network switches. This may be via direct paths or via signalling transfer points
(STPs), designed to route packets across this network.

A third entity, the service control point (SCP), is a database which may control
information relevant to routing, for example translating a freephone (0800) number
into a routing address within the network. No longer do individual switches need to
be modified to introduce a new service. Instead, such changes are made to the SCP
elements within the signalling network, which controls the user data switching
performed at the MSCs/Switches. The SCPs and MSCs/Switches communicate via
a standardised interface, and (if it has this functionality), the MSC/Switched is termed
a Service Switching Point (SSP).

In the UMTS CS domain, the MSCs correspond to the SS7 SSPs, providing both
basic switching, plus access points to supplementary and advanced IN services.
Location registers, such as the HLR and VLR, and additional service elements such
as the CAMEL Service Environment, are similar in functionality to the SCPs.

Where remote data bases are being accessed, a Signalling Point Relay (SPR) allows
the SS7 entity’s unique global address to be translated into the simpler format (point
codes) used in the individual SS7 packet-switched networks (called the Message
Transfer Port), as the signalling message is passed from one network to another
en-route to its remote destination.

Understanding UMTS
55 ©Informa Telecoms
MSC
(SSP)
SS7 NETWORK

STP

Databases

User Data
(SCP, HLR, CSE)

STP

MSC
(SSP)

Fig. 28 – SS7 within the Core Network CS Domain

©Informa Telecoms 56
The UMTS Architecture

5.7 Operation in the Core Network PS Domain

5.7.1 User and Control Information in the PS Domain


The Packet-Switched domain uses packets of information to carry both user data and
the control information for the user data between GSNs. This means a common set of
packet protocols can be defined to allow this exchange of information to take place.
The intermediate routers handle the information in the same way, simply routing it on
to its “final” destination (the SGSN or GGSN).

For mobility control and provision of operator specific services, the GSNs
communicate with the HLR and SCP respectively using the standard techniques
found within the Circuit-Switched domain.

Understanding UMTS
57 ©Informa Telecoms
Signalling
HLR (Control Information)
Packets of Data
(Control and User
Information)

4
SCP
3

Router

SGSN GGSN

1 2 Router
Pa )
cke Data
ts rol
(U
s er & C ont

Core Network

1 User Data
2 Control Data
3 Service Control
4 Mobility Management

Fig. 29 – User and Control Information in the PS Domain

©Informa Telecoms 58
The UMTS Architecture

5.8 OTHER NETWORK ENTITIES

5.8.1 Some other entities for specific services


Although the above are the basic and key components for GSM and GPRS based
systems, and hence the basis for the first release of UMTS, it should be noted that
there are various other network elements which relate to the delivery of specific
services. Notably

For SMS:
Two elements are important in the delivery of SMS. Firstly, the SMS Gateway MSC
acts as an interface between the SMSC (Short Message Service Centre) and the
PLMN for the delivery of messages. Its counterpart is the SMS Interworking MSC,
which acts in reverse, as an interface between the PLMN and SMSC for the
submission of messages. These connect to the serving MSC/GSN.

For Location Services:


The Serving Mobile Location Centre (SMLC) manages the overall scheduling of
resources to perform positioning. In UMTS this functionality is integrated into the
Serving RNC, an element of the UTRAN.

For CAMEL:
To support CAMEL features, including Service Control Functions, Switching Functions
and so on, the CAMEL Service Environment (CSE) is defined and lies within the Home
Network.

For Cell Broadcast:


The Cell Broadcast Centre (CBC) manages Cell Broadcast messages and determines
delivery parameters. The CBC attaches directly to the RNC via the Interface IuBC, for
which a mandatory logical interface protocol is defined.

Other entities include:

• the Group Call Register Entity, holding information on Voice Group Call or Voice
Broadcast Services

• the Shared Interworking Function, providing interworking for data/fax calls

• various Number Portability entities

However, detailed discussion of these further entities is beyond the scope of this
overview course.

Understanding UMTS
59 ©Informa Telecoms
SMS

• Short Message Service Centre

• Connects to the UMTS Core Network via SMS


Gateway/Interworking MSC

Location Services

• Serving Mobile Location Centre (SMLC)

• Located within the UTRAN Radio Network Controller

CAMEL

• Camel Service Environment

• Located within the Home Network

Cell Broadcast

• Cell Broadcast Centre

• Connects directly to the UTRAN Radio Network


Controller

Fig. 30 – Specific Services and Support Elements

©Informa Telecoms 60
The UMTS Architecture

6. IN/CAMEL IN UMTS

6.1 Intelligent Networks

Intelligent Networks originally provided advanced features such as freephone, calling


card and so on, by providing intelligence within databases which could translate
these dialled numbers into standard routing numbers within networks. These early
services were soon followed up by further advanced services based on this
intelligence, incorporating interaction with the user to further customise services.

Traditionally, switching equipment would need to be upgraded each time a new


service was required. IN separates service intelligence and switching, such that to
implement any defined “Capability Set” of services, upgrades to switches are
required, but the addition of the actual services within this capability set do not
require switch upgrades. This means that new services can be quicker and cheaper
to install, and that service creation and switching is split into two markets, thereby
increasing vendor competition.

IN can provide such services only when there is an exchange of data between
the switch and an application or database which has knowledge about number
translation or other features. Most INs, including GSM Phase 2+ networks, use lower
layer SS7 protocols to enable the Switches (known as Service Switching Points, or
SSPs) to communicate with databases known as Service Control Points (or SCPs).

The application or database must reside in the IN, and a standardised protocol layer
known as INAP is used to enable interaction between the SSP and SCP. INAP lies
above the internationally standard protocols which form the SS7 signalling system,
incorporating MTP, SCCP and TCAP.

The intelligent applications which control IN services are defined by the operator, and
are not themselves standardised. This means that IN offers a route to operator
differentiation, but equally that in many cases the same services cannot be offered
outside the network of that operator.

Understanding UMTS
61 ©Informa Telecoms
Pre-IN:

Switching
&
Service Control

IN:
Intelligent Applications

Service
Service
Creation
Control Point
Tools

SS7 (INAP)

Service
Switching Point

Switching

Fig. 31 – Intelligent Networks

©Informa Telecoms 62
The UMTS Architecture

6.2 CAMEL

CAMEL (Customised Application for Mobile network Enhanced Logic) is a feature


designed to provide support for services of operators which are not standardised
services (e.g. operator-specific IN services), even when subscribers are roaming
outside the home network. CAMEL is a network feature, not a supplementary service.

In order for CAMEL to function, information exchange is required between the Home
and Visited networks, and subscribers who have access to CAMEL services are
marked within each network.

The concept is basically that of IN, in that it is the MSCs (now termed SSPs within the
CAMEL context) which communicate with the SCP. The big difference is that the MSC
and SCP may well be in different networks (the SCP will be located in the subscriber’s
home network for home network operator specific service support).

Due to different networks being involved, the CAMEL standard is more tightly defined
than IN capability set 1 (IN CS-1), although it is still seen as an extension of CS-1. It is
specified within GSM Phase 2+, but is a core feature of the Virtual Home Environment
(VHE) concept of UMTS.

GPRS and Circuit-Switched connections are both supported by CAMEL.

Understanding UMTS
63 ©Informa Telecoms
CAMEL
SCP Service
Environment

HOME
UMTS
NETWORK

ns
tio
ac
ter
l In
me
Ca

Gateway
MSC/GSN
nel
an
Ch
affic SERVING
Tr
Serving UMTS
MSC/GSN NETWORK
(SSP)

Fig. 32 – CAMEL Within UMTS

©Informa Telecoms 64
The UMTS Architecture

7. CHARGING

Understanding UMTS
65 ©Informa Telecoms
CS Domain:

• Time

• Location

• Number of Channels

PS Domain:

• Time

• Location

• QoS

• Data volume

Fig. 33 – Charging

©Informa Telecoms 66
The UMTS Architecture

8. CORE NETWORK TRANSPORT

The CS Domain will in most cases be brought forward directly from an operator’s
existing GSM Phase 2+ core network. Such networks commonly use PDH or SDH,
although there is no standard specified for this.

Equally in the PS domain, no standard transport is specified – any IP network can lie
between the GGSN and SGSN. ATM is a common choice, since it is designed for
robust support of packet networks.

ATM is already specified for transport within the UTRAN. It seems likely that both core
network domains may also migrate to ATM in UMTS networks, particularly when
operators seek to combine the transport systems of the CS and PS domains, a major
goal behind the network architectures proposed in Release 4 and beyond.

Such an upgrade will require the addition of an interworking function within the MSCs
to support ATM-PSTN interworking, and provide support for the ATM protocol stack.

However currently, the choice of transport layers remains up to the operator, and is
not defined in the standards.

Understanding UMTS
67 ©Informa Telecoms
CS DOMAIN
PS DOMAIN

• Any IP
Network Mobility &
• Commonly Service
uses ATM Databases

• PDH or SDH

UTRAN

• ATM Based

• Goal is to combine PS & CS Transport Systems


(Release 4 Architecture)

Fig. 34 – Transport in the Core Network

©Informa Telecoms 68
The UMTS Architecture

9. MOBILE IP

9.1 Mobile IP: Basics

Mobile IP is an ongoing standardisation project within the IETF (Internet Engineering


Task Force), who are now also a market representation partner within 3GPP.

The aim of Mobile IP is to enable a mobile to communicate using the same IP


address at all times, regardless of the IP network through which it accesses the
Internet. If this were not the case, then active TCP sessions would be broken each
time the mobile wanted to access through a different network (e.g. UMTS vs. LAN),
meaning that guarantees of service quality, and a “seamless view” for the application,
would not be possible.

Mobile IP provides a mechanism whereby a mobile station is given a permanent IP


home address, which belongs within its original home network. If accessing through
this home network, it will therefore just act like any non-mobile station and can be
reached through normal IP routing.

However when it accesses through some visited network, it is assigned a “care of


address” (COA) which belongs to this visited network, and which identifies the current
location of the mobile. Since other stations do not know the location of the mobile,
they will send packets to its permanent home address, where the packets are
received by a router which is assigned the status of the “home agent” (HA).

This HA forwards packets onto the mobile station using tunnelling, having previously
been provided with the COA by the mobile. The mobile station can answer directly to
the other station, although using its home address rather than the COA as the source
address for the message. Any time the mobile station moves to attach via a different
IP subnetwork, it will register its new COA with its HA.

Understanding UMTS
69 ©Informa Telecoms
Home
Agent

“Permanent
(Home)
Address”

“COA”

Can Answer Direct


(Uses Home Address, not COA)
Caller
Called

Visited Network

COA – “Care of Address”

Fig. 35 – Mobile IP

©Informa Telecoms 70
The UMTS Architecture

9.2 Mobile IPv4 vs. IPv6

In the case of IPv4, a COA address will most likely be a router, called the foreign
agent (FA), which will have the functionality to enable it to forward messages on
to the mobile station. A single COA may apply to more than one mobile station.
Overlaying Mobile IP onto a GPRS/UMTS network means enabling the GGSN to have
this FA functionality, able to set up a PDP context for the mobile station, and tunnel
PDUs from the GGSN towards the user.

A key advantage in moving to IPv6 is that the number of IP addresses available


becomes effectively unlimited. It is possible to assign mobile stations a direct COA,
using some form of automatic assignment mechanism. Messages from the home
agent can be tunnelled directly towards the mobile station.

If the mobile station has a direct COA, then the core network tunnelling provided by
GTP becomes redundant, since data can be tunnelled directly from source to user.
Indeed it will be possible to combine the GGSN and SGSN into a single Internet
GPRS Support node (IGSN), which acts as the FA and marks the end of the UMTS-
specific network. The IGSN would need to support current SGSN functionality,
supporting MAP communication with UMTS location registers, plus of course support
Mobile IP and any accounting procedures required by an FA.

In effect, an ultimate scenario is that Mobile IP may handle mobility management and
tunnelling within the PS domain core network.

Understanding UMTS
71 ©Informa Telecoms
a) IPv4 Plus GPRS/UMTS

HA

PDP/
GTP “COA”

GGSN/
SGSN
FA
PDP/
GTP

Visited Network

COA – “Care of Address”


HA – Home Agent
b) IPv6 Plus GPRS/UMTS FA – Foreign Agent
IGSN – Internet GPRS
Support Node

HA

“COA”
“COA”
IGSN

Visited Network

Fig. 36 – Mobile IP Evolution

©Informa Telecoms 72
The UMTS Architecture

10. RELEASE 4

10.1 Release 4 – Control & Data Separation in the CS domain

In particular, Release 4 introduces the concept of separation of the control and user
planes (i.e. signalling & user data transport). Whereas Release ’99 is based on re-using
and extending the equipment from GSM core networks, Release ’00 makes the first
move towards implementing a full IP core network, and introduces new multimedia
server elements.

The advantage of this new approach is in moving towards a scenario needing only
a single transport network for both voice and data (i.e. both the circuit and packet
switched domains), so the same IP or ATM based interface can be employed to
transport packets between the Radio Access Network and the external PSTN or
IP networks.

In particular, the first step is that the circuit-switched domain is evolved by splitting the
MSC into two entities, a Media Gateway which handles actual user data transport
(“transport plane”), and the MSC server, which lies within the “control plane”, and is
involved in signalling and control of the Media Gateway. Non IP-native terminals
(e.g. legacy GSM handsets) are handled by the MSC servers.

Understanding UMTS
73 ©Informa Telecoms
1. Release ’99 – CS Domain

Signalling &
Iucs User Data
UTRAN MSC GMSC PSTN

HSS

2. Release 4 – CS Domain

User Data
UTRAN MGW MGW PSTN

Control Control

MSC Signalling GMSC


Server Server

HSS

Fig. 37 – Evolution of Circuit Switched Domain

©Informa Telecoms 74
The UMTS Architecture

10.2 The IP Multimedia Subsystem

In the packet switched domain, transport continues between the Serving SGN and
Gateway GSN, but a new subsystem, the IP Multimedia subsystem, is introduced into
the core network. This system is introduced in order to enable support for IP
telephony a well as IP multimedia applications, direct to multimedia,
IP-addressable terminals.

The use of IPv6 is mandatory within this IP Multimedia subsystem, and control of the
system is centred around a new element, the Multimedia Call Server (CSCF – Call
State Control Function). The CSCF is a SIP server, creating a SIP session to the
mobile terminal.

A Media Gateway takes care of the transformation of user and signalling traffic
between this packet-based domain and the PSTN world, or the IP Multimedia
Subsystem can of course connect directly into an external IP network via the GGSN.

Other new elements include the Media Gateway Control Function (MGCF) and the
Media Resource Function (MRF).

Understanding UMTS
75 ©Informa Telecoms
Internet
UTRAN SGSN GGSN
etc…

HSS MRF

CSCF
(SIP
Server)

PSTN
Signalling Only MGCF MGW etc…
User Data

Fig. 38 – IP Multimedia Subsystem

©Informa Telecoms 76
The UMTS Architecture

10.3 New Domain Concept in Release 4 and Beyond

Taking the new architectural evolutions into account, it is now possible to summarise
the new UMTS. The Radio Access and User Domains remain structurally the same.

The Core Network remains divided into circuit and packet switched domains, with the
IP multimedia Core Network subsystem newly added.

It is also useful to define the “service subsystem”, which can link into each of the
core network domains and the IP multimedia subsystem by means of a “service
control point” to the Open Service Architecture.

All these various systems of course must continue to interact with the Home
Subscriber Server, HSS.

For the sake of clarity, not all the elements or interfaces within and between the
various elements are shown.

Understanding UMTS
77 ©Informa Telecoms
Services Subsystem IP Multimedia CN Subsystem

OSA

SCP CSCF

HSS

GGSN

MSC
Server SGSN

CS Domain PS Domain

Radio
Access

User
Domain

Fig. 39 – Domains in All-IP UMTS

©Informa Telecoms 78
The UMTS Architecture

11. NETWORK EVOLUTION

11.1 3GPP Release ’00/Release 4

Release ’00 (Release 4) and future planned releases of UMTS concentrate on the
evolution of the core network architecture defined in Release ’99. In particular, the
long-term aim is to move towards an architecture which is “all IP”.

The phases of standardisation can be summarised as shown opposite.

This reiterates the major changes as follows, from GSM as the original starting point:

• GPRS introduced a packet switched domain into the system, and allowed
IP services tunnelled directly to ISPs (single media IP).

• UMTS Release ’99 added a brand new radio interface.

• UMTS Release ’00/4 and future releases, will integrate the packet and circuit-
switched domains in the core network, adding new server elements to achieve this,
and ultimately enabling true IP Multimedia services to be offered.

Understanding UMTS
79 ©Informa Telecoms
IP Multimedia
Tunnels to ISPs – PS Single Media

Services CS

IP Multimedia
Subsystem
PS Uses GSNs GSNs
Continue
Core Servers
CS Uses MSCs Replace MSCs
Network

UTRAN
GSM EDGE
Air
Interface
GSM GPRS R’99 R’00
(R4)

Fig. 40 – Phases of Standards

©Informa Telecoms 80
ANNEX 1
DOMAINS

©Informa Telecoms 81
The UMTS Architecture

A.1 DOMAINS IN UMTS

A.1.1 Domain Structure


The physical architecture in UMTS is modelled using the concept of domains,
where areas of the network are identified as separate entities, with each being
made up of the physical elements in that part of the network. Standard interfaces
connect the different domains together.

The domains are organised hierarchically such that the first split simply describes
a User Equipment Domain and an Infrastructure Domain. However, these are
further broken down into the USIM Domain and Mobile Equipment Domain (for
the User Equipment Domain), and Access Network Domain and Core Network
Domain (for the Infrastructure Domain). The Core Network Domain is then further
broken down into Serving, Transit and Home Network Domains.

In general, it is fairly clear what each domain represents.

Understanding UMTS
82 ©Informa Telecoms
HOME Home
NETWORK Network
Domain

Zu

Cu Uu Iu Yu
SERVING TRANSPORT
NETWORK NETWORK

Serving Network Transit Network


Domain Domain

Mobile Access Core Network Domain


Equipment Network
Domain Domain

User Equipment Infrastructure Domain


Domain

USIM
Domain

Fig. A.1 – Domains in UMTS

©Informa Telecoms 83

Vous aimerez peut-être aussi