RCS Message Template GUI with Concurrent Preview

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Businesses face difficulties in creating Rich Communication Services (RCS) message templates suitable for business communications due to the need for complex JavaScript Object Notation (JSON) programming and reliance on external entities for template generation, hindering widespread adoption of RCS messaging.

Innovation Solution

A graphical user interface (GUI) system that allows users to easily generate RCS message templates by inputting content and viewing a concurrent representative display, enabling the creation of static and parameterized message content without manual coding, and allowing businesses to generate and send customized RCS messages independently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If businesses use existing technologies to generate RCS templates, then they can send RCS messages, but they must write complicated JSON programming or rely on external entities to generate templates

Engineering Contradiction:
Improveease of template generationVSAvoidprogramming complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system enables businesses to self-service template generation through a graphical user interface that allows direct creation of RCS message templates without requiring JSON programming knowledge or external service provider intervention. The GUI provides intuitive form fields and visual builders that automatically generate the underlying JSON structure.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces the mechanical/technical barrier of JSON programming with a graphical user interface system. Instead of requiring businesses to manually write or configure complex JSON code, the system provides visual form fields, drag-and-drop elements, and automated generation mechanisms that substitute the manual coding process.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Ease of operation

If businesses rely on external entities to generate RCS templates, then they can avoid programming complexity, but they lose independence and control over template generation

Engineering Contradiction:
Improveease of template generationVSAvoidbusiness independence
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system eliminates dependency on external entities by providing businesses with direct access to template generation capabilities through the graphical user interface. Businesses can independently create, edit, and manage their own RCS templates without requiring third-party service providers to generate templates for them.

Inventive Principle:
Principle #25Self-service

3Productivity

If businesses use SMS messaging to approximate RCS functionality, then they can send messages with links, but users are less likely to access content due to the extra step of clicking the link

Engineering Contradiction:
Improvemessage delivery capabilityVSAvoiduser engagement
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system changes the fundamental parameters of message delivery by enabling direct RCS message transmission with embedded interactive features, buttons, and media content that can be viewed and interacted with directly within the messaging interface, eliminating the need for external link clicks and improving user engagement.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11853693B2Creating rich communication services (RCS) message templates with graphical build and concurrent representative display
Publication Date: 2023.12.26 TELESIGN CORP
  • US11853693B2 patent drawing
  • US11853693B2 patent drawing
  • US11853693B2 patent drawing

AI summary

System and method for generating RCS message templates using a graphical user interface (GUI) with concurrent representative display. Templates are generated based on inputs via an input region of the GUI. Inputs can include a template name, a template type, and message content, which can include text, images, video, interactive buttons or icons, and so forth. Inputs can be static or parameterized. A representative message based on the template is concurrently displayed in a display region of the GUI. Based on the inputs, the system generates RCS message templates, such as by compiling JSON code corresponding to the user inputs and the representative display. The templates can be used to generate and send finalized RCS messages, such as text messages, rich cards, and so forth, by invoking a generated template and providing data for any parameterized fields in the template.