- What are the various types of HAVi devices?
- What are the benefits of FAVs to users?
- Is a single IAV or FAV device capable of controlling multiple devices?
- Can any combination of IAVs and FAVs operate and interact in a HAVi network?
- Are there specific types of devices that need to be designed as IAV or FAV devices?
1. What are the various types of HAVi devices?
HAVi classifies Consumer Entertainment (CE) devices into four categories: Full AV (FAV), Intermediate AV (IAV), Base AV (BAV), and Legacy AV (LAV). HAVi-compliant devices are those in the first three categories, all other CE devices fall into the fourth category. Referring to the distinction between controllers and controlled devices -- FAVs and IAVs are controllers while BAVs and LAVs are controlled devices.
FAV -- FAV is an acronym for Full Audio Visual device. An FAV contains a complete set of the software elements comprising the HAVi Architecture. This device class generally has a rich set of resources and is capable of supporting a complex software environment. The primary distinguishing feature of an FAV is the presence of a runtime environment for Java bytecode. This allows an FAV to upload bytecode from other devices and so provide enhanced capabilities for their control. Likely candidates for FAV devices are Set-top Boxes, DTV receivers, general purpose home control devices, residential gateways, and home PCs.
IAV -- IAV is an acronym for Intermediate Audio Visual device. An IAV is generally lower in cost than an FAV and more limited in resources. IAVs do not provide a runtime environment for Java bytecode and so cannot act as controllers for arbitrary devices within the home network. However, an IAV may provide native support for control of particular devices on the home network.
BAV -- BAV is an acronym for Base Audio Visual devices These are devices that, for business or resource reasons, choose to implement future-proof behavior by providing uploadable Java bytecode, but do not host any of the software elements of the HAVi Architecture. These devices can be controlled by an FAV via the uploadable bytecode or from an IAV via native code. The protocol between the BAV and its controller may be proprietary or a standard device control protocol such as AV/C.
LAV -- LAV is an acronym for Legacy Audio Visual devices. These are devices that are not aware of the HAVi Architecture. LAVs generally use proprietary protocols that provide control-only functionality. Such devices can work in the home network but require that FAVs or IAVs act as an intermediary.
2. What are the benefits of FAVs to users?
Because FAVs have the ability to install Java applications on them, FAVs offer the following benefits:
- Forward Compatibility ("Future-proofing"). 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.
- Platform independence. Because Java is platform independent and the APIs are standardized by HAVi, Java applications will run on any FAV, regardless of manufacturer.
- Programmers support. Java is supported by a large community of developers and is being adopted by a growing number of standards bodies like DVB and ATSC. This will provide for a large base of potential application developers for HAVi.
- Link with the Internet and broadcast systems. Java is the key language for Internet-based applications. Standards bodies like DVB, ATSC and DAVIC are defining Java APIs to enable interactive applications to be downloaded to devices such as set-top boxes. When a Java API, as defined by HAVi, is implemented on a device, such a set-top box or an internet-enabled TV, these devices can interact with all the HAVi devices in the home.
3. Is a single IAV or FAV device capable of controlling multiple devices?
Yes, one IAV or FAV device can control multiple devices via multiple DCMs (for each target device).
4. Can any combination of IAVs and FAVs operate and interact in a HAVi network?
Yes. All the mechanisms in HAVi are designed to achieve interoperability that is equally supported by all FAVs and IAVs. IAVs and FAVs cooperate in a peer-to-peer fashion and there is no need for a special master device.
5. Are there specific types of devices that need to be designed as IAV or FAV devices?
No. Whether a HAVi device is built as an IAV or FAV is the choice of the manufacturer. However, on devices that already support Java (such as set-top boxes), it would be reasonable to expect this type of device to be designed as an FAV.
|
