US6085250A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method and system for using layered networking application program interfaces (APIs) using a native asynchronous transfer mode (ATM) API
Assignee: Sagemcom Broadband SAS
•
Filing: 1997-03-20
•
Granted: 2000-07-04
•
Expires: 2017-03-20
Abstract
Abstract This invention provides a system for transparently mapping user level non-asynchronous transfer mode (ATM) sockets to an ATM virtual channel circuit associated with an operating system of a computer workstation and includes an ATM middleware subsystem for receiving a plurality of ATM extension calls from a non-ATM aware application and translating the plurality of ATM extension calls to a plurality of native ATM API calls. A configuration data base stores translation data for translating the ATM extension calls from the non-ATM application to the native ATM API calls. A WinSocket™ application receives the native ATM API calls from the ATM middleware subsystem and responsively generates signals for controlling the operating system according to the contents of the native ATM API calls. The ATM middleware system further generates formatted calls to the operating system from the plurality of ATM extension calls according to preexisting protocols associated with the operating system.
Inventors
- 👤 William A. Perry
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-03 11:47
CPC Classifications
H; H04; H04Q; H04Q11/00; H04Q11/04; H04Q11/0428; H04Q11/0478; H04L; H04L12/00; H04L12/54; H04L12/56; H04L12/5601; H04L2012/5614; H04L2012/5616; H04L2012/5617; H04L2012/5629; H04L2012/563
Claims Analysis
Total Claims: 22
Claim 1
Independent Claim
119 words
A system for transparently mapping user level non-asynchronous transfer mode (non-ATM) sockets to an ATM virtual channel circuit associated with an operating system of a computer, comprising: an ATM middleware subsystem operable to intercept an extension call associated with the operating system from a non-ATM aware application and, using translation data, translating said extension call to an ATM API call; an ATM middleware service operable to determine whether an application comprises an ATM -aware application and controlling said ATM middleware subsystem in response to the determination; and a configuration data base accessible through said ATM middleware service and operable to store said translation data for translating said extension call from said non-ATM aware application to said ATM API call.
Claim 2
Independent Claim
119 words
A system for transparently mapping user level non-asynchronous transfer mode (non-ATM) sockets to an ATM virtual channel circuit associated with an operating system of a computer, comprising: an ATM middleware subsystem operable to intercept an extension call associated with the operating system from a non-ATM aware application and, using translation data, translating said extension call to an ATM API call; an ATM middleware service operable to determine whether an application comprises an ATM -aware application and controlling said ATM middleware subsystem in response to the determination; and a configuration data base accessible through said ATM middleware service and operable to store said translation data for translating said extension call from said non-ATM aware application to said ATM API call.
Claim 3
Dependent Claim
23 words
The system of claim 1, further comprising instructions within said ATM middleware for providing quality of service functions to said non-ATM aware application.
Claim 4
Dependent Claim
22 words
The system of claim 1, further comprising instructions within said ATM middleware for providing traffic management functions to said non-ATM aware application.
Claim 5
Dependent Claim
22 words
The system of claim 1, further comprising instructions within said ATM middleware for providing rate control functions to said non-ATM aware application.
Claim 6
Dependent Claim
23 words
The system of claim 1, wherein said extension call from said non-ATM aware application comprises a plurality of binary calls without ATM functionality.
Claim 7
Dependent Claim
25 words
The system of claim 1, wherein said ATM middleware subsystem comprises a plurality of dynamic link or shared libraries for accessing a configuration data base.
Claim 8
Dependent Claim
22 words
The system of claim 1, wherein said non-ATM aware application, said ATM middleware and said sockets are external to said operating system.
Claim 9
Independent Claim
80 words
A method for transparently mapping user level non-asynchronous transfer mode (non-ATM) sockets to an ATM virtual channel circuit associated with an operating system of a computer, comprising: intercepting an extention call associated with an operating system from a non-ATM aware application; translating said extension call to an ATM API; storing translation data for translating said extension call into said ATM API call and accessing translation data stored in a configuration database, and controlling an ATM middleware subsystem in response thereto.
Claim 10
Independent Claim
80 words
A method for transparently mapping user level non-asynchronous transfer mode (non-ATM) sockets to an ATM virtual channel circuit associated with an operating system of a computer, comprising: intercepting an extention call associated with an operating system from a non-ATM aware application; translating said extension call to an ATM API; storing translation data for translating said extension call into said ATM API call and accessing translation data stored in a configuration database, and controlling an ATM middleware subsystem in response thereto.
Claim 11
Dependent Claim
20 words
The method of claim 8, further comprising the step of providing quality of service functions to said non-ATM aware application.
Claim 12
Dependent Claim
19 words
The method of claim 8, further comprising the step of providing traffic management functions to said non-ATM aware application.
Claim 13
Dependent Claim
19 words
The method of claim 8, further comprising the step of providing rate control functions to said non-ATM aware application.
Claim 14
Dependent Claim
24 words
The method of claim 8, wherein determining whether said application comprises an ATM aware application comprises accessing translation data stored in a configuration database.
Claim 15
Dependent Claim
32 words
The method of claim 8, further comprising the steps of storing translation data for translating said extension call into said ATM API call and accessing said translation data using a shared library.
Claim 16
Dependent Claim
34 words
The method of claim 8, further comprising the step of generating a TCP formatted call to an operating system from said non-ATM API call according to a preexisting protocol associated with said operating system.
Claim 17
Dependent Claim
35 words
The method of claim 8, further comprising the step of generating a UDP formatted call to said operating system from said non-ATM API call according to a preexisting UDP protocol associated with said operating system.
Claim 18
Dependent Claim
19 words
The method of claim 8, further comprising the step of determining whether an application comprises an ATM aware application.
Claim 19
Dependent Claim
33 words
The method of claim 8, further comprising the step of generating protocol-specific formatted calls to said operating system from said non-ATM API call according to a preexisting protocol associated within said ATM middleware.
Claim 20
Dependent Claim
33 words
The method of claim 8, further comprising the step of operating said non-ATM application and a winsocket application externally to said operating system and operating an ATM middleware internal to said operating system.
Claim 21
Independent Claim
131 words
A method for transparently mapping a non-asynchronous transfer mode (non-ATM) application programming interface (API) call to an ATM API call comprising: intercepting, at an ATM middleware, a non-ATM API call associated with an operating system from a non-ATM aware application; determining whether a remote application is ATM aware; Translating said non-ATM API call into ATM API call and communicating said ATM API call over an ATM communication link to said remote application in response to determining that said remote application is ATM aware; storing translation data for translating said extension call into said ATM API call and accessing translation data stored in a configuration database; and communicating said non-ATM API call over a non-ATM communication link to said remote application in response to determining that said remote application is non-ATM aware.
Claim 22
Independent Claim
131 words
A method for transparently mapping a non-asynchronous transfer mode (non-ATM) application programming interface (API) call to an ATM API call comprising: intercepting, at an ATM middleware, a non-ATM API call associated with an operating system from a non-ATM aware application; determining whether a remote application is ATM aware; Translating said non-ATM API call into ATM API call and communicating said ATM API call over an ATM communication link to said remote application in response to determining that said remote application is ATM aware; storing translation data for translating said extension call into said ATM API call and accessing translation data stored in a configuration database; and communicating said non-ATM API call over a non-ATM communication link to said remote application in response to determining that said remote application is non-ATM aware.
References Cited (Backward Citations)
EP0130260A1
Cited
EP0325794A2
Cited
US5231631A
Cited
US5280476A
Cited
US5274768A
Cited
US5311509A
Cited
US5535197A
Cited
US5379297A
Cited
US5617416A
Cited
US5430721A
Cited
US5420858A
Cited
US5381411A
Cited
US5726985A
Cited
US5414707A
Cited
US5732071A
Cited
US5818842A
Cited
US5629937A
Cited
US5557607A
Cited
US5572522A
Cited
US5583861A
Cited
US5592476A
Cited
US5568486A
Cited
US5455826A
Cited
US5548587A
Cited
US5490141A
Cited
US5602853A
Cited
US5625625A
Cited
US5600650A
Cited
US5822521A
Cited
US5790809A
Cited
US5701292A
Cited
US5751709A
Cited
US5745477A
Cited
US5898669A
Cited
US5852655A
Cited
US5742765A
Cited
WO1998007282A2
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2003-07-04 | 2004-01-03 | 2004-07-04 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2007-07-04 | 2008-01-03 | 2008-07-04 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2011-07-04 | 2012-01-03 | 2012-07-04 | $7700.00 | Window Closed / Lapsed |