Gprs

GSM Association Permanent Reference Document: IR 35

Unrestricted - Industry

IR35331 Version 3.3.1 Page 1 of 93

PRD IR.35

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

Version 3.3.1 Date 11 February 2003

GSM Association Classifications

Non-Binding

Core

Security Classification Category: Unrestricted – Industry X

Information Category Roaming – Technical

Unrestricted This document is subject to copyright protection. The GSM MoU Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice. Access to and distribution of this document by the Association is made pursuant to the Regulations of the Association.

© Copyright of the GSM MoU Association 2003




Document History

Revision Date Brief Description Version Date Brief Description 0.0.1 22.06.1999 IREG Doc GPRS 23/99 with changes according 4th Meeting of IREG

GPRS for Ad-Hoc pre-discussion 0.0.2 06.08.1999 First draft of document for IREG GPRS group discussion (5th

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

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

GPRS 0.0.5 01.02.2000 Modifications from comments send by email

Introduction of “Operator Control of Service” test cases 0.0.6 03.03.2000 IREG Doc IR35 with changes according 7th Meeting of IREG GPRS

Charging-Information Operator Control of Service Test cases

0.0.7 24.02.2000 A new test case added in Chapter 2.2.3 0.0.8 01.03.2000 Charging information added, ODB test cases modified. 0.0.9 03.03.2000 Charging impacts, chapter 2.2, item no. 6 updated.

Final modifications before IREG#38 1.0.0 14.03.2000 Modified for IREG 38 approval 2.0.0 15.03.2000 Approved by IREG 38 subject to addition of Appendix A and B 2.1.0 29.03.2000 Appendix A and B completed 3.0.0 28.04.2000 Approved at Plenary 43. PL Doc 36/00 Rev 1 3.0.1 23.06.2000 IREG Doc GPRS 35/00 with changes according 9th Meeting of IREG

GPRS 3.0.2 30.08.2000 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.3 05.09.2000 IREG Doc GPRS 57/00 (CR) with changes according to 11th Meeting of IREG GPRS

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

3.0.5 05.01.2001 Modifications from comments according 1th IREG Packet-WP-GPRS (GSM NA IREG WG Suggested changes to IR35

3.0.6 01.03.2001 Separation of optional test cases in a separate Annex 3.0.7 21.08.2001 Modifications from comments according 3rd IREG-Packet-Meeting

(Creation of S-CDRs) 3.1.0 Modified document for presentation on the IREG-#41-Meeting 3.1.1 17.10.2001 Approved and revised document after IREG#41 3.1.2 18.03.2001 Modifications from comments /experiences made by Vodafone-D2:

1) Restructuring of test results; table-format 2) Removal of test-cases; chapter B1.2.7 and B1.2.8 (See also CR-003) Changes according 8th Meeting of IREG Packet

3.2.0 20.03.02 Approved and revised document after IREG#42 3.3.0 20.08.2002 CR-004_Hutchison-3G, IREG-Doc 068_02

Approved and revised document after IREG#43 3.3.1 11.02.2003 CR NTT-DoCoMo, IREG-Doc 092/02, Additional requirement of

operator control of service.




CR NTT-DoCoMo, IREG-Doc 093/02, The prohibition of accessing Internet within VPLMN, additional optional test case. CR NTT-DoCoMo, IREG-Doc 094/02, Clarify equipment requirements. CR-Sonera, IREG-Doc 102/02, two new optional MMS test cases

Changes Since Last Version




TABLE OF CONTENTS

1.1 Scope of document......................................................................................................................................................................................... 7

1.2 Abbreviations ................................................................................................................................................................................................. 7

1.3 Objective of Tests .......................................................................................................................................................................................... 9

1.4 Strategy for Testing ..................................................................................................................................................................................... 9

1.5 Prerequisites ................................................................................................................................................................................................. 9

2 TEST CASES.............................................................................................................................................. 12

2.1 Mobility Management.................................................................................................................................................................................13 2.1.1 GPRS-Attach of MS1(a) in VPLMN(b) (GPRS Attach only).......................................................................................................13

2.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b).....................................................................................................................14

2.2.1 Intranet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID but no Operator-ID and is not

allowed to use visited GGSN)...................................................................................................................................................................................15 2.2.2 PDP Context Modification Procedure triggered by changing of QoS Profile subscribed in HLR(a) .................................16 2.2.3 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID and no Operator-ID)......... 18

2.2.4 ISP/Internet 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) ............................................................................................................................................................................20 2.2.5 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides no Network-ID and no Operator-ID;

APN chosen from a single HLR PDP-context; no wild card using) .................................................................................................................22

2.3 SMS Test Cases ..........................................................................................................................................................................................24 2.3.1 Mobile originated and terminated SMS (MS1(a) GPRS-Attached only / MS2(a) GPRS-Attached only)............................24

2.4 Operator Control of Service......................................................................................................................................................................25 2.4.1 Location cancellation for MS1(a)-GPRS Subscription held in VPLMN(b) ..............................................................................25

2.4.2 Operator Determined Barring for all MS initiated PDP context activatons of MS 1(a)..........................................................26

3 EQUIPMENT REQUIREMENTS ............................................................................................................. 26

3.1 User Equipment............................................................................................................................................................................................26

3.2 Test Equipment ............................................................................................................................................................................................27

4 PRE-TESTING DATA EXCHANGE........................................................................................................ 27

4.1 Testing Contract Information...................................................................................................................................................................27

4.2 PLMN/IP-addressing, numbering and routing data .............................................................................................................................27

4.3 SIM associated data supplied by PLMN(a)..............................................................................................................................................27

4.4 GPRS Inter-PLMN connection parameters ...........................................................................................................................................28

4.5 IP-server information.................................................................................................................................................................................28

4.6 Required extension to MOU-IREG PRDs................................................................................................................................................28




APPENDIX A ..................................................................................................................................................... 29

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

A.1.1 Roaming Scenario to be Tested...........................................................................................................................................................29

A.1.2 Network Operator Information...........................................................................................................................................................30

A 2.1 Basic Test Results ................................................................................................................................................................................30 A 2.1.1 GPRS-Attach of MS1(a) in VPLMN(b) (GPRS Attach only).......................................................................................................31

A 2.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b) ................................................................................................................31

A 2.2.1 Intranet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID but no Operator-ID and is not

allowed to use visited GGSN)...................................................................................................................................................................................31 A 2.2.2 PDP Context Modification Procedure triggered by changing of QoS Profile subscribed in HLR(a) .................................32 A 2.2.3 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID and no Operator-ID)......... 33

A 2.2.4 ISP/Internet 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) ............................................................................................................................................................................34 A 2.2.5 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides no Network-ID and no Operator-ID;

APN chosen from a single HLR PDP-context; no wild card using).................................................................................................................35

A 2.3 SMS Test Cases......................................................................................................................................................................................36 A 2.3.1 Mobile originated and terminated SMS (MS1(a) GPRS-Attached only / MS2(a) GPRS-Attached only)............................36

A 2.4 Operator Control of Service.................................................................................................................................................................36 A 2.4.1 Location cancellation for MS1(a)-Subscription held in VPLMN(b) ..........................................................................................36

A 2.4.2 Operator Determined Barring for all MS initiated PDP context activations of MS 1(a)............................................................37

APPENDIX B (OPTIONAL TESTS)............................................................................................................... 38

B 1 TEST CASES .......................................................................................................................................... 39

B 1.1 Mobility Management ............................................................................................................................................................................39 B 1.1.1 Inter SGSN routing area update of MS1(a) in VPLMN(b) – Intra-System Change – GSM Radio Acces only.........................39

B 1.1.2 Inter SGSN routing area update of MS1(a) in VPLMN(b) – Intra-System Change – UMTS Radio Acces only.......................40

B 1.1.3 UMTS to GSM Inter SGSN routing area update of MS1(a) in VPLMN(b) – Inter-System Change............................................41

B 1.1.4 GSM to UMTS Inter SGSN routing area update of MS1(a) in VPLMN(b) – Inter-System Change............................................43

B 1.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b) ................................................................................................................45

B 1.2.1 Intranet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID but no Operator-ID)......................45

B 1.2.2 Intranet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID but no Operator-ID; Unsuccessful

first DNS interrogation with APN+VPLMN-Operator-ID)...............................................................................................................................47 B 1.2.3 Default Intranet/ISP access of MS1(a) in VPLMN(b) using visited GGSN (user provides no Network-ID and no Operator-

ID ; default APN chosen by SGSN(b); Wild Card using)...................................................................................................................................49 B 1.2.4 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID and HPLMN Operator-ID) ...51

B 1.2.5 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides no Network-ID and no Operator-ID; APN

chosen from a single HLR PDP-context; no wild card using)...........................................................................................................................53 B 1.2.6 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides no Network-ID and no Operator-ID; APN

chosen from a single HLR PDP-context; no wild card using; unsuccessful first interrogation with APN+VPLMN-Operator-ID)...55 B 1.2.7 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID and Operator-ID, VPLM not

allowed) ........................................................................................................................................................................................................................57




B 1.3 3G to 3G Roaming only – GPRS PDP Context Activation by MS1(a) in VPLMN(b) using Home GGSN – Different QoS

Profiles are applied.......................................................................................................................................................................................................58 B 1.3.1 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Background Traffic Class....58

B 1.3.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Interactive Traffic Class and

