INTERROGATION

Cross Reference To Related Applications

[0001] This application claims the benefit of U.S. Provisional Application No.

62/555,586 filed on September 7, 2017, the disclosure of which is incorporated by reference herein.

Technical Field

[0002] This disclosure relates to the field of secure connection of wireless networks, and more specifically to identifying the behavioral characteristics of wireless networks relating to security of the wireless networks requesting access to a secure local area networks (LAN).

Background

[0003] In most local area networks (LAN)s, there is typically continuous removal and entry of new devices, and networks. Even if the LAN had been secured from any intrusions and attacks from outside, the new devices and networks that connect to the LAN need not be secure and may provide a path-way for security breaches and cyber-attacks. Currently the IEEE 802.1 li and the Extensible Authentication Protocol (EAP) methods from the internet engineering task force (IETF) for wireless networks are the two standards that support secure wireless LAN deployments. These when implemented are expected to provide protection from security breaches and cyber-attacks on the secure WLANs that conform to 802.11 group of wireless networks. The two current security methods under 802.1 li and EAP for WLAN security typically only implement 802. IX access control with EAP-having transport level security (TLS) referred to as the 802. IX with EAP-TLS protocol for mutual authentication and performing a negotiation phase allowing for the granting of access based on Pre-Shared Keys (PSKs) or successful authentication through IEEE 802. lx exchanges. IEEE 802.1 li provides a Robust Security Network (RSN) with two new protocols: the 4-Way Handshake; and the Group Key Handshake. These utilize the authentication services and port access control described in IEEE 802. IX to establish and exchange the appropriate cryptographic keys. [0004] Figure 1 shows example components and actions (100) of 802. IX with EAP- TLS protocol. A new network or device designated supplicant (101) requests access to the network through the authenticator (102), which is a gateway or hot spot to the secure local area network (SLAN). The authenticator (102) responds to the supplicant (101) with an EAP protocol request to identify itself. The supplicant (101) provides EAP protocol identification response to the authenticator (102) which is passed on to the authentication server (103) which generate the necessary security keys or challenge to be sent to the supplicant (101). The authenticator sends the key using EAP protocol to the supplicant who responds to the challenge which when checked and accepted by the authentication server (103) result in a successful connection between the supplicant and (101) and the SLAN through the authenticator. This process of secure connection using IEEE 802.1 li provides for further security as explained based on the interaction between the access point (AP) which is the authenticator 202 and the supplicant station (STA) which is the client (201) using Figure 2. The current IEEE 802.1 li uses a four-way handshake to establish and ensure the secure and authenticated connection. The initial authentication process is carried out either using a pre-shared key (PSK), or following an EAP exchange through 802. IX (which generally requires the presence of an authentication server). This process ensures that the client station (STA) is authenticated with the access point (AP). After the PSK or 802. IX authentication, a shared secret key is generated, called the Pairwise Master Key (PMK). In a pre-shared-key network, the PSK is the PMK. If an 802. IX EAP exchange was carried out, the PMK is derived from the EAP parameters provided by the authentication server. The PMK is used by both the STA and AP to decrypt messages.

[0005] Figure 2 shows an example sequence of actions 200 used to generate an additional secure key, the pair wise transient key (PTK), and also the Group Temporal key used for multicast and broadcast messages to provide further protection for the paired master key (PMK) under the 802.1 li process.

[0006] A four-way handshake is used to establish the Pairwise Transient Key (PTK). The PTK is generated by concatenating the following attributes: PMK, AP nonce value (ANonce), STA nonce value (SNonce), AP MAC address, and STA MAC address. The product is then put through a pseudo random function. [0007] The actual messages exchanged during the handshake for generation of PTK are depicted in Figure 2 and explained below. All messages are sent as EAPOL-Key frames:

[0008] The AP (202) sends a nonce-value (ANonce) to the STA (201). The client STA (201) now has all the attributes to construct the PTK (215 a) in the first step of the process S211.

[0009] The STA sends its own nonce-value (SNonce) to the AP together with a Message Integrity Code (MIC), including authentication, which is really a Message Authentication and Integrity Code (MAIC), in the second step of the process S212.

