IP Library Granted Patent US 9,571,361
Granted Patent B1
US 9,571,361 · App. 14/066,688 · Granted Feb 14, 2017

Status reporting system

Inventor: Kenneth A. Robesky (Mountain View, CA)
Assignee: Shoretel, Inc.
H04L43/0805
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,571,361
App. No.
14/066,688
Granted
Feb 14, 2017
Kind
B1
Abstract

A supervisor entity comprises an entity status module for maintaining status of its subordinate entities and updating the supervisor entity with status updates for itself and the subordinate entities. The entity status module comprises an entity status controller for receiving a status message from a first subordinate entity, a subordinate determination module for determining a second subordinate entity that is subordinate to the first subordinate entity, a status update module for updating the status of the second subordinate entity based on the received status message from the first subordinate entity, a status reporting module for reporting the updated status of the second subordinate entity to a supervisor entity and a status storage for storing the status of the second subordinate entity.

Claims (41)

1. A computer-implemented method comprising:

determining, by an entity status controller in a first entity, an appropriate time for transmitting a status message reporting a status of the first entity to a second entity, wherein the first entity is a device subordinate to the second entity in a hierarchical network, the status of the first entity reflecting whether or not the first entity is active; and

transmitting, by an entity status reporting module in the first entity, the status message reporting the status of the first entity to the second entity, the status message including a list of identifications for active entities and a list of identifications for inactive entities, such that the second entity receives the status of the first entity and entities subordinate to the first entity in the hierarchical network,

wherein the appropriate time for transmitting the status message is a predetermined time after the first entity is initialized or a time after the status of the first entity has stabilized.

2. The method of claim 1 wherein the hierarchical network comprises at least four hierarchical levels of entities, and there is at least one hierarchical level, comprising one or more entities, subordinate to the first entity.

3. The method of claim 1 wherein the appropriate time is a configurable duration after the first entity is initialized.

4. The method of claim 1 , wherein the hierarchical network comprises at least four hierarchical levels of entities, and there are at least two hierarchical levels, each comprising one or more entities, subordinate to the first entity.

5. The method of claim 1 , further comprising:

receiving a signal from the second entity, the signal requesting the first entity to update the second entity with any status updates for entities subordinate to the first entity.

6. The method of claim 1 , further comprising:

receiving, by the entity status controller, a first set of alive messages from an entity subordinate to the first entity;

determining, by the entity status controller, that the entity status controller is no longer receiving the first set of alive messages from the entity subordinate to the first entity; and

in response to the determining, transmitting, by the entity status reporting module, a second status message to the second entity indicating the entity subordinate to the first entity as inactive.

7. The method of claim 6 , further comprising;

receiving, by the entity status controller, a second set of alive messages from the entity subordinate to the first entity;

in response to receiving the second set of alive messages from the entity subordinate to the first entity, determining, by the entity status controller, that the entity subordinate to the first entity is active; and

in response to determining that the entity subordinate to the first entity is active, transmitting, by the entity status reporting module, a third status message to the second entity indicating the entity subordinate to the first entity as active.

8. The method of claim 1 , further comprising:

determining, by the entity status controller, a change in the status of the first entity; and

upon determining the change, transmitting, by the entity status reporting module, a status message reporting a subsequent status of the first entity to the second entity.

9. The method of claim 8 , further comprising:

receiving, by the entity status controller, a signal from the second entity, the signal requesting a status update to the second entity.

10. The method of claim 8 , further comprising:

determining, by the entity status controller, that the status of the first entity has stabilized; and

in response to determining that the status of the first entity has stabilized, transmitting, by the entity status reporting module, the status message reporting the status of the first entity to the second entity.

11. An entity status reporting apparatus in a first entity for reporting a status of the first entity to a second entity, the apparatus comprising:

an entity status controller in the first entity configured to determine an appropriate time for transmitting a status message reporting the status of the first entity to the second entity, wherein the first entity is a device subordinate to the second entity in a hierarchical network, the status of the first entity reflecting whether or not the first entity is active; and

an entity status reporting module in the first entity, communicatively coupled to the entity status controller, configured to transmit the status message reporting the status of the first entity to the second entity, the status message including a list of identifications for active entities and a list of identifications of inactive entities, such that the second entity receives the status of the first entity and all entities subordinate to the first entity,

wherein the entity status controller determines the appropriate time for transmitting the status message is a predetermined time after the first entity is initialized or a time after the status of the first entity has stabilized.

12. The entity status reporting apparatus of claim 11 wherein the hierarchical network comprises at least four hierarchical levels of entities in the hierarchical network each comprising one or more entities subordinate to the first entity.

13. The entity status reporting apparatus of claim 11 wherein the first entity has stabilized after a pre-configured amount of resources are available for executing system functions.

14. The entity status reporting apparatus of claim 11 , wherein the hierarchical network comprises at least two hierarchical levels subordinate to the first entity, each level comprising one or more entities.

15. The entity status reporting apparatus of claim 11 wherein:

the entity status controller is further configured to receive a first set of alive messages from an entity subordinate to the first entity and determine that the entity status controller is no longer receiving the first set of alive messages from the entity subordinate to the first entity; and

the entity status reporting module is further configured to transmit a second status message to the second entity indicating the entity subordinate to the first entity as inactive in response to the entity status controller determining that the entity status controller is no longer receiving the first set of alive messages from the entity subordinate to the first entity.

16. The entity status reporting apparatus of claim 15 wherein:

the entity status controller is further configured to receive a second set of alive messages from the entity subordinate to the first entity and determine that the entity subordinate to the first entity is active in response to receiving the second set of alive messages from the entity subordinate to the first entity; and

the entity status reporting module is further configured to transmit a third status message to the second entity indicating the entity subordinate to the first entity as active in response to the entity status controller determining that the entity subordinate to the first entity is active.

17. The entity status reporting apparatus of claim 11 wherein:

the entity status controller is further configured to determine a change in the status of the first entity; and

the entity status reporting module is further configured to transmit a status message reporting a subsequent status of the first entity to the second entity upon the entity status controller determining the change.

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 Mar 21, 2014
From: ROBESKY, KENNETH A.
To: SHORETEL, INC.
Reel/Frame 032491/0242 →
Continuity (1)
Continuation 12571065 · Sep 30, 2009