Tekelec

5200 Paramount Parkway

Morrisville, NC 27560
Voice: 919-460-5500
Fax: 919-460-0877
THIS DOCUMENT AND THE DATA DISCLOSED HEREIN OR HEREWITH IS PROPRIETARY AND IS NOT TO BE REPRODUCED, USED OR DISCLOSED IN
WHOLE OR IN PART TO ANYONE WITHOUT THE WRITTEN PERMISSION OF TEKELEC. COPYRIGHT, TEKELEC 2015

Title:
Technical Reference
Doc Number:
289453719.doc

Revision:

1.0

ECN:

IAS
EAAA Professional Services KPI generation

MAP Roaming Tutorial

Jean-Marie Rota

Do Not Copy
Hard Copies of this document are for Reference Only
The latest approved version is located under version control.

Originator:
Checked:
Approved:

Jean-Marie Rota

Date:
Date:
Date:

10/11/15

Title:
Technical Reference
Doc. No.:
289453719.doc

Revision:

1.0
Page 1 of 17

CHANGE HISTORY
Date

Revision #

Author

Revision Description

20 Jan
2010

1.0

Jean-Marie
Rota

Creation

Title:
Doc No.:

Technical Reference
289453719.doc

Approved
(Yes/No)

Revision:

1.0
Page 2 of 17

TABLE OF CONTENTS

1.
1.1
1.2
1.3
1.4

INTRODUCTION......................................................................................................4
Purpose..................................................................................................................4
Product Summary..................................................................................................4
References.............................................................................................................4
Acronyms...............................................................................................................4

2.1
2.2
2.3
2.4

WHAT IS ROAMING?..............................................................................................6
Roaming measurements through IAS system.......................................................6
Roaming types.......................................................................................................6
Roaming Inbound and Outbound..........................................................................6
Roaming agreements between operators.............................................................7

2.

3.

INBOUND ROAMING TECHNICAL DESCRIPTION...............................................8

3.1 Network case.........................................................................................................8
3.2 Sequence details...................................................................................................8
3.3 Useful Information from IAS xDR fields.................................................................9
3.3.1
3.3.2
3.3.3

4.

Addresses for Network identification (Roaming-In Update_Loc)..............................9

Getting Roaming Inbound traffic from IAS..............................................................10
External requirements for Inbound..........................................................................11

OUTBOUND ROAMING TECHNICAL DESCRIPTION.........................................12

4.1 Network case.......................................................................................................12
4.2 Sequence details.................................................................................................12
4.3 Useful Information from IAS xDR fields...............................................................13
4.3.1
4.3.2
4.3.3

5.
5.1
5.2
5.3

Addresses for Network identification (Roaming-Out Update_Loc).........................13

Getting Roaming Outbound traffic from IAS............................................................14
External requirements for Outbound.......................................................................15

NUMBERING PLANS AND FORMATS.................................................................16

E164 - MSISDN...............................................................................................16
E212 - IMSI......................................................................................................16
E214.....................................................................................................................16

6.

TESTABILITY.........................................................................................................17

7.

DOCUMENT REVIEW NOTES..............................................................................17

Title:
Doc No.:

Technical Reference
289453719.doc

Revision:

1.0
Page 3 of 17

1.

INTRODUCTION

1.1

Purpose

The purpose of this document is to provide engineers with the required knowledge about
network behavior in order to deploy, integrate and test Key Performance Indicators (KPI) on an
existing Tekelec IAS system.

1.2

Product Summary

N/A. This document describes the behavior of the GSM network. It is so independent of the
Tekelec IAS system which is monitoring the network.

1.3

References
1. GSM MAP Specifications

1.4

Acronyms

MS
PLMN
HPLMN
MAP
SSN
SCCP

HLR
VLR
MSC
GMSC
N.E.

IMSI
MSISDN
MSRN

