Feed Service Engine Scheduling Data Streams
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network-connected embedded systems face challenges in managing data flow effectively, leading to bandwidth bottlenecks and resource depletion, which can result in the loss of utility and violations of service level agreements with third-party data sources.
Innovation Solution
A data feed service platform that schedules and manages data streams from various sources to devices, using a feed service engine to coordinate data feed jobs, batch requests, cache data, and deliver it efficiently, thereby improving network performance and conserving bandwidth and processing resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network-connected embedded systems continuously request and receive data feeds from third-party sources, then devices can access real-time information and maintain functionality, but bandwidth is depleted, network bottlenecks occur, and service level agreements are violated
Solution Approach 1:
The system performs preliminary actions by scheduling data feed requests in advance based on predetermined time intervals and dependencies. The feed service engine creates a schedule of when data should be requested from third-party sources, allowing the system to proactively manage bandwidth usage while ensuring data is available when needed. This prevents reactive, uncoordinated requests that deplete bandwidth.
Solution Approach 2:
The system implements feedback mechanisms by monitoring data feed consumption patterns, network conditions, and service level agreement compliance. The feed service engine adjusts scheduling decisions based on this feedback, optimizing the balance between delivering reliable data feeds and conserving bandwidth resources. This closed-loop control ensures continuous improvement of resource utilization.
2Adaptability or versatility
If embedded systems implement role-based access control and remote interface capabilities, then device functionality and security are enhanced, but considerable manufacturer resources are consumed
Solution Approach 1:
The patent introduces a feed service engine as an intermediary component that manages data feed scheduling, access control, and device coordination. This intermediary handles the complexity of role-based access control and remote interface management centrally, rather than embedding all control logic within each device. This reduces individual device complexity while maintaining enhanced security and adaptability capabilities.
3Speed
If data feeds are delivered without scheduling or management, then devices can receive updates in real-time, but temporary storage is depleted and network performance deteriorates
Solution Approach 1:
The system implements periodic action by delivering data feeds at scheduled time intervals rather than continuously or on-demand. The feed service engine determines optimal update frequencies for different data types and devices, delivering updates periodically to maintain data currency while preventing temporary storage depletion. This rhythmic delivery pattern balances real-time data needs with storage constraints.
Data Source
AI summary
A processing device executing a data feed service performs a first query of a repository of data feed entries. The processing device determines, based on the first query, that a first data feed entry comprises a schedule to provide data from a first data feed of a first data source to a first device in an upcoming first time period, wherein the first data feed entry identifies the first data source, a first data type associated with the first data source, the first time period, and the first device. The processing device sends, to the first data source, a request for first data having the first data type and then receives the first data. The processing device sends the first data to the first device in the first time period.