Beacon extension design

Abstract

The present disclosure provides methods, components, devices, and systems for beacon extension design. A wireless station can receive one or more beacon containers including a beacon extension container and can communicate one or more messages based on a section of the one or more beacon containers related to the wireless station. Each section can correspond to a respective device type. Each section can include a frame check sequence and a message integrity code corresponding to each respective section. The wireless station can receive a first beacon container according to a first periodicity and a second beacon container according to a second periodicity. The first periodicity and the second periodicity can have different values based on a device type of the wireless station. The beacon container can include a type-specific section corresponding to the device type. Each type-specific section can include a parameter or updated information of the wireless station.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of Provisional Patent Application No. 63 / 614,990, entitled “BEACON EXTENSION DESIGN,” filed December 27, 2023, by Patil et al., and U.S. Patent Application No. 18 / 999,573, entitled “BEACON EXTENSION DESIGN,” filed December 23, 2024, by Patil et al.; each of these applications is assigned to the assignee of this application, and each of these applications is expressly incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates generally to wireless communication, and more specifically to beacon extension designs. A wireless station can receive one or more beacon containers including a beacon extension container and can convey one or more messages based on segments of the one or more beacon containers associated with the wireless station. Background Technology

[0004] A Wireless Local Area Network (WLAN) can be formed by one or more wireless access points (APs) that provide a shared wireless communication medium for use by multiple client devices (also known as wireless stations (STAs)). The basic building block of a WLAN conforming to the IEEE 802.11 standard family is the Basic Service Set (BSS) managed by the AP. Each BSS is identified by a Basic Service Set Identifier (BSSID) advertised by the AP. The AP periodically broadcasts beacon frames to enable any STA within the AP's wireless range to establish or maintain a communication link with the WLAN. Summary of the Invention

[0005] The systems, methods, and apparatus disclosed herein each have some innovative aspects, and no single aspect is solely responsible for the desired properties disclosed herein.

[0006] One innovative aspect of the subject matter described in this disclosure can be implemented in a first wireless device for wireless communication. The first wireless device may include a processing system comprising processor circuitry and memory circuitry storing code. The processing system may be configured to cause the first wireless device to: receive from a second wireless device a first message container comprising one or more type-specific segments of a first set, the first type-specific segment of the first set including one or more type-specific parameters; receive from the second wireless device a second message container comprising one or more type-specific segments of a second set, wherein both the first type-specific segments and the second type-specific segments correspond to a device type of the first wireless device; and communicate one or more messages to the second wireless device based on the first and second type-specific segments.

[0007] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication by a first wireless device. The method may include: receiving from a second wireless device a first message container comprising one or more type-specific segments of a first set, the first type-specific segment of the first set including one or more type-specific parameters; receiving from the second wireless device a second message container comprising one or more second set of type-specific segments, wherein both the first type-specific segment and the second type-specific segment of the second set correspond to a device type of the first wireless device; and communicating one or more messages to the second wireless device based on the first type-specific segment and the second type-specific segment.

[0008] Another innovative aspect of the subject matter described in this disclosure can be implemented in a first wireless device for wireless communication. The first wireless device may include: components for receiving from a second wireless device a first message container comprising one or more type-specific segments of a first set, the first type-specific segment of the first set including one or more type-specific parameters; components for receiving from the second wireless device a second message container comprising one or more type-specific segments of a second set, wherein both the first type-specific segment and the second type-specific segment of the second set correspond to a device type of the first wireless device; and components for communicating one or more messages with the second wireless device based on the first type-specific segment and the second type-specific segment.

[0009] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication. The code may include instructions executable by one or more processors to: receive from a second wireless device a first message container comprising one or more first group of type-specific segments, the first type-specific segment of the first group of one or more type-specific segments including one or more first group of type-specific parameters; receive from the second wireless device a second message container comprising one or more second group of type-specific segments, wherein both the first type-specific segment and the second type-specific segment of the second group of one or more type-specific segments correspond to a device type of the first wireless device; and communicate one or more messages to the second wireless device based on the first type-specific segment and the second type-specific segment.

[0010] In some examples of the methods described herein, the first wireless device, and the non-transitory computer-readable medium, the first message container and the second message container may be received via a main channel.

[0011] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, a single physical layer protocol data unit (PPDU) includes a first message container and a second message container.

[0012] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, the first physical layer protocol data unit (PPDU) includes a first message container and the second PPDU includes a second message container.

[0013] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, a first type-specific segment includes information for configuring the device type of the first wireless device and one or more generations of device types preceding that device type, and a second type-specific segment includes information for configuring the device type of the first wireless device.

[0014] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, a second type-specific segment indicates an update to at least one parameter in one or more of the first group of type-specific parameters.

[0015] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, a first type-specific segment, a second type-specific segment, or both include information elements, fields, or both.

[0016] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, a second group of one or more type-specific segments included in the second message container includes type-specific segments having values ​​that may have changed since the first message container was received.

[0017] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, receiving the first message container may include operations, features, components, or instructions for the following actions: receiving the first message container including an indication that at least a first portion of a first set of one or more type-specific parameters may be included in the first message container, at least a second portion of the first set of one or more type-specific parameters may be included in a second message container, or both, wherein the indication may be based on the device type of the first wireless device.

[0018] The methods described herein, examples of the first wireless device, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for: receiving a group of one or more first message containers according to a first periodicity; and receiving a group of one or more second message containers according to a second periodicity, wherein the second periodicity may be greater than the first periodicity.

[0019] The methods described herein, examples of the first wireless device, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for: periodically receiving a group of one or more first message containers according to a first periodicity, each of the group of one or more first message containers including one or more common parameters; and periodically receiving a group of one or more second message containers according to a second periodicity, each of the group of one or more second message containers including a second group of one or more type-specific parameters, wherein the second group of one or more type-specific parameters corresponds to the device type of the first wireless device.

[0020] Another innovative aspect of the subject matter described in this disclosure can be implemented in a second wireless device for wireless communication. The second wireless device may include a processing system comprising processor circuitry and memory circuitry storing code. The processing system may be configured to cause the second wireless device to: transmit a first message container comprising one or more type-specific segments of a first set, wherein the first type-specific segment of the first set of one or more type-specific segments includes one or more type-specific parameters; transmit a second message container comprising one or more type-specific segments of a second set, wherein both the first type-specific segment and the second type-specific segment of the second set of one or more type-specific segments correspond to a device type of the first wireless device; and communicate one or more messages to the first wireless device based on the first type-specific segment and the second type-specific segment.

[0021] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication by a second wireless device. The method may include: sending a first message container comprising one or more type-specific segments of a first set, the first type-specific segment of the first set including one or more type-specific parameters; sending a second message container comprising one or more type-specific segments of a second set, wherein both the first type-specific segments and the second type-specific segment of the second set correspond to a device type of the first wireless device; and communicating one or more messages to the first wireless device based on the first type-specific segments and the second type-specific segments.

[0022] Another innovative aspect of the subject matter described in this disclosure can be implemented in a second wireless device for wireless communication. The second wireless device may include: components for transmitting a first message container comprising one or more type-specific segments of a first set, the first type-specific segment of the first set including one or more type-specific parameters; components for transmitting a second message container comprising one or more type-specific segments of a second set, wherein both the first type-specific segment and the second type-specific segment of the second set correspond to a device type of the first wireless device; and components for communicating one or more messages with the first wireless device based on the first type-specific segment and the second type-specific segment.

[0023] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication. The code may include instructions executable by one or more processors to: transmit a first message container comprising one or more type-specific segments of a first set, the first type-specific segment of the first set including one or more type-specific parameters; transmit a second message container comprising one or more type-specific segments of a second set, wherein both the first type-specific segments and the second type-specific segment of the second set correspond to a device type of the first wireless device; and communicate one or more messages to the first wireless device based on the first and second type-specific segments.

[0024] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, the first message container and the second message container may be transmitted via the main channel.

[0025] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, a single physical layer protocol data unit (PPDU) includes a first message container and a second message container.

[0026] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, the first physical layer protocol data unit (PPDU) includes a first message container and the second PPDU includes a second message container.

[0027] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, a first type-specific segment includes information for configuring the device type of the first wireless device and one or more generations of device types preceding that device type, and a second type-specific segment includes information for configuring the device type of the first wireless device.

[0028] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, the second type-specific segment indicates an update to at least one parameter in one or more of the first group of type-specific parameters.

[0029] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, a first type-specific segment, a second type-specific segment, or both include information elements, fields, or both.

[0030] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, a second group of one or more type-specific segments included in the second message container includes type-specific segments having values ​​that may have changed since the first message container was sent.

[0031] The methods described herein, examples of second wireless devices, and non-transitory computer-readable media may also include operations, features, components, or instructions for: transmitting one or more first message containers according to a first periodicity; and transmitting one or more second message containers according to a second periodicity, wherein the second periodicity may be greater than the first periodicity.

[0032] The methods described herein, examples of second wireless devices, and nontransitory computer-readable media may also include operations, features, components, or instructions for: periodically transmitting a group of one or more first message containers according to a first periodicity, each of the group of one or more first message containers including one or more common parameters; and periodically transmitting a group of one or more second message containers according to a second periodicity, each of the group of one or more second message containers including a second group of one or more type-specific parameters, wherein the second group of one or more type-specific parameters corresponds to a device type of the first wireless device.

[0033] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, the second wireless device may be an access point.

[0034] Another innovative aspect of the subject matter described in this disclosure can be implemented in a first wireless device for wireless communication. The first wireless device may include a processing system comprising processor circuitry and memory circuitry storing code. The processing system may be configured to cause the first wireless device to: receive from a second wireless device a message extension container comprising one or more segments, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types; and to communicate one or more messages to the second wireless device based on the one or more common parameters and a first set of one or more type-specific parameters from the one or more segments corresponding to the device type of the first wireless device.

[0035] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication by a first wireless device. The method may include: receiving from a second wireless device a message extension container comprising one or more segments, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types; and communicating one or more messages to the second wireless device based on the one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment of the one or more segments corresponding to the device type of the first wireless device.

[0036] Another innovative aspect of the subject matter described in this disclosure can be implemented in a first wireless device for wireless communication. The first wireless device may include: components for receiving from a second wireless device a message extension container comprising one or more segments, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types; and components for communicating one or more messages with the second wireless device based on one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment of one or more segments corresponding to the device type of the first wireless device.

[0037] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication. The code may include instructions executable by one or more processors to: receive from a second wireless device a message extension container comprising one or more segments, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types; and communicate one or more messages to the second wireless device based on the one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment corresponding to the device type of the first wireless device.

[0038] In some examples of the methods described herein, the first wireless device, and the nontransitory computer-readable medium, conveying one or more messages may include operations, features, components, or instructions for the following actions: conveying one or more messages to an access point based on a second set of one or more type-specific parameters from one or more second type-specific segments, the one or more second type-specific segments being based on the device type of the first wireless device.

[0039] In some examples of the methods, first wireless devices, and nontransitory computer-readable media described herein, receiving a message extension container may include operations, features, components, or instructions for receiving a message extension container comprising a set of multiple frame check sequences, wherein each of one or more segments comprises a corresponding frame check sequence from the set of multiple frame check sequences.

[0040] In some examples of the methods, first wireless devices, and nontransitory computer-readable media described herein, receiving a message extension container may include operations, features, components, or instructions for receiving a message extension container comprising a set of multiple message integrity codes, wherein each of one or more segments comprises a corresponding message integrity code of the set of multiple message integrity codes.

[0041] Another innovative aspect of the subject matter described in this disclosure can be implemented in a second wireless device for wireless communication. The second wireless device may include a processing system comprising processor circuitry and memory circuitry storing code. The processing system may be configured to cause the second wireless device to: transmit a message extension container comprising one or more segments to a first wireless device, the one or more segments comprising a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments comprising a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types; and to communicate one or more messages to the first wireless device based on the one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment of one or more segments corresponding to the device type of the first wireless device.

[0042] Another innovative aspect of the subject matter described in this disclosure can be implemented in a method for wireless communication by a second wireless device. The method may include: transmitting a message extension container comprising one or more segments to a first wireless device, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types; and communicating one or more messages to the first wireless device based on the one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment in the one or more segments corresponding to the device type of the first wireless device.

[0043] Another innovative aspect of the subject matter described in this disclosure can be implemented in a second wireless device for wireless communication. The second wireless device may include: components for transmitting a message extension container comprising one or more segments to a first wireless device, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types; and components for communicating one or more messages with the first wireless device based on one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment of one or more segments corresponding to the device type of the first wireless device.

[0044] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transitory computer-readable medium storing code for wireless communication. The code may include instructions executable by one or more processors to: transmit a message extension container comprising one or more segments to a first wireless device, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types; and communicate one or more messages to the first wireless device based on the one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment corresponding to the device type of the first wireless device in the one or more segments.

[0045] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, conveying one or more messages may include operations, features, components, or instructions for the following actions: conveying one or more messages to the first wireless device based on a second set of one or more type-specific parameters from one or more second type-specific segments of one or more segments, the one or more second type-specific segments being based on the device type of the first wireless device.

[0046] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, the transmission message extension container may include operations, features, components, or instructions for transmitting a message extension container comprising a set of multiple frame check sequences, wherein each of one or more segments comprises a corresponding frame check sequence from the set of multiple frame check sequences.

[0047] In some examples of the methods described herein, the second wireless device, and the nontransitory computer-readable medium, receiving a message extension container may include operations, features, components, or instructions for: sending a message extension container comprising a set of multiple message integrity codes, wherein each of one or more segments comprises a corresponding message integrity code of the set of multiple message integrity codes.

[0048] Details of one or more specific embodiments 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, drawings, and claims. Note that the relative dimensions in the following drawings may not be drawn to scale. Attached Figure Description

[0049] Figure 1 A schematic diagram of an example wireless communication network is shown.

[0050] Figure 2An example Protocol Data Unit (PDU) is shown that can be used for communication between a wireless access point (AP) and one or more wireless stations (STA).

[0051] Figure 3 An example physical layer (PHY) protocol data unit (PPDU) capable of being used for communication between a wireless AP and one or more wireless STAs is shown.

[0052] Figure 4 A hierarchical format of an example PPDU capable of being used for communication between a wireless AP and one or more wireless STAs is shown.

[0053] Figure 5 A frequency diagram depicting an example distributed tone map is shown.

[0054] Figure 6 An example of a signaling diagram supporting beacon extension design is shown.

[0055] Figure 7 An example of a beacon frame diagram supporting the beacon extension design is shown.

[0056] Figure 8 An example message container diagram supporting the beacon extension design is shown.

[0057] Figure 9 An example of a signal timing diagram supporting a beacon extension design is shown.

[0058] Figure 10 An example of a signal timing diagram supporting a beacon extension design is shown.

[0059] Figure 11 An example of a signal timing diagram supporting a beacon extension design is shown.

[0060] Figure 12 An example message container diagram supporting the beacon extension design is shown.

[0061] Figure 13 and Figure 14 An example of the process flow supporting beacon extension design is shown.

[0062] Figure 15 A block diagram of an example wireless communication device supporting beacon extension design is shown.

[0063] Figure 16 A block diagram of an example wireless communication device supporting beacon extension design is shown.

[0064] Figure 17 and Figure 18 A flowchart illustrating an example process that can be performed by or at a first wireless device supporting a beacon extension design is shown.

[0065] Figure 19 A flowchart illustrating an example process that can be performed by or at a second wireless device that supports the beacon extension design is shown.

[0066] Figure 20 A flowchart illustrating an example process that can be performed by or at a first wireless device supporting a beacon extension design is shown.

[0067] Figure 21 A flowchart illustrating an example process that can be performed by or at a second wireless device that supports the beacon extension design is shown.

[0068] Similar reference numerals and names in the various figures indicate similar elements. Detailed Implementation

[0069] The following description refers to certain specific examples in order to illustrate the innovative aspects of this disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. Some or all of the examples described can be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals according to one or more of the following: the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, or Bluetooth as defined by the Bluetooth Special Interest Group (SIG). ® The standards, or Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)) standards published by the 3rd Generation Partnership Project (3GPP), etc. The described examples can be implemented in any device, system, or network 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), Space Division Multiple Access (SDMA), Rate Split Multiple Access (RSMA), Multi-User Shared Access (MUSA), Single-User (SU) Multiple-Input Multiple-Output (MIMO), and Multi-User (MU) MIMO (MU-MIMO). The described examples can also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of Wireless Personal Area Networks (WPANs), Wireless Local Area Networks (WLANs), Wireless Wide Area Networks (WWANs), Wireless Metropolitan Area Networks (WMANs), or Internet of Things (IoT) networks.

[0070] Various aspects broadly relate to a wireless station capable of receiving one or more message containers, including beacon frames and beacon extension frames, and capable of conveying one or more messages based on segments of one or more message containers associated with the wireless station. A message container can refer to data organized in a specific format for transmission. Examples of message containers are frames (such as frames conforming to the IEEE 802.11 series of wireless communication protocol standards or Physical Layer (PHY) Protocol Data Units (PPDUs), etc. Some aspects more specifically relate to one or more segments of a message container, each segment corresponding to a corresponding device type (or device generation). Each segment may include a Frame Check Sequence (FCS) and a Message Integrity Code (MIC) corresponding to each corresponding segment. In some specific implementations, the wireless station may parse a subset of one or more segments, including common segments for multiple device types and type-specific segments corresponding to the wireless station's device type. The wireless station may also perform error detection and integrity checks on each segment.

[0071] Some aspects also involve a wireless station receiving a set of message containers, including a first message container (such as a beacon frame), according to a first periodicity, and receiving a second message container (such as a beacon extension frame or a subsequent frame) according to a second periodicity. In some specific implementations, the beacon extension may be an example of a second message container that can offload information from the first message container (such as a legacy beacon frame). The first periodicity and the second periodicity may have different values ​​depending on the device type of the wireless station. Each message container may include a corresponding set of segments. The first message container may include one or more type-specific parameters in a type-specific segment corresponding to the device type. Type-specific parameters may refer to information that configures the device type and optionally configures subsequent generations or more of the device type to perform specific operations (such as one or more parameters for configuring a device conforming to the Ultra-High Reliability (UHR) IEEE standard).

[0072] The second message container may include updates to type-specific parameters in a second type-specific segment corresponding to the device type. While the first and second message containers may be described as beacon frames, beacon extension frames, similar beacon containers, or combinations thereof, it should be noted that the techniques described herein are applicable to any container (such as any frame or message container) comprising segments that can be divided into information segments, each segment associated with a different class or type of receiver (such as a radio station with a different device type or generation). In some specific implementations, the first message container, the second message container, or both may be a probe response frame (such as a broadcast probe response frame in response to a probe request frame), a (re)association response frame, a management frame (such as a new common action frame), or a probe response frame transmitted via a specific type of PPDU (such as a PPDU formatted according to the UHR PPDU format).

[0073] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some specific embodiments, by parsing relevant segments of one or more message containers, the described techniques can be used to allow the wireless station to save processing power, reduce the memory required to store content, and reduce the computational effort required to process large amounts of data (to generate MIC / FCS). Furthermore, the wireless station can receive communication parameters while avoiding exceeding the configured threshold length of the message container size (such as the beacon frame size) and can communicate according to the communication parameters.

[0074] In the following text Figure 1 – Figure 21 In the description, it should be noted that processes described as being performed by APs and STAs can be performed by one or more STAs (such as non-AP STAs), one or more APs, or any combination thereof. For example, a non-AP STA can send message containers or frames (such as broadcast probe request frames) to be received by multiple APs in neighboring (or network) networks belonging to different generations (or device types). In some specific implementations, the techniques described herein can be applied to, for example, reduce the amount of processing power at the receiving AP or reduce the size of the probe request frame. That is, although the following description describes an AP sending one or more message containers (such as beacon frames), the techniques described herein can be applied to situations where a non-AP STA sends one or more message containers (which may include beacon frames or other containers, such as broadcast probe request frames or other frames).

[0075] Figure 1A schematic diagram of an example wireless communication network 100 is shown. Depending on some aspects, the wireless communication network 100 may be an example of a wireless local area network (WLAN) (such as a Wi-Fi network). For example, the wireless communication network 100 may be a network implementing at least one of the IEEE 802.11 wireless communication protocol standard families (such as those defined by the IEEE 802.11-2020 specification or its revisions, including but not limited to 802.11ay, 802.11ax, 802.11az, 802.11ba, 802.11bd, 802.11be, 802.11bf, and 802.11bn). In some other examples, the wireless communication network 100 may be an example of a cellular radio access network (RAN), such as a 5G RAN or 6G RAN implementing one or more cellular protocols (such as those specified in one or more 3GPP standards). In some other examples, the wireless communication network 100 may include a WLAN that operates in a manner interoperable with or converged 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 these devices to connect to the core of the cellular network, such as accessing network management capabilities and functionality provided by the cellular network core. The terms “wireless communication device” and “wireless equipment” are used interchangeably and may encompass a radio station (STA) 104, a wireless access point (AP) 102, or both.

[0076] The wireless communication network 100 may include a number of wireless communication devices, including at least one wireless access point (AP) 102 and any number of wireless stations (STAs) 104. Although Figure 1 Only one AP 102 is shown, but the wireless communication network 100 may include multiple APs 102. AP 102 may be or represent various different types of network entities, including but not limited to home networking APs, enterprise APs, single-band APs, dual-band synchronous (DBS) APs, tri-band synchronous (TBS) APs, standalone APs, non-standalone APs, software-enabled APs (software APs), and multi-link APs (also known as AP multi-link devices (MLDs)), as well as cellular (such as 3GPP, 4G LTE, 5G, or 6G) base stations or other cellular network nodes (such as Node B, evolved Node B (eNB), gNB, Transmit Receive Point (TRP)) or another type of equipment or apparatus included in the radio access network (RAN), including open RAN (O-RAN) network entities such as central units (CUs), distributed units (DUs), or radio units (RUs).

[0077] Each STA 104 may also be referred to as a mobile station (MS), mobile device, mobile phone, wireless phone, access terminal (AT), user equipment (UE), subscriber station (SS), or subscriber unit, etc. STA 104 can represent a variety of devices such as mobile phones, other handheld or wearable communication devices, netbooks, laptops, tablets, laptops, Chromebooks, augmented reality (AR), virtual reality (VR), mixed reality (MR), or extended reality (XR) wireless headsets or other peripherals, wireless earbuds, other wearable devices, display devices (e.g., televisions, computer monitors, or video game 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, remote keys (e.g., for passive keyless entry and start (PKES) systems), Internet of Things (IoT) devices, vehicles, etc.

[0078] A single AP 102 and its associated set of STA 104s may be referred to as a Basic Service Set (BSS), which is managed by the respective AP 102. Figure 1 Additionally, an example coverage area 108 of AP 102 is shown, which may represent the Basic Service Area (BSA) of wireless communication network 100. The BSA can be identified by STA 104 and other devices via a Service Set Identifier (SSID) and a Basic Service Set Identifier (BSSID), which may be the Media Access Control (MAC) address of AP 102. AP 102 may periodically broadcast beacon frames (“beacons”) including the BSSID to enable any STA 104 within the wireless range of AP 102 to “associate” or reassociate with AP 102 to establish or maintain a corresponding communication link 106 (also referred to hereinafter as a “Wi-Fi link”) with AP 102. For example, the beacon may include an identifier or indication of the primary channel used by the corresponding AP 102, and a Timing Synchronization Function (TSF) for establishing or maintaining timing synchronization with AP 102. AP 102 can provide access to external networks to each STA 104 in the wireless communication network 100 via the corresponding communication link 106.

[0079] To establish a communication link 106 with AP 102, each STA 104 is configured to perform passive or active scanning operations (“scans”) on frequency channels in one or more frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, or 60 GHz bands). To perform a passive scan, STA 104 listens for beacons transmitted by the corresponding AP 102 at periodic time intervals (referred to as the Target Beacon Transmission Time (TBTT)). To perform an active scan, STA 104 generates probe requests and transmits these requests sequentially on each channel to be scanned, and listens for probe responses from AP 102. Each STA 104 can identify, determine, detect, or select an AP 102 to associate with based on the scanning information obtained through passive or active scanning, and performs authentication and association operations to establish a communication link 106 with the selected AP 102. The selected AP 102 assigns an association identifier (AID) to STA 104 at the end of the association operation, and AP 102 uses the association identifier (AID) to track STA 104.

[0080] As wireless networks become increasingly prevalent, STA 104 may have the opportunity to choose from one of many BSSs within its range or from multiple APs 102 that together form an Extended Service Set (ESS) (comprising multiple connected BSSs). For example, wireless communication network 100 may be connected to a wired or wireless distribution system capable of connecting multiple APs 102 in such an ESS. Therefore, STA 104 may be covered by more than one AP 102 and may be associated with different APs 102 at different times for different transmissions. Additionally, after associating with an AP 102, STA 104 may periodically scan its surroundings to find a more suitable AP 102 to associate with. For example, STA 104 moving relative to its associated AP 102 may perform a “roaming” scan to find another AP 102 with more desirable network characteristics, such as a larger Received Signal Strength Indicator (RSSI) or reduced traffic load.

[0081] STA 104 can form a network that does not have AP 102 or any other equipment besides STA 104 itself. An example of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may also be referred to as mesh networks or peer-to-peer (P2P) networks. In some implementations, ad hoc networks can be implemented within a larger network, such as wireless communication network 100. In such examples, while STA 104 may be able to communicate with each other via communication link 106 through AP 102, STA 104 may also communicate directly with each other via direct wireless communication link 110. Additionally, two STA 104 may communicate via direct wireless communication link 110, regardless of whether the two STA 104 are associated with and served by the same AP 102. In such ad hoc systems, one or more STAs among STA 104 may assume the role played by AP 102 in the BSS. Such STA 104 may be referred to as 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 Wi-Fi Tunneling Direct Link Establishment (TDLS) links, and other P2P group connections.

[0082] In some networks, AP 102 or STA 104, or both, can support applications associated with high throughput or low latency requirements, or provide lossless audio to one or more other devices. For example, AP 102 or STA 104 can support applications and implementations associated with ultra-low latency (ULL) (such as ULL gaming), or stream lossless audio and video to one or more personal audio devices (such as peripherals) or AR / VR / MR / XR headsets. In scenarios where a user uses two or more peripherals, AP 102 or STA 104 can support extended personal audio networks that enable communication with these two or more peripherals. Additionally, AP 102 and STA 104 can support additional ULL applications with ULL and high throughput requirements, such as cloud-based applications (such as VR cloud gaming).

[0083] As indicated above, in some implementations, AP 102 and STA 104 may operate and communicate according to one or more of the IEEE 802.11 wireless communication protocol family of standards (via the corresponding communication link 106). These standards define WLAN radio and baseband protocols for the physical (PHY) layer and MAC layer. AP 102 and STA 104 transmit and receive wireless communications to and from each other in the form of PHY Protocol Data Units (PPDUs) (also referred to below as "Wi-Fi communication" or "wireless packets").

[0084] Each PPDU is a composite structure comprising a PHY preamble and a payload in the form of a PHY Service Data Unit (PSDU). The information provided in the preamble can be used by the receiving device to decode subsequent data in the PSDU. In instances where the PPDU is transmitted on a bound channel or a wideband channel, the preamble field may be copied and transmitted in each of the 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 can be used for other purposes such as packet detection, automatic gain control, and channel estimation. The legacy preamble is also typically used to maintain compatibility with legacy equipment. The format, decoding, and information provided in the non-legacy portion of the preamble are associated with the specific IEEE 802.11 wireless communication protocol to be used to transmit the payload.

[0085] AP 102 and STA 104 in wireless communication network 100 can transmit PPDUs on unlicensed spectrum, which may be a portion of the spectrum including frequency bands traditionally used by Wi-Fi technologies, such as the 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, and 60 GHz bands. Some examples of AP 102 and STA 104 described herein can also communicate in other frequency bands that can support both licensed and unlicensed communication. For example, AP 102 or STA 104, or both, may also be able to communicate on licensed operating frequency bands, where multiple operators may have corresponding licenses to operate in the same or overlapping frequency ranges. Such licensed operating bands may be mapped to or associated with the following frequency ranges: FR1 (410MHz–7.125GHz), FR2 (24.25GHz–52.6GHz), FR3 (7.125GHz–24.25GHz), FR4a or FR4–1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz).

[0086] Each of these frequency bands may include multiple subbands and frequency channels (also referred to as subchannels). For example, PPDUs conforming to revisions of the IEEE 802.11n, 802.11ac, 802.11ax, 802.11be, and 802.11bn standards may be transmitted on one or more of the 2.4 GHz, 5 GHz, or 6 GHz frequency bands, each of which is divided into multiple 20 MHz channels. Therefore, these PPDUs are transmitted on physical channels with a minimum bandwidth of 20 MHz, but larger channels can be formed through channel bonding. For example, PPDUs may be transmitted on physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz, 240 MHz, 320 MHz, 480 MHz, or 640 MHz by bonding multiple 20 MHz channels together.

[0087] Furthermore, as described herein, the terms "channel" and "subchannel" are used interchangeably and each can refer to a portion of the spectrum through which communication between two or more wireless communication devices can be allocated. For example, a channel or subchannel can refer to a discrete portion (such as a discrete amount, span, range, or subset) of the frequency of the operating bandwidth. A channel or subchannel can refer to a 20MHz portion, a 40MHz portion, an 80MHz portion, or a 160MHz portion, etc. In other words, a channel or subchannel may include one or more 20MHz channels. A primary channel or subchannel can be understood as a portion of the spectrum that includes the primary 20MHz used for beacon transmission and other (management) frame transmission. A secondary channel or subchannel can be understood as a portion of the spectrum excluding the primary 20MHz (or at least excluding the main primary (M-Primary) channel). In some systems, a secondary channel or subchannel may include an opportunistic primary (O-Primary) channel. Wireless communication devices may use an M-Primary channel (such as M-Primary 20MHz) to transmit beacons and / or serve legacy clients, and may use an O-Primary channel (such as O-Primary 20MHz) for opportunistic access on one or more other channels (such as if the M-Primary channel is busy or occupied).

[0088] In some aspects, different portions of the spectrum (such as a 40MHz portion, an 80MHz portion, or a 160MHz portion) may be associated with multiple (20MHz) sub-channels and at least one anchor channel. In such aspects, the anchor channel may define, indicate, or identify the lowest (20MHz) sub-channel within a given portion of the spectrum. For example, a first anchor channel may define, indicate, or identify the lowest 20MHz sub-channel within a secondary 40MHz bandwidth, a second anchor channel may define, indicate, or identify the lowest 20MHz sub-channel within a secondary 80MHz bandwidth, and a third anchor channel may define, indicate, or identify the lowest 20MHz sub-channel within a secondary 160MHz bandwidth. In some aspects, wireless communication devices may use the anchor channel as an O-Primary channel.

[0089] In some wireless communication networks, an AP can send beacons to one or more STAs within a BSS. The beacon can play one or more roles in the operation of the BSS. For example, the beacon may include timing information (such as a TSF). The timing information provides a common clock for each STA across the BSS. The beacon may include a flow indicator that tells one or more STAs that the AP has buffered flow for one or more STAs. Additionally or alternatively, the beacon may indicate the AP's capability and operational attributes and may include mechanisms for indicating critical updates to one or more BSS parameters.

[0090] A group of one or more STAs with different device types (such as belonging to different generations) can each handle beacons from an AP. For example, a beacon from an AP belonging to one generation (such as an Extremely High Throughput (EHT) AP) can be handled by a STA (such as a non-AP STA) in a wireless communication network belonging to another generation or device type (such as 11a, 11b, 11g, 11n, 11ac, 11ax, or 11be generations). Each STA in the group of one or more STAs can determine that the AP supports its generation based on information elements (IEs) carried in the beacon (such as in the beacon frame) (such as capability elements and / or operational elements for that generation). For example, a STA in the group of one or more STAs can determine that the AP supports its generation based on the presence of IEs indicating capabilities and operations in the AP's beacon frame.

[0091] In some implementations, device type can be interpreted as or can refer to a specific generation of wireless devices, a set of devices from a specific version, or any combination thereof. In some implementations, device type (such as each generation of Wi-Fi devices) may have a set of IEs that define the device type, carrying information related to the device type (such as capabilities or operational information or other parameters). An AP (such as an EHT AP) may send elements belonging to its device type or generation (such as EHT) along with elements defined as part of the AP beacon frame by previous device types or generations (such as those from the 802.11 family of standards, including 11a, 11b, 11g, 11n, 11ac, 11ax, or 11be generations). Therefore, adding device type information can result in relatively large beacon frames (such as exceeding 2000 octets).

[0092] In some wireless communication networks, some devices (such as relatively old-generation devices) can resolve beacons whose size does not exceed a certain threshold. For example, a device may expect the beacon size to not exceed a specific length. The size threshold may vary depending on the device type (e.g., between 1500 and 1800 bytes). Devices encountering beacons exceeding the threshold size (or length) may not be able to resolve the complete beacon, which can cause various problems. For example, if a STA (such as an older-generation or device-type STA) cannot resolve the complete beacon, the STA may not be able to discover the AP's capability information and operating parameters, and therefore the STA is unlikely to communicate normally with the AP. If the AP includes additional elements that cause the beacon length to exceed the threshold size (such as due to critical updates), the STA may incorrectly conclude that the link with the AP has been lost. In some implementations, the STA may unassociate itself with the AP, which may disrupt ongoing traffic flow. The STA may begin sending probes to discover the AP and reassociate with it, which may result in increased management frame overhead. In some implementations, if the STA fails to resolve the complete beacon, the STA may "blacklist" the AP and avoid attempting to associate with it.

[0093] Furthermore, the beacon may include a Frame Check Sequence (FCS) following other information in the beacon frame, such as an IE related to the device type and operation. In some implementations, the STA may verify the FCS after successfully parsing the other information in the beacon frame. In such implementations, the STA may inefficiently use resources (such as processing and power) by parsing segments of the beacon frame that include information unrelated to the STA's device type. For example, before verifying the FCS, a first STA (such as an Ultra High Throughput (VHT) non-APSTA) with a first device type associated with an AP with a second device type (such as an Ultra High Reliability (UHR) AP) may parse information related to the second device type and potentially related to various other device types (such as High Efficiency (HE), EHT, and UHR IE). Therefore, the first STA may inefficiently use processing and power each time it receives a beacon (e.g., every 100 ms).

[0094] Wireless communication network 100 may include STA 104, which can receive frames (such as beacon extension frames or subsequent frames) carrying one or more IEs (such as IEs typically present in beacons). For example, AP 102 may offload some elements of a beacon frame (such as IEs defined by a specific device type) to be carried in a separate frame (such as a beacon extension frame). Wireless communication network 100 may provide beacon frames and beacon extension frames that take into account threshold sizes associated with some device types. Furthermore, wireless communication network 100 may provide flexibility such that STA 104 may parse (or process) only a portion of a frame (such as a portion of a frame associated with STA 104's device type). For example, STA 104 may parse fields, segments, or IEs associated with STA 104's device type, but may avoid parsing fields, segments, or IEs associated with other device types (such as those associated with devices several generations newer than STA 104). As described herein, a beacon extension frame may refer to a subsequent frame, a message container, or any combination thereof.

[0095] Figure 2 An example protocol data unit (PDU) 200 capable of wireless communication between a wireless access point (AP) and one or more wireless STAs is shown. For example, the AP and STA can be reference... Figure 1Examples of AP 102 and STA 104 are described. PDU 200 can be configured as a PPDU. As shown, PDU 200 includes a PHY preamble 202 and a PHY payload 204. For example, preamble 202 may include a legacy portion, which itself includes a legacy short training field (L-STF) 206 consisting of two symbols, a legacy long training field (L-LTF) 208 consisting of two symbols, and a legacy signal field (L-SIG) 210 consisting of two symbols. The legacy portion of preamble 202 may be configured according to the IEEE 802.11a wireless communication protocol standard. Preamble 202 may also include a non-legacy portion, which includes one or more non-legacy fields 212, for example, conforming to one or more of the IEEE 802.11 series of wireless communication protocol standards.

[0096] L-STF 206 generally enables receiving devices (such as AP 102 or STA 104) to perform coarse timing and frequency tracking, as well as automatic gain control (AGC). L-LTF 208 generally enables receiving devices to perform fine timing and frequency tracking, and also to perform initial estimation of the radio channel. L-SIG 210 generally enables receiving devices to determine (e.g., acquire, select, identify, detect, determine, calculate, or compute) the duration of the PDU and use the determined duration to avoid transmission over the PDU. The legacy portion of the preamble can be modulated according to a binary phase shift keying (BPSK) modulation scheme, including L-STF 206, L-LTF 208, and L-SIG 210. The payload 204 can be modulated according to a BPSK modulation scheme, a quadrature BPSK (Q-BPSK) modulation scheme, a quadrature amplitude modulation (QAM) modulation scheme, or another suitable modulation scheme. Payload 204 may include a PSDU containing a data field (DATA) 214, which in turn may carry higher-level data in the form of, for example, MAC Protocol Data Unit (MPDU) or Aggregated MPDU (A-MPDU).

[0097] Figure 3 An example physical layer (PHY) protocol data unit (PPDU) 350 capable of being used for communication between a wireless AP and one or more wireless STAs is shown. For example, the AP and STA can be reference... Figure 1Examples of AP 102 and STA 104 are described below. As shown, PPDU 350 includes a PHY preamble (which includes a legacy portion 352 and a non-legacy portion 354) and a payload 356 (which includes a data field 374). The legacy portion 352 of the preamble includes L-STF 358, L-LTF 360, and L-SIG 362. The non-legacy portion 354 of the preamble includes a repetition of L-SIG (RL-SIG) 364 and multiple wireless communication protocol version-related signal fields following RL-SIG 364. For example, the non-legacy portion 354 may include a general signal field 366 (referred to herein as "U-SIG 366") and an EHT signal field 368 (referred to herein as "EHT-SIG 368"). The presence of RL-SIG 364 and U-SIG 366 ensures compatibility with EHT or later versions. STA 104 indicates that PPDU 350 is an EHT PPDU or a PPDU conforming to a new wireless communication protocol (conforming to future IEEE 802.11 wireless communication protocol standards). One or both of U-SIG 366 and EHT-SIG 368 can be constructed as other wireless communication protocol versions above EHT that are associated with a revision of the IEEE standards family and carry version-related information. For example, U-SIG 366 can be used by receiving devices (such as AP102 and STA 104) to interpret bits in one or more of EHT-SIG 368 or data field 374. Similar to L-STF 358, L-LTF 360, and L-SIG 362, in instances involving the use of bound channels, the information in U-SIG 366 and EHT-SIG 368 can be repeated and transmitted in each of the component 20MHz channels.

[0098] The non-legacy portion 354 also includes an additional short training field 370 (referred to herein as "EHT-STF 370," though it can also be constructed for other wireless communication protocol versions above EHT and carry version-related information) and one or more additional long training fields 372 (referred to herein as "EHT-LTF 372," though they can also be constructed for other wireless communication protocol versions above EHT and carry version-related information). EHT-STF 370 can be used for timing and frequency tracking as well as AGC, while EHT-LTF 372 can be used for more refined channel estimation.

[0099] EHT-SIG 368 can be used by AP 102 to identify one or more STAs 104 and notify those STAs that AP 102 has scheduled uplink (UL) or downlink (DL) resources for them. EHT-SIG 368 can be decoded by each compatible STA 104 served by AP 102. EHT-SIG 368 can generally be used by the receiving device to interpret the bits in data field 374. For example, EHT-SIG 368 may include resource element (RU) allocation information, spatial flow configuration information, and per-user (e.g., STA-specific) signaling information. Each EHT-SIG 368 may include a common field and at least one user-specific field. In the context of OFDMA, the common field may indicate the RU distribution across multiple STAs 104, indicate RU assignment in the frequency domain, indicate which RUs are allocated for MU-MIMO transmission and which RUs correspond to OFDMA transmission, and the number of users in the allocation, etc. The user-specific field is assigned to a specific STA 104 and carries STA-specific scheduling information, such as user-specific MCS values ​​and user-specific RU allocation information. This information enables the corresponding STA 104 to identify and decode the corresponding RU in the associated data field 374.

[0100] Figure 4 A hierarchical format of an example PPDU capable of being used for communication between a wireless AP and one or more wireless STAs is shown. For example, the AP and STA can be references. Figure 1Examples of AP 102 and STA 104 described. As described, each PPDU 400 includes a PHY preamble 402 and a PSDU 404. Each PSDU 404 may represent (or “carry”) one or more MAC Protocol Data Units (MPDUs) 416. For example, each PSDU 404 may carry an aggregated MPDU (A-MPDU) 406, which includes an aggregation of multiple A-MPDU subframes 408. Each A-MPDU subframe 408 may include an MPDU frame 410 that includes a MAC delimiter 412 and a MAC header 414 preceding an accompanying MPDU 416, which includes the data portion (“payload” or “frame body”) of the MPDU frame 410. Each MPDU frame 410 may also include an FCS field 418 for error detection (e.g., the FCS field 418 may include a Cyclic Redundancy Check (CRC)) and padding bits 420. MPDU 416 may carry one or more MAC Service Data Units (MSDUs) 430. For example, MPDU 416 may carry an aggregated MSDU (A-MSDU) 422, which comprises multiple A-MSDU subframes 424. Each A-MSDU subframe 424 may be associated with an MSDU frame 426 (such as being an example of that MSDU frame or otherwise referred to as an MSDU frame) and may contain a corresponding MSDU 430, preceded by a subframe header 428 and, in some examples, followed by padding bits 432.

[0101] Returning to reference MPDU frame 410, MAC delimiter 412 can be used as a marker to indicate the start of associated MPDU 416 and the length of associated MPDU 416. MAC header 414 may include multiple fields containing information defining or indicating the characteristics or attributes of the data encapsulated within the frame body. MAC header 414 includes a duration field indicating the duration from the end of the PPDU until at least the end of the acknowledgment (ACK) or block ACK (BA) for that PPDU to be transmitted by the receiving wireless communication device. The use of the duration field is to reserve the radio medium for the indicated duration and to enable the receiving device to establish its Network Allocation Vector (NAV). MAC header 414 also includes one or more fields indicating the address of the data encapsulated within the frame body. For example, MAC header 414 may include a combination of source address, transmitter address, receiver address, or destination address. MAC header 414 may also include a frame control field containing control information. The frame control field may specify the frame type, such as a data frame, control frame, or management frame (such as a common action frame).

[0102] Some APs and STAs (e.g., reference) Figure 1The described AP 102 and STA 104 implement techniques for spatial reuse involving coordinated communication schemes. According to such techniques, AP 102 can contend for access to a radio medium to gain control of that medium for use in the TXOP. The AP that wins the contention (also referred to hereinafter as the "sharing AP") can select one or more other APs (also referred to hereinafter as the "shared AP") to share the TXOP's resources. The sharing AP and the shared APs can be located close to each other such that at least some of their radio coverage areas at least partially overlap. Some examples may specifically involve coordinated AP TDMA or OFDMA techniques for sharing time or frequency resources of the TXOP. To share the time or frequency resources of the TXOP, the sharing AP can divide the TXOP into multiple time segments or frequency segments, each time segment or frequency segment including a corresponding time or frequency resource representing a portion of the TXOP. The sharing AP can allocate the time or frequency segment to itself or to one or more of the shared APs. For example, each shared AP can use a portion of the TXOPs assigned by the shared AP to perform uplink or downlink communication with its associated STA.

[0103] In some examples of such TDMA technologies, each of the multiple sections of the TXOP includes a set of time resources that do not overlap with any time resources of any other section of the TXOP. In such examples, scheduling information may include indications of the time resources associated with each section of the TXOP among the multiple time resources. For example, scheduling information may include indications of time segments of the TXOP (such as indications of one or more time slots or sets of symbol periods associated with each section of the TXOP), such as for use in multi-user TDMA.

[0104] In some examples of OFDMA technology, each of the multiple sections of a TXOP includes a set of frequency resources that do not overlap with any frequency resources of any other section. In such examples, scheduling information may include indications of the frequency resources associated with each section of the TXOP. For example, scheduling information may include indications of bandwidth portions of a radio channel (such as indications of one or more sub-channels or resource elements associated with each section of the TXOP), such as for use in multi-user OFDMA.

[0105] In this way, the shared acquisition of TXOPs by a single AP enables communication between one or more additional shared APs and their respective BSSs with appropriate power control and link adaptation. For example, the sharing AP can limit the transmit power of a selected shared AP so that interference from the selected AP does not prevent the STA associated with the TXOP owner from successfully decoding packets transmitted by the sharing AP. Such techniques can be used to reduce latency because other APs can transmit and receive data according to conventional CSMA / CA or Enhanced Distributed Channel Access (EDCA) techniques without waiting to win contention for the TXOP. Additionally, by enabling a group of APs 102 associated with different BSSs to participate in a coordinated AP transmission session, during which the group of APs can share at least a portion of a single TXOP acquired by any of the participating APs, such techniques can increase throughput on the BSSs associated with the participating APs and also improve throughput fairness. Furthermore, by appropriately selecting the shared APs and scheduling their corresponding time or frequency resources, media utilization can be maximized or otherwise increased, while packet loss caused by overlapping BSS (OBSS) interference is minimized or otherwise reduced. Various specific implementations can achieve these and other advantages without requiring the sharing AP or the shared AP to know about the STA 104 associated with other BSSs, without requiring pre-assigned or dedicated master APs or pre-assigned AP groups, and without requiring backhaul coordination between APs participating in TXOP.

[0106] In some examples where the signal strength or interference level associated with the selected AP is relatively low (e.g., less than a given value), or when the decoding error rate of the selected AP is relatively low (e.g., less than a threshold), the start time of communication between different BSSs can be synchronized. Conversely, when the signal strength or interference level associated with the selected AP is relatively high (e.g., greater than a given value), or when the decoding error rate of the selected AP is relatively high (e.g., greater than a threshold), the start time can be offset from each other by a time period associated with decoding the preamble of the radio packet and determining whether the radio packet is an intra-BSS packet or an OBSS packet based on the decoded preamble. For example, the time period between the transmission of an intra-BSS packet and the transmission of an OBSS packet can allow the corresponding AP (or its associated STA) to decode the preamble of the radio packet and obtain the BSS color value carried in the radio packet to determine whether the radio packet is an intra-BSS packet or an OBSS packet. In this way, each of the participating APs and its associated STAs can be able to receive and decode intra-BSS packets in the presence of OBSS interference.

[0107] In some implementations, a shared AP may perform polling of a set of unmanaged or non-co-managed APs that support coordinated reuse to identify candidates for future space reuse opportunities. For example, a shared AP may send one or more space reuse polling frames to determine one or more space reuse criteria and select one or more other APs as part of the shared APs. Based on the polling, the shared AP may receive responses from one or more of the polled APs. In some specific examples, the shared AP may send a Coordinating AP TXOP Indication (CTI) frame to other APs, indicating the time and frequency of resources for a shareable TXOP. The shared AP may select one or more candidate APs upon receiving a Coordinating AP TXOP Request (CTR) frame from the corresponding candidate AP, indicating that the corresponding AP expects to participate in the TXOP. The polling response or CTR frame may include power indications, such as received (RX) power or RSSI measured by the corresponding AP. In some other examples, the shared AP may directly measure potential interference with services (such as UL transmission) supported at one or more APs and select the shared APs based on the measured potential interference. Shared APs typically select an AP to participate in coordinated space reuse, allowing it to still protect its own outgoing traffic and transmissions from STAs in its BSS (these transmissions may be referred to as primary transmissions). As described above, resources can be allocated to the selected AP during TXOP.

[0108] In certain environments, locations, or conditions, regulatory agencies may impose power spectral density (PSD) limits on one or more communication channels or on an entire frequency band (e.g., the 6 GHz band). PSD is a measure of transmit power as a function of unit bandwidth (such as per 1 MHz). Therefore, the total transmit power is the product of the PSD and the total bandwidth transmitted. Unlike the 2.4 GHz and 5 GHz bands, the Federal Communications Commission (FCC) has established PSD limits for low-power devices operating in the 6 GHz band. The FCC defines three power levels for operation in the 6 GHz band: standard power, low-power indoor, and ultra-low power. Some AP 102 and STA 104 devices operating in the 6 GHz band may meet the low-power indoor (LPI) power level, which limits the transmit power of AP 102 and STA 104 to 5 dBm / MHz and –1 dBm / MHz, respectively. In other words, the transmit power in the 6 GHz band is subject to PSD limitation on a per MHz basis.

[0109] Such PSD limitations unnecessarily reduce transmission range, decrease packet detection capability, and reduce channel estimation capabilities of AP 102 and STA 104. In some examples where transmission is PSD-limited, AP 102 or STA 104 of wireless communication network 100 can transmit over a larger transmission bandwidth to increase total transmission power, which can improve SNR and expand the coverage of wireless communication devices. For example, to overcome or relax PSD limitations and improve the SNR of low-power devices operating in PSD-limited bands, 802.11be introduced a duplicate (DUP) mode for transmission, in which data in the payload portion of the PPDU is modulated for transmission on a “basic” frequency subband (such as the first RU for OFDMA transmission) and copied (e.g., repeated) to another frequency subband (such as the second RU for OFDMA transmission). In DUP mode, two copies of the data are transmitted, and dual-carrier modulation (DCM) is used for each of the repeating RUs. This also has the effect of replicating the data, so that each of the repeating RUs carries two copies of the data, resulting in, for example, four copies of the data being transmitted. While the data rate for each copy of user data transmitted using DUP mode can be the same as that transmitted using "normal" mode, the transmit power using DUP mode is essentially doubled according to the number of copies of data being transmitted, at the cost of increased bandwidth. Therefore, using DUP mode may extend range but reduce spectral efficiency.

[0110] In some other examples where transmission is PSD-limited, distributed tone mapping operations can be used to increase the bandwidth that STA 104 can use to communicate uplink communications to AP 102. As used herein, the term "distributed transmission" refers to PPDU transmission on discontinuous tones (or subcarriers) of a wireless channel. In contrast, the term "continuous transmission" refers to PPDU transmission on continuous tones. As used herein, a logical RU represents the multiple tones or subcarriers assigned to a given STA 104 for transmitting PPDUs. As used herein, the term "regular RU" (or rRU) refers to any undistributed RU or multi-RU (MRU) tone scheme, such as configurations supported by 802.11be or earlier versions of the IEEE 802.11 wireless communication protocol family of standards. As used herein, the term "distributed RU" (or dRU) refers to tones distributed across a set of discontinuous subcarrier indexes mapped to by a logical RU. The term "distributed tone scheme" refers to the set of discontinuous subcarrier indexes associated with a dRU. The channel or portion of the channel that distributes the distributed tones is called the spread spectrum bandwidth, which can be, for example, 40 MHz, 80 MHz, or higher. The use of dRUs may be limited to uplink communication, as the benefits of overcoming PSD limitations may only exist in uplink communication.

[0111] Figure 5 A frequency diagram 500 depicting an example distributed tone map is shown. More specifically, Figure 5 An example mapping is shown of how the tones of the payload 501 of the PPDU 502 are distributed for transmission over the spread spectrum bandwidth of the wireless channel. In the illustrated example, the tones in the logical RU 504 associated with the payload 501 (which may represent an rRU of non-distributed tones according to a legacy tones scheme) are mapped to distributed RUs (dRUs) 506 according to a distributed tones scheme.

[0112] All aspects of this disclosure recognize that by distributing tones across a wider bandwidth, the per-tone transmit power of the logic RU 504 can be increased to provide greater flexibility in media utilization for wireless channels with PSD constraints. For example, when mapped to an rRU (such as the logic RU 504), the transmit power of the logic RU 504 may be severely limited based on the PSD of the wireless channel. For instance, in the 6 GHz band, the LPI power class limits the transmit power of AP 102 and STA 104 to 5 dBm / MHz and -1 dBm / MHz, respectively. Therefore, the per-tone transmit power of the logic RU 504 is limited by the number of tones mapped to each 1 MHz subchannel of the wireless channel.

[0113] By enabling the STA 104 to map modulation symbols in a distributed manner onto discontinuous tones scattered throughout the entire wireless channel, distributed transmission allows for increased per-tone transmission power for each individual distributed tone, and thus increases the total transmission power of the PPDU 502 without exceeding the PSD limit of the wireless channel. Figure 5 As shown in the example, STA 104 can map the logical RU 504 to a set of 26 non-contiguous subcarrier indices that span a 40MHz wireless channel (also referred to herein as the exemplary “spread spectrum bandwidth”). This contrasts with the tone mapping described above regarding the legacy tone scheme. Figure 5 The distributed tone mapping described effectively reduces the number of tones (in logic RU 504) in each 1MHz sub-channel. For example, each of the 26 tones can be mapped to a different 1MHz sub-channel within a 40MHz channel. Therefore, implementation... Figure 5 Each AP 102 or STA 104 with distributed tone mapping can maximize its per-tone transmit power (which in turn maximizes the total transmit power of logic RU 504).

[0114] In some examples ( Figure 5In a diagram (not shown), multiple logical RUs can be mapped to interleaved subcarrier indices of a shared radio channel. For example, STA 104 can modulate a portion of the symbols on multiple tones representing multiple logical RUs onto a non-contiguous subcarrier index associated with the shared radio channel according to a distributed tone scheme. Furthermore, distributed transmissions performed by multiple STA 104s can be multiplexed onto different distributed tone sets of the shared radio channel, such as to increase the transmit power of each device without sacrificing spectral efficiency. This increase in transmit power can be combined with some MCS to increase the range and throughput of wireless communication on PSD-limited radio channels. Distributed transmission can also improve packet detection and channel estimation capabilities.

[0115] To support distributed transmission, new packet designs and signaling can be used to indicate whether PPDU 502 is transmitted over tones spanning rRUs (such as logical RU 504) (according to the legacy tone scheme) or dRUs 506 (according to the distributed tone scheme). For example, the IEEE 802.11be standard revision or earlier versions of the IEEE 802.11 wireless communication protocol family of standards define a trigger frame format that can be used to request the transmission of trigger-based (TB) PPDUs from one or more STAs 104. The trigger frame allocates resources to the STA 104 for the transmission of the TB PPDU and indicates how the TB PPDU will be configured for transmission. For example, the trigger frame may indicate the logical RU or MRU allocated for transmission in the TB PPDU. In some specific implementations, the trigger frame may also be configured to carry tone distribution information indicating whether a logical RU (or MRU) is mapped to an rRU or a dRU.

[0116] In some implementations, STA 104 may include a distributed tone mapper that maps logical RU 504 to dRU 506 in the frequency domain. dRU 506 is converted to a time-domain signal (e.g., via inverse Fast Fourier Transform) for transmission over a wireless channel. AP 102 may receive the time-domain signal and reconstruct dRU 506 (e.g., via Fast Fourier Transform). In some implementations, AP 102 may include a distributed tone modulator that demaps dRU 506 back to logical RU 504. In other words, the distributed tone modulator inverts the mapping performed by the distributed tone mapper at STA 104. As a result of the demapping, AP 102 may recover the information carried (or modulated) on logical RU 504.

[0117] exist Figure 5 In the example, the logic RU 504 is uniformly distributed across the spread spectrum bandwidth. Although Figure 5The example shown illustrates a 40 MHz spread spectrum bandwidth, but spread spectrum bandwidths can also include 80 MHz, 160 MHz, or 320 MHz. In some implementations, the logic RU 504 can be mapped to any suitable pattern of non-contiguous subcarrier indexing. For example, in various implementations, the distance between any pair of adjacent modulated tones can be less than or greater than [missing information]. Figure 5 The distance described in the text.

[0118] Figure 6 An example of a signaling diagram 600 supporting a beacon extension design is shown. In some specific implementations, the signaling diagram 600 may implement, or be implemented by, aspects of the wireless communication network 100. For example, the signaling diagram 600 may include one or more STA 104s (such as STA 104-a and STA 104-b) and one or more AP 102s (such as AP 102-a), which may be examples of the corresponding wireless devices described herein. STA 104-a and STA 104-b may each be examples of user equipment (such as smartphones, laptops, or similar devices). STA 104-a and STA 104-b may each communicate with AP 102-a via one or more wireless links 602 (such as wireless links 602-a and 602-b). For example, STA 104-a may receive signaling 604-a from AP 102-a via radio link 602-a, and STA 104-b may receive signaling 604-b from AP 102-a via radio link 602-b. In the following description of signaling diagram 600, signaling 604-a may include information similar to signaling 604-b. For example, if signaling 604-a is described as including a first set of information, then signaling 604-b may include a second set of information similar to the first set of information.

[0119] Signaling 604-a and signaling 604-b may each include one or more beacon containers. For example, signaling 604-a may include beacon frames, beacon extension frames, or any combination thereof. It should be noted that signaling 604-a and signaling 604-b may be performed between one or more STA 104s (such as non-AP STAs). For example, STA 104-a may send one or more message containers (such as beacon frames, beacon extension frames, or other frames or containers) to STA 104-b. Therefore, although a message container as described herein may be described as being sent by AP 102 and received by STA 104, one or more STA 104s may send and / or receive message containers.

[0120] Figure 7An example of a beacon frame diagram 700 supporting beacon extension design is shown. In some implementations, the beacon frame diagram 700 may implement aspects of, or be implemented by, the wireless communication network 100, the signaling diagram 600, or both. For example, the beacon frame diagram 700 includes a beacon frame 702 that may be transmitted by AP 102 and received by STA 104. The beacon frame 702 may include one or more segments depicted as IE 704 (such as device types IE 704-a, 704-b, 704-c, 704-d, 704-e, etc.). The segments may be referred to as shared segments, which include one or more parameters shared by multiple different device types (such as device type IE704-a). The segments may also be referred to as type-specific segments, which include one or more parameters corresponding to a specific device type and may also be used by subsequent generation device types. In some implementations, the beacon frame 702 may support beacon protection. For example, beacon frame 702 may include fields that include information for performing error detection and message integrity procedures. To support such procedures, beacon frame 702 may include, for example, an FCS 706, a MIC, or both. In some specific implementations, beacon frame 702 may include device types IE 704 ordered by device type. For example, device type 1 IE 704-a may correspond to an older generation device compared to device type 2 IE 704-b, device type 2 IE 704-b may correspond to an older generation device compared to device type 3 IE 704-c, and so on.

[0121] In some implementations, STA 104 may receive beacon frame 702 and subsequently parse one or more device type IE 704. For example, if STA 104 is associated with or has device type 3, STA 104 may parse device type 3 IE 704-c. In some implementations, STA 104 may parse device type 1 IE 704-a and device type 2 IE 704-b, which may correspond to device generations older than the device generation of STA 104. STA 104 may also perform beacon protection procedures such as error detection and message integrity checks. For example, STA 104 may use FCS 706, MIC, or both to verify beacon frame 702 and to detect errors in information segments such as device type IE 704.

[0122] Figure 8An example of a message container diagram 800 supporting a beacon extension design is shown. In some specific implementations, the message container diagram 800 may implement aspects of, or be implemented by, the wireless communication network 100, the signaling diagram 600, or both. For example, the message container diagram 800 includes a message container 802 (or a beacon container) that can be sent by AP 102 and received by STA 104. The message container 802 may include one or more segments 804 (such as segments 804-a, 804-b, 804-c, 804-d, 804-e). The starting segment may be referred to as a shared segment, which includes one or more shared parameters (such as a pre-UHR segment with one or more shared parameters) that can be used by multiple different device generations. As discussed herein, shared parameters may refer to parameters that are shared or can be used by multiple different device types, devices, generations, and / or different versions of IEEE 802.11 (such as 802.11be, 802.11ax, etc.).

[0123] Each of one or more segments 804 may include a corresponding MIC 806, FCS 808, one or more IE 810s (such as fields with one or more parameters), or any combination thereof. Segments following common segment 804-a may each be a different type-specific type (such as type-specific segments) that includes one or more parameters for the corresponding device type (such as UHR, UHR+, UHR++, UHR+++, etc.). Each type-specific segment may include one or more type-specific parameters (such as IE) corresponding to a specific device type (such as a specific generation) and may be usable by subsequent generation devices.

[0124] In some implementations, message container 802 may refer to a beacon extension container, a PPDU, or a similar message container. In some implementations, message container 802 may be a beacon extension frame including one or more segments 804 (such as segments 804-a, 804-b, 804-c, 804-d, 804-e). In some implementations, message container 802 may be a PPDU, and the segments 804 of the PPDU may be a set of independent beacon extension containers (such as a set of beacon extension frames). Therefore, a PPDU may carry multiple independent beacon extension containers, each of which includes information or parameters corresponding to the device type or generation.

[0125] In some implementations, the message container may include a strict ordering of segments 804. For example, segments 804 may be ordered according to device type (such as from older generation to newer generation devices). In some implementations, device type 1 segment 804-a may correspond to an older generation device compared to device type 2 segment 804-b, device type 2 segment 804-b may correspond to an older generation device compared to device type 3 segment 804-c, and so on. In some implementations, STA 104 may have a device type (such as device type 3, corresponding to the UHR generation) and may use the corresponding MIC 806, FCS 808, or both to verify one or more IE 810s in at least a subset of segments 804. For example, STA 104 can resolve device type 3 segment 804-c (including IE 810) and uses MIC 806, FCS 808, or both to verify IE 810, and similarly can resolve and verify segments 804-a and 804-b. Therefore, STA 104 can resolve segment 804 corresponding to its generation or device type, and can additionally or alternatively resolve segment 804 corresponding to a previous generation or device type. For example, STA 104 can parse segment 804 (such as fields or IEs) up to its generation (such as up to segment 804-c), can verify the FCS associated with each segment 804 (such as verifying the FCS in segment 804-a, the FCS in segment 804-b, and the FCS in segment 804-c) or the FCS corresponding to its generation (such as only verifying the FCS in segment 804-c, but skipping verifying the FCS in segment 804-b and the FCS in segment 804-a), or both, and can avoid parsing or processing the remaining segments 804. That is, STA 104 can skip the remaining segments 804.

[0126] In some implementations, MIC 806, FCS 808, or both may be incremental across different segments 804. For example, each MIC 806 and FCS 808 may not be self-contained; rather, a given MIC 806 and a given FCS 808 may be applied across one or more previous segments. Therefore, when resolving multiple segments 804, a receiver (such as STA 104) may skip MIC 806 and FCS 808 up to the segment 804 corresponding to the receiver's device type (or generation). For example, MIC 806 and FCS 808 in device type 3 segment 804-c may correspond to each set of IE 810 in segments 804-a, 804-b, and 804-c. In some implementations, STA 104 can resolve IE 810 in segments 804-a, 804-b, and 804-c, and can use MIC 806 and FCS 808 in segment 804-c to perform error detection and message verification. For example, STA 104 can perform a single set of error detection and message verification procedures on multiple segments in message container 802.

[0127] In some implementations, AP 102 may send one or more message containers 802, including a first message container and a second message container. The first message container may be a beacon container or a beacon extension container. Similarly, the second message container may be a beacon container or a beacon extension container. A given message container 802 may include one or more segments 804 from a set of segments 804 associated with a plurality of STAs 104 of the wireless communication network. For example, the first message container may include a first portion of IE 810 or a segment 804 from that set of segments 804. The second message container may include a second portion of IE 810 or a segment 804 from that set of segments 804.

[0128] In some implementations, AP 102 may not include all segments (such as fields / IEs) in every beacon frame, beacon extension frame, or both sent by the AP. In the example, AP 102 may only include segments (such as fields / IEs) whose values ​​have changed. In the example, the second message container 802 may include IEs 810 or segments 804 whose values ​​have changed since AP 102 sent the first message container 802. In some implementations, both the first message container 802 and the second message container 802 may include at most some segments or some network IEs 810, such as TSFs, traffic indicators, or similar information. For example, AP 102 may include network IEs 810 in every message container 802 sent by AP 102.

[0129] In some implementations, a critical update mechanism in message container 802 may indicate a change to one or more operating parameters at a wireless device (such as STA 104 or AP 102). The change count field in the critical update mechanism may indicate the most recent (such as latest or most recent) set of parameters and may also indicate other markers (such as a Critical Update Frame (CUF) marker or an Include All Updates (AUI) marker). Similarly, the change count field may indicate the presence of updated parameters. A wireless device (such as STA 104 or AP 102) may include one or more critical update mechanisms or frames corresponding to one or more device types (or generations of devices). Alternatively or additionally, message container 802 may include a shared critical update frame, wherein each segment 804 contains markers indicating whether one or more parameters corresponding to the device type or generation of the respective segment 804 have changed. In some implementations, during an update (such as a critical update), a separate message container 802 (such as a beacon frame) may include fields or IEs corresponding to the update.

[0130] STA 104 may perform an active scan (or probe) to discover IE 810 (such as attributes) associated with the BSS of AP 102. For example, in some implementations, STA 104 may perform an active scan instead of a pass-through scan (e.g., if a passive scan is insufficient to obtain relevant attributes from AP 102). In some implementations, AP 102 may send message container 802 as part of (or during) a Delivery Flow Indication Message (DTIM). Message container 802 (such as a beacon extension frame or PPDU) may carry a complete profile associated with AP 102, STA 104, or both. In some implementations, the first Delivery Flow Indication Message (DTIM) interval associated with a first device type may differ from the second DTIM interval associated with a second device type, such that AP 102 sends DTIMs of different device types at different instances (e.g., therefore not carrying all information simultaneously). Therefore, AP 102 may control or limit the size of message container 802.

[0131] It should be noted that a hybrid approach can be applied, where different device types (such as generations) can have different periodicities to include the corresponding device type-specific attributes in beacon frames, beacon extension frames, or both, and the beacon frames carry one or more segments (such as fields / IEs) corresponding to critical updates.

[0132] Each segment 804 may include a MIC 806, enabling the STA 104 to perform integrity checks on each segment 804. For example, the corresponding integrity check within each segment 804 may be "self-contained." In some implementations, the MIC 806 in each segment 804 may include one or more security parameters shared by one or more device types. In such implementations, the security parameters for each segment 804 may be the same set of security parameters. In some implementations, if the security parameters for each segment are the same set of security parameters, the shared segment 804 may include security parameters (such as a key identifier, a block number, or both). Alternatively or additionally, at most each device type may correspond to a different set of security parameters (such as a different key identifier, a different block number, or both for each device type). For example, if a device type has a relatively strong security algorithm, the MIC 806 corresponding to the device type may include a specific set of security parameters that differs from another set of security parameters corresponding to other device types. In some implementations, the STA 104 may verify data integrity based on the block number and key identifier in each segment 804.

[0133] In some implementations, the information included in segment 804 may be protected with integrity (e.g., via MIC 806 as described herein). In some implementations, the content included in segment 804 may be encrypted. In such implementations, a first set of segments 804 may have one or more common security parameters, while a second set of segments 804 may have one or more type-specific security parameters based on the device type corresponding to the segment 804. In some implementations, one or more type-specific security parameters may be relatively advanced (e.g., having stronger or more complex encryption) compared to the common security parameters. For example, common security parameters may have relatively low face values.

[0134] Figure 9 An example of a signal timing diagram 900 supporting a beacon extension design is shown. In some specific implementations, the signal timing diagram 900 may implement aspects of, or be implemented by, the wireless communication network 100, the signaling diagram 600, the message container diagram 800, or any combination thereof. For example, the signal timing diagram 900 includes one or more message containers 902 (such as message containers 902-a, 902-b, 902-c, 902-d, 902-e, 902-f, etc.), which may be references Figure 8 A corresponding example of the described message container 802. AP 102 may send one or more message containers 902, such that at least one STA 104 can receive each message container in message container 902. Each message container 902 may include one or more common segments 904, one or more type-specific segments 906, or any combination thereof. In some specific implementations, refer to... Figure 9 The techniques described herein may be combined with other techniques described herein.

[0135] In some implementations, different device types may be associated with different periodicities, allowing AP 102 to send type-specific IEs or attributes (such as IEs or attributes associated with a specific device type or generation) in at least a portion of a set of sent message containers 902. For example, a first device type (or device generation) may be associated with a first periodicity 908. AP 102 may send message container 902-a, and message container 902-b may be sent after the first periodicity 908 (such as after a first time duration). Message containers 902-a and 902-b may each contain a common segment 904 and one or more type-specific segments 906 (such as IEs specific to a device type or device generation). The type-specific segments 906 (including type-specific IEs) in message containers 902-a and 902-b may correspond to the first device type, and therefore a first STA 104 having the first device type may periodically receive IEs (including parameters) corresponding to the first device type according to the first periodicity.

[0136] In some implementations, message containers (such as message containers 902-a and 902-b) may include a shared segment 904 and zero or more type-specific segments 906. In such implementations, periodicity 908 may be associated with the transmission of information shared by STAs 104 in the BSS of AP 102. For example, AP 102 may transmit network information (such as fields or IEs) including TSFs, traffic indicators, or similar information in each message container 902. In some implementations, the periodicity corresponding to a beacon frame may be greater than the first periodicity 908, allowing one or more STAs 104 in the BSS to receive network information at a higher frequency than one or more STAs 104 receiving beacon frames. For example, the first periodicity may be defined as a relatively short interval or may have the same value as another interval (such as dot11FILSFDFrameBeaconMaximumInterval, or 100 milliseconds).

[0137] In some implementations, a second device type may be associated with a second periodicity 910. For example, AP 102 may send message container 902-c, and message container 902-f may be sent after the second periodicity 910 (such as after a second time duration). Message containers 902-c and 902-f may each contain a common segment 904 and a type-specific segment 906. The type-specific segment 906 (including type-specific IEs) in message containers 902-c and 902-f may correspond to the second device type. Therefore, a second STA 104 having the second device type may periodically receive IEs corresponding to the second device type, including operational IEs and capability IEs, according to the second periodicity 910. For example, operational IEs and capability IEs may appear once every n beacons, where n may have different values ​​or the same value for a single device type. In addition, the periodicity of legacy beacons can be increased (from 100ms to 500ms) and shorter beacon-like frames (such as Fast Initial Link Establishment (FILS) discovery) carrying selected segments (such as the base field / IE) can be transmitted approximately every 100ms. Shorter beacon intervals can be specified, or the MIB (such as dot11FILSFDFrameBeaconMaximumInterval) can be set to 100ms.

[0138] It should be noted that a hybrid approach can be applied, in which AP 102 may not include all segments (such as fields / IEs) in every beacon frame, beacon extension frame, or both transmitted by AP 102, and different device types (such as generations) may have different periodicity to include the corresponding device type-specific attributes in the beacon frame, beacon extension frame, or both.

[0139] In some implementations, a specific common segment 904 may include information (such as fields or IEs) applicable to more than one device type (such as applicable to multiple generations or all generations of devices). Specific common segment 904 may include an FCS and an existence bitmap. The existence bitmap may indicate which fields or IEs exist in the specific common segment 904. The existence bitmap may indicate capability information of AP 102, such as features that AP 102 can support. Additionally or alternatively, a specific common segment 904 may include mechanisms for identifying the order of segments within a given message container 902. For example, a specific common segment 904 may include fields identifying the existence and order of segments relative to device type (or generation). In some implementations, each common segment 904 and each type-specific segment 906 may include a corresponding field (such as at the beginning of the segment) identifying the device type corresponding to the respective segment.

[0140] In some implementations, a segment (such as a common segment 904 or a type-specific segment 906) may include indications of which fields or IEs are present in the segment. For example, a segment may include a bitmap identifying each IE or field, or the category of an IE or field. In some implementations, the bitmap may include bit flags indicating a complete or partial profile. For example, a "0" may indicate that the segment includes a partial profile corresponding to a device type, while a "1" may indicate that the segment includes a complete profile corresponding to a device type.

[0141] In some implementations, a specific message container 902 (such as any message container 902, a beacon frame, or a probe response frame) may include indications of which device type (or generation) is included in a corresponding segment of the specific message container 902. The specific message container 902 may include a bitmap having bits corresponding to each supported device type. For example, a "0" may indicate that the specific message container 902 does not include information related to a specific device type, while a "1" may indicate that the specific message container 902 includes information for a specific device type. In some implementations, one or more bits in the bitmap may indicate which device types (or generations) are supported by the AP 102. For example, a "0" may indicate that a specific device type is not supported by the AP 102, while a "1" may indicate that a specific device type is supported by the AP 102.

[0142] In some implementations, message container 902-a may be an example of a beacon frame. The beacon frame may include indications as to whether AP 102 can send a beacon extension frame (or message extension container). For example, the beacon frame may indicate whether all information is included in the beacon frame and may similarly indicate whether a particular portion is carried in the beacon extension frame. The beacon frame may also include indications indicating whether an IE or segment corresponding to the device type is carried within the beacon frame, or whether an IE or segment corresponding to the device type is carried within the beacon extension frame.

[0143] In some implementations, segments (such as shared segment 904 or type-specific segment 906) may include a length field. The length field may indicate the length of the segment. For example, the length field may indicate the number of bytes occupied by the segment. STA 104 may identify the value in the length field before parsing each segment in message container 902. STA 104 may also determine the generation corresponding to each segment. If STA 104 determines that a given segment is not related to the device type of STA 104, STA 104 may skip the segment by skipping the number of bytes corresponding to the length field of the given segment.

[0144] The framework discussed in this paper provides APs with the flexibility to announce one or more self-contained type-specific parameters or to announce parameters incrementally, such as when each new device type (such as a new generation) is built on top of one or more previous generations (such as when only one or more new parameters defined by that generation are included in the generation segment).

[0145] In some implementations, AP 102 may support processes associated with multiple BSS identifiers (MBSSIDs). For example, AP 102 may send a BSSID, and the sent BSSID may correspond to a sent beacon extension frame carrying one or more MBSSID IEs. In some implementations, the sent beacon extension frame may include an MBSSID extension IE corresponding to the beacon extension frame. Therefore, the beacon extension frame may include information identifying unsent BSSIDs. In some implementations, MBSSID inheritance may be based on any of the following: message container 902-a (or beacon frame) and message container 902-b (or subsequent beacon extension frames), independent content or information within each message container 902, or any combination thereof. For example, the MBSSID of a BSS may be inherited based on one or more message containers 902. Additionally or alternatively, the MBSSID may be inherited based on an IE within a message container 902.

[0146] Figure 10 An example of a signal timing diagram 1000 supporting a beacon extension design is shown. In some specific implementations, the signal timing diagram 1000 may implement aspects of, or be implemented by, the wireless communication network 100, the signaling diagram 600, the message container diagram 800, the signal timing diagram 900, or any combination thereof. For example, the signal timing diagram 1000 includes one or more first message containers 1002 (such as first message containers 1002-a, 1002-b, 1002-c, 1002-d, 1002-e, etc.) and one or more second message containers 1004 (such as second message containers 1004-a, 1004-b, etc.), which may be references. Figure 8 A corresponding example of the described message container 802. AP 102 may send one or more message containers 1002 and 1004, such that at least one STA 104 may receive each of message containers 1002 and 1004.

[0147] In some implementations, the first message container 1002 may be a corresponding example of a beacon frame. The first message container 1002 may include network information such as TSF, traffic indicators, or similar information (such as segments including basic fields / IEs). Additionally or alternatively, the first message container 1002 may include update information (such as critical updates to parameters associated with a specific or common type of STA 104), one or more fields with frequently changing data (such as between beacon frames, beacon extension frames, or both), or similar information associated with the type of device receiving STA 104. The first message container 1002 may be associated with a first periodicity 1006. For example, AP 102 may send the first message container 1002-a, and after a first time duration (such as corresponding to the first periodicity 1006), AP 102 may send the first message container 1002-b.

[0148] In some implementations, the second message container 1004 may be a corresponding example of a beacon extension frame. The second message container 1004 may include other information, such as type-specific IEs, parameter updates, or similar information. In some implementations, AP 102 may send the second message container 1004 during DTIM beacon transmission. Each device type may correspond to a corresponding DTIM interval, such that AP 102 sends DTIMs for different device types at different instances (e.g., so that not all information is carried simultaneously). Therefore, AP 102 may control or limit the size of the second message container 1004. The second message container 1004 may be associated with a second periodicity 1008. For example, AP 102 may send the second message container 1004-a, and after a second time duration (such as corresponding to the second periodicity 1008), AP 102 may send the second message container 1004-b. The value of the second periodicity 1008 may be greater than the value of the first periodicity 1006.

[0149] It should be noted that a hybrid approach can be applied, where different device types (such as generations) can have different periodicities to include the corresponding device type-specific attributes in beacon frames, beacon extension frames, or both, and beacon frames carry one or more segments (such as base fields / IE) and critical updates, while beacon extension frames carry one or more other segments (such as other fields / IE).

[0150] Figure 11An example of a signal timing diagram 1100 supporting a beacon extension design is shown. In some specific implementations, the signal timing diagram 1100 may implement aspects of, or be implemented by, the wireless communication network 100, the signaling diagram 600, the message container diagram 800, the signal timing diagram 900, or any combination thereof. For example, the signal timing diagram 1100 includes one or more first message containers 1102 (such as first message containers 1102-a, 1102-b, 1102-c, 1102-d, 1102-e, etc.) and one or more second message containers 1104 (such as second message containers 1104-a, 1104-b, etc.), which may be references. Figure 8 A corresponding example of the described message container 802. AP 102 may send one or more message containers 1102 and 1104, such that at least one STA 104 may receive each of message containers 1102 and 1104.

[0151] In some specific implementations, such as for greenfield deployments, AP 102 may send a first message container 1102 (which may be a beacon extended frame or PPDU) according to a first periodicity 1106. The first message container 1102 may be shorter than the second message container 1104 (or may occupy less data or memory than the second message container). The first message container 1102 may include network information such as TSF, traffic indicators, and quick initial link setup information (such as basic fields / IE). Additionally or alternatively, the first message container 1102 may each include update information (such as critical updates to signaling parameters).

[0152] AP 102 may similarly send a second message container 1104 (which may be a beacon frame) according to the second periodicity 1108. The second message container may include a complete profile of the device type (including signaling parameters). In some implementations, the second message container may include semi-static fields. The second periodicity 1108 may correspond to a longer duration than the first periodicity 1106.

[0153] Figure 12 An example of a message container diagram 1200 supporting a beacon extension design is shown. In some implementations, message container diagram 1200 may implement aspects of, or be implemented by, wireless communication network 100, signaling diagram 600, message container diagram 800, or any combination thereof. For example, message container diagram 1200 includes message container 1202 (or beacon container) that can be sent by AP 102 and received by STA 104. Message container 1202 may include one or more segments or fields. Each segment or field may include a corresponding set of information. In some implementations, message container 1202 may be referred to as a mini-beacon (such as a type-specific mini-beacon or a generation-specific mini-beacon).

[0154] In some implementations, STA 104 may receive a message container 1202 from AP 102, which includes a set of information. The message container 1202 may be a beacon frame, a beacon extension frame, or a type-specific mini-beacon. For example, the fields may include header field 1204 (such as an MPDU header). In some implementations, this set of information may include a TSF 1206 with relatively high granularity (such as sub-microsecond granularity). This set of information may include a traffic indication 1208 (such as a TIM) supporting compression, secondary assignment, or similar processes.

[0155] In some implementations, this set of information may include a bitmap 1210 indicating one or more device types (or generations) supported by AP 102. Bitmap 1210 may include a payload 1218 (such as an IE payload) comprising a set of bits 1220. Each bit in this set of bits may correspond to a device type (such as a device generation) from a set of device types. For example, if message container 1202 includes information related to a first device type, bit 1220-a corresponding to the first device type may have a value "1". If message container 1202 does not include information related to a second device type, bit 1220 corresponding to the second device type may have a value "0".

[0156] In some implementations, this set of information may include a set of additional IEs 1212, which includes a set of IEs or fields. For example, the set of IEs or fields may include the most recently updated IE (such as the IE updated since the last transmission). AP 102 may include a set of IEs or fields for a certain number of beacon intervals (such as 10 beacon intervals or up to the next x-th DTIM, where x is the ordinal number of the DTIM). For example, AP 102 may include a set of IEs or fields for a certain number of consecutive beacons of a specific device type. In some implementations, AP 102 may limit the number of consecutive beacons that may include a set of IEs or fields for a specific device type. In some implementations, this set of information may include MIC 1214 and FCS 1216. MIC 1214 and FCS 1216 may each correspond to the content of an entire frame (e.g., MIC 1214 and FCS 1216 may be calculated at the wireless communication device across the content of the entire frame).

[0157] In some implementations, STA 104 may determine the capability and operational parameters of AP 102 based on message container 1202. STA 104 may perform a probing process. For example, STA 104 may include a request element (e.g., as part of a probing process) to request a specific IE (such as an IE belonging to AP 102) from AP 102. In some implementations, a group of STA 104s (such as a group not associated with AP 102) may perform an active scan to collect the capability parameters, operational parameters, or other attributes of AP 102.

[0158] Figure 13 An example of a process flow 1300 supporting beacon extension design is shown. Process flow 1300 includes AP102-b and STA 104-c, which can be as relative to... Figure 1 and Figure 6 Examples of the corresponding devices described. In the following description of process flow 1300, the operations between AP 102-b and STA 104-c may be performed in a different order than the example order shown. Some operations may also be omitted from process flow 1300, and other operations may be added to process flow 1300. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously. Although these operations may be described as being performed between AP 102-b and STA 104-c, these operations may be performed between one or more STA 104, one or more AP 102, or any combination thereof. Additionally, the techniques discussed in this figure and throughout this application can be applied to infrastructure BSSs (e.g., BSSs set up by APs) or non-infrastructure BSSs (e.g., as P2P networks, such as TDLS, Wi-Fi Direct, etc.).

[0159] At 1302, STA 104-c can receive beacon frames from AP 102-b. The beacon frame can be as shown in the reference. Figure 7 An example of a beacon frame as described. For instance, a beacon frame may include one or more communication parameters for STA 104-c.

[0160] At 1304, STA 104-c can receive a first message container from AP 102-b, comprising one or more type-specific segments of a first group. The first type-specific segment in the first group of one or more type-specific segments may include one or more type-specific parameters of the first group. In some embodiments, the first message container may include an indication (such as an indication carried in a beacon frame or probe response frame) indicating that at least a first portion of the first group of one or more type-specific parameters is included in the first message container, at least a second portion of the first group of one or more type-specific parameters is included in a second message container, or both. This indication is based on the device type of STA 104-c.

[0161] In some implementations, STA 104-c may receive one or more first message containers from AP 102-b according to a first periodicity. In some implementations, the group of one or more first message containers may include first message containers. Each first message container in the group of one or more first message containers may include one or more common parameters.

[0162] At 1306, STA 104-c may receive from AP 102-b a second message container comprising one or more type-specific segments of a second group. In some implementations, the first message container may be an example of a beacon frame, and the second message container may be an example of a beacon extension frame (such as a subsequent frame).

[0163] Both the first type-specific segment and the second type-specific segment in the second group of one or more type-specific segments may correspond to the device type of STA 104-c. In some embodiments, the second type-specific segment may indicate an update to at least one parameter in the first group of one or more type-specific parameters. In some embodiments, the second message container may include one or more FCSs. Each segment in the second group of one or more type-specific segments includes a corresponding Frame Check Sequence (FCS) in one or more Frame Check Sequences (FCS). In some embodiments, the second message container may include one or more MICs. Each segment in the second group of one or more type-specific segments may include a corresponding MIC in one or more MICs. In some embodiments, at least one type-specific segment in the second group of one or more type-specific segments may include an indication of the length of at least one type-specific segment.

[0164] The second message container may be an example of a type-specific management frame (such as a type-specific beacon or a type-specific mini-beacon), which includes at least one of the following: a first flow indicator, a first TSF, an indication of one or more supported device types, a type-specific parameter update, a MIC, an FCS, or any combination thereof. In some embodiments, the type-specific management frame may correspond to a device type of STA 104-c. In some embodiments, the type-specific management frame may be communicated via a broadcast message or may be transmitted to a broadcast or group address. It should be noted that one or more fields or elements included or carried in the second message container may have a different format, different encoding, or different interpretation than the corresponding fields or elements included or carried in the first message container. For example, in some embodiments, the first message container may include: a second flow indicator having a different format, different encoding, or different interpretation than the first flow indicator; a second TSF having a different format, different encoding, or different interpretation than the first TSF; or both. It should be noted that some operations that are not applicable to certain fields, elements, or both in the first container (such as in legacy beacons) (for example, beacon protection) may be applied and / or be able to be applied to fields, elements, or both carried in some or all segments in the second container, because, for example, newer generations of non-AP STAs may support this feature and / or operation.

[0165] In some implementations, STA 104-c may receive one or more second message containers from AP 102-b according to a second periodicity. The second periodicity may be greater than the first periodicity, depending on the device type of STA 104-c. In some implementations, the group of one or more second message containers may include second message containers. Each second message container in the group of one or more second message containers may include a second set of one or more type-specific parameters. The second set of one or more type-specific parameters may correspond to the device type of STA 104-c. In some implementations, one or more messages may be communicated to the access point according to one or more common parameters and a second set of one or more type-specific parameters. In some implementations, at least one message container in the one or more second message containers includes an indication of which one or more type-specific segments are included in at least one message container.

[0166] At 1308, STA 104-c can communicate one or more messages with AP 102-b based on a first type-specific segment and a second type-specific segment.

[0167] Figure 14An example of a process flow 1400 supporting beacon extension design is shown. Process flow 1400 includes AP102-c and STA 104-d, which can be as relative to... Figure 1 and Figure 6 Examples of the corresponding devices described. In the following description of process flow 1400, the operations between AP 102-c and STA 104-d may be performed in a different order than the example order shown. Some operations may also be omitted from process flow 1400, and other operations may be added to process flow 1400. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously. Although these operations may be described as being performed between AP 102-c and STA 104-d, these operations may be performed between one or more STA 104, one or more AP 102, or any combination thereof.

[0168] At position 1402, STA 104-d receives a beacon frame from AP 102-c. The beacon frame can be as shown in the reference. Figure 7 An example of a beacon frame is described. For instance, a beacon frame may include one or more communication parameters for STA 104-d.

[0169] At 1404, STA 104-d can receive from AP 102-c a message extension container (such as a beacon extension container or a follow-up container) comprising one or more segments. The one or more segments may include a common segment with one or more common parameters and a set of one or more type-specific segments. Each type-specific segment in this set of one or more type-specific segments may include a corresponding set of one or more type-specific parameters corresponding to the corresponding device type among a variety of device types.

[0170] In some implementations, the message extension container may be an example of a PPDU that includes one or more beacon extension frames. In some implementations, the message extension container may be an example of a beacon extension frame. In some implementations, the message extension container may include one or more FCSs. Each segment in one or more segments may include a corresponding FCS among one or more FCSs. In some implementations, the message extension container may include one or more MICs. Each segment in one or more segments includes a corresponding MIC among multiple MICs.

[0171] At 1406, STA 104-d may communicate one or more messages with AP 102-c based on one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment. The first type-specific segment may come from one or more segments corresponding to the device type of STA 104-d. In some implementations, STA 104-d may communicate one or more messages with AP 102-c based on a second set of one or more type-specific parameters from one or more second type-specific segments in one or more segments. The one or more second type-specific segments may be based on the device type of the first wireless device.

[0172] Figure 15 A block diagram of an example wireless communication device 1500 supporting a beacon extension design is shown. In some specific implementations, the wireless communication device 1500 is configured to perform respective references. Figure 17 , Figure 18 and Figure 20 The processes described are 1700, 1800, and 2000. Wireless communication device 1500 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 wireless communication device 1500 and typically processes information (such as inputs or signals) received from and outputs information (such as outputs or signals) to such other components. In some aspects, an example chip may include a processing system, a first interface for outputting or transmitting information, and a second interface for receiving or acquiring information. For example, the first interface may refer to an interface between the chip's processing system and a transmitting component, enabling wireless communication device 1500 to transmit information output from the chip. In such examples, the second interface may refer to an interface between the chip's processing system and a receiving component, enabling wireless communication device 1500 to receive information, which is then passed to the processing system. In some such examples, the first interface may also, for example, acquire information from the transmitting component, and the second interface may also, for example, output information to the receiving component.

[0173] The processing system of the wireless communication device 1500 includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as a central processing unit (CPU), graphics processing unit (GPU), or digital signal processor (DSP)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuitry, each of which may include tangible storage media such as random access memory (RAM) or ROM or combinations thereof (all of which are generally referred to herein individually as “memory” or collectively as “memory” or “memory circuitry”). One or more of these memories may be coupled to one or more processors and may store processor-executable code, individually or collectively, which, when executed by one or more processors, configures one or more processors to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors may be pre-configured to perform the various functions or operations described herein without software configuration. The processing system may also include or be coupled to one or more modems (such as a Wi-Fi (e.g., IEEE compliant) modem or a cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modem). In some embodiments, one or more processors of the processing system include or implement one or more modems. The processing system may also include or be coupled to multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers.

[0174] In some specific implementations, the wireless communication device 1500 may be configured to be used for, or be configured to be used for, in a STA (such as reference STA). Figure 1The described STA 104 is used. In some other examples, the wireless communication device 1500 may be a STA that includes such a processing system and other components including multiple antennas. The wireless communication device 1500 is capable of transmitting and receiving wireless communications, for example, in the form of wireless packets. For example, the wireless communication device 1500 may be configured to or be configured to transmit and receive packets in the form of physical layer PPDUs and MPDUs conforming to one or more wireless communication protocol standards in the IEEE 802.11 family of wireless communication protocol standards. In some other examples, the wireless communication device 1500 may be configured to or be configured to transmit and receive signals and communications conforming to one or more 3GPP specifications, including specifications for 5G NR or 6G. In some implementations, the wireless communication device 1500 also includes one or more application processors or may be coupled to one or more application processors, which may also be coupled to one or more other memories. In some implementations, the wireless communication device 1500 also includes a user interface (UI) (such as a touchscreen or keypad) and a display that may be integrated with the UI to form a touchscreen display coupled to the processing system. In some implementations, the wireless communication device 1500 may also include one or more sensors, such as one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors coupled to the processing system.

[0175] The wireless communication device 1500 includes a first message container component 1525, a second message container component 1530, a message component 1535, a message extension container component 1540, and a parameter component 1545. A portion of one or more of the first message container component 1525, the second message container component 1530, the message component 1535, the message extension container component 1540, and the parameter component 1545 may be implemented at least partially in hardware or firmware. For example, one or more of the first message container component 1525, the second message container component 1530, the message component 1535, the message extension container component 1540, and the parameter component 1545 may be implemented at least partially by a processor or a modem. In some embodiments, a portion of one or more of the first message container component 1525, the second message container component 1530, the message component 1535, the message extension container component 1540, and the parameter component 1545 may be implemented at least partially by a processor and software in the form of processor-executable code stored in memory.

[0176] Wireless communication device 1500 can support wireless communication according to the examples disclosed herein. A first message container component 1525 can be configured or configured to receive from a second wireless device a first message container including one or more type-specific segments of a first set, wherein the first type-specific segment of the first set includes one or more type-specific parameters. A second message container component 1530 can be configured or configured to receive from the second wireless device a second message container including one or more type-specific segments of a second set, wherein both the first type-specific segment and the second type-specific segment of the second set correspond to a device type of the first wireless device. A message component 1535 can be configured or configured to communicate one or more messages to the second wireless device based on the first type-specific segment and the second type-specific segment.

[0177] In some embodiments, the first message container and the second message container are received via the main channel. In some embodiments, a single Physical Layer Protocol Data Unit (PPDU) includes the first message container and the second message container. In some embodiments, the first Physical Layer Protocol Data Unit (PPDU) includes the first message container and the second PPDU includes the second message container. In some embodiments, a first type-specific segment, a second type-specific segment, or both include information elements, fields, or both. In some embodiments, the first type-specific segment includes information for configuring the device type of the first wireless device and one or more generations of device types preceding that device type, and the second type-specific segment includes information for configuring the device type of the first wireless device.

[0178] In some implementations, the second type-specific segment indicates an update to at least one parameter in one or more type-specific parameters of the first group.

[0179] In some specific implementations, in order to support the reception of a first message container, the first message container component 1525 can be configured or configured to receive a first message container including an indication (such as an indication carried in a beacon frame or probe response frame) indicating that at least a first portion of a first set of one or more type-specific parameters is included in the first message container, at least a second portion of the first set of one or more type-specific parameters is included in a second message container, or both, wherein the indication is based on the device type of the first wireless device.

[0180] In some implementations, the first message container component 1525 can be configured or configured to receive a group of one or more first message containers according to a first periodicity. In some implementations, the second message container component 1530 can be configured or configured to receive a group of one or more second message containers according to a second periodicity, wherein the second periodicity is greater than the first periodicity.

[0181] In some embodiments, the first message container component 1525 can be configured or configured to receive a group of one or more first message containers according to a first periodicity, each of the group of one or more first message containers including one or more common parameters. In some embodiments, the second message container component 1530 can be configured or configured to receive a group of one or more second message containers according to a second periodicity, each of the group of one or more second message containers including a second group of one or more type-specific parameters, wherein the second group of one or more type-specific parameters corresponds to the device type of the first wireless device.

[0182] In some specific implementations, one or more messages are communicated to a second wireless device based on one or more common parameters and one or more type-specific parameters from a second set.

[0183] In some implementations, at least one message container in the group of one or more second message containers includes an indication of which one or more type-specific segments are included in at least one message container.

[0184] In some specific implementations, in order to support receiving a second message container, the second message container component 1530 can be configured or configured to receive a second message container comprising a set of multiple frame check sequences, wherein each segment in the second set of one or more type-specific segments comprises a corresponding frame check sequence in the set of multiple frame check sequences.

[0185] In some specific implementations, in order to support receiving a second message container, the second message container component 1530 can be configured or configured to receive a second message container including a set of multiple message integrity codes, wherein each segment in the second set of one or more type-specific segments includes a corresponding message integrity code of the set of multiple message integrity codes.

[0186] In some implementations, the second message container is a type-specific management frame that includes at least one of the following: a first traffic indicator, a first timing synchronization function, an indication of one or more supported device types, a type-specific parameter update, a message integrity code, a frame check sequence, or any combination thereof. In some implementations, the type-specific management frame corresponds to the device type of the first wireless device.

[0187] In some specific implementations, the first message container includes: a second flow indicator having a different format, encoding, or interpretation than the first flow indicator; a second timing synchronization function having a different format, encoding, or interpretation than the first timing synchronization function; or both.

[0188] In some implementations, at least one type-specific segment in the second group of one or more type-specific segments includes an indication of the length of at least one type-specific segment.

[0189] In some specific implementations, the first message container is a beacon frame, and the second message container is a beacon extension frame.

[0190] In some specific implementations, the first message container is a beacon extension frame, and the second message container is a beacon frame.

[0191] Additionally or alternatively, the wireless communication device 1500 may support wireless communication according to the examples disclosed herein. The message extension container component 1540 can be configured or configured to receive from the second wireless device a message extension container comprising one or more segments, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types. The parameter component 1545 can be configured or configured to communicate one or more messages to the second wireless device based on one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment of one or more segments corresponding to the device type of the first wireless device.

[0192] In some specific implementations, in order to support the transmission of one or more messages, parameter component 1545 can be configured or configured to transmit one or more messages to a second wireless device based on a second set of one or more type-specific parameters from one or more second type-specific segments in one or more segments, the one or more second type-specific segments being based on the device type of the first wireless device.

[0193] In some specific implementations, in order to support receiving message extension containers, message extension container component 1540 can be configured or configured to receive message extension containers comprising a set of multiple frame check sequences, wherein each of one or more segments comprises a corresponding frame check sequence in a set of multiple frame check sequences.

[0194] In some specific implementations, in order to support receiving message extension containers, message extension container component 1540 can be configured or configured to receive message extension containers that include a set of multiple message integrity codes, wherein each of one or more segments includes a corresponding message integrity code of the set of multiple message integrity codes.

[0195] In some specific implementations, a message extension container is a physical layer protocol data unit that includes a set of multiple beacon extension frames.

[0196] In some specific implementations, the message extension container is the beacon extension frame.

[0197] Figure 16 A block diagram of an example wireless communication device 1600 supporting a beacon extension design is shown. In some specific implementations, the wireless communication device 1600 is configured to perform respective references. Figure 19 and Figure 21 The processes described are 1900 and 2100. 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 wireless communication device 1600 and typically processes information (such as inputs or signals) received from and outputs information (such as outputs or signals) to such other components. In some aspects, an example chip may include a processing system, a first interface for outputting or transmitting information, and a second interface for receiving or acquiring information. For example, the first interface may refer to an interface between the chip's processing system and a transmitting component, enabling wireless communication device 1600 to transmit information output from the chip. In such examples, the second interface may refer to an interface between the chip's processing system and a receiving component, enabling wireless communication device 1600 to receive information, which is then passed to the processing system. In some such examples, the first interface may also, for example, acquire information from the transmitting component, and the second interface may also, for example, output information to the receiving component.

[0198] The processing system of the wireless communication device 1600 includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as a central processing unit (CPU), graphics processing unit (GPU), or digital signal processor (DSP)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuitry, each of which may include tangible storage media such as random access memory (RAM) or ROM or combinations thereof (all of which are generally referred to herein individually as “memory” or collectively as “memory” or “memory circuitry”). One or more of these memories may be coupled to one or more processors and may store processor-executable code, individually or collectively, which, when executed by one or more processors, configures one or more processors to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors may be pre-configured to perform the various functions or operations described herein without software configuration. The processing system may also include or be coupled to one or more modems (such as a Wi-Fi (e.g., IEEE compliant) modem or a cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modem). In some embodiments, one or more processors of the processing system include or implement one or more modems. The processing system may also include or be coupled to multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers.

[0199] In some specific implementations, the wireless communication device 1600 may be configured to be used for, or be configured to be used for, in an AP (such as a reference). Figure 1The described AP 102 is used. In some other examples, the wireless communication device 1600 may be an AP that includes such a processing system and other components including multiple antennas. The wireless communication device 1600 is capable of transmitting and receiving wireless communications, for example, in the form of wireless packets. For example, the wireless communication device 1600 may be configured or configured to transmit and receive packets in the form of physical layer PPDUs and MPDUs conforming to one or more wireless communication protocol standards in the IEEE 802.11 series of wireless communication protocol standards. In some other examples, the wireless communication device 1600 may be configured or configured to transmit and receive signals and communications conforming to one or more 3GPP specifications, including specifications for 5G NR or 6G. In some implementations, the wireless communication device 1600 also includes one or more application processors or may be coupled to one or more application processors, which may also be coupled to one or more other memories. In some implementations, the wireless communication device 1600 also includes at least one external network interface coupled to the processing system, which enables communication with the core network or backhaul network implementing the wireless communication device 1600 to obtain access to external networks, including the Internet.

[0200] The wireless communication device 1600 includes a first message container manager 1625, a second message container manager 1630, a message manager 1635, a message extension container manager 1640, and a parameter manager 1645. A portion of one or more of the first message container manager 1625, the second message container manager 1630, the message manager 1635, the message extension container manager 1640, and the parameter manager 1645 may be implemented at least partially in hardware or firmware. For example, one or more of the first message container manager 1625, the second message container manager 1630, the message manager 1635, the message extension container manager 1640, and the parameter manager 1645 may be implemented at least partially by a processor or a modem. In some embodiments, a portion of one or more of the first message container manager 1625, the second message container manager 1630, the message manager 1635, the message extension container manager 1640, and the parameter manager 1645 may be implemented at least partially by a processor and software in the form of processor-executable code stored in memory.

[0201] Wireless communication device 1600 can support wireless communication according to the examples disclosed herein. A first message container manager 1625 can be configured or configured to send a first message container comprising one or more type-specific segments of a first set, wherein the first type-specific segment of the first set includes one or more type-specific parameters. A second message container manager 1630 can be configured or configured to send a second message container comprising one or more type-specific segments of a second set, wherein both the first type-specific segment and the second type-specific segment of the second set correspond to a device type of the first wireless device. Message manager 1635 can be configured or configured to communicate one or more messages to the first wireless device based on the first and second type-specific segments.

[0202] In some implementations, the first message container and the second message container are transmitted via the main channel. In some implementations, a single Physical Layer Protocol Data Unit (PPDU) includes both the first and second message containers. In some implementations, the first PPDU includes the first message container and the second PPDU includes the second message container. In some implementations, a first type-specific segment, a second type-specific segment, or both include information elements, fields, or both. In some implementations, the first type-specific segment includes information for configuring the device type of the first wireless device and one or more generations of device types preceding that device type, and the second type-specific segment includes information for configuring the device type of the first wireless device.

[0203] In some implementations, the first message container manager 1625 can be configured to or be configured to send a group of one or more first message containers according to a first periodicity. In some implementations, the second message container manager 1630 can be configured to or be configured to send a group of one or more second message containers according to a second periodicity, wherein the second periodicity is greater than the first periodicity.

[0204] In some implementations, the first message container manager 1625 can be configured to or be configured to send a group of one or more first message containers according to a first periodicity, each of the group of one or more first message containers including one or more common parameters. In some implementations, the second message container manager 1630 can be configured to or be configured to send a group of one or more second message containers according to a second periodicity, each of the group of one or more second message containers including a second group of one or more type-specific parameters, wherein the second group of one or more type-specific parameters corresponds to the device type of the first wireless device.

[0205] In some implementations, at least the second message container includes an indication of which one or more type-specific segments are included in at least one message container.

[0206] In some implementations, at least one type-specific segment in the second group of one or more type-specific segments includes an indication of the length of at least one type-specific segment.

[0207] In some specific implementations, the first wireless device is a wireless station or a non-access point station, and the second wireless device is an access point.

[0208] Additionally or alternatively, the wireless communication device 1600 may support wireless communication according to the examples disclosed herein. The message extension container manager 1640 can be configured or configured to send a message extension container comprising one or more segments to the first wireless device, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types. The parameter manager 1645 can be configured or configured to communicate one or more messages to the first wireless device based on one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment of one or more segments corresponding to the device type of the first wireless device.

[0209] In some implementations, in order to support the communication of one or more messages, the parameter manager 1645 can be configured or configured to communicate one or more messages with a first wireless device based on a second set of one or more type-specific parameters from one or more second type-specific segments in one or more segments, the one or more second type-specific segments being based on the device type of the first wireless device.

[0210] In some specific implementations, in order to support the sending of message extension containers, the message extension container manager 1640 can be configured to or be configured to send message extension containers that include a set of multiple frame check sequences, wherein each of one or more segments includes a corresponding frame check sequence in a set of multiple frame check sequences.

[0211] In some specific implementations, in order to support receiving message extension containers, the message extension container manager 1640 can be configured to or be configured to send message extension containers that include a set of multiple message integrity codes, wherein each of one or more segments includes a corresponding message integrity code of the set of multiple message integrity codes.

[0212] Figure 17A flowchart illustrating an example process 1700 that can be performed by or at a first wireless device supporting a beacon extension design is shown. Operation of process 1700 can be implemented by a first wireless device or its components as described herein. For example, process 1700 can be performed by a wireless communication device operating as a wireless STA or within a wireless AP (such as reference 1700). Figure 15 The described wireless communication device 1500 performs this operation. In some specific implementations, process 1700 may be performed by a wireless STA (such as reference STA). Figure 1 The STA described in STA 104 is used to perform this action.

[0213] In some implementations, in block 1705, a first wireless device may receive from a second wireless device a first message container comprising one or more type-specific segments in a first set of one or more type-specific segments, the first type-specific segment in the first set of one or more type-specific segments including one or more type-specific parameters. Operation of block 1705 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1705 may be provided by reference to [reference needed]. Figure 15 The first message container component 1525, as described, is used for execution.

[0214] In some implementations, in block 1710, a first wireless device may receive from a second wireless device a second message container comprising one or more second type-specific segments, wherein both the first type-specific segment and the second type-specific segment in the second or more second group of type-specific segments correspond to the device type of the first wireless device. Operation of block 1710 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1710 may be provided by reference to [reference needed]. Figure 15 The second message container component 1530, as described, is used for execution.

[0215] In some implementations, in block 1715, the first wireless device may communicate one or more messages to the second wireless device based on a first type-specific segment and a second type-specific segment. Operation of block 1715 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1715 may be provided by reference to [reference needed]. Figure 15 The message component 1535 described is used for execution.

[0216] Figure 18 A flowchart illustrating an example process 1800 that can be performed by or at a first wireless device supporting a beacon extension design is shown. Operation of process 1800 can be implemented by a first wireless device or its components as described herein. For example, process 1800 can be performed by a wireless communication device operating as a wireless STA or within a wireless AP (such as reference 1800). Figure 15The described wireless communication device 1500 performs the procedure. In some specific implementations, the process 1800 may be performed by a wireless STA (such as reference STA). Figure 1 The STA described in STA 104 is used to perform this action.

[0217] In some implementations, in block 1805, a first wireless device may receive from a second wireless device a first message container comprising one or more type-specific segments in a first set of one or more type-specific segments, the first type-specific segment in the first set of one or more type-specific segments including one or more type-specific parameters. Operation of block 1805 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1805 may be provided by reference to [reference needed]. Figure 15 The first message container component 1525, as described, is used for execution.

[0218] In some implementations, in block 1810, the first wireless device may periodically receive a set of one or more first message containers, each of which includes one or more common parameters. Operation of block 1810 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1810 may be provided by reference to [reference needed]. Figure 15 The first message container component 1525, as described, is used for execution.

[0219] In some implementations, in block 1815, the first wireless device may receive from the second wireless device a second message container comprising one or more second type-specific segments, wherein both the first type-specific segment and the second type-specific segment in the second or more second group of type-specific segments correspond to the device type of the first wireless device. Operation of block 1815 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1815 may be provided by reference to [reference needed]. Figure 15 The second message container component 1530, as described, is used for execution.

[0220] In some implementations, in block 1820, the first wireless device may periodically receive one or more sets of second message containers, each set of one or more second message containers including one or more second sets of type-specific parameters, wherein the second set of one or more type-specific parameters corresponds to the device type of the first wireless device. Operation of block 1820 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1820 may be provided by reference to [reference needed]. Figure 15 The second message container component 1530, as described, is used for execution.

[0221] In some implementations, in block 1825, the first wireless device may communicate one or more messages to the second wireless device based on a first type-specific segment and a second type-specific segment. Operation of block 1825 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1825 may be provided by reference to [reference needed]. Figure 15 The message component 1535 described is used for execution.

[0222] Figure 19 A flowchart illustrating an example process 1900 that can be performed by or at a second wireless device supporting a beacon extension design is shown. Operation of process 1900 can be implemented by a second wireless device or its components as described herein. For example, process 1900 can be performed by a wireless communication device (such as reference 1900) operating as a wireless access point (AP) or within a wireless AP. Figure 16 The described wireless communication device 1600 performs this process. In some specific implementations, process 1900 may be performed by a wireless AP (such as reference 1600). Figure 1 The AP described in AP 102 is used to perform this action.

[0223] In some implementations, in block 1905, the second wireless device may transmit a first message container comprising one or more first group type-specific segments to the first wireless device, wherein the first type-specific segment in the first group of one or more type-specific segments includes one or more first group type-specific parameters. Operation of block 1905 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1905 may be provided by reference to [reference needed]. Figure 16 The first message container manager 1625 described is used for execution.

[0224] In some implementations, in block 1910, the second wireless device may send a second message container comprising one or more second group of type-specific segments to the first wireless device, wherein both the first type-specific segment and the second type-specific segment in the second group of one or more type-specific segments correspond to the device type of the first wireless device. Operation of block 1910 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1910 may be provided by reference to [reference needed]. Figure 16 The second message container manager 1630 described is used for execution.

[0225] In some implementations, in block 1915, the second wireless device may communicate one or more messages to the first wireless device based on a first type-specific segment and a second type-specific segment. Operation of block 1915 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 1915 may be provided by reference to [reference needed]. Figure 16 The described message manager 1635 is executed.

[0226] Figure 20 A flowchart illustrating an example process 2000 that can be executed by or at a first wireless device supporting a beacon extension design is shown. Operation of process 2000 can be implemented by a first wireless device or its components as described herein. For example, process 2000 can be implemented by a wireless communication device operating as a wireless STA or within a wireless AP (such as reference 1). Figure 15 The described wireless communication device 1500 performs the process. In some specific implementations, process 2000 may be performed by a wireless STA (such as reference STA). Figure 1 The STA described in STA 104 is used to perform this action.

[0227] In some implementations, in block 2005, a first wireless device may receive from a second wireless device a message extension container comprising one or more segments, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type in a set of multiple device types. Operation of block 2005 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 2005 may be provided by reference to [reference needed]. Figure 15 The message extension container component 1540 described is used for execution.

[0228] In some implementations, in block 2010, the first wireless device may communicate one or more messages to the second wireless device based on one or more common parameters and one or more type-specific parameters from one or more segments corresponding to the device type of the first wireless device in a first type-specific segment. Operation of block 2010 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 2010 may be provided by reference to [reference needed]. Figure 15 The parameter component 1545 described is used for execution.

[0229] Figure 21 A flowchart illustrating an example process 2100 that can be performed by or at a second wireless device supporting a beacon extension design is shown. Operation of process 2100 can be implemented by a second wireless device or its components as described herein. For example, process 2100 can be performed by a wireless communication device (such as reference 2100) operating as a wireless access point (AP) or within a wireless AP. Figure 16 The described wireless communication device 1600) performs the procedure. In some specific implementations, the process 2100 may be performed by a wireless AP (such as reference 1600). Figure 1 The AP described in AP 102 is used to perform this action.

[0230] In some implementations, in block 2105, the second wireless device may send a message extension container comprising one or more segments to the first wireless device. The one or more segments include a common segment having one or more common parameters and a set of one or more type-specific segments, each of which includes a corresponding set of one or more type-specific parameters corresponding to a corresponding device type from a set of multiple device types. Operation of block 2105 may be performed according to the examples disclosed herein. In some implementations, aspects of operation of block 2105 may be provided by reference to [reference needed]. Figure 16 The described message extension container manager 1640 is used for execution.

[0231] In some implementations, in block 2110, the second wireless device may communicate one or more messages to the first wireless device based on one or more common parameters and a first set of one or more type-specific parameters from one or more segments corresponding to the device type of the first wireless device. The operation of block 2110 may be performed according to the examples disclosed herein. In some implementations, aspects of the operation of block 2110 may be provided by reference to [reference needed]. Figure 16 The parameter manager 1645 described is used for execution.

[0232] Specific implementation examples are described in the following numbered clauses:

[0233] Aspect 1: A method for wireless communication at a first wireless device, the method comprising: receiving from a second wireless device a first message container including one or more type-specific segments of a first set, the first type-specific segment of the first set including one or more type-specific parameters; receiving from the second wireless device a second message container including one or more type-specific segments of a second set, wherein both the first type-specific segment and the second type-specific segment of the second set correspond to a device type of the first wireless device; and communicating one or more messages to the second wireless device based on the first type-specific segment and the second type-specific segment.

[0234] Aspect 2: According to the method of aspect 1, wherein the first message container and the second message container are received via the main channel.

[0235] Aspect 3: The method according to any one of Aspects 1 to 2, wherein a single physical layer protocol data unit (PPDU) includes the first message container and the second message container.

[0236] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the first physical layer protocol data unit (PPDU) includes the first message container and the second PPDU includes the second message container.

[0237] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the first type-specific segment includes information for configuring the device type of the first wireless device and one or more generations of device types preceding the device type, and the second type-specific segment includes information for configuring the device type of the first wireless device.

[0238] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the second type-specific segment indicates an update of at least one parameter in the first group of one or more type-specific parameters.

[0239] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the first type-specific segment, the second type-specific segment, or both comprise an information element, a field, or both.

[0240] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the second group of one or more type-specific segments included in the second message container includes type-specific segments having values ​​that have changed since the first message container was received.

[0241] Aspect 9: The method according to any one of Aspects 1 to 8, wherein receiving the first message container further comprises: receiving the first message container including an indication that at least a first portion of the first group of one or more type-specific parameters is included in the first message container, at least a second portion of the first group of one or more type-specific parameters is included in the second message container, or both, wherein the indication is at least partially based on the device type of the first wireless device.

[0242] Aspect 10: The method according to any one of aspects 1 to 9, the method further comprising: receiving one or more first message containers according to a first periodicity; and receiving one or more second message containers according to a second periodicity, wherein the second periodicity is greater than the first periodicity.

[0243] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: periodically receiving one or more first message containers according to a first periodicity, each of the one or more first message containers including one or more common parameters; and periodically receiving one or more second message containers according to a second periodicity, each of the one or more second message containers including a second set of one or more type-specific parameters, wherein the second set of one or more type-specific parameters corresponds to the device type of the first wireless device.

[0244] Aspect 12: The method according to any one of aspects 1 to 11, wherein the one or more messages are communicated to the second wireless device according to one or more common parameters and the second set of one or more type-specific parameters.

[0245] Aspect 13: The method according to any one of aspects 1 to 12, wherein the second message container includes an indication of which one or more type-specific segments are included in the at least one message container.

[0246] Aspect 14: The method according to any one of Aspects 1 to 13, wherein receiving the second message container further comprises: receiving the second message container comprising a plurality of frame check sequences, wherein each segment in the second group of one or more type-specific segments comprises a corresponding frame check sequence in the plurality of frame check sequences. In some specific embodiments, each corresponding frame check sequence is used to verify one or more previous segments in the second group of one or more type-specific segments.

[0247] Aspect 15: The method according to any one of Aspects 1 to 14, wherein receiving the second message container further comprises: receiving the second message container including a plurality of message integrity codes, wherein each segment in the second group of one or more type-specific segments includes a corresponding message integrity code among the plurality of message integrity codes. In some specific embodiments, each corresponding message integrity code is used to verify one or more previous segments in the second group of one or more type-specific segments, and wherein each corresponding message integrity code corresponds to a first set of security parameters, the first set of security parameters being stronger than a second set of security parameters for the message integrity codes of one or more shared segments.

[0248] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the second message container is a type-specific management frame, the type-specific management frame comprising at least one of the following: a first traffic indicator, a first timing synchronization function, an indication of one or more supported device types, a type-specific parameter update, a message integrity code, a frame check sequence, or any combination thereof, the type-specific management frame corresponding to the device type of the first wireless device.

[0249] Aspect 17: According to the method of aspect 16, the first message container includes: a second flow indicator having a different format, different encoding, or different interpretation than the first flow indicator; a second timing synchronization function having a different format, different encoding, or different interpretation than the first timing synchronization function; or both. In some specific implementations, at least one operation that is not applicable to one or more fields, elements, or both in the first message container is applicable to one or more fields, elements, or both in the second message container.

[0250] Aspect 18: The method according to any one of aspects 1 to 17, wherein at least one type-specific segment in the second group of one or more type-specific segments includes an indication of the length of the at least one type-specific segment.

[0251] Aspect 19: The method according to any one of Aspects 1 to 18, wherein the first message container is a beacon frame and the second message container is a beacon extended frame.

[0252] Aspect 20: The method according to any one of Aspects 1 to 19, wherein the first message container is a beacon extended frame and the second message container is a beacon frame.

[0253] Aspect 21: A method for wireless communication at a second wireless device, the method comprising: transmitting a first message container comprising one or more type-specific segments of a first set, the first type-specific segment of the first set of one or more type-specific segments comprising one or more type-specific parameters; transmitting a second message container comprising one or more type-specific segments of a second set, wherein both the first type-specific segment and the second type-specific segment of the second set of one or more type-specific segments correspond to a device type of the first wireless device; and communicating one or more messages with the first wireless device based on the first type-specific segment and the second type-specific segment.

[0254] Aspect 22: According to the method of aspect 21, wherein the first message container and the second message container are received via a main channel.

[0255] Aspect 23: The method according to any one of Aspects 21 to 22, wherein a single physical layer protocol data unit (PPDU) includes the first message container and the second message container.

[0256] Aspect 24: The method according to any one of Aspects 21 to 23, wherein the first physical layer protocol data unit (PPDU) includes the first message container and the second PPDU includes the second message container.

[0257] Aspect 25: The method according to any one of Aspects 21 to 24, wherein the first type-specific segment includes information for configuring the device type of the first wireless device and one or more generations of device types preceding the device type, and the second type-specific segment includes information for configuring the device type of the first wireless device.

[0258] Aspect 26: The method according to any one of aspects 21 to 25, wherein the second type-specific segment indicates an update of at least one parameter in the first group of one or more type-specific parameters.

[0259] Aspect 27: The method according to any one of Aspects 21 to 26, wherein the first type-specific segment, the second type-specific segment, or both comprise an information element, a field, or both.

[0260] Aspect 28: The method according to any one of aspects 21 to 27, wherein the second group of one or more type-specific segments included in the second message container includes type-specific segments having values ​​that have changed since the first message container was sent.

[0261] Aspect 29: The method according to any one of aspects 21 to 28, the method further comprising: sending one or more first message containers according to a first periodicity; and sending one or more second message containers according to a second periodicity, wherein the second periodicity is greater than the first periodicity.

[0262] Aspect 30: The method according to any one of Aspects 21 to 29, the method further comprising: periodically transmitting one or more first message containers according to a first periodicity, each of the one or more first message containers including one or more common parameters; and periodically transmitting one or more second message containers according to a second periodicity, each of the one or more second message containers including a second set of one or more type-specific parameters, wherein the second set of one or more type-specific parameters corresponds to the device type of the first wireless device.

[0263] Aspect 31: According to the method of aspect 30, at least one message container in the one or more second message containers includes an indication of which one or more type-specific segments are included in the at least one message container. In some examples, at least one type-specific segment in the second set of one or more type-specific segments includes a bitmap indicating a set of device types supported by the second wireless device.

[0264] Aspect 32: The method according to any one of aspects 21 to 31, wherein at least one type-specific segment in the second group of one or more type-specific segments includes an indication of the length of the at least one type-specific segment.

[0265] Aspect 33: The method according to any one of Aspects 21 to 32, wherein the first wireless device is a wireless station or a non-access point station, and wherein the second wireless device is an access point.

[0266] Aspect 34: A method for wireless communication at a first wireless device, the method comprising: receiving from a second wireless device a message extension container comprising one or more segments, the one or more segments comprising a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments comprising a corresponding set of one or more type-specific parameters corresponding to a corresponding device type among a plurality of device types; and communicating one or more messages to the second wireless device based on the one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment of the one or more segments corresponding to a device type of the first wireless device.

[0267] Aspect 35: The method according to aspect 34, wherein conveying the one or more messages further comprises: conveying the one or more messages to the access point based on a second set of one or more type-specific parameters from one or more second type-specific segments of the one or more segments, the one or more second type-specific segments being at least partially based on the device type of the first wireless device.

[0268] Aspect 36: The method according to any one of Aspects 34 to 35, wherein receiving the message extension container further comprises: receiving the message extension container comprising a plurality of frame check sequences, wherein each of the one or more segments comprises a corresponding frame check sequence among the plurality of frame check sequences.

[0269] Aspect 37: The method according to any one of Aspects 34 to 36, wherein receiving the message extension container further comprises: receiving the message extension container including a plurality of message integrity codes, wherein each of the one or more segments includes a corresponding message integrity code among the plurality of message integrity codes.

[0270] Aspect 38: The method according to any one of Aspects 34 to 37, wherein the message extension container is a physical layer protocol data unit comprising a plurality of beacon extension frames.

[0271] Aspect 39: The method according to any one of aspects 34 to 38, wherein the message extension container is a beacon extension frame.

[0272] Aspect 40: A method for wireless communication at a second wireless device, the method comprising: transmitting a message extension container comprising one or more segments to a first wireless device, the one or more segments comprising a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments comprising a corresponding set of one or more type-specific parameters corresponding to a corresponding device type among a plurality of device types; and communicating one or more messages to the first wireless device based on the one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment of the one or more segments corresponding to a device type of the first wireless device.

[0273] Aspect 41: The method according to aspect 40, wherein conveying the one or more messages further comprises: conveying the one or more messages to the first wireless device based on a second set of one or more type-specific parameters from one or more second type-specific segments of the one or more segments, the one or more second type-specific segments being at least partially based on the device type of the first wireless device.

[0274] Aspect 42: The method according to any one of Aspects 40 to 41, wherein sending the message extension container further comprises: sending the message extension container comprising a plurality of frame check sequences, wherein each of the one or more segments comprises a corresponding frame check sequence among the plurality of frame check sequences.

[0275] Aspect 43: The method according to any one of aspects 40 to 42, wherein receiving the message extension container further comprises: sending the message extension container including a plurality of message integrity codes, wherein each of the one or more segments includes a corresponding message integrity code among the plurality of message integrity codes.

[0276] Aspect 44: A first wireless device for wireless communication, the first wireless device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the first wireless device to perform the method according to any one of aspects 1 to 20.

[0277] Aspect 45: A first wireless device for wireless communication, the first wireless device comprising at least one component for performing the method according to any one of aspects 1 to 20.

[0278] Aspect 46: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 20.

[0279] Aspect 47: A method for wireless communication, the method comprising causing a first wireless device to perform the method according to any one of aspects 1 to 20.

[0280] Aspect 48: A second wireless device for wireless communication, the second wireless device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the second wireless device to perform the method according to any one of aspects 21 to 33.

[0281] Aspect 49: A second wireless device for wireless communication, the second wireless device comprising at least one component for performing the method according to any one of aspects 21 to 33.

[0282] Aspect 50: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform a method according to any one of aspects 21 to 33.

[0283] Aspect 51: A method for wireless communication, the method comprising causing a first wireless device to perform the method according to any one of aspects 21 to 33.

[0284] Aspect 52: A first wireless device for wireless communication, the first wireless device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the first wireless device to perform a method according to any one of aspects 34 to 39.

[0285] Aspect 53: A first wireless device for wireless communication, the first wireless device comprising at least one component for performing the method according to any one of aspects 34 to 39.

[0286] Aspect 54: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform a method according to any one of aspects 34 to 39.

[0287] Aspect 55: A method for wireless communication, the method comprising causing a first wireless device to perform the method according to any one of aspects 34 to 39.

[0288] Aspect 56: A second wireless device for wireless communication, the second wireless device comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, thereby enabling the second wireless device to perform the method according to any one of aspects 40 to 43.

[0289] Aspect 57: A second wireless device for wireless communication, the second wireless device comprising at least one component for performing the method according to any one of aspects 40 to 43.

[0290] Aspect 58: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform a method according to any one of aspects 40 to 43.

[0291] Aspect 47: A method for wireless communication, the method comprising causing a first wireless device to perform the method according to any one of aspects 40 to 43.

[0292] As used herein, the term "determine" encompasses a wide variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, estimation, investigation, searching (such as by searching in a table, database, or other data structure), reasoning, probing, or measurement, among other possibilities. Furthermore, "determine" can include receiving (such as receiving information), accessing (such as accessing data stored in memory), or sending (such as sending information), among other possibilities. Additionally, "determine" can include parsing, selecting, obtaining, choosing, building, and other similar actions.

[0293] As used herein, the phrase “at least one of” or “one or more of” refers to any combination of these items, including a single member. For example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc. As used herein, “or” is intended to be interpreted in an inclusive sense unless otherwise expressly indicated. For example, “a or b” may include only a, only b, or a combination of a and b. Furthermore, as used herein, the phrase referring to “one” element means one or more of such elements that act individually or collectively to perform the stated function. Additionally, “set” means one or more items, and “subset” means less than the entire set, but not empty.

[0294] As used herein, unless otherwise expressly indicated, “based on” is intended to be interpreted in an inclusive sense. For example, unless otherwise explicitly indicated, “based on” may be used interchangeably with “at least partially based on,” “associated with,” “associated with,” or “according to.” Specifically, unless the phrase in the context means “based on only one” or an equivalent, whether it is “based on one” or “at least partially based on one”, it may be based solely on “one” or based on a combination of “one” and one or more other factors, conditions, or information.

[0295] The various exemplary components, logic units, logic blocks, modules, circuits, operations, and algorithmic processes described in conjunction with the examples disclosed herein can be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed in this specification and their structural equivalents. This interchangeability of hardware, firmware, and software has been generally described in terms of its functionality and exemplified in the various exemplary components, blocks, modules, circuits, and processes described above. Whether this functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.

[0296] Various modifications to the examples described herein will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the examples shown herein, but are to be granted the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0297] Additionally, the various features described in this specification in the context of individual examples may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple examples. Thus, although features may be described above as functioning in a particular combination, and even initially claimed in this way, one or more features from the claimed combination may be removed from the combination in some embodiments, and the claimed combination may be for sub-combinations or variations thereof.

[0298] Similarly, although operations are depicted in a specific order in the diagrams, this should not be construed as requiring such operations to be performed in the specific order shown or in sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the accompanying figures may schematically depict one or more example processes in the form of flowcharts or flow diagrams. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some environments, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the examples described above should not be construed as requiring such separation in all examples, but rather should be understood as meaning that the described program components and systems can generally be integrated together in a single software product or encapsulated in multiple software products.

Claims

1. A first wireless device, the first wireless device comprising: The processing system, including processor circuitry and memory circuitry for storing code, is configured to cause the first wireless device to: Receive a first message container from a second wireless device, which includes one or more type-specific segments in a first group, wherein the first type-specific segment in the first group of one or more type-specific segments includes one or more type-specific parameters. Receive a second message container from the second wireless device, comprising one or more type-specific segments from a second set of segments, wherein both the first type-specific segment and the second type-specific segment from the second set of segments correspond to the device type of the first wireless device; and One or more messages are communicated to the second wireless device based on the first type-specific segment and the second type-specific segment.

2. The first wireless device according to claim 1, wherein the first message container and the second message container are received via a main channel.

3. The first wireless device according to claim 1, wherein a single physical layer protocol data unit (PPDU) includes the first message container and the second message container.

4. The first wireless device according to claim 1, wherein the first physical layer protocol data unit (PPDU) includes the first message container and the second PPDU includes the second message container.

