ROUTING AND SERVICE PERFORMANCE MANAGEMENT IN AN APPLICATION ACCELERATION ENVIRONMENT

• US 20120179796A1
• Filed: 06/24/2010
• Published: 07/12/2012
• Est. Priority Date: 06/24/2010
• Status: Active Grant

• Current Assignee: Aryaka Networks
• Original Assignee: Aryaka Networks
• Inventors: Nagaraj, Ashwath, Bharadhwaj, Rajeev, Gupta, Ajit
• Granted Patent: US 8,396,954 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 47/193 at the transport layer, e.g. TCP related
• CPC Class Codes: H04L 47/22 Traffic shaping
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/27 Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
• CPC Class Codes: H04L 47/38 by adapting coding or compression rate

Abstract

Disclosed are a system, a method and an apparatus of reduction of routing and service performance management in an application acceleration environment. In one embodiment, a system includes a branch site that includes a branch client. In addition, the system includes a headquarters site that includes a headquarters server. The headquarters site including a headquarters server includes the branch site. The headquarters site is communicatively coupled over a link via transmission media. The link is identified through a link identifier. The headquarters site including a headquarters server also includes the branch client and the headquarters server being communicatively coupled over a network connection via the transmission media. The network connection is identified through a connection identifier. The system also includes a first point of presence (POP) communicatively coupled with the branch site over a first segment of the link.

Claims

1. A system comprising:

a branch site including a branch client;

a headquarters site including a headquarters server;

the branch site and the headquarters site being communicatively coupled over a link via transmission media, the link being identified through a link identifier, and

the branch client and the headquarters server being communicatively coupled over a network connection via the transmission media, the network connection being identified through a connection identifier;

a first point of presence (POP) communicatively coupled with the branch site over a first segment of the link; and

a second POP communicatively coupled with the first POP over a second segment of the link, and communicatively coupled with the headquarters site over a third segment of the link,

the branch site being configured to transmit a packet of the network connection, and associated with the branch client, over the first segment to the first POP, based on the link identifier, the packet encoding the link identifier and the connection identifier,

the first POP being configured to,

select a delivery optimization operation to perform on the packet based on a first POP identifier, the link identifier, and the connection identifier,

perform the delivery optimization operation on the packet based on that identification,

transmit the packet to the second POP over the second segment of the link based on the link identifier, and

the second POP being configured to,

select a further delivery optimization operation to perform on the packet based on a second POP identifier, the link identifier, and the connection identifier,

perform the further delivery optimization operation on the packet based on that identification, and

transmit the packet to the headquarters site over the third segment of the link based on at least one of the link identifier and the connection identifier.

2. The system of claim 1, wherein the branch client and the headquarters server have established the network connection with one another prior to the branch site directing the packet to the first POP over the first segment of the link.

3. The system of claim 2, wherein a set of branch clients of the branch site and a set of headquarters servers of the headquarters site have established a plurality of separate network connections with one another,

wherein the system is configured to direct a plurality of packets, each associated with a different one of the plurality of network connections, simultaneously over at least one of the first segment, the second segment, and the third segment of the link,

wherein the network connection is one of the plurality of separate network connections.

4. The system of claim 2, wherein the branch client and the headquarters server have established the network connection through a transmission control protocol three-way handshake and the connection identifier is encoded in an Internet Protocol header that includes at least one of a source IP address, a destination IP address, a source port identifier, and a destination port identifier.

5. The system of claim 1, wherein the first POP and the second POP each include

an enterprise selection module configured to identify in a memory system an enterprise associated with the packet, based on the link identifier, and

an operation set selection module configured to identify in the memory system a set of delivery optimization operations associated with the packet, based on the identified enterprise and the connection identifier.

6. The system of claim 5, wherein the set of delivery optimization operations associated with the packet includes a data compression function, a data decompression function, a protocol proxy function, an encryption function, and a decryption function.

7. The system of claim 5, wherein the first POP includes an operation selection module configured to

select the delivery optimization operation of the identified set of delivery optimization operations to perform on the packet, based on an association of the first POP identifier with the connection identifier in the memory system, and

a delivery optimization module configured to utilize a processor to perform the selected delivery optimization operation on the packet.

8. The system of claim 5, wherein the second POP includes:

an operation selection module configured to select the delivery optimization operation of the identified set of delivery optimization operations to perform on the packet, based an association of the second POP identifier with the connection identifier in the memory system, and

a delivery optimization module configured to utilize a processor to perform the selected further delivery optimization operation on the packet.

