JP6997405B1 - Cache server, content provision system, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently manage a license for using a content. SOLUTION: A cache server has a storage unit for storing content received from a server, a request acquisition unit for acquiring request information including information for specifying content from a terminal device, and a storage unit for storing content specified by request information. The content transmission unit that reads from and sends it to the terminal device, the cache expiration date management unit that determines whether the retention period of the content stored in the storage unit is within the predetermined expiration date, and the retention period exceeds the expiration date. If the update processing unit that performs the update request processing that requests the server to update the content and the content that is the target of the update request processing are rejected by the server, the content whose update is rejected is displayed. It is provided with a notification unit for notifying the terminal device that the license for use is invalid. [Selection diagram] Fig. 3

Description

Embodiments of the present invention relate to a cache server, a content providing system, and a program.

In recent years, a system that distributes various digital contents to a plurality of terminal devices via a computer network has been used. Further, in such a system, a cache server that intervenes between the content server that distributes the content and the terminal device and caches the content is used. By using the cache server, the terminal device can receive the content from the cache server without directly accessing the content server.

Japanese Unexamined Patent Publication No. 2005-173876

The above content may be licensed to allow its use. In such cases, if the license has expired, the user will not be able to use the content.

An object to be solved by the present invention is to provide a cache server, a content providing system, and a program capable of efficiently managing licenses for using the content.

The cache server according to the first aspect of the present invention is specified by the storage unit for storing the content received from the server, the request acquisition unit for acquiring the request information including the information for specifying the content from the terminal device, and the request information. A content transmission unit that reads the content to be read from the storage unit and transmits the content to the terminal device, and a cache expiration date for determining whether or not the storage period of the content stored in the storage unit is within a predetermined expiration date. The management unit, the update processing unit that performs the update request processing that requests the server to update the content when the retention period exceeds the expiration date, and the content that is the target of the update request processing. It is provided with a notification unit for notifying the terminal device that the license for using the content for which the update is refused is invalid when the update is refused by the server.

In the content providing system according to the second aspect of the present invention, the cache server and the terminal device are connected via a network, and the cache server stores the content received from the server and the content from the terminal device. A request acquisition unit that acquires request information including specific information, a content transmission unit that reads the content specified by the request information from the storage unit and transmits the content to the terminal device, and the content storage unit stored in the storage unit. A cache expiration management unit that determines whether the content retention period is within a predetermined expiration date, and an update that requests the server to update the content when the retention period exceeds the expiration date. When the update processing unit that performs request processing and the update of the content that is the target of the update request processing are rejected by the server, the license for using the content whose update is rejected is invalid. It is provided with a notification unit for notifying the terminal device of the fact.

The program according to the third aspect of the present invention includes a process of storing content received from a server in a storage device in a computer, a process of acquiring request information including information for specifying the content from a terminal device, and the request information. A process of reading the content specified by the method from the storage device and transmitting the content to the terminal device, and a process of determining whether or not the storage period of the content stored in the storage device is within a predetermined expiration date. When the retention period exceeds the expiration date, the update request process for requesting the update of the content to the server and the update of the content subject to the update request process are rejected by the server. In this case, the process of notifying the terminal device that the license for using the content whose update has been refused is invalid is executed.

According to the present invention, it is possible to provide a cache server, a content providing system, and a program capable of efficiently managing licenses for using contents.

FIG. 1 is a diagram showing an example of a configuration of a content providing system according to an embodiment. FIG. 2 is a diagram showing an example of the hardware configuration of the cache server according to the embodiment. FIG. 3 is a diagram showing an example of the functional configuration of the cache server according to the embodiment. FIG. 4 is a flowchart showing an example of the renewal request process and the process for notifying the invalidity of the license according to the embodiment. FIG. 5 is a table showing an example of the relationship between the cache expiration date, the presence / absence of a license, and the availability of cache data according to the embodiment. FIG. 6 is a diagram showing an example of a request header according to an embodiment. FIG. 7 is a sequence diagram showing an example of processing when the license is valid in the content providing system according to the embodiment. FIG. 8 is a sequence diagram showing an example of processing when the license is invalid in the content providing system according to the embodiment.

Hereinafter, exemplary embodiments of the present invention will be disclosed. The configurations of the embodiments shown below, as well as the actions, results, and effects produced by such configurations, are examples. The present invention can be realized by a configuration other than the configurations disclosed in the following embodiments, and at least one of various effects and derivative effects based on the basic configuration can be obtained.

