Print this page Print NPIF » NANC Change Orders » NANC 169

NANC 169

Delta Download File Creation by Time Range for SVs

Origination Date :05/23/1997

Originator:Bellcore

Description:

It has been requested that requirements be added to the FRS to allow for creation of a delta download file by date and time range, for SVs.

During Dec ’98 Natl N Pool meeting, discussed need to change functionality when requesting SV BDD with a time range.  Currently, the NPAC provides all “active” SVs based on Activation Broadcast Complete Timestamp.  This creates an issue for modifications that are within the specified time range window, but the Activation was prior to the specified time range.  There is also an issue for Activation Failures.

During Jan LNPAWG meeting, proposed changes to handle two issues, include:
1.  Incorporate the start and end time ranges into the file name.
2.  Need to capture all SV activity (activation, modification, disconnect) into the file, when doing time range.

For #1 (new words in highlighted text ), in FRS Appendix E, Download File Examples,

Subscription versions in the download file are selected by an NPA-NXX begin and end range.  The file name for the Subscriptions download file, where a time range is NOT selected,   will be in the format:

NPANXX-NPANXX.DD-MM-YYYYHH24MISS

The NPANXX-NPANXX values map to the selection criteria and the time stamp maps to the current time (Central Time - standard/daylight) .

The Subscriptions file given in the example would be named:

    303123-303125.10-13-1996081122

In the case where a time range is selected, the file name for the Subscriptions download file with a time range, will be in the format:

NPANXX-NPANXX.DD-MM-YYYYHH24MISS. DD-MM-YYYYHH24MISS. DD-MM-YYYYHH24MISS.TIMEZONE

The NPANXX-NPANXX values map to the selection criteria, the first time stamp maps to the current time (when the file is generated), the second time stamp maps to the start time range, and the third time stamp maps to the end time range.  All three time stamps are represented in Central Time (standard/daylight), even though the Subscription Versions are stored in the NPAC in Greenwich Mean Time.  The TIMEZONE value will contain one of two values, either CST or CDT, depending on the current time zone in the Central Time Zone (when the file is generated).

The Subscriptions file with a time range given in the example would be named:

    303123-303125.10-13-1996081122.10-10-1996000000.10-12-1996115959.CST

Also for #1, no functional requirements or IIS flows are affected by this change.

For #2, new requirements are proposed (see below)

Req 1  Subscription Version Information Bulk Download File Creation – Subscription Versions

NPAC SMS shall allow NPAC personnel to request a bulk data download file for Subscription Version data via the NPAC Administrative Interface.  (existing NPAC SMS functionality)

Req 2  Subscription Version Information Bulk Download File Creation – Selection Criteria

NPAC SMS shall include the Requesting Service Provider, Active/Disconnect Pending/Partial Failure Subscription Versions Only or Latest View of Subscription Version Activity Choice, Time Range in Central Time (standard/daylight), and TN Range as Selection Criteria fields for the Subscription Version bulk data download file via the NPAC Administrative Interface.

Req 3  Subscription Version Information Bulk Download File Creation – Active/Disconnect Pending/Partial Failure Subscription Versions Only or Latest View of Subscription Version Activity Choice

NPAC SMS shall allow NPAC Personnel to select either Active/Disconnect Pending/Partial Failure Subscription Versions Only or Latest View of Subscription Version Activity , and shall use the selected choice, for Subscription Version data.

Req 4  Subscription Version Information Bulk Download File Creation – Data in Active/Disconnect pending/Partial Failure Subscription Versions Only Choice

NPAC SMS shall use the Active/Disconnect Pending/Partial Failure Subscription Versions Only  selection to only include Subscription Versions with a status of either Active, Disconnect Pending or Partial Failure in the Subscription Version Bulk Data Download file.

Req 5  Subscription Version Information Bulk Download File Creation – Data in Latest View of Subscription Version Activity Choice

NPAC SMS shall use the Latest View of Subscription Version Activity selection to include all Subscription Versions, regardless of status, in order to capture activation, modification, and deletion transactions for Subscription Version data, but only include the latest instance of the TN in the Subscription Version Bulk Data Download file, for a given NPA-NXX, when a Subscription Version has more than one activity (e.g., addition, then modification) within the specified time range.

