+ All Categories
Home > Documents > Annex_10_IR35_direct LTE Roaming Test Woth Charging

Annex_10_IR35_direct LTE Roaming Test Woth Charging

Date post: 01-Nov-2014
Category:
Upload: azmir-mahamood
View: 159 times
Download: 4 times
Share this document with a friend
Description:
Annex_10_IR35_direct LTE Roaming Test Woth Charging
41
Title Version 5,0 Date 26-May-11 Antitrust Notice The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy. Version Brief Description Date 0.0.1 End–to–End Functional Capability Test Specification for Inter-PLMN GPRS- and LTE-Roaming Official Document IR.35 1.0.0 0.0.7 0.0.8 0.0.3 0.0.5 0.0.6 0.0.9 3.0.1 3.0.2 3.0.3 3.0.4 2.1.0 2.0.0 3.0.5 Changes/Clarification towards the meaning of the APN- Network-Identifier: APN-Network-ID defines to which external network the GGSN is connected to 3.0.0 Approved by IREG 38 subject to addition of Appendix A and B Appendix A and B completed Approved at Plenary 43. PL Doc 36/00 Rev 1 Modifications from comments according 1th IREG Packet-WP-GPRS (GSM NA IREG WG Suggested 12/14/1999 2/1/2000 3/3/2000 IREG Doc GPRS 23/99 with changes according 4 th Meeting of IREG GPRS for Ad-Hoc pre-discussion 6/22/1999 8/6/1999 11/29/1999 First draft of document for IREG GPRS group discussion (5th Meeting) Modifications from comments send by email Introduction of “Operator Control of Service” test cases IREG Doc IR35 with changes according 7th Meeting of IREG GPRS Charging-Information/Operator Control of Service Test Charging impacts, chapter 2.2 item no. 6 updated. Final modifications before IREG#38 Modified for IREG 38 approval A new test case added in Chapter 2.2.3 Second draft of document for IREG GPRS group discussion (6th Meeting) IREG Doc GPRS 23/99 with changes according 6th Meeting of IREG GPRS Charging information added, ODB test cases modified. 0.0.2 0.0.4 Document History 2/24/2000 8/30/2000 3/15/2000 3/29/2000 4/28/2000 6/23/2000 3/3/2000 3/14/2000 3/1/2000 IREG Doc GPRS 35/00 with changes according 9th Meeting of IREG GPRS IREG Doc GPRS 57/00 (CR) with changes according to 11th Meeting of IREG GPRS Approved and revised document after IREG#39 for discussion on 1th Packet-WP-Meeting 9/5/2000 11/23/2000 1/5/2001 IR35 General 1(42) IR3550
Transcript
Page 1: Annex_10_IR35_direct LTE Roaming Test Woth Charging

Title

Version 5,0Date 26-May-11

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

Version Brief Description

Date

0.0.1

End–to–End Functional Capability Test Specification for Inter-PLMN GPRS- and

LTE-Roaming Official Document IR.35

1.0.0

0.0.7

0.0.8

0.0.3

0.0.5

0.0.6

0.0.9

3.0.1

3.0.2

3.0.3

3.0.4

2.1.0

2.0.0

3.0.5

Changes/Clarification towards the meaning of the APN-Network-Identifier: APN-Network-ID defines to which external network the GGSN is connected to

3.0.0

Approved by IREG 38 subject to addition of Appendix A and B

Appendix A and B completed

Approved at Plenary 43. PL Doc 36/00 Rev 1

Modifications from comments according 1th IREG Packet-WP-GPRS (GSM NA IREG WG Suggested

12/14/1999

2/1/2000

3/3/2000

IREG Doc GPRS 23/99 with changes according 4th

Meeting of IREG GPRS for Ad-Hoc pre-discussion

6/22/1999

8/6/1999

11/29/1999

First draft of document for IREG GPRS group discussion (5th Meeting)

Modifications from comments send by emailIntroduction of “Operator Control of Service” test cases

IREG Doc IR35 with changes according 7th Meeting of IREG GPRSCharging-Information/Operator Control of Service Test

Charging impacts, chapter 2.2 item no. 6 updated.Final modifications before IREG#38

Modified for IREG 38 approval

A new test case added in Chapter 2.2.3

Second draft of document for IREG GPRS group discussion (6th Meeting)

IREG Doc GPRS 23/99 with changes according 6th Meeting of IREG GPRS

Charging information added, ODB test cases modified.

0.0.2

0.0.4

Document History

2/24/2000

8/30/2000

3/15/2000

3/29/2000

4/28/2000

6/23/2000

3/3/2000

3/14/2000

3/1/2000

IREG Doc GPRS 35/00 with changes according 9th Meeting of IREG GPRS

IREG Doc GPRS 57/00 (CR) with changes according to 11th Meeting of IREG GPRS

Approved and revised document after IREG#39 for discussion on 1th Packet-WP-Meeting

9/5/2000

11/23/2000

1/5/2001

IR35 General 1(42) IR3550

Page 2: Annex_10_IR35_direct LTE Roaming Test Woth Charging

5/26/20115.0 Add the provision of roaming scenarios where LTE and 2G/3G co-exist.

3.0.7

3.0.6

Packet-WP-GPRS (GSM NA IREG WG Suggested changes to IR35)

3/1/2001

8/21/2001

Separation of optional test cases in a separate Annex

Modifications from comments according 3rd IREG-Packet-Meeting (Creation of S-CDRs)

3.1.2 3/18/2001

3.1.0

3.1.1 Approved and revised document after IREG#41

Modified document for presentation on the IREG-#41-Meeting

Modifications from comments /experiences made by Vodafone-D2:Restructuring of test results; table-format; Removal of test-cases; chapter B1.2.7 and B1.2.8; (See also CR-003) Changes according 8th Meeting of IREG Packet

10/17/2001

3.3.0 CR-004_Hutchison-3G, IREG-Doc 068_02Approved and revised document after IREG#43

8/20/2002

3.2.0 Approved and revised document after IREG#42 3/20/2002

3.3.1 CR NTT-DoCoMo, IREG-Doc 092/02, Additional requirement of operator control of service.CR NTT-DoCoMo, IREG-Doc 093/02, The prohibition

2/11/2003

3.4.0 Reorganization of document according IREG-IR35-Ad-Hoc-Meeting, 14.04.04-Düsseldorf01.10.04: Final Release after EMC-Approval

10/1/2004

4.0 Changed IR35 from Word to EXCEL within GSMA Open Connectivity project

9/2/2008

4.1 LTE Roaming added to IR35 1/27/2010

IR35 General 2(42) IR3550

Page 3: Annex_10_IR35_direct LTE Roaming Test Woth Charging

11.1 Scope of Document

1.2 Abbreviations

Term2.5G2.5G – SGSNAPNBSSAP+BSSDNSEPC Evolved Packet CoreEPS Evolved Packet SystemFTPG-CDRGGSNGMSCHLRHSS Home Subscriber ServerHPLMNHTTPIPISPLTE Long Term EvolutionM-CDRMMMMEMMSCMSMSCPCRFPDPPLMNP-GW PDN GateWayRAISAE System Architecture EvolutionSCTP Stream Control Transmission ProtocolS-CDRSGSNS-GW Serving GateWaySMSSMS-SCUDPVMSCVLRWAP

1.3 Objective of Tests

1.4 Strategy for Testing

1.5 Prerequisites

Prerequisites for GPRS only testing:

HLR GPRS Subscription Data:Field

The fundamental objective of this testing is to confirm the capability of packet switched data services which users will receive when roaming from their Home PLMN(a) to PLMN(b). Consequently the tests are restricted to top-level capability testing. There is no provocative or inopportune behaviour testing.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.The overall objective of the tests is to confirm that functionality and features of data services, which are already known to operate correctly within each separate PLMN, will also operate correctly for Inter-PLMN roaming.The tests described here do not replace the international roaming tests described in IR24. They represent a completion of IR24 tests regarding packet switched data features.The test cases in Chapter 2 and Chapter 19 are first of all mandatory . However they can/should only be done if the technical prerequisites are given for both involved networks under test.

Visited Mobile Services Switching CentreUser Datagram Protocol

Visitor Location RegisterGWWAP Gateway

Description

Towards a first introduction of GPRS following prerequisites are assumed:1. GPRS mobile stations supporting the network operation modes in VPLMN(b).(Note: Class-C-Mobiles can be used for testing however IMSI-/GSM-procedures are not in scope but covered in IREG-IR24)2. The HLR contains GPRS subscription data and routing information (PDP type (S), PDP address (S), APN (S), and VPLMN address allowed). These subscription data are permanent data in the HLR and have to be inserted for the tests. The HLR is accessible from the SGSN via the Gr interface. For roaming MSs, the HLR is in a different PLMN than the current SGSN. The SGSN is updated with new GPRS subscription data with the “Insert Subscriber Data” procedure. IMSI is the primary key to the GPRS subscription data stored in the HLR. There may be several sets of GPRS subscription data per IMSI.

Short Message Service Centre

Mobile Services Switching Centre

Packet Data Protocol, e.g., IP or X.25Public Land Mobile Network PLMN(a)

Routing Area Identity

Policy and Charging Rules Function

Home Location Register

Serving GPRS Support Node – Call Detail RecordServing GPRS Support Node

Short Message Service

Mobility Management Entity

Home PLMNHypertext Transport ProtocolInternet ProtocolInternet Service Provider

Mobility Management

Multimedia Messaging Service Centre

In order to maximize the efficiency of testing, the test cases have been drawn up 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 HLR/HSS.Accordingly, the program of testing forms three distinct components.(i) HPLMN(a) issues pre-programmed SIMs (see chapter 4.3) and programmes HLR/HSS(ii) PLMN(b) performs tests(iii) PLMN(b) and HPLMN(a) discuss results

DefinitionGPRS Release ‘97/98’Release ‘97/98 SGSNAccess Point Name

Mobility Management - Call Detail Record

File Transfer Protocol

Mobile Station MSx(b) indicates that the MS subscription is managed by PLMN(b)

Gateway GPRS Support Node – Call Detail RecordGateway GPRS Support NodeGateway Mobile Services Switching Centre

This document is the specification of IREG End-to-end Functional Capability tests relating to the international roaming of a Mobile Station subscribed to packet switched data services, belonging to a home PLMN (a), to and within a visited PLMN (b).Throughout this document, GPRS refers to GPRS Release ‘97/98 (i.e. 2.5G).Throughout this document, LTE/EPC, and LTE+2G/3G Co-existence refers to Release8.The tests specified here do not replace the End-to-end Functional Capability tests for Inter-PLMN Roaming [see Stage 4: IREG PRD IR24], because not every roamer will be subscribed to a packet switched data service. This document represents rather an extension to the IR24 tests. The tests should be done after successful Stage 4 testing.Whilst it is expected that packet switched data-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 MS1(a) to VPLMN(b) only. There is no reference to a Mobile Station MS1(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.IREG Document PRD IR23 defines the scope and purpose of each stage of testing.This document does not cover:• SCCP testing. [See Stage 2: IREG PRD IR25]• SCTP/UDP/IP testing.• Exchange of PLMN numbering, addressing and routeing data. [See Stage 3: IREG PRD IR23]• Testing of Transferred Account Procedure, billing applications and any inter-PLMN financial -statement; [see TADIG PRD TD06]. 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 Stage 3: IREG PRD IR23]• IR24 International Roaming testing. [See Stage 4: IREG PRD IR24]IREG Document PRD IR88 defines the LTE roaming and LTE+2G/3G co-existence guidelines.

INTRODUCTION

Base Station System Application Part +Base Station SubsystemDomain Name System

IR35 General 3(42) IR3550

Page 4: Annex_10_IR35_direct LTE Roaming Test Woth Charging

IMSI

MSISDN

SGSN Number

SGSN Address

SMS Parameters

MS Purged for GPRS

MNRG

PDP Context Identifier

PDP Type

PDP Address

QoS Profile Subscribed

VPLMN Address Allowed

Prerequisites for LTE only testing:

HSS EPS Subscription Data:FieldIMSI IMSI is the main reference key.MSISDN The basic MSISDN of the UE (Presence of MSISDN is optional).IMEI / IMEISV International Mobile Equipment Identity - Software Version NumberMME Address The IP address of the MME currently serving this MS.MME Capabilities Indicates the capabilities of the MME with respect to core functionality e.g. regional access restrictions.MS PS Purged from EPC

Indicates that the EMM and ESM contexts of the UE are deleted from the MME.

ODB parameters Indicates that the status of the operator determined barring Access Restriction Indicates the access restriction subscription information. EPS Subscribed Charging Charactericstics

The charging characteristics for the MS, e.g. normal, prepaid, flat-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. 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

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.

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 Characteristics

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.

PLMN of PDN GW Identifies the PLMN in which the dynamically selected PDN GW is located

List of APN - PDN GW ID relations (for PDN subscription context with wildcard APN):

APN - P GW relation #n

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

4. S9 interface is implemented in HPLMN(a) and VPLMN(b) (when PMIP is used on S8)

8. Dynamic Address allocation for access to Intranet/ISP

Prerequisites for LTE+2G/3G Co-existence - 2G/3G ac cess towards PGW using Gp- or S8- Interface testing :

7. 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 can be sent by mobile during Initial Attach or can be set by default by the MME. The APN-Network Identifier defines to which external network the P-GW is connected. This means in detail the interface of the P-GW to an external network. This external interface at the P-GW is connected to the infrastructure providing Intranet functionality (e.g. local HTTP-Server) or to a kind of 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 MME accordingly

The GSN number and optional IP address pair related to the GGSN that shall be contacted when activity from the MS is detected and MNRG is set. The GSN number shall be either the number of the GGSN or the protocol-converting GSN as described in the subclause "MAP-based GGSN – HLR Signalling" and "GTP and MAP-based GGSN – HLR Signalling".

GGSN-list

PDP address, IP or X.121 address. This field shall be empty if dynamic addressing is allowed.

Indicates that the MM and PDP contexts of the MS are deleted from the SGSN.

Indicates that the MS is not reachable through an SGSN, and that the MS is marked as not reachable for GPRS at the SGSN and possibly at the GGSN.

Each IMSI contains zero or more of the following PDP context subscription records:

Index of the PDP context.

PDP type, e.g., PPP or IP.

6. MME and vPCRF(if PMIP is used) has access to DNS functionality

The APN and the identity of the dynamically allocated PDN GW of a PDN connection that is authorised by the PDN subscription context with the wildcard APN. The PDN GW identity may be either an FQDN or an IP address. The PDN GW identity refers to a specific PDN GW.

Towards a first introduction of LTE/EPC following prerequisites are assumed:1. LTE mobile stations supporting the network operation modes in VPLMN(b).2. The HSS contains LTE subscription data and routing information (PDN type, PDN address, APN, and VPLMN address allowed). 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 “Insert Subscriber Data” procedure. IMSI is the primary key to the EPS subscription data stored in the HSS. There may be several sets of HSS subscription data per IMSI.

Description

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.

The quality of service profile subscribed. QoS Profile Subscribed is the default level if a particular QoS profile is not requested.

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.

A label according to DNS naming conventions describing the access point to the external packet data network.In case of “Wild Card APN” this field shall be filled with “*”

Access Point Name

Each subscription profile contains one or more PDN subscription contexts:

The charging characteristics of this PDN Subscribed context for the MS, e.g. normal, prepaid, flat-rate, and/or hot billing subscription. The charging characteristics is associated with this APN.

3. Towards GPRS no supplementary services are invoked.4. The Gi-Interface is implemented in HPLMN(a) and VPLMN(b)5. The Gp-Interface is implemented (Inter-PLMN connection)6. SGSN/GGSN-access to DNS-Functionality7. 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 can be sent by mobile during PDP-context activation or can be set by default by the SGSN. The APN-Network Identifier defines to which external network the GGSN is connected. This means in detail the interface of the GGSN to an external network. This external interface at the GGSN is connected to the infrastructure providing Intranet functionality (e.g. local HTTP-Server) or to a kind of 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 GSM 23.60 and Annex A of TS 23. 60.8. Dynamic Address allocation for access to Intranet/ISP

The basic MSISDN of the MS.

The SS7 number of the SGSN currently serving this MS.

The IP address of the SGSN currently serving this MS.

SMS-related parameters, e.g., operator-determined barring.

IMSI is the main reference key.

The following prerequisites are assumed:1. LTE and GPRS user equipment (UE) supporting the network operation modes in VPLMN(b).

2. HSS contains EPS subscription data for LTE roaming. Prerequisites are same as described in the table "Prerequisies for LTE testing" above.

3. The HSS/HLR contains GPRS and EPS subscription data and routing information (PDP/PDN type (S), PDP/PDN address (S), APN (S), and VPLMN address allowed) for 2G/3G roaming.

These subscription data are permanent data in the HSS/HLR and have to be inserted for the tests. The HSS/HLR is accessible from the SGSN via the Gr interface. For roaming UEs, the HSS/HLR 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/HLR. There may be several sets of GPRS and EPS subscription data per IMSI.

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 above. If S4/S8 interfaces are used for 2G/3G roaming, the subscription information stored in HSS/HLR for 2G/3G roaming is defined below "HSS GPRS Subscription Data" table.

IR35 General 4(42) IR3550

Page 5: Annex_10_IR35_direct LTE Roaming Test Woth Charging

HSS GPRS Subscription Data:FieldIMSI

MSISDN

SGSN Number

SGSN Address

Subscribed Charging CharacteristicsTrace Reference

Trace Type

OMC Identity

SMS Parameters

MS Purged for GPRS

MNRG

GPRS-CSIMG-CSIAPN-OI Replacement

ODB for PS parameters

Access RestrictionIMEISVNRFSP Index

PDP Context Identifier

PDP Type

PDP Address

Access Point Name

QoS Profile Subscribed

VPLMN Address Allowed

PDP Context Charging CharacteristicsEPS subscribed QoS profileAPN-AMBR

P-GW Address

1.6 Equipment Requirements

1.6.1 User Equipment

User Equipment for GPRS Testing:

User Equipment for LTE/EPC Testing:

1.6.2 Test Equipment

Test equipment for GPRS only Testing:

Test equipment for LTE/EPC only Testing:

Test equipment for for LTE+2G/3G Co-existence (2G/3 G access towards PGW using Gp- or S8- Interface) Te sting:

3. Towards GPRS no supplementary services are invoked.4. The SGi-Interface is implemented in HPLMN(a) and VPLMN(b)5. The Gp-Interface or S8-Interface is implemented (Inter-PLMN connection)6. SGSN/PGW-access to DNS-Functionality7. 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 can be sent by mobile during PDP-context activation or can be 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 is connected to the infrastructure providing Intranet functionality (e.g. local HTTP-Server) or to a kind of 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-resolut ion algorithms are implemented correctly in his SGS N according 3GPP TS 23.060 and Annex A of 3GPP TS 2 3.060.8. Dynamic Address allocation for access to Intranet/ISP

(a) The availability of a CCITT # 7 tester able to decode SCCP, TCAP, MAP is highly advisable, but not strictly necessary for these tests. However it is essential for any analysis of test case failures.(b) The availability of a SGi, Gp, S8 and S4 interface IP testing and monitoring equipment is highly advisable.(c) Sample files and applications for data transfer testing.

PDP address, e.g., and IP address. This field shall be empty if dynamic addressing is allowed.

The address currently used for the P-GW supporting this APN

The quality of service profile subscribed. QoS Profile Subscribed is the default level if a particular QoS profile is not requested.

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.

A label according to DNS naming conventions describing the access point to the external packet data network.In case of “Wild Card APN” this field shall be filled with “*”

The charging characteristics of this PDP Bearer Context e.g. normal, prepaid, flat-rate and/or hot billing

The EPS bearer level QoS parameter values for that APN's default bearer (QCI and ARP)

the maximum aggregated uplink and downlink MBR values to be shared across all Non-GBR EPS bearers, which are established for this APN

Each IMSI contains zero or more of the following PDP context subscription records:

Index of the PDP context.

PDP type, e.g., PPP or IP (IPv4, IPv6, IPv4v6)

SMS-related parameters, e.g. operator-determined barring

An index to specific RRM configuration in the UTRAN/GERAN

Optional GPRS CAMEL Subscription information, see TS23.016Optional Mobility Management for GPRS CAMEL subscription information, see TS23.016

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.

Indicates that the status of the opeartor determined barring for packet oriented services

The Equipment described in this Section is necessary for undertaking the test cases described in Section 2 and 19.

(a) Two User Equipments supplied by VPLMN(b).(b) 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:i) Spare cards in case of failureii) Allocation from different HSSs(c) It shall be possible to specify what types of User Equipments are supplied for testing between operator agreement (HPLMN (a) and VPLMN (b)).

