RDF Data Provider Pattern Definition for IoT Format Conformance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems fail to deliver data from a data provider to a client in the exact data format requested by the client, leading to inefficiencies and the need for additional transformations or gateways, which complicates data integration across different application domains in the Internet of Things.
Innovation Solution
A method where a data request message expressed in RDF query language, such as SPARQL, includes a query section and a pattern definition for the desired data structure, allowing the data provider to retrieve and return data values within the specified structure directly, leveraging semantically enriched data models like Thing Description and RDF stores.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If conventional RDF query languages are used to query data, then semantic search capability is improved, but the ability to deliver data in a specific requested format is lost
Solution Approach 1:
The patent combines the query language (SPARQL) with a pattern definition component that specifies the desired output data structure. This merging allows the system to both query semantically enriched data models and deliver results in a client-requested format within a single communication exchange.
Solution Approach 2:
The data provider is designed to perform multiple functions: it can query RDF data stores using SPARQL, interpret pattern definitions for desired output formats, and generate responses in various data structures (JSON, XML, etc.) based on the client's request, all within a unified system.
2Reliability
If multiple communication exchanges are used to retrieve and transform data, then data accuracy is improved, but network traffic and communication overhead increase
Solution Approach 1:
The patent merges the query execution and data transformation operations into a single communication exchange. The client sends one request containing both the query and the desired output pattern, and receives one response with the data already formatted according to the pattern, eliminating the need for multiple back-and-forth communications.
Solution Approach 2:
The client performs preliminary action by specifying the desired data structure pattern in advance within the request message. This allows the data provider to pre-format the data according to the client's requirements before transmission, avoiding subsequent transformation steps that would require additional communications.
3Adaptability or versatility
If data transformation and gateway components are added to support multiple formats, then adaptability is improved, but device complexity increases
Solution Approach 1:
The patent extracts the data format specification requirements from the communication protocol and places them directly into the request message as a pattern definition. This eliminates the need for separate gateway components or transformation layers, as the formatting requirements are now embedded in the messages themselves.
Solution Approach 2:
The data provider uses the pattern definition provided by the client to automatically format the response data according to the requested structure. This self-service approach eliminates the need for external gateways or intermediate transformation components, reducing system complexity while maintaining format compatibility.
4Productivity
If conventional query responses are returned without pattern conformance, then processing speed is improved, but additional client-side transformation is required
Solution Approach 1:
The client performs preliminary action by specifying the desired output pattern in the request. This allows the data provider to perform the formatting work in advance, delivering ready-to-use data that requires no additional client-side transformation, thus maintaining fast retrieval while reducing client processing effort.
Data Source
Figure 1~2
AI summary
Embodiments for providing data as described herein generally involve responding to a data request message. In one embodiment a method for providing data is disclosed, wherein a data request message submitted to a data provider is received. The data request message is expressed in a query language for RDF or Resource Description Framework. The data request message comprises a query section and a pattern definition. The query section is referencing one or more semantically enriched data models for semantically querying at least one property name of at least one data element. The pattern definition defines a data structure requested for a response of the data provider. The data provider is then querying at least one property name - or a semantic expression in general - in at least one of the semantically enriched data models which are referenced in the query section. Consequently, the data provider receives one or more references for said one or more data elements in response to said query. The data provider is then retrieving one or more data values of said one or more data elements, whereby these data values are expressed by the data provider within the data structure. The data provider is then generating a result message providing said data structure and sending the result message as a response to the instance which had been initiated the data request message.