ITU-T G 852 16-2001 Enterprise Viewpoint for Pre-Provisioned Route Discovery - Series G Transmission Systems and Media Digital Systems and Networks Digital Networks - Management of.pdf

《ITU-T G 852 16-2001 Enterprise Viewpoint for Pre-Provisioned Route Discovery - Series G Transmission Systems and Media Digital Systems and Networks Digital Networks - Management of.pdf》由会员分享，可在线阅读，更多相关《ITU-T G 852 16-2001 Enterprise Viewpoint for Pre-Provisioned Route Discovery - Series G Transmission Systems and Media Digital Systems and Networks Digital Networks - Management of.pdf（14页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNIONITU-T G.852.16TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU(01/2001)SERIES G: TRANSMISSION SYSTEMS AND MEDIA,DIGITAL SYSTEMS AND NETWORKSDigital networks Management of transport networkEnterprise viewpoint for pre-provisioned routediscoveryITU-T Recommendation G.

2、852.16(Formerly CCITT Recommendation)ITU-T G-SERIES RECOMMENDATIONSTRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKSINTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS G.100G.199GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMSG.200G.299INDIVIDUAL CHARACTERISTICS OF

3、 INTERNATIONAL CARRIER TELEPHONESYSTEMS ON METALLIC LINESG.300G.399GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONESYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITHMETALLIC LINESG.400G.449COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY G.450G.499TESTING EQUIPMENTS G.500G

4、.599TRANSMISSION MEDIA CHARACTERISTICS G.600G.699DIGITAL TERMINAL EQUIPMENTS G.700G.799DIGITAL NETWORKS G.800G.899General aspects G.800G.809Design objectives for digital networks G.810G.819Quality and availability targets G.820G.829Network capabilities and functions G.830G.839SDH network characteris

5、tics G.840G.849Management of transport network G.850G.859SDH radio and satellite systems integration G.860G.869Optical transport networks G.870G.879DIGITAL SECTIONS AND DIGITAL LINE SYSTEM G.900G.999For further details, please refer to the list of ITU-T Recommendations.ITU-T G.852.16 (01/2001) iITU-

6、T Recommendation G.852.16Enterprise viewpoint for pre-provisioned route discoverySummaryThis Recommendation specifies the enterprise viewpoint for the pre-provisioned route discovery of atransport network.The objective of the community is to identify appropriate routes for setting up, or reserving t

7、he routecomponents for (by using other communities), a trail, a tandem connection or a subnetworkconnection. It is possible to request conditions that have to be met by the identified route. In additionto proposing routes, information is provided to help in the selection among the candidate routes o

8、nthe basis of a set of properties. In case of protection, the number of routes corresponds to theprotection scheme chosen.SourceITU-T Recommendation G.852.16 was prepared by ITU-T Study Group 4 (2001-2004) andapproved under the WTSA Resolution 1 procedure on 19 January 2001.ii ITU-T G.852.16 (01/200

9、1)FOREWORDThe International Telecommunication Union (ITU) is the United Nations specialized agency in the field oftelecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ ofITU. ITU-T is responsible for studying technical, operating and tariff questions and i

10、ssuing Recommendationson them with a view to standardizing telecommunications on a worldwide basis.The World Telecommunication Standardization Assembly (WTSA), which meets every four years,establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on thesetopi

11、cs.The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.In some areas of information technology which fall within ITU-Ts purview, the necessary standards areprepared on a collaborative basis with ISO and IEC.NOTEIn this Recommendation, the expression “Admi

12、nistration“ is used for conciseness to indicate both atelecommunication administration and a recognized operating agency.INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation mayinvolve the use of a claimed Intellectual Property

13、 Right. ITU takes no position concerning the evidence,validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or othersoutside of the Recommendation development process.As of the date of approval of this Recommendation, ITU had not received notice of intell

14、ectual property,protected by patents, which may be required to implement this Recommendation. However, implementors arecautioned that this may not represent the latest information and are therefore strongly urged to consult theTSB patent database. ITU 2001All rights reserved. No part of this publica

15、tion may be reproduced or utilized in any form or by any means,electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.ITU-T G.852.16 (01/2001) iiiCONTENTSPage1 Scope 12 References 13 Definitions 14 Abbreviations . 15 Conventions 16 COMMUNITY pre-provis