(a) The availability of a SGi, S6a, S8 and S9 interface IP testing and monitoring equipment is highly advisable.(b) Sample files and applications for data transfer testing.

(a) The availability of a CCITT # 7 tester able to decode SCCP, TCAP, MAP, BSSAP+ is highly advisable, but not strictly necessary for these tests. However it is essential for any analysis of test case failures.(b) The availability of a Gi and Gp interface IP testing and monitoring equipment is highly advisable.(c) Sample files and applications for data transfer testing.

The Equipment described in this Section is necessary for undertaking the test cases described in Section 2.

(a) Two Mobile Equipments supplied by VPLMN(b). (The Mobile Stations should be in minimum class C-GPRS Mobile Stations however class A- and B-Mobiles can be used also)

(b) Two GPRS compatible SIMs supplied by HPLMN(a).The supply of additional SIMs may be agreed by the HPLMN(a) and VPLMN(b), typically for the purposes of:i) Spare cards in case of failureii) Allocation from different HLRs(c) It shall be possible to specify what types of Mobile Equipments are supplied for testing between operator agreement (HPLMN (a) and VPLMN (b)).

Indicates that the MM and PDP contexts of the MS are deleted from the SGSN.

Indicates that the MS is not reachable through an SGSN, and that the MS is marked as not reachable for GPRS at the SGSN and possibly at the GGSN.

GGSN-list The GSN number and optional IP address pair related to the GGSN that shall be contacted when activity from the MS is detected and MNRG is set. The GSN number shall be either the number of the GGSN or the protocol-converting GSN as described in the subclause "MAP-based GGSN – HLR Signalling" and "GTP and MAP-based GGSN – HLR Signalling".

Indicates the access restriction subscription information (Note, the access restriction applies to both packet and circuit oriented services)International Mobile Equipment IdentitySoftware Version Number

Identifies a record or a collection of records for a particular trace

DescriptionIMSI is the main reference key.

The basic MSISDN of the MS.

The SS7 number of the SGSN currently serving this MS.

The IP address of the SGSN currently serving this MS.

Indicates the type of trace, e.g. MSC/BSS trace, HLR trace, and/or SGSN/GGSN/BSS trace

Identifies the OMC that shall receive the trace record(s)

The charging characteristics for the MS e.g. normal, prepaid, flat-rate, and /or hot billing subscription

IR35 General 5(42) IR3550

Page 6: Annex_10_IR35_direct LTE Roaming Test Woth Charging

IR35 General 6(42) IR3550

Page 7: Annex_10_IR35_direct LTE Roaming Test Woth Charging

2

The test configuration for LTE/EPC (GTP based) is shown below

The test configuration for LTE/EPC (PMIP based) is shown below

The test cases are divided in three groups:

1) GPRS-attachment and -detachment, LTE-attachement and -detachment2) Services /PDP-Context Activation/EPS Bearer Establishment3) MAP/DiameterTests

Each operator has to make sure that the APN-resolut ion algorithms are implemented correctly in his SGS N according to GSM 23.60 and Annex A of 3GPP TS 23. 060 for GPRS, and in MME according to 3GPP TS 23.401 for LTE.

The test configuration for GPRS is shown below. It is anticipated that it may be necessary to monitor both signalling messages and IP packet data on the Network Entity interfaces shown in the diagram. However this is not a firm requirement for this test specification.

