MPIRICAL

LTE Architecture

Reference Document

www.mpirical.com
LTE Architecture

LTE Architecture

Reference Document

MPI0001-00-01 Mpirical Limited, 2015 i

 LTE Architecture

Mpirical classes have been developed in accordance with the technical specifications
published by the 3GPP. As such the 3GPP have granted Mpirical Limited the right to use the
3GPP logo to identify specifications, compliant products and services.

First published by Mpirical Limited in 2015

Mpirical Limited, 2015
All rights reserved. No part of this book or accompanying software may be reproduced or
transmitted in any form by any means, electronic, mechanical, photocopying, recording, or
otherwise without the prior written consent of the publisher. Although every precaution has
been taken in the preparation of this book the publisher assumes no responsibility for errors
and omissions. Nor is any liability assumed for damages resulting from the use of the
information contained within.

ii Mpirical Limited, 2015 MPI0001-00-01

LTE Architecture

Contents

Introduction ............................................................................................................ 1
1.1 The Need for LTE .......................................................................................... 1
1.2 Migration from UMTS/HSPA ......................................................................... 1
1.3 LTE Releases and Features .......................................................................... 2
E-UTRAN Architecture .......................................................................................... 3
2.1 User Equipment ............................................................................................ 4
2.2 Evolved Node B ............................................................................................ 5
2.3 Home Evolved Node B .................................................................................. 6
2.4 E-UTRAN Interfaces and Protocols .............................................................. 6
EPC Architecture ................................................................................................... 7
3.1 Mobility Management Entity .......................................................................... 7
3.2 Serving Gateway ........................................................................................... 8
3.3 Packet Data Network Gateway ..................................................................... 9
3.4 EPC Interfaces and Protocols ....................................................................... 9
PCC Architecture ................................................................................................. 13
4.1 Policy and Charging Rules Function ........................................................... 13
4.2 Policy and Charging Enforcement Function................................................ 13
4.3 PCC Interfaces and Protocols ..................................................................... 13
IMS Architecture .................................................................................................. 14
5.1 Call Session Control Function ..................................................................... 15
5.2 Home Subscriber Server ............................................................................. 15
5.3 IMS Protocols .............................................................................................. 15

MPI0001-00-01 Mpirical Limited, 2015 iii

 LTE Architecture

iv Mpirical Limited, 2015 MPI0001-00-01

LTE Architecture

Figures

Figure 1 Global Mobile Data Traffic Forecasts (Cisco, 2013) ....................................... 1

Figure 2 Migration from UMTS/HSPA ........................................................................... 2

Figure 3 LTE Development ............................................................................................ 3

Figure 4 E-UTRAN Architecture .................................................................................... 4

Figure 5 LTE and LTE Advanced Channels .................................................................. 5

Figure 6 Evolved Node B Functions .............................................................................. 5

Figure 7 Femto Cell Architecture ................................................................................... 6

Figure 8 Uu Interface ..................................................................................................... 6

Figure 9 X2 Interface ..................................................................................................... 7

Figure 10 EPC Architecture ........................................................................................... 7

Figure 11 MME Functions.............................................................................................. 8

Figure 12 S-GW Functions ............................................................................................ 8

Figure 13 PDN-GW Functions ....................................................................................... 9

Figure 14 S1-MME Interface ....................................................................................... 10

Figure 15 S1-U Interface ............................................................................................. 10

Figure 16 S5/S8 Interface ........................................................................................... 10

Figure 17 S10 Interface ............................................................................................... 11

Figure 18 S11 Interface ............................................................................................... 11

Figure 19 SGs Interface .............................................................................................. 11

Figure 20 S3 Interface ................................................................................................. 12

Figure 21 S4 Interface ................................................................................................. 12

Figure 22 S6a Interface ............................................................................................... 12

Figure 23 PCC Architecture ......................................................................................... 13

Figure 24 Gx Interface ................................................................................................. 14

Figure 25 IMS Architecture .......................................................................................... 14

