AMN - Access Media Network

Mediabroker™ Distribution Services

 

Program Flow and Technology Architecture Document

By Dale B. Schalow, Founder AMN

 

 

November 17, 2005

Presented to Paramount VOD and Distribution (Bluhdorn Bldg. - Paramount Studios Lot)

 


NOTICE: AMN has proceeded with intellectual property protection as filed with the USPTO in the territory of the United States.

 

 


 


Access Media Network
Mediabroker™ Secure Consumer Distribution Services
Technology Architecture and Program Flow

 

 

 

 

Overview

 

This document defines layered components and their respective elements of AMN’s Mediabroker™ media flow services and commerce (MFSC) framework.  There are three (3) primary layers contained in this document:

 

 

Each layer represents a structure necessary to ensure accurate end-to-end processing of media (e.g. TV, commercials, educational courses, public service announcements, advertising, video, movies), and music (e.g. music-on-demand, etc) products provided as HD (high-definition 1080p) source by a media content owner or studio that are sold in multiple HD and compression formats directly to consumers by AMN’s Mediabroker™ technology.  Compensation from the consumer is provided to 1) AMN as the media distributor and 2) Production Studio as the media products owner. Methods of electronic funds transfers (EFT) are handled through secure payment processing using e-commerce over the Internet.

 

Description

 

Three technical drawings have been created to show the flow of the programs used within the Mediabroker™ system.  The drawings use icons, directional object connectors and lines, and enumeration to describe the sequence of events for each layer.  With minor exceptions in Layer 2 & 3, the general direction of the layers’ programs use a top-to-bottom flow model.  In other words, a flow begins at the top of the drawing and runs through all of the layer’s elements to the bottom.  Layers 2 & 3 incorporate a minor flow shift back-upwards after reaching the bottom elements.

 

 The following diagram illustrates Layer 1 – Automated Transcoding Services.

 

 

Each Component in Layer 1 – Automated Media Transcoding, is described as follows:

 

1)      HD Source Tape provided by Owner

·        Masters will be shipped and/or couriered by Content Owner or Provider

·        10 -  20 masters per month for Layer 1 processing

·        Film/reels will not be accepted

2)      HD Pro-conversion service

·        1080p HD source tape recommended

·        Betacam or other non-HD will be evaluated for HD-upconversion (e.g. 1080p, 720p)

·        A manual process converting the physical source tape signal to software format.

o       Windows Media Video HD (v9 or higher)

§         Resolution 1080p (WMV)

§         Resolution 720p (WMV)

o       Apple Quicktime (v7 or higher)

§         Resolution 1080p (H.264)

§         Resolution 720p (H.264)

·        Pro-conversion formats will be handled by an experienced service provider either in Los Angeles, CA or Washington, D.C.

·        Two Professional copies (1080p and 720p) of the HD Source Tape will be stored and maintained using the service provider’s media vault facility

·        The original Source Tape (HD or other provided by Studio) will be shipped back to Studio as required

3)      Transcoding servers hosted by AMN

·        Servers running automated transcoding software services:

o       Mediabroker™ COM and Java-based classes

o       Apple Quicktime Version 7+ API

o       Windows Media Video Encoding Version 9 or higher API

·        Hardware servers will be equal to:

o       Intel Pentium/Xeon 1.5GHz+

o       Parallel processing as available

§         Dual-CPU (e.g. 3.6GHz X 2)

§         Dual-core (OEM available)

·        Windows and Unix-based hosting for web services including:

o       Java servlet

o       IT security

4)      Transcoding services

·        Software batch jobs run through the automation

·        Process works as follows:

o       Media location defined for the HD source file

o       Media location path names defined for the destination files (transcoded output)

o       Depending on CPU availability a multi-threading function helps support concurrent compression processing (i.e. transcoding more that one format at a time)

 

5)      Compressed formats hosting

·        Compressed files are the results of Step #4

·        Compressed media files are stored in the following formats:

1.      3GPP – Used with mobile phones on a 3G network

2.      MP4 – MPEG-4 Video used with CDMA/GSM mobile phones

