Ir24 5q2nu

Title

Version Date

End-to-End Functional Capability Specification for Inter-PLMN Roaming (Stage 4 Testing)

5.0 12. Mar 08

GSM Association Classifications Binding Core

IR24 General

1(41)

234429122.xls.ms_office

Security Classification Category: Unrestricted X Industry 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 1992

Document History Version

Brief Description For Ad Hoc group discussion

Date

Issue 1.01.01 to 1.04.00:

For IREG Discussions

Dec 1991 – May 1992

Version 2.00.00:

Incorporates comments from GSM Association Plenary

27th July 1992

Version 2.01.00:

Incorporates comments from IREG August 1992

25th Aug 1992

Version 2.01.01:

Editorial Corrections

7th Sept 1992

Version 3.00.00:

Approved MoU 21

21st Sept 1992

Version 3.01.00:

Approved MoU 23 Includes CRs 1, 2, 3 and 4

31st Mar 1993

Draft Issues

Version 3.02.00:

Approved MoU 24 Includes CRs 5, 6, 7 and 8

30th June 1993

Version 3.03.00:

Approved MoU 25 Includes CRs 9 and 10

15th Feb 1994

Version 3.04.00:

Approved MoU 30 Includes CR11

24th Mar 1995

Version 3.05.00:

Approved MoU31 Includes CR.12

Version 3.06.00:

Approved MoU 40 Includes CR.13 To modify 2.1.6 (PSTN Telephone in Country Containing PLMN(b) Calls MS(A), which had roamed to VPLMN(b), But is not able to respond to paging) for Pre-paging – proposed from NTT DoCoMo.

th

Feb 11 2003

IR24 General

Oct - Dec 1991

Dec 1st 2003

IREG Doc 46/027 “NCR 016 to IR.24 Ver.3.7.0 for Clarification of Roaming Scenario to be Tested” incorporated

Version 3.7

IREG Doc 46/027 Incorporated

?

20th Oct 1998 3/ Jul/ 00

3/ Jul/ 01

1st Dec 2003

2(41)


4.0

Version 3.8 Version 4.0 Version 4.1

Version 4.1

Version 5.0

Signal Doc 30_007_rev 1 “Major CR 031 to IR.24 Nov 13th 2006 Change Request” incorporated, to include SMS Interworking tests as Appendix C and D. IREG Doc 48/054 Incorporated 11th Feb 2005 Approved CR30_007 5/ Sep/ 06 IREG Doc 48/054 “NCR 029 to IR.24 for Testing of 3/ Aug/ 07 CLI Delivery” incorporated. IREG Doc 48/013_Rev 1 “NCR 028 to IR.24” incorporated. additional corrections in setups of sheetGENERAL,TEST CASE PAGE, TEMPLATE PAGE after converting from WORD to EXCEL Changed IR24 from Word to EXCEL within GSMA Open Connectivity project

1

INTRODUCTION

1.1

Scope of Document

14th July 2008

12th March 2008

This document is the specification of IREG End-to-end Functional Capability tests relating to the international roaming of a Mobile Station, belonging to a home PLMN(a), to and within a visited PLMN(b). Whilst it is expected that roaming will be a bilateral activity between two PLMNs, please note that this document is written in a unidirectional context. Hence Roaming is taking place by a MS(a) to VPLMN(b) only. There is no reference to a Mobile Station MS(b) visiting PLMN(a). To complete IREG End-to-end Functional Capability tests for bilateral roaming, it is necessary to perform the tests in this document twice: the second time the real identities of PLMN(a) and PLMN(b) are swapped. IREG Document PRD IR23 defines the scope and purpose of each stage of testing. This document does not cover: · SC testing · Exchange of PLMN numbering, addressing and routing data [see Stage 3: IREG PRD IR23] · Testing of Transferred Procedure, billing applications and any inter-PLMN financial statement; [see TADIG PRD TD06]. However the production of a Toll Ticketing file, for use in the TADIG Stage 3 testing is included. ·

Definition of operation and maintenance procedures such as points for fault reporting and notification of planned works. [see Stage 3: IREG PRD IR23]

The Scope of this issue of the document extends to GSM Association Phase 1 services only.

1.2.

Abbreviations The following abbreviations are used: ·

PLMN ("Public Land Mobile Network") including RSS ("Radio Sub-System") and NSS ("Network Sub-System"). PLMN (a) indicates the "ath" PLMN.

·

VPLMN ("Visited PLMN")

·

HPLMN ("Home PLMN")

·

HLR ("Home Location ")

·

VMSC ("Visited Mobile Services Switching Centre"), including the always co-located entities MSC ("Mobile Services Switching Centre") and VLR ("Visitor Location ")

·

GMSC ("Gateway Mobile Services Switching Centre")

·

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

·

PSTN telephone (b) indicates a PSTN telephone in the country which contains PLMN (b)

·

DN ("Directory Number")

The "visitor" and "roaming" are equivalent through the document.

IR24 General

3(41)


1.3. Objective of Tests The fundamental objective of this testing is to confirm the capability, and sample the quality of service which GSM s 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: this type of testing forms part of the Stage 1 testing [see IREG PRD IR23]. Because the testing is at a top-level, its scope includes checking the correct working of features and any network features required by the HPLMN (e.g. barring). The scope also includes the confirmation of acceptable quality of transmission, absence of echo and call set-up delay. The overall objective of the tests is to confirm that the functions and features, which are already known to operate correctly within each separate PLMN, will also operate correctly for Inter-PLMN roaming. When there is no difference in a PLMN's operation between Home and Visiting MSs, then there is no requirement to confirm successful operation during Stage 4 testing. An example of this is "handover". In addition where a feature involves only the Gateway MSC and HLR, (both located in the HPLMN), then there is no requirement to test during Stage 4. The specific objectives are to prove that: (a) (b)

c)

"Location updating" and the associated "Inserting of Subscriber data" can be successfully completed for MS (a) roaming to PLMN (b). In addition, that the "cancel location" service operates correctly. Incoming speech calls to MS (a) can be handled by: (i)

HPLMN(a) asking for Roaming Number from VPLMN (b)

(ii)

HPLMN(a) successfully routing the call

(iii)

VPLMN(b) connecting the call

Outgoing speech calls by MS(a) to the VPLMN(b) are handled for: (i)

Emergency calls

(ii)

Calls to VPLMN(b) country (i.e. local calls)

(iii)

International calls

(iv)

Calls to any other/relevant "Operator Services" on VPLMN(b)/PSTN(b)

(d)

Supplementary Services can be ed and activated, and their status interrogated by the MS (a).

(e)

Specific Supplementary Services can be invoked successfully: (i)

Call Barring: All Outgoing Calls

(ii)

Call Barring: Outgoing International Calls

(iii)

Call Barring: Outgoing International Calls except to Home Country

(iv)

Call Forwarding on not reachable (Before IMSI detach)

(v)

Call Forwarding on Not reachable (After IMSI detach - If Attach/Detach ed by VMSC)

(vi)

Call Forwarding on Busy

(vii)

Call Forwarding on No Reply

(f)

Specific Supplementary Services can be activated by a MS which is roamed.

(g)

Barring of Incoming Calls when roamed

(h)

Short Message Service is available between Home Country Service Centre and roamed mobile station.

If either the HPLMN or VPLMN contain GSM Network Entities which are supplied by more than one manufacturer, then the test cases should be repeated for each manufacturer. Therefore if HPLMN(a) contains HLR and GMSC from "m" suppliers, and the VPLMN(b) contains VMSC from "n" suppliers, then potentially the tests should be performed m*n times. The actual number of repeats of the test cases is for bilateral agreement between the HPLMN and VPLMN. However if agreement is not straightforward, it is for the HPLMN to decide the scope of the repeating of test cases, because it is ultimately responsible to its customers for the service ed when roaming.

An associated optional objective is to use the Toll Ticketing function of the VMSC to generate a live data file, which is used by the TADIG Stage 3 testing. After transfer to the HPLMN via TADIG processes, the HPLMN may use the information from the test results to validate the details of the Toll tickets, however this is not part of the GSM Association IREG roaming testing.

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 t activity by both PLMN (a) and PLMN (b).

Accordingly, the program of testing forms three distinct components. (i)

HPLMN(a) issues pre-programmed SIMs and programmed HLR

(ii)

PLMN(b) performs tests

(iii)

PLMN(b) and HPLMN(a) discuss results.

It is recognized that some parts of this specification are of greater priority than others. The test cases concerning the “Basic Service" (Section 2.1) are of greater priority than those for the “Supplementary Services” (Section 2.2).

It is anticipated that further updated issues will be made in response to IREG comments and following experience of testing. It is anticipated that further Issues will be needed to extend the testing beyond GSM phase 1.

IR24 General

4(41)


1.5

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

1.5.1

Equipment

(a)

Two Mobile Equipments supplied by VPLMN(b)

(b)

Two PSTN telephones in PSTN(b)

(c)

Two 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) (ii)

(d)

Spare cards in case of failure Allocation from different HLRs

Two SIMs supplied by VPLMN(b) It is expected that manual selection will be used to select VPLMN(b) when using the SIMs supplied by HPLMN(a). To facilitate subsequent automatic selection it is required that bits b6 and b5 of byte 2 of the SIM Service Table (Data-field 38) be set to "1", and the chosen VPLMN is in the PLMN Selector (Data-field 30) In order to replicate the service that general roamers will encounter, it is required that any SIM used in the tests shall have one access class out of the classes 0-9 defined. No other access class (e.g. 10 or 11-15) shall be defined. It is recommended that on any new SIM the Location Update Status field is set to "Status not updated" before the tests start (bit b2 set to "0" and bit b1 set to "1", of byte 11 of Data-field 7E).

1.5.2

Test Equipment

(a)

The availability of a CCITT # 7 tester able to decode SC, TCAP and MAP is highly advisable, but not strictly necessary for these tests. However it is essential for any analysis of test case failures.

(b)

Clock capable of being used to allow testing personnel to record call start and chargeable start ( i.e. answer) time of calls to an accuracy of better than five seconds. If possible, the clock shall be adjusted to be in alignment with the internal MSC clock which is used for the Toll Ticketing function.

(c)

Stopwatch capable of measuring perceived chargeable duration of calls to an accuracy of one second.

IR24 General

5(41)


2

TEST CASES The test cases are in three groups: Basic Service (Mobility Management and Telephony) Supplementary Services Short Message Service (Point to point) The test configuration is shown in Figure 1 below. It is anticipated that it may be necessary to monitor both signaling messages and voice calls on any of the Network Entity interfaces shown in the diagram. However this is not a firm requirement for this test specification. The results of the test cases shall be recorded in Appendix A.

Figure 1: Test case Configuration

1. regular scenario is PSTN (b2) > MS1 (a) w. Call Forw. to > PSTN (b1) 2. regular scenario PSTN (b2) > MS1(a) 3. regular scenario MS1(a) > MS2(a) 4. Regular scenario MS1(a) > PSTN (c1) 5. Regular scenario MS1(a) > PSTN (a) To provide valid toll ticketing recording, then both the clock used to note call start and finish times for the test result sheets, and the internal VMSC clock must be checked against each other and set to an accuracy of better than five seconds. Note the VMSC clock must only be altered in conjunction with local operating rules and procedures because all Toll Tickets will be affected by any alteration.

2.1

Basic Service Test Cases It should be noted that no supplementary services are active during the Test cases which are described in Section 2.1.

2.1.1