MPI0001-00-01 Mpirical Limited, 2015 v

 LTE Architecture

vi Mpirical Limited, 2015 MPI0001-00-01

LTE Architecture

Tables

Table 1 E-UTRA; User Equipment Radio Access Capabilities ...................................... 4

MPI0001-00-01 Mpirical Limited, 2015 vii

LTE Architecture

Introduction
Since the launch of GPRS (General Packet Radio Service) in 1999, there
have been countless predictions that mobile data volumes would increase
exponentially year on year. However, history tells us this was not the case
until the later part of the last decade with mobile data only really becoming
mainstream with the introduction of flat rate charging and the arrival of the
smartphone / app stores.
In 2010, eleven years after the launch of the world's first GPRS network, data
finally overtook voice as the largest contributor to total network traffic.

1.1 The Need for LTE

The growth in mobile data has continued apace over the past two years and
most analysts predict it will continue to do so for several years to come.

12

10
Exabytes/Month

0
2012 2013 2014 2015 2016 2017

North America Western Europe

Asis Pacif ic Latin America
Central and Eastern Europe Middle East and Af rica

Figure 1 Global Mobile Data Traffic Forecasts (Cisco, 2013)

In addition to the need to provide more network capacity, service providers

were also looking for the 4G networks to offer substantial cost savings over
and above the legacy 2G and 3G architectures. This drive to reduce both
CAPEX (Capital Expenditure) and OPEX (Operational Expenditure) was a
significant factor in the move towards a flat IP architecture incorporating only
a packet switched domain. As such all new services will be delivered over an
IP centric network, thereby negating the need to maintain a costly circuit
switched infrastructure.

1.2 Migration from UMTS/HSPA

In 2004, the 3GPP (Third Generation Partnership Project) began the
development of a fourth generation network with the formation of two study
groups. The LTE (Long Term Evolution) group was set up to investigate the
development of a new access network whereas the SAE (System Architecture
Evolution) group had responsibility over a new packet core network. Today

MPI0001-00-01 Mpirical Limited, 2015 1

 LTE Architecture

however, the term LTE is synonymous with the entire network and SAE has
tended to drift into archives of history! This concept is represented in Figure 2.

GMSC GGSN

MME PDN
GW
MSC SGSN System
Architecture S-GW
Evolution

BSC RNC Long Term

Evolution

BTS Node B eNB

MS UE UE

Figure 2 Migration from UMTS/HSPA

1.3 LTE Releases and Features

As with the 2G and 3G technologies of GSM, GPRS and UMTS, the 3GPP
continues to standardize new features and services through the various
releases. These can be found in detail at the 3GPP website however key
highlights for Release 8 onwards are summarized here.
Release 8
Release 8 introduced LTE for the first time and set about defining a new air
interface and packet core. Key highlights included:
300Mbps (Downlink) and 75Mbps (Uplink).
Latency down to 10ms.
New air interface - OFDMA (Downlink) and SC-FDMA (Uplink).
Support for MIMO antennas.
All IP core network.
Release 9
Release 9 brought about a number of refinements to features introduced in
Release 8. These included:
Introduction of LTE Femto Cells (HeNBs).
SON (Self Organizing Networks).
eMBMS (evolved Multimedia Broadcast and Multicast Service).
LCS (Location Services).

2 Mpirical Limited, 2015 MPI0001-00-01

LTE Architecture

Release 8 Release 10 Release 12

Release 9 Release 11 Release 13

Figure 3 LTE Development

Release 10
Release 10 provided a substantial increase in capacity through the
introduction of LTE Advanced. Key highlights included:
3Gbps (Downlink) and 1.5Gbps (Uplink).
Carrier aggregation of five 20MHz channels to a maximum of 100MHz.
Higher order MIMO antennas - 88 (Downlink) and 44 (Uplink).
Relay nodes to support HetNet (Heterogeneous Network).
Release 11
Release 11 built upon a number of services and features of Release 10
including:
Enhancements to carrier aggregation.
Introduction of new frequency bands.
Coordination of multipoint transmission and reception.
Advanced receivers.
Release 12
Still under development (Stage 3 Freeze - 2014), there are a number of work
items gaining traction. These include:
Enhanced small cells for LTE.
Interworking between LTE, Wi-Fi (Wireless - Fidelity) and HSPA.
Inter-site carrier aggregation.
LTE as a public safety network.

