Patent application EP16175174A (EP), filed 2016-06-20
Publication number: EP3260991A1
Title: SYSTEM AND METHOD CONFIGURED TO EXECUTE DATA MODEL TRANSFORMATIONS ON DATA FOR CLOUD BASED APPLICATIONS
Abstract: The invention concerns a method and a system to expose the common data model in a wider range of data model specific views by using a meta-data store, a load balancer (32), model router (33) and model transformer (34).
IPC codes: G06F  17/    30            A I
Claims: number: 1
text: System configured to execute data model transformations on data for cloud based applications comprising:
number: 2
text: System according to claim 1,
 characterized in that the data store is not directly accessible to the cloud based application (70, 70a).
number: 3
text: System according to claim 1 or 2,
 characterized in that the meta-data store is not directly accessible to the cloud based application (70,70a).
number: 4
text: System according to any one of claims 1 to 3,
 characterized in that the desired data protocol is a Transmission Control Protocol and/or an User Datagram Protocol.
number: 5
text: System according to any one of claims 1 to 4,
 characterized in that the request is provided in the desired data protocol.
number: 6
text: System according to any one of claims 1 to 5,
 characterized in that the model router (33) is configured to have computing capacity.
number: 7
text: System according to any one of claims 1 to 6,
 characterized in that the model router (33) is configured to identify the desired data protocol by technical attributes based on the desired data protocol.
number: 8
text: System according to claim 7,
 characterized in that the technical attributes are the port number and/or the HTTP header information and/or the request structure.
number: 9
text: System according to any one of claims 1 to 8, characterized in that the meta data (37) are configured to comprise the relationship between the data of interest (36) stored in the data store and the required meta data (37) information.
number: 10
text: System according to any one of claims 1 to 9, characterized in that in the case of more than one model routers (33) the one which receives the request will handle the upcoming data exchance between the cloud based application (70,70a) and the specific model transformer (34).
number: 11
text: System according to any one of claims 1 to 10, characterized in that there will be at least one specific model transformer (34) for each available desired protocol.
number: 12
text: System according to any one of claims 1 to 11, characterized in that the transformation rules are configured to comprise at least one of the following information:
number: 13
text: System according to any one of claims 1 to 12, characterized in that the model transformer (34) configured to fetch the rules from the rule database (35).
number: 14
text: System according to any one of claims 1 to 13, characterized in that the model transformer (34) is configured to fetch all required data from the data store based on the cloud based application's (70) demand.
number: 15
text: System according to any one of claims 1 to 14 characterized in that the model transformer (34) is configured to fetch all associated meta data (37) of the data of interest (36) from the meta-data store.
number: 16
text: System according to any one of claims 1 to 15, characterized in that the model transformer (34) is configured to generate a response in the format of the requested data model based on the rules.
number: 17
text: Method configured to execute data model transformations on data for cloud based applications the method comprising:
number: 18
text: Method according to claim 17,
 characterized in that there is no direct accessibility from the cloud based application (70, 70a) to the data store.
number: 19
text: Method according to claim 17 or 18,
 characterized in that there is no direct accessibility from the cloud based application (70,70a) to the meta-data store.
number: 20
text: Method according to any one of claims 17 to 19, wherein the method comprises:
number: 21
text: Method according to any one of claims 17 to 20, characterized in that the model router (33) is configured to have computing capacity.
number: 22
text: Method according to any one of claims 17-21, wherein the model router (33) comprises:
number: 23
text: Method according to any one of claims 17 to 22, characterized in that the transformation rules are configured to comprise at least one of the following information:
number: 24
text: Method according to any one of claims 17 to 23, characterized in that the rules are fetched from the rule database (35).
number: 25
text: Method according to any one of claims 17 to 24, characterized in that based on the cloud based application's demand, all required data is fetched from the data store.
number: 26
text: Method according to any one of claims 17 to 25, characterized in that all associated data is fetched from the meta-data store.
number: 27
text: Method according to any one of claims 17 to 26, characterized in that based on the rules, the model transformer (34) is configured to generate a response in the format of the requested data model.
Office action: search_report, dated 2017-12-27
Prior art cited: ref_id: US2004254924A1
ref_type: patent
severity: background
ref_id: GB2431257A
ref_type: patent
severity: background
ref_id: US2004254924
ref_type: patent
severity: background
ref_id: GB2431257
ref_type: patent
severity: background
Final disposition: pending (2017-12-27)