# US 2004/0205124 A1 · Availability and scalability in a messaging system in a manner transparent to the application

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

- Number: US 2004/0205124 A1
- Document ID: US20040205124A1
- Status: Published application
- Kind: A1
- Application number: 10/402,052
- Filed: 2003-03-27
- Published: 2004-10-14
- Earliest claimed: 2003-03-27
- Assignees: Microsoft Corporation
- Inventors: Rodney T. Limprecht; Richard D. Hill; David E. Langworthy; Hany Essam Ramadan; Shy Cohen
- Web page: https://patentgrep.com/patent/US20040205124A1

## CPC

- H04L 47/2433: {Allocation of priorities to traffic types}
- G06F 9/546: {Message passing systems or structures, e.g. queues}
- H04L 47/10: Flow control; Congestion control
- H04L 47/125: by balancing the load, e.g. traffic engineering
- H04L 47/30: in combination with information about buffer occupancy at either end or at transit nodes
- H04L 51/214: using selective forwarding
- H04L 69/329: in the application layer [OSI layer 7]
- H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066)
- H04L 67/62: Establishing a time schedule for servicing the requests
- 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

Methods, systems, and computer program products that provide for a runtime messaging infrastructure, which abstracts send and receive operations for exchanging messages with partner endpoint. The messaging infrastructure improves availability and scalability of a message application by improving on the availability and scalability of the underlying message transports. In particular, availability and scalability are improved by linking the message application at runtime with any number of the message transports, without the message application specifying a transport at development time. The message infrastructure receives instructions from the message application specifying end-to-end delivery assurances. The infrastructure uses transports in order to fulfill the specified delivery assurance, and creates a link between the message application and transports for use in exchanging messages. Session state storage can be maintained in a pluggable store, which could be, for example, a durable database store or an application memory store.

## Claims

### Claim 1

In a runtime messaging infrastructure that abstracts send and receive operations for exchanging messages with a partner endpoint over one or more available message transports, a method of improving availability and scalability of a messaging application by selecting at least one of the one or more message transports to link with the messaging application at runtime, the method comprising acts of:
receiving one or more instructions from the messaging application that specify one or more end-to-end message delivery assurances to be used in selecting at least one suitable message transport at runtime, without the messaging application specifying the at least one suitable message transport at development time, wherein the one or more end-to-end message delivery assurances comprise at least one of the following: at least once message delivery, at most once message delivery, in order sent message delivery, and session time to live;
selecting the at least one suitable message transport from the one or more available message transports in order to fulfill the one or more end-to-end message delivery assurances specified in the one or more instructions received from the messaging application; and
creating a link within the messaging infrastructure between the messaging application and the selected at least one suitable message transport for exchanging messages between the messaging application and the partner endpoint.

### Claim 2 (depends on 1)

The method of claim 1, further comprising an act of:
receiving one or more instructions from the messaging application that specify one or more local reliable message features, wherein the one or more local reliable message features comprise at least one of the following: a session state storage, a message time to live, and transacted message buffering.

### Claim 3 (depends on 2)

The method of claim 2, wherein the session state storage comprises a pluggable store.

### Claim 4 (depends on 3)

The method of claim 3, wherein the pluggable store comprises at least one of an in-memory storage, on-disk durable storage, in a daemon process storage, in non-volatile memory store, on optical storage, magnetic tape, network attached storage, or removable.

### Claim 5 (depends on 4)

The method of claim 4, wherein the pluggable store comprises a store that is remote from the messaging infrastructure.

### Claim 6 (depends on 2)

The method of claim 2, wherein the local reliable message features further comprise a maximum buffer quota that defines a maximum number of messages that will be buffered by the messaging infrastructure, and wherein when combined with a maximum message size defines a maximum number of bytes that will be buffered by the messaging infrastructure, a minimum buffer quota that defines a minimum reserved number of messages that will be buffered by the messaging infrastructure, and wherein when combined with a maximum message size defines a minimum number of bytes that will be buffered by the messaging infrastructure, a send timeout, which unblocks the send operation after the send timeout expires, wherein higher priority messages are given transmission and delivery precedence over lower priority messages, and a configurable poison message feature, wherein a number of times a message delivery is aborted is configurable to determine when the message is poison.

