Search
Patexia Research
Issue Date Apr 15, 2021
Claim this application
PDF Unavailable

Patent Application - MOBILE PUSH NOTIFICATION FOR ROBOTIC PROCESS AUTOMATION (RPA) > Claims

  • 1. A cloud server comprising: a transceiver configured to receive a webhook event, wherein a webhook of the received webhook event was generated by a mobile application related to an orchestrator for robotic automation and wherein the received webhook event is triggered by the orchestrator; anda processor communicatively coupled with the transceiver, the processor configured to inspect the received webhook event for duplicates, where the received webhook event is batched for notification to a device based on a predetermined timer,wherein the transceiver is further configured to transmit, to a push notification service for delivery to the mobile application related to the orchestrator, a single notification send request having the notification with other notifications for an event type.
    • 2. The cloud server of claim 1 wherein the received webhook event includes one or more of a job faulted event, a schedule faulted event, a queue transaction failure event, or a queue transaction abandoned event.
      • 3. The cloud server of claim 2 wherein the processor is further configured to discard duplicate webhook events.
    • 4. The cloud server of claim 1 wherein the processor is further configured to set the timer until batching of notifications is processed.
    • 5. The cloud server of claim 1 wherein information received by the cloud server is cached to run-time memory.
    • 6. The cloud server of claim 1 wherein the processor purges all data related to the notification from the run-time memory upon sending of the notification.
    • 7. The cloud server of claim 1 wherein the processor is configured to queue notifications.
      • 8. The cloud server of claim 7 wherein the queuing is based on one or more of a push ID token that identifies a mobile device the event is intended for, an event type, and an event ID that identifies an event.
    • 9. The cloud server of claim 1 wherein the processor sets a maximum number of requests from the orchestrator.
  • 10. A method of providing push notifications, implemented in a cloud server, the method comprising: receiving, by a transceiver of the cloud server, a webhook event, wherein a webhook of the received webhook event was generated by a mobile application related to an orchestrator for robotic automation and wherein the received webhook event is triggered by the orchestrator;inspecting, by a processor of the cloud server, the received webhook event for duplicates, where the received webhook event is batched for notification to a device based on a predetermined timer; andtransmitting, by the transceiver of the cloud server, to a push notification service for delivery to the mobile application related to the orchestrator, a single notification send request having the notification with other notifications for an event type.
    • 11. The method of claim 10 wherein the received webhook event includes one or more of a job faulted event, a schedule faulted event, a queue transaction failure event, or a queue transaction abandoned event.
      • 12. The method of claim 11, further comprising discarding, by the processor, duplicate webhook events.
    • 13. The method of claim 10, further comprising setting, by the processor, the timer until batching of notifications is processed.
    • 14. The method of claim 10, further comprising caching information received by the cloud server to run-time memory.
    • 15. The method of claim 10, further comprising purging, by the processor, all data related to the notification from the run-time memory upon sending of the notification.
    • 16. The method of claim 10, further comprising queueing notifications by the processor.
      • 17. The method of claim 16 wherein the queuing is based on one or more of a push ID token that identifies a mobile device the event is intended for, an event type, and an event ID that identifies an event.
    • 18. The method of claim 10, further comprising setting, by the processor a maximum number of requests from the orchestrator.
  • 19. A non-transitory computer-readable medium for providing push notifications in a computer system, the non-transitory computer-readable medium having instructions recorded thereon, that when executed by a processor, cause the processor to perform operations including: receiving, from a transceiver operatively coupled with the processor, a webhook event, wherein a webhook of the received webhook event was generated by a mobile application related to an orchestrator for robotic automation and wherein the received webhook event is triggered by the orchestrator;inspecting, by the processor, the received webhook event for duplicates, where the received webhook event is batched for notification to a device based on a predetermined timer; andcausing the transceiver to transmit, to a push notification service for delivery to the mobile application related to the orchestrator, a single notification send request having the notification with other notifications for an event type.
    • 20. The non-transitory computer-readable medium of claim 19 wherein the received webhook event includes one or more of a job faulted event, a schedule faulted event, a queue transaction failure event, or a queue transaction abandoned event.
Menu