JP2006344107A - Content distribution system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To dynamically manage fee setting of content distribution, to enhance user's convenience and to prevent a problem such as double charging when a content is redistributed. <P>SOLUTION: This content distribution system includes a client, a center server for distributing content and a management server for managing a content distribution history and a set fee table from the center server, wherein the client notifies the center server of a fee information request including a user ID and a content ID and receives the fee information request from the client to execute processing for inquiring fee information from the management server, the management server determines fee information including a fee setting ID and a fee amount on the basis of the fee information request, the content distribution history and the set fee table and executes processing for notifying the center server of the fee information, the center server executes processing for notifying the client of the notified fee information, and the client executes processing for displaying the fee amount included in the fee information. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a content distribution system that distributes content, a client, a center server, and a management server that configure these, a program used for these, and a content distribution method.

  In a content distribution system that distributes content purchased by a user, typically including video or audio, through a network such as the Internet, consideration is provided / provided between the administrator on the distribution side and the user The fee is set as follows. In this charge setting, a charge for a content unit typified by pay-per-view, a fixed charge for a fixed period or a fixed amount of content, or a combination of these is generally used. Conventionally, since a uniform fee setting is often performed regardless of the content, flexible fee setting that reflects the distribution status and the contents of the content is required between the administrator and the user.

  Further, in a download type or streaming type content distribution system, there is a case where charging is completed when the download is completed or when the provision of the content is completed when the streaming is started or completed. Depending on the pricing set between the administrator and the user, there may be a case where the user is not charged twice even if the same content is distributed or redistributed multiple times under certain conditions. The certain condition is, for example, a case where download is necessary again due to incomplete content data, etc., and a time limit or period during which viewing is possible, which is the number of times.

  Conventionally, an administrator who provides content may cope with the problem of double charging by managing the content distribution history with the content distribution server or the management server. When a terminal to which content has been distributed holds an electronic receipt issued by the server and requests redistribution of the content, there is a device that sends this electronic receipt to the server (Patent Document 1).

