GSM Association Non-confidential

Official Document IR.38 - LTE and EPC Roaming Testing

LTE and EPC Roaming Testing

Version 1.0
03 April 2014

This is a Non-binding Permanent Reference Document of the GSMA

Security Classification: Non-confidential

Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the
Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and
information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted
under the security classification without the prior written approval of the Association.

Copyright Notice
Copyright © 2015 GSM Association

Disclaimer
The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept
any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document.
The information contained in this document may be subject to change without prior notice.

Antitrust Notice
The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy.

V1.0 Page 1 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

Table of Contents
1 Introduction 4
1.1 Scope of document 4
1.2 Objective of tests 4
1.3 Definition of Terms 5
1.4 Document Cross-References 6
2 Requirements For The Testing 7
2.1 Overview 7
2.2 Test Configuration 7
2.2.1 GTP-based LTE Roaming Configuration 7
2.2.2 PMIP-based LTE Roaming Configuration 8
2.2.3 CS Fallback / SMS over SGs Configuration 8
2.3 Prerequisites for the Network Entities 9
2.3.1 Prerequisites for LTE-only Testing 9
2.3.2 Prerequisites for CS Fallback / SMS over SGs Testing 11
2.3.3 Prerequisites for LTE+2G/3G Co-existence Testing 11
2.4 User Equipment 13
2.5 Test Equipment 14
2.5.1 Test equipment for LTE-only Testing 14
2.5.2 Test equipment for CS Fallback / SMS over SGs Testing 14
2.5.3 Test equipment for for LTE+2G/3G Co-existence Testing 14
3 Test Cases 14
3.1 LTE-only Testing 14
3.1.1 LTE-only Attach and Detach (for Non-CS Fallback / Data only Device) 14
3.1.2 LTE Cancel Location 16
3.1.3 LTE Operator Determined Barring 17
3.2 CS Fallback / SMS over SGs Testing 18
3.2.1 Combined Attach (for CS Fallback/SMS over SGs Device) 18
3.2.2 CS Fallback Mobile Originating Voice Calls 19
3.2.3 CS Fallback Mobile Terminating Voice Calls 19
3.2.4 SMS over SGs (Mobile Originated and Mobile Terminated) 20
3.3 LTE+2G/3G Co-existence Testing 21
3.3.1 Data Access from 2G/3G using PGW in HPLMN (a) over Gp Interface 21
3.3.2 Data Access from 2G/3G using PGW in HPLMN (a) over S8 Interface 22
4 Pre-Testing Data Exchange 24
4.1 General 24
4.2 Testing Contact Information 24
4.3 PLMN/IP-addressing, numbering and routing data 24
4.3.1 LTE-only testing 24
4.3.2 CS Fallback / SMS over SGs testing 24
4.3.3 LTE+2G/3G Co-existence testing 25
4.4 USIM associated data supplied by PLMN (a) 25
4.5 Inter-PLMN Connection Parameters 25

V1.0 Page 2 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

4.6 IP-Server Information 25

5 Test Cases Excel Sheet 26
Annex A Document Management 27
A.1 Document History 27
Other Information 27

V1.0 Page 3 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

1 Introduction
1.1 Scope of document
This document is the specification of the Interworking, Roaming Expert Group (IREG) end-
to-end functional capability tests for services over Long Term Evolution (LTE) (LTE data,
Circuit Switch (CS) Fallback voice and SMS over SGs) relating to the international roaming
of a User Equipment (UE), belonging to a Home Public Land Mobile Network (HPLMN) (a),
to and within a visited PLMN (VPLMN) (b).

Whilst it is expected that roaming will be a bilateral activity between two PLMNs, please note
that this document is written in a unidirectional context. Hence roaming is taking place by a
UE (a) to VPLMN (b) only. There is no reference to a UE (b) visiting PLMN (a).

To complete IREG end-to-end functional capability tests for bilateral roaming, it is necessary
to perform the tests in this document twice: the second time the real identities of PLMN (a)
and PLMN (b) are swapped.

GSMA Permanent Reference Document (PRD) IR.23 [1] defines the scope and purpose of
each stage of testing.

GSMA PRD IR.88 [5] defines the LTE roaming and LTE+2G/3G co-existence guidelines. For
the 3GPP Release to be supported in each network, it is recommended to follow the
guidelines in IR.88 [5].

This document does not cover:

 Testing of Voice and Short Message Service (SMS) over LTE using IMS (See
IREG PRD IR.25 [2])
 Testing of Transferred Account Procedure (TAP), billing applications and any
inter-PLMN financial statement; (see TADIG PRD TD.41 [6]). However the
production of a Toll Ticketing file, for use in the TADIG Stage 3 testing is
included.
 Definition of operation and maintenance procedures such as contact points for
fault reporting and notification of planned works. (See IREG PRD IR.23 [1]).

1.2 Objective of tests

The fundamental objective of this testing is to confirm the capability of LTE data/CS
Fallback/SMS over SGs services which users will receive when roaming from their
HPLMN(a) to VPLMN(b). Consequently the tests are restricted to top-level capability testing.
There is no provocative or inopportune behaviour testing: this type of testing forms part of
the Stage 1 testing (see IREG PRD IR.23 [1]).

The overall objective of the tests is to confirm that functionality and features, which are
already known to operate correctly within each separate PLMN, will also operate correctly for
Inter-PLMN roaming.

Not all possible services should be tested.

In addition to the handling of the tests itself the collection/comparison of charging information
respective the generation of charging detailed records (CDR) is described.

V1.0 Page 4 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

The specific objectives are to prove that procedures defined in Section 2.1 of this document
operate correctly.

The actual number of repetitions of the test cases is for bilateral agreement between the
HPLMN and VPLMN.

In order to maximize the efficiency of testing, the test cases have been specified so as to
minimize the requirement for simultaneous joint activity by both PLMN (a) and PLMN (b).
This concerns mainly the administration of mobile subscriber data in the HSS.

