US 6,671,741 B1Grant

Apparatus and method for hybrid network access

Issue Date:2003-12-30

•20 Claims

•10 Drawing Sheets

Abstract

A system in which a personal computer sends messages into a TCP/IP network using a conventional dial-up link and downloads data from the TCP/IP network using a high-speed one-way satellite link. A preferred embodiment uses a conventional SLIP provider to connect to the TCP/IP network and uses a commercial software TCP/IP package that has a standard driver interface. A spoofing protocol compensates for the long propagation delays inherent to satellite communication.

Metadata

Assignee

Hughes Electronics Corp.

Inventor

Douglas M. Dillon

Application Information

Application Number:US 09/722,488

Filing Date:2000-11-28

Priority Date:1994-06-08

Art Unit:7

Classifications

IPC:

G06F 1516

Field of Search:

709250709249709245709243709219709217709246709227

Patent Drawings (10 sheets)

Description

[0002] This application is a division of application Ser. No. 09/204,436 filed Dec. 3, 1998, U.S. Pat. No. 6,161,141, which is a division of application Ser. No. 08/901,152 filed Jul. 28, 1997, U.S. Pat. No. 5,995,725, which is a continuation of application Ser. No. 08/257,670 filed Jun. 8, 1994, now abandoned.

BACKGROUND OF THE INVENTION

[0003] This application relates to a computer network and, more specifically, to a method and apparatus for allowing both high-speed and regular-speed access to a computer network.

[0004] The Internet is an example of a TCP/IP network. The Internet has over 10 million users. Conventionally, access to the Internet is achieved using a slow, inexpensive method, such as a terrestrial dial-up modem using a protocol such as SLIP (Serial Line IP), PPP, or by using a fast, more expensive method, such as a switched 56 Kbps, frame relay, ISDN (Integrated Services Digital Network), or T1.

[0005] Users generally want to receive (download) large amounts of data from networks such as the Internet. Thus, it is desirable to have a one-way link that is used only for downloading information from the network. A typical user will receive much more data from the network than he sends. Thus, it is desirable that the one-way link be able to carry large amounts of data very quickly. What is needed is a high bandwidth one-way link that is used only for downloading information, while using a slower one-way link to send data into the network.

[0006] Currently, not all users have access to high speed links to networks. Because it will take a long time to connect all users to networks such as the Internet via physical high-speed lines, such as fiber optics lines, it is desirable to implement some type of high-speed line that uses the existing infrastructure.

[0007] Certain types of fast network links have long propagation delays. For example, a link may be transmitting information at 10 Mbps, but it may take hundreds of milliseconds for a given piece of information to travel between a source and a destination on the network. In addition, for even fast low-density links, a slow speed return-link may increase the round trip propagation time, and thus limit throughput. The TCP/IP protocol, as commonly implemented, is not designed to operate over fast links with long propagation delays. Thus, it is desirable to take the propagation delay into account when sending information over such a link.

SUMMARY OF THE INVENTION

[0008] The present invention overcomes the problems and disadvantages of the prior art by allowing a user to download data using a fast one-way satellite link, while using a conventional low-speed Internet connection for data being sent into the network. The invention uses a “spoofing” technique to solve the problem of the long propagation delays inherent in satellite communication.

[0009] In accordance with the purpose of the invention, as embodied and broadly described herein, the invention is a network system that forms a part of a network, comprising: a source computer, having a link to the network; a destination computer, having a link to the network; a satellite interface between the source computer and the destination computer, wherein information passes from the source computer to the destination computer; means in the destination computer for requesting information from the source computer over the network; means for receiving an information packet sent from the source computer in response to the request and for sending the information packet to the destination computer over the satellite interface; and means for sending an ACK message to the source computer in response to receipt of the information packet, wherein the ACK message appears to the source computer to have come from the destination computer.

[0010] In further accordance with the purpose of the invention, as embodied and broadly described herein, the invention is a gateway in a network system that forms a part of a TCP/IP network, wherein the network includes a source computer having a link to the TCP/IP network and a link to a high speed satellite interface, and a destination computer having a link to the TCP/IP network and a link to the high speed satellite interface, the gateway comprising: means for receiving an information packet sent from the source computer and for sending the information packet to the destination computer over the satellite interface; and means for sending an ACK message to the source computer in response to receipt of the information packet, wherein the ACK message appears to the source computer to have come from the destination computer.

[0011] Objects and advantages of the invention will be set forth in part in the description which follows and in part will be obvious from the description or may be learned by practice of the invention. The objects and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several embodiments of the invention and, together with the description, serve to explain the principles of the invention.

[0013] FIG. 1 is a hardware block diagram of a preferred embodiment of the invention;

[0014] FIG. 2 is a diagram of a portion of a hybrid terminal of FIG. 1;

[0015] FIG. 3 is a diagram showing an IP packet format;

[0016] FIG. 4 is a diagram showing a plurality of packet formats, including an Ethernet packet format;

[0017] FIG. 5 is a diagram showing a tunneling packet format;

[0018] FIG. 6 is a diagram of steps performed by the hybrid terminal of FIG. 1;

[0019] FIG. 7 is a diagram showing an example of partial data in a tunneling packet;

[0020] FIG. 8 is a flowchart of steps performed by the hybrid terminal of FIG. 1;

[0021] FIG. 9 is a diagram of steps performed by a hybrid gateway of FIG. 1;

[0022] FIG. 10 is a diagram showing a format of packets sent to a satellite gateway of FIG. 1;

[0023] FIG. 11 is a diagram showing a TCP packet format;

[0024] FIG. 12 is a ladder diagram showing packets sent from an application server to the hybrid gateway and from the hybrid gateway to the hybrid terminal over a satellite link; and

[0025] FIGS. 13(a) through 13(e) are flowcharts of steps performed by the hybrid gateway of FIG. 1.

[0026] FIGS. 14 and 15 are figures from the Phase A Data Sheet incorporated herein.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] Reference will now be made in detail to the preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

a. General Overview

[0028] A preferred embodiment of the present invention uses satellite technology to implement a high-speed one way link between a user's computer and a TCP/IP network, such as the Internet or a private TCP/IP network. This high-speed link is used to download data from the network. The user's computer also has a conventional TCP/IP link for sending data to the network. The invention can use various forms of high-speed, one-way links, such as satellites, and cable television lines. The invention can use various forms of low-speed networks, such as TCP/IP networks, dial-up telephones, ISDN D-channel, CPDP, and low-speed satellite paths.

[0029] The described embodiment of the present invention uses satellites to provide a high-speed one-way link. Satellites can cover large geographical areas and are insensitive to the distance between a transmitter and a receiver. In addition, satellites are very efficient at point-to-point and broadcast applications, and are resilient and resistant to man-made disasters. Two-way satellites are expensive to use, however, because of the costs involved in purchasing and installing satellite earth station hardware. In the past, these costs have placed satellite communications outside the reach of the consumer.

[0030] The present invention allows a personal computer to receive downloaded information from the network via a satellite at a very practical cost. In the present invention, the cost of satellite communications is reduced because a one-way satellite link is used. Receive-only earth station equipment is cheaper to manufacture because it requires less electronics than send/receive antennae.

