Mobile Device Code Activation via Network Instructions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices' sandbox security model restricts the ability to download and execute new compiled code, limiting the capability to change the behavior and functionality of applications, which hinders the delivery of diverse graphical presentations and advertising without reprogramming the device.

Innovation Solution

Abstracting graphical animation capabilities into not compiled code instructions that can be downloaded and executed on mobile devices, allowing for the creation of various movements and behaviors without requiring new compiled code, thus enabling efficient and secure delivery of graphical presentations and games.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the sandbox security model is enforced to prevent malicious code execution, then device security is improved, but the capability to download and execute new compiled code is restricted, limiting application functionality changes

Engineering Contradiction:
Improvedevice securityVSAvoidapplication functionality change capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system separates application functionality into two distinct components: compiled code (for core application logic and security) and not compiled code instructions (for dynamic behavior changes). The compiled code resides in the secure sandbox environment, while the not compiled code instructions are downloaded and executed to modify application behavior without compromising security. This segmentation allows functionality changes while maintaining security boundaries.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary execution layer that processes not compiled code instructions. These instructions act as a mediator between the external content delivery and the secure compiled code environment, enabling dynamic behavior changes without directly modifying or compromising the secured compiled code. The intermediary layer translates high-level instructions into secure operations within the sandbox.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If new compiled code is downloaded to change application behavior, then functionality is improved, but bandwidth usage and download time increase

Engineering Contradiction:
Improveapplication behavior change capabilityVSAvoidbandwidth usage
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The system uses not compiled code instructions as lightweight, temporary objects for delivering dynamic behavior. These instructions are much smaller in size compared to full compiled code applications, consuming minimal bandwidth for download. After execution, they serve their purpose of modifying application behavior temporarily without requiring permanent storage or large data transfers.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Solution Approach 2:

Instead of downloading entire compiled code applications to change behavior, the system downloads compact not compiled code instructions that reference and trigger existing compiled code functionality. This copying approach allows the same compiled code to be invoked with different parameters and behaviors through small instruction sets, dramatically reducing data transfer requirements.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If compiled code is used to deliver graphical presentations and games, then functionality is improved, but development time and deployment complexity increase

Engineering Contradiction:
Improvegraphical content delivery capabilityVSAvoiddevelopment and deployment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system enables dynamic delivery of graphical presentations and games through not compiled code instructions that can be updated and deployed remotely without requiring full application recompilation. Content creators can modify graphical behavior, animations, and game logic by updating instructions rather than rebuilding entire compiled applications, significantly accelerating the development and deployment cycle.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system performs preliminary compilation of core application functionality once, creating a stable compiled code base. Subsequent graphical presentations and game variations are then delivered through not compiled code instructions that build upon this pre-prepared foundation. This preliminary action eliminates the need to recompile core functionality for each content variation, saving substantial development time.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If the sandbox model prevents downloading additional compiled code, then security is improved, but content diversity and advertising capabilities are limited

Engineering Contradiction:
Improvemobile network securityVSAvoidcontent diversity
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The not compiled code instructions serve multiple functions within the secure sandbox environment: delivering graphical presentations, displaying diverse advertising content, enabling game variations, and modifying application behavior. This universal instruction set replaces the need for multiple separate compiled code applications, achieving content diversity while maintaining security through a single secured code base.

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

Data Source

PatentUS10540485B2Instructions received over a network by a mobile device determines which code stored on the device is to be activated
Publication Date: 2020.01.21 SMALTZ DAVID GENE
  • US10540485B2 patent drawing
  • US10540485B2 patent drawing
  • US10540485B2 patent drawing

AI summary

Compiled code is stored on a mobile device or embedded in an application on the device. Instructions are assembled in a compiled program and stored on a system for subsequent transmission to the mobile device over a network. An application on the mobile device interfaces with the network to request and receive instructions. The instructions are retrieved from the data store and returned over the connection to the mobile device. After receipt by the mobile device, the instructions determine which code is to be activated. New instructions are downloaded to the device and the new instructions activate different code.