Computer system and method for commissioning network assets

Abstract

A computer device and method for automatically generating a network configuration connecting a plurality of network asset devices to a public network. Metadata associated with each of a plurality of network asset devices to be installed on a public network is received in a network configuration device. A defined functional group consisting of one or more network asset devices is assigned to each of the plurality of network asset devices in the network configuration device. And generating, by the network configuration device, a dynamic host configuration protocol (DHCP) retention table that defines, for each of the defined functional groups of the network asset devices, a subnet mask for configuring the public network to implement the plurality of network asset devices.

Description

Technical Field

[0001] The disclosed embodiments generally relate to computer-implemented methods and systems for debugging network assets, and more specifically, to allocating network addresses and associating assets in function groups, and determining network configurations for debugging assets on a network. Background Technology

[0002] Currently, commissioning of many residential and building network-coupled asset devices (including but not limited to: Operational Technology (OT); Industrial Internet of Things (IIoT) and Internet of Things (IoT) assets) (“network asset devices”) is often time-consuming and prone to errors due to mis-entry of network asset device configuration data (such as network information and device associations (e.g., a specific camera asset device being associated with a specific apartment in a residential building)). Furthermore, the time-consuming process of entering network configuration data significantly increases the overall cost of system installation.

[0003] Therefore, there is a need for systems and methods that eliminate the aforementioned drawbacks of current methods for debugging network asset devices used on public infrastructure networks by providing efficient and rapid mechanisms / methods for allocating network IP addresses and associating network asset devices within functional groups, while automatically determining the network configuration data required for the network installation of multiple network asset devices. Furthermore, there is a need to reduce the skill level required of users to perform debugging of network asset devices on public infrastructure networks. Summary of the Invention

[0004] The objects and advantages of the illustrated embodiments described below will be set forth in the description and will become apparent therefrom. Additional advantages of the illustrated embodiments will be realized and obtained through the written description and its claims, as well as the devices, systems, and methods particularly pointed out in the drawings.

[0005] To achieve these and other advantages, and in accordance with the purposes of the illustrated embodiments, the disclosed embodiments generally relate to providing efficient computer tools and processes for assigning assets to functional network packets with network IP addresses and determining network configurations (e.g., subnet masks and DHCP reservation lists) to configure the network for using / deploying assets. In specific embodiments, the subnet mask and DHCP reservation list are uploaded to a network-associated router / firewall device. A significant advantage of the illustrated embodiments is that they significantly reduce the skill required of users (e.g., technicians) responsible for deploying multiple assets in a specific location (e.g., an apartment building).

[0006] According to one aspect of the illustrated embodiment, a computer apparatus and process are provided that utilizes a QR code with specific information, combined with a specialized computer debugging process and tools, for creating and maintaining a hierarchical information set regarding multiple assets to be debugged in a specific geographic location (e.g., an apartment building). In some embodiments, the hierarchical information includes names, network addresses, and subnet masks, as well as functional groupings associated with the assets. According to other embodiments, and as an alternative to using QR codes, a portable computer device, such as a smartphone, is configured and operated (e.g., via an app) to scan text from the asset to identify a printed MAC address from the asset's standard device label, and additionally enables the asset installer (e.g., a user of the portable computer device) to selectively select the device type, preferably from a drop-down list / menu.

[0007] The illustrated embodiment provides an efficient process that quickly creates DHCP IP reservation tables and required subnet masks for networks associated with public infrastructure (such as apartment building networks) to debug asset usage on the network. The illustrated embodiment also generates configuration information for basic / headend / control units associated with functional groups of certain assets.

[0008] In a further optional aspect, a computer device and method for automatically generating network configurations to connect multiple network asset devices to a public network are disclosed. The network configuration device receives metadata associated with each of the multiple network asset devices to be installed on the public network. The network configuration device assigns a defined function group, consisting of one or more network asset devices, to each of the multiple network asset devices. And the network configuration device generates a Dynamic Host Configuration Protocol (DHCP) reservation table, which defines a subnet mask for configuring the public network to implement the multiple network asset devices for each defined function group of the network asset devices. Attached Figure Description

[0009] Therefore, those skilled in the art to which this subject matter pertains will readily understand how to manufacture and use the devices and methods disclosed herein without excessive experimentation. Preferred illustrative embodiments will now be described in detail with reference to certain accompanying drawings, in which:

