IP Library › Granted Patent US 12,664,224
Granted Patent B2
US 12,664,224 · App. 18/655,901 · Granted Jun 23, 2026

Systems and methods for discovering and monitoring devices using search patterns for object identifiers and values

Inventors: Scott Logan (Arlington, MA); Kevin Davis (Apollo Beach, FL)
Assignee: ConnectWise, LLC
G06F16/955G06F16/2246G06F16/951H04L41/0213H04L41/0853H04L43/0817H04L41/0695H04L41/0803H04L41/0843H04L41/0846
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 12,664,224
App. No.
18/655,901
Filed
May 6, 2024
Granted
Jun 23, 2026
Kind
B2
Art Unit
2164
USPC
707/770
Abstract

The present disclosure is directed to systems and methods of managing remote devices. The system can include a server with memory, a detection module, and a collection module. The memory can store a management information base (MIB) having a hierarchical tree of object identifiers and corresponding object values. The detection module can query devices and receive a first object identifier and its first object value, which can vary from those in the MIB; and use patterns to match the first object identifier and object value; and generate an identification of the device from the matches. The collection module can use the identification to select a collection template, which can indicate a subtree of the MIB and a collection pattern; traverse the subtree and identify a second object identifier that matches the collection pattern, and its second object value; and associate the second object value with the first object value.

Claims (40)

1 . A system for managing remote devices, comprising:

a device comprising a memory and one or more processors to:

receive a query for device information; and

retrieve, from the memory, an object identifier and an object value responsive to the query, the object identifier varying from each of a stored plurality of object identifiers and the object value varying from each of a stored plurality of corresponding object values; and

a server comprising one or more second processors to:

receive the object identifier and the object value from the device;

generate an identification of the device based on a first pattern that matches the object identifier and a second pattern that matches the object value;

select a collection template from a plurality of collection templates based on the identification of the device, the selected collection template comprising a collection pattern accounting for variations between the object identifier and each of the stored plurality of object identifiers,

identify a second object identifier that matches the collection pattern and a corresponding second object value; and

associate the corresponding second object value with the object value received from the device based on the collection pattern.

2 . The system of claim 1 , wherein the memory stores attributes associated with each of the stored plurality of object identifiers, the attributes comprising a data type, and a set of supported operations.

3 . The system of claim 1 , wherein the object identifier varies from each of the stored plurality of object identifiers.

4 . The system of claim 1 , wherein the object value varies from each of the stored plurality of corresponding object values.

5 . The system of claim 1 , wherein the server detects that the object value varies from each of the stored plurality of corresponding object values subsequent to production of the device.

6 . The system of claim 1 , wherein the server implements a data collection strategy responsive to a variation between the object identifier and each of the stored plurality of object identifiers or the variation between the object value and each of the stored plurality of corresponding object values.

7 . The system of claim 1 , wherein at least one of the object identifier or the corresponding second object identifier comprises a numeric value or a string value.

8 . The system of claim 1 , wherein the collection pattern comprises a regular expression that indicates a relationship between the corresponding second object value and the object value.

9 . The system of claim 1 , wherein the server:

uses the collection pattern to identify each object identifier that matches the collection pattern; and

associates each object value received from the device corresponding to each object identifier that matches the collection pattern with the second object value received from the device.

10 . The system of claim 1 , wherein at least one of the object identifier or the second object identifier is based on an X.690 object identifier.

11 . A method for managing remote devices, comprising:

receiving, by a device comprising a memory and one or more processors, a query for device information;

retrieving, by the device from the memory, an object identifier and an object value responsive to the query, the object identifier varying from each of a stored plurality of object identifiers and the object value varying from each of a stored plurality of corresponding object values stored;

receiving, by a server comprising one or more second processors, the object identifier and the object value from the device;

generating, by the server, an identification of the device based on a first pattern that matches the object identifier and a second pattern that matches the object value;

select a collection template from a plurality of collection templates based on the identification of the device, the selected collection template comprising a collection pattern accounting for variations between the object identifier and each of the stored plurality of object identifiers;

identify a second object identifier that matches the collection pattern and a corresponding second object value; and

associating, by the server, the corresponding second object value with the object value received from the device based on the collection pattern.

12 . The method of claim 11 , further comprising storing, by the memory, attributes associated with each of the stored plurality of object identifiers, the attributes comprising a data type, and a set of supported operations.

13 . The method of claim 11 , wherein the object identifier varies from each of the stored plurality of object identifiers.

