Application Version Selection via Context-Aware Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face difficulties in selecting the appropriate version of an application on their client devices due to multiple versions being available, leading to cluttered interfaces and incorrect selections, which can result in security issues and access restrictions based on location, device type, and time.

Innovation Solution

A system and method that aggregates multiple versions of an application into a single icon, allowing users to select a version based on context and attributes, such as location and device type, ensuring compatibility and compliance with access rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple versions of an application are provided to users, then users have more options and flexibility, but the interface becomes cluttered and selection becomes difficult

Engineering Contradiction:
Improveapplication version optionsVSAvoidinterface clutter
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent combines multiple application versions behind a single icon or unified interface element. Instead of displaying separate icons for each version, the system merges them into one selectable item that presents version options to the user upon selection, thereby reducing visual clutter while preserving access to multiple versions.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent segments the version selection process into two stages: first presenting a unified interface, then revealing specific version options only when needed. This segmentation separates the navigation layer from the selection layer, reducing initial interface complexity while maintaining full version availability.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If users can manually select application versions, then flexibility is increased, but user errors and security issues increase

Engineering Contradiction:
Improveversion selection flexibilityVSAvoidsecurity compliance
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system provides feedback to users about which application version will be launched based on their selection and current context (location, device type, time). This feedback mechanism allows the system to warn users of potential security issues or incompatibilities and guide them toward appropriate selections, reducing errors while maintaining flexibility.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary checks of user context (geolocation, device attributes, time of day) before allowing version selection or launch. By pre-evaluating compatibility and security requirements, the system can prevent problematic selections before they occur, ensuring reliability while preserving user choice.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If security access controls are strictly enforced, then security is improved, but user convenience decreases

Engineering Contradiction:
Improvesecurity controlVSAvoiduser convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system automatically evaluates user context and determines appropriate application versions without requiring manual security checks or administrative intervention. The security controls operate in the background, self-adjusting based on user attributes and context, thereby maintaining strict security enforcement while presenting a seamless, convenient user experience.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Security context evaluation is performed in advance of the actual application launch. By pre-assessing user permissions, device compatibility, and security policies, the system can automatically select or guide users to appropriate versions without requiring them to navigate complex security protocols during the launch process.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If context-based version selection is implemented, then security and compatibility are improved, but system complexity increases

Engineering Contradiction:
Improvecontext-based selectionVSAvoidsystem architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a context evaluation service as an intermediary layer between the user and the application launch process. This mediator automatically assesses user context (location, device type, time) and determines appropriate version selections, shielding users from system complexity while enabling sophisticated context-based routing. The intermediary handles the computational burden of context analysis centrally.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11586434B2Selecting a version of an application
Publication Date: 2023.02.21 CITRIX SYSTEMS INC
  • US11586434B2 patent drawing
  • US11586434B2 patent drawing
  • US11586434B2 patent drawing

AI summary

Described embodiments provide systems and methods for selecting a version of an application to launch for a client device according to a context of the client device. A computing device can receive a request from a client device to launch an application. The request can include an identifier that indicates multiple versions of the application are accessible in which to launch the application. The computing device can select, using the identifier, a version of the application according to a context of the client device. The computing device can provide the client device with access to the selected version of the application, so as to enable the client device to launch a version of the application compatible with the context of the client device.