5. The first wireless device of claim 1, wherein the first type-specific segment includes information for configuring the device type of the first wireless device and one or more generations of device types preceding the device type, and wherein the second type-specific segment includes information for configuring the device type of the first wireless device.

6. The first wireless device of claim 1, wherein the second type-specific segment indicates an update of at least one parameter in the first group of one or more type-specific parameters.

7. The first wireless device according to claim 1, wherein the first type-specific segment, the second type-specific segment, or both comprise information elements, fields, or both.

8. The first wireless device of claim 1, wherein the second group of one or more type-specific segments included in the second message container includes type-specific segments having values ​​that have changed since the first message container was received.

9. The first wireless device according to claim 1, wherein, In order to receive the first message container, the processing system is further configured to cause the first wireless device to: The first message container is received including an indication that at least a first portion of one or more type-specific parameters of the first group are included in the first message container, at least a second portion of one or more type-specific parameters of the first group are included in the second message container, or both, wherein the indication is at least partially based on the device type of the first wireless device.

10. The first wireless device of claim 1, wherein the processing system is further configured to cause the first wireless device to: According to the first periodic reception of one or more first message containers; and One or more second message containers are received according to a second periodicity, wherein the second periodicity is greater than the first periodicity.

11. The first wireless device of claim 1, wherein the processing system is further configured to cause the first wireless device to: According to the first periodic reception of one or more first message containers, each of the one or more first message containers includes one or more common parameters; and According to the second periodic reception of one or more second message containers, each of the one or more second message containers includes a second set of one or more type-specific parameters, wherein the second set of one or more type-specific parameters corresponds to the device type of the first wireless device.

