Ir 35

GSM Association Permanent Reference Document: IR 35
Unrestricted - Industry
PRD IR.35
Title
Version Date
End to End Functional Capability Test Specification for Inter-PLMN GPRS Roaming
3.3.1 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
IR35331
Version 3.3.1
Page 1 of 93
Document History
Revision
Version 0.0.1 0.0.2 0.0.3 0.0.4 0.0.5 0.0.6
Date
Date 22.06.1999 06.08.1999 29.11.1999 14.12.1999 01.02.2000 03.03.2000
Brief Description
Brief Description IREG Doc GPRS 23/99 with changes according 4th Meeting of IREG GPRS for Ad-Hoc pre-discussion First draft of document for IREG GPRS group discussion (5th Meeting) Second draft of document for IREG GPRS group discussion (6th Meeting IREG Doc GPRS 23/99 with changes according 6th Meeting of IREG GPRS Modifications from comments send by email Introduction of Operator Control of Service test cases IREG Doc IR35 with changes according 7th Meeting of IREG GPRS Charging-Information Operator Control of Service Test cases A new test case added in Chapter 2.2.3 Charging information added, ODB test cases modified. Charging impacts, chapter 2.2, item no. 6 updated. Final modifications before IREG#38 Modified for IREG 38 approval Approved by IREG 38 subject to addition of Appendix A and B Appendix A and B completed Approved at Plenary 43. PL Doc 36/00 Rev 1 IREG Doc GPRS 35/00 with changes according 9th Meeting of IREG GPRS Changes/Clarification towards the meaning of the APN-NetworkIdentifier: APN-Network-ID defines to which external network the GGSN is connected to IREG Doc GPRS 57/00 (CR) with changes according to 11th Meeting of IREG GPRS Approved and revised document after IREG#39 for discussion on 1th Packet-WP-Meeting Modifications from comments according 1th IREG Packet-WP-GPRS (GSM NA IREG WG Suggested changes to IR35 Separation of optional test cases in a separate Annex Modifications from comments according 3rd IREG-Packet-Meeting (Creation of S-CDRs) Modified document for presentation on the IREG-#41-Meeting Approved and revised document after IREG#41 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 Approved and revised document after IREG#42 CR-004_Hutchison-3G, IREG-Doc 068_02 Approved and revised document after IREG#43 CR NTT-DoCoMo, IREG-Doc 092/02, Additional requirement of operator control of service.
Version 3.3.1 Page 2 of 93
0.0.7 0.0.8 0.0.9 1.0.0 2.0.0 2.1.0 3.0.0 3.0.1 3.0.2
24.02.2000 01.03.2000 03.03.2000 14.03.2000 15.03.2000 29.03.2000 28.04.2000 23.06.2000 30.08.2000
3.0.3 3.0.4 3.0.5 3.0.6 3.0.7 3.1.0 3.1.1 3.1.2
05.09.2000 23.11.2000 05.01.2001 01.03.2001 21.08.2001
17.10.2001 18.03.2001
3.2.0 3.3.0 3.3.1

IR35331
20.03.02 20.08.2002 11.02.2003
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
IR35331
Version 3.3.1
Page 3 of 93

TABLE OF CONTENTS
1.1 1.2 1.3 1.4 1.5
Scope of document......................................................................................................................................................................................... 7 Abbreviations ................................................................................................................................................................................................. 7 Objective of Tests .......................................................................................................................................................................................... 9 Strategy for Testing ..................................................................................................................................................................................... 9 Prerequisites ................................................................................................................................................................................................. 9
TEST CASES.............................................................................................................................................. 12
Mobility Management.................................................................................................................................................................................13 GPRS-Attach of MS 1 (a) in VPLMN(b) (GPRS Attach only).......................................................................................................13 GPRS PDP Context Activation by MS 1 (a) in VPLMN(b).....................................................................................................................14
2.1 2.1.1 2.2 2.2.1
Intranet access of MS 1 (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 MS 1 (a) in VPLMN(b) using visited GGSN (user provides Network-ID and no Operator-ID)......... 18 2.2.4 ISP/Internet access of MS 1 (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 MS 1 (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 2.3.1 2.4 2.4.1 2.4.2 SMS Test Cases ..........................................................................................................................................................................................24 Mobile originated and terminated SMS (MS 1 (a) GPRS-Attached only / MS 2 (a) GPRS-Attached only)............................24 Operator Control of Service......................................................................................................................................................................25 Location cancellation for MS 1 (a)-GPRS Subscription held in VPLMN(b) ..............................................................................25 Operator Determined Barring for all MS initiated PDP context activatons of MS 1(a)..........................................................26
3
3.1 3.2
EQUIPMENT REQUIREMENTS ............................................................................................................. 26

User Equipment............................................................................................................................................................................................26 Test Equipment ............................................................................................................................................................................................27
4
4.1 4.2 4.3 4.4 4.5 4.6
PRE-TESTING DATA EXCHANGE........................................................................................................ 27

Testing Contract Information...................................................................................................................................................................27 PLMN/IP-addressing, numbering and routing data .............................................................................................................................27 SIM associated data supplied by PLMN(a)..............................................................................................................................................27 GPRS Inter-PLMN connection parameters ...........................................................................................................................................28 IP-server information.................................................................................................................................................................................28 Required extension to MOU-IREG PRDs................................................................................................................................................28
IR35331
APPENDIX A ..................................................................................................................................................... 29
IREG GPRS Test Results for Mobile Stations of HPLMN(a) Roaming to VPLMN(b).........................................................................................29 A.1.1 A.1.2 A 2.1 A 2.1.1 A 2.2 A 2.2.1 Roaming Scenario to be Tested...........................................................................................................................................................29 Network Operator Information...........................................................................................................................................................30 Basic Test Results ................................................................................................................................................................................30 GPRS-Attach of MS 1 (a) in VPLMN(b) (GPRS Attach only).......................................................................................................31 GPRS PDP Context Activation by MS 1 (a) in VPLMN(b) ................................................................................................................31
Intranet access of MS 1 (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 MS 1 (a) in VPLMN(b) using visited GGSN (user provides Network-ID and no Operator-ID)......... 33 A 2.2.4 ISP/Internet access of MS 1 (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 MS 1 (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 A 2.3.1 A 2.4 A 2.4.1 A 2.4.2 SMS Test Cases......................................................................................................................................................................................36 Mobile originated and terminated SMS (MS 1 (a) GPRS-Attached only / MS 2 (a) GPRS-Attached only)............................36 Operator Control of Service.................................................................................................................................................................36 Location cancellation for MS 1 (a)-Subscription held in VPLMN(b) ..........................................................................................36 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 MS 1 (a) in VPLMN(b) Intra-System Change GSM Radio Acces only.........................39 B 1.1.2 Inter SGSN routing area update of MS 1 (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 MS 1 (a) in VPLMN(b) Inter-System Change............................................41 B 1.1.4 GSM to UMTS Inter SGSN routing area update of MS 1 (a) in VPLMN(b) Inter-System Change............................................43 B 1.2 GPRS PDP Context Activation by MS 1 (a) in VPLMN(b) ................................................................................................................45 B 1.2.1 Intranet access of MS 1 (a) in VPLMN(b) using visited GGSN (user provides Network-ID but no Operator-ID)......................45 B 1.2.2 Intranet access of MS 1 (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 MS 1 (a) in VPLMN(b) using visited GGSN (user provides no Network-ID and no OperatorID ; default APN chosen by SGSN(b); Wild Card using)...................................................................................................................................49 B 1.2.4 ISP/Internet access of MS 1 (a) in VPLMN(b) using home GGSN (user provides Network-ID and HPLMN Operator-ID) ...51 B 1.2.5 ISP/Internet access of MS 1 (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 MS 1 (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 MS 1 (a) in VPLMN(b) using visited GGSN (user provides Network-ID and Operator-ID, VPLM not allowed) ........................................................................................................................................................................................................................57
IR35331 Version 3.3.1 Page 5 of 93

B 1.3
3G to 3G Roaming only GPRS PDP Context Activation by MS 1 (a) in VPLMN(b) using Home GGSN Different QoS
Profiles are applied.......................................................................................................................................................................................................58 B 1.3.1 GPRS PDP Context Activation by MS 1 (a) in VPLMN(b) Subscribed QoS Profile includes Background Traffic Class....58 B 1.3.2 GPRS PDP Context Activation by MS 1 (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 MS 1 (a) in VPLMN(b) Subscribed QoS Profile includes Streaming Traffic Class.......67 B 1.3.4 GPRS PDP Context Activation by MS 1 (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 (MS 1 (a) / MS 2 (a)) .................................................................................71 B 1.4.2 MMS Interworking: Mobile originated and terminated MMS (MS 1 (b) / MS 2 (a)) .........................................................................71
B.2 BASIC TEST RESULTS........................................................................................................................ 72

B 2.1 Mobility Management ............................................................................................................................................................................72 B 2.1.1 Inter SGSN routing area update of MS 1 (a) in VPLMN(b) Intra-System Change GSM Radio Acces only........................72 B 2.1.2 Inter SGSN routing area update of MS 1 (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 MS 1 (a) in VPLMN(b) Inter-System Change............................................73 B 2.1.4 GSM to UMTS Inter SGSN routing area update of MS 1 (a) in VPLMN(b) Inter-System Change............................................74 B 2.2 GPRS PDP Context Activation by MS 1 (a) in VPLMN(b) ................................................................................................................74
B 2.2.1 Intranet access of MS 1 (a) in VPLMN(b) using visited GGSN (user provides Network-ID but no Operator-ID)......................74 B 2.2.2 Intranet access of MS 1 (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 MS 1 (a) in VPLMN(b) using visited GGSN (user provides no Network-ID and no OperatorID ; default APN chosen by SGSN(b); Wild Card using)...................................................................................................................................77 B 2.2.4 ISP/Internet access of MS 1 (a) in VPLMN(b) using home GGSN (user provides Network-ID and HPLMN Operator-ID) ..78 B 2.2.5 ISP/Internet access of MS 1 (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 MS 1 (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 MS 1 (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 MS 1 (a) in VPLMN(b) with different QoS Profiles applied....... 81
B 2.3.1 GPRS PDP Context Activation by MS 1 (a) in VPLMN(b) Subscribed QoS Profile includes Background Traffic Class....82 B 2.3.2 GPRS PDP Context Activation by MS 1 (a) in VPLMN(b) Subscribed QoS Profile includes Interactive Traffic Class.......83 B 2.3.3 GPRS PDP Context Activation by MS 1 (a) in VPLMN(b) Subscribed QoS Profile includes Streaming Traffic Class.......86 B 2.3.4 GPRS PDP Context Activation by MS 1 (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 (MS 1 (a) / MS 2 (a)) .................................................................................88 B 2.4.2 MMS Interworking: Mobile originated and terminated MMS (MS 1 (b) / MS 2 (a)) .........................................................................89
APPENDIX C ..................................................................................................................................................... 91
IR35331
Version 3.3.1
Page 6 of 93

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 3G (GPRS Release 97/98) (GPRS Release 99 or UMTS)
2G-SGSN (Release 97/98 SGSN) 3G-SGSN (Release 99 SGSN) APN BSSAP+ BSS DNS
IR35331
(Access Point Name) (Base Station System Application Part +) (Base Station Subsystem) (Domain Name System)

Diffserv DSCP FTP G-CDR GGSN GMSC HLR HPLMN HTTP IP ISP M-CDR MM MMSC MS MSC PDP PLMN RAI S-CDR SGSN SMS SMS-SC UDP THP UMTS UTRAN VMSC VLR WAP GW (IETF Differentiated Services) (DiffServ Code Point) (File Transfer Protocol) Gateway GPRS Support Node Call Detail Record (Gateway GPRS Support Node) (Gateway Mobile Services Switching Centre) (Home Location Register) (Home PLMN) (Hypertext Transport Protocol) (Internet Protocol) (Internet Service Provider) (Mobility Management - Call Detail Record) (Mobility Management) ( Multimedia Messaging Service Center)
(Mobile Station). (MSx(b) indicates that the MS subscription is managed by PLMN(b)). (Mobile Services Switching Centre) (Packet Data Protocol, e.g., IP or X.25) (Public Land Mobile Network) PLMN(a) (Routeing Area Identity) (Serving GPRS Support Node Call Detail Record) (Serving GPRS Support Node). (Short Message Service) (Short Message Service Centre) (User Datagram Protocol) (Traffic Handling Priority) (Universal Mobile Telecommunications System) (UMTS Terrestrial Radio Access Network) (Visited Mobile Services Switching Centre) (Visitor Location Register). (WAP Gateway).
IR35331
Version 3.3.1
Page 8 of 93

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) (ii) (iii) HPLMN(a) issues pre-programmed SIMs (see chapter 4.3) and programmes HLR PLMN(b) performs tests 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.
IR35331
Version 3.3.1
Page 9 of 93
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.
IR35331
Version 3.3.1
Page 10 of 93

HLR GPRS Subscription Data: Field IMSI MSISDN SGSN Number SGSN Address SMS Parameters MS Purged for GPRS
Description IMSI is the main reference key. The basic MSISDN of the MS. The SS7 number of the SGSN currently serving this MS. The IP address of the SGSN currently serving this MS. SMS-related parameters, e.g., operator-determined barring. 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 The quality of service profile subscribed. QoS Profile Subscribed Subscribed is the default level if a particular QoS profile is not requested. VPLMN Address Specifies whether the MS is allowed to use the APN in the Allowed 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/ISPfunctionality. 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.
Country (a)
PLMN(b)
Country (b)
PLMN(a)
MS 1 SIM(a) ROOT DNS HLR / SGSN
MS 2 SIM(a)
BSS or UTRAN or
/ GGSN
Intra PLMN
GPRS EXCHANGE
Intra PLMN
/ SGSN
M / GGSN LOCAL DNS LOCAL DNS INTRANET/ISP INTRANET/ISP
RADIUS/DHCP-SERVER
RADIUS/DHCP-SERVER
= Monitor
IR35331
Version 3.3.1
Page 12 of 93

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 MS 1(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. Power-up MS1(a) and perform GPRS Attach only on VPLMN(b). Check MM contexts in MS1(a) and SGSN(b) for the IMSI/P-TMSI /MSISDN of MS1(a). Successful result if MS1(a) is in READY state (2.5G) or PMM-CONNECTED state (3G) Successful result if valid MM contexts are established in the MS1(a) and SGSN(b). This test case confirms operation of Insert Subscriber Data procedures after GPRSAttach only . It checks the support of relevant MAP operations, TCAP processes and SCCP addressing.
Actions:
Result:
Comments:
Message-flow: (GPRS Attach only)
IR35331
Version 3.3.1
Page 13 of 93

MS BSS UTRAN SGSN(b)
EIR
HLR(a)
1. Attach Request (Attach Type: GPRS Attach only)
2. Identity Request 2. Identity Response 3. Authentication 4. IMEI Check 5a. Update Location
5b. Inser Subscriber Data

5c Insert Subscriber Data Ack
5dUpdate Location Ack
8. Attach Accept 9. Attach Complete
2.2
GPRS PDP Context Activation by MS 1(a) in VPLMN(b) M-CDR is already open (GPRS-Attach) Opening of S-CDR and G-CDR (The S-CDR and G-CDR are closed after PDP-contextdeactivation) 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 SCDR. 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
Charging aspects:
QoS Profile for R99 MS1(a):
IR35331
Version 3.3.1
Page 14 of 93
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 MS 1(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:
VPLMN
HPLMN
APN:Intranet
HLR
VPLMN add. not allowed
SGSN
DNS success
DNS
mnc789.mcc888.gprs (VPLMN) mnc123.mcc456.gprs (HPLMN)
VGGSN
APN: Intranet.mnc123.mcc456.gprs
HGGSN
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.
IR35331

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)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. 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.
Result:
Comments:
2.2.2 PDP Context Modification Procedure triggered by changing of QoS Profile subscribed in HLR(a) Precondition: Action: Preconditions and PDP-Context initiated within chapter 2.2.1 still exists. 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. PDP Context is changed towards QoS in GGSN(a)
Result:
IR35331
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: Result:
MS1(a) performs Deactivate PDP Context Request. 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)

M S
SGSN(b)
GGSN(a)
HLR(a)
1. Insert Subscriber Date (QoS-Negotiation) 2. Insert Subscriber Date Ack
3. Update PDP Context Request 4. Update PDP Context Response 5. Modify PDP Context Request 6. Modify PDP Context Accept
IR35331
Version 3.3.1
Page 17 of 93
2.2.3 ISP/Internet access of MS 1(a) in VPLMN(b) using visited GGSN (user provides NetworkID and no Operator-ID) Test handling:
VPLMN
HPLMN
APN:Internet
HLR
DNS success
SGSN
VPLMN add. allowed flag=YES
DNS
VGGSN
APN: Internet.mnc123.mcc456.gprs
HGGSN
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. 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) 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. MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated
Result:
Action: Result:
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.
IR35331
Version 3.3.1
Page 19 of 93
2.2.4 ISP/Internet access of MS 1(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:
VPLMN HPLMN
APN:Internet
HLR
VPLMN add. not allowed
SGSN
DNS success
DNS
mnc789.mcc888.gprs (HPLMN) mnc123.mcc456.gprs (VPLMN)
VGGSN
APN:Internet.mnc123.mcc456.gprs
HGGSN
APN:Internet.mnc.789.mcc888.gprs
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 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, 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) receives APN(R) sent by MS1(a). SGSN(b) selects PDP context subscription record (APN(S ), APN(S)=(APN(R)) and sets selection mode parameter to subscribed. SGSN interrogates DNS-Functionality with selected APN with appended HPLMN APN-Operator-ID. Selected APN is translated to a GGSN(a)-Address in the HPLMN(a). SGSN(b) returns an Activate PDP Context Accept message to the MS1(a) including PDP type and PDP address. Valid PDP contexts are established in the MS1(a). Connection to Network specified by APN(Network-ID) is established. Pre-defined file is successfully transferred at an agreed quality (data rate) with no errors after using HTTP- or FTP-Service or doing WAP-access. MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated 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.
Result:
Action: Result: Comments:
IR35331
Version 3.3.1
Page 21 of 93
2.2.5 ISP/Internet access of MS 1(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:
VPLMN
HPLMN
APN: no APN
HLR SGSN
VPLMN add. not allowed flag=YES
DNS success
DNS
VGGSN
APN: Subscribed APN.mnc123.mcc456.gprs
HGGSN
IR35331
Version 3.3.1
Page 22 of 93

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. 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). 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. 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. MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated This test case confirms PDP context activation/deactivation towards a home GGSN(a) 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
Action:
Result:
IR35331
Version 3.3.1
Page 23 of 93
2.3
SMS Test Cases
2.3.1 Mobile originated and terminated SMS (MS 1(a) GPRS-Attached only / MS 2(a) GPRSAttached 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). 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. Successful result if Short Message is correctly delivered after switching MS2(a) on. 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.
Action:
Result: Comments:
Message flow: Mobile originated and terminated SMS transfer over GPRS channels
IR35331
Version 3.3.1
Page 24 of 93
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 | | | | | | | | |<----|-----------| | | | | | 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 MS 1(a)-GPRS Subscription held in VPLMN(b) Test handling: Preconditions: SGSN(b) in VPLMN(b) contains GPRS-subscription information of MS1(a) and PDPcontext for MS1(a) is activated. HPLMN(a) personal deletes MS1(a) GPRS-subscription from HLR(a) either using HLR`s Man-Machine Interface not via Administrative Data Centre (ADC) input to HLR(a). Successful result if SGSN(b) and GGSN(a) or GGSN(b) record for MS1(a) has been erased and PDP-Context for MS1(a) has been deactivated. This test case confirms that the Cancel Location between HLR(a) and SGSN(b) procedure and PDP Context Deactivation initiated by the network operates correctly.
Action:
Result:
Comments:
HLR-Initiated Detach Procedure (reference 3GPP TS23.060) The HLR-Initiated Detach procedure is initiated by the HLR. The HLR uses this procedure for operatordetermined purposes to request the removal of a subscriber's MM and PDP contexts at the SGSN
IR35331
Version 3.3.1
Page 25 of 93

MS BSS/UTRAN SGSN GGSN HLR
MSC/VLR
2. Detach Request
1. Cancel Location 3. Delete PDP Context Request 3. Delete PDP Context Response C1
5. Detach Accept
4. GPRS Detach Indication
C2 6. Cancel Location Ack 7. PS Signalling Connection Release
2.4.2 Operator Determined Barring for all MS initiated PDP context activatons of MS 1(a). Test handling: Preconditions: Action: SGSN(b) in VPLMN(b) contains subscription information of MS1(a). 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). Successful result if SGSN(b) record for MS1(a) contains ODB information and no PDP-context-activation and SMS-mobile originated attemps are successful. This test case confirms that the ODB procedure for outgoing calls operates correctly.
Result:
Comments:
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 CGPRS 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)
IR35331
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) 4.2 Test Co-ordination contact names, telephone numbers and fax number
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) (ii) (iii) (iv) (v) (vi) (vii) (viii) (ix) 4.3
E212-E214 translation E164 Number range International Gateway Signaling Point Codes SMS Service Centre E164 address SGSN-/GGSN-IP addresses used SGSN-/GGSN Global Title Address used PDP context profiles APNs DNS IP-Addresses
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).
IR35331

(ii) (iii) (iv) (v) (vi)
IMSI MSISDN Basic Service Subscription Information Subscriber data concerning GPRS-attach and GPRS-data-transfer (PDP-context files) Access point names
In order to perform the tests, 3 different SIM-card profiles are required: SIM A: APN Name : This should contain one HPLMNs APN VPLMN allowed = yes SIM B: APN Name : This should contain one HPLMNs 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) (iii) (iv) 4.5 Link carrier and topology Gp interface information Security related information if necessary towards interconnection
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
IR35331
Version 3.3.1
Page 28 of 93

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) GPRS R97/98

IR35331
VPLMN(b) GPRS R97/98

Version 3.3.1
X
Page 29 of 93

GPRS R99/UMTS GPRS R97/98 GPRS R99/UMTS GPRS R97/98 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.
IR35331
Version 3.3.1
Page 30 of 93
A 2.1.1
GPRS-Attach of MS 1(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 MS 1(a) in VPLMN(b)
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.
A 2.2.1
Intranet access of MS 1(a) in VPLMN(b) using home GGSN (user provides Network-ID but no Operator-ID and is not allowed to use visited GGSN) Scenario Serving Network (Internet) SIM to be used HGGSN Intranet SIM B (HLR Subscription: APN1: This should contain one HPLMNs Intranet APN , VPLMN allowed flag = no) Net Id:
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 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) MSISDN of originating MS (i.e.MS1(a)) MS type & software used APN keyed into the MS or Terminal New QoS-Parameter (bit-rate) 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.3
ISP/Internet access of MS 1(a) in VPLMN(b) using visited GGSN (user provides Network-ID and no Operator-ID)
Scenario Serving Network (Internet) SIM to be used
VGGSN ISP/Internet SIM A (HLR Subscription: APN1: This should contain one HPLMNs Internet APN , VPLMN allowed flag = yes) Net Id:
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 IP address Live Net WAP GW Primary Port Secondary Port
Expected Result
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.4
ISP/Internet access of MS 1(a) in VPLMN(b) using home GGSN (user provides Network-ID and no Operator-ID and is not allowed to use visited GGSN)
HGGSN ISP/Internet SIM B (HLR Subscription: APN1: This should contain one HPLMNs Internet APN , VPLMN allowed flag = no) Net Id:
Expected Result
IR35331
Version 3.3.1
Page 34 of 93

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.5
ISP/Internet access of MS 1(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)
HGGSN ISP/Internet SIM B (HLR Subscription: APN1: This should contain one HPLMNs Internet APN , VPLMN allowed flag = no)
IR35331
Version 3.3.1
Page 35 of 93

Expected Result
A 2.3 A 2.3.1
SMS Test Cases Mobile originated and terminated SMS (MS 1(a) GPRS-Attached only / MS 2(a) GPRSAttached 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 A 2.4.1
Operator Control of Service Location cancellation for MS 1(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 MS 1(a) MSISDN of MS1(a) Operator performed barring towards PDPcontext 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
IR35331
Version 3.3.1
Page 37 of 93
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) GPRS R97/98 GPRS R99/UMTS GPRS R97/98 GPRS R99/UMTS
VPLMN(b) GPRS R97/98 GPRS R97/98 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.
IR35331
Version 3.3.1
Page 38 of 93
B 1 Test cases
B 1.1 Mobility Management B 1.1.1 Inter SGSN routing area update of MS 1(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. 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). 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. 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.
Actions:
Result:
Comments:
Message-flow:
IR35331
Version 3.3.1
Page 39 of 93

MS1(a) BSS SGSN 2(b) SGSN1(b)
GGSN
HLR(a)
1. Routeing Area Update Request 2. SGSN Context Request 2. SGSN Context Response 3. Security Functions 4. SGSN Context Acknowledge 5. Forward Packets 6. Update PDP Context Request 6. Update PDP Context Response 7. Update Location 8. Cancel Location 8. Cancel Location Ack 9. Insert Subscriber Data 9. Insert Subscriber Data Ack 10. Update Location Ack 11. Routeing Area Update Accept 12. Routeing Area Update Complete
B 1.1.2 Inter SGSN routing area update of MS 1(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 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). 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.
Actions:
Result:
IR35331

Comments:
This testcase 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) UTRAN SGSN 2(b) SGSN 1(b) GGSN HLR(a)
1. Routeing Area Update Request
2. SGSN Context Request
2a. SRNS Context Request 2a. SRNS Context Response 3. SGSN Context Response 4. Security Functions 5. SGSN Context Ack 6. SRNS Data Forward Command 7. Forward Packets 8. Forward Packets 9. Update PDP Context Request 9. Update PDP Context Response 10. Update Location 11a. Iu Release Command 11a. Iu Release Complete 11. Cancel Location Ack 12. Insert Subscriber Data 12. Insert Subscriber Data Ack 13. Update Location Ack 14. Routeing Area Update Accept 15. Routeing Area Update Complete 11. Cancel Location
B 1.1.3 UMTS to GSM Inter SGSN routing area update of MS 1(a) in VPLMN(b) Inter-System Change Preconditions: MS1(a) is attached to VPLMN(b). MM context is established for MS1(a) in SGSN1(b). PDP context(s) may be active Enable the movement of MS1(a) from a routing area served by SGSN1(b) to a routing area served by SGSN2(b).
Actions:
IR35331
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. This testcase 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.
Comments:
Message-flow:
MS1 (a) BSS UTRAN 2G-SGSN 2(b) 3G-SGSN1 (b) GGSN HLR(a)
1. Intersystem change decision 2. Routing Area Update Request 3. SGSN Context Request 4. SRNS Context Request 4. SRNS Context Response 5. SGSN Context Response 6. Security Functions 7. SGSN Context Acknowledge 8. SRNS Data Forward Command 8a. Forward Packets 9. Forward Packets 10. Update PDP Context Request 10. Update PDP Context Response 11. Update GPRS Location 12. Cancel Location 13. Iu Release Command 13. Iu Release Complete 12. Cancel Location Ack 14. Insert Subscriber Data 14. Insert Subscriber Data Ack 15. Update GPRS Location Ack 16. Routing Area Update Accept 17. Routing Area Update Complete
IR35331
Version 3.3.1
Page 42 of 93
B 1.1.4 GSM to UMTS Inter SGSN routing area update of MS 1(a) in VPLMN(b) Inter-System Change Preconditions: MS1(a) is attached to VPLMN(b). MM context is established for MS1(a) in SGSN1(b). PDP context(s) may be active 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). 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. This testcase 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.
Actions:
Result:
Comments:
Message-flow:
IR35331
Version 3.3.1
Page 43 of 93

MS1 (a) BSS UTRAN 3G-SGSN 2(b) 2G-SGSN1 (b)
GGSN
HLR(a)
1. Intersystem change decision 2. Routing Area Update Request 3. SGSN Context Request 4. SGSN Context Response 5. Security Functions 6. SGSN Context Acknowledge 7. Forward Packets 8. Update PDP Context Request 8. Update PDP Context Response 9. Update GPRS Location 10. Cancel Location 10. Cancel Location Ack 11. Insert Subscriber Data 11. Insert Subscriber Data Ack 12. Update GPRS Location Ack 13. Routing Area Update Accept 14. Routing Area Update Complete
IR35331
Version 3.3.1
Page 44 of 93

B 1.2 GPRS PDP Context Activation by MS 1(a) in VPLMN(b)
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.
B 1.2.1 Intranet access of MS 1(a) in VPLMN(b) using visited GGSN (user provides Network-ID but no Operator-ID)
Test handling:
VPLMN
HPLMN
APN: Intranet
HLR
DNS success
SGSN
DNS
VGGSN
HGGSN
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.
IR35331
Version 3.3.1
Page 45 of 93

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) 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.
Result:
Action: Result:
MS1(a) performs Deactivate PDP Context Request. 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.
IR35331
Version 3.3.1
Page 46 of 93
B 1.2.2 Intranet access of MS 1(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:
VPLMN
APN: I n t r a n e t
HPLM N
HLR
VPLMN add. allowed
SGSN
DNS success
DNS
mnc789.mcc888.gprs (HPLMN)
VGGSN
HGGSN
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 allowed for selected PDP context subscription records MS1(a) performs Activate PDP Context Request. PDP type (R) is sent by MS1(a). A PDP Address is not sent by MS1(a) and is not present in a PDP context subscription record. (Dynamic address allocation)
Action:
IR35331
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. MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated 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)) 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
IR35331
Version 3.3.1
Page 48 of 93
B 1.2.3 Default Intranet/ISP access of MS 1(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:
VPLMN
HPLMN
APN:no APN
HLR SGSN
DNS success
DNS
mnc123.mcc456.gprs(VPLMN)) mnc789.mcc888.gprs (HPLMN)
VGGSN
APN: default APN.mnc123.mcc456.gprs
HGGSN
APN: default APNmnc789.mcc888.gprs
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) MS1(a) performs Activate PDP Context Request.
Action:
IR35331
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. Result: SGSN(b) receives no APN(R). 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. MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated This test case confirms PDP context activation/deactivation towards a visited GGSN(b) 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
IR35331
Version 3.3.1
Page 50 of 93
B 1.2.4 ISP/Internet access of MS 1(a) in VPLMN(b) using home GGSN (user provides NetworkID and HPLMN Operator-ID)
Test handling:
VPLMN
HPLMN
HLR
DNS success
SGSN
DNS
VGGSN
HGGSN
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.

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. 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. MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated 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.
Result:
IR35331
Version 3.3.1
Page 52 of 93
B 1.2.5 ISP/Internet access of MS 1(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:
VPLM N
HPLM N
APN: no APN
HLR SGSN
DNS success
DNS
VGGSN
HGGSN
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)
IR35331
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. 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). 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. 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 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. MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated This test case confirms PDP context activation/deactivation towards a visited GGSN(b) 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
Result:
IR35331
Version 3.3.1
Page 54 of 93
B 1.2.6 ISP/Internet access of MS 1(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:
VPLMN
HPLMN
APN: no APN
HLR SGSN
DNS success
DNS
mnc789.mcc888.gprs (HPLMN)
VGGSN
HGGSN
Precondition:
IR35331
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). 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). 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. 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 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 MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated This test case confirms PDP context activation/deactivation towards a home GGSN(a) 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.
Result:
IR35331
Version 3.3.1
Page 56 of 93
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 MS 1(a) in VPLMN(b) using visited GGSN (user provides NetworkID and Operator-ID, VPLM not allowed) Test handling:
VPLMN
APN:Internet.mnc123.mcc456.gprs
HPLMN
HLR SGSN DNS

mnc123.mcc456.gprs (VPLMN) VPLMN add. Not allowed flag=YES
VGGSN
HGGSN
Precondition:
IR35331
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). 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). SGSN (b) does not allow activating PDP-context for MS1(a). This test case confirms PDP context activation is rejected. Because the user chooses the APN that is specified as VPLMN not allowed Flag
Result: Comment:
B 1.3
3G to 3G Roaming only GPRS PDP Context Activation by MS 1(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 MS 1(a) in VPLMN(b) Subscribed QoS Profile includes Background Traffic Class Test handling:
VPLMN (3G)
HPLMN (3G)
HLR
IR35331
APN:Intranet
VPLMN add. not allowed Version 3.3.1QoS (S) includes Background Traffic Class
Page 58 of 93
Precondition:
MS1(a) is GPRS-Attached in VPLMN(b). (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) performs Activate PDP Context Request. 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) receives APN(R) sent by MS1(a). 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).
Action:
Result:
IR35331
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 MS 1(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:
VPLMN (3G)
HPLMN (3G)
HLR
APN:Intranet
VPLMN add. not allowed QoS (S) includes Interactive Traffic Class and THP of value 1
SGSN
DNS success
IR35331 Version 3.3.1
DNS
Page 60 of 93
Precondition:
MS1(a) is GPRS-Attached in VPLMN(b). (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 Interactive Traffic Class and Traffic Handling Priority of value 1, VPLMN Address is NOT Allowed, NO PDP Address is present (Dynamic Address Allocation). MS1(a) performs Activate PDP Context Request. 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) receives APN(R) sent by MS1(a). 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.
Action:
Result:
IR35331

Comments:
This test case confirms PDP context activation towards a home GGSN(a) using a QoS 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.
IR35331
Version 3.3.1
Page 62 of 93

(b) Traffic Handling Priority is 2 Test handling:
VPLMN (3G)
HPLMN (3G)
HLR
APN:Intranet
SGSN
DNS success
DNS
VGGSN
HGGSN
Precondition:
MS1(a) is GPRS-Attached in VPLMN(b). (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 Interactive Traffic Class and Traffic Handling Priority of value 2, VPLMN Address is NOT Allowed, NO PDP Address is present (Dynamic Address Allocation). MS1(a) performs Activate PDP Context Request. 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.
Action:
IR35331
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. Result: SGSN(b) receives APN(R) sent by MS1(a). 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 010010 for both uplink and downlink traffic. This test case confirms PDP context activation towards a home GGSN(a) using a QoS Profile where the Traffic Class is Interactive and the Traffic Handling Priority is of value 2 (3G to 3G roaming only). VSGSN(b) Diffserv marks uplink Gp traffic with DSCP 010010. HGGSN(a) Diffserv marks downlink Gp traffic with DSCP 010010. 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.
Comments:
IR35331
Version 3.3.1
Page 64 of 93

(c) Traffic Handling Priority is 3 Test handling:
VPLMN (3G)
HPLMN (3G)
HLR
APN:Intranet
SGSN
DNS success
DNS
VGGSN
HGGSN
Precondition:
MS1(a) is GPRS-Attached in VPLMN(b). (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 Interactive Traffic Class and Traffic Handling Priority of value 3, VPLMN Address is NOT Allowed, NO PDP Address is present (Dynamic Address Allocation). MS1(a) performs Activate PDP Context Request. 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.
Action:
IR35331
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. Result: SGSN(b) receives APN(R) sent by MS1(a). 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 001010 for both uplink and downlink traffic. This test case confirms PDP context activation towards a home GGSN(a) using a QoS Profile where the Traffic Class is Interactive and the Traffic Handling Priority is of value 3 (3G to 3G roaming only). VSGSN(b) Diffserv marks uplink Gp traffic with DSCP 001010. HGGSN(a) Diffserv marks downlink Gp traffic with DSCP 001010. 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.
Comments:
IR35331
Version 3.3.1
Page 66 of 93
B 1.3.3 GPRS PDP Context Activation by MS 1(a) in VPLMN(b) Subscribed QoS Profile includes Streaming Traffic Class Test handling:
VPLMN (3G)
HPLMN (3G)
HLR
APN:Intranet
VPLMN add. not allowed QoS (S) includes Streaming Traffic Class
SGSN
DNS success
DNS
VGGSN
HGGSN
Precondition:
MS1(a) is GPRS-Attached in VPLMN(b). (MS1(a) in PMM-IDLE or PMM-CONNECTED state for 3G)

IR35331
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). Action: MS1(a) performs Activate PDP Context Request. 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. 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. Result: SGSN(b) receives APN(R) sent by MS1(a). 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). 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: 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.
Comments:
IR35331
Version 3.3.1
Page 68 of 93
B 1.3.4 GPRS PDP Context Activation by MS 1(a) in VPLMN(b) Subscribed QoS Profile includes Conversational Traffic Class Test handling:
VPLMN (3G)
HPLMN (3G)
HLR
APN:Intranet
VPLMN add. not allowed QoS (S) includes Conversational Traffic Class
SGSN
DNS success
DNS
VGGSN
HGGSN
IR35331
Version 3.3.1
Page 69 of 93
Precondition:
MS1(a) is GPRS-Attached in VPLMN(b). (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 Conversational Traffic Class, VPLMN Address is NOT Allowed, NO PDP Address is present (Dynamic Address Allocation). MS1(a) performs Activate PDP Context Request. 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. 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.
Action:
Result:
SGSN(b) receives APN(R) sent by MS1(a). 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. This test case confirms PDP context activation towards a home GGSN(a) using a QoS Profile where the Traffic Class is Conversational (3G to 3G roaming only).
Comments:
IR35331
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: 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.
B 1.4 MMS Test Cases B 1.4.1 MMS Roaming: Mobile originated and terminated MMS (MS 1(a) / MS 2(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). 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.
Action:
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 (MS 1(b) / MS 2(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). 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.
Action:
Result:
Successful result if Multimedia Message is correctly delivered. If delivery report is requested, check that it is correctly delivered. This test case confirms correct operation of mobile-originated/terminated MMS interworking routing and transfer over GPRS radio channels
Comments:
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 MS 1(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 MS 1(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 MS 1(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 MS 1(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 MS 1(a) in VPLMN(b) 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. B 2.2.1 Intranet access of MS 1(a) in VPLMN(b) using visited GGSN (user provides Network-ID but no Operator-ID) Scenario Serving Network (Internet)
IR35331
VGGSN Intranet

SIM to be used
SIM A (HLR Subscription: APN1: This should contain one HPLMNs Internet APN , VPLMN allowed flag = yes) Net Id:
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 IP address Live Net WAP GW Primary Port Secondary Port
Expected Result
IR35331
Version 3.3.1
Page 75 of 93
B 2.2.2 Intranet access of MS 1(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 Serving Network (Internet) SIM to be used HGGSN Intranet SIM A (HLR Subscription: APN1: This should contain one HPLMNs Internet APN , VPLMN allowed flag = yes) Net Id:
Application to be tested APN keyed into the MS or Terminal Web Settings: Startpage Login Password Primary IP Addresses of Internet DNS Secondary IP Addresses of Internet DNS
Expected Result
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
B 2.2.3 Default Intranet/ISP access of MS 1(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 Serving Network (Internet) SIM to be used 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 VGGSN Defaul Intranet/ISP SIM C (HLR Subscription: * , VPLMN allowed flag = yes)
WAP Settings:
Start page Login Password IP address Live Net WAP GW Primary Port Secondary Port
Expected Result
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
B 2.2.4 ISP/Internet access of MS 1(a) in VPLMN(b) using home GGSN (user provides Network-ID and HPLMN Operator-ID) Scenario Serving Network (Internet) SIM to be used HGGSN Internet SIM A (HLR Subscription: APN1: This should contain one HPLMNs Internet APN , VPLMN allowed flag = yes) Net-Id: Op-Id:
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
Expected Result
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
B 2.2.5 ISP/Internet access of MS 1(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)
VGGSN Internet SIM A (HLR Subscription: APN1: This should contain one PLMNs 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: Start page Login Password Primary IP Addresses of Internet DNS Secondary IP Addresses of Internet DNS
Expected Result
IR35331
Version 3.3.1
Page 79 of 93

B 2.2.6 ISP/Internet access of MS 1(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)
HGGSN Internet SIM A (HLR Subscription: APN1: This should contain one HPLMNs Internet APN , VPLMN allowed flag = yes) Net-Id:
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 IP address Live Net WAP GW

Primary Port Secondary Port
Expected Result
B.2.2.7 ISP/Internet access of MS 1(a) in VPLMN(b) using visited GGSN (user provides NetworkID 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 VSGSN 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 MS 1(a) in VPLMN(b) with different QoS Profiles applied
IR35331
Version 3.3.1
Page 81 of 93
B 2.3.1 GPRS PDP Context Activation by MS 1(a) in VPLMN(b) Subscribed QoS Profile includes Background Traffic Class Scenario Serving Network SIM to be used HGGSN / 3G to 3G Roaming Intranet SIM B (HLR Subscription: This shall contain one HPLMNs APN and VPLMN Address Allowed flag = no) Net Id:
Application to be tested APN keyed into the MS or Terminal 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.
MSISDN of originating MS (i.e.MS1(a)) 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]

Date and Name of Tester
B 2.3.2 GPRS PDP Context Activation by MS 1(a) in VPLMN(b) Subscribed QoS Profile includes Interactive Traffic Class
(a)
Traffic Handling Priority = 1 Scenario Serving Network SIM to be used HGGSN / 3G to 3G Roaming Intranet SIM B (HLR Subscription: This shall contain one HPLMNs APN and VPLMN Address Allowed flag = no) Net Id:
Application to be tested APN keyed into the MS or Terminal 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
MSISDN of originating MS (i.e.MS1(a)) MS type & software used Time of PDP-context activation (hh:mm:ss) Application usage successful?

DSCP of uplink Gp traffic is 011010? DSCP of downlink Gp traffic is 011010? 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] Date and Name of Tester (b) Traffic Handling Priority = 2 Scenario Serving Network SIM to be used
HGGSN / 3G to 3G Roaming Intranet SIM B (HLR Subscription: This shall contain one HPLMNs APN and VPLMN Address Allowed flag = no)
Application to be tested APN keyed into the MS or Terminal 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 Net Id:
Expected Result
IR35331
The tunnel shall be opened, the application shall work successfully and

DSCP of Gp traffic shall be 010010.
MSISDN of originating MS (i.e.MS1(a)) MS type & software used Time of PDP-context activation (hh:mm:ss) Application usage successful? DSCP of uplink Gp traffic is 010010? DSCP of downlink Gp traffic is 010010? 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] Date and Name of Tester
(c)
Traffic Handling Priority = 3 Scenario Serving Network SIM to be used HGGSN / 3G to 3G Roaming Intranet SIM B (HLR Subscription: This shall contain one HPLMNs APN and VPLMN Address Allowed flag = no)
Application to be tested APN keyed into the MS or Terminal Web Settings: Startpage Login Password Primary IP Addresses of Internet DNS Secondary IP Addresses of Internet DNS WAP Settings: Startpage
Net Id:

Login Password IP address Live Net WAP GW Primary Port Secondary Port
Expected Result
MSISDN of originating MS (i.e.MS1(a)) MS type & software used Time of PDP-context activation (hh:mm:ss) Application usage successful? DSCP of uplink Gp traffic is 001010? DSCP of downlink Gp traffic is 001010? 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] Date and Name of Tester
B 2.3.3 GPRS PDP Context Activation by MS 1(a) in VPLMN(b) Subscribed QoS Profile includes Streaming Traffic Class Scenario Serving Network SIM to be used HGGSN / 3G to 3G Roaming Intranet SIM B (HLR Subscription: This shall contain one HPLMNs APN and VPLMN Address Allowed flag = no)
Application to be tested APN keyed into the MS or Terminal Net Id:
IR35331
Version 3.3.1
Page 86 of 93

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.
MSISDN of originating MS (i.e.MS1(a)) MS type & software used Time of PDP-context activation (hh:mm:ss) Application usage successful? DSCP of uplink Gp traffic is 100010? DSCP of downlink Gp traffic is 100010? Measured QoS parameters within target? 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] Date and Name of Tester
B 2.3.4 GPRS PDP Context Activation by MS 1(a) in VPLMN(b) Subscribed QoS Profile includes Conversational Traffic Class Scenario Serving Network SIM to be used
IR35331
HGGSN / 3G to 3G Roaming Intranet SIM B (HLR Subscription: This shall contain one HPLMNs APN and VPLMN Address Allowed

flag = no) Application to be tested APN keyed into the MS or Terminal Net Id:
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.
MSISDN of originating MS (i.e.MS1(a)) MS type & software used Time of PDP-context activation (hh:mm:ss) Application usage successful? DSCP of uplink Gp traffic is 101110? DSCP of downlink Gp traffic is 101110? Measured QoS parameters within target? 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] Date and Name of Tester
B 2.4 MMS Test Cases B 2.4.1 MMS Roaming: Mobile originated and terminated MMS (MS 1(a) / MS 2(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 (MS 1(b) / MS 2(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
IR35331
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) GPRS R97/98 GPRS R99/UMTS GPRS R97/98 GPRS R99/UMTS VPLMN(b) GPRS R97/98 GPRS R97/98 GPRS R99/UMTS GPRS R99/UMTS
The Services tested were:GPRS attach only GPRS PDP context activation Short Message Services Operator Control of Service [Pass / Fail / Not applicable].................... [Pass / Fail / Not applicable].................... [Pass / Fail / Not applicable].................... [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...................................................................... of PLMN.....................
IR35331 Version 3.3.1
Date...........................................
Page 92 of 93

Signed......................................................................
of PLMN.....................
Date...........................................
End Of Appendix C
IR35331
Version 3.3.1
Page 93 of 93

Ir 35

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ir 35

Uploaded by

Copyright:

Available Formats

GSM Association Permanent Reference Document: IR 35

GSM Association Classifications

GSM Association Permanent Reference Document: IR 35

0.0.7 0.0.8 0.0.9 1.0.0 2.0.0 2.1.0 3.0.0 3.0.1 3.0.2

24.02.2000 01.03.2000 03.03.2000 14.03.2000 15.03.2000 29.03.2000 28.04.2000 23.06.2000 30.08.2000

3.0.3 3.0.4 3.0.5 3.0.6 3.0.7 3.1.0 3.1.1 3.1.2

05.09.2000 23.11.2000 05.01.2001 01.03.2001 21.08.2001

3.2.0 3.3.0 3.3.1

20.03.02 20.08.2002 11.02.2003

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

2.1 2.1.1 2.2 2.2.1

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

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

GSM Association Permanent Reference Document: IR 35

APPENDIX B (OPTIONAL TESTS)............................................................................................................... 38 B 1 TEST CASES .......................................................................................................................................... 39

GSM Association Permanent Reference Document: IR 35

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

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

Strategy for Testing

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

MS 1 SIM(a) ROOT DNS HLR / SGSN

M / GGSN LOCAL DNS LOCAL DNS INTRANET/ISP INTRANET/ISP

GSM Association Permanent Reference Document: IR 35

Message-flow: (GPRS Attach only)

GSM Association Permanent Reference Document: IR 35

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

5b. Inser Subscriber Data

5dUpdate Location Ack

8. Attach Accept 9. Attach Complete

QoS Profile for R99 MS1(a):

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

MS1(a) performs Deactivate PDP Context Request. PDP-Context is deactivated

Message-flow: (Update PDP Context Request Procedure)

1. Insert Subscriber Date (QoS-Negotiation) 2. Insert Subscriber Date Ack

GSM Association Permanent Reference Document: IR 35

VPLMN add. allowed flag=YES

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

Action: Result: Comments:

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

Action: Result: Comments:

GSM Association Permanent Reference Document: IR 35

SMS Test Cases

GSM Association Permanent Reference Document: IR 35

Operator Control of Service

GSM Association Permanent Reference Document: IR 35

4. GPRS Detach Indication

C2 6. Cancel Location Ack 7. PS Signalling Connection Release

3 Equipment Requirements 3.1 User Equipment

spare cards in case of failure

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

GSM Association Permanent Reference Document: IR 35

HPLMN(a) GPRS R97/98