Method and system for an ontology based request/reply service
First Claim
1. A system for an ontology-based request/reply service (RRS), comprising:
- a storage which is configured to store an RRS ontology; and
a processor cooperatively operable with the storage, and configured to;
host a plurality of different request/reply services (RRS), each different RRS is dedicated to represent a different unique service and to provide connections from a client to a server instance of the different unique service, each different RRS is accessible by client instances and server instances through a same independent communication layer (ICL) that handles different transport protocols between different platforms;
receive, from the client through the ICL, a request that indicates a unique service and determine which RRS of the different RRSs is dedicated to represent the unique service which is indicated in the request;
determine whether the RRS, that is dedicated to represent the unique service indicated in the request, is already instantiated and available for communications with the client, so as to not re-instantiate the RRS,instantiate an RRS of one of the different RRSs which is determined to not be already instantiated and available for communications, the RRS being instantiated according to an individual RRS ontology stored in the RRS ontology, wherein the individual RRS ontology provides a syntactical and semantical framework to establish processing which is dedicated to represent the unique service, wherein the one of the different RRSs has a plurality of subordinate RRSs instantiated corresponding to each of a plurality of unique services;
route the request which is received by the one RRS to the instantiated RRS of the different RRSs which is the subordinate RRS and is determined to be dedicated to represent the unique service which is indicated in the request, and then route the request through a server instance corresponding to the unique service indicated in the request to the subordinate RRS, to process the request and to return, from the subordinate RRS via the one RRS to the client, a response to satisfy the request; and
manage transport connectivity and mutual communication between a plurality of clients and the plurality of different RRSs, mutual communication between the plurality of different RRSs, and mutual communication between the plurality of different RRSs and a plurality of server instances.
1 Assignment
0 Petitions
Accused Products
Abstract
In a method, system, or computer-readable medium for an ontology-based request/reply service (RRS), different request/reply services (RRS) are hosted, each different RRS dedicatedly represents a different unique service and provides connections from client to server instance of the unique service, each different RRS accessed by client and server instances through a same independent communication layer (ICL). A request from the client is received through the ICL. The RRS is determined by the unique service indicated in the request, and instantiated dynamically as needed, according to an individual RRS ontology which establishes a syntactical and semantical framework dedicated to the unique service. The request is routed to the RRS and then through a server instance of the unique service to process the request; then a response is returned to the client to satisfy the request. It provides transport connectivity and mutual communication between combinations of clients, different RRSs, and server instances.
-
Citations
20 Claims
-
1. A system for an ontology-based request/reply service (RRS), comprising:
-
a storage which is configured to store an RRS ontology; and a processor cooperatively operable with the storage, and configured to; host a plurality of different request/reply services (RRS), each different RRS is dedicated to represent a different unique service and to provide connections from a client to a server instance of the different unique service, each different RRS is accessible by client instances and server instances through a same independent communication layer (ICL) that handles different transport protocols between different platforms; receive, from the client through the ICL, a request that indicates a unique service and determine which RRS of the different RRSs is dedicated to represent the unique service which is indicated in the request; determine whether the RRS, that is dedicated to represent the unique service indicated in the request, is already instantiated and available for communications with the client, so as to not re-instantiate the RRS, instantiate an RRS of one of the different RRSs which is determined to not be already instantiated and available for communications, the RRS being instantiated according to an individual RRS ontology stored in the RRS ontology, wherein the individual RRS ontology provides a syntactical and semantical framework to establish processing which is dedicated to represent the unique service, wherein the one of the different RRSs has a plurality of subordinate RRSs instantiated corresponding to each of a plurality of unique services; route the request which is received by the one RRS to the instantiated RRS of the different RRSs which is the subordinate RRS and is determined to be dedicated to represent the unique service which is indicated in the request, and then route the request through a server instance corresponding to the unique service indicated in the request to the subordinate RRS, to process the request and to return, from the subordinate RRS via the one RRS to the client, a response to satisfy the request; and manage transport connectivity and mutual communication between a plurality of clients and the plurality of different RRSs, mutual communication between the plurality of different RRSs, and mutual communication between the plurality of different RRSs and a plurality of server instances. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A method for an ontology-based request/reply service (RRS), comprising:
-
hosting, by a processor, a plurality of different request/reply services (RRS), each different RRS is dedicated to represent a different unique service and to provide connections from a client to a server instance of the different unique service, each different RRS is accessible by client instances and server instances through a same independent communication layer (ICL) that handles different transport protocols between different platforms; receiving, by the processor from the client through the ICL, a request that indicates a unique service and determine which RRS of the different RRSs is dedicated to represent the unique service which is indicated in the request; determining whether the RRS, that is dedicated to represent the unique service indicated in the request, is already instantiated and available for communications with the client, so as to not re-instantiate the RRS, instantiating, by the processor, an RRS of one of the different RRSs which is determined to not be already instantiated and available for communications, the RRS being instantiated according to an individual RRS ontology stored in an RRS ontology provided in a storage, wherein the individual RRS ontology provides a syntactical and semantical framework to establish processing which is dedicated to represent the unique service, wherein the one of the different RRSs has a plurality of subordinate RRSs instantiated corresponding to each of a plurality of unique services; routing, by the processor, the request which is received by the one RRS, to the instantiated RRS of the different RRSs which is the subordinate RRS and is determined to be dedicated to represent the unique service which is indicated in the request, and then routing, by the processor, the request through a server instance corresponding to the unique service indicated in the request to the subordinate RRS, to process the request and then returning, from the subordinate RRS via the one RRS to the client, a response to satisfy the request; and managing, by the processor, transport connectivity and mutual communication between a plurality of clients and the plurality of different RRSs, mutual communication between the plurality of different RRSs, and mutual communication between the plurality of different RRSs and a plurality of server instances. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16)
-
-
17. A non-transitory computer readable medium comprising executable instructions for a method for an ontology-based request/reply service (RRS), the instructions being executed by a processor to perform:
-
providing a storage which is configured to store an RRS ontology; hosting a plurality of different request/reply services (RRS), each different RRS is dedicated to represent a different unique service and to provide connections from a client to a server instance of the different unique service, each different RRS is accessible by client instances and server instances through a same independent communication layer (ICL) that handles different transport protocols between different platforms; receiving, from the client through the ICL, a request that indicates a unique service and determine which RRS of the different RRSs is dedicated to represent the unique service which is indicated in the request; determining whether the RRS, that is dedicated to represent the unique service indicated in the request, is already instantiated and available for communications with the client, so as to not re-instantiate the RRS, instantiating an RRS of one of the different RRSs which is determined to not be already instantiated and available for communications, the RRS being instantiated according to an individual RRS ontology stored in the RRS ontology provided in the storage, wherein the individual RRS ontology provides a syntactical and semantical framework to establish processing which is dedicated to represent the unique service, wherein the one of the different RRSs has a plurality of subordinate RRSs instantiated corresponding to each of a plurality of unique services; routing the request which is received by the one RRS to the instantiated RRS of the different RRSs which is the subordinate RRS and is determined to be dedicated to represent the unique service which is indicated in the request, and then routing the request through a server instance corresponding to the unique service indicated in the request to the subordinate RRS, to process the request and then returning, from the subordinate RRS via the one RRS to the client, a response to satisfy the request; and managing transport connectivity and mutual communication between a plurality of clients and the plurality of different RRSs, mutual communication between the plurality of different RRSs, and mutual communication between the plurality of different RRSs and a plurality of server instances. - View Dependent Claims (18, 19, 20)
-
Specification