JP 2002-334173 A (FIG. 1)

  However, with respect to the content distribution system of the prior art, it is insufficient to manage the content distribution history using the electronic receipt. That is, information such as the viewing limit and the viewing time limit is already recorded in the electronic receipt, and charging is performed based on the information. Therefore, there is a possibility that unauthorized charging may be performed by falsification of the electronic receipt data. There is. In addition, since much information is incorporated in the electronic receipt itself, there is a problem in flexibly changing the service system and fee setting on the administrator side who distributes the content. Reflects the content of the content that the administrator has considered for the user's convenience, including whether the user will not be charged twice even if the same content is distributed or redistributed multiple times under certain conditions There is a limit to the pricing.

  The present invention has been made to solve the above-described problems of the prior art, and its purpose is to provide a content distribution system that distributes content, as well as a client, a center server, and a management server that constitute these, In addition, regarding the programs used for these, when content distribution is requested by a user, not only the content distribution history for that user, but also various parameters at that time related to the content are referred to as needed. It is an object of the present invention to provide a content distribution system and a content distribution method that can dynamically manage and improve user convenience and prevent problems such as double charging during redistribution.

  The content distribution system of the present invention includes a client that reproduces content to be distributed, a center server that distributes content to the client, and a management server that manages a content distribution history and a set fee table from the center server to the client. The client executes a process of notifying the center server of a charge information request including the user ID and the content ID, and the center server receives the charge information request from the client and executes a process of inquiring the charge information to the management server. The management server executes a process of determining the charge information including the charge setting ID and the charge amount based on the charge information request, the content distribution history, and the set charge table and notifying the center server of the charge information. , Clients with notified pricing information Run the process to be notified, the client, to execute the process of displaying the fee amount that is included in the price information.

  Preferably, in the content distribution system of the present invention, the client notified of the charge information holds the charge setting ID and the content ID in association with each other and notifies the center server of a distribution request including the user ID and the content ID. When the center server receives the distribution request from the client, the center server executes the process of starting the distribution of the content. When the distribution of the content is completed, the client The center server executes processing for notifying the management server of the notified fee setting ID, and the management server performs processing for updating the content distribution history based on the notified fee setting ID. Execute.

  Preferably, in the content distribution system of the present invention, the client executes a process of notifying a charge information request including an error flag set in relation to a content reproduction error, and the management server sets the error flag. When a charge information request is received, processing for determining free charge information is executed based on the content distribution history.

  Preferably, in the content distribution system of the present invention, the set fee table for determining fee information is determined by a fee parameter that varies based on the content distribution history managed by the management server.

  Further, the program of the present invention is executed in the control unit of the client of the content distribution system. Or the program of this invention makes a computer function as a management server of said content delivery system.

  The content distribution method of the present invention also includes a step of notifying a charge information request including a user ID and a content ID to a center server that distributes content to the client, and receiving a charge information request from the client to the client from the center server Based on the step of inquiring charge information to the management server that manages the content distribution history and the set charge table, the charge information request, the content distribution history, and the set charge table, the charge information including the charge setting ID and the charge amount is obtained. Determining and notifying the center server, notifying the notified fee information from the center server to the client, and displaying the fee amount included in the fee information by the client.

  In the content distribution method of the present invention, the client notified of the charge information holds the charge setting ID and the content ID in association with each other, and notifies the center server of the distribution request including the user ID and the content ID. And a step of starting distribution of contents from the center server when receiving a distribution request from the client, and a step of notifying the fee setting ID from the client to the center server when the distribution of contents is completed. And a step of notifying the charge setting ID from the center server to the management server, and a step of updating the content distribution history of the management server based on the notified charge setting ID.

  Preferably, the content distribution method of the present invention includes a step of notifying the management server of a fee information request including an error flag set in relation to a content reproduction error in the client, and a fee information request in which the error flag is set. And receiving free fee information based on the content distribution history when received.

  Preferably, in the content distribution method of the present invention, the set fee table for determining fee information is determined by a fee parameter that varies based on the content distribution history managed by the management server.

  The operation of the present invention will be described below.

  The content distribution system of the present invention includes a client to which content is distributed, a center server that distributes content to the client, and a management server that manages a content distribution history from the center server to the client. For example, the client is a viewing terminal for downloading content, and may be a dedicated device or a personal computer. The program of the present invention is executed in a microcomputer or CPU (central processing circuit) constituting the control unit of the client. The center server and the management server are computers or servers, and the program of the present invention causes the computer or server to function as a management server. The center server and the management server may be separate or may be shared by a single server.

  First, the client executes processing for notifying the center server of a charge information request including a user ID and a content ID. The center server receives the charge information request from the client, performs user authentication, and executes processing for inquiring the charge information to the management server. The management server executes a process of determining the charge information including the charge setting ID and the charge amount and notifying the center server based on the charge information request, the content distribution history, and the set charge table.

  In the content distribution system of the present invention, the fee information request notified from the client to the center server and the management server includes an error flag set in association with a content reproduction error. The error flag is automatically set by the client in relation to the content reproduction error. When receiving the charge information request in which the error flag is set, the management server determines free charge information based on the content distribution history. Therefore, the content cannot be played back due to some trouble in the viewing terminal, and even if an error is found during playback, it can be downloaded again, and problems such as double charging do not occur.

  The center server notifies the client of the notified fee information, and the client executes processing for displaying the fee amount included in the fee information. Therefore, when a content fee information request is made by a user, the content distribution fee setting is dynamically managed by referring to not only the content distribution history to the user but also various parameters related to the content at that time. And display the charge. Also, free fee information can be displayed in response to playback errors in the client. Furthermore, since the center server notifies the client only of charge information including the charge setting ID and the charge amount, not the information like the conventional electronic receipt including many parameters, flexible charge setting on the management server side This makes it possible to prevent unauthorized charges due to falsification of electronic receipts.

  The client notified of the charge information holds the charge setting ID and the content ID in association with each other and executes a process of notifying the center server of a distribution request including the user ID and the content ID. After receiving the distribution request, the client executes a process of starting the distribution of the content, and the client executes a process of notifying the center server of the charge setting ID when the distribution of the content is completed. The management server executes a process of notifying the notified fee setting ID to the management server, and the management server executes a process of updating the content distribution history based on the notified fee setting ID. Therefore, since the fee setting ID is notified to the management server when the content distribution is completed, the management server can update the content distribution history only by collating with the fee setting ID set in advance.

  Preferably, in this content distribution system, a set fee table for determining fee information is determined by a fee parameter that varies based on a content distribution history managed by the management server. Therefore, the administrator of the management server dynamically refers to not only the content distribution history for the user but also various parameters at that time relating to the content at any time, and sets the fee by dynamically managing the content distribution fee setting. Can provide a flexible service to the user.

  The content distribution system and content distribution method of the present invention refers to not only the content distribution history to the user but also various parameters at that time related to the content as needed when a content fee information request is made from the user. It is possible to dynamically manage content distribution fee settings to improve user convenience and to prevent problems such as double charging at the time of redistribution.

  The content distribution system and the content distribution method of the present invention are designed to dynamically manage content distribution charge settings, improve user convenience, and prevent problems such as double charging during redistribution. A client that reproduces the content to be distributed, a center server that distributes the content to the client, and a management server that manages a content distribution history and a set fee table from the center server to the client. The center server executes a process for notifying a charge information request including a user ID and a content ID, the center server receives a charge information request from the client, and executes a process for inquiring the charge information to the management server. , Content distribution history, and setting fee table The charge information including the charge setting ID and the charge amount is determined and the process of notifying the center server is executed. The center server executes the process of notifying the client of the notified charge information. This was realized by executing the process of displaying the charge amount included in the.

  Hereinafter, although the content delivery system by the preferable embodiment of this invention, the program used for these, and the content delivery method are demonstrated, this invention is not limited to these embodiment.

  FIG. 1 is a diagram illustrating a content distribution system 1 according to a preferred embodiment of the present invention. The content distribution system 1 includes a client 2 that is connected to a network 10 such as the Internet and distributes content such as video and music, a center server 3 that distributes content to the client 2 via the network 10, A management server 4 that manages a content distribution history to the client 2. When the user who uses the client 2 uses the content under a contract with the manager of the center server 3 and the management server 4, the user is charged corresponding to the use of the content.

  The client 2 is a viewing terminal device that receives content such as video and music viewed by the user via the network 10 and enables viewing of the content. Typically, it is a PC (personal computer), a dedicated receiver, or a portable terminal, and includes at least a control unit 21 including a microcomputer and a memory, a recording / reproducing unit 22 that records and reproduces content, and content or control information. In addition, a display unit 23 for displaying charge information, an operation unit 24 operated by a user, and a network connection unit 25 connected to the network 10 are connected via an internal control bus 20. For example, the recording / playback unit 22 is an HDD (hard disk drive), and the display unit 23 may be a display window using an FL tube built in the client 2, or may be an external display device such as a display connected to the client 2. . A program for controlling the client 2 is stored in the memory of the control unit 21 or the recording / reproducing unit 22 and is executed by the microcomputer of the control unit 21.

  The center server 3 is a server installed by an administrator who provides content in the distribution system 1, and is a server that centrally manages content library information and client information included in each client 2 in a database. The center server 3 includes at least a control unit 31 including a CPU (central processing circuit) and a memory, a distribution storage unit 32 including a content database for recording and distributing content, and a network connection unit 33. They are connected by an internal control bus 30. The center server 3 may be composed of a plurality of servers such as a content server including content and library information and a client management server including client information.

  The management server 4 is a server (or computer) installed by an administrator who provides content or manages charging in the distribution system 1 and stores a content fee database, various parameters for setting fees, and a content distribution history. It is a server that manages, dynamically sets a fee for content for which fee information is requested, centrally manages the charging status of each client, and provides charging information to the charging administrator. The management server 4 includes at least a control unit 41 including a CPU (central processing circuit) and a memory, a record database 42 including a charge database, various parameters for setting charges, and a content distribution history, a network connection unit 43, A storage unit 44 for holding a program for causing the server to function as the management server 4 of the distribution system 1, an input unit 45 for setting various parameters by an administrator, and a display unit 46 for displaying various types of information are provided. Are connected by a control bus 40. The control unit 41 causes the server (or computer) to function as the management server 4 by executing the program held in the storage unit 44.

  The management server 4 only needs to be connected to the center server 3 and may be connected via the network 10. Further, the center server 3 and the management server 4 may be provided on a common server, or may be configured by a plurality of servers. Further, the network 10 may be a network such as the Internet, and may include a LAN. The client 2 may be plural or only one.

