# US 8,751,574 B2 · Method and apparatus of configuring a data broadcast service > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,751,574 B2 - Document ID: US8751574B2 - Status: Granted - Kind: B2 - Application number: 13/099,832 - Filed: 2011-05-03 - Published: 2012-11-08 - Granted: 2014-06-10 - Earliest claimed: 2011-05-03 - Assignees: Kaseya International Limited - Applicants: Javier Alejandro Figueroa - Inventors: Javier Alejandro Figueroa - Web page: https://patentgrep.com/patent/US8751574B2 ## CPC - H04L 51/02: using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages - H04L 12/1881: {with schedule organisation, e.g. priority, sequence management} - H04L 67/142: Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms - H04L 67/75: Indicating network or usage conditions on the user display - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## 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 ### Claim 1 A method of broadcasting a message to at least one server, the method comprising: creating a message to be broadcasted via user input; serializing the message to a predetermined format; transmitting the message to an application programming interface (API) of a notification engine; scheduling a broadcast of the message via the notification engine to the at least one server based on the user input; and transmitting the message as a broadcast message to the at least one server via the notification engine responsive to the scheduled broadcast, wherein the broadcast message comprises content of the message and is configured as a request message format. ### Claim 2 (depends on 1) 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. ### Claim 3 (depends on 2) 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. ### Claim 4 (depends on 1) 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. ### Claim 5 (depends on 1) The method of claim 1, wherein the message further comprises a target uniform resource locator (URL) associated with the at least one server. ### Claim 6 (depends on 1) The method of claim 1, wherein the message is broadcast to a plurality of domains via a HTTP POST message. ### Claim 7 (depends on 1) The method of claim 1, wherein the message is broadcast to a REST endpoint device. ### Claim 8 An apparatus configured to broadcast a message to at least one server, the apparatus comprising: a user interface configured to receive user input to create a message to be broadcasted; a processor configured to serialize the message to a predetermined format; a transmitter configured to transmit the message to an application programming interface (API) of a notification engine; and wherein the processor is further configured to schedule a broadcast of the message via the notification engine to the at least one server based on the user input, and the transmitter is further configured to transmit the message as a broadcast message to the at least one server via the notification engine responsive to the scheduled broadcast, wherein the broadcast message comprises content of the message and is configured as a request message format. ### Claim 9 (depends on 8) 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. ### Claim 10 (depends on 9) 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. ### Claim 11 (depends on 8) 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. ### Claim 12 (depends on 8) The apparatus of claim 8, wherein the message further comprises a target uniform resource locator (URL) associated with the at least one server. ### Claim 13 (depends on 8) The apparatus of claim 8, wherein the message is broadcast to a plurality of domains via a HTTP POST message. ### Claim 14 (depends on 8) The apparatus of claim 8, wherein the message is broadcast to a REST endpoint device. ### Claim 15 A non-transitory computer readable storage medium comprising instructions that when executed cause a processor to perform broadcasting a message to at least one server, the processor being further configured to perform: creating a message to be broadcasted via user input; serializing the message to a predetermined format; transmitting the message to an application programming interface (API) of a notification engine; scheduling a broadcast of the message via the notification engine to the at least one server based on the user input; and transmitting the message as a broadcast message to the at least one server via the notification engine responsive to the scheduled broadcast, wherein the broadcast message comprises content of the message and is configured as a request message format. ### Claim 16 (depends on 15) 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. ### Claim 17 (depends on 16) 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. ### Claim 18 (depends on 16) 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. ### Claim 19 (depends on 16) The non-transitory computer readable storage medium of claim 16, wherein the message further comprises a target uniform resource locator (URL) associated with the at least one server. ### Claim 20 (depends on 16) 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.