System for network addressing

• US 6,836,806 B1
• Filed: 09/18/2000
• Issued: 12/28/2004
• Est. Priority Date: 06/01/2000
• Status: Expired due to Term

• Current Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Original Assignee: Aerocast, Inc.
• Inventors: Raciborski, Nathan F., Thompson, Mark R.
• Primary Examiner(s): Jean, Frantz B.
• Application Number:
  US09/664,179
• Time in Patent Office: 1,562 Days
• Field of Search: 709/245, 709/219, 709/230-232, 709/238-244
• US Class Current: 709/245
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 2216/09 Obsolescence
• CPC Class Codes: H04L 2101/33 containing protocol addresses or telephone numbers
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 2101/659 Internet protocol version 6 [IPv6] addresses
• CPC Class Codes: H04L 2101/663 Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
• CPC Class Codes: H04L 45/30 Routing of multiclass traffic
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 61/5069 for group communication, multicast communication or broadcast communication
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/611 for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/101 : based on network conditions
• CPC Class Codes: H04L 67/1029 : using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/14 : Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/63 : Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/24 : Negotiation of communication capabilities
• CPC Class Codes: H04L 69/32 : Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]

Abstract

A system relating to distributing content objects to a client computer. One system includes a server, a first content cache, a second content cache and a preference list. The first server is at a first address and the second server is at a second address. The server includes a content object that is copied to the first and second content caches. Originating from a client computer, the preference list includes at least one of the first and second addresses. A multiple address system provides for metadata to be combined with a first location for an object. A port identifier can be added to the address to allow a desired port to be referenced. The port identifier allows a predetermined port to be addressed in response to an inquiry.

Claims

1. A method of providing an address, said method comprising:

providing a requesting device coupled to a network;

providing an address, said address comprising a protocol identifier;

providing a port identifier, said port identifier operable to identify a port on said requesting device;

including said port identifier as part of said address;

transmitting said address from said requesting device onto said network;

receiving said address at an intermediate device; and

addressing a data provider device while including said port identifier as part of an address string.

2. The method as described in claim 1 and further comprising:

transmitting a message from said data provider to the port of said requesting device identified by said port identifier.

3. A method of providing an address, comprising:

providing a protocol identifier;

providing an IP identifier;

providing a requesting device identifier;

providing a requesting device port identifier;

coupling said protocol identifier, said IP identifier, said requesting device identifier, and said requesting device port identifier as an address string.

4. The method as described in claim 3 and further comprising:

providing a file identifier.

5. The method as described in claim 4 wherein said coupling further comprises:

coupling said protocol identifier with said IP identifier, said requesting device identifier, said requesting device port identifier, and said file identifier as an address string.

6. The method as described in claim 5 and further comprising:

organizing said address structure so that said port identifier is adjacent said requesting device identifier.

7. A data structure for addressing a device on a network, said data structure comprising:

a protocol identifier field;

an internet protocol identifier field for use in addressing an intermediary device;

a requesting device identifier field;

a requesting device port identifier field; and

wherein said protocol identifier field, said internet protocol identifier field, said requesting device identifier field, and said requesting device port identifier field are combined as part of an address string.

8. The data structure as described in claim 7 wherein said internet protocol identifier field is located between said protocol identifier field and said requesting device identifier field.

9. The data structure as described in claim 7 wherein said requesting device identifier field is located between said protocol identifier field and said internet protocol identifier field.

10. The data structure as described in claim 7 wherein said requesting device port identifier field is located adjacent said requesting device identifier field.

11. The data structure as described in claim 7 and further comprising a file identifier field for identifying a file stored on a data provider device.

12. A computer data signal comprising:

a protocol identifier segment;

an internet protocol identifier segment for use in addressing an intermediary device;

a requesting device identifier segment;

a requesting device port identifier segment;

wherein said protocol identifier segment, said internet protocol identifier segment;

said requesting device identifier segment, and said requesting device port identifier segment are configured as part of an address string.

13. The computer data signal as described in claim 12 and further comprising:

a file identifier segment for identifying a file stored on a data provider device.

14. The computer data signal as described in claim 12 wherein said requesting device port identifier segment is operable for designating a port on a requesting device from which a request for data originated.

15. An apparatus for use in a network, said apparatus comprising:

a computer operable to provide an address for addressing a device on said network;

code for use by said computer operable to provide a protocol identifier field;

code for use by said computer operable to provide an internet protocol identifier field for use in addressing an intermediary device;

code for use by said computer operable to provide a requesting device identifier field;

code for use by said computer operable to provide a requesting device port identifier field;

code for use by said computer operable to configure said protocol identifier field, said internet protocol identifier field, said requesting device identifier field, and said requesting device port identifier field as a single address.

16. The apparatus as described in claim 15 and further comprising:

code for use by said computer operable to provide a file identifier field.

17. The apparatus as described in claim 16 wherein said code for use by said computer operable to configure said protocol identifier field, said internet protocol identifier field, said requesting device identifier field, and said requesting device port identifier field as a single address comprises:

code for use by said computer operable to configure said protocol identifier field, said internet protocol identifier field, said requesting device identifier field, said requesting device port identifier field, and said file identifier field as a single address.