US 5,768,525 AGrant
Transparent Support of Protocol and Data Compression Features for Data Communication
Issue Date:1998-06-16
•9 Claims
•5 Drawing Sheets
Abstract
A method for efficiently setting up a data transmission session over a communication channel between a local endpoint application and a network endpoint application with a proxy engine in a manner that is transparent to the user. The proxy engine is placed in simultaneous communication sessions with the local endpoint application and the network endpoint application. The proxy engine determines the network control protocols that are supported by both the network endpoint application and the local endpoint application. The proxy engine enables the network control protocols that are supported by both the network endpoint application and the local endpoint application. Optionally, the proxy engine enables data compression techniques that are supported by both the network endpoint application and the proxy engine. After the network control protocols and data compression techniques (if desired) are enabled, the proxy engine transmits data between the local endpoint application and the network endpoint application over the communication channel.
Metadata
Assignee
- U.S. Robotics Corp.
Inventors
- Joseph D. Kralowetz
- Douglas F. Ortega
Application Information
Application Number:US 8453233
Filing Date:1997-04-25
Priority Date:1995-09-08
Art Unit:273
Classifications
IPC:
H04L 932G06F 1516G06F 1338
Field of Search:
395370379380364200.57;200.58;200.32;200.6396;410;465;256;401;466;52493.0849DIG. 1;DIG. 2
Patent Drawings (5 sheets)
Description
Background of the Invention
A. Field of the Invention
This invention relates generally to the field of telecommunication and the processes by which digital data is transmitted between computer systems over a network or communications link. The invention is particularly suitable for use in devices that support Integrated Service Digital Network (ISDN) digital telephone services or the like, in which the digital data is transmitted via the ISDN or other digital line to a data terminal equipment (DTE), such as a computer.
B. Description of Related Art
In order for digital data to be transmitted from the source of the data (such as a computer) to a destination (such as another computer) over a network or telecommunication line, the data must be formated and presented to the transmission medium and the destination in a form that is compatible to the elements of the system. For example, if the source of the data wishes to compress the data using a particular data compression technique, the source and the destination must support both the chosen data compression algorithms.
It is a well known fact of life that the various computers in a network of computers may not have compatible data transmission and formatting software, due to the differences in technology available when the computers were purchased, the different options and features that may have been built into the computers subsequent to their purchase, or the fact that the owners of the computers on the network (such as the Internet) do not know or care about what features other computers on the network may support. When transmission of data in this situation is attempted, the lowest common denominator in terms of the communications protocols is determined during the call connect process. If the source of the data runs communications software that supports only basic communication protocols, but the destination runs backwardly compatible advanced protocols and compression functions, the call will typically proceed, but only in accordance with the basic communications protocols supported by the source.
The present invention addresses this problem by determining, in the call connect process, the communication protocols and compression techniques that are supported at both ends of the network, and by supporting multiple compression protocols and compression algorithms, so as to facilitate communication between the elements of the system. The invention does this automatically, and in a manner that is transparent to the user. Further, if the telecommunication line between the source and destination supports multiple communication channels (such as an ISDN line), the invention automatically enables the data to be transmitted through multiple communication channels. This has the effect of increasing data throughput, and significantly shortening the call connect time.
In order to better understand these and other advantages and features of the invention, a brief exposition of data communication technology and the Point-To-Point Protocol is set forth here.
The Open Systems Interconnect Reference Model is the standard model for describing the layers of functions and protocols necessary for data communications between computers. This well-known model consists of a hierarchy of seven layers of protocols which control the transmission of data from a source of the data to a destination via a network.
The lowest layer in the model is the physical layer, which manages the physical connection of network elements. The next two higher layers are the link layer and the network layer, respectively. The link layer, also known as the data link layer, manages the flow of data between the user and the network, or between a DTE and Data Communications Equipment (DCE). This layer's responsibility is to assure reliable and efficient data transfer, data formatting, the detection, correction and recovery of errors, data transparency, and some forms of addressing.
The network layer manages the details of transmitting data across the physical network between network elements, as well as between networks. The network layer also has the responsibility to define data call establishment procedures for packet and cell switched networks, and manage the segmentation and assembly of data across the network. The application layer is the top layer of the model, and manages the program or device that generates the data that is to be sent from the source through the network to the intended destination.
The Point-to-Point Protocol (PPP) provides a standard method of encapsulating network layer protocol information over point-to-point links. The PPP also defines an extensible Link Control Protocol (LCP), and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. The PPP is described in detail in a series of documents that are available on-line. Persons of skill in the art are familiar with these documents, known as the Request For Comments. The Request For Comments (RFC) 1661, which is incorporated by reference herein, gives an informative overview of the PPP.
The initial deployment of the PPP has been over short local lines, leased lines, and plain-old-telephone-service (POTS) using modems. As new packet services and higher speed lines are introduced, PPP is easily deployed in these environments as well.
As noted above, the PPP has three main components:
1. A procedure for encapsulating datagrams over serial links;
2. A Link Control Protocol (LCP) for establishing, configuring, and testing the data-link connection; and
3. A family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols.
In order to establish communications over a point-to-point link, each end of the PPP link must first send LCP packets to configure the data link during the Link Establishment phase. After the link has been established, PPP provides for an optional Authentication phase before proceeding to the Network-Layer Protocol phase.
By default, authentication (i.e., password identification) is not mandatory. If authentication of the link is desired, an implementation must specify the Authentication-Protocol Configuration Option during Link Establishment phase.
These authentication protocols are intended for use primarily by hosts and routers that connect to a PPP network server via switched circuits or dial-up lines, but might be applied to dedicated links as well. The server can use the identification of the connecting host or router in the selection of options for network layer negotiations.
PPP encapsulation of data communications is possible when the data is transmitted over digital communication lines, such as ISDN lines. ISDN lines comprise two data channels (referred to as bearer channels or "B" channels), and a control channel known as the "D" channel. The ISDN D-channel can also be used for sending PPP packets when suitably framed, but is limited in bandwidth and often restricts communication links to a local switch. Since the ISDN B-channel is by definition a point-to-point link, PPP is well suited to use over ISDN lines.
The ISDN Primary Rate Interface may support many concurrent B-channel links. The PPP Link Control Protocol and Network Control Protocol mechanisms are particularly useful in this situation in reducing or eliminating hand configuration, and facilitating ease of communication between diverse implementations.
In order to accommodate ISDN data links over multiple channels simultaneously, a protocol known as PPPML or PPP MultiLink is used. The PPP MultiLink protocol is described in the Request For Comments 1717, which is incorporated by reference herein
In our invention, an element of communication equipment we have called a proxy engine is used in establishing a connection between the local endpoint application (i.e., the application running at the source of the data) and the application located at the far end of the network (i.e., the application running at the destination for the data). The application located at the destination is referred to herein as the "network endpoint application". The proxy engine, which in the preferred form constitutes a communication software structure, may be installed at the source, at the destination, or at both the source and destination. The term "proxy" is meant to indicate that the proxy engine is supplying the protocol feature or data compression on behalf of the local endpoint application. The term "engine" stems from the fact that the proxy engine actively provides or supports these protocol and/or compression features in real time during the call connection and data transfer process.
In our invention, the proxy engine conducts simultaneous communications sessions with the local endpoint application and the network endpoint application to determine what protocol features are supported by the endpoint applications. Additionally, the proxy engine supports or enables multiple advanced features available with the Point-To-Point Protocol, such as PPP MultiLink, various data compression techniques over PPP or PPP Multilink, Challenge Handshake Application Protocol (CHAP) MD5, and any Link Control Protocol extensions that are implemented in the proxy engine, such as Link Control Protocol ECHO.sub.-- REQUEST, ECHO.sub.-- REPLIES, call back, endpoint identification, etc. Because these features are supported in the proxy engine, the user does not have to independently develop these features. The invention allows an application running above the proxy engine to "leverage", or take advantage of, all the advanced set of features described in the PPP Request For Comments, without supplementing any part of the PPP but the most basic feature of the set described in Request for Comments 1661, and possibly the Password Authentication Protocol and at least one Network Control Protocol.
Computers that implement the present invention will essentially level the playing field for all the endpoint applications, because the proxy engine makes up for and supports the data compression, multiple link, and authentication features that are lacking in the local endpoint application. The benefit to the user of the invention is thus increased throughput and data capacity over their existing equipment, because the proxy engine will provide the necessary protocol or compression features that may be lacking in the endpoint application.
In accordance with the present invention, the proxy engine learns each of the endpoint's particular configuration parameters, such as security information, network addressing, error correction routines and data compression technique, during communication sessions at the outset of the call connect process. To the user and the local endpoint application, it appears as though the local endpoint application is communicating directly with the network endpoint application, but in reality the local endpoint application is interfacing with the proxy engine. Similarly, the network endpoint application appears to be communicating directly with the local endpoint application, but is actually interfacing with the proxy engine. All of this is done in a manner that is transparent to the user at the local endpoint application, i.e, the user does not need to initiate any special configurations or take special action, as it occurs automatically. Thus, the invention provides for "spoofing" for quick determination and implementation of PPP network control protocols over one or more channels, and for data compression techniques, during the call connection process.
Summary of the Invention
The present invention is implemented in a system comprising a source of data, a receiver of data and a communication channel linking the source and the receiver. In one aspect, the invention is a method for setting up a data transmission session between a local endpoint application at the source and a network endpoint application at the destination with a proxy engine in a transparent manner. The method comprises the steps of:
placing the proxy engine in simultaneous communication sessions with the local endpoint application and the network endpoint application;
determining with the proxy engine at least one of the following: (a) security protocols, (b) multiple channel capabilities, (d) data compression techniques, and/or (d) network control protocols, that are supported by the network endpoint application,
determining with the proxy engine the security protocols and/or network control protocols that are supported by the local endpoint application;
enabling the security protocols, multiple channel capabilities, data compression techniques and network protocols that are supported by both
(1) the network endpoint application, and
(2) the combination of the proxy engine and the local endpoint application, and
transmitting data between the local endpoint application and the network endpoint application, whereby data may be transmitted from the source of the data to the receiver of the data over the communication channel. In this manner, to the extent that the network endpoint application requests multiple channel capabilities or data compression techniques that are not supported by the local endpoint application, these features are provided by the proxy engine. Additionally, the proxy engine enables the security protocols and network control protocols that are supported by the local endpoint application.
In general, the local endpoint application communication session ("the local session") may be negotiated as a single link with no data compression. Conversely, the network endpoint application communication session ("the network session") will be negotiated with multiple links and with data compression.
In accordance with the preferred form of the present invention, in order for the network session and the local session to gain each other's configuration information, the two sessions are preferably brought up (or "enabled") in a specific order. Inherently, PPP requires that multiple control layers be established before a session may be brought into service.
Where the proxy engine supports multiple links over the PPP, the preferred embodiment of the invention provides for opening up a second communication channel or multiple communication channels for transmission of the data between the source and the receiver of the data, and transmitting the data over all of the opened channels simultaneously from the source to the receiver. If more than two channels are available (as in ISDN Primary Rate service), then the proxy engine may open up more than two channels and pipe the data to the endpoint application down however many channels may be opened. This feature permits a significant reduction in the overall call connection time and a significant increase in call throughput.
Brief Description of the Drawings
Presently preferred embodiments of the invention are depicted in the drawings, wherein like reference numerals refer to like elements in the various views, and wherein:
FIG. 1A is an illustration of a prior art local endpoint application that communicates with a network endpoint application via a single channel communication line connected to a network;
FIG. 1B is an illustration of a prior art local endpoint application that communicates with a network endpoint application via a multiple channel communication line connected to a network;
FIG. 2 is an illustration of the interrelationship between a local endpoint application, a proxy engine and a network endpoint application according to a preferred form of the invention;
FIG. 3 is a hardware and software diagram of the local endpoint, showing the local endpoint application, proxy engine and communications hardware, in conjunction with the communication channel leading to the network and network endpoint equipment;
FIG. 4 is an illustration of the sequence of the flow of information between the local endpoint application, the proxy engine, and the network endpoint application of FIGS. 2 and 3, when the data transmission session is established according to a preferred embodiment of the invention; and
FIG. 5 is a schematic diagram of a source of data which implements the invention in communication with a variety of possible different network endpoint destinations over a network, wherein the proxy engine of FIGS. 2-4 may be implemented in one or more of the network endpoint destinations in addition to the source.
Detailed Description of the Preferred Embodiment
FIG. 1 shows a prior art data communication system wherein a local endpoint application 20 is in communication with a network endpoint application 30 via a network 40. The local endpoint application 20 is the source of data to be transmitted to the network endpoint application 30. The local endpoint application is linked via communications hardware (not shown) to a communication channel 22A (such as a B-channel of an ISDN line), which is turn routed through the network or communication system 40 to a second ISDN channel 22B. Channel 22B is connected via conventional hardware (not shown) to the computer running the network endpoint application 30. Typically, the channel 22A supports the Point-To-Point Protocol (PPP) with or without the implementation of data compression techniques. In order for advanced PPP protocols to be used by both the local 20 and endpoint 30 applications, both would have to be supported by the respective applications.
FIG. 1B shows a similar prior art arrangement of the local and network endpoint applications 20 and 30 respectively, except that a multiple channel line 24A links the local endpoint application 20 to the network 40. Similarly, a multiple channel line 24B links the network 40 to the network endpoint application 30. The capabilities of the local and network endpoint applications is the lowest common denominator of protocol and compression suites that may be supported by the local and network endpoint applications.
Referring now to FIG. 2, the presently preferred embodiment of the invention uses a proxy engine 50 to facilitate the communication between the local endpoint application 20 and the network endpoint application 30. The proxy engine 50 consists of a software structure that is typically implemented at the source computer (not shown in FIG. 2) running the local endpoint application 20, such as at the ISDN driver for the source computer. The proxy engine 50 consists of a set of routines 52 that communicate with the local endpoint application in a local endpoint application communication session 26, and a set of routines 54 that communicate with the network endpoint application 30 in a network endpoint application communication session 28.
The routines 52 consist of PPP, single channel, no data compression routines that are described in detail below in conjunction with FIG. 4 and set forth in the appended software listing. The routines 54 consists of multiple channel PPPML routines, with compressed data, and are also described below in conjunction with FIG. 4 and set forth in the appended software listing. The double arrow 53 indicates that the local endpoint application routines 52 pass information learned about the local endpoint application 20 to the routines 54 that communicate with the network endpoint application 30, and vice versa.
FIG. 3 is a hardware and software diagram of a source of data or local endpoint 32, showing the local endpoint application 20 (in software), proxy engine 50 (also in software), in their relationship to the communication hardware 56 that connects the source 32 to the communication channel 24. The communications hardware 56 is, for example, an ISDN basic rate adapter which is installed in a personal computer, and corresponds to the physical layer of the OSIRM model. The communication hardware 56 is controlled by the software 34 that runs at the source 32. The proxy engine 50 is in communication via the line 24A, network 40, and line 24B with the destination or network endpoint 38, which has its own communications hardware 56 controlled by its own application software 30.
The local endpoint application 20 will typically support the Point-to-Point protocol and perhaps some limited subset of the advanced PPP features, and may or may not support particular data compression algorithms. The session 26 negotiates the PPP protocol down to single channel and no data compression. The proxy engine 50 supports single channel non-compressed PPP protocol to the local endpoint application 20 from the routines 52. The proxy engine 50 supports multiple compressed PPP channels to the network endpoint application 30 (which supports PPP or PPPML) and possibly compression of the data packets from routines 54.
The network endpoint or destination 38 contains a network endpoint application 30 which supports PPP or PPPML and possibly compression of data packets. If the network endpoint application 30 supports a particular data compression algorithm, but the local endpoint application 20 does not, the proxy engine 50 provides for the local endpoint application 20 the necessary data compression feature, provided that the proxy engine supports this particular compression feature. It will be apparent that to optimize the usefulness of the proxy engine with a large and diverse set of potential network endpoints, it is preferable to support as large a number of protocol features (such as PPPML, security requirements such PAP) and data compression techniques as possible. It will also be appreciated that the present invention may be used with just support for PPP features such as PPPML or PAP and no data compression, or data compression but no protocol features, or with both protocol features and data compression, the idea being that the proxy engine supplies the missing authentication protocol (i.e., CHAP in the present embodiment), data, compression technique, or multiple link protocol that happens to not be implemented at the local endpoint application.
The data transmission session establishment process is preferably performed in a sequence of steps. In particular, FIG. 4 illustrates the session establishment flow between the network endpoint application 30 and the local endpoint application 20, with the reference numerals 1-10 corresponding to the steps described below. The arrows in FIG. 4 represent the flow of requests and information between the proxy engine 50, the local endpoint application 20 and the network endpoint application 30. As noted in FIG. 4, the proxy engine is placed in simultaneous communication sessions 26, 28 between the proxy network endpoint application 30 and the local endpoint application 20. The routines 52 and 54 (FIG. 3) which are performed in the proxy engine 50 are described in conduction with the ten steps set forth below.
Step 1: Bring up the physical layer of the network session 28.
The process begins by the source DTE 32 placing a call over a communication link (such as an ISDN D-channel) to a remote DTE 38 on the network or communication system 40, thereby allocating an end-to-end circuit through the communication network 40.
Step 2: Bring up the network endpoint application 30 LCP layer.
The proxy engine 50 establishes the link-control-protocol (LCP) layer of the network session 28 prior to responding to any messages from the local endpoint application 20. This step involves a series of handshaking routines (such as configure-request or CFG.sub.-- REQ messages) to determine that the user at source 32 has called up a PPP entity 38 over the network 40. The Internet Standard for PPP is used for the LCP layer. Two of the items of information that are learned when the LCP layer in brought up in step 2 are (1) whether or not password authentication needs to take place, and (2) whether MultiLink (or PPPML) is supported by the network endpoint application 30.
Step 3: Bring up the local endpoint application 20 LCP layer.
Once the network endpoint application 30 LCP is established, the local endpoint application 20 LCP session is brought up. In the configure-request message, the Password Authentication Protocol (PAP) Authentication is specified if the network endpoint application 30 requires any kind of authentication. PAP is used so that the user name/password is obtained transparently from the local endpoint application 20 without requiring user intervention.
Step 4: Bring up the local endpoint application 20 Authentication Layer (if applicable)
If the network session 28 at step 2 specified that the local endpoint application 20 must authenticate passwords before bringing up the network control protocols (NCP's), the user name/password combination must be obtained from the local endpoint application 20. By requesting to the local endpoint application 20 during the link control protocol negotiations that the local endpoint application 20 must authenticate with the proxy engine 50 (the proxy engine 50 being the Authenticator and the local endpoint application 20 being the Peer), we now bring up the PAP Authentication control protocol with the application session as per the Internet Standard for PPP Authentication Protocols.
Step 5: Bring up the network endpoint application 30 Authentication Layer.
Once the local endpoint application 20 authentication control protocol is open, the network endpoint application 30's authentication control protocol is brought up, with the network endpoint application 30 being the Authenticator and the proxy engine 50 being the Peer. In the preferred embodiment, the proxy engine 50 can support both PAP or CHAP (Challenge Handshake Authentication Protocol). Also, the proxy engine 50 will only be the Peer on the network endpoint side and the Authenticator on the local endpoint side.
Step 6a: Determine which Network Control Protocols (NCP's) the local endpoint application 20 wants to bring up.
At this point, the proxy engine 50 needs to determine which of the network control protocols the local endpoint application 20 supports and wishes to open. In order to determine this, the proxy engine 50 will wait to receive the CFG.sub.-- REQ message from the local endpoint application 20 for the NCP's that the network endpoint application 20 wishes to open and communicate over. Upon receiving a CFG-REQ message, the proxy engine 50 will first learn any information that is necessary for successful proxy operations.
The learned information for each supported network control protocol is as follows:
(i) BCP (Bridging Control Protocol): None.
(ii) IPCP (Internet Protocol Control Protocol): The local endpoint application 20's internet protocol address, including whether the local endpoint application 20 is asking for an internet protocol address to be assigned from the network endpoint application 30.
(iii) IPXCP (Internet Packet Exchange Control Protocol):
a) The local endpoint application 20's internet packet exchange network address, including whether the local endpoint application 20 is asking for the IPX network address from the network endpoint application 30; and
b) The local endpoint application 20's IPX Node Address, including whether the application 20 is asking for an IPX Node Address to be assigned from the network endpoint application 30. If the local endpoint application 20 is asking for one to be assigned, the proxy engine 50 will return the proxy engine's Media Access Control Address as the assigned Node Address (which is stored in an EEPROM memory, not shown) instead of asking the network endpoint application 30 for one.
c) NBFCP (NetBEUI control protocol): The local endpoint application 20's name in the IBM Network Basic Input/Output System Extended User Interface (NetBEUI) protocol.
Since multiple network control protocols can be opened over a single PPP session, each network control protocol state machine can operate autonomously.
Step 6b: Determine which (if any) Compression Protocols the network endpoint application 30 is trying to bring up. If it is one that the proxy engine supports, bring it up.
Once all of the LCP and Authentication Layers are opened, the network endpoint application 30 is allowed to attempt compression control protocol (CCP) negotiations, that is, opening up a compression session between the proxy engine 50 and the network endpoint application 30. The proxy engine 50 listens for any CCP CFG.sub.-- REQ messages from the network endpoint application 30. Upon receiving one, the proxy engine 50 determines what compression scheme the network endpoint application 30 is trying to negotiate.
Specificallly, the compression algorithm that the network endpoint application 30 is attempting to negotiate is determined in two steps. The first step is to look at the CCP Option Type Field in the CCP Configuration Request (CFG.sub.-- REQ) message. If the CCP Option Value indicates Microsoft PPC Compression, the proxy engine does not need to proceed further with the interrogation. If the CCP Option Value indicates STAC Electronics LZS, the proxy engine 50 needs to determine whether it is STAC LZS.TM. or Ascend.TM.'s version of STAC LZS. Th difference between these two is that the length of the STAC Electronics Configuration Request Message is five (5) bytes long whereas Ascend's length is six (6) bytes long (Ascend has an additional byte for negotiating the dictionary reset mode). If none of the three compression techniques were detected, no compression will be allowed.
Persons of skill in the art will of course appreciate that the above identification technique for presently popular data compression techniques can be readily adapted to other types of data compression techniques that may be developed in the future.
If the compression techniques that the network endpoint application 30 is a compression scheme that is supported by the proxy engine 50, the proxy engine 50 will open the compression layer control protocol with the network endpoint application 30. If it is not one that the proxy engine 50 supports, the proxy engine 50 will reject the request to negotiate the compression layer with a PROTO.sub.-- REJECT message, thereby disallowing compressed data packets over the network session 28. Thus, even if the local endpoint application does not support the data compression algorithm requested by the network endpoint application 30, the proxy engine 50 provides it for the local endpoint application 20, allowing the data compression technique to be used in the transmission of data from the source to the destination.
Preferably, the proxy engine 50 supports a wide variety of known compression protocols, such as STAC LZS.TM., Microsoft PPC.TM., and Ascend.TM. version of STAC LZS.TM.. Licenses from the proprietors of the compression techniques should be obtained in order for the proxy engine 50 to implement proprietary compression techniques.
Step 7: For each NCP that the local endpoint application 20 has specified (via step 6 (a)), bring up the respective network endpoint application 30 NCP.
After learning the local endpoint application 20 NCP information in step 6(a), the proxy engine 50 will use this information in bringing up the respective network endpoint application 30 NCP's. If any information was dynamically assigned by the network endpoint application 30 (as dictated by the local endpoint application 20) the proxy engine 50 will store the learned information for later use.
Step 8: Once the Network endpoint application 30 NCP are opened, bring up the respective application NCP.
After the network endpoint application 30 NCP is opened, the proxy engine 50 will bring up the respective local endpoint application 20 NCP (passing back to it any dynamically assigned information from either the network endpoint application 30 or the proxy engine 50). Once this step is complete, data packets may flow over the proxy engine 50 logical interface.
Step 9: Once the local endpoint application 20 NCP is open, the proxy engine will now allow data packets to flow through it.
As the proxy engine 50 receives data packets from the local endpoint application 20, it will:
(1) try to compress the packet (if applicable);
(2) split the packet (original or compressed) into multiple fragments; and
(3) transmit the fragments over one or more open data channels to the network endpoint application 30.
As the proxy engine 50 receives data fragments from the network endpoint application 30, it will:
(1) collect all the fragments which constitute a complete data packet;
(2) reassemble the fragments into one contiguous data packet;
(3) uncompress the reassembled data packet (if applicable); and
(4) transmit the uncompressed reassembled data packet to the local endpoint application 20.
Step 10: If the network allows MultiLink to be brought up, bring up a second data channel.
Once the first NCP is opened on the local endpoint application 20 side, the proxy engine 50 will preferably attempt to bring up a second data channel (such as the second B-channel in ISDN basic rate service) over the network session 28. Unlike the first link, the local session 26 is not aware of the second B-channel activity. Once the second B-channel comes up, the data packets are transmitted over both the multiple active B-channels to the network endpoint application 30 running at the destination DTE 38, thereby increasing call throughput and reducing the overall call connect time.
The present invention may be implemented in a variety of situations. Referring to FIG. 5, the source DTE 32 is shown connected via channel 24A to a network 40 (the details of which are not important). The network 40 may supply a line 24B to a bridge 60 connected to a second network 61, a line 24C connected to a router 62 connected to another network 63, a line 24D connected to computer 64, or a line 24E connected to a computer 70.
In FIG. 5, source 32 is shown as having a proxy engine in communication with communication hardware 56 (such as an ISDN basic rate adapter), and running an application software comprising the local endpoint application 20. The source 32 may attempt to transfer data to the bridge 60, which runs its own application and thus is considered herein as a network endpoint application. The same holds true for router 62.
Note that computer 64 has its own proxy engine 50 and application 20. The combination of the proxy engine 50 and the local endpoint application 20 running in the computer 64 constitutes in effect a network endpoint application 65 that may be called by the source 32.
The computer 70 is shown connected to a line 24E via an ISDN terminal adapter 72. The computer 70 does not have a proxy engine of its own. However, the source 32 may transmit data to the computer 70 using its own proxy engine in the manner described above. The combination of the computer 70 running its own application and ISDN TA 72 could also be considered a network endpoint application as that term is used herein.
In all of the above representative examples of FIG. 5, it will be appreciated that the proxy engine 50 in the source 32 facilitates the communication with whatever network endpoint application it may happen to call to transmit data. The description above in conjunction with FIGS. 2-4 would apply to any of these data transmission sessions.
The appended computer software listing (See Appendix) sets forth the source code for a presently preferred embodiment of the invention. The source code is preferably incorporated into the ISDN driver, and runs on the motherboard of a host personal computer. The reader is directed to the Notice Re: Copyright set forth above.
It will be appreciated from the forgoing description of a presently preferred embodiment of the invention that some variation in the above procedure is envisioned depending on the particular features of the data transmission medium, the capabilities of the local and network endpoint applications, and the protocol features that may be supported by the proxy engine. Such variations will apparent to those of skill in the art and are intended to be within the spirit and scope of the invention. As additional protocols are developed (such as authentication protocols and multiple link protocols, some modification to the operation of the proxy engine may be necessary in order to implement the invention, and such modifications are considered to be within the capabilities of persons of ordinary skill in this art. This true spirit and scope is defined by the appended claims, to be interpreted in light of the foregoing specification. ##SPC1##
Claims
We claim:
1. Apparatus for linking a local endpoint application running at a source of digital data with an application running at a network endpoint application at a receiver of said digital data, said local and network endpoint applications capable of communication over a communication channel, comprising, in combination: a proxy engine placed at said source of digital data for conducting simultaneous communication sessions between said source and said destination over said communication channel, said proxy engine comprising at least one software routine for determining whether a security protocol, multiple channel protocol, data compression protocol, link control protocol or network control protocol is supported by the network endpoint application but not the local endpoint application; said proxy engine further comprising at least one software routine for implementing for said local endpoint application at least one security protocol, multiple channel protocol, data compression protocol, link control protocol or network control protocol that is supported by the network endpoint application but not the local endpoint application protocol feature to thereby permit said local and network endpoint applications to communicate in accordance with said implemented protocol; and communications hardware responsive to said proxy engine and interfacing with said communication channel for placing said digital data from said local endpoint application onto said communication channel for transmission to said receiver, whereby bilateral digital communication between said local and network endpoint applications is improved.
2. The apparatus of claim 1, wherein said communication channel comprises a digital telephone line.
3. The apparatus of claim 2, wherein said digital communication line comprises an ISDN line.
4. The apparatus of claim 1, wherein said multiple channel protocol comprises PPPML.
5. The apparatus of claim 1, wherein said authentication protocol comprises CHAP.
6. The apparatus of claim 1, wherein said authentication protocol comprises PAP.
7. The apparatus of claim 1, wherein said data compression feature is selected from the group consisting of STAC Electronics LZS and Microsoft Corp. PPC data compression protocol.
8. The apparatus of claim 1, wherein said link control protocol is selected from the group consisting of ECHO-REQUEST, ECHO.sub.-- REPLIES, call back and endpoint identification.
9. In a system comprising a source of data, a receiver of data and a communication channel linking the source to the receiver, a method for setting up a data transmission session between a local endpoint application at said source and a network endpoint application at said receiver with a proxy engine in a transparent manner, comprising the steps of: (1) determining the link control protocols that are supported by the network endpoint application; (2) determining the link control protocols that are supported by the local endpoint application; (3) enabling the link control protocols that are supported by both the network endpoint application and the combination of the proxy engine and the local endpoint application, and thereafter (4) transmitting data between the local endpoint application and the network endpoint application, whereby data is able to be transmitted from the source of the data to the receiver of the data over the communication channel.
Patent Citations (13)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4965795 | 1990-10-01 | Coffelt et al. | |
| US5291479 | 1994-03-01 | Vaziri et al. | |
| US5293379 | 1994-03-01 | Carr | |
| US5408470 | 1995-04-01 | Rothrock et al. | |
| US5410671 | 1995-04-01 | Elgamal et al. | |
| US5414712 | 1995-05-01 | Kaplan et al. | |
| US5438614 | 1995-08-01 | Rozman et al. | |
| US5444702 | 1995-08-01 | Burnett et al. | |
| US5497463 | 1996-03-01 | Stein et al. | |
| US5537474 | 1996-07-01 | Brown et al. | |
| US5539744 | 1996-07-01 | Chu et al. | |
| US5586260 | 1996-12-01 | Hu | |
| US5657452 | 1997-08-01 | Kralowetz et al. |
Non-Patent Literature (14)
- RFC 1333 PPP Link Quality Monitoring (May 1992).
- RFC 1661 The Point-to-Point Protocol, W. Simpson, ed., (Jul. 1994).
- RFC 1662 PPP in HDLC-like framing, W. Simpson, ed., (Jul. 1994).
- RFC 1144 Compressing TCP/IP Headers for Low-Speed Serial Links, V. Jacobson (Feb. 1990).
- RFC 1323 TCP Extensions for High Performance, V. Jacobson, (May 1992).
- RFC 1332 The PPP Internet Protocol Control Protocol (PCP), G. McGregor (May 1992).
- RFC 1333 PPP Link Internetwork Packet Exchange Control Protocol (IPXCP), W. Simpson, (Dec. 1993).
- RFC 1552 The PPP Internetwork Packet Exchange Control Protocol (IPXCP), W. Simpson, (Dec. 1993).
- RFC 1570 PPP LCP Extensions, W. Simpson, (Jan. 1994).
- RFC 1598 PPP in X.25, W. Simpson, (Mar. 1994).
- RFC 1618 PPP over ISDN, W. Simpson, (May 1994).
- RFC 1638 PPP Bridging Control Protocol (BCP), F. Baker, (Jun. 1994).
- RFC 1334 PPP Authentication Protocols, B. Lloyd, (Oct. 1992).
- RFC 1717 The PPP Multilink Protocol (MP), K. Sklower, B. Lloyd, G. McGregor, D. Carr, (Nov. 1994).