Transcript HAVi

Introduction to
HAVi (Home A/V Interoperability)
배유석
([email protected])
인터넷정보가전연구부
컴퓨터S/W 기술연구소
Home Network Classification
▣ Data
Network
◈ Jini,
UPnP, HomeRF, Bluetooth
◈ USB
▣ A/V
Network
◈ HAVi,
VESA (HWW)
◈ IEEE1394
▣ Control
Network
◈ OSGi
◈ LonWorks,
X.10, CEBus
2
Public networks
PSTN, Internet
Connecting Everything
Powerful, but complex
infrastructure
Network
camera
HomePNA
Phone line network
Power line
network
Hub
Web
phone
Printer
IEEE 1394
HomeRF
Communications
and control
Camera
Entertainment
Center
Scanner
3
Media and Function Evolution
Standards will coexist
Multimedia
distribution
1394, fast RF,
other
Device sharing
Shared Internet access
Communications
Multi-player gaming
Home
Automation
Phone line, RF, Ethernet,
power line
X-10, CEBus
Control
-1998
Control + data
1999
Control + data
+ multimedia
2000+ 4
What’s HAVi?
▣ Abstract
◈ Consumer Electronics(CE) industry standard
◈ Support various vendor, brand’s Digital AV devices
◈ Transfer and manipulate digital AV data between
devices
◈ Not control network
–
cf. LonWorks (Lightning, Climate Control, and etc)
▣ History
◈ Sony, Matsushita, Philips, Thomson, Hitachi, Toshi
ba, Sharp, Grundig, Samsung, Sun Microsystems
◈ Core Spec is published in May 1998
◈ HAVi Spec. 1.0 is published in January 2000
◈ HAVi device & Demo in March 2000
5
Interoperability
▣ Interoperability
◈ HAVi
device detects each other
◈ HAVi protocol is used to communicate
◈ Various vendors will support HAVi to
cooperate
▣ Benefits
of interoperability
◈ User
will do only power-on
◈ Independent of vendor and brand
◈ Accept new device to network easily
6
Network Environment for HAVi
▣ IEEE-1394
◈ Backbone
–
–
–
–
–
–
of HAVi network
Plug-N-Play, Self Configuration
Bandwidth is 100-400Mbps
Asynchronous, Isochronous transfer protocol
FireWire(Apple), i.Link(Sony) : accepted for digital
devices
◈ How
–
bus
does HAVi relate to IP?
IP is open network protocol for distributed Internet
HAVi uses closed protocol for in-home network
Web Access API for HAVi devices with IP stack