[0031] As is well-known in the art, communication over the Internet and similar TCP/IP networks is achieved through a group (suite) of protocols called Transmission Control Protocol/Internet Protocol (TCP/IP). The TCP/IP protocol is described in the book “Internetworking With TCP/IP, Vol I” by Douglas Comer, published by Prentice-Hall, Inc., of Englewood Cliffs, N.J., 1991, which is incorporated by reference.

b. Hybrid TCP/IP Access

[0032] FIG. 1 is a hardware block diagram of a preferred embodiment of the invention. FIG. 1 includes five subsystems: a hybrid terminal 110, a SLIP provider (Internet connection) 130, an application server 140, a hybrid gateway 150, and a satellite gateway 160. Hybrid terminal 110 is connected to a modem 190, e.g., a 9600 baud modem, which connects to SLIP provider 130 through a telephone line 192. A satellite transmitter 170, a satellite 175, and a satellite receiver 180 provide a fast, one-way link for transferring data from satellite gateway 160 to hybrid terminal 110. Each of SLIP provider 130, application server 140, and hybrid gateway 150 are connected to the Internet 128. As is well-known in the art, the Internet 128 is a “network of networks” and can be visually depicted only in general terms, as seen in FIG. 1.

[0033] Each of hybrid terminal 110, SLIP provider 130, application server 140, hybrid gateway 150 and satellite gateway 160 includes a processor (not shown) that executes instructions stored in a memory (not shown). Other parts of the invention also include processors that are not discussed herein, such as I/O processors, etc. Preferably, hybrid terminal 110, hybrid gateway 150, and satellite gateway 160 are implemented as personal computers including an 80386/80486 based personal computer operating at least 33 MHz, but these elements can be implemented using any data processing system capable of performing the functions described herein. In the described embodiment, SLIP provider 130 is a conventional SLIP provider and application server 140 is any application server that can connect to the Internet 128 via TCP/IP.

[0034] As shown in FIG. 1, hybrid terminal 110 preferably includes application software 112, driver software 114, a serial port 122 for connecting hybrid terminal 110 to modem 190, and satellite interface hardware 120 for connecting hybrid terminal 110 to satellite receiver 180.

[0035] FIG. 2 shows a relationship between software in application 112, software in driver 114, serial port 122, and satellite interface 120. Application software 112 includes TCP/IP software, such as SuperTCP, manufactured by Frontier, Inc., Chameleon, manufactured by Netmanager, and IRNSS, manufactured by Spry, Inc. The described embodiment preferably operates with the SuperTCP TCP/IP package and, thus, uses a standard interface 212 between the TCP/IP software 210 and driver 114. Examples of standard interface 212 between TCP/IP software 210 and driver 114 includes the Crynson-Clark Packet Driver Specification and the 3Com/Microsoft Network Driver Interface Specification (NDIS). Other embodiments use other standard or non-standard interfaces between TCP/IP software 210 and driver 114.

[0036] As shown in FIG. 2, application software preferably 112 also includes well-known Internet utilities, such as FTP 230, and well-known user interfaces, such as Mosaic and Gopher (shown). Application software 112 can also include other utilities, e.g., News and Archie (not shown).

[0037] The following paragraphs describe how a request from hybrid terminal 110 is carried through the Internet 128 to application server 140 and how a response of application server 140 is carried back to the user at hybrid terminal 110 via the satellite link. The operation of each subsystem will be described below in detail in separate sections.

[0038] In the present invention, hybrid terminal 110 is given two IP addresses. One IP packet address corresponds to SLIP provider 130 and is assigned by a SLIP service provider. The other IP address corresponds to satellite interface 120 and is assigned by a hybrid service provider. IP addresses are assigned by the SLIP and satellite network managers and loaded into hybrid terminal 110 as part of an installation configuration of the hybrid terminal's hardware and software. These two IP addresses correspond to completely different physical networks. SLIP provider 130 does not “know” anything about the satellite IP address or even whether the user is using the satellite service. If a host somewhere in the Internet is trying to deliver a packet to the satellite interface IP address by using the Internet routing scheme of routers, gateways, and ARPs (Address Resolution protocol), the only way that the packet can reach the satellite IP interface is to traverse the satellite by being routed through satellite gateway 160.

[0039] The following example assumes that a user at hybrid terminal 110 desires to send a request to a remote machine, such as application server 140, that is running FTP (File Transfer protocol) server software. The FTP software running on application server 140 receives file transfer requests and responds to them in an appropriate fashion.

[0040] FIG. 3 shows the contents of a source field (SA) and of a destination field (DA) of packets sent between the elements of FIG. 1. A request for a file and a response of a file sent from application server 140 to hybrid terminal 110 takes the following path.

[0041] 1) Within hybrid terminal 110, FTP client software 230 generates a request and passes it to TCP/IP software 210. TCP/IP software 210 places the request in a TCP packet (see FIG. 11). Next, the TCP packet is placed in an IP packet, having a format shown in FIG. 3. TCP/IP software 210 places the IP packet in an Ethernet packet, as shown in FIG. 4, and passes the Ethernet packet to driver 114. This packet has a source IP address corresponding to satellite interface 120 and a destination IP address of application server 140.

[0042] 2) In driver 114, the Ethernet header and checksum are stripped off the packet and the IP packet is encapsulated, or “tunneled,” inside of another IP packet and sent over serial port 122 to SLIP provider 130. FIG. 5 shows a format of a tunnelled packet. FIG. 7 shows an example of a tunnelled packet. The encapsulation adds a new IP header 530 in front of the original packet 540 with a source address corresponding to SLIP provider 130 and a destination address corresponding to hybrid gateway 150.

[0043] 3) SLIP provider 130 receives the IP packet, analyzes the tunneling header and, thinking it is destined for hybrid gateway 150, uses standard Internet routing to send the packet to hybrid gateway 150.

[0044] 4) When hybrid gateway 150 receives the packet, it strips off the tunneling header, revealing the true header with application server 140 as the destination. The packet is then sent back out into the Internet 128.

[0045] 5) Internet routing takes the packet to application server 140, which replies with the requested file and addresses the reply to the request's source IP address, i.e., the IP address of the hybrid terminal's satellite interface 120.

[0046] 6) In order to find the hybrid terminal's satellite interface 120, the Internet routing protocol will send the packet to the subnet containing a router/gateway connected to hybrid gateway 150. When a router on the same physical network as satellite gateway 160 and hybrid gateway 150 sends out an ARP for the IP address of satellite interface 120 (to find a physical address of satellite interface 120), hybrid gateway 150 responds and says “send it to me.” Thus, application server 140 and the rest of the Internet 128 think that packets sent to hybrid gateway 150 will reach the hybrid terminal's satellite interface.

[0047] 7) Once hybrid gateway 150 receives a reply packet from application server 140, it sends it to satellite gateway 160. In the described embodiment, hybrid gateway 150 encapsulates the packet in a special packet format that is used over the satellite link and uses the satellite interface IP address to uniquely identify the satellite packet's destination. Then hybrid gateway 150 sends the packet over the Ethernet to satellite gateway 160.

[0048] 8) Satellite gateway 160 broadcasts over the satellite link any packets it receives from hybrid gateway 150.

[0049] 9) Driver 114 in hybrid terminal 110 that services satellite interface 120 scans all packets broadcast over satellite transmitter 170 looking for its satellite interface IP address in the header. Once it identifies one, it captures it, strips off the satellite header revealing the reply IP packet, and sends it to driver 114.