Accordingly, the program of testing forms three distinct components:

i. HPLMN(a) issues pre-programmed USIMs and programmes HSS

ii. VPLMN(b) performs tests
iii. VPLMN(b) and HPLMN(a) discuss results

1.3 Definition of Terms

Term Description
APN Access Point Name
BSS Base Station Subsystem
CDR Charging Detailed Record
CCITT International Telegraph and Telephone Consultative Committee
CS Circuit Switched
CSFB Circuit-Switched Fallback
DNS Domain Name System
EPC Evolved Packet Core
EPS Evolved Packed System
FQDN Fully Qualified Domain Name
FTP File Transfer Protocol
GGSN Gateway GPRS Support Node
GMSC Gateway Mobile Services Switching Centre
GPRS Generic Packet Radio Access
GTP GPRS Tunnelling Protocol
HSS Home Subscriber Server
HPLMN Home PLMN
HTTP Hypertext Transport Protocol
IMSI International Mobile Subscriber Identifier
IP Internet Protocol
ISP Internet Service Provider
LTE Long Term Evolution
MAP Mobility Application Part
MME Mobility Management Entity
MSC Mobile Services Switching Centre

V1.0 Page 5 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

ODB Operator Determined Barring

PCRF Policy and Charging Rules Function
PDN Packet Data Network
PDP Packet Data Protocol
PLMN Public Land Mobile Network
PMIP Proxy Mobile IP
PGW PDN Gateway
SCCP Signalling Connection Control Part
SGSN Serving GPRS Support Node
SGW Serving Gateway
SMS Short Message Service
SMSC Short Message Service Centre
TCAP Transaction Capabilities Application Part
TCP Transmission Control Protocol
UDP User Datagram Protocol
UE User Equipment
USIM Universal Subscriber Identity Module
VMSC Visited Mobile Services Switching Centre
VLR Visitor Location Register

1.4 Document Cross-References

Document
Ref Number Title
1 GSMA PRD IR.23 Organisation of GSM International Roaming Tests
2 GSMA PRD IR.25 VoLTE Roaming Testing
End-to-End Functional Capability Test Specification for Inter-
3 GSMA PRD IR.35
PLMN GPRS Roaming
4 GSMA PRD IR.67 DNS/ENUM Guidelines for Service Providers
5 GSMA PRD IR.88 LTE and EPC Roaming Guidelines
6 GSMA PRD TD.41 Testing the Transferred Account Procedure (TAP)
General Packet Radio Service (GPRS); Service description; Stage
7 3GPP TS 23.060
2
8 3GPP TS 29.303 Domain Name System Procedures; Stage 3

V1.0 Page 6 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

2 Requirements For The Testing

2.1 Overview
The test cases are divided in three (3) groups:

1. LTE-only services for UE (a) roaming to VPLMN (b) operates correctly by testing the
following procedures:
a) LTE Attach (including PDN Connection set up and Detach)
b) LTE Cancel Location
c) LTE Operator Determined Barring

2. CS Fallback / SMS over SGs between UE1 (a) and UE2 (a) roaming to VPLMN (b)
operates correctly by testing the following procedures:
a) Combined Attach
b) CS Fallback – mobile originating and terminating voice calls
c) SMS over SGs – mobile originated and terminated SMS

3. 2G/3G data services (i.e. web browsing) for UE (a) roaming to VPLMN (b) operates
correctly by testing the following procedures:
a) Packet Data Protocol (PDP) Context Activation using Gp interface towards PGW
b) PDP Context Activation using S4/S8 interface towards SGW/PGW

For the 2G/3G data service using S4/S8, the testing of S8 interface (using GTP or PMIP) is
assumed to be covered in the "LTE-only" test cases (see the prerequisites in Section 2.3.3).
Thus this PRD does not provide specific test cases for GTP and PMIP variants for the
2G/3G data service.

Each operator has to make sure that the Access Point Name (APN) resolution algorithms
are implemented in correctly in their Serving GPRS Support Node (SGSN) and MME
according to GSMA PRD IR.88 [5] and GSMA PRD IR.67 [4]

2.2 Test Configuration

2.2.1 GTP-based LTE Roaming Configuration

The test configuration for LTE Roaming using GPRS Tunnelling Protocol (GTP)-based S8
interface is specified below.

V1.0 Page 7 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

Country (a) Country (b)

PLMN(a) PLMN(b)
UE 1
USIM(a)
RNS
ROOT DNS
/BSS

SGSN SGW
Diameter eNB
HSS M
Edge Agent

GPRS / IP Diameter MME

HPCRF Intra PLMN EXCHANGE Intra PLMN Edge Agent

M GGSN
PGW
PGW
LOCAL DNS
LOCAL DNS

INTRANET/ISP
INTRANET/ISP

RADIUS/DHCP-SERVER RADIUS/DHCP-SERVER

M = Monitor

Figure 2.2.1-1: GTP based LTE Roaming Configuration

2.2.2 PMIP-based LTE Roaming Configuration

The test configuration for LTE Roaming using Proxy Mobile IP (PMIP)-based S8 interface is
specified below.

Country (a) Country (b)

PLMN(a) PLMN(b)
UE 1
USIM(a)
RNS
/BSS
ROOT DNS

HSS SGSN SGW eNB

M
VPCRF
Diameter
Edge Agent
GPRS / IP Diameter MME
HPCRF Intra PLMN EXCHANGE Intra PLMN Edge Agent

M GGSN
PGW
PGW
LOCAL DNS
GGSN
LOCAL DNS

INTRANET/ISP
INTRANET/ISP

RADIUS/DHCP-SERVER RADIUS/DHCP-SERVER

M = Monitor

Figure 2.2.2-1: PMIP based LTE Roaming Configuration

2.2.3 CS Fallback / SMS over SGs Configuration

The test configuration for CS Fallback and SMS over SGs is specified below.

V1.0 Page 8 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

