Enhanced radio environment reporting

Abstract

Devices and methods are provided for enhanced wireless environment reporting. 802.11k reporting provides information that can have limited functionality because they do not provide extended details that can be beneficial to network infrastructure. Enhanced wireless environment reporting allows network devices and client devices to request wireless environment reporting (WER) based on several enhanced parameters. A device, such as a network device or a client device, generates a WER request including at least one of a condition, a peer-to-peer (P2P) specification, a non-IEEE 802.11 specification, or an element restriction, and sends the WER request to another device, such as a client station. The other device generates a WER with the requested enhanced information and sends it to the device. The information included in the WER report can be processed and used to perform network analysis, network management tasks, and other functions that are useful to network infrastructure.

Description

Technical Field

[0001] This disclosure relates to communication networks. More specifically, this disclosure relates to enhanced wireless environment reporting for optimizing wireless network management.

[0002] Cross-references to related applications This application claims priority to U.S. Patent Application No. 18 / 917,963, filed October 16, 2024, which claims priority to Indian Provisional Patent Application No. 202341089516, filed December 28, 2023, which is incorporated herein by reference in its entirety. Background Technology

[0003] The IEEE 802.11k standard enhances the ability of wireless networks (particularly wireless local area networks, WLANs) to manage client devices seamlessly switching between access points. Client devices can roam from one access point to another when experiencing weak signals. Roaming decisions can be based on various factors, including, for example, received signal strength and the availability of access points on the same or other networks that the client device has previously joined or configured to join automatically. The 802.11k standard helps client devices quickly identify adjacent access points available for roaming and roam between them more rapidly, ensuring smoother handovers and minimizing packet loss during transitions. This is particularly beneficial for applications such as Voice over Internet Protocol (VoIP), where performance is sensitive to roaming latency.

[0004] Client devices that support the IEEE 802.11k standard (also known as "11k-capable client devices") can request neighbor reports from their current access point. These neighbor reports include information about known neighboring access points that are roaming candidates. The neighbor report can include a list of neighboring access points, also known as a "neighbor list." 802.11k neighbor reporting improves the roaming experience for client devices by enabling them to make more informed decisions about when and where to roam, which helps optimize network performance and ensures smoother handovers between access points.

[0005] The 802.11k standard also allows access points to request information from one of their client devices, for example, in the form of an 802.11k beacon report, requesting the client device (actively or passively) to scan one or more channels or frequency bands and report the access points detected in those channels or frequency bands. Access points can also request client devices to share only the results of previous or most recent scans. Client devices can be requested to report all detected access points associated with any Service Set Identifier (SSID), or only the single SSID associated with the client device. 802.11k beacon reports can primarily provide a view of the wireless environment from the client device's perspective. However, because 802.11k reports are designed solely for roaming decisions, the limited information they provide may only help a site or client device find the next optimal access point, without providing extended information useful to the network infrastructure and potentially helpful to the site or client device in several other dimensions. Summary of the Invention

[0006] This document describes apparatus and methods for enhancing wireless environment reporting to optimize wireless network management, according to embodiments of the present disclosure.

[0007] In many embodiments, a network device includes a processor, a network interface controller configured to provide access to a network, and a memory communicatively coupled to the processor. The memory includes network management logic configured to: generate a wireless environment report request, send the generated wireless environment report request, and receive a wireless environment report based on the sent wireless environment report request. The wireless environment report request includes at least one of conditions, peer-to-peer (P2P) specifications, non-IEEE 802.11 specifications, or element limitations.

[0008] In various embodiments, the wireless environment report request includes conditions.

[0009] In several embodiments, the wireless environment report request is configured to indicate an excluded service set identifier (SSID).

[0010] In a further embodiment, the wireless environment report request is configured to indicate the SSID and the conditions associated with that SSID.

[0011] In more embodiments, the wireless environment report request is configured to indicate at least one of the channels or frequency bands.

[0012] In further embodiments, the wireless environment reporting request is also configured to instruct the reporting of the local SSID on at least one of the indicated channels or frequency bands.

[0013] In further embodiments, the wireless environment report request is also configured to instruct the reporting of a missing neighbor SSID on at least one of the indicated channels or frequency bands.

[0014] In further embodiments, the wireless environment reporting request is also configured to instruct: based on the detection of a local SSID on at least one of the indicated channels or frequency bands, to report all local SSIDs on at least one of the indicated channels or frequency bands.

[0015] In various embodiments, the wireless environment reporting request is also configured to instruct that all local SSIDs be reported on at least one of the indicated channels or frequency bands, based on the fact that no local SSID was detected on at least one of the indicated channels or frequency bands.

[0016] In several embodiments, the wireless environment report request is also configured to indicate the results of a standards-based evaluation.

[0017] In many embodiments, standards-based evaluation includes one or more logical operations.

[0018] In an additional embodiment, the wireless environment reporting request includes P2P technical specifications.

[0019] In several additional embodiments, the wireless environment report request is configured to indicate the number of reported P2P pairs.

[0020] In many additional embodiments, wireless environment reporting requests include non-IEEE 802.11 technical specifications.

[0021] In a further embodiment, the wireless environment report request is configured to indicate at least one of the channels or frequency bands.

[0022] In yet another embodiment, the wireless environment report request includes element restrictions.

[0023] In an additional embodiment, a wireless environment report request is sent to the client device, and the wireless environment report is received from the client device.

[0024] In a further embodiment, a client device includes a processor, a network interface controller configured to provide access to a network, and a memory communicatively coupled to the processor. The memory includes network management logic configured to generate a wireless environment report and transmit the wireless environment report. The wireless environment report is associated with at least one of conditions, P2P technical specifications, non-IEEE 802.11 technical specifications, or element limitations.

[0025] In many further embodiments, the network management logic is also configured to receive wireless environment report requests. These requests include at least one of conditions, P2P technical specifications, non-IEEE 802.11 technical specifications, or element restrictions. The wireless environment report is generated based on the received wireless environment report request.

[0026] In various other embodiments, a client device includes a processor, a network interface controller configured to provide access to a network, and a memory communicatively coupled to the processor. The memory includes network management logic configured to: generate a wireless environment report request, send the generated wireless environment report request to another client device via a P2P link, and receive a wireless environment report based on the sent wireless environment report request from the other client device via a P2P link.

[0027] Other objects, advantages, novel features, and further scope of this disclosure will be set forth in part in the detailed description which follows, and in part will become apparent to those skilled in the art upon reviewing the following, or may be learned by practice of this disclosure. Although the foregoing description contains many specific details, these should not be construed as limiting the scope of this disclosure, but rather as providing only an illustration of some currently preferred embodiments of the disclosure. Therefore, various other embodiments are possible within its scope. Consequently, the scope of this disclosure should not be determined by the embodiments shown, but rather by the appended claims and their equivalents. Attached Figure Description

[0028] The above and other aspects, features and advantages of several embodiments of this disclosure will become more apparent from the following description, presented in conjunction with the following figures.

[0029] Figure 1 These are schematic diagrams of wireless local area network systems according to various embodiments of the present disclosure; Figure 2 This is a conceptual network diagram of various environments in which network management logic according to various embodiments of this disclosure can operate on multiple network devices; Figure 3 This is a schematic block diagram illustrating a wireless environment for optimizing wireless network management through enhanced wireless environment reporting, according to various embodiments of the present disclosure. Figure 4 This is a flowchart depicting a process for enhanced wireless environment reporting from the access point's perspective, according to various embodiments of this disclosure. Figure 5 This is a flowchart depicting a process for enhanced wireless environment reporting from a site perspective according to various embodiments of the present disclosure; Figure 6This is a flowchart depicting a process for enhanced wireless environment reporting from a site perspective based on the detection of a local service set identifier (SSID) according to various embodiments of the present disclosure; Figure 7 This is a flowchart depicting a process for enhanced wireless environment reporting between peer client devices according to various embodiments of the present disclosure; and Figure 8 It is a conceptual block diagram of a device capable of executing components and logic for implementing the functions and embodiments described above.

[0030] Throughout the accompanying figures, corresponding reference characters indicate the corresponding components. Elements in the figures are shown for simplicity and clarity and are not necessarily drawn to scale. For example, the dimensions of some elements may be emphasized relative to others to facilitate understanding of the various embodiments currently disclosed. Furthermore, common but well-known elements that are useful or necessary in commercially viable embodiments are generally not depicted to provide a less obstructed view of the various embodiments of this disclosure. Detailed Implementation

[0031] In response to the aforementioned issues, this paper discusses devices and methods for enhancing wireless environment reporting to optimize wireless network management. Wireless environment reporting can refer to reports presenting information about the wireless environment, including sites (referred to herein as "STAs"), access points, client devices, etc. These reports can provide extended information useful to network infrastructure and can aid in network analysis, in addition to facilitating intelligent roaming decisions. Reports may include, for example, 802.11k neighbor reports, 802.11k beacon reports, and other conditional reports. The information contained in these reports can be processed and used to perform network analysis, network management tasks, and other functions useful to the network infrastructure.

[0032] The IEEE 802.11k standard allows STAs (Standing Points), including client devices, to request information about neighboring access points (typically on the same Extended Service Set, "ESS") from their access points in the form of 802.11k neighbor reports to aid in intelligent roaming decisions. When a client device requests a report from an access point using the 802.11k standard (e.g., an 802.11k neighbor report), the access point can send information to the client device, including, for example, the access point's Basic Service Set Identifier (BSSID), Service Set Identifier (SSID), channel information, max / min information, etc. 802.11k neighbor reports can be configured to assist client devices in making informed roaming decisions by providing information about neighboring access points within the same or different Basic Service Sets (BSSs) that the client device can detect. The information provided in an 802.11k neighbor report may include, for example, the neighboring access point's BSSID, signal strength, channel information, and other network characteristics. 802.11k neighbor reports can be used by client devices to determine the optimal access point to connect to based on network conditions.

[0033] The 802.11k standard also allows access points to request information from one of their client devices, for example, in the form of an 802.11k beacon report, requesting the client device (actively or passively) to scan one or more channels or frequency bands and report the access points detected in those channels or frequency bands. Access points can also request client devices to share only the results of previous or most recent scans. A client device can be requested to report all detected access points associated with any SSID, or only a single SSID associated with that client device. 802.11k beacon reports can provide specific information about beacon frames sent by neighboring access points. 802.11k beacon reports can provide information about the capabilities and characteristics of neighboring access points by analyzing beacon frames broadcast by neighboring access points. In addition to information about beacon frames sent by neighboring access points, 802.11k beacon reports can include access point capabilities, supported data rates, other configuration information broadcast in the beacon frames, channel information, signal strength, etc.

