WO2011126280A2 - Drm을 이용한 광고 컨텐트 갱신 방법 - Google Patents
Drm을 이용한 광고 컨텐트 갱신 방법 Download PDFInfo
- Publication number
- WO2011126280A2 WO2011126280A2 PCT/KR2011/002381 KR2011002381W WO2011126280A2 WO 2011126280 A2 WO2011126280 A2 WO 2011126280A2 KR 2011002381 W KR2011002381 W KR 2011002381W WO 2011126280 A2 WO2011126280 A2 WO 2011126280A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- content
- drm
- advertisement content
- rights object
- rights
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 76
- 230000004044 response Effects 0.000 claims description 21
- 238000005516 engineering process Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 238000007726 management method Methods 0.000 description 7
- 238000004364 calculation method Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
- G06Q20/123—Shopping for digital content
- G06Q20/1235—Shopping for digital content with control of digital rights management [DRM]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/101—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measures for digital rights management
Definitions
- This specification relates to Digital Rights Management (DRM).
- DRM Digital Rights Management
- DRM is a system technology that securely protects and systematically manages the rights to digital content. It prevents illegal copying of content, acquires DRM content and Rights Objects (ROs), creates and distributes DRM content, and uses rights. It provides a set of protection and management systems.
- ROs Rights Objects
- the DRM system may be configured to include a terminal 1, a Rights Issuer (RI) 2, and a Contents Issuer (CI) 3.
- RI Rights Issuer
- CI Contents Issuer
- a general DRM system controls that digital content delivered to the user by the content providers can be used only as much as the right granted to the user.
- the content provider is an entity corresponding to the content issuer 3 and / or the rights issuer 2.
- the content issuer (CI) 3 issues protected content (hereinafter referred to as DRM content) using a specific encryption key so that the content is protected from unauthorized user access, and the rights issuer (RI) 2 Issues a Rights Object (RO) associated with the DRM content to the user.
- DRM content protected content
- RI rights issuer
- RO Rights Object
- such a DRM system may be used as a system for advertising providers to distribute advertising content (advertisement content) to the terminal, and to consume, update, and manage the distributed advertising content.
- the DRM system may control each entity so that the advertisement content is consumed, updated, and managed in association with general content that is not advertisement content, that is, non-advertisement content.
- One embodiment disclosed herein is to propose a method for forcibly consuming advertising content prior to the consumption of non-advertising content.
- an embodiment disclosed herein is to propose a method for updating the advertising content without changing the rights object associated with the non-advertising content.
- an embodiment disclosed in the present specification is to propose a method for setting the rights object to benefit the permissions for the use of the general content based on the consumption of the advertising content.
- a method of updating content may include receiving, by the terminal, data of a specific format including a container and a variable information box from the server, the container including a header, and the variable information box including new advertisement content,
- the header includes a field containing information about first advertising content, wherein the field indicates that the new advertising content is used for updating the first advertising content;
- the one rights object may include constraints such that at least one of the first advertisement content and the new advertisement content is consumed before the non-advertising content is consumed.
- the one embodiment or the other embodiments may include one or more of the following features.
- the data of the specific format may be a DRM content format.
- the field may be an old content ID field.
- the first advertisement content and the new advertisement content may be decrypted based on a content encryption and key in the one right object.
- the rights object may include at least one of a playout constraint and a displayout constraint.
- the method of updating the content may include transmitting, by the terminal, a rights object request message, wherein the rights object request message includes impression data about consumption of the new advertisement content or the first advertisement content. and; And receiving, by the terminal, a rights object response message including a rights object for the non-advertising content.
- the advertisement provider may update the advertisement content directly or by a request of the terminal side.
- the DRM agent may consume non-advertising content in association with the advertising content.
- the advertisement content update method even if only one rights object is issued for use of general DRM content, the advertisement can be continuously updated. Through this, even if the advertisement content is continuously updated, the DRM agent can update the rights object for the general DRM content. It does not have to be issued again.
- the DRM agent may be advantageous in consuming non-advertising content by reflecting the result of the consumption of the advertisement content.
- 1 shows a configuration of a general DRM system.
- FIG. 2 is an exemplary diagram of a DRM system for providing advertisement content.
- FIG. 3 is a diagram illustrating an example of a DCF used in a DRM system.
- FIG. 4 is a flowchart illustrating a ROAP applicable to embodiments disclosed herein.
- FIG. 5A illustrates a rights object applicable to the embodiments disclosed herein
- FIG. 5B illustrates a multipart DCF including advertisement content associated with the rights object.
- FIG. 6A illustrates a rights object applicable to the embodiments disclosed herein
- FIG. 6B illustrates a multipart DCF associated with the rights object.
- FIG. 7 is a diagram illustrating a method for updating advertisement content applicable in embodiments disclosed herein.
- 8A to 8D show a relationship between a rights object and a DCF used in the first embodiment of the advertisement content updating method illustrated in FIG. 7.
- 9A to 9C illustrate a relationship between a DCR and a rights object used to update advertising content without updating the rights object as a second embodiment of the method for updating the advertising content shown in FIG. 7.
- 10A to 10C show a relationship between a rights object and a DCF used in the third embodiment of the advertisement content updating method illustrated in FIG. 7.
- FIG. 11 is a flowchart illustrating a method of acquiring a rights object by reflecting a consumption result of advertisement content as a fourth embodiment of the technology disclosed herein applicable to the embodiments described with reference to FIGS. 7 to 10.
- FIG. 12 is an exemplary view showing a configuration of an apparatus according to the embodiments disclosed herein.
- DRM digital rights management
- present invention is not limited thereto, and the present invention can be applied to all communication systems and methods to which the technical spirit of the technology can be applied, and to systems and methods for protecting digital content.
- first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.
- first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.
- a terminal may be called a user equipment (UE), a device, a mobile equipment (ME), or a mobile station (MS).
- the terminal may be a portable device having a communication function, such as a mobile phone, a PDA, a smart phone, a notebook computer, or a non-portable device such as a PC or a vehicle-mounted device.
- FIG. 2 is an exemplary diagram of a DRM system that provides advertisement content according to embodiments disclosed herein.
- the DRM system includes a terminal 10, a Rights Issuer (RI) 20, a Content Issuer (CI) 30, and an Advertisement Provider ( 30 ').
- RI Rights Issuer
- CI Content Issuer
- 30 ' Advertisement Provider
- the terminal 10 is configured to include a DRM agent 11.
- the DRM agent 11 is an entity existing in the terminal 10, and receives the DRM content 300 from the content issuer (CI) 30 and the rights issuer (RI) 20.
- the permission right refers to the usage methods authorized by the rights issuer (RI) 20 with respect to the DRM content 300
- the restriction refers to a condition that specifically restricts the permission right with respect to the DRM content 300. .
- the DRM content 300 is a protected form of digital work that can be used in accordance with the permission and restrictions contained in the right to use.
- the digital asset protected by the DRM content may include, for example, a ring tones, a screen saver, a background screen, a game, an advertisement content, or a combination thereof.
- the DRM content 300 is transmitted to the DRM agent 11 in the form of a DRM content format (hereinafter referred to as DCF).
- DCF DRM content format
- the terminal 10 may be configured to include a trusted storage 12 which is a storage where unauthorized access from the outside is prohibited.
- the secure storage 12 may be implemented using tamper-resistant hardware or software. Since the secure storage 12 is blocked from access from unauthorized entities other than the DRM agent 11, the DRM agent 11 provides the secure storage 12 with information requiring confidentiality and integrity for management and storage. Can be stored in However, when the DCF is stored in the secure storage 12, it may mean that only portions other than the portions already encrypted and protected with DRM content are stored and managed.
- the DRM system may use a public key infrastructure (PKI). Entities in such a DRM system have a cryptographically paired public key (Puk) and private key (PrK).
- Puk public key
- PrK private key
- the public key PuK and the private key PrK may be certified by a certification authority (CA) (not shown).
- CA certification authority
- the main information in the rights object (RO) is encrypted by a Rights Object Encryption Key (hereinafter referred to as REK), which is a symmetric key, and the REK is a public key (PuK) of a specific terminal (or a specific DRM agent). Is encrypted using). Therefore, only the terminal (or DRM agent) having the private key PrK cryptographically paired with the public key PuK can decrypt the rights object RO.
- REK Rights Object Encryption Key
- the rights object RO includes a REK encrypted by the rights issuer (RI) 20 using the public key PuK of the DRM agent 11.
- the DRM agent 11 has a public key (PuK) and a private key (PrK) of the terminal. Therefore, the DRM agent 11 can decrypt the encrypted REK in the rights object using the private key PrK of the terminal.
- the DRM agent 11 acquires the main information in the rights object RO by using the REK, interprets the permissions and / or constraints included in the rights object RO, and then applies the corresponding information. The use of the DRM content in the terminal 10 is controlled.
- the DRM agent 11 may use the right to use the first DRM content.
- the issuer (RI) 20 requests the first rights object RO.
- the rights issuer (RI) 20 issues the first rights object (RO) associated with the first DRM content.
- the DRM agent 31 may decrypt the first DRM content by using an encryption key in the first rights object RO, and the permission rights and / or restrictions included in the first rights object RO. As a result, the first DRM content is consumed.
- the advertisement content 400 may be protected in the form of DRM content as a form of digital content, and may be transmitted and consumed to the terminal 10.
- the advertisement content 400 refers to a media object having a promotional nature, such as a video advertisement, and may be treated in the same manner as a general media object described herein. That is, the advertisement content 400 is also consumed according to a set of permission rights defined in the rights object, and is represented as DRM content.
- the advertisement provider 30 ′ transmits the advertisement content 400 to the content issuer (CI) 30 and the terminal 10 transmits the advertisement content 400 from the content issuer (CI) 30. ) Can be received.
- the consumption of the advertising content 400 is characterized in that it is used in connection with the general consumption of the DRM content 300 that is not for advertising due to the nature of the content provided for promotion.
- Enforced Advertising Consumption refers to a method of consuming advertising content that is forcibly rendered according to a rule included in a rights object or DCF.
- the present specification discloses a method in which the advertisement content 400 is updated separately from the DRM content.
- the present disclosure discloses a method of obtaining a rights object for which permission rights and / or restrictions for the DRM content 300 are determined based on a result of consumption of the advertisement content 400.
- FIG. 3 is a diagram illustrating an example of a DCF used in the embodiments disclosed herein.
- the DCF 300 is a form of data used by the content issuer (CI) 30 to issue DRM content or to allow the DRM agent 11 to receive and manage the issued DRM content.
- the DRM agent 11 receives the DCF 300 from the content issuer (CI) 30, analyzes it according to the DCF format, and manages the digital content included in the DCF 300 to be consumed. .
- the format of the DCF may be configured to have a different structure according to the characteristics of the DRM content.
- the format of the DCF may be divided into a continuous media profile for streaming content and a discrete media profile for download content.
- the discrete media profile may be a media file format in accordance with ISO 14496-12. While the techniques disclosed herein are described by way of example using DCF with discrete media profiles, the technical idea of protection and management of DRM content is not limited thereto and may be applied to continuous media profiles and other formats of DCF. .
- the DCF is for DRM content that is downloaded and consumed, and represents a format conforming to an ISO-based discrete media profile.
- the DCF 300 includes a fixed length DCF header 310, one or more DRM containers 320, 330, 340, and a variable DRM information box. information box 350).
- the fixed length DCF header 310 represents file type information defined in an ISO-based media file format, and thus may be configured to indicate brand and version information of the DCF 300.
- the fixed length DCF header 310 may include brand information 'odcf' and version information '2' to indicate that the file conforms to the DCF format of OMA DRM 2.x.
- the one or more DRM containers 320, 330, 340, etc. may be configured to include DRM content and header information thereof.
- the first DRM container 320 immediately following the fixed length DCF header 310 will be described.
- the first DRM container 320 may be configured to include an OMA DRM header 321 and a content object 327.
- the OMA DRM header 321 may include a DCF headers 322, a common header box 323, and a user-data box 324.
- the DCF header 322 refers to a DCF header for the DRM container 320.
- the DCF header 322 includes brand information about the DRM container 320 and the like.
- the general header 323 stores information about the content object 327 included in the first DRM container 320 (specifically, information about DRM content in the content object 327). Include. Information included in the general header 323 is shown in Table 1.
- the Version field indicates the version of the standard document that defines the DCF format.
- the EncryptionMethod field indicates an algorithm used to encrypt DRM content in the content object 327 and may indicate, for example, an encryption method of the AES block encryption algorithm.
- the PaddingScheme field indicates how the last block is padded while using the block encryption algorithm.
- the PlaintextLength field indicates the length of digital content before encryption.
- the ContentIDLength field indicates the length of the ContentID field
- the RightsIssuerURLLength field indicates the length of the RightsIssuerURL field
- the TextualHeadersLength field indicates the length of the TextualHeaders field.
- the TextualHeaders field indicates additional information of the digital content in the form of 'name: value' pair. Additional information that may be included in the TextualHeaders field includes a Silent header, Preview header, ContentURL header, ContentVersion header, Content-Location header, ProfileName header.
- the ExtendedHeaders field contains extended information about the digital content.
- the ExtendedHeaders field may include GroupID information indicating an identifier of the specific content group when the digital content corresponds to a part of a specific content group.
- the ExtendedHeaders field may include an OldContentID field used in some of the embodiments disclosed herein.
- the OldContentID field represents an identifier of advertisement content to be updated, which will be described later with embodiments.
- the content object 327 includes encrypted digital content, that is, DRM content.
- the DRM content is encrypted by the content issuer (CI) 30 using an algorithm indicated by the EncryptionMethod field of the generic header 323.
- the DRM agent 11 obtains a rights object (RO) associated with the DRM content with reference to a ContentID included in the general header 323, and encrypts the DRM content from the associated rights object (RO).
- RO rights object
- the advertisement content used in the embodiments disclosed herein may be included in the content object 327.
- the DRM agent 11 is associated with a method of updating a previous advertisement content using the advertisement content included in the content object 327. The advertising content updating method will be described later.
- the variable DRM information box 350 includes information editable by the terminal 10.
- Data that may be included in the variable DRM information box 350 may include transaction tracking information, rights object information, user data information, and content ID sub-box. There is).
- the variable DRM information box 350 is ignored in the DCF hash calculation process.
- the DCF hash may be included as a field in a rights object (RO) associated with the DRM content or as a parameter in a protocol for obtaining the associated rights object (RO) in order to protect the integrity of the DCF.
- RO rights object
- the integrity of the variable DRM information box 350 is not protected.
- the DCF variable DRM information box 350 may not be included in a streamable packetized DCF (PDCF).
- PDCF streamable packetized DCF
- One variable DRM information box 350 is used for one DCF.
- advertisement content is included in the variable DRM information box 350.
- the advertisement content may be included in user data information in the variable DRM information box 350.
- a multipart DCF refers to a DCF including a plurality of DRM containers. That is, when the DCF 300 includes a second DRM container 330 or more DRM containers 340 in addition to the first DRM container 320, the DCF 300 is a multipart DCF. In the case of a multipart DCF, the media type of the digital content included in each DRM container may be different.
- each DRM container may have the same structure as the first DRM container 320 as described above. Therefore, the general header of each DRM container includes the ContentID of digital content included in the content object of each DRM container. In addition, the DRM agent 11 is associated with each digital content included in one multipart DCF.
- each DRM container of the multipart DCF may be configured to include advertisement content.
- the rights object (RO) includes permissions, constraints, and identification information for the associated DRM content that the Rights Issuer (RI) 20 has granted to the use of the DRM content.
- the permission right for the DRM content refers to a usage method authorized by the rights issuer (RI) 20 so that the DRM agent 11 can consume the DRM content.
- the constraints on the DRM content refer to a condition that specifically restricts usage methods of the DRM content according to the permission.
- the rights object RO may be transmitted or stored in the form of a Rights Object Container.
- the rights object container may be represented by document encoding rules in machine readible form.
- the rights object container may be represented by a Rights Expression Language (REL), and an example of such a right expression language may be an extensible Markup Language (XML) or a sub language thereof.
- REL Rights Expression Language
- XML extensible Markup Language
- ODRL Open Digital Rights Language
- the rights object RO may be represented by a REL conforming to a mobile profile of ODRL v1.1.
- each right item included in the rights object RO may be expressed using elements of the REL.
- the rights items in the rights object RO may be classified by their functions.
- Table 2 describes a functional model of elements that may be included in a rights object (RO) used in the embodiments disclosed herein.
- the Foundation model includes a ⁇ rights> element that corresponds to the top-level element of the rights object.
- the foundation model serves as a starting point for combining the agreement model and the context model below.
- the context model includes ⁇ version> and ⁇ uid> elements. Elements of the context model are included in the ⁇ rights> element, the ⁇ asset> element, the ⁇ individual> element, the ⁇ system> element, and the ⁇ inherit> element, and display meta information about each element.
- the ⁇ context> element included as a sub-element of the ⁇ rights> element may include identification information of the rights object.
- the agreement model includes elements indicating identification information about DRM content and elements indicating permission rights and constraints associated with the DRM content.
- the agreement model may be expressed in detail using a permission model and a constraint model. That is, the method and limitations that can consume the DRM content by using an element corresponding to the permission model and an element corresponding to the constraint model are defined.
- the rights object RO may include a ⁇ rights> element
- the ⁇ rights> element may include a ⁇ context> element and an ⁇ agreement> element.
- the ⁇ context> element may include identification information of the rights object
- the ⁇ agreement> element may include an ⁇ asset> element including information about DRM content associated with the rights object, and the associated DRM content. It may contain a ⁇ permission> element that contains the permissions.
- the permissions that can be represented by the rights object RO include ⁇ play>, ⁇ display>, ⁇ execute>, ⁇ print>, ⁇ export> and ⁇ access> elements.
- Elements corresponding to the Requirement model include ⁇ tracked>, ⁇ access-code>, ⁇ AdvertisementPolicy>, ⁇ playout>, ⁇ displayout>, ⁇ executeout>, ⁇ enforcement-duration>, and ⁇ enforcement-count>.
- Elements included in the Requirement model are those that represent certain prerequisites that must be pre-empted in order to obtain associated permissions.
- the DRM agent 11 may consume the permission expressed by the ⁇ permission> after consuming the specific advertisement content referred to by the element of the requirement model. Can be obtained.
- the Constraint model includes ⁇ count>, ⁇ timed-count>, ⁇ datetime>, ⁇ interval>, ⁇ accumulated>, ⁇ individual>, ⁇ system>, ⁇ discrete>, ⁇ max-resolution>, ⁇ DeviceNumThresh>, ⁇ execute -level> elements.
- the security model may include elements for ensuring the confidentiality of the DRM content.
- the DRM content included in the content object in the DCF is encrypted using a content encryption key (hereinafter referred to as a CEK), and the CEK may be included in the rights object in a form encrypted by the REK.
- REK is a key used to encrypt items in the rights object (RO) that need to be securely stored, such as CEK.
- the REK may be transmitted in an encrypted state using the public key PuK of the DRM agent 11 to ensure confidentiality during transmission from the rights issuer (RI) 20 to the DRM agent 11. have.
- the REK may be managed and stored using the secure storage 12.
- the security model may include elements for ensuring the integrity (integrity) of the association between the DRM content and rights objects.
- the ⁇ digest> element may indicate a DCF hash value for the DRM content referenced by the ⁇ uid> element in the same ⁇ asset> element.
- the ⁇ digest> element may include a ⁇ DigestMethod> element representing a hash algorithm and a ⁇ DigestValue> element representing a hash value.
- the DRM agent 11 may use a separate data format to manage the permissions and / or restrictions granted to the DRM content associated with the rights object (RO). That is, the DRM agent 11 may manage the rights object RO by using right metadata, state information, and the like. In addition, the DRM agent 11 may store the rights object in the form of a rights object container for future use.
- RO rights object
- the rights metadata includes a rights object version, a rights alias, a rights holder's ID, a rights holder's address, and a rights holder's time information. It may include data.
- the state information refers to information representing the current state of each stateful usage right.
- the stateful usage right refers to a usage right in which state information is correctly maintained so that permission rights and / or constraints can be managed accurately in the terminal. Examples of stateful usage rights managed through state information include remaining counts, intervals, and start dates.
- the DRM agent 11 may manage and store various types of information about the rights object RO using the secure storage 12.
- ROAP Rights Object Acquisition Protocol
- the rights issuer (RI) 20 may transmit a trigger message, for example, a trigger message for acquiring a rights object, or a ROAP trigger message, to the terminal 100 to provide a rights object (Rights Object). S1).
- a trigger message for example, a trigger message for acquiring a rights object, or a ROAP trigger message
- the trigger message may be transmitted when the rights issuer (RI) 20 requests delivery of a rights object (RO) for a specific content from a user through a method such as web browsing.
- RI rights issuer
- IMSI and information about the terminal 10, for example, a device ID may be delivered to the rights issuer (RI) 20.
- the trigger message may be in the following form.
- the rights issuer (RI) 20 may generate a rights object (RO) for the specific content.
- the creation of the rights object RO may be performed after receiving the rights object request message from the terminal 10 later.
- the DRM agent 11 of the terminal 10 upon receiving the trigger message, the DRM agent 11 of the terminal 10 generates a rights object request message to request the rights object RO to the rights issuer (RI) 20 (S2). .
- the rights object request message includes the ID of the terminal.
- the rights object request message includes the rights issuer's ID, device number, request time, RO information, and extension parameters.
- the rights object request message includes a signature.
- the rights object request message containing the signature requires integrity.
- the rights object request message includes an HMAC value, which ensures that the rights object request message has not been altered while being transmitted.
- the DRM agent 11 transmits the rights object request message to the rights issuer (RI) 20 (S3).
- the rights issuer (RI) 20 generates a rights object response message, for example, an RO response message (S4).
- the rights issuer (RI) 20 transmits the rights object response message, for example, a RO Response message, to the DRM agent 11 (S5).
- the rights issuer (RI) 20 includes the previously generated or currently generated rights object (RO) in the form of a protected rights object (protected RO) in the rights object response message.
- the rights object response message includes the signature of the rights issuer (RI) 20.
- the rights object request message and the rights object response message follow the protocol of DRM 2.0 or the protocol of DRM 2.1.
- the advertisement content may be treated in the same way as the DRM content, but an additional control method is required in order to provide a function for consuming the advertisement prior to the consumption of the DRM content.
- the association of such advertisement content and non-advertisement content may be implemented through a relationship between a rights object (RO) and DRM content.
- RO rights object
- FIG. 5 illustrates a multipart DCF including a rights object applicable to the embodiments disclosed herein and advertisement content associated with the rights object.
- FIG. 5A illustrates a rights object 2100
- FIG. 5B illustrates a DCF 3100 associated with the rights object 2100.
- the DCF 3100 is configured in the form of a multipart DCF and includes a DRM container 3120 including non-advertising content 3127 and a DRM container 3130 including ad content 3137.
- the rights object 2100 includes ⁇ rights> elements 2110 corresponding to a foundation model.
- An element (not shown) of a context model indicating an identifier of the rights object 2100 may be included below the ⁇ rights> element 2110.
- ⁇ asset> elements indicating identification information of the DRM content included in the DCF
- ⁇ permission> and ⁇ constraint indicating the permission and constraints associated with the DRM content.
- ⁇ Agreement> element (not shown) that includes> elements.
- the ⁇ assetID> element 2120 below the ⁇ agreement> element indicates an identifier of the DRM content 3127 that is non-advertising content included in the DCF 3100, and the ⁇ permission> element 2130. Indicates the permissions and / or constraints associated with the DRM content 3127 along with its underlying ⁇ constraint> element 2132.
- the identifier of the DRM content 3127 may be included in the DCF header 3121 in the DRM container 3120.
- the rights object 2100 includes elements 21321, 21321a, and 21321b of the requirement model indicating that the DRM content 3127 needs to be consumed before consumption. That is, the ⁇ pre-access> element 21321, which is an element of the requirement model, indicates that the DRM content 3137, which is the advertisement content indicated by the ⁇ assetID> element 21321a, must be consumed first.
- the advertisement content 3137 may be delivered to the DRM agent 11 in the form of a multipart DCF 3100.
- the advertisement content 3137 may be included in the multipart DCF 3100 in a plain text or encrypted state.
- a separate rights object (not shown) for decrypting the advertisement content 3137 may be required.
- FIG. 6 is a diagram illustrating a relationship between a multipart DCF and a rights object applicable to the embodiments disclosed herein.
- FIG. 6A illustrates a rights object 2200
- FIG. 6B illustrates a multipart DCF 3200 associated with the rights object 2200
- the multipart DCF 3200 is configured to include a DRM container 3220 containing non-advertising content 3227 and DRM containers 3230 and 3240 respectively containing ad contents 3237 and 3247. have.
- the rights object 2200 selects and consumes any one of a plurality of advertisement contents 3237, 3247, etc. included in the multipart DCF 3200 of FIG. 6B. It includes permits and / or restrictions that allow for such provision.
- the rights object 2200 includes a ⁇ rights> element 2210 corresponding to a foundation model.
- An element (not shown) of a context model indicating an identifier of the rights object 2200 may be included below the ⁇ rights> element 2210.
- ⁇ asset> elements indicating identification information of the DRM content included in the DCF
- ⁇ permission> and ⁇ constraint indicating the permission and constraints associated with the DRM content.
- ⁇ Agreement> element (not shown) that includes> elements.
- the ⁇ assetID> element 2220 below the ⁇ agreement> element indicates an identifier of the DRM content 3227 that is non-advertising content included in the DCF 3200, and the ⁇ permission> element 2230. Indicates the permissions and / or constraints associated with the DRM content 3227 with its underlying ⁇ constraint> element 2232.
- the identifier of the DRM content 3227 may be included in a DCF header 3221 in the DRM container 3220.
- the rights object 2200 includes elements 22321, 22321a, 22321b, 22321c, and 22321d of the requirement model indicating that the DRM content 3227 should be consumed before consumption.
- the ⁇ pre-access> element 22321 which is an element of the requirement model is a DRM content 3237 which is advertisement contents indicated by the ⁇ assetID> elements 22321b, 22321c, and 22321d displayed under the ⁇ choice> element 22321a. , 3247, etc.) should be consumed first.
- advertisement contents 3237, 3247, and the like may be delivered to the DRM agent 11 in the form of a multipart DCF 3200.
- the advertisement contents 3237, 3247, etc. may be included in the multipart DCF 3200 in plain text or encrypted state.
- a separate rights object (not shown) for decrypting the advertisement contents 3237 and 3247 may be required.
- FIG. 7 is a diagram illustrating an advertisement content management method that can be employed in the embodiments disclosed herein. Hereinafter, referring to FIG. 7, a method of distributing, consuming, and updating advertisement content is disclosed.
- the terminal 10 selects DRM content (non-advertising content) and selects to consume advertising content for the DRM content (S10).
- the terminal 10 accesses the content issuer (CI) 30 to search for and select the DRM content (S11).
- the terminal 10 may select an option of consuming (ie, playing out or displaying) advertisement content before consuming the retrieved DRM content.
- the terminal 10 may allow the advertisement provider (not shown) to update the advertisement content. Thereafter, the content issuer (CI) 30 notifies the right issuer (RI) 20 of the selection of the terminal 10 (S15).
- the DRM agent 11 of the terminal 10 obtains a right object necessary for consuming the DRM content by requesting the rights issuer (RI) 20 (S20).
- the procedure for requesting the rights object is performed by the rights object acquisition protocol (ROAP) S1 to S5 described with reference to FIG. 3.
- the DRM agent 11 obtains the necessary rights object by transmitting the rights object request message to the rights issuer (RI) 20 and receiving a rights object response message including the rights object in response thereto. .
- the rights object as described above, the permission authority prescribed to play the advertising content before the rights issuer (RI) 20 consumes the DRM content based on the selection of the terminal 10 and It is created to include a constraint.
- the rights object may include permission rights and constraints such as compulsory reproduction of the advertisement content, the number of advertisement contents to be reproduced, reproduction rules, identifiers of specific advertisement contents to be reproduced, and the like.
- the DRM agent 11 receives the DRM content and the advertisement content (S30).
- the DRM content and the advertisement content can be received by various methods.
- the DRM content is included in the DCF and received. Accordingly, the DRM agent 11 receives the DCF including the selected content in a manner that includes the advertisement content together (S31), or receives the DCF including only the content (S33) and, if necessary, the advertisement content.
- the DCF including a may be separately received (S35).
- it may receive a DCF including instructions on how the advertisement content should be forcibly played.
- the DRM agent 11 consumes the DRM content according to the permission right and restrictions expressed in the rights object (S40).
- the DRM agent 11 interprets the rights object in which the correlation between the advertisement content and the DRM content is expressed.
- the DRM agent 11 may consume the DRM content first after consuming the advertisement content according to the analysis result.
- the DRM agent 11 may receive a separate rights object for the advertisement content and consume the advertisement content according to the permission rights and restrictions defined in the received separate rights object. have.
- the DRM agent 11 performs a procedure for updating the advertising content (S50).
- the procedure for updating the advertisement content is to replace the already received advertisement content with newly received advertisement content.
- the DRM agent 11 receives new advertisement content (S51).
- the advertisement content may be updated by the content issuer (CI) 30 or at the request of the DRM agent 11.
- the receiving of the new advertisement content may be performed by a method of receiving a DCF including the new advertisement content by the request of the DRM agent 11 or by pushing the content issuer (CI) 30 ( It may be performed by the method of receiving the new advertisement content that is pushed) or by the method of receiving the new advertisement content by the DRM agent 11 when the condition of device management by scheduling is satisfied.
- CI content issuer
- the DRM agent 11 performs a process of checking whether there is an advertisement content to be updated by comparing the received advertisement content with the new advertisement content (S53).
- the previously received advertisement content is replaced by using the new advertisement content (S55).
- FIG. 8 is a diagram illustrating a method of updating advertisement content according to a first embodiment of the technology disclosed herein. Referring to FIG. 8, a method of updating the advertisement content already received by the DRM agent 11 with new advertisement content will be described.
- the DRM agent 11 has already received and stored the multipart DCF 3400 in the storage 12.
- the rights object 2400 associated with the DRM content 3227 included in the multipart DCF 3400 is also received and stored in the storage 12.
- the already received right object 2400 includes a ⁇ rights> element 2410 corresponding to a foundation model.
- the ⁇ rights> element 2410 may include an element (not shown) of the context model representing the identifier of the rights object 2400.
- ⁇ asset> elements indicating identification information of the DRM content included in the DCF
- ⁇ permission> and ⁇ constraint indicating the permission and restrictions associated with the DRM content.
- ⁇ Agreement> element (not shown) that includes> elements.
- the ⁇ o-ex: asset> element 2420 below the ⁇ agreement> element indicates an identifier of the DRM content 3227, which is non-advertising content included in the DCF 3400.
- permission> element 2450 together with its underlying ⁇ constraint> element 2452, indicates the permissions and / or constraints associated with the DRM content 3425.
- the identifier of the DRM content 3227 may be included in a DCF header 341 in the DRM container 3420.
- the rights object 2400 includes elements 224521, 24521a, and 24521b of the requirement model indicating that the DRM content 3427 should be consumed before consumption. That is, the ⁇ pre-access> element 24221, which is an element of the requirement model, indicates that the DRM content 3437, which is the advertisement content indicated by the ⁇ assetID> element 224521, should be consumed first.
- the rights object 2400 includes a ⁇ digest> element 24221b including a hash value of the DCF for integrity protection of the DCF 3400. In the first embodiment, since the DCF hash value is changed in a subsequent advertisement content update procedure, the value of the ⁇ digest> element 24221b in the rights object 2400 including the same will also be changed to another value.
- the method (S50) for updating the advertisement content by the DRM agent 11 is as follows.
- the DRM agent 11 receives a new rights object 2400 ′ and a new multipart DCF 3400 ′ shown in FIGS. 8C and 8D (S51).
- the new rights object 2400 ′ and the new multipart DCF 3400 ′ may be received together or separately.
- the DRM agent 11 checks whether there is advertisement content to be updated in the storage 12 (S53).
- the checking process may be performed by a method of determining whether identification numbers of the DRM content 3227 in the already received multipart DCF 3400 and the new multipart DCF 3400 'are the same.
- the DRM agent 11 forcibly consumes the updated advertisement content 3437 'according to permission rights and restrictions included in the new rights object 2400'. shall.
- the DRM agent 11 determines whether the two rights objects 2400 and 2400 'are associated with the same DRM content and checks whether there is advertisement content to be updated in the storage 12 (S53). , 2400 '), it may be determined whether there is an element of advertisement content among elements of the requirement model.
- step S55 the advertisement content 3437 defined in FIG. 3 is replaced with the advertisement content 3437 'defined in the new rights object 2400'.
- FIG. 9 is a diagram illustrating a method of updating advertisement content according to a second embodiment of the technology disclosed herein.
- a method of updating, by the DRM agent 11, only the advertising content that has already been received with the new advertisement content without updating the rights object will be described with reference to FIG. 9.
- the DRM agent 11 has already received the DCF 3500 and stored in the storage 12. It is assumed that the rights object 2500 associated with the DRM content 3525 included in the DCF 3500 is also received and stored in the storage 12.
- the already received right object 2500 includes a ⁇ rights> element 2510 corresponding to a foundation model.
- An element (not shown) of a context model indicating an identifier of the rights object 2500 may be included below the ⁇ rights> element 2510.
- ⁇ asset> elements indicating identification information of the DRM content included in the DCF
- ⁇ permission> and ⁇ constraint indicating the permission and restrictions associated with the DRM content.
- ⁇ Agreement> element (not shown) that includes> elements.
- the ⁇ o-ex: asset> element 2520 below the ⁇ agreement> element indicates an identifier of the DRM content 3525 that is non-advertising content included in the DCF 3500
- the identifier of the DRM content 3525 may be included in the DCF header 3351 in the DRM container 3520.
- the rights object 2500 includes elements 252521 and 25521a of a requirement model indicating that the DRM content 3525 needs to be consumed before consumption. That is, the ⁇ pre-access> element 252521, which is an element of the requirement model, indicates that the DRM content 3575, which is the advertisement content referred to by the ⁇ AdRef> element 252521, should be consumed first.
- the method (S50) for updating the advertisement content by the DRM agent 11 is as follows.
- the DRM agent 11 receives a new DCF 3500 'shown in FIG. 9C (S51).
- the DRM content 3525 'included in the new DCF 3500' may be configured to be the same as the DRM content 3525 included in the previously received DCF 3500.
- the DRM agent 11 checks whether there is advertisement content to be updated in the storage 12 (S53).
- the verification process may be performed by a method of confirming whether advertisement content matching the identifier of the advertisement content to be updated included in the new DCF 3500 ′ exists in the storage 12. That is, the identifier of the advertisement content to be updated indicates that the new advertisement content 3575 'is used for updating the advertisement content 3575 to be updated.
- the update process is performed by replacing the advertisement content 3575 to be updated with the new advertisement content 3575 '. (S55).
- the DRM agent 11 in order for the DRM agent 11 to consume the DRM content 3525 ', the DRM agent 11 must forcibly consume the updated advertisement content 3575' according to the permission and restrictions included in the rights object 2500. do.
- the DRM contents 3525 and 3527 ' are not changed even when the new DCF 3500' is received. There is no need to newly receive the rights object 2500.
- the advertisement contents 3557 and 3557 ' may include a variable DRM information box 3550 and 3550' of the DCF 3500 and 3500 '. May be included in each. Accordingly, the new DF information box 3550 'of the new DCF 3500' may include new advertisement content 3575 '.
- variable DRM information boxes 3550 and 3550 are ignored in the DCF hash calculation in the second embodiment, unlike other embodiments, the hash value of the DCF is not maintained in the element of the requirement model in the rights object 2500. You don't have to.
- the identifier of the advertisement content to be updated may be included in a DRM container including the DRM content 3525 'of the new DCF 3500'.
- the identifier of the advertisement content to be updated may be represented by an 'OldContentID' field and may be included in the DCF header 3351 of the DRM container. More specifically, the 'OldContentID' field, which is an identifier of the advertisement content to be updated, may be included in an extended header field in the general header of the DCF header 3351.
- the 'OldContentID' field may include a ContentID field indicating an identifier of the advertisement content to be updated and a ContentIDLength field indicating a length of the ContentID field.
- the new DCF 3500 ' may be a DCF that does not include DRM content but includes only the variable DRM information box 3550' that includes the new advertisement content 3557 '.
- the modified embodiment of the second embodiment may include the DRM content 3525 'included in the new DCF 3500' in the second embodiment of the DRM content 3250 included in the previously received DCF 3500. It is similar to the case configured to be the same as 3527). That is, according to the second embodiment and the embodiment, since the DRM content 3525 is not changed, other steps may be performed in the same manner as the second embodiment.
- FIG. 10 is a diagram illustrating a method of updating advertisement content according to a third embodiment of the technology disclosed herein.
- a method of updating, by the DRM agent 11, only another already received advertisement content in the rights object with new advertisement content without updating the rights object will be described with reference to FIG. 10.
- the DRM agent 11 has already received and stored the multipart DCF 3600 in the storage 12.
- the rights object 2600 associated with the DRM content 3627 included in the multipart DCF 3600 is also received and stored in the storage 12.
- the already received right object 2600 includes a ⁇ rights> element 2610 corresponding to a foundation model.
- An element (not shown) of a context model representing an identifier of the rights object 2600 may be included below the ⁇ rights> element 2610.
- ⁇ asset> elements indicating identification information of the DRM content included in the DCF
- ⁇ permission> and ⁇ constraint indicating the permission and constraints associated with the DRM content.
- ⁇ Agreement> element (not shown) that includes> elements.
- the ⁇ asset> element 2620 below the ⁇ agreement> element indicates an identifier of the DRM content 3627 that is non-advertisement content included in the multipart DCF 3600, and indicates a ⁇ requirement> element ( 2630 represents a rule of enforced advertising, with the ⁇ permission> element 2640 along with its underlying ⁇ constraint> element 2641 and the permissions and / or constraints associated with the DRM content 3627. Indicates.
- the identifier of the DRM content 3627 may be included in a DCF header 3621 in the DRM container 3620.
- ⁇ expire> element 2631 indicating a period in which the DRM content 3627 expires according to a compulsory advertisement consumption rule, and an address of a server that can be accessed for continuous use.
- ⁇ uri> element 2632 that represents.
- the rights object 2600 includes elements 26411, 26411a, and 26411b of a requirement model indicating that the DRM content 3627 should be consumed before consumption. That is, the ⁇ pre-access> element 26411, which is an element of the requirement model, indicates that the DRM content 3637, which is the advertisement content indicated by the ⁇ assetID> element 26411a, should be consumed first. Also, the rights object 2600 includes a ⁇ digest> element 26411b including a hash value of the DCF to protect the integrity of the DCF 3600. In the third embodiment, since the DCF hash value is changed in a subsequent advertisement content update procedure, the value of the ⁇ digest> element 26411b in the rights object 2600 including the same will also be changed to another value.
- the method (S50) for updating the advertisement content by the DRM agent 11 is as follows.
- the following procedure for updating the advertisement content may be performed when the period indicated by the ⁇ expire> element 2631 below the ⁇ requirement> element 2630 expires.
- the DRM agent 11 receives the new DCF 3600 'shown in FIG. 10C (S51).
- the DRM content 3627 'included in the new DCF 3600' may be configured to be the same as the DRM content 3627 included in the previously received DCF 3600.
- the DRM agent 11 checks whether there is advertisement content to be updated in the storage 12 (S53).
- the verification process may be performed by a method of confirming whether advertisement content corresponding to the identifier of the advertisement content to be updated included in the new DCF 3600 'exists in the storage 12.
- the update process is performed by replacing the advertisement content to be updated 3637 with the new advertisement content 3637 '. (S55).
- the DRM agent 11 receives the new rights object (not shown) and updates the updated advertisement content 3557' according to the permission rights and restrictions included therein. Must be forcibly consumed.
- the new DCF 3600 ' may not be a multipart DCF, but may be a DCF including only a DRM container including advertisement content.
- the DRM content 3627 'included in the new DCF 3600' may include the DRM content (included in the previously received DCF 3600). Similar to the case configured to be the same as 3627). That is, according to the third embodiment and the embodiments, since the DRM content 3627 is not changed, other steps may be performed in the same manner as in the third embodiment.
- FIG. 11 is a flowchart of obtaining a rights object by reflecting a consumption result of advertisement content as a fourth embodiment of the technology disclosed herein.
- the fourth embodiment relates to the DRM agent 11 trying to consume non-advertising content after the advertisement content is updated by the previous embodiments. That is, when the DRM agent consumes each updated advertisement content, when the DRM agent wants to obtain the rights object for the non-advertising content again, the method provides a benefit to the consumption of the non-advertising content based on the consumption of the advertisement content. .
- the DRM agent 11 updates the impression data when the advertising content is consumed.
- the impression data is information indicating that consumption of the advertisement content is completed by the user of the terminal 10.
- the fourth embodiment may be performed through a rights object acquisition protocol using the impression data.
- the impression data should be stored in the DRM agent 11, ie in the secure repository 12, and should be updated when the DRM agent 11 plays the advertisement content.
- the DRM agent 11 downloads the DRM content with the payment option related to the reproduction information of the advertisement content, the DRM agent 11 uses the impression data to the rights issuer (RI) 20. To request permission to the DRM content.
- RI rights issuer
- the DRM agent 11 receives the advertisement content and the DRM content (non-advertisement content) according to the embodiments described above (S10 to S50). That is, according to the above-described embodiments, the DRM agent 11 may update the new advertisement content after receiving the advertisement content.
- the rights object for the DRM content may be received through the ROAP described with reference to FIG. 4. However, in a subsequent step, the procedure of acquiring a new right object associated with the DRM content based on the consumption result of the advertisement content may continue.
- the DRM agent 11 consumes the advertisement content, and updates impression data based on the consumption result (S60).
- the impression data may be data in the form shown in Table 4 below.
- the form of the impression data may be the same as the rawMeteringReportData format.
- the DRM agent 11 obtains a rights object for the DRM content from the rights issuer (RI) 20 based on the impression data (S70).
- the rights object acquisition method based on the impression data is different from the rights object acquisition method described with reference to FIG. 4.
- the DRM agent 11 generates a rights object request message to request the rights object RO to the rights issuer RI (S72).
- the rights object request message includes the impression data in addition to the ID of the terminal, the ID of the rights issuer, a device number, a request time, a RO information, and an extension parameter.
- the rights object request message includes a signature.
- the impression data in the rights object request message may be displayed as follows.
- the DRM agent 11 transmits the rights object request message to the rights issuer (RI) 20 (S73).
- the rights issuer (RI) 20 generates a rights object response message, for example, an RO Response message (S74). Subsequently, the rights issuer (RI) 20 transmits the rights object response message, for example, a RO Response message, to the DRM agent 11 (S75).
- the rights issuer (RI) 20 grants permission based on the policy of the impression data and rights issuer (RI) 20. Can be issued. If the impression data is not sufficient, the rights issuer (RI) 20 should send an RO response message with an error code.
- the UnableToDecryptAdvertisementImpressionData response message is an InsufficientAdvertisementImpressionData response message when the RI fails to decrypt the impression data, and is a response message sent when the impression data is not sufficient.
- the DRM agent 11 may consume the DRM content by obtaining a rights object reflecting the impression data from the RO Response message received from the rights issuer (RI) 20.
- FIG. 12 is an exemplary view showing a configuration of an apparatus according to the embodiments disclosed herein.
- the terminal 10 includes a controller 17, a storage means 18, and a transceiver 19.
- the controller 17 is configured to be connected to the storage means 18 and the transceiver, to execute the DRM agent, and to play non-advertisement content and advertisement content. In this case, the controller 17 may limit the reproduction of the non-ad content and the advertisement content according to the rights object RO.
- the storage means 18 respectively store a DRM agent, non-advertising content and advertisement content, and a rights object for the content.
- the transceiver 19 receives non-advertising and advertisement content from the content issuer (CI) 30, and receives a rights object (RO) from the rights issuer (RI) 20.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Multimedia (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Marketing (AREA)
- Finance (AREA)
- Economics (AREA)
- Computing Systems (AREA)
- Development Economics (AREA)
- Accounting & Taxation (AREA)
- Storage Device Security (AREA)
- Information Transfer Between Computers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
필드 | 설명 |
Version | Common Headers Version |
EncryptionMethod | Encryption method |
PaddingScheme | Padding type |
PlaintextLength | Plaintext content length in bytes |
ContentIDLength | Length of ContentID field in bytes |
RightsIssuerURLLength | Rights Issuer URL field length in bytes |
TextualHeadersLength | Length of the TextualHeaders array in bytes |
ContentID | Content ID string |
RightsIssuerURL | Rights Issuer URL string |
TextualHeaders | Additional headers as Name:Value pairs |
ExtendedHeaders | Extended headers boxes |
Foundation 모델 | 권리항목들의 기본이 되는 엘리먼트들. |
Agreement 모델 | Asset에 해당하는 DRM 컨텐트에 대하여 허가된 권리항목들을 표현하는 엘리먼트들. |
Context 모델 | 항목들에 대한 메타 정보를 표현하는 엘리먼트들. 상기 foundation 모델, 상기 agreement 모델, 및 constraint 모델에 대하여 부가적인 정보를 표시함으로써 이들을 확장. |
Permission 모델 | DRM 컨텐트에 대하여 허가된 권리항목들을 자세하게 표현한 엘리먼트들. Constraint 모델과 함께 DRM 컨텐트의 소비를 자세하게 제어. |
Constraint 모델 | 하나의 permission 엘리먼트와 연관되어 DRM 컨텐트의 소비를 자세하게 제어하기 위한 엘리먼트들. |
Requirements 모델 | 연관된 허가권한들을 획득하기 위하여 선결되어야 하는 특정 선행 조건들을 나타내는 엘리먼트들. |
Inheritance 모델 | 부(parent) 권리객체로부터 상속되는 허가권한 및 제약들을 표현하는 엘리먼트들. |
Security 모델 | CEK의 기밀성, DRM 컨텐트 및 권리객체들 간의 연관성에 대한 무결성, 권리객체의 무결성과 인증 등을 제공하는 엘리먼트들. |
Claims (6)
- 컨텐트를 갱신하는 방법으로서,단말이 컨테이너 및 가변 정보 박스를 포함하는 특정 포맷의 데이터를 서버로부터 수신하는 단계와, 상기 컨테이너는 헤더를 포함하고, 상기 가변 정보 박스는 새로운 광고 컨텐트를 포함하고, 상기 헤더는 제1 광고 컨텐트에 대한 정보를 포함하는 필드를 포함하고, 상기 필드는 상기 새로운 광고 컨텐트가 상기 제1 광고 컨텐트의 갱신을 위하여 사용됨을 나타내고;상기 단말이 상기 제1 광고 컨텐트에 대한 정보와 매칭되는 정보가 있는지 여부를 확인하는 단계와, 상기 제1 광고 컨텐트는 상기 특정 포맷의 데이터 내에 비광고 컨텐트와 함께 포함되고; 그리고상기 확인 결과 매칭되는 정보가 발견되면 상기 특정 포맷의 데이터 내의 상기 제1 광고 컨텐트를 상기 새로운 광고 컨텐트로 교체하는 단계를 포함하되,상기 제1 광고 컨텐트 및 상기 새로운 광고 컨텐트는 하나의 권리객체에 기초하여 소비될 수 있고,상기 하나의 권리객체는 상기 비광고 컨텐트를 소비하기 전에 상기 제1 광고 컨텐트 및 새로운 광고 컨텐트 중 적어도 하나가 소비되도록 하는 제약사항들을 포함하는 것을 특징으로 하는 컨텐트 갱신 방법.
- 제1 항에 있어서, 상기 특정 포맷의 데이터는 DRM 컨텐트 포맷인 것을 특징으로 하는 컨텐트 갱신 방법.
- 제1 항에 있어서, 상기 필드는 old content ID 필드 인 것을 특징으로 하는 컨텐트 갱신 방법.
- 제1 항에 있어서, 상기 제1 광고 컨텐트 및 상기 새로운 광고 컨텐트는 상기 하나의 권리객체 내의 컨텐트 암호와 키를 기초로 복호화되는 것을 특징으로 하는 컨텐트 갱신 방법.
- 제1 항에 있어서, 상기 권리객체는 재생(playout) 제약사항 및 표시(displayout) 제약사항 중 적어도 하나를 포함하는 것을 특징으로 하는 컨텐트 갱신 방법.
- 제1 항에 있어서,상기 단말이 권리객체 요청 메시지를 전송하는 단계와, 상기 권리객체 요청 메시지는 상기 새로운 광고 컨텐트 또는 상기 제1 광고 컨텐트의 소비에 대한 인상 데이터(impression data)를 포함하고; 그리고상기 단말이 상기 비광고 컨텐트를 위한 권리객체를 포함하는 권리객체 응답 메시지를 수신하는 단계를 더 포함하는 것을 특징으로 하는 컨텐트 갱신 방법.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/639,699 US9443242B2 (en) | 2010-04-05 | 2011-04-05 | Method for updating advertisement content using DRM |
CN201180017845.6A CN102822842B (zh) | 2010-04-05 | 2011-04-05 | 使用drm更新广告内容的方法 |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US32112210P | 2010-04-05 | 2010-04-05 | |
US61/321,122 | 2010-04-05 | ||
US32664610P | 2010-04-21 | 2010-04-21 | |
US61/326,646 | 2010-04-21 | ||
US37938810P | 2010-09-02 | 2010-09-02 | |
US61/379,388 | 2010-09-02 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2011126280A2 true WO2011126280A2 (ko) | 2011-10-13 |
WO2011126280A3 WO2011126280A3 (ko) | 2012-03-22 |
Family
ID=44763393
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2011/002381 WO2011126280A2 (ko) | 2010-04-05 | 2011-04-05 | Drm을 이용한 광고 컨텐트 갱신 방법 |
Country Status (3)
Country | Link |
---|---|
US (1) | US9443242B2 (ko) |
CN (1) | CN102822842B (ko) |
WO (1) | WO2011126280A2 (ko) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7805373B1 (en) * | 2007-07-31 | 2010-09-28 | Qurio Holdings, Inc. | Synchronizing multiple playback device timing utilizing DRM encoding |
US8060904B1 (en) | 2008-02-25 | 2011-11-15 | Qurio Holdings, Inc. | Dynamic load based ad insertion |
KR101830968B1 (ko) * | 2010-08-24 | 2018-02-21 | 삼성전자주식회사 | 다양한 종류의 광고를 강제 시청하게 하는 장치 및 방법 |
CN103177867B (zh) * | 2013-03-27 | 2015-06-17 | 山西恒立诚磁业有限公司 | 烧结钕铁硼永磁体的制备方法及装置 |
CN103530797A (zh) * | 2013-10-12 | 2014-01-22 | 惠州Tcl移动通信有限公司 | 一种利用机顶盒发布广告的方法及系统 |
US9883224B2 (en) * | 2013-12-10 | 2018-01-30 | Cellco Partnership | Take it with you premium video content |
CN104202622B (zh) * | 2014-09-23 | 2017-11-07 | 山东泰信电子股份有限公司 | 一种广告安全播出方法及系统 |
US11310094B2 (en) | 2015-09-08 | 2022-04-19 | Lg Electronics Inc. | Apparatus and method for transmitting or receiving broadcast signal |
WO2017043898A1 (ko) | 2015-09-08 | 2017-03-16 | 엘지전자(주) | 방송 신호 송수신 장치 및 방법 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20060040489A (ko) * | 2004-11-06 | 2006-05-10 | 엘지전자 주식회사 | 광고컨텐츠가 첨부된 디지털저작권관리 컨텐츠 처리 방법및 장치 |
KR20080027040A (ko) * | 2006-09-22 | 2008-03-26 | 삼성전자주식회사 | 컨텐츠 공유를 위한 컨텐츠 생성 방법 및 그 장치 |
KR20090000144A (ko) * | 2007-01-16 | 2009-01-07 | 엔에이치엔(주) | 스트리밍 서비스 기반의 콘텐츠에 대한 drm 방법 및상기 방법을 수행하는 시스템 |
KR20090000133A (ko) * | 2007-01-09 | 2009-01-07 | 엔에이치엔(주) | 벨 소리 무료 제공 서비스를 이용한 광고 방법 및 광고시스템, 그리고 상기 광고 방법을 실행시키기 위한프로그램이 기록된 컴퓨터에서 판독 가능한 기록 매체 |
KR20090010468A (ko) * | 2007-07-23 | 2009-01-30 | 손대원 | 새로운 컨테이너 포멧, 상기 컨테이너 포멧을 이용한drm 방법 및 시스템 그리고 광고 제공 방법 및 시스템 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6912571B1 (en) * | 2000-02-22 | 2005-06-28 | Frank David Serena | Method of replacing content |
US8667525B2 (en) * | 2002-12-13 | 2014-03-04 | Sony Corporation | Targeted advertisement selection from a digital stream |
US20070271455A1 (en) * | 2004-07-20 | 2007-11-22 | Toshihisa Nakano | Reproduction Control Device, Gate Device, and Reproduction Control System |
WO2008060300A1 (en) | 2006-11-16 | 2008-05-22 | Dynomedia, Inc. | Systems and methods for distributed digital rights management |
AU2008205545B2 (en) | 2007-01-17 | 2012-03-08 | Intertrust Technologies Corporation | Methods, systems, and apparatus for fragmented file sharing |
CN101296359A (zh) | 2007-04-24 | 2008-10-29 | 宋亚民 | 基于广告付费的视频节目数字版权管理方法 |
KR101593569B1 (ko) * | 2009-02-02 | 2016-02-15 | 삼성전자주식회사 | 콘텐츠 오브젝트 구성 방법 및 시스템 |
CN101835148B (zh) * | 2009-03-13 | 2012-12-26 | 中国移动通信集团公司 | 一种数字内容分发与获取方法、系统及设备 |
-
2011
- 2011-04-05 US US13/639,699 patent/US9443242B2/en active Active
- 2011-04-05 WO PCT/KR2011/002381 patent/WO2011126280A2/ko active Application Filing
- 2011-04-05 CN CN201180017845.6A patent/CN102822842B/zh not_active Expired - Fee Related
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20060040489A (ko) * | 2004-11-06 | 2006-05-10 | 엘지전자 주식회사 | 광고컨텐츠가 첨부된 디지털저작권관리 컨텐츠 처리 방법및 장치 |
KR20080027040A (ko) * | 2006-09-22 | 2008-03-26 | 삼성전자주식회사 | 컨텐츠 공유를 위한 컨텐츠 생성 방법 및 그 장치 |
KR20090000133A (ko) * | 2007-01-09 | 2009-01-07 | 엔에이치엔(주) | 벨 소리 무료 제공 서비스를 이용한 광고 방법 및 광고시스템, 그리고 상기 광고 방법을 실행시키기 위한프로그램이 기록된 컴퓨터에서 판독 가능한 기록 매체 |
KR20090000144A (ko) * | 2007-01-16 | 2009-01-07 | 엔에이치엔(주) | 스트리밍 서비스 기반의 콘텐츠에 대한 drm 방법 및상기 방법을 수행하는 시스템 |
KR20090010468A (ko) * | 2007-07-23 | 2009-01-30 | 손대원 | 새로운 컨테이너 포멧, 상기 컨테이너 포멧을 이용한drm 방법 및 시스템 그리고 광고 제공 방법 및 시스템 |
Also Published As
Publication number | Publication date |
---|---|
WO2011126280A3 (ko) | 2012-03-22 |
US9443242B2 (en) | 2016-09-13 |
CN102822842A (zh) | 2012-12-12 |
US20130030912A1 (en) | 2013-01-31 |
CN102822842B (zh) | 2016-11-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011126280A2 (ko) | Drm을 이용한 광고 컨텐트 갱신 방법 | |
EP2596452A2 (en) | Method and apparatus for providing drm service | |
WO2019227557A1 (zh) | 密钥管理方法、设备、存储介质及装置 | |
WO2012112011A2 (ko) | 심리스 콘텐트 재생 방법 및 장치 | |
WO2010087567A1 (en) | Method for installing rights object for content in memory card | |
WO2013137644A1 (ko) | 북마크를 이용한 심리스 재생 방법, 장치 및 시스템 | |
WO2014069949A1 (ko) | 컨텐트 재생 방법 및 장치 | |
US8079089B2 (en) | Information usage control system and information usage control device | |
WO2020189926A1 (ko) | 블록체인 네트워크를 이용하여 사용자의 아이덴티티를 관리하는 방법 및 서버, 그리고, 블록체인 네트워크 기반의 사용자 아이덴티티를 이용하여 사용자를 인증하는 방법 및 단말 | |
EP2435966A2 (en) | Method and apparatus for searching and downloading related contents by terminal through broadcast service | |
WO2013047997A1 (ko) | 라이트 체크를 기반으로 하는 콘텐트 다운로드 방법, 디바이스 및 시스템 | |
US20130003969A1 (en) | Method and apparatus for key distribution with implicit offline authorization | |
WO2021177787A1 (ko) | 개별화된 시간 관리를 위한 효율적인 데이터베이스 아키텍쳐를 통한 콘텐츠 제공 방법 및 시스템 | |
WO2022060149A1 (ko) | 탈중앙화 네트워크를 이용하여 권리를 관리하는 전자 장치 및 이의 동작 방법 | |
WO2020141782A1 (ko) | 블록체인 네트워크를 이용하여 사용자의 아이덴티티를 관리하는 방법 및 서버, 그리고, 블록체인 네트워크 기반의 사용자 아이덴티티를 이용하여 사용자를 인증하는 방법 및 단말 | |
WO2020189993A1 (ko) | 암호화폐 분실 방지 방법 및 시스템 | |
WO2015161645A1 (zh) | 一种多媒体内容更改检测方法、装置及资源传播系统 | |
WO2019088688A1 (ko) | 블록체인기술을 이용한 컨텐츠 유통 관리 시스템 및 방법 | |
WO2012149717A1 (zh) | 基于tcm或tpm的license动态管理方法、装置及系统 | |
WO2017067284A1 (zh) | 一种指纹信息的安全调用方法、装置及移动终端 | |
WO2014133337A1 (ko) | 컨텐트 재생 방법 및 장치 | |
WO2010147410A2 (en) | Method and device for upgrading rights object that was stored in memory card | |
WO2018079971A1 (ko) | 전자 장치, 방송 서비스 제공 시스템 및 그 동작방법 | |
WO2011037318A2 (en) | Method for using rights to contents | |
WO2019160167A1 (ko) | 복수의 블록체인에 기반을 둔 생명정보 데이터 제공 방법, 생명정보 데이터 저장 방법 및 생명정보 데이터 전송 시스템 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201180017845.6 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11766131 Country of ref document: EP Kind code of ref document: A2 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13639699 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11766131 Country of ref document: EP Kind code of ref document: A2 |