E

Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

1 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

FLEXIBLE NUMBERING
Contents 1 1.1 1.2 1.3 1.4 1.5 2 2.1 2.2 2.3 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 4 5 6 Page 2 2 2 2 2 2 5 5 5 6 8 8 11 13 14 15 18 21 23

GENERAL . . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Application . . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Features . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Introduction . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Concepts . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Commands and Printouts . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . DEMO PREPARATION . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Demo Prerequisites . . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Demo Aid Requirements . . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Preparation of Demo Parameter Values . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . DEMO EXECUTION . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Flexible Allocation of MSISDN .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Default Routing .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . File Output in FNR .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Stopping of File Output process in FNR . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . File Input of MSISDN in FNR from HLR . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Ending Database of MSISDN in FNR from HLR . . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . File Input of MSISDN in FNR from FNR . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . Ending File Input of MSISDN in FNR from FNR . . .. . . .. . .. . .. . .. . .. . . .. . .. . .. .

HELPFUL HINTS . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 26 ABBREVIATIONS .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 27 TEST CASE SUMMARY LIST . . .. . .. . .. . . .. . .. . .. . .. . . .. . .. . .. . .. . .. . . .. . .. . .. . 28

A4 XSEIF R2

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

2 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

1
1.1

GENERAL
Application
This is a general document to be used for System Demonstration of Flexible numbering in GSM/UMTS.

1.2

Features
NF 628.1 NF 690.1 NF 691.1 NF 975.1 Flexible allocation of MSISDN File Input for Subscriber Data in FNR File Output for Subscriber Data in FNR FNR basic package information

1.3

Introduction
The Flexible Numbering function enables mobile operators to allocate subscriber identities in a flexible way. It is possible to allocate any MSISDN number to an IMSI. This is done by introducing a node called Flexible Number Register (FNR). The FNR acts like a gateway for the HLRs and routes the messages to the correct HLR. The function File Input/Output for Subscriber Data gives the operation and maintenance staff the ability to obtain a file input/output of subscriber definitions, for all or a subset of subscribers, stored in the FNR database. The function is administered by the operator by means of commands provided to allow initiation and ending of subscriber definitions file input/output, as well as printing of status for the file input/output process. This function is useful, for instance, when the operator wishes to move large amounts of subscriber data between FNRs. This demo instruction will demonstrate the functionality Flexible Allocation of MSISDN and File Input for Flexible Allocation of MSISDN in the FNR. The functionality File Input/Output for Subscriber Data is also demonstrated.

1.4

Concepts
-

1.5
1.5.1

Commands and Printouts

Commands
FGDRC FGDRP Flexible Numbering Register, Default Route Translation, Change Flexible Numbering Register, Default Route Translation, Print

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

3 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

FGFIE FGFII FGFIP FGFOE FGFOI FGFOP FGFRI FGNTC FGNTE FGNTI FGNTP HGPFI INFIP INFII INFIT IOIFI IOIFP

Flexible Numbering Register, File Input, End Flexible Numbering Register, File Input, Initiate Flexible Numbering Register, File Input Log Data, Print Flexible Numbering Register, File Output, End Flexible Numbering Register, File Output Data, Initiate Flexible Numbering Register, File Output, Print Flexible Numbering Register, File Input Log Data Reset, Initiate Flexible Numbering Register, Subscriber Number Translation, Change Flexible Numbering Register, Subscriber Number Translation, End Flexible Numbering Register, Subscriber Number Translation, Initiate Flexible Numbering Register, Subscriber Number Translation, Print Home Location Register, Permanent Subscriber Data File Output, Initiate IO Subsystem Functions File Administration, Print IO Subsystem Functions File Administration, Initiate IO Subsystem Functions File Administration, Transfer IO Infinite Sequential File Functions, Insert IO Infinite Sequential File Functions, Print

1.5.2

Printouts
FILE ATTRIBUTE INFINITE SEQUENTIAL FILE FILE COPY INTERNAL FNR DEFAULT ROUTE DATA FNR FLEXIBLE ALLOCATION FILE INPUT LOG DATA FNR OWN GMSC SERIES DATA FNR OWN NETWORK PREFIX DATA FNR SUBSCRIBER DEFINITION FILE OUTPUT STATUS FNR SUBSCRIBER DEFINITION FILE INPUT LOG DATA

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

