IP Library › Granted Patent US 12,389,207
Granted Patent B2
US 12,389,207 · App. 18/589,452 · Granted Aug 12, 2025

System and method for expanded reach rich business messaging

Inventors: Inderpal Singh Mumick (Berkeley Heights, NJ); Surinder Singh Anand (Highland, NJ)
Assignee: GUPSHUP INC.
H04W4/14H04L51/046H04L51/23H04L51/58
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,389,207
App. No.
18/589,452
Granted
Aug 12, 2025
Kind
B2
Abstract

A method and a system employing an expanded reach rich messaging application (ERRMA) for creating and transmitting a rich message or an equivalent rich message is provided. The ERRMA receives a request to send a rich message on a specified rich messaging channel (SRMC) to a user's mobile number. The ERRMA determines whether the user's mobile number is enabled for receiving rich messages on the SRMC. Upon a successful determination, the ERRMA creates and transmits the rich message on the SRMC to the user's mobile number. Upon an unsuccessful determination, the ERRMA determines whether the user's mobile number is enabled for receiving the rich message on an alternative rich messaging channel. Upon determining that the user's mobile number is enabled for receiving the rich message on the alternative rich messaging channel, the ERRMA creates and transmits the equivalent rich message on the alternative rich messaging channel to a user device.

Claims (46)

1. A method employing an expanded reach rich messaging application defining computer program instructions executable by at least one processor for transmitting a rich message, said method comprising:

receiving said rich message from a rich message application programming interface for a specified rich messaging channel;

identifying whether a recipient of said rich message is active on said specified rich messaging channel;

upon identifying that said recipient of said rich message is active on said specified rich messaging channel, transmitting said rich message on said specified rich messaging channel to said recipient;

upon identifying that said recipient of said rich message is inactive on said specified rich messaging channel, identifying whether said recipient of said rich message is active on one or more of a plurality of alternative rich messaging channels;

upon identifying that said recipient of said rich message is active on one or more of a plurality of alternative rich messaging channels, creating an equivalent rich message for transmitting on said identified one or more plurality of alternative rich messaging channels; and

transmitting said created equivalent rich message to said recipient on said identified one or more plurality of alternative rich messaging channels.

2. The method of claim 1 , further comprising:

transmitting said rich message to said recipient as a standard short message service message if said recipient of said rich message is identified as inactive on said specified rich messaging channel and said one or more of said alternative rich messaging channels.

3. The method of claim 1 , further comprising:

concurrently (a) sending said rich message over said specified rich messaging channel and (b) sending said created equivalent rich message over at least one of said plurality of alternative rich messaging channels, to increase chances of delivery of said rich message or said created equivalent rich message; and

revoking said created equivalent rich message as soon as said rich message is delivered or revoking said rich message as soon as said created equivalent rich message is delivered.

4. The method of claim 1 , wherein said one or more of said alternative rich messaging

channels are selected based on one or more factors comprising:

size of said rich message;

cost of sending said rich message via said specified rich messaging channel and

said one or more of said alternative rich messaging channels in terms of standard

pricing and dynamic pricing based on traffic patterns;

history of said recipient in terms of message delivery status, message delivery time, message read status, message read time, and user response; and

maintaining consistency by sending said rich message on a single rich messaging channel instead of switching between a plurality of rich messaging channels.

5. A method employing an expanded reach rich messaging application defining computer program instructions executable by at least one processor for exchanging rich communication services messages via a rich business messaging channel, said method comprising:

receiving a request to send said rich communication services message on a rich communication services channel from an entity to a mobile number of a user, wherein said rich communication services message is created using an application programming interface;

determining whether said mobile number of said user is enabled for receiving said rich communication services message on said rich communication services channel;

upon determination that said mobile number of said user is not enabled for receiving said rich communication services message on said rich communication services channel, determining whether said mobile number of said user has exchanged equivalent rich communication services messages on said rich business messaging channel;

upon successful determination that said mobile number of said user has exchanged said equivalent rich communication services messages on said rich business messaging channel, performing steps comprising:

determining a rich business messaging identifier mapped to said mobile number of said user;

creating an equivalent rich communication services message on said rich business messaging channel for said mobile number of said user by translating said rich communication services message into a rich business message; and

transmitting said created equivalent rich communication services message on said rich business messaging channel to said rich business messaging identifier mapped to said mobile number of said user; and

upon determination that said mobile number of said user has not exchanged said equivalent rich communication services messages on said rich business messaging channel, performing steps comprising:

creating an internal identifier configured to securely map to said mobile number of said user;

creating an equivalent short message service message comprising a uniform resource locator encoded with said internal identifier;

transmitting said created equivalent short message service message with said uniform resource locator to said mobile number of said user; and

exchanging said equivalent rich communication services messages on said rich business messaging channel upon clicking said uniform resource locator by said user.

6. The method of claim 5 , further comprising transmitting subsequent equivalent rich communication services messages to said mapped rich business messaging identifier on said rich business messaging channel once said uniform resource locator has been clicked.

7. The method of claim 5 , wherein a username of said user, a universally unique identifier, and a globally unique identifier are excluded in said uniform resource locator transmitted to said mobile number of said user.

8. The method of claim 5 , further comprising:

receiving a mapping between said mobile number of said user and a business messaging channel-specific identifier and storing said mapping for future use; and

maintaining a mapping of said mobile number of said user and said internal identifier used to construct said uniform resource locator instead of including said mobile number of said user in said uniform resource locator transmitted to said mobile number of said user.

9. A method employing an expanded reach rich messaging application defining computer program instructions executable by at least one processor for creating and transmitting a rich message, said method comprising:

receiving a request to send a rich message on a specified rich messaging channel from an entity to a mobile number of a user;

determining whether said mobile number of said user is enabled for receiving said rich message on said specified rich messaging channel;

upon successful determination that said mobile number of said user is enabled for receiving said rich message on said specified rich messaging channel, creating and transmitting said rich message on said specified rich messaging channel to said mobile number of said user;

upon determination that said mobile number of said user is not enabled for receiving said rich message on said specified rich messaging channel, determining whether said mobile number of said user has exchanged a rich communication services message with said entity on an alternative rich business messaging channel;

upon successful determination that said mobile number of said user has exchanged said rich communication services message with said entity on said alternative rich business messaging channel, determining a rich business messaging channel-specific identifier of said user mapped to said mobile number of said user;

creating an equivalent rich message on said alternative rich business messaging channel; and

transmitting said created equivalent rich message to said mobile number of said user using said rich business messaging channel-specific identifier of said user.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 23, 2025
From: MUMICK, INDERPAL SINGH; ANAND, SURINDER SINGH
To: GUPSHUP INC
Reel/Frame 071799/0235 →
Continuity (3)
Continuation 18167837 · Feb 11, 2023
Provisional Application 63309415 · Feb 11, 2022
Related Publication 20240205645A1 · Jun 20, 2024
References Cited (8)
US 12112321B2 · Tiwari · 2024 [cited by examiner]
US 12112350B2 · Logvinov · 2024 [cited by examiner]
US 12112582B2 · Ha · 2024 [cited by examiner]
US 12113930B2 · Zhao · 2024 [cited by examiner]
US 12113932B2 · Montero · 2024 [cited by examiner]
US 20200387887A1 · Rathod · 2020 [cited by examiner]
US 20210359991A1 · Mumick · 2021 [cited by examiner]
US 20210383399A1 · Hayes, Jr. · 2021 [cited by examiner]