### Claim 7 (depends on 2)

The method of claim 2, wherein the local reliable message feature of transacted message buffering is available regardless of the durability of the session state storage.

### Claim 8 (depends on 1)

The method of claim 1, wherein the link created comprises a channel, a session state buffer, a protocol and a pluggable store.

### Claim 9 (depends on 8)

The method of claim 8, wherein the one or more specified end-to-end delivery assurances comprise at least once message delivery, wherein the protocol periodically sends a copy of a previously sent message to the partner endpoint after a retry interval until an acknowledge is received.

### Claim 10 (depends on 9)

The method of claim 9, wherein the one or more specified end-to-end delivery assurance further comprise a session time-to-live, wherein if an acknowledge is not received within a specified session time-to-live, no further retries are done and n error indication is given to the messaging application.

### Claim 11 (depends on 9)

The method of claim 9, further comprising the acts of:
receiving a local reliable message feature of a message time-to-live, wherein if an acknowledge is not received within a specified message time-to-live, no further retries are done and an error indication is give to the messaging application.

### Claim 12 (depends on 9)

The method of claim 9, wherein the retry interval is adjusted by a back-off interval after successive retry intervals.

### Claim 13 (depends on 8)

The method of claim 8, wherein state for the channel, session state buffers, and protocol are maintained in the pluggable store.

### Claim 14 (depends on 1)

The method of claim 1, wherein the at least one suitable message transport comprises at least one of the following transports: TCP/IP, UDP, HTTP, RPC and SMTP.

### Claim 15 (depends on 1)

The method of claim 1, wherein the exchanging of messages is defined by a plurality of message exchange patterns comprising at least one of one-way messaging, request/response messaging, and full duplex messaging.

### Claim 16

In a runtime messaging infrastructure that abstracts send and receive operations for exchanging messages with a partner endpoint over one or more available message transports, a computer program product comprising one or more computer readable media carrying computer executable instructions that implement a method of improving availability and scalability of a messaging application by selecting at least one of the one or more message transports to link with the messaging application at runtime, the method comprising acts of:
receiving one or more instructions from the messaging application that specify one or more end-to-end message delivery assurances to be used in selecting at least one suitable message transport at runtime, without the messaging application specifying the at least one suitable message transport at development time, wherein the one or more end-to-end message delivery assurances comprise at least one of the following: at least once message delivery, at most once message delivery, in order sent message delivery, and session time to live;
selecting the at least one suitable message transport from the one or more available message transports in order to fulfill the one or more end-to-end message delivery assurances specified in the one or more instructions received from the messaging application; and
creating a link within the messaging infrastructure between the messaging application and the selected at least one suitable message transport for exchanging messages between the messaging application and the partner endpoint.

### Claim 17 (depends on 16)

The computer program product of claim 16, the method further comprising an act of:
receiving one or more instructions from the messaging application that specify one or more local reliable message features, wherein the one or more local reliable message features comprise at least one of the following: a session state storage, a message time to live, and transacted message buffering.

### Claim 18 (depends on 17)

The computer program product of claim 17, wherein the session state storage comprises a pluggable store.

### Claim 19 (depends on 17)

The computer program product of claim 17, wherein the local reliable message features further comprise a maximum buffer quota that defines a maximum number of messages that will be buffered by the messaging infrastructure, and wherein when combined with a maximum message size defines a maximum number of bytes that will be buffered by the messaging infrastructure, a minimum buffer quota that defines a minimum reserved number of messages that will be buffered by the messaging infrastructure, and wherein when combined with a maximum message size defines a minimum number of bytes that will be buffered by the messaging infrastructure, a send timeout, which unblocks the send operation after the send timeout expires, wherein higher priority messages are given transmission and delivery precedence over lower priority messages, and a configurable poison message feature, wherein a number of times a message delivery is aborted is configurable to determine when the message is poison.