PLMN(a) PLMN(b)
UE1(a)
USIM(a)
HLR/HSS MME eNB

UE2(a)
VLR/ RNS/ USIM(a)
GMSC
VMSC BSS

PSTN

Figure 2.2.3-1: CS Fallback / SMS over SGs Configuration

2.3 Prerequisites for the Network Entities

2.3.1 Prerequisites for LTE-only Testing

Towards a first introduction of LTE Roaming, the following prerequisites are assumed:
1. UE supports necessary LTE capabilities for roaming in VPLMN (b).
2. The HSS contains LTE subscription data and routing information (PDN type, PDN
address, APN, and VPLMN address allowed (only applicable when Local Breakout is
used)). These subscription data are permanent data in the HSS and have to be inserted
for the tests. The HSS is accessible from the MME via the S6a interface. For roaming
UEs, the HSS is in a different PLMN than the current MME. The MME is updated with
new EPS subscription data with the "Update Location Request" or the “Insert Subscriber
Data” procedures.

IMSI is the primary key to the Evolved Packed System (EPS) subscription data stored in
the HSS.

The relevant parameters for the IREG testing in the HSS must be configured according
to the following table:

Field Description
IMSI IMSI is the main reference key.
MSISDN The basic Mobile Subscriber ISDN Number (MSISDN) of
the UE (Presence of MSISDN is optional).
MME Capabilities Indicates the capabilities of the MME with respect to
core functionality e.g. regional access restrictions.
ODB parameters Indicates that the status of the operator determined
barring
Access Restriction Indicates the access restriction subscription information.
EPS Subscribed Charging The charging characteristics for the MS, e.g. normal,
Characteristics prepaid, flat-rate, and/or hot billing subscription.
Trace Reference Identifies a record or a collection of records for a
particular trace.

V1.0 Page 9 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

Trace Type Indicates the type of trace, e.g. HSS trace, and/or MME/
Serving GW / PDN GW trace.
OMC Identity Identifies the OMC that shall receive the trace record(s).
Subscribed-UE-AMBR The Maximum Aggregated uplink and downlink MBRs to
be shared across all Non-GBR bearers according to the
subscription of the user.
APN-OI-Replacement Indicates the domain name to replace the APN OI when
constructing the PDN GW FQDN upon which to perform
DNS queries. This replacement applies for all the APNs
in the subscriber's profile.
RFSP Index An index to specific RRM configuration in the E-UTRAN
URRP-MME UE Reachability Request Parameter indicating that UE
activity notification from MME has been requested by the
HSS.
Each subscription profile contains one or more PDN subscription contexts:
Context Identifier Index of the PDN subscription context.
PDN Address Indicates subscribed IP address(es).
PDN Type Indicates the subscribed PDN Type (IPv4, IPv6, IPv4v6).
Access Point Name (APN) A label according to DNS naming conventions
describing the access point to the packet data network
(or a wildcard).
EPS subscribed QoS profile The bearer level QoS parameter values for that APN's
default bearer (QCI and ARP).
Subscribed-APN-AMBR The maximum aggregated uplink and downlink MBRs to
be shared across all Non-GBR bearers, which are
established for this APN.
EPS PDN Subscribed Charging The charging characteristics of this PDN Subscribed
Characteristics context for the MS, e.g. normal, prepaid, flat-rate, and/or
hot billing subscription. The charging characteristics are
associated with this APN.
VPLMN Address Allowed Specifies whether for this APN the UE is allowed to use
the PDN GW in the domain of the HPLMN only, or
additionally the PDN GW in the domain of the VPLMN.
PDN GW identity The identity of the PDN GW used for this APN. The PDN
GW identity may be either an FQDN or an IP address.
The PDN GW identity refers to a specific PDN GW.
PDN GW Allocation type Indicates whether the PDN GW is statically allocated or
dynamically selected by other nodes. A statically
allocated PDN GW is not changed during PDN GW
selection.
List of APN - PDN GW ID relations (for PDN subscription context with wildcard APN):
APN - P GW relation #n The APN and the identity of the dynamically allocated
PDN GW of a PDN connection that is authorized by the
PDN subscription context with the wildcard APN. The
PDN GW identity may be either an Fully Qualified
Domain Name (FQDN) or an IP address. The PDN GW

V1.0 Page 10 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

identity refers to a specific PDN GW.

Table 1Table 2.3.1-1: HSS Configuration for LTE-only roaming

3. S8 interface is implemented in HPLMN(a) and VPLMN(b) and both HPLMN(a) and

VPLMN(b) are using the same protocol (e.g. GTP or PMIP)
4. S9 interface is implemented in HPLMN(a) and VPLMN(b) (when PMIP is used on S8).
5. MME and visited Policy and Charging Rules Function (vPCRF) (if PMIP is used) has
access to Domain Name System (DNS) functionality.
6. VPMLN MME local policies are configured for the Quality of Service.
7. Configuration of the test environment for transparent or non-transparent access to
Intranet/ Internet Service Provider (ISP) (The key point for the access of an Intranet or an
ISP infrastructure is the APN-Network-Identifier). This is sent by the UE during Initial
Attach or is set by default by the HSS. The APN-Network Identifier defines to which
external network the PGW is connected. This means, in detail, the interface of the PGW
to an external network. This external interface at the PGW is connected to the
infrastructure providing Intranet functionality (e.g. local HTTP-Server) or similar to a
Serverfarm providing ISP functionality (HTTP-Server, Proxy-Server or FTP-Server with
connection to the external Internet). This mechanism provides the physical path to the
Intranet/ISP-functionality. However each operator needs to guarantee that the APN-
resolution algorithms are implemented correctly in his MME accordingly.
8. Dynamic IP Address allocation for access to Intranet/ISP.

2.3.2 Prerequisites for CS Fallback / SMS over SGs Testing

