Patent ID: 12244628

DETAILED DESCRIPTION OF THE DISCLOSURE

Again, the present disclosure relates to systems and methods for building intelligence around IoT devices that can prioritize an attack attack sphere, such that scanning and protection can be focused on risky spheres before others that may be less at risk. The attack spheres include specific device types, vendors, geographic locations, demographics, or organizations. Priority based vulnerability scanning and protection is utilized along with the concept of attack spheres to define priority zones which may be unique. Priority computation based on trend analysis and predictive analysis is used to determine the vulnerability of specific devices and groups of devices. This will significantly reduce the attack exposure and ensures the proactive damage control.

Distributed Wi-Fi System

FIG.1is a network diagram of a distributed Wi-Fi system10with control via a cloud12service. The distributed Wi-Fi system10can operate in accordance with the IEEE 802.11 protocols and variations thereof. The distributed Wi-Fi system10includes a plurality of access points14(labeled as access points14A-14H), which can be distributed throughout a location, such as a residence, office, or the like. That is, the distributed Wi-Fi system10contemplates operation in any physical location where it is inefficient or impractical to service with a single access point, repeaters, or a mesh system. As described herein, the distributed Wi-Fi system10can be referred to as a network, a system, a Wi-Fi network, a Wi-Fi system, a cloud-based system, etc. The access points14can be referred to as nodes, access points, Wi-Fi nodes, Wi-Fi access points, etc. The objective of the access points14is to provide network connectivity to Wi-Fi client devices16(labeled as Wi-Fi client devices16A-16E). The Wi-Fi client devices16can be referred to as client devices, user devices, clients, Wi-Fi clients, Wi-Fi devices, etc.

In a typical residential deployment, the distributed Wi-Fi system10can include between 3 to 12 access points or more in a home. A large number of access points14(which can also be referred to as nodes in the distributed Wi-Fi system10) ensures that the distance between any access point14is always small, as is the distance to any Wi-Fi client device16needing Wi-Fi service. That is, an objective of the distributed Wi-Fi system10can be for distances between the access points14to be of similar size as distances between the Wi-Fi client devices16and the associated access point14. Such small distances ensure that every corner of a consumer's home is well covered by Wi-Fi signals. It also ensures that any given hop in the distributed Wi-Fi system10is short and goes through few walls. This results in very strong signal strengths for each hop in the distributed Wi-Fi system10, allowing the use of high data rates, and providing robust operation. Note, those skilled in the art will recognize the Wi-Fi client devices16can be mobile devices, tablets, computers, consumer electronics, home entertainment devices, televisions, IoT devices, or any network-enabled device. For external network connectivity, one or more of the access points14can be connected to a modem/router18, which can be a cable modem, Digital Subscriber Loop (DSL) modem, or any device providing external network connectivity to the physical location associated with the distributed Wi-Fi system10.

While providing excellent coverage, a large number of access points14(nodes) presents a coordination problem. Getting all the access points14configured correctly and communicating efficiently requires centralized control. This cloud12service can provide control via servers20that can be reached across the Internet and accessed remotely, such as through an application (“app”) running on a user device22. The running of the distributed Wi-Fi system10, therefore, becomes what is commonly known as a “cloud service.” The servers20are configured to receive measurement data, to analyze the measurement data, and to configure the access points14in the distributed Wi-Fi system10based thereon, through the cloud12. The servers20can also be configured to determine which access point14each of the Wi-Fi client devices16connect (associate) with. That is, in an example aspect, the distributed Wi-Fi system10includes cloud-based control (with a cloud-based controller or cloud service in the cloud) to optimize, configure, and monitor the operation of the access points14and the Wi-Fi client devices16. This cloud-based control is contrasted with a conventional operation that relies on a local configuration, such as by logging in locally to an access point. In the distributed Wi-Fi system10, the control and optimization does not require local login to the access point14, but rather the user device22(or a local Wi-Fi client device16) communicating with the servers20in the cloud12, such as via a disparate network (a different network than the distributed Wi-Fi system10) (e.g., LTE, another Wi-Fi network, etc.).