[0010] The AP now constructs the PTK (215b) and the GTK using the information received and sends the GTK and a sequence number together with another MIC. This sequence number will be used in the next multicast or broadcast frame, so that the receiving STA can perform basic replay detection in the third step of the process S213.

[0011] The STA sends a confirmation to the AP as the fourth step and completing the process S214.

Brief Description of Drawings

[0012] The embodiments herein are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to "an" or "one" embodiment in this disclosure are not necessarily to the same embodiment, and they mean at least one. Also, in the interest of conciseness and reducing the total number of figures, a given figure may be used to illustrate the features of more than one embodiment, and not all elements in the figure may be required for a given embodiment.

[0013] Figure 1 illustrates a pictorial depiction 100 of conventional components and action of 802. IX with EAP-TLS protocol.

[0014] Figure 2 illustrates a pictorial representation 200 of conventional actions used to generate an additional secure key, to provide protection for the paired master key (PMK) under the 802.1 li process. [0015] Figure 3 illustrates an example block diagram 300 for explaining a secure local area network (SLAN) showing a sensor and a connected central console according an embodiment.

[0016] Figure 4 illustrates an example block diagram 400 for explaining an SLAN connected to known secure networks and devices for collection and consolidation of data and information for classification of networks and generation of query packages according to an embodiment.

[0017] Figure 5 illustrates an example block diagram 500 for explaining an SLAN connecting to a net-new network, the net-new network can be classified and queried to determine its operational security prior to enabling connectivity according to an

embodiment.

[0018] Figure 6 illustrates an example flow chart for explaining generation of classifications of known connecting networks and generation and storage of query packages for each classification from data and information collected and consolidated according to an embodiment.

[0019] Figure 7 illustrates an example flow chart for explaining classifying a new network requesting connection to the SLAN and choosing / generating a query package and using the same to evaluate the operational security of the new network prior to enabling connection to the SLAN according to an embodiment.

Detailed Description

[0020] Various embodiments and aspects will be described with reference to details discussed below, and the accompanying drawings will illustrate the various embodiments. The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of various embodiments. However, it is understood that embodiments disclosed herein may be practiced without these specific details. In certain instances, well-known or conventional details, such as circuits, structures, and techniques, are not described in order to provide a concise discussion of example embodiments. [0021] Reference in the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in conjunction with the embodiment can be included in at least one embodiment. The appearances of the phrase "in one embodiment" in various places in the specification do not necessarily all refer to the same embodiment.

[0022] The IEEE 802.11 standard when implemented generally results in a secure and authenticated connection between the SLAN and the requesting network. However, the inventors herein have recognized that in the implementation of the IEEE 802.1 li, the operational security of the new connecting network is typically not considered. This can result in the newly added devices and networks being cyber attackers posing as authentic devices and networks, or provide access to cyber attackers by not having the necessary security. Also by being within the secure LAN boundaries, these devices and networks, by themselves being unsecured, act as gateways for access by attackers making the secure LAN prone to cyber-attacks.

[0023] Hence it will be of great value to have a means of checking the operational security of devices and networks that are to be accepted as part of the secure LAN (SLAN) before the connection requests are accepted in the boundaries of the SLAN, in terms of network connectivity and accessibility, are extended to cover these new connected devices and networks.

[0024] The present disclosure provides a network and data security testing app for mobile devices (e.g., mobile phone, tablet devices), which are connected to the Internet via a wireless network. The app downloads and stores one or more network security or data loss test cases from a centralized server, which are then executed on the mobile device. For example, a test case attempts to access predetermined web pages through the wireless network and then determines whether access was granted. In another example, a test case attempts to transmit sensitive data through the network. Results of the test case are displayed on the mobile device and uploaded to the centralized server. The network and data security testing app also identifies whether access was granted to web pages hosting botnets, malicious web exploits, malicious web obfuscation, malicious iframe redirection, and malware files.

[0025] The disclosure herein provides for: [0026] The collection and compilation of characteristic queries and response data from trusted networks comprising a plurality of elements, for generating a characterization query framework for new networks/ device requesting connection.

[0027] Use of the compiled queries to extract responses from the network / device.

[0028] Using a cloud based security monitor for comparing, analyzing and identifying deviations from norm in the responses.

