PRESENTATION

GSM evolution -UMTS CORE NETWORK ARCHITECTURE

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Presentation Contents
GSM network
GSM data services evolution - HSCSD - 14.4 kbps data service - EDGE Circuit Switching vs Packet Switching

GPRS
UMTS access Core Network Architecture

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

GSM network

SC MAP SMS-IWMSC SMS-GMSC MAP HLR

MAP

FNR ILR MAP

MAP

MAP

AUC

PSTN
ISUP GMSC

EIR MAP BTS BSC

TRA

BSS
BSSAP A-IF

MSC/VLR gsmSSF ISUP CAP INAP SSP SCP SDP MSC/VLR ISUP

PLMN

A-bis

MIN

Transcoder at BSC

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

GSM network

SC MAP SMS-IWMSC SMS-GMSC MAP HLR

MAP

FNR ILR MAP

MAP

MAP

AUC

PSTN
ISUP GMSC

EIR MAP BTS BSC

TRA

BSS
BSSAP A-IF

MSC/VLR gsmSSF ISUP CAP INAP SSP SCP SDP MSC/VLR ISUP

PLMN

A-bis

MIN

Initially GSM had been optimized for speech.

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Data Access with GSM

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

GSM Air Interface (TDMA)

uplink frequencies

TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7 TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7

downlink frequencies

TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7 TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7

The 9.6 kbits/sec limitation origins from the standardized definition of the frame duration and the definition of the TS structure called Channel coding (not all the bits in a TS convey user information, there are tail bits, parity flags, protocol information for data Control etc)

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

High Speed Circuit Switched Data - HSCSD

TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7

Up to 4 timeslots can be used in order to offer data speeds up to 38.4 kbps (in case of data compression 100-150 kbps can be achieved)
On the A-I/f a multiplexing scheme is used and up to 4 TCHs are multiplexed into a 64 kbps PCM time slot in order to avoid waste of terrestrial circuits Dynamic allocation of timeslots during connection is supported Information of timeslots used during the connection is continuously reported to the MSC for charging purposes

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

14.4 kbps data service

14.4 kbps data service provides higher throughput per timeslot using a new channel coding by deleting certain bits and use them to transfer user data.
In order to achieve this the protocols that control the data flow over the A I/f were modified to support new frame formats HSCSD in combination with 14.4 kbps data service offers data speeds up to 57.6 kbps

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Enhanced Data Rate for GSM Evolution

EDGE mainly affects the radio-access part of the network
BTS BSSAP BSC A-bis A-IF MSC/VLR gsmSSF

New hardware is required

New software is required

To increase the bit rate on the air-interface a new modulation scheme is introduced the eight-phase-shift-keying (8-PSK) modulation. Using 8-PSK modulation we can have up to 64 kbps on the air interface

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Circuit switching vs Packet Switching

Both type of networks provide communication capabilities between nodes/hosts and they try to distribute network resources efficiently between competing entities Circuit Switching Packet Switching

TDM (Time Division Multiplexing) FDM (Frequency Division Multiplexing)

Use idle periods in link for other data flows

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Circuit switching vs Packet Switching

DISADVANTAGES
Circuit Switching For services that require bursty nature of data transmission (e.g WWW browsing) the circuit remains seized for big time intervals without actually being used i.e. a lot of idle bursts might be sent while the network is close to congestion The user can be charged based on the time that the circuit is seized and not based on the amount of data that she/he sent/received. Packet Switching If there is high traffic in the network and too many data flows the packets are buffered. This causes problems to real time applications like speech, video etc.

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

General Packet Radio Services - GPRS

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

GPRS Radio Resource sharing

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

GPRS Logical Architecture

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Why UMTS ?
Requirements of a mobile network High quality speech High data rates over radio interface Packet radio services and volume based charging

Demand for access anywhere-anytime

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Why UMTS ?
2nd generation mobile systems (one of them is GSM) use incompatible radio technologies and different frequencies and can not offer service everywhere. 3rd generation mobile system had to be adopted by all the standardization forums in order to be able to provide global coverage

