ITU-T H Series Recommendations: New Documents

[ H.Sup4 (12/11) ] - Repository of generic parameters for ITU-T H.460.x sub-series Recommendations

sam, 10 f�v 2012 15:05:42 GMT

Summary

Supplement 4 to the H-series of ITU-T Recommendations lists generic parameters assigned in the ITU-T H.460.x series Recommendations. Its purpose is to provide a quick reference to those parameters. This revision of Supplement 4 adds parameters that have been defined in the new Recommendations of the ITU-T H.460.x series since the previous edition of this supplement was published.

This revision adds feature identifiers for H.460.23 Amendment 1 and H.460.24 Amendment 1.

[ H.Sup4 (12/11) ] - Repository of generic parameters for ITU-T H.460.x sub-series Recommendations

sam, 10 f�v 2012 15:05:42 GMT

Summary

This revision adds feature identifiers for H.460.23 Amendment 1 and H.460.24 Amendment 1.

[ H.Sup2 (12/11) ] - ITU-T H.248.x sub-series packages guide - Release 15

sam, 10 f�v 2012 15:04:25 GMT

Summary

Supplement 2 to ITU-T H-series Recommendations summarizes packages that have been standardized in the time-frame from June 2000 to December 2011. It identifies packages that meet ITU-T H.248.x sub-series requirements for package definition and are for general use by the wider standards community.

ITU-T H.248.x sub-series packages guide - Release 15 provides for the:

.�� identification of packages that are considered technically consistent with ITU-T H.248.x sub-series principles and packages definition rules in clause 12 of Recommendation ITU-T H.248.1;

.�� identification of packages that are currently being worked upon;

.�� identification of packages that have been worked upon over a certain period of time;

.�� identification of packages with overlapping functionality.

Implementors are encouraged to review the packages in this supplement before proposing new packages.

Release 15 contains:

.�� New packages defined in Recommendations ITU-T H.248.82 (ex ITU-T H.248.ECN) and ITU-T H.248.83 (ex ITU-T H.248.MGINST).

.�� Revised packages in Recommendation ITU-T H.248.12.

.�� References to new work items: Recommendations ITU-T H.248.82 (ex ITU-T H.248.ECN), ITU-T H.248.83 (ex ITU-T H.248.MGINST) and ITU-T H.248.NATTP2P.

[ H.Sup2 (12/11) ] - ITU-T H.248.x sub-series packages guide - Release 15

sam, 10 f�v 2012 15:04:24 GMT

Summary

ITU-T H.248.x sub-series packages guide - Release 15 provides for the:

.�� identification of packages that are considered technically consistent with ITU-T H.248.x sub-series principles and packages definition rules in clause 12 of Recommendation ITU-T H.248.1;

.�� identification of packages that are currently being worked upon;

.�� identification of packages that have been worked upon over a certain period of time;

.�� identification of packages with overlapping functionality.

Implementors are encouraged to review the packages in this supplement before proposing new packages.

Release 15 contains:

.�� New packages defined in Recommendations ITU-T H.248.82 (ex ITU-T H.248.ECN) and ITU-T H.248.83 (ex ITU-T H.248.MGINST).

.�� Revised packages in Recommendation ITU-T H.248.12.

.�� References to new work items: Recommendations ITU-T H.248.82 (ex ITU-T H.248.ECN), ITU-T H.248.83 (ex ITU-T H.248.MGINST) and ITU-T H.248.NATTP2P.

[ H.350 (05/11) ] - Directory services architecture for multimedia conferencing

jeu, 08 f�v 2012 16:39:08 GMT

Summary

Recommendation ITU-T H.350 describes a directory services architecture for multimedia conferencing using lightweight directory access protocol (LDAP). Standardized directory services can support the association of persons with endpoints, searchable white pages, and clickable dialling. Directory services can also assist in the configuration of endpoints, and user authentication based on authoritative data sources. This Recommendation describes a standardized LDAP schema to represent endpoints on the network and associate those endpoints with users. It discusses design and implementation considerations for the interrelation of video and voice-specific directories, enterprise directories, call servers and endpoints.

This revised version of Recommendation ITU-T H.350 introduces several enhancements and clarifications to the previous version, primarily the addition of ITU-T X.500 directories support and authentication across multiple directories, and clarifications of commPrivate and commOwner.

This Recommendation includes an electronic attachment containing two schema configuration files for commURIObject and CommObject.

[ H.350.6 (05/11) ] - Directory services architecture for call forwarding and preferences

jeu, 08 f�v 2012 16:35:25 GMT

Summary

Recommendation ITU-T H.350.6 describes a simple lightweight directory access protocol (LDAP) and ITU-T X.500 schemas to represent call forwarding and call preference information in an ITU-T H.350 directory. It is intended to represent addresses to which calls should be forwarded in the case that an endpoint does not answer a call. It can direct calls to simple ITU-T H.320, ITU-T H.323 or session initiation protocol (SIP) addresses, or complex forwarding schemes such as time of day preferences, web pages, electronic mail or other applications. Implementers should review Recommendation ITU-T H.350 in detail before proceeding with this Recommendation.

