OCAP, the OpenCable Application Platform, is the middleware specification for US digital cable:

1. OCAP is an open standard and is Java based,
2. it is being deployed by cable operators in North America. Initial roll-out is underway. Full-scale deployment is likely to occur during 2008.
3. OCAP runs on set-top boxes and digital TVs, often referred to as "terminals", "hosts" or "receivers".

OCAP was developed by CableLabs with a number of the cable operating companies and software firms. OCAP 1.0 Profile is based on a European middleware standard, the DVB Multimedia Home Platform 1.0.3 (DVB MHP). OCAP is consistent with the DVB Globally Executable MHP (GEM) specification, 1.0.2, meaning that GEM-compliant applications will run on OCAP middleware.

The OCAP specification defines an application interface that includes all required APIs, content/data formats, and protocols up to the application level. OCAP applications are therefore expected to execute on all OCAP conformant devices creating an interoperable "write once" environment.

OCAP conformant terminals must also be OpenCable certified devices.

Bound , Unbound and Native OCAP Applications

OCAP specification identifies three classifications of applications which can run on an OCAP terminal:

• Bound applications are those bound to, or associated with, the currently tuned channel. When the viewer tunes away, the bound application must be terminated.

• Unbound applications are not tied to a particular channel. They do not go out of scope when the viewer tunes from a specific service.

• Native are applications written for a specific host.