3GPP
IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Definition of 3GPP
US T1P1 Europe ETSI Japan ARIB, TTC South Korea TTA Other Market Partners

3rd Generation Partnership Project

3GPP will provide globally applicable Technical Specifications for a 3rd Generation Mobile System based on the evolved GSM core network, and the Universal Terrestrial Radio Access (UTRA), to be transported by relevant Standardization bodies (Organizational Partners) into Appropriate deliverables (e.g., standards)

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

3GPP major decisions

UMTS spectrum allocation
W-CDMA (Wideband Code Division Multiple Access) to be used as Radio Transmission Technology

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

WCDMA
Higher capacity and coverage
Designed for both packet and circuit switched services Fast and efficient packet access Higher service flexibility - bandwidth on demand - support for services with variable rate - support for simultaneous services - support of multiple parallel variable-rate services on one connection More users per transceiver reduced base station cost

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

UMTS Logical Architecture

MSC SCF

BSS SIM MS BTS BSC

GMSC

A Iu

MSC HLR AUC

EIR RNS USIM UE BS RNC

SMSGMSC
SMSIWMSC GGSN

External Network

Gb

Iu
Iur RNS USIM UE BS RNC

SGSN

SGSN UTRAN

Core Network
IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Transcoder Handling
Contrary to GSM for UMTS access the transcoder is not placed at the RNC. Speech is sent encoded to the core network in order to save capacity and its responsibility of the CN to place the Transcoder (preferably at the edge of the network).

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

UMTS Logical Architecture

MSC SCF

BSS SIM MS BTS BSC

GMSC

A Iu

MSC HLR AUC

EIR RNS USIM UE BS RNC

SMSGMSC
SMSIWMSC GGSN

External Network

Gb

Iu
Iur RNS USIM UE BS RNC

SGSN

SGSN UTRAN

Core Network
IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Iur Interface
Iur

RNSAP
DRNC Q.AAL2 SRNC Iu MSC/VLR

During an active call each RNC (acting as Serving RNC) can address any other RNC (acting as Drifting RNC) and establish a logical connection via Iur interface.
RNSAP: (Radio Network Subsystem Application Part) is the control plane protocol used to establish signalling connections between Serving and Drifting RNC. Q.AAL2: bearer control protocol, that is used to establish/release bearer connections between network entities

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Iur Interface
PLMN2 PLMN1

SRNC DRNC DRNC

When the UE moves into the next DRNC, the old Iur-connection is released and a new Iur-connection is established between SRNC (still the same) and a new DRNC. In this way UE can move far away from SRNC and it can happen that DRNC may belong to another MSC service area and even to another network. Problem: The SAI (CGI in GSM) received from DRNC via Iur-interface may not be recognized by the MSC/VLR server. This would cause problems e.g. for enquiry call because data needed to route the call is not available.
IXG/DG G.Viennas 2002-12-04 Rev A

MSC/VLR

AXE SWDC

Area Cluster
Instead of administered CGIs and LAIs of own and neighboring MSC/VLR service area the area cluster administration was introduced.

An area cluster can have one or more SAIs, LAIs or PLMNs connected to it. One SA, LA or PLMN identity can be connected to only one area cluster. An area cluster can contain areas both inside and outside the own MSC/VLR service area. Default data

PLMN Area Cluster MSC/VLR area cluster

LAI area cluster

SAI area cluster

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Iu Interface
RANAP

RNC
Architecture split between call control and bearer control becomes visible

Q.AAL2

MSC/VLR

RANAP: is a protocol needed to support procedures for connection management, mobility management and radio resource management. It transfers signaling messages between UE and MSC/VLR and RNC and MSC/VLR. Q.AAL2: bearer control protocol, that is used to establish/release bearer connections between RNC and MSC/VLR User data: i.e. speech or data are exchanged between RNC and MSC/VLR using an ATM connection and the Binding Information (Iu Transport Association on RANAP or Server User Generated Reference on Q.AAL2) is used to correlate the signaling path with the respective ATM connection.
IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Iu Interface
RANAP