This revised version of Recommendation ITU-T H.350.6 introduces some corrections to the previous version, primarily updater of ITU-T X.500 ASN.1 contained in clause 8.

This Recommendation includes an electronic attachment containing a schema configuration file for callPreferenceURI.

[ H.350.5 (05/11) ] - Directory services architecture for non-standard protocols

jeu, 08 f�v 2012 08:27:59 GMT

Summary

Recommendation ITU-T H.350.5 describes a lightweight directory access protocol (LDAP) schema to represent non-standard multimedia communications endpoints, and is meant to provide a very basic framework for representing these elements in a directory. It is an auxiliary class related to Recommendation ITU-T H.350 and derives much of its functionality from that architecture. Implementers should review Recommendation ITU‑T H.350 in detail before proceeding with this Recommendation.

The scope of this Recommendation does not include normative methods for the use of the LDAP directory itself or the data it contains. The purpose of the schema is not to represent all possible data elements in the ITU-T H.323 protocol, but rather to represent the minimal set required to accomplish the design goals enumerated in Recommendation ITU-T H.350.

This revised version of Recommendation ITU-T H.350.5 introduces several enhancements and clarifications to the previous version, primarily the addition of ITU-T X.500 directories support.

This Recommendation includes an electronic attachment containing a schema configuration file for genericIdentity.

[ H.350.2 (05/11) ] - Directory services architecture for H.235

jeu, 08 f�v 2012 08:19:23 GMT

Summary

Recommendation ITU-T H.350.2 describes a lightweight directory access protocol (LDAP) schema to represent ITU-T H.235 elements. It is an auxiliary class related to Recommendation ITU-T H.350 and derives much of its functionality from that architecture. Implementers should review Recommendation ITU-T H.350 in detail before proceeding with this Recommendation. Its attributes include ITU-T H.235 identity, password and certificate elements. These elements can be downloaded to an endpoint for automatic configuration or accessed by a gatekeeper for call signalling and authentication.

The scope of this Recommendation does not include normative methods for the use of the LDAP directory itself or the data it contains. The purpose of the schema is not to represent all possible data elements in the ITU-T H.235 protocol, but rather to represent the minimal set required to accomplish the design goals enumerated in Recommendation ITU-T H.350.

This revised version of Recommendation ITU-T H.350.2 introduces several enhancements and clarifications to the previous version, primarily the addition of ITU-T X.500 directories support.

This Recommendation includes an electronic attachment containing a schema configuration file for h235Identity.

[ H.350.1 (05/11) ] - Directory services architecture for H.323

jeu, 08 f�v 2012 08:11:17 GMT

Summary

Recommendation ITU-T H.350.1 describes a lightweight directory access protocol (LDAP) schema to represent ITU-T H.323 endpoints. It is an auxiliary class related to Recommendation ITU-T H.350 and derives much of its functionality from that architecture. Implementers should review Recommendation ITU-T H.350 in detail before proceeding with this Recommendation. Its attributes include all ITU-T H.323 alias types. These aliases can be downloaded to an endpoint for automatic configuration, accessed by a gatekeeper for call signalling and authorization, and published to white pages to create user dialling directories.

This revised version of Recommendation ITU-T H.350.1 introduces several enhancements and clarifications to the previous version, primarily the addition of ITU-T X.500 directories support and clarification of h323IdentitypartyNumber.

This Recommendation includes an electronic attachment containing a text-only version of the schema configuration file for h323Identity.

[ H.460.24 (2009) Amendment 1 (05/11) ] - Improvements for NAT traversal without intermediary entities

ven, 02 f�v 2012 10:23:44 GMT

Summary

Recommendation ITU‑T H.460.24 enables an ITU‑T H.323 gatekeeper to formulate a decision to enable direct media flows between ITU‑T H.323 endpoints that reside behind network address translator (NAT)/firewall (FW) devices. This extension is used in conjunction with Recommendation ITU-T H.460.18 to facilitate the traversal of media across NAT/FW devices and Recommendation ITU-T H.460.23 to discover the characteristics of NAT/FW devices sitting in front of ITU‑T H.323 endpoints, reducing the frequency with which media proxy devices (as described in Recommendation ITU-T H.460.19) are needed by allowing direct media connectivity between the endpoints. Connectivity is achieved via the formulation of an intelligent media transmission decision and call signalling that instructs endpoints to initiate media flows in such a manner that a reliable direct media pathway is established, even if one or both endpoints reside behind a NAT/FW device.

Amendment 1 to Recommendation ITU-T H.460.24 further improves conditions where media pathways do not require the services of an intermediary to achieve NAT traversal. New Annex B allows endpoints under certain conditions, after first establishing media flows through an intermediary entity, to probe for a direct route and, if detected, change the media pathway to flow directly between the endpoints freeing up the resources of the intermediary entity.

