System, method, and data structure for multimedia communications

• US 20030108030A1
• Filed: 01/21/2003
• Published: 06/12/2003
• Est. Priority Date: 01/21/2003
• Status: Abandoned Application

• Current Assignee: Medianet Systems International Incorporated, MPNET International, Inc.
• Original Assignee: MPNET International, Inc.
• Inventors: Gao, Henry
• Application Number:
  US10/333,597
• Publication Number:
  US 20030108030A1
• Time in Patent Office: Days
• US Class Current: 370/351
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 45/10 Routing in connection-oriented networks, e.g. X.25 or ATM
• CPC Class Codes: H04L 45/302 Route determination based on requested QoS
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/66 Layer 2 routing, e.g. in Ethernet based MAN's
• CPC Class Codes: H04L 49/201 Multicast operation; Broadcast operation
• CPC Class Codes: H04L 49/3009 Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 49/351 for local area network [LAN], e.g. Ethernet switches
• CPC Class Codes: H04L 49/602 Multilayer or multiprotocol switching, e.g. IP switching
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1101 Session protocols

Abstract

The invention is based on a highly efficient protocol for the delivery of high-quality multimedia communication services, such as video multicasting, video on demand, real-time interactive video telephony, and high-fidelity audio conferencing over a packet-switched network. The invention addresses the silicon bottleneck problem and enables high-quality multimedia services to be widely used. The invention can be expressed in a variety of ways, including methods, systems, and data structures. One aspect of the invention involves a method in which a packet (10) of multimedia data is forwarded through a plurality of logical links in a connection-oriented, packet-switched network using a datagram address contained in the packet (i.e., datagram address-based routing). The datagram address operates as both a data link layer address and a network layer address.

Claims

1. A method for transmitting data, comprising:

forwarding asynchronously a packet of multimedia data through a plurality of logical links in a connection-oriented, packet-switched network using a datagram address in said packet, wherein

said plurality of logical links forms a transmission path between a source node and a destination node,

prior to said forwarding, a node in said network approves said forwarding based on measured usage of resources along said plurality of logical links,

address information in partial address subfields of said datagram address self-directs said packet through a plurality of top-down logical links, said plurality of top-down logical links being a subset of said plurality of logical links,

said packet remains unchanged as it is transferred along multiple links in said plurality of logical links, and

said datagram address operates as both a data link layer address and a network layer address.

2. The method of claim 1, wherein said forwarding does not use the Internet Protocol.

3. A system for transmitting data, comprising:

a connection-oriented, packet-switched network including a plurality of logical links; and

a plurality of data packets passing asynchronously through said plurality of logical links, each of said packets comprising

a header field including

a datagram address containing a plurality of partial address subfields, wherein address information in said partial address subfields self-directs said packet through a plurality of top-down logical links, said plurality of top-down logical links being a subset of said plurality of logical links, and said datagram address operates as both a data link layer address and a network layer address,

and a payload field containing multimedia data;

wherein said plurality of logical links forms a transmission path between a source node and a destination node,

prior to said passing, a node in said network approves said passing based on measured usage of resources along said plurality of logical links, and

each of said packets remains unchanged as it is transferred along multiple links in said plurality of logical links.

4. The system of claim 3, wherein said packet-switched network does not use the Internet Protocol to pass said plurality of data packets through said plurality of logical links.

5. A data structure for a packet, comprising:

a header field containing a datagram address containing a plurality of partial address subfields, wherein

address information in said partial address subfields self-directs said packet through a plurality of top-down logical links that forms a subset of a plurality of logical links in a connection-oriented, packet-switched network, and

said datagram address operates as both a data link layer address and a network layer address;

and a payload field containing multimedia data;

wherein said plurality of logical links forms a transmission path between a source node and a destination node,

said packet is forwarded asynchronously through said plurality of logical links,

prior to said forwarding, a node in said network approves said forwarding based on measured usage of resources along said plurality of logical links, and

said packet remains unchanged as it is transferred along multiple links in said plurality of logical links.

6. The data structure of claim 5, wherein said packet-switched network does not use the Internet Protocol.

7. A computer readable medium containing executable program instructions for transmitting data through a network, which when executed cause said network to:

forward asynchronously a packet of multimedia data through a plurality of logical links in a connection-oriented, packet-switched network using a datagram address in said packet, wherein

said plurality of logical links forms a transmission path between a source node and a destination node,