16、ioned route discovery. 26.1 PURPOSE. 26.2 ROLE 26.3 COMMUNITY_POLICY. 46.4 ACTION . 46.4.1 discover routes. 46.4.2 report route discovery 5ITU-T G.852.16 (01/2001) 1ITU-T Recommendation G.852.16Enterprise viewpoint for pre-provisioned route discovery1ScopeThis Recommendation specifies the enterprise

17、 viewpoint for the pre-provisioned route discovery of atransport network.2 ReferencesThe following ITU-T Recommendations and other references contain provisions which, throughreference in this text, constitute provisions of this Recommendation. At the time of publication, theeditions indicated were

18、valid. All Recommendations and other references are subject to revision;users of this Recommendation are therefore encouraged to investigate the possibility of applying themost recent edition of the Recommendations and other references listed below. A list of the currentlyvalid ITU-T Recommendations

19、 is regularly published.1 ITU-T G.851.1 (1996), Management of the transport network Application of the RM-ODPframework.2 ITU-T G.852.2 (1999), Management of the transport network Enterprise viewpointdescription of transport network resource model.3 DefinitionsNo new term is defined in this Recommend

20、ation.4 AbbreviationsThis Recommendation uses the following abbreviations:Id IdentifierITU-T International Telecommunication Union Telecommunication Standardization Sectorprd pre-provisioned route discoveryRM-ODP Reference Model for Open Distributed Processing5 ConventionsNone.2 ITU-T G.852.16 (01/2

21、001)6 COMMUNITY pre-provisioned route discovery6.1 PURPOSE“The objective of the community is to identify appropriate routes for setting up, or reserving theroute components for (by using other communities), a trail, a tandem connection or a subnetworkconnection. It is possible to request conditions

22、that have to be met by the identified route. In additionto proposing routes, information is provided to help in the selection among the candidate routes onthe basis of a set of properties. In case of protection, the number of routes corresponds to theprotection scheme chosen.“6.2 ROLEprd_caller“This

23、 role reflects the client of the actions defined within this community. One and only one callerrole occurrence must exist in the community.“prd_provider“This role reflects the server of the actions defined within this community. One and only oneprovider role occurrence must exist in the community.“i

24、ndividual route component“This role represents one of the components of an individual route. It is either a link connectionresource as defined in ITU-T G.852.2 (in an arc-oriented view) or a connection termination pointresource as defined in ITU-T G.852.2 (in a point-oriented view) that has been des

25、ignated as acomponent of a route. Zero or more individual route component role occurrences may exist withinthis community.“notification receiver“This role represents a receiver of the reporting actions defined within this community. Zero or morenotification receiver role occurrences may exist in the

26、 community.“individual route“This role represents the route for an unprotected scheme or one of the routes in a protected scheme.Zero or more role occurrences may exist within the community.“route end“This role reflects a resource that lies at the end of a route. This role may represent a link conne

27、ctionresource, trail termination point resource, connection termination point resource, access groupresource, link resource, topological link resource, link end resource, topological link end resource orsubnetwork resource as defined in ITU-T G.852.2. Zero or more route end role occurrences mayexist

28、 within the community.“layer network domain“This role represents the layer network domain resource defined in ITU-T G.852.2. One and onlyone role occurrence must exist in the community.“route set“This role represents the set of routes returned by the provider in response to the route discoveryaction

29、. Zero or one role occurrence must exist in the community.“ITU-T G.852.16 (01/2001) 3route“This role represents a route returned by the provider in response to the route discovery action. Incase of a route for a protection scheme it may contain several individual routes corresponding to theprotectio

30、n scheme requested. One or more role occurrences may exist in the community.“T04114310-00individual route componentrouterouterouteroute setrouteroute setexample return information for a route without protection (the route and the individual routeare the same in this case)example return information f

31、or a route with 1+1 protectionindividual routesindividual routeindividual routeindividual routeindividual route component individual route componentindividual route component individual route component individual route componentindividual route component individual route component individual route c

32、omponentindividual route component individual route component individual route componentindividual route component individual route componentrouteindividual routesindividual route component individual route component individual route componentindividual route component individual route componentindi