Different Traffic Handling Priorities ....................................................................................................................................................................60 B 1.3.3 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Streaming Traffic Class .......67

B 1.3.4 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Conversational Traffic Class69

B 1.4 MMS Test Cases.....................................................................................................................................................................................71 B 1.4.1 MMS Roaming: Mobile originated and terminated MMS (MS1(a) / MS2(a)) .................................................................................71

B 1.4.2 MMS Interworking: Mobile originated and terminated MMS (MS1(b) / MS2(a)) .........................................................................71

B.2 BASIC TEST RESULTS........................................................................................................................ 72

B 2.1 Mobility Management ............................................................................................................................................................................72 B 2.1.1 Inter SGSN routing area update of MS1(a) in VPLMN(b) – Intra-System Change – GSM Radio Acces only........................72

B 2.1.2 Inter SGSN routing area update of MS1(a) in VPLMN(b) – Intra-System Change – UMTS Radio Acces only.......................73

B 2.1.3 UMTS to GSM Inter SGSN routing area update of MS1(a) in VPLMN(b) – Inter-System Change............................................73

B 2.1.4 GSM to UMTS Inter SGSN routing area update of MS1(a) in VPLMN(b) – Inter-System Change............................................74

B 2.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b) ................................................................................................................74

B 2.2.1 Intranet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID but no Operator-ID)......................74

B 2.2.2 Intranet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID but no Operator-ID; Unsuccessful

first DNS interrogation with APN+VPLMN-Operator-ID)...............................................................................................................................76 B 2.2.3 Default Intranet/ISP access of MS1(a) in VPLMN(b) using visited GGSN (user provides no Network-ID and no Operator-

ID ; default APN chosen by SGSN(b); Wild Card using)...................................................................................................................................77 B 2.2.4 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID and HPLMN Operator-ID) ..78

B 2.2.5 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides no Network-ID and no Operator-ID; APN

chosen from a single HLR PDP-context; no wild card using)...........................................................................................................................79 B 2.2.6 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides no Network-ID and no Operator-ID; APN

chosen from a single HLR PDP-context; no wild card using; unsuccessful first interrogation with APN+VPLMN-Operator-ID)...80 B.2.2.7 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID and Operator-ID, VPLM not

allowed) ........................................................................................................................................................................................................................81

B 2.3 3G to 3G Roaming only – GPRS PDP Context Activation by MS1(a) in VPLMN(b) with different QoS Profiles applied....... 81

B 2.3.1 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Background Traffic Class....82

B 2.3.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Interactive Traffic Class.......83

B 2.3.3 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Streaming Traffic Class .......86

B 2.3.4 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Conversational Traffic Class87

B 2.4 MMS Test Cases.....................................................................................................................................................................................88 B 2.4.1 MMS Roaming: Mobile originated and terminated MMS (MS1(a) / MS2(a)) .................................................................................88

B 2.4.2 MMS Interworking: Mobile originated and terminated MMS (MS1(b) / MS2(a)) .........................................................................89

APPENDIX C ..................................................................................................................................................... 91




1. Introduction

1.1 Scope of document

This document is the specification of MoU-IREG End-to-end Functional Capability tests relating to the international roaming of a Mobile Station subscribed to GPRS services, belonging to a home PLMN (a), to and within a visited PLMN (b).

Throughout this document, GPRS refers to as both GPRS Release ‘97/98 (i.e. 2.5G) and GPRS Release ’99/UMTS (i.e. 3G). Also, if a roaming subscriber gains access to GPRS services through a GSM radio network (BSS) and a R99 SGSN then, in this case, VPLMN(b) is considered as a GPRS R97/98 network.

The tests specified here do not replace the End-to-end Functional Capability tests for Inter-PLMN Roaming [see Stage 4: MoU-IREG PRD IR24], because not every roamer will be subscribed to a GPRS 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 GPRS-roaming will be a bilateral activity between two PLMNs, please note that this document is written in an 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 MoU-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.

MoU-IREG Document PRD IR23 defines the scope and purpose of each stage of testing.

This document does not cover:

-SCCP testing. [see Stage 2: MoU-IREG PRD IR25] -UDP/IP testing. -Exchange of PLMN numbering, addressing and routeing data. [see Stage 3: MoU-IREG PRD IR23] -Testing of Transferred Account Procedure, billing applications and any inter-PLMN financial -statement; [see MoU-TADIG PRD TD06]. However the production of a Toll Ticketing file, for use in the MoU-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: MoU-IREG PRD IR23] -IR24 International Roaming testing. [see Stage 4: MoU-IREG PRD IR24]

1.2 Abbreviations

The following abbreviations are used:

2.5G (“GPRS Release ‘97/98”)

3G (“GPRS Release ’99 or UMTS”)

2G-SGSN (“Release ‘97/98 SGSN”)

3G-SGSN (“Release ’99 SGSN”)

APN (“Access Point Name”)

BSSAP+ (“Base Station System Application Part +”)

BSS (“Base Station Subsystem”)

DNS (“Domain Name System”)




Diffserv (“IETF Differentiated Services”)

DSCP (“DiffServ Code Point”)

FTP (“File Transfer Protocol”)

G-CDR Gateway GPRS Support Node – Call Detail Record

GGSN (“Gateway GPRS Support Node”)

GMSC (“Gateway Mobile Services Switching Centre”)

HLR (“Home Location Register”)

HPLMN (“Home PLMN”)

HTTP (“Hypertext Transport Protocol”)

IP (“Internet Protocol)

ISP (“Internet Service Provider”)

M-CDR (“Mobility Management - Call Detail Record”)

MM (“Mobility Management”)

MMSC ( “Multimedia Messaging Service Center”)

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

MSC (“Mobile Services Switching Centre”)

PDP (“Packet Data Protocol, e.g., IP or X.25”)

PLMN (“Public Land Mobile Network”) PLMN(a)

RAI (“Routeing Area Identity”)

S-CDR (“Serving GPRS Support Node – Call Detail Record”)

SGSN (“Serving GPRS Support Node”).

SMS (“Short Message Service”)

SMS-SC (“Short Message Service Centre”)

UDP (“User Datagram Protocol”)

THP (“Traffic Handling Priority”)

UMTS (“Universal Mobile Telecommunications System”)

UTRAN (“UMTS Terrestrial Radio Access Network”)

VMSC (“Visited Mobile Services Switching Centre”) VLR (“Visitor Location Register”).

WAP GW (“WAP Gateway”).




1.3 Objective of Tests

The fundamental objective of this testing is to confirm the capability of GPRS 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 behavior testing.

Not all possible services within GPRS should be tested. The focus is on services like HTTP,FTP or WAP but not on for example E-Mail.

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 the GPRS-functions and GPRS-features, 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 GPRS features.

The test cases in Chapter 2 are first of all mandatory. However they can/should only be done if the technical prerequisites are given for both involved networks under test.

The test scenarios in Annex B are optional. In order to ensure that services offered by a certain operator also work for the roaming case, both operators have to agree, if these optional test should be performed or not. However, in case one of the operators prefers to perform an optional test, the other operator has to provide facilities to accommodate this request. The performed optional test must be listed in Annex C.

1.4 Strategy for Testing

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.

Accordingly, the program of testing forms three distinct components.

(i) HPLMN(a) issues pre-programmed SIMs (see chapter 4.3) and programmes HLR (ii) PLMN(b) performs tests (iii) PLMN(b) and HPLMN(a) discuss results

1.5 Prerequisites

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 MOU-IREG-IR24)

2. The HLR contains GPRS subscription data and routeing 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 prime key to the GPRS subscription data stored in the HLR. There may be several sets of GPRS subscription data per IMSI.




HLR GPRS Subscription Data:

Field Description IMSI IMSI is the main reference key. MSISDN The basic MSISDN of the MS. SGSN Number The SS7 number of the SGSN currently serving this MS. SGSN Address The IP address of the SGSN currently serving this MS. SMS Parameters SMS-related parameters, e.g., operator-determined barring. MS Purged for GPRS Indicates that the MM and PDP contexts of the MS are deleted

from the SGSN. MNRG 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 subclauses "MAP-based GGSN – HLR Signalling" and "GTP and MAP-based GGSN – HLR Signalling".

Each IMSI contains zero or more of the following PDP context subscription records: PDP Context Identifier Index of the PDP context. PDP Type PDP type, e.g., PPP or IP. PDP Address PDP address, IP or X.121 address. This field shall be empty if

dynamic addressing is allowed. QoS Profile Subscribed

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

VPLMN Address Allowed

Specifies whether the MS is allowed to use the APN in the domain of the HPLMN only, or additionally the APN in the domain of the VPLMN.

Access Point Name 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 “*”

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

7. Configuration of test ennvironment 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 send 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 to. 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. The access of special services like WWW-pages will then be done by using browsers with special URL-addresses)

8. Dynamic Address allocation for access to Intranet/ISP

2 Test Cases The test cases are devided in four groups:

GPRS-attachment procedure IP-address administration and Intranet or Internet/ISP access (PDP-context-activation) Short Message Service (Point to point) Operator control of service

The test configuration 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.

HLR

PLMN(a)

SIM(a)

MS1

SIM(a)

MS2

PLMN(b)

Country (b)Country (a)

M = Monitor

RADIUS/DHCP-SERVER

M

INTRANET/ISP

LOCAL DNS

RADIUS/DHCP-SERVER