12. The first wireless device of claim 1, wherein the one or more messages are communicated to the second wireless device based on one or more common parameters and the second set of one or more type-specific segments.

13. The first wireless device of claim 1, wherein at least the second message container includes an indication of which one or more type-specific segments are included in the first message container.

14. The first wireless device according to claim 1, wherein, In order to receive the second message container, the processing system is further configured to cause the first wireless device to: Receive a second message container comprising a plurality of frame check sequences, wherein each segment in one or more type-specific segments of the second group comprises a corresponding frame check sequence in the plurality of frame check sequences.

15. The first wireless device according to claim 1, wherein, In order to receive the second message container, the processing system is further configured to cause the first wireless device to: Receive a second message container comprising a plurality of message integrity codes, wherein each segment in one or more type-specific segments of the second group comprises a corresponding message integrity code among the plurality of message integrity codes.

16. The first wireless device according to claim 1, wherein: The second message container is a type-specific management frame, which includes at least one of the following: a first traffic indicator, a first timing synchronization function, an indication of one or more supported device types, a type-specific parameter update, a message integrity code, a frame check sequence, or any combination thereof, wherein the type-specific management frame corresponds to the device type of the first wireless device.

17. The first wireless device of claim 16, wherein the first message container comprises: A second flow indicator, which has a different format, different encoding, or different interpretation than the first flow indicator; The second timing synchronization function has a different format, different encoding, or different interpretation than the first timing synchronization function; or both.