prior to said forwarding, a node in said network approves said forwarding based on measured usage of resources along said plurality of logical links,

address information in partial address subfields of said datagram address self-directs said packet through a plurality of top-down logical links, said plurality of top-down logical links being a subset of said plurality of logical links,

said packet remains unchanged as it is transferred along multiple links in said plurality of logical links, and

said datagram address operates as both a data link layer address and a network layer address.

8. The computer readable medium of claim 7, wherein said forwarding does not use the Internet Protocol.

9. A method for transmitting data, comprising:

forwarding a packet of multimedia data through a plurality of logical links in a connection-oriented, packet-switched network using a datagram address in said packet, wherein

address information in partial address subfields of said datagram address self-directs said packet through a plurality of top-down logical links, said plurality of top-down logical links being a subset of said plurality of logical links,

said packet remains unchanged as it is transferred along multiple links in said plurality of logical links, and

said datagram address operates as both a data link layer address and a network layer address.

10. The method of claim 9, wherein said plurality of logical links forms a transmission path between a source node and a destination node.

11. The method of claim 9, wherein said forwarding does not use the Internet Protocol.

12. The method of claim 9, wherein said forwarding occurs at wirespeed.

13. The method of claim 9, wherein said forwarding uses forwarding tables calculated off-line.

14. The method of claim 9, wherein said forwarding does not use real-time routing table calculations.

15. The method of claim 9, wherein said forwarding occurs asynchronously.

16. The method of claim 9, wherein said forwarding is facilitated by information in said datagram address about the type of service that the packet is providing.

17. The method of claim 9, wherein said packet has a length that is different from the length of another packet of multimedia data that is forwarded in said network.

18. The method of claim 9, wherein said packet remains unchanged as it is forwarded along a majority of links in said plurality of logical links.

19. The method of claim 9, wherein said packet has no “

time-to-live”

data.

20. The method of claim 9, wherein said packet is transferred along a majority of links in said plurality of logical links without using routing calculations.

21. The method of claim 9, wherein said multimedia data includes data for telephony.

22. The method of claim 9, wherein said multimedia data includes data for media on demand.

23. The method of claim 9, wherein said multimedia data includes data for multicast.

24. The method of claim 9, wherein said multimedia data includes data for broadcast.

25. The method of claim 9, wherein said multimedia data includes data for transfer.

26. The method of claim 9, wherein said multimedia data is displayed on a user terminal.

27. The method of claim 26, wherein said user terminal is a set top box that provides access to both MediaNetwork Protocol and non-MediaNetwork Protocol networks.

28. The method of claim 26, wherein said user terminal is a teleputer that processes both MediaNetwork Protocol and non-MediaNetwork packets.

29. The method of claim 9, wherein said multimedia data is stored on a home server.

30. The method of claim 9, wherein said multimedia data is stored in a mass storage unit.

31. The method of claim 9, wherein said packet-switched network includes a plurality of non-peer-to-peer user terminals.

32. The method of claim 9, wherein said packet-switched network includes a plurality of non-peer-to-peer middle switches.

33. The method of claim 9, wherein said packet-switched network includes a plurality of non-peer-to-peer home gateways.

34. The method of claim 9, wherein said packet-switched network automatically configures a node when said node is added to said network.

35. The method of claim 34, wherein said automatic configuration includes checking the node identification number.

36. The method of claim 9, wherein said packet-switched network approves said forwarding prior to said forwarding.

37. The method of claim 36, wherein said approval is based on measured usage of resources along said plurality of logical links.

38. The method of claim 37, wherein said approval is on a per-session basis.

39. The method of claim 9, wherein a node in said packet-switched network approves said forwarding prior to said forwarding.

40. The method of claim 39, wherein said approval is based on measured usage of resources along said plurality of logical links.

41. The method of claim 40, wherein said approval is on a per-session basis.

42. The method of claim 9, wherein said packet-switched network includes servers that distribute network information to a plurality of switches in said network.

43. The method of claim 42, wherein said network information includes bandwidth usage for a plurality of switches in said network.

44. The method of claim 42, wherein said network information is distributed using bulletin packets.

45. The method of claim 9, wherein said packet-switched network verifies an account of a paying party prior to forwarding said packet.

46. The method of claim 9, wherein said packet-switched network measures, collects, and stores usage data.

47. The method of claim 46, wherein said usage data includes accounting data.

