Comfone Key2roam

Data Roaming

Implementation Guideline

Comfone AG Tel: +41 31 341 10 10

Nussbaumstrasse 25 Fax: +41 31 341 10 11
P.O. Box www.comfone.com
CH-3000 Bern 22

Confidential 1/17
 Key2roam
Data Roaming Implementation Guideline

Statement of Confidentiality

The descriptive materials and related information in this document are confidential and
proprietary to Comfone. Information is submitted with the express understanding that it will
be held in strict confidence and will not be disclosed, duplicated or used, in whole or in part,
for any purpose other than evaluation of this project.
This document is proprietary to Comfone. It is supplied in confidence to the receiving
company. The contents of the document remain restricted to, and may only be disclosed to,
the employees of the receiving company involved in the evaluation process.
This document must not be reproduced in whole or in part, or used for tendering or
manufacturing purposes, except under an agreement or with the consent in writing of
Comfone and then only on the condition that this notice is included in any such reproduction.
No information as to the contents or subject matter of this document or any part thereof –
arising directly or indirectly therefrom – shall be given orally or in writing or shall be
communicated in any manner whatsoever to any third party – being an individual firm or
company or any employee thereof – without the prior consent in writing of Comfone.

Comfone AG Carried out SR/MB 2/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

Table of contents

1 INTRODUCTION ...............................................................................................4
1.1 Purpose and Scope ....................................................................................................................4

1.2 The Data Roaming Platform ......................................................................................................4

1.3 Data Roaming Network Architecture........................................................................................7

1.4 Comfone’s IP Address Ranges .................................................................................................8

1.5 DNS and GTP message flow .....................................................................................................9

2 TECHNICAL IMPLEMENTATION PROCEDURE........................................... 10

2.1 Prerequisites.............................................................................................................................10

2.2 MAP Connectivity Set-up.........................................................................................................11

2.3 IP Connectivity Setup...............................................................................................................11

2.4 DNS configuration in the visited network ..............................................................................13

2.5 TADIG Code and TAP File Flow ..............................................................................................15

2.6 Billing System Configuration ..................................................................................................15

2.7 Test SIM Cards for GPRS Data Roaming Test.......................................................................15

3 GLOSSARY .................................................................................................... 16

4 COMFONE DOCUMENT REFERENCES ....................................................... 17

Comfone AG Carried out SR/MB 3/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

1 Introduction

1.1 Purpose and Scope

The scope of this document is to describe the concept of Key2roam Data Roaming with the
goal to support the Key2roam partner during the initial Key2roam Data Roaming
implementation and to establish new Data Roaming relations via Key2roam.
The following sections are providing an overview of the Key2roam Data Roaming Solution
and the Data Roaming Platform that enables the service feature for Key2roam. The
document provides the IP addressing method, Network configuration details, examples for
the main implementation steps, and the comprehensive description of all the MAP and GTP
aspects relevant to Key2roam Data Roaming.
This document complements the Key2roam Data Roaming Service Description.

1.2 The Data Roaming Platform

In order to simplify the set-up and maintenance of data roaming relations, Comfone fully
integrates the data layers into Key2roam.
The concept of the platform and the service provided by Comfone is inline with the all today’s
service principles of Key2roam.
Members can use their existing infrastructure and suppliers such as SCCP and GRX
provider to access the Data Roaming Platform and no additional investment in the network
infrastructure is required by the member.
In order to extend the roaming hubbing principle to data roaming and have one single
technical and commercial relation with the hub to reach many destinations, Comfone
virtualises the GSN nodes of the Key2roam members using the Data Roaming Platform as
illustrated below:

Comfone AG Carried out SR/MB 4/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

Comfone Key2roam
MNO A (VPMN) MNO B (HPMN)
MNO B’ MNO A’

Roaming
RoamingManagement Roaming Roaming
RoamingManagement
Management RoamingCoordination
Coordination Management

DC/FC
DC/FC DC/FC
DC/FC
Clearing
Clearing(DC/FC)
(DC/FC)

STP STP
CS SS7
SS7Signalling
Signalling SCCP B
CSCore
Core SCCP A CS
CSCore
Core
SMS-C SMS-C
SMS-IW
SMS-IWHub
Hub

