Network Session Allocation for Trace-Capable Resource Separation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network entities face a trade-off between efficient implementation of primary functionalities such as call and data session processing and trace functionalities, which can negatively impact performance due to resource consumption and potential system outages from incorrect or excessive tracing.
Innovation Solution
A network entity separates traced and non-traced sessions by allocating messages to trace capable (T-Workers) and trace disabled (N-Workers) resource entities, optimizing processing requirements and load distribution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If trace functionalities are implemented in network entities alongside primary functionalities, then detailed monitoring and optimization information is obtained, but system performance deteriorates due to resource consumption and potential outages
Solution Approach 1:
The network entity is segmented into two distinct functional components: a primary functionality module for processing call and data sessions, and a trace functionality module for monitoring and logging. This segmentation allows trace operations to be performed on copied data without interfering with the performance-critical primary processing paths, thus maintaining both measurement precision and productivity.
Solution Approach 2:
The trace functionality is extracted as a separate, optional module that can be independently activated or deactivated. This extraction allows the system to obtain detailed monitoring information when needed while keeping the main processing entity lightweight and efficient during normal operations, resolving the contradiction between obtaining trace information and maintaining processing efficiency.
2Measurement precision
If excessive or incorrect tracing is performed, then comprehensive monitoring data is collected, but system reliability decreases due to resource exhaustion and potential outages
Solution Approach 1:
The trace functionality module implements dynamic control mechanisms where tracing parameters, including activation status and monitoring depth, can be adjusted in real-time based on system conditions. This dynamic adaptation allows the system to maintain comprehensive monitoring coverage when resources are available while automatically reducing tracing intensity to preserve system stability under resource constraints, thus resolving the contradiction between monitoring coverage and system reliability.
3Productivity
If trace capable resource entities are dedicated for traces and trace disabled resource entities for session processing, then load distribution is optimized, but device complexity increases
Solution Approach 1:
The network entity is designed with a universal architecture where the primary functionality module can handle both session processing and provide data for tracing, while the trace functionality module can operate independently when activated. This multi-functionality allows load distribution optimization without requiring completely separate physical systems, thus improving productivity while limiting the increase in device complexity through shared infrastructure.
Data Source
AI summary
There is provided receiving, at a network entity, a message from at least one peer network entity, determining, if the received message comprises information indicating a trace, at least one trace capable resource entity for processing the received message or subsequent messages of a session of the received message from a set of resource entities comprising trace capable resource entities and trace disabled resource entities, allocating the received message or the subsequent messages of a session of the received message to the determined at least one trace capable resource entity.