ITU-T 建议书 G.1081

IPTV性能监测点 Performance monitoring points for IPTV

Summary

Successful deployment of IPTV servicesrequires performance parameters to be monitored at a number of different pointsin the complete end to end chain, including the customer premises, keyaggregation points and at interconnect points between disparate and
serviceprovider network domains. This Recommendation defines five monitoring pointswhere such performance measurements can be made.

Keywords

IPTV,performance, QoS, QoE, monitoring points

1. 范围 (Scope)

ThisRecommendation defines performance monitoring points which will allow theservice provider/network operator to monitor the performance of the completeIPTV service delivery to the end-user.

Successful deployment of IPTV servicesrequires performance monitoring at the customer premise (e.g. set-top-box), keyaggregation points (e.g DSL Access Multiplexer DSLAM) or cable modemtermination system (CMTS) and at interconnect points between disparate
networkdomains and service provider domain boundaries. Performance monitoring can helpin:

·        Finding errors in an end-to-endsystem (system debugging)

·        Checking the resourceutilization and the work load of system components

·        Comparing values (metrics)regarding performance of different system deployments

·        Providing a base for modellingthe system

·        Identifying system bottlenecks

·        Optimizing IPTV networkdeployment

·        Ensuring that systemperformance does not degrade with time.

The goal of performance monitoring is toprovide end-users of IPTV services with a high user experience by identifying,localizing and quantifying service and network issues.

2. 参考 (References)

Thefollowing ITU-T Recommendations and other references contain provisions, which,through reference in this text, constitute provisions of this Recommendation.At the time of publication, the editions indicated were valid. AllRecommendations and other references
are subject to revision; users of this Recommendationare therefore encouraged to investigate the possibility of applying the mostrecent edition of the Recommendations and other references listed below. A listof the currently valid ITU-T Recommendations is
regularly published.

Thereference to a document within this Recommendation does not give it, as astand-alone document, the status of a Recommendation.

[ITU-T Y.1540]          ITU-TRecommendation Y.1540 (2007), “Internet protocol data communication service –IP packet transfer and availability performance parameters,” Nov. 2007.

[ITU-T Y.1543]          ITU-T Recommendation Y.1543 (2007), “Measurements in IPnetworks for inter-domain performance assessment,” Nov. 2007.

[ITU-T Y.1544]          ITU-T Recommendation Y.1544 (2008), “Multicast IPperformance parameters,” .

3. 定义 (Definitions)

Platform          Ahardware and/or software architecture that serves as a foundation or base forrealising a certain functionality.

4. 缩写和首字母缩略词 (Abbreviations and acronyms)

本建议使用下列缩略语:

CMTS             Cable Modem Termination System 电缆调制解调器终端系统

DSLAM         DSL Access Multiplexer DSL接入复用器

NMS               NetworkManagement System 网络管理系统

OSS                 OperationsSupport System

QoE                 Qualityof Experience 体验质量

QoS                 Qualityof Service 服务质量

VoD                Videoon Demand 视频点播

5. 约定 (Conventions)

In this document:

The keyword “is recommended” indicates a requirement which isrecommended but which is not absolutely required.  Thus this requirement need not be present toclaim conformance.

The keyword “may” indicates a requirement which is optional.

6. IPTV性能监测点 (IPTV performance monitoring points)

The entire IPTV content delivery chain can be divided into multiple domains. Operators at domain bordershave the option to perform monitoring which, when taken together, forms anend-to-end monitoring topology.

This domain approach is independent of any specific monitoringmethod.

Monitored performance characteristics, across a single domain ormultiple domains, can be integrated with existing or new operations supportsystems (OSS)and/or network management system (NMS) systems.

Figure1/G.1081 – IPTV模型 (IPTV Domains)

The exact topology and domains will varyfrom one operator to another; however, monitoring can be applied at each domainboundary. An example topology with generalized domain boundaries is shown inFigure 1. These domains are further divided into specific monitoring
domains inFigure 2. Within each domain, different aspects can be monitored at each domainboundary as outlined below.

Figure2/G.1081 – IPTV性能监测点 (IPTV Performance Monitoring Points)

A complete performance monitoring system is recommended to include aperformance monitoring management platform to translate the measured data fromthe monitoring points into actionable knowledge. Functions of the managementplatform could include data storage,
analysis, correlation, faultidentification, root cause analysis, report generation and visualization. Therange of the management platform(s) may cover all domains as shown in Figure 2.

The interfaces between the performance monitoring managementplatform(s) and the monitoring points will be further defined in the future.

7. 性能监测点定义 (Performance monitoringpoint definitions)

This section provides a basic description of each monitoring point shown inthe previous section. The capabilities and parameters listed below are not anexhaustive list. Some parameters may be difficult to obtain in some scenarios.Conversely, there may be
some other parameters that are essential. These arestill under study.

7.1  监测点1 Monitoring point 1 – PT1

This point demarcates the domain borderbetween content provision and IPTV control. PT1 is located at the domain border between content providers (contentowners and aggregators) and IPTV Service provider.

