GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
GEOGRAPHIC NUMBER
PORTABILITY (GNP)
SCOPING DOCUMENT FOR
THE IMPLEMENTATION OF
INTERFACE SPECIFICATION
RELEASE 4.2 ISSUE 3
ELECTRONIC LINK BETWEEN
TELECOMMUNICATION
OPERATORS
Author : GNP Industry
Working Group
Issue 3
Date
Page 1 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
Table of Contents
1. OBJECTIVES AND SCOPE
3
2. WORK PACKAGE ONE
4
2.1
Order Handling Phase One
4
3. WORK PACKAGE TWO
3.1
5
Order Handling Phase Two
5
4. WORK PACKAGE THREE
4.1
6
Order Handling Phase Three
6
5. WORK PACKAGE FOUR
5.1
7
Order Handling Phase Four
7
6. WORK PACKAGE FIVE
6.1
8
RTR Phase One
8
7. WORK PACKAGE SIX
7.1
10
RTR Phase Two
10
8. WORK PACKAGE SEVEN
11
8.1
RTR Phase Three
11
9. REFERENCES
12
10.
13
Issue 3
HISTORY
Date
Page 2 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
1. Objectives and scope
This document defines the work packages required to deliver the functionality
defined in issue 4 of the GNP Order Automation Interface Specification as agreed by
the GNP Industry Working Group.
The objective of this document is to scope a mutually agreed approach to the
development and implementation of the required changes in a timely manner.
The industry agreed changes are tabulated below with references to the appropriate
sections of the Geographic Number Portability: Interface Specification Issue 4
(Reference document [2]).
Other areas which will probably have an impact on the development schedule are
anticipated to be: National Number Changes (Oftel Project 2000)
 Year 2000 Compliance
 EC NP directive
Issue 3
Date
Page 3 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
2. Work Package One
2.1 Order Handling Phase One
 R & X File Rejection
Sect
Description of change
2.2
File format tables have been changed:
Field types have been clarified - Alpha, Alpha/Numeric, etc
New column “Mandatory status” added.
mandatory, conditional or optional.
States whether field is
New column “Rejection level” added. States whether field errors would
cause File or Record level rejection.
2.3
All fields are case insensitive unless otherwise stated. Filenames and
directory names must be UPPERCASE.
3.3
Clarification of GNP filename rules:
Only 12-character filename in “8.3” format will be processed.
Only UPPERCASE filenames will be processed.
Only GNP file types P, Q, T & U will be recognised & processed.
Only filenames with prefixes U, R or X will be recognised & processed.
3.4
Clarification of GNP filename prefixes:
Clarification of meaning and use of the “A” prefix meaning “transient
state”.
Introduction of new “X” prefix to indicate rejection of a NPAR file due to
invalid or unrecognised Requesting Operator ID. (note: addition to
interface specification since version 3.1, but already in use)
9.1
Issue 3
In a Push/Pull scenario, rejected NPAR files (X & R prefix) will now be
placed in the AO’s NPAA directory rather than left in the AO’s NPAR
directory.
Date
Page 4 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
3. Work Package Two
3.1 Order Handling Phase Two
 Re-submission of R & X files
Sect
Description of change
3.6
Clarification of the generic causes of file level rejection.
Only NPAR file rejection is catered for automatically. Invalid NPAA files
can only be handle manually.
An X-prefix rejected file may be re-submitted using the same filename.
An R-prefix rejected file can only be re-submitted using a new filename.
Issue 3
Date
Page 5 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
4. Work Package Three
4.1 Order Handling Phase Three
 NPAR/NPAA Storage and re-sending (push/pull)
Sect
Description of change
11.3
This appendix states the “agreed” NPAA retention and availability times
if an RO requests a re-send/re-retrieve of an NPAA file.
Issue 3
Date
Page 6 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
5. Work Package Four
5.1 Order Handling Phase Four
 Push/Push for NPAR/NPAA
 NPAR/NPAA Storage and re-sending (push/push)
 NPAR & NPAA records Version 2 for time stamps, new order types and
Authentication code for Subsequent and Simultaneous Mobility.
 RTR flag (Y/N) added to file format version 2