3.      WMV – Windows Media Video used with Windows Media Player and Windows Mobile Devices

4.      M4V – Used with iPod devices supporting video

5.      AVI – Windows Video used with Microsoft and other media players

6.      MPG – MPEG-1 Video used with several media players including Windows, Java, Apple and Linux platforms

7.      MOV – Used with Apple Quicktime supported players including HD (Version 7+)

8.      FLV – Flash Video used with generated flash movies for Windows, Apple, Linux embedded platforms

9.      Other – Additional formats as needed to continue expansion of Mediabroker™ device support

a.       Reference: JMF Supported Formats

b.   Reference: Apple Quicktime 7 Supported Formats (QT7 Pro)

 

6)      Content ready for DRM Processing

·        Uses secure electronic method such as SecureFX, token-based access such as RSA/SecurID or DRM hosting system like KeyOS

 

 

The following diagram illustrates Layer 2 – DRM Processing.

 

Each Component in Layer 2 – DRM Processing, is described as follows.

 

1)      DRM Import provided by AMN (OPTIONAL)

·        Digital rights encryption package used by DRM support team

o       Windows Media DRM (v10)

§         USA Distribution

§         Global DRM Support

§         Ref: Windows DRM Site

o       OMA for global support

§         International Distribution Support

§         Embedded OEM specs delivered

§         Ref: OMA DRM Site

o       Apple DRM – FairPlay when available

§         iPod

§         Site Reference Not Available

·        Files from Layer 1 are imported into the DRM application

·        Media Files are encrypted using DRM packages for their respective formats:

o       Windows devices supporting Windows media formats are encrypted with Windows DRM with transcribing services when necessary (Ref: Windows DRM Transcribing)

o       OMA devices supporting global DRM media capabilities are encrypted with OMA packages including Microsoft DRM

2)      Business parameters are applied

·        A fee defined for the specific distribution purpose

·        The distribution purpose is one or more of the following:

o       Pay-per-view, subscription plan, customized

o       Parameters including but not limited to:

§         Expiration date

§         Unlimited play

§         Transfer to SDMI/non-SDMI

§         Counted operations (plays, transfers)

 

3)      License Keys are generated (OPTIONAL)

·        The number of keys generated depends on the number of files imported

·        A minimum of ten (10) formats generated from baseline deployment

·        Registration of licenses with AMN’s DRM clearing house

o       Qualifed expertise for license clearing will be based on business costs and capability – examples:

§         BuyDRM

§         Loudeye

§         PayVision

4)      Encrypted Media Files Host

·        An experienced hosting company selected to provide content for purchase

·        DoD certification is preferred but not required – examples:

o       Qwest

o       MCI/Verizon

 

 

 

The following diagram illustrates Layer 3 – POS Content Delivery Process.

 

 

 

 

Each Component in Layer 3 – POS Content Delivery Process, is described as follows.

 

1)  Consumer

·        Customer possessing a media video-capable device

·        Individual possessing a valid credit or debit card for use with secure Internet purchasing

   2) Place of Purchase

·        The location of the customer using the device

·        Location settings including home, office, retailer, automobile, airliner, hotel, taxi, cruise ship and mobile-based locations

·        Wireless access points (AP) to centralized media networks may include:

o       Download stations (kiosk)

o       Media center at home

o       AutoPC with satellite uplink/downlink

3) Mobile Device

·        A media capable device to playback purchased content

·        See ‘Appendix’ at the end of this document for GUI shots

·        Types of devices include:

o       Laptop or tablet

o       Mobile phone

o       iPod

o       PocketPC

·        The capability support is performed using a user-agent gestalt function (i.e. from the devices management matrix) to determine appropriate codec and DRM compatibility – examples:

o        SonyEricssonK700i/R2N SEMC-Browser/4.0.1 Profile/MIDP-2.0 Configuration/CLDC-1.1

o       NokiaN-Gage/1.0 SymbianOS/6.1 Series60/1.2 Profile/MIDP-1.0 Configuration/CLDC-1.0