PT1 enablesthe measurement of source audio-visual quality and metadata verification and theanalysis of information to be exchanged between content provider and IPTV serviceprovider.

PT1 may capture thefollowing information:

·        Coding parameters of video, audioand text content;

·        Quality parameters of video,audio and text content;

·        Acknowledgement for the report ofsource content transfer receipt;

PT1may support thefollowing capabilities:

·        Real-time request/responsetransactions by the protocols involved;

·        Real-time notifications ofasynchronous events;

·        Reliable and secure deliveryof  any messages involved;

·        Clock synchronization withother monitoring points;

·        Identification of variouscontent providers;

·        Report  testing information for quality parameters ofvideo audio and text content from various content providers to the service quality monitoring platform.

7.2 监测点2 Monitoring point 2 – PT2

This point is located at the domain borderbetween the service provider and network provider. It should aim for originalstreaming quality monitoring. PT2 monitors the service provider streamquality at the head-end egress.

PT2 may capture thefollowing information:

·        Quality parameters of streammedia from the core node of the service provider;

·        Performance parameters of EPGservers at the core node of the service provider;

·        Performance parameters of VODservers at the core node of the service provider;

·        Performance parameters of  service related  servers at the core node of service provider;

PT2 may support thefollowing capabilities:

·        Real-time request/responsetransactions by the protocols involved;

·        Real-time notifications ofasynchronous events;

·        Reliable and secure delivery ofany messages involved;

·        Clock synchronization withothermonitoring points;

·        Identification of variousservers;

·         Report information for quality parameters ofvideo, audio and text content and performance parameters of servers  to the  service quality monitoring platform.

7.3  监测点3 Monitoring point 3 – PT3

This point is located at the boundarybetween the IP core and IP edge networks for monitoring of IP-relatedperformance parameters.This point can be placed on any type of  interfacebetween the IPTV core network and the edge network.

PT3 may capture the following information:

·        Source network segment anddestination network segment to be measured;

·        IP network performance as definedin (ITU-T Y.1540]. Recommended methods of measurement are found in [ITU-T Y.1543].

o   Mean one-way delay

o   One-way packet delay variation

o   Packet loss ratio

o   Packet loss profile

o   Path unavailability

·        Multicast IP networkperformance parameters defined in [ITU-T Y.1544].

o   Successful join time

o   Successful leave time

o   Group mean one-way delay

o   Group IP service availability

o   Mean group loss ratio

PT3 may support the following capabilities:

·        Real-time request/response transactions;

·        Real-time notifications ofasynchronous events;

·        Reliable and secure delivery ofany messages involved;

·        Clock synchronization withother monitoring points;

·        Submission of r information forquality parameters of IP network to service quality monitoring platform

·        Access to raw IP information(e.g., packet headers, type of codec) of the audio-visual or text stream;

·        Able to capture information onquality originating from end-user devices.

7.4  监测点4 Monitoring Point 4 – PT4

This point is closest to the user wheremonitoring the quality of streaming, audio-visual quality, and IPTV serviceattributes areimportant. Monitoring at this point can be implemented byintroducing the performance monitoring function in Home Gateways and
STBs, forexample.

PT4 may capture the following information:

·        Source network segment anddestination network segment to be measured;

·        Access the service qualityinformation and stream media quality information of the IPTV service platformfrom edge point of IPTV;

·        Access to raw IP information(e.g., packet headers, type of codec) of the audiovisual or text stream;

·        IP network performance parametersdefined in [ITU-T Y.1540]. Recommended methods of measurement are found in [ITU-TY.1543].

o   Mean one-way delay

o   One-way packet delay variation

o   Packet loss ratio

o   Path unavailability

·        Multicast IP network performanceparameters defined in [ITU-T Y.1544].

o   Successful join time

o   Successful leave time

o   Group mean one-way delay

o   Group IP service availability

o   Mean group loss ratio

PT4 may be able to support the following capabilities:

·        Real-time request/response transactions;

·        Real-time notifications ofasynchronous events;

·        Reliable and secure delivery ofthe messages involved;

·        Clock synchronization withothermonitoring points;

·        Simulate the integrated serviceflow of IPTV terminal;

·        Report information for  parameters of IP network performance, servicequality that access IPTV service platform from edge point, and stream mediaquality to service quality monitoring platform.

7.5  监测点5 Monitoring point 5 – PT5

This point is at the final end-point anddirectly relates to end-user QoE. Monitoring audio-visual quality, textaccuracy and IPTV service attributes as perceived by the end-user areimportant.

PT5 may capture the following information:

·        Source network segment anddestination network segment to be monitored;

·        Access the quality informationof service and stream media of the IPTV service platform from the client;

PT5 may support the following capabilities:

·        Real-time request/response transactions;

·        Real-time notifications ofasynchronous events;

·        Reliable and secure delivery of any messages involved;

·        Clock synchronization withother monitoring points;

·        Integrated service informationof IPTV terminal;

·        Report information for  parameters of IP network performance, servicequality that access IPTV service platform from client, and stream media qualityto service quality monitoring platform.

8.  安全性考虑 (Security considerations)

