IP Library Granted Patent US 9,106,596
Granted Patent B2
US 9,106,596 · App. 14/298,146 · Granted Aug 11, 2015

Method and apparatus of configuring a data broadcast service

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 9,106,596
App. No.
14/298,146
Granted
Aug 11, 2015
Kind
B2
Abstract

Disclosed are an apparatus and method of broadcasting a message to one or more servers operating in one or more domains. One example method of operation may include creating a message to be broadcasted via user input provided by a user of a computer interface. The method may also include serializing the message to a predetermined format and transmitting the message to an application programming interface (API). The method may also provide scheduling a broadcast of the message based on the user input, and transmitting the message to the at least one server responsive to the scheduled broadcast.

Claims (37)

1. A method of broadcasting a message, the method comprising:

creating a message to be broadcasted based on at least one scheduling parameter of a calendar application;

serializing the message to a predetermined format;

transmitting the message to an application programming interface (API);

scheduling a broadcast of the message based on via a scheduling application of a broadcast server based on the at least one scheduling parameter; and

transmitting the message responsive to the scheduled broadcast.

2. The method of claim 1 , wherein the message is a calendar message comprising at least one date to be broadcast and at least time to be broadcast.

3. The method of claim 2 , wherein the serialized message is a JavaScript object notation message (JSON) comprising a subject portion that includes at least one date and time, and at least one body portion that includes other message information.

4. The method of claim 1 , further comprising:

receiving a hyper text transfer protocol (HTTP) response to confirm the at least one server's subscription to the broadcast, the HTTP response being received responsive to the broadcast message.

5. The method of claim 1 , wherein the message further comprises a target uniform resource locator (URL) associated with at least one server.

6. The method of claim 1 , wherein the message is broadcast to a plurality of domains via a HTTP POST message.

7. The method of claim 1 , wherein the message is broadcast to a REST endpoint device.

8. An apparatus configured to broadcast a message, the apparatus comprising:

a user interface configured to create a message to be broadcasted based on at least one scheduling parameter of a calendar application;

a processor configured to serialize the message to a predetermined format;

a transmitter configured to transmit the message to an application programming interface (API); and

wherein the processor is further configured to schedule a broadcast of the message via a scheduling application based on the at least one scheduling parameter, and the transmitter is further configured to transmit the message responsive to the scheduled broadcast.

9. The apparatus of claim 8 , wherein the message is a calendar message comprising at least one date to be broadcast and at least time to be broadcast.

10. The apparatus of claim 9 , wherein the serialized message is a JavaScript object notation message (JSON) comprising a subject portion that includes at least one date and time, and at least one body portion that includes other message information.

11. The apparatus of claim 8 , further comprising:

a receiver configured to receive a hyper text transfer protocol (HTTP) response to confirm the at least one server's subscription to the broadcast, the HTTP response being received responsive to the broadcast message.

12. The apparatus of claim 8 , wherein the message further comprises a target uniform resource locator (URL) associated with at least one server.

13. The apparatus of claim 8 , wherein the message is broadcast to a plurality of domains via a HTTP POST message.

14. The apparatus of claim 8 , wherein the message is broadcast to a REST endpoint device.

15. A non-transitory computer readable storage medium comprising instructions that when executed cause a processor to perform broadcasting a message, the processor being further configured to perform:

creating a message to be broadcasted based on at least one scheduling parameter of a calendar application;

serializing the message to a predetermined format;

transmitting the message to an application programming interface (API);

scheduling a broadcast of the message via a scheduling application of a broadcast server based on the at least one scheduling parameter; and

transmitting the message responsive to the scheduled broadcast.

16. The non-transitory computer readable storage medium of claim 15 , wherein the message is a calendar message comprising at least one date to be broadcast and at least time to be broadcast.

17. The non-transitory computer readable storage medium of claim 16 , wherein the serialized message is a JavaScript object notation message (JSON) comprising a subject portion that includes at least one date and time, and at least one body portion that includes other message information.

18. The non-transitory computer readable storage medium of claim 16 , wherein the processor is further configured to perform:

receiving a hyper text transfer protocol (HTTP) response to confirm the at least one server's subscription to the broadcast, the HTTP response being received responsive to the broadcast message.

19. The non-transitory computer readable storage medium of claim 16 , wherein the message further comprises a target uniform resource locator (URL).

20. The non-transitory computer readable storage medium of claim 16 , wherein the message is broadcast to a plurality of domains via a HTTP POST message.

Assignments (11)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 27, 2025
From: FIGUEROA, JAVIER ALEJANDRO
To: KASEYA INTERNATIONAL LIMITED
Reel/Frame 071548/0286 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Mar 24, 2025
From: KASEYA LIMITED
To: MORGAN STANLEY SENIOR FUNDING, INC., AS SECOND LIEN COLLATERAL AGENT
Reel/Frame 070608/0176 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Mar 21, 2025
From: KASEYA LIMITED
To: MORGAN STANLEY SENIOR FUNDING, INC., AS FIRST LIEN COLLATERAL AGENT
Reel/Frame 070586/0814 →
CHANGE OF NAME Recorded Oct 27, 2023
From: DATTO, INC.
To: DATTO, LLC
Reel/Frame 065385/0256 →
RELEASE OF SECURITY INTEREST Recorded May 8, 2019
From: WELLS FARGO BANK, NATIONAL ASSOCIATION
To: KASEYA LIMITED
Reel/Frame 049122/0181 →
RELEASE OF SECURITY INTEREST Recorded May 8, 2019
From: VEEAM SOFTWARE LIMITED
To: KASEYA LUXEMBOURG HOLDINGS S.C.A.
Reel/Frame 049122/0138 →
SUBORDINATED SECOND LIEN US PATENT SECURITY AGREEMENT Recorded Jun 1, 2018
From: SPANNING CLOUD APPS LLC; UNITRENDS, INC.; KASEYA LIMITED; RAPIDFIRE TOOLS INC.
To: FABSTONE INVESTMENTS LLC
Reel/Frame 046286/0755 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT Recorded May 31, 2017
From: SILICON VALLEY BANK
To: KASEYA LIMITED
Reel/Frame 042642/0023 →
SECURITY INTEREST Recorded May 26, 2017
From: KASEYA LIMITED
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS AGENT
Reel/Frame 042589/0410 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 1, 2014
From: KASEYA INTERNATIONAL LIMITED
To: KASEYA LIMITED
Reel/Frame 033880/0921 →
SECURITY INTEREST Recorded Jul 14, 2014
From: KASEYA LIMITED
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 033312/0618 →