JP4981653B2 - Media content management system and media content management method - Google Patents

Description

  The present invention relates to a network media content management system and a media content management method.

  Conventionally, a technique for preventing unauthorized use of digital content distributed via a network has been considered.

For example, in Patent Document 1, in order to prevent illegal secondary use of digital content distributed via a network, a user terminal is authenticated for a client terminal that requests download, and a download is performed based on the authentication result. It is disclosed that a composition rule is set for a target digital content.
JP 2005-190440 A

  However, in the case of the technique described in Patent Document 1, it is possible to prevent unauthorized secondary use for a user who does not have a valid title. On the other hand, in the case of disseminating digital content by permitting secondary use, on the other hand, determining the composition rule for the digital content to be downloaded based on the authentication result may hinder the spread of secondary usage. It becomes. Further, from the viewpoint of providing digital content, there is also a problem that it is impossible to track and understand what kind of content the digital content provided by the user is secondary used.

An object of the present invention, taking the provider to allow secondary use of the media content is to facilitate the understanding of the contents of the secondary use media content.

The invention described in claim 1
First receiving means for receiving first media content input from the outside;
First storage management means for storing and managing the first media content received by the first receiving means;
Second receiving means for receiving product information input from the outside in order to generate second media content including the first media content and personal content to be combined with the first media content; ,
Obtaining means for obtaining the product information received by the second receiving means;
Second storage management means for storing and managing the product information received by the second receiving means in association with the first media content;
Third storage management means for storing and managing the personal content received by the second receiving means;
Generating means for generating the second media content based on the first media content, the product information, and the personal content by an external input;
Publishing means for publishing the second media content generated by the generating means to a network via a communication line;
When there is a download request from the outside, the second media content generated by the generation unit is digitally watermarked, and the second media content subjected to the digital watermark processing is outside the download request source. First transmitting means for transmitting;
It is characterized by having.

The invention according to claim 2 is the invention according to claim 1,
A judgment means for judging whether or not the product information is received by the second receiving means;
The acquisition unit acquires the product information determined to be received by the determination unit.

The invention according to claim 3 is the invention according to claim 2 ,
Generation program storage means for storing a generation program for the outside to generate the second media content;
Second transmission means for transmitting the generation program stored in the generation program storage means to the outside;
Is further provided.

The invention according to claim 4 is the invention according to any one of claims 1 to 3 ,
The first storage management means further stores creator information of the first media content in association with the first media content;
When the product information is acquired by the acquisition unit, the creator information of the first media content associated with the product information is extracted from the first storage management unit, and the extracted creation Notification means for notifying the creator based on the creator information;
Is further provided.

The invention according to claim 5 is the invention according to any one of claims 1 to 4 ,
The first media content is a CG image, the second media content is a captured image obtained by combining the CG image, and the product information indicates a combined state of the CG image combined with the captured image. It is characterized by including the synthesis parameters shown.

The invention described in claim 6
A first receiving step in which the first receiving means receives the first media content input from the outside;
A first storage management step for storing and managing the first media content received by the first reception step;
The second receiving means outputs the product information for generating the second media content including the first media content input from the outside, and the personal content for combining with the first media content. A second receiving step for receiving;
An obtaining unit for obtaining the product information received by the second receiving step;
A second storage management step for storing and managing the product information received in the second receiving step in association with the first media content;
A third storage management step for storing and managing the personal content received by the second reception step;
A generating step for generating the second media content based on the first media content, the product information, and the personal content according to an external request;
When there is a download request from the outside, the transmission means performs a digital watermark process on the second media content generated by the generation step, and downloads the second media content subjected to the digital watermark process. A transmission process to send to the original outside,
It is characterized by including.

  According to the present invention, it becomes easy for a provider who permits secondary use of media content to grasp the content of the media content that has been secondary used.

Embodiment 1
First, Embodiment 1 of the present invention will be described.
FIG. 1 shows a configuration example of a media content management system 1 according to the first embodiment. As shown in FIG. 1, the media content management system 1 includes a content management server 10, a user deliverable server 11, a user data management server 12, a DB (Data Base) server 20, a copyright management contract server 30, a billing server 40, The search server 50 and the application server 60 are configured, and the application server 60 and the user terminal 100 are connected via a communication network N so that data can be transmitted and received. The communication network N is constituted by a communication network such as a WAN (Wide Area Network) or the Internet, for example, but may include a LAN (Local Area Network) or the like, such as a telephone line, a dedicated line, a mobile communication network, a communication A satellite network, CATV (Cable Television) line, Internet provider, etc. may be included.

  Further, the content management server 10, user deliverable server 11, user data management server 12, DB server 20, copyright management contract server 30, billing server 40, search server 50, and application server 60 are as shown in FIG. Each is connected via a network such as a LAN so that data can be transmitted and received.

  The content management server 10, user deliverable server 11, user data management server 12, DB server 20, copyright management contract server 30, billing server 40, search server 50, application server 60, and user terminal 100 cooperate with the program. Each of them is composed of a CPU, a storage unit, a RAM (Random Access Memory), an input unit, a display unit, a communication unit, and the like.

The content management server 10 functions as a first storage management unit, and media as first media content uploaded via a copyright management contract server 30 by a creator who is a creator (creator) of media content. Content (hereinafter simply referred to as content) is stored and managed. The content is data to be sold to the user, for example, an object file composed of 3DCG (3Dimention Computer Graphics) created by a creator.
The user deliverable server 11 functions as a second storage management unit, and synthesizes image data such as photos (hereinafter referred to as personal content) uploaded by the user from the user terminal 100 and content uploaded by the creator, Information necessary for generating media content (hereinafter referred to as a product) generated as the second media content is stored and managed.
The user data management server 12 functions as a third storage management unit that stores and manages personal information such as the user's name and credit card information, and personal content uploaded by the user via the application server 60. Yes.