[ H.460.24 (2009) Amendment 1 (05/11) ] - Improvements for NAT traversal without intermediary entities

ven, 02 f�v 2012 10:23:44 GMT

Summary

[ H.460.23 (2009) Amendment 1 (05/11) ] - Support for ITU-T H.460.24 Annex B

ven, 02 f�v 2012 10:21:30 GMT

Summary

Recommendation ITU-T H.460.23 enables an ITU-T H.323 endpoint residing behind a network address translator (NAT) or firewall (FW) device to report NAT/FW characteristics to the gatekeeper. When used with Recommendation ITU‑T H.460.24, a gatekeeper may utilize NAT/FW information in order to formulate a decision as to how to enable direct media flow between two devices. In most cases, following these procedures will allow the gatekeeper to avoid the need for a media proxy as described in Recommendation ITU‑T H.460.19, as media can be successfully transmitted directly between two endpoints residing behind distinct NAT/FW devices.

Amendment 1 to Recommendation ITU-T H.460.23 adds the ability for endpoints to advertise to the gatekeeper support for ITU‑T H.460.24 Annex B (included in Recommendation ITU-T H.460.24 Amendment 1).

[ H.460.23 (2009) Amendment 1 (05/11) ] - Support for ITU-T H.460.24 Annex B

ven, 02 f�v 2012 10:21:30 GMT

Summary

[ H.Imp248.x (12/2011) ] - Implementors' Guide for the H.248 Sub-series of Recommendations ("Media Gateway Control Protocol")

mar, 30 jan 2012 06:45:24 GMT

Implementors' Guide for the H.248 Sub-series of Recommendations ("Media Gateway Control Protocol")

[ H.740 (2010) Amendment 1 (03/11) ] - New video handling sensor event scenario in Appendix II

ven, 26 jan 2012 13:42:02 GMT

Summary

Recommendation ITU-T H.740 provides a framework for application event handling for IPTV, such as emergency alert and audience measurement. This Recommendation provides a basic framework for application event model, application event description and notification, metadata model, delivery methods and security mechanism for application event for IPTV.

Amendment 1 includes a new use case about a video handling sensor event. This event can be used as supplemental information on audience measurement and other IPTV applications.

[ H.740 (2010) Amendment 1 (03/11) ] - New video handling sensor event scenario in Appendix II

ven, 26 jan 2012 13:42:01 GMT

Summary

Amendment 1 includes a new use case about a video handling sensor event. This event can be used as supplemental information on audience measurement and other IPTV applications.

[ H.222.0 (2006) Amendment 6 (05/11) ] - Extension to AVC video descriptor and signalling of operation points for MVC

ven, 26 jan 2012 13:39:37 GMT

Summary

Amendment 6 to Recommendation ITU-T H.222.0 | ISO/IEC 13818-1 specifies additional signalling for the transport of bitstreams conforming to profiles defined in Annex H of Recommendation ITU-T H.264 (2010) | ISO/IEC 14496‑10:2010 over MPEG-2 transport streams as defined in Recommendation ITU-T H.222.0 (2006) | ISO/IEC 13818-1:2007 Amendment 4 (2009). This amendment 6 introduces the new MVC operation point descriptor and clarifies certain use cases defined in Recommendation ITU‑T H.222.0 (2006) | ISO/IEC 13818-1:2007 Amendment 4 (2009).

The MVC operation point descriptor includes signalling of stream characteristics needed to support additional use cases for MVC video defined in Recommendation ITU-T H.264 (2010) | ISO/IEC 14496‑10:2010.

This amendment also extends the AVC video descriptor to signal presence of frame packing SEI in the AVC video elementary stream.

[ H.222.0 (2006) Amendment 6 (05/11) ] - Extension to AVC video descriptor and signalling of operation points for MVC

ven, 26 jan 2012 13:39:37 GMT

Summary

This amendment also extends the AVC video descriptor to signal presence of frame packing SEI in the AVC video elementary stream.

[ H.222.0 (2006) Amendment 5 (05/11) ] - Transport of JPEG 2000 Part 1 (ITU-T T.800 | ISO/IEC 15444-1) video over ITU-T H.222.0 | ISO/IEC 13818-1

ven, 26 jan 2012 13:37:31 GMT

Summary

Amendment 5 to Recommendation ITU-T H.222.0 | ISO/IEC 13818-1 specifies the carriage of JPEG 2000 video bitstreams conforming to one or more profiles defined in Recommendation ITU‑T T.800 | ISO/IEC 15444-1 over Recommendation ITU-T H.222.0 (05/2006) | ISO/IEC 13818-1:2007. The structure of JPEG 2000 access units as well as the syntax and semantics are specified in the JPEG 2000 standards and are also included in Annex S of this Recommendation | International Standard. Each access unit is self-contained and decodable without reference to any other access unit in the video stream. The carriage of JPEG 2000 video will be limited to transport streams only in this amendment.