TEST CASES for GPRS and LTE - overview

H LR

PLM N (a)

S IM (a)

M S1SIM (a)

M S2

P LM N (b)

C oun try (b )C oun try (a )

M = M on itor

R AD IU S /D H C P -SE R VE R

M

IN TR A N ET /IS P

LO C AL D N S

R AD IU S/D H C P -SE R V ER

LO C AL D N S

IN TR A N ET /IS P

/SG SN

/G G SN/SG S N

BSS orU TR ANor

R O O T D N S

G PR S EX C H A N G E

M

In tra PLM N

/G G SN

In tra PLM N

PLMN(a)

USIM(a)

UE 1

PLMN(b)

Country (b) Country (a)

M = Monitor

RADIUS/DHCP-SERVER

M

INTRANET/ISP

LOCAL DNS

RADIUS/DHCP-SERVER

LOCAL DNS

INTRANET/ISP

ROOT DNS

M PGW

Intra PLMN

SGW eNB

MME

Diameter Edge Agent

Intra PLMN GPRS / IP EXCHANGE

USIM(b)

UE 2

PGW

HPCRF

Diameter Edge Agent

MME HSS

PLMN(a)

USIM(a)

UE 1

PLMN(b)

Country (b) Country (a)

= Monitor

RADIUS/DHCP-SERVER

M

INTRANET/ISP

LOCAL DNS

RADIUS/DHCP-SERVER

LOCAL DNS

INTRANET/ISP

MME

ROOT DNS

PGW

eNB

MME Intra PLMN

GPRS / IP EXCHANGE

USIM(b)

UE 2

PGW

HPCRF

Diameter Edge Agent

HSS SGW

M

Intra PLMN Diameter Edge Agent

VPCRF

IR35 General 7(42) IR3550

Page 8: Annex_10_IR35_direct LTE Roaming Test Woth Charging

The test configuration for LTE and 2G/3G Co-exisitence Roaming is shown below. See GSMA PRD IR.88 for the details of roaming scenarios.

2.1 GPRS-Attachment

2.1.1 GPRS-Attach of MS1(a) in VPLMN(b) (GPRS Attach only)

Preconditions:

Action:

Result:

Comments:

Message-flow: (GPRS Attach only)

Charging aspects:

Opening of a M-CDRCharging parameters to collect/compare:1) IMSI/MSISDN of the MS2) IMEI of the ME, if available3) Timestamp when GPRS-Attach is done (The M-CDR is closed after GPRS-Detach)

This test case confirms operation of Insert Subscriber Data procedures after GPRS-Attach only.It checks the support of relevant MAP operations, TCAP processes and SCCP addressing.

Power-up MS1(a) and perform GPRS Attach only on VPLMN(b). Check MM contexts in MS1(a) and SGSN(b) for the IMSI/P-TMSI /MSISDN of MS1(a).

Successful result if MS1(a) is in READY state (2.5G)Successful result if valid MM contexts are established in the MS1(a) and SGSN(b).

MS1(a) contains SIM of HPLMN(a).No valid MM contexts are established for MS1(a).HLR(a) record contains basic service information including GPRS subscription data.

2 . Id en tity R e sp o n se

1 . A tta ch R eq u e st (A tta ch T y p e: G P R S A tta ch o n ly )

2 . Id en tity R e q u est

3 . A u th en ticatio n

5 a. U p d ate L o c atio n

5c In ser t S u bscr iber D ata A ck

M S B S S U T R A N S G S N (b ) H L R (a )E IR

9 . A ttac h C o m p le te

8 . A ttach A cc ep t

5 b . In se r S u b scrib er D ata

5 d U p d ate L o catio n A c k

4 . IM E I C h ec k

M = Monitor

PLMN(a)

USIM(a)

UE 1

PLMN(b)

Country (b) Country (a)

M = Monitor

RADIUS/DHCP-SERVER

M

INTRANET/ISP

LOCAL DNS

RADIUS/DHCP-SERVER

MME

ROOT DNS

PGW

eNB

MME GPRS / IP EXCHANGE

USIM(b)

UE 2

HPCRF

Diameter Edge Agent

HSS

M

Diameter Edge Agent

VPCRF

SGW SGSN

RNC

LOCAL DNS

Intra PLMN

INTRANET/ISP

PGW

GGSN

GGSN

Intra PLMN

IR35 General 8(42) IR3550

Page 9: Annex_10_IR35_direct LTE Roaming Test Woth Charging

2.2 Services (Intranet-/ISP-Access, WAP, MMS) / PDP-Context Activation

2.2.1

Preconditions:

Action:

Result:

Action: MS1(a) performs “Deactivate PDP Context Request”.

Result: PDP-Context is deactivated

Comments:

2.2.2

Preconditions:

WAP access of MS1(a) in VPLMN(b) using home GGSN (u ser provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), WAP-Browsi ng

MS1(a) performs “Activate PDP Context Request”. PDP type (R) is sent by MS1(a). A PDP Address is not sent by MS1(a) and is not present in a PDP context subscription record. (Dynamic address allocation)APN (R) (Network-ID, no Operator-ID) is sent by MS1(a).Pre-defined file is requested/transferred from External Network (Network-ID) to MS1(a) by accessing HTTP-server over WEB-browsing.SGSN(b) receives APN(R) sent by MS1(a).SGSN(b) selects PDP context subscription record (APN(S ), APN(S)=(APN(R)) and sets selection mode parameter to “subscribed”.SGSN interrogates DNS-Functionality with selected APN with appended HPLMN APN-Operator-IDSelected APN is translated to a GGSN(a)-Address in the HPLMN(a).SGSN(b) returns an “Activate PDP Context Accept” message to the MS1(a) including PDP type and PDP address.Valid PDP contexts are established in the MS1(a).Connection to Network specified by APN(Network-ID) is established.Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP-Service.

This test case confirms PDP context activation/deactivation towards a home GGSN(a) with: • APN(R) is not empty; (Network-ID, no Operator-ID)• Setting of APN (Operator-ID) by subscription for HPLMN(a) (APN(S)).• Setting up IP-tunnel connections (GTP, IP, UDP/TCP)• 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.

Charging aspects:

M-CDR is already open (GPRS-Attach)Opening of S-CDR and G-CDR by PDP-context-activation (The S-CDR and G-CDR are closed after PDP-context-deactivation)

Charging parameters to collect/compare: (S-CDR and G-CDR)1) IMSI/MSISDN of the MS2) IMEI of the ME, if available3) Access Point Name4) Timestamp when PDP-context-activation is done5) Timestamp when downloading of pre-defined file is started6) Size of total down- and uplink data towards download of predefined file(The volume of the predefined file to be transferred has to create in minimum 11/2 S-CDR. How to create this S-CDR and the amount of data to be transferred is operator dependent) 7) Timestamp when PDP-context-deactivation is done

Intranet-/ISP-Access of MS1(a) in VPLMN(b) using home GGSN (use r provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), HTTP-WEB -Browsing

MS1(a) is GPRS-Attached in VPLMN(b). (MS in STANDBY or READY state for 2.5G)No valid PDP contexts are established in the MS1(a).PDP context subscription record(s) exists in HLR(a) where PDP type (S) = PDP type (R).One PDP context subscription record exists in HLR(a) where APN(S) = APN(R). VPLMN not allowed for selected PDP context subscription records.

MS1(a) is GPRS-Attached in VPLMN(b). (MS in STANDBY or READY state for 2.5G)No valid PDP contexts are established in the MS1(a).PDP context subscription record(s) exists in HLR(a) where PDP type (S) = PDP type (R).One PDP context subscription record exists in HLR(a) where APN(S) = APN(R).

SGSN

VGGSN

APN:Intranet/ISP.mnc123.mcc456.gprs

mnc123.mcc456.gprs (VPLMN)

DNS

mnc789.mcc888.gprs (HPLMN)

HGGSN APN:Intranet/ISP.mnc.789.mcc888.gprs

HLR

VPLMN HPLMN

APN:Intranet/ISP

VPLMN add. not allowed

DNS success

SGSN

VGGSN

APN:WAP.mnc123.mcc456.gprs

mnc123.mcc456.gprs (VPLMN)

DNS

mnc789.mcc888.gprs (HPLMN)

HGGSN

APN:WAP.mnc .789.mcc888.gprs

HLR

VPLMN HPLMN

APN:WAP

VPLMN add. not allowed

DNS success

IR35 General 9(42) IR3550

Page 10: Annex_10_IR35_direct LTE Roaming Test Woth Charging

Action:

Result:

Action: MS1(a) performs “Deactivate PDP Context Request”.

Result: PDP-Context is deactivated

Comments:

2.2.3 MMS with MS1(a), MS2(a) in VPLMN(b) using home GGSN and MMSC

Preconditions:

Action:

Result:

Comments:

2.2.4

Preconditions:

Action:

Result:

Action: UE1(a) performs “Deactivate PDP Context Request”.

Result: PDP-Context is deactivated

Comments:

UE1(a) is GPRS-Attached in VPLMN(b). (UE in STANDBY or READY state for 2.5G)No valid PDP contexts are established in the UE1(a).PDP context subscription record(s) exists in HSS(a) where PDP type (S) = PDP type (R).One PDP context subscription record exists in HSS(a) where APN(S) = APN(R). VPLMN not allowed for selected PDP context subscription records.UE1(a) performs “Activate PDP Context Request”. PDP type (R) is sent by UE1(a). A PDP Address is not sent by UE1(a) and is not present in a PDP context subscription record. (Dynamic address allocation)APN (R) (Network-ID, no Operator-ID) is sent by UE1(a).Pre-defined file is requested/transferred from External Network (Network-ID) to UE1(a) by accessing HTTP-server over WEB-browsing.SGSN(b) receives APN(R) sent by UE1(a).SGSN(b) selects PDP context subscription record (APN(S ), APN(S)=(APN(R)) and sets selection mode parameter to “subscribed”.SGSN interrogates DNS-Functionality using procedures defined in 3GPP TS29.303 with selected APN with appended HPLMN APN-Operator-IDSelected APN is translated to a PGW-Address in the HPLMN(a).SGSN(b) returns an “Activate PDP Context Accept” message to the UE1(a) including PDP type and PDP address.Valid PDP contexts are established in the UE1(a).Connection to Network specified by APN(Network-ID) is established.Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP-Service.

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

Intranet-/ISP-Access of UE1(a) in VPLMN(b) using home PGW over Gp-interface (user provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), HTTP-WEB -Browsing

This test case confirms PDP context activation/deactivation towards a home GGSN(a) with: • APN(R) is not empty; (Network-ID, no Operator-ID)• Setting of APN (Operator-ID) by subscription for HPLMN(a) (APN(S)).• Setting up IP-tunnel connections (GTP, IP, UDP/TCP)• 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.

This test case confirms correct operation of mobile-originated/terminated MMS routing and transfer over GPRS radio channels

MMS-MO/MT is provisioned MS1(a) and MS2(a) are registered in VPLMN(b).

Use MS1(a) to transmit a Multimedia Message to MS2(a) via the Home MMSCAwait delivery of Multimedia Message to MS2(a)Check contents of Multimedia Message with those transmitted

Successful result if Multimedia Message is correctly delivered. If delivery report is requested, check that it is correctly delivered.

M-CDR is already open (GPRS-Attach)S-CDR is already open (PDP-context-activation)Charging parameters to collect/compare: (M-CDR and S-CDR)1) IMSI/MSISDN of the MS2) IMEI of the ME, if available3) Timestamp when MMS is send by MS1(a) (S-CDR)4) Timestamp when MMS is fetched by MS2(a) (S-CDR)5) Amount of total data DL / UL transfer MS1(a) & MS2(a)6) MMS APN (S-CDR)

Charging aspects:

