Standardization of Common API for T-DMB receivers

1
Standardization ofCommon API for T-DMB receivers

• May. 20. 2008
• IEC/TC100/AGS, Washington DC, USA

2
Contents

• Status of Standardization on T-DMB receivers
• Coverage of the Standardization

2
3
Standardization - Status

• A series of international standards on T-DMB
  receivers are under way
• Series 1 IEC 62516-1 Terrestrial Digital
  Multimedia Broadcasting (T-DMB) Receivers - Part
  1 Basic requirements
• (IEC 62516-1 published as an IS on 03/2009)
•  Series 2 IEC 62516-2 Terrestrial Digital
  Multimedia Broadcasting (T-DMB) Receivers - Part
  2 interactive data service using BIFS (Binary
  Format For Scene)
• (100/1540/NP is in circulation by 07/10/2009)
•  Series 3 IEC 62516-3 Terrestrial Digital
  Multimedia Broadcasting (T-DMB) Receivers - Part
  3 Common API for T-DMB receivers (Preparation of
  NWIP is required)

3
4
Standardization - Why needed? (1)

• There are many receiver chipsets in the market
• They have their own Command Set API Solution for
  the development of T-DMB Software

5
Standardization - Why needed? (2)

• If the T-DMB Receiver chipset is changed, the
  software development cycle has to be started all
  over again to accommodate this
• new hardware.

6
Standardization - Why needed? (3)

• There are various kinds of receiver chipsets in
  the market
• They have their own Command Set API Solution for
  the development of T-DMB receiver Software
• This causes heavy dependence of T-DMB software
  on receiver chipsets
• If the T-DMB Receiver chipset is once changed,
  the software development cycle has to be started
  all over again to accommodate the new hardware
• gt Standardization of Common Command Set API is
  required

7
Standardization - Why needed? (4)

• Common API Standards in relevant technologies
• DAB DCSR (Command Set API for Receivers)
• MediaFLO Receiver API
• DVB ETSI ES 201 812 MHP Specification
• DVB platform API

8
Applications of Common API of T-DMB
9
Standardization - Why needed? (4)

• T-DMB will be serviced not only in Korea, but
  also in Norway, France, and Indonesia soon as
  well.
• In addition to video delivery, T-DMB will be able
  to provide various kinds of additional services
  such as visual radio, BIFS, TPEG, etc.
• Implementing these services in software requires
  a significant amount of time and effort.
• A common API needs to be standardized for these
  application services in order to make
  implementation of inter-operable and reliable
  T-DMB software easier.

10
Receiver Sales
11
Number of Receiver Manufacturers
12
Standardization Variety of platforms
12
13
Coverage of the Standard Series 3

• Common API for T-DMB needs to include
• Standardization of Command Set API for T-DMB
  Receiver (RF/Baseband)
• Standardization of Common API for T-DMB Audio
  Service (Visual Radio)
• Standardization of Common API for T-DMB Video
  Service
• Standardization of Common API for T-DMB
  BIFS/TPEG/BWS/EWS/DLS/SLS Service
• Standardization of Common API for T-DMB CAS
  Solution

13
14
Thank you
IEC/TC100/AGS
2008-10-10
14