[0034] Because the aforementioned 802.11k reports may be designed solely for roaming decisions, and the limited information they provide may only help a site or client device find the next optimal access point, there is a need for enhanced 802.11k reports, including extended information that is useful to the network infrastructure and can assist the site or client device in several other dimensions. In many embodiments, the devices and methods discussed herein implement an enhancement mechanism for STAs to provide extended 802.11k reports to the network infrastructure to assist in wireless network management and improve the STA's experience in wireless networks (e.g., wireless local area networks (WLANs)). In several embodiments, the devices and methods discussed herein provide a radio frequency (RF) view of the STA, which can help extend the access point view to the ground and provide information useful to the network infrastructure to assist the STA in several other dimensions, including, for example, P2P detection, detection of unavailable channels, detection of very low power (VLP) systems, and detection of other local RF events that may degrade the STA's experience but are not directly visible to the access point. RF views enhance the visibility and management of wireless coverage and performance by integrating or extending data and insights from access points to a more detailed or specific level (typically at the physical or operational level on the ground). In further embodiments, the devices and methods discussed herein can enhance the IEEE 802.11k standard, enabling the specialization of 802.11k reports shared with the network infrastructure to aid in various network management tasks. Furthermore, in additional embodiments, the devices and methods discussed herein can enhance 802.11k beacon reports for analytical purposes. 802.11k beacon reports can be used for more detailed analysis of the capabilities and configurations of neighboring access points, which can be useful for network management and optimization.

[0035] In further embodiments, the devices and methods discussed herein may allow access points to generate wireless environment report requests, such as requests for conditional beacon reports, requests for conditional neighbor reports, etc. In still more embodiments, the generated wireless environment report request may include at least one of conditions, P2P specifications, non-IEEE 802.11 specifications, or element restrictions. In still further embodiments, the wireless environment report request may include a negative SSID or an excluded SSID, which may specifically be excluded from an available network list or network scan. In further embodiments, the wireless environment report request may include an SSID and conditions associated with that SSID. Furthermore, the wireless environment report request may be configured to indicate at least one of a channel or frequency band. In still more embodiments, when the wireless environment report request includes conditions, the wireless environment report request may be configured to indicate reporting a local SSID on the indicated channel or frequency band, reporting the absence of a neighbor SSID on the indicated channel or frequency band, reporting all local SSIDs on the indicated channel or frequency band, and / or the results of a standards-based evaluation. A standards-based evaluation may include one or more logical operations. In further embodiments, when the wireless environment reporting request includes P2P technical specifications, the wireless environment reporting request can be configured to indicate the number of reported P2P pairs. In still further embodiments, the wireless environment reporting request may include one or more thresholds.

[0036] In many further embodiments, the access point may send the generated wireless environment report request to the STA, such as a client device. The client device may generate a wireless environment report based on the wireless environment report request. For example, the client device may generate a wireless environment report associated with at least one of the conditions, P2P technical specifications, non-IEEE 802.11 technical specifications, or element limitations included in the wireless environment report request. The client device may send the generated wireless environment report to the access point. The access point may receive the generated wireless environment report.

[0037] In many additional embodiments, Radio Environment Reporting Requests (RRMs) can be used for Radio Management Requests (RRMs). RRM can involve optimizing the use of RF resources to improve network performance and efficiency, and assisting in the allocation of radio channels to different devices or access points to minimize interference and maximize the use of available spectrum. RRM can also involve adjusting the transmit power of devices to balance coverage and minimize interference. For example, RRM can ensure that devices use just enough power to communicate effectively without causing excessive interference to others. RRM can also include managing the distribution of network traffic across different access points or channels to avoid overloading any single component and ensure a balanced and efficient network, as well as transferring the connection of client devices from one access point to another when client devices move, ensuring seamless connectivity. RRM can be used to plan and optimize network layout, including the placement of access points and the configuration of their settings, to enhance overall network coverage and performance. In even further embodiments, RRMs can also be used to detect rogue or adjacent access points that may disrupt the managed operation of access points, thereby affecting the roaming efficiency of STAs. A rogue can refer to a rogue device or unauthorized access point attempting to connect to or interfere with the network, potentially jeopardizing network security and performance. The following are example scenarios for enhancing wireless environment reporting to optimize wireless network management.

[0038] In the first example scenario, the access point or the wireless LAN controller (WLC) connected to the access point may be aware of neighboring systems utilizing some form of adaptive radio management (ARM) / RRM. ARM can refer to a subset of RRM and focuses on optimizing wireless network performance by dynamically adjusting radio parameters based on real-time conditions. ARM can dynamically select and allocate radio channels to minimize interference and maximize throughput, adapting to changes in the radio environment and network load. ARM can continuously analyze network performance and adjust radio parameters to improve coverage, capacity, and overall user experience. In this example scenario, the access point can request STAs to scan channels or frequency bands via a radio environment report request and report whether a local SSID is detected and whether a neighboring SSID is not reported. STAs can generate a radio environment report in response to the radio environment report request from the access point. The generated radio environment report can be used to guide roaming STAs to channels unaffected by neighboring systems.

[0039] In the second example scenario, the access point can request a STA to scan channels or frequency bands via a Radio Environment Report Request (REER Request) and report all detected SSIDs, but only on channels where the local SSID is also detected. The STA can generate a Radio Environment Report based on the RERROW request from the access point. The generated RERROW report can be used to detect rogues that may be located at the edge of other BSSs.

[0040] In the third example scenario, an access point can request a STA to scan channels or frequency bands via a Radio Environment Report Request (RIRFP) and report systems detected on any channels where the local SSID is not detected. The STA can generate a Radio Environment Report based on the RIRFP request from the access point. The generated Radio Environment Report can be used for RRM to predict the most efficient channel changes, for example, in scenarios where directional antennas prevent adjacent access points from detecting each other.

[0041] In the fourth example scenario, an access point can request a STA to perform logical operations based on its 802.11k report and return the results via a wireless environment report request. For example, an access point can request a STA to report the number of access points it sees on SSID "blizzard" with a Received Signal Strength Indicator (RSSI) greater than a first threshold or a Signal-to-Noise Ratio (SNR) less than a second threshold. RSSI can refer to a measurement of the received signal strength or power of radio signals received in the wireless environment.

[0042] In additional embodiments, the devices and methods discussed herein may also allow the access point to generate specialized radio environment report requests, such as specialized neighbor report requests. Specialized neighbor report requests may include information elements (IEs) configured to indicate the type of detection requested from the STA. IEs may include elements such as Datagram Transport Layer Security (DTLS) pairs or P2P systems. In several embodiments, a P2P system may include another STA with which the STA communicates via a P2P protocol, such as a Neighbor Aware Network (NAN) protocol, a DTLS protocol, etc. The STA may generate specialized radio environment reports, such as specialized neighbor reports, based on specialized neighbor report requests from the access point. The generated specialized neighbor reports may be used by the access point to schedule P2P exchanges, detect P2P density in the cell (and thus its impact on available call time in the BSS), or notify the RRM of channel allocation. In still several embodiments, the IE may also extend multi-band operation (MBO), other radio technology reports, request the STA to scan channels or frequency bands, and report active non-Wi-Fi radios used or detected by the STA. Other radio technology reports may refer to reports associated with non-IEEE 802.11 technical specifications. MBOs and other radio technology reports can be used to detect, for example, active use of ultra-wideband (UWB) or Bluetooth Low Energy (BLE) radios by STAs.

[0043] In a further scenario, the access point may have a fairly accurate view of the wireless environment, but may be missing some elements. These elements may include, for example, information about rogue access points on different ESSs, or other information about access points that are uncertain. In this case, the access point may not need the full 802.11k report, but may only need certain fields from the 802.11k report. Therefore, in an action frame sent to the STA, in several additional embodiments, the access point may request only the necessary portions of the 802.11k report from the STA, or request detailed information about an access point that the STA cannot clearly see. In this case, the STA may only respond to the elements or fields requested by the access point. For example, the access point may request the STA to report whether the detected access point is a VLP system, thereby facilitating the detection of self-organizing or low-power systems.

[0044] In various embodiments, a client device (referred to herein as a "requesting client device") may also generate a wireless environment report request that includes at least one of the following: conditions, P2P specifications, non-IEEE 802.11 specifications, or element limitations. The requesting client device may send the generated wireless environment report request to another client device (referred to herein as a "responding client device") via a P2P link. The responding client device may generate a wireless environment report based on the wireless environment report request. For example, the responding client device may generate a wireless environment report associated with at least one of the conditions, P2P specifications, non-IEEE 802.11 specifications, or element limitations included in the wireless environment report request. The responding client device may send the generated wireless environment report to the requesting client device via a P2P link. The requesting client device may receive the sent wireless environment report from the responding client device via a P2P link.

[0045] In various other embodiments, the devices and methods discussed herein can allow an access point to request conditional reports from a STA, since the STA has sufficient processing capacity. Conditional reports can include conditions such as "report a non-blizzard SSID on this channel if blizzard is also detected," or "report P2P pairs on this channel," etc. Beyond roaming optimization, in several further embodiments, the devices and methods discussed herein can perform exchanges between the STA and the access point, including analysis.

[0046] In numerous embodiments, the devices and methods discussed herein provide network management logic configured to enhance wireless environment reporting for optimized wireless network management. This network management logic can include various hardware and / or software deployments and can be configured in various ways. For example, it can be configured as a standalone device, as logic within another network device, distributed among various cooperating network devices, or operated remotely as part of a cloud-based network management tool. Examples of network devices that can implement this network management logic include, but are not limited to, access points, WLCs, client devices, servers, or any other device supporting 802.11k.

[0047] Various aspects of this disclosure may be embodied as an apparatus, system, method, or computer program product. Therefore, various aspects of this disclosure may 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, all of which are generally referred to herein as a “function,” “module,” “apparatus,” or “system.” Furthermore, various aspects of this disclosure may take the form of a computer program product embodied in one or more non-transitory computer-readable storage media storing computer-readable and / or executable program code. Many functional units described in this specification have been labeled as functions to more specifically emphasize their implementation independence. For example, a function may be implemented as hardware circuitry including custom very large-scale integration (VLSI) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Functions may also be implemented in programmable hardware devices, such as by field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As an example, a computer-readable medium is provided carrying instructions that, when executed by one or more processors, cause to perform any of the methods described herein.

[0048] The functionality can also be implemented, at least partially, in software for execution by various types of processors. The identified functionality of the executable code can, for example, comprise one or more physical or logical blocks of computer instructions, which can be organized, for example, as objects, procedures, or functions. However, the executable file containing the identified functionality does not need to be physically located together, but can include different instructions stored in different locations that, when logically combined, constitute the functionality and achieve its stated purpose.

[0049] In practice, the functionality of executable code can include a single instruction or many instructions, and can even be distributed across several different code segments, different programs, or across several storage devices. Where the functionality or a portion of the functionality is implemented in software, the software portion can be stored on one or more computer-readable and / or executable storage media. Any combination of one or more computer-readable storage media can be utilized. Computer-readable storage media can include, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination of the foregoing, but excluding signal propagation. In the context of this document, computer-readable and / or executable storage media can be any tangible and / or non-transitory medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, processor, or device.

[0050] Computer program code used to perform the operations of various aspects of this disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Java, Smalltalk, C++, C#, Objective C, etc., conventional procedural programming languages ​​such as the "C" programming language, scripting programming languages, and / or other similar programming languages. The program code may be executed, partially or wholly, on one or more user computers and / or on remote computers or servers via data networks, etc.

