Differentiated content and application delivery via internet

• US 6,976,090 B2
• Filed: 02/16/2001
• Issued: 12/13/2005
• Est. Priority Date: 04/20/2000
• Status: Expired due to Fees

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Actona Technologies Limited (Cisco Systems, Inc.)
• Inventors: Ben-Shaul, Israel, Lev-Ran, Itai, Unger, Oren, Cidon, Israel, Kessler, Ilan
• Primary Examiner(s): Winder, Patrice
• Assistant Examiner(s): LESNIEWSKI, VICTOR D
• Application Number:
  US09/785,977
• Publication Number:
  US 20020010798A1
• Time in Patent Office: 1,761 Days
• Field of Search: 709201-203, 709217-219, 709223-226, 709245-247
• US Class Current: 709/246
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• 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/1021 based on client or server locations
• CPC Class Codes: H04L 67/1023 based on a hash applied to IP addresses or costs
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal

Abstract

A technique for centralized and differentiated content and application delivery system allows content providers to directly control the delivery of content based on regional and temporal preferences, client identity and content priority. A scalable system is provided in an extensible framework for edge services, employing a combination of a flexible profile definition language and an open edge server architecture in order to add new and unforeseen services on demand. In one or more edge servers content providers are allocated dedicated resources, which are not affected by the demand or the delivery characteristics of other content providers. Each content provider can differentiate different local delivery resources within its global allocation. Since the per-site resources are guaranteed, intra-site differentiation can be guaranteed. Administrative resources are provided to dynamically adjust service policies of the edge servers.

Claims

1. A content and application delivery system comprising:

an origin web site having an origin web server, said origin web server having a first memory for storing a first version of a web content;

an edge server disposed in an external domain name zone communicating via a data network with said origin web server and a policy control server, said data network comprising a regional DNS server;

said edge server having a second memory for storing a second version of said web content and deriving said second version from said origin web server according to directives of a service policy that resides at said policy control server, said edge server downloading said directives of said service policy from said policy control server via said data network;

an edge DNS server linked to said regional DNS server, said edge DNS server being configured as an authoritative DNS server for said external domain name zone, said edge DNS server further being configured to cooperate with said regional DNS server to cause a request of a user for a URL within said origin web site requiring a DNS address resolution by said regional DNS server to be resolved so as to redirect said request to said edge server and to entirely avoid an access of said origin web site by said user,

wherein responsively to said request a third version of said web content is provided to the user from said edge server, said third version being derived from said second version in accordance with said directives of said service policy.

2. The system according to claim 1, wherein said policy control server is said origin web server.

3. The system according to claim 1, wherein said directives of said service policy are specified using an XML based language.

4. The system according to claim 3, wherein said directives of said service policy include a description of resources of said origin web site.

5. The system of claim 4 wherein said description of resources is specified using a resource definition framework, said resource definition framework having extensions comprising protocol, type, size, encoding convention, creation time, expiration time, keyword, target groups, an alternate URL for fetching said resources, and a location of a code for creating a dynamic resource;

wherein said description of resources includes at least one of said extensions.

6. The system according to claim 4 wherein said directives of said service policy include a description of users at a target site.

7. The system of claim 1 wherein communication between said edge server and at least one of said policy control server and said origin web server is effected using an http protocol or an https protocol.

8. The system of claim 1, wherein said origin web site comprises a plurality of origin web sites, and said first version is distributed in said plurality of origin web sites, defining thereby a distributed first version, said second version being derived from said distributed first version.

9. The system of claim 1 wherein said policy control server comprises a plurality of web servers.

10. The system of claim 9, wherein said web servers are said origin web server and said edge server being located at a third party site.

11. The system of claim 1, wherein said directives comprise a description of an edge server group associated with said origin web site.

12. The system of claim 11, wherein said description of an edge server group includes information concerning at least one of an organization type, geographical region, language, business relation to said origin web site, edge server hardware capabilities, edge server software capabilities, edge server security specifications, internet location and internet connection speed of members of said edge server group.

13. The system of claim 1, wherein said second version is derived from said first version by the steps of:

selecting resources from said first version according to predetermined criteria comprising at least one of a resource URL, time of resource generation, length, keyword list, target groups, data format, and key;

transforming a selected resource in said second memory responsive to said directives, wherein said directives comprise a description of an edge server group associated with said origin web site to define a transformed selected resource; and

storing said transformed selected resource in said second memory.

14. The system according to claim 13, wherein said second memory comprises a cache memory.

15. The system according to claim 13, wherein said predetermined criteria comprise a presence of updated resources in said first version that are absent in said second version.

16. The system according to claim 1, wherein said service policy differentiates a resource of said first version from a resource of said second version according to an attribute of said edge server and an attribute of at least one of said first version and said second version.

17. The system according to claim 16, wherein said attribute comprises at least one of a caching priority, caching validation, a caching invalidation, preposition at a predetermined time and preposition upon an occurrence of a predetermined event.

18. The system according to claim 1, wherein said service policy differentiates a resource of said second version from a resource in said third version according to at least one of attribute of the user, attribute of the edge server, request time and attribute of the resource.

