Reducing beacon overhead in a mesh network

WO2026217715A3PCT designated stage Publication Date: 2026-11-12QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/022911
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-04-11
Filing Date
2026-04-08
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Wireless communication networks face increased overhead costs due to frequent beaconing, which reduces network performance, especially in networks with limited resources such as low bandwidth.

Method used

Implementing a configuration element in beacon frames that includes a file identifier to access predefined network configuration files stored in a database, allowing for compressed network configuration information, and optionally using override elements to update dynamic parameters, thereby reducing the need for full network configuration information in every beacon frame.

Benefits of technology

This approach reduces overhead airtime usage, improving spectral efficiency and network performance by conserving bandwidth and resources for data communication, particularly in networks with limited capacity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026022911_12112026_PF_FP_ABST
    Figure US2026022911_12112026_PF_FP_ABST
Patent Text Reader

Abstract

This disclosure provides methods, components, devices and systems for providing network and device configuration information in a compressed beacon frame. Some aspects more specifically relate to providing compressed network configuration information in a frame body of a beacon frame by replacing an entirety of network configuration information content provided in a standard beacon frame body with a configuration element. In some examples, the configuration element includes a file identifier identifying a predefined network configuration file stored in a configuration database. In some examples, wireless communication devices communicate network traffic via the wireless network using a network configuration selected or extracted from the predefined network configuration file in the configuration database, where the network configuration file is selected using the file identifier.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] REDUCING BEACON OVERHEAD IN A MESH NETWORK

[0002] PRIORITY INFORMATION

[0003] [1] This application claims priority to Indian Provisional Patent Application No.

[0004] 202541035551, filed April 11, 2025, and entitled “REDUCING BEACON OVERHEAD IN A MESH NETWORK,” which is expressly incorporated by reference herein.

[0005] TECHNICAL FIELD

[0006] [2] This disclosure relates generally to wireless communication, and more specifically, to providing network and device configuration information in a compressed beacon frame to improve spectral efficiency provided by reduced overhead airtime usage in a wireless network.

[0007] DESCRIPTION OF THE RELATED TECHNOLOGY

[0008] [3] Wireless communication networks may include various types of wireless communication devices including network entities (such as wireless access points (AP) or base stations (BS)), client devices (such as wireless stations (STAs) or user equipment (UEs)), and other wireless nodes. These wireless communication devices may communicate with one another via a variety of technologies and wireless communication protocols, including wireless local area network (WLAN) or Wi-Fi-based protocols or cellular (such as 4G, 5G, or 6G)-based protocols. The wireless communication networks may be capable of supporting communication with multiple users by sharing the available system resources (such as time, frequency, and spatial resources). To enable features or provide improved performance, the wireless communication devices may employ technologies such as orthogonal frequency divisional multiple access (OFDMA), multiuser Multiple-Input Multiple-Output (MU-MIMO), spatial multiplexing, and beamforming. For greater inter-operability, the wireless communication networks may support backwards compatibility (such as supporting legacy wireless communication devices) as well as forward compatibility (such as supporting communication with wireless communication devices compatible with next-generation wireless communication standards).

[0009] SUMMARY

[0010] [4] The systems, methods and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.[5] One innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. The wireless communication device includes a processing system that includes processor circuitry and memory circuitry that stores code. The processing system is configured to cause the wireless communication device to: receive a beacon frame including a frame body from a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network, and where the configuration element includes a file identifier identifying a predefined network configuration file stored in a configuration database, and communicate network traffic via the mesh wireless network using a network configuration selected from the predefined network configuration file in the configuration database using the file identifier.

[0011] [6] In some examples, the techniques described herein relate to a wireless communication device, where the configuration database includes a plurality of predefined network configuration files, and where each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body.

[0012] [7] In some examples, the techniques described herein relate to a wireless communication device, where the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body.

[0013] [8] In some examples, the techniques described herein relate to a wireless communication device, where the frame body further includes mandatory fields including a plurality of mandatory parameters, where the plurality of mandatory parameters includes one or more of: a timestamp, a beacon interval, capability information, a service set identifier (SSID), and supported rates.

[0014] [9] In some examples, the techniques described herein relate to a wireless communication device, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0015]

[0010] In some examples, the techniques described herein relate to a wireless communication device, where the at least one override element includes an override file identifier identifying a predefined sub-configuration file stored in the configurationdatabase, and where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file.

[0016]

[0011] In some examples, the techniques described herein relate to a wireless communication device, where the configuration database further includes a configuration map, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0017]

[0012] In some examples, the techniques described herein relate to a wireless communication device, where the at least one override element includes parameter information fields, and where the set of parameters in the network configuration is updated using information provided in the parameter information fields.

[0018]

[0013] In some examples, the techniques described herein relate to a wireless communication device, where the at least one override element further includes a delimiter field identifying the parameter information fields in the frame body.

[0019]

[0014] In some examples, the techniques described herein relate to a wireless communication device, where the at least one override element further includes an override file identifier identifying a predefined sub-configuration file stored in the configuration database, where the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body, and where a subset of the set of parameters in the network configuration is updated using information stored in the predefined sub-configuration file.

[0020]

[0015] In some examples, the techniques described herein relate to a wireless communication device, where a parameter of the set of parameters is associated with a plurality of parameter information elements (IES), and where the at least one override element includes: a bitmap field representing the plurality of parameter IEs, where the bitmap field identifies a number condensed subset of the plurality of parameter IEs for override, and information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of the parameter IEs.

[0021]

[0016] In some examples, the techniques described herein relate to a wireless communication device, where the configuration element includes a vendor information element (IE), where the vendor IE includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration.

[0017] In some examples, the techniques described herein relate to a wireless communication device, where the vendor IE further includes at least one field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration, and where a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0022]

[0018] In some examples, the techniques described herein relate to a wireless communication device, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0023]

[0019] In some examples, the techniques described herein relate to a wireless communication device, where the processing system is further configured to cause the wireless communication device to: count a reception of the beacon frame as a beacon miss when a beacon decode error is detected, where the beacon decode error includes at least one of: the file identifier is not found in the configuration database, a file identifier format mismatch, an override element error, and the file identifier is a misused reserved file identifier, and implement a beacon miss procedure for the mesh wireless network according to the beacon miss count.

[0024]

[0020] Another innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication device. The wireless communication device includes a processing system that includes processor circuitry and memory circuitry that stores code. The processing system is configured to cause the wireless communication device to provide a beacon frame including a frame body to a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network detected at the wireless communication device, and where the configuration element includes a file identifier identifying a predefined network configuration file selected from a configuration database, and communicate network traffic via the mesh wireless network using a network configuration associated with the predefined network configuration file in the configuration database.

[0025]

[0021] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication by a wireless communication device. The method includes receiving a beacon frame including a frame body from a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network, and where the configuration element includesa file identifier identifying a predefined network configuration file stored in a configuration database, and communicating network traffic via the mesh wireless network using a network configuration selected from the predefined network configuration file in the configuration database using the file identifier.

[0026]

[0022] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.

[0027] BRIEF DESCRIPTION OF THE DRAWINGS

[0028]

[0023] Figure 1 shows a pictorial diagram of an example wireless communication network.

[0029]

[0024] Figure 2 shows an example protocol data unit (PDU) usable for communications between a wireless access point (AP) and one or more wireless stations (STAs).

[0030]

[0025] Figure 3 shows a hierarchical format of an example PPDU usable for communications between a wireless AP and one or more wireless STAs.

[0031]

[0026] Figure 4 shows a pictorial diagram of another example wireless communication network.

[0032]

[0027] Figure 5 shows a pictorial diagram of an example mesh wireless network providing network and device configuration information in a compressed beacon frame.

[0033]

[0028] Figure 6 shows a pictorial diagram of an example network system that provides reduced beaconing overhead in a mesh network using a compressed beacon frame and configuration database.

[0034]

[0029] Figure 7 shows an example beacon frame usable for providing compressed network configuration information between wireless communication devices in a network.

[0035]

[0030] Figure 8 shows an example beacon frame with mandatory fields and usable for providing compressed network configuration information between wireless communication devices in a network.

[0036]

[0031] Figures 9A and 9B show example beacon frames with a vendor information element (IE) providing compressed network configuration information between wireless communication devices in a network.

[0032] Figures 10A and 1OB show example beacon frames with override elements usable for providing compressed network configuration information between wireless communication devices in a network.

[0037]

[0033] Figures 11A-11C show example beacon frames with override elements with delimiters, usable for providing compressed network configuration information between wireless communication devices in a network.

[0038]

[0034] Figure 12 shows an example beacon frame with an override element with a bitmap, usable for providing compressed network configuration information between wireless communication devices in a network.

[0039]

[0035] Figure 13 shows a flowchart illustrating an example process performable by or at a wireless communication device that supports providing network and device configuration information in a compressed beacon frame.

[0040]

[0036] Figure 14 shows a flowchart illustrating an example process performable by or at a wireless communication device that supports error checking a compressed beacon frame.

[0041]

[0037] Figure 15 shows a flowchart illustrating an example process performable by or at a wireless communication device that supports providing network and device configuration information in a compressed beacon frame.

[0042]

[0038] Figure 16 shows a block diagram of an example wireless communication device that supports providing network and device configuration information in a compressed beacon frame.

[0043]

[0039] Like reference numbers and designations in the various drawings indicate like elements.

[0044] DETAILED DESCRIPTION

[0045]

[0040] The following description is directed to some particular examples for the purposes of describing innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. Some or all of the described examples may be implemented in any device, system or network that is capable of transmitting and receiving radio frequency (RF) signals according to one or more of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, the IEEE 802.15 standards, the Bluetooth® standards as defined by the Bluetooth Special Interest Group (SIG), or the Long Term Evolution (LTE), 3G, 4G, 5G (New Radio (NR)) or 6G standards promulgated by the 3rdGeneration Partnership Project (3GPP), among others.

[0041] The described examples can be implemented in any suitable device, component, system or network that is capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiplexing (OFDM), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), spatial division multiple access (SDMA), rate-splitting multiple access (RSMA), multi-user shared access (MUSA), single-user (SU) multiple-input multiple-output (MEMO) and multi-user (MU)-MIMO (MU-MIMO). The described examples also can be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless personal area network (WPAN), a wireless local area network (WLAN), a wireless wide area network (WWAN), a wireless metropolitan area network (WMAN), a non-terrestrial network (NTN), or an internet of things (IOT) network.

[0046]

[0042] In some wireless communication networks, a large number of wireless communication devices may interact and communicate with other devices in the network. For example, a mesh wireless communication network may include wireless communication devices or mesh nodes that frequently communicate with neighboring devices in the mesh wireless communication network. In some examples, the mesh nodes and other wireless communication devices in the mesh wireless network may move frequently or encounter network environment conditions where network configurations and conditions frequently change or update. In some examples, the device movement and frequent updates results in an increase in the amount of beaconing needed in the network to provide the changing network configuration information through the network. For example, the mesh nodes in the mesh wireless communication network may increase a number of beacon frames provided to the other devices in the network as the frequency of changes and updates in the network occurs. In some examples, mesh wireless communication networks may have limited network resources, such as low bandwidth capacity, where increased beaconing may also increase the overhead costs on the network. In some examples, increased overhead costs may result in reduced network performance, where network data traffic and other information is not quickly or reliably provided through the wireless communication network.

[0047]

[0043] Various aspects relate generally to wireless communication and more particularly to improving spectral efficiency in a wireless network by reducing overhead airtime usage. Some aspects more specifically relate to providing network and device configuration information in a compressed beacon frame. In some aspects, compressednetwork configuration information is provided in a frame body of a beacon frame by replacing an entirety of network configuration information content provided in a standard beacon frame body with a configuration element. In some aspects, the configuration element includes a file identifier identifying a predefined network configuration file stored in a configuration database. In some examples, wireless communication devices communicate network traffic via the wireless network using a network configuration selected or extracted from the predefined network configuration file in the configuration database, where the network configuration file is selected using the file identifier. In some examples, the configuration database is locally stored on each wireless communication device in the wireless communication network and includes multiple predefined network configuration files. In some examples, each predefined network configuration file stored in the configuration database includes content or values for at least one network configuration parameter defining network configuration information included in a standard beacon frame body. In some examples, the beacon frame supports compatibility with various communication protocol standards by including mandatory fields such as a timestamp, a beacon interval, capability information, a service set identifier (SSID), and supported rates in the frame body.

[0048]

[0044] In some aspects, the configuration element may also include a vendor information element (IE), where the vendor IE includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration. In some examples, the vendor IE may also include a field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration, where a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0049]

[0045] In some aspects, the configuration element may also include override elements to update dynamic or semi-static network configuration parameters in a network configuration. In some examples, the override element includes an override file identifier that identifies a predefined sub-configuration file that is also stored in the configuration database, where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file. In some examples, the override element includes parameter information fields, where the set of parameters in the network configuration is updated using information provided in the parameter information fields. In some examples, the configuration database includes a configuration map that provides an identification of a format for the override element. In some examples, the override element also includes a delimiter identifying the format ofthe override element and the parameter information fields in the frame body. In some examples, the configuration element may also include a bitmap field representing parameter information elements (IES) for a network parameter, where the bitmap field also identifies a number of parameter IEs for override. In some examples, the configuration element includes information to override the number of the parameter IEs without including a non-bitmap representation of every parameter IE.

[0050]

[0046] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. Compressed network configuration information in beacon frames provides for improved network performance by reducing overhead resource usage, including reduced airtime used by overhead signaling. By reducing the overhead of the wireless network more bandwidth and other network resources may be used to communicate network traffic between wireless communication devices in a wireless communication network. More specifically, overhead reduction can improve network performance in low capacity wireless communication networks, such as networks with low bandwidth or other limited network resources.

