Volatile Memory Data Provisioning Framework

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprise data scattered across different systems and applications leads to fragmented infrastructure, causing latency, inconsistency, and inefficiencies in user experience, management, and access control, making it challenging to provide a unified and secure data provisioning solution.

Innovation Solution

A communication system that transfers database query results from a first computer system to a second computer system as initial pages of memory via a network connection, using volatile memory to enhance security and efficiency by keeping data up-to-date without storing it on non-volatile memory, allowing for real-time updates and secure access control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is stored on non-volatile memory for persistent access, then data availability is improved, but security is worsened due to increased risk of unauthorized access

Engineering Contradiction:
Improvedata availabilityVSAvoidunauthorized access risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts data from non-volatile storage and loads it into volatile memory (RAM) for processing. The application program accesses data exclusively from volatile memory during runtime, and data is automatically unloaded when the application terminates, preventing persistent storage vulnerabilities

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system dynamically manages data in volatile memory by loading data when the application starts and automatically unloading it when the application ends. This dynamic allocation ensures data is available during operation but not persistently stored, creating a balance between availability and security

Inventive Principle:
Principle #15Dynamics

2Object-affected harmful factors

If data is kept in volatile memory for security, then security is improved, but data refreshment capability is worsened

Engineering Contradiction:
Improveunauthorized access riskVSAvoiddata refreshment capability
Core Design Contradiction:
Object-affected harmful factorsVSProductivity

Solution Approach 1:

The system maintains continuous data refreshment capability by monitoring the database for changes and automatically updating the volatile memory copy when modifications are detected. This ensures data remains current while staying in secure volatile storage

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system implements a feedback mechanism where the database transactional system monitors for changes and triggers automatic data refreshes. When changes are detected in the database, the system retrieves updated data and replaces the old data in volatile memory, ensuring data currency without persistent storage

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If data is accessed via fragmented infrastructure across different systems, then system flexibility is improved, but user experience is worsened due to latency and inconsistency

Engineering Contradiction:
Improvesystem flexibilityVSAvoiddata access latency
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary data loading by retrieving data from the database and loading it into volatile memory before the application needs it for processing. This pre-positioning of data in fast-access memory eliminates runtime access delays and ensures immediate availability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces volatile memory as an intermediary layer between the database and the application program. This intermediary provides fast access to frequently used data while the system maintains flexibility to access diverse data sources, resolving the conflict between speed and adaptability

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3173951B1Integrated framework for secured data provisioning and management
Publication Date: 2020.07.01 SAP SE
  • EP3173951B1 patent drawingFigure 1
  • EP3173951B1 patent drawingFigure 2
  • EP3173951B1 patent drawingFigure 3

AI summary

The invention provides for a communication system (1500) comprising a first computer system (104, 1501) with a first processor (1510) and a first volatile memory (1512). The first computer system comprises first machine executable instructions (1522) configured for implementing a real-time database transactional system. The real-time database transactional system is further configured for connecting to two or more database systems (308, 310, 312, 314, 1508, 1508', 1508", 1508"'). The communication system further comprises a second computer system (1502) with a second processor (1516) and a second volatile memory (1518). The second computer system comprises second machine executable instructions (1524) for execution by the second processor to implement an application (102, 1526). The communication system further comprises a network connection (1506) between the second computer system and the first computer system. Execution of the second machine executable instructions cause the second processor to generate (1700) a data request (1528) for application data for an instance of the application and send (1702) the data request to the first computer system via the network connection. Execution of the first machine executable instructions cause the first processor to: generate (1704) an initial database query (1530) using the data request; query (1706) the two or more database systems using the initial database query; receive (1708) an initial query response (1532) from the two or more database systems in response to the database query; transform (1710) the initial query response into the application data using a memory model, wherein the memory model is configured for formatting the application data as one or more initial pages (1524, 1534') of memory; and push (1712) the application data across the network connection to the second processor. Execution of the second machine executable instructions cause the second processor to swap (1714) the one or more initial pages of memory into the second volatile memory.