For CS Fallback / SMS over SGs testing, the following prerequisites are assumed:
1. IREG tests for legacy 2G/3G CS domain services have already been performed between
HPLMN (a) and VPLMN (b) according to PRD IR.23 [1].
2. IREG tests for LTE-only services have already been performed between HPLMN (a) and
VPLMN (b) as specified in this document.
3. UE supports necessary CS Fallback and SMS over SGs capabilities for roaming in
VPLMN (b).
4. SGs interface is implemented between MME and Mobile Switching Centre/ Visitor
Location Register (MSC/VLR) in VPLMN (b).
5. Prerequisites for LTE-only testing have been met according to Section 2.2.4.1.

2.3.3 Prerequisites for LTE+2G/3G Co-existence Testing

For LTE+2G/3G Co-existence testing, the following prerequisites are assumed:
1. IREG tests for legacy 2G/3G PS domain services have already been performed between
HPLMN (a) and VPLMN (b) according to PRD IR.23 [1].
2. IREG tests for LTE-only services have already been performed between HPLMN (a) and
VPLMN (b) as specified in this document.
3. LTE and GPRS UE supporting the network operation modes in VPLMN (b).
4. HSS contains EPS subscription data for LTE roaming. Prerequisites are same as
described in Section 2.2.4.1.

The HSS contains GPRS and EPS subscription data and routing information (e.g.
PDP/PDN type (S)) for 2G/3G roaming.

These subscription data are permanent data in the HSS and must be inserted for the
tests. The HSS is accessible from the SGSN via the Gr interface. For roaming UEs, the

V1.0 Page 11 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

HSS is in a different PLMN than the current SGSN. The SGSN is updated with new
GPRS and EPS subscription data with the “Insert Subscriber Data” procedure.

IMSI is the primary key to the GPRS subscription data stored in the HSS.

If Gn/Gp interface is used for 2G/3G roaming, the subscription information stored in
HSS/HLR for 2G/3G roaming is defined in "Prerequisites for GPRS only roaming" table as
specified in PRD IR.35 [3].

If S4/S8 interfaces are used for 2G/3G roaming, the relevant parameters “GPRS
Subscription Data” for the IREG testing in HSS must be configured according to the
following table:

HSS GPRS Subscription Data:

Field Description
IMSI IMSI is the main reference key.
MSISDN The basic MSISDN of the MS
Subscribed Charging The charging characteristics for the MS e.g. normal, prepaid, flat-
Characteristics rate, and /or hot billing subscription
Trace Reference Identifies a record or a collection of records for a particular trace.
Trace Type Indicates the type of trace, e.g. MSC/BSS trace, HLR trace, and/or
SGSN/GGSN/BSS trace.
OMC Identity Identifies the OMC that shall receive the trace record(s)
SMS Parameters SMS-related parameters, e.g. operator-determined barring
GPRS-CSI Optional GPRS CAMEL Subscription information, see TS23.016
MG-CSI Optional Mobility Management for GPRS CAMEL subscription
information, see TS23.016
APN-OI Replacement Indicates the domain name to replace the APN-OI when
constructing the GGSN FQDN upon which to perform a DNS
resolution. This replacement applies for all the APNs in the
subscribers' profile.
ODB for PS parameters Indicates the status of the operator determined barring for packet
oriented services.
Access Restriction Indicates the access restriction subscription information (Note: the
access restriction applies to both packet and circuit oriented
services).
RFSP Index An index to specific RRM configuration in the UTRAN/GERAN
Each IMSI contains zero or more of the following PDP context subscription records:
PDP Context Identifier Index of the PDP context
PDP Type PDP type, e.g., PPP or IP (IPv4, IPv6, IPv4v6)
PDP Address PDP address, e.g., and IP address. This field shall be empty if
dynamic addressing is allowed.
Access Point Name A label according to DNS naming conventions describing the access
point to the external packet data network.

V1.0 Page 12 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

In case of “Wild Card APN” this field shall be filled with

QoS Profile Subscribed The quality of service profile subscribed. QoS Profile Subscribed is
the default level if a particular QoS profile is not requested.
VPLMN Address Allowed Specifies whether the MS is allowed to use the APN in the domain
of the HPLMN only, or additionally the APN in the domain of the
VPLMN.
PDP Context Charging The charging characteristics of this PDP Bearer Context e.g.
Characteristics normal, prepaid, flat-rate and/or hot billing
EPS subscribed QoS profile The EPS bearer level QoS parameter values for that APN's default
bearer (QCI and ARP)
APN-AMBR The maximum aggregated uplink and downlink MBR values to be
shared across all Non-GBR EPS bearers, which are established for
this APN.

Table 2.3.3-1: Additional HSS Configuration for 2G/3G Roaming using S4/S8
interface

5. Towards GPRS no supplementary services are invoked.

6. The Gp-Interface or S8-Interface is implemented between HPLMN (a) and VPLMN (b).
7. SGSN in VPLMN (b) has access to DNS functionality.
8. Configuration of the test environment for transparent or non-transparent access to
Intranet/ISP (The key point for the access of an Intranet or an ISP infrastructure is the
APN-Network-Identifier). This is sent by mobile during PDP-context activation or is set by
default by the SGSN. The APN-Network Identifier defines to which external network the
PGW is connected. This means, in detail, the interface of the PGW to an external
network. This external interface at the PGW (a) is connected to the infrastructure
providing Intranet functionality (e.g. local HTTP-Server) or similar to a Serverfarm
providing ISP functionality (HTTP-Server, Proxy-Server or FTP-Server with connection to
the external Internet). This mechanism will provide the physical path to the Intranet/ISP-
functionality. However each operator has to make sure that the APN-resolution
algorithms are implemented correctly in his SGSN according to 3GPP TS 23.060 [7] and
Annex A of 3GPP TS 23.060 [7].
9. Dynamic IP Address allocation for access to Intranet/ISP.

2.4 User Equipment

