Interactive TV standards /
For any digital TV developer or manager, the maze of standards and specifications related to MHP and OCAP is daunting-you have to patch together pieces from several standards to gather all the necessary knowledge you need to compete worldwide. The standards themselves can be confusing, and contain m...
Clasificación: | Libro Electrónico |
---|---|
Autor principal: | |
Otros Autores: | |
Formato: | Electrónico eBook |
Idioma: | Inglés |
Publicado: |
Amsterdam ; Boston :
Elsevier/Focal Press,
2005.
|
Temas: | |
Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
Tabla de Contenidos:
- Cover
- Acknowledgments
- Permissions
- Trademarks
- Table of contents
- Introduction
- Intended Audience
- Book Organization
- Versions
- 1 The Middleware Market
- Why Do We Need Open Standards?
- Driving Forces Behind Open Standard Middleware
- Standards in DTV
- Correcting the Fragmented ITV Market
- What Are DVB and CableLabs?
- The Digital Video Broadcasting Project
- DVB-MHP: The Multimedia Home Platform
- CableLabs
- OpenCable Applications Platform (OCAP)
- A History Lesson: The Background of MHP and OCAP
- The MHP Family Tree
- JavaTV: A Common Standard for DTV
- Harmonization: Globally Executable MHP
- The Difficult Part of Standardization
- Intellectual Property and Royalties
- Where Do We Go from Here?
- Open Versus Proprietary Middleware
- 2 An Introduction to Digital TV
- The Consumer Perspective
- Customizable TV
- Understanding DTV Services
- Producing DTV Content
- Elementary Streams
- Transport Streams
- The Multiplexing Process
- Carrying Transport Streams in the Network
- Energy Dispersal
- Error Correction
- Modulation
- Cable, Satellite, and Terrestrial Broadcasting
- Broadcasting Issues and Business Opportunities
- Subscriber Management and Scrambling
- Access Issues
- The Subscriber Management System
- The Return Channel: Technical and Commercial Considerations
- 3 Middleware Architecture
- MHP and OCAP Are Not Java
- They Are Not the Web, Either
- Working in the Broadcast World
- The Anatomy of an MHP/OCAP Receiver
- The Navigator
- Differences in OCAP
- A New Navigator: The Monitor Application
- Modules in the Execution Engine
- Architectural Issues for Implementers
- Choosing a Java VM
- Sun's JVM or a Clean-room Implementation?
- The Impact of the Java Community Process
- Portability
- Performance Issues
- 4 Applications and Application Management
- An Introduction to Xlets
- Xlet Basics
- Xlet Contexts
- Writing Your First Xlet
- Dos and Don'ts for Application Developers
- Application Signaling
- Extending the AIT
- Controlling Xlets
- Registering Unbound Applications
- Making Applications Coexist Reliably
- Pitfalls for Middleware Developers
- 5 The JavaTV Service Model
- What Happens During Service Selection?
- Abstract Services
- Managing Abstract Services in OCAP
- Registering Applications
- Selecting Abstract Services
- 6 Resource Management Issues
- Introducing the Resource Notification API
- Using the Resource Notification API
- Handling Resource Contention
- Resource Management in OCAP
- Resource Contention Before Version I12
- Resource Contention in Later Versions
- Common Features of Resource Contention Handling
- An Example of a Possible Resource Contention Solution
- Resource Management Strategies in OCAP
- Merging OCAP and MHP Resource Management
- 7 Graphics APIs
- The Display Model in a DTV Receiver
- HScreens and HScreenDevices
- Configuring Screen Devices
- Screen Devices and Resource Management
- A Practical Example of Device Configuration
- HScenes and HSceneTemplates
- Creating.