Location Update by MS(a) in VPLMN(b)

Preconditions:

MS1 contains SIM of HPLMN(a) No VLR record exists for MS. HLR record contains basic and supplementary service information.

Action:

Power-up MS1(a) and perform location registration on VPLMN(b) Check VLR record for the IMSI/MSISDN of MS1.

Expected Reult:

Successful result if VLR record is identical to the pre-testing information supplied by PLMN(a). Unsuccessful result if any of the basic and supplementary services tested by this document or all of the information is missing.

Comments:

This test case confirms operation of Update Location and Insert Subscriber Data procedures. It checks the of the relevant MAP operations, TCAP processes and SC addressing for both E214 and E164 Global Titles, between the HLR(a) and VMSC(b).

IR24 General

6(41)


2.1.2

Operator Control of Service

A) Location Cancellation for MS(a) Subscription held in VPLMN(b). Preconditions:

VLR in VPLMN(b) contains subscription information for MS(a)

Action:

HPLMN(a) personnel deletes MS(a) subscription from HLR either using HLRs Man-Machine Interface or via istrative Data Centre (ADC) input to HLR. Check VLR for record of MS(a). Establish a MOC from MS(a).

Expected Result: Successful result if VLR record for MS (a) has been erased and when the established communication is cut. Comments:

This test case confirms that the "cancel location" procedure operates correctly and cuts the communication.

B) Operator Determined Barring (ODB) for All Outgoing Calls and All Incoming Calls when on Roaming of MS(a) Preconditions:

VLR in VPLMN(b) contains subscription information for MS(a)

Action:

HPLMN(a) personnel activates ODB for All Outgoing Calls and All Incoming Calls when on Roaming for MS(a) from HLR either using HLR’s Man-Machine Interface or via istrative Data Centre (ADC) input to HLR.

Expected Result: Successful result if VLR record for MS(a) contains ODB information and none of the call attempts is successful. Comments:

This test case confirms that ODB procedures operate correctly.

2.1.3

MS1(a) Calls MS2(a), Both Roamed In VPLMN(b)

Preconditions:

MS1(a) and MS2(a) have location updated successfully in VPLMN(b).

Action:

MS1(a) establishes call to MS2(a). Call answered and held for one minute. Quality assessed.

Expected Result: Successful result if call is established in 30 seconds, and call is stable in unanswered and answered phases, and there is no perceptible echo to either , and call remains in intelligible/high quality conversation phase for one minute. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. This test will also confirm the correct delivery of CLI information (or lack thereof) in a roaming scenario. Comments:

This test case confirms Mobile Originated and Mobile Terminated call sequences for roamers. It checks the of the Provide Roaming Number MAP operation between PLMN(a) and PLMN(b). It checks the ability to establish international call between the two PLMNs using roaming numbers. It implies the ability of the PLMNs to disable excessive instances of echo control devices.

2.1.4

PSTN Telephone In Country Containing PLMN(b) Calls MS1(a), Which Has Roamed To VPLMN(b), But The VLR Has Lost The Record For MS1(a). PSTN Telephone(b2) Calls MS1(a) (VLR has lost the record for MS1(a) )

Preconditions:

MS1(a) does not have a record in VMSC(b) but HLR(a) indicates that MS1 (a) is roamed to VMSC(b). MS1(a) is active, but has not location updated in (periodic, normal or IMSI attach) since VLR record was removed.

Action:

PSTN telephone(b2) calls MS1(a). If call is successfully established, then maintain answered call for one minute. Assess quality. If call attempt returns "System Failure" message, then make MS1(a) perform a location update, and repeat this test case.

Expected Result: Successful result if either first call-attempt is established or "System Failure" message is returned within 30 seconds. In addition the answered call, whether establish on the first attempt or after the location update, has no perceptible echo to either , and that an acceptable quality connection can be maintained. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. This test will also confirm the correct delivery of CLI information (or lack thereof) in a roaming scenario.

Comment:

This test case confirms the VLR recovery mechanism, which may use the Send Parameters MAP operation. It also checks that the Gateway MSC (in PLMN(a)) correctly inserts an echo cancellation device, and implies that other instances of echo control devices have been correctly configured.

2.1.5

PSTN Telephone In Country Containing PLMN(b) Calls MS(a), Which Has Roamed To VPLMN(b), But Has Performed IMSI Detach. PSTN Telephone(b2) Calls MS1(a) Roamed To Country(b) - IMSI Detached (Power off)

Precondition:

MS(a) is detached or deed in the VLR in VPLMN(b) but VLR(b) contains a record for MS(a)

Action:

Check that the subscriber is detached in the VLR, if possible. Attempt a call from PSTN telephone(b2) to MS1(a)

Expected Result: Successful result if PSTN telephone(b2) receives an announcement that MS1(a) cannot be reached or is unavailable.

IR24 General

7(41)


Comments:

IR24 General

This test case confirms that the "absent subscriber" reason is given as the result of a roaming number enquiry to the VLR(b) where the MS(a) has performed an IMSI detach. The detach status of the subscriber should be checked in the VLR, because the switching-off procedure of a Mobile does not guarantee that the subscriber will be detached, because no acknowledgement message is sent from the VLR to the MS. The announcement may be in the language of PLMN(a), as it can be raised at the GMSC(a), but can also be in the language of the PSTN in the country containing PLMN(b).

8(41)


2.1.6

PSTN Telephone In Country Containing PLMN(b) Calls MS(a), Which Has Roamed To VPLMN(b), But Is Not Able To Respond To Paging or Pre-Paging (Battery off) PSTN Telephone(b2) Calls MS1(a) Roamed To Country(b) - No Response to Paging or Pre-Paging (Battery off)

Pre-Check:

Check if the HPLMN(a) and PLMN(b) Pre-paging, and HPLMN(a) sets a “Pre-paging ed” parameter in MAP_SEND_ROUTING_INFORMATION and MAP_PROVIDE_ROAMING_NUMBER. (YES/NO)

If:

NO continue with A. YES continue with B

A) Paging Precondition: Action:

MS1(a) is attached. Disable MS(a) so that it is unable to respond to paging [Note MS(a) must not send IMSI Detach message, while being disabled]. Check that the subscriber is attached in the VLR, if possible. Immediately attempt a call from PSTN telephone(b2) to MS1(a)

Expected Result: Successful result if PSTN telephone(b2) receives an announcement in the language of PLMN(b) that MS1(a) cannot be reached. Comments:

This test case confirms that the correct response is given when a call is made to a roamed mobile that does not respond to paging. Note that there will be some delay before the failure announcement is given while the paging is performed. The announcement will be in the language of PLMN(b).

B) Precondition:

Pre-Paging MS1(a) is attached. HPLMN(a) and PLMN(b) Pre-paging, and HPLMN(a) sets a “Pre-paging ed” parameter in MAP_SEND_ROUTING_INFORMATION and MAP_PROVIDE_ROAMING_NUMBER.

Action:

Disable MS(a) so that it is unable to respond to pre-paging [Note MS(a) must not send IMSI Detach message, while being disabled]. Check that the subscriber is attached in the VLR, if possible. Immediately attempt a call from PSTN telephone(b1) to MS1(a)

Expected Result: Successful result if PSTN telephone(b1) receives an announcement in the language of HPLMN(a) that MS1(a) cannot be reached. Comments:

This test case confirms that the correct response is given when a call is made to a roamed mobile that does not respond to Pre-paging. Note that there will be some delay before the failure announcement is given while the Pre-paging is performed. The announcement will be in the language of HPLMN(a).

2.2

Supplementary Service Test Cases Test cases 2.2.1 to 2.2.8 require that the MS(a) is able to manage its own Supplementary Service registration and activation status. The Call Forwarding test cases should be performed by using the "+" key. It should be noted that only those Supplementary services referenced in the "Preconditions" notes are to be active.

2.2.1

Barring Of All Outgoing Calls BAOC]

Preconditions:

HLR entry contains "SS:BAOC:Active" [Set by MS]

Action:

(i) MS(a) attempts Emergency Call [112 keyed on MS] (ii) MS(a) attempts call to PSTN.

Expected Result: Successful result if call "i" succeeds and call "ii" fails. (i) MS(a) attempts Emergency Call [112 keyed on MS] (ii) MS(a) attempts call to PSTN. Comment:

This test case confirms the of this Supplementary Service by the VPLMN (b). It also indicates that Emergency Services are available to visitors from HPLM(a).

2.2.2.

Barring Of Outgoing International Calls [BOIC]

Preconditions:

HLR entry contains "SS:BOIC:Active". [Set by MS]

Action:

(i) MS(a) attempts call to PLMN(b) or PSTN(b) General Operator Service [The call should be made to an Operator Position, which uses a signaling system to obtain the identity of the Calling Party] (ii) MS(a) attempts outgoing call to Home PLMN Country.

Expected Result: Successful result if call "i" succeeds and call "ii" fails. (i) MS(a) attempts call to PLMN(b) or PSTN(b) General Operator Service [The call should be made to an Operator Position, which uses a signaling system to obtain the identity of the Calling Party] (ii) MS(a) attempts outgoing call to Home PLMN Country. Comment:

This test case confirms the of this Supplementary Service by the VPLMN(b). It also indicates that General Operator Services are available to visitors from HPLMN(a), that any special routing operates successfully, and that any Calling Party information displayed to the operator is appropriately presented.

IR24 General

9(41)


A

2.2.3

Barring Of Outgoing International Calls except To Home PLMN Country [BOICexHC]

Pre-Check

Check if the VPLMN does the SS:BOICexHC. (YES/NO) YES continue with A. NO continue with B.

2.2.3.1

Activated Service is BOICexHC (VPLMN s SS: BOICexHC)

Preconditions: HLR entry contains "SS: BOIC ex HC: Active" [Set by MS] Action:

(i) MS(a) attempts an outgoing call to Home-PSTN-telephone(a). (ii) MS(a) attempts a call to the country, where the MS is presently located by making use of the international number format. (iii) MS(a) attempts an international call to any other country than mentioned in (i) or (ii). (International Format should be +CC ...)

Expected Result: Successful result if calls of test cases "i" and "ii" succeeds, and the call of test case "iii" fails.

B

2.2.3.2

Activated Service is BOICexHC (VPLMN does not SS: BOICexHC):

Preconditions: HLR entry contains "SS: BOICexHC: Active" [Set by MS] Action:

(i) MS(a) attempts a call to local PSTN. (ii) MS(a) attempts outgoing call to Home PLMN country.

Expected Result: Successful result, if the call (i) succeeds and call (ii) fails.

Comment:

This test case confirm the of this Supplementary Service by the VPLMN(b). In the case VPLMN(b) does not the SS: BOICex HC then the switch makes a Functional fallback because it s BOIC.

2.2.4

Barring Of All Incoming Calls (BAIC / BAICroaming)

Pre-Check:

Check if the VPLMN does the SS: BAICroaming. (YES / NO)

If:

YES continue with A. NO continue with B.

A)

Preconditions: HLR no entry for Barring of all incoming calls when roaming in VPLMN.

Action:

Preconditions: HLR no entry for Barring of all incoming calls when roaming in VPLMN. MS(a) in VPLMN (b) activates the SS: BAICroaming PSTN (b) calls MS(a)

Expected Result: Successful result, if calls fail B)

Preconditions: HLR no entry for Barring of all incoming calls.

Action:

Preconditions: HLR no entry for Barring of all incoming calls. MS(a) in VPLMN (b) activates the SS: BAIC PSTN(b) calls MS(a)

