US 6,775,276 B1Grant
Method and system for seamless address allocation in a data-over-cable system
Issue Date:2004-08-10
•27 Claims
•28 Drawing Sheets
Abstract
A method and system is provided to send and receive Dynamic Host Configuration Protocol (“DHCP”) messages in a data-over-cable system via a route with one or more routers. The routers may apply one or more different protocol filters to DHCP messages, such as filtering out DHCP messages with a “Martian” Internet Protocol (“IP”) address (e.g., 0.0.0.0) and other characteristics. The Martian IP address is commonly used as an initial IP address in a DHCP initialization sequence but is often filtered out by routers as an invalid IP address. DHCP messages are received by a first protocol agent from a first User Datagram Protocol (“UDP”) port. The first UDP port is used by DHCP servers and network devices such as cable modems and customer premise equipment to send and receive DHCP messages via a route that may apply one or more DCHP filters. The first protocol agent sends the DHCP messages to a second protocol agent on a second UDP port via a route that does not apply filters to the DHCP messages. The first protocol agent receives DHCP messages from the second protocol agent on the second UDP port. The first protocol agent sends messages back to a DHCP protocol server or network device such as a cable modem on the first UDP port. The protocol agent allows DHCP messaging to be seamlessly used in a data-over-cable system with routers that apply a variety of protocol filters to DHCP messages.
Metadata
Assignee
- 3Com Corporation
Inventor
- Nurettin B. Beser
Application Information
Application Number:US 09/085,555
Filing Date:1998-05-27
Priority Date:1998-05-27
Art Unit:7
Classifications
IPC:
H04L 1228H04L 1256
Field of Search:
370351370352370353370354370342370347370431370469370389709223709224709225709227709228709229709230709237709238709232709246713201
Patent Drawings (28 sheets)
Description
Field of Invention
[0002] The present invention relates to communications in computer networks. More specifically, it relates to a method and system for protocol messaging in a cable modem in a data-over-cable system.
Background of the Invention
[0003] Cable television networks such as those provided by Comcast Cable Communications, Inc., of Philadelphia, Pa., Cox Communications of Atlanta Ga., Tele-Communications, Inc., of Englewood, Colo., Time-Warner Cable, of Marietta, Ga., Continental Cablevision, Inc., of Boston, Mass., and others provide cable television services to a large number of subscribers over a large geographical area. The cable television networks typically are interconnected by cables such as coaxial cables or a Hybrid Fiber/Coaxial (“HFC”) cable system which have data rates of about 10 Mega-bits-per-second (“Mbps”) to 30+ Mbps.
[0004] The Internet, a world-wide-network of interconnected computers, provides multi-media content including audio, video, graphics and text that typically require a large bandwidth for downloading and viewing. Most Internet Service Providers (“ISPs”) allow customers to connect to the Internet via a serial telephone line from a Public Switched Telephone Network (“PSTN”) at data rates including 14,400 bps, 28,800 bps, 33,600 bps, 56,000 bps and others that are much slower than the about 10 Mbps to 30+ Mbps available on a coaxial cable or HFC cable system on a cable television network.
[0005] With the explosive growth of the Internet, many customers have desired to use the larger bandwidth of a cable television network to connect to the Internet and other computer networks. Cable modems, such as those provided by 3Com Corporation of Santa Clara, Calif., Motorola Corporation of Arlington Heights, Ill., Hewlett-Packard Co. of Palo Alto, Calif., Bay Networks of Santa Clara, Calif., Scientific-Atlanta, of Norcross, Ga. and others offer customers higher-speed connectivity to the Internet, an intranet, Local Area Networks (“LANs”) and other computer networks via cable television networks. These cable modems currently support a data connection to the Internet and other computer networks via a cable television network with a data rate of up to 30+ Mbps which is a much larger data rate than can be supported by a modem used over a serial telephone line.
[0006] However, most cable television networks provide only uni-directional cable systems, supporting only a “downstream” data path. A downstream data path is the flow of data from a cable system “headend” to a customer. A cable system headend is a central location in the cable television network that is responsible for sending cable signals in the downstream direction. A return data path via a telephone network, such as a public switched telephone network provided by AT&T and others, (i.e., a “telephony return”) is typically used for an “upstream” data path. An upstream data path is the flow of data from the customer back to the cable system headend. A cable television system with an upstream connection to a telephony network is called a “data-over-cable system with telephony return.”
[0007] An exemplary data-over-cable system with telephony return includes customer premise equipment (e.g., a customer computer), a cable modem, a cable modem termination system, a cable television network, a public switched telephone network, a telephony remote access concentrator and a data network (e.g., the Internet). The cable modem termination system and the telephony remote access concentrator together are called a “telephony return termination system.”
[0008] The cable modem termination system receives data packets from the data network and transmits them downstream via the cable television network to a cable modem attached to the customer premise equipment. The customer premise equipment sends response data packets to the cable modem, which sends response data packets upstream via public switched telephone network to the telephony remote access concentrator, which sends the response data packets back to the appropriate host on the data network.
[0009] When a cable modem used in the data-over-cable system with telephony return is initialized, a connection is made to both the cable modem termination system via the cable network and to the telephony remote access concentrator via the public switched telephone network. As a cable modem is initialized, it will initialize one or more downstream channels (i.e., downstream connections) to the cable modem termination system via the cable network or the telephony remote access concentrator via the public switched telephone network.
[0010] As a cable modem is initialized in a data-over-cable system, it registers with a cable modem termination system to allow the cable modem to receive data over a cable television connection and from a data network (e.g., the Internet or an Intranet). The cable modem forwards configuration information it receives in a configuration file during initialization to the cable modem termination system as part of a registration request message.
[0011] Many data-over-cable systems in the prior art use a Dynamic Host Configuration Protocol (“DHCP”) as a standard messaging protocol to allocate network addresses such as Internet Protocol (“IP”) addresses. As is known in the art, DHCP is a protocol for passing configuration information to network devices on a network. IP is an addressing protocol designed to route traffic within a network or between networks. DHCP uses User Datagram Protocol (“UDP”) as a transport protocol. DHCP messages sent from a network device to a DHCP server are sent via UDP DHCP server-port-67, and DHCP messages from a DHCP server to a network device are sent via UDP DHCP client-port-68. DHCP messaging starts with the use of a “Martian” IP address (e.g., 0.0.0.0) as a source address for a network device (e.g., a cable modem) since no legitimate IP address has been assigned to the network device.
[0012] Since a DHCP server may be at a different geographical location from other network devices in the data-over-cable system, DHCP messages may pass through one or more routers on a network such as the data-over-cable system. As is known in the art, routers route data packets to an appropriate network device on a network based on a network address.
[0013] Routers typically use one or more types of filters to provide varying levels of security to a network. For example, a first type of router may filter all inbound messages that do not have an IP address for a specified network (e.g., an intranet). A second type of router may filter all outbound messages that are not addressed to a specific IP address. In a data-over-cable system, many routers have default filters that filter out all external DHCP messages regardless of the source address to prevent a rogue network device from being assigned a legitimate IP address on the data-over-cable system. In addition, many routers in a data-over-cable system filter DHCP messages with a Martian source address since such a source address is often used to launch an attack on a data-over-cable system.
[0014] Thus, it is desirable to use DHCP messaging to allocate network addresses in a data-over-cable system with routers that may employ DHCP filters. It is also desirable to use DHCP messaging with Martian source addresses with routers that use filters to filter DHCP messages with Martian source addresses.
Summary of the Invention
[0015] In accordance with a preferred embodiment of the present invention, the problems associated with DHCP filters in routers in a data-over-cable system are overcome. A method and system for seamless network address allocation is provided. The method includes receiving a first message with a first protocol from a first network device on a first port on a protocol agent. The first port is used to send messages from the first protocol server via a route that may apply one or more protocol filters to the first protocol. The first message is sent from the protocol agent on a second port. The second port is used to send messages with the first protocol via a route that does not apply protocol filters to the first protocol. A second message is received on the second port on the protocol agent. The second message is sent from the protocol agent to the first network device on the first port.
[0016] In a preferred embodiment of the present invention, the first protocol is DHCP, the first network device is any of a protocol server, cable modem, or cable modem termination system and the first port is a UDP DHCP port (e.g., UDP DHCP port 67 or 68). The second port is a UDP port other than a UDP DHCP port (e.g., other than UDP DHCP port 67 or 68). However, the present invention is not limited to these network devices, protocols and ports, and other network devices, protocols and ports could also be used (e.g., BOOT Transmission Protocol (“BOOTP”) and Transmission Control Protocol (“TCP”) ports).
[0017] The system includes a protocol agent, for sending and receiving messages for a first protocol in a data-over-cable system. The system also includes a protocol agent port for sending and receiving messages for the first protocol in a data-over-cable system. The protocol agent port is used to send and receive messages via a route that does not apply protocol filters to the first protocol in a data-over-cable system. In a preferred embodiment of the present invention, the protocol agent is a DHCP agent, and the protocol agent port is a UDP port other than a UDP DHCP port (e.g., other than UDP port 67 or 68). However, the present invention is not limited to these protocols and ports, and other protocols and ports could also be used.
[0018] The foregoing and other features and advantages of a preferred embodiment of the present invention will be more readily apparent from the following detailed description, which proceeds with references to the accompanying drawings.
Brief Description of the Drawings
[0019] FIG. 1 is a block diagram illustrating a cable modem system with telephony return;
[0020] FIG. 2 is a block diagram illustrating a protocol stack for a cable modem;
[0021] FIG. 3 is a block diagram illustrating a Telephony Channel Descriptor message structure;
[0022] FIG. 4 is a block diagram illustrating a Termination System Information message structure;
[0023] FIG. 5 is a flow diagram illustrating a method for addressing hosts in a cable modem system;
[0024] FIG. 6 is a block diagram illustrating a Dynamic Host Configuration Protocol message structure;
[0025] FIGS. 7A and 7B are a flow diagram illustrating a method for discovering hosts in a cable modem system;
[0026] FIG. 8 is a block diagram illustrating a data-over-cable system for the method illustrated in FIGS. 7A and 7B;
[0027] FIG. 9 is a block diagram illustrating the message flow of the method illustrated in FIGS. 7A and 7B;
[0028] FIGS. 10A and 10B are a flow diagram illustrating a method for resolving host addresses in a data-over-cable system;
[0029] FIG. 11 is a flow diagram illustrating a method for resolving discovered host addresses; and
[0030] FIG. 12 is a block diagram illustrating the message flow of the method illustrated in FIG. 10;
[0031] FIGS. 13A and 13B are a flow diagram illustrating a method for obtaining addresses for customer premise equipment;
[0032] FIGS. 14A and 14B are a flow diagram illustrating a method for resolving addresses for customer premise equipment;
[0033] FIGS. 15A and 15B are a flow diagram illustrating a method for addressing network host interfaces from customer premise equipment;
[0034] FIGS. 16A and 16B are a flow diagram illustrating a method for resolving network host interfaces from customer premise equipment;
[0035] FIG. 17 is a block diagram illustrating a message flow for the methods in FIGS. 15A, 15B, and 16A and 16B;
[0036] FIG. 18 is a block diagram illustrating a data-over-cable system with protocol messaging;
[0037] FIG. 19 is a flow diagram illustrating a method for protocol messaging;
[0038] FIG. 20 is a flow diagram illustrating a method for protocol messaging;
[0039] FIG. 21 is a flow diagram illustrating a method for protocol messaging; and
[0040] FIG. 22 is a flow diagram illustrating a method for protocol messaging.
Detailed Description of a Preferred Embodiment
[0041] Cable Modem System With Telephony Return
[0042] FIG. 1 is a block diagram illustrating a data-over-cable system with telephony return 10, hereinafter data-over-cable system 10. Most cable providers known in the art predominately provide uni-directional cable systems, supporting only a “downstream” data path. A downstream data path is the flow of data from a cable television network “headend” to customer premise equipment (e.g., a customer's personal computer). A cable television network headend is a central location that is responsible for sending cable signals in a downstream direction. A return path via a telephony network (“telephony return”) is typically used for an “upstream” data path in uni-directional cable systems. An upstream data path is the flow of data from customer premise equipment back to the cable television network headend.
[0043] However, data-over-cable system 10 of the present invention may also provide a bi-directional data path (i.e., both downstream and upstream) without telephony return as is also illustrated in FIG. 1 and the present invention is not limited to a data-over-cable system with telephony return. In a data-over cable system without telephony return, customer premise equipment or cable modem has an upstream connection to the cable modem termination system via a cable television connection, a wireless connection, a satellite connection, or a connection via other technologies to send data upstream to the cable modem termination system.
[0044] Data-over-cable system 10 includes a Cable Modem Termination System (“CMTS”) 12 connected to a cable television network 14, hereinafter cable network 14. FIG. 1 illustrates one CMTS 12. However, data-over-cable system 10 can include multiple CMTS 12. Cable network 14 includes cable television networks such as those provided by Comcast Cable Communications, Inc., of Philadelphia, Pa., Cox Communications, or Atlanta, Ga., Tele-Communications, Inc., of Englewood, Colo., Time-Warner Cable, of Marietta, Ga., Continental Cablevision, Inc., of Boston, Mass., and others. Cable network 14 is connected to a Cable Modem (“CM”) 16 with a downstream cable connection. CM 16 is any cable modem such as those provided by 3Com Corporation of Santa Clara, Calif., Motorola Corporation of Arlington Heights, Ill., Hewlett-Packard Co. of Palo Alto, Calif., Bay Networks of Santa Clara, Calif., Scientific-Atlanta, of Norcross, Ga. and others. FIG. 1 illustrates one CM 16. However, in a typical data-over-cable system, tens or hundreds of thousands of CM 16 are connected to CMTS 12.
[0045] CM 16 is connected to Customer Premise Equipment (“CPE”) 18 such as a personal computer system via a Cable Modem-to-CPE Interface (“CMCI”) 20. CM 16 is connected to a Public Switched Telephone Network (“PSTN”) 22 with an upstream telephony connection. PSTN 22 includes those public switched telephone networks provided by AT&T, Regional Bell Operating Companies (e.g., Ameritch, U.S. West, Bell Atlantic, Southern Bell Communications, Bell South, NYNEX, and Pacific Telesis Group), GTE, and others. The upstream telephony connection is any of a standard telephone line connection, Integrated Services Digital Network (“ISDN”) connection, Asymmetric Digital Subscriber Line (“ADSL”) connection, or other telephony connection. PSTN 22 is connected to a Telephony Remote Access Concentrator (“TRAC”) 24. In a data-over cable system without telephony return, CM 16 has an upstream connection to CMTS 12 via a cable television connection, a wireless connection, a satellite connection, or a connection via other technologies to send data upstream outside of the telephony return path. An upstream cable television connection via cable network 14 is illustrated in FIG. 1.
[0046] FIG. 1 illustrates a telephony modem integral to CM 16. In another embodiment of the present invention, the telephony modem is a separate modem unit external to CM 16 used specifically for connecting with PSTN 22. A separate telephony modem includes a connection to CM 16 for exchanging data. CM 16 includes cable modems provided by the 3Com Corporation of Santa Clara, Calif., U.S. Robotics Corporation of Skokie, Ill., and others. In yet another embodiment of the present invention, CM 16 includes functionality to connect only to cable network 14 and receives downstream signals from cable network 14 and sends upstream signals to cable network 14 without telephony return. The present invention is not limited to cable modems used with telephony return.
[0047] CMTS 12 and TRAC 24 may be at a “headend” of cable system 10, or TRAC 24 may be located elsewhere and have routing associations to CMTS 12. CMTS 12 and TRAC 24 together are called a “Telephony Return Termination System” (“TRTS”) 26. TRTS 26 is illustrated by a dashed box in FIG. 1. CMTS 12 and TRAC 24 make up TRTS 26 whether or not they are located at the headend of cable network 14, and TRAC 24 may in located in a different geographic location from CMTS 12. Content severs, operations servers, administrative servers and maintenance servers used in data-over-cable system 10 (not shown in FIG. 1) may also be in different locations. Access points to data-over-cable system 10 are connected to one or more CMTS's 12 or cable headend access points. Such configurations may be “one-to-one”, “one-to-many,” or “many-to-many,” and may be interconnected to other Local Area Networks (“LANs”) or Wide Area Networks (“WANs”).
[0048] TRAC 24 is connected to a data network 28 (e.g., the Internet or an intranet) by a TRAC-Network System Interface 30 (“TRAC-NSI”). CMTS 12 is connected to data network 28 by a CMTS-Network System Interface (“CMTS-NSI”) 32. The present invention is not limited to data-over-cable system 10 illustrated in FIG. 1, and more or fewer components, connections and interfaces could also be used.
[0049] Cable Modem Protocol Stack
[0050] FIG. 2 is a block diagram illustrating a protocol stack 36 for CM 16. FIG. 2 illustrates the downstream and upstream protocols used in CM 16. As is known in the art, the Open System Interconnection (“OSI”) model is used to describe computer networks. The OSI model consists of seven layers including from lowest-to-highest, a physical, data-link, network, transport, session, application and presentation layer. The physical layer transmits bits over a communication link. The data link layer transmits error free frames of data. The network layer transmits and routes data packets.
[0051] For downstream data transmission, CM 16 is connected to cable network 14 in a physical layer 38 via a Radio Frequency (“RF”) Interface 40. In a preferred embodiment of the present invention, RF Interface 40 has an operation frequency range of 50 Mega-Hertz (“MHz”) to 1 Giga-Hertz (“GHz”) and a channel bandwidth of 6 MHz. However, other operation frequencies may also be used and the invention is not limited to these frequencies. RF interface 40 uses a signal modulation method of Quadrature Amplitude Modulation (“QAM”). As is known in the art, QAM is used as a means of encoding digital information over radio, wire, or fiber optic transmission links. QAM is a combination of amplitude and phase modulation and is an extension of multiphase phase-shift-keying. QAM can have any number of discrete digital levels typically including 4, 16, 64 or 256 levels. In one embodiment of the present invention, QAM-64 is used in RF interface 40. However, other operating frequencies modulation methods could also be used. For more information on RF interface 40 see the Institute of Electrical and Electronic Engineers (“IEEE”) standard 802.14 for cable modems incorporated herein by reference. IEEE standards can be found on the World Wide Web at the Universal Resource Locator (“URL”) “www.ieee.org.” However, other RF interfaces 40 could also be used and the present invention is not limited to IEEE 802.14 (e.g., RF interfaces from Multimedia Cable Network Systems (“MCNS”) and others could also be used).
[0052] Above RF interface 40 in a data-link layer 42 is a Medium Access Control (“MAC”) layer 44. As is known in the art, MAC layer 44 controls access to a transmission medium via physical layer 38. For more information on MAC layer protocol 44 see IEEE 802.14 for cable modems. However, other MAC layer protocols 44 could also be used and the present invention is not limited to IEEE 802.14 MAC layer protocols (e.g., MCNS MAC layer protocols and others could also be used).
[0053] Above MAC layer 44 is an optional link security protocol stack 46. Link security protocol stack 46 prevents unauthorized users from making a data connection from cable network 14. RF interface 40 and MAC layer 44 can also be used for an upstream connection if data-over-cable system 10 is used without telephony return.
[0054] For upstream data transmission with telephony return, CM 16 is connected to PSTN 22 in physical layer 38 via modem interface 48. The International Telecommunications Union-Telecommunication Standardization Sector (“ITU-T”, formerly known as the CCITT) defines standards for communication devices identified by “V.xx” series where “xx” is an identifying number. ITU-T standards can be found on the World Wide Web at the URL “www.itu.ch.”
[0055] In one embodiment of the present invention, ITU-T V.34 is used as modem interface 48. As is known in the art, ITU-T V.34 is commonly used in the data link layer for modem communications and currently allows data rates as high as 33,600 bits-per-second (“bps”). For more information see the ITU-T V.34 standard. However, other modem interfaces or other telephony interfaces could also be used.
[0056] Above modem interface 48 in data link layer 42 is Point-to-Point Protocol (“PPP”) layer 50, hereinafter PPP 50. As is known in the art, PPP is used to encapsulate network layer datagrams over a serial communications link. For more information on PPP see Internet Engineering Task Force (“IETF”) Request for Comments (“RFC”), RFC-1661, RFC-1662 and RFC-1663 incorporated herein by reference. Information for IETF RFCs can be found on the World Wide Web at URLs “ds.internic.net” or “www.ietf.org.”
[0057] Above both the downstream and upstream protocol layers in a network layer 52 is an Internet Protocol (“IP”) layer 54. IP layer 54, hereinafter IP 54, roughly corresponds to OSI layer 3, the network layer, but is typically not defined as part of the OSI model. As is known in the art, IP 54 is a routing protocol designed to route traffic within a network or between networks. For more information on IP 54 see RFC-791 incorporated herein by reference.
[0058] Internet Control Message Protocol (“ICMP”) layer 56 is used for network management. The main functions of ICMP layer 56, hereinafter ICMP 56, include error reporting, reachability testing (e.g., “pinging”) congestion control, route-change notification, performance, subnet addressing and others. Since IP 54 is an unacknowledged protocol, datagrams may be discarded and ICMP 56 is used for error reporting. For more information on ICMP 56 see RFC-971 incorporated herein by reference.
[0059] Above IP 54 and ICMP 56 is a transport layer 58 with User Datagram Protocol layer 60 (“UDP”). UDP layer 60, hereinafter UDP 60, roughly corresponds to OSI layer 4, the transport layer, but is typically not defined as part of the OSI model. As is known in the art, UDP 60 provides a connectionless mode of communications with datagrams. For more information on UDP 60 see RFC-768 incorporated herein by reference.
[0060] Above the network layer are a Simple Network Management Protocol (“SNMP”) layer 62, Trivial File Protocol (“TFTP”) layer 64, Dynamic Host Configuration Protocol (“DHCP”) layer 66 and a UDP manager 68. SNMP layer 62 is used to support network management functions. For more information on SNMP layer 62 see RFC-1157 incorporated herein by reference. TFTP layer 64 is a file transfer protocol used to download files and configuration information. For more information on TFTP layer 64 see RFC-1350 incorporated herein by reference. DHCP layer 66 is a protocol for passing configuration information to hosts on an IP 54 network. For more information on DHCP layer 66 see RFC-1541 and RFC-2131 incorporated herein by reference. UDP manager 68 distinguishes and routes packets to an appropriate service (e.g., a virtual tunnel). More or few protocol layers could also be used with data-over-cable system 10.
[0061] CM 16 supports transmission and reception of IP 54 datagrams as specified by RFC-791. CMTS 12 and TRAC 24 may perform filtering of IP 54 datagrams. CM 16 is configurable for IP 54 datagram filtering to restrict CM 16 and CPE 18 to the use of only their assigned IP 54 addresses. CM 16 is configurable for IP 54 datagram UDP 60 port filtering (i.e., deep filtering).
[0062] CM 16 forwards IP 54 datagrams destined to an IP 54 unicast address across cable network 14 or PSTN 22. Some routers have security features intended to filter out invalid users who alter or masquerade packets as if sent from a valid user. Since routing policy is under the control of network operators, such filtering is a vendor specific implementation. For example, dedicated interfaces (i.e., Frame Relay) may exist between TRAC 24 and CMTS 12 which preclude filtering, or various forms of virtual tunneling and reverse virtual tunneling could be used to virtually source upstream packets from CM 16. For more information on virtual tunneling see Level 2 Tunneling Protocol (“L2TP”) or Point-to-Point Tunneling Protocol (“PPTP”) in IETF draft documents incorporated herein by reference by Kory Hamzeh, et. al (IETF draft documents are precursors to IETF RFCs and are works in progress).
[0063] CM 16 also forwards IP 54 datagrams destined to an IP 54 multicast address across cable network 14 or PSTN 22. CM 16 is configurable to keep IP 54 multicast routing tables and to use group membership protocols. CM 16 is also capable of IP 54 tunneling upstream through the telephony path. A CM 16 that wants to send a multicast packet across a virtual tunnel will prepend another IP 54 header, set the destination address in the new header to be the unicast address of CMTS 12 at the other end of the tunnel, and set the IP 54 protocol field to be four, which means the next protocol is IP 54.
[0064] CMTS 12 at the other end of the virtual tunnel receives the packet, strips off the encapsulating IP 54 header, and forwards the packet as appropriate. A broadcast IP 54 capability is dependent upon the configuration of the direct linkage, if any, between TRAC 24 and CMTS 12. CMTS 12, CM 16, and TRAC 24 are capable of routing IP 54 datagrams destined to an IP 54 broadcast address which is across cable network 14 or PSTN 22 if so configured. CM 16 is configurable for IP 54 broadcast datagram filtering.
[0065] An operating environment for CM 16 of the present invention includes a processing system with at least one high speed Central Processing Unit (“CPU”) and a memory system. In accordance with the practices of persons skilled in the art of computer programming, the present invention is described below with reference to acts and symbolic representations of operations that are performed by the processing system, unless indicated otherwise. Such acts and operations are sometimes referred to as being “computer-executed”, or “CPU executed.”
[0066] It will be appreciated that the acts and symbolically represented operations include the manipulation of electrical signals by the CPU. As electrical system with data bits causes a resulting transformation or reduction of the electrical signal representation, and the maintenance of data bits at memory locations in the memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to the data bits.
[0067] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, organic disks, and any other volatile or non-volatile mass storage system readable by the CPU. The computer readable medium includes cooperating or interconnected computer readable media, which exist exclusively on the processing system or is distributed among multiple interconnected processing systems that may be local or remote to the processing system.
[0068] Initialization of a Cable Modem With Telephony Return
[0069] When CM 16 is initially powered on, if telephony return is being used, CM 16 will receive a Telephony Channel Descriptor (“TCD”) from CMTS 12 that is used to provide dialing and access instructions on downstream channels via cable network 14. Information in the TCD is used by CM 16 to connect to TRAC 24. The TCD is transmitted as a MAC management message with a management type value of TRI_TCD at a periodic interval (e.g., every 2 seconds). To provide for flexibility, the TCD message parameters are encoded in a Type/Length/Value (“TLV”) form. However, other encoding techniques could also be used. FIG. 3 is a block diagram illustrating a TCD message structure 70 with MAC 44 management header 72 and Service Provider Descriptor(s) (“SPD”) 74 encoded in TLV format. SPDs 74 are compound TLV encodings that define telephony physical-layer characteristics that are used by CM 16 to initiate a telephone call. SPD 74 is a TLV-encoded data structure that contains sets of dialing and access parameters for CM 16 with telephony return. SPD 74 is contained within TCD message 70. There may be multiple SPD 74 encodings within a single TCD message 70. There is at least one SPD 74 in TCD message 70. SPD 74 parameters are encoded as SPD-TLV tuples. SPD 74 contains the parameters shown in Table 1 and may contain optional vendor specific parameters. However, more or fewer parameters could also be used in SPD 74.
| TABLE 1 | |
|---|---|
| SPD 74 Parameter | Description |
| Factory Default Flag | Boolean value, if TRUE(1), indicates a |
| SPD which should be used by CM 16. | |
| Service Provider Name | This parameter includes the name of a |
| service provider. Format is standard | |
| ASCII string composed of numbers and | |
| letters. | |
| Telephone Numbers | These parameters contain telephone |
| numbers that CM 16 uses to initiate a | |
| telephony modem link during a login | |
| process. Connections are attempted in | |
| ascending numeric order (i.e., Phone | |
| Number 1, Phone Number 2 . . .). The SPD | |
| contains a valid telephony dial string as | |
| the primary dial string (Phone Number 1), | |
| secondary dial-strings are optional. | |
| Format is ASCII string(s) composed of: | |
| any sequence of numbers, pound “#” and | |
| star “*” keys and comma character “,” | |
| used to indicate a two second pause in | |
| dialing. | |
| Connection Threshold | The number of sequential connection |
| failures before indicating connection | |
| failure. A dial attempt that does not result | |
| in an answer and connection after no | |
| more than ten rings is considered a | |
| failure. The default value is one. | |
| Login User Name | This contains a user name CM 16 will use |
| an authentication protocol over the | |
| telephone link during the initialization | |
| procedure. Format is a monolithic | |
| sequence of alphanumeric characters in | |
| an ASCII string composed of numbers | |
| and letters. | |
| Login Password | This contains a password that CM 16 will |
| use during authentication over a | |
| telephone link during the initialization | |
| procedure. Format is a monolithic | |
| sequence of alphanumeric characters in | |
| an ASCII string composed of numbers | |
| and letters. | |
| DHCP Authenticate | Boolean value, reserved to indicate that |
| CM 16 uses a specific indicated DHCP 66 | |
| Server (see next parameter) for a DHCP | |
| 66 Client and BOOTP Relay Process | |
| when TRUE (one). The default is FALSE | |
| (zero) which allows any DHCP 66 Server. | |
| DHCP Server | IP 54 address value of a DHCP 66 Server |
| CM 16 uses for DHCP 66 Client and | |
| BOOTP Relay Process. If this attribute is | |
| present and DHCP 66 Authenticate | |
| attribute is TRUE(1). The default value is | |
| integer zero. | |
| RADIUS Realm | The realm name is a string that defines a |
| RADIUS server domain. Format is a | |
| monolithic sequence of alphanumeric | |
| characters in an ACSII string composed | |
| of numbers and letters. | |
| PPP Authentication | This parameter instructs the telephone |
| modem which authentication procedure to | |
| perform over the telephone link. | |
| Demand Dial Timer | This parameter indicates time (in |
| seconds) of inactive networking time that | |
| will be allowed to elapse before hanging | |
| up a telephone connection at CM 16. If | |
| this optional parameter is not present, or | |
| set to zero, then the demand dial feature | |
| is not activated. The default value is zero. | |
| Vendor Specific Extensions | Optional vendor specific extensions. |
[0070] A Termination System Information (“TSI”) message is transmitted by CMTS 12 at periodic intervals (e.g., every 2 seconds) to report CMTS 12 information to CM 16 whether or not telephony return is used. The TSI message is transmitted as a MAC 44 management message. The TSI provides a CMTS 12 boot record in a downstream channel to CM 16 via cable network 14. Information in the TSI is used by CM 16 to obtain information about the status of CMTS 12. The TSI message has a MAC 44 management type value of TRI_TSI.
[0071] FIG. 4 is a block diagram of a TSI message structure 76. TSI message structure 76 includes a MAC 44 management header 78, a downstream channel IP address 80, a registration IP address 82, a CMTS 12 boot time 84, a downstream channel identifier 86, an epoch time 88 and vendor specific TLV encoded data 90.
[0072] A description of the fields of TSI message 76 are shown in Table 2. However, more or fewer fields could also be used in TSI message 76.
| TABLE 2 | |
|---|---|
| TSI 76 Parameter | Description |
| Downstream Channel | This field contains an IP 54 address of |
| IP Address 80 | CMTS 12 available on the downstream |
| channel this message arrived on. | |
| Registration IP Address 82 | This field contains an IP 54 address |
| CM 16 sends its registration request | |
| messages to. This address MAY be | |
| the same as the Downstream Channel | |
| IP 54 address. | |
| CMTS Boot Time 84 | Specifies an absolute-time of a CMTS |
| 12 recorded epoch. The clock setting | |
| for this epoch uses the current clock | |
| time with an unspecified accuracy. | |
| Time is represented as a 32 bit binary | |
| number. | |
| Downstream Channel ID 86 | A downstream channel on which this |
| message has been transmitted. This | |
| identifier is arbitrarily chosen by CMTS | |
| 12 and is unique within the MAC 44 | |
| layer. | |
| Epoch 88 | An integer value that is incremented |
| each time CMTS 12 is either re- | |
| initialized or performs address or | |
| routing table flush. | |
| Vendor Specific Extensions 90 | Optional vendor extensions may be |
| added as TLV encoded data. | |
[0073] After receiving TCD 70 message and TSI message 76, CM 16 continues to establish access to data network 28 (and resources on the network) by first dialing into TRAC 24 and establishing a telephony PPP 50 session. Upon the completion of a successful PPP 50 connection, CM 16 performs PPP Link Control Protocol (“LCP”) negotiation with TRAC 24. Once LCP negotiation is complete, CM 16 requests Internet Protocol Control Protocol (“IPCP”) address negotiation. For more information on IPCP see RFC-1332 incorporated herein by reference. During IPCP negotiation, CM 16 negotiates an IP 54 address with TRAC 24 for sending IP 54 data packet responses back to data network 28 via TRAC 24.
[0074] When CM 16 has established an IP 54 link to TRAC 24, it begins “upstream” communications to CMTS 12 via DHCP layer 66 to complete a virtual data connection by attempting to discover network host interfaces available on CMTS 12 (e.g., IP 54 host interfaces for a virtual IP 54 connection). The virtual data connection allows CM 16 to receive data from data network 28 via CMTS 12 and cable network 14, and send return data to data network 28 via TRAC 24 and PSTN 22. CM 16 must first determine an address of a host interface (e.g., an IP 54 interface) available on CMTS 12 that can be used by data network 28 to send data to CM 16. However, CM 16 has only a downstream connection from CMTS 12 and has to obtain a connection address to data network 28 using an upstream connection to TRAC 24.
[0075] Addressing Network Host Interfaces in the Data-over-cable System via the Cable Modem
[0076] FIG. 5 is a flow diagram illustrating a method 92 for addressing network host interfaces in a data-over-cable system with telephony return via a cable modem. Method 92 allows a cable modem to establish a virtual data connection to a data network. In method 92, multiple network devices are connected to a first network with a downstream connection of a first connection type, and connected to a second network with an upstream connection of a second connection type. The first and second networks are connected to a third network with a third connection type.
[0077] At step 94, a selection input is received on a first network device from the first network over the downstream connection. The selection input includes a first connection address allowing the first network device to communicate with the first network via upstream connection to the second network. At step 96, a first message of a first type for a first protocol is created on the first network device having the first connection address from the selection input in a first message field. The first message is used to request a network host interface address on the first network. The first connection address allows the first network device to have the first message with the first message type forwarded to network host interfaces available on the first network via the upstream connection to the second network.
[0078] At step 98, the first network device sends the first message over the upstream connection to the second network. The second network uses the first address field in the first message to forward the first message to one or more network host interfaces available on first network at step 100. Network host interfaces available on the first network that can provide the services requested in first message send a second message with a second message type with a second connection address in a second message field to the first network at step 102. The second connection address allows the first network device to receive data packets from the third network via a network host interface available on the first network. The first network forwards one or more second messages on the downstream connection to the first network device at step 104.
[0079] The first network device selects a second connection address from one of the second messages from one of the one or more network host interfaces available on the first network at step 106 and establishes a virtual connection from the third network to the first network device using the second connection address for the selected network host interface.
[0080] The virtual connection includes receiving data on the first network host interface on the first network from the third network and sending the data over the downstream connection to the first network device. The first network device sends data responses back to the third network over the upstream connection to the second network, which forwards the data to the appropriate destination on the third network.
[0081] In one embodiment of the present invention, the data-over-cable system is data-over-cable system 10, the first network device is CM 16, the first network is cable television network 14, the downstream connection is a cable television connection. The second network is PSTN 22, the upstream connection is a telephony connection, the third network is data network 28 (e.g., the Internet or an intranet) and the third type of connection is an IP 54 connection. The first and second connection addresses are IP 54 addresses. However, the present invention is not limited to the network components and addresses described. Method 92 allows CM 16 to determine an IP 54 network host interface address available on CMTS 12 to receive IP 54 data packets from data network 28, thereby establishing a virtual IP 54 connection with data network 28.
[0082] After addressing network host interfaces using method 92, an exemplary data path through cable system 10 is illustrated in Table 3. However other data paths could also be used and the present invention is not limited to the data paths shown in Table 3. For example, CM 16 may send data upstream back through cable network 14 (e.g., CM 16 to cable network 14 to CMTS 12) and not use PSTN 22 and the telephony return upstream path.
| TABLE 3 | |
|---|---|
| 1. | An IP 54 datagram from data network 28 destined for CM 16 arrives |
| on CMTS-NSI 32 and enters CMTS 12. | |
| 2. | CMTS 12 encodes the IP 54 datagram in a cable data frame, |
| passes it to MAC 44 and transmits it “downstream” to RF interface | |
| 40 on CM 16 via cable network 14. | |
| 3. | CM 16 recognizes the encoded IP 54 datagram in MAC layer 44 |
| received via RF interface 40. | |
| 4. | CM 16 responds to the cable data frame and encapsulates a response |
| IP 54 datagram in a PPP 50 frame and transmits it “upstream” with | |
| modem interface 48 via PSTN 22 to TRAC 24. | |
| 5. | TRAC 24 decodes the IP 54 datagram and forwards it via |
| TRAC-NSI 30 to a destination on data network 28. | |
[0083] Dynamic Network Host Configuration on Data-over-cable System
[0084] As was illustrated in FIG. 2, CM 16 includes a Dynamic Host Configuration Protocol (“DHCP”) layer 66, hereinafter DHCP 66. DHCP 66 is used to provide configuration parameters to hosts on a network (e.g., an IP 54 network). DHCP 66 consists of two components: a protocol for delivering host-specific configuration parameters from a DHCP 66 server to a host and a mechanism for allocation of network host addresses to hosts. DHCP 66 is built on a client-server model, where designated DHCP 66 servers allocate network host addresses and deliver configuration parameters to dynamically configured network host clients.
[0085] FIG. 6 is a block diagram illustrating a DHCP 66 message structure 108. The format of DHCP 66 messages is based on the format of BOOTstrap Protocol (“BOOTP”) messages described in RFC-951 and RFC-1542 incorporated herein by reference. From a network host client's point of view, DHCP 66 is an extension of the BOOTP mechanism. This behavior allows existing BOOTP clients to interoperate with DHCP 66 servers without requiring any change to network host the clients' BOOTP initialization software. DHCP 66 provides persistent storage of network parameters for network host clients.
[0086] To capture BOOTP relay agent behavior described as part of the BOOTP specification and to allow interoperability of existing BOOTP clients with DHCP 66 servers, DHCP 66 uses a BOOTP message format. Using BOOTP relaying agents eliminates the necessity of having a DHCP 66 server on each physical network segment.
[0087] DHCP 66 message structure 108 includes an operation code field 110 (“op”), a hardware address type field 112 (“htype”), a hardware address length field 114 (“hlen”), a number of hops field 116 (“hops”), a transaction identifier field 118 (“xid”), a seconds elapsed time field 120 (“secs”), a flags field 122 (“flags”), a client IP address field 124 (“ciaddr”), a your IP address field 126 (“yiaddr”), a server IP address field 128 (“siaddr”), a gateway/relay agent IP address field 130 (“giaddr”), a client hardware address field 132 (“chaddr”), an optional server name field 134 (“sname”), a boot file name 136 (“file”) and an optional parameters field 138 (“options”). Descriptions for DHCP 66 message 108 fields are shown in Table 4.
| TABLE 4 | |
|---|---|
| DCHP 66 | |
| Parameter | Description |
| OP 110 | Message op code/message type. |
| 1 BOOTREQUEST, 2 = BOOTREPLY. | |
| HTYPE 112 | Hardware address type |
| (e.g., ‘1’ = 10 Mps Ethernet). | |
| HLEN 114 | Hardware address length |
| (e.g., ‘6’ for 10 Mbps Ethernet). | |
| HOPS 116 | Client sets to zero, optionally used by |
| relay-agents when booting via a relay-agent. | |
| XID 118 | Transaction ID, a random number |
| chosen by the client, used by the client | |
| and server to associate messages and | |
| responses between a client and a server. | |
| SECS 120 | Filled in by client, seconds elapsed |
| since client started trying to boot. | |
| FLAGS 122 | Flags including a BROADCAST bit. |
| CIADDR 124 | Client IP address; filled in by client in |
| DHCPREQUEST if verifying previously | |
| allocated configuration parameters. | |
| YIADDR 126 | ‘Your’(client) IP address. |
| SIADDR 128 | IP 54 address of next server to use in bootstrap; |
| returned in DHCPOFFER, DHCPACK and DHCPNAK | |
| by server. | |
| GIADDR 130 | Gateway relay agent IP 54 address, used in booting |
| via a relay-agent. | |
| CHADDR 132 | Client hardware address |
| (e.g., MAC layer 44 address). | |
| SNAME 134 | Optional server host name, null terminated string. |
| FILE 136 | Boot file name, terminated by a null string. |
| OPTIONS 138 | Optional parameters. |
[0088] The DHCP 66 message structure shown in FIG. 6 is used to discover IP 54 and other network host interfaces in data-over-cable system 10. A network host client (e.g., CM 16) uses DHCP 66 to acquire or verify an IP 54 address and network parameters whenever the network parameters may have changed. Table 5 illustrates a typical use of the DHCP 66 protocol to discover a network host interface from a network host client.
| TABLE 5 | |
|---|---|
| 1. | A network host client broadcasts a DHCP 66 discover message on its |
| local physical subnet. The DHCP 66 discover message may include | |
| options that suggest values for a network host interface address. | |
| BOOTP relay agents may pass the message on to DHCP 66 servers | |
| not on the same physical subnet. | |
| 2. | DHCP servers may respond with a DHCPOFFER message that |
| includes an available network address in the ‘yiaddr’ field | |
| (and other configuration parameters in DHCP 66 options) | |
| from a network host interface. DHCP 66 servers unicasts the | |
| DHCPOFFER message to the network host client (using the | |
| DHCP/BOOTP relay agent if necessary) if possible, or may | |
| broadcast the message to a broadcast address | |
| (preferably 255.255.255.255) on the client's subnet. | |
| 3. | The network host client receives one or more DHCPOFFER |
| messages from one or more DHCP 66 servers. The network host | |
| client may choose to wait for multiple responses. | |
| 4. | The network host client chooses one DHCP 66 server with an |
| associated network host interface from which to request | |
| configuration parameters, based on the configuration parameters | |
| offered in the DHCPOFFER messages. | |
[0089] Discovering Network Host Interfaces in the Data-over-cable System
[0090] The DHCP discovery process illustrated in table 5 will not work in data-over-cable system 10. CM 16 has only a downstream connection from CMTS 12, which includes DHCP 66 servers, associated with network host interfaces available on CMTS 12. In a preferred embodiment of the present invention, CM 16 discovers network host interfaces via TRAC 24 and PSTN 22 on an upstream connection.
[0091] The DHCP 66 addressing process shown in Table 5 was not originally intended to discover network host interfaces in data-over-cable system 10. CMTS 12 has DHCP 66 servers associated with network host interfaces (e.g., IP interfaces), but CM 16 only has as downstream connection from CMTS 12. CM 16 has an upstream connection to TRAC 24, which has a DHCP 66 layer. However, TRAC 24 does not have DHCP 66 servers, or direct access to network host interfaces on CMTS 12. FIGS. 7A and 7B are a flow diagram illustrating a method 140 for discovering network host interfaces in data-over-cable system 10. When CM 16 has established an IP 54 link to TRAC 24, it begins communications with CMTS 12 via DHCP 66 to complete a virtual IP 54 connection with data network 28. However, to discover what IP 54 host interfaces might be available on CMTS 12, CM 16 has to communicate with CMTS 12 via PSTN 22 and TRAC 24 since CM 16 only has a “downstream” cable channel from CMTS 12.
[0092] At step 142 in FIG. 7A, after receiving a TSI message 76 from CMTS 12 on a downstream connection, CM 16 generates a DHCP discover (“DHCPDISCOVER”) message and sends it upstream via PSTN 22 to TRAC 22 to discover what IP 54 interfaces are available on CMTS 12. The fields of the DHCP discover message are set as illustrated in Table 6. However, other field settings may also be used.
| TABLE 6 | |
|---|---|
| DHCP 66 | |
| Parameter | Description |
| OP 110 | Set to BOOTREQUEST. |
| HTYPE 112 | Set to network type |
| (e.g., one for 10 Mbps Ethernet). | |
| HLEN 114 | Set to network length |
| (e.g., six for 10 Mbps Ethernet) | |
| HOPS 116 | Set to zero. |
| FLAGS 122 | Set BROADCAST bit to zero. |
| CIADDR 124 | If CM 16 has previously been assigned an IP 54 address, |
| the IP 54 address is placed in this field. | |
| If CM 16 has previously been assigned an IP 54 address | |
| by DHCP 66, and also has been assigned an address via | |
| IPCP, CM 16 places the DHCP 66 IP 54 address in this | |
| field. | |
| GIADDR 130 | CM 16 places the Downstream Channel IP 54 address |
| 80 of CMTS 12 obtained in TSI message 76 on a | |
| cable downstream channel in this field. | |
| CHADDR 132 | CM 16 places its 48-bit MAC 44 LAN address |
| in this field. | |
[0093] The DHCPDISCOVER message is used to “discover” the existence of one or more IP 54 host interfaces available on CMTS 12. DHCP 66 giaddr-field 130 (FIG. 6) includes the downstream channel IP address 80 of CMTS 12 obtained in TSI message 76 (e.g., the first message field from step 96 of method 92). Using the downstream channel IP address 80 of CMTS 12 obtained in TSI message 76 allows the DHCPDISCOVER message to be forwarded by TRAC 24 to DHCP 66 servers (i.e., protocol servers) associated with network host interfaces available on CMTS 12. If DHCP 66 giaddr-field 130 (FIG. 6) in a DHCP message from a DHCP 66 client is non-zero, the DHCP 66 server sends any return messages to a DHCP 66 server port on a DHCP 66 relaying agent (e.g., CMTS 12) whose address appears in DHCP 66 giaddr-field 130.
[0094] In a typical DHCP 66 discovery process the DHCP 66 giaddr-field 130 is set to zero. In a typical DHCP 66 discovery process the DHCP 66 giaddr-field 130 is set to zero. However, in a preferred embodiment of the present invention, the giaddr-field 130 contains the IP address 80 of CMTS 12. If DHCP 66 giaddr-field 130 is zero, the DHCP 66 client is on the same subnet as the DHCP 66 server, and the DHCP 66 server sends any return messages to either the DHCP 66 client's network address, if that address was supplied in DHCP 66 ciaddr-field 124 (FIG. 6), or to a client's hardware address specified in DHCP 66 chaddr-field 132 (FIG. 6) or to a local subnet broadcast address (e.g., 255.255.255.255).
[0095] At step 144, a DHCP 66 layer on TRAC 24 broadcasts the DHCPDISCOVER message on its local network leaving DHCP 66 giaddr-field 130 intact since it already contains a non-zero value. TRAC's 24 local network includes connections to one or more DHCP 66 proxies (i.e., network host interface proxies). The DHCP 66 proxies accept DHCP 66 messages originally from CM 16 destined for DHCP 66 servers connected to network host interfaces available on CMTS 12 since TRAC 24 has no direct access to DCHP 66 servers associated with network host interfaces available on CMTS 12. DHCP 66 proxies are not used in a typical DHCP 66 discovery process.
[0096] One or more DHCP 66 proxies on TRAC's 24 local network recognizes the DHCPDISCOVER message and forwards it to one or more DHCP 66 servers associated with network host interfaces (e.g., IP 54 interfaces) available on CMTS 12 at step 146. Since DHCP 66 giaddr-field 130 (FIG. 6) in the DHCPDISCOVER message sent by CM 16 is already non-zero (i.e., contains the downstream IP address of CMTS 12), the DHCP 66 proxies also leave DHCP 66 giaddr-field 130 intact.
[0097] One or more DHCP 66 servers for network host interfaces (e.g., IP 54 interfaces) available on CMTS 12 receive the DHCPDISCOVER message and generate a DHCP 66 offer message (“DHCPOFFER”) at step 148. The DHCP 66 offer message is an offer of configuration parameters sent from network host interfaces to DHCP 66 servers and back to a network host client (e.g., CM 16) in response to a DHCPDISCOVER message. The DHCP 66 offer message is sent with the message fields set as illustrated in Table 7. However, other field settings can also be used. DHCP 66 yiaddr-field 126 (e.g., second message field from step 102 of method 92) contains an IP 54 address for a network host interface available on CMTS 12 and used for receiving data packets from data network 28.
| TABLE 7 | |
|---|---|
| DHCP 66 Parameter | Description |
| FLAGS 122 | BROADCAST bit set to zero. |
| YIADDR 126 | IP 54 address from a network host interface to |
| allow CM 16 to receive data from data network 28 | |
| via a network host interface available on CMTS 12. | |
| SIADDR 128 | An IP 54 address for a TFTP 64 server to |
| download configuration information for an | |
| interface host. | |
| CHADDR 132 | MAC 44 address of CM 16. |
| SNAME 134 | Optional DHCP 66 server identifier with an |
| interface host. | |
| FILE 136 | A TFTP 64 configuration file name for CM 16. |
[0098] DHCP 66 servers send the DHCPOFFER message to the address specified in 66 giaddr-field 130 (i.e., CMTS 12) from the DHCPDISCOVER message if associated network host interfaces (e.g., IP 54 interfaces) can offer the requested service (e.g., IP 54 service) to CM 16. The DHCPDISOVER message DHCP 66 giaddr-field 130 contains a downstream channel IP address 80 of CMTS 12 that was received by CM 16 in TSI message 76. This allows CMTS 12 to receive the DHCPOFFER messages from the DHCP 66 servers and send them to CM 16 via a downstream channel on cable network 14.
[0099] At step 150 in FIG. 7B, CMTS 12 receives one or more DHCPOFFER messages from one or more DHCP 66 servers associated with the network host interfaces (e.g., IP 54 interfaces). CMTS 12 examines DHCP 66 yiaddr-field 126 and DHCP 66 chaddr-field 132 in the DHCPOFFER messages and sends the DHCPOFFER messages to CM 16 via cable network 14. DHCP 66 yiaddr-field 126 contains an IP 54 address for a network host IP 54 interface available on CMTS 12 and used for receiving IP 54 data packets from data network 28. DHCP 66 chaddr-field 132 contains the MAC 44 layer address for CM 16 on a downstream cable channel from CMTS 12 via cable network 14. CMTS 12 knows the location of CM 16 since it sent CM 16 a MAC 44 layer address in one or more initialization messages (e.g., TSI message 76).
[0100] If a BROADCAST bit in flags field 124 is set to one, CMTS 12 sends the DHCPOFFER messages to a broadcast IP 54 address (e.g., 255.255.255.255) instead of the address specified in DHCP 66 yiaddr-field 126. DHCP 66 chaddr-field 132 is still used to determine that MAC 44 layer address. If the BROADCAST bit in DHCP 66 flags field 122 is set, CMTS 12 does not update internal address or routing tables based upon DHCP 66 yiaddr-field 126 and DHCP 66 chaddr-field 132 pair when a broadcast message is sent.
[0101] At step 152, CM 16 receives one or more DHCPOFFER messages from CMTS 12 via cable network 14 on a downstream connection. At step 154, CM 16 selects an offer for IP 54 service from one of the network host interfaces (e.g., an IP interfaces 54) available on CMTS 12 that responded to the DHCPDISOVER message sent at step 142 in FIG. 7A and establishes a virtual IP 54 connection. The selected DHCPOFFER message contains a network host interface address (e.g., IP 54 address) in DHCP 66 yiaddr-field 126 (FIG. 6). A cable modem acknowledges the selected network host interface with DHCP 66 message sequence explained below.
[0102] After selecting and acknowledging a network host interface, CM 16 has discovered an IP 54 interface address available on CMTS 12 for completing a virtual IP 54 connection with data network 28. Acknowledging a network host interface is explained below. The virtual IP 54 connection allows IP 54 data from data network 28 to be sent to CMTS 12 which forwards the IP 54 packets to CM 16 on a downstream channel via cable network 14. CM 16 sends response IP 54 packets back to data network 28 via PSTN 22 and TRAC 24.
[0103] FIG. 8 is a block diagram illustrating a data-over-cable system 156 for the method illustrated in FIGS. 7A and 7B. Data-over-cable system 156 includes DHCP 66 proxies 158, DHCP 66 servers 160 and associated Network Host Interfaces 162 available on CMTS 12. Multiple DHCP 66 proxies 158, DHCP 66 servers 160 and network host interfaces 162 are illustrated as single boxes in FIG. 8. FIG. 8 also illustrates DHCP 66 proxies 158 separate from TRAC 24. In one embodiment of the present invention, TRAC 24 includes DHCP 66 proxy functionality and no separate DHCP 66 proxies 158 are used. In such an embodiment, TRAC 24 forwards DHCP 66 messages using DHCP 66 giaddr-field 130 to DHCP 66 servers 160 available on CMTS 12. FIG. 9 is a block diagram illustrating a message flow 164 of method 140 (FIGS. 7A and 7B).
[0104] Message flow 164 includes DHCP proxies 158 and DHCP servers 160 illustrated in FIG. 8 Steps 142, 144, 146, 148, 150 and 154 of method 140 (FIGS. 7A and 7B) are illustrated in FIG. 9. In one embodiment of the present invention, DHCP proxies 158 are not separate entities, but are included in TRAC 24. In such an embodiment, DHCP proxy services are provided directly by TRAC 24.
[0105] Resolving Addresses For Network Host Interfaces
[0106] Since CM 16 receives multiple DHCPOFFER messages (Step 152FIG. 7B) CM 16 resolves and acknowledges one offer from a selected network host interface. FIGS. 10A and 10B are a flow diagram illustrating a method 166 for resolving and acknowledging host addresses in a data-over-cable system. Method 166 includes a first network device that is connected to a first network with a downstream connection of a first connection type, and connected to a second network with an upstream connection of a second connection type. The first and second networks are connected to a third network with a third connection type. In one embodiment of the present invention, the first network device is CM 16, the first network is cable network 14, the second network is PSTN 22 and the third network is data network 28 (e.g., the Internet). The downstream connection is a cable television connection, the upstream connection is a telephony connection, and the third connection is an IP connection.
[0107] Turning to FIG. 10A, one or more first messages are received on the first network device from the first network on the downstream connection at step 168. The one or more first messages are offers from one or more network host interfaces available on the first network to provide the first network device a connection to the third network. The first network device selects one of the network host interfaces using message fields in one of the one or more first messages at step 170. The first network device creates a second message with a second message type to accept the offered services from a selected network host interface at step 172. The second message includes a connection address for the first network in a first message field and an identifier to identify the selected network host interface in a second message field.
[0108] The first network device sends the second message over the upstream connection to the second network at step 174. The second network uses the first message field in the second message to forward the second message to the one or more network host interfaces available on first network at step 176.
[0109] A network host interface available on the first network identified in second message field in the second message from the first network device recognizes an identifier for the network host interface at 178 in FIG. 10B. The selected network host interface sends a third message with a third message type to the first network at step 180. The third message is an acknowledgment for the first network device that the selected network host interface received the second message from the first network device. The first network stores a connection address for the selected network interface in one or more tables on the first network at step 182. The first network will forward data from the third network to the first network device when it is received on the selected network host interface using the connection address in the one or more routing tables. The first network forwards the third message to the first network device on the downstream connection at step 184. The first network device receives the third message at step 186. The first network and the first network device have the necessary addresses for a virtual connection that allows data to be sent from the third network to a network host interface on the first network, and from the first network over the downstream connection to the first network device. Method 166 accomplishes resolving network interface hosts addresses from a cable modem in a data-over-cable with telephony return.
[0110] Method 166 of the present invention is used in data-over-cable system 10 with telephony return. However, the present invention is not limited to data-over-cable system 10 with telephony return and can be used in data-over-cable system 10 without telephony return by using an upstream cable channel instead of an upstream telephony channel.
[0111] FIGS. 11A and 11B are a flow diagram illustrating a method 188 for resolving discovered host addresses in data-over-cable system 10 with telephony return. At step 190 in FIG. 11A, CM 16 receives one or more DHCPOFFER messages from one or more DHCP 66 servers associated with one or more network host interfaces (e.g., at step 168 in method 166). The one or more DHCPOFFER messages include DHCP 66 fields set as illustrated in Table 7 above. However, other field settings could also be used. At step 192, CM 16 selects one of the DHCPOFFER messages (see also, step 170 in method 166). At step 194, CM 16 creates a DHCP 66 request message (“DHCPREQUEST”) message to request the services offered by a network host interface selected at step 192. The fields of the DHCP request message are set as illustrated in Table 8. However, other field settings may also be used.
| TABLE 8 | |
|---|---|
| DHCP 66 | |
| Parameter | Description |
| OP 110 | Set to BOOTREQUEST. |
| HTYPE 112 | Set to network type |
| (e.g., one for 10 Mbps Ethernet). | |
| HLEN 114 | Set to network length |
| (e.g., six for 10 Mbps Ethernet) | |
| HOPS 116 | Set to zero. |
| FLAGS 118 | Set BROADCAST bit to zero. |
| CIADDR 124 | If CM 16 has previously been assigned an IP address, |
| the IP address is placed in this field. | |
| If CM 16 has previously been assigned an IP address | |
| by DHCP 66, and also has been assigned an address | |
| via IPCP, CM 16 places the DHCP 66 IP 54 address in | |
| this field. | |
| YIADDR 126 | IP 54 address sent from the selected network interface |
| host in DCHPOFFER message | |
| GIADDR 130 | CM 16 places the Downstream Channel IP 54 address |
| 80 CMTS 12 obtained in TSI message 76 on a cable | |
| downstream channel in this field. | |
| CHADDR 132 | CM 16 places its 48-bit MAC 44 LAN address in this |
| field. | |
| SNAME 134 | DHCP 66 server identifier for the selected network |
| interface host | |
[0112] The DHCPREQUEST message is used to “request” services from the selected IP 54 host interface available on CMTS 12 using a DHCP 66 server associated with the selected network host interface. DHCP 66 giaddr-field 130 (FIG. 6) includes the downstream channel IP address 80 for CMTS 12 obtained in TSI message 76 (e.g., the first message-field from step 172 of method 166). Putting the downstream channel IP address 80 obtained in TSI message 76 allows the DHCPREQUEST message to be forwarded by TRAC 24 to DCHP 66 servers associated with network host interfaces available on CMTS 12. DHCP 66 giaddr-field 126 contains an identifier (second message field, step 172 in method 166) DHCP 66 sname-field 134 contains a DHCP 66 server identifier associated with the selected network host interface.
[0113] If DHCP 66 giaddr-field 130 in a DHCP message from a DHCP 66 client is non-zero, a DHCP 66 server sends any return messages to a DHCP 66 server port on a DHCP 66 relaying agent (e.g., CMTS 12) whose address appears in DHCP 66 giaddr-field 130. If DHCP 66 giaddr-field 130 is zero, the DHCP 66 client is on the same subnet as the DHCP 66 server, and the DHCP 66 server sends any return messages to either the DHCP 66 client's network address, if that address was supplied in DHCP 66 ciaddr-field 124, or to the client's hardware address specified in DHCP 66 chaddr-field 132 or to the local subnet broadcast address.
[0114] Returning to FIG. 11A at step 196, CM 16 sends the DHCPREQUEST message on the upstream connection to TRAC 24 via PSTN 22. At step 198, a DHCP 66 layer on TRAC 24 broadcasts the DHCPREQUEST message on its local network leaving DHCP 66 giaddr-field 130 intact since it already contains a non-zero value. TRAC's 24 local network includes connections to one or more DHCP 66 proxies. The DHCP 66 proxies accept DHCP 66 messages originally from CM 16 destined for DHCP 66 servers associated with network host interfaces available on CMTS 12. In another embodiment of the present invention, TRAC 24 provides the DHCP 66 proxy functionality, and no separate DHCP 66 proxies are used.
[0115] The one or more DHCP 66 proxies on TRAC's 24 local network message forwards the DHCPOFFER to one or more of the DHCP 66 servers associated with network host interfaces (e.g., IP 54 interfaces) available on CMTS 12 at step 200 in FIG. 11B. Since DHCP 66 giaddr-field 130 in the DHCPDISCOVER message sent by CM 16 is already non-zero (i.e., contains the downstream IP address of CMTS 12), the DHCP 66 proxies leave DHCP 66 giaddr-field 130 intact.
[0116] One or more DHCP 66 servers for the selected network host interfaces (e.g., IP 54 interface) available on CMTS 12 receives the DHCPOFFER message at step 202. A selected DHCP 66 server recognizes a DHCP 66 server identifier in DHCP 66 sname-field 134 or the IP 54 address that was sent in the DCHPOFFER message in the DHCP 66 yiaddr-field 126 from the DHCPREQUST message as being for the selected DHCP 66 server.
[0117] The selected DHCP 66 server associated with network host interface selected by CM 16 in the DHCPREQUEST message creates and sends a DCHP 66 acknowledgment message (“DHCPACK”) to CMTS 12 at step 204. The DHCPACK message is sent with the message fields set as illustrated in Table 9. However, other field settings can also be used. DHCP 66 yiaddr-field again contains the IP 54 address for the selected network host interface available on CMTS 12 for receiving data packets from data network 28.
| TABLE 9 | |
|---|---|
| DHCP 66 Parameter | Description |
| FLAGS 122 | Set a BROADCAST bit to zero. |
| YIADDR 126 | IP 54 address for the selected network host |
| interface to allow CM 16 to receive data from | |
| data network 28. | |
| SIADDR 128 | An IP 54 address for a TFTP 64 server to download |
| configuration information for an interface host. | |
| CHADDR 132 | MAC 44 address of CM 16. |
| SNAME 134 | DHCP 66 server identifier associated with the |
| selected network host interface. | |
| FILE 136 | A configuration file name for an network interface |
| host. | |
[0118] The selected DHCP 66 server sends the DHCACK message to the address specified in DHCP 66 giaddr-field 130 from the DHCPREQUEST message to CM 16 to verify the selected network host interface (e.g., IP 54 interface) will offer the requested service (e.g., IP 54 service).
[0119] At step 206, CMTS 12 receives the DHCPACK message from the selected DHCP 66 server associated with the selected network host interface IP 54 address(e.g., IP 54 interface). CMTS 12 examines DHCP 66 yiaddr-field 126 and DHCP 66 chaddr-field 132 in the DHCPACK message. DHCP 66 yiaddr-field 126 contains an IP 54 address for a network host IP 54 interface available on CMTS 12 and used for receiving IP 54 data packets from data network 28 for CM 16. DHCP 66 chaddr-field 132 contains the MAC 44 layer address for CM 16 on a downstream cable channel from CMTS 12 via cable network 14.
[0120] CMTS 12 updates an Address Resolution Protocol (“ARP”) table and other routing tables on CMTS 12 to reflect the addresses in DHCP 66 yiaddr-field 126 and DHCP 66 chaddr-field 132 at step 208. As is known in the art, ARP allows a gateway such as CMTS 12 to forward any datagrams from a data network such as data network 28 it receives for hosts such as CM 16. ARP is defined in RFC-826, incorporated herein by reference. CMTS 12 stores a pair of network address values in the ARP table, the IP 54 address of the selected network host interface from DHCP 66 yiaddr-field 126 and a Network Point of Attachment (“NPA”) address. In a preferred embodiment of the present invention, The NPA address is a MAC 44 layer address for CM 16 via a downstream cable channel. The IP/NPA address pair are stored in local routing tables with the IP/NPA addresses of hosts (e.g., CMs 16) that are attached to cable network 14.
[0121] At step 210, CMTS 12 sends the DHCPACK message to CM 16 via cable network 14. At step 212, CM 16 receives the DHCPACK message, and along with CMTS 12 has addresses for a virtual connection between data network 28 and CM 16. When data packets arrive on the IP 54 address for the selected host interface they are sent to CMTS 12 and CMTS 12 forwards them using a NPA (i.e., MAC 44 address) from the routing tables on a downstream channel via cable network 14 to CM 16.
[0122] If a BROADCAST bit in flags field 124 is set to one in the DHCPACK, CMTS 12 sends the DHCPACK messages to a broadcast IP 54 address (e.g., 255.255.255.255). DHCP 66 chaddr-field 132 is still used to determine that MAC layer address. If the BROADCAST bit in flags field 122 is set, CMTS 12 does not update the ARP table or offer routing tables based upon DHCP 66 yiaddr-field 126 and DHCP 66 chaddr-field 132 pair when a broadcast message is sent.
[0123] FIG. 12 is a block diagram illustrating the message flow 214 of the method 188 illustrated in FIGS. 11A and 11B. Message flow 214 includes DHCP proxies 158 and DHCP servers 160 illustrated in FIG. 8. Method steps 194, 196, 198, 204, 208, 210 and 212 of method 188 (FIGS. 11A and 11B) are illustrated in FIG. 12. In one embodiment of the present invention, DHCP proxies 158 are not separate entities, but are included in TRAC 24. In such an embodiment, DHCP proxy services are provided directly by TRAC 24.
[0124] After method 188, CMTS 12 has a valid IP/MAC address pair in one or more address routing tables including an ARP table to forward IP 54 data packets from data network 28 to CM 16, thereby creating a virtual IP 54 data path to/from CM 16 as was illustrated in method 92 (FIG. 5) and Table 3. CM 16 has necessary parameters to proceed to the next phase of initialization, a download of a configuration file via TFTP 64. Once CM 16 has received the configuration file and has been initialized, it registers with CMTS 12 and is ready to receive data from data network 14.
[0125] In the event that CM 16 is not compatible with the configuration of the network host interface received in the DHCPACK message, CM 16 may generate a DHCP 66 decline message (“DHCPDECLINE”) and transmit it to TRAC 24 via PSTN 22. A DHCP 66 layer in TRAC 24 forwards the DHCPDECLINE message to CMTS 12. Upon seeing a DHCPDECLINE message, CMTS 12 flushes its ARP tables and routing tables to remove the now invalid IP/MAC pairing. If an IP 54 address for a network host interface is returned that is different from the IP 54 address sent by CM 16 in the DCHCPREQUEST message, CM 16 uses the IP 54 address it receives in the DHCPACK message as the IP 54 address of the selected network host interface for receiving data from data network 28.
[0126] The present invention is described with respect to, but is not limited to a data-over-cable-system with telephony return. Method 188 can also be used with a cable modem that has a two-way connection (i.e., upstream and downstream) to cable network 14 and CMTS 12. In a data-over-cable-system without telephony return, CM 16 would broadcast the DHCPREQUEST message to one or more DHCP 66 servers associated with one or more network host interfaces available on CMTS 12 using an upstream connection on data network 14 including the IP 54 address of CMTS 12 in DHCP 66 giaddr-field 130. Method 188 accomplishes resolving addresses for network interface hosts from a cable modem in a data-over-cable with or without telephony return, and without extensions to the existing DHCP protocol.
[0127] CPE Initialization in a Data-over-cable System
[0128] CPE 18 also uses DHCP 66 to generate requests to obtain IP 54 addresses to allow CPE 18 to also receive data from data network 28 via CM 16. In a preferred embodiment of the present invention, CM 16 functions as a standard BOOTP relay agent/DHCP Proxy 158 to facilitate CPE's 18 access to DHCP 66 server 160. FIGS. 13A and 13B are a flow diagram illustrating a method 216 for obtaining addresses for customer premise equipment. CM 16 and CMTS 12 use information from method 214 to construct IP 54 routing and ARP table entries for network host interfaces 162 providing data to CMCI 20 and to CPE 18.
[0129] Method 216 in FIGS. 13A and 13B includes a data-over-cable system with telephony return and first network device with a second network device for connecting the first network device to a first network with a downstream connection of a first connection type, and for connecting to a second network with an upstream connection of a second connection type. The first and second networks are connected to a third network with a third connection type.
[0130] In one embodiment of the present invention, data-over-cable system with telephony return is data-over-cable system 10 with the first network device CPE 18 and the second network device CM 16. The first network is cable television network 14, the downstream connection is a cable television connection, the second network is PSTN 22, the upstream connection is a telephony connection, the third network is data network 28 (e.g., the Internet or an intranet) and the third type of connection is an IP 54 connection. However, the present invention is not limited to the network components described and other network components may also be used. Method 216 allows CPE 18 to determine an IP 54 network host interface address available on CMTS 12 to receive IP 54 data packets from data network 54, thereby establishing a virtual IP 54 connection with data network 28 via CM 16.
[0131] Returning to FIG. 13A at step 218, a first message of a first type (e.g., a DHCP 66 discover message) with a first message field for a first connection is created on the first network device. The first message is used to discover a network host interface address on the first network to allow a virtual connection to the third network.
[0132] At step 220, the first network device sends the first message to the second network device. The second network device checks the first message field at step 222. If the first message field is zero, the second network device puts its own connection address into the first message field at step 224. The second network device connection address allows the messages from network host interfaces on the first network to return messages to the second network device attached to the first network device. If the first message field is non-zero, the second network device does not alter the first message field since there could be a relay agent attached to the first network device that may set the first connection address field.
[0133] At step 226, the second network device forwards the first message to a connection address over the upstream connection to the second network. In one embodiment of the present invention, the connection address is an IP broadcast address (e.g., 255.255.255.255). However, other connection addresses can also be used.
[0134] The second network uses the first connection address in the first message field in the first message to forward the first message to one or more network host interfaces (e.g., IP 54 network host interfaces) available on first network at step 228. One or more network host interfaces available on the first network that can provide the services requested in first message send a second message with a second message type with a second connection address in a second message field to the first network at step 230 in FIG. 13B. The second connection address allows the first network device to receive data packets from the third network via a network host interface on the first network. The first network forwards the one or more second messages on the downstream connection to the second network device at step 232. The second network device forwards the one or more second messages to the first network device at step 234. The first network device selects one of the one or more network host interfaces on the first network using the one or more second messages at step 236. This allows a virtual connection to be established between the third network and the first network device via the selected network host interface on the first network and the second network device.
[0135] FIGS. 14A and 14B are a flow diagram illustrating a method 240 for resolving addresses for the network host interface selected by a first network device to create a virtual connection to the third network. Turning to FIG. 14A, at step 240 one or more second messages are received with a second message type on the first network device from the second network device from the first network on a downstream connection at step 242. The one or more second messages are offers from one or more protocol servers associated with one or more network host interfaces available on the first network to provide the first network device a connection to the third network. The first network device selects one of the network host interfaces using one of the one or more second messages at step 244. The first network device creates a third message with a third message type to accept the offered services from the selected network host interface at step 246. The third message includes a connection address for the first network in a first message field and an identifier to identify the selected network host interface in a second message field. At step 248, first network device equipment sends the third message to the second network device.
[0136] The second network device sends the third message over the upstream connection to the second network at step 250. The second network uses the first message field in the third message to forward the third message to the one or more network host interfaces available on first network at step 252.
[0137] A network host interface available on the first network identified in second message field in the third message from the first network device recognizes an identifier for the selected network host interface at step 254 in FIG. 14B. The selected network host interface sends a fourth message with a fourth message type to the first network at step 256. The fourth message is an acknowledgment for the first network device that the selected network host interface received the third message. The fourth message includes a second connection address in a third message field. The second connection address is a connection address for the selected network host interface. The first network stores the connection address for the selected network interface from the third message in one or more routing tables (e.g., an ARP table) on the first network at step 258. The first network will forward data from the third network to the first network device via the second network device when it is received on the selected network host interface using the connection address from the third message field. The first network forwards the fourth message to the second network device on the downstream connection at step 260. The second network device receives the fourth message and stores the connection address from the third message field for the selected network interface in one or more routing tables on the second network device at step 262. The connection address for the selected network interface allows the second network device to forward data from the third network sent by the selected network interface to the customer premise equipment.
[0138] At step 264, the second network device forward the fourth message to the first network device. At step 266, the first network device establishes a virtual connection between the third network and the first network device.
[0139] After step 266, the first network, the second network device and the first network device have the necessary connection addresses for a virtual connection that allows data to be sent from the third network to a network host interface on the first network, and from the first network over the downstream connection to the second network and then to the first network device. In one embodiment of the present invention, method 240 accomplishes resolving network interface hosts addresses from customer premise equipment with a cable modem in a data-over-cable with telephony return without extensions to the existing DHCP protocol.
[0140] Methods 216 and 240 of the present invention are used in data-over-cable system 10 with telephony return with CM 16 and CPE 18. However, the present invention is not limited to data-over-cable system 10 with telephony return and can be used in data-over-cable system 10 without telephony return by using an upstream cable channel instead of an upstream telephony channel.
[0141] FIGS. 15A and 15B are a flow diagram illustrating a method 268 for addressing network host interfaces from CPE 18. At step 270 in FIG. 15A, CPE 18 generates a DHCPDISCOVER message broadcasts the DHCPDISCOVER message on its local network with the fields set as illustrated in Table 6 above with addresses for CPE 18 instead of CM 16. However, more or fewer field could also be set. CM 16 receives the DHCPDISCOVER as a standard BOOTP relay agent at step 272. The DHCP DISCOVER message has a MAC 44 layer address for CPE 18 in DHCP 66 chaddr-field 132, which CM 16 stores in one or more routing tables. As a BOOTP relay agent, the CM 16 checks the DHCP 66 giaddr-field 130 (FIG. 6) at step 274. If DHCP 66 giaddr-field 130 is set to zero, CM 16 put its IP 54 address into DHCP 66 giaddr-field 130 at step 276.
[0142] If DHCP 66 giaddr-field 130 is non-zero, CM 16 does not alter DHCP 66 giaddr-field 130 since there could be another BOOTP relay agent attached to CPE 18 which may have already set DHCP 66 giaddr-field 130. Any BOOTP relay agent attached to CPE 18 would have also have acquired its IP 54 address from using a DCHP 66 discovery process (e.g., FIG. 12).
[0143] Returning to FIG. 15A, at step 278, CM 16 broadcasts the DHCPDISCOVER message to a broadcast address via PSTN 22 to TRAC 24. In one embodiment of the present invention, the broadcast address is an IP 54 broadcast address (e.g., 255.255.255.255). At step 280, one or more DHCP 66 proxies 158 associated with TRAC 24, recognize the DHCPDISOVER message, and forward it to one or more DHCP 66 servers 160 associated with one or more network host interfaces 162 available on CMTS 12. Since DHCP 66 giaddr-field 130 is already non-zero, the DHCP proxies leave DHCP 66 giaddr-field 130 intact. In another embodiment of the present invention, TRAC 24 includes DCHP 66 proxy 158 functionality and no separate DHCP 66 proxies 158 are used.
[0144] At step 282 in FIG. 15B, the one or more DHCP servers 160 receive the DHCPDISCOVER message from one or more DHCP proxies, and generate one or more DHCPOFFER messages to offer connection services for one or more network host interfaces 162 available on CMTS 12 with the fields set as illustrated in Table 7. The one or more DHCP servers 160 send the one or more DHCPOFFER messages to the address specified in DHCP 66 giaddr-field 130 (e.g., CM 16 or a BOOTP relay agent on CPE 18), which is an IP 54 address already contained in an ARP or other routing table in CMTS 12. Since CMTS 12 also functions as a relay agent for the one or more DHCP servers 160, the one or more DHCPOFFER messages are received on CMTS 12 at step 284.
[0145] CMTS 12 examines DHCP 66 yiaddr-field 126 and DHCP 66 giaddr-field 130 in the DHCPOFFER messages, and sends the DHCPOFFER messages down cable network 14 to IP 54 address specified in the giaddr-field 130. The MAC 44 address for CM 16 is obtained through a look-up of the hardware address associated with DHCP 66 chaddr-field 130. If the BROADCAST bit in DHCP 66 flags-field 122 is set to one, CMTS 12 sends the DHCPOFFER message to a broadcast IP 54 address (e.g., 255.255.255.255), instead of the address specified in DHCP 66 yiaddr-field 126. CMTS 12 does not update its ARP or other routing tables based upon the broadcast DCHP 66 yiaddr-field 126 DHCP 66 chaddr-field 132 address pair.
[0146] Returning to FIG. 15B, CM 16 receives the one or more DHCPOFFER messages and forwards them to CPE 18 at step 286. CM 16 uses the MAC 44 address specified determined by DHCP 66 chaddr-field 132 look-up in its routing tables to find the address of CPE 18 even if the BROADCAST bit in DHCP 66 flags-field 122 is set. At step 290, CPE 18 receives the one or more DHCPOFFER messages from CM 16. At step 292, CPE 18 selects one of the DHCPOFFER messages to allow a virtual connection to be established between data network 28 and CPE 18. Method 266 accomplishes addressing network interface hosts from CPE 18 in data-over-cable system 10 without extensions to the existing DHCP protocol.
[0147] FIGS. 16A and 16B are a flow diagram illustrating a method 294 for resolving network host interfaces from CPE 18. At step 296, CPE 18 receives the one or more DHCPOFFER messages from one or more DHCP 66 servers associated with one or more network host interface available on CMTS 12. At step 298, CPE 18 chooses one offer of services from a selected network host interface. At step 300, CPE 18 generates a DHCPREQUEST message with the fields set as illustrated in Table 8 above with addresses for CPE 18 instead of CM 16. However, more or fewer fields could also be set. At step 302, CPE 18 sends the DHCPREQUEST message to CM 16. At step 304, CM 16 forwards the message to TRAC 24 via PSTN 22.
[0148] At step 306, a DHCP 66 layer on TRAC 24 broadcasts the DHCPREQUEST message on its local network leaving DHCP 66 giaddr-field 130 intact since it already contains a non-zero value. TRAC's 24 local network includes connections to one or more DHCP 66 proxies. The DHCP 66 proxies accept DHCP 66 messages originally from CPE 18 destined for DHCP 66 servers associated with network host interfaces available on CMTS 12. In another embodiment of the present invention, TRAC 24 provides the DHCP 66 proxy functionality, and no separate DHCP 66 proxies are used.
[0149] One or more DHCP 66 proxies on TRAC's 24 local network recognize the DHCPOFFER message and forward it to one or more of the DHCP 66 servers associated with network host interfaces (e.g., IP 54 interfaces) available on CMTS 12 at step 308 in FIG. 16B. Since DHCP 66 giaddr-field 130 in the DHCPDISCOVER message sent by CPE 18 is already non-zero, the DHCP 66 proxies leave DHCP 66 giaddr-field 130 intact.
[0150] One or more DHCP 66 servers for the selected network host interfaces (e.g., IP 54 interface) available on CMTS 12 receive the DHCPOFFER message at step 310. A selected DHCP 66 server recognizes a DHCP 66 server identifier in DHCP 66 sname-field 134 or the IP 54 address that was sent in the DCHPOFFER message in the DHCP 66 yiaddr-field 126 from the DHCPREQUST message for the selected DHCP 66 server.
[0151] The selected DHCP 66 server associated with network host interface selected by CPE 18 in the DHCPREQUEST message creates and sends a DCHP acknowledgment message (“DHCPACK”) to CMTS 12 at step 312 using the DHCP 66 giaddr-field 130. The DHCPACK message is sent with the message fields set as illustrated in Table 9. However, other field settings can also be used. DHCP 66 yiaddr-field contains the IP 54 address for the selected network host interface available on CMTS 12 for receiving data packets from data network 28 for CPE 18.
[0152] At step 314, CMTS 12 receives the DHCPACK message. CMTS 12 examines the DHCP 66 giaddr-field 130 and looks up that IP address in its ARP table for an associated MAC 44 address. This is a MAC 44 address for CM 16, which sent the DHCPREQUEST message from CPE 18. CMTS 12 uses the MAC 44 address associated with the DHCP 66 giaddr-field 130 and the DHCP 66 yiaddr-field 126 to update its routing and ARP tables reflecting this address pairing at step 316. At step 318, CMTS 12 sends the DHCPACK message on a downstream channel on cable network 14 to the IP 54 and MAC 44 addresses, respectively (i.e., to CM 16). If the BROADCAST bit in the DHCP 66 flags-field 122 is set to one, CMTS 12 sends the DHCPACK message to a broadcast IP 54 address (e.g., 255.255.255.255), instead of the address specified in the DHCP 66 yiaddr-field 126. CMTS 12 uses the MAC 44 address associated with the DHCP 66 chaddr-field 130 even if the BROADCAST bit is set.
[0153] CM 16 receives the DHCPACK message. It examines the DHCP 66 yiaddr-field 126 and chaddr-field 132, and updates its routing table and an ARP routing table to reflect the address pairing at step 320. At step 322, CM 16 sends the DHCPACK message to CPE 18 via CMCI 20 at IP 54 and MAC 44 addresses respectively from its routing tables. If the BROADCAST bit in the DHCP 66 flags-field 122 is set to one, CM 16 sends the downstream packet to a broadcast IP 54 address (e.g., 255.255.255.255), instead of the address specified in DHCP 66 yiaddr-field 126. CM 16 uses the MAC 44 address specified in DHCP 66 chaddr-field 132 even if the BROADCAST bit is set to located CPE 18. At step 324, CPE 18 receives the DHCPACK from CM 16 and has established a virtual connection to data network 28.
[0154] In the event that CPE 18 is not compatible with the configuration received in the DHCPACK message, CPE 18 may generate a DHCP 66 decline (“DHCPDECLINE”) message and send it to CM 16. CM 16 will transmit the DHCPDECLINE message up the PPP 50 link via PSTN 22 to TRAC 24. On seeing a DHCPDECLINE message TRAC 24 sends a unicast copy of the message to CMTS 12. CM 16 and CMTS 12 examine the DHCP 66 yiaddr-field 126 and giaddr-field 130, and update their routing and ARP tables to flush any invalid pairings.
[0155] Upon completion of methods 266 and 292, CM 16 CMTS 12 have valid IP/MAC address pairings in their routing and ARP tables. These tables store the same set of IP 54 addresses, but does not associate them with the same MAC 44 addresses. This is because CMTS 12 resolves all CPE 18 IP 54 addresses to the MAC 44 address of a corresponding CM 16. The CMs 16, on other hand, are able to address the respective MAC 44 addresses of their CPEs 18. This also allows DHCP 66 clients associated with CPE 18 to function normally since the addressing that is done in CM 16 and CMTS 12 is transparent to CPE 18 hosts.
[0156] FIG. 17 is a block diagram illustrating a message flow 326 for methods 268 and 294 in FIGS. 15A, 15B, and 16A and 16B. Message flow 326 illustrates a message flow for methods 268 and 294, for a data-over-cable system with and without telephony return. In another embodiment of the present invention, CM 16 forwards requests from CPE 18 via an upstream connection on cable network 14 to DHCP servers 160 associated with one or more network host interfaces available on CMTS 12.
[0157] Method 268 and 294 accomplishes resolving addresses for network interface hosts from customer premise equipment in a data-over-cable with or without telephony return without extensions to the existing DHCP protocol. Methods 268 and 294 of the present invention are used in data-over-cable system 10 with telephony return. However, the present invention is not limited to data-over-cable system 10 with telephony return and can be used in data-over-cable system 10 without telephony return by using an upstream cable channel instead of an upstream telephony channel.
[0158] Using the initialization sequences described above (FIG. 12), CM 16 obtains configuration parameters at the beginning of every session on data-over-cable system 10. CM 16 uses an IP 54 address and a configuration file name obtained in a DHCP 66 response message during initialization to establish connections to data-over-cable system 10. CM 16 initiates a TFTP 64 exchange to request the configuration file obtained in the DHCP 66 response message.
[0159] The configuration file name obtained by CM 16 includes required configuration parameters for initialization and additional parameters for Class-of-Service and Quality-of-Service. The configuration parameters obtained in the required configuration file and additional parameters are sent from CM 16 to CMTS 12 in a registration message.
[0160] Seamless Network Address Allocation with a Protocol Agent
[0161] DHCP 66 messaging (FIG. 12) with a DHCP 66 discover message starts with the use of a “Martian” IP address (e.g., 0.0.0.0) as a source address (e.g., in DHCP 66 yiaddr-field 126, FIG. 6) for a network device (e.g., CM 16) since no legitimate IP address has been assigned to the network device by DHCP server 160 (FIG. 8). Since DHCP server 160 (FIG. 8) may be at a different geographical location from other network devices in the data-over-cable system 156, DHCP 66 messages may pass through one or more routers on a route through data-over-cable system 156 (FIG. 8). As is known in the art, routers translate differences between network protocols and route data packets to an appropriate network device on a network.
[0162] Routers typically use one or more types of filters to provide varying levels of security to a network. For example, a first type of router may filter all inbound messages that do not have an IP address for a specified network such as an intranet. A second type of router may filter all outbound messages that are not addressed to a specific IP address. Other types of filters may also be used on routers. It is desirable to use DHCP 66 messaging with routers, without having the routers filter out necessary DHCP 66 messages.
[0163] FIG. 18 is a block diagram illustrating a data-over-cable system 330 for protocol messaging. In data-over-cable system 330, router 332 has different filters for protocol messaging. For example, a first filter may be used in router 332 to filter out all external protocol messages from data network 28 regardless of the source address to prevent a rogue network device from being assigned a legitimate IP address in data-over-cable system 330. A second filter in router 332 may be used to filter protocol messages with a Martian source address since such a source address is often used to attack the data-over-cable system. However, other routers with other filters may also be used. Protocol agents 336, 338 and 340 provide network address allocation with protocol messaging regardless of the type of filtering used in router 332. Protocol agents, 336, 338 and 340 are shown as separate entities. However, protocol agents 336, 338 and 340 may also be integral to a network device (e.g., as a protocol agent process) and the invention is not limited to protocol agents as separate entities. In a preferred embodiment of the present invention, protocol agents 336, 338, and 340 are DHCP 66 agents. However, other protocol agents could also be used.
[0164] FIG. 19 is a flow diagram illustrating a method 342 for protocol messaging. Method 342 includes receiving a first message with a first protocol from a first network device on a first port on a protocol agent at step 344. The first port is used to send messages from the first network device via a route with one or more routers that may apply one or more protocol filters to the first protocol. The first message is sent from the protocol agent on a second port at step 346. The second port is used to send messages via a route that does not apply protocol filters to the first protocol. A second message is received on the second port on the protocol agent at step 348. The second message is sent from the protocol agent to the first network device on the first port at step 350. The first protocol server thereby avoids route filtering of the first protocol messages by using the protocol agent to send and receive messages on the second port.
[0165] In a preferred embodiment of the present invention, the first protocol is DHCP 66, the protocol agent is any of protocol agents 336, 338, or 340 used as a DHCP 66 agent and the first network device is any of DHCP server 160, CMTS 12, CM 16, CPE 18 or other network device.
[0166] As is known in the art, DHCP 66 uses UDP 60 as its transport protocol. For more information on UDP DHCP 66 see RFC-1541. DHCP 66 messages from a client (e.g., CM 16) to a server (e.g., DHCP server 160) are sent to the UDP “DHCP server” port-67, and DHCP messages from a server to a client are sent to the UDP “DHCP client” port-68. In a preferred embodiment of the present invention, first port is a UDP DHCP port (e.g., UDP DHCP client port 67 or UDP DHCP server port 68). The second port is a UDP port other than a UDP DHCP port (e.g., other than UDP client port-67 or UDP server port-68). Method 342 can be used with or without a second protocol agent on a second network device communicating on the second port. However, the present invention is not limited to these protocols and ports, and other protocols and ports could also be used (e.g., BOOTP protocol with TCP ports).
[0167] FIG. 20 is a flow diagram illustrating a method 352 for protocol messaging. Method 352 includes receiving a first message on protocol agent 336 associated with DHCP server 130 with DHCP 66 protocol for a network device on a UDP DHCP port (e.g., UDP DHCP server port-68) at step 354. The UDP DHCP port is used to send messages from DHCP server 160 to the network device via a route with one or more routers (e.g., 332) that may apply one or more protocol filters to DCHP 66. The first message is sent from protocol agent 336 to the network device on a second UDP 60 port at step 356 (i.e., on a UDP port other than UDP DHCP server port-68). The second UDP 60 port is used to send messages from protocol agent 336 on DHCP server 160 with DHCP 66 to the network device on a route that does not apply protocol filters to DHCP 66. A second message is received on the second UDP 60 port on protocol agent 336 from the network device at step 358. The second message is sent from protocol agent 336 to DHCP server 160 on a UDP DHCP port at step 360 (e.g., UDP DHCP client port-67). Method 352 is described with respect to protocol agent 336 associated with DHCP server 160. However, method 352 can also be practiced with a protocol agent associated with CMTS 12, CM 16, CPE 18, or other network devices in data-over-cable system 330 that use DHCP 66 messaging.
[0168] FIG. 21 is a flow diagram illustrating a method 362 for protocol messaging. At step 364, a first message is received on a first port on a protocol agent with a first protocol. The first port is used to send and receive messages via a route that may apply protocol filters to the first protocol. At step 366, the first message is sent from the first protocol agent to a second protocol agent on a second port. The second port is used to send and receive first protocol messages for the second protocol agent via a route that does not apply protocol filters to the first protocol. At step 368, a second message is received on the first protocol agent from the second protocol agent on the second port. At step 370, the second message is sent from the first protocol agent on the first port, thereby avoiding a route with routers that apply one or more protocol filters to the first protocol.
[0169] In a preferred embodiment of the present invention, the first protocol is DHCP 66, the first protocol agent is a DHCP 66 protocol agent, the second protocol agent is a DHCP 66 agent and the first port is a UDP DHCP port, and the second port is a UDP port other than a UDP DHCP port (e.g., other than UDP DHCP port 67 or 68). However, the present invention is not limited to these protocols and ports, and other protocols and ports could also be used (e.g., BOOTP protocol with TCP ports).
[0170] FIG. 22 is a flow diagram illustrating a method 372 for protocol messaging. At step 374, a first DHCP 66 message for CM 16 is received on a first port on protocol agent 340 associated with CMTS 12. The first port is used to send and receive messages via a route that may apply protocol filters to DHCP 66. At step 376, the first DHCP 66 message is sent from protocol agent 340 associated with CMTS 12 to protocol agent 338 associated with CM 16 on a second port. The second port is used to send and receive first protocol messages for protocol agent 338 via a route that does not apply protocol filters to DHCP 66. At step 378, a second DHCP 66 message is received on protocol agent 340 associated with CMTS 12 from protocol agent 338 on CM 16 on the second port. At step 380, the second DHCP 66 message is sent from protocol agent 340 to CMTS 12 on the first port, thereby avoiding a route with routers that apply one or more protocol filters to DHCP 66.
[0171] Method 374 is described with respect to protocol agent 340 associated with a CMTS 12 and protocol agent 338 associated with CM 16. However, method 362 can also be practiced with protocol agents associated with CPE 18, DHCP server 160, or other network devices in data-over-cable system 330.
[0172] A preferred embodiment of the present invention includes a system with a protocol agent and a protocol agent port. The system includes a protocol agent, for sending and receiving messages for a first protocol in a data-over-cable system. The protocol agent port sends and receives messages for a first protocol in a data-over-cable system. The protocol agent port is used to send and receive messages via a route that does not apply protocol filters to the first protocol.
[0173] In a preferred embodiment of the present invention, the protocol agent is a DHCP 66 agent, and the protocol agent port is a UDP 60 port other than a UDP DHCP port (i.e., other than UDP DHCP ports 67 or 68). However, the present invention is not limited to these protocols and ports, and other protocols and ports could also be used.
[0174] In a preferred embodiment of the present invention, the protocol agent is a software agent that implements one or more of the methods or system described herein. However, the protocol agent can also be implemented in hardware, firmware, or any combination thereof of hardware, software and firmware
[0175] The protocol agent can be implemented in any network device in data-over-cable system 330 that uses DHCP 66 messaging (e.g., CMTS 12, CM 16, CPE 18, DHCP server 160, etc.). The protocol agent can be integral to a DHCP 66 stack or implemented as a separate entity (e.g., a protocol agent process).
[0176] In another embodiment of the present invention, a first message is received on a first port on a first network device with a first protocol. The first port is used to send and receive messages via a route that may apply protocol filters to the first protocol. The first message is sent from the first network device to a second protocol agent on a second port. The second port is used to send and receive first protocol messages for the second protocol agent via a route that does not apply protocol filters to the first protocol. The second network device sends the message to a third network device. The second network device acts as a gateway in such a scenario. As is known in the art, a gateway stores and forwards data packets between dissimilar network devices.
[0177] The second network device adds its own network address as a gateway address to the first message and puts a DHCP 66 XID from DHCP XID-field 118 (FIG. 6) and/or a DHCP 66 chaddr (FIG. 6) from DHCP 66 chaddr-field 132 with a DHCP 66 giaddr into an internal table. A second message is received on the second network device from the third network device on the second port. The second network device looks up a DHCP 66 XID and/or DHCP 66 chaddr available in an internal table and determines that an address for the first network device from the internal table and forwards the second message to the first network device on the second port. If there are no messages received for a certain period of time then the DCHP 66 XID-field 118 and/or DHCP 66 chaddr-field 132 first network device address entry is erased.
[0178] In a preferred embodiment of the present invention, the first protocol is DHCP 66, the first port is a UDP DHCP port, and the second port is a UDP port other than a UDP DHCP port (e.g., other than UDP DHCP port 67 or 68). However, the present invention is not limited to these protocols and ports, and other protocols and ports could also be used (e.g., BOOTP protocol with TCP ports).
[0179] In another embodiment of the present invention, the first network device listens for data packets and listens for messages in data packets when the first network device receives a DHCP 66 message destined for a certain DHCP server 160. In such an embodiment, the first network device puts a DHCP 66 XID from DHCP XID-field 118 (FIG. 6) and/or a DHCP 66 chaddr from DHCP 66 chaddr-field 132 with a DHCP 66 giaddr into an internal table. A second message is received on the first network device from the second network device on the second port. The first network device looks up DHCP 66 XID-field 118 and/or DHCP 66 chaddr-field 132 the internal table and determines a DCHP 66 giaddr address from the internal table and forwards the second message to a gateway for the DHCP 66 message on the second port. If there are no messages received for a certain period of time then the DCHP 66 XID-field 118 and/or DHCP 66 chaddr-field 132 first network device address entry is deleted.
[0180] A preferred embodiment of the present invention provides several advantages over the prior art. The protocol agent allows DCHP messaging to be used in a data-over-cable system with routers that filter certain DHCP messages, filter DCHP messages with a Martian source address or apply other DHCP filters. The protocol agent uses a designated port that is not filtered in route to send and receive DHCP messages. Existing DHCP servers do not have to be modified as the protocol agent handles sending and receiving messages for the DHCP servers. The protocol agent can be used in a DHCP server, cable modem, cable modem termination system, telephone remote access concentrator or other network device to provide DHCP messaging via a route that does not apply filters to DHCP messages.
[0181] It should be understood that the programs, processes, methods, systems and apparatus described herein are not related or limited to any particular type of computer apparatus (hardware or software), unless indicated otherwise. Various types of general purpose or specialized computer apparatus may be used with or perform operations in accordance with the teachings described herein.
[0182] In view of the wide variety of embodiments to which the principles of the invention can be applied, it should be understood that the illustrated embodiments are exemplary only, and should not be taken as limiting the scope of the present invention. For example, the steps of the flow diagrams may be taken in sequences other than those described, and more or fewer elements or components may be used in the block diagrams.
[0183] The claims should not be read as limited to the described order or described elements unless stated to that effect. Therefore, all embodiments that come within the scope and spirit of the following claims and equivalents thereto are claimed as the invention.
Claims
I claim:
1. In a data system with a plurality of network devices, a method for protocol messaging, the method comprising the following steps:
receiving a first message with a first protocol on a first port on a protocol agent associated with a first network device, wherein the first protocol is a Dynamic Host Configuration Protocol, and the first port is used to send and receive messages for the first network device via a route that may apply one or more protocol filters to the first protocol;
sending the first message from the protocol agent on a second port, wherein the second port is used to send and receive messages for the first network device via a route that does not apply protocol filters to the first protocol;
receiving a second message on the second port on the protocol agent; and
sending the second message from the protocol agent to the first network device on the first port.
2. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 1.
3. The method of claim 1 wherein the first port is a Dynamic Host Configuration Protocol port.
4. The method of claim 1 wherein the second port is a port other than a Dynamic Host Configuration Protocol port.
5. The method of claim 1 wherein the second port is a transmission layer protocol port.
6. The method of claim 5 wherein the transmission layer protocol port is a User Datagram Protocol port.
7. The method of claim 1 wherein the step of sending the first message from the protocol agent on the second port includes sending the first message on the second port to a second protocol agent associated with a second network device on the second port.
8. The method of claim 1 wherein the second port is associated with a separate send port for sending messages and a separate receive port for receiving messages.
9. The method of claim 1 wherein the first network device is any of a protocol server, cable modem or cable modem termination system.
10. In a data system with a plurality of network devices, a method for protocol messaging, the method comprising the following steps:
receiving a first message with a first protocol on a first port on a first protocol agent associated with a first network device, wherein the first port is used to send and receive messages via a route that applies protocol filters to the first protocol;
sending the first message from the first protocol agent to a second protocol agent associated with a second network device on a second port, wherein the second port is used to send and receive first protocol messages via a route that does not apply protocol filters to the second protocol;
receiving a second message on the first protocol agent from the second protocol agent on the second port; and
sending the second message from the first protocol agent on the first port;
wherein the first protocol is a Dynamic Host Configuration Protocol, the first port is a Dynamic Host Configuration Protocol port, and the second port is other than a Dynamic Host Configuration Protocol port.
11. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 10.
12. The method of claim 10 wherein the second port is a User Datagram Protocol port.
13. The method of claim 10 wherein the first port is associated with a separate send port for sending messages and a separate receive port for receiving messages.
14. The method of claim 10 wherein the second port is associated with a separate send port for sending messages and a separate receive port for receiving messages.
15. The method of claim 10 wherein the first protocol agent and second protocol agent are associated with any of a protocol server, cable modem or cable modem termination system.
16. A protocol messaging system, the system comprising:
a protocol agent for sending and receiving messages for a protocol in a data system;
a first protocol agent port, for sending and receiving messages for a protocol, wherein the first protocol agent port is used to send and receive messages via a route that may apply one or more protocol filters to the protocol in a data system; and
a second protocol agent port, for sending and receiving messages for a protocol, wherein the second protocol agent port is used to send and receive messages via a route that does not apply protocol filters to the protocol in a data system;
wherein the protocol is a Dynamic Host Configuration Protocol, and the second protocol agent port is a port other than a Dynamic Host Configuration Protocol port.
17. The system of claim 16 wherein the second protocol agent port is a User Datagram Protocol port.
18. In a data system with a plurality of network devices, a method for protocol messaging, the method comprising the following steps:
receiving a first message with a Dynamic Host Configuration Protocol on a first User Datagram Protocol port on a protocol agent associated with a Dynamic Host Configuration Protocol server, wherein the first User Datagram Protocol port is a port used to send and receive messages for the Dynamic Host Configuration Protocol server via a route that applies one or more protocol filters to the Dynamic Host Configuration Protocol;
sending the first message from the protocol agent on a second User Datagram Protocol port, wherein the second User Datagram Protocol port is used to send and receive messages for the Dynamic Host Configuration Protocol server via a route that does not apply protocol filters to the Dynamic Host Configuration Protocol;
receiving a second message on the second User Datagram Protocol port on the protocol agent; and
sending the second message from the protocol agent to the Dynamic Host Configuration Protocol server on the first User Datagram Protocol port for the Dynamic Host Configuration Protocol.
19. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 18.
20. In a data system with a plurality of network devices, a method for protocol messaging, the method comprising the following steps:
receiving a first message with a Dynamic Host Configuration Protocol on a first User Datagram Protocol port on a first protocol agent associated with a first network device, wherein the first User Datagram Protocol port is used to send and receive messages via a route that applies protocol filters to the Dynamic Host Configuration Protocol;
sending the first message from the first protocol agent to a second protocol agent associated with a second network device on a second User Datagram Protocol Port, wherein the second User Datagram Protocol Port is used to send and receive messages via a route that does not apply protocol filters to the Dynamic Host Configuration Protocol;
receiving a second message on the first protocol agent from the second protocol agent on the second User Datagram Protocol port; and
sending the second message from the first protocol agent to first network device on the first User Datagram Protocol port.
21. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 20.
22. The method of claim 20 wherein the first network device and second network device is any of a protocol server, a cable modem termination system, or a cable modem.
23. In a data system with a plurality of network devices, a method for protocol messaging, the method comprising the following steps:
receiving a first message with a first protocol on a first port on a first network device, wherein the first port is used to send and receive messages for the first network device via a route that may apply one or more protocol filters to the first protocol;
sending the first message from the first network device on a second port, wherein the second port is used to send and receive messages for the first network device via a route that does not apply protocol filters to the first protocol;
receiving the first message on the second port on a second network device;
adding a network address for the second network device to the first message; and
sending the first message from the second network device to a third network device on the second port;
wherein the first protocol is a Dynamic Host Configuration Protocol, the first port is a Dynamic Host Configuration Protocol port, and the second port is other than a Dynamic Host Configuration Protocol port.
24. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 23.
25. The method of claim 23 further comprising:
receiving a second message on the second port on the second network device from the third network device; and
sending the second message from the second network device to the first network device on the second port.
26. In a data system with a plurality of network devices, a method for protocol messaging, the method comprising the following steps:
receiving a first message with a Dynamic Host Configuration Protocol on a Dynamic Host Configuration Protocol port on a Dynamic Host Configuration Protocol agent associated with a first network device, wherein the Dynamic Host Configuration Protocol port is used to send and receive messages via a route that applies protocol filters to the Dynamic Host Configuration Protocol;
sending the first message from the Dynamic Host Configuration Protocol agent to a second protocol agent associated with a second network device on a second port, wherein the second port is used to send and receive messages via a route that does not apply protocol filters to the second protocol, and wherein the second port is a port other than a Dynamic Host Configuration Protocol port;
receiving a second message on the Dynamic Host Configuration Protocol agent from the second protocol agent on the second port; and
sending the second message from the Dynamic Host Configuration Protocol agent on the Dynamic Host Configuration Protocol port.
27. A computer readable medium having stored therein instructions for causing a central processing unit to execute the method of claim 26.
Patent Citations (153)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4644533(A) | 1987-02-01 | Braff et al. | Applicant |
| US4881263(A) | 1989-11-01 | Herbison et al. | Applicant |
| US4996685(A) | 1991-02-01 | Farese et al. | Applicant |
| US5014234(A) | 1991-05-01 | Edwards, Jr. | Applicant |
| US5138712(A) | 1992-08-01 | Corbin | Applicant |
| US5301273(A) | 1994-04-01 | Konishi | Applicant |
| US5347304(A) | 1994-09-01 | Moura et al. | Applicant |
| US5430727(A) | 1995-07-01 | Callon | Applicant |
| US5442749(A) | 1995-08-01 | Northcutt et al. | Applicant |
| US5488412(A) | 1996-01-01 | Majeti et al. | Applicant |
| US5489897(A) | 1996-02-01 | Inoue | Applicant |
| US5528595(A) | 1996-06-01 | Walsh et al. | Applicant |
| US5583931(A) | 1996-12-01 | Schneider et al. | Applicant |
| US5586121(A) | 1996-12-01 | Moura et al. | Applicant |
| US5598410(A) | 1997-01-01 | Stone | Applicant |
| US5600717(A) | 1997-02-01 | Schneider et al. | Applicant |
| US5606606(A) | 1997-02-01 | Schneider et al. | Applicant |
| US5608446(A) | 1997-03-01 | Carr et al. | Applicant |
| US5610910(A) | 1997-03-01 | Focsaneanu et al. | Applicant |
| US5623542(A) | 1997-04-01 | Schneider et al. | Applicant |
| US5623601(A) | 1997-04-01 | Vu | Applicant |
| US5636211(A) | 1997-06-01 | Newlin et al. | Applicant |
| US5675732(A) | 1997-10-01 | Majeti et al. | Applicant |
| US5675742(A) | 1997-10-01 | Jain et al. | Applicant |
| US5678041(A) | 1997-10-01 | Baker et al. | Applicant |
| US5708654(A) | 1998-01-01 | Arndt et al. | Applicant |
| US5710885(A) | 1998-01-01 | Bondi | Applicant |
| US5724510(A) | 1998-03-01 | Arndt et al. | Applicant |
| US5761602(A) | 1998-06-01 | Wagner et al. | Applicant |
| US5778181(A) | 1998-07-01 | Hidary et al. | Applicant |
| US5784597(A) | 1998-07-01 | Chiu et al. | Applicant |
| US5790198(A) | 1998-08-01 | Roop et al. | Applicant |
| US5790548(A) | 1998-08-01 | Sistanizadeh et al. | Applicant |
| US5790677(A) | 1998-08-01 | Fox et al. | Applicant |
| US5790770(A) | 1998-08-01 | McClure et al. | Applicant |
| US5790806(A) | 1998-08-01 | Koperda | Applicant |
| US5793747(A) | 1998-08-01 | Kline | Applicant |
| US5799086(A) | 1998-08-01 | Sudia | Applicant |
| US5805804(A) | 1998-09-01 | Laursen et al. | Applicant |
| US5809252(A) | 1998-09-01 | Beighe et al. | Applicant |
| US5812819(A) | 1998-09-01 | Rodwin et al. | Applicant |
| US5815664(A) | 1998-09-01 | Asano | Applicant |
| US5818845(A) | 1998-10-01 | Moura et al. | Applicant |
| US5819028(A) | 1998-10-01 | Manghirmalani et al. | Applicant |
| US5819042(A) | 1998-10-01 | Hansen | Applicant |
| US5828655(A) | 1998-10-01 | Moura et al. | Applicant |
| US5828666(A) | 1998-10-01 | Focsaneanu et al. | Applicant |
| US5835720(A) | 1998-11-01 | Nelson et al. | Applicant |
| US5835727(A) | 1998-11-01 | Wong et al. | Applicant |
| US5841777(A) | 1998-11-01 | Cohen | Applicant |
| US5848233(A) | 1998-12-01 | Radia et al. | Examiner |
| US5852721(A) | 1998-12-01 | Dillon et al. | Applicant |
| US5854901(A) | 1998-12-01 | Cole et al. | Applicant |
| US5859852(A) | 1999-01-01 | Moura et al. | Applicant |
| US5864679(A) | 1999-01-01 | Kanai et al. | Applicant |
| US5870134(A) | 1999-02-01 | Laubach et al. | Applicant |
| US5872523(A) | 1999-02-01 | Dellaverson et al. | Applicant |
| US5884024(A) | 1999-03-01 | Lim et al. | Applicant |
| US5892754(A) | 1999-04-01 | Kompella et al. | Applicant |
| US5894479(A) | 1999-04-01 | Mohammed | Applicant |
| US5903558(A) | 1999-05-01 | Jones et al. | Applicant |
| US5909549(A) | 1999-06-01 | Compliment et al. | Applicant |
| US5913037(A) | 1999-06-01 | Spofford et al. | Applicant |
| US5915119(A) | 1999-06-01 | Cone | Applicant |
| US5922049(A) | 1999-07-01 | Radia et al. | Applicant |
| US5922051(A) | 1999-07-01 | Sidey | Applicant |
| US5923659(A) | 1999-07-01 | Curry et al. | Applicant |
| US5926458(A) | 1999-07-01 | Yin | Applicant |
| US5929850(A) | 1999-07-01 | Broadwin et al. | Applicant |
| US5941988(A) | 1999-08-01 | Bhagwat et al. | Examiner |
| US5943604(A) | 1999-08-01 | Chen et al. | Applicant |
| US5954797(A) | 1999-09-01 | Sidey | Applicant |
| US5958007(A) | 1999-09-01 | Lee et al. | Applicant |
| US5960177(A) | 1999-09-01 | Tanno | Examiner |
| US5974453(A) | 1999-10-01 | Andersen et al. | Applicant |
| US5982748(A) | 1999-11-01 | Yin et al. | Applicant |
| US5987524(A) | 1999-11-01 | Yoshida et al. | Applicant |
| US5991292(A) | 1999-11-01 | Focsaneanu et al. | Applicant |
| US5991306(A) | 1999-11-01 | Burns et al. | Applicant |
| US5996076(A) | 1999-11-01 | Rowney et al. | Applicant |
| US5999536(A) | 1999-12-01 | Kawafuji et al. | Applicant |
| US6003077(A) | 1999-12-01 | Bawden et al. | Applicant |
| US6005851(A) | 1999-12-01 | Craddock et al. | Applicant |
| US6006264(A) | 1999-12-01 | Colby et al. | Applicant |
| US6009103(A) | 1999-12-01 | Woundy | Applicant |
| US6012088(A) | 2000-01-01 | Li et al. | Applicant |
| US6013107(A) | 2000-01-01 | Blackshear et al. | Applicant |
| US6014545(A) | 2000-01-01 | Wu et al. | Applicant |
| US6018767(A) | 2000-01-01 | Fijolek et al. | Applicant |
| US6031841(A) | 2000-02-01 | Woundy | Applicant |
| US6032019(A) | 2000-02-01 | Chen et al. | Applicant |
| US6041041(A) | 2000-03-01 | Ramanathan et al. | Applicant |
| US6046979(A) | 2000-04-01 | Bauman | Applicant |
| US6049546(A) | 2000-04-01 | Ramakrishnan | Applicant |
| US6049825(A) | 2000-04-01 | Yamamoto | Applicant |
| US6049826(A) | 2000-04-01 | Beser | Applicant |
| US6052724(A) | 2000-04-01 | Willie et al. | Applicant |
| US6058421(A) | 2000-05-01 | Fijolek et al. | Applicant |
| US6058431(A) | 2000-05-01 | Srisuresh et al. | Examiner |
| US6061349(A) | 2000-05-01 | Coile et al. | Applicant |
| US6064372(A) | 2000-05-01 | Kahkoska | Applicant |
| US6065049(A) | 2000-05-01 | Beser et al. | Applicant |
| US6070187(A) | 2000-05-01 | Subramaniam et al. | Examiner |
| US6070242(A) | 2000-05-01 | Wong et al. | Examiner |
| US6070246(A) | 2000-05-01 | Beser | Applicant |
| US6073178(A) | 2000-06-01 | Wong et al. | Examiner |
| US6075787(A) | 2000-06-01 | Bobeck et al. | Applicant |
| US6091709(A) | 2000-07-01 | Harrison et al. | Applicant |
| US6094431(A) | 2000-07-01 | Yamato et al. | Applicant |
| US6104700(A) | 2000-08-01 | Haddock et al. | Applicant |
| US6112258(A) | 2000-08-01 | Miller et al. | Applicant |
| US6122254(A) | 2000-09-01 | Aydemir et al. | Applicant |
| US6128298(A) | 2000-10-01 | Wootton et al. | Applicant |
| US6130879(A) | 2000-10-01 | Liu | Applicant |
| US6130880(A) | 2000-10-01 | Naudus et al. | Applicant |
| US6137792(A) | 2000-10-01 | Jonas et al. | Applicant |
| US6137793(A) | 2000-10-01 | Gorman et al. | Applicant |
| US6148410(A) | 2000-11-01 | Baskey et al. | Applicant |
| US6157965(A) | 2000-12-01 | Mohammed et al. | Applicant |
| US6170061(B1) | 2001-01-01 | Beser | Applicant |
| US6178455(B1) | 2001-01-01 | Schutte et al. | Applicant |
| US6185624(B1) | 2001-02-01 | Fijolek et al. | Applicant |
| US6189102(B1) | 2001-02-01 | Beser | Applicant |
| US6208656(B1) | 2001-03-01 | Hrastar et al. | Applicant |
| US6212563(B1) | 2001-04-01 | Beser | Applicant |
| US6216171(B1) | 2001-04-01 | Isono et al. | Applicant |
| US6223222(B1) | 2001-04-01 | Fijolek et al. | Applicant |
| US6240464(B1) | 2001-05-01 | Fijolek et al. | Applicant |
| US6243369(B1) | 2001-06-01 | Grimwood et al. | Applicant |
| US6260072(B1) | 2001-07-01 | Rodriguez-Moral | Applicant |
| US6269099(B1) | 2001-07-01 | Borella et al. | Applicant |
| US6272150(B1) | 2001-08-01 | Hrastar et al. | Applicant |
| US6275853(B1) | 2001-08-01 | Beser et al. | Applicant |
| US6289377(B1) | 2001-09-01 | Lalwaney et al. | Examiner |
| US6295554(B1) | 2001-09-01 | Karadogan et al. | Applicant |
| US6301223(B1) | 2001-10-01 | Hrastar et al. | Applicant |
| US6301618(B1) | 2001-10-01 | Sitaraman et al. | Applicant |
| US6308328(B1) | 2001-10-01 | Bowcutt et al. | Applicant |
| US6331987(B1) | 2001-12-01 | Beser | Applicant |
| US6332163(B1) | 2001-12-01 | Bowman-Amuah | Applicant |
| US6337858(B1) | 2002-01-01 | Petty et al. | Applicant |
| US6351773(B1) | 2002-02-01 | Fijolek et al. | Applicant |
| US6370147(B1) | 2002-04-01 | Beser | Applicant |
| US6393478(B1) | 2002-05-01 | Bahlmann | Applicant |
| US6442158(B1) | 2002-08-01 | Beser | Applicant |
| US6449291(B1) | 2002-09-01 | Burns et al. | Applicant |
| US6453472(B1) | 2002-09-01 | Leano et al. | Applicant |
| US6490727(B1) | 2002-12-01 | Nazarathy et al. | Applicant |
| US6510162(B1) | 2003-01-01 | Fijolek et al. | Applicant |
| US2002/0122050(A1) | 2002-09-01 | Sandberg | Applicant |
| US2002/0136165(A1) | 2002-09-01 | Ady et al. | Applicant |
| US2003/0028891(A1) | 2003-02-01 | Hardt et al. | Applicant |
| WO/67385 | 2000-11-01 | Applicant |
Non-Patent Literature (24)
- W. Wimer, RFC 1542—Clarifications and Extensions for BOOTP, Oct. 1993.Applicant
- Kyees, P.J. et al., ADSL: A New Twisted-Pair Access to the Information Highway, IEEE Communications Magazine, vol. 33, Issue 4, Apr. 1995, pp. 52-60.Applicant
- Huang, Yin-Hwa et al., Design of an MPEG-Based Set-Top Box for Video on Demand Services, Acoustics, Speech, and Signal Processing, 1995, ICASSP-95., 1995 International Conference, vol. 4, ISBN: 0-7803-2431-5, May 9-12, 1995, pp. 2655-2658.Applicant
- “Cable Modem to Customer Premise Equipment Interface Specification (Interim) SP-CMCI-I02-980317”, Multimedia Cable Network Systems (MCNS) Holdings, L.P., 1998, pp. ii to 40.Applicant
- “Operations Support System Interface Specification Baseline Privacy Interface MIB (Interim) SP-OSSI-BPI-l01-980331”, MCNS Holdings, L.P., pp. ii to 33.Applicant
- “Cable Modem Termination System-Network Side Interface Specification (Interim Specification) SP-CMTS-NSll01-960702”, MCNS Holdings, L.P., 1996, pp. ii to 13.Applicant
- “Removable Security Module Interface Specification (Interim Specification) SP-RSMI-l01-980204”, MCNS Holdings, L.P., 1997, pp. ii to 48.Applicant
- “Baseline Privacy Interface Specification (Interim) SP-BPI-l01-970922”, MCNS Holdings, L.P., 1997, pp. ii to 66.Applicant
- “Operations Support System Interface Specification (Interim) SP-OSSll01-970403”, MCNS Holdings, L.P., 1997, pp. 1 to 30.Applicant
- “Radio Frequency Interface Specification (Interim Specification) SP-RFI-l02-971008”, MCNS Holdings, L.P., 1997, pp. ii to 186.Applicant
- “Cable Modem Telephony Return Interface Specification (Interim) SP-CMTRI-l01-970804”, MCNS Holdings, L.P., 1997, pp. ii to 74.Applicant
- “Security System Specification (Interim Specification) SP-SSI-l01-970506”, MCNS Holdings, L.P., 1997, pp. ii to 103.Applicant
- “Internet Engineering Task Force, Request for Comments 2131, Dynamic Host Configuration Protocol (DHCP)”, Mar. 1997, pp. 1 to 42.Applicant
- J. Fijolek, S. Adiraju, IPCDN Telephony Return MIB, “<draft-ietf-ipcdn-tri-mib-00.1.txt>,” Mar. 23, 1998. pp. 1 to 40.Applicant
- “Radio Frequency Interface Specification (Interim Specification) SP-RFI-I04-980724”, MCNS Holdings, L.P., 1997, pp. ii to 196.Applicant
- Droms, R., Dynamic Host Configuration Protocol, Request for Comments 1541, Oct. 1993, pp. 1 to 31.Applicant
- RFC 791, Internet Protocol, DARPA Internet Program Protocol Specification, Sep. 1981, pp. 1-37.Applicant
- Postel, J., Internet Protocol, DARPA Internet Program Protocol Specification, RFC 792, Sep. 1981, pp. 1-14.Applicant
- Postel, J., User Datagram Protocol, RFC 768, Aug. 28, 1980, pp. 1-3.Applicant
- RFC 793, Transmission Control Protocol, DARPA Internet Program Protocol Specification, Sep. 1981, pp. 1-51.Applicant
- Case, J. et al., A Simple Network Management Protocol (SNMP), RFC 1157, May 1990, pp. 1-26.Applicant
- Sollins, K., The TFTP Protocol (Revision 2), RFC 1350, Jul. 1992, pp. 1-9.Applicant
- Alexander, S., DHCP Options and BOOTP Vendor Extensions, RFC 2132, Mar. 1997, pp. 1-37.Applicant
- “Radio Frequency Interface Specification (Interim Specification) SP-RFIv1.1-103-991105”, MCNS Holdings, L.P., 1999, pp. Ii to 366.Applicant