System and method for mobility and multi-homing content retrieval applications

• US 9,215,283 B2
• Filed: 09/30/2011
• Issued: 12/15/2015
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Hampel, K. Georg, Klein, Thierry E.
• Primary Examiner(s): Etienne, Ario
• Assistant Examiner(s): Shiu, Ho
• Application Number:
  US13/249,314
• Publication Number:
  US 20130086142A1
• Time in Patent Office: 1,537 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/101 based on network conditions
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 36/0011 for data sessions of end-to-end connection

Abstract

A controller function residing underneath a client application in a TCP/IP stack or session layer monitors state and status information associated with session-based application layer functions (e.g., content retrieval) and uses this information to migrate one or more sessions from a first client interface to a second client interface (e.g., 3G, 4G, LTE, 802.11x, WiMAX) and to a different application function serving entity (e.g., a different content server, cache server, service provider).

Claims

1. A method for migrating a content retrieval session associated with a content retrieval application at a host from a first server to a second server, the method comprising:

establishing a transport connection with the first server using a first network interface associated with a first network;

caching a first content request message transmitted toward the first server via the first network interface;

monitoring content received from the first server via the first network interface to determine an amount of content received by the content retrieval application via the first network interface;

establishing a transport connection with the second server using a second network interface associated with a second network; and

transmitting, toward the second server via the second network interface, a second content request message determined based on the cached first content request message and the determined amount of content received by the content retrieval application via the first network interface, wherein the second content request message comprises information from the cached first content request message and an instruction configured to instruct the second server to omit delivery of the amount of content received by the content retrieval application via the first network interface;

wherein the first network interface and the second network interface are different.

2. The method of claim 1, wherein the content is propagated via an application layer protocol, wherein monitoring the content received from the first server via the first network interface to determine the amount of content received by the content retrieval application via the first network interface comprises discounting signaling information associated with delivery of the content from the first server via the first network interface.

3. The method of claim 1, wherein the amount of content received by the content retrieval application via the first network interface is represented using at least one of:

an amount of octets or bits of content received by the content retrieval application via the first network interface;

a byte count of bytes of payload representing content data portions that have been delivered via the first network interface and acknowledged;

a list of object identifiers;

a number of frames received;

or

a time interval it would take to play the content received by the content retrieval application via the first network interface.

4. The method of claim 1, wherein the instruction comprises an offset indicative of the determined amount of content received by the content retrieval application via the first network interface.

5. The method of claim 4, wherein the offset comprises one of:

an amount of octets or bits of content received by the content retrieval application via the first network interface;

a byte count of bytes of payload representing content data portions that have been delivered via the first network interface and acknowledged;

a list of object identifiers;

a number of frames received;

or

a time interval it would take to play the content received by the content retrieval application via the first network interface.

6. The method of claim 1, wherein the second content request message comprises a Hypertext Transfer Protocol (HTTP) GET message, wherein the instruction comprises an HTTP RANGE command including an amount of octets of content received by the content retrieval application via the first network interface.

7. The method of claim 1, further comprising:

intercepting a domain name server (DNS) request sent toward a DNS server, the DNS request comprising a uniform resource identifier (URI) or uniform resource locator (URL) of the requested content;

caching the URI or the URL of the requested content;

intercepting a DNS response from the DNS server, the DNS response including an IP address of the first server; and

caching the IP address of the first server in a manner for associating the IP address of the first server with the cached URI or URL of the requested content.

8. The method of claim 1, further comprising:

detecting a request to switch from the first network interface to the second network interface;

propagating, toward a domain name server (DNS), a DNS request comprising a uniform resource identifier (URI) or uniform resource locator (URL) of the requested content;

intercepting a DNS response from the DNS server, the DNS response including an IP address of the second server; and

caching the IP address of the second server in a manner for associating the IP address of the second server with the cached URI or URL of the requested content.

9. The method of claim 1, further comprising:

monitoring outgoing method invocations associated with a supported application layer protocol; and

identifying a uniform resource identifier (URI) or uniform resource locator (URL) associated with an outgoing method invocation and caching an association of the URI or the URL to an Internet Protocol (IP) address of the first server.

10. The method of claim 9, wherein monitoring outgoing method invocations associated with the supported application layer protocol comprises at least one of:

for monitoring performed at a transport layer using a Transmission Control Protocol (TCP), analyzing a first outgoing data packet after a SYN/ACK handshake;

for monitoring performed at a transport layer using a Stream Control Transmission Protocol, analyzing a first outgoing data packet after an INIT handshake;

or

for monitoring performed at a session layer, analyzing a first outgoing data packet after a CONNECT( ) call.

11. The method of claim 9, wherein identifying the URI or URL associated with the outgoing method invocation and caching the association of the URI or the URL to the IP address of the first server comprises:

intercepting a domain name server (DNS) request sent toward a DNS server, the DNS request comprising the URI or the URL of the requested content;

caching the URI or the URL of the requested content;

intercepting a DNS response from the DNS server, the DNS response including an IP address of the first server; and

caching the IP address of the first server in a manner for associating the IP address of the first server with the cached URI or URL of the requested content.

12. The method of claim 1, further comprising:

identifying the second server based on a domain name server (DNS) location service.

13. The method of claim 12, wherein a uniform resource indicator (URI) or a uniform resource locator (URL) used for a DNS request for the DNS location service is derived from at least one of a prior DNS request sent by the host or the first content request message.

14. The method of claim 1, further comprising:

suppressing further delivery of content from the first server.

15. The method of claim 14, wherein Transmission Control Protocol (TCP) is used as a transport mechanism, wherein suppressing further delivery of content from the first server comprises transmitting a TCP RST message toward the first server via the first network interface.

16. The method of claim 1, further comprising:

analyzing a content bearing data stream received via the second network interface of the host to identify further content portions received by the content retrieval application via the second network interface; and

forwarding, toward the content retrieval application, identified content portions not received by the content retrieval application via the first network interface.

17. The method of claim 1, wherein the first and second servers comprise the same server.

18. An apparatus for migrating a content retrieval session associated with a content retrieval application at a host from a first server to a second server, the apparatus comprising:

a processor and a memory communicatively connected to the processor, the processor configured to;

establish a transport connection with the first server using a first network interface associated with a first network;

cache a first content request message transmitted toward the first server via the first network interface;

monitor content received from the first server via the first network interface to determine an amount of content received by the content retrieval application via the first network interface;

establish a transport connection with the second server using a second network interface associated with a second network; and

transmit, toward the second server via the second network interface, a second content request message determined based on the cached first content request message and the determined amount of content received by the content retrieval application via the first network interface, wherein the second content request message comprises information from the cached first content request message and an instruction configured to instruct the second server to omit delivery of the amount of content received by the content retrieval application via the first network interface;

wherein the first network interface and the second network interface are different.

19. A non-transitory computer-readable storage medium storing instructions which, when executed by a computer, cause the computer to perform a method for migrating a content retrieval session associated with a content retrieval application at a host from a first server to a second server, the method comprising:

establishing a transport connection with the first server using a first network interface associated with a first network;

caching a first content request message transmitted toward the first server via the first network interface;

monitoring content received from the first server via the first network interface to determine an amount of content received by the content retrieval application via the first network interface;

establishing a transport connection with the second server using a second network interface associated with a second network; and

transmitting, toward the second server via the second network interface, a second content request message determined based on the cached first content request message and the determined amount of content received by the content retrieval application via the first network interface, wherein the second content request message comprises information from the cached first content request message and an instruction configured to instruct the second server to omit delivery of the amount of content received by the content retrieval application via the first network interface;

wherein the first network interface and the second network interface are different.