Expected Result: Successful result, if calls fail Comment:

This test case confirms the of the activation of this Supplementary Service when roaming inside VPLMN.

2.2.5

Call Forwarding on Not Reachable (CFNRC -Before IMSI Detach TAKE BATTERY OFF WHILE PHONE IS SWITCHED ON)

Preconditions:

HLR entry for MS(a1) contains "SS : CFNRc: Active "Forwarded -to-address is PSTN telephone(b1). [Set by MS] In some PLMNs there are HLR restrictions on ing a forwarded-to-address which is outside the HPLMN country. There are also some PLMNs in which MSCs prevent the invocation of a call forward towards a distant country. In these cases the forwarded-to-address shall be MS(a2). If MS(a2) cannot be used, then the forwarded-to-address shall be PSTN telephone(a). MS (a1) is attached. If used, MS(a2) is attached.

Action:

Disable MS(a1) so that it is unable to respond to paging [Note MS(a1) must not send IMSI Detach message, while being disabled. This can be achieved by removing the battery while the phone is switched on]. Immediately attempt a call from PSTN telephone(b2) to MS(a1). Answer resultant call to PSTN telephone(b1), MS(a2) or PSTN telephone(a).

Expected Result: Successful result if the call is completed to PSTN(b1), MS(a2) or PSTN(a) and the call quality is acceptable. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. Optionally, PSTN(b2) may receive an announcement that the call is being forwarded. Comments:

This test case confirms that CFNRc (before IMSI detach) operates correctly and implies that echo cancellers are correctly configured. Note the announcement could be in the language of PLMN(b), as the call was forwarded by the VMSC(b).

IR24 General

10(41)


2.2.6

Call Forwarding on Not Reachable (CFNRC -After IMSI Detach SWITCH THE PHONE OFF)

Preconditions:

HLR entry for MS(a1) contains "SS CFNRc: Active: Forwarded-to-address is PSTN telephone(b1)". [Set by MS] In some PLMNs there are HLR restrictions on ing a forwarded-to-address which is outside the HPLMN country. There are also some PLMNs in which MSCs prevent the invocation of a call forward towards a distant country. In these cases the forwarded-to-address shall be MS(a2). If MS(a2) cannot be used, then the forwarded-to-address shall be PSTN telephone(a). MS (a1) is detached or deed in the VLR, but the VLR contains a record for MS(a1). If used, MS(a2) is attached.

Action:

Check that the subscriber MS(a1) is detached in the VLR, if possible. Attempt a call from PSTN telephone(b2) to MS(a1).

Answer

resultant call to PSTN(b1), MS(a2) or PSTN(a).

Expected Result: Successful result if the call is completed to PSTN(b1), MS(a2) or PSTN(a) and the call quality is acceptable. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. Optionally, PSTN telephone(b2) may receive an announcement that the call is being forwarded. Comments:

This test case confirms that CFNRc (after IMSI detach) operates correctly and implies that echo cancellers are correctly configured. The detached status of the subscriber should be checked in the VLR, because the switching-off procedure of a Mobile does not guarantee that the subscriber will be detached, because no acknowledgement message is sent from the VLR to the MS. Note the announcement will be in the language of PLMN (a) as the call was forwarded by GMSC(a).

2.2.7

Call Forwarding on Busy (CFB)

Preconditions:

HLR entry for MS (a1) contains SS: CFB: Active: Forwarded-to-address is PSTN telephone (b1). [Set by MS] In some PLMNs there are HLR restrictions on ing a forwarded-to-address which is outside the HPLMN country. There are also some PLMNs in which MSCs prevent the invocation of a call forward towards a distant country. In these cases the forwarded-to-address shall be MS(a2). If MS(a2) cannot be used, then the forwarded-to-address shall be PSTN telephone(a).

Action:

MS (a1) is in conversation state. If used, MS(a2) is attached. Attempt a call from PSTN telephone(b2) to MS(a1). Answer resultant call to PSTN(b1), MS(a2) or PSTN(a).

Expected Result: Successful result if indicate the call is completed to PSTN(b1), MS(a2) or PSTN(a) and the call quality is acceptable. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. Optionally, PSTN telephone(b2) may receive an announcement that the call is being forwarded. Comments:

This test case confirms that CFB operates correctly.

2.2.8

Call Forwarding on No Reply (CFNRY)

Preconditions:

HLR entry for MS (a1) contains "SS: CFNRy: Active: Forwarded-to-address is PSTN telephone (b1). [Set by MS] MS(a1) is attached and idle. If used, MS(a2) is attached.

Action:

MS(a) initiates an “Interrogate Call Forward Information”. MS(a) displays information. Attempt a call from PSTN telephone(b2) to MS(a1). After a period of time during which MS(a1) "rings", call is diverted to PSTN(b1), MS(a2) or PSTN(a) where it is answered.

Expected Result: Successful result if MS(a) displays equivalent information to that stored in HLR and if MS(a1) "rings" for length of time equal to "No Reply Timeout" value stored in HLR, and call is completed to PSTN(b1), MS(a2) or PSTN(a), and the call quality is acceptable. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. Optionally, PSTN telephone(b2) may receive an announcement that the call is being forwarded. Comments:

This test case confirms that CFNRy operates correctly. It also confirms that the procedure “Interrogate Call Forward Information” operates correctly.

2.3

SMS Test Cases

2.3.1

Mobile ORIGINATED and Terminated Short Message Service (SMS-MO)

Preconditions:

SMS-MO/MT is provisioned in HLR subscription. MS 1(a) and MS2(a) are ed in VPLMN(b).

Action:

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

Expected Result: Successful result if Short Message is correctly delivered within [2] minutes of switching MS 2(a) on. Comments:

IR24 General

This test case confirms correct operation of SMS - Mobile Originated / Terminated Services including "Message Waiting" and "Note MS Present" procedures.

11(41)


2.4

SMS Interworking Test Cases

2.4.1

Information on the testing (SMS-IW)

Preconditions:

Please find below some information about how to perform it. 1. For the whole SMS IW test you will have to switch the MS2 off and wait for at least 2 minutes after you sent the SMS before you switch the phone on again,

2. The several times you will have to report consist on the time you have a - sent the SMS b - switched the MS2 on (and not when UL is done) c - received the SMS on the MS2 3. Please do not forget to fill, sign and fax us the Appendix with all our required and selected test cases. (see 2nd sheet "IR24 Setup Info & COMPL. CERT.")

2.4.2.1

Details of the tests In order to be able to proceed the test independently from the roaming partner, SMS IW test can be performed with one SIM cards of the PLMN (a) and one SIM card of the PLMN (b) both located on the PLMN (b). Therefore, SIM (a) of PLMN (a) has to be able to roam on PLMN (b), so PLMN (a) and (b) must have a roaming agreement. In the case of a roaming agreement as described above, the tests to be performed are the C.2.4.2.1 and C.2.4.2.2

C.2.4.2.1

Mobile (a) of PLMN a

C.2.4.2.2

Mobile (b) of PLMN b

PLMN b

2.4.2.1

SMS Test Results in case (WITH ROAMING AGREEMENT), Details of the test C.2.4.2.1

2.4.2.1

Mobile(a) in PLMN(b) to Mobile(b) in PLMN(b) SM S


MSC/VLR where is mobile a

SMS Submitt Cg SC @ = MSC/VLR (b) Cd SC @ = SMS-C (a) SMS Submitt ack

SMS-C (a)

SRI for SM Cg SC @ = SMS-C (a) Cd SC @ = MSISDN (b)

HLR of mobile b

SRI for SM ack

SMS-C (a)

SMS Delivered Cg SC @ = SMS-C (a) Cd SC @ = MSC/VLR (b) Mobile (b) of PLMN b

MSC/VLR where is mobile b

SMS Delivered ack

PLMN b

IR24 General

SMS-C (a)

PLMN a

12(41)


2.4.2.2

Details of the test C.2.4.2.2 (WITH ROAMING AGREEMENT)

2.4.2.2

Mobile(b) in PLMN(b) to Mobile(a) in PLMN(b)

SM S



SMS Submitt Cg SC @ = MSC/VLR (b) Cd SC @ = SMS-C (b) SMS Submitt ack

SMS-C (b)

SRI for SM Cg SC @ = SMS-C (b) Cd SC @ = MSISDN (a) SMS-C (b)

SRI for SM ack

HLR of mobile a

SMS Deliver Cg SC @ = SMS-C (b) Cd SC @ = MSC/VLR (b) Mobile (a) of PLMN a


SMS Deliver ack

SMS-C (b)

PLMN b

2.4.3

PLMN a

Tests without roaming agreement If PLMN (a) and (b) do not have roaming agreements, the tests described above can not be performed, therefore, tests for SMS IW has to be performed in coordination with the SMS IW partner. In the case of non roaming agreement, the tests to be performed are the C.2.4.3.1 and C.2.4.3.2.

.3.1 C.2.4



.3.2 C.2.4

PLMN b

2.4.3.1

Details of the test C.2.4.3.1 (NON ROAMING AGREEMENT)

2.4.3.1

Mobile (b) in PLMN (b) to Mobile (a) in PLMN (a)

PLMN a

SMS Submitt Cg SC @ = MSC/VLR (b) Cd SC @ = SMS-C (b)


SMS Submitt ack

SMS-C (b)

SRI for SM Cg SC @ = SMS-C (b) Cd SC @ = MSISDN (a)

Mobile (b) of PLMN b SMS-C (b)

SRI for SM ack

HLR of mobile a

SMS Deliver Cg SC @ = SMS-C (b) Cd SC @ = MSC/VLR (a) SMS Deliver ack

SMS-C (b)

PLMN b

IR24 General

PLMN a

13(41)




IR24 General

14(41)


2.4.3.2


2.4.3.2

Mobile (a) in PLM (a) to Mobile (b) in PLMN (b)

SMS Submitt Cg SC @ = MSC/VLR (a) Cd SC @ = SMS-C (a) SMS-C (a)

SMS Submitt ack

SRI for SM Cg SC @ = SMS-C (a) Cd SC @ = MSISDN (b) SRI for SM ack


Mobile (a) of PLMN a SMS-C (a)

HLR of mobile b

SMS Deliver Cg SC @ = SMS-C (a) Cd SC @ = MSC/VLR (b) Mobile (b) of PLMN b


IR24 General

SMS Deliver ack

SMS-C (a)

PLMN b

PLMN a

15(41)


6

Test case selection and Completion Certificates

6.1

Test case selection and result overview Roaming Scenario to be Tested (H)PLMN (a) 2G / GSM 3G / UMTS 2G / GSM 3G / UMTS

(V)PLMN YES / NO (b) 2G / GSM 2G / GSM 3G / UMTS 3G / UMTS

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

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

Test Case Selection

Requested Test-cases & Description

Results Not Performed

1

YES

2.1.1

Location Update by MS(a) in VPLMN(b)

1

YES

2.1.2

A) Location Cancellation for MS(a) Subscription held in VPLMN(b).

1

YES

2.1.2

B) Operator Determined Barring (ODB) for All Outgoing Calls and All Incoming Calls when on Roaming of MS(a)

1

YES

2.1.3

MS1(a) Calls MS2(a), Both Roamed In VPLMN(b)

1

YES

2.1.4

PSTN Telephone In Country Containing PLMN(b) Calls MS1(a), Which Has Roamed To VPLMN(b), But The VLR Has Lost The Record For MS1(a).

