US 6,922,412 B2Grant

Methods for dynamically assigning link addresses and logical network addresses

Issue Date:2005-07-26

•20 Claims

•11 Drawing Sheets

Abstract

An asymmetrical network for coupling customer-premises Internet hosts such as personal computers to the Internet. The head end of a CATV system has a high-bandwidth connection to the Internet. The down link connecting the personal computers to the Internet is the cables provided by the CATV system; the up link is a telephone connection to the head end. A router is connected to the down link by means of a RF modem, to the up link by means of an analog modem, and to a LAN which is connected to the Pcs. The router routes IP packets for the hosts that are received on the CATV cable to the hosts via the LAN; it routes IP packets from the hosts that are destined for the Internet to the head end via the telephone line. The asymmetrical network conserves IP addresses and addresses on the CATV cable by dynamically allocating the IP addresses for an RF modem's hosts and an address on the CATV cable for the RF modem in response to a request made by the RF modem via the telephone line. It further saves IP addresses by assigning a non-unique IP address to the router for use inside the LAN. When the CATV system fails, the asymmetrical network automatically begins to use the telephone line as both the up link and the down link, and when the CATV system is restored, the asymmetrical network automatically returns to using the CATV cable as the down link and the telephone line as the up link. A further feature of the asymmetrical network is that the head end components and the RF modem have IP addresses, so that standard TCP/IP protocols can be used to control the asymmetrical network.

Metadata

Assignee

Scientific-Atlanta, Inc.

Inventors

Scott E. Hrastar
George Horkan Smith

Application Information

Application Number:US 09/760,961

Filing Date:2001-01-16

Priority Date:1997-01-17

Art Unit:2661

Patent Drawings (11 sheets)

Description

Cross Reference to Related Patent Applications

[0001] This application is a continuation of U.S. patent application Ser. No. 08/843,061, which was filed Apr. 11, 1997, now U.S. Pat. No. 6,208,656 which claimed the priority to U.S. Provisional Application No. 60/035,618, filed Jan. 17, 1997, which was one of 10 patent applications directed to the cable data network system disclosed in the above Provisional Application that were filed on the same day. The 10 patent applications are listed by (former) attorney docket numbers and title in two groups. The seven in the first group all have the same Detailed Description.

[0002] U.S. application Ser. No. 08/833,198, U.S. Pat. No. 6,286,058, Apparatus and Methods for Automatically Rerouting Packets in the Event of a Link Failure

[0003] U.S. application Ser. No. 08/837,073, U.S. Pat. No. 6,301,223, Method of Using Routing protocols to Reroute Packets during a link Failure

[0004] U.S. application Ser. No. 08/843,061, U.S. Pat. No. 6,208,656, Methods for Dynamically Assigning Link Addresses and Logical Network Addresses

[0005] U.S. application Ser. No. 08,843,056, U.S. Pat. No. 6,178,455, Router which Dynamically Requests a Set of Logical Network Addresses and Assign Addresses in the Set to Hosts Connected to the Router

[0006] U.S. application Ser. No. 08/838,833, U.S. Pat. No. 6,618,353, Router for Use with a Link that has a Set of Concurrent Channels

[0007] U.S. application Ser. No. 08/832,714, U.S. Pat. No. 6,295,298, Method of Dynamically Assigning A Logical Network Address and a Link Address

[0008] U.S. application Ser. No. 08/840,304, U.S. Pat. No. 6,249,523, Router for which a Logical Network Address which is not Unique to the Router is the Gateway Address in Default Routing Table Entries

[0009] U.S. application Ser. No. 08/835,917, U.S. Pat. No. 6,308,328, Usage Statistics Collection for a Cable Data Delivery System

[0010] U.S. application Ser. No. 08/835,916, U.S. Pat. No. 6,324,267, Two-Tiered Authorization And Authentication for a Cable Data Delivery System

[0011] U.S. application Ser. No. 08/835,966, U.S. Pat. No. 6,052,819, System and Method for Detecting Correcting and Discarding Corrupted Data Packets in a Cable Data Delivery System

Field of the Invention

[0012] The invention concerns data networks generally and more particularly concerns data networks that employ protocols belonging to the TCP/IP protocol suite and data networks that are asymmetric, that is, data networks in which there is more capacity to move data in one direction than there is in the reverse direction.

Description of the Prior Art

[0013] In the not-too-distant past, images could be processed and displayed only by large, special-purpose computer systems. Owners of lower-cost and less-powerful computers such as personal computers had to content themselves with character-based displays. The cost of memory has dropped so quickly and the power of microprocessors has increased so greatly in recent years, however, that modern personal computers are completely capable of processing and displaying images. Indeed, modern graphical user interfaces depend to a large extend on this capability.

[0014] Frustratingly enough for users of personal computers, the old problems with images have returned in another area, namely network computing. In network computing, the personal computer or work station is connected to a network and is able to use the network to fetch the data it is processing from remote locations. The most recent development in network computing is the Internet, a world-wide logical network which permits anyone who has access to the Internet to interactively fetch data including images from just about anywhere in the world. For example, using the Internet, it is possible to fetch pictures of the latest restoration projects in Florence, Italy from that city's home page on the World Wide Web.

[0015] The main drawback to interactively fetching data on the Internet is the length of time it takes to retrieve and display images. The problem is so serious that many people set up the program they use to access the Internet so that it does not fetch images. Doing this restricts the user to character data, but greatly decreases the time it takes to access information. The bottleneck in retrieving images from the Internet is not the personal computer, but rather the lack of capacity or bandwidth of the networks over which the images must be fetched. One part of the network where bandwidth is particularly restricted is the analog telephone line that connects most PC users to the Internet. It has been known for years that the bandwidth of the telephone system can be increased by replacing the analog system with a digital system, but all of the known techniques for doing this require extensive modification of the telephone system.

[0016] A great many homes do in fact have a high bandwidth connection, namely that provided by cable television. The problem with this connection is that it is one way. A PC may receive data via a home's CATV cable, but it cannot use the cable to send data. Again, ways of making the CATV system bidirectional have been known for years. For example, in the early 1980's, Scientific-Atlanta, Inc. introduced and marketed a product known as the Model 6404 Broadband Data Modem for use with bidirectional CATV systems. Scientific-Atlanta, Inc. has also recently filed U.S. patent application Ser. No. 08/627,062, filed Apr. 3, 1966, Ser. No. 08/732,668, filed Oct. 16, 1996, and a continuation-in-part titled System and Method for Providing Statistics for Flexible Billing in a Cable Environment, Koperda, et al., filed Mar. 14, 1997 which describe bidirectional CATV systems. As with the telephone systems, the problem here is not the technology, but the fact that its introduction requires extensive modification of most existing CATV systems.

[0017] Given that many homes have a CATV cable and virtually all homes have an analog telephone line, systems have been proposed in which the CATV cable is used to send data from the Internet to the PC and the telephone line used to return data from the PC to the Internet. These systems take advantage of the fact that by far the most common pattern of interaction between users and networks is for the user to retrieve a large amount of data over the network, for example an image of a restored art work from Florence, examine the image, and then send a few keystrokes over the network. With this kind of interaction, far less bandwidth is needed in the channel that is used to return the keystrokes than in the channel that is used to fetch the image.

[0018] An example of such a system is the one disclosed in Moura et al., Asymmetric Hybrid Access System and Method, U.S. Pat. No. 5,586,121, issued Dec. 17, 1996, and in Moura et al., Remote Link Adapter for use in TV Broadcast Data Transmission System, U.S. Pat. No. 5,347,304, issued Sep. 13, 1994. In this system, the head end of a cable system has high bandwidth access to the Internet or to other networks and access via CATV cables and the telephone system to households or businesses with PCs. Data received from these networks is sent to PCs connected to the cable system's cables and responses from the PCs are collected via the telephone system and sent to the network. In the home or business, the PC is connected either directly or via a local area network to a device which includes both a radio frequency modem and a standard analog telephone modem. The radio frequency modem is connected to the CATV cable. It receives and decodes the data sent on the CATV cable and provides it to the PC. The telephone modem is connected to a standard telephone line. It receives data from the PC and sends it to the CATV head end, which in turn forwards it to the Internet or other networks.

[0019] While systems such as the one disclosed in the Moura references do provide a solution to the bandwidth problem, they have a number of deficiencies, particularly when used in the context of the Internet. Among the deficiencies are the following:

[0020] The system of Moura wastes Internet Protocol (IP) addresses for the computers attached to the modem. IP addresses are in short supply. In the system of Moura, however, IP addresses are statically assigned to the PCs and are consequently not available for reuse when a PC is idle or not engaged in an activity which involves network access.

[0021] From the point of view of the Internet, the system of Moura is a link level system, that is, the components of the system of Moura do not themselves have IP addresses and cannot themselves execute IP protocols. In particular, IP routing is not used within the system of Moura. One difficulty arising from this situation is that IP routing is centralized in the IP router that connects the head end to the Internet; another is that the modem in the system of Moura cannot function as an IP router.

[0022] In Moura, the telephone connection to the modem is used solely to transfer data from the PC and modem to the head end. All data received by the PC and modem is sent via the CATV cable. Consequently, when the CATV system fails, the PC is left without a connection by which it can receive data. This situation is made even less desirable by the fact that CATV systems are far more likely to fail than the telephone system.

[0023] The CATV channel to which the modem of Moura responds is statically assigned to a given modem, thereby rendering the channel unavailable for use by other modems when the PC connected to the given modem is idle or is not engaged in an activity which involves network access.

[0024] It is an object of the system disclosed herein to overcome the preceding and other deficiencies of systems like that of Moura.

Summary of the Invention

[0025] The problem of wasting IP addresses and link addresses by statically assigning them to hosts and cable modems is solved as follows: when the cable router becomes active, it first reads data from the CATV cable from which the CATV system can determine the CATV cable the cable router is attached to. The cable router then sends a message containing this information via the telephone line to the head end, which assigns a set of IP addresses for the PCs connected to the cable router and a link address for the cable router on the cable and sends a message containing the set of IP addresses and the link address to the cable router. The cable router then begins listening to the cable at the link address and responds to requests by the hosts for IP addresses by assigning them IP addresses from the set.

[0026] Other objects and advantages of the invention will be apparent to those skilled in the arts to which the invention pertains upon perusing the following Detailed Description and Drawing, wherein:

Brief Description of the Drawing

[0027] FIG. 1 is an overview of the physical components of the cable data network disclosed herein;

[0028] FIG. 2 shows the logical networks to which the IP addresses used in the cable data network belong;

[0029] FIG. 3 shows an IP datagram and an Ethernet frame as they are employed in a preferred embodiment;

[0030] FIG. 4 shows the channels, superframes, and superpackets used to carry data on the RF link in the preferred embodiment;

[0031] FIG. 5 is a block diagram of a preferred embodiment of the RF modem employed in the cable data network;

[0032] FIG. 6 is a diagram of the IP addresses and subnetwork masks employed in the cable data network;

[0033] FIG. 7 is a diagram that shows how the RF modem receives IP addresses and a <channel,pipe,link ID> triple when the RF modem becomes active;

[0034] FIG. 8 is a diagram that shows how IP packets addressed to hosts are rerouted via the telephone network when the RF modem detects a failure in the RF link;

[0035] FIG. 9 is a diagram of routing tables for router 101, modem pool 135, RF modem 106, and communications manager 102;

[0036] FIG. 10 is a diagram of the ARP cache for communications manager 102,

[0037] FIG. 11 is a diagram of a routing table and an ARP cache for a host 108; and

[0038] FIG. 12 is a diagram showing how IP addresses and <channel,pipe,LinkID> triples are dynamically assigned.

[0039] The reference numbers in the drawings have at least three digits. The two rightmost digits are reference numbers within a figure; the digits to the left of those digits are the number of the figure in which the item identified by the reference number first appears. For example, an item with reference number 203 first appears in FIG. 2.

