JP2005032125A - Method, device and program for encapsulation, method, device and program for license generation, method, device and program for service provision, and method, device and program for viewing content - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a contents circulation management technique which integrates a plurality of content circulation management (Digital Rights Management, DRM) systems to prevent contents from being wrongfully utilized. <P>SOLUTION: A license generation device acquires key information used for encapsulation of the content and identifier information of a DRM system showing by which DRM system the content has been encapsuled, from an encapsulation device while making the content to correspond to a content ID. When receiving a license generation request with designation of a content ID from a service provision device which receives a license issue request of a user terminal device, the license generation device acquires the key information and identifier information of a DRM system which the content ID indicates, from information received from the encapsulation device, and generates license information on the basis of these pieces of information. Thus the license information for the content for which license generation has been requested is generated and is transmitted to the user terminal device via the service provision device. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an encapsulating apparatus and method, a license generating apparatus and method, a service providing apparatus and method, a content viewing apparatus and the same used for realizing a content distribution management system that prevents unauthorized use of content. The present invention relates to a method, an encapsulation program, a license generation program, a service providing program, and a content viewing program.

  More specifically, the present invention encrypts content data using an encryption technique, and adds (encapsulates) information necessary for copyright management, thereby permitting use of the content. The present invention relates to content distribution management (DRM (Digital Rights Management)) technology that controls conditions and prevents unauthorized use of content, and in particular, integrates multiple DRM systems to manage content distribution management (copyright management). The present invention relates to content distribution management technology to be performed.

Prior to the description of the background art of the present invention, definitions of terms to be used will be described. The following terms are used with the following meanings.
(1) “Digital content” means digital data obtained by digitizing content such as still images, videos, music, texts, software, etc., and digital data of original content before copyright protection processing. is there.
(2) “Capsule content” means digital content that has been subjected to copyright protection processing (encapsulation) such as encryption or addition of copyright management information in order to protect the copyright of the digital content.
(3) “Right information” means, for example, copyright management such as a content ID for identifying content, attribute information such as a digital content title and author information, a use permission condition such as a viewable period and a reproducible number of times, etc. It means data that describes necessary information.
(4) “License” is data describing the right of the user to view the capsule content on the user terminal. For example, the DRM system on the user terminal, such as right information and user terminal information, This means data in which information necessary for controlling the viewing of capsule content is described.
(5) “Content distributor” means a person or company that owns the right to distribute digital content to users.
(6) “Content distributor” means a person or company that is entrusted with the sale of capsule content by a content distributor and directly provides services such as license sales to users.
(7) “Distribution right information” means content right information set by a content distributor and information described in a copyright management language independent of the DRM method.
(8) “Sales right information” means content right information set by a content distributor and information written in a copyright management language independent of the DRM method.
(9) “Encapsulation program” means a program that encrypts digital content using encryption technology and adds information (right information, etc.) necessary for copyright management.
(10) “License generation program” means a program that generates a license in a format that can be interpreted by the player of the user terminal that issued the license issuance based on the content right information and user terminal information. It is.
(11) “Service providing program” means a program that directly accesses a user and provides various services for the user such as authentication, billing, and license generation / distribution.

  In recent years, digital contents such as music, video, and games have been actively distributed through networks such as the Internet and cable television, or information recording media such as CDs and DVDs. On the other hand, digital information has the feature that it is easy to copy and does not deteriorate, and it becomes a problem that illegal copies of digital contents are created and distributed without the copyright holders between pirated vendors or consumers. ing. For this reason, development of a DRM system for preventing unauthorized copying of digital contents and the spread of pirated versions and protecting / managing copyrights has been underway.

  In a conventional content distribution management (DRM) system, a content distributor creates rights information including digital content attribute information and usage permission conditions, and encapsulates the digital content based on the rights information. Distribute content (capsule content) to the market.

  The user obtains capsule content distributed in the market and a dedicated player necessary for viewing the capsule content, and in some cases, a right (license) for viewing the capsule content is obtained from the content distributor. The content can be viewed by purchasing separately.

  On the other hand, multiple DRM systems such as Windows Media Rights Manager (system provided by Microsoft), Real System Media Commerce Suite (system provided by Real Networks), and Adobe Content Server (system provided by Adobe) have already been put into practical use. With the increase in content to be distributed and the demand for high-performance copyright protection of the content, more various DRM systems are being realized one after another.

  However, these DRM systems differ in the right information description method, the type of use permission condition, the type of player for viewing the capsule content, etc., depending on the implementation method used by each DRM system. Therefore, the user needs to obtain a tool (such as a dedicated player) necessary for viewing each time according to the DRM system specified by the content distributor. Also, if the tool (dedicated player or the like) does not support the type of user terminal, there is a problem that the capsule content cannot be viewed.

  By the way, in the DRM method in which the right (license) for viewing the capsule content is purchased from a content distributor separately from the capsule content, the capsule content and the license are separated and distributed separately. In this case, an address of a server (license server or the like) that issues a license is embedded in the capsule content, and information (right information or the like) that controls viewing of the capsule content is embedded in the license.

  When the user views the capsule content, the dedicated player of the DRM system installed in the user terminal first checks whether the license exists on the terminal (valid) or not, and the license does not exist (valid) If not, a license issuance request is made to the address of the license server embedded in the capsule content. Here, when the license exists (is valid), the capsule content can be viewed.

  In the license server, when a license issuance request is received from the user terminal, a service providing program dedicated to the DRM system is activated, a purchase service such as authentication processing or billing processing, activation of the license generation program, license to the requesting user Performs license issuance processing for users, such as distribution. Here, when the license generation program is started from the service providing program, a license corresponding to the DRM system is generated based on the right information created by the content distributor and returned to the service providing program.

  The user terminal can view the capsule content by acquiring this license.

The conventional DRM system described above is introduced in detail in the following non-patent documents.
“What is Q & A DRM technology?”, NTT Technical Journal, 2002 Vol.14 No.11 pp.62-63 "Digital Content Copyright Management and Protection Platform: Copyright Management Platform", Hiroyuki Omura et al., NTT Technology Journal, 2002 Vol.14 No.10 pp.16-23 "Copyright protection technology", Hiroshi Fujii et al., NTT Technical Journal, 2002 Vol.14 No.8 pp.20-22 "Development and Evaluation of Rights Distribution Platform", Tomohiro Yamada et al., Information Processing Society of Japan Research Report, 2002-DPS-109 pp.51-57

  In such a conventional content distribution management method, when supporting a plurality of DRM systems, as shown in FIG. 25, a license server on which a dedicated service providing program and a dedicated license generating program are installed for each DRM system. prepare. Then, the user terminal transmits a license issuance request from the DRM dedicated player installed in each terminal to the corresponding license server, and acquires a desired license.

(A) First problem of the conventional method However, in such a conventional method, when a content distribution management service corresponding to a plurality of DRM systems is to be provided, the description method of the right information differs for each DRM system. It is necessary to prepare rights information specialized for each DRM system for one content by the number of corresponding DRM systems, and as the number of contents to be distributed and the number of corresponding DRM systems increase, There was the first problem that management became complicated.

  That is, there is a problem that it is necessary to create right information for each DRM system in consideration of the DRM system.

(B) Second problem of conventional methods In addition, in order to promote the distribution of content, the functions of a service providing program that directly accesses users and provides various services are extracted, and contents such as an Internet service provider (ISP) It is conceivable to entrust the operation to the distributor, but since the content distributor cannot change the right information set by the content distributor on its own, it is flexible on the service provision program operated by the content distributor. There was a second problem that it was difficult to change the rights information.

  That is, since rights information set in advance is used when generating a license, there is a problem that flexible rights information cannot be set when providing a service.

(C) Third problem of the conventional method Furthermore, since the execution method of the license generation program and the license distribution method are different for each DRM system, it is necessary to prepare a service providing program depending on each DRM system for each DRM system. As the number of corresponding DRM systems increases, there is a third problem that the system scale of the entire content distribution system increases.

  That is, there is a problem that it is necessary to create a service providing program conscious of the DRM system for each DRM system.

(D) Fourth problem of the conventional method Furthermore, since the URL of the service providing program is embedded in the capsule content, the content is reencapsulated when the location of the service providing program is changed due to a change in the provided service, etc. There is a fourth problem that capsule content already distributed cannot be used.

  That is, since the position of the service providing server is fixed at the time of encapsulation, there is a problem that it is difficult to change the service.

  The present invention has been made in view of such circumstances, and in a content distribution management service corresponding to a plurality of DRM systems, it is not necessary to prepare right information specialized for each DRM system, and the service is performed when a license is issued. The right information can be changed flexibly on the providing program side, so there is no need to prepare a service providing program that depends on each DRM system, and there is no need to re-encapsulate the content when the location of the license server is changed. The purpose is to provide a new content distribution management technology.

  In order to achieve this object, according to the present invention, in realizing a content distribution management service corresponding to a plurality of DRM systems, an encapsulating apparatus, a license generating apparatus, a service providing apparatus, a user terminal apparatus ( A content viewing device).

(A) Encapsulation device of the present invention The encapsulation device of the present invention comprises (1) means for registering distribution right information of content described in a language independent of the DRM method in the storage means, and (2) any DRM. (3) save the content by encapsulating the content by the method and registering it in the storage means, and registering the key information used for encapsulation and the DRM method identifier information indicating which DRM method is used in the storage means; Means for notifying the license generation device of distribution right information stored in the means, key information stored in the storage means, and DRM system identifier information.

  Each of the processing means described above can be realized by a computer program, and this computer program can be provided by being recorded on a recording medium such as a semiconductor memory or via a network.

(B) License generation apparatus according to the present invention The license generation apparatus according to the present invention includes (1) distribution right information of content described in a language independent of the DRM method, key information used to encapsulate the content, and which DRM system identifier information indicating that the DRM system is used, means for registering in the storage means, (2) means for receiving a license generation request from the service providing device, and (3) storage means , Means for acquiring distribution right information, key information and DRM system identifier information for a content having a license generation request; (4) acquisition of sales right information described in the language specified in the license generation request; Means for verifying the legitimacy of the sales right information by comparing the distribution right information, and (5) the sales specified in the license generation request. Means for generating license information for content with a license generation request in accordance with the DRM method indicated by the acquired identifier information based on the selling right information and the acquired key information, and (6) providing the generated license information as a service Means for transmitting to the apparatus.

  When adopting this configuration, the registering means may register the address information of the service providing apparatus in the storage means. At this time, (7) means for accepting a license issuance request from the user terminal apparatus; (8) means for acquiring the address information of the service providing apparatus for the content designated by the license issuance request from the storage means, and (9) means for notifying the user terminal apparatus of the acquired address information.

  Each of the processing means described above can be realized by a computer program, and this computer program can be provided by being recorded on a recording medium such as a semiconductor memory or via a network.

