ITU-T Z 336-1988 TRAFFIC MEASUREMENT ADMINISTRATION《通信量测量管理》.pdf

《ITU-T Z 336-1988 TRAFFIC MEASUREMENT ADMINISTRATION《通信量测量管理》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Z 336-1988 TRAFFIC MEASUREMENT ADMINISTRATION《通信量测量管理》.pdf（40页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION)45G134 : TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU-!.G13-!#().%G0G0,!.5!%42!2) measurement dependent time parameters (e.g. time parameters which define the periodicity ofmeasurement);3) measurement independent time parameters (e.g. time parameters which are

2、related to the actual start or stopof a certain measurement in activation and deactivation functions).4.2 Traffic measurement structureA traffic measurement (in the following called measurement) consists of: measurement set information, time information, output routing and scheduling information (ou

3、tput parameters).Measurement set information, time information, output routing and scheduling information may be completelyor partially pre-defined (initially provided by the supplier but changeable via MML inputs) or fixed (not changeable viaMML inputs). The MML functions described for traffic meas

4、urements administration are intended to be supported tothe extent that there is a need for user manipulation of the identified information items.If some of this information is fixed in a system, the relevant MML functions may not be provided in thatsystem._1)Sampling interval, the time interval betw

5、een two consecutive samplings.4 Fascicle X.7 - Rec. Z.3364.2.1 Measurement set informationMeasurement set information consists of one or several selected measurement types with defined objects(object lists) and measurement type dependent parameters (e.g. sampling interval, number of events of a cert

6、aincategory, destination codes, etc.).Note that for traffic measurement administration purposes measurement types are fixed at a given moment intime and they cannot be created, deleted or changed by MML commands; these measurement types may be changedonly later by supplier releases according to new

7、requirements. It is recognized that administrations may require MMLfunctions to administer measurement types, grouping predefined entities of object types. Such functions should beconsidered as system extension and upgrade functions and, therefore, they should belong to the system controlfunctional

8、area. However, due to the fact that system control functions will not be inserted in the presentRecommendations, they are described hereafter.4.2.2 Time informationMeasurements of types A and B may involve continuous recording or recording on predetermined days(recording days).For measurements perfo

9、rming continuous recording only the start data is needed.For recording on predetermined days, these days are determined on a periodical basis (periodicity pattern) incase of measurements of undetermined duration. For measurements of predetermined duration, the recording days aredetermined on a perio

10、dical basis or on a non-periodical basis (dates of recording days). These possibilities aresummarized in Figure 4/Z.336.Time data are defined at three main levels, as shown in Figure 5/Z.336.Measurement level contains information about either: dates of recording days (in case of a non-periodical mea

11、surement). The start and stop date of themeasurement are implicitly defined by the dates of the first and the last recording day. No activationfunction may be needed in this case; periodicity pattern (in case of periodical measurement) of recording and non-recording days.Recording day level contains

12、 information about the start time and stop time for the recording periods within arecording day (e.g. from 09 to 12 and from 15 to 17). No overlap of recording periods is allowed for the samemeasurement.Recording period level contains information about the periodicity of the data collection based on

13、 the resultaccumulation period. The result accumulation period is the time interval within a recording period during which therequired measurement entities are processed and at the end of which results are stored for immediate or later output(e.g. 15 minutes). The result accumulation period can be s

14、horter than the recording period; in that case more than oneset of data is collected for each of the recording periods to be routed toward the output media according to the resultsoutput schedule.Fascicle X.7 - Rec. Z.336 55 Additional information5.1 Measurement output contents and proceduresActivat

15、ion of a traffic measurement causes the output of measurement results with the following procedures.The produced output is routed toward the media specified in the output routing list associated to themeasurement, e.g. printers, magnetic tapes, data links, system output files, etc. The output is mad

16、e according to theoutput schedule.The measurement results output is done according to time data related to the measurement. A measurementresults output is made with the following logical blocks:a) a “begin block” which contains measurement data, parameters i.e. measurement types data, time data,outp

17、ut data and data of interest related to the exchange configuration;b) one or more “result blocks”, one for each result output period, which contain the measurement results;c) an “end block” which contains a general summary about the performance of the measurement, i.e. numberof result blocks, number

18、 of interruptions of the measurement and the causes of the deactivation of themeasurement (scheduled or forced).If during the performance of the measurement, the measurement is suspended (e.g. due to a system crash) themeasurement results output could be continued after the system restart with a new

19、 output of the begin block. Thiscontinuation may be accomplished automatically by the system or by user action. The system should notify the user viaan output if the latter case applies.The relationship between time data for the result accumulation period and time data defining the results outputsch

20、edule is system or even measurement dependent and it is not considered herein.5.2 Simplification of traffic measurement administrationIt is recognized that, for particular applications, there may not be an interest in administering the data base oftraffic measurements. Consequently, the only MML fun

21、ctions needed are activation and deactivation functions.In such cases, in order to ease the operators work, the association between the measurement and the objectsmay be made when activating the measurement itself, provided that the association is unambiguous.6 Glossary of used termsRecordingPerform

22、ance of the operations implied by the measurement entities in order to collect the required data.6 Fascicle X.7 - Rec. Z.336recording dayDay when a recording is performed. Several recording periods are allowed within a recording day. No overlapof recording periods is allowed for the same measurement

23、. Each recording period can have a different length.start dateStart day for the measurement execution.stop dateStop day for the measurement execution.periodicity patternA pattern which indicates which days are recording (or results output) days and which are not. The start daypositions this time spa

24、n. Once activated, the execution of the measurements (or of the results output) is performedaccording to this pattern, until disabled by a deactivation command.start timeTime for beginning the recording period in a recording day.stop timeTime for terminating a recording period in a recording day.rec

