1、 International Telecommunication Union ITU-T H.248.87TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2014) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSInfrastructure of audiovisual services Communication procedures Gateway control protocol: Guidelines on the use of ITU-T H.248 capabilities for p
2、erformance monitoring in RTP networks in ITU-T H.248 profiles Recommendation ITU-T H.248.87 ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS H.100H.199 INFRASTRUCTURE OF AUDIOVISUAL SERVICES General H.200H.219 Transmission multiplexing and
3、 synchronization H.220H.229 Systems aspects H.230H.239 Communication procedures H.240H.259Coding of moving video H.260H.279 Related systems aspects H.280H.299 Systems and terminal equipment for audiovisual services H.300H.349 Directory services architecture for audiovisual and multimedia services H.
4、350H.359 Quality of service architecture for audiovisual and multimedia services H.360H.369 Supplementary services for multimedia H.450H.499 MOBILITY AND COLLABORATION PROCEDURES Overview of Mobility and Collaboration, definitions, protocols and procedures H.500H.509 Mobility for H-Series multimedia
5、 systems and services H.510H.519 Mobile multimedia collaboration applications and services H.520H.529 Security for mobile multimedia systems and services H.530H.539 Security for mobile multimedia collaboration applications and services H.540H.549 Mobility interworking procedures H.550H.559 Mobile mu
6、ltimedia collaboration inter-working procedures H.560H.569 BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629 Ubiquitous sensor network applications and Internet of Things H.640H.649 IPTV
7、 MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV General aspects H.700H.719 IPTV terminal devices H.720H.729 IPTV middleware H.730H.739 IPTV application event handling H.740H.749 IPTV metadata H.750H.759 IPTV multimedia application frameworks H.760H.769 IPTV service discovery up to consumption H.770H.
8、779 Digital Signage H.780H.789 E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS Interoperability compliance testing of personal health systems (HRN, PAN, LAN and WAN) H.820H.849 Multimedia e-health data exchange services H.860H.869 For further details, please refer to the list of ITU-T Recommendations.
9、 Rec. ITU-T H.248.87 (01/2014) i Recommendation ITU-T H.248.87 Gateway control protocol: Guidelines on the use of ITU-T H.248 capabilities for performance monitoring in RTP networks in ITU-T H.248 profiles Summary Recommendation ITU-T H.248.87 provides guidelines on the use of performance monitoring
10、 tools for real-time transport protocol (RTP) traffic in ITU-T H.248 profiles. Such tools are related to RTP control protocol (RTCP) reports and the use of the ITU-T H.248-based gateway control interface for configuring measurement, filtering and reporting activities. These profile guidelines may be
11、 used by other standards developing organizations (SDOs) when defining their ITU-T H.248.1 profiles in support of ITU-T H.248 procedures and packages related to RTP bearer traffic with associated RTCP reports. History Edition Recommendation Approval Study Group Unique ID*1.0 ITU-T H.248.87 2014-01-1
12、3 16 11.1002/1000/12061-en _ *To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T H.248.87 (01/2014) FOREWORD The International Tel
13、ecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and
14、tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide 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 Rec
15、ommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 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 Recom
16、mendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoper
17、ability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that c
18、ompliance with the Recommendation is required of any party. 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, vali
19、dity or applicability 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 requ
20、ired to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2014 All rights reserved. No part of this publication may be reproduc
21、ed, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.248.87 (01/2014) iii Table of Contents Page 1 Scope 1 1.1 Framework and layout of this Recommendation 2 2 References. 4 3 Definitions 5 3.1 Terms defined elsewhere 5 3.2 Terms defined in this Recommendation . 5 4
22、Abbreviations and acronyms 6 4.1 Indices . 7 5 Conventions 8 5.1 Prescriptive language for requirements specification . 8 6 Relation to other ITU-T H.248.x-series Recommendations . 8 6.1 ITU-T H.248.30: RTCP extended performance metrics packages 8 6.2 ITU-T H.248.48: RTCP XR block reporting package
23、. 8 6.3 Expired proposal ITU-T H.248.xnq: Gateway control protocol: Extended network quality metrics packages for next generation networks (NGNs). 8 7 Classification of performance metrics 8 8 Roles provided by MG . 9 8.1 ITU-T H.248 MG as general measurement point (MP) . 11 8.2 ITU-T H.248 MG as lo
24、cation-dependent measurement point (MP) 11 8.3 ITU-T H.248 MG as collection point (CP) 12 8.4 ITU-T H.248 MG as reporting point at IP bearer interface (RPRTCP) 12 8.5 ITU-T H.248 MG as reporting point at an ITU-T H.248 interface (RPH.248) 12 8.6 ITU-T H.248 MG as filtering point (FP) (for RTCP traff
25、ic) 13 8.7 ITU-T H.248 MG as loopback point (LP) (for RTP/RTCP traffic) . 14 8.8 Support of specific RTP topologies 14 9 ITU-T H.248 profile specification guidelines 14 9.1 Profile identification . 15 9.2 Summary . 15 9.3 Gateway control protocol version 15 9.4 Connection model . 15 9.5 Context attr
26、ibutes 15 9.6 Terminations . 15 9.7 Descriptors 15 9.8 Command API 17 9.9 Generic command syntax and encoding . 18 9.10 Transactions 18 9.11 Messages . 18 iv Rec. ITU-T H.248.87 (01/2014) Page 9.12 Transport . 18 9.13 Security . 18 9.14 Packages . 18 9.15 Mandatory support of SDP and ITU-T H.248.1 A
27、nnex C information elements 22 9.16 Optional support of SDP and ITU-T H.248.1 Annex C information elements 23 9.17 Procedures 23 Appendix I Example use cases for ITU-T H.248-based performance monitoring in RTP networks 25 I.1 Overview 25 I.2 Use case 1: ITU-T H.248 MG with connection model (RTP non-
28、RTP) e.g., trunking gateway 25 I.3 Use case 2: IP-IP H.248 MG and remote SIP UE Single control plane RP by MG . 26 I.4 Use case 3: IP-IP ITU-T H.248 MG and remote SIP UE Single control plane RP by UE 27 I.5 Use case 4: IP-IP ITU-T H.248 MG and remote SIP UE Single location of MPs (“LP by MG“) 29 I.6
29、 Use case 5: Distributed control plane reporting with near-end measurements only (at the example of a trunking gateway) 30 I.7 Use case 6: IP-IP ITU-T H.248 MG as peering node . 32 I.8 Use case 7: Multiple IP network domains Segment-based measurements 32 I.9 Use case 8: MP relocation by loopbacking
30、34 Appendix II Design of the expired extended network quality base (XNQ) package . 36 II.1 Introduction 36 II.2 Extended network quality base package . 36 Appendix III Example performance metric types . 41 III.1 Background . 41 III.2 Transport level metrics . 41 III.3 Application level metrics 42 Ap
31、pendix IV Relationship between IETF RTCP XR documents and ITU-T H.248.x items and Recommendations 43 IV.1 Background . 43 IV.2 Capabilities versus ITU-T H.248.x packages support 46 Appendix V Use case specific capability sets Two examples . 48 V.1 Overview 48 Bibliography. 50 Rec. ITU-T H.248.87 (01
32、/2014) 1 Recommendation ITU-T H.248.87 Gateway control protocol: Guidelines on the use of ITU-T H.248 capabilities for performance monitoring in RTP networks in ITU-T H.248 profiles 1 Scope The scope of this Recommendation covers performance monitoring in RTP networks with the involvement of ITU-T H
33、.248 entities. Performance monitoring as such is a network service across multiple network entities which are located in user, control and/or management planes. The scope of this Recommendation is limited to the user/control/management plane interfaces of ITU-T H.248 entities. The notion of performa
34、nce monitoring is used to emphasize a call/session dependent service, which is basically in contrast to the legacy performance management capability, which is a pure management plane function (see ITU-T M.3010 and ITU-T M.60). Performance monitoring could be considered as a network overlay function.
35、 This Recommendation provides: an overview of the existing “entire ITU-T H.248 toolkit“ for RTCP extended report (XR) support, i.e., the set of available ITU-T H.248 packages in that area an overview of available ITU-T H.248 packages for non-XR related performance metrics, typically subject to RTCP
36、basic report (SR, RR) capabilities example network use cases with different ITU-T H.248 MG types (primarily physical-to-RTP gateways, media-agnostic IP-to-IP gateways, RTP-topology-aware RTP-to-RTP gateways) a collection of functional requirements in order to motivate associated profile guidelines a
37、 classification of performance metrics (such as application-level versus transport-level metrics) in order to indicate applicability or not for ITU-T H.248 MGs the following principal ITU-T H.248 MG tasks: measurement of RTP traffic reporting of measurement data via RTCP XR reports collection of RTC
38、P XR carried measurement data loopback of RTP (in order to relocate a measurement point) filtering of RTCP XR reports modification of RTCP XR reports and/or reporting of measurement data via ITU-T H.248 statistics to the MGC control of such tasks via ITU-T H.248 that could be addressed in an ITU-T H
39、.248 profile, i.e., the identification of appropriate ITU-T H.248 packages the detailed specification of package usage the example call-dependent procedures the association to other related ITU-T H.248.x Recommendations such as ITU-T H.248.71, ITU-T H.248.79, ITU-T H.248.85 and b-ITU-T H.248.88 cont
40、rol of measurement methods (such as interval, cumulative and alert type of measurements) usage of ITU-T H.248.47-based conditional reporting ITU-T H.248.47. 2 Rec. ITU-T H.248.87 (01/2014) This Recommendation also discusses the purpose of performance monitoring (and therefore the possible motivation
41、 of a use case). For example: capture of grade-of-service (GoS) related data in order to evaluate network conditions capture of quality of service (QoS) and quality of experience (QoE) related data in order to evaluate service conditions (e.g., as part of service level agreements) capture of billing
42、/charging related data capture of data as input for routing algorithms capture of data as input for network node selection algorithms capture of data as input for centralized servers as support of network operations capture of data as part of online tests. 1.1 Framework and layout of this Recommenda
43、tion The scope, purpose, structuring principle and framework of this Recommendation are summarized in Figure 1. The primary audience of this Recommendation are authors of ITU-T H.248 profile specifications, which aim to support a particular network performance monitoring use case, and the considerat
44、ion of a specific location and/or type of an ITU-T H.248 MG. Performance monitoring support could affect three areas of an ITU-T H.248 profile: 1. basic protocol capabilities (such as connection model); 2. packages and their detailed usage; and/or 3. call-dependent procedures. This Recommendation pr
45、ovides guidelines for these profile areas. Typically to define an ITU-T H.248 profile there are several steps that are followed, according to Figure 1, given by: 1. Requirements stage: selecting use case(s) and the identification of required MG behaviour in terms of measurements, reporting, filterin
46、g, etc. capabilities; 2. Protocol stage: addressing the necessary templates of the indicated profile areas and recommended input; and 3. Profile stage: incorporating “guidelines“ in an actual profile specification and adapting the templates to the concrete specification setting. Rec. ITU-T H.248.87
47、(01/2014) 3 H.248.87(14)_F01ITU-T H.248 profile specification1) Basic protocol capabilities Protocol version: Connection model: (RTP topology) Context attributes Terminations: (“RTP“, “IP“) Descriptors Command API Encoding Transactions Messages Transport SecurityProfile specification guidelines (thi
48、s Recommendation)C1) Basic protocol capabilities: (RTP topology): (“RTP“, “IP“) Protocol version: Context attributes Descriptors Command API Encoding Transactions Messages Transport Security Connection model TerminationsC2) Packages: 2) Packages: Overview Overview Call-independent procedures Call-in
49、dependent procedures Measurement related procedures Measurement related procedures Reporting-related procedures Reporting-related procedures Filtering-related procedures Filtering-related procedures Loopback-related procedures Loopback-related procedures3. MG behaviour4. Use case determinesprotocol requirements5. Generic profile elements (tool kit)6. mapped i