4 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

FNR SUBSCRIBER NUMBER TRANSLATION DATA HLR SUBSCRIBER DATA FILE OUTPUT INITIATE RESULT

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

5 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

2
2.1

DEMO PREPARATION
Demo Prerequisites
-

2.2
2.2.1

Demo Aid Requirements

Hardware Tools
Three Mobile Stations or User Equipment. For the purpose of this document Mobile Stations have been used, but they can be substituted for User Equipment.

2.2.2

Software Tools
-

2.2.3

Network Configuration
IMSI 1 IMSI 3 HLR 1 MS1/UE1 MS3/UE3

FNR
MSC/VLR MSC SERVER MGW BSC RNC BTS

MS2/UE2

IMSI 2

HLR 2

Figure 1

Network configuration

In order to demonstrate Flexible Numbering two HLRs, HLR 1 and HLR 2, are required along with an MSC/VLR or MSC server, BSC/RNC and BTS. One of the HLRs could be an integrated part of the MSC ( MSC/HLR ).

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

6 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

2.3
2.3.1

Preparation of Demo Parameter Values

Exchange Dependent Parameters
AXE parameters Feature parameter for Flexible Allocation of MSISDN must be active. DBTSP:TAB=AXEPARS,SETNAME=GSMFNSF,NAME=FNRNFFAMF; Feature parameter for File Input for Flexible Allocation of MSISDN must be active. DBTSP:TAB=AXEPARS,SETNAME=GSMFNSF,NAME=FNRNFFI; Feature parameter for Number Portability must be active. DBTSP:TAB=AXEPARS,SETNAME=GSMFNSF,NAME=FNRNFNP; Result: VALUE=1 If not, set it to enable the features and their corresponding functions. Parameters for FLNAN A Translation Table is used by FNR to convert the IMSI to Mobile Global Title. The table has up to 16 positions, where each position contains, as input, the leading IMSI digits to be replaced and, as output, the digits that replace them. To define the table the following values are needed: CC The Country Code IMSISERIELENGTH The number of digits in the IMSI series IMSISERIE0L, IMSISERIE0H The leading digits in the IMSI series MGTSERIE0L, MGTSERIE0H The leading digits in the MGT series These values are set by means of commands in TEST SYSTEM. EXAMPLE Country Code = 34 ( Spain ) CC = #F34 ( CC is 3 digits - unused digits are assigned the value #F )

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

7 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

IMSI Series = 847260 IMSISERIELENGTH = 6, IMSISERIE0H = #FF84, IMSISERIE0L = #7260

MGT Series = 1277737 MGTSERIE0H = #F127, MGTSERIE0L = #7737

Commands (FLNAN CAAZ 107 2606 R6A): TEST SYSTEM; SET VAR FLNAN 296(28)=HF34; ! CC ! SET VAR FLNAN 296(29)=H0F3; ! CC => 4 ! SET VAR FLNAN 296(30)=H00F; ! CC => 8 ! SET VAR FLNAN 296(40)=6; ! IMSISERIELENGTH ! SET VAR FLNAN 0:163(0)=H7260; ! IMSISERIE0L ! SET VAR FLNAN 0:163(1)=HFF84; ! IMSISERIE0H ! SET VAR FLNAN 0:163(2)=H7737; ! MGTSERIE0L ! SET VAR FLNAN 0:163(3)=HF127; ! MGTSERIE0H ! END TEST;

2.3.2

Exchange Dependent Data

IMSI1 and IMSI2 must be defined with the same MSISDN but should be located in different HLRs.

2.3.3

Check of data
-

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

8 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

3
3.1