25、ording periodA period of recording during a recording day.results accumulation periodTime interval within a recording period during which the required measurement entities are processed and atthe end of which results are stored for immediate or later output.output parametersData determining output r

26、outing and scheduling.results output routingData defining the media to which results output is to be directed.results output scheduleData specifying a set of days (or a periodicity pattern) and of times during these days when the output of theresults is to be made.ANNEX A(to Recommendation Z.336)Lis

27、t of system functions to be controlled by MML and list of jobsA.1 List of system functions to be controlled by MML1) Performing traffic measurements.2) Scheduling traffic measurements execution and results output.3) Managing measurements data.4) Retrieving measurements data.Fascicle X.7 - Rec. Z.336

28、 7A.2 List of jobs1) To create new measurements or measurement components and to modify old ones, by defining the entitiesto be measured and the objects and parameters of the measurements themselves (what and how tomeasure): the purpose of this job is to create and/or modify a set of data which is u

29、sed by the system to perform ameasurement in a given way; the system is supposed to record the set of data of the measurement, and to check their staticcorrectness; the user is supposed to input/change all relevant data. The modification of data may be performed bymeans of different procedures, depe

30、nding whether or not those data are related to activatedmeasurements; the complexity of the job could be high depending on the amount of data to be input; the frequency of the job is low; the job is supposed to be performed at exchange and/or OMC level.2) To delete obsolete measurements or measureme

31、nt components: the purpose of the job is to delete measurement of no further use or measurement components to releasethe employed resources; the system is supposed to delete the data related to a specified measurement if the measurement is notactive. The system is supposed to delete a measurement co

32、mponent only if it is not an activemeasurement component; the user is supposed to input the identities of measurements or measurement components to be deleted; the complexity of the job is low; the frequency of the job is low; the job is supposed to be performed at exchange and/or OMC level;3) To de

33、fine the measurement results output routing and scheduling (where and when the results will beoutput): the purpose of the job is to define where the measurement outputs have to be routed to and when theyshould be output; the system has to route the measurement outputs toward the recording media or t

34、oward other systemsspecified, according to the results output schedule; the user has to input the identity of the destination of the output and the results output schedule to befollowed by the system; the complexity of the job is low; the frequency of the job is medium; the job may be performed at e

35、xchange and/or OMC level.4) To activate and to deactivate measurements (when to measure): the purpose of the job is to activate and/or deactivate the performance of the measurements that havebeen previously defined; the system is supposed to activate and/or deactivate a measurement and to start the

36、production of theresults; the user is supposed to input the date and time of activation and/or deactivation; the complexity of the job is low; the frequency of the job is medium; the job may be performed at exchange and/or OMC level.5) To retrieve different kinds of information related to traffic me

37、asurements: the purpose of the job is to get information on measurements previously input in the system(s) in orderto be aware of the current situation; the system is supposed to output in suitable formats and on the selected device(s) the informationrequested; the user is supposed to input the iden

38、tity of the items to be interrogated and to select retrieving criteria; the complexity of the job is low;8 Fascicle X.7 - Rec. Z.336 the frequency of the job is medium; the job may be performed at exchange and/or OMC level.ANNEX B(to Recommendation Z.336)Guidelines for the list of MML functionsand a

39、ssociated information structure diagramsB.1 IntroductionThis Annex contains guidelines for the list of MML functions and associated information structure diagramsrelated to the routing administration model defined in Recommendation Z.336, 4.B.2 List of MML functionsThis list contains possible MML fu

40、nctions for traffic measurement administration. Those functions dealing withinformation (e.g. measurement set, time data list, etc.) that is fixed in a system are not relevant for that system.This list is not mandatory nor complete, it may vary according to Administration needs, telecommunicationnet

41、work levels, regulatory needs, etc.These MML functions do not represent the actual command structure of any real implementation of the man-machine interface. Each of the MML functions identified can be implemented by providing one or more separatedistinctive commands or several MML functions could b

42、e implemented by using a single command.1) Creation create a measurement; create a measurement set; create an object list; create a time data list; create an output routing list; create a result output schedule.2) Deletion delete a measurement; delete a measurement set; delete an object list; delete

43、 a time data list; delete an output routing list; delete a result output schedule.3) Activation activate a measurement.4) Deactivation deactivate a measurement.5) Interrogation interrogate a measurement; interrogate a measurement set; interrogate a measurement type; interrogate an object list;Fascic

44、le X.7 - Rec. Z.336 9 interrogate a time data list; interrogate an output routing list; interrogate a result output schedule.6) Changing change a measurement; change a measurement set; change an object list; change a time data list; change an output routing list; change a result output schedule.7) A

45、dministration of measurement types create a measurement type; delete a measurement type; change a measurement type.B.3 Information structure diagramsThe information entities needed for the MML functions previously defined have been identified and arereported in this section by means of diagrams repr

46、esenting each MML function information structure (Figures from B-2/Z.336 to B-41/Z.336). In particular, the information structure diagrams of the measurement outputs are given inFigures from B-42/Z.336 to B-45/Z.336.An overview of the measurement data structure is also given in Figure B-1/Z.336.The

47、metalanguage used is defined in Recommendation Z.333.10 Fascicle X.7 - Rec. Z.336 Fascicle X.7 - Rec. Z.3361112 Fascicle X.7 - Rec. Z.336 Fascicle X.7 - Rec. Z.336 13 14 Fascicle X.7 - Rec. Z.336 Fascicle X.7 - Rec. Z.336 15 16 Fascicle X.7 - Rec. Z.336 Fascicle X.7 - Rec. Z.336 17 18 Fascicle X.7 - Rec. Z.336 Fascicle X.7 - Rec. Z.336 19 20 Fascicle X.7 - Rec. Z.336