# US 2022/0286423 A1 · Message Queue Architecture and Interface for a Multi-Application Platform

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0286423 A1
- Document ID: US20220286423A1
- Status: Published application
- Kind: A1
- Application number: 17/666,208
- Filed: 2022-02-07
- Published: 2022-09-08
- Earliest claimed: 2021-03-02
- Assignees: ServiceNow, Inc.
- Applicants: ServiceNow, Inc.
- Inventors: Khosrow Jian Motamedi; Nikhil Prashant Bendre; Harry Thomas Nelson; Sunil Kumar
- Web page: https://patentgrep.com/patent/US20220286423A1

## CPC

- H04L 41/02: Standardisation; Integration
- H04L 51/226: Delivery according to priorities
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- H04L 41/342: between virtual entities, e.g. orchestrators, SDN or NFV entities
- H04L 41/5022: by giving priorities, e.g. assigning classes of service
- H04L 51/214: using selective forwarding
- H04L 67/55: Push-based network services
- H04L 47/50: Queue scheduling
- H04L 51/18: Commands or executable codes
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Non-volatile memory may contain definitions of: (i) a plurality of message queue implementations respectively associated with different queue behaviors, the different queue behaviors specified by corresponding sets of modes, and (ii) an application programming interface (API) through which applications can access one or more message queues. One or more processors may be configured to: create a message queue of a particular message queue type, supported by a corresponding message queue implementation, by specifying a set of modes corresponding to a queue behavior; receive, from a producing application and by way of the API, one or more messages for the message queue; store the one or more messages in a data structure associated with the message queue; receive, from a consuming application and by way of the API, a request to read from the message queue; and provide a message from the message queue to the consuming application.

## Claims

### Claim 1

A system comprising:
non-volatile memory containing definitions of: a message producer, a message consumer, and a context specifying a plurality of instantiated queues, wherein each of the instantiated queues has a different respective set of queuing behaviors controlling its storage, directionality, or usage; and
one or more processors configured to:
receive, at the message producer and by way of a message queue application programming interface (API), a message from a first application;
determine, at the message producer, a particular queue from the instantiated queues based on the context or metadata of the message;
place, at the message producer, the message into the particular queue;
receive, at the message consumer and by way of the message queue API, a request from a second application;
identify, at the message consumer, the particular queue based on the context or the request; and
provide, at the message consumer, the message from the particular queue to the second application.

### Claim 2 (depends on 1)

The system of claim 1, wherein the message producer and the message consumer operate independently from the first application and the second application.

### Claim 3 (depends on 1)

The system of claim 1, wherein the message queue API is part of a software library that provides the first application and the second application access to the message producer and the message consumer.

### Claim 4 (depends on 1)

The system of claim 1, wherein the metadata identifies a queue name of the particular queue.

### Claim 5 (depends on 1)

The system of claim 1, wherein the metadata identifies one or more queueing behaviors of the particular queue.

### Claim 6 (depends on 1)

The system of claim 1, wherein the context of the particular queue is determined by the message.

### Claim 7 (depends on 1)

The system of claim 1, wherein the storage, the directionality, or the usage of the message is determined by the respective set of queueing behaviors of the particular queue.

### Claim 8 (depends on 1)

The system of claim 1, wherein the message includes a service header that contains one or more units of the metadata, wherein the one or more units of the metadata are not provided to the second application, and are used by the message producer or the message consumer.

### Claim 9 (depends on 8)

The system of claim 8, wherein the message also contains a body and a client header, wherein the body contains content from the first application that the message producer and the message consumer transparently provide to the second application, wherein the client header contains one or more further units of the metadata from the first application that the message producer and the message consumer transparently provide to the second application.

### Claim 10 (depends on 1)

The system of claim 1, wherein the respective set of queuing behaviors of the particular queue include a queueing behavior controlling usage of the particular queue to be either point-to-point or publish/subscribe, wherein the usage being point-to-point results in the message being removed from the particular queue when provided to the second application, and wherein the usage being publish/subscribe results in the message persisting in the particular queue after being provided to the second application.

### Claim 11 (depends on 1)