[ H.222.0 (2006) Amendment 5 (05/11) ] - Transport of JPEG 2000 Part 1 (ITU-T T.800 | ISO/IEC 15444-1) video over ITU-T H.222.0 | ISO/IEC 13818-1

ven, 26 jan 2012 13:37:31 GMT

Summary

[ H.248.11 (2002) Corrigendum 1 (06/08) ] - Clarifying MG_overload event relationship with ADD commands

ven, 26 jan 2012 10:54:59 GMT

Summary

Recommendation ITU-T H.248.11 describes a package for media gateway (MG) overload control for use with the H.248.1 gateway control protocol. It serves to protect an MG from processing overload that prevents the timely execution of H.248.1 transactions.

In summary, in this Recommendation, overload protection is achieved as follows:

1)�� An MG (or virtual MG) detects that it is in overload and notifies its media gateway controller (MGC) of that fact whenever it receives an ADD command.

2)�� The MGC adaptively throttles the rate it sets up calls using that MG (or virtual MG) to maximize the MG's effective throughput whilst bounding its response times. It does this by throttling the rate at which transactions that set up new calls or that new call legs are sent to the overloaded MG, so as to cause the rate of overload notifications the MGC receives from the overloaded MG (or virtual MG) to converge to a suitably low level.

A separate instance of the overload control shall be initiated at an MGC for each of its dependent MGs (or virtual MGs) that is overloaded. These separate instances should run independently (that is, they do not explicitly exchange information). Their overload control parameters shall be separately configurable, for example, by means of a proprietary management interface, or the use of SNMP to invoke configuration functions.

The most general overload scenario the control can handle is where one or more MGCs are jointly overloading a single MG that has several virtual MGs (virtual MG 'i' interacting only with MGC "i'). The control does not need to know how many MGCs are causing the MG to be overloaded, nor what the MG capacity is. Informative reference [b-Oftel] provides a full explanation of one way this can be achieved, and informative reference [b-whitehead] provides further material on designing overload controls.

The overload control is largely specified by saying how it shall behave, but not how it should be implemented to achieve that behaviour. This has two important consequences.

As a first consequence, part of the package (see clause 8.5) defines a set of overload scenarios, and any fully-compliant implementation of the package must automatically (i.e., without the need for operator intervention to adjust parameter values from one overload scenario to another) satisfy all the requirements for each of the scenarios.

As a second consequence, not all configurable parameters can be known to this package since they depend upon specific implementations of the control. Nevertheless, there is a requirement that the implementation shall provide a means by which an operator can change all parameters which affect the performance of the control. See clause 9 for the management requirements associated with this package. It is expected that they will be realized by a proprietary management interface, or the use of SNMP.

Corrigendum 1 to Recommendation ITU-T H.248.11 clarifies that, when the MG is overloaded, overload events may be sent either only following the first ADD.request which creates a new context, or following all ADD.request commands. These two options result in different normalizations of the overload event rate as an indicator of the level of MG overload. The concept of normalization is explained.

[ H.248.11 (2002) Corrigendum 1 (06/08) ] - Clarifying MG_overload event relationship with ADD commands

ven, 26 jan 2012 10:54:59 GMT

Summary

In summary, in this Recommendation, overload protection is achieved as follows:

1)�� An MG (or virtual MG) detects that it is in overload and notifies its media gateway controller (MGC) of that fact whenever it receives an ADD command.

The overload control is largely specified by saying how it shall behave, but not how it should be implemented to achieve that behaviour. This has two important consequences.

[ H.625 (10/10) ] - Architecture for network-based speech-to-speech translation services

sam, 25 nov 2011 15:23:59 GMT

Summary

Recommendation ITU-T H.625 defines the system architecture for network-based speech-to-speech translation (S2ST) on the basis of Recommendation ITU-T F.745 and serves as a technical introduction to the subsequent definitions of detailed system components and protocols. The scope of this Recommendation is to describe the functional architecture and mechanisms of network‑based S2ST, interface protocols between S2ST modules, and a workflow of the network-based S2ST system.

[ H.625 (10/10) ] - Architecture for network-based speech-to-speech translation services

sam, 25 nov 2011 15:23:59 GMT

Summary

[ H.761 (06/11) ] - Nested context language (NCL) and Ginga-NCL

ven, 22 sep 2011 08:00:38 GMT

Summary

Recommendation ITU-T H.761 gives the specification of the nested context language (NCL) and of an NCL presentation engine called Ginga-NCL to provide interoperability and harmonization among IPTV multimedia application frameworks.

NCL is a glue language that holds media objects together in multimedia presentations, no matter which object types they are. As an example, NCL treats an HTML document as one of its possible media objects. In this way, NCL does not substitute, but embed, XHTML-based documents. The same reasoning applies to other media content and multimedia content objects, and also to objects with content coded in any computer language. Ginga-NCL is an NCL presentation engine built as a component of a DTV middleware. A very special NCL object type defined in Ginga-NCL is NCLua, an imperative media-object with Lua code.

