NANC 343
Doc Only Change Order for IIS: Exhibit 12 of IIS section 4.2.2 does not reflect all filtering operations currently supported by the NPAC SMS.
Origination Date :11/14/2001
Originator:LNPA-WG
Description:
“From Section 4.2.2:
The following table shows the CMISE primitive filtering support required of the Local SMS by the NPAC SMS for the subscriptionVersion object.
Exhibit 2 - CMISE Primitive Filtering Support for the Subscription Version Object
CMISE Primitives | Filter Supported | Notes |
M-ACTION | N | No filtering is applied to the actions for the subscriptionVersion object. |
M-GET | Y | TN Range with greaterOrEqual, lessOrEqual, equality must be supported for auditing. |
M-SET | Y | TN Range with greaterOrEqual, lessOrEqual, equality must be supported for Mass Update or TN range modify requests. |
M-DELETE | Y | TN Range with greaterOrEqual, lessOrEqual, equality will be supported for range disconnect or port to original requests. |
"
Modify text and table as follows to clarify exact functionality for TNs and for Number Pooling functionality:
From Section 4.2.2:
The following table shows the CMISE primitive filtering support required of the Local SMS by the NPAC SMS for the subscriptionVersion object
.
Exhibit 1 - CMISE Primitive Filtering Support for Local System Objects
CMISE Primitives | Filter Supported | Notes |
M-ACTION | N | No filtering is applied to the actions. |
M-GET | Y | TN Query
The fields used with greaterOrEqual and lessOrEqual filters are subscriptionTN and subscriptionActivationTimeStamp. The field used with equality is subscriptionTN. Filters supported contain either a greaterOrEqual and lessOrEqual filter, or equality filter, for subscriptionTN only or a more complex filter. The more complex filter uses two criteria for filtering. The first criteria used is greaterOrEqual and lessOrEqual filters with subscriptionTN. The second criteria uses greaterOrEqual and lessOrEqual filters for subscriptionActivationTimeStamp. Both criteria must be matched for the data being queried (logical and). The scope for the filters is level 1 only with a base managed object class of lnpSubscriptions. |
Number Pool Block Query with greaterOrEqual and lessOrEqual, and equality for EDR support. The fields used with greaterOrEqual and lessOrEqual filters are numberPoolBlockNPA-NXX-X and numberPoolBlockActivationTimeStamp. The field used with equality is numberPoolBlockNPA-NXX-X. Filters supported contain either a greaterOrEqual and lessOrEqual filter, or equality filter, for numberPoolBlockNPA-NXX-X only or a more complex filter. The more complex filter uses two criteria for filtering. The first criteria used is equality filter with numberPoolBlockNPA-NXX-X. The second criteria uses greaterOrEqual and lessOrEqual filters for numberPoolBlockActivationTimeStamp. Both criteria must be matched for the data being queried (logical and). The scope for the filters is level 1 only with a base managed object class of lnpSubscriptions. |
M-SET | Y | TN The field used with greaterOrEqual and lessOrEqual filters is subscriptionTN. The fields used with equality are subscriptionTN and subscriptionNewCurrentSP. Filters supported contain either a greaterOrEqual and lessOrEqual filter, or equality filter, for subscriptionTN only, or a more complex filter. In the case of Modification of TNs for non-EDR number pool block the filter is more complex and uses two criteria for modification. The first criteria uses the subscriptionNewCurrentSP field with equality. The second criteria uses lessOrEqual and greaterOrEqual for subscriptionTN. Both criteria must be matched for the data being set (logical and). Additionally, a filter for LNP Type equal to ‘pool’ may be used. The scope for the filters is level 1 only with a base managed object class of lnpSubscriptions. |
Number Pool Block Modify with greaterOrEqual and lessOrEqual, and equality for EDR support. The field used with greaterOrEqual and lessOrEqual is numberPoolBlockNPA-NXX-X. The field used with equality is numberPoolBlockNPA-NXX-X. The scope for the filters is level 1 only with a base managed object class of lnpSubscriptions. |
M-DELETE | Y | TN The field used with greaterOrEqual and lessOrEqual filters is subscriptionTN. The field used with equality is subscriptionTN. The scope for the filter is level 1 only with a base managed object class of lnpSubscriptions. In the case of Deletion of TNs for non-EDR number pool block the filter is more complex and uses two criteria for deletion. The first criteria uses the subscriptionNewCurrentSP field with equality. The second criteria uses lessOrEqual and greaterOrEqual for subscriptionTN. Both criteria must be matched for the data being set (logical and). Additionally, a filter for LNP Type equal to ‘pool’ may be used. |
NOTE: Exhibit 13 will be removed from the IIS.
GDMO Documentation
DOCUMENTATION changes should be made in the GDMO behavior for the following objects to accurately reflect scooping and filtering support required for the NPAC SMS to the LSMS:
- lnpSubscriptions
- subscriptionVersion
- numberPoolBlock
Further GDMO modifications will be necessary to reflect SOA and LSMS scoping and filtering support when sending requests to the NPAC SMS for the following objects:
- subscriptionVersionNPAC
- numberPoolBlockNPAC
Additional GDMO text will be added to reflect SOA and LSMS scoping and filtering support when sending requests to the NPAC SMS for other objects.
lnpSubscriptions:
The lnpSubscriptionsDefinition BEHAVIOUR should be modified as follows:
lnpSubscriptionsDefinition BEHAVIOUR
DEFINED AS !
Local SMS and NPAC SMS Managed Object for the SOA to NPAC SMS and the Local SMS to NPAC SMS interface.
The lnpSubscriptions class is the managed object that is used as the container object for the subscription version objects and numberPoolBlock objects on the NPAC SMS and the Local SMS.
Local SMS interfaces must be able to support scoped/filtered
and filtered requests with a level 1 scope and a base managed object class of lnpSubscription.M-SETs and M-DELETEs with a TN range as the primary filter.
Specific filter criteria support is defined in the behavior for the subscriptionVersion and numberPoolBlock managed objects.
!;
subscriptionVersion:
The subscriptionVersionBehaviour BEHAVIOUR should be modified as follows:
subscriptionVersionBehavior BEHAVIOUR
DEFINED AS !
.
.
.
The Local SMS can not modify any of the subscription version data locally unless changes were downloaded via a download request.
The Local SMS must be able to support scoped and filtered requests with a level 1 scope and a base managed object class of lnpSubscription for subscription version (M-GET, M-SET, and M-DELETE) requests. with a filter for equality and ordering on the subscriptionTN from the NPAC SMS
.
Filtering Support for M-GET:
TN Query with greaterOrEqual and lessOrEqual, and equality must be supported for auditing.
The fields used with greaterOrEqual and lessOrEqual filters are subscriptionTN and subscriptionActivationTimeStamp.
The field used with equality is subscriptionTN.
Filters supported contain either a greaterOrEqual and lessOrEqual filter, or equality filter, for subscriptionTN only or a more complex filter.
The more complex filter uses two criteria for filtering. The first criteria used is greaterOrEqual and lessOrEqual filters with subscriptionTN. The second criteria uses greaterOrEqual and lessOrEqual filters for subscriptionActivationTimeStamp. Both criteria must be matched for the data being queried (logical and).
Filtering Support for M-SET:
TN Modify with greaterOrEqual and lessOrEqual, and equality must be supported for Mass Update or TN modify requests.
The field used with greaterOrEqual and lessOrEqual filters is subscriptionTN.
The fields used with equality are subscriptionTN and subscriptionNewCurrentSP.
Filters supported contain either a greaterOrEqual and lessOrEqual filter, or equality filter, for subscriptionTN only, or a more complex filter.
In the case of Modification of TNs for non-EDR number pool block the filter is more complex and uses two criteria for modification. The first criteria uses the subscriptionNewCurrentSP field with equality. The second criteria uses greaterOrEqual and lessOrEqual for subscriptionTN. Both criteria must be matched for the data being set (logical and). Additionally, a filter for LNP Type equal to ‘pool’ may be used.
The scope for the filters is level 1 only with a base managed object class of lnpSubscriptions.
Filtering Support for M-DELETE:
TN Delete with greaterOrEqual and lessOrEqual, and equality will be supported.
The field used with greaterOrEqual and lessOrEqual filters is subscriptionTN.
The field used with equality is subscriptionTN.
The scope for the filters is level 1 only with a base managed object class of lnpSubscriptions.
In the case of Deletion of TNs for non-EDR number pool block the filter is more complex and uses two criteria for deletion. The first criteria uses the subscriptionNewCurrentSP field with equality. The second criteria uses lessOrEqual and greaterOrEqual for subscriptionTN. Both criteria must be matched for the data being set (logical and). Additionally, a filter for LNP Type equal to ‘pool’ may be used.
!;
numberPoolBlock:
The numberPoolBlock-Behaviour BEHAVIOUR should be modified as follows:
numberPoolBlock-Behavior BEHAVIOUR
DEFINED AS !
.
.
.
The Local SMS can not modify any of the number pool block data locally unless changes were downloaded via a download request.
The Local SMS must support scoped and filtered requests with a level 1 scope and a base managed object class of lnpSubscriptions for numberPoolBlock M-GET and M-SET requests.equality and ordering on the numberPoolBlockNPA-NXX-X attribute in a scoped and filtered request for mass updates and audits.
Filtering Support for M-GET:
Number Pool Block Query with greaterOrEqual and lessOrEqual, and equality for EDR support.
The fields used with greaterOrEqual and lessOrEqual filters are numberPoolBlockNPA-NXX-X and numberPoolBlockActivationTimeStamp.
The field used with equality is numberPoolBlockNPA-NXX-X.
Filters supported contain either a greaterOrEqual and lessOrEqual filter, or equality filter, for numberPoolBlockNPA-NXX-X only or a more complex filter.
The more complex filter uses two criteria for filtering. The first criteria used is equality filter with numberPoolBlockNPA-NXX-X. The second criteria uses greaterOrEqual and lessOrEqual filters for numberPoolBlockActivationTimeStamp. Both criteria must be matched for the data being queried (logical and).
The scope for the filters is level 1 only with a base managed object class of lnpSubscriptions.
numberPoolBlock:
The numberPoolBlock-Behaviour BEHAVIOUR should be modified as follows:
numberPoolBlock-Behavior BEHAVIOUR
DEFINED AS !
.
.
.
The Local SMS can not modify any of the number pool block data locally unless changes were downloaded via a download request.
The Local SMS must support scoped and filtered requests with a level 1 scope and a base managed object class of lnpSubscriptions for numberPoolBlock M-GET and M-SET requests. equality and ordering on the numberPoolBlockNPA-NXX-X attribute in a scoped and filtered request for mass updates and audits.
Filtering Support for M-GET:
Number Pool Block Query with greaterOrEqual and lessOrEqual, and equality for EDR support.
The fields used with greaterOrEqual and lessOrEqual filters are numberPoolBlockNPA-NXX-X and numberPoolBlockActivationTimeStamp.
The field used with equality is numberPoolBlockNPA-NXX-X.
Filters supported contain either a greaterOrEqual and lessOrEqual filter, or equality filter, for numberPoolBlockNPA-NXX-X only or a more complex filter.
The more complex filter uses two criteria for filtering. The first criteria used is equality filter with numberPoolBlockNPA-NXX-X. The second criteria uses greaterOrEqual and lessOrEqual filters for numberPoolBlockActivationTimeStamp. Both criteria must be matched for the data being queried (logical and).
The scope for the filters is level 1 only with a base managed object class of lnpSubscriptions.
!;
Implemented in IIS 3.3.0a, and GDMO 3.3.0.
Final Resolution:
Incorporate into next release of IIS.
12/12/01 – Reviewed during December LNPA WG meeting. Needs more revisions. Will be reviewed again during January 2002 meeting.
01/09/02 – Reviewed revisions. More revisions required. The new revisions are highlighted in yellow. Will review again during the February 2002 meeting.
Nov ‘02 LNPAWG – Reviewed at meeting, move to accepted. Additional text has been added to make consistent with the numberPoolBlockNPAC MANAGED OBJECT CLASS in the GDMO, related to LNP Type.
Implemented in IIS 3.3.0a, and GDMO 3.3.0.
Related Release:
Implemented in IIS 3.3.0a, and GDMO 3.3.0.
Status: Implemented