[0029] Use of a pseudo-network to emulate a real network so that the connection query responses between the pseudo network and the new network requesting connection can be extracted for analysis for classification of the operational security of the new network.

[0030] The analysis methods used above including data science approaches, correlation analysis and classification methods on a network level to classify the whole network rather than any single element of the network.

[0031] Determining the security level of the network to be connected from the result of the analysis of the deviations and enabling or refusing connection request based on the findings, or disconnecting the unapproved connection.

[0032] The embodiments herein include systems and methods for providing security to an enterprise local area network (LAN). Typically, the Enterprise LAN will have access and operational security established and exist as a monitored space, to prevent attacks by cyber attackers, making it a Secure LAN (SLAN). A typical enterprise network which forms the SLAN will have a plurality of elements, such as servers, mobile devices, storage devices, peripheral devices, display systems, other processing and communication elements connected as the secure network. The embodiments herein cover systems and methods for ensuring the security of the SLAN by pre-vetting and identifying the security characteristics and actions of any new wireless networks that are identified in the vicinity and that tries to connect to the SLAN. The disclosure herein provides the capability for identification and classification of IEEE 802.11 wireless networks by using a monitoring sensor system within and managed by a centralized cloud. The monitoring sensors interrogate the network mimicking the behavior of known platforms, such as an end-user's workstation or mobile device followed by random actions simulating a human person. The response characteristics of the wireless network including the behavior patterns relating to the LAN system and human behavior are collected. The security system uses methods of

classification provided through analysis of the collected information using methods including data science approaches, correlation analysis, and machine learning classification methods to determine the pre-vetting result. The analysis results in a determination of a security classification of the newly detected wireless network. Based on this security classification which provides the operational security status of the network trying to connect to the secure LAN, decisions can be made to allow or disallow such connection request.

[0033] In one embodiment, for establishing connections normal access point (AP) of a network there is a negotiation process leading to connection. The AP typically broadcasts its information as data frames which include the extended service set identification (ESSID) of the network or its name, reachability address or the hardware address of the Wi-Fi chip set which is called the basic service set identification (BSSID) and capabilities (CAP). Any Wi- Fi client or station (STA) needing to connect to the network use this data to get connected. In the case of a SLAN the IEEE 802.1 li security protocol is used by the STA and the AP to ensure a secure connection. The IEEE 802.1 li security specification standard uses secure keys and EAP transfer protocols for achieving a secure connection between the STA and AP. As discussed previously the IEEE 802.1 li standard does not typically check or ensure operational security of the STA to check if the connecting STA is an operationally secure device or SLAN and not vulnerable to attackers. By virtue of the arrangements disclosed herein, it is possible to correct the above-mentioned limitation of the 802.1 li security standard.

[0034] Figure 3 is a block diagram for explaining an enterprise network that is a secure local area network (SLAN) 300 according to an embodiment herein. The enterprise network includes a plurality of elements as is well known and therefore not explicitly shown in Figure 3, that may include servers, mobile devices, storage devices, peripheral and I/O devices, communication devices etc. connected together. It may also have a plurality of access points enabling the secure elements inside the SLAN to interact with the outside world. Figure 3 shows the secure LAN (SLAN) (301) having a plurality of access points (AP) (302-x). In one embodiment, sensor (303) is associated with each of the APs (302-x) of the SLAN (301) and is linked to a central console (CC) (311) in the cloud (310). The sensor (303) is enabled to collect 802.1 lWi-Fi data frames that enable unique identification indicators of any networks, including devices, that connect to the AP (302-x). The collected data frames also comprise normal queries and responses between the SLAN (301) and the networks normally connecting to the SLAN (301) via the AP (302-x). The data and information collected by the sensor (303) are collated and delivered to the CC (311) in the cloud (310) over a communication link (304). Typically, the SLAN (301) uses a plurality of sensors (303) to ensure ease of data collection and transfer of the collected and collated information to the CC (311). The information and data received is stored in a historic database (312) in the cloud (310) which is continuously up dated by the CC (311) as new data is received. Further the CC (311) continuously analyzes the information and Data of interactions and develops a set of potential markers for classification of all the networks connecting to the SLAN (301). The classification uses system and human behavior and interactions received as part of the connection and handshake process and the set of queries and answers received, that point to potential markers during and after connection. These are analyzed to generate a classification of the requesting network, using data science approaches, correlation analysis and machine learning.