E-UTRAN Architecture
The LTE study group proposed a new access network termed the E-UTRAN
(Evolved - Universal Terrestrial Radio Access Network) and in so doing a new
air interface - E-UTRA (Evolved - Universal Terrestrial Radio Access). Strictly
speaking, the E-UTRAN does not include the mobile or UE (User Equipment)
but in the interests of clarity, it has been included here. The E-UTRAN
architecture is illustrated in Figure 4.

MPI0001-00-01 Mpirical Limited, 2015 3

 LTE Architecture

E-UTRA
Evolved
Packet Core
Uu
S1

X2
UE eNB

eNB

E-UTRAN

Figure 4 E-UTRAN Architecture

2.1 User Equipment

The mobile device, like that of UMTS, is termed the User Equipment and is
comprised of two distinct elements: the USIM (Universal Subscriber Identity
Module) and the ME (Mobile Equipment).

Mobile Equipment
In addition to the numerous capabilities a LTE mobile will be able to support, it
must also be able to support the new air interface or E-UTRA. In so doing, the
3GPP have defined a number of UE categories 1 which are summarized in
Table 1.

Max No. Of Support for

UE Max Uplink
Downlink Downlink 64QAM in
Category Data Rate
Data Rate Streams Uplink
1 10.3Mbps 1 5.2Mbps No
2 51.0Mbps 2 25.5Mbps No
3 102.0Mbps 2 51.0Mbps No
4 150.8Mbps 2 51.0Mbps No
5 299.6Mbps 4 75.4Mbps Yes
6 301.5Mbps 2 or 4 51.0Mbps No
7 301.5Mbps 2 or 4 102.0Mbps No
8 2998.5Mbps 8 1497.8Mbps Yes
Table 1 E-UTRA; User Equipment Radio Access Capabilities

In terms of radio spectrum, the mobile will be able to support various scalable
channels including: 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz and 20MHz whilst
operating in FDD (Frequency Division Duplex) and TDD (Time Division
Duplex) mode.

1
3GPP TS 36.306 - E-UTRA; User Equipment Radio Access Capabilities

4 Mpirical Limited, 2015 MPI0001-00-01

LTE Architecture

1.4MHz 3MHz 5MHz 10MHz

15MHz 20MHz

20MHz

100MHz (520MHz - LTE Advanced)

Figure 5 LTE and LTE Advanced Channels

Furthermore, mobiles supporting LTE Advanced features will be able to utilize

channel bandwidths of 100MHz. This is unlikely to be available as one
contiguous allocation of spectrum so LTE Advanced enables devices to
transmit and receive on up to five component carriers, each with a maximum
bandwidth of 20MHz. This technique is referred to as CA (Carrier
Aggregation).

2.2 Evolved Node B

Radio
Uplink Packet Data
Resource
Classification Compression
Management

User Data
Routing
Encryption

Figure 6 Evolved Node B Functions

The eNB (Evolved Node B) or base station is comprised of the following

functions:
Radio Resource Management - this process involves the allocation of
physical radio resources to the mobile for uplink and downlink
transmission. In terms of allocation, this also includes admission and
commitment of the requested radio resource or the downgrading of this
resource due to availability.
Uplink Packet Classification and QoS Policy Enforcement -
classification involves the marking of packets for uplink transport to
the core network. This process is based on subscription information or
through policies defined by the local service provider. Closely coupled
with packet classification is QoS Policy Enforcement; once a mobiles
QoS has been negotiated, then this must be enforced at the network
edge.
Data Compression - IP compression is performed using PDCP (Packet
Data Convergence Protocol). This process involves the compression of
the IP header.