19. The system according to claim 1, wherein one of said directives of said service policy instructs said edge server to redirect said request of said user to another web resource.

20. The system according to claim 19, wherein said another web resource is located at said origin web site.

21. The system according to claim 19, wherein said another web resource is external to said origin web site.

22. The system according to claim 19, wherein said request is redirected by sending an http redirect instruction from said edge server to said user.

23. The system according to claim 19, wherein said request is redirected to another resource by said edge server by modifying a URL portion of said request and loading the resource from the origin site.

24. The system according to claim 19, wherein said request is redirected according to an attribute of the user.

25. The system according to claim 1, wherein at least two of said first version, said second version, and said third version are identical.

26. The system according to claim 1, wherein a group of resources of said first version is stored in a compressed form, and a corresponding group of resources of said second version is uncompressed by said edge server according to said directives.

27. The system according to claim 26, wherein said group of resources of said first version is stored in a packed form, and said corresponding group of resources of said second version is unpacked by said edge server according to said directives.

28. The system according to claim 1, wherein a resource of said first version is in an encrypted form, and a corresponding resource of said second version is decrypted by said edge server according to said directives.

29. The system according to claim 1, wherein a resource of said first version is communicated by a first protocol to form a resource of said second version, wherein said resource of said second version is communicated by a second protocol to form a resource of said third version.

30. The system according to claim 29, wherein said first protocol is file transfer protocol and said second protocol is http.

31. The system according to claim 29, wherein said first protocol is identical to said second protocol, wherein parameters of said first protocol differ from parameters of said second protocol.

32. The system according to claim 1, wherein a resource at said URL has an action defined therein, and said edge server performs said action.

33. The system according to claim 32, wherein said action comprises execution of an application.

34. The system according to claim 33, wherein said application is a web form processing application;

wherein in a first step said edge server communicates a form to be completed by the user; and

in a second step parameters of said form are transmitted from the user to said edge server.

35. The system according to claim 33, wherein said application is a user password processing application;

wherein in a first step said edge server triggers a password template to be filled by the user; and

in a second step form parameters of said password template are transmitted from the user to said edge server.

36. The system according to claim 33, wherein instructions of said application cause said edge server to identify an attribute of said user that is included in said request and to return resources in said second memory of said edge server that are associated with a said URL of said request and said attribute of said user.

37. The system according to claim 36, wherein said attribute is identified in a request header having a cookie, and said resources are defined in said directives of said service policy, wherein said directives are stored in said edge server.

38. The system according to claim 33, wherein said application is a user password processing application;

wherein said edge server forwards said request to said origin web server and delivers a user name and a user password to said origin web server;

wherein responsive to said user name and said user password said resource is transmitted by said origin web server to said edge server.

39. The system according to claim 38, wherein said resource is held in a cache by said edge server.

40. The system according to claim 33, wherein said application is a web common gateway interface extension or a Java servlet.

41. The system according to claim 1 wherein the user is a member of a group, and responsive to said request said edge server authenticates a membership of the user in said group.

42. The system according to claim 1, wherein said edge server is in communication with an external web server via said data network, and a portion of said second version is obtained from said external web server according to said service policy.

43. The system according to claim 1, wherein a resource at said URL is received by said edge server from said origin web server and stored therein, wherein said resource is modified prior to being stored in said edge server responsive to attributes of said edge server, said user, and said resource that are specified in said directives of said service policy.

44. The system according to claim 43, wherein said resource is modified by replacement thereof with a second resource that is local to said edge server.

45. The system according to claim 43, wherein said resource is modified by combination thereof with a second resource that is local to said edge server.

46. The system according to claim 43, wherein said resource is a web page that is modified by an operation consisting of at least one of frame insertion, textual or graphic insertion, html code insertion, link modification, embedded object modification, and adaptation of said web page to requirements of a browser.

47. The system according to claim 46, wherein a first URL in an embedded link of said web page is modified to define a second URL having a domain name value such that a routing of said request using said second URL is directed to said edge server.

48. The system according to claim 1, wherein said request is modified according to edge server, user and resource attributes that are specified in said directives.

49. The system according to claim 48, wherein said request is modified by an operation consisting of at least one of an addition of user information to an http header of said request, adding a cookie to said request, modifying said URL of said request, modifying form content of said URL, modifying a body of said request, and adding password information to said URL.

50. The system according to claim 48 wherein a resource at said URL comprises a first URL, and said request is modified by an operation comprising modifying said first URL to define a second URL having a domain name value such that a routing of said request using said second URL omits said edge server.

51. The system according to claim 48, wherein a resource at said URL comprises a first URL, wherein in a first operation said first URL is modified to define a second URL having a domain name value such that a routing of said request using said second URL is directed to said edge server, and in a second operation said second URL is modified to define a third URL having a domain name value such that a routing of said request using said third URL omits said edge server.

52. The system according to claim 1, wherein said second version is obtained by said edge server from said origin web server according to a modification of said URL, said modification designating a portion of said first version in said origin web server.