One PDP context subscription record exists in HLR(a) where APN(S) = APN(R).VPLMN not allowed for selected PDP context subscription records.MS1(a) performs “Activate PDP Context Request”. PDP type (R) is sent by MS1(a). A PDP Address is not sent by MS1(a) and is not present in a PDP context subscription record. (Dynamic address allocation)APN (R) (Network-ID, no Operator-ID) is sent by MS1(a).Pre-defined file is requested/transferred from External Network (Network-ID) to MS1(a) by accessing WAP-server over WAP-browsingSGSN(b) receives APN(R) sent by MS1(a).SGSN(b) selects PDP context subscription record (APN(S ), APN(S)=(APN(R)) and sets selection mode parameter to “subscribed”.SGSN interrogates DNS-Functionality with selected APN with appended HPLMN APN-Operator-ID.Selected APN is translated to a GGSN(a)-Address in the HPLMN(a).SGSN(b) returns an “Activate PDP Context Accept” message to the MS1(a) including PDP type and PDP address.Valid PDP contexts are established in the MS1(a).Connection to Network specified by APN(Network-ID) is established.Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using WAP-Service.

SGSN

VGGSN

APN:Intranet/ISP.mnc123.mcc456.gprs

mnc123.mcc456.gprs (VPLMN)

DNS (as per 3GPP TS 29.303)

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

HPGW APN: Internet/ISP.apn.epc.mnc123.mcc888.3gppnetwork.org

HSS

VPLMN HPLMN

APN:Intranet/ISP

VPLMN add. not allowed

DNS (including S-NAPTR procedure) success

IR35 General 10(42) IR3550

Page 11: Annex_10_IR35_direct LTE Roaming Test Woth Charging

2.2.5

Preconditions:

Action:

Result:

Action: UE1(a) performs “Deactivate PDP Context Request”.

Result: EPS Bearer Context is deactivated

Comments:

• 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.

SGSN(b) receives APN(R) sent by UE1(a).SGSN(b) selects EPS Bearer subscription record (APN(S ), APN(S)=(APN(R)) and sets selection mode parameter to “subscribed”.SGSN interrogates DNS-Functionality using procedures defined in 3GPP TS29.303 with selected APN with appended HPLMN APN-Operator-IDSelected APN is translated to a SGW-Address in the VPLMN(b) and PGW-Address in the HPLMN(a).SGSN(b) returns an “Activate PDP Context Accept” message to the UE1(a) including PDN type and PDN address.Valid EPS Bearer contexts are established in the UE1(a).Connection to Network specified by APN(Network-ID) is established.Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP-Service.

This test case confirms EPS Bearer context activation/deactivation towards a visited SGW(b) and home PGW(a) with: • APN(R) is not empty; (Network-ID, no Operator-ID)• Setting of APN (Operator-ID) by subscription for HPLMN(a) (APN(S)).• Setting up IP-tunnel connections (GTP, IP, UDP/TCP)• 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.

Intranet-/ISP-Access of UE1(a) in VPLMN(b) using visited SGW and home PGW over S8-interface (user provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), HTTP-WEB- Browsing

UE1(a) is GPRS-Attached in VPLMN(b). (UE in STANDBY or READY state for 2.5G)No valid EPS Bearers are established in the UE1(a).EPS Bearer subscription record(s) exists in HSS(a) where PDN type (S) = PDN type (R).One PDN context subscription record exists in HSS(a) where APN(S) = APN(R). VPLMN not allowed for selected EPS Bearer context subscription records.UE1(a) performs “Activate PDP Context Request”. PDP type (R) is sent by UE1(a). A PDN Address is not sent by UE1(a) and is not present in a EPS Bearer context subscription record. (Dynamic address allocation)APN (R) (Network-ID, no Operator-ID) is sent by UE1(a).Pre-defined file is requested/transferred from External Network (Network-ID) to MS1(a) by accessing HTTP-server over WEB-browsing.

SGSN

VGGSN

APN:Intranet/ISP.mnc123.mcc456.gprs

mnc123.mcc456.gprs (VPLMN)

DNS (as per 3GPP TS 29.303)

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

HPGW APN: Internet/ISP.apn.epc.mnc123.mcc888.3gppnetwork.org

HSS

VPLMN HPLMN

APN:Intranet/ISP

VPLMN add. not allowed

DNS (including S-NAPTR procedure) success

SGW DNS (as per 3GPP TS 29.303) to select SGW

IR35 General 11(42) IR3550

Page 12: Annex_10_IR35_direct LTE Roaming Test Woth Charging

2.3

2.3.1 Mobile originated and terminated SMS (MS1(a) GPRS-Attached only / MS2(a) GPRS-Attached only)

Preconditions:

Action:

Result:

Comments:

Message flow: Mobile originated and terminated SMS transfer over GPRS channels

2.3.2 Location cancellation for MS1(a)-GPRS Subscription held in VPLMN(b)

Preconditions:

Action:

Result:

Comments:

2.3.3 Operator Determined Barring for all MS initiated PDP cont ext activatons of MS 1(a).

Preconditions:

Action:

Result:

Comments:

SMS-MO/MT is provisioned in HLR subscription including GPRS subscription data.MS1(a) and MS2(a) are registered in VPLMN(b).

SGSN(b) in VPLMN(b) contains GPRS-subscription information of MS1(a) and PDP-context for MS1(a) is activated.

Successful result if Short Message is correctly delivered to MS2(a).

This test case confirms correct operation of mobile-originated/terminated SMS routing and transfer over GPRS radio channels including “Message Waiting” and “Note MS Present” procedures.

Charging aspects:

M-CDR is already open (GPRS-Attach)S-CDR is already open (PDP-context-activation)Charging parameters to collect/compare: (M-CDR and S-CDR)1) IMSI/MSISDN of the MS2) IMEI of the ME, if available3) Timestamp when GPRS-Attach of MS2(a) is done (M-CDR)4) Timestamp when SMS is send (S-CDR)5) Timestamp when SMS is received (S-CDR)6) Timestamp when GPRS-Detach of MS1(a) and MS2(a) is done (M-CDR)7) SMS-SC-Number (S-CDR)

Use MS1(a) to transmit a 160 character Short Message to MS2(a) via the Home Country SMS - Service Centre with Message Waiting priority selected.Await delivery of Short Message to MS2(a)Check contents of Short Message with those transmitted.

Successful result if SGSN(b) record for MS1(a) contains ODB information and no PDP-context-activation and SMS-mobile originated attempts are successful.

SGSN(b) in VPLMN(b) contains subscription information of MS1(a).

HLR-Initiated Detach Procedure (reference 3GPP TS23.060)The HLR-Initiated Detach procedure is initiated by the HLR. The HLR uses this procedure for operator determined purposes to request the removal of a subscriber's MM and PDP contexts at the SGSN

MAP-Tests (SMS, Location Cancellation, GPRS-Barring)

This test case confirms that the ODB procedure for outgoing calls operates correctly.

HPLMN(a) personnel activates ODB for MS initiated PDP context activation for MS1(a) from HLR(a) either using HLR`s Man-Machine Interface or via Administrative Data Centre (ADC) input to HLR(a).Check SGSN(b) for records of MS1(a).Try to make a PDP-context-activation from MS1(a) and try to send a SMS from MS1(a).

HPLMN(a) personal deletes MS1(a) GPRS-subscription from HLR(a) either using HLR`s Man-Machine Interface not via Administrative Data Centre (ADC) input to HLR(a).

Successful result if SGSN(b) and GGSN(a) or GGSN(b) record for MS1(a) has been erased and PDP-Context for MS1(a) has been deactivated.

This test case confirms that the “Cancel Location” between HLR(a) and SGSN(b) procedure and “PDP Context Deactivation” initiated by the network operates correctly.

HLRMS BSS/UTRAN GGSNSGSN M SC/VLR

3. Delete PDP Context Request

1. Cancel Location

4. GPRS Detach Indication

2. Detach Request

6. Cancel Location Ack

3. Delete PDP Context Response

5. Detach Accept

7. PS Signalling Connection Release

C2

C1

IR35 General 12(42) IR3550

Page 13: Annex_10_IR35_direct LTE Roaming Test Woth Charging

19.1

19.1.1

Preconditions:

Action:

Expected Result:

Comments:

Message-flow: LTE-Attach (including PDN connectivity establishment) procedure

Message-flow: UE requested LTE-Detach

G S M A - SPECIFIC TESTS

LTE Attach and Detach

UE1(a) contains USIM of HPLMN(a).No valid EMM contexts are established for UE1(a).HSS(a) record contains basic service information including EPS subscription data.No valid PDN connectivity are established in the UE1(a).One EPS bearer context subscription record exists in HSS(a) where APN(S) = APN(R). VPLMN not allowed for selected EPS context subscription records.

Power-up UE1(a) and perform LTE Attach only on VPLMN(b). Check EMM contexts in UE1(a) and MME(b) for the IMSI/GUTI /MSISDN of MS1(a).A PDN Address is not sent by UE1(a) and is not present in a EPS context subscription record. (Dynamic address allocation)APN (R) (Network-ID, no Operator-ID) is sent by UE1(a).PDN connectivity establishment should be testedLTE-detach procedure should be tested

Charging parameters to collect/compare:1) IMSI/MSISDN of the UE2) IMEI of the UE, if available3) Timestamp when LTE-Initial-Attach with EPS bearer establishment is done4) Access Point Name5) Timestamp when total down- and uplink data started6) Size of total down- and uplink data during the EPS bearer establishment7) Timestamp when LTE Detach is done8) LTE-detach

Charging aspects:

Successful result if UE1(a) is in EMM-REGISTERED and ECM-CONNECTED stateSuccessful result if valid EMM contexts are established in the UE1(a) and MME(b).Successful result if PDN Connectivity towards the default APN is established.Successful result if LTE-detach for UE1(a) is completed.

This test case confirms operation of Insert Subscriber Data procedures after LTE-Attach only.It checks the support of relevant Diameter operations

When GTP is used

When PMIP is used

1. Attach Request

MME Serving GW VPCRF HPCRFPDN GW

2. Attach Request

eNodeB UE

4. Identity Request 4. Identity Response 5a. Authentication / Security

22. Initial Context Setup Request / Attach Accept

24. RRC Connection Reconfiguration Complete 23. RRC Connection Reconfiguration

25. Initial Context Setup Response

21. Create Session Response

12. Create Session Request

8. Update Location Request

11. Update Location Ack

13. Create Session Request

15. Create Session Response

EIR

5b. ME Identity Check 5b. Identity Request/Response

14. PCEF Initiated IP-CAN Session Establishment/Modification

6. Ciphered Options Request

6. Ciphered Options Response

26. Direct Transfer 27. Attach Complete

19. Proxy Binding Ack

17. Proxy Binding Update

16. Gateway Control Session Establishment Procedure

18. IP-CAN Session Establishment

Procedure

20. Gateway Control and QoS Rules Provison Procedure

HSS

When GTP is used

1. Detach Request

MME Serving GW VPCRF HPCRFPDN GW

2. Detach Request

eNodeB UE

3. Delete Session Request

5. Delete Session Request

7. Delete Session Response

6. PCEF Initiated IP-CAN Session Termination

4. Delete Session Response

IR35 General 13(42) IR3550

Page 14: Annex_10_IR35_direct LTE Roaming Test Woth Charging

19.2.1

Preconditions:

Action:

Expected Result:

Comments:

Message-flow: LTE Cancel Location

……

………………

19.3.1

Preconditions:

Action:

Expected Result:

Comments:

Message-flow: LTE Operator Determined Barring

LTE Cancel Location

LTE Operator Determined Barring

Charging aspects:

none

Charging aspects:

none

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

MME(b) in VPLMN(b) contains EPS-subscription information of UE1(a) and PDN connectivity for UE1(a) is activated.

HPLMN(a) personnel activates 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).Check MME(b) for records of UE1(a).Try to make a LTE-attach from UE1(a) and send attach request from UE1(a).

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

UE1(a) is attached to VPLMN(b) and has a PDN connectivity.MME(b) in VPLMN(b) contains subscription information of UE1(a).

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

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

eNodeB MME

2. Detach Request

3. Delete Session Request

11. Delete Session Response 12. Detach Accept

1. Cancel Location

13. Cancel Location ACK

UE Serving GW PDN GW hPCRF HSS vPCRF

7. Gateway Control Session Termination Procedure

9. PCEF-Initiated IP-CAN Session Termination

Procedure

