File Naming Conventions

All BDD file names include a creation timestamp, which is represented as <create>. Time Range BDD file names also contain start (<start>) and end (<end>) timestamps. All timestamps are represented as DD-MM-YYYYhhmmss where:

DD represents a two-digit day

MM represents a two-digit month

YYYY represents a four-digit year

hh represents a two-digit hour

mm represents a two-digit minute

ss represents a two-digit second

An example timestamp is 11-10-2006123015.

For Object Range BDD files, <start> is always 00-00-0000000000 and <end> is always 99-99-9999999999. These are the default values.

Table 1 references the pages where you can find information about file naming conventions for each data type:

Determining Naming Conventions for NPAC Data Files
Type of Data File	See:
Subscription Version (Object Ranges and Time Ranges are supported)	Table C-2
Number Pool Block (Object Ranges and Time Ranges are supported)	Table C-3
LRN, NPA-NXX, and NPA-NXXX (Only Objects are supported)	Table C-4
SPID (Only Objects are supported)	Table C-5

Note: Object ranges are used so that potentially very large files can be broken down into smaller files based on NPA-NXX (for SVs) or NPA-NXX-X (for NPBs) ranges. Because of the much smaller number of LRN, NPA-NXX, NPA-NXX-X, or SPID objects, ranges are not supported for these data file types.

Subscription Version File Naming Convention

The file name for subscription version files is represented as <NPANXX-NPANXX>, which indicates the range of NPA-NXX values contained in the download file. The file extension values depend on whether you are requesting a file for an Object Range BDD or for a Time Range BDD, as shown in Table C-2.

NPAC File Naming Convention for Subscription Version Data File
Range Type	Naming Convention
Object Range BDD	<NPANXX-NPANXX>.<create>².00-00-0000000000.99-99-9999999999
Time Range¹ BDD	<NPANXX-NPANXX>.<create>.<start>.<end>²
¹Time Range files are supported only if you have installed the NANC 3.2 feature ²For format of <create>, <start>, and <end>, see File Naming Conventions.

Following are examples of uses for subscription version BDD files:

If you need to bulk download all subscription versions from the NPAC, use the following file name:
```
<000000-999999>.<create>.00-00-0000000000.99-99-9999999999
```
If you need to bulk download all subscription versions for a time period from midnight February 12, 2006 to midnight February 13, 2006 in a file created February 14, 2006 at 9:00 a.m., use the following file name:
```
<000000-999999>.14022006090000.12022006000000.13022006000000
```
If you need files to correct an NPA split, specify three Object Range files that have the same NPANXX values before and after the hyphen:
- One file with the old NPANXX value
- One file with the correct new NPANXX value
- One file with the erroneous new NPANXX value
For example, if an NPA split was erroneously entered from 909-860 to 123-860 instead of correctly from 909-860 to 124-860, specify the following files:
- 909860-909860
- 124860-124860
- 123860-123860
Because no file extension is specified in these files, the default values of 00-00-0000000000.99-99-9999999999 are assumed.

Number Pool Block File Naming Convention

The file name for number pool block files is represented as <NPANXXX-NPANXXX>, which indicates the range of EDR NPA-NXXX values contained in the download file. The file extension values depend on whether you are requesting a file for an Object Range BDD or for a Time Range BDD, as shown in Table C-3.

NPAC File Naming Convention for Number Pool Block Data File
Range Type	Naming Convention
Object Range BDD	<NPANXXX-NPANXXX>.<create>².00-00-0000000000.99-99-9999999999
Time Range¹ BDD	<NPANXXX-NPANXXX>.<create>.<start>.<end>²
¹Time Range files are supported only if you have installed the NANC 3.2 feature ²For format of <create>, <start>, and <end>, see File Naming Conventions.

These file types exist only if the NPAC supports Efficient Data Representation (EDR). Following are examples of uses for number pool block BDD files:

If you need to bulk download all number pool blocks from the NPAC, use the following file name:
```
<0000000-9999999>.<create>.00-00-0000000000.99-99-9999999999
```
If you need to bulk download all number pool blocks for a time period from midnight February 12, 2006 to midnight February 13, 2006 in a file created February 14, 2006 at 9:00 a.m., use the following file name:
```
<0000000-9999999>.14022006090000.12022006000000.13022006000000
```
If you need files to correct an NPA split, specify three files, each with the NPANXX value followed by a 0 before the hyphen and the NPANXX value followed by a 9 after the hyphen:
- One file with the old NPANXX value
- One file with the correct new NPANXX value
- One file with the erroneous new NPANXX value
  
  For example, if an NPA split was erroneously entered from 909-860 to 123-860 instead of correctly from 909-860 to 124-860, specify the following files:
- 9098600-9098609
- 1248600-1248609
- 1238600-1238609

Because no file extension is specified in these files, the default values of 00-00-0000000000.99-99-9999999999 are assumed.

LRN, NPA-NXX, and NPA-NXXX File Naming Convention

Note:

In contrast to SVs and NPBs data file types, there are a much smaller number of LRN, NPA-NXX, and NPA-NXX-X objects; therefore, ranges are not supported for these data file types, as shown in Table C-4.

The file name for LRN files is represented as <LRN>, which indicates the LRN value contained in the download file.
The file name for NPA-NXX files is represented as <NPANXX>,which indicates the NPA-NXX value contained in the download file.
The file name for NPA-NXXX files is represented as <NPANXX>, , which indicates the EDR NPA-NXXX value contained in the download file. This file type exists only if the NPAC supports Efficient Data Representation (EDR).

The file extension values depend on whether you are requesting a file for an Object BDD or for a Time Range BDD, as shown in Table C-4.

NPAC File Naming Convention for LRN, NPA-NXX, and NPA-NXXX Network Data Files
Type	Naming Convention
Object BDD	<LRN>.<create>².00-00-0000000000.99-99-9999999999
	<NPANXX>.<create>².00-00-0000000000.99-99-9999999999
	<NPANXX>.<create>².00-00-0000000000.99-99-9999999999
Time Range¹BDD	<LRN>.<create>.<start>.<end>²
	<NPANXX>.<create>.<start>.<end>²
	<NPANXXX>.<create>.<start>.<end>²
¹ Time Range files are supported only if you have installed the NANC3.2 feature ² For format of <create>, <start>, and <end>, see File Naming Conventions.

SPID File Naming Convention

Note:

In contrast to SVs and NPBs data file types, there is a much smaller number of SPID objects; therefore, ranges are not supported for this data file type, as shown in Table C-5.

The SPID naming convention only applies to Object BDD files; Time Range is not supported. The file name for SPID files is represented as <SPID>, which indicates the SPID value contained in the download file..

NPAC File Naming Convention for SPID Network Data File
Type	Naming Convention
Object BDD	<SPID>.<create>².00-00-0000000000.99-99-9999999999
² For format of <create>, <start>, and <end>, see File Naming Conventions.

Only the <create> timestamp field is supported.

Because no file extension is specified in these files, the default values of 00-00-0000000000.99-99-9999999999 are assumed.