The document provides an overview of the evolution from GSM to UMTS networks and 3G network architecture. It discusses: 1) The types of evolution including technical, network, and service evolution from 2G to 3G. 2) The basic GSM network elements and functions. 3) Enhancements to GSM including GPRS, EDGE, and HSCSD that improved data capabilities within the 2G network. 4) The 3G UMTS network architecture defined in 3GPP Release 99, including the UTRAN radio access network and core network nodes.

1. Evolution from GSM to UMTS

2. Outline of the lecture
• Evolutions form GSM to UMTS.
• 3G network architecture.
• Service provision in UMTS.

3. Evolution types
• Evolution contains not only technical evolution but also expansion to network
architecture and services.
• Technical evolution: how network elements are developed and with witch
technology.
• Network evolution: in result of network element evolutions the general
functionality of the network is changing.
– Technical evolution different for different vendors.
• Service evolution: demand generated by the end-users that can be supported by
the technical features of the network.
2G 3G
Technical Evolution
Network Evolution
Service Evolution

4. Evolution of the wireless networks
SMS
9.6
UMTS
E
D
G
E
G
P
R
S
HSCSD
14.4
1998 1999 2000 2001 2002
10k
100k
1000k
64k
1k
Circuit
Packet

5. Basic GSM network (1)
• Driving idea in GSM: to define several open interfaces.
– Operator may obtain different network components form different suppliers.
– Strictly defined interface determines how the functions are proceeding in the network
and which functions are implemented internally by the network element.
• GSM provides a means to distribute intelligence in the network. Network
divided into four subsystems:
• Network Subsystem (NSS): call control.
• Base station Subsystem (BSS): radio path control.
• Network Management Subsystem (NMS): operation and maintenance.
• Mobile Station (MS).
• Difference between 1G and 2G:
– Symmetric data transfer possibility.
– Service palette adopted from Narrowband ISDN.

6. Basic GSM network (2)
BSS NSS
BTS BSC
Um A
MS
MSC/VLR GMSC
HLR/AuC/EIR
TRAU ISDN
PSPDN
PSTN
CSPDN
Network Management (NMS)

7. GSM Network elements
• MS: mobile equipment + subscriber data (Service Identity Module)
• Base Station Controller (BSC):
– Maintains radio connections towards Mobile Station.
– Maintains terrestrial connection towards the NSS.
• Base Transceiver Station (BTS):
– Air interface signalling, ciphering and speech processing.
• Mobile Service Switching Centre (MSC):
– Call control.
– BSS control functions.
– Internetworking functions.
– Charging,
– Statistics,
– Interface signalling towards BSS and external networks.
• Serving MSC: BSS connections, mobility management, inter-working.
• Gateway MSC: Connections to the other networks.
• Visitor Location Register (VLR): local store for all the variables and functions
needed to handle calls in the area related to VLR.

8. Value Added Service platform
• Value Added Service (VAS) platform: simple platform for supporting certain
type of services in GSM. (Short Message Service Centre (SMSC), Voice Mail
System (VMS))
– Use standard interface towards GSM. May or may not have external interfaces
towards other networks.
BSS NSS
BTS BSC
Um A
MS
MSC/VLR GMSC
HLR/AuC/EIR
TRAU ISDN
PSPDN
PSTN
CSPDN
Network Management (NMS)
V
A
S

9. Intelligent Network (IN)
• Intelligent network: a platform for creating and providing additional services.
– Enables service evolution.
– Changes in the GSM switching elements to integrate the IN functionality.
– Example pre paid subscription.
• IN adopted from fixed network.
– Not possible to transfer service information between networks.
BSS NSS
BTS BSC
Um A
MS
MSC/VLR GMSC
HLR/AuC/EIR
TRAU ISDN
PSPDN
PSTN
CSPDN
Network Management (NMS)
V
A
S
I
N