[0051]

[0047] The compressed network configuration information can be provided in several different formats in a configuration element according to the needs and format of the wireless communication network. For example, the configuration element may reduce an overall size of a beacon frame by replacing an entirety of network configuration information content provided in a standard beacon frame body with a vendor IE or file identifier for a network configuration. In some examples, the configuration element also provides for a compressed beacon and reduced overhead by also including override elements to override or update network configuration information that is semi-static or dynamic. In some examples, further compression and overhead reduction is provided by bitmap representation of changing network parameters, where the override element only includes specific information for changing identified parameters in the override element.

[0052]

[0048] Figure 1 shows a pictorial diagram of an example wireless communication network 100. According to some aspects, the wireless communication network 100 can be an example of a wireless local area network (WLAN) such as a Wi-Fi network. For example, the wireless communication network 100 can be a network implementing at least one of the IEEE 802.11 family of wireless communication protocol standards, such as defined by the IEEE 802.11-2020 specification or amendments thereof (including, but not limited to, 802.1 lay, 802.1 lax (also referred to as Wi-Fi 6), 802.11 az, 802.11ba, 802.1 Ibc, 802.1 Ibd, 802.1 Ibe (also referred to as Wi-Fi 7), 802.1 Ibf, and 802.1 Ibn (alsoreferred to as Wi-Fi 8)) or other WLAN or Wi-Fi standards, such as that associated with the Integrated Millimeter Wave (IMMW) study group. In some other examples, the wireless communication network 100 can be an example of a cellular radio access network (RAN), such as a 5G or 6G RAN that implements one or more cellular protocols such as those specified in one or more 3GPP standards. In some other examples, the wireless communication network 100 can include a WLAN that functions in an interoperable or converged manner with one or more cellular RANs to provide greater or enhanced network coverage to wireless communication devices within the wireless communication network 100 or to enable such devices to connect to a cellular network’s core, such as to access the network management capabilities and functionality offered by the cellular network core. In some other examples, the wireless communication network 100 can include a WLAN that functions in an interoperable or converged manner with one or more personal area networks, such as a network implementing Bluetooth or other wireless technologies, to provide greater or enhanced network coverage or to provide or enable other capabilities, functionality, applications or services.

[0053]

[0049] The wireless communication network 100 may include numerous wireless communication devices including a wireless access point (AP) 102 and any number of wireless stations (STAs) 104. While only one AP 102 is shown in Figure 1, the wireless communication network 100 can include multiple APs 102 (for example, in an extended service set (ESS) deployment, enterprise network or AP mesh network), or may not include any AP at all (for example, in an independent basic service set (IBSS) such as a peer-to-peer (P2P) network or other ad hoc network). The AP 102 can be or represent various different types of network entities including, but not limited to, a home networking AP, an enterprise-level AP, a single-frequency AP, a dual-band simultaneous (DBS) AP, a tri -band simultaneous (TBS) AP, a standalone AP, a non- standalone AP, a software-enabled AP (soft AP), and a multi-link AP (also referred to as an AP multi-link device (MLD)), as well as cellular (such as 3GPP, 4G LTE, 5G or 6G) base stations or other cellular network nodes such as a Node B, an evolved Node B (eNB), a gNB, a transmission reception point (TRP) or another type of device or equipment included in a radio access network (RAN), including Open-RAN (O-RAN) network entities, such as a central unit (CU), a distributed unit (DU) or a radio unit (RU).

[0054]

[0050] Each of the STAs 104 also may be referred to as a mobile station (MS), a mobile device, a mobile handset, a wireless handset, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, among other examples. The STAs 104 may represent various devices such as mobile phones, other handheld orwearable communication devices, netbooks, notebook computers, tablet computers, laptops, Chromebooks, augmented reality (AR), virtual reality (VR), mixed reality (MR) or extended reality (XR) wireless headsets or other peripheral devices, wireless earbuds, other wearable devices, display devices (for example, TVs, computer monitors or video gaming consoles), video game controllers, navigation systems, music or other audio or stereo devices, remote control devices, printers, kitchen appliances (including smart refrigerators) or other household appliances, key fobs (for example, for passive keyless entry and start (PKES) systems), Internet of Things (loT) devices, and vehicles, among other examples.

[0055]

[0051] A single AP 102 and an associated set of STAs 104 may be referred to as an infrastructure basic service set (BSS), which is managed by the respective AP 102.

[0056] Figure 1 additionally shows an example coverage area 108 of the AP 102, which may represent a basic service area (BSA) of the wireless communication network 100. The BSS may be identified by STAs 104 and other devices by a service set identifier (SSID), as well as a basic service set identifier (BSSID), which may be a medium access control (MAC) address of the AP 102. The AP 102 may periodically broadcast beacon frames (“beacons”) including the BSSID to enable any STAs 104 within wireless range of the AP 102 to “associate” or re-associate with the AP 102 to establish a respective communication link 106 (hereinafter also referred to as a “Wi-Fi link”), or to maintain a communication link 106, with the AP 102. For example, the beacons can include an identification or indication of a primary channel used by the respective AP 102 as well as a timing synchronization function (TSF) for establishing or maintaining timing synchronization with the AP 102. The AP 102 may provide access to external networks to various STAs 104 in the wireless communication network 100 via respective communication links 106.

[0057]

[0052] To establish a communication link 106 with an AP 102, each of the STAs 104 is configured to perform passive or active scanning operations (“scans”) on frequency channels in one or more frequency bands (for example, the 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, or 60 GHz bands). To perform passive scanning, a STA 104 listens for beacons, which are transmitted by respective APs 102 at periodic time intervals referred to as target beacon transmission times (TBTTs). To perform active scanning, a STA 104 generates and sequentially transmits probe requests on each channel to be scanned and listens for probe responses from APs 102. Each STA 104 may identify, determine, ascertain, or select an AP 102 with which to associate in accordance with the scanning information obtained through the passive or active scans, and to perform authenticationand association operations to establish a communication link 106 with the selected AP 102. The selected AP 102 assigns an association identifier (AID) to the STA 104 at the culmination of the association operations, which the AP 102 uses to track the STA 104.

[0058]

[0053] As a result of the increasing ubiquity of wireless networks, a STA 104 may have the opportunity to select one of many BSSs within range of the STA 104 or to select among multiple APs 102 that together form an extended service set (ESS) including multiple connected BSSs. For example, the wireless communication network 100 may be connected to a wired or wireless distribution system that may enable multiple APs 102 to be connected in such an ESS. As such, a STA 104 can be covered by more than one AP 102 and can associate with different APs 102 at different times for different transmissions. Additionally, after association with an AP 102, a STA 104 also may periodically scan its surroundings to find a more suitable AP 102 with which to associate. For example, a STA 104 that is moving relative to its associated AP 102 may perform a “roaming” scan to find another AP 102 having more desirable network characteristics such as a greater received signal strength indicator (RS SI) or a reduced traffic load.

[0059]

[0054] In some examples, STAs 104 may form networks without APs 102 or other equipment other than the STAs 104 themselves. One example of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may alternatively be referred to as mesh networks or peer-to-peer (P2P) networks. In some examples, ad hoc networks may be implemented within a larger network such as the wireless communication network 100. In such examples, while the STAs 104 may be capable of communicating with each other through the AP 102 using communication links 106, STAs 104 also can communicate directly with each other via direct wireless communication links 110. Additionally, two STAs 104 may communicate via a direct wireless communication link 110 regardless of whether both STAs 104 are associated with and served by the same AP 102. In such an ad hoc system, one or more of the STAs 104 may assume the role filled by the AP 102 in a BSS. Such a STA 104 may be referred to as a group owner (GO) and may coordinate transmissions within the ad hoc network. Examples of direct wireless communication links 110 include Wi-Fi Direct connections, connections established by using a Wi-Fi Tunneled Direct Link Setup (TDLS) link, and other P2P group connections.

[0060]

[0055] In some networks, the AP 102 or the STAs 104, or both, may support applications associated with high throughput or low-latency requirements, or may provide lossless audio to one or more other devices. For example, the AP 102 or the STAs 104 may support applications and use cases associated with ultra-low-latency(ULL), such as ULL gaming, or streaming lossless audio and video to one or more personal audio devices (such as peripheral devices) or AR. / VR. / MR. / XR. headset devices. In scenarios in which a user uses two or more peripheral devices, the AP 102 or the STAs 104 may support an extended personal audio network enabling communication with the two or more peripheral devices. Additionally, the AP 102 and STAs 104 may support additional ULL applications such as cloud-based applications (such as VR cloud gaming) that have ULL and high throughput requirements.

[0061]

[0056] As indicated above, in some implementations, the AP 102 and the STAs 104 may function and communicate (via the respective communication links 106) according to one or more of the IEEE 802.11 family of wireless communication protocol standards. These standards define the WLAN radio and baseband protocols for the physical (PHY) and MAC layers. The AP 102 and STAs 104 transmit and receive wireless communications (hereinafter also referred to as “Wi-Fi communications” or “wireless packets”) to and from one another in the form of PHY protocol data units (PPDUs).

[0062]

[0057] Each PPDU is a composite structure that includes a PHY preamble and a payload that is in the form of a PHY service data unit (PSDU). The information provided in the preamble may be used by a receiving device to decode the subsequent data in the PSDU. In instances in which a PPDU is transmitted over a bonded or wideband channel, the preamble fields may be duplicated and transmitted in each of multiple component channels. The PHY preamble may include both a legacy portion (or “legacy preamble”) and a non-legacy portion (or “non-legacy preamble”). The legacy preamble may be used for packet detection, automatic gain control and channel estimation, among other uses. The legacy preamble also may generally be used to maintain compatibility with legacy devices. The format of, coding of, and information provided in the non-legacy portion of the preamble is associated with the particular IEEE 802.11 wireless communication protocol to be used to transmit the payload.

[0063]

[0058] The APs 102 and STAs 104 in the wireless communication network 100 may transmit PPDUs over an unlicensed spectrum, which may be a portion of spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, and 60 GHz bands. Some examples of the APs 102 and STAs 104 described herein also may communicate in other frequency bands that may support licensed or unlicensed communications. For example, the APs 102 or STAs 104, or both, also may be capable of communicating over licensed operating bands, where multiple operators may have respective licenses to operate in the same or overlapping frequency ranges. Such licensed operating bands may map to or be associated with frequency rangedesignations of FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz).

[0064]

[0059] Each of the frequency bands may include multiple sub-bands and frequency channels (also referred to as subchannels). The terms “channel” and “subchannel” may be used interchangeably herein, as each may refer to a portion of frequency spectrum within a frequency band (for example, a 20 MHz, 40 MHz, 80 MHz, or 160 MHz portion of frequency spectrum) via which communication between two or more wireless communication devices can occur. For example, PPDUs conforming to the IEEE 802.1 In, 802.1 lac, 802.1 lax, 802.11be and 802.11bn standard amendments may be transmitted over one or more of the 2.4 GHz, 5 GHz, or 6 GHz bands, each of which is divided into multiple 20 MHz channels. As such, these PPDUs are transmitted over a physical channel having a minimum bandwidth of 20 MHz, but larger channels can be formed through channel bonding. For example, PPDUs may be transmitted over physical channels having bandwidths of 40 MHz, 80 MHz, 160 MHz, 240 MHz, 320 MHz, 480 MHz, or 640 MHz by bonding together multiple 20 MHz channels.

[0065]

[0060] An AP 102 may determine or select an operating or operational bandwidth for the STAs 104 in its BSS and select a range of channels within a band to provide that operating bandwidth. For example, the AP 102 may select sixteen 20 MHz channels that collectively span an operating bandwidth of 320 MHz. Within the operating bandwidth, the AP 102 may typically select a single primary 20 MHz channel on which the AP 102 and the STAs 104 in its BSS monitor for contention-based access schemes. In some examples, the AP 102 or the STAs 104 may be capable of monitoring only a single primary 20 MHz channel for packet detection (for example, for detecting preambles of PPDUs). Conventionally, any transmission by an AP 102 or a STA 104 within a BSS must involve transmission on the primary 20 MHz channel. As such, in conventional systems, the transmitting device must contend on and win a TXOP on the primary channel to transmit anything at all. However, some APs 102 and STAs 104 supporting ultra-high reliability (UHR) communications or communication according to the IEEE 802.1 Ibn standard amendment can be configured to operate, monitor, contend and communicate using multiple primary 20 MHz channels. Such monitoring of multiple primary 20 MHz channels may be sequential such that responsive to determining, ascertaining or detecting that a first primary 20 MHz channel is not available, a wireless communication device may switch to monitoring and contending using a second primary 20 MHz channel. Additionally, or alternatively, a wireless communication device maybe configured to monitor multiple primary 20 MHz channels in parallel. In some examples, a first primary 20 MHz channel may be referred to as a main primary (M-Primary) channel and one or more additional, second primary channels may each be referred to as an opportunistic primary (O-Primary) channel. For example, if a wireless communication device measures, identifies, ascertains, detects, or otherwise determines that the M-Primary channel is busy or occupied (such as due to an overlapping BSS (OBSS) transmission), the wireless communication device may switch to monitoring and contending on an O-Primary channel. In some examples, the M-Primary channel may be used for beaconing and serving legacy client devices and an O-Primary channel may be specifically used by non-legacy (for example, UHR- or IEEE 802.1 Ibn-compatible) devices for opportunistic access to spectrum that may be otherwise under-utilized.

[0066]

