System and method of generating aggregated functional data

Abstract

A method of aggregating and updating heterogeneous data objects for a client subsystem includes: storing a set of data object definitions, each defining a mapping between an aggregated data object format and a plurality of supplier data object formats; storing a set of update definitions, each defining a mapping between an aggregated update operation and a plurality of supplier update mechanisms; receiving a data object in a supplier data object formats; selecting, based on the supplier data object format of the received data object, a data object definitions and generating an aggregated data object according to the selected definition; presenting the generated aggregated data object to the client subsystem; receiving an aggregated update operation from the client subsystem for updating the aggregated data object; and selecting, based on the received aggregated update operation, one of the update definitions and initiating a supplier update mechanism according to the selected update definition.

1 . A method of generating an aggregated functional data object for a client subsystem from a set of supplier data objects having different data object formats, comprising:
 storing the set of supplier data objects according to their respective data object formats, each supplier data object including a plurality of elements;   creating a further data object for linking selected supplier data objects based on common ones of said elements shared between the selected supplier data objects; and   creating the aggregated functional data object by merging and combining said common ones of said elements with remaining ones of the plurality of elements from the selected supplier data objects according to said linking, for presentation to the client subsystem.   
     
     
         2 . The method of  claim 1 , further comprising:
 receiving a request from the client subsystem to modify one of the selected supplier data objects and in response one of either creating, deleting or modifying elements of said one of the supplier data objects;   updating the linking to reflect any modification of said common ones of said elements; and   creating a further aggregated functional data object by merging and combining said common ones of said elements with said remaining ones of the plurality of elements from the selected supplier data objects, including the modified one of the selected supplier data objects, according to the updated linking, for presentation to the client subsystem.   
     
     
         3 . The method of  claim 1 , wherein each of said supplier data objects includes a distribution channel indicator indicative of its data object format. 
     
     
         4 . The method of  claim 1 , wherein each of said supplier data objects includes a record identifier. 
     
     
         5 . The method of  claim 4 , wherein each said record identifier is maintained in said further data object upon creating the aggregated functional data object. 
     
     
         6 . The method of  claim 1 , wherein the data object formats correspond to data acquired through at least one of either New Distribution Capability (NDC) messaging and Global Distribution System (GDS) messaging. 
     
     
         7 . The method of  claim 2 , wherein creating elements of said one of the supplier data objects comprises copying one or more common elements from another one of the supplier data objects. 
     
     
         8 . The method of  claim 1 , wherein the set of supplier data objects and further data object use identical serialization. 
     
     
         9 . The method of  claim 6 , wherein the aggregated functional object is presented to the client subsystem using an Application Programming Interface (API) according to a context defined by said one of the data object formats. 
     
     
         10 . A transaction processor server, comprising:
 a memory storing:
 a set of supplier data objects stored according to respective data object formats, each supplier data object including a plurality of elements; and 
   a processor interconnected with the memory, the processor configured to:
 create a further data object for linking selected supplier data objects based on common ones of said elements shared between the selected supplier data objects; 
 create an aggregated functional data object by merging and combining said common ones of said elements with remaining ones of the plurality of elements from the selected supplier data objects according to said linking; and 
 present the aggregated functional data object to a client subsystem. 
   
     
     
         11 . The transaction processor server of  claim 10 , wherein the processor is further configured to:
 receive a request from the client subsystem to modify one of the selected supplier data objects and in response one of either create, delete or modify elements of said one of the supplier data objects;   update the linking to reflect any modification of said common ones of said elements;   create a further aggregated functional data object by merging and combining said common ones of said elements with said remaining ones of the plurality of elements from the selected supplier data objects, including the modified one of the selected supplier data objects, according to said linking; and   present the further aggregated functional data object to the client subsystem.   
     
     
         12 . The transaction processor server of  claim 10 , wherein each of said supplier data objects includes a distribution channel indicator indicative of its data object format. 
     
     
         13 . The transaction processor server of  claim 10 , wherein each of said supplier data objects includes a record identifier. 
     
     
         14 . The transaction processor server of  claim 13 , wherein the processor is further configured to maintain each said record identifier in said further data object upon creating the aggregated functional data object. 
     
     
         15 . The transaction processor server of  claim 10 , wherein the data object formats correspond to data acquired through at least one of either New Distribution Capability (NDC) messaging and Global Distribution System (GDS) messaging. 
     
     
         16 . The transaction processor server of  claim 11 , wherein the processor is further configured to create elements of said one of the supplier data objects by copying one or more common elements from another one of the supplier data objects. 
     
     
         17 . The transaction processor server of  claim 10 , wherein the set of supplier data objects and further data object use identical serialization. 
     
     
         18 . The transaction processor server of  claim 15 , wherein the aggregated functional object is presented to the client subsystem using an Application Programming Interface (API) according to a context defined by said one of the data object formats. 
     
     
         19 . A computer program product comprising program instructions stored on a computer readable medium, for generation of an aggregated functional data object for a client subsystem from a set of supplier data objects having different data object formats, wherein execution of the instructions by a transaction processor server configures the transaction processor server to:
 store the set of supplier data objects according to their respective data object formats, each supplier data object including a plurality of elements;   create a further data object for linking selected supplier data objects based on common ones of said elements shared between the selected supplier data objects; and   create the aggregated functional data object by merging and combining said common ones of said elements with remaining ones of the plurality of elements from the selected supplier data objects according to said linking, for presentation to the client subsystem.