Cycle Detection in Wireless Application Component Relationships

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems lack mechanisms to prevent recursive loops in component instantiation, leading to device lock-ups, application crashes, and resource saturation in wireless applications, posing risks for service providers due to third-party developer-created applications.

Innovation Solution

A method and system that construct a data model digraph to detect and identify recursive instantiation loops by representing each data component as a node and relationships as edges, using a modified Depth First Search algorithm to systematically search for cycles and alert developers to potential issues, allowing for safe component relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If component relationships are allowed to be freely defined by programmers, then application functionality and versatility are improved, but recursive loops may be created causing device lock-ups and resource saturation

Engineering Contradiction:
Improveapplication functionalityVSAvoiddevice stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary analysis of component relationships during application deployment or compilation, constructing a data model digraph to detect potential recursive loops before they can cause device lock-ups or resource saturation. This preventive approach allows programmers to define flexible component relationships while ensuring reliability through upfront validation.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If recursive loop detection mechanisms are implemented, then device reliability is improved, but system complexity increases due to additional analysis requirements

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

Solution Approach 1:

The system introduces an intermediary data model digraph that represents component relationships in a structured format, enabling recursive loop detection through graph cycle detection algorithms. This intermediary representation separates the detection logic from the actual component instantiation process, managing complexity while ensuring reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If third-party applications are permitted, then service provider adaptability is improved, but risk of malicious or erroneous recursive loops increases

Engineering Contradiction:
Improveservice provider adaptabilityVSAvoidrecursive loop risks
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system applies preliminary anti-action by detecting and preventing recursive loops in third-party applications before deployment. By analyzing component relationships upfront and identifying potential recursive patterns, the system neutralizes harmful effects before they can impact device stability, allowing service providers to accept third-party applications with reduced risk.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS8074208B2System and method for generating safe and efficient component relationships in wireless applications
Publication Date: 2011.12.06 MALIKIE INNOVATIONS LTD
  • US8074208B2 patent drawing
  • US8074208B2 patent drawing
  • US8074208B2 patent drawing

AI summary

A method of detecting recursive instantiation loops in a wireless application. A data model digraph is constructed including a respective node for each data component in the wireless application, and a respective edge for each relationship between a pair of data components. The data model digraph is searched to identify any cycles. For each identified cycle, each data component that participates in the cycle is identified.