MPI0001-00-01 Mpirical Limited, 2015 5

 LTE Architecture

User Data Encryption - encryption of the radio link is performed by the

eNB. It should be noted that this only protects the data across the air
interface.
Routing - this process involves the forwarding of control plane
signalling towards the MME (Mobility Management Entity). Likewise
User Plane traffic is routed to the S-GW (Serving Gateway).

2.3 Home Evolved Node B

Often discussed under the general topic of Femto Cells or Small Cells, the
3GPP have defined a specific base station in order to improve network
coverage and capacity within the SoHo (Small Office Home Office)
environment. Termed the HeNB (Home Evolved Node B), this device also
forms part of the E-UTRAN. The system may also include a HeNB-GW (Home
Evolved Node B - Gateway) which is designed in order to support large
numbers of HeNBs in the role of a concentrator. This concept is illustrated in
Figure 7.

HeNB
Uu GW
Evolved
S1 Packet Core

HeNB S1
UE

HeNB

Figure 7 Femto Cell Architecture

2.4 E-UTRAN Interfaces and Protocols

Uu Interface
The Uu interface contains both a Control and User Plane. The principle
control plane protocol is RRC (Radio Resource Control) whereas the user
plane is designed to transport IP datagrams. Both planes use the services of
PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), and
MAC (Medium Access Control).

Control Plane User Plane

RRC IP

PDCP PDCP

RLC RLC

MAC MAC

Layer 1 Layer 1

UE eNB

Figure 8 Uu Interface

X2 Interface
6 Mpirical Limited, 2015 MPI0001-00-01
LTE Architecture

The X2 interface connects two eNBs and supports both signalling and user
data. The control plane protocol operating across X2 is X2AP (X2 Application
Protocol) which utilizes the services of SCTP (Stream Control Transmission
Protocol) whereas the user plane utilizes GTP-U (GPRS Tunnelling Protocol -
User) to carry the IP datagrams.

Control Plane User Plane

X2AP GTP-U

SCTP UDP

eNB IP IP

Layer 2 Layer 2

eNB Layer 1 Layer 1

Figure 9 X2 Interface

EPC Architecture
The 3GPP also defined the EPC (Evolved Packet Core) as part of its
evolution or migration of cellular networks to a higher data rates, lower
latency, packet optimized system that supports multiple RAT (Radio Access
Technology). The focus of this work was in the packet switched domain, with
the assumption that it would support all services including voice, video and
multimedia. The EPC architecture is illustrated in Figure 10.

MME MME
S10

S11
S1-MME
S-GW PDN
GW

S1-U
S5/S8 SGi
E-UTRAN

Figure 10 EPC Architecture

3.1 Mobility Management Entity

The MME (Mobility Management Entity) is responsible for the following
functions:
NAS (Non Access Stratum) Signalling - NAS signalling includes EMM
(EPS Mobility Management) and ESM (EPS Session Management)
information. This includes procedures such as Location Updating and
Service Data Flow establishment etc. The MME is also responsible for
security signalling between itself and the mobile.

MPI0001-00-01 Mpirical Limited, 2015 7

 LTE Architecture

NAS Gateway
Idle State
Signalling Selection

Inter MME Authentication

Mobility

Figure 11 MME Functions

Idle State - whilst the mobile is in the ECM Idle State, its position is
tracked by the MME to the granularity of a Tracking Area. As well as
tracking the mobile, the MME will issue paging messages to the eNBs
associated with the relevant tracking area should data arrive for the
mobile.
Gateway Selection - on receipt of requests from a mobile to establish a
SDF (Service Data Flow), the MME selects the most appropriate
gateways to act as the S-GW and PDN-GW (Packet Data Network -
Gateway) respectively. This selection process may be based on criteria
such as the location of the mobile or through some method of load
balancing.
Inter MME Mobility - if a handover involves changing the point of
attachment within the EPC, this may involve an Inter MME handover. If
this is the case, the Serving MME will select the most appropriate
Target MME with which to conduct this process.
Authentication - the MME interacts with functions such as the HSS
(Home Subscriber Server) to obtain AAA (Authentication, Authorization
and Accounting) information with which to authenticate the subscriber.
Authentication in LTE is based upon AKA (Authentication and Key
Agreement). The AAA server will reside in the subscribers home
network. Consequently the MME must be capable of supporting these
procedures even in the roaming environment.

