3 1538 Apt 210 26 Pb2 Flexible Numbering

DEMO INSTRUCTION 1 ( 29 )

ERA/FZ/BIF Vjekoslav Budimir 3/1538-APT 210 26 Uae

ERA/UG/BIFC (Mikael Österberg) 2002-03-27 PB2

Prepared (also subject responsible if other) No

Approved Checked Date Rev Reference

E

FLEXIBLE NUMBERING

Contents Page

1 GENERAL .. .. . .. . . .. . .. . . . . .. . . . . . . . . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . 21.1 Application . . .. . .. . . .. . .. . .. . . . . . . . . .. . .. . .. . . . . . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 21.2 Features . .. . .. . .. . . .. . .. . .. . . . . . . . . .. . .. . .. . . . . . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 21.3 Introduction . .. . .. . . .. . .. . .. . . . . . . . . .. . .. . .. . . . . . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 21.4 Concepts . .. . .. . . . . . .. . . . . .. . . . . . . . . .. . .. . .. . . . . . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 21.5 Commands and Printouts . .. . . .. . .. . .. . .. . . . . . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 2

2 DEMO PREPARATION ... . .. . . .. . .. . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . 52.1 Demo Prerequisites . . .. . .. . . . . . .. . .. . .. . .. . . . . . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 52.2 Demo Aid Requirements . . .. . . .. . .. . .. . .. . . . . . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 52.3 Preparation of Demo Parameter Values . . .. . .. . .. . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 6

3 DEMO EXECUTION ... . .. . .. . . .. . .. . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . 83.1 Flexible Allocation of MSISDN .. . .. . .. . . . . . .. . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 83.2 Default Routing .. . . .. . .. . .. . .. . . . . . .. . .. . .. . . . . . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 113.3 File Output in FNR .. . .. . .. . . . . . .. . .. . .. . .. . . . . . .. . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 133.4 Stopping of File Output process in FNR .. .. . .. . .. . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 143.5 File Input of MSISDN in FNR from HLR .. .. . .. . .. . . . . . . . . .. . . . . .. . . . . . . . . . . . .. . 153.6 Ending Database of MSISDN in FNR from HLR .. .. . . .. . .. . .. . .. . . . . . . . . . . . .. . 183.7 File Input of MSISDN in FNR from FNR .. .. . .. . .. . . . . . .. . .. . . . . .. . . . . . . . . . . . .. . 213.8 Ending File Input of MSISDN in FNR from FNR .. .. . . .. . .. . .. . .. . . . . . . . . . . . .. . 23

4 HELPFUL HINTS ... . .. . .. . . . . . .. . . . . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . 26

5 ABBREVIATIONS .. . .. . .. . .. . . .. . . . . .. . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . 27

6 TEST CASE SUMMARY LIST . . .. . .. . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. . 28

A4 XSEIF R2






E

1 GENERAL

1.1 Application

This is a general document to be used for System Demonstration of Flexiblenumbering in GSM/UMTS.

1.2 Features

NF 628.1 Flexible allocation of MSISDN

NF 690.1 File Input for Subscriber Data in FNR

NF 691.1 File Output for Subscriber Data in FNR

NF 975.1 FNR basic package information

1.3 Introduction

The Flexible Numbering function enables mobile operators to allocatesubscriber identities in a flexible way. It is possible to allocate any MSISDNnumber to an IMSI. This is done by introducing a node called Flexible NumberRegister (FNR). The FNR acts like a gateway for the HLRs and routes themessages to the correct HLR.

The function File Input/Output for Subscriber Data gives the operation andmaintenance 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 isadministered by the operator by means of commands provided to allow initiationand ending of subscriber definitions file input/output, as well as printing of statusfor the file input/output process. This function is useful, for instance, when theoperator wishes to move large amounts of subscriber data between FNRs.

This demo instruction will demonstrate the functionality “Flexible Allocation ofMSISDN” and “File Input for Flexible Allocation of MSISDN” in the FNR. Thefunctionality File Input/Output for Subscriber Data is also demonstrated.

1.4 Concepts

-

1.5 Commands and Printouts

1.5.1 Commands

FGDRC Flexible Numbering Register, Default Route Translation,Change

FGDRP Flexible Numbering Register, Default Route Translation,Print






E

FGFIE Flexible Numbering Register, File Input, End

FGFII Flexible Numbering Register, File Input, Initiate

FGFIP Flexible Numbering Register, File Input Log Data, Print

FGFOE Flexible Numbering Register, File Output, End

FGFOI Flexible Numbering Register, File Output Data, Initiate

