1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T E.360.7TELECOMMUNICATION 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 Traffic engineering
2、 operational requirements ITU-T Recommendation E.360.7 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 concernin
3、g 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 Maritime
4、 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 UTILIZATION
5、 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 E.410
6、E.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 automat
7、ic 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 DEPEN
8、DABILITY 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 planning o
9、f 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.7 (05/2002) i ITU-T Recommendation E.360.7 QoS routing and related t
10、raffic engineering methods Traffic engineering operational requirements Summary The E.360.x series of Recommendations describes, analyzes, and recommends methods which control a networks response to traffic demands and other stimuli, such as link failures or node failures. The functions discussed an
11、d 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 optimization
12、 of operational networks. It encompasses the measurement, modeling, 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 efficient utilizati
13、on 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 methods propose
14、d 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-based, and T
15、DM-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 be extensible
16、 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 Recommendations be us
17、ed 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 include QoS res
18、ource 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-based, and/or T
19、DM-based technologies. Source ITU-T Recommendation E.360.7 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.7 (05/2002) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized age
20、ncy 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 a worldwide
21、 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 down in WTSA R
22、esolution 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 administrat
23、ion 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 applicability
24、 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 implement thi
25、s 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 prior writte
26、n permission of ITU. ITU-T Rec. E.360.7 (05/2002) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 4 Abbreviations 2 5 Traffic management 2 5.1 Real-time performance monitoring 2 5.2 Network control 3 5.3 Work centre functions 5 5.3.1 Automatic controls . 5 5.3.2 Code controls 5 5.3.3 Rer
27、oute controls 5 5.3.4 Peak-day control. 5 5.4 Traffic management on peak days 6 5.5 Interfaces to other work centres . 6 6 Capacity management Forecasting 6 6.1 Load Forecasting 6 6.1.1 Configuration database functions. 6 6.1.2 Load aggregation, basing and projection functions 7 6.1.3 Load adjustmen
28、t cycle and view of business adjustment cycle . 8 6.2 Network design. 8 6.3 Work centre functions 8 6.4 Interfaces to other work centres . 9 7 Capacity management Daily and weekly performance monitoring 9 7.1 Daily congestion analysis functions . 9 7.2 Study-week congestion analysis functions. 9 7.3
29、 Study-period congestion analysis functions . 10 8 Capacity management Short-term network adjustment. 10 8.1 Network design functions. 10 8.2 Work centre functions 10 8.3 Interfaces to other work centres . 10 9 Comparison of off-line (TDR) versus on-line (SDR/EDR) TE methods . 11 10 Conclusions/reco
30、mmendations. 11 iv ITU-T Rec. E.360.7 (05/2002) Introduction As discussed in the E.360.x series of Recommendations, Figure 1/E.360.1 illustrates a model for network routing and network management and design. The central box represents the network, which can have various configurations, and the traff
31、ic routing tables and transport routing tables within the network. Routing tables describe the route choices from an originating node to a terminating node for a connection request for a particular service. Hierarchical, nonhierarchical, fixed, and dynamic routing tables have all been discussed in t
32、hese series of Recommendations. Routing tables are used for a multiplicity of services on the telecommunications network, such as an MPLS/TE-based network used for illustration in this Recommendation. Traffic engineering functions include traffic management, capacity management, and network planning
33、. Figure 1/E.360.1 illustrates these functions as interacting feedback loops around the network. The input driving the network is a noisy traffic load, consisting of predictable average demand components added to unknown forecast error and other load variation components. The feedback controls funct
34、ion to regulate the service provided by the network through traffic management controls, capacity adjustments, and routing adjustments. Traffic management provides monitoring of network performance through collection and display of real-time traffic and performance data and allows traffic management
35、 controls such as code blocks, connection request gapping, and reroute controls to be inserted when circumstances warrant. Capacity management includes capacity forecasting, daily and weekly performance monitoring, and short-term network adjustment. Forecasting operates over a multiyear forecast int
36、erval and drives network capacity expansion. Daily and weekly performance monitoring identify any service problems in the network. If service problems are detected, short-term network adjustment can include routing table updates and, if necessary, short-term capacity additions to alleviate service p
37、roblems. Updated routing tables are sent to the switching systems either directly or via an automated routing update system. Short-term capacity additions are the exception, and most capacity changes are normally forecasted, planned, scheduled and managed over a period of months, or a year or more.
38、Network design embedded in capacity management includes routing design and capacity design. Network planning includes longer-term node planning and transport network planning, which operates over a horizon of months to years to plan and implement new node and transport capacity. In 6.2 to 6.5, we fo
39、cus on the steps involved in traffic management of the MPLS/TE-based network (see 6.2), capacity forecasting in the MPLS/TE-based network (see 6.3), daily and weekly performance monitoring (see 6.4), and short-term network adjustment in the MPLS/TE-based network (see 6.5). For each of these three to
40、pics, we illustrate the steps involved with examples. Monitoring of traffic and performance data is a critical issue for traffic management, capacity forecasting, daily and weekly performance monitoring, and short-term network adjustment. This topic is receiving attention in IP-based networks FGLRR9
41、9 where traffic and performance data has been somewhat lacking, in contrast to TDM-based networks where such TE monitoring data has been developed to a sophisticated standard over a period of time A98. The discussions in this Recommendation intend to point out the kind and frequency of TE traffic an
42、d performance data required to support each function. See ITU-T Recs E.490 to E.504 on general principles and requirements for traffic measurements and GOS monitoring; E.505 and E.743 on measurements for SS7 signalling networks; E.745 on measurements for ATM networks and E.506 to E.508 on forecastin
43、g methods. ITU-T Rec. E.360.7 (05/2002) 1 ITU-T Recommendation E.360.7 QoS routing and related traffic engineering methods Traffic engineering operational requirements 1 Scope The E.360.x series of Recommendations describes, analyzes, and recommends methods which control a networks response to traff
44、ic 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 Engineering Working Group (TEWG) within the Internet Engineeri
45、ng Task Force (IETF): Internet Traffic Engineering is concerned with the performance optimization of operational networks. It encompasses the measurement, modeling, characterization, and control of Internet traffic, and the application of techniques to achieve specific performance objectives, includ
46、ing 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, QoS resource management, routing table management, dynamic
47、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.419 for network management and E.490 to E.780 for other tra
48、ffic 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 widely applied in operational networks worldwide, particularly i
49、n 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 packet 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 implem
