BD-J allows for more sophisticated bonus content on Blu-ray Disc titles than standard DVD, including network access, picture-in-picture and access to expanded local storage. Collectively, these features (other than internet access) are referred to as "Bonus View", and the addition of internet access is called "BD Live". BD-J was developed by the Blu-ray Disc Association. All Blu-ray Disc players supporting video content are required by the specification to support BD-J.[1] Starting on October 31, 2007, all new players are required to have hardware support for the "Bonus View" features, but the players may require future firmware updates to enable the features. "BD Live" support is always optional for a BD player.[2]
Sony's PlayStation 3 has been the de facto leader in compliance and support of BD-J, adding Blu-ray Profile 1.1 support with a firmware upgrade, used to showcase BD-Live at CES 2008 in January.
The invocation of BD-J Xlets are triggered by events occurring around them—for example, by the selection of a film title, or by the insertion of a new disc. Xlets in turn can then call other Xlets into play.
Security in BD-J is based on the Java platform security model. That is, signed applications in JARs can perform more tasks than non-signed, such as Read/Write access to local storage, network access, selection of other titles on the BD-ROM disc, and control of other running BD-J applications.
Xlets (as part of the CDC Personal Basis Profile) have no GUI (i.e. no AWT widgets such as java.awt.Button), so additional classes are called into play for generating animation and GUI. The BD-J uses the Havi UI device model and widget set for remote control use, but it is extended to allow for the BD supported resolutions and BD supported A/V controls.
BD-J has classes that allow the user to synchronize accurately to specific frames in the film.
There are two types of video synchronizations allowed, one called "loose synchronization", which uses a call back method and is accurate to within several frames of the event, and the other being "tight synchronization", which uses the package org.bluray. Tight synchronization allows applications to synchronize accurately to the exact frame using timecodes from the package javax.media.Time of JMF (Java Media Framework).
A BD-J application's GUI can be operated with a remote control with a required set of keys and an optional pointing device. The set of required keys includes at least the keys needed to support the User Operations in HDMV[expand acronym] applications.
The GUI framework in BD-J includes the HAVi(6) UI framework mandated by GEM; it is not a desktop GUI framework like SwingorAWT. The GUI framework is based on the core of AWT as specified by PBP, but the widget set includes mechanisms for remote control navigation from GEM and easy customization of look and feel from HAVi.
BD-J includes a media framework similar to JMF for the playback of media content related to the BD-ROM disc. It is assumed that the BD-ROM disc will be the prime source for media files, but it will not be the only one; other sources could be the studio's web server and local storage.
BD-J includes standard Java libraries for decoding and displaying images in JFIF (JPEG), PNG and other image formats. These images can be displayed on the Java graphics plane using standard Java graphics functions. An image can also be rendered in the background plane using a BD-J specific package.
Text can be rendered using standard Java text functions. These text-rendering functions are extended with a more advanced text layout manager that integrates with the BD-J UI framework. The text is rendered using a vector-based font either coming from the disc, the player (default font) or downloaded from the network.
Button sounds from HDMV[expand acronym] can also be used by the Java UI framework. Sound files can be loaded and rendered as a reaction to the user pressing a key, or as a reaction on a marked event related to the film—or as a reaction to any event generated by a BD-J Application.
Authenticated applications can use a (signed) permission request file to acquire permissions that go beyond the BD-J sandbox. Permissions can be acquired for:
Reading and writing to local and system storage
Using the network connection (to connect to defined servers)
Access of the file system on the BD-ROM disc
Title selection of other titles on the BD-ROM disc
Control of other running BD-J applications
BD-J applications can use the java.net package to connect to servers on the Internet. The physical connection might differ between implementations e.g. Ethernet, telephone line, etc. At the network level, TCP/IP is supported and the HTTP protocol may be used. Moreover, the Java package for secure connections is included (JSSE) as part of the BD-J platform. Before a BD-J application can use the network connection, it must be authenticated and have suitable permission to use the network.
The websites to which the application will go are under full control of the Content Provider. This control is guaranteed in two ways:
Only (disc) authenticated BD-J applications are allowed to run when the disc is played. The application controls the use of the network connection.
In addition, permissions defined on the disc can restrict the use of the (TCP/IP) network connection to certain sites.
BD-J will include support for storage. Two flavors of storage are included: mandatory System Storage and optional Local Storage. All storage is accessed using methods from the Java IO package. The path for local storage is as specified by [GEM].
System storage is storage that will be present in all BD-J players. The required minimum size of this system storage will permit storage of application data like settings, high-scores etc. It will not be big enough to store downloaded AV material. For this purpose, optional local storage is available. Typically system storage will be implemented using Flash memory and the optional local storage will be implemented on a HDD.
Since storage is a shared resource between all discs played on the player, Java access control is part of BD-J. BD-J applications can only access a disc specific part of the storage space and cannot access the part belonging to other discs.
Content authors have a variety of development strategies available, including the use of traditional Integrated Development Environments (IDEs) like NetBeansorEclipse, non-programming graphical environments similar to Macromedia Director, or via rendering engines which consume standard data formats such as HTML, XML, or SVG. Having a full programming environment available on every Blu-ray Disc player provides developers with a platform for creating content types not bound by the restrictions of standard DVD. In addition to the standard BD-J APIs, developers may make use of existing Java libraries and application frameworks, assuming they do not use features outside the constraints of the BD-J platform, include that Java ME only supports Java version 1.3 class files.
A set of freely available tools that allow Java developers to produce complete disc images incorporating BD-J is available from the HD Cookbook Project.[3] In order to test content in a typical development environment (MS Windows), one needs either a PlayStation 3 or a third-party software player for Windows, paying attention to player versions to ensure that the player supports BD-J.[4][5][6]
Because of the many different standards and components involved, creating unified documentation on BD-J has proven to be a challenge.[7][8]
The BD-J environment is designed to run Xlets with non-javax.* packages available to take advantage of the features particular to this platform beyond that defined by Java TV.
A developer might choose to use not javax.* packages and instead use:
HAVi classes in package tree org.havi.*: alternative classes to obtain, for example, an org.havi.ui.HScene far beyond what is provided by javax.tv.graphics.TVContainer (they are both extensions of java.awt.Container)
Digital Video Broadcasting (DVB) classes in package tree org.dvb.*: alternative classes to, for example, the org.dvb.event.UserEventListener interface rather than java.awt.event.KeyListener for support for key presses and keycodes specific to popular CDC devices.
Blu-ray Disc classes in the package tree org.bluray.*: the DAVIC and DVB classes depend upon to recognize additional events peculiar to the BD-J platform such as popup menus and to locate media on the Blu-ray disc.
DAVIC API classes in package tree org.davic.*: A small set of classes wrapping or extending other network and media resources peculiar to interactive TV the HAVi, DVB and Blu-ray classes use for locators and specialized exceptions beyond the realm of JMF (such as content authorization).
A working example of a program using some features from each of the class trees would be the BdjGunBunny Xlet (a very simple version of Space Invaders using an image of a rabbit as the shooter and turtles as the targets) provided as an example in the Java ME 3.0 SDK.
importjavax.tv.xlet.XletContext;importorg.havi.ui.HScene;importorg.havi.ui.HSceneFactory;importjava.awt.Container;importjavax.tv.graphics.TVContainer;// Getting a container for the screen could bepublicvoidinitXlet(XletContextcontext){// Java TV API to be compatible with Java TVTVContainerscene=TVContainer.getRootContainer(context);// Or for BD-J, to utilize HAVi features not available in Java TVHScenescene=HSceneFactory.getInstance().getDefaultHScene();// Or perhaps more generally...Containercontainer=null;booleanrealBDJ=true;if(realBDJ)container=HSceneFactory.getInstance().getDefaultHScene();elsecontainer=TVContainer.getRootContainer(context);...}
and the same for the other non-javax.* packages. Likewise, when trying to play a video, one might call the Blu-ray and DAVIC utility rather than using generic JMF:
importjavax.media.Player;importorg.bluray.net.BDLocator;importorg.davic.media.MediaLocator;MediaLocatorstars=newMediaLocator(newBDLocator("bd://0.PLAYLIST:00003"));Playerplayer=Manager.createPlayer(stars);// Rather than traditional and portable but more limited pure JMFimportjava.net.URL;importjavax.media.Manager;importjavax.media.Player;PlayermediaPlayer=Manager.createRealizedPlayer(newURL("file:/mymovie.mov"));
