Compiled Data Modules for Carrier Rate Lookup

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Carrier management systems face challenges in updating rate and zone data without affecting system performance and ensuring data security, particularly when the data center is unavailable or when users and third-parties can easily modify the data.

Innovation Solution

Converting rate and zone tables into executable code, which improves lookup performance, encapsulates data logic, and prevents end-users and third-parties from modifying the data by embedding it within the application's code.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If rate and zone data are stored in a database and queried by the application, then the data can be updated frequently without changing application code, but the system performance deteriorates due to additional query process time

Engineering Contradiction:
Improvedata update capabilityVSAvoidquery process time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent pre-compiles rate and zone data into executable code modules before runtime. This preliminary action transforms data retrieval from a database query operation into a direct code execution operation, eliminating query overhead while maintaining data update capability through regeneration of compiled modules when data changes

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces the mechanical database query system with a code-based execution system. Instead of using database management system queries to retrieve rate and zone data, the data is compiled into executable code that can be directly executed by the application, substituting a slower mechanical query process with a faster code execution process

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

2Loss of time

If rate and zone data are embedded in the application code, then system performance improves by eliminating database queries, but the code must be changed every time data is updated

Engineering Contradiction:
Improvequery process timeVSAvoidcode maintenance complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent segments the application into distinct components: the main application code and separate compilable data modules (rate tables and zone tables). This segmentation allows data to be compiled into executable modules that can be independently regenerated without modifying the main application code, reducing maintenance complexity while maintaining performance

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the state of rate and zone data from static database records to dynamic executable code modules. By parameterizing the data compilation process to accept input data and generate executable output, the system can update data by regenerating modules with new parameters rather than modifying source code

Inventive Principle:
Principle #35Parameter changes

3Loss of time

If data files are downloaded to client systems to reduce network latency, then system performance improves, but the files can be easily doctored or corrupted by users or third-parties

Engineering Contradiction:
Improvenetwork latencyVSAvoiddata security
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The patent replaces the vulnerable file-based data storage system with a compiled code-based system. Instead of distributing editable data files that can be doctored, the data is compiled into executable code modules with protected code structure, making it significantly more difficult to alter or corrupt the data without detection

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

Solution Approach 2:

The patent creates a composite structure by combining data with executable code logic into integrated compiled modules. This composite approach embeds data within the code structure, providing both the performance benefit of local execution and the security benefit of protected code format that resists unauthorized modification

Inventive Principle:
Principle #40Composite materials

4Productivity

If the data center is unavailable due to maintenance or network failure, then centralized data management is compromised, but users should be able to continue operations

Engineering Contradiction:
Improvesystem availabilityVSAvoiddata center dependency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent pre-compiles and distributes rate and zone data to client systems before data center unavailability occurs. This preliminary action enables clients to execute with local compiled data modules even when the data center is down, maintaining productivity while reducing dependency on continuous data center availability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces compiled data modules as intermediaries between the data center and the application execution. These modules act as local copies that can be executed without real-time data center connection, serving as a mediator that maintains system operation during data center unavailability while still allowing updates when connected

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8584107B2Compiled data for software applications
Publication Date: 2013.11.12 UNITED PARCEL SERVICE OF AMERICAN INC
  • US8584107B2 patent drawing
  • US8584107B2 patent drawing
  • US8584107B2 patent drawing

AI summary

Various embodiments of the present invention provide systems and methods of converting data used for shipment rate calculations into executable code. More specifically, certain embodiments if the present invention provide systems and methods of converting data used for shipment calculations into executable code by scanning the data from at least one source file, parsing the data in accordance with a template, and generating the executable code by utilizing the parsed data. As a result, the code may be executed to provide the data used for shipment rate calculations without having to access the original source file. In addition, compiling such data into executable code may improve look-up performance, may provide encapsulation of logic related to the specific nature of the data, and may provide a mechanism by which the raw data is not overtly exposed to end users of the software and third-parties.