KR20150040172A - Method for caching contents based on content request record and request priority and HTTP cache server using the method - Google Patents

Abstract

Between a web server and a client, a cache server caches content and determines, using a cache key acquired from a request for content from the client, if content corresponding to the cache key is a caching target. At the time, based on cache key related information, which includes time requested when requests are made and the number of requests, it can be determined if the content is a caching target or not. If the content is determined as a caching target, the cache server caches the content and provides the content for the client.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a content caching method and a content caching method,

The present invention relates to a Hypertext Transfer Protocol (HTTP) cache server and a method for caching content by an HTTP cache server.

[0003] With the development of communication technology, various contents are digitized through a network, and content sharing is performed through the Internet. An HTTP proxy (hereinafter referred to as a proxy) server has a cache server between a device for providing content on the Internet and a device for receiving content It assists the service so that smooth service can be operated while relaying data.

The cache server is located between a device that receives content, that is, a client, and a device that provides content, that is, a web server. When a cache server receives a request for a data request from a client for a specific HTTP address, , And if not in the cache server repository, fetch data from the source server of the specific HTTP address requested and provide it to the client. The specific HTTP address corresponding to the data and data provided to the client is stored in the repository.

In this case, the cache server receives data from the original server in response to the request from the client to the cache server repository and transfers the data to the client. In response to the same request, The ability to store in the repository is called caching.

The server that performs these caching functions is called a cache server. In general, the source server uses a large storage area to store all the content necessary for the service. However, the cache server uses a small capacity storage area and caches .

Since cache server generally uses less space than the source server, various algorithms are used to efficiently manage caching data stored in limited storage space. The most commonly used method is LRU (least recently used) algorithm.

A cache server using a limited storage space must delete one or more existing cached contents in order to secure a space for caching new contents when all of the repositories are in use. In the cache server, the LRU algorithm is used to select the content to be deleted. In the LRU algorithm, the content with the oldest last usage time among the contents stored in the repository is selected as the deletion target.

In case of managing the repository using the LRU algorithm, unspecified contents with little possibility of repeated requests from clients are stored in the cache server's storage at the time of first request and given the highest priority. If there is no reuse, the priority of the LRU algorithm is gradually decreased, and finally, if the LRU algorithm falls to the lowest rank, it can be selected as the content to be deleted.

If a large number of contents are selected and deleted after being cached and deleted once or after providing a small number of services, the operating load of the hard disk used as a cache storage generally increases. An increase in the storage operation load of the cache server causes the service speed to be lowered and the cache efficiency is also lowered because the limited storage space can not be efficiently used.

1 is an exemplary view illustrating a storage management state of a cache server using an LRU algorithm.

For example, as shown in FIG. 1, content provided from a source server is provided to a client via a cache server and is stored (cached) in a cache server's storage. Here, the portion denoted by H indicates the hot content, that is, the content frequently used.

If only three pieces of content can be stored (cached) in the cache server's storage, the high priority H1 and H2 are still used according to the LRU algorithm. However, the remaining unused content (cold contents) C1 to C8 are stored in the cache server's storage And the storage operation load of the cache server is increased as the storage / deletion process is repeatedly performed.

SUMMARY OF THE INVENTION The present invention provides a method of efficiently caching content in a content providing service and a cache server using the same.

According to an aspect of the present invention, there is provided a content caching method, comprising: receiving a request for content from a client in a cache server caching content between a web server and a client; Obtaining a cache key from the request; Wherein if the content corresponding to the request is not cached in the cache server, the cache-key-related information, i.e., the information includes the request time and the number of requests, ; And caching the content and providing the content to the client if the content is determined to be a caching target.

The determining whether the content is a caching target may determine that the content is a caching target when a request corresponding to the cache key occurs within a set time and the number of requests corresponding to the cache key is equal to or greater than a preset number.

The cache key related information may additionally include ranking information based on the number of requests. In this case, the step of determining whether the content is the caching target may include: when a request corresponding to the cache key occurs within the set time, and ranking information according to the number of requests corresponding to the cache key is included in a set upper rank, It can be judged to be a caching target.