[0061] The AP 102 and the STAs 104 of the wireless communication network 100 may implement technologies, protocols or procedures compliant with current and future generations of the IEEE 802.11 family of wireless communication protocol standards, such as Extremely High Throughput (EHT) operation defined by the IEEE 802.1 Ibe standard amendment and Ultra-High Reliability (UHR) operation defined by the IEEE 802.1 Ibn standard amendments, to enable additional capabilities or features relative to previous generations, such as devices supporting only legacy operation such as Very High Throughput (VHT) operation defined by the 802.1 lac standard amendment or High Efficiency (HE) operation defined by the IEEE 802.1 lax standard amendment. For example, the IEEE 802.1 Ibe standard amendment introduced 320 MHz channels, which are twice as wide as those possible with the IEEE 802.1 lax standard amendment.

[0067] Accordingly, the AP 102 or the STAs 104 may use 320 MHz channels enabling double the throughput and network capacity, as well as providing rate versus range gains at high data rates due to linear bandwidth versus log SNR trade-off. EHT, UHR or other newer wireless communication protocols may support flexible operating bandwidth enhancements, such as broadened operating bandwidths relative to legacy operating bandwidths or more granular operation relative to legacy operation. For example, an EHT system may allow communications spanning operating bandwidths of 20 MHz, 40 MHz, 80 MHz, 160 MHz, 240 MHz, and 320 MHz while a UHR system may enable communications spanning even greater bandwidths, such as 480 MHz, 640 MHz or greater. EHT systems may, for example, support multiple bandwidth modes such as a contiguous 240 MHz bandwidth mode, a contiguous 320 MHz bandwidth mode, a noncontiguous 160+160 MHz bandwidth mode, or a noncontiguous 80+80+80+80 (or “4x80”) MHz bandwidth mode.

[0062] In some examples in which a wireless communication device (such as the AP 102 or the STA 104) operates in a contiguous 320 MHz bandwidth mode or a 160+160 MHz bandwidth mode, signals for transmission may be generated by two different transmit chains of the wireless communication device each having or associated with a bandwidth of 160 MHz (and each coupled to a different power amplifier). In some other examples, two transmit chains can be used to support a 240 MHz / 160+80 MHz bandwidth mode by puncturing 320 MHz / 160+160 MHz bandwidth modes with one or more 80 MHz subchannels. For example, signals for transmission may be generated by two different transmit chains of the wireless communication device each having a bandwidth of 160 MHz with one of the transmit chains outputting a signal having an 80 MHz subchannel punctured therein. In some other examples in which the wireless communication device may operate in a contiguous 240 MHz bandwidth mode, or a noncontiguous 160 + 80 MHz bandwidth mode, the signals for transmission may be generated by three different transmit chains of the wireless communication device, each having a bandwidth of 80 MHz. In some other examples, signals for transmission may be generated by four or more different transmit chains of the wireless communication device, each having a bandwidth of 80 MHz.

[0068]

[0063] In noncontiguous examples, the operating bandwidth may span one or more disparate sub-channel sets. For example, the 320 MHz bandwidth may be contiguous and located in the same 6 GHz band or noncontiguous and located in different bands or regions within a band (such as partly in the 5 GHz band and partly in the 6 GHz band).

[0069]

[0064] In some examples, the AP 102 or the STA 104 may benefit from operability enhancements associated with EHT, UHR and newer generations of the IEEE 802.11 family of wireless communication protocol standards. For example, the AP 102 or the STA 104 attempting to gain access to the wireless medium of the wireless communication network 100 may perform techniques (which may include modifications to existing rules, structure, or signaling implemented for legacy systems) such as clear channel assessment (CCA) operation based on EHT or UHR enhancements such as increased bandwidth, puncturing, or refinements to carrier sensing and signal reporting mechanisms.

[0070]

[0065] Transmitting and receiving devices AP 102 and STA 104 may support the use of various modulation and coding schemes (MCSs) to transmit and receive data in the wireless communication network 100 so as to optimally take advantage of wireless channel conditions, for example, to increase throughput, reduce latency, or enforce various quality of service (QoS) parameters. For example, existing technology (such asIEEE 802.1 lax standard amendment protocols) supports the use of up to 1024-quadrature amplitude modulation (QAM), where a modulated symbol carries 10 bits. To further improve peak data rate, each of the AP 102 or the STA 104 may employ use of 4096-QAM (also referred to as “4k QAM”), which enables a modulated symbol to carry 12 bits. 4k QAM may enable massive peak throughput with a maximum theoretical PHY rate of 10 bps / Hz / subcarrier / spatial stream, which translates to 23 Gbps with 5 / 6 LDPC code (10 bps / Hz / subcarrier / spatial stream * 996*4 subcarriers * 8 spatial streams / 13.6 ps per OFDM symbol). The AP 102 or the STA 104 using 4096-QAM may enable a 20% increase in data rate compared to 1024-QAM given the same coding rate, thereby allowing users to obtain higher transmission efficiency.

[0071]

[0066] Figure 2 shows an example protocol data unit (PDU) 200 usable for wireless communication between a wireless AP and one or more wireless STAs. For example, the AP and STAs may be examples of the AP 102 and the STAs 104 described with reference to Figure 1. The PDU 200 can be configured as a PPDU. As shown, the PDU 200 includes a PHY preamble 202 and a PHY payload 204. For example, the preamble 202 may include a legacy portion that itself includes a legacy short training field (L-STF) 206, which may consist of two symbols, a legacy long training field (L-LTF) 208, which may consist of two symbols, and a legacy signal field (L-SIG) 210, which may consist of two symbols. The legacy portion of the preamble 202 may be configured according to the IEEE 802.1 la wireless communication protocol standard. The preamble 202 also may include a non-legacy portion including one or more non-legacy fields 212, for example, conforming to one or more of the IEEE 802.11 family of wireless communication protocol standards.

[0072]

[0068] Figure 3 shows a hierarchical format of an example PPDU usable for communications between a wireless AP and one or more wireless STAs. For example, the AP and STAs may be examples of the AP 102 and the STAs 104 described with reference to Figure 1. As described, each PPDU 300 includes a PHY preamble 302 and a PSDU 304. Each PSDU 304 may represent (or “carry”) one or more MAC protocol data units (MPDUs) 316. For example, each PSDU 304 may carry an aggregated MPDU (A-MPDU) 306 that includes an aggregation of multiple A-MPDU subframes 308. Each A-MPDU subframe 306 may include an MPDU frame 310 that includes a MAC delimiter 312 and a MAC header 314 prior to the accompanying MPDU 316, which includes the data portion (“payload” or “frame body”) of the MPDU frame 310. Each MPDU frame 310 also may include a frame check sequence (FCS) field 318 for error detection (for example, the FCS field 318 may include a cyclic redundancy check (CRC)) and paddingbits 320. The MPDU 316 may carry one or more MAC service data units (MSDUs) 316. For example, the MPDU 316 may carry an aggregated MSDU (A-MSDU) 322 including multiple A-MSDU subframes 324. Each A-MSDU subframe 324 may be associated with an MSDU frame 326 and may contain a corresponding MSDU 330 preceded by a subframe header 328 and, in some examples, followed by padding bits 332.

[0073]

[0069] Referring back to the MPDU frame 310, the MAC delimiter 312 may serve as a marker of the start of the associated MPDU 316 and indicate the length of the associated MPDU 316. The MAC header 314 may include multiple fields containing information that defines or indicates characteristics or attributes of data encapsulated within the frame body. The MAC header 314 includes a duration field indicating a duration extending from the end of the PPDU until at least the end of an acknowledgment (ACK) or Block ACK (BA) of the PPDU that is to be transmitted by the receiving wireless communication device. The use of the duration field serves to reserve the wireless medium for the indicated duration, and enables the receiving device to establish its network allocation vector (NAV). The MAC header 314 also includes one or more fields indicating addresses for the data encapsulated within the frame body. For example, the MAC header 314 may include a combination of a source address, a transmitter address, a receiver address or a destination address. The MAC header 314 may further include a frame control field containing control information. The frame control field may specify a frame type, for example, a data frame, a control frame, or a management frame.

[0074]

[0070] In some wireless communication systems, wireless communication between an AP 102 and an associated STA 104 can be secured. For example, either an AP 102 or a STA 104 may establish a security key for securing wireless communication between itself and the other device and may encrypt the contents of the data and management frames using the security key. In some examples, the control frame and fields within the MAC header of the data or management frames, or both, also may be secured either via encryption or via an integrity check (for example, by generating a message integrity check (MIC) for one or more relevant fields).

[0075]

[0071] Figure 4 shows a pictorial diagram of another example wireless communication network 400. According to some aspects, the wireless communication network 400 can be an example of a mesh network, an loT network or a sensor network in accordance with one or more of the IEEE 802.11 family of wireless communication protocol standards (including the 802.11 ah amendment). The wireless communication network 400 may include multiple wireless communication devices 414, which in some implementations may include APs 402, STAs 404, or both. The wireless communicationdevices 414 may represent various devices such as display devices (for example, TVs, computer monitors, navigation systems, among others), music or other audio or stereo devices, remote control devices (“remotes”), printers, kitchen or other household appliances, among other examples.

[0076]

[0072] In some examples, the wireless communication devices 414 sense, measure, collect or otherwise obtain and process data and transmit such raw or processed data to an intermediate device 412 for subsequent processing or distribution. Additionally, or alternatively, the intermediate device 412 may transmit control information, digital content (for example, audio or video data), configuration information or other instructions to the wireless communication devices 414. The intermediate device 412 and the wireless communication devices 414 can communicate with one another via wireless communication links 416. In some examples, the wireless communication links 416 include Bluetooth links, or other PAN or short-range communication links.

[0077]

[0073] In some examples, the intermediate device 412 also may be configured for wireless communication with other networks such as with a WLAN or a wireless (for example, cellular) wide area network (WWAN), which may, in turn, provide access to external networks including the Internet. For example, the intermediate device 412 may associate and communicate, over a Wi-Fi link 418, with an AP 402 of a wireless communication network 400, which also may serve various STAs 404. In some examples, the intermediate device 412 is an example of a network gateway, for example, an loT gateway. In such a manner, the intermediate device 412 may serve as an edge network bridge providing a Wi-Fi core backhaul for the loT network including the wireless communication devices 414. In some examples, the intermediate device 412 can analyze, preprocess and aggregate data received from the wireless communication devices 414 locally at the edge before transmitting it to other devices or external networks via the Wi-Fi link 418. The intermediate device 412 also can provide additional security for the loT network and the data it transports.

[0078]

[0074] Some processes, methods, operations, techniques or other aspects described herein may be implemented, at least in part, using an artificial intelligence (Al) program, such as a program that includes a machine learning (ML) or artificial neural network (ANN) model, hereinafter referred to generally as an AI / ML model. One or more AI / ML models may be implemented in wireless communication devices (for example, APs 102 and STAs 104) to enhance various aspects associated with wireless communication. For example, an AI / ML model may be trained to identify patterns or relationships in data observed in a wireless communication network 100. An AI / ML model may supportoperational decisions implemented by one or more wireless communication devices relating to aspects described herein that are associated with wireless communications networks or services. For example, an AI / ML model may be utilized for supporting or improving aspects such as reducing signaling overhead (such as by CSI feedback compression, etc.), enhancing roaming or other mobility operations, multi-AP coordination, and generally facilitating network management or optimizing network connections or characteristics to, for example, increase throughput or capacity, reduce latency or otherwise enhance user experience.

[0079]

[0075] Figure 5 shows a pictorial diagram of an example mesh wireless network 500 providing network and device configuration information in a compressed beacon frame. In some implementations, the mesh wireless network 500 includes multiple wireless communication devices communicating in the mesh wireless network 500 as mesh nodes or other mesh devices. In some examples, the mesh nodes may include a variety of wireless communication devices including any combination of APs 102 and STAs 104, described with reference to Figure 1, APs 402, STAs 404, intermediate device 412 and wireless communication devices 414, described with reference to Figure 4. In some examples, the mesh wireless network 500 has a constrained or limited communication wireless communication capacity, such as low bandwidth in the communication links between the devices. In some examples, the various devices in the mesh wireless network 500 may operate to limit or minimize network overheads including limiting or reducing the overhead due to management signaling as described in more detail herein.

[0080]

[0076] In some examples, the mesh wireless network 500 is an unmanned aerial vehicle (UAV) network that provides communication and control for UAVs via a Wi-Fi network implementing or using the IEEE 802. Ils mesh networking protocol. For example, the mesh wireless network 500 includes UAV 505, UAV 510, UAV 515, UAV 520, controller 530 and AP 540. In some examples, the devices in the mesh wireless network 500 communicate via mesh links 550. In some examples, a UAV network may include various performance parameters or indicators to provide an efficient UAV network. For example, UAVs 500-520 in the mesh wireless network 500 may meet performance factors including low latency in multi hop mesh networks, fast adaptation to varying network topologies, zero downtime path change, ability to multicast / broadcast UAV-generated data to multiple sink devices, such as the controller 530 and AP 540, and to scale to a large number of devices.

[0081]

[0077] In some examples, the mesh links 550 have limited network capacity, such as limited bandwidth or other similar network factors. In some examples, the devices in themesh wireless network 500, including the UAVs 505-525 may frequently change location or related aspect that results in a frequently changing network topology for the mesh wireless network 500. In some examples, as the network topology of the mesh wireless network 500 changes, the devices including the UAVs 505-525, controller 530, and AP 540 send and receive management frames, such as beacon frames, to indicate the updated network conditions and network topology to the other devices in the network and in order to meet the performance factors for the UAV network. In some examples, the frequent changing and updating of the network topology and associated beaconing between the devices may result in network degradation due to network resources being utilized by network overhead caused by the management signaling or beaconing. In some examples, the devices in the mesh wireless network 500 provide for reduced network overhead by reducing or compressing the size of the management signals, including reduced or compressed beacon frames as described in more detail in relation to Figure 6.

[0082]

[0078] Figure 6 shows a pictorial diagram of an example network system 600 that provides reduced beaconing overhead in a mesh network using a compressed beacon frame and configuration database. In some examples, the network system 600 includes wireless communication devices from the mesh wireless network 500, such as the UAV 505 and the UAV 510, described with reference to Figure 5. In some examples, the UAV 505 and UAV 510 communicate via the mesh link 550 as also described with reference to Figure 5. In some examples, the communication between the devices on the mesh link 550 includes management signaling, such as beacon frames, that provides information representing the network conditions, network topology, device capabilities and other information for a network configuration. In some examples, the UAVs 505 and 510 each include a configuration module 610 that generates beacon frames 615 that are provided to other devices in the network, including being transmitted or broadcast via the mesh links 550 or other network connection.

[0083]

[0079] In some examples, the UAVs 505 and 510 also include a configuration database 650 which may also include a configuration map 655 and network configuration files 670. In some examples, the configuration database 650 is a database that is installed on a wireless communication device during a device setup, such as at a time of device manufacture, a device connection to a network or during an update of the device enabling connection to the mesh wireless network 500. In some examples, the network configuration files 670 includes multiple predefined network configuration files. In some examples, each predefined network configuration file in the network configuration files670 includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body. For example, a configuration file may include values or content for a network parameter of the network configuration where the parameters include a timestamp, beacon interval, capability information for the device and network, SSID information, supported rates, a traffic indication map (TIM) and parameter sets for frequency hopping, sequencing, contention and IBSS, among other parameters and network information. In some examples, the network configuration files 670 may also include information for optional parameters such as a transmit power control (TPC) report, information for network / device capabilities such as High Throughput (HT) Capabilities, configurations information such as spatial reuse parameters, and reports, such as a reduced neighbor report.

[0084]

[0080] In some examples, the network configuration information may include static information such as an SSID parameter set, country information, and HT capabilities as well as dynamic information such as the TIM and a BSS load. In some examples, a network configuration file may include information for one parameter or any combination of parameters, including information for an entire network configuration that would be represented in a standard beacon frame body. In some examples, the use of the compressed beacon frames 615 and the configuration database 650 provides for the UAVs and other devices in the mesh wireless network 500 to reduce overhead costs and meet performance factors including low latency in multi hop mesh networks, fast adaptation to varying network topologies, zero downtime path change, ability to multicast / broadcast UAV-generated data to multiple sink devices, such as the controller 530 and AP 540, and to scale to a large number of devices, as described with reference to Figure 5.

[0085]

[0081] In some implementations, the configuration module 610 provides, transmits or broadcasts beacon frames, such as the beacon frames 615, for the respective wireless communication device, such as the UAV 505 and the UAV 510. In some examples, the configuration module 610 also receives beacon frames, such as the beacon frames 615, from the other wireless communication devices in the network. In some examples, the beacon frames 615 include a frame body that includes a configuration element with compressed network configuration information for a mesh wireless network, such as the mesh wireless network 500 described with reference to Figure 5. In some examples, the configuration element includes a file identifier identifying a predefined network configuration file stored in a configuration database. In some examples, the configuration element includes a vendor information element (IE) identifying apredefined network configuration file stored in a configuration database. In some examples, the configuration element may also include other compressed network configuration information that alters or updates the network configuration in the identified predefined network configuration file. For example, the configuration element may include override elements that include information to override a set of parameters defined in the network configuration.

[0086]

[0082] In some examples, the configuration module 610 communicates network traffic via the mesh wireless network, such as the mesh wireless network 500, using a network configuration selected from the predefined network configuration file in the configuration database 650 using the file identifier. For example, the configuration module 610 may select a file from the network configuration files 670 using the file identifier and extract or select a network configuration from the selected configuration file and communicate with the other devices in the mesh wireless network 500 using the network configuration. In some examples, the beacon frame 615 including the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body as described in more detail with reference to Figures 7-11C herein.

[0087]

[0083] Figure 7 shows an example beacon frame 700 usable for providing compressed network configuration information between wireless communication devices in a network. In some examples, the beacon frame 700 is or is a part of a PDU, such as the PDU 200 described with reference to Figure 2 and the PPDU 300 described with reference to Figure 3. In some examples, the beacon frame 700 is a Wi-Fi beacon frame as defined by the IEEE 802.11 set of standards. In another example, the beacon frame 700 is a management frame used in other types of networks to communicate network configuration and other information to devices in the network. As network conditions and topologies change in a wireless network, the wireless communication devices in the wireless network send and receive beacon frames to propagate the network changes and updates throughout the network. In some examples, in order to avoid high network overhead costs and network congestion that may be caused by frequent beaconing in the network, the wireless communication devices, such as those described with reference to Figures 5 and 6, utilize the beacon frame 700 to provide compressed network configuration information. In some examples, the smaller or compressed size of the beacon frame 700 conserves network resources and prevents network degradation due to high overhead communication.

[0084] In some examples, the beacon frame 700 includes various fields and frame elements that include information for communicating the beacon frame 700, such as a header and frame check sequence (FCS), as well as network configuration information. For example, the beacon frame 700 includes a header 705, a frame body 710 and an FCS 715. In some examples, the header 705 is a medium access control (MAC) header, such as a MAC header defined in the IEEE 802.11 set of standards. In some examples, the compressed network configuration information for the beacon frame 700 is provided in the frame body 710.

[0088]

[0085] For example, the frame body 710 may include a configuration element 720 that includes a file identifier (ID) identifying a predefined network configuration file stored in a configuration database. For example, the configuration element 720 includes a file ID 750 which includes identifying information pointing to or identifying a predefined network configuration file in the configuration database 650. For example, with reference to Figures 5 and 6, the file ID 750 may point to or identify the network configuration file 672 in the configuration database 650 as the network configuration for the mesh wireless network 500. In some examples, network configuration information stored in the network configuration file 672 includes a value for every network configuration parameter that is included in a standard beacon frame body. For example, the network configuration parameters may include configuration parameters, capabilities parameters and network configuration / condition reports. In some examples, the frame body 710 and configuration element 720 include only the file ID 750. In this example, the network configuration in the network configuration file 672 may also include information for mandatory parameters included in a standard beacon frame, such as a timestamp, a beacon interval, capability information, a service set identifier (SSID), and supported rates. In some examples, the configuration element 720 provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body with the file ID 750. In some examples, the frame body 710 and configuration element 720 may include additional fields or compressed network configuration information as described with reference to Figures 8-11C.

[0089]

[0086] Figure 8 shows an example beacon frame 800 with mandatory fields and usable for providing compressed network configuration information between wireless communication devices in a network. In some examples, the beacon frame 800 is or is a part of a PDU, such as the PDU 200 described with reference to Figure 2 and the PPDU 300 described with reference to Figure 3. In some examples, the beacon frame 800 is aWi-Fi beacon frame as defined by the IEEE 802.11 set of standards. In another example, the beacon frame 800 is a management frame used in other types of networks to communicate network configuration and other information to devices in the network. In some examples, the beacon frame 800 includes some elements of the beacon frame 700 described with reference to Figure 7. For example, the beacon frame 800 includes the header 705, a frame body 710 and the FCS 715. In some examples, in order to avoid high network overhead costs and network congestion that may be caused by frequent beaconing in the network, the wireless communication devices, such as those described with reference to Figures 5 and 6, utilize the beacon frame 800 to provide compressed network configuration information, where the smaller or compressed size of the beacon frame 800 conserves network resources and prevents network degradation due to high overhead communication. In some examples, the compressed network configuration information for the beacon frame 800 is provided in the frame body 710.

[0090]

[0087] In some examples, the frame body 710 includes mandatory fields 805. In some examples, the mandatory fields 805 include various fields for a plurality of mandatory parameters. In some examples, the mandatory parameters may include parameters defined by the IEEE 802.11 set of standards. For example, the mandatory fields may include fields / information for a timestamp, a beacon interval, capability information, an SSID, and supported rates. In some examples, the mandatory fields 805 provide standard compatibility, such as compatibility with the Wi-Fi standard for the frame body 710 and the beacon frame 800.

[0091]

[0088] In some examples, the frame body 710 of the beacon frame 800 includes the configuration element 720 that includes the file ID 750 identifying a predefined network configuration file stored in a configuration database. In some examples, with reference to Figures 5 and 6, the file ID 750 may point to or identify the network configuration file 672 in the configuration database 650 as the network configuration for the mesh wireless network 500. In some examples, network configuration information stored in the network configuration file 672 includes a value for network configuration parameters, not including the mandatory parameters included in the mandatory fields 805. In some examples, the configuration element 720 provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body, and not covered by the mandatory fields 805, with the file ID 750. In some examples, the frame body 710 and configuration element 720 may include additional fields or compressed network configuration information thatprovides override information for network configuration information stored in the configuration database 650 as described with reference to Figures 10A and 10B.

[0092]

[0089] Figures 9A and 9B show example beacon frames with a vendor information element (IE) providing compressed network configuration information between wireless communication devices in a network. Figure 9A shows a beacon frame 900 and Figure 9B shows a beacon frame 950. In some examples, the beacon frames 900 and 950 are or are a part of a PDU, such as the PDU 200 described with reference to Figure 2 and the PPDU 300 described with reference to Figure 3. In some examples, the beacon frames 900 and 950 are a Wi-Fi beacon frame as defined by the IEEE 802.11 set of standards. In another example, the beacon frames 900 and 950 are management frames used in other types of networks to communicate network configuration and other information to devices in the network. In some examples, the beacon frames 900 and 950 includes some elements of the beacon frames 700 and 800 described with reference to Figures 7 and 8. For example, the beacon frames 900 and 950 each include the header 705, a frame body 710, the FCS 715 and mandatory fields 805. In some examples, in order to avoid high network overhead costs and network congestion that may be caused by frequent beaconing in the network, the wireless communication devices, such as those described with reference to Figures 5 and 6, utilize the beacon frames 900 and 950 to provide compressed network configuration information, where the smaller or compressed size of the beacon frames 900 and 950 conserves network resources and prevents network degradation due to high overhead communication. In some examples, the compressed network configuration information for the beacon frames 900 and 950 is provided in the frame body 710.

[0093]

[0090] In some examples, the frame body 710 of the beacon frames 900 and 950 includes mandatory fields 805 and the configuration element 720. In some examples, the configuration element 720 in both beacon frames 900 and 950 also includes a vendor IE 905 for identifying the network configuration. For example, the vendor IE 905 may include at least one field identifying a predefined network configuration file, such as the network configuration file 672 and the associated, network configuration in the network configuration file 672 as a master network configuration. For example, the vendor IE 905 in the beacon frame 900 may include a tag 910, a length 912, an organizationally unique identifier (OUI) 914, a type field 916 and a file ID 920. In some examples, the tag 910, length 912, and OUI 914 identify the vendor IE and the type field 916 indicates that the file ID 920 and associated network configuration file is associated with a master network configuration.

[0091] In some examples, the vendor IE may also include information for updating / altering the master file configuration. For example, the vendor IE 905 in the beacon frame 950 includes the tag 910, the length 912, the OUI 914, the type field 916 identifying the file ID 920 as associated with the master network configuration and a type field 955 and file ID 960. In some examples, the type field 955 indicates that the file ID 960 identifies a predefined sub-configuration file, where the network configuration is an incremental network configuration. For example, in the incremental network configuration, the master configuration is updated by the network configuration associated with the sub-configuration file. For example, a set of parameters defined in the master network configuration is updated using information in the incremental network configuration. In some examples, the vendor IE 905 may include additional type fields and file ID such that the master network configuration is updated by several network configuration associated with sub-configuration files.

[0094]

[0092] In some examples, the configuration element 720 provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body, and not covered by the mandatory fields 805, with the vendor IE 905, including both the master configuration of the beacon frame 900 and the incremental configuration of the beacon frame 950. In some examples, the frame body 710 and configuration element 720 may include additional fields or compressed network configuration information that provides additional override information for network configuration information stored in the configuration database 650 as described with reference to Figures 10A and 10B.

[0095]

[0093] Figures 10A and 10B show example beacon frames with override elements usable for providing compressed network configuration information between wireless communication devices in a network. For example, Figure 10A shows an example beacon frame 1000 and Figure 10B shows an example beacon frame 1050, where each beacon frame includes an override element. In some examples, the beacon frames 1000 and 1050 provide compressed network configuration information between wireless communication devices in a network. In some examples, the beacon frames 1000 and 1050 are or are a part of a PDU, such as the PDU 200 described with reference to Figure 2 and the PPDU 300 described with reference to Figure 3. In some examples, the beacon frames 1000 and 1050 are Wi-Fi beacon frames as defined by the IEEE 802.11 set of standards or other types of management frames used in other types of networks to communicate network configuration and other information to devices in the network.

[0094] In some examples, the beacon frames 1000 and 1050 includes some elements of the beacon frames 700 and 800 described with reference to Figures 7-8. For example, the beacon frames 1000 and 1050 each include the header 705, the frame body 710, the FCS 715 and the mandatory fields 805. In some examples, the beacon frames 1000 and 1050 may alternatively include a vendor IE, such as the vendor IE 905 described in relation to Figures 9A and 9B. In some examples, in order to avoid high network overhead costs and network congestion that may be caused by frequent beaconing in the network, the wireless communication devices, such as those described with reference to Figures 5 and 6, utilize the beacon frame 1000 to provide compressed network configuration information.

