IPFIX Application Metadata Export Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The IPFIX protocol lacks a standardized method to dynamically configure network devices to export only relevant application metadata, leading to inefficient resource consumption and difficulty in incorporating new application metadata as standards evolve.
Innovation Solution
The proposed solution involves using the IPFIX protocol to allow network devices to advertise their application metadata detection capabilities, enabling collectors to request and receive only the subset of metadata needed, thereby optimizing resource usage and facilitating dynamic customization of templates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the IPFIX protocol exports all application metadata types, then comprehensive network visibility is achieved, but resource consumption increases and efficiency decreases
Solution Approach 1:
The patent extracts only the necessary subset of application metadata that is relevant to the collector's specific needs, rather than exporting all available metadata. This is achieved through dynamic template customization where collectors can request specific metadata types based on their operational requirements, thereby reducing resource consumption while maintaining comprehensive visibility of relevant information.
Solution Approach 2:
The patent implements local quality by allowing different collectors to receive different subsets of application metadata tailored to their specific functions and requirements. Each collector can customize the metadata types it receives based on local needs, optimizing resource usage while ensuring each collector gets the comprehensive visibility it requires for its particular purpose.
2Ease of manufacture
If the IPFIX protocol uses fixed templates, then implementation simplicity is maintained, but adaptability to new application metadata types is limited
Solution Approach 1:
The patent introduces dynamics by enabling runtime customization of metadata export templates. Collectors can dynamically request and receive different subsets of application metadata types based on evolving needs and new standards. This dynamic template customization allows the system to adapt to new application metadata types while maintaining the simplicity of the underlying IPFIX protocol implementation.
Solution Approach 2:
The patent achieves universality by creating a flexible template system that can accommodate both existing and future application metadata types within the same IPFIX framework. The dynamic template customization mechanism provides a universal solution that works across different metadata types and collector requirements, eliminating the need for separate implementations for different scenarios.
3Loss of information
If all application metadata is exported to all collectors, then complete information availability is achieved, but network bandwidth consumption increases
Solution Approach 1:
The patent extracts only the relevant subset of application metadata that each collector needs for its specific function, rather than exporting all metadata to all collectors. This selective extraction reduces network bandwidth consumption while ensuring each collector receives complete information availability for its particular operational context.
Solution Approach 2:
The patent implements local quality by allowing each collector to receive a customized subset of application metadata tailored to its local requirements. This ensures that each collector gets the complete information it needs for its specific purpose while minimizing unnecessary data transmission across the network, thereby reducing overall bandwidth consumption.
4Loss of energy
If dynamic template customization is implemented, then resource efficiency is improved, but protocol complexity increases
Solution Approach 1:
The patent achieves universality by implementing dynamic template customization within the existing IPFIX protocol framework, allowing the same protocol to handle both fixed and dynamic template scenarios. This approach improves resource efficiency through selective metadata export while avoiding the need for a completely new protocol, thereby limiting the increase in protocol complexity.
Solution Approach 2:
The patent introduces an intermediary layer of template customization logic that sits between the metadata generation and export processes. This intermediary enables dynamic template selection and customization, improving resource efficiency by exporting only relevant metadata, while encapsulating the complexity within the intermediary layer rather than spreading it throughout the entire protocol implementation.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
In general, techniques for providing application metadata using an Internet Protocol Flow Information eXport (IPFIX) protocol in computer networks are described. In one example, a first network device including a processor and a memory may perform the techniques. The processor may be configured to determine types of the application metadata that the first network device has a capability to detect through analysis of network packets. The application metadata may comprise data representative of network protocols used by networking processes that exchange packets. The memory may be configured to store the application metadata. The processor may further be configured to execute the IPFIX protocol to advertise the types of the application metadata to a second network device configured to collect a subset of the application metadata.