3.2 Serving Gateway

The S-GW is responsible for the following functions:
Mobility - the S-GW acts as the mobility anchor point for the User Plane
during handovers between eNB. Likewise it must also anchor mobility
for inter 3GPP handovers such as those towards legacy 3G network
elements. It should be noted that the PDN-GW anchors mobility when
non 3GPP interworking is invoked.
Data Buffering - when traffic arrives for a mobile in the ECM Idle state,
the S-GW must buffer this traffic prior to the mobile entering the ECM
Connected state. Transition to the ECM Connected state will be
through interaction with the MME and subsequent paging of the mobile.
Routing - traffic must be routed to the correct eNB or towards the PDN-
GW.
Lawful Interception - monitoring of VoIP (Voice over IP) and other
services may be conducted at the S-GW.

Lawful
Mobility Data Buffering Routing
Interception

Figure 12 S-GW Functions

8 Mpirical Limited, 2015 MPI0001-00-01

LTE Architecture

3.3 Packet Data Network Gateway

The PDN-GW terminates the SGi interface and is responsible for the following
functions:
Policy Enforcement - as part of the LTE security procedures, policy
information from the AAA server in the subscribers home network will
be downloaded to the EPC. The PDN-GW is responsible for monitoring
traffic characteristics on a subscriber by subscriber basis to ensure that
the agreed traffic policy is being adhered to.
Packet Filtering and Screening - deep packet inspection will be
conducted at the PDN-GW to ensure data such as Malware and
unauthorized data types are filtered at the network edge. This ensures
improved network and subscriber integrity.
Accounting - charging support is located at the PDN-GW to monitor
volumes and traffic types.
IP Address Allocation - IP addressing information for the mobile is
allocated by the PDN-GW. This is included as part of the initial bearer
establishment or when mobiles roam between access technologies.
The allocation of IP address information may be through 3GPP
protocols such as EPS bearer establishment or in the case of non
3GPP interworking, Mobile IP.
Lawful Interception - monitoring of VoIP and other services may be
conducted at the S-GW and PDN Gateway.

Packet
Policy
Filtering and Accounting
Enforcement
Screening

IP Address Lawful
Allocation Interception

Figure 13 PDN-GW Functions

NOTE It is now common to see the functions of the S-GW and PDN-GW combined into a single
physical entity. As such, the S5 interface will be transparent to the network.

3.4 EPC Interfaces and Protocols

S1-MME Interface
The S1-MME interface links the eNB and the MME and as such carries
control signalling between the E-UTRAN and the EPC. In so doing, it uses the
service of S1AP (S1 Application Protocol). However, it should be stated that
some protocols such as NAS pass across the S1-MME interface but terminate
on the mobile rather than the eNB.

MPI0001-00-01 Mpirical Limited, 2015 9

 LTE Architecture

Control Plane
MME
S1AP

SCTP

IP

Layer 2

eNB Layer 1

Figure 14 S1-MME Interface

S1-U Interface
The S1-U interface spans the link between the eNB and S-GW. This carries
user plane information using the services of GTP-U and the underlying IP
network.

S-GW User Plane

GTP-U

UDP

IP

Layer 2

eNB Layer 1

Figure 15 S1-U Interface

S5/S8 Interface
The S5 and S8 interfaces span the link between the S-GW and the PDN-GW;
either within the same PLMN (Public Land Mobile Network) as in the case of
S5, or in visited networks in the case of S8. These interfaces carry both
control and user plane information using the services of GTPv2-C (GPRS
Tunnelling protocol v 2 - Control) and GTP-U respectively.

