Application Manager Decoupling for Network Resource Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing policy servers complicate the design of application servers by requiring them to manage network resources, leading to unnecessary cost and complexity, especially for installations that do not need application managers.

Innovation Solution

A method is introduced where an application manager is logically and physically decoupled from the application server, using protocols like PCMM, SIP, and XML to convey QoS information and select network resources for establishing connections between network endpoints, thereby simplifying the application server's functionality and reducing unnecessary complexity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the application manager functionality is integrated into the application server, then resource management capability is provided, but device complexity and cost increase

Engineering Contradiction:
Improveresource management capabilityVSAvoidapplication server complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the application server functionality by extracting the application manager as a separate logical and physical component. This allows the application server to focus on application-specific functions while the application manager handles resource management, thereby reducing application server complexity while maintaining resource management capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The application manager functionality is extracted from the application server into a separate entity. This extraction removes the complexity of resource management from the application server, allowing it to operate more simply while the application manager independently provides resource management services to multiple applications.

Inventive Principle:
Principle #2Taking out (Extraction)

2Device complexity

If the application manager is decoupled from the application server, then application server complexity is reduced, but communication overhead increases

Engineering Contradiction:
Improveapplication server complexityVSAvoidcommunication overhead
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The application manager acts as an intermediary between the application server and the network resources. It receives resource management requests from the application server, processes them according to QoS policies, and manages network resources accordingly. This intermediary role streamlines communication by providing a dedicated resource management interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If transparent resource management is implemented without modifying network endpoints, then interoperability is improved, but resource management control is reduced

Engineering Contradiction:
ImproveinteroperabilityVSAvoidresource management control
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The application manager provides universal resource management functionality that works across different network endpoints, application servers, and network technologies. It implements a standardized interface for QoS resource management that is technology-agnostic, enabling interoperability while maintaining centralized control over network resources.

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

Data Source

PatentUS7738440B2PCMM application manager
Publication Date: 2010.06.15 CAMIANT INC
  • US7738440B2 patent drawing
  • US7738440B2 patent drawing
  • US7738440B2 patent drawing

AI summary

A method of assigning network resources between network endpoints includes providing a session initiation request to an application manager. The application manager is logically and physically decoupled from an application server associated with the network endpoints. This request initiates communication between the network endpoints through the set of network resources. The communication employs an application residing on an application server. The method also includes providing a PCMM message from the application manager to a policy server as a result of the session initiation request. The PCMM message includes at least some information, for example QoS information, embedded in the session initiation request. The method further includes selecting, via the policy server, a set of network resources for creating a path connecting the network endpoints. The policy server selects the set of network assets based on the PCMM message, for example to set QoS for the communication between the two endpoints.