The DB server 20 includes a content DB 21, a product DB 22, and a user DB 23, and stores and manages information such as image data and various types of user information as a database. The contents of the database of the content DB 21 are copied to the content management server 10 and stored and managed by the content management server 10. The contents of the database of the deliverable DB 22 are copied to the user deliverable server 11 and stored and managed by the user deliverable server 11. The contents of the database of the user DB 23 are copied to the user data management server 12 and stored and managed by the user data management server 12.
The content management server 10, the user deliverable server 11, and the user data management server 12 periodically synchronize with the DB server 20 to match the contents. For example, synchronization may be performed every time a certain time has elapsed, or synchronization may be performed at a timing when personal content is uploaded from the user terminal 100 or the like.

FIG. 2 shows an example of data storage in the content DB 21.
As shown in FIG. 2, the content DB 21 is a database that stores information about content uploaded by creators, and is composed of a content DB main table T1. As shown in FIG. 2, the content DB main table T1 includes a “content ID” field, a “user ID” field, a “format” field, a “capacity” field, a “storage location” field, a “thumbnail storage location” field, “ It has a “keyword” field, a “genre” field, a “use price” field, and a “usable number” field.

  The “content ID” field stores a content ID uniquely assigned to the content uploaded by the creator. The “user ID” field stores a user ID uniquely assigned to the creator. The “format” field stores the data format of the content. The “capacity” field stores the data capacity of the content. The “storage location” field stores a directory in which content is stored. The “thumbnail storage location” field stores a directory in which thumbnails of content are stored. The “keyword” field stores a keyword used when searching for content desired by the user. The “genre” field stores the genre to which the content belongs. The “use price” field stores the use price of the content. The “usable number” field stores the number of times the content can be used.

FIG. 3 shows an example of data storage in the product DB 22.
The product DB 22 is a database that stores product information (composition parameters, content IDs, and personal content IDs, which will be described later) necessary for generating the products. As illustrated in FIG. The product DB main table T2, the used content table T3, and the used personal content table T4.

  FIG. 3A shows a data storage example of the product DB main table T2. The deliverable DB main table T2 is a table that stores basic information related to deliverables. As shown in FIG. 3A, the product DB main table includes a “product ID” field, a “production date” field, a “user ID” field, a “synthesis parameter” field, a “thumbnail storage location” field, and It has a “use log storage location” field.

  The “product ID” field stores a product ID uniquely assigned to each product. The “production date” field stores the date and time when each deliverable was created. The “user ID” field stores the user ID that created the deliverable. The “synthesis parameter” field stores a synthesis parameter related to the deliverable. The composite parameter is information indicating a composite state of content (an object file composed of 3DCG) created by a creator that displays personal content (image data such as a photograph) as a lower layer on a higher layer. In detail, coordinate information such as the size of the content to be combined and displayed, the combined display position, the display direction of the content, and the irradiation direction (lighting) of the light source irradiated to the content is shown. A deliverable is generated by synthesizing content and personal content based on this synthesis parameter. The “thumbnail storage location” field stores a directory in which thumbnails of deliverables are stored. The “use log storage location” field stores a directory that stores use logs obtained by a product release process described later.

  FIG. 3B shows a data storage example of the used content table T3. The used content table T3 stores the content ID of the content used when creating the deliverable. In the example of FIG. 3B, the number of contents that can be combined with one product is limited to four. As shown in FIG. 3B, the used content table T3 has a “delivered product ID” field, a “content ID1” field, a “content ID2” field, a “content ID3” field, and a “content ID4” field.

  The “product ID” field stores a product ID. The “content ID 1” field, the “content ID 2” field, the “content ID 3” field, and the “content ID 4” field store the content ID corresponding to the content used when creating the deliverable. When the number of used contents is 4 or less, a NULL value is stored in a field that does not store a content ID.

  FIG. 3C shows a data storage example of the used personal content table T4. The used personal content table T4 stores the personal content ID of the personal content used when creating the deliverable. In the example of FIG. 3C, the number of personal contents that can be combined with one product is up to four. As shown in FIG. 3C, the used personal content table T4 includes a “delivered product ID” field, a “personal content ID1” field, a “personal content ID2” field, a “personal content ID3” field, and a “personal content ID4”. "Field.

  The “product ID” field stores a product ID. The “Personal Content ID 1” field, “Personal Content ID 2” field, “Personal Content ID 3” field, and “Personal Content ID 4” field are the personal content uniquely assigned to the personal content uploaded by the user when the product is generated. Store the ID. When less than four personal contents are used, a NULL value is stored in the field that does not store the personal contents ID.

