IAC
`
`S 20050004873A1
`
`as) United States
`a2) Patent Application Publication co) Pub. No.: US 2005/0004873 Al
`(43) Pub. Date: Jan. 6, 2005
`
`Pou et al.
`
`(54) DISTRIBUTION AND RIGHTS
`MANAGEMENTOFDIGITAL CONTENT
`
`Publication Classification
`
`Techniques and systems for for managing digital rights can
`be implemented to protect against unauthorized copying of
`digital content andto help ensure payment to content owners
`and distributors. Digital wrappers can be appliedto data files
`to prevent access without a valid authorization. Information
`relating to authorizations to access data files and/or keys for
`accessing the data files may be stored andretrieved using
`data stored in a non-volatile storage area of a user device.
`(21) Appl. No:—10/726,284
`Software on the user device can be used to recognize files
`and to apply digital wrappers to recognized files. In addition,
`the software can be used to remove digital wrappers from
`files in accordance with authorizations to access the files.
`
`Tints C17 cacccccssccssssscesssassnssnseunsensesn GO6F 17/60
`(SD)
`(52) U.S. Ce cesssessssssssessesssestnetesssnssnseanieesneseee 705/51
`
`(57)
`
`ABSTRACT
`
`Payments or other credits can be allocated among distribu-
`tors of a data file using information associated with the
`digital wrappers.
`
`(76)
`
`Inventors: Robin Pou, Dallas, TX (US); Brad
`Edmonson, Franklin, TN (US); Dave
`Jaworski, Brentwood, TN (US); Jozef
`Nuyens, Brentwood, TN (US); Scott
`Lewis, El Dorado Hills, CA (US)
`
`Correspondence Address:
`FISH & RICHARDSON P.C.
`5000 BANK ONE CENTER
`1717 MAIN STREET
`DALLAS, TX 75201 (US)
`
`(22)
`
`Filed:
`
`Dec. 2, 2003
`
`Related U.S. Application Data
`
`(60) Provisional application No. 60/444,581, filed on Feb.
`3, 2003.
`
`100=
`
`705
`
`Detect New File
`
`710
`
`Identify File
`
`
`
`
`
`
`115 2
`
`
`
`
`
` Allow Accessto File
`
`125
`
`Offer License
`
`
`User
`
`
`Deny Access
`Accepts
`
`
`to File
`License
`
`
`?
`
`
`130
`
`140
`
`Store License
`Information
`
`EX1005
`Roku V. Media Chain
`U.S. Patent No. 10,489,560
`
`EX1005
`Roku V. Media Chain
`U.S. Patent No. 10,489,560
`
`

`

`Patent Application Publication
`
`Jan. 6,2005 Sheet 1 of 10
`
`US 2005/0004873 Al
`
`
`
` 120
`to File
`ons
`115
`
`
`to File
`
`105
`
`Detect NewFile
`
`110
`
`Identify File
`
`125
`
`Offer License
`
`130
`
` User
`Accepts
`ee
`
`140
`
`Store License
`Information
`
`Allow Access
`
`Deny Access
`
`FIG. 1
`
`

`

`Patent Application Publication
`
`Jan. 6,2005 Sheet 2 of 10
`
`US 2005/0004873 Al
`
`200 hy
`
`User
`Device Processor
`
`Central
`Server
`
`245
`
`
`
`
`
` Central
`
`License
`Database
`
`FIG. 2
`
`

`

`Patent Application Publication
`
`Jan. 6, 2005 Sheet 3 of 10
`
`US 2005/0004873 Al
`
`wsS&S
`
`ooa05
`
`Create Media File
`
`310
`
`Apply Digital Wrapper
`
`315
`
`Receive WrappedFile
`
`330
`
`340
`
`Deny
`Access
`
`
`Valid
`2320
`
`
`
`No
`Offer Installation
`Solution Software
`SianeG
`
`
`
`325
`Offer Purchase of
`Wrapped File
`
`coe
`
`350
`
`Yes
`
`Obtain Payment
`
`Unwrap File
`
`355
`
`360
`
`365
`
`Check Other Media
`
`FIG. 3
`
`

`