DEMO EXECUTION
Flexible Allocation of MSISDN
This demo case will verify the definition, change and removal of a relationship between an MSISDN and two IMSIs in the FNR. It will also verify the routing to the HLR using different traffic cases. The result of the test should be that all definitions work and the calls are routed through. ________________________________________________________ 1. Action: Print the default IMSI, used to obtain the default route in the FNR database. FGDRP; Result: FNR DEFAULT ROUTE DATA Comment: Make a note of the default IMSI. ________________________________________________________ 2. Action: Change the default IMSI so it routes towards HLR1 FGDRC:IMSI=hlr1imsi; Result: EXECUTED Comment: HLR1IMSI = IMSI No. that routes towards HLR1. ________________________________________________________ 3. Action: Verify the definition of the default IMSI. FGDRP; Result: FNR DEFAULT ROUTE DATA ________________________________________________________ 4. Action: Initiate a relationship between MSISDN1 and IMSI1 in the FNR. FGNTI:MSISDN=msisdn1,IMSI=imsi1; Result: EXECUTED ________________________________________________________ 5. Action: Verify the relationship.

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

9 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

FGNTP:MSISDN=msisdn1; Result: FNR SUBSCRIBER NUMBER TRANSLATION DATA ________________________________________________________ 6. Action: Make a location update with MS1 and MS3. Result: The location update was successful. ________________________________________________________ 7. Action: Establish a call from MS1 to MS3. Result: Speech connection. ________________________________________________________ 8. Action: Release the call. Result: The call is released. ________________________________________________________ 9. Action: Establish a call from MS3 to MS1. Result: Speech connection. ________________________________________________________ 10. Action: Release the call. Result: The call is released. ________________________________________________________ 11. Action: Change the relationship so MSISDN1 uses IMSI2 instead of IMSI1. FGNTC:MSISDN=msisdn1,IMSI=imsi2; Result: EXECUTED ________________________________________________________ 12. Action: Verify the relationship. FGNTP:MSISDN=msisdn1; Result:

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

10 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

FNR SUBSCRIBER NUMBER TRANSLATION DATA ________________________________________________________ 13. Action: Make a location update with MS2. Result: The location update was successful. ________________________________________________________ 14. Action: Establish a call from MS2 to MS3. Result: Speech connection. ________________________________________________________ 15. Action: Release the call. Result: The call is released. ________________________________________________________ 16. Action: Establish a call from MS3 to MS2. Result: Speech connection. ________________________________________________________ 17. Action: Release the call. Result: The call is released. ________________________________________________________ 18. Action: Undefine the relationship between MSISDN1 and IMSI2. FGNTE:MSISDN=msisdn1; Result: EXECUTED ________________________________________________________ 19. Action: Verify the removal of the relationship. FGNTP:MSISDN=msisdn1. Result: FNR SUBSCRIBER NUMBER TRANSLATION DATA ________________________________________________________

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

11 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

20. Action: Restore the default IMSI. FGDRC:IMSI=defimsi; Result: EXECUTED Comment: Use the IMSI retrieved in step 1. ________________________________________________________

3.2

Default Routing
This case demonstrates the default routing procedure. This is applicable when a fault occurs in the IMSI translation (e.g. missing translation data) or if translation data is incorrectly defined. The default IMSI is translated into an MGT which leads to a default route, normally to the HLR. Two mobiles are used in this part. MS1 should be registered in HLR1 and MS2 in HLR2. ________________________________________________________ 1. Action: Print the default IMSI, used to obtain the default route in the FNR database. FGDRP; Result: FNR DEFAULT ROUTE DATA Comment: Make a note of the default IMSI. ________________________________________________________ 2. Action: Change the default IMSI to route to HLR1, if not already done. FGDRC:IMSI=hlr1imsi; Result: EXECUTED ________________________________________________________ 3. Action: Make sure that no IMSI translation is defined in the FNR data base for MS2. FGNTE:MSISDN=ms2msisdn; Result:

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

12 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

EXECUTED or FAULT CODE 14 ________________________________________________________ 4. Action: Switch MS1 and MS2 off and on. Result: MS1 and MS2 perform location updating. Comment: MS1 should be registered in HLR1 and MS2 in HLR2. ________________________________________________________ 5. Action: Call MS2 from MS1. Result: The call setup fails. Comment: The interrogation in HLR1 fails, since MS2 is registered in HLR2. ________________________________________________________ 6. Action: Change the default IMSI to route to HLR2. FGDRC:IMSI=hlr2imsi; Result: EXECUTED ________________________________________________________ 7. Action: Switch MS1 and MS2 off and on. Result: MS1 and MS2 perform location updating. Comment: MS1 and MS2 should be registered in HLR1. ________________________________________________________ 8. Action: Call MS2 from MS1. Result: MS1 and MS2 are connected. Comments: Verify speech connection. ________________________________________________________ 9. Action: Disconnect the call.

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