(C) Service providing apparatus of the present invention The service providing apparatus of the present invention includes (1) means for obtaining distribution right information of content described in a language independent of the DRM method, and (2) the acquired distribution right information. A means for creating sales right information of content described in a language independent of the DRM method and registering it in the storage means; (3) means for receiving a license issuance request from the user terminal device; and (4 ) Means for obtaining sales right information for content for which a license is issued based on the sales right information stored in the storage means; and (5) information specified in the license issuance request for the license generation device. Means for designating the acquired sales right information and requesting generation of a license for content for which a license issuance request is made, and (6) a license Receiving license information returned in response to the service generation request and issuing the license information to the user terminal device.

  Each of the processing means described above can be realized by a computer program, and this computer program can be provided by being recorded on a recording medium such as a semiconductor memory or via a network.

(D) User terminal device according to the present invention The user terminal device according to the present invention has the function of notifying the address information of the service providing device when the license generating device according to the present invention has the function of (1) using any DRM method. Means for acquiring encapsulated content, and (2) license generation as a device indicated by address information embedded in the encapsulated content when there is no license required for viewing the encapsulated content A means for requesting the device to issue a license; (3) a means for receiving address information returned in response to the license issuance request; and (4) a service provision that is a device indicated by the received address information. Means for requesting the device to issue a license again; and (5) the license returned in response to the license reissue request. Means for receiving sense information; and (6) means for decrypting the encapsulated content using the received license information.

  Each of the processing means described above can be realized by a computer program, and this computer program can be provided by being recorded on a recording medium such as a semiconductor memory or via a network.

  In the content distribution management system configured as described above according to the present invention, the encapsulating apparatus sets distribution right information of content described in a language independent of the DRM method. Then, the content attribute information included in the distribution right information of the content to be encapsulated is used to encapsulate the content by an arbitrary DRM method, and the content ID is embedded in the header of the encapsulated content. While taking the correspondence, the license generation apparatus is notified of the distribution right information of the encapsulated content, the key information used for the encapsulation, and the DRM system identifier information indicating which DRM system is used.

  On the other hand, when the user terminal device obtains and views the encapsulated content and there is no license necessary for viewing the encapsulated content, the user terminal device headers the encapsulated content. The content ID embedded in the header of the encapsulated content and the DRM specific data (consisting of header information, user terminal device specific information, etc.) Specify and request to issue a license.

  When this URL points to the service providing device, it requests the service providing device to issue a license, but this URL points to a device other than the service providing device (for example, a license generating device). In this case, the device is requested to issue a license. In this case, since the URL of the service providing apparatus is returned from the apparatus, when the URL of the service providing apparatus is received, the service providing apparatus is requested to issue a license.

  In this manner, when the license issuing request is received by designating the content ID and the DRM specific data from the user terminal device, the service providing device sends the content ID and the DRM specific data to the license generating device. Specify to request generation of a license. At this time, the service providing apparatus requests the generation of a license by specifying the sales right information of the content created based on the distribution right information obtained from the encapsulating apparatus.

  Upon receiving this license generation request, the license generation device receives the distribution right information / point indicated by the content ID specified in the license generation request from the distribution right information / key information / DRM system identifier information received from the encapsulation device. Key information / DRM system identifier information is acquired. Then, the validity of the sales right information is verified by determining whether the sales right information specified in the license generation request falls within the range of the acquired distribution right information, and the validity of the sales right information is verified. If the license information is generated, the license information (the DRM method indicated by the acquired identifier information) about the content for which the license generation request is made based on the information (including the sales right information) specified in the license generation request and the acquired key information. Is generated according to the license information and is transmitted to the service providing apparatus.

  In response, the service providing device returns the license information returned from the license generating device to the user terminal device that is the license issuance request source. In response to this, the user terminal device receives the information from the service providing device. The received license information that is returned is received, and the encapsulated content is decrypted using the received license information to view the encapsulated content.

  According to this configuration, according to the present invention, the service providing apparatus does not need to be aware of the DRM method at all, and can flexibly change the sales right information within the range of the distribution right information set by the encapsulating apparatus. . The user terminal device can know the URL of the service providing device even if the URL of the service providing device is changed.

  In this way, according to the present invention, in the content distribution management service corresponding to a plurality of DRM systems, it is not necessary to prepare rights information specialized for each DRM system, and the service providing program can flexibly issue a license when issuing a license. It is possible to change the rights information, and there is no need to prepare a service providing program depending on each DRM system, and it is possible to realize that the re-encapsulation of contents is not required when the position of the license server is changed. It becomes like this.

(A) Configuration in which user terminal device transmits license issuance request directly to service providing device A content distribution management system according to the present invention encapsulates digital content by an arbitrary DRM method, The capsule content in which the content ID is embedded is distributed from the encapsulating device to an unspecified number of user terminal devices, and the user terminal device issues a license issuance request to the service providing device when attempting to view the capsule content. And the service providing apparatus sets sales right information and transmits a license generation request to the license generation apparatus. The license generation apparatus generates a license that allows viewing of the capsule content based on the sales right information, Service provision equipment from generation device The license is distributed to the user terminal device via a device.

  When adopting this configuration, the license generating apparatus (1) sets the license information in which the content ID of the digital content, the DRM method and key information used for the encapsulation, and the distribution right information are associated with each other and stored in the license DB. And (2) receiving a license generation request sent from the service providing apparatus via a network, collecting information necessary for license generation processing from the license generation request and the license DB, and including the information in the license generation request The license generation pre-processing means for generating the individual DRM license generation request used for generating the license, and (3) using the individual DRM license generation request generated by the license generation pre-processing means, DRM-specific license by specified DRM method A license generation execution unit that generates license transmission data for generating and transmitting the DRM-specific license to the user terminal device; and (4) the license transmission data generated by the license generation execution unit License information transmitting means for transmitting to the service providing apparatus.

  The encapsulating apparatus includes (1) an encapsulating instruction unit that creates an encapsulating instruction for executing encapsulation from a content ID, a file name, and the like of digital content to be encapsulated, and (2) Necessary for encapsulating the DRM method by determining a DRM method for protecting digital content from the encapsulation command created by the encapsulation command means and the IPR-DB storing content attribute information and distribution right information. A pre-encapsulation processing unit that extracts a simple parameter, embeds a content ID in any of the parameters, and creates an encapsulation parameter for use in encapsulation of the DRM method; and (3) the pre-encapsulation processing unit Using the created encapsulation parameter, it is specified by the encapsulation preprocessing means. (4) Capsule content created by the encapsulation execution unit and key information used for the encapsulation are stored, and the capsule content is requested in response to a request. And encapsulated information storage means for distributing key information.

(B) Configuration in which user terminal device transmits license issuance request to service providing device via license generating device In the content distribution management system according to the present invention, the user terminal device is connected to the service providing device. Instead of transmitting the license issuance request directly, the license issuance request may be transmitted to the service providing apparatus via the license generation apparatus.

  In the case of adopting this configuration, the content distribution management system according to the present invention encapsulates the digital content by an arbitrary DRM method, and encapsulates the capsule content in which the content ID of the digital content is embedded from the encapsulation device. The user terminal device transmits a license issuance request to the service providing device via the license generating device when the user terminal device attempts to view the capsule content, and the service providing device provides the sales right information. Set and send a license generation request to the license generation device, the license generation device generates a license that allows viewing of the capsule content based on the sales right information, and the user from the license generation device via the service providing device The license to the terminal device Configured to trust.

  When adopting this configuration, the encapsulating apparatus (1) encapsulating instruction means for creating an encapsulating instruction for executing encapsulation from the content ID or file name of the digital content to be encapsulated And (2) determining the DRM method for protecting the digital content from the encapsulation command created by the encapsulation command means and the IPR-DB storing the content attribute information and distribution right information, and the DRM method A pre-encapsulation processing means for extracting a parameter required for encapsulation, embedding a content ID in any item of the parameter, and creating an encapsulation parameter used for encapsulation of the DRM method; and (3) the capsule Using the encapsulation parameter created by the pre-encapsulation processing means. And (4) storing the capsule content created by the encapsulation execution unit and the key information used for the encapsulation in response to a request. And encapsulating information storage means for distributing capsule contents and key information accordingly.

  The license generating device (1) obtains the content ID of the digital content, the DRM method and key information used for encapsulation, the distribution right information, and the address (service URL) of the service providing device that provides the service. (2) a license issuance request sent from a user terminal device via a network is received, and the license information is set based on the content ID included in the license issuance request. Service resolver that obtains a service URL and redirects a license issuance request to the service URL; (3) accepts a license generation request sent from the service providing apparatus via a network, and receives the license generation request and the license From DB A license generation pre-processing unit that collects information necessary for sense generation processing, authenticates sales right information included in the license generation request, and generates an individual DRM license generation request used for license generation; and (4) the license Using the individual DRM license generation request generated by the generation preprocessing means, a DRM specific license is generated by a specified DRM method, and license transmission data for transmitting the DRM specific license to the user terminal device is generated And (5) license information transmission means for transmitting the license transmission data created by the license generation execution means to the service providing apparatus that is the request source.

  Further, the service resolving means (1) accepts a license issuance request sent from the user terminal device, and transmits license data for redirecting the license issuance request to the service URL to the user terminal device. Request accepting means, (2) service determining means for obtaining a service URL from the license DB based on the content ID included in the license issuance request, and (3) a script for redirecting the user terminal device to the service providing device. Redirection data creation means for creating redirection data for redirecting the license issuance request accepted by the license issuance request acceptance means to the service URL using a redirection data template in which is described Features To.

  Then, the user terminal device is (1) content acquisition means for acquiring capsule content from the encapsulation device or a network directory in which capsule content encapsulated by the encapsulation device is stored and an information storage medium. And (2) content viewing means for outputting the contents of the capsule content to a display device such as a display in accordance with a viewing request from the user, and (3) a license necessary for viewing the capsule content on the user terminal device If the license exists, the capsule content is decrypted. If the license does not exist, a license issuance request is made to the address embedded in the capsule content. Acquired and acquired license Characterized in that it comprises a viewing control unit further performs decoding processing of the capsule content.

  And (1) a service accepting unit that accepts a license issuance request sent from the user terminal device via the network, and extracts a content ID and DRM-specific data from the license issuance request; 2) Sales right information acquisition means for acquiring the sales right information of the content requested by the user based on the content ID from the sales management DB storing the sales right information of the content, (3) the content ID of the content, and the DRM License generation request means for transmitting a license generation request including unique data and sales right information to the license generation apparatus via the network; and (4) license transmission data generated by the license generation apparatus via the network. License information acquisition method acquired from the license generation device via When, characterized in that it comprises a license issue means for distributing the DRM-specific license to the user terminal device by using the (5) the license transmission data.

