CN103416027B - The system of the method, buffer and cache optimization of cache optimization - Google Patents

Abstract

The invention provides a cache optimization method, a cache and a cache optimization system. Wherein, the cache optimization method includes: the cache node receives multiple service requests from the terminal for the first uniform resource locator URL, and respectively receives multiple first response messages from the content source based on the multiple service requests. A response message does not carry a cache control header field or the cache control header field carried indicates no caching, respectively determine the first signature values of the content contained in the multiple first response messages; the cache node compares the multiple first signature values, If they are the same, the content contained in the first response message and the first URL are cached; if not, the content contained in the first response message is not cached. The cache optimization method, cache and cache optimization system of the present invention can determine the cache content cached in the local cache device based on the signature value of the requested service content, thereby reducing bandwidth and improving terminal service experience.

Description

Cache-optimized method, cache and cache-optimized system

technical field

Embodiments of the present invention relate to the communication field, and more specifically, relate to a cache optimization method, a cache, and a cache optimization system.

Background technique

In recent years, the development of the Internet has had a huge impact on society and people's lives. The number of Internet users, types of Internet applications, and network bandwidth have all shown explosive growth. These applications bring customers a rich Internet experience, but also lead to a surge in network traffic. In order to meet the ever-increasing user needs, network operators and managers mainly adopt methods such as expanding bandwidth, controlling traffic, introducing web cache (web cache), and introducing content sources. Compared with the limited improvements brought about by bandwidth expansion, flow control, introduction of network cache, and introduction of content sources, telecom operators can also choose to deploy cache nodes in the network to cache popular content, thereby reducing bandwidth to achieve low-cost To operate and improve service quality, that is, operators actively deploy OTT (over the top) cache nodes in their networks.

Usually, the OTT cache node is deployed next to the Internet exit of the network, policy routing is deployed on the router, and the Hyper Text Transfer Protocol (HTTP, Hyper Text Transport Protocol) service is routed to the cache node. If the content requested by the terminal is not cached on the cache node, the cache node will proxy the terminal to request the content from the content source and then deliver it to the terminal.

After the OTT cache node obtains the content from the content source through the HTTP protocol, if it finds that the cache control header field carried in the HTTP response message returned by the content source indicates that the content can be cached, it will cache the content according to the cache control header field; if it finds that the content source If the returned HTTP response message does not carry the cache control header field or the cache control header field carried indicates no caching, the content will not be cached by default.

Generally speaking, service provider/content provider (SP/CP, service provider/contentprovider) is not inclined to let the operator's network cache its own content for the sake of protecting its own business and content, so in the response message It often does not carry the cache control header field by default or carries the cache control header field to indicate not to cache. Then, if the OTT cache node always decides to cache and refresh the content according to the cache control header field, the caching effect will be poor, and a large number of service requests still need to go to the content source, which will not reduce the bandwidth and improve the terminal service experience. Effect.

Or, the operator analyzes whether the content provided by the SP/CP with relatively large traffic can be cached offline, and then configures the analysis result as a policy on the OTT cache node. However, the refresh of the configuration policy is not flexible and timely enough, so it cannot quickly track business changes. Once the content source modifies the rules, its service quality may be affected.

Contents of the invention

The embodiment of the present invention provides a cache optimization method, a cache and a cache optimization system, which can avoid the problem of affecting service quality by deciding whether to cache completely according to the cache control header field in the HTTP response header.

In one aspect, a cache optimization method is provided, including: receiving multiple service requests from a terminal for a first Uniform Resource Locator (URL, Uniform Resource Locator), and respectively receiving multiple service requests from a content source based on the multiple service requests. A first response message, when none of the plurality of first response messages carries a cache control header field or the carried cache control header field indicates no caching, respectively determine the first of the content contained in the plurality of first response messages A signature value; compare multiple first signature values, if they are the same, cache the content contained in the first response message and the first URL, if not, do not cache the content contained in the first response message Content.

In another aspect, a cache is provided, including: a processing unit, configured to receive multiple service requests from a terminal for a first URL, and respectively receive multiple first response messages from a content source based on the multiple service requests, When the plurality of first response messages do not carry a cache control header field or the carried cache control header field indicates no caching, respectively determine the first signature value of the content contained in the plurality of first response messages; the comparison unit , for comparing multiple first signature values, if they are the same, the cache caches the content contained in the first response message and the first URL, if not, the cache does not cache the The content contained in the above-mentioned first response message.