MMSC GRX A GRX B MMSC

MMS-IW
MMS-IWHub
Hub

PS
PSCore
Core PS
PSCore
Core
Data Roaming Platform
SGSN
GRX A DNS GRX B GGSN
GGSN’ SGSN’

GW-MSC Voice Carriers GW-MSC

Figure 1: Integration of the IP layer into Key2roam

Comfone AG Carried out SR/MB 5/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

In addition to the technical part of the Data Roaming Platform, the following Key2roam
building blocks (marked in red) are required to establish, operate and maintain the data
roaming relations via Key2roam:

Comfone Key2roam
MNO A (VPMN) MNO B (HPMN)
MNO B’ MNO A’

Roaming
RoamingManagement Roaming Roaming
RoamingManagement
Management RoamingCoordination
Coordination Management

DC/FC
DC/FC DC/FC
DC/FC
Clearing
Clearing(DC/FC)
(DC/FC)

STP STP
CS SS7
SS7Signalling
Signalling SCCP B
CSCore
Core SCCP A CS
CSCore
Core
SMS-C SMS-C
SMS-IW
SMS-IWHub
Hub

MMSC GRX A GRX B MMSC

MMS-IW
MMS-IWHub
Hub

PS
PSCore
Core PS
PSCore
Core
Data Roaming Platform
SGSN
GRX A DNS GRX B GGSN
GGSN’ SGSN’

GW-MSC Voice Carriers GW-MSC

Figure 2: Data Roaming components of Key2roam

Comfone AG Carried out SR/MB 6/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

1.3 Data Roaming Network Architecture

The data roaming network architecture for Key2roam is based on two main principles:
• The SS7 signalling traffic related to data roaming is centralised on the Key2roam
platform using the Alias GT method (as per GSMA IR.80, already implemented for
Key2roam voice/SMS relations).
• The data roaming traffic (GTP-C and GTP-U traffic) is centralised on the Data
Roaming Platform

SCCP Connectivity

SCCP MAPv3,CAPv3 SCCP

Provider A MAPv3,CAPv3 Provider B

Key2roam
Signalling Platform

DNS

SCCP GW Data Roaming SCCP GW

Platform

DNS VLR HLR

Member A Member B
(VPMN) (HPMN)
GTP-C,GTP-U IP Connectivity GTP-C,GTP-U
VLR DNS
SGSN GGSN

GRX GRX
Provider B Provider B

Figure 3: Network integration of the Data Roaming Platform

The Key2roam signalling setup is transparent for MAP and CAP messages. For the data
roaming traffic, the MAPv3 protocol has to be supported by both networks.
The Data Roaming Platform handles data related SS7 traffic and can accept or reject the
GPRS location updates. Therefore, the Data Roaming traffic screening on the MAP layer is
done on the Key2roam Signalling Platform and on the IP layer by the Data Roaming
Platform.
Access to the Data Roaming Platform does not require the Key2roam member to use
Comfone as GRX provider. However, using Comfone as GRX provider not only simplifies the
initial set-up, but also troubleshooting because no third party needs to be involved.

Comfone AG Carried out SR/MB 7/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

1.4 Comfone’s IP Address Ranges

For the IP network configuration, there is only one activity to be performed by the Key2roam
member and its GRX provider in order to enable the data roaming traffic!

Member A (VPMN) Data Roaming Platform

for Key2roam Member B (HPMN)

PS DNS
PSCore
Core SGSN GRX A GRX B
GGSN PS
PSCore
Core
GGSN’ SGSN’

Real Identity: A
Messages from A to B (A,B) origins as (A,b’) Real Identity: B
Data Roaming Platform Identity: a‘
and are mapped in the Platform to (a’, B) Data Roaming Platform Identity: b‘

Data Roaming Platform IP Address Ranges

AS 35030
195.211.12.128/25
195.211.13.128/25
195.211.12.96/27
195.211.13.96/27