LOCAL DNS

INTRANET/ISP

/SGSN

/GGSN/SGSN

BSS orUTRANor

ROOT DNS

GPRS EXCHANGE

M

Intra PLMN

/GGSN

Intra PLMN




2.1 Mobility Management

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

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

Charging aspects: Opening of a M-CDR Charging parameters to collect/compare:

1) IMSI/MSISDN of the MS 2) IMEI of the ME, if available 3) Timestamp when GPRS-Attach is done (The M-CDR is closed after GPRS-Detach)

Test handling:

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

Actions: 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).

Result: Successful result if MS1(a) is in READY state (2.5G) or PMM-CONNECTED state

(3G) Successful result if valid MM contexts are established in the MS1(a) and SGSN(b).

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

Message-flow: (GPRS Attach only)




2. Identity Response

1. Attach Request (Attach Type: GPRS Attach only)

2. Identity Request

3. Authentication

5a. Update Location

5c Insert Subscriber Data Ack

M S BSS UTRAN SGSN(b) HLR(a)EIR

9. Attach Complete

8. Attach Accept

5b. Inser Subscriber Data

5dUpdate Location Ack

4. IMEI Check

2.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b)

Charging aspects: M-CDR is already open (GPRS-Attach) Opening of S-CDR and G-CDR (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 MS 2) IMEI of the ME, if available 3) Access Point Name 4) Timestamp when PDP-context-activation is done 5) Timestamp when downloading of pre-defined file is started 6) 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 QoS Profile for R99 MS1(a):




For the test cases defined in this section, if MS1(a) is of R99 then the Subscribed R99 QoS Profile, stored in HLR(a), shall include the Background Traffic Class as a minimum. The Interactive Traffic Class can alternatively be used for these test cases.

Note: Test cases involving R99 QoS Profiles for real-time applications, i.e. including Conversational or Streaming Traffic Class, are described in Appendix B (Optional Tests).

2.2.1 Intranet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID but

no Operator-ID and is not allowed to use visited GGSN)

Test handling:

Precondition: MS1(a) is GPRS-Attached in VPLMN(b).

(MS1(a) in STANDBY or READY state for 2.5G) (MS1(a) in PMM-IDLE or PMM-CONNECTED state for 3G)) 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). (Subscribed in HLR(a)) VPLMN not allowed for selected PDP context subscription records.

SGSN

VGGSNAPN: Intranet.mnc123.mcc456.gprs

mnc123.mcc456.gprs (HPLMN)

DNSmnc789.mcc888.gprs (VPLMN)

HGGSNAPN: Intranet.mnc789.mcc888.gprs

HLR

VPLMN HPLMN

APN:IntranetVPLMN add. not allowed

DNS success




Action: 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- or FTP-server or doing WAP-access.

Result: 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(b) interrogates DNS-Functionality with selected APN with appended HPLMN(a) 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 HTTP- or FTP-service or doing WAP-access.

Comments: This test case confirms PDP context activation 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.

2.2.2 PDP Context Modification Procedure triggered by changing of QoS Profile subscribed in HLR(a)

Precondition: Preconditions and PDP-Context initiated within chapter 2.2.1 still exists. Action: Operator of PLMN(A) changes the QoS in HLR(a) of the active PDP context to the

highest data throughput rate while PDP Context is active. (PDP Context Modification Procedure) Pre-defined file is requested/transferred from External Network (Network-ID) to MS1(a) by accessing HTTP- or FTP-server or doing WAP-access.

Result: PDP Context is changed towards QoS in GGSN(a)




Pre-defined file is successfully transferred at a new agreed higher quality (data rate) with no errors after using HTTP- or FTP-service or doing WAP-access.

Action: MS1(a) performs “Deactivate PDP Context Request”. Result: PDP-Context is deactivated Comments: This test case confirms Update PDP Context Request/Response procedure between

SGSN(b) and GGSN(a) normally done during an Inter SGSN Routing Area Update procedure. In addition PDP context deactivation towards a home GGSN(a) is tested. It should be mentioned that the used mobile can influence this test case by not supporting the requested QoS-Class subscribed in the HLR(a).

Message-flow: (Update PDP Context Request Procedure)

2. Insert Subscriber Date Ack

3. Update PDP Context Request

1. Insert Subscriber Date (QoS-Negotiation)

MS SGSN(b) HLR(a)

5. Modify PDP Context Request

6. Modify PDP Context Accept

4. Update PDP Context Response

GGSN(a)




2.2.3 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID and no Operator-ID)

Test handling:

Precondition: MS1(a) is GPRS-Attached in VPLMN(b). (MS in STANDBY or READY state for 2.5G) (MS in PMM-IDLE or PMM-CONNECTED state for 3G)) 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). (Subscribed in HLR(a))

SGSN

VGGSNAPN: Internet.mnc123.mcc456.gprs

DNSmnc123.mcc456.gprs (VPLMN)mnc789.mcc888.gprs (HPLMN)

HGGSNAPN: Internet.mnc789.mcc888.gprs

HLR

VPLMN HPLMN

APN:Internet

VPLMN add. allowedflag=YES

DNS success




VPLMN allowed for selected PDP context subscription records.

Action: 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- or FTP-Server or doing WAP-access.

Result: 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 VPLMN APN-Operator-ID. Selected APN is translated to a GGSN(b)-Address in the VPLMN(b). 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- or FTP-service or doing WAP-access.

Action: MS1(a) performs “Deactivate PDP Context Request”. Result: PDP-Context is deactivated

Comments: This test case confirms PDP context activation/deactivation towards a visited GGSN(b)

with: · APN(R) is not empty; (Network-ID, no Operator-ID) · Setting of APN (Operator-ID) by subscription for VPLMN(b) (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.




2.2.4 ISP/Internet 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)

Test handling:

Precondition: MS1(a) is GPRS-Attached in VPLMN(b). (MS in STANDBY or READY state for 2.5G) (MS in PMM-IDLE or PMM-CONNECTED state for 3G)) 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).

SGSN

VGGSNAPN:Internet.mnc123.mcc456.gprs

mnc123.mcc456.gprs (VPLMN)

DNSmnc789.mcc888.gprs (HPLMN)

HGGSNAPN:Internet.mnc.789.mcc888.gprs

HLR

VPLMN HPLMN

APN:Internet

VPLMN add. not allowed

DNS success




One PDP context subscription record exists in HLR(a) where APN(S) = APN(R). (Subscribed in HLR(a))VPLMN not allowed for selected PDP context subscription records.


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- or FTP-server or doing WAP-access.


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 HTTP- or FTP-Service or doing WAP-access.


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




2.2.5 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides no Network-ID and no Operator-ID; APN chosen from a single HLR PDP-context; no wild card using)

Test handling:

SGSN

VGGSNAPN: Subscribed APN.mnc123.mcc456.gprs


HGGSNAPN: Subscribed APN.mnc789.mcc888.gprs

HLR

VPLMN HPLMN

APN: no APN

VPLMN add. not allowedflag=YES

DNS success




Precondition: MS1(a) is GPRS-Attached in VPLMN(b). (MS1(a) in STANDBY or READY state for 2.5G) (MS1(a) in PMM-IDLE or PMM-CONNECTED state for 3G) No valid PDP contexts are established in the MS1(a). A unique PDP context subscription record exists in HLR(a) where PDP type (S) = PDP type (R) and with an APN(S) (Subscribed). VPLMN is not allowed for selected PDP context subscription records.


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). No APN(R) is sent by MS1(a). (APN(R) not present) Pre-defined file is requested/transferred from External Network (Network-ID) by accessing HTTP- or FTP-server or doing WAP-access.

Result: SGSN(b) receives no APN(R).

SGSN(b)selects PDP context subscription record with APN(S) and sets selection mode parameter to “subscribed”. SGSN(b) interrogates DNS-Functionality with selected APN with appended HPLMN(a) 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 context is established in the MS1(a). Connection to Network specified by APN is established. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP- or FTP-service or doing WAP-access.



with: · APN is chosen as the APN(S) from the single PDP context. · Setting of APN by subscription for HPLMN(a). (APN(S)) · Setting up IP-tunnel connections (GTP, IP, UDP) · 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 attempt




2.3 SMS Test Cases

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

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 MS 2) IMEI of the ME, if available 3) 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)

Test handling:

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

Action: Switch on MS1(a) (GPRS-Attached only). Switch off MS2(a).

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. Switch on MS2(a) (GPRS-Attached only). Await delivery of Short Message to MS2(a) Check contents of Short Message with those transmitted.

Result: Successful result if Short Message is correctly delivered after switching MS2(a) on.

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

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




MS BSS/UTRAN SGSN GGSN MSC/VLR HLR SMS-IW SM-SC | | | | | | | | |<----|---------->| | | | | | Message Transfer 1 | | | | | | | | (SM) | | |-----|-----|----->| | Forward Short Message 2 | | | | | | | | (SM) | | | | | | |---->| Message Transfer 3 | | | | | | | | (SM) | | | | | | |<----| Delivery Report 4 | | | | | | | | | | |<----|-----|-----|-----| | Forward Short Message Result 5 | | | | | | | | |<----|-----------| | | | | | Delivery Report 6 MS BSS/UTRAN SGSN GGSN MSC/VLR HLR SMS-GMSC SM-SC | | | | | | | | | | | | | | |<----| Message Transfer 1 | | | | | | | | (SM, MS Address) | | | | | |<----| | Send Routeing Info For Short Message | | | | | | | | | | | | | |---->| | Send Routeing Info For Short Message | | | | | | | | Result | | | | | | | | (SGSN Number, MSC Number) | | |<----|-----|-----|-----| | Forward Short Message 4 | | | | | | | | (SM) |<----|---------->| | | | | | Message Transfer 5 | | | | | | | | (SM) | | |-----|-----|-----|---->| | Forward Short Message Result 6 | | | | | | | | | | | | | | |---->| Delivery Report 7