1

YES

2.1.5

PSTN Telephone In Country Containing PLMN(b) Calls MS(a), Which Has Roamed To VPLMN(b), But Has Performed IMSI Detach.

Not Performed

Not Performed Not Performed Not Performed Not Performed

1

YES

2.1.6

1

YES

2.2.1

Barring Of All Outgoing Calls BAOC]

Not Performed

1

YES

2.2.2.

Barring Of Outgoing International Calls [BOIC]

Not Performed Not Performed

1

YES

2.2.3

Barring Of Outgoing International Calls except To Home PLMN Country [BOICexHC]

1

YES

2.2.4

Barring Of All Incoming Calls (BAIC / BAICroaming)

Not Performed

2.2.5

Call Forwarding on Not Reachable (CFNRC -Before IMSI Detach TAKE BATTERY OFF WHILE PHONE IS SWITCHED ON)

Not Performed Not Performed

YES

n/a (see original entries in IR24 TEST CASES)

Not Performed

PSTN Telephone In Country Containing PLMN(b) Calls MS(a), Which Has Roamed To VPLMN(b), But Is Not Able To Respond To Paging or Pre-Paging (Battery off)

1

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

1

YES

2.2.6

Call Forwarding on Not Reachable (CFNRC -After IMSI Detach SWITCH THE PHONE OFF)

1

YES

2.2.7

Call Forwarding on Busy (CFB)

1

YES

2.2.8

Call Forwarding on No Reply (CFNRY)

1

YES

2.3.1

Mobile ORIGINATED and Terminated Short Message Service (SMS-MO)

Not Performed

1

YES

2.4.1

1

YES

2.4.2.1

Information on the testing (SMS-IW) SMS Test Results in case (WITH ROAMING AGREEMENT), Details of the test C.2.4.2.1

1

YES

2.4.2.2

Details of the test C.2.4.2.2 (WITH ROAMING AGREEMENT)

1

YES

2.4.3.1


1

YES

2.4.3.2


1

No

19.1.1

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

1

No

19.2.1


1

No

19.3.1


1

No

19.4.1


1

No

19.5.1


1

No

19.6.1


1

No

19.7.1


Not Performed

1

No

19.8.1


#REF!

1

No

19.9.1


#REF!

1

No

19.10.1


#REF!

1

YES

20.1.1

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

1

YES

20.2.1


1

YES

20.3.1

OPERATOR

-SPEC. TEST CASE HEADER 20.3.1

1

YES

20.4.1

OPERATOR


1

YES

20.5.1

OPERATOR


1

YES

20.6.1


1

YES

20.7.1

OPERATOR


1

YES

20.8.1

OPERATOR


1

YES

20.9.1

OPERATOR


1

YES

20.10.1

OPERATOR


n/a

n/a (see original entries in IR24 TEST CASES)

#REF! #REF! #REF!

41

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

6.2

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

This certificate confirms the successful completion of selected Tests in 6.1 for Mobile Subscribers of. HPLM PLMN Network visited

HPLMN > field in TEST CASE PAGE entry H25 VPLMN > field in TEST CASE PAGE entry H26

Other comments

Toll Ticket file is being forwarded from PLMN via TADIG procedures. (Delete if not applicable)

VPLMN > field in TEST CASE PAGE entry H26

HPLMN > field in TEST CASE PAGE entry H25

to

The tests were completed on. Date: The testing team in HPLMN Name: HPLMN TESTER NAME (a) > field in TEST CASE PAGE H28 eMail: Tester@ HPLMN > field in TEST CASE PAGE H30 The testing team in VPLMN Name: TESTER NAME (b) > field in TEST CASE PAGE H31 eMail: Tester@ VPLMN > field in TEST CASE PAGE H33

Signed for HPLMN (a)

Date:

Signed for VPLMN (b)

Date:

End of Completion Certificate

IR24 Setup Info & COMPL. CERT.

16(39)


IR24 General Page

Setup Page

Test Cases Page

Templates Page

TADIG Page

Instructions

IREG 24 Test Results for Mobile Stations of PLMN(a) Roaming to PLMN(b ) A.1.1

Roaming Scenario to be Tested (H)PLMN(a) 2G / GSM 3G / UMTS 2G / GSM 3G / UMTS

(V)PLMN(b) 2G / GSM 2G / GSM 3G / UMTS 3G / UMTS

YES / NO 0 0 0 0

Network Operator Information

A.1.2

all test numbers below, will be used for testing purposes and could be manual changed with different values within a later test, at each time during the test, if it is required. MSISDN MS1 (a) IMSI MS1 (a) MSISDN MS2 (a) IMSI MS2 (a) MSISDN MS2 (b) IMSI MS2 (b) Directory Number (DN) of PSTN telephone (b1) (FORW. TO PARTY at CF-tests) Directory Number (DN) of PSTN telephone (b2) (regular CALLING PARTY) Home PSTN Country number (a)

(H)PLMN (a) (V)PLMN (b) Date of Tests Testing personnel PLMN(a) Tel/Fax: email PLMN (a): Testing personnel PLMN(b) Tel/Fax: email PLMN (b): HLR Identity/Identities HLR Manufacturer(s) HLR Software Build Level(s) GMSC Identity/Identities GMSC Manufacturer(s) GMSC Software Build Level(s) VMSC Identity/Identities VMSC Manufacturer(s) VMSC Software Build Level(s) SMS-SC Identity / Identities SMS-SC Manufacturer(s) SMS-SC Software Build Level(s) Comments

MSISDN MS1 (a) f.A1.2 I16 IMSI MS1 (a) f.A1.2 I17 MSISDN MS2 (a) f.A1.2 I18 IMSI MS2 (a) f.A1.2 I19 MSISDN MS2 (b) f.A1.2 I20 used for SMSIMSI MS2 (b) f.A1.2 I21 used for SMS-IW PSTN (b1) from no. I22 used for CFx PSTN (b2) from no. I23 (regular A-Pty) HPLMN PSTN (a) from field I24

HPLMN > field in TEST CASE PAGE entry H25 VPLMN > field in TEST CASE PAGE entry H26 HPLMN TESTER NAME (a) > field in TEST CASE PAGE H28 Tester@ HPLMN > field in TEST CASE PAGE H30 TESTER NAME (b) > field in TEST CASE PAGE H31 Tester@ VPLMN > field in TEST CASE PAGE H33

Toll Ticket Configuration

A.1.3

Call Toll Ticketing in use at VMSC? Supplementary Service activity Toll Ticketing in use at VMSC? Toll Ticketing in use at GMSC for Roaming call legs? Will VMSC Toll Ticket file be transferred to VPLMN Computing Centre? Will VMSC Toll Ticket file be transferred to the HPLMN from VPLMN? Method of transfer of Toll Ticket File to HPLMN [Via TADIG mechanism /other] Comments

[Yes/No] [Yes/No] [Yes/No] [Yes/No] [Yes/No]

Notes: 1. If Toll Ticketing is not in use then the line items marked with an asterisk (*) may be omitted from these Test Result Sheets. 2. If Supplementary Service activity Toll Ticketing is not in use there is no need to write the time at the lines marked with a plus (+).

Basic Service Test Cases

A 2.1

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

A 2.1.1

Location Update by MS(a) in VPLMN(b) action: . . . . . .

Power-up MS1(a) and perform location registration on VPLMN(b) Check VLR record for the IMSI/MSISDN of MS1.

. . . . .

click Help forTime Macro

expected result: . . . . . .

Successful result if VLR record is identical to the pre-testing information supplied by PLMN(a). Unsuccessful result if any of the basic and supplementary services tested by this document or all of the information is missing.

VLR Record contents: MSISDN MS1 (a) IMSI MS1 (a) Teleservices SPEECH SMS MO SMS MT Fax Bearer Services Supplementary Services BAOC BOIC BOICexHC CFB CFNRy CFNRc CW CH MPTY AOCC AOCI Others HLR E164 Address Comments

MSISDN MS2 (a) IMSI MS2 (a) Teleservices SPEECH SMS MO SMS MT Fax Bearer Services Supplementary Services BAOC BOIC BOICexHC CFB CFNRy CFNRc CW CH MPTY AOCC

[Y/N] [Y/N] [Y/N] [Y/N]

[Y/N] [Y/N] [Y/N] [Y/N] [Y/N] [Y/N]

C Number C Number C Number [Y/N] [Y/N] [Y/N] [Y/N] [Y/N]

[Y/N] [Y/N] [Y/N] [Y/N]

[Y/N] [Y/N] [Y/N] [Y/N] [Y/N] [Y/N]

C Number C Number C Number [Y/N] [Y/N] [Y/N] [Y/N]

AOCI Others HLR E164 Address Comments

Testcase Result

IR24 Test Cases

[Y/N]

[ / FAIL / NOT PERFORMED]

Not Performed

17(39)


Signature of Tester

TESTER NAME (b) > field in TEST CASE PAGE H31

Date

Operator Control of Service

A.2.1.2

A) Location Cancellation for MS(a) Subscription held in VPLMN(b). action: HPLMN(a) personnel deletes MS(a) subscription from HLR either using HLRs Man-Machine Interface or via istrative Data Centre (ADC) input to HLR. Check VLR for record of MS(a). Establish a MOC from MS(a). . .


. . . . . . . . .


Successful result if VLR record for MS (a) has been erased and when the established communication is cut.

VLR Record contents prior to cancellation MSISDN MS1(a/b) IMSI MS1 (a/b) VLR record erased? Time delay between HLR deleting subscription and VLR erasing record Comments

Testcase Result


Signature of Tester


[Yes/No] Secs

Not Performed Date

B) Operator Determined Barring (ODB) for All Outgoing Calls and All Incoming Calls when on Roaming of MS(a) action: . . . . . . . . . . .

HPLMN(a) personnel activates ODB for All Outgoing Calls and All Incoming Calls when on Roaming for MS(a) from HLR either using HLR’s Man-Machine Interface or via istrative Data Centre (ADC) input to HLR.

Check VLR for record of MS(a). MSISDN of MS1 (a) IMSI MS1(a) Operator performed barring from HLR

[Yes/No]

VLR record contains barring tags Perform a call from MS(a). Is it successful? Call MS(a). Is it successful? Comments

A 2.1.3

Testcase Result


Signature of Tester


Not Performed

Date

MS1(a) Calls MS2(a), Both Roamed In VPLMN(b) action: . . . . . . . . . .


[Yes/No] [Yes/No] [Yes/No]

.

MS1(a) establishes call to MS2(a). Call answered and held for one minute. Quality assessed. Info

Successful result if call is established in 30 seconds, and call is stable in unanswered and answered phases, and there is no perceptible echo to either , and call remains in intelligible/high quality conversation phase for one minute. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. This test will also confirm the correct delivery of CLI information (or lack thereof) in roaming scenario. MSISDN of originatingaMS (i.e. MS1(a))

Info


IMSI MS1(a) Number keyed into MS1 (a) IMSI MS2(a) Time of start of call (i.e. SEND key operation) (hrs:mins:secs) Delay between SEND key operation at MS1(a) and MS2(a) alerting secs Time of perceived answer of call (hrs:mins:secs) Time of end of call (hrs:mins:secs) Chargeable Call Duration (i.e. perceived answer until end of call. Duration must be 60sec or more.) secs Quality of call [Excellent, Good, Fair, Poor, Bad] Echo present? [Yes/No] If Yes, to which MS? [MS1(a) / MS2(a)] (i) Is the MSISDN of MS1(a) displayed at MS2(a) in proper format? IF NO, what does MS2(a) display? (j) Comments