Detailed Description

[0040] The following Detailed Description will begin with an overview of Internet protocol packets (datagrams) and of the IP addressing architecture employed in the cable data network of the preferred embodiment and will then describe the physical components of the cable data network of the preferred embodiment. Thereupon the discussion will show how IP addresses are mapped onto these components, how IP addresses are assigned to the components, and how routing of IP packets may be dynamically changed in response to failure of an RF link.

Internet Protocol Packets (Data Grams): FIG. 3

[0041] FIG. 3 shows those parts of an Internet protocol (IP) packet or datagram 301 that are required to understand the following discussion. An IP packet 301 has two main parts, header 303, which carries control information about the packet, and data 305, which is the data being transported in the packet. Header 303 has a fixed format and length, while data 305 may have a varying length. All that need be known about the contents of header 303 for the present discussion is that it contains two 32-bit Internet Protocol (IP) addresses, one of which, DEST IPA 307 specifies a destination in the Internet to which IP packet 301 is to be delivered, and the other of which, SRC IPA 309, specifies the source in the Internet of packet 301. Sources and destinations of Internet packets 301 are termed herein Internet hosts. An Internet host is an entity in a network which has an IP address and which is capable of responding to at least some of the protocols in the TCP/IP protocol suite. For details on IP addressing and the protocols of the TCP/IP protocol suite, see W Richard Stevens, TCP/IP Illustrated: The Protocols, Addison-Wesley, 1994, which is hereby incorporated by reference into this patent application.

[0042] The Internet is a logical network, not a physical network. Internet packets 301 are transported across a variety of different physical networks. While an Internet packet 301 is in a given physical network, it is transported in the same fashion that the physical network transports any kind of data. For example, one common kind of physical network is a LAN that uses the 10 base T protocol. One example of such a LAN is a LAN that uses the Ethernet® protocol developed by Xerox Corporation. In the Ethernet protocol, data moves in packets called frames. Each frame has a preamble 313, a destination Ethernet address 315, a source Ethernet address 317, an ethertype field, which specifies a type of the protocol, a data field 321, which carries the data, and a frame check sequence 323, which is an error checking code. When an Ethernet frame 311 is carrying an IP datagram 301, IP datagram 301 simply occupies data field 321. It is worth pointing out here that the Ethernet protocol does not examine the contents of IP datagram 301. There may of course be many levels of protocols between an IP datagram 301 and the physical medium upon which the IP datagram is being transported. In the following, only the next level down from the IP level is of concern, and this level is termed generically the link level, with the addresses at that level being termed link addresses. Thus, if the link level employs the Ethernet protocol, the link addresses are DA 315 and SA 317.

The IP Addressing and Routing Architecture

[0043] The IP addressing and routing architecture of the cable data network define how the IP addresses which are used to route Internet protocol packets (datagrams) in the Internet are mapped onto the networks which make up the cable data network's link level. The architecture has a number of fundamental principles:

- [0044] Each cable data network defines its own IP addressing domain, i.e., the network defines how IP addresses in a set of IP addresses which has been assigned to the cable data network are assigned to component devices in the cable data network.
- [0045] All devices in the cable data network which do routing or maintain data bases used in determining routes are IP hosts.
- [0046] Within the addressing domain, sets of IP addresses are assigned to hosts connected by a LAN to an RF modem, which is in turn connected to a CATV cable that is part of a network in the addressing domain. The RF modem functions as a router for packets addressed to the hosts connected to the LAN.
- [0047] IP routing in the networks consisting of portions of the cable network is hierarchical. An IP packet addressed to a host is first routed to the proper cable network, then captured by the host's RF modem and finally routed to the host by the RF modem.
- [0048] The RF modem may receive IP packets addressed to its hosts from two independent link level networks: an RF link level network (for example, a CATV network) and a switched public telephone network. The RF modem may further route outgoing IP packets via the switched public telephone network.
  Several advantages flow from these principles:

[0049] Because all of the devices that do routing or maintain routing data bases are Internet hosts, IP address assignment, packet rerouting, and network management can be done using the standard DHCP, RIP, and SNMP TCP/IP protocols. For details, see the Stevens reference, supra.

[0050] Because the RF modem can receive packets addressed to its hosts not only via the RF link level, but also via the telephone network, if the RF link fails, packets for the hosts can be simply rerouted to the RF modem via the telephone network. Moreover, the rerouting can by done by means of the RIP TCP/IP protocol.

[0051] Packets sent to the RF modem via the telephone network may be employed to tune the RF modem to a particular channel in the RF link, making it possible to dynamically assign a channel in the RF link to an RF modem. In effect, a link-level address in the RF link is dynamically assigned to the RF modem.

[0052] Because the cable data network can assign its own IP addresses, a mixed static-dynamic policy for assigning addresses may be pursued, with components that are constantly active having statically-assigned IP addresses and components that are intermittently active, such as the RF modems and the hosts attached to them, having dynamically-assigned IP addresses that are assigned at the beginning of activity by the component and are deassigned at the end of activity.

[0053] The dynamic assignment of IP addresses to RF modems and their hosts makes it possible to share a small number of IP addresses among a much larger group of users. Moreover, the dynamic assignment of IP addresses can by done by means of the DHCP TCP/IP protocol.

[0054] The dynamic assignment of IP addresses to RF modems also makes it possible to share a small number of addresses in the RF link among a much larger group of RF modems.

[0055] Network management can be done by means of the SNMP TCP/IP protocol.

[0056] The number of IP addresses required in the network is further reduced by giving the RF modems a reusable IP address for use inside the LAN to which a given RF modem's hosts are attached.

Physical Components of the Cable Data Network: FIG. 1

[0057] FIG. 1 shows the physical components of cable data network 100 in a preferred embodiment Cable data network 100 transfers data packets with IP addresses between Internet 150 and hosts 108, which in a preferred embodiment are PCs or work stations. Cable data network 100 also transfers packets with IP addresses among the components of cable data network 100 and uses Internet 150 to exchange data packets with IP addresses between cable data network 100 and remotely-located control and management components 111. These components typically deal with functions such as receiving information about new subscribers or billing.

[0058] In a preferred embodiment, cable data network 100 is implemented in a cable television (CATV) system. Packets from Internet 150 that contain the IP address of a host 108(i) are received in CATV head end 122, are put in the proper form for transmittal over cable 132 belonging to the CATV system, and are transmitted via cable 132 to RF modem 106(j) to which destination host 108(i) is attached. RF modem 106(j) reads the IP address of host 108 from the packet and routes the packet to host 108(i). Packets from host 108(i) which are intended for a destination in Internet 150 go to RF modem 106(j), which routes them via telephone line 131 and public switched telephone network (PSTN) 109 to a telephone modem (Tmodem) 110(k) in telephone modem pool 135 in head end 122. Tmodem 110(k) routes the packet to router 101, which routes it to Internet 150. Since public switched telephone network 109 allows bidirectional communication, router 101 may also route packets received from Internet 150 for host 108(i) to host 108(i) via tmodem 110(k) and RF modem 106(j). As will be explained in more detail in the following, this route is used in the event of a failure in the CATV portion of network 100.

[0059] Continuing with the details of the implementation of cable data network 100, data packets are transferred between Internet 150 and CATV head end 122 by means of a transmission medium belonging to a wide-area backbone network 124. Typically, the transmission medium will be a high-speed, high-capacity fiber optic cable such as a T1 or T3 cable, but it could also be a terrestrial or satellite microwave link. The transmission medium is connected to router 101, which in a preferred embodiment may be a router belonging to the 7000 series manufactured by Cisco Systems, Inc., San Jose, Calif.

[0060] Router 101 is coupled between WAN backbone 124 and local-area network (LAN) 120, which is the link-level network that connects the components of cable data network 100 which are located in CATV head end 122. Router 101 may both receive packets from backbone 124 or LAN 120 and provide them to backbone 124 or LAN 120. Each component connected to LAN 120 has both an IP address and a LAN address on LAN 120, and router 101 contains a routing table which it uses to route IP packets to IP hosts, including other routers. Router 101 examines every packet it receives on WAN backbone 124 or LAN 120; if the packet's destination IP address is one of the ones in the routing table, router 101 routes it to the component on LAN 120 which is to receive IP packets having that address; if it is not one of the addresses in the routing table, router 101 routes it to WAN backbone 124, which takes it to Internet 150. In each case, router 101 puts the data packet into the proper form to be transmitted via the relevant link-level network.

[0061] As will be apparent from the foregoing discussion, LAN 120 and router 101 can be used to route IP packets received from Internet 150 and destined to a host 108 via two routes. The first is via communications manager 102 and cable plant 105, cable 132, and RF modem 106. The second is to host 108 via telephone modem pool 135 and RF modem 106. Packets from host 108 and from RF modem 106 go via telephone modem pool 135 and LAN 120 to router 101. In other embodiments, it may also be possible to route packets addressed to RF modem 106 via the first route. Router 101 can finally route packets via Internet 150 between the components in head end 122, hosts 108, RF modems 106, and control and management component 111.

[0062] When packets are to go to a host 108 via cable 132, they are routed to communications manager 102, which puts the packets into the proper form for transport by that link-level network. FIG. 4 shows how data is transported on cable 132 in a preferred embodiment Cable 132 is an RF medium 401 which carries data in a fixed number of channels 403. Each channel 403 occupies a portion of the range of frequencies transported by cable 132. Within a channel 403(i), data moves in superframes 405. Each superframe contains a superframe header 414 and a fixed number of fixed-sized superpackets 407. The only portion of the superframe header that is important to the present discussion is stream identifier (STRID) 415, which is a unique identifier for the stream of data carried on channel 403. The combination of a channel's frequency and the stream identifier 415 uniquely identifies the network to which cable 132 belongs in the CATV system. As will be explained in more detail later, this unique identification of the network cable 132 belongs to is used by communications manager 102 to determine which network should receive the IP packets intended for hosts 108 connected to a given RF modem 106(i).

[0063] Each superpacket 407 contains a header 409 and data 411. The header contains a link identifier (LinkID) 413 in cable network 132 for an RF modem 106. The number of superpackets 407 is the number of pipes in channel 403(i). When a given RF modem 106(i) is active, it is associated with a <channel,pipe,link ID> triple, that is, the RF modem 106(i) is tuned to the channel 403(j) specified in the triple and watches the superpackets that belong to the pipe specified in the triple. For example, if the RF modem is associated with pipe 3, it watches superpacket 407(3) in superframe 405, and if superpacket 407(3)'s header 409 contains RF modem 106(i)'s Link Id 413, RF modem 106(i) reads data 411 from superpacket 407(3). The <channel, pipe, linkID> triple is thus the link address of RF modem 106(i) on cable 132. Data 411 is of course all or part of an IP packet 301. If the IP address of packet 301 specifies a host 108 connected to RF modem 106(i), RF modem 106(i) routes it to that host 108.

[0064] Returning to communications manager 102, that component receives IP packets 301 addressed to hosts 108 connected to networks whose link layers are cables 132 connected to head end 105 and routes them to the proper RF modems 106 for the hosts. It does by relating the IP address of an active host 108 to one of the networks and within the network to a <channel,pipe,linkID> triple specifying the RF modem 106 to which the host 108 is connected. As employed in the present context, an active host is one that currently has an IP address assigned to it. Using the information in the routing table, communications manager 102 makes superframes 405 for each channel 403(i) in the network containing cable 132. The superframes contain superpackets 407 directed to the RF modems 106 connected to that channel for which communications manager 102 has received IP packets 301. The superframes are stored in a dual-ported memory which is accessible to QPR modulators 103.