In yet another aspect, a cache optimization system is provided, including: multiple caches; a service management device; an Extensible Message Processing Presence Protocol XMPP server, used to obtain the cache rules issued by the service management device and each of the The analysis result issued by the cache on whether the URL can be cached, so that the service management device can obtain the analysis result on whether the URL of the uniform resource locator issued by each cache can be cached through the XMPP server, and each The cache obtains the caching rules issued by the service management device and the analysis results of whether the URL can be cached issued by other caches through the XMPP server.

The cache optimization method, cache, and cache optimization system of the embodiments of the present invention can determine the cache content cached in the local cache device based on the signature value of the requested service content, thereby reducing bandwidth and improving terminal service experience.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only some of the present invention. Embodiments, for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

Fig. 1 is a flowchart of a cache optimization method according to an embodiment of the present invention.

FIG. 2 is a schematic structural diagram of a buffer according to an embodiment of the present invention.

FIG. 3 is a schematic structural diagram of a buffer according to another embodiment of the present invention.

FIG. 4 is a schematic structural diagram of a buffer according to yet another embodiment of the present invention.

FIG. 5 is a schematic structural diagram of a register according to yet another embodiment of the present invention.

FIG. 6 is a schematic structural diagram of a buffer according to yet another embodiment of the present invention.

FIG. 7 is a schematic structural diagram of a cache optimization system according to an embodiment of the present invention.

detailed description

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some of the embodiments of the present invention, but not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

The embodiment of the present invention provides a caching optimization method, that is, a method for actively caching content, which is simple to implement and transparent to terminals, content sources, and operators. The method of the embodiment of the present invention can automatically analyze the popular uniform resource locator (URL, Uniform Resource Locator), and judge whether the content can be cached by analyzing the response messages of multiple requests corresponding to the URL. In addition, the cached content can be identified according to the signature value of the actual content, so even when the URL changes, the ratio of the cached content can be increased, and the relatively hot content that can be cached can be cached on the cache node, thereby promoting To reduce bandwidth and improve terminal service experience. Moreover, the solution of the present invention can quickly track service changes, so that popular content can be terminated locally as soon as possible.

The cache optimization method according to the embodiment of the present invention will be specifically described below with reference to FIG. 1 .

By configuring Policy-Based Routing (PBR, Policy-Based Routing) on the router, the traffic of the user accessing the external network server is diverted to the cache node through PBR, so that the HTTP traffic is diverted from the router to the cache node, and then the cache node acts as the agent for the user to go to the external network The server downloads the content and provides it to the user. That is, the user's HTTP access request is drawn to the cache node through PBR; if the cache node does not cache the content requested by the user locally, the proxy user initiates an HTTP access request to the external network server; the external network server returns a response message to the external network server according to the HTTP access request. Cache node; the cache node returns the response message to the user.

When the cache node provides content delivery for users, for each received HTTP request, if the corresponding content is not cached locally, it needs to request the content from the content source server of the SP/CP. For the response message received from the content source server, the cache node needs to check its cache control header field. If the cache control header field carries a header field that can be cached, it can be directly cached locally on the cache node. The response message does not carry the cache control header field. domain or the cache control header field carried indicates not to cache, the cache node analyzes popular URLs to determine whether the content contained in the response message can be cached.

In Figure 1, the cache optimization method includes the following steps:

11. The caching node receives multiple service requests from the terminal for the first uniform resource locator URL, and respectively receives multiple first response messages from the content source (for example, the content source server) based on the multiple service requests, if the multiple None of the first response messages carries a cache control header field or the carried cache control header field indicates no caching, and first signature values of the contents contained in the multiple first response messages are respectively determined.

That is to say, when the terminal initiates a service request for the first URL to the cache node, and the cache node receives the first response message from the content source, if the first response message does not carry the cache control header field or the cache control header field carried If no caching is indicated, the caching node determines the first signature value of the content contained in the first response message. It can be understood that the first signature value may be determined for all or part of the content contained in the first response message. At this time, the cache node does not store the first URL and its corresponding content. If the terminal then initiates multiple service requests for the first URL to the cache node, the cache node still calculates multiple first signature values according to the corresponding content. At this point, the cache node still does not save the first URL and its corresponding content.