8. Proxy Binding Update

10. Proxy Binding Ack

When PMIP is used

5. PCEF-Initiated IP-CAN Session Termination

Procedure

4. Delete Session Request

6. Delete Session Resonse

When GTP is used

When PMIP is used

11. Proxy Binding Ack

9. Proxy Binding Update

8 Gateway Control Session Termination Procedure

10. IP-CAN Session Termination Procedure

12. Detach Accept

MME UE HSS

3. Reject

1. Insert Subscriber Data

2. Attach Request

IR35 General 14(42) IR3550

Page 15: Annex_10_IR35_direct LTE Roaming Test Woth Charging

19.4.1

Preconditions:Action:

Expected Result:Comments:

19.5.1

Preconditions:Action:

Expected Result:Comments:

19.6.1

Preconditions:Action:

Expected Result:Comments:

19.7.1

Preconditions:Action:

Expected Result:Comments:

19.8.1

Preconditions:Action:

Expected Result:Comments:

19.9.1

Preconditions:Action:

Expected Result:Comments:

19.10.1

Preconditions:Action:

Expected Result:Comments:

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 19.1.1

Take the space, whatever you require to decribe the test case by inserting additional lines !

G S M A -SPEC. TEST CASE HEADER 19.8.1 (not in use now)

Detail Text 3 (Result) 19.1.1

Take the space, whatever you require to decribe the test case by inserting additional lines !

Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 3 (Result) 19.1.1

Detail Text 4Detail Text 5

G S M A -SPEC. TEST CASE HEADER 19.5.1 (not in use now)

Detail Text 4

Detail Text 3 (Result) 19.1.1

Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 3 (Result) 19.1.1

Detail Text 5

Detail Text 5

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1

Detail Text 5

Charging aspects:

G S M A -SPEC. TEST CASE HEADER 19.4.1 (not in use now)

Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 4

Charging aspects:

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 19.1.1

Detail Text 2 / Action- field in General TC 19.1.1 Detail Text 3 (Result) 19.1.1

Charging aspects:

Detail Text 2 / Action- field in General TC 19.1.1

Charging aspects:

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1

Detail Text 4

G S M A -SPEC. TEST CASE HEADER 19.7.1 (not in use now)

Charging aspects:

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 19.1.1

Charging aspects:

G S M A -SPEC. TEST CASE HEADER 19.9.1 (not in use now)

Detail Text 4Detail Text 5

Charging aspects:

Detail Text 4

Detail Text 2 / Action- field in General TC 19.1.1 Detail Text 3 (Result) 19.1.1

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 19.1.1

Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 5Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 4Detail Text 3 (Result) 19.1.1

Detail Text 5

G S M A -SPEC. TEST CASE HEADER 19.10.1 (not in use now)

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1

G S M A -SPEC. TEST CASE HEADER 19.6.1 (not in use now)

IR35 General 15(42) IR3550

Page 16: Annex_10_IR35_direct LTE Roaming Test Woth Charging

20.1

20.1.1

Preconditions:Action:

Expected Result:Comments:

20.2.1

Preconditions:Action:

Expected Result:Comments:

20.3.1

Preconditions:Action:

Expected Result:Comments:

20.4.1

Preconditions:Action:

Expected Result:Comments:

20.5.1

Preconditions:Action:

Expected Result:Comments:

20.6.1

Preconditions:Action:

Expected Result:Comments:

20.7.1

Preconditions:Action:

Expected Result:Comments:

20.8.1

Preconditions:Action:

Expected Result:Comments:

20.9.1

Preconditions:Action:

Detail Text 4

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 20.7.1

Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 2 / Action- field in General TC 20.5.1

Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 3 (Result) 20.5.1

Detail Text 3 (Result) 20.1.1

Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 4Detail Text 5

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1

Detail Text 5

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 20.9.1

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 20.8.1 Detail Text 3 (Result) 20.8.1

O P E R A T O R -SPEC. TEST CASE HEADER 20.9.1

Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 20.3.1 Detail Text 3 (Result) 20.3.1

O P E R A T O R -SPEC. TEST CASE HEADER 20.1.1

O P E R A T O R- SPECIFIC TESTS

Charging aspects:

Detail Text 5Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 2 / Action- field in General TC 20.1.1

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 20.2.1 Detail Text 3 (Result) 20.2.1Detail Text 4

Charging aspects:

O P E R A T O R -SPEC. TEST CASE HEADER 20.2.1

Detail Text 4Detail Text 5

Charging aspects:

O P E R A T O R -SPEC. TEST CASE HEADER 20.3.1

Charging aspects:

O P E R A T O R -SPEC. TEST CASE HEADER 20.4.1

Detail Text 5Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 20.4.1 Detail Text 3 (Result) 20.4.1Detail Text 4

O P E R A T O R -SPEC. TEST CASE HEADER 20.6.1

Detail Text 4Detail Text 5

Charging aspects:

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1

O P E R A T O R -SPEC. TEST CASE HEADER 20.5.1

Charging aspects:

O P E R A T O R -SPEC. TEST CASE HEADER 20.7.1

Detail Text 5Take the space, whatever you require to decribe the test case by inserting additional lines !

Charging aspects:

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 20.6.1

Charging aspects:

O P E R A T O R -SPEC. TEST CASE HEADER 20.8.1

Charging aspects:

Detail Text 3 (Result) 20.6.1Detail Text 4

Detail Text 3 (Result) 20.7.1

Detail Text 5Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 4

IR35 General 16(42) IR3550

Page 17: Annex_10_IR35_direct LTE Roaming Test Woth Charging

Expected Result:Comments:

20.10.1

Preconditions:Action:

Expected Result:Comments:

Detail Text 3 (Result) 20.9.1

Charging aspects:

O P E R A T O R -SPEC. TEST CASE HEADER 20.10.1

Detail Text 5Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 1 MS1(a/b) "action" MS2 (a/b) "action" MS3 (a/b) /1Detail Text 2 / Action- field in General TC 20.10.1 Detail Text 3 (Result) 20.10.1Detail Text 4

Take the space, whatever you require to decribe the test case by inserting additional lines !

Detail Text 4Detail Text 5

IR35 General 17(42) IR3550

Page 18: Annex_10_IR35_direct LTE Roaming Test Woth Charging

6

6.1 Test case selection and result overview

Roaming Scenario to be Tested(H)PLMN

(a)(V)PLMN

(b)YES / NO

2G / GSM 2G / GSM3G / UMTS 2G / GSM2G / GSM 3G / UMTS3G / UMTS 3G / UMTSLTE LTE Yes

LTE(PGW) 2G/3G(Gp) No

LTE(PGW) 2G/3G(S8) No

In the following table the HPLMN should indicate the test cases that are requested to be performed by the roaming partner (VPLMN).

Requested Test-cases & Description Results

1 Y E S 2.1.1

1 Y E S 2.2.1

1 Y E S 2.2.2

1 Y E S 2.2.3

1 Y E S 2.2.4

1 Y E S 2.2.5

1 Y E S 2.3.1

1 Y E S 2.3.2

1 Y E S 2.3.3

1 Y E S 19.1.1

1 Y E S 19.2.1

1 Y E S 19.3.1

1 No 19.4.1

1 No 19.5.1

1 No 19.6.1

1 No 19.7.1

1 No 19.8.1

1 No 19.9.1

1 No 19.10.1

1 Y E S 20.1.1

1 Y E S 20.2.1

1 Y E S 20.3.1

1 Y E S 20.4.1

1 Y E S 20.5.1

1 Y E S 20.6.1

1 Y E S 20.7.1

1 Y E S 20.8.1

1 Y E S 20.9.1

1 Y E S 20.10.1

29

6.2

This certificate confirms the successful completion of selected Tests in 6.1 above

Subscribers of HPLMNPLMN Network visited

Other comments

The tests were completed on.Date:

The testing team in HPLMN

O P E R A T O R -SPEC. TEST CASE HEADER 20.8.1

G S M A -SPEC. TEST CASE HEADER 19.7.1 (not in use now)

O P E R A T O R -SPEC. TEST CASE HEADER 20.7.1

Test CaseSelection

Intranet-/ISP-Access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), HTTP-WEB-BrowsingWAP access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), WAP-Browsing

G S M A -SPEC. TEST CASE HEADER 19.4.1 (not in use now)

G S M A -SPEC. TEST CASE HEADER 19.5.1 (not in use now)

LTE Attach and Detach

Location cancellation for MS1(a)-GPRS Subscription held in VPLMN(b)

LTE Cancel Location

MMS with MS1(a), MS2(a) in VPLMN(b) using home GGSN and MMSC

Test case selection and Completion Certificates

O P E R A T O R -SPEC. TEST CASE HEADER 20.10.1

IREG-comments from "IR35 TEST CASES", if any

GPRS-Attach of MS1(a) in VPLMN(b) (GPRS Attach only)

Mobile originated and terminated SMS (MS1(a) GPRS-Attached only / MS2(a) GPRS-Attached only)

Intranet-/ISP-Access of UE1(a) in VPLMN(b) using home PGW over Gp-interface (user provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), HTTP-WEB-BrowsingIntranet-/ISP-Access of UE1(a) in VPLMN(b) using visited SGW and home PGW over S8-interface (user provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), HTTP-WEB-Browsing

LTE Operator Determined Barring

O P E R A T O R -SPEC. TEST CASE HEADER 20.9.1

G S M A -SPEC. TEST CASE HEADER 19.6.1 (not in use now)

O P E R A T O R -SPEC. TEST CASE HEADER 20.3.1

O P E R A T O R -SPEC. TEST CASE HEADER 20.1.1

O P E R A T O R -SPEC. TEST CASE HEADER 20.2.1

G S M A -SPEC. TEST CASE HEADER 19.10.1 (not in use now)

G S M A -SPEC. TEST CASE HEADER 19.9.1 (not in use now)

G S M A -SPEC. TEST CASE HEADER 19.8.1 (not in use now)

VPLMN (b) > field in TEST CASE PAGE H23

COMPLETION CERTIFICATE related to the in 6.1 required and selected test cases

O P E R A T O R -SPEC. TEST CASE HEADER 20.4.1

O P E R A T O R -SPEC. TEST CASE HEADER 20.5.1

O P E R A T O R -SPEC. TEST CASE HEADER 20.6.1

Operator Determined Barring for all MS initiated PDP context activatons of MS1(a).

HPLMN (a) > field in TEST CASE PAGE H22

When you have selected the Test Cases you want performed please click here

When you have selected the Test Cases you want performed please click here

IR35 Setup Info & COMPL. CERT. 18(41) IR3550

Page 19: Annex_10_IR35_direct LTE Roaming Test Woth Charging

Name:eMail:

The testing team in VPLMN

Name:eMail:

Signed for HPLMN (a)Date:

Signed for VPLMN (b)Date:

End of Completion Certificate

Email Tester@VPLMN (b) field in TEST CASE PAGE H30

Email Tester@HPLMN (a) field in TEST CASE PAGE H27

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

Email Tester@VPLMN (b) field in TEST CASE PAGE H30

HPLMN TESTER NAME (a) > field in TEST CASE PAGE H25

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

HPLMN TESTER NAME (a) > field in TEST CASE PAGE H25

Email Tester@HPLMN (a) field in TEST CASE PAGE H27

IR35 Setup Info & COMPL. CERT. 19(41) IR3550

Page 20: Annex_10_IR35_direct LTE Roaming Test Woth Charging

IREG GPRS Test Results for Mobile Stations of HPLMN (a) Roaming to VPLMN(b)

A.1.0 (H)PLMN(a) (V)PLMN(b) YES / NO

2G / GSM 2G / GSM 0

3G / UMTS 2G / GSM 0

2G / GSM 3G / UMTS 0

3G / UMTS 3G / UMTS 0

LTE LTE Yes

LTE(PGW) 2G / 3G No

LTE(PGW) 2G / 3G No

A.1.1 Network Operator Information

For GPRS and LTE

(H)PLMN (a)(V)PLMN (b) Date of TestsTesting personnel PLMN(a) Tel/Fax:email PLMN (a):Testing personnel PLMN(b) Tel/Fax: email PLMN (b):