The cache key related information may additionally include ranking information based on the number of requests. At this time, the step of determining whether or not the caching target is performed includes a step of generating a request corresponding to the cache key within a set time, a ranking information of the cache key being a higher ratio, and the upper ratio being a total number of cache keys If the content is included in the number corresponding to the setting ratio, it can be determined that the content is a caching target.

The cache key related information may additionally include ranking information based on the number of requests. At this time, the step of determining whether or not the caching target is performed includes a step of generating a request corresponding to the cache key within a set time, a ranking information of the cache key being a higher ratio, , The content can be judged to be a caching target.

Meanwhile, the cache-key related information may further include a correction value obtained by dividing the file size of the content, the number of requests, and the content size, and the ranking information may be rank based on the correction value.

The cache-key related information may further include a correction value obtained by dividing a file size of the content, a cumulative transfer amount of the content during the set time, and a request count divided by the content size and the cumulative transfer amount, It can be one rank.

According to another aspect of the present invention, there is provided a content caching method comprising the steps of: receiving a request for content from a client in a method for a cache server to cache content between a web server and a client; Obtaining a cache key from the request; A first determination method, a second determination method, and a third determination method for determining whether the content is a caching target based on the cache-key-related information when the content corresponding to the request is not cached in the cache server Determining whether the content is a caching target, using at least one of the content; And caching the content and providing the cached content to the client when the content is determined to be a caching target, wherein the cache key related information includes the requested time, the number of requests, and the ranking information.

Wherein the first determination method is a method of determining that the content is a caching subject when the number of requests corresponding to the cache key is equal to or greater than a preset number, Wherein the cache control unit determines that the content is a caching target when the ranking information is included in a set upper rank, A number corresponding to a setting ratio of the total number of keys or a number corresponding to a setting ratio of the total number of requests of the cache keys obtained up to the present time, and judges that the content is a caching target Lt; / RTI >

The determining whether the content is a caching target may determine that the content is a caching target when a request corresponding to the cache key occurs within a set time.

In addition, the step of determining whether or not the caching target is the caching target may include determining at least one of the first determination method, the second determination method, and the second determination method, taking into consideration at least one of the entire range of the content, At least one of a determination method and a third determination method may be used.

According to another aspect of the present invention, there is provided a cache server for providing contents between a web server and a client, the object cache server comprising: A table, and attribute information related to a request of a client, the attribute information including a request time and a request count corresponding to a cache key, A cache key storage unit including a table; A cache key generation unit for obtaining a key from a Hypertext Transfer Protocol (HTTP) request received from a client; A caching object determining unit that determines whether the content corresponding to the cache key is a caching object based on the information stored in the request record table and the request record ranking table when the obtained cache key is not present in the object cache key table; A caching storage unit for caching the content provided from the web server server when the content corresponding to the cache key is a caching target; And a data providing unit for providing cached contents corresponding to the request to the client.

In the request record table, a request time is stored for each cache key. Rank information based on the number of requests and the number of requests for each cache key may be stored in the request record ranking table.

Wherein the request record ranking table further includes a correction value obtained by dividing a file size of the content, a cumulative transfer amount of the content during the set time, a request quantity divided by a content size and a cumulative transfer amount, and the rank information is based on the correction value And may further include a correction order.

If the number of requests corresponding to the cache key is equal to or greater than the preset number, the caching target determining unit determines that the content is a caching target, A second determination method of determining that the content is a caching target when the content is included in the cache, a ranking ratio of the cache key being a higher ratio, Or a third determination method of determining that the content is a caching target when the upper rate is included in the number of cases corresponding to the setting ratio of the total number of requests of the cache keys acquired so far, Can be determined.

According to the embodiment of the present invention, it is possible to efficiently determine whether caching is performed by efficiently distinguishing popular content frequently used in content service and non-popular content having a small number of times of use. Accordingly, the popular contents can be received from the original server, transmitted to the client and simultaneously cached, and then provided to the original server without requesting the original server at the request of the client. In addition, since the uninvited contents are received from the original server and transmitted to the client, the non-infringing contents are not cached, thereby preventing unnecessary contents from being cached in the cache server storage and increasing the load on the cache server.

