ITU-T E 492-1996 Traffic Reference Period - Telephone Network and ISDN Quality of Service Network Management and Traffic Engineering (Study Group 2) 11 pp《话务参考周期 电话网络和综合业务服务网(ISDN).pdf

《ITU-T E 492-1996 Traffic Reference Period - Telephone Network and ISDN Quality of Service Network Management and Traffic Engineering (Study Group 2) 11 pp《话务参考周期 电话网络和综合业务服务网(ISDN).pdf》由会员分享，可在线阅读，更多相关《ITU-T E 492-1996 Traffic Reference Period - Telephone Network and ISDN Quality of Service Network Management and Traffic Engineering (Study Group 2) 11 pp《话务参考周期 电话网络和综合业务服务网(ISDN).pdf（11页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU E.492 (02/96) TELEPHONE NETWORK AND ISDN QUALITY OF SERVICE, NETWORK MANAGEMENT AND TRAFFIC ENGINEERING TRAFFIC REFERENCE PERIOD ITU-T Recommendation E.492 (Previously “CCIlT Recommendation”) COPYRIGHT Intern

2、ational Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Services ITU-T RECMN*E.472 76 = 4862571 061b781 2b4 FOREWORD The -T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (). The ITU-T is responsible for st

3、udying technical, operating and tariff questions and issuing Recommen- dations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Stud

4、y Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). IT-T Recommendation E.492 was prepared by ITU-T Study Group 2 (1993-1996) a

5、nd was approved under the WTSC Resolution No. 1 procedure on the 19th of February 1996. NOTE In this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. O ITiJ 1996 All rights reserved. No part

6、 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 the ITU. COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Services

7、1 2 3 4 5 6 7 8 9 10 11 12 13 14 . ITU-T RECMNUUE.492 96 m 4862591 0616382 LTO = CONTENTS Scope References Terms and definitions . Introduction Principles Operations Measurement seasons and days Combination of measured da ta . Measurement hours Read-out periods Reference periods for quality factors

8、during the normal and high load . Reference periods for network-wide quality factors Different networks and services . 13.1 PSTN . 13.2 N-ISDN and the IN-based services . 13.3 Signalling System No . 7 (SS No . 7) . 13.4 B-ISDN . 13.5 Other networks and services . History Annex A . Traffic measuremen

9、ts process ch art Annex B - Examples of traffic measurements . Recommendation E.492 (02/96) Page 1 1 1 1 1 2 2 2 2 2 3 3 3 3 3 4 4 4 4 5 6 i COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesITU-T RECMN*Ee492 96 4862573 Ob36783 037 SUMMAR

10、Y Traffic reference period is a time period, relevant in traffic observations for quality control or dimensioning. The traffic reference periods are defined to detect periods of loads appropriate for monitoring Grade of Service (GOS). Normally these are not predictable. This Recommendation discusses

11、 aspects related to determining these periods. Definitions are provided, also, for normal and high load. Recommendation E.492 (OW96) 11 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesRecommendation E.492 TRAFFIC REFERENCE PERIOD (Genev

12、a, 1996) 1 Scope This Recommendation provides the definition of traffic reference periods, normal load and high load for the purpose of collecting measurements for monitoring Grade of Service (GOS) for networks and network components (e.g. exchanges and circuit-groups). 2 References Related Recommen

13、dations are E.490, E.491, ES00 and ES02 about traffic measurements and dimensioning and E.721, E.723, E.771 and E.776 about specifying target service quality parameters. 3 Terms and definitions Terms and definitions follow Recommendations E.600 and E.800. 4 Introduction Switched or packet networks a

14、re now being used, and will be used even more in the future, for different services. The traffic management of a network provided by a single operator is described in Recommendation E.490; but many actual network structures involve multiple network operators. Agiven service can make use of the netwo

15、rks of several operators in several countries. In order to guarantee the service level in the networks, a number of operations are necessary, like augmentations, restructuring and reroutings. Many of these operations are based on known and forecasted changes in the traffic intensity. Therefore, rele