FIG. 1 is a diagram showing an example of the configuration of the content providing system 1 according to the embodiment. The content providing system 1 includes a content server 11 (server), a cache server 12, and a plurality of client terminals 13 (terminal devices).

The content server 11 is an information processing device that distributes a predetermined content via a computer network, and may be, for example, a Web server or the like. The "content" means software, data, or the like for realizing a predetermined function in the client terminal 13. The type of content should not be limited, but may be, for example, software, data, or the like that allows a user such as a student to view teaching materials or the like on the client terminal 13.

The cache server 12 is an information processing device that caches the content distributed from the content server 11. The cache server 12 exemplified here is communicably connected to the content server 11 via an external network 14 such as the Internet, and is connected via an internal network 15 such as a LAN (Local Area Network) or a WLAN (Wireless Local Area Network). It is communicably connected to each of the plurality of client terminals 13. The cache server 12 executes a process for managing each client terminal 13 by using a MIB (Management Information Base) or the like.

The client terminal 13 is an information processing device that realizes a predetermined function by using the content distributed from the content server 11, and may be, for example, a personal computer (tablet type terminal, notebook PC, smartphone, etc.).

The configuration shown in FIG. 1 is an example, and the configuration of the content providing system 1 is not limited to this. For example, a plurality of content servers 11 may exist, or there may be one client terminal 13. Further, the content server 11 and the cache server 12 may be connected via an internal network such as a LAN, or the cache server 12 and the client terminal 13 may be connected via an external network such as the Internet. Further, the client terminal 13 and the content server 11 may be able to directly communicate with each other.

FIG. 2 is a diagram showing an example of the hardware configuration of the cache server 12 according to the embodiment. The cache server 12 exemplified here includes a control device 51, a storage device 52, a communication I / F (Interface) 53, and a user I / F 54.

The control device 51 is a processor including a CPU (Central Processing Unit), a RAM (Random Access Memory), a ROM (Read Only Memory), and the like. The CPU operates the RAM as a working area according to a program stored in a non-volatile storage medium such as a ROM, and performs arithmetic processing for realizing various functions.

The storage device 52 is a storage configured by using a non-volatile storage medium such as an SSD (Solid State Drive) and an HDD (Hard Disk Drive). The storage device 52 stores various data necessary for realizing the function of the cache server 12. The storage device 52 may, for example, include content delivered from the content server 11, a MIB file for managing each client terminal 13, a request header (request information) received from the client terminal 13, a response header received from the content server 11, and the like. Remember.

The communication I / F 53 is a device for establishing communication with the content server 11 via the external network 14, communication with the client terminal 13 via the internal network 15, and the like. The user I / F 54 is a device that enables information to be sent / received to / from the user (administrator), and may be, for example, a keyboard, a pointing device, a display, a speaker, or the like.

The configuration shown in FIG. 2 is an example, and the configuration of the cache server 12 is not limited to the above, and should be appropriately selected within a range in which the functions described later can be realized.

FIG. 3 is a diagram showing an example of the functional configuration of the cache server 12 according to the embodiment. The cache server 12 includes a storage unit 101, a request acquisition unit 102, a cache processing unit 103, a content transmission unit 104, a cache deadline management unit 105, an update processing unit 106, and a notification unit 107. These functional components 101 to 107 are configured by the cooperation of the hardware components 51 to 54 exemplified in FIG. 2 and software components such as a program stored in a ROM or the like.

The storage unit 101 stores (caches) the content received from the content server 11. In addition, the storage unit 101 stores various data necessary for processing such as caching and reading of contents.

The request acquisition unit 102 acquires the request header transmitted from the client terminal 13. The request header includes information for specifying the content requested to be used by the client terminal 13 and authentication information for specifying the user (licensee). The request header acquired by the request acquisition unit 102 is stored in the storage unit 101.

The cache processing unit 103 performs processing for caching the content received from the content server 11 in the storage unit 101.

The content transmission unit 104 reads the content corresponding to the request header from the storage unit 101 and transmits it to the client terminal 13.

The cache deadline management unit 105 manages the retention period of the content cached in the storage unit 101. The cache expiration date management unit 105 determines whether or not the retention period of the cached content is within a predetermined cache expiration date. The cache expiration date may be set in consideration of, for example, a predetermined maximum retention period, a ratio of the retention period to the elapsed period from the date when the content is created or changed, a predetermined minimum retention period, and the like. The cache expiration date is not limited to the above, and should be appropriately set according to the usage status, the type of content, and the like.