`Patent Application Publication
`
`Jan. 6,2005 Sheet 4 of 10
`
`US 2005/0004873 Al
`
`400—~.
`
`tf05
`
`Create Media File
`
`tf
`
`10
`
`& 15
`
`Receive File
`
`Identify File
`
`425
`
`0
`
`Allow Access
`
`420
`
`File
`;
`Recognized
`?
`
`0"
`
`440
`
`MDs
`
`fA45
`
`Yes
`
`Obtain Payment
`
`a30
`Update License
`Database
`
`f
`
`30
`
`Wrap File
`
`FIG. 4
`
`

`

`Patent Application Publication
`
`Jan. 6,2005 Sheet 5 of 10
`
`US 2005/0004873 Al
`
`sO 505
`
`510
`
`User
`Device
`
`515
`
`520
`
`
`
`Central
`Server
`
`Central
`Database
`
`|
`
`522
`Initiate Installation
`
`|Request
`
`524
`
`ofSolutionSoftwareLyDownload
`
`
`
`528
`
`Receive Acceptance
`of License Agreement
`
`530
`
`Collect User
`Information
`
`532
`
`
`:
`‘
`\
`Establish SSL Connection
`
`534~,__ Transmit UserInfo
`
`538
`
`Search for User
`
`
`Generate Key
` Store Key
`540
`
`542
`
`Encrypt Key
`Transmit Encrypted Key
`\ 544
`Store Encrypted Key
`Create License
`oe
`Database
`
`548
`
`FIG. 5
`
`

`

`Patent Application Publication
`
`Jan. 6,2005 Sheet 6 of 10
`
`US 2005/0004873 Al
`
`605
`
`610
`
`User
`Device
`
`620
`
`Server
`
`Central
`
`Central
`Database
`
`Run Executable|-630
`Wrapper Code
`
`Checkfor Valid
`Installation
`of Solution
`
`Software
`
`Checkfor Valid
`Key
`RequestFile License
`
`640
`
`642
`
`Send Key|“644|644
`
`650
`Unencrypt
`Key
`
`Calculate
`Checksum
`
`655
`
`860
`
`
`
`Verify Key
`and/or Checksum
`675
`6
`Authorization
`
`Searchfor —License Sass
`__|__Upeate
`680
`
`645
`
`65
`
`FIG. 6
`
`685
`Allow Use of
`Media
`
`

`

`Patent Application Publication
`
`Jan. 6,2005 Sheet 7 of 10
`
`US 2005/0004873 Al
`
`715
`
`705
`
`720
`
`725
`
`
`
`User
`Device
`
`Central
`Server
`
`Central
`Database
`
`730
`Determinethat
`No Licence Exists
`
`Notify
`
`735
`
`740
`
`Payment
`
`Request 755
`
`Process Payment
`
`Update
`760
`
`745
`
`Update
`
`765
`
`Allow Use of
`Media File
`
`770:
`
`FIG. 7
`
`

`

`Patent Application Publication
`
`Jan. 6,2005 Sheet 8 of 10
`
`US 2005/0004873 Al
`
`815
`
`805
`
`Device
`
`Local
`Database
`
`User
`
`830
`
`RequestTransfer
`
`Request Device ID
`835
`Send Device ID
`
`Central
`Server
`
`
`
`
`Transfer File &
`8507—License Info
`
`845
`
`Confirm Rules
`Allow Transfer .
`
`
`
`860
`
`855
`
`Update Local
`License Info
`
`Update License
`Info
`
`825
`
`
`
`
`
`
`
`
`
`
`
`vaidato||5
`
`
`
`Establish Connection
`
`
`
`865
`
`Upload License Updates
`
`FIG. 8
`
`
`
`

`

`Patent Application Publication
`
`Jan. 6,2005 Sheet 9 of 10
`
`US 2005/0004873 Al
`
`x900
`
`905
`
`User 2 Receives
`Media File from User 1
`
`910
`
`User 2 Purchases
`Media File License
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`915
`
`Examine Payment/
`Business Rules
`
`920
`
`Credit User 71 with
`Commission
`
`925
`
`User 3 Receives Media
`File from User 2
`
`User 3 Purchases
`
`
`
`930
`
`935
`
`
`
`Examine Payment/
`Business Rules
`
`940
`
`Credit User 1 &
`User 2
`
`FIG. 9
`
`

`

`Patent Application Publication
`
`Jan. 6,2005 Sheet 10 of 10
`
`US 2005/0004873 Al
`
`Identify Business
`Rules
`
`Select Media File
`to be Wrapped
`
`
`
`Generate UFID
`
`Apply Wrapper
`
`FIG. 10
`
`

`

