Service Traffic Identification Module for Web Service Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication network monitoring systems struggle to effectively monitor and manage web services, which decouple signaling and data from the infrastructure, making it difficult for network operators to police services, generate billing records, and provide value-added services due to the lack of scalable solutions for third-party services.
Innovation Solution
A network resident monitoring system comprising a service traffic identification module, traffic monitor, and interface that identifies and monitors web service traffic, compiles usage statistics, polices usage, generates billing records, and mirrors traffic, allowing for transparent monitoring of third-party services without requiring orchestration within the network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web services decouple signaling and data from communication network infrastructure, then new data services and revenue opportunities are facilitated, but service monitoring and control become more difficult
Solution Approach 1:
The patent introduces a service monitoring system that acts as an intermediary between web service traffic and network operators. This system includes a service traffic identification module that intercepts and analyzes service traffic, extracting monitoring information without requiring changes to the web service infrastructure itself. The intermediary captures service-level statistics, usage patterns, and performance metrics while maintaining the decoupled architecture that enables service flexibility.
2Measurement precision
If service-specific proxies are deployed for each third party web service, then monitoring capability is achieved, but scalability is compromised with high bit rate services and increasing service offerings
Solution Approach 1:
The patent implements a universal service monitoring system that can handle multiple types of web services and traffic patterns through a single platform. The service traffic identification module is designed to be service-agnostic, capable of identifying and monitoring various web service protocols (SOAP, REST, XML-RPC) using common monitoring techniques. This multi-functional approach eliminates the need for service-specific proxies while maintaining monitoring accuracy across diverse service offerings.
Solution Approach 2:
The system creates simplified copies or representations of service traffic characteristics rather than requiring full service-specific monitoring infrastructure. By capturing essential service attributes and traffic patterns in a standardized format, the system can monitor diverse web services without replicating complex service-specific monitoring logic for each service type.
3Reliability
If existing SBCs are used for monitoring, then SIP-based communication monitoring is available, but web service traffic parsing and processing cannot be performed
Solution Approach 1:
The patent transforms the monitoring approach by changing the parameters of service identification from protocol-specific signatures to more generic service characteristic parameters. The service traffic identification module uses adaptable identification criteria that can be configured for different web service protocols, allowing the same monitoring infrastructure to handle multiple protocols by adjusting identification parameters rather than requiring protocol-specific monitoring devices.
Data Source
AI summary
Service-centric communication network monitoring apparatus and methods are provided. Service traffic, associated with a third-party service provided by an external service provider that is controlled independently of a communication network, is identified in communication traffic that is being transferred through that communication network. The identified service traffic is monitored, for example, to compile service usage statistics, to police usage of the service, to generate billing records for usage of the service, and/or to mirror the identified service traffic. A registry in which the service is registered may interact with a monitoring system of the communication network so as to establish monitoring for the service traffic.