PDN Control Plane User Plane

GW
GTPv2-C GTP-U

UDP UDP

S-GW IP IP

Layer 2 Layer 2

Layer 1 Layer 1

Figure 16 S5/S8 Interface

S10 Interface
The S10 interface carries control plane information between MMEs. This uses
the protocol GTPv2-C on top of the underlying IP network.

10 Mpirical Limited, 2015 MPI0001-00-01

LTE Architecture

Control Plane
MME
GTPv2-C

UDP

IP
MME Layer 2

Layer 1

Figure 17 S10 Interface

S11 Interface
The S11 interface carries the control plane signalling between the MME and
the S-GW. It also uses the protocol GTPv2-C and the underlying IP network.

Control Plane
S-GW
GTPv2-C

UDP

IP
MME Layer 2

Layer 1

Figure 18 S11 Interface

SGs Interface
The SGs interface connects the MME with a 2G or 3G MGCF (Media
Gateway Control Function) and in so doing supports the SGsAP (SGs
Application Part) protocol on SCTP. The interface is used to support the
Combined Attach procedure and other signalling associated with CSFB
(Circuit Switched Fallback) operation.

Control Plane
MGCF
SGsAP

SCTP

IP
MME Layer 2

Layer 1

Figure 19 SGs Interface

S3 Interface
The S3 interface links the MME with the SGSN (Serving GPRS Support
Node) in order to support interworking and PS (Packet Switched) handovers.
It utilizes the GTPv2-C protocol.

MPI0001-00-01 Mpirical Limited, 2015 11

 LTE Architecture

SGSN Control Plane

GTPv2-C

UDP

IP
MME Layer 2

Layer 1

Figure 20 S3 Interface

S4 Interface
Control Plane User Plane
S-GW
GTPv2-C GTP-U

SGSN UDP UDP

IP IP

Layer 2 Layer 2

Layer 1 Layer 1

Figure 21 S4 Interface

The S4 interface links the SGSN with the S-GW. It is used during PS
handovers between LTE and UMTS/GPRS and in so doing utilizes the
GTPv2-C protocol.

S6a Interface
The S6a interface connects the MME with the HSS which resides within the
IMS (IP Multimedia Subsystem). The application protocol on this interface is
Diameter.

Control Plane

Diameter
HSS
SCTP

IP
MME Layer 2

Layer 1

Figure 22 S6a Interface

SGi Interface
The SGi interface links the LTE network with the external world or specifically
the PDN-GW with the PDN (Packet Data Network). The interface is typically
based on IP and as such supports a vast array of IETF (Internet Engineering
Task Force) protocols.

12 Mpirical Limited, 2015 MPI0001-00-01

LTE Architecture

PCC Architecture
Given that all user plane communication across the LTE network will be via an
IP based packet switched network, PCC (Policy and Charging Control) is
necessary to ensure that the correct service is provided to the subscriber on a
packet flow basis. This is achieved through the use of a PCRF (Policy and
Charging Rules Function) and PCEF (Policy and Charging Enforcement
Function) which provide bearer network control regarding the QoS which
should be provisioned and applied for a given service data flow, charging
vectors and the rules which may be associated with these flows. The basic
architecture of the PCC is illustrated in Figure 23.

PCRF

Gx
PDN
GW
PCEF

Figure 23 PCC Architecture

4.1 Policy and Charging Rules Function

The PCRF is a policy decision point for subscriber data flows in the network.
Using inputs from other network nodes, the PCRF will formulate rules which
control how traffic flows (required QoS, restrictions, throttling, blocking, billing
etc) over the network down to individual subscriber granularity. The PCRF
passes these rules to the PCEF.

4.2 Policy and Charging Enforcement Function

