Remote Party Notification in IMS Media Replication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In 3GPP Release 10 IMS systems, remote parties are unaware of additional users or devices joining a collaborative session, leading to privacy and billing concerns, as they are not informed or consulted about the replication of media flows to new devices.

Innovation Solution

Implementing additional signaling to notify remote parties of new device additions and allowing them to accept or reject these changes, using an extended Session Description Protocol (SDP) with an 'a=target' attribute and out-of-band or in-band signaling to inform users of the requested IUT operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If media flow replication is implemented to allow multiple devices to participate in a collaborative session, then the versatility and collaboration capability of the system is improved, but the privacy and billing control for remote parties deteriorates as they are not informed of the changes

Engineering Contradiction:
Improvecollaborative session capabilityVSAvoidremote party awareness of session changes
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system implements feedback by notifying the remote party of media flow replication requests through signaling messages. The remote party receives information about the requested replication, can review the details, and provides feedback by accepting or rejecting the request. This ensures the remote party remains informed and maintains control over session changes.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary action by notifying the remote party before actually implementing the media flow replication. The notification is sent prior to the replication taking effect, allowing the remote party to review and provide consent in advance. This prevents unexpected changes and gives the remote party time to prepare for the session modification.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If media flow replication is performed without remote party notification, then the system operation efficiency is improved, but the privacy and billing concerns of remote parties are not addressed

Engineering Contradiction:
Improvesession setup speedVSAvoidprivacy and billing concerns
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The system uses feedback mechanisms to notify remote parties of replication requests and receive their consent. This feedback loop ensures privacy and billing concerns are addressed while maintaining efficient operation. The remote party's response is recorded and used to determine whether the replication should proceed.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The notification is sent as a preliminary action before the replication is executed. This allows the system to maintain high productivity by proceeding with replication once consent is obtained, while still addressing privacy and billing concerns through advance notification and consent mechanisms.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If the system automatically replicates media flows to new devices, then the ease of operation is improved, but the control and awareness of remote parties over their session deteriorates

Engineering Contradiction:
Improvedevice addition simplicityVSAvoidremote party session control
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system implements feedback by notifying the remote party of the requested replication and waiting for their response. This feedback mechanism maintains ease of operation for the initiating party while ensuring the remote party retains control over their session. The remote party can accept or reject the replication based on their preferences.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary notification before replication, allowing the remote party to review and provide consent in advance. This preliminary action maintains ease of operation by automating the process once consent is given, while ensuring the remote party maintains control and awareness of session changes.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8838816B2System and method for remote party restrictions in a communications system
Publication Date: 2014.09.16 FUTUREWEI TECHNOLOGIES INC
  • US8838816B2 patent drawing
  • US8838816B2 patent drawing
  • US8838816B2 patent drawing

AI summary

A system and method for remote party restrictions in a communications system are provided. A method for controller operations includes receiving a request from a first communications device to replicate a media flow that is being transmitted to the first communications device from a second communications device during a session, where the replicated media flow is to be provided to a third communications device, and where the second communications device is operated by a remote user. The method also includes allocating resources to a transmission of the replicated media flow to the third communications device, notifying the remote user of the request, and determining a response of the remote user to the request.