ETSI GS MOI 002-2012 Measurement Ontology for IP traffic (MOI) Requirements for IP traffic measurement ontologies development (V1 1 1)《IP流量的测量本体(MOI) IP流量测量本体的发展要求 版本1 1 1》.pdf

《ETSI GS MOI 002-2012 Measurement Ontology for IP traffic (MOI) Requirements for IP traffic measurement ontologies development (V1 1 1)《IP流量的测量本体(MOI) IP流量测量本体的发展要求 版本1 1 1》.pdf》由会员分享，可在线阅读，更多相关《ETSI GS MOI 002-2012 Measurement Ontology for IP traffic (MOI) Requirements for IP traffic measurement ontologies development (V1 1 1)《IP流量的测量本体(MOI) IP流量测量本体的发展要求 版本1 1 1》.pdf（31页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI GS MOI 002 V1.1.1 (2012-07) Measurement Ontology for IP traffic (MOI); Requirements for IP traffic measurement ontologies development Disclaimer This document has been produced and approved by the Measurement Ontology for IP traffic (MOI) ETSI Industry Specification Group (ISG) and represents

2、the views of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. Group Specification ETSI ETSI GS MOI 002 V1.1.1 (2012-07) 2Reference DGS/MOI-0002 Keywords IP, ontology, requirements, traffic ETSI 650 Route des Lucioles F-06921 Sophi

3、a Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The

4、 present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI pri

5、nters of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/

6、tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing res

7、triction extend to reproduction in all media. European Telecommunications Standards Institute 2012. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit o

8、f its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI GS MOI 002 V1.1.1 (2012-07) 3Contents Intellectual Property Rights 4g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g32.1 Normative references .

9、 5g32.2 Informative references 5g33 Abbreviations . 8g34 Framework of the Ontology for IP Measurements . 8g35 KPI Descriptions and Mapping to MOI . 9g35.1 Parameters Related to Delay or Delay Variation 10g35.2 Parameters Related to Errors and Losses . 11g35.3 Parameters Related to Packet Reordering,

10、 Replication and Duplication 11g35.4 Parameters Related to Connectivity and Service Availability 12g35.5 Throughput Related Parameters . 12g35.6 Operational Real-world KPIs . 13g36 Information Models Requirements for IP Traffic Monitoring Applications 13g36.1 Use Case Scenarios 13g36.1.1 IP Networks

11、 Characterisation . 14g36.1.2 QoS Measurements in IP Networks 14g36.1.3 Traffic Monitoring for Security Applications . 15g36.1.4 Autonomic Network Monitoring and Management 16g36.1.5 Law Enforcement 16g36.2 Requirements Derived from the Quality of Experience Concepts 17g36.3 Ontology Requirements to

12、 Support Business Management Applications 18g37 Additional Input for Privacy Protection Approaches . 19g38 Main Features and Global Requirements for MOI . 24g38.1 Data Types Support Requirements . 24g38.1.1 Requirements for Application-specific Data Types 25g38.2 Operational Requirements 26g38.3 Req

13、uirements for Integral Privacy Protection Provisions. 27g39 Ontology Architecture and Structure Requirements 28g39.1 Requirements of Expandability 28g39.2 Requirements of Interoperability 28g39.3 Requirements of Ontological Processing Performance 29g3Annex A (informative): Authors Essential, or pote

14、ntially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No

15、guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification (ISG) Mea

16、surement Ontology for IP traffic (MOI). Introduction Defining a complete set of concepts and their relationship to support coherent developments of traffic measurement systems needs not only an extensive mapping of key performance indicators (KPI), key quality indicators (KQI) and currently used par

17、ameters to describe IP networks, but a serious pre-definition of the framework and extension of the ontology to be set up. If it is true that ontologies should be complete and internally coherent, one ought to be aware of the final purpose of establishing such an ontology, namely supporting informat

18、ion systems to achieve IP traffic monitoring and quality of service (QoS) applications that can exchange information and back service level agreements (SLA) up and fulfil the expectations of customers by assuring the quality of experience (QoE). The present document starts setting up the limits to t

