GSM Association Official Document TD.

46

TAP Test Cases (TTC) for CAMEL Phase 1, Phase 2 and Phase 3 Services 3.5 22 May 2008
This is a binding permanent reference document of the GSM Association.

Security Classification: This document contains GSMA Confidential Information

Access to and distribution of this document is restricted to the persons listed under the heading Security Classification Category. This document is confidential to the Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those listed under Security Classification Category without the prior written approval of the Association. The GSM Association (Association) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document. The information contained in this document may be subject to change without prior notice.

Security Classification CONFIDENTIAL GSMA Material

Confidential Confidential Confidential Confidential

GSMA GSMA GSMA GSMA

Full Members Associate Members Rapporteur Members Parent Company Members

X X X X

Copyright Notice
Copyright 2009 GSM Association

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

107235734.doc

Page 1 of 27

GSM Association Official Document TD.46

Table of Contents ........................................................................................................................1 TAP Test Cases (TTC) for CAMEL Phase 1, Phase 2 and Phase 3 Services......1 3.5...................................................................................................................1 22 May 2008....................................................................................................1 1 Introduction.................................................................................................. 3 1.1 Scope of Document...................................................................................3 1.2 Document Cross References.....................................................................3 1.3 Abbreviations.............................................................................................3 2 TAP Test Cases (TTCs)...............................................................................6 Parameters:.....................................................................................................6 3 TAP Test Case Cross Reference Tables....................................................7 Description TTC Cross Reference Table Contents........................................7 3.1 Structure of TTC Cross Reference Tables................................................7 4 TTC............................................................................................................... 8 4.1 CAMEL Phase 1 Test cases .....................................................................8 1.1.1 Basic Service TTCs...............................................................................8 1.1.2 Supplementary Service and ODB TTCs................................................9 4.2 CAMEL Phase 2 Testcases.....................................................................10 1.1.3 Basic Service TTCs.............................................................................10 1.1.4 Supplementary Service and ODB TTCs..............................................13 1.1.5 MO SMS Control.................................................................................14 1.1.6 GPRS Control......................................................................................16 1.1.7 Mobility Management...........................................................................19 The TAP Test Report for CAMEL Phase 1, Phase 2 and Phase 3 Services20 ANNEX A TAP Test Report....................................................................... 20 5 DOCUMENT MANAGEMENT.....................................................................26

107235734.doc

Page 2 of 27

GSM Association Official Document TD.46

1 INTRODUCTION
1.1 Scope of Document
This document specifies the TAP Test Cases (TTC) for CAMEL Phase 1, Phase 2 and Phase 3 Services that have to be executed by the Roaming Partner under test, in its quality of VPMN, as applicable and in accordance to the TAP Testing Procedures defined by TADIG PRD TD.41, Testing the Transferred Account Procedure (TAP). Note that TD.41 also defines the scope, the different scenarios to test the TAP and the use of administrative documents required for testing the TAP. Furthermore, the usage of TAP Testing Tools (e.g. TAP Testing Toolkit TTT) will be handled there, too. Accordingly, these matters are out of the scope of this document. Furthermore, note that this document is subordinate to the IREG PRD IR.32, which means the IREG terms (e.g. numbering of test cases, abbreviations, performed test cases) will be the same. To simplify the editorial work and differentiate between the TAP release specific information, separate sections for the each TAP release will be available, as applicable. Appendix A defines the recommended TAP Test Report for CAMEL Phase 1, Phase 2 and Phase 3 Services to be compiled and provided by the Roaming Partner under test, in its quality of VPMN, to the Roaming Partner, in its quality of HPMN, during the execution of the TAP Testing Procedure. Finally, note that TAP Test Cases related to other services will be handled in different TADIG PRDs.

1.2

Document Cross References

Title End-to-End Functional Capability Specification for Inter-PLMN CAMEL Roaming (CAMEL Phase 1, Phase 2 and Phase 3) Testing the Transferred Account Procedure Transferred Account Procedure Data Record Format Specification

PRD Number GSM Association PRD IR.32 GSM Association PRD TD.41 GSM Association PRD TD.57

1.3
AAC AACx ABT AC ACR ANM AoCI

Abbreviations
Automatic Answering Circuit destination Number of Announcement x TCAP-Abort CAP-Apply Charging CAP-Apply Charging Report ISUP-Answer Advice of Charge Information Page 3 of 27

107235734.doc

GSM Association Official Document TD.46 ARI AT ATI CAMEL CAP CC CIRep CIReq CON CPD CTR CUE DFC DN(c) DRA EDP ERB ETC FCI FTN GMSC HLR HPMN IAM IDP IMSC IR ISD MS PMN(b) MSIN NDC O-CSI ODB OR PA PMN ("Network PSI PSTN country b. RC REL RIDE RRBE SCF SCI SCP SoA SRF SRR SS TAP CAP-Assist Request Instructions CAP-Activity Test Any Time Interrogation Customised Applications for Mobile networks using Enhanced Logic CAMEL Application Part Country Code CAP-Call Information Report CAP-Call Information Request CAP-Connect max Call Period Duration CAP-Connect To Resource CAP-Continue CAP-Disconnect Forward Connection Destination Number which is located in country(c) Destination Routing Address Event Detection Point Event Report BCSM CAP-Establish Temporary Connection CAP-Furnish Charging Info Forwarded To Number Gateway Mobile Services Switching Centre. Home Location Register. Home PMN ISUP-Initial Address Message CAP-Initial DP Interrogating MSC International Roaming Insert Subscriber Data Mobile Station MS(b) indicates that the MS subscription is managed by Mobile Subscriber Identification Number Network Destination Code Originating CAMEL Subscription Information. Operator Determined Barring. Optimal Routing CAP-Play Announcement Public Mobile Network including RSS ("Radio Sub-System") and NSS Sub-System") PMN(a) indicates the "ath" PMN. MAP-ProvideSubscriberInformation Public Switched Telephone Network; PSTN(b) indicates a PSTN telephone in CAP-Release Call ISUP-Release Release If Duration Exceeded CAP-Request Report BCSM Event Service Control Function CAP-Send Charging Info Service Control Point Suppression of Announcement Specialized Resource Function CAP-Specialized Resource Report Supplementary Services Transferred Account Procedure Page 4 of 27