[0065] There is a QPR modulator 103 for each channel 403 in a given network, and the QPR modulator reads the superframes for its channel, digitally modulates the RF signal for the channel according to the contents of the superframes, and outputs the modulated signal to combiner 104, which combines the outputs from all QPR modulators and provides the combined output to cable plant 105, which outputs it to cables 132 belonging to the network. The QPR modulators employ quadrature partial response modulation. Of course, any kind of digital RF frequency modulation could be employed as well. It should also be pointed out that any arrangement could be employed which relates a given RF modem 106 to a portion of the bandwidth of the network to which cable 132 belongs, rather than the <channel,pipe,LinkID> triple used in the preferred embodiment, and that the portion of the bandwidth that carries packets addressed to hosts 108 connected to a given RF modem 106 can be termed in a broad sense the RF modem's “channel”.

[0066] Following cable 132 to RF modem 106, RF modem 106 is connected between cable 132, a LAN 133 to which one or more hosts 108 are connected, and telephone line 131 and provides interfaces to cable 132, LAN 133, and telephone line 131. FIG. 5 shows a block diagram of a preferred embodiment of RF modem 106. The components of RF modem 106 operate under control of CPU 505 and read data from and write data to memory 507, which has three kinds of memory components: static RAM 509, which is nonvolatile, that is, it is writable but retains its contents when RF modem 106 is turned off, dynamic RAM 511, which is volatile, and FLASH RAM 513, which is nonvolatile and writable but will only permit a fixed number of writes. SRAM 509 is used to store data which changes but must be kept across activations of RF modem 106. Examples of such data are the RF modem's telephone number and the addresses of RF modem 106 and hosts 108 on LAN 133. DRAM 511 is used for data that is only valid during an activation, such as the current routing table. FLASH RAM 513 is used for information that changes only rarely, such as the programs executed by CPU 505. In the preferred embodiment, RF modem 106 can load programs it receives in IP packets via telephone line 131 into Flash RAM 513.

[0067] Turning to the interfaces and beginning with the interface to cable 132, that interface has two main components, tuner 501 and decoder 503. Tuner 501 can be tuned under control of CPU 505 to a channel 403(i) in cable 132. Tuner 501 further demodulates the superframes 405 it receives on that channel and passes them to decoder 503. Decoder 503 examines superpacket 407(i) for the pipe which carries data addressed to RF modem 106, and if LinkID 413 in superpacket 407(i) specifies RF modem 106, decoder 503 does error correction, decodes the data, and passes it to memory 507. When an IP packet has accumulated in memory 507, CPU 505 examines the destination IP address in the packet, and uses a routing table in memory 507 to determine whether the packet is addressed to a host 108 connected to RF modem 106. If the packet is so addressed, CPU 505 obtains the LAN address corresponding to the IP address. CPU 505 provides the LAN address and the location of the packet in memory 507 to Ethernet integrated circuit 515, which packages the packet into one or more Ethernet frames and outputs it to Ethernet 133.

[0068] RF modem may also receive IP packets via phone line 131 and modem chip 517 that are addressed either to the RF modem 106 itself or to one of the hosts 108 connected to RF modem 106. In the first case, RF modem 106 responds to the packet; in the second, it routes the packet to the host as just described for packets from cable 132. When RF modem 106 receives a packet via LAN 133 that is not addressed to RF modem 106 itself, it routes the packet via modem chip 517 and telephone line 131 Included in host 108 is the software 107 necessary to interact with RF modem 106.

[0069] Continuing with the portion of the link level that is implemented using the public switched telephone network, modem chip 517 in RF modem 106 is connected by means of a standard analog telephone line 131 to public switched telephone network 109, and RF modem 106 can thus call other telephone numbers via PSTN 109 and be called from other telephone numbers in PSTN 109 In the present case, when RF modem 106 wishes to set up a session that will permit it to transfer IP packets 301 for a host 108, it calls a telephone number for telephone modem pool 135 The modem pool responds by assigning a telephone modem (Tmodem) 110 to RF modem 106 and assigning RF modem 106 an IP address. As shown in FIG. 1, telephone modem pool 135 is also connected to LAN 120 in head end 122. Telephone modem pool 135 serves as a router with respect to LAN 120 and the telephone connections currently being served as by the tmodems 110 in the modem pool. Once a telephone modem 110 and an IP address have been assigned to RF modem 106, RF modem 106 may send IP packets 301 to the devices connected to LAN 120 and receive IP packets 301 from those devices.

[0070] As will be explained in more detail in the following, the fact that PSTN 109 provides a bidirectional link between the devices connected to LAN 120 and RF modem 106 is employed to determine where RF modem 106 is in the cable network managed by head end 122, to dynamically assign a <channel,pipe,linkID> triple in cable 132 to RF modem 106, and to provide an alternate route to hosts 108 connected to RF modem 106 when there is a failure in the RF link between head end 122 and RF modem 106.

[0071] The remaining device which is connected to LAN 120 is control/management server 125, which in a preferred embodiment is implemented in software executing on a server constructed by SUN Microsystems, Inc., Mountain View, Calif. Control/management server 125 manages CDN 100. It responds to DHCP packets by dynamically allocating IP addresses to hosts 108 and sending SNMP packets to router 101 and communications manager 102 which cause them to set their routing tables as required for the newly-assigned IP address, responds to SNMP trap packets from the devices connected to LAN 120 and from RF modems 106, responds to RIP packets as required to update routings, and maintains the Management information Database used by the SNMP protocol as well as a list of unassigned IP addresses. A graphical user interface in control management server 125 shows the current status of CDN 100 and permits operator intervention in the operation of cable data network 100.

IP Addressing Architecture of CDN 100: FIGS. 6 and 2

[0072] CDN 100 maintains its own IP address domain. The proprietors of CDN 100 receive a set of 32-bit IP addresses and can apply those addresses to devices connected to CDN 100 as they see fit. FIG. 6 shows 32-bit IP address 601. The 32 bits are divided into two fields: type field 603, which defines the type of IP address 601 and host ID field 613, which identifies a specific host 108. The host IDs are organized into sets of IDs for the networks in the address domain. This is done by means of a technique called classless interdomain routing (CIDR). In this technique, the entire address is a host ID 613 that identifies an individual host; some number of the most significant bits of the host IP address are designated to specify a given network belonging to the domain; these bits are the same for all IP addresses in the given network and make up network ID 605.

[0073] Packets with IP addresses that have been assigned using the CIDR technique are routed by means of subnetwork masks. A subnetwork mask 608 is a 32-bit string of bits that is used to mask an IP address, that is, to select that part of the IP address that is currently relevant to the routing process. For example, if the IP address is being routed to the network it belongs to, the only part of the address that is relevant is the part that contains network ID 605. As shown in FIG. 6, in this case, unmasked part 610 selects the bits of network ID 605; masked part 611 hides the remaining bits of the IP address. Once the packet is in the network identified by network ID 605, the entire IP address is relevant and none of it is masked.

[0074] Using this technique, the proprietors of a domain of IP addresses can easily define the number of hosts in a network In CDN 100, the bits of IP address 601 specified by the subnetwork mask that identifies network ID field 605 specify a portion of a metropolitan cable network (for example, a single cable 132, a single cable plant 105 and the cables radiating from it, or even a single head end 122 and the cables 132 served by it). Host ID field 613 identifies one of the hosts 108 in the network identified by network ID field 605. As one would expect from the fact that CDN 100 has a relatively small number of CATV cables, a relatively large number of RF modems 106, and a relatively small number of hosts 108 per RF modem 106, the number of bits in network ID field 605 is comparatively small.

[0075] Comparison of addresses for routing purposes is done using subnetwork masks 608. The order in which an IP address being routed is compared to addresses in the routing table is by the unmasked length of the address in the routing table. Thus, the address being routed is compared first with addresses that are completely unmasked. For details, see Stevens, supra, pp. 7-9 and 140-141.

[0076] FIG. 2 shows the IP networks that exist in the cable data network and how they relate to the link level networks. Each addressable component of the cable data network appears in FIG. 2 with the IP addresses and link level addresses that apply to it. As is the case with all IP networks, each host must have its own IP address and must have in addition the address of a gateway in the network to which it can send IP packets for routing. Only one set of the IP networks, namely networks B 208(0 . . . n) need belong to cable data network IP address domain 202, that is, the cable data network assigns the addresses in these networks from the set provided to it. In the preferred embodiment, networks A and D also belong to address domain 202. IP addresses in network A all have network A's NetID 605 and IP addresses in network B 208(i) all have network B 208(i)'s NetID 605. The third IP network is network D 212. The router for this network is modem pool 135. In a preferred embodiment, the IP addresses in network D 212 are not visible outside cable data network 100. In other embodiments, the IP addresses in network D 212 may belong to another domain entirely, for example, one belonging to the telephone company that provides the modem pool.

[0077] Continuing with IP network A 206, this network has LAN 120 as its link level network. LAN 120 connects components of cable data network 100 that are always in use, and consequently, the IP addresses in network A 206 may be statically assigned. Routers with IP addresses in Net A are router 101, communications manager 102, and modem pool 135.

[0078] IP network B 208(i) may be one of several such networks, each of which will have its own statically-assigned NetID 605. Network B 208(i) has as its link layer one or more cables 132, to which RF modems 106 are connected. The router for network B 208(i) is communications manager 102. Each active RF modem 206(j) in network B 208(i) has a set 210(j) of IP addresses having network B 208(i)'s network ID 605 that are available to be assigned to hosts 108 connected to RF modem 206(j). An active RF modem 106 is one that has an active host 108 connected to it. Any IP address having the network ID for the network may belong to a given set 210(j). The link level network for each set of IP addresses 210(j) is the LAN 133 connecting the hosts 108 with RF modem 106(j). RF modem 106(j) serves as the router for that set of addresses. IP addresses of hosts 108 in net B 208(i) are dynamically assigned by control/management server 125. When RF modem 106(j) becomes active, control/management server 125 assigns modem 106(j) a set of IP addresses for the hosts 108 connected to RF modem 106(j). The IP addresses have the NetID 605 for network B 208(i) and as many host IDs 613 as are required for the hosts 108. As will be explained in more detail below, every host 108 connected to an RF modem 106(j) has an IP address for RF modem 106(j). Cable data network 100 conserves IP addresses by giving RF modems 106(j) identical IP addresses on the LANs 133 connecting the RF modems 106 to their hosts 108.

[0079] As indicated before, network 212 D uses hidden IP addresses belonging to the domain of cable data network 100 in a preferred embodiment, but the IP addresses may also be provided by another party such as a telephone company. The link layer in this network is public switched telephone network 109. When RF modem 106(j) dials into modem pool 135, modem pool 135 dynamically assigns RF modem 106(j) an IP address. Modem pool 135 also functions as the router in network 212 D. Modem pool 135 routes incoming IP packets with RF modem 106(j)'s IP address via network D 212 to RF modem 106(j). When the RF link is inoperative, modem pool 135 also routes incoming packets with the IP addresses of the hosts 108 attached to RF modem 106(j) to RF modem 106(j), which routes them further to the hosts. Modem pool 135 additionally routes all outgoing packets received from RF modem 106(j) via LAN 120 to router 101.

[0080] Router 101 normally routes IP packets destined for network B to communications manager 102 and those destined for network D to modem pool 135. If there is a failure in network B, router 101 can also route packets destined for a host 108 connected to RF modem 106(j) to RF modem 106(j) via network D.

[0081] FIG. 2 also shows the IP and link layer addresses by means of which the components of CDN 100 may be reached. Beginning with the components on Net A 206, router 101 has an IP address 203(b) of its own in Net A 206 and also has an address 205(a) on LAN 120 and an address 207 on WAN 124. Communications manager 102 has an IP address 203(c) of its own in Net A 206 and an address 205(d) on LAN 120. Router 101 also routes all packets to communications manager 102 that are to be carried via the networks B 208 specified in one or more NETID fields 605 in the IP addresses. Continuing with control/management server 125, that component has an IP address 203(e) in Net A 206 and a LAN address 205(b). Modem pool 135 has an IP address 214(b) in Net D 212, a LAN address 205(c), and a telephone number 208(a) in PSTN 109.

