IP Library Granted Patent US 9,407,671
Granted Patent B2
US 9,407,671 · App. 13/971,725 · Granted Aug 2, 2016

Acknowledgement message monitoring

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,407,671
App. No.
13/971,725
Granted
Aug 2, 2016
Kind
B2
Abstract

The invention relates to a system and method for monitoring a handshaking exchange between a call initiator and a call recipient to determine if handshaking has failed, to avoid repeated failed calls between the call initiator and the call recipient.

Claims (46)

1. A method for monitoring the set-up of a communication link, the method comprising:

a call initiator sending a call initialisation message to a recipient;

the recipient sending a response message in response to the call initialisation message; and

the call initiator sending an acknowledgement message to the recipient in response to the response message, the method further comprising:

the recipient sending one or more further response messages if no acknowledgement message is received;

the call initiator sending an acknowledgement message to the recipient in response to each of said further response messages; and

determining that a fault condition exists after the call initiator receives a predetermined number of further response messages.

2. A method according to claim 1 , further comprising the recipient sending each further response message after a predetermined delay, if no acknowledgement message is received.

3. A method according to claim 1 , wherein the recipient stops sending said further response messages after a timeout period has elapsed.

4. A method according to claim 1 , wherein the response message includes an identifier associated with the IP address of the recipient and the call initiator includes a cache for storing associations between IP addresses and identifiers, and wherein upon the identification of a fault condition, the call initiator determines the IP address associated with the identifier included in the further response message to be invalid.

5. A method according to claim 4 , wherein the call initiator clears the invalid IP address associated with the identifier.

6. A method according to claim 4 , wherein the call initiator performs a lookup to identify an IP address associated with an address identifier if said cache has no valid IP address associated with an identifier.

7. A method according to claim 1 , wherein said call initialisation message is a SIP “INVITE” message, said response message is a SIP “200 OK” message and said acknowledgement message is a SIP “ACK” message.

8. A method of controlling a call initiator in a communication system, the method comprising:

sending a call initialisation message to a recipient;

receiving a response message from said recipient in response to the call initialisation message; and

sending an acknowledgement message to said recipient in response to the receipt of a response message, the method further comprising:

sending a further acknowledgement message to the recipient in response to each further response messages received from said recipient; and

determining that a fault condition exists after the call initiator receives a predetermined number of further response messages.

9. A method according to claim 8 , wherein the response message includes an identifier associated with the IP address of the recipient and the method further includes:

maintaining a cache for storing associations between IP addresses and identifiers, and

upon the identification of a fault condition, determining that the IP address associated with the identifier included in the further response message to be invalid.

10. A method according to claim 9 , further comprising clearing the invalid IP address associated with the identifier from the cache.

11. A method according to claim 9 , further comprising performing a lookup to identify an IP address associated with said identifier if said cache has no valid IP address associated with the identifier.

12. A method according to claim 8 , wherein said call initialisation message is a SIP “INVITE” message, said response message is a SIP “200 OK” message and said acknowledgement message is a SIP “ACK” message.

13. A system for controlling a set-up of a communication link, the system comprising:

a call initiator; and

a recipient, wherein

the call initiator is arranged to send a call initialisation message for reception by the recipient;

the recipient is arranged for sending a response message in response to the call initialisation message;

the call initiator is arranged for sending an acknowledgement message to the recipient in response to the response message,

the recipient is arranged for sending one or more further response messages if no acknowledgement message is received from the recipient;

the call initiator is arranged for sending an acknowledgement message to the recipient in response to each of said further response messages; and

the call initiator is further arranged for determining that a fault condition exists after the call initiator receives a predetermined number of further response messages.

14. A system according to claim 13 , wherein a received response message includes an identifier associated with the IP address of the recipient, and said call initiator comprises a cache to store associations between IP addresses and said identifier, and wherein, upon determining that a fault condition exists, the call initiator determines the IP address associated with the identifier included in the further response message to be invalid.

15. A system according to claim 14 , further arranged to perform a lookup to identify an IP address associated with said identifier if said cache has no valid IP address associated with the identifier and store said IP address in said cache.

16. A system according to claim 14 , wherein said call initiator is further arranged to clear the invalid IP address associated with the associated identifier from said cache.

17. A communication device for communicating with a recipient device comprising:

a call initiator arranged to send a call initialisation message to a recipient; and

reception means for receiving response messages from a recipient, wherein

the call initiator is arranged to send an acknowledgement message when a response message is received by said reception means,

the call initiator is further arranged to send further acknowledgement messages to the recipient in response to receipt of further response messages from the recipient; and

the communication device determines that a fault exists after the reception means receives a predetermined number of further response messages, sent by the recipient when it does not receive an acknowledgement message from the call initiator.

18. A communication device according to claim 17 , wherein a received response message includes an identifier associated with the IP address of the recipient, and said call initiator comprises a cache to store associations between IP addresses and said identifier, and wherein, upon determining that a fault exists, the call initiator determines the IP address associated with the identifier included in the further response message to be invalid.

19. A communication device according to claim 17 , further arranged to perform a lookup to identify an IP address associated with said identifier if said cache has no valid IP address associated with the identifier and store said IP address in said cache.

20. A communication device according to claim 17 , wherein said call initiator is further arranged to clear the invalid IP address associated with the associated identifier from said cache.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2026
From: MICROSOFT TECHNOLOGY LICENSING, LLC
To: ALIANZA, INC.
Reel/Frame 075645/0892 →
CHANGE OF NAME Recorded May 13, 2026
From: ALIANZA, INC.
To: ALIANZA, LLC
Reel/Frame 075646/0037 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 13, 2026
From: METASWITCH NETWORKS LTD.
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 075578/0155 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 3, 2013
From: SCOTT, PHILIP ANTHONY; SUGARMAN, RICHARD DAVID
To: METASWITCH NETWORKS LIMITED
Reel/Frame 031341/0992 →