RNC

MSC/VLR

MGW
RANAP: is a protocol needed to support procedures for connection management, mobility management and radio resource management. It transfers signaling messages between UE and MSC/VLR and RNC and MSC/VLR. Q.AAL2: bearer control protocol, that is used to establish/release bearer connections between RNC and MSC/VLR User data: i.e. speech or data are exchanged between RNC and MSC/VLR using an ATM connection and the Binding Information (Iu Transport Association on RANAP or Server User Generated Reference on Q.AAL2) is used to correlate the signaling path with the respective ATM connection.
IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Presentation Contents
GSM network
GSM data services evolution - HSCSD - 14.4 kbps data service - EDGE Circuit Switching vs Packet Switching

GPRS
UMTS access Core Network Architecture

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Core Network: Definition

The Core Network interconnects an operators Access Networks with each other and with External Networks.

The Core Network consists of the physical entities/nodes (such as Control, Media Gateway and Signaling Gateway nodes) which provide support for the network features and telecommunication services. We can connect different access networks like UTRAN (UMTS) or BSS (GSM) to the same core network. There is therefore no such thing like a UMTS core network! We only have ATM based core networks, STM based core networks or IP based core networks (or a mixture of these technologies within the same core network)

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Core Network Architecture

Vertical vs Horizontal Integration

Dedicated Networks
Services
Services/Applications Data/IP Networks PSTN/ISDN PSTN/ISDN

Core Network

Data/IP Networks

PLMN

PLMN

CATV

Connectivity

Access Transport & Switching Networks

IXG/DG G.Viennas 2002-12-04 Rev A

CATV

AXE SWDC

Architectural split : Why?

Architectural split is the split between the Control and Connectivity layer of the core network, contrary to the monolithic networks where Connectivity and Control Layers overlap each other.
Current trend, at markets and standardisation bodies

Enables introduction of new bearer technology without affecting the call control Needed for a common core network (circuit switched and packet switched (GPRS)) Needed for a common core network to provide several services that currently provided by different networks
IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Core Network Architecture

Application Servers Service enablers Application Servers

Services/applications
MSC SGSN Server Server HLR/AuC/FNR GMSC/Transit Server SGW PSTN/ ISDN MGW WCDMA EDGE GSM Control User data
IXG/DG G.Viennas 2002-12-04 Rev A

Control

Connectivity

MGW GGSN

Internet Intranets

AXE SWDC

Core Network entities

Server
MGC

Control Layer The Media Gateway operates on the user plane and converts media provided in one type of network to the format required in another type of network. The Media Gateway terminates the bearer control protocols and contains hardware devices for network access termination and media stream manipulation (e.g. tones sender, announcements, DTMF digit receiver, etc.). The Media Gateway is remote controlled by a Server (via GCP).

GCP

GCP

MGW

MGW

Connectivity Layer

A Server node is responsible for the set-up and control of connections within the core network The Media Gateway Controller function is the part of the Server node that controls the remote resources in the Media Gateway node.

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

MGW functions

Speech Coder function (SC) Transcoding in Core Network Echo Canceller function (EC) Tone Sender/Receiver function (TSR) Interactive Messaging function (IM) Multi Party Call function (MPC) Circuit Switched Data function (CSD)

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Protocols used in CN with Architectural Split

Call control protocol

Server
E.g. BICC (IAM, ACM, etc.)

Server
Gateway Control Protocol
GCP

Gateway Control Protocol

GCP

Bearer control protocol

E.g. Q.AAL2

MGW

Establish Request (ERQ)

MGW

Establish Confirm (ECF)

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Gateway Control Protocol (GCP) Used between Media Gateway controller and Media Gateway and allows the MGC to control the bearer in the MGW It is a master/slave protocol Based on ITU-T H.248, but coming from the internet world it uses concepts we are not used to: Context, Terminations, .

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Gateway Control Protocol

SERVER