107235734.doc

GSM Association Official Document TD.46 TINTS TS TSI TSLTS VMSC entities Time If No Tariff Switch Tariff Switch Tariff Switch Interval Time since Last Tariff Switch Visited Mobile Services Switching Centre, including the always co-located

MSC ("Mobile Services Switching Centre") and VLR ("Visitor Location Register"). VPMN Visited PMN.

107235734.doc

Page 5 of 27

GSM Association Official Document TD.46

2 TAP TEST CASES (TTCS)

Parameters:
PMN(A) PMN(B) MS1(A), MS2(A) HMSC VMSC PSTN telephone (B), (B1), (B2) PSTN telephone (A) PSTN telephone not PMN (A), not PMN (B) Home PMN of MS1(A) and MS2(A) Visited PMN of MS1(A) and MS2(A) Mobile Subscribers from HPMN(A) roaming in the VPMN(B) HPMNs Mobile Switching Centre VPMNs Mobile Switching Centre PMN(B)s PSTN telephones PMN(A)s PSTN telephone PSTN telephones belonging not to the PMN(A) nor the PMN(B)

107235734.doc

Page 6 of 27

GSM Association Official Document TD.46

3 TAP TEST CASE CROSS REFERENCE TABLES Description TTC Cross Reference Table Contents
The below listed Cross Reference tables briefly define the raised Call Event Details for CAMEL Phase 1, Phase 2 and Phase 3 Services TAP Test Cases (TTC). The TTC description and the TTC numbering will be taken over from the already existing IREG terms as mentioned in the scope of the document. The subcoding (in alphabetical order) will identify the raised Call Event Details. Please note that the tables will just outline expected data on Call Event Details Level. More detailed information about Groups, Single Fields, and Sub Single Fields will be available in the applicable version of TD57. The Conditionality of the raised Call Event Details will be as following: Conditionality Mandatory Conditional Abbreviation M C Explanation Must be present. In general, must be present. However in certain circumstances the element may not occur because the particular circumstance is not relevant or the information is not available (e.g. from the network). Does not need to be present. Inclusion/exclusion of optional elements is at the discretion of the Sender PMN, no specific agreements need to be in place to allow the PMN to include these elements. Must NOT be transferred on the TAP. For further study.

Optional

Not applicable Further Study

N F

3.1
TTC

Structure of TTC Cross Reference Tables

TTC description Test Chain Table Brief scenario description of part 1 of test chain Brief scenario description of part 2 of test chain (a) (b) Call Event Details to be raised on TAP Conditionality Data expected Conditionality Data expected

Subcode

Appendix A TTC TESTING PARAMETERS details additional testing information, performance and comments of TTCs.

107235734.doc

Page 7 of 27

GSM Association Official Document TD.46

4 TTC
4.1
1.1.1

CAMEL Phase 1 Test cases

Basic Service TTCs Location Update by MS1(a) in VPMN(b) Test Chain Table Call Event Details to be raised on TAP N Power-up MS1(a) and perform location registration on VPMN(b).

B2.1.1.1 Subcode (a)

B 2.1.1.2 Subcode (a)

Location Update by MS2(a) in VPMN(b) Test Chain Table Call Event Details to be raised on TAP N Power-up MS2(a) and perform location registration on VPMN(b).

B 2.1.2 Subcode (a)

Check operation of IDP and CON Test Chain Table Call Event Details to be raised on TAP MS1(a), registered in VPMN(b), makes a call to M TestNbr1 MOC[MS1(A)] Check operation of PSI. Test Chain Table Call Event Details to be raised on TAP MS1(A) calls subscriber MS2(A), both registered in M MOC[MS1(A)] VPMN (B) MS2(A) receives call from MS1(A) M MTC[MS2(A)] Check reporting of EDP O_Answer and operation of RC Test Chain Table MS1(A), registered in VPLMN(b), makes a call to TestNbr2. 10 seconds after Test Announcement 3 is connected to calling party, the call is released from SCP. Call Event Details to be raised on TAP M MOC[MS1(A)]

B 2.1.3 Subcode (a) (b)

B 2.1.4 Subcode (a)

107235734.doc

Page 8 of 27

GSM Association Official Document TD.46 B 2.1.5 Subcode (a) Check operation of CUE Test Chain Table MS1(A) calls MS3(b), both registered in VPMN(B) MS3(b) receives call from MS1(A). MS3 (b) disconnects the call. Call Event Details to be raised on TAP M MOC[MS1(A)] N No Record on TAP

(b)

B 2.1.6.1 Subcode (a)

Check default call handling; default call handling set to continue call Test Chain Table MS1(A) calls AAC1; call successful (test announcement 1 played) Call Event Details to be raised on TAP M MOC[MS1(A)]

B 2.1.6.2 Subcode (a)

