IP Library Granted Patent US 10,602,323
Granted Patent B2
US 10,602,323 · App. 16/257,977 · Granted Mar 24, 2020

Messaging service application programming interface

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 10,602,323
App. No.
16/257,977
Granted
Mar 24, 2020
Kind
B2
Abstract

In one example, a method includes receiving, from a client application executing on a client device, a message transmission request including an identifier associated with a recipient device. The message transmission request is added to an outbound queue based on determining the message transmission request is valid. A message is transmitted to the recipient device based on the message transmission request being included in the outbound queue. Status information specifying a status of transmission of the message is obtained, the status information including an indication of successful transmission of the message. A record of the message transmission request is stored responsive to the causing the transmission of the message, the storing the record including storing the message and the indication of successful transmission of the message.

Claims (33)

1. A system comprising:

one or more processors and executable instructions accessible on a computer-readable medium that, when executed, cause the one or more processors to perform operations comprising:

receiving, from a client application executing on a client device, a message transmission request including an identifier associated with a recipient device;

adding the message transmission request to an outbound queue based on determining the message transmission request is valid;

causing transmission of a message to the recipient device based on the message transmission request being included in the outbound queue;

obtaining status information specifying a status of transmission of the message, the status information including an indication of successful transmission of the message; and

storing a record of the message transmission responsive to the causing the transmission of the message, the storing the record including storing the message and the indication of successful transmission of the message.

2. The system of claim 1 , wherein the causing transmission of the message comprises transmitting a request to a Short Message Service (SMS) aggregator, the request identifying the identifier and a carrier associated with the recipient device, the SMS aggregator to route the message to the carrier.

3. The system of claim 1 , wherein a predefined messaging standard specifies a particular format for the message.

4. The system of claim 1 , wherein the message is transmitted as a Short Message Service (SMS) message.

5. The system of claim 1 , wherein the message transmission request is a Hypertext Transfer Protocol (HTTP) request.

6. A method comprising:

receiving, from a client application executing on a client device, a message transmission request including an identifier associated with a recipient device;

adding the message transmission request to an outbound queue based on determining the message transmission request is valid;

causing transmission of a message to the recipient device based on the message transmission request being included in the outbound queue;

obtaining status information specifying a status of transmission of the message, the status information including an indication of successful transmission of the message; and

storing a record of the message transmission request responsive to the causing the transmission of the message, the storing the record including storing the message and the indication of successful transmission of the message.

7. The method of claim 6 , further comprising determining that the identifier is valid by determining that the identifier includes a particular number of characters.

8. The method of claim 6 , wherein the causing transmission of the message comprises transmitting a request to a Short Message Service (SMS) aggregator, the request identifying the identifier and a carrier associated with the recipient device, the SMS aggregator to route the message to the carrier.

9. The method of claim 6 , wherein a predefined messaging standard specifies a particular format for the message.

10. The method of claim 6 , wherein the message is transmitted as a Short Message Service (SMS) message.

11. The method of claim 6 , wherein the message transmission request is a Hypertext Transfer Protocol (HTTP) request.

12. A non-transitory machine-readable medium comprising instructions which, when executed by a machine, cause the machine to perform operations comprising, at least:

receiving, from a client application executing on a client device, a message transmission request including an identifier associated with a recipient device;

adding the message transmission request to an outbound queue based on determining the message transmission request is valid;

causing transmission of a message to the recipient device based on the message transmission request being included in the outbound queue;

obtaining status information specifying a status of transmission of the message, the status information including an indication of successful transmission of the message; and

storing a record of the message transmission request responsive to the causing the transmission of the message, the storing the record including storing the message and the indication of successful transmission of the message.

13. The medium of claim 12 , wherein the operations further comprise determining that the identifier is valid by determining that the identifier includes a particular number of characters.

14. The medium of claim 12 , wherein the causing transmission of the message comprises transmitting a request to a Short Message Service (SMS) aggregator, the request identifying the identifier and a carrier associated with the recipient device, the SMS aggregator to route the message to the carrier.

15. The medium of claim 12 , wherein a predefined messaging standard specifies a particular format for the message.

16. The medium of claim 12 , wherein the message is transmitted as a Short Message Service (SMS) message.

17. The medium of claim 12 , wherein the message transmission request is a Hypertext Transfer Protocol (HTTP) request.

Assignments (9)
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT REEL 055212, FRAME 0964 Recorded Aug 30, 2024
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: ZETA GLOBAL CORP.
Reel/Frame 068822/0167 →
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Recorded Aug 30, 2024
From: ZETA GLOBAL CORP.; ZSTREAM ACQUISITION LLC
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 068822/0154 →
RELEASE OF SECURITY INTEREST Recorded Feb 11, 2021
From: FIRST EAGLE PRIVATE CREDIT, LLC, AS SUCCESSOR TO NEWSTAR FINANCIAL, INC
To: ZBT ACQUISITION CORP.; ZETA GLOBAL CORP.; 935 KOP ASSOCIATES, LLC
Reel/Frame 055282/0276 →
NOTICE OF GRANT OF SECURITY INTEREST IN PATENTS Recorded Feb 3, 2021
From: ZETA GLOBAL CORP.
To: BANK OF AMERICA, N.A.
Reel/Frame 055212/0964 →
SECURITY INTEREST Recorded Dec 3, 2020
From: ZETA GLOBAL CORP.
To: FIRST EAGLE PRIVATE CREDIT, LLC
Reel/Frame 054585/0770 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 23, 2020
From: RUTTENBUR, ERIC P.
To: EBAY, INC.
Reel/Frame 051602/0086 →
CHANGE OF NAME Recorded Jan 23, 2020
From: ZETA INTERACTIVE CORP.
To: ZETA GLOBAL CORP.
Reel/Frame 051602/0720 →
CHANGE OF NAME Recorded Jan 23, 2020
From: 935 KOP ASSOCIATES, LLC
To: ZETA INTERACTIVE CORP.
Reel/Frame 051602/0501 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 23, 2020
From: EBAY INC.
To: 935 KOP ASSOCIATES, LLC
Reel/Frame 051602/0278 →