[0051] As used herein, components include tangible, physical, non-transient devices. For example, a component may be implemented as hardware logic circuitry including custom VLSI circuitry, gate arrays, or other integrated circuits; off-the-shelf semiconductors, such as logic chips, transistors, or other discrete devices; and / or other mechanical or electrical devices. Components may also be implemented in programmable hardware devices, such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. A component may include one or more silicon integrated circuit devices (e.g., chips, dies, die planes, packages) or other discrete electrical devices that are electrically in communication with one or more other components via electrical wiring on a printed circuit board (PCB), etc. Each function and / or module described herein may alternatively be embodied by or implemented as a component in some embodiments.

[0052] As used herein, a circuit includes a group of one or more electrical and / or electronic components that provide one or more paths for current. In some embodiments, a circuit may include a current return path, such that the circuit is a closed loop. However, in another embodiment, a group of components that does not include a current return path may be referred to as a circuit (e.g., open loop). For example, an integrated circuit may be referred to as a circuit, regardless of whether the integrated circuit is coupled to ground (as a current return path). In various embodiments, a circuit may include a portion of an integrated circuit, an integrated circuit, a group of integrated circuits, a group of non-integrated electrical and / or electronic components with or without integrated circuit devices, etc. In one embodiment, a circuit may include custom VLSI circuitry, gate arrays, logic circuitry, or other integrated circuits; off-the-shelf semiconductors, such as logic chips, transistors, or other discrete devices; and / or other mechanical or electrical devices. A circuit may also be implemented as a synthesized circuit in a programmable hardware device, such as a field-programmable gate array, programmable array logic, programmable logic device, etc. (e.g., as firmware, netlist, etc.). A circuit may include one or more silicon integrated circuit devices (e.g., chips, dies, die planes, packages) or other discrete electrical devices that are electrically communicated with one or more other components via electrical traces on a PCB, etc. In some embodiments, each function and / or module described herein may be embodied in or implemented as a circuit.

[0053] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment of this disclosure. Therefore, the phrases "in an embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless explicitly stated otherwise. The terms "comprising," "including," "having," and variations thereof mean "including, but not limited to," unless explicitly stated otherwise. The enumeration of items does not imply that any or all items are mutually exclusive and / or mutually inclusive, unless explicitly stated otherwise. The terms "a," "an," and "described" also mean "one or more," unless explicitly stated otherwise.

[0054] Furthermore, as used herein, references to reading, writing, storing, buffering, and / or transferring data can include all of the data, a portion of the data, a set of the data, and / or a subset of the data. Similarly, references to reading, writing, storing, buffering, and / or transferring non-host data can include all of the non-host data, a portion of the non-host data, a set of the non-host data, and / or a subset of the non-host data.

[0055] Finally, as used herein, the terms “or” and “and / or” should be interpreted as inclusive “or,” meaning any one or any combination thereof. Therefore, “A, B, or C” or “A, B, and / or C” means “any one of the following: A; B; C; A and B; A and C; B and C; A, B, and C.” Exceptions to this definition will only occur if the combination of elements, functions, steps, or actions is inherently mutually exclusive in some way.

[0056] The aspects of this disclosure are described below with reference to schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and computer program products according to embodiments of this disclosure. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a computer or other programmable data processing apparatus to produce machinery, such that the instructions, executable via the processor or other programmable data processing apparatus, create means for implementing the functions and / or actions specified in one or more blocks of the schematic flowcharts and / or schematic block diagrams.

[0057] It should also be noted that in some alternative implementations, the functions marked in the boxes may not occur in the order indicated in the figures. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods that are functionally, logically, or effectively equivalent to one or more boxes or portions thereof in the figures shown are conceivable. Although various arrow and line types may be used in flowcharts and / or block diagrams, they are understood not to limit the scope of the corresponding embodiments. For example, arrows may indicate wait or monitoring periods of unspecified duration between enumeration steps in a depicted embodiment.

[0058] In the following detailed description, reference is made to the accompanying drawings, which form a part thereof. The foregoing summary is illustrative only and is not intended to be limiting in any way. Further aspects, embodiments, and features, in addition to the illustrative aspects, embodiments, and features described above, will become apparent from reference to the accompanying drawings and the following detailed description. Descriptions of elements in each figure may refer to elements in the preceding figures. Similar reference numerals may refer to similar elements in the figures, including alternative embodiments of similar elements.

[0059] refer to Figure 1This illustration shows a schematic diagram of a wireless local area network (WLAN) system 100 according to various embodiments of the present disclosure. WLAN standards allow seamless communication and connectivity between various devices within a local area. One such WLAN standard is Wi-Fi® from the Wi-Fi Alliance Corporation, which is based on the IEEE 802.11 protocol family. The IEEE 802.11 protocol family, developed by the Institute of Electrical and Electronics Engineers (IEEE), defines the protocols for wireless local area networks (WLANs). Wi-Fi® provides high-speed wireless access to the Internet and local network resources, with standards such as 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, and 802.11ax, each offering improvements in speed, range, and efficiency. Each adoption of a Wi-Fi® standard is typically designed to deliver enhanced performance, increased capacity, and better efficiency in congested network environments. Other standards are generally used for short-range wireless communication between devices, particularly in the personal area network (PAN) domain. Wi-Fi® and other protocols have become an integral part of modern connectivity, supporting a wide range of devices and applications in homes, businesses, and public spaces. Emerging technologies and future iterations continue to refine wireless network standards, ensuring the evolution of efficient, reliable, and secure wireless communication.

[0060] In the IEEE 802.11 wireless LAN standard (often associated with Wi-Fi® technology), service sets play a role in defining and organizing wireless network devices. A service set can refer to a collection of wireless devices that share a common Service Set Identifier (SSID). The SSID is typically recognized by users as a network name presented in natural language, used as a means of identification and differentiation between various wireless networks. Within a service set, nodes including devices (such as laptops, smartphones, or other Wi-Fi-enabled devices) cooperate and adhere to shared link-layer network parameters. These link-layer network parameters encompass specific communication settings and protocols that facilitate seamless interaction between devices within the service set. Service sets can form cohesive and logically structured network segments, creating an organized structure for wireless communication where devices can communicate and share data within defined parameters, thereby enhancing the efficiency and coordination of wireless network operation.

[0061] In the context of wireless LAN standards, services can be configured in two different forms: Basic Service Set (BSS) or Extended Service Set (ESS). A BSS represents a subset within a service set, including devices that share common physical layer media access characteristics. These characteristics include parameters such as radio frequencies, modulation schemes, and security settings, ensuring a seamless wireless network between devices. A BSS is uniquely identified by a Basic Service Set Identifier (BSSID), a 48-bit tag conforming to the MAC-48 convention. Although a device may have multiple BSSIDs, each BSSID is typically associated with at most one BSS set at any given time.

[0062] BSS should not be confused with the coverage area of ​​an access point, which is called the Basic Service Area (BSA). The BSA encompasses the physical space where the access point provides wireless coverage, while the Basic Service Area focuses on logical groups of devices sharing common network characteristics. This distinction emphasizes that the Basic Service Area is a conceptual grouping based on shared communication parameters, while the Basic Service Area defines the spatial extent of the access point's wireless coverage. Understanding these distinctions is fundamental for effectively configuring and managing wireless networks, ensuring optimal performance and coordination between connected devices.

[0063] An SSID defines a Service Set or Extended Service Set. SSIDs are typically broadcast in plaintext by a site in beacon packets to announce the existence of the network and are perceived by users as the name of the wireless network. Unlike the Basic Service Set Identifier, the SSID is usually customizable. Because the content of the SSID field is arbitrary, the 802.11 standard allows devices to announce the existence of a wireless network using beacon packets. Sites can also send packets with the SSID field set to empty; this prompts the associated access point to send the site a list of supported SSIDs. Once a device is associated with a Basic Service Set, for efficiency, the SSID is not sent in the packet header; only the BSSID is used for addressing.

[0064] An Extended Service Set (ESS) is a more sophisticated wireless network architecture designed to provide seamless coverage across larger areas, typically spanning environments such as homes or offices that may be too large to be reliably covered by a single access point. This network is created through the collaboration of multiple access points, presenting users with a unified and continuous network experience. Extended Service Sets operate by integrating one or more infrastructure basic service sets within a common logical network segment, characterized by sharing the same Internet Protocol (IP) subnet and Virtual Local Area Network (VLAN).

[0065] The concept of an extended service set is specifically designed for scenarios where a single access point cannot adequately cover the entire desired area. By strategically employing multiple access points, users can move seamlessly within an extended service set without experiencing connection interruptions, thus maintaining a consistent wireless internet experience across a larger space, where users can switch between different physical locations covered by different access points.

[0066] In addition, the Extended Services Set provides additional features such as distribution services and centralized authentication. Distribution services facilitate the efficient distribution of network resources and services across the entire Extended Services Set. Centralized authentication enhances security and simplifies access control by allowing users to authenticate once to access any part of the Extended Services Set, thereby simplifying user experience and network management. Overall, the Extended Services Set provides a scalable and robust solution for ensuring reliable and comprehensive wireless connectivity in diverse and wide-ranging environments.

[0067] A network can include various user terminal devices connected to the network. These devices are sometimes referred to as stations (STAs). Each device is typically configured with a Media Access Control (MAC) address according to the IEEE 802.11 standard. Figure 8 As described in more detail below, various devices on the network may include components such as processors, transceivers, and user interfaces. These components can be configured to process data frames sent and / or received over a wireless network. An access point is a wireless device configured to provide user terminal equipment with access to a larger network, such as the Internet.

[0068] exist Figure 1 In the depicted embodiment, a wireless network controller 120 (shown as a WLC) is connected to a public network such as the Internet 110. The wireless network controller 120 communicates with an ESS 130. The ESS 130 includes two separate basic service sets, such as BSS 1 140 and BSS 2 150. ESS 130, BSS 1 140, and BSS 2 150 all broadcast and are configured with the same SSID, “WiFi name,” which can be the BSSID of each of BSS 1 140 and BSS 2 150, as well as the Extended Service Set Identifier (ESSID) of ESS 130.

[0069] Within the first BSS 1 140, the network includes multiple devices, such as a first laptop 141, a second laptop 142, a first telephone 143, a second telephone 144, and a third laptop 160. Each of these devices can communicate with a first access point 145. Similarly, within the second BSS 2 150, the network includes multiple devices, such as a first tablet 151, a fourth laptop 152, a third telephone 153, and a first watch 154. Each of these devices can communicate with a second access point 155. The third laptop 160 is communicatively connected to both the first BSS 1 140 and the second BSS 2 150. In this setup, the third laptop 160 can be seen roaming from a physical area served by the first BSS 1 140 to a physical area served by the second BSS 2 150. Any of the aforementioned devices, including the first and second laptops and the first, second, and third telephones, can be replaced with similar devices (such as tablets or laptops) without departing from the spirit and scope of this disclosure. For example, in many embodiments, laptops and notebooks can be considered synonyms.