Testcase Result


Signature of Tester


A 2.1.4a

2

. . . . . . . . . . .

-3

Info 0 1 1 2

3 0 0 0

[Yes/No]

Not Performed

Date

PSTN Telephone(b2) Calls MS1(a) (VLR has lost the record for MS1(a) ) action:


Alert Time

Info

Info

Info

PSTN telephone(b2) calls MS1(a). If call is successfully established, then maintain answered call for one minute. Assess quality. If call attempt returns "System Failure" message, then make MS1(a) perform a location update, and repeat this test case. Alert Time


Successful result if either first call-attempt is established or "System Failure" message is returned within 30 seconds. In addition the answered call, whether establish on the first attempt or after the location update, has no perceptible echo to either , and that an acceptable quality connection can be maintained. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. This test will also confirm the correct delivery of CLI information (or lack thereof) in a roaming scenario.

Directory Number (DN) of PSTN telephone (b2) Number of MS1(a) dialled by PSTN telephone (b2) IMSI MS1(a) Time of start of call (i.e. SEND key operation) (hrs:mins:secs) Delay between dialing last digit of MSISDN of MS1(a) at PSTN telephone(b2) secs Time of perceived answer of call (hrs:mins:secs) (hrs:mins:secs) Time of end of call (hrs:mins:secs) Chargeable Call Duration (i.e. perceived answer until end of call. Duration must be 60sec or more.) secs Was first call successful? [Yes/No] Quality of successful call [Excellent, Good, Fair, Poor, Bad] Echo present? [Yes/No] If Yes, to which party? Is the Directory Number (DN) of Telephone(b) displayed at MS1(a) in proper format? IF NO, what does MS1(a) display? Comments

A 2.1.4b

Testcase Result


Signature of Tester


Info

-3

Info 0 1 1 2

3 0 0 0

[PSTN/MS1(a)] [Yes/No]

Not Performed Date

MS1(a) performs a location update - PSTN(b) calls MS1(a) action: . . . . . . .


2

. . . .

PSTN telephone(b2) calls MS1(a). If call is successfully established, then maintain answered call for one minute. Assess quality. If call attempt returns "System Failure" message, then make MS1(a) perform a location update, and repeat this test case.

expected result:

Successful result if either first call-attempt is established or "System Failure" message is returned within 30 seconds. In addition the answered call, whether establish on the first attempt or after the location update, has no perceptible echo to either , and that an acceptable quality connection can be maintained. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. This test confirm the correct Directory Number (DN)will of also PSTN telephone (b2) delivery of CLI information (or lack thereof) in a roaming scenario. . . . . . .

Number of MS1(a) dialled by PSTN telephone (b2)

IR24 Test Cases

Info

18(39)


IMSI MS1(a) Time of start of call (i.e. SEND key operation) Delay between dialing last digit of MSISDN of MS1(a) at PSTN telephone(b2) and MS1(a) alerting Time of perceived answer of call

Info

(hrs:mins:secs)

(hrs:mins:secs)

0

secs

1 1

0 0

2

0

(hrs:mins:secs)

Time of end of call (hrs:mins:secs) Chargeable Call Duration (i.e. perceived answer until end of call. Duration must be 60sec or more.) secs Was location update sequence originated from the Mobile Station necessary ? [Yes/No] Yes Quality of successful call [Excellent, Good, Fair, Poor, Bad] Echo present? [Yes/No] If Yes, to which party? [PSTN/MS1(a)] Is the Directory Number (DN) of Telephone(b) displayed at MS1(a) in proper format? [Yes/No]

IR24 Test Cases

19(39)


IF NO, what does MS1(a) display? Comments

A 2.1.5

Testcase Result


Signature of Tester


Date

PSTN Telephone(b2) Calls MS1(a) Roamed To Country(b) - IMSI Detached (Power off) action: . . . .


Not Performed

. .

Check that the subscriber is detached in the VLR, if possible. Attempt a call from PSTN telephone(b2) to MS1(a)

. . . . .

expected result:

Successful result if PSTN telephone(b2) receives an announcement that MS1(a) cannot be reached or is unavailable.

. . . . . .

Info

Directory Number (DN) of PSTN telephone (b2) Number of MS1(a) dialled by PSTN telephone (b2)

Info

IMSI MS1(a) Time of start of call (i.e. last digit dialled) Time of start of "not reachable" announcement Time of end of call Chargeable Call Duration (i.e. perceived answer until end of call) Language of announcement Text of announcement Comments

click Help

A 2.1.6

0

(hrs:mins:secs)

1

(hrs:mins:secs) (hrs:mins:secs)

1 2

0 0

secs

Testcase Result


Signature of Tester


Not Performed Date

PSTN Telephone In Country Containing PLMN(b) Calls MS(a), Which Has Roamed To VPLMN(b), action: . . . . . . . . . . .


Disable MS(a) so that it is unable to respond to paging [Note MS(a) must not send IMSI Detach message, while being disabled]. Check that the subscriber is attached in the VLR, if possible. Immediately attempt a call from PSTN telephone(b2) to MS1(a)

Disable MS(a) so that it is unable to respond to pre-paging [Note MS(a) must not send IMSI Detach message, while being disabled]. Check that the subscriber is attached in the VLR, if possible. Immediately attempt a call from PSTN telephone(b1) to MS1(a)

Successful result if PSTN telephone(b2) receives an announcement in the language of PLMN(b) that MS1(a) cannot be reached.

Successful result if PSTN telephone(b1) receives an announcement in the language of HPLMN(a) that MS1(a) cannot be reached.

Does HPLMN(a) and PLMN(b) Pre-Paging? Does HPLMN(a) sets a “Pre-paging ed” parameter in MAP_SEND_ROUTING_INFORMATION and Which test case was executed? [A (Paging) / B (Pre-paging)] Directory Number of calling PSTN telephone(b2) Number dialled by PSTN telephone(b2) e.g. MS1(a) IMSI MS1(a) Time of start of call (i.e. last digit dialled) Time of start of "not reachable" announcement Time of end of call Chargeable Call Duration (i.e. perceived answer until end of call)

[Yes/No] [Yes/No]

Info 0 Info

(hrs:mins:secs) (hrs:mins:secs) (hrs:mins:secs)

0 0 0

1 1 2

0

secs

Language of announcement Text of announcement Comments

0

Testcase Result


Signature of Tester


Not Performed

Date Info

A 2.2

Supplementary Service Test Cases

A 2.2.1i

Barring Of All Outgoing Calls BAOC] action:

Info

Alert Time

(i) MS(a) attempts Emergency Call

. . . .


. . . . . . .

2

-3


Info

MSISDN MS1(a) IMSI MS1(a) Time of activation of BAOC Emergency code keyed [i.e.112] Time of start of emergency call (i.e. SEND key operation) Time of perceived answer of call Time of end of call Chargeable Call Duration (i.e. perceived answer until end of call) Emergency Call successful? Time of deactivation of BAOC Comments

Testcase Result


Signature of Tester


0 Info (hrs:mins:secs)

1


1 1

(hrs:mins:secs)

2

3 0 0 0

secs [Yes/No] (hrs:mins:secs)

2

Not Performed Date

A 2.2.1ii

action:

(ii) MS(a) call to PSTN

. . . .


. . . . . . .


MSISDN MS1(a) IMSI MS1(a)

Time of activation of BAOC

IR24 Test Cases

Info

(hrs:mins:secs)

20(39)

1


A 2.2.2i

Time of start of call (i.e. SEND key operation)

(hrs:mins:secs)

1

Time of end of call PSTN (b) number keyed (enter number in international format) PSTN (b) call successful? Time of deactivation of BAOC Comments

(hrs:mins:secs)

2

[Yes/No] (hrs:mins:secs)

2

Testcase Result


Signature of Tester


Not Performed 0 0 0

Date

Barring Of Outgoing International Calls [BOIC] action: .


Info

. . . .

(i) MS(a) attempts call to PLMN(b) or PSTN(b) General Operator Service [The call should be made to an Operator Position, which uses a signaling system to obtain the identity of the Calling Party]

. . . . . .


MSISDN MS1(a) IMSI MS1(a) Time of activation of BAIC

Info (hrs:mins:secs)

2

(hrs:mins:secs)

0 1 1 2

0 0

Operator Service number or PSTN (b) number keyed

0

Time of start of national PSTN call (i.e. SEND key operation) Delay between SEND key operation and MS(a) receiving alerting indication Time of perceived answer of call Time of end of call Chargeable Call Duration (i.e. perceived answer until end of call) Call routed to correct Operator position? Time of deactivation of BOIC Comments

secs (hrs:mins:secs) (hrs:mins:secs)

secs [Yes/No] (hrs:mins:secs)

0 2 ################ ################

A 2.2.2ii

Testcase Result


Signature of Tester


Not Performed Date

0 0 0

Barring Of Outgoing International Calls [BOIC] action:

(ii) MS(a) attempts outgoing call to Home PLMN Country

.


. . . . . . . . . .


MSISDN MS1(a) IMSI MS1(a) Time of activation of BAIC Time of end of call Home PLMN Country number keyed (enter number in international format +CC) Home PLMN Country call successful? Time of deactivation of BOIC Comments

A 2.2.3

Info

Testcase Result


Signature of Tester



2 2


2

Not Performed

Info

Info

Info

Info

Info Date

0

Barring Of Outgoing International Calls except To Home PLMN Country [BOICexHC] action:

Check if the VPLMN does the SS:BOICexHC. (YES/NO)

. . . .


. . . . . . .

0

expected result:

see below

. . . . . .

General Method of Supplementary Service Configuration Does the switch the SS: BOICexHC?

[MS /HLR operator] [Yes/No]

MSISDN MS1(a) IMSI MS1(a)

A.2.2.3.1

Split into different cases if VPLMN(b) Activated Service is BOICexHC (VPLMN s SS: BOICexHC) action: (i) MS(a) attempts an outgoing call to Home-PSTN-telephone(a). expected result:

Alert Time Info

.

. . . . . .

Info

A.1) (i) Call to Home-PSTN-telephone(a): Home PSTN (a) Country number keyed Time of activation of BOICexHC Time of start of Home PSTN Country call (i.e. SEND key operation) Time of perceived answer of call Time of end of call Time of deactivation of BOICexHC Home PSTN Country call Chargeable Call Duration (i.e. perceived answer until end of call) Results of this test case and comments: Comments

Testcase Result


Signature of Tester


(hrs:mins:secs) (hrs:mins:secs) (hrs:mins:secs)

2

1 1 5

secs

Not Performed

-3

3 0 0 0

1

Date

1 5

A.2) (ii) Call to country where the MS is presently located: PSTN (b2) number of the country keyed, where MS(a) is presently located Time of activation of BOICexHC Time of start of call within the country where the MS(a) is presently located (i.e. SEND key operation) Time of perceived answer of call Time of end of call Time of deactivation of BOICexHC

IR24 Test Cases

(hrs:mins:secs) (hrs:mins:secs) (hrs:mins:secs) 8

21(39)


Chargeable Call Duration (i.e. perceived answer until end of call) Results of this test case and comments:

secs

Comments

Testcase Result


Signature of Tester


Not Performed

Info Date

1

Info

Alert Time 2