FIG. 4 shows an example of data storage in the user DB 23.
The user DB 23 stores information related to users, and includes a personal content table T5, a personal information table T6, and a purchase content table T7 as shown in FIG.

  FIG. 4A shows an example of data storage in the personal content table T5. The personal content table T5 stores information about personal content uploaded by the user. As shown in FIG. 4A, the personal content table T5 includes a “personal content ID” field, a “user ID” field, a “format” field, a “capacity” field, and a “storage location” field.

  The “personal content ID” field stores a personal content ID uniquely associated with each personal content. The “user ID” field stores a user ID. The “format” field stores the data format of the personal content. The “capacity” field stores the data capacity of the personal content. The “storage location” field stores the storage location of the personal content.

  FIG. 4B shows a data storage example of the personal information table T6. The personal information table T6 stores user personal information. As shown in FIG. 4B, the personal information table T6 includes a “user ID” field, a “password” field, a “name” field, a “mail address” field, and a “credit card information” field.

  The “user ID” field stores a user ID. The “password” field stores a password set for each user ID. The “name” field stores the name of the user. The “mail address” field stores the mail address of the user. The “credit card information” field stores the credit card information of the user.

  FIG. 4C shows a data storage example of the purchase content table T7. The purchase content table T7 stores information related to the content purchased by the user. As shown in FIG. 4C, the purchase content table T7 includes a “user ID” field, a “content ID” field, a “purchase date” field, and a “usage count” field.

  The “user ID” field stores a user ID. The “content ID” field stores the content ID of the content purchased by the user. The “purchase date” field stores the date when the content is purchased. “Use count” stores the remaining use count of the content purchased by the user.

  The copyright management contract server 30 functions as a first receiving means, and when the creator uploads content data to the content management server 10 by a terminal (not shown) owned by the creator, the copyright management contract server 30 copyrights the terminal owned by the creator. Consent to protection terms and request content data. A terminal (not shown) of the creator connects to the copyright management contract server 30 when uploading content data.

Hereinafter, the flow of an input operation when a creator uploads content data to the content DB 21 will be described with reference to the drawings.
FIG. 5 (a) shows a copyright management contract screen G1 displayed on the terminal of the creator when the creator uploads the content data. The copyright management contract screen G1 includes an area G1a in which the text of the copyright management contract is written, radio buttons G1b and G1c, an “OK” button G1d, and the like. The copyright management contract screen G1 is displayed on the login screen (not shown) transmitted from the copyright management contract server 30 when the terminal of the creator is connected to the copyright management contract server 30 and the creator's own user ID and A password is entered. Displayed after login to the copyright management contract server 30.
The user ID and password input at this time are authenticated by collating with the personal information table T6 stored in the user data management server 12 via the copyright management contract server 30. In this embodiment, a person who has a user ID can log in as a creator who uploads and sells content created by himself or as a user who purchases and uses other people's content. That is, the media content management system 1 can be used as a creator when connected to the copyright management contract server 30 and as a user when connected to the application server 60. On the other hand, when the media content management system 1 is used as a creator, a user ID different from the user ID used as a user may be input.

  When the “I agree” radio button G1b on the copyright management contract screen G1 is selected by the creator's operation and the “OK” button G1d is pressed, the screen changes to an upload data selection screen G2 described later. If the radio button G1c of “I do not agree” is selected and the “OK” button G1d is pressed, the screen is terminated as if the copyright management contract was not agreed.

  FIG. 5B shows an upload data selection screen G2 displayed when the creator uploads content data. The upload data selection screen G2 includes an “upload data selection” tag G2a, a “reference” button G2b, a “keyword” tag G2c, a “genre selection” tag G2d, a “usage count” tag G2e, a “use charge” tag G2f, and “ It is composed of G2g such as an “OK” button.

In the upload data selection screen G2, when a “reference” button G2b is pressed by a creator's operation and a folder storing image data to be uploaded is specified, content to be uploaded is displayed in an “upload data selection” tag G2a. Is specified. Next, a keyword is input to the “keyword” tag G2c by the operation of the creator. Then, the genre related to the content is selected in the “genre selection” tag G2d. In the example of the upload data selection screen G2, the “keyword” tag G2c can be freely input, and the “genre selection” tag G2d is selected from the pull-down menu. However, the input format is limited to this embodiment. is not.
Next, the number of times of using the content is input to the “use count” tag G2e and the “use charge” tag G2f by the creator's operation. In the example of FIG. 5B, if the user pays 50 yen, this content can be used five times.

When the “OK” button G2g is pressed, the input data is uploaded to the content management server 10 via the copyright management contract server 30 and stored in the content DB main table T1. Specifically, a content ID is uniquely assigned by the content management server 10 to the uploaded content, and a thumbnail of the content is created. The content and the thumbnail of the content are stored in a designated folder designated in advance by the content management server 10. In addition, the content management server 10 adds a new record to the content DB main table T1, the content ID is in the “content ID” field, the user ID of the uploaded creator is in the “user ID” field, and the data format of the content is “format ”Field, the content data capacity is in the“ Capacity ”field, the folder in which the content is stored is in the“ Storage Location ”field, the folder in which the content thumbnail is stored is in the“ Thumbnail Storage Location ”field, and the entered keyword is“ In the “Keyword” field, the selected genre is in the “Genre” field, and the usage price entered in the upload data selection screen G2 is entered in the “Usage price” field, and the number of times that can be used in the upload data selection screen G2. They are respectively stored in the "Available count" field.
The content upload is completed by the operations described above.

  The billing server 40 aggregates the cost of the content purchased by the user and bills the user for the cost.

  The search server 50 searches for content stored in the content management server 10.

  The application server 60 provides an application for using each service to the user terminal 100 and performs processing according to an input from the user terminal 100, or the content management server 10, the user deliverable server 11, The input information received from the user terminal 100 is transmitted to the user data management server 12 and the search server 50.

  Next, main operations of the media content management system 1 according to the first embodiment will be described in detail with reference to flowcharts.

