See

discussions, stats, and author profiles for this publication at: https://www.researchgate.net/publication/228854874

Challenges in interoperability and roaming

between LTE-Legacy core for mobility
management, routing, real time charging
Article January 2011

CITATION

READS

250

1 author:
Rajarshi Sanyal
Aalborg University
12 PUBLICATIONS 9 CITATIONS
SEE PROFILE

Available from: Rajarshi Sanyal

Retrieved on: 02 September 2016

2011 Technical Symposium at ITU Telecom World (ITU WT)

Challenges in Interoperability and Roaming

between LTE - Legacy core for Mobility
Management, Routing, Real Time Charging
Rajarshi Sanyal
Engineering and Operations Expert (Roaming and Signaling)
Belgacom International Carrier Services
rajarshi.sanyal@bics.com

interworking between these two domains. In this paper, we

attempt to bring out the possible solutions which can be
implemented in mobile networks or carrier networks which
will facilitate mobility, roaming and interoperations across the
two boundaries. For realising Voice Over LTE and
interworking with 2G/3G, actuating TDM break-out, the
initiatives of voLTE are mentionable. But this topic is not
specifically addressed in this paper.

Keywords: MME, PCRF, D2M/C, DIAMETER, SRVCC

One of the significant criteria for the
acceptability and reach of the LTE worldwide will be
based on its ability to seamlessly interoperate in the 2G/3G
networks. Interoperability in this case, implies that
subscribers from one or the other network should be able
to seamlessly roam for voice, SMS and data. This will
entail in actuating mobility and location management
across the two network domains, render all categories of
data and services, and to ensure the Real Time Charging.
The mode of operation for voice, SMS and Data is
philosophically different in LTE. So it is not only a
question of bridging two core network protocols for LTE
and legacy. The main challenge is also to synchronise the
two different operation models, adopted by LTE and
Legacy. In LTE, we have Home routing and Local
breakout. The voice and SMS interworking principle
implemented by LTE is chalk and cheese compared to
2G/3G. The charging and billing processes have
disparities. This paper attempts to address the key
challenges and identify the solutions for actuating
Interoperability across the LTE and the traditional
(2G/3G) Networks during roaming.

Abstract

II.LTE TO 2G/3G ROAMING LANDSCAPE

There are primarily three categories of LTE networks
1.

LTE Networks evolving from 2G/3G: We generally

see the co-existence of LTE and Legacy topologies.
Interworking and roaming can be attained by CS
Fallback whenever required. The other option is
SRVCC [8] . SRVCC provides the ability to
transition a voice call from the VoIP/IMS packet
domain to the legacy circuit domain.

2.

LTE only networks establishing roaming with 2G/3G

networks: For LTE only networks, inter-standard
roaming is essential if they need a worldwide
roaming coverage in 2G/3G networks[4]. The
interoperability principles for roaming and
interworking are discussed in this paper.

3.

For CDMA/TDMA networks, evolving to LTE, a

global roaming coverage with the existing 2G/3G
(only) Networks can be achieved by the
interoperability principles addressed in the following
sections.

1.INTRODUCTION
In the roaming world , the factors that contribute to service
assurance in the core network is to ensure that the operations
related to Mobility and Location Management and Real Time
charging are actuated flawlessly across the networks. For
roaming between LTE networks, there is a defined structure.
For enabling roaming across LTE and 2G/3G networks, the
standards are evolving. Worldwide 90 % of the GSM
networks are 2G/3G, so it is important to ensure roaming and

Copyright 2011 ITU - All rights reserved

116

GTP Traffic

III .KEY CHALLENGES IN MOBILITY MAN

NAGEMENT

S8:- The interface between Serviing Gateway (alike SGSN in

2G/3G) and PDN Gateway (alike GGSN in 2G/3G) carrying
GTP V2 traffic

In legacy core networks, we have the Mobile A