A.3) (iii) International Call, not to Home PLMN country and not to country where the MS is presently located: MSISDN of MS(a) Time of activation of BOICexHC International (Non Home PLMN Country and non country where MS(a) is presently located) call successful? [Yes/No]

1 5

-3

Info

3

Time of deactivation of BOICexHC

0

Results of this test case and comments: Comments

0 0 3

A.2.2.3.2

Testcase Result


Signature of Tester


Not Performed

Date

Activated Service is BOICexHC (VPLMN does not SS: BOICexHC): action: (i) MS(a) attempts a call to local PSTN. (ii) MS(a) attempts outgoing call to Home PLMN country.

0

. . . . . . . . . . .



B.1) (i) Call to country where the MS is presently located: PSTN (b) number of the country keyed, where MS(a) is presently located Time of start of national PSTN call (i.e. SEND key operation) Time of activation of BOICexHC Time of perceived answer of call Time of end of call

(hrs:mins:secs) Info (hrs:mins:secs) (hrs:mins:secs)

Time of deactivation of BOICexHC PSTN Chargeable Call Duration (i.e. perceived answer until end of call)

3

secs

Results of this test case and comments: Comments

Info

Info

2

Testcase Result


Signature of Tester


Not Performed

Info Date

0 Alert Time

B.2) (ii) Call to Home-PSTN-telephone(a):

2

Home PSTN (a) Country number keyed Time of activation of BOICexHC Home PSTN Country call successful? Time of deactivation of BOICexHC Results of this test case and comments: Comments

[Yes/No] 3 0 0 0

Info

A 2.2.4a click Help

Testcase Result


Signature of Tester


Not Performed

3 Date 0 1 1

Barring of all incoming Calls (BAICroaming) action: . . . . . . .

expected result:

-3

Preconditions: HLR no entry for Barring of all incoming calls when roaming in VPLMN. Successful result, if calls fail

2

0

. . . . . .

MSISDN MS1(a) IMSI MS1(a) Time of activation of [BAIC / BAICroaming] PSTN (b) number to call Number keyed by PSTN Call successful? Time of deactivation of [BAIC/BAICroaming]

(hrs:mins:secs)


Comments Info

Testcase Result


Info

Not Performed Display Receipt Time

Signature of Tester

A 2.2.4b


Date

Info

2

-3

2

-3

Barring of All incoming Calls (BAIC) action:

Preconditions: HLR no entry for Barring of all incoming calls.

. . . .


. . . . . . .

MS(a) in VPLMN (b) activates the SS: BAIC PSTN(b) calls MS(a)

expected result: Successful result, if calls fail MSISDN MS1(a) IMSI MS1(a) Time of activation of [BAIC / BAICroaming] PSTN (b) number to call Number keyed by PSTN Call successful? Time of deactivation of [BAIC/BAICroaming] Comments

A 2.2.5 click Help

Testcase Result


Signature of Tester


Alert Time

Info [Yes/No] (hrs:mins:secs)

0 1 1 2

3 0 0 0

Not Performed Date

Call Forwarding on Not Reachable (CFNRC -Before IMSI Detach TAKE BATTERY OFF WHILE PHONE IS SWITCHED ON) action: . . . . . . .


Disable MS(a1) so that it is unable to respond to paging [Note MS(a1) must not send IMSI Detach message, while being disabled. This can be achieved by removing the battery while the phone is switched on]. Successful result if the call is completed to PSTN(b1), MS(a2) or PSTN(a) and the call quality is acceptable. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. Optionally, PSTN(b2) may receive an announcement that the call is being forwarded.

MSISDN MS1(a) IMSI MS1(a) Time of activation of CFNRc Directory Number (i.e. DN) of calling PSTN telephone(b2) DN of forwarded - to - PSTN telephone(b1). Note 1

IR24 Test Cases

3 0 (hrs:mins:secs)

0

4

(hrs:mins:secs)

22(39)


Time of start of call Delay between dialing last digit of MSISDN of MS(a1) at PSTN telephone(b2) and PSTN telephone(b1) Time of perceived answer of call

(hrs:mins:secs) sec (hrs:mins:secs)

Time of end of call (hrs:mins:secs) Chargeable Call Duration (i.e. perceived answer until end of call) sec Was an announcement that call was - being - forwarded received by PSTN [Yes/No] Language of announcement [If applicable] Text of announcement [If applicable] Quality of successful call [Excellent, Good, Fair, Poor, Bad] Echo present? [Yes/No] If Yes, to which party? [caller/called] Note 1. If forwarding to PSTN telephone (b1) is restricted by HPLMN or VPLMN, then use MS(a2). If MS(a2) cannot be used then

Info

Info 3 0

Comments 0

Testcase Result


Signature of Tester

A 2.2.6

0 1 1 2

Not Performed


Date

0

Call Forwarding on Not Reachable (CFNRC -After IMSI Detach SWITCH THE PHONE OFF) action:

Check that the subscriber MS(a1) is detached in the VLR, if possible.

. . .


. . . . .

Attempt a call from PSTN telephone(b2) to MS(a1).

. . .

expected result:

Successful result if the call is completed to PSTN(b1), MS(a2) or PSTN(a) and the call quality is acceptable. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. Optionally, PSTN telephone(b2) may receive an announcement that the call is being forwarded. MSISDN MS1(a) IMSI MS1(a) Directory Number (DN) of PSTN telephone (b2) Directory Number (DN) of PSTN telephone (b1) Note 1 Time of start of call (hrs:mins:secs) sec Delay between dialing last digit of MSISDN of MS(a1) at PSTN telephone(b2) and PSTN telephone(b1) Time of perceived answer of call (hrs:mins:secs) Time of end of call (hrs:mins:secs) Chargeable Call Duration (i.e. perceived answer until end of call) sec Was an announcement that call was - being - forwarded received by PSTN [Yes/No] Language of announcement [If applicable] Text of announcement [If applicable] Quality of successful call [Excellent, Good, Fair, Poor, Bad] Echo present? [Yes/No] If Yes, to which party? [caller/called] Time of deactivation of CFNRc (hrs:mins:secs) Note 1. If forwarding to PSTN telephone (b1) is restricted by HPLMN or VPLMN, then use MS(a2). If MS(a2) cannot be used then . . . . . .

4

Info

Comments

A 2.2.7


Signature of Tester


0 1

Not Performed Date

Call Forwarding on Busy (CFB) action: . . . .


2

Testcase Result

. .

0

MS (a1) is in conversation state. If used, MS(a2) is attached.

. . . . .

Attempt a call from PSTN telephone(b2) to MS(a1). Answer resultant call to PSTN(b1), MS(a2) or PSTN(a). 1


Successful result if indicate the call is completed to PSTN(b1), MS(a2) or PSTN(a) and the call quality is acceptable. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. Optionally, PSTN telephone(b2) may receive an announcement that the call is being forwarded.

MSISDN MS1(a) IMSI MS1(a) Time of activation of CFB Directory Number (DN) of PSTN telephone (b2) Directory Number (DN) of PSTN telephone (b1) Note 1 Party with which MS(a1) is in conversation [DN] IMSI MS2(a) Time of start of call Delay between dialing last digit of MSISDN of MS(a1) at PSTN telephone(b2) and PSTN telephone(b1) ringing. Note 1 Time of perceived answer of call Time of end of call Chargeable Call Duration (i.e. perceived answer until end of call) Was an announcement that call was - being - forwarded received by PSTN Language of announcement [If applicable] Text of announcement [If applicable]

1 2

+385957014391 219020000369002 (hrs:mins:secs) 09:23:52 +385957014354 +385957014392 +12462530239 342600202180998 (hrs:mins:secs) 09:24:14 Sec 00:00:21 (hrs:mins:secs) 09:24:40 (hrs:mins:secs) 09:25:51 sec 00:01:11 [Yes/No]

4

Quality of successful call [Excellent, Good, Fair, Poor, Bad] Poor Echo present? [Yes/No] If Yes, to which party? [caller/called] Time of deactivation of CFB (hrs:mins:secs) 09:26:15 Note 1. If forwarding to PSTN telephone (b1) is restricted by HPLMN or VPLMN, then use MS(a2). If MS(a2) cannot be used then Comments Info

Testcase Result


Signature of Tester


Info Date 2014-03-26

3 0

A 2.2.8

Call Forwarding on No Reply (CFNRY) 1

action: . . . .


. .

MS(a) initiates an “Interrogate Call Forward Information”. MS(a) displays information. Attempt a call from PSTN telephone(b2) to MS(a1). After a period of time during which MS(a1) "rings", call is diverted to PSTN(b1), MS(a2) or PSTN(a) where it is answered.

. . . . .

1


0

Successful result if MS(a) displays equivalent information to that stored in HLR and if MS(a1) "rings" for length of time equal to "No Reply Timeout" value stored in HLR, and call is completed to PSTN(b1), MS(a2) or PSTN(a), and the call quality is acceptable. See CCITT Rec P.84 Annex D for instructions on use of Quality Scales. Optionally, PSTN telephone(b2) may receive an announcement that the call is being forwarded.

MSISDN MS1(a) IMSI MS1(a) Time of activation of CFNRY Interrogate Supplementary Service at MS(a) by pressing *#61# Start Time of SS activity (i.e. SEND key operation) Delay between SEND key operation and receipt of Display information Information displayed on MS(a)?

+385957014391 219020000369002 (hrs:mins:secs) 09:14:47

Does MS(a) displays correct status of the call forwarding service? Directory Number (DN) of PSTN telephone (b2) Directory Number (DN) of PSTN telephone (b1) Note 1 Time of start of call

[Yes/No] +12462530239 +385957014392 (hrs:mins:secs) 09:14:54 sec 00:00:30 (hrs:mins:secs) 09:15:29 (hrs:mins:secs) 09:16:41 sec 00:01:11 [Yes/No]

(hrs:mins:secs) 09:14:50 sec 00:00:02

Delay between dialing last digit of MSISDN of MS(a1) at PSTN telephone(b2) and PSTN telephone(b1) ringing. Note 1

Time of perceived answer of call Time of end of call Chargeable Call Duration (i.e. perceived answer until end of call) Was an announcement that call was - being - forwarded received by PSTN Language of announcement [If applicable] Text of announcement [If applicable] Quality of successful call

0

Info 0

[Excellent, Good, Fair, Poor, Bad] Poor

Echo present? [Yes/No] If Yes, to which party? [caller/called] Time of deactivation of CFNRY (hrs:mins:secs) 09:16:33 Note 1. If forwarding to PSTN telephone (b1) is restricted by HPLMN or VPLMN, then use MS(a2). If MS(a2) cannot be used then choose PSTN telephone(a).

0 0

Comments

Testcase Result

IR24 Test Cases


23(39)


Signature of Tester

A 2.3 A 2.3.1


Date 2014-03-26

SMS Test Cases Mobile ORIGINATED and Terminated Short Message Service (SMS-MO) action:

Switch on MS1(a). 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)

expected result:

Successful result if Short Message is correctly delivered within [2] minutes of switching MS2(a) on.

. . . . . .

MSISDN MS1(a) IMSI MS1(a) E164 address of HPLMN SMS – Service Centre Time of transmitting to SMS - Service Centre MSISDN MS2(a) IMSI MS2(a) Time of switching on MS2(a)

(hrs:mins:secs)

Time of receipt of SMS at MS2(a) Was message correctly received? If the message was not received, repeat test with MS2(a) switched on. Was message

(hrs:mins:secs) [Yes/No] [Yes/No]