Check default call handling; default call handling set to release call Test Chain Table MS1(A) calls AAC2; call not successful (test announcement 2 not played) Call Event Details to be raised on TAP N No Record on TAP

B 2.1.7 Subcode (a)

Check Suppression of Announcement Test Chain Table MS2(A) takes battery off in order to provoke unsuccessful call establishment detected in VMSC. MS3(B) attempts a call to MS2(a). Call Event Details to be raised on TAP N No Record on TAP N No Record on TAP

(b)

1.1.2

Supplementary Service and ODB TTCs Call Forward on No Reply [CFNRy]; Test Chain Table MS1(A) registers and activates CFNRy to destination number MS3(b) calls MS1(A). MS1(a) does NOT answer the call and MS3(b) waits until NoAnswer timer expires Call Event Details to be raised on TAP O SS[MS1(A)] M MTC[MS1(A)]

B2.1.8.1 Subcode (a) (b)

107235734.doc

Page 9 of 27

GSM Association Official Document TD.46 (c) CFNRy is invoked for MS1(A). The call is forwarded to destination number MOC[MS1(A)] M OFFLINE: SS[MS1(A)] INLINE: see note 1 M

(d)

B 2.1.8.2 Subcode (a) (b)

Barring of Outgoing International Calls Except to HPMN Country [BOICexHC] Test Chain Table Call Event Details to be raised on TAP MS1(A) activates BOIC-exHC O SS[MS1(A)] MS1(A) attempts a call to TestNbr3. The SCF N No Record on TAP alters the destination address to be that of destination number not located in HPMN's Country.

B 2.1.8.3 Subcode (a)

ODB: Barring of Outgoing International Calls Except to HPMN Country [ODB-BOIC exHC] Test Chain Table Call Event Details to be raised on TAP MS2(A) attempts a call to TestNbr3. The SCF N No Record on TAP alters the destination address to be that of destination number not located in HPMN's Country.

4.2
1.1.3

CAMEL Phase 2 Testcases

Basic Service TTCs Location Update by MS4(a) in VPMN(b) Test Chain Table Call Event Details to be raised on TAP N Power-up MS4(a) and perform location registration No Record on TAP on VPMN(b). Location Update by MS5(a) in VPMN(b) Test Chain Table Call Event Details to be raised on TAP N Power-up MS5(a) and perform location registration No Record on TAP on VPMN(b).

B 2.2.1.1 Subcode (a)

B 2.2.1.2 Subcode (a)

: In case of INLINE description no SS Call Event Detail will be applicable. The SS information will be transferred in the (e) part MOC[MS1(A)] of the test chain.

107235734.doc

Page 10 of 27

GSM Association Official Document TD.46 B 2.2.2.1 Subcode (a) Check Operation of IDP and DP2 Criteria _ Called Number of Length within Destination Number Length List Test Chain Table Call Event Details to be raised on TAP MS4(a), registered in VPMN(b), makes a call to MOC[MS4(A)] M TestNbr4 Check Operation of IDP and DP2 Criteria _ Called Number Length not Defined by Destination Number Length List Test Chain Table Call Event Details to be raised on TAP MS4(a), registered in VPMN(b), makes a call to MOC[MS4(A)] M AAC4

B 2.2.2.2 Subcode (a)

B 2.2.3 Subcode (a) (b) B 2.2.4 Subcode (a)

Check Operation of PSI Test Chain Table Call Event Details to be raised on TAP MS5(a) makes a call to MS4(a), both registered in MOC[MS5(A)] M VPMN(b) MS4(a) receives call from MS5(a) MTC[MS4(A)] M Check reporting of EDP O_Answer, O_Disconnect and operation of RC Test Chain Table Call Event Details to be raised on TAP MS4(a), registered in VPLMN(b), makes a call to MOC[MS4(A)] M TestNbr11. 10 seconds after Test Announcement 3 is connected to calling party, the call is released from SCP. Check operation of CUE and FCI with Follow-On Call due to Called Party does not Reply Test Chain Table Call Event Details to be raised on TAP MS5(a) makes a call to a MS 3(b), which is located MOC[MS5(a)] M in the VPMN(b). MS3(b) receives call from MS5(b). MS3(b) does not No Record on TAP N answer the call. Check operation of CUE and FCI with Follow-On Call due to Called Party is busy" (optional) Test Chain Table Call Event Details to be raised on TAP MS5(a) makes a call to a MS 3(b), which is located MOC[MS5(a)] M in the VPMN(b) and rendered busy. MS3(b) receives call from MS5(b). MS3(b) is No Record on TAP N engaged in a call.

B 2.2.5.1 Subcode (a) (b)

B 2.2.5.2 Subcode (a) (b)

107235734.doc

Page 11 of 27

GSM Association Official Document TD.46 B 2.2.5.3 Subcode (a) (b) Check operation of CUE and FCI with Follow-On Call due to Called Party is NotReachable" (optional) Test Chain Table Call Event Details to be raised on TAP MS5(a) makes a call to a MS 3(b), which is located MOC[MS5(a)] M in the VPMN(b) and switched off (explicitly detached). MS3(b) receives call from MS5(b). MS3(b) is No Record on TAP N switched off. Check operation of CUE and FCI with Follow-On Call due to RouteSelectFailure" by "Release before Answer" (optional) Test Chain Table Call Event Details to be raised on TAP MS5(a) attempts a call to a number range of VPMN MOC[MS5(a)] M B.

B 2.2.5.4 Subcode (a)

B 2.2.6.1 Subcode (a)

(b)

