Sidebar Calls via SIP REFER Commands

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for conducting private sidebar calls during multiparty teleconferences are cumbersome and expensive, requiring multiple phone lines and complex steps, and are not supported by current mobile telephone standards, making it difficult to maintain privacy and efficiency in global business communications.

Innovation Solution

The use of Session Initiation Protocol (SIP) commands, specifically the REFER and INVITE commands, to initiate and conduct sidebar or subconference calls in parallel with multiparty conference calls, allowing parties to create a private, parallel call without the need for multiple lines or complex announcements, by including a conference identifier in the SIP commands to maintain context and privacy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple phone lines are used to enable sidebar calls during multiparty conferences, then privacy and ability to conduct subconferences are improved, but device complexity and cost increase

Engineering Contradiction:
ImproveprivacyVSAvoidmultiple phone lines
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the multiparty conference call into separate parallel calls using SIP REFER commands. When a sidebar call is needed, the system divides the conference into the main conference and a separate subconference, allowing private discussions without requiring multiple physical phone lines. Each participant can be selectively transferred to different call paths.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses SIP REFER commands as an intermediary mechanism to manage call routing. Instead of requiring participants to manually switch between multiple phone lines, the SIP REFER command acts as a mediator that automatically routes participants to appropriate call paths, simplifying the interface while maintaining privacy and conference control.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple phone lines and complex steps are used for sidebar calls, then privacy is improved, but ease of operation deteriorates

Engineering Contradiction:
ImproveprivacyVSAvoidcomplex steps
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent enables self-service operation by allowing participants to initiate sidebar calls automatically through SIP REFER commands without requiring manual intervention to manage multiple phone lines. The system handles call routing, switching, and reconnection automatically, eliminating the need for complex manual steps while maintaining privacy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent changes the operational parameters from manual phone line management to automated SIP command-based routing. By transitioning from physical line switching to protocol-based call control, the system maintains privacy functionality while dramatically improving ease of operation through automated parameter management.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If parties hang up and redial conference numbers to conduct sidebars, then privacy is achieved, but loss of time increases

Engineering Contradiction:
ImproveprivacyVSAvoidhanging up and redialing
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary action by establishing parallel call paths during the conference call itself, rather than requiring participants to hang up and redial after the fact. The SIP REFER command initiates the sidebar call setup while the main conference is ongoing, so that when participants need to discuss privately, the infrastructure is already in place and they can transition seamlessly without time loss.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent maintains continuity of useful action by keeping the main conference call active while simultaneously establishing parallel sidebar calls. Instead of interrupting the main conference to handle sidebar requests, the system continues the main call and adds parallel subconferences, eliminating the need to hang up and redial and thus preventing time loss.

Inventive Principle:
Principle #20Continuity of useful action

4Adaptability or versatility

If existing mobile telephone standards are used for multiparty calls, then connectivity is achieved, but adaptability for sidebar calls deteriorates

Engineering Contradiction:
Improvesidebar call capabilityVSAvoidprotocol support
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent achieves universality by implementing sidebar call capability through SIP REFER commands that work across existing mobile telephone standards like GSM and UMTS. The same SIP infrastructure used for standard multiparty calls is extended to handle sidebar functionality, making the system multi-functional without requiring separate dedicated protocols for each call type.

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

Data Source

PatentUS7634074B2Method and apparatus for making sidebar calls
Publication Date: 2009.12.15 GOOGLE TECHNOLOGY HOLDINGS LLC
  • US7634074B2 patent drawing
  • US7634074B2 patent drawing
  • US7634074B2 patent drawing

AI summary

A method and apparatus for conducting a sidebar, subconference call from a multiparty conference call is provided. Once a party has joined a multiparty conference call, the party is able to initiate the subconference call by transmitting a session initiation protocol (SIP) command to a target party. Two SIP commands that may be employed to initiate the subconference call are the REFER command and the INVITE command. To allow the target party to distinguish between incoming communication requests related to the multiparty conference call from extraneous ones, the REFER or INVITE command includes at least one data field containing an identifier of the conference call referred the REFER or INVITE command. Once received and verified, the target party may respond accordingly to establish the subconference call. The target party's handset may reference data fields in the SIP command to those locally stored and known to be associated with the multiparty conference call. Where recognized, the handset may present the communication request to the target party along with an option to accept the communication request.