JP2011113252A - Cache device, cache system and cache method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a cache device etc. for verifying the validity of a message received from a provider device or terminal equipment. <P>SOLUTION: A cache device 11 holds a sales history with authentication code including a first authentication code etc. generated by using at least a part of content sales history as a seed. When receiving a download request from terminal equipment 12, the cache device 11 specifies the sales history with authentication code of content to be downloaded when caching the content to be downloaded, and collates the first authentication code included in the specified sales history with authentication code with a second authentication code received from the terminal equipment 12. Only when collation succeeds, the cache device 11 transmits the content to be downloaded to the terminal equipment 12. When the content to be downloaded is not cached, the cache device 11 requests the download device 13 to distribute the content. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technology for causing a terminal device to download content purchased at a site on the Internet using the terminal device.

  A system that sells content such as videos, music, and electronic books on the Internet has become widespread, and a user uses a terminal device to access a provider device that is a server device that operates a site that sells content. And now you can easily purchase the contents sold on the site.

  In a system for selling content on the Internet, the content is sold to a download device, which is a server device that stores various content sold by the provider device and transmits the charged content to the user terminal device. It is generally installed separately from the provider device operated by a certain site.

  Regardless of whether the content is purchased or not purchased, there are many users accessing the sales site operated by the provider device, processing related to user operations such as content search processing, and processing for transmitting content to the user terminal device In addition to reducing the load on the provider device, the maintenance cost of the cache device can be reduced by providing a download device that can be used in common at a plurality of sites.

  When the number of provider devices that use download devices increases, such as when selling content in many countries, the download devices receive download requests from many provider devices, and after the provider devices receive download requests. Since the throughput for transmitting content to the terminal device is reduced, the load on the download device is distributed by providing each provider device with a cache device that receives a download request instead of the download device.

  The cache device for distributing the load of the download device makes a content distribution request to the download device when the content requested for download from the terminal device is not cached in the cache device, and sends the content distributed from the download device. When the content that has been cached and transmitted to the terminal device and the download request has been cached is cached, the cached content is transmitted to the terminal device without sending the content distribution request to the download device. Since the content is directly transmitted from the cache device to the terminal device without going through the provider device that has performed the charging processing of the content to be transmitted to the terminal device, the validity of the message transmitted by the terminal device when receiving a download request, , Provider equipment Problems that can not verify the validity in the cache unit of the message received from the remains.

  As an invention for verifying the legitimacy of a terminal device that is a content transmission destination, for example, in Patent Document 1, when receiving a content purchase request from a provider device, URI information including an access key is generated. When the URI information is transmitted to the provider device and the URI information is received from the terminal device, the validity of the access key included in the URI information is determined. A server device for transmitting content is disclosed.

  Further, in Patent Document 2, when a video transmission device serving as a download device receives a video transmission request from a terminal device, whether or not the user of the terminal device has a right to reproduce the video information requested to be transmitted. A moving image transmission method is disclosed in which the moving image transmission is stopped when the user does not have the right to reproduce the moving image information requested to be transmitted to the authentication device.

  Furthermore, in the inventions disclosed in Patent Document 1 and Patent Document 2 described above, the validity of the message received from the provider device or the terminal device could not be verified on the download device side. Japanese Patent Application No. 2009-268091 has already proposed a download device that can verify the validity of a message received from a provider device or terminal device using an authentication code generated from at least a part of the sales history received from the provider device.

Japanese Patent No. 3428979 Japanese Patent No. 4069652

  However, in the above-described invention, the cache device installed to distribute the load on the download device cannot verify the validity of the message received from the provider device or the terminal device. Accordingly, an object of the present invention is to provide a cache device, a cache system, and a cache method that can verify the validity of a message received from a provider device or a terminal device.

A first invention that solves the above-described problem is a cache device that transmits content sold at a site operated by a provider device to a terminal device, and manages all the content sold at the site. In addition to the first authentication code generated according to a predetermined algorithm using at least a part of the sales history including the identifier of the content and the identifier of the site as a seed from the downloaded download device, the transmission of the content An authentication code holding means for holding the received sales history with an authentication code when receiving the sales history with an authentication code that is the sales history including the identifier of the terminal device;
The terminal device receives a download request using the second authentication code generated by the provider device in the same procedure as the download device, and the URI of the download source in which at least the content identifier and the site identifier are embedded. If the content requested to be downloaded is held, and the content requested to be downloaded is not held, the content distribution request using the URI of the download source and the identifier of the terminal device is The authentication code held by the authentication code holding means when the download device holds the content distributed from the download device and then transmits the content to the terminal device and holds the content requested for download. In the sales history with code The sales history with the authentication code is specified by using the identifier of the content and the identifier of the site included in the URI of the download source and the identifier of the terminal device that requested the download, and the specified sales with the authentication code is specified. Using the first authentication code included in the history, the second authentication code included in the URI of the download source is verified, and only when the verification is successful, the content requested to be downloaded is requested to be downloaded. Transmitting means for transmitting to the terminal device is provided.

  According to the first invention, the terminal device used by the user is uniquely determined by the identifier of the terminal device, and the site and the content are uniquely determined by the identifier of the site and the identifier of the content, respectively. Therefore, by using the site identifier, the content identifier, and the terminal device identifier received from the terminal device when receiving the download request, the sales history with the authentication code corresponding to the download request is specified. And when the content that has received the download request is cached on the cache device side, the cache device includes the first authentication code included in the sales history with the authentication code corresponding to the download request, The terminal device when receiving a content download request By matching the received second authentication code, it is possible to verify the authenticity of the message received from the terminal device when receiving a download request.

  For example, if the identifier of the content received from the terminal device when the download request is received is falsified, the sales history with the authentication code cannot be specified, or the sales history with the authentication code is specified incorrectly. Therefore, the verification of the second authentication code using the first authentication code fails.

  Further, when the download device receives the content distribution request, if the download device side can verify the first authentication code, the cache device side caches the download request content. If not, the validity of the message received from the terminal device when a download request is received can be delegated to the download device.

  Further, in the cache device of the second invention, the sales history with the authentication code received from the download device includes the second authentication code generated by the provider device, and the transmission means includes the download source In addition to the second authentication code obtained from the URI, the second authentication code included in the identified sales history with the authentication code is also verified, and a download request is made only when two verifications are successful. The cache device according to the first aspect of the invention is characterized in that the transmitted content is transmitted to the terminal device that has requested download.

  According to the second invention, the second authentication code included in the sales history with the authentication code is generated on the provider device side based on at least a part of the sales history. By verifying the second authentication code included in the sales history with the authentication code, the cache device can verify the validity of the sales history of the content before transmitting the content.

  Further, in the cache device of the third invention, when the authentication code holding means receives the sales history with the authentication code, it adds an initial value download flag to hold the sales history with the authentication code, and the transmitting means. When the download completion request is received from the terminal device, the value of the download flag given to the sales history with the authentication code including the first authentication code used for verification is confirmed. If it is an initial value, a download completion notification request is made to the download device, and then the download flag is updated to a value indicating that it has been used for download. It is.

  According to the third invention, by adding the download flag to the sales history with the authentication code, the cache device refers to the download flag so that the content transmitted to the terminal device is re-downloaded. It becomes possible to determine whether or not the cache device side. When the download of the content purchased by the user is completed, it is necessary to send a download completion notification from the download device to the provider device. When the user re-downloads the purchased content, the download completion notification Need not be transmitted to the provider device, and if the cache device can determine whether or not the content to be transmitted to the terminal device is a re-download, only when the user has downloaded the content. The cache device can notify the download device that the download has been completed.

