Smart Home Device API Access Control Using Intermediary Service

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing smart home systems face challenges in securely allowing third-party access to smart devices while maintaining user experience, as direct access can potentially disrupt device operation.

Innovation Solution

Implementing a device service that allows third-party applications to interact with smart home devices through an application programming interface (API), enabling communication and control while maintaining security and user experience by using a subscription-based model and authorization processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If direct access is granted to third-party applications to control smart devices, then application versatility and user experience are improved, but device operation stability and security deteriorate due to potential disruptions

Engineering Contradiction:
Improveapplication versatilityVSAvoiddevice operation stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements a device service as an intermediary component that sits between third-party applications and smart devices. This service receives requests from applications, validates them against a policy, and forwards approved requests to devices. The intermediary architecture allows versatile third-party access while maintaining device stability through centralized control and validation mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If access restrictions are imposed on third-party applications to protect device operation, then device stability is maintained, but application versatility and user experience deteriorate

Engineering Contradiction:
Improvedevice operation stabilityVSAvoidapplication versatility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic access control where the device service evaluates each request in real-time against a policy and adjusts access permissions accordingly. Rather than static restrictions, the system dynamically determines whether to allow or deny access based on the specific request, application credentials, and device state, thereby maintaining stability while preserving versatility.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes access parameters dynamically based on request characteristics. The device service modifies authorization levels, request routing, and validation strictness according to the specific application and request type, allowing versatile access for authorized applications while maintaining security and stability.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If a device service intermediary is implemented to manage third-party access, then device operation stability is maintained, but system complexity increases

Engineering Contradiction:
Improvedevice operation stabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The device service is designed as a universal intermediary that handles multiple functions: request validation, policy enforcement, authentication, and request routing. By consolidating these diverse functions into a single multi-functional service, the system maintains stability without proportionally increasing complexity, as the service reuses common validation and control mechanisms across different device types and applications.

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

Data Source

PatentUS10638292B2Methods and apparatus for using smart environment devices via application program interfaces
Publication Date: 2020.04.28 GOOGLE LLC
  • US10638292B2 patent drawing
  • US10638292B2 patent drawing
  • US10638292B2 patent drawing

AI summary

Systems and Methods disclosed herein relate to providing a message to an application programming interface (API). The message includes a request for data from a data model, a submission of data to the data model, or both; and a host selection between: a representational state transfer (REST) host and a subscription-based application programming interface (API) host, wherein the REST host receives REST-based messages and the subscription-based API host receives messages in accordance with a standard of the subscription-based API host; wherein the request for data, the submission of data, or both are configured to create, delete, modify, or any combination thereof data related to a smart-device environment structure, a thermostat, a hazard detector, or any combination thereof stored in a data model accessible by the API.