CA2403736A1 - Service selection in a shared access network using dynamic host configuration protocol - Google Patents
Service selection in a shared access network using dynamic host configuration protocol Download PDFInfo
- Publication number
- CA2403736A1 CA2403736A1 CA002403736A CA2403736A CA2403736A1 CA 2403736 A1 CA2403736 A1 CA 2403736A1 CA 002403736 A CA002403736 A CA 002403736A CA 2403736 A CA2403736 A CA 2403736A CA 2403736 A1 CA2403736 A1 CA 2403736A1
- Authority
- CA
- Canada
- Prior art keywords
- network
- service
- access
- address
- access device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2801—Broadband local area networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5084—Providing for device mobility
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2858—Access network architectures
- H04L12/2859—Point-to-point connection between the data network and the subscribers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2858—Access network architectures
- H04L12/2861—Point-to-multipoint connection from the data network to the subscribers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2869—Operational details of access network equipments
- H04L12/287—Remote access server, e.g. BRAS
- H04L12/2872—Termination of subscriber connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2869—Operational details of access network equipments
- H04L12/287—Remote access server, e.g. BRAS
- H04L12/2874—Processing of data for distribution to the subscribers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
- H04L12/2869—Operational details of access network equipments
- H04L12/287—Remote access server, e.g. BRAS
- H04L12/2876—Handling of subscriber policies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5691—Access to open networks; Ingress point selection, e.g. ISP selection
- H04L12/5692—Selection among different networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/302—Route determination based on requested QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/302—Route determination based on requested QoS
- H04L45/306—Route determination based on the nature of the carried application
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/20—Traffic policing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/58—Caching of addresses or names
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0227—Filtering policies
- H04L63/0236—Filtering by address, protocol, port number or service, e.g. IP-address or URL
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0869—Network architectures or network communication protocols for network security for authentication of entities for achieving mutual authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1441—Countermeasures against malicious traffic
- H04L63/1466—Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/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
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Abstract
It is an object of the invention to enable multiple services or service providers to share the facilities of an access network infrastructure providing physical connectivity to subscribers. A network access device advantageously may be used in communication network services with a service or service provider that is separate from the operator of the access network infrastructure.
Description
SERVICE SELECTION IN A SHARED ACCESS NETWORK
USING DYNAMIC HOST CONFIGURATION PROTOCOL
Field of the Invention The present invention relates generally to communication network services, and, more particularly, to providing multiple services in a communication network.
Background of the Invention 1 o Customers of communication network services often desire access to a plurality of different services and different service providers. For example, when using a dial-up connection to a packet-switched data network such as the Internet, a customer can choose from multiple service providers by dialing different telephone numbers in the PSTN. The physical path from the customer to t5 the customer's Internet Service Provider (ISP) is dedicated to the connection for the duration of the telephone call. The ISP assigns an IP address to the customer and can link the authenticated customer and the assigned IP address to the physical address (e.g. dial-up modem) used by the customer. With this linkage, the ISP can ensure the customer only uses the address authorized by the ISP
and 20 can use the customer's IP address to manage access to the ISP's services.
The physical connection between a customer and the ISP, as well as the linkage to IP
address assignment and customer authentication is terminated when the dial-up connection is terminated.
Constrained by the physical capacity of these temporary 25 connections across the PSTN, many service providers are moving to high-speed access architectures (e.g., digital subscriber line (DSL), wireless, satellite, or cable) that provide dedicated physical connectivity directly to the subscriber and under the control of the ISP. These alternatives to shared access through the switched telephone network, however, do not lend themselves to shared access by 30 multiple services and/or service providers.
Summary of the Invention It is an object of the invention to enable multiple services or service providers to share the facilities of an access network infrastructure 35 providing physical connectivity to subscribers. In accordance with an embodiment of the invention, a router situated at an edge of an access network forwards packets to any of a plurality of packet-switched service networks.
The muter uses a policy based on the source address of the packets to determine to which service network to forward the packet. Each network access device is 40 assigned a network address, which is associated with a particular service or service provider to which the user of the device is subscribed. The network access device advantageously may be used in communication network services with a service or service provider that is separate from the operator of the access network infrastructure.
45 In accordance with another aspect of the invention, interconnections between a plurality of packet-switched service networks and an access network are localized into managed access points. Routers in the access network can advantageously forward packets to the managed access points using conventional routing procedures, thus enabling the access network to provide 50 "local" packet-switched services. The managed access points use source address-based policy to determine to which service network to forward a packet. Where a packet arrives at a managed access point that is not connected to the correct service network, the managed access point can use packet encapsulation or some other form of tunneling to redirect the packet to the correct managed access point.
55 The present invention, among other advantages, does not require interconnection points to each service network at every regional access network site.
In accordance with another aspect of the invention, a configuration server, upon receiving a request from a network access device selecting a particular service, allocates a network address from a pool of addresses associated 60 with the service and assigns the network address to the network access device using a host configuration protocol, such as DHCP. In accordance with an embodiment of the invention, the configuration server authenticates the network access device before assigning a network address. In accordance with another embodiment of the invention, the configuration server transmits authentication 65 information received from the network access device to a server in the service network responsible for authentication. In accordance with another embodiment of the invention, the host configuration protocol messages acknowledging allocation of a network address to the service subscriber's network access device are used to create entries in an address resolution protocol cache in order to 7o restrict access to the access network infrastructure to those network access devices that are properly registered and authenticated. In accordance with another embodiment of the invention, the host configuration protocol acknowledging allocation of the network address to the service subscriber's network access device are used to initiate the distribution of service policies to policy 75 enforcement points in order to enable differentiated quality-of-support for different subscribers of different services or service providers. The present invention, among other advantages, enables the network addresses-which ultimately determine the service network utilized by the particular network access device-to be allocated and reassigned dynamically.
8o These and other advantages of the invention will be apparent to those of ordinary skill in the art by reference to the following detailed description and the accompanying drawings.
Brief Description of the Drawings 85 FIG. 1 illustrates an interconnection of packet-switched service networks and an access network embodying principles of the invention.
FIG. 2A and FIG. 2B is conceptual representation of an example embodiment illustrating principles of the invention based on an HFC access architecture with corresponding end-to-end protocol layers.
90 FIG. 3 is a flowchart of processing performed at a policy router, in accordance with an embodiment of the invention.
FIG. 4 is a simplified example of router configuration instructions.
FIG. 5 illustrates an interconnection of packet-switched service network, regional access networks, and a packet-switched access network, 95 embodying principles of another aspect of the invention.
FIG. 6 is a flowchart of processing performed at a policy router acting as a managed access point, in accordance with another embodiment of the invention.
FIG. 7 is a timeline diagram of messages exchanged in the 100 assignment of a network address associated with a particular service to a network access device, in accordance with a preferred embodiment of another aspect of the invention.
FIG. 8 is a conceptual representation of a DHCP message exchanged between the network access device and a DHCP server.
105 FIG. 9 is timeline diagram of messages exchanged in the assignment of a network address associated with a particular service to a network access device, in accordance with a preferred embodiment of another aspect of the invention.
FIG. 10 is a timeline diagram of messages exchanged in the 110 assignment of a network address associated with a particular service to a network access device, in accordance with a preferred embodiment of another aspect of the invention.
FIG. 11 is a flowchart of processing performed at a Cable Modem Termination System, exemplifying an embodiment of another aspect of the 115 invention.
FIG. 12 is a timeline diagram of messages exchanged in the assignment of a service class to a subscriber, in accordance with a preferred embodiment of another aspect of the invention.
FIG. 13 is a conceptual diagram of a hierarchical link-sharing 120 structure.
Detailed Description In FIG. 1, a plurality of subscribers operating network access devices 101, 102, 103, ... 104 are provided access to communication network 125 services, which are facilitated by a plurality of packet-switched data networks, shown in FIG. 1 as 151 and 152. Packet-switched data networks 151 and 152, referred to herein as "service networks," offer access to different services and/or are operated by different service providers. For example, service network 151 could provide packet-switched connectivity to public data networks while service 130 network 152 could offer packet-switched telephony service (or the same public data network connectivity, but from a different service provider). The service networks, as is well known in the art, utilize a network addressing scheme to route datagrams to and from hosts: for example, where the service networks utilize the TCP/IP protocol suite, Internet Protocol (IP) addresses are assigned to each host 135 and utilized in the process of routing packets from a source to a destination in the networks. See, e.g., "INTERNET PROTOCOL," IETF Network Working Group, RFC 791 (September 1981); S. Deering, R. Hinden, ,"Internet Protocol, Version (IPv6) Specification," IETF Network Working Group, RFC 1883 (December 1995), which are incorporated by reference herein. The invention shall be 140 described herein with particular reference to the TCP/IP protocol suite and IP
addresses, although those skilled in the art would readily be able to implement the invention using any of a number of different communication protocols.
The network access devices 101 ... 104 are typically customer premises equipment (CPE) such as a personal computer, information appliance, 145 personal data assistant, data-enabled wireless handset, or any other type of device capable of accessing information through a packet-switched data network. Each network access device 101 ... 104 is either connected to or integrated with a network interface unit 111 ... 114, e.g. a modem, which enables communication through an access network infrastructure, shown as 120 in FIG. 1. Each network 150 access device is assigned an IP address which, in accordance with an aspect of the invention, is associated with a particular service or service provider to which the user of the device is subscribed. For example, network access device 101 is assumed to have been assigned, for purposes of the description herein, an IP
address associated with a service provider operating service network 151. As 155 further described herein, it is advantageous to provide a service activation system 160 which advantageously permits the dynamic allocation, assignment, and reassignment of IP addresses to the plurality of network access devices based on customer subscriptions to particular services.
The network access device 101 communicates with the service 16o network 151 through the access network infrastructure 120, which, in accordance with aspects of the invention, is capable of recognizing and directing traffic to the proper service network. The access network infrastructure 120 advantageously can be operated and maintained by an entity that is the same as or different from the entities operating and maintaining the service networks 151 and 152. In ~ 65 accordance with an embodiment of an aspect of the present invention, the different IP-based services offered by the different service networks 151 and utilize shared layer one and layer two resources in the access network 120.
Layer three routing procedures, however, are modified to permit IP traffic from network access device 101 to flow to the correct subscribed service network 151. The 17o access network 120 has a muter 130 on the edge of the access network. The router 130 has a first interface with a connection to a router 141 in service network 151 and a second interface with a connection to a router 142 in service network 152. As further described herein, the router processes packets and is capable of directing traffic to the proper service network.
175 FIG. 2A shows an exemplary access architecture based on a hybrid fiber coaxial (HFC) access network. As is known in the art, each network interface device 201 ... 202 is either connected to or integrated with a cable modem 211 which enables communication through the HFC network 221. In accordance with the Data Over Cable Service Interface Specification (DOCSIS), a 18o Cable Modem Termination System (CMTS), shown as 225 in FIG. 2A, communicates with the cable modems 211 and manages access to both upstream and downstream cable capacity on the HFC networks 221. See, e.g., "Data-Over-Cable Service Interface Specifications: Cable Modem Termination System -Network Side Interface Specification," Cable Television Laboratories, Inc., SP-X85 CMTS-NSI-I01-960702; "Data-Over-Cable Service Interface Specifications:
Cable Modem to Customer Premise Equipment Interface Specification," Cable Television Laboratories, Inc., SP-CMCI-C02C-991015; "Data-Over-Cable Service Interface Specifications: Baseline Privacy Plus Interface Specifications,"
Cable Television Laboratories, Inc., SP-BPI+-I06-001215, which are incorporated 190 by reference herein. The CMTS 225 manages the scheduling of both upstream and downstream transmission and allocates cable capacity to individual customers identified by a Service IDs (SIDS). The CMTS 225 can have an integrated router 228 or can be a separate device 226 that bridges to a fast Ethernet switch 227 which connects to the muter 228. The IP muter 228 provides connectivity to an 195 IP network 222, which further comprises the muter 230 (corresponding to router 130 in FIG. 1) which interfaces to IP routers 241 and 242 in service networks and 252, respectively. Accordingly, the HFC network 221, the CMTS 225, and the IP network 222 correspond to the access network infrastructure 120 shown in FIG. 1. FIG. 2B shows a conceptual diagram of the end-to-end communication 20o protocol stack from a network access device 201 ( 101 ) to a router 241 ( 141 ) in service provider's network 251 (151). As is known in the art, the lowest layer deals with the physical layer (PL) of the protocol stack, e.g. the Ethernet physical media device (PMD) layer; the second layer deals with the data link layer, e.g. the Ethernet Media Access Control (MAC) layer; and the third layer in the protocol 205 stack deals with the network layer, e.g. the IP layer. The following aspects of the invention deal with modifications to routing processes in the network layer of the protocol stack.
Router 130 in the access network 120 in FIG. 1 (corresponding to IP router 230 in FIG. 2) separates the IP traffic to the multiple services or service 210 providers as well as combines traffic from the multiple services or service providers. In accordance with an aspect of the invention, IP packets are routed from network access device 101 to the subscribed service network 151 using source address-based policy routing. Conventional routing is destination-based:
the muter consults an internal routing table which maps the destination addresses 215 of all inbound packets to a physical interface address for use for outgoing packets.
Policy routing schemes, however, will selectively choose different paths for different packets even where the packet's destination address may be the same.
Since network access devices are assigned addresses associated with a particular network service provider, the source address based policy routing scheme ensures 22o packets from a network access device will go to the appropriate service network.
Conventional destination-based routing will ensure that packets addressed to a network access device will be routed to the appropriate service network. Note that this would require service providers to advertise their service address ranges to their peers.
225 FIG. 3 sets forth the processing performed at a muter in the access network, e.g. router 130 in FIG. 1. At step 301, the router receives an incoming packet. At step 302, the muter reads the packet header and retrieves the packet filtering rules, typically stored in an access list as further described below. At steps 303, 305, and 307, the router applies the packet filtering rules. At step 303, 23o the muter compares the source IP address in the packet header to a list of addresses allocated to subscribers of services of a first service provider, e.g.
operating service network 151 in FIG. 1. If the source address matches one of these addresses, then at step 304 the muter forwards the packet to a router in service network 151, e.g. router 141 in FIG. 1. At step 305, the router compares 235 the source IP address in the packet header to a list of addresses allocated to subscribers of services of a second service provider, e.g. operating service network 152 in FIG. 1. If the source IP address matches one of these addresses, then at step 305 the muter forwards the packet to a router in service network 152, e.g. muter 142 in FIG. 1. The muter continues in this fashion with any other 240 packet filtering rules identifying IP addresses allocated to subscribers of any other service providers. Assuming the IP source address does not match any such addresses associated with a service provider, at step 307, the muter applies any remaining packet filtering rules and routes or denies the packet accordingly.
FIG. 4 sets forth an example of router configuration instructions 245 written for the Cisco Internetworking Operating System (IOS), which is used pervasively on conventional IP routers. Only the relevant portions of the configuration instructions are shown. Lines 401 to 405 configure the interface to utilize policy routing. Lines 406 to 410 specify the particular policy, namely to set the next "hop" address to the router address of a router in a one of the service 25o networks, i.e. "ispl next-hop-address," if the source address matches a range of addresses allocated to subscribers of the services provided by the service network, i.e. "ispl-subs." Lines 412 to 413 set forth access lists associating "i sp 1-subs" with ranges of addresses expressed, by convention, as a source address and a mask portion, i.e., the above policy is applied by the router to any 255 traffic with a subscriber source address expressed as "ispl pref ixl" with a mask portion of "ispl pref ixl wildcard".
The embodiment shown in FIG. 1 notably requires interconnection points to all relevant service networks at each edge of each regional access network. In accordance with another aspect of the invention, it is desirable to 260 create a regional transport network of routers and to localize the interconnection between the service networks and the access infrastructure into managed access points. A managed access point is a physical location at which the interfaces to the service networks can be provided. Having one or a small plurality of managed access points advantageously allows service selection to be implemented without 265 requiring network service providers to connect physical facilities into, for example, every cable head end in an HFC-based network-thereby reducing costs for both the access network infrastructure operator and the service network providers. Each router in the regional transport network can be configured with policy information and invoke source address routing to forward packets to the 270 managed access point providing access to the relevant service network. By overriding normal routing procedures, however, these procedures may introduce potential routing loops absent significant coordination between the routers external to known routing protocols. This risk can be minimized by centralizing the policy routing function in a single muter that provides the interfaces to the 275 service networks.
FIG. 5 illustrates an embodiment of this aspect of the invention.
Each network access device 501 is connected through a network interface unit to one of a plurality of access networks, e.g. 521 and 522 in FIG. 5. Each access network has an edge router (531 and 532 respectively in FIG. 5) which connects 280 the access network to a regional IP network of routers, represented abstractly in FIG. 5 as IP access network 570. It is advantageous to aggregate connections from groups of edge routers to a single aggregation router 571 in the IP
access network 570, as shown in FIG. 5. Aggregation muter 571 can then connect to other routers in the regional IP network 570, i.e. routers 572 ... 573, which can 285 also be aggregation routers connecting to pluralities of edge routers.
Routers 541, 542, ... 543 in service networks 551, 552, ... 553 connect to the IP network 570 at routers 574 and 575, which act as managed access points to the service networks.
Only the managed access point routers, e.g. 575, need invoke policy routing based on packet source address. All intermediate routers within the IP access network 290 570, i.e. 571 ... 573, use normal destination-based forwarding procedures for destinations that are not local to the network 570. No configuration of policy in the intermediate routers is necessary.
By locating the policy routing functions at the interfaces to the service networks, the access network infrastructure (whether reflected generally 295 by 120 in FIG. 1 or, in the packet-switched context, as network 570 in FIG. 5) can provide access to "local" services available from within the access network infrastructure. For example, IP network 570 can provide access to "local"
packet-switched services and operate independent of the source address assigned to the network access devices. Since the intermediate routers 571 ... 573 all use 300 conventional destination-based forwarding, network 570 will properly route local service packets along the correct routing paths. "Non-local" service packets, however, are routed towards the managed access point routers 575 and 574 and policy routed to the correct service network. Where the network 570 forwards to a single managed access point muter or where each managed access point router 305 has a connection to each service network, the managed access point router can forward packets in accordance with the policies described above. Where, however, there are service networks that connect to only a subset of the managed access points (e.g., in FIG. 5, where service network 553 only connects to managed access point router 574), packets can be redirected or "tunneled" to the 31o correct managed access point in order to ensure that the packets arrive at the correct service network. The multiple interconnected managed access points can then provide a single "logical" inter-domain gateway, again permitting all other routers to use conventional destination-based routing procedures.
FIG. 6 sets forth a flowchart of the processing performed at a 3~5 managed access point router, e.g. muter 575 in FIG. 5, illustrating an embodiment of this aspect of the invention. The particular managed access point router 575 is assumed to be connected to two service networks, e.g. service networks 551 and 552 in FIG. 5, while a second managed access point router 574 provides access to a third service network, service network 553. At step 601, the muter receives an 320 incoming packet. At step 602, the router reads the packet header and retrieves the packet filtering rules, as well as decapsulates any encapsulated packets, as further described herein. At steps 603, 605, 607, and 609, the router applies the packet filtering rules. At step 603, the router compares the source IP address in the packet header to a list of addresses allocated to subscribers of services of a first 325 service provider, e.g. operating service network 551 in FIG. 5. If the source address matches one of these addresses, then at step 604 the muter forwards the packet to a muter in service network 551, e.g. muter 541 in FIG. 5. At step 605, the router compares the source IP address in the packet header to a list of addresses allocated to subscribers of services of a second service provider, e.g.
330 operating service network 552 in FIG. 5. If the source IP address matches one of these addresses, then at step 606 the router forwards the packet to a muter in service network 552, e.g. muter 542 in FIG. 5. At step 607, the router compares the source IP address in the packet header to a list of addresses allocated to subscribers of services of a third service provider, e.g. operating service network 335 553 in FIG. 5, which is not connected to this particular managed access point. If the source IP address matches one of these addresses, then at step 608, the router encapsulates the packet, using any of a number of known methods for packet encapsulation, and routes the packet to a new destination address, namely the address of the managed access point with access to service network 553, i.e.
34o managed access point router 574. Packet encapsulation is a method by which a packet may rerouted to an intermediate destination other than the destination that would be selected using normal routing procedures. See, e.g., C. Perkins, "IP
Encapsulation within IP," IETF Network Working Group, RFC 2003 (October 1996); C. Perkins, "Minimal Encapsulation within IP," IETF Network Working 345 Group, RFC 2004 (October 1996), which are incorporated by reference herein.
The receiving router 574 will decapsulate the packet and route the packet, accordingly, to service network 553. The muter continues in this fashion with any other packet filtering rules identifying IP addresses associated with any other service providers. Assuming the IP source address does not match any addresses 350 associated with any other service providers, at step 609, the router applies any remaining packet filtering rules and routes or denies the packet accordingly.
Note that if managed access point 575 has a direct physical connection to managed access point 574, then no encapsulation is needed. In fact, a typical configuration might include multiple port-constrained policy routers on a GIG Ethernet 355 providing the logical managed access point function without any encapsulation.
Encapsulation is only really needed to provide a logical direct connection if there is not a direct physical connection.
Packets traveling between network access devices connected to the same access network infrastructure can be forwarded directly between the devices 360 in the access network - rather than forwarding the packets outwards to a service network and back to the same access network. This advantageously saves on bandwidth and other network resources. The only packets that need be routed to a managed access point muter need be the ones for which no specific route is known internally to the access network infrastructure.
365 It is advantageous to enable the IP addresses-which ultimately determine the service network utilized by the particular network access device-to be allocated and reassigned dynamically. With reference to FIG. 1, a service activation system 160 is shown which further comprises a configuration server WO 01/71983 PCT/USOl/08849 161 and a registration server 162 connected to the access network infrastructure 370 120. The registration server 162 provides a network-based subscription/authorization process for the various services shared on the access network infrastructure 120. A customer desiring to subscribe to a new service can access and provide registration information to the registration server 162, e.g. by using HTML forms and the Hyper Text Transfer Protocol (HTTP) as is known in 375 the art. Upon successful service subscription, the registration server 162 updates a customer registration database 163. The configuration server 161 uses the registration information to activate the service. The configuration server 161 is responsible for allocating network addresses on behalf of the service networks from a network address space associated with the selected service. In a preferred 380 embodiment of this aspect of the invention, the configuration server 161 uses a host configuration protocol such as the Dynamic Host Configuration Protocol (DHCP) to configure the network addresses of the network access devices. See R. Droms, "Dynamic Host Configuration Protocol," IETF Network Working Group, RFC 2131 (March 1997); S. Alexander, R. Droms, "DHCP Options and 385 BOOTP Vendor Extensions," IETF Network Working Group, RFC 2132 (March 1997); which are incorporated by reference herein. This aspect of the invention shall be described herein with particular reference to DHCP, and the configuration server 161 shall be referred to herein as the DHCP server, although those skilled in the art would readily be able to implement this aspect of the invention using a 39o different protocol.
FIG. 7 is a simplified timeline diagram of DHCP messages exchanged as the DHCP server 720 assigns a service-specific network address to a network access device 710 acting as a DHCP client. At 701, the network access device 710 sends a DHCPDISCOVER message through the access network 395 infrastructure. The DHCPDISCOVER message, in accordance with an aspect of the invention, includes a "svc-id" option field that identifies the service to which the network access device has been subscribed and from which service is desired.
The DHCP server 720 receives the DHCPDISCOVER message and, at 702, allocates an IP address from the pool of addresses associated with the particular 40o service. The DHCP server 720 can use the device's MAC address to lookup the customer's registration information and confirm that the device is authorized to access the identified service. Where the DHCP server 720 cannot find the device's MAC address in the registration database, the server can allocate a special IP address that only allows access to the registration server. At 703, the 405 DHCP server 720 responds with a DHCPOFFER message that includes the IP
address in a field in the DHCP message. At 704, the network access device 710 receives the DHCPOFFER (and any other offers from any other DHCP servers in the access network) and sends out a DHCPREQUEST directed to the DHCP
server which requests the IP address identified in the DHCPOFFER. At 707, the 410 DHCP server commits to assigning the IP address to the network access device, commits the binding to persistent storage, and transmits a DHCPACK message containing the configuration parameters for the device. If the DHCP server is unable to satisfy the DHCPREQUEST message, the server responds with a DHCPNAK message. FIG. 8 is a simplified representation of the fields in a 4 ~ 5 DHCP message, including a "svc-id" option field (820) which identifies the selected service.
It is preferable that the DHCP servers and clients use some mutual authentication mechanism to restrict address assignment to authorized hosts and to prevent clients from accepting addresses from invalid DHCP servers. See, for 42o example, the "delayed authentication" scheme described in R. Droms, W.
Arbaugh, "Authentication for DHCP Messages," IETF Network Working Group, Internet Draft, <draft-ietf-dhc-authentication--.txt>; or the Kerberos-based authentication mechanism described in K. Hornstein, T. Lemon, B. Aboba, J.
Trostle, "DHCP Authentication via Kerberos V," IETF Network Working Group, 425 Internet Draft, <draft-hornstein-dhc-kerbauth ->; which are incorporated by reference herein. The "delayed authentication" mechanism supports mutual authentication of DHCP clients and servers based on a shared secret, which may be provisioned using out-of-band mechanisms. On the other hand, the Kerberos-based mechanisms are very well suited for inter-realm authentication, thereby 43o supporting client mobility, i.e. a network access device could connect to a m particular access network infrastructure without any prior registration with the access network. Each service network provider could securely authenticate the network access device accessing the service network from another network "realm," e.g. the access network infrastructure.
435 The operator of the relevant service network, e.g. service network 152 in FIG. l, may desire to maintain a separate registration server, e.g.
server 155 in FIG. 1, and to retain responsibility for user authentication and authorization. The service activation system 160 can provide a proxy server configured to permits HTTP traffic only between local hosts and registration 440 server 155 in service network 152. The service provider operating service network 152 would then be responsible for providing the appropriate registration information required for proper service selection to the service activation system 160. The service provider would also be responsible for notifying the service activation system 160 when service should be discontinued. Alternatively, the 445 DHCP server 161 in the service activation system 160 can interact with the registration server 155 using a back-end authentication protocol, e.g. the Remote Authentication Dial In User Service (RADIUS). See C. Rigney, A. Rubens, W.
Simpson, S. Willens, "Remote Authentication Dial In User Service (RADIUS),"
IETF Network Working Group, RFC 2058 (January 1997), which is incorporated 45o by reference herein. The DHCP server can contain a RADIUS client and, thereby, leverage the large RADIUS embedded base used for dial access authentication.
FIG. 9 illustrates this embodiment of this aspect of the invention in a flowchart corresponding to the flowchart shown in FIG. 7. At 903, the DHCP server 920 generates a random challenge and includes the challenge along with the allocated 455 IP address in the DHCPOFFER message. The DHCP client 910 generates a response to the challenge by encrypting the challenge with a key that is derived from the subscriber's authentication information. At 904, the client 910 includes the challenge, response, and IP address in the DHCPREQUEST message. The DHCP server 920 forwards both the challenge and response in a 46o RADIUS ACCESS REQ message to a RADIUS server 930 in the selected service network. The RADIUS server 930 either accepts or rejects the RADIUS
USING DYNAMIC HOST CONFIGURATION PROTOCOL
Field of the Invention The present invention relates generally to communication network services, and, more particularly, to providing multiple services in a communication network.
Background of the Invention 1 o Customers of communication network services often desire access to a plurality of different services and different service providers. For example, when using a dial-up connection to a packet-switched data network such as the Internet, a customer can choose from multiple service providers by dialing different telephone numbers in the PSTN. The physical path from the customer to t5 the customer's Internet Service Provider (ISP) is dedicated to the connection for the duration of the telephone call. The ISP assigns an IP address to the customer and can link the authenticated customer and the assigned IP address to the physical address (e.g. dial-up modem) used by the customer. With this linkage, the ISP can ensure the customer only uses the address authorized by the ISP
and 20 can use the customer's IP address to manage access to the ISP's services.
The physical connection between a customer and the ISP, as well as the linkage to IP
address assignment and customer authentication is terminated when the dial-up connection is terminated.
Constrained by the physical capacity of these temporary 25 connections across the PSTN, many service providers are moving to high-speed access architectures (e.g., digital subscriber line (DSL), wireless, satellite, or cable) that provide dedicated physical connectivity directly to the subscriber and under the control of the ISP. These alternatives to shared access through the switched telephone network, however, do not lend themselves to shared access by 30 multiple services and/or service providers.
Summary of the Invention It is an object of the invention to enable multiple services or service providers to share the facilities of an access network infrastructure 35 providing physical connectivity to subscribers. In accordance with an embodiment of the invention, a router situated at an edge of an access network forwards packets to any of a plurality of packet-switched service networks.
The muter uses a policy based on the source address of the packets to determine to which service network to forward the packet. Each network access device is 40 assigned a network address, which is associated with a particular service or service provider to which the user of the device is subscribed. The network access device advantageously may be used in communication network services with a service or service provider that is separate from the operator of the access network infrastructure.
45 In accordance with another aspect of the invention, interconnections between a plurality of packet-switched service networks and an access network are localized into managed access points. Routers in the access network can advantageously forward packets to the managed access points using conventional routing procedures, thus enabling the access network to provide 50 "local" packet-switched services. The managed access points use source address-based policy to determine to which service network to forward a packet. Where a packet arrives at a managed access point that is not connected to the correct service network, the managed access point can use packet encapsulation or some other form of tunneling to redirect the packet to the correct managed access point.
55 The present invention, among other advantages, does not require interconnection points to each service network at every regional access network site.
In accordance with another aspect of the invention, a configuration server, upon receiving a request from a network access device selecting a particular service, allocates a network address from a pool of addresses associated 60 with the service and assigns the network address to the network access device using a host configuration protocol, such as DHCP. In accordance with an embodiment of the invention, the configuration server authenticates the network access device before assigning a network address. In accordance with another embodiment of the invention, the configuration server transmits authentication 65 information received from the network access device to a server in the service network responsible for authentication. In accordance with another embodiment of the invention, the host configuration protocol messages acknowledging allocation of a network address to the service subscriber's network access device are used to create entries in an address resolution protocol cache in order to 7o restrict access to the access network infrastructure to those network access devices that are properly registered and authenticated. In accordance with another embodiment of the invention, the host configuration protocol acknowledging allocation of the network address to the service subscriber's network access device are used to initiate the distribution of service policies to policy 75 enforcement points in order to enable differentiated quality-of-support for different subscribers of different services or service providers. The present invention, among other advantages, enables the network addresses-which ultimately determine the service network utilized by the particular network access device-to be allocated and reassigned dynamically.
8o These and other advantages of the invention will be apparent to those of ordinary skill in the art by reference to the following detailed description and the accompanying drawings.
Brief Description of the Drawings 85 FIG. 1 illustrates an interconnection of packet-switched service networks and an access network embodying principles of the invention.
FIG. 2A and FIG. 2B is conceptual representation of an example embodiment illustrating principles of the invention based on an HFC access architecture with corresponding end-to-end protocol layers.
90 FIG. 3 is a flowchart of processing performed at a policy router, in accordance with an embodiment of the invention.
FIG. 4 is a simplified example of router configuration instructions.
FIG. 5 illustrates an interconnection of packet-switched service network, regional access networks, and a packet-switched access network, 95 embodying principles of another aspect of the invention.
FIG. 6 is a flowchart of processing performed at a policy router acting as a managed access point, in accordance with another embodiment of the invention.
FIG. 7 is a timeline diagram of messages exchanged in the 100 assignment of a network address associated with a particular service to a network access device, in accordance with a preferred embodiment of another aspect of the invention.
FIG. 8 is a conceptual representation of a DHCP message exchanged between the network access device and a DHCP server.
105 FIG. 9 is timeline diagram of messages exchanged in the assignment of a network address associated with a particular service to a network access device, in accordance with a preferred embodiment of another aspect of the invention.
FIG. 10 is a timeline diagram of messages exchanged in the 110 assignment of a network address associated with a particular service to a network access device, in accordance with a preferred embodiment of another aspect of the invention.
FIG. 11 is a flowchart of processing performed at a Cable Modem Termination System, exemplifying an embodiment of another aspect of the 115 invention.
FIG. 12 is a timeline diagram of messages exchanged in the assignment of a service class to a subscriber, in accordance with a preferred embodiment of another aspect of the invention.
FIG. 13 is a conceptual diagram of a hierarchical link-sharing 120 structure.
Detailed Description In FIG. 1, a plurality of subscribers operating network access devices 101, 102, 103, ... 104 are provided access to communication network 125 services, which are facilitated by a plurality of packet-switched data networks, shown in FIG. 1 as 151 and 152. Packet-switched data networks 151 and 152, referred to herein as "service networks," offer access to different services and/or are operated by different service providers. For example, service network 151 could provide packet-switched connectivity to public data networks while service 130 network 152 could offer packet-switched telephony service (or the same public data network connectivity, but from a different service provider). The service networks, as is well known in the art, utilize a network addressing scheme to route datagrams to and from hosts: for example, where the service networks utilize the TCP/IP protocol suite, Internet Protocol (IP) addresses are assigned to each host 135 and utilized in the process of routing packets from a source to a destination in the networks. See, e.g., "INTERNET PROTOCOL," IETF Network Working Group, RFC 791 (September 1981); S. Deering, R. Hinden, ,"Internet Protocol, Version (IPv6) Specification," IETF Network Working Group, RFC 1883 (December 1995), which are incorporated by reference herein. The invention shall be 140 described herein with particular reference to the TCP/IP protocol suite and IP
addresses, although those skilled in the art would readily be able to implement the invention using any of a number of different communication protocols.
The network access devices 101 ... 104 are typically customer premises equipment (CPE) such as a personal computer, information appliance, 145 personal data assistant, data-enabled wireless handset, or any other type of device capable of accessing information through a packet-switched data network. Each network access device 101 ... 104 is either connected to or integrated with a network interface unit 111 ... 114, e.g. a modem, which enables communication through an access network infrastructure, shown as 120 in FIG. 1. Each network 150 access device is assigned an IP address which, in accordance with an aspect of the invention, is associated with a particular service or service provider to which the user of the device is subscribed. For example, network access device 101 is assumed to have been assigned, for purposes of the description herein, an IP
address associated with a service provider operating service network 151. As 155 further described herein, it is advantageous to provide a service activation system 160 which advantageously permits the dynamic allocation, assignment, and reassignment of IP addresses to the plurality of network access devices based on customer subscriptions to particular services.
The network access device 101 communicates with the service 16o network 151 through the access network infrastructure 120, which, in accordance with aspects of the invention, is capable of recognizing and directing traffic to the proper service network. The access network infrastructure 120 advantageously can be operated and maintained by an entity that is the same as or different from the entities operating and maintaining the service networks 151 and 152. In ~ 65 accordance with an embodiment of an aspect of the present invention, the different IP-based services offered by the different service networks 151 and utilize shared layer one and layer two resources in the access network 120.
Layer three routing procedures, however, are modified to permit IP traffic from network access device 101 to flow to the correct subscribed service network 151. The 17o access network 120 has a muter 130 on the edge of the access network. The router 130 has a first interface with a connection to a router 141 in service network 151 and a second interface with a connection to a router 142 in service network 152. As further described herein, the router processes packets and is capable of directing traffic to the proper service network.
175 FIG. 2A shows an exemplary access architecture based on a hybrid fiber coaxial (HFC) access network. As is known in the art, each network interface device 201 ... 202 is either connected to or integrated with a cable modem 211 which enables communication through the HFC network 221. In accordance with the Data Over Cable Service Interface Specification (DOCSIS), a 18o Cable Modem Termination System (CMTS), shown as 225 in FIG. 2A, communicates with the cable modems 211 and manages access to both upstream and downstream cable capacity on the HFC networks 221. See, e.g., "Data-Over-Cable Service Interface Specifications: Cable Modem Termination System -Network Side Interface Specification," Cable Television Laboratories, Inc., SP-X85 CMTS-NSI-I01-960702; "Data-Over-Cable Service Interface Specifications:
Cable Modem to Customer Premise Equipment Interface Specification," Cable Television Laboratories, Inc., SP-CMCI-C02C-991015; "Data-Over-Cable Service Interface Specifications: Baseline Privacy Plus Interface Specifications,"
Cable Television Laboratories, Inc., SP-BPI+-I06-001215, which are incorporated 190 by reference herein. The CMTS 225 manages the scheduling of both upstream and downstream transmission and allocates cable capacity to individual customers identified by a Service IDs (SIDS). The CMTS 225 can have an integrated router 228 or can be a separate device 226 that bridges to a fast Ethernet switch 227 which connects to the muter 228. The IP muter 228 provides connectivity to an 195 IP network 222, which further comprises the muter 230 (corresponding to router 130 in FIG. 1) which interfaces to IP routers 241 and 242 in service networks and 252, respectively. Accordingly, the HFC network 221, the CMTS 225, and the IP network 222 correspond to the access network infrastructure 120 shown in FIG. 1. FIG. 2B shows a conceptual diagram of the end-to-end communication 20o protocol stack from a network access device 201 ( 101 ) to a router 241 ( 141 ) in service provider's network 251 (151). As is known in the art, the lowest layer deals with the physical layer (PL) of the protocol stack, e.g. the Ethernet physical media device (PMD) layer; the second layer deals with the data link layer, e.g. the Ethernet Media Access Control (MAC) layer; and the third layer in the protocol 205 stack deals with the network layer, e.g. the IP layer. The following aspects of the invention deal with modifications to routing processes in the network layer of the protocol stack.
Router 130 in the access network 120 in FIG. 1 (corresponding to IP router 230 in FIG. 2) separates the IP traffic to the multiple services or service 210 providers as well as combines traffic from the multiple services or service providers. In accordance with an aspect of the invention, IP packets are routed from network access device 101 to the subscribed service network 151 using source address-based policy routing. Conventional routing is destination-based:
the muter consults an internal routing table which maps the destination addresses 215 of all inbound packets to a physical interface address for use for outgoing packets.
Policy routing schemes, however, will selectively choose different paths for different packets even where the packet's destination address may be the same.
Since network access devices are assigned addresses associated with a particular network service provider, the source address based policy routing scheme ensures 22o packets from a network access device will go to the appropriate service network.
Conventional destination-based routing will ensure that packets addressed to a network access device will be routed to the appropriate service network. Note that this would require service providers to advertise their service address ranges to their peers.
225 FIG. 3 sets forth the processing performed at a muter in the access network, e.g. router 130 in FIG. 1. At step 301, the router receives an incoming packet. At step 302, the muter reads the packet header and retrieves the packet filtering rules, typically stored in an access list as further described below. At steps 303, 305, and 307, the router applies the packet filtering rules. At step 303, 23o the muter compares the source IP address in the packet header to a list of addresses allocated to subscribers of services of a first service provider, e.g.
operating service network 151 in FIG. 1. If the source address matches one of these addresses, then at step 304 the muter forwards the packet to a router in service network 151, e.g. router 141 in FIG. 1. At step 305, the router compares 235 the source IP address in the packet header to a list of addresses allocated to subscribers of services of a second service provider, e.g. operating service network 152 in FIG. 1. If the source IP address matches one of these addresses, then at step 305 the muter forwards the packet to a router in service network 152, e.g. muter 142 in FIG. 1. The muter continues in this fashion with any other 240 packet filtering rules identifying IP addresses allocated to subscribers of any other service providers. Assuming the IP source address does not match any such addresses associated with a service provider, at step 307, the muter applies any remaining packet filtering rules and routes or denies the packet accordingly.
FIG. 4 sets forth an example of router configuration instructions 245 written for the Cisco Internetworking Operating System (IOS), which is used pervasively on conventional IP routers. Only the relevant portions of the configuration instructions are shown. Lines 401 to 405 configure the interface to utilize policy routing. Lines 406 to 410 specify the particular policy, namely to set the next "hop" address to the router address of a router in a one of the service 25o networks, i.e. "ispl next-hop-address," if the source address matches a range of addresses allocated to subscribers of the services provided by the service network, i.e. "ispl-subs." Lines 412 to 413 set forth access lists associating "i sp 1-subs" with ranges of addresses expressed, by convention, as a source address and a mask portion, i.e., the above policy is applied by the router to any 255 traffic with a subscriber source address expressed as "ispl pref ixl" with a mask portion of "ispl pref ixl wildcard".
The embodiment shown in FIG. 1 notably requires interconnection points to all relevant service networks at each edge of each regional access network. In accordance with another aspect of the invention, it is desirable to 260 create a regional transport network of routers and to localize the interconnection between the service networks and the access infrastructure into managed access points. A managed access point is a physical location at which the interfaces to the service networks can be provided. Having one or a small plurality of managed access points advantageously allows service selection to be implemented without 265 requiring network service providers to connect physical facilities into, for example, every cable head end in an HFC-based network-thereby reducing costs for both the access network infrastructure operator and the service network providers. Each router in the regional transport network can be configured with policy information and invoke source address routing to forward packets to the 270 managed access point providing access to the relevant service network. By overriding normal routing procedures, however, these procedures may introduce potential routing loops absent significant coordination between the routers external to known routing protocols. This risk can be minimized by centralizing the policy routing function in a single muter that provides the interfaces to the 275 service networks.
FIG. 5 illustrates an embodiment of this aspect of the invention.
Each network access device 501 is connected through a network interface unit to one of a plurality of access networks, e.g. 521 and 522 in FIG. 5. Each access network has an edge router (531 and 532 respectively in FIG. 5) which connects 280 the access network to a regional IP network of routers, represented abstractly in FIG. 5 as IP access network 570. It is advantageous to aggregate connections from groups of edge routers to a single aggregation router 571 in the IP
access network 570, as shown in FIG. 5. Aggregation muter 571 can then connect to other routers in the regional IP network 570, i.e. routers 572 ... 573, which can 285 also be aggregation routers connecting to pluralities of edge routers.
Routers 541, 542, ... 543 in service networks 551, 552, ... 553 connect to the IP network 570 at routers 574 and 575, which act as managed access points to the service networks.
Only the managed access point routers, e.g. 575, need invoke policy routing based on packet source address. All intermediate routers within the IP access network 290 570, i.e. 571 ... 573, use normal destination-based forwarding procedures for destinations that are not local to the network 570. No configuration of policy in the intermediate routers is necessary.
By locating the policy routing functions at the interfaces to the service networks, the access network infrastructure (whether reflected generally 295 by 120 in FIG. 1 or, in the packet-switched context, as network 570 in FIG. 5) can provide access to "local" services available from within the access network infrastructure. For example, IP network 570 can provide access to "local"
packet-switched services and operate independent of the source address assigned to the network access devices. Since the intermediate routers 571 ... 573 all use 300 conventional destination-based forwarding, network 570 will properly route local service packets along the correct routing paths. "Non-local" service packets, however, are routed towards the managed access point routers 575 and 574 and policy routed to the correct service network. Where the network 570 forwards to a single managed access point muter or where each managed access point router 305 has a connection to each service network, the managed access point router can forward packets in accordance with the policies described above. Where, however, there are service networks that connect to only a subset of the managed access points (e.g., in FIG. 5, where service network 553 only connects to managed access point router 574), packets can be redirected or "tunneled" to the 31o correct managed access point in order to ensure that the packets arrive at the correct service network. The multiple interconnected managed access points can then provide a single "logical" inter-domain gateway, again permitting all other routers to use conventional destination-based routing procedures.
FIG. 6 sets forth a flowchart of the processing performed at a 3~5 managed access point router, e.g. muter 575 in FIG. 5, illustrating an embodiment of this aspect of the invention. The particular managed access point router 575 is assumed to be connected to two service networks, e.g. service networks 551 and 552 in FIG. 5, while a second managed access point router 574 provides access to a third service network, service network 553. At step 601, the muter receives an 320 incoming packet. At step 602, the router reads the packet header and retrieves the packet filtering rules, as well as decapsulates any encapsulated packets, as further described herein. At steps 603, 605, 607, and 609, the router applies the packet filtering rules. At step 603, the router compares the source IP address in the packet header to a list of addresses allocated to subscribers of services of a first 325 service provider, e.g. operating service network 551 in FIG. 5. If the source address matches one of these addresses, then at step 604 the muter forwards the packet to a muter in service network 551, e.g. muter 541 in FIG. 5. At step 605, the router compares the source IP address in the packet header to a list of addresses allocated to subscribers of services of a second service provider, e.g.
330 operating service network 552 in FIG. 5. If the source IP address matches one of these addresses, then at step 606 the router forwards the packet to a muter in service network 552, e.g. muter 542 in FIG. 5. At step 607, the router compares the source IP address in the packet header to a list of addresses allocated to subscribers of services of a third service provider, e.g. operating service network 335 553 in FIG. 5, which is not connected to this particular managed access point. If the source IP address matches one of these addresses, then at step 608, the router encapsulates the packet, using any of a number of known methods for packet encapsulation, and routes the packet to a new destination address, namely the address of the managed access point with access to service network 553, i.e.
34o managed access point router 574. Packet encapsulation is a method by which a packet may rerouted to an intermediate destination other than the destination that would be selected using normal routing procedures. See, e.g., C. Perkins, "IP
Encapsulation within IP," IETF Network Working Group, RFC 2003 (October 1996); C. Perkins, "Minimal Encapsulation within IP," IETF Network Working 345 Group, RFC 2004 (October 1996), which are incorporated by reference herein.
The receiving router 574 will decapsulate the packet and route the packet, accordingly, to service network 553. The muter continues in this fashion with any other packet filtering rules identifying IP addresses associated with any other service providers. Assuming the IP source address does not match any addresses 350 associated with any other service providers, at step 609, the router applies any remaining packet filtering rules and routes or denies the packet accordingly.
Note that if managed access point 575 has a direct physical connection to managed access point 574, then no encapsulation is needed. In fact, a typical configuration might include multiple port-constrained policy routers on a GIG Ethernet 355 providing the logical managed access point function without any encapsulation.
Encapsulation is only really needed to provide a logical direct connection if there is not a direct physical connection.
Packets traveling between network access devices connected to the same access network infrastructure can be forwarded directly between the devices 360 in the access network - rather than forwarding the packets outwards to a service network and back to the same access network. This advantageously saves on bandwidth and other network resources. The only packets that need be routed to a managed access point muter need be the ones for which no specific route is known internally to the access network infrastructure.
365 It is advantageous to enable the IP addresses-which ultimately determine the service network utilized by the particular network access device-to be allocated and reassigned dynamically. With reference to FIG. 1, a service activation system 160 is shown which further comprises a configuration server WO 01/71983 PCT/USOl/08849 161 and a registration server 162 connected to the access network infrastructure 370 120. The registration server 162 provides a network-based subscription/authorization process for the various services shared on the access network infrastructure 120. A customer desiring to subscribe to a new service can access and provide registration information to the registration server 162, e.g. by using HTML forms and the Hyper Text Transfer Protocol (HTTP) as is known in 375 the art. Upon successful service subscription, the registration server 162 updates a customer registration database 163. The configuration server 161 uses the registration information to activate the service. The configuration server 161 is responsible for allocating network addresses on behalf of the service networks from a network address space associated with the selected service. In a preferred 380 embodiment of this aspect of the invention, the configuration server 161 uses a host configuration protocol such as the Dynamic Host Configuration Protocol (DHCP) to configure the network addresses of the network access devices. See R. Droms, "Dynamic Host Configuration Protocol," IETF Network Working Group, RFC 2131 (March 1997); S. Alexander, R. Droms, "DHCP Options and 385 BOOTP Vendor Extensions," IETF Network Working Group, RFC 2132 (March 1997); which are incorporated by reference herein. This aspect of the invention shall be described herein with particular reference to DHCP, and the configuration server 161 shall be referred to herein as the DHCP server, although those skilled in the art would readily be able to implement this aspect of the invention using a 39o different protocol.
FIG. 7 is a simplified timeline diagram of DHCP messages exchanged as the DHCP server 720 assigns a service-specific network address to a network access device 710 acting as a DHCP client. At 701, the network access device 710 sends a DHCPDISCOVER message through the access network 395 infrastructure. The DHCPDISCOVER message, in accordance with an aspect of the invention, includes a "svc-id" option field that identifies the service to which the network access device has been subscribed and from which service is desired.
The DHCP server 720 receives the DHCPDISCOVER message and, at 702, allocates an IP address from the pool of addresses associated with the particular 40o service. The DHCP server 720 can use the device's MAC address to lookup the customer's registration information and confirm that the device is authorized to access the identified service. Where the DHCP server 720 cannot find the device's MAC address in the registration database, the server can allocate a special IP address that only allows access to the registration server. At 703, the 405 DHCP server 720 responds with a DHCPOFFER message that includes the IP
address in a field in the DHCP message. At 704, the network access device 710 receives the DHCPOFFER (and any other offers from any other DHCP servers in the access network) and sends out a DHCPREQUEST directed to the DHCP
server which requests the IP address identified in the DHCPOFFER. At 707, the 410 DHCP server commits to assigning the IP address to the network access device, commits the binding to persistent storage, and transmits a DHCPACK message containing the configuration parameters for the device. If the DHCP server is unable to satisfy the DHCPREQUEST message, the server responds with a DHCPNAK message. FIG. 8 is a simplified representation of the fields in a 4 ~ 5 DHCP message, including a "svc-id" option field (820) which identifies the selected service.
It is preferable that the DHCP servers and clients use some mutual authentication mechanism to restrict address assignment to authorized hosts and to prevent clients from accepting addresses from invalid DHCP servers. See, for 42o example, the "delayed authentication" scheme described in R. Droms, W.
Arbaugh, "Authentication for DHCP Messages," IETF Network Working Group, Internet Draft, <draft-ietf-dhc-authentication--.txt>; or the Kerberos-based authentication mechanism described in K. Hornstein, T. Lemon, B. Aboba, J.
Trostle, "DHCP Authentication via Kerberos V," IETF Network Working Group, 425 Internet Draft, <draft-hornstein-dhc-kerbauth ->; which are incorporated by reference herein. The "delayed authentication" mechanism supports mutual authentication of DHCP clients and servers based on a shared secret, which may be provisioned using out-of-band mechanisms. On the other hand, the Kerberos-based mechanisms are very well suited for inter-realm authentication, thereby 43o supporting client mobility, i.e. a network access device could connect to a m particular access network infrastructure without any prior registration with the access network. Each service network provider could securely authenticate the network access device accessing the service network from another network "realm," e.g. the access network infrastructure.
435 The operator of the relevant service network, e.g. service network 152 in FIG. l, may desire to maintain a separate registration server, e.g.
server 155 in FIG. 1, and to retain responsibility for user authentication and authorization. The service activation system 160 can provide a proxy server configured to permits HTTP traffic only between local hosts and registration 440 server 155 in service network 152. The service provider operating service network 152 would then be responsible for providing the appropriate registration information required for proper service selection to the service activation system 160. The service provider would also be responsible for notifying the service activation system 160 when service should be discontinued. Alternatively, the 445 DHCP server 161 in the service activation system 160 can interact with the registration server 155 using a back-end authentication protocol, e.g. the Remote Authentication Dial In User Service (RADIUS). See C. Rigney, A. Rubens, W.
Simpson, S. Willens, "Remote Authentication Dial In User Service (RADIUS),"
IETF Network Working Group, RFC 2058 (January 1997), which is incorporated 45o by reference herein. The DHCP server can contain a RADIUS client and, thereby, leverage the large RADIUS embedded base used for dial access authentication.
FIG. 9 illustrates this embodiment of this aspect of the invention in a flowchart corresponding to the flowchart shown in FIG. 7. At 903, the DHCP server 920 generates a random challenge and includes the challenge along with the allocated 455 IP address in the DHCPOFFER message. The DHCP client 910 generates a response to the challenge by encrypting the challenge with a key that is derived from the subscriber's authentication information. At 904, the client 910 includes the challenge, response, and IP address in the DHCPREQUEST message. The DHCP server 920 forwards both the challenge and response in a 46o RADIUS ACCESS REQ message to a RADIUS server 930 in the selected service network. The RADIUS server 930 either accepts or rejects the RADIUS
2 PCT/USOi/08846 request and responds accordingly at 906. If the RADIUS request is accepted, the DHCP server 920 sends a DHCPACK message at 907 and the client 910 enters a bound state. If the RADIUS request is rejected, the DHCP server 920 sends a 465 DHCPNACK message which informs the client 910 that the IP address that was allocated has been withdrawn.
Rather than modifying the DHCP protocol in order to establish the association between the device's MAC address and the service selection, it is advantageous to use an alternative two-step process. The registration server 470 can associate the customer's IP address (used for registration) with the subscribed service, while the configuration server 161 can associate the customer's IP
address with the customer's MAC address. The servers can interact and share their associations in the registration database 163 shown in FIG. 1. Thus, the subscriber can register the service selection with the registration server which 475 temporarily establishes the association between the network access device's hardware address (e.g. the MAC address of the device) and the chosen service selection. The configuration server then uses the MAC address of the network access device to assign an IP address from the proper address space. FIG. 10 is a simplified timeline diagram of DHCP messages exchanged, in accordance with 48o such an embodiment. At 1001, the network access device 1010 registers a service selection with the registration server 1030. It is assumed that the subscriber has passed the proper authentication procedures for the particular service selected, either beforehand (e.g. through transactions directly with the service provider's network) or in the same session with the registration server. The registration 485 server 1030 sends some acknowledgment 1002 to the network access device 1010.
At 1003, the registration server 1030 stores the selected service and associates the service selection with the hardware device address (e.g. MAC address) of the network access device 1010. After receiving the acknowledgment from the registration server 1030, the network access device 1010 releases any pre-existing 49o address assignment by issuing a DHCPRELEASE message at 1004. At 1005, the network access device issues a standard DHCPDISCOVER message (i.e., there is no need for the service selection id in the message set forth above). The DHCP
~6 server 1020 receives the DHCPDISCOVER message and, at 1006, allocates an IP
address from the pool of address associated with the particular service associated 495 with the device's hardware address. At 1007, the DHCP server 1020 sends a DHCPOFFER message that includes the IP address in a field in the DHCP
message. At 1008, the network access device 1010 receives the DHCPOFFER
and sends out a DHCPREQUEST back to the DHCP server 1030. At 1009, the DHCP server 1030 commits to assigning the IP address to the network access 500 device 1010, commits the binding to persistent storage, and transmits a DHCPACK message containing the configuration parameters for the device.
It is desirable to restrict access to the access network infrastructure to those network access devices that are properly registered and authenticated. In accordance with another aspect of the invention, the access network infrastructure 505 can be configured to perform access control taking advantage of the above described address allocation process. An access network infrastructure with broadcast capabilities will often use a protocol such as the Address Resolution Protocol (ARP) to map network layer addresses used by the packet-switched networks to the hardware addresses used in the datalink layer of the access 510 network infrastructure. See, e.g., D. Plummer, "An Ethernet Address Resolution Protocol," IETF Network Working Group, RFC 826 (November 1982). For example, and with reference to the HFC embodiment shown in FIG. 2, the CMTS
225 has an ARP cache, which is a table of entries storing bindings between IP
addresses and the hardware MAC addresses assigned to network access devices 515 201, 202. The ARP cache permits the CMTS to learn the correspondence between IP addresses and MAC addresses without resorting to broadcasting an ARP
request. As is known in the art, the CMTS can act as a DHCP relay agent and use information in DHCP messages to populate its ARP cache. This mechanism, in combination with the DHCP address allocation process described above, can be 520 advantageously utilized to control access to the network.
With reference to FIG. 7 (and FIG. 9), the CMTS acts as a DHCP
relay agent and snoops on DHCP messages exchanged between the host acting as a DHCP client and the DHCP server. At step 707 in FIG. 7 and step 907 in FIG.
9, the DHCP server issues a DHCPACK message with configuration parameters 525 including the committed IP address allocated to the subscriber to the particular service selected, as described above. This only occurs after the proper authentication steps have been performed. FIG. 11 is a flowchart illustrating the processing performed at the CMTS. At step 1101, the CMTS receives the DHCP
message and proceeds to snoop on its contents in the process of relaying it to the 53o proper DHCP client at step 1106. At step 1102, the CMTS determines that the DHCP message is a DHCPACK message by examining the options field of the DHCP message. At step 1103, the CMTS proceeds to read the information from the DHCPACK message, in particular the "yiaddr" and "chaddr" fields (fields and 808 in FIG. 8) which indicate the assigned IP address and the hardware MAC
535 address respectively. The CMTS updates the ARP cache to reflect the mapping of IP address to MAC address (and SID) used for communication with the subscriber. Thereafter, the CMTS permits upstream and downstream packets to and from the particular network access device based on the ARP cache entry.
Where there has been a failure in authentication, this will result in a failure to 540 update the ARP cache and in a denial of access to the access network infrastructure. The information in the ARP cache entry can also be utilized by the CMTS to monitor attempts to "spoof' the IP address of an authenticated subscriber: e.g., by refusing to forward upstream packets with a source IP
address that is not associated with the proper SID or MAC address. The CMTS can set 545 the timeout for the ARP cache entry to the same value as the timeout for the IP
address specified in the DHCP exchange. If a customer subsequently releases the IP address by issuing a DHCPRELEASE message (or declines to accept the offered IP address, both at step 1104), the CMTS flushes the corresponding ARP
cache entry upon receipt of the DHCP message at step 1105.
550 The DHCP server should be configured to ensure that every response that changes an IP address assignment or a lease on a DHCP assignment gets relayed to the CMTS. For example, a network access device using standard DHCP can send a DHCPRENEW message directly to the DHCP server. The DHCP server would respond directly to the client, and the CMTS would not 555 perform a DHCP relay function for these messages. Such direct communication between the DHCP client and server may modify information (e.g. lease time) used by the CMTS to manage the ARP cache. Therefore, it is advantageous to modify the DHCP server so that it will notify the CMTS of any changes to IP
address assignment including lease time. This can be accomplished, for example, 56o by sending all responses to the CMTS to relay to the client-rather than sending them directly to the client.
It is advantageous for the access network infrastructure to support quality-of-support, in particular to differentiate service between subscribers to different services or service providers. For example, with reference to FIG.
1, a 565 subscriber to services offered by a service network 151 could get a higher share of access link capacity in the access network infrastructure than a subscriber to services offered by service network 152. Likewise, the aggregate capacity for subscribers to service network 151 may be different (e.g. higher) than aggregate capacity for subscribers to service network 152. It is preferable to avoid relying 570 on the network access devices 101...104 or the network interface units 111...114 to enforce service policies. Instead, it is advantageous for the access network infrastructure to have a policy engine, referred to herein as a policy decision point, and points at which policies may be enforced. The policy decision point, for example, could be a server in the service activation system 160 in the access 575 network infrastructure with access to the relevant registration information for subscribers. The policy decision preferably should be made at a point at which the association between the service network and the access network has been established, e.g. when the authenticated IP address is provided to the network access device as described above. The service class assignment would reflect the 580 results of negotiation between the entity operating the access network infrastructure and the entity operating the service network.
FIG. 12, for example, sets forth a timeline diagram of messages exchanged in assigning a service class to a subscriber, in the context of the particular HFC architecture described above. At 1201, the network access device 585 1210 sends the DHCPREQUEST message to the DHCP server 1250, requesting the service-related IP address identified in a previous DHCPOFFER message. At 1202, the DHCP server 1250 commits to assigning the IP address to the network access device 1210 and transmits a DHCPACK message containing the configuration parameters for the device. At 1203, the DHCP server 1250 sends a 590 message to a Policy Decision Point ("PDP") 1240 authorizing assignment of a particular service class to the subscriber. The PDP 1240 transmits traffic parameters for the authorized service flow to the CMTS 1230, which receives the policy parameters at 1204 and begins the process of Dynamic Service Addition (DSA) in accordance with DOCSIS to schedule the service flow. A service flow, 595 as defined by DOCSIS, is a unidirectional flow of packets that is provided a particular quality of service. At 1205, the CMTS 1230 sends a dynamic service addition request (DSA-REQ) message to the cable modem 1220 attached to the relevant network access device 1210. At 1206, the cable modem 1220 sends a dynamic service addition response (DSA-RSP) message after confirming that the 600 cable modem 1220 can support the service flow. At 1207, the CMTS 1230 sends a dynamic service addition acknowledge (DSA-ACK) message after enabling transmission and reception of data on the new service flow. At 1208, the service flow has been allocated, and transmission on the new service flow has been enabled. At 1209, the network access device 1210 can begin transmitting data 605 upstream to the CMTS 1230 which, as described above, forwards the data to the relevant packet-switched network.
Where the packet-switched network also provides for differentiation in service, e.g. based on the "DiffServ" framework, the cable modem 1220 can mark the Type Of Service (TOS) field of the packet to indicate 610 the service class for the packet. See K. Nichols, S. Blake, F. Baker, D.
Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers," IETF Network Working Group, RFC 2474 (December 1998); S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W. Weiss, "An Architecture for Differentiated Services," IETF Network Working Group, RFC 2475 (December 615 1998), which are incorporated by reference herein. Using the policy information received from the PDP 1240, the CMTS 1230 can act as a policy enforcement ?o point and police the packets received from the cable modem 1220 and remark the TOS field of the packet where there is any deviation from the policy specified for the particular subscriber. Similarly, the CMTS 1230 can police service flows in 62o the downstream direction, again based on the policy provided by the PDP
1240.
The CMTS 1230 performs scheduling based on the policies provided by the PDP 1240. Scheduling can be based on differentiation between subscribers to different services or service providers and can also be used to ensure that reserved minimum traffic rate requirements are met (this may require 625 some measurement of capacity allocated to different subscribers as well as an accounting of bandwidth usage). One method of scheduling in the CMTS is to follow class based queuing (CBQ). See S. Floyd, V. Jacobson, "Link-Sharing and Resource Management Models for Packet Networks," IEEE/ACM Transactions on Networking, Vol. 3, No. 4, August 1995, which is incorporated by reference 630 herein. CBQ allows for support of quality-of-support and flexible link sharing.
The mechanism can be used to share capacity of a link across services, protocol families and/or traffic types. It can be used to allocate "shares" to individual service providers and subdivide the share amongst the subscribers of a given service provider. For example, arriving packet flows are aggregated into classes, 635 each class having a "priority" and a throughput allocation. The traditional method is to use the information in the packet header, although it is possible, in the HFC
architecture, to classify based on SID and the policy set up at the time the service flow is setup. A hierarchy of classes is constructed, e.g. as depicted in FIG.
13.
The access link 1300 is shared between three service providers 1351, 1352, and 640 1353. Each service provider shares its allocation of link bandwidth among its customers, i.e., 1311, 1312, 1313 being subscribers of service provider 1351;
1321, 1322 being subscribers of 1352; 1331 being a subscriber of service provider 1353. The link scheduler may associate weights for each service provider. The service provider "weight" determines the overall share of access link bandwidth to 645 all subscribers of the service provider, when the link is fully utilized.
The link scheduler further allocates weights to each customer of the service provider-the customer's weight determining the share of the service provider's link bandwidth 2~
available to the subscriber. It can then be possible to "borrow" bandwidth from other service provider subscribers when the service provider's share is not fully 650 subscribed, as well as from other service providers when the link is not fully loaded. It is advantageous for the scheduling to provide such flexible sharing.
When the link is underloaded, there is no need for any regulation of access to the HFC link by active SIDS. The scheduler can regulate a particular customer, e.g.
by postponing giving grants to a SID of the customer, only when the customer is 655 over the limit in terms of bandwidth share during the short-term interval.
The foregoing Detailed Description is to be understood as being in every respect illustrative and exemplary, but not restrictive, and the scope of the invention disclosed herein is not to be determined from the Detailed Description, but rather from the claims as interpreted according to the full breadth permitted by 660 the patent laws. It is to be understood that the embodiments shown and described herein are only illustrative of the principles of the present invention and that various modifications may be implemented by those skilled in the art without departing from the scope and spirit of the invention. For example, the detailed description describes an embodiment of the invention with particular reference to 665 an HFC access network architecture. However, the principles of the present invention could be readily extended to other access network architectures, such as DSL, wireless, satellite, etc. Such an extension could be readily implemented by one of ordinary skill in the art given the above disclosure.
Rather than modifying the DHCP protocol in order to establish the association between the device's MAC address and the service selection, it is advantageous to use an alternative two-step process. The registration server 470 can associate the customer's IP address (used for registration) with the subscribed service, while the configuration server 161 can associate the customer's IP
address with the customer's MAC address. The servers can interact and share their associations in the registration database 163 shown in FIG. 1. Thus, the subscriber can register the service selection with the registration server which 475 temporarily establishes the association between the network access device's hardware address (e.g. the MAC address of the device) and the chosen service selection. The configuration server then uses the MAC address of the network access device to assign an IP address from the proper address space. FIG. 10 is a simplified timeline diagram of DHCP messages exchanged, in accordance with 48o such an embodiment. At 1001, the network access device 1010 registers a service selection with the registration server 1030. It is assumed that the subscriber has passed the proper authentication procedures for the particular service selected, either beforehand (e.g. through transactions directly with the service provider's network) or in the same session with the registration server. The registration 485 server 1030 sends some acknowledgment 1002 to the network access device 1010.
At 1003, the registration server 1030 stores the selected service and associates the service selection with the hardware device address (e.g. MAC address) of the network access device 1010. After receiving the acknowledgment from the registration server 1030, the network access device 1010 releases any pre-existing 49o address assignment by issuing a DHCPRELEASE message at 1004. At 1005, the network access device issues a standard DHCPDISCOVER message (i.e., there is no need for the service selection id in the message set forth above). The DHCP
~6 server 1020 receives the DHCPDISCOVER message and, at 1006, allocates an IP
address from the pool of address associated with the particular service associated 495 with the device's hardware address. At 1007, the DHCP server 1020 sends a DHCPOFFER message that includes the IP address in a field in the DHCP
message. At 1008, the network access device 1010 receives the DHCPOFFER
and sends out a DHCPREQUEST back to the DHCP server 1030. At 1009, the DHCP server 1030 commits to assigning the IP address to the network access 500 device 1010, commits the binding to persistent storage, and transmits a DHCPACK message containing the configuration parameters for the device.
It is desirable to restrict access to the access network infrastructure to those network access devices that are properly registered and authenticated. In accordance with another aspect of the invention, the access network infrastructure 505 can be configured to perform access control taking advantage of the above described address allocation process. An access network infrastructure with broadcast capabilities will often use a protocol such as the Address Resolution Protocol (ARP) to map network layer addresses used by the packet-switched networks to the hardware addresses used in the datalink layer of the access 510 network infrastructure. See, e.g., D. Plummer, "An Ethernet Address Resolution Protocol," IETF Network Working Group, RFC 826 (November 1982). For example, and with reference to the HFC embodiment shown in FIG. 2, the CMTS
225 has an ARP cache, which is a table of entries storing bindings between IP
addresses and the hardware MAC addresses assigned to network access devices 515 201, 202. The ARP cache permits the CMTS to learn the correspondence between IP addresses and MAC addresses without resorting to broadcasting an ARP
request. As is known in the art, the CMTS can act as a DHCP relay agent and use information in DHCP messages to populate its ARP cache. This mechanism, in combination with the DHCP address allocation process described above, can be 520 advantageously utilized to control access to the network.
With reference to FIG. 7 (and FIG. 9), the CMTS acts as a DHCP
relay agent and snoops on DHCP messages exchanged between the host acting as a DHCP client and the DHCP server. At step 707 in FIG. 7 and step 907 in FIG.
9, the DHCP server issues a DHCPACK message with configuration parameters 525 including the committed IP address allocated to the subscriber to the particular service selected, as described above. This only occurs after the proper authentication steps have been performed. FIG. 11 is a flowchart illustrating the processing performed at the CMTS. At step 1101, the CMTS receives the DHCP
message and proceeds to snoop on its contents in the process of relaying it to the 53o proper DHCP client at step 1106. At step 1102, the CMTS determines that the DHCP message is a DHCPACK message by examining the options field of the DHCP message. At step 1103, the CMTS proceeds to read the information from the DHCPACK message, in particular the "yiaddr" and "chaddr" fields (fields and 808 in FIG. 8) which indicate the assigned IP address and the hardware MAC
535 address respectively. The CMTS updates the ARP cache to reflect the mapping of IP address to MAC address (and SID) used for communication with the subscriber. Thereafter, the CMTS permits upstream and downstream packets to and from the particular network access device based on the ARP cache entry.
Where there has been a failure in authentication, this will result in a failure to 540 update the ARP cache and in a denial of access to the access network infrastructure. The information in the ARP cache entry can also be utilized by the CMTS to monitor attempts to "spoof' the IP address of an authenticated subscriber: e.g., by refusing to forward upstream packets with a source IP
address that is not associated with the proper SID or MAC address. The CMTS can set 545 the timeout for the ARP cache entry to the same value as the timeout for the IP
address specified in the DHCP exchange. If a customer subsequently releases the IP address by issuing a DHCPRELEASE message (or declines to accept the offered IP address, both at step 1104), the CMTS flushes the corresponding ARP
cache entry upon receipt of the DHCP message at step 1105.
550 The DHCP server should be configured to ensure that every response that changes an IP address assignment or a lease on a DHCP assignment gets relayed to the CMTS. For example, a network access device using standard DHCP can send a DHCPRENEW message directly to the DHCP server. The DHCP server would respond directly to the client, and the CMTS would not 555 perform a DHCP relay function for these messages. Such direct communication between the DHCP client and server may modify information (e.g. lease time) used by the CMTS to manage the ARP cache. Therefore, it is advantageous to modify the DHCP server so that it will notify the CMTS of any changes to IP
address assignment including lease time. This can be accomplished, for example, 56o by sending all responses to the CMTS to relay to the client-rather than sending them directly to the client.
It is advantageous for the access network infrastructure to support quality-of-support, in particular to differentiate service between subscribers to different services or service providers. For example, with reference to FIG.
1, a 565 subscriber to services offered by a service network 151 could get a higher share of access link capacity in the access network infrastructure than a subscriber to services offered by service network 152. Likewise, the aggregate capacity for subscribers to service network 151 may be different (e.g. higher) than aggregate capacity for subscribers to service network 152. It is preferable to avoid relying 570 on the network access devices 101...104 or the network interface units 111...114 to enforce service policies. Instead, it is advantageous for the access network infrastructure to have a policy engine, referred to herein as a policy decision point, and points at which policies may be enforced. The policy decision point, for example, could be a server in the service activation system 160 in the access 575 network infrastructure with access to the relevant registration information for subscribers. The policy decision preferably should be made at a point at which the association between the service network and the access network has been established, e.g. when the authenticated IP address is provided to the network access device as described above. The service class assignment would reflect the 580 results of negotiation between the entity operating the access network infrastructure and the entity operating the service network.
FIG. 12, for example, sets forth a timeline diagram of messages exchanged in assigning a service class to a subscriber, in the context of the particular HFC architecture described above. At 1201, the network access device 585 1210 sends the DHCPREQUEST message to the DHCP server 1250, requesting the service-related IP address identified in a previous DHCPOFFER message. At 1202, the DHCP server 1250 commits to assigning the IP address to the network access device 1210 and transmits a DHCPACK message containing the configuration parameters for the device. At 1203, the DHCP server 1250 sends a 590 message to a Policy Decision Point ("PDP") 1240 authorizing assignment of a particular service class to the subscriber. The PDP 1240 transmits traffic parameters for the authorized service flow to the CMTS 1230, which receives the policy parameters at 1204 and begins the process of Dynamic Service Addition (DSA) in accordance with DOCSIS to schedule the service flow. A service flow, 595 as defined by DOCSIS, is a unidirectional flow of packets that is provided a particular quality of service. At 1205, the CMTS 1230 sends a dynamic service addition request (DSA-REQ) message to the cable modem 1220 attached to the relevant network access device 1210. At 1206, the cable modem 1220 sends a dynamic service addition response (DSA-RSP) message after confirming that the 600 cable modem 1220 can support the service flow. At 1207, the CMTS 1230 sends a dynamic service addition acknowledge (DSA-ACK) message after enabling transmission and reception of data on the new service flow. At 1208, the service flow has been allocated, and transmission on the new service flow has been enabled. At 1209, the network access device 1210 can begin transmitting data 605 upstream to the CMTS 1230 which, as described above, forwards the data to the relevant packet-switched network.
Where the packet-switched network also provides for differentiation in service, e.g. based on the "DiffServ" framework, the cable modem 1220 can mark the Type Of Service (TOS) field of the packet to indicate 610 the service class for the packet. See K. Nichols, S. Blake, F. Baker, D.
Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers," IETF Network Working Group, RFC 2474 (December 1998); S. Blake, D. Black, M. Carlson, E. Davies, Z. Wang, W. Weiss, "An Architecture for Differentiated Services," IETF Network Working Group, RFC 2475 (December 615 1998), which are incorporated by reference herein. Using the policy information received from the PDP 1240, the CMTS 1230 can act as a policy enforcement ?o point and police the packets received from the cable modem 1220 and remark the TOS field of the packet where there is any deviation from the policy specified for the particular subscriber. Similarly, the CMTS 1230 can police service flows in 62o the downstream direction, again based on the policy provided by the PDP
1240.
The CMTS 1230 performs scheduling based on the policies provided by the PDP 1240. Scheduling can be based on differentiation between subscribers to different services or service providers and can also be used to ensure that reserved minimum traffic rate requirements are met (this may require 625 some measurement of capacity allocated to different subscribers as well as an accounting of bandwidth usage). One method of scheduling in the CMTS is to follow class based queuing (CBQ). See S. Floyd, V. Jacobson, "Link-Sharing and Resource Management Models for Packet Networks," IEEE/ACM Transactions on Networking, Vol. 3, No. 4, August 1995, which is incorporated by reference 630 herein. CBQ allows for support of quality-of-support and flexible link sharing.
The mechanism can be used to share capacity of a link across services, protocol families and/or traffic types. It can be used to allocate "shares" to individual service providers and subdivide the share amongst the subscribers of a given service provider. For example, arriving packet flows are aggregated into classes, 635 each class having a "priority" and a throughput allocation. The traditional method is to use the information in the packet header, although it is possible, in the HFC
architecture, to classify based on SID and the policy set up at the time the service flow is setup. A hierarchy of classes is constructed, e.g. as depicted in FIG.
13.
The access link 1300 is shared between three service providers 1351, 1352, and 640 1353. Each service provider shares its allocation of link bandwidth among its customers, i.e., 1311, 1312, 1313 being subscribers of service provider 1351;
1321, 1322 being subscribers of 1352; 1331 being a subscriber of service provider 1353. The link scheduler may associate weights for each service provider. The service provider "weight" determines the overall share of access link bandwidth to 645 all subscribers of the service provider, when the link is fully utilized.
The link scheduler further allocates weights to each customer of the service provider-the customer's weight determining the share of the service provider's link bandwidth 2~
available to the subscriber. It can then be possible to "borrow" bandwidth from other service provider subscribers when the service provider's share is not fully 650 subscribed, as well as from other service providers when the link is not fully loaded. It is advantageous for the scheduling to provide such flexible sharing.
When the link is underloaded, there is no need for any regulation of access to the HFC link by active SIDS. The scheduler can regulate a particular customer, e.g.
by postponing giving grants to a SID of the customer, only when the customer is 655 over the limit in terms of bandwidth share during the short-term interval.
The foregoing Detailed Description is to be understood as being in every respect illustrative and exemplary, but not restrictive, and the scope of the invention disclosed herein is not to be determined from the Detailed Description, but rather from the claims as interpreted according to the full breadth permitted by 660 the patent laws. It is to be understood that the embodiments shown and described herein are only illustrative of the principles of the present invention and that various modifications may be implemented by those skilled in the art without departing from the scope and spirit of the invention. For example, the detailed description describes an embodiment of the invention with particular reference to 665 an HFC access network architecture. However, the principles of the present invention could be readily extended to other access network architectures, such as DSL, wireless, satellite, etc. Such an extension could be readily implemented by one of ordinary skill in the art given the above disclosure.
Claims (12)
1. A method of assigning a network address to a network access device connected to an access network infrastructure connected to a plurality of service networks, comprising the steps of:
receiving a request from a subscriber operating a network access device selecting a service provided by a service network and subscribed to by the subscriber;
allocating a network address from a pool of addresses allocated to subscribers of the service;
assigning the network address to the network access device using a host configuration protocol wherein the network address is utilized by the access network infrastructure to forward packets from the network access device to the service network providing the selected service.
receiving a request from a subscriber operating a network access device selecting a service provided by a service network and subscribed to by the subscriber;
allocating a network address from a pool of addresses allocated to subscribers of the service;
assigning the network address to the network access device using a host configuration protocol wherein the network address is utilized by the access network infrastructure to forward packets from the network access device to the service network providing the selected service.
2. The invention of claim 1 wherein the host configuration protocol is DHCP.
3. The invention of claim 1 further comprising the step of authenticating the subscriber before assigning the network address to the network access device.
4. The invention of claim 1 wherein the service networks utilize the Internet Protocol and wherein the addresses are Internet Protocol addresses.
5. The invention of claim 4 wherein the plurality of service networks are operated by different Internet Service Providers.
6. The invention of claim 4 wherein the plurality of service networks offer access to different Internet Protocol-based services.
7. A method of assigning a network address to a network access device connected to an access network infrastructure connected to a plurality of service networks comprising the steps of:
receiving a request from a subscriber operating a network access device selecting a service provided by a service network and to which the subscriber is subscribed;
allocating a network address from a pool of addresses allocated to subscribers of the service;
receiving authentication information from the subscriber;
transmitting the authentication information to the service network;
if the service network authenticates the subscriber, assigning the network address to the network access device using a host configuration protocol, wherein the network address is utilized by the access network to forward packets from the network access device to the service network providing the selected service.
receiving a request from a subscriber operating a network access device selecting a service provided by a service network and to which the subscriber is subscribed;
allocating a network address from a pool of addresses allocated to subscribers of the service;
receiving authentication information from the subscriber;
transmitting the authentication information to the service network;
if the service network authenticates the subscriber, assigning the network address to the network access device using a host configuration protocol, wherein the network address is utilized by the access network to forward packets from the network access device to the service network providing the selected service.
8. The invention of claim 7 wherein the host configuration protocol is DHCP.
9. The invention of claim 7 wherein the service network authenticates the subscriber using RADIUS protocol.
10. The invention of claim 7 wherein the service networks utilize the Internet Protocol and wherein the addresses are Internet Protocol addresses.
11. The invention of claim 7 wherein the plurality of service networks are operated by different Internet Service Providers.
12. The invention of claim 7 wherein the plurality of service networks offer access to different Internet Protocol-based services.
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US19063600P | 2000-03-20 | 2000-03-20 | |
US19063300P | 2000-03-20 | 2000-03-20 | |
US60/190,633 | 2000-03-20 | ||
US60/190,636 | 2000-03-20 | ||
PCT/US2001/008849 WO2001071983A1 (en) | 2000-03-20 | 2001-03-20 | Service selection in a shared access network using dynamic host configuration protocol |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2403736A1 true CA2403736A1 (en) | 2001-09-27 |
Family
ID=26886284
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002403628A Expired - Fee Related CA2403628C (en) | 2000-03-20 | 2001-03-20 | Service selection in a shared access network using policy routing |
CA002403736A Abandoned CA2403736A1 (en) | 2000-03-20 | 2001-03-20 | Service selection in a shared access network using dynamic host configuration protocol |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002403628A Expired - Fee Related CA2403628C (en) | 2000-03-20 | 2001-03-20 | Service selection in a shared access network using policy routing |
Country Status (4)
Country | Link |
---|---|
US (7) | US20020013844A1 (en) |
AU (2) | AU2001250888A1 (en) |
CA (2) | CA2403628C (en) |
WO (2) | WO2001071983A1 (en) |
Families Citing this family (292)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7529856B2 (en) * | 1997-03-05 | 2009-05-05 | At Home Corporation | Delivering multimedia services |
US6370571B1 (en) | 1997-03-05 | 2002-04-09 | At Home Corporation | System and method for delivering high-performance online multimedia services |
CA2442592C (en) * | 2000-03-29 | 2009-12-22 | Transcept Opencell, Inc. | Operations and maintenance architecture for multiprotocol distributed system |
US20020022483A1 (en) * | 2000-04-18 | 2002-02-21 | Wayport, Inc. | Distributed network communication system which allows multiple wireless service providers to share a common network infrastructure |
US6842459B1 (en) | 2000-04-19 | 2005-01-11 | Serconet Ltd. | Network combining wired and non-wired segments |
US20010034831A1 (en) * | 2000-04-19 | 2001-10-25 | Brustoloni Jose C. | Method and apparatus for providing internet access to client computers over a lan |
US6842769B1 (en) * | 2000-05-05 | 2005-01-11 | Interland, Inc. | Automatically configured network server |
US20020010800A1 (en) * | 2000-05-18 | 2002-01-24 | Riley Richard T. | Network access control system and method |
US7571308B1 (en) * | 2000-06-28 | 2009-08-04 | Microsoft Corporation | Method for controlling access to a network by a wireless client |
US6985963B1 (en) * | 2000-08-23 | 2006-01-10 | At Home Corporation | Sharing IP network resources |
US7092390B2 (en) * | 2000-09-07 | 2006-08-15 | Sbc Technology Resources, Inc. | Internal substitution bi-level addressing for compatible public networks |
US7574495B1 (en) * | 2000-09-13 | 2009-08-11 | Fortinet, Inc. | System and method for managing interworking communications protocols |
US7272643B1 (en) * | 2000-09-13 | 2007-09-18 | Fortinet, Inc. | System and method for managing and provisioning virtual routers |
US8250357B2 (en) | 2000-09-13 | 2012-08-21 | Fortinet, Inc. | Tunnel interface for securing traffic over a network |
US7487232B1 (en) | 2000-09-13 | 2009-02-03 | Fortinet, Inc. | Switch management system and method |
US7444398B1 (en) * | 2000-09-13 | 2008-10-28 | Fortinet, Inc. | System and method for delivering security services |
US7389358B1 (en) * | 2000-09-13 | 2008-06-17 | Fortinet, Inc. | Distributed virtual system to support managed, network-based services |
KR100402981B1 (en) * | 2000-09-29 | 2003-10-22 | 엘지전자 주식회사 | Apparatus and Method of Managing IP Address in the Exchange |
US7054321B1 (en) * | 2000-10-27 | 2006-05-30 | Redback Networks Inc. | Tunneling ethernet |
US7088737B1 (en) * | 2000-10-27 | 2006-08-08 | Redback Networks Inc. | Method and apparatus for combining packets having different protocol encapsulations within a circuit |
US7190686B1 (en) * | 2000-12-20 | 2007-03-13 | Cisco Technology, Inc. | Self configuring high throughput medium access control for wireless networks |
FR2819962B1 (en) * | 2001-01-22 | 2003-06-20 | Cit Alcatel | ACTIVE NETWORK ACCESS CONTROL GATEWAY |
US6952428B1 (en) * | 2001-01-26 | 2005-10-04 | 3Com Corporation | System and method for a specialized dynamic host configuration protocol proxy in a data-over-cable network |
US7444404B2 (en) * | 2001-02-05 | 2008-10-28 | Arbor Networks, Inc. | Network traffic regulation including consistency based detection and filtering of packets with spoof source addresses |
US20020129377A1 (en) * | 2001-03-08 | 2002-09-12 | Cloonan Thomas J. | Method and apparatus for controlling traffic loading on links between internet service providers and cable modem termination system |
US20020162021A1 (en) * | 2001-04-30 | 2002-10-31 | Audebert Yves Louis Gabriel | Method and system for establishing a remote connection to a personal security device |
US7450595B1 (en) * | 2001-05-01 | 2008-11-11 | At&T Corp. | Method and system for managing multiple networks over a set of ports |
US7639617B2 (en) * | 2001-06-27 | 2009-12-29 | Cisco Technology, Inc. | Upstream physical interface for modular cable modem termination system |
US7688828B2 (en) * | 2001-06-27 | 2010-03-30 | Cisco Technology, Inc. | Downstream remote physical interface for modular cable modem termination system |
US7181547B1 (en) * | 2001-06-28 | 2007-02-20 | Fortinet, Inc. | Identifying nodes in a ring network |
US20030009585A1 (en) * | 2001-07-06 | 2003-01-09 | Brian Antoine | Dynamic policy based routing |
US7360245B1 (en) * | 2001-07-18 | 2008-04-15 | Novell, Inc. | Method and system for filtering spoofed packets in a network |
US7809806B1 (en) * | 2001-08-02 | 2010-10-05 | Cisco Technology, Inc. | Neighbor discovery using address registration protocol over ELMI |
US7134012B2 (en) * | 2001-08-15 | 2006-11-07 | International Business Machines Corporation | Methods, systems and computer program products for detecting a spoofed source address in IP datagrams |
JP4236398B2 (en) * | 2001-08-15 | 2009-03-11 | 富士通株式会社 | Communication method, communication system, and communication connection program |
JP2003110596A (en) * | 2001-09-28 | 2003-04-11 | Hitachi Ltd | Data communication service providing method |
US7436842B2 (en) | 2001-10-11 | 2008-10-14 | Serconet Ltd. | Outlet with analog signal adapter, a method for use thereof and a network using said outlet |
US7813346B1 (en) * | 2001-11-21 | 2010-10-12 | Juniper Networks, Inc. | Filter-based forwarding in a network |
FI20012338A0 (en) * | 2001-11-29 | 2001-11-29 | Stonesoft Corp | Firewall for filtering tunneled data packets |
US7617317B2 (en) * | 2001-12-03 | 2009-11-10 | Sprint Spectrum L.P. | Method and system for allowing multiple service providers to serve users via a common access network |
US7379465B2 (en) * | 2001-12-07 | 2008-05-27 | Nortel Networks Limited | Tunneling scheme optimized for use in virtual private networks |
US20030159072A1 (en) * | 2002-02-04 | 2003-08-21 | Atreus Systems Corp. | Single sign-on for multiple network -based services |
CN100431305C (en) * | 2002-02-08 | 2008-11-05 | 艾利森电话股份有限公司 | Method and system ralating service providers to clients in an access network, using dynamically allocated MAC addresses |
AU2003205797A1 (en) * | 2002-02-13 | 2003-09-04 | Nokia Corporation | Filtering of data packets in a communication network according to interface identifiers |
US7844817B2 (en) * | 2002-02-28 | 2010-11-30 | Siemens Aktiengesellschaft | Ensuring quality of service in a communications network |
US20030167338A1 (en) * | 2002-03-01 | 2003-09-04 | Globespanvirata Incorporated | System and method to provide PPPoE connectivity to non-PPPoE clients |
US20030169694A1 (en) * | 2002-03-07 | 2003-09-11 | Seaman Michael John | Use of alternate ports in spanning tree configured bridged virtual local area networks |
US20030172170A1 (en) * | 2002-03-08 | 2003-09-11 | Johnson Gerald R. | Providing multiple ISP access to devices behind NAT |
EP1488610B1 (en) * | 2002-03-27 | 2018-09-12 | British Telecommunications public limited company | System for selecting a connectivity mechanism |
US7324515B1 (en) | 2002-03-27 | 2008-01-29 | Cisco Technology, Inc. | Proxy addressing scheme for cable networks |
JP3665622B2 (en) * | 2002-03-29 | 2005-06-29 | 株式会社東芝 | Source address selection system, router device, communication node, and source address selection method |
US7720044B1 (en) * | 2002-04-19 | 2010-05-18 | Nokia Corporation | System and method for terminal configuration |
US7376125B1 (en) | 2002-06-04 | 2008-05-20 | Fortinet, Inc. | Service processing switch |
US7177311B1 (en) | 2002-06-04 | 2007-02-13 | Fortinet, Inc. | System and method for routing traffic through a virtual router-based network switch |
US7116665B2 (en) * | 2002-06-04 | 2006-10-03 | Fortinet, Inc. | Methods and systems for a distributed provider edge |
US7203192B2 (en) * | 2002-06-04 | 2007-04-10 | Fortinet, Inc. | Network packet steering |
US7161904B2 (en) | 2002-06-04 | 2007-01-09 | Fortinet, Inc. | System and method for hierarchical metering in a virtual router based network switch |
US20040001496A1 (en) * | 2002-06-21 | 2004-01-01 | Jon Yusko | Method and apparatus for PPP auto-connect |
CN1233135C (en) * | 2002-06-22 | 2005-12-21 | 华为技术有限公司 | Method for preventing IP address deceit in dynamic address distribution |
US7174376B1 (en) * | 2002-06-28 | 2007-02-06 | Cisco Technology, Inc. | IP subnet sharing technique implemented without using bridging or routing protocols |
US6801528B2 (en) * | 2002-07-03 | 2004-10-05 | Ericsson Inc. | System and method for dynamic simultaneous connection to multiple service providers |
US7243150B2 (en) * | 2002-07-10 | 2007-07-10 | Radwin Ltd. | Reducing the access delay for transmitting processed data over transmission data |
US20040015262A1 (en) * | 2002-07-18 | 2004-01-22 | International Business Machines Corporation | Method for controlling access to devices in a pervasive embedded environment |
WO2004014045A1 (en) * | 2002-07-24 | 2004-02-12 | International Business Machines Corporation | Service class dependant asignment of ip addresses for cotrolling access to an d delivery of e-sevices |
US7143435B1 (en) | 2002-07-31 | 2006-11-28 | Cisco Technology, Inc. | Method and apparatus for registering auto-configured network addresses based on connection authentication |
US7298750B2 (en) | 2002-07-31 | 2007-11-20 | At&T Knowledge Ventures, L.P. | Enhancement of resource reservation protocol enabling short-cut internet protocol connections over a switched network |
US7065092B2 (en) * | 2002-07-31 | 2006-06-20 | Sbc Properties, L.P. | Resource reservation protocol based guaranteed quality of service internet protocol (IP) connections over a switched network using newly assigned IP addresses |
US7301951B2 (en) * | 2002-07-31 | 2007-11-27 | At&T Knowledge Ventures, L.P. | Resource reservation protocol based guaranteed quality of service internet protocol connections over a switched network |
US7272145B2 (en) | 2002-07-31 | 2007-09-18 | At&T Knowledge Ventures, L.P. | Resource reservation protocol based guaranteed quality of service internet protocol connections over a switched network through proxy signaling |
US7684400B2 (en) * | 2002-08-08 | 2010-03-23 | Intel Corporation | Logarithmic time range-based multifield-correlation packet classification |
US20040045035A1 (en) * | 2002-08-27 | 2004-03-04 | Broadcom Corporation | Distributed cable modem termination system (CMTS) architecture |
US20040045033A1 (en) * | 2002-08-27 | 2004-03-04 | Broadcom Corporation | Distributed cable modem termination system (CMTS) architecture implementing a media access control chip |
US7551610B2 (en) * | 2002-08-27 | 2009-06-23 | Broadcom Corporation | MiniMAC implementation of a distributed cable modem termination system (CMTS) architecture |
US20040045037A1 (en) * | 2002-08-27 | 2004-03-04 | Broadcom Corporation | Distributed cable modem termination system (CMTS) architecture implementing a media access control chip |
US7096383B2 (en) | 2002-08-29 | 2006-08-22 | Cosine Communications, Inc. | System and method for virtual router failover in a network routing system |
WO2004034229A2 (en) | 2002-10-10 | 2004-04-22 | Rocksteady Networks, Inc. | System and method for providing access control |
US7587512B2 (en) | 2002-10-16 | 2009-09-08 | Eric White | System and method for dynamic bandwidth provisioning |
US7337224B1 (en) * | 2002-10-24 | 2008-02-26 | Cisco Technology, Inc. | Method and apparatus providing policy-based determination of network addresses |
US7434254B1 (en) * | 2002-10-25 | 2008-10-07 | Cisco Technology, Inc. | Method and apparatus for automatic filter generation and maintenance |
US20050105513A1 (en) * | 2002-10-27 | 2005-05-19 | Alan Sullivan | Systems and methods for direction of communication traffic |
US20050027882A1 (en) * | 2003-05-05 | 2005-02-03 | Sullivan Alan T. | Systems and methods for direction of communication traffic |
ATE552692T1 (en) | 2002-11-06 | 2012-04-15 | Ericsson Telefon Ab L M | PROCEDURE AND ARRANGEMENT FOR PROTECTION AGAINST UNLAWFUL USE OF IP ADDRESSES |
USRE47253E1 (en) | 2002-11-06 | 2019-02-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and arrangement for preventing illegitimate use of IP addresses |
IL152824A (en) * | 2002-11-13 | 2012-05-31 | Mosaid Technologies Inc | Addressable outlet and a network using same |
US7266120B2 (en) | 2002-11-18 | 2007-09-04 | Fortinet, Inc. | System and method for hardware accelerated packet multicast in a virtual routing system |
US7475243B2 (en) | 2002-12-11 | 2009-01-06 | Broadcom Corporation | Preventing a non-head end based service provider from sending media to a media processing system |
US7450501B2 (en) | 2002-12-11 | 2008-11-11 | Broadcom Corporation | Media processing system based on satellite set top box platform with telephony downstream and upstream data paths |
US8495180B2 (en) | 2002-12-11 | 2013-07-23 | Broadcom Corporation | Server architecture supporting a personal media exchange network |
US9357256B2 (en) | 2002-12-11 | 2016-05-31 | Broadcom Corporation | Third party media channel access in a media exchange network |
US8260941B2 (en) * | 2002-12-20 | 2012-09-04 | Time Warner Cable, Inc. | System and method for detecting and reporting cable modems with duplicate media access control addresses |
US7272846B2 (en) * | 2002-12-20 | 2007-09-18 | Time Warner Cable, A Division Of Time Warner Entertainment Company, Lp | System and method for detecting and reporting cable modems with duplicate media access control addresses |
US7467227B1 (en) | 2002-12-31 | 2008-12-16 | At&T Corp. | System using policy filter decision to map data traffic to virtual networks for forwarding the traffic in a regional access network |
EP1443736A3 (en) | 2003-01-30 | 2006-01-04 | Broadcom Corporation | Server architecture supporting a personal media exchange network |
US7222173B2 (en) * | 2003-02-10 | 2007-05-22 | International Business Machines Corporation | Limited knowledge of configuration information of a FICON controller |
KR100886551B1 (en) * | 2003-02-21 | 2009-03-02 | 삼성전자주식회사 | Apparatus for traffic flow template packet filtering according to internet protocol version in mobile communication system and method thereof |
US20040165600A1 (en) * | 2003-02-21 | 2004-08-26 | Alcatel | Customer site bridged emulated LAN services via provider provisioned connections |
JP3819368B2 (en) * | 2003-02-24 | 2006-09-06 | 株式会社東芝 | Communication control device, communication control method, server device with communication control, communication control method and communication control program using server device with communication control |
US20080114832A1 (en) * | 2003-03-07 | 2008-05-15 | Atreus Systems Corp. | Using multiple policy distribution points to initiate a network-based service |
US20040193730A1 (en) * | 2003-03-25 | 2004-09-30 | Vernon Stephen K. | Method and computer programs for providing special processing of a communication sent across a communication network |
US7558844B1 (en) * | 2003-05-06 | 2009-07-07 | Juniper Networks, Inc. | Systems and methods for implementing dynamic subscriber interfaces |
US7293282B2 (en) * | 2003-07-03 | 2007-11-06 | Time Warner Cable, Inc. | Method to block unauthorized access to TFTP server configuration files |
IL157787A (en) | 2003-09-07 | 2010-12-30 | Mosaid Technologies Inc | Modular outlet for data communications network |
US7720002B1 (en) * | 2003-07-10 | 2010-05-18 | Juniper Networks, Inc. | Systems and methods for initializing cable modems |
US7533255B1 (en) * | 2003-07-11 | 2009-05-12 | Cisco Technology, Inc. | Method and apparatus for restricting address resolution protocol table updates |
US7739394B2 (en) * | 2003-07-29 | 2010-06-15 | At&T Intellectual Property I, L.P. | Bi-level addressing for internet protocol broadband access |
US7447203B2 (en) | 2003-07-29 | 2008-11-04 | At&T Intellectual Property I, L.P. | Broadband access for virtual private networks |
US7698455B2 (en) | 2003-08-01 | 2010-04-13 | Foundry Networks, Inc. | Method for providing scalable multicast service in a virtual private LAN service |
US7165111B2 (en) * | 2003-08-04 | 2007-01-16 | Sbc Knowledge Ventures, L.P. | System and method to identify devices employing point-to-point-over Ethernet encapsulation |
US7624438B2 (en) | 2003-08-20 | 2009-11-24 | Eric White | System and method for providing a secure connection between networked computers |
US7720095B2 (en) * | 2003-08-27 | 2010-05-18 | Fortinet, Inc. | Heterogeneous media packet bridging |
US8788823B1 (en) * | 2003-09-03 | 2014-07-22 | Cisco Technology, Inc. | System and method for filtering network traffic |
DE60304704T2 (en) * | 2003-09-18 | 2007-04-12 | Sap Aktiengesellschaft | Network system, routers and network setup procedures |
US8321534B1 (en) * | 2003-10-15 | 2012-11-27 | Radix Holdings, Llc | System and method for synchronization based on preferences |
US7653730B1 (en) * | 2003-10-30 | 2010-01-26 | Sprint Communications Company L.P. | System and method for latency assurance and dynamic re-provisioning of telecommunication connections in a carrier virtual network |
US7512969B2 (en) * | 2003-11-21 | 2009-03-31 | Time Warner Cable, A Division Of Time Warner Entertainment Company, L.P. | System and method for detecting and reporting cable network devices with duplicate media access control addresses |
US8005112B2 (en) * | 2003-12-19 | 2011-08-23 | Teledata Networks, Ltd. | Service connection method and architecture |
IL159838A0 (en) * | 2004-01-13 | 2004-06-20 | Yehuda Binder | Information device |
KR20050079420A (en) * | 2004-02-05 | 2005-08-10 | 삼성전자주식회사 | Tunnelling sevice method and system thereof |
CA2457368C (en) * | 2004-02-11 | 2013-01-08 | Solutioninc Limited | A server, system and method for providing access to a public network through an internal network of a multi-system operator |
IL160417A (en) * | 2004-02-16 | 2011-04-28 | Mosaid Technologies Inc | Outlet add-on module |
US7610621B2 (en) * | 2004-03-10 | 2009-10-27 | Eric White | System and method for behavior-based firewall modeling |
US7590728B2 (en) | 2004-03-10 | 2009-09-15 | Eric White | System and method for detection of aberrant network behavior by clients of a network access gateway |
US7665130B2 (en) * | 2004-03-10 | 2010-02-16 | Eric White | System and method for double-capture/double-redirect to a different location |
JP2005260415A (en) * | 2004-03-10 | 2005-09-22 | Matsushita Electric Ind Co Ltd | Network repeating device |
US8543710B2 (en) * | 2004-03-10 | 2013-09-24 | Rpx Corporation | Method and system for controlling network access |
US7509625B2 (en) | 2004-03-10 | 2009-03-24 | Eric White | System and method for comprehensive code generation for system management |
US20050204022A1 (en) * | 2004-03-10 | 2005-09-15 | Keith Johnston | System and method for network management XML architectural abstraction |
JP4440265B2 (en) * | 2004-03-30 | 2010-03-24 | パナソニック株式会社 | COMMUNICATION SYSTEM, TRANSMISSION DEVICE, RECEPTION DEVICE, COMMUNICATION METHOD, AND AIRCRAFT CONTENT DISTRIBUTION SYSTEM |
US20070291739A1 (en) * | 2004-05-04 | 2007-12-20 | Sullivan Alan T | Systems and Methods for Direction of Communication Traffic |
EP1596553B1 (en) * | 2004-05-11 | 2016-07-27 | Alcatel Lucent | Method of providing resources with restricted access |
US7532627B2 (en) | 2004-05-25 | 2009-05-12 | Cisco Technology, Inc. | Wideband upstream protocol |
US7539208B2 (en) * | 2004-05-25 | 2009-05-26 | Cisco Technology, Inc. | Timing system for modular cable modem termination system |
US7835274B2 (en) * | 2004-05-25 | 2010-11-16 | Cisco Technology, Inc. | Wideband provisioning |
US8149833B2 (en) * | 2004-05-25 | 2012-04-03 | Cisco Technology, Inc. | Wideband cable downstream protocol |
US7817553B2 (en) * | 2004-05-25 | 2010-10-19 | Cisco Technology, Inc. | Local area network services in a cable modem network |
US8102854B2 (en) | 2004-05-25 | 2012-01-24 | Cisco Technology, Inc. | Neighbor discovery proxy with distributed packet inspection scheme |
US7720101B2 (en) * | 2004-05-25 | 2010-05-18 | Cisco Technology, Inc. | Wideband cable modem with narrowband circuitry |
US7864686B2 (en) | 2004-05-25 | 2011-01-04 | Cisco Technology, Inc. | Tunneling scheme for transporting information over a cable network |
US7646786B2 (en) * | 2004-05-25 | 2010-01-12 | Cisco Technology, Inc. | Neighbor discovery in cable networks |
GB2416266A (en) * | 2004-07-15 | 2006-01-18 | Siemens Ag | Head office and branch office network connections |
US9596240B2 (en) * | 2004-08-30 | 2017-03-14 | Arris Enterprises, Inc. | Method and system for layer-3 subscriber login in a cable data network |
US7733811B2 (en) * | 2004-09-15 | 2010-06-08 | Fujitsu Limited | Method and system for bridging traffic in a resilient packet ring network |
US7499419B2 (en) | 2004-09-24 | 2009-03-03 | Fortinet, Inc. | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
EP1643710A1 (en) | 2004-09-30 | 2006-04-05 | Nagravision S.A. | Method of updating a lookup table of addresses and identification numbers |
US20060072482A1 (en) * | 2004-10-06 | 2006-04-06 | Nokia Corporation | Service routing |
US20060095546A1 (en) * | 2004-10-07 | 2006-05-04 | Nokia Corporation | Method and system for locating services in proximity networks for legacy application |
US7854000B2 (en) * | 2004-10-26 | 2010-12-14 | Cisco Technology, Inc. | Method and system for addressing attacks on a computer connected to a network |
US7808904B2 (en) | 2004-11-18 | 2010-10-05 | Fortinet, Inc. | Method and apparatus for managing subscriber profiles |
US7342925B2 (en) * | 2004-11-30 | 2008-03-11 | At&T Corp. | Technique for automated MAC address cloning |
EP1662703A1 (en) * | 2004-11-30 | 2006-05-31 | Alcatel | Replacement of DHCP server IP address with relay agent IP address in DHCP message |
US7558866B2 (en) * | 2004-12-08 | 2009-07-07 | Microsoft Corporation | Method and system for securely provisioning a client device |
US7881289B1 (en) * | 2004-12-22 | 2011-02-01 | At&T Intellectual Property Ii, L.P. | Method and apparatus for porting telephone numbers of endpoint devices |
US20060140182A1 (en) * | 2004-12-23 | 2006-06-29 | Michael Sullivan | Systems and methods for monitoring and controlling communication traffic |
ATE354901T1 (en) * | 2005-01-05 | 2007-03-15 | Cit Alcatel | METHOD FOR CONFIGURING A DSL CONNECTION IN WHICH A HOME IP PLUG CONTROL IS ENABLED TO INITIATE COMMUNICATION WITH A HOME IP PLUG |
US20060161636A1 (en) * | 2005-01-06 | 2006-07-20 | Tellabs Operations, Inc. | Method and apparatus for automated discovery of a remote access device address |
US20060179013A1 (en) * | 2005-02-10 | 2006-08-10 | Andre Beliveau | Configurable distribution of signals in a network |
US7440405B2 (en) * | 2005-03-11 | 2008-10-21 | Reti Corporation | Apparatus and method for packet forwarding with quality of service and rate control |
ATE360938T1 (en) | 2005-03-17 | 2007-05-15 | Alcatel Lucent | METHOD FOR EXCHANGING DATA PACKETS |
US9438683B2 (en) * | 2005-04-04 | 2016-09-06 | Aol Inc. | Router-host logging |
US7630361B2 (en) * | 2005-05-20 | 2009-12-08 | Cisco Technology, Inc. | Method and apparatus for using data-over-cable applications and services in non-cable environments |
CA2609415A1 (en) * | 2005-05-24 | 2006-11-30 | Paxfire, Inc. | Enhanced features for direction of communication traffic |
US7668195B2 (en) | 2005-06-14 | 2010-02-23 | General Instrument Corporation | Method and apparatus for transmitting and receiving data over a shared access carrier network |
KR101291190B1 (en) | 2005-09-15 | 2013-07-31 | 삼성전자주식회사 | Method for sharing network resources between two network operators |
US20070116234A1 (en) * | 2005-10-19 | 2007-05-24 | Marco Schneider | Methods and apparatus for preserving access information during call transfers |
US20070086433A1 (en) * | 2005-10-19 | 2007-04-19 | Cunetto Philip C | Methods and apparatus for allocating shared communication resources to outdial communication services |
US7924987B2 (en) * | 2005-10-19 | 2011-04-12 | At&T Intellectual Property I., L.P. | Methods, apparatus and data structures for managing distributed communication systems |
US20070086432A1 (en) * | 2005-10-19 | 2007-04-19 | Marco Schneider | Methods and apparatus for automated provisioning of voice over internet protocol gateways |
US8238327B2 (en) * | 2005-10-19 | 2012-08-07 | At&T Intellectual Property I, L.P. | Apparatus and methods for subscriber and enterprise assignments and resource sharing |
US7643472B2 (en) | 2005-10-19 | 2010-01-05 | At&T Intellectual Property I, Lp | Methods and apparatus for authorizing and allocating outdial communication services |
US7839988B2 (en) | 2005-10-19 | 2010-11-23 | At&T Intellectual Property I, L.P. | Methods and apparatus for data structure driven authorization and/or routing of outdial communication services |
US7606232B1 (en) | 2005-11-09 | 2009-10-20 | Juniper Networks, Inc. | Dynamic virtual local area network (VLAN) interface configuration |
US7649886B2 (en) * | 2005-11-21 | 2010-01-19 | Motorola, Inc. | Method and system for processing incoming packets in a communication network |
EP2802106B1 (en) * | 2005-12-03 | 2018-10-17 | Huawei Technologies Co., Ltd. | System and method for implementing the interconnection of a DSL network and a wireless communication network |
US20070162331A1 (en) * | 2006-01-10 | 2007-07-12 | Michael Sullivan | Systems and methods for providing information and conducting business using the internet |
CN101005381B (en) * | 2006-01-17 | 2012-05-02 | 华为技术有限公司 | System and method for realizing flow statistic based user's service on terminal |
US7633956B1 (en) | 2006-01-19 | 2009-12-15 | Cisco Technology, Inc. | System and method for providing support for multipoint L2VPN services in devices without local bridging |
JP2009524355A (en) | 2006-01-20 | 2009-06-25 | パックスファイアー インコーポレイテッド | System and method for determining and controlling communication traffic |
US7808994B1 (en) | 2006-02-22 | 2010-10-05 | Juniper Networks, Inc. | Forwarding traffic to VLAN interfaces built based on subscriber information strings |
US7492766B2 (en) * | 2006-02-22 | 2009-02-17 | Juniper Networks, Inc. | Dynamic building of VLAN interfaces based on subscriber information strings |
FR2897736B1 (en) * | 2006-02-22 | 2008-04-11 | Viaccess Sa | METHOD FOR ESTABLISHING A CRYPTOGRAPHIC KEY, NET HEAD AND RECEIVER FOR THIS METHOD, AND METHOD FOR TRANSMITTING SIGNALS |
US7624181B2 (en) * | 2006-02-24 | 2009-11-24 | Cisco Technology, Inc. | Techniques for authenticating a subscriber for an access network using DHCP |
US7853708B2 (en) * | 2006-02-24 | 2010-12-14 | Cisco Technology, Inc. | Techniques for replacing point to point protocol with dynamic host configuration protocol |
CN101496387B (en) * | 2006-03-06 | 2012-09-05 | 思科技术公司 | System and method for access authentication in a mobile wireless network |
US7715562B2 (en) * | 2006-03-06 | 2010-05-11 | Cisco Technology, Inc. | System and method for access authentication in a mobile wireless network |
US8301115B1 (en) | 2006-03-08 | 2012-10-30 | Alcatel Lucent | Method for inverse port-based authentication |
US8004973B2 (en) * | 2006-04-25 | 2011-08-23 | Citrix Systems, Inc. | Virtual inline configuration for a network device |
FR2903264B1 (en) * | 2006-06-30 | 2008-09-26 | Sagem Comm | METHOD AND DEVICE FOR CONNECTING A CLIENTE MACHINE |
EP1876799A1 (en) * | 2006-07-06 | 2008-01-09 | Swisscom Solutions AG | Method and computer system for the exchange of data with a computer |
US8107396B1 (en) * | 2006-07-24 | 2012-01-31 | Cisco Technology, Inc. | Host tracking in a layer 2 IP ethernet network |
FR2904503A1 (en) * | 2006-07-28 | 2008-02-01 | France Telecom | METHOD OF CUSTOMER ACCESS TO SERVICE THROUGH A NETWORK, BY COMBINED USE OF A DYNAMIC CONFIGURATION PROTOCOL AND POINT-TO-POINT PROTOCOL, CORRESPONDING COMPUTER EQUIPMENT AND PROGRAM |
DE602006004338D1 (en) * | 2006-08-04 | 2009-01-29 | Alcatel Lucent | Device, module and method for routing an access network |
EP1931085B1 (en) * | 2006-12-06 | 2012-07-18 | Genexis B.V. | Modular network connection equipment |
US7725594B2 (en) * | 2006-12-29 | 2010-05-25 | Verizon Patent And Licensing Inc. | Assigning priority to network traffic at customer premises |
US7706267B2 (en) * | 2007-03-06 | 2010-04-27 | Hewlett-Packard Development Company, L.P. | Network service monitoring |
EP1973269B1 (en) * | 2007-03-22 | 2013-04-24 | PacketFront Software Solutions AB | Configuration preprocessor language |
EP1973270B1 (en) * | 2007-03-22 | 2018-01-03 | PacketFront Software Solutions AB | Broadband service delivery |
US7822036B2 (en) * | 2007-03-27 | 2010-10-26 | Alcatel Lucent | Method and system for policy-based routing in a private network-to-network interface protocol based network |
ATE467962T1 (en) | 2007-05-29 | 2010-05-15 | Packetfront Systems Ab | METHOD FOR CONNECTING VLAN SYSTEMS TO OTHER NETWORKS VIA A ROUTER |
DE102007029120B4 (en) * | 2007-06-25 | 2010-06-17 | Siemens Ag | A method of operating a wireless, meshed data network having a plurality of network nodes |
US20110071997A1 (en) * | 2007-07-30 | 2011-03-24 | Sullivan Alan T | Systems and methods for direction of communication traffic |
US8792339B2 (en) * | 2007-08-10 | 2014-07-29 | Arris Enterprises, Inc. | Method and system for moving distinctive traffic flows to a different priority service flow |
EP2045992A1 (en) * | 2007-10-04 | 2009-04-08 | Gemplus | A method for accessing a portable device, corresponding portable device, host device and system |
EP2048857A1 (en) * | 2007-10-12 | 2009-04-15 | PacketFront Systems AB | Method of configuring routers using external servers |
EP2048858B1 (en) * | 2007-10-12 | 2010-04-14 | PacketFront Systems AB | Configuration of routers for DHCP service requests |
EP2048848B1 (en) * | 2007-10-12 | 2013-12-18 | PacketFront Network Products AB | Optical data communications |
US8325674B2 (en) | 2007-10-31 | 2012-12-04 | Alcatel Lucent | Method of integrating femtocells in a packet cable multimedia architecture |
KR101474840B1 (en) * | 2007-11-05 | 2014-12-19 | 삼성전자 주식회사 | System and method for controlling network device based on UPnP |
US8179799B2 (en) * | 2007-11-30 | 2012-05-15 | Solarwinds Worldwide, Llc | Method for partitioning network flows based on their time information |
US8601113B2 (en) * | 2007-11-30 | 2013-12-03 | Solarwinds Worldwide, Llc | Method for summarizing flow information from network devices |
US9331919B2 (en) * | 2007-11-30 | 2016-05-03 | Solarwinds Worldwide, Llc | Method for summarizing flow information of network devices |
CN101478576B (en) * | 2008-01-03 | 2012-02-15 | 华为技术有限公司 | Method, apparatus and system for selecting service network |
US20090201897A1 (en) * | 2008-02-11 | 2009-08-13 | Nokia Siemens Networks Oy | Classification process involving mobile stations |
US8621198B2 (en) * | 2008-02-19 | 2013-12-31 | Futurewei Technologies, Inc. | Simplified protocol for carrying authentication for network access |
US8429739B2 (en) | 2008-03-31 | 2013-04-23 | Amazon Technologies, Inc. | Authorizing communications between computing nodes |
US20110161360A1 (en) * | 2008-05-28 | 2011-06-30 | Packetfront Systems Ab | Data retrieval in a network of tree structure |
US8326958B1 (en) | 2009-01-28 | 2012-12-04 | Headwater Partners I, Llc | Service activation tracking system |
US8346225B2 (en) | 2009-01-28 | 2013-01-01 | Headwater Partners I, Llc | Quality of service for device assisted services |
US8275830B2 (en) | 2009-01-28 | 2012-09-25 | Headwater Partners I Llc | Device assisted CDR creation, aggregation, mediation and billing |
US8402111B2 (en) | 2009-01-28 | 2013-03-19 | Headwater Partners I, Llc | Device assisted services install |
US8832777B2 (en) | 2009-03-02 | 2014-09-09 | Headwater Partners I Llc | Adapting network policies based on device service processor configuration |
US8406748B2 (en) | 2009-01-28 | 2013-03-26 | Headwater Partners I Llc | Adaptive ambient services |
US8589541B2 (en) | 2009-01-28 | 2013-11-19 | Headwater Partners I Llc | Device-assisted services for protecting network capacity |
US8627061B1 (en) | 2008-08-25 | 2014-01-07 | Apriva, Llc | Method and system for employing a fixed IP address based encryption device in a dynamic IP address based network |
US8199348B2 (en) * | 2008-11-03 | 2012-06-12 | Sharp Laboratories Of America, Inc. | Methods and systems for handling files for MFPS utilizing external services |
US10264138B2 (en) | 2009-01-28 | 2019-04-16 | Headwater Research Llc | Mobile device and service management |
AU2010208183A1 (en) * | 2009-01-28 | 2011-09-08 | Headwater Partners I Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US10715342B2 (en) | 2009-01-28 | 2020-07-14 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
US10237757B2 (en) | 2009-01-28 | 2019-03-19 | Headwater Research Llc | System and method for wireless network offloading |
US10798252B2 (en) | 2009-01-28 | 2020-10-06 | Headwater Research Llc | System and method for providing user notifications |
US9955332B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Method for child wireless device activation to subscriber account of a master wireless device |
US9565707B2 (en) | 2009-01-28 | 2017-02-07 | Headwater Partners I Llc | Wireless end-user device with wireless data attribution to multiple personas |
US10841839B2 (en) * | 2009-01-28 | 2020-11-17 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US10248996B2 (en) | 2009-01-28 | 2019-04-02 | Headwater Research Llc | Method for operating a wireless end-user device mobile payment agent |
US10779177B2 (en) | 2009-01-28 | 2020-09-15 | Headwater Research Llc | Device group partitions and settlement platform |
US10484858B2 (en) | 2009-01-28 | 2019-11-19 | Headwater Research Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US9270559B2 (en) | 2009-01-28 | 2016-02-23 | Headwater Partners I Llc | Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow |
US9572019B2 (en) | 2009-01-28 | 2017-02-14 | Headwater Partners LLC | Service selection set published to device agent with on-device service selection |
US9954975B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Enhanced curfew and protection associated with a device group |
US10492102B2 (en) | 2009-01-28 | 2019-11-26 | Headwater Research Llc | Intermediate networking devices |
US9706061B2 (en) | 2009-01-28 | 2017-07-11 | Headwater Partners I Llc | Service design center for device assisted services |
US10326800B2 (en) | 2009-01-28 | 2019-06-18 | Headwater Research Llc | Wireless network service interfaces |
US11218854B2 (en) | 2009-01-28 | 2022-01-04 | Headwater Research Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US10200541B2 (en) | 2009-01-28 | 2019-02-05 | Headwater Research Llc | Wireless end-user device with divided user space/kernel space traffic policy system |
US10783581B2 (en) | 2009-01-28 | 2020-09-22 | Headwater Research Llc | Wireless end-user device providing ambient or sponsored services |
US9392462B2 (en) | 2009-01-28 | 2016-07-12 | Headwater Partners I Llc | Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy |
US9980146B2 (en) | 2009-01-28 | 2018-05-22 | Headwater Research Llc | Communications device with secure data path processing agents |
WO2010088957A1 (en) * | 2009-02-05 | 2010-08-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Host identity protocol server address configuration |
US8392698B2 (en) | 2010-04-16 | 2013-03-05 | Cisco Technology, Inc. | System and method for providing prefixes indicative of mobility properties in a network environment |
US9497164B2 (en) * | 2010-05-27 | 2016-11-15 | At&T Intellectual Property I, L.P. | System and method of redirecting internet protocol traffic for network based parental controls |
US20120023562A1 (en) * | 2010-07-26 | 2012-01-26 | David Harp | Systems and methods to route network communications for network-based services |
US9886315B2 (en) * | 2010-08-27 | 2018-02-06 | Ebay Inc. | Identity and semaphore-based quality of service |
US8923133B2 (en) * | 2010-12-27 | 2014-12-30 | Symbol Technologies, Inc. | Detection of unauthorized changes to an address resolution protocol cache in a communication network |
EP2645641A4 (en) * | 2011-04-21 | 2014-12-03 | Nec Corp | Communication system, control device, communication method, and program |
US9148776B1 (en) * | 2011-09-28 | 2015-09-29 | Pulse Secure, Llc | Network address preservation in mobile networks |
US8965362B1 (en) * | 2011-11-21 | 2015-02-24 | Wichorus | Methods and apparatus for prefix filtering of international mobile subscriber identity (IMSI) wildcard application |
US8719344B2 (en) * | 2011-12-20 | 2014-05-06 | Cisco Technology, Inc. | Flexible address provisioning across subnets and VRFs |
US8750122B1 (en) * | 2012-03-22 | 2014-06-10 | Avaya, Inc. | Method and apparatus for layer 2 loop prevention in a multi-node switch cluster |
US20140215034A1 (en) * | 2013-01-29 | 2014-07-31 | Huawei Device Co., Ltd. | Processing Method and Processing Device for Automatically Setting Internet Access Mode |
US9634940B2 (en) | 2013-01-31 | 2017-04-25 | Mellanox Technologies, Ltd. | Adaptive routing using inter-switch notifications |
US20140281497A1 (en) * | 2013-03-13 | 2014-09-18 | General Instrument Corporation | Online personalization update system for externally acquired keys |
WO2014159862A1 (en) | 2013-03-14 | 2014-10-02 | Headwater Partners I Llc | Automated credential porting for mobile devices |
EP2790386A1 (en) * | 2013-04-10 | 2014-10-15 | Alcatel Lucent | Method of managing wired connections and connection manager |
US9319307B2 (en) | 2013-09-06 | 2016-04-19 | At&T Intellectual Property I, L.P. | Providing differentiated service to traffic flows obscured by content distribution systems |
US9548960B2 (en) * | 2013-10-06 | 2017-01-17 | Mellanox Technologies Ltd. | Simplified packet routing |
KR101502490B1 (en) * | 2013-10-18 | 2015-03-13 | 주식회사 케이티 | Subscibe terminal and security farm node for monitoring network traffic |
US20150271268A1 (en) * | 2014-03-20 | 2015-09-24 | Cox Communications, Inc. | Virtual customer networks and decomposition and virtualization of network communication layer functionality |
US10277422B2 (en) * | 2014-05-06 | 2019-04-30 | International Business Machines Corporation | Virtual port support in a logical switch architecture |
US9729473B2 (en) | 2014-06-23 | 2017-08-08 | Mellanox Technologies, Ltd. | Network high availability using temporary re-routing |
US9806994B2 (en) | 2014-06-24 | 2017-10-31 | Mellanox Technologies, Ltd. | Routing via multiple paths with efficient traffic distribution |
US9912563B2 (en) * | 2014-07-22 | 2018-03-06 | International Business Machines Corporation | Traffic engineering of cloud services |
US9699067B2 (en) | 2014-07-22 | 2017-07-04 | Mellanox Technologies, Ltd. | Dragonfly plus: communication over bipartite node groups connected by a mesh network |
US9516700B1 (en) | 2014-09-25 | 2016-12-06 | Google Inc. | Cloud-based controller for managing access points |
US9894005B2 (en) | 2015-03-31 | 2018-02-13 | Mellanox Technologies, Ltd. | Adaptive routing controlled by source node |
US9769115B2 (en) * | 2015-04-24 | 2017-09-19 | Fortinet, Inc. | DHCP agent assisted routing and access control |
CN105099941B (en) * | 2015-06-19 | 2018-09-04 | 新华三技术有限公司 | A kind of message processing method and device |
US9973435B2 (en) | 2015-12-16 | 2018-05-15 | Mellanox Technologies Tlv Ltd. | Loopback-free adaptive routing |
US10819621B2 (en) | 2016-02-23 | 2020-10-27 | Mellanox Technologies Tlv Ltd. | Unicast forwarding of adaptive-routing notifications |
US10873637B2 (en) * | 2016-05-02 | 2020-12-22 | Microsoft Technology Licensing, Llc | Controlling service discovery and activation among peers |
US10178029B2 (en) | 2016-05-11 | 2019-01-08 | Mellanox Technologies Tlv Ltd. | Forwarding of adaptive routing notifications |
US10511530B2 (en) * | 2016-12-13 | 2019-12-17 | Viasat, Inc. | Return-link routing in a hybrid network |
US10200294B2 (en) | 2016-12-22 | 2019-02-05 | Mellanox Technologies Tlv Ltd. | Adaptive routing based on flow-control credits |
US10425330B2 (en) * | 2017-04-24 | 2019-09-24 | International Business Machines Corporation | Routing packets in multiple destination networks with overlapping address spaces |
US10693715B1 (en) * | 2017-10-26 | 2020-06-23 | Amazon Technologies, Inc. | Dynamic network address space allocation for virtual networks |
US10439933B2 (en) * | 2018-01-09 | 2019-10-08 | Entry Point, Llc | Isolating services across a single physical network interface |
US10644995B2 (en) | 2018-02-14 | 2020-05-05 | Mellanox Technologies Tlv Ltd. | Adaptive routing in a box |
US11005724B1 (en) | 2019-01-06 | 2021-05-11 | Mellanox Technologies, Ltd. | Network topology having minimal number of long connections among groups of network elements |
US11394693B2 (en) * | 2019-03-04 | 2022-07-19 | Cyxtera Cybersecurity, Inc. | Establishing network tunnel in response to access request |
US11277442B2 (en) * | 2019-04-05 | 2022-03-15 | Cisco Technology, Inc. | Verifying the trust-worthiness of ARP senders and receivers using attestation-based methods |
US11575594B2 (en) | 2020-09-10 | 2023-02-07 | Mellanox Technologies, Ltd. | Deadlock-free rerouting for resolving local link failures using detour paths |
US11411911B2 (en) | 2020-10-26 | 2022-08-09 | Mellanox Technologies, Ltd. | Routing across multiple subnetworks using address mapping |
US11870682B2 (en) | 2021-06-22 | 2024-01-09 | Mellanox Technologies, Ltd. | Deadlock-free local rerouting for handling multiple local link failures in hierarchical network topologies |
US11765103B2 (en) | 2021-12-01 | 2023-09-19 | Mellanox Technologies, Ltd. | Large-scale network with high port utilization |
Family Cites Families (85)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US466964A (en) * | 1892-01-12 | Willis s | ||
US5500860A (en) * | 1991-06-14 | 1996-03-19 | Digital Equipment Corporation | Router using multiple hop redirect messages to enable bridge like data forwarding |
AU7210894A (en) * | 1993-06-25 | 1995-01-17 | Xircom, Inc. | Virtual carrier detection for wireless local area network with distributed control |
US5325362A (en) * | 1993-09-29 | 1994-06-28 | Sun Microsystems, Inc. | Scalable and efficient intra-domain tunneling mobile-IP scheme |
US5633865A (en) * | 1995-03-31 | 1997-05-27 | Netvantage | Apparatus for selectively transferring data packets between local area networks |
US5737328A (en) * | 1995-10-04 | 1998-04-07 | Aironet Wireless Communications, Inc. | Network communication system with information rerouting capabilities |
US6091725A (en) * | 1995-12-29 | 2000-07-18 | Cisco Systems, Inc. | Method for traffic management, traffic prioritization, access control, and packet forwarding in a datagram computer network |
US5959990A (en) * | 1996-03-12 | 1999-09-28 | Bay Networks, Inc. | VLAN frame format |
SE511236C2 (en) * | 1996-11-29 | 1999-08-30 | Ericsson Telefon Ab L M | A modem with IP support |
US5918019A (en) * | 1996-07-29 | 1999-06-29 | Cisco Technology, Inc. | Virtual dial-up protocol for network communication |
US5914938A (en) * | 1996-11-19 | 1999-06-22 | Bay Networks, Inc. | MAC address table search unit |
US6073178A (en) * | 1996-12-09 | 2000-06-06 | Sun Microsystems, Inc. | Method and apparatus for assignment of IP addresses |
US6324267B1 (en) * | 1997-01-17 | 2001-11-27 | Scientific-Atlanta, Inc. | Two-tiered authorization and authentication for a cable data delivery system |
US5991292A (en) * | 1997-03-06 | 1999-11-23 | Nortel Networks Corporation | Network access in multi-service environment |
JP3028783B2 (en) * | 1997-04-25 | 2000-04-04 | 日本電気株式会社 | Network monitoring method and device |
FI104667B (en) * | 1997-07-14 | 2000-04-14 | Nokia Networks Oy | Implementation of access service |
US6608832B2 (en) * | 1997-09-25 | 2003-08-19 | Telefonaktiebolaget Lm Ericsson | Common access between a mobile communications network and an external network with selectable packet-switched and circuit-switched and circuit-switched services |
US6029203A (en) * | 1997-09-26 | 2000-02-22 | 3Com Corporation | Apparatus and methods for use therein for an ISDN LAN modem that provides enhanced network activity |
US6023724A (en) * | 1997-09-26 | 2000-02-08 | 3Com Corporation | Apparatus and methods for use therein for an ISDN LAN modem that displays fault information to local hosts through interception of host DNS request messages |
DE19742681C2 (en) * | 1997-09-26 | 2003-03-06 | Ericsson Telefon Ab L M | GPRS subscriber selection from several Internet service providers |
US6512754B2 (en) * | 1997-10-14 | 2003-01-28 | Lucent Technologies Inc. | Point-to-point protocol encapsulation in ethernet frame |
US6092110A (en) * | 1997-10-23 | 2000-07-18 | At&T Wireless Svcs. Inc. | Apparatus for filtering packets using a dedicated processor |
DE69829203T2 (en) * | 1997-11-03 | 2006-02-16 | British Telecommunications P.L.C. | Packet network |
US6484210B1 (en) * | 1997-11-10 | 2002-11-19 | General Instrument Corporation | Packet processing relay agent to provide link layer forwarding in one-way cable/wireless/satellite modems |
US6009103A (en) | 1997-12-23 | 1999-12-28 | Mediaone Group, Inc. | Method and system for automatic allocation of resources in a network |
US6535493B1 (en) * | 1998-01-15 | 2003-03-18 | Symbol Technologies, Inc. | Mobile internet communication protocol |
WO2000005684A2 (en) * | 1998-07-20 | 2000-02-03 | Easynet Access Inc. | Internet billing |
US6058421A (en) * | 1998-02-04 | 2000-05-02 | 3Com Corporation | Method and system for addressing network host interfaces from a cable modem using DHCP |
US6006272A (en) * | 1998-02-23 | 1999-12-21 | Lucent Technologies Inc. | Method for network address translation |
US6353614B1 (en) * | 1998-03-05 | 2002-03-05 | 3Com Corporation | Method and protocol for distributed network address translation |
US6154776A (en) * | 1998-03-20 | 2000-11-28 | Sun Microsystems, Inc. | Quality of service allocation on a network |
US6831914B1 (en) * | 1998-03-27 | 2004-12-14 | Verizon Services Corp. | Services control point selection in an advanced intelligent network |
US6556584B1 (en) * | 1998-04-06 | 2003-04-29 | Motorola, Inc. | System and method of communicating non-standardized addresses over a standardized carrier network |
US6173316B1 (en) | 1998-04-08 | 2001-01-09 | Geoworks Corporation | Wireless communication device with markup language based man-machine interface |
US6195705B1 (en) * | 1998-06-30 | 2001-02-27 | Cisco Technology, Inc. | Mobile IP mobility agent standby protocol |
US6385169B1 (en) * | 1998-07-29 | 2002-05-07 | Lucent Technologies Inc. | Allocation of bandwidth in a packet switched network among subscribers of a service provider |
US6438100B1 (en) * | 1998-08-07 | 2002-08-20 | Alcatel Canada Inc. | Method and apparatus for routing server redundancy in a network having carrier scale internetworking |
US6182228B1 (en) * | 1998-08-17 | 2001-01-30 | International Business Machines Corporation | System and method for very fast IP packet filtering |
US6442588B1 (en) * | 1998-08-20 | 2002-08-27 | At&T Corp. | Method of administering a dynamic filtering firewall |
US6735190B1 (en) * | 1998-10-21 | 2004-05-11 | Lucent Technologies Inc. | Packet transport method device utilizing header removal fields |
US6263369B1 (en) * | 1998-10-30 | 2001-07-17 | Cisco Technology, Inc. | Distributed architecture allowing local user authentication and authorization |
US6490289B1 (en) * | 1998-11-03 | 2002-12-03 | Cisco Technology, Inc. | Multiple network connections from a single PPP link with network address translation |
US6427174B1 (en) * | 1998-11-12 | 2002-07-30 | Cisco Technology, Inc. | Dynamic IP addressing and quality of service assurance |
US6651105B1 (en) * | 1998-11-12 | 2003-11-18 | International Business Machines Corporation | Method for seamless networking support for mobile devices using serial communications |
US6427170B1 (en) * | 1998-12-08 | 2002-07-30 | Cisco Technology, Inc. | Integrated IP address management |
US6636894B1 (en) * | 1998-12-08 | 2003-10-21 | Nomadix, Inc. | Systems and methods for redirecting users having transparent computer access to a network using a gateway device having redirection capability |
US6657991B1 (en) * | 1998-12-21 | 2003-12-02 | 3Com Corporation | Method and system for provisioning network addresses in a data-over-cable system |
US6789118B1 (en) * | 1999-02-23 | 2004-09-07 | Alcatel | Multi-service network switch with policy based routing |
US6434627B1 (en) * | 1999-03-15 | 2002-08-13 | Cisco Technology, Inc. | IP network for accomodating mobile users with incompatible network addressing |
AU3529500A (en) * | 1999-03-17 | 2000-10-04 | Broadcom Corporation | Network switch |
US7349391B2 (en) * | 1999-03-19 | 2008-03-25 | F5 Networks, Inc. | Tunneling between a bus and a network |
US6393484B1 (en) * | 1999-04-12 | 2002-05-21 | International Business Machines Corp. | System and method for controlled access to shared-medium public and semi-public internet protocol (IP) networks |
US6553028B1 (en) * | 1999-04-30 | 2003-04-22 | Cisco Technology, Inc. | Method and apparatus for multicast switching using a centralized switching engine |
US6697862B1 (en) * | 1999-05-21 | 2004-02-24 | 3Com Corporation | System and method for network address maintenance using dynamic host configuration protocol messages in a data-over-cable system |
US6553423B1 (en) * | 1999-05-27 | 2003-04-22 | Cisco Technology, Inc. | Method and apparatus for dynamic exchange of capabilities between adjacent/neighboring networks nodes |
US6708187B1 (en) * | 1999-06-10 | 2004-03-16 | Alcatel | Method for selective LDAP database synchronization |
US6466964B1 (en) * | 1999-06-15 | 2002-10-15 | Cisco Technology, Inc. | Methods and apparatus for providing mobility of a node that does not support mobility |
WO2000079733A2 (en) * | 1999-06-23 | 2000-12-28 | At & T Wireless Services, Inc. | Methods and apparatus for reducing traffic over a communication link in a computer network |
US6577628B1 (en) * | 1999-06-30 | 2003-06-10 | Sun Microsystems, Inc. | Providing quality of service (QoS) in a network environment in which client connections are maintained for limited periods of time |
US6628654B1 (en) * | 1999-07-01 | 2003-09-30 | Cisco Technology, Inc. | Dispatching packets from a forwarding agent using tag switching |
US6650641B1 (en) * | 1999-07-02 | 2003-11-18 | Cisco Technology, Inc. | Network address translation using a forwarding agent |
US6584071B1 (en) * | 1999-08-03 | 2003-06-24 | Lucent Technologies Inc. | Routing with service level guarantees between ingress-egress points in a packet network |
US6523066B1 (en) * | 1999-08-23 | 2003-02-18 | Harris-Exigent, Inc. | Dynamic distributed memory locking in a computer network |
US6523068B1 (en) * | 1999-08-27 | 2003-02-18 | 3Com Corporation | Method for encapsulating and transmitting a message includes private and forwarding network addresses with payload to an end of a tunneling association |
US6553568B1 (en) * | 1999-09-29 | 2003-04-22 | 3Com Corporation | Methods and systems for service level agreement enforcement on a data-over cable system |
US6603758B1 (en) * | 1999-10-01 | 2003-08-05 | Webtv Networks, Inc. | System for supporting multiple internet service providers on a single network |
US6510144B1 (en) * | 1999-12-07 | 2003-01-21 | Cisco Technology, Inc. | Network layer support to enhance the transport layer performance in mobile and wireless environments |
US6879593B1 (en) * | 1999-12-20 | 2005-04-12 | Intel Corporation | Connections of nodes on different networks |
US6598083B1 (en) * | 1999-12-30 | 2003-07-22 | Intel Corporation | System and method for communicating over a non-continuous connection with a device on a network |
CA2296213C (en) * | 2000-01-07 | 2009-04-14 | Sedona Networks Corporation | Distributed subscriber management |
JP2001216987A (en) * | 2000-01-31 | 2001-08-10 | Honda Motor Co Ltd | Humidifying system for fuel cell |
US6678273B1 (en) * | 2000-02-10 | 2004-01-13 | Semaphore Corporation | Managed private network system |
US6725264B1 (en) * | 2000-02-17 | 2004-04-20 | Cisco Technology, Inc. | Apparatus and method for redirection of network management messages in a cluster of network devices |
US6574214B1 (en) * | 2000-05-25 | 2003-06-03 | Nortel Networks Limited | Reduced overhead tunneling techniques in a communications network having mobile foreign agents |
US6769127B1 (en) * | 2000-06-16 | 2004-07-27 | Minerva Networks, Inc. | Method and system for delivering media services and application over networks |
US6633761B1 (en) * | 2000-08-11 | 2003-10-14 | Reefedge, Inc. | Enabling seamless user mobility in a short-range wireless networking environment |
KR100353892B1 (en) * | 2001-02-19 | 2002-09-28 | 주식회사 파워콤 | A Multi Internet Service Provider System and a Method |
US7079520B2 (en) * | 2001-12-28 | 2006-07-18 | Cisco Technology, Inc. | Methods and apparatus for implementing NAT traversal in mobile IP |
US7224687B2 (en) * | 2002-02-28 | 2007-05-29 | Lucent Technologies Inc. | Method and apparatus for voice over IP network address translation |
US6464210B1 (en) * | 2002-03-22 | 2002-10-15 | Agrimond, Llc | Fluid dissolution apparatus |
US7587498B2 (en) * | 2002-05-06 | 2009-09-08 | Cisco Technology, Inc. | Methods and apparatus for mobile IP dynamic home agent allocation |
US6865184B2 (en) * | 2003-03-10 | 2005-03-08 | Cisco Technology, Inc. | Arrangement for traversing an IPv4 network by IPv6 mobile nodes |
US7505432B2 (en) * | 2003-04-28 | 2009-03-17 | Cisco Technology, Inc. | Methods and apparatus for securing proxy Mobile IP |
US20040260752A1 (en) * | 2003-06-19 | 2004-12-23 | Cisco Technology, Inc. | Methods and apparatus for optimizing resource management in CDMA2000 wireless IP networks |
KR100744530B1 (en) * | 2003-09-17 | 2007-08-01 | 한국전자통신연구원 | Apparatus and method for providing a real-time connection traceback using connection redirection technique |
-
2001
- 2001-03-20 AU AU2001250888A patent/AU2001250888A1/en not_active Abandoned
- 2001-03-20 US US09/812,444 patent/US20020013844A1/en not_active Abandoned
- 2001-03-20 WO PCT/US2001/008849 patent/WO2001071983A1/en active Application Filing
- 2001-03-20 US US09/812,509 patent/US20020016855A1/en not_active Abandoned
- 2001-03-20 US US09/813,258 patent/US20020023160A1/en not_active Abandoned
- 2001-03-20 US US09/812,316 patent/US20020019875A1/en not_active Abandoned
- 2001-03-20 WO PCT/US2001/008846 patent/WO2001071982A1/en active Application Filing
- 2001-03-20 US US09/812,441 patent/US20020038419A1/en not_active Abandoned
- 2001-03-20 US US09/812,323 patent/US7065578B2/en not_active Expired - Fee Related
- 2001-03-20 CA CA002403628A patent/CA2403628C/en not_active Expired - Fee Related
- 2001-03-20 CA CA002403736A patent/CA2403736A1/en not_active Abandoned
- 2001-03-20 AU AU2001287257A patent/AU2001287257A1/en not_active Abandoned
- 2001-03-20 US US09/812,443 patent/US20020023174A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
WO2001071983A1 (en) | 2001-09-27 |
US20020038419A1 (en) | 2002-03-28 |
CA2403628A1 (en) | 2001-09-27 |
US7065578B2 (en) | 2006-06-20 |
US20020023160A1 (en) | 2002-02-21 |
US20020019875A1 (en) | 2002-02-14 |
US20020023171A1 (en) | 2002-02-21 |
US20020013844A1 (en) | 2002-01-31 |
US20020023174A1 (en) | 2002-02-21 |
CA2403628C (en) | 2007-05-01 |
AU2001287257A1 (en) | 2001-10-03 |
US20020016855A1 (en) | 2002-02-07 |
AU2001250888A1 (en) | 2001-10-03 |
WO2001071982A1 (en) | 2001-09-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20020023174A1 (en) | Service selection in a shared access network using dynamic host configuration protocol | |
US7069344B2 (en) | Method and apparatus for coordinating a change in service provider between a client and a server | |
US7027432B2 (en) | Method and apparatus for coordinating a change in service provider between a client and a server with identity based service access management | |
US7058022B1 (en) | Method for managing access to networks by employing client software and a configuration protocol timeout | |
US6986157B1 (en) | Method and system for dynamic service registration in a data-over-cable system | |
US6331987B1 (en) | Method and system for bundling data in a data-over-cable system | |
US6714987B1 (en) | Architecture for an IP centric distributed network | |
US7558863B1 (en) | Support IP pool-based configuration | |
US6223222B1 (en) | Method and system for providing quality-of-service in a data-over-cable system using configuration protocol messaging | |
US6018767A (en) | Method and system for managing subscription services with a cable modem | |
US6351773B1 (en) | Methods for restricting access of network devices to subscription services in a data-over-cable system | |
US6553568B1 (en) | Methods and systems for service level agreement enforcement on a data-over cable system | |
US6442158B1 (en) | Method and system for quality-of-service based data forwarding in a data-over-cable system | |
US9054966B2 (en) | Method and arrangement for network QoS | |
US20010044893A1 (en) | Distributed subscriber management system | |
US20080285569A1 (en) | Device for Session-Based Packet Switching | |
US6560203B1 (en) | Method for changing type-of-service in a data-over-cable system | |
JP4034611B2 (en) | Network system and network branching device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued |