EP1372055A2 - Publishing content in connection with digital rights management (DRM) architecture - Google Patents
Publishing content in connection with digital rights management (DRM) architecture Download PDFInfo
- Publication number
- EP1372055A2 EP1372055A2 EP03013284A EP03013284A EP1372055A2 EP 1372055 A2 EP1372055 A2 EP 1372055A2 EP 03013284 A EP03013284 A EP 03013284A EP 03013284 A EP03013284 A EP 03013284A EP 1372055 A2 EP1372055 A2 EP 1372055A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- content
- license
- packager
- provisioning
- user
- 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.)
- Granted
Links
Images
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
- the present invention relates to an architecture for enforcing rights in digital content. More specifically, the present invention relates to such an enforcement architecture that allows access to encrypted digital content only in accordance with parameters specified by license rights acquired by a user of the digital content. Even more specifically, the present invention relates to such an architecture that is particularly useful in connection with publishing content.
- digital rights management (DRM) and enforcement system is highly desirable in connection with digital content 12 such as digital audio, digital video, digital text, digital data, digital multimedia, etc., where such digital content 12 is to be distributed to users.
- digital content 12 such as digital audio, digital video, digital text, digital data, digital multimedia, etc.
- DRM digital rights management
- enforcement system is highly desirable in connection with digital content 12 such as digital audio, digital video, digital text, digital data, digital multimedia, etc., where such digital content 12 is to be distributed to users.
- digital content 12 such as digital audio, digital video, digital text, digital data, digital multimedia, etc.
- a content owner distributing such digital content 12 wishes to restrict what the user can do with such distributed digital content 12. For example, the content owner may wish to restrict the user from copying and re-distributing such content 12 to a second user, or may wish to allow distributed digital content 12 to be played only a limited number of times, only for a certain total time, only on a certain type of machine, only on a certain type of media player, only by a certain type of user, etc.
- a DRM system 10 allows the controlled rendering or playing of arbitrary forms of digital content 12, where such control is flexible and definable by the content owner of such digital content.
- content 12 is distributed to the user in the form of a package 13 by way of any appropriate distribution channel.
- the digital content package 13 as distributed may include the digital content 12 encrypted with a symmetric encryption / decryption key (KD), (i.e., (KD(CONTENT))), as well as other information identifying the content, how to acquire a license for such content, etc.
- KD symmetric encryption / decryption key
- the trust-based DRM system 10 allows an owner of digital content 12 to specify license rules that must be satisfied before such digital content 12 is allowed to be rendered on a user's computing device 14.
- license rules can include the aforementioned temporal requirement, and may be embodied within a digital license 16 that the user / user's computing device 14 (hereinafter, such terms are interchangeable unless circumstances require otherwise) must obtain from the content owner or an agent thereof.
- license 16 also includes the decryption key (KD) for decrypting the digital content, perhaps encrypted according to a key decryptable by the user's computing device.
- KD decryption key
- the content owner for a piece. of digital content 12 must trust that the users computing device 14 will abide by the rules and requirements specified by such content owner in the license 16, i.e. that the digital content 12 will not be rendered unless the rules and requirements within the license 16 are satisfied.
- the user's computing device 14 is provided with a trusted component or mechanism 18 that will not render the digital content 12 except according to the license rules embodied in the license16 associated with the digital content 12 and obtained by the user.
- the trusted component 18 typically has a license evaluator 20 that determines whether the license 16 is valid, reviews the license rules and requirements in such valid license 16, and determines based on the reviewed license rules and requirements whether the requesting user has the right to render the requested digital content 12 in the manner sought, among other things.
- the license evaluator 20 is trusted in the DRM system 10 to carry out the wishes of the owner of the digital content 12 according to the rules and requirements in the license 16, and the user should not be able to easily alter such trusted element for any purpose, nefarious or otherwise.
- the rules and requirements in the license 16 can specify whether the user has rights to render the digital content 12 based on any of several factors, including who the user is, where the user is located, what type of computing device the user is using, what rendering application is calling the DRM system, the date, the time, etc.
- the rules and requirements of the license 16 may limit the license 16 to a predetermined number of plays, or pre-determined play time, for example.
- the rules and requirements may be specified in the license 16 according to any appropriate language and syntax.
- the language may simply specify attributes and values that must be satisfied (DATE must be later than X, e.g.), or may require the performance of functions according to a specified script (IF DATE greater than X, THEN DO ..., e.g.).
- the digital content 12 can then be rendered.
- the decryption key (KD) is obtained from the license 12 and is applied to (KD(CONTENT)) from the content package 13 to result in the actual content 12, and the actual content 12 is then in fact rendered.
- content 12 is packaged for use by a user by encrypting such content 12 and associating a license 16 having a set of rules with the content 12, whereby the content 12 can be rendered only in accordance with the rules in the license 16. Because the content 12 requires the license 16 for access thereto, then, the content 12 may be freely distributed. Accordingly, to package content 12 for publishing in accordance with the DRM system 10, a packager and a licensor must exchange information such that the packager can package DRM content 12 for which the licensor can issue a corresponding license 16.
- a packager packages digital content for a user and a licensor issues a digital license to the user for the content such that the user renders the content only in accordance with the license.
- the licensor upon receiving a provisioning request from the packager generates a Secret to be shared with the packager.
- the shared Secret allows the packager and the licensor to calculate a content key (KD) for the content.
- the licensor generates a random content key (KD-PROV), and encrypts the Secret according to (KD-PROV) to form (KD-PROV(Secret)).
- KD-PROV random content key
- the licensor signs a public key of the packager (PU-PA1) with a private key of the licensor (PR-Ll) to certify same ((PU-PA1) S (PR-Ll)), and sends (KD-PROV(Secret)), (PU-PA1) S (PR-Ll), and any associated certificate chain to the packager.
- the packager as provisioned has provisioning content from the licensor including (KD-PROV(Secret)), and a provisioning license from the licensor including (KD-PROV) encrypted according to a public key of the packager (PU-PA2) ((PU-PA2(KD-PROV))).
- the packager selects the provisioning license and provisioning content from the licensor, obtains (PU-PA2(KD-PROV)) from the provisioning license, applies a corresponding private key of the packager (PR-PA2) to (PU-PA2(KD-PROV)) to result in (KD-PROV), obtains (KD-PROV(Secret)) from the provisioning content, and applies (KD-PROV) to (KD-PROV(Secret)) to result in the shared Secret.
- the packager then generates a random content ID for the content, calculates a content key (KD) based on the random content ID and the Secret, and encrypts the content according to (KD) ((KD(Content))). Thereafter, the packager obtains a provisioning content ID having an identifier of the licensor from one of the provisioning license and the provisioning content, appends to (KD(Content)) the random content ID, a public key of the packager (PU-PA1), and the identifier of the licensor to form the packaged content, and distributes the packaged content to the user.
- KD content key
- the packaged content as possessed by the user includes (KD(Content)), the content lD, and (PU-PA1).
- the licensor receives a request including the content ID, (PU-PA1), and a public key associated with the user (PU-US) that is to be employed to bind the license to the user.
- the licensor obtains based on (PU-PA1 ) stored provisioning information regarding the packager including the shared Secret, calculates (KD) based on the content lD received with the request and the obtained Secret, and encrypts (KD) according to (PU-US) as received with the request ((PU-US(KD))).
- the licensor then appends to (PU-US(KD)) the content lD to form the license, and sends the license to the user.
- Fig. 1 and the following discussion are intended to provide a brief general description of a suitable computing environment in which the present invention and/or portions thereof may be implemented.
- the invention is described in the general context of computer-executable instructions, such as program modules, being executed by a computer, such as a client workstation or a server.
- program modules include routines, programs, objects, components, data structures and the like that perform particular tasks or implement particular abstract data types.
- the invention and/or portions thereof may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers and the like.
- the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote memory storage devices.
- an exemplary general purpose computing system includes a conventional personal computer 120 or the like, including a processing unit 121, a system memory 122, and a system bus 123 that couples various system components including the system memory to the processing unit 121.
- the system bus 123 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
- the system memory includes read-only memory (ROM) 124 and random access memory (RAM) 125.
- ROM read-only memory
- RAM random access memory
- the personal computer 120 may further include a hard disk drive 127 for reading from and writing to a hard disk (not shown), a magnetic disk drive 128 for reading from or writing to a removable magnetic disk 129, and an optical disk drive 130 for reading from or writing to a removable optical disk 131 such as a CD-ROM or other optical media.
- the hard disk drive 127, magnetic disk drive 128, and optical disk drive 130 are connected to the system bus 123 by a hard disk drive interface 132, a magnetic disk drive interface 133, and an optical drive interface 134, respectively.
- the drives and their associated computer-readable media provide non-volatile storage of computer readable instructions, data structures, program modules and other data for the personal computer 20.
- exemplary environment described herein employs a hard disk, a removable magnetic disk 129, and a removable optical disk 131
- other types of computer readable media which can store data that is accessible by a computer may also be used in the exemplary operating environment.
- Such other types of media include a magnetic cassette, a flash memory card, a digital video disk, a Bernoulli cartridge, a random access memory (RAM), a read-only memory (ROM), and the like.
- a number of program modules may be stored on the hard disk, magnetic disk 129, optical disk 131, ROM 124 or RAM 125, including an operating system 135, one or more application programs 136, other program modules 137 and program data 138.
- a user may enter commands and information into the personal computer 120 through input devices such as a keyboard 140 and pointing device 142.
- Other input devices may include a microphone, joystick, game pad, satellite disk, scanner, or the like.
- serial port interface 146 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port, or universal serial bus (USB).
- a monitor 147 or other type of display device is also connected to the system bus 123 via an interface, such as a video adapter 148.
- a personal computer typically includes other peripheral output devices (not shown), such as speakers and printers.
- the exemplary system of Fig. 2 also includes a host adapter 155, a Small Computer System Interface (SCSI) bus 156, and an external storage device 162 connected to the SCSI bus 156.
- SCSI Small Computer System Interface
- the personal computer 120 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 149.
- the remote computer 149 may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the personal computer 120, although only a memory storage device 150 has been illustrated in Fig. 2.
- the logical connections depicted in Fig. 2 include a local area network (LAN) 151 and a wide area network (WAN) 152.
- LAN local area network
- WAN wide area network
- the personal computer 120 When used in a LAN networking environment, the personal computer 120 is connected to the LAN 151 through a network interface or adapter 153. When used in a WAN networking environment, the personal computer 120 typically includes a modem 154 or other means for establishing communications over the wide area network 152, such as the Internet.
- the modem 154 which may be internal or external, is connected to the system bus 123 via the serial port interface 146.
- program modules depicted relative to the personal computer 120, or portions thereof may be stored in the remote memory storage device. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
- the DRM architecture 10 controls access to digital content 12 by encrypting and packaging the content 12 and allowing access to the content 12 only in accordance with a set of rules in a corresponding license 16.
- the DRM architecture 10 as set forth above is somewhat involved. Especially in the area of publishing, where an individual wishes to publish content 12 within the framework of the DRM architecture 10, such architecture 10 may be somewhat modified as set forth below to enable such personal packaging and publishing in a simplified and economical manner.
- any packager / publisher may employ the architecture 10 set forth below without departing from the spirit and scope of the present invention.
- publishing of content 12 and consumption of the published content 12 in connection with the DRM architecture 10 requires: (1) that a licensor 'provision' a publisher or the like to package content 12 for publishing; (2) that the packager in fact packages the content 12 for publishing; and (3) that the packaged content 13 as published be rendered by a user at a computing device 14 based on a license 16 obtained from the licensor.
- a licensor 'provision' a publisher or the like
- a packager 60 and a licensor 62 prior to actually publishing content 12, a packager 60 and a licensor 62 must exchange information such that the packager 60 / publisher can publish content 12 for consumption by a user 64 at a computing device 14, and such that the licensor 62 can issue a license 16 to the user 64 for rendering the content 12. Put another way, the licensor 62 must 'provision' the packager.
- the packager 60 of the content 12 may be the publisher of such content 12 or may be separate from such publisher.
- provisioning is based on a Secret that is shared between the packager 60 and licensor 62 and a public private key pair associated with the packager 60 (PU-PA1, PR-PA1).
- the key pair (PU-PA1, PR-PA1) is employed by the packager 60 to identify itself, to encrypt and decrypt, and to create a signature.
- the shared Secret between the licensor and the packager allows each to calculate a content key (KD) for a piece of content 12. The calculation can be based on any algorithm agreed upon by both the licensor and the packager without departing from the spirit and scope of the present invention.
- the content key (KD) fora piece of content 12 having a content ID is obtained from a hash of the content ID and the Secret, such as for example a hash based on the SHA algorithm:
- Content Key (KD) SHA( Content ID, Secret )
- provisioning is performed as follows.
- the packager 60 requests that the licensor 62 provision such packager 60 (step 1401).
- the request may take any particular form without departing from the spirit and scope of the present invention, but at a minimum includes an identifying certificate 66 and an associated certificate chain 68.
- the identifying certificate 66 in particular includes a public key associated with the packager 60 (PU-PA2) that is to be employed to bind a license 16 to the packager 60, where the packager 60 also has a corresponding private key (PR-PA2).
- PU-PA2 public key associated with the packager 60
- PR-PA2 private key
- (PU-PA2, PR-PA2) may be different from (PU-PA1, PR-PA1) or the same as (PU-PA1, PR-PA1). Ideally, however, the pairs of keys should be distinct. In particular, and as is conventional, (PR-PA2) should be accessible only by the trusted component 18, and should never be made available externally.
- the request can include proposed business rules 70.
- the business rules 70 are the conditions under which a user 64 is to be granted a license 16 for content 12 packaged by the packager 60.
- Such rules 70 may for example specify that the content be rendered only a set number of times, a set number of days, etc.
- the licensor 62 typically has the discretion to agree to the business rules 70 or to require modifications thereto.
- the licensor 62 may first perform any transaction with the packager 60 that the licensor 62 deems appropriate (step 1403). For example, the licensor 62 could require the packager 60 to start a subscription, pay a fee, etc. The licensor 62 could also authenticate the identity of the packager 60 through any available mechanism.
- the licensor 62 begins provisioning the packager 60 by generating items specific to such packager 60 (step 1405). Specifically, the licensor 62 generates the aforementioned shared Secret. In addition, it may be the case that the licensor 62 generates the key pair (PU-PA1, PR-PA1) for the packager 60 at this point. If so, the licensor 62 signs (PU-PA 1) with a private key (PR-LI) to certify same (i.e., (PU-PA1) S (PR-LI)).
- the packager 60 may object to the licensor 62 knowing (PR-PA1). If so, the Packager obtains the key pair (PU-PA1, PR-PA1)from another source, sends (PU-PA1)to the licensor as part of the request at step 1401, and the licensor 62 signs the sent (PU-PA1) with a private key (PR-LI) to certify same (i.e., (PU-PA1) S (PR-LI)).
- PR-LI private key
- the generated shared Secret, (PU-PA1) S (PR-LI), an associated certificate chain for (PU-PA1) S (PR-LI), and (PR-PA1) if generated by the licensor 62 are to be sent to the packager 60 by such licensor 62, and at least some of such items must be received and retained by the packager 60 in a secure manner. Accordingly, in one embodiment of the present invention, such items are sent in the form of a piece of DRM content 12, which in this case is provisioning content 12.
- provisioning content 12 is a special form of content 12 in that such provisioning content 12 is in effect rendered only to divulge the items therein.
- the licensor generates a random content key (KD-PROV) for the provisioning content 12 (step 1407), and then encrypts one or more of such items (Secret, (PU-PA1) S (PR-Ll), certificate chain, and (PR-PA1 )) according to (KD-PROV) to form such provisioning content 12 (step 1409).
- KD-PROV random content key
- all of such items may be encrypted to form the provisioning content 12, or only select ones of such items may be so encrypted. In the latter case, and for example, only Secret and (PR-PA1) are so encrypted, and (PU-PA1) S (PR-Ll)and the certificate chain are appended to the encrypted provisioning content 12 as a header or the like.
- a corresponding provisioning license 16 is required for the provisioning content 12 to be 'rendered' by the packager 60 and a trusted component 18 thereof. Accordingly, the licensor generates such a provisioning license by retrieving (PU-PA2) from the identifying certificate 66 that accompanied the request in step 1401 (step 1411), and encrypting (KD-PROV) with (PU-PA2) to form (PU-PA2(KD-PROV)) (step 1413).
- the provisioning license 16 and the provisioning content 12 both should have a content ID. Accordingly, the licensor 62 generates such a content ID and appends same to both the provisioning license 16 and the provisioning content 12.
- Such content lD may be any appropriate content lD. without departing from the spirit and scope of the present invention.
- the content ID may be an identifier of the licensor 62, such as a URL thereof.
- each set should have a unique content ID. Accordingly, and in such a case, the content lD may also be based on the URL of the licensor 62 and additional information.
- the licensor 62 may wish to constrain the ability of the packager 60 to package content 12. For example, the licensor 60 may wish to have the packager 60 pay a fee each time such content 12 is packaged thereby.
- the provisioning license 16 is a rich license that can include an abundant set of usage rules that apply to the packager 62. Accordingly, and in such a case, the licensor specifies particular usage rules for using the provisioning license 16 (step 1415), and appends same to the provisioning license 16 (step 1417).
- the licensor 62 maintains a record of at least some of the information incumbent in the provisioning license 16 and the provisioning content 12.
- provisioning information is stored in a database or the like (step 1419), and is used when constructing a license 16 for a user 64 based on content 12 packaged by the packager 60 in accordance with the provisioning license 16 and the provisioning content 12, as will be disclosed in more detail below.
- the licensor 62 sends the provisioning license 16 and the provisioning content 12 to the packager 60 and the packager 60 appropriately stores same (step 1421) in a license store and content store of a trusted component 18 thereof, respectively.
- a provisioning license 16 and piece of provisioning content 12 are shown in Figs. 5 and 6, respectively.
- a packager 60 can package content 12 as packaged content 13 and distribute same, as follows. Note that packaging may be performed in response to a request for the content 12 from a user 64, or may be performed to have content 12 available should a user 64 request same.
- the packager 60 selects a licensor 62 to issue licenses 16 for the to-be-packaged content 12 (step 1701).
- a licensor 62 is available for use by the packager 60, and the packager 60 has at least one set of a provisioning license 16 and provisioning content 12 for each available licensor 62.
- the packager binds to the selected provisioning license 16. That is, the packager 60 has a trusted component 18 operating on a computing device 14 of such packager 60, and the packager 60 requests that the trusted component 18 make available the provisioning content key (KD-PROV) from such selected provisioning license 16 (step 1703). Accordingly, the trusted component 18 reviews any usage rules in the selected provisioning license 16 and makes a determination based on such usage rules and any other rules on whether the provisioning content key(KD-PROV) can be made available (step 1705).
- KD-PROV provisioning content key
- the trusted component 18 in fact obtains such (KD-PROV) by obtaining (PU-PA2(KD-PROV)) from the license 16 (step 1707), and applying (PR-PA2) thereto to result in (KD-PROV) (step 1709).
- (PR-PA2) may be the private key of the black box 30 of the trusted component 18 (PR-BB), or may be the private key of another key pair.
- Such another key pair may for example be a key pair owned by the packager 60 and available to the trusted component 18 and the black box 30 thereof.
- the packager 60 / trusted component 18 decrypts the encrypted contents of the selected provisioning content 12 corresponding to the selected provisioning license 16 (step 1711). Accordingly, the content lD including the URL of the licensor 62, the Secret, (PU-PA1) S (PR-Ll), the certificate chain, and (PR-PA1) are available, and (PU-PA1) is made available by traversing the certificate chain to obtain (PU-Ll) and applying same to (PU-PA1) S (PR-Ll) to verify (PU-PA1).
- the packager 60 already knows (PU-PA1) and (PR-PA1), the Secret, (PU-PA1) S (PR Ll) and the certificate chain are available from the provisioning content, the certificate chain is traversed to obtain (PU-Ll) and verify (PU-PA1) S (PR-Ll)
- the packager 60 Based on having the content ID including the URL of the licensor 62, the Secret, (PU-PA1), and (PR-PA1), the packager 60 then can package the content 12.
- the content ID could be random or non-random, and in fact can be an identifier such as for example an ISBN number for a book, a docket number for a document, etc.
- the packaged content 13 includes the encrypted content 12 (KD(Cohtent)) and a rights label having meta-data, relevant to the encrypted content 12.
- the packager 60 packages (KD(Content)) with a rights label 72 including the content lD,(PU-PA1), the URL of the licensor 62, and usage rules specifying how the user 64 can render the content 12 as packaged (step 1719).
- the rights label 72 or at least a portion thereof should be signed by (PR-PA1) to prevent unauthorized tampering therewith.
- the usage rules in the rights label 72 can be in addition to or instead of the business rules 70 included with the request in step 1401, above.
- Such packaged content 13 may then be distributed to a user 64 (step 1721). As should be appreciated, the packaged content 13 upon being distributed does not as yet have any license 16 corresponding thereto. Such packaged content 12 is shown in Fig. 8.
- a packager 60 can decrypt any self-packaged content 12 using only the provisioning license 16, the provisioning content 12, and the content ID in a manner akin to that set forth in Fig. 7 to calculate the content key (KD) for the content 12.
- KD content key
- the packager can discard the unencrypted content 12 after being packaged without impacting the packager's ability to access the packaged content 13.
- the packager 60 need not obtain a license 16 from the licensor 62 for the content 12.
- the packager 60 wants to access the self-packaged content 12, for example to edit the content 12, such packager 60 can do so by locating the provisioning license for the licensor URL specified in the packaged content 13 (Fig 8), obtaining the shared secret and computing (KD) (Fig. 7), and decrypting the packaged content 13 using (KD).
- the provisioning content key (KD-PROV) is divulged to the packager 60.
- the trusted component 18 on the computing device 14 of the packager 60 takes the provisioning license 16 and the provisioning content 12 as input, extracts (KD-PROV), employs same to extract the shared Secret from the provisioning content 12, and then packages the content 12, all without allowing the packager 60 or any other individual to see (KD-PROV) or any other secrets or keys employed.
- the user 64 When a user 64 after obtaining the packaged content 13 attempts to render same, the user 64 is directed to obtain a valid license from the licensor 62 in a manner akin to that described above.
- the license 16 for the packaged content 13 is obtained from the licensor 62 in the following manner.
- the user 64 at a computing device 14 having a trusted component 18 thereon retrieves the rights label 72 packaged with the encrypted content 12 (step 1901), and obtains from the rights label 72 the URL of the licensor 62 (step 1903).
- the user 64 then sends an identifying certificate 74, an associated certificate chain 76, and the rights label 72 to the licensor 62 at the obtained URL thereof (step 1905) to request a license 16 for the content 12.
- the identifying certificate 74 includes a public key associated with the user 64 (PU-US) that is to be employed to bind the license 16 to the user 64, where the user 64 also has a corresponding private key (PR-US).
- (PU-US, PR-US) may be the public and private keys of the black box 30 of the trusted component 18 of the computing device 14 of the user 64 (PU-BB, PR-BB), or may be the public and private keys of another key pair.
- Such another key pair may for example be a key pair owned by the user 64 and available to the trusted component 18 and the black box 30 thereof.
- the licensor 62 upon receiving the request from the user 64 including the identifying certificate 74, the associated certificate chain 76, and the rights label 72 obtains (PU-PA1) from the rights label 72 and based thereon verifies the signature (S(PR-PA1)) of such rights label 72 with the obtained (PU-PA1 ) (step 1907). Assuming the signature verifies, the licensor 62 then obtains based on (PU-PA1) information regarding the packager 60 as was stored as provisioning information at step 1419. In particular, the licensor 62 obtains the shared Secret from such provisioning information (step 1909).
- the licensor 62 may also perform any transaction with the user 64 that the licensor 62 deems appropriate (step 1911). For example, the licensor 62 could require the user 64 to start a subscription, pay a fee, etc. The licensor 62 could also authenticate the identity of the user 64 through any available mechanism. As may be appreciated, the transaction may be based in part on the usage rules in the rights label 72, the büsiness rules 70 included with the request in step 1401, above, or based on other rules.
- the Licensor 62 then issues a license 16 corresponding to the content 12 to the user 64.
- the licensor 62 places in the license 16 the content ID for the content 12 as obtained from the rights label 72 and the usage rules for using the content 16 as obtained from the rights label 72 (step 1921).
- the license 16 as constructed or at least a portion thereof may be signed by a private key of the licensor 62 (S (PR-LI)), and the license may be provided with the corresponding (PU-Ll) to verify same.
- the licensor 62 then sends the license 16 to the user 64 and the user 64 appropriately stores same (step 1923) in a license store 38 of the trusted component 18 thereof.
- a license 16 is shown in Fig. 10.
- the user 64 can now render the content 12 under the conditions set forth in the license 16.
- the present invention comprises a new and useful method and mechanism by which a licensor 62 can 'provision' a packager 60 to package content 12 for publishing, by which the packager 60 in fact packages the content 12 for publishing, and by which a license 16 for the packaged content 13 is obtained by a user. It be appreciated that changes could be made to the embodiments described above without departing from the inventive concepts thereof, Examples of such changes include the following.
- the present invention although disclosed above in terms of content 12 with rights label 72 could also be implemented in terms of content 12 with a header containing information similar to that disclosed as being in the rights label 72.
- the present invention could also be implemented in terms of content 12 having a license 16 incorporated thereinto.
- the licensor 62 is disclosed herein as both provisioning the packager 60 and issuing a license 16 to the user 64, the present invention could also be implemented with one entity provisioning the packager 60 and another entity issuing the license 16 to the user 64, assuming the license issuing entity has access to the provisioning information created by the provisioning entity.
- provisioning as disclosed herein can be employed for purposes other than for publishing.
- a user can be provisioned to access content 12 already on media such as a portable media.
- the user acquires one or more licenses 16 with symmetric keys that allow mapping into a key table on the portable media.
- Another example is for Enterprise Software License Managers, which are services set up within a corporation or other logical entity that issue software licenses to other devices.
- a root / hub license manager could be provisioned to issue a certain number of software licenses to down-level computers.
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
Description
Claims (30)
- A method in combination with a digital rights management architecture wherein a packager packages digital content for a user and a licensor issues a digital license to the user for the content, the user rendering the content only in accordance with the license, the method for the licensor to provision the packager to package the content for the user such that the licensor can issue the license to the user and comprising:receiving a provisioning request from the packager;generating a Secret to be shared with the packager, the shared Secret allowing each to calculate a content key (KD) for the content;generating a random content key (KD-PROV);encrypting the Secret according to (KD-PROV) to form (KD-PROV(Secret));signing a public key of the packager (PU-PA1) with a private key of the licensor (PR-LI) to certify same ((PU-PA1) S (PR-Ll)), the packager having a corresponding private key (PR-PA1) and the licensor having a corresponding public key (PU-LI); andsending (KD-PROV(Secret)), (PU-PA1) S (PR-LI), and any associated certificate chain to the packager.
- The method of claim 1 further comprising generating (PU-PA1, PR-PA1) for the packager, and encrypting (PR-PA1) according to (KD-PROV) to form (KD-PROV(PR-PA1)), the method comprising sending. (KD-PROV(Secret)), (KD-PROV(PR-PA1)), (PU-PA1) S (PR-LI), and any associated certificate chain to the packager.
- The method of claim 1 comprising receiving a provisioning request from the packager including (PU-PA1).
- The method ofclaim 1 comprising receiving the provisioning request including proposed business rules specifying conditions under which the user is to be granted the license for the content packaged by the packager.
- The method of claim 1 further comprising performing a financial transaction with the packager to provision same.
- The method of claim 1 comprising sending (KD-PROV(Secret)), (PU-PA1 ) S (PR-Ll), and any associated certificate chain to the packager as provisioning content renderable by the packager only in accordance with a corresponding provisioning license.
- The method of claim 6 comprising receiving the provisioning request including a public key associated with the packager (PU-PA2), the packager havinga corresponding private key (PR-PA2), the method further comprising generating the provisioning license by encrypting (KD-PROV) with (PU-PA2) to form (PU-PA2(KD-PROV)), and sending the provisioning license to the packager.
- The method of claim 7 wherein (PU-PA2, PR-PA2) are (PU-PA1, PR-PA1).
- The method of claim 7 wherein (PU-PA2, PR-PA2) are different from (PU-PA1, PR-PA1).
- The method of claim 7 further comprising generating a provisioning content ID and appending same to the provisioning license.
- The method of claim 10 further comprising appending the generated provisioning content ID to the provisioning content.
- The method of claim 10 wherein the provisioning content ID includes an identifier of the licensor,
- The method of claim 7 further comprising specifying usage rules for using the provisioning license and appending same to the provisioning license.
- The method of claim 1 further comprising storing provisioning information including (PU-PA1) and the shared Secret, the stored provisioning information to be employed when constructing the license for the user.
- A method in combination with a digital rights management architecture wherein a packager packages digital content for a user and a licensor issues a digital license to the user for the content, the user rendering the content only in accordance with the license, the packager having provisioning content from the licensor including a shared Secret encrypted according to a random content key (KD-PROV) ((KD-PROV(Secret))); and a provisioning. license from the licensor including (KD-PROV) encrypted according to a public key of the packager (PU-PA2) ((PU-PA2(KD-PROV))), the method for the packager to package the content for the user such that the licensor can issue the license to the user and comprising:selecting the provisioning license and provisioning content from the licensor;obtaining (PU-PA2(KD-PROV)) from the provisioning license;applying a corresponding private key of the packager (PR-PA2) to (PU-PA2(KD-PROV)) to result in (KD-PROV);obtaining (KD-PROV(Secret)) from the provisioning content;applying (KD-PROV) to (KD-PROV(Secret)) to result in the shared Secret;generating a random content ID for the content;calculating a conteritkey (KD) based on the random content ID and the Secret;encrypting the content according to (KD)((KD(Content)));obtaining from one of the provisioning license and the provisioning content a provisioning content lD having an identifier of the licensor;appending to (KD(Content)) the random content ID, a public key of the packager (PU-PA1), and the identifier of the licensor to form the packaged content; anddistributing the packaged content to the user.
- The method of claim 15 wherein the provisioning license further includes usage rules for using the provisioning license, the method further comprising reviewing the usage rules and making a determination based on such usage rules that (KD-PROV) can be made available from the provisioning license.
- The method of claim 15 comprising calculating the content key (KD) based on a hash of the random content ID and the Secret.
- The method of claim 15 wherein the provisioning content includes a signature based on a private key of the licensor (PR-Ll) to certify same (S (PR-LI)), and any associated certificate chain, the method further comprising traversing the certificate chain to obtain (PU-Ll) and applying same to verify S (PR-Ll).
- The method of claim 15 further comprising appending a signature to (KD(Content)), the signature being based on at least one of the random content ID, the public key of the packager (PU-PA1 ), the identifier of the licensor, and any usage rules specifying how the user can render the content as packaged.
- The method of claim 15 wherein (PU-PA2) is (PU-PA1).
- The method of claim 15 wherein (PU-PA2) is different from (PU-PA1).
- The method of claim 15 further comprising appending to (KD(Content)) any usage rules specifying how the user can render the content as packaged to form the content.
- A method in combination with a digital rights management architecture wherein a packager packages digital content for a user and a licensor issues digital license to the user for the content, the user rendering the content only in accordance with the license, the packaged content including the content encrypted according to a content key (KD) ((KD(Content))), a content ID, and a public key of the packager (PU-PA1), the method for the licensor to issue the license to the user and comprising:receiving a request for a license from the user, the request including the content ID, (PU-PAl), and a public key associated with the user (PU-US) that is to be employed to bind the license to the user, the user having a corresponding private key (PR-US);obtaining based on (PU-PA1) stored provisioning information regarding the packager including a Secret shared therewith;calculating (KD) based on the content ID received with the request and the obtained Secret;encrypting (KD) according to (PU-US) as received with the request ((PU-US(KD)));appending to (PU-US(KD)) the content ID to form the license; andsending the license to the user.
- The method of claim 2 comprising calculating the content key (KD) based on a hash of the random content lD and the Secret.
- The method of claim 23 comprising receiving the request further including usage rules specifying how the user can render the content; and further comprising appending to (PU-US(KD)) the usage rules.
- The method of claim 23 comprising receiving (PU-US) in an identifying certificate, and any associated certificate chain.
- The method of claim 23 wherein the packaged content further includes a signature based on a private key of the packager (PR-PA1), corresponding to the public key of the packager (PU-PA1) ((S(PR-PA1))), the method comprising receiving the request further including (S(PR-PA1)) and verifying (S(PR-PA1)) with (PU-PA1).
- The method of claim 23 further comprising performing a financial transaction with the user to license same.
- The method of claim 23 comprising calculating the content key (KD) based on a hash of the random content ID and the Secret.
- The method of claim 23 further comprising appending to (PU-US(KD)) a signature based on a private key of the licensor (S (PR-Ll)), and a corresponding public key of the licensor (PU-LI) to verify same.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/170,791 US7065787B2 (en) | 2002-06-12 | 2002-06-12 | Publishing content in connection with digital rights management (DRM) architecture |
US170791 | 2002-06-12 |
Publications (3)
Publication Number | Publication Date |
---|---|
EP1372055A2 true EP1372055A2 (en) | 2003-12-17 |
EP1372055A3 EP1372055A3 (en) | 2005-10-05 |
EP1372055B1 EP1372055B1 (en) | 2008-12-17 |
Family
ID=27612933
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP03013284A Expired - Lifetime EP1372055B1 (en) | 2002-06-12 | 2003-06-12 | Publishing content in connection with digital rights management (DRM) architecture |
Country Status (6)
Country | Link |
---|---|
US (1) | US7065787B2 (en) |
EP (1) | EP1372055B1 (en) |
JP (1) | JP4467255B2 (en) |
AT (1) | ATE418111T1 (en) |
DE (1) | DE60325298D1 (en) |
NO (1) | NO332658B1 (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1480100A1 (en) * | 2003-05-22 | 2004-11-24 | Copyright Clearance Center, Inc. | Method and apparatus for secure delivery and rights management of digital content |
EP1621955A1 (en) * | 2004-07-30 | 2006-02-01 | Irdeto Access B.V. | Method and device for providing access to encrypted content |
EP1621956A1 (en) * | 2004-07-30 | 2006-02-01 | Irdeto Access B.V. | Method of providing rights data objects |
EP1876550A1 (en) | 2006-07-07 | 2008-01-09 | Swisscom Mobile AG | Method and system for encrypted data transmission |
US7324648B1 (en) | 2003-07-08 | 2008-01-29 | Copyright Clearance Center, Inc. | Method and apparatus for secure key delivery for decrypting bulk digital content files at an unsecure site |
WO2009141784A1 (en) * | 2008-05-23 | 2009-11-26 | Koninklijke Philips Electronics N.V. | Identity-based encryption of data items for secure access thereto |
WO2012149717A1 (en) * | 2011-08-31 | 2012-11-08 | 华为技术有限公司 | License dynamic management method, device and system based on tcm or tpm |
WO2021041676A1 (en) * | 2019-08-27 | 2021-03-04 | Intertrust Technologies Corporation | Multi-party cryptographic systems and methods |
US12316613B2 (en) | 2006-07-07 | 2025-05-27 | Interdigital Ce Patent Holdings, Sas | Process and system for selectable data transmission |
Families Citing this family (60)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7895661B2 (en) * | 2003-04-25 | 2011-02-22 | Apple Inc. | Method and system for secure network-based distribution of content |
US7278165B2 (en) * | 2003-03-18 | 2007-10-02 | Sony Corporation | Method and system for implementing digital rights management |
JP4271483B2 (en) * | 2003-04-24 | 2009-06-03 | ソニー株式会社 | Content processing apparatus and content processing method |
EP1630998A1 (en) * | 2003-06-05 | 2006-03-01 | Matsushita Electric Industrial Co., Ltd. | User terminal for receiving license |
KR100493900B1 (en) * | 2003-08-21 | 2005-06-10 | 삼성전자주식회사 | Method for Sharing Rights Object Between Users |
US20050076214A1 (en) * | 2003-10-03 | 2005-04-07 | Thomas David Andrew | Method and system for file downloads to portable computing devices |
US20050097052A1 (en) * | 2003-10-31 | 2005-05-05 | Nokia Corporation | Distribution of media objects |
US7499550B2 (en) * | 2004-02-09 | 2009-03-03 | International Business Machines Corporation | System and method for protecting a title key in a secure distribution system for recordable media content |
US7676846B2 (en) * | 2004-02-13 | 2010-03-09 | Microsoft Corporation | Binding content to an entity |
JP4350549B2 (en) * | 2004-02-25 | 2009-10-21 | 富士通株式会社 | Information processing device for digital rights management |
JP2005266896A (en) * | 2004-03-16 | 2005-09-29 | Nec Corp | System for preventing unauthorized use of software, method and program for preventing unauthorized use of software |
KR101043336B1 (en) * | 2004-03-29 | 2011-06-22 | 삼성전자주식회사 | Method and apparatus for acquiring and removing informations of digital right objects |
US7437771B2 (en) * | 2004-04-19 | 2008-10-14 | Woodcock Washburn Llp | Rendering protected digital content within a network of computing devices or the like |
KR101169021B1 (en) * | 2004-05-31 | 2012-07-26 | 삼성전자주식회사 | Method and Apparatus for sending right object information between device and portable storage |
US20050273629A1 (en) * | 2004-06-04 | 2005-12-08 | Vitalsource Technologies | System, method and computer program product for providing digital rights management of protected content |
JP4333494B2 (en) * | 2004-06-17 | 2009-09-16 | ソニー株式会社 | Content reproduction apparatus, content reproduction method, content management apparatus, content management method, and computer program. |
JP2006014035A (en) * | 2004-06-28 | 2006-01-12 | Toshiba Corp | Storage medium processing method, storage medium processor and program |
KR100608585B1 (en) | 2004-07-12 | 2006-08-03 | 삼성전자주식회사 | Method and apparatus for searching rights objects stored in portable storage device using object location data |
WO2006006781A1 (en) * | 2004-07-12 | 2006-01-19 | Samsung Electronics Co., Ltd. | Method and apparatus for searching rights objects stored in portable storage device using object location data |
US7827416B2 (en) * | 2004-08-26 | 2010-11-02 | Mitsubishi Denki Kabushiki Kaisha | Key management apparatus, document security and editing system, and key management method |
US8568225B2 (en) * | 2004-09-16 | 2013-10-29 | Bally Gaming, Inc. | User interface system and method for creating and verifying signed content |
WO2006033154A1 (en) * | 2004-09-24 | 2006-03-30 | Fujitsu Limited | Content distribution program |
US8843414B2 (en) * | 2005-02-04 | 2014-09-23 | Ricoh Company, Ltd. | Techniques for accessing controlled media objects |
WO2006095726A1 (en) * | 2005-03-11 | 2006-09-14 | Brother Kogyo Kabushiki Kaisha | Information distribution system, node device, and release data issuing method, etc. |
US7827113B2 (en) * | 2005-03-30 | 2010-11-02 | Sony Corporation | Method and system for providing a content subscription service |
US9507919B2 (en) * | 2005-04-22 | 2016-11-29 | Microsoft Technology Licensing, Llc | Rights management system for streamed multimedia content |
US20060272031A1 (en) * | 2005-05-24 | 2006-11-30 | Napster Llc | System and method for unlimited licensing to a fixed number of devices |
US7684566B2 (en) | 2005-05-27 | 2010-03-23 | Microsoft Corporation | Encryption scheme for streamed multimedia content protected by rights management system |
US8321690B2 (en) * | 2005-08-11 | 2012-11-27 | Microsoft Corporation | Protecting digital media of various content types |
US8887309B2 (en) * | 2005-08-23 | 2014-11-11 | Intrinsic Id B.V. | Method and apparatus for information carrier authentication |
US8194859B2 (en) * | 2005-09-01 | 2012-06-05 | Qualcomm Incorporated | Efficient key hierarchy for delivery of multimedia content |
US7565506B2 (en) | 2005-09-08 | 2009-07-21 | Qualcomm Incorporated | Method and apparatus for delivering content based on receivers characteristics |
US20070055629A1 (en) * | 2005-09-08 | 2007-03-08 | Qualcomm Incorporated | Methods and apparatus for distributing content to support multiple customer service entities and content packagers |
US8528029B2 (en) | 2005-09-12 | 2013-09-03 | Qualcomm Incorporated | Apparatus and methods of open and closed package subscription |
US8893179B2 (en) | 2005-09-12 | 2014-11-18 | Qualcomm Incorporated | Apparatus and methods for providing and presenting customized channel information |
US20070115929A1 (en) * | 2005-11-08 | 2007-05-24 | Bruce Collins | Flexible system for distributing content to a device |
US8571570B2 (en) | 2005-11-08 | 2013-10-29 | Qualcomm Incorporated | Methods and apparatus for delivering regional parameters |
US8600836B2 (en) | 2005-11-08 | 2013-12-03 | Qualcomm Incorporated | System for distributing packages and channels to a device |
US8533358B2 (en) | 2005-11-08 | 2013-09-10 | Qualcomm Incorporated | Methods and apparatus for fragmenting system information messages in wireless networks |
US7818261B2 (en) * | 2006-01-18 | 2010-10-19 | Corbis Corporation | Method and system for managing licenses to content |
US20070265977A1 (en) * | 2006-05-12 | 2007-11-15 | Chris Read | Method and system for improved digital rights management |
US8775319B2 (en) * | 2006-05-15 | 2014-07-08 | The Directv Group, Inc. | Secure content transfer systems and methods to operate the same |
US20070269044A1 (en) * | 2006-05-16 | 2007-11-22 | Bruestle Michael A | Digital library system with rights-managed access |
JP4957988B2 (en) * | 2006-05-29 | 2012-06-20 | ソニーモバイルコミュニケーションズ株式会社 | Content playback device |
JP4959796B2 (en) * | 2006-07-25 | 2012-06-27 | ソニー エレクトロニクス インク | Method and system for providing content subscription service |
KR100885722B1 (en) * | 2007-03-02 | 2009-02-26 | 주식회사 케이티프리텔 | User-generated content protection system and method |
US20080222044A1 (en) * | 2007-03-05 | 2008-09-11 | Microsoft Corporation | Protected content renewal |
US8296240B2 (en) * | 2007-03-22 | 2012-10-23 | Sony Corporation | Digital rights management dongle |
US8132020B2 (en) * | 2007-03-26 | 2012-03-06 | Zhu Yunzhou | System and method for user authentication with exposed and hidden keys |
US8474054B2 (en) * | 2007-06-26 | 2013-06-25 | Digital Keystone, Inc. | Systems and methods for conditional access and digital rights management |
US20090089883A1 (en) * | 2007-09-29 | 2009-04-02 | Sympact Technologies Llc | Method and apparatus for controlling media content distribution |
US8458099B2 (en) * | 2007-11-21 | 2013-06-04 | Licensestream, Inc. | System and method for online content licensing and distribution |
US20090254553A1 (en) * | 2008-02-08 | 2009-10-08 | Corbis Corporation | Matching media for managing licenses to content |
US20090210933A1 (en) * | 2008-02-15 | 2009-08-20 | Shear Jeffrey A | System and Method for Online Content Production |
US20090259591A1 (en) * | 2008-04-11 | 2009-10-15 | Microsoft Corporation | Information Rights Management |
KR101593569B1 (en) * | 2009-02-02 | 2016-02-15 | 삼성전자주식회사 | System and method for configurating of content object |
KR100930303B1 (en) | 2009-03-19 | 2009-12-08 | 주식회사 파수닷컴 | Digital Media Content Protection System and Method |
WO2010108181A2 (en) * | 2009-03-20 | 2010-09-23 | Lyryq, Inc. | Network-based simulated package for enclosing digital objects |
US8082486B1 (en) | 2011-06-09 | 2011-12-20 | Storify, Inc. | Source attribution of embedded content |
US12333484B1 (en) * | 2015-02-26 | 2025-06-17 | Comscore, Inc. | Secure access to controlled inventory profiles |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5715403A (en) * | 1994-11-23 | 1998-02-03 | Xerox Corporation | System for controlling the distribution and use of digital works having attached usage rights where the usage rights are defined by a usage rights grammar |
EP0968585A1 (en) | 1997-03-14 | 2000-01-05 | Cryptoworks Inc. | Digital product rights management technique |
US6289452B1 (en) * | 1997-11-07 | 2001-09-11 | Cybersource Corporation | Method and system for delivering digital products electronically |
US20020019814A1 (en) * | 2001-03-01 | 2002-02-14 | Krishnamurthy Ganesan | Specifying rights in a digital rights license according to events |
US7024393B1 (en) | 1999-03-27 | 2006-04-04 | Microsoft Corporation | Structural of digital rights management (DRM) system |
US7073063B2 (en) * | 1999-03-27 | 2006-07-04 | Microsoft Corporation | Binding a digital license to a portable device or the like in a digital rights management (DRM) system and checking out/checking in the digital license to/from the portable device or the like |
US7103574B1 (en) | 1999-03-27 | 2006-09-05 | Microsoft Corporation | Enforcement architecture and method for digital rights management |
US6920567B1 (en) * | 1999-04-07 | 2005-07-19 | Viatech Technologies Inc. | System and embedded license control mechanism for the creation and distribution of digital content files and enforcement of licensed use of the digital content files |
US6772340B1 (en) | 2000-01-14 | 2004-08-03 | Microsoft Corporation | Digital rights management system operating on computing device and having black box tied to computing device |
AU2001262517A1 (en) | 2000-06-05 | 2001-12-17 | Sealedmedia Limited | Digital rights management |
US6891953B1 (en) | 2000-06-27 | 2005-05-10 | Microsoft Corporation | Method and system for binding enhanced software features to a persona |
US7065507B2 (en) * | 2001-03-26 | 2006-06-20 | Microsoft Corporation | Supervised license acquisition in a digital rights management system on a computing device |
US7080043B2 (en) * | 2002-03-26 | 2006-07-18 | Microsoft Corporation | Content revocation and license modification in a digital rights management (DRM) system on a computing device |
-
2002
- 2002-06-12 US US10/170,791 patent/US7065787B2/en not_active Expired - Lifetime
-
2003
- 2003-06-11 JP JP2003167013A patent/JP4467255B2/en not_active Expired - Fee Related
- 2003-06-12 NO NO20032676A patent/NO332658B1/en not_active IP Right Cessation
- 2003-06-12 EP EP03013284A patent/EP1372055B1/en not_active Expired - Lifetime
- 2003-06-12 AT AT03013284T patent/ATE418111T1/en not_active IP Right Cessation
- 2003-06-12 DE DE60325298T patent/DE60325298D1/en not_active Expired - Lifetime
Cited By (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7493499B1 (en) | 2003-05-22 | 2009-02-17 | Copyright Clearance Center, Inc. | Method and apparatus for secure delivery and rights management of digital content |
EP1480100A1 (en) * | 2003-05-22 | 2004-11-24 | Copyright Clearance Center, Inc. | Method and apparatus for secure delivery and rights management of digital content |
US8638934B2 (en) | 2003-07-08 | 2014-01-28 | Imophaze Research Co., L.L.C. | Method and apparatus for secure key delivery for decrypting bulk digital content files at an unsecure site |
US8130963B2 (en) | 2003-07-08 | 2012-03-06 | Imophaze Research Co., L.L.C. | Method and apparatus for secure key delivery for decrypting bulk digital content files at an unsecure site |
US7324648B1 (en) | 2003-07-08 | 2008-01-29 | Copyright Clearance Center, Inc. | Method and apparatus for secure key delivery for decrypting bulk digital content files at an unsecure site |
CN100549903C (en) * | 2004-07-30 | 2009-10-14 | 耶德托存取公司 | The method and system of rights data objects is provided |
EP1621956A1 (en) * | 2004-07-30 | 2006-02-01 | Irdeto Access B.V. | Method of providing rights data objects |
EP1621955A1 (en) * | 2004-07-30 | 2006-02-01 | Irdeto Access B.V. | Method and device for providing access to encrypted content |
RU2390950C2 (en) * | 2004-07-30 | 2010-05-27 | Ирдето Эксесс Б.В. | Method of providing data objects on rights |
RU2395166C2 (en) * | 2004-07-30 | 2010-07-20 | Ирдето Эксесс Б.В. | Method for provision of access to coded content of one of multiple subscriber systems, device for access provision to coded content and method for generation of protected content packets |
AU2005203126B2 (en) * | 2004-07-30 | 2010-07-22 | Irdeto Access B.V. | Method of providing access to encrypted content to one of a plurality of consumer systems, device for providing access to encrypted content and method of generating a secure content package |
AU2005203126B8 (en) * | 2004-07-30 | 2010-12-23 | Irdeto Access B.V. | Method of providing access to encrypted content to one of a plurality of consumer systems, device for providing access to encrypted content and method of generating a secure content package |
US8527420B2 (en) | 2006-07-07 | 2013-09-03 | Swisscom Ag | Process and system for data transmission |
US10096024B2 (en) | 2006-07-07 | 2018-10-09 | Swisscom Ag | Process and system for data transmission |
US12316613B2 (en) | 2006-07-07 | 2025-05-27 | Interdigital Ce Patent Holdings, Sas | Process and system for selectable data transmission |
US10102527B2 (en) | 2006-07-07 | 2018-10-16 | Swisscom Ag | Process and system for data transmission |
EP1876550A1 (en) | 2006-07-07 | 2008-01-09 | Swisscom Mobile AG | Method and system for encrypted data transmission |
US8627103B2 (en) | 2008-05-23 | 2014-01-07 | Koninklijke Philips N.V. | Identity-based encryption of data items for secure access thereto |
WO2009141784A1 (en) * | 2008-05-23 | 2009-11-26 | Koninklijke Philips Electronics N.V. | Identity-based encryption of data items for secure access thereto |
CN102037474A (en) * | 2008-05-23 | 2011-04-27 | 皇家飞利浦电子股份有限公司 | Identity-based encryption of data items for secure access thereto |
CN102986162B (en) * | 2011-08-31 | 2015-08-05 | 华为技术有限公司 | Based on license dynamic management approach, the Apparatus and system of TCM or TPM |
CN102986162A (en) * | 2011-08-31 | 2013-03-20 | 华为技术有限公司 | TCM or TPM-based license dynamic management method, device and system |
WO2012149717A1 (en) * | 2011-08-31 | 2012-11-08 | 华为技术有限公司 | License dynamic management method, device and system based on tcm or tpm |
WO2021041676A1 (en) * | 2019-08-27 | 2021-03-04 | Intertrust Technologies Corporation | Multi-party cryptographic systems and methods |
US11843686B2 (en) | 2019-08-27 | 2023-12-12 | Intertrust Technologies Corporation | Multi-party cryptographic systems and methods |
US12200099B2 (en) | 2019-08-27 | 2025-01-14 | Intertrust Technologies Corporation | Multi-party cryptographic systems and methods |
Also Published As
Publication number | Publication date |
---|---|
NO20032676L (en) | 2003-12-15 |
ATE418111T1 (en) | 2009-01-15 |
EP1372055B1 (en) | 2008-12-17 |
DE60325298D1 (en) | 2009-01-29 |
JP4467255B2 (en) | 2010-05-26 |
NO332658B1 (en) | 2012-11-26 |
NO20032676D0 (en) | 2003-06-12 |
EP1372055A3 (en) | 2005-10-05 |
US7065787B2 (en) | 2006-06-20 |
US20030233561A1 (en) | 2003-12-18 |
JP2004046833A (en) | 2004-02-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1372055B1 (en) | Publishing content in connection with digital rights management (DRM) architecture | |
US7318236B2 (en) | Tying a digital license to a user and tying the user to multiple computing devices in a digital rights management (DRM) system | |
US7860802B2 (en) | Flexible licensing architecture in content rights management systems | |
US7577999B2 (en) | Publishing digital content within a defined universe such as an organization in accordance with a digital rights management (DRM) system | |
US7502945B2 (en) | Using a flexible rights template to obtain a signed rights label (SRL) for digital content in a rights management system | |
US7353402B2 (en) | Obtaining a signed rights label (SRL) for digital content and obtaining a digital license corresponding to the content based on the SRL in a digital rights management system | |
US7549060B2 (en) | Using a rights template to obtain a signed rights label (SRL) for digital content in a digital rights management system | |
US7891007B2 (en) | Systems and methods for issuing usage licenses for digital content and services | |
US8738536B2 (en) | Licensing content for use on portable device | |
US20040158731A1 (en) | Publishing digital content within a defined universe such as an organization in accordance with a digital rights management (DRM) system | |
US7457964B2 (en) | Trusted path for transmitting content thereon | |
HK1069462A (en) | Tying a digital license to a user and tying the user to multiple computing devices in a digital rights management (drm) system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL LT LV MK |
|
PUAL | Search report despatched |
Free format text: ORIGINAL CODE: 0009013 |
|
AK | Designated contracting states |
Kind code of ref document: A3 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL LT LV MK |
|
17P | Request for examination filed |
Effective date: 20060327 |
|
AKX | Designation fees paid |
Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06F 21/00 20060101AFI20071213BHEP |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REF | Corresponds to: |
Ref document number: 60325298 Country of ref document: DE Date of ref document: 20090129 Kind code of ref document: P |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 |
|
NLV1 | Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act | ||
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20090328 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20090317 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20090518 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20090317 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 |
|
26N | No opposition filed |
Effective date: 20090918 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090630 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20090612 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20100226 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: RN |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090630 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090630 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090630 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090612 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090612 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: FC |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100101 |
|
PGRI | Patent reinstated in contracting state [announced from national office to epo] |
Ref country code: FR Effective date: 20100604 Ref country code: DE Effective date: 20100426 |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: S28 Free format text: RESTORATION ALLOWED Effective date: 20100709 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20090318 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20090612 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20090618 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20081217 |
|
PGRI | Patent reinstated in contracting state [announced from national office to epo] |
Ref country code: DE Effective date: 20100426 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R082 Ref document number: 60325298 Country of ref document: DE Representative=s name: GRUENECKER, KINKELDEY, STOCKMAIR & SCHWANHAEUS, DE |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: 732E Free format text: REGISTERED BETWEEN 20150108 AND 20150114 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 60325298 Country of ref document: DE Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, REDMOND, US Free format text: FORMER OWNER: MICROSOFT CORP., REDMOND, WASH., US Effective date: 20150126 Ref country code: DE Ref legal event code: R082 Ref document number: 60325298 Country of ref document: DE Representative=s name: GRUENECKER PATENT- UND RECHTSANWAELTE PARTG MB, DE Effective date: 20150126 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20150611 Year of fee payment: 13 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: TP Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, US Effective date: 20150724 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 14 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 15 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20160612 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 16 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20220506 Year of fee payment: 20 Ref country code: FR Payment date: 20220510 Year of fee payment: 20 Ref country code: DE Payment date: 20220505 Year of fee payment: 20 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R071 Ref document number: 60325298 Country of ref document: DE |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230501 |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: PE20 Expiry date: 20230611 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION Effective date: 20230611 |