SSV CHANGE TO SEIZE CALL CONTROL APPLICATION SEIZE SEIZE BOTHWAY ASYMETRICAL BOTHWAY THROUGH ASV1 ASV2 CONNECTION
ASV1 OPERATE GS SSV ASV2

CONRM

GCPH

Ctx$ ADD((T$)Mode SR) Ctx1 Ctx1 MODIFY ADD( Ctx1 Ctx1 ACCEPT(T2) ACCEPT(T2) (T$)Mode ACCEPT (T2)Mode (T1) inactive) SR

SEIZE MUP1

X
GS

MGW

SEIZE MUP2

T1

T2

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Bearer Independent Call Control Protocol

Used between servers (within the core network) when a bearer different than TDM is used. Successor of ISUP Independent from the bearer technology: Currently used with AAL2 and IP Messages look very similar to ISUP messages: IAM, ACM, .

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Q.AAL2

Q.AAL2

MGW

MGW

Q.AAL2 is a bearer control protocol that controls the bearer establishment and release between the MGWs. Q.AAL2 runs over ATM and is used for bearer control of ATM based core networks

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

IPBCP
BICC with tunneled IPBCP

Server
GCP with tunneled IPBCP

Server
GCP with tunneled IPBCP

IPBCP (Logical)

MGW

MGW

IPBCP (IP Bearer Control Protocol) is used as bearer control protocol in IP core networks
IPBCP messages are exchanged between MGWs tunneled via GCP and BICC CS2 messages
IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Core Network Major Functions

Major functions within the CN: -MGW Selection

-Transcoder Free Operations (TrFO)

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

MGW Selection
Select a MGW which is most suitable for a given call case -Optimal placement of the MGW in the network (place the transcoder at the edge of the network)

-Save capacity since encoded speech is transferred through the core network until the edge
-Use as less resources (MGWs) in the core network as possible

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

MGW Selection
Nc Bicc Iu RANAP MSC Server TSC Server N-ISUP
SGW

Mc GCP

Mc GCP

Mc GCP UTRAN (ATM) PSTN/ISDN PLMN (TDM)

Iu

T1 TRA

T3

T2

T3

T4

T4

MGW1

Iu
T1 TRA T2

MGW2

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

MGW Selection
Nc Bicc Iu RANAP MSC Server

IAM(fw) COT APM (MGW id)

TSC Server

N-ISUP
SGW

RAB assignment

Add Accept
Mc GCP

Setup
RAB ass. resp.

Call Proceeding

Add Accept

Mc GCP

IAM

Mc GCP UTRAN (ATM)

T1 TRA T2 T3 T4

Iu

PSTN/ISDN PLMN (TDM)

Establishment of AAL2 bearer AMR coded speech

Iu

MGW1

MGW2

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Trnascoder Free Operations TrFO

Contrary to GSM for UMTS access the transcoder is not placed at the RNC. Speech is sent encoded to the core network in order to save capacity and its responsibility of the CN to place the transcoder at the edge of the network.

In the optimum case, a call originating and terminating in UMTS access within the same Core Network no transcoder is used. In order to achieve this additional signalling procedures are required.

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Trnascoder Free Operations TrFO

Since both terminations handle AMR2 coded speech no Transcoder is seized by CELLO MGW

APM(AMR2,CodecList) IAM(Fw,CodecList) COT

MSC Server OoB Codec Negotiation BICC MSC Server

MSC compares codec list in IAM and CALL CONF and selects theCodec e.g AMR2

RANAP/NAS

CBC (GCP)

CBC (GCP)

RANAP/NAS

UE

UTRAN

RNC

MGW
CN Bearer

MGW

UE RNC UTRAN

Radio Bearer

Iu Bearer

Iu Bearer

Radio Bearer

Compressed Voice

Establish Bearer (AMR2 coded speech)

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Core Network migration scenario

PLMN STM based
A
MSC/ VLR
AXE10

GSM BSS

GSM BSS A
MSC/ VLR TSC
AXE10

HLR
AXE10

STM

STM TSC
AXE10

STM STM GMSC

AXE10

STM

STM

STM
MSC/ VLR GMSC
AXE10

