OSP Resource Handling Settings for Low-Latency ERP Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing online software platforms face inefficiencies in processing, storage, and data transmission, requiring significant resources and capable hardware, which limits their ability to perform tasks with low latency and resource preservation.
Innovation Solution
The system constructs outbound datasets with specific parameters and values, transmitting them to an OSP computer system that applies digital resource rules to generate resources, which are then processed and returned as inbound datasets, allowing for selective addition or exclusion based on handling settings, optimizing resource utilization and reducing hardware requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If online software platforms process computations and make determinations for clients, then service functionality is provided, but processing resources, storage resources, and data transmission resources are significantly consumed
Solution Approach 1:
The patent segments the resource consumption by distinguishing between base value processing (performed by the client device) and resource value additions (performed by the online software platform). This segmentation allows the platform to provide service functionality while reducing overall processing resource consumption by handling only the incremental resource additions rather than complete computations.
Solution Approach 2:
The patent extracts the base value from the complete resource calculation and handles it locally at the client device, removing this portion from the online software platform's processing burden. Only the resource additions (marginal resources) are processed by the platform, significantly reducing its resource consumption while maintaining service functionality.
2Productivity
If online software platforms process computations and make determinations for clients, then service functionality is provided, but hardware capability requirements increase
Solution Approach 1:
The patent segments the computational workload between client devices and online software platforms. Client devices handle base value processing while platforms handle only resource addition computations. This segmentation reduces the hardware capability requirements for both parties, allowing the platform to provide service functionality without requiring high-end hardware.
Solution Approach 2:
The patent uses lightweight data structures (outbound datasets and inbound datasets) that are created, transmitted, and discarded in each transaction. These temporary data objects require minimal hardware resources to handle, enabling the platform to provide service functionality on less capable hardware without requiring persistent complex data structures.
3Productivity
If online software platforms transmit data across networks, then computations are performed, but data transmission resources are consumed
Solution Approach 1:
The patent extracts only the essential information needed for resource addition computations and transmits it as compact outbound datasets. By transmitting only the necessary data (relationship instance data with dataset parameters) rather than complete computation contexts, the platform achieves computation throughput while minimizing data transmission resource consumption.
Solution Approach 2:
The patent transforms complex relationship instance data into parameterized outbound datasets with structured parameters and values. This parameterization reduces data transmission size and optimizes network resource usage while maintaining the computational information needed for resource calculations.
4Productivity
If online software platforms produce multiple resources according to digital rules, then comprehensive results are generated, but processing time increases latency
Solution Approach 1:
The patent performs preliminary processing by constructing outbound datasets with pre-validated relationship instance data and dataset parameters before transmission. This preliminary action ensures that when the online software platform receives the data, it can quickly produce comprehensive results without extensive validation or preprocessing, reducing processing latency while maintaining result comprehensiveness.
Solution Approach 2:
The patent uses parameterized datasets that structure relationship instance data in a format optimized for rapid processing. By transforming data into parameterized form (with dataset parameters and values), the platform can efficiently generate comprehensive results through rule-based processing without extensive data manipulation, reducing latency.
Data Source
AI summary
In embodiments, in processes that can be repeated numerous times, relationship instance data is inputted, of relationship instances between primary entities and secondary entities. For a relationship instance, an outbound dataset is constructed that has dataset parameters with respective dataset values. One of the dataset values characterizes an attribute of one of the entities, and another encodes a base value for the relationship instance data. The outbound dataset is transmitted across a network to an Online Software Platform (OSP) computer system. The OSP computer system produces, according to digital rules, two or more resources for the dataset, and an inbound dataset is returned with the results, for forwarding to an output device. Handling settings are also inputted by a UI. Depending on the handling settings, one of the resources is added, or not, to the base value for a user as part of forwarded results.