1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T E.360.4TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (05/2002) SERIES E: OVERALL NETWORK OPERATION, TELEPHONE SERVICE, SERVICE OPERATION AND HUMAN FACTORS International routing plan QoS routing and related traffic engineering methods Routing table manag
2、ement methods and requirements ITU-T Recommendation E.360.4 ITU-T E-SERIES RECOMMENDATIONS OVERALL NETWORK OPERATION, TELEPHONE SERVICE, SERVICE OPERATION AND HUMAN FACTORS INTERNATIONAL OPERATION Definitions E.100E.103 General provisions concerning Administrations E.104E.119 General provisions conc
3、erning users E.120E.139 Operation of international telephone services E.140E.159 Numbering plan of the international telephone service E.160E.169 International routing plan E.170E.179 Tones in national signalling systems E.180E.189 Numbering plan of the international telephone service E.190E.199 Mar
4、itime mobile service and public land mobile service E.200E.229 OPERATIONAL PROVISIONS RELATING TO CHARGING AND ACCOUNTING IN THE INTERNATIONAL TELEPHONE SERVICE Charging in the international telephone service E.230E.249 Measuring and recording call durations for accounting purposes E.260E.269 UTILIZ
5、ATION OF THE INTERNATIONAL TELEPHONE NETWORK FOR NON-TELEPHONY APPLICATIONS General E.300E.319 Phototelegraphy E.320E.329 ISDN PROVISIONS CONCERNING USERS E.330E.349 INTERNATIONAL ROUTING PLAN E.350E.399 NETWORK MANAGEMENT International service statistics E.400E.409 International network management
6、E.410E.419 Checking the quality of the international telephone service E.420E.489 TRAFFIC ENGINEERING Measurement and recording of traffic E.490E.505 Forecasting of traffic E.506E.509 Determination of the number of circuits in manual operation E.510E.519 Determination of the number of circuits in au
7、tomatic and semi-automatic operation E.520E.539 Grade of service E.540E.599 Definitions E.600E.649 Traffic engineering for IP-networks E.650E.699 ISDN traffic engineering E.700E.749 Mobile network traffic engineering E.750E.799 QUALITY OF TELECOMMUNICATION SERVICES: CONCEPTS, MODELS, OBJECTIVES AND
8、DEPENDABILITY PLANNING Terms and definitions related to the quality of telecommunication services E.800E.809 Models for telecommunication services E.810E.844 Objectives for quality of service and related concepts of telecommunication services E.845E.859 Use of quality of service objectives for plann
9、ing of telecommunication networks E.860E.879 Field data collection and evaluation on the performance of equipment, networks and services E.880E.899 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. E.360.4 (05/2002) i ITU-T Recommendation E.360.4 QoS routing and rela
10、ted traffic engineering methods Routing table management methods and requirements Summary The E.360.x series of Recommendations describes, analyses, and recommends methods which control a networks response to traffic demands and other stimuli, such as link failures or node failures. The functions di
11、scussed, and recommendations made, related to traffic engineering (TE) are consistent with the definition given in the Framework document of the Traffic Engineering Working Group (TEWG) within the Internet Engineering Task Force (IETF): Internet Traffic Engineering is concerned with the performance
12、optimization of operational networks. It encompasses the measurement, modelling, characterization, and control of Internet traffic, and the application of techniques to achieve specific performance objectives, including the reliable and expeditious movement of traffic through the network, the effici
13、ent utilization of network resources, and the planning of network capacity. The methods addressed in the E.360.x series include call and connection routing, QoS resource management, routing table management, dynamic transport routing, capacity management, and operational requirements. Some of the me
14、thods proposed herein are also addressed in or are closely related to those proposed in ITU-T Recs E.170 to E.179 and E.350 to E.353 for routing, E.410 to E.419 for network management and E.490 to E.780 for other traffic engineering issues. The recommended methods are meant to apply to IP-based, ATM
15、-based, and TDM-based networks, as well as the interworking between these network technologies. Essentially, all of the methods recommended are already widely applied in operational networks worldwide, particularly in PSTN networks employing TDM-based technology. However, these methods are shown to
16、be extensible to packet-based technologies, that is, to IP-based and ATM-based technologies, and it is important that networks which evolve to employ these packet technologies have a sound foundation of methods to apply. Hence, it is the intent that the methods recommended in this series of Recommen
17、dations be used as a basis for requirements for specific methods, and, as needed, for protocol development in IP-based, ATM-based, and TDM-based networks to implement the methods. The methods encompassed in this Recommendation include traffic management through control of routing functions, which in
18、clude QoS resource management. Results of analysis models are presented which illustrate the tradeoffs between various approaches. Based on the results of these studies as well as established practice and experience, methods are recommended for consideration in network evolution to IP-based, ATM-bas
19、ed, and/or TDM-based technologies. Source ITU-T Recommendation E.360.4 was prepared by ITU-T Study Group 2 (2001-2004) and approved under the WTSA Resolution 1 procedure on 16 May 2002. ii ITU-T Rec. E.360.4 (05/2002) FOREWORD The International Telecommunication Union (ITU) is the United Nations spe
20、cialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on
21、 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 these topics. The approval of ITU-T Recommendations is covered by the procedure laid do
22、wn in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication
23、 administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or a
24、pplicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development 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 i
25、mplement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2003 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the
26、prior written permission of ITU. ITU-T Rec. E.360.4 (05/2002) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 4 Abbreviations 2 5 Routing table management for IP-based networks. 2 6 Routing table management for ATM-based networks 6 7 Routing table management for TDM-based networks 8 8 Si
27、gnalling and information exchange requirements . 10 8.1 Call routing (number translation to routing address) information-exchange parameters 12 8.2 Connection routing information-exchange parameters 12 8.3 QoS resource management information-exchange parameters 13 8.4 Routing table management inform
28、ation-exchange parameters 14 8.5 Harmonization of information-exchange standards . 15 8.6 Open routing Application Programming Interface (API). 15 9 Examples of internetwork routing 16 9.1 Internetwork E uses a mixed path selection method 16 9.2 Internetwork E uses a single path selection method. 18
29、 10 Conclusions/recommendations. 18 Annex A Modelling of traffic engineering methods. 19 iv ITU-T Rec. E.360.4 (05/2002) Introduction Routing table management typically entails the automatic generation of routing tables based on network topology and other information such as status. Routing table ma
30、nagement information, such as topology update, status information, or routing recommendations, is used for purposes of applying the routing table design rules for determining path choices in the routing table. This information is exchanged between one node and another node, such as between the origi
31、nating node (ON) and destination node (DN), for example, or between a node and a network element such as a bandwidth-broker processor (BBP). This information is used to generate the routing table, and then the routing table is used to determine the path choices used in the selection of a path. This
32、automatic generation function is enabled by the automatic exchange of link, node, and reachable address information among the network nodes. In order to achieve automatic update and synchronization of the topology database, which is essential for routing table management, IP- and ATM-based networks
33、already interpret HELLO protocol mechanisms to identify links in the network. For topology database synchronization, the link state advertisement (LSA) is used in IP-based networks, and the PNNI topology-state-element (PTSE) exchange is used in ATM-based networks to automatically provision nodes, li
34、nks, and reachable addresses in the topology database. Use of a single peer group/autonomous system for topology update leads to more efficient routing and easier administration, and is best achieved by minimizing the use of topology state (LSA and PTSE) flooding for dynamic topology state informati
35、on. It is required in 8.4 that a topology state element (TSE) be developed within TDM-based networks. When this is the case, then the HELLO and LSA/TSE/PTSE parameters will become the standard topology update method for interworking across IP-, ATM-, and TDM-based networks. Status update methods are
36、 required for use in routing table management within and between network types. In TDM-based networks, status updates of link and/or node status are used E.350, E.351. Within IP- and ATM-based networks, status updates are provided by a flooding mechanism. It is required in 8.4 that a routing status
37、element (RSE) be developed within TDM-based networks, which will be compatible with the PNNI topology state element (PTSE) in ATM-based networks and the link state advertisement (LSA) element in IP-based networks. When this is the case, then the RSE/PTSE/LSA parameters will become the standard statu
38、s update method for interworking across TDM-, ATM-, and IP-based networks. Query for status methods are required for use in routing table management within and between network types. Such methods allow efficient determination of status information, as compared to flooding mechanisms. Such query for
39、status methods are provided in TDM-based networks E.350, E.351. It is required in 8.4 that a routing query element (RQE) be developed within ATM-based and IP-based networks. When this is the case, then the RQE parameters will become the standard query for status method for interworking across TDM-,
40、ATM-, and IP-based networks. Routing recommendation methods are proposed for use in routing table management within and between network types. For example, such methods provide for a database, such as a BBP, to advertise recommended paths to network nodes based on status information available in the
41、 database. Such routing recommendation methods are provided in TDM-based networks E.350, E.351. It is required in 8.4 that a routing recommendation element (RRE) be developed within ATM-based and IP-based networks. When this is the case, then the RRE parameters will become the standard query for sta
42、tus method for interworking across TDM-, ATM-, and IP-based networks. ITU-T Rec. E.360.4 (05/2002) 1 ITU-T Recommendation E.360.4 QoS routing and related engineering methods Routing table management methods and requirements 1 Scope The E.360.x series of Recommendations describes, analyses, and recom
43、mends methods which control a networks response to traffic demands and other stimuli, such as link failures or node failures. The functions discussed, and recommendations made, related to traffic engineering (TE) are consistent with the definitions given in the Framework document of the Traffic Engi
44、neering Working Group (TEWG) within the Internet Engineering Task Force (IETF): Internet Traffic Engineering is concerned with the performance optimization of operational networks. It encompasses the measurement, modelling, characterization, and control of Internet traffic, and the application of te
45、chniques to achieve specific performance objectives, including the reliable and expeditious movement of traffic through the network, the efficient utilization of network resources, and the planning of network capacity. The methods addressed in the E.360.x series include call and connection routing,
46、QoS resource management, routing table management, dynamic transport routing, capacity management, and operational requirements. Some of the methods proposed herein are also addressed in or are closely related to those proposed in ITU-T Recs E.170 to E.179 and E.350 to E.353 for routing, E.410 to E.
47、419 for network management and E.490 to E.780 for other traffic engineering issues. The recommended methods are meant to apply to IP-based, ATM-based, and TDM-based networks, as well as the interworking between these network technologies. Essentially, all of the methods recommended are already widel
48、y applied in operational networks worldwide, particularly in PSTN networks employing TDM-based technology. However, these methods are shown to be extensible to packet-based technologies, that is, to IP-based and ATM-based technologies, and it is important that networks which evolve to employ these p
49、acket technologies have a sound foundation of methods to apply. Hence, it is the intent that the methods recommended in this series of Recommendations be used as a basis for requirements for specific methods, and, as needed, for protocol development in IP-based, ATM-based, and TDM-based networks to implement the methods. Hence the methods encompassed in this series of Recommendations include: traffic management through control of routing functions, which include call routing (number/name translation to routing address), connection rout