[0050] Thus, IP packets sent into Internet 128 are carried by the SLIP connection, while IP packets from the Internet 128 are carried by the satellite link. The following paragraphs describe the operation of each subsystem in more detail.

[0051] 1. The Hybrid Terminal

[0052] Hybrid terminal 110 is the terminal with which the user interacts. Thus, hybrid terminal 110 includes a user interface device (not shown) such as a mouse, keyboard, etc. As shown in FIG. 1, hybrid terminal 110 includes one or more application programs 112 (including TCP/IP software 210), and driver software 114, which communicates with SLIP provider 130 through a serial port 122 and modem 190, using a driver portion 118, and which communicates with satellite receiver 180 through a satellite interface 120, using a driver portion 116.

[0053] To TCP/IP software 210, driver 114 appears to be an Ethernet card, although driver 114 is actually connected to satellite receiver 180 (via satellite interface 120) and to SLIP provider 130 (via serial line 122 and modem 190). Thus, TCP/IP software 210 believes that it is communicating with a single physical network, when it is, in reality, communicating with two physical networks (the SLIP dial-up network and a satellite network). Ethernet is a packet switching protocol standardized by Xerox Corporation, Intel Corporation, and Digital Equipment Corporation, which is described in “The Ethernet: A Local Area Network Data Link Layer and Physical Layer Specification,” September 1980, which is available from any of these three companies, and which is incorporated by reference.

[0054] FIG. 6 is a diagram of steps performed by driver 114 of hybrid terminal 110 of FIG. 1. As shown in FIG. 6, driver 114 receives packets of data from TCP/IP software 210 and passes them to SLIP provider 130 via serial port 122 and modem 190. A packet sent by application server 140 is received through satellite receiver 180, passed through the satellite interface 120, passed to the satellite driver 220, and passed to driver 114, which passes the received packet to TCP/IP software 210.

[0055] The following paragraphs discuss two basic functions performed by driver 114 (tunneling and ARP handling) and discuss various implementation details for the preferred embodiment.

A. “TUNNELING”

[0056] As discussed above, hybrid terminal 110 has two IP addresses associated with it: one for SLIP provider 130 and one for the satellite interface 120. Packets containing requests are sent from hybrid terminal 110 to application server 140 via the Internet 128, while packets containing a reply are sent back via the satellite link. Tunneling is the method by which application server 140 is “fooled” into sending a reply to a different IP address (satellite interface 120) than that of the sender (serial port 122).

[0057] A packet received by driver 114 from the TCP/IP software 210 has a source address of satellite gateway 160 and a destination address of application server 140. As shown in step 610 of FIG. 6, driver 114 removes the Ethernet header and checksum and encapsulates the IP header into an IP tunneling header having a source address of SLIP provider 130 and a destination address of hybrid gateway 150 (see FIG. 7). As described above, at hybrid gateway 150, the tunneling header is removed and the packet is sent back into the Internet 128 to be sent to application server 140.

[0058] When forming a tunneling header, driver 114 copies all the values from the old header into the new one with the following exceptions. The source and destination addresses of the tunneling header change, as described above. In addition, a total packet length field 510 is changed to contain the contents of length field 310 plus the length of the tunneling header. Lastly, the driver 114 recalculates checksum 520 of the tunneling header because some of the fields have changed.

B. ARP HANDLING

[0059] ARP (Address Resolution Protocol) is used by TCP/IP to dynamically bind a physical address, such as an Ethernet address, to an IP address. When TCP/IP finds an IP address for which it does not know a physical address, TCP/IP broadcasts an ARP packet to all nodes, expecting a response that tells TCP/IP what physical address corresponds to the IP address.

[0060] During initialization, driver 114 declares to TCP/IP software 210 that driver 114 is an Ethernet card to ensure that the packets that TCP/IP package sends are Ethernet packets and that the TCP/IP package will be prepared to receive packets at a high-rate of speed. As shown in step 620 of FIG. 6, when driver 114 detects that TCP/IP has sent an ARP packet, driver 114 creates a physical address and sends a reply packet to TCP/IP software 210. The contents of the physical address are irrelevant, because driver 114 strips off the Ethernet header on packets from TCP/IP before the packets are sent to SLIP provider 130.

C. OTHER FUNCTIONS

[0061] As shown in step 630 of FIG. 6, packets received by driver 114 from satellite receiver 180 (via satellite driver 114) are merely passed to TCP/IP software 210. The following paragraphs discuss implementation details for the described embodiment.

