Runtime Execution Data Extraction in Cloud Containers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies face challenges in extracting and analyzing runtime software execution information in cloud environments, particularly in large-scale systems, due to the transient nature of containers and the complexity of modern software development, making it difficult to monitor performance and security, and acquire forensic data post-incident.

Innovation Solution

An apparatus and method for collecting and analyzing runtime software execution information by tracing operating system functions, instrumenting system calls, and using software artifacts to identify and extract relevant data, including file, memory, and system call information, enabling real-time monitoring and analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If log file analysis is used to extract runtime information, then information can be collected, but it is impossible to extract relevant information when software is executed because logs are only generated for specific functionalities

Engineering Contradiction:
Improveruntime execution informationVSAvoidinformation extraction capability
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent applies preliminary action by installing instrumentation code and agents into the software and container image repositories before the software is executed. This instrumentation is prepared in advance so that when the software runs, the collection unit can automatically trace system calls and collect execution information without requiring post-hoc log configuration or manual intervention.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If debugging tools are used to extract execution information, then detailed software behavior can be analyzed, but it is difficult to use debugging tools in actual software execution environments because they are designed for development phase

Engineering Contradiction:
Improvesoftware behavior analysisVSAvoidexecution environment compatibility
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent extracts the essential functionality of debugging tools by separating the information collection capability from the development-phase debugging context. The collection unit and analysis unit are extracted as independent components that can operate in production environments, collecting and analyzing execution information without requiring the full debugging tool suite or development environment setup.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary approach by using agents embedded within the container images and the collection unit as a mediator between the executing software and the analysis system. This intermediary layer allows execution information to be captured transparently during normal operation without requiring direct intervention from external debugging tools.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If system-monitoring tools are used to monitor software execution, then system performance can be analyzed, but it is difficult to extract required information from software-execution-related resources

Engineering Contradiction:
Improvesystem performance monitoringVSAvoidsoftware execution information
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent applies universality by designing the collection unit to perform multiple functions: it traces system calls, monitors file operations, tracks memory access, and collects software component information all through a unified instrumentation approach. This multi-functional collection unit can extract diverse execution information from various software resources without requiring separate specialized tools for each type of data.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Measurement precision

If memory analysis tools are used to extract execution information, then detailed memory-related data can be obtained, but they have limitations in real-time analysis of large-scale systems

Engineering Contradiction:
Improvememory information extractionVSAvoidreal-time analysis capability
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the information collection and analysis functions into distinct modular units: the collection unit that traces and gathers data, and the analysis unit that processes the collected information. This segmentation allows the system to handle large-scale real-time analysis by processing information in manageable segments rather than requiring monolithic analysis of entire memory spaces.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250013556A1Apparatus and method for extracting and analyzing runtime software execution information
Publication Date: 2025.01.09 ELECTRONICS & TELECOMM RES INST
  • US20250013556A1 patent drawing
  • US20250013556A1 patent drawing
  • US20250013556A1 patent drawing

AI summary

Disclosed herein is an apparatus and method for extracting and analyzing runtime software execution information. The apparatus may include a collection unit for collecting execution-related data by tracing functions of an operating system on which software is executed or access to data and an analysis unit for generating required information by analyzing the collected execution-related data.