[0010] Figure 1 An example communication network is shown for use with one or more illustrated embodiments;

[0011] Figure 2 Example network devices / nodes are shown for use with one or more illustrated embodiments;

[0012] Figure 3 This is an exemplary system diagram depicting an asset debugging tool for debugging assets running on a network, according to the illustrated embodiment; and

[0013] Figure 4 The illustration depicts the utilization according to the shown embodiment. Figure 3 The asset debugging tool is a flowchart of the computer process for debugging assets running on the network. Detailed Implementation

[0014] The illustrated embodiments will now be described more fully with reference to the accompanying drawings, wherein like reference numerals denote similar structural / functional features. The illustrated embodiments are not intended to be limited in any way to what is shown, as the illustrated embodiments described below are merely exemplary and, as those skilled in the art will understand, can be embodied in various forms. Therefore, it should be understood that any structural and functional details disclosed herein should not be construed as limiting, but merely as the basis for the claims and as an indication to teach those skilled in the art to use the discussed embodiments in various ways. Furthermore, the terminology and phrases used herein are not intended to be limiting, but rather to provide an understandable description of the illustrated embodiments.

[0015] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. Although any methods and materials similar to or equivalent to those described herein may also be used in the practice or testing of the illustrated embodiments, exemplary methods and materials are described hereafter.

[0016] It is important to note that, as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural indicators unless the context clearly specifies otherwise. Thus, for example, a reference to “stimulus” includes a plurality of such stimuli, a reference to “signal” includes a reference to one or more signals, and their equivalents known to those skilled in the art, etc.

[0017] It should be understood that the illustrated embodiments discussed below are preferably software algorithms, programs, or code residing on a computer-usable medium, having control logic for enabling execution on a machine having a computer processor. This machine typically includes memory configured to provide execution outputs of the computer algorithm or program according to the illustrated embodiments.

[0018] As used herein, the term "software" means synonymous with any code or program that can be implemented in the processor of a host computer, whether the implementation is in hardware, firmware, or as a software computer product available on a disk, memory storage device, or for download from a remote machine. The embodiments described herein include software that implements the equations, relations, and algorithms described above. Based on the above embodiments, those skilled in the art will understand further features and advantages of the illustrated embodiments. Therefore, the illustrated embodiments are not limited to what has been specifically shown and described, except as pointed out in the appended claims.

[0019] Now we turn descriptively to the accompanying drawings, in which similar reference numerals in multiple views denote similar elements. Figure 1 An exemplary communication network 100 is depicted, in which the embodiments shown below can be implemented. It should be understood that the communication network 100 is a geographically distributed collection of nodes interconnected by communication links and segments for transmitting data between end nodes, such as personal computers, workstations, smartphones, tablets, televisions, sensors, and / or other devices, such as automobiles. Many types of networks are available, ranging from Local Area Networks (LANs) to Wide Area Networks (WANs). LANs typically connect nodes via dedicated, proprietary communication links located in the same common physical location (such as a building or campus). WANs, on the other hand, typically connect geographically dispersed nodes via long-distance communication links, such as public carrier telephone lines, optical paths, Synchronous Optical Networks (SONETs), Synchronous Digital Hierarchy (SDH) links, or Power Line Communication (PLC), etc.

[0020] Figure 1 This is a schematic block diagram of an example communication network 100, which schematically includes nodes / devices 101-108 (e.g., sensors 102, asset debugging devices / devices 103, smartphone devices 105, servers 106, routers 107, switches 108, databases, etc.) interconnected via various communication methods. For example, link 109 may be a wired link or may include a wireless communication medium, wherein some nodes communicate with other nodes based on factors such as distance, signal strength, current operating status, location, etc. Furthermore, as those skilled in the art will understand, each device may, where appropriate, communicate data packets (or frames) 142 with other devices using predefined network communication protocols (e.g., various wired and wireless protocols, etc.). In this case, the protocol consists of a set of rules defining how nodes interact with each other. Those skilled in the art will understand that any number of nodes, devices, links, etc., can be used in a computer network, and the view shown herein is for simplicity. Furthermore, although embodiments are shown herein with reference to a general network cloud, the description herein is not limited thereto and can be applied to hardwired networks.

[0021] As those skilled in the art will understand, aspects of the illustrated embodiments can be embodied as a system, method, or computer program product. Therefore, aspects of the illustrated embodiments can take the form of a completely hardware embodiment, a completely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which are generally referred to herein as “device,” “apparatus,” “module,” or “system.” Furthermore, aspects of the illustrated embodiments can take the form of a computer program product embodied in one or more computer-readable media containing computer-readable program code.