Furthermore, the fourth aspect of the invention is that a provider device that operates a site that sells content, a cache device that transmits the content sold on the site to the terminal device, and all that are sold on the site The provider device manages the content, and the provider device receives the purchase request for the content from the terminal device that has accessed the site, After generating a sales history including an identifier of the site and transmitting the identifier of the terminal device requested for purchase and the sales history to the download device, the second authentication is performed according to a predetermined algorithm using at least a part of the sales history as a seed. Generate a code and identify the content included in the sales history And comprising a sales means for transmitting the site identifier and the second at least embedded download source URI authentication code of the terminal device,
When the download device receives the sales history and the identifier of the terminal device from the provider device, the download device generates a first authentication code in the same procedure as the provider device, and the first authentication code and the identifier of the terminal device The first authentication code holding means for transmitting the sales history with the authentication code to the cache device, the URI of the download source, and the identifier of the terminal device. When the content distribution request is received from the cache device, the identifier of the content received from the cache device from the sales history with the authentication code held by the first authentication code holding means, the site The sales history with one authentication code is identified using the identifier and the identifier of the terminal device. The first authentication code included in the identified sales history with the authentication code is used to verify the second authentication code received from the cache device, and only when the verification is successful, the content requested to be distributed Distribution means for transmitting to the cache device, and when the cache server receives the sales history with an authentication code from the download device, second authentication code holding means for holding the received sales history with the authentication code; When a download request using the URI of the download source is received from the terminal device, it is confirmed whether or not the content requested to be downloaded is held. If the content requested to be downloaded is not held, the URI of the download source is checked. And distribution of the content using the identifier of the terminal device When the request is made to the download device, the content distributed from the download device is held and then transmitted to the terminal device, and the content requested for download is held, the second authentication code holding means One sale with an authentication code using the identifier of the content and the identifier of the site included in the URI of the download source and the identifier of the terminal device that requested the download from the held sales history with the authentication code Only when the history is specified, the second authentication code included in the URI of the download source is verified using the first authentication code included in the specified sales history with the authentication code, and the verification is successful, Send the download requested content to the terminal device that requested the download It is characterized by having a transmission means.

  Furthermore, in the cache system according to the fifth aspect of the present invention, the selling means of the provider device transmits the second authentication code and the second authentication code before transmitting the URI of the download source to the terminal device. The sales history used for generation is transmitted to the download device, and the first authentication code holding means of the download device holds the first authentication code, and then stores the second authentication code and the sales history. Is received from the provider device, and the sales history with the authentication code corresponding to the received sales history is specified from the sales history with the authentication code held by the first authentication code holding means, and specified. Including the second authentication code in the sales history with the authentication code, and the sales history with the authentication code including the second authentication code. And the transmission means of the cache device includes the second authentication code obtained from the URI of the download source and the second authentication code included in the identified sales history with the authentication code. The cache system according to the fourth invention is characterized in that the authentication code of 2 is also collated, and only when the two collations are successful, the content requested to be downloaded is transmitted to the terminal device that requested the download.

  Further, in the cache system of the sixth invention, when the download device receives a download completion notification request from the cache device, the download device generates a download completion notification corresponding to the download completion notification request and transmits the download completion notification to the provider device. And a second notification code holding unit of the cache device, when receiving the sales history with the authentication code, adds a download flag of an initial value and holds the sales history with the authentication code. When the transmission means receives a download completion request from the terminal device, the transmission means confirms the value of the download flag given to the sales history with the authentication code including the first authentication code used for verification. If the download flag is an initial value, the download of the content is completed. After a notification request to the downloading device, a cache system according to the fifth invention, characterized in that updating the flag to a value indicating that it is available for download.

  Further, the seventh invention provides a provider device operated by a site selling content, a terminal device used when accessing the site, and transmits the content sold at the site to the terminal device. And a content caching method using a download device that manages all the contents sold at the site, wherein the provider device receives the content from the terminal device that has accessed the site. Upon receipt of the purchase request, the sales history including the charged content and the identifier of the site is generated, and the identifier of the terminal device requested for purchase and the sales history are transmitted to the download device, and then the same as the download device. A second authentication code is generated in the procedure, and the content included in the sales history is And a download source URI at least including the second authentication code embedded in the terminal device, the download device sends the sales history and the terminal device identifier to the provider device. And receiving at least a part of the received sales history as a seed, generating a first authentication code according to a predetermined algorithm, and including the first authentication code and the identifier of the terminal device in the sales history Holding the sales history with the authentication code and transmitting the sales history with the authentication code to the cache device; b, when the cash device receives the sales history with the authentication code from the download device, the received authentication code Step c for holding attached sales history, the cash When the device receives a download request using the URI of the download source, the cache device holds the content requested to be downloaded in steps d and d to check whether the content requested to be downloaded is held. If not, step e wherein the cache device makes a distribution request to the download device using the URI of the download source and the identifier of the terminal device, and the download device receives the second authentication code One sales history with an authentication code is identified using the content identifier, the site identifier, and the terminal device identifier received from the cache device from the sales history with the authentication code held by the holding means. Sales with the specified authentication code A step of verifying the second authentication code received from the cache device using the first authentication code included in the history and transmitting the requested content to the cache device only when the verification is successful. f and a step g in which the cache device holds the content distributed from the download device and then transmits the content to the terminal device, and the cache device holds the content requested to be downloaded in the step d. If so, the content identifier and the site identifier included in the URI of the download source and the identifier of the terminal device that requested the download are included in the sales history with the authentication code held by the cache device. Use one of the authentication codes to identify the sales history The first authentication code included in the identified sales history with the authentication code is used to verify the second authentication code included in the URI of the download source, and the download request is made only when the verification is successful. The cache method is characterized in that the step h of transmitting the content to the terminal device that has requested download is executed.

Furthermore, in the cache method of the eighth invention, in the step a, the provider device uses the sales history used for generating the second authentication code before transmitting the download source URI to the terminal device. And the second authentication code to the download device,
In step b, when the download device receives the second authentication code and the sales history from the provider device after holding the first authentication code, the download device holds the second authentication code. Identifying the sales history with the authentication code corresponding to the received sales history from the sales history with the authentication code, including the second authentication code in the identified sales history with the authentication code, The sales history with the authentication code including the second authentication code is transmitted to the cache device, and in step f, the download device adds the second authentication code obtained from the URI of the download source. The second authentication code included in the identified sales history with the authentication code is also verified, and two verifications are successful. Only, the content requested to be transmitted is transmitted to the cache device, and in the step h, the cache device adds the specified authentication code in addition to the second authentication code obtained from the URI of the download source. The second authentication code included in the attached sales history is also verified, and only when two verifications are successful, the content requested to be downloaded is transmitted to the terminal device that requested the download. This is a caching method described in the invention.

  Further, according to a ninth aspect of the present invention, in the step c, when the cash device receives the sales history with the authentication code, the cash device attaches an initial value download flag to hold the sales history with the authentication code, and the step g Alternatively, after the execution of the step h, when the cache device receives a download completion request from the terminal device, the download given to the sales history with the authentication code used for the verification of the first authentication code Checking the value of the flag, and if the download flag is an initial value, after making a download completion notification request to the download device, updating the flag to a value indicating that it has been used for downloading i and the download device sends a download completion notification request to the cache device. Upon receiving from a eighth cache method according to the invention, wherein the step j to be transmitted to the provider apparatus generates a completion notification of download corresponding to the completion notification request of the download is performed.

  The fourth to sixth inventions relate to the cache system. According to the fourth to sixth inventions, the same effects as the first to third inventions can be obtained. . The seventh to ninth inventions relate to the cache method. According to the seventh to ninth inventions, the same effects as the first to third inventions can be obtained. .

  Thus, according to the present invention, it is possible to provide a cache device, a cache system, and a cache method that can verify the validity of a message received from a provider device or a terminal device.

