In-situ OAM Proxy for Container Telemetry

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Container applications often lack the capability to insert in-situ Operations, Administration, and Management (iOAM) data into packets, especially when experiencing high utilization, which hinders effective telemetry and management within network service chains.

Innovation Solution

Implementing an iOAM proxy within a network connected device that provides iOAM functionality for container applications, either by inserting iOAM data into packets or offloading this functionality from container applications, using a flow table and database to determine and apply the necessary iOAM data based on packet processing and service chain requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If container applications process packets at high utilization, then network throughput is improved, but the capability to insert iOAM data into packets deteriorates

Engineering Contradiction:
Improvenetwork throughputVSAvoidiOAM data insertion capability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces an iOAM proxy as an intermediary component that handles iOAM data insertion separately from the container application's packet processing path. The proxy intercepts packets, inserts iOAM telemetry data, and returns them to the application, allowing high-utilization packet processing to continue uninterrupted while iOAM functionality is maintained by the dedicated proxy component

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If iOAM functionality is implemented within container applications, then telemetry capability is improved, but device complexity and resource consumption worsen

Engineering Contradiction:
Improvetelemetry informationVSAvoidapplication complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent extracts iOAM functionality from the container application and places it in a separate iOAM proxy component. This extraction removes the complexity of iOAM implementation from the application code while maintaining the telemetry capability. The application simply communicates packet flow information to the proxy, which handles all iOAM data insertion operations

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The iOAM proxy is designed as a universal component that can serve multiple container applications simultaneously. Instead of each application implementing its own iOAM functionality, a single multi-functional proxy handles iOAM for all applications, reducing overall system complexity and resource consumption

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

Data Source

PatentUS10588012B2In-situ operations, administration and management proxy
Publication Date: 2020.03.10 CISCO TECHNOLOGY INC
  • US10588012B2 patent drawing
  • US10588012B2 patent drawing
  • US10588012B2 patent drawing

AI summary

A process executing on a network connected device provides distinct Internet Protocol addresses to a plurality of workload applications. The process determines that a first of the plurality of workload applications will not be providing in-situ Operations, Administration and Management (iOAM) data in packets processed by the first of the plurality of workload applications. The process receives a packet processed by the first of the plurality of workload applications. The process inserts iOAM data for the first of the plurality of workload applications into the packet.