9. The system of claim 5, wherein the branch site is associated with a branch enterprise premise module configured to perform at least one of the set of delivery optimization operations on the packet prior to the branch site transmitting the packet over the first segment to the first POP.

10. The system of claim 5, wherein the headquarters site is associated with a headquarters enterprise premise module configured to perform at least one of the set of delivery optimization operations on the packet subsequent to receiving the packet from the second POP over the second segment.

11. The system of claim 1, including

a set of interconnectors including,

a branch site interconnector associated with the branch site,

a first POP interconnector associated with the first POP,

a second POP interconnector associated with the second POP, and

a headquarters site interconnector associated with the headquarters site, wherein each of the set of interconnectors are configured to perform at least one of a router function and a bridge function,

wherein the first segment is identified through a first segment identifier that identifies at least one of the branch site interconnector and the first POP interconnector, the second segment is identified through a second segment identifier that identifies at least one of the first POP interconnector and the second POP interconnector, and the third segment is identified through a third segment identifier that identifies at least one of the second POP interconnector and the headquarters interconnector.

12. The system of claim 11, wherein the branch site and the headquarters site are associated with an enterprise and the branch site interconnector is not programmable by the enterprise to manipulate an extended header of the packet.

13. The system of claim 12, further comprising:

a database server communicatively coupled with the branch client and configured to;

receive from the branch client, a target destination for the packet, and

provide a unique Internet Protocol (IP) address to the branch client based on the target destination, the unique IP address uniquely encoding the first segment identifier, the link identifier, and the connection identifier,

the branch client being configured to transmit, via the branch site interconnector, the packet to the first POP over the first segment using the first segment identifier.

14. The system of claim 11, wherein the branch site and the headquarters site are associated with an enterprise and the branch site interconnector is programmable by the enterprise to manipulate an extended header of the packet.

15. The system of claim 14, wherein the branch site interconnector is configured to

determine through a memory system that the first segment identifier is associated with the link identifier,

place the link identifier in the extended header of the packet,

place the first segment identifier in another extended header of the packet, and

based on the first segment identifier, transmit the packet over the first segment to the first POP.

16. The system of claim 11, wherein the first POP interconnector is configured to

determine through a memory system that the second segment identifier is associated with the link identifier,

place the link identifier in an extended header of the packet,

place the second segment identifier in another extended header of the packet, and

based on the second segment identifier, transmit the packet over the second segment to the second POP.

17. The system of claim 11, wherein the branch site and the headquarters site are associated with an enterprise and the headquarters site is associated with the headquarters site interconnector that is not programmable by the enterprise to manipulate an extended header of the packet.

18. The system of claim 17, wherein the packet is a request packet, the connection identifier includes a headquarters server identifier and a branch client identifier, and the second POP interconnector is configured to

substitute the branch client identifier with

the third segment identifier, and

a modified branch client identifier, wherein the connection identifier reflects the headquarters server identifier as a destination, and reflects the third segment identifier and the modified branch client identifier as a source, and

cause the second POP interconnector to transmit the request packet to the headquarters site over the third segment,

the headquarters site being configured to

provide the request packet to the headquarters server using the headquarters server identifier as the destination,

designate the third segment identifier and the modified branch client identifier as the destination, and the headquarters server identifier as the source, and

subsequent to providing the request packet to the headquarters server,

transmit a return packet that is associated with the request packet over the third segment to the second POP based on the third segment identifier.

19. The system of claim 18, wherein responsive to receiving the return packet from the headquarters site, the second POP is configured to

access a memory system to associate the modified branch client identifier with the branch client identifier,

access the memory system to associate the branch client identifier and the headquarters server identifier with the connection identifier,

access the memory system to associate the connection identifier with the link identifier;

access the memory system to associate the link identifier with the second segment identifier, and

transmit the return packet to the first POP based on the second segment identifier.

20. The system of claim 11, wherein the branch site and the headquarters site are associated with an enterprise and the headquarters site is associated with the headquarters site interconnector that is programmable by the enterprise to manipulate an extended header of the packet.

21. The system of claim 20, wherein the second POP interconnector is configured to

determine through a memory system that the third segment identifier is associated with the link identifier,

place the link identifier in the extended header of the packet,

place the third segment identifier in another extended header of the packet, and

based on the third segment identifier, transmit the packet over the third segment to the headquarters site.

22. The system of claim 21, wherein at least one of the extended header and the other extended header reflect at least one of IPSec, MPLS, VLAN, IP, and GRE access protocols.