Associated with the PDN-GW, the PCEF is a DPI (Deep Packet Inspection)
device responsible for the enforcement of rules which have been configured
statically or supplied to the PCEF dynamically from the PCRF. The PCEF sits
on the user plane and ensures that subscriber traffic flows are treated in
accordance with network policy e.g. implementing QoS, throttling traffic,
blocking traffic etc. Crucially, the PCEF will ensure that services are billed
accordingly.

4.3 PCC Interfaces and Protocols

Gx Interface
The Diameter based Gx interface utilises the "Diameter Credit Control"
application. The messages found on the Gx interface are largely associated
with the management of the IP-CAN (IP Connectivity Access Network)
sessions, such as during the establishment of a Default EPS Bearer or
triggering of a Dedicated EPS Bearer. As part of this, the Gx interface is used
to push rules from the PCRF to the PCEF, as well as facilitate event reporting
from the PCEF to the PCRF.

MPI0001-00-01 Mpirical Limited, 2015 13

 LTE Architecture

User Plane
PCRF
Diameter

SCTP

IP
PCEF Layer 2

Layer 1

Figure 24 Gx Interface

IMS Architecture
For seamless mobility and service delivery to be successful, a viable
architecture must be established to ensure that a subscribers services can be
delivered to them irrespective of their terminal, access network and core
network connectivity. This may be within the home network or on a visited or
roamed network. In order to achieve this, the session signalling must be
independent of the underlying bearer network to enable it to provide a
consistent interface between the terminal / mobile and the AS (Application
Server).
As illustrated in Figure 25, this abstraction of service management is
facilitated through the introduction of a service layer that extends across all
functions involved in the delivery of services. This encompasses the AS, that
provides service and session control, the CSCF (Call Session Control
Function) that provides a SIP (Session Initiation Protocol) Proxy function and
the HSS that provides subscription, security and mobility information.

HSS

Application Servers
I S P
CSCF CSCF CSCF

PDN
GW

LTE
(IP-CAN)

UE

Figure 25 IMS Architecture

14 Mpirical Limited, 2015 MPI0001-00-01

LTE Architecture

5.1 Call Session Control Function

The CSCF controls the session between the mobile and the services that it is
accessing. This relates to both mobile originated and mobile terminated
sessions. Moreover, in supporting the session, the CSCF will interact with AS
such as call servers, media servers, voice mail servers etc, that will provide
the service logic which will ultimately dictate how services are delivered to the
user.

P-CSCF
The P-CSCF (Proxy - Call Session Control Function) acts as the ingress and
egress point to and from a service provider's IMS domain with respect to the
IMS client. The P-CSCF has a large number of responsibilities, including:
onward routing of registration and session requests to the correct nodes in the
network, ensuring the S-CSCF (Serving - Call Session Control Function) is
kept updated on the access network the subscriber is using, providing session
information to the PCRF and maintaining a secure connection with the client
device.

I-CSCF
The I-CSCF (Interworking - Call Session Control Function) is responsible for
onward routing of SIP messages to the appropriate S-CSCF for a given
subscriber. This routing capability is utilized in specific scenarios only, such as
during registration in order to assign or ascertain the S-CSCF which should be
used. Routing SIP requests arriving from other SIP networks is also a
responsibility of the I-CSCF.
The I-CSCF queries the HSS in order to discover the S-CSCF a particular
subscriber has been assigned to.

S-CSCF
The Serving - Call Session Control Function is the primary node in the IMS
responsible for session control. Subscribers will be allocated a S-CSCF for
the duration of their IMS registration in order to facilitate routing of SIP
messages as part of service establishment procedures. Consequently, the S-
CSCF will download a subscriber profile from the HSS at the time of
registration, which allows the S-CSCF to ascertain which Application Server
any service requests should be sent to. The S-CSCF will also be involved in
breakout to the PSTN, if this is supported.

5.2 Home Subscriber Server

The HSS is the master database for a given subscriber, acting as a central
repository of information for network nodes. Subscriber related information
held by the HSS includes user identification, security, location and
subscription profiles. The HLR (Home Location Register) is a functional
element of the HSS.

5.3 IMS Protocols