(C) Detailed configuration of each processing means The pre-encapsulation processing means (1) obtains an encapsulation instruction created by the encapsulation instruction means, and uses the DRM method used for the encapsulation processing from the encapsulation instruction and content (2) Attribute information acquisition that acquires attribute information of the target content from the IPR-DB based on the content ID acquired by the encapsulation command analysis unit Means (3) content ID embedding means for extracting information to be stored in the header of the capsule content from the attribute information acquired by the attribute information acquisition means, and embedding the content ID in any of the data; (4) Based on the DRM method acquired by the encapsulation instruction analyzing means, information necessary for the encapsulation of the DRM method is collected and encapsulated. And encapsulating parameter creating means for creating an encapsulating parameter to be used for encapsulating.

  Further, the content ID embedding means embeds the content ID as a URL parameter in the address (URL) of the server that issues the license in the header information of the capsule content.

  The license generation preprocessing means receives (1) a license generation request sent from the service providing apparatus via the network, and receives a content ID, DRM specific data, and sales right information from the license generation request. License generation request accepting means to be extracted; (2) based on the content ID acquired by the license generation request accepting means, from the license DB, the DRM method and key information used for encapsulating the target content, distribution rights information, (3) Rights information for authenticating rights information by comparing the sales rights information obtained by the license generation request accepting means with the distribution rights information obtained by the license information obtaining means Authentication means, and (4) based on the DRM method acquired by the license information acquisition means Collects information necessary for license generation, characterized in that it comprises a separate DRM license generation request creating means for creating a separate DRM license generation request comprising a key information and sales rights information and DRM specific data.

  The license generation execution means includes a plurality of individual DRM license generation means according to the DRM method, and each of these individual DRM license generation means receives the individual DRM license generation request generated by the license generation preprocessing means as an input. (1) key information analysis means for acquiring key information from the individual DRM license generation request, analyzing the key information, and extracting parameters necessary for generating a license for the corresponding DRM scheme; and (2) the individual information DRM-specific data analyzing means for acquiring DRM-specific data from a DRM license generation request, analyzing the DRM-specific data, and extracting parameters necessary for generating a corresponding DRM-type license; (3) generating the individual DRM license Obtain sales rights information from the request and use the rights description conversion table to Sales right information analyzing means for converting rights information into rights information description specific to the corresponding DRM system and extracting parameters necessary for license generation; (4) the key information analyzing means, DRM specific data analyzing means and sales A license generation parameter creation unit that creates a license generation parameter for generating a license from the parameters extracted by the right information analysis unit, and (5) a license generation parameter created by the license generation parameter creation unit Generating a license using a license generation program for creating a DRM-specific license by the DRM method and (6) a license transmission data template which is a script template for transmitting the DRM-specific license to the user terminal device D created by the program Characterized in that it comprises a license transmission data creation means for creating a license for transmission data for transmitting M-specific license to the user terminal.

(D) Other configurations Distribution rights information and sales rights information may consist of data written in a markup language.

  Also, the sales rights information and the distribution rights information with the same content ID have the same tag structure, and the contents of the license conditions described in the sales rights information are within the scope of the contents of the license conditions described in the distribution rights information. In other cases, it may be designated as illegal, otherwise it may be considered illegal.

  Further, the sales right information analyzing means may use an XSLT stylesheet as a right description conversion table and use XSLT (XML Stylesheet Language Transform) as a conversion method from the sales right information to a right information description specific to the DRM method. is there.

  The service receiving means may provide a user with services such as a content purchase service such as an authentication process and a billing process, and an information providing service such as an advertisement and a recommendation, based on the content ID.

  The license transmission data may be composed of HTML in which a script for sending a DRM-specific license to a user terminal is described.

  The license issuing means may edit the license transmission data, insert information such as advertisements and recommendations, and perform a process of presenting the information to the user.

  Hereinafter, Embodiment 1 of the present invention will be described in detail with reference to the drawings.

  First, an overview of various data flows and processes handled by the content distribution management system according to the first embodiment will be described with reference to FIG. In the figure, 1 is an encapsulation device, 2 is a license generation device, 3 is a service providing device, and 4 is a user terminal device. It is assumed that the encapsulating apparatus 1 is managed by a content distributor and the service providing apparatus 3 is managed by a content distributor.

  First, a content distributor prepares distribution right information of the digital content when distributing the digital content to the market (step S1). In this distribution right information, content attribute information and use permission conditions are described in a common format (language) independent of the DRM method.

  As a common format (language) independent of the DRM method, for example, an XML-based digital copyright management language XrML (http://www.xrml.org/) can be used. This XrML is defined by the XrML Core Schema, Standard Extension Schema, and Content Extension Schema. Etc. can be described.

  Next, the content distributor encapsulates the digital content based on any designated DRM encapsulation method, and generates the capsule content and the key information of the capsule content (step S2).

  Next, the content distributor presents the distribution right information describing the right information of the digital content to the content distributor that actually distributes the content to the user. Creates sales right information based on the distribution right information (step S3).

  This sales right information is set with a digital content use permission condition when the content is actually provided to the user. Note that the relationship between the distribution right information and the sales right information is solved in advance by contract processing or the like.

  In the first embodiment, in order to clarify the scope of rights between the content distributor and the content distributor, the sales right information has the same tag structure as the distribution right information, and the value of the license agreement for the sales right information is There is a restriction that it must be set within the range of values specified in the license agreement for distribution rights information (distribution rights information> sales rights information).

  Specifically, as shown in FIG. 2 and FIG. 3, for example, the distribution rights information (shown in FIG. 2) and the sales rights information (shown in FIG. 3) have the same tag structure. The number of playable times (exerciseLimit / stateReference / count) defined in the line (changed from 10 to 3 in the example) and the expiration date defined in the 18th to 20th lines It is possible to change only the value of the date and time (validityInterval / notAfter) (changed from 00: 00: 00: 00 on March 15, 2010 to 00: 00: 00: 00 on March 15, 2005 in the figure).

  Next, the content distributor registers the distribution right information and key information in the license generation device 2 so that the content distributor can issue a license to the user of the capsule content. (Step S4).

  Next, the content distributor or content distributor distributes the capsule content to the user by downloading or streaming (step S5).

  Next, when the user views the capsule content on the user terminal device 4, if the license necessary for viewing the capsule content does not exist on the user terminal device 4, the user terminal device 4 The DRM-specific data is transmitted as a license issuance request to the location (URL) of the server that issues the license described in the header of the capsule content (step S6).

  The information described in the DRM specific data differs depending on the DRM method, but generally the header information of the capsule content and the specific information (for example, IP address, MAC address, etc.) of the user terminal device 4 are encrypted or hashed. It is described with anti-tampering treatment.

  Next, the content distributor who has received the license issuance request creates license generation data based on the DRM specific data sent from the user terminal device 4 and the sales right information created in step S3 (step S7). .

  In the license generation data, sales right information, DRM specific data, content ID, and the like are described. Since the content of the DRM specific data differs depending on the DRM method, the content is not analyzed here, and the DRM specific data sent from the user terminal device 4 is stored in the license generation data as it is. Specifically, as shown in FIG. 4, for example, DRM-specific data and a content ID tag and value are added to the sales right information described in XrML.

  Next, the content distributor transmits the license generation data created in step S7 to the license generation device 2 in order to generate the license of the user who has received the license issuance request (step S8).

  Next, the license generation apparatus 2 that has received the license generation request extracts the sales right information from the license generation data acquired in step S8, compares the sales right information with the corresponding distribution right information, and sells the content. The validity of the sales right information sent from the supplier is inspected (step S9).

  As a check of the validity, in the first embodiment, whether or not the sales right information and the tag structure of the corresponding distribution right information are the same, and the value of the use permission condition of the sales right information is the use permission of the distribution right information. Check whether it is within the range of the value specified in the condition.

  Specifically, as shown in FIGS. 2 and 3, for example, the sales rights information and the distribution rights information have the same tag structure, the sales rights information can be reproduced (3 times), and the expiration date and time When the value (March 15, 2005 0: 0: 0) is within the range specified in the distribution rights information (10 times and March 15, 2010 0: 0: 0) Judged to be legitimate. In addition, it may be possible to perform a more flexible validity check by using a tag structure check based on an XML schema or a table defining a comparison condition of right information.

  Next, when the legitimacy of the sales right information is confirmed in step S9, the license generation device 2 uses the license generation data to perform a DRM-specific license (viewing of capsule content according to the DRM method) by an arbitrary DRM method. The license transmission data to be transmitted from the DRM-specific license to the user terminal device 4 is generated (step S10).

  Although the description format of the license transmission data differs depending on the DRM method, for example, as shown in FIG. 5, it can be described using HTML and Java Script (Java is a registered trademark). Here, in FIG. 5, the DRM-specific license is stored in the 8th to 19th lines.

  Next, the license generation device 2 transmits the license transmission data to the content distributor that has received the license generation request (step S11).

  Next, the content distributor uses the license transmission data acquired in step S11 to transmit the DRM-specific license to the user terminal device 4 of the user who has received the license issuance request (step S12).

  Here, the content distributor can use the license transmission data as it is for creating an HTTP response to the HTTP request sent from the user, so that it is not necessary to generate different script data each time according to the DRM method.

  Finally, the user can view the capsule content on the user terminal device 4 with the DRM-specific license distributed from the content distributor (step S13).

  6 and 7 are block diagrams showing the configuration of the first embodiment.

<Overall configuration>
As shown in FIG. 6, the encapsulation apparatus 1 includes an encapsulation command means 10, an encapsulation preprocessing means 11, an encapsulation execution means 12, an encapsulation information storage means 13, a content DB 14, an IPR-DB (Intellectual Property Rights). Database) 15. Furthermore, the pre-encapsulation processing unit 11 includes an encapsulation command analysis unit 110, an attribute information acquisition unit 111, a content ID embedding unit 112, and an encapsulation parameter creation unit 113. The encapsulation execution unit 12 includes a plurality of encapsulation execution units 12. Are encapsulated programs (DRM1 to DRMn).

  The license generation apparatus 2 includes a license information setting unit 20, a license generation preprocessing unit 21, a license generation execution unit 22, a license information transmission unit 23, and a license DB 24. Further, the license generation preprocessing unit 21 includes a license generation request reception unit 210, a license information acquisition unit 211, a right information authentication unit 212, and an individual DRM license generation request generation unit 213. The license generation execution unit 22 includes A plurality of individual DRM license generating means (DRM1 to DRMn).

  Further, each individual DRM license generating means (DRM1 to DRMn) includes a key information analyzing means 220, a DRM specific data analyzing means 221, a sales right information analyzing means 222, a license generation parameter generating means 223, a license, as shown in FIG. It comprises a generation program 224, a license transmission data creation means 225, a right description conversion table 226, and a license transmission data template 227.

  The service providing apparatus 3 includes a service accepting unit 30, a sales right information acquiring unit 31, a license generation requesting unit 32, a license information acquiring unit 33, a license issuing unit 34, and a sales management DB 35.

  The user terminal device 4 includes a content acquisition unit 40, a content viewing unit 41, and a viewing control unit 42.

  The user terminal device 4 and the service providing device 3 are connected via a network, and the service providing device 3 and the license generating device 2 are connected via a network. Further, the user terminal device 4 may acquire capsule content online by connecting to the encapsulation device 1 via a network, or may receive capsule content offline via an information recording medium such as a CD or a DVD. You may get it.