[0070] Despite about Figure 1 Specific embodiments of the wireless local area network system 100 suitable for performing the various steps, processes, methods, and operations described herein have been discussed; however, any of a variety of systems and / or processes may be utilized according to embodiments of this disclosure. For example, the wireless local area network system 100 may be configured with any number of various network topologies, including different types of interconnection devices and user equipment. Figure 1 The elements depicted in the text can also be related to... Figure 2-8 Other elements may be interchanged to achieve a particular desired implementation.

[0071] refer to Figure 2 A conceptual network diagram 200 is shown illustrating various environments in which network management logic according to various embodiments of the present disclosure can operate on multiple network devices. Those skilled in the art will recognize that the network management logic can include various hardware and / or software deployments and can be configured in various ways. In many embodiments, the network management logic can be configured as a standalone device, exist as logic within another network device, be distributed among various network devices operating collaboratively, or operate remotely as part of a cloud-based network management tool. In several embodiments, one or more servers 210 may be configured with network management logic, or may otherwise operate as network management logic. In various embodiments, the network management logic can operate on one or more servers 210 connected to a communication network 220 (shown as the "Internet"). The communication network 220 can include a wired network or a wireless network. The network management logic can be provided as a cloud-based service that can serve remote networks, such as, but not limited to, a deployed network 240.

[0072] However, in various embodiments, network management logic can be implemented as a distributed logical operation across multiple network devices. Figure 2 In the depicted embodiments, multiple network access points (referred to as "APs") 250 may operate as network management logic in a distributed manner, or a specific device may operate as the network management logic for all adjacent or sibling access points 250. Access points 250 can facilitate Wi-Fi® connectivity for various electronic devices, such as, but not limited to, mobile computing devices including cellular phones 260, laptops 270, portable tablets 280, and wearable computing devices 290.

[0073] In many embodiments, network management logic can be integrated into another network device. Figure 2 In the depicted embodiments, the Wireless LAN Controller (WLC) 230 may have integrated network logic that the WLC 230 can utilize to monitor or control the power consumption of multiple access points 235 to which the WLC 230 is connected, either wired or wirelessly. In additional embodiments, a personal computer 225 may be used to remotely access and / or manage various aspects of the network management logic, either directly or within the network itself. Figure 2 In the depicted embodiment, the personal computer 225 communicates via the communication network 220 and can access the network management logic of the server 210, the network access point 250, or the WLC 230.

[0074] Despite about Figure 2 Specific embodiments of the network management logic applicable to performing the various steps, processes, methods, and operations described herein are discussed, and these logics can operate on multiple network devices. However, according to embodiments of this disclosure, any of a variety of systems and / or processes can be utilized. For example, the network management logic may be provided as a separate device or software from the WLC 230, or the network management logic may be integrated into the WLC 230. Figure 2 The elements depicted in the text can also be related to... Figure 1 and Figure 3-8 Other elements may be interchanged to achieve a particular desired implementation.

[0075] refer to Figure 3This document illustrates a schematic block diagram of a wireless environment 300 for optimizing wireless network management, according to various embodiments of the present disclosure. In many embodiments, the wireless environment 300 may deploy a WLAN. A WLAN can allow multiple devices to communicate with each other and wirelessly connect to a network (e.g., the Internet) within a relatively small geographic area, such as a home, office, or campus. A WLAN can utilize radio waves to transmit data between devices. In several embodiments, devices in the WLAN may be configured to operate according to IEEE 802.11 wireless communication technology (e.g., Wi-Fi® from Wi-FiAlliance Corporation). In a WLAN deployment, one or more wireless access points may be present serving wireless client devices (also referred to as STAs or clients). An STA can refer to any device that can connect to the WLAN, including end-user devices (such as laptops, smartphones, game consoles, wearable devices), other devices (such as printers, Internet of Things (IoT) devices), or network infrastructure devices (such as wireless mesh nodes). In various embodiments, all STAs in the WLAN may be configured to generate generic beacon reports using the IEEE 802.11k standard. A STA can be in client mode associated with an access point, or in access point mode acting as a network provider. When acting as a client device, the STA can connect to the access point to gain network access. For example, in... Figure 3 In this configuration, the STA can be configured to operate as client devices 306 and 308, which can connect to access point 304. In various embodiments, client devices 306 and 308 can connect to a WLAN to utilize services and resources provided by a server, an access point such as access point 304, or other network devices. Examples of client devices 306 and 308 may be laptops, tablets, dual-mode cellular phones, Voice over Internet Protocol (VoIP) phones, personal digital assistants (e.g., converged devices supporting WLAN data and / or voice and cellular connectivity), game consoles, wearable devices, etc.

[0076] In further embodiments, the WLAN may allow wireless communication via a central access point 304 as well as direct wireless communication (e.g., peer-to-peer "P2P" communication) between client devices 306 and 308. In additional embodiments, the WLAN may include access points 304, 310A, 310B, and 310C, client devices 306 and 308, and one or more wireless controllers, such as... Figure 3 The WLAN controller 302 is shown. Client devices 306 and 308 can communicate within the WLAN network infrastructure via access point 304.

[0077] Access points 304, 310A, 310B, and 310C may refer to network devices that allow wirelessly capable devices (e.g., client devices 306 and 308) to connect to a wired network, such as a wireless router. The wired network may be a wired local area network, such as Ethernet. Access points 304, 310A, 310B, and 310C may provide wireless connectivity to client devices 306 and 308 and act as bridges between the WLAN and the wired network. In a further embodiment, access points 304, 310A, 310B, and 310C may broadcast the WLAN's SSID and handle data traffic between client devices 306 and 308 and the network infrastructure. Although... Figure 3 The wireless environment 300 shown in the diagram has four access points 304, 310A, 310B, and 310C, but the wireless environment 300 may include any number of access points. Access points 304, 310A, 310B, and 310C can communicate with each other to operate in coordination.

[0078] In further embodiments, the WLAN controller 302 may be a computing device configured to manage and control the actions of one or more access points (e.g., access points 304, 310A, 310B, and 310C) in a WLAN. In yet further embodiments, the data management and reporting responsibilities of access points 304, 310A, 310B, and 310C regarding detected client devices 306 and 308 may be offloaded to the WLAN controller 302. Although the WLAN controller 302... Figure 3 While shown as a single computing device, the WLAN controller 302 can represent multiple different computing devices that are physically located near access points 304, 310A, 310B, and 310C, or that are physically separated and accessed through one or more networks (such as the Internet or the cloud).

[0079] exist Figure 3In the example scenario shown, client device 306 can connect to access point 304 to gain access to the WLAN. Access point 304 can be operatively coupled to WLAN controller 302. Furthermore, in additional embodiments, client device 306 can connect to another client device 308 via a P2P link. In some further embodiments, WLAN controller 302 can be configured to receive information from access point 304 related to monitored transmissions, storing data indicating when client device 306 establishes a P2P link with another client device 308, forms a P2P group, or joins an existing P2P group. Access point 304 can also manage locally unique P2P interface addresses for any P2P device. In various further embodiments, by tracking the P2P interface and device address, access point 304 or the wireless infrastructure (including, for example, WLAN controller 302 to which access points 304, 310A, 310B, and 310C are connected) can correctly track a P2P device (e.g., client device 306) when it joins different P2P groups.

[0080] In further embodiments, the WLAN may also include a non-IEEE 802.11 enabled device 312 configured to implement a non-IEEE 802.11 technical specification. The non-IEEE 802.11 technical specification can refer to wireless communication standards that do not belong to the IEEE 802.11 family, including, for example, Bluetooth® of Bluetooth Sig, Inc., ZigBee® of ZigBee Alliance Corporation, Z-Wave® of Z-Wave Alliance, Inc., Near Field Communication (NFC), cellular technologies (such as LTE, 5G, 6G, XG-enabled mobile communication (where XG can refer to any future generation of mobile communication), etc.), WiMAX® of the WiMAX Forum, etc. The non-IEEE 802.11 enabled device 312 can be connected to the WLAN using, for example, a bridging device, a gateway device, an adapter, a converter, a Wi-Fi® enabled device, a wired connection, etc.

[0081] The IEEE 802.11k standard allows client device 306 to request information about neighboring access points 310A, 310B, and 310C (typically on the same Extended Service Set, "ESS") from connected access point 304 in the form of an 802.11k neighbor report to assist in making intelligent roaming decisions. When client device 306 requests a radio environment report (e.g., an 802.11k neighbor report) from access point 304 using the 802.11k standard, in addition to sending information to client device 306 including, for example, access point 304's BSSID, SSID, channel information, and maximum / min information, access point 304 can further enhance the radio environment report to include extended information based on several parameters and / or conditions. This extended information is useful for network infrastructure and can assist in network analysis and various network management tasks.

[0082] The 802.11k standard also allows access point 304 to request information from client device 306, for example, in the form of an 802.11k beacon report, requesting client device 306 to scan one or more channels or frequency bands (actively or passively) and report access points detected in those channels or frequency bands. Access point 304 can also request client device 306 to share only the results of previous or most recent scans. It can request client device 306 to report all detected access points associated with any SSID, or only the single SSID associated with client device 306. In addition to providing a view of the wireless environment 300 from the perspective of client device 306, 802.11k beacon reports can be enhanced to provide extended information useful to network infrastructure and can assist client device 306 in multiple other dimensions and various network management tasks.

[0083] In further embodiments, network management logic configured to enhance wireless environment reporting in wireless environment 300 can be implemented in access point 304, client device 306, and / or WLAN controller 302 to optimize wireless network management. In many further embodiments, access point 304 can generate a wireless environment report request that includes at least one of conditions, P2P specifications, non-IEEE 802.11 specifications, or element restrictions. Access point 304 can send the generated wireless environment report request to client device 306. Client device 306 can generate a wireless environment report based on the wireless environment report request. For example, client device 306 can generate a wireless environment report associated with at least one of the conditions, P2P specifications, non-IEEE 802.11 specifications, or element restrictions included in the wireless environment report request. Client device 306 can send the generated wireless environment report to access point 304. Access point 304 can receive the generated wireless environment report.

[0084] In many additional embodiments, client device 306 (referred to herein as the "requesting client device") may generate a wireless environment report request that includes at least one of conditions, P2P specifications, non-IEEE 802.11 specifications, or element restrictions. Requesting client device 306 may send the generated wireless environment report request to another client device 308 (referred to herein as the "responding client device") via a P2P link. Response client device 308 may generate a wireless environment report based on the wireless environment report request. For example, response client device 308 may generate a wireless environment report associated with at least one of the conditions, P2P specifications, non-IEEE 802.11 specifications, or element restrictions included in the wireless environment report request. Response client device 308 may send the generated wireless environment report to the requesting client device via a P2P link. Requesting client device 306 may receive the sent wireless environment report from response client device 308 via a P2P link.

