Dynamic Feature Access via Server-Side Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The lack of standardization in SIP protocols and frequent updates in application servers create challenges for mobile devices to access additional features, leading to software complexity, user distraction, and management issues due to the need for multiple software versions.

Innovation Solution

A method and system that allow a communications device to dynamically obtain information for accessing additional features offered by application servers, eliminating the need for hardcoding, using a feature accessing function to configure the device and instruct the server to execute selected features, potentially using SIP extensions or other protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If mobile devices use hard-coded information to access application server features, then feature access is straightforward, but the software becomes complex and requires frequent updates to support new features

Engineering Contradiction:
Improvefeature access capabilityVSAvoidsoftware complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a server-side configuration system that acts as an intermediary between the application server and mobile device. The server provides feature access information dynamically, eliminating the need for hard-coded configurations in mobile device software. This mediator approach allows flexible feature access without increasing client software complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system transitions from static hard-coded feature configurations to dynamic server-provided configurations. The mobile device can adapt to different application servers and their features by receiving runtime configuration information, making the system flexible without requiring software updates or version management.

Inventive Principle:
Principle #15Dynamics

2Adaptability or versatility

If multiple software versions are maintained to support all features on all application servers, then all features are accessible, but management and control become more complex

Engineering Contradiction:
Improvefeature compatibilityVSAvoidsoftware version management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The mobile device software is designed to be universal by implementing a standard interface for receiving and processing feature access information from any application server. This single software version can work with multiple servers and features by adapting to server-provided configurations, eliminating the need for multiple specialized versions.

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

Solution Approach 2:

The application server automatically provides the necessary configuration information for feature access. The mobile device simply receives and uses this information without requiring manual updates or complex version management. The system self-adapts to new features through server-side configuration updates.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If frequent software updates are issued to support new features, then feature access is maintained, but user experience is degraded due to distractions and error opportunities

Engineering Contradiction:
Improvefeature supportVSAvoiduser experience
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system shifts the burden of feature updates from the client side to the server side. Application servers automatically provide updated feature access information without requiring mobile device software updates. Users experience no disruptions, and the system maintains current feature support through server-side configuration updates alone.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If parallel software versions are used to support different SIP standards, then compatibility is improved, but development, testing, and distribution become more difficult

Engineering Contradiction:
ImproveSIP version compatibilityVSAvoidsoftware development
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent introduces a configuration information exchange mechanism as an intermediary that handles SIP standard variations. Instead of creating parallel software versions for different SIP standards, the system uses a standardized interface that receives server-specific configuration information, allowing single software version to support multiple SIP variations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The mobile device software implements a universal interface for SIP communication that can adapt to different SIP standards and versions. By receiving server-specific configuration information, a single software version achieves compatibility with multiple SIP implementations, eliminating the need for parallel version development.

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

Data Source

PatentEP2041914B1System and method for accessing features offered by an application server
Publication Date: 2018.08.08 BLACKBERRY LTD
  • EP2041914B1 patent drawingFigure 1
  • EP2041914B1 patent drawingFigure 2
  • EP2041914B1 patent drawingFigure 3

AI summary

Systems and methods are provided for accessing additional features offered by an application server. The additional features are generally regarded as being specific to the application server. According to an embodiment of the application, a communications device obtains information for accessing the additional features. The communications device accesses an additional feature by instructing the application server to execute the additional feature according to the information that has been obtained. In specific implementations, the information for accessing the additional features is provided by an Extensible Markup Language 'XML' file.