The UE described in this section is necessary for undertaking the test cases described in
this document. This applies to all groups specified in Section 2.1 of this document:
1. Two UEs supplied by VPLMN (b).
2. Two LTE compatible USIMs supplied by HPLMN (a).
The supply of additional USIMs may be agreed by the HPLMN (a) and VPLMN (b),
typically for the purposes of:

a) Spare cards in case of failure

b) Allocation from different HSSs

3. It shall be possible to specify what types of UEs are supplied for testing between
operator agreement (HPLMN (a) and VPLMN (b)).

V1.0 Page 13 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

2.5 Test Equipment

2.5.1 Test equipment for LTE-only Testing

The availability of a SGi, S6a, S8, S9 (when PMIP S8 is used) and DNS interface IP testing
and monitoring equipment is highly advisable.
It is also recommended to have sample files and applications for data transfer testing.

2.5.2 Test equipment for CS Fallback / SMS over SGs Testing

The availability of an International Telegraph and Telephone Consultative Committee
(CCITT) # 7 tester able to decode Signalling Connection Control Part (SCCP), Transaction
Capabilities Application Part (TCAP), Mobile Application Part (MAP) is highly advisable, but
not strictly necessary for these tests. However it is essential for any analysis of test case
failures.
Clock capable of being used to allow testing personnel to record call start and chargeable
start (that is, answer) time of calls to an accuracy of better than five seconds is required. If
possible, the clock shall be adjusted to be in alignment with the internal MSC clock which is
used for the Toll Ticketing function.
Stopwatch capable of measuring perceived chargeable duration of calls to an accuracy of
one second.

2.5.3 Test equipment for for LTE+2G/3G Co-existence Testing

The availability of a CCITT # 7 tester able to decode SCCP, TCAP, and MAP (for Gr
interface) is highly advisable, but not strictly necessary for these tests. However it is
essential for any analysis of test case failures.
The availability of a SGi, Gn, Gp, S6a, S6d, S8, S4 and DNS interface IP testing and
monitoring equipment is highly advisable.
It is also recommended to have sample files and applications for data transfer testing.
3 Test Cases
3.1 LTE-only Testing

3.1.1 LTE-only Attach and Detach (for Non-CS Fallback / Data only Device)

3.1.1.1 Preconditions
1. UE1 (a) contains USIM of HPLMN (a).
2. No valid EMM contexts are established for UE1 (a).
3. HSS (a) record contains basic service information including EPS subscription data.
4. No valid PDN connection is established in the UE1 (a).
5. One EPS bearer context subscription record exists in HSS (a) where APN(S) = APN(R).
6. VPLMN is not allowed for selected EPS context subscription records.
7. A PDN Address is not sent by UE1 (a) and is not present in an EPS context subscription
record. (Dynamic address allocation).

3.1.1.2 Action
1. Power-up UE1 (a) and perform LTE Attach only on VPLMN (b).
2. Check EMM contexts in UE1 (a) and MME (b) for the IMSI/GUTI /MSISDN of UE1 (a).

V1.0 Page 14 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

3. Check PDN connection is established for the UE by performing HTTP browsing.

4. Power-off UE1(a) and perform LTE Detach procedure.

3.1.1.3 Information Flow

The information flow for LTE Attach procedure is described as follows:
UE eNodeB MME EIR Serving GW PDN GW VPCRF HPCRF HSS

1. Attach Request
2. Attach
Request

4. Identity Request
4. Identity Response
5a. Authentication / Security
5b. Identity Request/Response
5b. ME Identity Check
6. Ciphered Options Request
6. Ciphered Options Response

8. Update Location Request

11. Update Location Ack

12. Create Session Request

When GTP is used

13. Create Session Request
14. PCEF Initiated IP-CAN Session
Establishment/Modification

15. Create Session Response

When PMIP is used

16. Gateway Control Session
Establishment Procedure

17. Proxy Binding Update

18. IP-CAN Session

Establishment
Procedure
19. Proxy Binding Ack

20. Gateway Control and QoS

Rules Provison Procedure

21. Create Session Response

22. Initial Context Setup Request / Attach Accept
23. RRC Connection Reconfiguration
24. RRC Connection Reconfiguration Complete
25. Initial Context Setup Response
26. Direct Transfer
27. Attach Complete

Figure 3.1.1.3-1: LTE Attach Procedure

The information flow for LTE Detach procedure is described as follows:

V1.0 Page 15 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

UE eNodeB MME Serving GW PDN GW VPCRF HPCRF

1. Detach Request
2. Detach
Request
3. Delete Session Request
4. Delete Session Response

When GTP is used

5. Delete Session Request

6. PCEF Initiated IP-CAN

Session Termination

7. Delete Session Response

When PMIP is used

8 Gateway Control Session
Termination Procedure

9. Proxy Binding Update

10. IP-CAN Session

Termination Procedure

11. Proxy Binding Ack

12. Detach Accept

Figure 3.1.1.3-2: LTE Detach Procedure

3.1.1.4 Expected Result

1. Successful result if UE1 (a) is in EMM-REGISTERED and ECM-CONNECTED state.
2. Successful result if valid EMM contexts are established in the UE1 (a) and MME (b).
3. Successful result if PDN Connectivity towards the default APN is established.
4. Successful result if LTE Detach procedure for UE1 (a) is completed.

3.1.1.5 Comments
This test case confirms the Attach (including PDN connection establishment), and Detach
procedures. It checks the support of the relevant Diameter operations.

3.1.2 LTE Cancel Location

3.1.2.1 Preconditions
1. MME (b) in VPLMN (b) contains EPS subscription information of UE1 (a).
2. PDN connectivity for UE1 (a) is activated.