HLR Identity/IdentitiesHLR Manufacturer(s)HLR Software Build Level(s)SGSN Identity/IdentitiesSGSN Manufacturer(s)SGSN Software Build Level(s)HGGSN Identity/IdentitiesHGGSN Manufacturer(s)HGGSN Software Build Level(s)SMS-SC Identity / Identities SMS-SC Manufacturer(s)SMS-SC Software Build Level(s) MMSC Identity / Identities MMSC Manufacturer(s)MMSC Software Build Level(s) FOR LTE

HSS(a) Identity/IdentitiesHSS(a) Manufacturer(s)HSS(a) Software Build Level(s)SGW(b) Identity/IdentitiesSGW(b) Manufacturer(s)SGW(b) Software Build Level(s)MME(b) Identity/IdentitiesMME(b) Manufacturer(s)MME(b) Software Build Level(s)PGW(a) Identity / Identities PGW(a) Manufacturer(s)PGW(a) Software Build Level(s) HPCRF(a) Identity / Identities HPCRF(a) Manufacturer(s)HPCRF(a) Software Build Level(s) VPCRF(b) Identity / Identities VPCRF(b) Manufacturer(s)VPCRF(b) Software Build Level(s) Diameter Edge Agent(a) Identity / Identities Diameter Edge Agent(a) Manufacturer(s)Diameter Edge Agent(a) Software Build Level(s) Diameter Edge Agent(b) Identity / Identities Diameter Edge Agent(b) Manufacturer(s)Diameter Edge Agent(b) Software Build Level(s)

Comments

IMSI MS2/UE2 (a) TestCasePage I34

FOR GPRS

IMSI MS1 (a) / IMSI UE1 (a) IMSI MS1/UE1 (a) TestCasePage I32

HPLMN (a) > field in TEST CASE PAGE H22

VPLMN (b) > field in TEST CASE PAGE H23

MSISDN MS1 (a) / MSISDN UE1 (a) MSISDN MS1/UE1 (a) TestCasePage I31

MSISDN MS2/UE2 (a) TestCasePage I33

All numbers below, will be used for testing purpose s and could be over ride with different values with in a later test, at each time during the test, if i t is required.

IMSI MS2 (a) / IMSI UE2 (a)MSISDN MS2 (a) / MSISDN UE2 (a)

HPLMN TESTER NAME (a) > field in TEST CASE PAGE H25

Email Tester@HPLMN (a) field in TEST CASE PAGE H27

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

Roaming Scenario to be Tested

Email Tester@VPLMN (b) field in TEST CASE PAGE H30

Page 21: Annex_10_IR35_direct LTE Roaming Test Woth Charging

A.1.2 Basic Test Results

The numbering of the test result sections within this appendix is identical to the associated Test case from section 2 of the main document.

A.2.1 GPRS-Attachment

A 2.1.1 GPRS-Attach of MS1(a) in VPLMN(b) (GPRS Attach only)

a) MSC/VLR Record contents:MSISDN MS1 (a)IMSI MS1 (a)SGSN-NumberOthersHLR E164 Addressb) SGSN Record contentsMSISDN MS1 (a)IMSI MS1 (a)MM-StateSGSN-AddressComments

Testcase Result

Signature of Tester Date

A 2.2 Services (Intranet-/ISP-Access, WAP, MMS) / PDP-Con text Activation

A.2.2.1

Application to be testedAPN keyed into the MS or Terminal/ Net Id:1st URL (Intranet)2nd URL (Internet)3rd URL (Internet)Web SettingsLoginPasswordPrimary IP Addresses of Internet DNSSecondary IP Addresses of Internet DNSPlease make sure that the PDP context is activated for at least 5 mins!

The tunnel shall be opened and the application work successfully.

