Cloakware DRM Solutions - OMA DRM

Cloakware is committed to developing and deploying world-class standards-based and proprietary DRM solutions. Cloakware OMA DRM 1.0 and 2.0 Clients are based on a progressive cross-platform architecture. They have been designed to meet the most stringent operator and device requirements, while providing a simplified integration process on mobile devices — from less robust feature phones to the highest performance smartphones.

As a pioneer in DRM, Cloakware has an unrivaled depth of experience in mobile DRM. From client-side deployments on 2G, 2.5G, and 3G devices to server side rollouts for global network operators, Cloakware engineers have played key roles in the earliest implementations of mobile DRM.

Cloakware OMA DRM 1.0 Client

> OMA DRM 1.0 datasheet
> OMA Windows Mobile™ datasheet
> OMA Android™ datasheet

Cloakware OMA DRM 1.0 Client fully implements the OMA DRM 1.0 specification. It supports all content delivery methods, enforces content licenses, and provides mechanisms to manage super-distribution. Cloakware has also incorporated several proprietary enhancements, including:

Cloakware OMA DRM 2.0 Client

> OMA DRM 2.0 datasheet

Cloakware OMA DRM 2.0 Client builds on the foundation of the first client. It fully implements the OMA DRM 2.0 specification, while upgrading core architecture. As a result, the OMA DRM 2.0 Client continues to offer high performance in a low-footprint package. Cloakware’s product development places a premium on cross-platform portability, a positive user experience, and easy integration. The OMA DRM 2.0 Client perpetuates these features while incorporating OMA DRM 2.0 features such as:

Architecture

Cloakware OMA DRM Clients are built on a progressive, cross-platform client architecture. They are designed to meet a range of device requirements, from less robust feature phones to the highest performance smartphones. The tiered architecture separates platform-specific from platform-neutral components. This method of compartmentalizing components promotes easy portability across hardware and software platforms. Cloakware OMA DRM Clients are designed for optimal customization and extension. They can be modified in both UI presentation and core functionality.

Client components

Cloakware OMA DRM Clients are made up of a strategic set of software components and APIs. A fully implemented solution will include three main components: Content Ingestion Agent, DRM-enabled media application, and DRM Engine.

Content ingestion agent

The Content Ingestion Agent, using the Content Ingestion API, is primarily responsible for processing received OMA content and licenses, verifying that incoming content can be rendered on the device, handling ROAP sequences and processing security certificates (OMA DRM 2.0).

OMA media application

A media application uses the Content API to enable consumer access to OMA content. Functionality in the Content API includes: checking for valid licenses and decrypting content files, viewing content metadata, sharing OMA-protected content with peers, viewing license details, and renewing expired licenses.

DRM engine

The DRM Engine contains the core logic for managing OMA-protected content, responding to requests by content ingestion agents and OMA media applications via the two APIs. The DRM Engine saves content files on the device, updates OMA databases, evaluates licenses and tracks usage, decrypts content for rendering and validates security certificates.

Features

• Accepts all OMA delivery types: separate delivery, combined delivery, forward lock.
• Supports complex delivery schemes, such as multipart encrypted files with multiple media and/or licenses.
• Supports domain licensing, including multiple domains, for content use across consumer groups or multiple devices.
• Incorporates user-friendly UI components and messages for a non-intrusive downloading and licensing experience.
• Supports OMA DRM 2.0 content preview functionality, enabling consumers to sample content prior to purchasing.
• Provides tools to manage peer-to-peer sharing and licensing of shared content.
• Supports consumer use of removable storage devices and media.
• Implements OMA DRM 2.0 ROAP security for registration, rights issuance, and revocation, with bilateral authentication/authorization based on DRM PKI infrastructure.
• Both OMA DRM Clients encrypt all OMA content and key it to the device for security.
• Both OMA DRM Clients incorporate a secure clock to maintain timed-license integrity.
• Maintains an efficient license database on the device, with automated garbage collection to remove expired licenses and optimize storage consumption.
• Able to support CMLA compliance and robustness rules.
• Provides streamlined device integration for commonly used platforms.
• Supports 27 languages and is easily localizable.
• Uses a tiered architecture for portability and customization across platforms.
• Includes detailed, readable documentation to meet deployment needs, including an integration guide and references

• Security Impacts of Set-Top Boxes
• Sustainable Device Security
• Advantages of White-Box Cryptography

• Cloakware DRM Solutions
• OMA DRM 1.0 Cross-Platform Client Architecture
• OMA DRM 1.0 Client for Windows Mobile™- based Devices
• OMA DRM 1.0 Client for Android™- based Devices
• OMA DRM 2.0 Cross-Platform Client Architecture