<Content DB14>
The content DB 14 stores digital content before the encapsulation process. The digital content is stored in association with a content identifier (content ID) for uniquely identifying the content. For the content ID, for example, a standard defined in the content ID forum (http://www.cidf.org/) can be used.

<IPR-DB (Intellectual Property Database) 15>
The IPR-DB 15 stores content attribute information and distribution right information expressed in a standardized form. Here, for each content, content attribute information and distribution right information are described and stored in a common format independent of the DRM method.

  The content attribute information includes attributes of the content itself such as the title and type of the content, copyright information such as a producer name and production date, a location where a license is issued (license issuance URL), and the like. In the first embodiment, it is assumed that the address of the service accepting unit 30 of the service providing apparatus 3 that directly provides a service to the user is described as the license issuance URL. The distribution right information includes usage permission condition information such as a viewable period and a reproducible number of times. In addition, a content identifier (content ID) for uniquely identifying the content is managed.

  The contents of the IPR-DB 15 are generally registered in advance by a content producer and a content distributor at the start of content distribution.

<License DB 24>
In the license DB 24, the DRM method and key information used for encapsulating the digital content and the distribution right information of the content are stored in association with the corresponding content ID.

<Sales management DB 35>
In the sales management DB 35, the sales right information of the content is stored in association with the corresponding content ID. Note that the sales right information is generally created in advance within the scope of the rights of the distribution right information acquired from the content distributor by the content distributor at the start of selling the content to the user, and is registered in the sales management DB 35. The

  The sales management DB 35 may store customer information such as content user IDs, passwords, and age, and sales information such as content sales prices and sales start dates, which may be used for services to users. .

<Description of operation>
A content distribution management method realized by the content distribution management system according to the first embodiment configured as shown in FIGS. 6 and 7 will be described in detail with reference to the flowcharts shown in FIGS.

  First, the flow of processing in the encapsulation apparatus 1 according to the first embodiment will be described in detail with reference to the flowcharts shown in FIGS. Here, as shown in FIG. 8, the flow of processing in the encapsulation apparatus 1 according to the first embodiment is “encapsulation instruction processing (step S80)”, “pre-encapsulation processing (step S81)”, “capsule”. Process (step S82) ”and“ encapsulated information storage process (step S83) ”.

  In the “encapsulation command process (step S80)”, an encapsulation command for encapsulating digital content is created based on a request from the content distributor (step S80).

  At this time, the content distributor selects the DRM method used for encapsulation, the content ID of the digital content to be distributed, the file name of the digital content to be encapsulated (input file name), and the file name of the encapsulated capsule content (output) File name). As an input means, when the content distributor and the encapsulating apparatus 1 are connected remotely via a network, the encapsulating apparatus 1 uses a Web server to inform the content distributor of a Web browser Etc. can be used to input data. Based on the input data, an encapsulation instruction is created in a form that can be interpreted by the next pre-encapsulation process.

Specifically, for example, when the DRM format is “DRM1”, the content ID is “0001/000000000001”, the input file name is “in-file.wmv”, and the output file name is “out-file.wmv”,
Pack DRM1 0001/000000000001 in-file.wmv out-file.wmv ・ ・ ・ (i)
An encapsulated instruction is created in a command format such as

  Note that the correspondence between the actual DRM method and the command parameter name of the DRM method can be solved by describing the correspondence relationship in a file read when the program is started, such as an initial setting file. Further, in the first embodiment, the encapsulation is performed by the DRM method requested by the content distributor, but the method of performing the encapsulation by the optimum DRM method based on the user's usage environment (type of player to be viewed). Is also possible.

  In the “pre-encapsulation process (step S81)”, an encapsulation parameter necessary for encapsulating the digital content based on the encapsulation command created by the encapsulation command process and the content of the IPR-DB 15 is created. The designated DRM type encapsulation program (DRM1 to DRMn provided in the encapsulation execution means 12 shown in FIG. 6) is called (step S81).

  Next, a detailed processing flow of “pre-encapsulation processing (step S81)” will be described with reference to FIG. Here, the “pre-encapsulation process (step S81)” includes, as shown in FIG. 9, “encapsulation instruction analysis process (step S90)”, “attribute information acquisition process (step S91)”, “content ID embedding”. Processing (step S92) ”and“ encapsulation parameter creation processing (step S93) ”.

  In the “encapsulated instruction analysis process (step S90)”, the encapsulated instruction created in “encapsulated instruction process (step S80)” is input, and the content of the encapsulated instruction is confirmed (whether the encapsulated instruction is in the correct format). Confirmation, whether the DRM method specified by the encapsulation command is a compatible method, etc.), and if it is determined that encapsulation is possible, encapsulation is performed from the encapsulation command. The DRM system to be performed, the content ID of the digital content, the input file name and the output file name of the digital content are extracted, and the processing is continued. If it is determined that encapsulation is not possible, an error message is presented to the content distributor and the encapsulation is interrupted (step S90).

  In the case of the above example, the DRM method “DRM1”, the content ID “0001/000000000001”, the input file name “in-file.wmv”, and the output file name “out-file.wmv” are extracted. The correspondence between the command parameter name of the DRM method and the actual DRM method is described in the file read at the time of starting the program, such as the initial setting file, as in the “encapsulation instruction process (step S80)”. Can be solved. The correspondence relationship between the DRM method described in the initial setting file and the command parameter name needs to be the same as that in the “encapsulation instruction process (step S80)”.

  In the “attribute information acquisition process (step S91)”, the IPR-DB 15 is accessed based on the content ID acquired in the “encapsulation instruction analysis process (step S90)” to acquire the attribute information of the content ID (step S91). S91). Specifically, for example, content attribute information as shown in FIG. 16 is acquired.

  In the “content ID embedding process (step S92)”, among the attribute information acquired in the “attribute information acquisition process (step S91)”, the DRM method encapsulation acquired in the “encapsulation instruction analysis process (step S90)” The content ID is embedded in any of the attribute information used in (written in the header of the capsule content at the time of encapsulation) (step S92).

  Here, the type of attribute information for embedding the content ID and the embedding method are not particularly defined. For example, a license issuance URL can be used. In this case, the license issuance URL is directly used as a license acquisition destination address when a license issuance request is made. Therefore, by embedding the content ID as a URL parameter, the license issuance side can easily obtain the content ID by acquiring the URL parameter. become. The content ID to be embedded is URL encoded.