This Recommendation includes an electronic attachment containing NCL 3.0 module schemas used in the Enhanced DTV profile.

[ H.264 (06/11) ] - Advanced video coding for generic audiovisual services

ven, 22 sep 2011 07:57:32 GMT

Summary

This Recommendation | International Standard represents an evolution of the existing video coding standards (H.261, H.262, and H.263) and it was developed in response to the growing need for higher compression of moving pictures for various applications such as videoconferencing, digital storage media, television broadcasting, Internet streaming, and communication. It is also designed to enable the use of the coded video representation in a flexible manner for a wide variety of network environments. The use of this Recommendation | International Standard allows motion video to be manipulated as a form of computer data and to be stored on various storage media, transmitted and received over existing and future networks and distributed on existing and future broadcasting channels.

The revision approved 2005-03 contained modifications of the video coding standard to add four new profiles, referred to as the High, High 10, High 4:2:2, and High 4:4:4 profiles, to improve video quality capability and to extend the range of applications addressed by the standard (for example, by including support for a greater range of picture sample precision and higher-resolution chroma formats). Additionally, a definition of new types of supplemental data was specified to further broaden the applicability of the video coding standard. Finally, a number of corrections to errors in the published text were included.

Corrigendum 1 to ITU-T Rec. H.264 corrected and updated various minor aspects to bring the ITU-T version of the text up to date relative to the April 2005 output status approved as a new edition of the corresponding jointly-developed and technically-aligned text ISO/IEC 14496-10. It additionally fixed a number of minor errors and needs for clarification and defined three previously-reserved sample aspect ratio indicators.

Amendment 1 "Support of additional colour spaces and removal of the High 4:4:4 Profile" contained alterations to ITU‑T Rec. H.264 | ISO/IEC 14496‑10 Advanced Video Coding to specify the support of additional colour spaces and to remove the definition of the High 4:4:4 Profile.

NOTE - ITU-T Rec. H.264 is a twin text with ISO/IEC 14496‑10 and this amendment was published in two different documents in the ISO/IEC series:

-�� The removal of the High 4:4:4 profile was found in ISO/IEC 14496-10:2005/Cor.2.

-�� The specification for support of additional colour spaces was found in ISO/IEC 14496-10:2005/Amd.1.

Amendment 2 "New profiles for professional applications" contained extensions to ITU-T Rec. H.264 | ISO/IEC 14496‑10 Advanced Video Coding to specify the support of five additional profiles intended primarily for professional applications (the High 10 Intra, High 4:2:2 Intra, High 4:4:4 Intra, CAVLC 4:4:4 Intra, and High 4:4:4 Predictive profiles) and two new types of supplemental enhancement information (SEI) messages (the post-filter hint SEI message and the tone mapping information SEI message).

Amendment 3 "Scalable video coding" contained extensions to ITU-T Rec. H.264 | ISO/IEC 14496-10 Advanced Video Coding to specify a scalable video coding extension in three profiles (the Scalable Baseline, Scalable High, and Scalable High Intra profiles).

The H.264 edition published in 2005-11 included the text approved 2005-03 and its Corrigendum 1 approved 2005-09. H.264 (2005) Amd.2 (2007) was available only as pre-published text since it was superseded by H.264 Amd.3 (2007-11) before its publication; further, H.264 Amd.3 was not published separately. This third edition integrated into the H.264 edition published in 2005-11 all changes approved in Amendments 1 (2006-06), 2 (2007-04) and 3 (2007-11).

Corrigendum 1 (2009) provides a significant number of minor corrections, clarifications, consistency improvements and formatting improvements drafted in response to accumulated errata reports collected since publication of the 2nd edition (dated 2005-03, which included a Cor.1 approved 2005-09).

The H.264 edition published in 2009-05 contained enhancement extensions to support multiview video coding (MVC), specification of a "Constrained Baseline Profile", and some miscellaneous corrections and clarifications.

The H.264 edition published in 2010-03 contained the specification of a new profile (the Stereo High profile) for two‑view video coding with support of interlaced coding tools, the specification a new SEI message (the frame packing arrangement SEI message), and some miscellaneous corrections and clarifications.

This revision to ITU-T Rec. H.264 contains the specification of a new level (Level 5.2) supporting higher processing rates in terms of maximum macroblocks per second, a new profile (the Progressive High profile) to enable implementation of decoders supporting only the frame coding tools of the previously specified High profile, and includes miscellaneous corrections and clarifications.

[ H.264 (06/11) ] - Advanced video coding for generic audiovisual services

ven, 22 sep 2011 07:57:32 GMT

Summary

NOTE - ITU-T Rec. H.264 is a twin text with ISO/IEC 14496‑10 and this amendment was published in two different documents in the ISO/IEC series:

-�� The removal of the High 4:4:4 profile was found in ISO/IEC 14496-10:2005/Cor.2.

-�� The specification for support of additional colour spaces was found in ISO/IEC 14496-10:2005/Amd.1.

[ H.362 (09/10) ] - A framework for adaptive end-to-end QoS control based on variable bit-rate codecs in wireless networks

