LTE TRAFFIC BREAKOUT

LIPA-SIPTO OVERVIEW
APR 25 ,2018

Amaresh Prasad Grahacharya

Architect
References

The following 3GPP Release 10 Technical specification for

Reference of LIPA and SIPTO.

 3gpp 23.829: Technical Specification Group Services and

System Aspects;Local IP Access and Selected IP Traffic
Offload (LIPA-SIPTO).
 3GPP TS 22.220: Service requirements for Home NodeBs and
Home eNodeBs
 3GPP TS 22.101:Service Aspects & Service Principles for
UMTS & LTE.
ABBREVIATIONS
 LIPA: Local IP Access
 SIPTO: Selected IP Traffic Offload
 H(e)NB:Home EnodeB
 RAN: Radio Access Network
 E-UTRAN: Evolved UTRAN
 SGW: Serving Gateway
 PGW:Packet data Network Gateway
 MME:Mobility management Entity
 SGSN:Serving GPRS Support Node.
 SEGW: Security Gateway.
Introduction

As connected device penetration increases globally, more and

more users are using their mobile devices not just for voice but
also for data services, As a result many operators are faced with
bandwidth and network capacity limitations
On the access network side, the introduction of HNBs ensures
efficient usage of radio spectrum by allowing home users to
access the network through the HNB using a local IP backhaul
link to the core network.
However, this puts an increasing amount of stress on core
network nodes such as SGSN and GGSN since more HNBs
connected to the core network means that these nodes have to
handle exponentially higher traffic. Hence a traffic breakout is
recommended in the form of LIPA-SIPTO.
Advantages of LIPA-SIPTO

 Reduced Network Congestion

 Better quality experience of QOS .
 Optimal utilization of resources and improved revenue.
 Reduce Service Cost.
 Breakout is performed without end user intervention so
transparently services can be given to subscriber.
LOCAL IP ACCESS(LIPA)

 Local IP Access provides access for IP capable UEs

connected via a H(e)NB (i.e. using H(e)NB radio access) to
other IP capable entities in the same residential/enterprise IP
network.
 Data traffic for LIPA is expected to not traverse the mobile
operator"s network except mobile operator network
components in the residential/enterprise premises.
 Signaling traffic for LIPA will continue to traverse the mobile
operator network.
LOCAL IP ACCESS(LIPA)
General Requirements for LIPA
 Simultaneous access from a UE to the mobile operator"s core
network and LIPA to a residential/enterprise IP network shall be
supported.
 LIPA traffic shall be routable only between the UE, H(e)NB and
other entities within the residential/enterprise IP network.
 LIPA shall not affect services running in parallel for the same UE.
 The mobile operator shall be able to configure the H(e)NB to
enable/disable LIPA .
 A UE shall be able to use LIPA in a visited network subject to
roaming agreement between mobile operators.
 The H(e)NB subsystem shall allow the mobile operator to collect
fault management information related to LIPA for each H(e)NB.
LIPA Scenarios
LIPA breakout is performed in the same residential/enterprise
IP network. Figure below illustrates this breakout at a Local GW
(L-GW) in the residential/enterprise IP network.
SIPTO (Selected IP Traffic Offload)

 SIPTO function enable an operator to offload certain type of

traffic to Service providing node that is closed to UE in
ACCESS network.
 In LTE, SIPTO over RAN is possible be selecting S-GW and P-
GW that is geographically closest to UE.
 General Requirements for SIPTO
The following requirements apply to Selected IP Traffic Offload:
 The mobile operator may enable/disable SIPTO on a per UE per
defined IP network basis (e.g. based on tariff, subscription type etc.).
 It shall be possible for IP traffic of a UE associated with a particular
defined IP network to be offloaded while IP traffic of that same UE
associated with other defined IP network(s) is not offloaded.
 Offloading selected IP traffic for a UE shall not affect services running
in parallel for the same UE.
 It shall be possible for the mobile operator to collect traffic and
signalling performance measurements related to SIPTO for each
user.
 SIPTO shall support mobility within the macro network. Any
