Frame dropping under negotiated control frame protection

By defining the types of control frames that need to be discarded under negotiated control frame protection and using protected Multi-STA BlockAck frames for confirmation, the problem of undefined discarded control frames in the prior art is solved, thereby improving the security and reliability of wireless communication.

CN123123907APending Publication Date: 2026-11-17INTEL PRODUCT IP LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611121990.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2026-06-18
Filing Date
2026-07-27
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing technologies do not define which control frames need to be discarded under negotiated control frame protection, which allows attackers to launch attacks by forging unprotected control frames, affecting the security of wireless communication.

Method used

When negotiating control frame protection, define the types of unprotected control frames that need to be discarded, including individually addressed and group addressed control frames. Use protected Multi-STA BlockAck frames for acknowledgment, prohibit sending empty frames when DUO or LLI is enabled, and encapsulate the control frames to be protected after PTKSA is established.

Benefits of technology

It effectively prevents attackers from forging control frames, improves the security and reliability of wireless communication, and ensures the integrity and consistency of frame exchange.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123907A_ABST
    Figure CN123123907A_ABST
Patent Text Reader

Abstract

This application relates to frame discarding under negotiated control frame protection. This disclosure describes systems, methods, and apparatus related to optimized frame protection. The apparatus can negotiate control frame protection with a peer. The apparatus can establish a Paired Temporary Key Security Association (PTKSA) with the peer. The apparatus can receive control frames from the peer. The apparatus can discard control frames based on whether the control frame is included in a discard control frame list and after the PTKSA is established.
Need to check novelty before this filing date? Find Prior Art

Description

Cross-references to related applications

[0001] This application claims the benefits of U.S. Provisional Application No. 63 / 858,022, filed August 5, 2025; U.S. Provisional Application No. 63 / 873,277, filed August 29, 2025; and U.S. Provisional Application No. 63 / 911,972, filed November 5, 2025, the disclosures of which are incorporated herein by reference as if fully set forth herein. Technical Field

[0002] This application relates to the field of wireless communication technology, and more specifically, discloses frame dropping under negotiated control frame protection. Background Technology

[0003] Wireless devices are becoming more ubiquitous, making efficient access to wireless channels essential. Standards are evolving to enhance connectivity, thereby integrating advanced technologies into modern networks. Summary of the Invention

[0004] In a first aspect, this application provides an apparatus for control frame protection, including a processing circuitry coupled to a storage device, the processing circuitry being configured to: negotiate control frame protection with a peer; establish a pairwise temporary key security association (PTKSA) with the peer; receive control frames from the peer; and discard control frames based on the control frames being included in a discard control frame list and after the PTKSA is established.

[0005] In a second aspect, this application provides a computer-readable medium storing computer-executable instructions that, when executed by one or more processors, cause an operation to be performed, the operation including: negotiating control frame protection with a peer; establishing a pairwise temporary key security association (PTKSA) with the peer; receiving a control frame from the peer; and discarding the control frame based on the control frame being included in a discard control frame list and after the PTKSA is established.

[0006] In a third aspect, this application provides a method for control frame protection, comprising: negotiating control frame protection with a peer; establishing a pairwise temporary key security association (PTKSA) with the peer; receiving a control frame from the peer; and discarding the control frame based on the control frame being included in a discard control frame list and after the PTKSA is established. Attached Figure Description

[0007] Figure 1 This is a network diagram illustrating an example network environment for optimizing frame protection according to one or more example embodiments of the present disclosure.

[0008] Figure 2The illustration shows a flow of a process for optimizing a frame protection system according to one or more exemplary embodiments of the present disclosure.

[0009] Figure 3 The illustration shows a functional diagram of an exemplary communication station that may be suitable for use as a user equipment according to one or more example embodiments of the present disclosure.

[0010] Figure 4 A block diagram of an example machine capable of performing any one or more technologies (e.g., methods) according to one or more example embodiments of the present disclosure is illustrated.

[0011] Figure 5 It is a block diagram of a wireless architecture based on some examples.

[0012] Figure 6 The illustration depicts one or more exemplary embodiments of the present disclosure for use with Figure 5 Example front-end module circuit system of wireless architecture.

[0013] Figure 7 The illustration depicts one or more exemplary embodiments of the present disclosure for use with Figure 5 An example wireless IC circuit system with a wireless architecture.

[0014] Figure 8 The illustration depicts one or more exemplary embodiments of the present disclosure for use with Figure 5 An example baseband processing circuit system for a wireless architecture. Detailed Implementation

[0015] The following description and accompanying drawings fully illustrate specific embodiments to enable those skilled in the art to practice those embodiments. Other embodiments may include structural, logical, electrical, process, algorithm, and other changes. Parts and features of some embodiments may be included in other embodiments, or substitute for those parts and features of other embodiments. The embodiments set forth in the claims cover all available equivalents of those claims.

[0016] Wi-Fi 8 (IEEE 802.11bn or Ultra-High Reliability (UHR)) is the next generation of Wi-Fi and the successor to the IEEE 802.11be (Wi-Fi 7) standard. Consistent with all previous Wi-Fi standards, Wi-Fi 8 aims to improve wireless performance overall while introducing new and innovative features to further advance Wi-Fi technology.

[0017] Control frame protection is defined in revmf to protect the following control frames as described in revmf D0.2.

[0018] The control frames defined as protected are: Individual addressing trigger frames and group addressing trigger frames; Individually addressed Multi-STA BlockAck frames and group-addressed Multi-STA BlockAck frames; Separately address compressed BlockAckReq (block acknowledgment request) frames; Address the Multi-TID BlockAckReq frame separately.

[0019] The two STAs negotiate control frame protection based on the capability bits in RSNXE, as described in the following text in revmf D0.2.

[0020] The dot11CIPActivated field of the STA that supports control frame protection is true. Control frame protection is negotiated if both the associated non-AP STA and AP have the CIP support field set to 1 in RSNXE.

[0021] After the negotiation control frame protection, Multi-STA BA is used to acknowledge individual addressing frames, as described in the following text in revmfD0.2.

[0022] If the STA has negotiated control frame protection, the STA should use the protected Multi-STA BlockAck frame to provide acknowledgment for a separate addressing frame that requests acknowledgment for another STA.

[0023] After control frame protection is negotiated, Multi-STA BA is also used to acknowledge requests from GCR MU-BAR or MU-BAR, as described in the following text in revmf D0.2.

[0024] A protected GCR MU-BAR trigger frame should request a protected Multi-STA BlockAck frame, not a GCR BlockAck frame.

[0025] Non-AP STAs that support GCR and have negotiated control frame protection should include a protected Multi-STA BlockAck frame, not a GCR BlockAck frame, in the TB PPDU sent in response to a protected GCR MU-BAR trigger frame (see 9.3.1.22.7 (GCR MU-BAR trigger frame format)). APs should not send GCR BlockAckReq frames to non-AP STAs that support GCR and have negotiated control frame protection.

[0026] A protected MU-BAR trigger frame should request a protected Multi-STA BlockAck frame. Non-AP STAs that have negotiated control frame protection should include the protected Multi-STA BlockAck frame in the TB PPDU sent in response to a protected MU-BAR trigger frame (see 9.3.1.22.4 (MU-BAR trigger frame format)).

[0027] Under negotiated control frame protection, certain unprotected control frames need to be discarded, preventing attackers from continuing to send forged unprotected control frames to launch attacks.

[0028] The existing solution does not define what kind of control frames need to be discarded.

[0029] The IEEE 802.11 technical standard defines the specifications for Wi-Fi. ® Communication includes communication with empty frames, which are control frames that do not carry data payloads. Currently, sending empty frames between Quality of Service (QoS) Station Equipment (STAs) is not recommended. However, empty frames are not currently disabled for QoS STAs. In 802.11 revmf, it is defined that if control frame protection is negotiated, Multi-STA Block Acknowledgment (M-BA) should be used to acknowledge individually addressed frames. In 802.11bn, it is also specified that if DUO (Dynamically Unavailable Operation) or LLI (Low Latency Indication) is enabled, Multi-STA BA (M-BA) should be used for acknowledgment. However, Multi-STA BA currently does not have an empty frame acknowledgment context. For reference, 802.11 currently specifies that "a QoS STA should not send individually addressed frames to another QoS STA that have a type subfield indicating data and a subtype subfield indicating an empty frame." The following table is currently included in 802.11.

[0030] Table 1: Valid Type and Subtype Combinations Table 2: Context of each AID TID information subfield and the existence of optional subfields when the AID11 subfield is not 2045 The 802.11bn standard specifies that: "A UHR AP sending a PPDU requesting acknowledgment or block acknowledgment from a UHR STA with DUO or LLI enabled shall ensure that: 1) the value of the duration / ID field of the MPDU carried in the PPDU and 2) the resources allocated in any triggering frame carried in the PPDU are considered in the immediate response, which is a Multi-STABlockAck frame. In addition to the Per AID TID Info field containing the requested (block) acknowledgment context, the Multi-STABlockAck frame shall also contain at least: If DUO is enabled on a non-AP STA, carry an unavailability feedback per AID TID Info field (see 37.19.2 (Dynamic Unavailability Operation (DUO) Mode)) [8 octets]; When LLI is enabled on a non-AP STA, a Per AID TID Info field (see 37.24 (Low Latency Indication (LLI))) [8 octets] is carried to provide low latency feedback; Carry zero or more Per AID TID Info fields [variable octets] filled.

