Network architecture supports hosting and content distribution on a global scale. The architecture allows a Content Provider to replicate and serve its most popular content at an unlimited number of points throughout the world. The inventive framework comprises a set of servers operating in a distributed manner. The actual content to be served is preferably supported on a set of hosting servers (sometimes referred to as ghost servers). This content comprises HTML page objects that, conventionally, are served from a Content Provider site. A base HTML document portion of a Web page is served from the Content Provider's site while one or more embedded objects for the page are served from the hosting servers, preferably, those hosting servers near the client machine. By serving the base HTML document from the Content Provider's site, the Content Provider maintains control over the content.

Global hosting system

Resource requests made by clients of origin servers in a network are intercepted by reflector mechanisms and selectively reflected to other servers called repeaters. The reflectors select a best repeater from a set of possible repeaters and redirect the client to the selected best repeater. The client then makes the request of the selected best repeater. The resource is possibly rewritten to replace at least some of the resource identifiers contained therein with modified resource identifiers designating the repeater instead of the origin server.

Optimized network resource location

An architecture and methodology for designing, deploying, and managing a distributed application onto a distributed computing system is described.

Architecture for distributed computing system and automated design, deployment, and management of distributed applications

A system and method in a building or vehicle for an actuator operation in response to a sensor according to a control logic, the system comprising a router or a gateway communicating with a device associated with the sensor and a device associated with the actuator over in-building or in-vehicle networks, and an external Internet-connected control server associated with the control logic implementing a PID closed linear control loop and communicating with the router over external network for controlling the in-building or in-vehicle phenomenon. The sensor may be a microphone or a camera, and the system may include voice or image processing as part of the control logic. A redundancy is used by using multiple sensors or actuators, or by using multiple data paths over the building or vehicle internal or external communication. The networks may be wired or wireless, and may be BAN, PAN, LAN, WAN, or home networks.

System and method for server based control

The Internet Protocol.

A client-server architecture includes a plurality of clients and a plurality of servers. Information resources are replicated among the servers. According to one aspect, the invention includes an intermediary device called a “depot” sitting transparently between a client and a pool of servers which have the replicated information resources. The depot dynamically distributes multiple sessions contained in a client request among the servers. This architecture realizes a good granular scaleability of servers, and improved server throughput with a good response time. Multiple depots also realize robustness.

A scaleable web server and method of efficiently managing multiple servers

This memo defines a Time Sliding Window Three Colour Marker (TSWTCM), which can be used as a component in a Diff-Serv traffic conditioner [RFC2475, RFC2474]. The marker is intended to mark packets that will be treated by the Assured Forwarding (AF) Per Hop Behaviour (PHB) [AFPHB] in downstream routers. The TSWTCM meters a traffic stream and marks packets to be either green, yellow or red based on the measured throughput relative to two specified rates: Committed Target Rate (CTR) and Peak Target Rate (PTR).

/pdf/a-time-sliding-window-three-colour-marker-tswtcm-1k2vdkix2m.pdf

A Time Sliding Window Three Colour Marker (TSWTCM)

A system and method for transmitting data in a data communications network, using a transmission control protocol, to provide reduced acknowledgment control traffic, error recovery and congestion control. A communications link is established between a transmitter and a receiver. Setting the communications link includes setting a network congestion window to an initial length. A sequence, or stream, of data packets is sent from the transmitter to the receiver. The receiver detects any missing packets, by examining the sequence numbers of the incoming packets, and sends negative acknowledgments, generally no more than four, to the transmitter identifying the missing data packet. When the transmitter receives a negative acknowledgment, it decreases the length of the congestion window, and re-transmits the missing packet. Detection and use of round-trip time, re-transmission time-out are provided.

System and method for a negative acknowledgement-based transmission control protocol

Much industry attention has been focused on providing differentiated levels of service to users on IP networks One such proposal is the RIO scheme proposed by Clark (see ACM Transactions on Networking, 1998 ) RIO is an extension of the RED algorithm that relies on a differentiated drop treatment during congestion to cause different levels of service The end result of differentiated dropping of packets during congestion is differentiated throughput rates for end-users The IETF's Diffserv Working Group has recently standardized a PHB (per hop behaviour) that is based on a differentiated drop scheme-assured forwarding (AF) This paper raises issues with providing bandwidth assurance for TCP flows in a RIO-enabled differentiated services network The main contribution is a detailed experimental study of five different factors that impact throughput assurances for TCP and UDP flows in such a network Our study demonstrates that these factors can cause different throughput rates for end-users in spite of having contracted identical service agreements

/pdf/bandwidth-assurance-issues-for-tcp-flows-in-a-differentiated-4juxovj7ef.pdf

Bandwidth assurance issues for TCP flows in a differentiated services network

The present invention defines a system and methods for distributed RSVP-TE (resource reservation protocol-traffic engineering) hitless graceful restart for a MPLS (multi-protocol label switching) network. The system comprises a plurality of ingress and egress cards, each card having an MPLS control plane forwarding table for reverse and forward traffic outgoing and incoming labels for LSPs (Label Switched Paths) in the MPLS network; the cards having data planes, each card data plane having said forwarding table stored thereon; and a means for providing messaging between the ingress card MPLS control plane, ingress card data plane, egress card MPLS control plane, and egress card data plane. The methods of the embodiments of this invention do not require hitless graceful restart in telecommunications networks with no requirement for GMPLS stack and therefore can be used in both traditional and generalized MPLS networks. The system and methods for distributed RSVP-TE hitless graceful restart for a MPLS network do not require any new hardware and software resources.

System and method for distributed resource reservation protocol-traffic engineering (RSVP-TE) hitless restart in multi-protocol label switching (MPLS) network

Biswajit Nandy

Papers

A scaleable web server and method of efficiently managing multiple servers

A Time Sliding Window Three Colour Marker (TSWTCM)

System and method for a negative acknowledgement-based transmission control protocol

Bandwidth assurance issues for TCP flows in a differentiated services network

System and method for distributed resource reservation protocol-traffic engineering (RSVP-TE) hitless restart in multi-protocol label switching (MPLS) network