48. The method of claim 9, wherein said packet-switched network regulates the flow of packets.

49. The method of claim 48, wherein said network regulates the flow of packets by adding packets.

50. The method of claim 48, wherein said network regulates the flow of packets by holding back packets.

51. The method of claim 9, wherein said packet-switched network contains a server group that includes a plurality of server systems, wherein each server system performs a specialized task.

52. The method of claim 9, wherein said packet-switched network filters said packet based on a set of filter criteria.

53. The method of claim 52, wherein said filter criteria are established on a per session basis.

54. The method of claim 52, wherein said filter criteria include a source address in said packet.

55. The method of claim 52, wherein said filter criteria include a destination address in said packet.

56. The method of claim 52, wherein said filter criteria include a traffic flow parameter.

57. The method of claim 52, wherein said filter criteria include data content information.

58. The method of claim 9, wherein said datagram address binds a node to a network attachment point and remains with said network attachment point if said node is changed.

59. The method of claim 9, wherein said datagram address contains partial address subfields that correspond to a network topology that leads to a network attachment point.

60. The method of claim 9, wherein said datagram address remains associated with a network attachment point when a node attached to said point is changed.

61. A system for transmitting data, comprising:

a connection-oriented, packet-switched network including a plurality of logical links; and

a plurality of data packets passing through said plurality of logical links, each of said packets comprising

a header field including

a datagram address containing a plurality of partial address subfields, wherein address information in said partial address subfields self-directs said packet through a plurality of top-down logical links, said plurality of top-down logical links being a subset of said plurality of logical links, and said datagram address operates as both a data link layer address and a network layer address;

and a payload field containing multimedia data,

wherein each of said packets remains unchanged as it is transferred along multiple links in said plurality of logical links.

62. The system of claim 61, wherein said plurality of logical links forms a transmission path between a source node and a destination node.

63. The system of claim 61, wherein said passing through does not use the Internet Protocol.

64. The system of claim 61, wherein said passing through occurs at wirespeed.

65. The system of claim 61, wherein said passing through uses forwarding tables calculated off-line.

66. The system of claim 61, wherein said passing through does not use real-time routing table calculations.

67. The system of claim 61, wherein said passing through occurs asynchronously.

68. The system of claim 61, wherein said passing through is facilitated by information in said datagram address about the type of service that the packet is providing.

69. The system of claim 61, wherein said packets have a variable length.

70. The system of claim 61, wherein said packets remain unchanged as they are forwarded along a majority of links in said plurality of logical links.

71. The system of claim 61, wherein said packets have no “

time-to-live”

data.

72. The system of claim 61, wherein said packets are transferred along a majority of links in said plurality of logical links without using routing calculations.

73. The system of claim 61, wherein said multimedia data includes data for telephony.

74. The system of claim 61, wherein said multimedia data includes data for media on demand.

75. The system of claim 61, wherein said multimedia data includes data for multicast.

76. The system of claim 61, wherein said multimedia data includes data for broadcast.

77. The system of claim 61, wherein said multimedia data includes data for transfer.

78. The system of claim 61, wherein said multimedia data is displayed on a user terminal.

79. The system of claim 78, wherein said user terminal is a set top box that provides access to both MediaNetwork Protocol and non-MediaNetwork Protocol networks.

80. The system of claim 78, wherein said user terminal is a teleputer that processes both MediaNetwork Protocol and non-MediaNetwork packets.

81. The system of claim 61, wherein said multimedia data is stored on a home server.

82. The system of claim 61, wherein said multimedia data is stored in a mass storage unit.

83. The system of claim 61, wherein said packet-switched network includes a plurality of non-peer-to-peer user terminals.

84. The system of claim 61, wherein said packet-switched network includes a plurality of non-peer-to-peer middle switches.

85. The system of claim 61, wherein said packet-switched network includes a plurality of non-peer-to-peer home gateways.

86. The system of claim 61, wherein said packet-switched network automatically configures a node when said node is added to said network.

87. The system of claim 86, wherein said automatic configuration includes checking the node identification number.

88. The system of claim 61, wherein said packet-switched network approves said passing through prior to said passing through.

89. The system of claim 88, wherein said approval is based on measured usage of resources along said plurality of logical links.

90. The system of claim 89, wherein said approval is on a per-session basis.

91. The system of claim 61, wherein a node in said packet-switched network approves said passing through prior to said passing through.