[0031] A UHR STA with DUO enabled or LLI enabled that receives a PPDU (which contains a frame requiring acknowledgment or block acknowledgment) shall respond with a Multi-STA BlockAck frame, which, in addition to the acknowledgment context defined in 26.4.2 (the acknowledgment context in the Multi-STA BlockAck frame), shall include at least the following after the Per AID TID Info field with the acknowledgment context: If the STA is a non-AP STA with DUO enabled, carry zero or one Per AIDTID Info field with unavailable feedback (see 37.19.2 (Dynamic Unavailable Operation (DUO) Mode) (8 octets); When the STA is a non-AP STA with LLI enabled, carry zero or one Per AIDTID Info field (see 37.24 (Low Latency Indication (LLI))) [8 octets] for low latency feedback; Carry zero or more Per AID TID Info fields [variable octets] filled.

[0032] Wi-Fi 8 (IEEE 802.11bn or Ultra-High Reliability (UHR)) is the next generation of Wi-Fi and the successor to the IEEE 802.11be (Wi-Fi 7) standard. Consistent with all previous Wi-Fi standards, Wi-Fi 8 aims to improve wireless performance overall while introducing new and innovative features to further advance Wi-Fi technology.

[0033] Control frame protection: RevMF has implemented protection for control frames such as trigger frames, M-BA, and BAR to protect control frames from various attacks.

[0034] This is an attack that sends forged trigger frames to induce the client to perform unnecessary actions (such as exiting low-power mode, performing long-duration transmissions, exiting low-operability mode, switching channels, etc.).

[0035] This addresses attacks that send forged block acknowledgment (BA) frames to cause the initiator to discard data in the transmission window or carry false feedback.

[0036] This addresses attacks that send forged Block Acknowledgment Request (BAR) frames to cause the responder to discard data in the received reordering buffer.

[0037] Some chip vendors have stated that they cannot support trigger frames that request acknowledgments via data aggregation in the A-MPDU. Trigger frames that aggregate data in the A-MPDU are used in a specific scenario to support the DL MU and guide each MU receiver to respond with acknowledgments in the correct resources of the TB PPDU. This is a common scenario when the DL MU is used by only a small number of users. If the DL MU is used by a large number of users, a more efficient approach is to send the DL MU, followed by the MU-BAR and acknowledgment. However, this may not be more efficient than using a separate addressing trigger frame with data aggregation.

[0038] One proposal is to simply disable trigger frames in the A-MPDU, but include only multiple repeating trigger frames in the A-MPDU without aggregating them with data, to improve reliability. Therefore, more use cases are disabled. Subsequently, the use of trigger frames aggregated with data to request acknowledgments is prohibited, which prevents common scenarios of requesting acknowledgments in the DL MU.

[0039] Exemplary embodiments of this disclosure relate to systems, methods, and apparatus for frame dropping under negotiated control frame protection.

[0040] It is proposed to appropriately define which unprotected control frames need to be discarded when negotiating control frame protection.

[0041] One or more advantages include: by discarding unprotected control frames, attackers cannot launch attacks using forged unprotected control frames.

[0042] In one or more embodiments, the device or system may include one or more components, which may include one or more of the following: apparatus, station (STA), access point (AP), and / or other network elements. In its most basic configuration, the device or system includes one or more processors, memory, and instructions. The processor may be implemented using a general-purpose microprocessor, digital signal processor (DSP), field-programmable gate array (FPGA), or other suitable computing entity capable of performing calculations or manipulations of information. The memory may include RAM, ROM, flash memory, or other storage media suitable for storing instructions and data required for system operation. These components, individually or in combination, implement the execution of processes that facilitate communication and functionality within the system.

[0043] This disclosure proposes (a) prohibiting the transmission of empty frames between QoS STAs when CFP (Control Frame Protection) is negotiated, DUO is enabled, or LLI is enabled, or (b) allowing the same acknowledgment context of QoS empty frames to be used for empty frames, or (c) prohibiting the transmission of empty frames between UHR STAs.

[0044] The enhancements described in this paper can be applied to, for example, 802.11revmf and / or 802.11bn.

[0045] The exemplary embodiments of this disclosure relate to systems, methods, and apparatus for controlling frame protection (with exceptions for trigger frame aggregation).

[0046] An exception is proposed for the control frame protection of trigger frames for data aggregation, with a specific configuration that focuses on scenarios requiring confirmation.

[0047] The client is proposed to respond to unprotected basic trigger frames only with acknowledgments, and the AP sends unprotected basic trigger frames using the above settings.

[0048] In one or more embodiments, the device or system may include one or more components, which may include one or more of the following: apparatus, station (STA), access point (AP), and / or other network elements. In its most basic configuration, the device or system includes one or more processors, memory, and instructions. The processor may be implemented using a general-purpose microprocessor, digital signal processor (DSP), field-programmable gate array (FPGA), or other suitable computing entity capable of performing calculations or manipulations of information. The memory may include RAM, ROM, flash memory, or other storage media suitable for storing instructions and data required for system operation. These components, individually or in combination, implement the execution of processes that facilitate communication and functionality within the system.

[0049] The above description is for illustrative purposes and is not intended to be limiting. Many other examples, configurations, processes, algorithms, etc., may exist, some of which will be described in more detail below. Example embodiments will now be described with reference to the accompanying drawings.

[0050] Figure 1 This is a network diagram illustrating an example network environment with optimized frame protection according to some example embodiments of the present disclosure. Wireless network 100 may include one or more user equipments 120 capable of communicating according to the IEEE 802.11 communication standard and one or more access points (APs) 102. User equipment 120 may be non-fixed mobile devices (e.g., without a fixed location) or fixed devices.

[0051] In some embodiments, the user equipment 120 and access point 102 may include one or more computer systems, the one or more computer systems being similar to Figure 3 Functional diagrams of computer systems and / or Figure 4 Example machine / system.

[0052] One or more illustrative user equipment 120 and / or AP 102 may be operated by one or more users 110. It should be noted that any addressable unit may be a station (STA). An STA may have several different characteristics, each affecting its functionality. As an example, a single addressable unit may simultaneously be a portable STA, a Quality of Service (QoS) STA, a subordinate STA, and a hidden STA. One or more illustrative user equipment 120 and AP 102 may be STAs. One or more illustrative user equipment 120 and / or AP 102 may operate as a Personal Basic Service Set (PBSS) control point / access point (PCP / AP). User equipment 120 (e.g., 124, 126, or 128) and / or AP 102 may contain any suitable processor-driven device, including but not limited to mobile or non-mobile devices, such as static devices. As an example, user equipment 120 and / or AP 102 may include user equipment (UE), station (STA), access point (AP), software-enabled AP (SoftAP), personal computer (PC), wearable wireless device (e.g., wristband, watch, glasses, ring, etc.), desktop computer, mobile computer, laptop computer, ultrabook TMComputers, laptops, tablets, server computers, handheld computers, handheld devices, Internet of Things (IoT) devices, sensor devices, PDA devices, handheld PDA devices, in-vehicle devices, off-vehicle devices, hybrid devices (e.g., combining cellular phone functionality with PDA device functionality), consumer devices, vehicle devices, non-vehicle devices, mobile or portable devices, non-mobile or non-portable devices, mobile phones, cellular phones, PCS devices, PDA devices incorporating wireless communication devices, mobile or portable GPS devices, DVB devices, relatively small computing devices, non-desktop computers, "Small Portable, Large Use" (CSLL) devices, ultra-mobile devices (UMD), ultra-mobile PCs (UMPC), mobile internet devices (MID), "foldable" devices or computing devices, devices supporting Dynamically Composable Computation (DCC), context-aware devices, video devices, audio devices, A / V devices, set-top boxes (STBs), Blu-ray disc (BD) players, BD recorders, digital video disc (DVD) players, high-definition (HD) DVD players, DVD recorders, HD DVD recorders, personal video recorders (PVRs), broadcast HD receivers, video sources, audio sources, video receivers, audio receivers, stereo tuners, broadcast wireless receivers, flat panel displays, personal media players (PMPs), digital video cameras (DVCs), digital audio players, speakers, audio receivers, audio amplifiers, gaming devices, data sources, data receivers, digital still cameras (DSCs), media players, smartphones, televisions, music players, etc. Other devices (including smart devices such as lights, thermostats, automotive components, home appliances, etc.) may also be included in this list.

[0053] As used herein, the term "Internet of Things (IoT) device" refers to any object (e.g., appliance, sensor, etc.) that has an addressable interface (e.g., Internet Protocol (IP) address, Bluetooth identifier (ID), Near Field Communication (NFC) ID, etc.) and is capable of sending information to one or more other devices via a wired or wireless connection. IoT devices may have passive communication interfaces, such as Quick Response (QR) codes, Radio Frequency Identification (RFID) tags, NFC tags, etc., or active communication interfaces, such as modems, transceivers, transmitter-receivers, etc. IoT devices can have a specific set of attributes (e.g., device status or condition (e.g., whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, etc.), cooling or heating functions, environmental monitoring or recording functions, light emission functions, sound emission functions, etc.), which can be embedded in and / or controlled / monitored by a central processing unit (CPU), microprocessor, ASIC, etc., and configured to connect to an IoT network, such as a local self-organizing network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwave ovens, freezers, dishwashers, tableware, hand tools, washing machines, dryers, stoves, air conditioners, thermostats, televisions, lamps, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., as long as the device is equipped with an addressable communication interface for communicating with the IoT network. IoT devices may also include mobile phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Therefore, an IoT network can consist of a combination of "traditional" internet-accessible devices (e.g., laptops or desktop computers, mobile phones, etc.) and devices that typically do not have internet connectivity (e.g., dishwashers, etc.).

[0054] According to one or more IEEE 802.11 standards and / or 3GPP standards, user equipment 120 and / or AP 102 may also be included in a grid station, for example, in a grid network.

[0055] Any of user equipment 120 (e.g., user equipment 124, 126, 128) and AP 102 may be configured to communicate with each other wirelessly or via one or more communication networks 130 and / or 135. User equipment 120 may also communicate peer-to-peer or directly with or without AP 102. Any of communication networks 130 and / or 135 may include, but is not limited to, any combination of different kinds of suitable communication networks, such as broadcast networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and / or public networks. Furthermore, any of communication networks 130 and / or 135 may have any suitable communication range associated with it and may include, for example, a global network (e.g., the Internet), a metropolitan area network (MAN), a wide area network (WAN), a local area network (LAN), or a personal area network (PAN). Additionally, any of the communication networks 130 and / or 135 may include any type of medium capable of carrying network traffic, including but not limited to coaxial cable, twisted pair, optical fiber, hybrid fiber-coaxial (HFC) medium, microwave terrestrial transceiver, radio frequency communication medium, space communication medium, ultra-high frequency communication medium, satellite communication medium, or any combination thereof.

[0056] Either user equipment 120 (e.g., user equipment 124, 126, 128) or AP 102 may include one or more communication antennas. The one or more communication antennas may be any suitable type of antenna corresponding to the communication protocol used by user equipment 120 (e.g., user equipment 124, 126, and 128) and AP 102. Some non-limiting examples of suitable communication antennas include Wi-Fi antennas, IEEE 802.11 series standard compliant antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi-omnidirectional antennas, etc. The one or more communication antennas may be communicatively coupled to wireless components to transmit and / or receive signals, such as communication signals to and / or from user equipment 120 and / or AP 102.

[0057] Any one of User Equipment 120 (e.g., User Equipment 124, 126, 128) and AP 102 can be configured to perform directional transmission and / or directional reception while conducting wireless communication in a wireless network. Any one of User Equipment 120 (e.g., User Equipment 124, 126, 128) and AP 102 can be configured to perform such directional transmission and / or directional reception using a collection of multiple antenna arrays (e.g., DMG antenna arrays, etc.). Each of the multiple antenna arrays can be used to transmit and / or receive in a specific corresponding direction or directional range. Any one of User Equipment 120 (e.g., User Equipment 124, 126, 128) and AP 102 can be configured to perform any given directional transmission toward one or more defined transmit sectors. Any one of User Equipment 120 (e.g., User Equipment 124, 126, 128) and AP 102 can be configured to perform any given directional reception from one or more defined receive sectors.

[0058] MIMO beamforming in a wireless network can be implemented using RF beamforming and / or digital beamforming. In some embodiments, when performing a given MIMO transmission, user equipment 120 and / or AP 102 may be configured to perform MIMO beamforming using all or a subset of its one or more communication antennas.

[0059] Either user equipment 120 (e.g., user equipment 124, 126, 128) and AP 102 may include any suitable radio and / or transceiver for transmitting and / or receiving radio frequency (RF) signals in a bandwidth and / or channel corresponding to a communication protocol utilized by either user equipment 120 or AP 102 to communicate with each other. The wireless component may include hardware and / or software for modulating and / or demodulating communication signals according to a pre-established transmission protocol. The wireless component may also have hardware and / or software instructions for communicating via one or more Wi-Fi and / or Wi-Fi Direct protocols defined in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard. In some example embodiments, the wireless components and communication antennas can be configured to communicate via 2.4 GHz channels (e.g., 802.11b, 802.11g, 802.11n, 802.11ax), 5 GHz channels (e.g., 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11bn, etc.), 6 GHz channels (e.g., 802.11ax, 802.11be, 802.11bn, etc.), or 60 GHz channels (e.g., 802.11ad, 802.11ay), or 800 MHz channels (e.g., 802.11ah). The communication antennas can operate at 28 GHz and 40 GHz. It should be understood that this list of communication channels is only a partial list according to certain 802.11 standards, and other 802.11 standards (e.g., next-generation Wi-Fi or other standards) may be used. In some embodiments, communication between devices may use non-Wi-Fi protocols, such as Bluetooth, Dedicated Short-Range Communication (DSRC), Ultra High Frequency (UHF) (e.g., IEEE 802.11af, IEEE 802.22), white-band frequencies (e.g., open space), or other packet-based wireless communications. The wireless components may include any known receiver and baseband suitable for communication via a communication protocol. The wireless components may also include a low-noise amplifier (LNA), an additional signal amplifier, an analog-to-digital (A / D) converter, one or more buffers, and a digital baseband.

[0060] In one embodiment, and referring to Figure 1User equipment 120 can communicate with one or more APs 102. For example, one or more APs 102 can implement optimized frame protection 142 with one or more user equipment 120. One or more APs 102 can be multi-link devices (MLDs), and one or more user equipment 120 can be non-AP MLDs. Each of the one or more APs 102 can include multiple individual APs (e.g., AP1, AP2, ..., APn, where n is an integer), and each of the one or more user equipment 120 can include multiple individual STAs (e.g., STA1, STA2, ..., STAn). AP MLDs and non-AP MLDs can establish one or more links (e.g., Link1, Link2, ..., Linkn) between each of the individual APs and STAs. It is understood that the above description is for illustrative purposes and is not intended to be limiting.

[0061] In one or more embodiments, it is proposed to define the list of discarded control frames as follows.

[0062] When control frame protection is negotiated, individual addressing control frames and group addressing control frames defined as to be protected should be encapsulated using the procedures defined in 12.6.xx (Protection of Control Frames) after PTKSA is established, and subsequent frames from peer STAs that have negotiated control frame protection should be discarded after PTKSA is established.

[0063] Unprotected standalone addressing control frames are defined as pending protection. This is because after PTKSA is established, all standalone addressing control frames defined as pending protection will always be protected.

[0064] Unprotected group addressing control frames are defined as pending protection. This is because after PTKSA is established, all group addressing control frames defined as pending protection will always be protected.

[0065] Ack frames. This is because a protected Multi-STA BA will be used instead.

[0066] Compress the BlockAck frame. This is because a protected Multi-STA BA will be used instead.

[0067] When GCR is supported, the GCR BlockAck frame will be executed. This is because a protected Multi-STA BA will be used instead.

[0068] When GCR is supported, the GCR BlockAckReq frame will be used. This is because a protected GCR MU-BAR will be used instead.

[0069] Please understand that the above description is for illustrative purposes and is not intended to impose limitations.

[0070] It also discloses a capability bit in the Robust Security Network Extension Element (RSNXE) to allow for exceptions to the basic trigger frame for protection and data frame aggregation to request acknowledgment.

[0071] This bit can be referred to as the basic trigger frame that supports requesting acknowledgment in the A-MPDU.

[0072] The following definition is proposed for a control frame that is to be protected.

[0073] The control frame defined as to be protected is: Individual addressing trigger frames and group addressing trigger frames with the following exceptions: In a separately addressed basic trigger frame in an A-MPDU (not an S-MPDU), if the associated non-AP STA or AP sets the "Basic trigger frame that supports requesting acknowledgment in A-MPDU" field in RSNXE to 0, the TID aggregation limit field of the separately addressed basic trigger frame is equal to 0, and the UL length subfield in the public information field is less than or equal to 418.

[0074] Individually addressed Multi-STA BlockAck frames and group-addressed Multi-STA BlockAck frames.

[0075] Separately address compressed BlockAckReq frames.

[0076] Address the Multi-TID BlockAckReq frame separately.

[0077] The following rules are proposed.

[0078] If control frame protection is negotiated, and the associated non-AP STA or AP sets the "Support basic trigger frame for requesting acknowledgment in A-MPDU" field in RSNXE to 0, then: In any transmission from an unprotected, separately addressed basic trigger frame in an A-MPDU (not S-MPDU) to an associated non-AP STA, the AP should set the TID aggregation limit field to 0 and the UL length subfield in the common information field to less than or equal to 418.

[0079] The associated non-AP STA should acknowledge the response to the unprotected, individually addressed basic trigger frame from the AP in the HE TB PPDU (if capable) solely based on the A-MPDU content in the control response context of Table 9-728, and should not perform any other operations (e.g., SMPS).

[0080] It is recommended that non-AP STAs use the following procedure to determine whether unprotected basic trigger frames should be accepted rather than discarded.

[0081] The trigger frame must meet the following conditions: The trigger type subfield is set to basic.

[0082] The UL length subfield of the public information field is less than or equal to 418.

[0083] The RA address is addressed separately.

[0084] The EOF / Tag field of the MPDU separator preceding the MPDU carrying the unprotected basic trigger frame is set to 0, indicating that the MPDU is not an S-MPDU.

[0085] The TID aggregation limit subfield in the trigger-dependent user information subfield is set to 0.

[0086] Carrying in the A-MPDU: When the PPDU format is VHT, HE, EHT, or UHR.

[0087] When the PPDU format is HT and the aggregate subfield in HT-SIG is set to 1.

[0088] Please understand that the above description is for illustrative purposes and is not intended to impose limitations.

[0089] Figure 2 The illustration shows the flow of an illustrative process 200 for an optimized frame protection system according to one or more exemplary embodiments of the present disclosure.

[0090] Figure 2 The illustration shows the flow of an illustrative process 200 of an enhanced frame protection system according to one or more exemplary embodiments of the present disclosure.

[0091] At box 202, the device (e.g., Figure 1 User equipment 120 and / or AP 102 and / or Figure 4 The enhanced frame protection device 419 can negotiate with peer stations to control frame protection.

[0092] At box 204, the device can establish a Paired Temporary Key Security Association (PTKSA) with the peer station.

[0093] At frame 206, the device can receive control frames from the peer station.

[0094] At box 208, the device may discard control frames based on whether the control frame is included in the list of discarded control frames and after the PTKSA is established.

[0095] In one or more embodiments, the device or system may maintain a list of discarded control frames (which may include unprotected individual addressing control frames defined as pending protection), such that control frames intended to receive protection but arriving without carrying protection can be identified and shelved without processing. In one or more embodiments, the device or system may also include unprotected group addressing control frames defined as pending protection within the list of discarded control frames. Technical problems may arise if an attacker injects or replays control frames that should be protected but were received in plaintext, and the device can mitigate these problems by treating any such frames as candidate for discard. For example, if a control frame that should carry protection is received without it, the device can place the control frame in the list of discarded control frames and avoid taking action on its contents, thereby reducing exposure to spoofed or replayable control signaling.

[0096] In one or more embodiments, a device or system may populate a drop control frame list with Ack frames and compressed BlockAck frames, allowing these acknowledgment-related frames to be evaluated against protection expectations before being trusted. In one or more embodiments, where GCR is supported, the device or system may also include GCR BlockAck frames and GCR BlockAckReq frames in the drop control frame list, thereby allowing multicast acknowledgment signaling to be governed by the same expectations. For example, in a deployment where GCR is enabled for reliable group delivery, the device may drop GCR BlockAckReq frames that arrive without the intended protection, thereby helping to prevent manipulation of group acknowledgment exchanges.

[0097] In one or more embodiments, the device or system may be configured such that, after the PTKSA is established, encapsulation is defined as a separately addressed control frame to be protected based on the control frame protection process. This addresses the situation where control frames sent before the security association is in place cannot be cryptographically protected, as the device can postpone protection execution until the key material becomes available. For example, once the PTKSA is established between two stations, the device can begin encapsulating compliant control frames, allowing the receiver to verify their integrity and authenticity.

[0098] In one or more embodiments, a device or system may be configured to prohibit the transmission of empty frames to a QoS station based on at least one of control frame protection being negotiated, DUO being enabled, or LLI being enabled. Technical challenges may arise when empty frames are transmitted in a manner inconsistent with negotiated protection or latency-sensitive characteristics, and the device can prevent such transmissions to maintain consistent behavior. For example, with DUO or LLI enabled, the device can suppress empty frames directed to the QoS station to avoid signaling that may conflict with active protection or latency configurations.

[0099] In one or more embodiments, the device or system may be configured to acknowledge empty frames based on the acknowledgment context within the M-BA. This satisfies the need for efficient acknowledgment of empty frame reception when multiple stations share acknowledgment exchanges because the device can rely on the M-BA context instead of issuing individual responses. For example, the device can use the appropriate context within the M-BA to indicate acknowledgment of empty frames, thereby allowing acknowledgments for several stations within a single coordination response.

[0100] In one or more embodiments, a device or system may be configured to discard control frames based on the availability of a protected Multi-STA BA for acknowledgment. This addresses situations that would otherwise rely on a low-security acknowledgment path, as the device may tend to discard control frames when the protected Multi-STA BA is capable of performing acknowledgment functions. For example, when a protected Multi-STA BA is available, the device may discard control frames that would otherwise be acknowledged via a weaker mechanism, thereby aligning the acknowledgment process with the effective protection.

[0101] Please understand that the above description is for illustrative purposes and is not intended to impose limitations.

[0102] Figure 3 A functional diagram of an exemplary communication station 300 according to one or more example embodiments of the present disclosure is shown. In one embodiment, Figure 3 The illustration depicts an embodiment suitable for use as AP 102 ( Figure 1 ) or user equipment 120 ( Figure 1 The communication station 300 is a functional block diagram of a communication station. The communication station 300 can also be used as a handheld device, mobile device, cellular phone, smartphone, tablet computer, netbook, wireless terminal, laptop computer, wearable computer device, femtocell, high data rate (HDR) subscriber station, access point, access terminal or other personal communication system (PCS) device.

[0103] Communication station 300 may include a communication circuitry system 302 and a transceiver 310, the transceiver 310 being used to transmit signals to and receive signals from other communication stations using one or more antennas 301. Communication circuitry system 302 may include circuitry capable of operating physical layer (PHY) communication and / or controlling access to a wireless medium for Media Access Control (MAC) communication, and / or any other communication layer for transmitting and receiving signals. Communication station 300 may also include a processing circuitry system 306 and a memory 308 arranged to perform the operations described herein. In some embodiments, communication circuitry system 302 and processing circuitry system 306 may be configured to perform the operations detailed in the figures, diagrams, and flowcharts described above.

[0104] According to some embodiments, the communication circuitry system 302 may be arranged to compete for a wireless medium and configured for communicating frames or packets over the wireless medium. The communication circuitry system 302 may be arranged to transmit and receive signals. The communication circuitry system 302 may also include circuitry for modulation / demodulation, up-conversion / down-conversion, filtering, amplification, etc. In some embodiments, the processing circuitry system 306 of the communication station 300 may include one or more processors. In other embodiments, two or more antennas 301 may be coupled to the communication circuitry system 302 arranged to transmit and receive signals. The memory 308 may store information for configuring the processing circuitry system 306 to perform operations for configuring and transmitting message frames, as well as performing various operations described herein. The memory 308 may include any type of memory (including non-transitory memory) for storing information in a machine-readable (e.g., computer) form. For example, the memory 308 may include computer-readable storage devices, read-only memory (ROM), random access memory (RAM), disk storage media, optical storage media, flash memory devices, and other storage devices and media.

[0105] In some embodiments, the communication station 300 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capabilities, a network tablet computer, a wireless phone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device capable of wirelessly receiving and / or transmitting information.

[0106] In some embodiments, communication station 300 may include one or more antennas 301. Antenna 301 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for RF signal transmission. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture can be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas can be effectively separated for spatial diversity and the different channel characteristics that may result between each antenna and the antenna of the transmitting station.

[0107] In some embodiments, the communication station 300 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, a speaker, and other mobile device components. The display may be an LCD screen including a touchscreen.

[0108] Although the communication station 300 is illustrated as having several separate functional elements, two or more functional elements may be combined and implemented by a combination of software-configurable elements, such as processing elements including a digital signal processor (DSP) and / or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), radio frequency integrated circuits (RFICs), and combinations of various hardware and logic circuit systems for performing the functions described at least herein. In some embodiments, a functional element of the communication station 300 may refer to one or more processes operating on one or more processing elements.

[0109] Some embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device that can be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory memory mechanism for storing information in a machine-readable (e.g., computer) form. For example, a computer-readable storage device may include read-only memory (ROM), random access memory (RAM), disk storage media, optical storage media, flash memory devices, and other storage devices and media. In some embodiments, communication station 300 may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

[0110] Figure 4 The diagram illustrates an example of a machine 400 or system on which any one or more of the technologies (e.g., methods) discussed herein may be executed. In other embodiments, machine 400 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, machine 400 may operate as a server machine, a client machine, or both in a server-client network environment. In the example, machine 400 may act as a peer-to-peer (P2P) (or other distributed) network environment. Machine 400 may be a personal computer (PC), tablet PC, set-top box (STB), personal digital assistant (PDA), mobile phone, wearable computing device, network device, network router, switch, or bridge, or any machine capable of (sequentially or otherwise) executing instructions specifying actions to be performed by the machine, such as a base station. Furthermore, although only a single machine is illustrated, the term "machine" should also be understood to include any collection of machines that individually or jointly execute a set (or sets of sets) of instructions to perform any one or more of the methods (such as cloud computing, Software as a Service (SaaS), or other computer cluster configurations) discussed herein.

[0111] As described herein, examples may include logic or multiple components, modules, or mechanisms, or may operate on logic or multiple components, modules, or mechanisms. A module is a tangible entity (e.g., hardware) capable of performing a specified operation at operational time. A module includes hardware. In one example, the hardware may be specifically configured to perform a particular operation (e.g., hardwiring). In another example, the hardware may include a configurable execution unit (e.g., transistor, circuitry, etc.) and a computer-readable medium containing instructions that configure the execution unit to perform a specific operation at operational time. Configuration may occur under the guidance of the execution unit or loading mechanism. Thus, when the device operates, the execution unit is communicatively coupled to the computer-readable medium. In this example, the execution unit may be a component of more than one module. For example, in operation, the execution unit may be configured by a first set of instructions to implement a first module at a point in time, and reconfigured by a second set of instructions to implement a second module at a second point in time.

[0112] Machine (e.g., computer system) 400 may include a hardware processor 402 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), main memory 404, and static memory 406, some or all of which may communicate with each other via an interconnect link (e.g., a bus) 408. Machine 400 may also include a power management device 432, a graphics display device 410, an alphanumeric input device 412 (e.g., a keyboard), and a user interface (UI) navigation device 414 (e.g., a mouse). In this example, the graphics display device 410, the alphanumeric input device 412, and the UI navigation device 414 may be a touchscreen display. Machine 400 may additionally include a storage device (i.e., a drive unit) 416, a signal generation device 418 (e.g., a speaker), an optimized frame protection device 419, a network interface device / transceiver 420 coupled to an antenna 430, and one or more sensors 428, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. Machine 400 may include an output controller 434, such as serial (e.g., Universal Serial Bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.)) connection, to communicate with or control one or more peripheral devices (e.g., printers, card readers, etc.). Operation according to one or more exemplary embodiments of this disclosure may be performed by a baseband processor. The baseband processor may be configured to generate appropriate baseband signals. The baseband processor may also include physical layer (PHY) and media access control layer (MAC) circuitry and may also interface with hardware processor 402 for generating and processing baseband signals and for controlling the operation of main memory 404, storage device 416, and / or optimizing frame protection device 419. The baseband processor may be located on a single wireless card, a single chip, or an integrated circuit (IC).