18. The first wireless device of claim 1, wherein at least one type-specific segment in the second group of one or more type-specific segments includes an indication of the length of the at least one type-specific segment.

19. The first wireless device of claim 1, wherein the first message container is a beacon frame, and the second message container is one of a beacon extension frame, a probe response frame, or a management frame.

20. The first wireless device of claim 1, wherein the first message container is one of a beacon extension frame, a probe response frame, or a management frame, and the second message container is a beacon frame.

21. A second wireless device, the second wireless device comprising: The processing system, including processor circuitry and memory circuitry for storing code, is configured to cause the second wireless device to: A first message container comprising one or more type-specific segments of a first group is sent to a first wireless device, wherein the first type-specific segment of the first group of one or more type-specific segments comprises one or more type-specific parameters of the first group; A second message container comprising one or more type-specific segments in a second group is sent to the first wireless device, wherein both the first type-specific segment and the second type-specific segment in the second group of one or more type-specific segments correspond to the device type of the first wireless device; and One or more messages are communicated to the first wireless device based on the first type-specific segment and the second type-specific segment.

22. The second wireless device of claim 21, wherein the first message container and the second message container are transmitted via a main channel.

23. The second wireless device of claim 21, wherein a single physical layer protocol data unit (PPDU) includes the first message container and the second message container.

