Nexus8620 Service Test System

IREG 24 Reporting Description

Nexus8620

IREG Test Application

The IREG Reports are made to test the roaming between mobile network partners. GSM MoU Association as a Permanent Reference Document recommends it. The IREG tests cover all the basic tests and many of the supplementary services. These tests are intended to be run on a regularly base, e.g. every quarter. But with this testing much manual work is involved. The Nexus8620 IREG Reporting helps to automate it in order to save this intensive work. Years ago the IREG reporting was important to attest to roaming partners that theirs subscriber are able to roam in foreign networks. Nowadays this is not anymore an issue because there are several operators offering a wireless network in a country. Therefore if one of the network does not allow roaming, the subscriber just phones over another operator.

Contents
1 2 IREG 24 TestCase Introduction ............................... 3 Testcases ................................................................. 5 2.1 Basic Service Test Cases.................................. 5 2.2 Supplementary Service Test Cases .................. 8 2.3 SMS Test Cases.............................................. 12 Equipment .............................................................. 14 3.1 SimCards ......................................................... 14 Pre-Testing Data Exchange ................................... 15 4.1 Testing Contact Information............................. 15 4.2 PLMN addressing, numbering and routing data...................................................... 15 4.3 SIM associated data supplied by PLMN (a)..... 15 4.4 PSTN information supplied by PLMN(b).......... 16

3 4

Page 2

Nexus8620

IREG Test Application

IREG 24 Test Case Introduction

The purpose of the IREG reports is to test end-to-end Functional Capability relating to the international roaming of a Mobile Station, belonging to a home PLMN(a) within a visited PLMN(b). Whilst it is expected that roaming will be a bilateral activity between two PLMN's, it has to be considered that the IREG document is written in an unidirectional context. Hence Roaming is taking place from MS(a) to VPLMN(b) only. There is no reference to a Mobile Station MS(b) visiting PLMN(a) . The IREG report does not contain information regarding: SCCP testing [see Stage 2: MoU-IREG PRD IR25] Exchange of PLMN numbering, addressing and routing data [see Stage 3: MoU-IREG PRD IR23] testing of Transferred Account Procedure, billing applications and any inter-PLMN financial statement; [see MoU-TADIG PRD TD06]. definition of operation and maintenance procedures such as contact points for fault reporting and notification of planned works. [see Stage 3: MoUIREG PRD IR23]

1.1.1

Objective of Tests

The fundamental objective of IREG testing is to confirm the capability and to sample the quality of service which GSM users receive when roaming from their Home PLMN(a) to PLMN(b). Consequently the tests are restricted to top-level capability testing. There will be no fraud testing. Because the testing is at a top-level, its scope includes checking the correct working of user 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.

Page 3

Nexus8620

IREG Test Application

The specific objectives of IREG testing are to prove that: "Location updating" and the "cancel location" service operates correctly. Incoming speech calls to MS(a) can be handled by HPLMN(a) and VPLMN Outgoing speech calls by MS(a) to the VPLMN(b) are handled properly for Emergency calls, local calls to VPLMN(b), International calls and calls to any other "Operator Services" on VPLMN(b) / PSTN(b) Supplementary Services Call barring, Call Forwarding, Barring of Incoming Calls and Short Message Service are working. 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. For example if HPLMN(a) contains HLR and GMSC from "m" suppliers, and the VPLMN(b) contains VMSC from "n" suppliers, then the tests should be performed m*n times. However, it is up to the HPLMN operator to decide the scope of the repeating of test cases, because he is ultimately responsible to his customers for the supported roaming services.

1.1.2

Strategy for Testing

In order to maximize the efficiency of testing, the test cases have been designed in a way to minimize the requirement for simultaneous joint activity by both PLMN(a) and PLMN(b). It is recognized that some parts of this specification are of greater priority than others. The test cases concerning the " Basic Service" are of greater priority than those for the "Supplementary Services".

Page 4

Nexus8620

IREG Test Application

2
2.1
2.1.1

Testcases
Basic Service Test Cases
Location update by MS(A) in VPLMN(B)