<Price information request for content distribution>
FIG. 2 is a flowchart illustrating a content distribution charging method in the distribution system 1. When viewing the content, the client 2 requests fee information from the center server 3 regarding the fee for receiving distribution of the content selected from the content list (not shown) supplied from the center server 3 (S201). This fee information request includes a user ID for identifying the client 2, a content ID for identifying the content, and an error flag. The error flag is a flag set in relation to a reproduction error that occurs when the client 2 reproduces the content. For example, when the flag is set, the client 2 already holds the content. Regardless of this, it is a case where the content cannot be reproduced due to content data corruption or the like, and the content is requested to be redistributed from the client 2 to the center server 3. In addition, the error flag is not set in the charge information request in the case of a request for distributing content that does not involve a content reproduction error, or when the client 2 does not hold the content, This is a case of holding, that is, a case of a normal content distribution request.

  The center server 3 that has received the fee information request from the client 2 performs user authentication using the user ID included in the fee information request (S301). The user authentication may be performed by an authentication server different from the center server 3. If it is determined by the user authentication that the charge information request is a charge information request from the proper client 2, the center server 3 makes a charge information request for inquiring the management server 4 for the charge of the content requested to be distributed. (S302). The fee information request includes a user ID, a content ID for identifying content, and an error flag. Therefore, when the error flag is set in the fee information request from the client 2, the management server 4 is notified that the fee information request is a request for redistribution of contents.

  Upon receiving the charge information request from the center server 3, the management server 4 sets the charge for the content for which the charge information is requested from the content charge database, various charge setting parameters, and the content distribution history by the method described later. The fee information is determined (S401). This fee information includes a fee setting ID and a fee amount. For example, when an error flag is included in a fee information request from the client 2, the fee amount is “free” or 0 (zero). The management server 4 notifies the center server 3 of the determined fee information together with the user ID (S402). The center server 3 receiving the fee information from the management server 4 identifies the client 2 that notifies the fee information from the user ID (S303), and notifies the client 2 of the fee information including the fee setting ID and the fee amount (S304). . When the session between the center server 3 and the management server 4 is specified by another means, the management server 4 may notify the center server 3 only of the determined fee information.

  Upon receiving the fee information from the center server 3, the client 2 displays the fee amount included in the fee information on the display unit 23 (S202). That is, the client 2 displays a fee amount set by the administrator who provides the content for the distribution of the content based on its own fee information request. As a result, for example, in the case of a redistribution charge information request in which an error flag is set, the charge amount of “free” or 0 (zero) is displayed to the user using the client. At this time, the control unit 21 of the client 2 holds the fee setting ID, the user ID, and the content ID in association with each other or stores them in a memory and records fee information in the recording / reproducing unit 22 as necessary. To do.

