------------------------------------------------------- -- -- Source Control Ident String = "@(#) npac/cmip/libcmip/src/lnp.mo : %full_filespec: lnp.mo~7:gdmo:1 % %version: 7 % %date_modified: Mon Aug 19 16:24:42 2002 %" -- ------------------------------------------------------- -- (c) 1996 NeuStar, Inc. The Work is subject to the terms of the GNU -- General Public License (the "GPL"), a copy of which may be found at -- ftp://prep.ai.mit.edu/pub/gnu/GPL. Any use of this Work is subject to -- the terms of the GPL. The "Work" covered by the GPL by operation of -- this notice and license is this document and any and all modifications -- to or derivatives of this document. Where the words "Program," -- "software," "source code," "code," or "files" are used in the GPL, -- users understand and agree that the "Work" as defined here is substituted -- for purposes of this notice and license. -- -- May 27, 2005 -- GDMO for NPAC SMS Release 3.3.0. -- Based upon IIS v3.3.0. -- Updated to include change orders: -- ILL 130, NANC 151, NANC 227/254, NANC 285, -- NANC 299, NANC 300, NANC 346, NANC 351, -- NANC 352, NANC 357, NANC 375, NANC 383, -- NANC 388, NANC 394. -- Documentation-only change orders: -- NANC 243, NANC 360, NANC 361, NANC 365, -- NANC 371, NANC 373, NANC 374, NANC 376. -- -- Object Definitions -- -- 1.0 LNP Audits Managed Object lnpAudits MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY lnpAuditsPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 1}; lnpAuditsPkg PACKAGE BEHAVIOUR lnpAuditsDefinition, lnpAuditsBehavior; ATTRIBUTES lnpAuditsName GET; ; lnpAuditsDefinition BEHAVIOUR DEFINED AS ! The lnpAudits class is the managed object that is used as the container object for the subscriptionAudit objects on the NPAC SMS. This object has been created for scoping efficiency. !; lnpAuditsBehavior BEHAVIOUR DEFINED AS ! NPAC SMS Managed Object for the SOA to NPAC SMS interface. The service provider SOA can M-GET any lnpAudits object on the NPAC SMS. (SOA Management Association Function). The Local SMS can not M-GET any lnpAudits object on the NPAC SMS. The lnpAuditsName attribute is read only and can not be changed via the Local SMS or SOA Interface once the object has been created. The value of lnpAuditsName will always be "lnpAudits". Only one of these objects will exist per agent and it will only be created at startup of the CMIP agent software on the NPAC SMS. !; -- 2.0 LNP Local SMS Managed Object Class lnpLocalSMS MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY lnpLocalSMS-Pkg; CONDITIONAL PACKAGES applicationLevelHeartBeatPkg PRESENT IF !the object is instantiated on the Local SMS!, swimProcessing-RecoveryResultsPkg PRESENT IF !the Local SMS supports SWIM Recovery!; REGISTERED AS {LNP-OIDS.lnp-objectClass 2}; lnpLocalSMS-Pkg PACKAGE BEHAVIOUR lnpLocalSMS-Definition, lnpLocalSMS-Behavior; ATTRIBUTES lnpLocal-SMS-Name GET; ; lnpLocalSMS-Definition BEHAVIOUR DEFINED AS ! The lnpLocalSMS class is the managed object that is used as the container object for all Local SMS data in the NPAC SMS to Local SMS Interface. !; lnpLocalSMS-Behavior BEHAVIOUR DEFINED AS ! Local SMS Managed Object. The NPAC SMS can M-GET any lnpLocalSMS object (Data Download Association Function). The lnp-LocalSMS-Name attribute is read only and can not be changed via the Local SMS Interface once the object has been created. The value of lnpLocal-SMS-Name will always be a unique identifier for the Local SMS for the NPAC SMS to Local SMS Interface. Only one of these objects will exist and it will only be created at startup of the CMIP agent software on the Local SMS. !; -- 3.0 LNP Log Record for the Subscription Audit Local SMS Discrepancy Report lnpLogAudit-DiscrepancyRptRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogAudit-DiscrepancyRptPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 3}; lnpLogAudit-DiscrepancyRptPkg PACKAGE BEHAVIOUR lnpLogAudit-DiscrepancyRptDefinition, lnpLogAudit-DiscrepancyRptBehavior; ATTRIBUTES auditDiscrepancyTn GET, auditDiscrepancyVersionId GET, auditDiscrepancyLSMS-SP-Id GET, auditDiscrepancyFailureReason GET, accessControl GET; ; lnpLogAudit-DiscrepancyRptDefinition BEHAVIOUR DEFINED AS ! The lnpLogAudit-DiscrepancyRptRecord class is the managed object that is used to create log records for the subscriptionAudit-DiscrepancyRpt Notification. !; lnpLogAudit-DiscrepancyRptBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionAudit-DiscrepancyRpt Notification. !; -- 4.0 LNP Log Record for the Subscription Audit Results lnpLogAuditResultsRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogAuditResultsPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 4}; lnpLogAuditResultsPkg PACKAGE BEHAVIOUR lnpLogAuditResultsDefinition, lnpLogAuditResultsBehavior; ATTRIBUTES auditResultStatus GET, auditResultFailed-SP-List GET, auditResultNumberDiscrepancies GET, auditResultCompletionTime GET, accessControl GET; ; lnpLogAuditResultsDefinition BEHAVIOUR DEFINED AS ! The lnpLogAuditResultsRecord class is the managed object that is used to create log records for the subscriptionAuditResults Notification. !; lnpLogAuditResultsBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionAuditResults Notification. !; -- 5.0 LNP Log Record for the Subscription Version Cancellation -- Acknowledge Request Notification lnpLogCancellationAcknowledgeRequestRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogCancellationAcknowledgeRequestPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 5}; lnpLogCancellationAcknowledgeRequestPkg PACKAGE BEHAVIOUR lnpLogCancellationAcknowledgeRequestDefinition, lnpLogCancellationAcknowledgeRequestBehavior; ATTRIBUTES subscriptionTN GET, subscriptionVersionId GET, accessControl GET; ; lnpLogCancellationAcknowledgeRequestDefinition BEHAVIOUR DEFINED AS ! The lnpLogCancellationAcknowledgeRequestRecord class is the managed object that is used to create log records for the subscriptionVersionCancellationAcknowledgeRequest Notification. !; lnpLogCancellationAcknowledgeRequestBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionCancellationAcknowledgeRequest Notification. !; -- 7.0 LNP Log Record for the Subscription Version New SP Create Request -- Notification lnpLogNewSP-CreateRequestRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogNewSP-CreateRequestPkg; CONDITIONAL PACKAGES subscriptionTimerTypePkg PRESENT IF !present if the New SP SOA supports timer type!, subscriptionBusinessTypePkg PRESENT IF !present if the New SP SOA supports business type!; REGISTERED AS {LNP-OIDS.lnp-objectClass 7}; lnpLogNewSP-CreateRequestPkg PACKAGE BEHAVIOUR lnpLogNewSP-CreateRequestDefinition, lnpLogNewSP-CreateRequestBehavior; ATTRIBUTES subscriptionTN GET, subscriptionVersionId GET, subscriptionOldSP GET, subscriptionOldSP-DueDate GET, subscriptionOldSP-Authorization GET, subscriptionOldSP-AuthorizationTimeStamp GET, subscriptionStatusChangeCauseCode GET, accessControl GET; ; lnpLogNewSP-CreateRequestDefinition BEHAVIOUR DEFINED AS ! The lnpLogNewSP-CreateRequestRecord class is the managed object that is used to create log records for the subscriptionVersionNewSP-CreateRequest Notification. !; lnpLogNewSP-CreateRequestBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionNewSP-CreateRequest Notification. !; -- 8.0 LNP Log Record for the Subscription Version Old SP Concurrence Request -- Notification lnpLogOldSP-ConcurrenceRequestRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogOldSP-ConcurrenceRequestPkg; CONDITIONAL PACKAGES subscriptionTimerTypePkg PRESENT IF !present if the Old SP SOA supports timer type!, subscriptionBusinessTypePkg PRESENT IF !present if the Old SP SOA supports business type!; REGISTERED AS {LNP-OIDS.lnp-objectClass 8}; lnpLogOldSP-ConcurrenceRequestPkg PACKAGE BEHAVIOUR lnpLogOldSP-ConcurrenceRequestDefinition, lnpLogOldSP-ConcurrenceRequestBehavior; ATTRIBUTES subscriptionTN GET, subscriptionVersionId GET, subscriptionNewCurrentSP GET, subscriptionNewSP-DueDate GET, subscriptionNewSP-CreationTimeStamp GET, accessControl GET; ; lnpLogOldSP-ConcurrenceRequestDefinition BEHAVIOUR DEFINED AS ! The lnpLogOldSP-ConcurrenceRequestRecord class is the managed object that is used to create log records for the subscriptionVersionOldSP-ConcurrenceRequest Notification. !; lnpLogOldSP-ConcurrenceRequestBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionOldSP-ConcurrenceRequest Notification. !; -- 9.0 LNP Log Record for the NPAC SMS Operational Information Notification lnpLogOperational-InformationRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogOperational-InformationPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 9}; lnpLogOperational-InformationPkg PACKAGE BEHAVIOUR lnpLogOperational-InformationDefinition, lnpLogOperational-InformationBehavior; ATTRIBUTES downTime GET, npacContactNumber GET, additionalDownTimeInformation GET, accessControl GET; ; lnpLogOperational-InformationDefinition BEHAVIOUR DEFINED AS ! The lnpLogOperational-InformationRecord class is the managed object that is used to create log records for the lnpNPAC-SMS-Operational-Information Notification. !; lnpLogOperational-InformationBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the lnpNPAC-SMS-Operational-Information Notification. !; -- 10.0 LNP Log Record for the Subscription Version Status Attribute Value -- Change Notification lnpLogStatusAttributeValueChangeRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogStatusAttributeValueChangePkg; CONDITIONAL PACKAGES subscriptionVersionAttributeValueChangeFailed-SP-ListPkg PRESENT IF !the version broadcast failed!, subscriptionStatusChangeCauseCodePkg PRESENT IF !the version status is set to conflict by the old service provider!, subscriptionVersionTNPkg PRESENT IF !the subscription version TN is supported by the service provider in SAVC notifications!; REGISTERED AS {LNP-OIDS.lnp-objectClass 10}; lnpLogStatusAttributeValueChangePkg PACKAGE BEHAVIOUR lnpLogStatusAttributeValueChangeDefinition, lnpLogStatusAttributeValueChangeBehavior; ATTRIBUTES subscriptionVersionAttributeValueChangeInfo GET, accessControl GET; ; lnpLogStatusAttributeValueChangeDefinition BEHAVIOUR DEFINED AS ! The lnpLogStatusAttributeValueChangeRecord class is the managed object that is used to create log records for the subscriptionVersionStatusAttributeValueChange Notification. !; lnpLogStatusAttributeValueChangeBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionStatusAttributeValueChange Notification. !; -- 11.0 LNP Network Managed Object Class lnpNetwork MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY lnpNetworkPkg; CONDITIONAL PACKAGES lnpDownloadPkg PRESENT IF !the object is instantiated on the NPAC SMS!; REGISTERED AS {LNP-OIDS.lnp-objectClass 11}; lnpNetworkPkg PACKAGE BEHAVIOUR lnpNetworkDefinition, lnpNetworkBehavior; ATTRIBUTES lnpNetworkName GET; ; lnpNetworkDefinition BEHAVIOUR DEFINED AS ! The lnpNetwork class is the managed object that is used as the container object for the serviceProvNetwork objects. This object has been created primarily for scoping efficiency. The lnpDownloadPkg will only be used for lnpNetwork object instantiated on the NPAC SMS (Data Download Association Function). This package is used for initiating from the Local SMS or SOA downloading of serviceProvNetwork, serviceProvNPA-NXX, serviceProvNPA-NXX-X and serviceProvLRN object creation, modification, or deletion to the Local SMS or SOA from the NPAC SMS. !; lnpNetworkBehavior BEHAVIOUR DEFINED AS ! Local SMS, SOA, and NPAC SMS Managed Object used for the Local SMS to NPAC SMS and the SOA to NPAC SMS interfaces. The Local SMS, SOA, and the NPAC SMS can M-GET any lnpNetwork object (Data Download Association Function). The lnpNetworkName attribute is read only and can not be changed via the NPAC SMS to Local SMS or SOA to NPAC SMS Interfaces once the object has been created. The value of lnpNetworkName will always be "lnpNetwork". Only one of these objects will exist and it will only be created at startup of the CMIP agent software on the NPAC SMS the Local SMS or SOA. The lnpDownloadPkg will only be used for an lnpNetwork object instantiated on the NPAC SMS. This package is used for initiating downloading of NPA-NXX and LRN object creation or deletion to the Local SMS (Data Download Association Function). Also, the package is used for initiating downloading of NPA-NXX-X object creation, modification, or deletion to the Local SMS (Data Download Association Function). !; -- 12.0 LNP NPAC SMS Managed Object Class lnpNPAC-SMS MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY lnpNPAC-SMS-Pkg, lnpRecoveryCompletePkg, lnpNotificationRecoveryPkg; CONDITIONAL PACKAGES applicationLevelHeartBeatPkg PRESENT IF !the object is instantiated on the NPAC SMS!; REGISTERED AS {LNP-OIDS.lnp-objectClass 12}; lnpNPAC-SMS-Pkg PACKAGE BEHAVIOUR lnpNPAC-SMS-Definition, lnpNPAC-SMS-Behavior; ATTRIBUTES lnpNPAC-SMS-Name GET; NOTIFICATIONS lnpNPAC-SMS-Operational-Information, subscriptionVersionNewNPA-NXX; ; lnpNPAC-SMS-Definition BEHAVIOUR DEFINED AS ! The lnpNPAC-SMS class is the managed object that is used as the container object for all NPAC SMS objects in the NPAC SMS to Local SMS Interface and the SOA to NPAC SMS interface. !; lnpNPAC-SMS-Behavior BEHAVIOUR DEFINED AS ! NPAC SMS Managed Object for the SOA to NPAC SMS and the Local SMS to NPAC SMS interface. A Local SMS and SOA can M-GET any lnpNPAC-SMS object. The lnpNPAC-SMS-Name attribute is read only and can not be changed via either Interface once the object has been created. The lnpRecoveryComplete-Pkg is used to indicate the recovery mode for the Local SMS or SOA is complete and to send all updates made since the recovery mode began. (Data Download Functional Group). The lnpNotificationRecoveryPkg is used to recover notifications in recovery mode by the Local SMS or SOA. (Data Download Functional Group). Only one of these objects will exist and it will only be created at startup of the CMIP agent software on the NPAC SMS. The lnpNPAC-SMS-Operational-Information will be used to notify service provider SOA and Local SMS systems of planned outages. The subscriptionVersionNewNPA-NXX is used to support number pooling. A SOA or LSMS may implement an Application Level Heartbeat functionality. With this functionality the NPAC SMS will send a periodic Heartbeat message when a quiet period interval between the SOA/LSMS and the NPAC SMS exceeds the tunable value. If a SOA/LSMS fails to respond to the Heartbeat message within a timeout period, the association will be aborted by the NPAC SMS. !; -- 13.0 LNP Service Providers Managed Object Class lnpServiceProvs MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY lnpServiceProvsPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 13}; lnpServiceProvsPkg PACKAGE BEHAVIOUR lnpServiceProvsDefinition, lnpServiceProvsBehavior; ATTRIBUTES lnpServiceProvsName GET; ; lnpServiceProvsDefinition BEHAVIOUR DEFINED AS ! The lnpServiceProvs class is the managed object that is used as the container object for the serviceProv objects on the NPAC SMS. This object has been created for scoping efficiency. !; lnpServiceProvsBehavior BEHAVIOUR DEFINED AS ! NPAC SMS Managed Object used for the Local SMS to NPAC SMS and SOA to NPAC SMS interfaces. A Local SMS and service provider SOA can M-GET any lnpServiceProvs object (Network Data Association Function). The lnpServiceProvsName attribute is read only and can not be changed via the Local SMS Interface once the object has been created. The value of lnpServiceProvsName will always be "lnpServiceProvs". Only one of these objects will exist and it will only be created at startup of the CMIP agent software on the NPAC SMS. !; -- 14.0 LNP Subscriptions Managed Object Class lnpSubscriptions MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY lnpSubscriptionsPkg, subscriptionVersionLocalSMS-CreatePkg; CONDITIONAL PACKAGES lnpDownloadPkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionOldSP-CreatePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionNewSP-CreatePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionDisconnectPkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionModifyPkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionActivatePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionCancelPkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionOldSP-CancellationPkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionNewSP-CancellationPkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRemoveFromConflictPkg PRESENT IF !the object is instantiated on the NPAC SMS!, numberPoolBlock-CreatePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRangeStatusAttributeValueChangePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRangeAttributeValueChangePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRangeObjectCreationPkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRangeDonorSP-CustomerDisconnectDatePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRangeCancellationAcknowledgePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRangeNewSP-CreateRequestPkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRangeOldSP-ConcurrenceRequestPkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRangeOldSPFinalConcurrenceWindowExpirationPkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRangeNewSP-FinalCreateWindowExpirationPkg PRESENT IF !the object is instantiated on the NPAC SMS!, -- -- Packages for the sister ACTIONs with error codes -- subscriptionVersionActivateWithErrorCodePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionCancelWithErrorCodePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionNewSP-CancellationWithErrorCodePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionRemoveFromConflictWithErrorCodePkg PRESENT IF !the object is instantiated on the NPAC SMS!, subscriptionVersionOldSP-CancellationWithErrorCodePkg PRESENT IF !the object is instantiated on the NPAC SMS!; REGISTERED AS {LNP-OIDS.lnp-objectClass 14}; lnpSubscriptionsPkg PACKAGE BEHAVIOUR lnpSubscriptionsDefinition, lnpSubscriptionsBehavior; ATTRIBUTES lnpSubscriptionsName GET; NOTIFICATIONS subscriptionVersionLocalSMS-ActionResults; ; 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 scope and filtered requests with a level 1 scope and a base managed object class of lnpSubscriptions. Specific filter criteria support is defined in the behavior for the subscriptionVersion and numberPoolBlock managed objects. !; lnpSubscriptionsBehavior BEHAVIOUR DEFINED AS ! Local SMS and NPAC SMS Managed Object The Local SMS (Data Download Association Function) and the service provider SOA (SOA Management Association Function) can M-GET any lnpSubscriptions object. The lnpSubscriptionsName attribute is read only and can not be changed via the Local SMS Interface once the object has been created. The value of lnpSubscriptionsName will always be "lnpSubscriptions". Only one of these objects will exist and it will only be created at startup of the CMIP agent software on the NPAC SMS or the Local SMS. The lnpDownloadPkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for initiating downloading of subscriptionVersions and numberPoolBlock object creation, deletion, or modifications to the Local SMS (Data Download Association Function). The subscriptionVersionOldSP-CreatePkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for creation of subscription versions for porting TNs by the old service provider. The subscriptionVersionNewSP-CreatePkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for creation of subscription versions for porting TNs by the new service provider. The subscriptionVersionDisconnectPkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for disconnection of a ported TN by the current service provider. The subscriptionVersionModifyPkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for modification of a ported TN by a service provider. The subscriptionVersionActivatePkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for activation of a ported TN by a new service provider. The subscriptionVersionCancelPkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for cancellation of a ported TN by a service provider. The subscriptionVersionOldSP-CancellationPkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for acknowledgment of subscription versions with status values of cancel-pending. This action is used by the old service provider SOA. The subscriptionVersionNewSP-CancellationPkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for acknowledgment of subscription versions with status values of cancel-pending. This action is used by the new service provider SOA. The subscriptionVersionRemoveFromConflictPkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for setting the status of subscription versions with status values of conflict to pending. This action is used by either the new or old service provider SOA. The numberPoolBlock-CreatePkg will only be used for a lnpSubscriptions object instantiated on the NPAC SMS. This package is used for creation of number pool blocks. The SOA receives subscriptionVersionRangeStatusAttributeValueChange notifications if their Service Provider TN Range Notification Indicator is set to TRUE on the NPAC SMS. The subscriptionVersionRangeStatusAttributeValueChangePkg is used to send the subscriptionVersionRangeStatusAttributeValueChange notification. When this package is sent, it will include one set of information for the TN range. If the SVIDs are sequential for the TNs then an SVID range will be included. If the SVIDs are not sequential then a paired list of SVIDs and TNs will be sent. If the feature data does not apply to all TNs in the original range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN Range, and will be sent in separate messages. The SOA receives subscriptionVersionRangeAttributeValueChange notifications if their Service Provider TN Range Notification Indicator is set to TRUE on the NPAC SMS. The subscriptionVersionRangeAttributeValueChangePkg is used to send the subscriptionVersionRangeAttributeValueChange notification. When this package is sent, it will include one set of information for the TN range. If the SVIDs are sequential for the TNs then an SVID range will be included. If the SVIDs are not sequential then a paired list of SVIDs and TNs will be sent. If the feature data does not apply to all TNs in the original range, notifications will be broken up into smaller TN Range notifications such that the feature data applies to all TNs in the smaller TN Range, and will be sent in separate messages. The SOA receives subscriptionVersionRangeObjectCreation notifications if their Service Provider TN Range Notification Indicator is set to TRUE on the NPAC SMS. The subscriptionVersionRangeObjectCreationPkg is used to send the subscriptionVersionRangeObjectCreation notification. When this package is sent, it will include one set of information for the TN range, plus a paired list of TN/Subscription Version ID combinations or a range of TNs and Subscription Version Ids if the Subscription Version Ids are sequential. If the feature data does not apply to all TNs in the range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN Range, and will be sent in separate messages. The ObjectInfo field will contain the same data as the current object creation notifications sent to the old and new service provider. The TN and SVID fields that are sent in the single object creation notification will contain the TN and subscription version id for the first TN in the range or list. The SOA receives subscriptionVersionRangeDonorSP-CustomerDisconnectDate notifications if their Service Provider TN Range Notification Indicator is set to TRUE on the NPAC SMS. The subscriptionVersionRangeDonorSP-CustomerDisconnectDatePkg is used to send the subscriptionVersionRangeDonorSP-CustomerDisconnectDate notification. When this package is sent, it will include one set of information for the TN range, plus a paired list of TN/Subscription Version ID combinations or a range of TNs and Subscription Version Ids if the Subscription Version Ids are sequential. If the feature data does not apply to all TNs in the range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN Range, and will be sent in separate messages. The SOA receives subscriptionVersionRangeCancellationAcknowledge notifications if their Service Provider TN Range Notification Indicator is set to TRUE on the NPAC SMS. The subscriptionVersionRangeCancellationAcknowledgePkg is used to send the subscriptionVersionRangeCancellationAcknowledge notification. When this package is sent, it will include one set of information for the TN range, plus a paired list of TN/Subscription Version ID combinations or a range of TNs and Subscription Version Ids if the Subscription Version Ids are sequential. If the feature data does not apply to all TNs in the range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN Range, and will be sent in separate messages. The SOA receives subscriptionVersionRangeNewSP-CreateRequest notifications if their Service Provider TN Range Notification Indicator is set to TRUE on the NPAC SMS. The subscriptionVersionRangeNewSP-CreateRequestPkg is used to send the subscriptionVersionRangeNewSP-CreateRequest notification. When this package is sent, it will include one set of information for the TN range, plus a paired list of TN/Subscription Version ID combinations or a range of TNs and Subscription Version Ids if the Subscription Version Ids are sequential. If the feature data does not apply to all TNs in the range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN Range, and will be sent in separate messages. The SOA receives subscriptionVersionRangeOldSP-ConcurrenceRequest notifications if their Service Provider TN Range Notification Indicator is set to TRUE on the NPAC SMS. The subscriptionVersionRangeOldSP-ConcurrenceRequestPkg is used to send the subscriptionVersionRangeOldSP-ConcurrenceRequest notification. When this package is sent, it will include one set of information for the TN range, plus a paired list of TN/Subscription Version ID combinations or a range of TNs and Subscription Version Ids if the Subscription Version Ids are sequential. If the feature data does not apply to all TNs in the range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN Range, and will be sent in separate messages. The SOA receives subscriptionVersionRangeOldSPFinalConcurrenceWindowExpiration notifications if their Service Provider TN Range Notification Indicator is set to TRUE on the NPAC SMS. The SubscriptionVersionRangeOldSPFinalConcurrenceWindow-ExpirationPkg is used to send the subscriptionVersionRangeOldSPFinalConcurrenceWindowExpiration notification. When this package is sent, it will include one set of information for the TN range, plus a paired list of TN/Subscription Version ID combinations or a range of TNs and Subscription Version Ids if the Subscription Version Ids are sequential. If the feature data does not apply to all TNs in the range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN Range, and will be sent in separate messages. The SOA receives subscriptionVersionRangeNewSP-FinalCreateWindowExpiration notifications if their Service Provider TN Range Notification Indicator is set to TRUE on the NPAC SMS. The SubscriptionVersionRangeNewSP-FinalCreateWindow-ExpirationPkg is used to send the subscriptionVersionRangeNewSP-FinalCreateWindowExpiration notification. When this package is sent, it will include one set of information for the TN range, plus a paired list of TN/Subscription Version ID combinations or a range of TNs and Subscription Version Ids if the Subscription Version Ids are sequential. If the feature data does not apply to all TNs in the range, notifications will be broken up into smaller TN Range Notifications such that the feature data applies to all TNs in the smaller TN Range, and will be sent in separate messages. Range notifications are formatted according to the Service Provider Profile. If a Service Provider is an associated Service Provider to a primary Service Provider then the primary Service Provider SOA must be able to accept the notifications in the format indicated in the associated Service Provider Profile. !; -- 15.0 LNP Service Provider Managed Object Class serviceProv MANAGED OBJECT CLASS DERIVED FROM serviceProvNetwork; CHARACTERIZED BY serviceProvPkg; CONDITIONAL PACKAGES serviceProvBillingAddressPkg PRESENT IF !the service provider has billing address and contact information!, serviceProvSOA-AddressPkg PRESENT IF !the service provider has SOA address and contact information!, serviceProvLSMS-AddressPkg PRESENT IF !the service provider has LSMS address and contact information!, serviceProvWebAddressPkg PRESENT IF !the service provider has Web address and contact information!, serviceProvNetAddressPkg PRESENT IF !the service provider has network and communication facilities address and contact information!, serviceProvConflictAddressPkg PRESENT IF !the service provider has conflict resolution interface address and contact information!, serviceProvOperationsAddressPkg PRESENT IF !the service provider has operations address and contact information!, serviceProvRepairCenterInfoPkg PRESENT IF !the service provider has repair contact information!, serviceProvSecurityAddressPkg PRESENT IF !the service provider has security contact information!, serviceProvUserAdminAddressPkg PRESENT IF !the service provider has user administration interface address and contact information!; REGISTERED AS {LNP-OIDS.lnp-objectClass 15}; serviceProvPkg PACKAGE BEHAVIOUR serviceProvDefinition, serviceProvBehavior; ATTRIBUTES npacCustomerAllowableFunctions GET, serviceProvAddress GET-REPLACE, serviceProvSysLinkInfo GET-REPLACE; ; serviceProvDefinition BEHAVIOUR DEFINED AS ! The serviceProv class is the managed object used on the NPAC SMS to contain the data related to each LNP service provider. !; serviceProvBehavior BEHAVIOUR DEFINED AS ! NPAC SMS Managed Object used for the Local SMS to NPAC SMS interface. A Local SMS and service provider SOA can M-GET their serviceProv object (Network Data Association Function). Attempts to read any unauthorized service provider information will be rejected. All attributes in this object, except serviceProvID and npacCustomerAllowableFunctions can be M-SET by the Local SMS and SOA Interfaces once the object has been created on the NPAC SMS. If any of the contact data is modified, ALL contact information must be sent. Any missing contact data is presumed to be a deletion if the data currently exists on the NPAC SMS. Note: this behaviour is not following current CMIP standards. !; -- 16.0 LNP Service Provider LRN Managed Object Class serviceProvLRN MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY serviceProvLRN-Pkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 16}; serviceProvLRN-Pkg PACKAGE BEHAVIOUR serviceProvLRN-Definition, serviceProvLRN-Behavior; ATTRIBUTES serviceProvLRN-ID GET, serviceProvLRN-Value GET, serviceProvDownloadReason GET, serviceProvLRN-CreationTimeStamp GET; ; serviceProvLRN-Definition BEHAVIOUR DEFINED AS ! The serviceProvLRN class is the managed object used to identify Service Provider LRN values open for porting. !; serviceProvLRN-Behavior BEHAVIOUR DEFINED AS ! Local SMS and NPAC SMS Managed Object used for the Local SMS to NPAC SMS and SOA to NPAC SMS interfaces. All attributes are read only. Once created, the serviceProvLRN object can only be deleted via the Local SMS or SOA interface. The serviceProvLRN-ID is specified by the NPAC SMS. The serviceProvLRN-CreationTimeStamp will reflect the current system date and time when the object is created. NPAC SMS can M-GET, M-DELETE and M-CREATE any serviceProvLRN object on the Local SMS or SOA (Network Data Functional Unit). The Local SMS or SOA only creates local copies of serviceProvLRN objects after receiving the objects from an NPAC SMS create request, reading them from the NPAC SMS for initial instantiation, or from a download request. A Local SMS or SOA can M-GET any serviceProvLRN object (Network Data Functional Unit). The Local SMS or SOA can M-DELETE and M-CREATE any serviceProvLRN object on the NPAC SMS for the service provider id specified in the access control (Network Data Functional Unit). Attempts to take actions on unauthorized service provider objects will be rejected. The creation or deletion of a serviceProvLRN object will be distributed to all Local SMSs and SOAs. The serviceProvLRN-Value attributes on the NPAC SMS can not be modified by the Local SMS or SOA. The service provider will have to add a new object and delete the old one to modify the data. !; -- 17.0 LNP Service Provider Network Managed Object Class serviceProvNetwork MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY serviceProvNetworkPkg; CONDITIONAL PACKAGES serviceProvTypePkg PRESENT IF !the service provider has the service provider type information!, serviceProvDownloadReasonPkg PRESENT IF !the service provider has the download reason populated!; REGISTERED AS {LNP-OIDS.lnp-objectClass 17}; serviceProvNetworkPkg PACKAGE BEHAVIOUR serviceProvNetworkDefinition, serviceProvNetworkBehavior; ATTRIBUTES serviceProvID GET, serviceProvName GET-REPLACE; ; serviceProvNetworkDefinition BEHAVIOUR DEFINED AS ! The serviceProvNetwork class is the managed object used to contain the network data for a service provider. !; serviceProvNetworkBehavior BEHAVIOUR DEFINED AS ! Local SMS, SOA, and NPAC SMS Managed Object used for the Local SMS to NPAC SMS interface and the SOA to NPAC SMS interface. Service providers and the NPAC SMS can M-GET, M-CREATE, and M-SET any serviceProvNetwork object (Network Data Association Function). The serviceProvId attribute is read only and can not be changed via the NPAC SMS to Local SMS Interface or SOA to NPAC SMS interface once the object has been created on the Local SMS, SOA or NPAC SMS. The serviceProvName can be M-SET via the NPAC SMS to Local SMS Interface or the SOA to NPAC SMS interface by the NPAC SMS. The Local SMS and SOA only create or modify local copies of serviceProvNetwork objects after receiving the objects from an NPAC SMS M-CREATE or M-SET request or reading them from the NPAC SMS for initial instantiation. !; -- 18.0 LNP Service Provider NPA-NXX Managed Object Class serviceProvNPA-NXX MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY serviceProvNPA-NXX-Pkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 18}; serviceProvNPA-NXX-Pkg PACKAGE BEHAVIOUR serviceProvNPA-NXX-Definition, serviceProvNPA-NXX-Behavior; ATTRIBUTES serviceProvNPA-NXX-ID GET, serviceProvNPA-NXX-Value GET, serviceProvNPA-NXX-EffectiveTimeStamp GET, serviceProvDownloadReason GET, serviceProvNPA-NXX-CreationTimeStamp GET; ; serviceProvNPA-NXX-Definition BEHAVIOUR DEFINED AS ! The serviceProvNPA-NXX class is the managed object used to identify Service Provider NPA-NXX values open for porting. !; serviceProvNPA-NXX-Behavior BEHAVIOUR DEFINED AS ! Local SMS, SOA, and NPAC SMS Managed Object used for the Local SMS to NPAC SMS interface and the SOA to NPAC SMS interface. All attributes are read only. Once created, the serviceProvNPA-NXX object can only be deleted via the Local SMS or SOA interface. The serviceProvNPA-NXX-ID is specified by the NPAC SMS. The serviceProvNPA-NXX-CreationTimeStamp will be set to the current system date and time when the object is created. NPAC SMS can M-GET, M-DELETE and M-CREATE any serviceProvNPA-NXX object on the Local SMS or SOA (Network Data Association Function). The Local SMS or SOA only creates local copies of serviceProvNPA-NXX objects after receiving the objects from an NPAC SMS create, after reading them from the NPAC SMS for initial instantiation, or from a download. Service providers can M-GET any serviceProvNPA-NXX object. A Local SMS or SOA can M-DELETE and M-CREATE any serviceProvNPA-NXX object on the NPAC SMS for their service provider id specified in the access control (Network Data Association Function). Attempts to take actions on unauthorized service provider objects will be rejected. A Local SMS or SOA can not modify any of the attributes. To cause an NPA-NXX split to occur the service provider must contact the NPAC SMS operations personnel. !; -- 19.0 LNP Subscription Audit Managed Object subscriptionAudit MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY subscriptionAuditPkg; CONDITIONAL PACKAGES subscriptionAuditTN-ActivationRangePkg PRESENT IF !the audit is being done on an activation data range!; REGISTERED AS {LNP-OIDS.lnp-objectClass 19}; subscriptionAuditPkg PACKAGE BEHAVIOUR subscriptionAuditDefinition, subscriptionAuditBehavior; ATTRIBUTES subscriptionAuditId GET, subscriptionAuditName GET, subscriptionAuditStatus GET, subscriptionAuditAttributeList GET, subscriptionAuditTN-Range GET, subscriptionAuditServiceProvIdRange GET, subscriptionAuditNumberOfTNs GET, subscriptionAuditNumberOfTNsComplete GET, subscriptionAuditRequestingSP GET; NOTIFICATIONS subscriptionAuditResults, subscriptionAudit-DiscrepancyRpt, "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":attributeValueChange accessControlParameter, "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":objectCreation accessControlParameter, "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":objectDeletion accessControlParameter; ; subscriptionAuditDefinition BEHAVIOUR DEFINED AS ! The subscriptionAudit class is the managed object that represents a subscription audit request. This object is only instantiated on the NPAC SMS. !; subscriptionAuditBehavior BEHAVIOUR DEFINED AS ! When the subscriptionAuditStatus changes an attribute value change will be emitted to the audit requester. All attributes must be specified upon create with the exception of the subscriptionAuditTN-ActivationRange, if an audit is not being performed on an activation date range. If the subscriptionAuditAttributeList is not specified then a full audit is assumed. If the subscriptionAuditTN-ActivationRange is specified then an audit of all TNs in the range specified in subscriptionAuditTN-Range will be audited. The serviceAuditId is determined by the NPAC SMS. The subscriptionAuditRequestingSP is the id of the service provider who requested the audit. The subscriptionAuditTN-Range is the range of TNs to be audited. If only a single TN is to be audited, the ending TN station should be set to the value of the starting TN station. The NPAC SMS will be required to set the number of TNs that will be audited in the subscriptionAuditNumberOfTNs attribute based on the NPAC SMS audit request criteria. The SOA or NPAC SMS can M-CREATE, M-GET subscriptionAudit managed objects on the NPAC SMS (SOA Management Function). When a subscriptionAudit object is created on the NPAC SMS the NPAC SMS will begin the audit for the service provider specified or all service providers. The SOA can only M-GET subscriptionAudit that they created. The SOA will be required to set the requesting SP with their service provider id so that the origination of the audit request can be tracked and notifications can be sent to the requesting SOA. When this object is created and deleted, object creation and deletion notifications will be sent to the requester. Object deletion indicates completion of an audit. The audit results notification will be sent before the object is deleted by the entity performing the audit indicating how many discrepancies the audit found and reported during execution. If discrepancies are found during the audit, audit discrepancy notifications will be sent to the requester at the time they are found. When audit discrepancy notifications are sent by the NPAC SMS to the requesting SOA, create, modify or delete requests will be sent to the Local SMS by the NPAC SMS to correct the discrepancies found. For audits involving TNs that are within a pooled block or subscription versions with an LNPType of 'pool', the NPAC SMS will query subscription version objects from the non-EDR Local SMS and it will query the number pool block object and subscription version objects from the EDR Local SMS. The EDR Local SMS should not return any subscription versions with an LNPType of 'pool'. The NPAC SMS will report to the SOA the discrepancies with subscription version identifiers. Thus, if a numberPoolBlock object is in error, the discrepancy will be reported as all TNs within the audit range. Subscription version discrepancies will be reported as usual. If a subscription version or a number pool block is in a state of 'sending' at the time of the audit, the NPAC SMS will not perform comparisons and corrections to the requested objects. Deletion of an audit object cancels an audit request. The purge of audits are based on the tunable "Audit Log Retention Period" which defaults to 90 days. !; -- 20.0 LNP subscription Version Managed Object Class subscriptionVersion MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY subscriptionVersionPkg; CONDITIONAL PACKAGES subscriptionWSMSC-DataPkg PRESENT IF !the service provider is supporting WSMSC information!; REGISTERED AS {LNP-OIDS.lnp-objectClass 20}; subscriptionVersionPkg PACKAGE BEHAVIOUR subscriptionVersionDefinition, subscriptionVersionBehavior; ATTRIBUTES subscriptionVersionId GET, subscriptionTN GET, subscriptionLRN GET-REPLACE, subscriptionNewCurrentSP GET-REPLACE, subscriptionActivationTimeStamp GET-REPLACE, subscriptionCLASS-DPC GET-REPLACE, subscriptionCLASS-SSN GET-REPLACE, subscriptionLIDB-DPC GET-REPLACE, subscriptionLIDB-SSN GET-REPLACE, subscriptionCNAM-DPC GET-REPLACE, subscriptionCNAM-SSN GET-REPLACE, subscriptionISVM-DPC GET-REPLACE, subscriptionISVM-SSN GET-REPLACE, subscriptionEndUserLocationValue GET-REPLACE, subscriptionEndUserLocationType GET-REPLACE, subscriptionBillingId GET-REPLACE, subscriptionLNPType GET-REPLACE, subscriptionDownloadReason GET-REPLACE; ; subscriptionVersionDefinition BEHAVIOUR DEFINED AS ! The subscriptionVersion class is the managed object that represents a subscription version on the Local SMS. !; subscriptionVersionBehavior BEHAVIOUR DEFINED AS ! Local SMS Managed Object used for the NPAC SMS to Local SMS Interface. NPAC SMS can M-GET (Query Association Function), M-SET, M-DELETE and M-CREATE (Data Download Association Function) any subscriptionVersion object on the Local SMS (Data Download Association Function). The Local SMS only creates local copies of subscriptionVersion objects after receiving the objects from an NPAC SMS create request or reading them from the NPAC SMS for initial instantiation. The subscriptionVersionId is assigned upon creation by the NPAC SMS and is read only. The subscriptionTN, subscriptionLRN and associated routing information, are specified by the new service provider SOA upon creation of a new subscription version. The subscriptionActivationTimeStamp is set by the NPAC SMS as the current date and time when the subscriptionVersion activation request is received from the new service provider. The Local SMS can only modify the subscriptionVersionActivationTimeStamp locally upon receiving a modify request from the NPAC SMS. The Local SMS will receive the subscriptionWSMSC-DataPkg attributes if the 'NPAC New Functionality Support' indicator is set for the 'LSMS WSMSC DPC SSN Data' in their service provider profile on the NPAC SMS. When the subscription version is downloaded to the locals, the subscriptionDownloadReason is set to one of new, delete, modified, or audit-discrepancy. This field is not validated in audits. When the subscription version disconnect is broadcast, the subscriptionVersionDonorSP-CustomerDisconnectDate is sent to the donor SOA informing the service provider of the actual customer disconnect date. 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. 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. !; -- 21.0 LNP NPAC Subscription Version Managed Object Class subscriptionVersionNPAC MANAGED OBJECT CLASS DERIVED FROM subscriptionVersion; CHARACTERIZED BY subscriptionVersionNPAC-Pkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 21}; subscriptionVersionNPAC-Pkg PACKAGE BEHAVIOUR subscriptionVersionNPAC-Definition, subscriptionVersionNPAC-Behavior-1, subscriptionVersionNPAC-Behavior-2; ATTRIBUTES subscriptionVersionStatus GET-REPLACE, subscriptionOldSP GET-REPLACE, subscriptionNewSP-DueDate GET-REPLACE, subscriptionNewSP-CreationTimeStamp GET-REPLACE, subscriptionOldSP-DueDate GET-REPLACE, subscriptionOldSP-Authorization GET-REPLACE, subscriptionStatusChangeCauseCode GET-REPLACE, subscriptionOldSP-AuthorizationTimeStamp GET-REPLACE, subscriptionBroadcastTimeStamp GET-REPLACE, subscriptionConflictTimeStamp GET-REPLACE, subscriptionCustomerDisconnectDate GET-REPLACE, subscriptionEffectiveReleaseDate GET-REPLACE, subscriptionDisconnectCompleteTimeStamp GET-REPLACE, subscriptionCancellationTimeStamp GET-REPLACE, subscriptionCreationTimeStamp GET-REPLACE, subscriptionFailed-SP-List GET-REPLACE, subscriptionModifiedTimeStamp GET-REPLACE, subscriptionOldTimeStamp GET-REPLACE, subscriptionOldSP-CancellationTimeStamp GET-REPLACE, subscriptionNewSP-CancellationTimeStamp GET-REPLACE, subscriptionOldSP-ConflictResolutionTimeStamp GET-REPLACE, subscriptionNewSP-ConflictResolutionTimeStamp GET-REPLACE, subscriptionPortingToOriginal-SPSwitch GET-REPLACE, subscriptionPreCancellationStatus GET-REPLACE, subscriptionTimerType GET, subscriptionBusinessType GET; NOTIFICATIONS subscriptionVersionOldSP-ConcurrenceRequest, subscriptionVersionNewSP-CreateRequest, subscriptionVersionOldSPFinalConcurrenceWindowExpiration, subscriptionVersionNewNPA-NXX, subscriptionVersionCancellationAcknowledgeRequest, subscriptionVersionDonorSP-CustomerDisconnectDate, subscriptionVersionStatusAttributeValueChange, subscriptionVersionNewSP-FinalCreateWindowExpiration, "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":attributeValueChange accessControlParameter phoneNumberParameter, "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":objectCreation accessControlParameter; ; subscriptionVersionNPAC-Definition BEHAVIOUR DEFINED AS ! The subscriptionVersionNPAC class is the managed object that represents a subscription version on the NPAC SMS. !; subscriptionVersionNPAC-Behavior-1 BEHAVIOUR DEFINED AS ! NPAC SMS Managed Object for the SOA to NPAC SMS and the Local SMS to NPAC SMS interface. A Local SMS can M-GET any subscriptionVersionNPAC objects from the NPAC SMS via the Local SMS Interface (Data Download Association Function). A Service Provider SOA can M-GET any subscriptionVersionNPAC objects from the NPAC SMS via the SOA Interface (SOA Management Association Function). If a Service Provider SOA or Local SMS does a scoped filtered M-GET for subscription versions, this request will only be successful if the number of records to be returned is less than or equal to the NPAC SMS tunable parameter, "Max Subscriber Query". When the status of an object is changed to "cancel-pending", subscriptionPreCancellationStatus is first set to the current status. The subscriptionCreationTimeStamp is set to the current system time when the object is created. When the subscription version is modified for any reason, the subscriptionModifiedTimeStamp is updated with the current system time. When the subscription version is broadcast to Local SMSs via the NPAC to Local SMS interface, the subscriptionBroadcastTimeStamp is updated with the current system time. When the subscription version has its version status set to old, the subscriptionOldTimeStamp is updated with the current system time. When the subscription version has its version status set to cancel, the subscriptionCancellationTimeStamp is updated with the current system time. When the subscription version has its version status set to conflict, the subscriptionConflictTimeStamp is updated with the current system time. When the subscription version is being disconnected and the first successful response is received from the Local SMS to the subscription version disconnect request, the subscriptionDisconnectCompleteTimeStamp is updated with the current system time. When the subscription version status is set to disconnect pending the subscriptionEffectiveReleaseDate is set to the date the disconnect should be broadcast. When the subscription version in a cancel-pending state is acknowledged by an old service provider SOA, the subscriptionOldSP-CancellationTimeStamp is updated with the current system time. When the subscription version in a cancel-pending state is acknowledged by a new service provider SOA, the subscriptionNewSP-CancellationTimeStamp is updated with the current system time. When the subscription version in a conflict state is removed from conflict by the old service provider SOA, the subscriptionOldSP-ConflictResolutionTimeStamp is updated with the current system time. When the subscription version in a conflict state is removed from conflict by the new service provider SOA, the subscriptionNewSP-ConflictResolutionTimeStamp is updated with the current system time. When the subscription version broadcast is not successful to all service providers, the subscriptionFailed-SP-List is populated with a list of the failed service providers. When the subscription version is created, the subscriptionTimerType is set according to the type of timer the old and new service providers support. When the subscription version is created, the subscriptionBusinessType is set according to the business days and hours the old and new service providers support. When the subscription version is created, modified, or mass updated and contains a DPC value, a valid, corresponding SSN value must be present and vice versa. An SSN value of 000 (zero) must be present when its corresponding DPC value is populated, if the corresponding SSN Edit Flag Indicator is set to TRUE. When modifying either DPC or SSN, both values must be sent to the NPAC SMS in the request, even if only one is being modified. The Service Provider SOA can M-GET and M-SET subscriptionVersionNPAC objects via the SOA to NPAC SMS interface (SOA Management Association Function). Rules for M-SET are described below. For M-GET requests, the filter will support all attributes for a specified ported TN. Any service provider SOA can view any subscription version for any active ported TN (SOA Management Association Function). Subscription versions are created on the NPAC SMS via actions over the SOA to NPAC SMS interface to the lnpSubscriptions object (SOA Management Association Function). New service provider SOAs must use the subscriptionVersionNewSP-Create action and old service provider SOAs must use the subscriptionVersionOldSP-Create action. Creates can be performed provided there is only one currently active subscription version for the TN. subscriptionPortingToOriginal-SPSwitch can only be specified as TRUE for a TN that is currently ported and is being ported back to the original service provider, along with the home switch of the NPA-NXX. If the value of subscriptionPortingToOriginal-SPSwitch is TRUE, the LRN and GTT data should not be specified, since when the activate occurs for the subscription version, the Local SMS will receive requests to delete the old subscription version routing data in their networks and will not receive any new network routing data for the subscription. Concurrence from the old service provider is required. If the value of subscriptionPortingToOriginal-SPSwitch is TRUE, the LNP Type may be either "LSPP" or "LISP". If the port of the subscription version is an intra-service provider port, the new service provider SOA can use the subscriptionVersionNewSP-Create action specifying the old service provider equal to the new service provider. In this case, the old service provider create action is not required and processing proceeds after a valid pending version is created in the same manner as it does for inter-service provider porting. The new service provider SOA must provide the subscriptionWSMSC-DataPkg attributes if the 'NPAC New Functionality Support' indicator is set for the 'SOA WSMSC DPC SSN Data' in their service provider profile on the NPAC SMS. Once a version has been created that passes validation, the subscriptionVersionNPAC object subscriptionVersionStatus will be set to pending and an object creation notification will be sent to both old and new service provider SOAs. If a version previously existed, attribute value change notifications will be sent to both old and new service provider SOAs. If there is a pending version that does not have concurrence during the "Service Provider Concurrence Window" specified in the Service Data table, a subscriptionVersionConcurrenceRequest notification will be sent to the service provider SOA that has not responded. The subscriptionVersionStatus will be set to cancel if the new service provider SOA has not responded or to conflict if the old service provider SOA has not responded after the "Service Provider Final Concurrence Window". A status attribute value change will be sent to both service providers. The Service Provider SOA can M-SET or use an M-ACTION to modify attributes associated with pending or conflict subscription versions (SOA Management Association Function). Attempts to modify an active, sending, failed, partial failure, canceled, cancel-pending, disconnect-pending or old version using an M-SET will result in an access denied error. Modification of an active subscription can be done only by the current/new service provider SOA using the subscriptionVersionModify action. Modification of an active subscription with a subscriptionFailed-SP-List will be rejected by the NPAC. Old service provider SOAs can only modify the following attributes: subscriptionOldSP-DueDate subscriptionOldSP-Authorization subscriptionStatusChangeCauseCode New service provider SOAs can only modify the following attributes: subscriptionLRN subscriptionNewSP-DueDate subscriptionCLASS-DPC subscriptionCLASS-SSN subscriptionLIDB-DPC subscriptionLIDB-SSN subscriptionCNAM-DPC subscriptionCNAM-SSN subscriptionISVM-DPC subscriptionISVM-SSN subscriptionWSMSC-DPC subscriptionWSMSC-SSN subscriptionEndUserLocationValue subscriptionEndUserLocationType subscriptionBillingId !; subscriptionVersionNPAC-Behavior-2 BEHAVIOUR DEFINED AS ! Upon subscription version creation, the subscriptionOldSP-DueDate and subscriptionNewSP-DueDate must match. If the due date for the port is a previous date, the NPAC SMS accepts a value of a previous date from a service provider, in order to match the due date of the port that was previously received from the other Service Provider (new or old). The first submitted due date (either subscriptionNewSP-DueDate or subscriptionOldSP-DueDate) must be greater than or equal to BOTH the current date AND the NPA-NXX Live Timestamp, otherwise an error will be returned. Validation will be done for both old and new service provider data that is specified on an M-SET. If validation fails, no changes will be made and a processing failure will be returned. If the version passes validation, the version status will be set to pending. An error message will be returned to the service provider if the status is not pending when they attempt to change the version status to cancel-pending. When modifying a subscription version (M-ACTION or M-SET), a change in due date (either subscriptionNewSP-DueDate or subscriptionOldSP-DueDate) will be edited. The updated due date must be greater than or equal to BOTH the current date AND the NPA-NXX Live Timestamp, otherwise an error will be returned. Once a pending version has been created, the new service provider can activate the subscription version if the new service provider due date has been reached and the NPA-NXX effective date has been reached. Once the version is activated, the version status is set to sending, the broadcast time stamp is updated, and creates are sent to the Local SMSs. If the create requests are successful for all Local SMSs, the version status will be marked as active and the previously active subscription version will have its version status set to old. If create requests fail for a subscription version after the retry periods have expired, the version status will be set to failed or partial failure based on whether the download failed in all or some of the Local SMSs respectively. Prior to the subscription version becoming active, a status version attribute value change will be sent to both old and new service providers when the subscriptionVersionStatus is modified. If the version status is failed or partial failure then a list of failed service providers is provided in the subscriptionVersionStatus notification. A subscription version can be put into conflict by either the NPAC SMS or by the old service provider explicitly setting the subscriptionOldSP-Authorization off. If the old service provider explicitly sets the subscriptionOldSP-Authorization off, the subscriptionStatusChangeCauseCode must be given. The old service provider can only put a subscription version into conflict once and only by explicitly setting the subscriptionOldSP-Authorization off. A service provider should acknowledge the cancel pending state within a tunable time frame specified on the NPAC SMS with a cancel acknowledgement action. If a new service provider SOA fails to acknowledge the cancel pending state, a subscriptionVersionCancellationAcknowledgeRequest is sent to the service provider SOA. If they do not respond to this acknowledgement in a tunable time frame specified on the NPAC SMS, the version status will be set to conflict. If the old service fails to acknowledge the cancel pending state, the subscription version status will be set to cancel. Attribute value change notifications will be sent to both service provider SOAs when the following attribute values change for a pending, cancel-pending, or conflict subscription versions (AVCs are not sent for modify active subscription versions). Also when the NPAC automatically sets a subscription version from cancel-pending to conflict upon expiration of the appropriate timers: subscriptionNewSP-DueDate subscriptionNewSP-CreationTimeStamp subscriptionOldSP-DueDate subscriptionOldSP-Authorization subscriptionOldSP-AuthorizationTimeStamp subscriptionStatusChangeCauseCode subscriptionVersionStatus The TN of the SV will be put in the additionalInformation parameter of AttributeValueChangeInfo that is defined in the standard Attribute-ASN1Module. Object creation notifications will be sent to both old and new service provider SOAs when a subscriptionVersionNPAC associated with their Service Provider id is created. Object deletion notifications will not be used. Objects will only be deleted by the NPAC SMS as a result of housekeeping processing. When a subscription version disconnect is broadcast, the subscriptionVersionDonorSP-CustomerDisconnectDate is sent to the donor SOA informing the service provider of the actual customer disconnect date. The subscriptionTimerType is only returned on SOA queries to service providers that support the timer information and is only sent on object creation notifications to service providers that support it. The subscriptionBusinessType is only returned on SOA queries to service providers that support business days/hours and is only sent on object creation notifications to service providers that support business days/hours. For number pooling, the number pool block has corresponding subscription versions with LNP type equal to 'pool'. The number pool block status represents the status of the number pool block and all subscription versions. The status of each subscription version contains the results of the broadcast of that subscription version to the non-EDR Local SMS and the result of the number pool block broadcast to the EDR Local SMSs. If a subscription version with LNP type equal to 'pool' fails a broadcast, the failed service provider list on both that subscription version and the number pool block will be set to the service provider(s) who failed. If an EDR Local SMS fails the number pool block broadcast, each subscription version with LNP type equal to 'pool' within the number pool block TN range will contain that service provider in the subscriptionFailed-SP-List. Creation, modification or deletion of a subscription version with subscriptionLNPType equal to 'pool' by the SOA is not allowed. All updates must be performed on the number pool block object. The NPAC SMS will update and broadcast the subscription versions with LNP type equal to 'pool' that are within the TN range specified by the number pool block object. The SOA or Local SMS may issue a scoped and filtered M-GET request to the NPAC SMS. If the number of objects exceeds the Maximum Subscription Query tunable value, then the number of records that equal the tunable value will be returned, followed by an empty reply to indicate the end of the returned data. The SOA or Local SMS will use the data returned to submit a subsequent query, starting with the next record from where the previous query finished. Only when the subscription version data is returned that contains less than the tunable value, has all the data been returned. The subscription version linked replies will be sorted by TN and then by subscription version ID so a filter can be created to return the next set of data where the TN value is greater than the last TN returned, OR the TN is equal to the last TN returned AND the subscription version id is greater than the last subscription version id returned. (e.g., (TN > 123-456-7890 OR (TN = 123-456-7890 AND ID > 1234)) When the subscription version broadcast is not successful to all service providers, the subscriptionFailedSP-List is populated with a list of the failed service providers. If NPAC Personnel via the NPAC Administrative Interface, exclude a Service Provider from the subscriptionFailedSP-List, the list of Service Providers will not accurately reflect those Local SMSs that successfully processed this subscription version. Service Providers that DO NOT support the enhanced SV Query functionality (Service Provider SV Query Indicator set to FALSE). The SOA or Local SMS does a scoped filtered M-GET for subscription versions. This request will only be successful if the number of records to be returned is less than or equal to the NPAC SMS tunable parameter, Maximum Subscription Query. Service Providers that DO support the enhanced SV Query functionality (Service Provider SV Query Indicator tunable parameter set to TRUE). The SOA or Local SMS may issue a scoped and filtered M-GET request to the NPAC SMS. If the number of objects exceeds the Maximum Subscription Query tunable value, then the number of records that equal the tunable value will be returned, followed by an empty reply to indicate the end of the returned data. The SOA or Local SMS will use the data returned to submit a subsequent query, starting with the next record from where the previous query finished. Only when the subscription version data is returned that contains less than the tunable value, has all the data been returned. The subscription version linked replies will be sorted by TN and then by subscription version ID so a filter can be created to return the next set of data where the TN value is greater than the last TN returned, OR the TN is equal to the last TN returned AND the subscription version id is greater than the last subscription version id returned. (e.g., (TN > 123-456-7890 OR (TN = 123-456-7890 AND ID > 1234)) !; -- 22.0 LNP Log Record for the Subscription Version Donor Service Provider -- Customer Disconnect Date Notification lnpLogDonorSP-CustomerDisconnectDateRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogDonorSP-CustomerDisconnectDatePkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 22}; lnpLogDonorSP-CustomerDisconnectDatePkg PACKAGE BEHAVIOUR lnpLogDonorSP-CustomerDisconnectDateDefinition, lnpLogDonorSP-CustomerDisconnectDateBehavior; ATTRIBUTES subscriptionTN GET, subscriptionVersionId GET, subscriptionCustomerDisconnectDate GET, subscriptionEffectiveReleaseDate GET, accessControl GET; ; lnpLogDonorSP-CustomerDisconnectDateDefinition BEHAVIOUR DEFINED AS ! The lnpLogDonorSP-CustomerDisconnectDateRecord class is the managed object that is used to create log records for the subscriptionVersionDonorSP-CustomerDisconnectDate Notification. !; lnpLogDonorSP-CustomerDisconnectDateBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionDonorSP-CustomerDisconnectDate Notification. !; -- 23.0 LNP Log Record for the Subscription Version Local SMS Action Results -- Notification lnpLogLocalSMS-ActionResultsRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogLocalSMS-ActionResultsPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 23}; lnpLogLocalSMS-ActionResultsPkg PACKAGE BEHAVIOUR lnpLogLocalSMS-ActionResultsDefinition, lnpLogLocalSMS-ActionResultsBehavior; ATTRIBUTES actionId GET, actionResultsStatus GET, failedTN-List GET, resultsCompletionTime GET, accessControl GET; ; lnpLogLocalSMS-ActionResultsDefinition BEHAVIOUR DEFINED AS ! The lnpLogLocalSMS-ActionResultsRecord class is the managed object that is used to create log records for the subscriptionVersionLocalSMS-ActionResults Notification. !; lnpLogLocalSMS-ActionResultsBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionLocalSMS-ActionResults Notification. !; -- 24.0 LNP Log Record for the Subscription Version New NPA-NXX Notification lnpLogNewNPA-NXXRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogNewNPA-NXXPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 24}; lnpLogNewNPA-NXXPkg PACKAGE BEHAVIOUR lnpLogNewNPA-NXXDefinition, lnpLogNewNPA-NXXBehavior; ATTRIBUTES serviceProvNPA-NXX-ID GET, serviceProvNPA-NXX-Value GET, serviceProvNPA-NXX-EffectiveTimeStamp GET, serviceProvID GET, accessControl GET; ; lnpLogNewNPA-NXXDefinition BEHAVIOUR DEFINED AS ! The lnpLogNewNPA-NXX class is the managed object that is used to create log records for the subscriptionVersionNewNPA-NXX Notification. !; lnpLogNewNPA-NXXBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionNewNPA-NXX Notification. !; -- 25.0 LNP Service Provider Filter NPA-NXX Managed Object Class lsmsFilterNPA-NXX MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY lsmsFilterNPA-NXX-Pkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 25}; lsmsFilterNPA-NXX-Pkg PACKAGE BEHAVIOUR lsmsFilterNPA-NXX-Definition, lsmsFilterNPA-NXX-Behavior; ATTRIBUTES lsmsFilterNPA-NXX-ID GET, lsmsFilterNPA-NXX-Value GET; ; lsmsFilterNPA-NXX-Definition BEHAVIOUR DEFINED AS ! The lsmsFilterNPA-NXX class is the managed object used to identify the NPA-NXX values for which a service provider does not want to be informed of subscription version broadcasts, network downloads, or SOA notifications. !; lsmsFilterNPA-NXX-Behavior BEHAVIOUR DEFINED AS ! NPAC SMS Managed Object used for the Local SMS to NPAC SMS interface and the NPAC SMS to SOA interface. All attributes are read only. Once created, the lsmsFilterNPA-NXX object can be deleted via the Local SMS or SOA interface. The lsmsFilterNPA-NXX-ID is specified by the NPAC SMS. The Local SMS or SOA can M-DELETE, M-CREATE and M-GET the lsmsFilterNPA-NXX objects on the NPAC SMS. (LSMS Network Data Association Function). !; -- 26.0 LNP Log Record for the Subscription Version Final Concurrence -- Timer Expiration lnpLogOldSPFinalConcurrenceWindowExpirationRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogOldSPFinalConcurrenceWindowExpirationPkg; CONDITIONAL PACKAGES subscriptionTimerTypePkg PRESENT IF !present if the Old SP SOA supports timer type!, subscriptionBusinessTypePkg PRESENT IF !present if the Old SP SOA supports business type!; REGISTERED AS {LNP-OIDS.lnp-objectClass 26}; lnpLogOldSPFinalConcurrenceWindowExpirationPkg PACKAGE BEHAVIOUR lnpLogOldSPFinalConcurrenceWindowExpirationDefinition, lnpLogOldSPFinalConcurrenceWindowExpirationBehavior; ATTRIBUTES subscriptionTN GET, subscriptionVersionId GET, accessControl GET; ; lnpLogOldSPFinalConcurrenceWindowExpirationDefinition BEHAVIOUR DEFINED AS ! The lnpLogOldSPFinalConcurrenceWindowExpirationRecord class is the managed object that is used to create log records for the subscriptionVersionOldSPFinalConcurrenceWindowExpiration Notification. !; lnpLogOldSPFinalConcurrenceWindowExpirationBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionOldSPFinalConcurrenceWindowExpiration Notification. !; -- 27.0 LNP SOA Managed Object Class lnpSOA MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY lnpSOA-Pkg; CONDITIONAL PACKAGES applicationLevelHeartBeatPkg PRESENT IF !the object is instantiated on the SOA!, swimProcessing-RecoveryResultsPkg PRESENT IF !the SOA supports SWIM Recovery!; REGISTERED AS {LNP-OIDS.lnp-objectClass 27}; lnpSOA-Pkg PACKAGE BEHAVIOUR lnpSOA-Definition, lnpSOA-Behavior; ATTRIBUTES lnpSOA-Name GET; ; lnpSOA-Definition BEHAVIOUR DEFINED AS ! The lnpSOA class is the managed object that is used as the container object for all SOA data in the SOA to NPAC SMS Interface. !; lnpSOA-Behavior BEHAVIOUR DEFINED AS ! SOA Managed Object. The NPAC SMS can M-GET any lnpSOA object (Data Download Association Function). The lnp-SOA-Name attribute is read only and can not be changed via the SOA Interface once the object has been created. The value of lnpSOA-Name will always be a unique identifier for the SOA for the SOA to NPAC Interface. Only one of these objects will exist and it will only be created at startup of the CMIP agent software on the SOA. !; -- 28.0 LNP Log Record for the Number Pool Block Status Attribute Value -- Change Notification lnpLogNumberPoolBlockStatusAttributeValueChangeRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogNumberPoolBlockStatusAttributeValueChangePkg; CONDITIONAL PACKAGES numberPoolBlockAttributeValueChangeFailed-SP-ListPkg PRESENT IF !the number pool block broadcast failed!, numberPoolBlockNPA-NXX-XPkg PRESENT IF !the number pool block npa-nxx-x is supported by the service provider in the number pool block status attribute value change notification.!; REGISTERED AS {LNP-OIDS.lnp-objectClass 28}; lnpLogNumberPoolBlockStatusAttributeValueChangePkg PACKAGE BEHAVIOUR lnpLogNumberPoolBlockStatusAttributeValueChangeDefinition, lnpLogNumberPoolBlockStatusAttributeValueChangeBehavior; ATTRIBUTES subscriptionVersionAttributeValueChangeInfo GET, accessControl GET; ; lnpLogNumberPoolBlockStatusAttributeValueChangeDefinition BEHAVIOUR DEFINED AS ! The lnpLogNumberPoolBlockStatusAttributeValueChangeRecord class is the managed object that is used to create log records for the numberPoolBlockStatusAttributeValueChange Notification. !; lnpLogNumberPoolBlockStatusAttributeValueChangeBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the numberPoolBlockStatusAttributeValueChange Notification. !; -- 29.0 Number Pool Block Data Managed Object Class -- numberPoolBlock MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY numberPoolBlock-Pkg; CONDITIONAL PACKAGES numberPoolBlockWSMSC-DataPkg PRESENT IF !the service provider is supporting WSMSC information!; REGISTERED AS {LNP-OIDS.lnp-objectClass 29}; numberPoolBlock-Pkg PACKAGE BEHAVIOUR numberPoolBlock-Definition, numberPoolBlock-Behavior; ATTRIBUTES numberPoolBlockId GET, numberPoolBlockNPA-NXX-X GET, numberPoolBlockHolderSPID GET, numberPoolBlockActivationTimeStamp GET-REPLACE, numberPoolBlockLRN GET-REPLACE, numberPoolBlockCLASS-DPC GET-REPLACE, numberPoolBlockCLASS-SSN GET-REPLACE, numberPoolBlockLIDB-DPC GET-REPLACE, numberPoolBlockLIDB-SSN GET-REPLACE, numberPoolBlockCNAM-DPC GET-REPLACE, numberPoolBlockCNAM-SSN GET-REPLACE, numberPoolBlockISVM-DPC GET-REPLACE, numberPoolBlockISVM-SSN GET-REPLACE, numberPoolBlockDownloadReason GET-REPLACE; ; numberPoolBlock-Definition BEHAVIOUR DEFINED AS ! The numberPoolBlock class is the managed object used to identify number pool block information as stored on the LSMS. !; numberPoolBlock-Behavior BEHAVIOUR DEFINED AS ! Local SMS and NPAC SMS Managed Object used for the Local SMS to NPAC SMS interface. The NPAC Customer LSMS EDR Indicator in the service provider profile on the NPAC SMS indicates which type of object will be broadcasted to each LSMS. If the LSMS supports the number pool block object, no subscription version objects should exist on the LSMS with the LNP type equal to 'pool'. The number pool block object represents the default routing information for 1000 TNs. If a subscription version exists on the LSMS for a TN within the number pool block range, the subscription routing information should be used. Otherwise, if no subscription version exists for a TN within a number pool block range, the number pool block routing information should be used. The object can be created on the LSMS via the NPAC SMS to LSMS interface. The NPAC SMS can M-GET (Query Association Function), M-CREATE, M-DELETE, and M-SET (Data Download Association Function) any numberPoolBlock object on the Local SMS. The Local SMS only creates local copies of the numberPoolBlock objects after receiving the objects from a NPAC SMS create request or reading them from the NPAC SMS for initial instantiation. The numberPoolBlockId is assigned upon creation by the NPAC SMS and is read only. The numberPoolBlockHolderSPID must be the same as the service provider ID of the service provider who sent in the request and the service provider ID of the serviceProvNPA-NXX-X object for the specified NPA-NXX-X. The numberPoolBlockActivationTimeStamp is set by the NPAC SMS as the current date and time when the create request is received. The Local SMS can only modify the numberPoolBlockActivationTimeStamp locally upon receiving a modify request from the NPAC SMS. The Local SMS will receive the numberPoolBlockWSMSC-DataPkg attributes if the 'NPAC New Functionality Support' indicator is set for the 'LSMS WSMSC DPC SSN Data' in their service provider profile on the NPAC SMS. When the number pool block is downloaded to the LSMS, the numberPoolBlockDownloadReason is set to one of new, delete, modified or audit discrepancy. This field is not validated in audits. 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. 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. Filtering Support for M-SET: Number Pool Block Modify with greaterOrEqual and lessOrEqual, and equality for EDR support. The field used with greaterOrEqual and lessOrEqual filters 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. !; -- 30.0 Number Pool Block NPAC Data Managed Object Class -- numberPoolBlockNPAC MANAGED OBJECT CLASS DERIVED FROM numberPoolBlock; CHARACTERIZED BY numberPoolBlockNPAC-Pkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 30}; numberPoolBlockNPAC-Pkg PACKAGE BEHAVIOUR numberPoolBlockNPAC-Definition, numberPoolBlockNPAC-Behavior; ATTRIBUTES numberPoolBlockBroadcastTimeStamp GET, numberPoolBlockCreationTimeStamp GET, numberPoolBlockDisconnectCompleteTimeStamp GET, numberPoolBlockModifiedTimeStamp GET, numberPoolBlockSOA-Origination GET-REPLACE, numberPoolBlockStatus GET, numberPoolBlockFailed-SP-List GET; NOTIFICATIONS numberPoolBlockStatusAttributeValueChange, "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":attributeValueChange accessControlParameter numberPoolBlockNPA-NXX-XParameter, "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":objectCreation accessControlParameter; ; numberPoolBlockNPAC-Definition BEHAVIOUR DEFINED AS ! The numberPoolBlock class is the managed object used to identify number pool block NPAC information. !; numberPoolBlockNPAC-Behavior BEHAVIOUR DEFINED AS ! SOA SMS and NPAC SMS Managed Object used for the SOA SMS to NPAC SMS interface. The numberPoolBlock object is used to represent a block of 1000 TN values. A service provider LSMS either supports the number pool block representation of the TNs or individual subscription versions with LNPType value of 'pool'. The NPAC Customer LSMS EDR Indicator in the service provider profile on the NPAC SMS indicates which type of objects will be broadcasted to each LSMS. An object creation attempt will be rejected by the NPAC SMS if any subscription versions exist with a status of pending, conflict, cancel-pending or failed ("pending-like") for a TN implied by the NPA-NXX-X value and an active subscription version object does not exist for that TN. Once created, the numberPoolBlock object can only be deleted via the NPAC SMS. The numberPoolBlockCreationTimeStamp will be set to the current date and time when the object is created by the NPAC SMS. If the SOA sends the numberPoolBlock-Create M-ACTION to create a number pool block object, the numberPoolBlockSOA-Origination will be set to true when the object is created by the NPAC SMS. Otherwise, the value will be set to false. The numberPoolBlockStatus is set at creation time by the NPAC SMS to a value of 'sending'. Other values include: active, failed, partial failure and old. The numberPoolBlockBroadcastTimeStamp is set to the date and time of the start of the last broadcast to the LSMSs for the number pool block. The numberPoolBlockDisconnectCompleteTimeStamp is set to the date and time once the first successful response is received to a delete broadcast to the LSMSs for the number pool block or corresponding subscription versions with LNP type equal to 'pool'. The numberPoolBlockModifiedTimeStamp is set to the date and time of the last modification to the number pool block object. The numberPoolBlockFailed-SP-List is set when a failure occurs in sending to the LSMSs. It contains the list of EDR and non-EDR service provider IDs who failed to successfully respond to the broadcasted data. When the number pool block is created, modified, or mass updated and contains a DPC value, a valid, corresponding SSN value must be present and vice versa. An SSN value of 000 (zero) must be present when its corresponding DPC value is populated, if the corresponding SSN Edit Flag Indicator is set to TRUE. When modifying either DPC or SSN, both values must be sent to the NPAC SMS in the request, even if only one is being modified. Service providers can M-GET any numberPoolBlockNPAC object from the LSMS and SOA. If the SOA supports the numberPoolBlock object, it can M-ACTION and M-SET any numberPoolBlockNPAC object on the NPAC SMS for their own service provider id (SOA Management Association Function). The NPAC SMS will reject any attempts to take actions on other service provider objects (soa-not-authorized) or attempts to M-DELETE the objects (accessDenied). When the SOA or NPAC SMS creates the numberPoolBlockNPAC, the status is set to "sending". The NPAC SMS creates the corresponding subscription versions that represent the block with a status of "sending" and LNP type equal to 'pool'. The NPAC SMS broadcasts to the LSMSs either the numberPoolBlock object or subscriptionVersion objects according to their service provider NPAC Customer LSMS EDR Indicator on the NPAC SMS. The object creation notification will be sent to the SOA once the number pool block object has been created on the NPAC SMS, if the SOA-origination flag is true, and contain the following attributes: numberPoolBlockId numberPoolBlockNPA-NXX-X numberPoolBlockHolderSPID numberPoolBlockSOA-Origination numberPoolBlockCreationTimeStamp numberPoolBlockStatus numberPoolBlockLRN numberPoolBlockCLASS-DPC numberPoolBlockCLASS-SSN numberPoolBlockLIDB-DPC numberPoolBlockLIDB-SSN numberPoolBlockCNAM-DPC numberPoolBlockCNAM-SSN numberPoolBlockISVM-DPC numberPoolBlockISVM-SSN numberPoolBlockWSMSC-DPC (OPTIONAL) numberPoolBlockWSMSC-SSN (OPTIONAL) The SOA can only M-SET a single number pool block instance. The M-SET can specify the numberPoolBlockNPA-NXX-X in a scoped and filtered request or direct the request at the specific numberPoolBlock object. If the NPAC SMS or SOA sends a valid M-SET for the number pool block object, the NPAC SMS will also set the data on the corresponding subscription versions with LNPType of 'pool' and broadcast the number pool block modifications to the EDR LSMSs and the subscription versions to the Non-EDR LSMSs. The non-EDR Local SMS will receive a scope level-1 request with the filter specifying the TN-Range and LNP type equal to 'pool'. The attribute value change notification will be sent out to the SOA, if the SOA-origination flag is true, when any of the following attributes change: numberPoolBlockSOA-Origination numberPoolBlockLRN numberPoolBlockCLASS-DPC numberPoolBlockCLASS-SSN numberPoolBlockLIDB-DPC numberPoolBlockLIDB-SSN numberPoolBlockCNAM-DPC numberPoolBlockCNAM-SSN numberPoolBlockISVM-DPC numberPoolBlockISVM-SSN numberPoolBlockWSMSC-DPC (OPTIONAL) numberPoolBlockWSMSC-SSN (OPTIONAL) The attribute value change will not be sent when the SOA-Origination flag is set to false. The attribute value change notification attribute list contains only the modified attribute(s). The NPA-NXX-X value of the number pool block will be put in the additionalInformation parameter of AttributeValueChangeInfo that is defined in the standard Attribute-ASN1Module. The number pool block status attribute value change notification will be sent out to the SOA, if the SOA-origination flag is true, when the status changes and can contain the following attributes: numberPoolBlockStatus numberPoolBlockFailed-SP-List If the NPAC SMS M-DELETEs the number pool block object, the corresponding subscription versions with LNPType of 'pool' will also be disconnected. The NPAC SMS will send the M-DELETE for the number pool block object to the EDR LSMSs and send the M-DELETE(s) for the subscription versions to the Non-EDR LSMSs. The non-EDR Local SMS will receive a scope level-1 request with the filter specifying the TN-Range and LNP type equal to 'pool'. The NPAC SMS can only remove one numberPoolBlockNPAC object at a time. If NPAC Personnel via the NPAC Administrative Interface, exclude a Service Provider from the numberPoolBlockFailed-SP-List, the list of Service Providers will not accurately reflect those Local SMSs that successfully processed this number pool block. !; -- 31.0 Service Provider NPA-NXX-X Data Managed Object Class -- serviceProvNPA-NXX-X MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":top; CHARACTERIZED BY serviceProvNPA-NXX-X-Pkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 31}; serviceProvNPA-NXX-X-Pkg PACKAGE BEHAVIOUR serviceProvNPA-NXX-X-Definition, serviceProvNPA-NXX-X-Behavior; ATTRIBUTES serviceProvNPA-NXX-X-ID GET, serviceProvNPA-NXX-X-Value GET, serviceProvNPA-NXX-X-CreationTimeStamp GET, serviceProvNPA-NXX-X-ModifiedTimeStamp GET-REPLACE, serviceProvNPA-NXX-X-DownloadReason GET-REPLACE, serviceProvNPA-NXX-X-EffectiveTimeStamp GET-REPLACE; ; serviceProvNPA-NXX-X-Definition BEHAVIOUR DEFINED AS ! The serviceProvNPA-NXX-X class is the managed object used to identify Service Provider NPA-NXX-X data. !; serviceProvNPA-NXX-X-Behavior BEHAVIOUR DEFINED AS ! This is the Local SMS, SOA and NPAC SMS managed object used for the Local SMS to NPAC SMS interface and SOA to NPAC SMS interface. A Local SMS supports the serviceProvNPA-NXX-X via the NPAC Customer LSMS NPA-NXX-X Indicator in their service provider profile. A SOA supports the object via the NPAC Customer SOA NPA-NXX-X Indicator in their service provider profile. Only the NPAC SMS can create, modify or delete the object. All updates are initiated by the NPAC SMS and downloaded to the Local SMSs and SOAs. An object creation attempt will be rejected by the NPAC SMS if any subscription versions exist with a status of pending, conflict, cancel-pending or failed ("pending-like") for a TN implied by the NPA-NXX-X value and an active subscription version object does not exist for that TN or the subscription version is a port-to-original request. Additionally, an object creation attempt will be rejected by the NPAC SMS if, the date of the serviceProvNPA-NXX-X-EffectiveTimeStamp is NOT greater than or equal to BOTH current date AND the NPA-NXX Live Timestamp. NPAC SMS personnel can modify the date of the serviceProvNPA-NXX-X-EffectiveTimeStamp only prior to the number pool block activation. The updated date must be greater than or equal to BOTH the current date AND the NPA-NXX Live Timestamp. The serviceProvNPA-NXX-X-ID is specified by the NPAC SMS at creation time. The serviceProvNPA-NXX-X-CreationTimeStamp is set to the current date and time of when the NPAC SMS creates the object. The serviceProvNPA-NXX-X-ModifiedTimeStamp is set to the current date and time of when the NPAC SMS last modified the object. NPAC SMS can M-DELETE, M-SET and M-CREATE a single serviceProvNPA-NXX-X object on the Local SMS or SOA (Network Data Functional Unit). The Local SMS or SOA only creates local copies of serviceProvNPA-NXX-X objects after receiving the objects from an NPAC SMS create request, reading them from the NPAC SMS download file, or from an lnpDownload request. The following attribute can be modified by the NPAC SMS: serviceProvNPA-NXX-X-EffectiveTimeStamp The serviceProvNPA-NXX-X-DownloadReason and serviceProvNPA-NXX-X-ModifiedTimeStamp can be updated as a result. The NPAC SMS will send to the Local SMS or SOA the M-SET with the new serviceProvNPA-NXX-X-EffectiveTimeStamp and serviceProvNPA-NXX-X-ModifiedTimeStamp. The SOA and Local SMS can M-GET the serviceProvNPA-NXX-X object. The subscriptionVersionNewNPA-NXX will be sent to notify the service providers SOA and Local SMS systems of the creation of this object if the creation is the first usage of the NPA-NXX. However, this notification is not emitted from the serviceProvNPA-NXX-X object, but rather from the lnpNPAC-SMS object (top-level) instead. !; -- 32.0 LNP Log Record for the Subscription Version Range Attribute Value -- Change Notification lnpLogRangeAttributeValueChangeRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogRangeAttributeValueChangePkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 32}; lnpLogRangeAttributeValueChangePkg PACKAGE BEHAVIOUR lnpLogRangeAttributeValueChangeDefinition, lnpLogRangeAttributeValueChangeBehavior; ATTRIBUTES subscriptionVersionRangeAttributeValueChangeInfo GET, accessControl GET; ; lnpLogRangeAttributeValueChangeDefinition BEHAVIOUR DEFINED AS ! The lnpLogAttributeValueChangeRecord class is the managed object that is used to create log records for the subscriptionVersionRangeAttributeValueChange Notification. !; lnpLogRangeAttributeValueChangeBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionRangeAttributeValueChange Notification. !; -- 33.0 LNP Log Record for the Subscription Version Range Object Creation -- Notification lnpLogRangeObjectCreationRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogRangeObjectCreationPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 33}; lnpLogRangeObjectCreationPkg PACKAGE BEHAVIOUR lnpLogRangeObjectCreationDefinition, lnpLogRangeObjectCreationBehavior; ATTRIBUTES subscriptionVersionRangeObjectCreationInfo GET, accessControl GET; ; lnpLogRangeObjectCreationDefinition BEHAVIOUR DEFINED AS ! The lnpLogRangeObjectCreationRecord class is the managed object that is used to create log records for the subscriptionVersionRangeObjectCreation Notification. !; lnpLogRangeObjectCreationBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionObjectCreation Notification. !; -- 34.0 LNP Log Record for the Subscription Version Range Status Attribute -- Value Change Notification lnpLogRangeStatusAttributeValueChangeRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogRangeStatusAttributeValueChangePkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 34}; lnpLogRangeStatusAttributeValueChangePkg PACKAGE BEHAVIOUR lnpLogRangeStatusAttributeValueChangeDefinition, lnpLogRangeStatusAttributeValueChangeBehavior; ATTRIBUTES subscriptionVersionRangeStatusAttributeValueChangeInfo GET, accessControl GET; ; lnpLogRangeStatusAttributeValueChangeDefinition BEHAVIOUR DEFINED AS ! The lnpLogStatusAttributeValueChangeRecord class is the managed object that is used to create log records for the subscriptionVersionRangeStatusAttributeValueChange Notification. !; lnpLogRangeStatusAttributeValueChangeBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionRangeStatusAttributeValueChange Notification. !; -- 35.0 LNP Log Record for the Subscription Version Range Donor Disconnect -- Notification lnpLogRangeDonorSP-CustomerDisconnectDateRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogRangeDonorSP-CustomerDisconnectDatePkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 35}; lnpLogRangeDonorSP-CustomerDisconnectDatePkg PACKAGE BEHAVIOUR lnpLogRangeDonorSP-CustomerDisconnectDateDefinition, lnpLogRangeDonorSP-CustomerDisconnectDateBehavior; ATTRIBUTES subscriptionVersionRangeDonorSP-CustomerDisconnectDateInfo GET, accessControl GET; ; lnpLogRangeDonorSP-CustomerDisconnectDateDefinition BEHAVIOUR DEFINED AS ! The lnpLogRangeDonorSP-CustomerDisconnectDateRecord class is the managed object that is used to create log records for the subscriptionVersionRangeDonorSP-CustomerDisconnectDate Notification. !; lnpLogRangeDonorSP-CustomerDisconnectDateBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionRangeDonorSP-CustomerDisconnectDate Notification. !; -- 36.0 LNP Log Record for the Subscription Version Range Cancellation -- Acknowledge Request Notification lnpLogRangeCancellationAcknowledgeRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogRangeCancellationAcknowledgePkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 36}; lnpLogRangeCancellationAcknowledgePkg PACKAGE BEHAVIOUR lnpLogRangeCancellationAcknowledgeDefinition, lnpLogRangeCancellationAcknowledgeBehavior; ATTRIBUTES subscriptionVersionRangeCancellationAcknowledgeInfo GET, accessControl GET; ; lnpLogRangeCancellationAcknowledgeDefinition BEHAVIOUR DEFINED AS ! The lnpLogRangeCancellationAcknowledgeRecord class is the managed object that is used to create log records for the subscriptionVersionRangeCancellationAcknowledge Notification. !; lnpLogRangeCancellationAcknowledgeBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionRangeCancellationAcknowledge Notification. !; -- 37.0 LNP Log Record for the Subscription Version Range New SP Create -- Request Notification lnpLogRangeNewSP-CreateRequestRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogRangeNewSP-CreateRequestPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 37}; lnpLogRangeNewSP-CreateRequestPkg PACKAGE BEHAVIOUR lnpLogRangeNewSP-CreateRequestDefinition, lnpLogRangeNewSP-CreateRequestBehavior; ATTRIBUTES subscriptionVersionRangeNewSP-CreateRequestInfo GET, accessControl GET; ; lnpLogRangeNewSP-CreateRequestDefinition BEHAVIOUR DEFINED AS ! The lnpLogRangeNewSP-CreateRequestRecord class is the managed object that is used to create log records for the subscriptionVersionRangeNewSP-CreateRequest Notification. !; lnpLogRangeNewSP-CreateRequestBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionRangeNewSP-CreateRequest Notification. !; -- 38.0 LNP Log Record for the Subscription Version Range Old SP -- Concurrence Request Notification lnpLogRangeOldSP-ConcurrenceRequestRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogRangeOldSP-ConcurrenceRequestPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 38}; lnpLogRangeOldSP-ConcurrenceRequestPkg PACKAGE BEHAVIOUR lnpLogRangeOldSP-ConcurrenceRequestDefinition, lnpLogRangeOldSP-ConcurrenceRequestBehavior; ATTRIBUTES subscriptionVersionRangeOldSP-ConcurrenceRequestInfo GET, accessControl GET; ; lnpLogRangeOldSP-ConcurrenceRequestDefinition BEHAVIOUR DEFINED AS ! The lnpLogRangeOldSP-ConcurrenceRequestRecord class is the managed object that is used to create log records for the subscriptionVersionRangeOldSP-ConcurrenceRequest Notification. !; lnpLogRangeOldSP-ConcurrenceRequestBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionRangeOldSP-ConcurrenceRequest Notification. !; -- 39.0 LNP Log Record for the Subscription Version Range Old SP Final -- Concurrence Window Expiration Notification lnpLogRangeOldSPFinalConcurrenceWindowExpirationRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogRangeOldSPFinalConcurrenceWindowExpirationPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 39}; lnpLogRangeOldSPFinalConcurrenceWindowExpirationPkg PACKAGE BEHAVIOUR lnpLogRangeOldSPFinalConcurrenceWindowExpirationDefinition, lnpLogRangeOldSPFinalConcurrenceWindowExpirationBehavior; ATTRIBUTES subscriptionVersionRangeOldSPFinalConcurrenceWindowExpirationInfo GET, accessControl GET; ; lnpLogRangeOldSPFinalConcurrenceWindowExpirationDefinition BEHAVIOUR DEFINED AS ! The lnpLogRangeOldSPFinalConcurrenceWindowExpirationRecord class is the managed object that is used to create log records for the subscriptionVersionRangeOldSPFinalConcurrenceWindowExpiration Notification. !; lnpLogRangeOldSPFinalConcurrenceWindowExpirationBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionRangeOldSPFinalConcurrenceWindowExpiration Notification. !; -- 40.0 LNP Log Record for the Subscription Version Range New SP Final -- Create Window Expiration Notification lnpLogRangeNewSP-FinalCreateWindowExpirationRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogRangeNewSP-FinalCreateWindowExpirationPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 40}; lnpLogRangeNewSP-FinalCreateWindowExpirationPkg PACKAGE BEHAVIOUR lnpLogRangeNewSP-FinalCreateWindowExpirationDefinition, lnpLogRangeNewSP-FinalCreateWindowExpirationBehavior; ATTRIBUTES subscriptionVersionRangeNewSP-FinalCreateWindowExpirationInfo GET, accessControl GET; ; lnpLogRangeNewSP-FinalCreateWindowExpirationDefinition BEHAVIOUR DEFINED AS ! The lnpLogRangeNewSP-FinalCreateWindowExpirationRecord class is the managed object that is used to create log records for the subscriptionVersionRangeNewSP-FinalCreateWindowExpiration Notification. !; lnpLogRangeNewSP-FinalCreateWindowExpirationBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionRangeNewSP-FinalCreateWindowExpiration Notification. !; -- 41.0 LNP Log Record for the LNP Subscription version New Service -- Provider Final Create Window Expiration Notification lnpLogNewSP-FinalCreateWindowExpirationRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogNewSP-FinalCreateWindowExpirationPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 41}; lnpLogNewSP-FinalCreateWindowExpirationPkg PACKAGE BEHAVIOUR lnpLogNewSP-FinalCreateWindowExpirationDefinition, lnpLogNewSP-FinalCreateWindowExpirationBehavior; ATTRIBUTES subscriptionTN GET, subscriptionVersionId GET, subscriptionNewCurrentSP GET, subscriptionOldSP GET, subscriptionOldSP-DueDate GET, subscriptionOldSP-Authorization GET, subscriptionOldSP-AuthorizationTimeStamp GET, subscriptionStatusChangeCauseCode GET, subscriptionTimerType GET, subscriptionBusinessType GET, accessControl GET; ; lnpLogNewSP-FinalCreateWindowExpirationDefinition BEHAVIOUR DEFINED AS ! The lnpLogNewSP-FinalCreateWindowExpirationRecord class is the managed object that is used to create log records for the subscriptionVersionNewSP-FinalCreateWindowExpiration Notification. !; lnpLogNewSP-FinalCreateWindowExpirationBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the subscriptionVersionNewSP-FinalCreateWindowExpiration Notification. !; -- 42.0 LNP Log Record for the Application Level Heart Beat Notification lnpLogHeartBeat-InformationRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 :1992":eventLogRecord; CHARACTERIZED BY lnpLogHeartBeat-InformationPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 42}; lnpLogHeartBeat-InformationPkg PACKAGE BEHAVIOUR lnpLogHeartBeat-InformationDefinition, lnpLogHeartBeat-InformationBehavior; ATTRIBUTES msgSequenceNumber GET, heartBeatTimeStamp GET; ; lnpLogHeartBeat-InformationDefinition BEHAVIOUR DEFINED AS ! The lnpLogHeartBeat-InformationRecord class is the managed object that is used to create log records for the applicationLevelHeartBeat Notification. !; lnpLogHeartBeat-InformationBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the applicationLevelHeartBeat Notification. !; -- 43.0 Lnp Log Swim Processing Recovery Results Notification lnpLogSwimProcessing-RecoveryResultsRecord MANAGED OBJECT CLASS DERIVED FROM "CCITT Rec. X.721 (1992) | ISO/IEC 10165-2 : 1992":eventLogRecord; CHARACTERIZED BY lnpLogSwimProcessing-RecoveryResultsPkg; REGISTERED AS {LNP-OIDS.lnp-objectClass 43}; lnpLogSwimProcessing-RecoveryResultsPkg PACKAGE BEHAVIOUR lnpLogSwimProcessing-RecoveryResultsDefinition, lnpLogSwimProcessing-RecoveryResultsBehavior; ATTRIBUTES actionId GET, swimResultsStatus GET, resultsCompletionTime GET, accessControl GET; ; lnpLogSwimProcessing-RecoveryResultsDefinition BEHAVIOUR DEFINED AS ! The swimProcessing-RecoveryResultsRecord class is the managed object that is used to create log records for the swimProcessing-RecoveryResults Notification. !; lnpLogSwimProcessing-RecoveryResultsBehavior BEHAVIOUR DEFINED AS ! This log record can be used by any CME wanting to log the swimProcessing-RecoveryResults Notification. !; -- -- End of MO Definitions -- -- -- Name Binding Definitions -- -- 1.0 LNP Audits Managed Object Name Bindings lnpAudits-lnpNPAC-SMS NAME BINDING SUBORDINATE OBJECT CLASS lnpAudits AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpNPAC-SMS AND SUBCLASSES; WITH ATTRIBUTE lnpAuditsName; -- Note: Create through interface is not supported. -- Note: Delete through interface is not supported. REGISTERED AS {LNP-OIDS.lnp-nameBinding 1}; -- 2.0 LNP Local SMS Managed Object Name Bindings lnpLocalSMS-root NAME BINDING SUBORDINATE OBJECT CLASS lnpLocalSMS AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS "CCITT Rec. X.660 (1992) | ISO/IEC 9834-1 : 1992":root; WITH ATTRIBUTE lnpLocal-SMS-Name; -- Note: Create through interface is not supported. -- Note: Delete through interface is not supported. REGISTERED AS {LNP-OIDS.lnp-nameBinding 3}; -- 3.0 LNP Network Managed Object Name Bindings lnpNetwork-lnpNPAC-SMS NAME BINDING SUBORDINATE OBJECT CLASS lnpNetwork AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpNPAC-SMS AND SUBCLASSES; WITH ATTRIBUTE lnpNetworkName; -- Note: Create through interface is not supported. -- Note: Delete through interface is not supported. REGISTERED AS {LNP-OIDS.lnp-nameBinding 4}; lnpNetwork-lnpLocalSMS NAME BINDING SUBORDINATE OBJECT CLASS lnpNetwork AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpLocalSMS AND SUBCLASSES; WITH ATTRIBUTE lnpNetworkName; -- Note: Create through interface is not supported. -- Note: Delete through interface is not supported. REGISTERED AS {LNP-OIDS.lnp-nameBinding 5}; lnpNetwork-lnpSOA NAME BINDING SUBORDINATE OBJECT CLASS lnpNetwork AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpSOA AND SUBCLASSES; WITH ATTRIBUTE lnpNetworkName; -- Note: Create through interface is not supported. -- Note: Delete through interface is not supported. REGISTERED AS {LNP-OIDS.lnp-nameBinding 17}; -- 4.0 LNP NPAC SMS Managed Object Name Bindings lnpNPAC-SMS-root NAME BINDING SUBORDINATE OBJECT CLASS lnpNPAC-SMS AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS "CCITT Rec. X.660 (1992) | ISO/IEC 9834-1 : 1992":root; WITH ATTRIBUTE lnpNPAC-SMS-Name; -- Note: Create through interface is not supported. -- Note: Delete through interface is not supported. REGISTERED AS {LNP-OIDS.lnp-nameBinding 6}; -- 5.0 LNP Service Providers Managed Object Name Bindings lnpServiceProvs-lnpNPAC-SMS NAME BINDING SUBORDINATE OBJECT CLASS lnpServiceProvs AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpNPAC-SMS AND SUBCLASSES; WITH ATTRIBUTE lnpServiceProvsName; -- Note: Create through interface is not supported. -- Note: Delete through interface is not supported. REGISTERED AS {LNP-OIDS.lnp-nameBinding 7}; -- 6.0 LNP Subscriptions Managed Object Class Name Bindings lnpSubscriptions-lnpNPAC-SMS NAME BINDING SUBORDINATE OBJECT CLASS lnpSubscriptions AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpNPAC-SMS AND SUBCLASSES; WITH ATTRIBUTE lnpSubscriptionsName; -- Note: Create through interface is not supported. -- Note: Delete through interface is not supported. REGISTERED AS {LNP-OIDS.lnp-nameBinding 8}; lnpSubscriptions-lnpLocalSMS NAME BINDING SUBORDINATE OBJECT CLASS lnpSubscriptions AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpLocalSMS AND SUBCLASSES; WITH ATTRIBUTE lnpSubscriptionsName; -- Note: Create through interface is not supported. -- Note: Delete through interface is not supported. REGISTERED AS {LNP-OIDS.lnp-nameBinding 9}; -- 7.0 LNP Service Provider Managed Object Class Name Bindings serviceProv-lnpServiceProvs NAME BINDING SUBORDINATE OBJECT CLASS serviceProv AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpServiceProvs AND SUBCLASSES; WITH ATTRIBUTE serviceProvID; CREATE; DELETE ONLY-IF-NO-CONTAINED-OBJECTS; REGISTERED AS {LNP-OIDS.lnp-nameBinding 10}; -- 8.0 LNP Service Provider LRN Managed Object Class Name Bindings serviceProvLRN-serviceProvNetwork NAME BINDING SUBORDINATE OBJECT CLASS serviceProvLRN AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS serviceProvNetwork AND SUBCLASSES; WITH ATTRIBUTE serviceProvLRN-ID; CREATE WITH-AUTOMATIC-INSTANCE-NAMING; DELETE ONLY-IF-NO-CONTAINED-OBJECTS; REGISTERED AS {LNP-OIDS.lnp-nameBinding 11}; -- 9.0 LNP Service Provider Network Managed Object Class Name Bindings serviceProvNetwork-lnpNetwork NAME BINDING SUBORDINATE OBJECT CLASS serviceProvNetwork AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpNetwork AND SUBCLASSES; WITH ATTRIBUTE serviceProvID; CREATE; DELETE ONLY-IF-NO-CONTAINED-OBJECTS; REGISTERED AS {LNP-OIDS.lnp-nameBinding 12}; -- 10.0 LNP Service Provider NPA-NXX Managed Object Class Name Bindings serviceProvNPA-NXX-serviceProvNetwork NAME BINDING SUBORDINATE OBJECT CLASS serviceProvNPA-NXX AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS serviceProvNetwork AND SUBCLASSES; WITH ATTRIBUTE serviceProvNPA-NXX-ID; CREATE WITH-AUTOMATIC-INSTANCE-NAMING; DELETE ONLY-IF-NO-CONTAINED-OBJECTS; REGISTERED AS {LNP-OIDS.lnp-nameBinding 13}; -- 11.0 LNP Subscription Audit for the NPAC SMS Managed Object subscriptionAudit-lnpAudits NAME BINDING SUBORDINATE OBJECT CLASS subscriptionAudit AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpAudits AND SUBCLASSES; WITH ATTRIBUTE subscriptionAuditId; CREATE WITH-AUTOMATIC-INSTANCE-NAMING; DELETE ONLY-IF-NO-CONTAINED-OBJECTS; REGISTERED AS {LNP-OIDS.lnp-nameBinding 14}; -- 12.0 LNP Subscription Version Managed Object Class subscriptionVersion-lnpSubscriptions NAME BINDING SUBORDINATE OBJECT CLASS subscriptionVersion AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpSubscriptions AND SUBCLASSES; WITH ATTRIBUTE subscriptionVersionId; CREATE WITH-AUTOMATIC-INSTANCE-NAMING; DELETE ONLY-IF-NO-CONTAINED-OBJECTS; REGISTERED AS {LNP-OIDS.lnp-nameBinding 15}; -- 13.0 LNP Service Provider LSMS Filter NPA-NXX Managed Object Class -- Name Bindings lsmsFilterNPA-NXX-serviceProv NAME BINDING SUBORDINATE OBJECT CLASS lsmsFilterNPA-NXX AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS serviceProv AND SUBCLASSES; WITH ATTRIBUTE lsmsFilterNPA-NXX-ID; CREATE WITH-AUTOMATIC-INSTANCE-NAMING; DELETE ONLY-IF-NO-CONTAINED-OBJECTS; REGISTERED AS {LNP-OIDS.lnp-nameBinding 16}; -- 14.0 LNP SOA Managed Object Name Bindings lnpSOA-root NAME BINDING SUBORDINATE OBJECT CLASS lnpSOA AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS "CCITT Rec. X.660 (1992) | ISO/IEC 9834-1 : 1992":root; WITH ATTRIBUTE lnpSOA-Name; -- Note: Create through interface is not supported. -- Note: Delete through interface is not supported. REGISTERED AS {LNP-OIDS.lnp-nameBinding 18}; -- 15.0 LNP Number Pool Block Managed Object Class -- Name Bindings numberPoolBlock-lnpSubscriptions NAME BINDING SUBORDINATE OBJECT CLASS numberPoolBlock AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS lnpSubscriptions AND SUBCLASSES; WITH ATTRIBUTE numberPoolBlockId; CREATE WITH-AUTOMATIC-INSTANCE-NAMING; DELETE ONLY-IF-NO-CONTAINED-OBJECTS; REGISTERED AS {LNP-OIDS.lnp-nameBinding 19}; -- 16.0 LNP Service Provider NPA-NXX-X Managed Object Class -- Name Bindings serviceProvNPA-NXX-X-serviceProvNetwork NAME BINDING SUBORDINATE OBJECT CLASS serviceProvNPA-NXX-X AND SUBCLASSES; NAMED BY SUPERIOR OBJECT CLASS serviceProvNetwork AND SUBCLASSES; WITH ATTRIBUTE serviceProvNPA-NXX-X-ID; CREATE WITH-AUTOMATIC-INSTANCE-NAMING; DELETE ONLY-IF-NO-CONTAINED-OBJECTS; REGISTERED AS {LNP-OIDS.lnp-nameBinding 20}; -- -- Attribute Definitions -- -- 1.0 LNP Access Control Attribute accessControl ATTRIBUTE WITH ATTRIBUTE SYNTAX LNP-ASN1.LnpAccessControl; MATCHES FOR EQUALITY; BEHAVIOUR accessControlBehavior; REGISTERED AS {LNP-OIDS.lnp-attribute 1}; accessControlB