Windows Media Player Mobile DRM on Windows Mobile 6.5

Windows Media Player Mobile on Windows Mobile 6.5 managed copy-protected audio and video through the implementation of Windows Media Digital Rights Management 10 for Portable Devices (WMDRM 10-PD). This architecture enabled secure playback of subscription-based and purchased media from compatible online services by verifying cryptographic licenses tied directly to the device's hardware identity. Synchronization occurred primarily through a host PC, which transferred encrypted content alongside explicit usage rights, ensuring that protected media adhered strictly to playback limits, expiration dates, and anti-piracy policies.

WMDRM 10-PD Architecture

The media player relied on Microsoft's WMDRM 10-PD framework, designed specifically for tethered portable media players and smartphones. Protected files—typically encoded in WMA (Windows Media Audio) or WMV (Windows Media Video)—consisted of encrypted content payloads packaged with metadata headers. Playback required a matching digital license containing the symmetric key needed to decrypt the media stream along with specific usage rules, such as expiration timestamps or play counts.

Synchronization and License Acquisition

Windows Mobile 6.5 devices primarily acquired DRM content through a tethered connection via ActiveSync or the Windows Mobile Device Center (WMDC). Desktop applications, most notably Windows Media Player on the PC, acted as licensing proxies:

  1. Secure Handshake: When connected via Media Transfer Protocol (MTP), the PC and the mobile device established a secure authenticated channel.
  2. Device Authentication: The device presented a certificate containing its public key and a unique hardware ID (derived from the device's processor and internal hardware components).
  3. License Generation: The desktop software verified the device's certificate and repackaged the DRM license, encrypting the media key with the mobile device’s public key.
  4. Transfer: The protected audio/video file and the device-bound license were transferred to the mobile device’s internal memory or storage card.

While the underlying operating system supported direct over-the-air (OTA) license acquisition through Internet Explorer Mobile via HTTP/HTTPS, the desktop synchronization model remained the standard method for subscription services under the "PlaysForSure" ecosystem (such as Napster To Go or Rhapsody).

Hardware-Bound Secure Storage

Licenses transferred to a Windows Mobile 6.5 device were stored in a protected, hidden system store. The DRM subsystem utilized device-specific cryptographic keys to encrypt the license store, ensuring that licenses could not simply be copied to another device or swapped via an SD card. If the operating system was hard-reset, the cryptographic keys were discarded, invalidating any existing licenses on external storage until the device was resynchronized with the desktop host.

Real-Time Playback and Rule Enforcement

When a user opened a protected file in Windows Media Player Mobile, the player handed execution to the OS-level DRM component:

  • License Matching: The DRM engine scanned the local license store for a key matching the Key ID (KID) embedded in the file's header.
  • Condition Verification: The engine evaluated the license's embedded rules. For subscription tracks, it validated the current date against the device's secure internal clock to ensure the subscription had not lapsed. If the clock had been tampered with or reset, the player refused playback until a sync reset the secure timer.
  • In-Memory Decryption: If conditions were met, the audio or video data was decrypted in volatile system memory on a block-by-block basis immediately prior to rendering. Decrypted data was never written to the disk or unmanaged cache, preventing unauthorized interception.

If a license was expired or missing, Windows Media Player Mobile halted playback immediately and displayed an error message directing the user to connect the phone to their computer to update their media rights.