[0062] In a preferred embodiment, TCP/IP software 210 (e.g., Frontier's SuperTCP) sends an ACK (acknowledge) for every packet it receives, even though this action is not required by the TCP/IP protocol. In this situation, many packets compete for the slow link to SLIP provider 130. In TCP/IP, the ACK scheme is cumulative. This means that when a transmitter receives an ACK stating that the receiver has received a packet with sequence number N, then the receiver has received all packets with sequence numbers up to N as well, and there is no reason why every packet needs to be ACK'ed.

[0063] FIG. 8 is a flowchart of steps performed in a preferred embodiment by driver 114 of hybrid terminal 110. FIG. 11 is a diagram showing preferred a TCP packet format. FIG. 11 includes a sequence number field 1102, an acknowledgment (ACK) number field 1104, and a checksum field 1106. In step 810 of FIG. 8, driver 114 receives an ACK packet with sequence number N from TCP/IP software 210. The packet is queued along with other packets waiting to be sent to SLIP provider 130. In step 820 driver 114 checks to determine whether there is a “run” of sequential packets waiting to be sent. If so, in step 830, driver 114 deletes ACK packets for the same TCP connection that have sequence numbers in the run from the queue and sends an ACK only for the highest sequence number in the run. This action alleviates the bottleneck caused by the relatively slow modem speeds.

[0064] Serial port 122 provides a physical connection to modem 190 and, through it, to the terrestrial network via a SLIP protocol as described below in connection with SLIP provider 130. Serial data is sent and received through an RS-232 port connector by a UART (Universal Asynchronous Receiver Transmitter), such as a U8250, which has a one byte buffer and is manufactured by National Semiconductor, or a U16550, which has a 16 byte buffer and is also manufactured by National Semiconductor.

[0065] The invention preferably operates under the DOS operating system and Windows, but also can operate under other operating systems.

[0066] Satellite driver software 220 receives packets from satellite 180, and passes them to driver 114 using a DOS call. Thus, the two physical links are combined within driver 114 and the existence of two physical links is transparent to TCP/IP software 210. Satellite driver 220 scans all packets transmitted over the satellite channel for a packet with a header corresponding to the IP address of the satellite interface 122, performs some error detection and correction on the packet, buffers the received packet, and passes the packet to driver 114 using a DOS call, e.g., IOCTL-output-cmd( ). Driver 114 copies data from satellite driver 220 as quickly as possible and passes it to TCP/IP software 210.

[0067] As discussed above, TCP/IP software 210 is fooled into thinking that it is connected to an Ethernet network that can send and receive at 10 Mbps. This concept is helpful on the receive side because data from the satellite is being received at a high rate. On the transmit side, however, modem 190 is not capable of sending at such a high rate. In addition, TCP/IP software 210 sends Ethernet packets to driver 114, i.e., an IP packet is encapsulated into an Ethernet packet. Because SLIP provider 130 expects IP packets, driver 114 must strip the Ethernet header before the packet is sent to SLIP provider 130.

[0068] As described above in connection with FIG. 8, driver 114 also includes a transmit and receive queue. As data is received from TCP/IP software 210 and received from the satellite driver 220, it is buffered within the queue. When the queue is full, e.g., when TCP/IP is sending packets faster than modem 190 can send them, driver 114 drops the packets and returns an error so that TCP/IP software 210 will decrease its rate of transmission.

[0069] In a first preferred embodiment, a SLIP connection is initiated with an automatic logon procedure. In another preferred embodiment, driver 114 executes instructions to allow a user to perform a SLIP logon manually.

[0070] Because TCP/IP software 210 preferably is configured to talk to Ethernet and it is desirable to receive the largest packet size possible, driver 114 configures TCP/IP so that the MTU (Maximum Transmission Unit) of the network is as large as possible, e.g., 1500 bytes. Some SLIP providers 130 have a smaller MTU, e.g., 512 bytes. To handle the disparity in size, driver 114 segments large packets received from TCP/IP software 210 into segments the size of the SLIP MTU. Once a packet is segmented, it is reassembled in hybrid gateway 150. Only the tunneling header is copied as the header of the segments.

[0071] 2. The SLIP Provider

[0072] SLIP provider 130 performs the function of connecting hybrid terminal 110 to the Internet 128. As described above, other protocols, such as PPP, could also be used to perform the connecting function. SLIP server 130 receives SLIP encoded IP packets from modem 190, uncodes them, and forwards them to hybrid gateway 150 via the Internet 128.

[0073] In its most basic form, SLIP provider 130 delimits IP packets by inserting a control character hex 0×C0 between them. To insure that a data byte is not mistaken for the control character, all outgoing data is scanned for instances of the control character, which is replaced by a two character string. The SLIP protocol is described in detail in J. Romkey, “A Nonstandard for Transmission of IP Datagrams over Serial Lines: SLIP,” RFC 1055, June 1988, pp. 1-6, which is incorporated by reference.

[0074] 3. The Application Server

[0075] Application server 140 is a computer system running any combination of known application programs available on the Internet using the TCP/IP protocol suite. For example, application server 140 may be transferring files to requesting users via FTP. Although hybrid terminal 110 Actually has two IP addresses (a serial port address and an address for the satellite interface), the software executing on application server 140 thinks that it is receiving requests over the satellite network and sending responses over the satellite network. Hybrid terminal is completely transparent to application server 140.

[0076] 4. The Hybrid Gateway

[0077] Although only one hybrid terminal 110 is shown in FIG. 1, the invention can include a plurality of hybrid terminals 110. Preferably, all packets sent from all hybrid terminals 110 pass through hybrid gateway 150 to get untunnelled. Thus, hybrid gateway 150 is a potential system bottleneck. Because of this potential bottleneck, the functions of hybrid gateway 150 are as simple as possible and are performed as quickly as possible. Hybrid gateway 150 also has good Internet connectivity to minimize the accumulated delay caused by packets waiting to be processed by hybrid gateway 150.

A. UNTUNNELLING

[0078] FIG. 9 is a diagram of steps performed by hybrid gateway 150 of FIG. 1. In step 910, hybrid gateway 150 receives a tunneled packet having a format shown in FIG. 5. Hybrid gateway 150 “untunnels” the packet by stripping off the tunneling header and passes the packet back to the Internet 128.

[0079] As described above, packets are sometimes broken into segments when they are sent in order to accommodate a small MTU of SLIP provider 130. Packets may also be segmented as they pass through other elements of the Internet 128 having small MTUs. For fragmented packets, only the tunnelled header is copied into the header of each segment. Hybrid gateway 150 stores fragmented packets in a memory (not shown) and reassembles them in order before untunnelling the original packet and passing it to the Internet 128. Preferably, a “time to live” value is assigned to each packet when it is sent by driver 114 and if all segments do not arrive before a time to live timer expires, the packet is discarded.

B. ARP RESPONDING

[0080] Preferably, satellite gateway 160 is on a same physical network as hybrid gateway 150. As shown in step 920 of FIG. 9, when a router on the same physical network as satellite gateway 160 and hybrid gateway 150 sends out an ARP for the IP address of satellite interface 120 (to find a physical address of satellite interface 120), hybrid gateway 150 responds and says “send it to me.” Hybrid gateway 150 needs to intercept packets intended for satellite interface 120 because it needs to encapsulate packets for satellite gateway 160 as follows.

C. SATELLITE PACKETIZING

[0081] The following paragraphs describe how packets travel from application server 140 through hybrid gateway 150 and to satellite gateway 160. The following explanation is given by way of example and is not intended to limit the scope of the present invention. As shown in step 930 of FIG. 9, hybrid gateway 150 encapsulates replies from application server 140 into a satellite packet format. FIG. 10 is a diagram showing a format of a satellite packet sent to satellite gateway 160 of FIG. 1. A satellite packet includes the data 1010 of an original IP packet and two headers 1020, 1030 added by hybrid gateway 150.

[0082] Satellite gateway 160 expects IP packets to be encapsulated first in a special satellite packet and then within an LLC-1 IEEE 802.2 link level control, type 1 packet. Satellite header 1020 identifies the downlink and contains a sequence number and the packet length. An LLC-1 header 1030 preferably is used to send the packet to satellite gateway 160, in an Ethernet LAN. Hybrid gateway 150 prepares packets for satellite gateway 160 by appending headers 1020 and 1030 to the front of an IP packet 1010.

[0083] The receiver in hybrid terminal 110 does not receive the LLC-1 header 1030. Hybrid terminal 110 identifies packets intended for it by checking a least significant byte in the satellite IP address. Thus, a six byte satellite destination address is determined by reversing an order of bytes of the satellite IP address for hybrid terminal 110 and then padding the rest of the address with zeroes.

[0084] 5. The Satellite Gateway

[0085] Satellite gateway 160 can include any combination of hardware and software that connects satellite transmitter 170 to hybrid gateway 150. Satellite transmitter 170 and satellite receiver 180 can be any combination of hardware and software that allows data to be transmitted by satellite transmitter 170 and received by satellite receiver 180, and to be input to hybrid terminal 110. For example, satellite gateway 160 preferably is a personal computer with a high-speed Ethernet connection to hybrid terminal 110. When satellite gateway 160 receives a packet from hybrid gateway 150, it sends it over the satellite link.

[0086] Satellite communication may be effected by, for example, the Personal Earth station manufactured by Hughes Network Systems Inc. In a preferred embodiment, a one-way version of the Personal Earth Station is used. Another embodiment uses a satellite communication system manufactured by Comstream. Yet another embodiment uses a system that allows hybrid terminal 110 to be connected directly to satellite receiver 180 via Hughes Network Systems' DirecPC product. The DirecPC satellite interface card is described in “DirecPC, Phase A Data Sheet,” dated Jun. 7, 1993, which is incorporated by reference and by the inclusion of its contents which read as follows:

[0087] “DirecPC is a satellite, one-way broadcast network offering three services to the IBM compatible PC:

[0088] 1. Digital package delivery—Software, games, multi-media news, electronic documents and any other data in the form of a collection of PC files are made available to the PC on a scheduled or on-demand basis.

[0089] 2. Data Pipe—provides multiple independent digital streams to carry video, audio, etc.

[0090] 3. Hybrid Internet Access—high-speed, low-cost Internet connection where DirecPC carries packets from the Internet and dial-up modem carries packets into the Internet.

[0091] See FIG. 14.

[0092] To receive the DirecPC broadcast, a PC is equipped with a PC plug-in card and a 24 inch antenna. DirecPC uses a full Galaxy class Ku-Band transponder to provide an 11 Mbps broadcast channel. DES encryption based conditional access ensures that a receiver PC may only access data it is authorized to receive.

[0093] Section 1 PC User Perspective

[0094] The PC hardware consists of the DirecPC adapter, an antenna and a TVRO standard coaxial cable. The DirecPC adapter is a 16-bit ISA adapter providing throughput comparable to a 16-bit ISA ethernet adapter.

[0095] The software appears to the user as a set of Windows applications. The applications:

[0096] assist installation and service registration.

[0097] support package delivery by allowing the user to select packages for reception, be notified when packages are received. The software also supports billing for packages received.

[0098] provide a TCP/IP protocol stack and set of applications for Hybrid Internet access.

[0099] provide a driver DLL on which third party software may layer data pipe applications.

[0100] The software for a data pipe service is provided by the enterprise providing the service. Communications back to the uplink is required for billing purposes and also for Hybrid Internet access. These communications take place via the PC's dial-up AT command-set modem.

[0101] Section 2 Open Interfaces And APIs

[0102] The DirecPC architecture is open, allowing content providers complete control over their content and the user interface to their content. DirecPC provides interfaces to content providers at the uplink and Application Programming Interfaces (APIs) on the receiving PC. The specifications and APIs are available on request.

[0103] See FIG. 15.

[0104] Section 3 Content Providers

[0105] A content provider is an organization that supplies the data sent over the DirecPC system. A content provider can be categorized as being either a:

[0106] 1. Package Publisher—uses the DirecPC system as a means of selling and distributing software packages or data packages where a package consists of a set of PC files.

[0107] 2. Data Pipe Provider—uses the DirecPC system as a data pipe transport mechanism. User services (News Feeds, Internet Access, Broadcast Video and Audio, etc.) are layered on top of a datagram transport.

[0108] DirecPC supports multiple content providers of both kinds.

[0109] Section 4 DirecPC Package Distribution

[0110] The DirecPC system allows data packages to be distributed and purchased. The term “package” refers to any data (including electronic documents, multi-media data, software packages, games, etc.) which can take the form of a group of PC files.

[0111] To prepare a package for transmission, a publisher merges the package's files into a single file using the appropriate utility (e.g. PKZIP or ARJ) and loads the package into the uplink using an off-the-shelf file transfer mechanism (e.g. TCP/IP's FTP, floppy-disk, CD-ROM, X-Modem, etc.). Scheduling, pricing and conditional access restrictions can be performed either manually or automatically under publisher control when the package is loaded into the uplink.

