GSM Association Official Document TD.46 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 GSMA Full Members X Confidential GSMA Associate Members X Confidential GSMA Rapporteur Members X Confidential GSMA Parent Company Members X document.doc Page 1 of 35 TAP Test Cases (TTC) for CAMEL Phase 1, Phase 2 and Phase 3 Services 3.5 22 May 2008
Transcript
GSM AssociationOfficial Document TD.46
This is a binding permanent reference document of the GSM Association.
Security Classification: This document contains GSMA Confidential
InformationAccess 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 GSMA Full Members XConfidential GSMA Associate Members XConfidential GSMA Rapporteur Members XConfidential GSMA Parent Company Members X
Antitrust NoticeThe information contain herein is in full compliance with the GSM Association’s antitrust compliance policy.
document.doc Page 1 of 27
TAP Test Cases (TTC) for CAMEL Phase 1, Phase 2 and Phase 3 Services
3.5
22 May 2008
GSM AssociationOfficial Document TD.46
Table of Contents
1 Introduction.............................................................................................31.1 Scope of Document.............................................................................31.2 Document Cross References..............................................................31.3 Abbreviations......................................................................................3
2 TAP Test Cases (TTCs)...........................................................................6Parameters:....................................................................................................6
3 TAP Test Case Cross Reference Tables...............................................7Description TTC Cross Reference Table Contents.........................................73.1 Structure of TTC Cross Reference Tables..........................................7
4 TTC...........................................................................................................84.1 CAMEL Phase 1 Test cases...............................................................81.1.1 Basic Service TTCs.............................................................................81.1.2 Supplementary Service and ODB TTCs..............................................94.2 CAMEL Phase 2 Testcases..............................................................101.1.3 Basic Service TTCs...........................................................................101.1.4 Supplementary Service and ODB TTCs............................................131.1.5 MO SMS Control...............................................................................151.1.6 GPRS Control...................................................................................161.1.7 Mobility Management........................................................................19
The TAP Test Report for CAMEL Phase 1, Phase 2 and Phase 3 Services21
ANNEX A – TAP Test Report.........................................................................21
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
PRD Number Title
GSM Association PRD IR.32
End-to-End Functional Capability Specification for Inter-PLMN CAMEL Roaming (CAMEL Phase 1, Phase 2 and Phase 3)
GSM Association PRD TD.41
Testing the Transferred Account Procedure
GSM Association PRD TD.57
Transferred Account Procedure Data Record Format Specification
1.3 Abbreviations
AAC Automatic Answering CircuitAACx destination Number of Announcement xABT TCAP-AbortAC CAP-Apply ChargingACR CAP-Apply Charging ReportANM ISUP-AnswerAoCI Advice of Charge Information
document.doc Page 3 of 27
GSM AssociationOfficial Document TD.46
ARI CAP-Assist Request InstructionsAT CAP-Activity TestATI Any Time InterrogationCAMEL Customised Applications for Mobile networks using Enhanced LogicCAP CAMEL Application PartCC Country CodeCIRep CAP-Call Information ReportCIReq CAP-Call Information RequestCON CAP-ConnectCPD max Call Period DurationCTR CAP-Connect To ResourceCUE CAP-ContinueDFC CAP-Disconnect Forward ConnectionDN(c) Destination Number which is located in country(c) DRA Destination Routing AddressEDP Event Detection PointERB Event Report BCSMETC CAP-Establish Temporary ConnectionFCI CAP-Furnish Charging InfoFTN Forwarded To NumberGMSC Gateway Mobile Services Switching Centre.HLR Home Location Register.HPMN Home PMNIAM ISUP-Initial Address MessageIDP CAP-Initial DPIMSC Interrogating MSCIR International RoamingISD Insert Subscriber DataMS Mobile Station MS(b) indicates that the MS subscription is managed by PMN(b)MSIN Mobile Subscriber Identification NumberNDC Network Destination CodeO-CSI Originating CAMEL Subscription Information.ODB Operator Determined Barring.OR Optimal RoutingPA CAP-Play AnnouncementPMN Public Mobile Network including RSS ("Radio Sub-System") and NSS ("Network Sub-System") PMN(a) indicates the "ath" PMN.
PSI MAP-ProvideSubscriberInformationPSTN Public Switched Telephone Network; PSTN(b) indicates a PSTN telephone in country b.RC CAP-Release CallREL ISUP-ReleaseRIDE Release If Duration ExceededRRBE CAP-Request Report BCSM EventSCF Service Control FunctionSCI CAP-Send Charging InfoSCP Service Control PointSoA Suppression of AnnouncementSRF Specialized Resource FunctionSRR CAP-Specialized Resource ReportSS Supplementary ServicesTAP Transferred Account Procedure
document.doc Page 4 of 27
GSM AssociationOfficial Document TD.46
TINTS Time If No Tariff SwitchTS Tariff SwitchTSI Tariff Switch IntervalTSLTS Time since Last Tariff SwitchVMSC Visited Mobile Services Switching Centre, including the always co-located entities
MSC ("Mobile Services Switching Centre") and VLR ("Visitor Location Register").
VPMN Visited PMN.
document.doc Page 5 of 27
GSM AssociationOfficial Document TD.46
2 TAP TEST CASES (TTCS)
Parameters:
PMN(A) Home PMN of MS1(A) and MS2(A)
PMN(B) Visited PMN of MS1(A) and MS2(A)
MS1(A), MS2(A) Mobile Subscribers from HPMN(A) roaming in the VPMN(B)
PSTN telephones belonging not to the PMN(A) nor the PMN(B)
document.doc Page 6 of 27
GSM AssociationOfficial 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 Abbreviation ExplanationMandatory M Must be present.
Conditional C 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).
Optional O 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.
Not applicable N Must NOT be transferred on the TAP.
Further Study F For further study.
3.1 Structure of TTC Cross Reference Tables
TTC TTC description
Subcode Test Chain TableCall Event Details to be raised on TAP
(a) Brief scenario description of part 1 of test chain ConditionalityData expected
(b) Brief scenario description of part 2 of test chain ConditionalityData expected
… … …
Appendix A – TTC TESTING PARAMETERS’ details additional testing information, performance and comments of TTCs.
document.doc Page 7 of 27
GSM AssociationOfficial Document TD.46
4 TTC
4.1 CAMEL Phase 1 Test cases
1.1.1 Basic Service TTCs
B2.1.1.1 Location Update by MS1(a) in VPMN(b)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) Power-up MS1(a) and perform location registration on VPMN(b).
N
B 2.1.1.2 Location Update by MS2(a) in VPMN(b)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) Power-up MS2(a) and perform location registration on VPMN(b).
N
B 2.1.2 Check operation of IDP and CON
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS1(a), registered in VPMN(b), makes a call to TestNbr1
MMOC[MS1(A)]
B 2.1.3 Check operation of PSI.
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS1(A) calls subscriber MS2(A), both registered in
VPMN (B)
MMOC[MS1(A)]
(b) MS2(A) receives call from MS1(A) MMTC[MS2(A)]
B 2.1.4 Check reporting of EDP O_Answer and operation of RC
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) 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.
MMOC[MS1(A)]
document.doc Page 8 of 27
GSM AssociationOfficial Document TD.46
B 2.1.5 Check operation of CUE
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS1(A) calls MS3(b), both registered in VPMN(B) MMOC[MS1(A)]
(b) MS3(b) receives call from MS1(A). MS3 (b) disconnects the call.
NNo Record on TAP
B 2.1.6.1 Check default call handling; default call handling set to continue call
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS1(A) calls AAC1; call successful (test
announcement 1 played)
MMOC[MS1(A)]
B 2.1.6.2 Check default call handling; default call handling set to release call
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS1(A) calls AAC2; call not successful (test
announcement 2 not played)
NNo Record on TAP
B 2.1.7 Check Suppression of Announcement
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS2(A) takes battery off in order to provoke
unsuccessful call establishment detected in VMSC.
NNo Record on TAP
(b) MS3(B) attempts a call to MS2(a). NNo Record on TAP
1.1.2 Supplementary Service and ODB TTCs
B2.1.8.1 Call Forward on No Reply [CFNRy];
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS1(A) registers and activates CFNRy to
destination number
OSS[MS1(A)]
(b) MS3(b) calls MS1(A). MS1(a) does NOT answer
the call and MS3(b) waits until NoAnswer timer expires
MMTC[MS1(A)]
(c) CFNRy is invoked for MS1(A). M
document.doc Page 9 of 27
GSM AssociationOfficial Document TD.46
OFFLINE: SS[MS1(A)]
INLINE: see note 1 (d) The call is forwarded to destination number M
MOC[MS1(A)]
B 2.1.8.2 Barring of Outgoing International Calls Except to HPMN Country[BOICexHC]
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS1(A) activates BOIC-exHC OSS[MS1(A)]
(b) 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.
NNo Record on TAP
B 2.1.8.3 ODB: Barring of Outgoing International Calls Except to HPMN Country[ODB-BOIC exHC]
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) 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.
NNo Record on TAP
4.2 CAMEL Phase 2 Testcases
1.1.3 Basic Service TTCs
B 2.2.1.1 Location Update by MS4(a) in VPMN(b)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) Power-up MS4(a) and perform location registration on VPMN(b).
NNo Record on TAP
B 2.2.1.2 Location Update by MS5(a) in VPMN(b)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) Power-up MS5(a) and perform location registration on VPMN(b).
NNo Record on TAP
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[MS1(A)] of the test chain.
document.doc Page 10 of 27
GSM AssociationOfficial Document TD.46
B 2.2.2.1 Check Operation of IDP and DP2 Criteria _ Called Number of Length within Destination Number Length List
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS4(a), registered in VPMN(b), makes a call to TestNbr4
MOC[MS4(A)] M
B 2.2.2.2 Check Operation of IDP and DP2 Criteria _ Called Number Length not Defined by Destination Number Length List
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS4(a), registered in VPMN(b), makes a call to AAC4
MOC[MS4(A)] M
B 2.2.3 Check Operation of PSI
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS5(a) makes a call to MS4(a), both registered in VPMN(b)
MOC[MS5(A)] M
(b) MS4(a) receives call from MS5(a) MTC[MS4(A)] M
B 2.2.4 Check reporting of EDP O_Answer, O_Disconnect and operation of RC
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) 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.
MOC[MS4(A)] M
B 2.2.5.1 Check operation of CUE and FCI with Follow-On Call due to “Called Party does not Reply”
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS5(a) makes a call to a MS3(b), which is located in the VPMN(b).
MOC[MS5(a)] M
(b) MS3(b) receives call from MS5(b). MS3(b) does not answer the call.
No Record on TAP N
B 2.2.5.2 Check operation of CUE and FCI with Follow-On Call due to “Called Party is busy" (optional)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS5(a) makes a call to a MS3(b), which is located in the VPMN(b) and rendered busy.
MOC[MS5(a)] M
(b) MS3(b) receives call from MS5(b). MS3(b) is engaged in a call.
No Record on TAP N
document.doc Page 11 of 27
GSM AssociationOfficial Document TD.46
B 2.2.5.3 Check operation of CUE and FCI with Follow-On Call due to “Called Party is NotReachable" (optional)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS5(a) makes a call to a MS3(b), which is located in the VPMN(b) and switched off (explicitly detached).
MOC[MS5(a)] M
(b) MS3(b) receives call from MS5(b). MS3(b) is switched off.
No Record on TAP N
B 2.2.5.4 Check operation of CUE and FCI with Follow-On Call due to “RouteSelectFailure" by "Release before Answer" (optional)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS5(a) attempts a call to a number range of VPMN B.
MOC[MS5(a)] M
B 2.2.6.1 Check Operation of CIReq, SCI and AC, Check correct reporting of call periods (1)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) 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.
MOC[MS4(a)] M
(b) Depending on correct reporting of call periods, either Test Announcement 1 (AAC1) or Test Announcement 2 (AAC2) is played.
MOC[MS4(a)] M
B 2.2.6.2 Check Operation of CIReq, SCI and AC, Check reporting of call periods (2)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) 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.
MOC[MS4(a)] M
(b) Depending on correct reporting of the call periods either Test Announcement 1 (AAC1) or Test Announcement 2 (AAC2) is played
MOC[MS4(a)] M
B 2.2.6.3 Check warning tone and automatic call release
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS4(a), registered in VPMN(b), makes a call to TestNbr6 and is connected to Test Announcement 3 (AAC3).
MOC[MS4(a)] C
document.doc Page 12 of 27
GSM AssociationOfficial Document TD.46
Check if a warning tone is played to calling party after about 10 seconds
B 2.2.7 Check operation of ETC and DFC
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) 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
MOC[MS4(a)] C
B 2.2.8.1 Check Default Call Handling - defaultCallHandling set to continueCall
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS5(a) attempts a call to AAC1; Successful result if Test Announcement 1 is played to calling party
MOC[MS5(a)] M
B 2.2.8.2 Check Default Call Handling - defaultCallHandling set to releaseCall
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS6(a) attempts a call to AAC2; Successful result if call is NOT established and Test Announcement 2 is NOT played to calling party.
No Record on TAP N
B 2.2.9 Check Suppression Of Announcement
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS5(a) takes battery off in order to provoke unsuccessful call establishment detected in VMSC.
No Record on TAP N
(b) MS3(b) attempts a call to MS5(a) No Record on TAP N
1.1.4 Supplementary Service and ODB TTCs
B 2.2.10.1 Check Operation of SS-SCI, MRTY
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS4(a) makes a call to TestNbr12 and places the call on hold.
MOC[MS4(a)] M
(b) MS4(a) then initiates a call to Testnbr13 and invokes a Multi Party call
MOC[MS4(a)] M
document.doc Page 13 of 27
GSM AssociationOfficial Document TD.46
B 2.2.10.2 Call Forwarding on no reply (CFNRy)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS5(a) has activated Call Forwarding on No Reply to Test Announcement 3.
SS[MS5 (A)] O
(b) MS3(b) attempts a call to MS5(a). MS5(a) does NOT answer the call and MS3(b) waits until NoAnswer timer expires
MTC[MS5 (A)] M
(c) CFNRy is invoked for MS5 (A) OFFLINE: SS[MS5 (A)] MINLINE: see note1
(d) The call is forwarded to destination number MOC[MS5 (A)] M
B 2.2.10.3 Barring of outgoing international calls except to HPLMN country
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS4(a) activates BOIC-exHC. MS4(a) has activated Barring of outgoing international calls except those directed to the HPLMN country
SS[MS4 (A)] O
(b) 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).
No Record on TAP N
B 2.2.10.4 ODB: Barring of outgoing international calls except to HPLMN country (ODB-BOICexHC)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) 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).
No Record on TAP N
4.3 CAMEL Phase 3 Testscases
1.1.5 MO SMS Control
B2.3.1.1.1 Location Update by MS7(a) in VPMN(b)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) Power-up MS7(a) and perform location registration on VPMN(b).
NNo Record on TAP
B 2.3.1.1.2 Location Update by MS8(a) in VPMN(b)
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.
document.doc Page 14 of 27
GSM AssociationOfficial Document TD.46
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) Power-up MS8(a) and perform location registration on VPMN(b).
NNo Record on TAP
B 2.3.1.2 Check operation of IDP_SMS and CON_SMS
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS8(a) sends a SM to MS7(a) using TestNbr14 as SMSC Address. Depending on InitialDPSMS content the SM is forwarded to either MS7(a) or MS8(a) with a modified Calling Party and a modified SMSC-Address.
MOC[MS8(a)] M
(b) Successful result if MS8(a) receives the SM sent previously from MS8(a).
MTC[MS8(a)] M
B 2.3.1.3 Check operation of REL_SMS
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a) sends a SM to MS8(a) using HPMN_SMSC as SMSC Address. Successful result if the SM is Not sent.
NNo Record on TAP
B2.3.1.4.1 Check DefaultSMSHandling set to continue
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a) sends a SM to itself. SCP does not answer to InitialDPSSMS. The Default SMS Handling of MS7(a) equals continue
MOC[MS7(a)] M
(b) MS7(a) receives a SM from itself MTC[MS7(a)] M
B 2.3.1.4.2 Check DefaultSMSHandling set to release
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS8(a) sends a SM to itself. SCP does not answer to InitialDPSSMS. The Default SMS Handling of MS7(a) equals release. Successful result if SM is Not sent
No Record on TAP N
B 2.3.1.5 Check Operation of RR_SMS_Event, CUE_SMS and ER_SMS
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS8(a) sends a SM to MS3(b) using HPMN_SMSC as SMSC Address
MOC[MS8(a)] M
(b) MS3(b) receives a SM from MS8(a) MTC[MS3(b)] M
document.doc Page 15 of 27
GSM AssociationOfficial Document TD.46
(c) If HPMN has indicated that SCF-initiated SMS is used MS8(a) receives a SM : SMS_Submitted.
MTC[MS8(a)] O
B 2.3.1.6 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 SMSC Address; successful result if the SM transmission is barred
No Record on TAP N
(b) If HPMN has indicated that SCF-initiated SMS is used MS7(a) receives a SM : SMS_Failure.
MTC[MS7(a)] O
1.1.6 GPRS Control
1.1.6.1 GPRS - Attach
B 2..3.2.1.1 GPRS Attach by MS7(a) in VPMN (b) (GPRS Attach only)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) Power-up MS7(a) and perform GPRS Attach only on VPMN (b)
No Record on TAP N
B 2.3.2.1.2 GPRS Attach by MS8(a) in VPMN (b) (GPRS Attach only)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) Power-up MS8(a) and perform GPRS Attach only on VPMN (b)
No Record on TAP N
B 2.3.2.2.1 Check used volume, 2 PDP context periods, tariffSwitch after PCD
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a), GPRS attached in VPMN (b), sets up 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
GPRS Call [MS7(a)] M
B 2.3.2.2.2 Check used volume, 3 PDP context periods, tariffSwitch in 2nd period
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a), GPRS attached in VPMN (b), sets up 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
GPRS Call [MS7(a)] M
document.doc Page 16 of 27
GSM AssociationOfficial Document TD.46
B 2.3.2.2.3 Check used Time, 2 PDP context periods, tariffSwitch in 1st period
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a), GPRS attached in VPMN (b), sets up 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
GPRS Call [MS7(a)] M
B 2.3.2.2.4 Check used Time, 3 PDP context periods, tariffSwitch in 2nd period
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a), GPRS attached in VPMN (b), sets up 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.
GPRS Call [MS7(a)] M
B 2.3.2.2.5 Parallel GPRS dialogues using GPRS CAMEL Scenario 2 (optional)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a), GPRS attached in VPMN (b), sets up a GPRS dialogue to TestAPN5 which is connected to TestServer1 and a second GPRS dialogue to TestAPN6 which is connected to TestServer2. MS7(a) transfers data using a service provided by 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.
GPRS Call [MS7(a)] for PDP Context 1, M
GPRS Call [MS7(a)] for PDP Context 2, M
1.1.6.2 CAMEL scenario 1
B 2.3.2.3.1 Parallel PDP contexts using GPRS CAMEL Scenario 1 (optional)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS8(a), GPRS attached in VPMN (b), sets up one PDP context to TestAPN7 which is connected to TestServer1 and a second PDP context to TestAPN8 which is connected to TestServer2. MS8(a) transfers data using a service provided by HPMN(a) within PDP Context 1 & PDP Context 2.Successful result if both PDP contexts are
GPRS Call [MS8(a)] for PDP Context 1, M
GPRS Call [MS8(a)] for PDP Context 2, M
document.doc Page 17 of 27
GSM AssociationOfficial Document TD.46
released after transmission of 15.000 + 1500 byte.(b) If HPMN has indicated that SCF-initiated SMS is
used MS8(a) receives an appropriate SM. MTC[MS8(a)] C
B 2.3.2.3.2 Check Default GPRS handling set to continue
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS8(a), GPRS attached in VPMN (b), sets up 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
GPRS Call [MS8(a)] M
B 2.3.2.4.1 Check Default GPRS handling set to release within CAMEL Scenario 2, Abort during PDP context establishment
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a), GPRS attached in VPMN (b), attempts to 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.
No Record on TAP N
B 2.3.2.4.2 Check Default GPRS handling set to release within CAMEL Scenario 2, Abort during active PDP context
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a), GPRS attached in VPMN (b), attempts to 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
GPRS Call [MS7(a)] M
B 2.3.2.5 Check correct operation of EntityReleasedGPRS procedure (Optional)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a), GPRS attached in VPMN (b), sets up 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
GPRS Call [MS7(a)] M
document.doc Page 18 of 27
GSM AssociationOfficial Document TD.46
context by sending EntityReleasedGPRS.(b) If supported after reception of
ERELgprs(GPRScause) the SCF initiates the transmission of SM to MS7(a)
MTC[MS8(a)] O
1.1.7 Mobility Management
B 2.3.3.1 IMSI attach, IMSI Detach and Location update in the same VLR area with the same LAI
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a) registers in VPMN (b). Afterwards the MS is switched off.Then MS is switched on.
No Record on TAP N
(b) GsmSCF on receiving notification for IMSI Attach from VLR initiates SM sending procedure to MS7(a)
MTC[MS7(a)] O
(c) GsmSCF on receiving notification for IMSI Detach from VLR initiates SM sending procedure to MS7(a)
MTC[MS7(a)] O
B 2.3.3.2 Location update by MS7(a) in the same VLR of VPMN (b) with different LAI (optional)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a) registered in VPMN (b) moves to another Location Area within the same VLR service area, thus provoking a new update location.
No Record on TAP N
(b) Optionally MS7(a) receives SM (Update Location) MTC[MS7(a)] O
B 2.3.3.3 Location update by MS7(a) in another VLR area of VPMN (b) (optional)
Subcode Test Chain Table Call Event Details to be raised on TAP
(a) MS7(a) registered in VPMN (b) moves towards a new VLR service area.
No Record on TAP N
(b) Optionally MS7(a) receives SM (Update Location) MTC[MS7(a)] O
document.doc Page 19 of 27
GSM AssociationOfficial 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-CodeVPMN: 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)The syntax of the file name has to be performed as defined in the TADIG PRD TD57.
Data Record Format Version usedThe sender has to indicate the applicable TAP Format Version and Release version referred by the TAP Test File.
Used IMSIs – MSISDNsIn 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 fileDuring 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
document.doc Page 20 of 27
GSM AssociationOfficial Document TD.46
Sender (VPMN) PMN (B) : <PMN (B) Name>,
<Country >
TAP - Code: <TAP-Code>
Recipient (HPMN) PMN (A) : <PMN (A) Name>,
<Country >
TAP - Code: <TAP-Code>
TAP Test File Name(s): < TAP Test File Name >
Data Record Format Version used: TAP 3.<Release Number>
Used IMSIs – MSISDNs:
# IMSI MSISDN123…
First Call expected in the TAP Test file: <YYYYMMDDHHMMSS>
Last Call expected in the TAP Test file: <YYYYMMDDHHMMSS>
CAMEL Phase 1TTCRef. to used
IMSI(s) Comments
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)
document.doc Page 21 of 27
GSM AssociationOfficial Document TD.46
CAMEL Phase 1TTCRef. to used
IMSI(s) Comments
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.
CAMEL Phase 2
TTC Ref. to used IMSI(s) Comments
2.2.1.1 - Power-up MS4(a) and perform 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)
document.doc Page 22 of 27
GSM AssociationOfficial Document TD.46
TTC Ref. to used IMSI(s) Comments
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
document.doc Page 23 of 27
GSM AssociationOfficial Document TD.46
TTC Ref. to used IMSI(s) Comments
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 expiresCFNRy 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 countryMS4(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).
CAMEL Phase 3
TTC Ref. to used IMSI(s) Comments
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.1- DefaultSMSHandling set to continue
document.doc Page 24 of 27
GSM AssociationOfficial Document TD.46
TTC Ref. to used IMSI(s) Comments
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.5- Check 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
document.doc Page 25 of 27
GSM AssociationOfficial Document TD.46
TTC Ref. to used IMSI(s) Comments
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>:
Date Name Signature
5 DOCUMENT MANAGEMENT
Document History
Version Date Brief Description of ChangeApproval Authority
Editor / Company
1.0.0 12th June 2001
Final proposed version submitted to TADIG 51 for approval
TADIGHendrik Hoehndorf / MACH
2.0.0 13th July 2001
Version sent by Weekly Bulletin to Membership for Approval
TADIGHendrik Hoehndorf / MACH
3.0.0 27th July 2001
Membership Approved Version TADIG
Hendrik Hoehndorf / MACH
3.1.0 25th June 2002
CAMEL Phase 2 test cases added TADIG
Hendrik Hoehndorf / MACH
3.2 30th June 2003
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.
TADIGHendrik Hoehndorf / MACH
3.3 28th April 2005
Update to be in line with the IR.32 document (v.3.3.2) TADIG
Hendrik Hoehndorf / MACH
3.4 20th October 2005
Minor CR005 Correction for AAC Scenarios TADIG
Hendrik Hoehndorf / MACH
3.5 22nd May 2008
Minor CR006 Correction of TAP Test Report. New GSMA template applied (4 December 2008)