[0022] Any combination of one or more computer-readable media may be used. A computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium can be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples (not an exhaustive list) of computer-readable storage media will include: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In the context of this document, a computer-readable storage medium can be any tangible medium capable of containing or storing a program used by or in connection with an instruction execution system, apparatus, or device. A computer-readable signal medium may include a propagated data signal containing computer-readable program code, for example, in baseband or as part of a carrier wave. Such a propagated signal can take any of a variety of forms, including but not limited to electromagnetic, optical, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium that is not a computer-readable storage medium and can transmit, propagate or transfer a program used by or in connection with an instruction execution system, apparatus or device.

[0023] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cable, RF, or any suitable combination thereof. The computer program code for performing the operations of various aspects of this invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, Smalltalk, C++, Python, etc., and conventional procedural programming languages ​​such as the "C" programming language or similar languages. The program code may be executed entirely on the user's computer as a standalone software package, partially on the user's computer, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet through an Internet service provider).

[0024] The aspects of the illustrated embodiments are described below with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to the illustrated embodiments. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a computer device, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams.

[0025] These computer program instructions may also be stored in a computer-readable medium that can instruct a computer, other programmable data processing device, or other equipment to operate in a particular manner, such that the instructions stored in the computer-readable medium generate and maintain an inventory asset database, which includes instructions that implement functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0026] Computer program instructions may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide for implementing the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0027] Figure 2 This is a schematic block diagram of an example network computing device 200 (e.g., asset debugging apparatus / device 103, server 106, etc.) that can be used (or components thereof) with one or more embodiments described herein (e.g., as one of the nodes shown in network 100) to provide computer asset debugging tools and processes for debugging network-coupled asset devices. According to the illustrated embodiments, this includes, but is not limited to: Operational Technology (OT); Industrial Internet of Things (IIoT) and Internet of Things (IoT) assets (“network asset devices”) for configuring the network to use / debug assets at a specific physical location by assigning assets to certain functional network asset groups and by automatically assigning network IP addresses to assets and determining network configurations (e.g., subnet masks and DHCP reserved lists). As described above, in different embodiments, these various devices are configured to communicate with each other in any suitable manner, such as via communication network 100.

[0028] Device 200 is intended to represent any type of computer system capable of performing the teachings of the various illustrated embodiments. Device 200 is merely one example of a suitable system and is not intended to impose any limitation on the scope of use or functionality of the illustrated embodiments described herein.

[0029] It should be understood and appreciated that computing device 200 can operate in many other general-purpose or special-purpose computing system environments or configurations. Examples of well-known computing systems, environments, and / or configurations suitable for computing device 200 include, but are not limited to, personal computer systems, server computer systems, thin clients, fat clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, network PCs, minicomputer systems, and distributed data processing environments that include any of the aforementioned systems or devices. Computing device 200 can be described in the general context of computer system executable instructions, such as program modules, executed by a computer system. Typically, program modules can include routines, programs, objects, components, logic, data structures, etc., that perform a specific task or implement a specific abstract data type. Computing device 200 can be implemented in a distributed data processing environment, where tasks are performed by remote processing devices linked via communication network 100. In a distributed data processing environment, program modules can reside in local and remote computer system storage media, including memory storage devices.

[0030] Components of device 200 may include, but are not limited to, one or more processors or processing units 216, system memory 228, and a bus 218 that couples various system components, including system memory 228, to processor 216. Bus 218 represents one or more of a variety of bus architectures, including memory buses or memory controllers, peripheral buses, accelerated graphics ports, and processor or local buses using any of a variety of bus architectures. By way of example and not limitation, such architectures include Industry Standard Architecture (ISA) buses, Micro Channel Architecture (MCA) buses, Enhanced ISA (EISA) buses, Video Electronics Standards Association (VESA) local buses, and Peripheral Component Interconnect (PCI) buses. Computing device 200 typically includes various computer system readable media.