(Content purchase processing)
FIG. 6 shows a flow of content purchase processing executed by the user data management server 12, the search server 50, the application server 60, and the user terminal 100. This process is executed when an instruction to purchase content is input from the user terminal 100 to the application provided from the application server 60 to the user terminal 100.
The content purchase process is a process for purchasing content stored in the content management server 10 .
As a premise that the processing is performed, a user ID and a password are transmitted to the application server 60 by an input from the user terminal 100 on a login screen (not shown) in advance, and authentication is performed by the user data management server 12. Has been done.

  FIG. 7A shows a content search screen G3 displayed on the user terminal 100 when the content purchase processing is executed. The content search screen G3 includes a keyword input tag G3a, a genre selection tag G3b, a “search” button G3c, and the like.

  First, the content search screen G3 is displayed on the user terminal 100, and an input from the user terminal 100 such as a keyword or a genre is awaited (step S601). Next, by inputting from the user terminal 100, a keyword is input to the keyword input tag G3a or a genre is selected to the genre selection tag G3b, and a search button is pressed (step S602).

  When the keyword input in step S602 or the selected genre is transmitted to the search server 50 via the application server 60, content management is performed by using the keyword or genre transmitted from the user terminal 100 by the search server 50 as a search condition. Information stored in the content DB main table T1 of the server 10 is searched (step S603).

  The search process executed in step S603 may be a complete match between the keyword and the information stored in the “keyword” field of the content DB main table T1 stored in the content management server 10, or may be a partial match before and after. Good. When a genre is input, it is assumed to be completely coincident with information stored in the “genre” field.

  The search result obtained in step S603 is extracted by the search server 50, and transmitted to the user terminal 100 via the application server 60 (step S604). Based on the search result received by the user terminal 100, the search result screen G4 is displayed on the user terminal 100 (step S605).

  FIG. 7B shows a search result screen G4 displayed on the user terminal 100 in step S605. The search result screen G4 includes a thumbnail G4a, a radio button G4b, a usage price information display area G4c, a “Purchase” button G4d, and the like of content that matches the search condition transmitted from the user terminal 100 in step S602.

  Next, in the input from the user terminal 100, when a check is input to the radio button G4b corresponding to the content displayed in the search result screen G4 and the purchase button G4d is pressed, the radio button G4b is displayed on the application server 60. The content ID of the checked content is transmitted (step S606).

  In step S606, when the content ID of the content to be purchased input from the user terminal 100 is transmitted to the application server 60, the application server 60 transmits the purchase agreement details to the user terminal 100 (step S607). On the user terminal 100, a purchase agreement screen G5 is displayed.

  FIG. 7C shows a purchase agreement screen G5 displayed on the user terminal 100 based on the purchase agreement contents transmitted from the application server 60. The purchase agreement screen G5 is composed of text G5a describing the purchase agreement, radio buttons G5b and G5c, an “OK” button G5d, and the like.

  When the purchase agreement screen G5 is displayed on the user terminal 100, the radio button G5b of “I agree” is selected by the operation of the user terminal 100, and the “OK” button G5d is pressed, the purchase agreement is sent to the application server 60. Is transmitted (step S608). When the “I don't agree” radio button G5c is selected and the “OK” button G5d is pressed, the process ends.

  When the application server 60 receives an agreement to the purchase agreement from the user terminal 100, the content ID transmitted from the user terminal 100 and the user ID of the user are transmitted to the user data management server 12 (step S609). ).

  In the user data management server 12, the purchase content of the user is stored in the purchase content table T7 stored in the user data management server 12 (step S610). Specifically, the received user ID is stored in the “user ID” field of the purchase content table T7, the received content ID is stored in the “content ID” field, and the date when the content purchase processing is performed in the “purchase date” field. However, in the “usage count” field, the available count stored in the “usable count” field of the record in the content DB main table T1 corresponding to the content ID is registered as a new record. When registration in the purchase content table T7 is completed, the user data management server 12 transmits a purchase content confirmation screen (not shown) to the user terminal 100 via the application server 60. A confirmation screen is displayed on the user terminal 100 based on the received confirmation information of the purchase content (step S611), and the process ends.