Usually, since the terminal initiates many service requests to the cache node, many URLs are involved. Preferably, before the caching node receives multiple service requests from the terminal for the first URL, it can first count the popularity of the first URL, and if the popularity of the first URL does not reach the threshold, the caching node does not need to consider saving the first URL For its corresponding business content, only when the popularity of the first URL exceeds the threshold and it is determined that the first URL is not statically configured and not in the blacklist, the above operation of calculating the first signature value is performed. In this way, the cache node actively analyzes the URLs with high access popularity, compares the results of multiple requests, and forces local caching if they are consistent.

It can be seen from the above that when the caching node determines multiple first signature values, it may determine whether to cache the first URL and its corresponding content with respect to the multiple first signature values of the same first URL.

12. The cache node compares the multiple first signature values, and if they are the same, caches the content contained in the first response message and the first URL; otherwise, does not cache the content contained in the first response message.

Once the caching node determines that the content corresponding to the first URL can be cached, the first URL and the content corresponding to the first URL are cached locally. When the terminal initiates a service request for the first URL again, it does not need to wait for the content source server of the SP/CP to feed back relevant content, but only needs to obtain the required content directly from the local cache device. That is to say, the caching optimization method of the embodiment of the present invention can determine the caching content cached in the local caching device based on the signature value of the requested service content, thereby reducing bandwidth and improving terminal service experience.

Specifically, for a certain URL (for example, the first URL) access request, if the response message returned by the content source server does not carry the cache control header field or the cache control header field carried indicates not to cache, the cache node will not cache the content from the URL. The content carried in the response message obtained by the content source server, but the caching node counts the popularity of the first URL in real time based on the number of visits. When the popularity of the first URL reaches the set threshold (threshold), check whether there is a statically configured caching policy for the first URL that can match, and if so, it can be processed according to the corresponding static policy. The so-called static configuration means that if you clearly know that some URLs are dynamic URLs and cannot be cached, you can configure a static cache policy for these URLs to explicitly not cache these URLs. When the caching node determines that the first URL does not have a statically configured caching strategy, it checks whether the first URL is in the blacklist that does not cache, and if it is in the blacklist, it does not carry out subsequent processing, otherwise it continues to process as follows:

When the cache node receives the service request corresponding to the first URL, the cache node still needs to obtain the content from the content source server because the corresponding content is not cached locally. In the process of obtaining content from the content source server, a signature value is generated for the content obtained this time. There are many options for generating the signature value algorithm, such as the fifth version of the message digest algorithm (MD5, Message Digest Algorithm5) or security Hash algorithm (SHA, Secure HashAlgorithm). When calculating the signature value, you can calculate the entire content returned by the content source server to generate a single signature value, or you can sample the content to generate a single or multiple signature values in order to reduce the amount of calculation, for example, only use the first 16KB (Kbyte) of the returned content The signature value is calculated for the content, or the signature value is calculated separately for the first 16KB and the last 16KB. The calculated signature value is cached as a content attribute obtained from the content source server. At this time, the content obtained from the content source server still does not need to be saved locally. Later, when the cache node receives a service request corresponding to the first URL, the cache node still needs to obtain the content from the content source server because the corresponding content is not cached locally. In the process of obtaining content from the content source server, the above-mentioned algorithm is used to calculate the signature value, and the signature value calculated this time is compared with the previously calculated signature value. If the comparison results of the signature values of the content downloaded from the content source server for multiple consecutive times (for example, 2 or 3 times) are consistent, it is considered that the content corresponding to the first URL can be cached, that is, the content obtained from the content source server at this time The content of the first URL can be stored locally, and the service can be provided directly by using the content cached locally when a service request for the first URL is received later. If the signature value results are inconsistent, for example, the signature values calculated twice in a row are inconsistent, indicating that there are differences in the content obtained from the content source server each time, so the content of the first URL cannot be cached locally, and the first URL needs to enter Add it to the blacklist that does not cache or reduce the popularity statistics value of the first URL, so as to avoid subsequent judgment processing whether it can be cached.

In order to further optimize the above caching method, a TTL (Time To Live) can be set for the content contained in the cached first response message, so that when the TTL expires, the content contained in the cached first response message will be forcibly deleted. Content. Specifically, different TTL values are set for locally cached content. When the TTL expires, the content in the local cache is forcibly deleted, and when a new service request is received, the content is requested from the content source server again. In this way, the low-probability event that the signature value based on partial content technology is still consistent with a small change in the actual content can be avoided, thereby ensuring that the cached content is consistent with the content on the content source server.

