Ana səhifə

International organisation for standardization organisation internationale normalisation


Yüklə 32.34 Kb.
tarix25.06.2016
ölçüsü32.34 Kb.


INTERNATIONAL ORGANISATION FOR STANDARDIZATION

ORGANISATION INTERNATIONALE NORMALISATION

ISO/IEC JTC1/SC29/WG11

CODING OF MOVING PICTURES AND AUDIO

ISO/IEC JTC 1/SC 29/WG11 N11229

Kyoto, Japan – January 2010

Source: Requirements

Title: Advanced IPTV Terminal (AIT): Call for Proposals

Status: Output





International Telecommunication Union

International Organisation for Standardisation

International Electrotechnical Commission

Source:

ITU-T Q13/16 Multimedia terminals, systems and applications

and

ISO/IEC JTC1/SC29/WG11 Coding of Moving Pictures and Audio

Title:

Joint Call for Proposals on Advanced IPTV Terminal

Status:

Approved by ISO/IEC JTC1/SC29/WG11 (Kyoto, 22 January 2010)



Advanced IPTV Terminal (AIT): Call for Proposals


Introduction


MPEG, a working group in ISO/IEC, has produced many important standards (MPEG-1, MPEG-2, MPEG-4, MPEG-7, MPEG-21, …). Some of these standards concern basic technologies (video, audio and 3D Graphics compression, transport protocols etc.) while others concern system level issues such as MPEG-A (Multimedia Application Format), MPEG-E (MPEG Multimedia Middleware), and MPEG-M (MPEG Extensible Middleware).

Likewise, ITU-T SG16 has been working on a number of recommendations either published or under development for IPTV such as the basic IPTV terminals [1], the full-fledged [2] and mobile IPTV terminals [3].

Lately, a number of technology and business developments such as the deployment of broadband networks enabling new ways to deliver and exchange multimedia services and the improvement of hardware performance allowing many service aspects to be implemented as software are having substantial impacts on media services-related businesses. These are opening new business opportunities for multimedia services, such as IPTV services.

The purpose of the AIT standard is to leverage on advanced technologies to bring into IPTV services the buoyancy of new exciting initiatives – sometimes assembling millions of users in a fortnight – that pop up almost every day with new features such as open APIs and the possibility for third parties to provide applications to those APIs.

Both MPEG and Question 13 of ITU-T SG16 (Q.13/16) feel that, by standardizing a flexible set of protocols and interfaces, it will enable “media service ecosystems” yielding new forms of advanced digital media services capable of innovating the IPTV landscape. Such a set of protocols and interfaces is the target of the Advanced IPTV Terminal (AIT) standard that MPEG and ITU-T Question 13, “Multimedia Platforms and End-Systems for IPTV Services”, of Study Group16 (Q.13/16) plan to develop jointly for IPTV terminals more advanced (in terms of functionalities) than the current IPTV terminals standardized or being standardized by ITU-T.

As stated in the attached document, “Context and Objectives for Advanced IPTV Terminal” [1], the intended standard for “Advanced IPTV Terminal” (AIT) will support the service providers’ drive to deploy innovative multimedia services such as those described in [2] and [3] by identifying a set of “Elementary Services” and defining the corresponding set of protocols and APIs to enable any user in an AIT value chain to access those services in an interoperable fashion. Note that an AIT value chain is a collection of Users, including Creators, End Users and Service Providers, that conforms to the AIT standard.



Figure 1 below depicts the AIT standard-enabled digital media service eco-system underpinning and supporting the activities of content creators and consumers.


Figure 1 – The AIT Ecosystem
With this document, “Advanced IPTV Terminal (AIT): Call for Proposals”, MPEG and Q.13/16 would like to be informed about technologies that satisfy the requirements identified in the AIT Requirements document [3]. All parties that believe they have relevant technologies for AIT are invited to submit these technologies for consideration by MPEG and Q.13/16.
Please be aware that the current timeline for developing the AIT standard is as follows:

  • Publication of Call for Proposals: January 2010

  • Submission and study of responses: April 2010

  • Development of the AIT standard: April 2010-July 2011

  • Approval of the AIT standard (FDIS): July 2011



Requirements for the proposals


