WO2009144688A2 - Système, procédé et dispositif de mise en mémoire cache locale de données - Google Patents

Système, procédé et dispositif de mise en mémoire cache locale de données Download PDF

Info

Publication number
WO2009144688A2
WO2009144688A2 PCT/IB2009/053527 IB2009053527W WO2009144688A2 WO 2009144688 A2 WO2009144688 A2 WO 2009144688A2 IB 2009053527 W IB2009053527 W IB 2009053527W WO 2009144688 A2 WO2009144688 A2 WO 2009144688A2
Authority
WO
WIPO (PCT)
Prior art keywords
data
stored
access
peer
user
Prior art date
Application number
PCT/IB2009/053527
Other languages
English (en)
Other versions
WO2009144688A3 (fr
Inventor
Satya Mallya
Georges Nahon
Original Assignee
France Telecom
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by France Telecom filed Critical France Telecom
Publication of WO2009144688A2 publication Critical patent/WO2009144688A2/fr
Publication of WO2009144688A3 publication Critical patent/WO2009144688A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/289—Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5681—Pre-fetching or pre-delivering data based on network characteristics
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/288—Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles

Definitions

  • the present system relates to a system, method and device for locally caching data that utilizes one or more aspects of user interaction, attention and affinity to content to determine caching rules.
  • BACKGROUND OF THE PRESENT SYSTEM In interacting with data over a network such as the Internet, numerous delays are introduced by the network between the time when a request for data is made and an end of the delivery of the data to the requesting device. For example, in a Web based application, the performance a user experiences is dependent on elements such as network speed, load, Internet server load, client side memory, processor speed, proxies and browser limitations that may limit active connections, data transfer size, etc.
  • this information is either retrieved directly from the original server, from a browser cache on a local hard drive or from a nearby cache server.
  • a peer to peer approach may be utilized to reduce server overload by accessing data from one or more peers that duplicate data that may otherwise be available from a server. By providing multiple sources for data in a form of peers, loads on servers is greatly reduced, yet other bottlenecks in accessing data still exist.
  • Computer systems interacting with data often utilize local cache memory for maintaining portions of the content to facilitate quick interaction. This is particularly true when the content is being accessed over a network wherein limitations in transfer speed between a location where the content is provided and the location where the content is accessed, often cause delays in the interaction.
  • effective use of local caching of data requires rules that control what data is cached and for how long the data is cached. For example, a web 2.0 page that does not have an appropriate cache directive in an AJAX environment will have poor performance particularly when there are multiple AJAX calls, network latency (e.g., related to transatlantic hop) and proxies.
  • Existing caching rules are typically statistically based and are based on object sizes and retrieval latencies.
  • U.S. Patent No. 7,039,683 (“the '683 patent'), incorporated herein as if set out in its entirety, utilizes a collective system including anticipating requests for data and frequency or volume of access requests from a plurality of users to ameliorate a volume of transfers.
  • the data may in theory be provided in response to two or more requests reducing the volume of transfer by the number of times the data is transferred locally.
  • anticipating requests may be based on past requests for information, popularity of the subject matter, and direct feedback by access requestors regarding interest in data
  • the '683 patent fails to appreciate other characteristics of usage and therefore results in additional transfers of data due to local storage of data that may be of no current interest to a user.
  • the present system includes a system, method, processor and client device for controlling local caching of data available from a remote server.
  • Data sources are identified that are repetitively accessed including a time and frequency of data access.
  • a rate of updating the data source at the remote server is determined and the data from the data source is retrieved and stored in a local cache based on the identified time and frequency of data access and the determined rate of updating the data source.
  • a proxy may receive a request for data, make a determination if the data corresponds to data stored in the local cache, retrieve the data from the local cache if it is determined that the data is stored in the local cache and retrieve the data from the remote server if it is determined that the data is not stored in the local cache.
  • the rate of updating the data source at the remote server may be determined by periodically comparing a stored signature of a data page with a current data page retrieved from the remote server.
  • changes in the data that occur at times that do not correspond to the identified time and frequency of data access may not be downloaded.
  • Retrieving additional data may be based on an analysis of top level and lower level link data related to the data and based on user affinity to the additional data.
  • the time of data access may include a time of day and a day of week of the data access.
  • User interactions with an application utilized to access remote servers may be analyzed to determine and store usage characteristics in a user log.
  • User interactions with the application utilized to access remote servers may be analyzed to determine at least one of a user's affinity to the data and user attention to the data.
  • a device in accordance with the present system may be arranged in a peer to peer configuration to distribute the stored data to a peer device that has an affinity to the stored data.
  • the stored data may be distributed to peer devices based on an identified time and frequency of data access that is associated with the peer device.
  • the stored data may be distributed to the peer device in response to a request from the peer device for the stored data or it may be pushed by the present device to the peer device.
  • FIG. 1 shows a system in accordance with an embodiment of the present system
  • FIG. 2 shows a portion of a system in accordance with an embodiment of the present system
  • FIG. 3 shows a portion of a system in accordance with an embodiment of the present system.
  • FIG. 4 shows a process flow diagram in accordance with an embodiment of the present system.
  • the term data and formatives thereof as utilized herein should be understood to relate to any type of data that may be accessed by a user including textual data, audio data, visual data, audio/visual data, link data, application data, etc., for rendering and/or operation thereof.
  • the term "operatively coupled" and formatives thereof as utilized herein refer to a connection between devices or portions thereof that enables operation in accordance with the present system.
  • an operative coupling may include one or more of a wired connection and/or a wireless connection between two or more devices that enables a one and/or two-way communication path between the devices or portions thereof.
  • FIG. 1 shows a system 100, one or more portions of which may be utilized for operation in accordance with the present system.
  • the present system 100 provides a mechanism that considers user interaction, attention and affinity to types of data when caching and prefetching web data of a particular content service locally on a user's device.
  • the present system enhances user experience in terms of content access (browser or application based) and makes offline content accessible to a user that is highly relevant in both of a fixed and mobile network connection.
  • portions shown appear as individual portions, it may be readily appreciated that each of these portions may be comprised of hardware and/or software portions including memory storage portions that store instructions for configuring a processor 110 for operation in accordance with the present system.
  • the present system 100 is illustratively shown as discrete operating portions, as is readily appreciated, these discrete operating portions are merely provided to facilitate the following discussion and should not be understood to require corresponding physically discrete portions of the system.
  • the portions of the system 100 may be readily implemented as one or more programming portions that configure the system 100 for operation as described herein.
  • the processor 110 may be operationally coupled to a memory, such as represented by one or more of portions 120, 130, 145, 150, 155, 160, 165, 170, 175, 180.
  • the one or more memories may be any type of device for storing application data as well as other data related to the described operation.
  • the application data and other data are received by the processor 110 for configuring the processor 110 to perform operation acts in accordance with the present system.
  • the present system may be embodied as a computer software program, such program containing modules corresponding to one or more of the individual steps, acts and/or portions described and/or envisioned by the present system.
  • the operation acts may include operation in accordance with one or more of the portions 120, 130, 145, 150, 155, 160, 165, 170, 175, 180.
  • the processor 110 may operate utilizing a program portion, multiple program segments, and/or may be a hardware device utilizing a dedicated or multi-purpose integrated circuit.
  • the system 100 for example may be readily implemented on a properly configured general use personal computer.
  • the system 100 may be provided as a locally operated system as opposed to a centrally-based server system or central caching system as disclosed in prior systems.
  • the present system is directed to facilitating local access to cached data in place of accessing data from a remote location. It has been observed that often times, users have repetitive and habitual behavior (e.g., time of day usage) when it comes to accessing of data from a network.
  • a user typically accessing data over a remote network does not make requests for data directly, but in fact enters and/or selects URL's that direct an application, such as a web-browser, to a remote server data location wherein the data is available for download or streaming so that the data may be retrieved and/or consumed by the user.
  • URL's may point to default locations for data, such as a home page, as opposed to a URL solely associated with given data. In this way, default URL's may be utilized to facilitate a review and retrieval of data that currently is accessible from the default URL.
  • a URL associated with nyt.com may be utilized to facilitate accessing data that currently is available from a data server associated with the default URL, although the data provided by the data server may change at any time.
  • default URL's users are provided a reliable means of accessing data that is available from the default URL, regardless of the particular data provided by the data server. This is consistent with how users typically browse data available from a remote server, such as through the Internet. For example, a user may have a habit of browsing the home page of the New York Times TM every week day, at a beginning of a work day, yet the user has no expectation of what data will be provided by the New York Times data server.
  • a web based proxy 120 operatively coupled to the processor 110 acts as an internal service for intercepting calls from a user application, such as the browser application.
  • the calls are typically requests for data from an external network 135, such as may be provided in response to entrance of a Uniform Resource Locator (URL) into a browser address bar and/or as may be provided by selection of a URL provided on a web page, such as an XML and/or HTML based web page.
  • the web based proxy 120 may utilize an interceptor pattern to identify and intercept all or pre-configured data identifiers related to data requests which are either directed to a remote destination server or are directed to a retrieval service under control of the processor 110. Interceptor patterns that are known in the art, such as may be utilized by a local anti- phishing program, may be readily employed by the web based proxy 120 in accordance with an embodiment of the present system.
  • data analysis is performed, such as analysis of related URL's, pages, media, content blocks and links, by a data analysis portion 150 to determine a portion of caching rules for the user.
  • the data analysis portion 150 may utilize caching rules to determine data refresh rates and/or server update rates. As may be readily appreciated, many systems are available that may help determine whether data at a remote server is updated.
  • Web pages may be directly compared (e.g., bit-by-bit comparison, title analysis, data size may be compared, presence of new links may be identified, Really Simple Syndication (RSS) feed metadata may be analyzed, for example ignoring potential changes that may occur to advertising content and focusing on changes to the underlying data.
  • RSS Really Simple Syndication
  • the present system e.g., the data analysis portion 150
  • the data analysis portion may determine that data present at NYT.com changes more frequently than data present at sjmercurynews.com based on data signatures of data pages from the remote servers (e.g., NYT.com server and sjmercurynews.com server) that are stored locally and that are compared (e.g., periodically) with data pages currently retrieved from the remote servers.
  • a time pattern of data changes may be used to assist in a determination of a portion of enhanced caching and prefetch rules 175 to assist in a determination of when data should be pulled from a given remote data server.
  • the present system determines a portion of the enhanced caching and prefetch rules 175 (e.g., to determine whether cached data should be updated) to ensure that when desired, the locally cached data 140 currently reflects data stored on the data servers. It is important to note that at times, it is desirable that locally stored content does not reflect the content stored on a remote server to help ensure that unnecessary local caching of content is minimized unlike prior systems.
  • an affinity analysis portion 155 performs an analysis of user interaction patterns with a web application, such as a browser, including data accessed and locations of data access (e.g., domain, etc.) .
  • Click stream analysis may be performed to identify links that are accessed, data that is consumed, and a time and periodicity of data consumption to determine what data to prefetch and cache and a frequency of such prefetching and caching. This analysis may be performed on a log of user interactions and/or may be performed substantially real-time as the user interaction occurs.
  • the log of user interaction may be examined to determine user interaction characteristics such as periodicity of accessing the data including a time of typical interaction, days of week, months, etc., when content is accessed including whether given data locations are repetitively accessed.
  • user interaction with data that is not repeated may be discarded as a fleeting interest not resulting in prefetching of data.
  • prefetching and caching of data may be timed to precede a request by the user to access the data while enabling the present system to ignore changes in the data that occur between access requests .
  • a user may access a default URL (a home page) of a given website every morning at 9 A.M.
  • the user may not access the given website during week-ends and holidays.
  • changes in the data available from the website that occur over the weekend or holiday may be ignored as long as a prefetching of new data is performed prior to when the website is again accessed by the user.
  • the affinity analysis portion 155 may include an analysis of user attention to data, for example, by monitoring the activity of user's clicking on hyper links or other menus on the website and/or how long a user dwells on given web pages. Affinity is measured by user's explicit or implicit interaction with data sites.
  • An explicit example of a user's affinity for content may include monitoring a user's clicks on "WiMAX" in a search application, such a content aggregator as available at bubbletop.com or pageflakes.com and/or RSS feeds added by a user that have metadata including WiMAX.
  • Another explicit example of a user's affinity for content may be related to a high frequency of WiMAX and related content access by a user.
  • Dwell time may also serve as an indicator of user's attention. For example, user dwell time may be utilized to determine whether minor updates (e.g., changes in less than 5% or 10% of the data) should result in prefetching in updated data.
  • the percentage of change that results in a prefetching of new data in accordance with the present system may go down, to reflect the realization that the longer that data is scrutinized by the user, the more important the data is to the user and the more important that changes in the data be accurately reflected in the cached data. For example, for data that is viewed by the user for a period of one minute, a five percent change in the data may be acceptable before the present system determines that the new data is ready for prefetching. However, for data that the user typically views for less than 30 seconds, a 10% change in the data may be acceptable before any detected new data is prefetched.
  • an enhanced caching and prefetching portion 175 utilizes the affinity and content analysis portions 150, 155 in connection with other caching techniques to determine which data to prefetch and cache.
  • the enhanced caching and prefetching portion 175 may determine which data is static (e.g., data associated with a given link that does not change) and which data is dynamic (e.g., data and/or link data that does change) .
  • Given data that is archived in data server may have an associated URL that does not change and thereby may be determined to be static data.
  • analysis related to static data may be eliminated or minimized since the static data need only be prefetched and cached once irrespective of user affinity.
  • the enhanced caching and prefetching portion 175 may also set expiration rules for cached data determining, for example, one or more of when: - cached data may be overwritten and may include a time of the day when data is typically accessed, periodicity of access to particular portions of the data and the web application, may also include a specific user directive to the system including rules for prefetch and cache duration, directives from the peer to peer management portion 180 where content change frequency may be detected from peers that influence a given user's cache and prefetch rules, directives from the peer to peer management portion 180 which indicate that users with similar interest often prefetch and cache given content, and other user behavior such as to determine the prefetching and caching rules utilized by the system
  • the present system may make a qualified estimate on the client device (e.g., system 100) to determine if the content from a target web data/application needs to be prefetched taking into account usage behavior and web site content change frequency. In this way, prefetching of content that is not updated or not of current interest to the user may be avoided unlike prior systems.
  • the enhanced caching and prefetching portion 175 also may operate with one or more other common caching techniques to manage the size of the cached data 140.
  • LRU least recently used data items
  • MRU Most Recently Used
  • This caching mechanism may be used when data access is unpredictable by the affinity analysis portion 155, and when determining the least most recently used section of the cache system may require long and complex operations.
  • Typical database memory caches may employ the MRU to simplify caching operation and the system 100 may similarly employ the MRU algorithm.
  • a Pseudo-LRU (PLRU) algorithm may be employed for cached data items that have a large associativity
  • the PLRU algorithm may be utilized by the enhanced caching and prefetching portion 175 only requiring one bit per cache data item to operate as may be readily appreciated.
  • the enhanced caching and prefetching portion 175 may utilize a Least Frequently Used (LFU) algorithm that counts how often a data item is accessed by the user. Those data items that are used least often, may be discarded first. Further, the enhanced caching and prefetching portion 175 may utilize an Adaptive Replacement Cache
  • a cache control portion 145 is operably coupled between the processor 110 and cached data 140.
  • the cached data 140 is stored in a memory device that is local to the system 100 such that cached data 140 may be accessible to the user of the system 100 regardless of whether the system 100 is (currently) connected to the network 135.
  • the cache control portion 145 operates in response to instructions from the processor 110 to refresh cached content and prefetch content not previously cached.
  • the cache control operates to establish a connection with the network 135 to retrieve and store fresh data, in accordance with prefetch and cache rules stored in the enhanced caching and prefetching portion 175.
  • a storage and retrieval service portion 160 is operably coupled to the cache control 145 and controls prefetching and caching of data from web applications including caching of data associated with top-level links (URLs provided that directly link to data) and depth based link data retrieval (URLs provided together with data accessible from a top-level link and/or lower link data) . Further, links analysis may be performed together with an analysis of a user's affinity to the data accessible from the top-level link and/or lower link data to determine if the data accessible from the top-level link and/or lower link data should be locally cached.
  • top-level links URLs provided that directly link to data
  • depth based link data retrieval URLs provided together with data accessible from a top-level link and/or lower link data
  • the storage and retrieval service portion 160 may utilize an authentication and security portion 165 to enable access to the data without requiring user intervention in the prefetching process.
  • the user may be enabled through use of the authentication and security portion 165, to enter security information to make the security information available for use by the system 100 for prefetching of data that requires security and authentication information.
  • the web based proxy 120 redirects all content requests to the storage and retrieval service portion 160.
  • the storage and retrieval service portion 160 determines whether requested data (e.g., data associated with a URL that is provided in the web browser address bar) is available as cached data 140. In a case wherein the requested data is available as cached data 140, the cached data 140 is provided to the web browser for rendering. In a case wherein the requested data is not available as cached data 140, the storage and retrieval service portion 160 enables access to the network 135 for retrieval of the requested data and rendering by the web browser. In a case wherein the requested data is not available as cached data, the storage and retrieval service portion 160 may utilize the authentication and security portion 165 to access data that requires authentication for access, or the authentication and security portion 165 may enable prompting of the user for the authentication information.
  • requested data e.g., data associated with a URL that is provided in the web browser address bar
  • the storage and retrieval service portion 160 enables access to the network 135 for retrieval
  • the storage and retrieval service portion 160 in one embodiment may control portions of the system in an offline mode (e.g., when the network 135 is not available) to operate together with the web-based proxy portion 120 as a companion application to control access to cached data 140 and to record application commands from other portions of the system 100, such as the data analysis portion 150 and the affinity analysis portion 155, to enable continued operation when the user again connects to online applications through the network 135. Further, the storage and retrieval service portion 160 disables real-time command applications, such as a request from the cache control portion 145 to prefetch data, when the system 100 is in offline mode (e.g., when the network 135 is unavailable) .
  • FIG. 2 shows a portion of a system 200 in accordance with an embodiment of the present system that utilizes a peer to peer network to further reduce bandwidth demands on Internet gateways (e.g., network connections that are utilized for accessing external data servers) .
  • the system 200 includes client (peer) devices 250A, 250B, 250C, 250D, ... 250N, with each of two or more client devices 250A, 250B, 250C, 250D, ... 250N connected to an intranet 230 through corresponding proxy devices 240A, 240B, 240C, ..., 240N.
  • the intranet 230 is connected illustratively to a video repository 210 through an Internet connection 220.
  • This embodiment of the present system 200 provides a unique protocol where a system, such as provided by the illustrative system 100 shown in FIG. 1 and corresponding to each of the client peer devices 250A, 250B, 250C, 250D, ... 250N, may be enabled to discover peer client devices and communicate to peer client devices, data items that are locally cached including communicating changes in data items that are identified by the data analysis module 150 of a client device.
  • the system 100 may include a peer to peer management portion 180 operably coupled to the processor 110 as shown in FIG. 1.
  • the (identified) changed data item(s) may be propagated from one of the client devices, that has the changed data item(s) locally cached, to each of the other client devices that has an affinity for the changed data item(s) to reduce bandwidth usage and data access latency that would occur should each of the client devices that has an affinity for the changed data item(s) attempts to access the data item(s) individually over the Internet 220.
  • a framework is provided that allows users to share download capacity and mutually benefit in a data sharing embodiment, particularly as a method, etc., of distributing large amounts of data items widely without repeatedly accessing an original distributor of the data (e.g., such as the video repository 210) and without incurring related hardware, hosting and bandwidth costs.
  • the system 200 is configured to include a peer to peer data communications protocol that may include sharing of newsfeeds as well as other data items as may be readily appreciated by a person of ordinary skill in the art.
  • data items may be stored on each participating client device based on affinity determinations, such as frequency of data use, time of data use, etc., that may be made separately on each client device.
  • affinity determinations such as frequency of data use, time of data use, etc., that may be made separately on each client device.
  • a peer to peer management module e.g., the peer to per management module 180 shown in FIG.
  • the client device may search other client devices that are configured as peers to determine whether the requested data item is available on one or more of the client devices.
  • a reconciliation of affinity data may be performed to ensure that the requested data is current data.
  • the requesting client may download the requested data or corresponding portions thereof from the one or more other client devices as may be typical of a peer to peer data sharing network. While the above described embodiment is illustratively described operating utilizing a peer to peer pull model (e.g., peers request data from other peers), it should be readily appreciated that a peer to peer push model may be similarly utilized.
  • the given peer may publish this information to each other peer or may simply maintain a database identifying data items that are commonly accessed by the given peer and at least one other peer, and thereby push the prefetched data item to the at least one other peer.
  • FIG. 3 shows a portion of a system 300 in accordance with a further embodiment of the present system that utilizes a peer to peer network.
  • the system 300 includes a data server 350 that may be a publisher of data including application data, and/or may simply perform a function of a data aggregator and/or may simply identify locations of data.
  • the illustrative system 300 is shown having a single server, the data server 350, for purposes of simplifying the following discussion, where in a typical system, numerous data servers are utilized.
  • the data server 350 is shown operably coupled to peer devices 310, 320, 330 through a network 340.
  • the system 300 operates as a client server system wherein client devices (e.g., the peer devices 310, 320, 30) access content that originates from a server source.
  • client devices e.g., the peer devices 310, 320, 30
  • the network 340 may include one or more of Internet and intranet couplings for example as shown in FIG. 2.
  • the peer devices 310, 320, 330 may be similar to the system 100 as illustratively shown in FIG. 1.
  • server side caching e.g., server caching of data most often accessed
  • CDN Content Distribution Network
  • client side caching e.g., directives to a browser to cache content with an indicated "time to live” (TTL) indicating when the content expires
  • TTL time to live
  • a new peer to peer approach may be applied to caching content between multiple clients through a cooperative and pure P2P network of P2P caches as shown for each of the peer devices 310, 320, 330 including respective P2P caches 312, 322, 332 which may correspond to the cached content 140 shown in FIG. 1.
  • the proxy 120 may intercept a client request for data and analyze the data request so that the data may be prefetched and cached prior to a users request for data in the future.
  • the embodiments shown in FIGs. 2 and 3 further enhance this approach by offering a P2P cache extension supported by the respective P2P caches 312, 322, 332 under control of cache storage and retrieval portions 314, 324, 334.
  • Each of the peer devices 310, 320, 330 are shown including peer data registration portions 316, 326, 328 and peer propagation portions 318, 328, 338 which are illustratively shown in FIG. 1 as the peer to peer management portion 180.
  • an application or its proxy may register with the respective peer data registration portions 316, 326, 328 to register application data that the peer devices 310, 320, 330 cache and prefetch.
  • a determination of which data to register with the respective peer data registration portions 316, 326, 328 may be made through a corresponding data analysis portion and/or the enhanced caching rules portion as shown in FIG. 1.
  • applications and data registered with a given peer device may be propagated to other peer devices via peer propagation portions such that peer devices are aware of other peers (e.g., nodes) within a peer group (e.g., in the proximity of a peer device and/or within a subnet) that have interest in the same application and/or data.
  • the content may be propagated from a peer device that already has the data cached to the peer device requesting the data through the peer propagation portions.
  • data may be propagated from a peer that originally downloaded the data from the data server and/or may be propagated from a peer device that received the data from a device that received the data from the peer that downloaded the data from the data server.
  • the peer device may distribute the data to the peer device 320 and the peer device 330.
  • the peer device 330 may also receive the data from the peer device 320 in place of the peer device 310.
  • the present system may make use of an indication when the cached data was downloaded from the data server 350 and time to live data to assist in determining whether the cached data is outdated and should therefore be refetched from the data server 350. In this way, the present system reduces the number of download requests made to the server and allows for cached data on a given peer device to be updated by other devices present within the peer to peer network. As may be readily appreciated, this system may be applied for data and device applications that are unsecured and/or that have group and individual security access control logic (e.g., see the authentication and security portion 165 shown in FIG. 1) .
  • FIG. 4 shows a flow diagram 400 including details of an illustrative method in accordance with an embodiment of the present system.
  • a user may boot up a client device during act 410.
  • an application corresponding to one or more portions of the system for example as shown in one or more of FIGs. 1, 2, 3 is launched during act 420, such as a start-up application as may be readily appreciated.
  • the present system By configuring the present system to be instantiated as a portion of the boot up process, the user is alleviated from having to separately consider and launch the present system on the client device.
  • the storage and retrieval portion may connect to other client devices and/or remote data sources, for example without requiring opening of a browser application, to prefetch data items during act 430.
  • freshness data items that are relevant to the user's preferences, profiles and affinity and that are not available locally as cached data are retrieved. Thereafter, the present system may periodically (e.g., based on user access request characteristics) , request updated data items from a peer client device, if available, or may request updated data items from a remote data server. In response to a request for a data item from the storage and retrieval portion, the data server and/or the peer network, may send the updated data item(s) . Sometime thereafter, the user may open a web browser to access a data item such as a newsfeed during act 440.
  • a data item such as a newsfeed during act 440.
  • act 480 it is determined if more data items are requested by the user through operation of the web browser. In a case wherein a further data item is requested by the user, the process continues with act 450 as previously described. In a case wherein no further data items are currently requested, the process continues to prefetch and cache data items during act 430.
  • an improved prefetching and caching system that considers user interaction, attention and affinity to types of data when caching and prefetching data from a remote data server.
  • Websites wherein the data is accessed from may be analyzed to determine an ontology of the website and/or to categorize the website to assist with identifying other data that the user may have an affinity towards. For example, if several of the data servers accessed by the user where categorized as hosting right wing political data, the present system may determine that the user has an affinity to right wing political data and therefore prefetch right wing political data. Accordingly, the present system enhances a user's experience in terms of data access.
  • the prefetch protocol of the present system enables data retrieval by one user to result in updating of cached data on multiple client devices.

Abstract

L'invention concerne un dispositif de commande de mise en mémoire cache locale de données disponibles auprès d’un serveur à distance par l’identification de sources de données auxquelles un accès est effectué de manière répétée, notamment un temps et une fréquence d'accès aux données. Une fréquence de mise à jour de la source de données dans le serveur à distance est déterminée et les données de la source de données sont récupérées et mémorisées dans une mémoire cache locale sur la base du temps et de la fréquence identifiés d'accès aux données et de la fréquence déterminée de mise à jour de la source de données. Le dispositif peut être agencé dans une configuration point à point pour distribuer les données mémorisées à un dispositif pair qui a une affinité pour les données mémorisées. Les données mémorisées peuvent être distribuées à des dispositifs pairs sur la base d'un temps et d'une fréquence identifiés d'accès aux données associés au dispositif pair.
PCT/IB2009/053527 2008-05-28 2009-05-20 Système, procédé et dispositif de mise en mémoire cache locale de données WO2009144688A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US5651108P 2008-05-28 2008-05-28
US61/056,511 2008-05-28

Publications (2)

Publication Number Publication Date
WO2009144688A2 true WO2009144688A2 (fr) 2009-12-03
WO2009144688A3 WO2009144688A3 (fr) 2010-01-14

Family

ID=41278297

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2009/053527 WO2009144688A2 (fr) 2008-05-28 2009-05-20 Système, procédé et dispositif de mise en mémoire cache locale de données

Country Status (1)

Country Link
WO (1) WO2009144688A2 (fr)

Cited By (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090083317A1 (en) * 2007-09-21 2009-03-26 Canon Kabushiki Kaisha File system, data processing apparatus, file reference method, and storage medium
WO2012060996A2 (fr) 2010-11-01 2012-05-10 Michael Luna Mise en cache adaptée à un comportement d'application mobile et à des conditions de réseau
US20120151044A1 (en) * 2010-07-26 2012-06-14 Michael Luna Distributed caching for resource and mobile network traffic management
WO2012136828A1 (fr) * 2011-04-07 2012-10-11 Replify Ltd Système de cache multiutilisateur
US8732237B2 (en) 2010-11-29 2014-05-20 International Business Machines Corporation Interaction-based update delivery for user generated content
US8750123B1 (en) 2013-03-11 2014-06-10 Seven Networks, Inc. Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network
US8761756B2 (en) 2005-06-21 2014-06-24 Seven Networks International Oy Maintaining an IP connection in a mobile network
US8774844B2 (en) 2007-06-01 2014-07-08 Seven Networks, Inc. Integrated messaging
US8775631B2 (en) 2012-07-13 2014-07-08 Seven Networks, Inc. Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications
US8782222B2 (en) 2010-11-01 2014-07-15 Seven Networks Timing of keep-alive messages used in a system for mobile network resource conservation and optimization
US8799410B2 (en) 2008-01-28 2014-08-05 Seven Networks, Inc. System and method of a relay server for managing communications and notification between a mobile device and a web access server
US8812695B2 (en) 2012-04-09 2014-08-19 Seven Networks, Inc. Method and system for management of a virtual network connection without heartbeat messages
US8811952B2 (en) 2002-01-08 2014-08-19 Seven Networks, Inc. Mobile device power management in data synchronization over a mobile network with or without a trigger notification
US8832228B2 (en) 2011-04-27 2014-09-09 Seven Networks, Inc. System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief
US8839412B1 (en) 2005-04-21 2014-09-16 Seven Networks, Inc. Flexible real-time inbox access
US8843153B2 (en) 2010-11-01 2014-09-23 Seven Networks, Inc. Mobile traffic categorization and policy for network use optimization while preserving user experience
US8862657B2 (en) 2008-01-25 2014-10-14 Seven Networks, Inc. Policy based content service
US8868753B2 (en) 2011-12-06 2014-10-21 Seven Networks, Inc. System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation
US8874761B2 (en) 2013-01-25 2014-10-28 Seven Networks, Inc. Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols
US8909759B2 (en) 2008-10-10 2014-12-09 Seven Networks, Inc. Bandwidth measurement
US8934414B2 (en) 2011-12-06 2015-01-13 Seven Networks, Inc. Cellular or WiFi mobile traffic optimization based on public or private network destination
US9002828B2 (en) 2007-12-13 2015-04-07 Seven Networks, Inc. Predictive content delivery
US9009250B2 (en) 2011-12-07 2015-04-14 Seven Networks, Inc. Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation
US9021021B2 (en) 2011-12-14 2015-04-28 Seven Networks, Inc. Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system
US9043433B2 (en) 2010-07-26 2015-05-26 Seven Networks, Inc. Mobile network traffic coordination across multiple applications
US9065765B2 (en) 2013-07-22 2015-06-23 Seven Networks, Inc. Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network
US9084105B2 (en) 2011-04-19 2015-07-14 Seven Networks, Inc. Device resources sharing for network resource conservation
US9173128B2 (en) 2011-12-07 2015-10-27 Seven Networks, Llc Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol
EP2901310A4 (fr) * 2012-09-28 2016-04-27 Vmware Inc Reproduction automatisée de documents dans un système informatique distribué
US9594846B2 (en) 2011-08-11 2017-03-14 Helwett-Packard Development Company, L.P. Client side caching
CN108429777A (zh) * 2017-02-15 2018-08-21 腾讯科技（北京）有限公司 一种基于缓存的数据更新方法及服务器
US10299161B1 (en) 2010-07-26 2019-05-21 Seven Networks, Llc Predictive fetching of background data request in resource conserving manner
US10789629B2 (en) 2012-03-02 2020-09-29 Google Llc Content purchasing

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020107935A1 (en) * 2001-01-12 2002-08-08 Epicrealm Inc. Method and system for community data caching
US20020194434A1 (en) * 2001-06-13 2002-12-19 Toshiyasu Kurasugi Method of prefetching reference objects using wieght values of referrer objects
US20040128346A1 (en) * 2001-07-16 2004-07-01 Shmuel Melamed Bandwidth savings and qos improvement for www sites by catching static and dynamic content on a distributed network of caches
US20050086583A1 (en) * 2000-01-28 2005-04-21 Microsoft Corporation Proxy server using a statistical model

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050086583A1 (en) * 2000-01-28 2005-04-21 Microsoft Corporation Proxy server using a statistical model
US20020107935A1 (en) * 2001-01-12 2002-08-08 Epicrealm Inc. Method and system for community data caching
US20020194434A1 (en) * 2001-06-13 2002-12-19 Toshiyasu Kurasugi Method of prefetching reference objects using wieght values of referrer objects
US20040128346A1 (en) * 2001-07-16 2004-07-01 Shmuel Melamed Bandwidth savings and qos improvement for www sites by catching static and dynamic content on a distributed network of caches

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TAY T T ET AL: "Peer-distributed web caching with incremental update scheme" IEE PROCEEDINGS : COMMUNICATIONS, INSTITUTION OF ELECTRICAL ENGINEERS, GB, vol. 152, no. 3, 3 June 2005 (2005-06-03), pages 327-334, XP006024073 ISSN: 1350-2425 *

Cited By (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8811952B2 (en) 2002-01-08 2014-08-19 Seven Networks, Inc. Mobile device power management in data synchronization over a mobile network with or without a trigger notification
US8839412B1 (en) 2005-04-21 2014-09-16 Seven Networks, Inc. Flexible real-time inbox access
US8761756B2 (en) 2005-06-21 2014-06-24 Seven Networks International Oy Maintaining an IP connection in a mobile network
US8805425B2 (en) 2007-06-01 2014-08-12 Seven Networks, Inc. Integrated messaging
US8774844B2 (en) 2007-06-01 2014-07-08 Seven Networks, Inc. Integrated messaging
US20090083317A1 (en) * 2007-09-21 2009-03-26 Canon Kabushiki Kaisha File system, data processing apparatus, file reference method, and storage medium
US9002828B2 (en) 2007-12-13 2015-04-07 Seven Networks, Inc. Predictive content delivery
US8862657B2 (en) 2008-01-25 2014-10-14 Seven Networks, Inc. Policy based content service
US8838744B2 (en) 2008-01-28 2014-09-16 Seven Networks, Inc. Web-based access to data objects
US8799410B2 (en) 2008-01-28 2014-08-05 Seven Networks, Inc. System and method of a relay server for managing communications and notification between a mobile device and a web access server
US8909759B2 (en) 2008-10-10 2014-12-09 Seven Networks, Inc. Bandwidth measurement
US9049179B2 (en) 2010-07-26 2015-06-02 Seven Networks, Inc. Mobile network traffic coordination across multiple applications
US10638358B2 (en) 2010-07-26 2020-04-28 Seven Networks, Llc Mobile application traffic optimization
US9043433B2 (en) 2010-07-26 2015-05-26 Seven Networks, Inc. Mobile network traffic coordination across multiple applications
US8838783B2 (en) * 2010-07-26 2014-09-16 Seven Networks, Inc. Distributed caching for resource and mobile network traffic management
US10299161B1 (en) 2010-07-26 2019-05-21 Seven Networks, Llc Predictive fetching of background data request in resource conserving manner
US20120151044A1 (en) * 2010-07-26 2012-06-14 Michael Luna Distributed caching for resource and mobile network traffic management
US9275163B2 (en) 2010-11-01 2016-03-01 Seven Networks, Llc Request and response characteristics based adaptation of distributed caching in a mobile network
EP2635973A4 (fr) * 2010-11-01 2014-01-15 Seven Networks Inc Mise en cache adaptée à un comportement d'application mobile et à des conditions de réseau
GB2499534B (en) * 2010-11-01 2018-09-19 Seven Networks Llc Caching adapted for mobile application behavior and network conditions
US8782222B2 (en) 2010-11-01 2014-07-15 Seven Networks Timing of keep-alive messages used in a system for mobile network resource conservation and optimization
US8843153B2 (en) 2010-11-01 2014-09-23 Seven Networks, Inc. Mobile traffic categorization and policy for network use optimization while preserving user experience
EP2635973A2 (fr) * 2010-11-01 2013-09-11 Seven Networks, Inc. Mise en cache adaptée à un comportement d'application mobile et à des conditions de réseau
WO2012060996A2 (fr) 2010-11-01 2012-05-10 Michael Luna Mise en cache adaptée à un comportement d'application mobile et à des conditions de réseau
CN103620576A (zh) * 2010-11-01 2014-03-05 七网络公司 适用于移动应用程序行为和网络条件的缓存
US8732237B2 (en) 2010-11-29 2014-05-20 International Business Machines Corporation Interaction-based update delivery for user generated content
WO2012136828A1 (fr) * 2011-04-07 2012-10-11 Replify Ltd Système de cache multiutilisateur
US9084105B2 (en) 2011-04-19 2015-07-14 Seven Networks, Inc. Device resources sharing for network resource conservation
US8832228B2 (en) 2011-04-27 2014-09-09 Seven Networks, Inc. System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief
US9594846B2 (en) 2011-08-11 2017-03-14 Helwett-Packard Development Company, L.P. Client side caching
US8934414B2 (en) 2011-12-06 2015-01-13 Seven Networks, Inc. Cellular or WiFi mobile traffic optimization based on public or private network destination
US8977755B2 (en) 2011-12-06 2015-03-10 Seven Networks, Inc. Mobile device and method to utilize the failover mechanism for fault tolerance provided for mobile traffic management and network/device resource conservation
US8868753B2 (en) 2011-12-06 2014-10-21 Seven Networks, Inc. System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation
US9009250B2 (en) 2011-12-07 2015-04-14 Seven Networks, Inc. Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation
US9173128B2 (en) 2011-12-07 2015-10-27 Seven Networks, Llc Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol
US9208123B2 (en) 2011-12-07 2015-12-08 Seven Networks, Llc Mobile device having content caching mechanisms integrated with a network operator for traffic alleviation in a wireless network and methods therefor
US9021021B2 (en) 2011-12-14 2015-04-28 Seven Networks, Inc. Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system
US10789629B2 (en) 2012-03-02 2020-09-29 Google Llc Content purchasing
US8812695B2 (en) 2012-04-09 2014-08-19 Seven Networks, Inc. Method and system for management of a virtual network connection without heartbeat messages
US8775631B2 (en) 2012-07-13 2014-07-08 Seven Networks, Inc. Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications
US9619539B2 (en) 2012-09-28 2017-04-11 Vmware, Inc. Automated document replication in a distributed computing system
EP2901310A4 (fr) * 2012-09-28 2016-04-27 Vmware Inc Reproduction automatisée de documents dans un système informatique distribué
US8874761B2 (en) 2013-01-25 2014-10-28 Seven Networks, Inc. Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols
US8750123B1 (en) 2013-03-11 2014-06-10 Seven Networks, Inc. Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network
US9065765B2 (en) 2013-07-22 2015-06-23 Seven Networks, Inc. Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network
CN108429777A (zh) * 2017-02-15 2018-08-21 腾讯科技（北京）有限公司 一种基于缓存的数据更新方法及服务器
CN108429777B (zh) * 2017-02-15 2022-05-13 腾讯科技（北京）有限公司 一种基于缓存的数据更新方法及服务器

Also Published As

Publication number Publication date
WO2009144688A3 (fr) 2010-01-14

Similar Documents

Publication Publication Date Title
WO2009144688A2 (fr) Système, procédé et dispositif de mise en mémoire cache locale de données
US11233879B2 (en) System providing faster and more efficient data communication
US6766422B2 (en) Method and system for web caching based on predictive usage
US8990357B2 (en) Method and apparatus for reducing loading time of web pages
US11044335B2 (en) Method and apparatus for reducing network resource transmission size using delta compression
US20060259690A1 (en) Methods and system for prepositioning frequently accessed web content
US20180159769A1 (en) Request routing based on class
US6917960B1 (en) Intelligent content precaching
Davison A web caching primer
US20140019577A1 (en) Intelligent edge caching
US10735528B1 (en) Geographic relocation of content source in a content delivery network
US10200490B2 (en) Content-based redirection
US6687792B2 (en) Method and system for selectively caching web elements
Ariyasinghe et al. Distributed local area content delivery approach with heuristic based web prefetching
EP2552082B1 (fr) Procédé d'accélération de site Web favori et système
Chavan et al. Enhancing performance of proxy cache servers using daemon process
Mahdavi et al. Caching on the Web

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09754313

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09754313

Country of ref document: EP

Kind code of ref document: A2