Wherein, setting the TTL may be based on the following principles. According to different domain names: For example, for domain names that mainly provide video content, the frequency of content changes is low, so a longer TTL can be set; for domain names that mainly provide information, the frequency of content changes is high, so set TTL is relatively short. Set according to the extension of the requested content: different extensions actually correspond to different content types, so different TTLs can be set. Of course, the domain name and extension can be set together: that is, for different domain names, different TTL values can be set for the content of the same extension.

When using locally cached content to provide services, continue to send requests carrying the "If-Modified-Since" header field or "If-None-Match" header field to the content source server, Allow the content source server to record user access logs, and at the same time help to ensure timely refresh of content.

Because in some scenarios, the SP/CP needs to see the original user's request to collect the user's access log. At this time, the cache node can simulate the terminal to initiate a service request to the content source server, so that the content source server can use the requested Variable entity value information to check whether the content in the cache has changed.

For example, the If-Modified-Since header field carries the time information of the cached content generation, and the content source server can judge whether the cached content has been refreshed based on this information; or the If-None-Match header field carries the entity value generated by the cached content (Etag) signature information, the content source server can judge whether the cached content has been refreshed according to the signature information.

Specifically, if the HTTP download (HTTP Get) request message sent by the cache node carries the If-Modified-Since header field or If-None-Match header field, the content source server can directly Time information or the Etag signature information of the requested variable carried in the If-None-Match header field to check whether the content has changed. If there is no change, you can directly reply with a "304: not modified (not modified)" response message, and the response message does not need to carry actual data, so the bandwidth can also be reduced.

According to the cache optimization method shown in FIG. 1 , once the cache node determines that the content corresponding to the first URL can be cached, the first URL and the content corresponding to the first URL are cached locally. When the terminal initiates a service request for the first URL again, it does not need to wait for the content source server of the SP/CP to feed back relevant content, but only needs to obtain the required content directly from the local cache device.

However, when deploying actual services, in order to protect their own services and content, the SP/CP will not carry the cache control header field in the response message by default or carry the cache control header field to indicate no caching. The URL of the content, that is, the SP/CP publishes different URLs to different users for the same content. Judging from the requests received by the cache nodes, the URLs of each request are different. If you only look up the cached content based on the URL, it is basically a local miss.

In view of the above situation, the signature value can still be used to implement active caching, thereby reducing bandwidth and improving terminal service experience. The detailed implementation process is as follows.

First, after the cache node obtains the content from the content source server, it calculates the signature value of some content at the same time, for example, calculates the signature value of the first 16KB content and the signature value of the last 16KB content, and the calculated signature value and content are stored locally. The corresponding relationship between the signature value of the first 16KB content and the content, that is, not only the cached content can be indexed according to the URL, but also the cached content can be indexed according to the signature value.

When the cache node receives a new access request corresponding to the second URL, it will check whether there is locally cached content corresponding to the requested second URL according to the second URL, and if so, it can provide services based on the cached content. If not, first request the first 16KB of content from the content source server. The request for the first 16KB of content can be achieved by carrying the Range (Range) header field in the HTTP Get request message to indicate the request range, for example: Range:bytes=0-16383.

After the cache node receives the first 16KB of content, it calculates the signature value for the 16KB of content, and uses the calculated signature value as an index to search for the content of the local cache. If no matching result is found, it means that the requested content is not cached locally. Therefore, it is necessary to continue to request the remaining content from the content source server and deliver it to the terminal. The request for the remaining content can be realized by carrying the Range header field in the HTTP Get request message to indicate the request range, for example: Range:bytes=16384-. In the process of requesting content from the content source server, the signature value of the last 16KB content is calculated and the requested content and corresponding signature value are cached locally.

If the signature value of the locally cached content is found to be the same as the signature value of the first 16KB content calculated this time, it means that the locally cached content may be the content of this service request. In order to confirm that further verification and verification can be done, the cache node requests the last 16KB of content from the content source server. This can also be achieved by carrying the Range header field in the HTTP Get request message to indicate the request range, for example: Range:bytes= -16384. After the cache node receives the content of the last 16KB, the signature value is also calculated for the content of the last 16KB, and the calculated signature value is compared with the signature value of the last 16KB of the local cache content previously indexed based on the signature value of the first 16KB content. Compare. If they are consistent, it means that the content in the local cache can be used to provide services for end users. If not, it means that the requested content is not cached locally, so it is necessary to continue to request the remaining content from the content source server and deliver it to the terminal. The content of can be realized by carrying the Range header field in the HTTP Get request message to indicate the request range, for example: Range:bytes=16384-.