[0096]

[0095] In some examples, some of the network configuration information may include static, semi-static, and dynamic content. For example, static content may include parameters that generally do not change over time. Dynamic content may include parameters that frequently change, such as changing with every network configuration / topology update. In some examples, semi-static content may include parameters that may change, but are generally consistent between each beacon transmission such as changing with every network configuration / topology update. In some examples, to preserve network and device resources, such as memory space in the configuration database 650, dynamic parameters in a network configuration may be updated using override elements in the configuration element 720. In some examples, the override elements provide information to override a set of parameters defined in a network configuration.

[0097]

[0096] For example, the configuration element 720 in the beacon frame 1000 of Figure 10A includes the file ID 750 or vendor IE 905 which identifies a master network configuration in the configuration database 650 and an override element 1010 which may update one or more parameters in the master network configuration. For example, with reference to Figures 5 and 6, the file ID 750 / vendor IE 905 may point to or identify the network configuration file 672 in the configuration database 650 as a master network configuration and the override element 1010 may include information to override one or more parameters in the master network configuration file. In some examples, the override element 1010 in the beacon frame 1000 includes a tag field 1020 and an override file ID 1025. In some examples, the tag field 1020 identifies parameters in the master network configuration for override and a format of the override element 1010. For example, the tag field 1020 includes an identification of parameters for override and the format of the override element 1010 in Figure 10A as a file ID override. In this example,the configuration module 610 uses the configuration map 655 to locate a configuration file associated with the override file ID 1025. For example, the override file ID may point to or identify the network configuration file 676 and the configuration module 610 uses the associated network configuration in the network configuration file 676 to override or update the parameter identified in the tag field 1020 in the master network configuration.

[0098]

[0097] In some examples, the configuration element 720 provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body, and not covered by the mandatory fields 805, with the master configuration file identified in the file ID 750 as updated by the override element 1010.

[0099]

[0098] In some examples, the configuration element 720 may include information for updating the master configuration file within the override element itself. For example, the configuration element 720 in the beacon frame 1050 of Figure 10B includes the file ID 750 which identifies a master network configuration in the configuration database 650 and the override element 1010 which includes a tag field 1060, a length field 1062 and a value field 1064. For example, with reference to Figures 5 and 6, the file ID 750 / vendor IE 905 may point to or identify the network configuration file 672 in the configuration database 650 as a master network configuration and the tag field 1060, the length field 1062 and the value field 1064 of override element 1010 includes information to override one or more parameters in the master network configuration file. In some examples, the tag field 1060 identifies parameters in the master network configuration for override and a format of the override element 1010. For example, the tag field 1060 includes an identification of parameters for override and the format of the override element 1010 in Figure 10B as a parameter information fields override. In this example, the configuration module 610 uses information provided in the length field 1062 and the value field 1064 to override or update the parameter identified in the tag field 1060 in the master network configuration. In some examples, the configuration element 720 may include multiple override elements 1010 of both formats described above. In some examples, the various formats may be identified using a delimiter as described in relation to Figures 11 A, 1 IB and 11C.

[0100]

[0099] Figures 11A-11C show example beacon frames with override elements with delimiters, usable for providing compressed network configuration information between wireless communication devices in a network. For example, Figure 11 A shows an example beacon frame 1100, Figure 1 IB shows an example beacon frame 1120 andFigure 11C shows an example beacon frame 1160, where each beacon frame includes an override element. In some examples, the beacon frames 1100, 1120 and 1160 provides compressed network configuration information between wireless communication devices in a network. In some examples, the beacon frames 1100, 1120 and 1160 are or are a part of a PDU, such as the PDU 200 described with reference to Figure 2 and the PPDU 300 described with reference to Figure 3. In some examples, the beacon frames 1100, 1120 and 1160 are Wi-Fi beacon frames as defined by the IEEE 802.11 set of standards. In another example, the beacon frames 1100, 1120 and 1160 are management frames used in other types of networks to communicate network configuration and other information to devices in the network. In some examples, the beacon frames 1100, 1120 and 1160 includes some elements of the beacon frames 700, 800 described with reference to Figures 7-8. For example, the beacon frames 1100, 1120 and 1160 each include the header 705, the frame body 710, the FCS 715 and the mandatory fields 805. In some examples, the beacon frames 1100, 1120 and 1160 may alternatively include a vendor IE, such as the vendor IE 905 described in relation to Figures 9A and 9B.

[0101]

[0100] In some examples, some of the network configuration information may include static, semi-static, and dynamic content. For example, static content may include parameters that generally do not change over time. Dynamic content may include parameters that frequently change, such as changing with every network configuration / topology update. In some examples, semi-static content may include parameters that may change, but are generally consistent between each beacon transmission such as changing with every network configuration / topology update. In some examples, to preserve network and device resources, such as memory space in the configuration database 650, dynamic parameters in a network configuration may be updated using override elements, such as the override elements 1010 described with reference to Figures 10A and 10B.

[0102]

[0101] For example, the configuration element 720 in the beacon frame 1100 of Figure 11 A includes the file ID 750 / vendor IE 905 which identifies a master network configuration and the override element 1010 which may update one or more parameters in the master network configuration. In some examples, the override element 1010 includes information for updating the master configuration file within the element itself. In this example, the override element 1010 includes a delimiter 1105 identifying the parameter information fields in the frame body, including tag field 1110, length field 1112 and value field 1114. In this example, the configuration module 610 uses information provided in the delimiter 1105, tag field 1110 and the value field 1114 tooverride or update the parameter identified in the tag field 1110 in the master network configuration.

[0103]

[0102] In another example, the configuration element 720 in the beacon frame 1120 of Figure 1 IB includes the file ID 750 / vendor IE 905 which identifies a master network configuration and two override elements 1010 which may update one or more parameters in the master network configuration. For example, the override element 1010 including a tag field 1130 and a file ID 1135 is an override element that includes an override file identifier identifying a predefined sub-configuration file stored in the configuration database. The override element 1010 with a tag field 1150, length field 1152 and value field 1154 is an override element that includes information for updating the master configuration file within the element itself as described with relation to the beacon frame 1100 in Figure 11 A. In this example, a delimiter field 1140 is positioned between the override file identifier and the parameter information fields in the frame body. In some examples, the delimited field may also be used to indicate a change in the override element type. For example, the configuration element 720 in the beacon frame 1120 of Figure 1 IB may be updated to the configuration element 720 in the beacon frame 1160 shown in Figure 11C when the delimiter field 1140 is moved before the tag field 1130 shown in Figure 1 IB. In this example, the tag field 1130 and file ID 1135 are replaced / updated by the tag field 1162, length field 1164 and value 1166.

[0104]

[0103] In some examples, the configuration element 720 provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body, and not covered by the mandatory fields 805, with the master configuration file identified in the file ID 750 / vendor IE 905 as updated by the override elements described in Figures 11 A-C.

[0105]

[0104] Figure 12 shows an example beacon frame 1200 with an override element with a bitmap, usable for providing compressed network configuration information between wireless communication devices in a network. For example, Figure 12 shows an example beacon frame 1200 with an override element. In some examples, the beacon frame 1200 provides compressed network configuration information between wireless communication devices in a network. In some examples, the beacon frame 1200 is or is a part of a PDU, such as the PDU 200 described with reference to Figure 2 and the PPDU 300 described with reference to Figure 3. In some examples, the beacon frame 1200 is a Wi-Fi beacon frame as defined by the IEEE 802.11 set of standards. In another example, the beacon frame 1200 is a management frame used in other types of networks to communicate network configuration and other information to devices in the network. Insome examples, the beacon frame 1200 includes some elements of the beacon frames 700, 800 described with reference to Figure 7-8. For example, the beacon frame 1200 includes the header 705, the frame body 710, the FCS 715 and the mandatory fields 805. In some examples, the beacon frame 1200 may alternatively include a vendor IE, such as the vendor IE 905 described in relation to Figure 9 A and 9B.

[0106]

[0105] In some examples, some of the network configuration information may include static, semi-static, and dynamic content. For example, static content may include parameters that generally do not change over time. Dynamic content may include parameters that frequently change, such as changing with every network configuration / topology update. In some examples, semi-static may include parameters that may change, but are generally consistent between each beacon transmission such as changing with every network configuration / topology update. In some examples, the dynamic content may include a network parameter that includes a plurality of parameter information elements (IES). In some examples, only some of the plurality of parameter IES may change in a network configuration. In some examples, to preserve network and device resources dynamic parameters in an override element may be represented by a bitmap and reduced parameter IE information.

[0107]

[0106] For example, the configuration element 720 in the beacon frame 1200 includes the file ID 750 / vendor IE 905 which identifies a master network configuration and the override element 1010 which may update one or more parameters in the master network configuration. In some examples, the override element 1010 includes information for updating the master configuration file within the element itself. In this example, the override element 1010 includes a tag field 1210, length field 1215 and value field 1220. In some examples, the value field 1220 includes information for a plurality of parameter IEs such as IE fields 1221-1228 which may represent IE1-IE8 for a network parameter, where only IE4 and IE6 are updated in the beacon frame 1200.

[0108]

[0107] In some examples, in order to prevent duplicating the information in the nonupdated parameter IEs and to provide further beacon compression, the length field 1215 and the value field 1220 are replaced by a bitmap field 1250 and only information in the field 1224 and field 1226. In some examples, the included information represents only the changing parameter IEs. In some examples, the bitmap field 1250 is a bitmap or bitmap array that identifies a number of the plurality of parameter IEs for override. In some examples, the override element 1010 includes only information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of the parameter IEs. In some examples, the configurationelement 720 in the beacon frame 1200 provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body, and not covered by the mandatory fields 805, with the master configuration file identified in the file ID 750 / vendor IE 905 as updated by the override element 1010 described in Figure 12.

[0109]

[0108] Figure 13 shows a flowchart illustrating an example process 1300 performable by or at a wireless communication device that supports providing network and device configuration information in a compressed beacon frame. The operations of the process 1300 may be implemented by a wireless communication device or its components as described herein. For example, the process 1300 may be performed by a wireless communication device, such as the wireless communication device 1600 described with reference to Figure 16, operating as or within a wireless AP, a wireless STA or other similar wireless communication device operating as a mesh node. In some examples, the process 1300 may be performed any combination of APs 102 and STAs 104, described with reference to Figure 1, APs 402, STAs 404, intermediate device 412 and wireless communication devices 414 described with reference to Figure 4, and any of the UAVs and other wireless communication devices described with reference to Figures 5 and 6.

[0110]

[0109] In some examples, at block 1305, the wireless communication device receives a beacon frame that includes a frame body from a mesh node device in a mesh wireless network. In some examples, the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network. In some examples, the configuration element includes a file identifier identifying a predefined network configuration file stored in a configuration database.

[0111] [HO] In some examples, the configuration database includes a plurality of predefined network configuration files. For example, the configuration database 650 described with reference to Figure 6 includes the network configuration files 670, including network configuration files 672, 674 and 676. In some examples, each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body. For example, a configuration file of the network configuration file 670 may include values or content for a network parameter of the network configuration where the parameters include a timestamp, beacon interval, capability information for the device and network, SSID information, supported rates, a traffic indication map (TIM) and parameter sets forfrequency hopping, sequencing, contention and IBSS, among other parameters and network information. In some examples, the network configuration files 670 may also include information for optional parameters such as a transmit power control (TPC) report, information for network / device capabilities such as High Throughput (HT) Capabilities, configurations information such as spatial reuse parameters, and reports, such as a reduced neighbor report.

[0112] [Hl] In some examples, the network configuration information may include static information such as an SSID parameter set, country information, and HT capabilities as well as dynamic information such as the TIM and a BSS load. In some examples, a network configuration file may include information for one parameter or any combination of parameters, including information for an entire network configuration that would be represented in a standard beacon frame body.

[0113]

[0112] In some examples, the configuration element, such as the configuration element 720 described with reference to Figures 7-12 provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body. In some examples, the frame body, such as the frame body 710 described with reference to Figures 8-12 also includes mandatory fields, such as mandatory fields 805. In some examples, the mandatory fields include a plurality of mandatory parameters such as one or more of a timestamp, a beacon interval, capability information, a service set identifier (SSID) and supported rates.

[0114]

[0113] In some examples, the configuration element 720 includes a vendor information element (IE), such as the vendor IE 905 described with reference to Figures 9A-12. In some examples, the vendor IE 905 includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration. In some examples, the vendor IE 905 also includes at least one field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration. In some examples, a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0115]

[0114] In some examples, the configuration element 720 also includes at least one override element, such as override element 1010 described with reference to Figures 10A-12. In some examples, the override element 1010 includes information to override a set of parameters defined in the network configuration. For example, at least one override element may include an override file identifier identifying a predefined subconfiguration file stored in the configuration database, where the set of parametersdefined in the network configuration is updated using information stored in the predefined sub-configuration file as described with reference to Figure 10 A. In some examples, the configuration database 650 also includes a configuration map 655, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0116]

[0115] In some examples, the at least one override element, such as the override element 1010 includes parameter information fields, where the set of parameters in the network configuration is updated using information provided in the parameter information fields as described in relation to Figure 10B. In some examples, the at least one override element also includes a delimiter field identifying the parameter information fields in the frame body as described with reference to Figures 11 A-C. In some examples, the at least one override element includes both parameter information fields and an identification for a predefined sub-configuration file stored in the configuration database. In some examples, the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body as described with reference to Figure 1 IB.

[0117]