33、vidual route componentrouteindividual routesindividual route component individual route component individual route componentindividual route componentFigure 1/G.852.16 Role diagram explaining the notion of “route“ and “individual route“4 ITU-T G.852.16 (01/2001)6.3 COMMUNITY_POLICYOBLIGATION scope“O

34、nly properties that are explicitly stated in this community are valid and can be accessed by bothcaller and provider of this community. Conformance to this service depends only on the explicitspecification of this service. Any other modifications outside of this community are not relevant forconform

35、ance.“OBLIGATION serviceRejection“In case of service rejection the provider shall identify the obligation or prohibition which is notfulfilled either by the caller or the provider. The provider shall give an indication about anyexecution infrastructure problem. In this case, the level of detail indi

36、cated by the provider shall bedependent on the shared knowledge of the infrastructure on which the community is running. For thecase where any wrong parameters have been passed to the provider, the return exception shallindicate these parameters.“OBLIGATION signalId“Each resource in the community sh

37、all have the same signal identification.“OBLIGATION viewingCapabilities“The provider shall support a view of the resource properties and relationships that have beenidentified or permitted in the service contract with the caller.“OBLIGATION belongingConstraints“All resources managed in the community

38、 actions shall belong to the community.“OBLIGATION architecturalConstraints“All the modifications performed on the resources in the community shall respect the architecturalconstraints expressed in ITU-T G.852.2.“6.4 ACTION6.4.1 discover routes“This action identifies routes for trails, tandem connec

39、tions or subnetwork connections expressed asordered series of either link connections or connection termination points in a layer network. Theroutes pertain to a certain level of partitioning. This action may be also used for finding routes forvarious protection schemes. The provider will return a r

40、oute set that may contain a number of routesbased on the service contract with the caller.“ACTION_POLICYOBLIGATION supplyRouteEnds“The caller shall identify the route ends of the requested routes.“OBLIGATION noExistingRouteEnds“This action will fail if any of the supplied route ends does not exist w

41、ithin the layer networkdomain. In the case of failure, the provider shall return the identifier in error.“PERMISSION supplyRoutingConditions“The caller may request conditions that has to be met by the returned routes. These conditions couldbe technology independent or technology dependent.ITU-T G.85

42、2.16 (01/2001) 5Examples for technology independent conditions are: request topology criteria (The topology criteria consist of a list of topology resources.); maximum Number of nodes; diversity with respect to one or more routes.Examples for technology dependent conditions are: request a constraint

43、 on bandwidth properties of the resources serving the route components(e.g. maximum average spare capacity); request routes for a specific protection scheme (The total number of individual routes withineach route corresponds to the protection scheme chosen; with no protection each potentialreturned

44、route contains just one individual route, with 1+1/1:1 two individual routes arereturned, with m:n m+n individual routes are returned.).“OBLIGATION arcVersusPointOrientedRouteComponents“The caller may request that either arc-oriented (link connections) or point-oriented (connectiontermination points

45、) route components are returned.“OBLIGATION topologyResourcesListTypes“If PERMISSION “supplyRoutingConditions“ is part of the contracted service and topology criteriaare supplied, the topology criteria must be expressed as links or topological links if the callerrequests arc-oriented route component

46、s (i.e., link connections), or as link ends, topological link ends,or subnetworks if the caller requests point oriented route components (i.e. connection terminationpoints).“OBLIGATION routingConditionsNotFulfilled“If PERMISSION “supplyRoutingConditions“ is part of the contracted service and the req

47、uest couldnot be met, the provider will reject the action and return the condition that could not be fulfilled.“PERMISSION returnedProperties“The provider may return properties associated with each returned route. The properties may betechnology dependent e.g. bandwidth parameters (e.g., average spa

48、re capacity of thelinks/topological links involved), protection scheme, or technology independent (e.g., number ofnodes, total length of the physical route).“OBLIGATION freeRouteComponents“The provider shall return only those routes where every individual route component is free.“OBLIGATION returnId

49、s“Upon success of this action, the provider shall return the unique identifiers of the route ends and theroute set. The latter shall contain the routes, optionally the properties of each route and the individualroute components.“6.4.2 report route discovery“This action is used by the provider to report to the notification receiver the discovered routes.“ACTION_POLICYOBLIGATION informRouteDiscovery“When a route set is created by the provider upon request of the caller the notification receiver shallbe informed by the provider of the identifier of the route