This TestCase confirms operation of Update Location and Insert Subscriber Data procedures. It checks the support of the relevant MAP operations, TCAP processes and SCCP addressing for both E214 and E164 Global Titles, between the HLR(a) and VMSC(b). Action: Power-up MS1(a) and perform registration on VPLMN(b) Check Location Update of MS1. Result: Successful results if LoUp worked. location

2.1.2 2.1.2.1

Operator control of service Location Cancellation for Subscription held in VPLMN(b). MS(a)

This test case confirms that the "cancel location" procedure operates correctly. Action: HPLMN(a) deletes MS(a) subscription from HLR using HLR's Man-Machine Interface or via Administrative Data Center (ADC) input to HLR. Check VLR for record of MS(a). Result: Confirmation that VLR record for MS (a) has been erased. Note: This test is done by performing a LoUp at VPLMN(b). If it worked, the VLR record at VPLMN(a) was erased.

2.1.2.2

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

This test case confirms that ODB procedures operate correctly. 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 Administrative Data Center (ADC) input to HLR. Check VLR for record of MS(a).

Page 5

Nexus8620

IREG Test Application

Try to call MS(a) and try to make a call from MS(a). Result: Confirmation that VLR record for MS(a) contains ODB information and non-of the call attempt is successful.

2.1.3

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

This test case confirms Mobile Originated and Mobile Terminated calls for roamers. It checks the support of the Provide Roaming Number MAP operation between PLMN(a) and PLMN(b). It checks the ability to establish international calls between the two PLMN's using roaming numbers. It implies the ability of the PLMN's to disable excessive instances of echo control devices. Action: MS1(a) establishes call to MS2(a). Call answered and held for one minute. Quality assessed. Result: Confirmation that call is established in 30 seconds and is stable in unanswered and answered phases Confirmation that there is no perceivable echo to either user and that call remains on a high quality conversation level for one minute. Not yet automatically tested by Nexus8620 IREG Application: (g)* Quality of call [Excellent, Good, Fair, Poor, Bad] (h) Echo present

2.1.4

PSTN Telephone in country containing PLMN(b) calls MS(a), which has roamed to VPLMN(b), but the VLR has lost the record for MS(a).

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. Action: PSTN telephone(b) calls MS(a). If call is successfully established, maintain answered call for one mi nute. Assess speech channel quality. If call attempt returns "System Failure" message, then make MS(a) perform a location update and repeat this test case.
Page 6

Nexus8620

IREG Test Application

Result: Confirmation that either first call-attempt is established or "System Failure" message is returned within 30 seconds. In addition confirmation that the answered call, whether established on the first attempt or after the location update, has no perceivable echo to either user and that an acceptable quality connection can be maintained. Not yet automatically tested by Nexus8620 IREG Application: (g) If first call successful (h) If location update sequence originated from the Mobile Station necessary (i) Quality of successful call [Excellent, Good, Fair, Poor, Bad] (j) Echo present

2.1.5

PSTN telephone in country containing PLMN(b) calls MS(a), which has roamed to VPLMN(b) but has performed IMSI detach.

This test case confirms that the "absent subscriber" reason is given as the result of a roaming number inquiry 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. Note that the announcement will be in the language of PLMN(a). Action: Check that the subscriber is detached in the VLR, if possible. Attempt a call from PSTN telephone(b) to MS(a) Result: PSTN telephone(b) receives a message that MS(a) cannot be reached or is unavailable. Not yet automatically tested by Nexus8620 IREG Application: (d) Time of start of "not reachable" announcement (e) Duration of announcement (f) Language of announcement (g) Text of announcement

Page 7

Nexus8620

IREG Test Application

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

This test case confirms that the correct response is given when a call is made to a roamed mobile station that does not respond to paging. Note that there will be some delay before the failure message is given while the paging is performed. The message will be in the language of PLMN(b). Action: Disable MS(a) so that it is unable to respond to paging. Check that the subscriber is registered in the VLR, if possible. Immediately attempt a call from PSTN telephone(b) to MS(a) Result: PSTN telephone(b) receives a message that MS(a) cannot be reached. Not yet automatically tested by Nexus8620 IREG Application: (d) Time of start of "not reachable" announcement (e) Duration of announcement (f) Language of announcement (g) Text of announcement

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. Following test steps can not be measured automatically in Supplementary Services testing: Announcement that call was being forwarded received by PSTN telephone(b2) Language of announcement Text of announcement Quality of call Echo present

