Dependency Tracking Using Application and Network Layer Information

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Graph models lack detailed dependency tracking between application layer and network layer information, making it challenging to identify errors in cloud computing systems, where tasks are executed by different computing resources each time, leading to inefficient problem resolution.

Innovation Solution

A resource monitoring system that combines application layer and network layer information to generate a dependency map, illustrating relationships between tasks and computing resources, allowing for efficient identification and remediation of errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Illumination intensity

If graph models are used to represent data relationships, then the visual display of dependencies is improved, but the detail about application layer and network layer information is lost

Engineering Contradiction:
Improvevisibility of dependenciesVSAvoiddetailed information about nodes
Core Design Contradiction:
Illumination intensityVSLoss of information

Solution Approach 1:

The patent segments the graph model into different layers: a visual graph interface layer for displaying dependencies and a detailed data storage layer for maintaining application layer and network layer information. This allows the visual representation to remain simple while detailed information is preserved in the database structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a database as an intermediary between the graph visual representation and the detailed information. The database stores comprehensive node attributes (application layer and network layer information) while the graph interface provides visual dependency tracking, mediating between simplified visualization and detailed data storage.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If tasks are executed by different computing resources each time, then system flexibility is improved, but the ability to link application layer information with network layer information deteriorates

Engineering Contradiction:
Improveflexibility in task executionVSAvoidlinkage between application and network layer information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent performs preliminary actions by capturing and storing network layer information (source IP, destination IP, ports) at the time of task execution. This preliminary data collection ensures that even when tasks are reassigned to different computing resources, the linkage information is preserved before the dynamic reassignment occurs.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system establishes feedback loops where network layer information is continuously monitored and fed back into the database alongside application layer information. This feedback mechanism maintains the linkage between application tasks and network communications even as computing resources change dynamically.

Inventive Principle:
Principle #23Feedback

3Difficulty of detecting and measuring

If detailed dependency tracking is implemented, then error identification is improved, but system complexity increases

Engineering Contradiction:
Improveerror identification capabilityVSAvoidsystem structure complexity
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The patent makes the database structure universal by designing it to handle multiple types of information (application layer, network layer, dependency relationships) within a single unified schema. This multi-functional database structure enables detailed dependency tracking without requiring separate complex systems for each type of data management.

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

Data Source

PatentUS11818010B2Dependency tracking using application layer and network layer information
Publication Date: 2023.11.14 CAPITAL ONE SERVICES LLC
  • US11818010B2 patent drawing
  • US11818010B2 patent drawing
  • US11818010B2 patent drawing

AI summary

Disclosed herein are systems, products, and/or methods for determining a dependency between a task and a hardware component executing the task. The method may include: accessing an execution log storing information related to a plurality of tasks, each task of the plurality of tasks being executed by a respective computing device of a plurality of computing devices distributed across a network architecture; identifying a task of the plurality of tasks to obtain application layer information of the identified task; determining which respective computing device executed the identified task to obtain network layer information of the respective computing device; generating a dependency map illustrating a relationship between the identified task and the respective computing device that executed the identified task, the relationship including the application layer information and the network layer information; and displaying, using an interactive graphical user interface (GUI) on a user device, the dependency map.