Real ranges IP of Member A Data Roaming Platform Data Roaming Platform Real ranges IP of Member B
(VPMN) IP Address DNS IP Addresses (HPMN)
GTP-C
195.211.12.129 195.211.12.122
AS 98765 195.211.13.122 GTP-C AS 12344
202.2.68.0/24 80.255.71.0/24
202.96.18.0/24 GTP-U 80.255.78.0/23
202.96.115.0/24 Virtual IP of Member B Virtual IP of Member A 87.255.171.0/23
GTP-U
189.34.154.0/24 195.211.12.170 195.211.12.250 87.255.222.0/23
202.89.111.0/24 80.255.78.0/23

Figure 4: IP Connectivity to the Data Roaming Platform

As part of the initial set-up procedure and based on a specific Key2roam IR.21 provided by
Comfone, the firewalls within the Key2roam member network and its GRX provider have to
be opened for Comfone’s IP address ranges.
Opening new data roaming relations (in addition to live voice/SMS relations) requires no
additional firewalls configuration by members and their GRX providers.
The Data Roaming Platform takes over IP address handling from roaming partner. Therefore,
the solution avoids any IP related firewall problems in the Home or Visited networks and
related GRX networks because the underlying IP interconnection has already been
established during the initial set-up.
Whenever a PDP context is established in the roaming scenario, the Data Roaming Platform
will map the real GSN IP addresses so that both GSNs only see and handle IP addresses
published by the Data Roaming Platform and IP addresses belonging to its own IP address
pool. The Data Roaming Platform routes the GTP traffic between VPMN and HPMN.

Comfone AG Carried out SR/MB 8/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

The information about the real GSN IP addresses and the mapping table per member will be
stored in a database managed by the Data Roaming Platform and is available in the
Key2roam Online Reporting System.
Based on the static mapping between the members Inter PMN IP address and the uniquely
assigned Comfone Data Roaming IP address, the full end-to-end transparency is ensured.

1.5 DNS and GTP message flow

In addition to the GTP protocol for the data roaming traffic, the Data Roaming Platform also
supports the DNS protocol for the DNS queries. For this reason the local DNS in the visited
network must be configured to respond with the Data Roaming Platform IP address for any
APN of the HPMN.
Upon receiving the Create PDP Context message, the Data Roaming Platform will address
the real H-GGSN addresses through the DNS resolution of the APN parameter in the Create
PDP Context message.
The final DNS resolution will be initiated from the Data Roaming Platform over its own DNS
server towards the authoritative DNS for the HPMN.

Figure 5: GTP and DNS message flow

Comfone AG Carried out SR/MB 9/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

2 Technical Implementation Procedure

2.1 Prerequisites

2.1.1 GTP Versions

All SGSN and GGSN nodes have to support GTPv1.
After an analysis of the market situation, 3GPP standards, GSMA recommendations and the
existing SGSN/GGSN nodes of Key2roam members, Comfone came to a conclusion that
there is no need to support GTPv0; Neither from a business nor from a technical perspective.

2.1.2 Hybrid GSN Nodes

Hybrid/combined GSN nodes having the same IP address for both SGSN and GGSN
functionality are not supported. In a survey conducted by Comfone among Key2roam
members, there has never been such a case discovered.

2.1.3 IP Source Address of GTPv1 Response Message

The implementation of virtual GSN nodes in the Data Roaming Platform follows the strong
recommendation in the GSMA PRD documents IR.33 version 3.4 and IR.34 version 4.7
under the title “IP Source address of GTPv1 response message”. Therefore, it is assumed
that “MNOs configure their GGSNs to always respond to GTP request messages using the
source IP address that the GTP request message was sent to”.

Comfone AG Carried out SR/MB 10/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

2.2 MAP Connectivity Set-up

In order to ensure successful signalling traffic exchange between the member and the
Key2roam roaming hub, the principle of GT translation at SCCP layer is used. This ensures
correct routing in the entire SS7 network, irrespective of the carriers involved in the transport
of such signalling traffic.
To control and maintain the data roaming relations at SS7 signalling level, the Key2roam
member routes all data related signalling traffic to the Key2roam roaming hub.
More details about the principles of SS7 signalling via Key2roam are provided in the
document “Key2roam Signalling Implementation Guideline”.
The main points of network element configuration regarding the data roaming traffic are listed
here below:

2.2.1 IMSI Translation

• Translate MCC+ MNC of Key2roam community member to Comfone Key2roam GT
(E.214): 4179991

2.2.2 SCCP Routing (MAP Signalling)