2.2.1

Barring of All Outgoing Calls.

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

Page 8

Nexus8620

IREG Test Application

Action: (i) MS(a) attempts Emergency Call [112 keyed on MS] (ii) MS(a) attempts call to PSTN. Result: Successful result if call "i" succeeds and call "ii" fails. Not yet automatically tested by Nexus8620 IREG Application: (c) Emergency code keyed [i.e.112] (d) Time of start of emergency call (i.e. SEND key operation) (e) Time of perceived answer of call (f) Chargeable Call Duration (i.e. perceived answer until end of call) (To be measured irrespective of charging policy for emergency calls in VPLMN) (g) Emergency Call successful

2.2.2

Barring of Outgoing International Calls

This test case confirms the support 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. Action: (i) MS(a) attempts call to PLMN(b) or PSTN(b) General Operator Service (t[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. Result: Successful result if call "i" succeeds and call "ii" fails. Not yet automatically tested by Nexus8620 IREG Application: (h) Call routed to correct Operator position

2.2.3

Barring Of Outgoing International Calls Except To Home PLMN Country.

Insert HLR operator manually

Page 9

Nexus8620

IREG Test Application

2.2.3.1

VPLMN does support the SS: BOICexHC

Action: (i) MS(a) attempts an outgoing call to HomePSTN-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). Result: Successful result if calls of Testcases "i" and "ii" succeed, and the call of TestCase "iii" fails.

2.2.3.2

VPLMN does BOICexHC

not

support

the

SS:

This test case confirms the support of this Supplementary Service by the VPLMN(b). In the case VPLMN(b) does not support the SS:BOICexHC, the switch makes a Functional fallback because it supports BOIC. Action: (i) MS(a) attempts a call to local PSTN. (ii) MS(a) attempts outgoing call to Home PLMN country. Result: Successful result, if the call (i) succeeds and call (ii) fails.

2.2.4

Barring Of All Incoming Calls (BAIC / BAICroaming)

This test case confirms the support of the activation of this Supplementary Service when roaming inside VPLMN. Action: MS(a) in VPLMN(b) activates the SS: BAIC or BAICroaming PSTN(b) calls MS(a) Result: Successful result, if calls fail

2.2.5

Call Forwarding On Not Reachable (Before IMSI Detach).

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 VMSC(b) forwarded the call. Action: Disable MS(a1) so that it is unable to respond to paging. Immediately attempt a call from PSTN telephone(b2) to MS(a1). Answer resultant call to

Page 10

Nexus8620

IREG Test Application

PSTN telephone(b1), telephone(a).

MS(a2)

or

PSTN

Result: Successful result if the call is completed to PSTN(b1), MS(a2) or PSTN(a) and the call quality is acceptable. Optionally, PSTN(b2) may receive an announcement that the call is being forwarded.

2.2.6

Call Forwarding On Not Reachable (After IMSI Detach).

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 that the announcement will be in the language of PLMN(a) as GMSC(a) forwarded the call. 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). Result: Successful result if the call is completed to PSTN(b1), MS(a2) or PSTN(a) and the call quality is acceptable. Optionally, PSTN telephone(b2) may receive an announcement that the call is being forwarded. Note: If forwarding to PSTN telephone (b1) is restricted by HPLMN or VPLMN, then use MS(a2). If MS(a2) cannot be used then the PSTN telephone(a) has to be chosen manually.

2.2.7

Call Forwarding on Busy.

This test case confirms that CFB operates correctly. Action: Attempt a call from PSTN telephone(b2) to MS(a1). Answer resultant call to PSTN(b1), MS(a2) or PSTN(a). Result: Successful result if there is indication that the call is completed to PSTN(b1), MS(a2) or PSTN(a) and the call quality is acceptable. Optionally, PSTN telephone(b2) may receive an announcement that the call is being forwarded.
Page 11

Nexus8620

IREG Test Application

Note: If forwarding to PSTN telephone (b1) is restricted by HPLMN or VPLMN, then use MS(a2). If MS(a2) cannot be used then the PSTN telephone(a) has to be chosen manually.

2.2.8

Call Forwarding On No Reply.

