Application Server Device Capability Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices with varying capabilities face inconsistent user experiences due to lack of tailored services from application servers, which do not account for hardware and software differences across devices.

Innovation Solution

A database storing capability information for mobile devices allows application servers to tailor services by querying device capabilities, adjusting user interfaces, processing ratios, and application provisioning based on device attributes like screen size, processor type, and input mechanisms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If application servers provide standardized services to all mobile devices, then service deployment is simple and consistent, but user experience is not optimized for device-specific capabilities

Engineering Contradiction:
Improveservice adaptability to device capabilitiesVSAvoidsystem complexity for capability management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by establishing a database of device capabilities before service delivery. Capability information is collected and stored in advance, allowing application servers to retrieve and utilize this information when providing services, thereby enabling optimized service delivery without adding complexity during the service execution phase

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A capability database is introduced as an intermediary component between mobile devices and application servers. This intermediary stores and manages device capability information, allowing application servers to access device-specific information without directly managing device complexity, thus resolving the contradiction between adaptability and system complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If application servers query and store capability information for all devices, then service tailoring is enabled, but data storage and management requirements increase

Engineering Contradiction:
Improveservice tailoring capabilityVSAvoiddata storage requirements
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system extracts only the necessary capability information from comprehensive device specifications and stores only these extracted attributes in the capability database. By taking out only the essential capability parameters rather than storing complete device information, the system enables service tailoring while minimizing data storage requirements

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If application servers customize services based on device capabilities, then user experience is optimized, but service provisioning complexity increases

Engineering Contradiction:
Improveuser experience qualityVSAvoidservice provisioning complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The capability database performs self-service by automatically storing and managing device capability information without requiring manual configuration or complex provisioning processes. Application servers simply query the database for required capability information, enabling customized services while keeping provisioning processes simple and automated

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9078083B2Application server awareness of device capabilities in a wireless network
Publication Date: 2015.07.07 VERIZON PATENT & LICENSING INC
  • US9078083B2 patent drawing
  • US9078083B2 patent drawing
  • US9078083B2 patent drawing

AI summary

Capability information, relating to hardware and/or software capabilities of different types of mobile devices, may be used to tailor services provided to the mobile device based on the particular type of mobile device. In one implementation, a device, such as an application server that provide services to mobile devices, may: receive a request from a mobile device, for services; obtaining information indicating a type of the mobile device; obtain, based on the type of mobile device, information indicating capabilities of the mobile device; and provide the services to the mobile device, in which the provided services are tailored for the mobile device based on the capabilities of mobile device.