RTOS Multi-Application POS Software for Flexible App Installation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional POS machines are limited to single applications, cannot install new software at will, and require complex, time-consuming re-integration by manufacturers to respond to user needs, with high development costs and limited user customization.

Innovation Solution

An RTOS-based multi-application development method using a Jerryscript engine and AWTK engine, enabling compilation and packaging of applications into a system.bin file, followed by burning or uploading to a POS machine, supporting installation, uninstallation, and upgrade through an application market.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If applications are built-in by the manufacturer in conventional POS machines, then the system has stable performance and hardware compatibility, but the applications cannot be uninstalled or deleted by end users and require complex re-integration by manufacturers

Engineering Contradiction:
Improveapplication installation flexibilityVSAvoidsoftware re-integration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is divided into two independent parts: the operating system (RTOS) and applications. Applications are packaged as separate binary files that can be independently installed, uninstalled, and updated without affecting the OS or other applications. This segmentation enables end users to manage applications freely while maintaining system stability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The RTOS is designed with universal application support capabilities, including a file system for storing multiple application binaries, an installer for managing application installation and uninstallation, and a runtime environment that can execute any compiled application. This multi-functionality allows the same OS to support diverse applications without requiring manufacturer re-integration.

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

2Reliability

If applications are developed in C language with direct hardware access, then the performance and hardware compatibility are good, but the code complexity increases and development becomes difficult and time-consuming

Engineering Contradiction:
Improvehardware compatibilityVSAvoidcode complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary layer (the RTOS runtime environment and API library) between the high-level programming language and hardware. Developers can write applications in simpler languages while the RTOS provides hardware abstraction and direct access capabilities when needed, maintaining hardware compatibility without requiring developers to write complex low-level code.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical approach of direct hardware manipulation in C language with a software-based abstraction layer. The RTOS provides standardized APIs and runtime services that simplify hardware interaction, allowing developers to achieve the same hardware compatibility with less complex code by substituting low-level mechanical operations with higher-level software mechanisms.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If the conventional POS machine uses manufacturer-built-in applications, then the system has stable performance, but it cannot respond to user new service requirements in a timely manner

Engineering Contradiction:
Improveresponse to new service requirementsVSAvoidtime for re-integration
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The RTOS includes pre-built infrastructure components such as the file system, installer, and runtime environment that are prepared in advance. This preliminary preparation enables rapid deployment of new applications without requiring time-consuming manufacturer re-integration, as the system already has the necessary mechanisms in place to install and execute new applications immediately.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If end users require customized functions, then the system has high adaptability, but the functions must be developed and built in by the manufacturer which increases development cost and time

Engineering Contradiction:
Improveuser customization capabilityVSAvoiddevelopment efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The system enables end users to perform self-service by allowing them to install, uninstall, and manage their own applications without manufacturer intervention. Users can customize the POS machine by selecting and installing applications that meet their specific needs, eliminating the requirement for manufacturer development and building of customized functions.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12360755B1RTOS-based multi-application development method and apparatus
Publication Date: 2025.07.15 SHENZHEN TOPWISE COMM CO LTD
  • US12360755B1 patent drawing
  • US12360755B1 patent drawing
  • US12360755B1 patent drawing

AI summary

An RTOS-based, (Real-Time Operating System-based) multi-application development method and apparatus are provided. The method comprises: compiling and packaging an AWTK, (Toolkit Any Where) engine, a Jerryscript engine, and .c files through a GNU, (Gnu's Not Unix) compiler suite to generate a system.bin file; compiling and packaging xml files, js (JavaScript) files, and image files required by multiple applications through the AWTK engine to generate a fat.img containing the multiple applications; and burning the fat.img containing the multiple applications and the system.bin file into a POS (point of sale) machine with an RTOS. The Jerryscript engine and the AWTK engine support the development of JS language, then resource data (data) are generated from all images, XML (describing image elements and coordinates), and JS files used in the development of APPS, and finally, the resource data are compiled by GCC, (GNU Compiler Collection) to generate an APP.bin, thereby achieving multi-application development.