13 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

Result: Call is terminated. ________________________________________________________ 10. Action: Change the default IMSI back to the value obtained in step 1 page 11 . FGDRC:IMSI=defaultimsi; Result: EXECUTED ________________________________________________________

3.3

File Output in FNR

This part demonstrates the output of relationships, for all or a subset of subscribers, from the data base to an external file with a specific format in the IOG. ________________________________________________________ 1. Action: Determine the active subfile. IOIFP:FILE=FNRFOAFILE; Result: FILE ATTRIBUTE INFINITE SEQUENTIAL FILE Comment: Note the active subfile. ________________________________________________________ 2. Action: Initiate File Output for all the MSISDN relations. FGFOI:MSISDN; Result: ORDERED ________________________________________________________ 3. Action: Check status printout. FGFOP; Result:

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

14 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

FNR FILE OUTPUT INITIATE RESULT EXECUTED END ________________________________________________________ 4. Action: Print contents of FNRFOAFILE. IOFAT:FILE=FNRFOAFILE-000x,HEX; Result: FILE DUMP FNRFOAFILE-000x Comment: Check that the format is correct. ________________________________________________________

3.4

Stopping of File Output process in FNR

This part demonstrates stopping the pending File Output process. ________________________________________________________ 1. Action: Determine the active subfile. IOIFP:FILE=FNRFOAFILE; Result: FILE ATTRIBUTE INFINITE SEQUENTIAL FILE Comment: Note the active subfile. ________________________________________________________ 2. Action: Initiate File Output for all the MSISDN relations. FGFOI:MSISDN,TIME=hhmm; Result: ORDERED ________________________________________________________

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

15 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

3.

Action: Check that the File Output status is pending. FGFOP; Result: FILE OUTPUT INITIATE RESULT Comment: Check that status is pending.

________________________________________________________ 4. Action: Stop the File Output process. FGFOE; Result: EXECUTED Result: FNR FILE OUTPUT INITIATE RESULT NOT EXECUTED FAULT CODE 39 PROCESS STOPPED BY COMMAND Comment: Verify that the correct result printout is printed. ________________________________________________________

3.5

File Input of MSISDN in FNR from HLR

This part demonstrates how to transfer data from the HLR to the FNR. First the HLR data is dumped into file HPSDFOAFILE. The contents of this file is copied to file FLNUMFILE and then transferred to the FNR by command. This part also include resetting the File Transfer Log. ________________________________________________________ 1. Action: Determine the active subfile. IOIFP:FILE=HPSDFOAFILE; Result:

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

16 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

FILE ATTRIBUTE INFINITE SEQUENTIAL FILE Comment: Note the active subfile. ________________________________________________________ 2. Action: Copy the MSISDN-IMSI relations in HLR2 to the file. HGPFI:IMSIS=imsis; Result: HLR SUBSCRIBER DATA FILE OUTPUT INITIATE RESULT EXECUTED END Comment: Enter the command on an IO-terminal connected to HLR2. ________________________________________________________ 3. Action: Copy the data from the active subfile of HPSDFOAFILE to FLNUMFILE. INMCT:SPG=0; INFIT:FILE1=HPSDFOAFILE-000x,FILE2=FLNUMFILE,PHYSICAL; END; Result: FILE COPY INTERNAL EXECUTED ________________________________________________________ 4. Action: Transfer the data from FLNUMFILE to the FNR data base. FGFII:FILETYPE=HLRFO,OPER=INIT,TIME=hhmm; Result: ORDERED Comment: Make a note of the time the command was schedule. ________________________________________________________

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

17 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

5.

Action: Check the progress after a few seconds. FGFIP; Result: FNR FILE INPUT LOG DATA Result: Check that the STOPTIME field is empty. Check that the STATUS field is ACTIVE.