19、he ontology that needs to be defined for such purpose. Then, after reviewing the parameters that define IP networks, some use cases are used to analyse which internal specifications should be respected in order to give rise to a coherent ontology for IP traffic monitoring useful for practical purpos

20、es. ETSI ETSI GS MOI 002 V1.1.1 (2012-07) 51 Scope The present document identifies the requirements that should characterise an ontology for the semantic conceptualisation of information related to IP traffic measurements. The requirements are obtained through the analysis of use cases spanning acro

21、ss a variety of related application categories and domains of interest, as well as the consideration of additional qualitative needs, such as the protection of personal data. Additional inputs arise from user experience, as well as the GS/MOI-010 Work Item study, entitled “Report on information mode

22、ls for IP traffic measurement“ 1. The general difficulty of setting limits to an ontology, taking concepts from outside is also dealt within the present document that states MOI focus on IP traffic measurement concepts and lets side ontologies dealing with other subjects, an easy way to link. Thus a

23、 rather practical approach to define MOI ontology will be laid so that further QoS, traffic monitoring and Internet governance issues can be built on top of it by means of semantic tools. 2 References References are either specific (identified by date of publication and/or edition number or version

24、number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at

25、 http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are necessary for the application of the present document. 1 ETSI GS

26、 MOI 010: “Measurement Ontology for IP Traffic (MOI); Report on Information Models for IP Traffic Measurement“. 2.2 Informative references The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject are

27、a. i.1 FP7 ICT project MOMENT (Monitoring and Measurement in the Next Generation Technologies). NOTE: Available at http:/fp7-moment.eu/ i.2 FP7 ICT project PRISM (PRIvacy-aware Secure Monitoring). NOTE: Available at http:/fp7-prism.eu/ i.3 FP7 ICT project DEMONS (DEcentralized, cooperative, and priv

28、acy-preserving MONitoring for trustworthiness). NOTE: Available at http:/fp7-demons.eu/ i.4 IETF RFC 2330: “Framework for IP Performance Metrics“. i.5 ITU-T Recommendation Y.1561: “Performance and Availability Parameters for MPLS Networks“. i.6 ITU-T Recommendation Y.1540: “Internet protocol data co

29、mmunication service - IP packet transfer and availability performance parameters“. i.7 IETF RFC 2679: “A One-way delay Metric for IPPM“. i.8 ITU-T Recommendation Y.1544: “Multicast IP performance parameters“. ETSI ETSI GS MOI 002 V1.1.1 (2012-07) 6i.9 IETF RFC 5644: “IP Performance Metrics (IPPM): S

30、patial and Multicast“. i.10 IETF RFC 3393: “IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)“. i.11 ITU-T Recommendation Y.1543: “Measurements in IP networks for inter-domain performance assessment“. i.12 IETF RFC 2681: “A Round-trip Delay Metric for IPPM“. i.13 IETF RFC 2680: “A O

31、ne-way Packet Loss Metric for IPPM“. i.14 IETF RFC 3357: “One-way Loss Pattern Sample Metrics“. i.15 IETF RFC 4737: “Packet Reordering Metrics“. i.16 IETF RFC 5560: “A One-Way Packet Duplication Metric“. i.17 IETF RFC 3148: “A Framework for Defining Empirical Bulk Transfer Capacity Metrics“. i.18 IE

32、TF RFC 2678: “IPPM Metrics for Measuring Connectivity“. i.19 ITU-T Recommendation Y.1540 Amendment 1. i.20 IBM, “Understanding the Autonomic Manager Concept“. NOTE Available at http:/ i.21 D. E. Monnat, A. L. Ethen, “A Primer on the Federal Wiretap Act and Its Fourth Amendment Framework“, Journal of

33、 the Kansas Trial Lawyers Association, Vol. 28, No. 1, pp. 12-15, 2004. i.22 Council of the European Union, “Council Resolution of 17 January 1995 on the lawful interception of telecommunications“, Official Journal of the European Communities, No. C 329, pp. 1-6, November 1996. i.23 ETSI TS 102 233:

34、 “Lawful Interception (LI); Service specific details for E-mail services“. i.24 ETSI TS 102 234: “Lawful Interception (LI); Service-specific details for internet access services“. i.25 ETSI TS 102 656: “Lawful Interception (LI); Retained Data; Requirements of Law Enforcement Agencies for handling Re

35、tained Data“. i.26 ETSI TS 102 232-1: “Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery“. i.27 A. Zugenmaier and J. Claessens, “Privacy in Electronic Communications“, in Network Security: Current Status an

36、d Future Directions, C. Douligeris these include the retention of certain data for ensuring their availability if needed for the investigation, detection and prosecution of serious crimes, as well as the performance of Lawful Interception. Different monitoring tools and platforms have been developed

37、 through the years to obtain active and passive measurements about a variety of metrics. The integration of such measurements can be valuable for network operators to obtain network weathermaps or network tomographies. However, this integration in a single view is difficult because each platform use

38、s its own data structures and its own interaction interfaces. ETSI ETSI GS MOI 002 V1.1.1 (2012-07) 9Ontologies can become very useful for the conceptual integration of the different measurement data models. Dealing with the underlying information at a semantic level can enable some degree of infere

39、nce and automatic reasoning over the retrieved measurement data. At the same time, ontologies let define the information at different abstraction levels, allowing the definition of specific classes of measurements that are derived from generic ones. The present document focuses on this approach, app

40、lying the concepts provided by ontologies to address the integration of measurement information from a semantic viewpoint. The MOI ontology has to describe the set of concepts, properties, relationships and axioms in the domain of Internet Network Measurements. In that respect, it is very important

41、to define the limits of the ontology, and also set connections to other already defined and globally accepted ontologies. Given that the network measurement domain is very broad, it is important to be pragmatic, avoiding very large models that are difficult to apply in a real use case. For this, the

42、 ontology will be focused on what can be measured in an Internet Network; Quality of Service (QoS) and Quality of Experience (QoE) will be essential parts of this ontology, whereas special focus will be put on the critical issue of personal data protection as an integral part of the ontology. Other

43、concepts will be taken from other existing ontologies, to a some extent investigated in 1. Other general concepts are also available in already defined network management information models such as the CIM model, SNMP MIBs or ITU M.3100. The work presented here is supported by three European researc

44、h projects. The aim of the FP7 ICT MOMENT i.1 was precisely to find ways to solve the integration problem. This integration was twofold: definition of a standard interface to access the information, as well as definition of a homogeneous view of the available information. For the latter integration,

45、 it was necessary to combine database schemas of the existing network measurement infrastructures, and leverage existing definitions from PerfSONAR, CAIDA, IPPM IETF WG, etc. On the other hand, FP7 ICT PRISM i.2focused on the issue of privacy protection in the context of passive network monitoring;

46、a fundamental activity has been the specification of a semantic model. Finally, this work is supported by the FP7 ICT DEMONS i.3; it focuses on distributed and cooperative network monitoring for fulfilling a variety of objectives mostly centered around security, while it continues the work of PRISM

47、with respect to personal data protection leveraging semantic technologies. Next clauses investigate the requirements that should drive the development of the MOI ontology. A few representative use cases where the MOI ontology can be used are provided, while information domains and types that should

48、be specified in the ontology, such as Key Performance Indicators (KPI), are outlined. Moreover, in order to cope with the personal data protection aspects, the underlying principles are also investigated. As a result, the set of requirements of the ontology are defined, specifying both main features

49、 and global requirements, as well as the requirements for the ontology structure. 5 KPI Descriptions and Mapping to MOI Operators and private network managers require tools to manage the network, prevent and detect problems, plan and engineer sections. The Key Performance Indicators (KPI) serve the purpose of quantifying metrics that reflect factors critical for the correct network behaviour in the sense of operational and/or business objectives. They help