IP Library Granted Patent US 8,370,479
Granted Patent B2
US 8,370,479 · App. 11/538,402 · Granted Feb 5, 2013

System and method for dynamically grouping devices based on present device conditions

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 8,370,479
App. No.
11/538,402
Granted
Feb 5, 2013
Kind
B2
Abstract

A method to dynamically group devices based on device information, which is associated with a system for monitoring the device information that communicates information between a device and an enterprise. Information is collected from a device information source to obtain an actual status of a device. The actual status of the device is compared to a stored status of the device. The stored status is stored on a server of the enterprise. The enterprise determines if the actual status has been changed from the stored status. When a change is detected, the method performs at least one of the acts of automatically disassociating the device from a group that reflects the stored status and automatically associating the device with a new group to reflect the actual status.

Claims (60)

1. A method that is performed by an enterprise system, the method comprising:

obtaining information from a device to obtain an actual status of the device;

comparing the actual status of the device to a prior status of the device, the device initially being associated with a first group that corresponds to the prior status;

determining that the actual status is different from the prior status based on the comparing, wherein, initially, no group exists that corresponds to the actual status;

consulting a rule to determine to create a second group that corresponds to the actual status of the device, the rule for triggering group creation when no group exists that corresponds to the actual status;

creating the second group in accordance with the rule, the second group being part of a group hierarchy comprised of multiple groups at different levels in the group hierarchy;

automatically disassociating the device from the first group and automatically associating the device with the second group;

sending a notification to the second group; and

sending the notification to one or more groups that are above the second group in the group hierarchy based on failure to receive acknowledgement from the second group.

2. The method of claim 1 , further comprising establishing one or more group rules based on a condition of the device, the rule for triggering group creation being among the one or more group rules.

3. The method of claim 2 , further comprising, in response to an additional change in a status of the device, associating the device with one or more other groups and/or disassociating the device from the second group.

4. The method of claim 1 , further comprising sending the notification when the actual status of the device corresponds to a predefined condition.

5. The method of claim 1 , further comprising:

determining that the first group is empty after the device is disassociated from the first group; and

automatically deleting the first group.

6. The method of claim 1 , further comprising:

disassociating first group-based business logic from the device when the device is automatically disassociated from the first group; and

associating second group-based business logic with the device when the device is automatically associated with the second group.

7. The method of claim 1 , wherein the group hierarchy comprises a static root group and one or more sub-groups, the second group being among the one or more sub-groups.

8. The method of claim 7 , wherein the static root group is defined manually, and the one or more sub-groups is defined dynamically.

9. A system comprising a server, the system being configured to perform operations comprising:

obtaining information from a device to obtain an actual status of the device;

comparing the actual status of the device to prior status of the device, the device initially being associated with a first group that corresponds to the prior status;

determining that the actual status is different from the prior status based on the comparing wherein, initially, no group exists that corresponds to the actual status;

consulting a rule to determine to create a second group that corresponds to the actual status of the device, the rule for triggering group creation when no group exists that corresponds to the actual status;

creating the second group in accordance with the rule, the second group being part of a group hierarchy comprised of multiple groups at different levels in the group hierarchy; and

automatically disassociating the device from the first group and automatically associating the device with the second group;

sending a notification to the second group; and

sending the notification to one or more groups that are above the second group in the group hierarchy based on failure to receive acknowledgement from the second group.

10. The system of claim 9 , wherein the operations further comprise establishing one or more group rules based on a condition of the device, the rule for triggering group creation being among the one or more group rules.

11. The system of claim 10 , wherein the operations further comprise, in response to an additional change in a status of the device, associating the device with one or more other groups and/or disassociating the device from the second group.

12. The system of claim 9 , wherein the operations further comprise sending the notification when the actual status of the device corresponds to a predefined condition.

13. The system of claim 9 , wherein the operations further comprise:

determining that the first group is empty after the device is disassociated from the first group; and

automatically deleting the first group.