mar, 25 jui 2011 07:24:07 GMT

Summary

Recommendation ITU-T H.362 describes a framework for adaptive end-to-end quality of service (QoS) control using variable bit-rate codecs in wireless networks. Specifically, this Recommendation describes a reference network architecture, functional entities, references points, a terminal architecture, and signalling flows between functional entities. The framework in this Recommendation can be used for application level QoS support to control the multimedia service quality adaptively in wireless networks where the network status may change over time.

[ H.362 (09/10) ] - A framework for adaptive end-to-end QoS control based on variable bit-rate codecs in wireless networks

mar, 25 jui 2011 07:24:06 GMT

Summary

[ H.771 (05/11) ] - SIP-based discovery of IPTV services

ven, 21 jui 2011 12:30:35 GMT

Summary

ITU-T H.771 describes the process for IPTV service provider discovery and service discovery based on SIP [IETF RFC 3261]. The processes enable IPTV terminal device to acquire information about available IPTV service providers and IPTV services.

[ H.771 (05/11) ] - SIP-based discovery of IPTV services

ven, 21 jui 2011 12:30:34 GMT

Summary

[ H.762 (05/11) ] - Lightweight interactive multimedia environment (LIME) for IPTV services

jeu, 29 jui 2011 07:48:22 GMT

Summary

Recommendation ITU-T H.762 describes the high-level functionalities of the lightweight interactive multimedia environment (LIME) for IPTV. LIME supports functionalities in IPTV terminal devices to provide interactivity and a variety of content such as audio, video, graphics and text. Expected services include additional data such as text to enrich television programmes, and two-way portal pages.

This Recommendation describes the profile called "LIME-HTML" of W3C Recommendation XHTML 1.0, the profile called "LIME-CSS" of cascading style sheets 1 (CSS1), and a part of CSS2, the profile of document object model (DOM) called "LIME-DOM", and a script language called "LIME-Script" that is a subset of ECMAScript but has functional extensions required for IPTV services. It describes the use of IP-based protocols for transport of LIME and IPTV-related services.

This revision includes the addition of explanatory text and definitions to enhance readability and improve the understanding of the extended functions. Specifically the change of the string "BML" to "LIME" and the addition of explanations of the browser pseudo-object methods were considered. These changes do not modify any accepted functions nor introduce any new functionality.

[ H.762 (05/11) ] - Lightweight interactive multimedia environment (LIME) for IPTV services

jeu, 29 jui 2011 07:48:22 GMT

Summary

[ H.626 (05/11) ] - Architectural requirements for visual surveillance

jeu, 29 jui 2011 07:46:57 GMT

Summary

The purpose of Rec. ITU-T H.626 is to define a visual surveillance system based on IP networks. The visual surveillance system provides the display and storage of the multimedia (such as video, audio, image) captured by multiple remote cameras over an IP network for multiple users. It also provides other functionalities such as remote control, alarm and linkage actions, recording and playback.

This Recommendation defines the functional requirements, model, architecture, entities, reference points and service control flow of the visual surveillance. This document also describes the hierarchy model for deployment, visual surveillance management system, interworking and service convergence between visual surveillance system and other multimedia systems.

[ H.626 (05/11) ] - Architectural requirements for visual surveillance

jeu, 29 jui 2011 07:46:57 GMT

Summary

[ H.450.3 (05/11) ] - Call diversion supplementary service for ITU-T H.323 systems

mer, 28 jui 2011 08:08:49 GMT

Summary

This Recommendation describes the procedures and the signalling protocol for the Call diversion supplementary service (SS-DIV) in H.323 (Packet based multimedia communications systems) networks. This Recommendation comprises the services Call Forwarding Unconditional (SS-CFU), Call Forwarding Busy (SS-CFB), Call Forwarding No Reply (SS-CFNR) and Call Deflection (SS‑CD).

SS-CFU, SS-CFB, SS-CFNR and SS-CD are supplementary services which apply during call establishment providing a diversion of an incoming call to another destination endpoint.

This Recommendation makes use of the "Generic functional protocol for the support of supplementary services in H.323" as defined in Recommendation H.450.1

The procedures and the signalling protocol of this Recommendation are derived from the Call diversion supplementary service specified in ISO/IEC 13872 and ISO/IEC 13873.

The revision approved 2011/05 errors discovered in the initial publication.

[ H.450.3 (05/11) ] - Call diversion supplementary service for ITU-T H.323 systems

mer, 28 jui 2011 08:08:49 GMT

Summary

SS-CFU, SS-CFB, SS-CFNR and SS-CD are supplementary services which apply during call establishment providing a diversion of an incoming call to another destination endpoint.

This Recommendation makes use of the "Generic functional protocol for the support of supplementary services in H.323" as defined in Recommendation H.450.1

The procedures and the signalling protocol of this Recommendation are derived from the Call diversion supplementary service specified in ISO/IEC 13872 and ISO/IEC 13873.