Therefore, the cache server effectively minimizes the storage load due to the non-delivery contents while faithfully performing the original function, thereby providing a faster and more stable service.

1 is an exemplary view illustrating a storage management state of a cache server using an LRU algorithm.
2 is a diagram illustrating a network environment in which a content service is performed according to an embodiment of the present invention.
FIG. 3 illustrates an exemplary structure of an object cache key table according to an embodiment of the present invention. FIG. 4 illustrates an exemplary structure of a request log table according to an exemplary embodiment of the present invention. Referring to FIG.
5 is a diagram illustrating a structure of a request record ranking table according to an embodiment of the present invention.
FIGS. 6, 7, and 8 are diagrams illustrating the structure of a request record ranking table based on additional parameters to be considered.
9 is a flowchart of a content caching method according to an embodiment of the present invention.
10 is a diagram illustrating a structure of a cache server according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

Throughout the specification, when an element is referred to as "comprising ", it means that it can include other elements as well, without excluding other elements unless specifically stated otherwise.

Hereinafter, a method of storing contents according to an embodiment of the present invention and a cache server using the method will be described with reference to the drawings.

2 is a diagram illustrating a network environment in which a content service is performed according to an embodiment of the present invention.

As shown in FIG. 2, the cache server 100 is located between a server providing content, that is, a web server 200 and a client 300.

The web server 200 provides the client 300 with content corresponding to the request for providing the content from the client to the origin web server that provides the requested content.

A request to request content from a client is to request content corresponding to a URL (uniform resource locator) in response to a Hypertext Transfer Protocol (HTTP) request. These HTTP requests consist of a GET parameter / POST parameter or an HTTP request header (Header) in addition to the base URL.

The cache server 100 plays a role of relaying data between the web server 200 and the client 300. The cache server 100 performs caching of contents and provides cached contents for repeated requests, thereby reducing the load on the original web server and enabling quick service.

The cache server 100 according to the embodiment of the present invention includes a caching storage unit 10 for storing contents to be cached and determines whether to cache the contents provided from the web server 200 to the client 300 , And only the content for which caching is determined is stored and managed in the caching storage unit.

To this end, the cache server 100 separately manages the object information and the request record / request record order information on the content, and determines whether to cache the content based on the managed information. The object information represents information on the cached contents, and the request record / request record order represents information related to the request from the client.

The object information is information on contents that are cached contents, that is, contents requested by the client and provided to the client and then cached and managed by the cache server 100. The object information includes a cache key assigned to the cached data, And includes information related thereto. One cache key is assigned to one caching data.

The request record / request record rank information is based on a request from a client, and specifically includes information (for example, a time when the content is requested) about the content requested by the client. The request record / request record order information may include a cache key and related information.

The cache key is generated based on a request input from the client. For example, the cache key can be generated using a part or all of the request of the client, that is, the HTTP request. In the embodiment of the present invention, the cache key can be generated using information excluding the GET parameter in the client request URL. Alternatively, depending on the situation, protocol, domain, and port information may be additionally omitted in the client request and the cache key may be generated using the remainder. For example, in "http://vod.domain.com:80/sample.mp4?id=1234", the object cache key is "http://vod.domain.com:80/sample. mp4 ", or "/sample.mp4" excluding the GET parameter and domain information. By excluding the protocol, domain, and port information, even if the domain is wrong, the same content can be recognized if the path is the same.

The method of generating a cache key according to an embodiment of the present invention is not limited to that described above.

The object cache key table includes the cache key, the cache path, and the last request time. Here, the cache path represents a physical storage path in which the actual contents are stored in the cache server, and the last request time represents a time when the client last requested the cached contents and is used for managing the freshness of the cached contents.

The request log table includes a cache key and a request time. The request time indicates a time when a request from a client is input for content having the corresponding cache key. When a request is input from the client, the request time is stored corresponding to the cache key obtained from the request.