The system of claim 1, wherein the respective set of queuing behaviors of the particular queue include a queueing behavior controlling the storage of the particular queue to be either in-memory, persistent, or persistent cached, wherein the storage being in-memory results in the being stored only in volatile memory, wherein the storage being persistent results in the message being stored in the non-volatile memory, and wherein the storage being persistent cached results in the message in the particular queue being stored in the volatile memory and cached in the non-volatile memory.

### Claim 12 (depends on 1)

The system of claim 1, wherein the respective set of queuing behaviors of the particular queue include a queueing behavior controlling the directionality of the particular queue to be either unidirectional or bidirectional, wherein the directionality being unidirectional results in messages in the particular queue only flowing from the first application to the second application, and wherein the directionality being bidirectional results in some of the messages in the particular queue flowing from the first application to the second application and other messages in the particular queue flowing from the second application to the first application.

### Claim 13

A computer-implemented method comprising:
receiving, at a message producer and by way of a message queue application programming interface (API), a message from a first application, wherein non-volatile memory contains definitions of: the message producer, a message consumer, and a context specifying a plurality of instantiated queues, wherein each of the instantiated queues has a different respective set of queuing behaviors controlling its storage, directionality, or usage;
determining, at the message producer, a particular queue from the instantiated queues based on the context or metadata of the message;
placing, at the message producer, the message into the particular queue;
receiving, at the message consumer and by way of the message queue API, a request from a second application;
identifying, at the message consumer, the particular queue based on the context or the request; and
providing, at the message consumer, the message from the particular queue to the second application.

### Claim 14 (depends on 13)

The computer-implemented method of claim 13, wherein the metadata identifies a queue name of the particular queue.

### Claim 15 (depends on 13)

The computer-implemented method of claim 13, herein the message includes a service header that contains one or more units of the metadata, wherein the one or more units of the metadata are not provided to the second application, and are used by the message producer or the message consumer.

### Claim 16 (depends on 15)

The computer-implemented method of claim 15, wherein the message also contains a body and a client header, wherein the body contains content from the first application that the message producer and the message consumer transparently provide to the second application, wherein the client header contains one or more further units of the metadata from the first application that the message producer and the message consumer transparently provide to the second application.

### Claim 17 (depends on 13)

The computer-implemented method of claim 13, wherein the respective set of queuing behaviors of the particular queue include a queueing behavior controlling the usage of the particular queue to be either point-to-point or publish/subscribe, wherein the usage being point-to-point results in the message being removed from the particular queue when provided to the second application, and wherein the usage being publish/subscribe results in the message persisting in the particular queue after being provided to the second application.

### Claim 18 (depends on 13)

The computer-implemented method of claim 13, wherein the respective set of queuing behaviors of the particular queue include a queueing behavior controlling the storage of the particular queue to be either in-memory, persistent, or persistent cached, wherein the storage being in-memory results in the being stored only in volatile memory, wherein the storage being persistent results in the message being stored in the non-volatile memory, and wherein the storage being persistent cached results in the message in the particular queue being stored in the volatile memory and cached in the non-volatile memory.

### Claim 19 (depends on 13)

The computer-implemented method of claim 13, wherein the respective set of queuing behaviors of the particular queue include a queueing behavior controlling the directionality of the particular queue to be either unidirectional or bidirectional, wherein the directionality being unidirectional results in messages in the particular queue only flowing from the first application to the second application, and wherein the directionality being bidirectional results in some of the messages in the particular queue flowing from the first application to the second application and other messages in the particular queue flowing from the second application to the first application.

### Claim 20

An article of manufacture including a non-transitory computer-readable medium, having stored thereon program instructions that, upon execution by a computing system, cause the computing system to perform operations comprising:
receiving, at a message producer and by way of a message queue application programming interface (API), a message from a first application, wherein non-volatile memory contains definitions of: the message producer, a message consumer, and a context specifying a plurality of instantiated queues, wherein each of the instantiated queues has a different respective set of queuing behaviors controlling its storage, directionality, or usage;
determining, at the message producer, a particular queue from the instantiated queues based on the context or metadata of the message;
placing, at the message producer, the message into the particular queue;
receiving, at the message consumer and by way of the message queue API, a request from a second application;
identifying, at the message consumer, the particular queue based on the context or the request; and
providing, at the message consumer, the message from the particular queue to the second application.