STM

GSM BSS

MSC/ VLR TSC

AXE10

GSM BSS

STM

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

ATM TRUNKING
Some GSM nodes are collocated with ATM switches.
PLMN STM based
A
MSC/ VLR
AXE10

GSM BSS

GSM BSS A
MSC/ VLR TSC
AXE10

HLR
AXE10

STM

STM TSC
AXE10
AXD301

STM STM GMSC

AXE10

ATM

STM
ATM

STM

GSM BSS

MSC/ VLR GMSC

AXE10

AXD301

STM

AXD301

MSC/ VLR TSC

AXE10

GSM BSS

STM

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

UMTS access introduction

Q.AAL2 from RNC is terminated at the MSC.
PLMN STM based
A
MSC/ VLR
AXE10

GSM BSS

GSM BSS A
MSC/ VLR TSC
AXE10

HLR
AXE10

ATM

STM

UTRAN

Iu
STM TSC
AXE10
AXD301

STM STM GMSC

AXE10

ATM

STM
ATM

STM

GSM BSS

MSC/ VLR GMSC

AXE10

AXD301

STM

AXD301

MSC/ VLR TSC

AXE10

GSM BSS

STM

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

MGW introduction ATM based CN

Q.AAL2 from RNC is terminated at the MGW. MGW terminates STM traffic from BSC and to/from other networks
MGW
Cello

ATM

GSM BSS
STM

MSC/ VLR GMSC MGW

AXE10

Backbone ATM based

HLR
AXE10

UTRAN
ATM MSC/ VLR GMSC

Iu
ATM

STM STM ATM

ATM

MGW
AXE10

ATM

UTRAN

Iu
STM ATM ATM TSC MSC/ VLR GMSC
AXD301 AXD301 AXD301

MGW
Cello

ATM
ATM MGW
Cello

STM

STM

STM

STM MSC/ VLR GMSC TSC MGW

AXE10

MGW
AXE10

STM STM

GSM BSS

MGW

AXE10

STM

A GSM BSS
IXG/DG G.Viennas 2002-12-04 Rev A

STM

AXE SWDC

IP based CN
MGW
Cello

ATM

GSM BSS
STM

MSC/ VLR GMSC MGW

AXE10

Backbone IP based
HLR
AXE10

UTRAN
IP MSC/ VLR GMSC

Iu
ATM

STM STM ATM

IP

MGW
AXE10

IP

UTRAN

Iu
STM ATM IP
Router

MGW

IP IP

Cello

STM

STM

MGW
Cello

IP

TSC STM MSC/ VLR GMSC TSC MGW MGW

AXE10

IP
MSC/ VLR GMSC

STM

GSM BSS

A
STM

MGW
AXE10

MGW
Cello

A GSM BSS
IXG/DG G.Viennas 2002-12-04 Rev A

STM

AXE10

STM

AXE SWDC

Long Term Vision

MGW MGW
Cello

IPBSS

GSM BSS
MGW
Cello

Cello

Backbone ATM/IP based

HLR
AXE10

UTRAN
Router/ Switch ATM/IP

MGW
Cello Router/ Switch ATM/IP

UTRAN

MGW
Cello

MSC/VLR TSC/GMSC Server

AXE10

Router/ Switch ATM/IP

MGW
Cello

MSC/VLR TSC/GMSC Server

AXE10

MGW
Cello

GSM BSS

MGW
Cello

MGW
Cello

UTRAN

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

Thanks for your attention Questions?

IXG/DG G.Viennas 2002-12-04 Rev A

AXE SWDC

A Interface

BSC

BSSAP

MSC/VLR

BSSAP: is a protocol needed to support procedures for connection management, mobility management and radio resource management. It transfers signaling messages between MS and MSC/VLR and BSC and MSC/VLR. User data: i.e. speech or data are exchanged between BSC and MSC/VLR using a PCM link and the CIC (Circuit Identification Code) is used to correlate the signaling path with the respective PCM time slot.

IXG/DG G.Viennas 2002-12-04 Rev A