Shared Back-to-Back User Agent for SIP Services

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Session Initiation Protocol (SIP) standards are resource-intensive when creating multiple Back-to-Back User Agents (B2BUAs) for multiple services within a communication session, as each service requires a separate instance, leading to inefficiencies in resource usage, especially under high loads.

Innovation Solution

A mechanism is introduced to share a single instance of a B2BUA among multiple services by using a Micro-Sequencer Application Router Service (MSARS) that creates and manages Micro-service SipSessions and requests, allowing multiple services to share a single B2BUA instance while adhering to SIP and JSR 289 standards, thereby reducing resource consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a separate B2BUA instance is created for each service, then service-specific functionality and flexibility are maintained, but resource consumption increases significantly under high loads

Engineering Contradiction:
Improveservice-specific functionalityVSAvoidresource consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

Multiple B2BUA instances are merged into a single shared B2BUA instance that serves multiple services. The patent implements a B2BUA pool where services can obtain B2BUA instances from a common pool, allowing resource sharing while maintaining service-specific functionality through configuration and routing mechanisms.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The B2BUA instance is designed to be universal and multi-functional, capable of serving multiple different services simultaneously. The patent achieves this by implementing a B2BUA that can handle different service types (e.g., conferencing, call recording, IVR) through a single instance using service identification and routing logic.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple B2BUA instances are created for multiple services, then each service can operate independently, but system complexity and resource overhead increase

Engineering Contradiction:
Improveservice independenceVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system is segmented into distinct functional components: a B2BUA pool manager, service-specific logic layers, and a shared B2BUA instance pool. This segmentation allows services to operate independently by interacting with the pool through standardized interfaces, reducing overall system complexity while maintaining service independence.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A B2BUA pool manager acts as an intermediary between services and B2BUA instances. This mediator handles the complexity of instance management, allocation, and coordination, allowing services to access B2BUA functionality without directly managing instance complexity, thus reducing service-side complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Use of energy by moving object

If a single B2BUA instance is shared among multiple services, then resource efficiency improves, but service privacy and isolation may be compromised

Engineering Contradiction:
Improveresource efficiencyVSAvoidservice privacy
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The shared B2BUA instance implements local quality by maintaining service-specific contexts, states, and configurations for each service it serves. The patent achieves this through service identification mechanisms that allow the B2BUA to switch between different service contexts, ensuring privacy and isolation while sharing the same physical instance.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

Service-specific contexts and configurations are pre-established and isolated within the B2BUA instance before services begin operation. The patent implements this by pre-configuring service contexts, authentication credentials, and state information, ensuring that services are isolated from each other's data and operations from the start.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9350594B2Shared back-to-back user agent
Publication Date: 2016.05.24 ARLINGTON TECHNOLOGIES LLC
  • US9350594B2 patent drawing
  • US9350594B2 patent drawing
  • US9350594B2 patent drawing

AI summary

Mechanisms for sharing a Back-to-Back User Agent (B2BUA) instance between a plurality of services are provided. By sharing a single B2BUA instance, the need for additional Session Initiation Protocol (SIP)-related container processes and objects is obviated. In particular, a Micro-Sequencer Application Router Service (MSARS) is provided with the ability to deploy and undeploy a plurality of Micro-Sequenced Services (MSS) as well as provide a definition of a Micro-service B2BUAhelper class which creates linked SIP Sessions.