92. The system of claim 91, wherein said approval is based on measured usage of resources along said plurality of logical links.

93. The system of claim 92, wherein said approval is on a per-session basis.

94. The system of claim 61, wherein said packet-switched network includes servers that distribute network information to a plurality of switches in said network.

95. The system of claim 94, wherein said network information includes bandwidth usage for a plurality of switches in said network.

96. The system of claim 94, wherein said network information is distributed using bulletin packets.

97. The system of claim 61, wherein said packet-switched network verifies an account of a paying party prior to forwarding said packets.

98. The system of claim 61, wherein said packet-switched network measures, collects, and stores usage data.

99. The system of claim 98, wherein said usage data includes accounting data.

100. The system of claim 61, wherein said packet-switched network regulates the flow of packets.

101. The system of claim 100, wherein said network regulates the flow of packets by adding packets.

102. The system of claim 100, wherein said network regulates the flow of packets by holding back packets.

103. The system of claim 61, wherein said packet-switched network contains a server group that includes a plurality of server systems, wherein each server system performs a specialized task.

104. The system of claim 61, wherein said packet-switched network filters said packets based on a set of filter criteria.

105. The system of claim 104, wherein said filter criteria are established on a per session basis.

106. The system of claim 104, wherein said filter criteria include a source address in said packets.

107. The system of claim 104, wherein said filter criteria include a destination address in said packets.

108. The system of claim 104, wherein said filter criteria include a traffic flow parameter.

109. The system of claim 104, wherein said filter criteria include data content information.

110. The system of claim 61, wherein said datagram address binds a node to a network attachment point and remains with said network attachment point if said node is changed.

111. The system of claim 61, wherein said datagram address contains partial address subfields that correspond to a network topology that leads to a network attachment point.

112. The system of claim 61, wherein said datagram address remains associated with a network attachment point when a node attached to said point is changed.

113. A data structure for a packet, comprising:

a header field containing a datagram address containing a plurality of partial address subfields, wherein

address information in said partial address subfields self-directs said packet through a plurality of top-down logical links that forms a subset of a plurality of logical links in a connection-oriented, packet-switched network; and

said datagram address operates as both a data link layer address and a network layer address;

and a payload field containing multimedia data,

wherein said packet remains unchanged as it is transferred along multiple links in said plurality of logical links in said network.

114. The data structure of claim 113, wherein said packet is forwarded through said plurality of logical links, which forms a transmission path between a source node and a destination node in said network.

115. The data structure of claim 113, wherein said packet is forwarded through said network without using the Internet Protocol.

116. The data structure of claim 113, wherein said packet is forwarded through said network at wirespeed.

117. The data structure of claim 113, wherein said packet is forwarded through said network using forwarding tables calculated off-line.

118. The data structure of claim 113, wherein said packet is forwarded through said network without using real-time routing table calculations.

119. The data structure of claim 113, wherein said packet is forwarded through said network asynchronously.

120. The data structure of claim 113, wherein said packet is forwarded through said network and said forwarding is facilitated by information in said datagram address about the type of service that the packet is providing.

121. The data structure of claim 113, wherein said packet has a length that is different from the length of another packet of multimedia data that is forwarded in said network.

122. The data structure of claim 113, wherein said packet remains unchanged as it is forwarded along a majority of links in said plurality of logical links in said network.

123. The data structure of claim 113, wherein said packet has no “

time-to-live”

data.

124. The data structure of claim 113, wherein said packet is transferred along a majority of links in said plurality of logical links in said network without using routing calculations.

125. The data structure of claim 113, wherein said multimedia data includes data for telephony.

126. The data structure of claim 113, wherein said multimedia data includes data for media on demand.

127. The data structure of claim 113, wherein said multimedia data includes data for multicast.

128. The data structure of claim 113, wherein said multimedia data includes data for broadcast.

129. The data structure of claim 113, wherein said multimedia data includes data for transfer.

130. The data structure of claim 113, wherein said multimedia data is displayed on a user terminal.

131. The data structure of claim 130, wherein said user terminal is a set top box that provides access to both MediaNetwork Protocol and non-MediaNetwork Protocol networks.

132. The data structure of claim 130, wherein said user terminal is a teleputer that processes both MediaNetwork Protocol and non-MediaNetwork packets.

133. The data structure of claim 113, wherein said multimedia data is stored on a home server.