In the following text, “existing technologies” refer to existing MPEG and ITU-T technologies that are relevant to the AIT standard.
Those intending to submit a proposal in response to this Call should consider the following aspects:


  1. It is not required to be an MPEG or ITU-T member to submit a proposal

  2. A proposal need not support all the requirements listed in [3]. However, a table shall be provided indicating

    1. Which requirements are met/not met

    2. The reason why a requirement could be satisfied

  3. A response may include solutions that extend the requirements listed in [3]. In this case proponents shall justify why an extension should be beneficial to the AIT standard

  4. A response may propose additional requirements. MPEG and Q.13/16 may decide to retain the requirements or consider them in a future additional Calls for Proposals

  5. In general the core of a proposal should be protocols and APIs enabling Users to access and aggregate Services, and new technologies where required to define protocols and APIs.

  6. A response may include proposals of new technologies or technologies that are alternative to existing technologies such as those in [3]. In the latter case, proponents shall provide very valid and convincing arguments why it should be in the interest of the AIT standard and why the proposed technologies should be given preference over existing technologies.

  7. All proposed technologies should be thoroughly described. In the case of APIs and protocols a full specification comparable to the one provided in ISO/IEC 23006-2 [4] or ISO/IEC 23006-4 [5] is expected.

  8. Proposals shall be received by 2010/04/12T23.59 GMT, by two AIT Chairs, Masahito Kawamori (kawamori.masahito@lab.ntt.co.jp) and Xin Wang (xwang@huawei.com).

  9. Proponents shall provide software implementations of their proposed technologies suitable for integration in the reference software of the AIT standard by a time that shall be no later that FCD stage (January 2011). By responding to this Call, Proponents agree to be bound by the obligations contained in this point. Failure to provide the said software may lead to a removal of their technologies from the standard. Proponents are advised that the AIT reference software should be released according to the ISO/IEC JTC 1/SC 29 Software Copyright Licensing Disclaimer (http://www.itscj.ipsj.or.jp/sc29/29w7scld.htm).

Evaluation Procedure

MPEG and Q.13/16 will evaluate the proposals against the objectives and requirements as set forth in the AIT requirements. Where proponents provide comments on these requirements, these comments may be taken into consideration but proponents should be aware that the current requirements represent the considered view of the two groups. This Call for Proposals does not specifically solicit technologies that have already been addressed by existing standards, or ongoing in MPEG and ITU-T, as AIT will refer to these technologies when appropriate.


Proposals will be evaluated by MPEG and Q.13/16 at an evaluation meeting to be held on 2010/04/17 in Dresden, Germany. As the evaluation will be based on the discussions and consensus among the experts participating in the evaluation meeting, proponents are invited to come and present their proposals at the evaluation meeting and to participate in discussions about proposals. The evaluation will take the following (not necessarily complete) evaluation criteria into account: Completeness, Extensibility, Simplicity, Effectiveness, Flexibility and Scalability.
The evaluation is intended to lead to selecting and/or developing a specification based upon the responses to this Call. However, MPEG and Q.13/16 reserve the right to adopt none, one, or a combination of several proposals as well as to issue another call for proposals. All decisions will be made by consensus of the experts of MPEG and Q.13/16.

Time Schedule


The timeline below is provided as a reference. While MPEG and Q.13/16 will make all efforts to keep the schedule, it should not be taken as an engagement on the part of MPEG as well as Q.13/16 to stick to it.



Time

Place

Expected Event

2010/01/22

Kyoto

Call for Proposals issued

2010/04/12




Deadline for proposal submission

2010/04/18

Dresden

Evaluation of proposals (in an Ad Hoc Group meeting)

2010/04/23

Dresden

Approval of first Working Draft

2010/07/30

Geneva

Approval of Committee Draft

2010/10/22

Guangzhou

Study on Committee Draft

2011/01/28

(KR)

Approval of Final Committee Draft

2011/04/25

Geneva

Study on Final Committee Draft

2011/07/21

Torino

Approval of Final Draft International Standard


Source Code and IPR

Proponents are advised that, upon acceptance for further evaluation, it will be required that certain parts of any technology proposed be made available in source code format to participants in the core experiments process and for potential inclusion in the prospective standard as reference software. When a particular technology is a candidate for further evaluation, commitment to provide such software is a condition of participation. The software shall produce identical results to those submitted to the test. Additionally, submission of improvements (bug fixes, etc.) is certainly encouraged.


Furthermore, proponents are advised that this Call is being made subject to the common patent policy of ITU-T/ITU-R/ISO/IEC (see www.itu.int/ITU-T/dbase/patent/patent-policy.html or ISO/IEC Directives Part 1, Appendix I) and the other established policies of the standardization organizations.

References:

[1]

N11230

Context and Objectives for Advanced IPTV Terminal (AIT)

[2]

N11231

Use Cases for Advanced IPTV Terminal (AIT)

[3]

N11228

Requirements for Advanced IPTV Terminal (AIT)

[4]

Nxxxxx

ISO/IEC 23006-2 MXM APIs

[5]

Nxxxxx

ISO/IEC 23006-4 MXM Protocols




Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©atelim.com 2016
rəhbərliyinə müraciət