10. IN CS-1 (capability set 1)
Originating Basic Call State Model
(BCSM) for CS-1
1. O_Null & Authorize
Origination_Attempt
2. Collect_Info
1
3. Analyse_Info
4. Routing & Alerting
5. O_active
2
3
7
6. O_Exeption
10
4
5
6
8
9
Route_Select_Failure
O_Call_Party_Busy
O_No_Answer
O_Abandon
O_Disconnect
Orig. Attempt_Authorized
Collected_Info
Analyzed_Info
O_Answer
O_Mid_Call
7. T_Null & Authorize
Termination_Attempt
8. Select Facility &
Present_Call
12
9. T_Alerting
10. T_Active
11. T_Exeption
15
13
16
14
T_Abandon
Term._Attempt_Authorized
T_Answer
18
17
T_Called_Party_Busy
T_No_Answer
T_Mid_Call
T_Disconnect
Terminating BCSM for CS1
Incoming Call
Processing
Outgoing Call
Processing

11. BCSM
• BCSM is a high-level finite state machine description of call control function
(CCF) activities required to establish and maintain communication paths for
users.
• BCSM identifies points in basic call and connection processing when IN
service logic instances are permitted to interact with basic call and connection
control capabilities.
• Point In Call (PIC) identify CCF activities required to complete one or more
basic call/connection states or interest to IN service logic instances.
• Detection Point (DP) indicate points in basic call and connection processing at
which transfer of control can occur.
• Transition indicate the normal flow of basic call/connection processing from
one PIC to another.
• Events cause transitions into and out of PICs.

12. HSCSD
• The data throughput of the system is increased:
– Channel coding is improved (9.6 kb/s -> 14 kb/s).
• High Speed Circuit Switched Data (HSCSD).
– Several traffic channels can be used.
– Max data rate 40 -50 kb/s.
BSS NSS
BTS BSC
Um A
MS
MSC/VLR GMSC
HLR/AuC/EIR
TRAU ISDN
PSPDN
PSTN
CSPDN
Network Management (NMS)
V
A
S
I
N
HW&SW Changes for HSCSD

13. GPRS
• General Packet Radio Service
(GPRS)
– For supporting packet switching traffic
in GSM network. No voice channel
reservation.
– Support for asymmetric traffic.
• Requires new service nodes:
– Serving GPRS Support Node (SGSN).
– Gateway GPRS Support Node (GGSN).
• Can not guarantee the QOS.
BSS NSS
BTS BSC
Um A
MS
MSC/VLR GMSC
HLR/AuC/EIR
TRAU ISDN
PSPDN
PSTN
CSPDN
Network Management (NMS)
V
A
S
I
N
HW&SW Changes for GPRS
GPRS Packet Core
SGSN GGSN
Gb
Internet
Other Data NW

14. EDGE (1)
• Exchanged Data Rates for Global/GSM Evolution (EDGE):
– New modulation scheme. (8 PSK)
– Different coding classes. Maximal data rate 48 kbps per channel.
• EDGE phase 1:
– channel coding and modulation methods to provide up to 384 kbps data rate.
– One GPRS terminal gets 8 time slots. The channel should be good.
• EDGE phase 2:
– Guidelines for achieving high data speed for circuit switching services.
• Data rates achieved almost equal to the ones provided by UMTS.
• Data rates not available everywhere in the cell.

15. E-RAN NSS
BTS BSC
Um A
MS
MSC/VLR GMSC
HLR/AuC/EIR
TRAU ISDN
PSPDN
PSTN
CSPDN
Network Management (NMS)
V
A
S
I
N
HW&SW Changes for EDGE
E-GPRS Packet Core
SGSN GGSN
Gb
Internet
Other Data NW
EDGE (2)

