WO2008069887A2 - Procédé et système destinés à permettre l'accès du contenu d'un second système de gestion numérique des droits (drm) dans un premier système drm qui est protégé - Google Patents

Procédé et système destinés à permettre l'accès du contenu d'un second système de gestion numérique des droits (drm) dans un premier système drm qui est protégé Download PDF

Info

Publication number
WO2008069887A2
WO2008069887A2 PCT/US2007/023615 US2007023615W WO2008069887A2 WO 2008069887 A2 WO2008069887 A2 WO 2008069887A2 US 2007023615 W US2007023615 W US 2007023615W WO 2008069887 A2 WO2008069887 A2 WO 2008069887A2
Authority
WO
WIPO (PCT)
Prior art keywords
license
content
drm
drm system
application
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/US2007/023615
Other languages
English (en)
Other versions
WO2008069887B1 (fr
WO2008069887A3 (fr
Inventor
Fabrice Jogand-Coulomb
Haluk K. Tanik
Oktay S. Rasizade
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
SanDisk Corp
Original Assignee
SanDisk Corp
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
Priority claimed from US11/599,991 external-priority patent/US20080114692A1/en
Priority claimed from US11/600,005 external-priority patent/US20080114693A1/en
Application filed by SanDisk Corp filed Critical SanDisk Corp
Publication of WO2008069887A2 publication Critical patent/WO2008069887A2/fr
Publication of WO2008069887A3 publication Critical patent/WO2008069887A3/fr
Publication of WO2008069887B1 publication Critical patent/WO2008069887B1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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]

Definitions

  • a digital rights management (“DRM”) system is used to provide or limit access to content according to a set of permissions, which are usually stored in a license.
  • Differences in DRM systems e.g., differences in file format and/or license format
  • Differences in DRM systems can prevent an application operating with one type of DRM system from accessing content protected by a different type of DRM system.
  • an application that uses a DRM system that specifies a file format with a header that contains information needed to allow the application to access the content. If this application attempts to access content protected by a different DRM system that does not specify a header in its file format, the application will not find the needed information and will not be able to access the content.
  • a request is received from a host application for a license for content protected by a first DRM system, the first DRM system being different from the host application's DRM system.
  • a license supported by the host application's DRM system is then generated from a license supported by the first DRM system.
  • a request is received to store content protected by a first DRM system.
  • a portable license for the content is generated from a license • > supported by the first DRM system.
  • a portable file format for the content is generated from a file format supported by the first DRM system.
  • the request can come from a first computing platform, and the portable license and/or file format can be generated by a second computing platform.
  • Other embodiments are disclosed, and each of the embodiments can be used alone or together in combination. [0004] The embodiments will now be described with reference to the attached drawings.
  • Figure 1 is an illustration of a host device and a portable memory device of an embodiment.
  • Figure 2 is an illustration of a software agent of an embodiment.
  • Figure 3 is a flow chart of a method of an embodiment for converting a file format and a license format.
  • Figure 4 is an illustration of an embodiment showing conversion of a file format.
  • Figure 5 is an illustration of another host device communicating with the portable memory device of Figure 1.
  • Figure 6 is an illustration of a software agent of the host device of Figure 5.
  • Figure 7 is a flow chart of a method of an embodiment for allowing content protected by a first DRM system to be accessed by a second DRM system.
  • Figure 8 is a flow chart showing the acts in the "check license" act in Figure
  • the embodiments described below generally relate to allowing content that is protected by one type of digital rights management (“DRM”) system to be used by an application that uses a different type of DRM system.
  • DRM digital rights management
  • content refers to digital media and can include, but is not limited to, an audio file, a video file (with or without audio), a game, a book, a map, a data file, or a software program.
  • a DRM system controls access to content.
  • “access” is any action taken with respect to the content. Examples of various types of "access” include, but are not limited to, playing, displaying, printing, copying, and executing.
  • a DRM system is used to provide or limit access to content according to a set of permissions, which are usually stored in a license associated with the content.
  • a "permission” is used to refer to either a permission or a restriction.
  • a license (which may also be referred to herein as a "license object” or a “content license”) is an entity that stores permissions regarding the access of content. For example, the license can restrict the number of times the content can be accessed or set an expiration date and time for such access.
  • a license can also contain information about how to un-cipher ciphered content (e.g., a cipher key).
  • a license can be stored in any suitable location, with or separate from its associated content.
  • both the license and the content are stored together on a portable memory device, while, in another embodiment, the content is stored in the host or the network (or on a portable memory device), and the license is storied in a portable memory device (or in the network). Accordingly, the content and the license do not need to be stored on the same device.
  • Differences in DRM systems can prevent an application operating with one type of DRM system from accessing content protected by a different type of DRM system.
  • An application operating under a certain type of DRM system may expect to find certain information at certain locations (in the content or in the license, for example), and if the application does not find that information at that location, the application may not be able to access the content.
  • One difference between DRM systems can be file format. Content is usually stored in a file characterized by a file format (e.g., whether or not the file has a header or footer, the location in the file where the content starts/stops, etc.). Differences in file format can lead to incompatibility.
  • the file format for the iMode DRM system is a regular file format.
  • the file format for the OMA DRM system contains a header that contains information needed for the OMA DRM system to access the content (e.g., identification and location of the license that contains the cipher key and permissions). Accordingly, when an application operating with the OMA DRM system attempts to read a file protected by the i-Mode DRM system, the application will not find the expected header (since one is not present in an i-Mode- protected file), and the application will not be able to access the content.
  • DRM systems can be license format. As with file format, if an application operating under a certain type of DRM system does not find certain information at a certain location in the license, the application may not be able to check the license for permission and, accordingly, may not be able to access the content associated with the license. Different DRM systems may also have different license acquisition protocols. [0015] The embodiments described herein provide a component that performs the required translations/conversions to allow content protected by one type of DRM system to be compatible with an application using a different type of DRM system.
  • the component takes the form of a software agent running on a host device.
  • the component can be take other forms and be located at different locations (e.g., in a second computing platform in a portable memory device).
  • the component can also be distributed among different components (e.g., between a host device and a portable memory device).
  • a "host device” is any device that can be used to access content and includes, but is not limited to, a cell phone, a PC/notebook computer, a handheld computer, a handheld game console, an audio player (e.g., an MP3 player), a video player (e.g., a DVD player or a portable video player), an audio and/or video recorder, a digital camera, a set-top box, a display device (e.g., a television), a printer, a car stereo, and a navigation system.
  • a cell phone e.g., a PC/notebook computer
  • a handheld computer e.g., a portable computer
  • an audio player e.g., an MP3 player
  • a video player e.g., a DVD player or a portable video player
  • an audio and/or video recorder e.g., a digital camera
  • a set-top box e.g., a display device
  • a display device e.g
  • the host device 50 in Figure 1 comprises one or more processors 55 executing a host application 60 and a software agent 70.
  • the software agent 70 provides "cross DRM" compatibility and can provide other functions, such as security management functionality (e.g., login and decrypting mechanisms).
  • the host application 60 and the software agent 70 can be implemented as computer-readable instructions stored on a computer-readable medium and executed by one or more processors 55 on the host device 50.
  • the host application 60 and the software agent 70 are shown as separate components, in an alternate embodiment, those components can be combined into a single component.
  • Other components of the host device 50 such as a display device and driver(s), are not shown in Figure 1 for simplicity.
  • a "host application” refers to any application that can be used to access content. Examples of a host application include, but are not limited to, an audio player, a video player, and a document viewer. In addition to accessing content, a host application can have other functions, such as downloading content and storing information on a portable memory device. In this example, the host application 60 is operating under a DRM system referred to herein as "DRM x.”
  • DRM x DRM system
  • the host device 50 is in communication with the portable memory device 80.
  • a portable memory device is any device that contains a storage medium that can store content and be put in communication with a host device that can access the content stored in the storage medium.
  • a portable memory device can contain only memory (and associated circuitry) or can also contain other components, such as a processor.
  • portable memory devices include, but are not limited to, a removable memory card (e.g., a non-volatile, solid-state memory device, such as a flash memory card), an optical disc, a magnetic disk, as well as any of the examples of host devices listed above, when those devices have a storage medium and the capability of being placed in (wired or wireless) communication with a host device to access information stored in the storage medium.
  • a "host device” in some situations can be a "portable memory device” to another host device in other situations.
  • a cell phone can be used as a host device.
  • a cell phone can be used as a portable memory device when the cell phone is connected to a personal computer so content can be delivered from the cell phone to the personal computer.
  • a portable memory device can serve as a dedicated storage device or can contain additional functionality, such as playing music, making phone calls, etc.
  • content and/or a license can be provided to the host device without the use of a portable memory device (such as when the host device downloads the content and/or the license from a server).
  • a host device does not necessarily have to "host” a portable memory device in order to receive the content and/or a license for the content
  • the software agent 70 acts as a component that allows DRM x protected content to be accessible by different types of DRM systems.
  • Figure 2 is an illustration showing more detail of the software agent 70. As shown in Figure 2, the software agent 70 comprises (1) a common interface 72 for protected content and DRM and (2) a host-customized layer 74 for license format translation and generation.
  • the software agent 70 can have other components, which are not shown in Figure 2 to simplify the drawing.
  • the basic principle of compatibility in this embodiment is that the software agent 70 is not only loaded onto the host device 50 in Figure 1 , but is also loaded onto other host devices that wish to gain "cross DRM" compatibility.
  • the common interface 72 is the same in each of these software agents, while the host- customized layer 74 is customized to the DRM system of a particular host device.
  • the host-customized layer can generate a license that is supported by the host application's DRM system and provide access to the content - even if the file format and/or the license format of the DRM protected content is not supported by the host application's DRM system.
  • the host application 60 when the host application 60 wishes to save protected content to the portable memory device 80, because the host application 60 is operating under DRM x, the host application 60 would issue a command to save the content in a DRM x file format and to save a license in a DRM x license format (as shown by arrow 125 in Figure 2). (Alternatively, the host application 60 can issue a command to save the content in a cross-DRM format.)
  • DRM x is not supported by the common interface 72. Accordingly, if the content and the license were saved in a DRM x format, software agents in other host devices would not be able to read the content and the license, thereby preventing host applications on other host devices from accessing the protected content.
  • the software agent 70 performs the method shown in the flow chart in Figure 3.
  • the protected content is transferred to the software agent 70 to handle (act 150).
  • the file format of the protected content is changed to be compatible with the common interface 72 (act 155).
  • This act is illustrated diagrammatically in Figure 4.
  • a file 88 contains the protected content 100 (which is shown as ciphered) and a header 108 that stores information used in the DRM x system. This file format is not recognized by the common interface 72 of the software agent 70.
  • the host-customized layer 72 works with the common interface 72 to change the file format to be compatible with the common interface 72.
  • the content can be un-ciphered and then stored as ciphered on the portable memory device 80, or the ciphered content can simply be moved to the portable memory device 80.
  • the result is a file 90 with a file format that is recognized by the common interface 72 of the software agent 70; here, with a header 110 containing the DRM information (e.g., play only five times, etc.).
  • content information may be updated to specify that the content is to be handled by the software agent.
  • this information is shown as "+ INFO" in the file header 110.
  • a software agent on the same or different host device attempts to access the content, it will see this information and know that it needs to perform the cross-DRM functionality described below.
  • it may be preferred to update the content information to specify that the content is to be handled by the software agent as the software agent may be able to perform addition functions with respect to this content. Examples of such additional functions are described in the patent documents referenced below.
  • the license associated with the content is transferred to the software agent 70 (act 165).
  • the permissions could be transferred directly instead of the license specific to the DRM system.
  • the license format is not recognized by the common interface 72 of the software agent 70, the license format is changed to be compatible with the common interface 72 (act 170).
  • the permissions are extracted and imported in a compatible object or structure used as the portable license. Accordingly, as shown by arrow 130 in Figure 2, the software agent 70 generates a portable (i.e., non-DRM x (e.g., DRM z)) file format and license even thought the software agent 70 received a command (arrow 125) to store the content and license in a DRM x format.
  • non-DRM x e.g., DRM z
  • the portable file 90 and the portable license 120 are then stored in the portable memory device 80, as shown in Figure 1.
  • the acts of generating the portable file format and portable license can be performed by the host device, by the portable memory device, or by some other device.
  • this portable file format and portable license 120 to provide cross- DRM compatibility will now be described. Consider, for example, the situation shown in Figure 5 in which the portable memory device 80 is then placed in communication with another host device 175.
  • This host device 175 comprises a host application 180 operating with a DRM system (DRM y) that is both different from the DRM system of the host application 60 (DRM x) that stored the content 100 on the portable memory device 80 as well as different from the portable DRM system (DRM z).
  • This host device 175 also comprises a software agent 185, which, as shown in Figure 6 comprises a common interface 186 and a host-customized layer 187.
  • the common interface 186 of this software agent 185 is the same as the common interface 72 of the other software agent 70.
  • the host-customized layer 187 of this software agent 186 is customized for DRM y instead of DRM x.
  • FIG. 7 is a flow chart of a method for allowing content protected by a portable DRM to be accessed by the host application 180 operating with DRM y.
  • the first act in this method is to select content (act 205).
  • Content can be selected in any suitable manner.
  • the host application 180 (or another application) on the host device 175 can present a user with a menu of content options for the user to manually select the content.
  • Many alternatives can be used.
  • the user can type-in the name of the content he wants to select, or the content can be automatically selected for the user (as when the host application 180 automatically selects content based on prior selection choices made by the user).
  • the content 100 is protected with a portable DRM that is recognized by common interface modules of all software agents operating in this cross-DRM environment.
  • the host application 180 issues an "open file" command to the software agent 185 to open the file 90 (act 210).
  • the software agent 185 checks the content to see if it is recognized by the software agent 185 as being protected (act 215).
  • the common interface module 186 reads the header 1 10 to look for the stored information discussed previously.
  • the software agent 185 then sends the appropriate code back to the host application 180, and the host application 180 determines if the returned code states "protected" (act 220).
  • the code can, but does not have to, use the actual phrase "protected.” That is, another phrase (or character or, more generally, data) can be used in place of the word "protected.") If the returned code does not state "protected," the host application 180 reads the file 90 (i.e., accesses the content 100) as normal (act 258) and then closes the file 90 (act 260).
  • the host application 180 sends a "get license” command (see arrow 135 in Figure 6) to the software agent 185 (act 225).
  • the software agent 185 acquires the portable license 120 (see arrow 140 in Figure 6), checks the permissions in the portable license 120, and then generates a license that is compatible with the DRM system of the host application 180 (i.e., DRM y) (see arrow 146 in Figure 6).
  • the common interface module 186 in the software agent 185 is able to read the portable license 120.
  • the host- customized layer 187 knows the format needed for the host application's DRM system (DRM y) and works with the common interface 186 to generate a license supported by DRM y from the portable license 120, even though the portable license 120 is supported by a different DRM system (e.g., DRM z). The generated license is then provided to the host application 180.
  • DRM y DRM system
  • DRM z DRM system
  • the generated license can have the same or different permissions as the permissions in the portable license 120.
  • the generated license can have all or some of the permissions that are in the portable license 120 (e.g., play five times, no ring tones, etc.) as well as additional permissions such as cannot move, cannot copy, or play only once.
  • the restrictions of "cannot move” and “cannot copy” may be preferred because if the file were moved with the generated license, there may be an incompatibility issue with other host applications.
  • the permissions in the generated license do not necessarily exactly match the permissions in the portable license.
  • the license returned the license is checked to see if there is permission to access the content (act 230).
  • the file 90 is opened in a secure manner (act 235), and the file 90 is read in a secure manner (act 240) (i.e., the content 100 is streamed in a secure manner without DRM specifics).
  • the file is then closed (act 245).
  • FIG 8 is a flow chart showing more detail of the check license act (act 230).
  • the host application 180 receives the requested license (act 1000).
  • the host application 180 then extracts the permissions (act 1010) and parses the permissions it needs based on the requested access (act 1020).
  • the requested access is then validated using the parsed permissions (act 1030).
  • the software agent 70 can provide the license formatted according to the host DRM prior to act 1000.
  • the host application 70 would then be charged with the task of extracting the permissions from the license (act 1010).
  • the software agent 70 can provide the parsed permissions.
  • a "subsystem" can perform act 228.
  • the subsystem can be on the host device, on the portable memory device, on another device (e.g., in a network), or distributed among one or more of these devices.
  • the subsystem can be a DRM agent in the software agent that connects to the portable memory device, reads the license from the portable memory device, checks the permissions, and then provides the license to the host application.
  • the portable memory device can comprise a processor that executes its own DRM agent.
  • the software agent can ask the DRM agent running on the portable memory device if the host application is allowed to access the content.
  • the DRM agent would then internally fetch the license, check the permissions, and provide the appropriate license to the software agent.
  • the request to store content protected by a first DRM system can be issued by a first computing platform (e.g., a host device), and the portable license and/or portable file format can be generated by a second computing platform (e.g., a portable memory device connected to the host device or a server in wired or wireless communication with the host device).
  • a portable memory device is not necessarily needed to provide content and/or a license to the host device.
  • content and/or a license can be downloaded from a server to the host device, can be wirelessly transmitted to the host device from another host device, or can be "sideloaded” from a PC (e.g., downloaded onto a PC and then moved to the portable memory device).
  • the phrase “wirelessly transmitted” includes “wirelessly accessed.”
  • a portable memory device is not necessarily needed to practice these embodiments and should not be read into the claims unless explicitly recited therein.
  • the license was shown as being stored on the same memory device as the protected content, it should be understood that the license can be stored in any suitable location and not necessarily on the same memory device as the content.
  • some of the acts described herein can be performed in a different order.
  • the act of generating a portable license can be performed before or after the act of generating a portable file format. Accordingly, the acts described in the specification and recited in the claims should not be read as requiring a specific order unless explicitly mentioned.
  • certain acts were described herein as being performed by the software agent, host application, host, or subsystem, it should be noted that these acts can be performed by different entities named or unnamed herein.
  • an environment can be designed such that some or all of the acts performed in the examples by the software agent are instead performed by the host application.
  • the host and/or portable memory devices can have other components that perform some or all of the acts.
  • the host or the portable memory device can have a DRM module that checks permissions and updates the license. Accordingly, performance of the acts described herein can be distributed in any suitable fashion. Further, while these embodiments can be implemented in any suitable environment, it is presently preferred that these embodiments be implemented on a TrustedFlashTM platform by SanDisk Corporation.
  • a computer-readable storage media stores computer- readable operational instructions (i.e., computer-readable program code) to perform the acts involved in these embodiments.
  • Examples of computer-readable storage media include, but are not limited to, a solid-state storage device, an optical storage device (e.g., a CD or DVD), and a magnetic storage device (e.g., a hard drive).
  • the phrase "computer-readable storage media” is intended to cover either a single storage medium or a plurality of storage media in one or more devices. Accordingly, "computer-readable storage media" can be located in the host device or the portable memory device or both, for example.
  • the portable memory device can contain computer- readable storage media that carries the operational instructions (i.e., computer-executable code) to implement the software agent. These instructions can be provided to the host device when the portable memory device is put into communication with the host device. These instructions are then stored in computer-readable storage media of the host device. In this way, the software agent can be placed on a host device in a plug-and-play fashion. In another embodiment, the software agent is pre-loaded onto the host device, so the computer-readable storage media in the host device would carry the operational instructions to implement the software agent when sold to the end user.
  • the operational instructions i.e., computer-executable code
  • the operational instructions can be executed by one or more processors in the host device, portable memory device, or some other device (e.g., a computer in the network). Further, as mentioned above, the performance of the acts can be distributed. For example, a processor in the portable memory device can execute some of the operational instructions (stored in the computer-readable storage media in the portable memory device or the host), while the processor in the host device can execute other ones of the operational instructions (stored in the computer-readable storage device in the portable memory device or the host). Additionally, instead of being stored in computer-readable media and executed by a processor(s), some or all of the operational instructions can be implemented in hardware.
  • circuitry will be used herein to cover a purely hardware implementation, a purely software implementation, and/or an implementation that uses both hardware and software. Accordingly, “circuitry” can take the form of a processor and computer-readable program code that is stored in a computer-readable medium and is executable by the processor. “Circuitry” can also take the form of an application specific integrated circuit (ASIC), a programmable logic controller, an embedded microcontroller, and a single-board computer. Accordingly, the term “circuitry” should not be limited to any particular type of implementation, described herein or otherwise. Further, “circuitry” should not be limited to performing the functions described herein. For example, when circuitry takes the form of a processor executing firmware, it should be understood that the processor can perform functions in addition to the ones described above.
  • ASIC application specific integrated circuit

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Multimedia (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Storage Device Security (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un procédé, un système ainsi que des instructions de fonctionnement de mise en mémoire de supports lisibles par ordinateur destinés à permettre l'accès par un second système de gestion numérique des droits (DRM) au contenu protégé par un premier système (DRM). Dans une forme de réalisation, une demande est émise à partir d'une application hôte en vue d'obtenir une licence de son contenu protégé par un premier système DRM, le premier système DRM étant différent du système DRM de l'application hôte. Une licence fonctionnant sous le système DRM de l'application hôte est alors créée à partir d'une licence fonctionnant sous le premier système DRM. Dans un autre mode de réalisation, une demande de stockage de contenu protégé est transmise au premier système DRM. En réponse à cette demande, une licence portative du contenu est créée à partir d'une licence fonctionnant sous le premier système DRM. Alternativement ou en plus, un format de fichier portatif du contenu est créé à partir d'un format de fichier fonctionnant sous le premier système DRM. La demande peut être émise par une première plate-forme informatique, et la licence portative et/ou le format de fichier peut être créé par une seconde plate-forme informatique. D'autres formes de réalisation sont incluses, chacune d'entre elle pouvant être utilisée seule ou en combinaison.
PCT/US2007/023615 2006-11-14 2007-11-09 Procédé et système destinés à permettre l'accès du contenu d'un second système de gestion numérique des droits (drm) dans un premier système drm qui est protégé Ceased WO2008069887A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US11/600,005 2006-11-14
US11/599,991 US20080114692A1 (en) 2006-11-14 2006-11-14 System for allowing content protected by a first DRM system to be accessed by a second DRM system
US11/599,991 2006-11-14
US11/600,005 US20080114693A1 (en) 2006-11-14 2006-11-14 Method for allowing content protected by a first DRM system to be accessed by a second DRM system

Publications (3)

Publication Number Publication Date
WO2008069887A2 true WO2008069887A2 (fr) 2008-06-12
WO2008069887A3 WO2008069887A3 (fr) 2008-07-31
WO2008069887B1 WO2008069887B1 (fr) 2008-09-18

Family

ID=39382015

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/023615 Ceased WO2008069887A2 (fr) 2006-11-14 2007-11-09 Procédé et système destinés à permettre l'accès du contenu d'un second système de gestion numérique des droits (drm) dans un premier système drm qui est protégé

Country Status (2)

Country Link
TW (1) TW200834440A (fr)
WO (1) WO2008069887A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011031648A1 (fr) * 2009-09-08 2011-03-17 Apple Inc. Gestion de partage de contenu multimédia entre un ordinateur serveur et des ordinateurs clients sur un réseau informatique

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI381312B (zh) * 2008-08-27 2013-01-01 Condel Internat Technologies Inc 在不同作業系統平台之間可交互操作之數位權利管理程式的方法與系統

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100365535C (zh) * 1995-02-13 2008-01-30 英特特拉斯特技术公司 用于安全交易管理和电子权利保护的系统和方法
US20030126086A1 (en) * 2001-12-31 2003-07-03 General Instrument Corporation Methods and apparatus for digital rights management
EP1771966A1 (fr) * 2004-07-29 2007-04-11 Samsung Electronics Co., Ltd. Procede de transmission et de reproduction de contenu traite par divers systemes de drm

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011031648A1 (fr) * 2009-09-08 2011-03-17 Apple Inc. Gestion de partage de contenu multimédia entre un ordinateur serveur et des ordinateurs clients sur un réseau informatique

Also Published As

Publication number Publication date
WO2008069887B1 (fr) 2008-09-18
TW200834440A (en) 2008-08-16
WO2008069887A3 (fr) 2008-07-31

Similar Documents

Publication Publication Date Title
US8601470B2 (en) Symbiotic smart peripherals
US8327454B2 (en) Method for allowing multiple users to access preview content
US20080114693A1 (en) Method for allowing content protected by a first DRM system to be accessed by a second DRM system
US20080114880A1 (en) System for connecting to a network location associated with content
US8561130B2 (en) Personal license server and methods for use thereof
EP2095244B1 (fr) Gestion de droits numériques interopérables
JP4245374B2 (ja) 着脱式デバイスおよび制御回路
US20090094597A1 (en) Portable firmware device
WO2012172743A1 (fr) Dispositif de traitement d'informations, procédé de traitement d'informations, programme et circuit intégré
WO2009038928A2 (fr) Accès à des services hébergés par un dispositif à partir d'un environnement de script et d'autres environnements de programmation
US20140222875A1 (en) System having an apparatus that uses a resource on an external device
JP4768741B2 (ja) 少なくとも１つの保護されたコンテンツアイテムの使用権限を有効にする方法、装置、及びコンピュータプログラム製品
US20080114692A1 (en) System for allowing content protected by a first DRM system to be accessed by a second DRM system
US8201188B2 (en) Device-hosted services over media transfer protocol
EP1377980A2 (fr) Appareil d'enregistrement / reproduction de contenus, et support d'enregistrement contenant un programme d'enregistrement / reproduction de contenus
KR20110013188A (ko) 분리형 ｒｏ 관리를 위한 호스트 단말 및 저장 장치, 그의 분리형 ｒｏ 관리 방법 그리고, 이를 수행하는 프로그램을 기록한 기록매체
CN1517976B (zh) 内容处理设备和内容处理程序
TW201032048A (en) Network adapter, method & computer program product
JP2010514037A (ja) 分散環境でのデータの管理方法および機器
US20080114772A1 (en) Method for connecting to a network location associated with content
JP2012515372A (ja) 回路カードデータ保護
WO2004055651A1 (fr) Langage numerique simple de gestion de droits
CN102112976B (zh) 取决于与其连接的主机装置内的平台提供自适应服务的电子设备
TW200834440A (en) Method and system for allowing content protected by a first DRM system to be accessed by a second DRM system
WO2008060412A2 (fr) Procédé et système pour une connexion à un emplacement de réseau associé à un contenu

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07870859

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07870859

Country of ref document: EP

Kind code of ref document: A2