(Product generation processing)
FIG. 8 shows a flow of a product generation process executed by the user product server 11, the user data management server 12, the application server 60, and the user terminal 100. This process is executed when a content that the user purchased in the past is specified for the application provided from the application server 60 to the user terminal 100 and a product generation instruction is input.
The product generation process is a process of generating a product by synthesizing content purchased in the past by the user and personal content owned by the user terminal 100.
The user product server 11 functions as an acquisition unit that acquires product information through product generation processing. The application server 60 functions as a second reception unit, a product generation unit, and a notification unit that notifies a creator by a product generation process.

  FIG. 9A shows a personal content selection screen G6 displayed on the user terminal 100 when the product generation process is executed. The personal content selection screen G6 includes a preview area G6a, radio buttons G6b and G6c, a “reference” button G6d, an “OK” button G6e, and the like.

  First, when the personal content selection screen G6 is displayed on the user terminal 100 and the “reference” button G6d is pressed, a folder in the user terminal 100 in which the personal content is stored is selected (step S801). When the selected personal content is displayed in the preview area G6a of the personal content selection screen G6 and the “OK” button G6e is pressed, the data of the personal content is uploaded to the application server 60 (step S802). .

  When the user data management server 12 receives personal content via the application server 60 (step S803), a personal content ID is assigned to the received personal content (step S804). Then, the user data management server 12 stores the personal content in a folder designated in advance, and information related to the uploaded personal content is stored in the personal content table T5 stored in the user data management server 12. (Step S805). Specifically, in the “personal content ID” field of the personal content table T5, the personal content ID assigned in step S804 is stored in the “user ID” field, the user ID is stored in the “format” field, and the personal content data is stored. The format is registered as a new record in the “capacity” field, the data volume of the personal content, and the folder storing the personal content in the “storage location” field (step S805). When the registration in the personal content table T5 is completed, the fact that the upload has been completed and the personal content ID of this personal content are transmitted to the user terminal 100 via the application server 60. The user terminal 100 displays that the upload has been completed (step S806).

  Next, the content and personal content designated in advance by the user at the user terminal 100 are displayed on a composition instruction screen G7 to be described later (step S807).

  FIG. 9B shows the composition instruction screen G7 displayed in step S807. The composition instruction screen G7 includes an image composition area G7a, radio buttons G7b and G7c, a “decision” button G7d, and the like. The image composition area is an area for inputting a content designated by the user out of contents purchased by the user in the past and an instruction to compose personal content.

  When an image composition instruction is issued from the composition instruction screen G7, composition parameters are transmitted from the user terminal 100 to the application server 60 (step S808). The application server 60 generates a product based on the received synthesis parameter, and transmits this product to the user terminal 100 (step S809).

  Next, the composite image generated in step S809 is displayed on the user terminal 100 (step S810). Again, it is checked whether or not a synthesis execution instruction has been input from the user terminal 100 (step S811). When the composition execution instruction is input (step S811; NO), the process returns to step S808. When the designation for adding the content to be used is input, the application server 60 performs processing so as to acquire the designated content from the content management server 10 and display it on the composition instruction screen G7. When the composition execution instruction is not input (step S811; YES), the radio button G7b is checked, and when the “decision” button G7d on the composition instruction screen G7 is pressed, the product information is transmitted to the application server 60, and the application A thumbnail of the deliverable is created by the server 60 (step S812). Next, the user ID, product information, and thumbnail are transmitted to the user product server 11 by the application server 60 and stored in the user product server 11 (step S813). Specifically, the thumbnails of the deliverables are stored in a folder designated in advance in the user deliverable server 11, and a “record of achievement” is created as a new record for the deliverable DB main table T 2 stored in the user deliverable server 11. The product ID uniquely assigned to the product is displayed in the “Product ID” field, the date when the product generation processing is performed in the “Production Date” field, the user ID in the “User ID” field, and the “Synthesis” In the “Parameter” field, the synthesis parameter is stored. In the “Thumbnail storage location” field, the folder storing the thumbnail of the product is stored in the “Use log storage location” field. A storage folder is registered.

  At the same time, the product ID is displayed in the “product ID” field of the use content table T3, and the content ID is stored in the “content ID1” field, the “content ID2” field, the “content ID3” field, or the “content ID4” field. Stored. A NULL value is stored when there are less than four contents used in creating the deliverable.

  Similarly, in the “product ID” field of the used personal content table T4, the product ID is “personal content ID1” field, “personal content ID2” field, “personal content ID3” field, or “personal content ID4” field. Stores the personal content ID.