16. E-RAN CN CS Domain
BTS BSC
Um A
MS
MSC/VLR GMSC
HLR/AuC/EIR
ISDN
PSPDN
PSTN
CSPDN
Network Management (NMS)
V
A
S
C
A
M
E
L
UTRAN CN PS Domain
BS
RNC
Uu
UE
SGSN GGSN
Gb
M
E
X
E
W
A
P
U
S
A
T
Iu
Iu
Internet
Other Data NW
3G network R99 (1)

17. 3G network R99 (2)
• New Radio interface.
• More suitable for packet data
support.
• Interoperability with GSM:
– GSM radio interface modified to
broadcast CDMA system
information. WCDMA networks
transfer also GSM data.
– Possibility to set 2G MSC/VLR to
handle the wideband radio access,
UTRAN.
• Customised applications for Mobile
network Enhanced Logic (CAMEL):
– Possibility to transfer service
information between networks.
– In the future almost CAMEL will be
involved in all transactions between
networks.
• CS domain elements are able to handle
2G and 3G subscribers.
– Changes (upgrades) in MSC/VLR and
HLR/AC/EIR.
– For example SGSN
• 2G responsible for mobility management
(MM) for packet connections
• 3G MM divided between RNC and
SGSN.
• Services
– Initially 3G offers same services as 2G.
– Services transformed into PS domain.
• Trends
– Separation of connections in control and
services.
– Conversion of the network towards all
IP.
– Multimedia services provided by the
network.

18. 3GPP R4 (2)
• The 3GPP R4 introduces separation of connection, its control, and services for
CN CS domain.
• Media Gateway (MGW): an element for maintaining the connection and
performing switching function when required.
• MSC server: an element controlling MGW.
• Packet switched voice (Voice Over IP).
– The CS call is changed to the packet switched call in MGW.
– For higher uniformity the CS and PS domain is mediated by IP Multimedia
Subsystem.
• CAMEL will have a connection to the PS domain elements.

19. 3GPP R4 (1)
GERAN CN CS Domain
BTS BSC
Um
MS
MGW MGW
MSC Server
ISDN
PSTN CSPDN
Network Management (NMS)
UTRAN CN PS Domain
BS
RNC
Uu
UE
SGSN GGSN
Iu
IP, Multimedia
HSS V
A
S
C
A
M
E
L
M
E
X
E
W
A
P
U
S
A
T
IMS

20. 3GPP R5 (All IP)
• Network looks to the users always same
– Development inside the network
– New transport technology: R99 ATM based; R4, R5 IP based.
• All traffic from UTRAN is supposed to be IP based.
GERAN
BTS BSC
Um
MS
ISDN
PSTN CSPDN
Network Management (NMS)
UTRAN CN PS Domain
BS
RNC
Uu
UE
SGSN GGSN
Iu
IP, Multimedia
HSS V
A
S
C
A
M
E
L
M
E
X
E
W
A
P
U
S
A
T
IMS
IP/
ATM
IP/
ATM
IP/
ATM

21. Future trends
• Techniques:
– Further separation of the user plane from the control plane.
– Towards packet switching network.
– Transparency of access technologies. Greater emphasis to services and quality.
– 4G ?
• Data rate ~20 Mbps (200 Mbps)
• Self planning dynamic topologies.
• Integration of IP.
– OFDM
• Services
– Location based services. Many services existing at the same time at different
resolution.
– Separation of users:
• Commercial.
• Private users.
• Private users with specific needs.

22. 3G Network architecture
• 3G is to prepare a universal infrastructure able to carry existing and future
services.
• Separation of access technology, transport technology, service technology.
• The network architecture can be divided into subsystems based on the nature
of traffic, protocol structures, physical elements.
• Conceptual network model
• Structural network model
• Resource management architecture
• UMTS service and bearer architecture

