IP Library Granted Patent US 11,425,065
Granted Patent B1
US 11,425,065 · App. 17/521,342 · Granted Aug 23, 2022

Method of reconciling orphan A2P messaging delivery receipts

Inventors: Myron C. Prevatt, III (Tampa, FL); Madhusudhan Mysore (Bangalore, IN); Harish Kumar (Bangalore, IN); Chethan Ramaiah (Taluk Tumakuru, IN); Kiran Seetharamaiah (Bangalore, IN); Nithesh Sivasankaran (Bangalore, IN); Manjunath Lakshminarayan (Bangalore, IN); Trung K. Nguyen (Lakewood Ranch, FL); Abraham Elias (Lakewood Ranch, FL); Jamie Avins (Bradenton, FL)
Assignee: Syniverse Technologies, LLC
H04L51/046G06F16/906H04L51/30H04W4/14
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 11,425,065
App. No.
17/521,342
Granted
Aug 23, 2022
Kind
B1
Abstract

A method of delivering an orphan delivery receipt for a mobile-terminated message to a messaging platform from which the mobile-terminated message originated. A network of data exchange connectors is deployed, wherein each data exchange connector is associated with a messaging platform. When one of the messaging platforms receives a delivery receipt it cannot reconcile, the delivery receipt is replicated to all data exchange connectors. The data exchange connector associated with the messaging platform from which the mobile-terminated message originated identifies and consumes the delivery receipt based on predefined filtering criteria. The data exchange connector publishes the delivery receipt to the originator messaging platform. The originator messaging platform correlates the delivery receipt with the mobile-terminated message and posts the delivery receipt to a corresponding enterprise customer.

Claims (31)

1. A method of reconciling a delivery receipt for a mobile-terminated message comprising the steps of:

providing a first data exchange connector, wherein the first data exchange connector is associated with a first messaging platform;

providing a second data exchange connector, wherein the second data exchange connector is associated with a second messaging platform, wherein the first messaging platform and the second messaging platform are connected to a common messaging supplier and share connections associated with the common messaging supplier;

receiving, from the common messaging supplier by the second messaging platform, the delivery receipt for the mobile-terminated message originated from the first messaging platform, wherein the second messaging platform fails to correlate the delivery receipt with a record of the mobile-terminated message associated with the delivery receipt;

publishing, by the second messaging platform, the delivery receipt to the second messaging exchange network connector associated with the second messaging platform;

consuming, by the first data exchange connector, the delivery receipt;

publishing, by the first data exchange connector, the delivery receipt to the first messaging platform;

correlating, by the first messaging platform, the delivery receipt with the record of the mobile-terminated message originating from the first messaging platform; and

posting the delivery receipt to an entity that requested transmission of the mobile-terminated message.

2. The method of claim 1 , wherein the mobile-terminated message is an Application-to-Person (A2P) message.

3. The method of claim 1 , wherein the first data exchange connector and the second data exchange connectors belong to a network of data exchange connectors.

4. The method of claim 3 , wherein the delivery receipt is replicated to the network of data exchange connectors.

5. The method of claim 4 , wherein, upon the delivery receipt being replicated to the network of data exchange connectors, the first data exchange connector is configured to consume the delivery receipt based on a set of predefined filtering criteria.

6. The method of claim 1 , wherein responsive to the second messaging platform failing to correlate the delivery receipt with the mobile-terminated message, the delivery receipt is published to a predefined topic in a cluster of servers.

7. The method of claim 1 , wherein the first data exchange connector is a virtual machine application.

8. The method of claim 3 , wherein the network of data exchange connectors are based on a reactive streams or a container-native technology.

9. The method of claim 1 , wherein the first messaging platform and the second messaging platform are configured to send mobile-terminated messages using the common messaging supplier.

10. The method of claim 1 , wherein the common messaging supplier is a Short Message Service (SMS) operator or aggregator.

11. The method of claim 1 , wherein the first data exchange connector and the second data exchange connector are communicatively coupled to a global configuration store, and wherein setting adjustments entered via the global configuration store propagate to the first data exchange connector and the second data exchange connector.

12. A method of reconciling a delivery receipt for a mobile-terminated message comprising the steps of:

providing a network of a plurality of data exchange connectors, wherein each data exchange connector is associated with one or more messaging platforms, and wherein the one or more messaging platforms are connected to a common messaging supplier and share connections to the common messaging supplier;

receiving, from the common messaging supplier by a first data exchange connector of the plurality of data exchange connectors, the delivery receipt from a first messaging platform, wherein the first messaging platform failed to correlate the delivery receipt to the mobile-terminated message;

replicating the delivery receipt to the plurality of data exchange connectors;

consuming, by a second data exchange connector of the plurality of data exchange connectors, the delivery receipt based on one or more predefined filtering criteria, wherein the second data exchange connector is associated with a second messaging platform from which the mobile-terminated message originated; and

publishing, by the second data exchange connector, the delivery receipt to the second messaging platform, wherein the second messaging platform correlates the delivery receipt with the mobile-terminated message and posts the delivery receipt to an entity that requested transmission of the mobile-terminated message.

13. The method of claim 12 , wherein the mobile-terminated message is an Application-to-Person (A2P) message.

14. The method of claim 12 , wherein responsive to the first messaging platform failing to correlate the delivery receipt with the mobile-terminated message, the delivery receipt is published to a predefined topic in a cluster of servers.

15. The method of claim 12 , wherein the first data exchange connector is a virtual machine application.

16. The method of claim 12 , wherein the first data exchange connector is based on a reactive streams or a container-native technology.

17. The method of claim 12 , wherein the first messaging platform and the second messaging platforms are configured to send mobile-terminated messages using the common messaging supplier.

18. The method of claim 12 , wherein the common messaging supplier is a Short Message Service (SMS) operator or aggregator.

Assignments (3)
CORRECTIVE ASSIGNMENT TO CORRECT THE THE SECURITY INTEREST BY REMOVING THE INCORRECTLY ASSIGNED PATENT NOS. 8023971 AND 8819141 PREVIOUSLY RECORDED ON REEL 60072 FRAME 587. ASSIGNOR(S) HEREBY CONFIRMS THE NOTICE AND CONFIRMATION OF GRANT OF SECURITY INTEREST IN PATENTS. Recorded May 20, 2025
From: SYNIVERSE MESSAGING SOLUTIONS, LLC
To: BARCLAYS BANK PLC, AS COLLATERAL AGENT
Reel/Frame 071359/0846 →
NOTICE AND CONFIRMATION OF GRANT OF SECURITY INTEREST IN PATENTS Recorded May 16, 2022
From: SYNIVERSE MESSAGING SOLUTIONS, LLC
To: BARCLAYS BANK PLC, AS COLLATERAL AGENT
Reel/Frame 060072/0587 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 17, 2021
From: PREVATT, MYRON C., III; MYSORE, MADHUSUDHAN; KUMAR, HARISH; RAMAIAH, CHETHAN; SEETHARAMAIAH, KIRAN; SIVASANKARAN, NITHESH; LAKSHMINARAYAN, MANJUNATH; NGUYEN, TRUNG K.; ELIAS, ABRAHAM; AVINS, JAMIE
To: SYNIVERSE TECHNOLOGIES, LLC
Reel/Frame 058172/0855 →
Continuity (1)
Provisional Application 63110648 · Nov 6, 2020