Application Part
where the mobility management related messages are
described. MAP [1] is used between the Visitedd Network and
the Home Network for the purpose of Mobility, Location
management and for authentication. This protoccol is based on
SS7. If conveyed on traditional TDM on E1/T1 links or over
SCTP as a transport protocol if SS7 over IP ((SIGTRAN) is
used.

DIAMETER for LTE

ol adapted for LTE [3] , it
According to Diameter Protoco
supports Mobility Management fo
or

However, in case of LTE core we do not see SS7 anymore.

The DIAMETER protocol has been adopted to support all the
possible operations supported in conventional M
MAP.

Diameter to Diameter interwo

orking (LTE LTE)

Diameter to MAP interworking (LTE2G/3G)

Diameter exchanges the data baseed on Attribute Variable Pairs

(AVPs), which encapsulates the type of request pertaining to
the type of application. There aree common AVPs and vendor
specific AVPs, which are defined
d in a Diameter agent in a so
called Dictionary. The AVPs which
w
are defined as per [3]
and which translates to the DIA
AMETER commands are in
Table 1. So as per the geneeral philosophy, AVPs are
application specific and vendor specific. Hence [3] defines
Diameter Application ID 167772
251 for the S6a/S6d interface
and 3GPP Vendor-ID 10415. As per
p the new CR of 1R 80 [5],
these two values are proposed fo
or the LTE Network Element
for enabling roaming called Diam
meter Proxy, which is like the
STP of a traditional network.

In a pure LTE to LTE roaming scenario, the interfaces that

play a major role with respect to the varrious network
operations are as follows. Fig 1. highlights the interfaces
relevant to roaming.

From theoretical perspective, itt is quite straightforward to

bridge the MAP to Diameter (as in Table 2). Below is a
proposed mapping for Diametter to MAP messages for
mobility / location management.
Fig 1: LTE Architecture and the interfaces

AVP
Code

Message

Command

Mobility Management

316

Update-Location-Request/Answer

ULR/ULA

317

Cancel-Location-Request/Answer

CLR/CLA

S6a:- It enables transfer of subscription and authentication

data for authenticating/authorizing (AAA innterface) user
access to the LTE N/W between MME and HSS over
DIAMETER protocol.

318

Authentication-Information-Request/An
nswer

AIR/AIA

319

Insert Subscriber Data-Request/Answerr

IDR/IDA

320

Delete-Subscriber-Data-Request/Answeer

DSR/DSA

321

Purge-UE-Request/Answer

PUR/PUA

322

Reset-Request/Answer

RSR/RSA

S6d:- AAA related information exchange betweeen SGSN and

HSS over DIAMETER protocol.

323

Notify-Request/Answer

NOR/NOA

Policy Control and Charging

Table 1: DIAMETER commandss for LTE

S9:- It provides transfer of (QoS) policy controol and charging

information based on DIAMETER protocoll between the
Home PCRF and the Visited PCRF in order too support local
breakout function

But for practical implementation

n, it is not only entails the
mapping the messages as per th
he Table 2. It is needed to
analyse and synchronise the releevant network processes and
the associated parameters.

117

Let us analyse the vital network processes in LTE and 2G/3G

network and identify the primary issues in complementing for
the purpose of roaming.

Mobility Management
The first message that we see in the core network during a
network contact by a UE is called the Location Update. We
see the same message in MAP and in DIAMETER. But lets
see closely the call flows.

Authentication
If we start with Authentication during Network Acquisition,
which is the prerequisite for the Location Update process, we
see that the authentication algorithm supported in legacy
networks is quite different from what is supported on LTE.

GSM MAP Location Update

For a 2G Network, the Authentication Algorithm is called

Comp 128.The triplets (SRES, RAND and Kc) that are
computed by the Mobile Station / Visited Network are
encapsulated in this MAP message and routed towards the
Home network.
For a 3G network, the authentication algorithm is called
milenage.
Now
there
will
be
Quintuplets
(XRES,RAND,Ck,Ik,AUTN) which will be transferred from
the VPLMN to the HPLMN over the MAP interface.
In 4G, ie LTE , the authentication principle is quite different.
The purpose of the EPS authentication and key agreement
(AKA) procedure is to provide mutual authentication between
the user and the network and to agree on a key KASME. The
EPS AKA procedure is always initiated and controlled by the
network. However, the UE can reject the EPS authentication
challenge sent by the network.

Fig 2. Location Update procedure for a SS7 MAP based

(2G/3G Network)

A partial native EPS security context is established in the UE

and the network when an EPS authentication is successfully
performed. During a successful EPS authentication procedure,
the CK and IK are computed by the USIM. CK and IK are
then used by the Mobile Station as key material to compute a
new key, KASME. KASME is stored in the EPS security
contexts of both the network and in the volatile memory of the
ME while attached to the network, and is the root for the EPS
integrity protection and ciphering key hierarchy. The
parameters in EPS authentication procedure are not supported
by MAP. Hence if a mobile subscriber from LTE only Home
Network needs to roam in 2G/3G network, the Visited
network will not be able to populate the 4G Authentication
parameters to be conveyed to Home Network. Also on the
other way, if a 2G/3G subscriber needs to roam in a LTE only
visited network (with a LTE capable handset), still the
authentication procedure required to be completed before the
actual Location Update procedure will be a problem as
Diameter does not support the authentication parameters
related to 2G/3G.

Fig

Location Update in LTE networks

The major differences between the 2 processes are as follows.
1.

2.

118

In GSM MAP, the ISD message brings the entire

subscriber profile. In case a single ISD is not sufficient,
multiple ISDs are invoked by the VPLMN. In case of
Diameter the subscriber profile is encapsulated in the
Location Update Answer. The Diameter ISD is used only
during modification of the subscriber profile initiated by
the HPLMN.
Hence an Intelligent Network Element in between the two
network domains (LTE and 2G/3G) should be able to
actuate MAP to DIAMETER conversion and to

3.

orchestrate the Location Update processees between the

two network topologies.
me charging, is
Mapping the parameters related to real tim
also a challenge. If you see the GSM M
MAP call flow,
notice that for a CAMEL enabled subscrriber, CAMEL
flags are downloaded by the HPLMN
N towards the
VPLMN. However CAMEL is not supported in LTE.
DIAMETER does not support the CAMEL
L flags. Hence
the CAMEL flags cannot be ported diirectly to any
equivalent DIAMETER parameters. So tthe conversion
between MAP and DIAMETER in such a scenario is a
problematic issue.
IV.

O
AND REAL TIME
V.KEY CHALLENGES IN POLICY CONTROL
CHARGING.

y Control model proposed by

The Online Charging and Policy
GSMA [7] during the LTE to LT
TE roaming scenario depends
upon the specific roaming scenariio. After we study the options
proposed for LTE to LTE roam
ming, we will investigate the
issues related to Real Time Charrging and Policy Control for
4G to 2G/3G roaming
Home Routing
(
4) the Visited-PCRF
In case of Home routing (Fig
communicates Home-PCRF for Policy and Charging related
information. As indicated in the figure below, the S9 and the
Gy Interfaces are the most relevant.
r
We see Diameter
messages for QOS and charrging characteristic related
information. This information is specific
s
to the service availed
at the VPLMN. This leg however does not carry the
information for the data volum
me for actuating Real Time
Charging. The Gy interface ass in the diagram below is
responsible for conveying chargin
ng information for the traffic
volume and call control based on Diameter RFC 3588.

KEY CHALLENGES IN MESSAGE ROU

UTING

In SS7 networks, we have the MTP / SCCP layeers which takes

care of routing. With MTP, we can have the pooint code based
routing, while with the SCCP layer we have thhe Global title
based routing.
Diameter is based on SCTP, which is a transporrt protocol and
does not have the necessary intelligence to take part in routing
related functionalities. Hence the Application layer directly
takes part in routing. In SS7, the STP
P houses the
configurations for SCCP analysis based onn the different
numbering plans, like E.214 or E.164. However Diameter
does not have any dedicated algorithm for analysing and
routing of the messages to the destination network. It is
purely based in the analysis of the variouus parameters
pertaining to the command and the AVP andd mapping the
same to the right destination IP address.
Hence the network element in the middle will be responsible
for enabling interoperability between the 2 doomains should
also be responsible for facilitating the routing beetween the two
domains. It should be intelligent enough too interpret the
parameters with respect to each scenario and thhen decide how
to route to the destination. This new Network E
Element can be
termed as Diameter Proxy.
Local Breakout
In case of Local breakout (Fig 5), the Visited and the Home
Network should have a special arrangementt to exchange
traffic volume and call control related informattion on the Gy
interface. This is because the breakout happens at the VPLMN
and the traffic never reaches the home network. So the PDN at
the visited network directly interacts with the Onnline Charging
System at Home Network to actuate Real Time ccharging.

Fig 4. S9 and Gy Interface in Hom

me Routing

119

MAP Message

Diameter Comman
nds

SendAuthenticationInfo

AIR/AIA

UpdateGprsLocation

ULR/ULA

CancelLocation

CLR/CLA

PurgeMS

PUR/PUA

InsertSubscriberData

IDR/IDA

DeleteSubscriberData

DSR/DSA

Reset

RSR/RSA

UpdateGprsLocationInfo

NOR/NOA

ActivateTraceMode

IDR/IDA

DeactivateTraceMode

DSR/DSA

Table 2 : MAP to Diameter mapp

ping
The solutions that we will discu
uss in this section is
based on the following scenarios :
1.
2.
3.
4.

Fig 5. S9 and Gy Interface during Locaal Breakout

It can be inferred now that for LT
TE to 2G/3G
roaming we will face 2 main issuess, whether we
follow Home Routing or Local Breakouut.
1.

No policy control functionality on 2G/3G. Hence

QOS and charging related Policyy enforcement
will not be possible.

2.

In case of Home rerouting as iin the current

discussion, the charging for all tyypes of traffic
(Voice, SMS, Data) will be done tthrough the Gy
Interface between PDN Gateway and Online
Charging System. In a 2G/3G netw
work the online
charging interface between the GG
GSN (analogue
of PDN gateway in LTE) is validd only for Data
charging. Data Charging in 3G nettworks can also
be seen to be implemented on CA
AMEL Phase 3,
though it is rare. Voice chargingg is based on
CAMEL.SMS charging is usuallly based on a
proprietary charging interface between the
SMSC and Real Time Charging ssystem. So we
can infer that the real time chharging model
followed by a LTE network aand a 2G/3G
network are widely apart, and wee may need an
intelligent Hub in the middle to briidge the gap.

LTE(VPLMN) to 2G/3G
G(HPLMN) roaming
2G/3G(VPLMN) to LTE
E(HPLMN) roaming
SMS Interworking (LTE
E to 2G/3G).
Diameter Routing with Diameter
D
Proxy

Roaming when VPLMN is 2G/3G

G and the HPLMN is
LTE
Diameter to MAP conversion is required in this
scenario. Subscriber latches on
o in the 2G/3G
Network, so the HSS need
ds to support the
authentication algorithm (Comp
p128 and Milenage
algorithm). For GPRS, PDN GW
G in the HPLMN
should implement the Gp interface towards the
2G/3G VPLMN.
ut the solutions with
The following section chalks ou
respect to the different network processes that were
n.
discussed in the preceding section
Authentication
ould be able to hold
The Diameter AIA command sho
the 2G/3G Authentication tripletts/quintuplets. When
the MAP to Diameter conversiion is actuated, the
authentication vectors needs to be carried from the
VPLMN to the HPLMN.
Mobility Management
After the Authentication is succcessful, the Location
Update process should follow the call flow as
indicated. We see an important new component
called the Diameter to MA
AP/CAMEL(D2M/C)
converter, which resides between
n the Visited and the
Home Networks. As discussed before
b
, there is no
Insert Subscriber Data on the Diaameter leg during the

VI. LTE TO 2G/3G ROAMING SOLUTIO

ONS
The mobility management related messages are
mapped between Diameter and MAP protocol in IR
80 CR following TS 29.272.

120

Location Update process. So the D22M/C needs to

generate the ISD messages accorrding to the
subscription data at the 2G/3G leg.

GTP Traffic
The PDN gateway at Home shoulld be able to support
GTP V1 control plane traffic.

Another important functionality of thee D2M/C is to

understand the Real Time charging profile of the
customer and to accordingly populatee the CAMEL
flags (when applicable) at the 2G/3G leeg.

G and the VPLMN is

Roaming when HPLMN is 2G/3G
LTE

2.. DIAMETER ULR

1. MAP Location Update

5. MAP Insert Subscriber Data
(Tele&Supplm
Services , O-CSI Flag)

3.. DIAMETER ULA

(Tele&Supplm
Services, 3GPP Charging
Characteristics)
HSS @ LTE
HPLMN

MSC/VLR
@2G/3G VPLMN
MAP/CAMEL to Diameter
Converter
Based on the OCS IP address
Derived from HSS, MAP/CAMEL 2 Diameter
converter generates a SCP E.164 address to
be populated in the O-CSI CAMEL Flag
accordingly. The CAMEL messages from the
MSC/VLR will be routed to this converter which
Orchestrates the CAMEL to DIAMETER
Conversion

4.Query too OCS

To deterrmine
Whetheer the
Custom
mer is
Pre or Posst Paid
& subscripttion data

Online
Charging
Database

This scenario can be realised viaa Local Breakout, if

the customer wishes to latch on
o in the Enhanced
UTRAN N/W. The agreement between the HPLMN
and VPLMN should be done accordingly.S6a to
MAP conversion should be avaailable for Mobility
Management. Legacy HLR at home should support
the Authentication parameters forr LTE (KASME) on
the GR+ interface.MME shall bee able to actuate the
mapping of the services.The MM
ME in VPMN can do
the mapping of the subscriptio
on data for Gn/Gp
SGSN provided by the HLR
R.Services regarding
Home routing will not work. For Real time charging,
the PDN Gateway at VPLM
MN needs to have
Diameter Interface towards thee Online Charging
System at HPLMN.
s
SMS Roaming and Interworking solutions

Fig 6. Solution for Location Update prrocess between

2G/3G Network and LTE

When a customer latches in on a LTE network and

require to invoke SMS to a 2G//3G Network during
roaming scenarios, or pure inteerworking scenarios,
there are 2 options for conv
veying Roaming /
Interworking SMS.

Real Time Charging

CAMEL to Diameter (RFC 3588) conversion is
realized in accordance to the call flow bbelow.

MS through the SG
Option 1: is to convey the SM
interface between a MME and an upgraded Rel 6
MSC.

MME

SS7/MAP
FW_SM

SS7/MAP
FW_SM

SG

MSC

STP

SMSC

Fig 8: SMS conveyance from LTE

L
to 2G/3G using
the SG interface between MME and
a upgraded MSC
Option 2: The other option is to
o send SMS on SIP
client as seen in IMS. The SIP to
o SS7 converter will
convert SIP to SMS in SS7 format and route it to the
SMSC.
Fig 7.CAMEL to Diameter conversioon for Online
Charging

121

MME

SIP 2 SS7

The choice of the technologies at the operator end

depends on the deployment and evolution pattern of
the LTE network .To realize a complete roaming
framework between the LTE and legacy technologies
for prepaid and postpaid customers, a set of
specifications need to be ev
volved. This paper
attempts to identify the core issuees and provide some
guidelines to the realize the plausible solutions.

SS7/MAP
FW_SM

SS7/MAP
FW_SM

SIP

STP

SMSC

The UE should have

IMSI Client to send
SMS on SIP

Fig 9: SMS conveyance from LTE too 2G/3G using

IMS client for SMS.

References :
1.
2.
3.
4.

ming scenarios
Diameter Routing Solutions in roam
with Diameter Proxy
As we discussed before, Diameter dooes not have a
dedicated layer like SS7 to initiate inteelligent routing
functionalities. The criteria to route to destination IP
addresses is based upon the anaalysis of the
parameters along with their numberinng plans in the
populated in the incoming message from the 2G/3G
network. International Carrier networrks can value
add by facilitating Diameter proxying aand interfacing
with a legacy roaming hub for MAP coonversions. The
proposed Diameter Proxy (Fig 10.) w
will cater to all
the routing requirements between LTE
E to LTE and
LTE to non LTE networks.

5.
6.
7.
8.

Mobile Application Part, GSM 09.02

3GPP TS 23.272
3GPP TS 29.272
GSMA PRD IR.88 "LTE Roaming
Guidelines"
HPIG Doc 23_011
CR to PRD IR.80 Tecchnical Architecture
Alternatives
for
Open
O
Connectivity
Roaming Hubbing Modeel.
3GPP TS 29.215
3GPP Standard 23.216
6 V 8.6. 2009-12:
Single Radio Voice Call Continuity
(SRVCC) (Release 8).

In the Bilateral Roaming world for LTE capable

networks, each MNO needs to establishh a S6a & S6d
connectivity / S9 for policy controll. Without the
Diameter Proxy, this needs to be a one to one
connectivity between the partner netwoorks. Diameter
Proxy can be a part of the existing Opeen Connectivity
roaming Hub (as proposed in the new CR for
IR80).They can be hosted by the carrieer networks, or
can be centralised by a large mobile opeerator group .
With the Diameter Proxy acting as thee roaming hub
[Ref 6], the MNO needs to establish a oone time single
connectivity to the Roaming Hub, with a single
contract. So the Diameter Proxy maay sit between
LTE capable networks to enable International
Roaming across all the members connnected to the
Roaming Hub , or through peering witth another LTE
capable Roaming Hub.
ugh Diameter Proxy
Fig.10: Diameter Routing throu
for
Roaming
and
Interworking

Conclusion
CS Fallback and SRVCC may nott be the only
answers to the issue of roaming andd interworking.

122