23. Conceptual network model
• Protocol structure and responsibilities divided as:
– access stratum: protocol handling activities between UE and access network,
– non-access stratum: protocol handling activities between UE and Core Network,
• Stratum is the way of grouping protocols related to one aspect of the services
provided by one or several domains. (3GPP spec. TR 21-905)
USIM Mobile
Equipment
Access
Network
Serving
Network
Transit
Network
Cu Yu
Iu
Uu
Access Stratum
Home
Network
PS Domain
CS Domain
Non-Access Stratum
User Equipment Domain
Access Network
Domain
Core Network Domain
Infrastructure Domain
• Based on nature of traffic:
– packet switched (PS)
– circuit switched (CS)
• Domain is a highest level
of group of physical
entities and the defined
interfaces between such
domains. (3GPP spec. TR
21-905)

24. UMTS architecture domains
User Equipment domain: dual mode and multi-mode handsets, removable smart
cards … .
• Mobile Equipment (ME) domain:
– Mobile Termination (MT) entity performing the radio transmission and related
functions
– Terminal Equipment (TE) entity containing the end-to-end application.
• User Service Identity Module (USIM) domain:
– contains data and procedures to unambiguously and securely identify itself.
Infrastructure domains:
• Access network domain: physical entities managing the access network
resources and provides the users with mechanisms to access the core network.
• Core network domain: physical entities providing support for the network
features and telecommunication services: management of user location
information, control of network features and services, switching and
transmission.

25. Core network domains
• Serving Network (SN) domain representing the core network functions
local to the user’s access point and location changes when user moves.
• Home Network (HN) domain representing the core functions
conducted at a permanent location regardless of the user’s access point.
– The USIM is related by subscription to the HN.
• Transit Network (TN) domain: the CN part between the SN and the
remote party.

26. UMTS stratums
USIM
MT - AN
MT/ME
Access
Network
Domain
Serving
Network
Domain
Home
Network
Domain
AN - SN
“Access Stratum”
MT - SN
“Serving Stratum”
USIM - HN
SN - HN
“Home Stratum”
MT - SN
USIM - MT
“Transport Stratum”
USIM - MT
TE
MT - AN
MT
Access
Network
Domain
Serving
Network
Domain
Transit
Network
Domain
AN - SN
“Access Stratum”
TE - MT MT - SN
“Serving Stratum”
Application Stratum
Application
“Transport Stratum”
Remote
Party
Mobile
Equipment
Domain

27. Transport stratum
Supports the transport of user data and network control signalling from other strata
through UMTS
• consideration of physical transport formats used for transmission.
• Mechanisms for error correction and recovery.
• Mechanisms to encrypt data over the radio interface and in the infrastructure
part if required.
• Mechanisms for adaptation of data to use the supported physical format.
• Mechanism to transcode data to make efficient use of the radio interface.
• May include resource allocation and routing local to the different interfaces.
• The access stratum, which is specified to UMTS as the part of the trasnport
stratum.

28. Access stratum
• Consists of User Equipment (UE) and infrastructure parts, as well as access-
technique specific protocols between these parts.
• Provides services related to the transmission of data over the radio interface
and the management of the radio interface to the other parts of UMTS.
The access stratum includes the following protocols:
• Mobile termination - Access network (MT-AN) protocol supporting transfer of
detailed radio-related information to coordinate the use of radio resources
between MR and AN.
• Access network - Serving Network (AN - SN) protocol supporting the access
from the SN to the resources provided by the AN. It is independent of the
specific radio structure of the AN.

29. Serving stratum
Consists of protocols and functions to route and transmit user of network
generated data/information form source to destination. The source and
destination may be within the same of different networks. It contains functions
related to telecommunication services, and includes:
• USIM - Mobile termination (USIM - MT) protocol supporting access to
subscriber-specific information to allow functions in the user equipment
domain.
• Mobile Termination - Serving Network (MT -SN) protocol supporting access
from MT to the services provided by the serving network domain.
• Terminal Equipment - Mobile Termination (TE -MT) protocol supporting
exchange of control information between the TE and the MT.