Info 0

(hrs:mins:secs)

0 0

Comments

2.4

Testcase Result


Signature of Tester


Not Performed Date

SMS Interworking Test Cases This appendix gives a template and a description of the different cases for SMS IW tests.

2.4.1

Basic Test Results Info

Info

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

2.4.1 click Help forTime Macro

Location Update by MS(a) in PLMN(b) VLR Record contents: MSISDN IMSI Teleservices Speech [Y=Yes/N=No] SMS MO SMS MT Fax Bearer Services: (DCDA300 - 4800) Supplementary Services BAOC BOIC BOICexHC CFB CFNRy CFNRc CW

e.g. MS1(a)

[Y/N] [Y/N] [Y/N]

[Y/N]

C Number

[Y/N] [Y/N]

C Number C Number

CH MPTY AOCC AOCI Others:

IR24 Test Cases

[Y/N] [Y/N] [Y/N]

0

[Y/N]

0 0

[Y/N] [Y/N] [Y/N] [Y/N]

24(39)


IR24 Test Cases

25(39)


IR24 Test Cases

26(39)


MS3 (a/b) MS1 (a/b) MS2 (a/b) MS3 (a/b)

Status request for various issue / time SEND KEY Status request for various issue / time START Status request for various issue / time START Status request for various issue / time START

Testcase Result


Signature of Tester


(hrs:mins:secs) (hrs:mins:secs) (hrs:mins:secs) (hrs:mins:secs)

Not Performed Info Date

2.4.2

SMS Test Results in case (WITH ROAMING AGREEMENT), Details of the test C.2.4.2.1

2.4.2.1

Mobile(a) in PLMN(b) to Mobile(b) in PLMN(b)

click Help

action: expected result:

no test setup- see pictures in General, no link no result, no link

. . . . . .

MSISDN -MS1 (a) IMSI - MS1 (a) E164 address of HPLMN SMS – Service Centre Time of initial transmitting by Service Centre MSISDN -MS2 (b) IMSI - MS2 (b) Time of switching on MS2(b) Time of receipt of SMS at MS2(b) Was message correctly received? If the message was not received, repeat test with MS2(b) switched on. Was message

Info

Info

(hrs:mins:secs)

3

0

(hrs:mins:secs) (hrs:mins:secs) [Yes/No] [Yes/No]

1 1

0 0

Comments

2.4.2.2

Testcase Result


Signature of Tester


Not Performed Date

Mobile(b) in PLMN(b) to Mobile(a) in PLMN(b) action:

no test setup- see pictures in General, no link

. . . .


. . . . . . .

expected result:

no result, no link

. . . . . .

MSISDN -MS2 (b) IMSI - MS2 (b) E164 address of VPLMN SMS – Service Centre Time of initial transmitting by Service Centre MSISDN -MS1 (a) IMSI - MS1 (a) Time of switching on MS1 (a) Time of receipt of SMS at MS1 (a) Was message correctly received? If the message was not received, repeat test with MS2(b) switched on. Was message

Info

Info

(hrs:mins:secs)

3

0


1 1

0 0

Comments

Testcase Result


Signature of Tester


2.4.3

Test Results in case of NO ROAMING AGREEMENT

2.4.3.1

Mobile (b) in PLMN (b) to Mobile (a) in PLMN (a) action:

Not Performed Date


. . . .


. . . . . . .


MSISDN -MS2 (b) IMSI - MS2 (b) E164 address of VPLMN SMS – Service Centre Time of initial transmitting by Service Centre MSISDN -MS1 (a) IMSI - MS1 (a) Time of switching on MS1 (a) Time of receipt of SMS at MS1 (a) Was message correctly received? If the message was not received, repeat test with MS2(b) switched on. Was message

Info

Info

(hrs:mins:secs)

3

0


1 1

0 0

Comments

2.4.3.2

Testcase Result


Signature of Tester


Date

Mobile (a) in PLM (a) to Mobile (b) in PLMN (b) action:


. . . .


. . . . . . .


MSISDN -MS2 (a) IMSI - MS2 (a) E164 address of HPLMN SMS – Service Centre Time of initial transmitting by Service Centre MSISDN -MS1 (b) IMSI - MS1 (b) Time of switching on MS1 (b) Time of receipt of SMS at MS1 (b) Was message correctly received? If the message was not received, repeat test with MS2(b) switched on. Was message

Info

Info

(hrs:mins:secs)

3

0


1 1

0 0

Comments

Testcase Result


Signature of Tester


20.1

O P E R A TO R Specific Tests

20.1.1


click Help

Click here to paste a Template

action: expected result: Test Case

Date

Detail Text 2 / Action- field in General TC 20.1.1

Detail Text 3 (Result) 20.1.1

Testcase Result Signature of Tester Paste Test Case Below

[ / FAIL / NOT PERFORMED] TESTER NAME (b) > field in TEST CASE PAGE H31

Date

Click here

IR24 Test Cases

27(39)


Click here to Clear Pastecontents.

20.2.1 click Help

Click here to paste a Template page into this Test

O P E R A T O R -SPEC. TEST CASE HEADER 20.2.1 action: expected result: Test Case



Testcase Result


Signature of Tester Paste Test Case Below


Date


20.3.1 click Help

Click here to paste a Template page into






Date

Click here

IR24 Test Cases

28(39)



20.4.1 click Help





Testcase Result




Date


20.5.1 click Help







Date

Click here to Clear

IR24 Test Cases

29(39)



20.6.1 click Help





Testcase Result




Date


20.7.1

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


. . . . . .


. . . . .

expected result:


. . . . . .


Test Case Comments Testcase Result Signature of Tester Paste Test Case Below


Date

Click here to Clear

IR24 Test Cases

30(39)



20.8.1



. . . . .


. . . . . .

expected result:


. . . . . .


Test Case Comments Testcase Result




Date


20.9.1



. . . . . .


. . . . .

expected result:


. . . . . .


Test Case Comments Testcase Result Signature of Tester Paste Test Case Below


Date


IR24 Test Cases

31(39)


MS1 and MS2 template Return to IR24 Test Case Page Restore Test Case

Click to select this Operator Specific Test

MSISDN of originating MS (i.e. MS1(a/b)) VPLMN input required IMSI of MS1, if from HPLMN (a) VPLMN input required Number keyed into MS1(a) VPLMN input required MSISDN of originating MS (i.e. MS2(a/b)) VPLMN input required IMSI of MS2, if from HPLMN (a) VPLMN input required Number keyed into MS2(a) VPLMN input required SMSC Addr. For MSISDN MS1(a/b)) VPLMN input required SMSC Addr. For MSISDN MS2(a/b)) VPLMN input required Time of start of call MS1 (a/b) (i.e. SEND key operation) (hrs:mins:secs) Delay between SEND key operation at MS1(a/b) and MS2(a/b) alerting secs MS1 (a/b) Status request for various issue (e.g. balance in case of PREPAID) MS2 (a/b) Status request for various issue (e.g. balance in case of PREPAID) Time of start of call MS2 (a/b) (i.e. SEND key operation) (hrs:mins:secs) Time of perceived answer of call at MS1 (a/b) (hrs:mins:secs) Time of perceived answer of call at MS2 (a/b) (hrs:mins:secs) MS1 (a/b) Status request for various issue / time END (hrs:mins:secs) MS2 (a/b) Status request for various issue / time END (hrs:mins:secs) Chargeable Call Duration at MS1(a/b) = xxx sec or more secs Chargeable Call Duration at MS2(a/b) = xxx sec or more secs MS1 (a/b) Status request for various issue (e.g. balance in case of PREPAID) MS2 (a/b) Status request for various issue (e.g. balance in case of PREPAID) Quality of call [Excellent, Good, Fair, Poor, Bad] Echo present? [Yes/No] If Yes, to which MS (a/b)? [MS1(a/b) / MS2(a/b) / MS3(a/b)] Is the MSISDN of MS1(a) displayed at MS2(a) in proper format? [Yes/No] IF NO, what does MS2(a) display?

Info

Info

Info

Info

Alert Time 0:00:00

0 1

3 0

1 1 1 1 3

0 0 0 0 0

2

-3

0:00:00 0:00:00




Info

Info

Info

Info

Alert Time 0:00:00

0 1

3 0

1 1 1 1 3

0 0 0 0 0

2

-3

0:00:00 0:00:00

MS1, MS2 and MS3 template Return to IR24 Test Case Page Restore Test Case


MSISDN of originating MS (i.e. MS2(a/b)) IMSI of MS2, if from HPLMN (a) Number keyed into MS2(a) SMSC Addr. For MSISDN MS1(a/b)) SMSC Addr. For MSISDN MS2(a/b)) SMSC Addr. For MSISDN MS3(a/b)) Time of start of call MS1 (a/b) (i.e. SEND key operation) Delay between SEND key operation at MS1(a/b) and MS2(a/b) alerting MS1 (a/b) Status request for varius issue (e.g. balance in case of PREPAID) MS2 (a/b) Status request for varius issue (e.g. balance in case of PREPAID) MS3 (a/b) Status request for varius issue (e.g. balance in case of PREPAID) Time of start of call MS2 (a/b) (i.e. SEND key operation) Time of perceived answer of call at MS1 (a/b) Time of perceived answer of call at MS2 (a/b) Time of perceived answer of call at MS3 (a/b) Time of start of call MS3 (a/b) (i.e. SEND key operation) MS1 (a/b) Status request for varius issue / time END MS2 (a/b) Status request for varius issue / time END MS3 (a/b) Status request for varius issue / time END Chargeable Call Duration at MS1(a/b) = xxx sec or more Chargeable Call Duration at MS2(a/b) = xxx sec or more Chargeable Call Duration at MS3(a/b) = xxx sec or more MS1 (a/b) Status request for varius issue (e.g. balance in case of PREPAID)

VPLMN input required VPLMN input required VPLMN input required VPLMN input required VPLMN input required VPLMN input required (hrs:mins:secs)

secs

Info

Info

Info

Alert Time 3

1 1 1 1 1 1 1 4

0 0 0 0 0 0 0 0

0:00:00

(hrs:mins:secs) (hrs:mins:secs) (hrs:mins:secs) (hrs:mins:secs) (hrs:mins:secs)

(hrs:mins:secs) (hrs:mins:secs) (hrs:mins:secs) secs secs secs

Info 0

0:00:00 0:00:00 0:00:00

2

-3

MS2 (a/b) Status request for varius issue (e.g. balance in case of PREPAID) MS3 (a/b) Status request for varius issue (e.g. balance in case of PREPAID) Quality of call [Excellent, Good, Fair, Poor, Bad] Echo present? [Yes/No] If Yes, to which MS (a/b)? [MS1(a/b) / MS2(a/b) / MS3(a/b)] Is the MSISDN of MS1(a) displayed at MS2(a) in proper format? [Yes/No] IF NO, what does MS2(a) display?




Alert Time 0:00:00

0:00:00 0:00:00

0 1

3 0

1 1 1 1 3

0 0 0 0 0

2

-3

IR24 General Page

Setup Page

Test Cases Page

Instructions

Tadig Page

Templates Page

The intention of this worksheet is to allow easy of the IREG test results for TADIG testers. To this extent this page only provides results for tests where a CDR can be created in TAP. Whether or not that CDR is then created may also depend on the charging principles or network setup of the visited network. For more information on the expected outcome on TAP please refer to GSM PRD TD.43

Create CSV file

