Abstract: A method at an aggregator includes: storing previous search results resulting from previous client search requests, and for each previous search result, a previous handling indicator, indicating a relevance of the previous search result to the client; receiving, from the client, a search request containing search parameters; in response to the search request, selecting a subset of previous search results based on correspondence between attributes of the previous search results and the search parameters, and on the previous handling indicators; providing, to a supplier, the search request and auxiliary search parameters corresponding to the selected previous search results and indicating characteristics of the selected previous search results, for generation of current search results at the supplier employing the auxiliary search parameters as inputs; receiving, from the supplier, the current search results generated at the supplier; and returning at least one of the current search results to the client.

Abstract: A method at an aggregator includes: storing previous search results resulting from previous client search requests, and for each previous search result, a previous handling indicator, indicating a relevance of the previous search result to the client; receiving, from the client, a search request containing search parameters; in response to the search request, selecting a subset of previous search results based on correspondence between attributes of the previous search results and the search parameters, and on the previous handling indicators; providing, to a supplier, the search request and auxiliary search parameters corresponding to the selected previous search results and indicating characteristics of the selected previous search results, for generation of current search results at the supplier employing the auxiliary search parameters as inputs; receiving, from the supplier, the current search results generated at the supplier; and returning at least one of the current search results to the client.

Abstract: A method at an aggregator includes: storing previous search results resulting from previous client search requests, and for each previous search result, a previous handling indicator, indicating a relevance of the previous search result to the client; receiving, from the client, a search request containing search parameters; in response to the search request, selecting a subset of previous search results based on correspondence between attributes of the previous search results and the search parameters, and on the previous handling indicators; providing, to a supplier, the search request and auxiliary search parameters corresponding to the selected previous search results and indicating characteristics of the selected previous search results, for generation of current search results at the supplier employing the auxiliary search parameters as inputs; receiving, from the supplier, the current search results generated at the supplier; and returning at least one of the current search results to the client.

Abstract: A method includes: at an aggregator, storing historical data representing: (i) a plurality of previous search requests received at the aggregator, and (ii) for each previous search request, an outcome indicator defining whether a supplier subsystem generated previous search results meeting a relevance threshold in response to the previous search request; receiving, at the aggregator from a client subsystem, a search request containing a set of client search parameters; in response to receiving the search request, determining, based on the search request and the historical data, a likelihood of the supplier subsystem generating search results meeting the relevance threshold; and selecting, according to the likelihood, a routing action for the search request, relative to the supplier subsystem.

Abstract: A device, system and method for providing provider objects from a cache is provided. Provider objects are received representing items provided by provider systems. The provider objects are categorized by reusability and/or context characteristics and stored as categorized. A request is received for one or more items provided by the one or more provider systems. A stored and categorized provider object is determined to meet criteria associated with the request, including one or more of a respective reusability and respective context characteristics of the provider object. In response to determining that the provider object, that meets the criteria, is estimated to be currently valid, a response corresponding to the provider object is provided.

Abstract: Search requests are processed in a distributed database environment which includes a frontend module, one or more clients, a cache, a live data source, and multiple data records. Each data record includes at least one stable data piece stored in the cache and at least one volatile data piece. The frontend module receives a search request from a client and retrieves from the cache a set of data records. Each stable data piece in the set of data records corresponds to search criteria indicated in the search request. Current volatile data pieces, which correspond to the stable data pieces of the retrieved set of data records, are retrieved by the frontend module from the live data source for the retrieved set of data records. A completed set of data records is generated by combining the stable data pieces and the current volatile data pieces, and returned to the requesting client.

Abstract: Search requests are processed in a distributed database environment which includes a frontend module, one or more clients, a cache, a live data source, and multiple data records. Each data record includes at least one stable data piece stored in the cache and at least one volatile data piece. The frontend module receives a search request from a client and retrieves from the cache a set of data records. Each stable data piece in the set of data records corresponds to search criteria indicated in the search request. Current volatile data pieces, which correspond to the stable data pieces of the retrieved set of data records, are retrieved by the frontend module from the live data source for the retrieved set of data records. A completed set of data records is generated by combining the stable data pieces and the current volatile data pieces, and returned to the requesting client.

Abstract: A device, system and method for providing provider objects from a cache is provided. Provider objects are received representing items provided by provider systems. The provider objects are categorized by reusability and/or context characteristics and stored as categorized. A request is received for one or more items provided by the one or more provider systems. A stored and categorized provider object is determined to meet criteria associated with the request, including one or more of a respective reusability and respective context characteristics of the provider object. In response to determining that the provider object, that meets the criteria, is estimated to be currently valid, a response corresponding to the provider object is provided.

Abstract: Systems for managing pricing proposals and associated options in the travel industry with respect to the provision of travel services or products. The system is capable of communicating with a booking engine and a global distribution system (GDS), and is operable by a reservation agent. An itinerary pricing User Interface determines an itinerary for one or more predetermined passenger, segment, and option combinations, sends one or more informative pricing requests to the GDS, and receives as a result of the requests one or more pricing proposals for each predetermined passenger, segment and option combination from the GDS. A pricing summary module and User Interface stores each pricing proposal, such that the one or more pricing proposals are available for subsequent use. The pricing summary User Interface provides an intuitive representation of the one or more pricing proposals in order to compare the pricing proposals.