Req 6  Subscription Version Information Bulk Download File Creation – Time Range Fields

NPAC SMS shall use the Start Time Range entry field as an inclusive start range in Central Time (standard/daylight), and the End Time Range entry field as an inclusive ending range in Central Time (standard/daylight), for Subscription Version data that were broadcast during the specified Time Range.

Req 7  Subscription Version Information Bulk Download File Creation – TN Range Fields

NPAC SMS shall use the first TN Range entry field as an inclusive start range, and the second TN Range entry field as an inclusive ending range, for Subscription Version data.

Req 8  Subscription Version Information Bulk Download File Creation – Selection Criteria Combinations

NPAC SMS shall edit the selection criteria combination as shown in the table below:

                | Time Range | TN Range

--------------------------------------------------------------------------

Active/Disconnect Pending/

Partial Failure SVs Only      | Rejected  | Optional

Latest View of SV Activity     | Required  | Optional

Such that a combination of:

•    Active with a Time Range shall be rejected.

•    Latest View shall require a Time Range.

•    TN Range shall be optional for both Active and Latest View.

Req 9  Subscription Version Information Bulk Data Download – Subscription Version Results

NPAC SMS shall provide a bulk data download file, based on the selection criteria, that contains all Subscription Versions in the NPAC SMS.

Req 10  Subscription Version Information Bulk Data Download – Subscription Version Results Sort Order

NPAC SMS shall sort the Subscription Version Bulk Data Download file, in ascending order based on the value in the TN attribute.

Req 11  Subscription Version Information Bulk Data Download – Filters for Subscription Versions

NPAC SMS shall apply NPA-NXX Filters to Subscription Versions in the creation of bulk data download files.

Req 12  Subscription Version Information Bulk Data Download – FTP Sub-Directory

NPAC SMS shall automatically put the bulk data download file into the FTP sub-directory of the Service Provider, based on SPID, that requested the creation of the bulk data download file.

Req 13  Subscription Version Information Bulk Download File Creation – Time Range Fields and SV Data Model

NPAC SMS shall use the Start and End Time Range entry fields to include Subscription Version data, based on the Activation Broadcast Time Stamp, Modify Broadcast Time Stamp, and Disconnect Broadcast Time Stamp, in the NPAC’s Subscription Version Data Model, when generating the file for the Latest View of Subscription Version Activity selection.

Pure Backwards Compatible:  YES

This item is on hold until further experience is gained with download. This change is expected to help a service provider catch-up faster after an extend outage when the database becomes large.

It was indicated that this functionality is already available in the Lockheed Martin NPAC SMS implementation.  Delete Pending

This change order was re-opened for discussion during the Dec ’98 LNPAWG meeting.

Dec LNPAWG (Atlanta), verify start and end timestamps embedded in filename.  Update documentation to state Activation Broadcast Complete Timestamp is used for comparison.

Update:  The start and end timestamps are NOT embedded in the filename.

The proposal from the Natl N Pool Sub-Committee is to use the Last Modified Timestamp attribute in the SV, to determine whether or not an SV fits in the specified time range.

Jan LNPAWG (Atlanta), proposed changes were discussed.  CMA will include proposed changes in next version of the change management list.

Feb LNPAWG (San Ramon), updated multiple points for the change order (both file name and requirements).

NOTE:  The baseline for this change order is R2.  Therefore, when this change order gets merged into R3, need to change req 9 to reflect the EDR Flag, and filter out LNP Type of POOL  (ref. SV-521).

ACTION ITEM:  Jim will look at the broadcast timestamp for the SV Object, and how the NPAC Data Model attributes match up to the broadcast to the LSMSs.

CLOSED, Mar 99.  Activations are using the Activation Broadcast Timestamp in SV Data Model.

Mar LNPAWG (Denver), reviewed updated words.  Modifications will be reviewed in Apr.

Apr LNPAWG (DC), reviewed updates.  Move to Accepted List.

01/02/02 – Sometime during the R4.0 discussions this change order was removed from the R4.0 package.

Final Resolution:

Implemented

Related Release:

Implemented in FRS 3.2.0.

Status: Implemented