HAVi Fast Track Role Of Java

1
HAVi Fast TrackRole Of Java
Home Audio Video interoperability
2
Ravi Gauba rgauba_at_arch.sel.sony.com
3
Overview

• Why Java was chosen?
• Java's role in Device Classification
• Role of Java in FAV
• Security
• Uploadable DCM Code Units
• Havlets

4
Why Java?

• Requirements for HAVi Bytecode
• Publicly available
• Choice of multiple vendors
• Specification should be stable
• Platform independent
• Support for future updates
• Industry standard

5
Javas role in Device Classes

• Full AV device (FAV)
• Requires Java runtime environment
• Set of Java packages as defined by HAVi
• Download and execute HAVi applications
• Download and execute DCM for BAV / LAV

Controller Devices

• Intermediate AV device (IAV)
• No Java specific requirements

• Base AV device (BAV)
• May provide uploadable java bytecode information
  in ROM

• Legacy AV device (LAV)
• Conventional devices with NO knowledge of HAVi

6
HAVi Architecture
Application
havlet
Application
Interoperability API (native binding)
Interop. API (Java binding)
DCM
Stream Mgr
Resource Mgr
Messaging
Registry
Event Mgr
DCM
DCM
DCM
DCM
DCM
org.havi...
optional
JVM
Level I UI Engine
DCM Manager
Porting Layer
1394 Manager
Vendor-specific Platform (RTOS)
Other Device Drivers
1394 Device Drivers
7
Java Packages in FAV

• Support Sun JDK 1.1
• Java Packages Supported
• java.lang java.util, as defined in JDK 1.1
• subset of java.io java.util.zip
• org.havi.constants,
• org.havi.types,
• org.havi.system,
• org.havi.Iec61883,
• org.havi.fcm.,
• May Support Level 2 UI (optional)
• org.havi.ui, org.havi.ui.event
• Subset of java AWT

8
Security

• HAVi does not define security
• Protection of a device from hostile and flawed
  program is the responsibility of the vendor
• Access Level
• Trusted
• System software elements
• Pre-installed software elements
• All DCMs and FCMs
• Untrusted
• Unverified installed software

9
DCM Code Unit

• Java or native code
• Native DCM code unit are proprietary and not
  defined by HAVi
• Only one DCM code unit is installed per BAV/LAV
  on the entire network
• Profile
• Transferred DCM Code unit size (jar file)
• Installed DCM Code unit space
• Installed DCM Working space

10
Installation of DCM Code Unit

FAV
DCM Manager



Registry

Messaging System
CMM
Havi Java Packages
JVM

iLink Bus

11
BAV device plugged

FAV
DCM Manager



Registry

New device
Messaging System
CMM
Havi Java Packages
JVM

Bus Reset Event
iLink Bus

BAV
SDD
12
Download DCM code

FAV
DCM Manager



Registry

DCM CodeUnit
Messaging System
CMM
Havi Java Packages
JVM

iLink Bus

BAV
SDD
13
Instantiate DCM and FCM

FAV
DCM Manager



Registry

DCM CodeUnit
DCM
Messaging System
FCM
CMM
Havi Java Packages
JVM

iLink Bus

BAV
SDD
14
Unplug BAV

FAV
DCM Manager



Registry

Gone device
DCM CodeUnit
DCM
Messaging System
FCM
CMM
Havi Java Packages
JVM

Bus Reset Event
iLink Bus

15
Uninstall DCM Code Unit

FAV
DCM Manager



Registry

uninstall
DCM CodeUnit
Messaging System
CMM
Havi Java Packages
JVM

iLink Bus

16
Application Module

• Provide interface to services
• Developed by device vendor and third party
• Run on IAV and FAV
• Java bytecode applications are uploaded to FAV
• Discovery of third party application module is
  proprietary
• Application developers have full access to HAVi
  services

17
Havlets

• Portable HAVi application
• Are extracted from Application and DCM modules
• Level 2, device-dependent user application
• Run only on FAV
• They need not run on the originating FAV
• HAVi defines only the install and uninstall APIs
  for Havlets
• Havlets receive only proprietary messages

18
Pointers

• HAVi Specification
• Chapter 3.5, 3.6, 7
• Appendix A
• HAVi websitesite
• http//www.havi.org
• Sun Java JDK 1.1

19
Home Audio-Video interoperability