16、vant measured information on traffic intensities and qualities is needed. Different measurement periods and principles for collecting traffic data may have been used in different networks and services, depending on the operator. This solution leads, however, to overlapping data collecting and proces

17、sing, and increases the possibility of inconsistencies. This Recommendation presents some principles which facilitate collecting and handling of data for different purposes, in different networks and services, run by several operators. This Recommendation addresses traffic reference period for monit

18、oring GOS. Because dimensioning methods should be consistent with GOS monitoring, traffic reference periods defined here should also be used for dimensioning purposes. In the event that the definitions in this Recommendation conflict with previous Recommendations, this one shall prevail. 5 Principle

19、s Measurements can be alternatively continuous, scheduled, activated manually, or depend on observed values automatically. Values collected in continuous measurements are prehandled at an early stage. Scheduled measurements are motivated if the traffic variations are regular and predictable. Many ra

20、re measurements are started manually. Automatic measurements save from collecting unnecessary data and from continuous observations by operations people. Reporting can be started when the measured data exceeds a preset value. In order to avoid separate measurement operations for each network, each s

21、ervice and each action taken, the measurement principles and data should be applied consistently and one common database used for ail purposes in a given network, the data processing only varying case by case. Data collecting should be minimized, so that this administrative work does not unnecessari

22、ly load the control processors, data handling and reporting systems of the network. Recornmendation E.492 (OU96) 1 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesThere are three basic types of traffic load that are considered in networ

23、k dimensioning and monitoring GOS. For control devices, (e.g. exchanges) call attempts are considered, for traffic carrying devices, (e.g. circuit-groups) carried traffic intensity is considered, and for other aspects, (e.g. billing) the completed call attempts and their durations are considered. Tr

24、affic volume periods are defined separately for each of these types of traffic load. 6 Operations From the point of view of different operations, various traffic properties are relevant. Operations affecting the quality of service, like planning, dimensioning, forecasting, or fault detection, need p

25、eak values of the traffk measured even during short lengths of time. For optimizing, but especially for invoicing, accumulated values over longer periods are needed. The long-term prognoses form the basis for planning, the short-term prognoses for network management. 7 Measurement seasons and days T

26、raffk intensity varies irregularly during a year and it is not common for the highest loads to occur in the same weeks from one year to another. The lowest load season can be easier to predict. What is said about seasonal variations is valid also for individual days. Even if the weekdays can have re

27、peated similarities from week to week, the predictability of the highest intensities per day is often poor. The low intensities are mostly found at weekends or other holidays but, due to many special reasons, some of these days can be the most loaded ones, too. Therefore, the highest loads can be fo

28、und only by measuring the traffic continuously, interrupting the work only for very good reasons. Such reasons can be network operations in order to clear a network overload, reprogramming of the processor, augmentation procedures, or similar actions. Except for the first one, it is preferable to ca

29、rry out these operations during a predicted period with low load. 8 Combination of measured data Of all measurable traffic data, as described in Recommendation E.502, only those are recorded which are needed for further operations. Nevertheless, they may form an immense data quantity, not to be gath

30、ered unnecessarily, neither stored in its entirety. 9 Measurement hours In many cases the days peak hour can be found among the common office hours, but seldom during a fixed hour from day to day. Peak hours in the evening are usually caused by domestic calls, but sometimes by data traffic, too. Low

31、 evening or night tariffs encourage calling during those hours. Traffic measurements have to be continuous during the whole day so that the peak intensities can be found. 10 Read-out periods An important means to condense data is to summarize the phenomena over a certain length of time. Thus, data f

32、rom several calls are given as sum or average, integrated over this read-out period. The length of the read-out period has a decisive effect on the apparent size of traffic peaks, and to what extent they are damped by averaging with their neighbouring values. The read-out period has traditionally be

33、en one hour in manual telephony, corresponding from 10 to 20 times occupation time. For the purpose of discovering the relevant peak values, in actual automatic telephone traffic, but especially in signalling and data traffic with short occupation times, the read-out period has to be much shorter. T