`US 2005/0004873 Al
`
`Jan. 6, 2005
`
`DISTRIBUTION AND RIGHTS MANAGEMENT OF
`DIGITAL CONTENT
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] This application is related to co-pending provi-
`sional application Ser. No. 60/444,581, filed Feb. 3, 2003,
`which is incorporated herein by reference.
`
`TECHNICAL FIELD
`
`[0002] This description relates to digital rights manage-
`ment, and more particularly to facilitating authorized licens-
`ing and distribution of digital media.
`
`BACKGROUND
`
`[0003] The music industry is in the midst of significant
`turmoil. For decades, music companies have been in control
`of the physical distribution of the content it creates. For the
`first time in history, consumers have been given tools that
`have enabled them to seize control of this distribution of
`content. Rapidly developing and widely adopted technology
`has resulted in a consumer driven disruptive change to the
`status quo. The myriad of legal and illegal solutions has
`proven to be poor attempts to answer and solvethe innate
`challenges of content distribution in
`a digital world.
`Although problems with digital distribution of content may
`be associated to a significant extent with the music industry,
`other industries, such as the motion picture industry, suffer
`from the same challenges.
`
`Nosolution to date has satisfied both the content
`[0004]
`creator/owner and the consumer. The only digital distribu-
`tion solution that has been widely adopted is found in the
`various peer-to-peer networks. However,
`this
`solution
`allows millions of consumers to download music and other
`
`forms of copyrighted content without paying for the content
`they download, Content owners are left with no ability to
`collect fees owed to them. This situation has caused devas-
`tating revenue losses.
`
`(0003] Through their endorsement of digital subscription
`services among other things, many content creating entities
`such as the music companies have acknowledged that digital
`distribution is the future.
`It
`is the most efficient and eco-
`nomical means of distribution. To date, the music industry
`has still not fully embracedthe potential of this distribution
`vehicle. Digital distribution is also becoming prevalent in
`other industries and with respect to many types of content.
`
`[0006] Problems similar to those faced by the music
`industry have arisen, or are likely to arise, in the context of
`other types of content.
`
`[0007] Current digital distribution models in the music
`industry, for example, confine the consumer intoartificial
`purchasing patterns, have only limited song selections, and
`are limited in terms of other available options. Moreover,
`these models generally limit how the consumer uses the
`content they pay for, and some of the models mayfail to
`protect against
`infringement of rights in the underlying
`works.
`
`SUMMARY
`
`niques for protecting digital media and other content are
`inadequate and that processes can be implemented for
`licensing digital rights without materially impairing the
`ability of users to rightfully access digital media and other
`content. In addition, such processes can provide a mecha-
`nism to reward users for promoting and distributing such
`content.
`
`In one general aspect, management of digital rights
`[6009]
`involves detecting a data file on a user device. The data file
`includes a digital wrapper preventing accessto the data file
`without a valid authorization. A search is conducted for
`information relating to an authorization to access the data
`file using data stored in a non-volatile storage area of the
`user device. The digital wrapper is disabled if an authori-
`zation to access the data file is found during the search.
`
`Implementations include one or more of the fol-
`[6010]
`lowing features. The data file can be a media file. The search
`for informationrelating to an authorization to access the data
`file can be conducted in a license database on the user
`device. The license database can be located in the non-
`volatile storage area of the user device. The non-volatile
`storage area of the user device can be a basic input/output
`system (BIOS). The data stored in the non-volatile storage
`area of the user device can include a location of the license
`database and/or an access key for the license database, with
`the access key being necessary to access the license data-
`base. The license database can include an access key for the
`data file, with the access key being necessary to disable the
`wrapper. The search for information relating to an authori-
`zation to access the data file can be conducted in a license
`
`database associated with a remote server in response to a
`determination that a local database on the user device does
`not include information relating to an authorization to access
`the data file.
`
`Identification data for the user device can be sent to
`(0011]
`the central server, and the identification data can be adapted
`to allow the central server to validate the user device. The
`identification data can include a digital key associated with
`the user device and/or a user associated with the user device.
`An authorization to access the data file can be offered for
`purchase, and an acceptanceof the offer to purchase can be
`received. The digital wrapper can be disabled in response to
`the acceptance of the offer. The acceptance of the offer can
`be sent to a central server. A message from the central server
`can be received in response to the acceptance of the offer,
`and data contained in the message can be used to disable the
`digital wrapper. Identification data for the user device can be
`sent
`to the central server to allow the central server to
`validate the user device. The identification data can include
`
`a digital key associated with the user device and/or a user
`associated with the user device. Information relating to an
`authorization to access the data file can be stored on the user
`device. Access to the data file can be denied if an authori-
`zation to access the data file is not found during the search
`and if an offer to purchase an authorization to access the data
`file is not accepted. The search for information relating to an
`authorization to access the data file can include using
`executable instructions stored in the digital wrapper to
`determine whether the user device includes software for
`disabling the digital wrapper.
`
`[0008] Systems and techniques are provided for managing
`digital rights. The inventors recognized that existing tech-
`
`In another general aspect, a data file that does not
`[0012]
`include a digital wrapper is detected on a user device. The
`
`

