Software Service Function Resource Loading Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current resource loading methods for applications (APPs) result in long starting times for service functions due to the need to load many service resources, negatively impacting user experience, especially in scenarios requiring real-time performance.

Innovation Solution

The proposed method involves loading the foundation framework resource of a service function before receiving a service request, followed by loading the necessary page resource, reducing the resources needed to be loaded after the request is received, and utilizing a hybrid engine for REACT-based foundation framework loading.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all service resources are loaded after receiving a service request, then the service function can be implemented completely, but the starting time of the service function becomes long

Engineering Contradiction:
Improveservice function implementation completenessVSAvoidservice function starting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by loading the foundation framework resource before the service request is received. This pre-loading of the foundational infrastructure (without the specific page resources) allows the system to be prepared in advance, reducing the loading time when the actual service request comes in, while still ensuring complete service function implementation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the service resources into two distinct parts: foundation framework resources (loaded in advance) and page resources (loaded after service request). This segmentation allows the heavy foundational components to be prepared beforehand while only the necessary page-specific resources are loaded on-demand, resolving the contradiction between completeness and speed.

Inventive Principle:
Principle #1Segmentation

2Reliability

If many service resources are loaded to implement a service function, then the service function can be fully implemented, but the user experience is negatively affected due to long loading time

Engineering Contradiction:
Improveservice function implementationVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

By performing preliminary loading of the foundation framework resource before the user triggers the service function, the system prepares the essential infrastructure in advance. This reduces the perceived loading time for the user while maintaining full service functionality, thereby improving user experience without sacrificing service implementation completeness.

Inventive Principle:
Principle #10Preliminary action

3Loss of time

If foundation framework resource is loaded in advance, then the service function starting time is reduced, but the memory usage increases

Engineering Contradiction:
Improveservice function starting timeVSAvoidmemory usage
Core Design Contradiction:
Loss of timeVSQuantity of substance

Solution Approach 1:

The patent segments resources into foundation framework resources (pre-loaded) and page resources (loaded on-demand). This segmentation allows the system to load only the essential foundational components in advance, occupying minimal memory, while deferring the loading of specific page resources until they are actually needed, thus balancing memory usage with fast start-up time.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by loading only the foundation framework resource in advance, which is the minimum necessary infrastructure for service execution, rather than loading all possible resources. This partial pre-loading reduces memory consumption compared to full pre-loading while still achieving the goal of reduced service function starting time.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11693704B2Resource loading and a service function for a software application
Publication Date: 2023.07.04 ADVANCED NEW TECHNOLOGIES CO LTD
  • US11693704B2 patent drawing
  • US11693704B2 patent drawing
  • US11693704B2 patent drawing

AI summary

A foundation framework resource of a first service function is loaded in a software application. A service request for starting the first service function in the software application is received. A page resource required by the first service function is loaded. The first service function is implemented based on the foundation framework resource of the first service function and the page resource.