CRA Application Framework Offline Capability via Asynchronous Threads

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network communication technologies for mobile devices face challenges in providing a seamless user experience, especially when connected intermittently or offline, due to the need for specific coding in object-oriented programming languages like Objective C, which complicates functions such as caching and encryption, particularly in generating and editing trip reports for clinical studies.

Innovation Solution

The development of a mobile clinical research associate (CRA) application framework that uses declarative programming to enable offline capabilities, allowing data encryption and caching on mobile devices, and asynchronously processing resource-intensive operations to improve efficiency and scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If specific coding in object-oriented programming languages is used to implement network communication functions, then functions such as caching and encryption can be controlled, but the complexity of coding increases and offline capability becomes difficult to achieve

Engineering Contradiction:
Improveease of implementing offline capabilityVSAvoidcoding complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a service layer as an intermediary between the UI layer and data layer, which mediates network communication operations. This service layer handles caching, encryption, and offline capability logic centrally, eliminating the need for complex object-oriented coding in multiple layers and simplifying implementation while maintaining control over these functions

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If trip report data is generated and processed on the server, then data accuracy is maintained, but server resources are strained and network interactions increase

Engineering Contradiction:
Improvetrip report generation efficiencyVSAvoidserver resource stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the trip report generation process into distinct layers: UI layer for user interaction, service layer for business logic and data processing, and data layer for storage. This segmentation allows resource-intensive operations to be distributed and cached locally on mobile devices, reducing server strain while maintaining data accuracy through the structured service layer that ensures data integrity

Inventive Principle:
Principle #1Segmentation

3Loss of information

If network communication is maintained for real-time data access, then data freshness is improved, but offline capability is compromised

Engineering Contradiction:
Improvedata freshnessVSAvoidoffline capability
Core Design Contradiction:
Loss of informationVSAdaptability or versatility

Solution Approach 1:

The patent implements preliminary action by caching trip report data and business logic locally on mobile devices before network disconnection occurs. The service layer pre-processes and stores data in a structured format that can be accessed offline, ensuring data availability when the network is unavailable while maintaining data freshness through periodic synchronization when connected

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11693882B2System and method for offline capability for mobile devices including asynchronous threads
Publication Date: 2023.07.04 ORACLE INT CORP
  • US11693882B2 patent drawing
  • US11693882B2 patent drawing
  • US11693882B2 patent drawing

AI summary

Systems and methods are described herein that provide a system associated with a CRA application framework with offline capability for mobile devices. In one example embodiment, a network request is received via network communications from a mobile device. The request is identified and multiple processing threads are initiated that separate operations for performing the request. A Self Describing Object (SDO) is generated and is returned in response to a fetch request. This allows the mobile device to input data while offline from a server and to minimize network interactions therebetween.