[0031] System memory 228 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 230 and / or cache memory 232. Computing device 200 may also include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 234 may be provided for reading from and writing to non-removable, non-volatile magnetic media (not shown, and generally referred to as a "hard disk drive"). Although not shown, a disk drive for reading from and writing to a removable, non-volatile disk and an optical disk drive for reading from or writing to a removable, non-volatile optical disk (e.g., CD-ROM, DVD-ROM, or other optical media) may be provided. In this case, each may be connected to bus 218 via one or more data media interfaces. As will be further described below, memory 228 may include at least one program product having a set (e.g., at least one) of program modules (240) configured to perform the functions of the embodiments shown in the illustrated embodiments, such as computer asset debugging tools and processes for debugging assets operating in a specific physical location by configuring the network to use / debug assets by assigning assets to certain functional network asset groups and by automatically assigning network IP addresses to assets and determining network configurations (e.g., subnet masks and DHCP reservation lists).

[0032] By way of example and not limitation, a program / utility 240 having a set (at least one) of program modules 215 (e.g., an asset debugging module), along with an operating system, one or more applications, other program modules, and program data, may be stored in memory 228. Each of the operating system, one or more applications, other program modules, and program data, or some combination thereof, may include an implementation of a network environment. Program modules 215 typically perform the functions and / or methods of the illustrated embodiments described herein.

[0033] Device 200 can also communicate with one or more external devices 214, such as a keyboard, pointing device, display 224, etc.; one or more devices that enable a user to interact with computing device 200; and / or any device that enables computing device 200 to communicate with one or more other computing devices (e.g., network interface card, modem, etc.). This communication can be performed via input / output (I / O) interface 222. Furthermore, device 200 can communicate with one or more networks via network adapter 220, such as a local area network (LAN), a general wide area network (WAN), and / or a public network (e.g., the Internet). As shown, network adapter 220 communicates with other components of computing device 200 via bus 218. It should be understood that, although not shown, other hardware and / or software components can be used in conjunction with device 200. Examples include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archiving storage systems.

[0034] Figure 1 and Figure 2 The following is a brief summary description intended to provide illustrative and / or suitable exemplary environments in which the embodiments described below may be implemented. Figure 1 and 2 These are examples of suitable environments and are not intended to impose any limitations on the structure, scope of use, or functionality of the illustrated embodiments. A particular environment should not be construed as having any dependency or requirement on any component or combination thereof shown in the exemplary operating environment. For example, in some cases, one or more elements of the environment may be considered unnecessary and omitted. In other cases, one or more additional elements may be considered necessary and added.

