Mobile Application Server Segmentation for Multi-Device Compatibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing mobile device application distribution systems are limited in providing applications to multiple device types, networks, and geographic regions, often restricting compatibility and availability due to single-source, single-channel distribution environments.

Innovation Solution

A mobile device application server system that includes a database and processor to manage and provide applications across various device types, networks, and regions by using metadata to filter and deliver compatible applications based on device specifications, user preferences, and regional requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a mobile device application server is configured to provide applications to a single type of device via a single distribution channel, then it is relatively simple to ensure compatibility, but the system lacks adaptability to serve multiple device types, networks, and geographic regions

Engineering Contradiction:
Improveability to serve multiple device types and networksVSAvoidsystem complexity for managing multiple device types
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the application distribution system by introducing device-type-specific configuration files that divide and organize applications according to compatible device types. Each configuration file contains metadata describing which applications are compatible with specific device types, allowing the server to handle multiple device types through structured segmentation rather than monolithic management

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces configuration files as intermediary elements between the application server and mobile devices. These configuration files act as mediators that contain device-type-specific information and guide the server in selecting and delivering compatible applications, simplifying the interaction between the server and diverse device types

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If applications are provided through a single distribution channel to a single device type, then compatibility is easier to ensure, but user access and flexibility are limited

Engineering Contradiction:
Improveuser access to applicationsVSAvoidapplication compatibility assurance
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements preliminary action by pre-configuring device-type-specific configuration files that contain metadata about application compatibility before users request applications. The server uses these pre-prepared configuration files to quickly determine compatibility and deliver appropriate applications, enabling both broad user access and reliable compatibility assurance

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies parameter changes by using configuration files that contain device-type parameters and application compatibility metadata. The server modifies its behavior based on these parameters, selecting and delivering applications that match the specific device type parameters provided in the configuration files

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9542498B2Provision of applications to mobile devices
Publication Date: 2017.01.10 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9542498B2 patent drawing
  • US9542498B2 patent drawing
  • US9542498B2 patent drawing

AI summary

Embodiments related to the provision of applications to mobile devices are disclosed. One embodiment provides a mobile device application server system, comprising a database, a processor, and memory comprising instructions stored thereon that are executable by the processor to perform a method of providing applications to mobile devices. The method comprises receiving a first application configured to be run on a first mobile device type, storing the first application, receiving a second application configured to be run on a second device mobile device type, and storing the second application. The method further comprises receiving a request for the first application from a first mobile device of the first mobile device type, providing the first application to the first mobile device, receiving a request for the second application from a second mobile device of the second mobile device type, and providing the second application to the second mobile device.