24. The second wireless device of claim 21, wherein the first physical layer protocol data unit (PPDU) includes the first message container and the second PPDU includes the second message container.

25. The second wireless device of claim 21, wherein the first type-specific segment includes information for configuring the device type of the first wireless device and one or more generations of device types preceding the device type, and wherein the second type-specific segment includes information for configuring the device type of the first wireless device.

26. The second wireless device of claim 21, wherein the second type-specific segment indicates an update of at least one parameter of the first group of one or more type-specific parameters.

27. The second wireless device of claim 21, wherein the first type-specific segment, the second type-specific segment, or both comprise information elements, fields, or both.

28. The second wireless device of claim 21, wherein the second group of one or more type-specific segments included in the second message container includes type-specific segments having values ​​that have changed since the first message container was sent.

29. The second wireless device of claim 21, wherein the processing system is further configured to cause the second wireless device to: According to the first periodic sending of one or more first message containers; and One or more second message containers are sent according to a second periodicity, wherein the second periodicity is greater than the first periodicity.

30. The second wireless device of claim 21, wherein the processing system is further configured to cause the second wireless device to: According to a first periodic transmission of one or more first message containers, each of the one or more first message containers includes one or more common parameters; and According to the second periodic transmission of one or more second message containers, each of the one or more second message containers includes a second set of one or more type-specific parameters, wherein the second set of one or more type-specific parameters corresponds to the device type of the first wireless device.

31. The second wireless device of claim 30, wherein at least one of the one or more second message containers includes an indication of which one or more type-specific segments are included in the at least one message container.

32. The second wireless device of claim 21, wherein at least one type-specific segment in the second group of one or more type-specific segments includes an indication of the length of the at least one type-specific segment.

33. The second wireless device according to claim 21, wherein the first wireless device is a wireless station or a non-access point station, and the second wireless device is an access point.

34. A first wireless device, the first wireless device comprising: The processing system, including processor circuitry and memory circuitry for storing code, is configured to cause the first wireless device to: Receive a message extension container from a second wireless device, comprising one or more segments, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type among a variety of device types; as well as One or more messages are communicated to the second wireless device based on the one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment corresponding to the device type of the first wireless device in the one or more segments.

35. The first wireless device according to claim 34, wherein, In order to convey the one or more messages, the processing system is further configured to cause the first wireless device to: The one or more messages are communicated to the second wireless device based on a second set of one or more type-specific parameters from one or more second type-specific segments of the one or more segments, wherein the one or more second type-specific segments are at least partially based on the device type of the first wireless device.

36. The first wireless device according to claim 34, wherein, In order to receive the message extension container, the processing system is also configured to enable the first wireless device to: Receive the message extension container comprising a plurality of frame check sequences, wherein each of the one or more segments comprises a corresponding frame check sequence among the plurality of frame check sequences.

37. The first wireless device according to claim 34, wherein, In order to receive the message extension container, the processing system is also configured to enable the first wireless device to: Receive the message extension container including a plurality of message integrity codes, wherein each of the one or more segments includes a corresponding message integrity code among the plurality of message integrity codes.

38. The first wireless device of claim 34, wherein the message extension container is a physical layer protocol data unit comprising a plurality of beacon extension frames.

39. The first wireless device of claim 34, wherein the message extension container is one of a beacon extension frame, a probe response frame, or a management frame.

40. A second wireless device, the second wireless device comprising: The processing system, including processor circuitry and memory circuitry for storing code, is configured to cause the second wireless device to: A message extension container comprising one or more segments is sent to a first wireless device, the one or more segments comprising a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments comprising a corresponding set of one or more type-specific parameters corresponding to a corresponding device type among a plurality of device types; as well as One or more messages are communicated to the first wireless device based on one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment corresponding to the device type of the first wireless device in one or more segments.

41. The second wireless device according to claim 40, wherein, In order to convey the one or more messages, the processing system is further configured to cause the second wireless device to: The one or more messages are communicated to the first wireless device based on a second set of one or more type-specific parameters from one or more second type-specific segments, wherein the one or more second type-specific segments are at least partially based on the device type of the first wireless device.

42. The second wireless device according to claim 40, wherein, In order to send the message extension container, the processing system is also configured to enable the second wireless device to: Send the message extension container comprising a plurality of frame check sequences, wherein each of the one or more segments comprises a corresponding frame check sequence among the plurality of frame check sequences.

43. The second wireless device according to claim 40, wherein, In order to receive the message extension container, the processing system is also configured to enable the second wireless device to: Send the message extension container that includes multiple message integrity codes, wherein each of the one or more segments includes a corresponding message integrity code among the multiple message integrity codes.

44. A method for performing wireless communication at a first wireless device, the method comprising: Receive a first message container from a second wireless device, which includes one or more type-specific segments in a first group, wherein the first type-specific segment in the first group of one or more type-specific segments includes one or more type-specific parameters. Receive a second message container from the second wireless device, comprising one or more type-specific segments from a second set of segments, wherein both the first type-specific segment and the second type-specific segment from the second set of segments correspond to the device type of the first wireless device; and One or more messages are communicated to the second wireless device based on the first type-specific segment and the second type-specific segment.

45. The method of claim 44, wherein the first message container and the second message container are received via a main channel.

46. ​​The method of claim 44, wherein a single physical layer protocol data unit (PPDU) includes the first message container and the second message container.

47. The method of claim 44, wherein the first physical layer protocol data unit (PPDU) includes the first message container and the second PPDU includes the second message container.

48. The method of claim 44, wherein the first type-specific segment, the second type-specific segment, or both comprise an information element, a field, or both.

49. A method for performing wireless communication at a second wireless device, the method comprising: A first message container comprising one or more type-specific segments of a first group is sent to a first wireless device, wherein the first type-specific segment of the first group of one or more type-specific segments comprises one or more type-specific parameters of the first group; A second message container comprising one or more type-specific segments in a second group is sent to the first wireless device, wherein both the first type-specific segment and the second type-specific segment in the second group of one or more type-specific segments correspond to the device type of the first wireless device; and One or more messages are communicated to the first wireless device based on the first type-specific segment and the second type-specific segment.

50. The method of claim 49, wherein the first message container and the second message container are transmitted via a main channel.

51. The method of claim 49, wherein a single physical layer protocol data unit (PPDU) includes the first message container and the second message container.

52. The method of claim 49, wherein the first physical protocol data unit (PPDU) includes the first message container and the second PPDU includes the second message container.

53. The method of claim 49, wherein the first type-specific segment, the second type-specific segment, or both comprise an information element, a field, or both.

54. A method for performing wireless communication at a first wireless device, the method comprising: Receive a message extension container from a second wireless device, comprising one or more segments, the one or more segments including a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments including a corresponding set of one or more type-specific parameters corresponding to a corresponding device type among a variety of device types; as well as One or more messages are communicated to the second wireless device based on the one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment corresponding to the device type of the first wireless device in the one or more segments.

55. The method of claim 54, wherein conveying the one or more messages further comprises: The one or more messages are communicated to the second wireless device based on a second set of one or more type-specific parameters from one or more second type-specific segments of the one or more segments, wherein the one or more second type-specific segments are at least partially based on the device type of the first wireless device.

56. The method of claim 54, wherein receiving the message extension container further comprises: Receive the message extension container comprising a plurality of frame check sequences, wherein each of the one or more segments comprises a corresponding frame check sequence among the plurality of frame check sequences.

57. The method of claim 54, wherein receiving the message extension container further comprises: Receive the message extension container including a plurality of message integrity codes, wherein each of the one or more segments includes a corresponding message integrity code among the plurality of message integrity codes.

58. A method for performing wireless communication at a second wireless device, the method comprising: A message extension container comprising one or more segments is sent to a first wireless device, the one or more segments comprising a common segment having one or more common parameters and a set of one or more type-specific segments, each of the set of one or more type-specific segments comprising a corresponding set of one or more type-specific parameters corresponding to a corresponding device type among a plurality of device types; as well as One or more messages are communicated to the first wireless device based on one or more common parameters and a first set of one or more type-specific parameters from a first type-specific segment corresponding to the device type of the first wireless device in one or more segments.

59. The method of claim 58, wherein conveying the one or more messages further comprises: The one or more messages are communicated to the first wireless device based on a second set of one or more type-specific parameters from one or more second type-specific segments, wherein the one or more second type-specific segments are at least partially based on the device type of the first wireless device.

60. The method of claim 58, wherein sending the message extension container further comprises: Send the message extension container comprising a plurality of frame check sequences, wherein each of the one or more segments comprises a corresponding frame check sequence among the plurality of frame check sequences.

61. The method of claim 58, wherein receiving the message extension container further comprises: Send the message extension container that includes multiple message integrity codes, wherein each of the one or more segments includes a corresponding message integrity code among the multiple message integrity codes.

62. A first wireless device for wireless communication, the first wireless device comprising: Components for receiving from a second wireless device a first message container including a first group of one or more type-specific segments, wherein the first type-specific segment in the first group of one or more type-specific segments includes a first group of one or more type-specific parameters; Components for receiving from the second wireless device a second message container comprising a second group of one or more type-specific segments, wherein both the first type-specific segment and the second type-specific segment in the second group of one or more type-specific segments correspond to the device type of the first wireless device; and A component for communicating one or more messages with the second wireless device based on the first type-specific segment and the second type-specific segment.

63. A second wireless device for wireless communication, the second wireless device comprising: Components for transmitting a first message container, including one or more type-specific segments of a first group, to a first wireless device, wherein the first type-specific segment of the first group of one or more type-specific segments includes one or more type-specific parameters of the first group; Components for sending a second message container, including one or more type-specific segments in a second group, to the first wireless device, wherein both the first type-specific segment and the second type-specific segment in the second group of one or more type-specific segments correspond to the device type of the first wireless device; and A component for communicating one or more messages with the first wireless device based on the first type-specific segment and the second type-specific segment.

64. A non-transitory computer-readable medium storing code for wireless communication at a first wireless device, the code including instructions executable by one or more processors to: Receive a first message container from a second wireless device, which includes one or more type-specific segments in a first group, wherein the first type-specific segment in the first group of one or more type-specific segments includes one or more type-specific parameters. Receive a second message container from the second wireless device, comprising one or more type-specific segments from a second set of segments, wherein both the first type-specific segment and the second type-specific segment from the second set of segments correspond to the device type of the first wireless device; and One or more messages are communicated to the second wireless device based on the first type-specific segment and the second type-specific segment.

65. A non-transitory computer-readable medium storing code for wireless communication at a second wireless device, the code including instructions executable by one or more processors to: A first message container comprising one or more type-specific segments of a first group is sent to a first wireless device, wherein the first type-specific segment of the first group of one or more type-specific segments comprises one or more type-specific parameters of the first group; A second message container comprising one or more type-specific segments in a second group is sent to the first wireless device, wherein both the first type-specific segment and the second type-specific segment in the second group of one or more type-specific segments correspond to the device type of the first wireless device; and One or more messages are communicated to the first wireless device based on the first type-specific segment and the second type-specific segment.

Images