Table of Contents
1Scope,purposeandapplication
1.1Scope
1.2Purpose
1.3Application
2References
3Definitions
4Abbreviations
5Overview
5.1Genericservicerequestfragment
5.2LCSservicerequestfragment
5.3Linkconnectionservicerequestfragment
5.4Transportservicefragment
5.5Resourcefragment
6Informationmodel
6.1Managedobjectsforgenericservicerequest
fragment
6.2ManagedobjectsforLCSrequestfragment
6.3Managedobjectsforlinkconnectionservicerequest
fragment
6.4Managedobjectsforservicefragment
6.5Managedobjectsforresourcefragment
6.6Packages
6.7Attributes
6.8Errormessages
6.9Notifications
6.10Actions
6.11Namebindings
6.12ASN.1syntax
7Functionalunits
7.1Basictransportservicefunctionalunit
7.2Transportserviceorderfunctionalunit
7.3Transportserviceorderhistoryfunctionalunit
7.4Transportservicemodifyfunctionalunit
7.5Transportresourcevisibilityfunctionalunit
7.6Negotiationoffunctionalunits
8Conformance
8.1Staticconformance
8.2Dynamicconformance
8.3Conformancetomanagedobjectdefinitions
AppendixI-Protocol-independentobjectdescription
I.1Genericservicerequestfragment
I.2LCSrequestfragment
I.3Linkconnectionservicerequestfragment
I.4Servicefragment
I.5Reconfigurableservicefragment
I.6Resourcefragment
AppendixII-MappingofM.3208.1functionsinto
M.3108.1MOs
AppendixIII-UMLdiagramsforleasedcircuitservice
objectmodel Abstract
Gives a GDMO-based information model for supporting the management of the leased circuit service as described in Recommendation M.3208.1.
