WO2006054988A2 - Procede, systeme et dispositif destines a la consommation de contenu centre autour d'une licence - Google Patents

Procede, systeme et dispositif destines a la consommation de contenu centre autour d'une licence Download PDF

Info

Publication number
WO2006054988A2
WO2006054988A2 PCT/US2004/038474 US2004038474W WO2006054988A2 WO 2006054988 A2 WO2006054988 A2 WO 2006054988A2 US 2004038474 W US2004038474 W US 2004038474W WO 2006054988 A2 WO2006054988 A2 WO 2006054988A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
license
repository
content
shared
Prior art date
Application number
PCT/US2004/038474
Other languages
English (en)
Other versions
WO2006054988A3 (fr
Inventor
Michael Raley
Eddie Chen
Original Assignee
Contentguard Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Contentguard Holdings, Inc. filed Critical Contentguard Holdings, Inc.
Priority to JP2007542998A priority Critical patent/JP4898699B2/ja
Priority to KR1020127027792A priority patent/KR101350104B1/ko
Priority to KR1020077013787A priority patent/KR101213913B1/ko
Priority to EP20040811253 priority patent/EP1829270A4/fr
Priority to PCT/US2004/038474 priority patent/WO2006054988A2/fr
Priority to CN2004800447185A priority patent/CN101421969B/zh
Publication of WO2006054988A2 publication Critical patent/WO2006054988A2/fr
Publication of WO2006054988A3 publication Critical patent/WO2006054988A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0861—Network architectures or network communication protocols for network security for authentication of entities using biometrical features, e.g. fingerprint, retina-scan

Definitions

  • the present invention generally relates to the field of digital rights management, and more particularly to a method, system, and device for storage of, access to, and management of licenses for digital content.
  • application-centric For example, when consumers wanted to consume digital content, they first opened the appropriate application, such as a word processor. Consumers then accessed the content from within the application.
  • the current state of the art promotes a "content-centric" view. For example, when consumers want to consume digital content, they double-click the file, including the content, in their file system explorer, and the associated content consumption application launches.
  • the right to consume content is often tied to a particular embodiment of such content. For example, the right to view a movie is tied to physical possession of a DVD.
  • DRM digital rights management
  • use of that content is predicated upon use of the particular DRM system originally used to protect the content. For example, if the consumer purchased a license for content from company A, the consumer must have company A's DRM system installed on the consumption device to consume such content.
  • the license may be embedded in the content, or it may be a separate license, which may be machine readable or human readable, such as a click-through license or legal contract.
  • the DRM system interprets the license to identify what the consumer is permitted to do with the content, and restricts the consumer from doing things that are not permitted.
  • the mechanisms that the various DRM systems use to accomplish this task vary widely. For example, many DRM systems express, store, and maintain licenses in a proprietary manner. A consumer typically acquires a DRM system, and requests content provisioned for that system.
  • a content instance then is prepared with encryption or formatting, coupled with other trust and security technologies, that allow the content instance to be used only with a particular DRM implementation.
  • the license typically is stored in a proprietary repository of the DRM system or as part of the content.
  • Tying consumption of content to a particular combination of consumption application, consumption device, and/or DRM system places limitations on the consumer's purchasing, and consumption habits.
  • consumers want to purchase content from a variety of sources (e.g., brick and mortar stores, satellite/cable, internet download, and the like) in a variety formats (e.g., DVD, Redbook audio, computer DVD, streaming, and the like), for a variety of devices (e.g., PCs, home media center, set top boxes, car stereos, mobile phones, portable media players, devices networked to remote locations, and the like).
  • sources e.g., brick and mortar stores, satellite/cable, internet download, and the like
  • formats e.g., DVD, Redbook audio, computer DVD, streaming, and the like
  • devices e.g., PCs, home media center, set top boxes, car stereos, mobile phones, portable media players, devices networked to remote locations, and the like.
  • DRM systems that protect the content may not exist in the future (e.g., in the case of a time- expired DRM system), the company may be out of the business, or the DRM system may not be compatible with the devices that the consumers want to use to consume the content (e.g., in the case of a platform-restricted DRM system).
  • the consumer may have devices that can render the content, but such devices may not have the required DRM system.
  • Consumers also want all content to be available for any suitable device capable of rendering the content. Consumers also want to purchase the content once, and to be able to use that content at any suitable time in the future.
  • Content owners want to make their content accessible to consumers in accordance with usage rules stipulated in a license. Neither the content owner nor the consumer wants to be locked into a particular DRM system. DRM should not be a barrier to such goals. The fact that the current "content-centric" view does create such barriers hurts the content owners, because it limits a consumer's willingness to purchase content.
  • DRM systems offer different levels of enforcement. If content can travel to any compatible DRM system, a possible security problem is created. Consumers may move all their content to the least secure system, in order to take advantage of the lower level of rights enforcement. This fosters an environment in which the least secure DRM systems are the most widely used.
  • DRM systems enforce different sets of licensing conditions. Once again, if content can travel to any compatible DRM system, a possible security problem is created. For example, a consumer may move content from a DRM system that allows a one-day rental to a system that does not support the one-day rental restriction, in order to use the content beyond the one-day rental period.
  • DRM systems use different mechanisms to specify the usage rules assigned to content.
  • a DRM system may apply a fixed set of rules to all content types and/or instances, or such system may apply usage rules to content on an instance-by-instance basis.
  • DRM systems that apply usage rules to individual content instances vary in their ability to express types of usage rules.
  • DRM system A may enable content owners to stipulate that content can be viewed, but not copied.
  • DRM system B may provide this same capability, but also enable content owners to stipulate that content may be played only once.
  • DRM system C may use a language to offer greater flexibility in the expression of usage rules.
  • each DRM system has a proprietary user interface that consumers use to understand, consume, and inventory the content to which the consumers have access. Therefore, there is no consistency of user experience across DRM systems.
  • license acquisition when a consumer wants to acquire a license for content, the supplier of the license must understand the DRM system, and format, in order to provide content compatible with that combination of content, device, and DRM system.
  • OMA Mobile Alliance
  • REL Lights Expression Language
  • licenses With respect to life cycle, like most digital entities, licenses have lifecycles. Licenses are created, used to create new licenses, destroyed, expired, revoked, exercised, transferred, shared, and the like. Although an interoperable expression of rights is valuable in creating interoperable DRM systems, it does not provide all the functionality required to enable such systems to participate in the entire lifecycle of a digital license.
  • An exemplary shared license repository can be configured to implement a rich set of lifecycle capabilities (e.g., including peer-to-peer license transfer, renewal, search, acquisition, conversion from DRM to DRM, and the like).
  • the exemplary embodiments enable consumers to choose from a variety of repositories, such as handheld devices or web services, based on preferences of the consumers.
  • the exemplary embodiments improve the consumer's experience in dealing with a multitude of heterogeneous DRM systems, by providing mechanisms, and interfaces by which the shared license repository can interoperate with proprietary DRM systems.
  • a method, system, and device for license-centric content use or distribution including a pre-existing digital rights management (DRM) system having a unique interface to a repository of data thereof to govern use of content; a shared license repository configured to access the data to govern the use of the content and to communicate with the unique interface of the pre-existing DRM system; and a user interface configured to interact with the pre-existing DRM system, and configured to allow the user to send a license associated with the content from the shared license repository to the pre-existing DRM system or to another shared license repository.
  • DRM digital rights management
  • Figure 1 illustrates an exemplary system for describing interactions among exemplary components
  • Figure 2 provides an overview of an exemplary process for using a shared digital license repository of Figure 1;
  • Figure 3 illustrates an exemplary system for describing a shared license repository that provides a basic level of interoperability among proprietary DRM systems
  • Figure 4 illustrates an exemplary system including only some of the components illustrated in Figure 1.
  • the present invention includes recognition that in the current state of digital content consumption, a "content-centric" approach marries the content being consumed to a particular consumption application. For example, when a consumer want to consume digital content, the consumer double-clicks a file including the content in the file system explorer of the consumer, and the appropriate content consumption application launches.
  • the right to consume content is often tied to a particular embodiment of such content. For example, the right to view a movie is tied to physical possession of a DVD. If the content is being protected by a digital rights management (DRM) system, use of that content is predicated upon use of the particular DRM system originally used to protect the content.
  • DRM digital rights management
  • a license can include a representation of usage rules captured using rights expressions.
  • a license can convey the full context for the rights that are granted.
  • the information captured in a license can include the grantor of the rights, the grantee of the rights, the content, the permitted uses, and the associated terms and conditions.
  • a rights expression can include the manifestation of rights in digital form. Examples of rights expressions can include rights based on, for example, XML-based rights expression languages, such as ISO MPEG REL, XrML, SAML, XACML, ODRL, OMA REL, data structures, bit-fields, and the like.
  • consumers acquire (e.g. purchase, rent, exchange, and subscribe) licenses for content, and can use such licenses to use (e.g. consume, render, distribute, and share) the content, regardless of the consuming application or device used, the content distribution media, the DRM system used to enforce licensing terms, and the like.
  • a consumer can purchase a license for watching a movie, and such license need not be tied to a particular embodiment of such movie, such as a DVD. If the same movie is available on a different media, such as a pay-per-view broadcast or a high-definition DVD, the license of the consumer is still valid for watching that movie, assuming the license does permit such rendition.
  • the consumer acquires a license to play a movie on any devices within his home domain.
  • the license can be represented as an icon on his desktop.
  • DRM Player I e.g., Real Player
  • the movie plays on his PC monitor.
  • DRM Player II e.g., Windows Media Player
  • the movie also plays (e.g. on a large screen TV driven by DRM Player II).
  • the DRM Players fetch the content (e.g., as required) associated with the license suited for its rendering environment.
  • these devices also can fetch (e.g., as required) and render the content, as long as the devices belong to the home domain. This is much more convenient to the consumers than the state of the art DRM systems.
  • the exemplary embodiments enable consumers to access their inventory of purchased licenses, regardless of the consumer's location, the consuming application or device, or the proprietary DRM system that created the licenses.
  • the exemplary embodiments include an exemplary license repository that provides consumers with a single point of contact to manage all their licenses.
  • the exemplary license repository offers a consistent user interface to disparate DRM systems, while facilitating interoperability among such systems.
  • the exemplary embodiments include the storage and management of digital licenses, and the interfaces that provide access to such licenses.
  • the exemplary embodiments employ a "license-centric" approach to DRM-enabled digital content distribution.
  • Consumers acquire licenses for content, and can use such licenses to use the content, regardless of the consuming application or device used, the content distribution media, the DRM system used to enforce licensing terms, and the like.
  • a consumer can purchase a license for a music track, and the license need not be tied to a particular embodiment of the music, such as a CD. If the same music is available on a different media, such as an MP3 file for download, the consumer's license is still valid, and applicable assuming the license permits such rendition.
  • the exemplary embodiments improve the consumer's experience by enabling the consumer to focus on licenses, rather than on instances of content.
  • the exemplary embodiments improve the consumer's experience by enabling the consumer to better understand, and leverage their licenses, to accomplish lifecycle functions, such acquisition, peer- to-peer transfer (e.g., loan, sell, and the like), search, renew, archive, inventory, and the like.
  • the exemplary embodiments provide a consistent user experience, and a single point of contact for using and managing all licenses, regardless of the consumer's location, the consuming device, or the entities (e.g. proprietary DRM systems, content owners, and content distributors) that created the licenses.
  • the exemplary embodiments offer a minimal, yet sufficient, level of interoperability among different DRM systems, among different instances of the same DRM system, and among different versions of the same DRM system.
  • the exemplary embodiments provide mobile access to a shared digital license repository, and provide lifecycle management for stored licenses.
  • the exemplary embodiments include the storage of digital licenses, and the interfaces that provide access to such licenses.
  • the exemplary system 100 for license-centric content consumption can include licenses 106, 108, 128, 130, 132, and 134 that express usage rules for content.
  • the format of the licenses may be standardized, as in licenses 106, 128, 130, and 132, or proprietary, as in licenses 108, and 134.
  • Some proprietary licenses may be legal terms and conditions that the user agrees to when they acquire the content, the presence of the content within the proprietary DRM system, and an understanding of these terms and conditions forms the basis of the proprietary license.
  • the exemplary system 100 can include a shared digital license repository 142 that can be used by one or shared among multiple DRM systems, and/or instances of DRM systems 136, 138, and 140.
  • the shared digital license repository 142 can include one or more programmatic interfaces 110, 112, and 114 to interface with one or more of the proprietary DRM systems 136, 138, and 140, including repositories of the proprietary DRM systems, programmatic interfaces 122, 124, and 126 of the proprietary DRM systems, and/or the DRM systems themselves.
  • the programmatic interfaces 110, 112, 114, 122, 124, and 126 are logical functions. They can be implemented as part of the license repository and the proprietary DRM systems respectively or externally as separate glue ⁇ modules.
  • the shared digital license repository 142 can include one or more license management user interfaces 104 configured to manage the licenses, and further configured, as a part of the shared license repository 142, and/or as part of the proprietary DRM systems 136, 138, and 140.
  • the proprietary DRM systems 136, 138, and 140 can include DRM license repositories that are proprietary to the respective DRM systems, wherein the programmatic interface 122, 124, and 126, between instances of the shared digital license repository 142, are configured to enable license transfers therebetween.
  • the proprietary DRM systems 136, 138, and 140 also can include license management user interfaces 116, 118, and 120 that are configured to manage the transfer of licenses between the instances of shared digital license repositories.
  • the proprietary DRM systems 136, 138, and 140 can include the programmatic interfaces 122, 124, and 126, between service providers, and the shared digital license repository 142, configured to enable acquisition of licenses from the respective service providers, and configured for storage of the licenses on the shared digital license repository 142.
  • the license management user interfaces 116, 118, and 120 also can be configured to manage the acquisitions of new licenses from service providers, and for storage of the licenses on the shared digital license repository 142.
  • the shared digital license repository 142 also can include an authentication component 144 configured to provide authentication of the shared digital repository 142 itself, and/or the user/owner of the shared digital license repository 142.
  • the shared digital license repository 142 also can be configured as a repository for digital content.
  • the exemplary system 100 need not include all of the components described with respect to Figure 1, as further exemplary embodiments can include only some of the described components. [0040] At the heart of the exemplary system is the digital license repository
  • the repository 142 can store, searches for, and understand licenses that are either expressed explicitly or implied by context (e.g., ownership of a CD implies a license to play the corresponding music).
  • the licenses can be represented in a form unique to the repository 142.
  • the repository 142 can be configured as a mobile physical device that a user can carry, a device tethered to a network or tethered to a domain controlling device, such as a PC, set-top box, and game console, a software application running on a standard platform, a service accessible from various locations, and the like.
  • the shared digital license repository 142 enables multiple agents to participate in the lifecycle of licenses, wherein the multiple agents, advantageously, need not understand the proprietary expression of such licenses.
  • the shared digital license repository 142 interfaces 110, 112, and 114 can be configured for license search, license acquisition, peer-to-peer license transfer, license renewal, conversion of licenses between proprietary DRM system formats, and the like.
  • the shared digital license repository 142 provides the license management user interface 104 that enables a user to interpret the contents of the repository 142, and perform lifecycle functions on the licenses stored in the repository 142, such as backing up, acquiring new licenses, transferring licenses, searching for licenses, reporting state, status and inventory of licenses, renewing licenses, scavenging obsolete licenses, issuing licenses, converting licenses to standard format, converting licenses between proprietary formats, archiving licenses to paper or other digital form, and the like.
  • the shared digital license repository 142 provides the programmatic interfaces 110, 112, and 114 that enable the storage, searching, retrieval and other license lifecycle funtions that include rights expressions unique to the particular DRM system 136, 138, and 140.
  • the interfaces 110, 112, and 114 enable interoperability among the DRM systems 136, 138, and 140, advantageously, without requiring that the DRM systems 136, 138, and 140 understand each other's proprietary rights expressions.
  • the shared digital license repository 142 also can be configured to provide a proof of identity feature, for example, via the authentication component 144 that enables the proprietary DRM systems 136, 138, and 140 to authenticate users.
  • the shared digital license repository 142 can interact with other digital license repositories 142.
  • Each of the shared digital license repositories 142 can be configured to provide standardized interfaces (e.g., physical, programmatic, wireless or multiple, and the like) that enable the shared digital license repositories 142 to exchange licenses.
  • the ability to interact with other shared license repositories 142 enables users to select a repository based on their preferred experience for acting upon licenses or to transfer licenses between repositories.
  • One or more shared digital license repositories 142 can be implemented within a single computing entity. For example, a license repository service may provide the shared digital license repository service to multiple users.
  • the shared license repository 142 also caii employ a proprietary interface offered by a particular DRM system to interact with the particular DRM system. This enables the shared license repository 142 to interoperate with DRM systems that do not support the native programmatic interfaces 110, 112, and 114 provided by the shared digital license repository 142.
  • FIG. 2 provides an outline of exemplary steps for using the shared license repository 142, wherein in step 202 a user acquires, and configures the shared digital license repository 142.
  • the exemplary embodiments enable users to select a repository from a third party, unlike traditional DRM systems that are confined to proprietary repositories.
  • the shared digital license repository 142 can be a device, such as a handheld device that the user purchases, a software application running on a standard platform, a widely-available service, such as a web service or a service available to cellular phones, and the like. Since different implementations of the shared digital license repository 142 can offer different user interfaces, each user can choose among available shared digital license repository 142 offerings, for example, based on the user preferences, and the like. Then, the user can use the chosen shared digital license repository 142 to manage all their licenses, regardless of the DRM system that created the licenses.
  • the shared digital license repository 142 can be preloaded with a collection of licenses, or can interact with other digital license repositories 142 or various proprietary DRM systems 136, 138, and 140 to obtain the user's previously-acquired licenses.
  • the user can actively or passively acquire licenses, as part of another activity, such as purchasing content or a rendering program, and the like.
  • the shared digital license repository 142 can use the proprietary interface 122, 124, and 126 for each of the DRM systems 136, 138, and 140 to interact with the DRM systems 136, 138, and 140.
  • the shared digital license repository 142 can store copies of all the user's previously-purchased licenses.
  • the shared digital license repository 142 can be configured to copy the user's licenses from each of the DRM systems 136, 138, and 140 (e.g., via a pull process) or the DRM systems 136, 138, and 140 can be configured to copy the user's licenses to the shared license repository 142 (e.g., via a push process). Licenses can be explicitly expressed or implied from the consuming DRM system context (e.g., ownership of a DVD can imply a license to play the video encoded thereon).
  • the shared digital license repository 142 can enable content uses (e.g., rendering, consumption, copying, and distribution), using any suitable DRM system, by providing the necessary licenses in the proprietary format for the consuming DRM system. To use content, the appropriate license can be provided from the shared license repository 142 of the user to the consuming DRM system.
  • the shared digital license repository 142 also can be used to authenticate the user consuming the content, for example, via the authentication component 144. Depending on the shared digital license repository 142 implementation, authentication can include use of cryptographic keys, biometric mechanisms, and the like.
  • the shared digital license repository 142 can provide the user with a consolidated license user interface that provides many capabilities to ' use and manage licenses throughout the lifecycles of the licenses.
  • the user can choose among available repositories, based on the user's preferences, and can manage the licenses independently from the various DRM systems that originally created the licenses.
  • the exemplary embodiments permit the shared license repository 142 to implement a rich set of lifecycle capabilities, including license transfer (e.g., peer-to- peer), renewal, search, acquisition, conversion from DRM to DRM, and the like.
  • trust mechanisms such as digital signatures, and the like, provided by the originating DRM system, can be preserved when licenses are stored in the shared digital license repository 142. If the proof of the license's authenticity cannot be extracted from the originating DRM system or provided to the consuming DRM system, the shared license repository 142 can be used to attest to the license's authenticity.
  • the exemplary embodiments provide many advantages over conventional DRM systems. For example, with respect to consistency in the user experience, the exemplary embodiments allow consumers to perform license management operations using a single user interface.
  • the shared license repository 142 can include the license management user interface 104 that the user can use to manage licenses, regardless of where the licenses are stored, the entities (e.g., DRM system, content owners, and content distributors) that created the licenses, or the DRM system used to exercise the corresponding licensed rights.
  • the license management user interface 104 can interact with the proprietary DRM license repositories 136, 138, and 140 on behalf of the user.
  • the user need not directly interact with the various DRM systems 136, 138, and 140 from which the licenses originated.
  • the user can view information about all previously-acquired licenses, including information about the DRM systems to which such licenses apply.
  • the user also can use the shared license repository 142 to acquire additional licenses or renew expired licenses from any suitable DRM system.
  • the acquired licenses can be delivered directly to the shared license repository 142 for storage.
  • the user also can perform peer-to-peer transfers of licenses to other users via the license management user interface 104. In a transfer, the original user's license can be expired, revoked, or destroyed, and a new license can be created for another user on the shared digital license repository 142 of the other user.
  • the user also can create archival copies of licenses stored in the shared digital license repository 142 to be restored in the event of a DRM system failure, software/hardware move or upgrade, or change of authentication information such as email account and password.
  • Figure 3 illustrates an exemplary system 300, including the shared license repository 142 that provides a basic level of interoperability among proprietary DRM systems 136, 138, and 140.
  • the exemplary system 300 of Figure 3 operates in a similar manner as the exemplary system 100 of Figure 1 with respect to the common components.
  • Figure 4 illustrates a further exemplary system 400 that omits the shared license repository 142 component, and instead employs the shared license management user interface 104 to provide a virtual shared repository for combining licenses stored in the proprietary DRM systems 136, 138, and 140.
  • the shared license management user interface 104 can be configured to provide a view of all the user's licenses stored in the proprietary DRM repositories 136, 138, and 140.
  • the user interacts with the shared license management user interface 104, which uses the programmatic interfaces 122, 124, and 126, provided by the proprietary DRM repositories 136, 138, and 140, to effect user requests.
  • the exemplary system 400 of Figure 4 operates in a similar manner as the exemplary systems 100 and 300 of Figures 1 and 3, respectively, with respect to the common components.
  • the exemplary embodiments provide a consolidated license inventory.
  • the exemplary embodiments allow consumers to purchase content from a variety of sources (e.g., brick and mortar stores, satellite/cable, internet download, and the like) in a variety formats (e.g., DVD, Redbook audio, computer DVD, streaming, and the like), for a variety of devices (e.g., PCs, set top boxes, car stereos, devices networked to remote locations, and the like).
  • sources e.g., brick and mortar stores, satellite/cable, internet download, and the like
  • devices e.g., PCs, set top boxes, car stereos, devices networked to remote locations, and the like.
  • the exemplary embodiments also allow consumers to access content in accordance with the corresponding licenses, regardless of the licenses locations, the consumption device, or the DRM system that originally created the licenses.
  • the exemplary embodiments allow for all content to be available for any suitable device capable of rendering the content, within the usage rules stipulated by the corresponding licenses for the content.
  • the shared digital license repository 142 can store copies of all previously-acquired licenses of a user, providing a consolidated inventory of the licenses.
  • the shared digital license repository 142 can copy the user's licenses from each of the DRM systems 136, 138, and 140 (e.g., via a pull process) or the DRM systems 136, 138, and 140 can copy the user's licenses to the shared license repository 142 (e.g., via a push process).
  • the shared digital license repository 142 can use the proprietary programmatic interface 122, 124, and 126 for each of the DRM systems 136, 138, and 140 to interact with the DRM systems 136, 138, and 140.
  • the shared digital license repository 142 can be preloaded with a collection of licenses, such as all HBO or NFL programs, when the repository 142 is acquired.
  • a service or a software program can be employed to aggregate user's previously- acquired licenses, and load the licensees into the shared digital license repository 142.
  • the exemplary embodiments provide exemplary means to achieve license consolidation, but other equivalent means can be employed in further exemplary embodiments.
  • the exemplary embodiments provide user choices for shared digital license repositories, and DRM systems.
  • any suitable number of parties can offer shared digital license repository 142 implementations.
  • the user can make a preference-based selection of the shared digital license repository 142 to use.
  • the various implementers can differentiate their shared license repository 142 offerings according to factors, such as the storage of and access to licenses (e.g., portable device with a hardware interface, widely-available web service, and the like).
  • license management interfaces 104 can present a consolidated view of each user's licenses, regardless of the DRM system that created the licenses or the proprietary license repository on which the licenses are stored.
  • each shared digital license repository 142 can provide interoperability with an identified set of proprietary DRM license repositories.
  • implementer A might provide a shared license repository 142 as a web service that interoperates with proprietary DRM systems A, B, and C.
  • Implementer A's shared license repository 142 can maintain copies of all the licenses that a particular consumer acquired from proprietary DRM systems A, B, and C.
  • another implementer, B can confine interoperability to DRM systems A and B, but not C.
  • DRM vendors can offer their own proprietary user interface 104 that interoperates with the shared digital license repository 142.
  • the various DRM vendors can differentiate their offerings according to factors, such as the device that the consumer uses to interact with the shared digital license repository 142 (such as personal computer, PDA, cellular phone, and the like), the presentation of the user interface (e.g., graphical or text based), the capabilities of the interface (e.g., simplified or full-featured), the supported set of shared digital license repositories, price, and the like.
  • users can make preference- based selections of the user interface 104 to use, and still store all their licenses in a central, shared license repository 142.
  • the exemplary embodiments can use the shared digital license repository 142 to authenticate users.
  • the shared digital license repository 142 can optionally authenticate the user, for example, via the authentication component 144.
  • authentication can include use of cryptographic keys, biometric mechanisms, and the like.
  • An authentication license for example, in the form of an X.509 digital certificate or an ISO MPEG REL license with a possessProperty grant, and the like, can be provided to the consuming DRM system in the following ways.
  • the shared license repository 142 can provide the necessary license to the consuming DRM system in the proprietary format of the DRM system. For example, if the shared license repository 142 is available as a web service, and the consumer is using a PDA to consume content, the shared digital license repository 142 can provide the authentication license in the appropriate proprietary format to the DRM system residing on the PDA.
  • the consumer can copy the appropriate license from the shared digital license repository 142 to the consuming DRM system.
  • the shared digital license repository 142 is available as a portable device, and the consumer is using a personal computer to consume the content, the consumer can copy the license in the appropriate proprietary format to the DRM system residing on the personal computer.
  • the shared digital license repository 142 can be used by plugging the smart card into a host device, such as a PC, set-top box, game console, and the like.
  • a host device such as a PC, set-top box, game console, and the like.
  • the authentication licenses, and usage licenses can be made available to the host device to enable access, and use of the content.
  • the exemplary embodiments can be used for independent verification of content acquisitions.
  • trust mechanisms such as digital signatures, and the like, provided by the originating DRM system, can be preserved when licenses are stored in the shared license repository 142. If the proof of the license's authenticity cannot be extracted from the originating DRM system or provided to the consuming DRM system, the shared digital license repository 142 can be configured to attest to the license's authenticity.
  • the shared digital license repository 142 can provide independent verification of content acquisitions.
  • the shared digital license repository 142 acts an independent agent that determines whether, when, how, and where a license was previously acquired. DRM systems, other than the originating DRM system, may honor such a license based on trust in the shared digital license repository 142 attesting to the existence and trustworthiness of the license.
  • the shared digital license repository 142 enables consumers to prove such license acquisitions, if the licenses stored in the repository 142 need later to be reissued by the DRM system that originally created the licenses.
  • the exemplary embodiments can be used for exchange of licenses among interoperable repositories 142.
  • the exemplary embodiments allow consumers to access content in accordance with the corresponding licenses, regardless of the location of the licenses or the consumption device. Since any suitable number of parties can offer interoperable repositories 142, and license management interfaces to such repositories, each consumer can make a preference- based selection of one or more interoperable repositories to use.
  • the exemplary embodiments include interoperable repositories 142 that are able to exchange licenses. For example, assuming a consumer uses two interoperable repositories 142, one on a portable video player, and one available as a web service, and if the consumer has a license to play a particular movie on the portable video player, the exemplary embodiments allow the consumer to be able to transfer the license to the web service, and play the movie on a personal computer. Similarly, if a consumer uses a shared digital license repository 142 on a handheld device, and purchases a new handheld device, the exemplary embodiments allow the consumer to be able to transfer all the licenses from the old device to the new device. To provide such functionality, each shared digital license repository 142 can be configured to provide a standardized interface (e.g., physical, programmatic, or both) that enables the repository 142 to exchange licenses with other interoperable repositories 142.
  • a standardized interface e.g., physical, programmatic, or both
  • the exemplary embodiments provide interoperability, and since heterogeneity in the DRM marketplace will exist for years to come, the exemplary embodiments offer ways to facilitate concurrent deployment of such incompatible DRM systems, while still making consuming DRM-protected content an acceptable consumer experience. By offering such level of interoperability, the exemplary embodiments are able to offer a consistent user interface to disparate DRM systems.
  • the exemplary embodiments provide mobile access to digital licenses, regardless of the proprietary nature of the DRM system that created the licenses.
  • the exemplary embodiments can include a dedicated handheld license repository 142.
  • a user can purchase a portable license repository device 142, configured according to the exemplary embodiments, from a department store.
  • the user can choose to purchase the device 142 based on various features that differentiate the device from the competing devices offered by various manufacturers, such as the form factor, ergonomics of the device, the user interface, the perceived robustness and reliability, better or broader support for proprietary DRM APIs, availability, connectivity, peer-to-peer service compatibility, price, and the like.
  • the user can purchase the portable license repository 142, configured according to the exemplary embodiments, that supports USB, wireless service connectivity, that can work with and store licenses for any suitable type of content, that can interoperate with Adobe, Microsoft, and Adelphia DRM systems, and that can be connected to Microsoft Windows or MAC OS computers, a cellular phone, a set-top box, or a portable MP3 player.
  • a device can be configured as a dedicated device or the license repository 142 can be a feature of such a device that also includes other functions.
  • the user arrives home and can use the USB or wireless connectivity to attach the dedicated handheld license repository device 142 to, for example, Adobe, Microsoft, and Adelphia proprietary DRM systems on his personal computer running Microsoft Windows or some other software.
  • the repository device 142 can authenticate the user using biometric information (e.g., fingerprints) or the repository device itself can be the user's authentication (e.g., in the case of a smart card).
  • the device 142 can interact with each of the proprietary DRM systems 136, 138, and 140 using the corresponding proprietary interfaces 122, 124, and 126 thereof, extract the user's inventory of purchased licenses from each of the proprietary DRM systems 136, 138, and 140, and store copies of the extracted licenses.
  • the user can use a screen of the device 142 to view the inventory of purchased licenses, including information about the content, and the DRM systems 136, 138, and 140 to which the respective licenses apply.
  • the user can back up the licenses stored on the device 142 onto a computer.
  • the portable repository device 142 is ever broken, lost, stolen, or superseded by a "new and improved" device 142, the user will not lose all of the previously-acquired licenses, as the user can transfer the backup copies of the licenses to a replacement device.
  • the user can connect his license repository device 142 to his friend's computer, and make his license available for the content into his friend's Apple DRM system.
  • the user then can consume the downloaded content on his friend's computer using his own license, and the Apple DRM system installed on his friend's computer.
  • the exemplary embodiments can include the shared license repository
  • a user can subscribe to a web-based service that offers the shared license repository 142.
  • the user can access the shared license repository 142 service from any suitable device that has connectivity, regardless of the type of physical connection (e.g., DSL, cable modem service, wireless access, or ' satellite access).
  • the user can choose the shared license repository 142 web service based on various features that differentiate competing services, such as perceived robustness and reliability, better or broader support for proprietary DRM APIs, service functions such as backup and reporting, availability, connectivity, peer-to-peer service compatibility, price, and the like.
  • the user can subscribe to a shared license repository 142 service, which can work with and store licenses for any suitable type of content, and interoperate with Adobe, Microsoft, and Adelphia DRM systems.
  • the user can request that the shared license repository 142 service interact with the Adobe, Microsoft, and Adelphia proprietary DRM systems 136, 138, and 140 to obtain the user's licenses from each of the systems 136, 138, and 140.
  • the shared license repository 142 service can interact with each of the systems 136, 138, and 140 using the proprietary interfaces 122, 124 and 126 thereof, extract the user's inventory of acquired licenses from each of the systems 136, 138, and 140, and store copies of the licenses.
  • the user can use a web page of the shared license repository 142 service to view his inventory of acquired licenses, including information about the DRM system to which the licenses apply.
  • the user can use his friend's computer, and cable modem to connect to the shared license repository 142 service, and copy his license for the content into his friend's Microsoft DRM system.
  • the user then can consume the downloaded content on his friend's computer, using his own license, and the Microsoft DRM system installed on his friend's computer.
  • the exemplary embodiments can include the shared digital license repository 142 configured as a non-dedicated handheld device.
  • a handheld repository device 142 that is not dedicated can be integral to a device with another function, such as a cellular phone, a PDA, a portable game ' station, a portable video player ,or an MP3 player.
  • a user can purchase a PDA that includes a shared license repository 142.
  • the user can store licenses on the PDA for content protected with any suitable proprietary DRM system.
  • the user can consume such protected content using the PDA device, or can connect the PDA device to another consumption device, such as a PC, and the like.
  • the shared license repository 142 on the PDA can interoperate with the proprietary DRM system 136, 138, and 140 used to protect the content.
  • the shared license repository 142 can take place using the standardized interfaces 110, 112, and 114 of the shared license repository 142, if the DRM systems 136, 138, and 140 support such interfaces. If this is not possible, communication between the proprietary DRM systems 136, 138, and 140 and the shared license repository 142 can take place using the proprietary interfaces 122, 124, and 126 of the proprietary DRM systems 136, 138, and 140.
  • the exemplary embodiments can include the repository 142 interoperating with the DRM systems using proprietary interfaces.
  • a user subscribes to a web-based service that offers a shared license repository 142 that can work with and store licenses for any suitable type of content, and interoperate with Adobe, Microsoft, and Adelphia DRM systems 136, 138, and 140.
  • the user can use a computer to view an Adobe PDF file for which the user has a license stored in the shared license repository 142 web service.
  • Adobe Reader cannot locate a license for the PDF file in the Adobe proprietary license repository
  • Adobe Reader can prompt the user for the license location.
  • the user can provide the shared license repository 142 web service URL, and the Adobe DRM system then can use a proprietary interface thereof to interact with the shared license repository 142 web service, and obtain the appropriate license.
  • the repository 142 would behave as a repository that Adobe Reader already understands instead of a new standardized repository.
  • the Adobe DRM system then can check the provided license to determine whether stipulated usage rules are met, and if so, Adobe Reader can render the PDF file.
  • the exemplary embodiments can include the repository 142 interoperating with the DRM systems using a standard interface.
  • a user can purchase a dedicated portable repository device 142 that supports USB and wireless service connectivity.
  • the device 142 can provide a standard programmatic interface that can interoperate with any suitable DRM system that supports such an interface, and can store licenses for any suitable type of content.
  • the user arrives home and attaches the dedicated portable repository 142 to Microsoft, Adobe, and Apple DRM systemsl36, 138, and 140, all of which support the standard interface of the repository 142.
  • the dedicated portable repository 142 can interact with each of the DRM systemsl36, 138, and 140 using such standard interface, extract the user's inventory of acquired licenses from each of the systems 136, 138, and 140, and store copies of the licenses.
  • the user can travel to a friend's house, and download a video clip, for which the user has a license, from the internet onto a friend's computer.
  • the user then can try to play the video clip using Windows Media Player, but when Windows Media Player cannot locate a license for the video clip on the friend's computer, Windows Media Player can prompt the user for the license location.
  • the user can connect the dedicated portable repository 142 to the friend's computer, and specify the dedicated portable repository 142 as the license location.
  • the Microsoft DRM system on the friend's computer then can use the standard interface of the dedicated portable repository 142 to interact with the repository 142, and obtain the appropriate license.
  • the Microsoft DRM system would have been modified to support a new repository interface that is explicitly intended to allow consumers to have a shared license repository 142.
  • the Microsoft DRM system can check the provided license to determine whether stipulated usage rules are met, and if so, Windows Media Player can render the video clip.
  • the exemplary embodiments can include licenses that originate for the shared license repository 142.
  • a user can use a dedicated handheld repository device 142 to acquire, and store licenses, for any suitable type of content protected by a variety of proprietary DRM systems 136, 138, and 140.
  • the user wants to acquire a license for new content, the user can use the interface provided by the dedicated portable repository device 142.
  • the dedicated portable repository device 142 can search for the music the user wants to purchase.
  • the search interface of the dedicated portable repository device 142 can return all matching music files associated with licenses that are in either the standardized format of the device 142 or in proprietary formats for the DRM systems 136, 138, and 140 with which the dedicated handheld repository device 142 can interoperate.
  • the user can select the license the user wants to acquire (e.g., the license that costs the least).
  • the dedicated portable repository device 142 can obtain the selected license, and the music file can be downloaded to the MP3 player of the user.
  • the dedicated portable repository device 142 can provide the license to the proprietary DRM system used to protect the music file.
  • the exemplary embodiments can include peer-to-peer communication among dedicated portable repositories.
  • two users Jack and Nancy
  • both devices 142 can support the same standardized interface, so that the devices 142 can communicate with each other to perform various peer-to-peer activities, including license transfers and loans (e.g., temporary transfers), and the like.
  • Jack can connect his device 142 to Nancy's device 142, and use the user interface on his device 142 to transfer the license.
  • the original license on Jack's dedicated portable repository device 142 can be revoked, and a new, identical, license can created on Nancy's dedicated portable repository device 142.
  • This scenario would be practical for licenses granting usage rights to a group of people, such as members of a book club, and the like, to which both Jack and Nancy belong.
  • the proprietary DRM system that created, and consumes the transferred license can authorize the dedicated portable repository devices 142 to perform this type of license revocation, and creation. Therefore, when Nancy tries to use the new license, the proprietary DRM system trusts her license, and allows her to read the e-Book.
  • Jack can transfer his license for the e-Book to
  • Nancy's device 142 and the original license on Jack's dedicated portable repository device 142 can be marked as expired.
  • a new, similar, license can be created on Nancy's dedicated portable repository device 142.
  • the new license can grant the same usage rights, but can name Nancy as the person to whom such rights are granted.
  • the proprietary DRM system that created, and consumes the transferred license can authorize the dedicated portable repository devices 142 to perform this type of license revocation and creation. Therefore, when Nancy tries to use the new license, the proprietary DRM system trusts her license, and allows her to read the e-Book.
  • Jack can lend (e.g., temporarily transfer) his license to Nancy.
  • Jack's license can be disabled during the period of the loan, and Nancy's license can only be valid for the period of the loan.
  • Jack's license can be re-activated, and Nancy's license can expire.
  • the proprietary DRM system that creates, and consumes the licenses can authorize the dedicated portable repository devices 142 to perform this type of license expiration, and creation.
  • the dedicated portable repository devices 142 can communicate with a proprietary DRM system when performing peer- to-peer activities.
  • Jack's dedicated portable repository device 142 can request that the proprietary DRM system mark Jack's license as expired, and create a new license on Nancy's device ' 142.
  • Such requests can be made over the standardized interface of the dedicated portable repository device 142, if the proprietary DRM system supports such interface. Otherwise, the dedicated portable repository device 142 can use the proprietary interface of the DRM system to make such requests.
  • a transfer of a license can involve a financial transaction, and a third-party, such as an escrow or auction service.
  • a third-party such as an escrow or auction service.
  • Jack can auction licenses for rights to play several audio files, similar to selling a used CD collection. Nancy can bid on the licenses, and then win the auction.
  • Jack can transfer the licenses to an escrow account. Nancy can place her payment in the escrow account.
  • the escrow service can affect the transaction, transferring the payment to Jack, and transferring the licenses to Nancy's dedicated portable repository device 142, using a standardized interface thereof.
  • the exemplary embodiments can include the shared digital license repository 142 configured to provides license storage.
  • the shared digital license repository 142 can be used as a license storage service, without using or even having the license management user interface component 104.
  • a user can have a dedicated portable repository device 142 that can be used to store all licenses for the user.
  • the user can use the proprietary user interfaces provided by the DRM systems 136, 138, and 140 that created, and consume the licenses.
  • the proprietary DRM systems 136, 138, and 140 can communicate with the device 142 in various ways.
  • the DRM systems 136, 138, and 140 can look for the appropriate license on the dedicated portable repository device 142, and communicates with the device 142 using the standardized interface thereof.
  • the DRM systems 136, 138, and 140 also can look for the appropriate license on the dedicated portable repository device 142, and communicate with the device 142 using the proprietary interfaces of the DRM systems 136, 138, and 140.
  • the DRM systems 136, 138, and 140 also can look for the appropriate license in a proprietary license store of the DRM systems 136, 138, and 140.
  • the dedicated portable repository device 142 can be used to replace such a license store, and a transaction can be conducted with the licenses of the portable repository device 142. Accordingly, to the proprietary DRM systems 136, 138, and 140, the dedicated portable repository device 142 can look like the proprietary license store of the DRM systems 136, 138, and 140.
  • the exemplary embodiments can include the shared digital license repository 142 configured to verify content acquisitions.
  • a user can use the shared digital license repository 142 to address obsolescence of content media or DRM systems 136, 138, and 140.
  • the user can use the shared digital license repository 142 to verify a purchase of a license to particular content, and continue to access such content, even after the content media, which provided an implied license, or rendering device of the media has become obsolete.
  • the shared license repository 142 web service that interoperates with the various proprietary DRM systems 136, 138, and 140.
  • the shared license repository 142 web service also can interoperate with various online retailers of physical content media, such as Amazon.com. The user then can purchase a DVD for a movie from Amazon.com, wherein the purchase of the DVD implies a license to play the movie encoded on the DVD.
  • the shared digital license repository 142 web service can store such implied license.
  • the DVD can become obsolete (e.g., the DVD is replaced by streaming video), but because the user already has purchased the movie on DVD, the exemplary embodiments allow the user to continue watching the movie in another format, even though the DVD copy of the user has become outmoded.
  • the shared license repository 142 web service can attest that the user has already acquired a license for the movie in question.
  • the shared license repository 142 web service then ' can provide all the details of the original license proof of purchase, including the vendor (e.g., Amazon.com), the media (e.g., DVD), the date of purchase, the purchase price, and the like. Since the streaming video vendor can trust the shared license repository 142 web service, the user can be allowed to view the corresponding movie on streaming video.
  • the exemplarily embodiments include devices that support multiple physical interfaces.
  • the shared digital license repository 142 can include multiple physical mechanisms for connecting to other repositories or the DRM systems with which the repository 142 interoperates, such as USB, Bluetooth, 1394, PCMCIA, 802.11 (a/b/g), proprietary, RFID, CDMA, GSM, and the like. Such connections can be operated in parallel, serial, and the like.
  • the exemplarily embodiments include devices that support a variety of
  • DRM APIs for extracting licenses For example, a single shared digital license repository 142 can be configured to interoperate with several different DRM systems to extract licenses therefrom. Such interoperation can be via proprietary APIs that each DRM system natively supports.
  • the repository 142 can be configured to act as a rendering application for the purpose of extracting licenses when communicating with Adobe Acrobat. The repository 142 can query Adobe Acrobat about the permissible rights for a given piece of content, and record the results.
  • the exemplarily embodiments include devices that support a new standard API for accessing repositories of DRM systems.
  • a DRM vendor can offer direct support for digital license repositories 142, by supporting the standard APIs that explicitly enable each of the repositories 142 to query the DRM system to determine the available licenses.
  • the DRM systems can be configured to employ user interfaces thereof to push licenses to the shared digital license repository 142 or the repository 142 can be configured to pull licenses from the DRM systems.
  • a user can be using an instance of a
  • the DRM system can discover the shared repository 142, and offer to have the licenses that the DRM instance understands stored or copied into the repository 142.
  • the exemplarily embodiments include devices that support a mechanism for biometrically authenticating users of such devices. Accordingly, one complication in creating a DRM system is authenticating who or what can exercise the rights that have been expressed. Most conventional DRM systems bind usage of a given digital content instance to one specific instance of the DRM systems. For example, licenses typically are granted to a given device or PC. However, with exemplarily embodiments, the repository device 142 can offer an authentication service to DRM systems, such as a fingerprint reader, and the like. The DRM systems can query the repository 142 to check the fingerprint of the user of the device. In this way, licenses can be bound to the repository 142 or the fingerprint of the user connecting to multiple DRM systems, instead of being bound to an instance of a DRM system.
  • the DRM systems can be configured to trust the repository device 142 to authenticate a user. This is similar to the exemplary biometric system described above, but rather employing a log-in ID and password arrangement, digital certificate, RFID, or other type of user authentication system, and the like, that need not be biometrically based.
  • the DRM instance can bind the content to the authentication mechanism of the repository 142. Users can choose repositories 142 that support a form of authentication with which the users are comfortable.
  • a cell phone can be configured as the repository 142 to provide all the repository 142 functionality coupled with authentication via native identification capabilities of the cell phone.
  • the shared digital license repository 142 can be configured as a unique key, and the DRM systems can be configured to trust the presence of the unique key as the authorization for licenses.
  • a DRM system can be configured to check for accessibility to a uniquely-identified repository 142, and if the repository 142 is accessible, rights for ' the associated content can be exercised.
  • this exemplary embodiment enables mobility of licenses, wherein rights to content move as the repositories 142 move.
  • the exemplarily embodiments include the repository 142 not configured as a physical device, but rather configured as a connected service (e.g., cell phone service, Internet service, satellite service, and the like). Accordingly, the repository 142 need not be a physical device that the consumer owns, but rather can be configured as an Internet or mobile phone service, and the like. In such cases, the user can connect the repository 142 to an instance of a DRM system. Such connection can be built into the DRM system, if the DRM system natively supports the interface to the repository 142, or the connection can be made via a multifunction device, such a cell phone, and the like.
  • a connected service e.g., cell phone service, Internet service, satellite service, and the like.
  • the repository 142 need not be a physical device that the consumer owns, but rather can be configured as an Internet or mobile phone service, and the like.
  • the user can connect the repository 142 to an instance of a DRM system.
  • Such connection can be built into the DRM system, if
  • a user might have a Bluetooth- enabled CDMA phone that the user carries, and the user may encounter a Windows PC, and wish to exercise a stored license.
  • the phone can be connected to the PC via Bluetooth, and then using the phone as an intermediate, the. PC can be connected to the shared digital license repository 142 via CDMA. Then, the PC could find licenses for use in the CDMA-based repository 142.
  • the exemplarily embodiments include a user employing the digital license repository 142 to search online, and purchase new licenses.
  • the repository 142 can be configured to include its own user interface, and act as a store front for acquiring licenses from different services.
  • a user can visit a friend's home, and use the repository 142 to search for content for viewing or listening. After the content is identified, a purchase can take place, and a new license can be delivered to the repository 142. Then, the local DRM system at the friend's home can be used to view or listen to the content.
  • the exemplarily embodiments include a user making an offsite archival copy of content of the shared digital license repository device 142, and restoring the content for the future, if the device 142 is lost, stolen, or broken.
  • the shared digital license repository 142 or an offsite archival copy can be used for restoring the licenses of proprietary DRM systems 136, 138, and 140 if the licenses are lost, stolen, or broken.
  • the repository 142 can be configured to support an export mechanism that can be paper-based (e.g., glyphs or text for OCR), removable media-based (e.g., CDR or smart card), fixed media-based (e.g., a hard drive on a PC), service-based (e.g., Microsoft Passport), and the like.
  • an export mechanism can be paper-based (e.g., glyphs or text for OCR), removable media-based (e.g., CDR or smart card), fixed media-based (e.g., a hard drive on a PC), service-based (e.g., Microsoft Passport), and the like.
  • this enables users to retrieve their inventory of licenses, if the device 142 is lost, stolen, or broken.
  • the import of licenses from the archive can be proprietary to a brand of repository 142 or interoperable to enable a consumer to change repositories 142.
  • a shared digital license repository 142 of a user A can attach to a repository of a user B, wherein one of the licenses of the user A expires, and a new license that user B can use is created.
  • two users can agree to transfer a license from one repository 142 to another. In essence, two people agree to exchange rights for a specific content instance.
  • a user connects the two repositories 142 together, and gives a license away or sells the license.
  • the repositories 142 can include a mechanism to expire or to revoke a license that is given away or sold.
  • the repository device 142 can be authorized to expire, and generate new licenses, and the DRM systems can be configured to trust the device 142 to perform such a function.
  • the repository 142 can be entrusted by a DRM system to expire or terminate licenses.
  • the repository 142 can create a temporary license that can be exercised by the DRM system for a limited duration of time. In a disconnected system, the repository 142 can be trusted to generate limited licenses.
  • the repository 142 can use standardized
  • the repository 142 can be used to transfer a license from one DRM instance to another.
  • this exemplary ' embodiment enables two DRM systems to transfer a license via the repository 142, and connections thereof.
  • the right to transfer a license can be authorized, wherein the repository 142 acts as a conduit for the transfer.
  • the repository 142 can use APIs proprietary to the DRM systems that originally created licenses, to perform the expiration, and issuance of licenses, to execute the peer-to-peer license transfer.
  • the repository 142 can act as a responsible agent, and perform a transfer between two instances of DRM systems, instead of the repository 142 using standardized APIs to facilitate a license transfer with the cooperation of the DRM system. This transfer may or may not be a feature of either DRM system.
  • the repository 142 can be used to interpret rights.
  • the actual licenses can be stored in a DRM-neutral way, wherein the repository 142 interprets the rights instead of converting the license to a form that the DRM system can understand.
  • the repository 142 can be enhanced with an appropriate API that enables the DRM system to transfer responsibility for interpreting the licenses to the repository 142.
  • a peer-to-peer network of repositories 142 can be formed to facilitate license pooling, real ⁇ time/online auctioning, and the like.
  • a network of repositories 142 can be created, and can be used to transfer licenses in real-time.
  • a user for example, must offer five licenses for sharing.
  • the user can search the repository 142 network, and identify a license the user wants to exercise.
  • the license loan or transfer can be made to the repository 142 of the user in real time, and the DRM system can be notified to allow consumption. Thereafter, the license can be offered back to the repository 142 network.
  • such an exemplary system can potentially allow an infinite number of users to access an infinite number of licenses "legally.”
  • the repository 142 can be configured as a service to the DRM systems, and the DRM systems can use their own user interfaces to perform license management functions using standardized APIs.
  • the repository 142 can offer itself as a way for the DRM systems to store, and retrieve licenses.
  • the DRM systems can still own the management user interface for such licenses, wherein the DRM systems can be configured to support the APIs of the repository 142.
  • the repository 142 can be configured as a service to the DRM systems, and the DRM systems can use their own user interfaces to perform license management functions using proprietary APIs.
  • the repository 142 can offers itself as a way for the DRM systems to store, and retrieve licenses.
  • the DRM systems can still own the management user interface for such licenses, wherein the DRM systems are "tricked" into using the repository 142.
  • the repository 142 can be configured to intercept license store requests native to the DRM systems, and provide such functionality.
  • the repository 142 can include its own user interface to perform license management functions across each of the DRM systems via standardized APIs.
  • the user interface of the repository 142 can be configured to enable the user to see the licenses stored in an instance of a DRM system, wherein the DRM system can be configured to allow the repository 142 to access the license store of the DRM system via standardized APIs.
  • the repository 142 can include its own user interface to perform license management functions across each of the DRM systems via proprietary APIs.
  • the user interface of the repository 142 can be configured to enable the user to see the licenses stored in an instance of a DRM system, wherein the DRM system need not be modified, but rather the repository 142 is configured to uses the native APIs of the DRM system to determine the available licenses.
  • a seller can connect their repository 142 to a service, such as eBay, and the like, and offer licenses for auction, wherein eBay buyers then can browse the seller's repository 142, and prices for the licenses that are stored therein.
  • a service such as eBay, and the like
  • licenses for auction wherein eBay buyers then can browse the seller's repository 142, and prices for the licenses that are stored therein.
  • an escrow service thereafter verifies that a payment has been made, the seller's repository 142 can be connected to a repository 142 of the buyer, and a license transfer can be executed.
  • the repository 142 can be configured to offer other types of peer-to-peer license transfers.
  • other types of peer- to-peer transfers such as license lending and resale, can be supported between repositories 142.
  • the repositories 142 can transfer a license between each other, and agree to revoke and re-instate the loaned license, under appropriate conditions.
  • businesses can compete for the opportunity to create the repository 142 for a consumer, by providing better user interfaces, robustness, better proprietary API support, ergonomics, availability, peer- to-peer service compatibility, better price, reliability, and the like.
  • the form, capabilities, cost, and robustness of the repository 142 can be customized to find the right consumer.
  • a good precedence for this model is the variety and capabilities of cell phones and service programs in the wireless industry.
  • the above-described devices and subsystems of the exemplary embodiments of Figures 1-4 can include, for example, any suitable servers, workstations, PCs, laptop computers, PDAs, Internet appliances, handheld devices, cellular telephones, wireless devices, portable players, other devices, and the like, capable of performing the processes of the exemplary embodiments of Figures 1-4.
  • the devices and subsystems of the exemplary embodiments of Figures 1-4 can communicate with each other using any suitable protocol and can be implemented using one or more programmed computer systems or devices.
  • One or more interface mechanisms can be used with the exemplary embodiments of Figures 1-4, including, for example, Internet access, telecommunications in any suitable form (e.g., voice, modem, and the like), wireless communications media, and the like.
  • communications networks employed by the exemplary embodiments of Figures 1-4 can include one or more wireless communications networks, cellular communications networks, G3 communications networks, Public Switched Telephone Network (PSTNs), Packet Data Networks (PDNs), the Internet, intranets, a combination thereof, and the like.
  • PSTNs Public Switched Telephone Network
  • PDNs Packet Data Networks
  • the Internet intranets, a combination thereof, and the like.
  • a single computer system can be programmed to perform the special purpose functions of one or more of the devices and subsystems of the exemplary embodiments of Figures 1-4.
  • two or more programmed computer systems or devices can be substituted for any one of the devices and subsystems of the exemplary embodiments of Figures 1-4.
  • principles and advantages of distributed processing such as redundancy, replication, and the like, also can be implemented, as desired, to increase the robustness and performance the devices and subsystems of the exemplary embodiments of Figures 1-4.
  • 1-4 can store information relating to various processes described herein. This information can be stored in one or more memories, such as a hard disk, optical disk, magneto-optical disk, RAM, and the like, of the devices and subsystems of the exemplary embodiments of Figures 1-4.
  • One or more databases of the devices and subsystems of the exemplary embodiments of Figures 1-4 can store the information used to implement the exemplary embodiments of the present invention.
  • the databases can be organized using data structures (e.g., records, tables, arrays, fields, graphs, trees, lists, and the like) included in one or more memories or storage devices listed herein.
  • the processes described with respect to the exemplary embodiments of Figures 1-4 can include appropriate data structures for storing data collected and/or generated by the processes of the devices and subsystems of the exemplary embodiments of Figures 1-4 in one or more databases thereof.
  • All or a portion of the devices and subsystems of the exemplary embodiments of Figures 1-4 can be conveniently implemented using one or more general purpose computer systems, microprocessors, digital signal processors, micro ⁇ controllers, and the like, programmed according to the teachings of the exemplary embodiments of the present invention, as will be appreciated by those skilled in the computer and software arts.
  • Appropriate software can be readily prepared by programmers of ordinary skill based on the teachings of the exemplary embodiments, as will be appreciated by those skilled in the software art.
  • the devices and subsystems of the exemplary embodiments of Figures 1-4 can be implemented on the World Wide Web.
  • the devices and subsystems of the exemplary embodiments of Figures 1-4 can be implemented by the preparation of application- specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be appreciated by those skilled in the electrical art(s).
  • the exemplary embodiments are not limited to any specific combination of hardware circuitry and/or software.
  • the exemplary embodiments of the present invention can include software for controlling the devices and subsystems of the exemplary embodiments of Figures 1-4, for driving the devices and subsystems of the exemplary embodiments of Figures 1-4, for enabling the devices and subsystems of the exemplary embodiments of Figures 1- 4 to interact with a human user, and the like.
  • software can include, but is not limited to, device drivers, firmware, operating systems, development tools, ' applications software, and the like.
  • Such computer readable media further can include the computer program product of an embodiment of the present invention for performing all or a portion (if processing is distributed) of the processing performed in implementing the invention.
  • Computer code devices of the exemplary embodiments of the present invention can include any suitable interpretable or executable code mechanism, including but not limited to scripts, interpretable programs, dynamic link libraries (DLLs), Java classes and applets, complete executable programs, Common Object Request Broker Architecture (CORBA) objects, and the like. Moreover, parts of the processing of the exemplary embodiments of the present invention can be distributed for better performance, reliability, cost, and the like.
  • interpretable programs including but not limited to scripts, interpretable programs, dynamic link libraries (DLLs), Java classes and applets, complete executable programs, Common Object Request Broker Architecture (CORBA) objects, and the like.
  • CORBA Common Object Request Broker Architecture
  • the devices and subsystems of the exemplary embodiments of Figures 1-4 can include computer readable medium or memories for holding instructions programmed according to the teachings of the present invention and for holding data structures, tables, records, and/or other data described herein.
  • Computer readable medium can include any suitable medium that participates in providing instructions to a processor for execution. Such a medium can take many forms, including but not limited to, non-volatile media, volatile media, transmission media, and the like.
  • Non- volatile media can include, for example, optical or magnetic disks, magneto-optical disks, and the like.
  • Volatile media can include dynamic memories, and the like.
  • Transmission media can include coaxial cables, copper wire, fiber optics, and the like.
  • Transmission media also can take the form of acoustic, optical, electromagnetic waves, and the like, such as those generated during radio frequency (RF) communications, infrared (IR) data communications, and the like.
  • RF radio frequency
  • IR infrared
  • Common forms of computer-readable media can include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other suitable magnetic medium, a CD- ROM, CDRW, DVD, any other suitable optical medium, punch cards, paper tape, optical mark sheets, any other suitable physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH- EPROM, any other suitable memory chip or cartridge, a carrier wave, or any other suitable medium from which a computer can read.

Abstract

L'invention concerne un procédé, un système et un dispositif destinés à l'utilisation ou à la distribution d'un contenu centré autour d'une licence, y compris un système préexistant de gestion des droits numériques (DRM) possédant une interface unique avec un dépôt de données de manière à permettre la gestion de l'utilisation du contenu; un dépôt de licence partagée, configuré pour accéder aux données de manière à gérer l'utilisation du contenu et à communiquer avec l'interface unique du système DRM préexistant; et une interface utilisateur configurée pour interagir avec le système DRM préexistant, configuré pour permettre à l'utilisateur d'envoyer une licence associée au contenu avec le dépôt de licence partagée à destination du système DRM préexistant ou d'un autre dépôt de licence partagée.
PCT/US2004/038474 2004-11-18 2004-11-18 Procede, systeme et dispositif destines a la consommation de contenu centre autour d'une licence WO2006054988A2 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
JP2007542998A JP4898699B2 (ja) 2004-11-18 2004-11-18 ライセンスセントリックでコンテンツを使用するシステムおよび共有ライセンスレポジトリ
KR1020127027792A KR101350104B1 (ko) 2004-11-18 2004-11-18 라이센스 중심의 콘텐츠 소비를 위한 방법, 시스템, 및 장치
KR1020077013787A KR101213913B1 (ko) 2004-11-18 2004-11-18 라이센스 중심의 콘텐츠 소비를 위한 방법, 시스템, 및장치
EP20040811253 EP1829270A4 (fr) 2004-11-18 2004-11-18 Procede, systeme et dispositif destines a la consommation de contenu centre autour d'une licence
PCT/US2004/038474 WO2006054988A2 (fr) 2004-11-18 2004-11-18 Procede, systeme et dispositif destines a la consommation de contenu centre autour d'une licence
CN2004800447185A CN101421969B (zh) 2004-11-18 2004-11-18 许可证中心的内容消费的方法、系统和设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2004/038474 WO2006054988A2 (fr) 2004-11-18 2004-11-18 Procede, systeme et dispositif destines a la consommation de contenu centre autour d'une licence

Publications (2)

Publication Number Publication Date
WO2006054988A2 true WO2006054988A2 (fr) 2006-05-26
WO2006054988A3 WO2006054988A3 (fr) 2009-04-30

Family

ID=36407569

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2004/038474 WO2006054988A2 (fr) 2004-11-18 2004-11-18 Procede, systeme et dispositif destines a la consommation de contenu centre autour d'une licence

Country Status (5)

Country Link
EP (1) EP1829270A4 (fr)
JP (1) JP4898699B2 (fr)
KR (2) KR101350104B1 (fr)
CN (1) CN101421969B (fr)
WO (1) WO2006054988A2 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006097797A1 (fr) * 2005-01-27 2006-09-21 Nokia Corporation Systeme et procede permettant d'acceder a des fichiers proteges par drm oma a partir d'applications java
JP2008219552A (ja) * 2007-03-06 2008-09-18 Nec Corp 認証用イメージデータ生成装置、認証装置、認証用イメージデータ生成方法、認証方法及びプログラム
WO2009002643A1 (fr) * 2007-06-26 2008-12-31 Digital Keystone, Inc. Systèmes et procédés pour un accès conditionnel et une gestion de droits numériques
EP2009566A1 (fr) * 2007-06-29 2008-12-31 Thomson Licensing Procédé et dispositif d'échange de licences d'accord numériques
EP2248058A1 (fr) * 2008-02-28 2010-11-10 Honeywell International Inc. Système de gestion de licence de logiciel de poste-à-poste en vue de la réinstallation temporaire de licences de logiciel disponibles
KR101041368B1 (ko) * 2009-03-19 2011-06-14 주식회사 코아로직 라이센스 접근 방법 및 상기 라이센스 접근 방법을 이용하는 단말기
JP2011223578A (ja) * 2010-04-06 2011-11-04 Copyright Clearance Center Inc ライセンスを受けた視聴者へストリーミング映像の配信を許可する方法および装置
EP2065826A3 (fr) * 2007-11-22 2012-06-27 Thomson Licensing Procédé de transfert de licences de contenu numérique et dispositif de réception de telles licences

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090036326A (ko) * 2007-10-09 2009-04-14 삼성전자주식회사 방송 스트림 녹화 방법 및 단말기
KR100917312B1 (ko) * 2007-09-27 2009-09-11 (주) 엘지텔레콤 재구매를 위한 디지털 저작권 컨텐츠의 정보 갱신 시스템및 그 방법과 그 기능의 컴퓨터 프로그램이 기록된기록매체
KR101434354B1 (ko) 2007-11-07 2014-08-27 삼성전자 주식회사 Ｄｒｍ 권한 공유 시스템 및 방법
CN101957893B (zh) * 2009-07-15 2013-02-20 精品科技股份有限公司 档案使用权限管理系统
US8356359B2 (en) * 2010-04-19 2013-01-15 Ericsson Television, Inc. Licensing rights for media content that follows a subscriber
US20110302009A1 (en) * 2010-06-02 2011-12-08 Freed Ian W Referring, Lending, and Reselling of Digital Items
US8799363B2 (en) 2011-03-29 2014-08-05 Amazon Technologies, Inc. Lending digital items to identified recipients
US10296878B1 (en) 2011-06-28 2019-05-21 Amazon Technologies, Inc. Platform for providing generic e-content
CN104572890B (zh) * 2012-07-03 2019-02-19 厦门简帛信息科技有限公司 一种基于数字资源的网络系统的使用方法及作业方法
JP6424499B2 (ja) * 2014-07-10 2018-11-21 株式会社リコー 画像形成装置、情報処理方法、及びプログラム
KR102324837B1 (ko) * 2020-03-09 2021-11-10 군산대학교산학협력단 라이센스 정보 기반의 응용 프로그램 실행 방법 및 라이센스 정보 관리 방법

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030126086A1 (en) 2001-12-31 2003-07-03 General Instrument Corporation Methods and apparatus for digital rights management

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999027681A2 (fr) * 1997-11-25 1999-06-03 Motorola Inc. Procedes et systemes de restitution de contenu audio, et articles fabriques
JP4329258B2 (ja) * 1999-10-25 2009-09-09 ソニー株式会社 コンテンツデータの制御装置及び方法、並びに、記憶媒体
CA2356343A1 (fr) * 1999-10-25 2001-05-17 Sony Corporation Procede de gestion de donnees de contenu
JP4477822B2 (ja) * 2001-11-30 2010-06-09 パナソニック株式会社 情報変換装置

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030126086A1 (en) 2001-12-31 2003-07-03 General Instrument Corporation Methods and apparatus for digital rights management

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100918253B1 (ko) 2005-01-27 2009-09-21 노키아 코포레이션 Ｏｍａ ｄｒｍ 보호되는 파일에 자바 애플리케이션으로부터액세스하기 위한 시스템 및 방법
WO2006097797A1 (fr) * 2005-01-27 2006-09-21 Nokia Corporation Systeme et procede permettant d'acceder a des fichiers proteges par drm oma a partir d'applications java
US8739291B2 (en) 2005-01-27 2014-05-27 Nokia Corporation System and method for providing access to OMA DRM protected files from java application
JP2008219552A (ja) * 2007-03-06 2008-09-18 Nec Corp 認証用イメージデータ生成装置、認証装置、認証用イメージデータ生成方法、認証方法及びプログラム
WO2009002643A1 (fr) * 2007-06-26 2008-12-31 Digital Keystone, Inc. Systèmes et procédés pour un accès conditionnel et une gestion de droits numériques
US8474054B2 (en) 2007-06-26 2013-06-25 Digital Keystone, Inc. Systems and methods for conditional access and digital rights management
US8464355B2 (en) 2007-06-29 2013-06-11 Thomson Licensing Method and device for exchanging digital content licenses
EP2009566A1 (fr) * 2007-06-29 2008-12-31 Thomson Licensing Procédé et dispositif d'échange de licences d'accord numériques
EP2009567A1 (fr) * 2007-06-29 2008-12-31 Thomson Licensing Procédé de transfert de licences de contenu numérique et dispositif de réception de telles licences
WO2009003883A1 (fr) * 2007-06-29 2009-01-08 Thomson Licensing Procédé et dispositif pour échanger des licences de contenu numérique
US20100146630A1 (en) * 2007-06-29 2010-06-10 Olivier Courtay Method and device for exchanging digital content licenses
EP2065826A3 (fr) * 2007-11-22 2012-06-27 Thomson Licensing Procédé de transfert de licences de contenu numérique et dispositif de réception de telles licences
EP2248058A1 (fr) * 2008-02-28 2010-11-10 Honeywell International Inc. Système de gestion de licence de logiciel de poste-à-poste en vue de la réinstallation temporaire de licences de logiciel disponibles
EP2248058A4 (fr) * 2008-02-28 2012-12-19 Honeywell Int Inc Système de gestion de licence de logiciel de poste-à-poste en vue de la réinstallation temporaire de licences de logiciel disponibles
KR101041368B1 (ko) * 2009-03-19 2011-06-14 주식회사 코아로직 라이센스 접근 방법 및 상기 라이센스 접근 방법을 이용하는 단말기
JP2011223578A (ja) * 2010-04-06 2011-11-04 Copyright Clearance Center Inc ライセンスを受けた視聴者へストリーミング映像の配信を許可する方法および装置

Also Published As

Publication number Publication date
KR20120132569A (ko) 2012-12-05
WO2006054988A3 (fr) 2009-04-30
JP2008525864A (ja) 2008-07-17
KR101350104B1 (ko) 2014-01-08
KR101213913B1 (ko) 2012-12-18
EP1829270A4 (fr) 2011-10-19
JP4898699B2 (ja) 2012-03-21
CN101421969A (zh) 2009-04-29
CN101421969B (zh) 2013-05-29
KR20070086381A (ko) 2007-08-27
EP1829270A2 (fr) 2007-09-05

Similar Documents

Publication Publication Date Title
US20200074046A1 (en) Method, system, and device for license-centric content consumption
US8660961B2 (en) Method, system, and device for license-centric content consumption
KR20110045104A (ko) 라이센스 중심의 콘텐츠 소비를 위한 방법, 시스템, 및 장치
US7496540B2 (en) System and method for securing digital content
KR101350104B1 (ko) 라이센스 중심의 콘텐츠 소비를 위한 방법, 시스템, 및 장치
US7818262B2 (en) System and method for providing a flexible licensing system for digital content
US20060190410A1 (en) Digital content distribution systems and methods
KR101213818B1 (ko) 라이센스 중심의 콘텐츠 소비를 위한 방법, 시스템, 및장치
CN101901324B (zh) 许可证中心的内容消费的方法、系统和设备
JP6047076B2 (ja) Ｄｒｍシステムを備える装置及びライセンスリポジトリ
JP2012065353A (ja) ライセンスレポジトリデバイス、方法、及びレンダリングデバイス
JP2015207297A (ja) Ｄｒｍシステムを備える装置
KR100773081B1 (ko) 네트워크 기반의 유료컨텐츠 통합관리방법 및 그 시스템
CN103353927B (zh) 许可证中心的内容消费的方法、系统和设备
JP2003114947A (ja) 著作物データ交換システム、著作物データ交換方法、及び著作物データ交換プログラム

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200480044718.5

Country of ref document: CN

AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2007542998

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 912/MUMNP/2007

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2004811253

Country of ref document: EP

Ref document number: 1020077013787

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 2004811253

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 1020117008735

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 1020127027792

Country of ref document: KR