Message delivery in messaging networks

US9769110B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9769110-B2
Application numberUS-201715458553-A
CountryUS
Kind codeB2
Filing dateMar 14, 2017
Priority dateJan 25, 2008
Publication dateSep 19, 2017
Grant dateSep 19, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

In response to receipt of a request message from a requester, a reply message is created. The reply message includes a message identifier of the request message copied from the received request message. The reply message is published to each of a group of replicated message queues. The reply message is identifiable by the requester using the copied message identifier of the request message on any one of the group of replicated message queues prior to being consumed by the requester.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for message delivery in messaging networks, comprising: creating, by a requester computing device, a request message comprising a unique message identifier; sending, by the requester computing device via a first one of a plurality of second messaging manager systems, the request message to a first messaging manager system, wherein after the requester computing device sends the request message to the first messaging manager system the requester computing device disconnects from the first one of the plurality of second messaging manager systems; wherein a reply message is created by the first messaging manager system in response to receipt of the request message and the unique message identifier of the request message is copied into the reply message, wherein the reply message is published to each of a plurality of replicated message queues, and wherein the reply message is to be received by the requester computing device from any one of the plurality of replicated message queues; connecting, by the requester computing device, to a second one of the plurality of second messaging manager systems; specifying, by the requester computing device, the unique message identifier of the request message to receive the reply message; and receiving, by the requester computing device, the reply message from one of the plurality of replicated message queues. 2. The method of claim 1 , wherein the requester computing device disconnects from the first one of the plurality of second messaging manager systems when the connection fails between the requester computing device and the first one of the plurality of second messaging manager systems. 3. The method of claim 1 , wherein the first messaging manager system determines that the reply message is consumed by the requester computing device via a first replicated message queue of the plurality of replicated message queues, and sends a notification message to the plurality of replicated messages queues, other than the first replicated message queue, wherein the reply message is deleted from each of the plurality of replicated message queues based on receiving the notification message. 4. The method of claim 1 , wherein the request message is created with a reply-to destination as a replicated queue and the method further comprises saving the unique message identifier of the request message. 5. A computing device for message delivery in messaging networks, comprising: at least one processor; and a non-transitory computer-readable medium coupled with the at least one processor, the computer-readable storage medium having computer readable program code stored thereon that when executed by the at least one processor it causes the computing device to perform operations comprising: creating a request message comprising a unique message identifier; sending, via a first one of a plurality of second messaging manager systems, the request message to a first messaging manager system, wherein after sending the request message to the first messaging manager system the computing device disconnects from the first one of the plurality of second messaging manager system; wherein a reply message is created by the first messaging manager system in response to receipt of the request message and the unique message identifier of the request message is copied into the reply message, wherein the reply message is published to each of a plurality of replicated message queues, and wherein the reply message is to be received by the computing device from any one of the plurality of replicated message queues; connecting to a second one of the plurality of second messaging manager systems; specifying the unique message identifier of the request message to receive the reply message; receiving the reply message from one of the plurality of replicated message queues. 6. The computing device of claim 5 , wherein the computing device disconnects from the first one of the plurality of second messaging manager system when the connection fails between the computing device and the first one of the plurality of second messaging manager systems. 7. The computing device of claim 5 , wherein the first messaging manager system determines that the reply message is consumed by the computing device via a first replicated message queue of the plurality of replicated message queues, and sends a notification message to the plurality of replicated messages queues, other than the first replicated message queue, wherein the reply message is deleted from each of the plurality of replicated message queues based on receiving the notification message. 8. The computing device of claim 5 , wherein the request message is created with a reply-to destination as a replicated queue and the operations further comprise saving the unique message identifier of the request message. 9. A non-transitory computer-readable storage medium having computer readable program code stored thereon that when executed by at least one processor causes a computing device to perform operations comprising: creating a request message comprising a unique message identifier; sending via a first one of a plurality of second messaging manager systems, the request message to a first messaging manager system, wherein after sending the request message to the first messaging manager system the computing device disconnects from the first one of the plurality of second messaging manager systems; wherein a reply message is created by the backend messaging manager system in response to receipt of the request message and the unique message identifier of the request message is copied into the reply message, wherein the reply message is published to each of a plurality of message queues, and wherein the reply message is to be received by the computing device from any one of the plurality of replicated message queues; connecting to a second one of the plurality of second messaging manager systems; specifying the unique message identifier of the request message to receive the reply message; receiving the reply message from one of the plurality of message queues. 10. The non-transitory computer-readable storage medium of claim 9 , wherein the computing device disconnects from the first one of the plurality of second messaging manager system when the connection fails between the computing device and the first one of the plurality of second messaging manager systems. 11. The non-transitory computer-readable storage medium of claim 9 , wherein the first messaging manager system determines that the reply message is consumed by the computing device via a first replicated message queue of the plurality of replicated message queues, and sends a notification message to the plurality of replicated messages queues, other than the first replicated message queue, wherein the reply message is deleted from each of the plurality of replicated message queues based on receiving the notification message. 12. The non-transitory computer-readable storage medium of claim 9 , wherein the request message is created with a reply-to destination as a replicated queue and the operations further comprise saving the unique message identifier of the request message. 13. The non-transitory computer-readable storage medium of claim 9 , wherein before creating the request message, the computing device is workload balanced to the first one a of plurality of second messaging manager systems.

Assignees

Inventors

Classifications

  • Message adaptation to terminal or network requirements · CPC title

  • Real-time or near real-time messaging, e.g. instant messaging [IM] · CPC title

  • H04L51/34Primary

    Electricity · mapped topic

  • for tracking messages · CPC title

  • H04L51/214Primary

    using selective forwarding · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9769110B2 cover?
In response to receipt of a request message from a requester, a reply message is created. The reply message includes a message identifier of the request message copied from the received request message. The reply message is published to each of a group of replicated message queues. The reply message is identifiable by the requester using the copied message identifier of the request message on a…
Who is the assignee on this patent?
Snap Inc
What technology area does this patent fall under?
Primary CPC classification H04L51/34. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Sep 19 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 3 related publications on this page (citations in our corpus or others sharing the same primary CPC).