It can be seen from the above description that in addition to marking the cached content according to the URL of the original request, the content can also be marked according to the signature value of the content. When processing according to this solution, for hot content, even if the requested URL is different, after the content is identified according to the signature value, the locally cached content can still be used to provide services.

In practical applications, in order to improve performance, the generation and verification of the signature value corresponding to the last 16KB content can also be omitted, that is, the content is only identified according to the signature value of the previous 16KB content. Of course, the actual content used to calculate the signature value can be changed in many ways, such as dividing the original file into pieces, extracting some bytes from each piece and combining them together to calculate the signature value.

To sum up, optionally, in addition to caching the content contained in the first response message and the first URL, the caching node establishes and caches the correspondence between the content contained in the cached first response message and the first signature value relation. Therefore, when the caching node receives the terminal's service request for the second ULR, if the second URL is the same as the cached first URL, it sends the cached first URL corresponding to the first URL to the terminal. otherwise, receive a second response message from the content source (server) based on the service request for the second URL and the correspondence between the content contained in the cached first response message and the first signature value, and A second signature value of the content contained in the second response message is determined. The cache node compares the second signature value with the first signature value, and if they are the same, sends the content contained in the cached first response message to the terminal, otherwise sends the content contained in the second response message received from the content source (server) The entire content of the content is sent to the terminal.

A buffer according to an embodiment of the present invention is shown in FIG. 2 . In FIG. 2 , the buffer 20 includes a processing unit 21 and a comparing unit 22 . Wherein, the processing unit 21 is configured to receive multiple service requests from the terminal for the first URL, and respectively receive multiple first response messages from the content source based on the multiple service requests, and when all of the multiple first response messages are The first signature values of the content contained in the plurality of first response messages are respectively determined by not carrying the cache control header field or carrying the cache control header field indicating no caching. For example, the processing unit 21 may determine the first signature value according to part of the content contained in the first response message; or may determine the first signature value according to all the content contained in the first response message. The comparison unit 22 is used to compare multiple first signature values, if they are the same, the cache caches the content contained in the first response message and the first URL, otherwise the cache does not cache the Content contained in the first response message.

Therefore, the cache in the embodiment of the present invention can determine the cache content cached in the local cache device based on the signature value of the requested service content, thereby reducing bandwidth and improving terminal service experience.

A buffer according to another embodiment of the present invention is shown in FIG. 3 . In FIG. 3 , in addition to the processing unit 21 and the comparison unit 22 , the buffer 30 also includes a statistics unit 23 and a determination unit 24 . Wherein, the statistical unit 23 is used for counting popularity of the URL. The determining unit 24 is configured to determine that the URL is not statically configured and is not in the blacklist when the popularity of the URL exceeds a threshold.

A buffer according to yet another embodiment of the present invention is shown in FIG. 4 . In FIG. 4 , besides the processing unit 21 , the comparison unit 22 , the statistics unit 23 and the determination unit 24 , the buffer 40 also includes a setting unit 25 . The setting unit 25 is configured to set a time-to-live TTL for the content contained in the cached first response message, so that when the TTL expires, the content contained in the cached first response message is forcibly deleted.

A buffer according to yet another embodiment of the present invention is shown in FIG. 5 . In FIG. 5 , besides the processing unit 21 , the comparing unit 22 , the statistical unit 23 , the determining unit 24 and the setting unit 25 , the buffer 50 also includes an analog unit 26 . The simulation unit 26 is used to simulate a terminal to initiate a service request to the content source, so that the content source can check whether the content has changed according to the entity value information of the requested variable carried in the service request.

A buffer according to yet another embodiment of the present invention is shown in FIG. 6 . In Fig. 6, in addition to the processing unit 21, the comparison unit 22, the statistics unit 23, the determination unit 24, the setting unit 25 and the simulation unit 26, the buffer 60 also includes the establishment unit 27, which is used to establish the cached first A correspondence between content contained in a response message and the first signature value. Therefore, the processing unit 21 is further configured to receive a service request from the terminal for the second ULR, and if the second URL is the same as the cached first URL, send the cached first URL corresponding to the first URL to the terminal. A content contained in a response message, otherwise, receiving a second response message from the content source based on the service request for the second URL and the corresponding relationship, and determining a second signature value of the content contained in the second response message. The comparison unit 22 is further configured to compare the second signature value with the first signature value, and if they are the same, the buffer sends the content contained in the cached first response message to the terminal, otherwise the The cache sends all the content contained in the second response message received from the content source to the terminal.