<Price information settings>
FIG. 3 is a flowchart for explaining the process from the process for determining the charge information (S401) to the process for notifying the determined charge information to the center server 3 (S402). First, the management server 4 receives a charge information request from the center server 3 (S401), and determines whether or not an error flag is set to ON in the charge information request (S501). That is, the management server 4 determines whether the fee information request is a request for recharging fee content based on a content reproduction error in the client 2 (S501: Yes) or a request for normal content distribution (S501). : No) is determined.

  If the error flag is set: ON (S501: Yes), the control unit 41 of the management server 4 refers to the content distribution history (described later) provided in the recording storage unit 42, and the user of the client 2 It is checked whether or not the distribution of the content subject to the charge information request from is recorded in the past content distribution history (S502). At this time, it is preferable to check whether the content is within the viewing period. Even if the error flag is set, if there is no record in the content distribution history (S502: No), it is determined that there is a fee setting error (S503), and the management server 4 displays the fee information including the fee error as the center server. 3 is notified (S402).

  If the error flag is set and there is a record in the content distribution history and it is within the viewing deadline (S502: Yes), the control unit 41 of the management server 4 indicates that the fee information request is a content reproduction error in the client 2 As a content re-distribution request based on the above, the charge amount related to content distribution is set to “free” or 0 (zero) (S504) to prevent double charging to the user. The management server 4 notifies the charge information to the center server 3 through a step (S505) of registering charge information including a charge setting ID and a charge amount, which will be described later, in the charge setting table of the management server 4 (S402).

  On the other hand, if the error flag is not set (S501: No), the control unit 41 of the management server 4 refers to the content fee database, various parameters for fee setting, and the content distribution history, and plays back on the client 2. Dynamic content pricing. Here, the charge database and various parameters for setting the charge are parameters set by the administrator of the management server 4, and the charge for the content is determined, for example, through the following steps.

  First, a basic fee for providing content determined between the user and the administrator is acquired (S506), and it is checked whether there is a record of the content distribution history of the content (S507). Since the fee information request from the client 2 includes a user ID and a content ID for identifying the content, these are collated with a content distribution history recorded by the management server 4. FIG. 4A is an example of the content distribution history of the management server 4, and shows the fee calculated from the user ID, the content ID, the basic fee, etc., and the period during which the content can be viewed according to the fee. A viewing time limit, a distribution status indicating a state at the time of distribution, and a time stamp indicating a distribution date and time are sequentially recorded for each history number. Preferably, the content distribution history after a certain period may be cleared sequentially. If the user ID and content ID of the fee information request match the user ID and content ID of the content distribution history as a result of collation with the content distribution history (S507: Yes), the set viewing time limit is indefinite. It is determined whether or not there is (S508). For example, if the viewing time limit is indefinite (S508: Yes), it is determined that the request is an appropriate redistribution request, and the charge amount related to the content distribution is “free” to prevent double charging. Alternatively, 0 (zero) is set (S504).

  If the viewing time limit is not indefinite (S508: No), the control unit 41 of the management server 4 acquires redistribution parameters from the content fee database and various parameters for fee setting (S509). The redistribution parameter may be a numerical value obtained by counting how many times the content has been distributed in the past, and a discount from the basic fee can be set based on the redistribution parameter. For example, when the re-distribution parameter is a value indicating distribution twice or more in the past, a service to the user such as applying a 50% discount to the content fee or reducing a certain amount is provided. sell.

  Next, the control unit 41 of the management server 4 acquires a different content fee parameter for each content (S510). The content fee parameter is a parameter specific to each content that varies depending on the content, quality, time, and other contracts with the content provider. The fee for the content is calculated from the content fee parameter and the basic fee. For example, the content fee parameter may be an amount to be added to or reduced from the basic fee, or a fixed premium or discount rate.

  Next, the control unit 41 of the management server 4 acquires a user parameter from the user ID included in the fee information request (S511). The user parameters are parameters set for each user such as age, gender, residential area, birthday, etc. in addition to contract type information between the administrator and the user. It is a parameter that can provide a discount campaign from the value of. For example, when setting the user parameter of the management server 4, the administrator may set a discount for other age groups in order to recommend content for users of a specific age group. .

  Next, the control unit 41 of the management server 4 refers to the ranking database of the management server 4 and acquires a ranking parameter (S512). The ranking parameter is a parameter related to the ranking (ranking) obtained by counting the number of distributions for each content, and is a parameter for which a charge can be set according to the popularity of the content. For example, the administrator sets a higher price if the content popularity is high, and conversely sets a low price if the content popularity is low. You may make it promote use.

  Next, the control unit 41 of the management server 4 refers to the content database of the center server 3 and acquires a freshness parameter set for each content (S513). The freshness parameter is a parameter that allows different charges to be set between new content and old content resulting from the creation or release time of the content. For example, the administrator sets a high price for new popular content, and conversely sets a low price for old content that has been published for a long time. It may be possible to suppress the use and promote the use by making the attractive price setting for the old contents cheap.

  Next, the control unit 41 of the management server 4 obtains a list of content related to the content for which the distribution request has been received from the related content table, and then refers to the content distribution history again to determine the content related to the past. It is searched whether there is a distribution history (S514), and if there is a content distribution history of content related in the past, a related content parameter is acquired (S515). The related content may be a series content such as a drama, a movie content by the same director, a music content by a specific artist, or the like. FIG. 5 is an example of a related content table, and a plurality of related content IDs are recorded for each related series together with a charge parameter applied to the related series. For example, in Series A, the content ID is associated with CID2, CID3, and CID6, and “0.8 ^ number” is set in the charge parameter. If a plurality of related contents are found as a result of the search, a charge parameter may be set according to the number of contents. For example, if the distribution of two contents CID2 and CID3 included in Series A is in the content distribution history, the charge parameter “0.8 ^ 2” = “0.64” is applied when distributing the new CID6 May be. Moreover, if it turns out that it adapts to several related series, you may set several discount.

  Next, the control unit 41 of the management server 4 sets a viewing time limit pattern based on the viewing time limit set by the administrator for each content for which a distribution request has been received (S516). For example, in the case of setting an indefinite viewing deadline for a certain content, the administrator can set a viewing deadline pattern for setting a fee that is higher than that for content with a deadline. Further, even when a time limit is attached, weighting may be performed with a plurality of parameters according to the length of the viewing time limit selected by the user, and different charge settings may be made for each.

  The control unit 41 of the management server 4 obtains each parameter necessary for calculating the charge through the above steps, and calculates the charge amount corresponding to the content charge information request (S517). In the case of a normal content distribution request in which no error flag is set, the administrator of the management server refers to not only the content distribution history for the user but also various parameters at that time related to the content as needed. It is possible to dynamically set distribution charges and set charges, and to provide flexible services to users. In addition, when a plurality of fee amounts can be calculated from combinations of parameter settings, the plurality of fee amounts may be calculated.

  The control unit 41 of the management server 4 calculates the fee setting ID and the fee if the fee is calculated based on various parameters (S517), or if the fee is set to “free” or 0 (zero) (S504). Charge information including the amount is set (S505). When a plurality of fee amounts can be calculated, a plurality of fee information may be set. FIG. 6 is an example of a fee setting table held by the management server 4 that records these fee information. The fee setting ID is a code for identifying the set fee amount, the user ID, the content ID, the distribution status, and the time stamp, and is registered in the fee setting table together with these data. The fee setting table temporarily stores fee information for the client 2 to register in the content distribution history when actually viewing the content. The charge information including the finally determined charge setting ID and the charge amount is notified from the management server 4 to the center server 3 (S402).

