A computer-implemented method and system for caching multi-session data communications in a computer network.
|
1. A computer-implemented method of caching multi-session data communications in a computer network, comprising the steps of:
(a) receiving, intercepting, or monitoring a plurality of data sessions between a client executing a multi-session application for retrieving a desired content object and content sources providing portions of the content object;
(b) identifying a data protocol used by the client and identifying data queries within the data sessions;
(c) identifying the content object or portions thereof requested by the client from some but not all the data queries and data responses thereto; and
(d) determining, using information from step (c), if the content object or portions thereof are stored in cache and, if so, sending the content object or portions thereof stored in cache to the client.
2. The method of
3. The method of
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of
9. The method of
|
|||||||||||||||||||||||||||
This application is a continuation of U.S. patent application Ser. No. 13/341,619, filed on Dec. 30, 2011, issued as U.S. Pat. No. 8,185,612, entitled METHODS AND SYSTEMS FOR CACHING DATA COMMUNICATIONS OVER COMPUTER NETWORKS, which claims priority from U.S. Provisional Patent Application No. 61/428,538, filed on Dec. 30, 2010, entitled METHODS AND SYSTEMS FOR CACHING DATA COMMUNICATIONS OVER COMPUTER NETWORKS, both of which are hereby incorporated by reference.
The present application relates generally to the caching of data communications over computer networks such as, e.g., the Internet, a local area network, a wide area network, a wireless network, and others.
Caching of data communications over computer networks is a well-known network optimization technique, affording improvement of application performance and optimal utilization of network resources through storing and delivering popular content close to end users.
Content caching solutions have traditionally focused on caching of client-server communications, e.g., Web browsing or streaming sessions, where the cache intermediates delivery of content objects (e.g., text files and images in case of Web browsing) from server to client.
The content applications supported by the caching solutions are designed to support caching; they do not utilize end-to-end encryption of the data session, and they have optional client-side explicit support for caching and utilize well-known data ports (tcp/80 for HTTP, tcp/1935 for RTMP, etc.).
The data sessions established by Web browsing and streaming applications are atomic. Each such session incorporates all information needed for the cache to identify a content query, content object (or portion of it) requested, and address of the content source where the object may be maintained.
The traditional caching solutions accordingly implement the following caching methodology:
In recent years, Internet applications have evolved in functionality and complexity, using dynamic content object identifiers (e.g., HTTP URLs) that survive in the scope of one download session only, supporting transfer of the same content object over several concurrent sessions, from multiple content sources, involving multiple dynamic ports, involving end-to-end encryption of the data sessions. These new applications include multiple types of peer-to-peer (P2P) applications for file sharing and streaming, adaptive bitrate protocols for delivery of video over HTTP, HTTP download accelerators, and software update services such as Microsoft Windows Update.
The peer-to-peer applications typically implement a mechanism of “peer discovery” where the client application accesses the P2P network, queries the network to discover content sources that may offer the content object, and subsequently establishes data sessions with these content sources, with some of these sessions using end-to-end encryption.
It is a common practice for content sources in P2P networks to use dynamic rather than static “well-known” ports.
P2P applications can employ encryption of the session in such a way as to avoid detection by network elements, using Layer7 criteria for session identification.
As a result, traditional caching solutions cannot identify and intercept these data sessions, nor are they able to parse the data protocol to identify the data query, due to the encryption.
Non-P2P applications (e.g., download accelerators, adaptive bitrate video clients, software update services, and others) commonly establish multiple sessions to arrange retrieval of the same content object, where each separate session does not offer all the information needed for the cache to identify the requested data object and/or match a data request with a data response.
The features exhibited by these new applications obviate traditional caching methodology. It would be desirable to provide alternative approaches to content caching to support such new applications.
In accordance with one or more embodiments, a computer-implemented method of caching multi-session data communications in a computer network is provided, including the steps of: (a) receiving, intercepting, or monitoring one or more data sessions between a client executing a multi-session application for retrieving a desired content object and one or more metadata services, said client communicating with the one or more metadata services to discover metadata for the content object; (b) analyzing queries and responses exchanged between the client and the one of more metadata services to discover metadata for the content object; (c) receiving or intercepting subsequent data sessions between the client and content sources; (d) identifying a data protocol used by the client and identifying data queries within the data sessions; (e) identifying the content object or portions thereof requested by the client in the data queries; and (f) determining if the content object or portions thereof are stored in cache and, if so, sending the content object or portions thereof stored in cache to the client, and, if not, sending the data queries to the content sources, storing data responses from the content sources, and sending the data responses to the client.
In accordance with one or more embodiments, a computer-implemented caching service is provided for caching multi-session data communications in a computer network. The caching service is configured to: (a) receive, intercept, or monitor one or more data sessions between a client executing a multi-session application for retrieving a desired content object and one or more metadata services, said client communicating with the one or more metadata services to discover metadata for the content object; (b) analyze queries and responses exchanged between the client and the one of more metadata services to discover metadata for the content object; (c) receive or intercept subsequent data sessions between the client and content sources; (d) identify a data protocol used by the client and identify data queries within the data sessions; (e) identify the content object or portions thereof requested by the client in the data queries; and (f) determine if the content object or portions thereof are stored in cache and, if so, send the content object or portions thereof stored in cache to the client, and, if not, send the data queries to the content sources, store data responses from the content sources, and send the data responses to the client.
In accordance with various embodiments, a service is provided for caching of applications that utilize multiple sessions for retrieval of same content object (e.g., file or stream).
The multi-session applications supported by the caching service can include:
The content object meta-data includes at least one variable, selected from the following:
The content source address can be identified through an IP address, e.g., using IPv4 IP address 1.1.1.1 or IPv6 address fe80::200:f8ff:fe21:67cf, or using a domain name, e.g., cachel2.bos.us.cdn.net, that can be resolved to IP address using Domain Name System (DNS).
The content source address can use either implicitly named port number for applications using well-known protocol ports (e.g., port tcp/80 used by HTTP protocol) or name ports explicitly.
The content source address can be identified in conjunction with protocols supported by it, including, but not limited to, using universal resource locators (URL), as defined in RFC1738, that specifies protocol, content source address, port and remote path to the object.
The content object structure information includes information allowing client A1 to form data queries for parts of the object and to verify correctness of data responses received in response to such queries.
The content object structure information includes information pertaining to parts comprising the objects, e.g., “pieces” used by Bittorrent protocol, “parts” used by eDonkey P2P protocol or “playback levels” used in adaptive bitrate streaming protocols, such as Microsoft Silverlight Smooth Streaming, Adobe HTTP Dynamic Streaming, Apple HTTP Live Streaming, among others.
The information about content objects parts includes at least one of the following: enumeration of parts of the content object, length of each part, data checksum of each part, availability of parts at a specific content source, where the content source is identified using content source addresses as defined in [0023-0025] above.
The meta-data including all or some of the above information can be stored in a separate file with a pre-defined structure, e.g. a torrent file for Bittorrent or a manifest file used by Microsoft Silverlight smooth streaming.
The meta-data services M offering content object meta-data may include dedicated network servers designed to support delivery of a specific application or one or more content objects (e.g., Bittorrent trackers, ED2K servers, etc.), generic search engines (Google, Microsoft Bing, or others), a network of computer nodes that collectively stores the meta-data (e.g. distributed hash table networks used by P2P applications), or other clients that participate in distributed content source discovery networks (e.g., distributed hash table networks), or other clients that are downloading and/or serving the content object Z1 and maintain meta-data related to it.
Client A1 may use multiple meta-data services M to discover content object meta-data, where one service M1 can provide part of the content object meta-data and optionally point to another service M2 to provide another part.
Thus, for example, client A1 may retrieve a torrent file from a Bittorrent search engine that includes the content object data structure information as well as URL of a Bittorrent tracker that provides the information of currently active content source addresses.
Client A1 may continue to send data queries to meta-data services M during download of content object Z1 or portions of it, for purposes of identification of new content sources and/or content object structure information (for example, in case of object Z1 being a live stream, of which new parts become continuously available).
In accordance with one or more embodiments, the caching service C receives and stores data queries and/or responses exchanged between client A1 and one or more meta-data services M.
In accordance with one or more embodiments, the caching service C intercepts the sessions between A1 and M, either by being in data path between A1 and B, or through use of one or more dedicated redirection devices (e.g., a load balancer, a router, a DPI device, etc.) that sit in data path and redirect specific data sessions to the caching service C, and relays the data queries and responses between A1 and M.
In accordance with one or more embodiments, the caching service C modifies at least one of the meta-data responses provided by the meta-data service M, e.g., to indicate the caching service C as a content source or as a meta-data service for the content object Z1.
In accordance with one or more embodiments, the caching service C receives a copy of communications between the client A1 and the meta-data services M, using an optical tap, mirror port or other device replicating network traffic.
In accordance with one or more embodiments, the caching service C receives the data queries related to content object Z1 from client A1 by virtue of offering at least one of the meta-data services M.
In accordance with one or more embodiments, the caching service C subsequently queries the meta-data services M itself for meta-data related to content object Z1, and receives and stores the responses.
In accordance with one or more embodiments, the caching service C continuously analyzes the queries and responses exchanged between at least one client A1 and the meta-data services M, as well as the responses received by the caching service C directly from the meta-data services M, as described above.
As a result, the caching service C maintains content object meta-data Mz for at least one content object Z1 that client A1 is retrieving.
In accordance with one or more embodiments, the caching service C stores meta-data responses as part of meta-data Mz in conjunction with the most recent time the response was received by C.
The caching service C subsequently periodically discards any responses that were received more than some time ago based on time-out.
In accordance with one or more embodiments, the caching service monitors meta-data requests and responses and discards any stored responses that contradict meta-data responses received later.
Following retrieval of meta-data pertaining to the content object Z1, the client A1 and at least one of content sources B1 discovered by the client A1 using the meta-data services M, start establishing data sessions with each other, for purpose of retrieving content object Z1 or part of it by A1.
In accordance with one or more embodiments, the caching service C intercepts the data sessions S1 established between the client A1 and the content sources B1.
In accordance with one or more embodiments, the caching service C intercepts the data sessions either by being in a data path between A1 and B1, or through use of one or more dedicated redirection devices (e.g., load balancer, router, DPI device, etc.) that sit in data path and redirect specific data sessions to the caching service C.
In accordance with one or more embodiments, the caching service C intercepts only such sessions that have been established between A1 and such content sources B1′, that match the meta-data Mz stored for the object Z1 by the caching service C.
In accordance with one or more embodiments, the client A1 establishes at least one session S2 with the caching service C, which is identified by the client A1 as one of the content sources for the content object Z1.
In accordance with one or more embodiments, the caching service C utilizes at least one of the following protocols to interpret data queries and data responses in the session S1 between the client A1 and content source S1:
In accordance with one or more embodiments, the caching service C utilizes similar approach for session S2.
In accordance with one or more embodiments, when failing to identify data protocol of session S1 and S2, using method described in [0048], the caching service C may apply at least one of encryption keys K, stored by C as part of the meta-data Mz, to establish an encrypted session with either client A1, or content source B1, or both.
The encryption keys K may be associated with the content object Z (e.g., in Bittorrent the hash identifier of object Z is used for encryption of sessions between Bittorrent peers), or specific content sources.
In accordance with one or more embodiments, following establishment of data session with client A1 and identification of the protocol used in this session, the caching service C receives data query Q1 for object Z1 or portion of it from the client A1.
In accordance with one or more embodiments, the caching service C identifies a response matching the query, using the meta-data Mz associated with the content object Z1 as described above.
For example, if the client A1 requests a chunk of 500 Kbps playback level of content object Z1, available over Microsoft Silverlight smooth streaming protocol, that starts at offset 0, without identification of the end offset, the caching service C may use the meta-data Mz describing the object Z1, to identify the end offset.
In accordance with one or more embodiments, if the matching response R1 to the query Q1 is stored by the caching service C, C delivers the response to the end client A1.
In accordance with one or more embodiments, the caching service C may use the stored meta-data Mz associated with the content object Z to verify the validity of the data response R1, before sending it to the client A1.
In accordance with one or more embodiments, when a matching response to the query Q1 is not available at the caching service C and the query Q1 has been sent as part of session S1 between the client A1 and the content source B1, the caching service C forwards the query to retrieve such response from the content source B1, receives and optionally stores the response and relays the response to the client A1.
In accordance with one or more embodiments, when a matching response to the query Q1 is not found at the caching service C, the caching service C sends data query Q1′ allowing it to respond to the data query Q1 to at least one of content sources B, identified by C as carrying the content object Z, based on the meta-data Mz stored by C.
Subsequently, the caching service C receives the responses R1′ for these queries, stores them and optionally verifies their validity against the meta-data Mz, and delivers response to the query Q1 to the client A1.
In accordance with one or more embodiments, when a matching response to the query Q1 is not found at the caching service C, C may redirect the client A1 to one of content sources B for the content object Z, as stored by the caching service in the meta-data Mz.
(b) Multi-Session Applications Allowing Identification of Content Object Only in Some Sessions
Client A2 establishes multiple sessions S2 to one or more destinations B2 to retrieve content object Z2, in parallel or in series. The client A2 sends data queries for portions of the content object Z2 in each such session.
Depending on the naming convention for the content object Z and/or its parts, used by client A2 and destination(s) B2, the caching service C, intercepting or receiving sessions S2, may not be able to identify the content object and/or portions of it requested by client A2 in each session, or identify data responses matching those queries.
The client A2 and content source(s) B2 may use dynamic URL (so-called “hashed URLs”) to identify object Z2 that is assigned uniquely for each download of the content object Z2. In this case caching service C cannot rely on the data in the data query alone to identify a matching response, but rather analyzes data responses to identify the requested object and match it to the previously stored data responses.
According to one or more embodiments, when receiving such data queries and/or responses in one or more sessions S2 that allow identification of the content object Z, C stores the content object Z2 identification together with the IP address of client A2, the IP address of content source B2, and the dynamic content identification (e.g. URL) used by client A2, in a list L2.
According to one or more embodiments, when caching service C receives a data query and/or data response that does not allow it to identify the content object Z referenced in the query and/or response, caching service C establishes whether the IP address of client A2, dynamic content identification URL, and IP address of content source B2 are stored in list L2.
According to one or more embodiments, in case of applications that utilize multiple content sources, the caching service C may disregard the IP address of content source B2.
According to one or more embodiments, caching service C removes entries from list L4 based on the timeout since last activity seen by client A2, related to content object Z2.
The processes of the caching service described above may be implemented in software, hardware, firmware, or any combination thereof. The processes are preferably implemented in one or more computer programs executing on a programmable device including a processor, a storage medium readable by the processor (including, e.g., volatile and non-volatile memory and/or storage elements), and input and output devices. Each computer program can be a set of instructions (program code) in a code module resident in the random access memory of the device. Until required by the device, the set of instructions may be stored in another computer memory (e.g., in a hard disk drive, or in a removable memory such as an optical disk, external hard drive, memory card, or flash drive) or stored on another computer system and downloaded via the Internet or other network.
Having thus described several illustrative embodiments, it is to be appreciated that various alterations, modifications, and improvements will readily occur to those skilled in the art. Such alterations, modifications, and improvements are intended to form a part of this disclosure, and are intended to be within the spirit and scope of this disclosure. While some examples presented herein involve specific combinations of functions or structural elements, it should be understood that those functions and elements may be combined in other ways according to the present disclosure to accomplish the same or different objectives. In particular, acts, elements, and features discussed in connection with one embodiment are not intended to be excluded from similar or other roles in other embodiments.
Additionally, elements and components described herein may be further divided into additional components or joined together to form fewer components for performing the same functions. For example, the caching service may comprise one or more physical machines, or virtual machines running on one or more physical machines. In addition, the caching service may comprise a cluster of computers or numerous distributed computers that are connected by the Internet or another network.
Accordingly, the foregoing description and attached drawings are by way of example only, and are not intended to be limiting.
Arolovitch, Alan, Bachar, Shmuel, Shemer, Shay, Gavish, Dror M., Grin, Shahar G.
| Patent | Priority | Assignee | Title |
| 10484497, | Dec 30 2010 | ZEPHYRTEL, INC | Methods and systems for caching data communications over computer networks |
| 11019170, | Dec 30 2010 | ZEPHYRTEL, INC. | Methods and systems for caching data communications over computer networks |
| Patent | Priority | Assignee | Title |
| 3289358, | |||
| 5764982, | Oct 30 1992 | International Business Machines Corporation | Peer-to-peer communication interface |
| 5778185, | Aug 19 1994 | Cisco Technology, Inc | Method for finding a resource in a scalable distributed computing environment |
| 5852717, | Nov 20 1996 | Intel Corporation | Performance optimizations for computer networks utilizing HTTP |
| 5884046, | Oct 23 1996 | PARITY NETWORKS LLC | Apparatus and method for sharing data and routing messages between a plurality of workstations in a local area network |
| 5907678, | May 07 1997 | International Business Machines Corporation | Client/server system in which protocol caches for multiple sessions are selectively copied into a common checkpoint cache upon receiving a checkpoint request |
| 5950198, | Mar 24 1997 | JPMORGAN CHASE BANK, N A , AS SUCCESSOR AGENT | Processes and apparatuses for generating file correspondency through replication and synchronization between target and source computers |
| 5950205, | Sep 25 1997 | Cisco Technology, Inc | Data transmission over the internet using a cache memory file system |
| 5960404, | Aug 28 1997 | International Business Machines Corporation | Mechanism for heterogeneous, peer-to-peer, and disconnected workflow operation |
| 5987376, | Jul 16 1997 | Microsoft Technology Licensing, LLC | System and method for the distribution and synchronization of data and state information between clients in a distributed processing system |
| 6003045, | Sep 17 1997 | GOOGLE LLC | Accessing stored files from multiple storage devices |
| 6018780, | May 19 1998 | Alcatel Lucent | Method and apparatus for downloading a file to a remote unit |
| 6085251, | Apr 02 1998 | AIR FORCE, UNITED STATES OF AMERICA AS REPRESENTED BY THE SECRETARY OF THE, THE | Implementing a parallel file transfer protocol |
| 6105029, | Sep 17 1997 | International Business Machines Corporation | Retrieving network files through parallel channels |
| 6185598, | Feb 10 1998 | MOUNT SHASTA ACQUISITION LLC; Level 3 Communications, LLC | Optimized network resource location |
| 6199107, | Jul 22 1998 | Microsoft Technology Licensing, LLC | Partial file caching and read range resume system and method |
| 6219786, | Sep 09 1998 | FORCEPOINT FEDERAL HOLDINGS LLC; Forcepoint LLC | Method and system for monitoring and controlling network access |
| 6240461, | Sep 25 1997 | Cisco Technology, Inc | Methods and apparatus for caching network data traffic |
| 6263371, | Jun 10 1999 | CA, INC | Method and apparatus for seaming of streaming content |
| 6286084, | Sep 16 1998 | Cisco Technology, Inc. | Methods and apparatus for populating a network cache |
| 6304914, | Sep 22 1998 | Microsoft Technology Licensing, LLC | Method and apparatus for pre-compression packaging |
| 6339785, | Nov 24 1999 | SPEEDBIT LTD | Multi-server file download |
| 6366907, | Dec 15 1999 | MOON GLOW, SERIES 82 OF ALLIED SECURITY TRUST I | Real-time search engine |
| 6424992, | Dec 23 1996 | International Business Machines Corporation | Affinity-based router and routing method |
| 6434608, | Feb 26 1999 | CISCO TECHNOLOGY,INC | Methods and apparatus for caching network traffic |
| 6460087, | Feb 25 1998 | KDDI Corporation | Method of transferring file |
| 6622157, | Sep 28 1998 | ARRAY NETWORKS, INC | Extending network services using mobile agents |
| 6742023, | Apr 28 2000 | MOON GLOW, SERIES 82 OF ALLIED SECURITY TRUST I | Use-sensitive distribution of data files between users |
| 6865600, | May 19 2000 | MOON GLOW, SERIES 82 OF ALLIED SECURITY TRUST I | System and method for selecting internet media channels |
| 6940835, | Dec 28 2000 | RPX CLEARINGHOUSE LLC | Application-level mobility support in communications network |
| 6976165, | Sep 07 1999 | EMC IP HOLDING COMPANY LLC | System and method for secure storage, transfer and retrieval of content addressable information |
| 7010578, | Sep 21 2000 | AKAMAI TECHNOLOGIES, INC | Internet content delivery service with third party cache interface support |
| 7043644, | Jan 31 2001 | Qurio Holdings, Inc | Facilitating file access from firewall-protected nodes in a peer-to-peer network |
| 20020010866, | |||
| 20020049760, | |||
| 20030005040, | |||
| 20030046409, | |||
| 20030140159, | |||
| 20030195940, | |||
| 20050102427, | |||
| 20050132049, | |||
| 20060168088, | |||
| 20060212584, | |||
| 20070198726, | |||
| 20080005349, | |||
| 20080046596, | |||
| 20080281908, | |||
| 20090177778, | |||
| 20100005171, | |||
| 20110173345, | |||
| 20120011324, | |||
| EP1011244, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Dec 29 2011 | BACHAR, SHMUEL | PEERAPP LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028245 | /0709 | |
| Dec 29 2011 | GAVISH, DROR MOSHE | PEERAPP LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028245 | /0709 | |
| Dec 29 2011 | GRIN, SHAHAR GUY | PEERAPP LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028245 | /0709 | |
| Dec 29 2011 | SHEMER, SHAY | PEERAPP LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028245 | /0709 | |
| Dec 30 2011 | AROLOVITCH, ALAN | PEERAPP LTD | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028245 | /0709 | |
| May 21 2012 | PeerApp Ltd. | (assignment on the face of the patent) | / | |||
| Sep 14 2017 | PEERAPP LTD | Pacific Western Bank | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 043601 | /0449 | |
| Sep 15 2017 | PEERAPP LTD | PEERAPP SOLUTIONS, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 044017 | /0731 | |
| Jun 22 2018 | PEERAPP SOLUTIONS, INC | ZEPHYRTEL, INC | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 046783 | /0980 |
| Date | Maintenance Fee Events |
| Jan 29 2018 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
| Sep 13 2018 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Sep 07 2022 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| Date | Maintenance Schedule |
| Mar 24 2018 | 4 years fee payment window open |
| Sep 24 2018 | 6 months grace period start (w surcharge) |
| Mar 24 2019 | patent expiry (for year 4) |
| Mar 24 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Mar 24 2022 | 8 years fee payment window open |
| Sep 24 2022 | 6 months grace period start (w surcharge) |
| Mar 24 2023 | patent expiry (for year 8) |
| Mar 24 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Mar 24 2026 | 12 years fee payment window open |
| Sep 24 2026 | 6 months grace period start (w surcharge) |
| Mar 24 2027 | patent expiry (for year 12) |
| Mar 24 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |