Context Processing Service for IoT Rule Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems lack the capability to effectively record and act upon context data from mobile devices and IoT devices, limiting their ability to perform actions based on real-time user and device conditions.

Innovation Solution

A system that collects context data from various devices and applications, processes it using a cloud-based context processing service, and executes predefined rules to perform actions when specific conditions are met, utilizing context profiles and APIs to manage and communicate data across different devices and protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If a system collects and processes context data from multiple devices and applications, then the capability to perform automated actions based on real-time conditions is improved, but the device complexity and data management overhead increase

Engineering Contradiction:
Improveautomated actions based on context dataVSAvoidsystem complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent introduces a context processing service as an intermediary layer between context data providers (IoT devices, mobile applications) and rule execution systems. This service abstracts the complexity of collecting, normalizing, and managing context data from multiple sources, enabling automated rule execution without directly increasing the complexity of individual devices. The intermediary handles data aggregation, validation, and distribution to relevant rule engines.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If context data is collected from diverse devices and protocols, then the versatility and adaptability of the system improve, but the difficulty of detecting and measuring data increases

Engineering Contradiction:
Improvecompatibility with different devices and protocolsVSAvoiddata collection and processing difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The context processing service is designed with universal functionality to handle context data from multiple diverse sources including IoT devices, mobile applications, and various protocols. It provides a unified interface for data collection, normalization, and processing that works across different device types and communication protocols, thereby achieving multi-functionality without proportionally increasing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The intermediary context processing service acts as a protocol translator and data normalizer between diverse context data providers and the rule execution system. It standardizes data formats, handles protocol variations, and presents a uniform interface to the rule engine, reducing the difficulty of detecting and measuring data from heterogeneous sources.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If real-time data processing and rule execution are implemented, then the responsiveness and user experience improve, but the energy consumption and computational resources increase

Engineering Contradiction:
Improvereal-time data processing speedVSAvoidenergy consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The rule execution system implements partial action by selectively evaluating and executing only those rules that are relevant to the current context data, rather than continuously evaluating all possible rules. This approach maintains real-time responsiveness for critical operations while reducing overall computational overhead and energy consumption during periods when fewer rules are applicable.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system employs periodic action by scheduling rule evaluations based on event triggers and time-based conditions rather than continuous monitoring. Context data is processed and rules are executed periodically when relevant events occur or at scheduled intervals, maintaining real-time capability for important events while conserving energy during stable states.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS10621175B2Rule execution based on context data
Publication Date: 2020.04.14 SAP SE
  • US10621175B2 patent drawing
  • US10621175B2 patent drawing
  • US10621175B2 patent drawing

AI summary

Various embodiment of systems and methods to execute a rule based on context data has been described. Initially a trigger to initiate execution of the rule is received at a context processing service. A plurality of context parameters included in the rule are then identified. Context data corresponding to the plurality of context parameters from a context database are then retrieved. Context data may be received from a plurality of context providers including: an Internet of Things (IoT) network; and an application executing at a portable electronic device. Based on the retrieved context data, the rule is executed at the context processing service. Finally an action is executed corresponding to the rule based on execution of the rule.