30. Home stratum
• Consists of protocols and functions related to the handling and storage of
subscription data and possibly home network specific services.
• Functions to allow domains other than the home network domain to act on
behalf of the home network.
• Functions related to subscription data management and customer care, as well
as billing and charging, mobility management and authentication.
The home stratum include the following protocols:
• USIM - Home Network (USIM - HN) protocol supporting co-ordination of
subscriber-specific information between USIM and HN.
• USIM - Mobile Termination (USIM - MT) protocol providing the MT with
access to user specific data and resources necessary to perform actions on
behalf of the home network.
• Mobile Termination - Serving Network (MT - SN) protocol supporting user
specific data exchange between the MT and the SN.
• Serving Network - Home Network (SN - HN) protocol providing the SN with
access to HN data and resources necessary to perform its actions on behalf of
the HN.

31. Application stratum
• It represents the application process itself, provided to the end user.
• It includes end-to-end protocols and functions making use of services provided
by the home, serving, and transport strata and necessary infrastructure
supporting services and/or value added services.
• The functions and protocols within the application stratum may adhere to
GSM/UMTS standards or may be outside the scope of the UMTS standards.
• End-to-end functions are applications consumed by users at the edge
of/outside the overall network.
• Authentication and authorised users may access the applications by using any
variety of available user equipment.

32. Structural Network Architecture
• UE user equipment
• ME mobile equipment
• USIM UMTS Service Identity
Module
• RAN Radio Access Network
– UTRAM UMTS RAN
– GERAN GSM/EDGE RAN
• Node B Base Station (BS)
• RNC Radio Network Controller
• RNS Radio Network Subsystem
• CS Core network
• Iur Interface between two RNS
UTRAN CN
RNS
CN CS Domain
CN PS Domain
Registers
RNS
BS
RNC
RNC
BS
BS
BS
UE
Uu Iu
Iur
UE
UE
3G MSC/VLR 3G GMSC
HLR/Au/EIR
SGSN GGSN

33. Resource Management Architecture
• Communication Management: functions and procedures related to the user
connections.
• Mobility Management: functions and procedures related to mobility and
security.
• Radio Resource Management: algorithms related to the radio resource.
CM
RRM
MM MM MM
RRM
CM
Terminal (UE) UTRAN
NMS
CN
Communication Control
Mobility Control
Radio Resource Control
Mobility Control
Open Interface Uu Open Interface Iu
• The functions are related to the
control mechanisms:
– Communication Control.
– Mobility Control.
– Radio Resource Control.

34. UMTS Services
• 3G is designed as platform for
providing services
– The lower location the layer
has, the bigger is the
investment in the network
elements.
Content Provider layer
Service Creation Layer
Network Element Layer
Physical Transmission Layer
Network
Management
Security
Functions
– The higher location the layer has the bigger is the investment in people and ideas.
• Challenges: network management and securities.
• Methods for supporting service creation:
– Virtual Home Environment: concept for personal service environment portability
across network boundaries and between terminals.
– Mobile Station Execution Environment: provides a standardised execution
environment in an MS, and an ability to negotiate its supported capabilities with a
MExE service provider, allowing applications to be developed independently of any
MS platform.
– CAMEL network feature: subscriber can use of Operator Specific Services (OSS)
even when roaming outside the HPLMN.

35. Service Provision, user point of view
• The concept of the VHE is such that users are
consistently presented with the same personalised
features:
– Personalised services.
– Personalised User Interface (within the capabilities
of terminals).
– Consistent set of services from the user's perspective
irrespective of access e.g. (fixed, mobile, wireless
etc.) Global service availability when roaming.
USER
Personal
Service
Environment
Home
Environment
Provided and
Controlled by
User
Profile
Contains
1:N
Value Added
Service Provider
HE Value Added
Service Provider
N:N
• The User's personal service environment is a combination of services and
personalisation information (described in the user profile).
• The Home Environment provides services to the user in a managed way, possibly by
collaborating with HE-VASPs, but this is transparent to the user.
• User may access services directly from Value Added Service Providers.