14. The system of claim 9 , wherein the operations further comprise:

disassociating first group-based business logic from the device when the device is automatically disassociated from the first group; and

associating second group-based business logic with the device when the device is automatically associated with the second group.

15. The system of claim 9 , wherein the group hierarchy comprises a static root group and one or more sub-groups, the second group being among the one or more sub-groups.

16. The system of claim 15 , wherein the static root group is defined manually, and the one or more sub-groups is defined dynamically.

17. A non-transitory medium bearing instructions to cause a machine to perform operations comprising:

obtaining information from a device to obtain an actual status of the device;

comparing the actual status of the device to a prior status of the device, the device initially being associated with a first group that corresponds to the prior status;

determining that the actual status is different from the prior status based on the comparing, wherein, initially, no group exists that corresponds to the actual status;

consulting a rule to determine to create a second group that corresponds to the actual status of the device, the rule for triggering group creation when no group exists that corresponds to the actual status;

creating the second group in accordance with the rule, the second group being part of a group hierarchy comprised of multiple groups at different levels in the group hierarchy;

automatically disassociating the device from the first group and automatically associating the device with the second group;

sending a notification to the second group; and

sending the notification to one or more groups that are above the second group in the group hierarchy based on failure to receive acknowledgement from the second group.

18. The non-transitory medium of claim 17 , wherein the operations further comprise establishing one or more group rules based on a condition of the device, the rule for triggering group creation being among the one or more group rules.

19. The non-transitory medium of claim 17 , wherein the operations further comprise sending notification if when the actual status of the device corresponds to a predefined condition.

20. The non-transitory medium of claim 19 , wherein the operations further comprise, in response to an additional change in a status of the device, associating the device with one or more other groups and/or disassociating the device from the second group.

21. The non-transitory medium of claim 17 , wherein the operations further comprise:

determining that the first group is empty after the device is disassociated from the first group; and

automatically deleting the first group.

22. The non-transitory medium of claim 17 , wherein the operations further comprise:

disassociating first group-based business logic from the device when the device is automatically disassociated from the first group; and

associating second group-based business logic with the device when the device is automatically associated with the second group.

23. The non-transitory medium of claim 17 , wherein the group hierarchy comprises a static root group and one or more sub-groups, the second group being among the one or more sub-groups.

24. The non-transitory medium of claim 23 , wherein the static root group is defined manually, and the one or more sub-groups is defined dynamically.

Assignments (9)
SECURITY INTEREST Recorded Sep 13, 2018
From: PTC INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 047480/0888 →
SECURITY INTEREST Recorded Nov 4, 2015
From: PTC INC.
To: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 037046/0930 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNOR NAME PREVIOUSLY RECORDED AT REEL: 035697 FRAME: 0321. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER. Recorded Jun 1, 2015
From: AXEDA CORPORATION
To: PTC INC.
Reel/Frame 035806/0158 →
MERGER Recorded May 22, 2015
From: PTC INC.
To: PTC INC.
Reel/Frame 035697/0321 →
MERGER Recorded May 22, 2015
From: AXEDA ACQUISITION CORP.
To: AXEDA CORPORATION
Reel/Frame 035697/0044 →
RELEASE OF SECURITY INTEREST Recorded Aug 25, 2014
From: COMERICA BANK
To: AXEDA ACQUISITION CORP.
Reel/Frame 033607/0890 →
SECURITY AGREEMENT Recorded Jul 24, 2012
From: AXEDA ACQUISITION CORP.
To: COMERICA BANK
Reel/Frame 028629/0559 →
RELEASE OF SECURITY INTEREST Recorded Jul 17, 2012
From: SILICON VALLEY BANK
To: AXEDA ACQUISITION CORP.
Reel/Frame 028566/0210 →
RELEASE OF SECURITY INTEREST Recorded Jul 17, 2012
From: MMV CAPITAL PARTNERS INC.
To: AXEDA ACQUISITION CORP.
Reel/Frame 028566/0344 →