The revision approved 2011/05 errors discovered in the initial publication.

[ H.450.2 (05/11) ] - Call transfer supplementary service for ITU-T H.323 systems

mer, 28 jui 2011 08:07:39 GMT

Summary

This Recommendation describes the procedures and the signalling protocol for the Call Transfer supplementary service (SS-CT) in H.323 (Packet-based multimedia communications systems) networks.

SS-CT is a supplementary service which enables the served user A to transform an existing call (user A-user B) into a new call between user B and a user C selected by user A. User A may or may not have a call established with user C prior to Call Transfer.

This Recommendation makes use of the "Generic functional protocol for the support of supplementary services in H.323" as defined in Recommendation H.450.1

The procedures and the signalling protocol of this Recommendation are derived from the Call Transfer supplementary service specified in ISO/IEC 13865 and 13869.

This revision corrects errors discovered in the initial publication.

[ H.450.2 (05/11) ] - Call transfer supplementary service for ITU-T H.323 systems

mer, 28 jui 2011 08:07:39 GMT

Summary

This Recommendation describes the procedures and the signalling protocol for the Call Transfer supplementary service (SS-CT) in H.323 (Packet-based multimedia communications systems) networks.

This Recommendation makes use of the "Generic functional protocol for the support of supplementary services in H.323" as defined in Recommendation H.450.1

The procedures and the signalling protocol of this Recommendation are derived from the Call Transfer supplementary service specified in ISO/IEC 13865 and 13869.

This revision corrects errors discovered in the initial publication.

[ H.450.1 (05/11) ] - Generic functional protocol for the support of supplementary services in ITU-T H.323 systems

mer, 28 jui 2011 08:06:23 GMT

Summary

This Recommendation describes the procedures and the signalling protocol between H.323 entities (Packet-based multimedia communications systems) for the control of supplementary services. The signalling protocol which is defined within this Recommendation is common to all H.323 supplementary services.

Detailed procedures applicable to individual supplementary services are specified by other Recommendations of the H.450.x-Series and by individual manufacturers for proprietary services using the capabilities defined in this Recommendation.

The procedures of this Recommendation are derived from the generic functional protocol specified in ISO/IEC 11582 for Private Integrated Services Networks (PISN).

The revision approved 2011/05 corrects errors discovered in the initial publication.

[ H.450.1 (05/11) ] - Generic functional protocol for the support of supplementary services in ITU-T H.323 systems

mer, 28 jui 2011 08:06:23 GMT

Summary

The procedures of this Recommendation are derived from the generic functional protocol specified in ISO/IEC 11582 for Private Integrated Services Networks (PISN).

The revision approved 2011/05 corrects errors discovered in the initial publication.

[ H.245 (05/11) ] - Control protocol for multimedia communication

mer, 28 jui 2011 08:05:04 GMT

Summary

This Recommendation specifies syntax and semantics of terminal information messages as well as procedures to use them for in-band negotiation at the start of or during communication. The messages cover receiving and transmitting capabilities as well as mode preference from the receiving end, logical channel signalling, and Control & Indication. Acknowledged signalling procedures are specified to ensure reliable audiovisual and data communication.

Products claiming compliance with Version 16 of H.245 shall comply with all of the mandatory requirements of this Recommendation. Version 16 products can be identified by H.245 TerminalCapabilitySet messages containing a protocolIdentifier value of {itu-t (0) recommendation (0) h (8) 245 version (0) 16}.

Relative to H.245 Version 15 (2009-12), this version improves harmonisation with SIP by making the following changes:

- allowing a new dynamic payload number to be specified in the H.245 Open Logical Channel Acknowledgement message;

- revising clause B.3.2 to indicate that H.323 systems should use the dynamic payload type specified in the H.245 Open Logical Channel Acknowledgement message instead of the dynamic payload type specified in the H.245 Open Logical Channel message;

- defining a similar mechanism for logical channels that use multiple payload types; and

- defining a new capability in a new annex, Annex T, that specifies that an endpoint is capable of using the dynamic payload type replacement mechanisms in the H.245 Open Logical Channel Acknowledgement message.

.��

[ H.245 (05/11) ] - Control protocol for multimedia communication

mer, 28 jui 2011 08:05:04 GMT

Summary

Relative to H.245 Version 15 (2009-12), this version improves harmonisation with SIP by making the following changes:

- allowing a new dynamic payload number to be specified in the H.245 Open Logical Channel Acknowledgement message;

- defining a similar mechanism for logical channels that use multiple payload types; and

.��

[ H.350.4 (05/11) ] - Directory services architecture for SIP

sam, 24 jui 2011 10:05:59 GMT

Summary

This Recommendation describes an LDAP directory services architecture for multimedia conferencing using SIP. In particular, it defines an LDAP schema to represent SIP User Agents (UAs) on the network and associate those endpoints with users.

