US6041356A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method and apparatus for detecting network traffic and initiating a dial-up connection using separate upstream and downstream devices
Assignee: Intel Corp
•
Filing: 1997-03-31
•
Granted: 2000-03-21
•
Expires: 2017-03-31
Abstract
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.
Inventors
- 👤 Mannan Mohammed
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-07 10:26
CPC Classifications
H; H04; H04L; H04L12/00; H04L12/28; H04L12/2801
Claims Analysis
Total Claims: 15
Claim 1
Independent Claim
149 words
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.
Claim 2
Dependent Claim
149 words
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.
Claim 3
Dependent Claim
47 words
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.
Claim 4
Dependent Claim
48 words
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.
Claim 5
Dependent Claim
15 words
The method of claim 1, wherein said call command is an application programming interface command.
Claim 6
Dependent Claim
176 words
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.
Claim 7
Dependent Claim
176 words
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.
Claim 8
Dependent Claim
50 words
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.
Claim 9
Dependent Claim
53 words
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.
Claim 10
Dependent Claim
15 words
The client of claim 5, wherein said call command is an application programming interface command.
Claim 11
Independent Claim
188 words
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.
Claim 12
Independent Claim
188 words
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.
Claim 13
Dependent Claim
50 words
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.
Claim 14
Dependent Claim
53 words
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.
Claim 15
Dependent Claim
15 words
The system of claim 9, wherein said call command is an application programming interface command.
References Cited (Backward Citations)
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-03-21 | 2003-09-20 | 2004-03-21 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-03-21 | 2007-09-20 | 2008-03-21 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-03-21 | 2011-09-20 | 2012-03-21 | $7700.00 | Window Closed / Lapsed |