This test case confirms that CFNRy operates correctly. It also confirms that the procedure "Interrogate Call Forward Information" operates correctly. 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. Result: Successful result if MS(a) displays equivalent information to that stored in HLR and if MS(a1) "rings" for a length of time equal to the "No Reply Timeout" value stored in the HLR, and call is completed to PSTN(b1), MS(a2) or PSTN(a), and the call quality is acceptable. Optionally, PSTN telephone(b2) may receive an announcement that the call is being forwarded. Not yet automatically tested by Nexus8620 IREG Application: (c ) Interrogate Supplementary Service at MS(a) by pressing *#61#SEND (e) Delay between SEND key operation and receipt of Display information (f) Information displayed on MS(a) (g) Does MS(a) displays correct status of the call forwarding service? (l) Length of time for which MS(a1) "rings" Note: If forwarding to PSTN telephone (b1) is restricted by HPLMN or VPLMN, then use MS(a2). If MS(a2) cannot be used then the PSTN telephone(a) has to be chosen manually.

2.3
2.3.1

SMS Test Cases.

Mobile originated and terminated SMS

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

Page 12

Nexus8620

IREG Test Application

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 Center with Message Waiting priority selected. Switch on MS2(a) Await delivery of Short Message to MS2(a) Check contents of Short Message with transmitted contents. Result: Successful result if Short Message is correctly delivered within 2 minutes of switching on MS2(a). Not yet automatically tested by Nexus8620 IREG Application: (h) If the message was not received, repeat test with MS2(a) switched on.

Page 13

Nexus8620

IREG Test Application

3
3.1

Equipment
SIM Cards

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

Page 14

Nexus8620

IREG Test Application

Pre-Testing Data Exchange

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

4.1

Testing Contact Information

The Test Co-ordination contact names, telephone numbers and fax numbers should be exchanged by both PLMN's.

4.2

PLMN addressing, routing data

numbering

and

Confirmation of the PLMN addressing numbering and routing data as referenced in the Stage 3 [MoU-IREG PRD IR23], is regarded as advisable. Such information includes: E212-E214 translation. MSC/VLR and HLR E164 addresses. MSRN number ranges. International Signaling Point Codes (if applicable) SMS Service Center E164 address

4.3

SIM associated data supplied by PLMN (a)

The following information as stored in the SIM and/or HLR is required individually for each of the four SIMs. PIN, PUK/(SUPER PIN). IMSI MSISDN Basic Service Subscription Information Initial Supplementary Service Configuration Information, including Call Barring, Password and Call forwarding information. (These will be modified by the tests, but initial settings are required for TestCase 2.1.1)

Page 15

Nexus8620

IREG Test Application

4.4

PSTN information supplied by PLMN(b)

The PSTN Directory Numbers for telephones used for call-forwarding tests is required individually for each PSTN telephone.

Page 16

Nexus8620

IREG Test Application

Notice Every effort was made to ensure that the information in this document was accurate at the time of printing. However, information is subject to change without notice, and Nexus Telecom reserves the right to provide an addendum to this document with information not available at the time that this document was created. Copyright Copyright 2003 Nexus Telecom. All rights reserved. No part of this guide may be reproduced or transmitted electronically or otherwise without written permission of the publisher. Trademarks Nexus Telecom and its logo are trademarks of Nexus Telecom AG. All other trademarks and registered trademarks are the property of their respective owners.

Revision History Version 1 Date 26 Mai 2003 Author Walter Buehler

All General Inquiries: info@nexus-ag.com

Nexus Telecom AG
System Solutions
Feldbachstrasse 80 P.O. Box 215 CH-8634 Hombrechtikon Switzerland Tel. Fax +41 55 254 5111 +41 55 254 5112

Nexus Telecom AG
Wireless Network Systems
Frrlibuckstrasse 62 P.O. Box 167 CH-8037 Zrich Switzerland Tel. Fax +41 1 355 6611 +41 1 355 6612

NXS Solutions Inc.

(NA and CALA)
Suite 100 1101 Prince of Wales Drive Ottawa, Ontario Canada K2C 3W7 Tel. +1 613 224 2637 Fax +1 613 224 2761 sales@nxssolutions.com support@nexus-ag.com

sales@nexus-ag.com support@nexus-ag.com

sales@nexus-ag.com help@nexus-ag.com

Page 17