MSISDN of originating MS (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedTime of PDP-context activation [hh:mm:ss] 1HTTP-browsing (based on URLs) successful? [Yes/No]Time of PDP-context deactivation [hh:mm:ss] 1

Overall duration of context [mm:ss] 0:00:00

Total Data Sent during context (from MS) [bytes]Total Data Received during context (from MS) [bytes]Comments

Testcase Result

Signature of Tester Date

A.2.2.2

Application to be testedAPN keyed into the MS or Terminal/ Net Id:WAP SettingsStartpageLoginPasswordPrimary IP address WAP GWPrimary PortThe tunnel shall be opened and the application work successfully.

MSISDN of originating MS (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedTime of PDP-context activation [hh:mm:ss] 1WAP-browsing (based on URLs) successful? [Yes/No]Time of PDP-context deactivation [hh:mm:ss] 1

Overall duration of context [mm:ss] 0:00:00

Total Data Sent during context (from MS) [bytes]Total Data Received during context (from MS) [bytes]Comments

Testcase Result

Signature of Tester Date

A.2.2.3 MMS with MS1(a), MS2(a) in VPLMN(b) using home GGSN and MMSC

Application to be testedAPN keyed into the MS or Terminal/ Net Id:MMS SettingsIP address of HPLMN MMSCPrimary IP address WAP GWLoginPasswordAuthenticationSecurityDelivery report

Send MO/MT Multimedia message according to MMS Conformance Document (max. 30 kB) including pictureimage/audiovoice/text

WAPAPN Test Case Page I159

APN Test Case Page I191

[PASS / FAIL / NOT PERFORMED]

MMS

MS1(a) sends the message without error messages and MS2(a) receives the notification and fetches the message correctly. If case delivery report is used, the delivery report should be successfully received

expected result

expected result

[PASS / FAIL / NOT PERFORMED]

IMSI MS1/UE1 (a) TestCasePage I32

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

MS type of MS1 (a) Test Case Page I139

MSISDN MS1/UE1 (a) TestCasePage I31

MS type of MS1 (a) Test Case Page I139

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

MSISDN MS1/UE1 (a) TestCasePage I31

action

[PASS / FAIL / NOT PERFORMED]

HTTP (web) browsing

IMSI MS1/UE1 (a) TestCasePage I32

condition

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32

expected result

condition

WAP access of MS1(a) in VPLMN(b) using home GGSN (u ser provides Network-ID and no Operator-ID and is not allowed to use visited GGSN), WAP-Browsi ng

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

pre-condition

Set terminal to fetch message automatically also when roaming

action

action

APN Test Case Page I124

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32

Intranet-/ISP-Access of MS1(a) in VPLMN(b) using ho me GGSN (user provides Network-ID and no Operator-ID and is not allowed to use visited GG SN), HTTP-WEB-Browsing

click Help forTime Macro

click Help forTime Macro

Page 22: Annex_10_IR35_direct LTE Roaming Test Woth Charging

MSISDN of originating MS (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedMSISDN of terminating MS (i.e.MS2(a))IMSI (i.e.MS2(a))MS type & software usedTime of transmitting to MMSC [hh:mm:ss] 1Time of notification receipt of MMS at MS2(a) [hh:mm:ss] 1Time of message receipt of MMS at MS2(a) [hh:mm:ss] 1Amount of data sent MS (i.e.MS1(a)) [bytes]Amount of data received MS (i.e.MS1(a)) [bytes]Size of message sent/received MS (i.e.MS2(a)) [bytes]Was message correctly received? [Yes/No]Delivery report received Comments

Testcase Result

Signature of Tester Date

S4-SGSNGp-SGSN to PGW

A.2.2.4

Application to be testedAPN keyed into the UE or Terminal/ Net Id:1st URL (Intranet)2nd URL (Internet)3rd URL (Internet)Web SettingsLoginPasswordPrimary IP Addresses of Internet DNSSecondary IP Addresses of Internet DNSPlease make sure that the PDP context is activated for at least 5 mins!

The tunnel shall be opened and the application work successfully.

MSISDN of originating UE (i.e.UE1(a))IMSI (i.e.UE1(a))UE type & software usedTime of PDP-context activation [hh:mm:ss] 1HTTP-browsing (based on URLs) successful? [Yes/No]Time of PDP-context deactivation [hh:mm:ss] 1

Overall duration of context [mm:ss] 0:00:00

Total Data Sent during context (from UE) [bytes]Total Data Received during context (from UE) [bytes]Comments

Testcase Result

Signature of Tester Date

A.2.2.5

Application to be testedAPN keyed into the UE or Terminal/ Net Id:1st URL (Intranet)2nd URL (Internet)3rd URL (Internet)Web SettingsLoginPasswordPrimary IP Addresses of Internet DNSSecondary IP Addresses of Internet DNSPlease make sure that the EPS Bearer is activated for at least 5 mins!

The tunnel shall be opened and the application work successfully.

MSISDN of originating UE (i.e.UE1(a))IMSI (i.e.UE1(a))UE type & software usedTime of EPS Bearer activation [hh:mm:ss] 1HTTP-browsing (based on URLs) successful? [Yes/No]Time of EPS Bearer context deactivation [hh:mm:ss] 1

Overall duration of context [mm:ss] 0:00:00

Total Data Sent during context (from UE) [bytes]Total Data Received during context (from UE) [bytes]Comments

Testcase Result

Signature of Tester Date

[PASS / FAIL / NOT PERFORMED]

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32MS type of MS1 (a) Test Case Page I139

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

Intranet-/ISP-Access of UE1(a) in VPLMN(b) using vi sited SGW and home PGW over S8-interface (user prov ides Network-ID and no Operator-ID and is not allowed t o use visited GGSN), HTTP-WEB-Browsing

action

HTTP (web) browsingAPN Test Case Page I124

condition

expected result

IMSI MS1/UE1 (a) TestCasePage I32MS type of MS1 (a) Test Case Page I139

[PASS / FAIL / NOT PERFORMED]

condition

expected result

MSISDN MS1/UE1 (a) TestCasePage I31

Intranet-/ISP-Access of UE1(a) in VPLMN(b) using ho me PGW over Gp-interface (user provides Network-ID and no Operator-ID and is not allowed to use visited GG SN), HTTP-WEB-Browsing

action

HTTP (web) browsingAPN Test Case Page I124

MSISDN MS2/UE2 (a) TestCasePage I33IMSI MS2/UE2 (a) TestCasePage I34

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32MS type of MS1 (a) Test Case Page I139

expected result

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

[PASS / FAIL / NOT PERFORMED]

[Pass/Fail/Not applicable]

click Help forTime Macro

click Help forTime Macro

click Help forTime Macro

Page 23: Annex_10_IR35_direct LTE Roaming Test Woth Charging

A.2.3 MAP-Tests (SMS, Location Cancellation, GPRS-Barring )

A.2.3.1 Mobile originated and terminated SMS (MS1(a) GPRS-A ttached only / MS2(a) GPRS-Attached only)

Application to be tested E164 address of HPLMN SMS–Service CentreThe SMS shall be delivered to MS2(a).

MSISDN of originating MS (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedMSISDN of terminating MS (i.e.MS2(a))IMSI (i.e.MS2(a))MS type & software usedTime of transmitting to SMS-Service Centre [hh:mm:ss] 1Time of receipt of SMS at MS2(a) [hh:mm:ss] 1Was message correctly received? [Yes/No]Comments

Testcase Result

Signature of Tester Date

A.2.3.2 Location cancellation for MS1(a)-GPRS Subscription held in VPLMN(b)

action Application to be tested

deleting HLR subscription and erasing SGSN record

MSISDN of MS (i.e.MS1(a))IMSI (i.e.MS1(a))SGSN Record erased? [Yes/No]GGSN(a) or GGSN (b) record erased? [Yes/No]PDP context deactivation successful? [Yes/No]

[Secs]Comments

Testcase Result

Signature of Tester Date

A.2.3.3 Operator Determined Barring for all MS initiated PD P context activatons of MS1(a).

action Application to be tested

barring tags in SGSN record and unsuccussful PDP context activation

MSISDN of MS (i.e.MS1(a))IMSI (i.e.MS1(a))

[Yes/No]SGSN record contains barring tags [Yes/No]

[Yes/No]Comments

Testcase Result

Signature of Tester Date

MSISDN MS2/UE2 (a) TestCasePage I33MS type of MS1 (a) Test Case Page I139

SMS

IMSI MS1/UE1 (a) TestCasePage I32

[PASS / FAIL / NOT PERFORMED]

MSISDN MS1/UE1 (a) TestCasePage I31

Operator Determined Barring

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

location cancellation

expected result

MSISDN MS1/UE1 (a) TestCasePage I31

pre-condition

IMSI MS1/UE1 (a) TestCasePage I32

IMSI MS2/UE2 (a) TestCasePage I34

IMSI MS1/UE1 (a) TestCasePage I32

activated PDP context

pre-condition

activated PDP context

expected result

[PASS / FAIL / NOT PERFORMED]

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

Time delay between HLR deleting subscription and SGSN erasing record

Perform PDP-context activation from MS1(a). Is it successful?

Operator performed barring towards PDP-context activation from HLR

MSISDN MS1/UE1 (a) TestCasePage I31

action

expected result

[PASS / FAIL / NOT PERFORMED]

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

click Help forTime Macro

Page 24: Annex_10_IR35_direct LTE Roaming Test Woth Charging

19.1

19.1.1 LTE Attach and Detach

Application to be testedAPN keyed into the MS or Terminal/ Net Id:1st URL (Intranet)2nd URL (Internet)3rd URL (Internet)Web SettingsLoginPasswordPrimary IP Addresses of Internet DNSSecondary IP Addresses of Internet DNS

MSISDN (i.e.UE1(a))IMSI (i.e.UE1(a))UE type & software usedTime of PDN connectivity activation (= Time of Attach) [hh:mm:ss] 1HTTP-browsing (based on URLs) successful? [Yes/No]Time of PDN connectivity deactivation (= Time of Detach) [hh:mm:ss] 1Overall duration of context [mm:ss] 0:00:00

Total Data Sent during context (from UE) [bytes]Total Data Received during context (from UE) [bytes]

Comments

Testcase Result

Signature of Tester Date

19.2.1 LTE Cancel Location

action Application to be tested

MSISDN (i.e.UE1(a))IMSI (i.e.UE1(a))MME(b) Record erased? [Yes/No]SGW(b) record erased? [Yes/No]PGW(a) record erased? [Yes/No]vPCRF(b) record erased? [Yes/No]hPCRF(a) record erased? [Yes/No]PDN connectivity deactivation successful? [Yes/No]

[Secs]Comments

Testcase Result

Signature of Tester Date

pre-condition

UE1(a) is in EMM-REGISTERED and ECM-CONNECTED stateEMM contexts are established in the UE1(a) and MME(b).PDN Connectivity towards to the default APN is established.LTE-detach for UE1(a) is completed.

expected result

UE1(a) contains USIM of HPLMN(a).No valid EMM contexts are established for UE1(a).HSS(a) record contains basic service information including EPS subscription data.No valid PDN connectivity are established in the UE1(a).One EPS bearer context subscription record exists in HSS(a) where APN(S) = APN(R). VPLMN not allowed for selected EPS context subscription records.

condition Please make sure that the PDN connection is activated for at least 5 mins!

action

LTE Attach and DetachAPN Test Case Page I314

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32

condition

LTE Cancel Location

[PASS / FAIL / NOT PERFORMED]

pre-condition

MME(b) in VPLMN(b) contains EPS-subscription information of UE1(a) and PDN connectivity for UE1(a) is activated.

UE type of MS1(a) Test Case Page I338

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

expected result

If GTP is used for S8, 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.If PMIP is used for S8, 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.

Time delay between HSS deleting subscription and EPC entities erasing record

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32

[PASS / FAIL / NOT PERFORMED]

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

click Help forTime Macro

click Help forTime Macro

Page 25: Annex_10_IR35_direct LTE Roaming Test Woth Charging

19.3.1 LTE Operator Determined Barring

action Application to be tested

MSISDN (i.e.UE1(a))IMSI (i.e.UE1(a))

[Yes/No]MME record contains barring tags [Yes/No]

[Yes/No]Comments

Testcase Result

Signature of Tester Date

19.4.1 G S M A -SPEC. TEST CASE HEADER 19.4.1 (not in use now)

Application to be testedAPN keyed into the MS or Terminal/ Net Id:xxx Settings

MSISDN (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedMSISDN (i.e.MS2(a))IMSI (i.e.MS2(a))MS type & software used

Comments

Testcase Result

Signature of Tester Date

LTE Operator Determined Barring

IMSI MS1/UE1 (a) TestCasePage I32

condition

expected result

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

action

MSISDN MS1/UE1 (a) TestCasePage I31

Perform LTE Attach from UE1(a). Is it rejectedl as expected?

pre-condition

UE1(a) is attached to VPLMN(b) and MME(b) in VPLMN(b) contains subscription information of UE1(a).

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

[PASS / FAIL / NOT PERFORMED]

IMSI MS1/UE1 (a) TestCasePage I32Operator performed barring from HSS

condition

MSISDN MS1/UE1 (a) TestCasePage I31

pre-condition

[PASS / FAIL / NOT PERFORMED]

MS type of MS1 (a) Test Case Page I139MSISDN MS2/UE2 (a) TestCasePage I33IMSI MS2/UE2 (a) TestCasePage I34

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

click Help forTime Macro

Page 26: Annex_10_IR35_direct LTE Roaming Test Woth Charging

19.5.1 G S M A -SPEC. TEST CASE HEADER 19.5.1 (not in use now)

Application to be testedAPN keyed into the MS or Terminal/ Net Id:xxx Settings

MSISDN (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedMSISDN (i.e.MS2(a))IMSI (i.e.MS2(a))MS type & software used

Comments

Testcase Result

Signature of Tester Date

19.6.1 G S M A -SPEC. TEST CASE HEADER 19.6.1 (not in use now)

Application to be testedAPN keyed into the MS or Terminal/ Net Id:xxx Settings

MSISDN (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedMSISDN (i.e.MS2(a))IMSI (i.e.MS2(a))MS type & software used

Comments

Testcase Result

Signature of Tester Date

[PASS / FAIL / NOT PERFORMED]

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

IMSI MS2/UE2 (a) TestCasePage I34

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

action

[PASS / FAIL / NOT PERFORMED]

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32

IMSI MS2/UE2 (a) TestCasePage I34

action

pre-condition

condition

expected result

MS type of MS1 (a) Test Case Page I139MSISDN MS2/UE2 (a) TestCasePage I33

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32MS type of MS1 (a) Test Case Page I139MSISDN MS2/UE2 (a) TestCasePage I33

pre-condition

condition

expected result

Page 27: Annex_10_IR35_direct LTE Roaming Test Woth Charging

19.7.1 G S M A -SPEC. TEST CASE HEADER 19.7.1 (not in use now)

Application to be testedAPN keyed into the MS or Terminal/ Net Id:xxx Settings

MSISDN (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedMSISDN (i.e.MS2(a))IMSI (i.e.MS2(a))MS type & software used

Comments

Testcase Result

Signature of Tester Date

19.8.1 G S M A -SPEC. TEST CASE HEADER 19.8.1 (not in use now)

Application to be testedAPN keyed into the MS or Terminal/ Net Id:xxx Settings

MSISDN (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedMSISDN (i.e.MS2(a))IMSI (i.e.MS2(a))MS type & software used

Comments

Testcase Result

Signature of Tester Date

MSISDN MS1/UE1 (a) TestCasePage I31

condition

pre-condition

action

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

action

expected result

[PASS / FAIL / NOT PERFORMED]

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32MS type of MS1 (a) Test Case Page I139MSISDN MS2/UE2 (a) TestCasePage I33IMSI MS2/UE2 (a) TestCasePage I34

[PASS / FAIL / NOT PERFORMED]

MSISDN MS2/UE2 (a) TestCasePage I33IMSI MS2/UE2 (a) TestCasePage I34

pre-condition

IMSI MS1/UE1 (a) TestCasePage I32MS type of MS1 (a) Test Case Page I139

condition

expected result

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

Page 28: Annex_10_IR35_direct LTE Roaming Test Woth Charging

19.9.1 G S M A -SPEC. TEST CASE HEADER 19.9.1 (not in use now)

Application to be testedAPN keyed into the MS or Terminal/ Net Id:xxx Settings

MSISDN (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedMSISDN (i.e.MS2(a))IMSI (i.e.MS2(a))MS type & software used

Comments

Testcase Result

Signature of Tester Date

19.10.1 G S M A -SPEC. TEST CASE HEADER 19.10.1 (not in us e now)

Application to be testedAPN keyed into the MS or Terminal/ Net Id:xxx Settings

MSISDN (i.e.MS1(a))IMSI (i.e.MS1(a))MS type & software usedMSISDN (i.e.MS2(a))IMSI (i.e.MS2(a))MS type & software used

Comments

Testcase Result

Signature of Tester Date

[PASS / FAIL / NOT PERFORMED]

MSISDN MS2/UE2 (a) TestCasePage I33IMSI MS2/UE2 (a) TestCasePage I34

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

MS type of MS1 (a) Test Case Page I139

action

expected result

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32

pre-condition

condition

MSISDN MS2/UE2 (a) TestCasePage I33IMSI MS2/UE2 (a) TestCasePage I34

[PASS / FAIL / NOT PERFORMED]

IMSI MS1/UE1 (a) TestCasePage I32MS type of MS1 (a) Test Case Page I139

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

MSISDN MS1/UE1 (a) TestCasePage I31

condition

expected result

action

pre-condition

Page 29: Annex_10_IR35_direct LTE Roaming Test Woth Charging

20.1 O P E R A T O R- SPECIFIC TESTS

20.1.1 O P E R A T O R -SPEC. TEST CASE HEADER 20.1.1Action

Expected Result

Test Case Comments

Testcase Result

Signature of Tester Date

Paste Test Case Below

[PASS / FAIL / NOT PERFORMED]

VPLMN TESTER NAME (b) > field in TEST CASE PAGE H28

Detail Text 3 (Result) 20.1.1

Detail Text 2 / Action- field in General TC 20.1.1

Page 30: Annex_10_IR35_direct LTE Roaming Test Woth Charging

Return to IR35 Test Case Page Click to select this Operator Specific Test

Application to be testedAPN keyed into the MS or Terminal/ Net Id:xxx Settings

MSISDN (i.e.MS1(a))IMSI (i.e.MS1(a))

MS type & software usedMSISDN (i.e.MS2(a))IMSI (i.e.MS2(a))MS type & software used

MS type of MS1 (a) Test Case Page I139

condition

expected result

MSISDN MS2/UE2 (a) TestCasePage I33IMSI MS2/UE2 (a) TestCasePage I34

pre-condition

action

MSISDN MS1/UE1 (a) TestCasePage I31IMSI MS1/UE1 (a) TestCasePage I32

RestoreTestCase

Page 31: Annex_10_IR35_direct LTE Roaming Test Woth Charging

-- IR.35 - please refer to GSM PRD TD.47

IREG

Test Ref

Event

Number

TAP CDR Type Service Type MSISDN Other

(IMSI!)

Startime

of CDR

Chargeble

DURATION

Calling/Called

Party

APN Status

2.1.1 1 None Expected MSISDN MS1/UE1 (a) TestCasePage I31 IMSI MS1/UE1 (a) TestCasePage I32 none none none none N/A2.2.1 1 GPRS GPRS MSISDN MS1/UE1 (a) TestCasePage I31 IMSI MS1/UE1 (a) TestCasePage I32 0:00:00 0:00:00 none APN Test Case Page I124 N/A

2.2.2 1 GPRS GPRS MSISDN MS1/UE1 (a) TestCasePage I31 IMSI MS1/UE1 (a) TestCasePage I32 0:00:00 0:00:00 none APN Test Case Page I159 N/A

2.2.3 1 GPRS GPRS MSISDN MS1/UE1 (a) TestCasePage I31 IMSI MS1/UE1 (a) TestCasePage I32 0:00:00 none none APN Test Case Page I191 N/A2.2.3 2 GPRS GPRS MSISDN MS2/UE2 (a) TestCasePage I33 IMSI MS2/UE2 (a) TestCasePage I34 0:00:00 none none none N/A

2.2.4 1 GPRS GPRS MSISDN MS1/UE1 (a) TestCasePage I31 IMSI MS1/UE1 (a) TestCasePage I32 0:00:00 none none APN Test Case Page I124 N/A

2.2.5 1 GPRS GPRS MSISDN MS1/UE1 (a) TestCasePage I31 IMSI MS1/UE1 (a) TestCasePage I32 0:00:00 none none APN Test Case Page I124 N/A

2.3.1 1 MOC SMS-MO MSISDN MS1/UE1 (a) TestCasePage I31 IMSI MS1/UE1 (a) TestCasePage I32 0:00:00 none none none N/A2.3.1 2 MTC SMS-MT MSISDN MS2/UE2 (a) TestCasePage I33 IMSI MS2/UE2 (a) TestCasePage I34 0:00:00 none none none N/A

2.3.2 1 None Expected MSISDN MS1/UE1 (a) TestCasePage I31 IMSI MS1/UE1 (a) TestCasePage I32 none none none none N/A

2.3.3 1 None Expected MSISDN MS1/UE1 (a) TestCasePage I31 IMSI MS1/UE1 (a) TestCasePage I32 none none none none N/A

GSMA SPECIFIC Test Cases19.1.1 1 LTE LTE MSISDN MS1/UE1 (a) TestCasePage I31 IMSI MS1/UE1 (a) TestCasePage I32 0:00:00 0:00:00 none APN Test Case Page I314 N/A

19.2.1 1 None Expected N/A

19.3.1 1 None Expected N/A

Operator Specific Test Cases20.1.1 N/A

20.2.1 N/A

20.3.1 N/A

20.4.1 N/A

20.5.1 N/A

20.6.1 N/A

20.7.1 N/A

20.8.1 N/A

20.9.1 N/A

20.10.1 N/A

Subscriber ID

Page 32: Annex_10_IR35_direct LTE Roaming Test Woth Charging

GSMA Specific HelpA LINE BREAK FOR COMMENTS NEEDS TO BE ENTERED AS "LOWER SHIFT + RETURN" HERE

WARNINGS Do not enter data into any other cells unless you wish to overwrite the formula that is already in the cell.This will be the case, if you are need to chnage the test setup and use a different call party like MSx/ PSTNx.

General use of the spreadsheet Do not delete or insert rows or columns on any of the pages, except the SETUP PAGE.Here it is allowed as an exemption to add lines in section 4. for OPERATOR SPECIFIC HINTS.

Set up any filters on any page, filters are automatically set by the spreadsheet.- the grey numbers on the right side of the test cases are visible "counting steps" to make the time macro able to jump to the correct next input field. Don't change it without any reason.

- all areas which are indicated as light green belong to GSMA responsibility and are not allowed to be changed!The yellow indicated test cases are free for modification by all OPERATORs (see GENERAL and TEST CASES)."

HINTS - there is a TIME MACRO inserted, which allows you to insert the time into the testing document (based on your PC time).This can be used with the key combination "Ctrl + Low-Shift + A". Next to all test cases you will find a "red circle button" in the TESTING PAGE to remind you.

IMPORTANT: Your PC might not allow to use macros! In this case you have to follow the instruction from your PC office programm and adjust the security options in EXCEL to the expected value (e.g. from high to medium) and save the file again. After the re-opening, you will be asked for the macro activation, please confirm it.

For TADIG it's not relevant, that your time stamp is 1:1 to the network element. In case of a clock offset on your PC the mismatch is always the same, so TADIG can suggest the right value in the switch.Only if your PC time is far away from real time, you should notify this in your sheet on TEST CASES (e.g. comments) and TADIG PAGE (extra note).

All fields which require such a format are connected within the testing sequence (see grey digits).Please make sure if you are using the time macro that you PC clock is working in the 24h format. Check this under control panel/region settings ->clock/customized choose capitel letter "H"

- DROP DOWN BOXES, if you want to use the keyboard instead of the mouse, enter the field and try "ALT + arrow down"

- CHANGE OF LINK REFERENCES FOR USED MSx (a) / (b)- If you need to change such link reference, it might happen randomly,

Page 33: Annex_10_IR35_direct LTE Roaming Test Woth Charging

"UNPROTECT" PAGES - (there is no real protection!)If for some reason you need to see the EXCEL lines as A-Z and 1-n, please use - depending on your EXCEL version (language) - the sixth menu option (EXTRAS) from the left in the menu bar, then choose "options" and then "view". Here you can set a flag to make the headers visible called "rows & columns".

DATA ENTRY (e.g. IREG RESULTS) Only enter data if input is requested in cells which are coloured light blue(e.g. SETUP SHEET, TEST CASES)

IRxx GENERALon this page you will see all test case descriptions which you can access from the top immediately via the blue buttons.The important feature is the linking of the content of the test case header + general description below the header + action content + expected result content!SETUP PAGEFor the test cases you want to be completed select "Yes" from the dropdown menu. I m p o r t a n t - remember to click the red selection button after selecting your Test Cases! This button sets the filters on the TEST and TADIG Pages!

TEST CASE pageOnly enter data into the light blue coloured cells. If these cells are within a test case, it will turn white when you have entered your data. Complete section A1.1 and A1.2 before starting the test cases.Don't change any test case header in here, because they are linked to the IRxx GENERAL page and should reflect only the content from there.

Do not delete any grey numbers on the right side in the TEST CASES PAGE and TEMPLATES PAGE.They are used as "jump marks" to the next planned data entry field.

In case of the TEMPLATES PAGE, you might need to adjust them. You can try to change them for testing purposes and see how they work (it is not comlicated). If you want to reset the whole TEMPLATE , use the button for it and it will be restored.

There is a macro inserted, which allows you to insert the time into the testing document (based on your PC time).This can be used with the key combination "Ctrl + Low-Shift + A". You will find next to all test cases a "red circle button" in the TEST CASES PAGE, which reminds you of that.All fields which require such a format are connected within the testing sequence (see grey digits).

Page 34: Annex_10_IR35_direct LTE Roaming Test Woth Charging

TEMPLATE PAGE - OPERATOR TEST CASES (TC)1. If you want to create test cases on your own, please start with writing the description on the GENERAL PAGE (the DETAIL1-5 content cells are linked for the TC-header,"action" and "exp. results" to the TEST CASES PAGE). 2. Next, you need to select the requested 20.x TC plus confirm button!3. After this is done you can specify the TC via PASTE button and chose one of the offered templates to modify it by deleting the unwanted content.4. You might need to modify as well the numbers in grey, if the user should be able to jump from each time macro field into the next.(the first column and grey numbers in it are for the steps in vertical direction and the next column showing the horizontal steps.Try it in the TEMPLATE PAGE and you will see how they work)5. Insert your new TC into the test box area.

Please remember- DO NOT INSERT /DELETE COMPLETE LINES, CHANGE ONLY TEXT CONTENTS !Tipp: You can colour not used areas above & below the new created test

TADIG PAGEAll data (except test cases 19.x and 20.x) are linked to the corresponding field in TEST CASES.If you as OPERATOR want to link your call details from TEST CASES to TADIG, please do it on your own responsibility.See as well the hint for "UNPROTECTED PAGES" no.3 above.

INSTRUCTION PAGEIn OPERATOR SPECIFIC HELP (yellow) you can enter your own comments on how to read your tests. For the GSMA (green) it will be done officially and you shouldn't change any comments.If there is a mistake, please create a change request (see AA34) to GSMA."

Page 35: Annex_10_IR35_direct LTE Roaming Test Woth Charging

Operator Specific Help

Page 36: Annex_10_IR35_direct LTE Roaming Test Woth Charging

CALL DIVERSIONFeature Mode Sequence All calls Activate & register number ** 21 * Number # SEND Deactivate & deregister number ## 21 # SEND Activate to registered number * 21 # SEND Deactivate # 21 # SENDVerify *# 21 # SEND No answer Activate & register number ** 61 * Number # SEND Deactivate & deregister number ## 61 # SEND Activate * 61 * Number # SEND Deactivate # 61 #Verify *# 61 # SEND Unreachable Activate ** 62 * Number # SEND Deactivate ## 62 # SEND Verify *# 62 # SEND Busy Activate ** 67 * Number # SEND Deactivate ## 67 # SEND Verify *# 67 # SEND All types Deactivate ## 002 # SEND All conditional types Deactivate ## 004 # SEND

CALL BARRINGFeature Mode Sequence Barring all outgoing calls Activate * 33 * PIN # SENDDeactivate # 33 * PIN # SENDVerify *# 33 # SEND Barring all outgoing IDD calls Activate * 331 * PIN # SENDDeactivate # 331 * PIN # SENDVerify *# 331 # SEND Barring all outgoing IDD calls when roaming (except to home country) Activate * 332 * PIN # SENDDeactivate # 332 * PIN # SENDVerify *# 332 # SEND Barring all outgoing calls Activate * 333 * PIN # SEND Deactivate # 333 * PIN # SEND Verify *# 333 # SEND Barring all Incoming Calls Activate * 35 * PIN # SENDDeactivate # 35 * PIN # SENDVerify *# 35 # SEND Barring all incoming calls when international roaming Activate * 351 * PIN # SENDDeactivate # 351 * PIN # SENDVerify *# 351 # SEND Barring all calls Activate * 350 * PIN # SEND Deactivate # 350 * PIN # SEND Verify *# 350 # SEND Barring all incoming calls Activate * 353 * PIN # SEND Deactivate # 353 * PIN # SEND

Page 37: Annex_10_IR35_direct LTE Roaming Test Woth Charging

Verify *# 353 # SEND Deactivate all call barring # 330 * PIN # SENDChange call barring code ** 03 * old barring code * new barring code * new barring code # SEND

Page 38: Annex_10_IR35_direct LTE Roaming Test Woth Charging

CALL WAITINGFeature Mode Sequence Call waiting Activate * 43 # SEND Deactivate # 43 # SEND Verify *# 43 # SEND Reject call waiting or end call on hold 0 SENDEnd active call and switch to held or waiting call 1 SEND End a specific call (n = call number) 1n SEND Hold active call and retrieve held or waiting call 2 SEND Hold all active calls and except one (n = call number) 2n SEND Add held call into active call 3 SENDHold active call and place outgoing call Number SEND Alternate between callers SEND End all calls simultaneously except call waiting END

SIM SECURITY CODESFeature Sequence Change SIM Card PIN ** 04 * old PIN * new PIN * new PIN # Change SIM Card PIN 2 ** 042 * old PIN * new PIN *new PIN # Change SIM Card PUK ** 05 * old PUK * new PUK * new PUK # Change SIM Card PUK 2 ** 052 * old PUK * new PUK * new PUK # Display Handset IMEI *# 06 #

CALLER IDFeature Mode Sequence Incoming (CLIP) Activate * 30 # SEND Deactivate # 30 # SEND Verify *# 30 # SENDOutgoing (CLIR) Activate * 31 # SEND Deactivate # 31 # SEND Verify *# 31 # SENDOutgoing per-call block * 31 # Number SEND Outgoing per-call block # 31 # Number SENDOutgoing per-call force-send # 31 # Number SENDOutgoing per-call force-send *# 31 # Number SEND

EMERGENCY

Page 39: Annex_10_IR35_direct LTE Roaming Test Woth Charging

Feature Sequence Emergency Call 112 SEND

Page 40: Annex_10_IR35_direct LTE Roaming Test Woth Charging

Yes/No Dropdown Call Quality Dropdown

Yes ExcellentNo Good

FairTest Completed Dropdown Poor

Bad

PASSFAILNot Performed

Count6

Count4

Test Case Selection Dropdown Test Case Paste Value6

Y E S D940No 20.6

Page 41: Annex_10_IR35_direct LTE Roaming Test Woth Charging

Today MS DropdownMS1(a)

2012/12/05 MS2(a)MS3(a)

Paging Dropdown

A(Paging)B(Pre-Paging)

Test Case1 D729 20.12 D771 20.23 D813 20.34 D856 20.45 D898 20.56 D940 20.67 D982 20.78 D1024 20.89 D1066 20.9

10 D1108 20.10


Recommended