134. The data structure of claim 113, wherein said multimedia data is stored in a mass storage unit.

135. The data structure of claim 113, wherein said packet-switched network includes a plurality of non-peer-to-peer user terminals.

136. The data structure of claim 113, wherein said packet-switched network includes a plurality of non-peer-to-peer middle switches.

137. The data structure of claim 113, wherein said packet-switched network includes a plurality of non-peer-to-peer home gateways.

138. The data structure of claim 113, wherein said packet-switched network automatically configures a node when said node is added to said network.

139. The data structure of claim 138, wherein said automatic configuration includes checking the node identification number.

140. The data structure of claim 113, wherein said packet-switched network approves forwarding said packet through said plurality of logical links in said network prior to forwarding said packet.

141. The data structure of claim 140, wherein said approval is based on measured usage of resources along said plurality of logical links.

142. The data structure of claim 141, wherein said approval is on a per-session basis.

143. The data structure of claim 113, wherein a node in said packet-switched network approves forwarding said packet through said plurality of logical links in said network prior to said forwarding.

144. The data structure of claim 143, wherein said approval is based on measured usage of resources along said plurality of logical links.

145. The data structure of claim 144, wherein said approval is on a per-session basis.

146. The data structure of claim 113, wherein said packet-switched network includes servers that distribute network information to a plurality of switches in said network.

147. The data structure of claim 146, wherein said network information includes bandwidth usage for a plurality of switches in said network.

148. The data structure of claim 146, wherein said network information is distributed using bulletin packets.

149. The data structure of claim 113, wherein said packet-switched network verifies an account of a paying party prior to forwarding said packet.

150. The data structure of claim 113, wherein said packet-switched network measures, collects, and stores usage data.

151. The data structure of claim 150, wherein said usage data includes accounting data.

152. The data structure of claim 113, wherein said packet-switched network regulates the flow of packets.

153. The data structure of claim 152, wherein said network regulates the flow of packets by adding packets.

154. The data structure of claim 152, wherein said network regulates the flow of packets by holding back packets.

155. The data structure of claim 113, wherein said packet-switched network contains a server group that includes a plurality of server systems, wherein each server system performs a specialized task.

156. The data structure of claim 113, wherein said packet-switched network filters said packet based on a set of filter criteria.

157. The data structure of claim 156, wherein said filter criteria are established on a per session basis.

158. The data structure of claim 156, wherein said filter criteria include a source address in said packet.

159. The data structure of claim 156, wherein said filter criteria include a destination address in said packet.

160. The data structure of claim 156, wherein said filter criteria include a traffic flow parameter.

161. The data structure of claim 156, wherein said filter criteria include data content information.

162. The data structure of claim 113, wherein said datagram address binds a node to a network attachment point and remains with said network attachment point if said node is changed.

163. The data structure of claim 113, wherein said datagram address contains partial address subfields that correspond to a network topology that leads to a network attachment point.

164. The data structure of claim 113, wherein said datagram address remains associated with a network attachment point when a node attached to said point is changed.

165. A computer readable medium containing executable program instructions for transmitting data through a network, which when executed cause said network to:

forward a packet of multimedia data through a plurality of logical links in a connection-oriented, packet-switched network using a datagram address in said packet, wherein

address information in partial address subfields of said datagram address self-directs said packet through a plurality of top-down logical links, said plurality of top-down logical links being a subset of said plurality of logical links,

said packet remains unchanged as it is transferred along multiple links in said plurality of logical links, and

said datagram address operates as both a data link layer address and a network layer address.

166. The computer readable medium of claim 165, wherein said plurality of logical links forms a transmission path between a source node and a destination node.

167. The computer readable medium of claim 165, wherein said forwarding does not use the Internet Protocol.

168. The computer readable medium of claim 165, wherein said forwarding occurs at wirespeed.

169. The computer readable medium of claim 165, wherein said forwarding uses forwarding tables calculated off-line.

170. The computer readable medium of claim 165, wherein said forwarding does not use real-time routing table calculations.

171. The computer readable medium of claim 165, wherein said forwarding occurs asynchronously.

172. The computer readable medium of claim 165, wherein said forwarding is facilitated by information in said datagram address about the type of service that the packet is providing.

173. The computer readable medium of claim 165, wherein said packet has a length that is different from the length of another packet of multimedia data that is forwarded in said network.