Check Operation of CIReq, SCI and AC, Check correct reporting of call periods (1) Test Chain Table Call Event Details to be raised on TAP MS4(a), registered in VPMN(b), makes a call to MOC[MS4(a)] M TestNbr5 and is connected to Test Announcement 5 (AAC5). AAC5 disconnects the call after 30 seconds. Depending on correct reporting of call periods, MOC[MS4(a)] M either Test Announcement 1 (AAC1) or Test Announcement 2 (AAC2) is played. Check Operation of CIReq, SCI and AC, Check reporting of call periods (2) Test Chain Table Call Event Details to be raised on TAP MS4(a), registered in VPMN(b), makes a call to MOC[MS4(a)] M TestNbr7 and is connected to Test Announcement 5 (AAC5). AAC5 disconnects the call after 30 seconds. Depending on correct reporting of the call periods MOC[MS4(a)] M either Test Announcement 1 (AAC1) or Test Announcement 2 (AAC2) is played

B 2.2.6.2 Subcode (a)

(b)

B 2.2.6.3

Check warning tone and automatic call release Call Event Details to be raised on TAP MS4(a), registered in VPMN(b), makes a call to MOC[MS4(a)] C TestNbr6 and is connected to Test Announcement 3 (AAC3). Page 12 of 27

Subcode Test Chain Table (a)

107235734.doc

GSM Association Official Document TD.46 Check if a warning tone is played to calling party after about 10 seconds B 2.2.7 Subcode (a) Check operation of ETC and DFC Test Chain Table Call Event Details to be raised on TAP C MS4(a) attempts a call to TestNbr10; and is MOC[MS4(a)] connected to an IN Announcement located in Assisting SSF (a). Test Announcement 1 (AAC1) is played to calling party

B 2.2.8.1 Subcode (a)

Check Default Call Handling - defaultCallHandling set to continueCall Test Chain Table Call Event Details to be raised on TAP M MS5(a) attempts a call to AAC1; Successful result MOC[MS5(a)] if Test Announcement 1 is played to calling party Check Default Call Handling - defaultCallHandling set to releaseCall Test Chain Table Call Event Details to be raised on TAP N MS6(a) attempts a call to AAC2; Successful result No Record on TAP if call is NOT established and Test Announcement 2 is NOT played to calling party. Check Suppression Of Announcement Test Chain Table Call Event Details to be raised on TAP N MS5(a) takes battery off in order to provoke No Record on TAP unsuccessful call establishment detected in VMSC. No Record on TAP N MS3(b) attempts a call to MS5(a)

B 2.2.8.2 Subcode (a)

B 2.2.9 Subcode (a) (b) 1.1.4

Supplementary Service and ODB TTCs

B 2.2.10.1 Subcode (a) (b)

Check Operation of SS-SCI, MRTY Test Chain Table Call Event Details to be raised on TAP M MS4(a) makes a call to TestNbr12 and places the MOC[MS4(a)] call on hold. M MS4(a) then initiates a call to Testnbr13 and MOC[MS4(a)] invokes a Multi Party call

107235734.doc

Page 13 of 27

GSM Association Official Document TD.46

B 2.2.10.2 Subcode (a) (b)

Call Forwarding on no reply (CFNRy) Test Chain Table Call Event Details to be raised on TAP MS5(a) has activated Call Forwarding on No Reply SS[MS5 (A)] O to Test Announcement 3. MS3(b) attempts a call to MS5(a). MS5(a) does MTC[MS5 (A)] M NOT answer the call and MS3(b) waits until NoAnswer timer expires CFNRy is invoked for MS5 (A) OFFLINE: SS[MS5 (A)] M 1 INLINE: see note The call is forwarded to destination number MOC[MS5 (A)] M Barring of outgoing international calls except to HPLMN country Test Chain Table Call Event Details to be raised on TAP MS4(a) activates BOIC-exHC. MS4(a) has SS[MS4 (A)] O activated Barring of outgoing international calls except those directed to the HPLMN country N MS4(a) attempts a call to TestNbr9. The SCF No Record on TAP alters the destination address to be that of destination number located in country(c), DN(c). ODB: Barring of outgoing international calls except to HPLMN country (ODBBOICexHC) Test Chain Table Call Event Details to be raised on TAP N MS5(a) attempts a call to TestNbr9. The SCF No Record on TAP alters the destination address to be that of destination number located in country(c), DN(c).

(c) (d)

B 2.2.10.3 Subcode (a) (b)

B 2.2.10.4 Subcode (a)

4.3 CAMEL Phase 3 Testscases

1.1.5 MO SMS Control Location Update by MS7(a) in VPMN(b) Test Chain Table Call Event Details to be raised on TAP N Power-up MS7(a) and perform location registration No Record on TAP on VPMN(b). Location Update by MS8(a) in VPMN(b) Test Chain Table Call Event Details to be raised on TAP N Power-up MS8(a) and perform location registration

B2.3.1.1.1 Subcode (a)

B 2.3.1.1.2 Subcode (a)

1

In case of INLINE description no SS Call Event Detail will be applicable. The SS information will be transferred in the (e) part MOC[MS5 (A)] of the test chain.

107235734.doc

Page 14 of 27