Security aspects have not been addressed inthis Recommendation.

ITU-T G.1081 IPTV性能监测点 (Performance monitoring points for IPTV)的更多相关文章

  1. Linux System and Performance Monitoring

    写在前面:本文是对OSCon09的<Linux System and Performance Monitoring>一文的学习笔记,主要内容是总结了其中的要点,以及加上了笔者自己的一些理解 ...

  2. PostgreSQL Performance Monitoring Tools

    PostgreSQL Performance Monitoring Tools https://github.com/CloudServer/postgresql-perf-tools This pa ...

  3. 浏览器性能监控performance使用

    浏览器中有一个performance的性能监控,平时我也没有用到,接手了一个大数据的项目,发现页面打开的比较慢,使用浏览器的performance分析可以看到各个步骤花费的时间. 关于项目的性能分析如 ...

  4. 理解 OpenStack Swift (3):监控和一些影响性能的因素 [Monitoring and Performance]

    本系列文章着重学习和研究OpenStack Swift,包括环境搭建.原理.架构.监控和性能等. (1)OpenStack + 三节点Swift 集群+ HAProxy + UCARP 安装和配置 ( ...

  5. 怎么监视跟踪一个进程(Process)中的MS Unit Test DLL的详细性能(performance)【asp.net C#】

    Sample This tutorial will show how to instrument a unit test DLL for performance profiling. Visual S ...

  6. 基音检测算法的性能:Performance Evaluation of Pitch Detection Algorithms

    http://access.feld.cvut.cz/view.php?cisloclanku=2009060001 Vydáno dne 02. 06. 2009 (15123 přečtení) ...

  7. 浏览器性能接口performance.timing说明

    原文来自于 https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html 下图描述了该接口的各个时间 ...

  8. Language-Directed Hardware Design for Network Performance Monitoring——Marple

    网络监控困难 1.仅仅通过去增加特定的监控功能到交换机是不能满足运营商不断变化的需求的.(交换机需要支持网络性能问题的表达语言) 2.他们缺乏对网络深处的性能问题进行本地化的可见性,间接推断网络问题的 ...

  9. Windows Performance Monitoring with perfmon

    直接引用 - https://technet.microsoft.com/en-us/magazine/2008.08.pulse.aspx

随机推荐

  1. Android support library支持包常用控件介绍(一)

    谷歌官方推出Material Design 设计理念已经有段时间了,为支持更方便的实现Material Design设计效果,官方给出了Android support design library 支 ...

  2. Rxjava +Retrofit 你需要掌握的几个技巧,Retrofit缓存,RxJava封装,统一对有无网络处理,异常处理, 返回结果问题

    本文出处 :Tamic 文/ http://blog.csdn.net/sk719887916/article/details/52132106 Rxjava +Rterofit 需要掌握的几个技巧 ...

  3. 协议系列之UDP协议

    上节说的TCP协议虽然提供了可靠的传输,但是也有一个缺点,发送速度慢.那么有没有一种协议能快速发送的呢?这节要讨论的就是UDP协议,它提供了更加快的发送速度,但也牺牲了可靠性,它是一种无连接的传输协议 ...

  4. Android Multimedia框架总结(三)MediaPlayer中创建到setDataSource过程

    转载请把头部出处链接和尾部二维码一起转载,本文出自:http://blog.csdn.net/hejjunlin/article/details/52392430 前言:前一篇的mediaPlayer ...

  5. Android时遇到R.java was modified manually! Reverting to generated version!

    欢迎关注公众号,每天推送Android技术文章,二维码如下:(可扫描) 进入 eclipse后clipse Menu >Projects > clean 这么做就把R文件删了,但是别担心, ...

  6. 2.关于QT中的Dialog(模态窗口),文件选择器,颜色选择器,字体选择器,消息提示窗口

     1 新建一个空项目 A 编写 .pro文件 QT += gui widgets HEADERS += \ MyDialog.h SOURCES += \ MyDialog.cpp B 编写MyD ...

  7. Android之自定义AlertDialog和PopupWindow实现(仿微信Dialog)

    我们知道,在很多时候,我们都不用Android内置的一些控件,而是自己自定义一些自己想要的控件,这样显得界面更美观. 今天主要是讲自定义AlertDialog和popupWindow的使用,在很多需求 ...

  8. wincvs的“License for this product has expired”问题解决

    新入职的公司代码管理工具是CVS,使用wincvs作为客户端工具.今天发现执行login.logout.update等操作的时候总是报"License for this product ha ...

  9. Dynamics CRM2013/2015 Plugin注册工具Register New Assembly时无法看到注册按钮的解决办法

    CRM2013的注册插件工具UI相比2011之前有了一定的改变,但改变UI的同时也给开发人员带来了困扰,打开注册工具点击Register按钮选择dll时页面就是下面这样的,你完全看不到最下面的两个按钮 ...

  10. J2EE Exception:WELD-001408 Unsatisfied dependencies for type [SelectModelFactory] with qualifiers [@

    Issue: When you inject some resources using @Inject, you may encounter following exception after app ...