The update processing unit 106 performs update request processing for requesting the content server 11 to update (retransmit) the cached content when the retention period of the cached content exceeds the cache expiration date. In the update processing unit 106, for example, the ratio of the retention period to the elapsed period from the date when the retention period exceeds the maximum retention period (for example, 30 days, etc.) or the content is created or changed is a predetermined value (for example, 90%, etc.). ) May be exceeded, update request processing may be performed. Further, the update processing unit 106 may not perform the update request processing when the storage period is less than the minimum storage period (for example, 7 days or the like).

When the content server 11 rejects the update of the content that is the target of the update request processing (the cache has expired) (when the rejection response is received), the notification unit 107 of the content whose update is rejected. Notifies (transmits) the license expiration information indicating that the license is invalid (the license has expired) to the client terminal 13.

With the above configuration, when the cache expiration date of the content cached in the cache server 12 expires, the cache server 12 automatically executes the update request processing, and the license of the content is valid based on the success or failure of the update request processing. It is determined whether or not there is. Then, when the license is invalid (when the update of the content is refused), the client terminal 13 is notified that the license of the content is invalid.

FIG. 4 is a flowchart showing an example of the renewal request process and the process for notifying the invalidity of the license according to the embodiment. The cache expiration date management unit 105 determines whether or not the retention period of the content cached in the storage unit 101 is within the cache expiration date (S101). If the retention period is within the cache expiration date (S101: Yes), this routine ends. When the retention period is not within the cache expiration date (S101: No), the update processing unit 106 requests the content server 11 to update (retransmit) the content (S102).

After that, the update processing unit 106 determines whether or not the content update is permitted by the content server 11 (S103). When the content update is not permitted (when a rejection response is received from the content server 11) (S103: No), the notification unit 107 notifies the client terminal 13 that the license of the content is invalid. (S104). On the other hand, when the content update is permitted (S103: Yes), the update processing unit 106 updates the cache data using the received content (S105).

FIG. 5 is a table showing an example of the relationship between the cache expiration date, the presence / absence of a license, and the availability of cache data according to the embodiment. As shown in FIG. 5, when the cache expiration date is valid and the content license is valid, the client terminal 13 can use the content. If the cache expiration date is valid and the license is invalid (expired), the client terminal 13 is limited to the data cached in the cache server 12 or the data cached in the client terminal 13 itself. Content is available. In this case, information outside the range of the cached data (for example, information changed on the content server 11 side, linked information, etc.) cannot be used. If the cache expiration date is valid and there is no license (no license acquisition history), the client terminal 13 cannot use the content.

When the cache expiration date is invalid and the license is valid, the content in the cache server 12 is updated (retransmitted from the content server 11), and the client terminal 13 can use the content. If the cache expiration date is invalid and the license is invalid or absent, the client terminal 13 cannot use the content.

FIG. 6 is a diagram showing an example of a request header according to an embodiment. The request header 201 exemplified here includes an if-non-match header 211 that enables the client terminal 13 to specify the content requested to be used. The value of the if-non-match header 211 is assigned to each content. Further, even if the content is the same, if the content is changed, the value of the if-non-match header 211 is changed. By using such an if-non-match header 211, the content server 11 and the cache server 12 can specify the content requested from the client terminal 13. Further, by using such an if-non-match header 211, it is possible to determine whether or not the content acquired by the client terminal 13 and the content cached in the cache server 12 are in the latest state. The structure of the request header is not limited to the above, and should be appropriately designed according to the usage situation and the like.

FIG. 7 is a sequence diagram showing an example of processing when the license is valid in the content providing system 1 according to the embodiment. Here, a case where the first client terminal 13 accesses a plurality of times and then the second client terminal 13 accesses a plurality of times is illustrated.

When the first client terminal 13 transmits the request header 201 at the time of the first access of the first client terminal 13 (S201), the content server 11 caches the content corresponding to the request header 201 and the response header. It is transmitted to the server 12 (S202). The response header includes, for example, information indicating permission / denial of the request, information that makes the content identifiable (for example, a header having the same value as the if-non-match header 211), and the like. The cache server 12 caches the content received from the content server 11 (S203), and transmits the content to the first client terminal 13. The first client terminal 13 receives the content from the cache server 12 and starts using the content (S204).

