Patent US6904598B2 successfully refreshed from Google Patents.
US6904598B2
Expired / Lapsed
US
⏱️ 0.0 years remaining
COBOL metamodel
Assignee: eBay Inc
•
Filing: 2001-05-04
•
Granted: 2005-06-07
•
Expires: 2021-05-04
Abstract
Abstract A method of and a system for processing an enterpise an application request on an end user application and an application server. This is accomplished by initiating the application request on the end user application in a first language (such as a markup language) with a first application program (such as a Web browser), and transmitting the application request to the server and converting the application from the first language of the first end user application to a language running on the application server, processing the application request on the application server, and transmitting the response from the application server back to the end user application, and converting the response from the language running on the application server to the language of the end user application. The end user application and the application server have at least one connector between them, and the steps of (i) converting the application request from the language of the end user application (as a source language) to the language running on the application server (as a target language), and (ii) converting the response to the application request from the language running on the application server (as a source language) to the language of the end user application (as a target language), each include the steps of invoking connector metamodels of the respective source and target languages, populating the connector metamodels with metamodel data of each of the respective source and target languages, and converting the source language to the target language.
Inventors
- 👤 Shahaf Abileah
- 👤 Alan Roeder Elderon
- 👤 Shyh-Mei F. Ho
- 👤 II James Rush Rhyne
- 👤 William Nicholas John Tindall
- 👤 Tony Y Tsai
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-30 16:34
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/547; G06F8/00; G06F8/20; G06F9/541; G06F9/548
Claims Analysis
Total Claims: 54
Claim 1
Independent Claim
248 words
A method of processing an application request on an end user application and an application server comprising: a) initiating the application request on the end user application in a first language with a first application program; b) transmitting the application request to the application server and converting the application request from the first language of the first end user application to COBOL running on the application server; c) processing said application request on the application server; d) transmitting a response to the application request from the application server to the end user application, and converting the response to the application request from the COBOL running on the application server to the first language of the first end user application; and e) wherein the end user application and the application server have at least one connector therebetween, and the steps of (i) converting the application request from the first language of the first end user application as a source language to the COBOL running on the application server as a target language, and (ii) converting a response to the application request from the COBOL running on the application server as a source language to the first language of the first end user application as a target language, each comprise the steps of: 1) invoking connector metamodels of respective source and target languages; 2) populating the connector metamodels with metamodel data of each of the respective source and target languages; and 3) converting the source language to the target language.
Claim 2
Independent Claim
248 words
A method of processing an application request on an end user application and an application server comprising: a) initiating the application request on the end user application in a first language with a first application program; b) transmitting the application request to the application server and converting the application request from the first language of the first end user application to COBOL running on the application server; c) processing said application request on the application server; d) transmitting a response to the application request from the application server to the end user application, and converting the response to the application request from the COBOL running on the application server to the first language of the first end user application; and e) wherein the end user application and the application server have at least one connector therebetween, and the steps of (i) converting the application request from the first language of the first end user application as a source language to the COBOL running on the application server as a target language, and (ii) converting a response to the application request from the COBOL running on the application server as a source language to the first language of the first end user application as a target language, each comprise the steps of: 1) invoking connector metamodels of respective source and target languages; 2) populating the connector metamodels with metamodel data of each of the respective source and target languages; and 3) converting the source language to the target language.
Claim 3
Dependent Claim
14 words
The method of claim 1 wherein the end user application is a web browser.
Claim 4
Dependent Claim
27 words
The method of claim 2 wherein the end user application is connected to the application server through a web server, and the web server comprises a connector.
Claim 5
Dependent Claim
23 words
The method of claim 1 wherein the metamodel metadata comprises invocation metamodel metadata, application domain interface metamodel metadata, and type descriptor metamodel metadata.
Claim 6
Dependent Claim
35 words
The method of claim 4 wherein the invocation metamodel metadata is chosen from the group consisting of message control information, security data, transactional semantics, trace and debug information, pre-condition and post-condition resources, and user data.
Claim 7
Dependent Claim
22 words
The method of claim 4 wherein the application domain interface metamodel metadata comprises input parameter signatures, output parameter signatures, and return types.
Claim 8
Dependent Claim
17 words
The method of claim 4 wherein the application domain interface metamodel metadata further includes language metamodel metadata.
Claim 9
Dependent Claim
18 words
The method of claim 7 wherein the language metamodel metadata includes mappings between the source and target languages.
Claim 10
Dependent Claim
24 words
The method of claim 8 wherein the source language is object oriented, and the language metamodel metadata maps encapsulated objects into code and data.
Claim 11
Dependent Claim
17 words
The method of claim 9 wherein the language metamodel metadata maps object inheritances into references and pointers.
Claim 12
Dependent Claim
23 words
The method of claim 4 wherein the type descriptor metamodel metadata defines physical realizations, storage mapping, data types, data structures, and realization constraints.
Claim 13
Dependent Claim
41 words
The method of claim 1 wherein processing the application request relates to a rich transaction comprising a plurality of individual transactions, and wherein the plurality of individual transactions are processed on one end user application and a plurality of application servers.
Claim 14
Dependent Claim
13 words
The method of claim 12 comprising passing individual transactions among individual application servers.
Claim 15
Dependent Claim
338 words
A transaction processing system comprising a client, a server, and at least one connector therebetween, a) the client having an end user application, and being controlled and configured to initiate an application request with the server in a first language with a first application program and to transmit the application request to the server; b) the connector being configured and controlled to receive the application request from the client, convert the application request from the first language of the first end user application running on the client to COBOL running on the server; c) the server being configured and controlled to receive the converted application request from the connector and process the application request in COBOL with a second application program residing on the server, and to thereafter transmit a response to the application request through the connector back to the first application program on the client; d) the connector being configured and controlled to receive the response to the application request from the server, to convert the response to the application request from the COBOL running on the application server to the first language of the first application program running on the client; and e) wherein the connector between the client and the server is configured and controlled to (i) convert the application request from the first language of the first application on the client as a source language to the COBOL running on the application server as a target language, and (ii) convert the response to the application request from the COBOL running on the application server as a source language to the first language of the first application running on the client as a target language, each by a method comprising: 1) retrieving connector metamodels of respective source and target languages from a metamodel metadata repository; 2) populating the connector metamodels with metamodel data from the metamodel metadata repository for each of the respective source and target languages; and 3) invoking the retrieved, populated connector metamodels and converting the source language to the target language.
Claim 16
Dependent Claim
338 words
A transaction processing system comprising a client, a server, and at least one connector therebetween, a) the client having an end user application, and being controlled and configured to initiate an application request with the server in a first language with a first application program and to transmit the application request to the server; b) the connector being configured and controlled to receive the application request from the client, convert the application request from the first language of the first end user application running on the client to COBOL running on the server; c) the server being configured and controlled to receive the converted application request from the connector and process the application request in COBOL with a second application program residing on the server, and to thereafter transmit a response to the application request through the connector back to the first application program on the client; d) the connector being configured and controlled to receive the response to the application request from the server, to convert the response to the application request from the COBOL running on the application server to the first language of the first application program running on the client; and e) wherein the connector between the client and the server is configured and controlled to (i) convert the application request from the first language of the first application on the client as a source language to the COBOL running on the application server as a target language, and (ii) convert the response to the application request from the COBOL running on the application server as a source language to the first language of the first application running on the client as a target language, each by a method comprising: 1) retrieving connector metamodels of respective source and target languages from a metamodel metadata repository; 2) populating the connector metamodels with metamodel data from the metamodel metadata repository for each of the respective source and target languages; and 3) invoking the retrieved, populated connector metamodels and converting the source language to the target language.
Claim 17
Dependent Claim
14 words
The system of claim 14 wherein the end user application is a web browser.
Claim 18
Dependent Claim
27 words
The system of claim 15 wherein the end user application is connected to the application server through a web server, and the web server comprises a connector.
Claim 19
Dependent Claim
23 words
The system of claim 14 wherein the metamodel metadata comprises invocation metamodel metadata, application domain interface metamodel metadata, and type descriptor metamodel metadata.
Claim 20
Dependent Claim
35 words
The system of claim 17 wherein the invocation metamodel metadata is chosen from the group consisting of message control information, security data, transactional semantics, trace and debug information, pre-condition and post-condition resources, and user data.
Claim 21
Dependent Claim
23 words
The system of claim 18 wherein the type descriptor metamodel metadata defines physical realizations, storage mapping, data types, data structures, and realization constraints.
Claim 22
Dependent Claim
22 words
The system of claim 17 wherein the application domain interface metamodel metadata comprises input parameter signatures, output parameter signatures, and return types.
Claim 23
Dependent Claim
17 words
The system of claim 17 wherein the application domain interface metamodel metadata further includes language metamodel metadata.
Claim 24
Dependent Claim
18 words
The system of claim 21 wherein the language metamodel metadata includes mappings between the source and target languages.
Claim 25
Dependent Claim
24 words
The system of claim 22 wherein the source language is object oriented, and the language metamodel metadata maps encapsulated objects into code and data.
Claim 26
Dependent Claim
17 words
The system of claim 23 wherein the language metamodel metadata maps object inheritances into references and pointers.
Claim 27
Dependent Claim
23 words
The system of claim 14 wherein said system has a plurality of application servers and is configured and controlled to process rich transactions.
Claim 28
Dependent Claim
353 words
A transaction processing system configured and controlled to interact with a client application, and comprising a server and at least one connector between the server and the client application, wherein: a) the client has an end user application, and is controlled and configured to initiate an application request with the server in a first language with a first application program and to transmit the application request to the server; b) the connector being configured and controlled to receive the application request from the client, convert the application request from the first language of the first end user application running on the client to the COBOL running on the server; c) the server being configured and controlled to receive the converted application request from the connector and process the application request in the COBOL with a second application program residing on the server, and to thereafter transmit a response to the application request through the connector back to the first application program on the client; d) the connector being configured and controlled to receive the response to the application request from the server, to convert the response to the application request from the COBOL running on the server to the first language of the first application program running on the client; and e) wherein the connector between the client and the server is configured and controlled to (i) convert the application request from the first language of the client application on the client as a source language to the COBOL running on the server as a target language, and (ii) convert the response to the application request from the COBOL running on the server as a source language to the first language of the client application running on the client as a target language, each by a method comprising: 1) retrieving connector metamodel metadata of respective source and target languages from a metamodel metadata repository; 2) populating the connector metamodels with metamodel data of each of the respective source and target languages from the metamodel metadata repository and invoking the retrieved, populated connector metamodels; and 3) converting the source language to the target language.
Claim 29
Dependent Claim
353 words
A transaction processing system configured and controlled to interact with a client application, and comprising a server and at least one connector between the server and the client application, wherein: a) the client has an end user application, and is controlled and configured to initiate an application request with the server in a first language with a first application program and to transmit the application request to the server; b) the connector being configured and controlled to receive the application request from the client, convert the application request from the first language of the first end user application running on the client to the COBOL running on the server; c) the server being configured and controlled to receive the converted application request from the connector and process the application request in the COBOL with a second application program residing on the server, and to thereafter transmit a response to the application request through the connector back to the first application program on the client; d) the connector being configured and controlled to receive the response to the application request from the server, to convert the response to the application request from the COBOL running on the server to the first language of the first application program running on the client; and e) wherein the connector between the client and the server is configured and controlled to (i) convert the application request from the first language of the client application on the client as a source language to the COBOL running on the server as a target language, and (ii) convert the response to the application request from the COBOL running on the server as a source language to the first language of the client application running on the client as a target language, each by a method comprising: 1) retrieving connector metamodel metadata of respective source and target languages from a metamodel metadata repository; 2) populating the connector metamodels with metamodel data of each of the respective source and target languages from the metamodel metadata repository and invoking the retrieved, populated connector metamodels; and 3) converting the source language to the target language.
Claim 30
Dependent Claim
14 words
The system of claim 26 wherein the end user application is a web browser.
Claim 31
Dependent Claim
27 words
The system of claim 27 wherein the end user application is connected to the application server through a web server, and the web server comprises a connector.
Claim 32
Dependent Claim
23 words
The system of claim 26 wherein the metamodel metadata comprises invocation metamodel metadata, application domain interface metamodel metadata, and type descriptor metamodel metadata.
Claim 33
Dependent Claim
35 words
The system of claim 29 wherein the invocation metamodel metadata is chosen from the group consisting of message control information, security data, transactional semantics, trace and debug information, pre-condition and post-condition resources, and user data.
Claim 34
Dependent Claim
22 words
The system of claim 29 wherein the application domain interface metamodel metadata comprises input parameter signatures, output parameter signatures, and return types.
Claim 35
Dependent Claim
17 words
The system of claim 29 wherein the application domain interface metamodel metadata further includes language metamodel metadata.
Claim 36
Dependent Claim
18 words
The system of claim 32 wherein the language metamodel metadata includes mappings between the source and target languages.
Claim 37
Dependent Claim
24 words
The system of claim 33 wherein the source language is object oriented, and the language metamodel metadata maps encapsulated objects into code and data.
Claim 38
Dependent Claim
31 words
The method of claim 33 wherein the source language and the target language are different object oriented languages, and the language metamodel metadata maps encapsulated code and data between the languages.
Claim 39
Dependent Claim
17 words
The system of claim 33 wherein the language metamodel metadata maps object inheritances into references and pointers.
Claim 40
Dependent Claim
23 words
The system of claim 29 wherein the type descriptor metamodel metadata defines physical realizations, storage mapping, data types, data structures, and realization constraints.
Claim 41
Dependent Claim
23 words
The system of claim 26 wherein said system has a plurality of application servers and is configured and controlled to process rich transactions.
Claim 42
Dependent Claim
99 words
A program product comprising a computer-readable storage medium having invocation metamodel metadata, application domain interface metamodel metadata, and language metamodel metadata; computer instructions for building a metamodel metadata repository of source and target language metamodel metadata; and computer instructions to build a connector for: 1) retrieving connector metamodel metadata of respective source and target languages from the metamodel metadata repository; 2) populating the connector metamodels with metamodel data of each of the respective source and target languages from the metamodel metadata repository and invoking the retrieved, populated connector metamodels; and 3) converting the source language to the target language.
Claim 43
Dependent Claim
99 words
A program product comprising a computer-readable storage medium having invocation metamodel metadata, application domain interface metamodel metadata, and language metamodel metadata; computer instructions for building a metamodel metadata repository of source and target language metamodel metadata; and computer instructions to build a connector for: 1) retrieving connector metamodel metadata of respective source and target languages from the metamodel metadata repository; 2) populating the connector metamodels with metamodel data of each of the respective source and target languages from the metamodel metadata repository and invoking the retrieved, populated connector metamodels; and 3) converting the source language to the target language.
Claim 44
Dependent Claim
22 words
The program product of claim 39 wherein the computer-readable storage medium includes computer instructions for building connector stubs from said metamodel metadata.
Claim 45
Dependent Claim
27 words
The program product of claim 39 wherein the metamodel metadata in the repository comprises invocation metamodel metadata, application domain interface metamodel metadata, and type descriptor metamodel metadata.
Claim 46
Dependent Claim
36 words
The program product of claim 41 wherein the invocation metamodel metadata is chosen from the group consisting of message control information, security data, transactional semantics, trace and debug information, pre-condition and post-condition resources, and user data.
Claim 47
Dependent Claim
24 words
The program product of claim 42 wherein the type descriptor metamodel metadata defines physical realizations, storage mapping, data types, data structures, and realization constraints.
Claim 48
Dependent Claim
23 words
The program product of claim 41 wherein the application domain interface metamodel metadata comprises input parameter signatures, output parameter signatures, and return types.
Claim 49
Dependent Claim
18 words
The program product of claim 41 wherein the application domain interface metamodel metadata further includes language metamodel metadata.
Claim 50
Dependent Claim
19 words
The program product of claim 45 wherein the language metamodel metadata includes mappings between the source and target languages.
Claim 51
Dependent Claim
25 words
The program product of claim 46 wherein the source language is object oriented, and the language metamodel metadata maps encapsulated objects into code and data.
Claim 52
Dependent Claim
18 words
The program product of claim 46 wherein the language metamodel metadata maps object inheritances into references and pointers.
Claim 53
Dependent Claim
12 words
The program product of claim 39 wherein the source language is COBOL.
Claim 54
Dependent Claim
12 words
The program product of claim 39 wherein the target language is COBOL.
References Cited (Backward Citations)
US6233542B1
Cited
US6094688A
Cited
US20030191970A1
Cited
US6738975B1
Cited
US6253366B1
Cited
US6654784B1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2008-06-06 | 2008-12-06 | 2009-06-07 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2012-06-06 | 2012-12-06 | 2013-06-07 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2016-06-06 | 2016-12-06 | 2017-06-07 | $7700.00 | Window Closed / Lapsed |