[0082] Continuing with network B 208(i), a given host 108(k) has a dynamically-assigned IP address. In the address, the host ID 613 specifies host 108(k) and the net ID 605 specifies network B 208(i). Each host also has a LAN address 211(a) in LAN 133. The most complex addressing situation is that of RF modem 106(j). RF modem 106(j) has an IP address 214(a) in network D 212, and has a reusable IP address 216. At the link address level, RF modem 106(j) is addressed in cable 132 by a <channel,pipe,linkID> triple, has a telephone number 208(b), and a LAN address 211(b) in LAN 133.

Routing and Routing Tables: FIGS. 9-11

[0083] Every host in an Internet network has a routing table. The routing table relates destination IP addresses of IP packets that are received in the host to gateway IP addresses of hosts on the same link-level network as the host to which the routing table belongs. If the host is a router, its routing table will relate IP addresses that are received in the router to IP addresses of hosts on the link-level networks that are connected by the router. Thus, a host can send an IP packet to a host on another link-level network by sending the packet to the router in the host's link-level network that sends packets to the other link-level network. Every host in an Internet network is also capable of executing the ARP protocol, which translates an IP address into a link-level address of the link-level network that the host is connected to.

[0084] Actually routing an IP packet received by a host is thus a two-step process. First, the host consults the routing table to find the gateway IP address corresponding to the IP packet's destination IP address; the gateway IP address specifies which host on the link-level network the IP packet is to be sent to; then the host executes the ARP protocol to find the link-level address of the host specified by the gateway IP address. When the host has the link-level address, it puts the IP packet in the form required by the link-level network and sends it to the link-level address. In order to save time in executing the ARP protocol, each host also has an ARP cache, which is a table of the current mappings between IP addresses of hosts in the link-level network and the link-level addresses of those hosts. For details on routing tables, see Stevens, supra, pp. 111-117; for details on the ARP protocol, see Stevens, supra, pp. 53-64.

[0085] FIG. 11 shows a routing table 1101 for a host 108(k) when host 108(k) is connected to cable data network 100. Host 108(k) has only three destinations to which it can route IP packets to itself, to another host 108(i) connected to LAN 133, or to RF modem 106(j), which is of course a host in LAN 133, but is also the router for all IP packets that have destinations outside LAN 133. There are thus n+2 entries 1103 in routing table 1101, where n is the number of hosts 108 attached to LAN 133. Each entry has three parts: a destination IP address, a gateway IP address, which must be an IP address of a host on LAN 133, and routing information, which indicates among other things whether the host specified by the gateway IP address is a router and the name of the link-layer network upon which the packet is to be routed.

[0086] Entry 1103(i) is for the so-called loop-back interface. It has a special IP address that clients and servers on the same host can use to send IP packets to each other. Packets sent to this IP address are processed completely within client 108 and never appear on LAN 133. As can be seen from FIG. 11, the same loopback IP address 1103 is used for both the destination IPA and the gateway IPA The entries labelled 104 are for the other hosts 108 in set 210(j). Each of these has the full IP address of the given host as both its destination IP address and its gateway IP address. What this means is that when a packet has an IP address that matches the destination IPA in entry 1103(j), its ultimate destination is a host 108(l) and the next step in the routing is for host 108(k) to use the ARP protocol to determine the LAN address corresponding to the packet's gateway IP address and then to send the IP packet to the LAN address.

[0087] IP packets whose destination addresses are not in set 210(j) are handled by entry 1103(k), which is the default entry for IP addresses that cannot be routed using other entries 1103. The default IPA 1115 is accordingly the destination IPA. The gateway IPA is the reusable IPA for RF modem 106(j). As will be explained in more detail later, this reusable IPA 1117 does not belong to the set of IP addresses 210(j) that are dynamically assigned to hosts 108 connected to LAN 133 when RF modem 106(j) becomes active. When host 108(k) receives a packet that matches default entry 1103(k), host 108(k) uses the ARP protocol to find the LAN address corresponding to re-usable IPA 1117, that is, the LAN address of RF modem 106(j) and sends the IP packet to RF modem 106(j). Since both the hosts 108 and RF modem 106(j) are connected to LAN 133, the routing info in entries 1104 and 1103(k) specifies LAN 133.

[0088] FIG. 11 also shows ARP cache 1119 for host 108(k). Cache 1119 has a cache entry 1120 for each host 108 connected to LAN 133 that currently has an IP address assigned to it, shown at 1122, and a cache entry 1120(j) for RF modem 106(j). In entries 1122, each entry has the IP address 1121 for the host 108 to which the entry belongs and the LAN address 1123 for the host 108; entry 1120(j) has reusable IP address 1117 for RF modem 106(j) and RF modem 106(j)'s LAN address 1125.

[0089] FIG. 9 shows the routing tables for router 101, modem pool 135, and RF modem 106. Beginning with routing table 901 for router 101, for purposes of the present discussion, two routings are of interest in routing table 101. The routing shown by entry 903(i) is for an IP address that specifies a host 108 when the RF link connecting head end 122 to host 108's RF modem 106 is functioning. In entry 903(i), the destination IP address is masked so that only NetId 605 is used for routing. Since that is the case, entry 903(i) matches every destination IP address 307 with that Net ID 605, that is, the net addresses for all of the hosts which are connected to the RF network to which cable 132 belongs. The gateway IP address is IP address 203(c) for communications manager 102. Thus, unless there is an entry 903 whose mask is longer than the one used with entry 903(i), the packet is routed to communications manager 102.

[0090] As will be explained in more detail below, as long as the RF link provided by cable 132 to RF modem 106 is functioning, there will only be an entry for the Net ID 605 for the network that RF modem 106 is attached to, and thus all packets directed to hosts 108 attached to modem 106 will be routed via communications manager 102 and cable 132. If all or part of the RF link fails, an entry like that for 903(j) is made in routing table 901 for each host 108 attached to an RF modem 106 whose RF link has failed. In this entry, the unmasked IP address of the host is used as the destination IP address and the gateway IP address is IP address 214(b), which is the address of modem pool 135. As long as entry 903(j) exists in routing table 901, packets addressed to the host 108 specified in the destination IP address will go by way of modem pool 135 and public switched telephone network 109, rather than by way of cable 132.

[0091] Continuing with routing table 921 for modem pool 135, this routing table has the same basic structure as routing table 901 Again, there are two entries that are of interest in the present situation. When a given RF modem 106(i) is receiving IP packets addressed to its hosts 108 by way of cable 132, it is still capable of receiving IP packets addressed to RF modem 106(i)'s IP address 214(a), and consequently, there will be an entry 922(j) for that IP address as long as RF modem 106(i) is active. In that entry, the destination IP field 930 and the gateway IP field 932 will both have IP address 214(a).

[0092] When RF modem 106(i)'s RF link via cable 132 has failed, there will be another entry 922(i) for each of the hosts 108 attached to RF modem 106(i). This entry's destination IP field 929 will contain the IP address 929 for the host 108, and the gateway IP address field 931 has IP address 214(a) for RF modem 106(i). Thus when the RF link is down, packets for hosts 108 routed to modem pool 135 by router 101 are further routed by modem pool 135 to RF modem 106(i).

[0093] Continuing with routing table 933 for RF modem 106, this routing table has an entry 935 for each host 108 attached to LAN 133 and two others that are of interest in the present context In the entries 936 for the hosts 108, each contains the host's IP address as both its destination IP address and gateway IP address. Entry 935(j)'s destination IP address is the IP address 214(a) assigned RF modem 106(j) by modem pool 135 when RF modem 106(j) became active; the gateway IP address here is again RF modem 106(i)'s reusable IP address 1117. This entry routes messages for RF modem 106(j) received via PSTN 109 to RF modem 106(j) itself The final entry, 935(k), is the default entry; the gateway IP address is IP address 214(b) for modem pool 135, and thus, all remaining packets received by RF modem 106(j) are routed via PSTN 109 to modem pool 135 and from thence to router 101.

[0094] The routing table for communications manager 102 is shown at 949. Again, there are three entries 951 of interest. Entry 951(i) routes all IP packets destined for the networks managed by communications manager 102; in the destination IPA portion of this entry, everything is masked but the net ID portion of the address. Entry 951(j) routes packets intended for communications manager 102 itself; the destination IPA and the gateway IPA are IPA 203(c) for communications manager 102. Default entry 951(k), finally, has as its gateway IPA the IP address 203(b) of router 101, consequently, all other IP packets are routed back to router 101 via LAN 120.

[0095] FIG. 10, finally, shows the implementation of ARP cache 1001 in communications manager 102. The technique used to implement the table is hashing, which is a standard technique for reducing search time in large tables. In ARP cache table 1001, the IP addresses 1003 for incoming packets addressed to a host 108 are hashed, that is, they are input to a function 1005 which produces small integer values 1009 from the IP addresses. The small integer is used as an index into a hash array 1011, whose elements are pointers 1013 to lists of IP addresses that hash to the index of element 1013. Each list entry 1015 has three fields: field 1017 contains a destination IP address; field 1019 is a pointer to the next list entry 1015 in the list, and CCB pointer 1021 is a pointer to a data structure called a CCB block 1023 which specifies the frequency, pipe number, and linkID to which packets having IP address 1017 may be sent. The fields of CCB block 1023 are IP address 1025, which has the same IP address as IPA 1017, modulator number 1029, which effectively specifies the frequency, pipe number 1031, which specifies the pipe, linkID 1033, which specifies the RF modem 106, and next pointer 1035 which specifies the next CCB block 1023. Translation of an IP address into the corresponding <channel,pipe number,linkID> triple works by hashing the IP address to get the index of list pointer 1013, following list pointer 1013 to the list, searching list entries 1015 until one is found that has the IP address being translated as its IP address 1017, and going to that list entry 1015's CCB block 1023 to find the information needed to form the triple. It is worth noting here that it is the structure of ARP cache 1001 which makes it possible in a preferred embodiment to use any IP address in the network of the cable 124 to which an RF modem 106(j) is attached for a host 108 that is attached to RF modem 106(j).

Dynamic Assignment of Resources: FIG. 12

[0096] A problem in the design of networks that employ IP addresses is that the IP addresses are only 32 bits long. The maximum number of address is consequently 2³², and the enormous growth of the Internet has resulted in a shortage of IP addresses. One of the techniques that cable data network 100 employs to reduce the number of IP address needed in cable data network 100 is the dynamic assignment of IP addresses to hosts 108 in network B 208(i) and of the <channel,pipe,link ID> triples used to specify destinations of data in cable 132 to RF modems 106(j). By dynamic assignment is meant here that the IP addresses in a given set of addresses C 210(j) and the <channel,pipe,link ID> triple listened to by RF modem 106(j) are assigned to RF modem 106(j) for the period of time that RF modem 106(j) is active. When RF modem 106(j) is not active, the IP addresses are available for assignment to other hosts 108 and the <channel,pipe,link ID> triple is available for assignment to another RF modem 106(k). Since only a small percentage of hosts 108 is active at a given time, dynamic assignment makes it possible to share a relatively small number if IP addresses and <channel,pipe,link ID> triples among a much larger number of users. It should be further noted here that the binding between a <channel,pipe,link ID> triple and the set of IP addresses 210(j) is also dynamic, i.e., what IP addresses correspond to a given <channel,pipe,link ID> triple is decided only when the IP addresses and the <channel,pipe,link ID> triple are assigned.