`

`US 2005/0004873 Al
`
`Jan. 6, 2005
`
`data file is identified using a file recognition algorithm. A
`search is conducted for information relating to an authori-
`zation to access the data file using data stored in a non-
`volatile storage area of the user device. Access to the data
`file is allowed if an authorization to access the data file is
`found during the search.
`[0013]
`Implementations include one or more of the fol-
`lowing features. The file recognition algorithm can include
`a digital fingerprinting detection technique. The data file can
`be a media file. The search for information relating to an
`authorization to access the data file can be conducted in a
`license database on the user device. The data stored in the
`non-volatile storage area of the user device can identify a
`location of the license database in a volatile storage area of
`the user device. The search for information relating to an
`authorization to access the data file can be conducted in a
`license database associated with a remote server. An autho-
`
`rization to access the data file can be offered for purchase. If
`an acceptance of the offer to purchase is received, access to
`the data file can be allowed. Information relating to an
`authorization to access the data file can be stored in a
`database on the user device in response to the acceptance of
`the offer to purchase. A digital wrapper associated with the
`identified file can be applied to the data file.
`
`In another general aspect, proceeds are allocated in
`[0014]
`connection with thedistribution of digital rights by receiving
`a data file on a user device and receiving a request
`to
`purchase a right to access the data file. The data file includes
`a digital wrapper including information relating to one or
`more distributors of the data file. The information relating to
`one or more distributors is extracted from the digital wrap-
`per, and credits are allocated to the one or more distributors
`based on the extracted information.
`
`Implementations include one or more of the fol-
`[0015]
`lowing features. The digital wrapper can further include
`information relating to an assigned allocation of royalties
`associated with purchases of rights to access the data file.
`The extracted information can be a unique file identifier, and
`the distributor information and/or
`the royalty allocation
`information can be retrieved using the uniquefile identifier.
`The retrieved information can be retrieved from a central
`database located remotely from the user device. The request
`to purchase can besent to a central server, and the allocation
`of credits can be stored in a database associated with the
`central server.
`
`To participate in the allocation of proceeds in
`[0016]
`connection with a distribution of digital rights, a user of a
`device on which a data file is receivedis identified. The data
`
`file includes a digital wrapper including information relating
`to one or more distributors of the data file. The digital
`wrapper is modified to include information relating to the
`identification of the user. A detection of the data file with the
`
`modified digital wrapper then enables an allocation of credit
`to the user. The digital wrapper can be adapted to prevent
`access to the data file without a valid authorization. The data
`file with the modified digital wrapper can be sent to a device
`associated with a consumer, and a request to purchase access
`to the data file can be received from the consumer device.
`The digital wrapper on the consumerdevice can be disabled
`in response to the received request. Credit for the consumer
`purchase can be allocated among the one or more distribu-
`tors. The information relating to the identification of the user
`can be a unique user identifier assigned by a central server.
`
`In another general aspect, digital rights manage-
`(0017]
`ment is facilitated on a user device by collecting information
`relating to a user device, including unique identification data
`for the user device, from the user device, and generating a
`digital key using the collected information. The digital key
`is stored and encrypted, and the encrypted key is sent to the
`user devicefor storage on the user device, The encrypted key
`and information relating to the user deviceis subsequently
`received, and the user device is validated using the received
`encrypted key, the received information, and/or the stored
`digital key.
`[0018]
`Implementations include one or more of the fol-
`lowing features. Identification information relating to a user
`of the user device is collected, and the digital key is
`generated using the identification informationrelating to the
`user. The collected information is collected in accordance
`with executable code stored on the user device. The digital
`key is generated by and stored on a central server. The
`validation of
`the user device involves decrypting the
`encrypted key and comparing the encrypted key tothe stored
`digital key. The validation of the user device can also
`involve generating a digital key using the received informa-
`tion relating to the user device and comparingthe digital key
`to the storeddigital key. Access to a license database and/or
`access to a digital file can be authorized in response to
`validating the user device. The unique identification data is
`extracted from a non-volatile storage area ofthe user device.
`[0019]
`In yet another general aspect, an input/output sys-
`tem of a user device is monitored for attempted file transfers.
`An attempt to transfer a data file through the input/output
`system is detected, and a digital wrapper is applied to the
`data file before allowing the attempted transfer. The digital
`wrapper is adapted to prevent unauthorized access to the
`data file.
`
`Implementations include one or more of the fol-
`(0020]
`lowing features. The data file can be identified, and the
`digital wrapper can be applied basedon the identity of the
`data file. The digital wrapper can be applied based on the
`identity of the data file matching an identification of the data
`file in a database on the user device. Identifying the data file
`can be performed using a file recognition algorithm. The
`digital wrapper includes information identifying the datafile
`and information relating to an allocation ofcredits associ-
`ated with purchases of the data file.
`(0021]
`In another general aspect, a digital file is identified
`on a first user device, and the digital file is subject to a
`license in accordance with license information stored on the
`first user device. A request to copy the digital file from the
`first user device to a second user device is received, and
`information associated with the second user device, includ-
`ing unique identification data for the second user device, is
`obtained. The digital file is copied from the first user device
`to the second user device, and data identifying the copied
`digital file and the second user device is stored on the first
`user device.
`
`Implementations include one or more of the fol-
`[0022]
`lowing features. The stored data on the first user device can
`be synchronized with a central database. A determination
`can be made that the requested copying of the digital file is
`authorized based on the license information. The license
`
`information is containedin a digital wrapper for the digital
`file. The license information for the digital file can be stored
`on the second user device.
`
`