### Claim 20 (depends on 19)

The computer program product of claim 19, wherein the send timeout allows the send operation only if the buffer quota indicates space is available before a predetermined timeout period elapses.

### Claim 21 (depends on 17)

The computer program product of claim 17, wherein the local reliable message feature of a transacted message buffer is available regardless of the durability of the session state storage.

### Claim 22 (depends on 16)

The computer program product of claim 16, wherein the link created comprises a channel, a session state buffer, a protocol and a pluggable store.

### Claim 23 (depends on 22)

The computer program product of claim 22, wherein the protocol copies a received message into a receive buffer.

### Claim 24 (depends on 23)

The computer program product of claim 23, wherein the protocol records a next expected message sequence number.

### Claim 25 (depends on 23)

The computer program product of claim 23, wherein if a received message is a duplicate of a previously received message based on a state maintained by a session endpoint, then the duplicate message is discarded.

### Claim 26 (depends on 22)

The computer program product of claim 22, wherein the one or more specified end-to-end delivery assurances comprise at least once message delivery, wherein the protocol periodically sends a copy of a previously sent message to the partner endpoint after a retry interval until an acknowledge is received.

### Claim 27 (depends on 26)

The method of claim 26, wherein the one or more specified end-to-end delivery assurance further comprise a session time-to-live, wherein if an acknowledge is not received within a specified session time-to-live, no further retries are done and n error indication is given to the messaging application.

### Claim 28 (depends on 26)

The method of claim 26, further comprising the acts of:
receiving a local reliable message feature of a message time-to-live, wherein if an acknowledge is not received within a specified message time-to-live, no further retries are done and an error indication is give to the messaging application.

### Claim 29 (depends on 16)

The computer program product of claim 16, the method further comprising an act of:
scheduling transmission or delivery of at least one message of a sequence of messages to the partner endpoint.

### Claim 30 (depends on 29)

The computer program product of claim 29, wherein the scheduling is based on at least one of connectivity, load balancing, message priority, and use of a lower cost transport.

### Claim 31 (depends on 22)

The computer program product of claim 22, wherein state for the channel, session state buffers, and protocol are maintained in the pluggable store.

### Claim 32

In a runtime messaging infrastructure that abstracts send and receive operations for exchanging messages with a partner endpoint over one or more message transports, a method of improving availability and scalability of a messaging application by selecting at least one of the one or more message transports to link with the messaging application at runtime, the method comprising steps for:
determining at runtime at least one appropriate transport, without the messaging application specifying the at least one appropriate transport at development time, from among the one or more transports, that meets one or more end-to-end delivery assurances specified by the messaging application, wherein the one or more end-to-end transport assurances comprise at least one of: at least once delivery, at most once delivery, in-order delivery and session time to live; and
linking the messaging application and the determined at least one appropriate transport in order to exchange messages between the messaging application and the partner endpoint.

### Claim 33 (depends on 32)

The method of claim 32, further comprising the step for:
implementing one or more local reliable message features, wherein the one or more local reliable message features comprise at least one of: session state storage, a message time to live, and a transacted message buffering.

### Claim 34 (depends on 33)

The method of claim 33, wherein the session state storage is maintained in a pluggable store that comprises at least one of a daemon process store, a durable database store, and an application store.

### Claim 35 (depends on 33)

The method of claim 33, wherein the local reliable message feature further comprises a buffer quota, which defines a maximum number of messages that will be buffered by the messaging infrastructure, a send timeout, which unblocks the send operation after the send timeout expires, a priority option, wherein higher priority messages are transmitted before lower priority messages, and a configurable poison message feature, wherein a number of times a message delivery is aborted is configurable to determine when the message is poison.

### Claim 36 (depends on 33)

The method of claim 33, wherein the local reliable message feature of a transaction support is available regardless of the durability of the session state storage.

### Claim 37 (depends on 32)

The method of claim 32, wherein the messaging application and the determined at least one appropriate transport are linked by a channel, a session state buffer, a protocol and a pluggable store, within the messaging infrastructure.

