Data management profile for a fabric network

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Smart home networks face challenges in efficiently managing and accessing data across devices, requiring a standardized communication protocol to enable seamless data exchange and automation of home devices without complex setup or high technical expertise.

Innovation Solution

A fabric network system that uses multiple logical networks and data management profiles to enable devices to communicate using a standardized message format, allowing for data exchange and automation across different devices and networks, including IPv6 communication and low-power operation for battery-powered devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If devices use multiple different network types and protocols to communicate, then device compatibility and communication flexibility are improved, but system complexity and difficulty of integration increase

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

Solution Approach 1:

The patent implements a gateway device that acts as an intermediary between devices using different network protocols. The gateway translates messages between various protocols (WiFi, Bluetooth, Zigbee, etc.) and a standardized internal format, enabling heterogeneous devices to communicate without direct protocol compatibility. This mediator approach resolves the contradiction by maintaining high adaptability while managing complexity centrally in the gateway rather than in each device.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments communication functionality into modular components: protocol-specific adapters, message format converters, and application logic layers. Each device type has its own adapter module that handles protocol-specific complexity, while the core system uses a unified message structure. This segmentation allows the system to support multiple protocols without increasing overall complexity, as each segment handles only its specific protocol independently.

Inventive Principle:
Principle #1Segmentation

2Speed

If devices store and manage their own data locally, then data access speed and device autonomy are improved, but data sharing and coordination between devices become difficult

Engineering Contradiction:
Improvedata access speedVSAvoiddata sharing
Core Design Contradiction:
SpeedVSEase of operation

Solution Approach 1:

The patent combines local data storage with centralized data coordination through the gateway. Devices store data locally for fast access, while the gateway maintains a unified data model and message routing system that enables cross-device data sharing. The standardized message format includes data descriptors that allow devices to request and share data through the gateway without sacrificing local storage benefits, thus merging the advantages of both distributed and centralized approaches.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If a standardized message format is implemented across all devices, then communication efficiency and interoperability are improved, but flexibility in handling device-specific data formats is reduced

Engineering Contradiction:
Improvecommunication efficiencyVSAvoiddata format flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The message format implements local quality by having a standardized structure for common communication elements (headers, routing information, basic commands) while allowing device-specific payload sections with flexible schemas. Each device type can define its own data format within the payload area while maintaining compatibility with the standardized message envelope. This allows efficient standardized processing of message routing and basic operations while preserving flexibility for device-specific data requirements.

Inventive Principle:
Principle #3Local quality

4Reliability

If battery-powered devices operate continuously to maintain network connectivity, then network responsiveness and automation capability are improved, but power consumption increases

Engineering Contradiction:
Improvenetwork responsivenessVSAvoidpower consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Battery-powered devices use periodic wake-up cycles instead of continuous operation. Devices sleep for defined intervals and wake periodically to check for messages, send status updates, or perform scheduled tasks. The gateway buffers incoming messages for sleeping devices and delivers them during wake periods. This periodic action maintains network functionality and responsiveness while dramatically reducing power consumption compared to continuous operation.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS10826947B2Data management profile for a fabric network
Publication Date: 2020.11.03 GOOGLE LLC
  • US10826947B2 patent drawing
  • US10826947B2 patent drawing
  • US10826947B2 patent drawing

AI summary

Method and systems for controlling data remotely that includes connecting to a remote device within a fabric of smart devices. The remote device stores data locally. Controlling the data includes remotely controlling the data stored in the remote device from another device connected to the fabric by transmitting a message to the remote device. Moreover, the transmitted message includes a profile identifier that causes a data management entity of the remote device to perform an indicated data management action. Furthermore, the profile identifier identifies a data management profile, and the message includes a command tag that indicates the data management action to be performed.