COMMITTEE T1 – TELECOMMUNICATIONS
Working Group T1M1.5T1M1.5/99-180 Torrance, CA, August 2-6, 1999
Contribution
TITLE:Revised Version Of M.3108.2, Information Model For Connection Management Of Pre-Provisioned Service Link Connections To Form A
Reconfigurable Leased Circuit Service
SOURCE*:Telcordia Technologies: pursuant to work supported by National Telecommunications Alliance Clients
PROJECT:Information Models For R econfigurable Leased Circuit Services
_______________________________
ABSTRACT
The contribution contains a revised copy of M.3108.2. These revisions were made by the Recommendation’s editor based on instructions given by the Q15/4 experts at the March 1999 SG 4 meeting in Geneva. A copy of this contributions with any agreed changes made at this meeting of T1M1, will be submitted as a working document to the Q15/4 experts meeting the week of August 16, 1999, in Germany.
_______________________________
NOTICE
This contribution has been prepared to assist Accredited Standards Committee T1–Telecommunications. This document is offered to the Committee as a basis for discussion and is not a binding proposal on Telcordia Technologies or any other company. The requirements are subject to change in form and numerical value after more study. Telcordia Technologies specifically reserves the right to add to, amend, or withdraw the statements contained herein.
* CONTACT: Tobey Trygar; email: ttrygar@https://www.doczj.com/doc/ef5052534.html, Tel: (732) 758-5399; Fax: (732) 758-4344
Draft New Recommendation M.3108.2
TMN MANAGEMENT SERVICES FOR DEDICATED AND RECONFIGURABLE CIRCUITS NETWORK: INFORMATION MODEL FOR CONNECTION MANAGEMENT OF PRE-PROVISIONED SERVICE LINK CONNECTIONS TO FORM A
RECONFIGURABLE LEASED SERVICE
Summary (1)
Introduction And Background (1)
Keywords (1)
1 Scope (1)
2 References (1)
3 Definitions (2)
4 Abbreviations (4)
5 Conventions (4)
6 Overview Of The CM Information Model (5)
6.1 CM Managed Object Classes (5)
6.1.1 The cmLinkService MOC (5)
6.1.2 The cmLeasedCircuitService MOC (6)
6.2 Inheritance Hierarchy (6)
6.3 Referential Relationships (7)
6.4 Attributes (7)
6.4.1 The cmLinkService Attributes (8)
6.4.1.1administrativeState (8)
6.4.1.2AlarmStatus (8)
6.4.1.3CurrentProblemList (8)
6.4.1.4DedicatedOrPooled (8)
6.4.1.5EndPoints (8)
6.4.1.6LeasedCircuitServicePtrList (9)
6.4.1.7LinkConnectionSurvivability (9)
6.4.1.8LoopbackMode (9)
6.4.1.9operationalState (10)
6.4.1.10serviceID (10)
6.4.1.11serviceType (10)
6.4.1.12SupportedByObjectList (10)
i
6.4.1.13SupportedServiceNameList (10)
6.4.1.14UsageState (10)
6.4.2 The cmLeasedCircuitService Attributes (11)
6.4.2.1administrativeState (11)
6.4.2.2AlarmStatus (11)
6.4.2.3AllDedicatedSLC (11)
6.4.2.4AllSurvivableSLC (11)
6.4.2.5AvailabilityStatus (12)
6.4.2.6composedOfSLCPtrList (12)
6.4.2.7CurrentProblemList (12)
6.4.2.8operationalState (12)
6.4.2.9RestrictionsOnSLC (12)
6.4.2.10SapAEnd (13)
6.4.2.11SapZEnd (13)
6.4.2.12Schedule Specification Attributes (13)
6.4.2.13SelectionPriority (1314)
6.4.2.14ServiceAliasList (14)
6.4.2.15ServiceCustomerContact (14)
6.4.2.16ServiceDescription (14)
6.4.2.17serviceID (14)
6.4.2.18ServiceProfileObjectPtr (15)
6.4.2.19ServiceProviderContact (15)
6.4.2.20serviceType (15)
6.4.2.21startTime (15)
6.4.2.22stopTime (15)
6.4.2.23supportedByObjectList (15)
6.4.2.24SupportedServiceNameList (1516)
6.4.2.25TroubleReportFormatObjectPtr (16)
6.4.2.26UsageState (16)
6.5 Key Notifications (16)
6.5.1 Alarm-Based Notifications (16)
6.5.1.1The Quality of Service Alarm (16)
6.5.1.2The Quality of Service Protection Switching Event (1617)
6.5.2 Configuration (17)
6.5.2.1State Value Change (17)
ii
6.6.1 Create CM LCS (18)
6.6.1.1Processing Failure Specific Errors (21)
6.6.2 Identify Locked LCS (22)
6.6.3 Modify CM LCS (23)
6.6.3.1Changing The administrativeState Of An LCS (25)
6.6.4 Replace A Failed CM LCS (25)
6.6.5 Delete CM LCS (25)
6.6.5.1Processing Failure Specific Errors (26)
6.6.6 Initiate Loopback Of End-of-link Connection (26)
6.6.6.1Processing Failure Specific Errors (27)
6.6.7 Terminate Loopback Of End-of-link Connection (27)
6.7 Support For Security Requirements (28)
6.8 Naming Tree And Pointer Relationships (29)
7 Formal Model Specifications For Connection Management (30)
7.1 Managed Object Class Definitions (30)
7.1.1 cmLeasedCircuitService (30)
7.1.2 cmLinkService (30)
7.2 Package Definitions (31)
7.2.1 loopbackModePkg (31)
7.3 Parameter Definitions (31)
7.3.1 createCmLeasedCircuitServiceError (31)
7.3.2 deleteCmLeasedCircuitServiceError (32)
7.3.3 establishingLoopbackError (32)
7.3.4 terminatingLoopbackError (32)
7.4 Name Binding Definitions (33)
7.4.1 cmLeasedCircuitService-account (33)
7.4.2 cmLinkService-account (33)
7.5 Attribute Definitions (33)
7.5.1 allDedicatedSLC (33)
7.5.2 allSurvivableSLC (33)
7.5.3 composedOfSLCPtrList (34)
7.5.4 (34)
7.5.5 endPoints (34)
iii
7.5.8 loopbackMode (35)
7.5.9 restrictionsOnSLC (36)
7.5.10 sapAEnd (36)
7.5.11 sapZEnd (36)
7.5.12 selectionPriority (37)
7.5.13 serviceCustomerContact (37)
7.5.14 serviceProviderContact (37)
7.6 Behavior Definitions (38)
7.7 Action Definitions (38)
7.8 Notification Definitions (38)
7.8.1 Attribute Value Change (38)
7.8.2 Object Creation (38)
7.8.3 Object Deletion (38)
7.9 Extensibility Rules (38)
7.10 Supporting Productions (39)
8 Application Service Elements And Application Context (43)
9 Access Control (43)
10 Conformance (43)
10.1 Static Conformance (43)
10.2 Dynamic Conformance (44)
Appendix I Attribute Tables (45)
Appendix II (45)
Appendix III (46)
List Of Figures
Figure 1/M.3108.2 Inheritance hierarchy (6)
Figure 2/M.3108.2 Managed object class referential relationships (7)
Figure 3/M.3108.2 Naming tree and pointer relationships (29)
iv
List Of Tables
Table 1/ M.3208.2 functions supported in this Recommendation (17)
Table 2/M.3108.2 Information flow for CM LCS creation (18)
Table 3/M.3108.2 Information flows for identifying locked LCS (22)
Table 4/M.3108.2 Information flows for modifying LCS attributes (23)
Table 6/M.3108.2 Information Flow For Delete CM LCS (25)
Table 7/M.3108.2 Information flow for initiale loopback (27)
Table 8/M.3108.2 Information flow for termnate loopback (27)
v
Summary
To Be Added.
Introduction And Background
To Be Added.
Keywords
?Connection Management
?Dedicated and Reconfigurable Circuits Network
?Information Model
?Leased Circuit Services
?Leased Circuits
?Telecommunications Management Network (TMN)
?TMN Management Service
1Scope
This Recommendation provides a GDMO based information model to support the management of the pre-provisioned service link connections to form a leased circuit service as outlined in Recommendation M.3208.2. Informative Appendix I provides a mapping from the management functions in ITU-T Recommendation M.3208.2 to the managed objects defined in this Recommendation. Informative Appendix II provides a Unified Modeling Language (UML) view of the GDMO based information model defined herein.
2References
The following ITU-T Recommendations, and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
?ITU-T Recommendation G.805, Generic functional architecture of transport networks, November, 1995.
?ITU-T Recommendation M.125, Maintenance: Introduction and General Principles - Digital Loopback Mechanisms.
?ITU-T Recommendation M.3010, Principles for a telecommunications management network, May, 1996.
?ITU-T Recommendation M.3020, TMN Interface Specification Methodology.
1
?ITU-T Recommendation M.3100, Generic network information model, July, 1995.
?ITU-T Recommendation M.3108.1, Information model for management of leased circuit and reconfigurable services, 1999.
?ITU-T Recommendation M.3200, TMN management services and telecommunications managed areas: overview, April, 1997.
?ITU-T Recommendation M.3200, TMN Management Services.
?ITU-T Recommendation M.3208.1, T MN management services for dedicated and reconfigurable circuits network: Leased circuit services, October, 1997.
?ITU-T Recommendation M.3208.2, TMN Management Services For Dedicated And Reconfigurable Circuits Network: Connection Management Of Pre-Provisioned Service Link Connections To Form A Link Connection Service, 1999
?ITU-T Recommendation M.3320, Requirements for the X interface.
?ITU-T Recommendation M.3400, TMN management functions, April, 1997.
?ITU-T Recommendation Q.821, Stage 2 and stage 3 description for the Q3 interface -alarm surveillance.
?ITU-T Recommendation X.721, Information technology - Open Systems Interconnection - Structure of management information: Definition of management information, February, 1992.
?ITU-T Recommendation X.731, System Management: State Management Function.
?ITU-T Recommendation X.734, Information technology - Open Systems Interconnection - Systems Management: Event report management function, September, 1992.
?ITU-T Recommendation X.735, Information technology - Open Systems Interconnection - Systems Management: Log control function, September, 1992.
?ITU-T Recommendation X.746, I nformation technology - Open Systems Interconnection - Systems management: Scheduling function, April, 1995.
?ITU-T Recommendation X.790, Trouble Management for ITU-T Applications.
3Definitions
This Recommendation make use of the following terms defined and/or specialized in ITU-T Recommendation M.3208.1:
?connection point
?dedicated leased circuit service
?diversity
?layer network
?leased circuit service
?link connection
?network connection
2
?reconfigurable leased circuit service
?service access group
?service access point
?service characteristic
?service customer
?service node
?service provider
?subnetwork
?subnetwork connection
?termination connection point.
T his Recommendation make use of the following terms defined and/or specialized in ITU-T Recommendation M.3208.2:
?CM schedule:
?dedicated service link connection
?route
?service link connection
?shared service link connection
T his Recommendation make use of the following terms defined and/or specialized in ITU-T Recommendation G.805:
?access group
?access point
?connection point
?layer network
?link
?link connection
?network connection
?service node
?subnetwork
?subnetwork connection
?termination connection point
?trail
3
4Abbreviations
AP Access Point
ATM Asynchronous Transfer Mode
CM Connection Management
CP Connection Point
CPE Customer Premises Equipment
DSn Digital Signal Level n
GDMS Guidelines for the Definition of TMN Managed Services
LC Link Connection
LCS Leased Circuit Service
MS Management Services
NE Network Element
NML Network Level Management Layer
PDH Plesiochronous Digital Hierarchy
SAD Service Access Domain
SAG Service Access Group
SAP Service Access Point
SC Service Customer
SDH Synchronous Digital Hierarchy
SLA Service Level Agreement
SLC Service Link Connection
SML Service Level Management Layer
SN Service Node
SNC Sub-Network Connection
SP Service Provider
TCP Termination Connection Point
TMN Telecommunications Management Network
UML Universal Modeling Language
5Conventions
The entry, "See Recommendations M.3208.1/M.3208.2," in the Notes column of an information flow table means that the equivalent entry in Recommendations M.3208.1 and M.3208.2 are identical. Consequently the corresponding Note from either recommendation applies to this document. The entry, "See Recommendations M.3208.2” means that
4
corresponding Note in M.3208.2 is a modified version of the equivalent one in M.3208.1 and only the Note in M.3208.2 applies to this document. Note entries that do not reference other Recommendations means that the entry is an elaboration of the equivalent Note in M.3208.2 or the Note refers to an attribute that is not directly mapped to an M.3208.2 Information Element. If the Notes column is blank, the Note associated with the previous usage of the same parameter in a previous table in this Recommendation applies.
m Mandatory.
m(=) T he SP must provide the same value in the response as provided in the request by the SC.
o Optional. Optionality is subject to definition according to the service level agreement or contract between the SC and SP, i.e. a parameter listed as optional may be made mandatory by the contract.
o(=) Return of the value by the SP is optional; however, if the SP elects to return the value, it must be the same value supplied by the SC in the request. SP is not allowed to alter this field.
c Conditional parameter, definition of the condition will be specifie
d in th
e Notes
column. A numeric suffix is used to enable reuse of the conditional statements.
c(=) I f the value is provided in the request by the SC, the SP must provide the same value in the response.
Dash A dash implies that the parameter is not applicable.
To Be Added.
6Overview Of The CM Information Model
6.1 CM Managed Object Classes
The following two managed object classes (MOC) are required to meet the functional requirements specified in ITU-T Recommendation M.3208.2.
6.1.1The cmLinkService MOC
The cmLinkService MOC represents a pre- provisioned service level link connections between two connection points (CP) or between a CP and a service access point (SAP). The cmLinkService MOC represents only those aspects of a service link connection that are relevant to the creation of Reconfigurable LCSs.
The following are three examples of the service link connections. A service link connection can model the transport service resource between a SAP at a SC controlled facility and a subnetwork CP, e.g., a multiplexer port located in the SP's network. It can represent the transport service resources between two subnetwork CPs, e.g., two broadband digital cross connects in the SP’s network. It can also model the transport service resources between a subnetwork CP, such as a cross-connect in the SP's Serving Wire Center (SWC), and a SAP located in SC's end user's premises.
5
6
When properly combined with other cmLinkService managed object instances (MOI), a specific cmLinkService MOI is a component of an LCS represented by a cmLeasedCircuitService MOI.
6.1.2 The cmLeasedCircuitService MOC
The cmLeasedCircuitService MOC is a subclass of M.3108.1:transportService MOC. A cmLeasedCircuitService MOI represents an LCS. A cmLeasedCircuitService MOI models an LCS as an ordered list of service link connections. This list contains two or more service link connections. Exactly two of the service link connections in the list must be end link connections 1. A cmLeasedCircuitService MOI may be created by specifying the complete list of its constituent cmLinkService MOIs or by specifying the SAPs at the ends of the LCS.
The availability status of a cmLeasedCircuitService MOI is scheduled via the scheduling packages defined in ITU-T Recommendations X.734 and X.735.6.2 Inheritance Hierarchy
Figure 1Figure 1 contains the inheritance hierarchy for the MOCs defined in this
Figure 1/M.3108.2 Inheritance hierarchy
1
M.3208.2 only applies to point-to-point circuits.
= drop down box
Subclass Superclass = concrete class icon
7
6.3 Referential Relationships
Figure 3Figure 2 displays the referential (dependency) relationships which exist among the CM MOCs. Referential relationships represent logical dependencies between MOCs. A referential relationship may be realized by use of pointer attributes. Other choices are possible. Pointer attributes may also be used to serve other needs such as imporving the performance of the resulting application.
Figure 32/M.3108.2 Managed object class referential relationships
6.4 Attributes
This subclause describes the attributes used in CM. For each of the MOCs defined in this Recommendation, the attributes are arranged in alphabetical order in the following subclauses. Major portions of these subclauses are reused as behaviour descriptions in the GDMO templates contained in clause 7.
The following subclauses indicate if an attribute is defined in this Recommendation or if it is inherited from the transportService MOC defined in ITU-T Recommendation M.3108.1.
Appendix I contains additional information on attribute inheritance.
= SEQUENCE OF
6.4.1The cmLinkService Attributes
6.4.1.1 administrativeState
The administrativeState attribute is inherited from the M.3108.1:transportService MOC. For CM, the value of this attribute is set to unlocked when the resource is made available to the SC. The SC may change this attribute as required.for every cmLinkService MOI. Editor’s Note: Need to resolve the case where a SC changes a shared resource to locked.
6.4.1.2 AlarmStatus
Editor’s Note: This attribute could be removed from the cmLinkService class definition. There is no requirement to support alarms in M.3208.1 or in M.3208.2. Note that alarmStatus was contained in an optional package in T1.263.
The alarmStatus attribute is inherited from the “T1.240:1996”:Service MOC.
6.4.1.3 CurrentProblemList
Editor’s Note: This attribute could be removed from the cmLinkService class definition.
The currentProblemList attribute is inherited from the “T1.240:1996”:Service MOC.
6.4.1.4 DedicatedOrPooled
Editor’s Note: The information describing the relationship between the CM attributes and the M.3208.2 information elements has been move to Section 6.6, Connection Management Functions.
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: 1,
Supported functions: Create CM leased circuit service.
The dedicatedOrPooled attribute identifies whether the Service Link Connection is dedicated to the SC or is in a shared resource pool.
When a SC specifies an LCS via its SAPs, one of the possible LCS restrictions which may be specified is the value of the dedicatedOrPooled attribute for the service link connections used to support the LCS.
6.4.1.5 EndPoints
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: To Be Determined,
Supported functions: o Be Determined.
The endPoints attribute identifies both the type, and the location and the loopback status of end points of cmLinkService MOIs. End points are either service access points or connection points. End link connection has a SAP at one end point and a CP at the other. Mid link connections have CPs for both end points.
8
link connections, the loopback end point must also be specified.
A value of “true” implies that the link connection is loopbacked for testing at the end point.
A value of “true” may be specified for at most one end of the link connection.
The loopback Termination Time specifies the time at which the loopback will be removed. The loopbackMode attribute is a desirable feature because it allows a service customer to do pre-use testing and fault localization.
6.4.1.6 LeasedCircuitServicePtrList
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: 2,
Supported functions: Create CM leased circuit service.
This attribute is a list of all unlocked cmLeasedCircuitService MOIs which contain it. That is, for a specific cmLinkService MOI, it is a list of all the LCSs that (1) use the service link connection modeled by this MOI and that (2) have an administrativeState value of unlocked.
This attribute is used to determine if there is a scheduling conflict when a request to unlock an LCS which uses this cmLinkService MOI.
6.4.1.7 LinkConnectionSurvivability
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: 1,
Supported functions: Create CM leased circuit service.
The linkConnectionSurvivability attribute identifies whether or not the service link connection is survivable, i.e., the service uses facilities that are on a survivable ring or are in an Automatic Protection System protection group. A value of true indicates that the service link connection is survivable.
When a SC specifies an LCS via its SAPs, one of the possible LCS restrictions which may be specified is the value of the linkConnectionSurvivability attribute of the service link connections used to support the LCS.
6.4.1.8 LoopbackMode
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: 10,
Supported functions: Initiate and terminate loopback of end-of-link connection.
Editor’s Note: Based on the requirements in M.3208.2, the loopbackMode
attribute is expected to be removed. The loopback status information will become part of the information carried by the endPoints attribute.
9
mid link connections, the loopback end point must also be specified.
A value of “true” implies that the link connection is loopbacked for testing at the specified end. A value of “true” may be specified for at most one end of the link connection.
The loopbackMode attribute is a desirable feature because it allows a service customer to do pre-use testing and fault localization.
6.4.1.9 operationalState
The operationalState attribute is inherited from the M.3108.1:transportService MOC. In order for a link connection to support an LCS, its operationalState must have a value of enabled.
6.4.1.10 serviceID
The serviceID attribute is inherited from the M.3108.1:transportService MOC. The serviceID attribute is the Relative Distinguished Name (RDN) of the cmLinkService MOIs. It uniquely identifies the cmLinkService MOIs within a particular naming context.
6.4.1.11 serviceType
The serviceType attribute is inherited from the M.3108.1:transportService MOC.
6.4.1.12 SupportedByObjectList
Editor’s Note: This attribute is expected to be removed from the cmLinkService class definition.
The supportedByObjectList attribute is inherited from the “T1.240:1996”:Service MOC. 6.4.1.13 SupportedServiceNameList
Editor’s Note: This attribute is expected to be removed from the cmLinkService class definition.
The supportedServiceNameList attribute is inherited from the “T1.240:1996”:Service MOC.
6.4.1.14 UsageState
Editor’s Note: This attribute requires additional discussion.
The usageState indicates whether or not a service link connection is actively in use at a specific instant. A cmLinkService MOI has a usageState of Busy when it supports an on-duty cmLeasedCircuitService MOI. Its usageState is Idle when it is not supporting any cmLeasedCircuitService MOIs, or when it is supporting only locked or off-duty cmLeasedCircuitService MOIs.
10
6.4.2The cmLeasedCircuitService Attributes
6.4.2.1 administrativeState
The administrativeState attribute is inherited from the M.3108.1:transportService MOC.
If the administrativeState is changed by the SC from locked to unlocked, the availability of all service link connections comprising this LCS must be verified against the scheduled availability status of this LCS. If the requested administrativeState change causes a reservation conflict, the change request will be denied.
6.4.2.2 AlarmStatus
Editor’s Note: This attribute may be removed from the cmLinkService class definition.
The alarmStatus attribute is inherited from the “T1.256:1997”cnmServiceR1 MOC. AliasName
A conditional attribute in the transportService MOC. This is a possible substitute for the serviceAliasList attribute currently available from X.790.
6.4.2.3 AllDedicatedSLC
Editor’s Note: This attribute is not required and should be removed from the model. This functionality is covered by the restrictionOnSLC attribute.
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: 2,
Supported functions: Create CM leased circuit service.
This attribute specifies if an LCS must consist entirely of service link connections that are dedicated to the service customer, or if it may contain some service link connections from a shared pool. This attributes only applies when the request to create the LCS is made via specifying the SAPs for the LCS.
6.4.2.4 AllSurvivableSLC
Editor’s Note: This attribute is not required and should be removed from the model. This functionality is covered by the restrictionOnSLC attribute
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: 2,
Supported functions: Create CM leased circuit service.
This attribute specifies if an LCS must consist entirely of service link connections that are defined as survivable, or if it may contain some service link connections that are not defined as survivable. A value of true for the allSurvivableSLC attribute specifies that an LCS must use only survivable service link connections. False indicates that some non-survivable service link connections may be used in the LCS. This attributes only applies when the request to create the LCS is made via specifying the SAPs for the LCS.
11
6.4.2.5 AvailabilityStatus
Editor’s Note: This attribute requires additional discussion.
The availabilityStatus is inherited from the M.3108.1:transportService MOC. It is contained in the availableStatusPackage which is defined in ITU-T Recommendation X.721.
Bandwidth
Editor’s Note: Required by M.3208.2.
Inherited from transportServices.
6.4.2.6 composedOfSLCPtrList
This attribute identifies the service link connections that support an LCS. Whenever a cmLeasedCircuitService object is created, the SC may specify a series of service link connections that support the LCS or may specify a pair of SAPs. In the latter case, the service link connections are selected by the SP from the SC’s inventory of dedicated service link connections and possibly from the shared pool of service link connections. The selection of service link connections is constrained by the restrictionsOnSLC attribute.
6.4.2.7 CurrentProblemList
Editor’s Note: This attribute is expected to be removed from the cmLinkService class definition.
The currentProblemList attribute is inherited from the “T1.256:1997”cnmServiceR1 MOC.
6.4.2.8 operationalState
The operationalState attribute is inherited from the M.3108.1:transportService MOC.. In order to provide service, an LCS must have an administrativeState of unlocked, an operationalState of enabled and an availabilityStatus of on-duty.
OriginatingLocationCPE
Editor’s Note: Required by M.3208.2.
Reuse semantics and syntax from M.3108.1.
6.4.2.9 RestrictionsOnSLC
This attribute supports the following requirements and functions specified in M.3208.2:
Supported requirement: 2,
Supported functions: Create CM leased circuit service.
The restrictionsOnSLC attribute specifies constrains on the service link connections which may be selected by the SP when the SC requests the creation of an LCS via a pair of SAPs. These are used to determine which service link connections may support a specific LCS. The values for the restrictionsOnSLC attribute include:
a)No restrictions,
b)Survivable service link connections only,
c)Survivable and dedicated service link connections only,
12
d)Dedicated service link connections only with survivable links preferred,
e)Dedicated service link connections preferred and only survivable links to be
used,
f)Dedicated and survivable service link connections preferred.
6.4.2.10 SapAEnd
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: 2, 4,
Supported functions: Create CM leased circuit service.
The sapAEnd and the sapZEnd attributes identify the LCS’s service access points. Typically access points are located in an environment controlled by the SC. When a cmLeasedCircuitService MOI is created, either the values of these attributes or an explicit list of service link connection must be specified.
6.4.2.11 SapZEnd
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: 2, 4,
Supported functions: Create CM leased circuit service
The sapAEnd and the sapZEnd attributes identify the LCS’s service access points. Typically access points are located in an environment controlled by the SC. When a cmLeasedCircuitService MOI is created, either the values of these attributes or an explicit list of service link connection must be specified.
6.4.2.12 Schedule Specification Attributes
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: 8,
Supported functions: Create CM leased circuit service
The following three attributes are used to represent the scheduled on and off-duty times of an LCS:
a)intervalsOfDay,
b)schedulerName,
c)weekMask.
The intervalsOfDay attribute is defined in the dailyScheduling package. The schedularName attribute is defined in the externalSchedular package. The weekMask attribute is defined in the weelkyScheduling package. All of these packages are defined in ITU-T Recommendation X.721.
For a specific LCS, only one of these scheduling attributes will be used.
6.4.2.13 SelectionPriority
This attribute supports the following requirements and functions specified in M.3208.2:
13
Supported requirement: 5,
Supported functions: Create CM leased circuit service.
The selectionPriority attribute specifies the service customer's relative ranking of equivalent cmLeasedCircuitService MOIs between the same service access points. This priority is used to select a cmLeasedCircuitService MOI from the set of locked cmLeasedCircuitService MOIs whenever an LCS is specified via its SAPs. The set of locked cmLeasedCircuitService MOIs may be empty. See the restrictionsOnSLC attribute in Subclause 6.4.2.9 for additional details. Assignable priorities are 1 to 10 inclusive, with 1 being the highest priority. In the event of equal values of the selectionPriority attribute, the LCS selected for use is a local matter.
6.4.2.14 ServiceAliasList
Editor’s Note: This attribute is expected to be removed from the cmLinkService class definition.
The serviceAliasList attribute is inherited from the “T1.256:1997”:cnmServiceR1 MOC. serviceAvailabilityDate
Inherited from transportServices. This attribute is ignored for CM LCS purposes.
6.4.2.15 ServiceCustomerContact
This attribute supports the following requirements and functions specified in M.3208.2: Supported requirement: 2,3,
Supported functions: Create CM leased circuit service.
Editor’s Note: This attribute must be harmonized with a similar attribute in M.3108.1.
The serviceCustomerContact attribute contains the name and contact information of a person in the SC’s organization who may be called by the SP to discuss problems or questions relating to the particular LCS. This person is assumed to be knowledgeable about the SC’s LCS requirements.
6.4.2.16 ServiceDescription
Editor’s Note: This attribute is expected to be removed from the cmLinkService class definition.
The serviceDescription attribute is inherited from the “T1.256:1997”:cnmServiceR1 MOC.
6.4.2.17 serviceID
The serviceID attribute is inherited from the M.3108.1:transportService MOC. It is the Relative Distinguished Name (RDN) of the cmLeasedCircuitService MOIs. It uniquely identifies the cmLeasedCircuitService MOIs within a particular naming context. A value for the serviceID is assigned by the SP when a cmLeasedCircuitService MOIs is created. serviceLocationList
Inherited from transportServices.
14