________________________________________________________ 6. Action: Wait for completion of input. Result: FNR FILE INPUT INITIATE RESULT EXECUTED Comment: Note the time of completion. ________________________________________________________ 7. Action: Check the defined data. FGNTP:MSISDN=ALL; Result: The new pairs have been defined correctly. ________________________________________________________ 8. Action: Print the logfile. FGFIP:EXT; Result: FNR FILE INPUT LOG DATA Comment: There should be some previously defined pairs listed in the data.

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

18 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

________________________________________________________ 9. Action: Reset the file transfer log. FGFRI; Result: EXECUTED ________________________________________________________ 10. Action: Print the logfile. FGFIP:EXT; Result: FNR FILE INPUT LOG DATA Comment: Additional data removed. STARTTIME and STOPTIME are still present and also numbers of defined and failed pairs. ________________________________________________________

3.6

Ending Database of MSISDN in FNR from HLR

This part demonstrates how to verify that the relationships can be ended with the File Input process from a File Output file created in HLR. ________________________________________________________ 1. Action: Determine the active subfile. IOIFP:FILE=HPSDFOAFILE; Result: FILE ATTRIBUTE INFINITE SEQUENTIAL FILE Comment: Note the active subfile. ________________________________________________________ 2. Action: Copy the MSISDN-IMSI relations in HLR2 to the file. HGPFI:IMSIS=imsis; Result:

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

19 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

HLR SUBSCRIBER DATA FILE OUTPUT INITIATE RESULT EXECUTED END Comment: Enter the command on an IO-terminal connected to HLR2. ________________________________________________________ 3. Action: Copy the data from the active subfile of HPSDFOAFILE to FLNUMFILE. INMCT:SPG=0; INFIT:FILE1=HPSDFOAFILE-000x,FILE2=FLNUMFILE,PHYSICAL; END; Result: FILE COPY INTERNAL EXECUTED ________________________________________________________ 4. Action: Transfer the data from FLNUMFILE to the FNR data base. FGFII:FILETYPE=HLRFO,OPER=INIT; Result: EXECUTED Comment: The FNR database have defined subscriptions corresponding to the MSISDN/IMSI pairs in the HPSDFOAFILE. ________________________________________________________ 5. Action: Check the defined data. FGNTP:MSISDN=ALL; Result: The new pairs have been defined correctly. ________________________________________________________

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

20 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

6.

Action: Start to delete the database. FGFII:FILETYPE=HLRFO,OPER=END,TIME=hhmm; Result: ORDERED Comment: Make a note of the time the command was scheduled.

________________________________________________________ 7. Action: Check the progress after a few seconds after the scheduled time. FGFIP; Result: FNR FILE INPUT LOG DATA Comment: Check that the STOPTIME field is empty. Check that the STATUS field is ACTIVE. Check that the OPERATION field is END. ________________________________________________________ 8. Action: Wait for completion of input. Result: FNR FILE INPUT INITIATE RESULT EXECUTED Comment: Note the time of completion. ________________________________________________________ 9. Action: Print the log file. FGFIP:EXT; Result:

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

21 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

FNR FILE INPUT LOGDATA Comment: Check that the details are correct. ________________________________________________________ 10. Action: Check that the subscription have been ended. FGNTP:MSISDN=ALL; Result: The MSISDN/IMSI pairs removed from database. ________________________________________________________

3.7

File Input of MSISDN in FNR from FNR

This part demonstrates how to transfer data from a FNR to the another FNR. First the FNR data is dumped into file FNRFOAFILE. The contents of this file is copied to file FNRFIAFILE and then transferred to the FNR by command. ________________________________________________________ 1. Action: Determine the active subfile. IOIFP:FILE=FNRFOAFILE; Result: FILE ATTRIBUTE INFINITE SEQUENTIAL FILE Comment: Note the active subfile. ________________________________________________________ 2. Action: Copy the MSISDN relations in FNR to the file. FGFOI:MSISDN; Result: ORDERD ________________________________________________________ 3. Action: Copy the data from the active subfile of FNRFOAFILE to FNRFIAFILE.

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

22 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

