Methods and systems for routing requests using edge network elements

• US 20050198366A1
• Filed: 12/19/2002
• Published: 09/08/2005
• Est. Priority Date: 12/19/2002
• Status: Active Grant

• Current Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Original Assignee: Bellsouth Intellectual Property Corporation (AT&T, Inc.)
• Inventors: Littrell, Kim, Kreiner, Barrett, Perrella, Ron, Menon, Jai
• Granted Patent: US 7,487,224 B2
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 45/42 Centralised routing

Abstract

The present invention utilizes central offices, located on the edge of a network to route requests along the edge of the network. Once an edge client receives a request for information, the edge client makes a determination as to whether the edge client can provide the information requested. If the edge client cannot provide the information requested, then the edge client determines whether a routing instruction applies which specifies a second edge client. If the routing instruction applies, then the request is routed to the second edge client.

Claims

1. A method for routing a request by an edge client, comprising:

receiving the request;

in response to receiving the request, determining whether the edge client can satisfy the request;

if the edge client can satisfy the request, then providing a satisfied request;

if the edge client cannot satisfy the request, then determining whether a routing instruction applies which identifies a second edge client; and

if the routing instruction applies, then routing the request to the second edge client.

2. The method of claim 1, wherein determining whether a routing instruction applies, comprises:

comparing a routing parameter associated with the request to a routing parameter associated with the routing instruction.

3. The method of claim 2, wherein the routing parameter associated with the request specifies a subject.

4. The method of claim 1, wherein determining whether a routing instruction applies, comprises:

comparing a routing parameter associated with the request to a routing parameter associated with a network condition.

5. The method of claim 4, wherein the routing parameter associated with the network condition specifies a time interval.

6. The method of claim 4, wherein the routing parameter associated with the network condition specifies a load.

7. The method of claim 1, wherein the edge client provides central office functions.

8. The method of claim 1, further comprising:

if the routing instruction does not apply, then routing the request according to a default routing instruction.

9. The method of claim 8, wherein the default routing instruction identifies a network core.

10. The method of claim 8, wherein the default routing instruction identifies a nearby edge client.

11. A method for routing a request by an edge client, comprising:

receiving the request;

in response to receiving the request, determining whether the edge client can satisfy a portion of the request;

if the edge client can satisfy the portion of the request, then obtaining a satisfied portion of the request; and

routing a remaining portion of the request to a second edge client.

12. The method of claim 11, further comprising:

receiving a remaining satisfied portion of the request; and

combining the satisfied portion of the request and the remaining satisfied portion of the request and providing a satisfied request to a requester.

13. The method of claim 11, further comprising:

in response to obtaining a satisfied portion of a request, providing the satisfied portion of the request to a requester;

receiving a remaining satisfied portion of the request; and

in response to receiving the remaining satisfied portion of the request, providing the remaining satisfied portion of the request to the requestor.

14. A network system, comprising:

a plurality of edge network clients, each edge network client configured as a central office network having a central office server, a central office data store and a central office router and each edge network client connected to at least one of the other edge network clients, each edge network client operable to receive a request, examine the request, determine whether a routing instruction applies which identifies another edge network client, and route the request to the other edge network client; and

a network core having a core server and a data source connected to at least one edge network client.

15. The system of claim 14, wherein the edge network client examines the request using the central office router to examine a header associated with the request.

16. The system of claim 14, wherein a routing table is associated with the central office router and the routing table includes a plurality of routing instructions based on routing parameters that correspond to network conditions.

17. The system of claim 14, wherein a routing table is associated with the central office router and the routing table includes a plurality of routing instructions based on routing parameters that correspond to the request.

18. The system of claim 14, wherein the edge network client is further operative to determine whether the edge network client can satisfy a portion of the request and if the edge network client can satisfy a portion of the request, then routing an unsatisfied portion of the request.

19. The system of claim 18, wherein the edge network client can satisfy the portion of the request if the portion of the request corresponds to information stored in the central office data store.