Mobile Station : GSM terminal, with SIM Card, able to work on a network;
Public Land Mobile Network : GSM network, managed by an operator in a
country;
Home PLMN of the subscriber;
Mobile Application Part : SS7 layer 7 (application layer), uses TCAP for
connections, and allows dialoguing between GSM equipments;
Sub-System Number, identifies the functional type of a N.E : HLR, VLR, MSC,
INAP, MAP,;
Signalling Connection Control Part : SS7 protocol, provides connected or
connectionless services (in our case to TCAP, or BSSAP). Allows
interconnection of international semaphore networks;
Home Location Register : home (subscription) register switch of a mobile;
Visitor Location Register : current register switch of a mobile, usually attached
to a MSC;
Message-services Switching Centre : switching equipment, manages incoming
and outgoing calls;
Gateway MSC.
Network Element : any physical and functional element of the network, like
MSC, GMSC, VLR, HLR, SSP, SCP, STP, SMS-C, ;
International Mobile Subscriber Identity : international identity of a subscribers
SIM Card, fits to E212 plan. Its used most of the time by the network for
routing call or other matters;
Mobile Station ISDN number : phone number of a subscriber. Fits to E164
telephony plan;
Mobile Station Roaming Number : temporarily assigned E164-telephony-plan
number. Allows a call to be routed to the MSC where is called MS;
Title:
Doc No.:

Technical Reference
289453719.doc

Revision:

1.0
Page 4 of 17

TMSI
IMEI

CC
MCC
MNC
NDC

Temporary Mobile Station Identity : temporary identity assigned to a MS and

afterwards used for radio channel transactions;
International Mobile Equipment Identity : international identity of mobile
equipment;
Country Code. Contained in E164 numbering plan ;
Mobile Country Code. Identifies country in which is the PLMN. Contained in
E212/214 numbering plan;
Mobile Network Code. Identify the network in a given country. Contained in
E212/214 numbering plan;
Network Destination Code. Identify the network in a given country. Contained
in E164 numbering plan;

Title:
Doc No.:

Technical Reference
289453719.doc

Revision:

1.0
Page 5 of 17

2.

WHAT IS ROAMING?

In wireless telecommunications roaming is a general term that refers to the extending of

connectivity service in a location that is different from the home location where the service was
registered. Roaming ensures that the wireless device keeps connected to the network, without
losing the connection.
Roaming is technically supported by mobility management, authentication, authorization and
billing procedures. However, for KPI purposes based on Tekelec IAS monitoring system, this
document will mainly describe mobility management. Mobility management is enough to reflect
where subscribers are located. It involves the following MAP operations:
- MAP_UPDATE_LOCATION (subscribers location updated in its home network and
profile recorded in VLR of newly visited network)
- MAP_CANCEL_LOCATION (subscriber is cancelled in previous VLR)
Detailed description of mobility management is provided in this document; see Inbound and
Outbound roaming descriptions.

2.1

Roaming measurements through IAS system

The IAS system observes and records all type of MAP operations from the monitored network.
When considering location update operations, traffic contains:
- Roaming traffic (the moves involves another operator than the home network)
- Local mobility management traffic related to subscribers from the monitored network
moving into it. This is not considered as roaming as there is no operator change.
We consider as roaming traffic only update locations where moves are between another
operator and the monitored network. This corresponds to International or National Roaming
definitions. See below.

2.2

Roaming types

International Roaming:
This type of roaming refers to the ability to move to a foreign service provider's network.
So roaming occurs between two operators from two different countries.
National Roaming:
This type of roaming refers to the ability to move from one mobile operator to another in the
same country.
Regional Roaming:
This type of roaming refers to the ability of moving from one region to another region inside
national coverage of the mobile operator. Nowadays most of the operators are not making any
difference between regions. It might be exceptions in wide areas countries however.

2.3

Roaming Inbound and Outbound

The roaming traffic of a monitored network has to be considered in two independent categories
according to the way the roaming occurs:
Title:
Doc No.:

Technical Reference
289453719.doc

Revision:

1.0
Page 6 of 17

Inbound roaming or Roaming In:

Considering the situation seen from the monitored network, a subscriber from another operator
attaches to the monitored network. So all traffic related to subscribers coming from other
networks defines the roaming inbound traffic.
Outbound roaming or Roaming Out:
Subscribers belonging to the monitored network have moved to other networks. All traffic
generated into the monitored network for those subscribers who are located in other networks
defines the roaming outbound traffic.
NOTE:
The IAS monitoring system will provide Key Performance Indicators (KPIs) for these two
categories. The IAS system has to provide Inbound and Outbound KPIs separately.

2.4

Roaming agreements between operators

The legal roaming business aspects negotiated between the roaming partners for billing of the
services obtained are usually stipulated in so called roaming agreements. The GSM
Association broadly outlines the content of such roaming agreements in standardized form for
its members.
In order that a subscriber is able to "connect" on to a visited network, a roaming agreement
needs to be in place between the visited network and the home network. This agreement is
established after a series of testing processes called IREG (International Roaming Expert
Group) and TADIG (Transferred Account Data Interchange Group). While the IREG testing is to
test the proper functioning of the established communication links, the TADIG testing is to check
the billability of the calls.
The GSM Association provides useful technical documentation about roaming agreements. It is
accessible (members only) through GSMA Info Center web site (https://infocentre.gsm.org. ).
Tekelec has an account to this Information Center.
Regarding IAS KPI deployment, mainly the following information is important:
-

IR21 file:
There is one file per operator which describes all technical information related to the
network that is related to International Roaming. It includes codes, ranges, addresses in
the different numbering plans.
SE list:
This file provides the list of all GSM operators with names, labels and most of the
addressing information (country and network codes, addresses).

Title:
Doc No.:

Technical Reference
289453719.doc

Revision:

1.0
Page 7 of 17

3.

INBOUND ROAMING TECHNICAL DESCRIPTION

3.1

Network case

The Mobile subscriber (MS) does not belong to Monitored network and is moving from network
A to B.

2
Monitored
Network (B)

MSC

MSC

Previous
Network (A)
(Home network
or any other)

VLR
M
S

M
S

VLR

3
Update

Location

Cancel Ack

Insert Suscriber Data

Cancel Location

HLR

Home
Network of MS

3.2
Item
1

2
3

Sequence details
Description
The MS attempts to connect to network B.
From a MS power on the procedure Attach Request is sent. From handover from
network A a Location Updating Request is sent.
Parameters: in both cases the IMSI number and the LAI (location area identifier) are
provided. LAI includes MCC (mobile country code), MNC (mobile network code) and
LAC (location area code)
Note: In case the MS sends TMSI (Temporary MS Identity) first, an Identity Request is
sent to the MS. MS sends then an Identity Response that contains IMSI.
MSC sends a MAP_Update_Location_Area to VLR. Most of the time this operation is
not monitored because MSC/VLR is seen as a single network element.
The VLR of the monitored network sends an Update_Location to the HLR, in home
network of the MS.
Title:
Doc No.:

Technical Reference
289453719.doc

Revision:

1.0
Page 8 of 17

Parameters:
- IMSI of MS, it contains MCC-MNC-MSIN (E212 numbering plan)
- VLR B and MSC B addresses, format E164, CC-NDC-SN
Routing the Update_Location message:
- It uses SCCP layer, routing is based on GT (Global Title)
- CgSCCP address = VLR B address (of monitored network)
- CdSCCP address = This is processed specially. The address is defined in E214
format: CC-NDC-MSIN. To get this address:
o MSIN is extracted from the IMSI by removing the 5 first digits
o CC-NDC is translated from MCC-MNC (of the IMSI).
o In E214 format, CC-NDC is also called MGT (mobile global title). The
MGT used to address a home network is defined in the roaming
agreements.
4
5

The HLR sends several messages Insert_Subscriber_Data providing the VLR with:
- MSISDN of the MS. Format CC-NDC-SN (E164 format)
- Parameters related to MS profile
The HLR recorded (from previous location in network A) the previous VLR. The HLR
sends a Cancel_Location to the previous VLR A.
Parameter:
- IMSI of MS
Routing:
- It uses SCCP layer, routing is based on GT (Global Title)
- CdSCCP address = VLR B address (E164 format) that was recorded by HLR
Note about IAS monitoring system:
Cancel operation is only observed / recorded in the case where previous
network A was the home network (roamer is moving in home network). In all
other cases Cancel operation takes place in other PLMNs.
VLR A sends acknowledge to Cancel request.

NOTE: see also numbering plan formats chapter in this document.

3.3

Useful Information from IAS xDR fields

3.3.1 Addresses for Network identification (Roaming-In Update_Loc)

Note: examples in this table are consistent between them (come from same xDR). Last digits
are masked.
MAP xDR field
Description (case is Roaming-In Update_Loc)
IMSI
- Reflects the mobile subscriber, so in his home network.
- MCC-MNC-MSIN format (E212 ).
(reflects home
- The 2 first digits of MSIN reflects the HLR number
network in E212 - Example: 20801320166xxxx where:
format)
- 208 is the Mobile Country Code, 208 is France
- 01 is the Mobile Network Code, 01 is Orange France
- 32 defines the HLR number (in that network) in a unique way
CdSCCP Add
- Called SCCP address. It is used to route the message to the HLR in the
Home network. It is the one coming from the BEGIN message of the xDR.
(reflects home
- It is in E214 format, so MGT-MSIN (also defined as CC-NDC-MSIN):
Title:
Doc No.:

Technical Reference
289453719.doc

Revision:

1.0
Page 9 of 17

network in E214
format)

CgSCCP Add
(reflects
monitored
network in E164
format)
MSISDN

VLRnb

- The monitored network uses the MCC-MNC of the IMSI to get the
corresponding MGT. MGTs have been defined in theroaming
agreements.
- MSIN is the IMSI where the 5 first digits (MCC-MNC)are removed
- Remark: this E214 format is used to address the HLR in the BEGIN
message. The HLR will put his address in E164 format when answering back
with CONTINUE or END messages.
- Example: 33689320166xxxx where:
- 33689 is the MGT
- 320166xxxx is the MSIN (32 is the HLR number)
- Calling SCCP address of the VLR in the monitored network.
- CC-NDC-SN format (E164) CCNDC is variable length.
- Example: 44797302xxxx where CC=44 (U.K.) NDC=7973

- Mobile subscriber number (dialed number). The HLR sends it to the VLR
through the Insert_Subscriber_data operations as answer to the
Update_Location request.
- CC-NDC-SN format (E164)
- Example: 3367744xxxx provided by HLR according to IMSI

GSM SCF Add

(in home
network)

- VLR address (in monitored network).

- CC-NDC-SN format (E164) CCNDC is variable length
- Example: 44797302xxxx Actually same as CgSCCP Add (obviously!)
- HLR address (home network of course)
- CC-NDC-SN format (E164) CCNDC is variable length
- This address is different than the CdSCCP used on the first message
- This address is known with first HLR answer and used from 2nd message
until last message in the transaction.
- Example: 33689002xxx
- MSC address (in monitored network) that is using the VLR. Each MSC has a
(single) VLR, we actually often consider the couple MSC/VLR.
- CC-NDC-SN format (E164) CCNDC is variable length
- Example: 44797302yyyy (different than VLR address)
- Optional information, when known
- Service Control Function address, CC-NDC-SN format (E164)
- Example: 33689006xxx

CdSSN
CgSSN

- Called Sub-System Number is 6 (HLR)

- Calling Sub-System Number is 7 (VLR)

HLRnb

MSCnb

3.3.2 Getting Roaming Inbound traffic from IAS

In order to generate KPIs for Inbound roaming it is important to consider the right traffic within
the right xDR sessions of the monitored network.
Sessions:
Title:
Doc No.:

Technical Reference
289453719.doc

Revision:
1.0
Page 10 of 17

Only sessions that contain Mobility Management traffic related to Inter-PLMN (between
networks) have to be considered.
Traffic related to Inter-MSC mobility management of subscribers of the monitored
network is not considered (it is not roaming !).
It is suggested to select traffic related to gateways used for interconnecting PLMNs or
traffic related to GMSCs.

Within the selected session(s) Roaming-In can be identified by selecting xDR having the
following profile:
- Operation according to KPI (Update_Loc, Update_Loc for GPRS, Cancel_Loc if
required)
- IMSI that does not belong to monitored network (test on MCC-MNC). This option
includes traffic for both National and International roaming.
- Theres also a possibility to filter on point code if its necessary to consider the traffic to
gateways (GMSC for example). This depends on how the sessions are organized.
Note about using Way field in xDR MAP records:
Way reflects the direction (incoming or outgoing) of the transaction performed (Update_Location
for example). In IAS this direction is considered according to the far-end network element if
monitoring is on STPs. A roaming-in Update_Location xDR is marked incoming or outgoing
depending on the measurement topology. Care must be taken when using this field to select
traffic.

3.3.3 External requirements for Inbound

To analyze the Roaming-In traffic of the monitored network and generate KPIs the following
information is required:
-

A table that contains MCC-MNC codes with related country and operator names will be
required to analyze traffic by operator (and/or countries).

Possibly the IR21 file of the operator (monitored network) that contains all information
about international roaming. The GSM Association can provide this document. Tekelec is
member and can get this information as well.

Title:
Doc No.:

Technical Reference
289453719.doc

Revision:
1.0
Page 11 of 17

4.

OUTBOUND ROAMING TECHNICAL DESCRIPTION

4.1

Network case

The Mobile subscriber (MS) belongs to Monitored network is moving from network A to B.
Note: Diagram looks like Inbound diagram but network titles have changed.

Newly Visited
Network (B)
(Any except
home network)

2
MSC

MSC

Previous
Network (A)
(Home network
or any other)

VLR
M
S

M
S

VLR

3
Update

Location

6
Cancel Ack

Insert Suscriber Data

Cancel Location

HLR
Home Network of MS.
It is also the
Monitored Network

4.2

Sequence details

Item
1

Description
(In foreign PLMN, not monitored by IAS)
The MS attempts to connect to network B, B not being the home network.
From a MS power on the procedure Attach Request is sent. From handover from
network A a Location Updating Request is sent.
Parameters: in both cases the IMSI number and the LAI (location area identifier) are
provided. LAI includes MCC (mobile country code), MNC (mobile network code) and
LAC (location area code)
Note: In case the MS sends TMSI (Temporary MS Identity) first, an Identity Request is
sent to the MS. MS sends then an Identity Response that contains IMSI.

(In foreign PLMN, not monitored by IAS)

MSC sends a MAP_Update_Location_Area to VLR within the visited network.
Title:
Doc No.:

Technical Reference
289453719.doc

Revision:
1.0
Page 12 of 17

4
5

The VLR of the visited network sends an Update_Location to the HLR, in home
network of the MS.
Note: following parameters and routing info have exactly same definition as RoamingInbound.
Parameters:
- IMSI of MS, it contains MCC-MNC-MSIN (E212 numbering plan)
- VLR B and MSC B addresses, format E164, CC-NDC-SN
Routing the Update_Location message:
- It uses SCCP layer, routing is based on GT (Global Title)
- CgSCCP address = VLR B address (of monitored network)
- CdSCCP address = This is processed specially. The address is defined in E214
format: CC-NDC-MSIN. To get this address:
o MSIN is extracted from the IMSI by removing the 5 first digits
o CC-NDC is translated from MCC-MNC (of the IMSI).
o In E214 format, CC-NDC is also called MGT (mobile global title). The
MGT used to address a home network is defined in the roaming
agreements.
The HLR sends several messages Insert_Subscriber_Data providing the VLR with:
- MSISDN of the MS. Format CC-NDC-SN (E164 format)
- Parameters related to MS profile
The HLR recorded (from previous location in network A) the previous VLR. The HLR
sends a Cancel_Location to the previous VLR A.
Parameter:
- IMSI of MS
Routing:
- It uses SCCP layer, routing is based on GT (Global Title)
- CdSCCP address = VLR B address (E164 format) that was recorded by HLR
Note: All Cancel operations related to Outbound Roaming can be monitored in IAS as
HLR is in monitored network (it is not the case for Inbound Roaming).
VLR A sends acknowledge to Cancel request.

NOTE: see also numbering plan formats chapter in this document.

4.3

Useful Information from IAS xDR fields

4.3.1 Addresses for Network identification (Roaming-Out Update_Loc)

Note: examples in this table are consistent between them (come from same xDR). Last digits
are masked.
MAP xDR field
Description (case is Roaming-Out Update_Loc)
IMSI
- Reflects the mobile subscriber, so in his home network.
- MCC-MNC-MSIN format (E212 ).
(reflects home
- The 2 first digits of MSIN reflects the HLR number
and monitored
- Example: 23433430451xxxx where:
network in E212
- 234 is the Mobile Country Code, 234 is UK
format)
- 33 is the Mobile Network Code, 33 is Orange UK
- 43 defines the HLR number (in that network) in a unique way
Title:
Doc No.:

Technical Reference
289453719.doc

Revision:
1.0
Page 13 of 17

CdSCCP Add
(reflects home
and monitored
network in E214
format)

CgSCCP Add
(reflects visited
network in E164
format)
MSISDN
(home and
monitored
network in E164
format)
VLRnb
(reflects visited
network in E164
format)
HLRnb
(reflects home
and monitored
network in E164
format)

- Called SCCP address. It is used to route the message to the HLR in the
Home network. It is the one coming from the BEGIN message of the xDR.
- It is in E214 format, so MGT-MSIN (also defined as CC-NDC-MSIN):
- The monitored network uses the MCC-MNC of the IMSI to get the
corresponding MGT. MGTs have been defined in the roaming
agreements.
- MSIN is the IMSI where the 5 first digits (MCC-MNC)are removed
- Remark: this E214 format is used to address the HLR in the BEGIN
message. The HLR will put his address in E164 format when answering back
with CONTINUE or END messages.
- Example: 44973430451xxxx where:
- 44973 is the MGT
- 430451xxxx is the MSIN (43 is the HLR number)
- Calling SCCP address of the VLR in the visited network.
- CC-NDC-SN format (E164) CCNDC is variable length.
- Example: 3360900xxxx where CC=33 (France) NDC=609
- Mobile subscriber number (dialed number). The HLR sends it to the VLR
through the Insert_Subscriber_data operations as answer to the
Update_Location request.
- CC-NDC-SN format (E164)
- Example: 44789691xxxx provided by HLR according to IMSI
- VLR address in visited network.
- CC-NDC-SN format (E164) CCNDC is variable length
- Example: 3360900xxxx Actually same as CgSCCP Add (obviously!)

MSCnb
(reflects visited
network in E164
format)
GSM SCF Add
(in home
network)

- HLR address (home and monitored network)

- CC-NDC-SN format (E164) CCNDC is variable length
- This address is different than the CdSCCP used on the first message
- This address is known with first HLR answer and used from 2nd message
until last message in the transaction.
- Example: 44797305xxxx
- MSC address (in monitored network) that is using the VLR. Each MSC has a
(single) VLR, we actually often consider the couple MSC/VLR.
- CC-NDC-SN format (E164) CCNDC is variable length
- Example: 3360900xxxx (different than VLR address)
- Optional information, when known
- Service Control Function address, CC-NDC-SN format (E164)
- Example: 44797301xxxx

CdSSN
CgSSN

- Called Sub-System Number is 6 (HLR)

- Calling Sub-System Number is 7 (VLR)

4.3.2 Getting Roaming Outbound traffic from IAS

In order to generate KPIs for Outbound roaming it is important to consider the right traffic within
the right xDR sessions of the monitored network.
Title:
Doc No.:

Technical Reference
289453719.doc

Revision:
1.0
Page 14 of 17

Sessions:
- Only sessions that contain Mobility Management traffic related to Inter-PLMN (between
networks) have to be considered.
- Traffic related to Inter-MSC mobility management of subscribers of the monitored
network is not considered (it is not roaming !).
- It is suggested to select traffic related to gateways used for interconnecting PLMNs or
traffic related to GMSCs.
- If gateways or GMSC traffic is not available, Outbound roaming traffic is also available
on sessions recording HLR traffic (Notice that it is not the case for Inbound roaming).
Within the selected session(s) Outbound Roaming can be identified by selecting xDR having
the following profile:
- Operation according to KPI (Update_Loc, Update_Loc for GPRS, Cancel_Loc if
required)
- IMSI that belongs to monitored network (test on MCC-MNC). This option includes traffic
for both National and International roaming.
- Calling SCCP address (or VLR nb or MSC nb) does not belong to monitored network
(test on CC-NDC of monitored network). This condition guarantees that the MS is
located in another PLMN than home. In other words the condition removes all traffic that
is internal to the monitored network
- Theres also a possibility to filter on point code if its necessary to consider the traffic to
gateways or GMSC for example. This depends on how the sessions are organized.
Note about using Way field in xDR MAP records: (same remark here as Inbound)
Way reflects the direction (incoming or outgoing) of the transaction performed (Update_Location
for example). In IAS this direction is considered according to the far-end network element if
monitoring is on STPs. A roaming-out Update_Location xDR is marked incoming or outgoing
depending on the measurement topology. Care must be taken when using this field to select
traffic.

4.3.3 External requirements for Outbound

To analyze the Roaming-Out traffic of the monitored network and generate KPIs the following
information is required:
-

A table that contains E164 CC-NDC codes and ranges with related country and operator
names will be required to analyze traffic by operator (and/or countries).
Note: Operator and country can be tested on CgSCCP address, VLR nb or MSC nb of
the visited network. All are in E164 format. Depending on the PLMN there might be
several codes to test for one operator. It has to be verified which of the 3 fields is the
best compromise. Some PLMNs have lots of codes assigned

MCC-MNC code(s) of the monitored network. Also included in IR21 file of the operator
(monitored network).

Title:
Doc No.:

Technical Reference
289453719.doc

Revision:
1.0
Page 15 of 17

5.

NUMBERING PLANS AND FORMATS

5.1

E164 - MSISDN

E164 is the international numbering plan used for call establishment within fixed or mobile
networks. All dialed numbers are using this format.
In GSM networks E164 is used for:
- MSISDN, subscriber number Mobile Station ISDN Number
- Network elements such as MSC, VLR, HLR have a E164 number. It is used to route
signaling messages through standard SS7 signaling network.

CC
Country
Code
1 to 3 digits

5.2

NDC
National
Destination
Code
3 digits

SN
Subscriber Number
Variable length

E212 - IMSI

E212 is the mobile numbering plan.

A fix length of 5 digits defines the operator.

MCC
Mobile
Country
Code
3 digits

5.3

MNC
Mobile
Network
Code
2 digits

MSIN
Subscriber Number Identification Number.
Variable length, up to 10 digits max
The 2 first digits of MSIN define the HLR number
within the considered network. Digits are named
H1H2.

E214

E214 is a mobile global numbering plan used for signaling message routing purposes. It
combines routing capabilities of E164 header (CC-NDC) that is worldwide routable and Mobile
subscriber numbers. E214 is used in SS7-SCCP layer to route a signaling message.
The header composed of CC-NDC is also called MGT, Mobile Global Title.

MGT
CC
Country
Code
1 to 3 digits

NDC
National
Destination
Code
3 digits

MSIN
Subscriber Number Identification Number.
Variable length, up to 10 digits max
The 2 first digits of MSIN define the HLR number
within the considered network. Digits are named
H1H2.
Title:
Doc No.:

Technical Reference
289453719.doc

Revision:
1.0
Page 16 of 17

6.

TESTABILITY

On the IAS monitoring system, KPIs are compared to results from xDR Browser queries in order
to verify that KPI configuration is performed properly. Related test cases have to be developed.

7. DOCUMENT REVIEW NOTES

Title:
Doc No.:

Technical Reference
289453719.doc

Revision:
1.0
Page 17 of 17