Resource Management Node for Social Web Data Flow Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current solutions for networked object interconnectivity lack holistic and unified interaction with multiple devices, environments, and services, failing to provide intuitive management of relationships, data flows, and responses to triggering events across large numbers of objects.

Innovation Solution

The implementation of a resource management node using social mapping principles, which includes a system entity database, interaction flow database, and interaction execution engine to manage and facilitate data flows between networked resource nodes, with a recommendation engine generating recommended data flows and user-accepted connections based on metadata and triggering criteria.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If ad-hoc solutions are used for networked device connectivity, then specific limited functionalities are enabled, but holistic and unified interaction with multiple networked objects is not provided

Engineering Contradiction:
Improvefunctional capabilitiesVSAvoidsystem integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal resource management node that can interact with multiple types of networked objects (devices, services, environments) through a single unified interface. This node provides holistic management capabilities including relationship mapping, data flow control, and event response coordination across diverse networked objects, replacing the need for multiple ad-hoc solutions with one multi-functional system.

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

2Ease of operation

If traditional network management approaches are used, then basic connectivity is achieved, but intuitive management of relationships and data flows among large numbers of objects is not provided

Engineering Contradiction:
Improveuser understanding of networkVSAvoidnumber of networked objects
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent introduces a resource management node as an intermediary between users and large numbers of networked objects. This intermediary provides intuitive relationship mapping that visualizes and simplifies the complex network structure, making it easier for users to understand and manage relationships, data flows, and interactions among numerous networked objects without being overwhelmed by their quantity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If existing network solutions are implemented, then device connectivity is established, but management of associations, data flows, and responses to triggering events is not adequately addressed

Engineering Contradiction:
Improvenetwork connectivityVSAvoidmanagement system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-configuring the resource management node with relationship mapping rules, data flow policies, and event response protocols before networked objects are connected. This allows the system to automatically manage associations, control data flows, and coordinate responses to triggering events without requiring complex real-time management, thereby maintaining reliable connectivity while reducing management complexity.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9237062B2Management of data flows between networked resource nodes in a social web
Publication Date: 2016.01.12 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US9237062B2 patent drawing
  • US9237062B2 patent drawing
  • US9237062B2 patent drawing

AI summary

A resource management node is disclosed that manages a plurality of resource nodes connected to at least one network. The resource management node includes a system entity database, an interaction flow database, and an interaction execution engine. The system entity database contains information identifying communication addresses for the resource nodes and associated metadata identifying capabilities of the resource nodes. The interaction flow database contains information defining data flows that are permitted between identified ones of the resource nodes and associated triggering criteria defining when identified ones of the data flows are to be performed. The interaction execution engine is configured to determine that one of the triggering criteria defined by the interaction flow database is satisfied and to respond by establishing the associated data flow between the identified ones of the resource nodes. Related methods for managing a plurality of resource nodes connected to at least one network are disclosed.