Table of Contents
1Scope
2ReferencesandrelatedRecommendations
2.1References
2.2RelatedRecommendations
3Definitions
3.1Service-relateddefinitions
3.2Role-relateddefinitions
3.3Transportnetworkresourcedefinitions
4Abbreviations
5Conventions
5.1Legendfortheinformationflowtables
5.2FormatoffunctionsetsfollowsRecommendation
M.3208.1)
6Connectionmanagementservicesecurity
7Customeradministrationmanagementservice
7.1Managementservicedescription
7.2Managementgoals
7.2.1High-levelservicecustomerrequirements
forconnectionmanagement
7.2.2Specificfunctionalrequirement
7.2.3RelationshipwithRecommendationM.3208.1
7.3Managementscenarios
7.3.1Roles
7.3.2Telecommunicationsservicesandresources
7.3.3Managementfunctions
8Managementscenarios
8.1Scenariosforconnectionmanagementfunctions
8.1.1ScenariosforCMleasedcircuitservice
creation
8.1.2ScenariosforCMleasedcircuitservice
deletion
8.1.3ScenariosforCMleasedcircuitservice
modification
8.2ScenariosforCMleasedcircuitservicestatus
administration
8.2.1ScenariosforreportdeletionofCMleased
circuitservicetoservicecustomer
8.2.2Scenarioforloopbackcreation
8.2.3Scenarioforloopbackdeletion
8.2.4Scenarioforloopbackmodification
8.2.5ScenarioforlockedLCS'sidentifying
8.2.6ScenarioforfailedLCSrestoration
9Architecture
9.1Functionalarchitecture
9.2Physicalarchitecture
AppendixI-ASONETprivatelineserviceexample
AppendixII-Orderingprocessesforservicelinkconnections Abstract
Gives a profile of Recommendation M.3208.1 for customer administering of leased circuit services by means of pre-provisioned resources (link connections), which is achieved by use of existing function sets, functions and parameters from Recommendation M.3208.1 with the addition of other semantics and restrictions.