23. The system of claim 11, wherein the first POP interconnector is one of a plurality of interconnectors that are communicatively coupled with the branch site interconnector and accessible by the branch site interconnector, wherein the branch site interconnector is configured to select the first POP interconnector from the plurality of interconnectors based on the first segment identifier.

24. The system of claim 11, wherein the second POP interconnector is one of a plurality of POP interconnectors communicatively coupled with the first POP interconnector over a plurality of segments, wherein the first POP interconnector selects the second POP interconnector from the plurality of POP interconnectors based on the second segment identifier.

25. The system of claim 11, wherein the headquarters site interconnector is one of a plurality of headquarters site interconnectors that are communicatively coupled with the second POP interconnector over a plurality of segments, wherein the second POP interconnector is configured to select the headquarters site interconnector from the plurality of headquarters site interconnectors, based on the third segment identifier.

26. The system of claim 11, wherein the packet is a request packet, and the headquarters site interconnector is configured to

receive a return packet associated with the request packet from the headquarters server, and

determine through a memory system of the headquarters site that the link identifier encoded in the return packet is associated with the third segment identifier, and

transmit the return packet from the headquarters site to the second POP based on the third segment identifier,

the second POP interconnector is configured to

determine through a memory system of the second POP that the link identifier encoded in the return packet is associated with the second segment identifier, and

transmit the return packet from the second POP to the first POP, based on the second segment identifier,

the first POP interconnector is configured to,

determine through a memory system of the first POP that the link identifier encoded in the return packet is associated with the first segment identifier, and

transmit the return packet from the first POP to the branch site interconnector, based on the first segment identifier.

27. A system comprising:

a branch site including a branch client;

a headquarters site including a headquarters server;

the branch site and the headquarters site being communicatively coupled over a link via transmission media, the link being identified through a link identifier, and

the branch client and the headquarters server being communicatively coupled over a network connection via the transmission media, the network connection being identified through a connection identifier;

a first point of presence (POP) communicatively coupled with the branch site over a first segment of the link; and

a second POP communicatively coupled with the first POP over a second segment of the link, and communicatively coupled with the headquarters site over a third segment of the link,

the branch site being configured to forward a packet of the network connection, and associated with the branch client, over the first segment to the first POP, based on the link identifier, the packet encoding the link identifier and the connection identifier,

the first POP being configured to,

perform a delivery optimization operation on the packet,

determine whether to forward the packet to the second POP, and

based on determining that that the packet is to be forwarded to the second POP, forward the packet to the second POP over the second segment of the link based on the link identifier, and

the second POP being configured to,

perform a further delivery optimization operation on the packet,

determine whether to forward the packet to the headquarters site, and

based on determining that that the packet is to be forwarded to the headquarters site, forward the packet to the headquarters site over the third segment of the link based on at least one of the link identifier and the connection identifier.

28. The system of claim 27, including

a set of interconnectors including,

a branch site interconnector associated with the branch site,

a first POP interconnector associated with the first POP,

a second POP interconnector associated with the second POP, and

a headquarters site interconnector associated with the headquarters site, wherein each of the set of interconnectors are configured to perform at least one of a router function and a bridge function,

wherein the first segment is identified through a first segment identifier that identifies at least one of the branch site interconnector and the first POP interconnector, the second segment is identified through a second segment identifier that identifies at least one of the first POP interconnector and the second POP interconnector, and the third segment is identified through a third segment identifier that identifies at least one of the second POP interconnector and the headquarters interconnector.

29. The system of claim 28, wherein the link identifier is configured to be encoded in an inner extended header of the packet, and at least one of the first segment identifier, the second segment identifier, and the third segment identifier are configured to be encoded in outer extended header of the packet.

30. The system of claim 29, wherein the branch site interconnector is configured to encode the first segment identifier in a source field and a destination field of the outer extended header of the packet that the branch site is configured to forward to the first POP, the first segment identifier including a branch site interconnector identifier and a first POP interconnector identifier,

wherein based on the first POP determining that the packet is to be returned to the branch site, the first POP interconnector is configured to,

place the first POP interconnector identifier in the in the source field of the outer extended header,

place the branch site interconnector identifier in the destination field of the outer extended header, and

return the packet to the branch site over the first segment based on the branch site interconnector identifier in the destination field of the outer extended header.

31. The system of claim 29, wherein the first POP interconnector is configured to encode the second segment identifier in a source field and a destination field of the outer extended header of the packet that the first POP is configured to forward to the second POP, the second segment identifier including a second POP interconnector identifier and a headquarters site interconnector identifier,