Specifically, in the attribute information of FIG. 16, when the content ID “0001/000000000001” is embedded in the license issuance URL,
http://license_issuer.com/licenseAcqURL?Content_id=0001%2F000000000001
(Ii)
It becomes such a value. “% 2F” is a value obtained by URL-encoding “/”.

  In the “encapsulation parameter creation process (step S93)”, the attribute information in which the content ID has been embedded in the “content ID embedding process (step S92)” and the input acquired in the “encapsulation instruction analysis process (step S90)”. Using the output file name as input, collect the parameters used in DRM encapsulation (written in the header of the capsule content at the time of encapsulation) acquired in the “encapsulation instruction analysis process (step S90)”, and the DRM Create the encapsulation parameters required for method encapsulation. Also, using the encapsulation parameters, a designated DRM-type encapsulation program (DRM1 to DRMn provided in the encapsulation execution means 12 shown in FIG. 6) is called (step S93).

  Specifically, an encapsulation parameter as shown in FIG. 17 is created, and an encapsulation program (for example, DRM1) of a designated DRM method (for example, “DRM1”) is called. Since the types of encapsulated parameters differ depending on the DRM method, the parameters necessary for each DRM method are described by describing the types of parameters necessary for each DRM method in a file that is read when the program is started, such as an initial setting file. To collect. If the parameter to be collected is not included in the attribute information, a specified value such as an initial setting file can be used, or if the parameter is not an essential item, the parameter can be omitted.

  When the “pre-encapsulation process (step S81)” is thus completed, the “encapsulation execution process (step S82)” shown in FIG. 8 is subsequently executed.

  In the “encapsulation execution process (step S82)”, the encapsulation parameter and the content ID created in “pre-encapsulation process (step S81)” are input, and the input file name included in the content ID and the encapsulation parameter is used as a basis. The digital content to be encapsulated is acquired from the content DB 14, and the DRM encapsulating program called in the “pre-encapsulation process (step S81)” is started based on the digital content and the encapsulating parameter to encapsulate. To obtain capsule content and key information (step S82).

  Here, the contents of the key information differ depending on the DRM method. For example, as shown in FIG. 18, the DRM method used for encapsulation, the content ID, various key information, and the like are described using a description language such as XML.

  In the “encapsulation information storage process (step S83)”, the capsule content and key information created in the “encapsulation execution process (step S82)” are stored in the encapsulation information storage means 13 shown in FIG. 6 in association with the content ID. In response to the request, the capsule content and the key information are distributed (step S83).

  Here, the distribution destination of the capsule content is the user terminal device 4, and the distribution destination of the key information is the license generation device 2. As a capsule content distribution method, the entire content may be downloaded at once, or a part of the content data may be transmitted according to the user's viewing using streaming technology.

  Next, the flow of processing in the user terminal device 4 in the first embodiment will be described in detail with reference to the flowchart shown in FIG. Here, as shown in FIG. 10, the flow of processing in the user terminal device 4 in the first embodiment is “content acquisition processing (step S100)”, “viewing control processing (step S101)”, “content viewing”. Processing (Step S102) ”.

  In the “content acquisition process (step S100)”, the encapsulation information storage unit 13 of the encapsulation device 1 is accessed, and the capsule content is acquired based on the content ID (step S100). At this time, the user directly inputs the content ID, or searches and inputs the content ID of the desired content from the content attribute information (title, author, etc.).

  In the “viewing control process (step S101)”, it is determined whether or not the capsule content acquired in the “content acquisition process (step S100)” is viewable on the user terminal device 4. Using the key information described in the DRM-specific license, the capsule content is decrypted into digital content, and the digital content is sent to the “content viewing process (step S102)” (step S101).

  Here, the viewable state means that a DRM-specific license for viewing the capsule content exists on the user terminal device 4, and the user or the user terminal device 4 is described in the DRM-specific license. This is the case when the conditions for use permission are satisfied.

  If the DRM-specific license does not exist on the user terminal device 4, a license issue request is transmitted to the license issue URL embedded in the capsule content, the DRM-specific license is acquired from the license issue request destination, The license is stored in a license storage area on the user terminal device 4. The contents of the license issuance request differ depending on the DRM method, but for example, the header information of the capsule content and the unique information (MAC address, IP address, etc., and data obtained by encrypting them) of the user terminal device 4 are sent. The license issuance request is generally transmitted as an HTTP request from the user terminal device 4 using a Web browser function.

  In the “content viewing process (step S102)”, a signal that can output the digital content decrypted in the “viewing control process (step S101)” to an output device (display, speaker, etc.) on the user terminal device 4. And output to the output device so that the user can view the content (step S102).

  The “viewing control process (step S101)” and the “content viewing process (step S102)” are performed by decrypting the capsule content into the digital content, so that the digital content data is not leaked to the outside. This process needs to be concealed from the external device. In addition, “viewing control processing (step S101)” and “content viewing processing (step S102)” differ in processing depending on the DRM method, the type of media, and the like, and therefore a dedicated processing program is required.

  Next, the flow of processing in the service providing apparatus 3 according to the first embodiment will be described in detail with reference to the flowchart shown in FIG. Here, as shown in FIG. 11, the flow of processing in the service providing apparatus 3 according to the first embodiment is “service reception processing (step S110)”, “sales right information acquisition processing (step S111)”, “license”. Generation request processing (step S112) ”,“ license information acquisition processing (step S113) ”, and“ license issuance processing (step S114) ”.

  In “service acceptance process (step S110)”, a license issuance request sent from the user terminal device 4 is accepted, and a content ID and DRM specific data are extracted from the license issuance request (step S110).