[0035] Figure 4 shows the block diagram 400 for explaining connection of known secure networks, including devices, (401) (402) (403) connecting to the SLAN (301) via wireless 802.11 connections (404-1 to 404-3). The sensor (303) associated with and coupled to the CC (311), for example over communication link (304), collects the queries and responses during the regular connection of these secure networks (401 to 403). From the information and data of interactions collected from the known secure networks (401, 402) (403) connecting to the SLAN (301), the central console (311) generates query packages

(410) of the regular command/result behaviors. The command /behaviors comprise various requests and responses from internet protocols such as Domain Name Server (DNS), Hypertext Transfer Protocol (HTTP), TCP/UDP services, and other consistent behavior tokens. Additional information collected and analyzed and included in packages comprise attributes of similar AP, such as 802. IX public certificates, honeypot canary data such as DNS hostnames, usernames and passwords, ESSID, and any additional data as-specified by third parties. These query/ response packages (410-1 to 410-4) are saved in a query database

(411) associated with the SLAN (301) for use by the sensor (303) during evaluation of the operational and peripheral security of any new networks as they try to engage with the SLAN (301). [0036] Figure 5 is a view for explaining conditions 500 when a new previously unknown network (501) tries to connect to an SLAN (e.g., 301) at an AP using 802.11 wireless connection (504). The connection request is identified by the sensor (303) and flagged. The initial information and data from the flagged net-new network (501) are collected by the sensor during the 802.11 handshake for secure connection and sent to the CC (311) for comparison to the historic data and identification of potential markers for classification. Once a classification of the new network (501) is established, the CC (311) checks the canned stored query/answers package (401 to 404) for the identified

classification of the network, and based on the availability of the query package (410-n) in the database (411) the CC (311) chooses a canned query package (410-n) from the data base or generates a new query package (410-n) for the new classification to be provided to the sensor (303) to evaluate the operational security of the new network (501).

[0037] Once the query package (410-n) of requests and responses has been delivered to the sensor (303), the sensor (303) is requested to use the defined query package (410-n) to evaluate the new network (501). The sensor (303) with the help of the central console (311) establishes a pseudo-network with a client STA having a MAC address (510) (e.g., ac:bc:32:9f:4d: lc) that is similar to a known STA MAC address of network (401) in the neighborhood (such as ac:bc:32:9f:4d:0c). The generated STA MAC address (510) (e.g., ac:bc:32:9f:4d: lc) is used by the sensor (303) to engage with the new wireless

network(501), to establish connectivity to it. In the case of networks protected by IEEE 802. lx standard protocol the sensor (303) attempts to establish login authentication using credentials generated by randomization or provided by third party data.

[0038] Once connectivity is established to the new network (501) by the sensor (303) additional addressing services such as TCP/IP DHCPv4, TCP/IP DHCPv6 or other addressing services are used to obtain network-based identifiers to allow connectivity to known services. The sensor (303) now uses the packaged query to interrogate the new network (501) and record the results. These received results (511) are passed on to the CC (311) as received or with additional modifications based on the information collected. Once the package of queries is completed and results (512) have been collected, they are reviewed by the CC (311) and compiled into a new query package, which is used to update the query packages in the database 411. The result of the review is used to decide if the requesting network (501) is operationally secure to be connected to the SLAN (301). The CC (311) also creates a security summary for the network (501) in the historic database for any further review and processing.

[0039] Figures 3-5 are merely examples of particular implementations and are merely intended to illustrate the types of components that may be present in various networks. Note that while the networks are illustrated with various components, it is not intended to represent any particular architecture or manner of interconnecting the components; as such details are not germane to embodiments herein. It will also be appreciated that networks which have fewer components or perhaps more components may also be used with embodiments herein.

[0040] Figure 6 is an example flow chart 600 for explaining classification of networks and generation of query packages suitable to interrogate the networks under each classification for their operational security. In this regard, the following embodiments may be described as a process 600, which is usually depicted as a flowchart, a flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed. A process may correspond to a method, a procedure, etc. Process 600 may be performed by processing logic that includes hardware (e.g., circuitry, dedicated logic, etc.), software (e.g., embodied on a non-transitory computer readable medium), or a combination thereof.