[0085] Despite about Figure 3 Specific embodiments of a wireless environment for optimizing wireless network management and providing enhanced wireless environment reporting have been discussed, suitable for performing the various steps, processes, methods, and operations described herein. However, any of a variety of systems and / or processes can be utilized according to embodiments of this disclosure. For example, access point 304 may be configured to operate as an independent access point capable of providing connectivity among various wireless client devices, or as a multi-functional access point capable of operating as a combination of two or more access points, or as a controlled access point capable of operating as a client device of WLAN controller 302. Figure 3 The elements depicted in the text can also be related to... Figure 1-2 and Figure 4-8 Other elements may be interchanged to achieve a particular desired implementation.

[0086] refer to Figure 4 The diagram illustrates a flowchart of a process 400 for enhanced wireless environment reporting from an access point perspective, according to various embodiments of the present disclosure. Process 400 may implement an enhancement mechanism that allows client devices to provide extended reports (also referred to as “802.11k reports”) to the access point based on the IEEE 802.11k standard, and further to the network infrastructure, to assist in wireless network management and improve the experience of all client devices in the wireless environment.

[0087] In many embodiments, process 400 may generate a wireless environment report request (block 410). The wireless environment report request may be in the form of an 802.11 management frame referred to as an action frame. An action frame may be a type of management frame used to exchange specific control information between devices. Action frames may be configured to facilitate different types of actions or operations within the wireless environment. Action frames may be used to convey specific commands or requests between access points and client devices, or between access points. The wireless environment report request may be a request for a conditional report, a request for a report based on a specific technical specification, or a request for a report based on element restrictions. In several embodiments, the wireless environment report request may include at least one of conditions, P2P technical specifications, non-IEEE 802.11 technical specifications, or element restrictions.

[0088] In various embodiments, a wireless environment reporting request may include conditions. Conditions may refer to a specific set of criteria or rules upon which information should be reported to the access point. In various embodiments, a wireless environment reporting request may be configured to include a negative SSID or an excluded SSID, for example, as a condition. A negative SSID or an excluded SSID may refer to a Wi-Fi network identifier or SSID that can be specifically excluded from a list of available networks or a network scan. In more embodiments, a wireless environment reporting request may be configured to indicate an SSID and a condition associated with that SSID, also known as a “conditional SSID statement.” In additional embodiments, a wireless environment reporting request may be configured to indicate a channel or frequency band. In further embodiments, a wireless environment reporting request may be configured to instruct the reporting of a local SSID on the indicated channel or frequency band. In one example, a wireless environment reporting request may include the condition “Report a non-blizzard SSID on the channel if Blizzard is also detected.” In another example, process 400 may generate a wireless environment reporting request requesting a client device to scan a channel or frequency band and report all detected SSIDs, but only on channels where a local SSID is also detected. In another example, process 400 may generate a wireless environment report request, requesting the client device to scan channels or frequency bands and report systems detected on any channels where the local SSID is not detected.

[0089] In further embodiments, the wireless environment report request can be configured to indicate the absence of a neighbor SSID on the indicated channel or frequency band as a condition. In an example where the access point or a WLAN controller connected to the access point is aware of neighboring systems utilizing some form of adaptive radio management (ARM) / radio resource management (RRM), process 400 can generate a wireless environment report request, requesting the client device to scan the channel or frequency band and report whether a local SSID was detected and whether a neighbor SSID was not reported.

[0090] In a further embodiment, the wireless environment report request may be a conditional beacon report request, which is useful for RRM and detecting rogue or adjacent access points that may disrupt the operation of managed access points and thus affect the roaming efficiency of client devices. In an additional embodiment, the conditional beacon report request may include a threshold. For example, process 400 may generate a conditional beacon report request to report the number of access points seen by the client device on SSID “blizzard” with a Received Signal Strength Indicator (RSSI) greater than a first threshold (e.g., 65 dBm) or a Signal-to-Noise Ratio (SNR) less than a second threshold (e.g., 85 dBm).

[0091] In some further embodiments, the wireless environment report request can also be configured to indicate the results of a standards-based evaluation. In yet other various embodiments, the standards-based evaluation may include one or more logical operations. For example, process 400 may generate a wireless environment report request that requests the client device to perform logical operations based on its 802.11k report and return the results of the logical operations. Examples of logical operations performed by the client device may include measurements of the presence of beacon frames received from neighboring access points, signal strength, and a specific SSID.

[0092] In further embodiments, the wireless environment reporting request may include non-IEEE 802.11 specifications. In these embodiments, the wireless environment reporting request may also be configured to indicate a channel or frequency band. In one example, the access point may generate a wireless environment reporting request requesting client devices to scan channels or frequency bands and report active non-Wi-Fi radios used or detected by the client devices.

[0093] In some cases, an access point may have a fairly accurate view of the wireless environment, but may be missing some elements, including, for example, information about rogue access points on different ESSs, or other elements where the access point is uncertain. In these cases, the access point may not need the complete wireless environment report, but may only need certain fields of the wireless environment report. Therefore, in a further embodiment, in the generated wireless environment report request, process 400 may only indicate the necessary parts or elements of the wireless environment report, or process 400 may only request detailed information about a particular access point that the access point cannot clearly see. In this case, the client device may only respond to the elements or fields requested by the access point. For example, the access point may request the client device to report whether the detected access point is a very low power (VLP) system, thereby facilitating the detection of self-organizing or low-power systems.

[0094] In further embodiments, the wireless environment reporting request may include element restrictions. For example, process 400 may allow an access point to generate a specialized neighbor reporting request as a wireless environment reporting request, which includes information elements configured to indicate the type of detection requested from a client device. Information elements may refer to data structures used to convey information about network devices, services, or parameters in a network protocol. Information elements may be included in management frames of Wi-Fi protocols to provide additional information beyond the basic frame structure. For example, in the 802.11 protocol, information elements are used in frames such as beacon frames, probe requests, and probe responses to convey detailed information about network capabilities, supported data rates, and other attributes. In one example, information elements may include elements such as Datagram Transport Layer Security (DTLS) pairs. In another example, information elements may include elements such as P2P systems, where client devices can communicate with another client device via P2P protocols such as Neighbor Aware Network (NAN) protocols, DTLS protocols, etc. In many additional embodiments, the Information Element (IE) may also be extended to include Multi-Band Operation (MBO), other radio technology reporting, requesting client devices to scan channels or frequency bands, and reporting active non-Wi-Fi radios, such as Ultra-Wideband (UWB) or Bluetooth Low Energy (BLE) radios, that the client devices are using or detecting.

[0095] In a further embodiment, process 400 may send a wireless environment report request (block 420). In an additional embodiment, the wireless environment report request may be sent to a client device. The wireless environment report request may be generated by an access point and sent to the client device. In several embodiments, the wireless environment report request may be generated by a WLAN controller based on data provided by an access point and sent from the WLAN controller to the client device via the access point. In several more embodiments, the wireless environment report request may be generated by the WLAN controller based on data provided by an access point and sent directly from the WLAN controller to the client device.

[0096] In many embodiments, process 400 may receive a wireless environment report (block 430). In many additional embodiments, the wireless environment report may be received from the client device based on a sent wireless environment report request. For example, the wireless environment report may be associated with at least one of the conditions, P2P technical specifications, non-IEEE 802.11 technical specifications, or element limitations included in the wireless environment report request. Where the wireless environment report request only indicates the necessary parts of the wireless environment report or only indicates detailed information about an access point that is not clearly visible, the received wireless environment report may only include the elements or fields requested in the wireless environment report request. For example, process 400 may have requested the client device to report whether the detected access point is a VLP system. In this scenario, the received wireless environment report may only include information indicating whether the detected access point is a VLP system, thereby facilitating the detection of ad hoc or low-power systems.

[0097] In some further embodiments, process 400 can perform wireless network operations (block 440). A wireless environment report can provide a radio frequency (RF) view of client devices, which can help extend the access point view to the ground. Therefore, a wireless environment report can provide information useful to the network infrastructure to help the access point perform wireless network operations. For example, if a wireless environment report indicates high interference or poor signal quality on the current channel, the access point can switch to a less congested channel to improve performance and reduce interference. In another example, the access point can adjust its transmit power based on the reported signal strength and interference levels, which can minimize interference to neighboring access points. In yet another example, if a wireless environment report indicates that some access points are overloaded, the access point can assist in load balancing by directing client devices to less congested access points or coordinating with other access points to manage client distribution. In yet another example, the access point can adjust the beacon interval or other timing parameters based on the wireless environment report to optimize network efficiency and reduce overhead.

[0098] Despite about Figure 4 Specific embodiments of a process 400 for enhanced wireless environment reporting from an access point perspective, applicable to performing the various steps, procedures, methods, and operations described herein, have been discussed. However, any of various systems and / or processes can be utilized according to various embodiments of this disclosure. For example, instead of the access point performing the generation of wireless environment report requests, the access point can offload the report request generation function to another server in the WLAN controller or wireless network infrastructure, based on data provided by one or more access points that monitor transmissions from client devices in the WLAN. Figure 4 The elements depicted in the text can also be related to... Figure 1-3 and Figure 5-8Other elements may be interchanged to achieve a particular desired implementation.

[0099] refer to Figure 5 The diagram illustrates a flowchart of process 500 for enhanced wireless environment reporting from a site perspective, according to various embodiments of the present disclosure. In many embodiments, the STA can be configured to operate in a client mode associated with an access point. That is, the STA can be configured to operate as a client device that can connect to an access point in the wireless environment.

[0100] In several embodiments, process 500 may receive a wireless environment report request (block 510). Process 500 may receive the wireless environment report request from an access point. The wireless environment report request may be received by a client device connected to the access point. In various embodiments, the wireless environment report request may be a request for a conditional report. In various embodiments, the wireless environment report request may be a request for a report based on a specific technical specification (e.g., P2P technical specification, non-IEEE 802.11 technical specification, etc.). In more embodiments, the wireless environment report request may be a request for a report based on element restrictions (including, for example, DTLS pairs or P2P pairs). In one embodiment, the wireless environment report request may include a P2P technical specification, such as "Report P2P pairs on this channel".

[0101] In an additional embodiment, process 500 may scan the wireless environment (block 520). The wireless environment may be scanned by a client device. Process 500 may scan the wireless environment based on a received wireless environment report request. In one example, the wireless environment report request may indicate an SSID, conditions associated with that SSID, and a channel or frequency band. In this example, based on the indication in the wireless environment report request, process 500 may scan the indicated channel or frequency band to detect all SSIDs, but only on channels where the local SSID is also detected. In another example, based on the indication in the wireless environment report request, process 500 may scan the indicated channel or frequency band to detect systems on any channels where the local SSID is not detected. In yet another example, based on the indication in the wireless environment report request, process 500 may scan the indicated channel or frequency band to detect P2P pairs on the indicated channel or frequency band.

[0102] In a further embodiment, process 500 may generate a wireless environment report (block 530). The wireless environment report may be generated by a client device. Process 500 may generate the wireless environment report based on the results of scanning the wireless environment in response to a wireless environment report request. For example, for a wireless environment report request that may indicate an SSID, conditions associated with that SSID, and a channel or frequency band, based on the results of scanning the indicated channel or frequency band, process 500 may report all detected SSIDs, but only on channels where the local SSID is also detected. In another example, based on the results of scanning the indicated channel or frequency band, process 500 may generate a wireless environment report indicating the system on any channel where the local SSID is not detected. In yet another example, based on the results of scanning the indicated channel or frequency band, process 500 may generate a wireless environment report indicating P2P pairs detected on the requested channel or frequency band.