interruption to the data flow during mobility within the macro network
shall be minimised.
General Requirements for SIPTO CONTD …
 Selected IP Traffic Offload may also support mobility during the
following mobility events:
mobility between the macro network and H(e)NBs.
mobility between H(e)NBs.
Any interruption to the data flow during both these mobility
events shall be minimised.

 The mobile operator shall be able to enable/disable Selected IP

Traffic Offload for certain parts of the network.
 SIPTO Scenarios
For SIPTO two types of breakout architectures are distinguished:
 Architectures with breakout "at or above RAN" (covering macro
and some H(e)NodeB SIPTO scenarios).
Architectures with breakout "in the residential/enterprise IP
network" (covering LIPA and some H(e)NodeB SIPTO scenarios).
In addition, SIPTO for the Home (e)NodeB Subsystem may
support the following three scenarios:
Scenario 1: Home (e)NodeB Subsystem and backhaul are
provided by the same operator;
Scenario 2: Home (e)NodeB Subsystem and backhaul are
provided by different operators;
Scenario 3: Local Breakout point (L-PGW) for LIPA/SIPTO is
located in a private address domain, e.g. behind a NAT gateway
SIPTO Scenarios CONTD …
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO

Architectural principles:
The following architectural principles apply to all LIPA-SIPTO
solutions:
For traffic going through the mobile operator's Core Network,
the SGW/SGSN User Plane functions are located within the
Mobile Operator's Core Network.
Mobility management signalling between the UE and the
network is handled in the Mobile Operator's Core Network.
Session management signalling (bearer setup, etc.) for LIPA,
SIPTO traffic and traffic going through the mobile operator's Core
Network terminates in the Mobile Operator's Core Network;
Reselection of a UE's offload point for SIPTO traffic that is
geographically/topologically close to the user shall be possible
during idle mode mobility procedures.
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…

Solution 1 – LIPA and SIPTO solution based on traffic breakout

performed within H(e)NodeB using a local PDN connection
Applicability:
This solution supports the following scenarios:
 Local IP access for HNB and HeNodeB Subsystem
 Selected IP traffic offload for HNB and HeNodeB Subsystem
 This solution is applicable for breakout "in the
residential/enterprise IP network".
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…
Architecture variant 1 for LIPA
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…

Architecture variant 2 for LIPA

 ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…
Architecture variant 2 for LIPA/SIPTO
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…

Solution 2 – LIPA and SIPTO at H(e)NodeB by NAT.

Applicability:
This solution supports the following scenarios:
 Local IP access for HNB and HeNodeB Subsystem.
 Selected IP traffic offload for HNB and HeNodeB Subsystem.

This solution, implemented by an Offload Processing Module

(OPM), is applicable for breakout "in the
residential/enterprise IP network".
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…
Solution 3 – SIPTO at Iu-PS
Applicability:
This solution supports the following scenario:
 Selected IP Traffic Offload for UMTS macro
 Selected IP Traffic Offload for HNB subsystem.

This solution is applicable for breakout "at or above RAN".

ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…
Solution 4: - SIPTO solution based on local PDN GW selection.
Applicability:

This solution supports the following scenarios:

 Selected IP traffic offload for macro network
 Selected IP traffic offload for Home (e)NodeB subsystem

This solution is applicable for breakout "in the

residential/enterprise IP network" and breakout "at or above
RAN".
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…
 ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…

Solution 5: - Local Gateway based Architecture.

Applicability:
This solution supports the following scenarios:
 Local IP Access for H(e)NodeB subsystem
 Selected IP Traffic Offload for H(e)NodeB subsystem
 Selected IP Traffic Offload for macro network
The solution applies to both types of approaches: with separate
APNs for SIPTO and non-SIPTO traffic, and also with common
APN(s) for SIPTO and non-SIPTO traffic.
This solution is applicable for breakout "in the
residential/enterprise IP network".
.
ARCHITECTURAL SOLUTIONS FOR LIPA-SIPTO
CONTD…
MESSAGE FLOW - LIPA PDN connection establishment
S1 Release procedure
Message Flow – UE Triggered Service Request

UE Triggered Service Request procedure

Message Flow – PAGING triggered by HeNodeB