GSM Association Official Document TD.46 on VPMN(b). Check operation of IDP_SMS and CON_SMS Test Chain Table Call Event Details to be raised on TAP MS8(a) sends a SM to MS7(a) using TestNbr14 as MOC[MS8(a)] M SMSC Address. Depending on InitialDPSMS content the SM is forwarded to either MS 7(a) or MS8(a) with a modified Calling Party and a modified SMSC-Address. Successful result if MS8(a) receives the SM sent MTC[MS8(a)] M previously from MS8(a). Check operation of REL_SMS Test Chain Table Call Event Details to be raised on TAP MS7(a) sends a SM to MS8(a) using HPMN_SMSC N as SMSC Address. Successful result if the SM is No Record on TAP Not sent. Check DefaultSMSHandling set to continue Test Chain Table Call Event Details to be raised on TAP MS7(a) sends a SM to itself. SCP does not answer MOC[MS7(a)] M to InitialDPSSMS. The Default SMS Handling of MS7(a) equals continue MS7(a) receives a SM from itself MTC[MS7(a)] M Check DefaultSMSHandling set to release Test Chain Table Call Event Details to be raised on TAP MS8(a) sends a SM to itself. SCP does not answer No Record on TAP N to InitialDPSSMS. The Default SMS Handling of MS7(a) equals release. Successful result if SM is Not sent Check Operation of RR_SMS_Event, CUE_SMS and ER_SMS Test Chain Table Call Event Details to be raised on TAP MS8(a) sends a SM to MS3(b) using HPMN_SMSC MOC[MS8(a)] M as SMSC Address MS3(b) receives a SM from MS8(a) MTC[MS3(b)] M If HPMN has indicated that SCF-initiated SMS is MTC[MS8(a)] O used MS8(a) receives a SM : SMS_Submitted. No Record on TAP

B 2.3.1.2 Subcode (a)

(b)

B 2.3.1.3 Subcode (a)

B2.3.1.4.1 Subcode (a) (b) B 2.3.1.4.2 Subcode (a)

B 2.3.1.5 Subcode (a) (b) (c)

107235734.doc

Page 15 of 27

GSM Association Official Document TD.46 Barring of outgoing international calls except to HPMN country for SMS (BOICexHC) (optional) Subcode Test Chain Table Call Event Details to be raised on TAP (a) MS7(a) sends a SM to itself using TestNbr16 as No Record on TAP N SMSC Address; successful result if the SM transmission is barred (b) If HPMN has indicated that SCF-initiated SMS is MTC[MS7(a)] O used MS7(a) receives a SM : SMS_Failure. B 2.3.1.6 1.1.6 GPRS Control 1.1.6.1 GPRS - Attach GPRS Attach by MS7(a) in VPMN (b) (GPRS Attach only) B 2..3.2.1.1 Subcode (a) Test Chain Table Call Event Details to be raised on TAP N Power-up MS7(a) and perform GPRS Attach only No Record on TAP on VPMN (b) GPRS Attach by MS8(a) in VPMN (b) (GPRS Attach only) Test Chain Table Call Event Details to be raised on TAP N Power-up MS8(a) and perform GPRS Attach only No Record on TAP on VPMN (b) Check used volume, 2 PDP context periods, tariffSwitch after PCD Test Chain Table Call Event Details to be raised on TAP M MS7(a), GPRS attached in VPMN (b), sets up a GPRS Call [MS7(a)] PDP context to TestAPN1 and is connected to TestServer1. MS7(a) transfers data using a service provided by HPMN(a). Successful result if data transfer is released after 5000+500 byte Check used volume, 3 PDP context periods, tariffSwitch in 2nd period Test Chain Table Call Event Details to be raised on TAP M MS7(a), GPRS attached in VPMN (b), sets up a GPRS Call [MS7(a)] PDP context to TestAPN2 and is connected to TestServer1. MS7(a) transfers data using a service provided by HPMN(a). Successful result if data transfer is released after 30.000+300 byte Check used Time, 2 PDP context periods, tariffSwitch in 1st period Test Chain Table Call Event Details to be raised on TAP Page 16 of 27

B 2.3.2.1.2 Subcode (a)

B 2.3.2.2.1 Subcode (a)

B 2.3.2.2.2 Subcode (a)

B 2.3.2.2.3 Subcode

107235734.doc

GSM Association Official Document TD.46 (a) MS7(a), GPRS attached in VPMN (b), sets up a GPRS Call [MS7(a)] PDP context to TestAPN3 and is connected to TestServer1. MS7(a) transfers data using a service provided by HPMN(a). Successful result if data transfer is released after 15+2 seconds Check used Time, 3 PDP context periods, tariffSwitch in 2nd period Test Chain Table Call Event Details to be raised on TAP M MS7(a), GPRS attached in VPMN (b), sets up a GPRS Call [MS7(a)] PDP context to TestAPN4 and is connected to TestServer1. MS7(a) transfers data using a service provided by HPMN(a). MS7(a) disconnects the PDP context after 30 seconds. Successful result if PDP context remains active for more than 20 seconds. Parallel GPRS dialogues using GPRS CAMEL Scenario 2 (optional) Test Chain Table Call Event Details to be raised on TAP MS7(a), GPRS attached in VPMN (b), sets up a GPRS Call [MS7(a)] for PDP M GPRS dialogue to TestAPN5 which is connected Context 1, to TestServer1 and a second GPRS dialogue to TestAPN6 which is connected to TestServer2. GPRS Call [MS7(a)] for PDP M MS7(a) transfers data using a service provided by Context 2, HPMN(a) within PDP Context 1 & PDP Context 2. Successful result if both GPRS dialogues are released after transmission of 15.000 + 1500 byte in total. M

B 2.3.2.2.4 Subcode (a)

B 2.3.2.2.5 Subcode (a)

1.1.6.2

