1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T G.854.16 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2001) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital networks Management of transport network Computational viewpoint for pre-provisioned route discovery ITU-T Re
2、commendation G.854.16 (Formerly CCITT Recommendation) ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS G.100G.199 GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER-TRANSMISSION SYSTEMS G.200G.299 INDIVID
3、UAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES G.300G.399 GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES G.400G.449 COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY G.450G
4、.499 TESTING EQUIPMENTS G.500G.599 TRANSMISSION MEDIA CHARACTERISTICS G.600G.699 DIGITAL TERMINAL EQUIPMENTS G.700G.799 DIGITAL NETWORKS G.800G.899 General aspects G.800G.809 Design objectives for digital networks G.810G.819 Quality and availability targets G.820G.829 Network capabilities and functi
5、ons G.830G.839 SDH network characteristics G.840G.849 Management of transport network G.850G.859 SDH radio and satellite systems integration G.860G.869 Optical transport networks G.870G.879 DIGITAL SECTIONS AND DIGITAL LINE SYSTEM G.900G.999 For further details, please refer to the list of ITU-T Rec
6、ommendations. ITU-T G.854.16 (01/2001) i ITU-T Recommendation G.854.16 Computational viewpoint for pre-provisioned route discovery Summary This computational viewpoint specification is related to the pre-provisioned route discovery enterprise and information specification. The objective of the commu
7、nity is to identify appropriate routes for setting up, or reserving the route components for (by using other communities), a trail, a tandem connection or a subnetwork connection. It is possible to request conditions that have to be met by the identified route. In addition to proposing routes, infor
8、mation is provided to help in the selection among the candidate route on the basis of a set of properties. In case of protection, the number of routes corresponds to the protection scheme chosen. Source ITU-T Recommendation G.854.16 was prepared by ITU-T Study Group 4 (2001-2004) and approved under
9、the WTSA Resolution 1 procedure on 19 January 2001. ii ITU-T G.854.16 (01/2001) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU.
10、ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on 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
11、study by the ITU-T study groups which, in turn, produce Recommendations on these topics. 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 are prepared on
12、 a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice o
13、r implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development
14、process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore str
15、ongly urged to consult the TSB patent database. ITU 2001 All rights reserved. No part of this publication 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.854.16 (01/2001) iii CO
16、NTENTS Page 1 Scope. 1 2 References. 1 3 Definitions 1 4 Abbreviations 1 5 Conventions 2 6 Label references 2 7 Interfaces. 3 7.1 Query interfaces 3 7.2 Operational interfaces . 5 7.2.1 Route discovery interface 5 7.3 Reporting interfaces 7 7.3.1 Route discovery reporting interface 7 7.4 ASN.1 suppo
17、rting productions . 8 ITU-T G.854.16 (01/2001) 1 ITU-T Recommendation G.854.16 Computational viewpoint for pre-provisioned route discovery 1 Scope This computational viewpoint specification is related to the pre-provisioned route discovery enterprise specification defined in ITU-T G.852.16 and the p
18、re-provisioned route discovery information specification defined in ITU-T G.853.16. 2 References 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 i
19、ndicated 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
20、ITU-T Recommendations is regularly published. 1 ITU-T G.851.1 (1996), Management of the transport network Application of the RM-ODP framework. 2 ITU-T G.853.1 (1999), Common elements of the information viewpoint for the management of a transport network. 3 ITU-T G.852.16 (2001), Enterprise viewpoint
21、 for pre-provisioned route discovery. 4 ITU-T G.853.16 (2001), Information viewpoint for pre-provisioned route discovery. 5 ITU-T G.853.10 (1999), Information viewpoint for pre-provisioned link connection management. 6 ITU-T G.854.3 (1999), Computational viewpoint for topology management. 3 Definiti
22、ons No new term is defined in this Recommendation. 4 Abbreviations This Recommendation uses the following abbreviations: ASN.1 Abstract Syntax Notation One CTP Connection Termination Point Id Identifier Ifce Interface inv invariant ITU-T International Telecommunication Union Telecommunication Standa
23、rdization Sector layerND layerNetwork Domain LC LinkConnection plcm pre-provisioned link connection management 2 ITU-T G.854.16 (01/2001) prd pre-provisioned route discovery Rec. Recommendation RM-ODP Reference Model for Open Distributed Processing TTP Trail Termination Point 5 Conventions In order
24、to increase the readability of the behaviour in the operations: parameters are written in bold; elements defined in the information viewpoint specification are written in italic. 6 Label references Full label reference Local label reference prdAccessGroup prdLayerNetworkDomain prdLink prdLinkConnect
25、ion prdLinkEnd prdNetworkTTP prdNetworkCTP prdRoutingConditions prdRoute prdRouteSet prdSubnetwork prdTopologicalLink prdTopologicalLinkEnd layerNetworkDomainIs MadeOf prdRouteFulfillsRouting Conditions prdRouteSetHasRoutes directionality linkDirectionality plcmCallerId pointDirectionality prdArc-Po
26、int-orientedRouteComponents ITU-T G.854.16 (01/2001) 3 Full label reference Local label reference prdReturnedProperties prdRouteEnds prdIndividualRouteComponentsList resourceId signalIdentification topologicalEndDirection userLabel commonReportResourceId ChangeIfce commonResourceIfce Full ASN.1 prod
27、uction reference Local label reference SimpleNameType GraphicString 7 Interfaces This Recommendation does not define operations which change the userLabel of the resources or report this change to the notification receiver (these operations are defined in the superclass interfaces defined in ITU-T G
28、.854.3 and used in this Recommendation) because they do not change the state of the system. There exact signature will be developed as part of the engineering viewpoint specification with the concerned technology. 7.1 Query interfaces This Recommendation refers to interfaces that allow access to ide
29、ntification and properties of resources involved in the “pre-provisioned route discovery“ community. As the invocation of contained operations does not modify any state, there is no interest in developing them explicitly. Their exact signature will be developed as part of the engineering viewpoint,
30、with the concerned technology. These interfaces are listed in the following table with the information they allow access to. 4 ITU-T G.854.16 (01/2001) Interface name Information object Attributes and relationships prdAccessGroupQueryIfce prdLayerNetworkDomainQueryIfce prdLinkConnectionQueryIfce prd
31、LinkEndQueryIfce prdLinkQueryIfce prdNetworkCTPQueryIfce prdNetworkTTPQueryIfce prdRouteSetQueryIfce ITU-T G.854.16 (01/2001) 5 Interface name Information object Attributes and relationships prdRouteQueryIfce prdRoutingConditionsQueryIfce prdSubnetworkQueryIfce prdTopologicalLinkEndQueryIfce prdTopo
32、logicalLinkQueryIfce 7.2 Operational interfaces 7.2.1 Route discovery interface The route discovery interface provides functionality for retrieving potential routes that can be used when setting up trails, tandem connections or subnetwork connections as defined in . COMPUTATIONAL INTERFACE routeDisc
33、overyIfce DERIVED FROM OPERATION ; 6 ITU-T G.854.16 (01/2001) Discover routes OPERATION discoverRoutes INPUT_PARAMETERS routeEnds: RouteEnds := SEQUENCE OF aEnd AEndChoice, zEnd ZEndChoice; - one aEnd/zEnd pair is sufficient to represent the ends of all the routes suppliedRoutingConditions: Supplied
34、RoutingConditions - the ASN.1 type for suppliedRoutingConditions will be developed in technology - specific extensions of the route discovery community arcOrPointOrientedRouteComponents: ArcPointOriented; layerND: LayerNetworkDomainChoice; routeDir: RouteDirChoice := CHOICE dir Directionality, linkD
35、ir LinkDirectionality, pointDir PointDirectionality, topologicalEndDir TopologicalEndDirectionality; suppliedUserIdentifier: UserIdentifier; OUTPUT_PARAMETERS routeSet: ReturnedRouteSet := SET OF ReturnedRoute; routeEnds: RouteEnds - the ASN.1 type for ReturnedRoute will be developed in technology -
36、 specific extensions of the pre-provisioned route discovery community RAISED_EXCEPTIONS invalidRouteEnds: routeEnds; routingConditionsNotAssociated: SuppliedRoutingConditions; newRouteComponentsNotPartOfLND: SET OF RouteComponents; newRouteComponentsNotFree: SET OF RouteComponents; routeComponentsNo
37、tConsistent: NULL; BEHAVIOUR SEMI_FORMAL PARAMETER_MATCHING accessGroup: ; link: ; linkConnection: ; linkEnd : ; networkCTP: ; networkTTP: ; subnetwork: ; topologicalLink: ; topologicalLinkEnd: ; suppliedRoutingConditions: ; arcOrPointOrientedRouteComponents: ; layerND: ; suppliedUserIdentifier: ; r
38、outeSet: ; routeEnds: ; dir : ; linkDir: ; topologicalEndDir: ; pointDir : ; ITU-T G.854.16 (01/2001) 7 PRE_CONDITIONS inv_routeEndsLNDContainment “The elements representing the aEnd and zEnd of the routeEnds are referring to element in the relationship where layerND refers to containerLND.“ POST_CO
39、NDITIONS inv_associatedWithSuppliedRoutingConditions “The suppliedRoutingConditions have to participate in the relationship taking the fulfilledConditions role while routeSet is taking on the routeSet role.“ inv_newRouteComponentsLNDContainment “All route components of routeSet must refer to element
40、 in the relationship where layerND refers to containerLND.“ inv_freeNewRouteComponents “ of all route components contained in routeSet must be equal to NULL.“ inv_consistentRouteComponents “Only linkConnections are allowed as route components in routeSet when arcOrPointOrientedRouteComponents is equ
41、al to arc-oriented. Only networkCTPs are allowed as route components in routeSet when arcOrPointOrientedRouteComponents is equal to point-oriented.“ EXCEPTIONS IF PRE_CONDITION inv_routeEndsLNDContainment NOT_VERIFIED RAISE_EXCEPTION invalidRouteEnds; IF POST_CONDITION inv_associatedWithSuppliedRout
42、ingConditions NOT_VERIFIED RAISE_EXCEPTION routingConditionsNotAssociated; IF POST_CONDITION inv_newRouteComponentsLNDContainment NOT_VERIFIED RAISE_EXCEPTION newRouteComponentsNotPartOfLND; IF POST_CONDITION inv_freeNewRouteComponents NOT_VERIFIED RAISE_EXCEPTION newRouteComponentsNotFree; IF POST_
43、CONDITION inv_consistentRouteComponents NOT_VERIFIED RAISE_EXCEPTION routeComponentsNotConsistent; ; 7.3 Reporting interfaces 7.3.1 Route discovery reporting interface The route discovery reporting interface provides functionality for the reporting of the retrieving of potential routes that can be u
44、sed for setting up trails, tandem connections or subnetwork connections as defined in . COMPUTATIONAL INTERFACE routeDiscoveryReportingIfce DERIVED FROM OPERATION ; Route discovery reporting OPERATION reportRouteDiscovery INPUT_PARAMETERS layerND: LayerNetworkDomainChoice; routeSet: ReturnedRouteSet
45、 := SET OF ReturnedRoute; routeEnds: RouteEnds - the ASN.1 type for ReturnedRoute will be developed in technology - specific extensions of the pre-provisioned route discovery community OUTPUT_PARAMETERS - none 8 ITU-T G.854.16 (01/2001) RAISED_EXCEPTIONS - none BEHAVIOUR SEMI_FORMAL PARAMETER_MATCHI
46、NG layerND: ; routeSet: ; routeEnds: ; TRIGGERING_CONDITIONS PRE_CONDITIONS inv_noRouteSet “ routeSet does not refer to any element in the the relationship where layerND refers to containerLND.“ POST_CONDITIONS inv_existingRouteSet “ routeSet does refer to element in the the relationship where layer
47、ND refers to containerLND.“ EXCEPTIONS - none ; 7.4 ASN.1 supporting productions In this Recommendation, when an interface name is used within an ASN.1 production, the same label will be used, starting with a capital letter. The complete ASN.1 type definition for this query interface (e.g. use of Ob
48、jectIdentifier, INTEGER, .) will be developed as part of the engineering viewpoint, with the concerned technology. AccessGroupChoice := CHOICE prdAccessGroupQueryIfce PrdAccessGroupQueryIfce, userIdentifier UserIdentifier ; AEndChoice := CHOICE networkTTPChoice NetworkTTPChoice, networkCTPChoice Net
49、workCTPChoice, linkConnectionChoice LinkConnectionChoice, accessGroupChoice AccessGroupChoice, linkChoice LinkChoice, linkEndChoice LinkEndChoice, topologicalLinkChoice TopologicalLinkChoice, topologicalLinkEndChoice TopologicalLinkEndChoice, subnetworkChoice SubnetworkChoice; ArcPointOriented := CHOICE arc NULL,point NULL; LayerNetworkDomainChoice := CHOICE prdLayerNetworkDomainQueryIfce PrdLayerNetworkDomainQueryIfce, userIdentifier UserIdentifier; LinkChoice := CHOICE prdLi