Sect
Description of change
8.1
Clarification of the meaning and usage of Push/Pull and Push/Push file
transfer methods.
Push/Push can be used for NPAR/NPAA files.
10.1
In a Push/Push scenario, rejected NPAR files (X & R prefix) will now be
sent by the AO to the RO’s NPAA directory rather than left in the AO’s
NPAR directory.
11.3
This appendix states the “agreed” NPAA retention and availability times
if an RO requests a re-send/re-retrieve of an NPAA file.
Issue 3
Date
Page 7 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
6. Work Package Five
6.1 RTR Phase One
 R & X File Rejection
 Order Type ‘A’
Sect
Description of change
2.2
File format tables have been changed:
Field types have been clarified - Alpha, Alpha/Numeric, etc
New column “Mandatory status” added.
mandatory, conditional or optional.
States whether field is
New column “Rejection level” added. States whether field errors would
cause File or Record level rejection.
2.3
All fields are case insensitive unless otherwise stated. Filenames and
directory names must be UPPERCASE.
3.3
Clarification of GNP filename rules:
Only 12-character filename in “8.3” format will be processed.
Only UPPERCASE filenames will be processed.
Only GNP file types P, Q, T & U will be recognised & processed.
Only filenames with prefixes U, R or X will be recognised & processed.
3.4
Clarification of GNP filename prefixes:
Clarification of meaning and use of the “A” prefix meaning “transient
state”.
Introduction of new “X” prefix to indicate rejection of a RTAR file due to
invalid or unrecognised Requesting Operator ID.
3.6
Clarification of the generic causes of file level rejection.
Only RTAR file rejection is catered for automatically. Invalid RTAA files
can only be handled manually.
Issue 3
Date
Page 8 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
Sect
Description of change
An X-prefix rejected file may be re-submitted using the same filename.
An R-prefix rejected file can only be re-submitted using a new filename.
A file that does not contain the correct number of “complete” records will
be rejected.
6.1.1
RTAR data record
The RTAR order number is mandatory but does not have to be unique.
8.1
Clarification of the meaning and usage of Push/Pull and Push/Push file
transfer methods.
Only Push/Push can be used for RTAR/RTAA files.
10.3
In a Push/Push scenario, rejected RTAR files (X & R prefix) will now be
sent by the AO to the RO’s RTAA directory rather than sent to the RO’s
RTAR directory.
11.2
Initial RTAA Error Code list is included but subject to major review
shortly.
Issue 3
Date
Page 9 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
7. Work Package Six
7.1 RTR Phase Two
 Order Type ‘B’
Issue 3
Date
Page 10 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
8. Work Package Seven
8.1 RTR Phase Three
 RTAR & RTAA records Version 2 for time stamps
Issue 3
Date
Page 11 of 13
of
Issue
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
9. References
[1] Geographic Number Portability: End to End Process Manual.
Issue 5.3
[2] Geographic Number Portability: Interface Specification
Issue 4.3
Issue 3
Date
Page 12 of 13
of
Issue
.
31/8/99
GNP4SC43.DOC
GEOGRAPHIC NUMBER PORTABILITY INTERFACE SPECIFICATION
SCOPING DOCUMENT
10. History
Version
Issue 1
draft A
Issue 1
draft B
Issue1
draft C
Issue1
draft D
Issue 1
Issue 2
Date
10/12/97
Author(s)
TeleWest
18/12/97
Telewest
20/4/98
Telewest
Comments
First draft scoping document for discussion
with BT.
Second draft containing amendments after
discussions with BT.
Third draft incorporating amendments
3/9/98
Telewest
Fourth draft incorporating amendments
5/7/99
16/7/99
Telewest
Telewest
Issue 3
31/7/99
Telewest
Issued as Issue 1
Issued as Issue 2 to tie in with Interface
Specification 4.2.
In a Push/Push scenario, rejected NPAR files
(X & R prefix) will now be sent by the AO to
the RO’s NPAA directory rather than left in
the AO’s NPAR directory (previously
erroneously stated sent to RO’s NPAR
directory).
References updated to
[1]
Geographic Number Portability: End to
End Process Manual.
[2]
Geographic Number Portability:
Interface Specification.
[3] Test Plan Document For The
Implementation Of Work Packages 1-3
Relating To The Interface Specification
Electronic Link Between Telecommunication
Operators
End of Document
Issue 3
Date
Page 13 of 13
of
Issue
31/8/99
GNP4SC43.DOC