GSM Association Non Confidential

Official Document IR.25 – VoLTE Roaming Testing

VoLTE Roaming Testing

Version 4.0
15 October 2020

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 © 2020 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.

Table of Contents

V4.0 Page 1 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

Contents
1
1 Introduction 3
1.1 Scope of document 3
1.2 Objective of tests 3
1.3 Definition of Terms 5
1.4 Document Cross-References 6
2 Test Cases 7
2.1 S8HR architecture 7
2.2 BASIC SERVICE TEST CASES 9
2.2.1 IMS Registration of the UE1 (a) 9
2.2.2 UE1 (a) Calls UE2 (a), Both Roamed in VPMN (b) 10
2.2.3 UE1 (a) Calls to Local Number, UE3 (b) 10
2.2.4 Emergency call 11
2.3 SMS TEST CASES 11
2.3.1 Mobile Originated and Terminated Short Message Service (SMS-MO
and SMS-MT) 11
2.4 LAWFUL INTERCEPTION TEST CASES 12
2.4.1 Lawful Interception on originator side 12
2.4.2 Lawful Interception on terminator side 13
2.4.3 Lawful Interception of forwarded call 13
3 Equipment & Networks Requirements 14
3.1 User Equipment Requirement 14
3.2 Test Equipment Requirement 14
3.2.1 Specific Test Equipment Requirement for Emergency Call Testing 15
3.3 Prerequisite of the Network Entities 15
3.3.1 Prerequisite of the Visited Network Entities 15
3.3.2 Prerequisite of the Home Network Entities 15
3.3.3 Additional prerequisite for Emergency Call testing 16
4 Pre-Testing Data Exchange 16
4.1 Testing Contact Information 16
4.2 USIM associated data supplied by PMN(a) 16
5 Test Methodology 17
5.1 VoLTE Network Test 17
5.1.1 Evolution of VoLTE networks under Test 17
5.1.2 VoLTE roaming test between two VoLTE evolving network types 18
5.2 Device Test 18
5.2.1 Device Service Profiles 18
5.2.2 Device profile differences 19
5.2.3 Parameters impacting roaming 19
Annex A Appendix IR25.xlsm 20
Annex B Document Management 21

V4.0 Page 2 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

1 Introduction

1.1 Scope of document

This document is the specification of the IREG end-to-end functional capability tests for
VoLTE Roaming using “S8HR (S8 Home Routed)”as defined in GSMA PRD IR.88 [5], IR.65
[6] and Short Message Service (SMS) over LTE relating to the international roaming of a
User Equipment (UE), belonging to a home Public Mobile Network (HPMN) (a), to and
within a visited PMN (VPMN) (b).

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

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

GSMA IREG Permanent Reference Document (PRD) IR.23 [3] defines the scope and
purpose of each stage of testing. GSMA PRD IR.88 [5] defines the technical guidelines for
VoLTE Roaming.

This document does not cover:

 Testing of High Speed Packet Access/Long Term Evolution (HSPA/LTE) data