FGFOP Flexible Numbering Register, File Output, Print

FGFRI Flexible Numbering Register, File Input Log Data Reset,Initiate

FGNTC Flexible Numbering Register, Subscriber NumberTranslation, Change

FGNTE Flexible Numbering Register, Subscriber NumberTranslation, End

FGNTI Flexible Numbering Register, Subscriber NumberTranslation, Initiate

FGNTP Flexible Numbering Register, Subscriber NumberTranslation, Print

HGPFI Home Location Register, Permanent Subscriber Data FileOutput, Initiate

INFIP IO Subsystem Functions File Administration, Print

INFII IO Subsystem Functions File Administration, Initiate

INFIT IO Subsystem Functions File Administration, Transfer

IOIFI IO Infinite Sequential File Functions, Insert

IOIFP 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

FNR SUBSCRIBER NUMBER TRANSLATION DATA

HLR SUBSCRIBER DATA FILE OUTPUT INITIATE RESULT






E

2 DEMO PREPARATION

2.1 Demo Prerequisites

-

2.2 Demo Aid Requirements

2.2.1 Hardware Tools

Three Mobile Stations or User Equipment.

For the purpose of this document Mobile Stations have been used, but they canbe substituted for User Equipment.

2.2.2 Software Tools

-

2.2.3 Network Configuration

BSC

RNC

MS2/UE2

BTS

IMSI 2

MS3/UE3FNR

MSC/VLR

MSC SERVER

HLR 1

IMSI 3

HLR 2

IMSI 1

MS1/UE1

MGW

Figure 1 Network configuration

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






E

2.3 Preparation of Demo Parameter Values

2.3.1 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 beactive.

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, theleading 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

• 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)=H’F34; ! CC !

SET VAR FLNAN 296(29)=H’0F3; ! CC => 4 !

SET VAR FLNAN 296(30)=H’00F; ! CC => 8 !

SET VAR FLNAN 296(40)=6; ! IMSISERIELENGTH !

SET VAR FLNAN 0:163(0)=H’7260; ! IMSISERIE0L !

SET VAR FLNAN 0:163(1)=H’FF84; ! IMSISERIE0H !

SET VAR FLNAN 0:163(2)=H’7737; ! MGTSERIE0L !

SET VAR FLNAN 0:163(3)=H’F127; ! MGTSERIE0H !

END TEST;

2.3.2 Exchange Dependent Data

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

2.3.3 Check of data

-






E

3 DEMO EXECUTION

3.1 Flexible Allocation of MSISDN

This demo case will verify the definition, change and removal of a relationshipbetween an MSISDN and two IMSIs in the FNR. It will also verify the routing tothe HLR using different traffic cases.

The result of the test should be that all definitions work and the calls arerouted through.

________________________________________________________

1. Action: Print the default IMSI, used to obtain the default route in theFNR 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

FGNTP:MSISDN=msisdn1;

Result:


________________________________________________________

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.

________________________________________________________



________________________________________________________



________________________________________________________

11. Action: Change the relationship so MSISDN1 uses IMSI2 instead ofIMSI1.

FGNTC:MSISDN=msisdn1,IMSI=imsi2;

Result: EXECUTED

________________________________________________________

12. Action: Verify the relationship.

FGNTP:MSISDN=msisdn1;

Result:






E


________________________________________________________

13. Action: Make a location update with MS2.

Result: The location update was successful.

________________________________________________________



________________________________________________________



________________________________________________________



________________________________________________________



________________________________________________________

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:


________________________________________________________






E

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 applicablewhen a fault occurs in the IMSI translation (e.g. missing translation data) or iftranslation data is incorrectly defined. The default IMSI is translated into anMGT which leads to a default route, normally to the HLR.

Two mobiles are used in this part. MS1 should be registered in HLR1 andMS2 in HLR2.

________________________________________________________

1. Action: Print the default IMSI, used to obtain the default route in theFNR 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.


Result:

EXECUTED

________________________________________________________

3. Action: Make sure that no IMSI translation is defined in the FNR database for MS2.

FGNTE:MSISDN=ms2msisdn;

Result:






E

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

________________________________________________________

6. Action: Change the default IMSI to route to HLR2.


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

Result: Call is terminated.

________________________________________________________

10. Action: Change the default IMSI back to the value obtained in step 1page 11 .

FGDRC:IMSI=defaultimsi;

Result:

EXECUTED

________________________________________________________

3.3 File Output in FNR

This part demonstrates the output of relationships, for all or a subset ofsubscribers, from the data base to an external file with a specific formatin the IOG.