[0035] With the exemplary communication network 100 ( Figure 1 ) and computing devices 200 ( Figure 2 Having been generally shown and discussed above, a description of some of the illustrated embodiments will now be provided. It should be understood and appreciated that implementing… Figure 1-4 Exemplary embodiments of one or more components relate to computer asset debugging tools and processes for debugging assets operating at a specific physical location by configuring a network to use / debug assets by assigning assets to specific functional network asset groups, automatically assigning network IP addresses to assets, and determining network configurations (such as subnet masks and DHCP reserved lists).

[0036] Now for reference Figure 3A simplified exemplary embodiment depicting an asset commissioning tool / device 103 is shown, configured and operated to commission multiple network-coupled assets (e.g., 302-314) running on network 100, preferably in a geographic location 350 (e.g., apartment buildings, commercial buildings, residential / commercial floors, spaces, and other geographic locations with multiple assets to be specified in a particular functional grouping (as described herein)). It should be understood and appreciated that, according to the illustrated embodiment, the network-coupled asset device 103 may include IP-addressable devices, such as (but not limited to) operational technology (OT); industrial Internet of Things (IIoT) and Internet of Things (IoT) assets. Furthermore, it should be understood and appreciated that, according to the illustrated embodiment, the network-coupled asset device may also include non-IP-based network-coupled devices, such as (but not limited to) devices coupled to Zigbee and Z-Wave networks. Examples of such network-coupled asset devices may include (but are not limited to): sensors, actuators, appliances, cameras, gadgets, and various machines. For ease of description, the network-coupled asset devices (e.g., 302-314) described according to the illustrated embodiments are described in an environment intended for use in residential security-related devices (e.g., cameras, telephones, locks, door actuators) in an apartment in a residential apartment building 350. However, it should be understood and appreciated that the illustrated embodiments described herein should not be construed as being limited to devices applicable to residential buildings, as the illustrated embodiments will cover many other types of network asset devices intended for use in many types of geographic locations.

[0037] Now for reference Figure 3A unique QR code 375 is preferably created by asset commissioning device 103 (or another suitably configured device) to be provided / affixed to each asset (e.g., 302-314) for commissioning for network use in a specific geographic location 350 (e.g., residential apartment building 350). The information in the QR code includes metadata associated with the asset (e.g., 302), such as device type (e.g., door camera), its serial number, and network MAC address. It should be understood and appreciated that asset commissioning device 103 is preferably a portable computer device (e.g., a laptop or smartphone device) configured and operated (via software application or smartphone app—module 240) to perform the functions specified according to the illustrated embodiments described herein. As described herein, device 103 is configured and operated to associate the designated assets (e.g., 302-314) with functional groups (e.g., 320, 325, and 330). According to the illustrated embodiments, each functional group (e.g., public infrastructure 330) has an asset (e.g., management SW 314) that acts as the head-end unit role of that functional group (e.g., 330). The head-end unit asset (e.g., 314) for each functional group (e.g., 330) can be a separate device, or a single device that provides the necessary coordination for each functional group (e.g., 320, 325, and 330). As with other assets, a QR code 375 exists for each physical head-end unit (e.g., 314) or multiple head-end devices (discussed further below).

[0038] The following will be a reference Figure 4Further described, the asset commissioning process (400) preferably begins by creating and naming a new system file associated with the geographic location 350 (e.g., apartment building) where the assets (e.g., 302-314) will be commissioned. Next, the commissioning device 103 requests input regarding the type of system being installed, preferably from a dropdown list of supported system types (e.g., door access system). The commissioning device 103 also requests input of a basic unroutable IP address start point (e.g., 192.168.0.10) and the number of assets (e.g., 302-314) to be commissioned in the public infrastructure 350, to reserve that number of IP addresses, and preferably with an additional number (N) of IP addresses for future asset growth, starting from the beginning of a specified IP address range (e.g., 192.168.0.10). Next, for a specific asset (e.g., 302-314) to be debugged for use in public infrastructure 350, the user / technician of device 103 preferably selects the "New Function Group" action (e.g., via interaction with a GUI icon), then selects the function group type (e.g., preferably from a list of function group types supported by device 300 for this system type—e.g., "Apartment Door Access" or "Public Infrastructure"), and then preferably enters the name of the function group, such as "Apartment 1". Device 103 then preferably scans the QR code 375 of each asset (e.g., 302, 304) in that function group (e.g., 320), and then assigns an IP address and name based on the function group name and device type of each asset (e.g., 302, 304). Debugging device 103 also creates an entry in a DHCP reservation table created by debugging device 103 associated with the MAC address of each asset (e.g., 302, 304). Thus, when an asset (e.g., 302) is scanned, the asset installer (e.g., the user of device 130) is prompted to select the role of that asset, such as "Front Door Camera". Preferably, each asset role is unique, and each functional group can only be assigned once.

[0039] According to the illustrated embodiment, the debugging device 103 defaults to selecting the primary role for the asset type (e.g., "door camera"), but it can also preferably make a different selection each time a new function group (e.g., 320) is created (e.g., kitchen camera). If the role of the asset (e.g., 302) changes for the first asset, and the primary role has never been assigned to the asset, the debugging device 103 is preferably configured and operated to default to the new role assigned to the first asset type when the next function group is created and scanned by the device 103. Preferably, the aforementioned function group scan is terminated by the debugging device 103 when, for example, a "close function group" selection provided by the device 103 (e.g., preferably via a GUI) is initiated by the user. Note that if assets (e.g., 302-314) are omitted or need to be added later, the debugging device 103 can be operated to make the function group selectable (e.g., by selecting the "add device" button), so that another asset can be scanned and added to a predefined function group (e.g., 320, 325, and 330).

[0040] Once all QR codes 375 for assets (e.g., 302-314) in all functional groups (e.g., 320, 325, and 330) to be debugged for system / public infrastructure 350 have been scanned, the user initiates an end action, for example, by selecting the "End System QR Scan" button on the GUI associated with device 103. Note that if there is a single asset (e.g., 314) that provides multi-head functionality for all functional groups (e.g., 320, 325, and 330), a special functional group (e.g., the "Multi-head Device" functional group) is selected for that asset (e.g., 314) on device 103, and preferably its QR code is scanned before the aforementioned end system QR code scan.

[0041] Once the aforementioned “End System QR Scan” button is selected on the GUI associated with debugging device 103, debugging device 103 is configured and operated to automatically (e.g., without user intervention) generate the subnet masks required for debugging all assets (e.g., 302-314) for use on network 100 associated with system / public infrastructure 350, and to generate a DHCP reservation table in a format compatible with router 380 and / or firewall 382 used on network 100 for system / public infrastructure 350. This information is then uploaded from device 100 to preferred router 380 and / or firewall 382. According to the illustrated embodiment, debugging device 350 can also be operated and configured to generate a list of assets (e.g., 306, 308) in each functional group (e.g., 325), including the IP address, system type, device type, role, name information, and other relevant information for each asset, so as to load this information into the head-end unit (e.g., 304, 308, and 314) of each functional group.

[0042] Alternatively, and similarly to the above, once the debugging device 103 has completed scanning of QR codes 375 associated with assets (e.g., 302-314) used on network 100 associated with system / public infrastructure 350, the user of the debugging device 103 then preferably enables the debugging device 103 to update the aforementioned router 308 and / or firewall 382, ​​as well as other devices with DHCP server functionality. Preferably, the debugging device 103 downloads the current backup configuration file for system / public infrastructure 350 (e.g., one of several router / firewall models supported by the debugging device 103) from the aforementioned router 380 and / or firewall 382, ​​as well as other devices with DHCP server functionality associated with network 100, to modify the DHCP reserved portion of the aforementioned router 380 and / or firewall 382, ​​as well as other devices with DHCP server functionality, to merge each IP address into the MAC address allocation associated with the scanned assets (e.g., 302-314). The subnet mask portion of the aforementioned router 380 and / or firewall 382, ​​as well as other devices with DHCP server functionality in network 100, are then preferably modified by debugging device 103 based on the total number of assets (e.g., 302-314) in system / public infrastructure 350. Debugging device 103 is then preferably configured and operated to restore backup files to the aforementioned router 380 and / or firewall 382 and other devices with DHCP server functionality, and subsequently preferably instructs router 308 and / or firewall 382 to restart with their new / updated aforementioned configuration in order to enable operation of assets (e.g., 302-314) on network 100 of public infrastructure 350.

[0043] According to other illustrated embodiments, and instead of using QR codes, the debugging device 103 preferably includes a portable computer device, such as a smartphone, configured and operated (e.g., preferably via an app) to scan text from an asset (e.g., 302-314) to identify a printed MAC address from a standard device label on the asset, and additionally enabling the asset installer (e.g., the user of the portable computer debugging device 103) to selectively choose the device type, preferably from a drop-down list / menu.

[0044] Based on the above references Figure 3 A brief description of the operation of some of the illustrated embodiments is provided, and reference is now made to... Figure 4 (and continue to refer to) Figure 1-3The computer-implemented process 400 is now described for configuring network 100 to use / debug assets (302-314) by assigning assets (302-314) to specific function network asset groups (320, 325 and 330), automatically assigning network IP addresses to assets (302-314), and determining network configurations (e.g., subnet masks and DHCP reserved lists) to debug assets (e.g., network asset devices 302-314) running on network 100 at specific physical locations (350).

[0045] Beginning at step 402, the user defines, via debugging device 103, a preferred basic unroutable IP address starting point (e.g., 192.168.0.10) and the number of assets (e.g., 302-314) to be debugged in public infrastructure 350, so as to reserve that number of IP addresses for use on network 100 associated with public infrastructure, and preferably has an additional number (N) of IP addresses for future growth, starting at the beginning of the specified IP address range (e.g., 192.168.0.10). Next, in step 404, metadata associated with the asset (e.g., 302) to be debugged for use on network 100 of public infrastructure 350 is received, whereby the metadata may include (but is not limited to) device type (e.g., door camera), serial number, and network MAC address. As described above, the metadata is preferably obtained via QR code 375 associated with the asset (e.g., 302-314), or via other scanning means, such as scanning the MAC address associated with the asset (e.g., 302-314) by a suitable scanning device associated with debugging device 103.

[0046] In step 406, the debugging device 103 defines asset function groups (e.g., 320, 325, and 330), wherein the defined function group (e.g., 320) defines one or more assets (e.g., 302 and 304), which will be grouped for use with each other on the network 100 of the common infrastructure 350. In step 408, via the debugging device 103, an asset (e.g., 304), preferably via metadata received therefrom (step 404), is assigned to operate with a specific function group (e.g., 320), which consists of other assets (e.g., 302) with which it is intended to operate. In some embodiments, the asset (e.g., 304) in each function group (e.g., 320) is designated as the “head-end unit” of that function group (e.g., 320). Note that the head-end unit asset (e.g., 304) of each function group (e.g., 320) can be a separate device, or a single device providing the necessary coordination for each function group (e.g., 320, 325, and 330). Additionally, in step 412, if there exists a single asset (e.g., 314) that provides multi-head functionality for all functional groups (e.g., 320, 325, and 330), the commissioning device 103 assigns a special functional group (e.g., the "Multi-head Device" functional group) to that asset (e.g., 314).

[0047] Once the debugging device 103 has entered all assets (e.g., 302-314) for use on network 100 of public infrastructure 350, in step 414, the debugging device 103 automatically determines the required subnet mask for debugging all assets (e.g., 302-314) for use on network 100 associated with public infrastructure 350, and preferably also generates a DHCP reservation table in a format compatible with router 380 and / or firewall 380 and other devices with DHCP server functionality used on network 100 of public infrastructure 350. In step 416, this network configuration data (e.g., subnet mask and DHCP reservation table) is then uploaded from the debugging device 100 to preferred router 380 and / or firewall 382 and other devices with DHCP server functionality. Then, in step 418, each asset (e.g., 302-314) is used on network 100 of public infrastructure 350.

[0048] Furthermore, according to some of the illustrated embodiments, a list of assets (e.g., 306, 308) in each functional group (e.g., 325) is generated by the debugging device 103. This list preferably includes the IP address, system type, device type, role, and name information of each asset, so as to load this information into the head unit (e.g., 304, 308, and 314) of each functional group.

[0049] As will become apparent from the following description, the illustrated embodiments are particularly advantageous because large networked systems with multiple network assets are quickly and error-free commissioned using a workforce with basic skills that do not require networking fundamentals.

[0050] Regarding the illustrated embodiments described above, it should be understood that the various non-limiting embodiments described herein can be used alone, in combination, or selectively combined for a particular application. Furthermore, some features of the various non-limiting embodiments described above may be used without corresponding use of the other described features. Therefore, the foregoing description should be considered merely as an illustration of the principles, teachings, and exemplary embodiments of the invention, and not as a limitation thereof.

[0051] It should be understood that the above arrangement is merely an illustration of the application of the principles of the illustrated embodiments. Many modifications and alternative arrangements can be devised by those skilled in the art without departing from the scope of the illustrated embodiments, and the appended claims are intended to cover such modifications and arrangements.

Claims

1. A computer-implemented method for automatically generating network configurations that connect multiple network asset devices to a public network, comprising: Receives metadata related to each of the multiple network asset devices to be installed on a public network in the network configuration device; In the network configuration device, assign a defined functional group consisting of one or more network asset devices to each of the multiple network asset devices; as well as The network configuration device generates a Dynamic Host Configuration Protocol (DHCP) reservation table, which defines a functional group for each network asset device to configure a public network to implement a subnet mask for multiple network asset devices.

2. The computer-implemented method as described in claim 1, wherein, The metadata is received in the network configuration device by scanning a QR code associated with the network asset device, the QR code indicating the metadata.

3. The computer-implemented method of claim 1 further includes a number (N) IP addresses reserved by the network configuration device for use on the public network, wherein the number N is greater than the number of multiple network asset devices, for implementing future network configurations of network asset devices on the public network other than the multiple network asset devices.

4. The computer-implemented method as described in claim 1, wherein, Select a headend specified state for a designated network asset device in a specific function group, so that the network asset device designated as the headend unit is used to provide coordination for each network asset device in the specific function group. As a result, the network configuration device generates a list of each network asset device in each specific function group, and then uploads the list of network asset devices in each specific function group to the headend unit of the corresponding specific function group.

5. The computer-implemented method as described in claim 1, wherein, Select a multi-head designation state for network asset devices from the plurality of network asset devices, such that the network asset device designated as a multi-head unit is used to provide coordination for network asset devices in a plurality of functional groups.

6. A computer-implemented method for automatically providing network configurations for connecting multiple network asset devices to a public network, comprising: Use computer equipment to create a master function group, which will be associated with each of one or more location function groups; In a computer device, a type of system file is defined that corresponds to one or more specific functions to be performed among multiple network asset devices; The initial number of network asset devices to be associated with the main functional group is entered into the computer device to reserve multiple IP addresses corresponding to the initial number of network asset devices in the router for the public computer network; Define a function group file in a computer device that corresponds to a specific physical location in the main function group. One or more of the initial number of network asset devices will be associated with this function group file to perform the specific function of this type of system file. Enter the metadata related to the network asset device to be associated with the function group file in the computer device, wherein the metadata includes at least the MAC address of the network asset device, and assign the IP address from the reserved IP address to the MAC address of the network asset device; Once it is determined that all multiple network asset devices are associated with a specific function group file, a subnet mask is generated by a computer device for use by a router. This subnet mask contains at least the MAC address and assigned IP address of each of the initial number of network asset devices associated with the specific function group, so that it can operate within the main function group via a public computer network.

7. The computer-implemented method as described in claim 6, wherein, Each network asset device is equipped with a QR code that indicates the metadata of the network asset device, thereby allowing a scanning device associated with a computer device to scan the QR code to input the network asset device metadata.

8. The computer-implemented method as described in claim 7, wherein, After scanning the QR code, a role is assigned to the network asset device associated with the scanned QR role. This role is unique relative to the roles assigned to other network asset devices in the same functional group.

9. The computer-implemented method as described in claim 8, wherein, The QR code includes metadata that further identifies the serial number of the network asset device and the device indication type.

10. The computer-implemented method as described in claim 6, wherein, Select a headend designation state for a specified network asset device in a specific function group, such that the network asset device designated as the headend unit is used to provide coordination for each network asset device in the specific function group.

11. The computer-implemented method of claim 10, further comprising generating a list of each network asset device in each functional group by computer equipment of each functional group, the list including the IP address, system type identifier, device type identifier, operating role, and device name of each network asset device in a specific functional group, wherein, The list of each specific function group is uploaded to the specified network asset device at the head end of the specific function group.

12. The computer-implemented method as described in claim 6, wherein, Select a multi-header designation state for network asset devices in a specific function group, so that the network asset device designated as a multi-header unit can be used to provide coordination for all network asset devices in all function groups.

13. The computer-implemented method of claim 6, further comprising generating a DHCP reservation table for MAC addresses and assigned IP addresses for each of the initial number of network asset devices by the computer device, in a format compatible with routers, firewalls, and / or DHCP servers of a public computer network, for configuring routers, firewalls, and / or DHCP servers according to the DHCP reservation table.

14. The computer-implemented method as described in claim 13, wherein, The computer device electronically uploads the subnet mask and DHCP reservation table to the router, firewall, and / or DHCP server.

15. The computer-implemented method as described in claim 1, wherein, Reserving the number of IP addresses in the routers, firewalls, and / or DHCP servers also includes reserving an additional (N) number of IP addresses in the routers, firewalls, and / or DHCP servers to enable network asset devices beyond the initial number of network asset devices to be included in the main functional group.

16. A computer device for automatically generating network configurations that connect multiple network asset devices to a public network, comprising: Memory configured to store instructions; A processor configured to communicate with the memory, wherein the processor is configured to: Receive metadata related to each of the multiple network asset devices to be installed on a public network; Assign a defined group of functions consisting of one or more network asset devices to each of the multiple network asset devices; as well as Generate a Dynamic Host Configuration Protocol (DHCP) reservation table, which defines the configuration of a public network based on the functional groups defined for each network asset device to implement subnet masks for multiple network asset devices.

17. The computer device as claimed in claim 16, wherein, The metadata is received in the network configuration device by scanning a QR code associated with the network asset device, the QR code indicating the metadata.

18. The computer device of claim 16, further comprising a number (N) of IP addresses reserved by the network configuration device for use on the public network, wherein the number N is greater than the number of multiple network asset devices, for enabling future network configuration of network asset devices on the public network other than the multiple network asset devices.

19. The computer device as claimed in claim 16, wherein, Select a headend specified state for a designated network asset device in a specific function group, so that the network asset device designated as the headend unit is used to provide coordination for each network asset device in the specific function group. As a result, the network configuration device generates a list of each network asset device in each specific function group, and then uploads the list of network asset devices in each specific function group to the headend unit of the corresponding specific function group.

20. The computer device of claim 16, wherein, Select a multi-head designation state for network asset devices from the plurality of network asset devices, such that the network asset device designated as a multi-head unit is used to provide coordination for network asset devices in a plurality of functional groups.

Images