The access points14can include both wireless links and wired links for connectivity. In the example ofFIG.1, the access point14A has an example gigabit Ethernet (GbE) wired connection to the modem/router18. Optionally, the access point14B also has a wired connection to the modem/router18, such as for redundancy or load balancing. Also, the access points14A,14B can have a wireless connection to the modem/router18. The access points14can have wireless links for client connectivity (referred to as a client link) and for backhaul (referred to as a backhaul link). The distributed Wi-Fi system10differs from a conventional Wi-Fi mesh network in that the client links and the backhaul links do not necessarily share the same Wi-Fi channel, thereby reducing interference. That is, the access points14can support at least two Wi-Fi wireless channels—which can be used flexibly to serve either the client link or the backhaul link and may have at least one wired port for connectivity to the modem/router18, or for connection to other devices. In the distributed Wi-Fi system10, only a small subset of the access points14require direct connectivity to the modem/router18with the non-connected access points14communicating with the modem/router18through the backhaul links back to the connected access points14.

Distributed Wi-Fi System Compared to Conventional Wi-Fi Systems

FIG.2is a network diagram of differences in the operation of the distributed Wi-Fi system10relative to a conventional single access point system30, a Wi-Fi mesh network32, and a Wi-Fi repeater network33. The single access point system30relies on a single, high-powered access point34, which may be centrally located to serve all Wi-Fi client devices16in a location (e.g., house). Again, as described herein, in a typical residence, the single access point system30can have several walls, floors, etc. between the access point34and the Wi-Fi client devices16. Plus, the single access point system30operates on a single channel, leading to potential interference from neighboring systems. The Wi-Fi mesh network32solves some of the issues with the single access point system30by having multiple mesh nodes36, which distribute the Wi-Fi coverage. Specifically, the Wi-Fi mesh network32operates based on the mesh nodes36being fully interconnected with one another, sharing a channel such as a channel X between each of the mesh nodes36and the Wi-Fi client device16. That is, the Wi-Fi mesh network32is a fully interconnected grid, sharing the same channel, and allowing multiple different paths between the mesh nodes36and the Wi-Fi client device16. However, since the Wi-Fi mesh network32uses the same backhaul channel, every hop between source points divides the network capacity by the number of hops taken to deliver the data. For example, if it takes three hops to stream a video to a Wi-Fi client device16, the Wi-Fi mesh network32is left with only ⅓ the capacity. The Wi-Fi repeater network33includes the access point34coupled wirelessly to a Wi-Fi repeater38. The Wi-Fi repeater network33is a star topology where there is at most one Wi-Fi repeater38between the access point14and the Wi-Fi client device16. From a channel perspective, the access point34can communicate to the Wi-Fi repeater38on a first channel, Ch. X, and the Wi-Fi repeater38can communicate to the Wi-Fi client device16on a second channel, Ch. Y.

The distributed Wi-Fi system10solves the problem with the Wi-Fi mesh network32of requiring the same channel for all connections by using a different channel or band for the various hops (note, some hops may use the same channel/band, but it is not required), to prevent slowing down the Wi-Fi speed. For example, the distributed Wi-Fi system10can use different channels/bands between access points14and between the Wi-Fi client device16(e.g., Chs. X, Y, Z, A), and also, the distributed Wi-Fi system10does not necessarily use every access point14, based on configuration and optimization by the cloud12. The distributed Wi-Fi system10solves the problems of the single access point system30by providing multiple access points14. The distributed Wi-Fi system10is not constrained to a star topology as in the Wi-Fi repeater network33, which at most allows two wireless hops between the Wi-Fi client device16and a gateway. Also, the distributed Wi-Fi system10forms a tree topology where there is one path between the Wi-Fi client device16and the gateway, but which allows for multiple wireless hops, unlike the Wi-Fi repeater network33.

Wi-Fi is a shared, simplex protocol meaning only one conversation between two devices can occur in the network at any given time, and if one device is talking the others need to be listening. By using different Wi-Fi channels, multiple simultaneous conversations can happen simultaneously in the distributed Wi-Fi system10. By selecting different Wi-Fi channels between the access points14, interference and congestion are avoided. The server20through the cloud12automatically configures the access points14in an optimized channel hop solution. The distributed Wi-Fi system10can choose routes and channels to support the ever-changing needs of consumers and their Wi-Fi client devices16. The distributed Wi-Fi system10approach is to ensure Wi-Fi signals do not need to travel far—either for backhaul or client connectivity. Accordingly, the Wi-Fi signals remain strong and avoid interference by communicating on the same channel as in the Wi-Fi mesh network32or with Wi-Fi repeaters. In an example aspect, the servers20in the cloud12are configured to optimize channel selection for the best user experience.