[0097] FIG. 12 shows the system used to do dynamic assignment of IP addresses and <channel,pipe,link ID> triples in a preferred embodiment. Dynamic assignment is handled cooperatively by control/management server 125 and communications manager 102. Both are hosts in IP network A 206 and have TCP/IP SNMP (simple network management protocol) agents 1203 and 1233, and control/management server 125 and communications manager 102 can cooperate by means of SNMP messages. For details on SNMP, see Stevens, supra, pp. 359-387.

[0098] Control/management server 125 further has a DHCP server 1201 and an IPA manager 1204 executing on it. DHCP server 1201 responds to IP packets belonging to the TCP/IP DHCP (Dynamic Host Configuration) protocol. As will be explained in more detail below, this protocol is employed to dynamically assign an IP host an IP address. Details on the DHCP protocol may be found in R. Droms, Dynamic Host Configuration Protocol, RFC 1541, obtainable in March 1997 at the URL www.cis.ohio-state.edu/htbin/rfc/rfc1541.html. The IP addresses themselves are managed by IPA manager 1204. Communications manager 102 also has executing on it a channel manager 1231, which manages the <channel,pipe,link ID> triples assigned to RF modems 106.

[0099] Assignment of IP addresses to hosts 108 connected to RF modem 106 and of a <channel,pipe,link ID> triple to RF modem 106 begins when DHCP server 1201 receives a DHCPDISCOVER message from an RF modem 106(j) that has become active. The DHCPDISCOVER message requests assignment of a number of IP addresses for the hosts 108 attached to RF modem 106(j). In the preferred embodiment, the DHCPDISCOVER message includes the IP address 1215 of RF modem 106(j) (assigned it by modem pool 135). The vendor-encapsulated-options part of the DHCPDISCOVER message includes the following, as shown at 1213 in FIG. 12:

- [0100] The number of addresses being requested 1216. An address is requested for every host 108 connected to RF modem 106(j).
- [0101] <frequency,streamID> pair 1217 and 1219. These uniquely identify the cable 132 that RF modem 106 is connected to.

[0102] The IP addresses of the hosts 108 are assigned by IP address manager 1204, with the assistance of SNMP agent 1203. The first step in assigning the IP addresses is determining which IP network B 208(i) the cable 132 belongs to that RF modem 106(j) is connected to. IPA manager 1204 uses <freq,streamID>,NETID> table 1237 to make this determination. Each entry in the table relates a <frequency,streamID> pair to a Net ID. All IP addresses assigned in the IP network B 208 identified by the Net ID must include the Net ID. The information in table 1237 is provided by channel manager 1231 in communications manager 102.

[0103] When IPA manager 1204 has the Net ID, it can assign the IP addresses. IPA manager 1204 has a list 1211(i) of free IP addresses for each network B 208(i), and it takes a set of IP addresses that has the number of addresses specified in address range 1216 from the free list 1211 for the network B 208(i). IPA manager 1204 then provides an SNMP set message with the IP addresses to SNMP agent 1203. As shown by arrow 1241, SNMP agent 1203 sends the message to SNMP agent 1233 in communications manager 102.

[0104] SNMP agent 1233 passes the message on to channel manager 1231, which maintains a list 1235 of free CCB blocks 1023 for each network. Channel manager 1231 finds a free CCB block in the list for the specified Net ID. The block is for a particular <channel,pipe> pair. Channel manager 1231 fills the IP address from the SNMP message and a link ID for the RF modem 106 into the CCB block 1023 and adds CCB block 1023 to ARP table 1101. Channel manager 1231 then uses SNMP agent 1233 to send a return message via SNMP agent 1203 to IPA manager 1203. As shown at arrow 1243, the return message contains the IP address and the <channel,pipe,link ID> triple that has been assigned to it. Channel manager 1231 adds entries for the newly-assigned IP addresses to its assigned IPA data base 1207. Each entry contains the IP address and the <channel,pipe,link ID> triple. Now that all of the information needed to relate the IP addresses of RF modem 106(j)'s hosts 108 to a <channel,pipe,link ID> triple on cable 132 is available, DHCP server 1201 returns a DHCPOFFER IP packet to RF modem 106(j) which is to receive the IP packets whose destination IP address belong to the set of addresses 210(j) corresponding to the <channel,pipe,linkID> triple.

[0105] In a preferred environment, IP addresses assigned to the hosts belonging to RF modem 106 are deassigned when RF modem 106(j) becomes inactive. This is detected by modem pool 135 when RF modem 106(j) hangs up and modem pool 135 sends an SNMP message to SNMP agent 1203 in control/management server 125 informing agent 203 of that fact. Agent 1203 removes the entries for the IP addresses for the hosts 108 connected to RF modem 106(j) from its data base and returns the IP addresses to IPA manager 1204, which puts them on the proper free list 1211(i). Agent 1203 also sends an SNMP message to SNMP agent 1233 in communications manager 102 informing communications manager 102 that the IP addresses have been deassigned. Agent 1233 passes the IP addresses to channel manager 1231, which removes the CCB blocks for the IP addresses from ARP table 1101 and returns them to the free CCB block list 1235 for the network to which the addresses belong.

[0106] In other embodiments, additional techniques may be employed to ensure that IP addresses and <channel,pipe,link ID> triples that are not being used are deassigned. One technique is the lease mechanism in the DHCP protocol. This mechanism assigns an IP address only for a limited period of time; if another DHCP protocol renewing the lease is not received from RF modem 106(j) within the limited period of time, the IP address is deassigned. Another is to monitor the number of packets sent to an IP address over a period of time. If there are none, the address is deassigned. The same technique may be used with <channel,pipe,link ID> triples; if there is no traffic on the <channel,pipe,link ID> triple, it is deassigned. In general, techniques analogous to those used to recover cache entries or memory pages may be used with IP addresses and <channel,pipe,link ID> triples.

Setting Up a Session with RF Modem 106

[0107] FIG. 7 shows the interactions 701 between the components of cable data network 100 when a RF modem 106(i) is inactive and a user of host 108(j) connected to RF modem 106(i) wishes to become connected to Internet 150. The user executes routines in software 107 which cause host 108(j) to send a setup request to RF modem 106(i) at modem 106(i)'s address in LAN 133, as shown at 702. Included in the setup request is authentication information such as a user identification and password and the telephone number of telephone modem pool 135. In the preferred embodiment, the authentication is for all of the hosts 108 connected to RF modem 106. RF modem 106 responds by first sending a dummy IP address to host 108(j) and then dialing the telephone number. The dummy IP address has a short lease, i.e., is valid for only a short time. Telephone modem pool 135 responds by setting up a Point-to-Point Protocol (PPP) link via PSTN 109 between RF modem 106 and a tmodem 110(k). Once this is done, RF modem 106 sends the authentication information to modem pool 135, which passes them on to control/management server 125. Control management server 125 then checks the authentication information, and if it is valid, control/management server 125 assigns an IP address in network D 21Z to RF modem 106(i). It returns the IP address to RF modem 106(i). RF modem 106(i) can now use TCP/IP protocols to communicate with the head end devices connected to LAN 120.

[0108] RF modem 106(i) must next obtain an IP address for host 108(j) and the <channel,pipe,link ID> triple which it is to receive packets addressed to host 108(j)'s IP address on cable 132. To do this, it sends a DHCPOFFER IP packet 703 to modem pool 135. Included in the vendor-encapsulated options portion of the protocol are the IP address of RF modem 106(i) and a <frequency, streamID 405> pair which RF modem 106(i) obtains by listening to any frequency on cable 132. As explained earlier in the discussion of superframes 405, the <frequency,streamID> pair uniquely identifies which cable 132 RF modem 106(i) is connected to.

[0109] Modem pool 135 receives DHCPOFFER packet 703, adds modem pool 135's IP address to it, and unicasts the packet via net A 206 to DHCP server 1201. DHCP in control/management server 125 responds to packet 703 and assigns IP addresses for the hosts 108 attached to RF modem 106(j) and a <channel,pipe,link ID> triple to RF modem 106 as described above. The IP addresses have leases that are long enough for the period for which an RF modem 106 is typically active. Next, control/management server 125 sends a DHCPOFFER packet 715 addressed to RF modem 106's IP address. This is routed to modem pool 135. The OFFER packet contains the following information:

- [0110] Range of IP addresses for the hosts 108 connected to RF modem 106.
- [0111] An IP address for RF modem 106 in Ethernet 133. As will be explained in more detail below, this IP address is not unique to RF modem 106.
- [0112] the subnet mask for the host IP addresses.
- [0113] IP addresses in network A 206 for a domain name server, for SNMP agent 1203, for communications manager 102, and for router 101.
- [0114] Information about where RF modem 106 can obtain current firmware.
- [0115] The <channel,pipe, link ID> triple that has been assigned to RF modem 106.
  Telephone modem pool 135 forwards the DHCP response packet to RF modem 106(i) (717) and RF modern 106(i) sets its tuner 501 to listen on the specified frequency and its decoder 503 to read superpackets on the specified pipe when they have the RF modem's link ID.

[0116] By this time, the lease on host 108(j)'s dummy IP address is about to expire and host 108(j) sends a DHCPDISCOVER packet requesting a new IP address. RF modem 106(i) responds by assigning one of the IP addresses it received in its DHCPOFFER packet to host 108(j) and sending a DHCPOFFER packet with the IP address to host 108(j). Similarly, when RF modem 106(i) receives a DHCPDISCOVER packet from any of the other hosts 108 attached to LAN 133, it assigns one of the IP addresses to that host 108 and sends the host 108 a DHCPOFFER packet that contains the assigned IP address.

[0117] In other embodiments, RF modem 106(i) may further respond to the DHCP OFFER packet 715 by sending an acknowledgment IP packet via PSTN 109 and modem pool 135 to communications manager 102 (719). Communications manager 102 responds to the acknowledgment by sending an acknowledgment 721 on the cable 132 at the channel and pipe RF modem 106(i) is listening to. The acknowledgment contains at least RF modem 106(i)'s

Taking Down a Session with RF Modem 106

[0118] As long as any of hosts 108 is connected to Internet 150, RF modem 106 listens for super packets addressed to it at the <channel,pipe,link ID> triple for RF modem 106 and maintains its connection via the telephone network to modem pool 135. When the last host 108 shuts down its connection to Internet 150, RF modem 106 hangs up on the telephone line connecting it to modem pool 135. Modem pool 135 responds to the fact that RF modem 106 has hung up with a DHCP release message to DHCP server 1201. The DHCP release message specifies the IP addresses assigned to RF modem 106.

[0119] Server 125 sends an SNMP packet to communications manager 102 instructing it to remove the entries for the IP addresses from its ARP cache 1001. Communications manager 102 returns the <channel,pipe,linkID> triple to its list of free <channel,pipe,ID> triples. When server 125 receives an SNMP acknowledgment from communications manager 102, it deletes the entries for the IP addresses for the hosts 108 connected to the IP modem from its data base and returns the IP addresses to its list of free IP addresses. In other embodiments, the DHCP protocols used to get and free IP addresses for hosts 108 may originate with the individual host 108.

RF Modem 106 as a Proxy DHCP Server

[0120] The entities in a network that respond to DHCP protocols are known as DHCP servers. In cable data network 100, the DHCP server is implemented in software running on control/management server 125. Additionally, however, each active RF modem 106(i) functions as a proxy DHCP server. By this is meant that it retains enough information locally to handle DHCP protocols that originate with hosts 108 connected to RF modem 106(i). In so doing, it appears to host 108 as a standard DHCP server and further greatly decreases the amount of traffic required to provide hosts 108 with IP addresses.