14 . The method of claim 11 , wherein the object value varies from each of the stored plurality of corresponding object values.

15 . The method of claim 11 , further comprising detecting, by the server, that the object value varies from each of the stored plurality of corresponding object values subsequent to production of the device.

16 . The method of claim 11 , further comprising implementing, by the server, a data collection strategy responsive to a variation between the object identifier and each of the stored plurality of object identifiers or the variation between the object value and each of the stored plurality of corresponding object values.

17 . The method of claim 11 , wherein at least one of the object identifier or the corresponding second object identifier comprises a numeric value or a string value.

18 . The method of claim 11 , wherein the collection pattern comprises a regular expression that indicates a relationship between the corresponding second object value and the object value.

19 . The method of claim 11 , further comprising:

using the collection pattern to identify each object identifier that matches the collection pattern; and

associating, by the server, each object value received from the device corresponding to each object identifier that matches the collection pattern with the second object value.

20 . The method of claim 11 , wherein at least one of the object identifier or the second object identifier is based on an X.690 object identifier.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2025
From: LOGAN, SCOTT; DAVIS, KEVIN
To: LABTECH SOFTWARE, LLC
Reel/Frame 070438/0268 →
MERGER Recorded Mar 7, 2025
From: LABTECH SOFTWARE, LLC
To: CONNECTWISE, INC.
Reel/Frame 070438/0309 →
CHANGE OF NAME Recorded Mar 7, 2025
From: CONNECTWISE, INC.
To: CONNECTWISE, LLC
Reel/Frame 070446/0738 →
Continuity (6)
Continuation 18093529 · Jan 5, 2023
Continuation 17068436 · Oct 12, 2020
Continuation 15977164 · May 11, 2018
Continuation 14704606 · May 5, 2015
Provisional Application 61989548 · May 7, 2014
Related Publication 20240289404A1 · Aug 29, 2024
References Cited (92)
US 6081838A · Yoshihara · 2000 [cited by examiner]
US 6108782A · Fletcher et al. · 2000 [cited by applicant]
US 6954786B1 · Vered et al. · 2005 [cited by applicant]
US 7574431B2 · Young · 2009 [cited by applicant]
US 7668944B2 · Leib et al. · 2010 [cited by applicant]
US 7860960B1 · Knight et al. · 2010 [cited by applicant]
US 7886033B2 · Hopmann et al. · 2011 [cited by applicant]
US 8849973B2 · Leib et al. · 2014 [cited by applicant]
US 9971840B2 · Logan et al. · 2018 [cited by applicant]
US 10803138B2 · Logan et al. · 2020 [cited by applicant]
US 11562041B2 · Logan et al. · 2023 [cited by applicant]
US 11977597B2 · Logan et al. · 2024 [cited by applicant]
US 20030090716A1 · Umebayashi · 2003 [cited by examiner]
US 20030208480A1 · Faulkner · 2003 [cited by examiner]
US 20040255014A1 · Motoyama · 2004 [cited by examiner]
US 20050080886A1 · Croy · 2005 [cited by examiner]
US 20050114486A1 · Obert · 2005 [cited by examiner]
US 20050278692A1 · Sridhar · 2005 [cited by examiner]
US 20060092861A1 · Corday · 2006 [cited by examiner]
US 20070101193A1 · Johnson · 2007 [cited by examiner]
US 20090132719A1 · Havard · 2009 [cited by examiner]
US 20100009481A1 · Tseng et al. · 2010 [cited by applicant]
US 20100094981A1 · Cordray · 2010 [cited by examiner]
US 20110239058A1 · Umezuki · 2011 [cited by examiner]
US 20120030327A1 · Conrad · 2012 [cited by examiner]
US 20120239793A1 · Veerabhadrappa · 2012 [cited by examiner]
US 20120290704A1 · Primerano · 2012 [cited by examiner]
US 20130036108A1 · Corbeau · 2013 [cited by applicant]
US 20130138958A1 · Mandell · 2013 [cited by examiner]
US 20130311238A1 · Cheloff · 2013 [cited by examiner]
US 20140160942A1 · Mandavilli · 2014 [cited by examiner]
US 20150089055A1 · Sullivan · 2015 [cited by applicant]
US 20150324465A1 · Logan et al. · 2015 [cited by applicant]
US 20160134491A1 · Cordray · 2016 [cited by examiner]
US 20190114306A1 · Logan et al. · 2019 [cited by applicant]
US 20210133260A1 · Logan et al. · 2021 [cited by applicant]
US 20230145471A1 · Logan et al. · 2023 [cited by applicant]
CN 101582806A · 2009 [cited by examiner]
WO WO2005088905A1 · 2005 [cited by examiner]
Corrected Notice of Allowability for U.S. Appl. No. 17/068,436 dated Sep. 28, 2022. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 18/093,529 dated Jul. 19, 2023. [cited by applicant]
Alloy Software, “Alloy Discovery 6”, product datasheet, Apr. 16, 2013, Nutley, New Jersey. [cited by applicant]
Alloy Software, “Alloy Navigator 6”, product overview, Jun. 25, 2010, Nutley, New Jersey. [cited by applicant]
Barry et al., “The Cacti Manual”, section III. 12, SNMP Query XML Syntax, 2013, retrieved from cacti.net web site on Mar. 31, 2015. [cited by applicant]
Bass et al. “Rapid software development for multi-vendor services.” Bell Labs Technical Journal 9, No. 4, 2005, Alcatel-Lucent, Boulogne-Billancourt, France. [cited by applicant]
Cisco Systems, Inc., “Topology Discovery Methods”, User Guide for CiscoWorks Network Connectivity Monitor, chapter 9, document 78-15279-01, Aug. 4, 2007, San Jose, California. [cited by applicant]
Cisco Systems, Inc., “Understanding Discovery Results”, User Guide for CiscoWorks Network Connectivity Monitor, chapter 10, document 78-15279-01, Aug. 4, 2007, San Jose, California. [cited by applicant]
Curry, Jane, “Zenoss Discovery and Classification”, Skills 1st Ltd., Jun. 22, 2009, Maidenhead, United Kingdom. [cited by applicant]
Gavalas et al., “Advanced network monitoring applications based on mobile/intelligent agent technology”, Computer Communications 23, No. 8, Apr. 1, 2000, Elsevier, Amsterdam, Netherlands. [cited by applicant]
Goldszmidt, German, “Network Management Views using Delegated Agents”, Proceedings of the 6th CAS Conference, Nov. 1996, Toronto, Canada. [cited by applicant]
Ipswitch, Inc., “WhatsUp Gold Distributed edition”, data sheet, document WUG_C104-P775, Apr. 16, 2008, Lexington, Massachusetts. [cited by applicant]
Ipswitch, Inc., “WhatsUp Gold Premium”, data sheet, document WUG_C104-P774, Apr. 16, 2008, Lexington, Massachusetts. [cited by applicant]
Ipswitch, Inc., “WhatsUp Gold User Guide”, version 16.1, Mar. 11, 2013, Lexington, Massachusetts. [cited by applicant]
Ipswitch, Inc., “WhatsUp Gold WhatsConnected User Guide”, version 3.0, Feb. 9, 2011, Lexington, Massachusetts. [cited by applicant]
Jakubcik, Ondeej, “Sun servers open-source software systems management”, bachelor's thesis, Czech Technical University in Prague, Faculty of Electrical Engineering, May 27, 2010, Prague, Czech Republic. [cited by applicant]
Kaseya, “Discovery”, Kaseya 2 User Guide, Version 6.5 and 1.0, Jan. 23, 2014, Waltham, Massachusetts. [cited by applicant]
Kaseya, “Kaseya Discovery & Inventory”, product brief, Feb. 10, 2010, Waltham, Massachusetts. [cited by applicant]
Level Platforms Inc., “Managed Workplace 2012”, release notes, Mar. 19, 2012, Level Platforms, Ottawa, Ontario, Canada. [cited by applicant]
Level Platforms Inc., “Managed Workplace Setup Guide—On Premise”, user manual, Jul. 3, 2012, Level Platforms, Ottawa, Ontario, Canada. [cited by applicant]
Luderer et al. “Network Management Agents Supported by a Java Environment.” Integrated Network Management 86 (1997): 790-790. [cited by applicant]
Maestas, Joseph H., “Network Configuration Management: Paving the Way to Network Agility”, Sandia Report SAND2007-4475, Sandia National Laboratories, Aug. 2007, Albuquerque, New Mexico. [cited by applicant]
McMahon, Discovery of Delay-Tolerant Networking Endpoint Elements. Diss. Trinity College Dublin, 2013. [cited by applicant]
N-Able Technologies, Inc., a division of SolarWinds, “N-Central Getting Started”, version 9.1, Oct. 18, 2012, Ottawa, Ontario, Canada. [cited by applicant]
N-Able Technologies, Inc., a division of SolarWinds, “N-Central—An Introduction to SNMP”, Oct. 18, 2012, Ottawa, Ontario, Canada. [cited by applicant]
Networkview Software, pages from help file, extracted from downloaded/installed software from networkview.com web site Apr. 24, 2014, Apr. 30, 2011, Epalinges, Switzerland. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 14/704,606 dated Jan. 22, 2018. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 15/977,164 dated Jun. 11, 2020. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 17/068,436 dated Sep. 14, 2022. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 18/093,529 dated Jan. 8, 2024. [cited by applicant]
Office Action for U.S. Appl. No. 14/704,606 dated Aug. 8, 2017. [cited by applicant]
Office Action for U.S. Appl. No. 17/068,436 dated Feb. 16, 2022. [cited by applicant]
Pasnak, J. P., “Data Query Templates”, Cacti documentation and howtos, updated Jun. 10, 2010, retreived from cacti.net web site on Mar. 31, 2015. [cited by applicant]
Porter, Lee, “Agentx and multiple copies of same mibs—distributed control plane”, net-snmp mailing list, Mar. 21, 2006, downloaded from opensubscriber.com web site Apr. 12, 2015. [cited by applicant]
Rochon, Peter, “What's new in version 5”, Level Platforms Managed Workplace 5.0 release notes, Oct. 21, 2012, Level Platforms, Ottawa, Ontario, Canada. [cited by applicant]
Solarwinds Inc., “Network Topology Mapper”, datasheet, Nov. 27, 2013, Austin, Texas. [cited by applicant]
Solarwinds Worldwide, LLC, “Discover & Map Your Network Using SolarWinds® Network Topology Mapper (NTM)”, tech tip, Nov. 18, 2013, Austin, Texas. [cited by applicant]
Solarwinds Worldwide, LLC, “Network Performance Monitor Administrator Guide”, user manual, version 10.7, Mar. 4, 2014, Austin, Texas. [cited by applicant]
Story, Robert, “rstory's NET-SNMP Developers Frequently Asked Questions Page”, Apr. 19, 2006, downloaded from freesnmp.com web site Apr. 12, 2015. [cited by applicant]
The OpenNMS Group, Inc., “OpenNMS Provisioning”, user manual, version 1.8.0, Jan. 21, 2010, Pittsboro, North Carolina. [cited by applicant]
Vincente et al., “The Network Documentation Tool—Netdot”, University of Oregon, Dec. 12, 2013, Eugene, Oregon. [cited by applicant]
Zenoss, Inc., “Zenoss Administration”, part No. 06-102010-3.0-v03, Oct. 21, 2010, Annapolis, Maryland. [cited by applicant]
Zoho Corp., “WebNMS Framework 5 Administrator Guide”, version 5.2, Oct. 22, 2013, Pleasanton, California. [cited by applicant]
Zoho Corp., “WebNMS Framework 5 Deployment Guide”, version 5.0, May 5, 2011, Pleasanton, California. [cited by applicant]
Zoho Corp., “WebNMS Framework 5 Developer Guide”, version 5.2, Oct. 22, 2013, Pleasanton, California. [cited by applicant]
Zoho Corp., “WebNMS Framework 5 User Guide”, version 5.2, Oct. 22, 2013, Pleasanton, California. [cited by applicant]
Zoho Corporation, “Add Credentials”, OpManager online help topic, downloaded from help.opmanager.com site Apr. 17, 2014, Pleasanton, California. [cited by applicant]
Zoho Corporation, “Discover Individual Devices”, OpManager online help topic, downloaded from help.opmanager.com site Apr. 17, 2014, Pleasanton, California. [cited by applicant]
Zoho Corporation, “Discovering Networks Using OpManager”, OpManager online help topic, downloaded from help.opmanager.com site Apr. 17, 2014, Pleasanton, California. [cited by applicant]
Zoho Corporation, “Layer 2 Mapping”, OpManager online help topic, downloaded from help.opmanager.com site Apr. 17, 2014, Pleasanton, California. [cited by applicant]
Zoho Corporation, “ManageEngine OpManager User Guide”, Jan. 17, 2014, Pleasanton, California. [cited by applicant]
Zoho Corporation, “Rule Engine”, OpManager online help topic, downloaded from help.opmanager.com site Apr. 16, 2014, Pleasanton, California. [cited by applicant]
Zoho Corporation, demonstration pages for TopoMapper Plus product, downloaded from demo.topomapperplus.com site Apr. 16, 2014, Pleasanton, California. [cited by applicant]