[0041] At block S6001, a sensor (303) identifies known secure networks (401 and 402) including devices (403) that connect using 802.11 wireless means to the access points (302- x) of the Secure local area network (SLAN) (301).

[0042] At block S6002, sensor (303) collects data and information relating to the hand shake and post handshake queries & responses between the SLAN (301) and each of the networks (401 to 403) during their connection process.

[0043] At block S6003, sensor (303) sends the collected data and information generated during the connection transaction between each of the networks (401 to 403) and the SLAN (301) to a central console (311) in the cloud (310) for compilation and evaluation. [0044] At block S6004, central console (311) receives the data and information from the sensor (303) for each of the connecting networks (401 to 403) and consolidates the data and information, and stores it in a historic data base (312) which is continuously up dated with received data and information.

[0045] At block S6005, central console (311) analyzes the received information and data to identify markers for classification of the networks (401 to 403) connecting to the SLAN (301).

[0046] At block S6006, central console (311) using data science approaches, correlation analysis and machine learning, generates classification groups based on the markers identified, for networks (401 to 403) connecting to the SLAN (301).

[0047] At block S6007, central console (311) further generates query packages (410-1 to 410-4) comprising queries and responses for each classification group from the data and information collected from the secure networks (401 to 403) and the saved in the historic data and information saved in the historic database (312).

[0048] At block S6008, generated query packages (410-1 to 410-4) are saved in a query database (411) associated with the sensor (303) of the SLAN (301) by the central console (311), for conducting interrogation of any new network (501) that fall within the classifications already identified, for evaluating their operational security status as the new network tries to connect to the SLAN (301).

[0049] Figure 7 is an example flow chart 700 for explaining identifying, classifying and interrogating a net-new network trying to connect to the SLAN by 802.11 wireless means, using query packages for determining the new network's operational security status; and based on the result allowing or denying the connection to the SLAN. In this regard, the following embodiments may be described as a process 700, which is usually depicted as a flowchart, a flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. A process is terminated when its operations are completed. A process may correspond to a method, a procedure, etc. Process 700 may be performed by processing logic that includes hardware (e.g., circuitry, dedicated logic, etc.), software (e.g., embodied on a non-transitory computer readable medium), or a combination thereof.

[0050] At block S7001, a net-new network (501) requests connection through an access point (302-x) of the SLAN (301) using 802.11 wireless means.

[0051] At block S7002, sensor (303) identifies and flags the connection request, and collects data and information during the handshake and the secure pre-connection period.

[0052] At block S7003, the collected data and information are sent by the sensor (303) to the central console (311) in the cloud (310) for comparison to the historic data saved in the historical database (312) and identification of any available markers for classification of the new network (501).

[0053] At block S7004, the central console (311) checks the available markers for classification against stored classifications in the historic database (312) to see if the classification markers of the new network matches any existing classification. If the new network (501) is found to fall into an existing classification the next three steps are eliminated, but if the network is not identified by the central console (311) as falling into an existing classification, then the following three steps are initiated.

[0054] At block S7005, the central console generates a new classification for the network based on the identified markers from the data and information collected by the sensor (303).

[0055] At block S7006, based on the information and data collected by the sensor (303) and sent to the central console (311) and any relevant data in the historic data base (312) the central console (311) generates a new query package (410-n) for interrogation of the new network (501) and networks of the new classification.

[0056] At block S7007, the generated new query package (410-n) is stored in the query database (411) associated with the SLAN (301), referencing the new classification.

[0057] At block S7008, the central console (311) requests the sensor (303) to extract the query package (410-n) for the classification of the new network (510) from the query database (411) for evaluation of the operational security of the new network (501) requesting connection to the SLAN (301).

[0058] At block S7009, sensor (303) establishes a new pseudo-network (510) with a STA MAC address resembling that of a nearby trusted network (401) to directly engage with the new network (501) and establishes an authenticated connectivity with it, with handshake and secure connectivity.

[0059] At block S7010, sensor (303) once direct connection is established uses additional addressing services to get connected to known services, and using the queries and answers in the selected query package (410-n) interrogates the new network.