36. Implementation of Services
• Standardised Services: Vendor specific implementation using standardised
interfaces for service communication.
• Operator Specific services: Operator specific implementation of services by
using vendor specific toolkits with standardised interfaces.
• Other Applications: implementions using standardised interfaces to the Service
Capabilities (Bearers, Mechanisms). The functionality offered by the different
Service Capabilities are defined by Service Capability Features.
• Within the terminals Service Capabilities are accessible via APIs, for example,
MExE.
Network
terminal view
clientn
client2 ...
API (e.g. MExE, SAT)
GSM/GPRS/UMTS protocol(*)
(*) ... standardisedinterfaces
(+) ... to bestandardised
GSM/GPRS/UMTS protocols, CAP/MAP
(*)
SC 2 SC 3 SC n
Applications / Clients
MS functionality, Standardized Services
Service
capabilities SC 1
ervice
apability
eatures (+)
Application
Interface
SC 4
Service
Capabilities
Application Interface
Proprietary
Service
Capability
Feature
Proprietary
Service
Capability Pre-set by Standards, e.g.
CAMEL, SAT, MExE, access to
bearers etc.
Service
Capability Features
Accessible to Applications/Clients
via Standardised Application
Interface
Built using Service
Capability Features
Applications/Clients
Proprietary
Service
Personal Service Environment
Personal Service Environment
(Customised/Portable)
Standardised

37. User Requirements for VHE
• The Personal Service Environment describes how the user wishes to manage
and interact with their communications services.
• User Interface Profile:
– Menu settings: menu items shown, menu structure, the placement of icons.
– Terminal settings: ringing tone and volume, font type and size, screen and text
colour, language, content types and sizes accepted.
– Network related preferences: language used for announcements … .
• User Service Profile:
– A list of services subscribed to and references to Service Preferences for each of
those services if applicable.
– Service status (active/deactive).
• Use could have more than one service profile.

38. Home environment requirements for
VHE provision
• Control access to services:
– depending on the location of the user, and serving network.
– on a per user basis e.g subject to subscription.
– depending on available service capabilities in the serving network, and terminals.
• Define the scope for management of services by the user, for services provided by the
HE.
• Manage:
– service delivery based on for example end to end capabilities and/or user preferences.
– the prepaid accounts (e.g. increase, decrease the credit, or pass the information to an.
application which manages the credit).
– provision of services to users or groups of users.
• Request:
– version of specific services supported in serving network and terminal.
– details (e.g. protocol versions and API versions) of available service capabilities supported in
the serving network, and terminals.
• Handle charging for services.
• Inform the serving network:
– of the type of charging (i.e. prepaid or/and postpaid) for any required service.
– of the threshold set for a given service required by the user and charged on a prepaid account.
– how to manage a service for which the threshold has been reached.
• Deploy services to users or groups of users.

39. Serving Network requirements for VHE
provision
The serving network should not need to be aware of the services offered via the
home environment.
It shall be possible for the serving network to perform the following:
• The serving network shall support user access to services in the home
environment.
• The serving network shall provide the necessary service capabilities to support
the services from the home environment as far as possible.
• Dynamically provide information on the available service capabilities in the
serving network.
• Provide transparent communication between clients and servers in terminals
and networks.
• Request the charging information (type of charging, threshold for prepaid
services and behaviour if the threshold is reached) for any service possibly
required by the user.
• Handle the call according to the instructions received by the home
environment regarding charging activities.
• Inform the home environment of the chargeable events.

40. Bearer Service
End-toend Service
UMTS Bearer Service
External Bearer
Service
Local Bearer
Service
UTRA
Service
Radio
Bearer Service
Iu
Bearer Service
Physical
Bearer Service
Backbone Phys.
Bearer Service
Backbone
Bearer Service
CN
Bearer Service
Radio Access Bearer Service
TE MT UTRAN CN Iu EDGE CN gateway