Ad-hoc Group Presence Management in SIP/SIMPLE

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current SIP/SIMPLE extensions require external applications to manage group presence information, particularly for ad-hoc groups, leading to increased participant-side management responsibilities, such as updating conference servers and presence servers separately for conference call participants.

Innovation Solution

A system and method for ad-hoc group presence management in SIP/SIMPLE environments, where a presence server receives and processes information from a conference server to create and maintain a group presentity, reducing participant-side management by automating the update of presence information through conference documents and API instructions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If external applications are used to manage group presence information in SIP/SIMPLE extensions, then group presence information can be maintained, but participant-side management responsibility increases

Engineering Contradiction:
Improvegroup presence information maintenanceVSAvoidparticipant-side management responsibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The conference server automatically publishes presence information to the presence server without requiring participant intervention. The system serves itself by having the conference server directly interact with the presence server to maintain group presence information, eliminating the need for participants to manually update both servers.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The presence server acts as an intermediary between the conference server and participants. It receives presence information from the conference server and manages the presence data, reducing the operational burden on participants while maintaining reliable group presence information.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If participants separately update conference server and presence server, then both servers remain synchronized, but time and effort are lost

Engineering Contradiction:
Improveserver synchronizationVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The conference server proactively publishes presence information to the presence server as a preliminary action, ensuring synchronization before participants need the information. This prevents the need for participants to perform separate update operations and reduces overall update time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The update operations for the conference server and presence server are merged into a single action. When the conference server publishes presence information, both servers are updated simultaneously through this unified operation, eliminating the need for separate updates and reducing time loss.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If manual updates are performed by participants, then presence information can be maintained, but productivity decreases

Engineering Contradiction:
Improvepresence information maintenanceVSAvoidparticipant efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs self-service by automatically maintaining presence information through the conference server publishing to the presence server. This eliminates manual participant involvement in updates, maintaining reliable presence information while significantly improving participant productivity and efficiency.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7961667B2Ad-hoc groups in SIP/SIMPLE
Publication Date: 2011.06.14 RAKUTEN GROUP INC
  • US7961667B2 patent drawing
  • US7961667B2 patent drawing
  • US7961667B2 patent drawing

AI summary

A method for ad-hoc group presence management, the method including configuring a presence server to receive information regarding a group and entities belonging to the group and create a group presentity associated with the group, and providing information regarding a group and its entities to the presence server, thereby causing the presence server to create the group presentity.