After registration by the user deliverable server 11 is completed, the number of times of use of the content used by the deliverable generation process is reduced by 1 according to an instruction from the user deliverable server 11 to the user data management server 12 (step In step S814, an e-mail is sent to the creator who uploaded the content via the application server 60, and notification that the secondary use of the content of the creator is made (step S815). Specifically, the user associated with the content used in the product generation process is reduced by one use of the record of the purchase content table T7 of the user data management server 12 corresponding to the user ID and the content ID. The creator of ID is referred to the personal information table T6 and notified that the content has been used.

(Product release processing)
FIG. 10 shows a flow of a product publishing process executed by the user product server 11, the application server 60, and the user terminal 100. This process is executed when an instruction to publish a product is input from the user terminal 100 to the application provided from the application server 60 to the user terminal 100.
The deliverable publishing process is a process of requesting a list of deliverables stored in the user deliverable server 11 from the user terminal 100 and displaying the deliverables desired by the user in a viewable manner. When the creator of the deliverable browses, the deliverable can be downloaded.
The application server 60 functions as a publishing unit that publishes a product and a transmission unit that transmits the product by a product publishing process.

  First, a list of deliverables is requested from the application server 60 by an input from the user terminal 100 (step S1001). The request for the deliverable list may require all data stored in the user deliverable server 11 or may be configured such that the search server 50 performs a narrow search by inputting a content ID or the like.

The application server 60 transmits the product list request received from the user terminal 100 to the user product server 11, and the user product server 11 transmits the thumbnail of the product and the product ID to the application server 60 ( Step S1002). A product list is created by the application server 60 and transmitted to the user terminal 100 (step S1003).

  FIG. 11A shows a deliverable list screen G8 displayed on the user terminal 100 when the deliverable list is transmitted to the user terminal 100. The deliverable list screen G8 includes a plurality of deliverable thumbnails G8a and the like.

  When the product list screen G8 is displayed on the user terminal 100 (step S1004). When the thumbnail G8a displayed on the product list screen G8 is selected, the product ID corresponding to the selected thumbnail G8a is transmitted to the application server 60 (step S1005).

When the product ID is received in the application server 60, the product ID is requested to the user product server 11, and the product information is transmitted to the application server 60 by the user product server 11. (Step S1006).
The application server 60 generates a product based on the received product information (step S1007). The product generated in step S1007 is transmitted to the user terminal 100, and the product publication screen G9 is displayed on the user terminal 100 (step S1008).

FIG. 11B shows a product publication screen G9 displayed on the user terminal 100 when the product is received in step S1008. The product release screen G9 includes product image data G9a, a user ID tag G9b, a password tag G9c, a “download” button G9d, and the like.
Through the processing up to step S1008, the user can browse the deliverables made public to other users. The subsequent processing is processing that can be performed only by the user who created the deliverable.

In the user terminal 100, when the user ID is input to the user ID tag G9b, the password is input to the password tag G9c, and the “download” button G9d is pressed by the input on the product publication screen G9, the application server 60 is used. Then, authentication is performed by the user data management server 12, and the authentication result is transmitted to the user terminal 100 (step S1009). Specifically, by comparing the user ID and password input from the product release screen G9 with the “user ID” field and the “password” field of the personal information table T6 stored in the user data management server 12. Authentication is performed.

  If it is determined that the authentication result is invalid (step S1009; NO), the process ends. When the authentication result indicates that the user is a valid user (step S1009; YES), the user terminal 100 makes a download request for the deliverable to the application server 60 (step S1010). The application server 60 converts the product generated in step S1007 into a JPEG (Joint Photographic Experts Group) format (step S1011). The application server 60 applies copyright protection processing such as digital watermarking to the product data in JPEG format obtained in step S1011 and transmits it to the user terminal 100 (step S1012).

  The product data subjected to the copyright protection processing is downloaded by the user terminal 100, and a download completion notification is transmitted to the application server 60 (step S1013).

  In response to an instruction from the application server 60, a usage log is created in the user data management server 12, and the user product server 11 instructs the application server 60 to extract the email address of the creator who uploaded the content related to the product. Thus, the creator is notified (step S1014). Specifically, the personal data table T6 is referred to by the user data management server 12, and the mail stored in the “mail address” field in the record that matches the user ID of the creator who uploaded the content used for the product. A notification that the content has been downloaded is sent to the address. Then, a usage log is created by the user deliverable server 11 and stored in a predetermined directory.

As described above, in the media content management system 1, content, personal content, and deliverables are associated with each other and stored and managed by the content management server 10, the user deliverable server 11, and the user data management server 12. ing.
Accordingly, since the content used for the product downloaded by the user can be collectively managed on the server side, it is possible to identify the content used for the product that is suspected of being tampered with. it can. In addition, when a modification unintended by the creator is made, it is possible to determine which user has created the product.

  Further, the content and the personal content are synthesized by the application server 60, and the generated output is transmitted to the user terminal 100 by the application server 60 via the communication network N, so that the user terminal 100 can acquire the output. it can. As in the present embodiment, when the content is CG, it is possible to easily perform the creation work of the deliverable in which the content is secondarily used according to the user's preference.

  In addition, when a product is generated in the product generation process and the number of times the content is used is reduced by one, the creator is notified how the creator's content has been used by notifying that the creator's content has been used. Can know. As a result, if your content is used for a product that is not intended by the creator, take measures to prohibit the use of this product or to prohibit users from using the content uploaded by this creator. It can also be requested from the service provider.

[Embodiment 2]
Hereinafter, Embodiment 2 of the present invention will be described.
In the first embodiment, a product is generated by a product generation process in cooperation with the user terminal 100 and each server such as the application server 60. However, it is good when the user terminal 100 can connect to the application server 60 using a wired cable such as UTP (Unshielded Twist Pair cable), but the connection is made by a communication method such as a wireless LAN that is relatively easily disconnected. In the case of performing, there is a possibility that the exchange of data is interrupted in the middle of the product generation process, and a smooth service cannot be provided.
Therefore, in the second embodiment, in order to suppress the influence of the disconnection with the application server 60, a product generation process (referred to as a product generation process B in order to distinguish from the first embodiment) is performed on the user terminal 100 side. As a result, the number of connections with the application server 60 is reduced, and a smooth service can be provided.

FIG. 12 shows a configuration example of the product generation software 200 according to the second embodiment and folders for storing various data of the product generation software. As shown in FIG. 12, the product generation software 200 in the present embodiment includes a renderer 201, a 3DCG (3Dimention Computer Graphics) editor 202, management software 203, a management DB 204, and a communication module 205. , Exchange data with the user data folder 206, the purchase content folder 207, and the deliverable folder 208.

The renderer 201 is software that performs image processing of a three-dimensional image.
The 3DCG editor 202 is an editor for browsing and processing an image such as a product in the user terminal 100.

The management software 203 is software that is activated first when performing a product generation process B described later.

  The management DB 204 stores various data for operating the management software 203.

  The communication module 205 is a module for communicating with the application server 60.

The user data folder 206 has the same configuration as the user DB 23 of the first embodiment, and only records corresponding to user IDs possessed by the user of the user terminal 100 are extracted and stored. The purchased content folder 207 stores content data purchased by the user. The deliverable folder 208 has the same configuration as the deliverable DB 22 of the first embodiment, and only records corresponding to user IDs possessed by the user of the user terminal 100 are extracted and stored.
The user data folder 206, the purchase content folder 207, and the deliverable folder 208 cannot be accessed directly by operating the user terminal 100, and respond only to input from the management software 203.

  Other configurations in the second embodiment are the same as those described in the first embodiment, and thus description thereof is omitted.

Next, the operation in the second embodiment will be described.
In the second embodiment, the application server 60 functions as a generation program storage unit that stores the product generation software 200 and a transmission unit that transmits the product generation software in response to a request from the user terminal 100. The product generation software 200 is stored in the application server 60, and is transmitted to the user terminal 100 when requested by the user terminal 100. Simultaneously with downloading of the product generation software 200, a purchase content folder 207 , a product folder 208 , and a user data folder 206 are downloaded to the user terminal 100.

(Product generation processing B)
In the product generation process B according to the second embodiment, the process is performed according to the flow shown in FIG. The product generation process B is performed when the product generation software 200 is activated in response to an instruction from the user terminal 100 and an instruction for content to be used for product generation is given to the purchase content folder 207.

First, the personal content selection screen G6 is displayed on the user terminal 100, the “reference” button G6d is pressed, and the folder in the user terminal 100 storing the personal content is selected (step S1201). When the selected personal content is displayed in the preview area G6a of the personal content selection screen G6 and the “OK” button G6e is pressed, a personal content ID is given to the personal content by the operation of the management software 203 ( Step S1202). Next, the personal content and the personal content ID are stored in the user data folder 206 (step S1203).

  Next, a save completion screen (not shown) is displayed on the user terminal 100, and the 3DCG editor 202 is activated (step S1204). Next, a synthesis instruction screen G7 is displayed on the user terminal 100, and a synthesis parameter is input to the 3DCG editor 202 by an operation on the synthesis instruction screen G7 (step S1205). The 3DCG editor 202 synthesizes the content and the personal content based on the synthesis parameter (step S1206), and the generated product is displayed on the synthesis instruction screen G7 (step S1207).

  Then, it is checked again whether the synthesis parameter has been input from the user terminal 100 (step S1208). When the synthesis parameter is input (step S1208; NO), the process returns to step S1206. When an instruction to add content to be used is input, the management software 203 performs processing to acquire the content from the purchase content folder 207 and display it on the composition instruction screen G7. When the synthesis parameter is not input (step S1208; YES) and the “OK” button on the synthesis instruction screen G7 is pressed, a thumbnail is created by the management software 203, and the thumbnail and product information are stored in the product folder 208. (Step S1209). Next, the usage count of the purchase content table T7 of the user data folder 206 corresponding to the used content is decreased by 1 (step S1210).

(Judgment process)
FIG. 14 shows a flow of determination processing executed by the user product server 11, the user data management server 12, the application server 60, and the user terminal 100. This process is executed by the application server 60 when the user terminal 100 and the application server 60 are connected.
The application server 60 functions as a determination unit that determines whether information related to the deliverable has been transferred from the user terminal 100 through the determination process.
In the determination process, the contents of the user data folder 206 in the user terminal 100 and the contents of the user data management server 12 are compared, and the contents of the deliverable folder 208 and the contents of the user deliverable server 11 are compared. If the contents are different as a result of the comparison, the contents of the user data folder 206 are reflected on the user data management server 12, and the contents of the artifact folder 208 are reflected on the user artifact server 11.

First, when a connection is made to the application server 60 by operating the user terminal 100, the contents of the user data folder 206 and the deliverable folder 208 are uploaded to the application server 60 (step S1401). When the application server 60 determines that the contents of the user data folder 206 and the deliverable folder 208 have been uploaded, the contents of the user data folder 206 uploaded from the user terminal 100 are transmitted to the user data management server 12 (steps). S1402).