[0121] Standard DHCP servers are always active; thus, the standard Internet client software running on host 108 expects that the DHCP server will always respond to a DHCPDISCOVER packet from a host with a DHCPOFFER packet that contains an IP address for host 108. RF modem 106, however, is not always active and may have to establish a connection with Network A 206 and use the DHCP protocol to obtain the IP addresses for subnetwork C 210(j) before it can respond to a DHCPDISCOVER packet from a host 108. For that reason, when RF modem 106 first becomes active, it provides the host 108 that caused it to become active with a short-lived dummy IP address as previously described. RF modem 106 then obtains a set of IP addresses for its hosts 108 as previously described. Once it has the IP addresses, it responds to DHCPDISCOVER packets from the hosts 108 by assigning the hosts 108 IP addresses from the set. There is thus no need in these cases to send a DHCPDISCOVER packet to modem pool 135 and control/management server 125.

Automatic Rerouting in the Event of a Failure of the RF Link: FIG. 8

[0122] An important advantage of cable data network 100 is that if the RF link to a RF modem 106(i) fails, cable data network 100 automatically reroutes packets addressed to hosts 108 connected to that RF modem so that they are routed by way of modem pool 135 and public switched telephone network 109 to RF modem 106. When the RF link is again operative, cable data network 100 automatically again reroutes the packets via the RF link. This automatic fallback and restoration feature takes full advantage of the fact that public switched telephone network 109 is bidirectional and of the fact that an active RF modem 106 has an IP address by means of which it is accessible via modem pool 135 and PSTN 109.

[0123] The automatic fallback and restoration feature is implemented using the TCP/IP routing information (RIP-2) protocol, described beginning at page 29 of Stevens, supra. This protocol is used in networks employing IP addresses to propagate addressing information among the routers in the network. Any other protocol which performs this function could also be employed. Typically, each router in a network will broadcast a RIP packet to the other routers every thirty seconds or so. The RIP packet contains the current routing table of the router sending the RIP packet. The other routers read the RIP packet and update their routing tables accordingly. A triggered RIP packet is sent each time the metric for a route changes. The metric is a value which expresses the cost of sending a packet by the route. Each router keeps track of the time interval since it last received an RIP packet from each of the other routers, and if the time interval exceeds a predetermined maximum, the router removes the routes it received from that router from its routing table.

[0124] In the preferred embodiment, when RF modem 106 is active, it is constantly listening to cable 132. If tuner 501 detects that there is no RF signal on the channel it is listening to or decoder 503 detects that it is no longer receiving superframes 405, or that it can no longer decode the superpackets 407 it is receiving, or that the number of superpackets 407 with errors has increased above a predetermined threshold, tuner 501 or decoder 503 signals an error condition to CPU 505. What happens next is shown in FIG. 8. Portion 701 of the figure is the setup scenario of FIG. 7; portion 801 shows how RF modem 106 and system 100 respond when such an error condition occurs.

[0125] As shown at 803, when the error condition occurs, the routing tables in router 101 and communications manager 102 are routing IP packets addressed to hosts 108 via communications manager 102 and cable 132; IP packets from hosts 108 to IP addresses in Internet 150 are being routed via RF modem 106, PSTN 109, telephone modem pool 133, LAN 120, and router 101. This condition is indicated in portion 801 at 803. At 805, RF modem 106 detects a failure in the RF link; RF modem 106 thereupon sends an SNMP trap packet, i.e., an error message that uses the TCP/IP SNMP (Simple Network Management Protocol) addressed to control/management server 125 via PSTN 109 and telephone modem pool 135. The network management system (NMS) is implemented by programs executing on server 125, and NMS responds to the trap packet by recording the fact that there has been a failure in the RF link in its system management data bases. The NMS system response may also include other actions such as generating a display showing the problem in the NMS graphical user interface (GUI) or triggering an alarm.

[0126] Next, RF modem 106 sends a triggered RIP packet to modem pool 135 with RF modem 106's routing table. Modem pool 135 responds to the RIP packet by adding the IP addresses of the hosts 108 to its own routing table 921. It then sends a triggered RIP packet with the changes to the routers on LAN 120. Router 101 responds to the RIP packet by adding the IP addresses for the hosts 108 to its routing table 901. In other embodiments, RF modem 106 may send triggered RIP packets directly to modem pool 135 and router 101. As explained in the discussion of routing tables above, the result of these changes is that packets addressed to hosts 108 are now routed to hosts 108 via modem pool 135 and PSTN 109. Control/management server 125 also receives the RIP packet and generates an NMS trap 815 for the NMS system which indicates to it that the fallback setup has been completed. The NMS system stores that information in its data base and changes the displays showing the network accordingly.

[0127] It is important to note here that as long as the RF link is operative and RF modem 106 is active, the routing of packets to hosts 108 connected to RF modem 106 does not change. Consequently, when the RF link is operative, RF modem 106 does not produce RIP packets. However, as long as the RF link is inoperative, RF modem 106 periodically produces RIP packets in the fashion of other routers and the RIP packets are sent to modem pool 135 and router 101 as just described. The fallback routing for the IP addresses belonging to the hosts 108 continues as long as RF modem 106 continues to send RIP packets. If RF modem 106 senses that the RF link is again operative, RF modem 106 sends another trigger RIP packet with its routing table, but with the metric for reaching the hosts 108 set so high that modem pool 135 and router 101 remove the entries for the hosts' IP addresses. Thereupon, RF modem 106 ceases sending RIP packets. If RF modem simply ceases sending RIP packets, for example because a user has turned it off, the entries for the hosts' IP addresses are removed from the routers in the manner described in the discussion of the RIP protocol above.

Reusable IP Addresses for RF Modems 106: FIG. 11

[0128] As mentioned above, a major goal in the design of cable data network 100 is reducing the number of IP addresses required for the cable data network. One technique used to achieve this goal is giving all RF modems 106 in a network the same reusable IP address in the LANs 133 to which the hosts 108 for which RF modem 106 is the router are attached. This is possible because RF modem 106's IP address in LAN 133 is used only by hosts 108 attached to LAN 133; IP packets sent to RF modem 106 from other hosts are sent to IP address 214(a) in network D 212, which is provided by modem pool 135. Since RF modem 106's IP address in LAN 133 is not visible outside LAN 133, the IP address can be the same in all LAN 133s. As indicated in the discussion of setting up a session above, RF modem 106 receives its IP address in LAN 133 in the DHCPOFFER packet that contains the IP addresses for its hosts 108 and RF modem 106's <channel,pipe,link ID> triple. The savings of IP addresses made possible by this technique are significant. For example, many LANs 133 will be in private households and will have only a single PC as a host 108. Both the PC and RF modem 106 must have an IP address on LAN 133. It should further be noted that because reusable IP address 117 is used only within the LANs 133 connected to RF modem 106, there is no need that it even be an IP address in the address domain of cable data network 100.

Conclusion

[0129] The foregoing Detailed Description has disclosed to those skilled in the relevant arts how to make and use a cable data network which is fully integrated into the Internet, which takes advantage of the bidirectional nature of the telephone system to establish a control path between the head end of the cable data network and the RF modems attached to the CATV cable and to provide an alternate path for data being sent to hosts attached to the RF modem in case of failure of the RF link, which dynamically assigns IP addresses to hosts and link addresses to the RF modems, which employs the RF modems as routers, and which saves IP addresses by reusing the IP addresses of RF modems in the LANs to which they are attached.

[0130] While the Detailed Description presents the best mode presently known to the inventors of implementing the cable data network, it will be immediately apparent to those skilled in the relevant arts that the principles used to implement the cable data network may be employed in many other circumstances. For example, the RF link may be replaced by any unidirectional link and the telephone line may be replaced by any bidirectional link that is independent of the RF link. Similarly, the LAN that connects the RF modem to the hosts may be replaced by any medium which provides a bidirectional connection between RF modem and hosts.

[0131] Moreover, the techniques described herein for dynamically assigning IP addresses to hosts will work with any kind of logical network addresses, including, for example, virtual circuit numbers. Similarly, the techniques described for dynamically assigning <channel,pipe,linkID> triples to RF modems can be used equally well to dynamically assign any kind of link-level address. The techniques will also work with any technique for subdividing the bandwidth of the unidirectional connection among a number of modems.

[0132] Finally, the TCP/IP protocols employed in the preferred embodiment may be replaced by any other protocols which have the same effect. In particular, the DHCP protocol may be replaced by any protocol which can be used for dynamic assignment of logical network addresses, the RIP protocol may be replaced by any protocol which communicates changes in routings to routers, and the SNMP protocol may be replaced by any kind of network management protocol.

[0133] The foregoing being the case, the Detailed Description is to be understood as being illustrative and not restrictive and the scope of the invention claimed herein is to be determined not by the Detailed Description but rather by the attached claims as interpreted with the full breadth permitted under the patent laws.

Claims

1. A method employed in a RF modem in dynamic assignment of a link address on a RF connection, the RF connection connecting the RF modem with a head end, the link address being used by the head end for forwarding of information from the head end through the RF modem to at least one host that is connected to the RF modem, the method comprising the steps performed in the RF modem of:

receiving the link address, the link address being assigned by the head end;

selecting, based upon the link address, a message that is carried on the RF connection to be forwarded to the at least one host, wherein the link address comprises an identifier for a frequency in the RF connection, the messages being carried on the RF connection in a RF channel associated with the frequency; and

forwarding the selected message to the at least one host.

2. The method of claim 1, wherein the link address further comprises an identifier for a plurality of time periods, the message being carried on the RF connection in the RF channel during at least one time period of the plurality of time periods.

3. The method of claim 2, wherein each time period of the plurality of time periods is relative to the start of a frame that is repetitively transmitted on the RF channel.

4. The method of claim 3, wherein the link address further comprises an identifier that is matched with information in a header of the message before the message is forwarded to the at least one host.

5. The method of claim 1, wherein the link address further comprises an identifier that is matched with information in a header of the message before the message is forwarded to the at least one host.

6. The method of claim 1, further comprising the steps of:

determining that the forwarding of information from the head end through the RF modem to the at least one host has terminated; and

releasing the link address to the head end responsive to determining that the forwarding of information has terminated.

7. The method of claim 6, wherein the releasing step further comprises sending a DHCP (Dynamic Host Configuration Protocol) packet from the RF modem to the head end.

8. The method of claim 1, wherein the link address is received over a bidirectional link during the receiving step.

9. The method of claim 8, wherein the bidirectional link is a PSTN (Public Switched Telephone Network) link that is different from the RF connection.

10. The method of claim 1, wherein the received link address is received in a DHCP packet.

11. An apparatus for obtaining a dynamic assignment of a link address in a RF modem, the RF modem connected to a head end over a RF connection, the link address being used by the head end for forwarding of information from the head end through the RF modem to at least one host that is connected to the RF modem, the apparatus comprising:

logic configured to receive the link address, the link address being assigned by the head end;

logic configured to select, based upon the link address, a message that is carried on the RF connection to be forwarded to the at least one host, wherein the link address comprises an identifier for a frequency in the RF connection, the messages being carried on the RF connection in a RF channel associated with the frequency; and

logic configured to forward the selected message to the at least one host.

12. The apparatus of claim 11, wherein the link address further comprises an identifier for a plurality of time periods, the message being carried on the RF connection in the RF channel during at least one time period of the plurality of time periods.

13. The method of claim 11, wherein each time period of the plurality of time periods is relative to the start of a frame that is repetitively transmitted on the RF channel.

14. The apparatus of claim 13, wherein the link address further comprises an identifier that is matched with information in a header of the message before the message is forwarded to the at least one host.

15. The apparatus of claim 11, wherein the link address further comprises an identifier that is matched with information in a header of the message before the message is forwarded to the at least one host.

16. The apparatus of claim 11, further comprising:

logic configured to determine that the forwarding of information from the head end through the RF modem to the at least one host has terminated; and

logic configured to release the link address to the head end responsive to determining that the forwarding of information has terminated.

