HAVi Technical Overview

1
HAVi Technical Overview

• Presented by Jon Fairhurst, Sharp Laboratories of
  America
• Chairman of the Technical Steering Committee,
  HAVi Organisation
• jonf_at_sharplabs.com

2
What is HAVi?

• HAVi is
• An Organization Which Develops, Manages and
  Promotes the HAVi Specification
• A Middleware Specification Which Allows Digital
  A/V Devices to Interoperate
• HAVi is a Set of Software Element Definitions
  Which Provide Well Defined Services
• HAVi is a Set of APIs Which Allow Development of
  Distributed A/V Applications
• HAVi is a Set of Java Class Definitions Which
  Allow Remote Execution of Bytecode
• A Requirements Document which Ensures Compliance
• A Logo which Identifies Digital A/V Products as
  Interoperable

3
HAVi Goals Initial Requirements

• HAVi Was Developed To
• Allow A/V Products To Connect Digitally
  Intelligently
• IEEE-1394 / Firewire / i.Link
• Remote User Interface Supports Device Control
• Supports Distributed Applications Through
  Predefined Device Control Models
• Provide A Total A/V Interoperability Framework
• Supports a Wide Range of Products
• Simple/Flexible Device Model
• Interoperability Across Manufacturers and
  Operating Systems
• Allow Product Differentiation
• Future Proof

4
Connect A/V Products Digitally Intelligently

• IEEE-1394 / Firewire / i.Link
• High Speed - 100/200/400 MBPS
• Data Control
• Isochronous Streams
• Industry Standard
• By Using Only IEEE-1394, HAVi Maximizes
  Interoperability
• Remote User Interface Supports Device Control
• User Can Control All Devices From a Single Device
  Remote Control
• User Interface Is Fully Defined By Target Device
• Supports Distributed Applications Through
  Predefined Device Control Models
• Applications Can Coordinate Multiple Devices
• No More Flashing 1200!

5
A Total A/V Interoperability Solution

• Supports a Wide Range of Products
• Legacy Support - Legacy A/V Device (LAV)
• Inexpensive Products - Basic A/V Device (BAV)
• HAVi Elements are Passive
• Mid-Range Products - Intermediate A/V Device
  (IAV)
• HAVi Elements are Active
• High-End Products - Full A/V Device (FAV)
• Includes Java VM Built-In Classes
• Simple/Flexible Functional Device Model
• Devices are Modeled by Functional Control Modules
  (FCMs)
• Basic Functions Are Required
• Small Set of Optional Functions
• Custom FCMs are Possible

6
A Total A/V Interoperability Solution (cont.)

• Interoperability Across Manufacturers and
  Operating Systems
• HAVi Specification V1.0 is Complete and Available
• Developed by Consensus of Eight CE Companies
• HAVi is Middleware - OS Independence
• Java Bytecode - OS Independence
• Allow Product Differentiation
• Products May Offer Custom User Interfaces
• 1394 CMM Provides Low-Level 1394 Support
• Develop Your Own Proprietary Events
• Register Unique Devices
• Develop Custom DCMs FCMs
• Future Proof
• DCMs May Be Uploaded From Device / Downloaded
  From Internet
• All Software Elements Include Versioning API

7
HAVi Device Types

• Full AV Device (FAV)
• Download and execute all HAVi applications
• Download and execute DCMs

Controller- Capable HAVi Device

• Intermediate AV Device (IAV)
• Ability to communicate with other HAVi Devices
• Ability to execute limited applications
• Offers own control services
• Ability to host other known devices
• Ability to host legacy devices

• Base AV Device (BAV)
• Offers own control information in ROM

Controlled HAVi Device

• Legacy AV Device (LAV)
• Conventional devices w/ no HAVi SDD

8
HAVi Software Architecture - LAV
9
HAVi Software Architecture - BAV
10
HAVi Software Architecture - IAV
11
HAVi Software Architecture - FAV
12
Future Technical Work

• The Technical Steering Committee (TSC) Charter
  will be Presented for Approval at the Next Board
  Meeting
• If Approved, The HAVi Technical Steering
  Committee Will
• Be Staffed by Members of the Promoter Groups
• Submit Recommendations to The Board
• Make Technical Evaluations at the Request of the
  Board
• Manage Technical Working Groups which are
  Authorized By The HAVi Board
• Working Groups will have Well Defined Charters
  and Scope
• All HAVi Members May Join the Working Groups
• Initial Tasks for Working Groups are Likely to
  Include
• Fixing Any Problems Found in the Specification
• Simple Errors
• Interoperability Issues
• Completing the Compliance Documents
• HJA, L2 GUI
• Expansion of the HAVi Specification is Not
  Planned at This Time