-- IR.24 - please refer to GSM PRD TD.43

IREG Test Ref 2.1.1 2.1.2A 2.1.2B 2.1.3

Event Number 1 1 1 1

TAP CDR Type None Expected None Expected None Expected MOC

Service Type

2.1.3

2

MTC

Voice

2.1.4

1

MTC

Voice

2.1.5

1

None Expected

2.1.6

1

None Expected

2.2.1

1

MOC

Emergency

2.2.2 2.2.3.1.A

1 1

MOC SS

Voice BOIC-exHC

2.2.3.1.A

2

MOC

Voice

2.2.3.1.A 2.2.3.1.A 2.2.3.1.A 2.2.3.2.B

3 4 5 1

MOC None Expected SS SS

BOIC-exHC BOIC-exHC

2.2.3.2.B 2.2.3.2.B 2.2.3.2.B 2.2.4 2.2.5

2 3 4 1 1

MOC None Expected SS None Expected SS

BOIC-exHC

2.2.5

2

2.2.5

MSISDN

Subscriber ID Other (IMSI!)

Startime of CDR none none none

Chargeble DURATION none none

Voice

Calling/Call APN ed Party none none none none none #REF! none

Status YES Not Performed YES Not Performed YES Not Performed YES Not Performed YES

none

Not Performed YES

none

Not Performed YES

#REF!

missing yet

YES YES YES YES YES YES YES YES YES

none

none

none

Not Performed YES

none

none

none

Not Performed YES

none

Not Performed YES

none none

Not Performed YES N/A YES

none

N/A

YES

YES YES YES YES

#REF!

none

none

none none none

none none none

none none none none

N/A N/A N/A N/A

CFNRc

0:00:00 none none none none

none none none none

none none none none none

N/A YES N/A YES N/A YES Not Performed YES Not Performed YES

MTC

Voice

none

none

Not Performed YES

3

MOC

Voice

none

Not Performed YES

2.2.6 2.2.7

1 1

None Expected SS

CFNRC CFB

+385957014391

219020000369002

none 09:23:52

none none

none

none none

Not Performed YES YES

2.2.7

2

MOC

Voice

+385957014391

219020000369002

09:24:40

none

+12462530239 none

YES

none

+38595701439 1 none

YES

+38595701439 2 none none none

YES YES

none none

none none

YES YES

+12462530239 none

YES

2.2.7

3

MTC

Voice none none #REF!

Voice none none

Voice

+12462530239

342600202180998

09:24:40

2.2.7 2.2.7

4 5

MOC SS

Voice CFB

+385957014391 +385957014391

219020000369002 219020000369002

09:24:40 09:26:15

00:01:11 none

2.2.8 2.2.8

1 2

SS None Expected

CFNRy

+385957014391 none

219020000369002 none

09:14:50 none

none none

2.2.8

3

MTC

Voice

+385957014391

219020000369002

09:15:29

00:01:11

2.2.8 4 2.2.8 5 2.3.1 1 2.3.1 2 2.4.2.1 1 2.4.2.2 2 2.4.3.1 1 2.4.3.2 2 GSMA SPECIFIC Test Cases

IR24 TADIG-Input

MOC SS MOC MTC N/A N/A N/A N/A

Voice CFNRy SMS-MO SMS-MT SMS-MO SMS-MT SMS-MO SMS-MT

+385957014391 +385957014391

219020000369002 219020000369002

MSISDN MS1 (a) f.A1.2 I16 MSISDN MS1 (a) f.A1.2 I16 MSISDN MS1 (a) f.A1.2 I16 MSISDN MS2 (a) f.A1.2 I18

IMSI MS1 (a) f.A1.2 IMSI MS1 (a) f.A1.2 IMSI MS1 (a) f.A1.2 IMSI MS2 (a) f.A1.2

09:15:29 09:16:33

I17 I17 I17 I19

1900/01/00 1900/01/00 1900/01/00 1900/01/00

00:00:00 00:00:00 00:00:00 00:00:00

none none none none none none none none

+38595701439 2 none none none none none none none

34(39)

none none none none none none none none

YES YES Not Performed YES Not Performed YES N/A YES N/A YES N/A YES N/A YES YES


GSMA Specific Help 1

A LINE BREAK FOR COMMENTS NEEDS TO BE ENTERED AS "LOWER SHIFT + RETURN" HERE

Date /Sign.

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

Initial 2008

General use of the spreadsheet Do not delete or insert rows or columns on any of the pages, except the SETUP PAGE. Here it is allowed as an exemption to add lines in section 4. for OPERATOR SPECIFIC HINTS. Set up any filters on any page, filters are automatically set by the spreadsheet. - the grey numbers on the right side of the test cases are visible "counting steps" to make the time macro able to jump to the correct next input field. Don't change it without any reason. - all areas which are indicated as light green belong to GSMA responsibility and are not allowed to be changed! The yellow indicated test cases are free for modification by all OPERATORs (see GENERAL and TEST CASES)." 2

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

Initial 2008

IMPORTANT: Your PC might not allow to use macros! In this case you have to follow the instruction from your PC office programm and adjust the security options in EXCEL to the expected value (e.g. from high to medium) and save the file again. After the re-opening, you will be asked for the macro activation, please confirm it. For TADIG it's not relevant, that your time stamp is 1:1 to the network element. In case of a clock offset on your PC the mismatch is always the same, so TADIG can suggest the right value in the switch. Only if your PC time is far away from real time, you should notify this in your sheet on TEST CASES (e.g. comments) and TADIG PAGE (extra note). All fields which require such a format are connected within the testing sequence (see grey digits). Please make sure if you are using the time macro that your PC clock is working in the 24h format. Check this under control /region settings ->clock/customized choose capitel letter "H" - DROP DOWN BOXES, if you want to use the keyboard instead of the mouse, enter the field and try "ALT + arrow down"

3

- CHANGE OF LINK REFERENCES FOR USED MSx (a) / (b)- If you need to change such link reference, it might happen randomly, that the field lost its format as "standard" and you see only a text mark like "=I17" and not the related entry from that field. 1. Change the link reference as you want e.g. I17 to I23, 2. press "Ctrl + 1" and set the field again to STANDARD than OK 3. enter this field PAGES again and press is F2no+ real ENTER. "UNPROTECT" - (there protection!)

Initial 2008

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

4

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

5

Initial 2008 IRxx GENERAL on this page you will see all test case descriptions which you can access from the top immediately via the blue buttons. The important feature is the linking of the content of the test case header + general description below the header + action content + expected result content! If you plan to change any content for the GSMA test description in those fields , this content is shown 1:1 on the test case page. Normally no changes are allowed for the operator, because it should be the same GSMA testing content for all operator. Please : the new IRxx will be sent from operator (HPLMN) to operator (VPLMN) to use the option Operator- Flexible Test Cases for their own requirements !

6

SETUP PAGE For the test cases you want to be completed select "Yes" from the dropdown menu. I m p o r t a n t - to click the red selection button after selecting your Test Cases! This button sets the filters on the TEST and TADIG Pages!

7

Initial 2008 TEST CASE page Only enter data into the light blue coloured cells. If these cells are within a test case, it will turn white when you have entered your data. Complete section A1.1 and A1.2 before starting the test cases. Don't change any test case header in here, because they are linked to the IRxx GENERAL page and should reflect only the content from there. Do not delete any grey numbers on the right side in the TEST CASES PAGE and TEMPLATES PAGE. They are used as "jump marks" to the next planned data entry field. In case of the TEMPLATES PAGE, you might need to adjust them. You can try to change them for testing purposes and see how they work (it is not comlicated). If you want to reset the whole TEMPLATE , use the button for it and it will be restored. There is a macro inserted, which allows you to insert the time into the testing document (based on your PC time). This can be used with the key combination "Ctrl + Low-Shift + A". You will find next to all test cases a "red circle button" in the TEST CASES PAGE, which reminds you of that. All fields which require such a format are connected within the testing sequence (see grey digits).

Initial 2008

Initial 2008

8

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

Initial 2008

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

9

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

Initial 2008

10

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

Initial 2008

11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

Operator Specific Help A LINE BREAK FOR COMMENTS NEEDS TO BE ENTERED AS "LOWER SHIFT + RETURN" HERE 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26

CALL DIVERSION

Feature Mode Sequence All calls Activate & number ** 21 * Number # SEND Deactivate & de number ## 21 # SEND Activate to ed number * 21 # SEND Deactivate # 21 # SEND *# 21 # SEND No answer Activate & number ** 61 * Number # SEND Deactivate & de number ## 61 # SEND Activate * 61 * Number # SEND Deactivate # 61 # *# 61 # SEND Unreachable Activate ** 62 * Number # SEND Deactivate ## 62 # SEND *# 62 # SEND Busy Activate ** 67 * Number # SEND Deactivate ## 67 # SEND

Date /Sign.

*# 67 # SEND All types Deactivate ## 002 # SEND All conditional types Deactivate ## 004 # SEND

CALL BARRING Feature Mode Sequence Barring all outgoing calls Activate * 33 * PIN # SEND Deactivate # 33 * PIN # SEND *# 33 # SEND Barring all outgoing IDD calls Activate * 331 * PIN # SEND Deactivate # 331 * PIN # SEND *# 331 # SEND Barring all outgoing IDD calls when roaming (except to home country) Activate * 332 * PIN # SEND Deactivate # 332 * PIN # SEND *# 332 # SEND Barring all outgoing calls Activate * 333 * PIN # SEND Deactivate # 333 * PIN # SEND *# 333 # SEND Barring all Incoming Calls Activate * 35 * PIN # SEND Deactivate # 35 * PIN # SEND *# 35 # SEND Barring all incoming calls when international roaming Activate * 351 * PIN # SEND Deactivate # 351 * PIN # SEND *# 351 # SEND Barring all calls Activate * 350 * PIN # SEND Deactivate # 350 * PIN # SEND *# 350 # SEND Barring all incoming calls Activate * 353 * PIN # SEND Deactivate # 353 * PIN # SEND *# 353 # SEND Deactivate all call barring # 330 * PIN # SEND Change call barring code ** 03 * old barring code * new barring code * new barring code # SEND

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

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

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

EMERGENCY Feature Sequence Emergency Call 112 SEND

Yes/No Dropdown

Call Quality Dropdown

Yes No

Excellent Good Fair Poor Bad

Test Completed Dropdown

FAIL Not Performed Count 6 Count 4

Test Case Selection Dropdown YES No

Test Case Paste Value 10 D1588 20.1

Today

MS Dropdown MS1(a) MS2(a) MS3(a)

2014/06/17

Paging Dropdown A(Paging) B(Pre-Paging)

Test Case 1 2 3 4 5 6 7 8 9 10

D1012 D1076 D1140 D1204 D1268 D1332 D1396 D1460 D1524 D1588

20.1 20.2 20.3 20.4 20.5 20.6 20.7 20.8 20.9 20.10

Ir24 5q2nu

Overview 4q3b3c

More details 26j3b

Related Documents 171j1w

Ir24 5q2nu

More Documents from "Riki Foru" 403r1j

Ir24 5q2nu

Sop Deteksi Dini Gangguan Kesehatan Jiwa Fix j6w3i

Kerangka Acuan Program Kesehatan Indera 371651

1.1.1.1 Sk Jadwal Pelayanan Puskesmas 173ig

Makalah Korosi Kel 3 Sem 5 5m2345

1.1.1.3 Spo Komunikasi Dengan Masyarakat 4c306t