CAMEL scenario 1 Parallel PDP contexts using GPRS CAMEL Scenario 1 (optional) B 2.3.2.3.1 Subcode (a) Test Chain Table Call Event Details to be raised on TAP MS8(a), GPRS attached in VPMN (b), sets up one GPRS Call [MS8(a)] for PDP M PDP context to TestAPN7 which is connected to Context 1, TestServer1 and a second PDP context to TestAPN8 which is connected to TestServer2. GPRS Call [MS8(a)] for PDP M MS8(a) transfers data using a service provided by Context 2, HPMN(a) within PDP Context 1 & PDP Context 2. Successful result if both PDP contexts are released after transmission of 15.000 + 1500 byte. If HPMN has indicated that SCF-initiated SMS is MTC[MS8(a)] C used MS8(a) receives an appropriate SM.

(b)

107235734.doc

Page 17 of 27

GSM Association Official Document TD.46 B 2.3.2.3.2 Subcode (a) Check Default GPRS handling set to continue Test Chain Table Call Event Details to be raised on TAP M MS8(a), GPRS attached in VPMN (b), sets up a GPRS Call [MS8(a)] PDP context to TestServer1. SCF responds to ERgprs(PCEack) with TCAP Abort. The defaultGPRShandling of MS8(a) equals continue. Successful result if the PDP context is established

B 2.3.2.4.1 Subcode (a)

Check Default GPRS handling set to release within CAMEL Scenario 2, Abort during PDP context establishment Test Chain Table Call Event Details to be raised on TAP N MS7(a), GPRS attached in VPMN (b), attempts to No Record on TAP set up a PDP context to TestServer1. SCF responds to ERB(PCEack) with TCAP Abort. The defaultGPRShandling of MS7(a) equals release. Successful result if the PDP context is NOT established and MS7(a) is NOT connected to TestServer1.

B 2.3.2.4.2 Subcode (a)

Check Default GPRS handling set to release within CAMEL Scenario 2, Abort during active PDP context Test Chain Table Call Event Details to be raised on TAP M MS7(a), GPRS attached in VPMN (b), attempts to GPRS Call [MS7(a)] set up a PDP context to TestServer1. SCF sends TCAP Abort 10 seconds after PDP context is established. The defaultGPRShandling of MS7(a) equals release. Successful result if the PDP context is disconnected after 10 + seconds

B 2.3.2.5 Subcode (a)

Check correct operation of EntityReleasedGPRS procedure (Optional) Test Chain Table Call Event Details to be raised on TAP M MS7(a), GPRS attached in VPMN (b), sets up a GPRS Call [MS7(a)] PDP context to TestAPN9 and is connected to TestServer1. After the PDP Context is established the tester terminates the session. Successful result if gprsSSF has terminated the context by sending EntityReleasedGPRS. If supported after reception of MTC[MS8(a)] O ERELgprs(GPRScause) the SCF initiates the transmission of SM to MS7(a)

(b)

107235734.doc

Page 18 of 27

GSM Association Official Document TD.46 1.1.7 Mobility Management IMSI attach, IMSI Detach and Location update in the same VLR area with the same LAI Test Chain Table Call Event Details to be raised on TAP N MS7(a) registers in VPMN (b). Afterwards the MS No Record on TAP is switched off. Then MS is switched on. GsmSCF on receiving notification for IMSI Attach MTC[MS7(a)] O from VLR initiates SM sending procedure to MS7(a) GsmSCF on receiving notification for IMSI Detach MTC[MS7(a)] O from VLR initiates SM sending procedure to MS7(a)

B 2.3.3.1 Subcode (a) (b) (c)

B 2.3.3.2 Subcode (a) (b)

Location update by MS7(a) in the same VLR of VPMN (b) with different LAI (optional) Test Chain Table Call Event Details to be raised on TAP N MS7(a) registered in VPMN (b) moves to another No Record on TAP Location Area within the same VLR service area, thus provoking a new update location. MTC[MS7(a)] O Optionally MS7(a) receives SM (Update Location)

B 2.3.3.3 Subcode (a) (b)

Location update by MS7(a) in another VLR area of VPMN (b) (optional) Test Chain Table Call Event Details to be raised on TAP N MS7(a) registered in VPMN (b) moves towards a No Record on TAP new VLR service area. MTC[MS7(a)] O Optionally MS7(a) receives SM (Update Location)

107235734.doc

Page 19 of 27

GSM Association Official Document TD.46

THE TAP TEST REPORT FOR CAMEL PHASE 1, PHASE 2 AND PHASE 3 SERVICES
This section describes the contents of the TAP Test Report for CAMEL Phase 1, Phase 2 and Phase 3 Services given in Appendix A.

VPMN/HPMN/TAP-Code VPMN: to be filled according to the Roaming Partner under test. HPMN: to be filled according to the Roaming Partner of the specific Roaming Relationship.

TAP Test File Name(s)

TD<Senders TAP-Code><Recipients TAP-Code><File Sequence Number>

The syntax of the file name has to be performed as defined in the TADIG PRD TD57.

Data Record Format Version used

The sender has to indicate the applicable TAP Format Version and Release version referred by the TAP Test File.

Used IMSIs MSISDNs

In the past, a lot of time was spent to put together all the IMSIs and related MSISDNs used during TAP testing. Therefore a table with the relevant IMSIs and MSISDNs involved in the TTC execution has to be provided to save valuable time on TAP testing.

First/Last Call expected in the TAP Test file

During TAP testing the Roaming Partner under test may send more than one TAP test file. The reason therefore could be e.g. due to not performed tests or wrong processed testing data. To have an overview about the expected data within a TAP file, the First- and Last call timestamps should be given here.

