API and business language schema design framework for message exchanges
US-9201711-B2 · Dec 1, 2015 · US
US9697056B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9697056-B2 |
| Application number | US-201514920949-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 23, 2015 |
| Priority date | Nov 24, 2003 |
| Publication date | Jul 4, 2017 |
| Grant date | Jul 4, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A plurality of application servers hosts a plurality of business applications. A plurality of Application Program Interface (API) servers host a plurality of APIs to provide programmatic access to the plurality of business applications, each of the APIs configured to receive request messages compiled by a remote client application. An example method includes receiving a plurality of request messages generated by the remote client application, each request message requesting an activity to be performed by the targeted API, with respect to an associated application, and comprising at least one data component, and a request component including a reusable identified schema definition specific to the targeted API.
Opening claim text (preview).
What is claimed is: 1. A method of facilitating an exchange of messages between a remote client application and a server system, the server system being capable of supporting a plurality of application program interfaces (APIs) that includes a targeted API, the method including: receiving a plurality of request messages generated by the remote client application, each request message requesting an activity to be performed by the targeted API, with respect to an associated application, and comprising: at least one data component, and a request component including a reusable identified schema definition specific to the targeted API. 2. The method of claim 1 , wherein the at least one data component is common to each of the plurality of request messages and is selected from a group comprising a predetermined required level of detail, an error language component and a version identifier. 3. The method of claim 1 , wherein each of the plurality of APIs is configured to generate a response message that is sent to the remote client application, responsive to a received request message. 4. The method of claim 3 , wherein the response message includes an acknowledgement component for acknowledging receipt of the request message, a correlation identifier, a timestamp, error data and version data. 5. A method of facilitating an exchange of messages between a remote client application and a server system, the server system being capable of supporting a plurality of application program interfaces (APIs) that includes a targeted API, the method including: receiving a plurality of request messages generated by the remote client application, each request message requesting an activity to be performed by the targeted API, with respect to an associated application, and comprising at least one data component, and a request component including a reusable identified schema definition specific to the targeted API; extracting the at least one data component and the request component from the request message; and performing the activity requested by the request message. 6. The method of claim 5 , including performing version and error check operations. 7. The method of claim 5 , including generating a response message that is sent from the server system to the remote client application. 8. The method to claim 7 , wherein the generating of the response message includes generating an acknowledgement, a timestamp, a correlation identifier, error data and version data. 9. A non-transitory machine-readable storage device comprising instructions which, when executed by a machine, cause the machine to perform operations of facilitating an exchange of messages in a trading system between a remote client application and a server system, the server system being capable of supporting a plurality of application program interfaces, the operations comprising: receiving a plurality of request messages compiled by the remote client application, each of the plurality of request messages comprising at least one data component, and a request component that includes a reusable identified schema definition specific to one of the plurality of application program interfaces, to support the functionality of the requested application program interface; extracting the at least one data component and the request component from the request message; and performing the activity requested by the request message. 10. The machine-readable storage device of claim 9 , the operations further comprising performing version and error check operations. 11. The machine-readable storage device of claim 9 , the operations further comprising generating a response message that is to be sent from the server system to the remote client application. 12. The machine-readable storage device of claim 11 , the operations further comprising generating an acknowledgement, a timestamp, a correlation identifier, error data and version data.
Interprogram communication · CPC title
Auctions · CPC title
Execution arrangements for user interfaces · CPC title
Client-server · CPC title
in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.