17. The apparatus of claim 16, wherein the logic configured to release the link address further comprises logic configured to send a DHCP packet from the RF modem to the head end.

18. The apparatus of claim 11, wherein the logic configured to receive the link address is further configured to receive the link address over a bidirectional link.

19. The apparatus of claim 18, wherein the bidirectional link is a PSTN link that is different from the RF connection.

20. The apparatus of claim 11, wherein the logic configured to receive a link address is further configured to receive the link address in a DHCP packet.

Patent Citations (174)

Patent	Date	Inventor	Cited By
US3985962(A)	1976-10-01	Jones et al.	Applicant
US4186380(A)	1980-01-01	Edwin et al.	Applicant
US4207431(A)	1980-06-01	McVoy	Applicant
US4361851(A)	1982-11-01	Asip et al.	Applicant
US4475123(A)	1984-10-01	Dumbauld et al.	Applicant
US4491983(A)	1985-01-01	Pinnow et al.	Applicant
US4528589(A)	1985-07-01	Block et al.	Applicant
US4536791(A)	1985-08-01	Campbell et al.	Applicant
US4577224(A)	1986-03-01	Ost	Applicant
US4601028(A)	1986-07-01	Huffman et al.	Applicant
US4633462(A)	1986-12-01	Stifle et al.	Applicant
US4641304(A)	1987-02-01	Raychaudhuri	Applicant
US4672533(A)	1987-06-01	Noble et al.	Applicant
US4757460(A)	1988-07-01	Bione et al.	Applicant
US4771391(A)	1988-09-01	Blasbalg	Applicant
US4804248(A)	1989-02-01	Bhagavatula	Applicant
US4823386(A)	1989-04-01	Dumbauld et al.	Applicant
US4858224(A)	1989-08-01	Nakano et al.	Applicant
US4907224(A)	1990-03-01	Scoles et al.	Applicant
US4912721(A)	1990-03-01	Pidgeon, Jr. et al.	Applicant
US4980886(A)	1990-12-01	Bernstein	Applicant
US5012469(A)	1991-04-01	Sardana	Applicant
US5014125(A)	1991-05-01	Pocock et al.	Applicant
US5047928(A)	1991-09-01	Wiedemer	Applicant
US5050213(A)	1991-09-01	Shear	Applicant
US5113499(A)	1992-05-01	Ankney et al.	Applicant
US5131041(A)	1992-07-01	Brunner et al.	Applicant
US5136690(A)	1992-08-01	Becker et al.	Applicant
US5142690(A)	1992-08-01	McMullan, Jr. et al.	Applicant
US5155590(A)	1992-10-01	Beyers, II et al.	Applicant
US5157657(A)	1992-10-01	Potter et al.	Applicant
US5159592(A)	1992-10-01	Perkins	Applicant
US5166930(A)	1992-11-01	Braff et al.	Applicant
US5166931(A)	1992-11-01	Riddle	Applicant
US5181107(A)	1993-01-01	Rhoades	Applicant
US5185860(A)	1993-02-01	Wu	Applicant
US5195092(A)	1993-03-01	Wilson et al.	Applicant
US5197094(A)	1993-03-01	Tillery et al.	Applicant
US5208665(A)	1993-05-01	McCalley et al.	Applicant
US5214390(A)	1993-05-01	Montreuil	Applicant
US5226120(A)	1993-07-01	Brown et al.	Applicant
US5235619(A)	1993-08-01	Beyers, II et al.	Applicant
US5239540(A)	1993-08-01	Rovira et al.	Applicant
US5251324(A)	1993-10-01	McMullan, Jr.	Applicant
US5261044(A)	1993-11-01	Dev et al.	Applicant
US5271041(A)	1993-12-01	Montreuil	Applicant
US5276789(A)	1994-01-01	Besaw et al.	Applicant
US5278833(A)	1994-01-01	Crisler et al.	Applicant
US5287351(A)	1994-02-01	Wall, Jr.	Applicant
US5295140(A)	1994-03-01	Crisler et al.	Applicant
US5295244(A)	1994-03-01	Dev et al.	Applicant
US5303234(A)	1994-04-01	Kou	Applicant
US5327554(A)	1994-07-01	Palazzi, III et al.	Applicant
US5333183(A)	1994-07-01	Herbert	Applicant
US5347304(A)	1994-09-01	Moura et al.	Applicant
US5361259(A)	1994-11-01	Hunt et al.	Applicant
US5384777(A)	1995-01-01	Ahmadi et al.	Applicant
US5390181(A)	1995-02-01	Campbell et al.	Applicant
US5404505(A)	1995-04-01	Levinson	Applicant
US5423003(A)	1995-06-01	Berteau	Applicant
US5423006(A)	1995-06-01	Brown et al.	Applicant
US5436909(A)	1995-07-01	Dev et al.	Applicant
US5440555(A)	1995-08-01	Momona	Applicant
US5471399(A)	1995-11-01	Tanaka et al.	Applicant
US5473599(A)	1995-12-01	Li et al.	Applicant
US5481542(A)	1996-01-01	Logston et al.	Applicant
US5483631(A)	1996-01-01	Nagai et al.	Applicant
US5504921(A)	1996-04-01	Dev et al.	Applicant
US5515361(A)	1996-05-01	Li et al.	Applicant
US5515418(A)	1996-05-01	Yamaguchi et al.	Applicant
US5517488(A)	1996-05-01	Miyazaki et al.	Applicant
US5517502(A)	1996-05-01	Bestler et al.	Applicant
US5517618(A)	1996-05-01	Wada et al.	Applicant
US5521925(A)	1996-05-01	Merakos et al.	Applicant
US5533108(A)	1996-07-01	Harris et al.	Applicant
US5534913(A)	1996-07-01	Majeti et al.	Applicant
US5535206(A)	1996-07-01	Bestler et al.	Applicant
US5535403(A)	1996-07-01	Li et al.	Applicant
US5553095(A)	1996-09-01	Engdahl et al.	Applicant
US5553287(A)	1996-09-01	Bailey et al.	Applicant
US5572640(A)	1996-11-01	Schettler	Applicant
US5586121(A)	1996-12-01	Moura et al.	Applicant
US5594798(A)	1997-01-01	Cox et al.	Applicant
US5604528(A)	1997-02-01	Edwards et al.	Applicant
US5608446(A)	1997-03-01	Carr et al.	Applicant
US5610910(A)	1997-03-01	Focsaneanu et al.	Applicant
US5612959(A)	1997-03-01	Takase et al.	Applicant
US5631903(A)	1997-05-01	Dianda et al.	Examiner
US5644706(A)	1997-07-01	Ruigrok et al.	Applicant
US5650994(A)	1997-07-01	Daley	Applicant
US5654746(A)	1997-08-01	McMullan, Jr. et al.	Applicant
US5675732(A)	1997-10-01	Majeti et al.	Applicant
US5701465(A)	1997-12-01	Baugher et al.	Applicant
US5703795(A)	1997-12-01	Mankovitz	Applicant
US5706277(A)	1998-01-01	Klink	Applicant
US5708655(A)	1998-01-01	Toth et al.	Applicant
US5708961(A)	1998-01-01	Hylton et al.	Applicant
US5710884(A)	1998-01-01	Dedrick	Applicant
US5712897(A)	1998-01-01	Ortel	Applicant
US5720025(A)	1998-02-01	Wilkes et al.	Applicant
US5721780(A)	1998-02-01	Ensor et al.	Applicant
US5724492(A)	1998-03-01	Matthews, III et al.	Applicant
US5729682(A)	1998-03-01	Marquis et al.	Applicant
US5737311(A)	1998-04-01	Wyld	Applicant
US5737316(A)	1998-04-01	Lee	Applicant
US5745837(A)	1998-04-01	Fuhrmann	Examiner
US5751706(A)	1998-05-01	Land et al.	Applicant
US5751707(A)	1998-05-01	Voit et al.	Applicant
US5751971(A)	1998-05-01	Dobbins et al.	Applicant
US5761602(A)	1998-06-01	Wagner et al.	Applicant
US5768280(A)	1998-06-01	Way	Applicant
US5790548(A)	1998-08-01	Sistanizadeh et al.	Applicant
US5790806(A)	1998-08-01	Koperda	Applicant
US5793753(A)	1998-08-01	Hershey et al.	Applicant
US5796718(A)	1998-08-01	Caterisano	Applicant
US5796742(A)	1998-08-01	Klotzbach et al.	Examiner
US5799002(A)	1998-08-01	Krishnan	Applicant
US5799016(A)	1998-08-01	Onweller	Applicant
US5805591(A)	1998-09-01	Naboulsi et al.	Applicant
US5805596(A)	1998-09-01	Kranzler et al.	Applicant
US5808671(A)	1998-09-01	Maycock et al.	Applicant
US5808886(A)	1998-09-01	Suzuki	Applicant
US5812819(A)	1998-09-01	Rodwin et al.	Applicant
US5815505(A)	1998-09-01	Mills	Examiner
US5815793(A)	1998-09-01	Ferguson	Examiner
US5818845(A)	1998-10-01	Moura et al.	Applicant
US5822319(A)	1998-10-01	Nagami et al.	Applicant
US5828655(A)	1998-10-01	Moura et al.	Applicant
US5828666(A)	1998-10-01	Focsaneanu et al.	Applicant
US5835696(A)	1998-11-01	Hess	Applicant
US5835725(A)	1998-11-01	Chiang et al.	Applicant
US5841468(A)	1998-11-01	Wright	Applicant
US5845091(A)	1998-12-01	Dunne et al.	Applicant
US5859852(A)	1999-01-01	Moura et al.	Applicant
US5881234(A)	1999-03-01	Scwob	Applicant
US5881243(A)	1999-03-01	Zaumen et al.	Applicant
US5884024(A)	1999-03-01	Lim et al.	Applicant
US5884284(A)	1999-03-01	Peters et al.	Applicant
US5892812(A)	1999-04-01	Pester, III	Applicant
US5894479(A)	1999-04-01	Mohammed	Applicant
US5898780(A)	1999-04-01	Liu et al.	Applicant
US5903572(A)	1999-05-01	Wright et al.	Applicant
US5905714(A)	1999-05-01	Havansi	Applicant
US5905736(A)	1999-05-01	Ronen et al.	Applicant
US5926476(A)	1999-07-01	Ghaibeh	Examiner
US5956338(A)	1999-09-01	Ghaibeh	Examiner
US5956391(A)	1999-09-01	Melen et al.	Applicant
US5959972(A)	1999-09-01	Hamami	Applicant
US5963551(A)	1999-10-01	Minko	Examiner
US5966163(A)	1999-10-01	Lin et al.	Applicant
US5999970(A)	1999-12-01	Krisbergh et al.	Applicant
US6012088(A)	2000-01-01	Li et al.	Examiner
US6018767(A)	2000-01-01	Fijolek et al.	Applicant
US6028860(A)	2000-02-01	Laubach et al.	Applicant
US6031846(A)	2000-02-01	Gurusami et al.	Examiner
US6032266(A)	2000-02-01	Ichinohe et al.	Applicant
US6049826(A)	2000-04-01	Beser	Applicant
US6052819(A)	2000-04-01	Barker et al.	Applicant
US6055224(A)	2000-04-01	King	Applicant
US6058421(A)	2000-05-01	Fijolek et al.	Applicant
US6065049(A)	2000-05-01	Beser et al.	Applicant
US6070246(A)	2000-05-01	Beser	Applicant
US6073178(A)	2000-06-01	Wong et al.	Applicant
US6178455(B1)	2001-01-01	Schutte et al.	Applicant
US6208656(B1)	2001-03-01	Hrastar et al.	Applicant
US6230203(B1)	2001-05-01	Koperda et al.	Applicant
US6236653(B1)	2001-05-01	Dalton et al.	Examiner
US6249523(B1)	2001-06-01	Hrastar et al.	Applicant
US6272150(B1)	2001-08-01	Hrastar et al.	Applicant
US6282208(B1)	2001-08-01	Bowcutt et al.	Applicant
US6286058(B1)	2001-09-01	Hrastar et al.	Applicant
US6295298(B1)	2001-09-01	Hrastar et al.	Applicant
US6334219(B1)	2001-12-01	Hill et al.	Examiner
US2002/0044570(A1)	2002-04-01	Gurusami et al.	Examiner