### Claim 38 (depends on 37)

The method of claim 37, wherein the channel is an application programming interface that provides an abstraction for sending and receiving messages.

### Claim 39 (depends on 38)

The method of claim 38, wherein the session state buffers comprises a send buffer and uniquely stamps a message with a monotonically increasing message sequence number.

### Claim 40 (depends on 38)

The method of claim 38, wherein the session state buffers comprises a receive buffer that retains messages until delivered to the application.

### Claim 41 (depends on 37)

The method of claim 37, wherein the one or more specified end-to-end delivery assurance comprise at least once message delivery and session time-to-live, wherein during the session time-to-live the protocol periodically sends a copy of a previously sent message to the partner endpoint after a retry interval until an acknowledge message is received.

### Claim 42 (depends on 37)

The method of claim 37, wherein the messaging infrastructure provides at least one of session or message fault determination and handling.

### Claim 43 (depends on 42)

The method of claim 42, wherein the message fault handling comprises at least one of a notification of fault to a operating code, notification of fault to the messaging application, notification of the fault to one or more pluggable fault handlers, and notification of the fault to a human operator.

### Claim 44 (depends on 43)

The method of claim 43, wherein the survivable faults comprise corrupt messages, lost messages, duplicated messages, delayed messages, reordered messages, transport failures, network failures, process failures system failures.

### Claim 45 (depends on 42)

The method of claim 42, wherein the messaging infrastructure is notified that the fault was fixed and retries an operation that was faulted.

### Claim 46 (depends on 37)

The method of claim 37, wherein state for the channel, session state buffers, and protocol are maintained in the pluggable store.

### Claim 47

In a runtime messaging infrastructure that abstracts send and receive operations for exchanging messages with a partner endpoint over one or more transports, a computer program product comprising one or more computer readable media carrying computer executable instructions that implement a method of improving availability and scalability of a messaging application by selecting at least one of the one or more message transports to link with the messaging application at runtime, the method comprising steps for:
determining at runtime at least one appropriate transport, without the messaging application specifying the at least one appropriate transport at development time, from among the one or more transports, that meets one or more end-to-end delivery assurances specified by the messaging application, wherein the one or more end-to-end transport assurances comprise at least one of: at least once delivery, at most once delivery, in-order delivery and session time to live; and
linking the messaging application and the determined at least one appropriate transport in order to exchange messages between the messaging application and the partner endpoint.

### Claim 48 (depends on 47)

The method of claim 47, further comprising the step for:
implementing one or more local reliable message features, wherein the one or more local reliable message features comprise at least one of: session state storage, a message time to live, and a transacted message buffering.

### Claim 49 (depends on 50)

The computer program product of claim 50, wherein the session state storage is maintained in a pluggable store that comprises at least one of a daemon process store, a durable database store, and an application store.

### Claim 50 (depends on 50)

The computer program product of claim 50, wherein the local reliable message features further comprise a buffer quota, which defines a maximum number of messages that will be buffered by the messaging infrastructure, a send timeout, which unblocks the send operation after the send timeout expires, a priority option, wherein higher priority messages are transmitted before lower priority messages, and a configurable poison message feature, wherein a number of times a message delivery is aborted is configurable to determine when the message is poison.

### Claim 51 (depends on 50)

The computer program product of claim 50, wherein the local reliable message feature of a transacted message buffering is available regardless of the durability of the session state storage.

### Claim 52 (depends on 47)

The computer program product of claim 47, wherein the messaging application and the determined at least one appropriate transport are linked by a channel, a session state buffer, a protocol and a pluggable store, within the messaging infrastructure.

### Claim 53 (depends on 52)

The computer program product of claim 52, wherein the session state buffer captures messages from the messaging application, delivers messages to the messaging application, and maintains state information about messages sent and received.

### Claim 54 (depends on 53)

The computer program product of claim 53, wherein the state information comprises at least one of a session identifier, the one or more specified end-to-end transport assurances, and a partner endpoint address.