[0060] At block S7011, the additional data and information from the connection to the new network (501) and results of the interrogation are collected by the central console sensor (303) and sent to the central console (311) to evaluate the operational security of the new network.

[0061] At block S7012, the data and information collected from the new connection process to the pseudo-network (510) and the results of the interrogation are used by the central console (311) to update the query package (410-n) saved in the query database (411) for the new classification.

[0062] At block S7013, the result of the operational security evaluation is sent by the central console (311) to the sensor (303) of the SLAN 9301) which, based on the acceptability or not of the evaluation enables or denies the connection request of the new network (501) to the SLAN (301).

[0063] The processes described herein (e.g., processes 600 and 700) are not limited to the specific examples described. For example, processes 600 and 700 are not limited to the specific processing orders of Figures 6 and 7, respectively. Rather, any of the processing blocks of these figures may be re-ordered, combined or removed, performed in parallel or in serial, as necessary, to achieve the results set forth above. The processing blocks (for example, in the process 600 and the process 700) associated with implementing the system may be performed by one or more programmable processors executing one or more computer programs to perform the functions of the system. All or part of the system may be implemented as, special purpose logic circuitry (e.g., an FPGA (field-programmable gate array) and/or an ASIC (application-specific integrated circuit)). All or part of the system may be implemented using electronic hardware circuitry that include electronic devices such as, for example, at least one of a processor, a memory, a programmable logic device or a logic gate. Further, processes 600 and 700 can be implemented in any combination hardware devices and software components.

[0064] The processes described herein (e.g., process 600 and process 700) are not limited to use with the hardware and software of Figures 3 to 5; they may find applicability in any computing or processing environment and with any type of machine or set of machines that is capable of running a computer program. The processes described herein may be implemented in hardware, software (including computer code stored on a computer- readable medium, such as a hard drive or system memory), or a combination of the two. The processes described herein may be implemented in computer programs executed on programmable computers/machines that each includes a processor, a non-transitory machine-readable medium or other article of manufacture that is readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices. Program code may be applied to data entered using an input device to perform any of the processes described herein and to generate output information.

[0065] Embodiments of the PS and PPS may be implemented, at least in part, via a computer program product, (e.g., in a non-transitory machine-readable storage medium such as, for example, a non-transitory computer-readable medium), for execution by, or to control the operation of, data processing apparatus (e.g., a programmable processor, a computer, or multiple computers). Each such program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. However, the programs may be implemented in assembly or machine language. The language may be a compiled or an interpreted language and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network. A computer program may be stored on a non-transitory machine-readable storage medium that is readable by a general or special purpose programmable computer for configuring and operating the computer when the non-transitory machine-readable medium is read by the computer to perform the processes described herein.

[0066] For example, the systems and processes described herein may also be implemented as a non-transitory machine-readable storage medium having stored thereon instructions which program a processor to perform some or all of the operations described above. The non-transitory machine-readable storage medium may be configured with a computer program, where upon execution, instructions in the computer program cause the computer to operate in accordance with the processes. A non-transitory machine-readable medium may include but is not limited to a hard drive, compact disc, flash memory, nonvolatile memory, volatile memory, magnetic diskette and so forth but does not include a transitory signal per se. In other embodiments, some of these operations might be performed by specific hardware components that contain hardwired logic. Those operations might alternatively be performed by any combination of programmable computer components and fixed hardware circuit components.

[0067] The terms "computer-readable storage medium" and "machine-readable storage medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The terms "computer-readable storage medium" and "machine-readable storage medium" shall also be taken to include any medium that is capable of storing or encoding a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure. The terms

"computer-readable storage medium" and "machine-readable storage medium" shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, or any other non-transitory machine-readable medium.

[0068] While the present disclosure has been described in terms of embodiments, those of ordinary skill in the art will recognize that the invention is not limited to the

embodiments described, but can be practiced with modification and alteration within the spirit and scope of the appended claims. The description is thus to be regarded as illustrative instead of limiting. There are numerous other variations to different aspects of the invention described above, which in the interest of conciseness have not been provided in detail. Accordingly, other embodiments are within the scope of the claims.