Of note, the present disclosure for intelligent monitoring is not limited to the distributed Wi-Fi system10but contemplates any of the Wi-Fi networks10,30,32,33, with monitoring through the cloud12. For example, different vendors can make access points14,34, mesh nodes36, repeaters38, etc. However, it is possible for unified control via the cloud using standardized techniques for communication with the cloud12. One such example includes OpenSync, sponsored by the Applicant of the present disclosure and described at www.opensync.io/documentation. OpenSync is cloud-agnostic open-source software for the delivery, curation, and management of services for the modern home. That is, this provides standardization of the communication between devices and the cloud12. OpenSync acts as silicon, Customer Premises Equipment (CPE), and cloud-agnostic connection between the in-home hardware devices and the cloud12. This is used to collect measurements and statistics from the connected Wi-Fi client devices16and network management elements, and to enable customized connectivity services.

Cloud-Based Wi-Fi Management

Conventional Wi-Fi systems utilize local management, such as where a user on the Wi-Fi network connects to a designated address (e.g., 192.168.1.1, etc.). The distributed Wi-Fi system10is configured for cloud-based management via the servers20in the cloud12. Also, the single access point system30, the Wi-Fi mesh network32, and the Wi-Fi repeater network33can support cloud-based management as described above. For example, the APs34and/or the mesh nodes36can be configured to communicate with the servers20in the cloud12. This configuration can be through a software agent installed in each device or the like, e.g., OpenSync. As described herein, cloud-based management includes reporting of Wi-Fi related performance metrics to the cloud12as well as receiving Wi-Fi-related configuration parameters from the cloud12. The systems and methods contemplate use with any Wi-Fi system (i.e., the distributed Wi-Fi system10, the single access point system30, the Wi-Fi mesh network32, and the Wi-Fi repeater network33, etc.), including systems that only support reporting of Wi-Fi related performance metrics (and not supporting cloud-based configuration).

The cloud12utilizes cloud computing systems and methods abstract away physical servers, storage, networking, etc. and instead offer these as on-demand and elastic resources. The National Institute of Standards and Technology (NIST) provides a concise and specific definition which states cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. Cloud computing differs from the classic client-server model by providing applications from a server that are executed and managed by a client's web browser or the like, with no installed client version of an application required. Centralization gives cloud service providers complete control over the versions of the browser-based and other applications provided to clients, which removes the need for version upgrades or license management on individual client computing devices. The phrase SaaS is sometimes used to describe application programs offered through cloud computing. A common shorthand for a provided cloud computing service (or even an aggregation of all existing cloud services) is “the cloud.”

Example Server Architecture

FIG.3is a block diagram of a server200which may be used in the cloud12, in other systems, or standalone. The server200may be a digital computer that, in terms of hardware architecture, generally includes a processor202, input/output (I/O) interfaces204, a network interface206, a data store208, and memory210. It should be appreciated by those of ordinary skill in the art thatFIG.3depicts the server200in an oversimplified manner, and a practical embodiment may include additional components and suitably configured processing logic to support known or conventional operating features that are not described in detail herein. The components (202,204,206,208, and210) are communicatively coupled via a local interface212. The local interface212may be, for example, but not limited to, one or more buses or other wired or wireless connections, as is known in the art. The local interface212may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, among many others, to enable communications. Further, the local interface212may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.

The processor202is a hardware device for executing software instructions. The processor202may be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the server200, a semiconductor-based microprocessor (in the form of a microchip or chipset), or generally any device for executing software instructions. When the server200is in operation, the processor202is configured to execute software stored within the memory210, to communicate data to and from the memory210, and to generally control operations of the server200pursuant to the software instructions. The I/O interfaces204may be used to receive user input from and/or for providing system output to one or more devices or components. The user input may be provided via, for example, a keyboard, touchpad, and/or a mouse. System output may be provided via a display device and a printer (not shown). I/O interfaces204may include, for example, a serial port, a parallel port, a small computer system interface (SCSI), a serial ATA (SATA), a fibre channel, Infiniband, iSCSI, a PCI Express interface (PCI-x), an infrared (IR) interface, a radio frequency (RF) interface, and/or a universal serial bus (USB) interface.