[0103] In further embodiments, process 500 may generate a wireless environment report based on conditions included in the wireless environment report request. In a further embodiment, process 500 may generate a wireless environment report based on excluded SSIDs indicated in the wireless environment report request. In an additional embodiment, process 500 may generate a wireless environment report based on the SSID indicated in the wireless environment report request and conditions associated with that SSID. In some further embodiments, process 500 may generate a wireless environment report based on the channel or frequency band indicated in the wireless environment report request. For example, for a wireless environment report requesting a client device to scan a channel or frequency band and report all detected SSIDs but only on channels where the local SSID is also detected, process 500 may generate a wireless environment report that can be used to detect rogues that may be at the edge of other BSSs. In another example, for a wireless environment report requesting a client device to scan a channel or frequency band and report systems detected on any channel where the local SSID is not detected, process 500 may generate a wireless environment report that can be used for RRM to predict the most efficient channel changes, particularly in scenarios where directional antennas prevent adjacent access points from detecting each other.

[0104] In various other embodiments, process 500 may generate a wireless environment report to report the local SSID on the indicated channel or frequency band. In even more embodiments, process 500 may generate a wireless environment report to report the absence of neighboring SSIDs on the indicated channel or frequency band. For example, in response to a wireless environment report requesting a client device to scan a channel or frequency band and report whether a local SSID was detected and whether a neighboring SSID was not reported, process 500 may generate a wireless environment report that can be used to direct the roaming client device to a channel unaffected by neighboring systems.

[0105] In further embodiments, process 500 may generate a wireless environment report to report the results of a standards-based evaluation, which may include one or more logical operations. For example, the client device may generate a wireless environment report that includes metrics of beacon frames received from neighboring access points, signal strength, and the presence of a specific SSID. In many further embodiments, process 500 may generate a wireless environment report based on a non-IEEE 802.11 specification included in a wireless environment report request, which may indicate a channel or frequency band. For example, for a wireless environment report request that a client device scan a channel or frequency band and report active non-Wi-Fi radios used or detected by the client device, the client device may generate a wireless environment report such as an MBO or other radio technology report, which may be used to detect active use of UWB or BLE radios by the client device.

[0106] In many additional embodiments, process 500 may limit the generation of a wireless environment report based on elements included in the wireless environment report request. For example, for a specialized neighbor report request that may include information elements configured to indicate the type of detection requested from the client device (such as a DTLS pair or a P2P system), the client device may generate a specialized neighbor report that can be used by the access point for scheduling P2P exchanges, detecting P2P density in the cell and thus its impact on the available call time of the BSS, or notifying the RRM of channel allocation.

[0107] In one example, upon receiving a wireless environment report request that includes a threshold (such as an RSSI greater than a first threshold (e.g., 65 dBm) or an SNR less than a second threshold (e.g., 85 dBm)), process 500 can generate a wireless environment report indicating the number of access points with the requested threshold seen by the client device on SSID "blizzard". In another example, where the access point or a WLAN controller connected to the access point is aware of neighboring systems utilizing some form of ARM / RRM, the client device can scan the channel or frequency band indicated in the wireless environment report request and generate a wireless environment report indicating whether a local SSID was detected and whether a neighboring SSID was not reported. In yet another example, process 500 can generate a wireless environment report indicating P2P pairs detected on the indicated channel or frequency band.

[0108] In a further embodiment, process 500 may send a wireless environment report (block 540). Process 500 may send the wireless environment report to an access point. In various embodiments, process 500 may send the wireless environment report to a WLC. In various additional embodiments, process 500 may send the wireless environment report to a WLC via an access point.

[0109] Despite about Figure 5 Specific embodiments of a process 500 for enhanced wireless environment reporting from the STA's perspective, applicable to performing the various steps, procedures, methods, and operations described herein, have been discussed. However, any of various systems and / or processes may be utilized according to embodiments of this disclosure. For example, a STA or client device may share its updated wireless environment report unsolicited when the STA or client device observes a significant change in the WLAN. Figure 5 The elements depicted in the text can also be related to... Figure 1-4 and Figure 6-8 Other elements may be interchanged to achieve a particular desired implementation.

[0110] refer to Figure 6 The diagram illustrates a flowchart of a process 600 for enhanced wireless environment reporting based on the detection of a local SSID, from a site perspective, according to various embodiments of the present disclosure. In many embodiments, the STA can be configured to operate as a client device that can connect to an access point in the wireless environment.

[0111] In several embodiments, process 600 may receive a wireless environment report request (block 610) indicating a channel or frequency band. The wireless environment report request may be received by a client device from an access point. In various embodiments, the wireless environment report request may be configured to instruct reporting of local SSIDs on the indicated channel or frequency band. In various embodiments, the wireless environment report request may be configured to instruct reporting of all local SSIDs on the indicated channel or frequency band based on the detection of a local SSID on the indicated channel or frequency band. In more embodiments, the wireless environment report request may be configured to instruct reporting of all local SSIDs on the indicated channel or frequency band based on the absence of a local SSID on the indicated channel or frequency band.

[0112] In an additional embodiment, process 600 may scan the wireless environment based on an indicated channel or frequency band (block 620). The wireless environment may be scanned by a client device. Process 600 may scan the wireless environment based on a received wireless environment report request. In the example above, based on the indication in the wireless environment report request, process 600 may scan channels or frequency bands to detect all SSIDs, but only on channels where the local SSID is also detected. In another example, based on the indication in the wireless environment report request, process 600 may scan channels or frequency bands to detect systems on any channels where the local SSID is not detected. Process 600 may initiate a scan to find available wireless networks identified by its SSID, which may be automatically triggered, for example, by the operating system of the client device.

[0113] Wi-Fi networks can operate on specific frequency bands, such as 2.4 GHz, 5 GHz, 6 GHz, extended 6 GHz, etc. In various embodiments, process 600 can scan each channel within these frequency bands to discover available wireless networks. In even more embodiments, process 600 can perform a passive scan of the indicated channel or frequency band by listening to beacon frames broadcast by neighboring access points. A beacon frame can refer to a management frame that includes the local SSID and other network information. The client device can listen on each channel for a period of time, capturing beacon frames from access points broadcasting their presence. In a further embodiment, process 600 can perform an active scan of the indicated channel or frequency band by sending probe requests on the indicated channel or frequency band. These probe requests can refer to management frames requesting a response from any neighboring access point that matches the requested SSID or supports generic SSID discovery. The access point receiving the probe request can respond with a probe response frame that includes the SSID and other information about the wireless network. The client device can extract the SSID from the beacon frame or probe response frame. The SSID can be part of the frame's payload and can be used to identify a wireless network. Additional information, such as signal strength, supported data rates, security protocols, and network capabilities, can also be collected from received frames.

[0114] In a further embodiment, process 600 may determine whether a local SSID is detected (block 625). Process 600 may determine whether a local SSID is detected based on a scan of the wireless environment according to a received wireless environment report request. In a further embodiment, in response to determining that a local SSID is detected, process 600 may generate a wireless environment report based on the detection of the local SSID (block 630). The wireless environment report may be generated by a client device. Based on the wireless environment report request, the wireless environment report may include all SSIDs detected on channels where the local SSID is also detected. In some more embodiments, process 600 may generate a wireless environment report to report all local SSIDs on an indicated channel or frequency band based on the detection of the local SSID on the indicated channel or frequency band. For example, the client device may extract the local SSID from a beacon frame or probe response frame received from a neighboring access point and include the local SSID in the wireless environment report.

[0115] In various other embodiments, process 600 may send a wireless environment report (block 640). Process 600 may send the wireless environment report from a client device to an access point. In further embodiments, in order to send the wireless environment report to the access point, the client device may utilize an action frame having a category such as "radio measurement" or "measurement report". The action frame used to send the wireless environment report may include a header having frame control and address fields and a payload including report data.

[0116] However, in many further embodiments, in response to determining that no local SSID is detected, process 600 may generate a wireless environment report based on the absence of a local SSID (block 650). Based on a wireless environment report request, the wireless environment report may include systems detected on any channel where no local SSID is detected. In many further embodiments, the client device may generate a wireless environment report to report all local SSIDs on the indicated channel or frequency band based on the absence of a local SSID on the indicated channel or frequency band. In many additional embodiments, process 600 may send a wireless environment report (block 660). Process 600 may send the wireless environment report from the client device to the access point.

[0117] Despite about Figure 6 Specific embodiments of a site-perspective process 600 for enhanced wireless environment reporting based on the detection of a local SSID, applicable to the various steps, procedures, methods, and operations described herein, are discussed. However, any of a variety of systems and / or processes may be utilized according to embodiments of this disclosure. For example, a STA or client device may provide its wireless environment report, i.e., an IEEE 802.11k report, to the network infrastructure unsolicited, meaning that a wireless environment report is periodically published even without action frames. Figure 6 The elements depicted in the text can also be related to... Figure 1-5 and Figure 7-8 Other elements may be interchanged to achieve a particular desired implementation.

[0118] refer to Figure 7 The diagram illustrates a flowchart depicting a process 700 for enhanced wireless environment reporting between peer client devices according to various embodiments of the present disclosure. In many embodiments, P2P client devices may request wireless environment reports (e.g., IEEE 802.11k reports) from each other to obtain a better perspective on how their peers view the wireless environment, thereby allowing P2P client devices to select better radio parameters.

[0119] In several embodiments, process 700 may establish communication with a peer client device (block 710). The established communication (e.g., P2P communication) may refer to the transmission and interaction between two peer client devices over a wireless network (e.g., WLAN). In various embodiments, a client device attempting to establish P2P communication may first scan for available networks and neighboring client devices. These client devices in a WLAN may utilize standard Wi-Fi scanning mechanisms to discover potential peer client devices and their capabilities, and establish P2P communication. These standard Wi-Fi scanning mechanisms can allow client devices to connect directly to each other without a central access point. For example, client devices may utilize Wi-Fi Direct® to discover other client devices that support P2P communication and establish a P2P link between them. Client devices may exchange queries and responses to identify potential peers. Client devices on the P2P link interact directly with each other. In another example, a client device may establish communication with a peer client device via a P2P protocol (such as the NAN protocol, DTLS protocol, etc.). The NAN protocol may refer to a specification configured to facilitate direct P2P communication between adjacent client devices without requiring conventional network infrastructure. The DTLS protocol can be configured to provide security for datagram-based applications, such as those using the User Datagram Protocol (UDP).