2.4 Operator Control of Service

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

Test handling:

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

Action: 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).

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

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




HLRMS BSS/UTRAN GGSNSGSN MSC/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

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

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

Action: 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).

Result: Successful result if SGSN(b) record for MS1(a) contains ODB information and no

PDP-context-activation and SMS-mobile originated attemps are successful.

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

3 Equipment Requirements

3.1 User Equipment

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 failure




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

3.2 Test Equipment

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

4 Pre-Testing Data Exchange

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

Exchange of this data will be made in a centralized way under the responsibility of the GSM MoU Permanent Secretariat in charge of the maintenance of PRDs and in particular of PRD IR21-GPRS, where the relevant information is contained

4.1 Testing Contract Information

The following information should be exchanged by both PLMNs.

(i) Test Co-ordination contact names, telephone numbers and fax number

4.2 PLMN/IP-addressing, numbering and routing data

Confirmation of the PLMN/IP-addressing numbering and routing data as referenced in the Stage 3 [MoU-IREG PRD IR23], is regarded as advisable. Such information includes:

(i) E212-E214 translation (ii) E164 Number range (iii) International Gateway Signaling Point Codes (iv) SMS Service Centre E164 address (v) SGSN-/GGSN-IP addresses used (vi) SGSN-/GGSN Global Title Address used (vii) PDP context profiles (viii) APNs (ix) DNS IP-Addresses

4.3 SIM associated data supplied by PLMN(a)

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

(i) PIN, PUK/(SUPER PIN).




(ii) IMSI (iii) MSISDN (iv) Basic Service Subscription Information (v) Subscriber data concerning GPRS-attach and GPRS-data-transfer (PDP-context files) (vi) Access point names In order to perform the tests, 3 different SIM-card profiles are required: SIM A: APN Name : “This should contain one HPLMN´s APN” VPLMN allowed = yes SIM B: APN Name : “This should contain one HPLMN´s APN” VPLMN allowed = no SIM C: APN Name : “ * ” (wild card) VPLMN allowed = yes

4.4 GPRS Inter-PLMN connection parameters

To establish Inter-PLMN connectivity it is necessary to exchange information as: (i) Link transport, capacity and routing parameter

(ii) Link carrier and topology

(iii) Gp interface information

(iv) Security related information if necessary towards interconnection

4.5 IP-server information

The following information is required to provide IP-connectivity testing: (i) IP address of HPLMN(a) server (HTTP-, FTP-, DNS-, PROXY-server)

(access via GGSN(a)) (ii) IP address of VPLMN(b) server (HTTP-, FTP-, DNS-, PROXY-server)

(access via GGSN(b))

4.6 Required extension to MOU-IREG PRDs

The following extensions to MoU-IREG PRDs are required to provide the necessary information to run the tests described here: IR21-GPRS: In order to have a common and easy overview of the most important data related to international roaming, a database for storing this data has been created for GPRS: • New table including BSSAP+ Application Context and current version • Information about IP-routing and IP-naming-conventions • Information about logical addresses (APNs) • PDP-context types and profiles




IR23: • description of GPRS-testing specified within this document

END OF SPECIFICATION

APPENDIX A

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

A.1.1 Roaming Scenario to be Tested

HPLMN(a) VPLMN(b)

GPRS R97/98 GPRS R97/98 X




GPRS R99/UMTS GPRS R97/98

GPRS R97/98 GPRS R99/UMTS

GPRS R99/UMTS GPRS R99/UMTS

Note 1: GPRS R97/98 is also referred to as 2.5G and GPRS R99/UMTS as 3G.

Note 2: If a roaming subscriber gains access to services through a GSM radio network (BSS) and a R99 SGSN then, for this scenario, VPLMN(b) is considered to be a GPRS R97/98 network.

A.1.2 Network Operator Information

HPLMN (a) VPLMN (b) Date of Tests Testing personnel PLMN(a) Tel/Fax E-mail Testing personnel PLMN(b) Tel/Fax HLR Identity/Identities HLR Manufacturer(s) HLR Software Build Level(s) SGSN Identity/Identities SGSN Manufacturer(s) SGSN Software Build Level(s) GGSN Identity/Identities HGGSN 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) Comments

A 2.1 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.1 GPRS-Attach of MS1(a) in VPLMN(b) (GPRS Attach only)

(a) MSC/VLR Record contents: MSISDN IMSI SGSN-Number Others HLR E164 Address (b) SGSN Record contents MSISDN IMSI MM-State SGSN-Address (c) Comments (d) Test case Result [Pass/Fail/Not performed] (e) Time and Date (f) Signature of Tester

A 2.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b)


A 2.2.1 Intranet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID but no Operator-ID and is not allowed to use visited GGSN)

Scenario HGGSN Serving Network (Internet) Intranet SIM to be used SIM B (HLR Subscription: APN1: “ This should

contain one HPLMN´s Intranet APN ”, VPLMN allowed flag = no)

Application to be tested APN keyed into the MS or Terminal Net Id:

Web Settings:

Start page

Login




Password

Primary IP Addresses of Internet DNS

Secondary IP Addresses of Internet DNS WAP Settings:

Start page

Login

Password

IP address Live Net WAP GW

Primary Port

Secondary Port

Expected Result The tunnel shall be opened and the application work successfully

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

MS type & software used

Time of PDP-context activation (hh:mm:ss)

Application usage successful ?

Time of PDP-context deactivation (hh:mm:ss)

Overall duration of context (mm:ss)

Total Data Sent during context (from MS)

Total Data Received during context (from MS)

Comments

Test case Result [Pass/Fail/Not performed]

Date and Name of Tester

A 2.2.2 PDP Context Modification Procedure triggered by changing of QoS Profile subscribed in HLR(a)



APN keyed into the MS or Terminal

New QoS-Parameter (bit-rate)










Comments



A 2.2.3 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID and no Operator-ID)

Scenario VGGSN Serving Network (Internet) ISP/Internet SIM to be used SIM A (HLR Subscription: APN1: “ This should

contain one HPLMN´s Internet APN ”, VPLMN allowed flag = yes)


Web Settings:

Start page

Login

Password



Start page

Login

Password


Primary Port

Secondary Port













Comments



A 2.2.4 ISP/Internet 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)

Scenario HGGSN Serving Network (Internet) ISP/Internet SIM to be used SIM B (HLR Subscription: APN1: “ This should

contain one HPLMN´s Internet APN ”, VPLMN allowed flag = no)


Web Settings:

Start page

Login

Password



Start page

Login

Password


Primary Port

Secondary Port













Comments



A 2.2.5 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides no Network-ID and no Operator-ID; APN chosen from a single HLR PDP-context; no wild card using)

Scenario HGGSN Serving Network (Internet) ISP/Internet SIM to be used SIM B (HLR Subscription: APN1: “ This should

contain one HPLMN´s Internet APN ”, VPLMN allowed flag = no)

Application to be tested APN keyed into the MS or Terminal “ “

Web Settings:

Start page

Login

Password



Start page

Login

Password


Primary Port

Secondary Port













Comments



A 2.3 SMS Test Cases

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

MSISDN of MS1(a) E164 address of HPLMN SMS – Service Centre

Time of transmitting to SMS-Service Centre (hh:mm:ss)

MSISDN of MS2(a) Time of receipt of SMS at MS2(a) Was message correctly received? Comments Test case Result [Pass/Fail/Not performed] Date Signature of Tester

A 2.4 Operator Control of Service

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

SGSN Record contents prior to cancellation:




MSISDN IMSI SGSN Record ereased? [Yes/No] GGSN(a) or GGSN (b) record erased? [Yes/No] PDP context deactivation successful? [Yes/No] Time delay between HLR deleting subscription and SGSN erasing record (secs)

Comments Test case Result [Pass/Fail/Not performed] Time Date Signature of Tester

A 2.4.2 Operator Determined Barring for all MS initiated PDP context activations of MS1(a)

MSISDN of MS1(a) Operator performed barring towards PDP-context activation from HLR [Yes/No]

SGSN record contains barring tags [Yes/No] Perform PDP-context activation from MS1(a). Is it successful? [Yes/No]

Comments Test case Result [Pass/Fail/Not Performed] Time Date Signature of Tester

End Of Appendix A




APPENDIX B (Optional Tests)

IREG GPRS OPTIONAL TESTS

The test scenarios in this annex are optional. In order to ensure that services offered by a certain operator also work for the roaming case, both operators have to agree, if these optional test should be performed or not. However, in case one of the operators prefers to perform an optional test, the other operator has to provide facilities to accommodate this request. This means the strategy, the prerequisites, the requirements and pre testing data to exchange is the same as for the mandatory test cases. The Roaming Scenario to be tested is:

HPLMN(a) VPLMN(b)

GPRS R97/98 GPRS R97/98