The user data management server 12 that has received the contents of the user data folder 206 from the application server 60 makes a comparison with the contents stored in the user data management server 12 (step S1403). If the contents are different (step S1403; YES), an instruction to upload personal contents from the user deliverable server 11 is transmitted to the user terminal 100 via the application server 60, and the user terminal 100 sends the personal contents. Is uploaded to the application server 60 (step S1404). When the personal content uploaded in step S1404 is transmitted to the user data management server 12 via the application server 60, the information is updated by the user deliverable server 11 (step S1405). Specifically, the received personal content data is stored in a folder designated in advance, and the content of the user data folder 206 transmitted from the application server 60 in step S1402 is stored in the personal content table T5 and the purchased content table T7. Reflected.
If the contents are not different (step S1403; NO), the process proceeds to step S1406 and the process is continued.

Next, the contents of the deliverable folder 208 uploaded from the user terminal 100 are transmitted to the user deliverable server 11 by the application server 60 (step S1406).
When the contents of the deliverable folder 208 are received from the application server 60, the user deliverable server 11 makes a comparison with the contents stored in the user deliverable server 11 (step S1407). If the contents are different (step S1407; YES), the product server updates the information (step S1408). Specifically, the contents of the deliverable folder 208 transmitted from the application server 60 in step S1406 are reflected on the deliverable DB main table T2, the used content table T3, and the used personal content table T4.
If the contents are not different (step S1407; NO), the process ends.

Thus, in the product generation process B, a product is generated in the user terminal 100. When the product generation process B is executed, the tables in the user data folder 206 and the product folder 208 are updated. The contents of the user data folder 206 and the deliverable folder 208 are uploaded when connected to the application server 60, and the contents are reflected on the user data management server 12 and the user deliverable server 11, respectively. The timing of uploading the update contents to the application server 60 may be configured such that the content purchase processing is activated in order to purchase new content, or automatically transmitted when connected to the application server at another timing. It is good also as a structure to be made. Further, when the application server 60 is connected to the user terminal 100, the application server 60 compares the contents of the user data folder 206 and the deliverable folder 208 with the contents of the user data management server 12 and the user deliverable server 11, and instructs an update if they are different. Make a decision.
In the second embodiment, a product publishing process is performed based on the information of the user product server 11 updated by the determination of the application server 60, and the product generated by the user terminal 100 can be disclosed. .

As described above, in the second embodiment, the product generation software 200 that performs the product generation processing B stored in the application server 60 is transmitted to the user terminal 100, and the user terminal 100 generates the product generation. Since the product generation process B is performed by the user terminal 100 based on the software 200, the number of connections with the application server 60 can be reduced. As a result, since the disconnection of the connection does not occur during the product generation process B, the user can generate the product smoothly. Further, content data and the like are stored by the purchase character folder 207 , the product folder 208 , and the user data folder 206 , and each folder is periodically synchronized with the content management server 10, the user product server 11, and the user data management server 12. The service provider of the media content management system 1 can associate the deliverable with the used content by matching the contents.