In this “service acceptance process (step S110)”, the license issuance request sent from the user terminal device 4 is received via the web server. At this time, as shown in the above (ii), since the content ID is included as the URL parameter in the license issuance URL, the content ID can be acquired from the URL parameter using the function of the Web server. . For example, in the case of the license issuance URL shown in (ii),
Content _id = 0001% 2F000000000001 (iii)
Is stored in the array. Further, the content ID ("0001/000000000001" in the above example) can be obtained by URL decoding this value and disassembling the item.

  Further, although the transmission method of DRM specific data from the user terminal device 4 differs depending on the DRM method, it is generally transmitted using the HTTP POST method. In this case, the “service reception process (step S110)” can receive the transmission data from the web server via the standard input. Since the transmission data is URL-encoded or BASE64-encoded as in the case of acquiring the content ID, the transmission data is decoded by a corresponding method and further decomposed into items so that DRM-specific data (for example, DRM-specific data) "U1") can be obtained.

  Further, in the “service reception process (step S110)”, it is possible to interactively interact with the user (user terminal device 4) and perform various procedures for issuing a license (user authentication, billing process, etc.). it can.

  In the “sales right information acquisition process (step S111)”, the sales management DB 35 is accessed based on the content ID acquired in the “service reception process (step S110)”, and the sales right information of the content having the content ID is acquired. (Step S111).

  Here, the sales rights information stored in advance in the sales management DB 35 may be used as it is, or the sales rights acquired from the sales management DB 35 by interactively interacting with the user (user terminal device 4). You may edit information dynamically according to a user's usage. However, when dynamically editing the sales right information, it is necessary to set within the range of conditions set in advance by the content distributor.

  In the “license generation request process (step S112)”, a license is generated from the content ID, the DRM specific data, and the sales right information acquired in the “service reception process (step S110)” and the “sales right information acquisition process (step S111)”. Data is generated, and the license generation data is transmitted as a license generation request to the license generation apparatus 2 via the network (step S112).

  For example, as shown in FIG. 4, the license generation data includes a tag (challengeInfo) for storing DRM-specific data and a tag (issueID) for storing a content ID in the sales right information shown in FIG. Created by assigning a value. The license generation request is executed as an HTTP request, and the license generation data is transmitted using the HTTP POST method. Here, the method of adding the content ID and DRM specific data to the sales right information as the license generation data and transmitting it as a bundle of data has been described. It is also possible to send it in parts.

  In the “license information acquisition process (step S113)”, the license transmission data generated by the license generation apparatus 2 based on the license generation request requested in the “license generation request process (step S112)” is transmitted via the network. Obtained from the generation device 2 (step S113).

  Here, since the license transmission data is transmitted from the license generation apparatus 2 as an HTTP response, the “license information acquisition process (step S113)” receives the HTTP response and analyzes the contents to transmit the license. You can receive credit data. For example, when the license generation device 2 stores and transmits license transmission data in a message body of an HTTP response, the “license information acquisition process (step S113)” extracts the message body portion of the HTTP response and transmits the license. Get credit data. Further, when there are a plurality of messages from the license generating apparatus 2, license transmission data can be transmitted and received using the HTTP multipart format.

  In the “license issuance process (step S114)”, the DRM-specific license is distributed to the user terminal device 4 using the license transmission data acquired in the “license information acquisition process (step S113)” (step S114).

  Here, the “license issuance process (step S114)” is performed by inserting the license transmission data into the message body portion of the HTTP response to the license issuance request transmitted from the user terminal device 4 as an HTTP request. Regardless of the DRM, the DRM-specific license can be distributed to the user terminal device 4.

  Specifically, for example, when license transmission data as shown in FIG. 5 is inserted into the message body part of the HTTP response sent from the service providing apparatus 3 to the user terminal apparatus 4 and transmitted to the user terminal apparatus 4, The Web browser of the user terminal device 4 interprets the HTML and Java Script described in the license transmission data, starts up the necessary program, and assigns the DRM-specific license “L1” to the license storage area on the user terminal device 4 To store.

  Further, by editing the HTML of the license transmission data and inserting advertisements and recommendation information, the advertisement and recommendation information can be presented to the user. Furthermore, if advertisements and recommendation information for each user are stored in the sales management DB 35, different information for each user can be dynamically presented.

  Next, the flow of the license information setting process in the license generation apparatus 2 according to the first embodiment will be described in detail with reference to the flowchart shown in FIG. Here, as shown in FIG. 12, the flow of the license information setting process in the license generating apparatus 2 according to the first embodiment is “license information registration process (step S120)” and “license information deletion process (step S121)”. Consists of

  This license information setting process provides an interface for the content distributor to register or delete license information necessary for the license generator 2 to generate a license in response to a request from the content distributor. To do.

  In the “license information registration process (step S120)”, the content ID of the digital content, the DRM method and key information used for encapsulation, and the distribution right information are associated with each other and stored in the license DB 24 (step S120).

  At this time, the content distributor inputs the content ID and the DRM method, acquires the distribution right information from the IPR-DB 15 based on the content ID, and the key information from the encapsulated information storage unit 13 based on the content ID. get. Here, the registration of the license information means permission for the content distributor to issue the content license to the content distributor.

  In the “license information deletion process (step S121)”, the license information of the content ID designated by the content distributor is deleted from the record of the license DB 24 (step S121).

  At this time, the content distributor inputs the content ID of the content to be deleted. Here, the deletion of the license information means that the content distributor refuses to issue the content license to the content distributor. That is, by performing this “license information deletion process (step S121)”, it is possible to stop the sales of the corresponding content for the content seller who has performed an illegal act.

  Next, the flow of the license generation process in the license generation apparatus 2 according to the first embodiment will be described in detail with reference to the flowcharts shown in FIGS. Here, as shown in FIG. 13, the flow of the license generation process in the license generation apparatus 2 according to the first embodiment includes “license generation pre-processing (step S130)”, “license generation execution process (step S131)”, “License information transmission processing (step S132)”. Hereinafter, the “license generation execution process (step S131)” may be referred to as “individual DRM license generation process (step S131)”.

  In the “license generation pre-processing (step S130)”, the license generation request sent from the service providing apparatus 3 is received, the license generation data included in the license generation request, and the license information record stored in the license DB 24, To collect information necessary for the license generation process, authenticate the sales right information included in the license generation data, create an individual DRM license generation request for generating a license of the specified DRM method, The designated individual DRM license generation process (the process of the individual DRM license generation unit shown in FIG. 6) is called (step S130).

  Next, a detailed processing flow of “license generation preprocessing (step S130)” will be described with reference to FIG. Here, the “license generation pre-processing (step S130)” includes, as shown in FIG. 14, “license generation request acceptance processing (step S140)”, “license information acquisition processing (step S141)”, “right information authentication processing”. (Step S142) ”and“ Individual DRM License Generation Request Processing (Step S143) ”.

  In the “license generation request reception process (step S140)”, a license generation request sent from the service providing apparatus 3 via the network is received, the license generation data included in the license generation request is acquired, and the license generation is performed. The content ID, DRM specific data, and sales right information are extracted by analyzing the contents of the business data (step S140).

  Here, since the license generation request is transmitted as an HTTP request to the web server of the license generation apparatus 2 and the license generation data is transmitted using the POST method of the HTTP, the “license generation request reception process (step S140)”. The license generation data can be acquired from the Web server via the standard input. In addition, content ID, DRM-specific data, and sales right information can be extracted from the license generation data by analyzing the acquired license generation data using software that interprets an XML document such as an XML parser. it can.

  Specifically, for example, in the case of the license generation data shown in FIG. 4, the content ID “0001/000000000001”, the DRM specific data “U1”, and the sales right information shown in FIG. Extracted. Note that if the content ID, DRM-specific data, and sales rights information are sent as separate parts using the HTTP multi-part format as a license generation request, an XML parser is not necessary and a value may be acquired for each part. . Also, it is conceivable to authenticate the content distributor of the license generation request source in the “license generation request reception process (step S140)”.

  In the “license information acquisition process (step S141)”, the license DB 24 is accessed based on the content ID acquired in the “license generation request reception process (step S140)”, and the DRM method and key information associated with the content ID are obtained. And a record of distribution right information are acquired (step S141).

  If the license information of the content ID specified in the license DB 24 does not exist, the content distributor has not permitted the issuance of the license for the content with the content ID, so the license generation process is interrupted and an error is given to the content distributor. Send a message (license cannot be generated).

  In the “right information authentication process (step S142)”, the sales right information acquired in the “license generation request reception process (step S140)” and the distribution right information acquired in the “license information acquisition process (step S141)” are input. The sales rights information and the distribution rights information are compared, and the validity of the sales rights information sent from the content distributor is inspected (step S142).

  As a check of the validity, in the first embodiment, whether the tag structure of the distribution right information corresponding to the sales right information is the same, and the value of the license condition of the sales right information is the use permission condition of the distribution right information. Check whether it is within the range of the specified value. As a result of the inspection, if it is determined to be valid, the process proceeds to the next process. If it is determined not to be valid, it is considered that the description of the sales license condition is invalid, the license generation process is interrupted, and the content distributor An error message (license cannot be generated) is sent to.

  Specifically, for example, as shown in FIG. 2 and FIG. 3, the sales rights information and the distribution rights information have the same tag structure, the sales rights information can be reproduced (3 times), and the expiration date and time When the value (March 15, 2005 0: 0: 0) is within the range specified in the distribution rights information (10 times and March 15, 2010 0: 0: 0) Judged to be legitimate. In addition, it may be possible to perform a more flexible validity check by using a tag structure check based on an XML schema or a table defining a comparison condition of right information.

  Here, as individual DRM methods, Microsoft's Windows Media Rights Management (WMRM: http://www.microsoft.com/windows/windowsmedia/drm.aspx) and Real Networks Real System Media Commerce Suite (RSMCS: (http://www.jp.realnetworks.com/products/mcs/index.html) and the rights information description unique to each DRM system and XrML An example of the correspondence table is shown in FIG.

  In the figure, “<” is judged to be valid when “sales rights information ≦ distribution rights information”, and “>” is valid when “sales rights information ≧ distribution rights information”. “=” Is determined to be valid when “sales rights information = distribution rights information”, and “⊆” is determined to be valid when “sales rights information—distribution rights information”. “⊇” indicates that “sales rights information⊇distribution rights information” is determined to be valid.

  In FIG. 19, “Type” indicates the type of tag (right or condition) when describing in XrML, and “XrML tag (core, sx, cx schema)” is the basic definition of XrML. Indicates a tag that can be described by a certain XrML Core Schema, Standard Extension Schema, Content Extension Schema, and "XrML tag (unique NameSpace)" indicates a tag that can be described by a schema defined independently other than core, sx, cx. “Meaning” indicates the meaning of each right information, “WMRM item” indicates a variable of the right information description that can be used in WMRM, “RSMCS item” indicates a variable of the right information description that can be used in RSMCS, “Condition” indicates a comparison condition when the rights range of the sales right information and the distribution right information is compared in the “right information authentication process (step S142)”.

  The table shown in FIG. 19 corresponds to the right description conversion table 226 shown in FIG. 7. By using the table shown in FIG. 19, the right information described in XrML is converted into individual DRM method right information. Can be converted.

  In the “individual DRM license generation request process (step S143)”, the DRM specific data and sales right information acquired in the “license generation request reception process (step S140)” and the “license information acquisition process (step S141)” are acquired. An individual DRM license generation request is created from the key information, and the corresponding individual DRM license generation process (individual DRM license generation means shown in FIG. 6) is based on the DRM method acquired in the “license information acquisition process (step S141)”. The individual DRM license generation request is transmitted to (step S143).

  At this time, as an individual DRM license generation request, key information, DRM-specific data, and sales right information are sent as separate parts to the individual DRM license generation process using the HTTP multi-part format.

  When the “license generation pre-processing (step S130)” is completed according to the flowchart shown in FIG. 14, the “license generation execution processing (step S131)” shown in FIG. 13 is subsequently executed.

  In the “license generation execution process (step S131)”, the individual DRM license generation request sent from the “license generation preprocessing (step S130)” is changed to the corresponding individual DRM license generation process (the individual DRM license shown in FIG. 6). Generating means), generates a DRM specific license based on the individual DRM license generation request, and generates license transmission data for transmitting the DRM specific license to the user terminal device 4 (step S131).

  At this time, since the “license generation pre-processing (step S130)” is transmitted as an individual DRM license generation request in the HTTP multi-part format, the key information, DRM-specific data, and sales rights information are separated into separate parts, respectively. The individual DRM license generation process (individual DRM license generation means shown in FIG. 6) acquires a value for each part, and obtains key information, DRM specific data, and sales right information.

  Next, a detailed processing flow of “license generation execution processing (step S131)”, that is, “individual DRM license generation processing (step S131)” will be described with reference to FIG. Here, the “individual DRM license generation processing (step S131)” includes, as shown in FIG. 15, “key information analysis processing (step S150)”, “DRM specific data analysis processing (step S151)”, “sales rights information”. Analysis processing (step S152) ”,“ license generation parameter creation processing (step S153) ”,“ license generation program processing (step S154) ”, and“ license transmission data creation processing (step S155) ”.

  In the “key information analysis process (step S150)”, key information is input and key information parameters necessary for generating an individual DRM license are extracted from the key information (step S150).

  Specifically, when key information as shown in FIG. 18 is input, the key information “K1”, “K2”, “K3”, and “K4” are converted into key information parameters (keys necessary for decryption of capsule contents). Information). Note that the content of the key information parameter differs for each individual DRM method.

  In “DRM specific data analysis processing (step S151)”, DRM specific data is input, and DRM specific parameters necessary for generating an individual DRM license are extracted from the DRM specific data (step S151).

  Specifically, the DRM-specific data is different for each individual DRM method, but generally includes capsule content header information and terminal-specific information, and the DRM-specific parameter is used to generate an individual DRM license from the DRM-specific data. Necessary data such as terminal specific information is extracted and described.

  In the “sales rights information analysis process (step S152)”, the sales rights information is input, and the rights description conversion table 226 in which the correspondence between the rights information description unique to the individual DRM system and XrML is described is input. A right information parameter, which is a right information description unique to the individual DRM method, is extracted from the sales right information using the right description conversion table 226 (step S152).

  Specifically, as the right description conversion table 226, for example, the table shown in FIG. 19 described above can be used. Also, at this time, values as shown in FIG. 3 are input as sales rights information, and when the individual DRM method is WMRM, the rights information parameters are “Playcount = 3”, “ExpirationDate = 2005-03-15T00: 00 : 00 "is extracted. Note that the right description conversion table 226 may be a table as described above, or XSLT (http: //), which is a simple language for converting a document described in XML into another XML document. www.w3.org/TR/xslt).

  In the “license generation parameter creation process (step S153)”, the key information parameter, the DRM specific parameter, and the right information parameter are input, and the license generation parameter necessary for starting the license generation program specific to the individual DRM method is input. The license generation program is activated using the license generation parameters (step S153).

  Here, the description format of the license generation parameter differs for each individual DRM system, and is described according to the description format (interface specification) defined by the license generation program of the individual DRM system.

  In the “license generation program process (step S154)”, the license generation program started by the license generation parameter created in the “license generation parameter creation process (step S153)” is executed, and the key information parameter and the use license condition information are executed. And a DRM-specific license including terminal-specific information (step S154).

  Here, examples of the license generation program include the WMRM Packeger and RSMCS Package described above.

  In the “license transmission data creation process (step S155)”, the DRM-specific license generated by the license generation program and the license transmission that is a script template for transmitting the DRM-specific license to the user terminal device 4 are sent. Using the credit data template 227 as an input, license transmission data is created by embedding the DRM-specific license in the license transmission data template 227 (step S155).

  Specifically, for example, if the DRM-specific license is “L1”, license transmission data as shown in FIG. 5 is created. At this time, the license transmission data template 227 is a portion excluding the value of the DRM-specific license “L1” in the example shown in FIG.

  When the “license generation execution process (step S131)” is completed according to the flowchart shown in FIG. 15, the “license information transmission process (step S132)” shown in FIG. 13 is subsequently executed.

  In the “license information transmission process (step S132)”, the license transmission data generated in the “license generation execution process (step S131)” is transmitted to the service providing apparatus 3 that is the license generation request source (step S132).

  Here, the license transmission data is transmitted from the license generation apparatus 2 to the service provision apparatus 3 (HTTP response) as a reply to the license generation request (HTTP request) transmitted from the service provision apparatus 3 to the license generation apparatus 2. The At this time, for example, when the license transmission data is stored and transmitted in the message body of the HTTP response, or there are a plurality of messages from the license generation device 2, the license transmission data is transmitted using the HTTP multipart format. It is possible to send.

  Next, a second embodiment of the present invention will be described in detail with reference to the drawings.

  20 and 21 are block diagrams showing the configuration of the second embodiment. In the figure, as in the first embodiment, 1 is an encapsulating device, 2 is a license generating device, 3 is a service providing device, and 4 is a user terminal device.