• Implement Comfone GT 417999 for NP1 (E.164) and NP7 (E.214) in all GTT routing
tables: VLR / MSC, HLR, GSN, STP, etc.
• Instruct SCCP Service Provider to route Comfone GT 417999 for NP1 (E.164) and
NP7 (E.214) to Key2roam SCCP Gateway (Comfone).

2.2.3 GPRS Services

• The Key2roam roaming hub supports SS7 Signalling for data roaming. It is required
to configure SGSNs and GGSNs in order to route the GT 4179991 to the Key2roam
roaming hub.

2.3 IP Connectivity Setup

In order to be prepared for data roaming, a one-time IP network configuration at the
Key2roam member and its GRX provider is required.
This initial set-up enables each Key2roam member to establish data roaming relations to all
other members connected to the Data Roaming Platform. The establishing of new data
roaming relation does not require any additional implementation on the IP connectivity for the
Key2roam member and its GRX provider. The Data Roaming Platform takes over IP address
handling of every new roaming partner.
Access to the Data Roaming Platform respective Data Roaming Service does not require the
Key2roam member to use Comfone as GRX provider. However, using Comfone as GRX
provider does not only simplify the initial set-up, but as well as troubleshooting since a third
party does not need to be involved.

Comfone AG Carried out SR/MB 11/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

2.3.1 Responsibility for the IP Connectivity

The demarcation of the responsibility for the commercial service is presented in the following
two figures.

Key2roam members using the Comfone GRX only have to take care about its own network
elements. Comfone as GRX provider is handling all the other GRX activities and ensures
connectivity to the Data Roaming Platform.

Figure 6: Responsibility – Key2roam member with Comfone’s GRX

When a Key2roam member is connected via a third party GRX provider, the members
respective GRX provider is responsible for the connection and the service between its
network and the GRX peering point.

Figure 7: Responsibility – Key2roam member with GRX from another provider

Comfone AG Carried out SR/MB 12/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

2.3.2 Mobile Network Configuration

The firewalls at the Key2roam member have to be opened for:
• Comfone’s IP address pool (IP ranges used for the Data Roaming Platform and IP
address for the virtual SGSN/GGSN nodes):
o 195.211.12.128/25 (AS 35030)
o 195.211.13.128/25 (AS 35030)
o 195.211.12.96/27 (AS 35030)
o 195.211.13.96/27 (AS 35030)
• GTP traffic originating from / terminating to the Data Roaming Platform
• DNS queries originating from the Data Roaming Platform:
o 195.211.12.122 (AS 35030)
o 195.211.13.122 (AS 35030)
Correct BGP based routing has to be established to connect to the Data Roaming Platform at
GRX peering point.

2.3.3 GRX Network Configuration

On behalf of the Key2roam member, its GRX provider needs to configure its firewalls to be
opened for GTP and DNS traffic for Comfone IP address pool:
o 195.211.12.128/25 (AS 35030)
o 195.211.13.128/25 (AS 35030)
o 195.211.12.96/27 (AS 35030)
o 195.211.13.96/27 (AS 35030)
• Correct BGP based routing has to be established to connect to the Data Roaming
Platform at GRX peering point. This shall be established already as Comfone is a
GRX provider and peers with all other GRX providers.
Comfone is completely in charge for the IP connectivity in case that member is using
Comfone’s GRX.

2.4 DNS configuration in the visited network

The configuration of the DNS server of the visited network has to be changed that the result
of a DNS query for any APN of a HPMN will be the IP address of the Data Roaming Platform
(195.211.12.129). The message flow below illustrates the DNS resolution approach that is
required by the Data Roaming solution of Comfone.

Comfone AG Carried out SR/MB 13/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

Figure 8: DNS Message Flow for Key2roam Data Roaming

2.4.1 DNS Configuration Example

Modification in the named.conf file:

zone "mnc001.mcc123.gprs" {
// Acme Key2roam Member configuration for Key2roam Data Roaming
type master;
file "zones/mnc001.mcc123.gprs.db";
};

Creation of a zone (file name 'mnc001.mcc123.gprs.db'), that everything in domain

mnc001.mcc123.gprs is resolved to 195.211.12.129:

$ORIGIN .
$TTL 86400 ; 1 day

