Mobile Software Deployment Platform Adaptability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mobile software deployment platforms are inflexible and require costly, time-consuming custom development, often designed for desktop devices and reliant on foreign key relationships in relational databases, which wastes computing power and memory and limits database flexibility.

Innovation Solution

A single integrated software project deployment platform that allows administrators to deploy software projects easily to remote computers, using a smart database design with primary keys for meta-data construction of many-to-many relationships and an object-oriented approach to eliminate foreign key dependencies, enabling real-time data capture and synchronization across mobile devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional mobile software deployment platforms are used, then software can be deployed to mobile devices, but the platforms require costly and time-consuming custom development and are inflexible when business processes change

Engineering Contradiction:
Improveflexibility to adapt to changing business processesVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements dynamic adaptability by allowing the software platform to automatically adjust to changing business processes without requiring custom development. The system uses configurable parameters and templates that can be modified on-the-fly to accommodate new business requirements, enabling the platform to evolve dynamically as business needs change.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent creates a universal deployment platform that can handle multiple business processes and scenarios through a single standardized interface. By using generic templates and configurable parameters, the platform serves multiple functions across different business contexts without requiring process-specific custom development, thus reducing development time while maintaining adaptability.

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

2Adaptability or versatility

If relational databases with foreign key relationships are used, then data can be stored and queried, but computing power and memory are wasted and database flexibility is limited

Engineering Contradiction:
Improvedatabase flexibilityVSAvoidcomputing power and memory consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts and eliminates the foreign key relationship mechanism from the database design. By removing this rigid structural constraint, the system achieves greater database flexibility and reduces the computational overhead associated with maintaining and querying foreign key relationships, thereby lowering memory and processing requirements.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent changes the fundamental parameter of database relationship modeling by transitioning from foreign key-based relational modeling to a more flexible approach that uses configurable parameters and templates. This parameter change enables the database to adapt to different data structures and query patterns without the rigid constraints of traditional foreign key relationships, improving both flexibility and efficiency.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8751926B2Intelligent rendering on a mobile computing device
Publication Date: 2014.06.10 MOBILEFRAME LLC
  • US8751926B2 patent drawing
  • US8751926B2 patent drawing
  • US8751926B2 patent drawing

AI summary

A solution is provided wherein step information is intelligently rendered on a mobile computing device. A current page is created based on a default size. The step may then be placed on the current page below any previous steps. A height allocated for the step may then be increased if the step has multiple lines. If the placing of the step or increasing of the height causes the step to run past the end of the current page, then a new page may be created and the step may be placed there instead. This process may be repeated for each step. This allows each page to then be sequentially displayed on the mobile computing device without scroll bars.