<Delivery request after displaying charges>
Returning to FIG. 2, in the distribution system 1, the operation after the step (S202) in which the client 2 displays the fee amount included in the fee information on the display unit 23, that is, the content distribution from the client 2 notified of the fee amount. Until the content is distributed from the center server 3 and the content distribution history of the management server 4 is updated.

  When the client 2 displays the fee amount set by the administrator who provides the content for the distribution of the content based on its fee information request, if the user agrees to the fee amount, the content is sent to the center server 3. Is requested (S203). When there are a plurality of fee amounts, when the user selects one of them, the control unit 41 of the client 2 selects the fee information (the fee setting ID and the fee amount) corresponding to the most desired fee amount from among them. Contain) and then request distribution of the content. The distribution request includes the user ID and the content ID, and the center server 3 that has received the distribution request performs user authentication (S305), and confirms the user ID and the content ID to the client 2 to confirm the content ID and content. Is distributed (S306).

  Upon receiving the content distribution, the client 2 transmits a reception completion notification to the center server 3 when the content reception is completed (S204). The reception completion notification only needs to include a fee setting ID, and may be fee information including a fee amount. Upon receiving the reception completion notification, the center server 3 transfers the reception completion notification to the management server 4 and requests registration to the content distribution history provided in the management server 4 (S307).

