Patent Application
20240348493
The present disclosure relates generally to providing a troubleshooting trigger.
In computer networking, a wireless Access Point (AP) is a networking hardware device that allows a Wi-Fi compatible client device to connect to a wired network and to other client devices. The AP usually connects to a router (directly or indirectly via a wired network) as a standalone device, but it can also be an integral component of the router itself. Several APs may also work in coordination, either through direct wired or wireless connections, or through a central system, commonly called a Wireless Local Area Network (WLAN) controller. An AP is differentiated from a hotspot, which is the physical location where Wi-Fi access to a WLAN is available.
Prior to wireless networks, setting up a computer network in a business, home, or school often required running many cables through walls and ceilings in order to deliver network access to all of the network-enabled devices in the building. With the creation of the wireless AP, network users are able to add devices that access the network with few or no cables. An AP connects to a wired network, then provides radio frequency links for other radio devices to reach that wired network. Most APs support the connection of multiple wireless devices. APs are built to support a standard for sending and receiving data using these radio frequencies.
The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments of the present disclosure. In the drawings:
A troubleshooting trigger may be provided. A first computing device may provide, to a second computing device, data indicating a troubleshooting capability protocol. Next, first computing device may receive, from the second computing device, a troubleshooting request in accordance with the troubleshooting capability protocol. The first computing device may then perform the troubleshooting request in accordance with the troubleshooting capability protocol.
Both the foregoing overview and the following example embodiments are examples and explanatory only and should not be considered to restrict the disclosure's scope, as described and claimed. Furthermore, features and/or variations may be provided in addition to those described. For example, embodiments of the disclosure may be directed to various feature combinations and sub-combinations described in the example embodiments.
The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While embodiments of the disclosure may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the disclosure. Instead, the proper scope of the disclosure is defined by the appended claims.
Troubleshooting Wi-Fi issues may be challenging because the troubleshooter may only has a partial view of the scene. The Access Point (AP) may log elements that may include operational data (e.g., the time of a client message, its Received Signal Strength Indicator (RSSI), or Signal to Noise Ratio (SNR), etc.) and standard data (e.g., the details of the client frame and its various Information Elements (IEs)). The client device may perform mostly the same operations. Each side may then decide which events are beyond some normality threshold and should be logged to indicate an issue (e.g., excessive retries or a failure to complete a specific transaction).
In many cases, however, a user may signal issues while one or both sides did not detect any particular failure. In other cases, one side may detect a problem, but it's log may indicate that the other side failed to produce the expected answer. In both scenarios, the troubleshooting effort may end up in a dead-end with the support team left with the task of attempting to reproduce the issue. Accordingly, there may be a need for a process for the AP and the client device (i.e., a Station (STA)) to work together to address issues and facilitate troubleshooting scenarios. Embodiments of the disclosure may streamline the troubleshooting effort between a client device and an AP.
The plurality of APs and the plurality of client devices may use Multi-Link Operation (MLO) where they simultaneously transmit and receive across different bands and channels by establishing two or more links to two or more AP radios. These bands may comprise, but are not limited the 2 GHz band, the 5 GHZ band, the 6 GHz band, and the 60 GHz band.
Controller 105 may comprise a Wireless Local Area Network controller (WLC) and may provision and control coverage environment 110 (e.g., a WLAN). Controller 105 may allow first client device 130, second client device 135, and third client device 140 to join coverage environment 110. In some embodiments of the disclosure, controller 105 may be implemented by a Digital Network Architecture Center (DNAC) controller (i.e., a Software-Defined Network (SDN) controller) that may configure information for coverage environment 110 in order to provide a troubleshooting trigger.
The elements described above of operating environment 100 (e.g., controller 105, first AP 115, second AP 120, third AP 125, first client device 130, second client device 135, or third client device 140) may be practiced in hardware and/or in software (including firmware, resident software, micro-code, etc.) or in any other circuits or systems. The elements of operating environment 100 may be practiced in electrical circuits comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. Furthermore, the elements of operating environment 100 may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to, mechanical, optical, fluidic, and quantum technologies. As described in greater detail below with respect to
Method 200 may begin at starting block 205 and proceed to stage 210 where first AP 115 may provide, to first client device 130, data indicating a troubleshooting capability protocol. For example, first AP 115 and first client device 130 may signal to each other a cooperative troubleshooting protocol capability at association time. This may be signaled, for example, in a capability fields in an IE. Some client devices and APs may implement a full version of the troubleshooting protocol (e.g., selective logging as described below), others may implement a simplified version of the protocol (e.g., log everything or nothing), others may not implement the protocol (e.g., legacy clients).
From stage 210, where first AP 115 provides, to first client device 130, data indicating the troubleshooting capability protocol, method 200 may advance to stage 220 where first AP 115 may receive, from first client device 130, a troubleshooting request in accordance with the troubleshooting capability protocol. For example, at any time after association, first client device 130 or first AP 115 may trigger the troubleshooting protocol with a request/response exchange (e.g., an action frame). The exchange may include one or more elements used as the trigger, one or more thresholds, and one or more elements to log. For example, the triggers may include frame types 00, subtypes 0, 1, 2, 3 (management/association), the thresholds may include failure or delay>n ms”, and the elements to log may include frame type 00 and timestamps. The query may target one or more applications by characterizing the application (e.g., a tuple, Domain Name Service (DNS) response, package name, etc.). The exchange may include a single set of elements or contain a list. The exchange may be allowed to occur at any time and a request/response may augment or update a previous request/response.
The exchange may also include capability information. For example, some systems may be able to monitor frames (e.g., 802.11 frames), but not their payload, thus may have no application monitoring capability. Similarly, some systems may be able to allocate a monitoring buffer, thus allowing for the ability to monitor events that occurred before a failure was detected.
Once first AP 115 receives, from first client device 130, the troubleshooting request in accordance with the troubleshooting capability protocol in stage 220, method 200 may continue to stage 230 where first AP 115 may perform the troubleshooting request in accordance with the troubleshooting capability protocol. For example, at any point in time, one side may detect an issue of either of two types: i) a failure or ii) a performance threshold (i.e., delay>n ms). In case of failure, the detecting side may request the other side to log. In full protocol and monitoring buffer-capability cases, the detecting side may signal the failure type (e.g., based on the action frame described above in) and a timer (e.g., association failure, 600 ms past). When a monitoring buffer capability was not expressed, the same signaling may occur (e.g., without the timer), and the detecting side re-attempts the exchange, thus causing both sides to log the attempt. In the case of a performance threshold being reached, the detecting side may signal the target element (e.g., based on action frame described above in) along with a request to log.
In both cases, the other side may confirm that it starts logging. In an embodiment of the disclosure, the response may also include a flag signaling whether the responder also detected the flagged issue. In another embodiment, the request and/or the response may also include a logging timer that indicates the duration of the intended logging action.
In yet another embodiment (i.e., basic protocol implementation), each side may only be statically configured to log certain types of events without granularity). Thus the signaling may be limited to “issue detected, please log” for example.
At the end of the logging timer (e.g., either exchanged for full protocol implementers, or determined locally for basic implementations), the logging may stop and the corresponding side may signal the event to the other. The other side may also stop logging. In another embodiment, logging may stop early because of a triggering event, such as ‘buffer full’, or ‘issue no longer detected’ (e.g., for more than x seconds). In all cases, the stopping side may signal to the other side.
In one embodiment, the side that triggered the logging may request the log from the other side. In a variation of this embodiment, the logs may be sent to a location expressed by the requester. In all cases, both sides may confirm that the event logs are completed and thus that the event log, seen from both sides, is available for a support team.
As shown in
The failure may have been solved and first AP 115 and first client device 130 may be exchanging data again (stage 325). However, a performance threshold (i.e., delay>n ms) may have been reached (stage 330). Accordingly, first AP 115 may signal this to first client device 130, which elements to log (e.g., ABC), and when to start (e.g., now) the logging (stage 335). First client device 130 may signal to first AP 115 that logging has begun (stage 340). First AP 115 may signal to first client device 130 that logging has stopped and a what time it was stopped (stage 345). As illustrated by
Legacy client devices may not support the signaling described above. Thus, embodiments of the disclosure may allow for an AP to designate a third-party observer. The observer may be used to capture the responses from the AP (e.g., just like the client device would if it supported the protocol). The third-party observer may also be used as a source of a second opinion when the client device supports the cooperative troubleshooting protocol described above. Although the third-party observer may not have the same Radio Frequency (RF) view as the client device, it may still successfully log the exchange and thus collect valuable information. In both cases, when a third-party observer is involved, the signaling occurs between the AP and the third-party observer when the third-party observer has Over The Air (OTA) reachability to the AP. A third radio may be used as the third-party observer, thus suppressing the need for the OTA signaling.
Computing device 400 may be implemented using a Wi-Fi access point, a tablet device, a mobile device, a smart phone, a telephone, a remote control device, a set-top box, a digital video recorder, a cable modem, a personal computer, a network computer, a mainframe, a router, a switch, a server cluster, a smart TV-like device, a network storage device, a network relay device, or other similar microcomputer-based device. Computing device 400 may comprise any computer operating environment, such as hand-held devices, multiprocessor systems, microprocessor-based or programmable sender electronic devices, minicomputers, mainframe computers, and the like. Computing device 400 may also be practiced in distributed computing environments where tasks are performed by remote processing devices. The aforementioned systems and devices are examples, and computing device 400 may comprise other systems or devices.
Embodiments of the disclosure, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process. Accordingly, the present disclosure may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). In other words, embodiments of the present disclosure may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. A computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific computer-readable medium examples (a non-exhaustive list), the computer-readable medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, and a portable compact disc read-only memory (CD-ROM). Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
While certain embodiments of the disclosure have been described, other embodiments may exist. Furthermore, although embodiments of the present disclosure have been described as being associated with data stored in memory and other storage mediums, data can also be stored on or read from other types of computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or a CD-ROM, a carrier wave from the Internet, or other forms of RAM or ROM. Further, the disclosed methods' stages may be modified in any manner, including by reordering stages and/or inserting or deleting stages, without departing from the disclosure.
Furthermore, embodiments of the disclosure may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. Embodiments of the disclosure may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to, mechanical, optical, fluidic, and quantum technologies. In addition, embodiments of the disclosure may be practiced within a general purpose computer or in any other circuits or systems.
Embodiments of the disclosure may be practiced via a system-on-a-chip (SOC) where each or many of the element illustrated in
Embodiments of the present disclosure, for example, are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to embodiments of the disclosure. The functions/acts noted in the blocks may occur out of the order as shown in any flowchart. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
While the specification includes examples, the disclosure's scope is indicated by the following claims. Furthermore, while the specification has been described in language specific to structural features and/or methodological acts, the claims are not limited to the features or acts described above. Rather, the specific features and acts described above are disclosed as example for embodiments of the disclosure.