Home Gateway with IP over 1394
7
HAVi Network
▣ Clustering
of IEEE-1394 devices
◈ I-TV,
Set-Top Box, Cable Modem - controller
◈ Camcorder, Digital audio, VCR - controlled device
◈ Configured in distributed environment
8
HAVi Speciality
▣ Legacy
devices
◈ Support
non-HAVi 1394 devices
▣ Future-proof
◈ Accept
–
–
–
new device easily
SDD (Self Describing Data)
JRE (Java Run-time Environment)
DDI (Data Driven Interaction): Independent UI of device
▣ Plug-and-Play
◈ Detect
new device and configure network
automatically
▣ Flexible
◈ Can
use various devices of vendor, brand
◈ Support multiple H/W platforms (from CEs to
Servers)
9
HAVi SDD (Self Describing
Data)
▣
What?
ROM
◈
base(FFFF F000 0000)
◈
▣
Root
directory
Configuration
◈
Root directory
–
◈
Instance
directory
HAVi
unit directory
IEC 61883
unit directory
IEEE 1212 addressing scheme
Configuration ROM
Instance Directory
–
–
◈
HAVi unit directory offset
IEC61883 unit directory offset
HAVi unit directory
–
◈
vendor, Model_ID, instance
directory offset, unit directory
offset
spec_id,version, DCM_Profile,
DCM_Reference, Icon
IEC 61883 unit directory
–
spec_id, version, …
10
HAVi Model
▣ Control
Model
◈ Controller(FAV,
IAV), Controlled
device(BAV, LAV)
◈ Embedded DCM(non-Java), Uploaded
DCM(Java)
▣ Device
Model
◈ DCM(Device
Control Module)
◈ FCM(Functional Component Module)
▣ Device
◈ FAV
Classification
> IAV > BAV > LAV
11
HAVi Configuration
12
HAVi Basic Definition
▣ Software
Element
◈ middle
layer between platform specific
APIs and platform independent
applications
◈ network management(CMM),
◈ device abstraction(DCM, FCM)
◈ inter-device communication(MSG)
◈ UI management(DDI, Havlet)
13
Device Control Module
▣ an
interface for controlling general
functions of a device
▣ has a zero or more FCMs
▣ registered in the Registry and
communicate with other HAVi objects
via the Messaging System
14
Functional Component Module
▣ an
interface for controlling specific
functional component of a device
▣ represent the functionality of an device
▣ registered in the Registry and
communicate with other HAVi objects
via the Messaging System
15
HAVi Software Architecture
16
Communication Media Manager
▣ Packet
Transfer, Receive
◈ Low-level
Packet Send and Receive using 1394
bus
◈ Read, Write, Lock transaction
◈ Asynchronous Packet Receive Notify etc.
▣ GUID(Global
Unique ID)
◈ Unique
ID for a 1394 device
◈ NodeId is changed but GUID is fixed
◈ node-vendor ID (24bits)+unique chipset
number(40bits)
▣ Network
Reset
◈ Posted
when network topology is changed
◈ Send notification to Event Manager
17
Messaging System
▣ Message
◈ SEID
–
–
Send Layer
(Software Element ID)
Unique ID for All S/W Elements
GUID(64bits) + SwHandle(16bits) allocated by MSG
◈ Message
–
Transfer mode
simple, reliable (include synchronize)
◈ TAM(Transportation Adaptation
–
–
–
Module)
The unit of transfer between two S/W elements
Fragmentation and ordering of a HAVi message
IEC 61883 FCP(Function Control Protocol) Packet
18
General HAVi Message Format
▣
▣
▣
▣
▣
DestSEID : Receiving SE, SourceSEID : Sending SE
ProtocolType : HAVi_RMI
MessageType: simple, reliable
MessageNumber: Unique 8bit number to distinguish message
MessageLength :The Length of MessageBody(header,
parameters)
19
Event Manager
Internal
SE
Event
Manager
MSG
▣
SE registers interesting events to the Event Manager
▣
SE posts a Event to the local Event Manager
Event Manager has a Internal table for registered
Events
If a posted event is global then forward to all Event
Managers
▣
▣
20
Registry
SE
MSG
▣
Registry
Register
Retrieve
Retrieve
Get
Database
MSG
Has Registry Database
◈
(SEID, Attribute) Records
–
◈
attribute : ATT_DEVICE_MANUF, “sony”
Support simple or complex query API
21
Device Control
DCM
DDI
controller
FCM
IAV+
IAV- or FAVDDI
protocol
▣
Proprietary
Protocol
1394
havlet
FAV+
Controlled
device
All HAVi devices have DCM
◈
◈
◈
◈
Support APIs for UI, device control
FCMs exist related a DCM
Control : IAV (embedded DCM), FAV (JRE)
UI - IAV : DDI controller, FAV : havlet or Java application
22
DCM Code Unit
DCM Manager
DCM Code Unit
FCM 1
FCM n
DCM
CMM
▣
Registry
DCM code unit
◈
◈
◈
◈
Code Unit file (DCM, FCM, install code), Profile file
self-extracted JAR
HAVi device has SDD which contains DCM code unit
DCM manager gets some DCM code unit when power-up
23
DCM Manager
▣ Manages
DCM Code Units
◈ Install/Remove
DCM Code Unit for a HAVi device
◈ Check Profile, install Code Unit ->DCM ->FCM
▣ Preference
Management
◈ Only
one Code Unit exists on a HAVi Network
◈ Choose a Host which Code Unit will be installed
–
–
Find a host has same vendor as device : FAV->IAV
If above conditions are same then choose the host has
lower load
◈ Choose
–
–
the Code Unit will be installed
SDD has DCM Code Unit or URL
URL -> SDD’s DCM Code Unit
24
Stream Manager
▣ provide
(1/2)
end-to-end isochronous streaming
▣ Terms
◈ Plug
–
–
–
◈
Connection
–
–
◈
Transport system (like IEC61883, INTERNAL, CABLE)
Transmission format
–
◈
Media representation (like CD audio, video, etc)
Transport type
–
◈
internal connection, external connection
fc plug -> device plug ---> device plug->fc plug
Stream type
–
◈
component which a stream is coming in or going out
FC plug, device plug
source plug, sink plug
Transmission protocol (like IEC61883, FMT_FDF)
Channel
–
Resource provided by a transport mechanism to build
connection
25
Stream Manager
Stream
manager1
DCM
plug1
(2/2)
DCM
plug2
FCM
plug1
Controlled
device1
▣
Host 1
Stream
manager2
FCM
plug2
Host 2
Controlled
device2
Support all APIs for end-to-end streaming
◈
◈
◈
◈
◈
internal connections, external connections
Manage transport system resources
Manage connection map
Check plug compatibility
Recovery all connections when Network Reset occurs
26
Resource Manager
(1/2)
▣ Definition
◈ Resource
–
–
Network Resource like bandwidth, channel
Device Resource is FCMs
◈ Reservation
–
–
To use a service, reserve all resources for it
Client, contender, all-or-nothing
◈ Sharing
–
–
Some devices permit multiple clients to share it
Access: primary (full control), secondary (limited control)
◈ Negotiation
–
–
–
and Preemption
NIR(Non-Intrusive Reservation)
NIR fails then negotiate with Resource Manager
If client allows preemption then preempt it or fails
27
Resource Manager
▣
(2/2)
Reservation
◈
◈
◈
◈
Client1 gets the information of FCM (VCR2) from Registry
Try NIR through RM1
Preemption request to client2 through RM1
RM1 reserves FCM (VCR2) through RM2
28
Similar Technologies
▣ Jini
(Sun Microsystems)
◈ Infrastructure,
▣ UPnP
(MS, Intel)
◈ Discovery,
▣ OSGi
Description, Usage
(Cisco, Sun)
◈ Open
▣ HWW
Programming Model, Service
Service Gateway
(Samsung)
◈ IP-based
▣ LonMark
◈ Control
VESA-HN
(Echelon)
network: LonWorks
29
Future Home Network
HP develops software to allow
devices with Java execution
Environment to run under
UPnP (April 1999)
Jini
UPnP
HAVi
Sony, Sun and Philips agree to
develop gateway software
(January 1999)
Microsoft announces interconnections
with HAVi under UPnp specification
(January 1999)
30
Conclusion
▣ HAVi
◈ Connects
Digital CEs with IEEE 1394 bus
◈ Supports Intelligent devices and Legacy
devices
◈ Has Middleware to support interoperability
◈ It is easy to accept advanced device (with
JRE)
◈ Has closed in-home network protocol
◈ Can connect to outside through a Gateway
(Modem, Web APIs)
31
Q&A