Service Identification Logic for Network Traffic Prioritization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems cannot provide priority processing for specific services within an application server, as they lack the ability to identify network communications at a service-level between different services of the same application server, hindering efficient network traffic management.

Innovation Solution

The implementation of service identification logic that monitors software applications to identify priority services and their associated network communications, allowing for dynamic prioritization of network traffic by using unique source port values to mark packets for priority processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If priority processing is provided to an application server as a whole, then network communications from the application server receive priority, but individual services within the application server cannot be differentiated or prioritized separately

Engineering Contradiction:
Improvenetwork communication efficiencyVSAvoidservice-level identification capability
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the application server into individual services by introducing service identification logic that can distinguish and separately prioritize network communications from different services within the same application server. This allows granular control at the service level rather than treating the entire application server as a single unit.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces service identification logic as an intermediary component between the application server and the network communication processing system. This intermediary captures service-level information (such as source port values) and uses it to enable differentiated priority processing without modifying the application server itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If service-level identification is implemented to enable individual service prioritization, then network traffic management precision is improved, but system complexity increases

Engineering Contradiction:
Improveservice-level communication identificationVSAvoidmonitoring and identification system
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The service identification logic leverages existing service-level information (such as source port values) that is already generated by the services themselves during normal operation. Rather than requiring complex external monitoring infrastructure, the system uses these self-generated identifiers to enable precise service-level identification and prioritization.

Inventive Principle:
Principle #25Self-service

3Reliability

If priority processing is given to all services in an application server, then network communications receive priority, but critical services cannot be distinguished from non-critical services

Engineering Contradiction:
Improvepriority processing guaranteeVSAvoidnetwork communication efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies local quality by enabling different priority treatments for different services within the same application server. Critical services can be identified and given higher priority while non-critical services receive standard processing, allowing optimized resource allocation based on the specific needs of each service rather than uniform treatment.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS7555547B2System and method for identifying network communications of a priority service among a plurality of services
Publication Date: 2009.06.30 ORACLE INT CORP
  • US7555547B2 patent drawing
  • US7555547B2 patent drawing
  • US7555547B2 patent drawing

AI summary

Systems, methodologies, media, and other embodiments associated with identifying network communications of services are described. One example system embodiment includes a service identification logic configured to monitor execution of software of an application server and identify services being processed. The service identification logic can further include a logic configured to identify network communications associated with an identified service. The example system may also include a notification logic configured to notify one or more network devices to provide priority processing for the network communications associated with the identified service.