Note 1: GPRS R97/98 is also referred to as 2.5G and GPRS R99/UMTS as 3G. Note 2: If a roaming subscriber gains access to services through a GSM radio network (BSS) and a R99 SGSN then, for this scenario, VPLMN(b) is considered to be a GPRS R97/98 network.




B 1 Test cases

B 1.1 Mobility Management

B 1.1.1 Inter SGSN routing area update of MS1(a) in VPLMN(b) – Intra-System Change – GSM Radio Acces only

Preconditions: MS1(a) is attached to VPLMN(b). MM context is established for MS1(a) in SGSN1(b). PDP-context may be active.

Actions: Enable the movement of MS1(a) from a routing area served by SGSN1(b) to a routing area served by SGSN2(b). Check MM contexts in MS1(a), SGSN1(b)and SGSN2(b) for the IMSI/P-TMSI /MSISDN of MS1(a). If PDP context(s) exist(s), check PDP contexts in MS1(a), SGSN1(b) and SGSN2(b) for the MS1(a).

Result: Successful result if valid MM contexts are established in the MS1(a) and SGSN2(b).

Successful result if MM context is deleted from the SGSN1(b) at the expiry of SGSN1(b) timer. Successful result if PDP context are established in the SGSN2(b) in the case of active PDP contexts. Successful result if SGSN1(b) forwards the PDUs for MS1(a) to the SGSN2(b) till the expiry of SGSN1(b) timer.

Comments: This test case confirms operation of Update Location and Insert Subscriber Data

procedures after inter SGSN routing area update. It checks the support of relevant MAP operations, TCAP processes and SCCP address.

Message-flow:




MS1(a) BSS SGSN2(b) HLR(a)GGSNSGSN1(b)

2. SGSN Context Response 3. Security Functions

1. Routeing Area Update Request 2. SGSN Context Request



7. Update Location

10. Update Location Ack 11. Routeing Area Update Accept

8. Cancel Location


9. Insert Subscriber Data Ack

9. Insert Subscriber Data

12. Routeing Area Update Complete

5. Forward Packets

4. SGSN Context Acknowledge

B 1.1.2 Inter SGSN routing area update of MS1(a) in VPLMN(b) – Intra-System Change – UMTS Radio Acces only

Preconditions: MS1(a) is attached to VPLMN(b). MM context is established for MS1(a) in SGSN1(b). PDP context(s) may be active







Comments: This testcase confirms operation of Update Location and Insert Subscriber Data


Message-flow:


2. SGSN Context Request 1. Routeing Area Update Request

5. SGSN Context Ack

11. Cancel Location


9. Update PDP Context Response 9. Update PDP Context Request

10. Update Location

15. Routeing Area Update Complete

14. Routeing Area Update Accept 13. Update Location Ack

12. Insert Subscriber Data 12. Insert Subscriber Data Ack

2a. SRNS Context Request 2a. SRNS Context Response

11a. Iu Release Command 11a. Iu Release Complete

6. SRNS Data Forward Command 7. Forward Packets

8. Forward Packets

MS1(a) UTRAN SGSN2(b) HLR(a) GGSN SGSN1(b)

B 1.1.3 UMTS to GSM Inter SGSN routing area update of MS1(a) in VPLMN(b) – Inter-System Change


Actions: Enable the movement of MS1(a) from a routing area served by SGSN1(b) to a routing area served by SGSN2(b).




Check MM contexts in MS1(a), SGSN1(b)and SGSN2(b) for the IMSI/P-TMSI /MSISDN of MS1(a). If PDP context(s) exist(s), check PDP contexts in MS1(a), SGSN1(b) and SGSN2(b) for the MS1(a).





Message-flow:

2. Routing Area Update Request



11. Update GPRS Location

15. Update GPRS Location Ack


16. Routing Area Update Accept

12. Cancel Location





3. SGSN Context Request

13. Iu Release Command

13. Iu Release Complete

8a. Forward Packets

9. Forward Packets

4. SRNS Context Request

4. SRNS Context Response

8. SRNS Data Forward Command

1. Intersystem change decision

17. Routing Area Update Complete

MS1(a) 2G-SGSN2(b) HLR(a) GGSN 3G-SGSN1(b) BSS UTRAN




B 1.1.4 GSM to UMTS Inter SGSN routing area update of MS1(a) in VPLMN(b) – Inter-System Change







Message-flow:




2. Routing Area Update Request



9. Update GPRS Location

12. Update GPRS Location Ack


13. Routing Area Update Accept

10. Cancel Location





3. SGSN Context Request

7. Forward Packets

1. Intersystem change decision

14. Routing Area Update Complete

MS1(a) 3G-SGSN2(b) HLR(a) GGSN 2G-SGSN1(b) BSS UTRAN




B 1.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b)


B 1.2.1 Intranet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID but no Operator-ID) Test handling:

Precondition: MS1(a) is GPRS-Attached in VPLMN(b). (MS in STANDBY or READY state for 2.5G) (MS in PMM-IDLE or PMM-CONNECTED state for 3G)) 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). (Subscribed in HLR(a)) VPLMN allowed for selected PDP context subscription records.

SGSN




HLR

VPLMN HPLMN

APN: Intranet


DNS success




Action: 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- or FTP-Server or doing WAP-access.


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 VPLMN APN Operator-ID. Selected APN is translated to a GGSN(b)-Address in the VPLMN(b). 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- or FTP-service or doing WAP-access.



with: · APN(R) is not empty; (Network-ID, no Operator-ID) · Setting of APN (Operator-ID) by subscription for VPLMN(b) (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.




B 1.2.2 Intranet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID but no Operator-ID; Unsuccessful first DNS interrogation with APN+VPLMN-Operator-ID) Test handling:


(MS1(a) in STANDBY or READY state for 2.5G) (MS1(a) in PMM-IDLE or PMM-CONNECTED state for 3G)) 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). (Subscribed in HLR(a)) VPLMN allowed for selected PDP context subscription records


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)

SGSN

VGGSN


HGGSN

HLR

V P L M N HPLM N

VPLMN add. a l lowed

DNS success

APN: In t ranet .mnc789.mcc888.gprs

APN: In t rane t

APN: In t ranet .mnc123.mcc456.gprs




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- or FTP-server or doing WAP-access.

Result: 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(b) interrogates DNS-Functionality with selected APN with appended VPLMN(b) APN Operator-ID. Interrogation towards DNS-functionality with specific APN fails SGSN(b) interrogates DNS-Functionality with selected APN with appended HPLMN(a) 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 HTTP- or FTP-service or doing WAP-access.



with: · APN(R) is not empty; (Network-ID, no Operator-ID) · Setting of APN (Operator-ID) by subscription for HPLMN(a). (APN(S)) Unsuccessful first DNS-Interrogation with VPLMN-Operator-ID · 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




B 1.2.3 Default Intranet/ISP access of MS1(a) in VPLMN(b) using visited GGSN (user provides no Network-ID and no Operator-ID ; default APN chosen by SGSN(b); Wild Card using) Test handling:

Precondition: MS1(a) is GPRS-Attached in VPLMN(b). (MS1(a) in STANDBY or READY state for 2.5G) (MS1(a) in PMM-IDLE or PMM-CONNECTED state for 3G)) 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). PDP context subscription record exists in HLR where APN(S) = wild card. VPLMN allowed for wild card subscription records. SGSN(b) knows an APN(SGSN) supporting delivered PDP-type (R)


SGSN

VGGSNAPN: default APN.mnc123.mcc456.gprs

DNSmnc123.mcc456.gprs(VPLMN))mnc789.mcc888.gprs (HPLMN)

HGGSNAPN: default APNmnc789.mcc888.gprs

HLR

VPLMN HPLMN

APN:no APN


DNS success




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). No APN(R) is sent by MS1(a). (APN(R) not present) Pre-defined file is requested/transferred from External Network (Default Network-ID) to MS1(a) by accessing HTTP- or FTP-Server or doing WAP-access.


Check of HLR(a) if PDP context subscription record with APN(S) = wild card is available. SGSN(b)selects PDP context subscription record with APN(SGSN) (a default APN should be chosen by SGSN(b)) and sets selection mode parameter to “chosen by SGSN(b)”. (APN=APN(SGSN)) SGSN(b) interrogates DNS-Functionality with selected APN with appended VPLMN(b) APN Operator-ID. Selected APN is translated to a GGSN(b)-Address in the VPLMN(b). 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 is established. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP- or FTP-service or doing WAP-access.



with: · Default APN chosen by SGSN(b). · Default APN establishes a default ISP/Intranet connection chosen by SGSN(b) in VPLMN. · 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




B 1.2.4 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID and HPLMN Operator-ID) Test handling:

Precondition: MS1(a) is GPRS-Attached in VPLMN(b). (MS in STANDBY or READY state for 2.5G) (MS in PMM-IDLE or PMM-CONNECTED state for 3G)) 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). (Subscribed in HLR(a)) VPLMN is allowed for selected PDP context subscription records.

SGSN

VGGSNAPN: Internet.mnc123.mcc456.gprs


HGGSNAPN: Internet.mnc789.mcc888.gprs

HLR

VPLMN HPLMN

APN: Internet.mnc789.mcc888.gprs


DNS success




Action: 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, PLMN A Operator-ID) is sent by MS1(a). Pre-defined file is requested/transferred from External Network (Network-ID) by accessing HTTP- or FTP-server or doing WAP-access.