### Claim 55 (depends on 53)

The computer program product of claim 53, wherein the state information comprises at least one of a transmission sequence number and acknowledgement state information.

### Claim 56 (depends on 53)

The computer program product of claim 53, wherein the state information comprises at least one of a configurable time to live send, timeout and where information is stored.

### Claim 57 (depends on 52)

The computer program product of claim 52, wherein the protocol performs endpoint resolution to identify the partner endpoint.

### Claim 58 (depends on 57)

The computer program product of claim 57, wherein the protocol initiates endpoint resolution with an intermediary for directing messages to a node in at least one of an application farm or a partition within an application farm.

### Claim 59 (depends on 52)

The computer program product of claim 52, wherein the one or more specified end-to-end delivery assurance comprise at least once message delivery and session time-to-live, wherein during the session time-to-live the protocol periodically sends a copy of a previously sent message to the partner endpoint after a retry interval until an acknowledge message is received.

### Claim 60 (depends on 52)

The computer program product of claim 52, wherein state for the channel, session state buffers, and protocol are maintained in the pluggable store.

### Claim 61

For a runtime messaging infrastructure that abstracts session state storage and send and receive operations for exchanging messages with a partner endpoint over one or more message transports, a computer program product comprising one or more computer readable media carrying computer executable instructions that implement a method of improving availability and scalability of a messaging application by selecting at least one of the one or more message transports to link with the messaging application at runtime, the method comprising acts of:
receiving one or more instructions from the messaging application that specify session state storage, wherein the session state is maintained in a pluggable store comprising at least one of a daemon process store, a durable database store, and an application store;
receiving one or more instructions from the messaging application that specify one or more end-to-end delivery assurances to be used in selecting at least one suitable message transport at runtime, without the messaging application specifying the at least one suitable message transport at development time, wherein the one or more end-to-end delivery assurance comprise at least one of the following: at least once message delivery, at most once message delivery, in order sent message delivery, and session time to live;
selecting at least one suitable message transport from the one or more available message transports in order to fulfill the one or more end-to-end message delivery assurances specified in the instructions received from the messaging application; and
creating a link within the messaging infrastructure between the messaging application and the selected at least one transport for use in exchanging messages between the messaging application and the partner endpoint.

### Claim 62 (depends on 61)

The computer program product of claim 61, the method further comprising an act of receiving one or more local reliable message features comprising at least one of the following: an message of time to live, a transacted message buffering, a buffer quota, which defines a maximum number of messages that will be buffered by the messaging infrastructure, a send timeout, which unblocks the send operation after the send timeout expires, a priority option, wherein higher priority messages are transmitted before lower priority messages, and a configurable poison message feature, wherein a number of times a message delivery is aborted is configurable to determine when the message is poison.

### Claim 63 (depends on 61)

The computer program product of claim 61, wherein the link created comprises a channel, a session state buffer, a protocol, and the pluggable store.

### Claim 64 (depends on 63)

The computer program product of claim 63, wherein the one or more specified end-to-end delivery assurance comprise at least once message delivery and session time-to-live, wherein during the session time-to-live the protocol periodically sends a copy of a previously sent message to the partner endpoint after a retry interval until an acknowledge message is received.

### Claim 65 (depends on 64)

The computer program product of claim 64, wherein the retry interval is adjusted by a back-off interval after successive retry intervals.

### Claim 66 (depends on 61)

The computer program product of claim 61, the method further comprising an act of scheduling transfer of at least one message of a sequence of messages to the partner endpoint.

### Claim 67 (depends on 66)

The computer program product of claim 66, wherein the scheduling is based on at least one of intermittent connectivity, load balancing, message priority, and use of a lower cost transport.

### Claim 68 (depends on 63)

The computer program product of claim 63, wherein state for the channel, session state buffers, and protocol are maintained in the pluggable store.

### Claim 69 (depends on 61)

The computer program product of claim 61, wherein the exchanging of messages is defined by a plurality of message exchange patterns comprising at least one of one-way messaging, request/response messaging, and full duplex messaging.
