Message delivery in messaging networks

US9647972B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9647972-B2
Application numberUS-201514641113-A
CountryUS
Kind codeB2
Filing dateMar 6, 2015
Priority dateJan 25, 2008
Publication dateMay 9, 2017
Grant dateMay 9, 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 backend messaging manager system executing on one or more processors, a reply message in response to receipt of a request message from a requester via a first one of a plurality of front end messaging manager systems; copying into the reply message, by the backend messaging manager system, a unique message identifier of the request message from the received request message; publishing, by, the backend messaging manager system, the reply message to each of a plurality of replicated message queues, wherein the reply message is received by the requester on any one of the plurality of replicated message queues and wherein the reply message is identifiable by the requester using the copied unique message identifier of the request message on any one of the plurality of replicated message queues prior to being consumed by the requester, and wherein the requester receives the reply message via a second one of the plurality of front end messaging manager systems; determining that the reply message is consumed by the requester via a first replicated message queue of the plurality of replicated message queues; and sending a notification message to the plurality of the replicated message 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. 2. The method of claim 1 , where publishing the reply message to each of the plurality of replicated message queues comprises sending the reply message to each of a plurality of message managing systems in association with which the plurality of replicated message queues are defined. 3. The method of claim 1 , where the plurality of replicated message queues comprise a first plurality of replicated request message queues and a second plurality of replicated reply message queues, and further comprising: wherein the request message from the requester is received from one of the first plurality of replicated request message queues; and wherein publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of the second plurality of replicated reply message queues. 4. The method of claim 1 , where the request message further comprises a replicated reply-to message queue name identifier that specifies a plurality of replicated reply message queues, and where publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of a plurality of replicated reply message queues named as specified by the replicated reply-to message queue name identifier. 5. The method of claim 1 , where publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of a plurality of queue managers that each host one of the plurality of replicated message queues. 6. The method of claim 1 , where: the plurality of replicated message queues comprise a messaging network with a configured number of replicated message queues; and publishing the reply message to each of the plurality of replicated message queues provides redundant publication of the reply message that facilitates delivery of the reply message to the requester in an event of a failure of message managing systems that host all but one of the configured number of replicated message queues of the messaging network. 7. An apparatus for message delivery in messaging networks, comprising: a communication interface; and a processor programmed to perform operations comprising: creating a reply message, in response to receipt of a request message from a requester via a first one of a plurality of front end messaging manager systems; copying into the reply message, a message identifier of the request message from the received request message; publishing, via the communication interface, the reply message to each of a plurality of replicated message queues, wherein the reply message is received by the requester on any one of the plurality of replicated message queues and wherein the reply message is identifiable by the requester using the copied message identifier of the request message on any one of the plurality of replicated message queues prior to being consumed by the requester, and wherein the requester receives the reply message via a second one of the plurality of front end messaging manager systems; determining that the reply message is consumed by the requester via a first replicated message queue of the plurality of replicated message queues; and sending a notification message to the plurality of the replicated message 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 apparatus of claim 7 , where, publishing the reply message to each of the plurality of replicated message queues comprises sending the reply message to each of a plurality of message managing systems in association with which the plurality of replicated message queues are defined. 9. The apparatus of claim 7 , where the plurality of replicated message queues comprise a first plurality of replicated request message queues and a second plurality of replicated reply message queues, and where the operations further comprise: receiving the request message from the requester from one of the first plurality of replicated request message queues; and wherein publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of the second plurality of replicated reply message queues. 10. The apparatus of claim 7 , where the request message further comprises a replicated reply to message queue name identifier that specifies a plurality of replicated reply message queues, and where publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of a plurality of replicated reply message queues named as specified by the replicated reply-to message queue name identifier. 11. The apparatus of claim 7 , where, publishing the reply message to each of the plurality of replicated message queues comprises publishing the reply message to each of a plurality of queue managers that each host one of the plurality of replicated message queues. 12. The apparatus of claim 7 , where: the plurality of replicated message queues comprise a messaging network with a configured number of replicated message queues; and publishing the reply message to each of the plurality of replicated message queues provides redundant publication of the reply message that facilitates delivery of the reply message to the requester in an event of a failure of message managing systems that host all but one of the configured number of replicated message queues of the messaging network. 13. A non-transitory computer readable storage medium having computer readable program code embodied therewith, where the computer readable program code when executed on a computer causes the computer to perform operations comprising: creating a reply message, in response to receipt of a request message from a requester via a first one of a plurality of front end messaging manager systems; copying into the reply message, a message identifier of the request message from the received request message; publishing the reply message to each of a plurality of replicated message queues, wherein t

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

  • Buffering arrangements · CPC title

  • Electricity · mapped topic

  • Electricity · mapped topic

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 US9647972B2 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, Snap Inc
What technology area does this patent fall under?
Primary CPC classification H04L51/14. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue May 09 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 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).