[0116] In some examples, a parameter of the set of parameters is associated with a plurality of parameter information elements (IES) as described in relation to Figure 12. In some examples, the at least one override element includes a bitmap field representing the plurality of parameter IEs, such as the bitmap field 1250, where the bitmap field identifies a number of the plurality of parameter IEs for override, such as the fields 1224 and 1226, where the fields 1224 and 1226 also include information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of the parameter IEs.

[0118]

[0117] In some examples, at block 1310, the wireless communication device communicates network traffic via the mesh wireless network using a network configuration selected from the predefined network configuration file in the configuration database using the file identifier. For example, the devices in the mesh wireless network 500 described with reference to Figure 5 communicate use the network configuration indicated in the beacon frame, including any overrides provided by the configuration element.

[0119]

[0118] Figure 14 shows a flowchart illustrating an example process 1400 performable by or at a wireless communication device that supports error checking a compressed beacon frame. The operations of the process 1400 may be implemented by awireless communication device or its components as described herein. For example, the process 1400 may be performed by a wireless communication device, such as the wireless communication device 1600 described with reference to Figure 16, operating as or within a wireless AP, a wireless STA or other similar wireless communication device operating as a mesh node. In some examples, the process 1400 may be performed any combination of APs 102 and STAs 104, described with reference to Figure 1, APs 402, STAs 404, intermediate device 412 and wireless communication devices 414 described with reference to Figure 4, and any of the UAVs and other wireless communication devices described with reference to Figures 5 and 6.

[0120]

[0119] In some examples, at block 1405, the wireless communication device counts a reception of the beacon frame as a beacon miss when a beacon decode error is detected. In some examples, the beacon decode error may include any miss condition such as the file identifier is not found in the configuration database, a file identifier format mismatch, an override element error and the file identifier is a misused reserved file identifier.

[0121]

[0120] In some examples, at block 1410, the wireless communication device implements a beacon miss procedure for the mesh wireless network according to the beacon miss count. For example, the wireless communication device may perform a beacon miss procedure according to a protocol standard or other similar procedure.

[0122]

[0121] Figure 15 shows a flowchart illustrating an example process 1500 performable by or at a wireless communication device that supports providing network and device configuration information in a compressed beacon frame. The operations of the process 1500 may be implemented by a wireless communication device or its components as described herein. For example, the process 1500 may be performed by a wireless communication device, such as the wireless communication device 1600 described with reference to Figure 16, operating as or within a wireless AP, a wireless STA or other similar wireless communication device operating as a mesh node. In some examples, the process 1500 may be performed any combination of APs 102 and STAs 104, described with reference to Figure 1, APs 402, STAs 404, intermediate device 412 and wireless communication devices 414 described with reference to Figure 4, and any of the UAVs and other wireless communication devices described with reference to Figures 5 and 6.

[0123]

[0122] In some examples, at block 1505, the wireless communication device provides a beacon frame that includes a frame body to a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network detected atthe wireless communication device, and where the configuration element includes a file identifier identifying a predefined network configuration file selected from a configuration database.

[0124]

[0123] In some examples, the configuration database includes a plurality of predefined network configuration files. For example, the configuration database 650 described with reference to Figure 6 includes the network configuration file 670. In some examples, each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body. For example, a configuration file of the network configuration file 670 may include values or content for a network parameter of the network configuration where the parameters include a timestamp, beacon interval, capability information for the device and network, SSID information, supported rates, a traffic indication map (TIM) and parameter sets for frequency hopping, sequencing, contention and IBSS, among other parameters and network information. In some examples, the network configuration files 670 may also include information for optional parameters such as a transmit power control (TPC) report, information for network / device capabilities such as High Throughput (HT) Capabilities, configurations information such as spatial reuse parameters, and reports, such as a reduced neighbor report.

[0125]

[0124] In some examples, the network configuration information may include static information such as an SSID parameter set, country information, and HT capabilities as well as dynamic information such as the TIM and a BSS load. In some examples, a network configuration file may include information for one parameter or any combination of parameters, including information for an entire network configuration that would be represented in a standard beacon frame body.

[0126]

[0125] In some examples, the configuration element, such as the configuration element 720 described with reference to Figures 7-12 provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body. In some examples, the frame body, such as the frame body 710 described with reference to Figures 8-12 also includes mandatory fields, such as mandatory fields 805. In some examples, the mandatory fields include a plurality of mandatory parameters such as one or more of a timestamp, a beacon interval, capability information, a service set identifier (SSID) and supported rates.

[0127]

[0126] In some examples, the configuration element 720 includes a vendor information element (IE), such as the vendor IE 905 described with reference to Figures9A-12. In some examples, the vendor IE 905 includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration. In some examples, the vendor IE 905 also includes at least one field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration. In some examples, a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0128]

[0127] In some examples, the configuration element 720 also includes at least one override element, such as override element 1010 described with reference to Figures 10A-12. In some examples, the override element 1010 includes information to override a set of parameters defined in the network configuration. For example, at least one override element may include an override file identifier identifying a predefined subconfiguration file stored in the configuration database, where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file as described with reference to Figure 10 A. In some examples, the configuration database 650 also includes a configuration map 655, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0129]

[0128] In some examples, the at least one override element, such as the override element 1010 includes parameter information fields, where the set of parameters in the network configuration is updated using information provided in the parameter information fields as described in relation to Figure 10B. In some examples, the at least one override element also includes a delimiter field identifying the parameter information fields in the frame body as described with reference to Figures 11 A-C. In some examples, the at least one override element includes both parameter information fields and an identification for a predefined sub-configuration file stored in the configuration database. In some examples, the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body as described with reference to Figure 1 IB.

[0130]

[0129] In some examples, a parameter of the set of parameters is associated with a plurality of parameter information elements (IES) as described in relation to Figure 12. In some examples, the at least one override element includes a bitmap field representing the plurality of parameter IEs, such as the bitmap field 1250, where the bitmap field identifies a number of the plurality of parameter IEs for override, such as the fields 1224and 1226, where the fields 1224 and 1226 also include information to override the number of the plurality of parameter IES without including a representation of every parameter IE of the plurality of the parameter IEs.

[0131]

[0130] In some examples, at block 1510, the wireless communication device communicates network traffic via the mesh wireless network using the network configuration associated with the predefined network configuration file in the configuration database. For example, the devices in the mesh wireless network 500 described with reference to Figure 5 communicate use the network configuration indicated in the beacon frame, including any overrides provided by the configuration element.

[0132]

[0131] Figure 16 shows a block diagram of an example wireless communication device 1600 that supports providing network and device configuration information in a compressed beacon frame.

[0133]

[0132] In some examples, the wireless communication device 1600 is configured to perform the processes 1300, 1400 and 1500 described with reference to Figure 13, 14 and 15. The wireless communication device 1600 may include one or more chips, SoCs, chipsets, packages, components or devices that individually or collectively constitute or include a processing system. The processing system may interface with other components of the wireless communication device 1600, and may generally process information (such as inputs or signals) received from such other components and output information (such as outputs or signals) to such other components. In some aspects, an example chip may include a processing system, a first interface to output or transmit information and a second interface to receive or obtain information. For example, the first interface may refer to an interface between the processing system of the chip and a transmission component, such that the wireless communication device 1600 may transmit the information output from the chip. In such an example, the second interface may refer to an interface between the processing system of the chip and a reception component, such that the wireless communication device 1600 may receive information that is passed to the processing system. In some such examples, the first interface also may obtain information, such as from the transmission component, and the second interface also may output information, such as to the reception component.

[0134]

[0133] The processing system of the wireless communication device 1600 includes processor (or “processing”) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs) (also referred to as neuralnetwork processors or deep learning processors (DLPs)), or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASIC), programmable logic devices (PLDs) (such as field programmable gate arrays (FPGAs)), or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry”). One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as randomaccess memory (RAM) or read-only memory (ROM), or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry”). One or more of the memories may be coupled with one or more of the processors and may individually or collectively store processorexecutable code that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally, or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, IEEE compliant) modem or a cellular (for example, 3GPP 4G LTE, 5G or 6G compliant) modem). In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively “the radio”), multiple RF chains or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers.

[0135]

[0134] In some examples, the wireless communication device 1600 can be configurable or configured for use in any variety of wireless communication devices including any combination of APs 102 and STAs 104, described with reference to Figure 1, APs 402, STAs 404, intermediate device 412 and wireless communication devices 414, described with reference to Figure 4. In some other examples, the wireless communication device 1600 can be a wireless communication device that includes such a processing system and other components including multiple antennas. The wireless communication device 1600 is capable of transmitting and receiving wirelesscommunications in the form of, for example, wireless packets. For example, the wireless communication device 1600 can be configurable or configured to transmit and receive packets in the form of physical layer PPDUs and MPDUs conforming to one or more of the IEEE 802.11 family of wireless communication protocol standards. In some other examples, the wireless communication device 1600 can be configurable or configured to transmit and receive signals and communications conforming to one or more 3GPP specifications including those for 5GNR or 6G. In some examples, the wireless communication device 1600 also includes or can be coupled with one or more application processors which may be further coupled with one or more other memories. In some examples, the wireless communication device 1600 further includes at least one external network interface coupled with the processing system that enables communication with a core network or backhaul network that enables the wireless communication device 1600 to gain access to external networks including the Internet.

[0136]

[0135] The wireless communication device 1600 includes a memory component 1605, a processor component 1610, a modem component 1615, configuration module 610 and configuration database 650. Portions of one or more of the components 1605, 1610, 1615, configuration module 610 and configuration database 650 may be implemented at least in part in hardware or firmware. For example, the configuration module 610 may be implemented at least in part by a processor or a modem. In some examples, portions of one or more of the components 1605, 1610, 1615, configuration module 610 and configuration database 650 may be implemented at least in part by a processor and software in the form of processor-executable code stored in a memory.

[0137]

[0136] Implementation examples are described in the following numbered clauses:

[0138]

[0137] Clause 1. A wireless communication device, including: a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the wireless communication device to: receive a beacon frame including a frame body from a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network, and where the configuration element includes a file identifier identifying a predefined network configuration file stored in a configuration database; and communicate network traffic via the mesh wireless network using a network configuration selected from the predefined network configuration file in the configuration database using the file identifier.

[0139]

[0138] Clause 2. The wireless communication device of clause 1, where the configuration database includes a plurality of predefined network configuration files, andwhere each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body.

[0140]

[0139] Clause 3. The wireless communication device of any of clauses 1-2, where the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body.

[0141]

[0140] Clause 4. The wireless communication device of any of clauses 1-3, where the frame body further includes mandatory fields including a plurality of mandatory parameters, where the plurality of mandatory parameters includes one or more of a timestamp; a beacon interval; capability information; a service set identifier (SSID); and supported rates.

[0142]

[0141] Clause 5. The wireless communication device of any of clauses 1-4, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0143]

[0142] Clause 6. The wireless communication device of any of clauses 1-5, where the at least one override element includes an override file identifier identifying a predefined sub-configuration file stored in the configuration database, and where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file.

[0144]

[0143] Clause 7. The wireless communication device of any of clauses 1-6, where the configuration database further includes a configuration map, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0145]

[0144] Clause 8. The wireless communication device of any of clauses 1-7, where the at least one override element includes parameter information fields, and where the set of parameters in the network configuration is updated using information provided in the parameter information fields.

[0146]

[0145] Clause 9. The wireless communication device of any of clauses 1-8, where the at least one override element further includes a delimiter field identifying the parameter information fields in the frame body.

[0147]

[0146] Clause 10. The wireless communication device of any of clauses 1-9, where the at least one override element further includes an override file identifier identifying a predefined sub-configuration file stored in the configuration database, where the delimiter field is positioned between the override file identifier and the parameterinformation fields in the frame body, and where a subset of the set of parameters in the network configuration is updated using information stored in the predefined subconfiguration file.

[0148]

[0147] Clause 11. The wireless communication device of any of clauses 1-10, where a parameter of the set of parameters is associated with a plurality of parameter information elements (IES), and where the at least one override element includes: a bitmap field representing the plurality of parameter IEs, where the bitmap field identifies a number of the plurality of parameter IEs for override; and information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of the parameter IEs.

[0149]

[0148] Clause 12. The wireless communication device of any of clauses 1-11, where the configuration element includes a vendor information element (IE), where the vendor IE includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration.

[0150]

[0149] Clause 13. The wireless communication device of any of clauses 1-12, where the vendor IE further includes at least one field identifying a predefined subconfiguration file stored in the configuration database as an incremental network configuration, and where a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0151]

[0150] Clause 14. The wireless communication device of any of clauses 1-13, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0152]

[0151] Clause 15. The wireless communication device of any of clauses 1-14, where the processing system is further configured to cause the wireless communication device to: count a reception of the beacon frame as a beacon miss when a beacon decode error is detected, where the beacon decode error includes at least one of: the file identifier is not found in the configuration database; a file identifier format mismatch; an override element error; and the file identifier is a misused reserved file identifier; and implement a beacon miss procedure for the mesh wireless network according to the beacon miss count.

[0153]

[0152] Clause 16. A method for wireless communication the method including: receiving a beacon frame including a frame body from a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network, and where the configuration element includes a file identifier identifying a predefined networkconfiguration file stored in a configuration database; and communicating network traffic via the mesh wireless network using a network configuration selected from the predefined network configuration file in the configuration database using the file identifier.

[0154]

[0153] Clause 17. The method of clause 16, where the configuration database includes a plurality of predefined network configuration files, and where each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body.

[0155]

[0154] Clause 18. The method of any of clauses 16-17, where the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body.

[0156]

[0155] Clause 19. The method of any of clauses 16-18, where the frame body further includes mandatory fields including a plurality of mandatory parameters, where the plurality of mandatory parameters includes one or more of a timestamp; a beacon interval; capability information; a service set identifier (SSID); and supported rates.