3.1.2.2 Action
HPLMN (a) personnel deletes UE1 (a) EPS-subscription from HSS (a) either using HSS`s
Man-Machine Interface or via Administrative Data Centre (ADC) input to HSS (a).

V1.0 Page 16 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

3.1.2.3 Information Flow

The information flow for LTE Cancel Location procedure is described as follows:
UE eNodeB MME Serving GW PDN GW vPCRF hPCRF HSS

1. Cancel Location
2. Detach Request

3. Delete Session Request

When GTP is used

4. Delete Session Request

5. PCEF-Initiated IP-CAN
Session Termination
Procedure
6. Delete Session Resonse

When PMIP is used

7. Gateway Control Session Termination

Procedure
8. Proxy Binding Update

9. PCEF-Initiated IP-CAN
Session Termination
Procedure
10. Proxy Binding Ack

11. Delete Session Response

12. Detach Accept

13. Cancel Location ACK

Figure 3.1.2.3-1: LTE Cancel Location Procedure

3.1.2.4 Expected Result

1. If GTP is used for S8, successful result if records in MME (b), SGW (b), PGW (a) and
hPCRF (a) for UE1 (a) has been erased and PDN connectivity for UE1 (a) has been
deactivated.
2. If PMIP is used for S8, successful result if records in MME (b), SGW (b), PGW (a),
vPCRF (b) and hPCRF (a) for UE1 (a) has been erased and PDN connectivity for UE1
(a) has been deactivated.

3.1.2.5 Comments
This test case confirms that the “Cancel Location” procedure between HSS (a) and MME (b)
and the subsequent “Detach initiated by the network" procedure operate correctly.

3.1.3 LTE Operator Determined Barring

3.1.3.1 Preconditions
UE1 (a) is attached to VPLMN (b) and has a PDN connectivity.

V1.0 Page 17 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

3.1.3.2 Action
1. HPLMN (a) personnel activates Operator Determined Barring (ODB) for PDN
connectivity for UE1 (a) from HSS (a) either using HSS`s Man-Machine Interface or via
Administrative Data Centre (ADC) input to HSS (a).
2. Check MME (b) for records of UE1(a).
3. Try to make a LTE-attach from UE1 (a) and send attach request from UE1 (a).

3.1.3.3 Information Flow

The information flow for LTE ODB procedure is described as follows:
UE MME HSS

1. Insert Subscriber Data

2. Attach Request

3. Reject

Figure 3.1.3.3-1: LTE Operator Determined Barring Procedure

3.1.3.4 Expected Result

Successful result if MME (b) record for UE1 (a) contains ODB information, attach request is
rejected and no PDN connectivity establishment are successful.

3.1.3.5 Comments
This test case confirms that the “Operator Determined Barring” procedure between HSS (a)
and MME (b) operates correctly.

3.2 CS Fallback / SMS over SGs Testing

3.2.1 Combined Attach (for CS Fallback/SMS over SGs Device)

3.2.1.1 Preconditions
1. UE1 contains USIM of HPLMN(a).
2. UE1 (a) is either CS Fallback or SMS over SGs capable.
3. Neither MSC/VLR nor MME record exists for MS.
4. HLR/HSS record contains basic service information.

3.2.1.2 Action
1. Power-up UE1 (a) and perform Combined Attach procedure on VPLMN (b)'s LTE
network.
2. Check MME and MSC/VLR record for the IMSI/MSISDN of UE1.

V1.0 Page 18 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

3.2.1.3 Information Flow

Editor’s Note: The information flow for Combined Attach is not provided in this version of
the document.

3.2.1.4 Expected Result

1. Successful result if MSC/VLR and MME record is identical to the pre-testing information
supplied by PLMN (a).
2. Unsuccessful result if any of the CS Fallback / SMS over SGs services tested by this
document or all of the information is missing.

3.2.1.5 Comments
This test case confirms operation of Update Location and Insert Subscriber Data procedures
using SGs interfaces. It checks the support of the relevant SGs-AP, MAP and Diameter
(S6a) operations, TCAP processes and SCCP addressing for both E.214 and E.164 Global
Titles, between the HLR/HSS (a) and VMSC (b).

3.2.2 CS Fallback Mobile Originating Voice Calls

3.2.2.1 Preconditions
1. UE1 (a) is CS Fallback capable.
2. UE1 (a) is camping on LTE.
3. UE2 (a) has location updated successfully in VPLMN (b).

3.2.2.2 Action
1. UE1 (a) establishes call to UE2(a).
2. Call answered.

3.2.2.3 Information Flow

Editor’s Note: The information flow for CS Fallback Mobile Originating Voice Calls is not
provided in this version of the document.

3.2.2.4 Expected Result

Successful result if call is established.

3.2.2.5 Comments

This test case confirms Mobile Originated call procedures using CS Fallback for
roamers. It checks the support of originating call setup procedures using SGs
interface.

3.2.3 CS Fallback Mobile Terminating Voice Calls

3.2.3.1 Preconditions
1. UE1 (a) is CS Fallback capable.
2. UE1 (a) is camping on LTE.
3. UE2 (a) has location updated successfully in VPLMN (b).

V1.0 Page 19 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

3.2.3.2 Action
1. UE2 (a) establishes call to UE1 (a).
2. Call answered.

3.2.3.3 Information Flow

Editor’s Note: The information flow for CS Fallback Mobile Terminating Voice Calls is not
provided in this version of the document.

3.2.3.4 Expected Result

Successful result if call is established.

3.2.3.5 Comments

This test case confirms Mobile Terminated call procedures using CS Fallback for
roamers. It checks the support of terminating call setup procedures using SGs
interface.

3.2.4 SMS over SGs (Mobile Originated and Mobile Terminated)

3.2.4.1 Preconditions
1. SMS-MO/MT is provisioned in HLR subscription. UE1 (a) and UE2 (a) are registered in
VPLMN (b).
2. UE1 (a) and UE2 (a) are both SMS over SGs capable.
3. UE1 (a) and UE2 (a) are camping on LTE.

3.2.4.2 Action
1. Switch on UE1 (a) and UE2 (a).
2. Use UE1 (a) to transmit a 160 character Short Message to UE2 (a) via SMSC in HPLMN
(a).
3. Await delivery of Short Message to UE2 (a) on LTE.
4. Check contents of Short Message with those transmitted.