Note that the description in each of the above embodiments is a preferred example of the media content management system 1 according to the present invention, and the present invention is not limited to this.
For example, in the embodiment described above, image data such as CG has been described as an example of media content, but the present invention is not limited to image data. For example, audio data such as music or moving image data may be used. In other words, the creator may upload the moving image data, and the user who purchased the moving image data may upload the text data as his / her comment and perform the composition processing with the moving image data. In this case, the video data created by the creator and the user's comment can be managed in association with each other. The creator can specify this user when an unintended comment or modification is added to the video data uploaded by the creator.

  In the above embodiment, the screen of a personal computer has been described as an example of the user terminal 100. However, the user terminal 100 may be a portable communication device such as a mobile phone or a multifunction digital camera. For example, when the user terminal 100 is a mobile phone, a composition application may be downloaded to the mobile phone as in the second embodiment, and a photograph taken with the mobile phone and the content may be combined. In the case of a multi-function digital camera, the terminal may be connected to a multi-function digital camera installed at a consumer electronics retailer or the like, and a composition process may be performed by an operation on the multi-function digital camera.

  In addition, the detailed configuration and detailed operation of each device configuring the media content management system 1 can be changed as appropriate without departing from the spirit of the invention.

It is a block diagram which shows the structural example of the media content management system in embodiment of this invention. It is a figure which shows the example of data storage of content DB of FIG. (A) is a figure which shows the example of a data storage of the product DB main table stored in product DB of FIG. 1, (b) is the data of the use content table stored in product DB of FIG. It is a figure which shows a storage example, (c) is a figure which shows the data storage example of the use personal content table stored in deliverable DB of FIG. (A) is a figure which shows the data storage example of the personal content table stored in user DB of FIG. 1, (b) shows the data storage example of the personal information table stored in user DB of FIG. It is a figure, (c) is a figure which shows the data storage example of the purchase content table stored in user DB of FIG. (A) is a figure which shows the copyright management contract screen at the time of registering content in content DB of FIG. 1, (b) is the upload data selection screen at the time of registering content in content DB of FIG. FIG. It is a flowchart which shows the content purchase process performed by the media content management system of FIG. (A) is a figure which shows the content search screen at the time of searching a content in the content purchase process of FIG. 6, (b) is the search result at the time of receiving the search result of a content in the content purchase process of FIG. It is a figure which shows a screen, (c) is a figure which shows the purchase rule screen which confirms a purchase rule in the content purchase process of FIG. It is a flowchart which shows the product production | generation process performed by the media content management system of FIG. (A) is a figure which shows the personal content selection screen at the time of selecting a personal content in the product production | generation process of FIG. It is a figure which shows a synthetic | combination instruction | indication screen. It is a flowchart which shows the product publication process performed by the media content management system of FIG. (A) is a figure which shows the product list screen which displays the list of products in the product publication process of FIG. 10, (b) is when releasing a product in the product publication acquisition principle of FIG. FIG. FIG. 10 is a conceptual diagram illustrating a software configuration of product generation software 200 according to Embodiment 2. 13 is a flowchart showing a product generation process B executed by the management software 103 of FIG. It is a flowchart which shows the discrimination | determination process performed by the media content management system of FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Media content management system 10 Content management server 11 User deliverable server 12 User data management server 20 DB server 21 Content DB
22 Product DB
23 User DB
30 Copyright Management Contract Server 40 Billing Server 50 Search Server 60 Application Server 100 User Terminal 200 Product Generation Software 201 Renderer 202 3DCG Editor 203 Management Software 204 Management DB
205 Communication module 206 User data folder 207 Purchased content folder 208 Deliverable folder

Claims (6)

First receiving means for receiving first media content input from the outside;
First storage management means for storing and managing the first media content received by the first receiving means;
Second receiving means for receiving product information input from the outside in order to generate second media content including the first media content and personal content to be combined with the first media content; ,
Obtaining means for obtaining the product information received by the second receiving means;
Second storage management means for storing and managing the product information received by the second receiving means in association with the first media content;
Third storage management means for storing and managing the personal content received by the second receiving means;
Generating means for generating the second media content based on the first media content, the product information, and the personal content by an external input;
Publishing means for publishing the second media content generated by the generating means to a network via a communication line;
When there is a download request from the outside, the second media content generated by the generation unit is digitally watermarked, and the second media content subjected to the digital watermark processing is outside the download request source. First transmitting means for transmitting;
A media content management system comprising: A judgment means for judging whether or not the product information is received by the second receiving means;
The media content management system according to claim 1, wherein the acquisition unit acquires the product information determined to be received by the determination unit. Generation program storage means for storing a generation program for the outside to generate the second media content;
Second transmission means for transmitting the generation program stored in the generation program storage means to the outside;
The media content management system according to claim 2 , further comprising: The first storage management means further stores creator information of the first media content in association with the first media content;
When the product information is acquired by the acquisition unit, the creator information of the first media content associated with the product information is extracted from the first storage management unit, and the extracted creation Notification means for notifying the creator based on the creator information;
The media content management system according to any one of claims 1 to 3 , further comprising: The first media content is a CG image, the second media content is a captured image obtained by combining the CG image, and the product information indicates a combined state of the CG image combined with the captured image. The media content management system according to any one of claims 1 to 4 , further comprising: a synthesis parameter to be displayed. A first receiving step in which the first receiving means receives the first media content input from the outside;
A first storage management step for storing and managing the first media content received by the first reception step;
The second receiving means outputs the product information for generating the second media content including the first media content input from the outside, and the personal content for combining with the first media content. A second receiving step for receiving;
An obtaining unit for obtaining the product information received by the second receiving step;
A second storage management step for storing and managing the product information received in the second receiving step in association with the first media content;
A third storage management step for storing and managing the personal content received by the second reception step;
A generating step for generating the second media content based on the first media content, the product information, and the personal content according to an external request;
A publishing step for publishing the second media content generated by the generating step to a network via a communication line;
When there is a download request from the outside, the transmission means performs a digital watermark process on the second media content generated by the generation step, and downloads the second media content subjected to the digital watermark process. A transmission process to send to the original outside,
A media content management method comprising:

Images