[0113] Storage device 416 may include machine-readable medium 422 on which one or more sets of data structures or instructions 424 (e.g., software) are stored, which embody or are utilized by any one or more of the techniques or functions described herein. During execution by machine 400, instructions 424 may also reside wholly or at least partially within main memory 404, static memory 406, or hardware processor 402. In this example, one or any combination of hardware processor 402, main memory 404, static memory 406, or storage device 416 may constitute a machine-readable medium.

[0114] The optimized frame protection device 419 can perform or carry out any of the operations and processes described and shown above (e.g., process 200).

[0115] It is understood that the above is only a subset of the functions that the optimized frame protection device 419 can be configured to perform, and other functions included throughout this disclosure may also be performed by the optimized frame protection device 419.

[0116] Although machine-readable medium 422 is illustrated as a single medium, the term "machine-readable medium" can include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 424.

[0117] Various embodiments may be implemented entirely or partially in software and / or firmware. Such software and / or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. These instructions may then be read and executed by one or more processors to enable the performance of the operations described herein. The instructions may be in any suitable form, such as, but not limited to, source code, compiled code, interpreted code, executable code, static code, dynamic code, etc. Such computer-readable medium may include any tangible non-transitory medium (such as, but not limited to, read-only memory (ROM); random access memory (RAM); disk storage media; optical storage media; flash memory, etc.) for storing information in a form readable by one or more computers.

