Flexible Context-Aware Service Engine for Sensor-Partial Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional context-aware systems fail to provide services when not all context information is collected, leading to service disruptions due to missing or defective sensor nodes, especially in scenarios where multiple context information points are required.

Innovation Solution

A flexible context-aware service system utilizing a flexible CAS estimation engine that determines whether to provide service based on partial context information, allowing seamless service delivery even if not all sensors are registered or functioning correctly, by using a context-aware server to assess and adapt to available context data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional context-aware systems require all context information to be collected before providing service, then service accuracy is improved, but service availability deteriorates when sensor nodes are missing or defective

Engineering Contradiction:
Improveservice accuracyVSAvoidservice availability
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The patent applies partial action by requiring only a threshold number of context information points (e.g., at least 2 out of 3) rather than all required sensors to be functional. This allows the system to provide service based on partial context data when some sensors are missing or defective, thereby maintaining service availability while sacrificing complete measurement precision.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If the system requires multiple context information points to be collected, then service reliability is improved, but system complexity increases due to more sensor nodes and data processing

Engineering Contradiction:
Improveservice reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent changes the parameter from requiring all context information points to requiring only a threshold number (e.g., at least 2 out of 3). This parameter change reduces the system's complexity by lowering the bar for service provision while maintaining acceptable reliability levels, avoiding the need for all sensors to be functional simultaneously.

Inventive Principle:
Principle #35Parameter changes

3Loss of information

If the system provides service only when all context information is available, then information completeness is improved, but service responsiveness deteriorates

Engineering Contradiction:
Improveinformation completenessVSAvoidservice responsiveness
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system applies partial action by accepting service requests when a threshold number of context information points are available rather than waiting for all information to be collected. This enables the system to respond more quickly to user needs while maintaining sufficient information completeness through the threshold-based approach.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS7725532B2System and method for providing flexible context-aware service
Publication Date: 2010.05.25 ELECTRONICS & TELECOMM RES INST
  • US7725532B2 patent drawing
  • US7725532B2 patent drawing
  • US7725532B2 patent drawing

AI summary

Provided are a system and method for determining whether to provide service and a content of the service based on ubiquitous-based context information. The method includes the steps of registering at least one context-aware service (CAS); determining whether sensors associated with the CAS are registered; when all the sensors are registered, checking all contexts associated with the CAS; upon receipt of a CAS request, receiving context information from the sensors and determining whether the context information satisfies the contexts; and providing the CAS if the context information satisfies at least one of the contexts. With the flexible engine determining whether to provide service corresponding to a current context even though all context information constituting the CAS is not collected, information is quickly provided upon receipt of a service request from a user.