<Content distribution history registration>
The management server 4 requested to register to the content distribution history registers, for example, to the content distribution history shown in FIG. 4A (S403). The content distribution history includes a user ID, a content ID, a fee calculated from the basic fee, a viewing deadline indicating a period during which the content can be viewed according to the fee, and a distribution status indicating a state at the time of distribution. And a time stamp indicating the delivery date and time. Specifically, based on the notified fee setting ID, a new history registration is added with reference to the content distribution history.

  FIG. 4B is a diagram for explaining an example when new history numbers 006 and 007 are registered in the content distribution history (up to history number 005) shown in FIG. For example, a case where a history number 006 is newly registered will be described. In this case, the user 2 makes a re-distribution (replacement) request accompanying the reproduction error for the content CID1, that is, a charge information request in which the error flag is set (S501: Yes). Since user 2 records in the history number 002 that it has been recorded that the content CID1 with a viewing time limit: indefinite period is delivered at 10:15 on April 22, 2004 at a charge of 500 yen (S502: Yes), the management server 4 Is determined to be a re-distribution request accompanying a reproduction error, and the charge amount is set to 0 (S504), and charge setting ID 004 is registered in the charge setting table as charge information associated therewith (S505). Therefore, when receiving the fee setting ID 004 from the center server 3, the management server 4 refers to the fee setting table (FIG. 6) and registers other parameters such as history number 006 and user ID in the content distribution history (S403).

  Next, for example, a case where the history number 007 is newly registered will be described. In this case, a redistribution (addition) request is made for the content CID1 that has been distributed by user1 in the past (history number 001) after the viewing deadline has passed, that is, a charge information request with no error flag set. There is a case (S501: No). First, a basic content fee (for example, 500 yen) is acquired (S506). Since user1 records that content CID1 with a viewing time limit of 72 hours was distributed at 18:30 on April 20, 2004 at 18:30 on the history number 001 (S507: Yes, S508: No) The control unit 41 of the management server 4 acquires a re-distribution parameter (for example, −100 yen because it is the second distribution) from the content fee database and various parameters for setting the fee (S509). Subsequently, the applicable parameter is acquired from the various parameters, and the charge amount is calculated (S510 to S516). For example, if the ranking parameter (S512) and the viewing deadline pattern setting (S516) are applied, the content CID1 is in the top 100, so -100 yen is applied, and the viewing deadline is 24 hours. Since it is shortened, -100 yen is applied. As a result, the fee amount related to the redistribution request is calculated to be 200 yen (S517), and the fee setting ID 005 is registered in the fee setting table as fee information associated therewith (S505). Therefore, when receiving the fee setting ID 005 from the center server 3, the management server 4 refers to the fee setting table (FIG. 6) and registers other parameters such as history number 007 and user ID in the content distribution history (S403). .

  The distribution status, which is one of the other parameters, includes the content distribution history and the charge setting table, and indicates the state at the time of content distribution. New: New distribution, Replace: Redistribution (replacement), Further-Purchase: Re Distribution (addition), etc. are recorded. In the case of the history numbers 006 and 007, redistribution (replacement) and redistribution (addition) are recorded, respectively. When a new history is registered in the content distribution history (S403), the registration of the charge setting table corresponding to the recorded history may be deleted thereafter.

  When the content distribution history is updated according to the use of the content, the administrator of the management server 4 refers to the time stamp of the content distribution history and charges each user based on the content distribution history for the contract target period. That is, the actual fee can be collected. When a content distribution request is made by a user of the distribution system 1, problems such as double charging at the time of redistribution can be prevented if a reproduction error is involved. Moreover, not only the content distribution history for the user but also various parameters at that time related to the content can be referred to at any time to dynamically manage the content distribution fee setting. At the same time, the administrator can set a flexible fee reflecting the distribution status and contents.

  Further, in the distribution system 1, fee information corresponding to the fee setting at the time when a content request is made in the client 2 is determined, and this fee information is minimum data including a fee setting ID and a fee amount. Therefore, in the distribution system 1, as compared with the case where the content distribution history is managed using the electronic receipt, information such as the viewing limit number and the viewing time limit included in the electronic receipt is falsified and an unauthorized charge is made. There is no such thing.

  Note that the timing of registration (S403) in the content distribution history of the management server 4 is not limited to the case where the client 2 transmits a reception completion notification to the center server 3 (S204), so that the client 2 plays back the content. Registration may be requested to the content distribution history when it is first opened. The distribution system 1 of the above embodiment is a case where the content is distributed after the user selects the content from the content list, but is a case where the content is already downloaded automatically. However, only the content distribution timing is different, and other operation flows can be set in the same manner.

  The distribution system 1 of the present invention is not limited to the above system configuration. Any content distribution method for distributing content may be used as long as it implements the content distribution method of the above embodiment.

  The content distribution system of the present invention can be applied not only to a client such as a video viewing terminal installed at home, but also to a content distribution system to mobile devices such as mobile phones and in-vehicle devices.