[0118] The term "machine-readable medium" can include any medium capable of storing, encoding, or carrying instructions executable by machine 400 and causing machine 400 to perform any one or more of the techniques disclosed herein, or any medium capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of machine-readable media can include solid-state memory as well as optical and magnetic media. In examples, a mass-based machine-readable medium includes a machine-readable medium having a plurality of particles having rest mass. Specific examples of mass-based machine-readable media can include non-volatile memories such as semiconductor storage devices (e.g., electrically programmable read-only memory (EPROM) or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

[0119] Instruction 424 can also be sent or received over communication network 426 via network interface device / transceiver 420 using any of a variety of transport protocols (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Example communication networks may include local area networks (LANs), wide area networks (WANs), packet data networks (e.g., the Internet), mobile phone networks (e.g., cellular networks), ordinary old-style telephone (POTS) networks, and wireless data networks (e.g., known as Wi-Fi). ® The Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards, known as WiMax ® The IEEE 802.16 series of standards, the IEEE 802.15.4 series of standards, and peer-to-peer (P2P) networks are examples of such standards. In the example, the network interface device / transceiver 420 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 426. In the example, the network interface device / transceiver 420 may include multiple antennas to perform wireless communication using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technologies. The term "transmission medium" should be understood to include any intangible medium capable of storing, encoding, or carrying instructions executed by machine 400 and comprising digital or analog communication signals, or other intangible media that facilitate communication of such software.

[0120] In various implementations, the operations and procedures described and illustrated above can be executed or performed in any suitable order as needed. Additionally, in some implementations, at least a portion of the operations can be executed in parallel. Furthermore, in some implementations, fewer or more operations than those described can be performed.

[0121] Figure 5 According to some embodiments, it is possible Figure 1 Block diagrams of wireless architectures 105A and 105B implemented in either example AP 102 and / or example STA 120 are provided. Wireless architectures 105A and 105B may include wireless front-end module (FEM) circuitry systems 504a-504b, wireless IC circuitry systems 506a-506b, and baseband processing circuitry systems 508a-508b. As shown, wireless architectures 105A and 105B include both wireless local area network (WLAN) functionality and Bluetooth (BT) functionality, but embodiments are not limited thereto. In this disclosure, "WLAN" and "Wi-Fi" are used interchangeably.

[0122] FEM circuit systems 504a-504b may include a WLAN or Wi-Fi FEM circuit system 504a and a Bluetooth (BT) FEM circuit system 504b. The WLAN FEM circuit system 504a may include a receive signal path that includes circuitry configured to operate on WLAN RF signals received from one or more antennas 501, amplify the received signals, and provide an amplified version of the received signals to the WLAN wireless IC circuit system 506a for further processing. The BT FEM circuit system 504b may include a receive signal path that includes circuitry configured to operate on BT RF signals received from one or more antennas 501, amplify the received signals, and provide an amplified version of the received signals to the BT wireless IC circuit system 506b for further processing. The FEM circuit system 504a may also include a transmit signal path that includes circuitry configured to amplify the WLAN signals provided by the wireless IC circuit system 506a for wireless transmission via one or more antennas 501. Furthermore, the FEM circuit system 504b may also include a transmission signal path, which may include circuitry configured to amplify the BT signal provided by the wireless IC circuit system 506b for wireless transmission via one or more antennas. Figure 5 In the embodiments, although FEM 504a and FEM 504b are shown as different from each other, the embodiments are not so limited and include the use of FEM (not shown) that includes a transmit path and / or receive path for both WLAN signals and BT signals, or the use of one or more FEM circuit systems, wherein at least some of the FEM circuit systems share a transmit signal path and / or receive signal path for both WLAN signals and BT signals.

[0123] As shown in the figure, the wireless IC circuit systems 506a-506b may include a WLAN wireless IC circuit system 506a and a BT wireless IC circuit system 506b. The WLAN wireless IC circuit system 506a may include a receive signal path, which may include circuitry that down-converts the WLAN RF signal received from the FEM circuit system 504a and provides the baseband signal to the WLAN baseband processing circuit system 508a. The BT wireless IC circuit system 506b may further include a receive signal path, which may include circuitry that down-converts the BT RF signal received from the FEM circuit system 504b and provides the baseband signal to the BT baseband processing circuit system 508b. The WLAN wireless IC circuit system 506a may also include a transmit signal path, which may include circuitry that up-converts the WLAN baseband signal provided by the WLAN baseband processing circuit system 508a and provides the WLAN RF output signal to the FEM circuit system 504a for subsequent wireless transmission by one or more antennas 501. The BT wireless IC circuit system 506b may also include a transmission signal path, which may include a circuit system that up-converts the BT baseband signal provided by the BT baseband processing circuit system 508b and provides the BT RF output signal to the FEM circuit system 504b for subsequent wireless transmission by one or more antennas 501. Figure 5 In the embodiments, although wireless IC circuit systems 506a and 506b are shown as different from each other, the embodiments are not so limited and include the use of wireless IC circuit systems (not shown) that include transmit signal paths and / or receive signal paths for both WLAN signals and BT signals, or the use of one or more wireless IC circuit systems, wherein at least some of the wireless IC circuit systems share transmit signal paths and / or receive signal paths for both WLAN signals and BT signals.

[0124] The baseband processing circuit systems 508a-508b may include a WLAN baseband processing circuit system 508a and a BT baseband processing circuit system 508b. The WLAN baseband processing circuit system 508a may include a memory, such as a collection of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the WLAN baseband processing circuit system 508a. Each of the WLAN baseband processing circuit system 508a and the BT baseband circuit system 508b may also include one or more processors and control logic to process signals received from the corresponding WLAN or BT receive signal path of the wireless IC circuit systems 506a-506b, and to generate corresponding WLAN or BT baseband signals for the transmit signal paths of the wireless IC circuit systems 506a-506b. Each of the baseband processing circuit systems 508a and 508b may also include physical layer (PHY) and media access control layer (MAC) circuit systems, and may also be connected to a device interface for generating and processing baseband signals and for controlling the operation of the wireless IC circuit systems 506a-506b.

[0125] Still referencing Figure 5 According to the illustrated embodiment, the WLAN-BT coexistence circuitry system 513 may include logic providing an interface between the WLAN baseband circuitry system 508a and the BT baseband circuitry system 508b to enable use cases requiring WLAN-BT coexistence. Furthermore, a switch 503 may be provided between the WLAN FEM circuitry system 504a and the BT FEM circuitry system 504b to allow switching between WLAN wireless and BT wireless as needed for the application. Additionally, while antennas 501 are depicted as being connected to the WLAN FEM circuitry system 504a and the BT FEM circuitry system 504b respectively, embodiments within their scope include sharing one or more antennas between the WLAN FEM and the BT FEM, or providing more than one antenna connected to each of the FEMs 504a and 504b.

[0126] In some embodiments, the front-end module circuitry 504a-504b, the wireless IC circuitry 506a-506b, and the baseband processing circuitry 508a-508b may be housed on a single wireless card (such as wireless card 502). In some other embodiments, one or more antennas 501, FEM circuitry 504a-504b, and wireless IC circuitry 506a-506b may be housed on a single wireless card. In some other embodiments, the wireless IC circuitry 506a-506b and the baseband processing circuitry 508a-508b may be housed on a single chip or integrated circuit (IC) (such as IC 512).

[0127] In some embodiments, wireless card 502 may include a WLAN wireless card and may be configured for Wi-Fi communication, but the scope of the embodiments is not limited in this respect. In some of these embodiments, wireless architectures 105A, 105B may be configured to receive and transmit orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals via a multi-carrier communication channel. OFDM signals or OFDMA signals may include multiple orthogonal subcarriers.

[0128] In some of these multi-carrier embodiments, wireless architectures 105A and 105B may be part of a Wi-Fi communication station (STA) (such as a wireless access point (AP), base station, or mobile device containing Wi-Fi devices). In some of these embodiments, wireless architectures 105A and 105B may be configured to transmit and receive signals according to specific communication standards and / or protocols (such as any of the Institute of Electrical and Electronics Engineers (IEEE) standards, including 802.11n-2009, IEEE 802.11-2012, IEEE 802.11-2016, 802.11n-2009, 802.11ac, 802.11ah, 802.11ad, 802.11ay, and / or 802.11ax and / or specifications proposed for WLAN), but the scope of the embodiments is not limited in this respect. Wireless architectures 105A and 105B may also be adapted to transmit and / or receive communications according to other technologies and standards.

[0129] In some embodiments, wireless architectures 105A and 105B may be configured for efficient Wi-Fi (HEW) communication according to the IEEE 802.11ax standard. In these embodiments, wireless architectures 105A and 105B may be configured for communication according to OFDMA technology, but the scope of the embodiments is not limited in this respect.

[0130] In some other embodiments, wireless architectures 105A and 105B may be configured to transmit and receive signals transmitted using one or more other modulation techniques, such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and / or frequency hopping code division multiple access (FH-CDMA)), time division multiplexing (TDM) modulation, and / or frequency division multiplexing (FDM) modulation, but the scope of the embodiments is not limited in this respect.

[0131] In some embodiments, such as Figure 5 As further shown, the BT baseband circuit system 508b is compliant with Bluetooth (BT) connectivity standards, such as Bluetooth, Bluetooth 8.0, or Bluetooth 6.0, or any other iteration of the Bluetooth standard.

[0132] In some embodiments, wireless architectures 105A and 105B may include other wireless cards, such as cellular wireless cards configured for cellular (e.g., 5GPP such as LTE, LTE Advanced, or 7G communications).

[0133] In some IEEE 802.11 embodiments, wireless architectures 105A and 105B can be configured to communicate over various channel bandwidths, including bandwidths with center frequencies of approximately 900 MHz, 2.4 GHz, and 5 GHz, and bandwidths of approximately 2 MHz, 4 MHz, 5 MHz, 5.5 MHz, 6 MHz, 8 MHz, 10 MHz, 20 MHz, 40 MHz, 80 MHz (with continuous bandwidth) or 80 MHz + 80 MHz (160 MHz) (with discontinuous bandwidth). In some embodiments, a 920 MHz channel bandwidth may be used. However, the scope of the embodiments is not limited to the aforementioned center frequencies.

[0134] Figure 6 A WLAN FEM circuit system 504a according to some embodiments is illustrated. Although... Figure 6 The example is described in conjunction with the WLANFEM circuit system 504a, but Figure 6 Examples can be combined with example BT FEM circuit system 504b ( Figure 5 Other circuit system configurations can also be appropriate, as described by ) .

[0135] In some embodiments, FEM circuitry 504a may include a TX / RX switch 602 to switch between transmit mode operation and receive mode operation. FEM circuitry 504a may include a receive signal path and a transmit signal path. The receive signal path of FEM circuitry 504a may include a low-noise amplifier (LNA) 606 to amplify the received RF signal 603 and provide the amplified received RF signal 607 as an output (e.g., to wireless IC circuitry 506a-506b). Figure 5 The transmission signal path of circuit system 504a may include: a power amplifier (PA) for amplifying the input RF signal 609 (e.g., provided by wireless IC circuit systems 506a-506b); and one or more filters 612 (such as bandpass filters (BPF), low-pass filters (LPF), or other types of filters) for generating signals for subsequent transmission (e.g., via one or more antennas 501) via example duplexer 614. Figure 5 RF signal 615.

[0136] In some dual-mode embodiments for Wi-Fi communication, the FEM circuit system 504a can be configured to operate in either the 2.4 GHz or 5 GHz spectrum. In these embodiments, the receive signal path of the FEM circuit system 504a may include a receive signal path duplexer 604 to separate signals from individual spectrums and an LNA 606 to provide separation for each spectrum, as shown. In these embodiments, the transmit signal path of the FEM circuit system 504a may also include a power amplifier 610 and a filter 612 (such as a BPF, LPF, or another type of filter for each spectrum), and a transmit signal path duplexer 604 to provide signals from one of the different spectrums onto a single transmit path for transmission through one or more antennas 501 (…). Figure 5 Subsequent transmissions may be performed. In some embodiments, BT communication may utilize a 2.4 GHz signal path and may utilize the same FEM circuitry system 504a as that used for WLAN communication.

[0137] Figure 7 The illustration shows a wireless IC circuit system 506a according to some embodiments. Wireless IC circuit system 506a is suitable for use as a WLAN wireless IC circuit system 506a / BT wireless IC circuit system 506b. Figure 5 This is one example of a circuit system, but other circuit system configurations may also be applicable. Alternatively, Figure 7 An example can be described in conjunction with the example BT wireless IC circuit system 506b.

[0138] In some embodiments, the wireless IC circuit system 506a may include a receive signal path and a transmit signal path. The receive signal path of the wireless IC circuit system 506a may include at least a mixer circuit system 702 (such as the following frequency conversion mixer circuit system as an example), an amplifier circuit system 706, and a filter circuit system 708. The transmit signal path of the wireless IC circuit system 506a may include at least a filter circuit system 712 and a mixer circuit system 714, such as the above frequency conversion mixer circuit system as an example. The wireless IC circuit system 506a may also include a synthesizer circuit system 704 for synthesizing a frequency 705 for use by the mixer circuit systems 702 and 714. According to some embodiments, the mixer circuit system 702 and / or the mixer circuit system 714 may each be configured to provide direct conversion functionality. Compared to a standard superheterodyne mixer circuit system, the latter type of circuit system presents a simpler architecture, and any flicker noise introduced by the latter type of circuit system can be mitigated, for example, by using OFDM modulation. Figure 7Only a simplified version of the wireless IC circuit system is illustrated, and embodiments may include (though not shown) each of the circuit systems depicted that may include more than one component. For example, mixer circuit system 714 may each include one or more mixers, and filter circuit system 708 and / or filter circuit system 712 may each include one or more filters, such as one or more BPFs and / or LPFs depending on application requirements. For example, when the mixer circuit system is of the direct conversion type, the mixer circuit system may each include two or more mixers.

[0139] In some embodiments, mixer circuit system 702 may be configured to, based on the synthesis frequency 705 provided by synthesizer circuit system 704, adjust the frequency from FEM circuit systems 504a-504b. Figure 5 The received RF signal 607 is down-converted. Amplifier circuitry 706 can be configured to amplify the down-converted signal, and filter circuitry 708 may include LPFs configured to remove unwanted signals from the down-converted signal to generate the output baseband signal 707. The output baseband signal 707 can be provided to baseband processing circuitry 508a-508b. Figure 5 This is for further processing. In some embodiments, the output baseband signal 707 may be a zero-frequency baseband signal, but this is not required. In some embodiments, the mixer circuit system 702 may include a passive mixer, but the scope of the embodiments is not limited in this respect.

[0140] In some embodiments, mixer circuitry 714 may be configured to up-convert the input baseband signal 711 based on a synthesis frequency 705 provided by synthesizer circuitry 704 to generate an RF output signal 609 for FEM circuitry 504a-504b. The baseband signal 711 may be provided by baseband processing circuitry 508a-508b and may be filtered by filter circuitry 712. Filter circuitry 712 may include an LPF or a BPF, but the scope of the embodiments is not limited in this respect.

[0141] In some embodiments, mixer circuit system 702 and mixer circuit system 714 may each include two or more mixers and may be arranged to perform quadrature downconversion and / or quadrature upconversion respectively by means of synthesizer 704. In some embodiments, mixer circuit system 702 and mixer circuit system 714 may each include two or more mixers, each mixer being configured for image suppression (e.g., Hartley image suppression). In some embodiments, mixer circuit system 702 and mixer circuit system 714 may be arranged to perform direct downconversion and / or direct upconversion respectively. In some embodiments, mixer circuit system 702 and mixer circuit system 714 may be configured for superheterodyne operation, but this is not required.

[0142] According to one embodiment, the mixer circuit system 702 may include: quadrature passive mixers (e.g., for in-phase (I) paths and quadrature (Q) paths). In this embodiment, from Figure 7 The RF input signal 607 can be down-converted to provide the I baseband output signal and Q baseband output signal to be sent to the baseband processor.

[0143] The quadrature passive mixer can be driven by zero-degree and ninety-degree time-varying LO switching signals provided by a quadrature circuit system, which can be configured to receive the LO frequency (fLO) from a local oscillator or synthesizer, such as the LO frequency 705 of synthesizer 704. Figure 7 In some embodiments, the LO frequency may be the carrier frequency, while in other embodiments, the LO frequency may be a portion of the carrier frequency (e.g., half or one-third of the carrier frequency). In some embodiments, the zero-degree and ninety-degree time-varying switching signals may be generated by a synthesizer, but the scope of the embodiments is not limited in this respect.

[0144] In some embodiments, the LO signal may differ in duty cycle (the percentage of time the LO signal is high within a cycle) and / or offset (the difference between the start points of the cycle). In some embodiments, the LO signal may have an 85% duty cycle and an 80% offset. In some embodiments, each branch of the mixer circuitry (e.g., the in-phase (I) path and the quadrature-phase (Q) path) may operate with an 80% duty cycle, which can result in a significant reduction in power consumption.

[0145] RF input signal 607 ( Figure 6 The output signal may include a balanced signal, but the scope of the embodiments is not limited in this respect. The I-baseband output signal and the Q-baseband output signal may be provided to a low-noise amplifier (such as amplifier circuit system 706). Figure 7 Or to the filter circuit system 708 ( Figure 7 ).

[0146] In some embodiments, the output baseband signal 707 and the input baseband signal 711 may be analog baseband signals, but the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal 707 and the input baseband signal 711 may be digital baseband signals. In these alternative embodiments, the wireless IC circuit system may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuit systems.

[0147] In some dual-mode embodiments, separate wireless IC circuitry systems may be provided to process signals for each spectrum, or signals for other spectrums not mentioned herein, but the scope of the embodiments is not limited in this respect.

[0148] In some embodiments, synthesizer circuitry 704 may be a fractional N synthesizer or a fractional N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuitry 704 may be a Δ-Σ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider. According to some embodiments, synthesizer circuitry 704 may include a digital synthesizer circuitry. The advantage of using a digital synthesizer circuitry is that, although a digital synthesizer circuitry may still include some analog components, the footprint of a digital synthesizer circuitry can be reduced significantly compared to that of an analog synthesizer circuitry. In some embodiments, the frequency input to synthesizer circuitry 704 may be provided by a voltage-controlled oscillator (VCO), but this is not necessary. The frequency divider control input may also be provided by baseband processing circuitry 508a-508b (… Figure 5 The frequency divider control input (e.g., N) is provided according to the desired output frequency 705. In some embodiments, the frequency divider control input (e.g., N) may be determined from a lookup table (e.g., within a Wi-Fi card) based on the channel number and channel center frequency, as determined or indicated by the example application processor 510. The application processor 510 may include or be otherwise connected to one of the example security signal converter 101 or the example receive signal converter 103 (e.g., depending on which device the example wireless architecture is implemented in).

[0149] In some embodiments, the synthesizer circuitry 704 may be configured to generate a carrier frequency as an output frequency 705, while in other embodiments, the output frequency 705 may be a portion of the carrier frequency (e.g., half or one-third of the carrier frequency). In some embodiments, the output frequency 705 may be the LO frequency (fLO).

[0150] Figure 8 The illustration shows a functional block diagram of a baseband processing circuit system 508a according to some embodiments. The baseband processing circuit system 508a is suitable for use as a baseband processing circuit system 508a. Figure 5This is one example of a circuit system, but other circuit system configurations may also be suitable. Alternatively, one can use... Figure 7 Example implementation Figure 5 Example BT baseband processing circuit system 508b.

[0151] Baseband processing circuitry system 508a may include methods for processing data generated by wireless IC circuitry systems 506a-506b. Figure 5 The baseband processing circuit system 506a provides a receive baseband signal 709 and a transmit baseband processor (TX BBP) 804 for generating transmit baseband signals 711 for the wireless IC circuit systems 506a-506b. The baseband processing circuit system 506a may also include control logic 806 for coordinating the operation of the baseband processing circuit system 506a.

[0152] In some embodiments (e.g., when analog baseband signals are exchanged between baseband processing circuit systems 508a-508b and wireless IC circuit systems 506a-506b), baseband processing circuit system 508a may include an ADC 810 to convert analog baseband signals 809 received from wireless IC circuit systems 506a-506b into digital baseband signals for processing by RX BBP 802. In these embodiments, baseband processing circuit system 508a may also include a DAC 812 to convert digital baseband signals from TX BBP 804 into analog baseband signals 811.

[0153] In some embodiments (such as those transmitting OFDM or OFDMA signals via baseband processor 508a), the transmitting baseband processor 804 may be configured to generate an OFDM or OFDMA signal suitable for transmission by performing an inverse fast Fourier transform (IFFT). The receiving baseband processor 802 may be configured to process the received OFDM or OFDMA signal by performing an FFT. In some embodiments, the receiving baseband processor 802 may be configured to: detect the presence of an OFDM or OFDMA signal by performing autocorrelation; detect a preamble, such as a short preamble; and detect a long preamble by performing cross-correlation. The preamble may be part of a predetermined frame structure for Wi-Fi communication.

[0154] Return to reference Figure 5 In some embodiments, antenna 501 ( Figure 5Each antenna 501 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmitting RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result. Each antenna 501 may include a collection of phased array antennas, but embodiments are not so limited.

[0155] Although the wireless architectures 105A and 105B are illustrated as having several separate functional elements, one or more functional elements may be combined and implemented by a combination of software-configurable elements, such as processing elements including digital signal processors (DSPs) and / or other hardware elements. For example, some elements may include combinations of one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), radio frequency integrated circuits (RFICs), and various hardware and logic circuit systems for performing the functions described at least herein. In some embodiments, a functional element may refer to one or more processes operating on one or more processing elements.

[0156] The term "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or superior to other embodiments. As used herein, the terms "computing device," "user device," "communication station," "station," "handheld device," "mobile device," "wireless device," and "user equipment (UE)" refer to wireless communication devices such as cellular phones, smartphones, tablet computers, netbooks, wireless terminals, laptop computers, femtocells, high-speed data rate (HDR) subscriber stations, access points, printers, point-of-sale equipment, access terminals, or other personal communication systems (PCS) devices. Devices may be mobile or fixed.

[0157] As used herein, the term "communication" is intended to include sending or receiving, or both. This may be particularly useful in claims describing the organization of data sent by one device and received by another device, but only the functionality of one of those devices is required to constitute an infringement of the claim. Similarly, a two-way exchange of data between two devices (where both devices send and receive during the exchange) may be described as "communication" when only the functionality of one of those devices is claimed. As used herein, the term "communication" relating to wireless communication signals includes sending and / or receiving wireless communication signals. For example, a wireless communication unit capable of transmitting wireless communication signals may include: a wireless transmitter for sending wireless communication signals to at least one other wireless communication unit; and / or a wireless communication receiver for receiving wireless communication signals from at least one other wireless communication unit.

[0158] As used herein, unless otherwise stated, the use of ordinal adjectives such as “first,” “second,” “third,” etc., to describe a common object merely indicates different instances of the similar object being referred to, and is not intended to imply that the objects so described must be in a given order, whether in time, space, ordering, or in any other way.

[0159] As used herein, the term "access point (AP)" may refer to a fixed station. An access point may also be referred to as an access node, base station, evolved Node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be referred to as a mobile station, user equipment (UE), wireless communication device, or some other similar terminology known in the art. The embodiments disclosed herein generally relate to wireless networks. Some embodiments may relate to wireless networks operating according to one of the IEEE 802.11 standards.

[0160] Some embodiments can be used with a variety of devices and systems, such as personal computers (PCs), desktop computers, mobile computers, laptop computers, notebook computers, tablet computers, server computers, handheld computers, handheld devices, personal digital assistant (PDA) devices, handheld PDA devices, in-vehicle devices, off-vehicle devices, hybrid devices, vehicle devices, non-vehicle devices, mobile or portable devices, consumer devices, non-mobile or non-portable devices, wireless communication stations, wireless communication devices, wireless access points (APs), wired or wireless routers, wired or wireless modems, video devices, audio devices, audio-video (A / V) devices, wired or wireless networks, wireless local area networks, wireless video local area networks (WVANs), local area networks (LANs), wireless LANs (WLANs), personal area networks (PANs), wireless PANs (WPANs), etc.

[0161] Some embodiments may be used in conjunction with one-way and / or two-way wireless communication systems, cellular wireless-telephone communication systems, mobile phones, cell phones, cordless phones, personal communication system (PCS) devices, PDA devices containing wireless communication devices, mobile or portable global positioning system (GPS) devices, devices containing GPS receivers or transceivers or chips, devices containing RFID elements or chips, multiple-input multiple-output (MIMO) transceivers or devices, single-input multiple-output (SIMO) transceivers or devices, multiple-input single-output (MISO) transceivers or devices, devices with one or more internal antennas and / or external antennas, digital video broadcasting (DVB) devices or systems, multi-standard wireless devices or systems, wired or wireless handheld devices (e.g., smartphones), Wireless Application Protocol (WAP) devices, etc.

[0162] Some embodiments may be compatible with one or more wireless communication protocols, such as radio frequency (RF), infrared (IR), frequency division multiplexing (FDM), orthogonal FDM (OFDM), time division multiplexing (TDM), time division multiple access (TDMA), extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, code division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), and Bluetooth. ® This can be used in combination with one or more types of wireless communication signals and / or systems, including Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee, Ultra-Wideband (UWB), Global System for Mobile Communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, 5G mobile networks, 3GPP, Long Term Evolution (LTE), LTE Advanced, and Enhanced Data Rate Evolution of GSM (EDGE). Other embodiments can be used in various other devices, systems, and / or networks.

[0163] The following examples relate to further embodiments.

[0164] Example 1 may include an apparatus comprising a processing circuitry coupled to a storage device, the processing circuitry being configured to: negotiate control frame protection with a peer; establish a pairwise temporary key security association (PTKSA) with the peer; receive control frames from the peer; and discard control frames based on the control frames being included in a list of discarded control frames and after the PTKSA is established.

[0165] Example 2 may include the device of Example 1 and / or some other examples herein, wherein the list of discarded control frames includes unprotected individual addressing control frames that are defined as pending protection.

[0166] Example 3 may include the device of Example 1 and / or some other examples herein, wherein the list of discarded control frames includes unprotected group addressing control frames that are defined as pending protection.

[0167] Example 4 may include the device of Example 1 and / or some other examples herein, wherein the list of discarded control frames includes acknowledgment (Ack) frames and compressed BlockAck frames.

[0168] Example 5 may include the device of Example 1 and / or some other examples herein, wherein, if multicast with retry (GCR) is supported, the list of dropped control frames includes GCR BlockAck frames and GCRBlockAckReq frames.

[0169] Example 6 may include the device of Example 1 and / or some other examples herein, wherein the processing circuitry may also be configured such that, after PTKSA is established, the package is defined as a separate addressing control frame to be protected based on the control frame protection process.

[0170] Example 7 may include the device of Example 1 and / or some other examples herein, wherein the processing circuitry may also be configured to prohibit the transmission of empty frames to the Quality of Service (QoS) station based on at least one of control frame protection being negotiated, DUO being enabled, or LLI being enabled.

[0171] Example 8 may include the device of Example 1 and / or some other examples herein, wherein the processing circuitry may also be configured to: acknowledge empty frames based on the acknowledgment context within a multi-station block acknowledgment (M-BA).

[0172] Example 9 may include the device of Example 1 and / or some other examples herein, wherein the processing circuitry may also be configured to: use protected multi-station block acknowledgment (Multi-STA BA) to acknowledge control frames and discard control frames.

[0173] Example 10 may include a non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors, cause to perform operations including: negotiating control frame protection with a peer; establishing a pairwise temporary key security association (PTKSA) with the peer; receiving a control frame from the peer; and discarding the control frame based on the control frame being included in a list of discarded control frames and after the PTKSA is established.

[0174] Example 11 may include the non-transitory computer-readable medium of Example 10 and / or some other examples herein, wherein the list of discarded control frames includes unprotected individual addressing control frames that are defined as pending protection.

[0175] Example 12 may include the non-transitory computer-readable medium of Example 10 and / or some other examples herein, wherein the list of discarded control frames includes unprotected group addressing control frames that are defined as pending protection.

[0176] Example 13 may include the non-transitory computer-readable medium of Example 10 and / or some other examples herein, wherein the list of discarded control frames includes acknowledgment (Ack) frames and compressed BlockAck frames.

[0177] Example 14 may include the non-transitory computer-readable medium of Example 10 and / or some other examples herein, wherein, if multicast with retry (GCR) is supported, the list of discard control frames includes GCR BlockAck frames and GCRBlockAckReq frames.

[0178] Example 15 may include the non-transitory computer-readable medium of Example 10 and / or some other examples herein, wherein the operation further includes: after PTKSA is established, the encapsulation is defined as a separate addressing control frame to be protected based on the control frame protection process.

[0179] Example 16 may include the non-transitory computer-readable medium of Example 10 and / or some other examples herein, wherein the operation further includes: prohibiting the transmission of empty frames to a Quality of Service (QoS) station based on at least one of control frame protection being negotiated, DUO being enabled, or LLI being enabled.

[0180] Example 17 may include the non-transitory computer-readable medium of Example 10 and / or some other examples herein, wherein the operation further includes: confirming an empty frame based on the confirmation context within a multi-station block confirmation (M-BA).

[0181] Example 18 may include the non-transitory computer-readable medium of Example 10 and / or some other examples herein, wherein the operation further includes: using protected multi-station block acknowledgment (Multi-STA BA) to acknowledge control frames and discard control frames.

[0182] Example 19 may include a method comprising: negotiating control frame protection with a peer; establishing a pairwise temporary key security association (PTKSA) with the peer; receiving a control frame from the peer; and discarding the control frame based on the control frame being included in a list of discarded control frames and after the PTKSA is established.

[0183] Example 20 may include the method of Example 19 and / or some other examples herein, wherein the list of discarded control frames includes unprotected individual addressing control frames that are defined as pending protection.

[0184] Example 21 may include the method of Example 19 and / or some other examples herein, wherein the list of discarded control frames includes unprotected group addressing control frames that are defined as pending protection.

[0185] Example 22 may include the method of Example 19 and / or some other examples herein, wherein the list of discarded control frames includes acknowledgment (Ack) frames and compressed BlockAck frames.

[0186] Example 23 may include the method of Example 19 and / or some other examples herein, wherein, if multicast with retry (GCR) is supported, the list of discard control frames includes GCR BlockAck frames and GCRBlockAckReq frames.

[0187] Example 24 may include the method of Example 19 and / or some other examples herein, the method further comprising: after PTKSA is established, the encapsulation is defined as a single addressing control frame to be protected based on the control frame protection process.

[0188] Example 25 may include the method of Example 19 and / or some other examples herein, the method further comprising: prohibiting the transmission of empty frames to a Quality of Service (QoS) station based on at least one of control frame protection being negotiated, DUO being enabled, or LLI being enabled.

[0189] Example 26 may include the method of Example 19 and / or some other examples herein, which further includes: confirming empty frames based on the confirmation context within a multi-station block confirmation (M-BA).

[0190] Example 27 may include the methods of Example 19 and / or some other examples herein, which further include: using protected multi-station block acknowledgment (Multi-STA BA) to acknowledge control frames and discard control frames.

[0191] Example 28 may include an apparatus comprising means for: negotiating control frame protection with a peer; establishing a pairwise temporary key security association (PTKSA) with the peer; receiving control frames from the peer; and discarding control frames based on the fact that the control frames are included in a list of discarded control frames and after the PTKSA is established.

[0192] Example 29 may include the apparatus of Example 28 and / or some other examples herein, wherein the list of discarded control frames includes unprotected individual addressing control frames that are defined as pending protection.

[0193] Example 30 may include the apparatus of Example 28 and / or some other examples herein, wherein the list of discarded control frames includes unprotected group addressing control frames that are defined as pending protection.

[0194] Example 31 may include the apparatus of Example 28 and / or some other examples herein, wherein the list of discarded control frames includes acknowledgment (Ack) frames and compressed BlockAck frames.

[0195] Example 32 may include the apparatus of Example 28 and / or some other examples herein, wherein, if multicast with retry (GCR) is supported, the list of discard control frames includes GCR BlockAck frames and GCRBlockAckReq frames.

[0196] Example 33 may include the apparatus of Example 28 and / or some other examples herein, and also includes: after PTKSA is established, the encapsulation is defined as a separate addressing control frame to be protected based on the control frame protection process.

[0197] Example 34 may include the apparatus of Example 28 and / or some other examples herein, and also includes: prohibiting the transmission of empty frames to a Quality of Service (QoS) station based on at least one of control frame protection being negotiated, DUO being enabled, or LLI being enabled.

[0198] Example 35 may include the apparatus of Example 28 and / or some other examples herein, and also includes: confirming empty frames based on the confirmation context within a multi-station block confirmation (M-BA).

[0199] Example 36 may include the apparatus of Example 28 and / or some other examples herein, and may also include: protected multi-station block acknowledgment (Multi-STA BA) may be used to acknowledge control frames and discard control frames.

[0200] Example 37 may include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the methods described in or associated with any of Examples 1-36, or any other methods or processes described herein.

[0201] Example 38 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the methods described in or associated with any of Examples 1-36, or any other methods or processes described herein.

[0202] Example 39 may include a method, technique, or process, or a part or component thereof, as described in or related to any of Examples 1-36.

[0203] Example 40 may include an apparatus comprising: one or more processors; and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform, or a portion thereof, a method, technique, or process as described in or related to any of Examples 1-36.

[0204] Example 41 may include a communication method in a wireless network as shown in the figure and described herein.

[0205] Example 42 may include a system for providing wireless communication, as shown in the figure and described herein.

[0206] Example 43 may include a device for providing wireless communication, as shown in the figure and described herein.

[0207] Embodiments according to this disclosure are specifically disclosed in the appended claims, which relate to methods, storage media, apparatus, and computer program products, wherein any feature mentioned in one claim class (e.g., method) can also be claimed in another claim class (e.g., system). Dependencies or references in the appended claims are chosen solely for formal reasons. However, any subject matter arising from the deliberate reference to any prior claim (particularly multiple dependencies) can also be claimed, such that any combination of claims and their features is disclosed and can be claimed regardless of the dependencies chosen in the appended claims. Claimable subject matter includes not only combinations of features set forth in the appended claims but also any other combinations of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other features in the claims. Furthermore, any embodiments and features described or depicted herein can be claimed in a separate claim and / or in any combination with any embodiments or features described or depicted herein or with any features of the appended claims.

[0208] The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in accordance with the foregoing teachings, or may be obtained from practice of various embodiments.

[0209] The foregoing description of block diagrams and flowcharts of systems, methods, apparatuses, and / or computer program products according to various implementations has described certain aspects of this disclosure. It will be understood that one or more blocks of the block diagrams and flowcharts, as well as combinations of blocks in the block diagrams and flowcharts, can be implemented by computer-executable program instructions, respectively. Similarly, depending on some implementations, some blocks of the block diagrams and flowcharts may not necessarily need to be executed in the order presented, or may not need to be executed at all.

[0210] These computer-executable program instructions may be loaded onto a special-purpose computer or other specific machine, processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions, which execute on the computer, processor, or other programmable data processing apparatus, create means for implementing one or more functions specified in one or more flowchart blocks. These computer program instructions may also be stored in a computer-readable storage medium or memory that can direct the computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of writing comprising means for implementing one or more functions specified in one or more flowchart blocks. As an example, some implementations may provide a computer program product including a computer-readable storage medium having computer-readable program code or program instructions implemented therein, the computer-readable program code being adapted to be executed to implement one or more functions specified in one or more flowchart blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide elements or steps for implementing the functions specified in one or more flowchart blocks.

[0211] Therefore, the blocks in block diagrams and flowcharts support combinations of means for performing a specified function, combinations of elements or steps for performing a specified function, and program instruction means for performing a specified function. It will also be understood that each block in a block diagram and flowchart, and combinations of blocks in block diagrams and flowcharts, can be implemented by a hardware-based dedicated computer system that performs the specified function, element, or step, or by a combination of dedicated hardware and computer instructions.

[0212] Unless otherwise explicitly stated or understood in the context of use, conditional languages ​​(such as “can,” “may,” “may,” or “may”) are generally intended to convey that certain implementations may include certain features, elements, and / or operations, while other implementations do not. Therefore, such conditional languages ​​are not generally intended to imply that features, elements, and / or operations are required in any way for one or more implementations, or that one or more implementations necessarily include logic for determining whether such features, elements, and / or operations are included in or to be performed in any particular implementation, regardless of user input or prompts.

[0213] Many modifications and other implementations of the present disclosure set forth herein will be apparent from the teachings presented in the foregoing description and associated drawings. Therefore, it is to be understood that the present disclosure is not limited to the specific implementations disclosed, and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terminology is used herein, it is used in a general and descriptive sense only and not for purposes of limitation.

Claims

1. An apparatus for controlling frame protection, comprising a processing circuitry system coupled to a storage device, the processing circuitry system being configured to: Negotiate control frame protection with peer stations; Establish a pairwise temporary key security association (PTKSA) with the peer station; Receive control frames from the peer station; as well as The control frame is discarded based on its inclusion in the list of discarded control frames and after the PTKSA is established.

2. The device according to claim 1, wherein, The list of discarded control frames includes unprotected individual addressing control frames, which are defined as pending protection.

3. The device according to claim 1, wherein, The list of discarded control frames includes unprotected group addressing control frames, which are defined as pending protection.

4. The device according to claim 1, wherein, The list of discard control frames includes acknowledgment (Ack) frames and compressed block acknowledgment frames.

5. The device according to claim 1, wherein, If multicast with retry (GCR) is supported, the list of discard control frames includes GCR block acknowledgment frames and GCR block acknowledgment request frames.

6. The device according to claim 1, wherein, The processing circuitry is further configured such that, after the PTKSA is established, the encapsulation is defined as a single addressing control frame to be protected based on the control frame protection process.

7. The device according to claim 1, wherein, The processing circuitry is also configured to prohibit the transmission of empty frames to the Quality of Service (QoS) station based on at least one of the following: control frame protection being negotiated, dynamic unavailable operation being enabled, or low latency indication being enabled.

8. The device according to claim 1, wherein, The processing circuitry is also configured to: confirm empty frames based on the confirmation context within the multi-station block confirmation (M-BA).

9. The device according to claim 1, wherein, The processing circuitry is also configured to use protected multi-station block acknowledgment (Multi-STA BA) to acknowledge and discard the control frame.

10. A computer-readable medium storing computer-executable instructions, which, when executed by one or more processors, cause to perform operations, the operations including: Negotiate control frame protection with peer stations; Establish a pairwise temporary key security association (PTKSA) with the peer station; Receive control frames from the peer station; as well as The control frame is discarded based on its inclusion in the list of discarded control frames and after the PTKSA is established.

11. The computer-readable medium of claim 10, wherein, The list of discarded control frames includes unprotected individual addressing control frames, which are defined as pending protection.

12. The computer-readable medium of claim 10, wherein, The list of discarded control frames includes unprotected group addressing control frames, which are defined as pending protection.

13. The computer-readable medium of claim 10, wherein, The list of discard control frames includes acknowledgment (Ack) frames and compressed block acknowledgment frames.

14. The computer-readable medium of claim 10, wherein, If multicast with retry (GCR) is supported, the list of discard control frames includes GCR block acknowledgment frames and GCR block acknowledgment request frames.

15. The computer-readable medium of claim 10, wherein, The operation further includes: after the PTKSA is established, the encapsulation is defined as a single addressing control frame to be protected based on the control frame protection process.

16. The computer-readable medium of claim 10, wherein, The operation further includes: prohibiting the transmission of empty frames to the Quality of Service (QoS) station based on at least one of the control frame protection being negotiated, dynamic unavailable operation being enabled, or low latency indication being enabled.

17. The computer-readable medium of claim 10, wherein, The operation also includes: confirming empty frames based on the confirmation context within the Multi-Station Block Confirmation (M-BA).

18. The computer-readable medium of claim 10, wherein, The operation also includes: discarding the control frame based on the protection of multi-station block acknowledgment (Multi-STA BA) that can be used to acknowledge the control frame.

19. A method for controlling frame protection, comprising: Negotiate control frame protection with peer stations; Establish a pairwise temporary key security association (PTKSA) with the peer station; Receive control frames from the peer station; as well as The control frame is discarded based on its inclusion in the list of discarded control frames and after the PTKSA is established.

20. The method according to claim 19, wherein, The list of discarded control frames includes unprotected individual addressing control frames, which are defined as pending protection.