1 / 14

Standardization of Common API for T-DMB receivers

Standardization of Common API for T-DMB receivers. May. 20. 2008 IEC/TC100/AGS, Washington DC, USA. Contents. Status of Standardization on T-DMB receivers Coverage of the Standardization. 2. Standardization - Status. A series of international standards on T-DMB receivers are under way

conor
Download Presentation

Standardization of Common API for T-DMB receivers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. StandardizationofCommon 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 • Series1 : IEC 62516-1: Terrestrial Digital Multimedia Broadcasting (T-DMB) Receivers - Part 1: Basic requirements (IEC 62516-1 published as an IS on 03/2009) • Series2 : IEC 62516-2: Terrestrial Digital Multimedia Broadcasting (T-DMB) Receivers - Part 2: interactivedata service using BIFS (Binary Format For Scene) (100/1540/NP is in circulation by 07/10/2009) •  Series3 : 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. Application Software High-level API Middleware OS BB Driver Board Support Package RF Tuner Baseband Application Processor SW HW Application Software High-level API Middleware OS BB Driver Board Support Package Application Processor RF Tuner Baseband SW HW

  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-DMBsoftware 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 => 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 TPEG Solution Provider App. Processor Solution Provider CAS Solution Provider CAS Solution Provider App. Processor Solution Provider CAS Solution Provider App. Processor Solution Provider • TS DeMux • A/V Sync • A/V decoding • API BIFS Solution Provider EPG Solution Provider Solution Porting Solution Porting Baseband Application Processor RF module Receiver manufacturer Receiver manufacturer Receiver manufacturer Control API Porting GUI , Application Porting BB solution Provider • RF/BB control API BB solution Provider • RF/BB control API BB solution Provider • RF/BB control API

  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 Source : DMB Monthly, 2009 Units Sold (in 10,000) Terrestrial Satellite Total Mobile Phone Car Navigation USB Dongle Other Mobile Device Laptop

  11. Number of Receiver Manufacturers Source : DMB Monthly, 2009 Car Navigation USB Dongle Other Mobile Devices Mobile Phone Laptop Total Year 2006 2007 2008

  12. App. SW App. SW App. SW App. SW Player Player Player Player TPEG BWS BWS TPEG Common API for T-DMB Common API for T-DMB Common API for T-DMB Common API for T-DMB OS OS OS OS Linux Linux Linux Rex WinCE WinCE WinCE Symbian HW HW HW HW USB ARM ARM ARM PC DSP DSP DSP Standardization – Variety of platforms Application service BWS DLS SLS EPG TPEG CAS EWS BIFS Visual radio Common API for T-DMB Hardware dependent part BB Ctrl Device Driver A/V Ctrl Application Processor BaseBand 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

More Related