o       Example Profiler:  AMN’s WML device capability profiler



·        A dynamically designed configuration (XML) schema is devised to perform back-end detection of the device through the wireless connection

·        The device database may contain over 200 configuration overlaps to determine which format media is either 1) viewable, or 2) downloadable 

·        The customer may have the option to purchase and access a secure media package that contains more than one format

·        Encryption for additionally purchased content (multiple formats) is supported using more secure AES (Advanced Encryption Standard) with 256 bit key protection (Ref: NIST AES Validation site)

  4) Secure Payment

·        Payment is made by the customer before downloading media product

·        Secure transfer protocol is used as SSL over HTTPS

·        Payment methods include:

o       Valid Credit Card (MC, VISA, AMEX, DISCOVER)

o       Valid Debit/Check Card (ROUTING/ACCT #, CC/DC)

·        The card number, expiration date, secure ID, and name on the front of the credit card is entered by the customer into the device using keypad or alphkeypad

·        Additional information may be requested if not available via the automation for retrieving embedded device info (e.g. phone number, name, geographical data)

·        A transaction verification screen gives the user a summary for the purchase

·        The user may accept or cancel the transaction

·        If the user accepts the transaction the credit card information including the CC#, expiration date, secure ID, and name on the credit card is transferred securely to the e-commerce/DRM agency for licensing and clearance

5) DRM License Validation and Authentication

·        A transaction to purchase a license for the media is received by the DRM web service

·        The request contains all of the information for the purchase including:

o       Product key ID tag

o       Product Description

o       Timestamp

o       Device tag

o       Device telephone

o       Media format

o       Credit card data array (#, secure ID, name, expiration date)

·        The DRM agency processes the payment transaction prior to allowing download of the media

·        A generated license is used to pair the physical media copy with this customer transaction

·        The license contains all business parameters for usability including:

o       Play count

o       Playing time

o       Playing time after first use

o       Burn to CD

o       Times to burn to CD

o       Exporting to other PC

o       Exporting to DRM enabled device (pocket PC, smart phone)

o       Times to export

o       Play start date

·        An e-commerce payment clearing house may be used by the DRM agent to expedite the electronic funds transfer

·        Once the transaction is approved the encrypted media product purchase is approved and is downloaded to the device

6) Secure Media Download

·        The media product copy is downloaded to the customer with the paired license key verified with the customer (i.e. “This product is licensed”)

·        The package has already been encrypted as set forth with the DRM processing in Layer 2

·        A secure Internet transfer method (https) is used to send the product

·        The user receives the media file archive and is extracted based on the granted license approval

·        The extraction process for a single title purchase is automated based on one or more DRM branded assurance policies:

o       Playsforsure.com

 

·        Automated updates of the DRM for any of the devices in Step 4 may be necessary during the first Mediabroker™ customer transaction – example:

 

     

      Laptop message on embedded XP

        accessing a protected WMV file

 

·        If the user has purchased several formats (e.g. WMV, MOV) then the customer is notified via email of the purchase with a link to securely download the DRM monitored access of the purchased product package

·        Users of devices that do not yet have long-range wireless capability may include the following:

o       Apple iPod

o       Smart phones with no cell service but connect via data linke/USB to a PC

7) Funds Distribution to Owner and Distributor

·        Revenue generated from the customer transaction is split into two parts:

o       Part 1 – Revenue split with Content Owner

o       Part 2 – Revenue split with AMN Distributor

·        An automated direct deposit is made to each bank account by the DRM collection agent

·        The income split from the transaction is determined by the business terms agreement between the Content Owner and Distributor

 

 


 

 

 

Appendix - Mediabroker™ GUI Shots for Devices

 

Reference: A complete list of embedded flash devices

Appendix - Mediabroker™ GUI Shots for Devices (continued)

 

 

 

 

 

 

Illustration 3.0 – POS with WML-enabled device using Mediabroker™

 

 

 

 

 

 

 

 

 

 

 


Appendix - Mediabroker™ GUI Shots for Devices (continued)