[0157]

[0156] Clause 20. The method of any of clauses 16-19, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0158]

[0157] Clause 21. The method of any of clauses 16-20, where the at least one override element includes an override file identifier identifying a predefined subconfiguration file stored in the configuration database, and where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file.

[0159]

[0158] Clause 22. The method of any of clauses 16-21, where the configuration database further includes a configuration map, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0160]

[0159] Clause 23. The method of any of clauses 16-22, where the at least one override element includes parameter information fields, and where the set of parameters in the network configuration is updated using information provided in the parameter information fields.

[0160] Clause 24. The method of any of clauses 16-23, where the at least one override element further includes a delimiter field identifying the parameter information fields in the frame body.

[0161]

[0161] Clause 25. The method of any of clauses 16-24, where the at least one override element further includes an override file identifier identifying a predefined subconfiguration file stored in the configuration database, where the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body, and where a subset of the set of parameters in the network configuration is updated using information stored in the predefined sub-configuration file.

[0162]

[0162] Clause 26. The method of any of clauses 16-25, where a parameter of the set of parameters is associated with a plurality of parameter information elements (IES), and where the at least one override element includes: a bitmap field representing the plurality of parameter IEs, where the bitmap field identifies a number of the plurality of parameter IEs for override; and information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of the parameter IEs.

[0163]

[0163] Clause 27. The method of any of clauses 16-26, where the configuration element includes a vendor information element (IE), where the vendor IE includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration.

[0164]

[0164] Clause 28. The method of any of clauses 16-27, where the vendor IE further includes at least one field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration, and where a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0165]

[0165] Clause 29. The method of any of clauses 16-28, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0166]

[0166] Clause 30. The method of any of clauses 16-29, where the method further includes counting a reception of the beacon frame as a beacon miss when a beacon decode error is detected, where the beacon decode error includes at least one of: the file identifier is not found in the configuration database; a file identifier format mismatch; an override element error; and the file identifier is a misused reserved file identifier; and implementing a beacon miss procedure for the mesh wireless network according to the beacon miss count.

[0167] Clause 31. An apparatus for wireless communication by a wireless communication device, including: means for: receiving a beacon frame including a frame body from a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network, and where the configuration element includes a file identifier identifying a predefined network configuration file stored in a configuration database; and communicating network traffic via the mesh wireless network using a network configuration selected from the predefined network configuration file in the configuration database using the file identifier.

[0167]

[0168] Clause 32. The apparatus of clause 31, where the configuration database includes a plurality of predefined network configuration files, and where each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body.

[0168]

[0169] Clause 33. The apparatus of any of clauses 31-32, where the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body.

[0169]

[0170] Clause 34. The apparatus of any of clauses 31-33, where the frame body further includes mandatory fields including a plurality of mandatory parameters, where the plurality of mandatory parameters includes one or more of: a timestamp; a beacon interval; capability information; a service set identifier (SSID); and supported rates.

[0170]

[0171] Clause 35. The apparatus of any of clauses 31-34, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0171]

[0172] Clause 36. The apparatus of any of clauses 31-35, where the at least one override element includes an override file identifier identifying a predefined subconfiguration file stored in the configuration database, and where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file.

[0172]

[0173] Clause 37. The apparatus of any of clauses 31-36, where the configuration database further includes a configuration map, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0174] Clause 38. The apparatus of any of clauses 31-37, where the at least one override element includes parameter information fields, and where the set of parameters in the network configuration is updated using information provided in the parameter information fields.

[0173]

[0175] Clause 39. The apparatus of any of clauses 31-38, where the at least one override element further includes a delimiter field identifying the parameter information fields in the frame body.

[0174]

[0176] Clause 40. The apparatus of any of clauses 31-39, where the at least one override element further includes an override file identifier identifying a predefined subconfiguration file stored in the configuration database, where the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body, and where a subset of the set of parameters in the network configuration is updated using information stored in the predefined sub-configuration file.

[0175]

[0177] Clause 41. The apparatus of any of clauses 31-40, where a parameter of the set of parameters is associated with a plurality of parameter information elements (IES), and where the at least one override element includes: a bitmap field representing the plurality of parameter IEs, where the bitmap field identifies a number of the plurality of parameter IEs for override; and information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of the parameter IEs.

[0176]

[0178] Clause 42. The apparatus of any of clauses 31-41, where the configuration element includes a vendor information element (IE), where the vendor IE includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration.

[0177]

[0179] Clause 43. The apparatus of any of clauses 31-42, where the vendor IE further includes at least one field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration, and where a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0178]

[0180] Clause 44. The apparatus of any of clauses 31-43, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0179]

[0181] Clause 45. The apparatus of any of clauses 31-44, further including means for: counting a reception of the beacon frame as a beacon miss when a beacon decode error is detected, where the beacon decode error includes at least one of: the file identifieris not found in the configuration database; a file identifier format mismatch; an override element error; and the file identifier is a misused reserved file identifier; and implementing a beacon miss procedure for the mesh wireless network according to the beacon miss count.

[0180]

[0182] Clause 46. A non-transitory processor-readable storage medium including processor-readable instructions configured to cause one or more processors to perform a process at a wireless communication device, including code for: receiving a beacon frame including a frame body from a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network, and where the configuration element includes a file identifier identifying a predefined network configuration file stored in a configuration database; and communicating network traffic via the mesh wireless network using a network configuration selected from the predefined network configuration file in the configuration database using the file identifier.

[0181]

[0183] Clause 47. The non-transitory processor-readable storage medium of clause 46, where the configuration database includes a plurality of predefined network configuration files, and where each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body.

[0182]

[0184] Clause 48. The non-transitory processor-readable storage medium of any of clauses 46-47, where the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body.

[0183]

[0185] Clause 49. The non-transitory processor-readable storage medium of any of clauses 46-48, where the frame body further includes mandatory fields including a plurality of mandatory parameters, where the plurality of mandatory parameters includes one or more of: a timestamp; a beacon interval; capability information; a service set identifier (SSID); and supported rates.

[0184]

[0186] Clause 50. The non-transitory processor-readable storage medium of any of clauses 46-49, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0185]

[0187] Clause 51. The non-transitory processor-readable storage medium of any of clauses 46-50, where the at least one override element includes an override file identifieridentifying a predefined sub-configuration file stored in the configuration database, and where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file.

[0186]

[0188] Clause 52. The non-transitory processor-readable storage medium of any of clauses 46-51, where the configuration database further includes a configuration map, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0187]

[0189] Clause 53. The non-transitory processor-readable storage medium of any of clauses 46-52, where the at least one override element includes parameter information fields, and where the set of parameters in the network configuration is updated using information provided in the parameter information fields.

[0188]

[0190] Clause 54. The non-transitory processor-readable storage medium of any of clauses 46-53, where the at least one override element further includes a delimiter field identifying the parameter information fields in the frame body.

[0189]

[0191] Clause 55. The non-transitory processor-readable storage medium of any of clauses 46-54, where the at least one override element further includes an override file identifier identifying a predefined sub-configuration file stored in the configuration database, where the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body, and where a subset of the set of parameters in the network configuration is updated using information stored in the predefined sub-configuration file.

[0190]

[0192] Clause 56. The non-transitory processor-readable storage medium of any of clauses 46-55, where a parameter of the set of parameters is associated with a plurality of parameter information elements (IES), and where the at least one override element includes: a bitmap field representing the plurality of parameter IEs, where the bitmap field identifies a number of the plurality of parameter IEs for override; and information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of the parameter IEs.

[0191]

[0193] Clause 57. The non-transitory processor-readable storage medium of any of clauses 46-56, where the configuration element includes a vendor information element (IE), where the vendor IE includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration.

[0192]

[0194] Clause 58. The non-transitory processor-readable storage medium of any of clauses 46-57, where the vendor IE further includes at least one field identifying apredefined sub-configuration file stored in the configuration database as an incremental network configuration, and where a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0193]

[0195] Clause 59. The non-transitory processor-readable storage medium of any of clauses 46-58, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0194]

[0196] Clause 60. The non-transitory processor-readable storage medium of any of clauses 46-59, further including code for: counting a reception of the beacon frame as a beacon miss when a beacon decode error is detected, where the beacon decode error includes at least one of the file identifier is not found in the configuration database; a file identifier format mismatch; an override element error; and the file identifier is a misused reserved file identifier; and implementing a beacon miss procedure for the mesh wireless network according to the beacon miss count.

[0195]

[0197] Clause 61. A wireless communication device, including: a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the wireless communication device to: provide a beacon frame including a frame body to a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network detected at the wireless communication device, and where the configuration element includes a file identifier identifying a predefined network configuration file selected from a configuration database; and communicate network traffic via the mesh wireless network using a network configuration associated with the predefined network configuration file in the configuration database.

[0196]

[0198] Clause 62. The wireless communication device of clause 61, where the configuration database includes a plurality of predefined network configuration files, and where each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body.

[0197]

[0199] Clause 63. The wireless communication device of any of clauses 61-62, where the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body.

[0200] Clause 64. The wireless communication device of any of clauses 61-63, where the frame body further includes mandatory fields including a plurality of mandatory parameters, where the plurality of mandatory parameters includes one or more of: a timestamp; a beacon interval; capability information; a service set identifier (SSID); and supported rates.

[0198]

[0201] Clause 65. The wireless communication device of any of clauses 61-64, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0199]

[0202] Clause 66. The wireless communication device of any of clauses 61-65, where the at least one override element includes an override file identifier identifying a predefined sub-configuration file stored in the configuration database, and where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file.

[0200]

[0203] Clause 67. The wireless communication device of any of clauses 61-66, where the configuration database further includes a configuration map, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0201]

[0204] Clause 68. The wireless communication device of any of clauses 61-67, where the at least one override element includes parameter information fields, and where the set of parameters in the network configuration is updated using information provided in the parameter information fields.

[0202]

[0205] Clause 69. The wireless communication device of any of clauses 61-68, where the at least one override element further includes a delimiter field identifying the parameter information fields in the frame body.

[0203]

[0206] Clause 70. The wireless communication device of any of clauses 61-69, where the at least one override element further includes an override file identifier identifying a predefined sub-configuration file stored in the configuration database, where the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body, and where a subset of the set of parameters in the network configuration is updated using information stored in the predefined sub-configuration file.

[0204]

[0207] Clause 71. The wireless communication device of any of clauses 61-70, where a parameter of the set of parameters is associated with a plurality of parameter information elements (IES), and where the at least one override element includes: abitmap field representing the plurality of parameter IES, where the bitmap field identifies a number of the plurality of parameter IEs for override; and information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of the parameter IEs.

[0205]

[0208] Clause 72. The wireless communication device of any of clauses 61-71, where the configuration element includes a vendor information element (IE), where the vendor IE includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration.

[0206]

[0209] Clause 73. The wireless communication device of any of clauses 61-72, where the vendor IE further includes at least one field identifying a predefined subconfiguration file stored in the configuration database as an incremental network configuration, and where a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0207]

[0210] Clause 74. The wireless communication device of any of clauses 61-73, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0208] [2H] Clause 75. A method for wireless communication the method including: providing a beacon frame including a frame body to a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network detected at the wireless communication device, and where the configuration element includes a file identifier identifying a predefined network configuration file selected from a configuration database; and communicating network traffic via the mesh wireless network using a network configuration associated with the predefined network configuration file in the configuration database.

[0209]

[0212] Clause 76. The method of clause 75, where the configuration database includes a plurality of predefined network configuration files, and where each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body.

[0210]

[0213] Clause 77. The method of any of clauses 75-76, where the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body.

[0214] Clause 78. The method of any of clauses 75-77, where the frame body further includes mandatory fields including a plurality of mandatory parameters, where the plurality of mandatory parameters includes one or more of: a timestamp; a beacon interval; capability information; a service set identifier (SSID); and supported rates.

[0211]

[0215] Clause 79. The method of any of clauses 75-78, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0212]

[0216] Clause 80. The method of any of clauses 75-79, where the at least one override element includes an override file identifier identifying a predefined subconfiguration file stored in the configuration database, and where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file.

[0213]

[0217] Clause 81. The method of any of clauses 75-80, where the configuration database further includes a configuration map, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0214]

[0218] Clause 82. The method of any of clauses 75-81, where the at least one override element includes parameter information fields, and where the set of parameters in the network configuration is updated using information provided in the parameter information fields.

[0215]

[0219] Clause 83. The method of any of clauses 75-82, where the at least one override element further includes a delimiter field identifying the parameter information fields in the frame body.

[0216]

[0220] Clause 84. The method of any of clauses 75-83, where the at least one override element further includes an override file identifier identifying a predefined subconfiguration file stored in the configuration database, where the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body, and where a subset of the set of parameters in the network configuration is updated using information stored in the predefined sub-configuration file.

[0217]

[0221] Clause 85. The method of any of clauses 75-84, where a parameter of the set of parameters is associated with a plurality of parameter information elements (IES), and where the at least one override element includes: a bitmap field representing the plurality of parameter IEs, where the bitmap field identifies a number of the plurality of parameter IEs for override; and information to override the number of the plurality of parameter IEswithout including a representation of every parameter IE of the plurality of the parameter IES.

[0218]

[0222] Clause 86. The method of any of clauses 75-85, where the configuration element includes a vendor information element (IE), where the vendor IE includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration.

[0219]

[0223] Clause 87. The method of any of clauses 75-86, where the vendor IE further includes at least one field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration, and where a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0220]

[0224] Clause 88. The method of any of clauses 75-87, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0221]

