Mobility and Roaming

Diplomado en Telecomunicaciones y Tecnologas de la
Informacin con mencin en Comunicaciones Inalmbricas
Mobility and Roaming

Mobility: Identities GERAN/UMTS

Mobility
As the user terminals are not fixed to certain positions, the network must keep track on where
the mobile is located. The system must at least be capable of knowing the geographical area
in which the subscriber is located. As in GSM networks, UMTS has a cellular architecture that
allows the network to identify the subscriber.
The Home Location Register (HLR) is the central database

that stores information on the subscriber, such as the IMSI
and MSISDN. The HLR also stores information on which
serving MSC and SGSN the subscriber can be found.
Also in the HLR we store information on the
subscriber's service profile. In other words,
we have a record of the different services
(teleservices, supplementary and packet
services) that the subscriber can/cannot use.

Mobility : UTRAN registration areas
UTRAN Registration Area (URA).

Mobility: Location updating

As the network maintains three layers of information on the subscriber's location
(LA, RA and URA), there are multiple procedures used to track the subscriber's
movements. In practice, there are three basic types of location update procedures:
Location registration (power on / cell attach)
Movement between area
Periodic update
These are explained in more detail in the forthcoming pages. In a GSM network
the BSC took no responsibility for mobility management; instead the mobile would
contact the core networks directly to inform about a change in location.
In UMTS, the situation is different as the RNC not only keeps information on which
subscribers are in which URA, but is also responsible for the location updating to
the core network.

Mobility: Paging the subscriber

From the HLR, the network is able to determine at the very least in which location area/routing area the
subscriber is located. The network (e.g. MSC) will contact the MSC/SGSN serving that area and request
contact to the mobile. The VLR/SGSN will then send a paging message, which contains the ID of the
subscriber on a dedicated channel in the air interface. A mobile in idle mode is always listening to this
channel.

Mobility: Roaming in another network

When a subscriber is in a foreign network, the procedures are the same.
When the subscriber registers in the visiting network, it will in turn contact
the home network (remember that part of the IMSI code specifies the home
network). If the two operators have a roaming agreement and the
subscriber is valid, the subscriber information is copied into the serving
VLR of the MSC and the information on the subscriber is stored in the
HLR.
Every VLR in the world has a unique address. As a subscriber moves
from one network to another, the location updating proceeds as normal.
The HLR is always informed of the unique VLR, in which the subscriber
was last seen.

Mobility: Roaming in another network

Mobility: Management Procedures

There are several different mobility management procedures, some of which have
been mentioned in this module. The following is a short list of UMTS specified
procedures. In the following chapter we will look at some of the procedures in their
context of the session management layer:
Location registration (CS and PS)
Location update (CS)
IMSI attach/detach (CS)
Routing area update (PS)
Cell attach/detach (PS)
Location info retrieval (CS and PS)
Paging (CS)
Paging (PS)
Authentication procedure (CS/PS)
Ciphering procedure (CS/PS)
UE identity checking (CS/PS)
UE hardware (IMEI) checking (CS/PS)

Mobility : LTE
EPS mobility management comprises functions and procedures that maintain the
connectivity between UE and EPS as the UE moves between the coverage areas
of different base stations or access networks. As far as possible, seamless mobility
is provided so that the mobility is transparent to UEs and the applications they use.
For applications that require it, the mobility is lossless. In other words, the packet
loss probability is very low.
Mobility Scenarios
LTE Intra-RAT mobility comprises:
Intra-eNB mobility (handover between cells within a certain eNB)
Inter-eNB mobility (handover between adjacent eNBs).
Inter-RAT mobility comprises:
mobility between LTE and other 3GPP RATs (GERAN or UTRAN)
mobility between LTE and non-3GPP RATs (such as WLAN, WiMAX or 3GPP2
access network (HRPD))

Mobility: LTE Areas and Identities
TS 23.401 version 11.5.0
A number of identities have been brought forward into LTE from 2G/3G networks. A
few, however, are newly defined for LTE.