Result: 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. 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 context is 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- or FTP-service or doing WAP-access.

Action: MS1(a) performs “Deactivate PDP Context Request”. Result: PDP-Context is deactivated Comments: This test case confirms PDP context activation/deactivation towards a home GGSN(a)

with: · APN(R) is not empty; (Network-ID, PLMN A Operator-ID) · Setting up IP-tunnel connections (GTP, IP, UDP) · 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.




B 1.2.5 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides no Network-ID and no Operator-ID; APN chosen from a single HLR PDP-context; no wild card using) Test handling:


(MS1(a) in STANDBY or READY state for 2.5G) (MS1(a) in PMM-IDLE or PMM-CONNECTED state for 3G)

SGSN




HLR

VPLM N HPLM N

APN: no APN


DNS success




No valid PDP contexts are established in the MS1(a). A unique PDP context subscription record exists in HLR(a) where PDP type (S) = PDP type (R) and with an APN(S). VPLMN is allowed for selected PDP context subscription records.




SGSN(b)selects PDP context subscription record with APN(S) and sets selection mode parameter to “subscribed”. SGSN(b) interrogates DNS-Functionality with selected APN with appended VPLMN(b) APN Operator-ID. Selected APN is translated to a GGSN(b)-Address in the VPLMN(b). SGSN(b) returns an “Activate PDP Context Accept” message to the MS1(a) including PDP type and PDP address. Valid PDP context is established in the MS1(a). Connection to Network specified by APN is established. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP- or FTP-service or doing WAP-access.



with: · APN is chosen as the APN(S) from the single PDP context. · Setting of APN by subscription for VPLMN(b) (APN(S)). · Setting up IP-tunnel connections (GTP, IP, UDP) · 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




B 1.2.6 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides no Network-ID and no Operator-ID; APN chosen from a single HLR PDP-context; no wild card using; unsuccessful first interrogation with APN+VPLMN-Operator-ID) Test handling:


SGSN




HLR

VPLMN HPLMN

APN: no APN


DNS success




(MS1(a) in STANDBY or READY state for 2.5G) (MS1(a) in PMM-IDLE or PMM-CONNECTED state for 3G)) No valid PDP contexts are established in the MS1(a). A unique PDP context subscription record exists in HLR(a) where PDP type (S) = PDP type (R) and with an APN(S). VPLMN allowed for selected PDP context subscription records.




SGSN(b)selects PDP context subscription record with APN(S) and sets selection mode parameter to “subscribed”. SGSN(b) interrogates DNS-Functionality with selected APN with appended VPLMN(b) APN Operator-ID. Interrogation towards DNS-functionality with specific APN fails. SGSN(b) interrogates DNS-Functionality with selected APN with appended HPLMN(a) 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 context is established in the MS1(a). Connection to Network specified by APN is established. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP- or FTP-service or doing WAP-access



with: · APN is chosen as the APN(S) from the single PDP context. · Setting of APN by subscription for HPLMN(a). (APN(S)) · Unsuccessful first DNS-Interrogation with VPLMN-Operator-ID. · Setting up IP-tunnel connections (GTP, IP, UDP) · 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

B 1.2.7 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID and Operator-ID, VPLM not allowed)

Test handling:

Precondition: MS1(a) is GPRS-Attached in VPLMN(b). (MS in STANDBY or READY state for 2.5G)

SGSN

VGGSN

APN: Internet.mnc123.mcc456.gprs

DNS mnc123.mcc456.gprs (VPLMN)

HGGSN

HLR

VPLMN HPLMN

APN:Internet.mnc123.mcc456.gprs

VPLMN add. Not allowed flag=YES




(MS in PMM-IDLE or PMM-CONNECTED state for 3G)) 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). PDP Context subscription record exists in HLR(a) where APN(S) is Wild Card VPLMN not allowed for selected PDP context subscription records.

Action: 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 and VPLMN Operator-ID) is sent by MS1(a).

Result: SGSN (b) does not allow activating PDP-context for MS1(a). Comment: This test case confirms PDP context activation is rejected. Because the

user chooses the APN that is specified as VPLMN not allowed Flag

B 1.3 3G to 3G Roaming only – GPRS PDP Context Activation by MS1(a) in VPLMN(b) using Home GGSN – Different QoS Profiles are applied

The series of test cases described in this section are applicable to 3G to 3G roaming only, i.e. both HPLMN(a) and VPLMN(b) are GPRS R99/UMTS networks.

Before performing these tests, both HPLMN(a) and VPLMN(b) must ensure that their network (i.e. UTRAN + Core Network) supports the QoS level to be tested. For instance, two operators may initially perform the tests for QoS profiles including the Background and Interactive traffic classes until Streaming and Conversational traffic classes are supported.

Note that in order to fully test the end-to-end QoS performance, the GRX backbone(s) in place between HPLMN(a) and VPLMN(b) must provide support for UMTS QoS.

B 1.3.1 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Background Traffic Class Test handling:

HLR

VPLMN (3G) HPLMN (3G)

APN:Intranet VPLMN add. not allowed QoS (S) includes Background Traffic Class





(MS1(a) in PMM-IDLE or PMM-CONNECTED state for 3G) No valid PDP context established in MS1(a). One PDP context subscription record exists in HLR(a) where:

• PDP type (S) = PDP type (R), • APN (S) = APN (R), • QoS (S) includes the Background Traffic Class, • VPLMN Address is NOT Allowed, • NO PDP Address is present (Dynamic Address Allocation).


MS1(a) sends: • PDP type (R), • APN (R), where only Network Id is provided, • QoS (R), where all parameters are set to “Subscribed”, • NO PDP Address, i.e. Dynamic Address Allocation is applied.

Pre-defined file is requested/transferred from External Network (Network Id) to MS1(a) by accessing HTTP- or FTP-server. The Diffserv Code Point (DSCP) of IP packets (“Network” IP layer below GTP and UDP) on the Gp interface is checked for both uplink and downlink traffic.


SGSN(b) selects PDP context subscription record that includes APN (S) (APN (S) =APN (R)) and sets selection mode parameter to “subscribed”. SGSN(b) interrogates DNS-Functionality with selected APN with appended HPLMN(a) APN Operator Id. The selected APN is translated to a GGSN(a) IP Address in the HPLMN(a). SGSN(b) returns an “Activate PDP Context Accept” message to the MS1(a) (including the PDP type and PDP address). Valid PDP context is established in MS1(a).




Connection to the Network specified by APN (Network Id) is established. Pre-defined file is successfully transferred at an agreed quality (bitrate) with no errors after using HTTP- or FTP-service. The DSCP of IP packets on the Gp interface is “000000” for both uplink and downlink traffic.

Comments: This test case confirms PDP context activation towards a home GGSN(a) using a QoS

Profile where the Traffic Class is Background (3G to 3G roaming only). VSGSN(b) Diffserv marks uplink Gp traffic with DSCP “000000”. HGGSN(a) Diffserv marks downlink Gp traffic with DSCP “000000”. 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.

B 1.3.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Interactive Traffic Class and Different Traffic Handling Priorities The Traffic Handling Priority (THP) specifies the relative importance of applications that belong to the Interactive traffic class, e.g. m-commerce transactions may have a higher priority than web browsing traffic. THP can be allocated one of three values (1, 2 or 3) that result in different Diffserv Code Points used to mark Gp/Gn traffic. Note that THP of value 1 offers the highest level of priority.

(a) Traffic Handling Priority is 1

Test handling:

SGSN



HLR

VPLMN(3G)

HPLMN (3G)


DNS success

QoS (S) includes Interactive Traffic Classand THP of value 1






• PDP type (S) = PDP type (R), • APN (S) = APN (R), • QoS (S) includes the Interactive Traffic Class and Traffic Handling Priority of

value 1, • VPLMN Address is NOT Allowed, • NO PDP Address is present (Dynamic Address Allocation).



Pre-defined file is requested/transferred from External Network (Network Id) to MS1(a) by accessing HTTP- or FTP-server. The Diffserv Code Point (DSCP) of IP packets (“Network” IP layer below GTP and UDP) on the Gp interface is checked for both uplink and downlink traffic.


SGSN(b) selects PDP context subscription record that includes APN (S) (APN (S) =APN (R)) and sets selection mode parameter to “subscribed”. SGSN(b) interrogates DNS-Functionality with selected APN with appended HPLMN(a) APN Operator Id. The selected APN is translated to a GGSN(a) IP Address in the HPLMN(a). SGSN(b) returns an “Activate PDP Context Accept” message to the MS1(a) (including the PDP type and PDP address). Valid PDP context is established in MS1(a). Connection to the Network specified by APN (Network Id) is established. Pre-defined file is successfully transferred at an agreed quality (bitrate) with no errors after using HTTP- or FTP-service. The DSCP of IP packets on the Gp interface is “011010” for both uplink and downlink traffic.





Profile where the Traffic Class is Interactive and the Traffic Handling Priority is of value 1 (3G to 3G roaming only). VSGSN(b) Diffserv marks uplink Gp traffic with DSCP “011010”. HGGSN(a) Diffserv marks downlink Gp traffic with DSCP “011010”. The user may attempt another activation to the same APN up to a maximum number of attempts if:

• The PDP context activation procedure fails, or • The SGSN returns an “Activate PDP Context Reject” (Cause, PDP

Configuration Options) message, or • The network (e.g. SGSN) downgrades the requested QoS to a lower Traffic