This Recommendation is intended to supplement the CommObject directory architecture as discussed in ITU-T Rec. H.350, and not intended to be used as a stand-alone architecture. The implementation of this LDAP schema, together with the use of the H.350 CommObject architecture, facilitates the integration of SIP User Agents and conferencing devices into existing Enterprise Directories, thus allowing the user to perform white page lookups and access clickable dialling supported by SIP devices.� The primary reasons for implementing this schema are identical to those listed in ITU-T Rec. H.350 (the CommObject class definition) as they apply specifically to the use of SIP UAs.

This revised version of H.350.4 introduces several enhancements and clarifications to the previous version, primarily addition of X.500 directories support.

[ H.350.3 (05/11) ] - Directory services architecture for H.320

sam, 24 jui 2011 10:04:38 GMT

Summary

This Recommendation describes an LDAP schema to represent H.320 endpoints. It is an auxiliary class related to ITU-T Rec. H.350 and derives much of its functionality from that architecture. Implementors should review ITU-T Rec. H.350 in detail before proceeding with this Recommendation. Its attributes include basic H.320 address elements. These addresses can be downloaded to an endpoint for automatic configuration or published to white pages to create user dialling directories.

The scope of this Recommendation does not include normative methods for the use of the LDAP directory itself, or the data it contains. The purpose of the schema is not to represent all possible data elements in the H.320 protocol, but rather to represent the minimal set required to accomplish the design goals enumerated in ITU-T Rec. H.350.

This revised version of H.350.3 introduces several enhancements and clarifications to the previous version, primarily addition of X.500 directories support.

[ H.248.81 (05/11) ] - Gateway control protocol: Guidelines on the use of the international emergency preference scheme (IEPS) call indicator and priority indicator in ITU-T H.248 profiles

sam, 24 jui 2011 09:59:54 GMT

Summary

This Recommendation provides guidelines on the use of the International Emergency Preference Scheme (IEPS) call indicator and priority indicator in H.248 profiles for H.323 and NGN systems.� These guidelines may be used by other Standards Developing Organization (SDOs) when defining their H.248.1 profiles in support of priority services, e.g. Emergency Telecommunications Service (ETS), Multimedia Priority Service (MPS).

[ H.248.81 (05/11) ] - Gateway control protocol: Guidelines on the use of the international emergency preference scheme (IEPS) call indicator and priority indicator in ITU-T H.248 profiles

sam, 24 jui 2011 09:59:54 GMT

Summary

[ H.248.75 (05/11) ] - Gateway control protocol: Package identifier publishing and application package

sam, 24 jui 2011 09:58:45 GMT

Summary

This Recommendation defines a new package that allows the MGC to determine the relationship between the base and extended Packages as well as to determine/set which Package ID (base and/or extended) will be used (published) in commands. It also allows the MGC to suppress the use of certain packages on the MG.

[ H.248.75 (05/11) ] - Gateway control protocol: Package identifier publishing and application package

sam, 24 jui 2011 09:58:45 GMT

Summary

[ H.241 (2006) Corrigendum 1 (05/11) ] - Corrections to the CustomMaxDPB capability parameter

jeu, 22 jui 2011 12:38:09 GMT

Summary

This Recommendation defines the use of advanced video codecs, including ITU-T Rec. H.264, in ITU-T Recs H.310, H.320, H.321, H.322, H.323 and H.324 terminals. It also defines generic extended signalling for use with all video codecs in the H.300‑series terminals.

This revised version adds clarifications regarding H.264 VCL HRD (Type I HRD) versus NAL HRD (Type II HRD) bit rate usage, sample aspect ratio capabilities for H.264, signalling for Reduced Complexity Decoding Operation (RCDO) for H.264 bitstreams, and a new Annex B, "RCDO for H.264 Baseline Profile bitstreams". Annex A has been replaced with an inclusion by reference of the recently approved RFC 3984 (without actual change in content). New Annex B specifies a reduced‑complexity decoding process to be applied to H.264 Baseline profile bitstreams when such use has been negotiated using ITU‑T Rec. H.241.

Amendment 1 to this Recommendation provides a new clause 6.2.5 allowing for the negotiation of particular video submodes of H.264 encoding along with associated additions to Appendix I. It also includes a new Appendix II which contains non-normative examples describing the use of this new clause.

Amendment 2 to this Recommendation provides a new clause 8.3.2.14 defining a new optional H.264 capability parameter (MaxFPS). It also includes revised text for Appendix II.

Corrigendum 1 to this Recommendation revises the units used for the CustomMaxDPB parameter value to 256/3 macroblocks, which makes this parameter consistent with Table A.1/H.264 (2010). The scaling of this revised parameter is carefully chosen to maintain interoperability with existing systems.� The equation for the number of decoded frames in clause 8.3.2.6 is removed, as it produces incorrect results when applied to some H.264 picture formats.� It is replaced with new text that applies to all picture formats and profiles. Corrigendum 1 also includes a note added to Table 8-8/H.241, clarifying that cpbBrVclFactor and cpbBrNALFactor units are not used for the value of the CustomMaxBRandCPB parameter.