VoIP Call Transfer Resource Release via Preliminary Drop

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication session transfer methods in VoIP systems consume processor resources and network bandwidth, as they wait for confirmation of a successful transfer before terminating the original connection, leading to inefficiencies.

Innovation Solution

Implementing a method where a media terminal adapter (MTA) can initiate a drop request for a communication session after sending a transfer request, independent of confirmation that the new connection has been established, thereby reducing processing time and freeing up network bandwidth.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the first party's device waits for confirmation that the transfer has been completed before terminating participation, then the communication session transfer reliability is improved, but the processor resource consumption increases and the time delay increases

Engineering Contradiction:
Improvecommunication session transfer reliabilityVSAvoidprocessor resource efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The first party's device sends a preliminary indication message to the network entity before the transfer is fully completed, allowing the network to prepare for resource release in advance. This preliminary action reduces the waiting time for resource release while maintaining transfer reliability through subsequent confirmation messages.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the network entity sends confirmation messages to the first party's device about transfer completion status. This feedback allows the device to make informed decisions about when to terminate participation and release resources, balancing reliability with resource efficiency.

Inventive Principle:
Principle #23Feedback

2Reliability

If the first party's device waits for confirmation that the transfer has been completed before terminating participation, then the communication session transfer reliability is improved, but the time delay increases

Engineering Contradiction:
Improvecommunication session transfer reliabilityVSAvoidtransfer completion time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The first party's device sends a preliminary indication message to the network entity before the transfer is fully completed, allowing the network to prepare for resource release in advance. This preliminary action reduces the waiting time for resource release while maintaining transfer reliability through subsequent confirmation messages.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the network entity sends confirmation messages to the first party's device about transfer completion status. This feedback allows the device to make informed decisions about when to terminate participation and release resources, balancing reliability with resource efficiency.

Inventive Principle:
Principle #23Feedback

3Productivity

If the first party's device terminates participation immediately after sending the transfer request, then the processor resource efficiency is improved, but the communication session transfer reliability deteriorates

Engineering Contradiction:
Improveprocessor resource efficiencyVSAvoidcommunication session transfer reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The first party's device sends a preliminary indication message to the network entity before the transfer is fully completed, allowing the network to prepare for resource release in advance. This preliminary action reduces the waiting time for resource release while maintaining transfer reliability through subsequent confirmation messages.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the network entity sends confirmation messages to the first party's device about transfer completion status. This feedback allows the device to make informed decisions about when to terminate participation and release resources, balancing reliability with resource efficiency.

Inventive Principle:
Principle #23Feedback

4Stability of the object's composition

If the network bandwidth is consumed by the unneeded connection between the first and second parties, then the connection stability is improved, but the network resource efficiency deteriorates

Engineering Contradiction:
Improveconnection stabilityVSAvoidnetwork bandwidth efficiency
Core Design Contradiction:
Stability of the object's compositionVSLoss of energy

Solution Approach 1:

The first party's device sends a preliminary indication message to the network entity before the transfer is fully completed, allowing the network to prepare for resource release in advance. This preliminary action reduces the waiting time for resource release while maintaining transfer reliability through subsequent confirmation messages.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the network entity sends confirmation messages to the first party's device about transfer completion status. This feedback allows the device to make informed decisions about when to terminate participation and release resources, balancing reliability with resource efficiency.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8457294B1Transferring a communication session
Publication Date: 2013.06.04 ARRIS ENTERPRISES LLC
  • US8457294B1 patent drawing
  • US8457294B1 patent drawing
  • US8457294B1 patent drawing

AI summary

Methods, systems, and apparatus, including computer program products, in which a call transfer can be performed independently of a positive final response in a call transfer to the a third party subject of the call transfer. In some implementations, a first party to the communications session can send a drop/disconnect signal after initiating the call transfer or after receiving an acknowledgement of the initiation of a call transfer.