INMCT:SPG=0; INFIT:FILE1=FNRFOAFILE-000x,FILE2=FNRFIAFILE,PHYSICAL; END; Result: FILE COPY INTERNAL EXECUTED ________________________________________________________ 4. Action: Transfer the data from FNRFIAFILE to the FNR data base. FGFII:FILETYPE=FNRFO,OPER=INIT,TIME=hhmm; Result: ORDERED Result: Make a note of the time the command was scheduled. ________________________________________________________ 5. Action: Check the progress after a few seconds after the scheduled time. FGFIP; Result: FNR FILE INPUT LOG DATA Comment: Check that the STOPTIME field is empty. Check that the STATUS field is ACTIVE. Check that the OPERATION field is INITIATE. ________________________________________________________ 6. Action: Wait for completion of input. Result: FNR FILE INPUT INITIATE RESULT

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

23 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

EXECUTED Comment: Note the time of completion. ________________________________________________________ 7. Action: Check the defined data FGNTP:MSISDN=ALL; FGNTP:MSISDNS=ALL; Result: Data has been defined correctly. ________________________________________________________ 8. Action: Print the log file. FGFIP:EXT; Result: FNR FILE INPUT LOG DATA Comment: Check that the details are correct. ________________________________________________________

3.8

Ending File Input of MSISDN in FNR from FNR

This part demonstrates that the relationships can be ended with the File Input process from a File Output file created in FNR. ________________________________________________________ 1. Action: Determine the active subfile. IOIFP:FILE=FNRFOAFILE; Result: FILE ATTRIBUTE INFINITE SEQUENTIAL FILE Comment: Note the active subfile.

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

24 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

________________________________________________________ 2. Action: Copy the MSISDN relations in FNR to the file. FGFOI:MSISDN; Result: ORDERED ________________________________________________________ 3. Action: Copy the data from the active subfile of FNRFOAFILE to FNRFIAFILE. INMCT:SPG=0; INFIT:FILE1=FNRFOAFILE-000x,FILE2=FNRFIAFILE,PHYSICAL; END; Result: FILE COPY INTERNAL ________________________________________________________ 4. Action: Transfer the data from FNRFIAFILE to the FNR data base. FGFII:FILETYPE=FNRFO,OPER=INIT,TIME=hhmm; Result: EXECUTED Comment: The FNR database has defined relationships corresponding to the pairs of MSISDN/IMSI, MSISDN/NPREFIX, MSISDNS/NPREFIX. ________________________________________________________ 5. Action: Start to end the process. FGFIE; Result: EXECUTED ________________________________________________________

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

25 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

6.

Action: Wait for the printout from data transfer. Result: FNR FILE INPUT INITIATE RESULT FAULT CODE 39 PROCESS STOPPED BY COMMAND

________________________________________________________ 7. Action: Check that there are no relationships defined. FGNTP:MSISDN=ALL; FGNTP:MSISDNS=ALL; ________________________________________________________

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

26 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

HELPFUL HINTS

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

27 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

ABBREVIATIONS
FNR GSM HLR IMSI MS MSC MSISDN UE Flexible Numbering Global System for Mobile communication Home Location Register International Mobile Subscriber Identity Mobile Station Mobile Switching Centre Mobile Station ISDN number User Equipment

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

28 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

6
Table 1 Demo Case no.

TEST CASE SUMMARY LIST

Flexible Numbering Demo Case name Date Demo Appl Y Flexible Allocation of MSISDN Log files Comments Default Routing Log files Comments File Ouput for in FNR Log files Comments Stopping of File Ouput process in FNR N Test bed / SW status Demo Result Sign. of Tester Trouble Report Issued

Log files Comments

File Input of MSISDN in FNR from HLR

Log files Comments

Ending Database of MSISDN in FNR from HLR

Log files Comments

File Input of MSISDN in FNR from FNR

Log files Comments

E
Prepared (also subject responsible if other)

DEMO INSTRUCTION
No

29 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir

Approved Checked

3/1538-APT 210 26 Uae

Date Rev Reference

ERA/UG/BIFC (Mikael sterberg)

2002-03-27

PB2

Demo Case no.

Demo Case name

Date

Demo Appl Y N

Test bed / SW status

Demo Result

Sign. of Tester

Trouble Report Issued

Ending File Input of MSISDN in FNR from FNR

Log files Comments

Appendix: Demo performed by: Result: P F PR Passed Failed Passed after retest