174. The computer readable medium of claim 165, wherein said packet remains unchanged as it is forwarded along a majority of links in said plurality of logical links.

175. The computer readable medium of claim 165, wherein said packet has no “

time-to-live”

data.

176. The computer readable medium of claim 165, wherein said packet is transferred along a majority of links in said plurality of logical links without using routing calculations.

177. The computer readable medium of claim 165, wherein said multimedia data includes data for telephony.

178. The computer readable medium of claim 165, wherein said multimedia data includes data for media on demand.

179. The computer readable medium of claim 165, wherein said multimedia data includes data for multicast.

180. The computer readable medium of claim 165, wherein said multimedia data includes data for broadcast.

181. The computer readable medium of claim 165, wherein said multimedia data includes data for transfer.

182. The computer readable medium of claim 165, wherein said multimedia data is displayed on a user terminal.

183. The computer readable medium of claim 182, wherein said user terminal is a set top box that provides access to both MediaNetwork Protocol and non-MediaNetwork Protocol networks.

184. The computer readable medium of claim 182, wherein said user terminal is a teleputer that processes both MediaNetwork Protocol and non-MediaNetwork packets.

185. The computer readable medium of claim 165, wherein said multimedia data is stored on a home server.

186. The computer readable medium of claim 165, wherein said multimedia data is stored in a mass storage unit.

187. The computer readable medium of claim 165, wherein said packet-switched network includes a plurality of non-peer-to-peer user terminals.

188. The computer readable medium of claim 165, wherein said packet-switched network includes a plurality of non-peer-to-peer middle switches.

189. The computer readable medium of claim 165, wherein said packet-switched network includes a plurality of non-peer-to-peer home gateways.

190. The computer readable medium of claim 165, wherein said packet-switched network automatically configures a node when said node is added to said network.

191. The computer readable medium of claim 190, wherein said automatic configuration includes checking the node identification number.

192. The computer readable medium of claim 165, wherein said packet-switched network approves said forwarding prior to said forwarding.

193. The computer readable medium of claim 192, wherein said approval is based on measured usage of resources along said plurality of logical links.

194. The computer readable medium of claim 193, wherein said approval is on a per-session basis.

195. The computer readable medium of claim 165, wherein a node in said packet-switched network approves said forwarding prior to said forwarding.

196. The computer readable medium of claim 195, wherein said approval is based on measured usage of resources along said plurality of logical links.

197. The computer readable medium of claim 196, wherein said approval is on a per-session basis.

198. The computer readable medium of claim 165, wherein said packet-switched network includes servers that distribute network information to a plurality of switches in said network.

199. The computer readable medium of claim 198, wherein said network information includes bandwidth usage for a plurality of switches in said network.

200. The computer readable medium of claim 199, wherein said network information is distributed using bulletin packets.

201. The computer readable medium of claim 165, wherein said packet-switched network verifies an account of a paying party prior to forwarding said packet.

202. The computer readable medium of claim 165, wherein said packet-switched network measures, collects, and stores usage data.

203. The computer readable medium of claim 202, wherein said usage data includes accounting data.

204. The computer readable medium of claim 165, wherein said packet-switched network regulates the flow of packets.

205. The computer readable medium of claim 204, wherein said network regulates the flow of packets by adding packets.

206. The computer readable medium of claim 204, wherein said network regulates the flow of packets by holding back packets.

207. The computer readable medium of claim 165, wherein said packet-switched network contains a server group that includes a plurality of server systems, wherein each server system performs a specialized task.

208. The computer readable medium of claim 165, wherein said packet-switched network filters said packet based on a set of filter criteria.

209. The computer readable medium of claim 208, wherein said filter criteria are established on a per session basis.

210. The computer readable medium of claim 208, wherein said filter criteria include a source address in said packet.

211. The computer readable medium of claim 208, wherein said filter criteria include a destination address in said packet.

212. The computer readable medium of claim 208, wherein said filter criteria include a traffic flow parameter.

213. The computer readable medium of claim 208, wherein said filter criteria include data content information.

214. The computer readable medium of claim 165, wherein said datagram address binds a node to a network attachment point and remains with said network attachment point if said node is changed.

215. The computer readable medium of claim 165, wherein said datagram address contains partial address subfields that correspond to a network topology that leads to a network attachment point.

216. The computer readable medium of claim 165, wherein said datagram address remains associated with said network attachment point when a node attached to said point is changed.