NANC 269
Documentation change for Bulk Data Download
Origination Date :03/16/1999
Originator:National Number Pooling Sub-Com'ttee
Description:
While reviewing the Natl N Pool test cases, it was noted that the bulk data download functionality for Time Range and NPA-NXX Range, is not documented in the FRS.
It has been requested by the Sub-Committee to update this information in the FRS.
FRS
Section 3.9 Bulk Data Download Functionality (new section)
Req 3.9.1 Bulk Data Download – File Creation
NPAC SMS shall provide a mechanism that allows a Service Provider to recover network data and subscription data in file format.
Req 3.9.2 Bulk Data Download – File Naming Convention
NPAC SMS shall follow the file naming convention as described in Appendix E.
Req 3.9.3 Bulk Data Download – File Format
NPAC SMS shall follow the file format as described in Appendix E.
Req 3.9.4 Bulk Data Download – Selection Criteria for File Creation
NPAC SMS shall allow network data only, subscription data only, or both, as selection criteria for bulk data download file generation.
Req 3.9.5 Bulk Data Download – Required Selection Criteria for Network Data File Generation
NPAC SMS shall require, as selection criteria for network bulk data download file generation, a Service Provider filter of either a single Service Provider ID or ‘All Service Providers’.
Req 3.9.6 Bulk Data Download – Required Selection Criteria for Subscription Data File Generation
NPAC SMS shall require, as selection criteria for subscription bulk data download file generation, a Service Provider filter of either a single Service Provider ID or ‘All Service Providers’, and a start NPA-NXX–station (10 digits).
Req 3.9.7 Bulk Data Download – Optional Selection Criteria for Subscription Data File Generation
NPAC SMS shall accept, as optional selection criteria for subscription bulk data download file generation, an end NPA-NXX-station (10 digits), a start activation date and time, and an end activation date and time.
Req 3.9.8 Bulk Data Download – FTP Sub-Directory
NPAC SMS shall automatically put the subscription bulk data download file into the FTP sub-directory of the Service Provider, based on SPID, that requested the creation of the subscription bulk data download file.
Final Resolution:
Backwards Compatible: YES
Apr LNPAWG (DC), group O.K. with this.
This will be put into the queue of CMA updates to the FRS. No date has been scheduled.
Aug LNPAWG (Portland), reviewed the seven new requirements for the new section (3.9 BDD functionality). Will add another requirement to capture the automatic placement of the file into the requesting SP’s FTP sub-directory.
Sep LNPAWG (Chicago), reviewed new requirement (req 3.9.8). It was requested to add a note to Appendix E to indicate that the current functionality uses the activation timestamp criteria, and this will NOT include subsequent modifications made within the activation timestamp range. For example, an SV was activated three months ago, then a modify active request was issued during the 12 hours of an SP’s downtime. When the SP requests a bulk data download for those missing 12 hours, the modify active request will NOT be included in the BDD file.
Oct LNPAWG (KC), group accepted updates. Move to next doc category.
Related Release:
3.0.0
Status: Implemented