IP Library Granted Patent US 9,325,599
Granted Patent B2
US 9,325,599 · App. 13/925,527 · Granted Apr 26, 2016

Methods for providing a status to devices in a distributed system

Inventors: Nam Do (Pleasanton, CA); Vu Hwang (San Jose, CA)
Assignee: ShoreTel, Inc.
H04L43/10H04M3/56H04M7/006H04M2207/20
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,325,599
App. No.
13/925,527
Granted
Apr 26, 2016
Kind
B2
Abstract

A method for providing a status to a plurality of devices in a distributed VoIP system includes circulating a first status data packet between each device in the first group of devices and circulating a second status data packet between each device in the second group of devices. One device in the first group of devices participates in circulating both the first status data packet and the second status data packet, while the other devices in the first group of devices circulate only the first status data packet. One device in the second group of devices participates in circulating both the first status data packet and the second status data packet, while the other devices in the second group of devices circulate only the second status data packet.

Claims (44)

1. A method for providing a status to conference bridges in a distributed system, the status comprising a list of meetings hosted by one or more of the conference bridges, the method comprising:

at a second conference bridge:

receiving a status data packet, the status data packet sent from a first conference bridge to the second conference bridge and including the status of the first conference bridge, the status of the first conference bridge including a list of meetings hosted by the first conference bridge;

saving the status of the first conference bridge to a memory of the second conference bridge;

updating the status data packet with a status of the second conference bridge, the status of the second conference bridge including a list of meetings hosted by the second conference bridge;

obtaining a list of the conference bridges in the distributed system, the list providing a sequence for circulating the status data packet between the conference bridges, the sequence determined by:

determining a network lag between each of the conference bridges; and

determining the sequence by using the network lag to minimize a number of higher network lag communications between the conference bridges;

sending the status data packet including the status of the first conference bridge and the status of the second conference bridge from the second conference bridge to a next conference bridge in the sequence.

2. The method of claim 1 further comprising sending an acknowledgement of receipt of the status data packet from the second conference bridge to the first conference bridge.

3. The method of claim 1 further comprising receiving an acknowledgement of receipt of the status data packet from the next conference bridge in the sequence.

4. The method of claim 1 wherein the status data packet includes an ID of the first conference bridge and a time associated with receiving the status data packet at the second conference bridge.

5. The method of claim 1 wherein the distributed system is a distributed VoIP system.

6. The method of claim 1 wherein the next conference bridge is a last conference bridge in the sequence, and the last conference bridge sends the status data packet to the first conference bridge, the first conference bridge being a first conference bridge in the sequence.

7. The method of claim 1 further comprising incrementing a circulation counter after receiving the status data packet.

8. The method of claim 1 wherein the status data packet includes the list of the conference bridges in the distributed system.

9. The method of claim 1 further comprising:

at the second conference bridge:

waiting a period of time;

determining that an acknowledgement of receipt of the status data packet is not received from the next conference bridge during the period of time; and

sending the status data packet to a following conference bridge in the sequence, the following conference bridge being after the next conference bridge in the sequence.

10. The method of claim 9 wherein the period of time is determined based at least in part on a time duration required for the next conference bridge to receive the status data packet and send an acknowledgement of receipt of the status data packet.

11. The method of claim 1 further comprising:

at the second conference bridge:

waiting a period of time after receiving the status data packet and before sending the status data packet to the next conference bridge, wherein the period of time is greater than a time duration required to save the status of the first conference bridge to the memory and obtain the list of the plurality of conference bridges in the distributed system.

12. The method of claim 11 wherein the period of time is based at least in part on a number of the conference bridges.

13. A method for providing a status to a plurality of conference bridges in a distributed VoIP system, the status comprising a list of meetings hosted by one or more of the plurality of conference bridges, the plurality of conference bridges comprising at least a first group of conference bridges and a second group of conference bridges, the method comprising:

circulating a first status data packet between each conference bridge in the first group, the first status data packet comprising the status of each conference bridge in the first group including a list of meetings hosted by conference bridges in the first group;

circulating a second status data packet between each conference bridge in the second group, the second status data packet comprising the status of each conference bridge in the second group including a list of meetings hosted by conference bridges in the second group;

wherein one conference bridge in the first group participates in circulating both the first status data packet and the second status data packet, while the other conference bridges in the first group circulate only the first status data packet; and

wherein one conference bridge in the second group participates in circulating both the first status data packet and the second status data packet, while the other conference bridges in the second group circulate only the second status data packet; and

wherein the one conference bridge in the first group that participates in circulating both the first status data packet and the second status data packet updates the first status data packet with the status of each of the conference bridges in the second group and updates the second status data packet with the status of each of the conference bridges in the first group.

14. The method of claim 13 wherein the one conference bridge in the first group that participates in circulating both the first status data packet and the second status data packet and the one conference bridge in the second group that participates in circulating both the first status data packet and the second status data packet are the same conference bridge.

15. The method of claim 13 wherein the one conference bridge in the first group that participates in circulating both the first status data packet and the second status data packet is selected based on a device identification number of the one conference bridge compared to device identification numbers of the other conference bridges in the first group.