Performed TAP Test Cases (TTC)

This table lists all the performed TTCs contained in the respective TAP test file. A reference to the IMSI(s) involved in the specific TTC should also be given here (i.e. pointer to the used IMSIs MSISDN Table). Furthermore all deviations to the GSM standard, if any, have to be listed to reduce the number of open questions between the two testing parties (e.g. Emergency Calls to 112 not transferred on TAP).

ANNEX A TAP TEST REPORT

TAP Test Report for CAMEL Phase 1, Phase 2 and Phase 3 Services

107235734.doc

Page 20 of 27

GSM Association Official Document TD.46

Sender (VPMN) PMN (B) : <Country > TAP - Code: <TAP-Code> <PMN (B) Name>,

Recipient (HPMN) PMN (A) : <Country > TAP - Code: <TAP-Code> <PMN (A) Name>,

TAP Test File Name(s): Data Record Format Version used: Used IMSIs MSISDNs:

< TAP Test File Name > TAP 3.<Release Number>

# 1 2 3

IMSI

MSISDN

First Call expected in the TAP Test file:

<YYYYMMDDHHMMSS>

Last Call expected in the TAP Test file:

<YYYYMMDDHHMMSS>

CAMEL Phase 1TTC

2.1.1.1 Power-up MS1(a) and perform location registration on VPMN(b). 2.1.1.2 Power-up MS2(a) and perform location registration on VPMN(b). 2.1.2 MS1(a) registered in VPMN(b) makes a call to TestNbr1 2.1.3 MS1(A) calls subscriber MS2(A), both registered in VPMN (B) MS2(A) receives call from MS1(A)

Ref. to used IMSI(s)

Comments

Page 21 of 27

107235734.doc

GSM Association Official Document TD.46

CAMEL Phase 1TTC

2.1.4 MS1(A), registered in VPLMN(b), makes a call to TestNbr2. 10 seconds after Test Announcement 3 is connected to calling party, the call is released from SCP 2.1.5 MS1(A) calls MS3(b), both registered in VPMN(b). MS3(b) receives call from MS1(a). MS3(b) disconnects the call 2.1.6.1 MS1(A) calls AAC1; call successful (test announcement 1 played) 2.1.6.2 MS1(A) calls AAC2; call not successful (test announcement 2 not played) 2.1.7 MS2(A) takes battery off in order to provoke unsuccessful call establishment detected in VMSC. MS3(B) attempts a call to MS2(a). 2.1.8.1 MS1(a) registers and activates CFNRy to destination number. MS3(b) calls MS1(a). MS1(a) does NOT answer the call and MS3(b) waits until NoAnswer timer expires. CFNRy is invoked for MS1(a). The call is forwarded to destination number. 2.1.8.2 MS1(a) activates BOIC-exHC. MS1(A) attempts a call to TestNbr3. The SCF alters the destination address to be that of destination number not located in HPMN's Country. 2.1.8.3 MS2(A) attempts a call to TestNbr3. The SCF alters the destination address to be that of destination number not located in HPMN's Country.

Ref. to used IMSI(s)

Comments

CAMEL Phase 2 TTC

2.2.1.1 - Power-up MS4(a) and perform Ref. to used IMSI(s)

Comments

location registration on VPLMN(b).

2.2.1.2 - Power-up MS5(a) and perform

location registration on VPLMN(b).

2.2.2.1 MS4(a), registered in VPMN(b),

makes a call to TestNbr4

2.2.2.2 MS4(a), registered in VPMN(b), makes

a call to AAC4 2.2.3 - MS5(a) makes a call to MS4(a), both registered in VPLMN(b) MS4(a) receives call from MS5(a) 107235734.doc

Page 22 of 27

GSM Association Official Document TD.46 TTC 2.2.4 - MS4(a), registered in VPLMN(b), makes a call to TestNbr11. 10 seconds after Test Announcement 3 is connected to calling party, the call is released from SCP. 2.2.5.1 - MS5(a) makes a call to a MS3(b), which is located in the VPLMN(b). MS3(b) receives call from MS5(b). MS3(b) does not answer the call. 2.2.5.2 - MS5(a) makes a call to a MS3(b), which is located in the VPMN(b) and rendered busy. MS3(b) receives call from MS5(b). MS3(b) is engaged in a call. 2.2.5.3 - MS5(a) makes a call to a MS3(b), which is located in the VPMN(b) and switched off (explicitly detached). MS3(b) receives call from MS5(b). MS3(b) is switched off. 2.2.5.4 - MS5(a) attempts a call to a number range of VPMN B. 2.2.6.1 - MS4(a), registered in VPMN(b), makes a call to TestNbr5 and is connected to Test Announcement 5 (AAC5). AAC5 disconnects the call after 30 seconds. Depending on correct reporting of call periods, either Test Announcement 1 (AAC1) or Test Announcement 2 (AAC2) is played. 2.2.6.2 - MS4(a), registered in VPMN(b), makes a call to TestNbr7 and is connected to Test Announcement 5 (AAC5). AAC5 disconnects the call after 30 seconds. Depending on correct reporting of the call periods either Test Announcement 1 (AAC1) or Test Announcement 2 (AAC2) is played 2.2.6.3 - MS4(a), registered in VPLMN(b), makes a call to TestNbr6 and is connected to Test Announcement 3 (AAC3). Check if a warning tone is played to calling party after about 10 seconds 2.2.7 - MS4(a) attempts a call to TestNbr10; and is connected to an IN Announcement located in Assisting SSF (a). Test Announcement 1 (AAC1) is played to calling party 2.2.8.1 - MS5(a) attempts a call to AAC1; Successful result if Test Announcement 1 is played to calling party 2.2.8.2 - MS6(a) attempts a call to AAC2; Successful result if call is NOT established and Test Announcement 2 is NOT played to calling party 107235734.doc
Ref. to used IMSI(s)