To sum up, the cache in the embodiment of the present invention can track changes in popularity of content in real time, and cache content that is hot and can actually be cached locally as much as possible, thereby reducing bandwidth and improving terminal service experience. In addition, when the cache in this embodiment of the present invention provides services with locally cached content, it continues to send requests carrying If-Modified-Since header fields or If-None-Match header fields to the content source server as needed, and the content source server You can continue to keep records of user access logs, but you don't need to actually return the content, so the performance of the content source server is also improved.

FIG. 7 shows a cache optimization system according to an embodiment of the present invention. The analysis results of whether the URL can be cached are shared in real time among multiple cache nodes, that is, the cache policy can be shared across the entire network, thereby avoiding repeated calculations of multiple cache nodes, allowing cacheable content to be cached locally as soon as possible, thereby improving the overall The performance of the caching system.

For example, as shown in FIG. 7 , a cache optimization system 70 according to an embodiment of the present invention includes multiple caches 71 , a service management device 72 and an Extensible Messaging and Presence Protocol (XMPP, The Extensible Messaging and Presence Protocol) server 73 . Wherein, the plurality of registers 71 may be registers as shown in FIG. 2 to FIG. 6 . The XMPP server 73 can obtain the caching rules issued by the service management device 72 and the analysis result of whether the URL issued by each cache 71 can be cached, so that the service management device 72 can learn the URL issued by each cache 71 through the XMPP server 73 The analysis result of whether the URL can be cached, and each cache 71 obtains the caching rules issued by the service management device 72 and the analysis results of whether the URL can be cached issued by other caches through the XMPP server 73 . Therefore, the caching optimization system in the embodiment of the present invention can determine the caching content cached in the local caching device based on the signature value of the requested service content, thereby reducing bandwidth and improving terminal service experience.

In practice, the overall cache performance can be optimized by sharing the analysis results of each cache node (eg cache 71 ). For example, publishing and sharing of cached analysis results is implemented based on the publish/subscribe model of the XMPP protocol. Specifically, the service management device 72 can act as a publisher and publish known cache rules to the XMPP server 73 according to the configuration; each cache node (for example, cache 71) can also serve as a publisher and publish the known cache rules to the XMPP server 73 in real time. The caching node analyzes the results of whether the URL can be cached; the service management device 72 also serves as a subscriber, and subscribes to the XMPP server 73 to analyze the results of whether the URL can be cached in real time issued by other caching nodes. Hierarchical analysis and induction can finally form static rules and configure them on all cache nodes; each cache node (for example, cache 71) also acts as a subscriber, and sends the subscription service management device 72 to the XMPP server 73 It also subscribes to the analysis results published by other cache nodes on whether the URL can be cached. For example, if a cache node (for example, cache 71) receives a certain URL from other cache nodes that can be cached and the local site is currently not cacheable, it can be directly cached locally after the heat reaches the threshold without calculating the checksum. whether it is consistent; if a cache node (for example, cache 71) receives from other cache nodes that a certain URL cannot be cached, then directly put the URL into the blacklist that cannot be cached. By sharing the analysis results among multiple cache nodes, the operation of checking and comparing in the entire network can be reduced, thereby improving the performance of the entire system.

Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present invention.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk, and other media that can store program codes. .

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (13)

1. a kind of method of cache optimization, it is characterised in that including：

Count the temperature of the first uniform resource position mark URL；

If the temperature of a URL exceeds threshold value, determine whether whether a URL is statically configured and in black name Dan Zhong；

When the temperature of a URL exceeds threshold value, and determine that a URL is not statically configured and not in blacklist When middle, receiving terminal to multiple service requests of first uniform resource position mark URL, and based on the multiple service request Multiple first response messages are received respectively from content source, when not carrying buffer control header field in the multiple first response message Or the buffer control header field for carrying indicates not cache, the of the content for determining to be included in the multiple first response message respectively One signature value；