mnc001.mcc123.gprs IN SOA dns1.mnc001.mcc987.gprs.acme.com. (

2009240604 ; serial
28800 ; refresh (8 hours)
7200 ; retry (2 hours)
604800 ; expire (1 week)
86400 ; minimum (1 day)
)
NS dns1.mnc001.mcc987.gprs.
NS dns2.mnc001.mcc987.gprs.

$ORIGIN mnc001.mcc123.gprs.
* A 195.211.12.129

Comfone AG Carried out SR/MB 14/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

2.5 TADIG Code and TAP File Flow

Comfone is by default in the TAP/RAP loop for the community members acting a VPNM to
Key2roram acting as HPMN.
The same Key2roam Alias TADIG codes already implemented by the Key2roam member
have to be used in TAP files related to the Data Roaming traffic.

2.6 Billing System Configuration

The Key2roam member may use two different methods to identify the VPMN in their billing
systems.
• Unique IP address per Key2roam member
• RAI field in the Create PDP Context Request message.

2.6.1 Unique IP Address

The information about the real SGSNs/GGSNs IP addresses and the mapping table per each
member will be stored in a database managed by the Data Roaming Platform and is
available in the Key2roam Online Reporting System.
Based on the static mapping between the members Inter PMN IP address and the uniquely
assigned Comfone Data Roaming IP address, the full end-to-end transparency is ensured.
The billing system of the HPMN may use the unique IP addresses per Key2roam partner
network to correspond the roaming data session with the appropriate network to ensure
correct end user billing.

2.6.2 RAI Field

The provisioning of the RAI field by the VPMN is not mandatory according to the 3GPP
specifications for GTP protocol (see 4 Comfone Document References).
The Data Roaming Platform ensures the RAI field is either transferred in the original PDP
Context Request or missing RAI information is completed with the appropriate value when
the PDP Context Request is passing through the platform.

2.7 Test SIM Cards for GPRS Data Roaming Test

As part of the Key2roam agreement, a defined number of test SIM cards have to be provided
to Comfone’s SIM card manager.
Test SIM cards to be used for Data Roaming remote test have be provisioned with all
services that the Key2roam member wants to offer to its subscribers.

Comfone AG Carried out SR/MB 15/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

3 Glossary
2.5G 2.5 Generation
3G 3rd Generation
3GPP Third Generation Partnership Project
APN Access Point Name
ARPU Average Revenue Per User
BGP Border Gateway Protocol
CAMEL Customised Applications for Mobile networks Enhanced Logic
CAPv3 CAMEL Application Part version 3
DNS Directory Name Service
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GRX GPRS Roaming Exchange
GSM Global System for Mobile communications
GSMA GSM Association
GSN GPRS Support Nodes
GTP GPRS Tunnelling Protocol
GTPv0 GTP version 0
GTPv1 GTP version 1
GW Gateway
H-GGSN Home GGSN
HLR Home Location Register
HMN Home Mobile Network
HMNO Home Mobile Network Operator
IP Internet Protocol
MAP Mobile Application Part
MNO Mobile Network Operator
O&M Operation and Maintenance
PDP Packet Data Protocol
RAI Routing Area Identity
SCCP Signalling Connection Control Part
SGSN Serving GPRS Support Node
SS7 Signalling System No. 7
TAP Transferred Account Procedure
VLR Visitor Location Register
VMN Visited Mobile Network
VMNO Visited Mobile Network Operator
V-SGSN Visited SGSN

Comfone AG Carried out SR/MB 16/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland
 Key2roam
Data Roaming Implementation Guideline

4 Comfone Document References

GSMA - PRD IR.33: “GPRS Roaming Guidelines”
GSMA - PRD IR.34: “Inter-PLMN Backbone Guidelines”
GSMA - PRD IR.67: “DNS/ENUM Guidelines for Service Providers & GRX/IPX Providers”
3GPP - TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2“
3GPP - TS 29.060: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface" - GTPv1
Comfone – “Key2roam Signalling Implementation Guideline”

Comfone AG Carried out SR/MB 17/17

Nussbaumstrasse 25 Date of distribution 07.05.2010
P.O. Box Version 1.5
CH-3000 Bern 22 www.comfone.com
Switzerland