Networked Embedded Device Integration via Application Model Layer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current programming platforms for networked embedded devices, such as wireless sensor networks, are low-level and focus on details like communication protocols and power management, making it difficult to integrate these devices with business applications and limiting their widespread adoption due to complexity and lack of ease of use.
Innovation Solution
An architecture with an application model layer that integrates networked embedded devices with business applications, an intermediate device programming layer providing network-centric programming abstraction, and a self-optimizing run-time system layer that adapts to specific conditions, facilitating integration and simplifying development.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If low-level programming platforms are used for networked embedded devices, then detailed control over communication protocols and power management is achieved, but integration with business applications becomes difficult and device complexity increases
Solution Approach 1:
The patent introduces an intermediary integration layer that sits between the low-level device programming interface and the business application layer. This intermediary layer provides standardized adapters and translation mechanisms that enable business applications to communicate with networked embedded devices without requiring programmers to deal with low-level protocol details directly, thus reducing programming complexity while maintaining integration capability
Solution Approach 2:
The patent segments the programming interface into distinct layers: a simplified high-level interface for business applications and the underlying low-level interface for device control. This segmentation allows each layer to operate independently with well-defined interfaces, reducing the complexity burden on business application developers while preserving access to detailed device control when needed
2Adaptability or versatility
If proprietary customized interfaces are used for individual nodes, then specific device functionality is optimized, but programming difficulty increases due to focus on low-level details
Solution Approach 1:
The patent creates a universal programming interface that can work with multiple types of networked embedded devices regardless of their proprietary customized interfaces. The integration layer provides device-agnostic abstractions that enable a single programming approach to control diverse devices, maintaining adaptability to specific device functionalities while simplifying the programming experience through standardized interaction patterns
3Productivity
If rapid application development is pursued for networked embedded devices, then market adoption increases, but integration with business applications becomes more challenging
Solution Approach 1:
The patent implements preliminary action by pre-configuring standardized integration templates, common communication patterns, and reusable adapter components for typical business application scenarios. This allows developers to rapidly deploy applications by configuring pre-built integration frameworks rather than building integration logic from scratch, thereby increasing development speed while managing integration complexity through proven patterns
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
Embodiments of the invention relate to programming, configuring, and integrating networked embedded devices with other applications. Particular embodiments include an architecture having an application model layer that integrates the networked embedded devices with business application systems, by allowing the devices to be expressed as part of a business application concept. In certain embodiments, an intermediate device programming layer provides a network-centric programming abstraction, relieving the programmer of the details of low-level, node-centric programming. Finally, a self-optimizing run-time system layer adapts to the specific conditions in the deployed network embedded devices, by optimizing e.g. communication patterns and resource consumption based upon input from the higher layer(s). Embodiments may facilitate integration of networked embedded devices with the back ends of business applications, and may provide a unified extensible programming framework simplifying development of applications for network embedded devices.