Media User Agent Layer for SIP Call Flow Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of SIP-based Next Generation Intelligent Networks (NGIN) in telecom systems, with varying network equipment interpretations and evolving service requirements, makes it difficult for traditional Finite State Machine (FSM) design patterns to efficiently manage call flows, leading to inflexibility and scalability issues.
Innovation Solution
An adaptive intelligence engine within the NGIN platform that evaluates SIP call legs, party capabilities, and network elements to dynamically select and execute call flow behaviors, allowing for real-time adaptation and customization of call flows based on specific operator needs and equipment capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional Finite State Machine (FSM) design patterns are used to manage SIP call flows, then the system maintains stability and predictability, but the system becomes inflexible and difficult to adapt to evolving service requirements and equipment capabilities
Solution Approach 1:
The patent segments the call flow management into separate, independently configurable components: call flow templates define the structure, while call flow behaviors define the specific actions. This segmentation allows each component to be developed, tested, and modified independently, improving adaptability without increasing overall system complexity.
Solution Approach 2:
The patent introduces dynamic elements by allowing call flow behaviors to be selected and executed based on runtime conditions rather than being fixed in a static FSM. The system can dynamically choose which behavior to execute based on the current call state and requirements, enabling flexibility while maintaining structured management.
2Reliability
If custom network call flows are specified for each operator and equipment configuration, then the system meets specific operational requirements, but the development and maintenance time increases significantly
Solution Approach 1:
The patent implements preliminary action by pre-defining call flow templates with common structures and patterns. These templates are prepared in advance and can be quickly instantiated and customized for specific operator requirements, eliminating the need to develop call flows from scratch each time and significantly reducing development time while maintaining compliance.
Solution Approach 2:
The patent enables copying and reusing of call flow templates and behaviors across different operator configurations. Once a call flow template is developed and validated, it can be copied and adapted for multiple operators with similar requirements, reducing repetitive development work and maintenance effort while ensuring consistent compliance standards.
3Adaptability or versatility
If the system supports multiple network types (fixed and mobile) with different call flows, then the system covers diverse service scenarios, but the specification complexity and management difficulty increase
Solution Approach 1:
The patent implements universality by designing call flow templates and behaviors that can be applied across multiple network types (fixed and mobile). The same template framework supports different network-specific behaviors through parameterization and conditional logic, allowing a single unified specification system to manage diverse service scenarios without increasing complexity.
Data Source
AI summary
A method of processing session initiation protocol (SIP) call flows, the method comprising, at a back-to-back user agent (B2BUA) configuring a media user agent (UA) layer to interface between a SIP UA layer and a Media B2BUA layer. for call flow operation in the SIP UA layer to Media B2B UA layer direction, the configuring comprises, at the media UA layer first mapping each message received from the SIP UA layer comprised of one of a plurality of SIP layer message types into one of a SDP offer message type, a SDP answer message type and a third message type different from the SDP offer message and SDP answer types, and passing each first mapped message to the Media B2B UA layer for processing.