IP Library Granted Patent US 9,015,349
Granted Patent B2
US 9,015,349 · App. 13/684,156 · Granted Apr 21, 2015

Crisscross cancellation protocol

Inventors: Atul Adya (Redmond, WA); Alastair Wolman (Seattle, WA); John D Dunagan (Bellevue, WA)
Assignee: Microsoft Technology Licensing, LLC
H04L65/1003H04L67/14
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,015,349
App. No.
13/684,156
Granted
Apr 21, 2015
Kind
B2
Abstract

Technologies, systems, and methods for ordered message delivery that avoid message races or crisscrosses between communicating nodes. For example, if Node A sends message 3 towards Node B and, shortly thereafter, Node B sends message X to Node A. Node A would like to know whether or not message X reflects Node B's state after receiving message 3. If Node B received message 3 prior to sending message X, then proper state may be maintained between the nodes. But if messages 3 and X crisscrossed, or if message 3 was never properly received by Node B, then the state between the nodes may be corrupt. Technologies, systems, and methods are provided to avoid such corruption.

Claims (20)

1. A method performed on a computing device, the method comprising sending a message that comprises a set of variables including a nonce state variable configured for identifying a current session of the computing device, a counter state variable configured for indicating a last message sent by the computing device to a remote computing device, a remote nonce state variable configured for identifying a current session of the remote computing device as known by the computing device, and a remote counter state variable configured for indicating a last valid message received by the computing device from the remote computing device, the set of variables configured for use in detecting a message race condition.

2. The method of claim 1 where the nonce state variable is further configured to uniquely identify the current session.

3. The method of claim 1 where the counter state variable is further configured to include a monotonically increasing value that corresponds to the last sent message.

4. The method of claim 1 where a value of the remote nonce state variable indicates a last valid message received from the remote computing device, and where the value is initialized to zero.

5. The method of claim 1 where a value of the remote counter state variable indicates a last valid message received from the remote computing device.

6. The method of claim 1 where the sent message comprises a header that includes the nonce state variable, the counter state variable, the remote nonce state variable, and the remote counter state variable.

7. The method of claim 1 where the last valid message received by the computing device from the remote computing device comprises a header that includes another nonce state variable, another counter state variable, another remote nonce state variable, and another the remote counter state variable.

8. At least one computer-readable storage device comprising computer-executable instructions that, when executed by a computing device, cause the computing device to perform actions for detecting crisscrossed messages, the actions comprising sending a message that comprises a set of variables including a nonce state variable configured for identifying a current session of the computing device, a counter state variable configured for indicating a last message sent by the computing device to a remote computing device, a remote nonce state variable configured for identifying a current session of the remote computing device as known by the computing device, and a remote counter state variable configured for indicating a last valid message received by the computing device from the remote computing device, the set of variables configured for use in detecting a message race condition.

9. The at least one computer-readable storage device of claim 8 where the nonce state variable is further configured to uniquely identify the current session.

10. The at least one computer-readable storage device of claim 8 where the counter state variable is further configured to include a monotonically increasing value that corresponds to the last sent message.

11. The at least one computer-readable storage device of claim 8 where a value of the remote nonce state variable indicates a last valid message received from the remote computing device.

12. The at least one computer-readable storage device of claim 8 where a value of the remote counter state variable indicates a last valid message received from the remote computing device.

13. The at least one computer-readable storage device of claim 8 where the sent message comprises a header that includes the nonce state variable, the counter state variable, the remote nonce state variable, and the remote counter state variable.

14. The at least one computer-readable storage device of claim 8 where the last valid message received by the computing device from the remote computing device comprises a header that includes another nonce state.

15. A computing device and at least one program module together configured for sending a message that comprises a set of variables including a nonce state variable configured for identifying a current session of the computing device, a counter state variable configured for indicating a last message sent by the computing device to a remote computing device, a remote nonce state variable configured for identifying a current session of the remote computing device as known by the computing device, and a remote counter state variable configured for indicating a last valid message received by the computing device from the remote computing device, the set of variables configured for use in detecting a message race condition.

16. The computing device and at least one program module of claim 15 where the nonce state variable is further configured to uniquely identify the current session.

17. The computing device and at least one program module of claim 15 where the counter state variable is further configured to include a monotonically increasing value that corresponds to the last sent message.

18. The computing device and at least one program module of claim 15 where a value of the remote nonce state variable indicates a last valid message received from the remote computing device.

19. The computing device and at least one program module of claim 15 where a value of the remote counter state variable indicates a last valid message received from the remote computing device.

20. The computing device and at least one program module of claim 15 where the sent message comprises a header that includes the nonce state variable, the counter state variable, the remote nonce state variable, and the remote counter state variable.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 27, 2015
From: ADYA, ATUL; WOLMAN, ALASTAIR; DUNAGAN, JOHN D.
To: MICROSOFT CORPORATION
Reel/Frame 036895/0518 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 27, 2015
From: MICROSOFT CORPORATION
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 036895/0570 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 9, 2014
From: MICROSOFT CORPORATION
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 034544/0541 →
Continuity (3)
Continuation 12824092 · Jun 25, 2010
Continuation 11858140 · Sep 20, 2007
Related Publication 20130080632A1 · Mar 28, 2013