The network interface206may be used to enable the server200to communicate on a network, such as the Internet. The network interface206may include, for example, an Ethernet card or adapter (e.g., 10BaseT, Fast Ethernet, Gigabit Ethernet, 10 GbE) or a wireless local area network (W LAN) card or adapter (e.g., 802.11a/b/g/n/ac). The network interface206may include address, control, and/or data connections to enable appropriate communications on the network. A data store208may be used to store data. The data store208may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, and the like), and combinations thereof. Moreover, the data store208may incorporate electronic, magnetic, optical, and/or other types of storage media. In one example, the data store208may be located internal to the server200, such as, for example, an internal hard drive connected to the local interface212in the server200. Additionally, in another embodiment, the data store208may be located external to the server200such as, for example, an external hard drive connected to the I/O interfaces204(e.g., SCSI or USB connection). In a further embodiment, the data store208may be connected to the server200through a network, such as, for example, a network-attached file server.

The memory210may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.), and combinations thereof. Moreover, the memory210may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory210may have a distributed architecture, where various components are situated remotely from one another but can be accessed by the processor202. The software in memory210may include one or more software programs, each of which includes an ordered listing of executable instructions for implementing logical functions. The software in the memory210includes a suitable operating system (O/S)214and one or more programs216. The operating system214essentially controls the execution of other computer programs, such as the one or more programs216, and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. The one or more programs216may be configured to implement the various processes, algorithms, methods, techniques, etc. described herein.

Example User Device Architecture

FIG.4is a block diagram of a user device300, which may be used for the user device22or the like. The user device300can be a digital device that, in terms of hardware architecture, generally includes a processor302, input/output (I/O) interfaces304, a radio306, a data store308, and memory310. It should be appreciated by those of ordinary skill in the art thatFIG.4depicts the user device300in an oversimplified manner, and a practical embodiment may include additional components and suitably configured processing logic to support known or conventional operating features that are not described in detail herein. The components (302,304,306,308, and302) are communicatively coupled via a local interface312. The local interface312can be, for example, but not limited to, one or more buses or other wired or wireless connections, as is known in the art. The local interface312can have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, among many others, to enable communications. Further, the local interface312may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.

The processor302is a hardware device for executing software instructions. The processor302can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the user device300, a semiconductor-based microprocessor (in the form of a microchip or chipset), or generally any device for executing software instructions. When the user device300is in operation, the processor302is configured to execute software stored within the memory310, to communicate data to and from the memory310, and to generally control operations of the user device300pursuant to the software instructions. In an embodiment, the processor302may include a mobile optimized processor such as optimized for power consumption and mobile applications. The I/O interfaces304can be used to receive user input from and/or for providing system output. User input can be provided via, for example, a keypad, a touch screen, a scroll ball, a scroll bar, buttons, a barcode scanner, and the like. System output can be provided via a display device such as a liquid crystal display (LCD), touch screen, and the like. The I/O interfaces304can also include, for example, a serial port, a parallel port, a small computer system interface (SCSI), an infrared (IR) interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, and the like. The I/O interfaces304can include a graphical user interface (GUI) that enables a user to interact with the user device300. Additionally, the I/O interfaces304may further include an imaging device, i.e., camera, video camera, etc.

The radio306enables wireless communication to an external access device or network. Any number of suitable wireless data communication protocols, techniques, or methodologies can be supported by the radio306, including, without limitation: RF; IrDA (infrared); Bluetooth; ZigBee (and other variants of the IEEE 802.15 protocol); IEEE 802.11 (any variation); IEEE 802.16 (WiMAX or any other variation); Direct Sequence Spread Spectrum; Frequency Hopping Spread Spectrum; Long Term Evolution (LTE); cellular/wireless/cordless telecommunication protocols (e.g., 3G/4G/5G, etc.); wireless home network communication protocols; proprietary wireless data communication protocols such as variants of Wireless USB; and any other protocols for wireless communication. The data store308may be used to store data. The data store308may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, and the like), and combinations thereof. Moreover, the data store308may incorporate electronic, magnetic, optical, and/or other types of storage media.