roaming
 Diameter Testing
 Exchange of PMN numbering, addressing and routing data [see Stage 3: GSMA
PRDPRD IR.23 [3]
 Testing of Transferred Account Procedure (TAP), billing applications and any
inter-PMN financial statement; [see IDSWG PRD TD.41 [2]. However, the
production of a Toll Ticketing file, to 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 Stage 3: GSMA PRD IR
23 [3]

1.2 Objective of tests

The fundamental objective of this testing is to confirm the capability, and sample the quality
of S8HR VoLTE Roaming services that mobile users will receive when roaming from their
HPMN (a) to VPMN (b) in LTE. 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 GSMA PRD IR.23 [3].

Because the testing is at a top-priority, its scope includes checking the correct working of
user features and any network features required by the HPMN. The scope also includes the
confirmation of acceptable quality of transmission, absence of echo and call set-up delay.

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

V4.0 Page 3 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

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.

The specific objectives are to prove that:

 "Registration" can be successfully completed for the UE (a) roaming to a VPMN (b).

 Incoming speech calls to the UE (a) can be handled by the HPMN (a) and the VPMN
(b).

 HPMN (a) successfully routing the call.

 VPMN (b) connecting the call.

 Outgoing speech calls by the UE (a) to the VPMN (b) are handled for:

 Emergency calls
 Local calls to the VPMN (b) country

 Short Message Service is available between Home Country Service Centre and
roamed mobile station.

If either the HPMN or VPMN contain Evolved Packet System (EPS) Network Entities which
are supplied by more than one manufacturer, then the test cases should be repeated for
each manufacturer.

The actual number of repetitions of the test cases is for bilateral agreement between the
HPMN and VPMN. In order to maximize the efficiency of testing, the test cases have been
specified to minimize the requirement for simultaneous joint activity by both PMN (a) and
PMN (b). This concerns mainly the administration of mobile subscriber data in the HSS.

Accordingly, the program of testing forms three distinct components:

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

ii. VPMN(b) performs tests
iii. VPMN(b) and HPMN(a) discuss results

An associated optional objective is to use the Toll Ticketing function of the VPMN to
generate a live data file, which is used by the TADIG Stage 3 testing. After transfer to the
HPMN via TADIG processes, the HPMN may use the information from the test results to
validate the details of the Toll tickets, however this is not part of the GSM Association IREG
roaming testing.

V4.0 Page 4 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

1.3 Definition of Terms

Term Description
APN Access Point Name
CDR Charging Detailed Record
CCITT International Telegraph and Telephone Consultative Committee
CLI Calling Line Identity
CS Circuit Switched
CSFB Circuit-Switched Fallback
DNS Domain Name System
EENL Extended Emergency Numbers List
ENL Emergency Numbers List
EPC Evolved Packet Core
EPS Evolved Packed System
FQDN Fully Qualified Domain Name
FTP File Transfer Protocol
GPRS Generic Packet Radio Access
GTP GPRS Tunnelling Protocol
HSS Home Subscriber Server
HPMN Home Public Mobile Network
HSPA High Speed Packet Access
HSS Home Subscriber Server
IMS IP Multimedia Subsystem
IMSI International Mobile Subscriber Identity
IP Internet Protocol
LEA Law Enforcement Agency
LEMF Law Enforcement Monitoring Facility
LI Lawful Interception
LTE Long Term Evolution
MAP Mobile Application Part
MME Mobility Management Entity
MSISDN Mobile Subscriber ISDN Number
P-CSCF Proxy – Call Session Control Function
PCRF Policy and Charging Rules Function
PDN Packet Data Network
PDP Packet Data Protocol
PGW PDN Gateway
PIN Personal Identification Number
PMN Public Mobile Network
PSTN Public Switched Telephone Network

V4.0 Page 5 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

PUK PIN Unblocking Key

SGW Serving Gateway
SIP Session Initiation Protocol
SMS Short Message Service
SMSC Short Message Service Centre
S-CSCF Serving – Call Session Control Function
SIP Session Initiation Protocol
SMS Short Message Service
SMSC Short Message Service Centre
TAP Transferred Account Procedure
TCP Transmission Control Protocol
UDP User Datagram Protocol
UE User Equipment
URI Uniform Resource Identifier
USIM Universal Subscriber Identity Module
VLR Visitor Location Register
VMSC Visited Mobile Switching Centre
VPMN Visited Public Mobile Network

1.4 Document Cross-References

Document
Ref Number Title
1 3GPP TR 21.905 Vocabulary for 3GPP Specifications
2 GSMA PRD TD.41 Testing the Transferred Account Procedure (TAP)
3 GSMA PRD IR.23 Organisation of GSM International Roaming Tests
4 GSMA PRD IR.92 IMS Profile for Voice and SMS
5 GSMA PRD IR.88 LTE and EPC Roaming Guidelines
6 GSMA PRD IR.65 IMS Roaming and Interworking Guidelines
7 GSMA PRD IR.67 DNS/ENUM Guidelines for Service Providers
8 3GPP TS 23.228 IP Multimedia Subsystem (IMS); Stage 2
9 GSMA PRD TD.50 TAP Test Cases(TTC) for VoLTE Roaming Testing
10 GSMA PRD BA.27 Charging Principles
11 3GPP TS 23.167 IP Multimedia Subsystem (IMS) emergency sessions
12 GSMA PRD NG.119 Emergency communication for roamers
13 3GPP TS 23.401 GPRS enhancements for E-UTRAN access
14 GSMA PRD IR.38 LTE and EPC Roaming Testing
End to End Functional Capability Specification for Inter-PLMN
15 GSMA PRD IR.24
Roaming (Stage 4 Testing)

V4.0 Page 6 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

2 Test Cases
The structure for testing international voice roaming and SMS interworking in LTE are
recommended to be divided in four groups:

1. Basic Service (Registration and Voice Call)

2. Emergency Service (Emergency registration and Emergency Call)
3. Short Message Service (Point to point)
4. Lawful Interception

Supplementary Services provided for customers in HPMN (a) are independent from the
VPMN (b).

The GSMA PRD IR.25 tests can have two granularities for data volume measurement,
based on APN or based on QCI. If a need of observation of the data volume is identified,
e.g. for the rating purpose, the APN based measurement is a default setting where all data
associated with QCI 1, 5, 8 are aggregated regardless of QCI values. Optionally, the QCI
based data volume measurement can be configured on the individual QCI bearers for the
data volume measurement.

Note: this IR.25 test book could be used to test all services or part of them (e.g.: emergency
services only).

2.1 S8HR architecture

A high level architecture diagram of S8HR VoLTE Roaming Architecture is represented in
Figure 2.1. PDN-GW (P-GW) and Proxy - Call Session Control Function (P-CSCF) are
located in HPMN (a).

VPLMN of A-Party IPX HPLMN of A-Party

TAS

S6a
MME HSS S-CSCF

PCRF P-CSCF
S8
E-UTRAN SGW PGW IBCF/TrGW/BGCF/MGCF

Control Plane (SIP) TDM or IPX

User Plane (RTP media) B-PARTY

Figure 1: S8HR VoLTE Roaming Architecture

V4.0 Page 7 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

It is anticipated that it may be necessary to monitor both signalling messages and voice
calls on any of the Network Entity interfaces shown in the diagrams. However, this is not a
firm requirement for this test specification.

The results of the test cases shall be recorded in Annex A: Appendix IR25.xlsm.

The following roaming functions are included in the test cases defined within this PRD:

Functions H/V Section Mand / Comments

Opt
VoLTE registration H/V 2.2.1 M Check QCI 5 bearer
VoLTE MOC / MTC H/V 2.2.2 M Check QCI 1 bearer +
location
VoLTE call with local number H/V 2.2.3 M
SMSoIP MO / MT H/V 2.3.1 O Check location
Emergency call (UE detectable) V 2.2.4 O
Emergency call (non UE H/V 2.2.4 O Release by H IMS
detectable)
Lawful Interception on original V 2.4.1 O Null encryption for SIP
side signalling in roaming (to
be specified in bilateral
agreement)
Lawful Interception on terminator V 2.4.2 O Null encryption for SIP
side signalling in roaming (to
be specified in bilateral
agreement)
Lawful Interception of forwarding V 2.4.3 O Null encryption for SIP
call signalling in roaming (to
be specified in bilateral
agreement)

Table 1: List of Roaming Functions included in the Test Cases

GSMA PRD BA.27 [10] defines the charging principles for VoLTE Roaming and SMSoIP.
VoLTE Roaming Charging Principles

 Where charging by IMS APN, voice and SIP signalling will not be differentiated and
both charged by data volume.
 Where charging by QCI, voice is charged by differentiated QCI (QCI=1) and SIP
signalling by QCI5, both can be charged by data volume. This allows differentiated
charging between voice and signalling. [See section 11.6 of BA.27 [10])

SMSoIP Charging Principles

 Where charging by IMS APN, SMS and SIP signalling will not be differentiated and
both charged by data volume.

V4.0 Page 8 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

 Where charging by QCI, SMS and SIP signalling by QCI5, both can be charged by
data volume.

2.2 BASIC SERVICE TEST CASES

It should be noted that no supplementary services are active during the test cases which are
described in Section 2.2.

2.2.1 IMS Registration of the UE1 (a)

2.2.1.1 Preconditions
 UE1 (a) contains Universal Subscriber Identity Module (USIM) of HPMN (a).
 HSS record contains basic and supplementary service information.
 No valid EMM contexts are established for UE1 (a).
 No valid PDN connection is established in the UE1 (a).
 One EPS bearer context subscription record exists in HSS (a) where UE1(a) has a
subscription for IMS APN.

When enabling IMS voice roaming for a subscriber, the following subscription settings must
be taken into account for the IMS well-known APN:

 Barring on "All Packet Oriented Services" is not active

 The P-CSCF internal database does not have the home network contact information.
 The "VPMN Address Allowed" parameter in the HSS (a) must not be present or must
be set to “NOTALLOWED (0)”.
 An HPMN must set IMS encryption / unencryption (via IPsec) per VPMN basis for its
outbound roamers, to meet the VPMN’s (local) regulatory requirements. For the LI
purpose in the visiting country, the HPMN P-CSCF (a) must set null encryption for
IMS signalling for the outbound roaming UEs (a) in VPMN (b) [6].

2.2.1.2 Action
 Power-up UE1 (a).
 Perform initial registration through a P-CSCF in HPMN (a).
 Check EMM contexts in UE1 (a) and MME (b) for the IMSI/GUTI /MSISDN of UE1
(a).

2.2.1.3 Expected Result

 PDN Connection (i.e. Default Bearer) for IMS APN is successfully established.
 IMS registration is successfully completed.
 Check SIP Bearer is correctly created using QCI=5.
 Successful result if 200 OK arrives at the P-CSCF.

2.2.1.4 Comments
This test case confirms the operation of registration through the P-CSCF. It checks the
support of the relevant Session Initiation Protocol (SIP) operations.

V4.0 Page 9 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

2.2.2 UE1 (a) Calls UE2 (a), Both Roamed in VPMN (b)

2.2.2.1 Precondition
UE1 (a) and UE2 (a) have attached successfully and established a PDN connection for IMS
APN in VPMN (b).

 UE1 (a) and UE2 (a) have succeeded in IMS Registration to HPMN(a).

2.2.2.2 Actions
 UE1 (a) establishes call to UE2 (a).
 Call answered and held for one minute.
 Quality assessed

2.2.2.3 Expected Result

 Successful result if the call is established in 30 seconds, and the call is stable in the
unanswered and answered phases, and there is no perceptible echo to both users,
and call remains in intelligible/high quality conversation phase for one minute.
 Check that the Voice Media Bearer is correctly created using QCI=1 for mobile
originating and terminating calls respectively.

2.2.2.4 Comments
This test case confirms Mobile Originated and Mobile Terminated call procedures for
roamers.

2.2.3 UE1 (a) Calls to Local Number, UE3 (b)

2.2.3.1 Precondition
 UE1 (a) is attached to VPMN (b) and has a IMS-APN PDN connectivity.
 UE3 (b) is attached to VPMN (b).

2.2.3.2 Action
 UE1 (a) calls UE3 (b) using non-international number format
 Call answered and held for one minute
 Quality assessed

2.2.3.3 Expected Result

Successful result if the call is established in 30 seconds, and the call is stable during the
unanswered and answered phases, and there is no perceptible echo to both users, and call
remains in intelligible/high quality conversation phase for one minute. See CCITT Rec P.84
Annex D for instructions on use of Quality Scales. This test will also confirm the correct
delivery of Calling Line Identity (CLI) information (or lack thereof) or equivalent parameter in
SIP message in a roaming scenario.

2.2.3.4 Comments
This test case confirms that the “Local Number Translation” procedure of IMS entities in
HPMN that must support the handling of numbers in non-international format to route the
call, as specified in 3GPP TS23.228 [8] and in GSMA PRD IR.65 [6].

V4.0 Page 10 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

2.2.4 Emergency call

2.2.4.1 Preconditions
 UE1 (a) contains USIM of HPMN (a).
 A barring of all outgoing calls is activated on the UE1 (a) for testing UE detectable
Emergency Calls. Deactivate barring of all outgoing calls on UE1 (a) when testing
non UE detectable Emergency Calls.

2.2.4.2 Actions
Power-up UE1 (a) and perform an emergency call to:

 112 or 911
 A national emergency number of the visited country

Optionally perform a call to a short code service of HPMN

2.2.4.3 Expected Result

Successful result if calls are established with PSAP of the visited country or equivalent
simulated PSAP.

2.2.4.4 Comments
These tests check the possibility to make the Emergency Calls both in the cases of UE
Detectable Emergency Calls and in the case of non UE detectable Emergency Calls. The
handling of non UE detectable Emergency Calls is defined in GSMA PRD NG.119 [12].

The domain selection of an emergency session is referred to 3GPP TS 23.167, annex H

[11].

The following Emergency Call options are possible, depending on the capabilities of UE,
HPMN and VPMN (see also GSMA PRD NG.119 [12]):

 CSFB Emergency Call

 IMS Emergency Call with Emergency Registration in VPMN (requiring E-CSCF in
VPMN and an IMS interconnect between HPMN and VPMN)
 IMS Emergency Call without Emergency Registration, i.e. anonymous IMS
emergency call (requiring E-CSCF in VPMN)

Appropriate option needs to be specified in bilateral agreement between HPMN (a) and
VPMN (b).

2.3 SMS TEST CASES

2.3.1 Mobile Originated and Terminated Short Message Service (SMS-MO

and SMS-MT)

2.3.1.1 Precondition
SMS- Mobile Originated / Terminated (MO/MT) Services is provisioned in HSS subscription.
UE1 (a) and UE2 (a) are registered in VPMN (b).

V4.0 Page 11 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

 UE1 (a) and UE2 (a) are both SMS over IMS capable.
 UE1 (a) and UE2 (a) are camping on LTE.
 UE1 (a) and UE2 (a) successfully completed IMS Registration.

2.3.1.2 Actions
 Switch on UE1 (a). Switch off UE2 (a).
 Use UE1 (a) to transmit a 160 character Short Message to UE2 (a) via the Home
Country SMS - Service Centre with Message Waiting priority selected.
 Switch on UE2 (a).
 Await delivery of Short Message to UE2 (a) and check contents of Short Message
with those transmitted.

2.3.1.3 Expected Result

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

2.3.1.4 Comments
This test case confirms correct operation of SMS - Mobile Originated / Terminated Services
including "Message Waiting" and "Note UE Present" procedures.

2.4 LAWFUL INTERCEPTION TEST CASES

Disabling encryption for IMS signaling is a precondition for all LI test cases in VPMN.

2.4.1 Lawful Interception on originator side

2.4.1.1 Preconditions
 UE1 (a) and UE2 (a) are attached to VPMN (b) and have IMS-APN PDN
connectivity,
 UE1 (a) is targeted for Lawful Interception,
 To enable lawful interception within VPMN (b), the P-CSCF (a) in HPMN (a) must set
null encryption for IMS signalling at the outbound UE1 (a) and UE2 (a) in VPMN (b).

2.4.1.2 Actions
 UE1 (a) establishes call to UE2 (a).
 Call answered and held for five minutes.

2.4.1.3 Expected Result

 Call and Context Information is available in LEMF

2.4.1.4 Comments
In most cases the LEMF is situated within the LEA. In those cases, test has to be supported
and result verified by LEA experts.

V4.0 Page 12 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

2.4.2 Lawful Interception on terminator side

2.4.2.1 Preconditions
 UE1 (a) and UE2 (a) are attached to the VPMN (b) and have IMS-APN PDN
connectivity.
 UE2 (a) is targeted for Lawful Interception
 To enable lawful interception within VPMN (b), the P-CSCF (a) in HPMN (a) must set
null encryption for IMS signalling at the outbound UE1 (a) and UE2 (a) in VPMN (b).

2.4.2.2 Actions
 UE1 (a) establishes call to UE2 (a).
 Call answered and held for five minutes.

2.4.2.3 Expected Result

 Call and Context Information is available in LEMF

2.4.2.4 Comments
In most cases the LEMF is situated within the LEA. In those cases, test has to be supported
and result verified by LEA experts.

2.4.3 Lawful Interception of forwarded call

2.4.3.1 Preconditions
 UE1 (a), UE2 (a) and UE3 (a) are attached to VPMN (b) and have IMS-APN PDN
connectivity.
 UE2 (a) has call forwarding active to UE3 (a)
 UE2 (a) is targeted for Lawful Interception
 To enable lawful interception within VPMN (b), the P-CSCF (a) in HPMN (a) must set
null encryption for IMS signalling at the outbound UE1 (a), UE2 (a) and UE3 (a) in
VPMN (b).

2.4.3.2 Actions
 UE1 (a) establishes call to UE2 (a).
 Call answered and held for five minutes.

2.4.3.3 Expected Result

 Call and Context Information is available in LEMF

2.4.3.4 Comments
In most cases the LEMF is situated within the LEA. In those cases, test has to be supported
and result verified by LEA experts.

V4.0 Page 13 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

3 Equipment & Networks Requirements

3.1 User Equipment Requirement

 UEs are supplied based on the bilateral agreement between HPMN (a) and VPMN
(b).
 Two LTE compatible USIMs supplied by HPMN (a). The supply of additional USIMs
may be agreed by the HPMN(a) and VPMN(b), typically for the purposes of:

 Spare cards in case of failure.

 Allocation from different HSSs if applicable.

 One USIMs supplied by VPMN (b).

The device service profile of the UEs supplied for testing, as well as each value deviation of
the relevant IMS configuration parameters [4] from that service profile must be specified.

It is expected that manual selection will be used to select the VPMN (b) when using the
USIMs supplied by the HPMN (a). To facilitate the subsequent automatic selection, it is
required that bits b6 and b5 of byte 2 of the USIM Service Table (Data-field 38) be set to
"1", and the chosen the VPMN that is in the PMN Selector (Data-field 30).

In order to replicate the service that general roamers will encounter, it is required that any
USIM used in the tests must have one access class out of the classes 0-9 defined. No other
access class (for example 10 or 11-15) must be defined.

It is recommended that on any new USIM the Location Update Status field is set to "Status
not updated" before the tests start (bit b2 set to "0" and bit b1 set to "1", of byte 11 of Data-
field 7E).

3.2 Test Equipment Requirement

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. If possible, the
clock must be adjusted to be in alignment with the clock of MME in VPMN (b) which is used
for the Toll Ticketing function. Stopwatch capable of measuring perceived chargeable
duration of calls to an accuracy of one second. Packet counter can be prepared as
appropriate application installed in UE or Network entities.

The availability of a S6a, S8, and DNS interface monitoring equipment is highly advisable.
HPMN may have monitoring equipment in its IMS entities such as P-CSCF, S-CSCF and
TAS. It is not mandatory but may be useful for VPMN to have packet analyser that can
extract SIP signalling being exchanged over GTP tunnels. SIP traces are supposed to be
located between P-CSCF and UE. GTP traces are supposed to be located between P-GW
and S-GW.

If a system simulator is used as a test device for testing, it must:

 Select a correct test suite based on the HPMN and VPMN evolving type in
accordance with the section 5.1,

V4.0 Page 14 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

 Simulate one of the device service profiles assigned by the HPMN and identify the
deviation of the IMS configuration parameters in accordance with the section 5.2.

3.2.1 Specific Test Equipment Requirement for Emergency Call Testing

The availability of an IP and SIP protocol analyser able to show SIP messages is highly
advisable.

3.3 Prerequisite of the Network Entities

3.3.1 Prerequisite of the Visited Network Entities

For the VPMN and HPMN to enable S8HR VoLTE roaming, the following conditions must
be fulfilled in the EPC and E-UTRAN as specified in GSMA PRD IR.88 [5]. Conditions in
IMS are not listed. The VPMN must support the following VoLTE capabilities:
 SIP Bearer with QCI=5;
 Voice media bearer with QCI=1;
 if videocall is supported, then Video media bearer with QCI=2 in case HPMN (a)
decides to use GBR bearer, or any non-GBR QCI value.
(HPMN and VPMN should agree on another QCI value for videocall if VPMN does
not support QCI value of two (2).)
 Indication from EUTRAN to the UE on “ims-EmergencySupport” in SIB1 cell
broadcast
 Indication from MME to the UE “IMS VoPS Supported Indicator = supported”
 Indication from MME to the HSS "Homogeneous Support of IMS Voice over PS"
based on the conditions specified in 3GPP TS 23.401[13]
 Identifying which evolving type the VPMN belongs to.

3.3.2 Prerequisite of the Home Network Entities

For the VPMN and HPMN to enable S8HR VoLTE roaming, HPMN must support the
following VoLTE capabilities:
 SIP Bearer with QCI=5;
 Voice media bearer with QCI=1; and
 Video media bearer with QCI=2 (or non-GBR QCI).
 Identifying which evolving type the HPMN belongs to
 Identifying which device service profile the HPMN provisions to the UEs and
identifying the deviation of the IMS configuration parameters from that profile.

As ARP settings are exclusively related to the VPMN service prioritization strategy and may
change from one VPMN to another, HPMN should agree with VPMN on a right Priority Level
(PL) value to set on IMS default bearer and dedicated bearer in order to ensure that its
sessions will be handled with the right priority. QoS (QCI, ARP, AMBR) values should be
agreed between HPMN and VPMN.

V4.0 Page 15 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

3.3.3 Additional prerequisite for Emergency Call testing

For the VPMN and HPMN to enable Emergency Calls for non UE detectable emergency
numbers based on Emergency Number Lists, the VPMN must support the following
capabilities:
 ENL in MME
 Optional EENL in MME

For the VPMN and HPMN to enable Emergency Calls for non UE detectable emergency
numbers based on SIP 380 Alternative Response, the HPMN must support the following
capabilities:
 VPMN specific emergency number lists in P-CSCF

4 Pre-Testing Data Exchange

It is necessary for the two PMNs to have exchanged the pre-testing data defined in this
Section prior to the commencement of testing.

4.1 Testing Contact Information

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

 names,
 telephone numbers,
 fax numbers, and
 email address.

4.2 USIM associated data supplied by PMN(a)

The following information as stored in the SIM and/or HSS is required individually for each
of the two SIMs.

 PIN, PUK/ (SUPER PIN).

 IMSI
 MSISDN
 Basic Service Subscription Information
 Public User Identities

V4.0 Page 16 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

5 Test Methodology
VoLTE testing is based on the device-network relationship (defined in GSMA PRD IR.92
[4]). Some devices are certifying the network usage. Roaming eco-system also involves
device-network (visited and home). For testing purposes, simulators can be implemented at
device and network side. Figure 2 shows a VoLTE test ecosystem.

Figure 2: VoLTE Test Ecosystem

To streamline VoLTE test and to reduce device test overhead, it is recommended to break
down the VoLTE roaming and non-roaming test in two stages – network test prior device
test. The two testing parts complement each other and cannot replace each other.

5.1 VoLTE Network Test

Network test is initially to prove the network by using a commercially available test tool as a
reference test system with suitable test suites / test cases following present IR.25. The test
system is shown as testing simulator and/or service simulator in the Figure 2 above.

5.1.1 Evolution of VoLTE networks under Test

From the service testing view, a VoLTE network can be in one of the VoLTE service
evolving stages or types. Starting from LTE (type 0), four VoLTE network types (1 - 4) are
identified.

 Type 0 – deployed LTE, but has not launched VoLTE service,

 Type 1 - launched home VoLTE service,
 Type 2 - launched home VoLTE & SMSoIP services,
 Type 3 - launched home VoLTE & IMS emergency services,
 Type 4 - launched home VoLTE, SMSoIP & IMS emergency services.

Figure 3: VoLTE evolving types & test suites applied

V4.0 Page 17 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

The Fig. 3 shows an evolving model of the VoLTE networks from type 0 towards one of the
four types (1 – 4) and test suites to be applied, where the test suites are defined as:

 Test suite1 – VoLTE, SMSoNAS, CSFB Emergency

 Test suite2 – VoLTE, SMSoIP, CSFB Emergency
 Test suite3 – VoLTE, SMSoNAS, IMS Emergency
 Test suite4 – VoLTE, SMSoIP, IMS Emergency

Note: Referenced to GSMA PRD IR.38 [14], 3.2.3, an SMSoSGs test case is required by
Test Suite1 & Test Suite3. Referenced to GSMA PRD IR.24 [15], 2.2.1 (i), a CSFB
emergency test case is required by Test Suite1 & Test Suite2.
The test suites ensure that the voice, SMS and emergency services can be tested:

 in a network being one of the four evolving types in the non-roaming test,
 between a HPMN and a VPMN when the two networks are in the same or different
evolving types in the roaming test.

For example, the Test suite2 is applied to the non-roaming test in a HPMN if the HPMN has
deployed VoLTE and SMSoIP services, but the Emergency service is still CSFB-based.

5.1.2 VoLTE roaming test between two VoLTE evolving network types
If a VoLTE roaming is established between two types of VoLTE network, the table 2 shows
which test suite abovementioned is chosen for VoLTE roaming test.

Table 2: Selection of a test suite for VoLTE roaming between two types
For example, the Test suite2 is applied to the roaming test if a device from a Type2 HPMN
(A) is outbound roaming in a Type1 VPMN (B). The S8 home-routed VoLTE and SMSoIP
services as well as the CSFB Emergency service in the VPMN (B) are tested.

Another example is when a device from a Type2 HPMN (A) is outbound roaming in a Type3
VPMN (B). Either Test suite4 or Test suite2 is applied depending upon the VPMN (B)’s local
emergency policy for the VoLTE roamers. If EMS (IMS Emergency Service Support)
indicator is set, the Test suite4 is selected, otherwise the Test suite2 is applied. 3GPP TS
23.167 [11] Annex H specifies that a VoLTE capable UE supports the IMS emergency and
CSFB emergency calls and can select the emergency domain accordingly in the ATTACH
or RAU procedure.

5.2 Device Test

5.2.1 Device Service Profiles

Six standard device service profiles are defined to provide the device functionally
interoperability test in non-roaming at home and in roaming (referred in short as device
test). The profiles cover:

V4.0 Page 18 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

 2 x Voice over LTE profiles,

 2 x Voice & SMSoIP over LTE profiles,
 2 x Voice & SMSoIP over WiFi profiles.

5.2.2 Device profile differences

The differentiation between the voice profiles is characterised by the following IMS
configuration parameters in GSMA PRD IR.92 [4]:

 URI derivation,
 Reliable 18x,
 Home/Geo-Local,
 Voice / Voice & Video,
 Codec options.

The differentiation between Voice and Voice & SMS profiles is characterised by the IMS
configuration parameter:

 Enabling SMS.

The differentiation between LTE and WiFi Profiles, as well as between the WiFi profiles is
characterised by the following IMS configuration parameters:

 PS Voice Preference,
 HO settings (WLAN to LTE).

5.2.3 Parameters impacting roaming

Independent from the device profiles, the setting following IMS configuration parameters
has impact on roaming test:

 Policy on local numbers,

 Media type restriction policy when roaming,
 PS Voice Preference Indicator when roaming,
 XCAP PS Data Off Exempt,
 MMTEL Voice PS Data Off Exempt,
 Device Management PS Data Off Exempt,
 SMS over IP PS Data Off Exempt,
 USSI_PS Data Off Exempt,
 PRE AND POST CALL DATA OFF,
 MMTEL Video PS Data Off Exempt,
 Allow Handover of IMS PDN connection from WLAN to LTE,
 RCS VoLTE Single Registration

V4.0 Page 19 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

Annex A Appendix IR25.xlsm

Only one test book will describe the common tests for S8HR.

IR25v4_0.xlsm

V4.0 Page 20 of 21
GSM Association Non Confidential
Official Document IR.25 – VoLTE Roaming Testing

Annex B Document Management

Document History
Version Date Brief Description of Change Approval Editor /
Authority Company
1.0 19 Feb New PRD (IREG IREG #64 Alfonso Della
2013 CR1001).Approved at Fera, Telecom
PSMC
PSMC#118 Italia
2.0 3 May CR 1002 added with S8HR NG #3 Veronique
2016 description Verhé, SIGOS
GmbH
2.1 15 May IR.25 CR1003 IREG to TADIG NG#7 Veronique
2018 validation with one to one Verhé, SIGOS
mapping of test cases GmbH
2.2 11 Oct IR.25 CR1004 Clean-up NG#10 Veronique
2019 embedded Excel Sheets Verhé, SIGOS
GmbH
3.0 6 April IR.25 CR1005 Clean-up NG Veronique
2020 embedded Excel sheets and Verhé, SIGOS
convergence S8HR-LBO GmbH
4.0 15 Oct IR.25 CR1006 IR.25 CR LBO NG#12 Veronique
2020 Removal Verhé, SIGOS
GmbH

Other Information
Type Description
Document Owner NG
Editor / Company Veronique Verhé, SIGOS GmbH

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.

V4.0 Page 21 of 21