3.2.4.3 Information Flow

Editor’s Note: The information flow for SMS over SGs is not provided in this version of the
document.

3.2.4.4 Expected Result

Successful result if Short Message is correctly delivered within two (2) minutes of switching
UE2 (a) on.

3.2.4.5 Comments
This test case confirms correct operation of SMS over SGs - Mobile Originated / Terminated
for roamers.

V1.0 Page 20 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

3.3 LTE+2G/3G Co-existence Testing

3.3.1 Data Access from 2G/3G using PGW in HPLMN (a) over Gp Interface

3.3.1.1 Preconditions
1. UE1 (a) is GPRS-Attached in VPLMN (b) and camping on 2G/3G (e.g. UE in STANDBY
or READY state for 2.5G). The UE1 (a)’s LTE capability may be disabled manually to
fulfil this precondition.
2. No valid PDP contexts are established in the UE1 (a).
3. PDP context subscription record(s) exists in HSS (a) where PDP type(S) = PDP type(R).
4. One PDP context subscription record exists in HSS (a) where APN(S) = APN(R).
5. VPLMN not allowed for selected PDP context subscription records.
6. Access Point Name (APN) resolution algorithms are implemented correctly in SGSN
and PGW according to GSMA PRD IR.88 [5] and GSMA PRD IR.67 [4].

3.3.1.2 Action
1. UE1 (a) performs “Activate PDP Context Request”. PDP type (R) is sent by UE1 (a).
2. A PDP Address is not sent by UE1 (a) and is not present in a PDP context subscription
record. (Dynamic address allocation).
3. APN (R) (Network-ID, no Operator-ID) is sent by UE1 (a).
4. Pre-defined file is requested/transferred from External Network (Network-ID) to UE1 (a)
by accessing HTTP-server over WEB-browsing.
5. UE1 (a) performs “Deactivate PDP Context Request”.

3.3.1.3 Information Flow

The information flow for the procedures to support data access from 2G/3G using PGW in
HPLMN (a) over Gp interface is described as follows:

VPLMN HPLMN

APN:Intranet/ISP
HSS
VPLMN add. not allowed

SGSN
DNS (including S-NAPTR procedure) success

DNS (as per 3GPP TS 29.303)

Internet/ISP.apn.epc.mnc123.mcc888.3gppnetwork.org (HPLMN)
mnc123.mcc456.gprs (VPLMN)

VGGSN HPGW
APN:Intranet/ISP.mnc123.mcc456.gprs APN: Internet/ISP.apn.epc.mnc123.mcc888.3gppnetwork.org

Figure 3.3.1.3-1: Data access from 2G/3G using PGW in HPLMN (a) over Gp interface

V1.0 Page 21 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

3.3.1.4 Expected Result

