NANC 417

Provide record count(s) for BDD Files and Delta BDD Files

Origination Date :12/18/2006

Originator:Syniverse

Description:

When a BDD file is distributed, the number of records that are included in the file is not known. In order to ensure that the file was completely generated and received intact, a record count for the file should be included.

Since the NPAC is considered the database of record, alternatives such as counting the lines in the BDD file to compare it to what is currently in the LSMS are not considered genuinely accurate since the number of records could match, yet the content could be different. Even a small difference in the pool block BDD file can make a significant impact on the network, because of the 1000-to-1 representation. Therefore it is prudent to take steps to eliminate errors before processing the BDD files. This could include creating a record count or “snapshot” of the file contents when the BDD file is created. This will provide a reference point to compare to the BDD files received. Currently, there is no way to validate the record counts in the BDD files as they are received, thereby ensuring data integrity.

Description of Change:

This change order would add a record count to the BDD file. Since the BDD file contains detailed information on a row-by-row basis, the count would have to be added in either the file name or in a comment record, depending on the technical implementation.

There may be backward-compatibility issues that need to be discussed and resolved.

The requested record count would apply to all five file types (SPID, NPA-NXX, dash-X, LRN, NPB, SV).

In the case of delta BDDs, which are run from the NPAC GUI, the same principal(s) would be applied for the record count

Req 1 Service Provider BDD Record Count Indicator

NPAC SMS shall provide a Service Provider BDD Record Count Indicator tunable parameter which defines whether a Service Provider supports the commented record count information in their BDD Files.

Req 2 Service Provider BDD Record Count Indicator Default

NPAC SMS shall default the Service Provider BDD Record Count Indicator tunable parameter to FALSE.

Req 3 Service Provider BDD Record Count Indicator Modification

NPAC SMS shall allow NPAC Personnel, via the NPAC Administrative Interface, to modify the Service Provider BDD Record Count Indicator tunable parameter.

Updates to Appendix E of the FRS.

Appendix E. Download File Examples

The NPAC can generate Bulk Data Download files for Network Data (including SPID, LRN, NPA-NXX and NPA-NXX-X), Subscription Versions (including Number Pool Blocks) and Notifications.

All fields within files discussed in the following section are variable length. The download reason in all “Active-like” download files is always set to new. The download reason in all “Latest View” download files is set to the appropriate download reason based on activation/modification/deletion activity. ASCII 13 is the value used as the value for carriage return (CR) in the download files.

All Time Stamps contained within the download files and SMURF files, and file names are in GMT (Greenwich Mean Time). Files that contain three timestamps reference the time the files is created, and start and end time range. When the time range is not specified, the default start timestamp is 00-00-0000000000 and the default end timestamp is 99-99-9999999999.

The record count information will be added to the end of the BDD files. It will start with a pound sign (#) followed by the number of data records in the file. For example, if there are twenty-two (22) LRN records in the file, the 23^rd line would contain a pound sign, a space, and the number 22. The record count information will only be included in the BDD file if the Service Provider’s BDD Record Count Indicator is set to TRUE.

IIS

No Change Required.

GDMO

No Change Required.

ASN.1

No Change Required.

Final Resolution:

Move to closed/no-action.

Related Release:

N/A.

Status: Closed