Non-Patent Literature (62)

PPP Bridging Control Protocol (BCP); F. Baker et al.; Network Working Group Request for Comments, Jun. 1994; pps. 1-28.Applicant
Data-Over Cable Services Interface Specifications; Cable Modem to Customer Premise Equipment Interface Specification; SP-CMCI-102-980317; 1988; Cable Television Laboratories, Inc.; pps. 1-40.Applicant
Data-Over Cable Service Interface Specifications; Cable Modem Telephony Return Interface Specification; SP-CMTRI-I01-970804; 1997; Cable Television Laboratories, Inc.; pps. 1-74.Applicant
Data-Over Cable Service Interface Specifications; Radio Frequency Interface Specification; SPRFIv1.1-101-990311; 1999; Cable Television Laboratories, Inc.: pps. 1-310.Applicant
Data-Over Cable Technical Reports; Operations Support System Framework for Data Over Cable Services; TR-DOCS-OSSIW08-961016; 1996; MCNS Holding, LP; pps. 1-20.Applicant
Data-Over Cable Service Interface Specifications; Operations Support System Interface Specification; SP-OSSI-102-990113; 1999; Cable Television Laboratories, Inc.; pps. 1-26.Applicant
Data-Over Cable Service Interface Specifications; Operations Support System Interface Specification Radio Frequency Interface; SP-OSSI-RFI-I03-990113; 1999; Cable Television Laboratories, Inc.; pps. 1-29.Applicant
Data-Over Cable Service Interface Specifications; Operations Support System Interface Specification Baseline Privacy Interface MIB; SP-OSSI-BPI-I01-980331; 1997 & 1998; MCNS Holdings, LP; pps. 1-33.Applicant
Data-Over Cable Service Interface Specifications; Radio Frequency Interface Specification SP-RFI-104-980724; 1997; Cable Television Laboratories, Inc.; pp. 1-196.Applicant
Radio Frequency (RF) Interface Management Information Base for MCNS Complaint RF Interfaces Draft-ietf-ipcdn-rf-interface-mib-04.txt; May 22, 1009; Guenter Roeck (editor); pps. 1-55.Applicant
Cable Device Management Information Base for MCNS Complaint Cable Modems and Cable Modem Termination Systems draft-ietf-ipcdn-cable-device-mib-04.txt; May 22, 1998; Guenter Roeck (editor); pps. 1-32.Applicant
Baseline Privacy Interface Management Information Base for MCNS Complaint Cable Modems and Cable Modem Termination Systems; R. Woundy; Jan. 17, 1999; pps. 1-35.Applicant
Logical IP Subnetworks over IEE 802.14 Services; Mark Laubach; Mar. 13, 1998; pps. 1-13.Applicant
A Distribute Queueing Random Access Protocol for a broadcast Channel; Wenxin Xu and Graham Campbell; Illinois Institute of Technology (Comp. Science Dept.); pps.1-9.Applicant
CBR Channels on a DQRAP-based HFC Network; Chien-Ting Wu, Graham Campbell; Illinois Institute of Technology (Comp. Science Dept.); pps. 1-14.Applicant
Interleaved DQRAP with Global TQ; Chien-Ting Wu, Graham Campbell; Illinois Institute of Technology (Comp. Science Dept.); pps. 1-27.Applicant
The Extended DQRAP (XDARAP) Algorithm; Chien-Ting Wu, Graham Campbell; Illinois Institute of Technology (Comp. Science Dept.); Dec. 9, 1994; pps. 1-4.Applicant
Extended DQRAP (EXQRAP) A Cable TEV Protocol Functioning as a Distributed Switch; Chien-Ting Wu & Graham Campbell; Illinois Institute of Technology (Comp. Science Dept.); pps.1-7.Applicant
A Review of Contention Resolution Algorithms for IEEE 802.14 Networks; Nada Glomie; Yves Saintillan, & David H. Su; National Institute of Standards and Technology; pps. 1-11.Applicant
A Review of Contention Resolution Algorithms for IEEE 802.14 Networks; Nada Glomie; Yves Saintillan, & David H. Su; National Institute of Standards and Technology; pps. 1-12.Applicant
On IEEE 802.14 Medium Access Control Protocol; Ying-Dar Lin; 1998; pps. 1-13.Applicant
On IEEE 802.14 Medium Access Control Protocol; Ying-Dar Lin; 1998; pps. 1-11.Applicant
On IEEE 802.14 Medium Access Control Protocol; Ying-Dar Lin; 1998; pps. 1-10.Applicant
Extended DQRAP (XDQRAP); Chien Ting Wu et al.; C. S. Dept., Ill. Inst. of Tech.; Jan. 8, 1995 pps. 1-4.Applicant
Hybrid-Fiber Coax; Hung Nguyen and Felix Yao; Apr. 22, 1996; pps. 1-11.Applicant
Cable Data Modem Performance Evaluation, A Primer for Non-Technical Readers; Cable Television Laboratories Inc.; Nov. 15, 1996; pps. 1-8.Applicant
High Speed Cable Modems, Including IEEE 802.14 Standards; Albert A. Azzam; Chapter 5, 6.Applicant
Cable Device Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems; Michael St. Johns; Mar. 30, 1999; pps. 1-54.Applicant
Radio Frequency (RF) Interfaces Management Information Base for MCNS/DOCSIS Compliant RF Interfaces; Mike St. Johns, (Editor); Feb. 17, 1999; pps. 1-67.Applicant
Telephony-Return Interface (TRI) Management Information Base for DOCSIS complaint Telephony-Return Cable Modems and Cable Modem Termination systems; S. Adiraju, J. Fijolek; Apr. 2, 1999; pps. 1-27.Applicant
Data Over Cable System Quality of Service Management Information Base (DOCSIS-QOS MIB); Mike Patrick; J. Harvey; Motorola ING; Jun. 25, 1999; pps. 1-43.Applicant
Docsis 1.1 IGMP MIB; H. Abramson, Motorola; Jun. 1999; pps. 1-13.Applicant
Publications and Technical Reports of Dolors Sala—Home Page; pps. 1-6.Applicant
Scheduling Disciplines for HFC Systems: What can we learn from ATM scheduling?; Dolors Sala, John O. Limb; GA Tech; pps. 1-12.Applicant
A Protocol for Efficient Transfer of Data over Fiber/Cable Systems; Dolors Sala, John O. Limb; GA Tech; pps. 1-16.Applicant
MAC Protocols for Multimedia Data over HFC Architecture; Dolors Sala Batlle; Oct. 27, 1995; pps. 1-28.Applicant
An Access Protocol to Support Multimedia Traffic Over Hybrid Fiber/Coax Systems; John O. Limb, Dolors Sala; pps. 1-6.Applicant
Simulation of the Performance of XDQRAP under a Range of Conditions; John O. Limb, Dolors Sala, Json Collins, David Hartman, Daniel Howard; pps. 1-10.Applicant
Interleaved DQRAP with Global TQ; Chien-Ting Wu, Graham Campbell; Illinois Institute of Technology, CS Dept.; Jan. 8, 1995; pps. 1-26.Applicant
Data Link Protocols; Uyless Black; Bell Atlantic Education Services; PTR Prentice Hall; New Jersey; 1993 pps. 141-159.Applicant
ATM Foundation for Broadband Networks; vol. 1; Ed. 2; Uyless Black; Prentice Hall; NJ; 1999; pp. 260-299.Applicant
The V Series Recommendations; Ed. 2; Uyless Black; McGraw-Hill, Inc.; 1995; pp. 169-184.Applicant
Frame Relay Networks; Ed. 2; Uyless Black; McGraw-Hill, Inc.; 1996; pp. 159-176.Applicant
ISDN; Ed. 2; Gary C. Kessler & Peter V. Southwick; McGraw-Hill, Inc.; 1997; pp. 111-128.Applicant
ISDN & SS7: Architecture for Digital Signaling Networks; Uyless Black; Prentice Hall; NJ; 1997; pp. 31-47.Applicant
ISDN and Broadband ISDN with Frame Relay and ATM; Ed. 4; William Stallings; Prentice Hall; NJ; 1999 pp. 181-343; pp. 312-343.Applicant
RFC 1541—Dynamic Host Configuration Protocol, R. Droms, Oct. 1993, found at URL http:/www.cis.ohiostate,edu/htbin/rfc/rfc 1541.html.Applicant
R. Droms; Dynamic Host Configuration Protocol; Oct. 1993; pps. 1-39.Applicant
W. Richard Stevens; TCP/IP Illustrated, vol. 1, The Protocols; Chapters 1, 2, 3, 4, 9, 11, 16.Applicant
T. Li et al.; Cisco Hot Standby Router Protocol (HSRP), RFC 2281, Mar. 1998, pps. 1-17, ftp://ftp.isi.edu/in-notes/rfc2281.txt.Applicant
Y. Rekhter et al., Address Allocation for Private Internets, RFC 1597, Mar. 1994, pps. 1-8, ftp://ftp.isi.edu/in-notes/rfc 1597.txt.Applicant
E. Lear et al., Network 10 Considered Harmful (Some Practices Shouldn't be Codified), Jul. 1994, pps. 1-8; ftp://ftp.isi.edu/in-notes/rfc 1627.txt.Applicant
E. Gerich, Unique Addresses are Good, RFC 1814, Jun. 1995, pps. 1-3, ftp://ftp.isi.edu/in-notes/rfc 1814.txt.Applicant
Y. Rekhter et al., Address Allocation for Private Internets, RFC 1918 Feb. 1996, pps. 1-8 ftp://ftp.isi.edu/in-notes/rfc1918.txt.Applicant
K. Egevang, The IP Network Address Translator (NAT), RFC 1631, May 1994, pps. 1-10, ftp://ftp.isi.edu/in-notes/rfc1631.txt.Applicant
P. Srisuresh et al., IP Network Address Translator (NAT) Terminology and Consideration, RFC 2663, Aug. 1999, pps. 1-30, ftp://ftp.isi.edu/in-notes/rfc2663.txt.Applicant
P. Srisuresh et al., Load Sharing using IP Network Address Translation (LSNAT), RFC 2391, Aug. 1998, pps. 1-18, ftp://ftp.isi.edu/in-notes/rfc2391.txt.Applicant
P. Srisuresh et al., DNS Extensions to Network Address Translators (DNS_ALG), RFC 2694, Sep. 1999, pps. 1-29, ftp://ftp.isi.edu/in-notes/rfc2694.txt.Applicant
P. Srisuresh, Security Model with Tunnel-mode IPsec for NAT Domains, RFC 2709, Oct. 1999, pps 1-11, ftp://ftp.isi.edu/in-notes/rfc2709.txt.Applicant
G. Tsirtsis et al., Network Address Translation—Protocol Translation (NAT-PT), RFC 2766, Feb. 2000, pps, 1-21, ftp://ftp.isi.edu/in-notes/rfc2766.txt.Applicant
E. Nordmark, Stateless IP/ICMP Translation Algorithm (SIIT), RFC 2765, Feb. 2000, pps. 1-26 ftp://ftp.isi.edu/in-notes/rfc2709.txt.Applicant
M. Allman et al., FTP Extensions for IPv6 and NATs, RFC 2428, Sep. 1998, pps. 1-8, ftp://ftp.isi.edu/in-notes/rfc2428.txt.Applicant

Abstract