NANC 212

Activation Timestamp in M-GET Filter

Origination Date :04/21/1998

Originator:BellSouth

Description:

IIS flow 6.2.1 in step g states that the NPAC SMS to request data for an audit from the Local SMS can use a scoped filtered M-GET.  However, the step in the IIS flow does not state what attributes will be used in the filter.  There is also no indication in the GDMO that the activation timestamp and TN can be used in the M-GET filter.  The Lockheed Martin NPAC SMS uses the activation timestamp in the filter sent to the Local SMS.  It has been requested that the NPAC SMS not send the activation timestamp in the filter but rather used request criteria of activation timestamp (R8-9) to determine which TN’s to M-GET from the LSMS.

Final Resolution:

BellSouth has interpreted R8-9 differently form the current NPAC SMS implementation, and has requested that the NPAC SMS be changed to NOT send the Activation Timestamp in an M-GET filter.  This would require the NPAC SMS to determine the TNs, based on the activation timestamp, that should be requested to the LSMS.

Service Providers need to determine if this change would impact their current implementation of the LSMS.

Discussed at length during 7/8/98 telecon.  Current resolution is that numerous SPs propose that this change order NOT be implemented.  The reason is if the NPAC were changed to “pre-filter” the TNs in the M-GET to the LSMS, extraneous data in the LSMS would not get cleaned up.

For example, an LSMS contains an erroneous TN that is not in the NPAC.  If this was “pre-filtered” by the NPAC, this would NOT get identified (and not get deleted from the LSMS).

Moved to Pending Delete, per BST (Ron Steen), on 7/15/98.

Related Release:

N/A

Status: Closed