The memory310may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatile memory elements (e.g., ROM, hard drive, etc.), and combinations thereof. Moreover, the memory310may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory310may have a distributed architecture, where various components are situated remotely from one another but can be accessed by the processor302. The software in memory310can include one or more software programs, each of which includes an ordered listing of executable instructions for implementing logical functions. In the example ofFIG.3, the software in the memory310includes a suitable operating system (O/S)314and programs316. The operating system314essentially controls the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. The programs316may include various applications, add-ons, etc. configured to provide end-user functionality with the user device300. For example, example programs316may include, but not limited to, a web browser, social networking applications, streaming media applications, games, mapping and location applications, electronic mail applications, financial applications, and the like. In a typical example, the end user typically uses one or more of the programs316along with a network.

Attack Sphere

The present disclosure is focused on building an intelligent system that can prioritize attack attack spheres, such that scanning and protection can be focused on risky spheres before others. This will significantly reduce the attack exposure and ensures the proactive damage control.

An attack sphere is described as the impact scope of the attack in terms of time and space. The attack sphere can be based on a plurality of characteristics which include:Device types—a specific device type is impacted.Device vendors—one, more or all devices of a vendor are impacted.Device models—a specific model of a device type is impacted.Software version status:Recent software updates—a recent software update is impacted.No software update when one is required, which could be determined by date of last SW update, or determined by looking at what version of SW is available for the given device on the web and comparing those versions to the one currently on the device.Commonly used libraries— A commonly used library is impacted. A vulnerability is published in a commonly used library or component in IoT (e.g.: TCP stack, miniupnpd). All devices using the library are impacted.The distribution of the attacks is mostly focused on a geographic location, specific demographic, or organization.Time—Specific month of the year when the attack activity is high. Eg: political unrest, festive season, tax filing months etc.

An attack sphere can have a cascading effect on other spheres. In particular, some spheres or groups of devices may be shown to frequently transfer attacks laterally to other devices in the home. These spheres will be correlated to eventually identify the users that are most impacted or potential targets.

It will be appreciated that various embodiments of the present disclosure are adapted for building intelligence around IoT devices that can prioritize an attack attack sphere, although the present disclosure may be adapted to be used for any type of device and all such embodiments are contemplated herein.

Vulnerability Detection and Protection Method

The present disclosure provides the following method for vulnerability detection and protection of IoT devices. The method includes a current trend analysis system and an attack prediction system.

The current trend analysis system includes an on-going trend analysis based on the current vulnerability and attacks exploiting that vulnerability. Intelligent correlation of the vulnerabilities is based on factors such as corresponding attack history. This includes which sphere was most impacted by the vulnerability. Using well known clustering techniques, the present method can classify the vulnerability and attack data to build knowledge about the ongoing vulnerability and attack trends. These trends include general trends per attack sphere and specific vulnerability trends per attack sphere which include where the vulnerabilities are present and where the vulnerabilities are being compromised.

In addition to corresponding attack history, additional factors include ongoing attacks and correlation based on the trends.

The attack prediction system provides a predictive analysis system based on the historic data forecasting the spheres that are more likely and potential attack targets than others. The prediction system will forecast where future potential attacks might take place. This system takes advantage of attack history by building back-end analytics to identify which devices are highly prone to attacks. Additionally, a prediction algorithm is based on Machine Learning (ML) to predict which spheres are going to be potential targets of an attack.

The present system utilizes the combination of current trends in addition to the predictions to catch any emerging trend early before an attack might take place. For example, if an attack sphere is high-risk as per the prediction. Attack activities initiate in these spheres; However, the trend may still not be clear. In such cases, a predictive analysis will be leveraged to prioritize protection for these spheres.

The priority computation allows the system to prioritize spheres which may be identified as high-risk.FIG.5is a table showing different results based on trend502, prediction504, and the priority506given to a sphere based on the resulting trend502and prediction504findings. Generally, the priority computation may be based on a scoring system. The scoring system may combine many individual factors, and the combination of the individual factors may include a weighting of each of the factors based on their relative importance.

Priority Scanning and Protection

All of the devices300in the identified priority attack sphere will be scanned before others. It is likely that the users with attack spheres have additional devices300that may be targets of lateral attacks. Thus, all devices of these users will be scanned on priority. Additionally, scanning frequency will be increased for users in the attack sphere, and the scanning level will be increased (i.e., more ports to be scanned, more credentials to be checked).