________________________________________________________

1. Action: Determine the active subfile.

IOIFP:FILE=FNRFOAFILE;

Result:


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

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.

________________________________________________________



Result:



________________________________________________________

2. Action: Initiate File Output for all the MSISDN relations.

FGFOI:MSISDN,TIME=hhmm;

Result:

ORDERED

________________________________________________________






E

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 fileis copied to file FLNUMFILE and then transferred to the FNR by command.This part also include resetting the File Transfer Log.

________________________________________________________


IOIFP:FILE=HPSDFOAFILE;

Result:






E



________________________________________________________

2. Action: Copy the MSISDN-IMSI relations in HLR2 to the file.

HGPFI:IMSIS=imsis;

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

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

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:


Comment:

There should be some previously defined pairs listed in the data.






E

________________________________________________________

9. Action: Reset the file transfer log.

FGFRI;

Result:

EXECUTED

________________________________________________________

10. Action: Print the logfile.

FGFIP:EXT;

Result:


Comment:

Additional data removed. STARTTIME and STOPTIME are still presentand 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 withthe File Input process from a File Output file created in HLR.

________________________________________________________


IOIFP:FILE=HPSDFOAFILE;

Result:



________________________________________________________

2. Action: Copy the MSISDN-IMSI relations in HLR2 to the file.

HGPFI:IMSIS=imsis;

Result:






E


EXECUTED

END

Comment: Enter the command on an IO-terminal connected to HLR2.

________________________________________________________

3. Action: Copy the data from the active subfile of HPSDFOAFILE toFLNUMFILE.

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 theMSISDN/IMSI pairs in the HPSDFOAFILE.

________________________________________________________

5. Action: Check the defined data.

FGNTP:MSISDN=ALL;

Result:

The new pairs have been defined correctly.

________________________________________________________






E

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:


Comment:



Check that the OPERATION field is END.

________________________________________________________


Result:


EXECUTED

Comment:


________________________________________________________

9. Action: Print the log file.

FGFIP:EXT;

Result:






E

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 iscopied to file FNRFIAFILE and then transferred to the FNR by command.

________________________________________________________



Result:



________________________________________________________

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






E

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:


Comment:



Check that the OPERATION field is INITIATE.

________________________________________________________


Result:







E

EXECUTED

Comment:


________________________________________________________

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:


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 Inputprocess from a File Output file created in FNR.

________________________________________________________



Result:








E

________________________________________________________

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

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 ofMSISDN/IMSI, MSISDN/NPREFIX, MSISDNS/NPREFIX.

________________________________________________________

5. Action: Start to end the process.

FGFIE;

Result:

EXECUTED

________________________________________________________






E

6. Action: Wait for the printout from data transfer.

Result:


FAULT CODE 39

PROCESS STOPPED BY COMMAND

________________________________________________________

7. Action: Check that there are no relationships defined.

FGNTP:MSISDN=ALL;

FGNTP:MSISDNS=ALL;

________________________________________________________






E

4 HELPFUL HINTS






E

5 ABBREVIATIONS

FNR Flexible Numbering

GSM Global System for Mobile communication

HLR Home Location Register

IMSI International Mobile Subscriber Identity

MS Mobile Station

MSC Mobile Switching Centre

MSISDN Mobile Station ISDN number

UE User Equipment






E

6 TEST CASE SUMMARY LIST

Table 1 Flexible Numbering

DemoAppl

DemoCaseno.

Demo Case name Date

Y N

Test bed /SW status

DemoResult

Sign. ofTester

TroubleReportIssued

Log files

Flexible Allocation ofMSISDN

Comments

Log files

Default Routing

Comments

Log files

File Ouput for in FNR

Comments

Log files

Stopping of File Ouputprocess in FNR

Comments

Log files

File Input of MSISDN in FNRfrom HLR

Comments

Log files

Ending Database of MSISDNin FNR from HLR

Comments

Log files

File Input of MSISDN in FNRfrom FNR

Comments






E

DemoAppl

DemoCaseno.

Demo Case name Date

Y N

Test bed /SW status

DemoResult

Sign. ofTester

TroubleReportIssued

Log files

Ending File Input of MSISDNin FNR from FNR

Comments

Appendix:

Demo performed by:

Result: P Passed

F Failed

PR Passed after retest

Date post:	25-Oct-2014
Category:	Documents
Upload:	bisibambo
View:	99 times
Download:	3 times

3 1538 Apt 210 26 Pb2 Flexible Numbering

Documents