[0112] DirecPC's conditional access mechanism ensures that a user may only receive authorized packages. As part of initial registration, the user is provided a credit limit. The PC locally maintains a credit account. When the user selects a package for reception, the PC records the transaction and debits the account. A log of all package receptions is maintained on the PC's hard disk and can be browsed by the graphical front-end.

[0113] On uplink operator command, when the local credit limit is exceeded or when the user has purchased a certain number of packages, the PC makes a dial-up call to the DirecPC billing service. The call reports the billing information as well as usage information of packages received.

[0114] The usage information is used to provide feedback for future scheduling of packages. The reports given to publishers include for each package reception, the name, address etc. of the recipient, the ID of the package and when package delivery took place.

[0115] A software package may either be transmitted on a scheduled basis or on-demand. Scheduled transfers are perfect for:

[0116] 1. Periodical Distribution—examples include news and weather updates, electronic newspaper, magazine and catalog distribution.

[0117] Popular Package Delivery—packages for which there are expected to be multiple recipients. The most popular (or highest profit) packages would be scheduled more frequently to reduce the average time spent waiting, while less popular packages may be scheduled for overnight delivery. Scheduled delivery is lower cost than delivering a package on-request to each buyer. The schedule for individual packages is manually set by hub operators with the submission of the package.

[0118] Phase A package delivery allows a single transmission at any given time. The rate of transmission is settable under operator control at speeds up to 2 Mbits/sec. Support for simultaneous transmissions will be provided in a subsequent release of DirecPC software.

[0119] A software package may be transmitted on-demand in the gaps between scheduled transmissions. Such a transfer delivers the information more quickly to the requesting PC, but at greater cost as the package is not broadcast. A PC uses its modem to request the package.

[0120] DirecPC's low bit error rate and high availability ensure that packages are reliably delivered with one transmission. For even grater reliability, each package may be set to employ one or more of the following methods to ensure fail-safe delivery:

[0121] 1. Repeated Transmission—A package may be scheduled to be sent more than once to ensure its delivery. A receiving PC, if any packets are lost on the first transmission, fills in the gaps on subsequent transmissions. This mechanism ensures extremely high probability of delivery without requiring use of a return link.

[0122] 2. Retransmission requests—a PC, if it misses parts of a package, may request retransmission of those parts. The missing parts are multi-cast so that parts need only be retransmitted once even though they were missed by multiple PCS. Retransmission requests are most appropriate for scheduled individual package transmissions where the package is scheduled less frequently.

[0123] 3. Delivery confirmation—a PC, after successfully receiving and installing a package, may send a confirmation to the hub. These confirmations are tabulated and provided in the form of reports to the publisher. This method is more expensive in that it requires that a delivery confirmation (entailing a separate call) be sent by every receiving PC.

[0124] Section 5 Data Pipe Transmission

[0125] DirecPC's data pipe services are modelled on Local Area Network multi-cast transmission. The data pipe provider passes 802.2 LLC1 Token-Ring or Ethernet multi-cast packets to the uplink. This allows off-the-shelf bridges and routers to be used to support a terrestrial backhaul. It also allows some LAN based applications to operate across the spacelink with little or no modification. The uplink relays these packets across the spacelink. The DirecPC driver passes received packets to the applications. To prevent unauthorized access, each multi-cast address is encrypted under a different key. The DirecPC device driver API allows applications to designate which multi-cast addresses are of interest. Hardware filtering in the DirecPC adapter allows the reception of any 100 different multi-cast addresses.

[0126] DirecPC network management allocates to each service provider:

[0127] 1. a Committed Information Rate (CIR)—a fraction of broadcast channel bandwidth which is guaranteed to the data pipe provider, and

[0128] 2. one or more multi-cast 48 bit addresses—each address operates as a separate data stream multiplexed on the one broadcast channel.

[0129] Section 6 Hybrid Internet Access

[0130] Hybrid Internet access allows a PC high-speed (over 100 Kbps) access to the Internet. An HNS (Hughes Network Systems) provided NDIS device driver operates with an off-the-shelf TCP/IP package. Reception from the Internet takes place via DirecPC. Transmission into the Internet takes place via a dial-up SLIP connection into the uplink. Hybrid Internet Access allows operation of all the standard Internet applications including SMTP EMAIL, NNTP Usenet News, FTP, GOPHER and Mosaic. As part of initial registration, each receiving PC is provided a permanently assigned IP address.

[0131] Hybrid Internet Access is the result of joint development by HNS and the University of Maryland funded in part by a MIPs grant. Continuing development will increase performance and allow receive-only reception of Usenet News.

[0132] Section 7 Performance Specifications