In order to protect these devices300, additional security policies will be applied, blocking traffic on the vulnerable ports and services. Devices300can also be quarantined in order to prevent lateral attacks from taking place on additional devices300. The user of the devices300may additionally be advised and guided, for example, advised to take a device300offline, update software, etc.

The user and/or service provider can be informed of the scanning operations and outcomes in addition to the scanning prioritization. The user and/or service provider can also be informed of the benefits of the scanning prioritization, for example, how many scans were saved due to the knowledge of which devices300do not need to be scanned, or how much more frequently scans are taking place for high-risk devices300.

Cloud Service Providers (CSPs) can leverage the priority-based scanning system to effectively control the magnitude of the damage caused by a vulnerability compromise. CSPs can trigger intelligent vulnerability scans, and the protection can be prioritized for the users who are most vulnerable.

By focusing the vulnerability scanning, detection, and protection on high-risk spheres, the present system can significantly reduce the attack exposure, and ensure the proactive damage control. CSPs can use this intelligent prioritization method and provide improved protection to their users.

Detection and Protection Process

Again, the present disclosure relates to systems and methods for building intelligence around IoT devices that can prioritize an attack attack sphere (attack sphere), such that scanning and protection can be focused on risky spheres before others that may be less at risk. The attack spheres include specific device types, vendors, geographic locations, demographics, or organizations. Priority based vulnerability scanning and protection is utilized along with the concept of attack spheres to define priority zones which may be unique. Priority computation based on trend analysis and predictive analysis is used to determine the vulnerability of specific devices and groups of devices. This will significantly reduce the attack exposure and ensures the proactive damage control.

FIG.6is a flow chart of the Intelligent and proactive device vulnerability detection and protection process600of the present disclosure. The present correlation-based algorithm for improving the vulnerability scanning to provide improved proactive protection to consumer IoT users includes the following steps. Determining602attack threats for devices based on predictive analysis, as well as optional trend analysis. Assigning604priority to devices responsive to determining the threat to the devices. Scanning606devices based on the assigned priority, wherein devices in an identified priority attack sphere are one or more of scanned before other devices, scanned more frequently, and scanned at an increased level. Applying608additional security policies to devices in an identified priority attack sphere. And Informing610a user or service provider of the scanning operations and outcomes.

CONCLUSION

It will be appreciated that some embodiments described herein may include one or more generic or specialized processors (“one or more processors”) such as microprocessors; Central Processing Units (CPUs); Digital Signal Processors (DSPs): customized processors such as Network Processors (NPs) or Network Processing Units (NPUs), Graphics Processing Units (GPUs), or the like; Field Programmable Gate Arrays (FPGAs); and the like along with unique stored program instructions (including both software and firmware) for control thereof to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the methods and/or systems described herein. Alternatively, some or all functions may be implemented by a state machine that has no stored program instructions, or in one or more Application-Specific Integrated Circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic or circuitry. Of course, a combination of the aforementioned approaches may be used. For some of the embodiments described herein, a corresponding device in hardware and optionally with software, firmware, and a combination thereof can be referred to as “circuitry configured or adapted to,” “logic configured or adapted to,” etc. perform a set of operations, steps, methods, processes, algorithms, functions, techniques, etc. on digital and/or analog signals as described herein for the various embodiments.

Moreover, some embodiments may include a non-transitory computer-readable storage medium having computer readable code stored thereon for programming a computer, server, appliance, device, processor, circuit, etc. each of which may include a processor to perform functions as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory), Flash memory, and the like. When stored in the non-transitory computer-readable medium, software can include instructions executable by a processor or device (e.g., any type of programmable circuitry or logic) that, in response to such execution, cause a processor or the device to perform a set of operations, steps, methods, processes, algorithms, functions, techniques, etc. as described herein for the various embodiments.

Although the present disclosure has been illustrated and described herein with reference to preferred embodiments and specific examples thereof, it will be readily apparent to those of ordinary skill in the art that other embodiments and examples may perform similar functions and/or achieve like results. All such equivalent embodiments and examples are within the spirit and scope of the present disclosure, are contemplated thereby, and are intended to be covered by the following claims.