Mobile Terminal Connection Management via Application Layer Bus

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current connection management devices in mobile terminals do not effectively adapt network resources to applications based on transfer speed, security, and cost, leading to suboptimal performance and user experience due to limitations in managing protocol layers and application compatibility across different networks.

Innovation Solution

A mobile terminal with a connection management device that includes a management software bus, priority table, and modules for channel creation, optimization, and resource allocation, allowing for real-time adaptation of communication channels to match application requirements and user tariffs, optimizing network resource usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If connection management devices manage protocol layers at TCP/IP level or lower, then network connection control is simplified, but application layer compatibility and real-time adaptation to application requirements cannot be achieved

Engineering Contradiction:
Improveconnection management complexityVSAvoidapplication compatibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a new dimension of management by adding a software bus that operates at the application layer, perpendicular to the traditional protocol stack management. This allows connection management to occur simultaneously at multiple levels (protocol layer and application layer) without increasing complexity in the traditional sense, thereby resolving the contradiction between simplified management and application compatibility.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The software bus acts as an intermediary between applications and the connection management device, enabling real-time communication and adaptation. This intermediary layer allows the system to maintain simple protocol layer management while achieving sophisticated application-layer adaptability through the bus-mediated exchange of application requirements and connection status information.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If network resources are allocated without real-time adaptation to application needs, then resource management is simpler, but transfer speed, security, and cost optimization for specific applications cannot be achieved

Engineering Contradiction:
Improveresource management complexityVSAvoidapplication performance
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent implements feedback mechanisms where applications communicate their requirements and performance status through the software bus to the connection management device. The connection management device continuously monitors connection performance and adjusts resource allocation based on real-time feedback from applications, achieving optimized transfer speed, security, and cost without excessive management complexity through automated feedback-driven adjustments.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system transitions from static resource allocation to dynamic allocation that adapts in real-time to changing application requirements and network conditions. The software bus enables continuous monitoring and adjustment of connection parameters, allowing the system to optimize resource allocation dynamically based on current application needs, network status, and user tariffs.

Inventive Principle:
Principle #15Dynamics

3Device complexity

If manual user intervention is required to switch networks or resolve connection issues, then connection management logic is simpler, but user experience and continuity of service are degraded

Engineering Contradiction:
Improveconnection management logicVSAvoiduser experience
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The patent enables the connection management system to perform self-service operations through automated monitoring and decision-making. The connection management device continuously monitors application requirements and connection status through the software bus, automatically making decisions about network switching and resource allocation without requiring user intervention. This maintains relatively simple management logic while dramatically improving user experience through seamless, automated service continuity.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If multiple networks are available without intelligent selection, then network availability is maximized, but resource optimization and cost efficiency for specific applications are reduced

Engineering Contradiction:
Improvenetwork availabilityVSAvoidresource efficiency
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent implements preliminary action by having applications declare their requirements in advance through the software bus during the registration phase. The connection management device uses this advance information to pre-select appropriate networks and allocate resources before actual data transmission begins. This preliminary configuration enables the system to maintain multiple network availability while optimizing resource efficiency and reducing costs from the outset rather than reacting to performance issues.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2150090B1Multimode terminal with optimized connections
Publication Date: 2011.11.02 SOC FR DU RADIOTELEPHONE SFR
  • EP2150090B1 patent drawingFigure 1
  • EP2150090B1 patent drawingFigure 2
  • EP2150090B1 patent drawingFigure 3

AI summary

The terminal has a predetermined logical management bus (B0) provided in communication with connection interfaces (Int0, Int1, Intx) of a management device (ACM1) and application programs (App1, Appx), respectively. A priority table stores identifiers (ID-CA1, ID-CAx) of the corresponding programs and channel types associated to stored priority levels. The device has an allocation module that allocates one of established communication channels (CA1, CAx) to the corresponding program, where the allocated channel corresponds to the channel type associated to the program in the table. An independent claim is also included for a method for managing communication in a mobile terminal.