[0120] In various embodiments, process 700 may generate a wireless environment report request (block 720). In various additional embodiments, the wireless environment report request may include at least one of conditions, non-IEEE 802.11 technical specifications, or element restrictions. In more embodiments, the wireless environment report request may include P2P technical specifications. P2P technical specifications may define protocols, standards, and methods for establishing direct communication and interaction between client devices in a wireless network (e.g., WLAN) without a central access point, central server, or intermediary. In additional embodiments, the wireless environment report request may be configured to indicate the number of reported P2P pairs. In a P2P system, each P2P pair may include two peer client devices that have already established a direct P2P communication channel with each other. These two peer client devices may directly exchange data without relying on any central infrastructure or intermediary. When discovering each other through a scanning process, the two client devices may negotiate parameters, including, for example, connection security, data rate, and protocol, to establish a connection and form a P2P pair. In further embodiments, the two client devices may authenticate each other by exchanging credentials or security keys to establish secure P2P communication and form a P2P pair. In embodiments where the wireless environment reporting request includes P2P technical specifications, process 700 may allow a client device to request conditional reports, including, for example, "report P2P pairs on this channel." In further embodiments, process 700 may allow a client device to request conditional reports from peer client devices. For example, a conditional report request may include "reporting the number of access points seen by the peer client device on a particular SSID with an RSSI greater than a first threshold (e.g., 65 dBm) or an SNR less than a second threshold (e.g., 85 dBm)."

[0121] In a further embodiment, process 700 may send a wireless environment report request (block 730). The wireless environment report request can be sent from a client device to its peer client device. Process 700 may send the wireless environment report request to the peer client device via a P2P link established between the peer client devices. In a further embodiment, in order to send the wireless environment report to the peer client device, the client device may utilize an action frame having a category such as "radio measurement" or "measurement report". The action frame used to send the wireless environment report may include a header having frame control and address fields and a payload including report data.

[0122] In some further embodiments, process 700 may receive a wireless environment report (block 740). Process 700 may receive a wireless environment report from a peer client device via a P2P link based on a sent wireless environment report request. In one example, for a wireless environment report request that includes P2P technology specifications, the wireless environment report may report the number of P2P pairs on the indicated channel. Understanding the number of P2P pairs helps assess how bandwidth is being utilized. A large number of P2P connections can lead to network congestion and performance degradation, especially if many devices communicate directly with each other. The wireless environment report can provide a better perspective on how the peer client device views the wireless environment, allowing the peer client device to choose better radio parameters. In another example, for a wireless environment report request that includes P2P technology specifications, the wireless environment report may include, for example, the number of access points seen by the peer client device on a particular SSID with an indicated threshold (such as an RSSI greater than a first threshold (e.g., 65 dBm) or an SNR less than a second threshold (e.g., 85 dBm)). In some cases, the client device may not need the full wireless environment report from the peer client device, but may only need certain fields of the wireless environment report. Therefore, in another example, the wireless environment report may include only the necessary parts of the wireless environment report or only the details about an access point that is not clearly visible. In this case, the peer client device may only respond to the elements or fields requested by the client device in the wireless environment report request. In various other embodiments, the wireless environment report may be associated with conditions, non-IEEE 802.11 specifications, or element restrictions included in the wireless environment report request.

[0123] In various embodiments, process 700 may perform P2P wireless network operation (block 750). Process 700 may perform P2P wireless network operation based on received wireless environment reports. For example, upon receiving a wireless environment report indicating the number of P2P pairs on an indicated channel, process 700 may analyze the distribution of P2P pairs, identify areas with high P2P activity, and implement measures to balance the load across the network, such as by adjusting access points or optimizing network settings. Examples of P2P wireless network operation may include scanning available channels and selecting channels with minimal interference from other networks or peer client devices; selecting between 20 MHz, 40 MHz, 80 MHz, or 160 MHz channel widths; dynamically adjusting the transmit power of client devices based on distance to access points or other peer client devices to balance coverage and avoid interference; selecting data rates based on connection quality and signal strength; selecting between 2.4 GHz and 5 GHz bands based on factors such as signal strength, congestion, and the type of application being used; selecting parameters that prioritize critical traffic; creating a self-organizing P2P network, etc. In further embodiments, the wireless environment report can be used by the access point to schedule P2P switching time, detect P2P density in the cell and its impact on BSS available call time, or notify the RRM to allocate channels. In still further embodiments, based on the wireless environment report, process 700 can perform other network operations, such as P2P detection, unavailable channel detection, VLP system detection, and detection of other local RF events that may degrade the client device experience but are not directly visible to the access point.

[0124] Despite about Figure 7 Specific embodiments of a process 700 for enhanced wireless environment reporting between peer client devices performing the various steps, procedures, methods, and operations described herein are discussed. However, any of various systems and / or processes can be utilized according to embodiments of this disclosure. For example, in addition to establishing communication with a single peer client device to request a single wireless environment report, an STA or client device may simultaneously establish communication with multiple groups of peer client devices and send multiple different wireless environment report requests to these groups to receive enhanced information that may be useful to the network infrastructure. Figure 7 The elements depicted in the text can also be related to... Figure 1-6 and Figure 8 Other elements may be interchanged to achieve a particular desired implementation.

[0125] refer to Figure 8 A conceptual block diagram of a device 800 capable of executing components and logic for implementing the functions and embodiments described above is shown. Figure 8The embodiments of the conceptual block diagrams depicted herein may illustrate conventional server computers, workstations, desktop computers, laptop computers, tablets, network devices, e-readers, smartphones, or other computing devices, and may be used to execute any of the applications and / or logical components presented herein. In some examples, device(s) 800 may correspond to physical devices or virtual resources described herein. Figure 8 The conceptual block diagrams depicted herein can also illustrate access points, WLCs, client devices, etc., according to various embodiments of this disclosure. In many non-limiting examples, device 800 may correspond to the physical device or virtual resource described herein.

[0126] In many embodiments, device 800 may include environment 802, such as a substrate or “motherboard,” which in physical embodiments may be configured as a printed circuit board having numerous components or devices connected via a system bus or other electrical communication path. Conceptually, in virtualization embodiments, environment 802 may be a virtual environment that encompasses and executes the remaining components and resources of device 800. In several embodiments, one or more processors 804, such as, but not limited to, a central processing unit (CPU), may be configured to operate in conjunction with chipset 806. The processors (one or more) 804 may be standard programmable CPUs that perform the arithmetic and logical operations required to perform the operation of device 800.

[0127] In various embodiments, processor(s) 804 can perform one or more operations by manipulating switching elements that distinguish and change these states to transition from one discrete physical state to the next. Switching elements typically include electronic circuitry (such as flip-flops) that maintains one of two binary states and electronic circuitry (such as logic gates) that provides an output state based on a logical combination of the states of one or more other switching elements. These basic switching elements can be combined to create more complex logic circuits, including registers, adders / subtractors, arithmetic logic units, floating-point units, etc.

[0128] In various embodiments, chipset 806 may provide an interface between processor(s) 804 and the remaining components and devices within environment 802. Chipset 806 may provide an interface to random access memory (RAM) 808, which in some embodiments may serve as main memory in device 800. Chipset 806 may also be configured to provide an interface to computer-readable storage media, such as read-only memory (ROM) 810 or non-volatile RAM (NVRAM), for storing basic routines that can assist in various tasks, such as, but not limited to, booting device 800 and / or transferring information between various components and devices. ROM 810 or NVRAM may also store other application components required for the operation of device 800 according to the various embodiments described herein.

[0129] Different embodiments of device 800 can be configured to operate in a networked environment using logical connections to remote computing devices and computer systems via a network such as network 840. Chipset 806 may include functionality for providing network connectivity via a network interface controller (NIC) 812, which may include a Gigabit Ethernet adapter or similar component. NIC 812 enables device 800 to connect to other devices via network 840. It is conceivable that multiple NICs 812 may exist in device 800, connecting device 800 to other types of networks and remote systems.

[0130] In further embodiments, device 800 may be connected to storage device 818, which provides non-volatile storage for data accessible to device 800. Storage device 818 may, for example, store operating system 820, applications or programs 822, report request data 828, report data 830, and wireless environment data 832, which will be described in more detail below. Storage device 818 may be connected to environment 802 via storage controller 814 connected to chipset 806. In additional embodiments, storage device 818 may include one or more physical storage units. Storage controller 814 may interface with physical storage units via a Serial Attached SCSI (SAS) interface, a Serial Advanced Technology Attachment (SATA) interface, a Fibre Channel (FC) interface, or other types of interfaces for physical connection and data transfer between a computer and physical storage units.

[0131] Device 800 can store data in storage device 818 by changing the physical state of the physical storage units to reflect the information being stored. The specific changes in physical state can depend on various factors. Examples of these factors may include, but are not limited to, the technology used to implement the physical storage units, whether storage device 818 is characterized as a primary storage device or a secondary storage device, etc.

[0132] For example, device 800 can store information in storage device 818 by issuing instructions via storage controller 814 to change the magnetic properties of a specific location in a disk drive unit, the reflection or refraction properties of a specific location in an optical storage unit, or the electrical properties of a specific capacitor, transistor, or other discrete component in a solid-state storage unit. Other transformations of the physical medium are possible without departing from the scope and spirit of this description, and the foregoing examples are provided only to facilitate this description. Device 800 can also read or access information from storage device 818 by detecting the physical state or characteristics of one or more specific locations within the physical storage unit.

[0133] In addition to the aforementioned storage device 818, device 800 may access other computer-readable storage media to store and retrieve information, such as program modules, data structures, or other data. Those skilled in the art will understand that a computer-readable storage medium is any available medium that provides non-transitory storage of data and can be accessed by device 800. In some examples, operations performed by a cloud computing network and / or any components included therein may be supported by one or more devices similar to device 800. In other words, some or all of the operations performed by a cloud computing network and / or any components included therein may be performed by one or more devices 800 operating in a cloud-based configuration.

[0134] By way of example and not limitation, computer-readable storage media can include volatile and non-volatile, removable and non-removable media implemented in any method or technology. Computer-readable storage media include, but are not limited to, RAM, ROM, erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory or other solid-state memory technologies, compact disc ROM (CD-ROM), digital versatile disc (DVD), high-definition DVD (HD-DVD), Blu-ray or other optical storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information in a non-transitory manner.

[0135] As briefly mentioned above, storage device 818 may store operating system 820 for controlling the operation of device 800. According to one embodiment, operating system 820 includes a LINUX operating system. According to another embodiment, operating system 820 includes a WINDOWS® SERVER operating system from MICROSOFT Corporation of Redmond, Washington. According to a further embodiment, operating system 820 may include a UNIX operating system or a variant thereof. It should be understood that other operating systems may also be utilized. Storage device 818 may store other systems or applications and data used by device 800.

[0136] In a further embodiment, storage device 818 or other computer-readable storage medium is encoded with computer-executable instructions that, when loaded into device 800, can transform device 800 from a general-purpose computing system into a dedicated computer capable of implementing the embodiments described herein. These computer-executable instructions may be stored as an application or program 822 and transform device 800 by specifying how processor(s) 804(s) transition between states, as described above. In still more embodiments, device 800 may access a computer-readable storage medium storing computer-executable instructions that, when executed by device 800, perform the above-described... Figure 1-8 The various processes described herein. In a further embodiment, device 800 may also include a computer-readable storage medium thereon storing instructions for performing any other computer implementation of the operations described herein.

