- API
- Application Programming Interface.
- AV (device)
- Audio / Video (device)
- BAV
- BAV is an acronym for Base AV (device).
BAV devices are simple and inexpensive devices that do not have sufficient local resources to implement all the HAVi APIs and protocols. BAVs therefore rely on the more powerful FAV (Full AV) devices to install and execute their DCM.
A typical example of a BAV would be a digital still picture camera.
BAV devices are 'HAVi aware' but need to implement only a very small part of the HAVi protocols.
BAV devices can always be directly connected to the HAVi network and they carry within themselves their own DCM written in Java. So, provided that there is at least one FAV (Full AV) in the HAVi network with sufficient resources to install the DCM, a BAV is controllable.
- CE
- Consumer Electronic (device)
- DCM
- Device Control Modules.
A Device Control Module (DCM) is a Software Element that is installed and executed on a HAVi device that provides control over device-specific functionality, (such as a VCR or a camera) via the HAVi-defined APIs (such as the "PLAY" API of a VCR). DCMs are installable Software Elements, which means that their presence depends on which devices or functionality is actually present in a particular HAVi network.
In principle there can be multiple DCMs for one particular device present in a HAVi network. When a device is inserted or powered up in the network, all IAVs and FAVs will check to determine if they have a DCM for that device, and will then negotiate with each other as to which DCM will be installed for the device, and on which IAV or FAV it will be installed.
Only one DCM can be installed at any time for each particular device. This selection and installation process is controlled by the DCMs on the IAVs and FAVs, however, HAVi offers several user definable preferences settings for this process.
- DDI
- Data Driven Interaction
With DDI, an application or DCM can offer a DDI description of its UI. This description can be retrieved simultaneously by any HAVi device with a display. The user can interact with the UI in a way that is completely local to the HAVi device with the display. Such interaction will cause messages to be sent to the remote DCM or application that will interpret these messages and control the activity of the application or device. Any DDI description can be displayed on any type of display. Each display will match the DDI description of the UI to its own capability, which can vary from a high end graphics screen on a TV, to a simple text-only LCD screen.
Changes in the UI due to user actions or unsolicited changes in the state of the device (for example, if a user pushes a button directly on the device, or an application calls a control API of the DCM) are signaled to the display to indicate that new information has to be displayed.
- DV
- Digital Video
- Event Manager
- One of the Software Elements that provide certain functionality. In addition to the Event Manger, the Software Elements that are needed for interoperability between HAVi devices are the
- Messaging System
- Registry
- Resource Manager
- Stream Manager
- DCM
- FAV
- FAV is an acronym for Full AV device. This would be a device, such as a set-top box, that is designed to have Java applications installed on it, thereby adding specific functionality to it.
- FCM
- Functional Component Modules
- Future-proof
- The ability of a device, or a system of devices, to gain additional functionality or features by installing new or upgraded software (such as Java applications) onto it. This means that devices do not become obsolete as new devices come onto the market - they can be upgraded with new features.
- GUI
- Graphical User Interface
- HAVi
- HAVi is an acronym for Home Audio Video Interoperability.
- HAVi-enabled
- Any consumer Electronic (CE) device that is designed and built to conform to the HAVi specifications for interactivity.
- HAVi Specification (Spec.)
- The HAVi specification is a consumer electronics (CE) industry standard that will ensure that digital audio and video devices that conform to this standard, regardless of manufacturer, will have complete interoperability when connected via a network in the consumer's home.
The HAVi specification document can be downloaded from the Sony external web site: http://www.sony.co.jp/HAVi/
- Havlet
- A GUI JAVA API. A Havlet enables a GUI to be displayed on a HAVi device that has a display.
- IAV
- IAV is an acronym for Intermediate AV (device). This would be a low-cost device with more limited functionality than an FAV. An IAV would have vendor-specific functionality built into it, but would not have the capability of allowing additional, or upgraded JAVA applications to be installed on it by the user. However, the ability to upgrade such a device would still be possible, if the vendor provided a means to install such applications or DCMs. These applications or DCMs would most likely be platform specific, so they would have to come from that specific vendor.
- IEEE-1394
- IEEE-1394 (also referred to as i.LINKTM or FireWireTM) is a specification for data transfer between devices. It is the underlying network technology for the HAVi protocols as well as for the transport of the real-time AV streams.
- IP
- Internet Protocol
- LAV
- LAV is an acronym for Legacy AV devices.
LAV devices are existing devices that were designed prior to the development of HAVi and therefore are not 'HAVi aware'. Typical examples are current DV camcorders.
- Messaging System
- One of the Software Elements that comprise the basic mechanisms in HAVi to achieve interoperability. Each element provides a certain functionality. The Software Elements that are needed for interoperability between HAVi devices are the Messaging System, the Registry, the Event Manager, the Resource Manager, the Stream Manager and the DCM.
- Registry
- One of the Software Elements that comprise the basic mechanisms in HAVi to achieve interoperability. Each element provides a certain functionality. The Software Elements that are needed for interoperability between HAVi devices are the the Messaging System, the Registry, the Event Manager, the Resource Manager, the Stream Manager and the DCM.
- Remote User Interface
- A Remote User Interface enables a user to interact with an application via any HAVi device in the network that has a display. For example, a user could program the VCR in the living room from his TV in the bedroom, again, regardless of which manufacturer made either device
- Resource Manager
- The Resource Manager is a powerful feature that handles possible resource conflicts, such as when applications want to control the same DCM. The Resource Manager allows for the possibility of sharing devices. The sharing function is determined by the devices themselves. An example is a set-top box that can simultaneously select different TV programs in the same Transport Stream. The Resource Manager also handles conflicts that could occur, such as when multiple applications attempt to program a VCR (so called Scheduled Actions), or if there are conflicts that arise due to HAVi network resource or bandwidth issues.
- Software Elements
- Software elements are basic mechanisms in HAVi to achieve interoperability. Each element provides a certain functionality. The Software Elements that are needed for interoperability between HAVi devices are the Messaging System, the Registry, the Event Manager, the Resource Manager, the Stream Manager and the DCM.
- Stream Manager
- One of the Software Elements that comprise the basic mechanisms in HAVi to achieve interoperability. Each element provides a certain functionality. The Software Elements that are needed for interoperability between HAVi devices are the Messaging System, the Registry, the Event Manager, the Resource Manager, the Stream Manager and the DCM.
- UI
- User Interface
- Web Access APIs
- Web Access APIs are API's that can be implemented by HAVi devices to enable any HAVi device in the home (such as PCs or internet-enabled TVs) to have access to the internet, without requiring the device to have an IP stack itself. Through these APIs, the Internet protocols such as HTTP and FTP are encapsulated and delivered to these HAVi devices.
-
|