1. SGSN (b) receives APN (R) sent by UE1 (a).
2. SGSN (b) selects PDP context subscription record (APN(S), APN(S) = (APN(R)) and
sets selection mode parameter to “subscribed”.
3. SGSN interrogates DNS-Functionality using procedures defined in 3GPP TS29.303 [8]
with selected APN with appended HPLMN APN-Operator-ID.
4. Selected APN is translated to a PGW-Address in the HPLMN (a).
5. SGSN (b) returns an “Activate PDP Context Accept” message to the UE1 (a) including
PDP type and PDP address.
6. Valid PDP contexts are established in the UE1 (a).
7. Connection to Network specified by APN (Network-ID) is established.
8. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors
after using HTTP-Service.
9. EPS Bearer Context is deactivated, UE1 (a) performs "Deactivate PDP Context
Request".

3.3.1.5 Comments
This test case confirms PDP context activation/deactivation towards a home PGW (a) over
Gp interface with:
1. APN (R) is not empty; (Network-ID, no Operator-ID).
2. Setting of APN (Operator-ID) by subscription for HPLMN (a) = (APN(S)).
3. Setting up IP-tunnel connections (GTP, IP, UDP/TCP).
4. Root address lookup and dynamic address allocation.

If the PDP context activation procedure fails or if the SGSN returns an “Activate PDP
Context Reject” (Cause, PDP Configuration Options) message, then the user may attempt
another activation to the same APN up to a maximum number of attempts.

3.3.2 Data Access from 2G/3G using PGW in HPLMN (a) over S8 Interface

3.3.2.1 Preconditions
1. UE1 (a) is GPRS-Attached in VPLMN (b) (e.g. UE in STANDBY or READY state for
2.5G). The UE1 (a)’s LTE capability may be disabled manually to fulfil this precondition.
2. No valid EPS Bearers are established in the UE1 (a). The UE1 (a)’s LTE capability may
be disabled manually to fulfil this precondition.
3. EPS Bearer subscription record(s) exists in HSS (a) where PDN type(S) = PDN type(R).
4. One PDN context subscription record exists in HSS (a) where APN(S) = APN(R).
5. VPLMN not allowed for selected EPS Bearer context subscription records.

3.3.2.2 Action
1. UE1 (a) performs “Activate PDP Context Request”. PDP type (R) is sent by UE1 (a).
2. A PDN Address is not sent by UE1 (a) and is not present in an EPS Bearer context
subscription record. (Dynamic address allocation).
3. APN (R) (Network-ID, no Operator-ID) is sent by UE1 (a).
4. Pre-defined file is requested/transferred from External Network (Network-ID) to UE1 (a)
by accessing HTTP-server over WEB-browsing.
5. UE1 (a) performs “Deactivate PDP Context Request”.

V1.0 Page 22 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

3.3.2.3 Information Flow

The information flow for the procedures to support data access from 2G/3G using PGW in
HPLMN (a) over S8 interface is described as follows:

VPLMN HPLMN

HSS
VPLMN add. not allowed

APN:Intranet/ISP DNS (including S-NAPTR procedure) success

SGSN

DNS DNS (as per 3GPP TS 29.303)

(as per 3GPP TS 29.303) SGW Internet/ISP.apn.epc.mnc123.mcc888.3gppnetwork.org (HPLMN)
to select SGW
mnc123.mcc456.gprs (VPLMN)

VGGSN HPGW
APN:Intranet/ISP.mnc123.mcc456.gprs APN: Internet/ISP.apn.epc.mnc123.mcc888.3gppnetwork.org

Figure 3.3.2.3-1: Data access from 2G/3G using PGW in HPLMN (a) over S8 interface

3.3.2.4 Expected Result

1. SGSN (b) receives APN (R) sent by UE1 (a).
2. SGSN (b) selects EPS Bearer subscription record (APN(S), APN(S)=(APN(R)) and sets
selection mode parameter to “subscribed”.
3. SGSN interrogates DNS-Functionality using procedures defined in 3GPP TS29.303 [8]
with selected APN with appended HPLMN APN-Operator-ID.
4. Selected APN and UE's location (RA) is translated to a SGW-Address in the VPLMN (b)
and PGW-Address in the HPLMN (a).
5. SGSN (b) returns an “Activate PDP Context Accept” message to the UE1 (a) including
PDN type and PDN address.
6. Valid PDP contexts are established in the UE1 (a).
7. Connection to Network specified by APN (Network-ID) is established.
8. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors
after using HTTP-Service.
9. EPS Bearer Context is deactivated, UE1 (a) performs "Deactivate PDP Context
Request".

V1.0 Page 23 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

3.3.2.5 Comments
This test case confirms EPS Bearer context activation/deactivation towards a visited SGW(b)
and home PGW(a) over S8 interface with:
1. APN (R) is not empty; (Network-ID, no Operator-ID).
2. Setting of APN (Operator-ID) by subscription for HPLMN (a) = (APN(S)).
3. Setting up IP-tunnel connections (GTP or PMIP, IP, UDP/TCP).
4. Root address lookup and dynamic address allocation.
If the EPS Bearer context activation procedure fails or if the SGSN returns an “Activate PDP
Context Reject” (Cause, PDP Configuration Options) message, then the user may attempt
another activation to the same APN up to a maximum number of attempts.

4 Pre-Testing Data Exchange

4.1 General
It is necessary for the two PLMNs to have exchanged the pre-testing data defined in the
following sections prior to the commencement of testing.

4.2 Testing Contact Information

The following test Co-ordination contact information should be exchanged by both PLMNs:

1. Names
2. Telephone numbers
3. Fax numbers
4. Email address

4.3 PLMN/IP-addressing, numbering and routing data

4.3.1 LTE-only testing

For LTE-only testing is performed, the following information should be exchanged by both
PLMNs:

1. MME IP addresses used

2. SGW IP addresses used
3. PGW IP addresses used
4. PCRF IP addresses used
5. Diameter Edge Agent IP addresses and FQDNs used
6. HSS IP addresses used
7. PDN subscription context
8. APNs
9. DNS IP-Addresses

4.3.2 CS Fallback / SMS over SGs testing

If CS Fallback / SMS over SGs testing is performed, the confirmation of the PLMN
addressing numbering and routing data as referenced in PRD IR.23 [1] is regarded as
advisable. Such information includes:

1. E212-E214 translation

V1.0 Page 24 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

2. MSC/VLR and HLR E.164 addresses

3. MSRN number ranges
4. International Signalling Point Codes (if applicable)
5. SMS Service Centre E.164 address

4.3.3 LTE+2G/3G Co-existence testing

If LTE+2G/3G Co-existence testing is performed, the following information should be
exchanged by both PLMNs:

1. E212-E214 translation
2. E164 Number range
3. International Gateway Signalling Point Codes
4. SMS Service Centre E164 address
5. SGSN-/PGW-IP addresses used
6. SGSN Global Title Address used
7. PDP Context / EPS Bearer profiles
8. APNs
9. DNS IP-Addresses

4.4 USIM associated data supplied by PLMN (a)

The following information as stored in the USIM and/or HSS is required individually for each
of the USIMs.

1. PIN, PUK/(SUPER PIN).

2. IMSI
3. MSISDN
4. Basic Service Subscription Information
5. Subscriber data concerning PDN connectivity
6. Access point names
In order to perform the tests, following USIM-card profile is required:

1. APN Name: “This should contain one HPLMNs APN” or “ * ” (wild card)
2. VPLMN allowed = no

4.5 Inter-PLMN Connection Parameters

In order to establish Inter-PLMN connectivity it is necessary to exchange information as:
1. Link transport, capacity and routing parameter
2. Link carrier and topology
3. Gp/S8 interface information
4. Security related information if necessary towards interconnection
5. S9 interface information (if PMIP is used for S8)
6. LTE+2G/3G Co-existence scenarios being supported (see IR.88 [5] for the details)

4.6 IP-Server Information

The following information is required to provide IP-connectivity testing:
1. IP address of HPLMN (a) server (HTTP-, DNS-, PROXY-server), accessed via PGW (a)

V1.0 Page 25 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

5 Test Cases Excel Sheet

IR38_TEST_CASES.
xlsm

V1.0 Page 26 of 27
GSM Association Non-confidential
Official Document IR.38 - LTE and EPC Roaming Testing

Annex A Document Management

A.1 Document History

Version Date Brief Description of Change Approval Editor /
Authority Company
0.1-0.3 Initial drafts for discussion Itsuma Tanaka,
NTT DOCOMO
0.4 24 August Version for approval Networks
Itsuma Tanaka,
2013 Group
NTT DOCOMO
PSMC
03.04.2014 03.04.2014 CR for approval Networks Itsuma Tanaka
Group NTT DOCOMO

Other Information
Type Description
Document Owner IREG PACKET
Editor / Company Itsuma Tanaka, NTT DOCOMO

It is our intention to provide a quality product for your use. If you find any errors or omissions,
please contact us with your comments. You may notify us at [email protected]

Your comments or suggestions & questions are always welcome.

V1.0 Page 27 of 27