[0137] In further embodiments, device 800 may also include one or more input / output controllers 816 for receiving and processing input from multiple input devices, such as keyboards, mice, touchpads, touchscreens, electronic styluses, or other types of input devices. Similarly, input / output controllers 816 may be configured to provide output to a display, such as a computer monitor, flat panel display, digital projector, printer, or other types of output device. Those skilled in the art will recognize that device 800 may not include... Figure 8 All components shown, and may include Figure 8 Other components not explicitly shown in the document, or those that can be utilized with Figure 8 The architecture shown is completely different.

[0138] As described above, device 800 may support a virtualization layer, such as one or more virtual resources executing on device 800. In some examples, the virtualization layer may be supported by a hypervisor that provides one or more virtual machines running on device 800 to perform the functions described herein. The virtualization layer may typically support virtual resources that perform at least a portion of the techniques described herein. In some further embodiments, device 800 may include network management logic 824, which may be responsible for enhancing wireless environment reporting to optimize wireless network management. Network management logic 824 may be configured to perform various operations, such as, but not limited to: generating wireless environment report requests that include at least one of conditions, P2P technical specifications, non-IEEE 802.11 technical specifications or element restrictions, sending the generated wireless environment report requests, and receiving wireless environment reports based on the sent wireless environment report requests. In yet more various embodiments, network management logic 824 may also be responsible for enhanced P2P wireless environment reporting. In further embodiments, network management logic 824 may also be configured to perform various operations, such as, but not limited to: generating a wireless environment report request, sending the generated wireless environment report request to a peer client device via a P2P link, and receiving a wireless environment report based on the sent wireless environment report request from the peer client device via a P2P link. In additional embodiments, network management logic 824 may be configured to perform various operations, such as, but not limited to: receiving a wireless environment report request including at least one of conditions, P2P technical specifications, non-IEEE 802.11 technical specifications or element restrictions, generating a wireless environment report based on the received wireless environment report request, and sending the wireless environment report to another device, such as an access point, WLC, peer client device, etc.

[0139] In further embodiments, storage device 818 may include report request data 828. Report request data 828 may relate to data representing a wireless environment report request generated or received by device 800. For example, report request data 828 may include information about conditions, specifications, information elements, SSID, channel, or frequency band, based on which a wireless environment report can be generated.

[0140] In many further embodiments, storage device 818 may include report data 830. Report data 830 may relate to data representing wireless environment reports generated or received by device 800. Report data 830 may include, but is not limited to, SSID, BSSID, RSSI on the indicated channel or frequency band, results of standards-based evaluations including one or more logical operations, P2P communication data, channel information, maximum / minimum information, etc.

[0141] In many additional embodiments, storage device 818 may include wireless environment data 832. Wireless environment data 832 may relate to data from an RF view of the STA, which can help extend the access point view to the ground and provide information that may be useful to the network infrastructure. For example, wireless environment data 832 may include P2P communication data, VLP system information, active non-Wi-Fi radio data, RSSI and SNR data on various channels or frequency bands, channel utilization data, roaming data, etc.

[0142] Finally, in further embodiments, the data may be processed into a format available to the machine learning (“ML”) model 826 (e.g., feature vectors) and / or other preprocessing techniques. The ML model 826 may be any type of ML model, such as a supervised model, a reinforcement model, and / or an unsupervised model. The ML model 826 may include one or more of linear regression models, logistic regression models, decision trees, Naive Bayes models, neural networks, k-means clustering models, random forest models, and / or other types of ML models. The ML model 826 may be configured to analyze report request data 828, report data 830, and wireless environment data 832 to perform enhanced wireless environment reporting to optimize wireless network management. In various embodiments, the ML model 826 may be used to identify various parameters to be included in the wireless environment report request. For example, the ML model 826 may analyze the wireless environment data 832 and identify parameters needed to enhance the wireless environment data 832. Once the parameters are identified, the network management logic 824 can use these parameters (e.g., conditions, P2P specifications, non-IEEE 802.11 specifications, or element restrictions) to generate a wireless environment report request.

[0143] Despite about Figure 8 Specific embodiments of the device 800, configured with network management logic 824 to perform the various steps, processes, methods, and operations described herein, have been discussed. However, any of a variety of systems and / or processes may be utilized according to embodiments of this disclosure. For example, the device may be implemented in a virtual environment, such as a cloud-based network management suite or cloud computing environment, or the device may be distributed across various network devices, such that each device acts as a device and the network management logic 824 works collaboratively among the devices. Figure 8 The elements depicted in the text can also be related to... Figure 1-7 Other elements may be interchanged to achieve a particular desired implementation.

[0144] Although this disclosure has been described in certain specific aspects, many additional modifications and variations will be apparent to those skilled in the art. In particular, any of the various processes described above may be performed in an alternative order and / or in parallel (on the same or different computing devices) to achieve similar results in a manner more suited to the requirements of a particular application. Therefore, it should be understood that this disclosure may be practiced in ways different from those specifically described without departing from the scope and spirit of this disclosure. Accordingly, embodiments of this disclosure should be considered illustrative rather than restrictive in all respects. It will be apparent to those skilled in the art that several or all of the embodiments discussed herein may be freely combined as deemed suitable for a particular application of this disclosure. Throughout this disclosure, terms such as “advantageous,” “exemplary,” or “example” indicate elements or dimensions that are particularly suitable (but not essential) to this disclosure or its embodiments, and modifications may be made wherever a person skilled in the art deems it appropriate, unless expressly required. Therefore, the scope of this disclosure should not be determined by the embodiments shown but by the appended claims and their equivalents.

[0145] Any reference to an element in the singular is not intended to mean "one and only one," but rather "one or more," unless expressly stated otherwise. All structural and functional equivalents of the elements of the preferred and additional embodiments described above, as to those skilled in the art, are expressly incorporated herein by reference and are intended to be covered by these claims.

[0146] Furthermore, there is no requirement that the system or method solves every problem sought to be addressed by this disclosure, as solutions to these problems are covered by the claims. Moreover, no element, component, or method step in this disclosure is intended to be proprietary to the public, whether or not such element, component, or method step is expressly recited in the claims. Various changes and modifications in form, materials, workpiece, and manufacturing details may be made, as would be apparent to those skilled in the art, without departing from the spirit and scope of this disclosure as set forth in the appended claims, and these are also covered by this disclosure.

Claims

1. A network device, comprising: processor; The network interface controller is configured to provide access to the network; as well as A memory communicatively coupled to the processor, wherein the memory includes network management logic configured to: Generate a wireless environment report request, wherein the wireless environment report request includes at least one of the following: conditions, peer-to-peer (P2P) technical specifications, non-IEEE 802.11 technical specifications, or element restrictions; Send the generated wireless environment report request; and Receive wireless environment report based on the sent wireless environment report request.

2. The network device according to claim 1, wherein, The wireless environment report request includes the conditions stated above.

3. The network device according to any one of the preceding claims, wherein, The wireless environment report request is configured to indicate the excluded service set identifier (SSID).

4. The network device according to any one of the preceding claims, wherein, The wireless environment report request is configured to indicate a Service Set Identifier (SSID) and the conditions associated with the SSID.

5. The network device according to any one of the preceding claims, wherein, The wireless environment report request is configured to indicate at least one of the channels or frequency bands.

6. The network device according to claim 5, wherein, The wireless environment report request is also configured to instruct the reporting of a local service set identifier (SSID) on at least one of the indicated channels or frequency bands.

7. The network device according to claim 5 or 6, wherein, The wireless environment report request is also configured to indicate that a missing Neighbor Service Set Identifier (SSID) is reported on at least one of the indicated channels or frequency bands.

8. The network device according to claim 5, 6 or 7, wherein, The wireless environment report request is also configured to instruct that all local SSIDs be reported on at least one of the indicated channels or frequency bands based on the detection of a local service set identifier (SSID) on at least one of the indicated channels or frequency bands.

9. The network device according to any one of claims 5 to 8, wherein, The wireless environment report request is also configured to indicate that all local SSIDs are reported on at least one of the indicated channels or frequency bands, based on the fact that no local service set identifier (SSID) is detected on at least one of the indicated channels or frequency bands.

10. The network device according to any one of the preceding claims, wherein, The wireless environment report request is also configured to indicate that the report is based on the results of a standard-based evaluation.

11. The network device according to claim 10, wherein, The standards-based evaluation includes one or more logical operations.

12. The network device according to any one of the preceding claims, wherein, The wireless environment report request includes the P2P technical specifications.

13. The network device according to claim 12, wherein, The wireless environment report request is configured to indicate the number of reported P2P pairs.

14. The network device according to any one of the preceding claims, wherein, The wireless environment report request includes the non-IEEE 802.11 technical specifications.

15. The network device according to any one of the preceding claims, wherein, The wireless environment report request is configured to indicate at least one of the channels or frequency bands.

16. The network device according to any one of the preceding claims, wherein, The wireless environment report request includes the aforementioned element restrictions.

17. The network device according to any one of the preceding claims, wherein, The wireless environment report request is sent to the client device, and the wireless environment report is received from the client device.

18. A client device, comprising: processor; The network interface controller is configured to provide access to the network; as well as A memory communicatively coupled to the processor, wherein the memory includes network management logic configured to: Generate a wireless environment report, wherein the wireless environment report is associated with at least one of the following: conditions, peer-to-peer (P2P) technical specifications, non-IEEE 802.11 technical specifications, or element restrictions; and Send the aforementioned wireless environment report.

19. The client device according to claim 18, wherein, The network management logic is also configured to receive a wireless environment report request, the wireless environment report request including at least one of the conditions, the P2P technical specifications, the non-IEEE 802.11 technical specifications, or the element restrictions, and wherein the wireless environment report is generated based on the received wireless environment report request.

20. A client device, comprising: processor; The network interface controller is configured to provide access to the network; as well as A memory communicatively coupled to the processor, wherein the memory includes network management logic configured to: Generate a wireless environment report request; The generated wireless environment report request is sent to another client device via a peer-to-peer (P2P) link; and Receive a wireless environment report based on the sent wireless environment report request from the other client device via the P2P link.

21. A method comprising: Generate a wireless environment report request, which includes at least one of the following: conditions, peer-to-peer (P2P) technical specifications, non-IEEE 802.11 technical specifications, or element restrictions; Send the generated wireless environment report request; and Receive wireless environment report based on the sent wireless environment report request.

22. A method comprising: Generate a wireless environment report, wherein the wireless environment report is associated with at least one of the following: conditions, peer-to-peer (P2P) technical specifications, non-IEEE 802.11 technical specifications, or element restrictions; and Send the aforementioned wireless environment report.

23. A method comprising: Generate a wireless environment report request; The generated wireless environment report request is sent to another client device via a peer-to-peer (P2P) link; as well as Receive a wireless environment report based on the sent wireless environment report request from the other client device via the P2P link.

24. A computer-readable medium carrying instructions that, when executed by one or more processors, cause to perform the method according to any one of claims 21 to 23.

Images