The signalling protocols to coordinate service delivery are SIP and Diameter.
SIP is used as the common protocol interface between the AS, CSCF and
terminal whereas Diameter is used as a common interface between the HSS
and IMS functions. It should be stated that behind the HSS the various
databases that comprise this function use their generic protocols. These

MPI0001-00-01 Mpirical Limited, 2015 15

 LTE Architecture

include MAP (Mobile Application Part), DHCP (Dynamic Host Configuration

Protocol), DNS (Domain Name System) etc.
Ultimately, the IMS moves away from the stovepipe approach to service
delivery by allowing all services to utilize a common underlying architecture.

16 Mpirical Limited, 2015 MPI0001-00-01

LTE Architecture

MPI0001-00-01 Mpirical Limited, 2015 17

 LTE Architecture

18 Mpirical Limited, 2015 MPI0001-00-01

 LTE Architecture

Glossary

3GPP (Third Generation Partnership LCS (Location Services)

Project) LTE (Long Term Evolution)
AAA (Authentication, Authorization and MAC (Medium Access Control)
Accounting) MAP (Mobile Application Part)
AKA (Authentication and Key Agreement) ME (Mobile Equipment)
AS (Application Server) MGCF (Media Gateway Control Function)
CA (Carrier Aggregation) MME (Mobility Management Entity)
CAPEX (Capital Expenditure) NAS (Non Access Stratum)
CSCF (Call Session Control Function) OPEX (Operational Expenditure)
CSFB (Circuit Switched Fallback) PCC (Policy and Charging Control)
DHCP (Dynamic Host Configuration PCEF (Policy and Charging Enforcement
Protocol) Function)
DNS (Domain Name System) PCRF (Policy and Charging Rules
DPI (Deep Packet Inspection) Function)
eMBMS (evolved Multimedia Broadcast P-CSCF (Proxy - Call Session Control
and Multicast Service) Function)
EMM (EPS Mobility Management) PDCP (Packet Data Convergence
eNB (Evolved Node B) Protocol)
EPC (Evolved Packet Core) PDN (Packet Data Network)
ESM (EPS Session Management) PDN-GW (Packet Data Network -
E-UTRA (Evolved - Universal Terrestrial Gateway)
Radio Access) PLMN (Public Land Mobile Network)
E-UTRAN (Evolved - Universal Terrestrial PS (Packet Switched)
Radio Access Network) RLC (Radio Link Control)
FDD (Frequency Division Duplex) RRC (Radio Resource Control)
GPRS (General Packet Radio Service) S1AP (S1 Application Protocol)
GTP-U (GPRS Tunnelling Protocol - User) SAE (System Architecture Evolution)
GTPv2-C (GPRS Tunnelling protocol v 2 - S-CSCF (Serving - Call Session Control
Control) Function)
HeNB (Home Evolved Node B) SCTP (Stream Control Transmission
HeNB-GW (Home Evolved Node B - Protocol)
Gateway) SDF (Service Data Flow)
HetNet (Heterogeneous Network) SGsAP (SGs Application Part)
HLR (Home Location Register) SGSN (Serving GPRS Support Node)
HSS (Home Subscriber Server) S-GW (Serving Gateway)
I-CSCF (Interworking - Call Session SIP (Session Initiation Protocol)
Control Function) TDD (Time Division Duplex)
IETF (Internet Engineering Task Force) UE (User Equipment)
IMS (IP Multimedia Subsystem)

MPI0001-00-01 Mpirical Limited, 2015 19

 LTE Architecture

USIM (Universal Subscriber Identity Wi-Fi (Wireless - Fidelity)

Module) X2AP (X2 Application Protocol)
VoIP (Voice over IP)

20 Mpirical Limited, 2015 MPI0001-00-01

 MPIRICAL

Contact Us )))
Tel: +44 (0) 1524 844669
Email: enquiries@mpirical.com

Campus Locations
London, Dubai, Delhi, Hong Kong

www.mpirical.com