Digital rights management provision apparatus, system, and method
Claim Score by NHIP
Abstract
Provided is digital rights management (DRM) provision technology, and more particularly, are an apparatus, system, and method which can easily provide content using one or more DRM systems. A DRM provision apparatus includes a content download unit which downloads encrypted real content and dummy content from a download server and which manages the downloaded real content and dummy content; a license management unit which manages a license issued by a license server; and a processing unit which manages the downloaded real content and dummy content and the issued license.

Term
1.6 yearsto projected expiry
Projected expiry 16 April 2028, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
28 claims: 3 independent, 25 dependent
- 1A digital rights management (DRM) provision apparatus comprising:a content download unit which downloads encrypted real content and dummy content from a download server and manages the downloaded real content and dummy content;a license management unit which manages a license issued by a license server;and a processing unit which manages the downloaded real content and dummy content and the issued license.
- 6A Digital Rights Management (DRM) provision system comprising:a packaging server which performs a first packaging process and a second packaging process on unencrypted real content and which generates encrypted real content and dummy content respectively;a download server which downloads the encrypted real content and the dummy content;a license server which generates and issues a license for the encrypted real content;and a DRM provision apparatus which receives and manages the encrypted real content, the dummy content, and the license.
- 16Broadest claimClaim Score 91, very broad(NHIP)A Digital Rights Management (DRM) provision method comprising:receiving encrypted real content and dummy content;and receiving a license issued for the encrypted real content.
Independent claims3
104 paragraphs in 4 sections, as filed
0001This application claims priority from Korean Patent Application No. 10-2007-0020390 filed on Feb. 28, 2007 in the Korean Intellectual Property Office and U.S. Provisional Patent Application No. 60/852,992 filed on Oct. 20, 2006 in the United States Patent and Trademark Office, the disclosures of which are incorporated herein by reference in its entirety.
BACKGROUND OF THE INVENTION
00021. Field of the Invention
0003The present invention relates to digital rights management (DRM) provision technology, and more particularly, to an apparatus, system, and method which can easily provide content using one or more DRM systems.
00042. Description of the Related Art
0005Generally, digital rights management (DRM) technology protects and manages the rights of digital content creators. According to the DRM technology, a content provision server stores content in an encrypted form and provides encrypted content and key information required to decrypt the encrypted content to a user when the user makes a request for purchasing the encrypted content. The DRM technology defines the number of times that digital content can be played back, whether or not the digital content can be duplicated, the number of times the content can be duplicated, and the like.
0006DRM functions are largely divided into the following: the protection of digital content, the management of usage rules of the digital content, and the management of a billing system. In order to protect digital content, the DRM technology encrypts the digital content and thus prevents the illegal distribution or use of the digital content in all stages (i.e., creation, distribution, use, and disposal) of its life cycle. In addition, the DRM technology enables only an authorized user with an encryption key to decrypt and use encrypted content. Therefore, even if the encrypted content is illegally distributed, it cannot be used without the encryption key.
0007However, DRM technologies (such as Microsoft (MS) DRM and Open Mobile Alliance (OMA) DRM) developed by various developers are not compatible with each other. That is, a DRM structure developed by a developer runs on hardware or software that supports the DRM structure of the developer, but not on other platforms. Therefore, a user has to purchase different hardware or software that supports each DRM.
0008In this regard, there is a need for a technology that can play back content to which different DRM standards developed by various developers have been applied, on any host device.
SUMMARY OF THE INVENTION
0009It is an aspect of the present invention to implement a content provision system using one or more digital rights management (DRM) systems.
0010However, the aspects of the present invention are not restricted to the one set forth herein. The above and other aspects of the present invention will become more apparent to one of ordinary skill in the art to which the present invention pertains by referencing a detailed description of the present invention given below.
0011According to an aspect of the present invention, there is provided a DRM provision apparatus including a content download unit downloading encrypted real content and dummy content from a download server and managing the downloaded real content and dummy content; a license management unit managing a license issued by a license server; and a processing unit managing the downloaded real content and dummy content and the issued license.
0012According to another aspect of the present invention, there is provided a DRM provision system including a packaging server performing a first packaging process and a second packaging on unencrypted real content and generating encrypted real content and dummy content; a download server downloading the encrypted real content and the dummy content; a license server generating and issuing a license for the encrypted real content; and a DRM provision apparatus receiving and managing the encrypted real content, the dummy content, ad the license.
0013According to another aspect of the present invention, there is provided a DRM provision method including receiving encrypted real content and dummy content; and receiving a license issued for the encrypted real content.
BRIEF DESCRIPTION OF THE DRAWINGS
0014The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings in which:
0015<figref idref="DRAWINGS">FIG. 1</figref> illustrates a digital rights management (DRM) provision system according to an exemplary embodiment of the present invention;
0016<figref idref="DRAWINGS">FIG. 2</figref> illustrates a license binding structure of the DRM provision system according to an exemplary embodiment of the present invention;
0017<figref idref="DRAWINGS">FIG. 3</figref> illustrates the operation of a packaging server included in the DRM provision system according to an exemplary embodiment of the present invention;
0018<figref idref="DRAWINGS">FIG. 4</figref> illustrates the structure of a DRM header in the DRM provision system according to an exemplary embodiment of the present invention;
0019<figref idref="DRAWINGS">FIG. 5</figref> illustrates the operation of downloading content using the DRM provision system according to an exemplary embodiment of the present invention;
0020<figref idref="DRAWINGS">FIG. 6</figref> illustrates the operation of receiving a license using the DRM provision system according to an exemplary embodiment of the present invention;
0021<figref idref="DRAWINGS">FIG. 7</figref> is a block diagram of a DRM provision apparatus included in the DRM provision system according to an exemplary embodiment of the present invention;
0022<figref idref="DRAWINGS">FIG. 8</figref> is a block diagram of a portable storage device included in the DRM provision system according to an exemplary embodiment of the present invention;
0023<figref idref="DRAWINGS">FIG. 9</figref> illustrates the operation of a host device included in the DRM provision system according to an exemplary embodiment of the present invention; and
0024<figref idref="DRAWINGS">FIG. 10</figref> illustrates the operation of receiving DRM content using a kiosk included in the DRM provision system according to an exemplary embodiment of the present invention.
DETAILED DESCRIPTION OF THE INVENTION
0025The present invention will now be described more fully with reference to the accompanying drawings in which exemplary embodiments of the invention are shown. The invention may, however, be embodied in many different forms and should not be construed as being limited to the exemplary embodiments set forth herein; rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art. Like reference numerals in the drawings denote like elements, and thus their description will be omitted.
0026Exemplary embodiments of the present invention will hereinafter be described in detail with reference to the accompanying drawings.
0027<figref idref="DRAWINGS">FIG. 1</figref> illustrates a digital rights management (DRM) provision system <b>10</b> according to an exemplary embodiment of the present invention. Referring to <figref idref="DRAWINGS">FIG. 1</figref>, the DRM provision system <b>10</b> includes a packaging server <b>100</b>, a download server <b>200</b>, a license server <b>300</b>, and a DRM provision apparatus <b>400</b>. The DRM provision system <b>10</b> may further include a portable storage device <b>500</b> using content registered by a content provider and storing content and its license by communicating with the DRM provision apparatus <b>400</b>. The portable storage device <b>500</b> plays back content by being connected to a host device <b>600</b>.
0028The content provider registers content, which is to be provided, with a contents management system (CMS). The CMS supports a function of managing the registration, retrieval, and deletion of a product (content) and a function of setting rights. In addition, the content provider registers meta information of content in order to distribute the content to users who desire to use the content, sets usage rights of the content for service business application, and decides the price of the content.
0029The packaging server <b>100</b> performs a first packaging process and a second packaging process on real content registered in the CMS by the content provider and generates dummy content and a DRM packaging file. Here, packaging denotes an encryption process for protecting content. The dummy content denotes a file required to receive a license for each DRM (such as Microsoft (MS) DRM and Open Mobile Alliance (OMA) DRM).
0030That is, the packaging server <b>100</b> packages content in order to support the MSDRM and the OMA DRM. The first and second packaging processes will be described in detail later with reference to <figref idref="DRAWINGS">FIG. 3</figref>.
0031The download server <b>200</b> provides (downloads) content requested by a user to the DRM provision apparatus <b>400</b>. In this case, the downloaded content is the real content encrypted by the packaging server <b>100</b> and the dummy content. The operation of downloading content will be described in detail later with reference to <figref idref="DRAWINGS">FIG. 5</figref>.
0032The license server <b>300</b> issues (provides) a license for using the encrypted real content. Here, the license is issued based on information regarding the dummy content. The operation of receiving a license will be described in detail later with reference to <figref idref="DRAWINGS">FIG. 6</figref>.
0033The DRM provision apparatus <b>400</b> provides content (e.g., the encrypted real content and the dummy content) received from the download server <b>200</b> and the license server <b>300</b> to the portable storage device <b>500</b>. The DRM provision apparatus <b>400</b> may be a kiosk, a personal computer (PC), a portable multimedia player (PMP), a settop box, or a mobile phone. The operation of the DRM provision apparatus <b>400</b> will be described in detail later with reference to <figref idref="DRAWINGS">FIG. 7</figref>.
0034The portable storage device <b>500</b> stores the encrypted content, the dummy content, and the license provided by the DRM provision apparatus <b>400</b>. The portable storage device <b>500</b> includes a non-volatile memory, such as a flash memory, which can read, write and erase data, and is capable of performing a predetermined computation on data. In addition, the portable storage device <b>500</b> can easily be connected to or disconnected from the host device <b>600</b>. Examples of the portable storage device <b>500</b> include a smart media, a memory stick, a CompactFlash (CF) card, an extreme Digital (xD) card, and a multimedia card (MMC). The operation of the portable storage device <b>500</b> will be described in more detail later with reference to <figref idref="DRAWINGS">FIG. 8</figref>.
0035Meanwhile, the encrypted content, the dummy content, and the license may already be stored in the portable storage device <b>500</b>.
0036For example, a user may purchase the portable storage device <b>500</b> storing the encrypted content, the dummy content and the license, and use the encrypted content, the dummy content and the license already stored in the portable storage device <b>500</b>. That is, the user can purchase a portable storage device storing predetermined content and always use the content on the host device <b>600</b>.
0037The host device <b>600</b> can be connected to the portable storage device <b>500</b> and can play back a content object by using a license and a rights object. The host device <b>600</b> may be a portable content playback device, such as a mobile phone, a personal digital assistant (PDA) or an MP3 player, or a fixed content playback device such as a desktop computer or a digital television (TV). The operation of the host device <b>600</b> will be described in more detail later with reference to <figref idref="DRAWINGS">FIG. 9</figref>.
0038<figref idref="DRAWINGS">FIG. 2</figref> illustrates a license binding structure of the DRM provision system <b>10</b> according to an exemplary embodiment of the present invention. The DRM provision system <b>10</b> uses a different structure from that of a related DRM system which binds encrypted content to a license on a one-to-one basis.
0039Referring to <figref idref="DRAWINGS">FIG. 2</figref>, the related DRM system binds encrypted content and a license file for each DRM. Therefore, for 1 Gbyte of video, a memory with a capacity of n times 1 Gbyte is required.
0040On the other hand, the DRM provision system <b>10</b> according to the present invention provides a piece of encrypted real content and a bundle of approximately 5 Kbytes of encrypted dummy content and a license file for each DRM. Therefore, content provided by the DRM provision system <b>10</b> does not require a large memory space as in the related DRM system.
0041That is, the DRM provision system <b>10</b> according to the present invention has a hierarchical structure so that it can run both on a handset loaded with MSDRM and another handset loaded with OMA DRM.
0042When the related DRM system searches for a license in order to play back content, it reads a license ID (LID) or a content ID (CID) specified in a DRM handset of encrypted content and searches a license storage database (DB) or file for a corresponding license.
0043However, the DRM provision system <b>10</b> does not directly bind encrypted real content to a corresponding license in order to support both the MSDRM and the OMA DRM. Instead, the DRM provision system <b>10</b> includes dummy content between the encrypted real content and the corresponding license.
0044For example, if the host device <b>600</b> has the MSDRM, the DRM provision system <b>10</b> reads the ID of dummy content from encrypted real content and then searches for the dummy content protected by the MSDRM.
0045Then, if a file encrypted using the MSDRM is selected from the dummy content, the DRM provision system <b>10</b> obtains an LID from a header of a corresponding piece of dummy content and obtains a license from a license storage DB or file. The dummy content has a content format which can be played back or listened to by users. However, the dummy content merely serves as a medium by which the encrypted real content and the license can be bound to a number of versions of the DRM system. The license bound to the dummy content is a file that sets the rights for the encrypted real content. Meanwhile, the same process described above is applied to handsets loaded with the OMA DRM system and other DRM systems.
0046<figref idref="DRAWINGS">FIG. 3</figref> illustrates the operation of the packaging server <b>100</b> included in the DRM provision system <b>10</b> according to an exemplary embodiment of the present invention.
0047The packaging server <b>100</b> encrypts real content by performing the first and second packaging processes on the real content and generates dummy content and a DRM packaging file.
0048The first packaging process will now be described. The first packaging process includes a first operation of registering real content, a second operation of generating a DRM header, a third operation of generating a content encryption key (CEK), and a fourth operation of encrypting the real content.
0049Specifically, if a content provider registers real content with a CMS, the packaging server <b>100</b> generates a DRM header of the registered real content. The DRM header includes various forms of metadata that can explain content characteristics such as a dummy content name associated with encrypted content. In addition, information contained in the DRM header uses information registered with a metadata DB of the CMS, and a dummy content file name is automatically generated based on an uniform resource identifier (URI) registered with the CMS. In addition, the dummy content file name is composed of an English string with no more than 255 English characters.
0050The structure of the DRM header generated by the packaging server <b>100</b> will now be described with reference to <figref idref="DRAWINGS">FIG. 4</figref>.
0051Referring to <figref idref="DRAWINGS">FIG. 4</figref>, DRM type is recorded in a signature field of a DRM header, and a filename of dummy content is recorded in a filename length field. A DRM encryption algorithm is recorded in a DRM header length field, and DRM version information is recorded in a DRM header field. In addition, option information is recorded in a padding field, information regarding content length is recorded in a data length field, and content data information is recorded in a content data field.
0052Referring back to <figref idref="DRAWINGS">FIG. 3</figref>, the packaging server <b>100</b> generates a CEK in order to encrypt the registered real content. In order to generate a CEK (indicated by reference character CEK<sub>R</sub>) of the registered real content, the packaging server <b>100</b> generates a 16 byte-CEK using a seed value and base64-encodes the generated 16 byte-CEK. Here, the seed value uses a real-time session key value. While ‘real-time’ time information, when content is packaged, is used in the present exemplary embodiment, a random number table separately managed or other values may also be used. For example, certain music files, such as a musical instrument digital interface (MIDI), may be stored in a DB in the form of a random number table and may be used as CEK<sub>R </sub>for encrypting certain real content. In this case, CEK<sub>R </sub>is reproducible content.
0053Next, the real content is encrypted using the generated DRM header, CEK<sub>R </sub>and a symmetric key algorithm, and thus the encrypted real content is generated. The symmetric key algorithm uses an AES 128-bit algorithm and may also use other symmetric key algorithms.
0054If the first packaging process is completed, the second packaging process is performed. The second packaging process includes a first operation of generating dummy content, a second operation of generating a CEK of the dummy content, and a third operation of packaging the dummy content. The dummy content is not reproducible data, such as music or a movie, but an intermediate file for generating a license that sets the rights of encrypted content and binding the license to the encrypted content. If certain music files were used as CEK<sub>R </sub>in the first packaging process, the dummy content may be reproducible content.
0055Target dummy content of DRM packaging, which is to be supported, is automatically generated using CEK<sub>R </sub>that was used to encrypt the real content. Here, the body of the dummy content includes CEK<sub>R</sub>.
0056For example, the OMA DRM generates dummy content in an MP3 format. Thus, the dummy content has a payload as a CEK. In addition, the MSDRM generates dummy content in a Windows Media Audio (WMA) format. The MSDRM can generate dummy content not only in the WMA format but also in Windows Media Video (WMV) and Advanced Systems Format (ASF) formats. Also, the OMA DRM can generate dummy content in various formats.
0057Next, after generating the dummy content in the second packaging process the packaging server <b>100</b> generates a CEK in order to encrypt the dummy content. The CEK of the dummy content is indicated by reference character CEK<sub>D</sub>.
0058<figref idref="DRAWINGS">FIG. 5</figref> illustrates the operation of downloading content using the DRM provision system <b>10</b> according to an exemplary embodiment of the present invention.
0059Referring to <figref idref="DRAWINGS">FIG. 5</figref>, a user or a registration server checks whether the user's portable storage device <b>500</b> has been registered. Then, the user selects content that the user desires to purchase in a web page through the Internet and requests the download server <b>200</b> to download the selected content (operation {circle around (<b>1</b>)}).
0060Accordingly, the download server <b>200</b> requests a user authentication server (not shown) to authenticate information (provided by, for example, the portable storage device <b>500</b>) requested by the user. If the portable storage device <b>500</b> is not registered with the user authentication server, the user's request for downloading the selected content is rejected. That is, the download server <b>200</b> downloads the requested content only after the user registers the portable storage device <b>500</b> with the user authentication server.
0061Next, the download server <b>200</b> prepares the requested content, i.e., encrypted content and dummy content to be downloaded (operation {circle around (<b>2</b>)}). The encrypted content is a file, such as a moving picture or music, which is copyrighted, and the dummy content is a file bound to a license for a content file or to a rights object.
0062The download server <b>200</b> transmits the content requested by the user to the DRM provision apparatus <b>400</b> (operation {circle around (<b>3</b>)}), and the DRM provision apparatus <b>400</b> downloads the received content to the portable storage device <b>500</b> (operation {circle around (<b>4</b>)}).
0063Then, the downloaded content (i.e., the encrypted content and the dummy content) is stored in a content DB. Since the encrypted content itself does not have a license, the license server <b>300</b> can be accessed only when the encrypted content exists together with the dummy content.
0064<figref idref="DRAWINGS">FIG. 6</figref> illustrates the operation of receiving a license using the DRM provision system <b>10</b> according to an exemplary embodiment of the present invention. After content is downloaded, a user has to receive a license for the content in order to use the content. The license includes a CEK for decrypting the content as well as various rights for the content. In the present exemplary embodiment, the operation of obtaining a license using Windows Media (WM) DRM will be described.
0065The DRM provision apparatus <b>400</b> analyzes a DRM header of dummy content (operation {circle around (<b>1</b>)}). By analyzing the DRM header, the DRM provision apparatus <b>400</b> obtains URI information required to request the issuance of a license and a key ID (KID) value required to search for the license.
0066Then, the DRM provision apparatus <b>400</b> generates challenge data using the DRM header and a device certificate (operation {circle around (<b>2</b>)}) and transmits the generated challenge data to the license server <b>300</b> using a hypertext transfer protocol (HTTP)-post method (operation {circle around (<b>3</b>)}). The challenge data includes the DRM header and the device certificate and is base64-encoded.
0067The license server <b>300</b> base64-decodes the received challenge data and obtains the KID by analyzing the DRM header. Then, the license server <b>300</b> searches for a CEK that matches the obtained KID, encrypts the CEK using a public key included in the device certificate, and inserts the encrypted CEK into the license (operation {circle around (<b>4</b>)}). Here, the CEK is encrypted using an elliptic curve cryptography (ECC) asymmetric key encryption method.
0068The license server <b>300</b> base64-encodes the generated license and transmits the base64-encoded license to the DRM provision apparatus <b>400</b> (operation {circle around (<b>5</b>)}). A transmission method used here is a direct license acquisition (DLA) method. The DRM provision system <b>10</b> suggested in the present invention transmits the encoded license using the DLA method.
0069The DRM provision apparatus <b>400</b> provides the base64-encoded license to the portable storage device <b>500</b>, and the portable storage device <b>500</b> stores the base64-encoded license.
0070<figref idref="DRAWINGS">FIG. 7</figref> is a block diagram of the DRM provision apparatus <b>400</b> included in the DRM provision system <b>10</b> according to an exemplary embodiment of the present invention.
0071Referring to <figref idref="DRAWINGS">FIG. 7</figref>, the DRM provision apparatus <b>400</b> includes a content download unit <b>410</b>, a license management unit <b>420</b>, a preview provision unit <b>430</b>, and a processing unit <b>440</b>.
0072The content download unit <b>410</b> downloads content from the download server <b>200</b>, and the downloaded content is stored in the portable storage device <b>500</b>. The downloaded content includes encrypted real content and two pieces of dummy content (e.g., OMA DRM- *.dcf and MS-DRM- *.wma), which are managed together as a single piece of complex content.
0073The license management unit <b>420</b> receives a license (or a rights object) from the license server <b>300</b> so that a user can use the downloaded content. A license transmitted using an OMA DRM method and a license transmitted using an MS DRM method are stored in respective storage areas for licenses.
0074For example, an OMA rights object is stored in a rights object DB, and an encrypted storage space is configured and used in order to prevent rights from being arbitrarily accessed or modified. In addition, an MS DRM rights object is stored in a hash storage unit.
0075The preview provision unit <b>430</b> provides the content, which was downloaded by the content download unit <b>410</b> at the request of the user, on a preview screen.
0076The processing unit <b>440</b> manages the operation of each of the content download unit <b>410</b>, the license management unit <b>420</b>, and the preview provision unit <b>430</b> included in the DRM provision apparatus <b>400</b>. In addition, the processing unit <b>440</b> provides the real content and the dummy content downloaded by the content download unit <b>410</b> and a license of the dummy content provided by the license management unit <b>420</b> to the portable storage device <b>500</b>.
0077The term ‘unit’, as used herein, means, but is not limited to, a software or hardware component, such as a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), which performs certain tasks. A unit may advantageously be configured to reside on the addressable storage medium and configured to execute on one or more processors. Thus, a unit may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functionality provided for in the components and modules may be combined into fewer components and units or further separated into additional components and units.
0078<figref idref="DRAWINGS">FIG. 8</figref> is a block diagram of the portable storage device <b>500</b> included in the DRM provision system <b>10</b> according to an exemplary embodiment of the present invention.
0079Referring to <figref idref="DRAWINGS">FIG. 8</figref>, the portable storage device <b>500</b> includes storage space, i.e., a tamper resistant module (TRM) area <b>510</b>, a DRM area <b>520</b>, and a user access area <b>530</b>.
0080The TRM area <b>510</b> stores DRM security information. That is, the TRM area <b>510</b> stores a serial number of the portable storage device <b>500</b>, a public/private key, a certificate, a device group key, etc. for each DRM.
0081The TRM area <b>510</b> may be created when the portable storage device <b>500</b> is manufactured. Alternatively, the TRM area <b>510</b> may be written once when the portable storage device <b>500</b> is first used after being purchased. In this case, the TRM area <b>510</b> can be written after being authenticated by a network server. For security, it is desirable to create the TRM area <b>510</b> in advance when the portable storage device <b>500</b> is manufactured. The TRM area <b>510</b> is where data can be read only. The data stored in the TRM area <b>510</b> can be read using a particular application programming interface (API) that accesses the portable storage device <b>500</b>.
0082The rights to access the data recorded in the TRM area <b>510</b> must be given only to a DRM agent (not shown), and an external user must be prohibited from moving or changing the data.
0083The DRM area <b>520</b> stores encrypted dummy content and a license file (or a rights object). Even if the DRM area <b>520</b> is open to the outside, no security problem arises. However, if a user of the portable storage device <b>500</b> accesses the DRM area <b>520</b> and removes or changes a file therein, a fatal problem to the operation of the DRM agent may arise. Such a file is stored in the DRM area <b>520</b>. In addition, the DRM area <b>520</b> can be accessed using an API provided by the DRM agent or a particular portable storage device.
0084The user access area <b>530</b> stores encrypted real content, such as video or audio, which can actually be played back. General users can arbitrarily read or write content in the user access area <b>530</b>.
0085<figref idref="DRAWINGS">FIG. 9</figref> illustrates the operation of the host device <b>600</b> included in the DRM provision system <b>10</b> according to an exemplary embodiment of the present invention. In the present exemplary embodiment, it is assumed that the host device <b>600</b> also performs the function of the DRM provision apparatus <b>400</b> and includes the portable storage device <b>500</b>. In the present exemplary embodiment, the operation of playing back encrypted content using an MS DRM agent is described.
0086Referring to <figref idref="DRAWINGS">FIG. 9</figref>, if a user selects desired content (operation {circle around (<b>1</b>)}), the content download unit <b>410</b> determines whether DRM has been applied to a selected file. If the selected file is encrypted content, the content download unit <b>410</b> searches for a filename of dummy content in order to search for a license of the encrypted content (operation {circle around (<b>2</b>)}). Here, the filename of the dummy content is read from the DRM header.
0087Next, URI information required to request the issuance of the license and a KID required to search for the license are obtained by analyzing the DRM header (operation {circle around (<b>3</b>)}). Then, the license management unit <b>420</b> searches for the license stored in the DRM area <b>520</b> of the portable storage device <b>500</b> using the obtained KID (operation {circle around (<b>4</b>)}).
0088If it turns out that the license does not exist or has expired, the license management unit <b>420</b> requests the license server <b>300</b> to issue a license through a license downloading process. If the license management unit <b>420</b> obtains the license from the DRM area <b>520</b> of the portable storage device <b>500</b>, it transmits the obtained license to the host device <b>600</b>.
0089The host device <b>600</b> reads a decryption key CEK<sub>D </sub>of the dummy content included in the license. Since the decryption key CEK<sub>D </sub>of the dummy content is encrypted using a public key, the encrypted decryption key is decrypted using a private key stored in the TRM area <b>510</b>. Consequently, the decryption key CEK<sub>D </sub>is obtained. Then, the dummy content is decrypted, and thus CEK<sub>R </sub>of the encrypted real content is obtained (operation {circle around (<b>5</b>)}).
0090Next, the encrypted real content is decrypted using CEK<sub>R</sub>, and a file is played back (operation {circle around (<b>6</b>)}). The real content has been encrypted using the symmetric key (e.g., AES 128-bit) algorithm.
0091If the encrypted real content is normally played back, the host device <b>600</b> requests the license management unit <b>420</b> to update the license (for example, update a playback count) (operation {circle around (<b>7</b>)}).
0092<figref idref="DRAWINGS">FIG. 10</figref> illustrates the operation of receiving DRM content using a kiosk included in the DRM provision system <b>10</b> according to an exemplary embodiment of the present invention. First of all, a user has to register the portable storage device <b>500</b> before downloading content using the kiosk. The kiosk is an exemplary embodiment of the DRM provision apparatus <b>400</b>.
0093The user connects the portable storage device <b>500</b> (e.g., an MMC) to a portable storage device interface or universal serial bus (USB) interface of the kiosk, selects desired content and its license type from a product list of the kiosk, and makes a purchase request (operation {circle around (<b>1</b>)}).
0094Next, the kiosk identifies the portable storage device <b>500</b> that the user connected thereto. The kiosk includes a table that matches a user ID with a serial number of the portable storage device <b>500</b>. Therefore, the kiosk searches the table for the user ID based on the serial number of the portable storage device <b>500</b> connected thereto (operation {circle around (<b>2</b>)}). Alternatively, the kiosk may perform an authentication process through a network server.
0095Referring to the internal structure of the kiosk, the kiosk includes a TRM folder, a DRM folder, and a content folder. The TRM folder stores a table in which a user ID is matched with a serial number, and the DRM folder stores a license and dummy content for each user ID. In addition, the content folder stores encrypted content.
0096The kiosk downloads content at a shared directory using Active X (operation {circle around (<b>3</b>)}). Here, real content and dummy content are downloaded together.
0097If the content is downloaded, the kiosk obtains a license for the content selected by the user based on the found user ID. The process of obtaining the license for the content from the license server <b>300</b> using the kiosk is identical to the process of obtaining a license described above with reference to <figref idref="DRAWINGS">FIG. 6</figref>, and thus a detailed description thereof will be omitted.
0098Then, the kiosk provides a preview of the downloaded content (operation {circle around (<b>4</b>)}). If the user selects a [Playback] function on a purchase screen of the kiosk, a preview screen appears. Here, if the user selects a content type to preview, a content list is displayed. If the user selects the [Playback] function on the right of the content list, a preview function is executed. For the preview function, the encrypted real content is decrypted. Since the operation of decrypting encrypted content has been described above with reference to <figref idref="DRAWINGS">FIG. 9</figref>, a detailed description thereof will be omitted.
0099If the preview function is completed, the license for the content selected by the user based on the found user ID, the dummy content, and the encrypted content are transmitted to the portable storage device <b>500</b>, and thus the purchasing process of the content is completed (operation {circle around (<b>5</b>)}).
0100As described above, a DRM provision apparatus, system, and method according to the present invention provide at least one of the following advantages.
0101Since a content provision system is implemented using one or more DRM (MSDRM, OMA DRM, and the like) systems, it can provide content packaged using a unified encryption algorithm.
0102In addition, DRM content, which can be played back by host devices having different DRM systems, can be provided.
0103Regardless of an encoding format of copyrighted real content, multi-DRM packaging is provided for content in all formats. Therefore, there is no need for a content provider to spend additional money to encode content.
0104While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the following claims. The exemplary embodiments should be considered in descriptive sense only and not for purposes of limitation.
Contents4
11 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2019095591A1 | Cited by | United States of America | Search report |
| US10257548B2 | Cited by | United States of America | Search report |
| US8660961B2 | Cited by | United States of America | Search report |
| US2012042173A1 | Cited by | United States of America | Pre-grant |
| US2011213721A1 | Cited by | United States of America | Pre-grant |
| US2014215214A1 | Cited by | United States of America | Pre-grant |
| US2022398202A1 | Cited by | United States of America | Search report |
| US10445474B2 | Cited by | United States of America | Applicant |
| WO2016008918A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US8225097B2 | Cited by | United States of America | Search report |
| US2019089708A1 | Cited by | United States of America | Search report |
| US10462142B2 | Cited by | United States of America | Search report |
| US2006107046A1 | Cited by | United States of America | Pre-grant |
| CN105283881A | Cited by | China | Search report |
| US2009190765A1 | Cited by | United States of America | Pre-grant |
| US2015012932A1 | Cited by | United States of America | Pre-grant |
| US2010191974A1 | Cited by | United States of America | Pre-grant |
| US2010083176A1 | Cited by | United States of America | Pre-grant |
| US2013283052A1 | Cited by | United States of America | Pre-grant |
| EP2380307A4 | Cited by | European Patent Office (EPO) | Search report |
| US11257099B2 | Cited by | United States of America | Search report |
| ES2468690A1 | Cited by | Spain | Search report |
| US2009198993A1 | Cited by | United States of America | Pre-grant |
| US10229248B2 | Cited by | United States of America | Applicant |
| US9892239B2 | Cited by | United States of America | Search report |
| US2019095591A1 | Cited by | United States of America | Search report |
| US11544397B1 | Cited by | United States of America | Search report |
| US8856510B2 | Cited by | United States of America | Search report |
| US2012054315A1 | Cited by | United States of America | Pre-grant |
| US8869289B2 | Cited by | United States of America | Search report |
| US8908869B2 | Cited by | United States of America | Applicant |
| WO2015003088A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2009193254A1 | Cited by | United States of America | Pre-grant |
| US10146918B2 | Cited by | United States of America | Applicant |
| US8325927B2 | Cited by | United States of America | Search report |
| US9106619B2 | Cited by | United States of America | Search report |
| US10154037B2 | Cited by | United States of America | Search report |
| WO03058485A1 | Cites | World Intellectual Property Organization (WIPO) | Pre-grant |
| US2002018565A1 | Cites | United States of America | Pre-grant |
| US2002026445A1 | Cites | United States of America | Pre-grant |
| US2002138442A1 | Cites | United States of America | Pre-grant |
| US2003126088A1 | Cites | United States of America | Pre-grant |
| US2005289139A1 | Cites | United States of America | Pre-grant |
| US2006080529A1 | Cites | United States of America | Pre-grant |
| US2006095382A1 | Cites | United States of America | Pre-grant |
| US2006107046A1 | Cites | United States of America | Pre-grant |
| US6944776B1 | Cites | United States of America | Pre-grant |
| US7891007B2 | Cites | United States of America | Pre-grant |
11 priority claims, no other members on record
Priority claims11
| Document | Office | Kind | Date |
|---|---|---|---|
| 85299206 | United States of America | P | |
| 85299206 | United States of America | P | |
| 1020070020390 | Republic of Korea | – | |
| 20070020390 | Republic of Korea | A | |
| 20070020390 | Republic of Korea | A | |
| 85985207 | United States of America | A | |
| 1020070020390 | – | – | – |
| 60852992 | – | – | – |
| KR20070020390 | – | – | – |
| US20060852992P | – | – | – |
| US20070859852 | – | – | – |
101 transactions on the USPTO file
Allowed after 4 non-final rejections, 3 final rejections, 2 RCEs and 1 appeal.
- Non-final rejections
- 4
- Final rejections
- 3
- RCEs
- 2
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Appeal Brief FiledAP.B | AP.B | |
| Mail Appeals conf. Proceed to BPAIMAPCP | MAPCP | |
| Pre-Appeals Conference Decision - Proceed to BPAIAPCP | APCP | |
| Request for Pre-Appeal Conference FiledAP.C | AP.C | |
| Notice of Appeal FiledN/AP | N/AP | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Examiner Interview Summary (PTOL - 413)MEXIN | MEXIN | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Transfer Inquiry to GAUTI1050 | TI1050 | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Sent to Classification ContractorPGPC | PGPC | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| Translation of Specification into EnglishTRNSPEC | TRNSPEC | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Cleared by OIPE CSRL194 | L194 | |
| Request for Foreign Priority (Priority Papers May Be Included)RQPR | RQPR | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS |
Numbers
- Publication
- 20080098481
- Publication, DOCDB
- 2008098481
- Publication, EPODOC
- US2008098481
- Application
- 11859852
- Application, DOCDB
- 85985207
- Application, EPODOC
- US20070859852
Titles
- English
- DIGITAL RIGHTS MANAGEMENT PROVISION APPARATUS, SYSTEM, AND METHOD
Patent term adjustment
- A delay
- +553 daysthe office missed an examination deadline
- Applicant delay
- −348 days
- Net adjustment
- 205 days
Classification
- CPC, 11
- G06F21/1073
- G06F21/60
- G06Q20/38215
- H04L63/0428
- H04L2463/101
- H04L9/0825
- H04L2209/08
- H04L2209/603
- G06Q2220/12
- G06Q2220/18
- G06F17/00
- IPC, 2
- H04L9 32
- H04L9 14
- USPC, 2
- 726026000
- 380044000