<Overall configuration>
As shown in FIG. 20, the encapsulation device 1 is similar to the first embodiment in that the encapsulation command means 10, the pre-encapsulation processing means 11, the encapsulation execution means 12, the encapsulation information storage means 13, the content DB 14, the IPR -It consists of DB15. Further, the pre-encapsulation processing means 11 is composed of an encapsulation command analysis means 110, an attribute information acquisition means 111, a content ID embedding means 112, and an encapsulation parameter creation means 113, as in the first embodiment. The means 12 is composed of a plurality of encapsulated programs (DRM1 to DRMn) as in the first embodiment.

  The license generation device 2 includes a license information setting unit 20, a license generation preprocessing unit 21, a license generation execution unit 22, a license information transmission unit 23, a license DB 24, and a service resolve unit 25. Further, the license generation preprocessing unit 21 includes a license generation request reception unit 210, a license information acquisition unit 211, a right information authentication unit 212, and an individual DRM license generation request generation unit 213, as in the first embodiment. The execution means 22 is composed of a plurality of individual DRM license generation means (DRM1 to DRMn) as in the first embodiment.

  As shown in FIG. 21, the service resolver 25 newly provided in the second embodiment includes a license issuance request accepting unit 250, a service determining unit 251, a redirect data creating unit 252, and a redirect data template 253.

  As shown in FIG. 7, each individual DRM license generating means (DRM1 to DRMn) includes a key information analyzing means 220, a DRM specific data analyzing means 221, a sales right information analyzing means 222, a license, as shown in FIG. It includes a generation parameter creation unit 223, a license generation program 224, a license transmission data creation unit 225, a right description conversion table 226, and a license transmission data template 227.

  Similarly to the first embodiment, the service providing apparatus 3 includes a service reception unit 30, a sales right information acquisition unit 31, a license generation request unit 32, a license information acquisition unit 33, a license issue unit 34, and a sales management DB 35. The

  Similarly to the first embodiment, the user terminal device 4 includes a content acquisition unit 40, a content viewing unit 41, and a viewing control unit 42.

  The user terminal device 4 and the service providing device 3 are connected via a network, and the service providing device 3 and the license generating device 2 are connected via a network. Further, the user terminal device 4 may be connected to the encapsulating device 1 via a network to acquire capsule content online, or may be offline via an information recording medium such as a CD or DVD. You may get it.

<Content DB 14 / Sales Management DB 35>
The content DB 14 and the sales management DB 35 have the same functions as those described in the first embodiment.

<License DB 24>
The license DB 24 includes the DRM method and key information used for encapsulating the digital content, the content distribution right information, and the address of the service accepting unit 30 of the service providing apparatus 3 that actually provides services such as license issuance. The service URL is stored in association with the corresponding content ID.

<IPR-DB (Intellectual Property Database) 15>
The IPR-DB 15 stores content attribute information and distribution right information expressed in a standardized form. Here, for each content, content attribute information and distribution right information are described and stored in a common format independent of the DRM method.

  The content attribute information includes attributes of the content itself such as the title and type of the content, copyright information such as a producer name and production date, a location where a license is issued (license issuance URL), and the like. In the second embodiment, it is assumed that the URL of the service resolving unit 25 of the license generating device 2 is described as the license issuance URL. The distribution right information includes usage permission condition information such as a viewable period and a reproducible number of times. In addition, a content identifier (content ID) for uniquely identifying the content is managed.

  The contents of the IPR-DB 15 are generally registered in advance by a content producer and a content distributor at the start of content distribution.