wherein based on the second POP determining that the packet is to be returned to the first POP, the second POP interconnector is configured to,

place the second POP interconnector identifier in the in the source field of the outer extended header,

place a first POP interconnector identifier in the destination field of the outer extended header, and

return the packet to the first POP interconnector over the second segment based on the first POP interconnector identifier in the destination field of the outer extended header.

32. The system of claim 27, wherein the delivery optimization operation and the further delivery optimization operation are of a set of delivery optimization operations including a data compression function, a data decompression function, a protocol proxy function, an encryption function, and a decryption function.

33. The system of claim 32, wherein the branch site is associated with a branch enterprise premise module configured to perform at least one of the set of delivery optimization operations on the packet, and

wherein the branch enterprise premise module is further configured to:

determine whether to return the packet to the branch client prior to the branch site forwarding the packet over the first segment to the first POP, and

return the packet to the branch client based on determining that the packet is to be returned to the branch client.

34. The system of claim 32, wherein the headquarters site is associated with a headquarters enterprise premise module configured to perform at least one of the set of delivery optimization operations on the packet subsequent to receiving the packet from the second POP over the second segment.

35. A method performed a point of presence (POP), the method comprising:

acquiring a packet associated with a network connection, the packet travelling over a segment of a plurality of segments that form a link between a requesting site and a providing site, the packet including a link identifier that identifies the link, and a connection identifier that identifies the network connection;

selecting a set of delivery optimization operations to associate with the packet based on the link identifier and the connection identifier;

selecting a delivery optimization operation from the selected set of delivery optimization operations based on a POP identifier that identifies the POP, the link identifier, and the connection identifier;

processing the packet to perform the selected delivery optimization operation;

determining whether a further delivery optimization operation is to be performed prior to forwarding the processed packet to a delivery optimization operation provider; and

forwarding the packet to the delivery optimization operation provider over a further segment of the plurality of segments, based on determining that the further delivery optimization operation is to be performed.

36. The method of claim 35, wherein the delivery optimization operation provider includes a second POP, wherein the further delivery optimization operation is to be selected based on a second POP identifier, the link identifier and the connection identifier.

37. The method of claim 35, wherein the delivery optimization operation provider includes a provider enterprise premise equipment in a provider site, wherein the further delivery optimization operation is to be selected based on a headquarters site identifier, the link identifier and the connection identifier.

38. The method of claim 35, includes

determining that the further delivery optimization operation is not to be performed,

determining that the packet is to be returned to a source of the packet, and

returning the packet towards the source of the packet over the segment based on the determining that the further delivery optimization operation is not to be performed and the determining that the packet is to be returned to the source of the packet.

39. The method of claim 38, wherein the determining that the further delivery optimization operation is to be performed includes accessing a determination value stored in a memory system, wherein the determination value is associated with at least one of a bandwidth threshold value and a throughput threshold value related to the further segment.

40. The method of claim 35, wherein the selecting of the set of delivery optimization operations includes,

determining that the link identifier is associated with an enterprise identified through an enterprise identifier in a memory system, and determining that the enterprise identifier and the connection identifier are associated with the set of delivery optimization operations in the memory system, and

the selecting of the delivery optimization operation from the set of delivery optimization operations includes,

determining that the delivery optimization operation of the set of delivery optimization operations is associated with the connection identifier and the POP identifier in the memory system.

41. The method of claim 40, wherein the association between the link identifier, the connection identifier, and the set of delivery optimization operations is pre-defined based on a user preference.

42. The method of claim 40, wherein the association between the connection identifier and the delivery optimization operation of the set of delivery optimization operations is pre-defined based on a user configuration of the POP.

43. The method of claim 40, wherein the delivery optimization operation of the set of delivery optimization operations is selected from the group of delivery optimization operations consisting of data compression, data decompression, protocol proxy, authentication, encryption, and decryption.

44. The method of claim 35, wherein a requesting client of the requesting site and a providing server of the providing site established the network connection using Internet protocol.

45. The method of claim 35, wherein the connection identifier is encoded in a inner header of the packet and includes at least one of a source Internet protocol (IP) address, a destination IP address, a source port identifier, and a destination port identifier, and

the link identifier is encoded in an extended header of the packet and reflects at least one of generic routing encapsulation, multiprotocol label switching, virtual private local area network services, and Internet Protocol (IP) in IP.

46. A machine-readable medium including instructions that when executed by a machine, cause the machine to perform the method of claim 35.