16. The method of claim 13 wherein each of the conference bridges in the first group has a network lag that on average is different from that of each of the conference bridges in the second group.

17. The method of claim 13 wherein the plurality of conference bridges include a third group of conference bridges, the method further comprising:

circulating a third status data packet between each of the conference bridges in the third group;

wherein one conference bridge in the third group participates in circulating both the third status data packet and the second status data packet, while the other conference bridges in the third group circulate only the third status data packet.

18. A non-transitory computer readable medium including computer program code for providing a status to a plurality of conference bridges in a distributed VoIP system, the status comprising a list of meetings hosted by one or more of the plurality of conference bridges, the plurality of conference bridges comprising at least a first group of conference bridges and a second group of conference bridges, the computer readable medium comprising:

code for circulating a first status data packet between each of the conference bridges in the first group, the first status data packet comprising the status of each conference bridge in the first group including a list of meetings hosted conference bridges in the first group;

code for circulating a second status data packet between each of the conference bridges in the second group, the second status data packet comprising the status of each conference bridge in the second group including a list of meetings hosted conference bridges in the second group;

wherein one conference bridge in the first group participates in circulating both the first status data packet and the second status data packet, while the other conference bridges in the first group circulate only the first status data packet;

wherein one conference bridge in the second group participates in circulating both the first status data packet and the second status data packet, while the other conference bridges in the second group circulate only the second status data packet; and

wherein the one conference bridge in the first group that participates in circulating both the first status data packet and the second status data packet updates the first status data packet with the status of each of the conference bridges in the second group and updates the second status data packet with the status of each of the conference bridges in the first group.

Assignments (23)
SECURITY INTEREST Recorded Jun 30, 2025
From: MLN US HOLDCO LLC; MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: U.S. PCI SERVICES, LLC
Reel/Frame 071758/0843 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: ACQUIOM AGENCY SERVICES LLC
To: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071730/0632 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MITEL (DELAWARE), INC.; MITEL COMMUNICATIONS, INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071712/0821 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: ANKURA TRUST COMPANY, LLC
To: MITEL (DELAWARE), INC.; MITEL COMMUNICATIONS, INC.; MITEL CLOUD SERVICES, INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071722/0721 →
SECURITY INTEREST Recorded Jun 20, 2025
From: MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 071676/0815 →
SECURITY INTEREST Recorded Mar 12, 2025
From: MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 070689/0857 →
NOTICE OF SUCCCESSION OF AGENCY - 3L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 070006/0268 →
NOTICE OF SUCCCESSION OF AGENCY - PL Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 069895/0755 →
NOTICE OF SUCCESSION OF AGENCY - 5L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ANKURA TRUST COMPANY, LLC
Reel/Frame 069897/0046 →
NOTICE OF SUCCCESSION OF AGENCY - 2L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 069896/0001 →
NOTICE OF SUCCESSION OF AGENCY - 4L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ANKURA TRUST COMPANY, LLC
Reel/Frame 069896/0827 →
SECURITY INTEREST Recorded Nov 1, 2022
From: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL COMMUNICATIONS, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 061830/0760 →
SECURITY INTEREST Recorded Nov 1, 2022
From: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL COMMUNICATIONS, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 061830/0643 →
SECURITY INTEREST Recorded Nov 1, 2022
From: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL COMMUNICATIONS, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 061830/0715 →
SECURITY INTEREST Recorded Dec 13, 2018
From: MITEL NETWORKS, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047909/0814 →
SECURITY INTEREST Recorded Dec 13, 2018
From: MITEL NETWORKS, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047988/0478 →
RELEASE OF SECURITY INTEREST Recorded Dec 3, 2018
From: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
To: SHORETEL, INC.
Reel/Frame 047713/0843 →
MERGER AND CHANGE OF NAME Recorded Oct 15, 2018
From: MITEL NETWORKS, INC.; SHORETEL, INC.
To: SHORETEL, INC.
Reel/Frame 047239/0183 →
CHANGE OF NAME Recorded Oct 15, 2018
From: SHORETEL, INC.
To: MITEL NETWORKS, INC.
Reel/Frame 047239/0088 →
SECURITY INTEREST Recorded Sep 25, 2017
From: SHORETEL, INC.
To: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 043829/0711 →
RELEASE OF SECURITY INTEREST Recorded Sep 25, 2017
From: SILICON VALLEY BANK
To: SHORETEL, INC.
Reel/Frame 043993/0430 →
SECURITY INTEREST Recorded Oct 23, 2014
From: SHORETEL, INC.
To: SILICON VALLEY BANK
Reel/Frame 034038/0741 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 24, 2013
From: DO, NAM; HWANG, VU
To: SHORETEL, INC.
Reel/Frame 030674/0065 →
Continuity (3)
Continuation In Part 12975679 · Dec 22, 2010
Continuation In Part 12414238 · Mar 30, 2009
Related Publication 20130294260A1 · Nov 7, 2013