Source: http://www.google.com/patents/US8077732?dq=6,757,710
Timestamp: 2015-07-04 15:09:15
Document Index: 745023874

Matched Legal Cases: ['Application No. 06839794', 'Application No. 06839794', 'Application No. 06839794', 'Application No. 200680042373', 'Application No. 06839794', 'Application No 200680042373']

Patent US8077732 - Techniques for inserting internet protocol services in a broadband access ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsTechniques for inserting a network service in an Ethernet access network operated by an access service provider include sending routing data to customer premises equipment. The access network is between a physical layer link with customer premises equipment and a remote packet switched network. The routing...http://www.google.com/patents/US8077732?utm_source=gb-gplus-sharePatent US8077732 - Techniques for inserting internet protocol services in a broadband access networkAdvanced Patent SearchPublication numberUS8077732 B2Publication typeGrantApplication numberUS 11/273,066Publication dateDec 13, 2011Filing dateNov 14, 2005Priority dateNov 14, 2005Also published asCN101310486A, CN101310486B, EP1949621A2, EP1949621A4, EP1949621B1, US20070110048, WO2007059406A2, WO2007059406A3Publication number11273066, 273066, US 8077732 B2, US 8077732B2, US-B2-8077732, US8077732 B2, US8077732B2InventorsEric Voit, Frank Brockners, Huw Jones, Wojciech DecOriginal AssigneeCisco Technology, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (26), Non-Patent Citations (10), Referenced by (3), Classifications (11), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetTechniques for inserting internet protocol services in a broadband access network
US 8077732 B2Abstract
extracting routing data from configuration data received from an initial access server, which is a dynamic host configuration protocol (DHCP) server;
sending to customer premises equipment the routing data that indicates
a logical network address for a layer 3 access gateway that routes data packet traffic for access to remote packet-switched network, whereby the layer 3 access gateway is at a node of the remote packet-switched network,
a logical network address and a media access control (MAC) address for a layer 3 ancillary gateway being part of a plurality of ancillary gateways that routes data packet traffic for an ancillary service wherein the data packet traffic for the ancillary service is not routed through the access gateway to the remote packet-switched network, and
a range of Internet Protocol (IP) network addresses for one or more servers that provide the ancillary service, the logical network address for the layer 3 ancillary gateway being mapped to the range of IP network addresses, wherein the logical network address for the layer 3 access gateway is mapped to a plurality of IP network addresses not included in the range of IP network addresses, wherein the initial access server includes subscriber routing data indicating a subscriber of the customer premises equipment is authorized to access the ancillary service provided by the one or more servers corresponding to the range of IP network addresses; and
receiving from the customer premises equipment a data packet with a layer 2 destination address, wherein the layer 3 ancillary gateway is part of the plurality of ancillary gateways that operate to direct traffic associated with their specific ancillary service, wherein the data packet is being routed to a selected ancillary service and the layer 2 destination address corresponds to one of the plurality of ancillary gateways that directs traffic to the selected ancillary service, and wherein the layer 2 destination address is a MAC address that is checked against the routing data extracted from the configuration data to verify if the subscriber is authorized to access the selected ancillary service, and wherein if the subscriber is not authorized to access the selected ancillary service then the data packet is processed without forwarding the data packet to the layer 2 destination address, and
wherein the plurality of ancillary gateways are connected to an access network, the access network providing a communication link between the customer premises equipment and the access gateway.
2. A method as recited in claim 1, further comprising the step of receiving the configuration data from a network process of the DHCP server that processes an initial request from the customer premises equipment for communicating with the remote packet-switched network.
said step of receiving the configuration data further comprises receiving a DHCP message with a 121 option directed to the customer premises equipment; and
said step of sending the routing data to the customer premises equipment further comprises forwarding the DHCP message with the 121 option to the customer premises equipment.
4. A method as recited in claim 2, wherein the network process that processes the initial request from the customer premises equipment is a routing information protocol (RIP) address peer process.
5. A method as recited in claim 1, said step of sending the associated routing data further comprising receiving the configuration data in a message to the customer premises equipment from a network process of the DHCP server that processes an initial request from the customer premises equipment for communicating with the remote packet-switched network.
6. A method as recited in claim 5, wherein the network process that processes the initial request from the customer premises equipment is a routing information protocol (RIP) address peer process.
an initial access server, which is a dynamic host configuration protocol (DHCP) server;
a customer premises equipment; and
an intermediate node between the DHCP server and the customer premises equipment comprising:
means for extracting routing data from configuration data received from the initial access server;
means for sending to the customer premises equipment the routing data that indicates
a logical network address for a layer 3 access gateway that routes data packet traffic for access to a remote packet-switched network, whereby the layer 3 access gateway is at a node of the remote packet-switched network,
means for receiving from the customer premises equipment a data packet with a layer 2 destination address, wherein the layer 3 ancillary gateway is part of the plurality of ancillary gateways that operate to direct traffic associated with their specific ancillary service, wherein the data packet is being routed to a selected ancillary service and the layer 2 destination address corresponds to one of the plurality of ancillary gateways that directs traffic to the selected ancillary service, and wherein the layer 2 destination address is a MAC address that is checked against the routing data extracted from the configuration data to verify if the subscriber is authorized to access the selected ancillary service, and wherein if the subscriber is not authorized to access the selected ancillary service then the data packet is processed without forwarding the data packet to the layer 2 destination address, and
means for receiving configuration data from the initial access server, the configuration data including routing data that indicates:
a range of Internet Protocol (IP) network addresses for one or more servers that provide the ancillary service, the logical network address for the layer 3 ancillary gateway being mapped to the range of IP network addresses, wherein the logical network address for the layer 3 access gateway is mapped to a plurality of IP network addresses not included in the range of IP network addresses, wherein the initial access server includes subscriber routing data indicating a subscriber of the customer premises equipment is authorized to access the ancillary service provided by the one or more servers corresponding to the range of IP network addresses;
means for extracting the routing data from the configuration data; and
means for receiving from the customer premises equipment a data packet with a layer 2 destination address;
wherein the layer 3 ancillary gateway is part of the plurality of ancillary gateways that operate to direct traffic associated with their specific ancillary service, wherein the data packet is being routed to a selected ancillary service and the layer 2 destination address corresponds to one of the plurality of ancillary gateways that directs traffic to the selected ancillary service, and wherein the layer 2 destination address is a MAC address that is checked against the routing data extracted from the configuration data to verify if the subscriber is authorized to access the selected ancillary service, and wherein if the subscriber is not authorized to access the selected ancillary service then the data packet is dropped, and
a network interface that is coupled to an access network for communicating one or more packet flows therewith;
extracting routing data from configuration data received from the initial access server;
sending to the customer premises equipment the routing data that indicates
receiving from the customer premises equipment a data packet with a layer 2 destination address, wherein the layer 3 ancillary gateway is part of the plurality of ancillary gateways that operate to direct traffic associated with their specific ancillary service, wherein the data packet is being routed to a selected ancillary service and the layer 2 destination address corresponds to one of the plurality of ancillary gateways that directs traffic to the selected ancillary service, and wherein the destination address is a MAC address that is checked against the routing data extracted from the configuration data to verify if the subscriber is authorized to access the selected ancillary service, and wherein if the subscriber is not authorized to access the selected ancillary service then the data packet is processed without forwarding the data packet to the layer 2 destination address, and
wherein the plurality of ancillary gateways are connected to the access network, the access network providing a communication link between the customer premises equipment and the access gateway.
10. An apparatus as recited in claim 9, wherein execution of the one or more sequences of instructions further causes the one or more processors to carry out the step of receiving the configuration data from a network process of the DHCP server that processes an initial request from the customer premises equipment for communicating with the remote packet-switched network.
12. An apparatus as recited in claim 10, wherein the network process that processes the initial request from the customer premises equipment is a routing information protocol (RIP) address peer process.
13. An apparatus as recited in claim 9, said step of sending the associated routing data further comprising receiving the routing data in a message to the customer premises equipment from a network process of the DHCP server that processes an initial request from the customer premises equipment for communicating with the remote packet-switched network.
14. An apparatus as recited in claim 13, wherein the network process that processes the initial request from the customer premises equipment is a routing information protocol (RIP) address peer process.
a network interface that is coupled to the access network for communicating one or more packet flows therewith;
receiving configuration data from an initial access server, the configuration data including routing data that indicates:
a logical network address for a layer 3 ancillary gateway that routes data packet traffic for an ancillary service wherein the data packet traffic for the ancillary service is not routed through the access gateway to the remote packet-switched network, and
extracting the routing data from the configuration data; and
receiving from the customer premises equipment a data packet with a layer 2 destination address, wherein the layer 3 ancillary gateway is part of a plurality of ancillary gateways that operate to direct traffic associated with their specific ancillary service, wherein the data packet is being routed to a selected ancillary service and the layer 2 destination address corresponds to one of the plurality of ancillary gateways that directs traffic to the selected ancillary service, and wherein the layer 2 destination address is a media access control (MAC) address, which is included in the routing data, and the MAC address is checked against the routing data extracted from the configuration data to verify if the subscriber is authorized to access the selected ancillary service, and
wherein if the subscriber is not authorized to access the selected ancillary service then the data packet is dropped, and wherein the plurality of ancillary gateways are connected to the access network, the access network providing a communication link between the customer premises equipment and the access gateway.
16. The apparatus as recited in claim 15, said step of receiving the configuration data further comprising receiving the configuration data in a message to the customer premises equipment from a network process of the DHCP server that processes an initial request from the customer premises equipment for communicating with the remote packet-switched network.
17. The apparatus as recited in claim 16 said step of receiving the configuration data further comprising:
receiving the routing data in a DHCP message with a 121 option directed to the customer premises equipment; and
forwarding the DHCP message with the 121 option to the customer premises equipment.
FIG. 1A is a block diagram that illustrates a network that provides remote access to a core packet-switched network for communications between distant end nodes, according to an embodiment. An internet is a geographically distributed collection of interconnected sub-networks (e.g., sub-networks 110 a, 110 b, 110 c, 110 d collectively referenced hereinafter as sub-networks 110) for transporting data between nodes, such as computers, personal digital assistants and cell phones. A local area network (LAN) 110 a is an example of such a sub-network. The network's topology is defined by an arrangement of end nodes (e.g., end nodes 120 a, 120 b, 120 c, 120 d, collectively referenced hereinafter as end nodes 120) that communicate with one another, typically through one or more intermediate network nodes, such as a router or switch, that facilitates routing data between end nodes 120 on different sub-networks. As used herein, an end node 120 is a node that is configured to originate or terminate communications over the network. In contrast, an intermediate network node facilitates the passage of data between end nodes. Intermediate network nodes depicted in FIG. 1A include customer premises equipment (CPE) 150 a, 150 b, access modules 162 a, 162 b, and Broadband Remote Access Server (BRAS) node 164.
Four sub-networks 110 that are typically involved in remote access are depicted in FIG. 1A. Each sub-network 110 may includes zero or more intermediate network nodes. A core packet-switched network 110 d is the target for remote access by users at a customer site 102.
To access core network 110 d, a LAN 110 a is connected to CPE 150 a which serves as a bridge to an access module 162 a. In an illustrated embodiment, LAN 110 a uses Ethernet infrastructure. Although the customer site 102 includes an Ethernet LAN 110 a and two end nodes 120 a, 120 b, in other embodiments more or fewer end nodes 120 are connected to more or fewer or different LANs 110, such as one or more LANs using Asynchronous Transfer Mode (ATM) infrastructure.
The link between the CPE 150 and its corresponding access module is a physical layer (layer 1) connection. In some cases CPE is a telephone modem using acoustic frequency electrical signals over a low-bandwidth legacy telephone system. In some cases CPE is a cable modem using high frequency electrical signals over a cable system. In some cases CPE is an optical modem using optical signals over a fiber optic system. In some cases CPE is a wireless modem using wireless signals to distributed antennas. In an illustrated embodiment, CPE 150 a is a digital subscriber line (DSL) modem for establishing a high bandwidth DSL connection over a telephone wire circuit-switched network. According to some embodiments of the invention, the CPE includes a routing table 151 for determining layer 3 addresses, such as IP addresses, of intermediate network nodes that handle traffic for ranges of layer 3 destinations. The use of routing table 151 is described in more detail in a later section. In an illustrated embodiment, the protocol used for communications over the link from CPE 150 a to access module 162 a is ATM encapsulated in DSL (ATM/DSL).
Although two CPE 150 a, 150 b are depicted connected to access module 162 a, in other embodiments more or fewer CPE are connected to access module 162 a. In an illustrated embodiment, access module 162 a is a DSL Access Module (DSLAM). In other embodiments, access module 162 a is a controller for a bank of low-bandwidth modems or a cable or optical or wireless access module. According to some embodiments of the invention, access module 162 a includes an enforcer process 161, as described in more detail in a later section with reference to FIG. 4.
An access service provider (ASP) typically maintains several access modules 162 a, 162 b (collectively referenced hereinafter as a module 162) and an access network 110 c for connection to the core network 110 d through a remote access server, such as Broadband Remote Access Server (BRAS) 164 on an intermediate network node. In many former access networks, the access network is based on an ATM infrastructure, and the base communication protocol is ATM. In embodiments that use techniques of the current invention, the access network 110 c is based on an infrastructure that supports layer 2 switching and broadcasts. In the illustrated embodiment, the access network is an Ethernet access network 110 c based on Ethernet infrastructure. Although one BRAS 164 in one core network is depicted in FIG. 1A, in other embodiments, more remote access servers connected to the same or different packet-switched core networks are connected to access network 110 c. An Internet Service Provider (ISP) typically maintains a gateway server (not shown) on the core network 110 d for processing all traffic from its subscribers using a layer 3 protocol such as IP. Multiple ISPs may contract with the same ASP for use of the same access network 110 c. Each such ISP maintains its own gateway server (not shown) on the core network 110 d. According to various embodiments of the current invention, one or more gateway servers are provided on access network 110 c for supporting ancillary services other than access to core network 110 d. In the illustrated embodiment, the gateway servers for ancillary services (collectively referenced hereinafter as ancillary gateways 174) include broadcast gateway 174 a for audio or video or other broadcast data, video on demand (VOD) gateway 174 b, voice over IP (VOIP) gateway 174 c, and other gateway 174 d, such as a gateway that provides a layer 2 virtual private network (L2VPN). It is understood that an ancillary gateway 174 can be a single server, or a gateway to a cluster of multiple servers with or without a load balancer for distributing traffic among the cluster of servers.
Although, the initial access server 172 is connected to the access network 110 c in the illustrated embodiment, in other embodiments the initial access server 172 is connected to another sub-network, such as the core network 110 d. In some embodiments, the initial access server 172 is included in, or shares a host with, the BRAS 164. The initial access server 172 includes subscriber routing data 171, which includes data that indicates which of the ancillary gateways 174 can be used by a particular subscriber associated with a particular customer site and CPE.
According to embodiments of the invention, a CPE uses special routing information in routing table 151 to direct data packets to an ancillary gateway 174 connected to the access network 110 c instead of to the RAS, such as BRAS 164. The routing table 151 includes layer 3 addresses (e.g., IP addresses) for one or more of the ancillary gateways 174 on the access network 110 c. In some embodiments, the routing table 151 is statically configured. In an illustrated embodiment, data for the routing table 151 is customer specific and is dynamically configured based on subscriber routing data 171 in the initial access server 172, as described in more detail in a later section with reference to FIG. 4.
In some embodiments, the data packets from the CPE are still included in tunneled traffic, e.g. PPP traffic, to an access module; however, the access module (e.g., 162 a) extracts the PPP payload and forwards it according to a layer 2 protocol, e.g., Ethernet. For example, access module 162 a extracts a PPP data plane payload from CPE 150 a, determines a MAC destination address for one of the ancillary gateways 174 and forwards the PPP data plane payload according to that MAC destination. In the illustrated embodiment, an IP datagram arrives from the CPE over a direct link and is not encapsulated in a tunneling protocol like PPP.
In some embodiments, an access module 160 includes the enforcer process 161 that ensures the MAC destination is consistent with the configuration data for the CPE, such as the subscriber routing information 171 sent from the initial access server 172. The enforcer resolves the IP addresses of the ancillary servers in the routing information to the corresponding MAC addresses using any method known in the art, e.g., the Address Resolution Protocol (ARP). Thus, the enforcer process 161 makes sure the CPE does not receive services for which the customer associated with the CPE is not a subscriber. The workings of the enforcer process 161 are described in a later section with reference to FIG. 4 FIG. 1B is a block diagram that illustrates in more detail an Ethernet access network component of the network depicted in FIG. 1A, according to an embodiment 130. In this embodiment, the Ethernet access network 130 connects an access module 162 to BRAS 164. The Ethernet access network 130 includes two intermediate network nodes, a local office intermediate network node 132 (also called “local office node” 132) and a metro area intermediate network node 134 (also called a “metro area node” 134). In other embodiments, more or fewer intermediate network nodes are included in Ethernet access network 110 c. In the illustrated embodiment, the intermediate network nodes are Ethernet bridges or switches that preserve MAC addresses in the data packets they transmit.
In the illustrated embodiment, segment 131 a connects access module 162 to the local office node 132, and segments 131 b, 131 c, 131 d connect other access modules (not shown) to local office node 132. Segment 131 e connects the local office node 132 to metro area node 134, and segments 131 f, 131 g, 131 h connect other local office nodes (not shown) to metro area node 134. Segment 131 i connects the metro area node 134 to BRAS 164, and other segments (not shown) connect other metro area nodes (not shown) to BRAS 164. The illustrated segments 131 show how Ethernet segments are used to scale up to a large number of customer sites. For example, in some access networks, there are a few customer sites per access module, dozens of access modules per local office node, dozens of local offices per metro area, and a few metro area nodes connected to a BRAS; thus a single BRAS handles traffic from thousands of customer sites.
According to embodiments of the invention, ancillary services are pushed closer to the access modules, and therefore closer to the customer sites. In the illustrated embodiment, the broadcast gateway 174 a and VOD gateway 174 b are connected to network segment 131 e. Similarly, VoIP gateway 174 c and other gateway 174 d are connected to network segment 131 i. The initial access server 172 is also connected to network segment 131 i. In other embodiments, one or more of the gateways are located on other segments of the access network.
In the circuit switched scenario of prior approaches the tunnels ensured separation of traffic. In an Ethernet/DSL scenario the request to access multicast/broadcast traffic is intercepted on the DSLAM (e.g., access module 162 a), and based on either configured or dynamic policy, forwarding of the broadcast is allowed from the segment (e.g., 131 a) connected to the access module (e.g., 162) to that user (e.g., via CPE 150 a). The forwarding is based on the Internet Group Management Protocol (IGMP) and the ability of the access module (162) to snoop IGMP and allow or deny traffic. The use of IP multicasting in TCP/IP networks is defined as a TCP/IP standard in RFC 1112, “Internet Group Management Protocol (IGMP).” In addition to defining address and host extensions for how IP hosts support multicasting, this RFC also defines the Internet Group Management Protocol (IGMP) version 1. RFC 2236 defines IGMP version 2. Both versions of IGMP provide a protocol to exchange and update information about host membership in specific multicast groups. The entire contents of RFC 1112, RFC 2236 are herby incorporated by reference as if fully set forth herein. IGMP version 3, described in the Internet draft entitled “Internet Group Management Protocol, version 3,” allows hosts to specify interest in receiving multicast traffic from specified sources or from all but a specific set of sources.
FIG. 2 is a block diagram that illustrates a data structure 200 for storing routing information on customer premises equipment, according to an embodiment. In other embodiments, other routing tables, including other conventional routing tables, are used. The data structure 200 includes multiple IP routing records 210 a, 210 b and others indicated by ellipsis 219, collectively referenced hereinafter as IP routing records 210. Routing records 210 a, 210 b each includes a destination range start address field 212 a, 212 b, respectively (collectively referenced hereinafter as destination start field 212). Routing records 210 a, 210 b each includes a destination net mask field 214 a, 214 b, respectively (collectively referenced hereinafter as destination net mask field 214). Routing records 210 a, 210 b each includes a service gateway address field 216 a, 216 b, respectively (collectively referenced hereinafter as gateway address field 216). As is well known in the art of IP routing, a range of contiguous IP addresses can be indicated by a starting IP address and a mask. For example, an IPv4 address is a four octet value, where an octet is eight binary digits (bits). An IPv4 address is often represented by four decimal values between 0 and 255 separated by periods. A mask is a four octet value that has zero at bits that can change within the range of addresses and a value of 1 at bits that can not change within the range of addresses, but must match the bits in the starting address.
According to many embodiments of the invention, the routing data structure 200 is stored at CPE to determine a range of IP addresses to associate with each of one or more ancillary gateways 174. For example, a variety of video on demand servers with a corresponding variety of IP addresses are reached through VOD gateway 174 b with a particular IP address on the Ethernet access network 130. Thus the IP addresses of all those VOD severs are associated with the IP address of gateway 174 b, which acts as a gateway for those servers. The routing information indicates all traffic to any of those VOD servers are directed first to VOD gateway 174 b. If the set of VOD servers have IP addresses that are not contiguous, then multiple records are inserted into data structure 200, one for each contiguous set of addresses (called a subnet).
For some services such as video that do not allow access from the internet, private addresses are used in the homes and on the server for this service in some embodiments. These private addresses are not advertised outside of the access network 110 c. This allows the same addresses to be used in other access networks. Thus valuable network address space is conserved.
Destinations that
68.34.0.1
Broadcast & multi-cast video
Video on demand (gateway 174b)
Voice over IP (gateway 174c)
Other, e.g., Ethernet layer 2 VPN
CPE IP
According to several embodiments, during step 330, DHCP option 121 fields are included in the DHCP response. Based on the subscriber ID of“X1” and the service data in Table 2, the DHCP server determines that broadcast and VoIP services are to be allowed for the CPE making the DHCP request. Therefore, the DHCP response includes the IP addresses of gateways 174 a and 174 c as given in Table 1 which function as gateways for a cluster of servers that provide the subscribed service. A range of addresses for the cluster of servers that provide each service, such as listed in the last two columns of Table 1, are also included in the DHCP option 121 response.
Based on the DHCP 121 option, the receiving CPE forms a routing table 151 with the information for the subscribed services, as shown in Table 3. This information will cause the CPE to direct requests for broadcast services at addresses 192.168.22.1 through 192.168.22.255 to the broadcast gateway 174 a; and direct requests for VoIP services at addresses 10.10.0.20 through 10.10.255.255 to VoIP gateway 174 c; and direct all other requests to the BRAS 164. In effect option 121 supplies a routing table to the CPE, so the CPE has a destination and a next hop in the option. The CPE resolves the layer 2 MAC address by the Address Resolution Protocol (ARP), which maps IP network addresses to the hardware addresses used by a data link protocol. The protocol operates below the network layer 3 when IPv4 is used over Ethernet. ARP is described in RFC 826, the entire contents of which are herby incorporated by reference as if fully set forth herein. When a packet is sent to a destination, the destination is looked up in the routing/forwarding table. If there is an explicit match or the destination is in an explicit range, then the corresponding gateway is used by sending a data packet to the next hop MAC address that corresponds to that gateway. If there is no explicit match and the destination is not in an explicit range, then the default gateway (e.g., the BRAS in the first row of Table 3) is used.
Destinations start
Destinations net
FIG. 4 is a flow diagram that illustrates at a high level a method 400 for enforcing routing for services on an access network, according to an embodiment. This method is executed by a routing enforcer process, e.g., enforcer process 161. The enforcer process operates on any network node that is disposed on every path from the CPE to any ancillary gateway 174 in the access network 110 c. In some embodiments, the enforcer process 161 executes on an access node, e.g., access module 162 a. In an illustrated embodiment, the enforcer process 161 executes on the local office intermediate network node 132. In some embodiments, the enforcer process also operates on a backup device that is pressed into service if the original host fails for any reason.
In step 430, the configuration message is forwarded to the CPE. In the illustrated embodiment, the DHCP message is forwarded to the CPE. For example, a DHCP message with the data of Table 3 in an option 121 message from initial access server 172 is forwarded by local office intermediate network node 132 to CPE 150 a by way of access module 162 a. In some embodiments, steps 410, 420, 430 are omitted, and both the CPE and the enforcing process are statically configured with the routing data, e.g., with the data depicted in Table 3.
In step 450, it is determined whether the MAC destination is among the MAC addresses corresponding to the service gateway IP addresses that the CPE was configured for. For example, it is determined in step 450 whether the MAC destination corresponds to one of the IP addresses in the third column of table 3. If not, then the CPE is attempting to reach a service that it did not subscribe to, and control passes to step 452 to drop the packet and not process it further. In some embodiments, the packet is forwarded to the default remote access server (RAS) such as the BRAS 164 If it is determined in step 450 that the MAC destination corresponds to an IP address among the service gateway addresses that the CPE was configured for, then the packet is forwarded to the gateway. Thus the packet is directed to one of the gateways for which the CPE was configured. The packet is also received by other nodes on the same segment, and ignored unless that node is involved in a multi-cast or broadcast.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS6424657Dec 26, 2000Jul 23, 2002Verizon Communications Inc.Traffic queueing for remote terminal DSLAMsUS6512762Feb 11, 2000Jan 28, 2003General Bandwidth, Inc.System and method for communicating telecommunication information between customer premises equipment and network equipmentUS6704301Dec 29, 2000Mar 9, 2004Tropos Networks, Inc.Method and apparatus to provide a routing protocol for wireless devicesUS6778525Aug 31, 2000Aug 17, 2004Verizon Communications Inc.Automated service provisioning in combination of vertical services and digital subscriber line domainsUS6798751Dec 7, 2000Sep 28, 2004Verizon Communications Inc.Customer premises equipment for vertical services integrationUS6904054Aug 10, 2000Jun 7, 2005Verizon Communications Inc.Support for quality of service and vertical services in digital subscriber line domainUS7382778Jan 5, 2004Jun 3, 2008Tropos Networks, Inc.Link layer emulationUS7506065Nov 26, 2003Mar 17, 2009Hewlett-Packard Development Company, L.P.Remote mirroring using IP encapsulationUS7839855Jan 9, 2007Nov 23, 2010Cisco Technology, Inc.Layer 2 address translation for service provider wholesale IP sessionsUS20010019557Jan 16, 2001Sep 6, 2001Scientific-Atlanta, IncMethods for dynamically assigning link addresses and logical network addressesUS20020044567Dec 7, 2000Apr 18, 2002Voit Eric A.Automatic programming of customer premises equipment for vertical services integrationUS20020085552Sep 13, 2001Jul 4, 2002Narad Networks, Inc., Westford MassachusettsBroadband system having routing identification assignmentUS20020186698Jun 12, 2001Dec 12, 2002Glen CenizaSystem to map remote lan hosts to local IP addressesUS20040264443 *Jun 16, 2004Dec 30, 2004AlcatelDigital subscriber line access network with improved authentication, authorization, accounting and configuration control for multicast servicesUS20050152370 *Sep 30, 2004Jul 14, 2005Meehan Thomas J.Protocol for messaging between a centralized broadband remote aggregation server and other devicesUS20050286503 *Jun 23, 2005Dec 29, 2005Sotaro OdaCommunication deviceUS20060028983Aug 6, 2004Feb 9, 2006Wright Steven AMethods, systems, and computer program products for managing admission control in a regional/access network using defined link constraints for an applicationUS20060045075 *Aug 19, 2005Mar 2, 2006AlcatelMethod of selecting services provided by different network service providersUS20060045085 *Aug 24, 2004Mar 2, 2006Haixiang HeMethod and apparatus for authorizing multicast forwarding statesUS20060198302 *Mar 2, 2006Sep 7, 2006Sofman Lev BTraffic dimensioning in a metro area with IPTV architectureUS20070110048 *Nov 14, 2005May 17, 2007Cisco Technologies, Inc.Techniques for inserting internet protocol services in a broadband access networkUS20070274321 *Mar 17, 2004Nov 29, 2007Jonsson Ulf FVlan Mapping For Multi-Service ProvisioningUS20090129386 *Apr 29, 2005May 21, 2009Johan RuneOperator Shop SelectionCN101310486ANov 9, 2006Nov 19, 2008思科技术公司Techniques for inserting internet protocol services in a broadband access networkEP1949621A2Nov 9, 2006Jul 30, 2008Cisco Technology, Inc.Techniques for inserting internet protocol services in a broadband access networkWO2007059406A2Nov 9, 2006May 24, 2007Cisco Tech IncTechniques for inserting internet protocol services in a broadband access network* Cited by examinerNon-Patent CitationsReference1EPO Extended European Search Report and Search Opinion dated Feb. 15, 2011 for Application No. 06839794.2-2415/1949621 PCT/US2006/060720; 10 pages.2EPO Mar. 4, 2011 Communication from EP Application No. 06839794.2; 1 page.3EPO Oct. 11, 2011 Communication from EP Application No. 06839794.2; 5 pages.4International Preliminary Report on Patentability (1 page) and Written Opinion of the International Searching Authority (7 pages) for International Application No. PCT/US06/60720 mailed Oct. 26, 2007.5 *Lemon et al., "RFC 3442, The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4," Dec. 2002, The Internet Society.6Mar. 11, 2011 Response to State Intellectual Property Office of the People's Republic of China First Office Action dated Oct. 27, 2010 (untranslated) and amended claimes (translated), Application No. 200680042373.9, 48 pages.7Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration (1 page) and International Search Report (2 pages) for International Application No. PCT/US06/60720 mailed Oct. 26, 2007.8Sep. 6, 2011 Response to EPO Communication dated Mar. 4, 2011 from EP Application No. 06839794.2; 20 pages.9State Intellectual Property Office of the People's Republic of China, Application No 200680042373.9, Date of Issue Oct. 27, 2010, The First Office Action, 20 pages.10T-Joens, Y., "DHCP Reconfigure Extension," Network Working Group RFC 3203, Dec. 2001, 6 pages; http://tools.ietf.org/pdf/rfc3203.pdf.* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS8817799 *Apr 14, 2011Aug 26, 2014Broadcom CorporationNetwork processor for supporting residential gateway applicationsUS20110142212 *Sep 28, 2010Jun 16, 2011Electronics And Telecommunications Research InstituteMethod and apparatus for providing service oriented common access network serviceUS20120263462 *Apr 14, 2011Oct 18, 2012Broadlight, Ltd.Network Processor for Supporting Residential Gateway Applications* Cited by examinerClassifications U.S. Classification370/401, 370/352, 370/409International ClassificationH04L12/56, H04L12/28Cooperative ClassificationH04L45/66, H04L12/4633, H04L45/54European ClassificationH04L12/46E, H04L45/66, H04L45/54Legal EventsDateCodeEventDescriptionNov 14, 2005ASAssignmentFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VOIT, ERIC;BROCKNERS, FRANK;JONES, HUW;AND OTHERS;SIGNING DATES FROM 20051027 TO 20051108;REEL/FRAME:017237/0083Owner name: CISCO TECHNOLOGY, INC., CALIFORNIAOwner name: CISCO TECHNOLOGY, INC.,CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VOIT, ERIC;BROCKNERS, FRANK;JONES, HUW;AND OTHERS;SIGNING DATES FROM 20051027 TO 20051108;REEL/FRAME:017237/0083Owner name: CISCO TECHNOLOGY, INC.,CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VOIT, ERIC;BROCKNERS, FRANK;JONES, HUW AND OTHERS;SIGNEDBETWEEN 20051027 AND 20051108;US-ASSIGNMENT DATABASE UPDATED:20100225;REEL/FRAME:17237/83Owner name: CISCO TECHNOLOGY, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VOIT, ERIC;BROCKNERS, FRANK;JONES, HUW;AND OTHERS;SIGNING DATES FROM 20051027 TO 20051108;REEL/FRAME:017237/0083RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services