Class or Traffic Handling Priority.




(b) Traffic Handling Priority is 2

Test handling:







Pre-defined file is requested/transferred from External Network (Network Id) to MS1(a) by accessing HTTP- or FTP-server.

SGSN





HLR

VPLMN(3G)

HPLMN (3G)


DNS success





The Diffserv Code Point (DSCP) of IP packets (“Network” IP layer below GTP and UDP) on the Gp interface is checked for both uplink and downlink traffic.







Class or Traffic Handling Priority.




(c) Traffic Handling Priority is 3

Test handling:







Pre-defined file is requested/transferred from External Network (Network Id) to MS1(a) by accessing HTTP- or FTP-server.

SGSN





HLR

VPLMN(3G)

HPLMN (3G)


DNS success





The Diffserv Code Point (DSCP) of IP packets (“Network” IP layer below GTP and UDP) on the Gp interface is checked for both uplink and downlink traffic.







Class.




B 1.3.3 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Streaming Traffic Class Test handling:


(MS1(a) in PMM-IDLE or PMM-CONNECTED state for 3G)

SGSN





HLR

VPLMN(3G)

HPLMN (3G)


DNS success

QoS (S) includes Streaming Traffic Class




No valid PDP context established in MS1(a). One PDP context subscription record exists in HLR(a) where:

• PDP type (S) = PDP type (R), • APN (S) = APN (R), • QoS (S) includes the Streaming Traffic Class, • VPLMN Address is NOT Allowed, • NO PDP Address is present (Dynamic Address Allocation).



Streaming content is requested/transferred from External Network (Network Id) to MS1(a) by accessing streaming server through URL on web page. The Diffserv Code Point (DSCP) of IP packets (“Network” IP layer below GTP and UDP) on the Gp interface is checked for both uplink and downlink traffic. Techniques to measure QoS parameters (such as Delay, Jitter, Packet Loss, Bit Error Rate) shall be defined in the future. Target values for the measured QoS parameters shall be included.


SGSN(b) selects PDP context subscription record that includes APN (S) (APN (S) =APN (R)) and sets selection mode parameter to “subscribed”. SGSN(b) interrogates DNS-Functionality with selected APN with appended HPLMN(a) APN Operator Id. The selected APN is translated to a GGSN(a) IP Address in the HPLMN(a). SGSN(b) returns an “Activate PDP Context Accept” message to the MS1(a) (including the PDP type and PDP address). Valid PDP context is established in MS1(a).

Comments: This test case confirms PDP context activation towards a home GGSN(a) using a QoS Profile where the Traffic Class is Streaming (3G to 3G roaming only). VSGSN(b) Diffserv marks uplink Gp traffic with DSCP “100010”. HGGSN(a) Diffserv marks downlink Gp traffic with DSCP “100010”. The user may attempt another activation to the same APN up to a maximum number of attempts if:


Configuration Options) message, or The network (e.g. SGSN) downgrades the requested QoS to a lower Traffic Class.




B 1.3.4 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Conversational Traffic Class

Test handling:

SGSN

VGGSN

APN: Intranet.mnc123.mcc456.gprs


DNS

mnc789.mcc888.gprs (VPLMN)

HGGSN

APN: Intranet.mnc789.mcc888.gprs

HLR

VPLMN (3G) HPLMN (3G)

APN:Intranet VPLMN add. not allowed

DNS success

QoS (S) includes Conversational Traffic Class






• PDP type (S) = PDP type (R), • APN (S) = APN (R), • QoS (S) includes the Conversational Traffic Class, • VPLMN Address is NOT Allowed, • NO PDP Address is present (Dynamic Address Allocation).



At the time of writing this test case, no application requiring this QoS level is available. Once an application is made available this test case will be modified accordingly. The Diffserv Code Point (DSCP) of IP packets (“Network” IP layer below GTP and UDP) on the Gp interface is checked for both uplink and downlink traffic. Techniques to measure QoS parameters (such as Delay, Jitter, Packet Loss, Bit Error Rate) shall be defined in the future. Target values for the measured QoS parameters shall be included.


SGSN(b) selects PDP context subscription record that includes APN (S) (APN (S) =APN (R)) and sets selection mode parameter to “subscribed”. SGSN(b) interrogates DNS-Functionality with selected APN with appended HPLMN(a) APN Operator Id. The selected APN is translated to a GGSN(a) IP Address in the HPLMN(a). SGSN(b) returns an “Activate PDP Context Accept” message to the MS1(a) (including the PDP type and PDP address). Valid PDP context is established in MS1(a). Connection to the Network specified by APN (Network Id) is established. At the time of writing this test case, no application requiring this QoS level is available. Once an application is made available this test case will be modified accordingly. The DSCP of IP packets on the Gp interface is “101110” for both uplink and downlink traffic. The measured QoS parameters are within the value targets indicated above.


Profile where the Traffic Class is Conversational (3G to 3G roaming only).




VSGSN(b) Diffserv marks uplink Gp traffic with DSCP “101110”. HGGSN(a) Diffserv marks downlink Gp traffic with DSCP “101110”. The user may attempt another activation to the same APN up to a maximum number of attempts if:


Configuration Options) message, or the network (e.g. SGSN) downgrades the requested QoS to a lower Traffic Class.

B 1.4 MMS Test Cases

B 1.4.1 MMS Roaming: Mobile originated and terminated MMS (MS1(a) / MS2(a))

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 MS 2) IMEI of the ME, if available 3) 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)

Test handling:

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

Action: Use MS1(a) to transmit a Multimedia Message to MS2(a) via the Home MMSC

Await delivery of Multimedia Message to MS2(a) Check contents of Multimedia Message with those transmitted.

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

Comments: This test case confirms correct operation of mobile-originated/terminated MMS routing and transfer over GPRS radio channelsB 1.4.2 MMS Interworking: Mobile originated and terminated MMS (MS1(b) / MS2(a))

Charging aspects: Check that at least timestamps, amount of data, sender and receiver can be found in

MMS interworking CDR. Test handling:




Preconditions: MMS-MO/MT is provisioned

MS1(b) and MS2(a) are registered in VPLMN(b).

Action: Use MS1(b) to transmit a Multimedia Message to MS2(a) via inter-PLMN network Await delivery of Multimedia Message to MS2(a) Check contents of Multimedia Message with those transmitted.

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

Comments: This test case confirms correct operation of mobile-originated/terminated MMS

interworking routing and transfer over GPRS radio channels

B.2 Basic Test Results For Network Operator Information see Annex A. The numbering of the test result sections within this appendix is identical to the associated Test case from section B.1.

B 2.1 Mobility Management

B 2.1.1 Inter SGSN routing area update of MS1(a) in VPLMN(b) – Intra-System Change – GSM Radio Acces only

(a) MSC/VLR Record contents: MSISDN IMSI SGSN-Number HLR E164 Address Others HLR E164 Address




(b) SGSN Record contents MSISDN IMSI MM-State

New SGSN-Address Comments Test case Result [Pass/Fail/Not performed] Signature of Tester

B 2.1.2 Inter SGSN routing area update of MS1(a) in VPLMN(b) – Intra-System Change – UMTS Radio Acces only

(a) MSC/VLR Record contents: MSISDN IMSI SGSN-Number HLR E164 Address Others HLR E164 Address (b) SGSN Record contents MSISDN IMSI MM-State New SGSN-Address Comments Test case Result [Pass/Fail/Not performed] Signature of Tester

B 2.1.3 UMTS to GSM Inter SGSN routing area update of MS1(a) in VPLMN(b) – Inter-System Change

(a) MSC/VLR Record contents: MSISDN IMSI SGSN-Number HLR E164 Address Others HLR E164 Address




(b) SGSN Record contents MSISDN IMSI MM-State New SGSN-Address Comments Test case Result [Pass/Fail/Not performed] Signature of Tester

B 2.1.4 GSM to UMTS Inter SGSN routing area update of MS1(a) in VPLMN(b) – Inter-System Change

(a) MSC/VLR Record contents: MSISDN IMSI SGSN-Number HLR E164 Address Others HLR E164 Address (b) SGSN Record contents MSISDN IMSI MM-State New SGSN-Address Comments Test case Result [Pass/Fail/Not performed] Signature of Tester

B 2.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b)


B 2.2.1 Intranet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID but no Operator-ID)

Scenario VGGSN Serving Network (Internet) Intranet




SIM to be used SIM A (HLR Subscription: APN1: “ This should contain one HPLMN´s Internet APN ”, VPLMN allowed flag = yes)


Web Settings:

Start page

Login

Password


Secondary IP Addresses of Internet DNS

WAP Settings:

Start page

Login

Password


Primary Port

Secondary Port










Comments






B 2.2.2 Intranet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID but no Operator-ID; Unsuccessful first DNS interrogation with APN+VPLMN-Operator-ID)

Scenario HGGSN Serving Network (Internet) Intranet SIM to be used SIM A (HLR Subscription: APN1: “ This should



Web Settings:

Startpage

Login

Password


Secondary IP Addresses of Internet DNS

WAP Settings:

Start page Login Password IP address Live Net WAP GW Primary Port Secondary Port










Comments






B 2.2.3 Default Intranet/ISP access of MS1(a) in VPLMN(b) using visited GGSN (user provides no Network-ID and no Operator-ID ; default APN chosen by SGSN(b); Wild Card using)

Scenario VGGSN Serving Network (Internet) Defaul Intranet/ISP SIM to be used SIM C (HLR Subscription: “ * ”, VPLMN

allowed flag = yes) Application to be tested APN keyed into the MS or Terminal “ “

Web Settings:

Start page Login Password Primary IP Addresses of Internet DNS Secondary IP Addresses of Internet DNS

WAP Settings:

Start page

Login

Password


Primary Port

Secondary Port



MS type & software used Time of PDP-context activation (hh:mm:ss) Application usage successful ? Time of PDP-context deactivation (hh:mm:ss) Overall duration of context (mm:ss) Total Data Sent during context (from MS) Total Data Received during context (from MS)




Comments Test case Result [Pass/Fail/Not performed] Date and Name of Tester

B 2.2.4 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides Network-ID and HPLMN Operator-ID)

Scenario HGGSN Serving Network (Internet) Internet SIM to be used SIM A (HLR Subscription: APN1: “ This should


Application to be tested APN keyed into the MS or Terminal Net-Id: Op-Id:

Web Settings:


WAP Settings:














Comments



B 2.2.5 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides no Network-ID and no Operator-ID; APN chosen from a single HLR PDP-context; no wild card using)

Scenario VGGSN Serving Network (Internet) Internet SIM to be used SIM A (HLR Subscription: APN1: “ This should

contain one PLMN´s Internet APN ”, VPLMN allowed flag = yes) (*)

Application to be tested APN keyed into the MS or Terminal Net-Id: “ “

(*) The APN of SIM A should be implemented in the VPLMN

Web Settings:


WAP Settings:














Comments



B 2.2.6 ISP/Internet access of MS1(a) in VPLMN(b) using home GGSN (user provides no Network-ID and no Operator-ID; APN chosen from a single HLR PDP-context; no wild card using; unsuccessful first interrogation with APN+VPLMN-Operator-ID)

Scenario HGGSN Serving Network (Internet) Internet SIM to be used SIM A (HLR Subscription: APN1: “ This should


Application to be tested APN keyed into the MS or Terminal Net-Id: “ “

Web Settings:


WAP Settings:

Start page Login Password IP address Live Net WAP GW




Primary Port Secondary Port










Comments



B.2.2.7 ISP/Internet access of MS1(a) in VPLMN(b) using visited GGSN (user provides Network-ID and Operator-ID, VPLM not allowed)

MSISDN of originating MS (i.e.MS1(a)) MS type & software used APN keyed into the MS or Terminal The rejection to activate PDP context with V-SGSN is successful? : [Yes/No]

Time of PDP-context deactivation (hh:mm:ss) Test case Result [Pass/Fail/Not performed] Date Signature of Tester

B 2.3 3G to 3G Roaming only – GPRS PDP Context Activation by MS1(a) in VPLMN(b) with different QoS Profiles applied




B 2.3.1 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Background Traffic Class

Scenario HGGSN / 3G to 3G Roaming Serving Network Intranet SIM to be used SIM B (HLR Subscription: This shall contain one

HPLMN´s APN and VPLMN Address Allowed flag = no)


Web Settings:

Startpage Login Password Primary IP Addresses of Internet DNS Secondary IP Addresses of Internet DNS

WAP Settings:

Startpage Login Password IP address Live Net WAP GW Primary Port Secondary Port

Expected Result The tunnel shall be opened, the application shall work successfully and

DSCP of Gp traffic shall be “000000”.


MS type & software used Time of PDP-context activation (hh:mm:ss) Application usage successful? DSCP of uplink Gp traffic is “000000”? DSCP of downlink Gp traffic is “000000”? Time of PDP-context deactivation (hh:mm:ss) Overall duration of context (mm:ss) Total Data Sent during context (from MS) Total Data Received during context (from MS) Comments Testcase Result [Pass/Fail/Not performed]





B 2.3.2 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Interactive Traffic Class

(a) Traffic Handling Priority = 1

Scenario HGGSN / 3G to 3G Roaming Serving Network Intranet SIM to be used SIM B (HLR Subscription: This shall contain one

HPLMN´s APN and VPLMN Address Allowed flag = no)


Web Settings:


WAP Settings:


Expected Result The tunnel shall be opened, the application shall work successfully and DSCP of Gp traffic shall be “011010”.




Application usage successful?




DSCP of uplink Gp traffic is “011010”?

DSCP of downlink Gp traffic is “011010”?





Comments

Testcase Result [Pass/Fail/Not performed]


(b) Traffic Handling Priority = 2

Scenario HGGSN / 3G to 3G Roaming

Serving Network Intranet

SIM to be used SIM B (HLR Subscription: This shall contain one HPLMN´s APN and VPLMN Address Allowed flag = no)

Application to be tested

APN keyed into the MS or Terminal Net Id:

Web Settings:


WAP Settings:

















Comments



(c) Traffic Handling Priority = 3






Web Settings:


WAP Settings:

Startpage




Login Password IP address Live Net WAP GW Primary Port Secondary Port













Comments



B 2.3.3 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Streaming Traffic Class









Web Settings:

Startpage including URL for Streaming Content Login Password Primary IP Addresses of Internet DNS Secondary IP Addresses of Internet DNS

Expected Result The tunnel shall be opened, the application shall work successfully, the

DSCP of Gp traffic shall be “100010” and the measured QoS parameters shall be within the target values.







Measured QoS parameters within target?





Comments



B 2.3.4 GPRS PDP Context Activation by MS1(a) in VPLMN(b) – Subscribed QoS Profile includes Conversational Traffic Class



SIM to be used SIM B (HLR Subscription: This shall contain one HPLMN´s APN and VPLMN Address Allowed




flag = no)



At the time of writing this test case, no application requiring this QoS level is available.

Once an application is made available this test case will be modified accordingly.

Expected Result The tunnel shall be opened, the application shall work successfully, the DSCP of Gp traffic shall be “101110” and the measured QoS parameters shall be within the target values.







Measured QoS parameters within target?





Comments



B 2.4 MMS Test Cases

B 2.4.1 MMS Roaming: Mobile originated and terminated MMS (MS1(a) / MS2(a))

Scenario:

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




MMS Settings:

IP address of HPLMN MMSC WAP GW address APN Login Password Authentication Session/data mode (Primary/Secondary Port)

Security Delivery report Set terminal to fetch message automatically also when roaming

MSISDN of MS1(a) MSISDN of MS2(a) Time of transmitting to MMSC (hh:mm:ss) Time of notification receipt of MMS at MS2(a) Time of message receipt of MMS at MS2(a) Amount of data sent (bytes) Amount of data received (bytes) Was message correctly received? Comments MS type & software used Size of message sent/received (kB) Test case Result [Pass/Fail/Not performed] Delivery report received [Pass/Fail/Not applicable]

Date Signature of Tester

Excepted result:

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.

B 2.4.2 MMS Interworking: Mobile originated and terminated MMS (MS1(b) / MS2(a))

Scenario:

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




MMS Settings:

IP address of PLMN(a) MMSC WAP GW address (a) APN (a) Login (a) Password (a) Authentication (a) Session/data mode (Primary/Secondary Port) (a)

Security (a) Delivery report (a) IP address of PLMN(b) MMSC WAP GW address(b) APN (b) Login (b) Password (b) Authentication (b) Session/data mode (Primary/Secondary Port) (b)

Security (b) Delivery report (b) Set terminal to fetch message automatically also when roaming

MSISDN of MS1(b) MSISDN of MS2(a) Time of transmitting to MMSC (hh:mm:ss) Time of notification receipt of MMS at MS2(a) Time of message receipt of MMS at MS2(a) Amount of data sent (bytes) Amount of data received (bytes) MS type & software used Was message correctly received? Comments Test case Result [Pass/Fail/Not performed] Delivery report received [Pass/Fail/Not applicable]

Date Signature of Tester

Excepted MS1(b) sends the message without error messages and MS2(a) receives the




result: notification and fetches the message correctly. If case delivery report is used, the delivery report should be successfully received.

End Of Appendix B

APPENDIX C

Completion Certificate for IREG GPRS Testing for Inter-PLMN Roaming

Completion Certificate for MoU-IREGGPRS Testing for Inter-PLMN Roaming

This certificate confirms the successful completion of mandatory MoU-IREG-GPRS Tests for Mobile




Subscribers of.............................................PLMN(a) visiting.............................................................PLMN(b).

The roaming case tested was:-

HPLMN(a) VPLMN(b)

GPRS R97/98 GPRS R97/98




The Services tested were:-

GPRS attach only [Pass / Fail / Not applicable]....................

GPRS PDP context activation [Pass / Fail / Not applicable]....................

Short Message Services [Pass / Fail / Not applicable]....................

Operator Control of Service [Pass / Fail / Not applicable]....................

Other comments...........................................................................................................

..................................................................................................................................... Performed optional tests:..................................................................................................................................... The tests were completed on..............................(date). The testing team in PLMN...................................................................

were:.................................................................................................................

The testing team in PLMN...................................................................

were:................................................................................................................. Signed...................................................................... Date........................................... of PLMN.....................




Signed...................................................................... Date........................................... of PLMN.....................

End Of Appendix C

Gprs

Documents

valid mm contexts

root address lookup

dynamic address allocation

valid pdp contexts

ireg prd ir23

pdp configuration options

including pdp type

gprs release 97 98