Cloud Integration Layer for Premises Automation Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a need for systems and methods that integrate cloud services and internet-connected devices with a user interface and other components of a service provider system, enabling third-party devices and services to control or trigger automations within the service provider system, allowing end-users to integrate and use standalone internet-connected devices with each other and their service provider-based services.

Innovation Solution

The Integrated Cloud System (ICS) integrates cloud services with user interfaces and service provider systems, using a Cloud Integration Service/Server, partner proxies, and automation rules to enable interactions between premises devices and third-party devices and services, allowing for control and automation through a Rules Engine and user interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud services and internet-connected devices are integrated with the service provider system, then device interoperability and functionality are improved, but system complexity increases

Engineering Contradiction:
Improvedevice interoperabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud integration service as an intermediary layer between third-party devices and the service provider system. This mediator handles protocol translation, data normalization, and coordination, enabling diverse devices to interoperate without directly increasing the complexity of core system components. The cloud service acts as a buffer that manages integration complexity externally.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements universal communication protocols and standardized data formats that allow the service provider system to work with multiple types of third-party devices (smart locks, cameras, thermostats, etc.) through a common interface. This multi-functionality approach enables a single integration framework to handle diverse device types, reducing the need for device-specific integration logic.

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

2Ease of operation

If third-party devices are enabled to control automations, then ease of operation is improved, but reliability may deteriorate due to integration errors

Engineering Contradiction:
Improvecontrol capabilityVSAvoidsystem stability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system implements feedback mechanisms where the cloud integration service monitors communication between third-party devices and the service provider system. It validates data formats, checks for errors, and provides error reporting and debugging capabilities. This feedback loop enables easy operation while maintaining reliability by detecting and correcting integration issues.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent incorporates error handling and validation protocols that are established in advance before actual device operations. The system pre-configures communication protocols, validates device credentials, and sets up error recovery mechanisms beforehand, cushioning against potential integration failures and maintaining system stability.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Adaptability or versatility

If multiple standalone devices are integrated into a unified system, then adaptability is improved, but difficulty of detecting and measuring issues increases

Engineering Contradiction:
Improveintegration capabilityVSAvoiddebugging complexity
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system segments the integration architecture into distinct modular components: device-specific adapters, protocol translation layers, data normalization services, and application logic layers. This segmentation allows developers to isolate and debug issues in specific modules without being overwhelmed by the entire system, reducing debugging complexity while maintaining high integration capability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11616659B2Integrated cloud system for premises automation
Publication Date: 2023.03.28 ICONTROL NETWORKS INC
  • US11616659B2 patent drawing
  • US11616659B2 patent drawing
  • US11616659B2 patent drawing

AI summary

A system comprises premises equipment including premises devices located at a premises. The system includes a partner device located at the premises and configured to use a partner protocol different from a protocol of the premises equipment. The system includes a system server configured to interact with the premises devices. The system server is configured to interact with the partner device via a partner proxy corresponding to the partner device. The system includes automation rules coupled to the system server. The automation rules include actions and triggers for controlling interactions between at least one of the partner device and the premises devices. The system includes a user interface coupled to the system server and configured to interact with the premises devices and the partner device.