<Description of operation>
In the second embodiment, the operations in the encapsulation command process, the pre-encapsulation process, the encapsulation execution process, and the encapsulation information storage process of the encapsulation apparatus 1 are the same as those described in the first embodiment. The operations of the user terminal device 4 in content acquisition processing and content viewing processing are the same as those described in the first embodiment.

  Furthermore, the operations in the service reception process, the sales right information acquisition process, the license generation request process, the license information acquisition process, and the license issuance process of the service providing apparatus 3 are the same as those described in the first embodiment. Further, the operations of the license generation device 2 in the pre-license generation process, the license generation execution process, and the license information transmission process are the same as those described in the first embodiment.

  In the license information setting process of the license generation apparatus 2, in addition to the license information described in the first embodiment, a service URL (service reception) that is an address of a service reception process of the service providing apparatus 3 that actually provides a service such as license issuance. Registration and deletion of the URL of the means 30). At this time, the service URL is input by the content distributor in association with the content ID. Other operations are the same as those described in the first embodiment described with reference to the flowchart of FIG.

  In the viewing control process of the user terminal device 4, in addition to the operation described in the first embodiment, if the DRM-specific license does not exist on the user terminal device 4, the license issuance URL embedded in the capsule content is first (In the second embodiment, at the time of encapsulation, a license issuance request is transmitted to the license issuance URL as the license issuance URL embedded in the service resolving process URL of the license generation device 2 described in IPR-DB 15). Using the redirect data returned from the license issuance request destination based on the issuance request, the data is redirected to the service providing apparatus 3 that actually provides a service such as license issuance as the transmission destination of the license issuance request.

  Here, since the normal redirect process is automatically executed by the web browser of the user terminal device 4, the user need not be aware of the redirect process. The redirect data can be described using HTML and Java Script as shown in FIG. 22, for example.

  In the service resolving process of the license generation device 2, a license issuance request sent from the user terminal device 4 via the network is received, and the license DB 24 is accessed based on the content ID included in the license issuance request to access the content. A service URL associated with the ID is acquired, redirection data for redirecting a license issuance request to the service URL is created, and the redirection data is transmitted to the user terminal device 4.

  As shown in FIG. 23, the flow of the service resolving process in the license generating apparatus 2 according to the second embodiment is “license issuance request acceptance process (step S230)”, “service determination process (step S231)”, “redirection use”. Data creation processing (step S232) ".

  In the “license issuance request acceptance process (step S230)”, the license issuance request sent from the user terminal device 4 is accepted, the content ID and DRM specific data are extracted from the license issuance request, and the content ID and DRM are extracted. “Service determination process (step S231)” and “redirect data creation process (step S232)” are called from the unique data to create redirect data and transmit it to the user terminal device 4 (step S230).

  Here, the extraction of the content ID and the DRM specific data can be extracted from the license issuance request by the same method as the operation described in the service reception process of the first embodiment. The acceptance of the license issuance request and the transmission of the redirect data are processed as an HTTP request from the user terminal device 4 and an HTTP response to the user terminal device 4 using the Web server.

  In the “service determination process (step S231)”, the content ID acquired in the “license issuance request acceptance process (step S230)” is input, and the license DB 24 is accessed based on the content ID, and is associated with the content ID. A service URL is acquired (step S231).

  Here, the service URL describes the address of the service reception process of the service providing apparatus 3 that actually provides a service such as a license issuance.

  In the “redirect data creation process (step S232)”, the content ID and DRM specific data acquired in the “license issuance request reception process (step S230)”, the service URL acquired in the “service determination process (step S231)”, and , A redirection data template 253 in which a script template for redirecting a license issuance request to the service URL on the user terminal device 4 is input, and the redirection data template 253 includes the service URL, The redirection data is created by embedding the content ID and the DRM specific data (step S232).

  The redirect data template 253 input at this time can be described using HTML and Java Script, for example, as shown in FIG. Further, the portions surrounded by <% =...%> On the 12th and 13th lines in FIG. 24 indicate the embedded positions of the service URL, content ID, and DRM specific data, respectively.

  In the “redirect data creation process (step S232)”, the service URL (http://license_issuer.com/licenseAcqURL), content ID (0001/000000000001), DRM specific data (DRM specific data “DRM specific data“ By embedding the value of U1 "), redirection data as shown in FIG. 22 can be created.

  Here, in the second embodiment, the service resolving unit 25 is arranged in the license generating device 2, the service URL is stored in the license DB 24 on the license generating device 2, and the license issuance request is redirected. The resolver 25 may be placed anywhere as long as it can be accessed from the user terminal device 4.

  As described above, according to the present invention, content distribution management can be performed using right information described using a common description format (language) that does not depend on individual DRM schemes. Even when the method is applied, there is an effect that it is not necessary to add new right information. This makes it possible to construct a content distribution management system that can cope with a DRM system that will be provided in the future.

  According to the present invention, content distributors can distribute distribution rights information created by a content distributor within the scope of a contract with the content distributor, or within the conditions determined in advance by the license generating device. There is an effect that it is possible to create sales right information by changing the contents, generate a license by the license generation apparatus based on the sales right information, and distribute the license to the user. This makes it possible to construct a content distribution management system that allows flexible setting of rights information on the content distributor side.

  Furthermore, according to the present invention, the service providing apparatus performs analysis of DRM specific data depending on individual DRM methods and generation of a script for distributing a DRM specific license to a user terminal on the license generating apparatus side. Even when a new DRM method is applied, there is an effect that it is not necessary to add a new service providing program. As a result, when a new DRM method is applied, it is possible to construct a content distribution management system that can cope with it without changing the service providing apparatus.

  Furthermore, according to the present invention, it is possible to redirect the license issuance request sent from the user terminal device to the service URL registered in advance in the license DB by the service resolving process. Even when the URL is changed, there is an effect that it is not necessary to re-encapsulate the content. Thereby, even when the URL of the service providing apparatus is changed, it is possible to construct a content distribution management system that can use the content encapsulated so far as it is.

  Furthermore, according to the present invention, it is possible to automate the right authentication between the content distributor and the content distributor by checking the validity of the sales right information created by the content distributor by the license generation device. effective. This makes it possible to construct a content distribution management system that does not require complicated procedures for right authentication.

  Furthermore, according to the present invention, since the license generation device creates a DRM-specific license for each individual DRM method and distributes it to the user terminal device, it is possible to perform content viewing control specific to the DRM method. There is. As a result, it is possible to construct a content distribution management system that enables content viewing control specific to the DRM system without complicating complicated procedures.

It is a figure which shows the flow of the various data in Example 1, and the outline | summary of a process. It is a figure which shows an example of distribution right information. It is a figure which shows an example of sales right information. It is a figure which shows an example of the data for license production | generation. It is a figure which shows an example of the data for license transmission. 1 is a diagram illustrating an overall configuration of Example 1. FIG. It is a figure which shows the detailed structure of an individual DRM license production | generation means. It is a figure which shows the flow of a process in an encapsulation apparatus. It is a figure which shows the flow of a detailed process of the encapsulation pre-process. It is a figure which shows the flow of a process in a user terminal device. It is a figure which shows the flow of a process in a service provision apparatus. It is a figure which shows the flow of the registration deletion process of license information in a license production | generation apparatus. It is a figure which shows the flow of the license production | generation process in a license production | generation apparatus. It is a figure which shows the flow of a detailed process of a license production | generation pre-processing. It is a figure which shows the flow of a detailed process of an individual DRM license production | generation process. It is a figure which shows an example of content attribute information. It is a figure which shows an example of the encapsulation parameter. It is a figure which shows an example of key information. It is a figure which shows an example of a right description conversion table. FIG. 6 is a diagram illustrating an overall configuration of a second embodiment. It is a figure which shows the detailed structure of a service resolver. It is a figure which shows an example of the data for redirection. It is a figure which shows the flow of the service resolve process in a license production | generation apparatus. It is a figure which shows an example of the data template for redirection. It is explanatory drawing of a prior art.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Encapsulation apparatus 2 License generation apparatus 3 Service provision apparatus 4 User terminal apparatus 10 Encapsulation instruction means 11 Encapsulation preprocessing means 12 Encapsulation execution means 13 Encapsulation information storage means 14 Content DB
15 IPR-DB
20 License information setting means 21 License generation preprocessing means 22 License generation execution means 23 License information transmission means 24 License DB
25 Service Resolving Unit 30 Service Accepting Unit 31 Sales Rights Information Obtaining Unit 32 License Generation Requesting Unit 33 License Information Obtaining Unit 34 License Issuing Unit 35 Sales Management DB
40 content acquisition means 41 content viewing means 42 viewing control means

Claims (20)

An encapsulating apparatus used in a DRM system in which content encapsulated by an arbitrary DRM method can be viewed with a license according to the DRM method,
Means for registering distribution right information of contents described in a language independent of the DRM method in the storage means;
Means for encapsulating content in an arbitrary DRM system and registering it in the storage means, and registering in the storage means key information used for encapsulation and DRM system identifier information indicating which DRM system is used;
A capsule comprising: distribution right information stored in the storage means; key information and DRM system identifier information stored in the storage means; and means for notifying a device that performs license generation processing. Device. A license generating apparatus used in a DRM system in which content encapsulated by an arbitrary DRM method can be viewed with a license according to the DRM method,
Obtain and store distribution rights information of content described in a language independent of the DRM method, key information used to encapsulate the content, and DRM method identifier information indicating which DRM method was used Means for registering with means;
Means for accepting a license generation request;
Means for obtaining distribution right information, key information, and DRM system identifier information about the content requested to be generated from the storage means;
Means for verifying the legitimacy of the sales right information by comparing the sales right information described in the language specified in the license generation request with the acquired distribution right information;
Based on the information specified in the license generation request, the sales right information, and the acquired key information, generate license information for the content with the license generation request according to the DRM method indicated by the acquired identifier information Means to
Means for transmitting the license information to the license generation request source. The license generation device according to claim 2,
The means for registering registers the address information of a device that provides content services in the storage means,
And a means for accepting a license issuance request;
Means for obtaining from the storage means the address information about the content specified in the license issue request;
A license generating apparatus comprising: means for notifying the acquired address information to the license issue request source. In the license generation device according to claim 2 or 3,
The means for verifying whether or not the sales rights information and the distribution rights information have the same tag structure, and a usage condition described in the sales rights information is used in the distribution rights information. A license generation apparatus that verifies whether or not a license is within a range of permission conditions. The license generation device according to any one of claims 2 to 4,
The generating means uses a conversion table of correspondence relationship between right information description specific to the DRM method and right information description written in a language independent of the DRM method, according to the DRM method indicated by the acquired identifier information. Generating a license information. A service providing apparatus used in a DRM system in which content encapsulated by an arbitrary DRM method can be viewed with a license according to the DRM method,
Means for obtaining distribution rights information of content described in a language independent of the DRM method;
Based on the obtained distribution right information, means for creating sales right information of content described in the language and registering it in the storage means;
Means for accepting a license issuance request;
Means for acquiring sales right information about the content requested to be issued based on the sales right information stored in the storage means;
Means for requesting generation of a license for the content having the license issuance request by designating the information designated in the license issuance request and the acquired sales right information to the apparatus that manages the license generation process; ,
Means for receiving license information returned in response to the license generation request and issuing the license information to the license issuance request source. The service providing apparatus according to claim 6,
The service providing apparatus, wherein the receiving unit executes a service for issuing a license and / or a service for providing information to a viewer of content. In the service provision apparatus of Claim 6 or 7,
The issuing means inserts advertisement and / or recommendation information into the license information and issues it to the license issue request source. A content viewing apparatus used in a DRM system in which content encapsulated in an arbitrary DRM method can be viewed with a license according to the DRM method,
Means for acquiring content encapsulated by any DRM method;
Means for requesting issuance of a license to a device pointed to by address information embedded in the encapsulated content when there is no license necessary for viewing the encapsulated content;
Means for receiving address information returned in response to the license issuance request;
Means for requesting issuance of a license again to the device indicated by the received address information;
Means for receiving license information returned in response to the license reissue request;
Means for decrypting the encapsulated content using the received license information. An encapsulation method used in a DRM system in which content encapsulated by an arbitrary DRM method can be viewed with a license according to the DRM method,
Registering the distribution right information of the content described in a language independent of the DRM method in the storage means;
A process of encapsulating content in an arbitrary DRM system and registering it in the storage means, and registering in the storage means key information used for encapsulation and DRM system identifier information indicating which DRM system is used;
A capsule comprising: a distribution right information stored in the storage unit; a key information stored in the storage unit; and a DRM system identifier information to a device that manages the license generation process. Method. A license generation method used in a DRM system in which content encapsulated by an arbitrary DRM method can be viewed with a license according to the DRM method,
Obtain and store distribution rights information of content described in a language independent of the DRM method, key information used to encapsulate the content, and DRM method identifier information indicating which DRM method was used Registering with the means,
The process of accepting a license generation request;
Obtaining distribution right information, key information, and DRM system identifier information about the content having the license generation request from the storage unit;
Verifying the legitimacy of the sales rights information by comparing the sales rights information described in the language specified in the license generation request with the acquired distribution rights information;
Based on the information specified in the license generation request, the sales right information, and the acquired key information, generate license information for the content with the license generation request according to the DRM method indicated by the acquired identifier information The process of
And a step of transmitting the license information to the license generation request source. The license generation method according to claim 11,
In the registration process, the address information of the device that provides the content service is registered in the storage means,
And a process of accepting a license issuance request;
Obtaining the address information about the content specified in the license issue request from the storage means;
And a step of notifying the acquired license information to the license issuance request source. The license generation method according to claim 11 or 12,
In the verification process, whether or not the tag structure of the sales right information and the distribution right information is the same, and the use permission condition described in the sales right information is used in the distribution right information. A license generation method comprising: verifying whether or not a license is within a range of permission conditions. The license generation method according to any one of claims 11 to 13,
In the generation process, the conversion table of the correspondence relationship between the rights information description unique to the DRM method and the rights information description described in a language independent of the DRM method is used to correspond to the DRM method indicated by the acquired identifier information. A license generation method characterized by generating generated license information. A service providing method used in a DRM system in which content encapsulated by an arbitrary DRM method can be viewed with a license according to the DRM method,
A process of obtaining distribution rights information of content described in a language independent of the DRM method;
Based on the obtained distribution right information, creating sales right information of content described in the language and registering it in the storage means;
The process of accepting a license issuance request;
Obtaining the sales right information about the content for which the license issuance is requested based on the sales right information stored in the storage unit;
A process of requesting a device that performs license generation processing to specify the information specified in the license issue request and the acquired sales right information, and to generate a license for the content having the license issue request; ,
Receiving the license information returned in response to the license generation request, and issuing the license information to the license issuance request source. A content viewing method used in a DRM system in which content encapsulated by an arbitrary DRM method can be viewed with a license according to the DRM method,
Acquiring content encapsulated by any DRM method;
Requesting a device to issue a license to a device indicated by address information embedded in the encapsulated content when there is no license required for viewing the encapsulated content;
Receiving address information returned in response to the license issuance request;
Requesting the device indicated by the received address information to issue a license again;
Receiving license information returned in response to the license reissue request;
A content viewing method comprising: decrypting the encapsulated content using the received license information. An encapsulation program used to realize an encapsulation method used in a DRM system in which content encapsulated in an arbitrary DRM scheme can be viewed with a license according to the DRM scheme,
A process for registering distribution right information of content described in a language independent of the DRM method in the storage means;
A process of encapsulating content in an arbitrary DRM method and registering it in the storage unit, and registering in the storage unit key information used for encapsulation and DRM method identifier information indicating which DRM method is used;
Capsule for causing a computer to execute distribution right information stored in the storage unit, key information stored in the storage unit, and DRM system identifier information to a device that manages license generation processing Program. A license generation program used for realizing a license generation method used in a DRM system in which content encapsulated in an arbitrary DRM method can be viewed with a license according to the DRM method,
Obtain and store distribution rights information of content described in a language independent of the DRM method, key information used to encapsulate the content, and DRM method identifier information indicating which DRM method was used Processing to register with the means;
Processing to accept a license generation request;
Processing for obtaining distribution right information, key information, and DRM identifier information about the content requested to be generated from the storage means;
A process for verifying the legitimacy of the sales right information by comparing the sales right information described in the language specified in the license generation request with the acquired distribution right information;
Based on the information specified in the license generation request, the sales right information, and the acquired key information, generate license information for the content with the license generation request according to the DRM method indicated by the acquired identifier information Processing to
A license generation program for causing a computer to execute processing for transmitting the license information to the license generation request source. A service providing program used for realizing a service providing method used in a DRM system in which content encapsulated by an arbitrary DRM method can be viewed with a license according to the DRM method,
Processing for obtaining distribution rights information of content described in a language independent of the DRM method;
Based on the obtained distribution right information, processing for creating sales right information of content described in the language and registering it in a storage means;
Processing to accept a license issuance request;
Processing for acquiring sales right information about the content requested to be issued based on the sales right information stored in the storage unit;
Processing for requesting generation of a license for the content having the license issuance request by designating the information designated in the license issuance request and the acquired sales right information to the apparatus that manages the license issuance processing; ,
A service providing program for causing a computer to execute a process of receiving license information returned in response to the license generation request and issuing the license information to the license issuance request source. A content viewing program used for realizing a content viewing method used in a DRM system in which content encapsulated in an arbitrary DRM method can be viewed with a license according to the DRM method,
A process of acquiring content encapsulated by an arbitrary DRM method;
Processing for requesting a license to be issued to a device indicated by address information embedded in the encapsulated content when there is no license required for viewing the encapsulated content;
A process of receiving address information returned in response to the license issuance request;
Processing for requesting issuance of a license to the device indicated by the received address information again;
Processing for receiving license information returned in response to the license reissue request;
A content viewing program for causing a computer to execute a process of decrypting the encapsulated content using the received license information.

Images