FIG. 3 is a diagram illustrating a structure of an object cache key table according to an embodiment of the present invention, including a cache key obtained from a client request, a storage path of a cache server storage, and a last request time for a corresponding cache key. In the object cache key table, the cache key must be unique and the last request time is used to manage the freshness of the cache server. FIG. 4 is a diagram illustrating a structure of a request log table according to an exemplary embodiment of the present invention, including a cache key obtained in a client request and a requested time for the corresponding cache key. In the request history table, the cache key is not unique and is added at each client request.

FIGS. 3 and 4 illustrate the case where the request "http://sample.com/sample1.mp4", "http://sample.com/sample2.mp4", "http://sample.com/sample3.mp4" And the like are input, the information stored in the request record table and the object cache key table is shown.

The cache path can use the value obtained by changing the file name of the contents by using the hash function as the cache path and the value of "/ var / cache / 00/01/0000000000001" or "/ cache / 1" Lt; / RTI > The method of obtaining the cache path is not limited to this.

As described above, when a client request for content is input, the cache server according to the embodiment of the present invention generates a cache key using part of the information of the client request, and determines whether the content is cached And caches only content determined to be cached. A determination method based on various caching conditions may be used to determine whether caching is to be performed or not, that is, whether content corresponding to the request is a caching target. Basically, the content exists in the web server that is the source server and is not cached in the cache server, and it is judged whether or not the content is cached based on the previously requested record.

As a method of determining a caching target according to an embodiment of the present invention, an N-times requesting method may be used. The N-times request method is a method of determining a caching target based on whether a request for arbitrary content has occurred N times or more within the most recent set time. That is, the content corresponding to the request exists in the web server which is the source server and is not cached in the cache server, and the request time is within the set time (for example, 10 minutes) based on the current time, When the set number of times (for example, twice) is satisfied, the content is determined as a caching target.

For example, when a condition for caching is set up within two hours or more within one hour (3600 seconds), referring to the tables of FIGS. 3 and 4, the cache key "http://sample.com/sample1 quot ;, " .mp4 "has been requested twice for the request times" 1375251000 "and" 1375253000 ", respectively. When the request corresponding to the cache key occurs in the time of "1375251000 ", it occurs within the set time 1 hour (3600 seconds), but since the request is not satisfied twice, the content for the request is received from the web server, And is not stored in the storage unit of the cache server. However, if the request corresponding to the cache key subsequently occurs at the time of "1375253000 ", then" 1375253000 ", since the interval between the two requests is within one hour (3600 seconds) The contents provided from the web server are delivered to the client and stored in the storage unit of the cache server, that is, cached.

In addition, as a method of determining a caching target according to an embodiment of the present invention, a ranking entry method may be used. The upper ranking entry method is a method of determining a caching target based on whether ranking information about a request for random content is located in a preset upper rank. That is, the content corresponding to the request exists in the web server, which is the source server, and is not cached in the cache server. It is the content which has been previously requested and the ranking information based on the number of requests, . Here, although the number of requests is used as ranking information, it is not limited thereto, and other parameters can be used. This will be described later.

In order to determine a caching target based on the top ranking entry method, a request record ranking table may be additionally used in the request log table. The request record ranking table is a table in which ranking information about the number of requests for each cache key is recorded based on information of the request record table.

5 is a diagram illustrating a structure of a request record ranking table according to an embodiment of the present invention.

The request record ranking table stores the number of requests within the set time and the rank information for each cache key in association with each other. Based on the request record table, the number of requests is calculated for each cache key on the basis of the number of requests per cache key made within a set time (for example, 60 seconds or 3600 seconds) from the current time, and based on the number of requests per cache key, . If the ranking information based on the number of requests for the arbitrary cache key is within the set top rank (e.g., the third highest rank), the content corresponding to the cache key is received from the web server and delivered to the client. do.

The request record ranking table of FIG. 5 shows a state in which the cache keys are arranged based on the ranking information. If the set ranking is in the top third, the content corresponding to "http://sample.com/sample1.mp4", http://sample.com/sample2.mp4, and http://sample.com/sample3.mp4 It is determined to be a caching target and delivered to the client and stored in the storage unit of the cache server, and the contents corresponding to the remaining cache keys are delivered to the client without being cached in the cache server storage.