The figure explaining the structure of a cache system. The figure explaining the hardware with which the server apparatus was equipped. The block diagram of a provider apparatus. The block diagram of a download apparatus. The block diagram of a cache apparatus. The 1st flowchart of the process performed when selling a content. The 2nd flowchart of the process performed when selling a content. The 3rd flowchart of the process performed when selling a content. The figure explaining the web page which displays the list of contents. The figure explaining the web page explaining the detail of a content. The figure explaining the web page for content purchase confirmation. The figure explaining the web page for download. The figure explaining the content of the sales history with an authentication code. The figure explaining URI of download origin. The flowchart explaining the procedure at the time of re-downloading a content. The figure explaining the web page for purchase histories.

  From this, the embodiments of the present invention will be described to the extent that those skilled in the art of the present invention can understand the contents of the present invention and implement the present invention.

  FIG. 1 is a diagram for explaining the configuration of a cache system 1 in the present embodiment. The cache system 1 illustrated in FIG. 1 is a system developed for a system that sells content. The cache system 1 illustrated in FIG. 1 includes at least the Internet 14 as a network and is owned by a user as a device. Sold at the terminal device 12, the provider device 10 on which a sales site (for example, an electronic book site) for selling content such as moving images, music, and electronic books is sold on the Internet 14, and the provider device 10 sales site One download device 13 that stores all the contents that have been stored, and a cache device 11 that receives a download request from the terminal device 12 instead of the download device 13 are included.

  FIG. 1 exemplifies a system configuration when a system for selling content is developed in many countries (in FIG. 1, country A and country B), and a plurality of provider devices 10 are used when developing a system for selling content in multiple countries. Is provided for each country, and a cache device 11 is provided for each country. Note that the download device 13 is provided with only one common device in each country.

  The cache device 11 of the cache system 1 shown in FIG. 1 is a device provided to distribute the load of the download device 13, and the download request for the content sold by the provider device 10 is the cache of the country where the content is sold. The content is transmitted from the cache device 11 to the terminal device 12 that has been transmitted to the device 11 and requested to download.

  If the cache device 11 is provided to distribute the load of the download device 13 as in the cache system 1 illustrated in FIG. 1, the download request for the content purchased by the user is cached without going through the provider device 10 that sold the content. Since the device 11 receives the request, the cache device 11 cannot verify the validity of the download request received from the terminal device 12, and the cache device 11 transmits the content to the terminal device. On the other hand, there is a problem that the validity of the sales history of the content cannot be verified.

  There are various methods for solving this problem. In the cache system 1 shown in FIG. 1, the validity of the download request received from the terminal device 12 and the validity of the sales history of the content transmitted to the terminal device 12 are verified. In addition, an authentication code generated based on the sales history of the content transmitted to the terminal device 12 is used.

  When the billing process for the content ends normally, a sales history of the content is generated on the provider device 10 side, transmitted to the download device 13, and a first authentication code based on the sales history received on the download device 13 side is generated. . The provider device 10 also transmits the content sales history to the download device 13 and then generates a second authentication code based on the content sales history. The second authentication code generated by the provider device 10 is the download device. 13 is transmitted.

  The download device 13 stores the first authentication code generated by the download device 13 itself and the second authentication code received from the provider device 10 in the sales history, and the sales history includes the authentication code. The sales history with the authentication code is transmitted to the cache device 11 corresponding to the provider device 10 that has transmitted the sales history.

  When the provider device 10 generates the second authentication code, the provider device 10 embeds the second authentication code in the URI (URI: Uniform Resource Identifier) of the content download source, and transmits the second authentication code from the provider device 10 to the terminal device 12. When 12 makes a download request of content using the URI of the download source to the cache device 11, the cache device 11 uses the first authentication code included in the sales history with the authentication code of the content requested to be downloaded, and downloads it. By verifying the second authentication code obtained by disassembling the original URI and the second authentication code included in the sales history with the authentication code, the validity of the download request received from the terminal device 12 and the download Validate the sales history of the requested content.

  From here, each apparatus which comprises the cache system 1 illustrated in FIG. 1 is demonstrated. The terminal device 12 used by the user of the cache system 1 has a function as an Internet terminal and is a general-purpose computer in which a computer program (here, a browser) for browsing web pages published on the Internet 14 is installed. Specifically, a commercially available device such as a mobile phone, a smartphone, or a personal computer can be used as the terminal device 12.

  The provider device 10, the cache device 11, and the download device 13 of the cache system 1 are server devices that are implemented using commercially available server devices, and the commercially available server devices include hardware as illustrated in FIG. 2. It is common that

  FIG. 2 is a diagram illustrating hardware provided in the server device 2 used as the provider device 10, the cache device 11, and the download device 13.

  A commercially available server device includes, as hardware, a CPU 2a (CPU: Central Processing Unit), a ROM 2b (ROM: Read-Only Memory) on which a BIOS is mounted, and a RAM 2c (RAM: Random Access Memory) which is a main memory of a computer. ), A large-capacity data storage device 2d (for example, a hard disk) as an external storage device, an input / output interface 2e for data communication with an external device, a network interface 2f for network communication, a display 2g, and characters An input device 2h and a pointing device 2i are provided.

  The data storage device 2d of the server device 2 used as the provider device 10 is mounted with a computer program for functioning as the provider device 10 according to the present invention, and is stored in the data storage device 2d of the server device 2 used as the cache device 11. Is installed with a computer program for functioning as the cache device 11 according to the present invention, and the data storage device 2d of the server device 2 used as the download device 13 has a computer for functioning as the download device 13 according to the present invention. The program is implemented. In addition to the data storage device 2d, the server device 2 used as the cache device 11 or the download device 13 stores a large number of contents, and a storage that can shorten the time from when a download request is received until the contents can be transmitted. It is common for systems to be connected.

  FIG. 3 is a block diagram of the provider device 10 included in the cache system 1. As shown in FIG. 3, the provider device 10 that operates the content sales site authenticates the sales means 100 that sells the content and the user who operates the terminal device 12 as functions realized by the computer program. A user authentication unit 101 that performs the accounting process related to the sale of the content, and the sales unit 100 that sells the content includes a second authentication code based on the sales history of the content for which the accounting process has been completed. Is provided.

  The user authentication unit 101 provided in the provider apparatus 10 is a unit for authenticating a user who purchases content. A specific method of user authentication may be used, but a user ID for identifying the user and a user password are input. A technique of displaying a web page on the terminal device 12 and collating a password transmitted from the terminal device 12 is widely used.

  Further, the charging unit 102 provided in the provider apparatus 10 is a unit for executing a charging process related to the sale of content, and a specific method of the charging process may be arbitrary. When credit settlement is used for billing processing related to the sale of content, the billing means 102 provided in the provider apparatus 10 transmits credit information such as a credit number input by the user to the credit company server, thereby allowing the user to Becomes a means to settle the purchased content. Further, when the points on the sales site are used for the billing process related to the sale of the content, the billing means 102 provided in the provider apparatus 10 determines the amount of the content from the point balance possessed by the user input at this time. This is a means for subtracting points corresponding to.

  The selling device 100 provided in the provider device 10 is a device for selling content to the user by switching the web page displayed on the terminal device 12 in accordance with the operation received from the user. The selling device 100 is provided in the provider device 10. The details of the selling means 100 will be described following the procedure executed when selling the content.

  FIG. 4 is a block diagram of the download device 13 included in the cache system 1. As shown in FIG. 4, the download device 13 that stores a plurality of contents includes a content DB 132 that stores all contents handled by all provider devices 10 as a database (DB: DataBase), and a provider. A sales history DB 133 that stores the sales history received from the device 10, and a sales history with an authentication code that is a sales history including the first authentication code generated based on the sales history received from the provider device 10. 1 authentication code DB 134 and a sales site DB 135 for storing information related to the sales site operated by the provider device 10 are provided, and the functions realized by the computer program are based on the sales history received from the provider device 10. 1 authentication code is generated and the generated first authentication The sales history with the authentication code including the code and the second authentication code received from the provider device 10 is stored in the first authentication code DB 134 and stored in the cache device 11 corresponding to the provider device 10 that has transmitted the sales history. When receiving a content distribution request from the first authentication code holding means 130 for transmitting the sales history with the authentication code and the cache device 11, the first authentication included in the sales history with the authentication code corresponding to the content distribution request A content distribution unit 131 is provided for executing verification using a code and transmitting the requested content to the cache device 11 when the verification is successful.

  In the content DB 132 provided in the download device 13, all the content handled by the provider device 10 includes the content main body, the content creator, the publisher, the tax-included price, the content ID that is the content identifier, the content Information indicating whether or not can be transmitted is added as attribute information and stored.

  The sales history DB 133 provided in the download device 13 stores the sales history transmitted from the provider device 10 and stores the sales history with an authentication code stored in the first authentication code DB 134 provided in the download device 13. Includes, in addition to the sales history received from the provider device 10, a first authentication code generated based on the sales history, and a terminal device ID which is an identifier of the terminal device 12 used when the content corresponding to the sales history is purchased. In addition, when the download device 13 receives the second authentication code from the provider device 10, the provider device 10 displays the sales history with an authentication code corresponding to the sales history used for generating the second authentication code. The received second authentication code is added.

  In the sales site DB 135 provided in the download device 13, information related to the sales site operated by the provider device 10 is stored for each sales site, and the information related to the sales site includes a sales site that is an identifier of the sales site. The ID, the URI of the sales site, the URI of the cache device 11 corresponding to the sales site, and the like are included.

  FIG. 5 is a block diagram of the cache device 11 included in the cache system 1. As shown in FIG. 5, the cache device 11 that transmits content to the terminal device 12 that requested the download has a second authentication code DB 113 that stores a sales history with an authentication code received from the download device 13 as a database, A cache DB 112 for storing the content received from the download device 13 is provided, and as a function realized by a computer program, a second authentication code for storing the sales history with an authentication code received from the download device 13 in the second authentication code DB 113 When receiving a code download unit 110 and a content download request from the terminal device 12, a content transmission unit 111 that transmits the download requested content to the terminal device 12 is provided.

  The content received from the download device 13 is stored in the cache DB 112 provided in the cache device 11, and the sales history with the authentication code received from the download device 13 is stored in the second authentication code DB 113 provided in the cache device 11. Is stored in the second authentication code DB 113, and the second authentication code holding unit 110 assigns a download flag to the sales history with the authentication code.

  By giving the download flag to the sales history with the authentication code, the cache device 11 can determine whether or not the content transmitted to the terminal device 12 is redownload by referring to the download flag. become. When the download of the content purchased by the user is completed, it is necessary to send a download completion notification from the download device 13 to the provider device 10, but when the user re-downloads the purchased content, the download completion notification is sent to the provider. If the cache device 11 can determine whether or not the content to be transmitted to the terminal device 12 is a re-download, it is not necessary to transmit it to the device 10, but only when the user downloads the content. The device 11 can notify the download device 13 that the download has been completed.

  From here, explaining the processing executed when selling the content, the sales means 100 provided in the provider device 10, the first authentication code holding means 130 and the content distribution means 131 provided in the download device 13, The second authentication code holding unit 110 and the content transmission unit 111 provided in the cache device 11 will be described in detail. Note that the description of the process executed when selling the content also serves as the description of the invention relating to the method.

  FIG. 6 is a first flowchart of processing executed when selling content, FIG. 7 is a second flowchart of processing executed when selling content, and FIG. It is a 3rd flowchart of the process performed when selling.

  First, the flow illustrated in FIG. 6 will be described. When a user starts a browser on the terminal device 12 and accesses a sales site operated by the provider device 10 (S1), the sales means 100 of the provider device 10 displays content sold on the sales site. A web page for display is transmitted to the terminal device 12 (S2).

  FIG. 9 is a diagram for explaining a web page 3a that displays a list of contents that are included in a web page for content display and sold on a sales site. In FIG. 9, the content is an electronic book, and as shown in FIG. 9, the web page 3 a that displays a list of content is included in the search result in addition to the search button 3 a 1 for searching by keyword or genre. The content list 3a2 is displayed, and a link to a web page explaining the details of the contents is pasted on the text 3a3 explaining the outline of the contents.

  When the text 3a3 of the content that the user wants to purchase (here, novel 1) is clicked on the browser, the web page displayed on the browser jumps to the link destination affixed to the text, and the user purchases. A web page describing details of the content desired to be displayed is displayed on the terminal device 12.

  FIG. 10 is a diagram for explaining a web page 3b for explaining details of content. The web page 3b illustrated in FIG. 10 displays a button 3b2 to be clicked when purchasing content in addition to an image of the content (here, novel 1) selected by the user and a detailed description 3b1. .

  The HTML that displays the button 3b2 illustrated in FIG. 10 includes a URI that describes the host name of the provider device 10, the name of a program that executes processing related to content purchase, and the content of the content that is displayed in FIG. An element for delivering the ID to the provider apparatus 10 is included.

  When the button 3b2 illustrated in FIG. 10 is clicked, a message related to a content purchase request specified by the delivered content ID is transmitted from the terminal device 12 to the provider device 10, so that the terminal device 12 transmits the provider. A content purchase request is made to the apparatus 10 (S3), and the message includes at least the name of a program that executes processing related to the content purchase and the content ID of the content purchased by the user.

  Upon receiving a content purchase request from the terminal device 12, the selling means 100 of the provider device 10 starts processing related to content purchase, and first receives a purchase request from the terminal device 12 as processing related to content purchase. A content transmission confirmation request is sent to the download device 13 (S4). Here, the transmission confirmation request for the content received from the terminal device 12 is requested to sell the content for the convenience of the content creator (for example, publisher) regardless of the convenience of the sales site operator. This is because may be stopped.

  When the provider device 10 requests the download device 13 to confirm the content transmission, the site ID of the sales site operated by the provider device 10, the content ID of the content, the content format, the selling price of the content, etc. 10 to the cache device 11.

  When the content distribution means 131 of the download device 13 receives a content transmission confirmation request from the provider device 10, the content distribution unit 131 refers to the content DB 132, confirms whether the content requested for transmission confirmation is valid, and requested the content transmission confirmation. A content transmission confirmation result is returned to the provider apparatus 10 (S5).

  When the transmission confirmation result received from the download device 13 indicates that the content is valid, the selling means 100 of the provider device 10 dynamically generates a purchase confirmation web page for the requested content. Then, the purchase confirmation web page for the requested content is transmitted to the terminal device 12 (S6), and the content purchase confirmation web page is displayed on the browser of the terminal device 12 (S7).

  FIG. 11 is a diagram for explaining a web page 3c for content purchase confirmation. The content purchase confirmation web page 3c shown in FIG. 11 is used for canceling the content purchase and the button 3c2 used for determining the content purchase in addition to the content title, sales price, etc. 3c1. Button 3c3 is displayed.

  The HTML for displaying the button 3c2 used for determining the purchase of the content includes a URI in which the host name of the provider device 10, the name of the program that executes the billing process for the content purchase, and the content purchase confirmation are displayed. An element for delivering the content ID of the content displayed on the web page 3c and the terminal device ID of the terminal device 12 to the provider device 10 is included.

  As a method for acquiring the terminal device ID which is an identifier of the terminal device 12, there is a method in which a cookie to be stored in the browser of the terminal device 12 by the provider device 10 is stored in a personal computer. In the case of a smartphone, an attribute for transmitting an individual identification number stored in a USIM mounted on a mobile phone or a smartphone may be described in HTML that displays a button 3c2 used for determining content purchase. .

  When the button 3c2 illustrated in FIG. 11 is clicked, a message related to the charging process for the content purchase is transmitted from the terminal device 12 to the provider device 10, so that the terminal device 12 charges the provider device 10 for the content purchase. A processing request is made (S8), and the message includes at least the name of the computer program that executes the charging processing for the content purchase, the content ID, and the terminal device ID.

  When a billing processing request for content purchase is received from the terminal device 12, the sales unit 100 of the provider device 10 first activates the user authentication unit 101, and the user authentication unit 101 authenticates the user who operates the terminal device 12. If successful, the charging unit 102 of the provider apparatus 10 is activated to execute the charging process for the content purchase (S9).