[0133] Averaged across a whole year, each DirecPC receiver should be expected to have a BER less than 10E-10 more than 99.5% of the time where a single bit error causes the loss of an entire packet.

[0134] Section 8 User Characteristics

[0135] The receiver (antenna, cabling and PC plug-in card) is intended to be self-installable by consumers and small business. In cases where self-installation is not desirable, the DirecPC adapter will be installed by the customer and the antenna and cable will be installed by the HNS VSAT installers. The customer uses diagnostic software provided with the adapter to ensure that the PC as a whole is ready for the antenna to be installed.

[0136] Maintenance will be performed either by the user swapping components (DirecPC adapter, LNB, etc. with telephone support). HNS's nationwide VSAT field-service network may also be contracted for.”

[0137] At the downlink, satellite receiver 180 includes a 0.6 meter receive-only antenna receiving HDLC encapsulated LAN packets. Satellite interface 120 includes rate 2/3 Viterbi/Reed-Soloman concatenated forward error correction.

[0138] Although only one hybrid terminal 110 and one application server 140 are shown in FIG. 1, the invention can include a plurality of hybrid terminals 110 and/or a plurality of application servers 140. Preferably, all packets sent from all application servers 140 to a hybrid interface 110 pass through satellite gateway 160. Thus, satellite gateway 160 is a potential system bottleneck. Because of this potential bottleneck, the functions of satellite gateway 160 are as simple as possible and are performed as quickly as possible.

c. Protocol Spoofing

[0139] TCP/IP protocol specifies that only a predetermined number of packets can be outstanding during transmission, i.e., that only a limited number of packets can be sent before an ACK (acknowledgment) is received. The high bandwidth and long delays incurred in sending packets to an orbiting satellite and back means that at any given time, a large number of packets are “in the pipe” between transmitter and receiver.

[0140] When using conventional TCP/IP protocol, application server 140 sends a predetermined number of packets in accordance with a predetermined window size, and then waits to receive ACKs over the modem link before sending additional packets. The purpose of windowing is to limit a number of packets that must be re-sent if no ACK is received and to provide flow control, e.g., to prevent sending packets faster than they can be received. The packets that have not been ACK'ed are stored in a memory so that they can be re-sent if no ACK is received.

[0141] In a preferred embodiment of the present invention, hybrid gateway 150 “spoofs” application server 140 to improve the throughput over the satellite link. Specifically, hybrid gateway 150 sends an ACK to application server 140, even though a corresponding packet may not have been received by hybrid terminal 110 via the satellite at the time.

[0142] FIG. 12 is a ladder diagram showing packets sent from application server 140 to hybrid gateway 150 and from hybrid gateway to hybrid terminal 110 through the satellite link. FIG. 12 is not drawn to scale. In FIG. 12, application server 140 sends a message #1 to hybrid gateway 150. The propagation time for this transmission is relatively short. Hybrid gateway 150 immediately creates an ACK packet and sends it to application server 140. Hybrid gateway 150 also sends packet #1 to hybrid terminal 110 through the satellite link. This transmission has a long propagation delay. When hybrid terminal 110 receives the packet, it sends an ACK #1 back to hybrid gateway 150 (e.g., using the tunneling mechanism described above). In a system that does not use tunneling, hybrid gateway 150 needs to intercept the ACK packets from hybrid terminal 110.

[0143] FIGS. 13(a) through 13(e) are flowcharts of steps performed by hybrid gateway 150 of FIG. 1 during protocol spoofing. In step 1302 of FIG. 13(a), hybrid gateway 150 receives a packet from application server 140 indicating that a new connection is being formed between application server 140 and hybrid terminal 110. In step 1304, hybrid gateway 150 sets up a queue or similar data structure in memory to save un-ACK'ed packets for the new connection. FIG. 13(b) shows corresponding steps performed by hybrid gateway 150 when the connection is closed. Hybrid gateway 150 receives a packet indicating the closure in step 1306 and deletes the queue and saved values for the connection in step 1308.

[0144] In step 1310 of FIG. 13(c), hybrid gateway 150 fails to receive an ACK for a packet number X from hybrid terminal 110 before an end of a predetermined timeout period. Hybrid gateway 150 maintains a timer for each un-ACK'ed packet. At the end of the predetermined period, hybrid gateway 150 retransmits a packet corresponding to the expired timer. In step 1312, hybrid gateway 150 re-sends packet number X, which it previously saved in the memory queue for this connection (see FIG. 13(d) below).

[0145] In step 1314 of FIG. 13(d), hybrid gateway 150 receives a packet from application server 140. In step 1316, hybrid gateway 150 sends the received packet to satellite gateway 160, where it is transmitted over the satellite link, and saves the packet in case it needs to be retransmitted (see FIG. 13(c)). Hybrid gateway 150 then creates an ACK packet to send to application server 140 in step 1318. The created ACK packet incorporates a format shown in FIG. 11. Hybrid gateway 150 creates an ACK number for field 1104. The ACK number is determined as follows:

[0146] Hybrid gateway 150 saves the following information for each connection:

[0147] 1) Send sequence number—a highest in-sequence sequence number of packets sent by application server 140 over the connection.

[0148] 2) ACK sequence number—the ACK sequence number from the most recent packet sent by hybrid terminal 110 over this connection.

[0149] 3) ACK window size—the window size from the most recent packet from hybrid terminal 110 over this connection.

[0150] 4) ACK number—the ACK sequence number that is relayed to application server 140. The ACK number is set to:

[0151] minimum(send sequence number, ACK sequence number+spoofed window size—ACK window size).

[0152] 5) spoofed window size—predetermined maximum number window size to be allowed on this connection.

[0153] When hybrid gateway 150 inserts the ACK number in the packet, it also calculates the packet's checksum 1106.

[0154] In step 1320 of FIG. 13(e), hybrid gateway 150 receives an ACK packet over the modem link from hybrid terminal 110. In step 1322, hybrid gateway 150 removes from the queue the packet for which the ACK was received. Because an ACK was received, the packet does not need to be re-sent. In the TCP/IP protocol, a packet containing an ACK may or may not contain data. Hybrid gateway 150 edits the received packet to replace the packet's ACK number 1104 with a “spoofed” ACK number in step 1326. The spoofed ACK number is determined in the same way as the ACK number in step 1318 of FIG. 13(d). When hybrid gateway 150 substitutes the spoofed ACK number 1104 in the packet, it also recalculates the packet's checksum 1106 in step 1326.

[0155] In step 1328, hybrid gateway 150 forwards the received ACK packet to application server 140. Application server 140 may simply disregard the packet if it contains an ACK and no data. In another embodiment, hybrid gateway 150 simply discards a packet received from hybrid terminal 110 that contains an ACK, but no data.

[0156] If the connection goes down, either explicitly or after a predetermined period of time, hybrid gateway 150 deletes the saved packets for the connection.

d. Summary

[0157] In summary, the present invention allows a personal computer to send messages into the Internet using a conventional dial-up link and to download data from the Internet using a high-speed one-way satellite link. In a preferred embodiment, the invention uses a conventional SLIP provider to connect to the Internet and uses a commercial software TCP/IP package that has a standard driver interface. A spoofing protocol compensates for the long propagation delays inherent to satellite communication.

[0158] Other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope of the invention being indicated by the following claims.

Claims

What is claimed is:

1. A peripheral for coupling a satellite antenna device and a computing device, wherein said peripheral is configured to interface to a TCP/IP stack of the computing device using ethernet protocol,

wherein said peripheral generates an ARP response to an ARP request generated by the TCP/IP stack of the computing device.

2. A peripheral according to claim 1, wherein packets received from the satellite antenna device are scanned so that only packets matching a predetermined IP address are forwarded to the TCP/IP stack of the computing device.

3. A peripheral for connecting a satellite antenna device and a computing device, wherein said peripheral is configured to interface to a TCP/IP stack of the computing device using a network driver interface specification,

wherein said peripheral generates an ARP response to an ARP request generated by the TCP/IP stack of the computing device.

4. A peripheral according to claim 3, wherein said peripheral is an adapter card.

5. A peripheral according to claim 3, wherein packets received from the satellite antenna device are scanned so that only packets matching a predetermined IP address are forwarded to the TCP/IP stack of the computing device.

6. An interface between a wireless communication unit and a computing device, wherein the wireless communication unit is presented to a TCP/IP stack of the computing device so as to appear to be a LAN device,

wherein said interface generates an ARP response to an ARP request generated by the TCP/IP stack of the computing device.

7. An interface between a wireless communication unit and a computing device, wherein the wireless communication unit is presented to a TCP/IP stack of the computing device so as to appear to be an ethernet device,

wherein said interface generates an ARP response to an ARP request generated by the TCP/IP stack of the computing device.

8. An interface according to claim 7, wherein the wireless communication unit is a satellite antenna device.

9. An interface according to claim 8, wherein packets received from the satellite antenna device are scanned so that only packets matching a predetermined IP address are forwarded to the TCP/IP stack of the computing device.

10. An interface according to claim 7, wherein the computing device is a personal computer.

11. An interface between a wireless communication unit and a computing device,

wherein the wireless communication unit is presented to a TCP/IP stack of the computing device so as to appear to be any of: (a) a network interface card; (b) a Crynson-Clark Packet Driver Specification device; and (c) a 3Com/Microsoft Network Driver Interface Specification device, and

wherein said interface generates an ARP response to an ARP request generated by the TCP/IP stack of the computing device.

12. An interface according to claim 11, wherein the wireless communication unit is presented to the TCP/IP stack of the computing device so as to appear to be a network interface card.

13. An interface according to claim 11, wherein the wireless communication unit is presented to the TCP/IP stack of the computing device so as to appear to be a Crynson-Clark Packet Driver Specification device.

14. An interface according to claim 11, wherein the wireless communication unit is presented to the TCP/IP stack of the computing device so as to appear to be a 3Com/Microsoft Network Driver Interface Specification device.

15. A system comprising:

a device configured to interface a satellite antenna unit with a computer; and

computer-processable code for execution on the computer,

wherein said device and said computer-processable code are configured such that said device appears to a TCP/IP stack of the computer to be an ethernet device and such that an ARP response is generated in response to an ARP request generated by the TCP/IP stack of the computer.

16. A system according to claim 15, wherein said device is an adapter card.

17. A system comprising:

a device configured to interface a satellite antenna unit with a computer; and

computer-processable code for execution on the computer,

wherein said device and said computer-processable code are configured such that (a) a TCP/IP packet generated by a TCP/IP stack of the computer is encapsulated in an ethernet packet which is stripped off before the packet is sent to the internet, (b) a TCP/IP packet received through the satellite antenna unit from the internet is scanned to determine if the destination IP address matches a predetermined IP address, and if a match is found then the TCP/IP packet is encapsulated in an ethernet packet and passed to the TCP/IP stack of the computer.

18. A system according to claim 17, wherein said device is an adapter card.

19. A system according to claim 17, wherein the TCP/IP stack of the computer is configured to set the maximum transmission unit to be as large as possible.

20. A system according to claim 17, wherein in response to generation of an ARP packet by the TCP/IP stack of the computer, a physical address is generated by said computer-processable code and sent in a reply packet to the TCP/IP stack.

Patent Citations (133)