When the first client terminal 13 transmits the request header 201 (S211) at the time of the second and subsequent access of the first client terminal 13, the cache server 12 has the content corresponding to the request header 201 (here, here). (It is assumed that it is within the cache expiration date) is read from the cache data (storage unit 101) and transmitted to the first client terminal 13 (S212). The first client terminal 13 transmits an if-non-match header 211 in order to confirm whether or not the received content has been changed (S213). Upon receiving the if-non-match header 211, the content server 11 transmits information indicating whether or not the corresponding content has been changed (here, "Not-Modified" indicating that the content has not been changed) ("Not-Modified"). S214). When the first client terminal 13 receives Not-Modified, it starts using the content received from the cache server 12 (S215).

When the second client terminal 13 transmits the request header 201 (S221) at the time of the first access of the second client terminal 13, the content server 11 transmits the response header to the request header 201 (S222). The response header contains information that can determine whether or not the content of the content corresponding to the request header 201 (if-non-match header 211) has been changed. Here, it is assumed that the content has not been modified (Not-Modified). When the cache server 12 receives the response header, the cache server 12 reads the content corresponding to the request header 201 (here, it is assumed that it is within the cache expiration date) from the cache data and transmits it to the second client terminal 13 (S223). .. The second client terminal 13 receives the content and starts using the content (S224).

When the second client terminal 13 transmits the request header 201 (S231) at the time of the second and subsequent access of the second client terminal 13, the cache server 12 has the content corresponding to the request header 201 (here, here). (Assuming that it is within the cache expiration date) is read from the cache data and transmitted to the second client terminal 13 (S232). The second client terminal 13 transmits an if-non-match header 211 to confirm whether or not the received content has been changed (S233). Upon receiving the if-non-match header 211, the content server 11 transmits information indicating whether or not the corresponding content has been changed (here, "Not-Modified" indicating that the content has not been changed) ("Not-Modified"). S234). When the second client terminal 13 receives Not-Modified, it starts using the content received from the cache server 12 (S235).

FIG. 8 is a sequence diagram showing an example of processing when the license is invalid in the content providing system 1 according to the embodiment. When the client terminal 13 transmits the request header 201 at the time of the first access of the client terminal 13 (S301), the content server 11 permits the login of the client terminal 13 and refuses to use the content (S302).

At the time of the second and subsequent access of the client terminal 13, the client terminal 13 transmits the request header 201 (S311). When the retention period of the content corresponding to the request header 201 is within the cache expiration date, the cache server 12 reads the content from the cache data and transmits it to the client terminal 13 (S312). The client terminal 13 can use the received content only within the range cached in the cache server 12 (S313). At this time, among the contents received by the client terminal 13, the contents changed from the time of caching, the contents requiring a link to the external site, and the like cannot be used.

The cache server 12 executes an update request process for the content server 11 for the content whose retention period exceeds the cache expiration date among the cached contents (S321). The update request processing is performed regardless of the presence or absence of a request from the client terminal 13. In this example, since the license of the content is invalid, the content server 11 refuses to update (retransmit) the content subject to the update request processing (S322). When the cache server 12 receives a response from the content server 11 indicating that the update is rejected, the cache server 12 notifies each client terminal 13 that the license of the content whose update is rejected is invalid (S323). Each client terminal 13 outputs a warning display indicating that the license of the content has expired in response to the notification received from the cache server 12 (S324).

Programs for realizing the above functions are files in installable format or executable format, such as CD (Compact Disc) -ROM, flexible disc (FD), CD-R (Recordable), and DVD (Digital Versatile). It can be recorded and provided on a recording medium that can be read by a computer such as a disk). In addition, the program may be provided or distributed via a network such as the Internet.

According to the above embodiment, when the cache expiration date of the content cached in the cache server 12 has expired, the cache server 12 automatically executes the update request processing, and the license of the content is based on the success or failure of the update request processing. Is valid or not. Then, when the license is invalid (when the update of the content is refused), the client terminal 13 is notified that the license of the content is invalid. This makes it possible to efficiently manage the license for using the content.

Further, in the above embodiment, in the update processing unit 106, the retention period of the content exceeds the predetermined maximum retention period, or the ratio of the retention period to the elapsed period from the date when the content is created or changed exceeds the predetermined value. If so, update request processing is performed. By setting the cache expiration date in this way, the update request processing can be executed at an appropriate timing.

