Two-Level Network Application Control Architecture for Non-Session Service Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network-based application control architectures face challenges in efficiently monitoring and managing Non-Session-based services due to their heterogeneity and the complexity of protocols involved, leading to scalability issues and incomplete traffic analysis, particularly with proprietary protocols and encrypted traffic.
Innovation Solution
A two-level network-based application control architecture that includes a Network Trigger System (NTS) for analyzing data flows and detecting events, and a Usage Status Engine (USE) for configuring and processing event reports, utilizing Finite State Automatons (FSAs) to manage state transitions and enforce policies across multiple services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a network-based control framework is adopted to monitor Non-Session-based services, then the ability to intercept and analyze client-server communication flows is improved, but the device complexity and protocol analysis burden increase significantly
Solution Approach 1:
The patent segments the control architecture into two distinct levels: a network-level NTS responsible for packet interception and event detection, and a control-level USE responsible for policy processing and state management. This segmentation divides the complex protocol analysis task between network infrastructure components and application-level software, reducing the burden on any single component while maintaining comprehensive monitoring capability.
2Measurement precision
If Deep Packet Inspection is used to analyze proprietary and encrypted protocols, then measurement precision of traffic analysis is improved, but the difficulty of detecting and measuring increases due to protocol heterogeneity
Solution Approach 1:
The patent introduces an intermediary mechanism where the NTS acts as a mediator between the network traffic and the control plane. It intercepts packets at the network level, performs initial analysis using DPI techniques, and forwards relevant events to the USE for further processing. This intermediary approach enables precise traffic analysis while shielding the control logic from the complexity of heterogeneous protocols.
3Adaptability or versatility
If a centralized control architecture is used to manage all services, then adaptability to different protocols is improved, but the loss of time in processing and controlling multiple services increases
Solution Approach 1:
The patent implements preliminary action by having the NTS perform event detection and filtering before forwarding data to the USE. The network-level component pre-processes traffic by identifying relevant events based on configured criteria, reducing the volume of data that requires complex policy processing at the control level. This preliminary filtering action reduces processing time while maintaining comprehensive protocol adaptability.
4Productivity
If multiple probes are deployed to monitor different services simultaneously, then productivity of service monitoring is improved, but the device complexity and coordination overhead increase
Solution Approach 1:
The patent merges multiple probe functions into a unified two-level architecture where the NTS consolidates network-level monitoring capabilities and the USE consolidates control-level processing. Multiple service monitoring tasks are combined and coordinated through this unified structure, allowing parallel processing of different services while maintaining centralized policy management and reducing coordination complexity compared to independent probe deployments.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Disclosed herein is a two-level, network-based application control (NBAC) architecture for monitoring services provided via a packet-based network. The NBAC architecture comprises a Network Trigger System (NTS) provided at a network level to analyze data flows relating to services to be monitored to detect occurrence of configurable events, and to generate and send event reports; and a Usage Status Engine (USE) provided at a control level to configure the Network Trigger System to detect occurrence of events of interest, and to receive and process the event reports from the Network Trigger System to monitor the services.