Compare multiple first signature values, if identical, cache the content and institute included in first response message A URL is stated, if it is not the same, not caching the content included in first response message.

2. method according to claim 1, it is characterised in that described to determine to be wrapped in the multiple first response message respectively First signature value of the content for containing includes：

Determine the first signature value of the partial content of the content included in first response message；Or

Determine the first signature value of the full content of the content included in first response message.

3. method according to claim 1, it is characterised in that in being included in caching first response message After appearance, also include：

Be the curriculum offering life span TTL included in the first response message of the caching, so as to when the TTL time-out when, The content included in the first response message cached described in Force Deletion.

4. according to the method in any one of claims 1 to 3, it is characterised in that also include：

Pseudo-terminal to the content source initiating business request, so that the content source is according to the quilt carried in the service request Ask whether the content of the entity value information inspection caching of variable there occurs change.

5. method according to claim 4, it is characterised in that also include：

Corresponding relation between the content included in the first response message for setting up the caching and the first signature value.

6. method according to claim 5, it is characterised in that also include：

Receiving terminal is to the service request of the 2nd URL, if the 2nd URL is identical with a URL of caching, to institute Terminal transmission is stated corresponding to the content included in the first response message of the caching of a URL, otherwise, based on to institute The service request and the corresponding relation for stating the 2nd URL receive the second response message from the content source, determine described second Second signature value of the content included in response message；

Compare the second signature value and the first signature value, if identical, by the first response message of the caching Comprising content be sent to the terminal, if it is not the same, including in the second response message that will be received from the content source The full content of content is sent to the terminal.

7. a kind of buffer, it is characterised in that including：

Statistic unit, the temperature for counting the first uniform resource position mark URL；

Determining unit, if exceeding threshold value for the temperature of a URL, determines whether a URL is statically configured And whether in blacklist；

Processing unit, exceeds threshold value, and determine that a URL is not statically configured for the temperature as a URL And when not in blacklist, receiving terminal to multiple service requests of first uniform resource position mark URL, and based on institute State multiple service requests and receive multiple first response messages respectively from content source, do not taken when in the multiple first response message Indicate not cache with buffer control header field or the buffer control header field of carrying, in determining the multiple first response message respectively Comprising content the first signature value；

Comparing unit, for comparing multiple first signature values, if identical, the first response described in the buffer The content included in message and a URL, if it is not the same, during the buffer does not cache first response message Comprising content.

8. buffer according to claim 7, it is characterised in that the processing unit specifically for：

Determine the first signature value of the partial content of the content included in first response message；Or

Determine the first signature value of the full content of the content included in first response message.

9. buffer according to claim 7, it is characterised in that also including setting unit, for for the caching The curriculum offering life span TTL included in one response message, when the TTL is overtime, to be cached described in Force Deletion The content included in first response message.

10. the buffer according to any one of claim 7 to 9, it is characterised in that also include：

Analogue unit, for pseudo-terminal to the content source initiating business request, so that the content source is according to the business Whether the content of the entity value information inspection caching of the requested variable carried in request there occurs change.

11. buffers according to claim 10, it is characterised in that also include：

Unit is set up, between the content included in the first response message for setting up the caching and the first signature value Corresponding relation.

12. buffers according to claim 11, it is characterised in that

The processing unit is further used for service request of the receiving terminal to the 2nd URL, if the 2nd URL and caching First URL is identical, then bag in the first response message of the caching for corresponding to a URL is sent to the terminal The content for containing, otherwise, second is received based on the service request and the corresponding relation to the 2nd URL from the content source Response message, determines the second signature value of content included in second response message；

The comparing unit is further used for the second signature value described in comparing and the first signature value, described if identical The content included in first response message of the caching is sent to the terminal by buffer, if it is not the same, the caching The full content of the content included in the second response message that device will be received from the content source is sent to the terminal.

A kind of 13. systems of cache optimization, it is characterised in that including：

Multiple buffers as any one of claim 7 to 12；

Service management device；

Scalable message processes Presence Protocol XMPP server, for obtain the caching rule of service management device issue with And each described buffer issue to uniform resource position mark URL whether the analysis result that can be cached, so as to the business Managing device by the XMPP server know that each described buffer issues whether can be with to uniform resource position mark URL The analysis result of caching, and each described buffer knows what the service management device was issued by the XMPP server Caching rule and other buffers issue to the URL whether the analysis result that can be cached.