`

`US 2005/0004873 Al
`
`Jan. 6, 2005
`
`In yet another general aspect, a media file is
`[0023]
`identified for distribution. Access rules, including informa-
`tion relating to usage rights and usage fees, associated with
`the media file are identified. A digital wrapper is applied to
`the media file. The digital wrapper includes identification
`data for the media file and data relating to the access rules
`and is adapted to prevent unauthorized access to the media
`file.
`
`[0029] The described techniques can be implemented as a
`method, in a system, or in an article including a machine-
`readable medium storing instructions for causing one or
`more processors to perform operations.
`
`[0030] The details of one or more implementationsareset
`forth in the accompanying drawings and the description
`below. Other features will be apparent from the description
`and drawings, and from the claims.
`
`Implementations include one or more of the fol-
`[0024]
`lowing features. The digital wrapper can be adapted to be
`disabled for use of the media file by a user that has a license
`[0031] FIG.1isa flow diagram of a process for managing
`to access the mediafile. The digital wrapper further includes
`digital rights to a file that is loaded onto a user device, such
`information relating to one or more distributors of the media
`file.
`as a computer.
`
`DESCRIPTION OF DRAWINGS
`
`In another general aspect, a mediafile is encoded
`[0025]
`with licensing information, and the media file is locked
`using a digital wrapper to prevent unauthorized access. The
`[0033] FIG.3is a flow diagram ofa processforinstalling,
`wrapped media file is loaded ontoa user device. Instructions
`on a user device, software (“Solution Software”) that con-
`are installed on the user device to allow unlocking of media
`trols access to protected files.
`files. The instructions provide for identifying the media file
`and sending a message,
`in accordance with the licensing
`information encoded in the mediafile, to a remote server to
`obtain a license to use the media file. A license to access the
`media file is obtained from the remote server, and access to
`the media file on the user device is allowed using the license.
`
`[0032] FIG. 2 is a block diagram of a representative
`system for managing digital rights.
`
`[0034] FIG. 4 is a flow diagram of a process for wrapping
`content that arrives without any digital wrapper on a user
`device that includes the Solution Software.
`
`Implementations include one or more of the fol-
`[0026]
`lowing features. The license to access the media file is stored
`on the user device. The license includes data for unlocking
`the media file.
`
`FIG.5 is a signaling and flow diagram of a process
`[0035]
`for generating a unique customer identifier for a user and/or
`a key that is specific to the user device.
`
`FIG. 6 isa signaling and flow diagram of a process
`(0036]
`for accessing a mediafile in a case where a user already has
`a license for the media file.
`
`In another general aspect, a centralized database is
`(0027]
`[0037] FIG.7is a signaling and flow diagram of a process
`adaptedto store identifiers for digital files and to store user
`for accessing a media file in a case where a user does not
`licenses to use the digital
`files. A centralized server is
`have a license for the media file.
`operable to receive messages via a network from a remote
`device. Each received message includes a user identifier for
`(0038] FIG.8is a signaling and flow diagram of a process
`a user and identification information for a digital file. The
`for copying or moving a media file from a user device to a
`centralized server is further operable to process payment
`secondary device.
`information for a license to use the digital file,
`to store
`information associating the license to usethe digital file with
`the user, and to send licensing informationforthe digital file
`to the remote device. The licensing information is adapted to
`enable the remote device to allow use ofthe digital file by
`the user.
`
`[0040] FIG. 10 is a flow diagram of a process for wrap-
`ping a media file.
`
`[0039] FIG. 9 shows a flow diagram of an illustrative
`process for performing a pass-along distribution.
`
`Implementations include one or more of the fol-
`[0028]
`lowing features. The centralized server can be further oper-
`able to receive one or more digital keys from the remote
`device and to decrypt the one or moredigital keys to validate
`an identity of at least one of the remote device and the user.
`The centralized server can be further operable to receive
`device-specific data from the remote device for use in
`validating the remote device. The remote device can be a
`server adapted to support streaming of digital files to a user
`device associated with the user. The remote device can store
`
`the licensing information. The remote device can be a user
`device associated with the user. The centralized server can
`
`be further adapted to receive information from the user
`device, generate a digital key associated with the user and/or
`the user device, and send the digital key to the user device.
`The digital key can be adapted to enable access to the license
`information, a license database containing the license infor-
`mation, and/or the digital file. The licensing information can
`be data adapted for use in disabling a digital wrapper applied
`to the digital file.
`
`[0041] Like reference symbols in the various drawings
`indicate like elements.
`
`DETAILED DESCRIPTION
`
`[0042] The systems and techniques described here relate
`to a computer-implemented system for distribution and
`rights management ofdigital media files. The systems and
`techniques represent an end-to-end process that supports
`virtually any type of proprietary digital files including music
`and other recordings, movies and other video, books and
`other written works, and other files, such as those that
`pertain to the financial, legal, medical, gaming, and software
`industries. Although the following description focuses pri-
`marily on the use ofthe techniques in connection with music
`files, the techniquesare equally applicable to other types of
`digital files. Similarly, although the techniques are described
`in the context of mediafiles, the techniques may also be used
`in connection with multimedia files and other types of data
`files. The systems and techniques ensure that content owners
`are compensated for the distribution and use of their works
`
`