34、he read-out period should be suitably chosen so that traffic variations and peaks within the read-out period can be determined using mathematical models and its measured average intensity. The recommended read-out periods for different networks and services are given in clause 13. 2 Recommendation E

35、.492 (O96) COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesITU-T RECMN*E.492 96 m 4862591 0636786 84b m 11 Reference periods for quality factors during the normal and high load The quality values indicate the service from the users poin

36、t of view. These values, like congestion, waiting time and fault factors, normally grow with increasing load. Therefore, the quality factor measurements are concentrated on the peak-load periods, in cases when this period can be foreseen. Since this is often not possible, the quality factors too, ar

37、e measured continuously or automatically. For certain purposes, the quality factors per circuit-group and individual components (e.g. exchanges) are defined for a normal and high load. The normal load is determined over a monthly time interval by the following steps: 1) 2) 3) determine the maximum r

38、ead-out period load of each day; order the days in a month from the lowest to highest daily high read-out period load; select the day having the fourth highest daily high read-out period load. This load is defined as the normal load for the monthly interval being considered). The high load is determ

39、ined by following steps 1) and 2) above and then selecting the day having the second highest daily peak read-out period. This load is defined as the high load for the monthly interval being considered. The first highest monthly load is not used here, since it can be caused by extreme traffic circums

40、tances or fault conditions. The purpose of identifying the normal and high load as defined above is to select which day and read-out period to use, save and analyse monitored GOS performance and compare the monitored values to the GOS target values specified for normal and high load. The GOS measure

41、ments used are those collected for the day and read-out period in which the network normal and high load occur. It should be noted that different types of network components could have different time periods at which normal and high load occur. 12 A circuit-switched network consists of several circu

42、it-groups and other interconnected network components for service control and signal transfer. Quality factors, relevant for the network, are monitored during normal and high load of the network, defined in the following way. The load is defined commonly for the whole network. In order to avoid infl

43、uence of the network structure, the load is seen from outside: traffic incoming to and originated by the network are summarized in each read-out period. The periods for normal and high load are defined by this total traffic, as in clause 8. The normal and high load above serve to define the monthly

44、reference periods for quality factors. Reference periods for network-wide quality factors 13 Different networks and services 13.1 PSTN The recommended read-out periods are 60 minutes and/or 15 minutes. 13.2 The reference periods for traffic caused by narrow-band ISDN and the IN services, like freeph

45、one, UFT and televoting, are for further study. N-ISDN and the IN-based services I) If there is more information available on the distribution of the peak daily traffic load, a day other than the fourth highest might be determined to be more appropriate. Recommendation E.492 (OY96) 3 COPYRIGHT Inter

46、national Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling Services13.3 The traffk measurements for SS No. 7 loads should be collected continuously for read-out periods of between 5 and 15 minutes. The exact value depends on measured traffic variability, as discussed in

47、 2.4E.733. The peak value of this measurement should be recorded each day for each load set (e.g. a load set could be a link-set load, a point-to-point load, an aggregate STP load, etc.). For network dimensioning, a sliding window of M days is considered and the reference traffic load over a window

48、is defined as the average of the N highest daily peak measurements over those M days. This definition of reference traffic is based on the philosophy of the ADPH (Average of Days Peak Hours) method recommended in Recommen- dation ES00 (Rev. 1). Recommended values for M and N are provided in 2.3E.733

49、. Special measurement studies must be done periodically to determine a factor K to multiply the measured peak load to determine the peak value to be used for dimensioning. The factor K reflects burstiness and short-term load variations that are not captured by the load data from the continuous measurement periods. The methods of determining K are given in 2.4E.733. Signalling System No. 7 (SS No. 7) 13.4 B-ISDN The traffic measurements for B-ISDN loads should be handled as mentioned in 13.3 concerning SS No. 7. However, for B-ISDN there may be services having traffk with th