[0225] Clause 89. An apparatus for wireless communication by a wireless communication device, including: means for: providing a beacon frame including a frame body to a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network detected at the wireless communication device, and where the configuration element includes a file identifier identifying a predefined network configuration file selected from a configuration database; and communicating network traffic via the mesh wireless network using a network configuration associated with the predefined network configuration file in the configuration database.

[0222]

[0226] Clause 90. The apparatus of clause 89, where the configuration database includes a plurality of predefined network configuration files, and where each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body.

[0223]

[0227] Clause 91. The apparatus of any of clauses 89-90, where the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body.

[0224]

[0228] Clause 92. The apparatus of any of clauses 89-91, where the frame body further includes mandatory fields including a plurality of mandatory parameters, wherethe plurality of mandatory parameters includes one or more of: a timestamp; a beacon interval; capability information; a service set identifier (SSID); and supported rates.

[0225]

[0229] Clause 93. The apparatus of any of clauses 89-92, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0226]

[0230] Clause 94. The apparatus of any of clauses 89-93, where the at least one override element includes an override file identifier identifying a predefined subconfiguration file stored in the configuration database, and where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file.

[0227]

[0231] Clause 95. The apparatus of any of clauses 89-94, where the configuration database further includes a configuration map, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0228]

[0232] Clause 96. The apparatus of any of clauses 89-95, where the at least one override element includes parameter information fields, and where the set of parameters in the network configuration is updated using information provided in the parameter information fields.

[0229]

[0233] Clause 97. The apparatus of any of clauses 89-96, where the at least one override element further includes a delimiter field identifying the parameter information fields in the frame body.

[0230]

[0234] Clause 98. The apparatus of any of clauses 89-97, where the at least one override element further includes an override file identifier identifying a predefined subconfiguration file stored in the configuration database, where the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body, and where a subset of the set of parameters in the network configuration is updated using information stored in the predefined sub-configuration file.

[0231]

[0235] Clause 99. The apparatus of any of clauses 89-98, where a parameter of the set of parameters is associated with a plurality of parameter information elements (IES), and where the at least one override element includes: a bitmap field representing the plurality of parameter IEs, where the bitmap field identifies a number of the plurality of parameter IEs for override; and information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of the parameter IEs.

[0236] Clause 100. The apparatus of any of clauses 89-99, where the configuration element includes a vendor information element (IE), where the vendor IE includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration.

[0232]

[0237] Clause 101. The apparatus of any of clauses 89-100, where the vendor IE further includes at least one field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration, and where a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0233]

[0238] Clause 102. The apparatus of any of clauses 89-101, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0234]

[0239] Clause 103. A non-transitory processor-readable storage medium including processor-readable instructions configured to cause one or more processors to perform a process at a wireless communication device, including code for: providing a beacon frame including a frame body to a mesh node device in a mesh wireless network, where the frame body includes a configuration element that includes compressed network configuration information for the mesh wireless network detected at the wireless communication device, and where the configuration element includes a file identifier identifying a predefined network configuration file selected from a configuration database; and communicating network traffic via the mesh wireless network using a network configuration associated with the predefined network configuration file in the configuration database.

[0235]

[0240] Clause 104. The non-transitory processor-readable storage medium of clause 103, where the configuration database includes a plurality of predefined network configuration files, and where each predefined network configuration file of the plurality of predefined network configuration files includes content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body.

[0236]

[0241] Clause 105. The non-transitory processor-readable storage medium of any of clauses 103-104, where the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body.

[0237]

[0242] Clause 106. The non-transitory processor-readable storage medium of any of clauses 103-105, where the frame body further includes mandatory fields including aplurality of mandatory parameters, where the plurality of mandatory parameters includes one or more of: a timestamp; a beacon interval; capability information; a service set identifier (SSID); and supported rates.

[0238]

[0243] Clause 107. The non-transitory processor-readable storage medium of any of clauses 103-106, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0239]

[0244] Clause 108. The non-transitory processor-readable storage medium of any of clauses 103-107, where the at least one override element includes an override file identifier identifying a predefined sub-configuration file stored in the configuration database, and where the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file.

[0240]

[0245] Clause 109. The non-transitory processor-readable storage medium of any of clauses 103-108, where the configuration database further includes a configuration map, where the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

[0241]

[0246] Clause 110. The non-transitory processor-readable storage medium of any of clauses 103-109, where the at least one override element includes parameter information fields, and where the set of parameters in the network configuration is updated using information provided in the parameter information fields.

[0242]

[0247] Clause 111. The non-transitory processor-readable storage medium of any of clauses 103-110, where the at least one override element further includes a delimiter field identifying the parameter information fields in the frame body.

[0243]

[0248] Clause 112. The non-transitory processor-readable storage medium of any of clauses 103-111, where the at least one override element further includes an override file identifier identifying a predefined sub-configuration file stored in the configuration database, where the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body, and where a subset of the set of parameters in the network configuration is updated using information stored in the predefined sub-configuration file.

[0244]

[0249] Clause 113. The non-transitory processor-readable storage medium of any of clauses 103-112, where a parameter of the set of parameters is associated with a plurality of parameter information elements (IES), and where the at least one override element includes: a bitmap field representing the plurality of parameter IEs, where the bitmapfield identifies a number of the plurality of parameter IES for override; and information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of the parameter IEs.

[0245]

[0250] Clause 114. The non-transitory processor-readable storage medium of any of clauses 103-113, where the configuration element includes a vendor information element (IE), where the vendor IE includes at least one field identifying the network configuration in the predefined network configuration file as a master network configuration.

[0246]

[0251] Clause 115. The non-transitory processor-readable storage medium of any of clauses 103-114, where the vendor IE further includes at least one field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration, and where a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

[0247]

[0252] Clause 116. The non-transitory processor-readable storage medium of any of clauses 103-115, where the configuration element further includes at least one override element including information to override a set of parameters defined in the network configuration.

[0248]

[0253] As used herein, the term “determine” or “determining” encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, estimating, investigating, looking up (such as via looking up in a table, a database, or another data structure), inferring, ascertaining, or measuring, among other possibilities. Also, “determining” can include receiving (such as receiving information), accessing (such as accessing data stored in memory) or transmitting (such as transmitting information), among other possibilities. Additionally, “determining” can include resolving, selecting, obtaining, choosing, establishing and other such similar actions.

[0249]

[0254] As used herein, a phrase referring to “at least one of’ or “one or more of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, a-b, a-c, b-c, and a-b-c. As used herein, “or” is intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, “a or b” may include a only, b only, or a combination of a and b. Furthermore, as used herein, a phrase referring to “a” or “an” element refers to one or more of such elements acting individually or collectively to perform the recited function(s). Additionally, a “set” refers to one or more items, and a “subset” refers to less than a whole set, but non-empty.

[0255] As used herein, “based on” is intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, “based on” may be used interchangeably with “based at least in part on,” “associated with,” “in association with,” or “in accordance with” unless otherwise explicitly indicated. Specifically, unless a phrase refers to “based on only ‘a,’” or the equivalent in context, whatever it is that is “based on ‘a,’” or “based at least in part on ‘a,’” may be based on “a” alone or based on a combination of “a” and one or more other factors, conditions, or information.

[0250]

[0256] The various illustrative components, logic, logical blocks, modules, circuits, operations, and algorithm processes described in connection with the examples disclosed herein may be implemented as electronic hardware, firmware, software, or combinations of hardware, firmware, or software, including the structures disclosed in this specification and the structural equivalents thereof. The interchangeability of hardware, firmware and software has been described generally, in terms of functionality, and illustrated in the various illustrative components, blocks, modules, circuits and processes described above. Whether such functionality is implemented in hardware, firmware or software depends upon the particular application and design constraints imposed on the overall system.

[0251]

[0257] Various modifications to the examples described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the examples shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

[0252]

[0258] Additionally, various features that are described in this specification in the context of separate examples also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple examples separately or in any suitable subcombination. As such, although features may be described above as acting in particular combinations, and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

[0253]

[0259] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Further, the drawings may schematically depict one or more example processes in the form of a flowchart or flow diagram. However,other operations that are not depicted can be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the illustrated operations. In some circumstances, multitasking and parallel processing may be advantageous.

[0254] Moreover, the separation of various system components in the examples described above should not be understood as requiring such separation in all examples, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Claims

CLAIMSWhat is claimed is:

1. A wireless communication device, comprising:a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the wireless communication device to:receive a beacon frame comprising a frame body from a mesh node device in a mesh wireless network,where the frame body comprises a configuration element that includes compressed network configuration information for the mesh wireless network, andwhere the configuration element comprises a file identifier identifying a predefined network configuration file stored in a configuration database; andcommunicate network traffic via the mesh wireless network using a network configuration selected from the predefined network configuration file in the configuration database using the file identifier.

2. The wireless communication device of claim 1,wherein the configuration database comprises a plurality of predefined network configuration files, andwherein each predefined network configuration file of the plurality of predefined network configuration files comprises content for at least one network configuration parameter defining network configuration information included in a standard beacon frame body.

3. The wireless communication device of claim 1, wherein the configuration element provides the compressed network configuration information by replacing an entirety of network configuration information content provided in a standard beacon frame body.

4. The wireless communication device of claim 1, wherein the frame body further comprises mandatory fields including a plurality of mandatory parameters, wherein the plurality of mandatory parameters comprises one or more of:a timestamp;a beacon interval;capability information;a service set identifier (SSID); andsupported rates.

5. The wireless communication device of claim 4, wherein the configuration element further comprises at least one override element comprising information to override a set of parameters defined in the network configuration.

6. The wireless communication device of claim 5, wherein the at least one override element comprises an override file identifier identifying a predefined sub-configuration file stored in the configuration database, and wherein the set of parameters defined in the network configuration is updated using information stored in the predefined subconfiguration file.

7. The wireless communication device of claim 6, wherein the configuration database further comprises a configuration map, wherein the configuration map provides an identification of a format for the at least one override element as one of an override file identifier format or a parameter information fields format.

8. The wireless communication device of claim 5, wherein the at least one override element comprises parameter information fields, and wherein the set of parameters in the network configuration is updated using information provided in the parameter information fields.

9. The wireless communication device of claim 8, wherein the at least one override element further comprises a delimiter field identifying the parameter information fields in the frame body.

10. The wireless communication device of claim 9, wherein the at least one override element further comprises an override file identifier identifying a predefined subconfiguration file stored in the configuration database, wherein the delimiter field is positioned between the override file identifier and the parameter information fields in the frame body, and wherein a subset of the set of parameters in the network configuration is updated using information stored in the predefined sub-configuration file.

11. The wireless communication device of claim 5, wherein a parameter of the set of parameters is associated with a plurality of parameter information elements (IES), and wherein the at least one override element comprises:a bitmap field representing the plurality of parameter IEs, wherein the bitmap field identifies a number of the plurality of parameter IEs for override; and information to override the number of the plurality of parameter IEs without including a representation of every parameter IE of the plurality of parameter IEs.

12. The wireless communication device of claim 1, wherein the configuration element comprises a vendor information element (IE), wherein the vendor IE comprises at least one field identifying the network configuration in the predefined network configuration file as a master network configuration.

13. The wireless communication device of claim 12, wherein the vendor IE further comprises at least one field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration, and wherein a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

14. The wireless communication device of claim 12, wherein the configuration element further comprises at least one override element comprising information to override a set of parameters defined in the network configuration.

15. The wireless communication device of claim 1, wherein the processing system is further configured to cause the wireless communication device to:count a reception of the beacon frame as a beacon miss when a beacon decode error is detected, wherein the beacon decode error comprises at least one of:the file identifier is not found in the configuration database;a file identifier format mismatch;an override element error; andthe file identifier is a misused reserved file identifier; and implement a beacon miss procedure for the mesh wireless network according to the beacon miss count.

16. A wireless communication device, comprising:a processing system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the wireless communication device to:provide a beacon frame comprising a frame body to a mesh node device in a mesh wireless network,where the frame body comprises a configuration element that includes compressed network configuration information for the mesh wireless network detected at the wireless communication device, and where the configuration element comprises a file identifier identifying a predefined network configuration file selected from a configuration database; andcommunicate network traffic via the mesh wireless network using a network configuration associated with the predefined network configuration file in the configuration database.

17. The wireless communication device of claim 16, wherein the frame body further comprises:mandatory fields including a plurality of mandatory parameters, wherein the plurality of mandatory parameters comprises at least one of:a timestamp;a beacon interval;capability information;a service set identifier (SSID); andsupported rates; andat least one override element comprising information to override a set of parameters defined in the network configuration.

18. The wireless communication device of claim 17, wherein the at least one override element comprises at least one of:an override file identifier identifying a predefined sub-configuration file stored in the configuration database, and wherein the set of parameters defined in the network configuration is updated using information stored in the predefined sub-configuration file; andparameter information fields, and wherein the set of parameters in the network configuration is updated using information provided in the parameter information fields.

19. The wireless communication device of claim 16, wherein the configuration element comprises a vendor information element (IE), wherein the vendor IE comprises:at least one field identifying the network configuration in the predefined network configuration file as a master network configuration; andat least one field identifying a predefined sub-configuration file stored in the configuration database as an incremental network configuration, wherein a set of parameters defined in the master network configuration is updated using information in the incremental network configuration.

20. A method for wireless communication by a wireless communication device, comprising:receiving a beacon frame comprising a frame body from a mesh node device in a mesh wireless network,where the frame body comprises a configuration element that includes compressed network configuration information for the mesh wireless network, and where the configuration element comprises a file identifier identifying a predefined network configuration file stored in a configuration database; and communicating network traffic via the mesh wireless network using a network configuration selected from the predefined network configuration file in the configuration database using the file identifier.