Comments

Page 23 of 27

GSM Association Official Document TD.46 TTC 2.2.9 - MS5(a) takes battery off in order to provoke unsuccessful call establishment detected in VMSC. MS3(b) attempts a call to MS5(a) 2.2.10.1 - MS4(a) makes a call to TestNbr12 and places the call on hold. MS4(a) then initiates a call to Testnbr13 and invokes a Multi Party call 2.2.10.2 MS5(a) has activated Call Forwarding on No Reply to Test Announcement 3. MS3(b) attempts a call to MS5(a). MS5(a) does NOT answer the call and MS3(b) waits until NoAnswer timer expires CFNRy is invoked for MS5 (A) The call is forwarded to destination number 2.2.10.3 - MS4(a) activates BOIC-exHC. MS4(a) has activated Barring of outgoing international calls except those directed to the HPLMN country MS4(a) attempts a call to TestNbr9. The SCF alters the destination address to be that of destination number located in country(c), DN(c). 2.2.10.4 - MS5(a) attempts a call to TestNbr9. The SCF alters the destination address to be that of destination number located in country(c), DN(c).
Ref. to used IMSI(s)

Comments

CAMEL Phase 3 TTC 2.3.1.1.1- Location Update by MS7(a) in VPMN(b). 2.3.1.1.2- Location Update by MS8(a) in VPMN(b) 2.3.1.2 Check operation of IDP_SMS and CON_SMS 2.3.1.3- Check operation of REL_SMS 2.3.1.4.1continue DefaultSMSHandling set to
Ref. to used IMSI(s)

Comments

107235734.doc

Page 24 of 27

GSM Association Official Document TD.46 TTC 2.3.1.4.2 - DefaultSMSHandling set to release 2.3.1.5 Check Operation of RR_SMS_Event, CUE_SMS and ER_SMS 2.3.1.6- Barring of outgoing international calls except to HPMN country for SMS (BOICexHC) (optional) 2.3.2.1.1- GPRS Attach by MS7(a) in VPMN (b) (GPRS Attach only) 2.3.2.1.2- GPRS Attach by MS8(a) in VPMN (b) (GPRS Attach only) 2.3.2.2.1- Check used volume, 2 PDP context periods, tariffSwitch after PCD 2.3.2.2.2 Check used volume, 3 PDP context periods, tariffSwitch in 2nd period 2.3.2.2.3 - Check used Time, 2 PDP context periods, tariffSwitch in 1st period 2.3.2.2.4- Check used Time, 3 PDP context periods, tariffSwitch in 2nd period 2.3.2.2.5- Parallel GPRS dialogues using GPRS CAMEL Scenario 2 (optional) 2.3.2.3.1- Parallel PDP contexts using GPRS CAMEL Scenario 1 (optional) 2.3.2.3.2- Check Default GPRS handling set to continue 2.3.2.4.1- Check Default GPRS handling set to release within CAMEL Scenario 2, Abort during PDP context establishment 2.3.2.4.2- Check Default GPRS handling set to release within CAMEL Scenario 2, Abort during active PDP context 2.3.2.5Check correct operation of EntityReleasedGPRS procedure (Optional) 2.3.3.1- IMSI attach, IMSI Detach and Location update in the same VLR area with the same LAI
Ref. to used IMSI(s)

Comments

107235734.doc

Page 25 of 27

GSM Association Official Document TD.46 TTC 2.3.3.2- Location update by MS7(a) in the same VLR of VPMN (b) with different LAI (optional) 2.3.3.3- Location update by MS7(a) in another VLR area of VPMN (b) (optional) On behalf of <PMN (B) Name>:
Ref. to used IMSI(s)

Comments

Date

Name

Signature

5 DOCUMENT MANAGEMENT
Document History Version 1.0.0 2.0.0 3.0.0 3.1.0 3.2 Date 12th June 2001 13th July 2001 27th July 2001 25th June 2002 30th June 2003 Brief Description of Change Final proposed version submitted to TADIG 51 for approval Version sent by Weekly Bulletin to Membership for Approval Membership Approved Version CAMEL Phase 2 test cases added NSCR 002 (TADIG Doc 060/03) update with document 3.10 and NSCR 003 (TADIG Doc080/03) update to be in line with the IR.32 document with the inclusion of the CAMEL Phase 3 Testcases. Update to be in line with the IR.32 document (v.3.3.2) Minor CR005 Correction for AAC Scenarios Minor CR006 Correction of TAP Test Report. New GSMA template applied (4 December 2008) Approval Authority TADIG TADIG TADIG TADIG Editor / Company Hendrik Hoehndorf / MACH Hendrik Hoehndorf / MACH Hendrik Hoehndorf / MACH Hendrik Hoehndorf / MACH Hendrik Hoehndorf / MACH Hendrik Hoehndorf / MACH Hendrik Hoehndorf / MACH Hendrik Hoehndorf / MACH

TADIG

3.3 3.4 3.5

28th April 2005 20th October 2005 22nd May 2008

TADIG TADIG

TADIG

Other Information

107235734.doc

Page 26 of 27

GSM Association Official Document TD.46 Type Document Owner Editor / Company Description TADIG Hendrik Hoehndorf / MACH

107235734.doc

Page 27 of 27