`

`US 2005/0004873 Al
`
`Jan. 6, 2005
`
`and offer multiple levels of participation in the revenues
`generated by the sale and/or licensing ofdigital media.
`
`(0043] The techniques work with media that arrives at a
`user’s computer in a “wrapped” form (protected), as well
`with media that arrives “unwrapped” (i.¢., unprotected).
`Media rights owners have the ability to wrap a file with
`information about ownership and payment. This information
`is given a unique file ID and is stored in a central database.
`Thefile ID is stored and transmitted with the wrapper. Songs
`or other formsofdigital media without the wrapper mayalso
`be identified. Once a file is captured andidentified by the
`system, the information such as owner and payment require-
`ments can be retrieved(e.g., by matching the identified file
`with its unique file ID stored at
`the central database).
`Monitoring software provided in accordance with the
`described solution (“the Solution Software”) may be auto-
`matically or manually installed on any computer or other
`device on which a user attempts to access a wrappedfile.
`Once installed, all future media that passes through thefile
`input/output (I/O) system of the computer can be identified
`either by using the file ID, if available, or using file identi-
`fication software.
`
`distribution in which participation in revenues is permitted
`will be limited. The number of levels of payment for a
`particular media file may be optionally established by the
`content owner and/or by a subsequent distributor of the
`media file. The maximum numberof levels of payment and
`the rates for such payments may be established in the
`creation of the unique file ID for the media file along with
`the rates for payment. If the new user does not license the
`media file, he/she does not gain access to the file, although
`he/she may be able to pass along the file to other users for
`purchase.
`
`(0047] A file may contain rules for purchase or transfer
`that require related files to be purchased or transferred with
`the file. For example, a song may require that it only be sold
`as part of a collection of songs such as an album. Another
`example would require that trailers, ads, or other related
`material accompany a movie or distributed T'V show.
`
`[0048] To support the ability to properly allocate revenues
`in accordance with a tiered-level distribution technique, the
`Solution Software on a user’s computer may provide a
`mechanism whereby resellers and distributors can add their
`identification to a wrapped media file, which generally
`allowsidentification of resellers anddistributors so that they
`[0044] Auser ID may becreated for each user. The user ID
`can be compensated for sales where they were involved in
`may be stored along with device specific information in a
`the distribution channel. Each timeasales transaction occurs
`secure area on the computer, such as the BIOS of the
`for a particular media file, identification information for
`computer. The user ID may be stored in an encrypted or
`users in the distribution channel may be extracted from the
`unencrypted format. This information may represent a user
`wrapped media file to determine whois entitled to share in
`identification key, which may allow access to a local data-
`the revenue. All transactions may be centrally tracked for
`base oflicenses and related permissions held by the user. By
`payment and analysis. A central tracking database can be
`referring to this local license database, the Solution Software
`used to track payments forresellers, distributors (which may
`stored on the computer can determine whether the user is
`include users who pass along a wrappedfile), and users who
`authorized to use a particular file and, if so, unwrap the file.
`pass along a file that arrives without a wrapper. This latter
`Even ifthe file is not wrapped, access or use of the file may
`situation can occur, for example, when a user shares a song
`be allowed or prevented in accordance with business rules
`stored at the local database or at a central database level. For
`that originated from a standard audio CD or DVD. The
`referring user’s ID can be entered at the time of purchase so
`example, business rules may prevent certain types of files
`that the referrer and related resellers and distributors can be
`from being used unless a license is found in the local
`database while allowing the use of other types of files
`without the need for a license. Because users often have
`multiple devices, information about the user license may be
`centrally stored to ensure the user has access toall licensed
`media on more than one ofthe devices he/she owns.
`
`compensated.
`
`[0049] Licenses for files may be recognized across mul-
`tiple devices of a user. The methods and techniques
`described herein provide processes for managing, sharing,
`and moving licenses across multiple devices of a user.
`
`[0045] A user may be defined as an individual or a set of
`related individuals, such as a family, members of a house-
`hold, persons who access a shared private device, or a
`business entity. In addition, where information is described
`as being stored in a database, the information may be stored
`in multiple databases.
`
`[0046] Files may be forwarded to other users and other-
`wise exchanged among users. However, if a file requires a
`license and the new users do not purchase the mediafile, the
`new users do not gain access to the file. To encourage
`distribution ofthe file, users are given an incentive to “pass
`along” (electronically send) media files or links to media
`files to others they feel would be interested in the mediafiles
`(i.c., to potentially receive a portion of revenues generated
`by new purchasers). Recipients are given an incentive to
`purchase the media file (i.¢., to be able to access thefile) and
`also to further pass along the media file so that they too can
`participate in revenues. The numberoflevels of distribution
`in which participation in revenues is permitted can be
`unlimited. Typically, however,
`the number of levels of
`
`[0050] FIG. 1 is a flow diagram of a process 100 for
`managing digital rights to a file that is loaded onto a user
`device, such as a computer. The user device includes soft-
`ware interfaces with the I/O ports for the device to monitor
`all file I/O, much like a firewall, which scansall inbound and
`outbound traffic for the computer and checksall files being
`moved into and out of the system. Files may be loaded onto
`the device using any type of I/O port, including a floppy
`drive, an Ethernet or LAN connection, a dial-up connection,
`a CD-ROM or DVDdrive, a USBport, an infrared data port,
`a Bluetooth or other wireless connection, or any other
`mechanism and/or protocol for transferring data to and from
`the user device.
`
`(0051] When thefile is loaded onto the user device, thefile
`is detected (step 105). The detected file is further examined
`using file identification software in an attempt to identify the
`file (step 110). For example, the fi