Patent US6691302B1 successfully refreshed from Google Patents.
US6691302B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Interfacing a service component to a native API
Assignee: Unify Patente GmbH and Co KG
•
Filing: 2000-05-31
•
Granted: 2004-02-10
•
Expires: 2020-05-31
Abstract
Abstract Systems and methods for interfacing a service component written in any one of a variety of programming languages to a native operating system application program interface (API) are described. For example, in one embodiment, a generic interface between the Win32 API (application program interface) and Windows NT service components written in C, C++, and JAVA is provided. In one aspect, an interface module is configured to load a service component written in a non-native programming language. In another aspect, an interface module is configured to retrieve service component information from a configuration database.
Inventors
- 👤 Mark Skrzynski
- 👤 Huy Ton
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-08 14:30
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54
Claims Analysis
Total Claims: 36
Claim 1
Independent Claim
66 words
A system for interfacing a service component to a native operating system application program interface (API), wherein “service component” refers to a type of program that does not require interactive logon whenever running and that runs with facilitation by a service controller provided by the native operating system, the system comprising an interface module configured to load a service component written using a non-native programming language.
Claim 2
Independent Claim
66 words
A system for interfacing a service component to a native operating system application program interface (API), wherein “service component” refers to a type of program that does not require interactive logon whenever running and that runs with facilitation by a service controller provided by the native operating system, the system comprising an interface module configured to load a service component written using a non-native programming language.
Claim 3
Dependent Claim
26 words
The system of claim 1 , wherein the interface module is configured to create an application operating environment in which the service component application is operable.
Claim 4
Dependent Claim
30 words
The system of claim 2 , wherein the interface module is configured to create a JAVA virtual machine for executing a service component application written in a JAVA programming language.
Claim 5
Dependent Claim
29 words
The system of claim 2 , wherein the interface module is configured to treat the application operating environment and the service component application as a single process during execution.
Claim 6
Dependent Claim
25 words
The system of claim 4 , wherein the interface module is configured to create an application thread on which to create the application operating environment.
Claim 7
Dependent Claim
24 words
The system of claim 5 , wherein the interface module is configured to create a main thread for monitoring and blocking the application thread.
Claim 8
Dependent Claim
21 words
The system of claim 1 , wherein the interface module is configured to retrieve service component information from a configuration database.
Claim 9
Dependent Claim
28 words
The system of claim 7 , wherein the interface module is configured to retrieve from the configuration database the identity of a service component application to be executed.
Claim 10
Dependent Claim
22 words
The system of claim 8 , wherein the interface module is configured to load, run and control the identified service component application.
Claim 11
Dependent Claim
51 words
The system of claim 7 , wherein the interface module is configured to determine, based on said retrieved service component information, that said service component was written using said non-native programming language, and to create an operating environment that is appropriate for said non-native programming language, for running said service component.
Claim 12
Dependent Claim
19 words
The system of claim 1 , wherein the interface module includes a service component interface dynamic link library (DLL).
Claim 13
Dependent Claim
38 words
The system of claim 1 , wherein the interface module is operable under a Microsoft Windows Server operating system, and is configured to interface a Win32 API to service components written in C, C++ and JAVA programming languages.
Claim 14
Independent Claim
30 words
A system for interfacing a service component to a native operating system application program interface (API), comprising an interface module configured to retrieve service component information from a configuration database.
Claim 15
Independent Claim
30 words
A system for interfacing a service component to a native operating system application program interface (API), comprising an interface module configured to retrieve service component information from a configuration database.
Claim 16
Dependent Claim
28 words
The system of claim 13 , wherein the interface module is configured to retrieve from the configuration database the identity of a service component application to be executed.
Claim 17
Dependent Claim
22 words
The system of claim 14 , wherein the interface module is configured to load, run and control the identified service component application.
Claim 18
Dependent Claim
19 words
The system of claim 13 , wherein the interface module includes a service component interface dynamic link library (DLL).
Claim 19
Dependent Claim
38 words
The system of claim 13 , wherein the interface module is operable under a Microsoft Windows Server operating system, and is configured to interface a Win32 API to service components written in C, C++ and JAVA programming languages.
Claim 20
Independent Claim
61 words
A method for interfacing a service component to a native operating system application program interface (API), wherein “service component” refers to a type of program that does not require interactive logon whenever running and that runs with facilitation by a service controller provided by the native operating system, the method comprising loading a service component written using a non-native programming language.
Claim 21
Independent Claim
61 words
A method for interfacing a service component to a native operating system application program interface (API), wherein “service component” refers to a type of program that does not require interactive logon whenever running and that runs with facilitation by a service controller provided by the native operating system, the method comprising loading a service component written using a non-native programming language.
Claim 22
Dependent Claim
21 words
The method of claim 18 , further comprising creating an application operating environment in which the service component application is operable.
Claim 23
Dependent Claim
25 words
The method of claim 19 , wherein a JAVA virtual machine is created for executing a service component application written in a JAVA programming language.
Claim 24
Dependent Claim
24 words
The method of claim 19 , wherein the application operating environment and the service component application are treated as a single process during execution.
Claim 25
Dependent Claim
20 words
The method of claim 21 , further comprising creating an application thread on which to create the application operating environment.
Claim 26
Dependent Claim
19 words
The method of claim 22 , further comprising creating a main thread for monitoring and blocking the application thread.
Claim 27
Dependent Claim
16 words
The method of claim 18 , further comprising retrieving service component information from a configuration database.
Claim 28
Dependent Claim
23 words
The method of claim 24 , wherein the identity of a service component application to be executed is retrieved from the configuration database.
Claim 29
Dependent Claim
17 words
The method of claim 25 , further comprising loading, running and controlling the identified service component application.
Claim 30
Dependent Claim
34 words
The method of claim 25 , further comprising determining a language of the service component application and creating an operating environment, that is appropriate for the determined language, for running the service component application.
Claim 31
Dependent Claim
17 words
The method of claim 18 , wherein the service component is loaded by dynamic link library (DLL).
Claim 32
Independent Claim
25 words
A method for interfacing a service component to a native operating system application program interface (API), comprising retrieving service component information from a configuration database.
Claim 33
Independent Claim
25 words
A method for interfacing a service component to a native operating system application program interface (API), comprising retrieving service component information from a configuration database.
Claim 34
Dependent Claim
23 words
The method of claim 29 , wherein the identity of a service component application to be executed is retrieved from the configuration database.
Claim 35
Dependent Claim
17 words
The method of claim 30 , further comprising loading, running and controlling the identified service component application.
Claim 36
Dependent Claim
17 words
The method of claim 29 , wherein the service component is loaded by dynamic link library (DLL).
References Cited (Backward Citations)
EP0371941A2
Cited
GB2278468A
Cited
US5655154A
Cited
US5721876A
Cited
US5802367A
Cited
EP0770958A1
Cited
US5987517A
Cited
US5907701A
Cited
US6496865B1
Cited
US6185609B1
Cited
US6014666A
Cited
US6229537B1
Cited
WO2000068779A2
Cited
GB2354092A
Cited
US6405216B1
Cited
EP1126685A2
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2007-02-09 | 2007-08-11 | 2008-02-10 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2011-02-09 | 2011-08-11 | 2012-02-10 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2015-02-09 | 2015-08-11 | 2016-02-10 | $7700.00 | Window Closed / Lapsed |