Marlin provides an end-to-end digital rights management (DRM) development platform that is easy to use, efficient, and applicable to a variety of market implementations across content types, delivery mechanisms, format types and platforms.
It is based on a group of specifications and tools, including conformance test suites, reference implementations, and software development kits (SDKs) necessary to create a common DRM content distribution system. See below for an overview of the specifications.
For an example of how Marlin is typically implemented, see How Marlin Works.
With its developer community approach, Marlin delivers the most comprehensive and advanced rights management technology in the market today. Using Marlin, developers have the advantage of using industry-approved, standards-based, open DRM technology to create high-value services on a variety of devices with innovative revenue models.
At its core, Marlin is based on a general-purpose rights management architecture that allows for substantial flexibility and control in implementation. Marlin specifications define the capabilities and architecture so that devices and services can interoperate to provide consumers with valuable content options. In addition, wherever practicable, Marlin uses industry standards, including security standards from IETF, W3C, ISO, OASIS, and others.
The core system specifications, including underlying reference technologies, define elements common to most Marlin implementations.
The Marlin Core System Specification defines the basic components, protocols, and consumer domain model that enable the interoperability between Marlin-enabled devices and services. This specification is based on the Octopus and NEMO reference technologies (described below), which have been adapted for peer-to-peer device interactions.
The rights management within Marlin is based on a general-purpose DRM architecture (Octopus) that is extremely expressive and allows for flexible business rules. At the center of an Octopus system is a graph-based relationship engine. In Marlin, Octopus node objects are used to represent system entities (such as users and devices), and links between nodes represent relationships. The system of nodes and links is integral to managing where, how, and when content can be used in a Marlin system. Octopus is designed to run on various platforms, from smartcards to servers, being media format and cryptographically agnostic. It is extensible for future-proofing systems, easily configurable, optimized for small systems, and semantics-free.
NEMO is an acronym for Networked Environment for Media Orchestration. It provides a services-based framework for trusted connections between various components of a Marlin DRM system. Based on secure Web Services standards, NEMO defines service interfaces, service access policies, and support for trust relationships among distributed entities that play well-defined and certified roles. Through the use of the NEMO framework, Marlin components can leverage a consistent mechanism to ensure that messages are delivered with appropriate protection and are exchanged between entities that are properly authenticated and authorized. The services supported by NEMO may be operated together with other, application-specific media services that are not required to be NEMO-compliant.
Delivery system specifications define additional requirements for different types of delivery channels, such as mobile, IPTV, or broadband. For instance, the OMArlin specification bridges OMA-compliant devices with the Marlin technology. OMArlin enables interoperable download, streaming, sharing and consumption of content between OMA and Marlin DRM systems.
Other specifications define additional requirements for particular implementation needs. For instance, the Dynamic Media Zones specification identifies how to develop targeted advertising and subscription business models involving anonymous usage data collection.
To obtain more detailed information about Marlin technology, click here.