Call Management Server SIP INVITE Signaling Coordination

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing call management methods using Session Initiation Protocol (SIP) are inflexible and limit the management operations that can be accessed via APIs, particularly when managing sessions between a managed endpoint and multiple destination endpoints, restricting the ability to handle multiple simultaneous calls efficiently.

Innovation Solution

A method involving the use of SIP INVITE messages with the same call identifier to establish and manage sessions between a managed endpoint and multiple destination endpoints, allowing for the reuse of existing signaling channels to connect with new endpoints without requiring the managed endpoint to answer new calls, thereby enabling more than two simultaneous calls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional SIP call management methods are used, then call establishment is straightforward, but the system is inflexible and limits management operations via API, restricting ability to handle multiple simultaneous calls

Engineering Contradiction:
Improvecall management flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a call management server as an intermediary between the managed endpoint and destination endpoints. This server handles SIP signaling and coordinates call establishment, allowing flexible API-controlled call management while keeping the managed endpoint relatively simple. The server mediates between multiple destinations and the endpoint, enabling versatile call routing without complicating the endpoint device itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments call management functionality into separate components: the call management server handles signaling and coordination, while the managed endpoint focuses on media processing. This segmentation allows the server to provide flexible API-controlled management operations and handle multiple simultaneous calls, while the endpoint remains relatively simple in structure.

Inventive Principle:
Principle #1Segmentation

2Reliability

If separate SIP INVITE messages are sent for each destination endpoint, then call establishment is reliable, but the managed endpoint must answer each new call, limiting simultaneous call capability to two calls

Engineering Contradiction:
Improvecall establishment reliabilityVSAvoidsimultaneous call capability
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges multiple SIP INVITE messages into a single coordinated signaling flow through the call management server. Instead of the managed endpoint receiving separate INVITEs that require individual answers, the server consolidates the signaling, establishing multiple call legs simultaneously. This allows the endpoint to maintain multiple simultaneous calls without needing to answer each one separately, thereby increasing productivity while maintaining reliable call establishment through the server's coordinated signaling.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The call management server acts as an intermediary that coordinates multiple SIP INVITE messages to different destination endpoints. It manages the signaling flow so that the managed endpoint establishes simultaneous calls without needing to individually answer each INVITE, thus improving simultaneous call capability while maintaining reliable connection establishment through the server's mediation.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If the managed endpoint answers each incoming SIP INVITE, then call connection is established, but this requirement restricts the number of simultaneous calls to two

Engineering Contradiction:
Improveautomatic call answeringVSAvoidnumber of simultaneous calls
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The call management server serves as an intermediary that handles the automatic answering coordination on behalf of the managed endpoint. It manages the SIP signaling flow so that multiple calls can be established without requiring the endpoint to manually answer each one, thereby maintaining ease of operation through automatic handling while increasing the number of simultaneous calls beyond the traditional two-call limit.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The call management server performs preliminary signaling actions to prepare and coordinate multiple call establishments before the endpoint needs to respond. By pre-coordinating the SIP INVITE messages and managing the call legs through the server, the system enables automatic establishment of multiple simultaneous calls without requiring the endpoint to individually answer each one, thus improving productivity while maintaining ease of operation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4089995A1Call management invoked by telephony api
Publication Date: 2022.11.16 VODAFONE GROUP SERVICES LTD
  • EP4089995A1 patent drawingFigure 1
  • EP4089995A1 patent drawingFigure 2
  • EP4089995A1 patent drawingFigure 3

AI summary

A method of managing call sessions invoked by API between a managed endpoint and a plurality of destination endpoints is provided. The method comprises sending (S122) a first session initiation protocol, SIP, INVITE to the managed endpoint, wherein the first SIP INVITE comprises a first call identifier and a media address of a first destination endpoint of the plurality of destination endpoints. The method further comprises sending (S180) a second SIP INVITE to the managed endpoint, wherein the second SIP INVITE comprises the first call identifier and a media address of a second destination endpoint of the plurality of destination endpoints, wherein the second destination endpoint is different from the first destination endpoint.