When the content is determined to be stored based on such a determination method, the cache server storage can be operated while maintaining a predetermined number of popular contents.

Also, as a method of determining a caching target according to an embodiment of the present invention, an upper rate entry method may be used. The upper rate entry method is a method of determining a caching object based on whether or not a request for arbitrary content is located within a preset upper rate. That is, the content corresponding to the request exists in the web server, which is the original server, and is not cached in the cache server, and it is determined whether the content has been previously requested and the corresponding cache key is included in the upper rate.

Whether or not it is included in the upper rate can be judged based on the number of cache keys or the number of requests for the cache key. For example, an upper ratio may be set based on the number of cache keys. The number of the cache keys corresponding to the setting ratio of the total number of cache keys can be set to a higher ratio irrespective of the number of requests. For example, in the request record ranking table shown in FIG. 5, there are a total of 10 cache keys. If the set upper ratio is 50%, the cache keys (http://sample.com/sample1.mp4 to http: /) corresponding to the top five of the total 10 cache keys, that is, the ranking information 1, 2, 3, 4, /sample.com/sample5.mp4) may be determined as a caching target.

In addition, an upper rate can be set based on the number of requests. The number of requests corresponding to the setting rate of the total number of requests can be set to a higher rate. For example, 50% of the total number of requests is set as the upper rate, and the content corresponding to the cache keys having the number of requests exceeding the upper rate of 50% is included in the caching target. Referring to the request record ranking table shown in FIG. 5, since the total number of requests is 226, http://sample.com/sample1. Having a cache key included in a request of more than 113 times of the upper rate corresponding to 50% of 226. mp4, and http://sample.com/sample2.mp4 are included in the caching target. (The cache key http://sample.com/sample2.mp4 is included only 13 times as part of the total 50 requests, but in the example of the present invention, it is assumed that even if only a part of the requests are included, they are included in the caching target)

As described above, the upper rate entry method is based on the request record ranking table in the same manner as the upper ranking entry method. However, unlike the upper ranking entry method, the upper 10% and the upper 30 %, It is determined that the content request based on the cache key is a caching target, and the content provided from the web server is delivered to the client and is also stored in the storage unit of the cache server.

Accordingly, the number of contents to be cached dynamically with respect to the number of contents can be adjusted, as compared with the entry method of the higher ranking, so that the number of popular contents to be cached can be increased when the total number of contents increases.

On the other hand, in the upper ranking entry method and the upper ratio entry method described above, information other than the number of requests can be used as ranking information.

As described above, the ranking information can be determined based on the number of requests per cache key. If the ranking is determined based only on the number of requests, the content may not be cached in spite of the popular content. More specifically, the use of HTTP Range GET is increasing in progressive downloading. When the ranking is calculated with the number of simple requests, a large number of files, which are required to increase the number of requests due to the partial request for files, , And small files can not be cached.

In order to prevent such a situation, ranking information may be generated by considering additional parameters other than the number of requests.

FIGS. 6 to 8 illustrate a structure of a request record ranking table based on parameters to be additionally considered.

As shown in FIG. 6, in addition to the number of requests, the content size is additionally considered, and the correction order is additionally calculated based on the correction value obtained by dividing the number of requests by the content size.

A correction value obtained by dividing the number of requests for each cache key by the file size of the content (or the size of the file to which the correction coefficient is applied) is calculated, and a correction rank based on the calculated correction values is ranked Use as information.

In addition, as shown in FIG. 7, in addition to the number of requests, the cumulative transmission amount during the set time is additionally calculated, and the correction order is additionally calculated based on the correction value obtained by dividing the number of requests by the cumulative transmission amount.

Rather than directly using the number of requests as a rank, a correction rank based on a value obtained by dividing the number of requests by a cumulative transmission amount (or a cumulative transmission amount by applying a correction coefficient) according to a file transmitted during a set time is used as ranking information do.

In addition, as shown in FIG. 8, in addition to the number of requests, a cumulative transmission amount during a content size and a setup time is additionally considered, and a correction order is additionally calculated based on a correction value obtained by dividing the number of requests by a content size and a cumulative transmission amount .

The number of requests is divided by the file size of the content (or the size of the file to which the correction coefficient is applied), and the accumulated number of requests is compared with the cumulative transfer amount (or correction The cumulative transmission amount to which the coefficient is applied), is used as ranking information. Determining a caching target based on such a correction order can minimize an error in which popular content is not selected as a caching target when a part of the image is viewed like a preview service.

The contents to be cached can be determined on the basis of the above-mentioned entry ratio or entry method as described above, while using the correction orders thus obtained as ranking information.

By determining a caching target based on the correction rank based on the number of requests and the file size, it is possible to minimize the case in which caching is not performed even in the case of popular content.

On the other hand, the caching target can be determined by combining the upper ranking entry method and the upper ratio entry method described above. For example, if a cache entry is determined to satisfy all the conditions according to the upper ranking entry method and the upper ratio entry method, or if at least one of the upper ranking entry method and the upper ratio entry method is satisfied, the entry can be determined as a caching target.

For example, if the condition is "upper 100th or higher" in the upper ranking entry method and the condition is within the "upper 30%" in the upper percentage entry method, the ranking based on the ranking information or the correction ranking based on the number of requests is 100 And within the upper 30% of the number based on the number of caches or requests, it can be determined to be a caching target.

Also, the number of requests may be used as ranking information according to the type of contents, or the correction order as described above may be used as ranking information.

In the embodiment of the present invention, among the methods for determining various caching objects as described above according to the entire range of the contents, the range of actually used contents, the size of the cache space of the cache server, and the storage space of the cache server, One or more methods may be used in combination. For convenience of explanation in FIG. 9, the request record table and the request record ranking table are collectively referred to as "attribute information table ".

9 is a flowchart of a content providing method according to an embodiment of the present invention.

As shown in FIG. 9, the cache server 100 receives a request for providing content from the client 300, that is, an HTTTP request (S100).

The cache server 100 obtains the cache key from the received HTTP request (S110), and determines whether the obtained cache key exists in the object cache key table (S120). If the cache key obtained from the HTTP request of the client does not exist in the object cache key table as a result of the determination, the HTTP request is transmitted to the web server 200, which is the original server, to request content provision (S130).

Upon receipt of a normal response (HTTP 200 or 206 response) to the content request from the Web server 200 and determining that the content exists in the Web server (S140), the cache server 100 generates a request record table And the request record ranking table to judge whether or not the conditions based on the caching conditions corresponding to the caching target, that is, the various caching object judgment methods (the N-times request method, the higher ranking entry method, the higher ratio entry method) (S150).

As a result of the determination, it is determined that the content corresponding to the cache key is a caching target, and the cache server 100 performs caching to store the content (object) corresponding to the cache key in the caching storage unit, Information about the cached contents (cache key, caching path, etc.) is additionally stored in the table (S160). Then, the cache server 100 stores information on the cached contents (cache key, request time, number of requests, etc.) in the request record table and the request record rank table (S170).

Thereafter, the cache server 100 provides the cached contents to the client 300 (S180).

If it is determined in step S120 that the cache key obtained from the HTTP request exists in the object cache key table, it is determined that the content is already cached. Thereafter, the cache server 100 stores the cache-key related information in the object cache key table (S190), stores the information in the request record table and the request record ranking table (S170), and transmits the cached contents to the client 300 (S180).

If the normal response ((HTTP 200 or 206 response) is not received from the web server 200 in step S140, the cache server 100 transmits the HTTP response of the web server to the client 300 as it is In this case, the cache server 100 may not add the cache-key-related information acquired from the client's HTTP request to the request record table / request record ranking table.

Through this process, it is possible to effectively determine whether caching is performed by effectively distinguishing popular content frequently used in content services and non-used content having a small number of times of use, and unnecessary content is cached unnecessarily, It is possible to prevent the load from increasing.

10 is a diagram illustrating a structure of a cache server according to an embodiment of the present invention.

10, the cache server 100 according to the embodiment of the present invention includes a caching storage unit 10, a cache key generation unit 20, a cache key storage unit 30, a key presence determination unit 40 And a caching target determining unit 50. The caching target determining unit 50 further includes a data requesting unit 60 and a data providing unit 70. [

The cache key generating unit 20 obtains the cache key from the HTTP request received from the client.

The cache key storage unit 30 stores the retrieved cache key related information and includes an object cache key table 31, a request record table 32, a request record ranking table 33 ). The request record table 32 and the request record ranking table 33 may be collectively referred to as an "attribute information table ".

The key presence determination unit 40 determines whether the cache key obtained from the HTTP request of the client exists in the cache key storage unit 30. Specifically, it is determined whether a cache key (or an object cache key) exists in the object cache key table 31, and if a cache key (or an attribute cache key) exists in the request record table 32 or the request record ranking table 33 And provides the determination result to the caching subject determination unit 50. [

The caching subject determination unit 50 determines whether the content corresponding to the cache key obtained from the HTTP request of the client is a caching subject. As described above, it is possible to determine whether or not the object is a caching object based on at least one of the N-times request method, the high-ranking entry method, and the high-rate entry method.

Also, the caching target determining unit 50 stores and manages the cache-key-related information about the cached contents in the object cache key table 31 or the cache-key-related information about the non-cached contents in the request recording table (32) or the request record ranking table (33).

The data requesting unit 60 transmits the HTTP request to the web server 200 and requests the data.

The caching storage unit 10 caches content determined as a caching target from the contents provided from the web server 200. [

The data providing unit 70 transmits an HTTP request to the web server 200, requests content provision, and provides the provided content to the client.

The embodiments of the present invention are not limited to the above-described apparatuses and / or methods, but may be implemented through a program for realizing functions corresponding to the configuration of the embodiment of the present invention, a recording medium on which the program is recorded And such an embodiment can be easily implemented by those skilled in the art from the description of the embodiments described above.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, It belongs to the scope of right.

Claims (18)

In a method for a cache server to cache content between a web server and a client,
Receiving a request for content from the client;
Obtaining a cache key from the request;
Wherein if the content corresponding to the request is not cached in the cache server, the cache-key-related information, i.e., the information includes the request time and the number of requests, ; And
Caching the content and providing it to the client if it is determined to be a caching target
The content caching method comprising: The method of claim 1, wherein
The step of determining whether the object is a caching object
Wherein when the request corresponding to the cache key occurs within the set time and the number of requests corresponding to the cache key is equal to or greater than the preset number, the content caching method determines that the content is a caching target. The method of claim 1, wherein
The cache-key-related information additionally includes ranking information based on the number of requests,
The step of determining whether the object is a caching object
Wherein when the request corresponding to the cache key occurs within the set time and rank information according to the number of requests corresponding to the cache key is included in the set upper rank, the content caching method determines that the content is a caching target. The method of claim 1, wherein
The cache-key-related information additionally includes ranking information based on the number of requests,
The step of determining whether the object is a caching object
Wherein a request corresponding to the cache key has occurred within a set time, and the ranking information of the cache key is a higher ratio, and the upper ratio is a number corresponding to a setting ratio of the total number of cache keys obtained so far The content is judged to be a caching subject. The method of claim 1, wherein
The cache-key-related information additionally includes ranking information based on the number of requests,
The step of determining whether the object is a caching object
Wherein a request corresponding to the cache key has occurred within a set time and the rank information of the cache key has a higher ratio and the higher ratio corresponds to a setting ratio of the total number of requests of the cache keys obtained up to now If it is included, determines that the content is a caching target. The method according to any one of claims 3 to 5, wherein
Wherein the cache-key related information further includes a correction value obtained by dividing the file size of the content, the number of requests, and the content size, and the ranking information is ranked based on the correction value. The method according to any one of claims 3 to 5, wherein
Wherein the cache-key-related information further includes a correction value obtained by dividing a file size of the content, a cumulative transfer amount of the content with respect to the set time, a number of requests divided by a content size and a cumulative transfer amount, and the rank information is based on the correction value / RTI > in a content caching system. In a method for a cache server to cache content between a web server and a client,
Receiving a request for content from the client;
Obtaining a cache key from the request;
A first determination method, a second determination method, and a third determination method for determining whether the content is a caching target based on the cache-key-related information when the content corresponding to the request is not cached in the cache server Determining whether the content is a caching target, using at least one of the content; And
Caching the content and providing it to the client if it is determined to be a caching target
/ RTI >
Wherein the cache key related information includes a request time at which the request was made, a number of requests, and ranking information. The method of claim 8, wherein
Wherein the first determination method determines that the content is a caching target when the number of requests corresponding to the cache key is equal to or greater than a preset number,
The second determination method is a method of determining that the content is a caching subject when rank information according to the number of requests corresponding to the cache key is included in a set upper rank,
The third determination method may further comprise: determining whether the ranking information of the cache key is in a higher ratio and the upper ratio is a number corresponding to a setting ratio of the total number of cache keys acquired so far, Wherein the content is a caching target when the content is included in the number of cases corresponding to the setting ratio of the total number of requests. The method of claim 9, wherein
Wherein the cache-key related information further includes a correction value obtained by dividing the file size of the content, the number of requests, and the content size, and the ranking information is ranked based on the correction value. The method of claim 9, wherein
Wherein the cache-key-related information further includes a correction value obtained by dividing a file size of the content, a cumulative transfer amount of the content with respect to the set time, a number of requests divided by a content size and a cumulative transfer amount, and the rank information is based on the correction value / RTI > in a content caching system. 12. A method according to any one of claims 8 to 11
Wherein the step of determining whether the content is a caching object determines that the content is a caching target when a request corresponding to the cache key occurs within a set time. 12. A method according to any one of claims 8 to 11
The step of determining whether or not the caching target is the caching target may include determining at least one of the first determination method, the second determination method, and the second determination method based on at least one of the entire range of the content, the range of the actually used content, Using at least one of a method and a third determination method. In a cache server that provides content between a web server and a client,
An object cache key table in which object information related to content cached from the web server is stored corresponding to a cache key, and attribute information related to a request from a client, the attribute information including a request time A cache key storage unit including a request record table and a request record rank table in which the number of requests is stored in association with a cache key;
A cache key generation unit for obtaining a key from a Hypertext Transfer Protocol (HTTP) request received from a client;
A caching object determining unit that determines whether the content corresponding to the cache key is a caching object based on the information stored in the request record table and the request record ranking table when the obtained cache key is not present in the object cache key table;
A caching storage unit for caching the content provided from the web server server when the content corresponding to the cache key is a caching target; And
A data providing unit for providing cached contents corresponding to the request to the client,
And a cache server. The method of claim 14, wherein
Wherein a request time is stored for each cache key in the request record table, and a ranking information based on the number of requests and the number of requests for each cache key is stored in the request record ranking table. The method of claim 15, wherein
Wherein the request record ranking table further includes a correction value obtained by dividing the file size of the content, the number of requests, and the content size, and the ranking information further includes a correction ranking based on the correction value. The method of claim 15, wherein
Wherein the request record ranking table further includes a correction value obtained by dividing a file size of the content, a cumulative transfer amount of the content during the set time, a request quantity divided by a content size and a cumulative transfer amount, and the rank information is based on the correction value Wherein the cache server further comprises a correction rank. The method according to any one of claims 15 to 17, wherein
The caching subject determination unit
A first determination method for determining that the content is a caching target when the number of requests corresponding to the cache key is equal to or greater than a preset number,
A second determination method for determining that the content is a caching target when rank information according to the number of requests corresponding to the cache key is included in a set upper rank,
The ratio of the ranking information of the cache key to the ratio of the total number of cache keys obtained up to the present time or the upper ratio is the ratio of the total number of requests of the cache keys acquired so far A third determination method of determining that the content is a caching target
And determines a caching target based on at least one of the plurality of cache servers.

Images