Mobility: LTE Areas and Identities
TS 23.401 version 11.5.0
TAs (Tracking Areas)
The TA is a defined group of radio cells (much like the location areas or routing areas of earlier
networks), which may overlap.
The size of the TA depends on the expected number of idle-mode UEs in any particular area.
The dimensioning goal would be to reduce the amount of TAU signalling seen in any area and
to balance this against the amount of paging load required. Generally speaking, larger TAs will
reduce the amount of update signalling, but may increase the required paging load across the
TA. The actual size of the TA will therefore be a matter of system optimisation.

Mobility: Network Identifiers in LTE

The PLMN ID (Public Land Mobile Network Identity) identifies the network itself and is composed
of the MCC (Mobile Country Code) and MNC (Mobile Network Code). The MCC identifies the
country in which the PLMN is located while the MNC identifies the PLMN in that country. The
eNB-ID identifies a particular eNB within a network. A Global eNB ID identifies an eNB globally,
and comprises MCC, MNC and eNB-ID.
These comprise the TAI (Tracking Area Identity) and the ECGI (E-UTRAN Cell Global Identifier).
TAI is used to identify a particular tracking area within the E-UTRAN. It is constructed from the
MCC, MNC and TAC (Tracking Area Code). The TAC is a fixed-length code of 2 octets that
identifies a tracking area within a PLMN. .
The ECGI is globally unique and comprises the PLMN-Id and the 28-bit ECI (E-UTRAN Cell
Identity).

Mobility: UE/Subscriber Identifiers

