RCS Interworking Function for Pre-UP and UP Client Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Interoperability issues exist between Pre-Universal Profile (Pre-UP) and Universal Profile (UP) clients in Rich Communication Services (RCS) due to different implementations of RCS services, leading to challenges in communication and service compatibility.

Innovation Solution

The implementation of an Interworking Function (IWF) that includes a Session Initiation Protocol (SIP) Application Server and a Message Session Relay Protocol (MSRP) Server, enabling protocol translation and message mediation between Pre-UP and UP clients for various RCS services such as messaging, file transfer, and group chat, by establishing necessary servers and servers for each service type.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If Pre-UP and UP clients use different RCS service implementations, then each client type can maintain its own service features, but interoperability between the two client types deteriorates

Engineering Contradiction:
Improveservice featuresVSAvoidinteroperability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an Interworking Function (IWF) as an intermediary system between Pre-UP and UP clients. The IWF includes a SIP Application Server and MSRP Server that perform protocol translation and message mediation, allowing clients with different RCS implementations to communicate seamlessly while maintaining their native service features.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If protocol translation and message mediation are performed between Pre-UP and UP clients, then interoperability is improved, but system complexity increases

Engineering Contradiction:
ImproveinteroperabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The Interworking Function is segmented into distinct components: a SIP Application Server for protocol translation and a MSRP Server for message mediation. This segmentation allows each component to handle specific translation tasks independently, making the overall system more manageable and maintainable despite the added complexity.

Inventive Principle:
Principle #1Segmentation

3Reliability

If SIP Application Server translates SIP MESSAGE to SIP INVITE for messaging interworking, then messaging compatibility is improved, but translation processing time increases

Engineering Contradiction:
Improvemessaging compatibilityVSAvoidtranslation processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The SIP Application Server performs preliminary protocol translation actions by maintaining translation rules and message templates in advance. Common messaging patterns are pre-configured with their translation mappings, allowing the server to quickly translate SIP MESSAGE to SIP INVITE without extensive real-time processing.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10397176B2Method and system for interworking of RCS universal profile and pre-universal profile clients
Publication Date: 2019.08.27 SYNIVERSE TECHNOLOGIES LLC
  • US10397176B2 patent drawing
  • US10397176B2 patent drawing
  • US10397176B2 patent drawing

AI summary

This invention is a system and method for an interworking function that handles communications between Rich Communication Services (RCS) Pre-Universal Profile (Pre-UP) and Universal Profile (UP) clients, and their Controlling Function and Participating Function service points. The interworking function supports the interworking for Pre-UP and UP clients in the following scenarios: 1) CPM Standalone Messaging and CPM 1-to-1 Chat, 2) CPM Chat and IM/SIMPLE Chat, 3) File Transfer by MSRP and File Transfer by HTTP, and 4) Open Group Chat and Closed Group Chat. The interworking function performs the necessary SIP message conversation and/or headers and message bodies manipulation, acts as MSRP client and server, acts as a HTTP server to store file for file transfer interworking, and acts as message proxy for Controlling Function and Participating Function.