Method and apparatus for detecting network traffic and initiating a dial-up connection using separate upstream and downstream devices

• US 6,041,356 A
• Filed: 03/31/1997
• Issued: 03/21/2000
• Est. Priority Date: 03/31/1997
• Status: Expired due to Term

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Mohammed, Mannan
• Primary Examiner(s): Asta, Frank J.
• Assistant Examiner(s): Prieto, Beatriz
• Application Number:
  US08/829,584
• Time in Patent Office: 1,086 Days
• Field of Search: 382/115, 379/45, 379/230, 379/93.08, 379/93.32, 379/93.31, 370/398, 370/402, 370/389, 395/651, 340/825.52, 709/227, 709/220, 709/248, 709/225, 709/228, 709/237, 709/238, 709/250, 709/231, 709/219, 709/217, 709/203
• US Class Current: 709/227
• CPC Class Codes: H04L 12/2801 Broadband local area networks

Abstract

In a client having (i) an upstream device driver for controlling an upstream device which sends data to a server; (ii) a downstream device driver for controlling a downstream device which receives data from the server; and (iii) a dialer application for establishing an upstream connection using the upstream device driver, the present invention initiates a connection in response to upstream traffic generated by an application including the steps of receiving the upstream traffic in the downstream device driver; constructing a dial packet in the downstream device driver in response to the upstream traffic; transferring the dial packet from the downstream device driver to the dialer application; and, issuing a call command to the upstream device driver.

Claims

1. In a client having (i) an upstream device driver for controlling an upstream device which sends data to a server;

(ii) a downstream device driver for controlling a downstream device which receives data from said server, said upstream device driver and said downstream device driver being separate drivers for separate devices; and

(iii) a dialer application for establishing an upstream connection using said upstream device driver, a method for initiating a connection with said server in response to upstream traffic generated by an application in said client comprising the steps of;

receiving said upstream traffic in said downstream device driver, said downstream device driver being incapable of transmitting said upstream traffic;

constructing a dial packet in said downstream device driver in response to said upstream traffic;

transferring said dial packet from said downstream device driver to said dialer application; and

,

issuing a call command to said upstream device driver.

2. The method of claim 1, wherein said dial packet contains a destination port field and a data field, and said dial packet constructing step comprises the steps of:

placing a predetermined port value into said destination port field; and

,

placing a DIAL command in said data field.

3. The method of claim 2, wherein said transferring step comprises the step of:

extracting said predetermined port value from said destination port field of said dial packet; and

determining if said predetermined port value belongs to said dialer application; and

,

transferring said dial packet to said dialer application.

4. The method of claim 1, wherein said call command is an application programming interface command.

5. A client including:

a client processor;

an upstream device coupled to said client processor, said upstream device for sending and receiving data from a server;

a downstream device coupled to said client processor, said downstream device being a separate device from said upstream device for receiving data from said server and incapable of sending data to said server; and

,

client memory coupled to said client processor having (i) an upstream device driver for controlling said upstream device;

(ii) a downstream device driver for controlling said downstream device; and

(iii) a dialer application for establishing an upstream connection with said server using said upstream device driver in response to upstream traffic generated by an application in said client;

wherein said client memory is configured to enable said client processor to;

receiving said upstream traffic in said downstream device driver;

constructing a dial packet in said downstream device driver in response to said upstream traffic;

transferring said dial packet from said downstream device driver to said dialer application; and

,

issuing a call command to said upstream device driver.

6. The client of claim 5, wherein said dial packet contains a destination port field and a data field, and said client memory is further configured to enable said client processor to:

place a predetermined port value into said destination port field; and

,

place a DIAL command in said data field.

7. The client of claim 6, wherein said client memory is further configured to enable said client processor to:

extracting said predetermined port value from said destination port field of said dial packet; and

determining if said predetermined port value belongs to said dialer application; and

,

transferring said dial packet to said dialer application.

8. The client of claim 5, wherein said call command is an application programming interface command.

9. A system comprising:

a server; and

a client coupled to said server, said client including;

a client processor;

an upstream device coupled to said client processor, said upstream device for sending and receiving data from said server;

a downstream device coupled to said client processor, said downstream device being a separate device from said upstream device for receiving data from said server and incapable of sending data to said server; and

,

client memory coupled to said client processor having (i) an upstream device driver for controlling said upstream device;

(ii) a downstream device driver for controlling said downstream device; and

(iii) a dialer application for establishing an upstream connection with said server using said upstream device driver in response to upstream traffic generated by an application in said client;

wherein said client memory is configured to enable said client processor to;

receiving said upstream traffic in said downstream device driver;

constructing a dial packet in said downstream device driver in response to said upstream traffic;

transferring said dial packet from said downstream device driver to said dialer application; and

,

issuing a call command to said upstream device driver.

10. The system of claim 9, wherein said dial packet contains a destination port field and a data field, and said client memory is further configured to enable said client processor to:

place a predetermined port value into said destination port field; and

,

place a DIAL command in said data field.

11. The system of claim 10, wherein said client memory is further configured to enable said client processor to:

extracting said predetermined port value from said destination port field of said dial packet; and

determining if said predetermined port value belongs to said dialer application; and

,

transferring said dial packet to said dialer application.

12. The system of claim 9, wherein said call command is an application programming interface command.