Further, in the above embodiment, the update processing unit 106 does not perform the update request processing when the retention period of the content is less than the predetermined minimum retention period. As a result, it is possible to avoid an unnecessary increase in the execution frequency of the update request process.

Further, in the above embodiment, the request header 201 (request information) includes information (if-non-match header 211) that makes it possible to determine whether or not the content of the content has been changed. As a result, it is possible to determine whether or not the content acquired by the client terminal 13 and the content cached in the cache server 12 are up-to-date by using the information included in the request header 201.

Although the embodiments of the present invention have been exemplified above, the above-described embodiment is an example and is not intended to limit the scope of the invention. The above embodiment can be implemented in various other embodiments, and various omissions, replacements, combinations, and changes can be made without departing from the gist of the invention. In addition, specifications such as each configuration and shape (structure, type, direction, type, size, length, width, thickness, height, number, arrangement, position, material, etc.) are changed as appropriate. Can be carried out.

1 ... content providing system, 11 ... content server (server), 12 ... cache server, 13 ... client terminal (terminal device), 14 ... external network, 15 ... internal network, 51 ... control device, 52 ... storage device, 53 ... Call I / F, 54 ... User I / F, 101 ... Storage unit, 102 ... Request acquisition unit, 103 ... Cache processing unit, 104 ... Content transmission unit, 105 ... Cache deadline management unit, 106 ... Update processing unit, 107 ... Notification unit, 201 ... Request header (request information), 211 ... if-non-match header

Claims (7)

A storage unit that stores the content received from the server,
A request acquisition unit that acquires request information including information that identifies the content from the terminal device, and
A content transmission unit that reads the content specified by the request information from the storage unit and transmits the content to the terminal device.
A cache expiration management unit that determines whether or not the storage period of the content stored in the storage unit is within a predetermined expiration date, and a cache expiration management unit.
Whether or not the request information corresponding to the content subject to the update request processing has been acquired for the update request processing for requesting the server to update the content whose retention period has exceeded the expiration date. The update processing unit that is performed regardless of
Notification to notify the terminal device that the license for using the content for which the update is refused is invalid when the update of the content subject to the update request processing is refused by the server. Department and
A cache server with. The update processing unit performs the update when the retention period exceeds a predetermined maximum retention period, or when the ratio of the retention period to the elapsed period from the date when the content is created or changed exceeds a predetermined value. Perform request processing,
The cache server according to claim 1. The update processing unit does not perform the update request processing when the retention period does not reach a predetermined minimum retention period.
The cache server according to claim 1 or 2. The request information includes information that makes it possible to determine whether or not the content of the content has been changed.
The cache server according to any one of claims 1 to 3. A content providing system in which a cache server and a terminal device are connected via a network.
The cache server is
A storage unit that stores the content received from the server,
A request acquisition unit that acquires request information including information that identifies the content from the terminal device, and
A content transmission unit that reads the content specified by the request information from the storage unit and transmits the content to the terminal device.
A cache expiration management unit that determines whether or not the storage period of the content stored in the storage unit is within a predetermined expiration date, and a cache expiration management unit.
Whether or not the request information corresponding to the content subject to the update request processing has been acquired for the update request processing for requesting the server to update the content whose retention period has exceeded the expiration date. The update processing unit that is performed regardless of
Notification to notify the terminal device that the license for using the content for which the update is refused is invalid when the update of the content subject to the update request processing is refused by the server. Department and
To prepare
Content provision system. The terminal device outputs information indicating that the license of the content is invalid based on the notification from the notification unit.
The content providing system according to claim 5. On the computer
The process of storing the content received from the server in the storage device,
The process of acquiring request information including information that identifies the content from the terminal device, and
A process of reading the content specified by the request information from the storage device and transmitting the content to the terminal device.
A process of determining whether or not the storage period of the content stored in the storage device is within a predetermined expiration date, and a process of determining whether or not the storage period is within a predetermined expiration date.
Whether or not the request information corresponding to the content subject to the update request processing has been acquired for the update request processing for requesting the server to update the content whose retention period has exceeded the expiration date. Processing to be performed regardless of
When the update of the content subject to the update request process is rejected by the server, the process of notifying the terminal device that the license for using the content for which the update is rejected is invalid. When,
A program to execute.

Images