Upon receiving from the billing unit 102 that the billing process for the content that the user wishes to purchase is completed, the selling unit 100 of the provider apparatus 10
・ Site ID that is the identifier of the sales site
-Content ID that is the content identifier
Sales date and time when content billing processing ends. Sales history of content including the sales price of the sold content is generated, and the generated sales history and the terminal device ID delivered from the terminal device 12 are displayed. It transmits to the download device 13 (S10).

  When the sales history and the terminal device ID are transmitted from the provider device 10, the first authentication code holding means 130 of the download device 13 stores the sales history in the sales history DB 133 (S 11), and then from the provider device 10. The content ID and the site ID included in the received sales history are used as seeds, and a first authentication code is generated according to a predetermined algorithm. The generated first authentication code and the terminal device ID received from the provider device 10 are included. The first authentication code is held by storing the sales history with the authentication code as the sales history in the first authentication code DB 134 (S12).

  If the same content is sold at the same sales site, the first authentication code based on the sales history will have the same value even though the sales history is different. Is included in the seed of the first authentication code, the value of the first authentication code can be changed even in the case described above.

  The algorithm for generating the first authentication code can be arbitrarily selected, and it is preferable to use a hash function as the algorithm. However, when it is desired to increase security, an algorithm using an encryption key may be used. If the provider device 10 and the cache device 11 can have a common encryption key, a MAC (Message Authentication Code) may be used for the algorithm.

  The sales unit 100 of the provider device 10 transmits the sales history of the content for which the accounting process has been completed to the download device 13 in S10 of FIG. 6, and then uses the sales history transmitted to the download device 13 to obtain the second authentication code. The sales history and the second authentication code used when the second authentication code is generated are transmitted to the download device 13 (S13). The contents of the second authentication code generated by the sales unit 100 of the provider device 10 are the same as the first authentication code holding unit 130 of the download device 13, and here the sales unit 100 of the provider device 10 is the second authentication code. Details of generating the authentication code will not be described.

  When the sales history and the second authentication code are transmitted from the provider device 10, the first authentication code holding unit 130 of the download device 13 includes the authentication code-added sales history stored in the first authentication code DB 134. Then, the sales history with the authentication code corresponding to the sales history is searched, and the second authentication code received from the provider apparatus 10 is held by including the authentication code secondly in the searched sales history with the authentication code. (S14).

  FIG. 13 is a diagram for explaining the contents of a sales history with an authentication code stored in the first authentication code DB 134. FIG. 13A is a diagram illustrating the sales history 4a with an authentication code stored in the first authentication code DB 134 after the cache device 11 generates the first authentication code, and is illustrated in FIG. 13A. As described above, after the cache device 11 generates the first authentication code, the sales history with the authentication code stored in the first authentication code DB 134 includes the terminal device ID and the first authentication code in addition to the sales history. Is included.

  FIG. 13B illustrates the sales history 4b with an authentication code stored in the authentication code DB 114 after the cache device 11 receives the second authentication code from the provider device 10, and FIG. As illustrated, when the cache device 11 receives the second authentication code from the provider device 10, the second authentication code is added to the searched sales history with authentication code 4a, and the sales history with authentication code 4b includes: In addition to the sales history, the terminal device ID, the first authentication code, and the second authentication code are included.

  When the first authentication code holding unit 130 of the download device 13 holds the second authentication code received from the provider device 10, the first authentication code holding unit 130 refers to the sales site DB 135 and corresponds to the provider device 10 that has transmitted the second authentication code. The sales history with the authentication code including the second authentication code is transmitted to the cache device 11 (S15).

  When the second authentication code holding means 110 of the cache device 11 receives the sales history with the authentication code from the download device 13, the second authentication code holding means 110 assigns a download flag as an initial value, and uses the sales history with the authentication code as the second authentication code. Store in the DB 113 (S16).

  When the sales unit 100 of the provider device 10 generates a second authentication code from the sales history of the content for which the accounting process has been completed and transmits it to the download device 13, it generates a URI of the content source downloaded by the user, A web page for download including the URI is dynamically generated, the web page for download is transmitted to the terminal device 12 (S17), and the web page for download is displayed on the browser of the terminal device 12 (S18). .

  FIG. 12 is a diagram for explaining a download web page. The download web page 3d shown in FIG. 12 includes a button 3d2 for downloading the content purchased by the user to the terminal device 12 in addition to the detailed content 3d1 of the content purchased by the user, and the content purchased by the user. A button 3d3 for canceling the download is included.

  The HTML for displaying the button 3d2 for causing the terminal device 12 to download the content purchased by the user is used to deliver the URI of the download source of the content purchased by the user and the terminal device ID of the terminal device 12 to the cache device 11. Contains elements.

  FIG. 14 is a diagram for explaining the URI of the download source of the content purchased by the user. As shown in FIG. 14, a scheme (http: //) indicating that http is used for the URI of the download source of the content purchased by the user, and the host name of the cache device 11 corresponding to the provider device 10 ( www.ChasheServer.xxx), the name of the computer program that downloads the content (download), the site ID (SiteID = XXXX) of the sales site where the user purchased the content as a variable to be passed to the download processing program, and the user purchased The content ID of the content (ContentID = YYYYYYYY) and the second authentication code (AuthenticationCode2 = ZZZZ) generated on the provider device 10 side are added.

  When the button 3d2 illustrated in FIG. 12 is clicked, a message related to a download request for content purchased by the user is transmitted from the terminal device 12 to the cache device 11, so that the content is downloaded from the terminal device 12 to the cache device 11. A request is made (S19), and the message includes the terminal device ID of the terminal device 12 that requested the download in addition to the URI path of the download source.

  When a content download request is received from the terminal device 12, the content transmission means 111 of the cache device 11 first searches the cache DB 112 for a content corresponding to the content ID obtained by decomposing the URI of the download source, and this search result. The process is branched according to (S20).

  If the content requested to be downloaded is not stored in the cache DB 112 and cannot be retrieved, the content transmitting unit 111 of the cache device 11 proceeds to “A” and executes the flow shown in FIG. If the content requested to be downloaded is stored in the cache DB 112 and can be retrieved, the process proceeds to “B” and the flow shown in FIG. 8 is executed.

  First, the flow executed when the content requested to be downloaded is not stored in the cache DB 112 of the cache device 11 will be described with reference to FIG.

  If the content requested to be downloaded is not stored in the cache DB 112 of the cache device 11, the cache device 11 transfers a message relating to the content download request to the download device 13, thereby requesting distribution of the content requested to be downloaded. This is performed for the download device 13 (S21).

  When the content distribution unit 131 of the download device 13 receives a content distribution request from the cache device 11, the first authentication code indicates the sales history with the authentication code corresponding to the content specified by the message transmitted at the time of the content distribution request. By retrieving from the DB 134, the first authentication code used for collation is acquired (S22).

  For the search of the sales history with the authentication code, the site ID, the content ID, and the terminal device ID included in the message transmitted at the time of the content distribution request are used. The content distribution means 131 of the download device 13 includes the site ID and the content ID included in the message transmitted from the cache device 11 in the sales history, and the sales with the authentication code including the terminal device ID delivered from the terminal device 12. The history is searched from the first authentication code DB 134.

  When the content distribution unit 131 of the download device 13 searches the first authentication code DB 134 for the sales history with an authentication code corresponding to the content distribution request, the content authentication unit 131 uses the first authentication code included in the searched sales history with the authentication code. Then, the second authentication code obtained by disassembling the message transferred from the terminal device 12 is collated with the second authentication code added to the searched sales history with the authentication code (S23).

  When the content distribution means 131 of the download device 13 succeeds in each check, the content requested by the cache device 11 is searched from the content DB 132 and the content is distributed to the cache device 11 (S24). The cache device 11 downloads the content. The content received from the device 13 is cached in the cache DB 112 (S25). Note that the download device 13 does not distribute the content to the cache device 11 if the verification using the first authentication code fails.

  The cache device 11 receives the content received from the terminal device 12 from the download device 13, and the cache device 11 caches the content in the cache DB 112 and then transmits the content to the terminal device 12 that has received the download request. Then, the content is downloaded to the terminal device 12 (S27).

  When the content download is completed, a message relating to the content download completion request is transmitted to the cache device 11 by the browser function of the terminal device 12 (S28). This message includes the terminal device ID of the terminal device 12 in addition to the download URI path of the content that has been downloaded.

  When the content transmission unit 111 of the cache device 11 receives a message related to the download completion request from the terminal device 12, the content transmission unit 111 searches the second authentication code DB 113 for the sales history with the authentication code corresponding to the message, and searches. It is confirmed whether the value of the download flag given to the sales history with the authentication code is the initial value (S29).

  The flow in FIG. 7 is a flow executed when content is sold. In the flow in FIG. 7, the value of the download flag added to the searched sales history with an authentication code is always an initial value. The content transmission unit 111 of the device 11 updates the download flag assigned to the searched sales history with the authentication code to a value indicating that it has been used for downloading (S30).

  When the content transmission unit 111 of the cache device 11 updates the download flag assigned to the searched sales history with the authentication code, the content transmission unit 111 transmits a message related to the download completion notification request received from the terminal device 12 to the download device 13. Then, a download completion notification request is made to the download device 13 (S31). The message related to the download completion notification request includes a message received from the terminal device 12 when the cache device 11 receives the download completion request.

  When the download device 13 receives a download completion notification request from the cache device 11, the download device 13 indicates that the content has been downloaded, and indicates the site ID, content ID, second authentication code, terminal device ID, and information indicating the completion of the download. A completion notification including the above is generated (S32).

  The reason why the download device 14 generates a download completion notification and transmits it to the provider device 10 is that the processing related to the sale of the content is completed when the provider device 10 receives the download completion notification. .

  When the download device 13 generates the download completion notification, the download device 13 uses the sales site DB 135 to identify the provider device 10 corresponding to the cache device 11 that has requested the download completion notification, and notifies the specified provider device 10 of the download completion notification. Is transmitted (S33), and the provider device 10 receives a download completion notification (S34), the procedure illustrated in FIG. 7 ends.

  Next, a flow executed when the content requested to be downloaded is stored in the cache DB 112 of the cache device 11 will be described with reference to FIG.

  When the content requested to be downloaded is stored in the cache DB 112 of the cache device 11, the content transmission unit 111 of the cache device 11 responds to the download request without transferring a message related to the content download request to the download device 13. The first authentication code used for collation is acquired by searching the sales history with the authentication code to be searched from the second authentication code DB 113 of the cache device 11 (S40). Note that the content transmitting unit 111 of the cache device 11 searches for the sales history with an authentication code corresponding to the download request is the same as that of the download device 13, and therefore the description thereof is omitted here.

  When the content transmission unit 111 of the cache device 11 retrieves the sales history with the authentication code corresponding to the download request from the second authentication code DB 113, the content transmission unit 111 uses the first authentication code included in the retrieved sales history with the authentication code. The second authentication code obtained by disassembling the URI of the download source URI is compared with the second authentication code added to the searched sales history with the authentication code (S41).

  When the content transmission unit 111 of the cache device 11 succeeds in each collation, it transmits the retrieved content to the terminal device 12 (S42). Note that the content transmission unit 111 of the cache device 11 does not transmit the content to the terminal device 12 if the verification using the first authentication code fails.

  Similar to the float illustrated in FIG. 7, the content transmission unit 111 of the cache device 11 transmits the content that has received the download request to the terminal device 12, so that the content is downloaded to the terminal device 12 (S 43). When the download is completed, a message related to the content download completion request is transmitted to the cache device 11 by the browser function of the terminal device 12 (S44).

  When the content transmission unit 111 of the cache device 11 receives a message related to the download completion request from the terminal device 12, the content transmission unit 111 searches the second authentication code DB 113 for the sales history with the authentication code corresponding to the message, and searches. It is checked whether the value of the download flag given to the sales history with the authentication code is an initial value (S45).

  The flow shown in FIG. 8 is executed when the content is sold. In the flow shown in FIG. 8, the value of the download flag assigned to the searched sales history with the authentication code is always an initial value. The content transmission unit 111 of the device 11 updates the download flag assigned to the searched sales history with the authentication code to a value indicating that it has been used for downloading (S46).

  When the content transmission unit 111 of the cache device 11 updates the download flag assigned to the searched sales history with the authentication code, the content transmission unit 111 transmits a message related to the download completion notification request received from the terminal device 12 to the download device 13. Then, a download completion notification request is made to the download device 13 (S47).

  Upon receiving the download completion notification request from the cache device 11, the download device 13 generates a download completion notification (S48).

  When the download device 13 generates the download completion notification, the download device 13 uses the sales site DB 135 to identify the provider device 10 corresponding to the cache device 11 that has requested the download completion notification, and notifies the specified provider device 10 of the download completion notification. Is transmitted (S49), and the provider device 10 receives a download completion notification (S50), the procedure illustrated in FIG. 8 ends.

  Next, a procedure for re-downloading the content purchased by the user will be described with reference to FIG. FIG. 15 is a flowchart for explaining the procedure for re-downloading the content. In the present invention, when the user re-downloads the content purchased, the download completion notification request is not sent from the cache device 11 to the download device 13. The download device 13 does not generate or transmit a download completion notification.

  When a user operates a browser activated on the terminal device 12 to access a sales site operated by the provider device 10 and authenticates the user and then accesses a redownload page to request a redownload (S51), The sales means 100 of the provider device 10 transmits a purchase history web page displaying the history of the content purchased by the user at the sales site to the terminal device 12 (S52), and the purchase history web page is displayed on the browser of the terminal device 12. A web page is displayed (S53).

  FIG. 16 is a diagram for explaining a purchase history web page. In FIG. 16, the content is an electronic book, and as shown in FIG. 16, a list 3e1 of the content purchased by the user is displayed on the purchase history web page 3e, and in the text 3e2 explaining the outline of the content, An element for delivering the URI of the download source when the content is downloaded and the terminal device ID of the terminal device 12 to the cache device 11 is included. Note that the content of the URI of the download source when the content is downloaded is the same as described above.

  When one of the texts 3e2 illustrated in FIG. 16 is clicked, a message related to the content download request is transmitted from the terminal device 12 to the cache device 11, so that the content download request is sent from the terminal device 12 to the cache device 11. The message includes the terminal device ID of the terminal device 12 that requested the download in addition to the URI path of the download source.

  When the content re-download request is received from the terminal device 12, the content transmission unit 111 of the cache device 11 first searches the cache DB 112 for content corresponding to the content ID obtained by decomposing the URI of the download source ( S55). Here, since the content requested to be downloaded is re-downloaded, the content is cached in the cache DB 112.

  When the content requested to be downloaded is searched, the cache device 11 searches the second authentication code DB 113 of the cache device 11 for the sales history with the authentication code corresponding to the re-download request, and thereby the first authentication used for verification. A code is acquired (S56).

  When the content transmission unit 111 of the cache device 11 retrieves the sales history with the authentication code corresponding to the download request from the second authentication code DB 113, the content transmission unit 111 uses the first authentication code included in the retrieved sales history with the authentication code. The second authentication code obtained by disassembling the URI of the download source URI is compared with the second authentication code added to the searched sales history with the authentication code (S57).

  When the content transmission unit 111 of the cache device 11 succeeds in each collation, it transmits the retrieved content to the terminal device 12 (S58). Note that the cache device 11 does not transmit the content to the terminal device 12 if the verification using the first authentication code fails.

  The cache device 11 transmits the content that has received the re-download request to the terminal device 12 so that the content is downloaded to the terminal device 12 (S59). When the content download is completed, the browser device of the terminal device 12 functions. , A message related to the content download completion request is transmitted to the cache device 11 (S60).

  When the cache device 11 receives a message relating to the download completion request from the terminal device 12, the cache device 11 searches the second authentication code DB 113 for a sales history with an authentication code corresponding to the message, and searches the sales history with the authentication code. Check the value of the download flag assigned to.

  In the process of FIG. 15, in order to re-download the content purchased by the user, the re-download flag assigned to the searched sales history with the authentication code is updated to a value indicating that it has been used for download instead of the initial value. Therefore, the cache device 11 ends this procedure without sending the completion notification generation request to the download device 13.

DESCRIPTION OF SYMBOLS 1 Content download system 10 Provider apparatus 100 Sales means 101 User authentication means 102 Charge means 11 Cache apparatus 110 2nd authentication code holding means 111 Content transmission means 112 Cache DB
113 Second authentication code DB
12 terminal device 13 download device 130 first authentication code holding means 131 content distribution means 132 content DB
133 Sales history DB
134 First authentication code DB
135 Sales site DB
14 Internet

Claims (9)

A cache device that transmits content sold on a site operated by a provider device to a terminal device,
Generated according to a predetermined algorithm from a download device that manages all of the contents sold on the site as a seed using at least a part of the sales history including the identifier of the content that has been charged and the identifier of the site In addition to the first authentication code, when receiving the sales history with the authentication code that is the sales history including the identifier of the terminal device that is the transmission destination of the content, the received sales history with the authentication code is held An authentication code holding means,
The terminal device receives a download request using the second authentication code generated by the provider device in the same procedure as the download device, and the URI of the download source in which at least the content identifier and the site identifier are embedded. If the content requested to be downloaded is held, and the content requested to be downloaded is not held, the content distribution request using the URI of the download source and the identifier of the terminal device is The authentication code held by the authentication code holding means when the download device holds the content distributed from the download device and then transmits the content to the terminal device and holds the content requested for download. In the sales history with code The sales history with the authentication code is specified by using the identifier of the content and the identifier of the site included in the URI of the download source and the identifier of the terminal device that requested the download, and the specified sales with the authentication code is specified. Using the first authentication code included in the history, the second authentication code included in the URI of the download source is verified, and only when the verification is successful, the content requested to be downloaded is requested to be downloaded. A cache device comprising a transmission means for transmitting to a terminal device.   The sales history with the authentication code received from the download device includes the second authentication code generated by the provider device, and the transmission means obtains the second authentication obtained from the URI of the download source. In addition to the code, the second authentication code included in the identified sales history with the authentication code is also verified, and the terminal device that has requested download of the content requested to be downloaded only when two verifications are successful The cache device according to claim 1, wherein   When the authentication code holding means receives the sales history with the authentication code, the authentication code holding means assigns an initial download flag to hold the sales history with the authentication code, and the transmission means receives a download completion request from the terminal device. The download flag value given to the sales history with the authentication code including the first authentication code used for verification is confirmed. If the download flag is an initial value, the download of the content is performed. 3. The cache device according to claim 2, wherein after the completion notification request is made to the download device, the download flag is updated to a value indicating that the download device has been used for downloading. The provider device that manages the site that sells the content, the cache device that transmits the content sold on the site to the terminal device, and manages all the content sold on the site A cache system comprising at least a download device,
When the provider device receives a purchase request for the content from a terminal device that has accessed the site, the provider device generates a sales history including the charged content and the identifier of the site, and the identifier of the terminal device that requested the purchase and the identifier After the sales history is transmitted to the download device, a second authentication code is generated according to a predetermined algorithm using at least a part of the sales history as a seed, and the content identifier and the site identifier included in the sales history And a sales means for transmitting to the terminal device the URI of the download source in which at least the second authentication code is embedded,
When the download device receives the sales history and the identifier of the terminal device from the provider device, the download device generates a first authentication code in the same procedure as the provider device, and the first authentication code and the identifier of the terminal device The first authentication code holding means for transmitting the sales history with the authentication code to the cache device, the URI of the download source, and the identifier of the terminal device. When the content distribution request is received from the cache device, the identifier of the content received from the cache device from the sales history with the authentication code held by the first authentication code holding means, the site The sales history with one authentication code is identified using the identifier and the identifier of the terminal device. The first authentication code included in the identified sales history with the authentication code is used to verify the second authentication code received from the cache device, and only when the verification is successful, the content requested to be distributed A delivery means for transmitting to the cache device;
The cache server, upon receiving the sales history with the authentication code from the download device, second authentication code holding means for holding the received sales history with the authentication code;
When a download request using the URI of the download source is received from the terminal device, it is confirmed whether or not the content requested to be downloaded is held. If the content requested to be downloaded is not held, the URI of the download source is checked. A request for distribution of the content using the identifier of the terminal device is sent to the download device, the content distributed from the download device is held, and then transmitted to the terminal device, and the content requested for download is held. The content identifier and the site identifier included in the URI of the download source and the terminal that requested the download from the sales history with the authentication code held by the second authentication code holding means. One using device identifier The sales history with the authentication code is specified, and the second authentication code included in the URI of the download source is verified using the first authentication code included in the specified sales history with the authentication code. A cache system comprising: a transmission unit that transmits the content requested to be downloaded to the terminal device that requested the download only when the content is successful. The selling means of the provider device uses the second authentication code and the sales history used to generate the second authentication code before transmitting the download source URI to the terminal device. To
When the first authentication code holding means of the download device receives the second authentication code and the sales history from the provider device after holding the first authentication code, the first authentication code holding means A sales history with an authentication code corresponding to the received sales history is identified from the sales history with an authentication code held by a means, and the second authentication code is added to the identified sales history with an authentication code. Including the second authentication code and sending the sales history with the authentication code to the cash device;
In addition to the second authentication code obtained from the URI of the download source, the transmission unit of the cache device also checks the second authentication code included in the identified sales history with the authentication code. 5. The cache system according to claim 4, wherein only when two collations are successful, the content requested to be downloaded is transmitted to the terminal device that requested the download. When the download device receives a download completion notification request from the cache device, the download device includes a completion notification generation unit that generates a download completion notification corresponding to the download completion notification request and transmits the download completion notification to the provider device.
When the second authentication code holding means of the cache device receives the sales history with the authentication code, the second authentication code holding means assigns an initial value download flag to hold the sales history with the authentication code, and the transmission means includes the terminal When a download completion request is received from the device, the value of the download flag given to the sales history with the authentication code including the first authentication code used for verification is confirmed, and the download flag is an initial value. 6. The cache system according to claim 5, wherein the flag is updated to a value indicating that it has been used for downloading after making a download completion notification request to the download device. A provider device that operates a site that sells content, a terminal device that is used when accessing the site, a cache device that transmits content sold on the site to the terminal device, and the site A caching method using a download device that manages all of the contents sold,
When the provider device receives the content purchase request from the terminal device that has accessed the site, the provider device generates a sales history including the charged content and the site identifier, and the identifier of the terminal device that requested the purchase After the sales history is transmitted to the download device, a second authentication code is generated in the same procedure as the download device, and the content identifier and the site identifier included in the sales history and the second authentication code are generated. Transmitting the URI of the download source embedded with at least to the terminal device a,
When the download device receives the sales history and the identifier of the terminal device from the provider device, the download device generates at least a part of the received sales history as a seed, generates a first authentication code according to a predetermined algorithm, and Holding a sales history with an authentication code in which the authentication code of 1 and the identifier of the terminal device are included in the sales history, and transmitting the sales history with an authentication code to the cache device b,
When the cash device receives the sales history with the authentication code from the download device, the cache device retains the received sales history with the authentication code c.
When the cache device receives a download request using the URI of the download source, it confirms whether the content requested to be downloaded is held d,
In the step d, if the cache device does not hold the content requested to be downloaded, the cache device sends a distribution request for the content using the URI of the download source and the identifier of the terminal device. Step e, and the download device includes the identifier of the content received from the cache device, the identifier of the site, from the sales history with the authentication code held by the second authentication code holding means, and One sales history with an authentication code is specified using the identifier of the terminal device, and the second authentication received from the cache device using the first authentication code included in the specified sales history with the authentication code. Only when the code is verified and the verification is successful, before delivery is requested And step f of transmitting the content to the cache unit, said cache device, step g to be transmitted to the terminal device is performed after holding the contents distributed from the downloading device,
In the step d, when the cache device holds the content requested to be downloaded, the content included in the URI of the download source from the sales history with the authentication code held in the cache device. Identifying the sales history with one authentication code using the identifier of the site, the identifier of the site and the identifier of the terminal device that requested the download, and using the first authentication code included in the identified sales history with the authentication code, The second authentication code included in the URI of the download source is collated, and only when the collation is successful, the step h of transmitting the download requested content to the terminal device that requested the download is executed.
A caching method characterized by the above. In the step a, the provider device transmits the sales history and the second authentication code used for generating the second authentication code to the download device before transmitting the URI of the download source to the terminal device. To
In step b, when the download device receives the second authentication code and the sales history from the provider device after holding the first authentication code, the download device holds the second authentication code. Identifying the sales history with the authentication code corresponding to the received sales history from the sales history with the authentication code, including the second authentication code in the identified sales history with the authentication code, Sending the sales history with the authentication code including the second authentication code to the cash device;
In step f, in addition to the second authentication code obtained from the URI of the download source, the download device also checks the second authentication code included in the identified sales history with the authentication code. Only when two verifications are successful, the content requested for distribution is sent to the cache device,
In the step h, the cache device verifies the second authentication code included in the identified sales history with the authentication code in addition to the second authentication code obtained from the URI of the download source. The cache method according to claim 7, wherein only when two collations are successful, the content requested to be downloaded is transmitted to the terminal device that requested the download. In the step c, when the cash device receives the sales history with the authentication code, the cash device gives an initial value download flag to hold the sales history with the authentication code,
After step g or step h is executed,
When the cache device receives a download completion request from the terminal device, the cache device checks the value of the download flag assigned to the sales history with the authentication code used for the verification of the first authentication code, and the download flag Is an initial value, after making a download completion notification request to the download device, updating the flag to a value indicating that it has been used for download;
When the download device receives a download completion notification request from the cache device, step j is executed to generate and send a download completion notification corresponding to the download completion notification request to the provider device. The cache method according to claim 8.

Images