Patent	Date	Inventor	Cited By
US4018993(A)	1977-04-01	Edström	Applicant
US4135156(A)	1979-01-01	Sanders, Jr. et al.	Applicant
US4358672(A)	1982-11-01	Hyatt et al.	Applicant
US4538073(A)	1985-08-01	Freige et al.	Applicant
US4599647(A)	1986-07-01	George et al.	Applicant
US4636879(A)	1987-01-01	Narita et al.	Applicant
US4663743(A)	1987-05-01	Rampuria et al.	Applicant
US4680688(A)	1987-07-01	Inou et al.	Applicant
US4686698(A)	1987-08-01	Tompkins et al.	Applicant
US4720873(A)	1988-01-01	Goodman et al.	Applicant
US4724520(A)	1988-02-01	Athanas et al.	Applicant
US4736422(A)	1988-04-01	Mason	Applicant
US4768228(A)	1988-08-01	Clupper et al.	Applicant
US4775974(A)	1988-10-01	Kobayashi	Applicant
US4777657(A)	1988-10-01	Gillaspie	Applicant
US4793813(A)	1988-12-01	Bitzer et al.	Applicant
US4802215(A)	1989-01-01	Mason	Applicant
US4829569(A)	1989-05-01	Seth-Smith et al.	Applicant
US4841526(A)	1989-06-01	Wilson et al.	Applicant
US4847892(A)	1989-07-01	Shelley	Applicant
US4893307(A)	1990-01-01	McKay et al.	Applicant
US4918653(A)	1990-04-01	Johri et al.	Applicant
US4924303(A)	1990-05-01	Brandon et al.	Applicant
US4933936(A)	1990-06-01	Rasmussen et al.	Applicant
US4940963(A)	1990-07-01	Gutman et al.	Applicant
US4942569(A)	1990-07-01	Maeno	Applicant
US4959872(A)	1990-09-01	Imai et al.	Applicant
US5019910(A)	1991-05-01	Filmer	Applicant
US5029207(A)	1991-07-01	Gammie	Applicant
US5038265(A)	1991-08-01	Paladel	Applicant
US5058138(A)	1991-10-01	Figura et al.	Applicant
US5101267(A)	1992-03-01	Morales-Garza	Applicant
US5101478(A)	1992-03-01	Fu et al.	Applicant
US5111504(A)	1992-05-01	Esserman et al.	Applicant
US5131010(A)	1992-07-01	Derrenge et al.	Applicant
US5157662(A)	1992-10-01	Tadamura et al.	Applicant
US5159592(A)	1992-10-01	Perkins	Applicant
US5161194(A)	1992-11-01	Ujiie	Applicant
US5193151(A)	1993-03-01	Jain	Applicant
US5223923(A)	1993-06-01	Morales-Garza	Applicant
US5237610(A)	1993-08-01	Gammie et al.	Applicant
US5245429(A)	1993-09-01	Virginio et al.	Applicant
US5249164(A)	1993-09-01	Koz	Applicant
US5257369(A)	1993-10-01	Skeen et al.	Applicant
US5293250(A)	1994-03-01	Okumura et al.	Applicant
US5301358(A)	1994-04-01	Gaskill et al.	Applicant
US5303042(A)	1994-04-01	Lewis et al.	Applicant
US5309351(A)	1994-05-01	McCain et al.	Applicant
US5319705(A)	1994-06-01	Halter et al.	Applicant
US5319707(A)	1994-06-01	Wasilewski et al.	Applicant
US5319712(A)	1994-06-01	Finkelstein et al.	Applicant
US5335276(A)	1994-08-01	Thompson et al.	Applicant
US5337044(A)	1994-08-01	Folger et al.	Applicant
US5341425(A)	1994-08-01	Wasilewski et al.	Applicant
US5347304(A)	1994-09-01	Moura et al.	Applicant
US5359367(A)	1994-10-01	Stockill	Applicant
US5367571(A)	1994-11-01	Bowen et al.	Applicant
US5387994(A)	1995-02-01	McCormack et al.	Applicant
US5394469(A)	1995-02-01	Nagel et al.	Applicant
US5394561(A)	1995-02-01	Freeburg	Applicant
US5400401(A)	1995-03-01	Wasilewski et al.	Applicant
US5404505(A)	1995-04-01	Levinson	Applicant
US5404583(A)	1995-04-01	Lalezari et al.	Applicant
US5412660(A)	1995-05-01	Chen et al.	Applicant
US5420866(A)	1995-05-01	Wasilewski	Applicant
US5430709(A)	1995-07-01	Galloway	Applicant
US5452357(A)	1995-09-01	Naccache	Applicant
US5465213(A)	1995-11-01	Ross	Applicant
US5481609(A)	1996-01-01	Cohen et al.	Applicant
US5483466(A)	1996-01-01	Kawahara et al.	Applicant
US5483595(A)	1996-01-01	Owen	Applicant
US5488412(A)	1996-01-01	Majeti et al.	Applicant
US5491800(A)	1996-02-01	Goldsmith et al.	Applicant
US5504814(A)	1996-04-01	Miyahara	Applicant
US5506904(A)	1996-04-01	Sheldrick et al.	Applicant
US5526404(A)	1996-06-01	Wiedeman et al.	Applicant
US5532914(A)	1996-07-01	Kageyama et al.	Applicant
US5534913(A)	1996-07-01	Majeti et al.	Applicant
US5548753(A)	1996-08-01	Linstead et al.	Applicant
US5564076(A)	1996-10-01	Auvray	Applicant
US5568554(A)	1996-10-01	Eastlake, 3rd	Applicant
US5586121(A)	1996-12-01	Moura et al.	Applicant
US5590200(A)	1996-12-01	Nachman et al.	Applicant
US5592173(A)	1997-01-01	Lau et al.	Applicant
US5592620(A)	1997-01-01	Chen et al.	Applicant
US5594490(A)	1997-01-01	Dawson et al.	Applicant
US5594776(A)	1997-01-01	Dent	Applicant
US5594782(A)	1997-01-01	Zicker et al.	Applicant
US5608446(A)	1997-03-01	Carr et al.	Applicant
US5627528(A)	1997-05-01	Kuznicki	Applicant
US5634190(A)	1997-05-01	Wiedeman	Applicant
US5652795(A)	1997-07-01	Dillon et al.	Applicant
US5659350(A)	1997-08-01	Hendricks et al.	Applicant
US5764886(A)	1998-06-01	Danielson et al.	Applicant
US5995725(A)	1999-11-01	Dillon	Applicant
US5995726(A)	1999-11-01	Dillon	Applicant
US6006275(A)	1999-12-01	Picazo, Jr. et al.	Applicant
US6014378(A)	2000-01-01	Christie et al.	Applicant
US6016388(A)	2000-01-01	Dillon	Applicant
US6041356(A)	2000-03-01	Mohammed	Applicant
US6052718(A)	2000-04-01	Gifford	Applicant
US6067561(A)	2000-05-01	Dillon	Applicant
US6141682(A)	2000-10-01	Barker	Applicant
US6160797(A)	2000-12-01	Robert, III et al.	Applicant
US6161141(A)	2000-12-01	Dillon	Applicant
US6205473(B1)	2001-03-01	Thomasson et al.	Applicant
US6208656(B1)	2001-03-01	Hrastar et al.	Applicant
US6338131(B1)	2002-01-01	Dillon	Applicant
US6377992(B1)	2002-04-01	Plaza Fernandez et al.	Applicant
US6519651(B1)	2003-02-01	Dillon	Applicant
US6571296(B1)	2003-05-01	Dillon	Applicant
US2002/0087981(A1)	2002-07-01	Daniels	Applicant
EP483547	1992-05-01		Applicant
JP55-120249	1980-09-01		Applicant
JP56-2765	1981-01-01		Applicant
JP59-135948	1984-08-01		Applicant
JP60-167533	1985-08-01		Applicant
JP61-70823	1986-04-01		Applicant
JP61-210745	1986-09-01		Applicant
JP62-189823	1987-08-01		Applicant
JP62-221228	1987-09-01		Applicant
JP63-107254	1988-05-01		Applicant
JP63-131731	1988-06-01		Applicant
JP63-194426	1988-08-01		Applicant
JP3-62630	1991-03-01		Applicant
JP4-14811	1992-03-01		Applicant
JP4-306934	1992-10-01		Applicant
JP5-167565	1993-07-01		Applicant
JP5-252085	1993-09-01		Applicant
JP5-252087	1993-09-01		Applicant
JP5-252165	1993-09-01		Applicant
JP6-252896	1994-09-01		Applicant
JP9-506226	1997-06-01		Applicant

Non-Patent Literature (15)

End-to-end performance analysis for broadband island interconnection via satellite-RACE II/2074 (Catalyst) project by Hadjitheodosiou et al., Nov. 1993 publication, pp. 170-174.Applicant
End-to-end protocol performance in ATM/Satellite interconnected LANs by Komisarczuk et al., Nov. 1993 publication, pp. 87-91.Applicant
An Analysis of TCP/IP in the code network by Fairhurst et al., University of Aberdeen, U.K., Nov. 1993, publication, pp. 16-20.Applicant
Achieving network interconnection using satellite services by Linge et al., University of Salford, U.K., 1993, publication, pp. 165-169.Applicant
B-ISDN implementation via satellite: Catalyst project by Komisarczuk et al., Apr. 1993, publication, pp. 11/1-11/6.Applicant
B.R. Badrinath, A. Bakre, T. Imielinski, and R. Marantz, “Handling Mobile Clients: A Case for Indirect Interaction”, Proc. of the 4th Workshop on Workstation Operating Systems (WWOS-IV) (Oct. 1993).Applicant
A. Bakre and B. Badrinath, “I-TCP: Indirect TCP for mobile hosts”, Technical Report DCS-TR-314, Rutgers University (Oct. 1994).Applicant
Patent Abstracts of Japan, Abstract for JP 62-189823, Aug. 19, 1987.Applicant
Patent Abstracts of Japan, Abstract for JP 5-252165, Sep. 28, 1993.Applicant
Partial Translation of JP 4-14811, Mar. 16, 1992.Applicant
Patent Abstracts of Japan, Abstract for JP-A-61-70823, Apr. 11, 1986.Applicant
Partial Translation and Abstract JP-A-63-107254.Applicant
Brad Wood, “I Can't Get ISDN. Isn't There Another Way to Get Quick Access to the Web?”, Sep. 1996, PC World, pp. 264-265.Applicant
Partial Translation and Abstract of Japanese Laid-Open Patent Application No. 5-252087.Applicant
Partial Translation and Abstract of Japanese Laid-Open Patent Application No. 6-252896.Applicant

Abstract