It is a figure explaining the content delivery system 1 by preferable embodiment of this invention. Example 1 It is a flowchart which shows the charging method of the content delivery in the delivery system 1 by preferable embodiment of this invention. Example 1 It is a flowchart explaining the process in the management server 4 by preferable embodiment of this invention. Example 1 It is a figure explaining an example of the content delivery log | history of the management server 4 by preferable embodiment of this invention. Example 1 It is a figure explaining an example of the related content table in the management server 4 by preferable embodiment of this invention. Example 1 It is a figure explaining an example of the charge setting table in the management server 4 by preferable embodiment of this invention. Example 1

Explanation of symbols

1 Distribution system 2 Client 3 Center server 4 Management server

Claims (10)

A client that plays the delivered content,
A center server for delivering content to the client;
A management server for managing a content distribution history and a set fee table from the center server to the client,
The client executes processing for notifying the center server of a charge information request including a user ID and a content ID,
The center server receives the charge information request from the client and executes processing for inquiring charge information to the management server,
The management server performs a process of determining the charge information including a charge setting ID and a charge amount and notifying the center server based on the charge information request, the content distribution history, and the set charge table. Run,
The center server executes a process for notifying the client of the notified fee information,
The client executes a process of displaying a charge amount included in the charge information.
Content distribution system. The client notified of the fee information holds the fee setting ID and the content ID in association with each other, and executes a process of notifying the center server of the distribution request including the user ID and the content ID. And
When the center server receives the distribution request from the client, the center server executes a process of starting distribution of the content,
The client executes a process of notifying the center server of the charge setting ID when distribution of the content is completed,
The center server executes processing for notifying the management server of the notified fee setting ID,
The management server executes a process of updating the content distribution history based on the notified fee setting ID.
The content distribution system according to claim 1. The client performs a process of notifying a charge information request including an error flag set in relation to a content reproduction error;
When the management server receives the charge information request with the error flag set, it executes a process of determining free charge information based on the content distribution history.
The content distribution system according to claim 1 or 2. The set fee table for determining the fee information is:
Determined by a charge parameter that varies based on the content distribution history managed by the management server,
The content distribution system according to any one of claims 1 to 3. The program executed in the control part of the said client of the content delivery system in any one of Claim 1 to 4. The program for functioning a computer as the said management server of the content delivery system in any one of Claim 1 to 4. Notifying a charge information request including a user ID and a content ID to a center server that distributes content to a client;
Receiving the charge information request from the client and inquiring charge information from the center server to the management server that manages the content distribution history and the set charge table to the client;
Determining the charge information including a charge setting ID and a charge amount based on the charge information request, the content distribution history, and the set charge table, and notifying the center server;
Notifying the client of the notified fee information from the center server;
The client displaying a fee amount included in the fee information;
Content delivery method including: The client notified of the fee information holds the fee setting ID and the content ID in association with each other;
Notifying the center server of a distribution request including the user ID and the content ID;
Upon receiving the distribution request from the client, starting distribution of the content from the center server;
Notifying the fee setting ID from the client to the center server when distribution of the content is completed;
Notifying the notified fee setting ID from the center server to the management server;
Updating the content distribution history of the management server based on the notified fee setting ID;
The content delivery method according to claim 7 including: Notifying the management server of a charge information request including an error flag set in relation to a content reproduction error in the client;
When receiving the charge information request with the error flag set, determining free charge information based on the content distribution history;
The content delivery method according to claim 7 or 8, comprising: The set fee table for determining the fee information is:
Determined by a charge parameter that varies based on the content distribution history managed by the management server,
The content distribution method according to claim 7.

Images