The following identifiers are associated with the UE and the USIM and uniquely identify either the
subscriber or the equipment.
IMEI (International Mobile Equipment Identity)
IMSI (International Mobile Subscriber Identity)
TMSI (Temporary Mobile Subscriber Identity)
M-TMSI (MME Temporary Mobile Subscriber Identity)
S-TMSI (SAE Temporary Mobile Subscriber Identity)
GUTI (Globally Unique Temporary Identifier)
TS 23.003
The subscriber will also have their own unique telephone number, the MSISDN (Mobile
Subscriber ISDN Number).
The IMEI comprises the 8-digit TAC (Type Allocation Code), the 6-digit SNR (Serial Number), and
a one-digit CD (Check Digit) or SD (Spare Digit).
The IMSI, stored on the USIM (Universal Subscriber Identity Module), is unique and is allocated
to each mobile subscriber in the system. It comprises the MCC, the MNC and the MSIN (Mobile
Subscriber Identification Number (MSIN), which identifies the subscriber within a PLMN. For
user-security purposes, a TMSI (Temporary Mobile Subscriber Identity) may be allocated to
subscribers roaming onto the network.


A TMSI only has local significance (in LTE, within an MME and the area controlled by an MME).
The structure and coding of it is not defined, but can be chosen by agreement between operator
and manufacturer. The TMSI consists of 4 octets. The TMSI is only ever allocated only in
ciphered form, and is stored on the USIM.
The M-TMSI, which is new for LTE, identifies a user between the UE and the MME. The
relationship between M-TMSI and IMSI is known only in the UE and in the MME. It is 32 bits in
length.


The GUTI provides an unambiguous identification of the UE without revealing its or
the users IMSI in the EPS. It also uniquely identifies the MME that allocated the
GUTI, and the network where that MME resides. It can be used by the network and
the UE to establish the UE's identity during signalling between them in the EPS.
The GUTI comprises two components: the M-TMSI and the GUMMEI (Globally
Unique MME Identity), i.e. the identity of the MME that allocated the GUTI.
The S-TMSI is a shortened version of the GUTI, and is used to enable more
efficient radio signalling procedures including service request and paging. The
mobile is paged with the S-TMSI. It comprises the MMEC (MME Code) and the MTMSI.

Mobility: MME Identifiers

A number of identifiers are associated with the MME. These are:
MMEC (MME Code)
MMEGI (MME Group Identifier)
MMEI (MME Identity)
GUMMEI (Globally Unique MMEID)
The MMEC uniquely identifies the MME within all the pool areas. As well as being
unique within pool areas, the MMEC must be unique within overlapping pools. This
code is 8 bits in length.
The MMEGI is allocated to group of MMEs and is 16 bits in length.
The MMEI uniquely identifies the MME within a network, and comprises the MMEID
and the MMEC.
The GUMMEI comprises the PLMN ID (i.e. MCC and MNC) and the MMEI, thereby
uniquely identifying an MME throughout all networks.

Mobility: EPS Bearer Identity

An EPS bearer identity is allocated by the MME, and uniquely identifies an EPS
bearer for one UE accessing via the E-UTRAN.
There is a one-to-one mapping between the EPS radio bearer and EPS bearer and
their respective identities. This mapping is made by the E-UTRAN.

Mobility
: LTE Mobility Scenarios
EPS mobility management comprises functions and procedures that maintain the
connectivity between UE and EPS as the UE moves between the coverage areas
of different base stations or access networks. As far as possible, seamless mobility
is provided so that the mobility is transparent to UEs and the applications they use.
For applications that require it, the mobility is lossless. In other words, the packet
loss probability is very low.
Mobility Scenarios
LTE Intra-RAT mobility comprises:
Intra-eNB mobility (handover between cells within a certain eNB)
Inter-eNB mobility (handover between adjacent eNBs).
Inter-RAT mobility comprises:
mobility between LTE and other 3GPP RATs (GERAN or UTRAN)
mobility between LTE and non-3GPP RATs (such as WLAN, WiMAX or 3GPP2
access network (HRPD))

Mobility Scenarios
Identities for
GERAN/UMTS
Mobility scenarios for LTE/EPC

Identities for LTE

Interworking with 2G/3G Access

The EPC is not backwards-compatible with 2G/3G network architecture, but it does support
interworking with existing 2G/3G packet core nodes. This interoperability is provided by the S3
and S4 interfaces.
The role of S3 is to support user and bearer information exchange between the SGSN and the
MME, as the terminal is moving from one access type to the other. User context, negotiated
QoS and bearer information is exchanged between the nodes so that the new serving MME or
SGSN receives the necessary information about the session. The S3 interface is based on the
Gn interface designed for 2G/3G packet core architecture to support mobility between SGSN
nodes, and as such is based on GTP.
The S4 interface is associated with the session user plane and supports packet data transfer
between the SGSN and the SGW, which acts as a mobility anchor point within the EPC
architecture. S4 is based on the Gn interface, defined between the 2G/3G Packet Core SGSN
and GGSN nodes, and is also based on GTP.
Interworking can exist between the EPS and 3GPP 2G and/or 3G SGSNs that provide only Gn
and Gp interfaces but no S3, S4 or S5/S8 interfaces. These Gn/Gp SGSNs provide no
functionality that is introduced specifically for the EPS or for interoperation with the E-UTRAN.
Interoperation scenarios for operating E-UTRAN with a PLMN maintaining Gn/Gp SGSNs are
supported only with a GTP-based S5/S8.

Interworking with 2G/3G Access

S4 interface is associated with the
session user plane and supports packet
data transfer between the SGSN and
the SGW
S3 is to support user and bearer information

exchange between the SGSN and the MME

Trusted and Untrusted Non-3GPP Accesses
Access mechanisms are provided for both trusted and untrusted non-3GPP accesses, i.e.
accesses from networks that use access technologies that are not specified by 3GPP. These
include WiMAX, CDMA2000, Wi-Fi, and fixed-line access networks. Which access networks
are trusted and which are not is HPLMN (Home PLMN) operator specific.
Trusted accesses can connect directly to the EPC. In the case of untrusted accesses,
interworking via an ePDG (evolved Packet Data Gateway) is required. The main functions of
an ePDG are security-based, for example providing IPsec (IP security) tunnelling between
the UE and the EPC over the untrusted access.
In roaming scenario, the HPLMNs HSS/AAA (Authentication, Authorisation and Accounting)
server makes the final decision regarding whether a non-3GPP IP access network is trusted
or untrusted. The AAA Server may take the policy and capability of the VPLMN (Visited
HPLMN) into account, which will be determined from the AAA Proxy or the roaming
agreement.
For multiple PDNs, the same trust relationship shall apply to all the PDNs the UE connects to
from a particular non-3GPP access network, i.e. it shall not be possible to access one PDN
using the non-3GPP access network as trusted, while access to another PDN using the same
non-3GPP access network as untrusted.
The following figure shows the architecture that applies to trusted and untrusted non-3GPP
accesses.

Trusted and Untrusted Non-3GPP Accesses
HPLMN (3GPP networks)

No-3GPP networks, e.g.
WiMax
WLAN
PSTN
CDMA2000

Interworking and Mobility Management

The EPS supports the following mobility management mechanisms:
Network-based mobility management mechanism based on PMIP (Proxy Mobile
IP) or GTP.
Host-based mobility management mechanism (such as MIP (Mobile IP)) over S2
reference points.
IETF-based network-based mobility management mechanism (i.e. PMIP) over
S5/S8 reference points
Roaming Subscribers
Traffic for roaming subscribers may be either home routed or use local breakout.

Home-Routed Traffic
This scenario may occur when a user is roaming in another country or when a
national roaming agreement has been set up between operators, effectively allowing
them to share networks and reduce the investment required to provide national
coverage. Service logic is provided by the home network.
The local MME and S-GW enable the visited network to build and send charging
tickets to the subscribers home operator, corresponding to the amount of data
transferred and the Quality of Service allocated.
The MME is connected to the HSS of the subscribers home network via the S6a
interface (Diameter), enabling it to retrieve the user-specific security credentials
required during authentication and ciphering.
The session path goes through the home PDN-GW over the S8 (GTP) interface, so
as to apply policy and charging rules in the home network corresponding to the usersubscription parameters.

Roaming (Home-Routed Traffic)
VPLMN
No-3GPP networks

Local Breakout
The home routed architecture may be inefficient if the home PDN-GW and the
visiting S-GW are too far apart. In such cases, the EPC supports local breakout of
traffic, the term local breakout meaning that for a user moving within and across
one operator-defined network region (e.g. administrative domain), routing is
optimised such that user-plane traffic does not need to leave the current region. This
can apply whether a roaming subscriber is accessing the EPC via a 3GPP or a non3GPP access network.
Local breakout enables the routing of traffic via the visited PDN-GW, for example if a
user requires public Internet access; in this case, routing the traffic to the home
network would not add any value to the end-user. Routing traffic through the local
gateway avoids a complete round-trip of user data through the home network packet
gateways.
Local breakout is applicable for user-to-user traffic as well as for 3GPP-operator
provided services (including Internet access), and can be used in both roaming and
non-roaming scenarios.
Authorisation of local breakout is by the HPLMN. If local breakout is not authorised,
the user plane traffic shall be handled in the home routed mode.

Roaming (Local Breakout)
VPLMN
No-3GPP networks

Migration to LTE VoIP

The CS fallback and SMS over SGs in EPS function is realized by using the SGs
interface mechanism between the MSC Server and the MME.
The SGs interface functionality is based on the mechanisms specified for the Gs
interface, TS 23.060
TS 23.272
EPS architecture for CS fallback and SMS over SGs


When voice calls are initiated or received, the handset is directed by the network to
the CS network to complete both mobile terminated and mobile originated voice
calls. The functionality to fallback from LTE to CS domain is referred to as CS
Fallback (CSFB).
TS 23.272
EPS architecture for CS fallback and SMS over SGs


TS 23.272
CS Fa
l
lback
Indic
ator
Attach Request
The LTE handset sends the Attach Request together with specific CS
Fallback Indicator to the MME which starts the Location Update procedure
towards MSC/VLR via SGs interface.


TS 23.272
Location Update Request

MME starts the Location Update procedure towards MSC/VLR via SGs interface.


TS 23.272
A mobile terminal using LTE cannot use 3G at the same time. This implies that
the MME which contains the LTE location registration area (Tracking area (TA)), is
unable to identify which MSC/VLR it should send the mobility management
messages to from the TA alone. To solve this problem, the mapping of Tas and 3G
Location Areas (LA) within MME has benn adopted.

TS 23.272


TS 23.272
Mobile Originating Call


TS 23.272
Mobile Terminating Call


TS 23.272

MME starts the Location Update procedure towards MSC/VLR via SGs interface.

Data interruption time

If a user is in an active PS data session (e.g., streaming media) when a voice call
is initiated, the inter-RAT transition and routing area update will interrupt the data
transfer. The interruption time will depend on the mobility mechanism.
Using handover-based CSFB, the data
stream interruption time of 0.3 seconds is
unlikely to be noticeable. The user
experience impact of the much higher 5
second data stream interruption in the
redirection-based Release 9 SI Tunneling
and Release 8 Skip SIBs methods may be
mitigated in practice by the fact that user
attention will already be diverted to
initiating an outgoing call or receiving an
incoming call.
SIB: System Information Block
All units in seconds

Mobility Anchors
During mobility, the U-plane
data path continuity to the
PDN is maintained using
mobility anchors. These are
network element instances
which
are
permanent
members of the U-plane
path and located such that
the path from the anchor to
the PDN does not change.
Mobility anchor point

Mobility Anchors
Mobility scenarios and anchor points

MUCHAS
GRACIAS
por su atencin!
Av. San Luis 1771, San Borja, Lima - Per

Web: http://www.inictel-uni.edu.pe

Mobility and Roaming - T3.10

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Mobility and Roaming - T3.10

Transféré par

Droits d'auteur :

Formats disponibles

Diplomado en Telecomunicaciones y Tecnologas de la

Informacin con mencin en Comunicaciones Inalmbricas

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: Identities GERAN/UMTS

Diplomado en Telecomunicaciones y Tecnologas de la

The Home Location Register (HLR) is the central database

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility : UTRAN registration areas

UTRAN Registration Area (URA).

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: Location updating

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: Paging the subscriber

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: Roaming in another network

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: Roaming in another network

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: Management Procedures

Diplomado en Telecomunicaciones y Tecnologas de la

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: LTE Areas and Identities

TS 23.401 version 11.5.0

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: LTE Areas and Identities

TS 23.401 version 11.5.0

TAs (Tracking Areas)

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: Network Identifiers in LTE

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: UE/Subscriber Identifiers

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: UE/Subscriber Identifiers

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: UE/Subscriber Identifiers

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: MME Identifiers

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility: EPS Bearer Identity

Diplomado en Telecomunicaciones y Tecnologas de la

Diplomado en Telecomunicaciones y Tecnologas de la

Mobility scenarios for LTE/EPC

Diplomado en Telecomunicaciones y Tecnologas de la

Interworking with 2G/3G Access

Diplomado en Telecomunicaciones y Tecnologas de la

Interworking with 2G/3G Access

S3 is to support user and bearer information

Diplomado en Telecomunicaciones y Tecnologas de la

Trusted and Untrusted Non-3GPP Accesses

Diplomado en Telecomunicaciones y Tecnologas de la

Trusted and Untrusted Non-3GPP Accesses

HPLMN (3GPP networks)

Diplomado en Telecomunicaciones y Tecnologas de la

Interworking and Mobility Management

Diplomado en Telecomunicaciones y Tecnologas de la

Diplomado en Telecomunicaciones y Tecnologas de la

Roaming (Home-Routed Traffic)

HPLMN (3GPP networks)

Diplomado en Telecomunicaciones y Tecnologas de la

Diplomado en Telecomunicaciones y Tecnologas de la

Roaming (Local Breakout)

HPLMN (3GPP networks)