Gateway Software Framework Service Decoupling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The limited coverage of gateway devices in home environments requires multiple gateways, leading to complex information transmission coupling and service coupling, resulting in a heavy workload for gateway development and maintenance, making it difficult to expand gateway capacity.

Innovation Solution

A software framework with a service-oriented architecture that abstracts device capabilities into services, utilizing a data bus for communication between services, allowing decoupling of business development and simplifying application logic, enabling unified data transmission and cross-device communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Area of stationary object

If multiple gateway devices are deployed to expand coverage, then the coverage area is improved, but the information transmission coupling and service coupling become more complex

Engineering Contradiction:
Improvecoverage areaVSAvoidinformation transmission coupling
Core Design Contradiction:
Area of stationary objectVSDevice complexity

Solution Approach 1:

The patent segments the gateway system into independent service components that can be deployed across multiple gateway devices. Each gateway device contains a software framework with registered device services that can independently communicate through standardized interfaces, breaking the monolithic coupling into modular service interactions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal software framework that can be deployed on multiple gateway devices with different capabilities (Bluetooth, PLC, etc.). This framework provides unified service registration and communication mechanisms, allowing diverse gateway devices to interact through common protocols rather than requiring device-specific coupling logic.

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

2Area of stationary object

If multiple gateway devices are deployed to expand coverage, then the coverage area is improved, but the service coupling becomes more complex

Engineering Contradiction:
Improvecoverage areaVSAvoidservice coupling
Core Design Contradiction:
Area of stationary objectVSDevice complexity

Solution Approach 1:

The patent introduces a data bus as an intermediary layer between device services on different gateway devices. This data bus provides standardized communication protocols and interfaces, mediating the interactions between services across multiple gateways and eliminating the need for direct service-to-service coupling.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a comprehensive service registration mechanism where all device services are pre-registered in the software framework, even if not all services are actively used in every deployment scenario. This excessive registration approach simplifies runtime service discovery and invocation by providing a complete service catalog upfront.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If traditional gateway development approaches are used, then basic functionality is achieved, but the workload for development and maintenance becomes heavy

Engineering Contradiction:
Improvebasic functionalityVSAvoiddevelopment workload
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent pre-configures the software framework with registered device services and communication protocols during the development phase. This preliminary setup includes defining service interfaces, registration mechanisms, and data bus configurations, so that deployment and maintenance phases require minimal customization and configuration work.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables flexible configuration of gateway services through parameter-based service registration and invocation. Services can be dynamically enabled, disabled, or modified by changing registration parameters rather than requiring code modifications, significantly reducing maintenance workload for different deployment scenarios.

Inventive Principle:
Principle #35Parameter changes

4Reliability

If traditional gateway development approaches are used, then basic functionality is achieved, but it becomes difficult to expand gateway capacity

Engineering Contradiction:
Improvebasic functionalityVSAvoidgateway capacity expansion
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements a dynamic service registration and invocation mechanism that allows new device services to be added to the gateway software framework without requiring system reconfiguration. Services can be dynamically registered, discovered, and invoked through the standardized data bus interface, enabling flexible capacity expansion as new device types and protocols emerge.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12192031B2Invoking device services in preset software frameworks
Publication Date: 2025.01.07 BEIJING XIAOMI MOBILE SOFTWARE CO LTD
  • US12192031B2 patent drawing
  • US12192031B2 patent drawing
  • US12192031B2 patent drawing

AI summary

A method for operating a software framework is provided. The method may be applied to a software framework applicable to a gateway device, the software framework includes an application service layer and a basic service layer, the application service layer includes at least one device service registered in advance, and the basic service layer includes a data bus built in advance. The method includes: realizing a capability of a device associated with the gateway device based on the device service; and realizing communication between the device service and an external service based on the data bus, where the external service includes a device service belonging to a same gateway device as the device service or a different gateway device than the device service.